summaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/aot-compile.139
-rw-r--r--gcc/doc/cpp.179
-rw-r--r--gcc/doc/cpp.info3716
-rw-r--r--gcc/doc/cppinternals.info698
-rw-r--r--gcc/doc/extend.texi24
-rw-r--r--gcc/doc/fsf-funding.741
-rw-r--r--gcc/doc/g++.11122
-rw-r--r--gcc/doc/gc-analyze.139
-rw-r--r--gcc/doc/gcc.11122
-rw-r--r--gcc/doc/gcc.info39562
-rw-r--r--gcc/doc/gccinstall.info3809
-rw-r--r--gcc/doc/gccint.info38991
-rw-r--r--gcc/doc/gcj-dbtool.139
-rw-r--r--gcc/doc/gcj.173
-rw-r--r--gcc/doc/gcj.info2277
-rw-r--r--gcc/doc/gcov-tool.139
-rw-r--r--gcc/doc/gcov.143
-rw-r--r--gcc/doc/gfdl.777
-rw-r--r--gcc/doc/gfortran.173
-rw-r--r--gcc/doc/gij.139
-rw-r--r--gcc/doc/gpl.793
-rw-r--r--gcc/doc/grmic.143
-rw-r--r--gcc/doc/install.texi13
-rw-r--r--gcc/doc/invoke.texi29
-rw-r--r--gcc/doc/jcf-dump.139
-rw-r--r--gcc/doc/jv-convert.139
-rw-r--r--gcc/doc/md.texi21
-rw-r--r--gcc/doc/rebuild-gcj-db.139
28 files changed, 46600 insertions, 45618 deletions
diff --git a/gcc/doc/aot-compile.1 b/gcc/doc/aot-compile.1
index ff4988c49a..3ff4d20a6a 100644
--- a/gcc/doc/aot-compile.1
+++ b/gcc/doc/aot-compile.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "AOT-COMPILE 1"
-.TH AOT-COMPILE 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH AOT-COMPILE 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/cpp.1 b/gcc/doc/cpp.1
index cc0583a153..01bf9702b7 100644
--- a/gcc/doc/cpp.1
+++ b/gcc/doc/cpp.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "CPP 1"
-.TH CPP 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH CPP 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -181,11 +180,11 @@ Wherever possible, you should use a preprocessor geared to the language
you are writing in. Modern versions of the \s-1GNU\s0 assembler have macro
facilities. Most high level programming languages have their own
conditional compilation and inclusion mechanism. If all else fails,
-try a true general text processor, such as \s-1GNU M4.\s0
+try a true general text processor, such as \s-1GNU\s0 M4.
.PP
-C preprocessors vary in some details. This manual discusses the \s-1GNU C\s0
+C preprocessors vary in some details. This manual discusses the \s-1GNU\s0 C
preprocessor, which provides a small superset of the features of \s-1ISO\s0
-Standard C. In its default mode, the \s-1GNU C\s0 preprocessor does not do a
+Standard C. In its default mode, the \s-1GNU\s0 C preprocessor does not do a
few things required by the standard. These are features which are
rarely, if ever, used, and may cause surprising changes to the meaning
of a program which does not expect them. To get strict \s-1ISO\s0 Standard C,
@@ -202,7 +201,7 @@ differences that do exist are detailed in the section \fBTraditional
Mode\fR.
.PP
For clarity, unless noted otherwise, references to \fB\s-1CPP\s0\fR in this
-manual refer to \s-1GNU CPP.\s0
+manual refer to \s-1GNU\s0 \s-1CPP\s0.
.SH "OPTIONS"
.IX Header "OPTIONS"
The C preprocessor expects two file names as arguments, \fIinfile\fR and
@@ -306,7 +305,7 @@ get trigraph conversion without warnings, but get the other
.IP "\fB\-Wtraditional\fR" 4
.IX Item "-Wtraditional"
Warn about certain constructs that behave differently in traditional and
-\&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C
+\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
equivalent, and problematic constructs which should be avoided.
.IP "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
@@ -359,7 +358,7 @@ in finding bugs in your own code, therefore suppressed. If you are
responsible for the system library, you may want to see them.
.IP "\fB\-w\fR" 4
.IX Item "-w"
-Suppress all warnings, including those which \s-1GNU CPP\s0 issues by default.
+Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default.
.IP "\fB\-pedantic\fR" 4
.IX Item "-pedantic"
Issue all the mandatory diagnostics listed in the C standard. Some of
@@ -531,7 +530,7 @@ may be one of:
.el .IP "\f(CWiso9899:1990\fR" 4
.IX Item "iso9899:1990"
.PD
-The \s-1ISO C\s0 standard from 1990. \fBc90\fR is the customary shorthand for
+The \s-1ISO\s0 C standard from 1990. \fBc90\fR is the customary shorthand for
this version of the standard.
.Sp
The \fB\-ansi\fR option is equivalent to \fB\-std=c90\fR.
@@ -553,7 +552,7 @@ The 1990 C standard, as amended in 1994.
.el .IP "\f(CWc9x\fR" 4
.IX Item "c9x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 1999. Before
+The revised \s-1ISO\s0 C standard, published in December 1999. Before
publication, this was known as C9X.
.ie n .IP """iso9899:2011""" 4
.el .IP "\f(CWiso9899:2011\fR" 4
@@ -566,7 +565,7 @@ publication, this was known as C9X.
.el .IP "\f(CWc1x\fR" 4
.IX Item "c1x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 2011. Before
+The revised \s-1ISO\s0 C standard, published in December 2011. Before
publication, this was known as C1X.
.ie n .IP """gnu90""" 4
.el .IP "\f(CWgnu90\fR" 4
@@ -598,7 +597,7 @@ The 2011 C standard plus \s-1GNU\s0 extensions.
.ie n .IP """c++98""" 4
.el .IP "\f(CWc++98\fR" 4
.IX Item "c++98"
-The 1998 \s-1ISO \*(C+\s0 standard plus amendments.
+The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
.ie n .IP """gnu++98""" 4
.el .IP "\f(CWgnu++98\fR" 4
.IX Item "gnu++98"
@@ -753,7 +752,7 @@ line. If the value is less than 1 or greater than 100, the option is
ignored. The default is 8.
.IP "\fB\-fdebug\-cpp\fR" 4
.IX Item "-fdebug-cpp"
-This option is only useful for debugging \s-1GCC. \s0 When used with
+This option is only useful for debugging \s-1GCC\s0. When used with
\&\fB\-E\fR, dumps debugging information about location maps. Every
token in the output is preceded by the dump of the map its location
belongs to. The dump of the map holding the location of a token would
@@ -786,12 +785,12 @@ Note that \f(CW\*(C`\-ftrack\-macro\-expansion=2\*(C'\fR is activated by default
.IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fexec-charset=charset"
Set the execution character set, used for string and character
-constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding
+constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
.IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fwide-exec-charset=charset"
Set the wide execution character set, used for wide string and
-character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16,\s0 whichever
+character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever
corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with
\&\fB\-fexec\-charset\fR, \fIcharset\fR can be any encoding supported
by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have
@@ -799,9 +798,9 @@ problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR.
.IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4
.IX Item "-finput-charset=charset"
Set the input character set, used for translation from the character
-set of the input file to the source character set used by \s-1GCC. \s0 If the
+set of the input file to the source character set used by \s-1GCC\s0. If the
locale does not specify, or \s-1GCC\s0 cannot get this information from the
-locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale
+locale, the default is \s-1UTF\-8\s0. This can be overridden by either the locale
or this command-line option. Currently the command-line option takes
precedence if there's a conflict. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
@@ -838,7 +837,7 @@ Cancel an assertion with the predicate \fIpredicate\fR and answer
.IX Item "-dCHARS"
\&\fI\s-1CHARS\s0\fR is a sequence of one or more of the following characters,
and must not be preceded by a space. Other characters are interpreted
-by the compiler proper, or reserved for future versions of \s-1GCC,\s0 and so
+by the compiler proper, or reserved for future versions of \s-1GCC\s0, and so
are silently ignored. If you specify characters whose behavior
conflicts, the result is undefined.
.RS 4
@@ -914,7 +913,7 @@ The \fB\-CC\fR option is generally used to support lint comments.
.IP "\fB\-traditional\-cpp\fR" 4
.IX Item "-traditional-cpp"
Try to imitate the behavior of old-fashioned C preprocessors, as
-opposed to \s-1ISO C\s0 preprocessors.
+opposed to \s-1ISO\s0 C preprocessors.
.IP "\fB\-trigraphs\fR" 4
.IX Item "-trigraphs"
Process trigraph sequences.
@@ -932,7 +931,7 @@ Print text describing all the command-line options instead of
preprocessing anything.
.IP "\fB\-v\fR" 4
.IX Item "-v"
-Verbose mode. Print out \s-1GNU CPP\s0's version number at the beginning of
+Verbose mode. Print out \s-1GNU\s0 \s-1CPP\s0's version number at the beginning of
execution, and report the final form of the include path.
.IP "\fB\-H\fR" 4
.IX Item "-H"
@@ -947,7 +946,7 @@ header file is printed with \fB...x\fR and a valid one with \fB...!\fR .
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
.PD
-Print out \s-1GNU CPP\s0's version number. With one dash, proceed to
+Print out \s-1GNU\s0 \s-1CPP\s0's version number. With one dash, proceed to
preprocess as normal. With two dashes, exit immediately.
.SH "ENVIRONMENT"
.IX Header "ENVIRONMENT"
@@ -959,7 +958,7 @@ Note that you can also specify places to search using options such as
\&\fB\-I\fR, and control dependency output with options like
\&\fB\-M\fR. These take precedence over
environment variables, which in turn take precedence over the
-configuration of \s-1GCC.\s0
+configuration of \s-1GCC\s0.
.IP "\fB\s-1CPATH\s0\fR" 4
.IX Item "CPATH"
.PD 0
diff --git a/gcc/doc/cpp.info b/gcc/doc/cpp.info
index ec7b87a6ea..51c14e815f 100644
--- a/gcc/doc/cpp.info
+++ b/gcc/doc/cpp.info
@@ -1,4 +1,5 @@
-This is cpp.info, produced by makeinfo version 5.2 from cpp.texi.
+This is doc/cpp.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/doc/cpp.texi.
Copyright (C) 1987-2015 Free Software Foundation, Inc.
@@ -18,8 +19,9 @@ are (a) (see below), and the Back-Cover Texts are (b) (see below).
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
* Cpp: (cpp). The GNU C preprocessor.
@@ -55,7 +57,7 @@ useful on its own.
* Option Index::
* Concept Index::
- -- The Detailed Node Listing --
+ --- The Detailed Node Listing ---
Overview
@@ -130,7 +132,6 @@ Obsolete Features
* Obsolete Features::
-
Copyright (C) 1987-2015 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
@@ -149,8 +150,8 @@ are (a) (see below), and the Back-Cover Texts are (b) (see below).
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.

File: cpp.info, Node: Overview, Next: Header Files, Prev: Top, Up: Top
@@ -158,10 +159,11 @@ File: cpp.info, Node: Overview, Next: Header Files, Prev: Top, Up: Top
1 Overview
**********
-The C preprocessor, often known as "cpp", is a "macro processor" that is
-used automatically by the C compiler to transform your program before
-compilation. It is called a macro processor because it allows you to
-define "macros", which are brief abbreviations for longer constructs.
+The C preprocessor, often known as "cpp", is a "macro processor" that
+is used automatically by the C compiler to transform your program
+before compilation. It is called a macro processor because it allows
+you to define "macros", which are brief abbreviations for longer
+constructs.
The C preprocessor is intended to be used only with C, C++, and
Objective-C source code. In the past, it has been abused as a general
@@ -174,7 +176,7 @@ will be removed, and the Makefile will not work.
Having said that, you can often get away with using cpp on things
which are not C. Other Algol-ish programming languages are often safe
-(Pascal, Ada, etc.) So is assembly, with caution. '-traditional-cpp'
+(Pascal, Ada, etc.) So is assembly, with caution. `-traditional-cpp'
mode preserves more white space, and is otherwise more permissive. Many
of the problems can be avoided by writing C or C++ style comments
instead of native language comments, and keeping macros simple.
@@ -182,8 +184,8 @@ instead of native language comments, and keeping macros simple.
Wherever possible, you should use a preprocessor geared to the
language you are writing in. Modern versions of the GNU assembler have
macro facilities. Most high level programming languages have their own
-conditional compilation and inclusion mechanism. If all else fails, try
-a true general text processor, such as GNU M4.
+conditional compilation and inclusion mechanism. If all else fails,
+try a true general text processor, such as GNU M4.
C preprocessors vary in some details. This manual discusses the GNU
C preprocessor, which provides a small superset of the features of ISO
@@ -191,9 +193,9 @@ Standard C. In its default mode, the GNU C preprocessor does not do a
few things required by the standard. These are features which are
rarely, if ever, used, and may cause surprising changes to the meaning
of a program which does not expect them. To get strict ISO Standard C,
-you should use the '-std=c90', '-std=c99' or '-std=c11' options,
+you should use the `-std=c90', `-std=c99' or `-std=c11' options,
depending on which version of the standard you want. To get all the
-mandatory diagnostics, you must also use '-pedantic'. *Note
+mandatory diagnostics, you must also use `-pedantic'. *Note
Invocation::.
This manual describes the behavior of the ISO preprocessor. To
@@ -202,7 +204,7 @@ does not conflict with traditional semantics, the traditional
preprocessor should behave the same way. The various differences that
do exist are detailed in the section *note Traditional Mode::.
- For clarity, unless noted otherwise, references to 'CPP' in this
+ For clarity, unless noted otherwise, references to `CPP' in this
manual refer to GNU CPP.
* Menu:
@@ -224,42 +226,42 @@ there are really at least four.
The files input to CPP might be in any character set at all. CPP's
very first action, before it even looks for line boundaries, is to
-convert the file into the character set it uses for internal processing.
-That set is what the C standard calls the "source" character set. It
-must be isomorphic with ISO 10646, also known as Unicode. CPP uses the
-UTF-8 encoding of Unicode.
+convert the file into the character set it uses for internal
+processing. That set is what the C standard calls the "source"
+character set. It must be isomorphic with ISO 10646, also known as
+Unicode. CPP uses the UTF-8 encoding of Unicode.
The character sets of the input files are specified using the
-'-finput-charset=' option.
+`-finput-charset=' option.
All preprocessing work (the subject of the rest of this manual) is
carried out in the source character set. If you request textual output
-from the preprocessor with the '-E' option, it will be in UTF-8.
+from the preprocessor with the `-E' option, it will be in UTF-8.
After preprocessing is complete, string and character constants are
-converted again, into the "execution" character set. This character set
-is under control of the user; the default is UTF-8, matching the source
-character set. Wide string and character constants have their own
-character set, which is not called out specifically in the standard.
-Again, it is under control of the user. The default is UTF-16 or
-UTF-32, whichever fits in the target's 'wchar_t' type, in the target
-machine's byte order.(1) Octal and hexadecimal escape sequences do not
-undergo conversion; '\x12' has the value 0x12 regardless of the
+converted again, into the "execution" character set. This character
+set is under control of the user; the default is UTF-8, matching the
+source character set. Wide string and character constants have their
+own character set, which is not called out specifically in the
+standard. Again, it is under control of the user. The default is
+UTF-16 or UTF-32, whichever fits in the target's `wchar_t' type, in the
+target machine's byte order.(1) Octal and hexadecimal escape sequences
+do not undergo conversion; '\x12' has the value 0x12 regardless of the
currently selected execution character set. All other escapes are
replaced by the character in the source character set that they
represent, then converted to the execution character set, just like
unescaped characters.
In identifiers, characters outside the ASCII range can only be
-specified with the '\u' and '\U' escapes, not used directly. If strict
-ISO C90 conformance is specified with an option such as '-std=c90', or
-'-fno-extended-identifiers' is used, then those escapes are not
+specified with the `\u' and `\U' escapes, not used directly. If strict
+ISO C90 conformance is specified with an option such as `-std=c90', or
+`-fno-extended-identifiers' is used, then those escapes are not
permitted in identifiers.
---------- Footnotes ----------
(1) UTF-16 does not meet the requirements of the C standard for a
-wide character set, but the choice of 16-bit 'wchar_t' is enshrined in
+wide character set, but the choice of 16-bit `wchar_t' is enshrined in
some system ABIs so we cannot fix this.

@@ -279,35 +281,35 @@ standard.
1. The input file is read into memory and broken into lines.
Different systems use different conventions to indicate the end of
- a line. GCC accepts the ASCII control sequences 'LF', 'CR LF' and
- 'CR' as end-of-line markers. These are the canonical sequences
+ a line. GCC accepts the ASCII control sequences `LF', `CR LF' and
+ `CR' as end-of-line markers. These are the canonical sequences
used by Unix, DOS and VMS, and the classic Mac OS (before OSX)
- respectively. You may therefore safely copy source code written on
- any of those systems to a different one and use it without
+ respectively. You may therefore safely copy source code written
+ on any of those systems to a different one and use it without
conversion. (GCC may lose track of the current line number if a
file doesn't consistently use one convention, as sometimes happens
when it is edited on computers with different conventions that
share a network file system.)
- If the last line of any input file lacks an end-of-line marker, the
- end of the file is considered to implicitly supply one. The C
+ If the last line of any input file lacks an end-of-line marker,
+ the end of the file is considered to implicitly supply one. The C
standard says that this condition provokes undefined behavior, so
GCC will emit a warning message.
2. If trigraphs are enabled, they are replaced by their corresponding
single characters. By default GCC ignores trigraphs, but if you
- request a strictly conforming mode with the '-std' option, or you
- specify the '-trigraphs' option, then it converts them.
+ request a strictly conforming mode with the `-std' option, or you
+ specify the `-trigraphs' option, then it converts them.
- These are nine three-character sequences, all starting with '??',
+ These are nine three-character sequences, all starting with `??',
that are defined by ISO C to stand for single characters. They
- permit obsolete systems that lack some of C's punctuation to use C.
- For example, '??/' stands for '\', so '??/n' is a character
+ permit obsolete systems that lack some of C's punctuation to use
+ C. For example, `??/' stands for `\', so '??/n' is a character
constant for a newline.
Trigraphs are not popular and many compilers implement them
incorrectly. Portable code should not rely on trigraphs being
- either converted or ignored. With '-Wtrigraphs' GCC will warn you
+ either converted or ignored. With `-Wtrigraphs' GCC will warn you
when a trigraph may change the meaning of your program if it were
converted. *Note Wtrigraphs::.
@@ -315,8 +317,8 @@ standard.
from being confused with a trigraph by inserting a backslash
between the question marks, or by separating the string literal at
the trigraph and making use of string literal concatenation.
- "(??\?)" is the string '(???)', not '(?]'. Traditional C compilers
- do not recognize these idioms.
+ "(??\?)" is the string `(???)', not `(?]'. Traditional C
+ compilers do not recognize these idioms.
The nine trigraphs and their replacements are
@@ -325,7 +327,7 @@ standard.
3. Continued lines are merged into one long line.
- A continued line is a line which ends with a backslash, '\'. The
+ A continued line is a line which ends with a backslash, `\'. The
backslash is removed and the following line is joined with the
current one. No space is inserted, so you may split a line
anywhere, even in the middle of a word. (It is generally more
@@ -336,17 +338,17 @@ standard.
If there is white space between a backslash and the end of a line,
that is still a continued line. However, as this is usually the
- result of an editing mistake, and many compilers will not accept it
- as a continued line, GCC will warn you about it.
+ result of an editing mistake, and many compilers will not accept
+ it as a continued line, GCC will warn you about it.
4. All comments are replaced with single spaces.
- There are two kinds of comments. "Block comments" begin with '/*'
- and continue until the next '*/'. Block comments do not nest:
+ There are two kinds of comments. "Block comments" begin with `/*'
+ and continue until the next `*/'. Block comments do not nest:
/* this is /* one comment */ text outside comment
- "Line comments" begin with '//' and continue to the end of the
+ "Line comments" begin with `//' and continue to the end of the
current line. Line comments do not nest either, but it does not
matter, because they would end in the same place anyway.
@@ -369,7 +371,7 @@ comment.
oops! this isn't a comment anymore */
Comments are not recognized within string literals. "/* blah */" is
-the string constant '/* blah */', not an empty string.
+the string constant `/* blah */', not an empty string.
Line comments are not in the 1989 edition of the C standard, but they
are recognized by GCC as an extension. In C++ and in the 1999 edition
@@ -378,8 +380,8 @@ of the C standard, they are an official part of the language.
Since these transformations happen before all other processing, you
can split a line mechanically with backslash-newline anywhere. You can
comment out the end of a line. You can continue a line comment onto the
-next line with backslash-newline. You can even split '/*', '*/', and
-'//' onto multiple lines with backslash-newline. For example:
+next line with backslash-newline. You can even split `/*', `*/', and
+`//' onto multiple lines with backslash-newline. For example:
/\
*
@@ -389,7 +391,7 @@ next line with backslash-newline. You can even split '/*', '*/', and
O 10\
20
-is equivalent to '#define FOO 1020'. All these tricks are extremely
+is equivalent to `#define FOO 1020'. All these tricks are extremely
confusing and should not be used in code intended to be readable.
There is no way to prevent a backslash at the end of a line from
@@ -410,14 +412,15 @@ token of any kind. Tokens do not have to be separated by white space,
but it is often necessary to avoid ambiguities.
When faced with a sequence of characters that has more than one
-possible tokenization, the preprocessor is greedy. It always makes each
-token, starting from the left, as big as possible before moving on to
-the next token. For instance, 'a+++++b' is interpreted as
-'a ++ ++ + b', not as 'a ++ + ++ b', even though the latter tokenization
-could be part of a valid C program and the former could not.
+possible tokenization, the preprocessor is greedy. It always makes
+each token, starting from the left, as big as possible before moving on
+to the next token. For instance, `a+++++b' is interpreted as
+`a ++ ++ + b', not as `a ++ + ++ b', even though the latter
+tokenization could be part of a valid C program and the former could
+not.
Once the input file is broken into tokens, the token boundaries never
-change, except when the '##' preprocessing operator is used to paste
+change, except when the `##' preprocessing operator is used to paste
tokens together. *Note Concatenation::. For example,
#define foo() bar
@@ -431,12 +434,12 @@ preprocessing token becomes one compiler token.
Preprocessing tokens fall into five broad classes: identifiers,
preprocessing numbers, string literals, punctuators, and other. An
-"identifier" is the same as an identifier in C: any sequence of letters,
-digits, or underscores, which begins with a letter or underscore.
-Keywords of C have no significance to the preprocessor; they are
-ordinary identifiers. You can define a macro whose name is a keyword,
-for instance. The only identifier which can be considered a
-preprocessing keyword is 'defined'. *Note Defined::.
+"identifier" is the same as an identifier in C: any sequence of
+letters, digits, or underscores, which begins with a letter or
+underscore. Keywords of C have no significance to the preprocessor;
+they are ordinary identifiers. You can define a macro whose name is a
+keyword, for instance. The only identifier which can be considered a
+preprocessing keyword is `defined'. *Note Defined::.
This is mostly true of other languages which use the C preprocessor.
However, a few of the keywords of C++ are significant even in the
@@ -446,13 +449,13 @@ preprocessor. *Note C++ Named Operators::.
part of the "basic source character set", at the implementation's
discretion (such as accented Latin letters, Greek letters, or Chinese
ideograms). This may be done with an extended character set, or the
-'\u' and '\U' escape sequences. GCC only accepts such characters in the
-'\u' and '\U' forms.
+`\u' and `\U' escape sequences. GCC only accepts such characters in
+the `\u' and `\U' forms.
- As an extension, GCC treats '$' as a letter. This is for
-compatibility with some systems, such as VMS, where '$' is commonly used
-in system-defined function and object names. '$' is not a letter in
-strictly conforming mode, or if you specify the '-$' option. *Note
+ As an extension, GCC treats `$' as a letter. This is for
+compatibility with some systems, such as VMS, where `$' is commonly
+used in system-defined function and object names. `$' is not a letter
+in strictly conforming mode, or if you specify the `-$' option. *Note
Invocation::.
A "preprocessing number" has a rather bizarre definition. The
@@ -461,9 +464,9 @@ one expects of C, but also a number of other things one might not
initially recognize as a number. Formally, preprocessing numbers begin
with an optional period, a required decimal digit, and then continue
with any sequence of letters, digits, underscores, periods, and
-exponents. Exponents are the two-character sequences 'e+', 'e-', 'E+',
-'E-', 'p+', 'p-', 'P+', and 'P-'. (The exponents that begin with 'p' or
-'P' are new to C99. They are used for hexadecimal floating-point
+exponents. Exponents are the two-character sequences `e+', `e-', `E+',
+`E-', `p+', `p-', `P+', and `P-'. (The exponents that begin with `p'
+or `P' are new to C99. They are used for hexadecimal floating-point
constants.)
The purpose of this unusual definition is to isolate the preprocessor
@@ -471,22 +474,22 @@ from the full complexity of numeric constants. It does not have to
distinguish between lexically valid and invalid floating-point numbers,
which is complicated. The definition also permits you to split an
identifier at any position and get exactly two tokens, which can then be
-pasted back together with the '##' operator.
+pasted back together with the `##' operator.
It's possible for preprocessing numbers to cause programs to be
-misinterpreted. For example, '0xE+12' is a preprocessing number which
+misinterpreted. For example, `0xE+12' is a preprocessing number which
does not translate to any valid numeric constant, therefore a syntax
-error. It does not mean '0xE + 12', which is what you might have
+error. It does not mean `0xE + 12', which is what you might have
intended.
"String literals" are string constants, character constants, and
-header file names (the argument of '#include').(1) String constants and
-character constants are straightforward: "..." or '...'. In either case
-embedded quotes should be escaped with a backslash: '\'' is the
-character constant for '''. There is no limit on the length of a
+header file names (the argument of `#include').(1) String constants
+and character constants are straightforward: "..." or '...'. In either
+case embedded quotes should be escaped with a backslash: '\'' is the
+character constant for `''. There is no limit on the length of a
character constant, but the value of a character constant that contains
-more than one character is implementation-defined. *Note Implementation
-Details::.
+more than one character is implementation-defined. *Note
+Implementation Details::.
Header file names either look like string constants, "...", or are
written with angle brackets instead, <...>. In either case, backslash
@@ -497,19 +500,19 @@ Operation::.
No string literal may extend past the end of a line. Older versions
of GCC accepted multi-line string constants. You may use continued
-lines instead, or string constant concatenation. *Note Differences from
-previous versions::.
+lines instead, or string constant concatenation. *Note Differences
+from previous versions::.
"Punctuators" are all the usual bits of punctuation which are
meaningful to C and C++. All but three of the punctuation characters in
-ASCII are C punctuators. The exceptions are '@', '$', and '`'. In
+ASCII are C punctuators. The exceptions are `@', `$', and ``'. In
addition, all the two- and three-character operators are punctuators.
-There are also six "digraphs", which the C++ standard calls "alternative
-tokens", which are merely alternate ways to spell other punctuators.
-This is a second attempt to work around missing punctuation in obsolete
-systems. It has no negative side effects, unlike trigraphs, but does
-not cover as much ground. The digraphs and their corresponding normal
-punctuators are:
+There are also six "digraphs", which the C++ standard calls
+"alternative tokens", which are merely alternate ways to spell other
+punctuators. This is a second attempt to work around missing
+punctuation in obsolete systems. It has no negative side effects,
+unlike trigraphs, but does not cover as much ground. The digraphs and
+their corresponding normal punctuators are:
Digraph: <% %> <: :> %: %:%:
Punctuator: { } [ ] # ##
@@ -517,11 +520,12 @@ punctuators are:
Any other single character is considered "other". It is passed on to
the preprocessor's output unmolested. The C compiler will almost
certainly reject source code containing "other" tokens. In ASCII, the
-only other characters are '@', '$', '`', and control characters other
-than NUL (all bits zero). (Note that '$' is normally considered a
-letter.) All characters with the high bit set (numeric range 0x7F-0xFF)
-are also "other" in the present implementation. This will change when
-proper support for international character sets is added to GCC.
+only other characters are `@', `$', ``', and control characters other
+than NUL (all bits zero). (Note that `$' is normally considered a
+letter.) All characters with the high bit set (numeric range
+0x7F-0xFF) are also "other" in the present implementation. This will
+change when proper support for international character sets is added to
+GCC.
NUL is a special case because of the high probability that its
appearance is accidental, and because it may be invisible to the user
@@ -533,9 +537,9 @@ have the same meaning.
#define X^@1
#define X 1
-(where '^@' is ASCII NUL). Within string or character constants, NULs
-are preserved. In the latter two cases the preprocessor emits a warning
-message.
+(where `^@' is ASCII NUL). Within string or character constants, NULs
+are preserved. In the latter two cases the preprocessor emits a
+warning message.
---------- Footnotes ----------
@@ -569,8 +573,8 @@ and "macros" to be expanded. Its primary capabilities are:
program according to various conditions.
* Line control. If you use a program to combine or rearrange source
- files into an intermediate file which is then compiled, you can use
- line control to inform the compiler where each source line
+ files into an intermediate file which is then compiled, you can
+ use line control to inform the compiler where each source line
originally came from.
* Diagnostics. You can detect problems at compile time and issue
@@ -579,16 +583,16 @@ and "macros" to be expanded. Its primary capabilities are:
There are a few more, less useful, features.
Except for expansion of predefined macros, all these operations are
-triggered with "preprocessing directives". Preprocessing directives are
-lines in your program that start with '#'. Whitespace is allowed before
-and after the '#'. The '#' is followed by an identifier, the "directive
-name". It specifies the operation to perform. Directives are commonly
-referred to as '#NAME' where NAME is the directive name. For example,
-'#define' is the directive that defines a macro.
-
- The '#' which begins a directive cannot come from a macro expansion.
-Also, the directive name is not macro expanded. Thus, if 'foo' is
-defined as a macro expanding to 'define', that does not make '#foo' a
+triggered with "preprocessing directives". Preprocessing directives
+are lines in your program that start with `#'. Whitespace is allowed
+before and after the `#'. The `#' is followed by an identifier, the
+"directive name". It specifies the operation to perform. Directives
+are commonly referred to as `#NAME' where NAME is the directive name.
+For example, `#define' is the directive that defines a macro.
+
+ The `#' which begins a directive cannot come from a macro expansion.
+Also, the directive name is not macro expanded. Thus, if `foo' is
+defined as a macro expanding to `define', that does not make `#foo' a
valid preprocessing directive.
The set of valid directive names is fixed. Programs cannot define
@@ -596,8 +600,8 @@ new preprocessing directives.
Some directives require arguments; these make up the rest of the
directive line and must be separated from the directive name by
-whitespace. For example, '#define' must be followed by a macro name and
-the intended expansion of the macro.
+whitespace. For example, `#define' must be followed by a macro name
+and the intended expansion of the macro.
A preprocessing directive cannot cover more than one line. The line
may, however, be continued with backslash-newline, or by a block comment
@@ -614,7 +618,7 @@ File: cpp.info, Node: Header Files, Next: Macros, Prev: Overview, Up: Top
A header file is a file containing C declarations and macro definitions
(*note Macros::) to be shared between several source files. You request
the use of a header file in your program by "including" it, with the C
-preprocessing directive '#include'.
+preprocessing directive `#include'.
Header files serve two purposes.
@@ -625,8 +629,8 @@ preprocessing directive '#include'.
* Your own header files contain declarations for interfaces between
the source files of your program. Each time you have a group of
- related declarations and macro definitions all or most of which are
- needed in several different source files, it is a good idea to
+ related declarations and macro definitions all or most of which
+ are needed in several different source files, it is a good idea to
create a header file for them.
Including a header file produces the same results as copying the
@@ -640,7 +644,7 @@ as the risk that a failure to find one copy will result in
inconsistencies within a program.
In C, the usual convention is to give header files names that end
-with '.h'. It is most portable to use only letters, digits, dashes, and
+with `.h'. It is most portable to use only letters, digits, dashes, and
underscores in header file names, and at most one dot.
* Menu:
@@ -661,33 +665,33 @@ File: cpp.info, Node: Include Syntax, Next: Include Operation, Up: Header Fil
==================
Both user and system header files are included using the preprocessing
-directive '#include'. It has two variants:
+directive `#include'. It has two variants:
-'#include <FILE>'
+`#include <FILE>'
This variant is used for system header files. It searches for a
file named FILE in a standard list of system directories. You can
- prepend directories to this list with the '-I' option (*note
+ prepend directories to this list with the `-I' option (*note
Invocation::).
-'#include "FILE"'
+`#include "FILE"'
This variant is used for header files of your own program. It
searches for a file named FILE first in the directory containing
the current file, then in the quote directories and then the same
- directories used for '<FILE>'. You can prepend directories to the
- list of quote directories with the '-iquote' option.
+ directories used for `<FILE>'. You can prepend directories to the
+ list of quote directories with the `-iquote' option.
- The argument of '#include', whether delimited with quote marks or
+ The argument of `#include', whether delimited with quote marks or
angle brackets, behaves like a string constant in that comments are not
-recognized, and macro names are not expanded. Thus, '#include <x/*y>'
-specifies inclusion of a system header file named 'x/*y'.
+recognized, and macro names are not expanded. Thus, `#include <x/*y>'
+specifies inclusion of a system header file named `x/*y'.
However, if backslashes occur within FILE, they are considered
ordinary text characters, not escape characters. None of the character
escape sequences appropriate to string constants in C are processed.
-Thus, '#include "x\n\\y"' specifies a filename containing three
-backslashes. (Some systems interpret '\' as a pathname separator. All
-of these also interpret '/' the same way. It is most portable to use
-only '/'.)
+Thus, `#include "x\n\\y"' specifies a filename containing three
+backslashes. (Some systems interpret `\' as a pathname separator. All
+of these also interpret `/' the same way. It is most portable to use
+only `/'.)
It is an error if there is anything (other than comments) on the line
after the file name.
@@ -698,17 +702,17 @@ File: cpp.info, Node: Include Operation, Next: Search Path, Prev: Include Syn
2.2 Include Operation
=====================
-The '#include' directive works by directing the C preprocessor to scan
+The `#include' directive works by directing the C preprocessor to scan
the specified file as input before continuing with the rest of the
current file. The output from the preprocessor contains the output
already generated, followed by the output resulting from the included
file, followed by the output that comes from the text after the
-'#include' directive. For example, if you have a header file 'header.h'
-as follows,
+`#include' directive. For example, if you have a header file
+`header.h' as follows,
char *test (void);
-and a main program called 'program.c' that uses the header file, like
+and a main program called `program.c' that uses the header file, like
this,
int x;
@@ -720,7 +724,7 @@ this,
puts (test ());
}
-the compiler will see the same token stream as it would if 'program.c'
+the compiler will see the same token stream as it would if `program.c'
read
int x;
@@ -746,7 +750,7 @@ the file.
syntactic units--function declarations or definitions, type
declarations, etc.
- The line following the '#include' directive is always treated as a
+ The line following the `#include' directive is always treated as a
separate line by the C preprocessor, even if the included file lacks a
final newline.
@@ -758,7 +762,7 @@ File: cpp.info, Node: Search Path, Next: Once-Only Headers, Prev: Include Ope
GCC looks in several different places for headers. On a normal Unix
system, if you do not instruct it otherwise, it will look for headers
-requested with '#include <FILE>' in:
+requested with `#include <FILE>' in:
/usr/local/include
LIBDIR/gcc/TARGET/VERSION/include
@@ -766,14 +770,14 @@ requested with '#include <FILE>' in:
/usr/include
For C++ programs, it will also look in
-'LIBDIR/../include/c++/VERSION', first. In the above, TARGET is the
+`LIBDIR/../include/c++/VERSION', first. In the above, TARGET is the
canonical name of the system GCC was configured to compile code for;
often but not always the same as the canonical name of the system it
runs on. VERSION is the version of GCC in use.
- You can add to this list with the '-IDIR' command-line option. All
-the directories named by '-I' are searched, in left-to-right order,
-_before_ the default directories. The only exception is when 'dir' is
+ You can add to this list with the `-IDIR' command-line option. All
+the directories named by `-I' are searched, in left-to-right order,
+_before_ the default directories. The only exception is when `dir' is
already searched by default. In this case, the option is ignored and
the search order for system directories remains unchanged.
@@ -783,38 +787,38 @@ Thus, it is possible for a directory to occur twice in the final search
chain if it was specified in both the quote and bracket chains.
You can prevent GCC from searching any of the default directories
-with the '-nostdinc' option. This is useful when you are compiling an
+with the `-nostdinc' option. This is useful when you are compiling an
operating system kernel or some other program that does not use the
-standard C library facilities, or the standard C library itself. '-I'
-options are not ignored as described above when '-nostdinc' is in
+standard C library facilities, or the standard C library itself. `-I'
+options are not ignored as described above when `-nostdinc' is in
effect.
- GCC looks for headers requested with '#include "FILE"' first in the
+ GCC looks for headers requested with `#include "FILE"' first in the
directory containing the current file, then in the directories as
-specified by '-iquote' options, then in the same places it would have
+specified by `-iquote' options, then in the same places it would have
looked for a header requested with angle brackets. For example, if
-'/usr/include/sys/stat.h' contains '#include "types.h"', GCC looks for
-'types.h' first in '/usr/include/sys', then in its usual search path.
+`/usr/include/sys/stat.h' contains `#include "types.h"', GCC looks for
+`types.h' first in `/usr/include/sys', then in its usual search path.
- '#line' (*note Line Control::) does not change GCC's idea of the
+ `#line' (*note Line Control::) does not change GCC's idea of the
directory containing the current file.
- You may put '-I-' at any point in your list of '-I' options. This
-has two effects. First, directories appearing before the '-I-' in the
+ You may put `-I-' at any point in your list of `-I' options. This
+has two effects. First, directories appearing before the `-I-' in the
list are searched only for headers requested with quote marks.
-Directories after '-I-' are searched for all headers. Second, the
+Directories after `-I-' are searched for all headers. Second, the
directory containing the current file is not searched for anything,
-unless it happens to be one of the directories named by an '-I' switch.
-'-I-' is deprecated, '-iquote' should be used instead.
+unless it happens to be one of the directories named by an `-I' switch.
+`-I-' is deprecated, `-iquote' should be used instead.
- '-I. -I-' is not the same as no '-I' options at all, and does not
-cause the same behavior for '<>' includes that '""' includes get with no
-special options. '-I.' searches the compiler's current working
+ `-I. -I-' is not the same as no `-I' options at all, and does not
+cause the same behavior for `<>' includes that `""' includes get with
+no special options. `-I.' searches the compiler's current working
directory for header files. That may or may not be the same as the
directory containing the current file.
- If you need to look for headers in a directory named '-', write
-'-I./-'.
+ If you need to look for headers in a directory named `-', write
+`-I./-'.
There are several more ways to adjust the header search path. They
are generally less useful. *Note Invocation::.
@@ -843,20 +847,20 @@ contents of the file in a conditional, like this:
This construct is commonly known as a "wrapper #ifndef". When the
header is included again, the conditional will be false, because
-'FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire
+`FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire
contents of the file, and the compiler will not see it twice.
CPP optimizes even further. It remembers when a header file has a
-wrapper '#ifndef'. If a subsequent '#include' specifies that header,
-and the macro in the '#ifndef' is still defined, it does not bother to
+wrapper `#ifndef'. If a subsequent `#include' specifies that header,
+and the macro in the `#ifndef' is still defined, it does not bother to
rescan the file at all.
You can put comments outside the wrapper. They will not interfere
with this optimization.
- The macro 'FILE_FOO_SEEN' is called the "controlling macro" or "guard
-macro". In a user header file, the macro name should not begin with
-'_'. In a system header file, it should begin with '__' to avoid
+ The macro `FILE_FOO_SEEN' is called the "controlling macro" or
+"guard macro". In a user header file, the macro name should not begin
+with `_'. In a system header file, it should begin with `__' to avoid
conflicts with user programs. In any kind of header file, the macro
name should contain the name of the file and some additional text, to
avoid conflicts with other header files.
@@ -868,35 +872,35 @@ File: cpp.info, Node: Alternatives to Wrapper #ifndef, Next: Computed Includes
===================================
CPP supports two more ways of indicating that a header file should be
-read only once. Neither one is as portable as a wrapper '#ifndef' and
+read only once. Neither one is as portable as a wrapper `#ifndef' and
we recommend you do not use them in new programs, with the caveat that
-'#import' is standard practice in Objective-C.
+`#import' is standard practice in Objective-C.
- CPP supports a variant of '#include' called '#import' which includes
-a file, but does so at most once. If you use '#import' instead of
-'#include', then you don't need the conditionals inside the header file
-to prevent multiple inclusion of the contents. '#import' is standard in
-Objective-C, but is considered a deprecated extension in C and C++.
+ CPP supports a variant of `#include' called `#import' which includes
+a file, but does so at most once. If you use `#import' instead of
+`#include', then you don't need the conditionals inside the header file
+to prevent multiple inclusion of the contents. `#import' is standard
+in Objective-C, but is considered a deprecated extension in C and C++.
- '#import' is not a well designed feature. It requires the users of a
-header file to know that it should only be included once. It is much
+ `#import' is not a well designed feature. It requires the users of
+a header file to know that it should only be included once. It is much
better for the header file's implementor to write the file so that users
-don't need to know this. Using a wrapper '#ifndef' accomplishes this
+don't need to know this. Using a wrapper `#ifndef' accomplishes this
goal.
- In the present implementation, a single use of '#import' will prevent
-the file from ever being read again, by either '#import' or '#include'.
-You should not rely on this; do not use both '#import' and '#include' to
-refer to the same header file.
+ In the present implementation, a single use of `#import' will
+prevent the file from ever being read again, by either `#import' or
+`#include'. You should not rely on this; do not use both `#import' and
+`#include' to refer to the same header file.
Another way to prevent a header file from being included more than
-once is with the '#pragma once' directive. If '#pragma once' is seen
+once is with the `#pragma once' directive. If `#pragma once' is seen
when scanning a header file, that file will never be read again, no
matter what.
- '#pragma once' does not have the problems that '#import' does, but it
-is not recognized by all preprocessors, so you cannot rely on it in a
-portable program.
+ `#pragma once' does not have the problems that `#import' does, but
+it is not recognized by all preprocessors, so you cannot rely on it in
+a portable program.

File: cpp.info, Node: Computed Includes, Next: Wrapper Headers, Prev: Alternatives to Wrapper #ifndef, Up: Header Files
@@ -920,27 +924,27 @@ systems, for instance. You could do this with a series of conditionals,
That rapidly becomes tedious. Instead, the preprocessor offers the
ability to use a macro for the header name. This is called a "computed
include". Instead of writing a header name as the direct argument of
-'#include', you simply put a macro name there instead:
+`#include', you simply put a macro name there instead:
#define SYSTEM_H "system_1.h"
...
#include SYSTEM_H
-'SYSTEM_H' will be expanded, and the preprocessor will look for
-'system_1.h' as if the '#include' had been written that way originally.
-'SYSTEM_H' could be defined by your Makefile with a '-D' option.
+`SYSTEM_H' will be expanded, and the preprocessor will look for
+`system_1.h' as if the `#include' had been written that way originally.
+`SYSTEM_H' could be defined by your Makefile with a `-D' option.
- You must be careful when you define the macro. '#define' saves
+ You must be careful when you define the macro. `#define' saves
tokens, not text. The preprocessor has no way of knowing that the macro
-will be used as the argument of '#include', so it generates ordinary
+will be used as the argument of `#include', so it generates ordinary
tokens, not a header name. This is unlikely to cause problems if you
use double-quote includes, which are close enough to string constants.
If you use angle brackets, however, you may have trouble.
The syntax of a computed include is actually a bit more general than
-the above. If the first non-whitespace character after '#include' is
-not '"' or '<', then the entire line is macro-expanded like running text
-would be.
+the above. If the first non-whitespace character after `#include' is
+not `"' or `<', then the entire line is macro-expanded like running
+text would be.
If the line expands to a single string constant, the contents of that
string constant are the file to be included. CPP does not re-examine
@@ -950,20 +954,20 @@ escapes in the string. Therefore
#define HEADER "a\"b"
#include HEADER
-looks for a file named 'a\"b'. CPP searches for the file according to
+looks for a file named `a\"b'. CPP searches for the file according to
the rules for double-quoted includes.
- If the line expands to a token stream beginning with a '<' token and
-including a '>' token, then the tokens between the '<' and the first '>'
-are combined to form the filename to be included. Any whitespace
+ If the line expands to a token stream beginning with a `<' token and
+including a `>' token, then the tokens between the `<' and the first
+`>' are combined to form the filename to be included. Any whitespace
between tokens is reduced to a single space; then any space after the
-initial '<' is retained, but a trailing space before the closing '>' is
+initial `<' is retained, but a trailing space before the closing `>' is
ignored. CPP searches for the file according to the rules for
angle-bracket includes.
In either case, if there are any tokens on the line after the file
-name, an error occurs and the directive is not processed. It is also an
-error if the result of expansion does not match either of the two
+name, an error occurs and the directive is not processed. It is also
+an error if the result of expansion does not match either of the two
expected forms.
These rules are implementation-defined behavior according to the C
@@ -979,48 +983,48 @@ File: cpp.info, Node: Wrapper Headers, Next: System Headers, Prev: Computed I
===================
Sometimes it is necessary to adjust the contents of a system-provided
-header file without editing it directly. GCC's 'fixincludes' operation
+header file without editing it directly. GCC's `fixincludes' operation
does this, for example. One way to do that would be to create a new
header file with the same name and insert it in the search path before
the original header. That works fine as long as you're willing to
replace the old header entirely. But what if you want to refer to the
old header from the new one?
- You cannot simply include the old header with '#include'. That will
+ You cannot simply include the old header with `#include'. That will
start from the beginning, and find your new header again. If your
header is not protected from multiple inclusion (*note Once-Only
Headers::), it will recurse infinitely and cause a fatal error.
You could include the old header with an absolute pathname:
#include "/usr/include/old-header.h"
-This works, but is not clean; should the system headers ever move, you
-would have to edit the new headers to match.
+ This works, but is not clean; should the system headers ever move,
+you would have to edit the new headers to match.
There is no way to solve this problem within the C standard, but you
-can use the GNU extension '#include_next'. It means, "Include the
-_next_ file with this name". This directive works like '#include'
-except in searching for the specified file: it starts searching the list
-of header file directories _after_ the directory in which the current
+can use the GNU extension `#include_next'. It means, "Include the
+_next_ file with this name". This directive works like `#include'
+except in searching for the specified file: it starts searching the
+list of header file directories _after_ the directory in which the
+current file was found.
+
+ Suppose you specify `-I /usr/local/include', and the list of
+directories to search also includes `/usr/include'; and suppose both
+directories contain `signal.h'. Ordinary `#include <signal.h>' finds
+the file under `/usr/local/include'. If that file contains
+`#include_next <signal.h>', it starts searching after that directory,
+and finds the file in `/usr/include'.
+
+ `#include_next' does not distinguish between `<FILE>' and `"FILE"'
+inclusion, nor does it check that the file you specify has the same
+name as the current file. It simply looks for the file named, starting
+with the directory in the search path after the one where the current
file was found.
- Suppose you specify '-I /usr/local/include', and the list of
-directories to search also includes '/usr/include'; and suppose both
-directories contain 'signal.h'. Ordinary '#include <signal.h>' finds
-the file under '/usr/local/include'. If that file contains
-'#include_next <signal.h>', it starts searching after that directory,
-and finds the file in '/usr/include'.
-
- '#include_next' does not distinguish between '<FILE>' and '"FILE"'
-inclusion, nor does it check that the file you specify has the same name
-as the current file. It simply looks for the file named, starting with
-the directory in the search path after the one where the current file
-was found.
-
- The use of '#include_next' can lead to great confusion. We recommend
-it be used only when there is no other alternative. In particular, it
-should not be used in the headers belonging to a specific program; it
-should be used only to make global corrections along the lines of
-'fixincludes'.
+ The use of `#include_next' can lead to great confusion. We
+recommend it be used only when there is no other alternative. In
+particular, it should not be used in the headers belonging to a specific
+program; it should be used only to make global corrections along the
+lines of `fixincludes'.

File: cpp.info, Node: System Headers, Prev: Wrapper Headers, Up: Header Files
@@ -1031,38 +1035,38 @@ File: cpp.info, Node: System Headers, Prev: Wrapper Headers, Up: Header Files
The header files declaring interfaces to the operating system and
runtime libraries often cannot be written in strictly conforming C.
Therefore, GCC gives code found in "system headers" special treatment.
-All warnings, other than those generated by '#warning' (*note
+All warnings, other than those generated by `#warning' (*note
Diagnostics::), are suppressed while GCC is processing a system header.
Macros defined in a system header are immune to a few warnings wherever
-they are expanded. This immunity is granted on an ad-hoc basis, when we
-find that a warning generates lots of false positives because of code in
-macros defined in system headers.
+they are expanded. This immunity is granted on an ad-hoc basis, when
+we find that a warning generates lots of false positives because of
+code in macros defined in system headers.
Normally, only the headers found in specific directories are
-considered system headers. These directories are determined when GCC is
-compiled. There are, however, two ways to make normal headers into
+considered system headers. These directories are determined when GCC
+is compiled. There are, however, two ways to make normal headers into
system headers.
- The '-isystem' command-line option adds its argument to the list of
-directories to search for headers, just like '-I'. Any headers found in
-that directory will be considered system headers.
+ The `-isystem' command-line option adds its argument to the list of
+directories to search for headers, just like `-I'. Any headers found
+in that directory will be considered system headers.
- All directories named by '-isystem' are searched _after_ all
-directories named by '-I', no matter what their order was on the command
-line. If the same directory is named by both '-I' and '-isystem', the
-'-I' option is ignored. GCC provides an informative message when this
-occurs if '-v' is used.
+ All directories named by `-isystem' are searched _after_ all
+directories named by `-I', no matter what their order was on the
+command line. If the same directory is named by both `-I' and
+`-isystem', the `-I' option is ignored. GCC provides an informative
+message when this occurs if `-v' is used.
- There is also a directive, '#pragma GCC system_header', which tells
-GCC to consider the rest of the current include file a system header, no
-matter where it was found. Code that comes before the '#pragma' in the
-file will not be affected. '#pragma GCC system_header' has no effect in
-the primary source file.
+ There is also a directive, `#pragma GCC system_header', which tells
+GCC to consider the rest of the current include file a system header,
+no matter where it was found. Code that comes before the `#pragma' in
+the file will not be affected. `#pragma GCC system_header' has no
+effect in the primary source file.
On very old systems, some of the pre-defined system header
directories get even more special treatment. GNU C++ considers code in
-headers found in those directories to be surrounded by an 'extern "C"'
-block. There is no way to request this behavior with a '#pragma', or
+headers found in those directories to be surrounded by an `extern "C"'
+block. There is no way to request this behavior with a `#pragma', or
from the command line.

@@ -1073,17 +1077,17 @@ File: cpp.info, Node: Macros, Next: Conditionals, Prev: Header Files, Up: To
A "macro" is a fragment of code which has been given a name. Whenever
the name is used, it is replaced by the contents of the macro. There
-are two kinds of macros. They differ mostly in what they look like when
-they are used. "Object-like" macros resemble data objects when used,
-"function-like" macros resemble function calls.
+are two kinds of macros. They differ mostly in what they look like
+when they are used. "Object-like" macros resemble data objects when
+used, "function-like" macros resemble function calls.
You may define any valid identifier as a macro, even if it is a C
keyword. The preprocessor does not know anything about keywords. This
-can be useful if you wish to hide a keyword such as 'const' from an
+can be useful if you wish to hide a keyword such as `const' from an
older compiler that does not understand it. However, the preprocessor
-operator 'defined' (*note Defined::) can never be defined as a macro,
-and C++'s named operators (*note C++ Named Operators::) cannot be macros
-when you are compiling C++.
+operator `defined' (*note Defined::) can never be defined as a macro,
+and C++'s named operators (*note C++ Named Operators::) cannot be
+macros when you are compiling C++.
* Menu:
@@ -1109,21 +1113,21 @@ a code fragment. It is called object-like because it looks like a data
object in code that uses it. They are most commonly used to give
symbolic names to numeric constants.
- You create macros with the '#define' directive. '#define' is
+ You create macros with the `#define' directive. `#define' is
followed by the name of the macro and then the token sequence it should
be an abbreviation for, which is variously referred to as the macro's
"body", "expansion" or "replacement list". For example,
#define BUFFER_SIZE 1024
-defines a macro named 'BUFFER_SIZE' as an abbreviation for the token
-'1024'. If somewhere after this '#define' directive there comes a C
+defines a macro named `BUFFER_SIZE' as an abbreviation for the token
+`1024'. If somewhere after this `#define' directive there comes a C
statement of the form
foo = (char *) malloc (BUFFER_SIZE);
then the C preprocessor will recognize and "expand" the macro
-'BUFFER_SIZE'. The C compiler will see the same tokens as it would if
+`BUFFER_SIZE'. The C compiler will see the same tokens as it would if
you had written
foo = (char *) malloc (1024);
@@ -1132,7 +1136,7 @@ you had written
easier to read when it is possible to tell at a glance which names are
macros.
- The macro's body ends at the end of the '#define' line. You may
+ The macro's body ends at the end of the `#define' line. You may
continue the definition onto multiple lines, if necessary, using
backslash-newline. When the macro is expanded, however, it will all
come out on one line. For example,
@@ -1174,18 +1178,18 @@ macros to expand. For example,
==> BUFSIZE
==> 1024
-'TABLESIZE' is expanded first to produce 'BUFSIZE', then that macro is
-expanded to produce the final result, '1024'.
+`TABLESIZE' is expanded first to produce `BUFSIZE', then that macro is
+expanded to produce the final result, `1024'.
- Notice that 'BUFSIZE' was not defined when 'TABLESIZE' was defined.
-The '#define' for 'TABLESIZE' uses exactly the expansion you specify--in
-this case, 'BUFSIZE'--and does not check to see whether it too contains
-macro names. Only when you _use_ 'TABLESIZE' is the result of its
-expansion scanned for more macro names.
+ Notice that `BUFSIZE' was not defined when `TABLESIZE' was defined.
+The `#define' for `TABLESIZE' uses exactly the expansion you
+specify--in this case, `BUFSIZE'--and does not check to see whether it
+too contains macro names. Only when you _use_ `TABLESIZE' is the
+result of its expansion scanned for more macro names.
- This makes a difference if you change the definition of 'BUFSIZE' at
-some point in the source file. 'TABLESIZE', defined as shown, will
-always expand using the definition of 'BUFSIZE' that is currently in
+ This makes a difference if you change the definition of `BUFSIZE' at
+some point in the source file. `TABLESIZE', defined as shown, will
+always expand using the definition of `BUFSIZE' that is currently in
effect:
#define BUFSIZE 1020
@@ -1193,7 +1197,7 @@ effect:
#undef BUFSIZE
#define BUFSIZE 37
-Now 'TABLESIZE' expands (in two stages) to '37'.
+Now `TABLESIZE' expands (in two stages) to `37'.
If the expansion of a macro contains its own name, either directly or
via intermediate macros, it is not expanded again when the expansion is
@@ -1207,8 +1211,8 @@ File: cpp.info, Node: Function-like Macros, Next: Macro Arguments, Prev: Obje
========================
You can also define macros whose use looks like a function call. These
-are called "function-like macros". To define a function-like macro, you
-use the same '#define' directive, but you put a pair of parentheses
+are called "function-like macros". To define a function-like macro,
+you use the same `#define' directive, but you put a pair of parentheses
immediately after the macro name. For example,
#define lang_init() c_init()
@@ -1226,9 +1230,9 @@ same name, and you wish to use the function sometimes.
foo();
funcptr = foo;
- Here the call to 'foo()' will use the macro, but the function pointer
-will get the address of the real function. If the macro were to be
-expanded, it would cause a syntax error.
+ Here the call to `foo()' will use the macro, but the function
+pointer will get the address of the real function. If the macro were to
+be expanded, it would cause a syntax error.
If you put spaces between the macro name and the parentheses in the
macro definition, that does not define a function-like macro, it defines
@@ -1241,7 +1245,7 @@ parentheses.
The first two pairs of parentheses in this expansion come from the
macro. The third is the pair that was originally after the macro
-invocation. Since 'lang_init' is an object-like macro, it does not
+invocation. Since `lang_init' is an object-like macro, it does not
consume those parentheses.

@@ -1250,11 +1254,11 @@ File: cpp.info, Node: Macro Arguments, Next: Stringification, Prev: Function-
3.3 Macro Arguments
===================
-Function-like macros can take "arguments", just like true functions. To
-define a macro that uses arguments, you insert "parameters" between the
-pair of parentheses in the macro definition that make the macro
-function-like. The parameters must be valid C identifiers, separated by
-commas and optionally whitespace.
+Function-like macros can take "arguments", just like true functions.
+To define a macro that uses arguments, you insert "parameters" between
+the pair of parentheses in the macro definition that make the macro
+function-like. The parameters must be valid C identifiers, separated
+by commas and optionally whitespace.
To invoke a macro that takes arguments, you write the name of the
macro followed by a list of "actual arguments" in parentheses, separated
@@ -1286,19 +1290,19 @@ prevent a comma from separating arguments. Thus,
macro (array[x = y, x + 1])
-passes two arguments to 'macro': 'array[x = y' and 'x + 1]'. If you
-want to supply 'array[x = y, x + 1]' as an argument, you can write it as
-'array[(x = y, x + 1)]', which is equivalent C code.
+passes two arguments to `macro': `array[x = y' and `x + 1]'. If you
+want to supply `array[x = y, x + 1]' as an argument, you can write it
+as `array[(x = y, x + 1)]', which is equivalent C code.
All arguments to a macro are completely macro-expanded before they
are substituted into the macro body. After substitution, the complete
text is scanned again for macros to expand, including the arguments.
-This rule may seem strange, but it is carefully designed so you need not
-worry about whether any function call is actually a macro invocation.
-You can run into trouble if you try to be too clever, though. *Note
-Argument Prescan::, for detailed discussion.
+This rule may seem strange, but it is carefully designed so you need
+not worry about whether any function call is actually a macro
+invocation. You can run into trouble if you try to be too clever,
+though. *Note Argument Prescan::, for detailed discussion.
- For example, 'min (min (a, b), c)' is first expanded to
+ For example, `min (min (a, b), c)' is first expanded to
min (((a) < (b) ? (a) : (b)), (c))
@@ -1314,21 +1318,22 @@ and then to
preprocessor (but many macros will then expand to invalid code). You
cannot leave out arguments entirely; if a macro takes two arguments,
there must be exactly one comma at the top level of its argument list.
-Here are some silly examples using 'min':
+Here are some silly examples using `min':
min(, b) ==> (( ) < (b) ? ( ) : (b))
min(a, ) ==> ((a ) < ( ) ? (a ) : ( ))
min(,) ==> (( ) < ( ) ? ( ) : ( ))
min((,),) ==> (((,)) < ( ) ? ((,)) : ( ))
- min() error-> macro "min" requires 2 arguments, but only 1 given
- min(,,) error-> macro "min" passed 3 arguments, but takes just 2
+ min() error--> macro "min" requires 2 arguments, but only 1 given
+ min(,,) error--> macro "min" passed 3 arguments, but takes just 2
- Whitespace is not a preprocessing token, so if a macro 'foo' takes
-one argument, 'foo ()' and 'foo ( )' both supply it an empty argument.
+ Whitespace is not a preprocessing token, so if a macro `foo' takes
+one argument, `foo ()' and `foo ( )' both supply it an empty argument.
Previous GNU preprocessor implementations and documentation were
-incorrect on this point, insisting that a function-like macro that takes
-a single argument be passed a space if an empty argument was required.
+incorrect on this point, insisting that a function-like macro that
+takes a single argument be passed a space if an empty argument was
+required.
Macro parameters appearing inside string literals are not replaced by
their corresponding actual arguments.
@@ -1344,8 +1349,8 @@ File: cpp.info, Node: Stringification, Next: Concatenation, Prev: Macro Argum
Sometimes you may want to convert a macro argument into a string
constant. Parameters are not replaced inside string constants, but you
-can use the '#' preprocessing operator instead. When a macro parameter
-is used with a leading '#', the preprocessor replaces it with the
+can use the `#' preprocessing operator instead. When a macro parameter
+is used with a leading `#', the preprocessor replaces it with the
literal text of the actual argument, converted to a string constant.
Unlike normal parameter replacement, the argument is not macro-expanded
first. This is called "stringification".
@@ -1353,9 +1358,9 @@ first. This is called "stringification".
There is no way to combine an argument with surrounding text and
stringify it all together. Instead, you can write a series of adjacent
string constants and stringified arguments. The preprocessor will
-replace the stringified arguments with string constants. The C compiler
-will then combine all the adjacent string constants into one long
-string.
+replace the stringified arguments with string constants. The C
+compiler will then combine all the adjacent string constants into one
+long string.
Here is an example of a macro definition that uses stringification:
@@ -1367,22 +1372,23 @@ string.
==> do { if (x == 0)
fprintf (stderr, "Warning: " "x == 0" "\n"); } while (0);
-The argument for 'EXP' is substituted once, as-is, into the 'if'
-statement, and once, stringified, into the argument to 'fprintf'. If
-'x' were a macro, it would be expanded in the 'if' statement, but not in
-the string.
+The argument for `EXP' is substituted once, as-is, into the `if'
+statement, and once, stringified, into the argument to `fprintf'. If
+`x' were a macro, it would be expanded in the `if' statement, but not
+in the string.
- The 'do' and 'while (0)' are a kludge to make it possible to write
-'WARN_IF (ARG);', which the resemblance of 'WARN_IF' to a function would
-make C programmers want to do; see *note Swallowing the Semicolon::.
+ The `do' and `while (0)' are a kludge to make it possible to write
+`WARN_IF (ARG);', which the resemblance of `WARN_IF' to a function
+would make C programmers want to do; see *note Swallowing the
+Semicolon::.
Stringification in C involves more than putting double-quote
characters around the fragment. The preprocessor backslash-escapes the
-quotes surrounding embedded string constants, and all backslashes within
-string and character constants, in order to get a valid C string
-constant with the proper contents. Thus, stringifying 'p = "foo\n";'
+quotes surrounding embedded string constants, and all backslashes
+within string and character constants, in order to get a valid C string
+constant with the proper contents. Thus, stringifying `p = "foo\n";'
results in "p = \"foo\\n\";". However, backslashes that are not inside
-string or character constants are not duplicated: '\n' by itself
+string or character constants are not duplicated: `\n' by itself
stringifies to "\n".
All leading and trailing whitespace in text being stringified is
@@ -1407,11 +1413,11 @@ you have to use two levels of macros.
==> str (4)
==> "4"
- 's' is stringified when it is used in 'str', so it is not
-macro-expanded first. But 's' is an ordinary argument to 'xstr', so it
-is completely macro-expanded before 'xstr' itself is expanded (*note
-Argument Prescan::). Therefore, by the time 'str' gets to its argument,
-it has already been macro-expanded.
+ `s' is stringified when it is used in `str', so it is not
+macro-expanded first. But `s' is an ordinary argument to `xstr', so it
+is completely macro-expanded before `xstr' itself is expanded (*note
+Argument Prescan::). Therefore, by the time `str' gets to its
+argument, it has already been macro-expanded.

File: cpp.info, Node: Concatenation, Next: Variadic Macros, Prev: Stringification, Up: Macros
@@ -1420,39 +1426,39 @@ File: cpp.info, Node: Concatenation, Next: Variadic Macros, Prev: Stringifica
=================
It is often useful to merge two tokens into one while expanding macros.
-This is called "token pasting" or "token concatenation". The '##'
+This is called "token pasting" or "token concatenation". The `##'
preprocessing operator performs token pasting. When a macro is
-expanded, the two tokens on either side of each '##' operator are
-combined into a single token, which then replaces the '##' and the two
+expanded, the two tokens on either side of each `##' operator are
+combined into a single token, which then replaces the `##' and the two
original tokens in the macro expansion. Usually both will be
identifiers, or one will be an identifier and the other a preprocessing
number. When pasted, they make a longer identifier. This isn't the
only valid case. It is also possible to concatenate two numbers (or a
-number and a name, such as '1.5' and 'e3') into a number. Also,
-multi-character operators such as '+=' can be formed by token pasting.
+number and a name, such as `1.5' and `e3') into a number. Also,
+multi-character operators such as `+=' can be formed by token pasting.
However, two tokens that don't together form a valid token cannot be
-pasted together. For example, you cannot concatenate 'x' with '+' in
+pasted together. For example, you cannot concatenate `x' with `+' in
either order. If you try, the preprocessor issues a warning and emits
the two tokens. Whether it puts white space between the tokens is
-undefined. It is common to find unnecessary uses of '##' in complex
+undefined. It is common to find unnecessary uses of `##' in complex
macros. If you get this warning, it is likely that you can simply
-remove the '##'.
+remove the `##'.
- Both the tokens combined by '##' could come from the macro body, but
+ Both the tokens combined by `##' could come from the macro body, but
you could just as well write them as one token in the first place.
Token pasting is most useful when one or both of the tokens comes from a
-macro argument. If either of the tokens next to an '##' is a parameter
-name, it is replaced by its actual argument before '##' executes. As
+macro argument. If either of the tokens next to an `##' is a parameter
+name, it is replaced by its actual argument before `##' executes. As
with stringification, the actual argument is not macro-expanded first.
-If the argument is empty, that '##' has no effect.
+If the argument is empty, that `##' has no effect.
Keep in mind that the C preprocessor converts comments to whitespace
before macros are even considered. Therefore, you cannot create a
-comment by concatenating '/' and '*'. You can put as much whitespace
-between '##' and its operands as you like, including comments, and you
-can put comments in arguments that will be concatenated. However, it is
-an error if '##' appears at either end of a macro body.
+comment by concatenating `/' and `*'. You can put as much whitespace
+between `##' and its operands as you like, including comments, and you
+can put comments in arguments that will be concatenated. However, it
+is an error if `##' appears at either end of a macro body.
Consider a C program that interprets named commands. There probably
needs to be a table of commands, perhaps an array of structures declared
@@ -1471,12 +1477,12 @@ as follows:
...
};
- It would be cleaner not to have to give each command name twice, once
-in the string constant and once in the function name. A macro which
-takes the name of a command as an argument can make this unnecessary.
-The string constant can be created with stringification, and the
-function name by concatenating the argument with '_command'. Here is
-how it is done:
+ It would be cleaner not to have to give each command name twice,
+once in the string constant and once in the function name. A macro
+which takes the name of a command as an argument can make this
+unnecessary. The string constant can be created with stringification,
+and the function name by concatenating the argument with `_command'.
+Here is how it is done:
#define COMMAND(NAME) { #NAME, NAME ## _command }
@@ -1502,7 +1508,7 @@ a function. Here is an example:
This kind of macro is called "variadic". When the macro is invoked,
all the tokens in its argument list after the last named argument (this
macro has none), including any commas, become the "variable argument".
-This sequence of tokens replaces the identifier '__VA_ARGS__' in the
+This sequence of tokens replaces the identifier `__VA_ARGS__' in the
macro body wherever it appears. Thus, we have this expansion:
eprintf ("%s:%d: ", input_file, lineno)
@@ -1510,23 +1516,23 @@ macro body wherever it appears. Thus, we have this expansion:
The variable argument is completely macro-expanded before it is
inserted into the macro expansion, just like an ordinary argument. You
-may use the '#' and '##' operators to stringify the variable argument or
-to paste its leading or trailing token with another token. (But see
-below for an important special case for '##'.)
+may use the `#' and `##' operators to stringify the variable argument
+or to paste its leading or trailing token with another token. (But see
+below for an important special case for `##'.)
If your macro is complicated, you may want a more descriptive name
-for the variable argument than '__VA_ARGS__'. CPP permits this, as an
-extension. You may write an argument name immediately before the '...';
-that name is used for the variable argument. The 'eprintf' macro above
-could be written
+for the variable argument than `__VA_ARGS__'. CPP permits this, as an
+extension. You may write an argument name immediately before the
+`...'; that name is used for the variable argument. The `eprintf'
+macro above could be written
#define eprintf(args...) fprintf (stderr, args)
-using this extension. You cannot use '__VA_ARGS__' and this extension
+using this extension. You cannot use `__VA_ARGS__' and this extension
in the same macro.
You can have named arguments as well as variable arguments in a
-variadic macro. We could define 'eprintf' like this, instead:
+variadic macro. We could define `eprintf' like this, instead:
#define eprintf(format, ...) fprintf (stderr, format, __VA_ARGS__)
@@ -1534,8 +1540,8 @@ This formulation looks more descriptive, but unfortunately it is less
flexible: you must now supply at least one argument after the format
string. In standard C, you cannot omit the comma separating the named
argument from the variable arguments. Furthermore, if you leave the
-variable argument empty, you will get a syntax error, because there will
-be an extra comma after the format string.
+variable argument empty, you will get a syntax error, because there
+will be an extra comma after the format string.
eprintf("success!\n", );
==> fprintf(stderr, "success!\n", );
@@ -1546,46 +1552,46 @@ First, you are allowed to leave the variable argument out entirely:
eprintf ("success!\n")
==> fprintf(stderr, "success!\n", );
-Second, the '##' token paste operator has a special meaning when placed
+Second, the `##' token paste operator has a special meaning when placed
between a comma and a variable argument. If you write
#define eprintf(format, ...) fprintf (stderr, format, ##__VA_ARGS__)
-and the variable argument is left out when the 'eprintf' macro is used,
-then the comma before the '##' will be deleted. This does _not_ happen
-if you pass an empty argument, nor does it happen if the token preceding
-'##' is anything other than a comma.
+and the variable argument is left out when the `eprintf' macro is used,
+then the comma before the `##' will be deleted. This does _not_ happen
+if you pass an empty argument, nor does it happen if the token
+preceding `##' is anything other than a comma.
eprintf ("success!\n")
==> fprintf(stderr, "success!\n");
The above explanation is ambiguous about the case where the only macro
-parameter is a variable arguments parameter, as it is meaningless to try
-to distinguish whether no argument at all is an empty argument or a
-missing argument. In this case the C99 standard is clear that the comma
-must remain, however the existing GCC extension used to swallow the
-comma. So CPP retains the comma when conforming to a specific C
+parameter is a variable arguments parameter, as it is meaningless to
+try to distinguish whether no argument at all is an empty argument or a
+missing argument. In this case the C99 standard is clear that the
+comma must remain, however the existing GCC extension used to swallow
+the comma. So CPP retains the comma when conforming to a specific C
standard, and drops it otherwise.
- C99 mandates that the only place the identifier '__VA_ARGS__' can
+ C99 mandates that the only place the identifier `__VA_ARGS__' can
appear is in the replacement list of a variadic macro. It may not be
-used as a macro name, macro argument name, or within a different type of
-macro. It may also be forbidden in open text; the standard is
+used as a macro name, macro argument name, or within a different type
+of macro. It may also be forbidden in open text; the standard is
ambiguous. We recommend you avoid using it except for its defined
purpose.
Variadic macros are a new feature in C99. GNU CPP has supported them
-for a long time, but only with a named variable argument ('args...', not
-'...' and '__VA_ARGS__'). If you are concerned with portability to
+for a long time, but only with a named variable argument (`args...',
+not `...' and `__VA_ARGS__'). If you are concerned with portability to
previous versions of GCC, you should use only named variable arguments.
On the other hand, if you are concerned with portability to other
-conforming implementations of C99, you should use only '__VA_ARGS__'.
+conforming implementations of C99, you should use only `__VA_ARGS__'.
Previous versions of CPP implemented the comma-deletion extension
much more generally. We have restricted it in this release to minimize
the differences from C99. To get the same effect with both this and
-previous versions of GCC, the token preceding the special '##' must be a
-comma, and there must be white space between that comma and whatever
+previous versions of GCC, the token preceding the special `##' must be
+a comma, and there must be white space between that comma and whatever
comes immediately before it:
#define eprintf(format, args...) fprintf (stderr, format , ##args)
@@ -1619,25 +1625,25 @@ File: cpp.info, Node: Standard Predefined Macros, Next: Common Predefined Macr
--------------------------------
The standard predefined macros are specified by the relevant language
-standards, so they are available with all compilers that implement those
-standards. Older compilers may not provide all of them. Their names
-all start with double underscores.
+standards, so they are available with all compilers that implement
+those standards. Older compilers may not provide all of them. Their
+names all start with double underscores.
-'__FILE__'
+`__FILE__'
This macro expands to the name of the current input file, in the
form of a C string constant. This is the path by which the
preprocessor opened the file, not the short name specified in
- '#include' or as the input file name argument. For example,
- '"/usr/local/include/myheader.h"' is a possible expansion of this
+ `#include' or as the input file name argument. For example,
+ `"/usr/local/include/myheader.h"' is a possible expansion of this
macro.
-'__LINE__'
- This macro expands to the current input line number, in the form of
- a decimal integer constant. While we call it a predefined macro,
- it's a pretty strange macro, since its "definition" changes with
- each new line of source code.
+`__LINE__'
+ This macro expands to the current input line number, in the form
+ of a decimal integer constant. While we call it a predefined
+ macro, it's a pretty strange macro, since its "definition" changes
+ with each new line of source code.
- '__FILE__' and '__LINE__' are useful in generating an error message
+ `__FILE__' and `__LINE__' are useful in generating an error message
to report an inconsistency detected by the program; the message can
state the source line at which the inconsistency was detected. For
example,
@@ -1647,101 +1653,103 @@ example,
"%d at %s, line %d.",
length, __FILE__, __LINE__);
- An '#include' directive changes the expansions of '__FILE__' and
-'__LINE__' to correspond to the included file. At the end of that file,
-when processing resumes on the input file that contained the '#include'
-directive, the expansions of '__FILE__' and '__LINE__' revert to the
-values they had before the '#include' (but '__LINE__' is then
-incremented by one as processing moves to the line after the
-'#include').
+ An `#include' directive changes the expansions of `__FILE__' and
+`__LINE__' to correspond to the included file. At the end of that
+file, when processing resumes on the input file that contained the
+`#include' directive, the expansions of `__FILE__' and `__LINE__'
+revert to the values they had before the `#include' (but `__LINE__' is
+then incremented by one as processing moves to the line after the
+`#include').
- A '#line' directive changes '__LINE__', and may change '__FILE__' as
+ A `#line' directive changes `__LINE__', and may change `__FILE__' as
well. *Note Line Control::.
- C99 introduces '__func__', and GCC has provided '__FUNCTION__' for a
-long time. Both of these are strings containing the name of the current
-function (there are slight semantic differences; see the GCC manual).
-Neither of them is a macro; the preprocessor does not know the name of
-the current function. They tend to be useful in conjunction with
-'__FILE__' and '__LINE__', though.
+ C99 introduces `__func__', and GCC has provided `__FUNCTION__' for a
+long time. Both of these are strings containing the name of the
+current function (there are slight semantic differences; see the GCC
+manual). Neither of them is a macro; the preprocessor does not know the
+name of the current function. They tend to be useful in conjunction
+with `__FILE__' and `__LINE__', though.
-'__DATE__'
+`__DATE__'
This macro expands to a string constant that describes the date on
which the preprocessor is being run. The string constant contains
- eleven characters and looks like '"Feb 12 1996"'. If the day of
+ eleven characters and looks like `"Feb 12 1996"'. If the day of
the month is less than 10, it is padded with a space on the left.
If GCC cannot determine the current date, it will emit a warning
- message (once per compilation) and '__DATE__' will expand to
- '"??? ?? ????"'.
+ message (once per compilation) and `__DATE__' will expand to
+ `"??? ?? ????"'.
-'__TIME__'
+`__TIME__'
This macro expands to a string constant that describes the time at
which the preprocessor is being run. The string constant contains
- eight characters and looks like '"23:59:01"'.
+ eight characters and looks like `"23:59:01"'.
If GCC cannot determine the current time, it will emit a warning
- message (once per compilation) and '__TIME__' will expand to
- '"??:??:??"'.
+ message (once per compilation) and `__TIME__' will expand to
+ `"??:??:??"'.
-'__STDC__'
+`__STDC__'
In normal operation, this macro expands to the constant 1, to
signify that this compiler conforms to ISO Standard C. If GNU CPP
is used with a compiler other than GCC, this is not necessarily
true; however, the preprocessor always conforms to the standard
- unless the '-traditional-cpp' option is used.
+ unless the `-traditional-cpp' option is used.
- This macro is not defined if the '-traditional-cpp' option is used.
+ This macro is not defined if the `-traditional-cpp' option is used.
On some hosts, the system compiler uses a different convention,
- where '__STDC__' is normally 0, but is 1 if the user specifies
+ where `__STDC__' is normally 0, but is 1 if the user specifies
strict conformance to the C Standard. CPP follows the host
- convention when processing system header files, but when processing
- user files '__STDC__' is always 1. This has been reported to cause
- problems; for instance, some versions of Solaris provide X Windows
- headers that expect '__STDC__' to be either undefined or 1. *Note
- Invocation::.
+ convention when processing system header files, but when
+ processing user files `__STDC__' is always 1. This has been
+ reported to cause problems; for instance, some versions of Solaris
+ provide X Windows headers that expect `__STDC__' to be either
+ undefined or 1. *Note Invocation::.
-'__STDC_VERSION__'
+`__STDC_VERSION__'
This macro expands to the C Standard's version number, a long
- integer constant of the form 'YYYYMML' where YYYY and MM are the
+ integer constant of the form `YYYYMML' where YYYY and MM are the
year and month of the Standard version. This signifies which
version of the C Standard the compiler conforms to. Like
- '__STDC__', this is not necessarily accurate for the entire
+ `__STDC__', this is not necessarily accurate for the entire
implementation, unless GNU CPP is being used with GCC.
- The value '199409L' signifies the 1989 C standard as amended in
- 1994, which is the current default; the value '199901L' signifies
- the 1999 revision of the C standard. Support for the 1999 revision
- is not yet complete.
+ The value `199409L' signifies the 1989 C standard as amended in
+ 1994, which is the current default; the value `199901L' signifies
+ the 1999 revision of the C standard. Support for the 1999
+ revision is not yet complete.
- This macro is not defined if the '-traditional-cpp' option is used,
- nor when compiling C++ or Objective-C.
+ This macro is not defined if the `-traditional-cpp' option is
+ used, nor when compiling C++ or Objective-C.
-'__STDC_HOSTED__'
+`__STDC_HOSTED__'
This macro is defined, with value 1, if the compiler's target is a
"hosted environment". A hosted environment has the complete
facilities of the standard C library available.
-'__cplusplus'
+`__cplusplus'
This macro is defined when the C++ compiler is in use. You can use
- '__cplusplus' to test whether a header is compiled by a C compiler
- or a C++ compiler. This macro is similar to '__STDC_VERSION__', in
+ `__cplusplus' to test whether a header is compiled by a C compiler
+ or a C++ compiler. This macro is similar to `__STDC_VERSION__', in
that it expands to a version number. Depending on the language
- standard selected, the value of the macro is '199711L', as mandated
- by the 1998 C++ standard; '201103L', per the 2011 C++ standard; an
- unspecified value strictly larger than '201103L' for the
- experimental languages enabled by '-std=c++1y' and '-std=gnu++1y'.
+ standard selected, the value of the macro is `199711L', as
+ mandated by the 1998 C++ standard; `201103L', per the 2011 C++
+ standard; an unspecified value strictly larger than `201103L' for
+ the experimental languages enabled by `-std=c++1y' and
+ `-std=gnu++1y'.
-'__OBJC__'
+`__OBJC__'
This macro is defined, with value 1, when the Objective-C compiler
- is in use. You can use '__OBJC__' to test whether a header is
+ is in use. You can use `__OBJC__' to test whether a header is
compiled by a C compiler or an Objective-C compiler.
-'__ASSEMBLER__'
+`__ASSEMBLER__'
This macro is defined with value 1 when preprocessing assembly
language.
+

File: cpp.info, Node: Common Predefined Macros, Next: System-specific Predefined Macros, Prev: Standard Predefined Macros, Up: Predefined Macros
@@ -1753,42 +1761,42 @@ with the same meanings regardless of the machine or operating system on
which you are using GNU C or GNU Fortran. Their names all start with
double underscores.
-'__COUNTER__'
+`__COUNTER__'
This macro expands to sequential integral values starting from 0.
- In conjunction with the '##' operator, this provides a convenient
- means to generate unique identifiers. Care must be taken to ensure
- that '__COUNTER__' is not expanded prior to inclusion of
+ In conjunction with the `##' operator, this provides a convenient
+ means to generate unique identifiers. Care must be taken to
+ ensure that `__COUNTER__' is not expanded prior to inclusion of
precompiled headers which use it. Otherwise, the precompiled
headers will not be used.
-'__GFORTRAN__'
+`__GFORTRAN__'
The GNU Fortran compiler defines this.
-'__GNUC__'
-'__GNUC_MINOR__'
-'__GNUC_PATCHLEVEL__'
+`__GNUC__'
+`__GNUC_MINOR__'
+`__GNUC_PATCHLEVEL__'
These macros are defined by all GNU compilers that use the C
preprocessor: C, C++, Objective-C and Fortran. Their values are
the major version, minor version, and patch level of the compiler,
as integer constants. For example, GCC 3.2.1 will define
- '__GNUC__' to 3, '__GNUC_MINOR__' to 2, and '__GNUC_PATCHLEVEL__'
- to 1. These macros are also defined if you invoke the preprocessor
- directly.
+ `__GNUC__' to 3, `__GNUC_MINOR__' to 2, and `__GNUC_PATCHLEVEL__'
+ to 1. These macros are also defined if you invoke the
+ preprocessor directly.
- '__GNUC_PATCHLEVEL__' is new to GCC 3.0; it is also present in the
+ `__GNUC_PATCHLEVEL__' is new to GCC 3.0; it is also present in the
widely-used development snapshots leading up to 3.0 (which identify
themselves as GCC 2.96 or 2.97, depending on which snapshot you
have).
If all you need to know is whether or not your program is being
compiled by GCC, or a non-GCC compiler that claims to accept the
- GNU C dialects, you can simply test '__GNUC__'. If you need to
+ GNU C dialects, you can simply test `__GNUC__'. If you need to
write code which depends on a specific version, you must be more
- careful. Each time the minor version is increased, the patch level
- is reset to zero; each time the major version is increased (which
- happens rarely), the minor version and patch level are reset. If
- you wish to use the predefined macros directly in the conditional,
- you will need to write it like this:
+ careful. Each time the minor version is increased, the patch
+ level is reset to zero; each time the major version is increased
+ (which happens rarely), the minor version and patch level are
+ reset. If you wish to use the predefined macros directly in the
+ conditional, you will need to write it like this:
/* Test for GCC > 3.2.0 */
#if __GNUC__ > 3 || \
@@ -1808,48 +1816,48 @@ double underscores.
Many people find this form easier to understand.
-'__GNUG__'
+`__GNUG__'
The GNU C++ compiler defines this. Testing it is equivalent to
- testing '(__GNUC__ && __cplusplus)'.
+ testing `(__GNUC__ && __cplusplus)'.
-'__STRICT_ANSI__'
- GCC defines this macro if and only if the '-ansi' switch, or a
- '-std' switch specifying strict conformance to some version of ISO
- C or ISO C++, was specified when GCC was invoked. It is defined to
- '1'. This macro exists primarily to direct GNU libc's header files
- to restrict their definitions to the minimal set found in the 1989
- C standard.
+`__STRICT_ANSI__'
+ GCC defines this macro if and only if the `-ansi' switch, or a
+ `-std' switch specifying strict conformance to some version of ISO
+ C or ISO C++, was specified when GCC was invoked. It is defined
+ to `1'. This macro exists primarily to direct GNU libc's header
+ files to restrict their definitions to the minimal set found in
+ the 1989 C standard.
-'__BASE_FILE__'
+`__BASE_FILE__'
This macro expands to the name of the main input file, in the form
of a C string constant. This is the source file that was specified
on the command line of the preprocessor or C compiler.
-'__INCLUDE_LEVEL__'
+`__INCLUDE_LEVEL__'
This macro expands to a decimal integer constant that represents
the depth of nesting in include files. The value of this macro is
- incremented on every '#include' directive and decremented at the
+ incremented on every `#include' directive and decremented at the
end of every included file. It starts out at 0, its value within
the base file specified on the command line.
-'__ELF__'
+`__ELF__'
This macro is defined if the target uses the ELF object format.
-'__VERSION__'
- This macro expands to a string constant which describes the version
- of the compiler in use. You should not rely on its contents having
- any particular form, but it can be counted on to contain at least
- the release number.
-
-'__OPTIMIZE__'
-'__OPTIMIZE_SIZE__'
-'__NO_INLINE__'
- These macros describe the compilation mode. '__OPTIMIZE__' is
- defined in all optimizing compilations. '__OPTIMIZE_SIZE__' is
+`__VERSION__'
+ This macro expands to a string constant which describes the
+ version of the compiler in use. You should not rely on its
+ contents having any particular form, but it can be counted on to
+ contain at least the release number.
+
+`__OPTIMIZE__'
+`__OPTIMIZE_SIZE__'
+`__NO_INLINE__'
+ These macros describe the compilation mode. `__OPTIMIZE__' is
+ defined in all optimizing compilations. `__OPTIMIZE_SIZE__' is
defined if the compiler is optimizing for size, not speed.
- '__NO_INLINE__' is defined if no functions will be inlined into
+ `__NO_INLINE__' is defined if no functions will be inlined into
their callers (when not optimizing, or when inlining has been
- specifically disabled by '-fno-inline').
+ specifically disabled by `-fno-inline').
These macros cause certain GNU header files to provide optimized
definitions, using macros or inline functions, of system library
@@ -1857,216 +1865,216 @@ double underscores.
make sure that programs will execute with the same effect whether
or not they are defined. If they are defined, their value is 1.
-'__GNUC_GNU_INLINE__'
- GCC defines this macro if functions declared 'inline' will be
+`__GNUC_GNU_INLINE__'
+ GCC defines this macro if functions declared `inline' will be
handled in GCC's traditional gnu90 mode. Object files will contain
- externally visible definitions of all functions declared 'inline'
- without 'extern' or 'static'. They will not contain any
- definitions of any functions declared 'extern inline'.
+ externally visible definitions of all functions declared `inline'
+ without `extern' or `static'. They will not contain any
+ definitions of any functions declared `extern inline'.
-'__GNUC_STDC_INLINE__'
- GCC defines this macro if functions declared 'inline' will be
+`__GNUC_STDC_INLINE__'
+ GCC defines this macro if functions declared `inline' will be
handled according to the ISO C99 standard. Object files will
contain externally visible definitions of all functions declared
- 'extern inline'. They will not contain definitions of any
- functions declared 'inline' without 'extern'.
+ `extern inline'. They will not contain definitions of any
+ functions declared `inline' without `extern'.
- If this macro is defined, GCC supports the 'gnu_inline' function
+ If this macro is defined, GCC supports the `gnu_inline' function
attribute as a way to always get the gnu90 behavior. Support for
- this and '__GNUC_GNU_INLINE__' was added in GCC 4.1.3. If neither
- macro is defined, an older version of GCC is being used: 'inline'
- functions will be compiled in gnu90 mode, and the 'gnu_inline'
+ this and `__GNUC_GNU_INLINE__' was added in GCC 4.1.3. If neither
+ macro is defined, an older version of GCC is being used: `inline'
+ functions will be compiled in gnu90 mode, and the `gnu_inline'
function attribute will not be recognized.
-'__CHAR_UNSIGNED__'
- GCC defines this macro if and only if the data type 'char' is
+`__CHAR_UNSIGNED__'
+ GCC defines this macro if and only if the data type `char' is
unsigned on the target machine. It exists to cause the standard
- header file 'limits.h' to work correctly. You should not use this
+ header file `limits.h' to work correctly. You should not use this
macro yourself; instead, refer to the standard macros defined in
- 'limits.h'.
+ `limits.h'.
-'__WCHAR_UNSIGNED__'
- Like '__CHAR_UNSIGNED__', this macro is defined if and only if the
- data type 'wchar_t' is unsigned and the front-end is in C++ mode.
+`__WCHAR_UNSIGNED__'
+ Like `__CHAR_UNSIGNED__', this macro is defined if and only if the
+ data type `wchar_t' is unsigned and the front-end is in C++ mode.
-'__REGISTER_PREFIX__'
+`__REGISTER_PREFIX__'
This macro expands to a single token (not a string constant) which
is the prefix applied to CPU register names in assembly language
for this target. You can use it to write assembly that is usable
- in multiple environments. For example, in the 'm68k-aout'
- environment it expands to nothing, but in the 'm68k-coff'
- environment it expands to a single '%'.
+ in multiple environments. For example, in the `m68k-aout'
+ environment it expands to nothing, but in the `m68k-coff'
+ environment it expands to a single `%'.
-'__USER_LABEL_PREFIX__'
+`__USER_LABEL_PREFIX__'
This macro expands to a single token which is the prefix applied to
user labels (symbols visible to C code) in assembly. For example,
- in the 'm68k-aout' environment it expands to an '_', but in the
- 'm68k-coff' environment it expands to nothing.
+ in the `m68k-aout' environment it expands to an `_', but in the
+ `m68k-coff' environment it expands to nothing.
This macro will have the correct definition even if
- '-f(no-)underscores' is in use, but it will not be correct if
+ `-f(no-)underscores' is in use, but it will not be correct if
target-specific options that adjust this prefix are used (e.g. the
- OSF/rose '-mno-underscores' option).
-
-'__SIZE_TYPE__'
-'__PTRDIFF_TYPE__'
-'__WCHAR_TYPE__'
-'__WINT_TYPE__'
-'__INTMAX_TYPE__'
-'__UINTMAX_TYPE__'
-'__SIG_ATOMIC_TYPE__'
-'__INT8_TYPE__'
-'__INT16_TYPE__'
-'__INT32_TYPE__'
-'__INT64_TYPE__'
-'__UINT8_TYPE__'
-'__UINT16_TYPE__'
-'__UINT32_TYPE__'
-'__UINT64_TYPE__'
-'__INT_LEAST8_TYPE__'
-'__INT_LEAST16_TYPE__'
-'__INT_LEAST32_TYPE__'
-'__INT_LEAST64_TYPE__'
-'__UINT_LEAST8_TYPE__'
-'__UINT_LEAST16_TYPE__'
-'__UINT_LEAST32_TYPE__'
-'__UINT_LEAST64_TYPE__'
-'__INT_FAST8_TYPE__'
-'__INT_FAST16_TYPE__'
-'__INT_FAST32_TYPE__'
-'__INT_FAST64_TYPE__'
-'__UINT_FAST8_TYPE__'
-'__UINT_FAST16_TYPE__'
-'__UINT_FAST32_TYPE__'
-'__UINT_FAST64_TYPE__'
-'__INTPTR_TYPE__'
-'__UINTPTR_TYPE__'
+ OSF/rose `-mno-underscores' option).
+
+`__SIZE_TYPE__'
+`__PTRDIFF_TYPE__'
+`__WCHAR_TYPE__'
+`__WINT_TYPE__'
+`__INTMAX_TYPE__'
+`__UINTMAX_TYPE__'
+`__SIG_ATOMIC_TYPE__'
+`__INT8_TYPE__'
+`__INT16_TYPE__'
+`__INT32_TYPE__'
+`__INT64_TYPE__'
+`__UINT8_TYPE__'
+`__UINT16_TYPE__'
+`__UINT32_TYPE__'
+`__UINT64_TYPE__'
+`__INT_LEAST8_TYPE__'
+`__INT_LEAST16_TYPE__'
+`__INT_LEAST32_TYPE__'
+`__INT_LEAST64_TYPE__'
+`__UINT_LEAST8_TYPE__'
+`__UINT_LEAST16_TYPE__'
+`__UINT_LEAST32_TYPE__'
+`__UINT_LEAST64_TYPE__'
+`__INT_FAST8_TYPE__'
+`__INT_FAST16_TYPE__'
+`__INT_FAST32_TYPE__'
+`__INT_FAST64_TYPE__'
+`__UINT_FAST8_TYPE__'
+`__UINT_FAST16_TYPE__'
+`__UINT_FAST32_TYPE__'
+`__UINT_FAST64_TYPE__'
+`__INTPTR_TYPE__'
+`__UINTPTR_TYPE__'
These macros are defined to the correct underlying types for the
- 'size_t', 'ptrdiff_t', 'wchar_t', 'wint_t', 'intmax_t',
- 'uintmax_t', 'sig_atomic_t', 'int8_t', 'int16_t', 'int32_t',
- 'int64_t', 'uint8_t', 'uint16_t', 'uint32_t', 'uint64_t',
- 'int_least8_t', 'int_least16_t', 'int_least32_t', 'int_least64_t',
- 'uint_least8_t', 'uint_least16_t', 'uint_least32_t',
- 'uint_least64_t', 'int_fast8_t', 'int_fast16_t', 'int_fast32_t',
- 'int_fast64_t', 'uint_fast8_t', 'uint_fast16_t', 'uint_fast32_t',
- 'uint_fast64_t', 'intptr_t', and 'uintptr_t' typedefs,
+ `size_t', `ptrdiff_t', `wchar_t', `wint_t', `intmax_t',
+ `uintmax_t', `sig_atomic_t', `int8_t', `int16_t', `int32_t',
+ `int64_t', `uint8_t', `uint16_t', `uint32_t', `uint64_t',
+ `int_least8_t', `int_least16_t', `int_least32_t', `int_least64_t',
+ `uint_least8_t', `uint_least16_t', `uint_least32_t',
+ `uint_least64_t', `int_fast8_t', `int_fast16_t', `int_fast32_t',
+ `int_fast64_t', `uint_fast8_t', `uint_fast16_t', `uint_fast32_t',
+ `uint_fast64_t', `intptr_t', and `uintptr_t' typedefs,
respectively. They exist to make the standard header files
- 'stddef.h', 'stdint.h', and 'wchar.h' work correctly. You should
+ `stddef.h', `stdint.h', and `wchar.h' work correctly. You should
not use these macros directly; instead, include the appropriate
headers and use the typedefs. Some of these macros may not be
- defined on particular systems if GCC does not provide a 'stdint.h'
+ defined on particular systems if GCC does not provide a `stdint.h'
header on those systems.
-'__CHAR_BIT__'
+`__CHAR_BIT__'
Defined to the number of bits used in the representation of the
- 'char' data type. It exists to make the standard header given
+ `char' data type. It exists to make the standard header given
numerical limits work correctly. You should not use this macro
directly; instead, include the appropriate headers.
-'__SCHAR_MAX__'
-'__WCHAR_MAX__'
-'__SHRT_MAX__'
-'__INT_MAX__'
-'__LONG_MAX__'
-'__LONG_LONG_MAX__'
-'__WINT_MAX__'
-'__SIZE_MAX__'
-'__PTRDIFF_MAX__'
-'__INTMAX_MAX__'
-'__UINTMAX_MAX__'
-'__SIG_ATOMIC_MAX__'
-'__INT8_MAX__'
-'__INT16_MAX__'
-'__INT32_MAX__'
-'__INT64_MAX__'
-'__UINT8_MAX__'
-'__UINT16_MAX__'
-'__UINT32_MAX__'
-'__UINT64_MAX__'
-'__INT_LEAST8_MAX__'
-'__INT_LEAST16_MAX__'
-'__INT_LEAST32_MAX__'
-'__INT_LEAST64_MAX__'
-'__UINT_LEAST8_MAX__'
-'__UINT_LEAST16_MAX__'
-'__UINT_LEAST32_MAX__'
-'__UINT_LEAST64_MAX__'
-'__INT_FAST8_MAX__'
-'__INT_FAST16_MAX__'
-'__INT_FAST32_MAX__'
-'__INT_FAST64_MAX__'
-'__UINT_FAST8_MAX__'
-'__UINT_FAST16_MAX__'
-'__UINT_FAST32_MAX__'
-'__UINT_FAST64_MAX__'
-'__INTPTR_MAX__'
-'__UINTPTR_MAX__'
-'__WCHAR_MIN__'
-'__WINT_MIN__'
-'__SIG_ATOMIC_MIN__'
- Defined to the maximum value of the 'signed char', 'wchar_t',
- 'signed short', 'signed int', 'signed long', 'signed long long',
- 'wint_t', 'size_t', 'ptrdiff_t', 'intmax_t', 'uintmax_t',
- 'sig_atomic_t', 'int8_t', 'int16_t', 'int32_t', 'int64_t',
- 'uint8_t', 'uint16_t', 'uint32_t', 'uint64_t', 'int_least8_t',
- 'int_least16_t', 'int_least32_t', 'int_least64_t', 'uint_least8_t',
- 'uint_least16_t', 'uint_least32_t', 'uint_least64_t',
- 'int_fast8_t', 'int_fast16_t', 'int_fast32_t', 'int_fast64_t',
- 'uint_fast8_t', 'uint_fast16_t', 'uint_fast32_t', 'uint_fast64_t',
- 'intptr_t', and 'uintptr_t' types and to the minimum value of the
- 'wchar_t', 'wint_t', and 'sig_atomic_t' types respectively. They
- exist to make the standard header given numerical limits work
- correctly. You should not use these macros directly; instead,
- include the appropriate headers. Some of these macros may not be
- defined on particular systems if GCC does not provide a 'stdint.h'
- header on those systems.
-
-'__INT8_C'
-'__INT16_C'
-'__INT32_C'
-'__INT64_C'
-'__UINT8_C'
-'__UINT16_C'
-'__UINT32_C'
-'__UINT64_C'
-'__INTMAX_C'
-'__UINTMAX_C'
- Defined to implementations of the standard 'stdint.h' macros with
- the same names without the leading '__'. They exist the make the
+`__SCHAR_MAX__'
+`__WCHAR_MAX__'
+`__SHRT_MAX__'
+`__INT_MAX__'
+`__LONG_MAX__'
+`__LONG_LONG_MAX__'
+`__WINT_MAX__'
+`__SIZE_MAX__'
+`__PTRDIFF_MAX__'
+`__INTMAX_MAX__'
+`__UINTMAX_MAX__'
+`__SIG_ATOMIC_MAX__'
+`__INT8_MAX__'
+`__INT16_MAX__'
+`__INT32_MAX__'
+`__INT64_MAX__'
+`__UINT8_MAX__'
+`__UINT16_MAX__'
+`__UINT32_MAX__'
+`__UINT64_MAX__'
+`__INT_LEAST8_MAX__'
+`__INT_LEAST16_MAX__'
+`__INT_LEAST32_MAX__'
+`__INT_LEAST64_MAX__'
+`__UINT_LEAST8_MAX__'
+`__UINT_LEAST16_MAX__'
+`__UINT_LEAST32_MAX__'
+`__UINT_LEAST64_MAX__'
+`__INT_FAST8_MAX__'
+`__INT_FAST16_MAX__'
+`__INT_FAST32_MAX__'
+`__INT_FAST64_MAX__'
+`__UINT_FAST8_MAX__'
+`__UINT_FAST16_MAX__'
+`__UINT_FAST32_MAX__'
+`__UINT_FAST64_MAX__'
+`__INTPTR_MAX__'
+`__UINTPTR_MAX__'
+`__WCHAR_MIN__'
+`__WINT_MIN__'
+`__SIG_ATOMIC_MIN__'
+ Defined to the maximum value of the `signed char', `wchar_t',
+ `signed short', `signed int', `signed long', `signed long long',
+ `wint_t', `size_t', `ptrdiff_t', `intmax_t', `uintmax_t',
+ `sig_atomic_t', `int8_t', `int16_t', `int32_t', `int64_t',
+ `uint8_t', `uint16_t', `uint32_t', `uint64_t', `int_least8_t',
+ `int_least16_t', `int_least32_t', `int_least64_t',
+ `uint_least8_t', `uint_least16_t', `uint_least32_t',
+ `uint_least64_t', `int_fast8_t', `int_fast16_t', `int_fast32_t',
+ `int_fast64_t', `uint_fast8_t', `uint_fast16_t', `uint_fast32_t',
+ `uint_fast64_t', `intptr_t', and `uintptr_t' types and to the
+ minimum value of the `wchar_t', `wint_t', and `sig_atomic_t' types
+ respectively. They exist to make the standard header given
+ numerical limits work correctly. You should not use these macros
+ directly; instead, include the appropriate headers. Some of these
+ macros may not be defined on particular systems if GCC does not
+ provide a `stdint.h' header on those systems.
+
+`__INT8_C'
+`__INT16_C'
+`__INT32_C'
+`__INT64_C'
+`__UINT8_C'
+`__UINT16_C'
+`__UINT32_C'
+`__UINT64_C'
+`__INTMAX_C'
+`__UINTMAX_C'
+ Defined to implementations of the standard `stdint.h' macros with
+ the same names without the leading `__'. They exist the make the
implementation of that header work correctly. You should not use
these macros directly; instead, include the appropriate headers.
Some of these macros may not be defined on particular systems if
- GCC does not provide a 'stdint.h' header on those systems.
-
-'__SIZEOF_INT__'
-'__SIZEOF_LONG__'
-'__SIZEOF_LONG_LONG__'
-'__SIZEOF_SHORT__'
-'__SIZEOF_POINTER__'
-'__SIZEOF_FLOAT__'
-'__SIZEOF_DOUBLE__'
-'__SIZEOF_LONG_DOUBLE__'
-'__SIZEOF_SIZE_T__'
-'__SIZEOF_WCHAR_T__'
-'__SIZEOF_WINT_T__'
-'__SIZEOF_PTRDIFF_T__'
- Defined to the number of bytes of the C standard data types: 'int',
- 'long', 'long long', 'short', 'void *', 'float', 'double', 'long
- double', 'size_t', 'wchar_t', 'wint_t' and 'ptrdiff_t'.
-
-'__BYTE_ORDER__'
-'__ORDER_LITTLE_ENDIAN__'
-'__ORDER_BIG_ENDIAN__'
-'__ORDER_PDP_ENDIAN__'
- '__BYTE_ORDER__' is defined to one of the values
- '__ORDER_LITTLE_ENDIAN__', '__ORDER_BIG_ENDIAN__', or
- '__ORDER_PDP_ENDIAN__' to reflect the layout of multi-byte and
- multi-word quantities in memory. If '__BYTE_ORDER__' is equal to
- '__ORDER_LITTLE_ENDIAN__' or '__ORDER_BIG_ENDIAN__', then
+ GCC does not provide a `stdint.h' header on those systems.
+
+`__SIZEOF_INT__'
+`__SIZEOF_LONG__'
+`__SIZEOF_LONG_LONG__'
+`__SIZEOF_SHORT__'
+`__SIZEOF_POINTER__'
+`__SIZEOF_FLOAT__'
+`__SIZEOF_DOUBLE__'
+`__SIZEOF_LONG_DOUBLE__'
+`__SIZEOF_SIZE_T__'
+`__SIZEOF_WCHAR_T__'
+`__SIZEOF_WINT_T__'
+`__SIZEOF_PTRDIFF_T__'
+ Defined to the number of bytes of the C standard data types: `int',
+ `long', `long long', `short', `void *', `float', `double', `long
+ double', `size_t', `wchar_t', `wint_t' and `ptrdiff_t'.
+
+`__BYTE_ORDER__'
+`__ORDER_LITTLE_ENDIAN__'
+`__ORDER_BIG_ENDIAN__'
+`__ORDER_PDP_ENDIAN__'
+ `__BYTE_ORDER__' is defined to one of the values
+ `__ORDER_LITTLE_ENDIAN__', `__ORDER_BIG_ENDIAN__', or
+ `__ORDER_PDP_ENDIAN__' to reflect the layout of multi-byte and
+ multi-word quantities in memory. If `__BYTE_ORDER__' is equal to
+ `__ORDER_LITTLE_ENDIAN__' or `__ORDER_BIG_ENDIAN__', then
multi-byte and multi-word quantities are laid out identically: the
byte (word) at the lowest address is the least significant or most
significant byte (word) of the quantity, respectively. If
- '__BYTE_ORDER__' is equal to '__ORDER_PDP_ENDIAN__', then bytes in
+ `__BYTE_ORDER__' is equal to `__ORDER_PDP_ENDIAN__', then bytes in
16-bit words are laid out in a little-endian fashion, whereas the
16-bit subwords of a 32-bit quantity are laid out in big-endian
fashion.
@@ -2076,151 +2084,154 @@ double underscores.
/* Test for a little-endian machine */
#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
-'__FLOAT_WORD_ORDER__'
- '__FLOAT_WORD_ORDER__' is defined to one of the values
- '__ORDER_LITTLE_ENDIAN__' or '__ORDER_BIG_ENDIAN__' to reflect the
+`__FLOAT_WORD_ORDER__'
+ `__FLOAT_WORD_ORDER__' is defined to one of the values
+ `__ORDER_LITTLE_ENDIAN__' or `__ORDER_BIG_ENDIAN__' to reflect the
layout of the words of multi-word floating-point quantities.
-'__DEPRECATED'
+`__DEPRECATED'
This macro is defined, with value 1, when compiling a C++ source
file with warnings about deprecated constructs enabled. These
warnings are enabled by default, but can be disabled with
- '-Wno-deprecated'.
+ `-Wno-deprecated'.
-'__EXCEPTIONS'
+`__EXCEPTIONS'
This macro is defined, with value 1, when compiling a C++ source
- file with exceptions enabled. If '-fno-exceptions' is used when
+ file with exceptions enabled. If `-fno-exceptions' is used when
compiling the file, then this macro is not defined.
-'__GXX_RTTI'
+`__GXX_RTTI'
This macro is defined, with value 1, when compiling a C++ source
- file with runtime type identification enabled. If '-fno-rtti' is
+ file with runtime type identification enabled. If `-fno-rtti' is
used when compiling the file, then this macro is not defined.
-'__USING_SJLJ_EXCEPTIONS__'
+`__USING_SJLJ_EXCEPTIONS__'
This macro is defined, with value 1, if the compiler uses the old
- mechanism based on 'setjmp' and 'longjmp' for exception handling.
+ mechanism based on `setjmp' and `longjmp' for exception handling.
-'__GXX_EXPERIMENTAL_CXX0X__'
+`__GXX_EXPERIMENTAL_CXX0X__'
This macro is defined when compiling a C++ source file with the
- option '-std=c++0x' or '-std=gnu++0x'. It indicates that some
- features likely to be included in C++0x are available. Note that
+ option `-std=c++0x' or `-std=gnu++0x'. It indicates that some
+ features likely to be included in C++0x are available. Note that
these features are experimental, and may change or be removed in
future versions of GCC.
-'__GXX_WEAK__'
+`__GXX_WEAK__'
This macro is defined when compiling a C++ source file. It has the
value 1 if the compiler will use weak symbols, COMDAT sections, or
other similar techniques to collapse symbols with "vague linkage"
that are defined in multiple translation units. If the compiler
- will not collapse such symbols, this macro is defined with value 0.
- In general, user code should not need to make use of this macro;
- the purpose of this macro is to ease implementation of the C++
- runtime library provided with G++.
+ will not collapse such symbols, this macro is defined with value
+ 0. In general, user code should not need to make use of this
+ macro; the purpose of this macro is to ease implementation of the
+ C++ runtime library provided with G++.
-'__NEXT_RUNTIME__'
+`__NEXT_RUNTIME__'
This macro is defined, with value 1, if (and only if) the NeXT
- runtime (as in '-fnext-runtime') is in use for Objective-C. If the
- GNU runtime is used, this macro is not defined, so that you can use
- this macro to determine which runtime (NeXT or GNU) is being used.
+ runtime (as in `-fnext-runtime') is in use for Objective-C. If
+ the GNU runtime is used, this macro is not defined, so that you
+ can use this macro to determine which runtime (NeXT or GNU) is
+ being used.
-'__LP64__'
-'_LP64'
+`__LP64__'
+`_LP64'
These macros are defined, with value 1, if (and only if) the
- compilation is for a target where 'long int' and pointer both use
- 64-bits and 'int' uses 32-bit.
+ compilation is for a target where `long int' and pointer both use
+ 64-bits and `int' uses 32-bit.
-'__SSP__'
- This macro is defined, with value 1, when '-fstack-protector' is in
+`__SSP__'
+ This macro is defined, with value 1, when `-fstack-protector' is in
use.
-'__SSP_ALL__'
- This macro is defined, with value 2, when '-fstack-protector-all'
+`__SSP_ALL__'
+ This macro is defined, with value 2, when `-fstack-protector-all'
is in use.
-'__SSP_STRONG__'
+`__SSP_STRONG__'
This macro is defined, with value 3, when
- '-fstack-protector-strong' is in use.
+ `-fstack-protector-strong' is in use.
-'__SSP_EXPLICIT__'
+`__SSP_EXPLICIT__'
This macro is defined, with value 4, when
- '-fstack-protector-explicit' is in use.
+ `-fstack-protector-explicit' is in use.
-'__SANITIZE_ADDRESS__'
- This macro is defined, with value 1, when '-fsanitize=address' or
- '-fsanitize=kernel-address' are in use.
+`__SANITIZE_ADDRESS__'
+ This macro is defined, with value 1, when `-fsanitize=address' or
+ `-fsanitize=kernel-address' are in use.
-'__TIMESTAMP__'
- This macro expands to a string constant that describes the date and
- time of the last modification of the current source file. The
- string constant contains abbreviated day of the week, month, day of
- the month, time in hh:mm:ss form, year and looks like
- '"Sun Sep 16 01:03:52 1973"'. If the day of the month is less than
- 10, it is padded with a space on the left.
+`__TIMESTAMP__'
+ This macro expands to a string constant that describes the date
+ and time of the last modification of the current source file. The
+ string constant contains abbreviated day of the week, month, day
+ of the month, time in hh:mm:ss form, year and looks like
+ `"Sun Sep 16 01:03:52 1973"'. If the day of the month is less
+ than 10, it is padded with a space on the left.
If GCC cannot determine the current date, it will emit a warning
- message (once per compilation) and '__TIMESTAMP__' will expand to
- '"??? ??? ?? ??:??:?? ????"'.
-
-'__GCC_HAVE_SYNC_COMPARE_AND_SWAP_1'
-'__GCC_HAVE_SYNC_COMPARE_AND_SWAP_2'
-'__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4'
-'__GCC_HAVE_SYNC_COMPARE_AND_SWAP_8'
-'__GCC_HAVE_SYNC_COMPARE_AND_SWAP_16'
+ message (once per compilation) and `__TIMESTAMP__' will expand to
+ `"??? ??? ?? ??:??:?? ????"'.
+
+`__GCC_HAVE_SYNC_COMPARE_AND_SWAP_1'
+`__GCC_HAVE_SYNC_COMPARE_AND_SWAP_2'
+`__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4'
+`__GCC_HAVE_SYNC_COMPARE_AND_SWAP_8'
+`__GCC_HAVE_SYNC_COMPARE_AND_SWAP_16'
These macros are defined when the target processor supports atomic
compare and swap operations on operands 1, 2, 4, 8 or 16 bytes in
length, respectively.
-'__GCC_HAVE_DWARF2_CFI_ASM'
+`__GCC_HAVE_DWARF2_CFI_ASM'
This macro is defined when the compiler is emitting Dwarf2 CFI
directives to the assembler. When this is defined, it is possible
to emit those same directives in inline assembly.
-'__FP_FAST_FMA'
-'__FP_FAST_FMAF'
-'__FP_FAST_FMAL'
+`__FP_FAST_FMA'
+`__FP_FAST_FMAF'
+`__FP_FAST_FMAL'
These macros are defined with value 1 if the backend supports the
- 'fma', 'fmaf', and 'fmal' builtin functions, so that the include
- file 'math.h' can define the macros 'FP_FAST_FMA', 'FP_FAST_FMAF',
- and 'FP_FAST_FMAL' for compatibility with the 1999 C standard.
+ `fma', `fmaf', and `fmal' builtin functions, so that the include
+ file `math.h' can define the macros `FP_FAST_FMA', `FP_FAST_FMAF',
+ and `FP_FAST_FMAL' for compatibility with the 1999 C standard.
-'__GCC_IEC_559'
+`__GCC_IEC_559'
This macro is defined to indicate the intended level of support for
IEEE 754 (IEC 60559) floating-point arithmetic. It expands to a
- nonnegative integer value. If 0, it indicates that the combination
- of the compiler configuration and the command-line options is not
- intended to support IEEE 754 arithmetic for 'float' and 'double' as
- defined in C99 and C11 Annex F (for example, that the standard
- rounding modes and exceptions are not supported, or that
- optimizations are enabled that conflict with IEEE 754 semantics).
- If 1, it indicates that IEEE 754 arithmetic is intended to be
- supported; this does not mean that all relevant language features
- are supported by GCC. If 2 or more, it additionally indicates
- support for IEEE 754-2008 (in particular, that the binary encodings
- for quiet and signaling NaNs are as specified in IEEE 754-2008).
+ nonnegative integer value. If 0, it indicates that the
+ combination of the compiler configuration and the command-line
+ options is not intended to support IEEE 754 arithmetic for `float'
+ and `double' as defined in C99 and C11 Annex F (for example, that
+ the standard rounding modes and exceptions are not supported, or
+ that optimizations are enabled that conflict with IEEE 754
+ semantics). If 1, it indicates that IEEE 754 arithmetic is
+ intended to be supported; this does not mean that all relevant
+ language features are supported by GCC. If 2 or more, it
+ additionally indicates support for IEEE 754-2008 (in particular,
+ that the binary encodings for quiet and signaling NaNs are as
+ specified in IEEE 754-2008).
This macro does not indicate the default state of command-line
options that control optimizations that C99 and C11 permit to be
controlled by standard pragmas, where those standards do not
require a particular default state. It does not indicate whether
optimizations respect signaling NaN semantics (the macro for that
- is '__SUPPORT_SNAN__'). It does not indicate support for decimal
+ is `__SUPPORT_SNAN__'). It does not indicate support for decimal
floating point or the IEEE 754 binary16 and binary128 types.
-'__GCC_IEC_559_COMPLEX'
+`__GCC_IEC_559_COMPLEX'
This macro is defined to indicate the intended level of support for
- IEEE 754 (IEC 60559) floating-point arithmetic for complex numbers,
- as defined in C99 and C11 Annex G. It expands to a nonnegative
- integer value. If 0, it indicates that the combination of the
- compiler configuration and the command-line options is not intended
- to support Annex G requirements (for example, because
- '-fcx-limited-range' was used). If 1 or more, it indicates that it
- is intended to support those requirements; this does not mean that
- all relevant language features are supported by GCC.
-
-'__NO_MATH_ERRNO__'
- This macro is defined if '-fno-math-errno' is used, or enabled by
- another option such as '-ffast-math' or by default.
+ IEEE 754 (IEC 60559) floating-point arithmetic for complex
+ numbers, as defined in C99 and C11 Annex G. It expands to a
+ nonnegative integer value. If 0, it indicates that the
+ combination of the compiler configuration and the command-line
+ options is not intended to support Annex G requirements (for
+ example, because `-fcx-limited-range' was used). If 1 or more, it
+ indicates that it is intended to support those requirements; this
+ does not mean that all relevant language features are supported by
+ GCC.
+
+`__NO_MATH_ERRNO__'
+ This macro is defined if `-fno-math-errno' is used, or enabled by
+ another option such as `-ffast-math' or by default.

File: cpp.info, Node: System-specific Predefined Macros, Next: C++ Named Operators, Prev: Common Predefined Macros, Up: Predefined Macros
@@ -2231,23 +2242,23 @@ File: cpp.info, Node: System-specific Predefined Macros, Next: C++ Named Opera
The C preprocessor normally predefines several macros that indicate what
type of system and machine is in use. They are obviously different on
each target supported by GCC. This manual, being for all systems and
-machines, cannot tell you what their names are, but you can use 'cpp
+machines, cannot tell you what their names are, but you can use `cpp
-dM' to see them all. *Note Invocation::. All system-specific
predefined macros expand to a constant value, so you can test them with
-either '#ifdef' or '#if'.
+either `#ifdef' or `#if'.
The C standard requires that all system-specific macros be part of
the "reserved namespace". All names which begin with two underscores,
or an underscore and a capital letter, are reserved for the compiler and
library to use as they wish. However, historically system-specific
macros have had names with no special prefix; for instance, it is common
-to find 'unix' defined on Unix systems. For all such macros, GCC
+to find `unix' defined on Unix systems. For all such macros, GCC
provides a parallel macro with two underscores added at the beginning
-and the end. If 'unix' is defined, '__unix__' will be defined too.
-There will never be more than two underscores; the parallel of '_mips'
-is '__mips__'.
+and the end. If `unix' is defined, `__unix__' will be defined too.
+There will never be more than two underscores; the parallel of `_mips'
+is `__mips__'.
- When the '-ansi' option, or any '-std' option that requests strict
+ When the `-ansi' option, or any `-std' option that requests strict
conformance, is given to the compiler, all the system-specific
predefined macros outside the reserved namespace are suppressed. The
parallel macros, inside the reserved namespace, remain defined.
@@ -2258,7 +2269,7 @@ encourage you to correct older code to use the parallel macros whenever
you find it. We don't recommend you use the system-specific macros that
are in the reserved namespace, either. It is better in the long run to
check specifically for features you need, using a tool such as
-'autoconf'.
+`autoconf'.

File: cpp.info, Node: C++ Named Operators, Prev: System-specific Predefined Macros, Up: Predefined Macros
@@ -2269,25 +2280,25 @@ File: cpp.info, Node: C++ Named Operators, Prev: System-specific Predefined Ma
In C++, there are eleven keywords which are simply alternate spellings
of operators normally written with punctuation. These keywords are
treated as such even in the preprocessor. They function as operators in
-'#if', and they cannot be defined as macros or poisoned. In C, you can
+`#if', and they cannot be defined as macros or poisoned. In C, you can
request that those keywords take their C++ meaning by including
-'iso646.h'. That header defines each one as a normal object-like macro
+`iso646.h'. That header defines each one as a normal object-like macro
expanding to the appropriate punctuator.
These are the named operators and their corresponding punctuators:
Named Operator Punctuator
-'and' '&&'
-'and_eq' '&='
-'bitand' '&'
-'bitor' '|'
-'compl' '~'
-'not' '!'
-'not_eq' '!='
-'or' '||'
-'or_eq' '|='
-'xor' '^'
-'xor_eq' '^='
+`and' `&&'
+`and_eq' `&='
+`bitand' `&'
+`bitor' `|'
+`compl' `~'
+`not' `!'
+`not_eq' `!='
+`or' `||'
+`or_eq' `|='
+`xor' `^'
+`xor_eq' `^='

File: cpp.info, Node: Undefining and Redefining Macros, Next: Directives Within Macro Arguments, Prev: Predefined Macros, Up: Macros
@@ -2295,11 +2306,11 @@ File: cpp.info, Node: Undefining and Redefining Macros, Next: Directives Withi
3.8 Undefining and Redefining Macros
====================================
-If a macro ceases to be useful, it may be "undefined" with the '#undef'
-directive. '#undef' takes a single argument, the name of the macro to
+If a macro ceases to be useful, it may be "undefined" with the `#undef'
+directive. `#undef' takes a single argument, the name of the macro to
undefine. You use the bare macro name, even if the macro is
-function-like. It is an error if anything appears on the line after the
-macro name. '#undef' has no effect if the name is not a macro.
+function-like. It is an error if anything appears on the line after
+the macro name. `#undef' has no effect if the name is not a macro.
#define FOO 4
x = FOO; ==> x = 4;
@@ -2307,15 +2318,18 @@ macro name. '#undef' has no effect if the name is not a macro.
x = FOO; ==> x = FOO;
Once a macro has been undefined, that identifier may be "redefined"
-as a macro by a subsequent '#define' directive. The new definition need
-not have any resemblance to the old definition.
+as a macro by a subsequent `#define' directive. The new definition
+need not have any resemblance to the old definition.
However, if an identifier which is currently a macro is redefined,
then the new definition must be "effectively the same" as the old one.
Two macro definitions are effectively the same if:
* Both are the same type of macro (object- or function-like).
+
* All the tokens of the replacement list are the same.
+
* If there are any parameters, they are the same.
+
* Whitespace appears in the same places in both. It need not be
exactly the same amount of whitespace, though. Remember that
comments count as whitespace.
@@ -2324,7 +2338,7 @@ These definitions are effectively the same:
#define FOUR (2 + 2)
#define FOUR (2 + 2)
#define FOUR (2 /* two */ + 2)
-but these are not:
+ but these are not:
#define FOUR (2 + 2)
#define FOUR ( 2+2 )
#define FOUR (2 * 2)
@@ -2350,11 +2364,11 @@ these cases is undefined.
Versions of CPP prior to 3.2 would reject such constructs with an
error message. This was the only syntactic difference between normal
functions and function-like macros, so it seemed attractive to remove
-this limitation, and people would often be surprised that they could not
-use macros in this way. Moreover, sometimes people would use
+this limitation, and people would often be surprised that they could
+not use macros in this way. Moreover, sometimes people would use
conditional compilation in the argument list to a normal library
-function like 'printf', only to find that after a library upgrade
-'printf' had changed to be a function-like macro, and their code would
+function like `printf', only to find that after a library upgrade
+`printf' had changed to be a function-like macro, and their code would
no longer compile. So from version 3.2 we changed CPP to successfully
process arbitrary directives within macro arguments in exactly the same
way as it would have processed the directive were the function-like
@@ -2425,9 +2439,9 @@ outside of it. For example,
strange(stderr) p, 35)
==> fprintf (stderr, "%s %d", p, 35)
- The ability to piece together a macro call can be useful, but the use
-of unbalanced open parentheses in a macro body is just confusing, and
-should be avoided.
+ The ability to piece together a macro call can be useful, but the
+use of unbalanced open parentheses in a macro body is just confusing,
+and should be avoided.

File: cpp.info, Node: Operator Precedence Problems, Next: Swallowing the Semicolon, Prev: Misnesting, Up: Macro Pitfalls
@@ -2446,8 +2460,8 @@ way.
#define ceil_div(x, y) (x + y - 1) / y
whose purpose is to divide, rounding up. (One use for this operation is
-to compute how many 'int' objects are needed to hold a certain number of
-'char' objects.) Then suppose it is used as follows:
+to compute how many `int' objects are needed to hold a certain number
+of `char' objects.) Then suppose it is used as follows:
a = ceil_div (b & c, sizeof (int));
==> a = (b & c + sizeof (int) - 1) / sizeof (int);
@@ -2467,19 +2481,19 @@ Defining the macro as
provides the desired result.
- Unintended grouping can result in another way. Consider 'sizeof
+ Unintended grouping can result in another way. Consider `sizeof
ceil_div(1, 2)'. That has the appearance of a C expression that would
-compute the size of the type of 'ceil_div (1, 2)', but in fact it means
+compute the size of the type of `ceil_div (1, 2)', but in fact it means
something very different. Here is what it expands to:
sizeof ((1) + (2) - 1) / (2)
This would take the size of an integer and divide it by two. The
-precedence rules have put the division outside the 'sizeof' when it was
+precedence rules have put the division outside the `sizeof' when it was
intended to be inside.
Parentheses around the entire macro definition prevent such problems.
-Here, then, is the recommended way to define 'ceil_div':
+Here, then, is the recommended way to define `ceil_div':
#define ceil_div(x, y) (((x) + (y) - 1) / (y))
@@ -2491,7 +2505,7 @@ File: cpp.info, Node: Swallowing the Semicolon, Next: Duplication of Side Effe
Often it is desirable to define a macro that expands into a compound
statement. Consider, for example, the following macro, that advances a
-pointer (the argument 'p' says where to find it) across whitespace
+pointer (the argument `p' says where to find it) across whitespace
characters:
#define SKIP_SPACES(p, limit) \
@@ -2504,14 +2518,14 @@ Here backslash-newline is used to split the macro definition, which must
be a single logical line, so that it resembles the way such code would
be laid out if not part of a macro definition.
- A call to this macro might be 'SKIP_SPACES (p, lim)'. Strictly
+ A call to this macro might be `SKIP_SPACES (p, lim)'. Strictly
speaking, the call expands to a compound statement, which is a complete
statement with no need for a semicolon to end it. However, since it
looks like a function call, it minimizes confusion if you can use it
-like a function call, writing a semicolon afterward, as in 'SKIP_SPACES
+like a function call, writing a semicolon afterward, as in `SKIP_SPACES
(p, lim);'
- This can cause trouble before 'else' statements, because the
+ This can cause trouble before `else' statements, because the
semicolon is actually a null statement. Suppose you write
if (*p != 0)
@@ -2519,11 +2533,11 @@ semicolon is actually a null statement. Suppose you write
else ...
The presence of two statements--the compound statement and a null
-statement--in between the 'if' condition and the 'else' makes invalid C
+statement--in between the `if' condition and the `else' makes invalid C
code.
- The definition of the macro 'SKIP_SPACES' can be altered to solve
-this problem, using a 'do ... while' statement. Here is how:
+ The definition of the macro `SKIP_SPACES' can be altered to solve
+this problem, using a `do ... while' statement. Here is how:
#define SKIP_SPACES(p, limit) \
do { char *lim = (limit); \
@@ -2532,7 +2546,7 @@ this problem, using a 'do ... while' statement. Here is how:
p--; break; }}} \
while (0)
- Now 'SKIP_SPACES (p, lim);' expands into
+ Now `SKIP_SPACES (p, lim);' expands into
do {...} while (0);
@@ -2545,12 +2559,12 @@ File: cpp.info, Node: Duplication of Side Effects, Next: Self-Referential Macr
3.10.4 Duplication of Side Effects
----------------------------------
-Many C programs define a macro 'min', for "minimum", like this:
+Many C programs define a macro `min', for "minimum", like this:
#define min(X, Y) ((X) < (Y) ? (X) : (Y))
- When you use this macro with an argument containing a side effect, as
-shown here,
+ When you use this macro with an argument containing a side effect,
+as shown here,
next = min (x + y, foo (z));
@@ -2558,17 +2572,17 @@ it expands as follows:
next = ((x + y) < (foo (z)) ? (x + y) : (foo (z)));
-where 'x + y' has been substituted for 'X' and 'foo (z)' for 'Y'.
+where `x + y' has been substituted for `X' and `foo (z)' for `Y'.
- The function 'foo' is used only once in the statement as it appears
-in the program, but the expression 'foo (z)' has been substituted twice
-into the macro expansion. As a result, 'foo' might be called two times
-when the statement is executed. If it has side effects or if it takes a
-long time to compute, the results might not be what you intended. We
-say that 'min' is an "unsafe" macro.
+ The function `foo' is used only once in the statement as it appears
+in the program, but the expression `foo (z)' has been substituted twice
+into the macro expansion. As a result, `foo' might be called two times
+when the statement is executed. If it has side effects or if it takes
+a long time to compute, the results might not be what you intended. We
+say that `min' is an "unsafe" macro.
- The best solution to this problem is to define 'min' in a way that
-computes the value of 'foo (z)' only once. The C language offers no
+ The best solution to this problem is to define `min' in a way that
+computes the value of `foo (z)' only once. The C language offers no
standard way to do this, but it can be done with GNU extensions as
follows:
@@ -2577,7 +2591,7 @@ follows:
typeof (Y) y_ = (Y); \
(x_ < y_) ? x_ : y_; })
- The '({ ... })' notation produces a compound statement that acts as
+ The `({ ... })' notation produces a compound statement that acts as
an expression. Its value is the value of its last statement. This
permits us to define local variables and assign each argument to one.
The local variables have underscores after their names to reduce the
@@ -2585,9 +2599,9 @@ risk of conflict with an identifier of wider scope (it is impossible to
avoid this entirely). Now each argument is evaluated exactly once.
If you do not wish to use GNU C extensions, the only solution is to
-be careful when _using_ the macro 'min'. For example, you can calculate
-the value of 'foo (z)', save it in a variable, and use that variable in
-'min':
+be careful when _using_ the macro `min'. For example, you can
+calculate the value of `foo (z)', save it in a variable, and use that
+variable in `min':
#define min(X, Y) ((X) < (Y) ? (X) : (Y))
...
@@ -2596,7 +2610,7 @@ the value of 'foo (z)', save it in a variable, and use that variable in
next = min (x + y, tem);
}
-(where we assume that 'foo' returns type 'int').
+(where we assume that `foo' returns type `int').

File: cpp.info, Node: Self-Referential Macros, Next: Argument Prescan, Prev: Duplication of Side Effects, Up: Macro Pitfalls
@@ -2613,42 +2627,42 @@ preprocessor output unchanged. Consider an example:
#define foo (4 + foo)
-where 'foo' is also a variable in your program.
+where `foo' is also a variable in your program.
- Following the ordinary rules, each reference to 'foo' will expand
-into '(4 + foo)'; then this will be rescanned and will expand into '(4 +
-(4 + foo))'; and so on until the computer runs out of memory.
+ Following the ordinary rules, each reference to `foo' will expand
+into `(4 + foo)'; then this will be rescanned and will expand into `(4
++ (4 + foo))'; and so on until the computer runs out of memory.
The self-reference rule cuts this process short after one step, at
-'(4 + foo)'. Therefore, this macro definition has the possibly useful
-effect of causing the program to add 4 to the value of 'foo' wherever
-'foo' is referred to.
+`(4 + foo)'. Therefore, this macro definition has the possibly useful
+effect of causing the program to add 4 to the value of `foo' wherever
+`foo' is referred to.
In most cases, it is a bad idea to take advantage of this feature. A
-person reading the program who sees that 'foo' is a variable will not
+person reading the program who sees that `foo' is a variable will not
expect that it is a macro as well. The reader will come across the
-identifier 'foo' in the program and think its value should be that of
-the variable 'foo', whereas in fact the value is four greater.
+identifier `foo' in the program and think its value should be that of
+the variable `foo', whereas in fact the value is four greater.
One common, useful use of self-reference is to create a macro which
expands to itself. If you write
#define EPERM EPERM
-then the macro 'EPERM' expands to 'EPERM'. Effectively, it is left
+then the macro `EPERM' expands to `EPERM'. Effectively, it is left
alone by the preprocessor whenever it's used in running text. You can
-tell that it's a macro with '#ifdef'. You might do this if you want to
-define numeric constants with an 'enum', but have '#ifdef' be true for
+tell that it's a macro with `#ifdef'. You might do this if you want to
+define numeric constants with an `enum', but have `#ifdef' be true for
each constant.
- If a macro 'x' expands to use a macro 'y', and the expansion of 'y'
-refers to the macro 'x', that is an "indirect self-reference" of 'x'.
-'x' is not expanded in this case either. Thus, if we have
+ If a macro `x' expands to use a macro `y', and the expansion of `y'
+refers to the macro `x', that is an "indirect self-reference" of `x'.
+`x' is not expanded in this case either. Thus, if we have
#define x (4 + y)
#define y (2 * x)
-then 'x' and 'y' expand as follows:
+then `x' and `y' expand as follows:
x ==> (4 + y)
==> (4 + (2 * x))
@@ -2681,28 +2695,28 @@ same results.
You might expect the double scan to change the results when a
self-referential macro is used in an argument of another macro (*note
-Self-Referential Macros::): the self-referential macro would be expanded
-once in the first scan, and a second time in the second scan. However,
-this is not what happens. The self-references that do not expand in the
-first scan are marked so that they will not expand in the second scan
-either.
+Self-Referential Macros::): the self-referential macro would be
+expanded once in the first scan, and a second time in the second scan.
+However, this is not what happens. The self-references that do not
+expand in the first scan are marked so that they will not expand in the
+second scan either.
You might wonder, "Why mention the prescan, if it makes no
-difference? And why not skip it and make the preprocessor faster?" The
-answer is that the prescan does make a difference in three special
+difference? And why not skip it and make the preprocessor faster?"
+The answer is that the prescan does make a difference in three special
cases:
* Nested calls to a macro.
We say that "nested" calls to a macro occur when a macro's argument
- contains a call to that very macro. For example, if 'f' is a macro
- that expects one argument, 'f (f (1))' is a nested pair of calls to
- 'f'. The desired expansion is made by expanding 'f (1)' and
- substituting that into the definition of 'f'. The prescan causes
- the expected result to happen. Without the prescan, 'f (1)' itself
- would be substituted as an argument, and the inner use of 'f' would
- appear during the main scan as an indirect self-reference and would
- not be expanded.
+ contains a call to that very macro. For example, if `f' is a macro
+ that expects one argument, `f (f (1))' is a nested pair of calls to
+ `f'. The desired expansion is made by expanding `f (1)' and
+ substituting that into the definition of `f'. The prescan causes
+ the expected result to happen. Without the prescan, `f (1)' itself
+ would be substituted as an argument, and the inner use of `f' would
+ appear during the main scan as an indirect self-reference and
+ would not be expanded.
* Macros that call other macros that stringify or concatenate.
@@ -2717,8 +2731,8 @@ cases:
#define TABLESIZE 1024
#define BUFSIZE TABLESIZE
- then 'AFTERX(BUFSIZE)' expands to 'X_BUFSIZE', and
- 'XAFTERX(BUFSIZE)' expands to 'X_1024'. (Not to 'X_TABLESIZE'.
+ then `AFTERX(BUFSIZE)' expands to `X_BUFSIZE', and
+ `XAFTERX(BUFSIZE)' expands to `X_1024'. (Not to `X_TABLESIZE'.
Prescan always does a complete expansion.)
* Macros used in arguments, whose expansions contain unshielded
@@ -2731,9 +2745,9 @@ cases:
#define bar(x) lose(x)
#define lose(x) (1 + (x))
- We would like 'bar(foo)' to turn into '(1 + (foo))', which would
- then turn into '(1 + (a,b))'. Instead, 'bar(foo)' expands into
- 'lose(a,b)', and you get an error because 'lose' requires a single
+ We would like `bar(foo)' to turn into `(1 + (foo))', which would
+ then turn into `(1 + (a,b))'. Instead, `bar(foo)' expands into
+ `lose(a,b)', and you get an error because `lose' requires a single
argument. In this case, the problem is easily solved by the same
parentheses that ought to be used to prevent misnesting of
arithmetic operations:
@@ -2742,9 +2756,10 @@ cases:
or
#define bar(x) lose((x))
- The extra pair of parentheses prevents the comma in 'foo''s
+ The extra pair of parentheses prevents the comma in `foo''s
definition from being interpreted as an argument separator.
+

File: cpp.info, Node: Newlines in Arguments, Prev: Argument Prescan, Up: Macro Pitfalls
@@ -2765,7 +2780,7 @@ different to the line containing the argument causing the problem.
ignored (),
syntax error);
-The syntax error triggered by the tokens 'syntax error' results in an
+The syntax error triggered by the tokens `syntax error' results in an
error message citing line three--the line of ignore_second_arg-- even
though the problematic code comes from line five.
@@ -2777,27 +2792,27 @@ File: cpp.info, Node: Conditionals, Next: Diagnostics, Prev: Macros, Up: Top
4 Conditionals
**************
-A "conditional" is a directive that instructs the preprocessor to select
-whether or not to include a chunk of code in the final token stream
-passed to the compiler. Preprocessor conditionals can test arithmetic
-expressions, or whether a name is defined as a macro, or both
-simultaneously using the special 'defined' operator.
+A "conditional" is a directive that instructs the preprocessor to
+select whether or not to include a chunk of code in the final token
+stream passed to the compiler. Preprocessor conditionals can test
+arithmetic expressions, or whether a name is defined as a macro, or both
+simultaneously using the special `defined' operator.
- A conditional in the C preprocessor resembles in some ways an 'if'
+ A conditional in the C preprocessor resembles in some ways an `if'
statement in C, but it is important to understand the difference between
-them. The condition in an 'if' statement is tested during the execution
-of your program. Its purpose is to allow your program to behave
-differently from run to run, depending on the data it is operating on.
-The condition in a preprocessing conditional directive is tested when
-your program is compiled. Its purpose is to allow different code to be
-included in the program depending on the situation at the time of
-compilation.
+them. The condition in an `if' statement is tested during the
+execution of your program. Its purpose is to allow your program to
+behave differently from run to run, depending on the data it is
+operating on. The condition in a preprocessing conditional directive is
+tested when your program is compiled. Its purpose is to allow different
+code to be included in the program depending on the situation at the
+time of compilation.
However, the distinction is becoming less clear. Modern compilers
-often do test 'if' statements when a program is compiled, if their
+often do test `if' statements when a program is compiled, if their
conditions are known not to vary at run time, and eliminate code which
can never be executed. If you can count on your compiler to do this,
-you may find that your program is more readable if you use 'if'
+you may find that your program is more readable if you use `if'
statements with constant conditions (perhaps determined by macros). Of
course, you can only use this to exclude code, not type definitions or
other preprocessing directives, and you can only do it if the code
@@ -2825,19 +2840,19 @@ There are three general reasons to use a conditional.
one operating system may be erroneous on another operating system;
for example, it might refer to data types or constants that do not
exist on the other system. When this happens, it is not enough to
- avoid executing the invalid code. Its mere presence will cause the
- compiler to reject the program. With a preprocessing conditional,
- the offending code can be effectively excised from the program when
- it is not valid.
+ avoid executing the invalid code. Its mere presence will cause
+ the compiler to reject the program. With a preprocessing
+ conditional, the offending code can be effectively excised from
+ the program when it is not valid.
* You may want to be able to compile the same source file into two
different programs. One version might make frequent time-consuming
consistency checks on its intermediate data, or print the values of
those data for debugging, and the other not.
- * A conditional whose condition is always false is one way to exclude
- code from the program but keep it as a sort of comment for future
- reference.
+ * A conditional whose condition is always false is one way to
+ exclude code from the program but keep it as a sort of comment for
+ future reference.
Simple programs that do not need system-specific logic or complex
debugging hooks generally will not need to use preprocessing
@@ -2850,7 +2865,7 @@ File: cpp.info, Node: Conditional Syntax, Next: Deleted Code, Prev: Condition
======================
A conditional in the C preprocessor begins with a "conditional
-directive": '#if', '#ifdef' or '#ifndef'.
+directive": `#if', `#ifdef' or `#ifndef'.
* Menu:
@@ -2879,12 +2894,12 @@ included in the output of the preprocessor if and only if MACRO is
defined. We say that the conditional "succeeds" if MACRO is defined,
"fails" if it is not.
- The CONTROLLED TEXT inside of a conditional can include preprocessing
-directives. They are executed only if the conditional succeeds. You
-can nest conditional groups inside other conditional groups, but they
-must be completely nested. In other words, '#endif' always matches the
-nearest '#ifdef' (or '#ifndef', or '#if'). Also, you cannot start a
-conditional group in one file and end it in another.
+ The CONTROLLED TEXT inside of a conditional can include
+preprocessing directives. They are executed only if the conditional
+succeeds. You can nest conditional groups inside other conditional
+groups, but they must be completely nested. In other words, `#endif'
+always matches the nearest `#ifdef' (or `#ifndef', or `#if'). Also,
+you cannot start a conditional group in one file and end it in another.
Even if a conditional fails, the CONTROLLED TEXT inside it is still
run through initial transformations and tokenization. Therefore, it
@@ -2892,18 +2907,18 @@ must all be lexically valid C. Normally the only way this matters is
that all comments and string literals inside a failing conditional group
must still be properly ended.
- The comment following the '#endif' is not required, but it is a good
+ The comment following the `#endif' is not required, but it is a good
practice if there is a lot of CONTROLLED TEXT, because it helps people
-match the '#endif' to the corresponding '#ifdef'. Older programs
-sometimes put MACRO directly after the '#endif' without enclosing it in
+match the `#endif' to the corresponding `#ifdef'. Older programs
+sometimes put MACRO directly after the `#endif' without enclosing it in
a comment. This is invalid code according to the C standard. CPP
-accepts it with a warning. It never affects which '#ifndef' the
-'#endif' matches.
+accepts it with a warning. It never affects which `#ifndef' the
+`#endif' matches.
- Sometimes you wish to use some code if a macro is _not_ defined. You
-can do this by writing '#ifndef' instead of '#ifdef'. One common use of
-'#ifndef' is to include code only the first time a header file is
-included. *Note Once-Only Headers::.
+ Sometimes you wish to use some code if a macro is _not_ defined.
+You can do this by writing `#ifndef' instead of `#ifdef'. One common
+use of `#ifndef' is to include code only the first time a header file
+is included. *Note Once-Only Headers::.
Macro definitions can vary between compilations for several reasons.
Here are some samples.
@@ -2917,19 +2932,21 @@ Here are some samples.
conditionals to avoid using a system feature on a machine where it
is not implemented.
- * Macros can be defined or undefined with the '-D' and '-U'
- command-line options when you compile the program. You can arrange
- to compile the same source file into two different programs by
- choosing a macro name to specify which program you want, writing
- conditionals to test whether or how this macro is defined, and then
- controlling the state of the macro with command-line options,
- perhaps set in the Makefile. *Note Invocation::.
+ * Macros can be defined or undefined with the `-D' and `-U'
+ command-line options when you compile the program. You can
+ arrange to compile the same source file into two different
+ programs by choosing a macro name to specify which program you
+ want, writing conditionals to test whether or how this macro is
+ defined, and then controlling the state of the macro with
+ command-line options, perhaps set in the Makefile. *Note
+ Invocation::.
* Your program might have a special header file (often called
- 'config.h') that is adjusted when the program is compiled. It can
- define or not define macros depending on the features of the system
- and the desired capabilities of the program. The adjustment can be
- automated by a tool such as 'autoconf', or done by hand.
+ `config.h') that is adjusted when the program is compiled. It can
+ define or not define macros depending on the features of the
+ system and the desired capabilities of the program. The
+ adjustment can be automated by a tool such as `autoconf', or done
+ by hand.

File: cpp.info, Node: If, Next: Defined, Prev: Ifdef, Up: Conditional Syntax
@@ -2937,7 +2954,7 @@ File: cpp.info, Node: If, Next: Defined, Prev: Ifdef, Up: Conditional Syntax
4.2.2 If
--------
-The '#if' directive allows you to test the value of an arithmetic
+The `#if' directive allows you to test the value of an arithmetic
expression, rather than the mere existence of one macro. Its syntax is
#if EXPRESSION
@@ -2956,29 +2973,29 @@ restrictions. It may contain
* Arithmetic operators for addition, subtraction, multiplication,
division, bitwise operations, shifts, comparisons, and logical
- operations ('&&' and '||'). The latter two obey the usual
+ operations (`&&' and `||'). The latter two obey the usual
short-circuiting rules of standard C.
* Macros. All macros in the expression are expanded before actual
computation of the expression's value begins.
- * Uses of the 'defined' operator, which lets you check whether macros
- are defined in the middle of an '#if'.
+ * Uses of the `defined' operator, which lets you check whether macros
+ are defined in the middle of an `#if'.
* Identifiers that are not macros, which are all considered to be the
- number zero. This allows you to write '#if MACRO' instead of
- '#ifdef MACRO', if you know that MACRO, when defined, will always
+ number zero. This allows you to write `#if MACRO' instead of
+ `#ifdef MACRO', if you know that MACRO, when defined, will always
have a nonzero value. Function-like macros used without their
function call parentheses are also treated as zero.
- In some contexts this shortcut is undesirable. The '-Wundef'
+ In some contexts this shortcut is undesirable. The `-Wundef'
option causes GCC to warn whenever it encounters an identifier
- which is not a macro in an '#if'.
+ which is not a macro in an `#if'.
The preprocessor does not know anything about types in the language.
-Therefore, 'sizeof' operators are not recognized in '#if', and neither
-are 'enum' constants. They will be taken as identifiers which are not
-macros, and replaced by zero. In the case of 'sizeof', this is likely
+Therefore, `sizeof' operators are not recognized in `#if', and neither
+are `enum' constants. They will be taken as identifiers which are not
+macros, and replaced by zero. In the case of `sizeof', this is likely
to cause the expression to be invalid.
The preprocessor calculates the value of EXPRESSION. It carries out
@@ -2986,7 +3003,7 @@ all calculations in the widest integer type known to the compiler; on
most machines supported by GCC this is 64 bits. This is not the same
rule as the compiler uses to calculate the value of a constant
expression, and may give different results in some cases. If the value
-comes out to be nonzero, the '#if' succeeds and the CONTROLLED TEXT is
+comes out to be nonzero, the `#if' succeeds and the CONTROLLED TEXT is
included; otherwise it is skipped.

@@ -2995,33 +3012,34 @@ File: cpp.info, Node: Defined, Next: Else, Prev: If, Up: Conditional Syntax
4.2.3 Defined
-------------
-The special operator 'defined' is used in '#if' and '#elif' expressions
-to test whether a certain name is defined as a macro. 'defined NAME'
-and 'defined (NAME)' are both expressions whose value is 1 if NAME is
-defined as a macro at the current point in the program, and 0 otherwise.
-Thus, '#if defined MACRO' is precisely equivalent to '#ifdef MACRO'.
+The special operator `defined' is used in `#if' and `#elif' expressions
+to test whether a certain name is defined as a macro. `defined NAME'
+and `defined (NAME)' are both expressions whose value is 1 if NAME is
+defined as a macro at the current point in the program, and 0
+otherwise. Thus, `#if defined MACRO' is precisely equivalent to
+`#ifdef MACRO'.
- 'defined' is useful when you wish to test more than one macro for
+ `defined' is useful when you wish to test more than one macro for
existence at once. For example,
#if defined (__vax__) || defined (__ns16000__)
-would succeed if either of the names '__vax__' or '__ns16000__' is
+would succeed if either of the names `__vax__' or `__ns16000__' is
defined as a macro.
Conditionals written like this:
#if defined BUFSIZE && BUFSIZE >= 1024
-can generally be simplified to just '#if BUFSIZE >= 1024', since if
-'BUFSIZE' is not defined, it will be interpreted as having the value
+can generally be simplified to just `#if BUFSIZE >= 1024', since if
+`BUFSIZE' is not defined, it will be interpreted as having the value
zero.
- If the 'defined' operator appears as a result of a macro expansion,
+ If the `defined' operator appears as a result of a macro expansion,
the C standard says the behavior is undefined. GNU cpp treats it as a
-genuine 'defined' operator and evaluates it normally. It will warn
+genuine `defined' operator and evaluates it normally. It will warn
wherever your code uses this feature if you use the command-line option
-'-pedantic', since other compilers may handle it differently.
+`-pedantic', since other compilers may handle it differently.

File: cpp.info, Node: Else, Next: Elif, Prev: Defined, Up: Conditional Syntax
@@ -3029,7 +3047,7 @@ File: cpp.info, Node: Else, Next: Elif, Prev: Defined, Up: Conditional Synta
4.2.4 Else
----------
-The '#else' directive can be added to a conditional to provide
+The `#else' directive can be added to a conditional to provide
alternative text to be used if the condition fails. This is what it
looks like:
@@ -3042,7 +3060,7 @@ looks like:
If EXPRESSION is nonzero, the TEXT-IF-TRUE is included and the
TEXT-IF-FALSE is skipped. If EXPRESSION is zero, the opposite happens.
- You can use '#else' with '#ifdef' and '#ifndef', too.
+ You can use `#else' with `#ifdef' and `#ifndef', too.

File: cpp.info, Node: Elif, Prev: Else, Up: Conditional Syntax
@@ -3063,8 +3081,8 @@ two possible alternatives. For example, you might have
#endif /* X != 2 */
#endif /* X != 1 */
- Another conditional directive, '#elif', allows this to be abbreviated
-as follows:
+ Another conditional directive, `#elif', allows this to be
+abbreviated as follows:
#if X == 1
...
@@ -3074,20 +3092,20 @@ as follows:
...
#endif /* X != 2 and X != 1*/
- '#elif' stands for "else if". Like '#else', it goes in the middle of
-a conditional group and subdivides it; it does not require a matching
-'#endif' of its own. Like '#if', the '#elif' directive includes an
-expression to be tested. The text following the '#elif' is processed
-only if the original '#if'-condition failed and the '#elif' condition
-succeeds.
+ `#elif' stands for "else if". Like `#else', it goes in the middle
+of a conditional group and subdivides it; it does not require a
+matching `#endif' of its own. Like `#if', the `#elif' directive
+includes an expression to be tested. The text following the `#elif' is
+processed only if the original `#if'-condition failed and the `#elif'
+condition succeeds.
- More than one '#elif' can go in the same conditional group. Then the
-text after each '#elif' is processed only if the '#elif' condition
-succeeds after the original '#if' and all previous '#elif' directives
+ More than one `#elif' can go in the same conditional group. Then
+the text after each `#elif' is processed only if the `#elif' condition
+succeeds after the original `#if' and all previous `#elif' directives
within it have failed.
- '#else' is allowed after any number of '#elif' directives, but
-'#elif' may not follow '#else'.
+ `#else' is allowed after any number of `#elif' directives, but
+`#elif' may not follow `#else'.

File: cpp.info, Node: Deleted Code, Prev: Conditional Syntax, Up: Conditionals
@@ -3102,20 +3120,20 @@ code will end the commenting-out. The probable result is a flood of
syntax errors.
One way to avoid this problem is to use an always-false conditional
-instead. For instance, put '#if 0' before the deleted code and '#endif'
-after it. This works even if the code being turned off contains
-conditionals, but they must be entire conditionals (balanced '#if' and
-'#endif').
+instead. For instance, put `#if 0' before the deleted code and
+`#endif' after it. This works even if the code being turned off
+contains conditionals, but they must be entire conditionals (balanced
+`#if' and `#endif').
- Some people use '#ifdef notdef' instead. This is risky, because
-'notdef' might be accidentally defined as a macro, and then the
-conditional would succeed. '#if 0' can be counted on to fail.
+ Some people use `#ifdef notdef' instead. This is risky, because
+`notdef' might be accidentally defined as a macro, and then the
+conditional would succeed. `#if 0' can be counted on to fail.
- Do not use '#if 0' for comments which are not C code. Use a real
-comment, instead. The interior of '#if 0' must consist of complete
+ Do not use `#if 0' for comments which are not C code. Use a real
+comment, instead. The interior of `#if 0' must consist of complete
tokens; in particular, single-quote characters must balance. Comments
often contain unbalanced single-quote characters (known in English as
-apostrophes). These confuse '#if 0'. They don't confuse '/*'.
+apostrophes). These confuse `#if 0'. They don't confuse `/*'.

File: cpp.info, Node: Diagnostics, Next: Line Control, Prev: Conditionals, Up: Top
@@ -3123,11 +3141,11 @@ File: cpp.info, Node: Diagnostics, Next: Line Control, Prev: Conditionals, U
5 Diagnostics
*************
-The directive '#error' causes the preprocessor to report a fatal error.
-The tokens forming the rest of the line following '#error' are used as
+The directive `#error' causes the preprocessor to report a fatal error.
+The tokens forming the rest of the line following `#error' are used as
the error message.
- You would use '#error' inside of a conditional that detects a
+ You would use `#error' inside of a conditional that detects a
combination of parameters which you know the program does not properly
support. For example, if you know that the program will not run
properly on a VAX, you might write
@@ -3138,24 +3156,24 @@ properly on a VAX, you might write
If you have several configuration parameters that must be set up by
the installation in a consistent way, you can use conditionals to detect
-an inconsistency and report it with '#error'. For example,
+an inconsistency and report it with `#error'. For example,
#if !defined(FOO) && defined(BAR)
#error "BAR requires FOO."
#endif
- The directive '#warning' is like '#error', but causes the
+ The directive `#warning' is like `#error', but causes the
preprocessor to issue a warning and continue preprocessing. The tokens
-following '#warning' are used as the warning message.
+following `#warning' are used as the warning message.
- You might use '#warning' in obsolete header files, with a message
+ You might use `#warning' in obsolete header files, with a message
directing the user to the header file which should be used instead.
- Neither '#error' nor '#warning' macro-expands its argument. Internal
-whitespace sequences are each replaced with a single space. The line
-must consist of complete tokens. It is wisest to make the argument of
-these directives be a single string constant; this avoids problems with
-apostrophes and the like.
+ Neither `#error' nor `#warning' macro-expands its argument.
+Internal whitespace sequences are each replaced with a single space.
+The line must consist of complete tokens. It is wisest to make the
+argument of these directives be a single string constant; this avoids
+problems with apostrophes and the like.

File: cpp.info, Node: Line Control, Next: Pragmas, Prev: Diagnostics, Up: Top
@@ -3170,58 +3188,59 @@ reported as having appeared on the line of the source file where the
outermost macro was used. We intend to be more accurate in the future.
If you write a program which generates source code, such as the
-'bison' parser generator, you may want to adjust the preprocessor's
+`bison' parser generator, you may want to adjust the preprocessor's
notion of the current file name and line number by hand. Parts of the
-output from 'bison' are generated from scratch, other parts come from a
-standard parser file. The rest are copied verbatim from 'bison''s
-input. You would like compiler error messages and symbolic debuggers to
-be able to refer to 'bison''s input file.
+output from `bison' are generated from scratch, other parts come from a
+standard parser file. The rest are copied verbatim from `bison''s
+input. You would like compiler error messages and symbolic debuggers
+to be able to refer to `bison''s input file.
- 'bison' or any such program can arrange this by writing '#line'
-directives into the output file. '#line' is a directive that specifies
+ `bison' or any such program can arrange this by writing `#line'
+directives into the output file. `#line' is a directive that specifies
the original line number and source file name for subsequent input in
-the current preprocessor input file. '#line' has three variants:
+the current preprocessor input file. `#line' has three variants:
-'#line LINENUM'
+`#line LINENUM'
LINENUM is a non-negative decimal integer constant. It specifies
the line number which should be reported for the following line of
input. Subsequent lines are counted from LINENUM.
-'#line LINENUM FILENAME'
- LINENUM is the same as for the first form, and has the same effect.
- In addition, FILENAME is a string constant. The following line and
- all subsequent lines are reported to come from the file it
- specifies, until something else happens to change that. FILENAME
- is interpreted according to the normal rules for a string constant:
- backslash escapes are interpreted. This is different from
- '#include'.
+`#line LINENUM FILENAME'
+ LINENUM is the same as for the first form, and has the same
+ effect. In addition, FILENAME is a string constant. The
+ following line and all subsequent lines are reported to come from
+ the file it specifies, until something else happens to change that.
+ FILENAME is interpreted according to the normal rules for a string
+ constant: backslash escapes are interpreted. This is different
+ from `#include'.
- Previous versions of CPP did not interpret escapes in '#line'; we
+ Previous versions of CPP did not interpret escapes in `#line'; we
have changed it because the standard requires they be interpreted,
and most other compilers do.
-'#line ANYTHING ELSE'
+`#line ANYTHING ELSE'
ANYTHING ELSE is checked for macro calls, which are expanded. The
result should match one of the above two forms.
- '#line' directives alter the results of the '__FILE__' and '__LINE__'
-predefined macros from that point on. *Note Standard Predefined
-Macros::. They do not have any effect on '#include''s idea of the
-directory containing the current file. This is a change from GCC 2.95.
-Previously, a file reading
+ `#line' directives alter the results of the `__FILE__' and
+`__LINE__' predefined macros from that point on. *Note Standard
+Predefined Macros::. They do not have any effect on `#include''s idea
+of the directory containing the current file. This is a change from
+GCC 2.95. Previously, a file reading
+ #line 1 "../src/gram.y"
#include "gram.h"
- would search for 'gram.h' in '../src', then the '-I' chain; the
-directory containing the physical source file would not be searched. In
-GCC 3.0 and later, the '#include' is not affected by the presence of a
-'#line' referring to a different directory.
+ would search for `gram.h' in `../src', then the `-I' chain; the
+directory containing the physical source file would not be searched.
+In GCC 3.0 and later, the `#include' is not affected by the presence of
+a `#line' referring to a different directory.
We made this change because the old behavior caused problems when
generated source files were transported between machines. For instance,
it is common practice to ship generated parsers with a source release,
so that people building the distribution do not need to have yacc or
-Bison installed. These files frequently have '#line' directives
+Bison installed. These files frequently have `#line' directives
referring to the directory tree of the system where the distribution was
created. If GCC tries to search for headers in those directories, the
build is likely to fail.
@@ -3230,7 +3249,7 @@ build is likely to fail.
in the same directory as its source and it attempts to include a header
which would be visible searching from the directory containing the
source file. However, this problem is easily solved with an additional
-'-I' switch on the command line. The failures caused by the old
+`-I' switch on the command line. The failures caused by the old
semantics could sometimes be corrected only by editing the generated
files, which is difficult and error-prone.
@@ -3240,48 +3259,48 @@ File: cpp.info, Node: Pragmas, Next: Other Directives, Prev: Line Control, U
7 Pragmas
*********
-The '#pragma' directive is the method specified by the C standard for
+The `#pragma' directive is the method specified by the C standard for
providing additional information to the compiler, beyond what is
conveyed in the language itself. Three forms of this directive
-(commonly known as "pragmas") are specified by the 1999 C standard. A C
-compiler is free to attach any meaning it likes to other pragmas.
+(commonly known as "pragmas") are specified by the 1999 C standard. A
+C compiler is free to attach any meaning it likes to other pragmas.
GCC has historically preferred to use extensions to the syntax of the
-language, such as '__attribute__', for this purpose. However, GCC does
+language, such as `__attribute__', for this purpose. However, GCC does
define a few pragmas of its own. These mostly have effects on the
entire translation unit or source file.
In GCC version 3, all GNU-defined, supported pragmas have been given
-a 'GCC' prefix. This is in line with the 'STDC' prefix on all pragmas
+a `GCC' prefix. This is in line with the `STDC' prefix on all pragmas
defined by C99. For backward compatibility, pragmas which were
-recognized by previous versions are still recognized without the 'GCC'
-prefix, but that usage is deprecated. Some older pragmas are deprecated
-in their entirety. They are not recognized with the 'GCC' prefix.
-*Note Obsolete Features::.
-
- C99 introduces the '_Pragma' operator. This feature addresses a
-major problem with '#pragma': being a directive, it cannot be produced
-as the result of macro expansion. '_Pragma' is an operator, much like
-'sizeof' or 'defined', and can be embedded in a macro.
-
- Its syntax is '_Pragma (STRING-LITERAL)', where STRING-LITERAL can be
-either a normal or wide-character string literal. It is destringized,
-by replacing all '\\' with a single '\' and all '\"' with a '"'. The
-result is then processed as if it had appeared as the right hand side of
-a '#pragma' directive. For example,
+recognized by previous versions are still recognized without the `GCC'
+prefix, but that usage is deprecated. Some older pragmas are
+deprecated in their entirety. They are not recognized with the `GCC'
+prefix. *Note Obsolete Features::.
+
+ C99 introduces the `_Pragma' operator. This feature addresses a
+major problem with `#pragma': being a directive, it cannot be produced
+as the result of macro expansion. `_Pragma' is an operator, much like
+`sizeof' or `defined', and can be embedded in a macro.
+
+ Its syntax is `_Pragma (STRING-LITERAL)', where STRING-LITERAL can
+be either a normal or wide-character string literal. It is
+destringized, by replacing all `\\' with a single `\' and all `\"' with
+a `"'. The result is then processed as if it had appeared as the right
+hand side of a `#pragma' directive. For example,
_Pragma ("GCC dependency \"parse.y\"")
-has the same effect as '#pragma GCC dependency "parse.y"'. The same
+has the same effect as `#pragma GCC dependency "parse.y"'. The same
effect could be achieved using macros, for example
#define DO_PRAGMA(x) _Pragma (#x)
DO_PRAGMA (GCC dependency "parse.y")
- The standard is unclear on where a '_Pragma' operator can appear.
+ The standard is unclear on where a `_Pragma' operator can appear.
The preprocessor does not accept it within a preprocessing conditional
-directive like '#if'. To be safe, you are probably best keeping it out
-of directives other than '#define', and putting it on a line of its own.
+directive like `#if'. To be safe, you are probably best keeping it out
+of directives other than `#define', and putting it on a line of its own.
This manual documents the pragmas which are meaningful to the
preprocessor itself. Other pragmas are meaningful to the C or C++
@@ -3289,8 +3308,8 @@ compilers. They are documented in the GCC manual.
GCC plugins may provide their own pragmas.
-'#pragma GCC dependency'
- '#pragma GCC dependency' allows you to check the relative dates of
+`#pragma GCC dependency'
+ `#pragma GCC dependency' allows you to check the relative dates of
the current file and another file. If the other file is more
recent than the current file, a warning is issued. This is useful
if the current file is derived from the other file, and should be
@@ -3301,11 +3320,11 @@ compilers. They are documented in the GCC manual.
#pragma GCC dependency "parse.y"
#pragma GCC dependency "/usr/include/time.h" rerun fixincludes
-'#pragma GCC poison'
+`#pragma GCC poison'
Sometimes, there is an identifier that you want to remove
completely from your program, and make sure that it never creeps
back in. To enforce this, you can "poison" the identifier with
- this pragma. '#pragma GCC poison' is followed by a list of
+ this pragma. `#pragma GCC poison' is followed by a list of
identifiers to poison. If any of those identifiers appears
anywhere in the source after the directive, it is a hard error.
For example,
@@ -3316,9 +3335,9 @@ compilers. They are documented in the GCC manual.
will produce an error.
If a poisoned identifier appears as part of the expansion of a
- macro which was defined before the identifier was poisoned, it will
- _not_ cause an error. This lets you poison an identifier without
- worrying about system headers defining macros that use it.
+ macro which was defined before the identifier was poisoned, it
+ will _not_ cause an error. This lets you poison an identifier
+ without worrying about system headers defining macros that use it.
For example,
@@ -3328,19 +3347,20 @@ compilers. They are documented in the GCC manual.
will not produce an error.
-'#pragma GCC system_header'
+`#pragma GCC system_header'
This pragma takes no arguments. It causes the rest of the code in
the current file to be treated as if it came from a system header.
*Note System Headers::.
-'#pragma GCC warning'
-'#pragma GCC error'
- '#pragma GCC warning "message"' causes the preprocessor to issue a
- warning diagnostic with the text 'message'. The message contained
- in the pragma must be a single string literal. Similarly, '#pragma
- GCC error "message"' issues an error message. Unlike the
- '#warning' and '#error' directives, these pragmas can be embedded
- in preprocessor macros using '_Pragma'.
+`#pragma GCC warning'
+`#pragma GCC error'
+ `#pragma GCC warning "message"' causes the preprocessor to issue a
+ warning diagnostic with the text `message'. The message contained
+ in the pragma must be a single string literal. Similarly,
+ `#pragma GCC error "message"' issues an error message. Unlike the
+ `#warning' and `#error' directives, these pragmas can be embedded
+ in preprocessor macros using `_Pragma'.
+

File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Pragmas, Up: Top
@@ -3348,21 +3368,21 @@ File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Prag
8 Other Directives
******************
-The '#ident' directive takes one argument, a string constant. On some
+The `#ident' directive takes one argument, a string constant. On some
systems, that string constant is copied into a special segment of the
-object file. On other systems, the directive is ignored. The '#sccs'
-directive is a synonym for '#ident'.
+object file. On other systems, the directive is ignored. The `#sccs'
+directive is a synonym for `#ident'.
These directives are not part of the C standard, but they are not
official GNU extensions either. What historical information we have
been able to find, suggests they originated with System V.
- The "null directive" consists of a '#' followed by a newline, with
+ The "null directive" consists of a `#' followed by a newline, with
only whitespace (including comments) in between. A null directive is
understood as a preprocessing directive but has no effect on the
preprocessor output. The primary significance of the existence of the
-null directive is that an input line consisting of just a '#' will
-produce no output, rather than a line of output containing just a '#'.
+null directive is that an input line consisting of just a `#' will
+produce no output, rather than a line of output containing just a `#'.
Supposedly some old C programs contain such lines.

@@ -3404,36 +3424,39 @@ that the following line originated in file FILENAME at line LINENUM.
FILENAME will never contain any non-printing characters; they are
replaced with octal escape sequences.
- After the file name comes zero or more flags, which are '1', '2',
-'3', or '4'. If there are multiple flags, spaces separate them. Here
+ After the file name comes zero or more flags, which are `1', `2',
+`3', or `4'. If there are multiple flags, spaces separate them. Here
is what the flags mean:
-'1'
+`1'
This indicates the start of a new file.
-'2'
+
+`2'
This indicates returning to a file (after having included another
file).
-'3'
+
+`3'
This indicates that the following text comes from a system header
file, so certain warnings should be suppressed.
-'4'
+
+`4'
This indicates that the following text should be treated as being
- wrapped in an implicit 'extern "C"' block.
+ wrapped in an implicit `extern "C"' block.
As an extension, the preprocessor accepts linemarkers in
non-assembler input files. They are treated like the corresponding
-'#line' directive, (*note Line Control::), except that trailing flags
+`#line' directive, (*note Line Control::), except that trailing flags
are permitted, and are interpreted with the meanings described above.
If multiple flags are given, they must be in ascending order.
Some directives may be duplicated in the output of the preprocessor.
-These are '#ident' (always), '#pragma' (only if the preprocessor does
-not handle the pragma itself), and '#define' and '#undef' (with certain
-debugging options). If this happens, the '#' of the directive will
+These are `#ident' (always), `#pragma' (only if the preprocessor does
+not handle the pragma itself), and `#define' and `#undef' (with certain
+debugging options). If this happens, the `#' of the directive will
always be in the first column, and there will be no space between the
-'#' and the directive name. If macro expansion happens to generate
+`#' and the directive name. If macro expansion happens to generate
tokens which might be mistaken for a duplicated directive, a space will
-be inserted between the '#' and the directive name.
+be inserted between the `#' and the directive name.

File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: Preprocessor Output, Up: Top
@@ -3443,7 +3466,7 @@ File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: P
Traditional (pre-standard) C preprocessing is rather different from the
preprocessing specified by the standard. When GCC is given the
-'-traditional-cpp' option, it attempts to emulate a traditional
+`-traditional-cpp' option, it attempts to emulate a traditional
preprocessor.
GCC versions 3.2 and later only support traditional mode semantics in
@@ -3476,30 +3499,31 @@ simply treated as a stream of text with minimal internal form.
This implementation does not treat trigraphs (*note trigraphs::)
specially since they were an invention of the standards committee. It
-handles arbitrarily-positioned escaped newlines properly and splices the
-lines as you would expect; many traditional preprocessors did not do
-this.
+handles arbitrarily-positioned escaped newlines properly and splices
+the lines as you would expect; many traditional preprocessors did not
+do this.
The form of horizontal whitespace in the input file is preserved in
the output. In particular, hard tabs remain hard tabs. This can be
useful if, for example, you are preprocessing a Makefile.
Traditional CPP only recognizes C-style block comments, and treats
-the '/*' sequence as introducing a comment only if it lies outside
+the `/*' sequence as introducing a comment only if it lies outside
quoted text. Quoted text is introduced by the usual single and double
-quotes, and also by an initial '<' in a '#include' directive.
+quotes, and also by an initial `<' in a `#include' directive.
Traditionally, comments are completely removed and are not replaced
-with a space. Since a traditional compiler does its own tokenization of
-the output of the preprocessor, this means that comments can effectively
-be used as token paste operators. However, comments behave like
-separators for text handled by the preprocessor itself, since it doesn't
-re-lex its input. For example, in
+with a space. Since a traditional compiler does its own tokenization
+of the output of the preprocessor, this means that comments can
+effectively be used as token paste operators. However, comments behave
+like separators for text handled by the preprocessor itself, since it
+doesn't re-lex its input. For example, in
#if foo/**/bar
-'foo' and 'bar' are distinct identifiers and expanded separately if they
-happen to be macros. In other words, this directive is equivalent to
+`foo' and `bar' are distinct identifiers and expanded separately if
+they happen to be macros. In other words, this directive is equivalent
+to
#if foo bar
@@ -3513,7 +3537,7 @@ with replacement text that contains an unmatched quote. Of course, if
you attempt to compile preprocessed output containing an unmatched quote
you will get a syntax error.
- However, all preprocessing directives other than '#define' require
+ However, all preprocessing directives other than `#define' require
matching quotes. For example:
#define m This macro's fine and has an unmatched quote
@@ -3544,16 +3568,16 @@ can run together with the text after the macro invocation to produce a
single token.
Normally comments are removed from the replacement text after the
-macro is expanded, but if the '-CC' option is passed on the command-line
-comments are preserved. (In fact, the current implementation removes
-comments even before saving the macro replacement text, but it careful
-to do it in such a way that the observed effect is identical even in the
-function-like macro case.)
-
- The ISO stringification operator '#' and token paste operator '##'
-have no special meaning. As explained later, an effect similar to these
-operators can be obtained in a different way. Macro names that are
-embedded in quotes, either from the main file or after macro
+macro is expanded, but if the `-CC' option is passed on the
+command-line comments are preserved. (In fact, the current
+implementation removes comments even before saving the macro
+replacement text, but it careful to do it in such a way that the
+observed effect is identical even in the function-like macro case.)
+
+ The ISO stringification operator `#' and token paste operator `##'
+have no special meaning. As explained later, an effect similar to
+these operators can be obtained in a different way. Macro names that
+are embedded in quotes, either from the main file or after macro
replacement, do not expand.
CPP replaces an unquoted object-like macro name with its replacement
@@ -3573,22 +3597,23 @@ invocation.
Function-like macros are similar in form but quite different in
behavior to their ISO counterparts. Their arguments are contained
within parentheses, are comma-separated, and can cross physical lines.
-Commas within nested parentheses are not treated as argument separators.
-Similarly, a quote in an argument cannot be left unclosed; a following
-comma or parenthesis that comes before the closing quote is treated like
-any other character. There is no facility for handling variadic macros.
+Commas within nested parentheses are not treated as argument
+separators. Similarly, a quote in an argument cannot be left unclosed;
+a following comma or parenthesis that comes before the closing quote is
+treated like any other character. There is no facility for handling
+variadic macros.
This implementation removes all comments from macro arguments, unless
-the '-C' option is given. The form of all other horizontal whitespace
+the `-C' option is given. The form of all other horizontal whitespace
in arguments is preserved, including leading and trailing whitespace.
In particular
f( )
-is treated as an invocation of the macro 'f' with a single argument
+is treated as an invocation of the macro `f' with a single argument
consisting of a single space. If you want to invoke a function-like
-macro that takes no arguments, you must not leave any whitespace between
-the parentheses.
+macro that takes no arguments, you must not leave any whitespace
+between the parentheses.
If a macro argument crosses a new line, the new line is replaced with
a space when forming the argument. If the previous line contained an
@@ -3619,16 +3644,16 @@ File: cpp.info, Node: Traditional miscellany, Next: Traditional warnings, Pre
Here are some things to be aware of when using the traditional
preprocessor.
- * Preprocessing directives are recognized only when their leading '#'
- appears in the first column. There can be no whitespace between
- the beginning of the line and the '#', but whitespace can follow
- the '#'.
+ * Preprocessing directives are recognized only when their leading
+ `#' appears in the first column. There can be no whitespace
+ between the beginning of the line and the `#', but whitespace can
+ follow the `#'.
- * A true traditional C preprocessor does not recognize '#error' or
- '#pragma', and may not recognize '#elif'. CPP supports all the
+ * A true traditional C preprocessor does not recognize `#error' or
+ `#pragma', and may not recognize `#elif'. CPP supports all the
directives in traditional mode that it supports in ISO mode,
including extensions, with the exception that the effects of
- '#pragma GCC poison' are undefined.
+ `#pragma GCC poison' are undefined.
* __STDC__ is not defined.
@@ -3637,6 +3662,7 @@ preprocessor.
* If a line that looks like a directive appears within macro
arguments, the behavior is undefined.
+

File: cpp.info, Node: Traditional warnings, Prev: Traditional miscellany, Up: Traditional Mode
@@ -3644,24 +3670,24 @@ File: cpp.info, Node: Traditional warnings, Prev: Traditional miscellany, Up:
=========================
You can request warnings about features that did not exist, or worked
-differently, in traditional C with the '-Wtraditional' option. GCC does
-not warn about features of ISO C which you must use when you are using a
-conforming compiler, such as the '#' and '##' operators.
+differently, in traditional C with the `-Wtraditional' option. GCC
+does not warn about features of ISO C which you must use when you are
+using a conforming compiler, such as the `#' and `##' operators.
- Presently '-Wtraditional' warns about:
+ Presently `-Wtraditional' warns about:
* Macro parameters that appear within string literals in the macro
- body. In traditional C macro replacement takes place within string
- literals, but does not in ISO C.
+ body. In traditional C macro replacement takes place within
+ string literals, but does not in ISO C.
* In traditional C, some preprocessor directives did not exist.
Traditional preprocessors would only consider a line to be a
- directive if the '#' appeared in column 1 on the line. Therefore
- '-Wtraditional' warns about directives that traditional C
- understands but would ignore because the '#' does not appear as the
+ directive if the `#' appeared in column 1 on the line. Therefore
+ `-Wtraditional' warns about directives that traditional C
+ understands but would ignore because the `#' does not appear as the
first character on the line. It also suggests you hide directives
- like '#pragma' not understood by traditional C by indenting them.
- Some traditional implementations would not recognize '#elif', so it
+ like `#pragma' not understood by traditional C by indenting them.
+ Some traditional implementations would not recognize `#elif', so it
suggests avoiding it altogether.
* A function-like macro that appears without an argument list. In
@@ -3670,12 +3696,12 @@ conforming compiler, such as the '#' and '##' operators.
* The unary plus operator. This did not exist in traditional C.
- * The 'U' and 'LL' integer constant suffixes, which were not
- available in traditional C. (Traditional C does support the 'L'
+ * The `U' and `LL' integer constant suffixes, which were not
+ available in traditional C. (Traditional C does support the `L'
suffix for simple long integer constants.) You are not warned
about uses of these suffixes in macros defined in system headers.
- For instance, 'UINT_MAX' may well be defined as '4294967295U', but
- you will not be warned if you use 'UINT_MAX'.
+ For instance, `UINT_MAX' may well be defined as `4294967295U', but
+ you will not be warned if you use `UINT_MAX'.
You can usually avoid the warning, and the related warning about
constants which are so large that they are unsigned, by writing the
@@ -3711,68 +3737,67 @@ File: cpp.info, Node: Implementation-defined behavior, Next: Implementation li
====================================
This is how CPP behaves in all the cases which the C standard describes
-as "implementation-defined". This term means that the implementation is
-free to do what it likes, but must document its choice and stick to it.
+as "implementation-defined". This term means that the implementation
+is free to do what it likes, but must document its choice and stick to
+it.
* The mapping of physical source file multi-byte characters to the
execution character set.
The input character set can be specified using the
- '-finput-charset' option, while the execution character set may be
- controlled using the '-fexec-charset' and '-fwide-exec-charset'
+ `-finput-charset' option, while the execution character set may be
+ controlled using the `-fexec-charset' and `-fwide-exec-charset'
options.
- * Identifier characters.
+ * Identifier characters. The C and C++ standards allow identifiers
+ to be composed of `_' and the alphanumeric characters. C++ and
+ C99 also allow universal character names, and C99 further permits
+ implementation-defined characters.
- The C and C++ standards allow identifiers to be composed of '_' and
- the alphanumeric characters. C++ and C99 also allow universal
- character names, and C99 further permits implementation-defined
- characters.
-
- GCC allows the '$' character in identifiers as an extension for
- most targets. This is true regardless of the 'std=' switch, since
+ GCC allows the `$' character in identifiers as an extension for
+ most targets. This is true regardless of the `std=' switch, since
this extension cannot conflict with standards-conforming programs.
When preprocessing assembler, however, dollars are not identifier
characters by default.
- Currently the targets that by default do not permit '$' are AVR,
+ Currently the targets that by default do not permit `$' are AVR,
IP2K, MMIX, MIPS Irix 3, ARM aout, and PowerPC targets for the AIX
operating system.
- You can override the default with '-fdollars-in-identifiers' or
- 'fno-dollars-in-identifiers'. *Note fdollars-in-identifiers::.
+ You can override the default with `-fdollars-in-identifiers' or
+ `fno-dollars-in-identifiers'. *Note fdollars-in-identifiers::.
* Non-empty sequences of whitespace characters.
In textual output, each whitespace sequence is collapsed to a
single space. For aesthetic reasons, the first token on each
non-directive line of output is preceded with sufficient spaces
- that it appears in the same column as it did in the original source
- file.
+ that it appears in the same column as it did in the original
+ source file.
* The numeric value of character constants in preprocessor
expressions.
The preprocessor and compiler interpret character constants in the
- same way; i.e. escape sequences such as '\a' are given the values
+ same way; i.e. escape sequences such as `\a' are given the values
they would have on the target machine.
The compiler evaluates a multi-character character constant a
- character at a time, shifting the previous value left by the number
- of bits per target character, and then or-ing in the bit-pattern of
- the new character truncated to the width of a target character.
- The final bit-pattern is given type 'int', and is therefore signed,
- regardless of whether single characters are signed or not (a slight
- change from versions 3.1 and earlier of GCC). If there are more
- characters in the constant than would fit in the target 'int' the
- compiler issues a warning, and the excess leading characters are
- ignored.
-
- For example, ''ab'' for a target with an 8-bit 'char' would be
+ character at a time, shifting the previous value left by the
+ number of bits per target character, and then or-ing in the
+ bit-pattern of the new character truncated to the width of a
+ target character. The final bit-pattern is given type `int', and
+ is therefore signed, regardless of whether single characters are
+ signed or not (a slight change from versions 3.1 and earlier of
+ GCC). If there are more characters in the constant than would fit
+ in the target `int' the compiler issues a warning, and the excess
+ leading characters are ignored.
+
+ For example, `'ab'' for a target with an 8-bit `char' would be
interpreted as
- '(int) ((unsigned char) 'a' * 256 + (unsigned char) 'b')', and
- ''\234a'' as
- '(int) ((unsigned char) '\234' * 256 + (unsigned char) 'a')'.
+ `(int) ((unsigned char) 'a' * 256 + (unsigned char) 'b')', and
+ `'\234a'' as
+ `(int) ((unsigned char) '\234' * 256 + (unsigned char) 'a')'.
* Source file inclusion.
@@ -3780,18 +3805,19 @@ free to do what it likes, but must document its choice and stick to it.
*note Include Operation::.
* Interpretation of the filename resulting from a macro-expanded
- '#include' directive.
+ `#include' directive.
*Note Computed Includes::.
- * Treatment of a '#pragma' directive that after macro-expansion
+ * Treatment of a `#pragma' directive that after macro-expansion
results in a standard pragma.
- No macro expansion occurs on any '#pragma' directive line, so the
+ No macro expansion occurs on any `#pragma' directive line, so the
question does not arise.
Note that GCC does not yet implement any of the standard pragmas.
+

File: cpp.info, Node: Implementation limits, Next: Obsolete Features, Prev: Implementation-defined behavior, Up: Implementation Details
@@ -3806,12 +3832,12 @@ limit, please report that as a bug. *Note Reporting Bugs: (gcc)Bugs.
Where we say something is limited "only by available memory", that
means that internal data structures impose no intrinsic limit, and space
-is allocated with 'malloc' or equivalent. The actual limit will
+is allocated with `malloc' or equivalent. The actual limit will
therefore depend on many things, such as the size of other things
allocated by the compiler at the same time, the amount of memory
consumed by other processes on the same computer, etc.
- * Nesting levels of '#include' files.
+ * Nesting levels of `#include' files.
We impose an arbitrary limit of 200 levels, to avoid runaway
recursion. The standard requires at least 15 levels.
@@ -3837,10 +3863,10 @@ consumed by other processes on the same computer, etc.
The standard requires at least 4095 be possible. CPP is limited
only by available memory.
- * Number of parameters in a macro definition and arguments in a macro
- call.
+ * Number of parameters in a macro definition and arguments in a
+ macro call.
- We allow 'USHRT_MAX', which is no smaller than 65,535. The minimum
+ We allow `USHRT_MAX', which is no smaller than 65,535. The minimum
required by the standard is 127.
* Number of characters on a logical source line.
@@ -3852,10 +3878,11 @@ consumed by other processes on the same computer, etc.
* Maximum size of a source file.
The standard does not specify any lower limit on the maximum size
- of a source file. GNU cpp maps files into memory, so it is limited
- by the available address space. This is generally at least two
- gigabytes. Depending on the operating system, the size of physical
- memory may or may not be a limitation.
+ of a source file. GNU cpp maps files into memory, so it is
+ limited by the available address space. This is generally at
+ least two gigabytes. Depending on the operating system, the size
+ of physical memory may or may not be a limitation.
+

File: cpp.info, Node: Obsolete Features, Next: Differences from previous versions, Prev: Implementation limits, Up: Implementation Details
@@ -3864,8 +3891,8 @@ File: cpp.info, Node: Obsolete Features, Next: Differences from previous versi
======================
CPP has some features which are present mainly for compatibility with
-older programs. We discourage their use in new code. In some cases, we
-plan to remove the feature in a future version of GCC.
+older programs. We discourage their use in new code. In some cases,
+we plan to remove the feature in a future version of GCC.
11.3.1 Assertions
-----------------
@@ -3879,8 +3906,8 @@ define them with preprocessing directives or command-line options.
the compiler's target system and we added them for compatibility with
existing compilers. In practice they are just as unpredictable as the
system-specific predefined macros. In addition, they are not part of
-any standard, and only a few compilers support them. Therefore, the use
-of assertions is *less* portable than the use of system-specific
+any standard, and only a few compilers support them. Therefore, the
+use of assertions is *less* portable than the use of system-specific
predefined macros. We recommend you do not use them at all.
An assertion looks like this:
@@ -3891,12 +3918,12 @@ PREDICATE must be a single identifier. ANSWER can be any sequence of
tokens; all characters are significant except for leading and trailing
whitespace, and differences in internal whitespace sequences are
ignored. (This is similar to the rules governing macro redefinition.)
-Thus, '(x + y)' is different from '(x+y)' but equivalent to '( x + y )'.
-Parentheses do not nest inside an answer.
+Thus, `(x + y)' is different from `(x+y)' but equivalent to
+`( x + y )'. Parentheses do not nest inside an answer.
- To test an assertion, you write it in an '#if'. For example, this
-conditional succeeds if either 'vax' or 'ns16000' has been asserted as
-an answer for 'machine'.
+ To test an assertion, you write it in an `#if'. For example, this
+conditional succeeds if either `vax' or `ns16000' has been asserted as
+an answer for `machine'.
#if #machine (vax) || #machine (ns16000)
@@ -3905,8 +3932,8 @@ omitting the answer in the conditional:
#if #machine
- Assertions are made with the '#assert' directive. Its sole argument
-is the assertion to make, without the leading '#' that identifies
+ Assertions are made with the `#assert' directive. Its sole argument
+is the assertion to make, without the leading `#' that identifies
assertions in conditionals.
#assert PREDICATE (ANSWER)
@@ -3916,15 +3943,15 @@ answers. Subsequent assertions do not override previous ones for the
same predicate. All the answers for any given predicate are
simultaneously true.
- Assertions can be canceled with the '#unassert' directive. It has
-the same syntax as '#assert'. In that form it cancels only the answer
-which was specified on the '#unassert' line; other answers for that
+ Assertions can be canceled with the `#unassert' directive. It has
+the same syntax as `#assert'. In that form it cancels only the answer
+which was specified on the `#unassert' line; other answers for that
predicate remain true. You can cancel an entire predicate by leaving
out the answer:
#unassert PREDICATE
-In either form, if no such assertion has been made, '#unassert' has no
+In either form, if no such assertion has been made, `#unassert' has no
effect.
You can also make or cancel assertions using command-line options.
@@ -3937,8 +3964,8 @@ File: cpp.info, Node: Differences from previous versions, Prev: Obsolete Featu
=======================================
This section details behavior which has changed from previous versions
-of CPP. We do not plan to change it again in the near future, but we do
-not promise not to, either.
+of CPP. We do not plan to change it again in the near future, but we
+do not promise not to, either.
The "previous versions" discussed here are 2.95 and before. The
behavior of GCC 3.0 is mostly the same as the behavior of the widely
@@ -3947,48 +3974,48 @@ they generally represent bugs in the snapshots.
* -I- deprecated
- This option has been deprecated in 4.0. '-iquote' is meant to
+ This option has been deprecated in 4.0. `-iquote' is meant to
replace the need for this option.
- * Order of evaluation of '#' and '##' operators
+ * Order of evaluation of `#' and `##' operators
The standard does not specify the order of evaluation of a chain of
- '##' operators, nor whether '#' is evaluated before, after, or at
- the same time as '##'. You should therefore not write any code
+ `##' operators, nor whether `#' is evaluated before, after, or at
+ the same time as `##'. You should therefore not write any code
which depends on any specific ordering. It is possible to
guarantee an ordering, if you need one, by suitable use of nested
macros.
- An example of where this might matter is pasting the arguments '1',
- 'e' and '-2'. This would be fine for left-to-right pasting, but
- right-to-left pasting would produce an invalid token 'e-2'.
+ An example of where this might matter is pasting the arguments `1',
+ `e' and `-2'. This would be fine for left-to-right pasting, but
+ right-to-left pasting would produce an invalid token `e-2'.
- GCC 3.0 evaluates '#' and '##' at the same time and strictly left
- to right. Older versions evaluated all '#' operators first, then
- all '##' operators, in an unreliable order.
+ GCC 3.0 evaluates `#' and `##' at the same time and strictly left
+ to right. Older versions evaluated all `#' operators first, then
+ all `##' operators, in an unreliable order.
* The form of whitespace between tokens in preprocessor output
*Note Preprocessor Output::, for the current textual format. This
is also the format used by stringification. Normally, the
- preprocessor communicates tokens directly to the compiler's parser,
- and whitespace does not come up at all.
+ preprocessor communicates tokens directly to the compiler's
+ parser, and whitespace does not come up at all.
- Older versions of GCC preserved all whitespace provided by the user
- and inserted lots more whitespace of their own, because they could
- not accurately predict when extra spaces were needed to prevent
- accidental token pasting.
+ Older versions of GCC preserved all whitespace provided by the
+ user and inserted lots more whitespace of their own, because they
+ could not accurately predict when extra spaces were needed to
+ prevent accidental token pasting.
* Optional argument when invoking rest argument macros
As an extension, GCC permits you to omit the variable arguments
- entirely when you use a variable argument macro. This is forbidden
- by the 1999 C standard, and will provoke a pedantic warning with
- GCC 3.0. Previous versions accepted it silently.
+ entirely when you use a variable argument macro. This is
+ forbidden by the 1999 C standard, and will provoke a pedantic
+ warning with GCC 3.0. Previous versions accepted it silently.
- * '##' swallowing preceding text in rest argument macros
+ * `##' swallowing preceding text in rest argument macros
- Formerly, in a macro expansion, if '##' appeared before a variable
+ Formerly, in a macro expansion, if `##' appeared before a variable
arguments parameter, and the set of tokens specified for that
argument in the macro invocation was empty, previous versions of
CPP would back up and remove the preceding sequence of
@@ -3996,29 +4023,31 @@ they generally represent bugs in the snapshots.
extension is in direct conflict with the 1999 C standard and has
been drastically pared back.
- In the current version of the preprocessor, if '##' appears between
+ In the current version of the preprocessor, if `##' appears between
a comma and a variable arguments parameter, and the variable
argument is omitted entirely, the comma will be removed from the
expansion. If the variable argument is empty, or the token before
- '##' is not a comma, then '##' behaves as a normal token paste.
+ `##' is not a comma, then `##' behaves as a normal token paste.
- * '#line' and '#include'
+ * `#line' and `#include'
- The '#line' directive used to change GCC's notion of the "directory
- containing the current file", used by '#include' with a
+ The `#line' directive used to change GCC's notion of the
+ "directory containing the current file", used by `#include' with a
double-quoted header file name. In 3.0 and later, it does not.
*Note Line Control::, for further explanation.
- * Syntax of '#line'
+ * Syntax of `#line'
- In GCC 2.95 and previous, the string constant argument to '#line'
- was treated the same way as the argument to '#include': backslash
- escapes were not honored, and the string ended at the second '"'.
+ In GCC 2.95 and previous, the string constant argument to `#line'
+ was treated the same way as the argument to `#include': backslash
+ escapes were not honored, and the string ended at the second `"'.
This is not compliant with the C standard. In GCC 3.0, an attempt
- was made to correct the behavior, so that the string was treated as
- a real string constant, but it turned out to be buggy. In 3.1, the
- bugs have been fixed. (We are not fixing the bugs in 3.0 because
- they affect relatively few people and the fix is quite invasive.)
+ was made to correct the behavior, so that the string was treated
+ as a real string constant, but it turned out to be buggy. In 3.1,
+ the bugs have been fixed. (We are not fixing the bugs in 3.0
+ because they affect relatively few people and the fix is quite
+ invasive.)
+

File: cpp.info, Node: Invocation, Next: Environment Variables, Prev: Implementation Details, Up: Top
@@ -4033,39 +4062,39 @@ here are also acceptable to the C compiler and have the same meaning,
except that the C compiler has different rules for specifying the output
file.
- _Note:_ Whether you use the preprocessor by way of 'gcc' or 'cpp',
+ _Note:_ Whether you use the preprocessor by way of `gcc' or `cpp',
the "compiler driver" is run first. This program's purpose is to
translate your command into invocations of the programs that do the
actual work. Their command-line interfaces are similar but not
identical to the documented interface, and may change without notice.
The C preprocessor expects two file names as arguments, INFILE and
-OUTFILE. The preprocessor reads INFILE together with any other files it
-specifies with '#include'. All the output generated by the combined
+OUTFILE. The preprocessor reads INFILE together with any other files
+it specifies with `#include'. All the output generated by the combined
input files is written in OUTFILE.
- Either INFILE or OUTFILE may be '-', which as INFILE means to read
+ Either INFILE or OUTFILE may be `-', which as INFILE means to read
from standard input and as OUTFILE means to write to standard output.
-Also, if either file is omitted, it means the same as if '-' had been
+Also, if either file is omitted, it means the same as if `-' had been
specified for that file.
- Unless otherwise noted, or the option ends in '=', all options which
+ Unless otherwise noted, or the option ends in `=', all options which
take an argument may have that argument appear either immediately after
-the option, or with a space between option and argument: '-Ifoo' and '-I
-foo' have the same effect.
+the option, or with a space between option and argument: `-Ifoo' and
+`-I foo' have the same effect.
Many options have multi-letter names; therefore multiple
-single-letter options may _not_ be grouped: '-dM' is very different from
-'-d -M'.
+single-letter options may _not_ be grouped: `-dM' is very different from
+`-d -M'.
-'-D NAME'
- Predefine NAME as a macro, with definition '1'.
+`-D NAME'
+ Predefine NAME as a macro, with definition `1'.
-'-D NAME=DEFINITION'
+`-D NAME=DEFINITION'
The contents of DEFINITION are tokenized and processed as if they
- appeared during translation phase three in a '#define' directive.
- In particular, the definition will be truncated by embedded newline
- characters.
+ appeared during translation phase three in a `#define' directive.
+ In particular, the definition will be truncated by embedded
+ newline characters.
If you are invoking the preprocessor from a shell or shell-like
program you may need to use the shell's quoting syntax to protect
@@ -4074,76 +4103,76 @@ single-letter options may _not_ be grouped: '-dM' is very different from
If you wish to define a function-like macro on the command line,
write its argument list with surrounding parentheses before the
equals sign (if any). Parentheses are meaningful to most shells,
- so you will need to quote the option. With 'sh' and 'csh',
- '-D'NAME(ARGS...)=DEFINITION'' works.
+ so you will need to quote the option. With `sh' and `csh',
+ `-D'NAME(ARGS...)=DEFINITION'' works.
- '-D' and '-U' options are processed in the order they are given on
- the command line. All '-imacros FILE' and '-include FILE' options
- are processed after all '-D' and '-U' options.
+ `-D' and `-U' options are processed in the order they are given on
+ the command line. All `-imacros FILE' and `-include FILE' options
+ are processed after all `-D' and `-U' options.
-'-U NAME'
- Cancel any previous definition of NAME, either built in or provided
- with a '-D' option.
+`-U NAME'
+ Cancel any previous definition of NAME, either built in or
+ provided with a `-D' option.
-'-undef'
+`-undef'
Do not predefine any system-specific or GCC-specific macros. The
standard predefined macros remain defined. *Note Standard
Predefined Macros::.
-'-I DIR'
- Add the directory DIR to the list of directories to be searched for
- header files. *Note Search Path::. Directories named by '-I' are
- searched before the standard system include directories. If the
- directory DIR is a standard system include directory, the option is
- ignored to ensure that the default search order for system
- directories and the special treatment of system headers are not
- defeated (*note System Headers::) . If DIR begins with '=', then
- the '=' will be replaced by the sysroot prefix; see '--sysroot' and
- '-isysroot'.
-
-'-o FILE'
+`-I DIR'
+ Add the directory DIR to the list of directories to be searched
+ for header files. *Note Search Path::. Directories named by `-I'
+ are searched before the standard system include directories. If
+ the directory DIR is a standard system include directory, the
+ option is ignored to ensure that the default search order for
+ system directories and the special treatment of system headers are
+ not defeated (*note System Headers::) . If DIR begins with `=',
+ then the `=' will be replaced by the sysroot prefix; see
+ `--sysroot' and `-isysroot'.
+
+`-o FILE'
Write output to FILE. This is the same as specifying FILE as the
- second non-option argument to 'cpp'. 'gcc' has a different
+ second non-option argument to `cpp'. `gcc' has a different
interpretation of a second non-option argument, so you must use
- '-o' to specify the output file.
+ `-o' to specify the output file.
-'-Wall'
+`-Wall'
Turns on all optional warnings which are desirable for normal code.
- At present this is '-Wcomment', '-Wtrigraphs', '-Wmultichar' and a
- warning about integer promotion causing a change of sign in '#if'
+ At present this is `-Wcomment', `-Wtrigraphs', `-Wmultichar' and a
+ warning about integer promotion causing a change of sign in `#if'
expressions. Note that many of the preprocessor's warnings are on
by default and have no options to control them.
-'-Wcomment'
-'-Wcomments'
- Warn whenever a comment-start sequence '/*' appears in a '/*'
- comment, or whenever a backslash-newline appears in a '//' comment.
+`-Wcomment'
+`-Wcomments'
+ Warn whenever a comment-start sequence `/*' appears in a `/*'
+ comment, or whenever a backslash-newline appears in a `//' comment.
(Both forms have the same effect.)
-'-Wtrigraphs'
+`-Wtrigraphs'
Most trigraphs in comments cannot affect the meaning of the
program. However, a trigraph that would form an escaped newline
- ('??/' at the end of a line) can, by changing where the comment
+ (`??/' at the end of a line) can, by changing where the comment
begins or ends. Therefore, only trigraphs that would form escaped
newlines produce warnings inside a comment.
- This option is implied by '-Wall'. If '-Wall' is not given, this
+ This option is implied by `-Wall'. If `-Wall' is not given, this
option is still enabled unless trigraphs are enabled. To get
- trigraph conversion without warnings, but get the other '-Wall'
- warnings, use '-trigraphs -Wall -Wno-trigraphs'.
+ trigraph conversion without warnings, but get the other `-Wall'
+ warnings, use `-trigraphs -Wall -Wno-trigraphs'.
-'-Wtraditional'
+`-Wtraditional'
Warn about certain constructs that behave differently in
traditional and ISO C. Also warn about ISO C constructs that have
no traditional C equivalent, and problematic constructs which
should be avoided. *Note Traditional Mode::.
-'-Wundef'
+`-Wundef'
Warn whenever an identifier which is not a macro is encountered in
- an '#if' directive, outside of 'defined'. Such identifiers are
+ an `#if' directive, outside of `defined'. Such identifiers are
replaced with zero.
-'-Wunused-macros'
+`-Wunused-macros'
Warn about macros defined in the main file that are unused. A
macro is "used" if it is expanded or tested for existence at least
once. The preprocessor will also warn if the macro has not been
@@ -4162,9 +4191,9 @@ single-letter options may _not_ be grouped: '-dM' is very different from
#if defined the_macro_causing_the_warning
#endif
-'-Wendif-labels'
- Warn whenever an '#else' or an '#endif' are followed by text. This
- usually happens in code of the form
+`-Wendif-labels'
+ Warn whenever an `#else' or an `#endif' are followed by text.
+ This usually happens in code of the form
#if FOO
...
@@ -4172,92 +4201,92 @@ single-letter options may _not_ be grouped: '-dM' is very different from
...
#endif FOO
- The second and third 'FOO' should be in comments, but often are not
+ The second and third `FOO' should be in comments, but often are not
in older programs. This warning is on by default.
-'-Werror'
+`-Werror'
Make all warnings into hard errors. Source code which triggers
warnings will be rejected.
-'-Wsystem-headers'
+`-Wsystem-headers'
Issue warnings for code in system headers. These are normally
unhelpful in finding bugs in your own code, therefore suppressed.
If you are responsible for the system library, you may want to see
them.
-'-w'
+`-w'
Suppress all warnings, including those which GNU CPP issues by
default.
-'-pedantic'
- Issue all the mandatory diagnostics listed in the C standard. Some
- of them are left out by default, since they trigger frequently on
- harmless code.
+`-pedantic'
+ Issue all the mandatory diagnostics listed in the C standard.
+ Some of them are left out by default, since they trigger
+ frequently on harmless code.
-'-pedantic-errors'
+`-pedantic-errors'
Issue all the mandatory diagnostics, and make all mandatory
diagnostics into errors. This includes mandatory diagnostics that
- GCC issues without '-pedantic' but treats as warnings.
+ GCC issues without `-pedantic' but treats as warnings.
-'-M'
+`-M'
Instead of outputting the result of preprocessing, output a rule
- suitable for 'make' describing the dependencies of the main source
- file. The preprocessor outputs one 'make' rule containing the
+ suitable for `make' describing the dependencies of the main source
+ file. The preprocessor outputs one `make' rule containing the
object file name for that source file, a colon, and the names of
- all the included files, including those coming from '-include' or
- '-imacros' command-line options.
+ all the included files, including those coming from `-include' or
+ `-imacros' command-line options.
- Unless specified explicitly (with '-MT' or '-MQ'), the object file
+ Unless specified explicitly (with `-MT' or `-MQ'), the object file
name consists of the name of the source file with any suffix
replaced with object file suffix and with any leading directory
parts removed. If there are many included files then the rule is
- split into several lines using '\'-newline. The rule has no
+ split into several lines using `\'-newline. The rule has no
commands.
- This option does not suppress the preprocessor's debug output, such
- as '-dM'. To avoid mixing such debug output with the dependency
- rules you should explicitly specify the dependency output file with
- '-MF', or use an environment variable like 'DEPENDENCIES_OUTPUT'
- (*note Environment Variables::). Debug output will still be sent
- to the regular output stream as normal.
+ This option does not suppress the preprocessor's debug output,
+ such as `-dM'. To avoid mixing such debug output with the
+ dependency rules you should explicitly specify the dependency
+ output file with `-MF', or use an environment variable like
+ `DEPENDENCIES_OUTPUT' (*note Environment Variables::). Debug
+ output will still be sent to the regular output stream as normal.
- Passing '-M' to the driver implies '-E', and suppresses warnings
- with an implicit '-w'.
+ Passing `-M' to the driver implies `-E', and suppresses warnings
+ with an implicit `-w'.
-'-MM'
- Like '-M' but do not mention header files that are found in system
- header directories, nor header files that are included, directly or
- indirectly, from such a header.
+`-MM'
+ Like `-M' but do not mention header files that are found in system
+ header directories, nor header files that are included, directly
+ or indirectly, from such a header.
This implies that the choice of angle brackets or double quotes in
- an '#include' directive does not in itself determine whether that
- header will appear in '-MM' dependency output. This is a slight
+ an `#include' directive does not in itself determine whether that
+ header will appear in `-MM' dependency output. This is a slight
change in semantics from GCC versions 3.0 and earlier.
-'-MF FILE'
- When used with '-M' or '-MM', specifies a file to write the
- dependencies to. If no '-MF' switch is given the preprocessor
+`-MF FILE'
+ When used with `-M' or `-MM', specifies a file to write the
+ dependencies to. If no `-MF' switch is given the preprocessor
sends the rules to the same place it would have sent preprocessed
output.
- When used with the driver options '-MD' or '-MMD', '-MF' overrides
+ When used with the driver options `-MD' or `-MMD', `-MF' overrides
the default dependency output file.
-'-MG'
- In conjunction with an option such as '-M' requesting dependency
- generation, '-MG' assumes missing header files are generated files
- and adds them to the dependency list without raising an error. The
- dependency filename is taken directly from the '#include' directive
- without prepending any path. '-MG' also suppresses preprocessed
- output, as a missing header file renders this useless.
+`-MG'
+ In conjunction with an option such as `-M' requesting dependency
+ generation, `-MG' assumes missing header files are generated files
+ and adds them to the dependency list without raising an error.
+ The dependency filename is taken directly from the `#include'
+ directive without prepending any path. `-MG' also suppresses
+ preprocessed output, as a missing header file renders this useless.
This feature is used in automatic updating of makefiles.
-'-MP'
+`-MP'
This option instructs CPP to add a phony target for each dependency
other than the main file, causing each to depend on nothing. These
- dummy rules work around errors 'make' gives if you remove header
- files without updating the 'Makefile' to match.
+ dummy rules work around errors `make' gives if you remove header
+ files without updating the `Makefile' to match.
This is typical output:
@@ -4265,436 +4294,441 @@ single-letter options may _not_ be grouped: '-dM' is very different from
test.h:
-'-MT TARGET'
-
+`-MT TARGET'
Change the target of the rule emitted by dependency generation. By
default CPP takes the name of the main input file, deletes any
- directory components and any file suffix such as '.c', and appends
+ directory components and any file suffix such as `.c', and appends
the platform's usual object suffix. The result is the target.
- An '-MT' option will set the target to be exactly the string you
+ An `-MT' option will set the target to be exactly the string you
specify. If you want multiple targets, you can specify them as a
- single argument to '-MT', or use multiple '-MT' options.
+ single argument to `-MT', or use multiple `-MT' options.
- For example, '-MT '$(objpfx)foo.o'' might give
+ For example, `-MT '$(objpfx)foo.o'' might give
$(objpfx)foo.o: foo.c
-'-MQ TARGET'
-
- Same as '-MT', but it quotes any characters which are special to
- Make. '-MQ '$(objpfx)foo.o'' gives
+`-MQ TARGET'
+ Same as `-MT', but it quotes any characters which are special to
+ Make. `-MQ '$(objpfx)foo.o'' gives
$$(objpfx)foo.o: foo.c
The default target is automatically quoted, as if it were given
- with '-MQ'.
-
-'-MD'
- '-MD' is equivalent to '-M -MF FILE', except that '-E' is not
- implied. The driver determines FILE based on whether an '-o'
- option is given. If it is, the driver uses its argument but with a
- suffix of '.d', otherwise it takes the name of the input file,
- removes any directory components and suffix, and applies a '.d'
+ with `-MQ'.
+
+`-MD'
+ `-MD' is equivalent to `-M -MF FILE', except that `-E' is not
+ implied. The driver determines FILE based on whether an `-o'
+ option is given. If it is, the driver uses its argument but with
+ a suffix of `.d', otherwise it takes the name of the input file,
+ removes any directory components and suffix, and applies a `.d'
suffix.
- If '-MD' is used in conjunction with '-E', any '-o' switch is
+ If `-MD' is used in conjunction with `-E', any `-o' switch is
understood to specify the dependency output file (*note -MF:
- dashMF.), but if used without '-E', each '-o' is understood to
+ dashMF.), but if used without `-E', each `-o' is understood to
specify a target object file.
- Since '-E' is not implied, '-MD' can be used to generate a
+ Since `-E' is not implied, `-MD' can be used to generate a
dependency output file as a side-effect of the compilation process.
-'-MMD'
- Like '-MD' except mention only user header files, not system header
- files.
+`-MMD'
+ Like `-MD' except mention only user header files, not system
+ header files.
-'-x c'
-'-x c++'
-'-x objective-c'
-'-x assembler-with-cpp'
+`-x c'
+`-x c++'
+`-x objective-c'
+`-x assembler-with-cpp'
Specify the source language: C, C++, Objective-C, or assembly.
- This has nothing to do with standards conformance or extensions; it
- merely selects which base syntax to expect. If you give none of
- these options, cpp will deduce the language from the extension of
- the source file: '.c', '.cc', '.m', or '.S'. Some other common
+ This has nothing to do with standards conformance or extensions;
+ it merely selects which base syntax to expect. If you give none
+ of these options, cpp will deduce the language from the extension
+ of the source file: `.c', `.cc', `.m', or `.S'. Some other common
extensions for C++ and assembly are also recognized. If cpp does
not recognize the extension, it will treat the file as C; this is
the most generic mode.
- _Note:_ Previous versions of cpp accepted a '-lang' option which
+ _Note:_ Previous versions of cpp accepted a `-lang' option which
selected both the language and the standards conformance level.
- This option has been removed, because it conflicts with the '-l'
+ This option has been removed, because it conflicts with the `-l'
option.
-'-std=STANDARD'
-'-ansi'
+`-std=STANDARD'
+`-ansi'
Specify the standard to which the code should conform. Currently
CPP knows about C and C++ standards; others may be added in the
future.
STANDARD may be one of:
- 'c90'
- 'c89'
- 'iso9899:1990'
- The ISO C standard from 1990. 'c90' is the customary
+ `c90'
+ `c89'
+ `iso9899:1990'
+ The ISO C standard from 1990. `c90' is the customary
shorthand for this version of the standard.
- The '-ansi' option is equivalent to '-std=c90'.
+ The `-ansi' option is equivalent to `-std=c90'.
- 'iso9899:199409'
+ `iso9899:199409'
The 1990 C standard, as amended in 1994.
- 'iso9899:1999'
- 'c99'
- 'iso9899:199x'
- 'c9x'
+ `iso9899:1999'
+ `c99'
+ `iso9899:199x'
+ `c9x'
The revised ISO C standard, published in December 1999.
Before publication, this was known as C9X.
- 'iso9899:2011'
- 'c11'
- 'c1x'
+ `iso9899:2011'
+ `c11'
+ `c1x'
The revised ISO C standard, published in December 2011.
Before publication, this was known as C1X.
- 'gnu90'
- 'gnu89'
+ `gnu90'
+ `gnu89'
The 1990 C standard plus GNU extensions. This is the default.
- 'gnu99'
- 'gnu9x'
+ `gnu99'
+ `gnu9x'
The 1999 C standard plus GNU extensions.
- 'gnu11'
- 'gnu1x'
+ `gnu11'
+ `gnu1x'
The 2011 C standard plus GNU extensions.
- 'c++98'
+ `c++98'
The 1998 ISO C++ standard plus amendments.
- 'gnu++98'
- The same as '-std=c++98' plus GNU extensions. This is the
+ `gnu++98'
+ The same as `-std=c++98' plus GNU extensions. This is the
default for C++ code.
-'-I-'
- Split the include path. Any directories specified with '-I'
- options before '-I-' are searched only for headers requested with
- '#include "FILE"'; they are not searched for '#include <FILE>'. If
- additional directories are specified with '-I' options after the
- '-I-', those directories are searched for all '#include'
+`-I-'
+ Split the include path. Any directories specified with `-I'
+ options before `-I-' are searched only for headers requested with
+ `#include "FILE"'; they are not searched for `#include <FILE>'.
+ If additional directories are specified with `-I' options after
+ the `-I-', those directories are searched for all `#include'
directives.
- In addition, '-I-' inhibits the use of the directory of the current
- file directory as the first search directory for '#include "FILE"'.
+ In addition, `-I-' inhibits the use of the directory of the current
+ file directory as the first search directory for `#include "FILE"'.
*Note Search Path::. This option has been deprecated.
-'-nostdinc'
+`-nostdinc'
Do not search the standard system directories for header files.
- Only the directories you have specified with '-I' options (and the
+ Only the directories you have specified with `-I' options (and the
directory of the current file, if appropriate) are searched.
-'-nostdinc++'
+`-nostdinc++'
Do not search for header files in the C++-specific standard
directories, but do still search the other standard directories.
(This option is used when building the C++ library.)
-'-include FILE'
- Process FILE as if '#include "file"' appeared as the first line of
- the primary source file. However, the first directory searched for
- FILE is the preprocessor's working directory _instead of_ the
+`-include FILE'
+ Process FILE as if `#include "file"' appeared as the first line of
+ the primary source file. However, the first directory searched
+ for FILE is the preprocessor's working directory _instead of_ the
directory containing the main source file. If not found there, it
- is searched for in the remainder of the '#include "..."' search
+ is searched for in the remainder of the `#include "..."' search
chain as normal.
- If multiple '-include' options are given, the files are included in
- the order they appear on the command line.
+ If multiple `-include' options are given, the files are included
+ in the order they appear on the command line.
-'-imacros FILE'
- Exactly like '-include', except that any output produced by
+`-imacros FILE'
+ Exactly like `-include', except that any output produced by
scanning FILE is thrown away. Macros it defines remain defined.
This allows you to acquire all the macros from a header without
also processing its declarations.
- All files specified by '-imacros' are processed before all files
- specified by '-include'.
+ All files specified by `-imacros' are processed before all files
+ specified by `-include'.
-'-idirafter DIR'
+`-idirafter DIR'
Search DIR for header files, but do it _after_ all directories
- specified with '-I' and the standard system directories have been
+ specified with `-I' and the standard system directories have been
exhausted. DIR is treated as a system include directory. If DIR
- begins with '=', then the '=' will be replaced by the sysroot
- prefix; see '--sysroot' and '-isysroot'.
+ begins with `=', then the `=' will be replaced by the sysroot
+ prefix; see `--sysroot' and `-isysroot'.
-'-iprefix PREFIX'
- Specify PREFIX as the prefix for subsequent '-iwithprefix' options.
- If the prefix represents a directory, you should include the final
- '/'.
+`-iprefix PREFIX'
+ Specify PREFIX as the prefix for subsequent `-iwithprefix'
+ options. If the prefix represents a directory, you should include
+ the final `/'.
-'-iwithprefix DIR'
-'-iwithprefixbefore DIR'
- Append DIR to the prefix specified previously with '-iprefix', and
+`-iwithprefix DIR'
+`-iwithprefixbefore DIR'
+ Append DIR to the prefix specified previously with `-iprefix', and
add the resulting directory to the include search path.
- '-iwithprefixbefore' puts it in the same place '-I' would;
- '-iwithprefix' puts it where '-idirafter' would.
+ `-iwithprefixbefore' puts it in the same place `-I' would;
+ `-iwithprefix' puts it where `-idirafter' would.
-'-isysroot DIR'
- This option is like the '--sysroot' option, but applies only to
+`-isysroot DIR'
+ This option is like the `--sysroot' option, but applies only to
header files (except for Darwin targets, where it applies to both
- header files and libraries). See the '--sysroot' option for more
+ header files and libraries). See the `--sysroot' option for more
information.
-'-imultilib DIR'
+`-imultilib DIR'
Use DIR as a subdirectory of the directory containing
target-specific C++ headers.
-'-isystem DIR'
+`-isystem DIR'
Search DIR for header files, after all directories specified by
- '-I' but before the standard system directories. Mark it as a
+ `-I' but before the standard system directories. Mark it as a
system directory, so that it gets the same special treatment as is
applied to the standard system directories. *Note System
- Headers::. If DIR begins with '=', then the '=' will be replaced
- by the sysroot prefix; see '--sysroot' and '-isysroot'.
-
-'-iquote DIR'
- Search DIR only for header files requested with '#include "FILE"';
- they are not searched for '#include <FILE>', before all directories
- specified by '-I' and before the standard system directories.
- *Note Search Path::. If DIR begins with '=', then the '=' will be
- replaced by the sysroot prefix; see '--sysroot' and '-isysroot'.
-
-'-fdirectives-only'
+ Headers::. If DIR begins with `=', then the `=' will be replaced
+ by the sysroot prefix; see `--sysroot' and `-isysroot'.
+
+`-iquote DIR'
+ Search DIR only for header files requested with `#include "FILE"';
+ they are not searched for `#include <FILE>', before all
+ directories specified by `-I' and before the standard system
+ directories. *Note Search Path::. If DIR begins with `=', then
+ the `=' will be replaced by the sysroot prefix; see `--sysroot'
+ and `-isysroot'.
+
+`-fdirectives-only'
When preprocessing, handle directives, but do not expand macros.
- The option's behavior depends on the '-E' and '-fpreprocessed'
+ The option's behavior depends on the `-E' and `-fpreprocessed'
options.
- With '-E', preprocessing is limited to the handling of directives
- such as '#define', '#ifdef', and '#error'. Other preprocessor
- operations, such as macro expansion and trigraph conversion are not
- performed. In addition, the '-dD' option is implicitly enabled.
+ With `-E', preprocessing is limited to the handling of directives
+ such as `#define', `#ifdef', and `#error'. Other preprocessor
+ operations, such as macro expansion and trigraph conversion are
+ not performed. In addition, the `-dD' option is implicitly
+ enabled.
- With '-fpreprocessed', predefinition of command line and most
- builtin macros is disabled. Macros such as '__LINE__', which are
+ With `-fpreprocessed', predefinition of command line and most
+ builtin macros is disabled. Macros such as `__LINE__', which are
contextually dependent, are handled normally. This enables
- compilation of files previously preprocessed with '-E
+ compilation of files previously preprocessed with `-E
-fdirectives-only'.
- With both '-E' and '-fpreprocessed', the rules for '-fpreprocessed'
- take precedence. This enables full preprocessing of files
- previously preprocessed with '-E -fdirectives-only'.
+ With both `-E' and `-fpreprocessed', the rules for
+ `-fpreprocessed' take precedence. This enables full preprocessing
+ of files previously preprocessed with `-E -fdirectives-only'.
-'-fdollars-in-identifiers'
- Accept '$' in identifiers. *Note Identifier characters::.
+`-fdollars-in-identifiers'
+ Accept `$' in identifiers. *Note Identifier characters::.
-'-fextended-identifiers'
+`-fextended-identifiers'
Accept universal character names in identifiers. This option is
enabled by default for C99 (and later C standard versions) and C++.
-'-fno-canonical-system-headers'
+`-fno-canonical-system-headers'
When preprocessing, do not shorten system header paths with
canonicalization.
-'-fpreprocessed'
+`-fpreprocessed'
Indicate to the preprocessor that the input file has already been
preprocessed. This suppresses things like macro expansion,
trigraph conversion, escaped newline splicing, and processing of
most directives. The preprocessor still recognizes and removes
- comments, so that you can pass a file preprocessed with '-C' to the
- compiler without problems. In this mode the integrated
+ comments, so that you can pass a file preprocessed with `-C' to
+ the compiler without problems. In this mode the integrated
preprocessor is little more than a tokenizer for the front ends.
- '-fpreprocessed' is implicit if the input file has one of the
- extensions '.i', '.ii' or '.mi'. These are the extensions that GCC
- uses for preprocessed files created by '-save-temps'.
+ `-fpreprocessed' is implicit if the input file has one of the
+ extensions `.i', `.ii' or `.mi'. These are the extensions that
+ GCC uses for preprocessed files created by `-save-temps'.
-'-ftabstop=WIDTH'
+`-ftabstop=WIDTH'
Set the distance between tab stops. This helps the preprocessor
report correct column numbers in warnings or errors, even if tabs
appear on the line. If the value is less than 1 or greater than
100, the option is ignored. The default is 8.
-'-fdebug-cpp'
- This option is only useful for debugging GCC. When used with '-E',
- dumps debugging information about location maps. Every token in
- the output is preceded by the dump of the map its location belongs
- to. The dump of the map holding the location of a token would be:
- {'P':/file/path;'F':/includer/path;'L':LINE_NUM;'C':COL_NUM;'S':SYSTEM_HEADER_P;'M':MAP_ADDRESS;'E':MACRO_EXPANSION_P,'loc':LOCATION}
+`-fdebug-cpp'
+ This option is only useful for debugging GCC. When used with
+ `-E', dumps debugging information about location maps. Every
+ token in the output is preceded by the dump of the map its location
+ belongs to. The dump of the map holding the location of a token
+ would be:
+ {`P':`/file/path';`F':`/includer/path';`L':LINE_NUM;`C':COL_NUM;`S':SYSTEM_HEADER_P;`M':MAP_ADDRESS;`E':MACRO_EXPANSION_P,`loc':LOCATION}
- When used without '-E', this option has no effect.
+ When used without `-E', this option has no effect.
-'-ftrack-macro-expansion[=LEVEL]'
- Track locations of tokens across macro expansions. This allows the
+`-ftrack-macro-expansion[=LEVEL]'
+ Track locations of tokens across macro expansions. This allows the
compiler to emit diagnostic about the current macro expansion stack
- when a compilation error occurs in a macro expansion. Using this
- option makes the preprocessor and the compiler consume more memory.
- The LEVEL parameter can be used to choose the level of precision of
- token location tracking thus decreasing the memory consumption if
- necessary. Value '0' of LEVEL de-activates this option just as if
- no '-ftrack-macro-expansion' was present on the command line.
- Value '1' tracks tokens locations in a degraded mode for the sake
- of minimal memory overhead. In this mode all tokens resulting from
- the expansion of an argument of a function-like macro have the same
- location. Value '2' tracks tokens locations completely. This
- value is the most memory hungry. When this option is given no
- argument, the default parameter value is '2'.
-
- Note that '-ftrack-macro-expansion=2' is activated by default.
-
-'-fexec-charset=CHARSET'
+ when a compilation error occurs in a macro expansion. Using this
+ option makes the preprocessor and the compiler consume more
+ memory. The LEVEL parameter can be used to choose the level of
+ precision of token location tracking thus decreasing the memory
+ consumption if necessary. Value `0' of LEVEL de-activates this
+ option just as if no `-ftrack-macro-expansion' was present on the
+ command line. Value `1' tracks tokens locations in a degraded mode
+ for the sake of minimal memory overhead. In this mode all tokens
+ resulting from the expansion of an argument of a function-like
+ macro have the same location. Value `2' tracks tokens locations
+ completely. This value is the most memory hungry. When this
+ option is given no argument, the default parameter value is `2'.
+
+ Note that `-ftrack-macro-expansion=2' is activated by default.
+
+`-fexec-charset=CHARSET'
Set the execution character set, used for string and character
constants. The default is UTF-8. CHARSET can be any encoding
- supported by the system's 'iconv' library routine.
+ supported by the system's `iconv' library routine.
-'-fwide-exec-charset=CHARSET'
+`-fwide-exec-charset=CHARSET'
Set the wide execution character set, used for wide string and
character constants. The default is UTF-32 or UTF-16, whichever
- corresponds to the width of 'wchar_t'. As with '-fexec-charset',
- CHARSET can be any encoding supported by the system's 'iconv'
+ corresponds to the width of `wchar_t'. As with `-fexec-charset',
+ CHARSET can be any encoding supported by the system's `iconv'
library routine; however, you will have problems with encodings
- that do not fit exactly in 'wchar_t'.
+ that do not fit exactly in `wchar_t'.
-'-finput-charset=CHARSET'
+`-finput-charset=CHARSET'
Set the input character set, used for translation from the
- character set of the input file to the source character set used by
- GCC. If the locale does not specify, or GCC cannot get this
+ character set of the input file to the source character set used
+ by GCC. If the locale does not specify, or GCC cannot get this
information from the locale, the default is UTF-8. This can be
overridden by either the locale or this command-line option.
Currently the command-line option takes precedence if there's a
conflict. CHARSET can be any encoding supported by the system's
- 'iconv' library routine.
+ `iconv' library routine.
-'-fworking-directory'
+`-fworking-directory'
Enable generation of linemarkers in the preprocessor output that
will let the compiler know the current working directory at the
time of preprocessing. When this option is enabled, the
preprocessor will emit, after the initial linemarker, a second
linemarker with the current working directory followed by two
slashes. GCC will use this directory, when it's present in the
- preprocessed input, as the directory emitted as the current working
- directory in some debugging information formats. This option is
- implicitly enabled if debugging information is enabled, but this
- can be inhibited with the negated form '-fno-working-directory'.
- If the '-P' flag is present in the command line, this option has no
- effect, since no '#line' directives are emitted whatsoever.
-
-'-fno-show-column'
+ preprocessed input, as the directory emitted as the current
+ working directory in some debugging information formats. This
+ option is implicitly enabled if debugging information is enabled,
+ but this can be inhibited with the negated form
+ `-fno-working-directory'. If the `-P' flag is present in the
+ command line, this option has no effect, since no `#line'
+ directives are emitted whatsoever.
+
+`-fno-show-column'
Do not print column numbers in diagnostics. This may be necessary
if diagnostics are being scanned by a program that does not
- understand the column numbers, such as 'dejagnu'.
+ understand the column numbers, such as `dejagnu'.
-'-A PREDICATE=ANSWER'
+`-A PREDICATE=ANSWER'
Make an assertion with the predicate PREDICATE and answer ANSWER.
- This form is preferred to the older form '-A PREDICATE(ANSWER)',
+ This form is preferred to the older form `-A PREDICATE(ANSWER)',
which is still supported, because it does not use shell special
characters. *Note Obsolete Features::.
-'-A -PREDICATE=ANSWER'
+`-A -PREDICATE=ANSWER'
Cancel an assertion with the predicate PREDICATE and answer ANSWER.
-'-dCHARS'
- CHARS is a sequence of one or more of the following characters, and
- must not be preceded by a space. Other characters are interpreted
- by the compiler proper, or reserved for future versions of GCC, and
- so are silently ignored. If you specify characters whose behavior
- conflicts, the result is undefined.
+`-dCHARS'
+ CHARS is a sequence of one or more of the following characters,
+ and must not be preceded by a space. Other characters are
+ interpreted by the compiler proper, or reserved for future
+ versions of GCC, and so are silently ignored. If you specify
+ characters whose behavior conflicts, the result is undefined.
- 'M'
- Instead of the normal output, generate a list of '#define'
+ `M'
+ Instead of the normal output, generate a list of `#define'
directives for all the macros defined during the execution of
- the preprocessor, including predefined macros. This gives you
- a way of finding out what is predefined in your version of the
- preprocessor. Assuming you have no file 'foo.h', the command
+ the preprocessor, including predefined macros. This gives
+ you a way of finding out what is predefined in your version
+ of the preprocessor. Assuming you have no file `foo.h', the
+ command
touch foo.h; cpp -dM foo.h
will show all the predefined macros.
- If you use '-dM' without the '-E' option, '-dM' is interpreted
- as a synonym for '-fdump-rtl-mach'. *Note (gcc)Debugging
- Options::.
+ If you use `-dM' without the `-E' option, `-dM' is
+ interpreted as a synonym for `-fdump-rtl-mach'. *Note
+ Debugging Options: (gcc)Debugging Options.
- 'D'
- Like 'M' except in two respects: it does _not_ include the
- predefined macros, and it outputs _both_ the '#define'
+ `D'
+ Like `M' except in two respects: it does _not_ include the
+ predefined macros, and it outputs _both_ the `#define'
directives and the result of preprocessing. Both kinds of
output go to the standard output file.
- 'N'
- Like 'D', but emit only the macro names, not their expansions.
+ `N'
+ Like `D', but emit only the macro names, not their expansions.
- 'I'
- Output '#include' directives in addition to the result of
+ `I'
+ Output `#include' directives in addition to the result of
preprocessing.
- 'U'
- Like 'D' except that only macros that are expanded, or whose
+ `U'
+ Like `D' except that only macros that are expanded, or whose
definedness is tested in preprocessor directives, are output;
the output is delayed until the use or test of the macro; and
- '#undef' directives are also output for macros tested but
+ `#undef' directives are also output for macros tested but
undefined at the time.
-'-P'
+`-P'
Inhibit generation of linemarkers in the output from the
preprocessor. This might be useful when running the preprocessor
on something that is not C code, and will be sent to a program
which might be confused by the linemarkers. *Note Preprocessor
Output::.
-'-C'
+`-C'
Do not discard comments. All comments are passed through to the
- output file, except for comments in processed directives, which are
- deleted along with the directive.
+ output file, except for comments in processed directives, which
+ are deleted along with the directive.
- You should be prepared for side effects when using '-C'; it causes
+ You should be prepared for side effects when using `-C'; it causes
the preprocessor to treat comments as tokens in their own right.
For example, comments appearing at the start of what would be a
directive line have the effect of turning that line into an
ordinary source line, since the first token on the line is no
- longer a '#'.
+ longer a `#'.
-'-CC'
+`-CC'
Do not discard comments, including during macro expansion. This is
- like '-C', except that comments contained within macros are also
+ like `-C', except that comments contained within macros are also
passed through to the output file where the macro is expanded.
- In addition to the side-effects of the '-C' option, the '-CC'
- option causes all C++-style comments inside a macro to be converted
- to C-style comments. This is to prevent later use of that macro
- from inadvertently commenting out the remainder of the source line.
+ In addition to the side-effects of the `-C' option, the `-CC'
+ option causes all C++-style comments inside a macro to be
+ converted to C-style comments. This is to prevent later use of
+ that macro from inadvertently commenting out the remainder of the
+ source line.
- The '-CC' option is generally used to support lint comments.
+ The `-CC' option is generally used to support lint comments.
-'-traditional-cpp'
+`-traditional-cpp'
Try to imitate the behavior of old-fashioned C preprocessors, as
opposed to ISO C preprocessors. *Note Traditional Mode::.
-'-trigraphs'
+`-trigraphs'
Process trigraph sequences. *Note Initial processing::.
-'-remap'
+`-remap'
Enable special code to work around file systems which only permit
very short file names, such as MS-DOS.
-'--help'
-'--target-help'
+`--help'
+`--target-help'
Print text describing all the command-line options instead of
preprocessing anything.
-'-v'
+`-v'
Verbose mode. Print out GNU CPP's version number at the beginning
of execution, and report the final form of the include path.
-'-H'
+`-H'
Print the name of each header file used, in addition to other
normal activities. Each name is indented to show how deep in the
- '#include' stack it is. Precompiled header files are also printed,
- even if they are found to be invalid; an invalid precompiled header
- file is printed with '...x' and a valid one with '...!' .
+ `#include' stack it is. Precompiled header files are also
+ printed, even if they are found to be invalid; an invalid
+ precompiled header file is printed with `...x' and a valid one
+ with `...!' .
-'-version'
-'--version'
+`-version'
+`--version'
Print out GNU CPP's version number. With one dash, proceed to
preprocess as normal. With two dashes, exit immediately.
@@ -4709,60 +4743,60 @@ operates. You can use them to specify directories or prefixes to use
when searching for include files, or to control dependency output.
Note that you can also specify places to search using options such as
-'-I', and control dependency output with options like '-M' (*note
+`-I', and control dependency output with options like `-M' (*note
Invocation::). These take precedence over environment variables, which
in turn take precedence over the configuration of GCC.
-'CPATH'
-'C_INCLUDE_PATH'
-'CPLUS_INCLUDE_PATH'
-'OBJC_INCLUDE_PATH'
+`CPATH'
+`C_INCLUDE_PATH'
+`CPLUS_INCLUDE_PATH'
+`OBJC_INCLUDE_PATH'
Each variable's value is a list of directories separated by a
- special character, much like 'PATH', in which to look for header
- files. The special character, 'PATH_SEPARATOR', is
+ special character, much like `PATH', in which to look for header
+ files. The special character, `PATH_SEPARATOR', is
target-dependent and determined at GCC build time. For Microsoft
Windows-based targets it is a semicolon, and for almost all other
targets it is a colon.
- 'CPATH' specifies a list of directories to be searched as if
- specified with '-I', but after any paths given with '-I' options on
- the command line. This environment variable is used regardless of
- which language is being preprocessed.
+ `CPATH' specifies a list of directories to be searched as if
+ specified with `-I', but after any paths given with `-I' options
+ on the command line. This environment variable is used regardless
+ of which language is being preprocessed.
The remaining environment variables apply only when preprocessing
the particular language indicated. Each specifies a list of
- directories to be searched as if specified with '-isystem', but
- after any paths given with '-isystem' options on the command line.
+ directories to be searched as if specified with `-isystem', but
+ after any paths given with `-isystem' options on the command line.
In all these variables, an empty element instructs the compiler to
- search its current working directory. Empty elements can appear at
- the beginning or end of a path. For instance, if the value of
- 'CPATH' is ':/special/include', that has the same effect as
- '-I. -I/special/include'.
+ search its current working directory. Empty elements can appear
+ at the beginning or end of a path. For instance, if the value of
+ `CPATH' is `:/special/include', that has the same effect as
+ `-I. -I/special/include'.
See also *note Search Path::.
-'DEPENDENCIES_OUTPUT'
+`DEPENDENCIES_OUTPUT'
If this variable is set, its value specifies how to output
dependencies for Make based on the non-system header files
processed by the compiler. System header files are ignored in the
dependency output.
- The value of 'DEPENDENCIES_OUTPUT' can be just a file name, in
+ The value of `DEPENDENCIES_OUTPUT' can be just a file name, in
which case the Make rules are written to that file, guessing the
target name from the source file name. Or the value can have the
- form 'FILE TARGET', in which case the rules are written to file
+ form `FILE TARGET', in which case the rules are written to file
FILE using TARGET as the target name.
In other words, this environment variable is equivalent to
- combining the options '-MM' and '-MF' (*note Invocation::), with an
- optional '-MT' switch too.
+ combining the options `-MM' and `-MF' (*note Invocation::), with
+ an optional `-MT' switch too.
-'SUNPRO_DEPENDENCIES'
- This variable is the same as 'DEPENDENCIES_OUTPUT' (see above),
- except that system header files are not ignored, so it implies '-M'
- rather than '-MM'. However, the dependence on the main input file
- is omitted. *Note Invocation::.
+`SUNPRO_DEPENDENCIES'
+ This variable is the same as `DEPENDENCIES_OUTPUT' (see above),
+ except that system header files are not ignored, so it implies
+ `-M' rather than `-MM'. However, the dependence on the main input
+ file is omitted. *Note Invocation::.

File: cpp.info, Node: GNU Free Documentation License, Next: Index of Directives, Prev: Environment Variables, Up: Top
@@ -4773,7 +4807,7 @@ GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
+ `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -4798,21 +4832,21 @@ GNU Free Documentation License
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book. We
- recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it can
- be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright 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, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
- the license if you copy, modify or distribute the work in a way
- requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "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 containing the
Document or a portion of it, either copied verbatim, or with
@@ -4830,12 +4864,12 @@ GNU Free Documentation License
regarding them.
The "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 above definition of Secondary then it
- is not allowed to be designated as Invariant. The Document may
- contain zero Invariant Sections. If the Document does not identify
- any Invariant Sections then there are none.
+ 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 above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -4846,27 +4880,27 @@ GNU Free Documentation License
A "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 generic text editors or (for images composed
- of pixels) generic paint programs or (for drawings) some widely
- available drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of formats
- suitable for input to text formatters. A copy made in an otherwise
- Transparent file format whose markup, or absence 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".
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence 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".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and standard-conforming
- simple HTML, PostScript or PDF designed for human modification.
- Examples of transparent image formats include PNG, XCF and JPG.
- Opaque formats include proprietary formats that can be read and
- edited only by proprietary word processors, SGML or XML for which
- the DTD and/or processing tools are not generally available, and
- the machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -4904,8 +4938,8 @@ GNU Free Documentation License
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow the
- conditions in section 3.
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -4919,11 +4953,12 @@ GNU Free Documentation License
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on the
- covers in addition. Copying with changes limited to the covers, as
- long as they preserve the title of the Document and satisfy these
- conditions, can be treated as verbatim copying in other respects.
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -4931,39 +4966,40 @@ GNU Free Documentation License
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with
- each Opaque copy a computer-network location from which the general
- network-using public has access to download using public-standard
- network protocols a complete Transparent copy of the Document, free
- of added material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of Opaque
- copies in quantity, to ensure that this Transparent copy will
- remain thus accessible at the stated location until at least one
- year after the last time you distribute an Opaque copy (directly or
- through your agents or retailers) of that edition to the public.
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies,
- to give them a chance to provide you with an updated version of the
- Document.
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with the
- Modified Version filling the role of the Document, thus licensing
- distribution and modification of the Modified Version to whoever
- possesses a copy of it. In addition, you must do these things in
- the Modified Version:
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the
- History section of the Document). You may use the same title
- as a previous version if the original publisher of that
- version gives permission.
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -4993,30 +5029,31 @@ GNU Free Documentation License
I. Preserve the section Entitled "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, 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.
+ 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, 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.
J. Preserve the network location, if any, given in 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 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.
+ previous versions it was based on. These may be placed in
+ the "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.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section
- all the substance and tone of each of the contributor
+ 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.
- L. Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the
- equivalent are not considered part of the section titles.
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -5029,11 +5066,11 @@ GNU Free Documentation License
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain 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 be distinct from any other
- section titles.
+ 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 be distinct from any
+ other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -5042,15 +5079,15 @@ GNU Free Documentation License
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of
- the list of Cover Texts in the Modified Version. Only one passage
- of Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover, previously added
- by you or by arrangement made by the same entity you are acting on
- behalf of, you may not add another; but you may replace the old
- one, on explicit permission from the previous publisher that added
- the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -5060,8 +5097,8 @@ GNU Free Documentation License
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination all
- of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -5088,20 +5125,20 @@ GNU Free Documentation License
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the documents
- in all other respects.
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
7. AGGREGATION WITH INDEPENDENT WORKS
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
+ 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 the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -5146,8 +5183,8 @@ GNU Free Documentation License
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -5159,33 +5196,33 @@ GNU Free Documentation License
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, receipt of a copy of some or all of the
- same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, receipt of a copy of some or all of
+ the same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- <http://www.gnu.org/copyleft/>.
+ `http://www.gnu.org/copyleft/'.
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 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 Foundation. If the
- Document does not specify a version number 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
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number 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 statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
@@ -5215,6 +5252,7 @@ GNU Free Documentation License
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
+
ADDENDUM: How to use this License for your documents
====================================================
@@ -5231,7 +5269,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -5242,9 +5280,9 @@ combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of free
-software license, such as the GNU General Public License, to permit
-their use in free software.
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.

File: cpp.info, Node: Index of Directives, Next: Option Index, Prev: GNU Free Documentation License, Up: Top
@@ -5273,8 +5311,8 @@ Index of Directives
* #pragma GCC dependency: Pragmas. (line 55)
* #pragma GCC error: Pragmas. (line 100)
* #pragma GCC poison: Pragmas. (line 67)
-* #pragma GCC system_header: System Headers. (line 31)
* #pragma GCC system_header <1>: Pragmas. (line 94)
+* #pragma GCC system_header: System Headers. (line 31)
* #pragma GCC warning: Pragmas. (line 99)
* #sccs: Other Directives. (line 6)
* #unassert: Obsolete Features. (line 59)
@@ -5289,96 +5327,96 @@ Option Index
************
CPP's command-line options and environment variables are indexed here
-without any initial '-' or '--'.
+without any initial `-' or `--'.
* Menu:
-* A: Invocation. (line 566)
-* ansi: Invocation. (line 311)
-* C: Invocation. (line 624)
+* A: Invocation. (line 567)
+* ansi: Invocation. (line 308)
+* C: Invocation. (line 626)
+* C_INCLUDE_PATH: Environment Variables.
+ (line 16)
* CPATH: Environment Variables.
(line 15)
* CPLUS_INCLUDE_PATH: Environment Variables.
(line 17)
-* C_INCLUDE_PATH: Environment Variables.
- (line 16)
-* D: Invocation. (line 40)
-* dD: Invocation. (line 597)
+* D: Invocation. (line 39)
+* dD: Invocation. (line 599)
* DEPENDENCIES_OUTPUT: Environment Variables.
(line 44)
-* dI: Invocation. (line 606)
-* dM: Invocation. (line 582)
-* dN: Invocation. (line 603)
-* dU: Invocation. (line 610)
-* fdebug-cpp: Invocation. (line 497)
-* fdirectives-only: Invocation. (line 446)
-* fdollars-in-identifiers: Invocation. (line 467)
+* dI: Invocation. (line 608)
+* dM: Invocation. (line 583)
+* dN: Invocation. (line 605)
+* dU: Invocation. (line 612)
+* fdebug-cpp: Invocation. (line 496)
+* fdirectives-only: Invocation. (line 444)
+* fdollars-in-identifiers: Invocation. (line 466)
* fexec-charset: Invocation. (line 524)
-* fextended-identifiers: Invocation. (line 470)
+* fextended-identifiers: Invocation. (line 469)
* finput-charset: Invocation. (line 537)
-* fno-canonical-system-headers: Invocation. (line 474)
-* fno-show-column: Invocation. (line 561)
+* fno-canonical-system-headers: Invocation. (line 473)
+* fno-show-column: Invocation. (line 562)
* fno-working-directory: Invocation. (line 547)
-* fpreprocessed: Invocation. (line 478)
-* ftabstop: Invocation. (line 491)
+* fpreprocessed: Invocation. (line 477)
+* ftabstop: Invocation. (line 490)
* ftrack-macro-expansion: Invocation. (line 506)
* fwide-exec-charset: Invocation. (line 529)
* fworking-directory: Invocation. (line 547)
-* H: Invocation. (line 668)
-* help: Invocation. (line 660)
-* I: Invocation. (line 72)
-* I-: Invocation. (line 360)
-* idirafter: Invocation. (line 402)
-* imacros: Invocation. (line 393)
-* imultilib: Invocation. (line 427)
-* include: Invocation. (line 382)
-* iprefix: Invocation. (line 409)
-* iquote: Invocation. (line 439)
-* isysroot: Invocation. (line 421)
-* isystem: Invocation. (line 431)
-* iwithprefix: Invocation. (line 415)
-* iwithprefixbefore: Invocation. (line 415)
-* M: Invocation. (line 181)
-* MD: Invocation. (line 272)
-* MF: Invocation. (line 216)
-* MG: Invocation. (line 225)
-* MM: Invocation. (line 206)
-* MMD: Invocation. (line 288)
-* MP: Invocation. (line 235)
-* MQ: Invocation. (line 262)
-* MT: Invocation. (line 247)
-* nostdinc: Invocation. (line 372)
-* nostdinc++: Invocation. (line 377)
-* o: Invocation. (line 83)
+* H: Invocation. (line 671)
+* help: Invocation. (line 663)
+* I: Invocation. (line 71)
+* I-: Invocation. (line 357)
+* idirafter: Invocation. (line 399)
+* imacros: Invocation. (line 390)
+* imultilib: Invocation. (line 424)
+* include: Invocation. (line 379)
+* iprefix: Invocation. (line 406)
+* iquote: Invocation. (line 436)
+* isysroot: Invocation. (line 418)
+* isystem: Invocation. (line 428)
+* iwithprefix: Invocation. (line 412)
+* iwithprefixbefore: Invocation. (line 412)
+* M: Invocation. (line 180)
+* MD: Invocation. (line 269)
+* MF: Invocation. (line 215)
+* MG: Invocation. (line 224)
+* MM: Invocation. (line 205)
+* MMD: Invocation. (line 285)
+* MP: Invocation. (line 234)
+* MQ: Invocation. (line 260)
+* MT: Invocation. (line 246)
+* nostdinc: Invocation. (line 369)
+* nostdinc++: Invocation. (line 374)
+* o: Invocation. (line 82)
* OBJC_INCLUDE_PATH: Environment Variables.
(line 18)
-* P: Invocation. (line 617)
-* pedantic: Invocation. (line 171)
-* pedantic-errors: Invocation. (line 176)
-* remap: Invocation. (line 655)
-* std=: Invocation. (line 311)
+* P: Invocation. (line 619)
+* pedantic: Invocation. (line 170)
+* pedantic-errors: Invocation. (line 175)
+* remap: Invocation. (line 658)
+* std=: Invocation. (line 308)
* SUNPRO_DEPENDENCIES: Environment Variables.
(line 60)
-* target-help: Invocation. (line 660)
-* traditional-cpp: Invocation. (line 648)
-* trigraphs: Invocation. (line 652)
-* U: Invocation. (line 63)
-* undef: Invocation. (line 67)
-* v: Invocation. (line 664)
-* version: Invocation. (line 676)
-* w: Invocation. (line 167)
-* Wall: Invocation. (line 89)
-* Wcomment: Invocation. (line 97)
-* Wcomments: Invocation. (line 97)
-* Wendif-labels: Invocation. (line 144)
-* Werror: Invocation. (line 157)
-* Wsystem-headers: Invocation. (line 161)
-* Wtraditional: Invocation. (line 114)
-* Wtrigraphs: Invocation. (line 102)
-* Wundef: Invocation. (line 120)
-* Wunused-macros: Invocation. (line 125)
-* x: Invocation. (line 295)
+* target-help: Invocation. (line 663)
+* traditional-cpp: Invocation. (line 651)
+* trigraphs: Invocation. (line 655)
+* U: Invocation. (line 62)
+* undef: Invocation. (line 66)
+* v: Invocation. (line 667)
+* version: Invocation. (line 680)
+* w: Invocation. (line 166)
+* Wall: Invocation. (line 88)
+* Wcomment: Invocation. (line 96)
+* Wcomments: Invocation. (line 96)
+* Wendif-labels: Invocation. (line 143)
+* Werror: Invocation. (line 156)
+* Wsystem-headers: Invocation. (line 160)
+* Wtraditional: Invocation. (line 113)
+* Wtrigraphs: Invocation. (line 101)
+* Wundef: Invocation. (line 119)
+* Wunused-macros: Invocation. (line 124)
+* x: Invocation. (line 292)

File: cpp.info, Node: Concept Index, Prev: Option Index, Up: Top
@@ -5389,10 +5427,10 @@ Concept Index
* Menu:
-* '#' operator: Stringification. (line 6)
-* '##' operator: Concatenation. (line 6)
-* '_Pragma': Pragmas. (line 25)
-* alternative tokens: Tokenization. (line 104)
+* # operator: Stringification. (line 6)
+* ## operator: Concatenation. (line 6)
+* _Pragma: Pragmas. (line 25)
+* alternative tokens: Tokenization. (line 105)
* arguments: Macro Arguments. (line 6)
* arguments in macro definitions: Macro Arguments. (line 6)
* assertions: Obsolete Features. (line 13)
@@ -5400,7 +5438,7 @@ Concept Index
* backslash-newline: Initial processing. (line 61)
* block comments: Initial processing. (line 77)
* C++ named operators: C++ Named Operators. (line 6)
-* character constants: Tokenization. (line 83)
+* character constants: Tokenization. (line 84)
* character set, execution: Invocation. (line 524)
* character set, input: Invocation. (line 537)
* character set, wide execution: Invocation. (line 529)
@@ -5415,16 +5453,14 @@ Concept Index
* conditionals: Conditionals. (line 6)
* continued lines: Initial processing. (line 61)
* controlling macro: Once-Only Headers. (line 35)
-* 'defined': Defined. (line 6)
+* defined: Defined. (line 6)
* dependencies for make as output: Environment Variables.
(line 45)
-* dependencies for make as output <1>: Environment Variables.
- (line 61)
-* dependencies, 'make': Invocation. (line 181)
+* dependencies, make: Invocation. (line 180)
* diagnostic: Diagnostics. (line 6)
* differences from previous versions: Differences from previous versions.
(line 6)
-* digraphs: Tokenization. (line 104)
+* digraphs: Tokenization. (line 105)
* directive line: The preprocessing language.
(line 6)
* directive name: The preprocessing language.
@@ -5442,15 +5478,15 @@ Concept Index
* grouping options: Invocation. (line 34)
* guard macro: Once-Only Headers. (line 35)
* header file: Header Files. (line 6)
-* header file names: Tokenization. (line 83)
-* identifiers: Tokenization. (line 33)
+* header file names: Tokenization. (line 84)
+* identifiers: Tokenization. (line 34)
* implementation limits: Implementation limits.
(line 6)
* implementation-defined behavior: Implementation-defined behavior.
(line 6)
* including just once: Once-Only Headers. (line 6)
* invocation: Invocation. (line 6)
-* 'iso646.h': C++ Named Operators. (line 6)
+* iso646.h: C++ Named Operators. (line 6)
* line comments: Initial processing. (line 77)
* line control: Line Control. (line 6)
* line endings: Initial processing. (line 14)
@@ -5461,17 +5497,17 @@ Concept Index
* macros in include: Computed Includes. (line 6)
* macros with arguments: Macro Arguments. (line 6)
* macros with variable arguments: Variadic Macros. (line 6)
-* 'make': Invocation. (line 181)
+* make: Invocation. (line 180)
* manifest constants: Object-like Macros. (line 6)
* named operators: C++ Named Operators. (line 6)
* newlines in macro arguments: Newlines in Arguments.
(line 6)
* null directive: Other Directives. (line 15)
-* numbers: Tokenization. (line 59)
+* numbers: Tokenization. (line 60)
* object-like macro: Object-like Macros. (line 6)
-* options: Invocation. (line 39)
+* options: Invocation. (line 38)
* options, grouping: Invocation. (line 34)
-* other tokens: Tokenization. (line 118)
+* other tokens: Tokenization. (line 119)
* output format: Preprocessor Output. (line 12)
* overriding a header file: Wrapper Headers. (line 6)
* parentheses in macro bodies: Operator Precedence Problems.
@@ -5483,11 +5519,11 @@ Concept Index
* predicates: Obsolete Features. (line 26)
* preprocessing directives: The preprocessing language.
(line 6)
-* preprocessing numbers: Tokenization. (line 59)
+* preprocessing numbers: Tokenization. (line 60)
* preprocessing tokens: Tokenization. (line 6)
* prescan of macro arguments: Argument Prescan. (line 6)
* problems with macros: Macro Pitfalls. (line 6)
-* punctuators: Tokenization. (line 104)
+* punctuators: Tokenization. (line 105)
* redefining macros: Undefining and Redefining Macros.
(line 6)
* repeated inclusion: Once-Only Headers. (line 6)
@@ -5503,12 +5539,12 @@ Concept Index
(line 6)
* standard predefined macros.: Standard Predefined Macros.
(line 6)
-* string constants: Tokenization. (line 83)
-* string literals: Tokenization. (line 83)
+* string constants: Tokenization. (line 84)
+* string literals: Tokenization. (line 84)
* stringification: Stringification. (line 6)
* symbolic constants: Object-like Macros. (line 6)
-* system header files: Header Files. (line 13)
* system header files <1>: System Headers. (line 6)
+* system header files: Header Files. (line 13)
* system-specific predefined macros: System-specific Predefined Macros.
(line 6)
* testing predicates: Obsolete Features. (line 37)
@@ -5522,85 +5558,85 @@ Concept Index
(line 6)
* variable number of arguments: Variadic Macros. (line 6)
* variadic macros: Variadic Macros. (line 6)
-* wrapper '#ifndef': Once-Only Headers. (line 6)
+* wrapper #ifndef: Once-Only Headers. (line 6)
* wrapper headers: Wrapper Headers. (line 6)

Tag Table:
-Node: Top945
-Node: Overview3549
-Node: Character sets6383
-Ref: Character sets-Footnote-18538
-Node: Initial processing8719
-Ref: trigraphs10278
-Node: Tokenization14478
-Ref: Tokenization-Footnote-121507
-Node: The preprocessing language21618
-Node: Header Files24497
-Node: Include Syntax26413
-Node: Include Operation28050
-Node: Search Path29898
-Node: Once-Only Headers33099
-Node: Alternatives to Wrapper #ifndef34758
-Node: Computed Includes36500
-Node: Wrapper Headers39658
-Node: System Headers42081
-Node: Macros44131
-Node: Object-like Macros45272
-Node: Function-like Macros48862
-Node: Macro Arguments50478
-Node: Stringification54621
-Node: Concatenation57827
-Node: Variadic Macros60935
-Node: Predefined Macros65722
-Node: Standard Predefined Macros66310
-Node: Common Predefined Macros72279
-Node: System-specific Predefined Macros92352
-Node: C++ Named Operators94375
-Node: Undefining and Redefining Macros95339
-Node: Directives Within Macro Arguments97437
-Node: Macro Pitfalls98985
-Node: Misnesting99518
-Node: Operator Precedence Problems100630
-Node: Swallowing the Semicolon102496
-Node: Duplication of Side Effects104519
-Node: Self-Referential Macros106702
-Node: Argument Prescan109111
-Node: Newlines in Arguments112866
-Node: Conditionals113817
-Node: Conditional Uses115646
-Node: Conditional Syntax117004
-Node: Ifdef117324
-Node: If120481
-Node: Defined122785
-Node: Else124066
-Node: Elif124636
-Node: Deleted Code125925
-Node: Diagnostics127172
-Node: Line Control128721
-Node: Pragmas132496
-Node: Other Directives137250
-Node: Preprocessor Output138300
-Node: Traditional Mode141498
-Node: Traditional lexical analysis142556
-Node: Traditional macros145059
-Node: Traditional miscellany148860
-Node: Traditional warnings149856
-Node: Implementation Details152053
-Node: Implementation-defined behavior152674
-Ref: Identifier characters153424
-Node: Implementation limits156313
-Node: Obsolete Features158986
-Node: Differences from previous versions161873
-Node: Invocation166075
-Ref: Wtrigraphs170527
-Ref: dashMF175304
-Ref: fdollars-in-identifiers185046
-Node: Environment Variables194849
-Node: GNU Free Documentation License197815
-Node: Index of Directives222960
-Node: Option Index225040
-Node: Concept Index231443
+Node: Top996
+Node: Overview3601
+Node: Character sets6434
+Ref: Character sets-Footnote-18591
+Node: Initial processing8772
+Ref: trigraphs10331
+Node: Tokenization14533
+Ref: Tokenization-Footnote-121564
+Node: The preprocessing language21675
+Node: Header Files24553
+Node: Include Syntax26469
+Node: Include Operation28106
+Node: Search Path29954
+Node: Once-Only Headers33155
+Node: Alternatives to Wrapper #ifndef34814
+Node: Computed Includes36557
+Node: Wrapper Headers39715
+Node: System Headers42141
+Node: Macros44191
+Node: Object-like Macros45332
+Node: Function-like Macros48922
+Node: Macro Arguments50538
+Node: Stringification54683
+Node: Concatenation57889
+Node: Variadic Macros60997
+Node: Predefined Macros65784
+Node: Standard Predefined Macros66372
+Node: Common Predefined Macros72348
+Node: System-specific Predefined Macros92437
+Node: C++ Named Operators94460
+Node: Undefining and Redefining Macros95424
+Node: Directives Within Macro Arguments97528
+Node: Macro Pitfalls99076
+Node: Misnesting99609
+Node: Operator Precedence Problems100721
+Node: Swallowing the Semicolon102587
+Node: Duplication of Side Effects104610
+Node: Self-Referential Macros106793
+Node: Argument Prescan109202
+Node: Newlines in Arguments112956
+Node: Conditionals113907
+Node: Conditional Uses115737
+Node: Conditional Syntax117095
+Node: Ifdef117415
+Node: If120581
+Node: Defined122885
+Node: Else124168
+Node: Elif124738
+Node: Deleted Code126027
+Node: Diagnostics127274
+Node: Line Control128821
+Node: Pragmas132625
+Node: Other Directives137381
+Node: Preprocessor Output138431
+Node: Traditional Mode141632
+Node: Traditional lexical analysis142690
+Node: Traditional macros145193
+Node: Traditional miscellany148995
+Node: Traditional warnings149992
+Node: Implementation Details152189
+Node: Implementation-defined behavior152810
+Ref: Identifier characters153562
+Node: Implementation limits156446
+Node: Obsolete Features159120
+Node: Differences from previous versions162008
+Node: Invocation166216
+Ref: Wtrigraphs170668
+Ref: dashMF175443
+Ref: fdollars-in-identifiers185174
+Node: Environment Variables195019
+Node: GNU Free Documentation License197985
+Node: Index of Directives223149
+Node: Option Index225229
+Node: Concept Index231632

End Tag Table
diff --git a/gcc/doc/cppinternals.info b/gcc/doc/cppinternals.info
index a597a1bc5e..22e63846d1 100644
--- a/gcc/doc/cppinternals.info
+++ b/gcc/doc/cppinternals.info
@@ -1,12 +1,12 @@
-This is cppinternals.info, produced by makeinfo version 5.2 from
-cppinternals.texi.
+This is doc/cppinternals.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/doc/cppinternals.texi.
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
* Cpplib: (cppinternals). Cpplib internals.
END-INFO-DIR-ENTRY
-This file documents the internals of the GNU C Preprocessor.
+ This file documents the internals of the GNU C Preprocessor.
Copyright (C) 2000-2015 Free Software Foundation, Inc.
@@ -16,8 +16,8 @@ preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided also
-that the entire resulting derived work is distributed under the terms of
-a permission notice identical to this one.
+that the entire resulting derived work is distributed under the terms
+of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
@@ -46,9 +46,9 @@ preprocessor in previous versions of GCC would operate on text strings
as the fundamental unit.
This brief manual documents the internals of cpplib, and explains
-some of the tricky issues. It is intended that, along with the comments
-in the source code, a reasonably competent C programmer should be able
-to figure out what the code is doing, and why things have been
+some of the tricky issues. It is intended that, along with the
+comments in the source code, a reasonably competent C programmer should
+be able to figure out what the code is doing, and why things have been
implemented the way they have.
* Menu:
@@ -69,17 +69,17 @@ File: cppinternals.info, Node: Conventions, Next: Lexer, Prev: Top, Up: Top
Conventions
***********
-cpplib has two interfaces--one is exposed internally only, and the other
-is for both internal and external use.
+cpplib has two interfaces--one is exposed internally only, and the
+other is for both internal and external use.
The convention is that functions and types that are exposed to
-multiple files internally are prefixed with '_cpp_', and are to be found
-in the file 'internal.h'. Functions and types exposed to external
-clients are in 'cpplib.h', and prefixed with 'cpp_'. For historical
+multiple files internally are prefixed with `_cpp_', and are to be
+found in the file `internal.h'. Functions and types exposed to external
+clients are in `cpplib.h', and prefixed with `cpp_'. For historical
reasons this is no longer quite true, but we should strive to stick to
it.
- We are striving to reduce the information exposed in 'cpplib.h' to
+ We are striving to reduce the information exposed in `cpplib.h' to
the bare minimum necessary, and then to keep it there. This makes clear
exactly what external clients are entitled to assume, and allows us to
change internals in the future without worrying whether library clients
@@ -95,7 +95,7 @@ The Lexer
Overview
========
-The lexer is contained in the file 'lex.c'. It is a hand-coded lexer,
+The lexer is contained in the file `lex.c'. It is a hand-coded lexer,
and not implemented as a state machine. It can understand C, C++ and
Objective-C source code, and has been extended to allow reasonably
successful preprocessing of assembly language. The lexer does not make
@@ -104,17 +104,17 @@ them as they are encountered in a single pass of the input file. It
returns preprocessing tokens individually, not a line at a time.
It is mostly transparent to users of the library, since the library's
-interface for obtaining the next token, 'cpp_get_token', takes care of
+interface for obtaining the next token, `cpp_get_token', takes care of
lexing new tokens, handling directives, and expanding macros as
necessary. However, the lexer does expose some functionality so that
clients of the library can easily spell a given token, such as
-'cpp_spell_token' and 'cpp_token_len'. These functions are useful when
+`cpp_spell_token' and `cpp_token_len'. These functions are useful when
generating diagnostics, and for emitting the preprocessed output.
Lexing a token
==============
-Lexing of an individual token is handled by '_cpp_lex_direct' and its
+Lexing of an individual token is handled by `_cpp_lex_direct' and its
subroutines. In its current form the code is quite complicated, with
read ahead characters and such-like, since it strives to not step back
in the character stream in preparation for handling non-ASCII file
@@ -122,66 +122,66 @@ encodings. The current plan is to convert any such files to UTF-8
before processing them. This complexity is therefore unnecessary and
will be removed, so I'll not discuss it further here.
- The job of '_cpp_lex_direct' is simply to lex a token. It is not
+ The job of `_cpp_lex_direct' is simply to lex a token. It is not
responsible for issues like directive handling, returning lookahead
tokens directly, multiple-include optimization, or conditional block
-skipping. It necessarily has a minor ro^le to play in memory management
-of lexed lines. I discuss these issues in a separate section (*note
-Lexing a line::).
+skipping. It necessarily has a minor ro^le to play in memory
+management of lexed lines. I discuss these issues in a separate section
+(*note Lexing a line::).
The lexer places the token it lexes into storage pointed to by the
-variable 'cur_token', and then increments it. This variable is
+variable `cur_token', and then increments it. This variable is
important for correct diagnostic positioning. Unless a specific line
and column are passed to the diagnostic routines, they will examine the
-'line' and 'col' values of the token just before the location that
-'cur_token' points to, and use that location to report the diagnostic.
+`line' and `col' values of the token just before the location that
+`cur_token' points to, and use that location to report the diagnostic.
The lexer does not consider whitespace to be a token in its own
right. If whitespace (other than a new line) precedes a token, it sets
-the 'PREV_WHITE' bit in the token's flags. Each token has its 'line'
-and 'col' variables set to the line and column of the first character of
-the token. This line number is the line number in the translation unit,
-and can be converted to a source (file, line) pair using the line map
-code.
-
- The first token on a logical, i.e. unescaped, line has the flag 'BOL'
-set for beginning-of-line. This flag is intended for internal use, both
-to distinguish a '#' that begins a directive from one that doesn't, and
-to generate a call-back to clients that want to be notified about the
-start of every non-directive line with tokens on it. Clients cannot
-reliably determine this for themselves: the first token might be a
-macro, and the tokens of a macro expansion do not have the 'BOL' flag
-set. The macro expansion may even be empty, and the next token on the
-line certainly won't have the 'BOL' flag set.
+the `PREV_WHITE' bit in the token's flags. Each token has its `line'
+and `col' variables set to the line and column of the first character
+of the token. This line number is the line number in the translation
+unit, and can be converted to a source (file, line) pair using the line
+map code.
+
+ The first token on a logical, i.e. unescaped, line has the flag
+`BOL' set for beginning-of-line. This flag is intended for internal
+use, both to distinguish a `#' that begins a directive from one that
+doesn't, and to generate a call-back to clients that want to be
+notified about the start of every non-directive line with tokens on it.
+Clients cannot reliably determine this for themselves: the first token
+might be a macro, and the tokens of a macro expansion do not have the
+`BOL' flag set. The macro expansion may even be empty, and the next
+token on the line certainly won't have the `BOL' flag set.
New lines are treated specially; exactly how the lexer handles them
is context-dependent. The C standard mandates that directives are
terminated by the first unescaped newline character, even if it appears
in the middle of a macro expansion. Therefore, if the state variable
-'in_directive' is set, the lexer returns a 'CPP_EOF' token, which is
-normally used to indicate end-of-file, to indicate end-of-directive. In
-a directive a 'CPP_EOF' token never means end-of-file. Conveniently, if
-the caller was 'collect_args', it already handles 'CPP_EOF' as if it
-were end-of-file, and reports an error about an unterminated macro
-argument list.
+`in_directive' is set, the lexer returns a `CPP_EOF' token, which is
+normally used to indicate end-of-file, to indicate end-of-directive.
+In a directive a `CPP_EOF' token never means end-of-file.
+Conveniently, if the caller was `collect_args', it already handles
+`CPP_EOF' as if it were end-of-file, and reports an error about an
+unterminated macro argument list.
The C standard also specifies that a new line in the middle of the
arguments to a macro is treated as whitespace. This white space is
important in case the macro argument is stringified. The state variable
-'parsing_args' is nonzero when the preprocessor is collecting the
+`parsing_args' is nonzero when the preprocessor is collecting the
arguments to a macro call. It is set to 1 when looking for the opening
parenthesis to a function-like macro, and 2 when collecting the actual
arguments up to the closing parenthesis, since these two cases need to
be distinguished sometimes. One such time is here: the lexer sets the
-'PREV_WHITE' flag of a token if it meets a new line when 'parsing_args'
+`PREV_WHITE' flag of a token if it meets a new line when `parsing_args'
is set to 2. It doesn't set it if it meets a new line when
-'parsing_args' is 1, since then code like
+`parsing_args' is 1, since then code like
#define foo() bar
foo
baz
-would be output with an erroneous space before 'baz':
+would be output with an erroneous space before `baz':
foo
baz
@@ -190,87 +190,88 @@ would be output with an erroneous space before 'baz':
correct in the preprocessor; there are plenty of tests in the testsuite
for corner cases like this.
- The lexer is written to treat each of '\r', '\n', '\r\n' and '\n\r'
+ The lexer is written to treat each of `\r', `\n', `\r\n' and `\n\r'
as a single new line indicator. This allows it to transparently
preprocess MS-DOS, Macintosh and Unix files without their needing to
pass through a special filter beforehand.
- We also decided to treat a backslash, either '\' or the trigraph
-'??/', separated from one of the above newline indicators by non-comment
-whitespace only, as intending to escape the newline. It tends to be a
-typing mistake, and cannot reasonably be mistaken for anything else in
-any of the C-family grammars. Since handling it this way is not
-strictly conforming to the ISO standard, the library issues a warning
-wherever it encounters it.
+ We also decided to treat a backslash, either `\' or the trigraph
+`??/', separated from one of the above newline indicators by
+non-comment whitespace only, as intending to escape the newline. It
+tends to be a typing mistake, and cannot reasonably be mistaken for
+anything else in any of the C-family grammars. Since handling it this
+way is not strictly conforming to the ISO standard, the library issues a
+warning wherever it encounters it.
Handling newlines like this is made simpler by doing it in one place
-only. The function 'handle_newline' takes care of all newline
-characters, and 'skip_escaped_newlines' takes care of arbitrarily long
-sequences of escaped newlines, deferring to 'handle_newline' to handle
+only. The function `handle_newline' takes care of all newline
+characters, and `skip_escaped_newlines' takes care of arbitrarily long
+sequences of escaped newlines, deferring to `handle_newline' to handle
the newlines themselves.
The most painful aspect of lexing ISO-standard C and C++ is handling
trigraphs and backlash-escaped newlines. Trigraphs are processed before
any interpretation of the meaning of a character is made, and
unfortunately there is a trigraph representation for a backslash, so it
-is possible for the trigraph '??/' to introduce an escaped newline.
+is possible for the trigraph `??/' to introduce an escaped newline.
Escaped newlines are tedious because theoretically they can occur
-anywhere--between the '+' and '=' of the '+=' token, within the
-characters of an identifier, and even between the '*' and '/' that
+anywhere--between the `+' and `=' of the `+=' token, within the
+characters of an identifier, and even between the `*' and `/' that
terminates a comment. Moreover, you cannot be sure there is just
one--there might be an arbitrarily long sequence of them.
- So, for example, the routine that lexes a number, 'parse_number',
+ So, for example, the routine that lexes a number, `parse_number',
cannot assume that it can scan forwards until the first non-number
-character and be done with it, because this could be the '\' introducing
-an escaped newline, or the '?' introducing the trigraph sequence that
-represents the '\' of an escaped newline. If it encounters a '?' or
-'\', it calls 'skip_escaped_newlines' to skip over any potential escaped
-newlines before checking whether the number has been finished.
-
- Similarly code in the main body of '_cpp_lex_direct' cannot simply
-check for a '=' after a '+' character to determine whether it has a '+='
-token; it needs to be prepared for an escaped newline of some sort.
-Such cases use the function 'get_effective_char', which returns the
-first character after any intervening escaped newlines.
+character and be done with it, because this could be the `\'
+introducing an escaped newline, or the `?' introducing the trigraph
+sequence that represents the `\' of an escaped newline. If it
+encounters a `?' or `\', it calls `skip_escaped_newlines' to skip over
+any potential escaped newlines before checking whether the number has
+been finished.
+
+ Similarly code in the main body of `_cpp_lex_direct' cannot simply
+check for a `=' after a `+' character to determine whether it has a
+`+=' token; it needs to be prepared for an escaped newline of some
+sort. Such cases use the function `get_effective_char', which returns
+the first character after any intervening escaped newlines.
The lexer needs to keep track of the correct column position,
-including counting tabs as specified by the '-ftabstop=' option. This
+including counting tabs as specified by the `-ftabstop=' option. This
should be done even within C-style comments; they can appear in the
middle of a line, and we want to report diagnostics in the correct
position for text appearing after the end of the comment.
- Some identifiers, such as '__VA_ARGS__' and poisoned identifiers, may
-be invalid and require a diagnostic. However, if they appear in a macro
-expansion we don't want to complain with each use of the macro. It is
-therefore best to catch them during the lexing stage, in
-'parse_identifier'. In both cases, whether a diagnostic is needed or
+ Some identifiers, such as `__VA_ARGS__' and poisoned identifiers,
+may be invalid and require a diagnostic. However, if they appear in a
+macro expansion we don't want to complain with each use of the macro.
+It is therefore best to catch them during the lexing stage, in
+`parse_identifier'. In both cases, whether a diagnostic is needed or
not is dependent upon the lexer's state. For example, we don't want to
issue a diagnostic for re-poisoning a poisoned identifier, or for using
-'__VA_ARGS__' in the expansion of a variable-argument macro. Therefore
-'parse_identifier' makes use of state flags to determine whether a
+`__VA_ARGS__' in the expansion of a variable-argument macro. Therefore
+`parse_identifier' makes use of state flags to determine whether a
diagnostic is appropriate. Since we change state on a per-token basis,
and don't lex whole lines at a time, this is not a problem.
Another place where state flags are used to change behavior is whilst
-lexing header names. Normally, a '<' would be lexed as a single token.
-After a '#include' directive, though, it should be lexed as a single
-token as far as the nearest '>' character. Note that we don't allow the
-terminators of header names to be escaped; the first '"' or '>'
+lexing header names. Normally, a `<' would be lexed as a single token.
+After a `#include' directive, though, it should be lexed as a single
+token as far as the nearest `>' character. Note that we don't allow
+the terminators of header names to be escaped; the first `"' or `>'
terminates the header name.
Interpretation of some character sequences depends upon whether we
are lexing C, C++ or Objective-C, and on the revision of the standard in
-force. For example, '::' is a single token in C++, but in C it is two
-separate ':' tokens and almost certainly a syntax error. Such cases are
-handled by '_cpp_lex_direct' based upon command-line flags stored in the
-'cpp_options' structure.
+force. For example, `::' is a single token in C++, but in C it is two
+separate `:' tokens and almost certainly a syntax error. Such cases
+are handled by `_cpp_lex_direct' based upon command-line flags stored
+in the `cpp_options' structure.
Once a token has been lexed, it leads an independent existence. The
spelling of numbers, identifiers and strings is copied to permanent
storage from the original input buffer, so a token remains valid and
-correct even if its source buffer is freed with '_cpp_pop_buffer'. The
+correct even if its source buffer is freed with `_cpp_pop_buffer'. The
storage holding the spellings of such tokens remains until the client
program calls cpp_destroy, probably at the end of the translation unit.
@@ -287,9 +288,9 @@ to cpplib itself internally.
token stream. For example, after the name of a function-like macro, it
wants to check the next token to see if it is an opening parenthesis.
Another example is that, after reading the first few tokens of a
-'#pragma' directive and not recognizing it as a registered pragma, it
+`#pragma' directive and not recognizing it as a registered pragma, it
wants to backtrack and allow the user-defined handler for unknown
-pragmas to access the full '#pragma' token stream. The stand-alone
+pragmas to access the full `#pragma' token stream. The stand-alone
preprocessor wants to be able to test the current token with the
previous one to see if a space needs to be inserted to preserve their
separate tokenization upon re-lexing (paste avoidance), so it needs to
@@ -302,8 +303,8 @@ to jump back to a prior position in that stream if necessary.
preprocessor lex all tokens on a line consecutively into a token buffer,
which I call a "token run", and when meeting an unescaped new line
(newlines within comments do not count either), to start lexing back at
-the beginning of the run. Note that we do _not_ lex a line of tokens at
-once; if we did that 'parse_identifier' would not have state flags
+the beginning of the run. Note that we do _not_ lex a line of tokens
+at once; if we did that `parse_identifier' would not have state flags
available to warn about invalid identifiers (*note Invalid
identifiers::).
@@ -311,25 +312,25 @@ identifiers::).
line is valid, but since each logical line overwrites the tokens of the
previous line, tokens from prior lines are unavailable. In particular,
since a directive only occupies a single logical line, this means that
-the directive handlers like the '#pragma' handler can jump around in the
-directive's tokens if necessary.
+the directive handlers like the `#pragma' handler can jump around in
+the directive's tokens if necessary.
Two issues remain: what about tokens that arise from macro
-expansions, and what happens when we have a long line that overflows the
-token run?
+expansions, and what happens when we have a long line that overflows
+the token run?
Since we promise clients that we preserve the validity of pointers
that we have already returned for tokens that appeared earlier in the
-line, we cannot reallocate the run. Instead, on overflow it is expanded
-by chaining a new token run on to the end of the existing one.
+line, we cannot reallocate the run. Instead, on overflow it is
+expanded by chaining a new token run on to the end of the existing one.
The tokens forming a macro's replacement list are collected by the
-'#define' handler, and placed in storage that is only freed by
-'cpp_destroy'. So if a macro is expanded in the line of tokens, the
+`#define' handler, and placed in storage that is only freed by
+`cpp_destroy'. So if a macro is expanded in the line of tokens, the
pointers to the tokens of its expansion that are returned will always
remain valid. However, macros are a little trickier than that, since
they give rise to three sources of fresh tokens. They are the built-in
-macros like '__LINE__', and the '#' and '##' operators for
+macros like `__LINE__', and the `#' and `##' operators for
stringification and token pasting. I handled this by allocating space
for these tokens from the lexer's token run chain. This means they
automatically receive the same lifetime guarantees as lexed tokens, and
@@ -340,20 +341,20 @@ management issues, but not all. The opening parenthesis after a
function-like macro name might lie on a different line, and the front
ends definitely want the ability to look ahead past the end of the
current line. So cpplib only moves back to the start of the token run
-at the end of a line if the variable 'keep_tokens' is zero.
+at the end of a line if the variable `keep_tokens' is zero.
Line-buffering is quite natural for the preprocessor, and as a result
the only time cpplib needs to increment this variable is whilst looking
for the opening parenthesis to, and reading the arguments of, a
-function-like macro. In the near future cpplib will export an interface
-to increment and decrement this variable, so that clients can share full
-control over the lifetime of token pointers too.
+function-like macro. In the near future cpplib will export an
+interface to increment and decrement this variable, so that clients can
+share full control over the lifetime of token pointers too.
- The routine '_cpp_lex_token' handles moving to new token runs,
-calling '_cpp_lex_direct' to lex new tokens, or returning
+ The routine `_cpp_lex_token' handles moving to new token runs,
+calling `_cpp_lex_direct' to lex new tokens, or returning
previously-lexed tokens if we stepped back in the token stream. It also
-checks each token for the 'BOL' flag, which might indicate a directive
+checks each token for the `BOL' flag, which might indicate a directive
that needs to be handled, or require a start-of-line call-back to be
-made. '_cpp_lex_token' also handles skipping over tokens in failed
+made. `_cpp_lex_token' also handles skipping over tokens in failed
conditional blocks, and invalidates the control macro of the
multiple-include optimization if a token was successfully lexed outside
a directive. In other words, its callers do not need to concern
@@ -367,10 +368,10 @@ Hash Nodes
When cpplib encounters an "identifier", it generates a hash code for it
and stores it in the hash table. By "identifier" we mean tokens with
-type 'CPP_NAME'; this includes identifiers in the usual C sense, as well
-as keywords, directive names, macro names and so on. For example, all
-of 'pragma', 'int', 'foo' and '__GNUC__' are identifiers and hashed when
-lexed.
+type `CPP_NAME'; this includes identifiers in the usual C sense, as
+well as keywords, directive names, macro names and so on. For example,
+all of `pragma', `int', `foo' and `__GNUC__' are identifiers and hashed
+when lexed.
Each node in the hash table contain various information about the
identifier it represents. For example, its length and type. At any one
@@ -379,46 +380,46 @@ time, each identifier falls into exactly one of three categories:
* Macros
These have been declared to be macros, either on the command line
- or with '#define'. A few, such as '__TIME__' are built-ins entered
- in the hash table during initialization. The hash node for a
- normal macro points to a structure with more information about the
- macro, such as whether it is function-like, how many arguments it
- takes, and its expansion. Built-in macros are flagged as special,
- and instead contain an enum indicating which of the various
- built-in macros it is.
+ or with `#define'. A few, such as `__TIME__' are built-ins
+ entered in the hash table during initialization. The hash node
+ for a normal macro points to a structure with more information
+ about the macro, such as whether it is function-like, how many
+ arguments it takes, and its expansion. Built-in macros are
+ flagged as special, and instead contain an enum indicating which
+ of the various built-in macros it is.
* Assertions
- Assertions are in a separate namespace to macros. To enforce this,
- cpp actually prepends a '#' character before hashing and entering
- it in the hash table. An assertion's node points to a chain of
- answers to that assertion.
+ Assertions are in a separate namespace to macros. To enforce
+ this, cpp actually prepends a `#' character before hashing and
+ entering it in the hash table. An assertion's node points to a
+ chain of answers to that assertion.
* Void
Everything else falls into this category--an identifier that is not
currently a macro, or a macro that has since been undefined with
- '#undef'.
+ `#undef'.
When preprocessing C++, this category also includes the named
- operators, such as 'xor'. In expressions these behave like the
+ operators, such as `xor'. In expressions these behave like the
operators they represent, but in contexts where the spelling of a
token matters they are spelt differently. This spelling
distinction is relevant when they are operands of the stringizing
- and pasting macro operators '#' and '##'. Named operator hash
+ and pasting macro operators `#' and `##'. Named operator hash
nodes are flagged, both to catch the spelling distinction and to
prevent them from being defined as macros.
The same identifiers share the same hash node. Since each identifier
token, after lexing, contains a pointer to its hash node, this is used
to provide rapid lookup of various information. For example, when
-parsing a '#define' statement, CPP flags each argument's identifier hash
-node with the index of that argument. This makes duplicated argument
-checking an O(1) operation for each argument. Similarly, for each
-identifier in the macro's expansion, lookup to see if it is an argument,
-and which argument it is, is also an O(1) operation. Further, each
-directive name, such as 'endif', has an associated directive enum stored
-in its hash node, so that directive lookup is also O(1).
+parsing a `#define' statement, CPP flags each argument's identifier
+hash node with the index of that argument. This makes duplicated
+argument checking an O(1) operation for each argument. Similarly, for
+each identifier in the macro's expansion, lookup to see if it is an
+argument, and which argument it is, is also an O(1) operation. Further,
+each directive name, such as `endif', has an associated directive enum
+stored in its hash node, so that directive lookup is also O(1).

File: cppinternals.info, Node: Macro Expansion, Next: Token Spacing, Prev: Hash Nodes, Up: Top
@@ -431,29 +432,29 @@ and situations that render what you thought was a nifty way to optimize
the preprocessor's expansion algorithm wrong in quite subtle ways.
I strongly recommend you have a good grasp of how the C and C++
-standards require macros to be expanded before diving into this section,
-let alone the code!. If you don't have a clear mental picture of how
-things like nested macro expansion, stringification and token pasting
-are supposed to work, damage to your sanity can quickly result.
+standards require macros to be expanded before diving into this
+section, let alone the code!. If you don't have a clear mental picture
+of how things like nested macro expansion, stringification and token
+pasting are supposed to work, damage to your sanity can quickly result.
Internal representation of macros
=================================
The preprocessor stores macro expansions in tokenized form. This saves
-repeated lexing passes during expansion, at the cost of a small increase
-in memory consumption on average. The tokens are stored contiguously in
-memory, so a pointer to the first one and a token count is all you need
-to get the replacement list of a macro.
+repeated lexing passes during expansion, at the cost of a small
+increase in memory consumption on average. The tokens are stored
+contiguously in memory, so a pointer to the first one and a token count
+is all you need to get the replacement list of a macro.
If the macro is a function-like macro the preprocessor also stores
its parameters, in the form of an ordered list of pointers to the hash
table entry of each parameter's identifier. Further, in the macro's
stored expansion each occurrence of a parameter is replaced with a
-special token of type 'CPP_MACRO_ARG'. Each such token holds the index
-of the parameter it represents in the parameter list, which allows rapid
-replacement of parameters with their arguments during expansion.
+special token of type `CPP_MACRO_ARG'. Each such token holds the index
+of the parameter it represents in the parameter list, which allows
+rapid replacement of parameters with their arguments during expansion.
Despite this optimization it is still necessary to store the original
-parameters to the macro, both for dumping with e.g., '-dD', and to warn
+parameters to the macro, both for dumping with e.g., `-dD', and to warn
about non-trivial macro redefinitions when the parameter names have
changed.
@@ -461,56 +462,56 @@ Macro expansion overview
========================
The preprocessor maintains a "context stack", implemented as a linked
-list of 'cpp_context' structures, which together represent the macro
-expansion state at any one time. The 'struct cpp_reader' member
-variable 'context' points to the current top of this stack. The top
+list of `cpp_context' structures, which together represent the macro
+expansion state at any one time. The `struct cpp_reader' member
+variable `context' points to the current top of this stack. The top
normally holds the unexpanded replacement list of the innermost macro
under expansion, except when cpplib is about to pre-expand an argument,
in which case it holds that argument's unexpanded tokens.
When there are no macros under expansion, cpplib is in "base
-context". All contexts other than the base context contain a contiguous
-list of tokens delimited by a starting and ending token. When not in
-base context, cpplib obtains the next token from the list of the top
-context. If there are no tokens left in the list, it pops that context
-off the stack, and subsequent ones if necessary, until an unexhausted
-context is found or it returns to base context. In base context, cpplib
-reads tokens directly from the lexer.
+context". All contexts other than the base context contain a
+contiguous list of tokens delimited by a starting and ending token.
+When not in base context, cpplib obtains the next token from the list
+of the top context. If there are no tokens left in the list, it pops
+that context off the stack, and subsequent ones if necessary, until an
+unexhausted context is found or it returns to base context. In base
+context, cpplib reads tokens directly from the lexer.
If it encounters an identifier that is both a macro and enabled for
expansion, cpplib prepares to push a new context for that macro on the
-stack by calling the routine 'enter_macro_context'. When this routine
+stack by calling the routine `enter_macro_context'. When this routine
returns, the new context will contain the unexpanded tokens of the
replacement list of that macro. In the case of function-like macros,
-'enter_macro_context' also replaces any parameters in the replacement
-list, stored as 'CPP_MACRO_ARG' tokens, with the appropriate macro
+`enter_macro_context' also replaces any parameters in the replacement
+list, stored as `CPP_MACRO_ARG' tokens, with the appropriate macro
argument. If the standard requires that the parameter be replaced with
its expanded argument, the argument will have been fully macro expanded
first.
- 'enter_macro_context' also handles special macros like '__LINE__'.
+ `enter_macro_context' also handles special macros like `__LINE__'.
Although these macros expand to a single token which cannot contain any
-further macros, for reasons of token spacing (*note Token Spacing::) and
-simplicity of implementation, cpplib handles these special macros by
-pushing a context containing just that one token.
-
- The final thing that 'enter_macro_context' does before returning is
-to mark the macro disabled for expansion (except for special macros like
-'__TIME__'). The macro is re-enabled when its context is later popped
-from the context stack, as described above. This strict ordering
-ensures that a macro is disabled whilst its expansion is being scanned,
-but that it is _not_ disabled whilst any arguments to it are being
-expanded.
+further macros, for reasons of token spacing (*note Token Spacing::)
+and simplicity of implementation, cpplib handles these special macros
+by pushing a context containing just that one token.
+
+ The final thing that `enter_macro_context' does before returning is
+to mark the macro disabled for expansion (except for special macros
+like `__TIME__'). The macro is re-enabled when its context is later
+popped from the context stack, as described above. This strict
+ordering ensures that a macro is disabled whilst its expansion is being
+scanned, but that it is _not_ disabled whilst any arguments to it are
+being expanded.
Scanning the replacement list for macros to expand
==================================================
-The C standard states that, after any parameters have been replaced with
-their possibly-expanded arguments, the replacement list is scanned for
-nested macros. Further, any identifiers in the replacement list that
-are not expanded during this scan are never again eligible for expansion
-in the future, if the reason they were not expanded is that the macro in
-question was disabled.
+The C standard states that, after any parameters have been replaced
+with their possibly-expanded arguments, the replacement list is scanned
+for nested macros. Further, any identifiers in the replacement list
+that are not expanded during this scan are never again eligible for
+expansion in the future, if the reason they were not expanded is that
+the macro in question was disabled.
Clearly this latter condition can only apply to tokens resulting from
argument pre-expansion. Other tokens never have an opportunity to be
@@ -529,27 +530,27 @@ looking for the _next_ token do we pop it off the stack and drop to a
lower context. This makes backing up by one token easy, but more
importantly ensures that the macro corresponding to the current context
is still disabled when we are considering the last token of its
-replacement list for expansion (or indeed expanding it). As an example,
-which illustrates many of the points above, consider
+replacement list for expansion (or indeed expanding it). As an
+example, which illustrates many of the points above, consider
#define foo(x) bar x
foo(foo) (2)
-which fully expands to 'bar foo (2)'. During pre-expansion of the
-argument, 'foo' does not expand even though the macro is enabled, since
+which fully expands to `bar foo (2)'. During pre-expansion of the
+argument, `foo' does not expand even though the macro is enabled, since
it has no following parenthesis [pre-expansion of an argument only uses
tokens from that argument; it cannot take tokens from whatever follows
-the macro invocation]. This still leaves the argument token 'foo'
+the macro invocation]. This still leaves the argument token `foo'
eligible for future expansion. Then, when re-scanning after argument
-replacement, the token 'foo' is rejected for expansion, and marked
-ineligible for future expansion, since the macro is now disabled. It is
-disabled because the replacement list 'bar foo' of the macro is still on
-the context stack.
+replacement, the token `foo' is rejected for expansion, and marked
+ineligible for future expansion, since the macro is now disabled. It
+is disabled because the replacement list `bar foo' of the macro is
+still on the context stack.
If instead the algorithm looked for an opening parenthesis first and
then tested whether the macro were disabled it would be subtly wrong.
-In the example above, the replacement list of 'foo' would be popped in
-the process of finding the parenthesis, re-enabling 'foo' and expanding
+In the example above, the replacement list of `foo' would be popped in
+the process of finding the parenthesis, re-enabling `foo' and expanding
it a second time.
Looking for a function-like macro's opening parenthesis
@@ -559,18 +560,18 @@ Function-like macros only expand when immediately followed by a
parenthesis. To do this cpplib needs to temporarily disable macros and
read the next token. Unfortunately, because of spacing issues (*note
Token Spacing::), there can be fake padding tokens in-between, and if
-the next real token is not a parenthesis cpplib needs to be able to back
-up that one token as well as retain the information in any intervening
-padding tokens.
+the next real token is not a parenthesis cpplib needs to be able to
+back up that one token as well as retain the information in any
+intervening padding tokens.
Backing up more than one token when macros are involved is not
permitted by cpplib, because in general it might involve issues like
restoring popped contexts onto the context stack, which are too hard.
-Instead, searching for the parenthesis is handled by a special function,
-'funlike_invocation_p', which remembers padding information as it reads
-tokens. If the next real token is not an opening parenthesis, it backs
-up that one token, and then pushes an extra context just containing the
-padding information if necessary.
+Instead, searching for the parenthesis is handled by a special
+function, `funlike_invocation_p', which remembers padding information
+as it reads tokens. If the next real token is not an opening
+parenthesis, it backs up that one token, and then pushes an extra
+context just containing the padding information if necessary.
Marking tokens ineligible for future expansion
==============================================
@@ -578,12 +579,12 @@ Marking tokens ineligible for future expansion
As discussed above, cpplib needs a way of marking tokens as
unexpandable. Since the tokens cpplib handles are read-only once they
have been lexed, it instead makes a copy of the token and adds the flag
-'NO_EXPAND' to the copy.
+`NO_EXPAND' to the copy.
For efficiency and to simplify memory management by avoiding having
to remember to free these tokens, they are allocated as temporary tokens
from the lexer's current token run (*note Lexing a line::) using the
-function '_cpp_temp_token'. The tokens are then re-used once the
+function `_cpp_temp_token'. The tokens are then re-used once the
current line of tokens has been read in.
This might sound unsafe. However, tokens runs are not re-used at the
@@ -618,20 +619,20 @@ both for aesthetic reasons and because it causes problems for people who
still try to abuse the preprocessor for things like Fortran source and
Makefiles.
- For now, just notice that when tokens are added (or removed, as shown
-by the 'EMPTY' example) from the original lexed token stream, we need to
-check for accidental token pasting. We call this "paste avoidance".
-Token addition and removal can only occur because of macro expansion,
-but accidental pasting can occur in many places: both before and after
-each macro replacement, each argument replacement, and additionally each
-token created by the '#' and '##' operators.
-
- Look at how the preprocessor gets whitespace output correct normally.
-The 'cpp_token' structure contains a flags byte, and one of those flags
-is 'PREV_WHITE'. This is flagged by the lexer, and indicates that the
-token was preceded by whitespace of some form other than a new line.
-The stand-alone preprocessor can use this flag to decide whether to
-insert a space between tokens in the output.
+ For now, just notice that when tokens are added (or removed, as
+shown by the `EMPTY' example) from the original lexed token stream, we
+need to check for accidental token pasting. We call this "paste
+avoidance". Token addition and removal can only occur because of macro
+expansion, but accidental pasting can occur in many places: both before
+and after each macro replacement, each argument replacement, and
+additionally each token created by the `#' and `##' operators.
+
+ Look at how the preprocessor gets whitespace output correct
+normally. The `cpp_token' structure contains a flags byte, and one of
+those flags is `PREV_WHITE'. This is flagged by the lexer, and
+indicates that the token was preceded by whitespace of some form other
+than a new line. The stand-alone preprocessor can use this flag to
+decide whether to insert a space between tokens in the output.
Now consider the result of the following macro expansion:
@@ -639,39 +640,40 @@ insert a space between tokens in the output.
sum = add (1,2, 3);
==> sum = 1 + 2 +3;
- The interesting thing here is that the tokens '1' and '2' are output
-with a preceding space, and '3' is output without a preceding space, but
-when lexed none of these tokens had that property. Careful
-consideration reveals that '1' gets its preceding whitespace from the
-space preceding 'add' in the macro invocation, _not_ replacement list.
-'2' gets its whitespace from the space preceding the parameter 'y' in
-the macro replacement list, and '3' has no preceding space because
-parameter 'z' has none in the replacement list.
+ The interesting thing here is that the tokens `1' and `2' are output
+with a preceding space, and `3' is output without a preceding space,
+but when lexed none of these tokens had that property. Careful
+consideration reveals that `1' gets its preceding whitespace from the
+space preceding `add' in the macro invocation, _not_ replacement list.
+`2' gets its whitespace from the space preceding the parameter `y' in
+the macro replacement list, and `3' has no preceding space because
+parameter `z' has none in the replacement list.
Once lexed, tokens are effectively fixed and cannot be altered, since
pointers to them might be held in many places, in particular by
in-progress macro expansions. So instead of modifying the two tokens
-above, the preprocessor inserts a special token, which I call a "padding
-token", into the token stream to indicate that spacing of the subsequent
-token is special. The preprocessor inserts padding tokens in front of
-every macro expansion and expanded macro argument. These point to a
-"source token" from which the subsequent real token should inherit its
-spacing. In the above example, the source tokens are 'add' in the macro
-invocation, and 'y' and 'z' in the macro replacement list, respectively.
-
- It is quite easy to get multiple padding tokens in a row, for example
-if a macro's first replacement token expands straight into another
-macro.
+above, the preprocessor inserts a special token, which I call a
+"padding token", into the token stream to indicate that spacing of the
+subsequent token is special. The preprocessor inserts padding tokens
+in front of every macro expansion and expanded macro argument. These
+point to a "source token" from which the subsequent real token should
+inherit its spacing. In the above example, the source tokens are `add'
+in the macro invocation, and `y' and `z' in the macro replacement list,
+respectively.
+
+ It is quite easy to get multiple padding tokens in a row, for
+example if a macro's first replacement token expands straight into
+another macro.
#define foo bar
#define bar baz
[foo]
==> [baz]
- Here, two padding tokens are generated with sources the 'foo' token
-between the brackets, and the 'bar' token from foo's replacement list,
-respectively. Clearly the first padding token is the one to use, so the
-output code should contain a rule that the first padding token in a
+ Here, two padding tokens are generated with sources the `foo' token
+between the brackets, and the `bar' token from foo's replacement list,
+respectively. Clearly the first padding token is the one to use, so
+the output code should contain a rule that the first padding token in a
sequence is the one that matters.
But what if a macro expansion is left? Adjusting the above example
@@ -683,13 +685,13 @@ slightly:
[foo] EMPTY;
==> [ baz] ;
- As shown, now there should be a space before 'baz' and the semicolon
+ As shown, now there should be a space before `baz' and the semicolon
in the output.
- The rules we decided above fail for 'baz': we generate three padding
-tokens, one per macro invocation, before the token 'baz'. We would then
-have it take its spacing from the first of these, which carries source
-token 'foo' with no leading space.
+ The rules we decided above fail for `baz': we generate three padding
+tokens, one per macro invocation, before the token `baz'. We would
+then have it take its spacing from the first of these, which carries
+source token `foo' with no leading space.
It is vital that cpplib get spacing correct in these examples since
any of these macro expansions could be stringified, where spacing
@@ -697,11 +699,11 @@ matters.
So, this demonstrates that not just entering macro and argument
expansions, but leaving them requires special handling too. I made
-cpplib insert a padding token with a 'NULL' source token when leaving
+cpplib insert a padding token with a `NULL' source token when leaving
macro expansions, as well as after each replaced argument in a macro's
replacement list. It also inserts appropriate padding tokens on either
-side of tokens created by the '#' and '##' operators. I expanded the
-rule so that, if we see a padding token with a 'NULL' source token,
+side of tokens created by the `#' and `##' operators. I expanded the
+rule so that, if we see a padding token with a `NULL' source token,
_and_ that source token has no leading space, then we behave as if we
have seen no padding tokens at all. A quick check shows this rule will
then get the above example correct as well.
@@ -713,7 +715,7 @@ implementation of paste avoidance easy: wherever the stand-alone
preprocessor is fixing up spacing because of padding tokens, and it
turns out that no space is needed, it has to take the extra step to
check that a space is not needed after all to avoid an accidental paste.
-The function 'cpp_avoid_paste' advises whether a space is required
+The function `cpp_avoid_paste' advises whether a space is required
between two consecutive tokens. To avoid excessive spacing, it tries
hard to only require a space if one is likely to be necessary, but for
reasons of efficiency it is slightly conservative and might recommend a
@@ -732,6 +734,7 @@ There are three reasonable requirements a cpplib client might have for
the line number of a token passed to it:
* The source line it was lexed on.
+
* The line it is output on. This can be different to the line it was
lexed on if, for example, there are intervening escaped newlines or
C-style comments. For example:
@@ -746,14 +749,14 @@ the line number of a token passed to it:
name, or possibly the line of the closing parenthesis in the case
of function-like macro expansion.
- The 'cpp_token' structure contains 'line' and 'col' members. The
+ The `cpp_token' structure contains `line' and `col' members. The
lexer fills these in with the line and column of the first character of
the token. Consequently, but maybe unexpectedly, a token from the
replacement list of a macro expansion carries the location of the token
-within the '#define' directive, because cpplib expands a macro by
+within the `#define' directive, because cpplib expands a macro by
returning pointers to the tokens in its replacement list. The current
-implementation of cpplib assigns tokens created from built-in macros and
-the '#' and '##' operators the location of the most recently lexed
+implementation of cpplib assigns tokens created from built-in macros
+and the `#' and `##' operators the location of the most recently lexed
token. This is a because they are allocated from the lexer's token
runs, and because of the way the diagnostic routines infer the
appropriate location to report.
@@ -775,10 +778,10 @@ line other than the first.
To solve these issues, cpplib provides a callback that is generated
whenever it lexes a preprocessing token that starts a new logical line
-other than a directive. It passes this token (which may be a 'CPP_EOF'
+other than a directive. It passes this token (which may be a `CPP_EOF'
token indicating the end of the translation unit) to the callback
-routine, which can then use the line and column of this token to produce
-correct output.
+routine, which can then use the line and column of this token to
+produce correct output.
Representation of line numbers
==============================
@@ -798,14 +801,15 @@ starts counting from one.
translation unit. With some simple infrastructure, it is straight
forward to map from this to the original source file and line number
pair, saving space whenever line number information needs to be saved.
-The code the implements this mapping lies in the files 'line-map.c' and
-'line-map.h'.
+The code the implements this mapping lies in the files `line-map.c' and
+`line-map.h'.
Command-line macros and assertions are implemented by pushing a
-buffer containing the right hand side of an equivalent '#define' or
-'#assert' directive. Some built-in macros are handled similarly. Since
-these are all processed before the first line of the main input file, it
-will typically have an assigned line closer to twenty than to one.
+buffer containing the right hand side of an equivalent `#define' or
+`#assert' directive. Some built-in macros are handled similarly.
+Since these are all processed before the first line of the main input
+file, it will typically have an assigned line closer to twenty than to
+one.

File: cppinternals.info, Node: Guard Macros, Next: Files, Prev: Line Numbering, Up: Top
@@ -822,7 +826,7 @@ Header files are often of the form
to prevent the compiler from processing them more than once. The
preprocessor notices such header files, so that if the header file
-appears in a subsequent '#include' directive and 'FOO' is defined, then
+appears in a subsequent `#include' directive and `FOO' is defined, then
it is ignored and it doesn't preprocess or even re-open the file a
second time. This is referred to as the "multiple include
optimization".
@@ -833,12 +837,12 @@ inclusion would result in no tokens to return, and no relevant
directives to process. Therefore the current implementation imposes
requirements and makes some allowances as follows:
- 1. There must be no tokens outside the controlling '#if'-'#endif'
+ 1. There must be no tokens outside the controlling `#if'-`#endif'
pair, but whitespace and comments are permitted.
- 2. There must be no directives outside the controlling directive pair,
- but the "null directive" (a line containing nothing other than a
- single '#' and possibly whitespace) is permitted.
+ 2. There must be no directives outside the controlling directive
+ pair, but the "null directive" (a line containing nothing other
+ than a single `#' and possibly whitespace) is permitted.
3. The opening directive must be of the form
@@ -848,68 +852,70 @@ requirements and makes some allowances as follows:
#if !defined FOO [equivalently, #if !defined(FOO)]
- 4. In the second form above, the tokens forming the '#if' expression
+ 4. In the second form above, the tokens forming the `#if' expression
must have come directly from the source file--no macro expansion
must have been involved. This is because macro definitions can
- change, and tracking whether or not a relevant change has been made
- is not worth the implementation cost.
+ change, and tracking whether or not a relevant change has been
+ made is not worth the implementation cost.
- 5. There can be no '#else' or '#elif' directives at the outer
+ 5. There can be no `#else' or `#elif' directives at the outer
conditional block level, because they would probably contain
something of interest to a subsequent pass.
First, when pushing a new file on the buffer stack,
-'_stack_include_file' sets the controlling macro 'mi_cmacro' to 'NULL',
-and sets 'mi_valid' to 'true'. This indicates that the preprocessor has
-not yet encountered anything that would invalidate the multiple-include
-optimization. As described in the next few paragraphs, these two
-variables having these values effectively indicates top-of-file.
+`_stack_include_file' sets the controlling macro `mi_cmacro' to `NULL',
+and sets `mi_valid' to `true'. This indicates that the preprocessor
+has not yet encountered anything that would invalidate the
+multiple-include optimization. As described in the next few
+paragraphs, these two variables having these values effectively
+indicates top-of-file.
When about to return a token that is not part of a directive,
-'_cpp_lex_token' sets 'mi_valid' to 'false'. This enforces the
+`_cpp_lex_token' sets `mi_valid' to `false'. This enforces the
constraint that tokens outside the controlling conditional block
invalidate the optimization.
- The 'do_if', when appropriate, and 'do_ifndef' directive handlers
-pass the controlling macro to the function 'push_conditional'. cpplib
+ The `do_if', when appropriate, and `do_ifndef' directive handlers
+pass the controlling macro to the function `push_conditional'. cpplib
maintains a stack of nested conditional blocks, and after processing
-every opening conditional this function pushes an 'if_stack' structure
+every opening conditional this function pushes an `if_stack' structure
onto the stack. In this structure it records the controlling macro for
the block, provided there is one and we're at top-of-file (as described
-above). If an '#elif' or '#else' directive is encountered, the
-controlling macro for that block is cleared to 'NULL'. Otherwise, it
-survives until the '#endif' closing the block, upon which 'do_endif'
-sets 'mi_valid' to true and stores the controlling macro in 'mi_cmacro'.
+above). If an `#elif' or `#else' directive is encountered, the
+controlling macro for that block is cleared to `NULL'. Otherwise, it
+survives until the `#endif' closing the block, upon which `do_endif'
+sets `mi_valid' to true and stores the controlling macro in `mi_cmacro'.
- '_cpp_handle_directive' clears 'mi_valid' when processing any
+ `_cpp_handle_directive' clears `mi_valid' when processing any
directive other than an opening conditional and the null directive.
With this, and requiring top-of-file to record a controlling macro, and
-no '#else' or '#elif' for it to survive and be copied to 'mi_cmacro' by
-'do_endif', we have enforced the absence of directives outside the main
+no `#else' or `#elif' for it to survive and be copied to `mi_cmacro' by
+`do_endif', we have enforced the absence of directives outside the main
conditional block for the optimization to be on.
- Note that whilst we are inside the conditional block, 'mi_valid' is
-likely to be reset to 'false', but this does not matter since the
-closing '#endif' restores it to 'true' if appropriate.
+ Note that whilst we are inside the conditional block, `mi_valid' is
+likely to be reset to `false', but this does not matter since the
+closing `#endif' restores it to `true' if appropriate.
- Finally, since '_cpp_lex_direct' pops the file off the buffer stack
-at 'EOF' without returning a token, if the '#endif' directive was not
-followed by any tokens, 'mi_valid' is 'true' and '_cpp_pop_file_buffer'
+ Finally, since `_cpp_lex_direct' pops the file off the buffer stack
+at `EOF' without returning a token, if the `#endif' directive was not
+followed by any tokens, `mi_valid' is `true' and `_cpp_pop_file_buffer'
remembers the controlling macro associated with the file. Subsequent
-calls to 'stack_include_file' result in no buffer being pushed if the
+calls to `stack_include_file' result in no buffer being pushed if the
controlling macro is defined, effecting the optimization.
A quick word on how we handle the
#if !defined FOO
-case. '_cpp_parse_expr' and 'parse_defined' take steps to see whether
-the three stages '!', 'defined-expression' and 'end-of-directive' occur
-in order in a '#if' expression. If so, they return the guard macro to
-'do_if' in the variable 'mi_ind_cmacro', and otherwise set it to 'NULL'.
-'enter_macro_context' sets 'mi_valid' to false, so if a macro was
-expanded whilst parsing any part of the expression, then the top-of-file
-test in 'push_conditional' fails and the optimization is turned off.
+case. `_cpp_parse_expr' and `parse_defined' take steps to see whether
+the three stages `!', `defined-expression' and `end-of-directive' occur
+in order in a `#if' expression. If so, they return the guard macro to
+`do_if' in the variable `mi_ind_cmacro', and otherwise set it to `NULL'.
+`enter_macro_context' sets `mi_valid' to false, so if a macro was
+expanded whilst parsing any part of the expression, then the
+top-of-file test in `push_conditional' fails and the optimization is
+turned off.

File: cppinternals.info, Node: Files, Next: Concept Index, Prev: Guard Macros, Up: Top
@@ -918,13 +924,13 @@ File Handling
*************
Fairly obviously, the file handling code of cpplib resides in the file
-'files.c'. It takes care of the details of file searching, opening,
+`files.c'. It takes care of the details of file searching, opening,
reading and caching, for both the main source file and all the headers
it recursively includes.
The basic strategy is to minimize the number of system calls. On
-many systems, the basic 'open ()' and 'fstat ()' system calls can be
-quite expensive. For every '#include'-d file, we need to try all the
+many systems, the basic `open ()' and `fstat ()' system calls can be
+quite expensive. For every `#include'-d file, we need to try all the
directories in the search path until we find a match. Some projects,
such as glibc, pass twenty or thirty include paths on the command line,
so this can rapidly become time consuming.
@@ -936,45 +942,45 @@ repeating the filesystem queries whilst searching for the correct file.
For each file we try to open, we store the constructed path in a
splay tree. This path first undergoes simplification by the function
-'_cpp_simplify_pathname'. For example, '/usr/include/bits/../foo.h' is
-simplified to '/usr/include/foo.h' before we enter it in the splay tree
-and try to 'open ()' the file. CPP will then find subsequent uses of
-'foo.h', even as '/usr/include/foo.h', in the splay tree and save system
-calls.
-
- Further, it is likely the file contents have also been cached, saving
-a 'read ()' system call. We don't bother caching the contents of header
-files that are re-inclusion protected, and whose re-inclusion macro is
-defined when we leave the header file for the first time. If the host
-supports it, we try to map suitably large files into memory, rather than
-reading them in directly.
+`_cpp_simplify_pathname'. For example, `/usr/include/bits/../foo.h' is
+simplified to `/usr/include/foo.h' before we enter it in the splay tree
+and try to `open ()' the file. CPP will then find subsequent uses of
+`foo.h', even as `/usr/include/foo.h', in the splay tree and save
+system calls.
+
+ Further, it is likely the file contents have also been cached,
+saving a `read ()' system call. We don't bother caching the contents of
+header files that are re-inclusion protected, and whose re-inclusion
+macro is defined when we leave the header file for the first time. If
+the host supports it, we try to map suitably large files into memory,
+rather than reading them in directly.
The include paths are internally stored on a null-terminated
-singly-linked list, starting with the '"header.h"' directory search
-chain, which then links into the '<header.h>' directory chain.
+singly-linked list, starting with the `"header.h"' directory search
+chain, which then links into the `<header.h>' directory chain.
- Files included with the '<foo.h>' syntax start the lookup directly in
-the second half of this chain. However, files included with the
-'"foo.h"' syntax start at the beginning of the chain, but with one extra
-directory prepended. This is the directory of the current file; the one
-containing the '#include' directive. Prepending this directory on a
-per-file basis is handled by the function 'search_from'.
+ Files included with the `<foo.h>' syntax start the lookup directly
+in the second half of this chain. However, files included with the
+`"foo.h"' syntax start at the beginning of the chain, but with one
+extra directory prepended. This is the directory of the current file;
+the one containing the `#include' directive. Prepending this directory
+on a per-file basis is handled by the function `search_from'.
Note that a header included with a directory component, such as
-'#include "mydir/foo.h"' and opened as '/usr/local/include/mydir/foo.h',
-will have the complete path minus the basename 'foo.h' as the current
-directory.
+`#include "mydir/foo.h"' and opened as
+`/usr/local/include/mydir/foo.h', will have the complete path minus the
+basename `foo.h' as the current directory.
Enough information is stored in the splay tree that CPP can
immediately tell whether it can skip the header file because of the
-multiple include optimization, whether the file didn't exist or couldn't
-be opened for some reason, or whether the header was flagged not to be
-re-used, as it is with the obsolete '#import' directive.
+multiple include optimization, whether the file didn't exist or
+couldn't be opened for some reason, or whether the header was flagged
+not to be re-used, as it is with the obsolete `#import' directive.
For the benefit of MS-DOS filesystems with an 8.3 filename
limitation, CPP offers the ability to treat various include file names
as aliases for the real header files with shorter names. The map from
-one to the other is found in a special file called 'header.gcc', stored
+one to the other is found in a special file called `header.gcc', stored
in the command line (or system) include directories to which the mapping
applies. This may be higher up the directory tree than the full path to
the file minus the base name.
@@ -990,7 +996,7 @@ Concept Index
* assertions: Hash Nodes. (line 6)
* controlling macros: Guard Macros. (line 6)
-* escaped newlines: Lexer. (line 5)
+* escaped newlines: Lexer. (line 6)
* files: Files. (line 6)
* guard macros: Guard Macros. (line 6)
* hash table: Hash Nodes. (line 6)
@@ -998,7 +1004,7 @@ Concept Index
* identifiers: Hash Nodes. (line 6)
* interface: Conventions. (line 6)
* lexer: Lexer. (line 6)
-* line numbers: Line Numbering. (line 5)
+* line numbers: Line Numbering. (line 6)
* macro expansion: Macro Expansion. (line 6)
* macro representation (internal): Macro Expansion. (line 19)
* macros: Hash Nodes. (line 6)
@@ -1007,23 +1013,23 @@ Concept Index
* newlines: Lexer. (line 6)
* paste avoidance: Token Spacing. (line 6)
* spacing: Token Spacing. (line 6)
-* token run: Lexer. (line 191)
+* token run: Lexer. (line 192)
* token spacing: Token Spacing. (line 6)

Tag Table:
-Node: Top905
-Node: Conventions2590
-Node: Lexer3532
-Ref: Invalid identifiers11447
-Ref: Lexing a line13397
-Node: Hash Nodes18170
-Node: Macro Expansion21049
-Node: Token Spacing29997
-Node: Line Numbering35854
-Node: Guard Macros39939
-Node: Files44730
-Node: Concept Index48196
+Node: Top958
+Node: Conventions2643
+Node: Lexer3585
+Ref: Invalid identifiers11498
+Ref: Lexing a line13447
+Node: Hash Nodes18220
+Node: Macro Expansion21099
+Node: Token Spacing30046
+Node: Line Numbering35906
+Node: Guard Macros39991
+Node: Files44782
+Node: Concept Index48248

End Tag Table
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index d4c41c6123..79559c82d7 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -15118,10 +15118,15 @@ The following low level built-in functions are available with
@option{-mhtm} or @option{-mcpu=CPU} where CPU is `power8' or later.
They all generate the machine instruction that is part of the name.
-The HTM built-ins return true or false depending on their success and
-their arguments match exactly the type and order of the associated
-hardware instruction's operands. Refer to the ISA manual for a
-description of each instruction's operands.
+The HTM builtins (with the exception of @code{__builtin_tbegin}) return
+the full 4-bit condition register value set by their associated hardware
+instruction. The header file @code{htmintrin.h} defines some macros that can
+be used to decipher the return value. The @code{__builtin_tbegin} builtin
+returns a simple true or false value depending on whether a transaction was
+successfully started or not. The arguments of the builtins match exactly the
+type and order of the associated hardware instruction's operands, except for
+the @code{__builtin_tcheck} builtin, which does not take any input arguments.
+Refer to the ISA manual for a description of each instruction's operands.
@smallexample
unsigned int __builtin_tbegin (unsigned int)
@@ -15133,7 +15138,7 @@ unsigned int __builtin_tabortdci (unsigned int, unsigned int, int)
unsigned int __builtin_tabortwc (unsigned int, unsigned int, unsigned int)
unsigned int __builtin_tabortwci (unsigned int, unsigned int, int)
-unsigned int __builtin_tcheck (unsigned int)
+unsigned int __builtin_tcheck (void)
unsigned int __builtin_treclaim (unsigned int)
unsigned int __builtin_trechkpt (void)
unsigned int __builtin_tsr (unsigned int)
@@ -15268,7 +15273,7 @@ TM_buff_type TM_buff;
while (1)
@{
- if (__TM_begin (TM_buff))
+ if (__TM_begin (TM_buff) == _HTM_TBEGIN_STARTED)
@{
/* Transaction State Initiated. */
if (is_locked (lock))
@@ -17282,6 +17287,13 @@ void __builtin_ia32_xabort (status)
int __builtin_ia32_xtest ()
@end smallexample
+The following built-in functions are available when @option{-mmwaitx} is used.
+All of them generate the machine instruction that is part of the name.
+@smallexample
+void __builtin_ia32_monitorx (void *, unsigned int, unsigned int)
+void __builtin_ia32_mwaitx (unsigned int, unsigned int, unsigned int)
+@end smallexample
+
@node x86 transactional memory intrinsics
@subsection x86 Transactional Memory Intrinsics
diff --git a/gcc/doc/fsf-funding.7 b/gcc/doc/fsf-funding.7
index 815373f9ed..e78296056f 100644
--- a/gcc/doc/fsf-funding.7
+++ b/gcc/doc/fsf-funding.7
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "FSF-FUNDING 7"
-.TH FSF-FUNDING 7 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH FSF-FUNDING 7 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -142,7 +141,7 @@
fsf\-funding \- Funding Free Software
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-.SS "Funding Free Software"
+.Sh "Funding Free Software"
.IX Subsection "Funding Free Software"
If you want to have more free software a few years from now, it makes
sense for you to help encourage people to contribute funds for its
diff --git a/gcc/doc/g++.1 b/gcc/doc/g++.1
index dcd7f1481d..c56451f7a4 100644
--- a/gcc/doc/g++.1
+++ b/gcc/doc/g++.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCC 1"
-.TH GCC 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCC 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -154,7 +153,7 @@ Only the most useful options are listed here; see below for the
remainder. \fBg++\fR accepts mostly the same options as \fBgcc\fR.
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-When you invoke \s-1GCC,\s0 it normally does preprocessing, compilation,
+When you invoke \s-1GCC\s0, it normally does preprocessing, compilation,
assembly and linking. The \*(L"overall options\*(R" allow you to stop this
process at an intermediate stage. For example, the \fB\-c\fR option
says not to run the linker. Then the output consists of object files
@@ -189,7 +188,7 @@ these have both positive and negative forms; the negative form of
only one of these two forms, whichever one is not the default.
.SH "OPTIONS"
.IX Header "OPTIONS"
-.SS "Option Summary"
+.Sh "Option Summary"
.IX Subsection "Option Summary"
Here is a summary of all the options, grouped by type. Explanations are
in the following sections.
@@ -532,6 +531,7 @@ in the following sections.
\&\-momit\-leaf\-frame\-pointer \-mno\-omit\-leaf\-frame\-pointer
\&\-mtls\-dialect=desc \-mtls\-dialect=traditional
\&\-mfix\-cortex\-a53\-835769 \-mno\-fix\-cortex\-a53\-835769
+\&\-mfix\-cortex\-a53\-843419 \-mno\-fix\-cortex\-a53\-843419
\&\-march=\fR\fIname\fR \fB\-mcpu=\fR\fIname\fR \fB\-mtune=\fR\fIname\fR
.Sp
\&\fIAdapteva Epiphany Options\fR
@@ -1096,7 +1096,7 @@ See \s-1RS/6000\s0 and PowerPC Options.
\&\-maes \-mpclmul \-mfsgsbase \-mrdrnd \-mf16c \-mfma \-mprefetchwt1
\&\-mclflushopt \-mxsavec \-mxsaves
\&\-msse4a \-m3dnow \-mpopcnt \-mabm \-mbmi \-mtbm \-mfma4 \-mxop \-mlzcnt
-\&\-mbmi2 \-mfxsr \-mxsave \-mxsaveopt \-mrtm \-mlwp \-mmpx \-mthreads
+\&\-mbmi2 \-mfxsr \-mxsave \-mxsaveopt \-mrtm \-mlwp \-mmpx \-mmwaitx \-mthreads
\&\-mno\-align\-stringops \-minline\-all\-stringops
\&\-minline\-stringops\-dynamically \-mstringop\-strategy=\fR\fIalg\fR
\&\fB\-mmemcpy\-strategy=\fR\fIstrategy\fR \fB\-mmemset\-strategy=\fR\fIstrategy\fR
@@ -1155,7 +1155,7 @@ See S/390 and zSeries Options.
\&\fB\-ftrapv \-fwrapv \-fbounds\-check
\&\-fvisibility=\fR[\fBdefault\fR|\fBinternal\fR|\fBhidden\fR|\fBprotected\fR]
\&\fB\-fstrict\-volatile\-bitfields \-fsync\-libcalls\fR
-.SS "Options Controlling the Kind of Output"
+.Sh "Options Controlling the Kind of Output"
.IX Subsection "Options Controlling the Kind of Output"
Compilation can involve up to four stages: preprocessing, compilation
proper, assembly and linking, always in that order. \s-1GCC\s0 is capable of
@@ -1459,7 +1459,7 @@ option.
.IX Item "language"
Display the options supported for \fIlanguage\fR, where
\&\fIlanguage\fR is the name of one of the languages supported in this
-version of \s-1GCC.\s0
+version of \s-1GCC\s0.
.IP "\fBcommon\fR" 4
.IX Item "common"
Display the options that are common to all languages.
@@ -1556,7 +1556,7 @@ or \fB/./\fR, or make the path absolute when generating a relative
prefix.
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
-Display the version number and copyrights of the invoked \s-1GCC.\s0
+Display the version number and copyrights of the invoked \s-1GCC\s0.
.IP "\fB\-wrapper\fR" 4
.IX Item "-wrapper"
Invoke all subcommands under a wrapper program. The name of the
@@ -1578,7 +1578,7 @@ the shared object file is used to identify the plugin for the
purposes of argument parsing (See
\&\fB\-fplugin\-arg\-\fR\fIname\fR\fB\-\fR\fIkey\fR\fB=\fR\fIvalue\fR below).
Each plugin should define the callback functions specified in the
-Plugins \s-1API.\s0
+Plugins \s-1API\s0.
.IP "\fB\-fplugin\-arg\-\fR\fIname\fR\fB\-\fR\fIkey\fR\fB=\fR\fIvalue\fR" 4
.IX Item "-fplugin-arg-name-key=value"
Define an argument called \fIkey\fR with a value of \fIvalue\fR
@@ -1610,8 +1610,8 @@ option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
with a backslash. The \fIfile\fR may itself contain additional
@\fIfile\fR options; any such options will be processed recursively.
-.SS "Compiling \*(C+ Programs"
-.IX Subsection "Compiling Programs"
+.Sh "Compiling \*(C+ Programs"
+.IX Subsection "Compiling Programs"
\&\*(C+ source files conventionally use one of the suffixes \fB.C\fR,
\&\fB.cc\fR, \fB.cpp\fR, \fB.CPP\fR, \fB.c++\fR, \fB.cp\fR, or
\&\fB.cxx\fR; \*(C+ header files often use \fB.hh\fR, \fB.hpp\fR,
@@ -1634,7 +1634,7 @@ When you compile \*(C+ programs, you may specify many of the same
command-line options that you use for compiling programs in any
language; or command-line options meaningful for C and related
languages; or options that are meaningful only for \*(C+ programs.
-.SS "Options Controlling C Dialect"
+.Sh "Options Controlling C Dialect"
.IX Subsection "Options Controlling C Dialect"
The following options control the dialect of C (or languages derived
from C, such as \*(C+, Objective-C and Objective\-\*(C+) that the compiler
@@ -1644,8 +1644,8 @@ accepts:
In C mode, this is equivalent to \fB\-std=c90\fR. In \*(C+ mode, it is
equivalent to \fB\-std=c++98\fR.
.Sp
-This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO
-C90 \s0(when compiling C code), or of standard \*(C+ (when compiling \*(C+ code),
+This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO\s0
+C90 (when compiling C code), or of standard \*(C+ (when compiling \*(C+ code),
such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and
predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the
type of system you are using. It also enables the undesirable and
@@ -1655,7 +1655,7 @@ the \f(CW\*(C`inline\*(C'\fR keyword.
.Sp
The alternate keywords \f(CW\*(C`_\|_asm_\|_\*(C'\fR, \f(CW\*(C`_\|_extension_\|_\*(C'\fR,
\&\f(CW\*(C`_\|_inline_\|_\*(C'\fR and \f(CW\*(C`_\|_typeof_\|_\*(C'\fR continue to work despite
-\&\fB\-ansi\fR. You would not want to use them in an \s-1ISO C\s0 program, of
+\&\fB\-ansi\fR. You would not want to use them in an \s-1ISO\s0 C program, of
course, but it is useful to put them in header files that might be included
in compilations done with \fB\-ansi\fR. Alternate predefined macros
such as \f(CW\*(C`_\|_unix_\|_\*(C'\fR and \f(CW\*(C`_\|_vax_\|_\*(C'\fR are also available, with or
@@ -1672,7 +1672,7 @@ from declaring certain functions or defining certain macros that the
programs that might use these names for other things.
.Sp
Functions that are normally built in but do not have semantics
-defined by \s-1ISO C \s0(such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in
+defined by \s-1ISO\s0 C (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in
functions when \fB\-ansi\fR is used.
.IP "\fB\-std=\fR" 4
.IX Item "-std="
@@ -1685,9 +1685,9 @@ The compiler can accept several base standards, such as \fBc90\fR or
compiler accepts all programs following that standard plus those
using \s-1GNU\s0 extensions that do not contradict it. For example,
\&\fB\-std=c90\fR turns off certain features of \s-1GCC\s0 that are
-incompatible with \s-1ISO C90,\s0 such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR
+incompatible with \s-1ISO\s0 C90, such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR
keywords, but not other \s-1GNU\s0 extensions that do not have a meaning in
-\&\s-1ISO C90,\s0 such as omitting the middle term of a \f(CW\*(C`?:\*(C'\fR
+\&\s-1ISO\s0 C90, such as omitting the middle term of a \f(CW\*(C`?:\*(C'\fR
expression. On the other hand, when a \s-1GNU\s0 dialect of a standard is
specified, all features supported by the compiler are enabled, even when
those features change the meaning of the base standard. As a result, some
@@ -1707,11 +1707,11 @@ A value for this option must be provided; possible values are
.IP "\fBiso9899:1990\fR" 4
.IX Item "iso9899:1990"
.PD
-Support all \s-1ISO C90\s0 programs (certain \s-1GNU\s0 extensions that conflict
-with \s-1ISO C90\s0 are disabled). Same as \fB\-ansi\fR for C code.
+Support all \s-1ISO\s0 C90 programs (certain \s-1GNU\s0 extensions that conflict
+with \s-1ISO\s0 C90 are disabled). Same as \fB\-ansi\fR for C code.
.IP "\fBiso9899:199409\fR" 4
.IX Item "iso9899:199409"
-\&\s-1ISO C90\s0 as modified in amendment 1.
+\&\s-1ISO\s0 C90 as modified in amendment 1.
.IP "\fBc99\fR" 4
.IX Item "c99"
.PD 0
@@ -1722,7 +1722,7 @@ with \s-1ISO C90\s0 are disabled). Same as \fB\-ansi\fR for C code.
.IP "\fBiso9899:199x\fR" 4
.IX Item "iso9899:199x"
.PD
-\&\s-1ISO C99. \s0 This standard is substantially completely supported, modulo
+\&\s-1ISO\s0 C99. This standard is substantially completely supported, modulo
bugs and floating-point issues
(mainly but not entirely relating to optional C99 features from
Annexes F and G). See
@@ -1736,7 +1736,7 @@ names \fBc9x\fR and \fBiso9899:199x\fR are deprecated.
.IP "\fBiso9899:2011\fR" 4
.IX Item "iso9899:2011"
.PD
-\&\s-1ISO C11,\s0 the 2011 revision of the \s-1ISO C\s0 standard. This standard is
+\&\s-1ISO\s0 C11, the 2011 revision of the \s-1ISO\s0 C standard. This standard is
substantially completely supported, modulo bugs, floating-point issues
(mainly but not entirely relating to optional C11 features from
Annexes F and G) and the optional Annexes K (Bounds-checking
@@ -1747,21 +1747,21 @@ interfaces) and L (Analyzability). The name \fBc1x\fR is deprecated.
.IP "\fBgnu89\fR" 4
.IX Item "gnu89"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C90 \s0(including some C99 features).
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C90 (including some C99 features).
.IP "\fBgnu99\fR" 4
.IX Item "gnu99"
.PD 0
.IP "\fBgnu9x\fR" 4
.IX Item "gnu9x"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C99. \s0 The name \fBgnu9x\fR is deprecated.
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C99. The name \fBgnu9x\fR is deprecated.
.IP "\fBgnu11\fR" 4
.IX Item "gnu11"
.PD 0
.IP "\fBgnu1x\fR" 4
.IX Item "gnu1x"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C11. \s0 This is the default for C code.
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C11. This is the default for C code.
The name \fBgnu1x\fR is deprecated.
.IP "\fBc++98\fR" 4
.IX Item "c++98"
@@ -1769,7 +1769,7 @@ The name \fBgnu1x\fR is deprecated.
.IP "\fBc++03\fR" 4
.IX Item "c++03"
.PD
-The 1998 \s-1ISO \*(C+\s0 standard plus the 2003 technical corrigendum and some
+The 1998 \s-1ISO\s0 \*(C+ standard plus the 2003 technical corrigendum and some
additional defect reports. Same as \fB\-ansi\fR for \*(C+ code.
.IP "\fBgnu++98\fR" 4
.IX Item "gnu++98"
@@ -1785,7 +1785,7 @@ additional defect reports. Same as \fB\-ansi\fR for \*(C+ code.
.IP "\fBc++0x\fR" 4
.IX Item "c++0x"
.PD
-The 2011 \s-1ISO \*(C+\s0 standard plus amendments.
+The 2011 \s-1ISO\s0 \*(C+ standard plus amendments.
The name \fBc++0x\fR is deprecated.
.IP "\fBgnu++11\fR" 4
.IX Item "gnu++11"
@@ -1801,7 +1801,7 @@ The name \fBgnu++0x\fR is deprecated.
.IP "\fBc++1y\fR" 4
.IX Item "c++1y"
.PD
-The 2014 \s-1ISO \*(C+\s0 standard plus amendments.
+The 2014 \s-1ISO\s0 \*(C+ standard plus amendments.
The name \fBc++1y\fR is deprecated.
.IP "\fBgnu++14\fR" 4
.IX Item "gnu++14"
@@ -1813,7 +1813,7 @@ The name \fBc++1y\fR is deprecated.
The name \fBgnu++1y\fR is deprecated.
.IP "\fBc++1z\fR" 4
.IX Item "c++1z"
-The next revision of the \s-1ISO \*(C+\s0 standard, tentatively planned for
+The next revision of the \s-1ISO\s0 \*(C+ standard, tentatively planned for
2017. Support is highly experimental, and will almost certainly
change in incompatible ways in future releases.
.IP "\fBgnu++1z\fR" 4
@@ -1875,7 +1875,7 @@ In \*(C+, this switch only affects the \f(CW\*(C`typeof\*(C'\fR keyword, since
use the \fB\-fno\-gnu\-keywords\fR flag instead, which has the same
effect. In C99 mode (\fB\-std=c99\fR or \fB\-std=gnu99\fR), this
switch only affects the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, since
-\&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO C99.\s0
+\&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO\s0 C99.
.IP "\fB\-fno\-builtin\fR" 4
.IX Item "-fno-builtin"
.PD 0
@@ -1903,7 +1903,7 @@ known not to modify global memory.
With the \fB\-fno\-builtin\-\fR\fIfunction\fR option
only the built-in function \fIfunction\fR is
disabled. \fIfunction\fR must not begin with \fB_\|_builtin_\fR. If a
-function is named that is not built-in in this version of \s-1GCC,\s0 this
+function is named that is not built-in in this version of \s-1GCC\s0, this
option is ignored. There is no corresponding
\&\fB\-fbuiltin\-\fR\fIfunction\fR option; if you wish to enable
built-in functions selectively when using \fB\-fno\-builtin\fR or
@@ -1937,7 +1937,7 @@ implies \fB\-pthread\fR, and thus is only supported on targets that
have support for \fB\-pthread\fR.
.Sp
Note that this is an experimental feature, incomplete, and subject to
-change in future versions of \s-1GCC. \s0 See
+change in future versions of \s-1GCC\s0. See
<\fBhttps://gcc.gnu.org/wiki/OpenACC\fR> for more information.
.IP "\fB\-fopenmp\fR" 4
.IX Item "-fopenmp"
@@ -1969,7 +1969,7 @@ When the option \fB\-fgnu\-tm\fR is specified, the compiler
generates code for the Linux variant of Intel's current Transactional
Memory \s-1ABI\s0 specification document (Revision 1.1, May 6 2009). This is
an experimental feature whose interface may change in future versions
-of \s-1GCC,\s0 as the official specification changes. Please note that not
+of \s-1GCC\s0, as the official specification changes. Please note that not
all architectures are supported for this feature.
.Sp
For more information on \s-1GCC\s0's support for transactional memory,
@@ -2006,8 +2006,8 @@ fields declared using a typedef. This is only
supported for C, not \*(C+.
.IP "\fB\-trigraphs\fR" 4
.IX Item "-trigraphs"
-Support \s-1ISO C\s0 trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
-options for strict \s-1ISO C\s0 conformance) implies \fB\-trigraphs\fR.
+Support \s-1ISO\s0 C trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
+options for strict \s-1ISO\s0 C conformance) implies \fB\-trigraphs\fR.
.IP "\fB\-traditional\fR" 4
.IX Item "-traditional"
.PD 0
@@ -2016,8 +2016,8 @@ options for strict \s-1ISO C\s0 conformance) implies \fB\-trigraphs\fR.
.PD
Formerly, these options caused \s-1GCC\s0 to attempt to emulate a pre-standard
C compiler. They are now only supported with the \fB\-E\fR switch.
-The preprocessor continues to support a pre-standard mode. See the \s-1GNU
-CPP\s0 manual for details.
+The preprocessor continues to support a pre-standard mode. See the \s-1GNU\s0
+\&\s-1CPP\s0 manual for details.
.IP "\fB\-fcond\-mismatch\fR" 4
.IX Item "-fcond-mismatch"
Allow conditional expressions with mismatched types in the second and
@@ -2067,8 +2067,8 @@ These options control whether a bit-field is signed or unsigned, when the
declaration does not use either \f(CW\*(C`signed\*(C'\fR or \f(CW\*(C`unsigned\*(C'\fR. By
default, such a bit-field is signed, because this is consistent: the
basic integer types such as \f(CW\*(C`int\*(C'\fR are signed types.
-.SS "Options Controlling \*(C+ Dialect"
-.IX Subsection "Options Controlling Dialect"
+.Sh "Options Controlling \*(C+ Dialect"
+.IX Subsection "Options Controlling Dialect"
This section describes the command-line options that are only meaningful
for \*(C+ programs. You can also use most of the \s-1GNU\s0 compiler options
regardless of what language your program is in. For example, you
@@ -2080,12 +2080,12 @@ might compile a file \fIfirstClass.C\fR like this:
.PP
In this example, only \fB\-frepo\fR is an option meant
only for \*(C+ programs; you can use the other options with any
-language supported by \s-1GCC.\s0
+language supported by \s-1GCC\s0.
.PP
Here is a list of options that are \fIonly\fR for compiling \*(C+ programs:
.IP "\fB\-fabi\-version=\fR\fIn\fR" 4
.IX Item "-fabi-version=n"
-Use version \fIn\fR of the \*(C+ \s-1ABI. \s0 The default is version 0.
+Use version \fIn\fR of the \*(C+ \s-1ABI\s0. The default is version 0.
.Sp
Version 0 refers to the version conforming most closely to
the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0
@@ -2179,7 +2179,7 @@ Inject friend functions into the enclosing namespace, so that they are
visible outside the scope of the class in which they are declared.
Friend functions were documented to work this way in the old Annotated
\&\*(C+ Reference Manual.
-However, in \s-1ISO \*(C+\s0 a friend function that is not declared
+However, in \s-1ISO\s0 \*(C+ a friend function that is not declared
in an enclosing scope can only be found using argument dependent
lookup. \s-1GCC\s0 defaults to the standard behavior.
.Sp
@@ -2262,12 +2262,12 @@ controlled by \f(CW\*(C`#pragma implementation\*(C'\fR. This causes linker
errors if these functions are not inlined everywhere they are called.
.IP "\fB\-fms\-extensions\fR" 4
.IX Item "-fms-extensions"
-Disable Wpedantic warnings about constructs used in \s-1MFC,\s0 such as implicit
+Disable Wpedantic warnings about constructs used in \s-1MFC\s0, such as implicit
int and getting a pointer to member function via non-standard syntax.
.IP "\fB\-fno\-nonansi\-builtins\fR" 4
.IX Item "-fno-nonansi-builtins"
Disable built-in declarations of functions that are not mandated by
-\&\s-1ANSI/ISO C. \s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR,
+\&\s-1ANSI/ISO\s0 C. These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR,
\&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions.
.IP "\fB\-fnothrow\-opt\fR" 4
.IX Item "-fnothrow-opt"
@@ -2355,7 +2355,7 @@ warning or error to \fIn\fR. The default value is 10.
.IX Item "-ftemplate-depth=n"
Set the maximum instantiation depth for template classes to \fIn\fR.
A limit on the template instantiation depth is needed to detect
-endless recursions during template class instantiation. \s-1ANSI/ISO \*(C+\s0
+endless recursions during template class instantiation. \s-1ANSI/ISO\s0 \*(C+
conforming programs must not rely on a maximum depth greater than 17
(changed to 1024 in \*(C+11). The default value is 900, as the compiler
can run out of stack space before hitting 1024 in some situations.
@@ -2386,7 +2386,7 @@ are taken in different shared objects.
The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with
\&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not
appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection
-when used within the \s-1DSO. \s0 Enabling this option can have a dramatic effect
+when used within the \s-1DSO\s0. Enabling this option can have a dramatic effect
on load and link times of a \s-1DSO\s0 as it massively reduces the size of the
dynamic export table when the library makes heavy use of templates.
.Sp
@@ -2506,10 +2506,10 @@ is used when building the \*(C+ library.)
In addition, these optimization, warning, and code generation options
have meanings only for \*(C+ programs:
.IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4
-.IX Item "-Wabi (C, Objective-C, and Objective- only)"
+.IX Item "-Wabi (C, Objective-C, and Objective- only)"
When an explicit \fB\-fabi\-version=\fR\fIn\fR option is used, causes
G++ to warn when it generates code that is probably not compatible with the
-vendor-neutral \*(C+ \s-1ABI. \s0 Since G++ now defaults to
+vendor-neutral \*(C+ \s-1ABI\s0. Since G++ now defaults to
\&\fB\-fabi\-version=0\fR, \fB\-Wabi\fR has no effect unless either
an older \s-1ABI\s0 version is selected (with \fB\-fabi\-version=\fR\fIn\fR)
or an older compatibility version is selected (with
@@ -2532,7 +2532,7 @@ level, e.g. \fB\-Wabi=2\fR to warn about changes relative to
\&\fB\-fabi\-compat\-version=\fR\fIn\fR.
.Sp
The known incompatibilities in \fB\-fabi\-version=2\fR (which was the
-default from \s-1GCC 3.4\s0 to 4.9) include:
+default from \s-1GCC\s0 3.4 to 4.9) include:
.RS 4
.IP "*" 4
A template with a non-type template parameter of reference type was
@@ -2560,7 +2560,7 @@ These mangling issues were fixed in \fB\-fabi\-version=5\fR.
Scoped enumerators passed as arguments to a variadic function are
promoted like unscoped enumerators, causing \f(CW\*(C`va_arg\*(C'\fR to complain.
On most targets this does not actually affect the parameter passing
-\&\s-1ABI,\s0 as there is no way to pass an argument smaller than \f(CW\*(C`int\*(C'\fR.
+\&\s-1ABI\s0, as there is no way to pass an argument smaller than \f(CW\*(C`int\*(C'\fR.
.Sp
Also, the \s-1ABI\s0 changed the mangling of template argument packs,
\&\f(CW\*(C`const_cast\*(C'\fR, \f(CW\*(C`static_cast\*(C'\fR, prefix increment/decrement, and
@@ -2650,10 +2650,10 @@ Warn when a narrowing conversion prohibited by \*(C+11 occurs within
.Sp
This flag is included in \fB\-Wall\fR and \fB\-Wc++11\-compat\fR.
.Sp
-With \fB\-std=c++11\fR, \fB\-Wno\-narrowing\fR suppresses for
-non-constants the diagnostic required by the standard. Note that this
-does not affect the meaning of well-formed code; narrowing conversions
-are still considered ill-formed in \s-1SFINAE\s0 context.
+With \fB\-std=c++11\fR, \fB\-Wno\-narrowing\fR suppresses the diagnostic
+required by the standard. Note that this does not affect the meaning
+of well-formed code; narrowing conversions are still considered
+ill-formed in \s-1SFINAE\s0 context.
.IP "\fB\-Wnoexcept\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wnoexcept ( and Objective- only)"
Warn when a noexcept-expression evaluates to false because of a call
@@ -2693,7 +2693,7 @@ This is on by default for all pre\-\*(C+11 dialects and all \s-1GNU\s0 dialects:
\&\fB\-std=c++98\fR, \fB\-std=gnu++98\fR, \fB\-std=gnu++11\fR,
\&\fB\-std=gnu++14\fR.
This option is off by default
-for \s-1ISO \*(C+11\s0 onwards (\fB\-std=c++11\fR, ...).
+for \s-1ISO\s0 \*(C+11 onwards (\fB\-std=c++11\fR, ...).
.PP
The following \fB\-W...\fR options are not affected by \fB\-Wall\fR.
.IP "\fB\-Weffc++\fR (\*(C+ and Objective\-\*(C+ only)" 4
@@ -2789,7 +2789,7 @@ Warn when overload resolution chooses a promotion from unsigned or
enumerated type to a signed type, over a conversion to an unsigned type of
the same size. Previous versions of G++ tried to preserve
unsignedness, but the standard mandates the current behavior.
-.SS "Options Controlling Objective-C and Objective\-\*(C+ Dialects"
+.Sh "Options Controlling Objective-C and Objective\-\*(C+ Dialects"
.IX Subsection "Options Controlling Objective-C and Objective- Dialects"
(\s-1NOTE:\s0 This manual does not describe the Objective-C and Objective\-\*(C+
languages themselves.
@@ -2805,7 +2805,7 @@ For example, you might compile a file \fIsome_class.m\fR like this:
.PP
In this example, \fB\-fgnu\-runtime\fR is an option meant only for
Objective-C and Objective\-\*(C+ programs; you can use the other options with
-any language supported by \s-1GCC.\s0
+any language supported by \s-1GCC\s0.
.PP
Note that since Objective-C is an extension of the C language, Objective-C
compilations may also use options specific to the C front-end (e.g.,
@@ -2830,7 +2830,7 @@ runtime. This is the default for most types of systems.
.IP "\fB\-fnext\-runtime\fR" 4
.IX Item "-fnext-runtime"
Generate output compatible with the NeXT runtime. This is the default
-for NeXT-based systems, including Darwin and Mac \s-1OS X. \s0 The macro
+for NeXT-based systems, including Darwin and Mac \s-1OS\s0 X. The macro
\&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is
used.
.IP "\fB\-fno\-nil\-receivers\fR" 4
@@ -2847,7 +2847,7 @@ This option is currently supported only for the NeXT runtime. In that
case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for
properties and other Objective-C 2.0 additions. Version 1 is the
traditional (32\-bit) \s-1ABI\s0 with support for properties and other
-Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI. \s0 If
+Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI\s0. If
nothing is specified, the default is Version 0 on 32\-bit target
machines, and Version 2 on 64\-bit target machines.
.IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4
@@ -2871,7 +2871,7 @@ by the runtime immediately after a new object instance is allocated;
the \f(CW\*(C`\- (void) .cxx_destruct\*(C'\fR methods are invoked immediately
before the runtime deallocates an object instance.
.Sp
-As of this writing, only the NeXT runtime on Mac \s-1OS X 10.4\s0 and later has
+As of this writing, only the NeXT runtime on Mac \s-1OS\s0 X 10.4 and later has
support for invoking the \f(CW\*(C`\- (id) .cxx_construct\*(C'\fR and
\&\f(CW\*(C`\- (void) .cxx_destruct\*(C'\fR methods.
.IP "\fB\-fobjc\-direct\-dispatch\fR" 4
@@ -2886,7 +2886,7 @@ is required to use the Objective-C keywords \f(CW@try\fR,
\&\f(CW@throw\fR, \f(CW@catch\fR, \f(CW@finally\fR and
\&\f(CW@synchronized\fR. This option is available with both the \s-1GNU\s0
runtime and the NeXT runtime (but not available in conjunction with
-the NeXT runtime on Mac \s-1OS X 10.2\s0 and earlier).
+the NeXT runtime on Mac \s-1OS\s0 X 10.2 and earlier).
.IP "\fB\-fobjc\-gc\fR" 4
.IX Item "-fobjc-gc"
Enable garbage collection (\s-1GC\s0) in Objective-C and Objective\-\*(C+
@@ -2895,23 +2895,23 @@ programs. This option is only available with the NeXT runtime; the
does not require special compiler flags.
.IP "\fB\-fobjc\-nilcheck\fR" 4
.IX Item "-fobjc-nilcheck"
-For the NeXT runtime with version 2 of the \s-1ABI,\s0 check for a nil
+For the NeXT runtime with version 2 of the \s-1ABI\s0, check for a nil
receiver in method invocations before doing the actual method call.
This is the default and can be disabled using
\&\fB\-fno\-objc\-nilcheck\fR. Class methods and super calls are never
checked for nil in this way no matter what this flag is set to.
Currently this flag does nothing when the \s-1GNU\s0 runtime, or an older
-version of the NeXT runtime \s-1ABI,\s0 is used.
+version of the NeXT runtime \s-1ABI\s0, is used.
.IP "\fB\-fobjc\-std=objc1\fR" 4
.IX Item "-fobjc-std=objc1"
Conform to the language syntax of Objective-C 1.0, the language
-recognized by \s-1GCC 4.0. \s0 This only affects the Objective-C additions to
+recognized by \s-1GCC\s0 4.0. This only affects the Objective-C additions to
the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards,
which is controlled by the separate C/\*(C+ dialect option flags. When
this option is used with the Objective-C or Objective\-\*(C+ compiler,
-any Objective-C syntax that is not recognized by \s-1GCC 4.0\s0 is rejected.
+any Objective-C syntax that is not recognized by \s-1GCC\s0 4.0 is rejected.
This is useful if you need to make sure that your Objective-C code can
-be compiled with older versions of \s-1GCC.\s0
+be compiled with older versions of \s-1GCC\s0.
.IP "\fB\-freplace\-objc\-classes\fR" 4
.IX Item "-freplace-objc-classes"
Emit a special marker instructing \fB\f(BIld\fB\|(1)\fR not to statically link in
@@ -2920,7 +2920,7 @@ run time instead. This is used in conjunction with the Fix-and-Continue
debugging mode, where the object file in question may be recompiled and
dynamically reloaded in the course of program execution, without the need
to restart the program itself. Currently, Fix-and-Continue functionality
-is only available in conjunction with the NeXT runtime on Mac \s-1OS X 10.3\s0
+is only available in conjunction with the NeXT runtime on Mac \s-1OS\s0 X 10.3
and later.
.IP "\fB\-fzero\-link\fR" 4
.IX Item "-fzero-link"
@@ -2999,7 +2999,7 @@ that methods and selectors must be declared before being used.
.IX Item "-print-objc-runtime-info"
Generate C header describing the largest structure that is passed by
value, if any.
-.SS "Options to Control Diagnostic Messages Formatting"
+.Sh "Options to Control Diagnostic Messages Formatting"
.IX Subsection "Options to Control Diagnostic Messages Formatting"
Traditionally, diagnostic messages have been formatted irrespective of
the output device's aspect (e.g. its width, ...). You can use the
@@ -3121,14 +3121,14 @@ information. The source line is truncated to \fIn\fR characters, if
the \fB\-fmessage\-length=n\fR option is given. When the output is done
to the terminal, the width is limited to the width given by the
\&\fB\s-1COLUMNS\s0\fR environment variable or, if not set, to the terminal width.
-.SS "Options to Request or Suppress Warnings"
+.Sh "Options to Request or Suppress Warnings"
.IX Subsection "Options to Request or Suppress Warnings"
Warnings are diagnostic messages that report constructions that
are not inherently erroneous but that are risky or suggest there
may have been an error.
.PP
The following language-independent options do not enable specific
-warnings but control the kinds of diagnostics produced by \s-1GCC.\s0
+warnings but control the kinds of diagnostics produced by \s-1GCC\s0.
.IP "\fB\-fsyntax\-only\fR" 4
.IX Item "-fsyntax-only"
Check the code for syntax errors, but don't do anything beyond that.
@@ -3203,14 +3203,14 @@ warns that an unrecognized option is present.
.IP "\fB\-pedantic\fR" 4
.IX Item "-pedantic"
.PD
-Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0;
+Issue all the warnings demanded by strict \s-1ISO\s0 C and \s-1ISO\s0 \*(C+;
reject all programs that use forbidden extensions, and some other
-programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+. \s0 For \s-1ISO C,\s0 follows the
-version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used.
+programs that do not follow \s-1ISO\s0 C and \s-1ISO\s0 \*(C+. For \s-1ISO\s0 C, follows the
+version of the \s-1ISO\s0 C standard specified by any \fB\-std\fR option used.
.Sp
-Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without
+Valid \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ programs should compile properly with or without
this option (though a rare few require \fB\-ansi\fR or a
-\&\fB\-std\fR option specifying the required version of \s-1ISO C\s0). However,
+\&\fB\-std\fR option specifying the required version of \s-1ISO\s0 C). However,
without this option, certain \s-1GNU\s0 extensions and traditional C and \*(C+
features are supported as well. With this option, they are rejected.
.Sp
@@ -3220,24 +3220,24 @@ warnings are also disabled in the expression that follows
\&\f(CW\*(C`_\|_extension_\|_\*(C'\fR. However, only system header files should use
these escape routes; application programs should avoid them.
.Sp
-Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO
-C\s0 conformance. They soon find that it does not do quite what they want:
+Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO\s0
+C conformance. They soon find that it does not do quite what they want:
it finds some non-ISO practices, but not all\-\-\-only those for which
-\&\s-1ISO C \s0\fIrequires\fR a diagnostic, and some others for which
+\&\s-1ISO\s0 C \fIrequires\fR a diagnostic, and some others for which
diagnostics have been added.
.Sp
-A feature to report any failure to conform to \s-1ISO C\s0 might be useful in
+A feature to report any failure to conform to \s-1ISO\s0 C might be useful in
some instances, but would require considerable additional work and would
be quite different from \fB\-Wpedantic\fR. We don't have plans to
support such a feature in the near future.
.Sp
Where the standard specified with \fB\-std\fR represents a \s-1GNU\s0
extended dialect of C, such as \fBgnu90\fR or \fBgnu99\fR, there is a
-corresponding \fIbase standard\fR, the version of \s-1ISO C\s0 on which the \s-1GNU\s0
+corresponding \fIbase standard\fR, the version of \s-1ISO\s0 C on which the \s-1GNU\s0
extended dialect is based. Warnings from \fB\-Wpedantic\fR are given
where they are required by the base standard. (It does not make sense
-for such warnings to be given only for features not in the specified \s-1GNU
-C\s0 dialect, since by definition the \s-1GNU\s0 dialects of C include all
+for such warnings to be given only for features not in the specified \s-1GNU\s0
+C dialect, since by definition the \s-1GNU\s0 dialects of C include all
features the compiler supports with the given option, and there would be
nothing to warn about.)
.IP "\fB\-pedantic\-errors\fR" 4
@@ -3409,7 +3409,7 @@ functions without the attribute specified are disabled by
\&\fB\-ffreestanding\fR or \fB\-fno\-builtin\fR.
.Sp
The formats are checked against the format features supported by \s-1GNU\s0
-libc version 2.2. These include all \s-1ISO C90\s0 and C99 features, as well
+libc version 2.2. These include all \s-1ISO\s0 C90 and C99 features, as well
as features from the Single Unix Specification and some \s-1BSD\s0 and \s-1GNU\s0
extensions. Other library implementations may not support all these
features; \s-1GCC\s0 does not support warning about features that go beyond a
@@ -3525,12 +3525,12 @@ enabled by default and it is made into an error by
Same as \fB\-Wimplicit\-int\fR and \fB\-Wimplicit\-function\-declaration\fR.
This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wignored\-qualifiers\fR (C and \*(C+ only)" 4
-.IX Item "-Wignored-qualifiers (C and only)"
+.IX Item "-Wignored-qualifiers (C and only)"
Warn if the return type of a function has a type qualifier
-such as \f(CW\*(C`const\*(C'\fR. For \s-1ISO C\s0 such a type qualifier has no effect,
+such as \f(CW\*(C`const\*(C'\fR. For \s-1ISO\s0 C such a type qualifier has no effect,
since the value returned by a function is not an lvalue.
For \*(C+, the warning is only emitted for scalar types or \f(CW\*(C`void\*(C'\fR.
-\&\s-1ISO C\s0 prohibits qualified \f(CW\*(C`void\*(C'\fR return types on function
+\&\s-1ISO\s0 C prohibits qualified \f(CW\*(C`void\*(C'\fR return types on function
definitions, so such return types always receive a warning
even without this option.
.Sp
@@ -3717,9 +3717,9 @@ expression to a type other than \f(CW\*(C`bool\*(C'\fR. For example:
.Sp
This warning is enabled by default for C and \*(C+ programs.
.IP "\fB\-Wsync\-nand\fR (C and \*(C+ only)" 4
-.IX Item "-Wsync-nand (C and only)"
+.IX Item "-Wsync-nand (C and only)"
Warn when \f(CW\*(C`_\|_sync_fetch_and_nand\*(C'\fR and \f(CW\*(C`_\|_sync_nand_and_fetch\*(C'\fR
-built-in functions are used. These functions changed semantics in \s-1GCC 4.4.\s0
+built-in functions are used. These functions changed semantics in \s-1GCC\s0 4.4.
.IP "\fB\-Wtrigraphs\fR" 4
.IX Item "-Wtrigraphs"
Warn if any trigraphs are encountered that might change the meaning of
@@ -3756,7 +3756,7 @@ This warning is enabled by \fB\-Wall\fR.
.Sp
To suppress this warning use the \f(CW\*(C`unused\*(C'\fR attribute.
.IP "\fB\-Wunused\-local\-typedefs\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4
-.IX Item "-Wunused-local-typedefs (C, Objective-C, and Objective- only)"
+.IX Item "-Wunused-local-typedefs (C, Objective-C, and Objective- only)"
Warn when a typedef locally defined in a function is not used.
This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wunused\-parameter\fR" 4
@@ -3863,7 +3863,7 @@ This warning is enabled by \fB\-Wall\fR or \fB\-Wextra\fR.
.IP "\fB\-Wunknown\-pragmas\fR" 4
.IX Item "-Wunknown-pragmas"
Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by
-\&\s-1GCC. \s0 If this command-line option is used, warnings are even issued
+\&\s-1GCC\s0. If this command-line option is used, warnings are even issued
for unknown pragmas in system header files. This is not the case if
the warnings are only enabled by the \fB\-Wall\fR command-line option.
.IP "\fB\-Wno\-pragmas\fR" 4
@@ -4141,13 +4141,13 @@ probably mistaken.
.IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4
.IX Item "-Wtraditional (C and Objective-C only)"
Warn about certain constructs that behave differently in traditional and
-\&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C
+\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
equivalent, and/or problematic constructs that should be avoided.
.RS 4
.IP "*" 4
Macro parameters that appear within string literals in the macro body.
In traditional C macro replacement takes place within string literals,
-but in \s-1ISO C\s0 it does not.
+but in \s-1ISO\s0 C it does not.
.IP "*" 4
In traditional C, some preprocessor directives did not exist.
Traditional preprocessors only considered a line to be a directive
@@ -4202,9 +4202,9 @@ versa. The absence of these prototypes when compiling with traditional
C causes serious problems. This is a subset of the possible
conversion warnings; for the full set use \fB\-Wtraditional\-conversion\fR.
.IP "*" 4
-Use of \s-1ISO C\s0 style function definitions. This warning intentionally is
+Use of \s-1ISO\s0 C style function definitions. This warning intentionally is
\&\fInot\fR issued for prototype declarations or variadic functions
-because these \s-1ISO C\s0 features appear in your code when using
+because these \s-1ISO\s0 C features appear in your code when using
libiberty's traditional C compatibility macros, \f(CW\*(C`PARAMS\*(C'\fR and
\&\f(CW\*(C`VPARAMS\*(C'\fR. This warning is also bypassed for nested functions
because that feature is already a \s-1GCC\s0 extension and thus not relevant to
@@ -4222,8 +4222,8 @@ except when the same as the default promotion.
.IP "\fB\-Wdeclaration\-after\-statement\fR (C and Objective-C only)" 4
.IX Item "-Wdeclaration-after-statement (C and Objective-C only)"
Warn when a declaration is found after a statement in a block. This
-construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default
-allowed in \s-1GCC. \s0 It is not supported by \s-1ISO C90. \s0
+construct, known from \*(C+, was introduced with \s-1ISO\s0 C99 and is by default
+allowed in \s-1GCC\s0. It is not supported by \s-1ISO\s0 C90.
.IP "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive.
@@ -4305,7 +4305,7 @@ which depend on the \s-1MS\s0 runtime.
.IP "\fB\-Wpointer\-arith\fR" 4
.IX Item "-Wpointer-arith"
Warn about anything that depends on the \*(L"size of\*(R" a function type or
-of \f(CW\*(C`void\*(C'\fR. \s-1GNU C\s0 assigns these types a size of 1, for
+of \f(CW\*(C`void\*(C'\fR. \s-1GNU\s0 C assigns these types a size of 1, for
convenience in calculations with \f(CW\*(C`void *\*(C'\fR pointers and pointers
to functions. In \*(C+, warn also when an arithmetic operation involves
\&\f(CW\*(C`NULL\*(C'\fR. This warning is also enabled by \fB\-Wpedantic\fR.
@@ -4323,14 +4323,14 @@ For example, warn if a call to a function returning an integer type
is cast to a pointer type.
.IP "\fB\-Wc90\-c99\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc90-c99-compat (C and Objective-C only)"
-Warn about features not present in \s-1ISO C90,\s0 but present in \s-1ISO C99.\s0
+Warn about features not present in \s-1ISO\s0 C90, but present in \s-1ISO\s0 C99.
For instance, warn about use of variable length arrays, \f(CW\*(C`long long\*(C'\fR
type, \f(CW\*(C`bool\*(C'\fR type, compound literals, designated initializers, and so
on. This option is independent of the standards mode. Warnings are disabled
in the expression that follows \f(CW\*(C`_\|_extension_\|_\*(C'\fR.
.IP "\fB\-Wc99\-c11\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc99-c11-compat (C and Objective-C only)"
-Warn about features not present in \s-1ISO C99,\s0 but present in \s-1ISO C11.\s0
+Warn about features not present in \s-1ISO\s0 C99, but present in \s-1ISO\s0 C11.
For instance, warn about use of anonymous structures and unions,
\&\f(CW\*(C`_Atomic\*(C'\fR type qualifier, \f(CW\*(C`_Thread_local\*(C'\fR storage-class specifier,
\&\f(CW\*(C`_Alignas\*(C'\fR specifier, \f(CW\*(C`Alignof\*(C'\fR operator, \f(CW\*(C`_Generic\*(C'\fR keyword,
@@ -4338,19 +4338,19 @@ and so on. This option is independent of the standards mode. Warnings are
disabled in the expression that follows \f(CW\*(C`_\|_extension_\|_\*(C'\fR.
.IP "\fB\-Wc++\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc++-compat (C and Objective-C only)"
-Warn about \s-1ISO C\s0 constructs that are outside of the common subset of
-\&\s-1ISO C\s0 and \s-1ISO \*(C+,\s0 e.g. request for implicit conversion from
+Warn about \s-1ISO\s0 C constructs that are outside of the common subset of
+\&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+, e.g. request for implicit conversion from
\&\f(CW\*(C`void *\*(C'\fR to a pointer to non\-\f(CW\*(C`void\*(C'\fR type.
.IP "\fB\-Wc++11\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wc++11-compat ( and Objective- only)"
-Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0
-and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords
-in \s-1ISO \*(C+ 2011. \s0 This warning turns on \fB\-Wnarrowing\fR and is
+Warn about \*(C+ constructs whose meaning differs between \s-1ISO\s0 \*(C+ 1998
+and \s-1ISO\s0 \*(C+ 2011, e.g., identifiers in \s-1ISO\s0 \*(C+ 1998 that are keywords
+in \s-1ISO\s0 \*(C+ 2011. This warning turns on \fB\-Wnarrowing\fR and is
enabled by \fB\-Wall\fR.
.IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wc++14-compat ( and Objective- only)"
-Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0
-and \s-1ISO \*(C+ 2014. \s0 This warning is enabled by \fB\-Wall\fR.
+Warn about \*(C+ constructs whose meaning differs between \s-1ISO\s0 \*(C+ 2011
+and \s-1ISO\s0 \*(C+ 2014. This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wcast\-qual\fR" 4
.IX Item "-Wcast-qual"
Warn whenever a pointer is cast so as to remove a type qualifier from
@@ -4653,26 +4653,26 @@ Usually they indicate a typo in the user's code, as they have
implementation-defined values, and should not be used in portable code.
.IP "\fB\-Wnormalized\fR[\fB=\fR<\fBnone\fR|\fBid\fR|\fBnfc\fR|\fBnfkc\fR>]" 4
.IX Item "-Wnormalized[=<none|id|nfc|nfkc>]"
-In \s-1ISO C\s0 and \s-1ISO \*(C+,\s0 two identifiers are different if they are
+In \s-1ISO\s0 C and \s-1ISO\s0 \*(C+, two identifiers are different if they are
different sequences of characters. However, sometimes when characters
outside the basic \s-1ASCII\s0 character set are used, you can have two
different character sequences that look the same. To avoid confusion,
-the \s-1ISO 10646\s0 standard sets out some \fInormalization rules\fR which
+the \s-1ISO\s0 10646 standard sets out some \fInormalization rules\fR which
when applied ensure that two sequences that look the same are turned into
the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that
have not been normalized; this option controls that warning.
.Sp
-There are four levels of warning supported by \s-1GCC. \s0 The default is
+There are four levels of warning supported by \s-1GCC\s0. The default is
\&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is
-not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
+not in the \s-1ISO\s0 10646 \*(L"C\*(R" normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
recommended form for most uses. It is equivalent to
\&\fB\-Wnormalized\fR.
.Sp
Unfortunately, there are some characters allowed in identifiers by
-\&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in
+\&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+ that, when turned into \s-1NFC\s0, are not allowed in
identifiers. That is, there's no way to use these symbols in portable
-\&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC.
-\&\s0\fB\-Wnormalized=id\fR suppresses the warning for these characters.
+\&\s-1ISO\s0 C or \*(C+ and have all your identifiers in \s-1NFC\s0.
+\&\fB\-Wnormalized=id\fR suppresses the warning for these characters.
It is hoped that future versions of the standards involved will correct
this, which is why this option is not the default.
.Sp
@@ -4682,11 +4682,11 @@ only do this if you are using some other normalization scheme (like
\&\*(L"D\*(R"), because otherwise you can easily create bugs that are
literally impossible to see.
.Sp
-Some characters in \s-1ISO 10646\s0 have distinct meanings but look identical
+Some characters in \s-1ISO\s0 10646 have distinct meanings but look identical
in some fonts or display methodologies, especially once formatting has
-been applied. For instance \f(CW\*(C`\eu207F\*(C'\fR, \*(L"\s-1SUPERSCRIPT LATIN SMALL
-LETTER N\*(R",\s0 displays just like a regular \f(CW\*(C`n\*(C'\fR that has been
-placed in a superscript. \s-1ISO 10646\s0 defines the \fI\s-1NFKC\s0\fR
+been applied. For instance \f(CW\*(C`\eu207F\*(C'\fR, \*(L"\s-1SUPERSCRIPT\s0 \s-1LATIN\s0 \s-1SMALL\s0
+\&\s-1LETTER\s0 N\*(R", displays just like a regular \f(CW\*(C`n\*(C'\fR that has been
+placed in a superscript. \s-1ISO\s0 10646 defines the \fI\s-1NFKC\s0\fR
normalization scheme to convert all these into a standard form as
well, and \s-1GCC\s0 warns if your code is not in \s-1NFKC\s0 if you use
\&\fB\-Wnormalized=nfkc\fR. This warning is comparable to warning
@@ -4744,9 +4744,9 @@ have the packed attribute:
.IP "\fB\-Wpacked\-bitfield\-compat\fR" 4
.IX Item "-Wpacked-bitfield-compat"
The 4.1, 4.2 and 4.3 series of \s-1GCC\s0 ignore the \f(CW\*(C`packed\*(C'\fR attribute
-on bit-fields of type \f(CW\*(C`char\*(C'\fR. This has been fixed in \s-1GCC 4.4\s0 but
+on bit-fields of type \f(CW\*(C`char\*(C'\fR. This has been fixed in \s-1GCC\s0 4.4 but
the change can lead to differences in the structure layout. \s-1GCC\s0
-informs you when the offset of such a field has changed in \s-1GCC 4.4.\s0
+informs you when the offset of such a field has changed in \s-1GCC\s0 4.4.
For example there is no longer a 4\-bit padding between field \f(CW\*(C`a\*(C'\fR
and \f(CW\*(C`b\*(C'\fR in this structure:
.Sp
@@ -4793,7 +4793,7 @@ warnings produced by \fB\-Winline\fR to appear or disappear.
.IP "\fB\-Wno\-invalid\-offsetof\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wno-invalid-offsetof ( and Objective- only)"
Suppress warnings from applying the \f(CW\*(C`offsetof\*(C'\fR macro to a non-POD
-type. According to the 2014 \s-1ISO \*(C+\s0 standard, applying \f(CW\*(C`offsetof\*(C'\fR
+type. According to the 2014 \s-1ISO\s0 \*(C+ standard, applying \f(CW\*(C`offsetof\*(C'\fR
to a non-standard-layout type is undefined. In existing \*(C+ implementations,
however, \f(CW\*(C`offsetof\*(C'\fR typically gives meaningful results.
This flag is for users who are aware that they are
@@ -4818,12 +4818,12 @@ the search path but can't be used.
.IP "\fB\-Wlong\-long\fR" 4
.IX Item "-Wlong-long"
Warn if \f(CW\*(C`long long\*(C'\fR type is used. This is enabled by either
-\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR in \s-1ISO C90\s0 and \*(C+98
+\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR in \s-1ISO\s0 C90 and \*(C+98
modes. To inhibit the warning messages, use \fB\-Wno\-long\-long\fR.
.IP "\fB\-Wvariadic\-macros\fR" 4
.IX Item "-Wvariadic-macros"
-Warn if variadic macros are used in \s-1ISO C90\s0 mode, or if the \s-1GNU\s0
-alternate syntax is used in \s-1ISO C99\s0 mode. This is enabled by either
+Warn if variadic macros are used in \s-1ISO\s0 C90 mode, or if the \s-1GNU\s0
+alternate syntax is used in \s-1ISO\s0 C99 mode. This is enabled by either
\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR. To inhibit the warning
messages, use \fB\-Wno\-variadic\-macros\fR.
.IP "\fB\-Wvarargs\fR" 4
@@ -4887,7 +4887,7 @@ standard's minimum limit, but very portable programs should avoid
using longer strings.
.Sp
The limit applies \fIafter\fR string constant concatenation, and does
-not count the trailing \s-1NUL. \s0 In C90, the limit was 509 characters; in
+not count the trailing \s-1NUL\s0. In C90, the limit was 509 characters; in
C99, it was raised to 4095. \*(C+98 does not specify a normative
minimum maximum, so we do not diagnose overlength strings in \*(C+.
.Sp
@@ -4905,14 +4905,14 @@ from the decimal floating-point extension to C99.
Suppress warnings when a positional initializer is used to initialize
a structure that has been marked with the \f(CW\*(C`designated_init\*(C'\fR
attribute.
-.SS "Options for Debugging Your Program or \s-1GCC\s0"
+.Sh "Options for Debugging Your Program or \s-1GCC\s0"
.IX Subsection "Options for Debugging Your Program or GCC"
\&\s-1GCC\s0 has various special options that are used for debugging
either your program or \s-1GCC:\s0
.IP "\fB\-g\fR" 4
.IX Item "-g"
Produce debugging information in the operating system's native format
-(stabs, \s-1COFF, XCOFF,\s0 or \s-1DWARF 2\s0). \s-1GDB\s0 can work with this debugging
+(stabs, \s-1COFF\s0, \s-1XCOFF\s0, or \s-1DWARF\s0 2). \s-1GDB\s0 can work with this debugging
information.
.Sp
On most systems that use stabs format, \fB\-g\fR enables use of extra
@@ -4945,8 +4945,8 @@ be useful, this option requires a debugger capable of reading .dwo
files.
.IP "\fB\-ggdb\fR" 4
.IX Item "-ggdb"
-Produce debugging information for use by \s-1GDB. \s0 This means to use the
-most expressive format available (\s-1DWARF 2,\s0 stabs, or the native format
+Produce debugging information for use by \s-1GDB\s0. This means to use the
+most expressive format available (\s-1DWARF\s0 2, stabs, or the native format
if neither of those are supported), including \s-1GDB\s0 extensions if at all
possible.
.IP "\fB\-gpubnames\fR" 4
@@ -4961,8 +4961,8 @@ with a linker that can produce \s-1GDB\s0 index version 7.
.IX Item "-gstabs"
Produce debugging information in stabs format (if that is supported),
without \s-1GDB\s0 extensions. This is the format used by \s-1DBX\s0 on most \s-1BSD\s0
-systems. On \s-1MIPS,\s0 Alpha and System V Release 4 systems this option
-produces stabs debugging output that is not understood by \s-1DBX\s0 or \s-1SDB.\s0
+systems. On \s-1MIPS\s0, Alpha and System V Release 4 systems this option
+produces stabs debugging output that is not understood by \s-1DBX\s0 or \s-1SDB\s0.
On System V Release 4 systems this option requires the \s-1GNU\s0 assembler.
.IP "\fB\-feliminate\-unused\-debug\-symbols\fR" 4
.IX Item "-feliminate-unused-debug-symbols"
@@ -4999,7 +4999,7 @@ System V Release 4.
.IP "\fB\-gxcoff\fR" 4
.IX Item "-gxcoff"
Produce debugging information in \s-1XCOFF\s0 format (if that is supported).
-This is the format used by the \s-1DBX\s0 debugger on \s-1IBM RS/6000\s0 systems.
+This is the format used by the \s-1DBX\s0 debugger on \s-1IBM\s0 \s-1RS/6000\s0 systems.
.IP "\fB\-gxcoff+\fR" 4
.IX Item "-gxcoff+"
Produce debugging information in \s-1XCOFF\s0 format (if that is supported),
@@ -5014,9 +5014,9 @@ The value of \fIversion\fR may be either 2, 3, 4 or 5; the default version
for most targets is 4. \s-1DWARF\s0 Version 5 is only experimental.
.Sp
Note that with \s-1DWARF\s0 Version 2, some ports require and always
-use some non-conflicting \s-1DWARF 3\s0 extensions in the unwind tables.
+use some non-conflicting \s-1DWARF\s0 3 extensions in the unwind tables.
.Sp
-Version 4 may require \s-1GDB 7.0\s0 and \fB\-fvar\-tracking\-assignments\fR
+Version 4 may require \s-1GDB\s0 7.0 and \fB\-fvar\-tracking\-assignments\fR
for maximum benefit.
.IP "\fB\-grecord\-gcc\-switches\fR" 4
.IX Item "-grecord-gcc-switches"
@@ -5089,7 +5089,7 @@ debug information in version 1 of the \s-1DWARF\s0 format (which is very
different from version 2), and it would have been too confusing. That
debug format is long obsolete, but the option cannot be changed now.
Instead use an additional \fB\-g\fR\fIlevel\fR option to change the
-debug level for \s-1DWARF.\s0
+debug level for \s-1DWARF\s0.
.IP "\fB\-gtoggle\fR" 4
.IX Item "-gtoggle"
Turn off generation of debug info, if leaving out this option
@@ -5141,7 +5141,7 @@ at runtime. Current suboptions are:
.IX Item "-fsanitize=shift"
This option enables checking that the result of a shift operation is
not undefined. Note that what exactly is considered undefined differs
-slightly between C and \*(C+, as well as between \s-1ISO C90\s0 and C99, etc.
+slightly between C and \*(C+, as well as between \s-1ISO\s0 C90 and C99, etc.
.IP "\fB\-fsanitize=integer\-divide\-by\-zero\fR" 4
.IX Item "-fsanitize=integer-divide-by-zero"
Detect integer division by zero as well as \f(CW\*(C`INT_MIN / \-1\*(C'\fR division.
@@ -5447,9 +5447,9 @@ When this option is passed to the compiler driver, it causes the
other than debugging the compiler proper.
.IP "\fB\-feliminate\-dwarf2\-dups\fR" 4
.IX Item "-feliminate-dwarf2-dups"
-Compress \s-1DWARF 2\s0 debugging information by eliminating duplicated
+Compress \s-1DWARF\s0 2 debugging information by eliminating duplicated
information about each symbol. This option only makes sense when
-generating \s-1DWARF 2\s0 debugging information with \fB\-gdwarf\-2\fR.
+generating \s-1DWARF\s0 2 debugging information with \fB\-gdwarf\-2\fR.
.IP "\fB\-femit\-struct\-debug\-baseonly\fR" 4
.IX Item "-femit-struct-debug-baseonly"
Emit debug information for struct-like types
@@ -5461,7 +5461,7 @@ but at significant potential loss in type information to the debugger.
See \fB\-femit\-struct\-debug\-reduced\fR for a less aggressive option.
See \fB\-femit\-struct\-debug\-detailed\fR for more detailed control.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-femit\-struct\-debug\-reduced\fR" 4
.IX Item "-femit-struct-debug-reduced"
Emit debug information for struct-like types
@@ -5474,7 +5474,7 @@ with some potential loss in type information to the debugger.
See \fB\-femit\-struct\-debug\-baseonly\fR for a more aggressive option.
See \fB\-femit\-struct\-debug\-detailed\fR for more detailed control.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-femit\-struct\-debug\-detailed\fR[\fB=\fR\fIspec-list\fR]" 4
.IX Item "-femit-struct-debug-detailed[=spec-list]"
Specify the struct-like types
@@ -5520,7 +5520,7 @@ You may need to experiment to determine the best settings for your application.
.Sp
The default is \fB\-femit\-struct\-debug\-detailed=all\fR.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-fno\-merge\-debug\-strings\fR" 4
.IX Item "-fno-merge-debug-strings"
Direct the linker to not merge together strings in the debugging
@@ -5534,8 +5534,8 @@ When compiling files in directory \fI\fIold\fI\fR, record debugging
information describing them as in \fI\fInew\fI\fR instead.
.IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4
.IX Item "-fno-dwarf2-cfi-asm"
-Emit \s-1DWARF 2\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section
-instead of using \s-1GAS \s0\f(CW\*(C`.cfi_*\*(C'\fR directives.
+Emit \s-1DWARF\s0 2 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section
+instead of using \s-1GAS\s0 \f(CW\*(C`.cfi_*\*(C'\fR directives.
.IP "\fB\-p\fR" 4
.IX Item "-p"
Generate extra code to write profile information suitable for the
@@ -5692,7 +5692,7 @@ For example, with \fB\-fdbg\-cnt=dce:10,tail_call:0\fR,
.IX Item "-fdisable-kind-pass=range-list"
.PD
This is a set of options that are used to explicitly disable/enable
-optimization passes. These options are intended for use for debugging \s-1GCC.\s0
+optimization passes. These options are intended for use for debugging \s-1GCC\s0.
Compiler users should use regular options for enabling/disabling
passes instead.
.RS 4
@@ -6165,7 +6165,7 @@ by some other path.
When dumping pretty-printed trees, this option inhibits dumping the
bodies of control structures.
.Sp
-When dumping \s-1RTL,\s0 print the \s-1RTL\s0 in slim (condensed) form instead of
+When dumping \s-1RTL\s0, print the \s-1RTL\s0 in slim (condensed) form instead of
the default LISP-like representation.
.IP "\fBraw\fR" 4
.IX Item "raw"
@@ -6200,7 +6200,7 @@ Enable showing virtual operands for every statement.
Enable showing line numbers for statements.
.IP "\fBuid\fR" 4
.IX Item "uid"
-Enable showing the unique \s-1ID \s0(\f(CW\*(C`DECL_UID\*(C'\fR) for each variable.
+Enable showing the unique \s-1ID\s0 (\f(CW\*(C`DECL_UID\*(C'\fR) for each variable.
.IP "\fBverbose\fR" 4
.IX Item "verbose"
Enable showing the tree dump for each statement.
@@ -6278,7 +6278,7 @@ Dump aliasing information for each function. The file name is made by
appending \fI.alias\fR to the source file name.
.IP "\fBccp\fR" 4
.IX Item "ccp"
-Dump each function after \s-1CCP. \s0 The file name is made by appending
+Dump each function after \s-1CCP\s0. The file name is made by appending
\&\fI.ccp\fR to the source file name.
.IP "\fBstoreccp\fR" 4
.IX Item "storeccp"
@@ -6693,7 +6693,7 @@ Print the compiler's built-in specs\-\-\-and don't do anything else. (This
is used when \s-1GCC\s0 itself is being built.)
.IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4
.IX Item "-fno-eliminate-unused-debug-types"
-Normally, when producing \s-1DWARF 2\s0 output, \s-1GCC\s0 avoids producing debug symbol
+Normally, when producing \s-1DWARF\s0 2 output, \s-1GCC\s0 avoids producing debug symbol
output for types that are nowhere used in the source file being compiled.
Sometimes it is useful to have \s-1GCC\s0 emit debugging
information for all types declared in a compilation
@@ -6702,7 +6702,7 @@ in that compilation unit, for example
if, in the debugger, you want to cast a value to a type that is
not actually used in your program (but is declared). More often,
however, this results in a significant amount of wasted space.
-.SS "Options That Control Optimization"
+.Sh "Options That Control Optimization"
.IX Subsection "Options That Control Optimization"
These options control various sorts of optimizations.
.PP
@@ -6898,7 +6898,7 @@ function calls and pops them all at once.
Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR.
.IP "\fB\-fforward\-propagate\fR" 4
.IX Item "-fforward-propagate"
-Perform a forward propagation pass on \s-1RTL. \s0 The pass tries to combine two
+Perform a forward propagation pass on \s-1RTL\s0. The pass tries to combine two
instructions and checks if the result can be simplified. If loop unrolling
is active, two passes are performed and the second is scheduled after
loop unrolling.
@@ -6924,7 +6924,7 @@ restore frame pointers; it also makes an extra register available
in many functions. \fBIt also makes debugging impossible on
some machines.\fR
.Sp
-On some machines, such as the \s-1VAX,\s0 this flag has no effect, because
+On some machines, such as the \s-1VAX\s0, this flag has no effect, because
the standard calling sequence automatically handles the frame pointer
and nothing is saved by pretending it doesn't exist. The
machine-description macro \f(CW\*(C`FRAME_POINTER_REQUIRED\*(C'\fR controls
@@ -7049,7 +7049,7 @@ attribute or declspec
In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR
into the object file, even if the function has been inlined into all
of its callers. This switch does not affect functions using the
-\&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90. \s0 In \*(C+, emit any and all
+\&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU\s0 C90. In \*(C+, emit any and all
inline functions into the object file.
.IP "\fB\-fkeep\-static\-consts\fR" 4
.IX Item "-fkeep-static-consts"
@@ -7116,7 +7116,7 @@ The default is \fB\-ffunction\-cse\fR
.IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4
.IX Item "-fno-zero-initialized-in-bss"
If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that
-are initialized to zero into \s-1BSS. \s0 This can save space in the resulting
+are initialized to zero into \s-1BSS\s0. This can save space in the resulting
code.
.Sp
This option turns off this behavior because some programs explicitly
@@ -7239,11 +7239,11 @@ instructions to support this. Enabled by default at \fB\-O\fR and
higher on architectures that support this.
.IP "\fB\-fdce\fR" 4
.IX Item "-fdce"
-Perform dead code elimination (\s-1DCE\s0) on \s-1RTL.\s0
+Perform dead code elimination (\s-1DCE\s0) on \s-1RTL\s0.
Enabled by default at \fB\-O\fR and higher.
.IP "\fB\-fdse\fR" 4
.IX Item "-fdse"
-Perform dead store elimination (\s-1DSE\s0) on \s-1RTL.\s0
+Perform dead store elimination (\s-1DSE\s0) on \s-1RTL\s0.
Enabled by default at \fB\-O\fR and higher.
.IP "\fB\-fif\-conversion\fR" 4
.IX Item "-fif-conversion"
@@ -7403,7 +7403,7 @@ The default value is 5. If the value \fIn\fR is greater or equal to 10,
the dump output is sent to stderr using the same format as \fIn\fR minus 10.
.IP "\fB\-flra\-remat\fR" 4
.IX Item "-flra-remat"
-Enable CFG-sensitive rematerialization in \s-1LRA. \s0 Instead of loading
+Enable CFG-sensitive rematerialization in \s-1LRA\s0. Instead of loading
values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate)
values if it is profitable.
.Sp
@@ -7562,9 +7562,9 @@ When pipelining loops during selective scheduling, also pipeline outer loops.
This option has no effect unless \fB\-fsel\-sched\-pipelining\fR is turned on.
.IP "\fB\-fsemantic\-interposition\fR" 4
.IX Item "-fsemantic-interposition"
-Some object formats, like \s-1ELF,\s0 allow interposing of symbols by the
+Some object formats, like \s-1ELF\s0, allow interposing of symbols by the
dynamic linker.
-This means that for symbols exported from the \s-1DSO,\s0 the compiler cannot perform
+This means that for symbols exported from the \s-1DSO\s0, the compiler cannot perform
interprocedural propagation, inlining and other optimizations in anticipation
that the function or variable in question may change. While this feature is
useful, for example, to rewrite memory allocation functions by a debugging
@@ -7634,7 +7634,7 @@ at \fB\-O\fR and higher.
Perform full redundancy elimination (\s-1FRE\s0) on trees. The difference
between \s-1FRE\s0 and \s-1PRE\s0 is that \s-1FRE\s0 only considers expressions
that are computed on all paths leading to the redundant computation.
-This analysis is faster than \s-1PRE,\s0 though it exposes fewer redundancies.
+This analysis is faster than \s-1PRE\s0, though it exposes fewer redundancies.
This flag is enabled by default at \fB\-O\fR and higher.
.IP "\fB\-ftree\-phiprop\fR" 4
.IX Item "-ftree-phiprop"
@@ -7705,7 +7705,7 @@ The optimization reduces code size and may disturb unwind stacks by replacing
a function by equivalent one with a different name. The optimization works
more effectively with link time optimization enabled.
.Sp
-Nevertheless the behavior is similar to Gold Linker \s-1ICF\s0 optimization, \s-1GCC ICF\s0
+Nevertheless the behavior is similar to Gold Linker \s-1ICF\s0 optimization, \s-1GCC\s0 \s-1ICF\s0
works on different levels and thus the optimizations are not same \- there are
equivalences that are found only by \s-1GCC\s0 and equivalences found only by Gold.
.Sp
@@ -7740,7 +7740,7 @@ pass only operates on local scalar variables and is enabled by default
at \fB\-O\fR and higher.
.IP "\fB\-fssa\-phiopt\fR" 4
.IX Item "-fssa-phiopt"
-Perform pattern matching on \s-1SSA PHI\s0 nodes to optimize conditional
+Perform pattern matching on \s-1SSA\s0 \s-1PHI\s0 nodes to optimize conditional
code. This pass is enabled by default at \fB\-O\fR and higher.
.IP "\fB\-ftree\-switch\-conversion\fR" 4
.IX Item "-ftree-switch-conversion"
@@ -7896,8 +7896,8 @@ to enable the Graphite loop transformation infrastructure.
Enable the identity transformation for graphite. For every SCoP we generate
the polyhedral representation and transform it back to gimple. Using
\&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the
-\&\s-1GIMPLE \-\s0> \s-1GRAPHITE \-\s0> \s-1GIMPLE\s0 transformation. Some minimal optimizations
-are also performed by the code generator \s-1ISL,\s0 like index splitting and
+\&\s-1GIMPLE\s0 \-> \s-1GRAPHITE\s0 \-> \s-1GIMPLE\s0 transformation. Some minimal optimizations
+are also performed by the code generator \s-1ISL\s0, like index splitting and
dead code elimination in loops.
.IP "\fB\-floop\-nest\-optimize\fR" 4
.IX Item "-floop-nest-optimize"
@@ -8402,7 +8402,7 @@ targets.
Constructs webs as commonly used for register allocation purposes and assign
each web individual pseudo register. This allows the register allocation pass
to operate on pseudos directly, but also strengthens several other optimization
-passes, such as \s-1CSE,\s0 loop optimizer and trivial dead code remover. It can,
+passes, such as \s-1CSE\s0, loop optimizer and trivial dead code remover. It can,
however, make debugging impossible, since variables no longer stay in a
\&\*(L"home register\*(R".
.Sp
@@ -8420,7 +8420,7 @@ information.
.IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4
.IX Item "-flto[=n]"
This option runs the standard link-time optimizer. When invoked
-with source code, it generates \s-1GIMPLE \s0(one of \s-1GCC\s0's internal
+with source code, it generates \s-1GIMPLE\s0 (one of \s-1GCC\s0's internal
representations) and writes it to special \s-1ELF\s0 sections in the object
file. When the object files are linked together, all the function
bodies are read from these \s-1ELF\s0 sections and instantiated as if they
@@ -8545,7 +8545,7 @@ link time.
.Sp
If \s-1LTO\s0 encounters objects with C linkage declared with incompatible
types in separate translation units to be linked together (undefined
-behavior according to \s-1ISO C99 6.2.7\s0), a non-fatal diagnostic may be
+behavior according to \s-1ISO\s0 C99 6.2.7), a non-fatal diagnostic may be
issued. The behavior is still undefined at run time. Similar
diagnostics may be raised for other languages.
.Sp
@@ -8568,7 +8568,7 @@ regular (non-LTO) compilation.
If object files containing \s-1GIMPLE\s0 bytecode are stored in a library archive, say
\&\fIlibfoo.a\fR, it is possible to extract and use them in an \s-1LTO\s0 link if you
are using a linker with plugin support. To create static libraries suitable
-for \s-1LTO,\s0 use \fBgcc-ar\fR and \fBgcc-ranlib\fR instead of \fBar\fR
+for \s-1LTO\s0, use \fBgcc-ar\fR and \fBgcc-ranlib\fR instead of \fBar\fR
and \fBranlib\fR;
to show the symbols of object files with \s-1GIMPLE\s0 bytecode, use
\&\fBgcc-nm\fR. Those commands require that \fBar\fR, \fBranlib\fR
@@ -8603,7 +8603,7 @@ The current implementation of \s-1LTO\s0 makes no
attempt to generate bytecode that is portable between different
types of hosts. The bytecode files are versioned and there is a
strict version check, so bytecode files generated in one version of
-\&\s-1GCC\s0 do not work with an older or newer version of \s-1GCC.\s0
+\&\s-1GCC\s0 do not work with an older or newer version of \s-1GCC\s0.
.Sp
Link-time optimization does not work well with generation of debugging
information. Combining \fB\-flto\fR with
@@ -8686,8 +8686,8 @@ and the object code. This makes them usable for both \s-1LTO\s0 linking and norm
linking. This option is effective only when compiling with \fB\-flto\fR
and is ignored at link time.
.Sp
-\&\fB\-fno\-fat\-lto\-objects\fR improves compilation time over plain \s-1LTO,\s0 but
-requires the complete toolchain to be aware of \s-1LTO.\s0 It requires a linker with
+\&\fB\-fno\-fat\-lto\-objects\fR improves compilation time over plain \s-1LTO\s0, but
+requires the complete toolchain to be aware of \s-1LTO\s0. It requires a linker with
linker plugin support for basic functionality. Additionally,
\&\fBnm\fR, \fBar\fR and \fBranlib\fR
need to support linker plugins to allow a full-featured build environment
@@ -8796,7 +8796,7 @@ E.g.
.Ve
.Sp
Then use the \fBcreate_gcov\fR tool to convert the raw profile data
-to a format that can be used by \s-1GCC. \s0 You must also supply the
+to a format that can be used by \s-1GCC\s0. You must also supply the
unstripped binary for your program to this tool.
See <\fBhttps://github.com/google/autofdo\fR>.
.Sp
@@ -8826,15 +8826,15 @@ them to store all pertinent intermediate computations into variables.
.IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4
.IX Item "-fexcess-precision=style"
This option allows further control over excess precision on machines
-where floating-point registers have more precision than the \s-1IEEE
-\&\s0\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not
+where floating-point registers have more precision than the \s-1IEEE\s0
+\&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not
support operations rounding to those types. By default,
\&\fB\-fexcess\-precision=fast\fR is in effect; this means that
operations are carried out in the precision of the registers and that
it is unpredictable when rounding to the types specified in the source
code takes place. When compiling C, if
\&\fB\-fexcess\-precision=standard\fR is specified then excess
-precision follows the rules specified in \s-1ISO C99\s0; in particular,
+precision follows the rules specified in \s-1ISO\s0 C99; in particular,
both casts and assignments cause values to be rounded to their
semantic types (whereas \fB\-ffloat\-store\fR only affects
assignments). This option is enabled by default for C if a strict
@@ -8898,7 +8898,7 @@ The default is \fB\-fno\-unsafe\-math\-optimizations\fR.
.IP "\fB\-fassociative\-math\fR" 4
.IX Item "-fassociative-math"
Allow re-association of operands in series of floating-point operations.
-This violates the \s-1ISO C\s0 and \*(C+ language standard by possibly changing
+This violates the \s-1ISO\s0 C and \*(C+ language standard by possibly changing
computation result. \s-1NOTE:\s0 re-ordering may change the sign of zero as
well as ignore NaNs and inhibit or create underflow or overflow (and
thus cannot be used on code that relies on rounding behavior like
@@ -9001,8 +9001,8 @@ whether the result of a complex multiplication or division is \f(CW\*(C`NaN
default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by
\&\fB\-ffast\-math\fR.
.Sp
-This option controls the default setting of the \s-1ISO C99
-\&\s0\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to
+This option controls the default setting of the \s-1ISO\s0 C99
+\&\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to
all languages.
.IP "\fB\-fcx\-fortran\-rules\fR" 4
.IX Item "-fcx-fortran-rules"
@@ -9273,7 +9273,7 @@ optimization is not done.
.IP "\fBmax-gcse-insertion-ratio\fR" 4
.IX Item "max-gcse-insertion-ratio"
If the ratio of expression insertions to deletions is larger than this value
-for any expression, then \s-1RTL PRE\s0 inserts or removes the expression and thus
+for any expression, then \s-1RTL\s0 \s-1PRE\s0 inserts or removes the expression and thus
leaves partially redundant computations in the instruction stream. The default value is 20.
.IP "\fBmax-pending-list-length\fR" 4
.IX Item "max-pending-list-length"
@@ -9288,7 +9288,7 @@ when modulo scheduling a loop. Larger values can exponentially increase
compilation time.
.IP "\fBmax-inline-insns-single\fR" 4
.IX Item "max-inline-insns-single"
-Several parameters control the tree inliner used in \s-1GCC.\s0
+Several parameters control the tree inliner used in \s-1GCC\s0.
This number sets the maximum number of instructions (counted in \s-1GCC\s0's
internal representation) in a single function that the tree inliner
considers for inlining. This only affects functions declared
@@ -9644,7 +9644,7 @@ Tuning this may improve compilation speed; it has no effect on code
generation.
.Sp
The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when
-\&\s-1RAM \s0>= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is
+\&\s-1RAM\s0 >= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\s0\*(R" is
the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If
\&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower
bound of 30% is used. Setting this parameter and
@@ -9659,7 +9659,7 @@ by \fBggc-min-expand\fR% beyond \fBggc-min-heapsize\fR. Again,
tuning this may improve compilation speed, and has no effect on code
generation.
.Sp
-The default is the smaller of \s-1RAM/8, RLIMIT_RSS,\s0 or a limit that
+The default is the smaller of \s-1RAM/8\s0, \s-1RLIMIT_RSS\s0, or a limit that
tries to ensure that \s-1RLIMIT_DATA\s0 or \s-1RLIMIT_AS\s0 are not exceeded, but
with a lower bound of 4096 (four megabytes) and an upper bound of
131072 (128 megabytes). If \s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a
@@ -9884,7 +9884,7 @@ This value is the best found from numerous experiments.
This optimization is called inheritance. \s-1EBB\s0 is used as a region to
do this optimization. The parameter defines a minimal fall-through
edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in
-\&\s-1LRA. \s0 The default value of the parameter is 40. The value was chosen
+\&\s-1LRA\s0. The default value of the parameter is 40. The value was chosen
from numerous runs of \s-1SPEC2000\s0 on x86\-64.
.IP "\fBloop-invariant-max-bbs-in-loop\fR" 4
.IX Item "loop-invariant-max-bbs-in-loop"
@@ -10026,7 +10026,7 @@ The number of partitions should exceed the number of CPUs used for compilation.
The default value is 32.
.IP "\fBlto-minpartition\fR" 4
.IX Item "lto-minpartition"
-Size of minimal partition for \s-1WHOPR \s0(in estimated instructions).
+Size of minimal partition for \s-1WHOPR\s0 (in estimated instructions).
This prevents expenses of splitting very small programs into too many
partitions.
.IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4
@@ -10138,7 +10138,7 @@ automaton. The default is 50.
.RE
.RS 4
.RE
-.SS "Options Controlling the Preprocessor"
+.Sh "Options Controlling the Preprocessor"
.IX Subsection "Options Controlling the Preprocessor"
These options control the C preprocessor, which is run on each C source
file before actual compilation.
@@ -10262,7 +10262,7 @@ get trigraph conversion without warnings, but get the other
.IP "\fB\-Wtraditional\fR" 4
.IX Item "-Wtraditional"
Warn about certain constructs that behave differently in traditional and
-\&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C
+\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
equivalent, and problematic constructs which should be avoided.
.IP "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
@@ -10315,7 +10315,7 @@ in finding bugs in your own code, therefore suppressed. If you are
responsible for the system library, you may want to see them.
.IP "\fB\-w\fR" 4
.IX Item "-w"
-Suppress all warnings, including those which \s-1GNU CPP\s0 issues by default.
+Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default.
.IP "\fB\-pedantic\fR" 4
.IX Item "-pedantic"
Issue all the mandatory diagnostics listed in the C standard. Some of
@@ -10455,10 +10455,10 @@ This option allows use of a precompiled header together with \fB\-E\fR. It inse
\&\f(CW\*(C`#pragma GCC pch_preprocess "\f(CIfilename\f(CW"\*(C'\fR in the output to mark
the place where the precompiled header was found, and its \fIfilename\fR.
When \fB\-fpreprocessed\fR is in use, \s-1GCC\s0 recognizes this \f(CW\*(C`#pragma\*(C'\fR
-and loads the \s-1PCH.\s0
+and loads the \s-1PCH\s0.
.Sp
This option is off by default, because the resulting preprocessed output
-is only really suitable as input to \s-1GCC. \s0 It is switched on by
+is only really suitable as input to \s-1GCC\s0. It is switched on by
\&\fB\-save\-temps\fR.
.Sp
You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is
@@ -10511,7 +10511,7 @@ may be one of:
.el .IP "\f(CWiso9899:1990\fR" 4
.IX Item "iso9899:1990"
.PD
-The \s-1ISO C\s0 standard from 1990. \fBc90\fR is the customary shorthand for
+The \s-1ISO\s0 C standard from 1990. \fBc90\fR is the customary shorthand for
this version of the standard.
.Sp
The \fB\-ansi\fR option is equivalent to \fB\-std=c90\fR.
@@ -10533,7 +10533,7 @@ The 1990 C standard, as amended in 1994.
.el .IP "\f(CWc9x\fR" 4
.IX Item "c9x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 1999. Before
+The revised \s-1ISO\s0 C standard, published in December 1999. Before
publication, this was known as C9X.
.ie n .IP """iso9899:2011""" 4
.el .IP "\f(CWiso9899:2011\fR" 4
@@ -10546,7 +10546,7 @@ publication, this was known as C9X.
.el .IP "\f(CWc1x\fR" 4
.IX Item "c1x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 2011. Before
+The revised \s-1ISO\s0 C standard, published in December 2011. Before
publication, this was known as C1X.
.ie n .IP """gnu90""" 4
.el .IP "\f(CWgnu90\fR" 4
@@ -10578,7 +10578,7 @@ The 2011 C standard plus \s-1GNU\s0 extensions.
.ie n .IP """c++98""" 4
.el .IP "\f(CWc++98\fR" 4
.IX Item "c++98"
-The 1998 \s-1ISO \*(C+\s0 standard plus amendments.
+The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
.ie n .IP """gnu++98""" 4
.el .IP "\f(CWgnu++98\fR" 4
.IX Item "gnu++98"
@@ -10730,7 +10730,7 @@ line. If the value is less than 1 or greater than 100, the option is
ignored. The default is 8.
.IP "\fB\-fdebug\-cpp\fR" 4
.IX Item "-fdebug-cpp"
-This option is only useful for debugging \s-1GCC. \s0 When used with
+This option is only useful for debugging \s-1GCC\s0. When used with
\&\fB\-E\fR, dumps debugging information about location maps. Every
token in the output is preceded by the dump of the map its location
belongs to. The dump of the map holding the location of a token would
@@ -10763,12 +10763,12 @@ Note that \f(CW\*(C`\-ftrack\-macro\-expansion=2\*(C'\fR is activated by default
.IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fexec-charset=charset"
Set the execution character set, used for string and character
-constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding
+constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
.IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fwide-exec-charset=charset"
Set the wide execution character set, used for wide string and
-character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16,\s0 whichever
+character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever
corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with
\&\fB\-fexec\-charset\fR, \fIcharset\fR can be any encoding supported
by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have
@@ -10776,9 +10776,9 @@ problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR.
.IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4
.IX Item "-finput-charset=charset"
Set the input character set, used for translation from the character
-set of the input file to the source character set used by \s-1GCC. \s0 If the
+set of the input file to the source character set used by \s-1GCC\s0. If the
locale does not specify, or \s-1GCC\s0 cannot get this information from the
-locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale
+locale, the default is \s-1UTF\-8\s0. This can be overridden by either the locale
or this command-line option. Currently the command-line option takes
precedence if there's a conflict. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
@@ -10815,7 +10815,7 @@ Cancel an assertion with the predicate \fIpredicate\fR and answer
.IX Item "-dCHARS"
\&\fI\s-1CHARS\s0\fR is a sequence of one or more of the following characters,
and must not be preceded by a space. Other characters are interpreted
-by the compiler proper, or reserved for future versions of \s-1GCC,\s0 and so
+by the compiler proper, or reserved for future versions of \s-1GCC\s0, and so
are silently ignored. If you specify characters whose behavior
conflicts, the result is undefined.
.RS 4
@@ -10891,12 +10891,12 @@ The \fB\-CC\fR option is generally used to support lint comments.
.IP "\fB\-traditional\-cpp\fR" 4
.IX Item "-traditional-cpp"
Try to imitate the behavior of old-fashioned C preprocessors, as
-opposed to \s-1ISO C\s0 preprocessors.
+opposed to \s-1ISO\s0 C preprocessors.
.IP "\fB\-trigraphs\fR" 4
.IX Item "-trigraphs"
Process trigraph sequences.
These are three-character sequences, all starting with \fB??\fR, that
-are defined by \s-1ISO C\s0 to stand for single characters. For example,
+are defined by \s-1ISO\s0 C to stand for single characters. For example,
\&\fB??/\fR stands for \fB\e\fR, so \fB'??/n'\fR is a character
constant for a newline. By default, \s-1GCC\s0 ignores trigraphs, but in
standard-conforming modes it converts them. See the \fB\-std\fR and
@@ -10922,7 +10922,7 @@ Print text describing all the command-line options instead of
preprocessing anything.
.IP "\fB\-v\fR" 4
.IX Item "-v"
-Verbose mode. Print out \s-1GNU CPP\s0's version number at the beginning of
+Verbose mode. Print out \s-1GNU\s0 \s-1CPP\s0's version number at the beginning of
execution, and report the final form of the include path.
.IP "\fB\-H\fR" 4
.IX Item "-H"
@@ -10937,9 +10937,9 @@ header file is printed with \fB...x\fR and a valid one with \fB...!\fR .
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
.PD
-Print out \s-1GNU CPP\s0's version number. With one dash, proceed to
+Print out \s-1GNU\s0 \s-1CPP\s0's version number. With one dash, proceed to
preprocess as normal. With two dashes, exit immediately.
-.SS "Passing Options to the Assembler"
+.Sh "Passing Options to the Assembler"
.IX Subsection "Passing Options to the Assembler"
You can pass options to the assembler.
.IP "\fB\-Wa,\fR\fIoption\fR" 4
@@ -10954,7 +10954,7 @@ recognize.
.Sp
If you want to pass an option that takes an argument, you must use
\&\fB\-Xassembler\fR twice, once for the option and once for the argument.
-.SS "Options for Linking"
+.Sh "Options for Linking"
.IX Subsection "Options for Linking"
These options come into play when the compiler links object files into
an executable output file. They are meaningless if the compiler is
@@ -11241,7 +11241,7 @@ different symbols to force loading of additional library modules.
\&\fB\-z\fR is passed directly on to the linker along with the keyword
\&\fIkeyword\fR. See the section in the documentation of your linker for
permitted values and their meanings.
-.SS "Options for Directory Search"
+.Sh "Options for Directory Search"
.IX Subsection "Options for Directory Search"
These options specify directories to search for header files, for
libraries and for parts of the compiler:
@@ -11377,13 +11377,13 @@ by default, but it is often satisfactory.
\&\fB\-I\-\fR does not inhibit the use of the standard system directories
for header files. Thus, \fB\-I\-\fR and \fB\-nostdinc\fR are
independent.
-.SS "Specifying Target Machine and Compiler Version"
+.Sh "Specifying Target Machine and Compiler Version"
.IX Subsection "Specifying Target Machine and Compiler Version"
The usual way to run \s-1GCC\s0 is to run the executable called \fBgcc\fR, or
\&\fImachine\fR\fB\-gcc\fR when cross-compiling, or
\&\fImachine\fR\fB\-gcc\-\fR\fIversion\fR to run a version other than the
one that was installed last.
-.SS "Hardware Models and Configurations"
+.Sh "Hardware Models and Configurations"
.IX Subsection "Hardware Models and Configurations"
Each target machine types can have its own
special options, starting with \fB\-m\fR, to choose among various
@@ -11409,7 +11409,7 @@ but long int and pointer are 64\-bit.
.Sp
The default depends on the specific target configuration. Note that
the \s-1LP64\s0 and \s-1ILP32\s0 ABIs are not link-compatible; you must compile your
-entire program with the same \s-1ABI,\s0 and link with a compatible set of libraries.
+entire program with the same \s-1ABI\s0, and link with a compatible set of libraries.
.IP "\fB\-mbig\-endian\fR" 4
.IX Item "-mbig-endian"
Generate big-endian code. This is the default when \s-1GCC\s0 is configured for an
@@ -11465,6 +11465,15 @@ of \s-1TLS\s0 variables.
Enable or disable the workaround for the \s-1ARM\s0 Cortex\-A53 erratum number 835769.
This involves inserting a \s-1NOP\s0 instruction between memory instructions and
64\-bit integer multiply-accumulate instructions.
+.IP "\fB\-mfix\-cortex\-a53\-843419\fR" 4
+.IX Item "-mfix-cortex-a53-843419"
+.PD 0
+.IP "\fB\-mno\-fix\-cortex\-a53\-843419\fR" 4
+.IX Item "-mno-fix-cortex-a53-843419"
+.PD
+Enable or disable the workaround for the \s-1ARM\s0 Cortex\-A53 erratum number 843419.
+This erratum workaround is made at link time and this will only pass the
+corresponding flag to the linker.
.IP "\fB\-march=\fR\fIname\fR" 4
.IX Item "-march=name"
Specify the name of the target architecture, optionally suffixed by one or
@@ -11636,7 +11645,7 @@ This is the mode used for floating-point calculations with
round-to-nearest-or-even rounding mode.
.IP "\fBint\fR" 4
.IX Item "int"
-This is the mode used to perform integer calculations in the \s-1FPU,\s0 e.g.
+This is the mode used to perform integer calculations in the \s-1FPU\s0, e.g.
integer multiply, or integer multiply-and-accumulate.
.RE
.RS 4
@@ -11698,13 +11707,13 @@ values for \fIcpu\fR are
.RS 4
.IP "\fB\s-1ARC600\s0\fR" 4
.IX Item "ARC600"
-Compile for \s-1ARC600. \s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR.
+Compile for \s-1ARC600\s0. Aliases: \fB\-mA6\fR, \fB\-mARC600\fR.
.IP "\fB\s-1ARC601\s0\fR" 4
.IX Item "ARC601"
-Compile for \s-1ARC601. \s0 Alias: \fB\-mARC601\fR.
+Compile for \s-1ARC601\s0. Alias: \fB\-mARC601\fR.
.IP "\fB\s-1ARC700\s0\fR" 4
.IX Item "ARC700"
-Compile for \s-1ARC700. \s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR.
+Compile for \s-1ARC700\s0. Aliases: \fB\-mA7\fR, \fB\-mARC700\fR.
This is the default when configured with \fB\-\-with\-cpu=arc700\fR.
.RE
.RS 4
@@ -11731,7 +11740,7 @@ Generate Extended arithmetic instructions. Currently only
supported. This is always enabled for \fB\-mcpu=ARC700\fR.
.IP "\fB\-mno\-mpy\fR" 4
.IX Item "-mno-mpy"
-Do not generate mpy instructions for \s-1ARC700.\s0
+Do not generate mpy instructions for \s-1ARC700\s0.
.IP "\fB\-mmul32x16\fR" 4
.IX Item "-mmul32x16"
Generate 32x16 bit multiply and mac instructions.
@@ -11756,7 +11765,7 @@ implementation.
implementation.
.IP "\fB\-msimd\fR" 4
.IX Item "-msimd"
-Enable generation of \s-1ARC SIMD\s0 instructions via target-specific
+Enable generation of \s-1ARC\s0 \s-1SIMD\s0 instructions via target-specific
builtins. Only valid for \fB\-mcpu=ARC700\fR.
.IP "\fB\-msoft\-float\fR" 4
.IX Item "-msoft-float"
@@ -11923,7 +11932,7 @@ optimizers then assume that indexed stores exist, which is not
the case.
.IP "\fB\-mlra\fR" 4
.IX Item "-mlra"
-Enable Local Register Allocation. This is still experimental for \s-1ARC,\s0
+Enable Local Register Allocation. This is still experimental for \s-1ARC\s0,
so by default the compiler uses standard reload
(i.e. \fB\-mno\-lra\fR).
.IP "\fB\-mlra\-priority\-none\fR" 4
@@ -12029,7 +12038,7 @@ The following options are maintained for backward compatibility, but
are now deprecated and will be removed in a future release:
.IP "\fB\-margonaut\fR" 4
.IX Item "-margonaut"
-Obsolete \s-1FPX.\s0
+Obsolete \s-1FPX\s0.
.IP "\fB\-mbig\-endian\fR" 4
.IX Item "-mbig-endian"
.PD 0
@@ -12092,7 +12101,7 @@ Replaced by \fB\-mmultcost\fR.
These \fB\-m\fR options are defined for the \s-1ARM\s0 port:
.IP "\fB\-mabi=\fR\fIname\fR" 4
.IX Item "-mabi=name"
-Generate code for the specified \s-1ABI. \s0 Permissible values are: \fBapcs-gnu\fR,
+Generate code for the specified \s-1ABI\s0. Permissible values are: \fBapcs-gnu\fR,
\&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR.
.IP "\fB\-mapcs\-frame\fR" 4
.IX Item "-mapcs-frame"
@@ -12136,7 +12145,7 @@ and uses FPU-specific calling conventions.
.Sp
The default depends on the specific target configuration. Note that
the hard-float and soft-float ABIs are not link-compatible; you must
-compile your entire program with the same \s-1ABI,\s0 and link with a
+compile your entire program with the same \s-1ABI\s0, and link with a
compatible set of libraries.
.IP "\fB\-mlittle\-endian\fR" 4
.IX Item "-mlittle-endian"
@@ -12266,7 +12275,7 @@ If the selected floating-point hardware includes the \s-1NEON\s0 extension
(e.g. \fB\-mfpu\fR=\fBneon\fR), note that floating-point
operations are not generated by \s-1GCC\s0's auto-vectorization pass unless
\&\fB\-funsafe\-math\-optimizations\fR is also specified. This is
-because \s-1NEON\s0 hardware does not fully implement the \s-1IEEE 754\s0 standard for
+because \s-1NEON\s0 hardware does not fully implement the \s-1IEEE\s0 754 standard for
floating-point arithmetic (in particular denormal values are treated as
zero), so the use of \s-1NEON\s0 instructions may lead to a loss of precision.
.IP "\fB\-mfp16\-format=\fR\fIname\fR" 4
@@ -12339,7 +12348,7 @@ otherwise the default is \fBR10\fR.
.IX Item "-mpic-data-is-text-relative"
Assume that each data segments are relative to text segment at load time.
Therefore, it permits addressing data using PC-relative operations.
-This option is on by default for targets other than VxWorks \s-1RTP.\s0
+This option is on by default for targets other than VxWorks \s-1RTP\s0.
.IP "\fB\-mpoke\-function\-name\fR" 4
.IX Item "-mpoke-function-name"
Write the name of each function into the text section, directly
@@ -12463,7 +12472,7 @@ off by default.
Assume inline assembler is using unified asm syntax. The default is
currently off which implies divided syntax. Currently this option is
available only for Thumb1 and has no effect on \s-1ARM\s0 state and Thumb2.
-However, this may change in future releases of \s-1GCC. \s0 Divided syntax
+However, this may change in future releases of \s-1GCC\s0. Divided syntax
should be considered deprecated.
.IP "\fB\-mrestrict\-it\fR" 4
.IX Item "-mrestrict-it"
@@ -12532,37 +12541,37 @@ The default for this option is@tie{}\fBavr2\fR.
.ie n .IP """avr6""" 4
.el .IP "\f(CWavr6\fR" 4
.IX Item "avr6"
-\&\*(L"Enhanced\*(R" devices with 3\-byte \s-1PC,\s0 i.e. with more than 128@tie{}KiB of program memory.
+\&\*(L"Enhanced\*(R" devices with 3\-byte \s-1PC\s0, i.e. with more than 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atmega256rfr2\*(C'\fR, \f(CW\*(C`atmega2560\*(C'\fR, \f(CW\*(C`atmega2561\*(C'\fR, \f(CW\*(C`atmega2564rfr2\*(C'\fR.
.ie n .IP """avrxmega2""" 4
.el .IP "\f(CWavrxmega2\fR" 4
.IX Item "avrxmega2"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 8@tie{}KiB and up to 64@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 8@tie{}KiB and up to 64@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega16a4\*(C'\fR, \f(CW\*(C`atxmega16a4u\*(C'\fR, \f(CW\*(C`atxmega16c4\*(C'\fR, \f(CW\*(C`atxmega16d4\*(C'\fR, \f(CW\*(C`atxmega16e5\*(C'\fR, \f(CW\*(C`atxmega32a4\*(C'\fR, \f(CW\*(C`atxmega32a4u\*(C'\fR, \f(CW\*(C`atxmega32c3\*(C'\fR, \f(CW\*(C`atxmega32c4\*(C'\fR, \f(CW\*(C`atxmega32d3\*(C'\fR, \f(CW\*(C`atxmega32d4\*(C'\fR, \f(CW\*(C`atxmega32e5\*(C'\fR, \f(CW\*(C`atxmega8e5\*(C'\fR.
.ie n .IP """avrxmega4""" 4
.el .IP "\f(CWavrxmega4\fR" 4
.IX Item "avrxmega4"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a3\*(C'\fR, \f(CW\*(C`atxmega64a3u\*(C'\fR, \f(CW\*(C`atxmega64a4u\*(C'\fR, \f(CW\*(C`atxmega64b1\*(C'\fR, \f(CW\*(C`atxmega64b3\*(C'\fR, \f(CW\*(C`atxmega64c3\*(C'\fR, \f(CW\*(C`atxmega64d3\*(C'\fR, \f(CW\*(C`atxmega64d4\*(C'\fR.
.ie n .IP """avrxmega5""" 4
.el .IP "\f(CWavrxmega5\fR" 4
.IX Item "avrxmega5"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.
-\&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM\s0.
+\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR.
.ie n .IP """avrxmega6""" 4
.el .IP "\f(CWavrxmega6\fR" 4
.IX Item "avrxmega6"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a3\*(C'\fR, \f(CW\*(C`atxmega128a3u\*(C'\fR, \f(CW\*(C`atxmega128b1\*(C'\fR, \f(CW\*(C`atxmega128b3\*(C'\fR, \f(CW\*(C`atxmega128c3\*(C'\fR, \f(CW\*(C`atxmega128d3\*(C'\fR, \f(CW\*(C`atxmega128d4\*(C'\fR, \f(CW\*(C`atxmega192a3\*(C'\fR, \f(CW\*(C`atxmega192a3u\*(C'\fR, \f(CW\*(C`atxmega192c3\*(C'\fR, \f(CW\*(C`atxmega192d3\*(C'\fR, \f(CW\*(C`atxmega256a3\*(C'\fR, \f(CW\*(C`atxmega256a3b\*(C'\fR, \f(CW\*(C`atxmega256a3bu\*(C'\fR, \f(CW\*(C`atxmega256a3u\*(C'\fR, \f(CW\*(C`atxmega256c3\*(C'\fR, \f(CW\*(C`atxmega256d3\*(C'\fR, \f(CW\*(C`atxmega384c3\*(C'\fR, \f(CW\*(C`atxmega384d3\*(C'\fR.
.ie n .IP """avrxmega7""" 4
.el .IP "\f(CWavrxmega7\fR" 4
.IX Item "avrxmega7"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.
-\&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM\s0.
+\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR.
.ie n .IP """avrtiny""" 4
.el .IP "\f(CWavrtiny\fR" 4
.IX Item "avrtiny"
-\&\*(L"\s-1TINY\*(R"\s0 Tiny core devices with 512@tie{}B up to 4@tie{}KiB of program memory.
+\&\*(L"\s-1TINY\s0\*(R" Tiny core devices with 512@tie{}B up to 4@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`attiny10\*(C'\fR, \f(CW\*(C`attiny20\*(C'\fR, \f(CW\*(C`attiny4\*(C'\fR, \f(CW\*(C`attiny40\*(C'\fR, \f(CW\*(C`attiny5\*(C'\fR, \f(CW\*(C`attiny9\*(C'\fR.
.ie n .IP """avr1""" 4
.el .IP "\f(CWavr1\fR" 4
@@ -12778,7 +12787,7 @@ command-line option.
.IX Item "-<Switch/case dispatch tables. If you do not want such dispatch>"
tables you can specify the \fB\-fno\-jump\-tables\fR command-line option.
.IP "\-<C and \*(C+ constructors/destructors called during startup/shutdown.>" 4
-.IX Item "-<C and constructors/destructors called during startup/shutdown.>"
+.IX Item "-<C and constructors/destructors called during startup/shutdown.>"
.PD 0
.ie n .IP "\-<If the tools hit a ""gs()"" modifier explained above.>" 4
.el .IP "\-<If the tools hit a \f(CWgs()\fR modifier explained above.>" 4
@@ -12973,7 +12982,7 @@ The definition of these macros is affected by \fB\-mtiny\-stack\fR.
.el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4
.IX Item "__AVR_SP8__"
.PD
-The device has the \s-1SPH \s0(high part of stack pointer) special function
+The device has the \s-1SPH\s0 (high part of stack pointer) special function
register or has an 8\-bit stack pointer, respectively.
The definition of these macros is affected by \fB\-mmcu=\fR and
in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also
@@ -13006,7 +13015,7 @@ This macro reflects the \fB\-mno\-interrupts\fR command-line option.
.el .IP "\f(CW_\|_AVR_ERRATA_SKIP_JMP_CALL_\|_\fR" 4
.IX Item "__AVR_ERRATA_SKIP_JMP_CALL__"
.PD
-Some \s-1AVR\s0 devices (\s-1AT90S8515,\s0 ATmega103) must not skip 32\-bit
+Some \s-1AVR\s0 devices (\s-1AT90S8515\s0, ATmega103) must not skip 32\-bit
instructions because of a hardware erratum. Skip instructions are
\&\f(CW\*(C`SBRS\*(C'\fR, \f(CW\*(C`SBRC\*(C'\fR, \f(CW\*(C`SBIS\*(C'\fR, \f(CW\*(C`SBIC\*(C'\fR and \f(CW\*(C`CPSE\*(C'\fR.
The second macro is only defined if \f(CW\*(C`_\|_AVR_HAVE_JMP_CALL_\|_\*(C'\fR is also
@@ -13014,7 +13023,7 @@ set.
.ie n .IP """_\|_AVR_ISA_RMW_\|_""" 4
.el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4
.IX Item "__AVR_ISA_RMW__"
-The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0).
+The device has Read-Modify-Write instructions (\s-1XCH\s0, \s-1LAC\s0, \s-1LAS\s0 and \s-1LAT\s0).
.ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW""" 4
.el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4
.IX Item "__AVR_SFR_OFFSET__=offset"
@@ -13198,8 +13207,8 @@ should be used instead of \f(CW\*(C`main\*(C'\fR.
This option can only be used in conjunction with \fB\-mmulticore\fR.
.IP "\fB\-msdram\fR" 4
.IX Item "-msdram"
-Build a standalone application for \s-1SDRAM.\s0 Proper start files and
-link scripts are used to put the application into \s-1SDRAM,\s0 and the macro
+Build a standalone application for \s-1SDRAM\s0. Proper start files and
+link scripts are used to put the application into \s-1SDRAM\s0, and the macro
\&\f(CW\*(C`_\|_BFIN_SDRAM\*(C'\fR is defined.
The loader should initialize \s-1SDRAM\s0 before loading the application.
.IP "\fB\-micplb\fR" 4
@@ -13258,7 +13267,7 @@ These options are defined specifically for the \s-1CRIS\s0 ports.
.PD
Generate code for the specified architecture. The choices for
\&\fIarchitecture-type\fR are \fBv3\fR, \fBv8\fR and \fBv10\fR for
-respectively \s-1ETRAX\s0\ 4, \s-1ETRAX\s0\ 100, and \s-1ETRAX\s0\ 100\ \s-1LX.\s0
+respectively \s-1ETRAX\s0\ 4, \s-1ETRAX\s0\ 100, and \s-1ETRAX\s0\ 100\ \s-1LX\s0.
Default is \fBv0\fR except for cris-axis-linux-gnu, where the default is
\&\fBv10\fR.
.IP "\fB\-mtune=\fR\fIarchitecture-type\fR" 4
@@ -13351,7 +13360,7 @@ or storage for local variables needs to be allocated.
With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate)
instruction sequences that load addresses for functions from the \s-1PLT\s0 part
of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the
-\&\s-1PLT. \s0 The default is \fB\-mgotplt\fR.
+\&\s-1PLT\s0. The default is \fB\-mgotplt\fR.
.IP "\fB\-melf\fR" 4
.IX Item "-melf"
Legacy no-op option only recognized with the cris-axis-elf and
@@ -13407,7 +13416,7 @@ However, \fBfar\fR is not valid with \fB\-mcr16c\fR, as the
These options are defined for all architectures running the Darwin operating
system.
.PP
-\&\s-1FSF GCC\s0 on Darwin does not create \*(L"fat\*(R" object files; it creates
+\&\s-1FSF\s0 \s-1GCC\s0 on Darwin does not create \*(L"fat\*(R" object files; it creates
an object file for the single architecture that \s-1GCC\s0 was built to
target. Apple's \s-1GCC\s0 on Darwin does create \*(L"fat\*(R" files if multiple
\&\fB\-arch\fR options are used; it does so by running the compiler or
@@ -13467,7 +13476,7 @@ warn about constructs contained within header files found via
.IX Item "-gused"
Emit debugging information for symbols that are used. For stabs
debugging format, this enables \fB\-feliminate\-unused\-debug\-symbols\fR.
-This is by default \s-1ON.\s0
+This is by default \s-1ON\s0.
.IP "\fB\-gfull\fR" 4
.IX Item "-gfull"
Emit debugging information for all symbols and types.
@@ -13543,7 +13552,7 @@ an executable when linking, using the Darwin \fIlibtool\fR command.
This causes \s-1GCC\s0's output file to have the \fB\s-1ALL\s0\fR subtype, instead of
one controlled by the \fB\-mcpu\fR or \fB\-march\fR option.
.IP "\fB\-allowable_client\fR \fIclient_name\fR" 4
-.IX Item "-allowable_client client_name"
+.IX Item "-allowable_client client_name"
.PD 0
.IP "\fB\-client_name\fR" 4
.IX Item "-client_name"
@@ -13717,7 +13726,7 @@ compilers call this option \fB\-ieee_with_no_inexact\fR.
.IP "\fB\-mieee\-with\-inexact\fR" 4
.IX Item "-mieee-with-inexact"
This is like \fB\-mieee\fR except the generated code also maintains
-the \s-1IEEE \s0\fIinexact-flag\fR. Turning on this option causes the
+the \s-1IEEE\s0 \fIinexact-flag\fR. Turning on this option causes the
generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to
\&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor
macro. On some Alpha implementations the resulting code may execute
@@ -13843,8 +13852,8 @@ before it can find the variables and constants in its own data segment.
.IP "\fB\-mno\-max\fR" 4
.IX Item "-mno-max"
.PD
-Indicate whether \s-1GCC\s0 should generate code to use the optional \s-1BWX,
-CIX, FIX\s0 and \s-1MAX\s0 instruction sets. The default is to use the instruction
+Indicate whether \s-1GCC\s0 should generate code to use the optional \s-1BWX\s0,
+\&\s-1CIX\s0, \s-1FIX\s0 and \s-1MAX\s0 instruction sets. The default is to use the instruction
sets supported by the \s-1CPU\s0 type specified via \fB\-mcpu=\fR option or that
of the \s-1CPU\s0 on which \s-1GCC\s0 was built if none is specified.
.IP "\fB\-mfloat\-vax\fR" 4
@@ -13853,7 +13862,7 @@ of the \s-1CPU\s0 on which \s-1GCC\s0 was built if none is specified.
.IP "\fB\-mfloat\-ieee\fR" 4
.IX Item "-mfloat-ieee"
.PD
-Generate code that uses (does not use) \s-1VAX F\s0 and G floating-point
+Generate code that uses (does not use) \s-1VAX\s0 F and G floating-point
arithmetic instead of \s-1IEEE\s0 single and double precision.
.IP "\fB\-mexplicit\-relocs\fR" 4
.IX Item "-mexplicit-relocs"
@@ -13908,7 +13917,7 @@ The default is \fB\-mlarge\-text\fR.
Set the instruction set and instruction scheduling parameters for
machine type \fIcpu_type\fR. You can specify either the \fB\s-1EV\s0\fR
style name or the corresponding chip number. \s-1GCC\s0 supports scheduling
-parameters for the \s-1EV4, EV5\s0 and \s-1EV6\s0 family of processors and
+parameters for the \s-1EV4\s0, \s-1EV5\s0 and \s-1EV6\s0 family of processors and
chooses the default values for the instruction set from the processor
you specify. If you do not specify a processor type, \s-1GCC\s0 defaults
to the processor on which the compiler was built.
@@ -13953,14 +13962,14 @@ Schedules as an \s-1EV5\s0 and supports the \s-1BWX\s0 and \s-1MAX\s0 extensions
.IP "\fB21264\fR" 4
.IX Item "21264"
.PD
-Schedules as an \s-1EV6\s0 and supports the \s-1BWX, FIX,\s0 and \s-1MAX\s0 extensions.
+Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions.
.IP "\fBev67\fR" 4
.IX Item "ev67"
.PD 0
.IP "\fB21264a\fR" 4
.IX Item "21264a"
.PD
-Schedules as an \s-1EV6\s0 and supports the \s-1BWX, CIX, FIX,\s0 and \s-1MAX\s0 extensions.
+Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1CIX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions.
.RE
.RS 4
.Sp
@@ -14001,9 +14010,9 @@ A decimal number representing clock cycles.
.IX Item "main"
.PD
The compiler contains estimates of the number of clock cycles for
-\&\*(L"typical\*(R" \s-1EV4 & EV5\s0 hardware for the Level 1, 2 & 3 caches
+\&\*(L"typical\*(R" \s-1EV4\s0 & \s-1EV5\s0 hardware for the Level 1, 2 & 3 caches
(also called Dcache, Scache, and Bcache), as well as to main memory.
-Note that L3 is only valid for \s-1EV5.\s0
+Note that L3 is only valid for \s-1EV5\s0.
.RE
.RS 4
.RE
@@ -14076,7 +14085,7 @@ Use multiply and add/subtract instructions.
Do not use multiply and add/subtract instructions.
.IP "\fB\-mfdpic\fR" 4
.IX Item "-mfdpic"
-Select the \s-1FDPIC ABI,\s0 which uses function descriptors to represent
+Select the \s-1FDPIC\s0 \s-1ABI\s0, which uses function descriptors to represent
pointers to functions. Without any PIC/PIE\-related options, it
implies \fB\-fPIE\fR. With \fB\-fpic\fR or \fB\-fpie\fR, it
assumes \s-1GOT\s0 entries and small data are within a 12\-bit range from the
@@ -14099,7 +14108,7 @@ Assume a large \s-1TLS\s0 segment when generating thread-local code.
Do not assume a large \s-1TLS\s0 segment when generating thread-local code.
.IP "\fB\-mgprel\-ro\fR" 4
.IX Item "-mgprel-ro"
-Enable the use of \f(CW\*(C`GPREL\*(C'\fR relocations in the \s-1FDPIC ABI\s0 for data
+Enable the use of \f(CW\*(C`GPREL\*(C'\fR relocations in the \s-1FDPIC\s0 \s-1ABI\s0 for data
that is known to be in read-only sections. It's enabled by default,
except for \fB\-fpic\fR or \fB\-fpie\fR: even though it may help
make the global offset table smaller, it trades 1 instruction for 4.
@@ -14243,7 +14252,7 @@ Select the processor type for which to generate code. Possible values are
These \fB\-m\fR options are defined for GNU/Linux targets:
.IP "\fB\-mglibc\fR" 4
.IX Item "-mglibc"
-Use the \s-1GNU C\s0 library. This is the default except
+Use the \s-1GNU\s0 C library. This is the default except
on \fB*\-*\-linux\-*uclibc*\fR and \fB*\-*\-linux\-*android*\fR targets.
.IP "\fB\-muclibc\fR" 4
.IX Item "-muclibc"
@@ -14322,8 +14331,8 @@ These \fB\-m\fR options are defined for the \s-1HPPA\s0 family of computers:
.IP "\fB\-march=\fR\fIarchitecture-type\fR" 4
.IX Item "-march=architecture-type"
Generate code for the specified architecture. The choices for
-\&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0, \s0\fB1.1\fR for \s-1PA
-1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to
+\&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA\s0 1.0, \fB1.1\fR for \s-1PA\s0
+1.1, and \fB2.0\fR for \s-1PA\s0 2.0 processors. Refer to
\&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper
architecture option for your machine. Code compiled for lower numbered
architectures runs on higher numbered architectures, but not the
@@ -14349,7 +14358,7 @@ floating-point operations, the compiler aborts.
.IP "\fB\-mdisable\-indexing\fR" 4
.IX Item "-mdisable-indexing"
Prevent the compiler from using indexing address modes. This avoids some
-rather obscure problems when compiling \s-1MIG\s0 generated code under \s-1MACH.\s0
+rather obscure problems when compiling \s-1MIG\s0 generated code under \s-1MACH\s0.
.IP "\fB\-mno\-space\-regs\fR" 4
.IX Item "-mno-space-regs"
Generate code that assumes the target has no space registers. This allows
@@ -14406,17 +14415,17 @@ cross-compilation.
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-msio\fR" 4
.IX Item "-msio"
-Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO. \s0 The default is
+Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO\s0. The default is
\&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR,
-\&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO. \s0 These
+\&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO\s0. These
options are available under HP-UX and HI-UX.
.IP "\fB\-mgnu\-ld\fR" 4
.IX Item "-mgnu-ld"
-Use options specific to \s-1GNU \s0\fBld\fR.
+Use options specific to \s-1GNU\s0 \fBld\fR.
This passes \fB\-shared\fR to \fBld\fR when
building a shared library. It is the default when \s-1GCC\s0 is configured,
explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not
@@ -14426,10 +14435,10 @@ The \fBld\fR that is called is determined by the
\&\fB\-\-with\-ld\fR configure option, \s-1GCC\s0's program search path, and
finally by the user's \fB\s-1PATH\s0\fR. The linker used by \s-1GCC\s0 can be printed
using \fBwhich `gcc \-print\-prog\-name=ld`\fR. This option is only available
-on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
+on the 64\-bit HP-UX \s-1GCC\s0, i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
.IP "\fB\-mhp\-ld\fR" 4
.IX Item "-mhp-ld"
-Use options specific to \s-1HP \s0\fBld\fR.
+Use options specific to \s-1HP\s0 \fBld\fR.
This passes \fB\-b\fR to \fBld\fR when building
a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all
links. It is the default when \s-1GCC\s0 is configured, explicitly or
@@ -14440,7 +14449,7 @@ The \fBld\fR that is called is determined by the \fB\-\-with\-ld\fR
configure option, \s-1GCC\s0's program search path, and finally by the user's
\&\fB\s-1PATH\s0\fR. The linker used by \s-1GCC\s0 can be printed using \fBwhich
`gcc \-print\-prog\-name=ld`\fR. This option is only available on the 64\-bit
-HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
+HP-UX \s-1GCC\s0, i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
.IP "\fB\-mlong\-calls\fR" 4
.IX Item "-mlong-calls"
Generate code that uses long call sequences. This ensures that a call
@@ -14449,7 +14458,7 @@ long calls only when the distance from the call site to the beginning
of the function or translation unit, as the case may be, exceeds a
predefined limit set by the branch type being used. The limits for
normal calls are 7,600,000 and 240,000 bytes, respectively for the
-\&\s-1PA 2.0\s0 and \s-1PA 1.X\s0 architectures. Sibcalls are always limited at
+\&\s-1PA\s0 2.0 and \s-1PA\s0 1.X architectures. Sibcalls are always limited at
240,000 bytes.
.Sp
Distances are measured from the beginning of functions when using the
@@ -14477,7 +14486,7 @@ is available on HP-UX 10.10 and later. \fB98\fR is available on HP-UX
\&\fB95\fR for HP-UX 10.10 though to 11.00, and \fB98\fR for HP-UX 11.11
and later.
.Sp
-\&\fB\-munix=93\fR provides the same predefines as \s-1GCC 3.3\s0 and 3.4.
+\&\fB\-munix=93\fR provides the same predefines as \s-1GCC\s0 3.3 and 3.4.
\&\fB\-munix=95\fR provides additional predefines for \f(CW\*(C`XOPEN_UNIX\*(C'\fR
and \f(CW\*(C`_XOPEN_SOURCE_EXTENDED\*(C'\fR, and the startfile \fIunix95.o\fR.
\&\fB\-munix=98\fR provides additional predefines for \f(CW\*(C`_XOPEN_UNIX\*(C'\fR,
@@ -14543,7 +14552,7 @@ Generate (or don't) code for the \s-1GNU\s0 linker. This is the default.
.IP "\fB\-mno\-pic\fR" 4
.IX Item "-mno-pic"
Generate code that does not use a global pointer register. The result
-is not position independent code, and violates the \s-1IA\-64 ABI.\s0
+is not position independent code, and violates the \s-1IA\-64\s0 \s-1ABI\s0.
.IP "\fB\-mvolatile\-asm\-stop\fR" 4
.IX Item "-mvolatile-asm-stop"
.PD 0
@@ -14623,7 +14632,7 @@ instructions. The default is to use these instructions.
.IP "\fB\-mdwarf2\-asm\fR" 4
.IX Item "-mdwarf2-asm"
.PD
-Don't (or do) generate assembler code for the \s-1DWARF 2\s0 line number debugging
+Don't (or do) generate assembler code for the \s-1DWARF\s0 2 line number debugging
info. This may be useful when not using the \s-1GNU\s0 assembler.
.IP "\fB\-mearly\-stop\-bits\fR" 4
.IX Item "-mearly-stop-bits"
@@ -14647,7 +14656,7 @@ Specify bit size of immediate \s-1TLS\s0 offsets. Valid values are 14, 22, and
64.
.IP "\fB\-mtune=\fR\fIcpu-type\fR" 4
.IX Item "-mtune=cpu-type"
-Tune the instruction scheduling for a particular \s-1CPU,\s0 Valid values are
+Tune the instruction scheduling for a particular \s-1CPU\s0, Valid values are
\&\fBitanium\fR, \fBitanium1\fR, \fBmerced\fR, \fBitanium2\fR,
and \fBmckinley\fR.
.IP "\fB\-milp32\fR" 4
@@ -15096,7 +15105,7 @@ have to be emulated by software on the 68060. Use this option if your 68060
does not have code to emulate those instructions.
.IP "\fB\-mcpu32\fR" 4
.IX Item "-mcpu32"
-Generate output for a \s-1CPU32. \s0 This is the default
+Generate output for a \s-1CPU32\s0. This is the default
when the compiler is configured for CPU32\-based systems.
It is equivalent to \fB\-march=cpu32\fR.
.Sp
@@ -15105,16 +15114,16 @@ Use this option for microcontrollers with a
68336, 68340, 68341, 68349 and 68360.
.IP "\fB\-m5200\fR" 4
.IX Item "-m5200"
-Generate output for a 520X ColdFire \s-1CPU. \s0 This is the default
+Generate output for a 520X ColdFire \s-1CPU\s0. This is the default
when the compiler is configured for 520X\-based systems.
It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated
in favor of that option.
.Sp
Use this option for microcontroller with a 5200 core, including
-the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0
+the \s-1MCF5202\s0, \s-1MCF5203\s0, \s-1MCF5204\s0 and \s-1MCF5206\s0.
.IP "\fB\-m5206e\fR" 4
.IX Item "-m5206e"
-Generate output for a 5206e ColdFire \s-1CPU. \s0 The option is now
+Generate output for a 5206e ColdFire \s-1CPU\s0. The option is now
deprecated in favor of the equivalent \fB\-mcpu=5206e\fR.
.IP "\fB\-m528x\fR" 4
.IX Item "-m528x"
@@ -15123,15 +15132,15 @@ The option is now deprecated in favor of the equivalent
\&\fB\-mcpu=528x\fR.
.IP "\fB\-m5307\fR" 4
.IX Item "-m5307"
-Generate output for a ColdFire 5307 \s-1CPU. \s0 The option is now deprecated
+Generate output for a ColdFire 5307 \s-1CPU\s0. The option is now deprecated
in favor of the equivalent \fB\-mcpu=5307\fR.
.IP "\fB\-m5407\fR" 4
.IX Item "-m5407"
-Generate output for a ColdFire 5407 \s-1CPU. \s0 The option is now deprecated
+Generate output for a ColdFire 5407 \s-1CPU\s0. The option is now deprecated
in favor of the equivalent \fB\-mcpu=5407\fR.
.IP "\fB\-mcfv4e\fR" 4
.IX Item "-mcfv4e"
-Generate output for a ColdFire V4e family \s-1CPU \s0(e.g. 547x/548x).
+Generate output for a ColdFire V4e family \s-1CPU\s0 (e.g. 547x/548x).
This includes use of hardware floating-point instructions.
The option is equivalent to \fB\-mcpu=547x\fR, and is now
deprecated in favor of that option.
@@ -15158,14 +15167,14 @@ The option is equivalent to \fB\-march=68020\fR \fB\-mtune=68020\-60\fR.
.IX Item "-m68881"
.PD
Generate floating-point instructions. This is the default for 68020
-and above, and for ColdFire devices that have an \s-1FPU. \s0 It defines the
+and above, and for ColdFire devices that have an \s-1FPU\s0. It defines the
macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR
on ColdFire targets.
.IP "\fB\-msoft\-float\fR" 4
.IX Item "-msoft-float"
Do not generate floating-point instructions; use library calls instead.
This is the default for 68000, 68010, and 68832 targets. It is also
-the default for ColdFire devices that have no \s-1FPU.\s0
+the default for ColdFire devices that have no \s-1FPU\s0.
.IP "\fB\-mdiv\fR" 4
.IX Item "-mdiv"
.PD 0
@@ -15175,8 +15184,8 @@ the default for ColdFire devices that have no \s-1FPU.\s0
Generate (do not generate) ColdFire hardware divide and remainder
instructions. If \fB\-march\fR is used without \fB\-mcpu\fR,
the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0
-architectures. Otherwise, the default is taken from the target \s-1CPU
-\&\s0(either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For
+architectures. Otherwise, the default is taken from the target \s-1CPU\s0
+(either the default \s-1CPU\s0, or the one specified by \fB\-mcpu\fR). For
example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for
\&\fB\-mcpu=5206e\fR.
.Sp
@@ -15295,7 +15304,7 @@ that works if the \s-1GOT\s0 has more than 8192 entries. This code is
larger and slower than code generated without this option. On M680x0
processors, this option is not needed; \fB\-fPIC\fR suffices.
.Sp
-\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT.\s0
+\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT\s0.
While this is relatively efficient, it only works if the \s-1GOT\s0
is smaller than about 64k. Anything larger causes the linker
to report an error such as:
@@ -15437,7 +15446,7 @@ useful unless you also provide \fB\-mminmax\fR.
Selects one of the built-in core configurations. Each MeP chip has
one or more modules in it; each module has a core \s-1CPU\s0 and a variety of
coprocessors, optional instructions, and peripherals. The
-\&\f(CW\*(C`MeP\-Integrator\*(C'\fR tool, not part of \s-1GCC,\s0 provides these
+\&\f(CW\*(C`MeP\-Integrator\*(C'\fR tool, not part of \s-1GCC\s0, provides these
configurations through this option; using this option is the same as
using all the corresponding command-line options. The default
configuration is \fBdefault\fR.
@@ -15540,7 +15549,7 @@ Do not optimize block moves, use \f(CW\*(C`memcpy\*(C'\fR.
This option is deprecated. Use \fB\-fno\-zero\-initialized\-in\-bss\fR instead.
.IP "\fB\-mcpu=\fR\fIcpu-type\fR" 4
.IX Item "-mcpu=cpu-type"
-Use features of, and schedule code for, the given \s-1CPU.\s0
+Use features of, and schedule code for, the given \s-1CPU\s0.
Supported values are in the format \fBv\fR\fIX\fR\fB.\fR\fI\s-1YY\s0\fR\fB.\fR\fIZ\fR,
where \fIX\fR is a major version, \fI\s-1YY\s0\fR is the minor version, and
\&\fIZ\fR is compatibility code. Example values are \fBv3.00.a\fR,
@@ -15626,7 +15635,7 @@ configurations.
.IP "\fB\-march=\fR\fIarch\fR" 4
.IX Item "-march=arch"
Generate code that runs on \fIarch\fR, which can be the name of a
-generic \s-1MIPS ISA,\s0 or the name of a particular processor.
+generic \s-1MIPS\s0 \s-1ISA\s0, or the name of a particular processor.
The \s-1ISA\s0 names are:
\&\fBmips1\fR, \fBmips2\fR, \fBmips3\fR, \fBmips4\fR,
\&\fBmips32\fR, \fBmips32r2\fR, \fBmips32r3\fR, \fBmips32r5\fR,
@@ -15658,7 +15667,7 @@ The processor names are:
\&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR,
\&\fBxlr\fR and \fBxlp\fR.
The special value \fBfrom-abi\fR selects the
-most compatible architecture for the selected \s-1ABI \s0(that is,
+most compatible architecture for the selected \s-1ABI\s0 (that is,
\&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs).
.Sp
The native Linux/GNU toolchain also supports the value \fBnative\fR,
@@ -15754,7 +15763,7 @@ Equivalent to \fB\-march=mips64r6\fR.
.IX Item "-mno-mips16"
.PD
Generate (do not generate) \s-1MIPS16\s0 code. If \s-1GCC\s0 is targeting a
-\&\s-1MIPS32\s0 or \s-1MIPS64\s0 architecture, it makes use of the MIPS16e \s-1ASE.\s0
+\&\s-1MIPS32\s0 or \s-1MIPS64\s0 architecture, it makes use of the MIPS16e \s-1ASE\s0.
.Sp
\&\s-1MIPS16\s0 code generation can also be controlled on a per-function basis
by means of \f(CW\*(C`mips16\*(C'\fR and \f(CW\*(C`nomips16\*(C'\fR attributes.
@@ -15769,7 +15778,7 @@ not intended for ordinary use in compiling user code.
.IP "\fB\-mno\-interlink\-compressed\fR" 4
.IX Item "-mno-interlink-compressed"
.PD
-Require (do not require) that code using the standard (uncompressed) \s-1MIPS ISA\s0
+Require (do not require) that code using the standard (uncompressed) \s-1MIPS\s0 \s-1ISA\s0
be link-compatible with \s-1MIPS16\s0 and microMIPS code, and vice versa.
.Sp
For example, code using the standard \s-1ISA\s0 encoding cannot jump directly
@@ -15797,20 +15806,20 @@ and are retained for backwards compatibility.
.IP "\fB\-mabi=eabi\fR" 4
.IX Item "-mabi=eabi"
.PD
-Generate code for the given \s-1ABI.\s0
+Generate code for the given \s-1ABI\s0.
.Sp
Note that the \s-1EABI\s0 has a 32\-bit and a 64\-bit variant. \s-1GCC\s0 normally
generates 64\-bit code when you select a 64\-bit architecture, but you
can use \fB\-mgp32\fR to get 32\-bit code instead.
.Sp
-For information about the O64 \s-1ABI,\s0 see
+For information about the O64 \s-1ABI\s0, see
<\fBhttp://gcc.gnu.org/projects/mipso64\-abi.html\fR>.
.Sp
\&\s-1GCC\s0 supports a variant of the o32 \s-1ABI\s0 in which floating-point registers
are 64 rather than 32 bits wide. You can select this combination with
\&\fB\-mabi=32\fR \fB\-mfp64\fR. This \s-1ABI\s0 relies on the \f(CW\*(C`mthc1\*(C'\fR
and \f(CW\*(C`mfhc1\*(C'\fR instructions and is therefore only supported for
-\&\s-1MIPS32R2, MIPS32R3\s0 and \s-1MIPS32R5\s0 processors.
+\&\s-1MIPS32R2\s0, \s-1MIPS32R3\s0 and \s-1MIPS32R5\s0 processors.
.Sp
The register assignments for arguments and return values remain the
same, but each scalar value is passed in a single 64\-bit register
@@ -15821,11 +15830,11 @@ remains the same in that the even-numbered double-precision registers
are saved.
.Sp
Two additional variants of the o32 \s-1ABI\s0 are supported to enable
-a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX
-\&\s0(\fB\-mfpxx\fR) and \s-1FP64A \s0(\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR).
+a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX\s0
+(\fB\-mfpxx\fR) and \s-1FP64A\s0 (\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR).
The \s-1FPXX\s0 extension mandates that all code must execute correctly
when run using 32\-bit or 64\-bit registers. The code can be interlinked
-with either \s-1FP32\s0 or \s-1FP64,\s0 but not both.
+with either \s-1FP32\s0 or \s-1FP64\s0, but not both.
The \s-1FP64A\s0 extension is similar to the \s-1FP64\s0 extension but forbids the
use of odd-numbered single-precision registers. This can be used
in conjunction with the \f(CW\*(C`FRE\*(C'\fR mode of FPUs in \s-1MIPS32R5\s0
@@ -15872,7 +15881,7 @@ executables both smaller and quicker.
.PD
Assume (do not assume) that the static and dynamic linkers
support PLTs and copy relocations. This option only affects
-\&\fB\-mno\-shared \-mabicalls\fR. For the n64 \s-1ABI,\s0 this option
+\&\fB\-mno\-shared \-mabicalls\fR. For the n64 \s-1ABI\s0, this option
has no effect without \fB\-msym32\fR.
.Sp
You can make \fB\-mplt\fR the default by configuring
@@ -15887,7 +15896,7 @@ You can make \fB\-mplt\fR the default by configuring
Lift (do not lift) the usual restrictions on the size of the global
offset table.
.Sp
-\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT.\s0
+\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT\s0.
While this is relatively efficient, it only works if the \s-1GOT\s0
is smaller than about 64k. Anything larger causes the linker
to report an error such as:
@@ -15955,8 +15964,8 @@ operations. This is the default.
.IX Item "-mno-odd-spreg"
.PD
Enable the use of odd-numbered single-precision floating-point registers
-for the o32 \s-1ABI. \s0 This is the default for processors that are known to
-support these registers. When using the o32 \s-1FPXX ABI, \s0\fB\-mno\-odd\-spreg\fR
+for the o32 \s-1ABI\s0. This is the default for processors that are known to
+support these registers. When using the o32 \s-1FPXX\s0 \s-1ABI\s0, \fB\-mno\-odd\-spreg\fR
is set by default.
.IP "\fB\-mabs=2008\fR" 4
.IX Item "-mabs=2008"
@@ -15965,7 +15974,7 @@ is set by default.
.IX Item "-mabs=legacy"
.PD
These options control the treatment of the special not-a-number (NaN)
-\&\s-1IEEE 754\s0 floating-point data with the \f(CW\*(C`abs.\f(CIfmt\f(CW\*(C'\fR and
+\&\s-1IEEE\s0 754 floating-point data with the \f(CW\*(C`abs.\f(CIfmt\f(CW\*(C'\fR and
\&\f(CW\*(C`neg.\f(CIfmt\f(CW\*(C'\fR machine instructions.
.Sp
By default or when \fB\-mabs=legacy\fR is used the legacy
@@ -15976,7 +15985,7 @@ manipulate the sign bit of floating-point datum manually is used
instead unless the \fB\-ffinite\-math\-only\fR option has also been
specified.
.Sp
-The \fB\-mabs=2008\fR option selects the \s-1IEEE 754\-2008\s0 treatment. In
+The \fB\-mabs=2008\fR option selects the \s-1IEEE\s0 754\-2008 treatment. In
this case these instructions are considered non-arithmetic and therefore
operating correctly in all cases, including in particular where the
input operand is a NaN. These instructions are therefore always used
@@ -15988,14 +15997,14 @@ for the respective operations.
.IX Item "-mnan=legacy"
.PD
These options control the encoding of the special not-a-number (NaN)
-\&\s-1IEEE 754\s0 floating-point data.
+\&\s-1IEEE\s0 754 floating-point data.
.Sp
The \fB\-mnan=legacy\fR option selects the legacy encoding. In this
case quiet NaNs (qNaNs) are denoted by the first bit of their trailing
significand field being 0, whereas signalling NaNs (sNaNs) are denoted
by the first bit of their trailing significand field being 1.
.Sp
-The \fB\-mnan=2008\fR option selects the \s-1IEEE 754\-2008\s0 encoding. In
+The \fB\-mnan=2008\fR option selects the \s-1IEEE\s0 754\-2008 encoding. In
this case qNaNs are denoted by the first bit of their trailing
significand field being 1, whereas sNaNs are denoted by the first bit of
their trailing significand field being 0.
@@ -16025,8 +16034,8 @@ configurations; see the installation documentation for details.
.IP "\fB\-mno\-dsp\fR" 4
.IX Item "-mno-dsp"
.PD
-Use (do not use) revision 1 of the \s-1MIPS DSP ASE.
- \s0 This option defines the
+Use (do not use) revision 1 of the \s-1MIPS\s0 \s-1DSP\s0 \s-1ASE\s0.
+ This option defines the
preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines
\&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1.
.IP "\fB\-mdspr2\fR" 4
@@ -16035,8 +16044,8 @@ preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines
.IP "\fB\-mno\-dspr2\fR" 4
.IX Item "-mno-dspr2"
.PD
-Use (do not use) revision 2 of the \s-1MIPS DSP ASE.
- \s0 This option defines the
+Use (do not use) revision 2 of the \s-1MIPS\s0 \s-1DSP\s0 \s-1ASE\s0.
+ This option defines the
preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR.
It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2.
.IP "\fB\-msmartmips\fR" 4
@@ -16045,7 +16054,7 @@ It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2.
.IP "\fB\-mno\-smartmips\fR" 4
.IX Item "-mno-smartmips"
.PD
-Use (do not use) the \s-1MIPS\s0 SmartMIPS \s-1ASE.\s0
+Use (do not use) the \s-1MIPS\s0 SmartMIPS \s-1ASE\s0.
.IP "\fB\-mpaired\-single\fR" 4
.IX Item "-mpaired-single"
.PD 0
@@ -16070,7 +16079,7 @@ hardware floating-point support to be enabled.
.IP "\fB\-mno\-mips3d\fR" 4
.IX Item "-mno-mips3d"
.PD
-Use (do not use) the \s-1MIPS\-3D ASE. \s0
+Use (do not use) the \s-1MIPS\-3D\s0 \s-1ASE\s0.
The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR.
.IP "\fB\-mmicromips\fR" 4
.IX Item "-mmicromips"
@@ -16095,7 +16104,7 @@ Use (do not use) \s-1MT\s0 Multithreading instructions.
.IP "\fB\-mno\-mcu\fR" 4
.IX Item "-mno-mcu"
.PD
-Use (do not use) the \s-1MIPS MCU ASE\s0 instructions.
+Use (do not use) the \s-1MIPS\s0 \s-1MCU\s0 \s-1ASE\s0 instructions.
.IP "\fB\-meva\fR" 4
.IX Item "-meva"
.PD 0
@@ -16127,7 +16136,7 @@ determined.
Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide.
.Sp
The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on
-the \s-1ABI. \s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0
+the \s-1ABI\s0. All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0
uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use
32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs,
or the same size as integer registers, whichever is smaller.
@@ -16138,7 +16147,7 @@ or the same size as integer registers, whichever is smaller.
.IX Item "-mno-sym32"
.PD
Assume (do not assume) that all symbols have 32\-bit values, regardless
-of the selected \s-1ABI. \s0 This option is useful in combination with
+of the selected \s-1ABI\s0. This option is useful in combination with
\&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0
to generate shorter and faster references to symbolic addresses.
.IP "\fB\-G\fR \fInum\fR" 4
@@ -16243,13 +16252,13 @@ but other instructions must not do so. This option is useful on 4KSc
and 4KSd processors when the code TLBs have the Read Inhibit bit set.
It is also useful on processors that can be configured to have a dual
instruction/data \s-1SRAM\s0 interface and that, like the M4K, automatically
-redirect PC-relative loads to the instruction \s-1RAM.\s0
+redirect PC-relative loads to the instruction \s-1RAM\s0.
.IP "\fB\-mcode\-readable=no\fR" 4
.IX Item "-mcode-readable=no"
Instructions must not access executable sections. This option can be
useful on targets that are configured to have a dual instruction/data
\&\s-1SRAM\s0 interface but that (unlike the M4K) do not automatically redirect
-PC-relative loads to the instruction \s-1RAM.\s0
+PC-relative loads to the instruction \s-1RAM\s0.
.RE
.RS 4
.RE
@@ -16291,7 +16300,7 @@ The default is \fB\-mcheck\-zero\-division\fR.
.PD
\&\s-1MIPS\s0 systems check for division by zero by generating either a
conditional trap or a break instruction. Using traps results in
-smaller code, but is only supported on \s-1MIPS II\s0 and later. Also, some
+smaller code, but is only supported on \s-1MIPS\s0 \s-1II\s0 and later. Also, some
versions of the Linux kernel have a bug that prevents trap from
generating the proper signal (\f(CW\*(C`SIGFPE\*(C'\fR). Use \fB\-mdivide\-traps\fR to
allow conditional traps on architectures that support them and
@@ -16329,7 +16338,7 @@ This option has no effect on abicalls code. The default is
.IX Item "-mno-mad"
.PD
Enable (disable) use of the \f(CW\*(C`mad\*(C'\fR, \f(CW\*(C`madu\*(C'\fR and \f(CW\*(C`mul\*(C'\fR
-instructions, as provided by the R4650 \s-1ISA.\s0
+instructions, as provided by the R4650 \s-1ISA\s0.
.IP "\fB\-mimadd\fR" 4
.IX Item "-mimadd"
.PD 0
@@ -16367,7 +16376,7 @@ assembler files (with a \fB.s\fR suffix) when assembling them.
.IX Item "-mno-fix-24k"
.PD
Work around the 24K E48 (lost data on stores during refill) errata.
-The workarounds are implemented by the assembler rather than by \s-1GCC.\s0
+The workarounds are implemented by the assembler rather than by \s-1GCC\s0.
.IP "\fB\-mfix\-r4000\fR" 4
.IX Item "-mfix-r4000"
.PD 0
@@ -16427,8 +16436,8 @@ otherwise.
.IP "\fB\-mno\-fix\-rm7000\fR" 4
.IX Item "-mno-fix-rm7000"
.PD
-Work around the \s-1RM7000 \s0\f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The
-workarounds are implemented by the assembler rather than by \s-1GCC.\s0
+Work around the \s-1RM7000\s0 \f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The
+workarounds are implemented by the assembler rather than by \s-1GCC\s0.
.IP "\fB\-mfix\-vr4120\fR" 4
.IX Item "-mfix-vr4120"
.PD 0
@@ -16454,10 +16463,10 @@ instructions. These errata are handled by the assembler, not by \s-1GCC\s0 itse
.RE
.IP "\fB\-mfix\-vr4130\fR" 4
.IX Item "-mfix-vr4130"
-Work around the \s-1VR4130 \s0\f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The
-workarounds are implemented by the assembler rather than by \s-1GCC,\s0
+Work around the \s-1VR4130\s0 \f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The
+workarounds are implemented by the assembler rather than by \s-1GCC\s0,
although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the
-\&\s-1VR4130 \s0\f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR
+\&\s-1VR4130\s0 \f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR
instructions are available instead.
.IP "\fB\-mfix\-sb1\fR" 4
.IX Item "-mfix-sb1"
@@ -16465,7 +16474,7 @@ instructions are available instead.
.IP "\fB\-mno\-fix\-sb1\fR" 4
.IX Item "-mno-fix-sb1"
.PD
-Work around certain \s-1SB\-1 CPU\s0 core errata.
+Work around certain \s-1SB\-1\s0 \s-1CPU\s0 core errata.
(This flag currently works around the \s-1SB\-1\s0 revision 2
\&\*(L"F1\*(R" and \*(L"F2\*(R" floating-point errata.)
.IP "\fB\-mr10k\-cache\-barrier=\fR\fIsetting\fR" 4
@@ -16579,7 +16588,7 @@ Specifies whether \s-1FP\s0 exceptions are enabled. This affects how
The default is that \s-1FP\s0 exceptions are
enabled.
.Sp
-For instance, on the \s-1SB\-1,\s0 if \s-1FP\s0 exceptions are disabled, and we are emitting
+For instance, on the \s-1SB\-1\s0, if \s-1FP\s0 exceptions are disabled, and we are emitting
64\-bit code, then we can use both \s-1FP\s0 pipes. Otherwise, we can only use one
\&\s-1FP\s0 pipe.
.IP "\fB\-mvr4130\-align\fR" 4
@@ -16593,7 +16602,7 @@ instructions together if the first one is 8\-byte aligned. When this
option is enabled, \s-1GCC\s0 aligns pairs of instructions that it
thinks should execute in parallel.
.Sp
-This option only has an effect when optimizing for the \s-1VR4130.\s0
+This option only has an effect when optimizing for the \s-1VR4130\s0.
It normally makes code faster, but at the expense of making it bigger.
It is enabled by default at optimization level \fB\-O3\fR.
.IP "\fB\-msynci\fR" 4
@@ -16682,7 +16691,7 @@ to the \f(CW\*(C`rE\*(C'\fR epsilon register.
.PD
Generate code that passes function parameters and return values that (in
the called function) are seen as registers \f(CW$0\fR and up, as opposed to
-the \s-1GNU ABI\s0 which uses global registers \f(CW$231\fR and up.
+the \s-1GNU\s0 \s-1ABI\s0 which uses global registers \f(CW$231\fR and up.
.IP "\fB\-mzero\-extend\fR" 4
.IX Item "-mzero-extend"
.PD 0
@@ -16766,7 +16775,7 @@ Do not generate code using features specific to the \s-1AM33\s0 processor. This
is the default.
.IP "\fB\-mam33\-2\fR" 4
.IX Item "-mam33-2"
-Generate code using features specific to the \s-1AM33/2.0\s0 processor.
+Generate code using features specific to the \s-1AM33/2\s0.0 processor.
.IP "\fB\-mam34\fR" 4
.IX Item "-mam34"
Generate code using features specific to the \s-1AM34\s0 processor.
@@ -16851,8 +16860,8 @@ header file.
The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is
known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the
430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be
-used to select the 430 \s-1ISA. \s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0
-name selects the 430X \s-1ISA.\s0
+used to select the 430 \s-1ISA\s0. Similarly the generic \fBmsp430x\fR \s-1MCU\s0
+name selects the 430X \s-1ISA\s0.
.Sp
In addition an MCU-specific linker script is added to the linker
command line. The script's name is the name of the \s-1MCU\s0 with
@@ -16865,7 +16874,7 @@ This option is also passed on to the assembler.
.IX Item "-mcpu="
Specifies the \s-1ISA\s0 to use. Accepted values are \fBmsp430\fR,
\&\fBmsp430x\fR and \fBmsp430xv2\fR. This option is deprecated. The
-\&\fB\-mmcu=\fR option should be used to select the \s-1ISA.\s0
+\&\fB\-mmcu=\fR option should be used to select the \s-1ISA\s0.
.IP "\fB\-msim\fR" 4
.IX Item "-msim"
Link to the simulator runtime libraries and linker script. Overrides
@@ -17042,7 +17051,7 @@ global pointer.
.Sp
The default is \fB\-mgpopt\fR except when \fB\-fpic\fR or
\&\fB\-fPIC\fR is specified to generate position-independent code.
-Note that the Nios \s-1II ABI\s0 does not permit GP-relative accesses from
+Note that the Nios \s-1II\s0 \s-1ABI\s0 does not permit GP-relative accesses from
shared libraries.
.Sp
You may need to specify \fB\-mno\-gpopt\fR explicitly when building
@@ -17115,7 +17124,7 @@ of the default behavior of using a library call.
.Sp
The following values of \fIinsn\fR are supported. Except as otherwise
noted, floating-point operations are expected to be implemented with
-normal \s-1IEEE 754\s0 semantics and correspond directly to the C operators or the
+normal \s-1IEEE\s0 754 semantics and correspond directly to the C operators or the
equivalent \s-1GCC\s0 built-in functions.
.Sp
Single-precision floating point:
@@ -17274,14 +17283,14 @@ configuration by using the \f(CW\*(C`target("custom\-fpu\-cfg=\f(CIname\f(CW")\*
function attribute
or pragma.
.PP
-These additional \fB\-m\fR options are available for the Altera Nios \s-1II
-ELF \s0(bare-metal) target:
+These additional \fB\-m\fR options are available for the Altera Nios \s-1II\s0
+\&\s-1ELF\s0 (bare-metal) target:
.IP "\fB\-mhal\fR" 4
.IX Item "-mhal"
-Link with \s-1HAL BSP. \s0 This suppresses linking with the GCC-provided C runtime
+Link with \s-1HAL\s0 \s-1BSP\s0. This suppresses linking with the GCC-provided C runtime
startup and termination code, and is typically used in conjunction with
\&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code
-provided by the \s-1HAL BSP.\s0
+provided by the \s-1HAL\s0 \s-1BSP\s0.
.IP "\fB\-msmallc\fR" 4
.IX Item "-msmallc"
Link with a limited version of the C library, \fB\-lsmallc\fR, rather than
@@ -17295,7 +17304,7 @@ when linking. This option is only useful in conjunction with \fB\-mhal\fR.
\&\fIsystemlib\fR is the library name of the library that provides
low-level system calls required by the C library,
e.g. \f(CW\*(C`read\*(C'\fR and \f(CW\*(C`write\*(C'\fR.
-This option is typically used to link with a library provided by a \s-1HAL BSP.\s0
+This option is typically used to link with a library provided by a \s-1HAL\s0 \s-1BSP\s0.
.PP
\fINvidia \s-1PTX\s0 Options\fR
.IX Subsection "Nvidia PTX Options"
@@ -17307,7 +17316,7 @@ These options are defined for Nvidia \s-1PTX:\s0
.IP "\fB\-m64\fR" 4
.IX Item "-m64"
.PD
-Generate code for 32\-bit or 64\-bit \s-1ABI.\s0
+Generate code for 32\-bit or 64\-bit \s-1ABI\s0.
.IP "\fB\-mmainkernel\fR" 4
.IX Item "-mmainkernel"
Link in code for a _\|_main kernel. This is for stand-alone instead of
@@ -17332,13 +17341,13 @@ Return floating-point results in ac0 (fr0 in Unix assembler syntax).
Return floating-point results in memory. This is the default.
.IP "\fB\-m40\fR" 4
.IX Item "-m40"
-Generate code for a \s-1PDP\-11/40.\s0
+Generate code for a \s-1PDP\-11/40\s0.
.IP "\fB\-m45\fR" 4
.IX Item "-m45"
-Generate code for a \s-1PDP\-11/45. \s0 This is the default.
+Generate code for a \s-1PDP\-11/45\s0. This is the default.
.IP "\fB\-m10\fR" 4
.IX Item "-m10"
-Generate code for a \s-1PDP\-11/10.\s0
+Generate code for a \s-1PDP\-11/10\s0.
.IP "\fB\-mbcopy\-builtin\fR" 4
.IX Item "-mbcopy-builtin"
Use inline \f(CW\*(C`movmemhi\*(C'\fR patterns for copying memory. This is the
@@ -17410,14 +17419,14 @@ for \fIae_type\fR are \fB\s-1ANY\s0\fR, \fB\s-1MUL\s0\fR, and \fB\s-1MAC\s0\fR.
generated with this option runs on any of the other \s-1AE\s0 types. The
code is not as efficient as it would be if compiled for a specific
\&\s-1AE\s0 type, and some types of operation (e.g., multiplication) do not
-work properly on all types of \s-1AE.\s0
+work properly on all types of \s-1AE\s0.
.Sp
-\&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type
+\&\fB\-mae=MUL\fR selects a \s-1MUL\s0 \s-1AE\s0 type. This is the most useful \s-1AE\s0 type
for compiled code, and is the default.
.Sp
-\&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE. \s0 Code compiled with this
+\&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC\s0 \s-1AE\s0. Code compiled with this
option may suffer from poor performance of byte (char) manipulation,
-since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores.
+since the \s-1DSP\s0 \s-1AE\s0 does not provide hardware support for byte load/stores.
.IP "\fB\-msymbol\-as\-address\fR" 4
.IX Item "-msymbol-as-address"
Enable the compiler to directly use a symbol name as an address in a
@@ -17430,7 +17439,7 @@ rather than being permanently enabled.
.IX Item "-mno-inefficient-warnings"
Disables warnings about the generation of inefficient code. These
warnings can be generated, for example, when compiling code that
-performs byte-level memory operations on the \s-1MAC AE\s0 type. The \s-1MAC AE\s0 has
+performs byte-level memory operations on the \s-1MAC\s0 \s-1AE\s0 type. The \s-1MAC\s0 \s-1AE\s0 has
no hardware support for byte-level memory operations, so all byte
load/stores must be synthesized from word load/store operations. This is
inefficient and a warning is generated to indicate
@@ -17472,10 +17481,10 @@ Make the \f(CW\*(C`double\*(C'\fR data type be 64 bits (\fB\-m64bit\-doubles\fR)
or 32 bits (\fB\-m32bit\-doubles\fR) in size. The default is
\&\fB\-m32bit\-doubles\fR.
.PP
-\fI\s-1IBM RS/6000\s0 and PowerPC Options\fR
+\fI\s-1IBM\s0 \s-1RS/6000\s0 and PowerPC Options\fR
.IX Subsection "IBM RS/6000 and PowerPC Options"
.PP
-These \fB\-m\fR options are defined for the \s-1IBM RS/6000\s0 and PowerPC:
+These \fB\-m\fR options are defined for the \s-1IBM\s0 \s-1RS/6000\s0 and PowerPC:
.IP "\fB\-mpowerpc\-gpopt\fR" 4
.IX Item "-mpowerpc-gpopt"
.PD 0
@@ -17520,7 +17529,7 @@ These \fB\-m\fR options are defined for the \s-1IBM RS/6000\s0 and PowerPC:
.PD
You use these options to specify which instructions are available on the
processor you are using. The default value of these options is
-determined when configuring \s-1GCC. \s0 Specifying the
+determined when configuring \s-1GCC\s0. Specifying the
\&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these
options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option
rather than the options listed above.
@@ -17603,7 +17612,7 @@ capabilities. If you wish to set an individual option to a particular
value, you may specify it after the \fB\-mcpu\fR option, like
\&\fB\-mcpu=970 \-mno\-altivec\fR.
.Sp
-On \s-1AIX,\s0 the \fB\-maltivec\fR and \fB\-mpowerpc64\fR options are
+On \s-1AIX\s0, the \fB\-maltivec\fR and \fB\-mpowerpc64\fR options are
not enabled or disabled by the \fB\-mcpu\fR option at present because
\&\s-1AIX\s0 does not have full support for these options. You may still
enable or disable them individually if you're sure it'll work in your
@@ -17691,14 +17700,14 @@ Generate code that allows \fBld\fR and \fBld.so\fR
to build executables and shared
libraries with non-executable \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections.
This is a PowerPC
-32\-bit \s-1SYSV ABI\s0 option.
+32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-mbss\-plt\fR" 4
.IX Item "-mbss-plt"
-Generate code that uses a \s-1BSS \s0\f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR
+Generate code that uses a \s-1BSS\s0 \f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR
fills in, and
requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR
sections that are both writable and executable.
-This is a PowerPC 32\-bit \s-1SYSV ABI\s0 option.
+This is a PowerPC 32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-misel\fR" 4
.IX Item "-misel"
.PD 0
@@ -17747,7 +17756,7 @@ more direct access to the \s-1VSX\s0 instruction set.
.PD
Enable the use (disable) of the built-in functions that allow direct
access to the cryptographic instructions that were added in version
-2.07 of the PowerPC \s-1ISA.\s0
+2.07 of the PowerPC \s-1ISA\s0.
.IP "\fB\-mdirect\-move\fR" 4
.IX Item "-mdirect-move"
.PD 0
@@ -17756,7 +17765,7 @@ access to the cryptographic instructions that were added in version
.PD
Generate code that uses (does not use) the instructions to move data
between the general purpose registers and the vector/scalar (\s-1VSX\s0)
-registers that were added in version 2.07 of the PowerPC \s-1ISA.\s0
+registers that were added in version 2.07 of the PowerPC \s-1ISA\s0.
.IP "\fB\-mpower8\-fusion\fR" 4
.IX Item "-mpower8-fusion"
.PD 0
@@ -17773,7 +17782,7 @@ later processors.
.IX Item "-mno-power8-vector"
.PD
Generate code that uses (does not use) the vector and scalar
-instructions that were added in version 2.07 of the PowerPC \s-1ISA. \s0 Also
+instructions that were added in version 2.07 of the PowerPC \s-1ISA\s0. Also
enable the use of built-in functions that allow more direct access to
the vector instructions.
.IP "\fB\-mquad\-memory\fR" 4
@@ -17803,7 +17812,7 @@ instructions. The \fB\-mquad\-memory\-atomic\fR option requires use of
Generate code that uses (does not use) the scalar double precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.06 of the
-PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-df\fR is turned on by default if you
+PowerPC \s-1ISA\s0. \fB\-mupper\-regs\-df\fR is turned on by default if you
use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or
\&\fB\-mvsx\fR options.
.IP "\fB\-mupper\-regs\-sf\fR" 4
@@ -17815,7 +17824,7 @@ use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or
Generate code that uses (does not use) the scalar single precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.07 of the
-PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-sf\fR is turned on by default if you
+PowerPC \s-1ISA\s0. \fB\-mupper\-regs\-sf\fR is turned on by default if you
use either of the \fB\-mcpu=power8\fR or \fB\-mpower8\-vector\fR
options.
.IP "\fB\-mupper\-regs\fR" 4
@@ -17872,12 +17881,12 @@ pointer to 64 bits, and generates code for PowerPC64, as for
.IP "\fB\-mminimal\-toc\fR" 4
.IX Item "-mminimal-toc"
.PD
-Modify generation of the \s-1TOC \s0(Table Of Contents), which is created for
+Modify generation of the \s-1TOC\s0 (Table Of Contents), which is created for
every executable file. The \fB\-mfull\-toc\fR option is selected by
default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for
each unique non-automatic variable reference in your program. \s-1GCC\s0
-also places floating-point constants in the \s-1TOC. \s0 However, only
-16,384 entries are available in the \s-1TOC.\s0
+also places floating-point constants in the \s-1TOC\s0. However, only
+16,384 entries are available in the \s-1TOC\s0.
.Sp
If you receive a linker error message that saying you have overflowed
the available \s-1TOC\s0 space, you can reduce the amount of \s-1TOC\s0 space used
@@ -17885,7 +17894,7 @@ with the \fB\-mno\-fp\-in\-toc\fR and \fB\-mno\-sum\-in\-toc\fR options.
\&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point
constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to
generate code to calculate the sum of an address and a constant at
-run time instead of putting that sum into the \s-1TOC. \s0 You may specify one
+run time instead of putting that sum into the \s-1TOC\s0. You may specify one
or both of these options. Each causes \s-1GCC\s0 to produce very slightly
slower and larger code at the expense of conserving \s-1TOC\s0 space.
.Sp
@@ -17901,7 +17910,7 @@ only on files that contain less frequently-executed code.
.IP "\fB\-maix32\fR" 4
.IX Item "-maix32"
.PD
-Enable 64\-bit \s-1AIX ABI\s0 and calling convention: 64\-bit pointers, 64\-bit
+Enable 64\-bit \s-1AIX\s0 \s-1ABI\s0 and calling convention: 64\-bit pointers, 64\-bit
\&\f(CW\*(C`long\*(C'\fR type, and the infrastructure needed to support them.
Specifying \fB\-maix64\fR implies \fB\-mpowerpc64\fR,
while \fB\-maix32\fR disables the 64\-bit \s-1ABI\s0 and
@@ -17912,8 +17921,8 @@ implies \fB\-mno\-powerpc64\fR. \s-1GCC\s0 defaults to \fB\-maix32\fR.
.IP "\fB\-mno\-xl\-compat\fR" 4
.IX Item "-mno-xl-compat"
.PD
-Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics
-when using AIX-compatible \s-1ABI. \s0 Pass floating-point arguments to
+Produce code that conforms more closely to \s-1IBM\s0 \s-1XL\s0 compiler semantics
+when using AIX-compatible \s-1ABI\s0. Pass floating-point arguments to
prototyped functions beyond the register save area (\s-1RSA\s0) on the stack
in addition to argument FPRs. Do not assume that most significant
double in 128\-bit long double value is properly rounded when comparing
@@ -17922,16 +17931,16 @@ support routines.
.Sp
The \s-1AIX\s0 calling convention was extended but not initially documented to
handle an obscure K&R C case of calling a function that takes the
-address of its arguments with fewer arguments than declared. \s-1IBM XL\s0
+address of its arguments with fewer arguments than declared. \s-1IBM\s0 \s-1XL\s0
compilers access floating-point arguments that do not fit in the
\&\s-1RSA\s0 from the stack when a subroutine is compiled without
optimization. Because always storing floating-point arguments on the
stack is inefficient and rarely needed, this option is not enabled by
-default and only is necessary when calling subroutines compiled by \s-1IBM
-XL\s0 compilers without optimization.
+default and only is necessary when calling subroutines compiled by \s-1IBM\s0
+\&\s-1XL\s0 compilers without optimization.
.IP "\fB\-mpe\fR" 4
.IX Item "-mpe"
-Support \fI\s-1IBM RS/6000 SP\s0\fR \fIParallel Environment\fR (\s-1PE\s0). Link an
+Support \fI\s-1IBM\s0 \s-1RS/6000\s0 \s-1SP\s0\fR \fIParallel Environment\fR (\s-1PE\s0). Link an
application written to use message passing with special startup code to
enable the application to run. The system must have \s-1PE\s0 installed in the
standard location (\fI/usr/lpp/ppe.poe/\fR), or the \fIspecs\fR file
@@ -17945,11 +17954,11 @@ option are incompatible.
.IP "\fB\-malign\-power\fR" 4
.IX Item "-malign-power"
.PD
-On \s-1AIX,\s0 32\-bit Darwin, and 64\-bit PowerPC GNU/Linux, the option
+On \s-1AIX\s0, 32\-bit Darwin, and 64\-bit PowerPC GNU/Linux, the option
\&\fB\-malign\-natural\fR overrides the ABI-defined alignment of larger
types, such as floating-point doubles, on their natural size-based boundary.
The option \fB\-malign\-power\fR instructs \s-1GCC\s0 to follow the ABI-specified
-alignment rules. \s-1GCC\s0 defaults to the standard alignment defined in the \s-1ABI.\s0
+alignment rules. \s-1GCC\s0 defaults to the standard alignment defined in the \s-1ABI\s0.
.Sp
On 64\-bit Darwin, natural alignment is the default, and \fB\-malign\-power\fR
is not supported.
@@ -17983,7 +17992,7 @@ Specify type of floating-point unit. Valid values for \fIname\fR are
and \fBdp_full\fR (equivalent to \fB\-mdouble\-float\fR).
.IP "\fB\-mxilinx\-fpu\fR" 4
.IX Item "-mxilinx-fpu"
-Perform optimizations for the floating-point unit on Xilinx \s-1PPC 405/440.\s0
+Perform optimizations for the floating-point unit on Xilinx \s-1PPC\s0 405/440.
.IP "\fB\-mmultiple\fR" 4
.IX Item "-mmultiple"
.PD 0
@@ -18054,7 +18063,7 @@ mapped to \fB\-ffp\-contract=off\fR.
.IX Item "-mno-mulhw"
.PD
Generate code that uses (does not use) the half-word multiply and
-multiply-accumulate instructions on the \s-1IBM 405, 440, 464\s0 and 476 processors.
+multiply-accumulate instructions on the \s-1IBM\s0 405, 440, 464 and 476 processors.
These instructions are generated by default when targeting those
processors.
.IP "\fB\-mdlmzb\fR" 4
@@ -18064,7 +18073,7 @@ processors.
.IX Item "-mno-dlmzb"
.PD
Generate code that uses (does not use) the string-search \fBdlmzb\fR
-instruction on the \s-1IBM 405, 440, 464\s0 and 476 processors. This instruction is
+instruction on the \s-1IBM\s0 405, 440, 464 and 476 processors. This instruction is
generated by default when targeting those processors.
.IP "\fB\-mno\-bit\-align\fR" 4
.IX Item "-mno-bit-align"
@@ -18144,7 +18153,7 @@ processor in big-endian mode. The \fB\-mbig\-endian\fR option is
the same as \fB\-mbig\fR.
.IP "\fB\-mdynamic\-no\-pic\fR" 4
.IX Item "-mdynamic-no-pic"
-On Darwin and Mac \s-1OS X\s0 systems, compile code so that it is not
+On Darwin and Mac \s-1OS\s0 X systems, compile code so that it is not
relocatable, but that its external references are relocatable. The
resulting code is suitable for applications, but not shared
libraries.
@@ -18250,11 +18259,11 @@ On System V.4 and embedded PowerPC systems compile code for the
OpenBSD operating system.
.IP "\fB\-maix\-struct\-return\fR" 4
.IX Item "-maix-struct-return"
-Return all structures in memory (as specified by the \s-1AIX ABI\s0).
+Return all structures in memory (as specified by the \s-1AIX\s0 \s-1ABI\s0).
.IP "\fB\-msvr4\-struct\-return\fR" 4
.IX Item "-msvr4-struct-return"
Return structures smaller than 8 bytes in registers (as specified by the
-\&\s-1SVR4 ABI\s0).
+\&\s-1SVR4\s0 \s-1ABI\s0).
.IP "\fB\-mabi=\fR\fIabi-type\fR" 4
.IX Item "-mabi=abi-type"
Extend the current \s-1ABI\s0 with a particular extension, or remove such extension.
@@ -18263,29 +18272,29 @@ Valid values are \fBaltivec\fR, \fBno-altivec\fR, \fBspe\fR,
\&\fBelfv1\fR, \fBelfv2\fR.
.IP "\fB\-mabi=spe\fR" 4
.IX Item "-mabi=spe"
-Extend the current \s-1ABI\s0 with \s-1SPE ABI\s0 extensions. This does not change
-the default \s-1ABI,\s0 instead it adds the \s-1SPE ABI\s0 extensions to the current
-\&\s-1ABI.\s0
+Extend the current \s-1ABI\s0 with \s-1SPE\s0 \s-1ABI\s0 extensions. This does not change
+the default \s-1ABI\s0, instead it adds the \s-1SPE\s0 \s-1ABI\s0 extensions to the current
+\&\s-1ABI\s0.
.IP "\fB\-mabi=no\-spe\fR" 4
.IX Item "-mabi=no-spe"
-Disable Book-E \s-1SPE ABI\s0 extensions for the current \s-1ABI.\s0
+Disable Book-E \s-1SPE\s0 \s-1ABI\s0 extensions for the current \s-1ABI\s0.
.IP "\fB\-mabi=ibmlongdouble\fR" 4
.IX Item "-mabi=ibmlongdouble"
Change the current \s-1ABI\s0 to use \s-1IBM\s0 extended-precision long double.
-This is a PowerPC 32\-bit \s-1SYSV ABI\s0 option.
+This is a PowerPC 32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-mabi=ieeelongdouble\fR" 4
.IX Item "-mabi=ieeelongdouble"
Change the current \s-1ABI\s0 to use \s-1IEEE\s0 extended-precision long double.
This is a PowerPC 32\-bit Linux \s-1ABI\s0 option.
.IP "\fB\-mabi=elfv1\fR" 4
.IX Item "-mabi=elfv1"
-Change the current \s-1ABI\s0 to use the ELFv1 \s-1ABI.\s0
+Change the current \s-1ABI\s0 to use the ELFv1 \s-1ABI\s0.
This is the default \s-1ABI\s0 for big-endian PowerPC 64\-bit Linux.
Overriding the default \s-1ABI\s0 requires special system support and is
likely to fail in spectacular ways.
.IP "\fB\-mabi=elfv2\fR" 4
.IX Item "-mabi=elfv2"
-Change the current \s-1ABI\s0 to use the ELFv2 \s-1ABI.\s0
+Change the current \s-1ABI\s0 to use the ELFv2 \s-1ABI\s0.
This is the default \s-1ABI\s0 for little-endian PowerPC 64\-bit Linux.
Overriding the default \s-1ABI\s0 requires special system support and is
likely to fail in spectacular ways.
@@ -18439,7 +18448,7 @@ On Darwin/PPC systems, \f(CW\*(C`#pragma longcall\*(C'\fR generates \f(CW\*(C`jb
callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target
addresses represent the callee and the branch island. The
Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl
-callee\*(C'\fR if the \s-1PPC \s0\f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly;
+callee\*(C'\fR if the \s-1PPC\s0 \f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly;
otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch
island. The branch island is appended to the body of the
calling function; it computes the full 32\-bit address of the callee
@@ -18535,7 +18544,7 @@ which handle the double-precision reciprocal square root calculations.
.PD
Assume (do not assume) that the reciprocal estimate instructions
provide higher-precision estimates than is mandated by the PowerPC
-\&\s-1ABI. \s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or
+\&\s-1ABI\s0. Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or
\&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR.
The double-precision square root estimate instructions are not generated by
default on low-precision machines, since they do not provide an
@@ -18608,14 +18617,14 @@ pointer. The \fB\-mno\-save\-toc\-indirect\fR option is the default.
.PD
Generate (do not generate) code to pass structure parameters with a
maximum alignment of 64 bits, for compatibility with older versions
-of \s-1GCC.\s0
+of \s-1GCC\s0.
.Sp
-Older versions of \s-1GCC \s0(prior to 4.9.0) incorrectly did not align a
+Older versions of \s-1GCC\s0 (prior to 4.9.0) incorrectly did not align a
structure parameter on a 128\-bit boundary when that structure contained
a member requiring 128\-bit alignment. This is corrected in more
-recent versions of \s-1GCC. \s0 This option may be used to generate code
+recent versions of \s-1GCC\s0. This option may be used to generate code
that is compatible with functions compiled with older versions of
-\&\s-1GCC.\s0
+\&\s-1GCC\s0.
.Sp
The \fB\-mno\-compat\-align\-parm\fR option is the default.
.PP
@@ -18650,12 +18659,12 @@ values, however, so the \s-1FPU\s0 hardware is not used for doubles if the
.Sp
\&\fINote\fR If the \fB\-fpu\fR option is enabled then
\&\fB\-funsafe\-math\-optimizations\fR is also enabled automatically.
-This is because the \s-1RX FPU\s0 instructions are themselves unsafe.
+This is because the \s-1RX\s0 \s-1FPU\s0 instructions are themselves unsafe.
.IP "\fB\-mcpu=\fR\fIname\fR" 4
.IX Item "-mcpu=name"
-Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are
+Selects the type of \s-1RX\s0 \s-1CPU\s0 to be targeted. Currently three types are
supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and
-the specific \fB\s-1RX610\s0\fR \s-1CPU. \s0 The default is \fB\s-1RX600\s0\fR.
+the specific \fB\s-1RX610\s0\fR \s-1CPU\s0. The default is \fB\s-1RX600\s0\fR.
.Sp
The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the
\&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction.
@@ -18841,7 +18850,7 @@ type. This is the default.
Store (do not store) the address of the caller's frame as backchain pointer
into the callee's stack frame.
A backchain may be needed to allow debugging using tools that do not understand
-\&\s-1DWARF 2\s0 call frame information.
+\&\s-1DWARF\s0 2 call frame information.
When \fB\-mno\-packed\-stack\fR is in effect, the backchain pointer is stored
at the bottom of the stack frame; when \fB\-mpacked\-stack\fR is in effect,
the backchain is placed into the topmost word of the 96/160 byte register
@@ -18873,7 +18882,7 @@ register is always saved two words below the backchain.
.Sp
As long as the stack frame backchain is not used, code generated with
\&\fB\-mpacked\-stack\fR is call-compatible with code generated with
-\&\fB\-mno\-packed\-stack\fR. Note that some non-FSF releases of \s-1GCC 2.95\s0 for
+\&\fB\-mno\-packed\-stack\fR. Note that some non-FSF releases of \s-1GCC\s0 2.95 for
S/390 or zSeries generated code that uses the stack frame backchain at run
time, not just for debugging purposes. Such code is not call-compatible
with code compiled with \fB\-mpacked\-stack\fR. Also, note that the
@@ -18900,8 +18909,8 @@ which does not have this limitation.
.IX Item "-m31"
.PD
When \fB\-m31\fR is specified, generate code compliant to the
-GNU/Linux for S/390 \s-1ABI. \s0 When \fB\-m64\fR is specified, generate
-code compliant to the GNU/Linux for zSeries \s-1ABI. \s0 This allows \s-1GCC\s0 in
+GNU/Linux for S/390 \s-1ABI\s0. When \fB\-m64\fR is specified, generate
+code compliant to the GNU/Linux for zSeries \s-1ABI\s0. This allows \s-1GCC\s0 in
particular to generate 64\-bit instructions. For the \fBs390\fR
targets, the default is \fB\-m31\fR, while the \fBs390x\fR
targets default to \fB\-m64\fR.
@@ -18914,11 +18923,11 @@ targets default to \fB\-m64\fR.
When \fB\-mzarch\fR is specified, generate code using the
instructions available on z/Architecture.
When \fB\-mesa\fR is specified, generate code using the
-instructions available on \s-1ESA/390. \s0 Note that \fB\-mesa\fR is
+instructions available on \s-1ESA/390\s0. Note that \fB\-mesa\fR is
not possible with \fB\-m64\fR.
-When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0
+When generating code compliant to the GNU/Linux for S/390 \s-1ABI\s0,
the default is \fB\-mesa\fR. When generating code compliant
-to the GNU/Linux for zSeries \s-1ABI,\s0 the default is \fB\-mzarch\fR.
+to the GNU/Linux for zSeries \s-1ABI\s0, the default is \fB\-mzarch\fR.
.IP "\fB\-mmvcle\fR" 4
.IX Item "-mmvcle"
.PD 0
@@ -18942,7 +18951,8 @@ The default is to not print debug information.
Generate code that runs on \fIcpu-type\fR, which is the name of a system
representing a certain processor type. Possible values for
\&\fIcpu-type\fR are \fBg5\fR, \fBg6\fR, \fBz900\fR, \fBz990\fR,
-\&\fBz9\-109\fR, \fBz9\-ec\fR, \fBz10\fR, \fBz196\fR, and \fBzEC12\fR.
+\&\fBz9\-109\fR, \fBz9\-ec\fR, \fBz10\fR, \fBz196\fR, \fBzEC12\fR,
+and \fBz13\fR.
When generating code using the instructions available on z/Architecture,
the default is \fB\-march=z900\fR. Otherwise, the default is
\&\fB\-march=g5\fR.
@@ -18958,9 +18968,9 @@ The default is the value used for \fB\-march\fR.
.IP "\fB\-mno\-tpf\-trace\fR" 4
.IX Item "-mno-tpf-trace"
.PD
-Generate code that adds (does not add) in \s-1TPF OS\s0 specific branches to trace
+Generate code that adds (does not add) in \s-1TPF\s0 \s-1OS\s0 specific branches to trace
routines in the operating system. This option is off by default, even
-when compiling for the \s-1TPF OS.\s0
+when compiling for the \s-1TPF\s0 \s-1OS\s0.
.IP "\fB\-mfused\-madd\fR" 4
.IX Item "-mfused-madd"
.PD 0
@@ -19053,16 +19063,16 @@ Specify the \s-1SCORE7D\s0 as the target architecture.
These \fB\-m\fR options are defined for the \s-1SH\s0 implementations:
.IP "\fB\-m1\fR" 4
.IX Item "-m1"
-Generate code for the \s-1SH1.\s0
+Generate code for the \s-1SH1\s0.
.IP "\fB\-m2\fR" 4
.IX Item "-m2"
-Generate code for the \s-1SH2.\s0
+Generate code for the \s-1SH2\s0.
.IP "\fB\-m2e\fR" 4
.IX Item "-m2e"
Generate code for the SH2e.
.IP "\fB\-m2a\-nofpu\fR" 4
.IX Item "-m2a-nofpu"
-Generate code for the SH2a without \s-1FPU,\s0 or for a SH2a\-FPU in such a way
+Generate code for the SH2a without \s-1FPU\s0, or for a SH2a\-FPU in such a way
that the floating-point unit is not used.
.IP "\fB\-m2a\-single\-only\fR" 4
.IX Item "-m2a-single-only"
@@ -19078,7 +19088,7 @@ Generate code for the SH2a\-FPU assuming the floating-point unit is in
double-precision mode by default.
.IP "\fB\-m3\fR" 4
.IX Item "-m3"
-Generate code for the \s-1SH3.\s0
+Generate code for the \s-1SH3\s0.
.IP "\fB\-m3e\fR" 4
.IX Item "-m3e"
Generate code for the SH3e.
@@ -19095,10 +19105,10 @@ Generate code for the \s-1SH4\s0 assuming the floating-point unit is in
single-precision mode by default.
.IP "\fB\-m4\fR" 4
.IX Item "-m4"
-Generate code for the \s-1SH4.\s0
+Generate code for the \s-1SH4\s0.
.IP "\fB\-m4\-100\fR" 4
.IX Item "-m4-100"
-Generate code for \s-1SH4\-100.\s0
+Generate code for \s-1SH4\-100\s0.
.IP "\fB\-m4\-100\-nofpu\fR" 4
.IX Item "-m4-100-nofpu"
Generate code for \s-1SH4\-100\s0 in such a way that the
@@ -19113,7 +19123,7 @@ Generate code for \s-1SH4\-100\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-200\fR" 4
.IX Item "-m4-200"
-Generate code for \s-1SH4\-200.\s0
+Generate code for \s-1SH4\-200\s0.
.IP "\fB\-m4\-200\-nofpu\fR" 4
.IX Item "-m4-200-nofpu"
Generate code for \s-1SH4\-200\s0 without in such a way that the
@@ -19128,7 +19138,7 @@ Generate code for \s-1SH4\-200\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-300\fR" 4
.IX Item "-m4-300"
-Generate code for \s-1SH4\-300.\s0
+Generate code for \s-1SH4\-300\s0.
.IP "\fB\-m4\-300\-nofpu\fR" 4
.IX Item "-m4-300-nofpu"
Generate code for \s-1SH4\-300\s0 without in such a way that the
@@ -19143,10 +19153,10 @@ Generate code for \s-1SH4\-300\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-340\fR" 4
.IX Item "-m4-340"
-Generate code for \s-1SH4\-340 \s0(no \s-1MMU,\s0 no \s-1FPU\s0).
+Generate code for \s-1SH4\-340\s0 (no \s-1MMU\s0, no \s-1FPU\s0).
.IP "\fB\-m4\-500\fR" 4
.IX Item "-m4-500"
-Generate code for \s-1SH4\-500 \s0(no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the
+Generate code for \s-1SH4\-500\s0 (no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the
assembler.
.IP "\fB\-m4a\-nofpu\fR" 4
.IX Item "-m4a-nofpu"
@@ -19210,7 +19220,7 @@ Use 32\-bit offsets in \f(CW\*(C`switch\*(C'\fR tables. The default is to use
16\-bit offsets.
.IP "\fB\-mbitops\fR" 4
.IX Item "-mbitops"
-Enable the use of bit manipulation instructions on \s-1SH2A.\s0
+Enable the use of bit manipulation instructions on \s-1SH2A\s0.
.IP "\fB\-mfmovd\fR" 4
.IX Item "-mfmovd"
Enable the use of the instruction \f(CW\*(C`fmovd\*(C'\fR. Check \fB\-mdalign\fR for
@@ -19257,7 +19267,7 @@ Dump instruction size and location in the assembly code.
.IP "\fB\-mpadstruct\fR" 4
.IX Item "-mpadstruct"
This option is deprecated. It pads structures to multiple of 4 bytes,
-which is incompatible with the \s-1SH ABI.\s0
+which is incompatible with the \s-1SH\s0 \s-1ABI\s0.
.IP "\fB\-matomic\-model=\fR\fImodel\fR" 4
.IX Item "-matomic-model=model"
Sets the model of atomic operations and additional parameters as a comma
@@ -19274,7 +19284,7 @@ Generate GNU/Linux compatible gUSA software atomic sequences for the atomic
built-in functions. The generated atomic sequences require additional support
from the interrupt/exception handling code of the system and are only suitable
for SH3* and SH4* single-core systems. This option is enabled by default when
-the target is \f(CW\*(C`sh*\-*\-linux*\*(C'\fR and SH3* or SH4*. When the target is \s-1SH4A,\s0
+the target is \f(CW\*(C`sh*\-*\-linux*\*(C'\fR and SH3* or SH4*. When the target is \s-1SH4A\s0,
this option also partially utilizes the hardware atomic instructions
\&\f(CW\*(C`movli.l\*(C'\fR and \f(CW\*(C`movco.l\*(C'\fR to create more efficient code, unless
\&\fBstrict\fR is specified.
@@ -19417,20 +19427,20 @@ For targets other than SHmedia \fIstrategy\fR can be one of:
.IX Item "call-div1"
Calls a library function that uses the single-step division instruction
\&\f(CW\*(C`div1\*(C'\fR to perform the operation. Division by zero calculates an
-unspecified result and does not trap. This is the default except for \s-1SH4,
-SH2A\s0 and SHcompact.
+unspecified result and does not trap. This is the default except for \s-1SH4\s0,
+\&\s-1SH2A\s0 and SHcompact.
.IP "\fBcall-fp\fR" 4
.IX Item "call-fp"
Calls a library function that performs the operation in double precision
floating point. Division by zero causes a floating-point exception. This is
-the default for SHcompact with \s-1FPU. \s0 Specifying this for targets that do not
+the default for SHcompact with \s-1FPU\s0. Specifying this for targets that do not
have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR.
.IP "\fBcall-table\fR" 4
.IX Item "call-table"
Calls a library function that uses a lookup table for small divisors and
the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division
by zero calculates an unspecified result and does not trap. This is the default
-for \s-1SH4. \s0 Specifying this for targets that do not have dynamic shift
+for \s-1SH4\s0. Specifying this for targets that do not have dynamic shift
instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR.
.RE
.RS 4
@@ -19464,10 +19474,10 @@ specified separated by a comma.
Enable the use of the indexed addressing mode for SHmedia32/SHcompact.
This is only safe if the hardware and/or \s-1OS\s0 implement 32\-bit wrap-around
semantics for the indexed addressing mode. The architecture allows the
-implementation of processors with 64\-bit \s-1MMU,\s0 which the \s-1OS\s0 could use to
+implementation of processors with 64\-bit \s-1MMU\s0, which the \s-1OS\s0 could use to
get 32\-bit addressing, but since no current hardware implementation supports
this or any other way to make the indexed addressing mode safe to use in
-the 32\-bit \s-1ABI,\s0 the default is \fB\-mno\-indexed\-addressing\fR.
+the 32\-bit \s-1ABI\s0, the default is \fB\-mno\-indexed\-addressing\fR.
.IP "\fB\-mgettrcost=\fR\fInumber\fR" 4
.IX Item "-mgettrcost=number"
Set the cost assumed for the \f(CW\*(C`gettr\*(C'\fR instruction to \fInumber\fR.
@@ -19504,7 +19514,7 @@ the compiler are always valid to load with
but with assembler and/or linker tricks it is possible
to generate symbols that cause \f(CW\*(C`ptabs\*(C'\fR or \f(CW\*(C`ptrel\*(C'\fR to trap.
This option is only meaningful when \fB\-mno\-pt\-fixed\fR is in effect.
-It prevents cross-basic-block \s-1CSE,\s0 hoisting and most scheduling
+It prevents cross-basic-block \s-1CSE\s0, hoisting and most scheduling
of symbol loads. The default is \fB\-mno\-invalid\-symbols\fR.
.IP "\fB\-mbranch\-cost=\fR\fInum\fR" 4
.IX Item "-mbranch-cost=num"
@@ -19521,14 +19531,14 @@ is being compiled for.
Assume (do not assume) that zero displacement conditional branch instructions
\&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the
compiler prefers zero displacement branch code sequences. This is
-enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A. \s0 It can be explicitly
+enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A\s0. It can be explicitly
disabled by specifying \fB\-mno\-zdcbranch\fR.
.IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4
.IX Item "-mcbranch-force-delay-slot"
Force the usage of delay slots for conditional branches, which stuffs the delay
slot with a \f(CW\*(C`nop\*(C'\fR if a suitable instruction can't be found. By default
this option is disabled. It can be enabled to work around hardware bugs as
-found in the original \s-1SH7055.\s0
+found in the original \s-1SH7055\s0.
.IP "\fB\-mfused\-madd\fR" 4
.IX Item "-mfused-madd"
.PD 0
@@ -19550,7 +19560,7 @@ mapped to \fB\-ffp\-contract=off\fR.
Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine
and cosine approximations. The option \fB\-mfsca\fR must be used in
combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default
-when generating code for \s-1SH4A. \s0 Using \fB\-mno\-fsca\fR disables sine and cosine
+when generating code for \s-1SH4A\s0. Using \fB\-mno\-fsca\fR disables sine and cosine
approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect.
.IP "\fB\-mfsrra\fR" 4
.IX Item "-mfsrra"
@@ -19562,7 +19572,7 @@ Allow or disallow the compiler to emit the \f(CW\*(C`fsrra\*(C'\fR instruction f
reciprocal square root approximations. The option \fB\-mfsrra\fR must be used
in combination with \fB\-funsafe\-math\-optimizations\fR and
\&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for
-\&\s-1SH4A. \s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations
+\&\s-1SH4A\s0. Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations
even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are
in effect.
.IP "\fB\-mpretend\-cmove\fR" 4
@@ -19616,7 +19626,7 @@ These \fB\-m\fR options are supported on the \s-1SPARC:\s0
.IX Item "-mapp-regs"
.PD
Specify \fB\-mapp\-regs\fR to generate output using the global registers
-2 through 4, which the \s-1SPARC SVR4 ABI\s0 reserves for applications. Like the
+2 through 4, which the \s-1SPARC\s0 \s-1SVR4\s0 \s-1ABI\s0 reserves for applications. Like the
global register 1, each global register 2 through 4 is then treated as an
allocable register that is clobbered by function calls. This is the default.
.Sp
@@ -19662,7 +19672,7 @@ cross-compilation. The embedded targets \fBsparc\-*\-aout\fR and
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-mhard\-quad\-float\fR" 4
.IX Item "-mhard-quad-float"
@@ -19672,7 +19682,7 @@ instructions.
.IX Item "-msoft-quad-float"
Generate output containing library calls for quad-word (long double)
floating-point instructions. The functions called are those specified
-in the \s-1SPARC ABI. \s0 This is the default.
+in the \s-1SPARC\s0 \s-1ABI\s0. This is the default.
.Sp
As of this writing, there are no \s-1SPARC\s0 implementations that have hardware
support for the quad-word floating-point instructions. They all invoke
@@ -19713,10 +19723,10 @@ With \fB\-mfaster\-structs\fR, the compiler assumes that structures
should have 8\-byte alignment. This enables the use of pairs of
\&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure
assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs.
-However, the use of this changed alignment directly violates the \s-1SPARC
-ABI. \s0 Thus, it's intended only for use on targets where the developer
+However, the use of this changed alignment directly violates the \s-1SPARC\s0
+\&\s-1ABI\s0. Thus, it's intended only for use on targets where the developer
acknowledges that their resulting code is not directly in line with
-the rules of the \s-1ABI.\s0
+the rules of the \s-1ABI\s0.
.IP "\fB\-mcpu=\fR\fIcpu_type\fR" 4
.IX Item "-mcpu=cpu_type"
Set the instruction set, register set, and instruction scheduling parameters
@@ -19766,22 +19776,22 @@ SPARCStation 1, 2, \s-1IPX\s0 etc.
With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0
architecture. The only difference from V7 code is that the compiler emits
the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0
-but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=supersparc\fR, the compiler additionally
+but not in \s-1SPARC\-V7\s0. With \fB\-mcpu=supersparc\fR, the compiler additionally
optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and
2000 series.
.Sp
With \fB\-mcpu=sparclite\fR, \s-1GCC\s0 generates code for the SPARClite variant of
the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step
-and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0
+and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7\s0.
With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the
-Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU. \s0 With
+Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU\s0. With
\&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu
-\&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0
+\&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU\s0.
.Sp
With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of
the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate,
integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet
-but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=tsc701\fR, the compiler additionally
+but not in \s-1SPARC\-V7\s0. With \fB\-mcpu=tsc701\fR, the compiler additionally
optimizes it for the \s-1TEMIC\s0 SPARClet chip.
.Sp
With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0
@@ -19818,7 +19828,7 @@ toolchains, \fBnative\fR can also be used.
.IP "\fB\-mno\-v8plus\fR" 4
.IX Item "-mno-v8plus"
.PD
-With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI. \s0 The
+With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+\s0 \s-1ABI\s0. The
difference from the V8 \s-1ABI\s0 is that the global and out registers are
considered 64 bits wide. This is enabled by default on Solaris in 32\-bit
mode for all \s-1SPARC\-V9\s0 processors.
@@ -20273,9 +20283,9 @@ This option suppresses generation of the \f(CW\*(C`CALLT\*(C'\fR instruction for
v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the v850
architecture.
.Sp
-This option is enabled by default when the \s-1RH850 ABI\s0 is
+This option is enabled by default when the \s-1RH850\s0 \s-1ABI\s0 is
in use (see \fB\-mrh850\-abi\fR), and disabled by default when the
-\&\s-1GCC ABI\s0 is in use. If \f(CW\*(C`CALLT\*(C'\fR instructions are being generated
+\&\s-1GCC\s0 \s-1ABI\s0 is in use. If \f(CW\*(C`CALLT\*(C'\fR instructions are being generated
then the C preprocessor symbol \f(CW\*(C`_\|_V850_CALLT_\|_\*(C'\fR is defined.
.IP "\fB\-mrelax\fR" 4
.IX Item "-mrelax"
@@ -20315,7 +20325,7 @@ selected because its use is still experimental.
.IP "\fB\-mghs\fR" 4
.IX Item "-mghs"
.PD
-Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI. \s0 This is the
+Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI\s0. This is the
default. With this version of the \s-1ABI\s0 the following rules apply:
.RS 4
.IP "*" 4
@@ -20340,7 +20350,7 @@ When this version of the \s-1ABI\s0 is enabled the C preprocessor symbol
.RE
.IP "\fB\-mgcc\-abi\fR" 4
.IX Item "-mgcc-abi"
-Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI. \s0 With this
+Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI\s0. With this
version of the \s-1ABI\s0 the following rules apply:
.RS 4
.IP "*" 4
@@ -20435,7 +20445,7 @@ Generate code containing library calls for floating-point.
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-mcpu=\fR\fIcpu_type\fR" 4
.IX Item "-mcpu=cpu_type"
@@ -20463,8 +20473,8 @@ the access to general registers. This is the default.
.IP "\fB\-muser\-mode\fR" 4
.IX Item "-muser-mode"
Generate code for the user mode, where the access to some general registers
-is forbidden: on the \s-1GR5,\s0 registers r24 to r31 cannot be accessed in this
-mode; on the \s-1GR6,\s0 only registers r29 to r31 are affected.
+is forbidden: on the \s-1GR5\s0, registers r24 to r31 cannot be accessed in this
+mode; on the \s-1GR6\s0, only registers r29 to r31 are affected.
.PP
\fI\s-1VMS\s0 Options\fR
.IX Subsection "VMS Options"
@@ -20547,10 +20557,10 @@ produces code optimized for the local machine under the constraints
of the selected instruction set.
.IP "\fBi386\fR" 4
.IX Item "i386"
-Original Intel i386 \s-1CPU.\s0
+Original Intel i386 \s-1CPU\s0.
.IP "\fBi486\fR" 4
.IX Item "i486"
-Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.)
+Intel i486 \s-1CPU\s0. (No scheduling is implemented for this chip.)
.IP "\fBi586\fR" 4
.IX Item "i586"
.PD 0
@@ -20560,10 +20570,10 @@ Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.)
Intel Pentium \s-1CPU\s0 with no \s-1MMX\s0 support.
.IP "\fBpentium-mmx\fR" 4
.IX Item "pentium-mmx"
-Intel Pentium \s-1MMX CPU,\s0 based on Pentium core with \s-1MMX\s0 instruction set support.
+Intel Pentium \s-1MMX\s0 \s-1CPU\s0, based on Pentium core with \s-1MMX\s0 instruction set support.
.IP "\fBpentiumpro\fR" 4
.IX Item "pentiumpro"
-Intel Pentium Pro \s-1CPU.\s0
+Intel Pentium Pro \s-1CPU\s0.
.IP "\fBi686\fR" 4
.IX Item "i686"
When used with \fB\-march\fR, the Pentium Pro
@@ -20571,7 +20581,7 @@ instruction set is used, so the code runs on all i686 family chips.
When used with \fB\-mtune\fR, it has the same meaning as \fBgeneric\fR.
.IP "\fBpentium2\fR" 4
.IX Item "pentium2"
-Intel Pentium \s-1II CPU,\s0 based on Pentium Pro core with \s-1MMX\s0 instruction set
+Intel Pentium \s-1II\s0 \s-1CPU\s0, based on Pentium Pro core with \s-1MMX\s0 instruction set
support.
.IP "\fBpentium3\fR" 4
.IX Item "pentium3"
@@ -20579,89 +20589,89 @@ support.
.IP "\fBpentium3m\fR" 4
.IX Item "pentium3m"
.PD
-Intel Pentium \s-1III CPU,\s0 based on Pentium Pro core with \s-1MMX\s0 and \s-1SSE\s0 instruction
+Intel Pentium \s-1III\s0 \s-1CPU\s0, based on Pentium Pro core with \s-1MMX\s0 and \s-1SSE\s0 instruction
set support.
.IP "\fBpentium-m\fR" 4
.IX Item "pentium-m"
-Intel Pentium M; low-power version of Intel Pentium \s-1III CPU\s0
-with \s-1MMX, SSE\s0 and \s-1SSE2\s0 instruction set support. Used by Centrino notebooks.
+Intel Pentium M; low-power version of Intel Pentium \s-1III\s0 \s-1CPU\s0
+with \s-1MMX\s0, \s-1SSE\s0 and \s-1SSE2\s0 instruction set support. Used by Centrino notebooks.
.IP "\fBpentium4\fR" 4
.IX Item "pentium4"
.PD 0
.IP "\fBpentium4m\fR" 4
.IX Item "pentium4m"
.PD
-Intel Pentium 4 \s-1CPU\s0 with \s-1MMX, SSE\s0 and \s-1SSE2\s0 instruction set support.
+Intel Pentium 4 \s-1CPU\s0 with \s-1MMX\s0, \s-1SSE\s0 and \s-1SSE2\s0 instruction set support.
.IP "\fBprescott\fR" 4
.IX Item "prescott"
-Improved version of Intel Pentium 4 \s-1CPU\s0 with \s-1MMX, SSE, SSE2\s0 and \s-1SSE3\s0 instruction
+Improved version of Intel Pentium 4 \s-1CPU\s0 with \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0 and \s-1SSE3\s0 instruction
set support.
.IP "\fBnocona\fR" 4
.IX Item "nocona"
-Improved version of Intel Pentium 4 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE,
-SSE2\s0 and \s-1SSE3\s0 instruction set support.
+Improved version of Intel Pentium 4 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0,
+\&\s-1SSE2\s0 and \s-1SSE3\s0 instruction set support.
.IP "\fBcore2\fR" 4
.IX Item "core2"
-Intel Core 2 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3\s0 and \s-1SSSE3\s0
+Intel Core 2 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0 and \s-1SSSE3\s0
instruction set support.
.IP "\fBnehalem\fR" 4
.IX Item "nehalem"
-Intel Nehalem \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2\s0 and \s-1POPCNT\s0 instruction set support.
+Intel Nehalem \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2 and \s-1POPCNT\s0 instruction set support.
.IP "\fBwestmere\fR" 4
.IX Item "westmere"
-Intel Westmere \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AES\s0 and \s-1PCLMUL\s0 instruction set support.
+Intel Westmere \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AES\s0 and \s-1PCLMUL\s0 instruction set support.
.IP "\fBsandybridge\fR" 4
.IX Item "sandybridge"
-Intel Sandy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AES\s0 and \s-1PCLMUL\s0 instruction set support.
+Intel Sandy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AES\s0 and \s-1PCLMUL\s0 instruction set support.
.IP "\fBivybridge\fR" 4
.IX Item "ivybridge"
-Intel Ivy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND\s0 and F16C
+Intel Ivy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0 and F16C
instruction set support.
.IP "\fBhaswell\fR" 4
.IX Item "haswell"
-Intel Haswell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2\s0 and F16C instruction set support.
+Intel Haswell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0 and F16C instruction set support.
.IP "\fBbroadwell\fR" 4
.IX Item "broadwell"
-Intel Broadwell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2, F16C, RDSEED, ADCX\s0 and \s-1PREFETCHW\s0 instruction set support.
+Intel Broadwell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, F16C, \s-1RDSEED\s0, \s-1ADCX\s0 and \s-1PREFETCHW\s0 instruction set support.
.IP "\fBbonnell\fR" 4
.IX Item "bonnell"
-Intel Bonnell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3\s0 and \s-1SSSE3\s0
+Intel Bonnell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0 and \s-1SSSE3\s0
instruction set support.
.IP "\fBsilvermont\fR" 4
.IX Item "silvermont"
-Intel Silvermont \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AES, PCLMUL\s0 and \s-1RDRND\s0 instruction set support.
+Intel Silvermont \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AES\s0, \s-1PCLMUL\s0 and \s-1RDRND\s0 instruction set support.
.IP "\fBknl\fR" 4
.IX Item "knl"
-Intel Knight's Landing \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3,
-SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2, F16C, RDSEED, ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER\s0 and
+Intel Knight's Landing \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0,
+\&\s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, F16C, \s-1RDSEED\s0, \s-1ADCX\s0, \s-1PREFETCHW\s0, \s-1AVX512F\s0, \s-1AVX512PF\s0, \s-1AVX512ER\s0 and
\&\s-1AVX512CD\s0 instruction set support.
.IP "\fBk6\fR" 4
.IX Item "k6"
-\&\s-1AMD K6 CPU\s0 with \s-1MMX\s0 instruction set support.
+\&\s-1AMD\s0 K6 \s-1CPU\s0 with \s-1MMX\s0 instruction set support.
.IP "\fBk6\-2\fR" 4
.IX Item "k6-2"
.PD 0
.IP "\fBk6\-3\fR" 4
.IX Item "k6-3"
.PD
-Improved versions of \s-1AMD K6 CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support.
+Improved versions of \s-1AMD\s0 K6 \s-1CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support.
.IP "\fBathlon\fR" 4
.IX Item "athlon"
.PD 0
.IP "\fBathlon-tbird\fR" 4
.IX Item "athlon-tbird"
.PD
-\&\s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX,\s0 3dNOW!, enhanced 3DNow! and \s-1SSE\s0 prefetch instructions
+\&\s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX\s0, 3dNOW!, enhanced 3DNow! and \s-1SSE\s0 prefetch instructions
support.
.IP "\fBathlon\-4\fR" 4
.IX Item "athlon-4"
@@ -20671,7 +20681,7 @@ support.
.IP "\fBathlon-mp\fR" 4
.IX Item "athlon-mp"
.PD
-Improved \s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX,\s0 3DNow!, enhanced 3DNow! and full \s-1SSE\s0
+Improved \s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX\s0, 3DNow!, enhanced 3DNow! and full \s-1SSE\s0
instruction set support.
.IP "\fBk8\fR" 4
.IX Item "k8"
@@ -20683,9 +20693,9 @@ instruction set support.
.IP "\fBathlon-fx\fR" 4
.IX Item "athlon-fx"
.PD
-Processors based on the \s-1AMD K8\s0 core with x86\-64 instruction set support,
+Processors based on the \s-1AMD\s0 K8 core with x86\-64 instruction set support,
including the \s-1AMD\s0 Opteron, Athlon 64, and Athlon 64 \s-1FX\s0 processors.
-(This supersets \s-1MMX, SSE, SSE2,\s0 3DNow!, enhanced 3DNow! and 64\-bit
+(This supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, 3DNow!, enhanced 3DNow! and 64\-bit
instruction set extensions.)
.IP "\fBk8\-sse3\fR" 4
.IX Item "k8-sse3"
@@ -20695,7 +20705,7 @@ instruction set extensions.)
.IP "\fBathlon64\-sse3\fR" 4
.IX Item "athlon64-sse3"
.PD
-Improved versions of \s-1AMD K8\s0 cores with \s-1SSE3\s0 instruction set support.
+Improved versions of \s-1AMD\s0 K8 cores with \s-1SSE3\s0 instruction set support.
.IP "\fBamdfam10\fR" 4
.IX Item "amdfam10"
.PD 0
@@ -20703,56 +20713,56 @@ Improved versions of \s-1AMD K8\s0 cores with \s-1SSE3\s0 instruction set suppor
.IX Item "barcelona"
.PD
CPUs based on \s-1AMD\s0 Family 10h cores with x86\-64 instruction set support. (This
-supersets \s-1MMX, SSE, SSE2, SSE3, SSE4A,\s0 3DNow!, enhanced 3DNow!, \s-1ABM\s0 and 64\-bit
+supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, 3DNow!, enhanced 3DNow!, \s-1ABM\s0 and 64\-bit
instruction set extensions.)
.IP "\fBbdver1\fR" 4
.IX Item "bdver1"
CPUs based on \s-1AMD\s0 Family 15h cores with x86\-64 instruction set support. (This
-supersets \s-1FMA4, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A,
-SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions.)
+supersets \s-1FMA4\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0,
+\&\s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set extensions.)
.IP "\fBbdver2\fR" 4
.IX Item "bdver2"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, TBM, F16C, FMA, FMA4, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX,
-SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set
+supersets \s-1BMI\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0,
+\&\s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set
extensions.)
.IP "\fBbdver3\fR" 4
.IX Item "bdver3"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES,
-PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and
+supersets \s-1BMI\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1FSGSBASE\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0,
+\&\s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and
64\-bit instruction set extensions.
.IP "\fBbdver4\fR" 4
.IX Item "bdver4"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP,
-AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1,
-SSE4.2, ABM\s0 and 64\-bit instruction set extensions.
+supersets \s-1BMI\s0, \s-1BMI2\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1FSGSBASE\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1XOP\s0, \s-1LWP\s0,
+\&\s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1,
+\&\s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set extensions.
.IP "\fBbtver1\fR" 4
.IX Item "btver1"
CPUs based on \s-1AMD\s0 Family 14h cores with x86\-64 instruction set support. (This
-supersets \s-1MMX, SSE, SSE2, SSE3, SSSE3, SSE4A, CX16, ABM\s0 and 64\-bit
+supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0, \s-1SSE4A\s0, \s-1CX16\s0, \s-1ABM\s0 and 64\-bit
instruction set extensions.)
.IP "\fBbtver2\fR" 4
.IX Item "btver2"
CPUs based on \s-1AMD\s0 Family 16h cores with x86\-64 instruction set support. This
-includes \s-1MOVBE, F16C, BMI, AVX, PCL_MUL, AES, SSE4.2, SSE4.1, CX16, ABM,
-SSE4A, SSSE3, SSE3, SSE2, SSE, MMX\s0 and 64\-bit instruction set extensions.
+includes \s-1MOVBE\s0, F16C, \s-1BMI\s0, \s-1AVX\s0, \s-1PCL_MUL\s0, \s-1AES\s0, \s-1SSE4\s0.2, \s-1SSE4\s0.1, \s-1CX16\s0, \s-1ABM\s0,
+\&\s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE3\s0, \s-1SSE2\s0, \s-1SSE\s0, \s-1MMX\s0 and 64\-bit instruction set extensions.
.IP "\fBwinchip\-c6\fR" 4
.IX Item "winchip-c6"
-\&\s-1IDT\s0 WinChip C6 \s-1CPU,\s0 dealt in same way as i486 with additional \s-1MMX\s0 instruction
+\&\s-1IDT\s0 WinChip C6 \s-1CPU\s0, dealt in same way as i486 with additional \s-1MMX\s0 instruction
set support.
.IP "\fBwinchip2\fR" 4
.IX Item "winchip2"
-\&\s-1IDT\s0 WinChip 2 \s-1CPU,\s0 dealt in same way as i486 with additional \s-1MMX\s0 and 3DNow!
+\&\s-1IDT\s0 WinChip 2 \s-1CPU\s0, dealt in same way as i486 with additional \s-1MMX\s0 and 3DNow!
instruction set support.
.IP "\fBc3\fR" 4
.IX Item "c3"
-\&\s-1VIA C3 CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support. (No scheduling is
+\&\s-1VIA\s0 C3 \s-1CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support. (No scheduling is
implemented for this chip.)
.IP "\fBc3\-2\fR" 4
.IX Item "c3-2"
-\&\s-1VIA C3\-2 \s0(Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support.
+\&\s-1VIA\s0 C3\-2 (Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support.
(No scheduling is
implemented for this chip.)
.IP "\fBgeode\fR" 4
@@ -20786,7 +20796,7 @@ of your application will have, then you should use this option.
.Sp
As new processors are deployed in the marketplace, the behavior of this
option will change. Therefore, if you upgrade to a newer version of
-\&\s-1GCC,\s0 code generation controlled by this option will change to reflect
+\&\s-1GCC\s0, code generation controlled by this option will change to reflect
the processors
that are most common at the time that version of \s-1GCC\s0 is released.
.Sp
@@ -20798,7 +20808,7 @@ processors) for which the code is optimized.
.IP "\fBintel\fR" 4
.IX Item "intel"
Produce code optimized for the most current Intel processors, which are
-Haswell and Silvermont for this version of \s-1GCC. \s0 If you know the \s-1CPU\s0
+Haswell and Silvermont for this version of \s-1GCC\s0. If you know the \s-1CPU\s0
on which your code will run, then you should use the corresponding
\&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR.
But, if you want your application performs better on both Haswell and
@@ -20806,7 +20816,7 @@ Silvermont, then you should use this option.
.Sp
As new Intel processors are deployed in the marketplace, the behavior of
this option will change. Therefore, if you upgrade to a newer version of
-\&\s-1GCC,\s0 code generation controlled by this option will change to reflect
+\&\s-1GCC\s0, code generation controlled by this option will change to reflect
the most current Intel processors at the time that version of \s-1GCC\s0 is
released.
.Sp
@@ -20891,7 +20901,7 @@ comparison is unordered.
.IX Item "-msoft-float"
Generate output containing library calls for floating point.
.Sp
-\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC.\s0
+\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC\s0.
Normally the facilities of the machine's usual C compiler are used, but
this can't be done directly in cross-compilation. You must make your
own arrangements to provide suitable library functions for
@@ -20906,8 +20916,8 @@ Do not use the \s-1FPU\s0 registers for return values of functions.
.Sp
The usual calling convention has functions return values of types
\&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there
-is no \s-1FPU. \s0 The idea is that the operating system should emulate
-an \s-1FPU.\s0
+is no \s-1FPU\s0. The idea is that the operating system should emulate
+an \s-1FPU\s0.
.Sp
The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned
in ordinary \s-1CPU\s0 registers instead.
@@ -20915,7 +20925,7 @@ in ordinary \s-1CPU\s0 registers instead.
.IX Item "-mno-fancy-math-387"
Some 387 emulators do not support the \f(CW\*(C`sin\*(C'\fR, \f(CW\*(C`cos\*(C'\fR and
\&\f(CW\*(C`sqrt\*(C'\fR instructions for the 387. Specify this option to avoid
-generating those instructions. This option is the default on FreeBSD,
+generating those instructions. This option is the default on
OpenBSD and NetBSD. This option is overridden when \fB\-march\fR
indicates that the target \s-1CPU\s0 always has an \s-1FPU\s0 and so the
instruction does not need emulation. These
@@ -20952,7 +20962,7 @@ so \fB\-m96bit\-long\-double\fR is the default in 32\-bit mode.
.Sp
Modern architectures (Pentium and newer) prefer \f(CW\*(C`long double\*(C'\fR
to be aligned to an 8\- or 16\-byte boundary. In arrays or structures
-conforming to the \s-1ABI,\s0 this is not possible. So specifying
+conforming to the \s-1ABI\s0, this is not possible. So specifying
\&\fB\-m128bit\-long\-double\fR aligns \f(CW\*(C`long double\*(C'\fR
to a 16\-byte boundary by padding the \f(CW\*(C`long double\*(C'\fR with an additional
32\-bit zero.
@@ -20963,7 +20973,7 @@ its \s-1ABI\s0 specifies that \f(CW\*(C`long double\*(C'\fR is aligned on 16\-by
Notice that neither of these options enable any extra precision over the x87
standard of 80 bits for a \f(CW\*(C`long double\*(C'\fR.
.Sp
-\&\fBWarning:\fR if you override the default value for your target \s-1ABI,\s0 this
+\&\fBWarning:\fR if you override the default value for your target \s-1ABI\s0, this
changes the size of
structures and arrays containing \f(CW\*(C`long double\*(C'\fR variables,
as well as modifying the function calling convention for functions taking
@@ -20983,7 +20993,7 @@ type. This is the default for 32\-bit Bionic C library. A size
of 128 bits makes the \f(CW\*(C`long double\*(C'\fR type equivalent to the
\&\f(CW\*(C`_\|_float128\*(C'\fR type. This is the default for 64\-bit Bionic C library.
.Sp
-\&\fBWarning:\fR if you override the default value for your target \s-1ABI,\s0 this
+\&\fBWarning:\fR if you override the default value for your target \s-1ABI\s0, this
changes the size of
structures and arrays containing \f(CW\*(C`long double\*(C'\fR variables,
as well as modifying the function calling convention for functions taking
@@ -20992,7 +21002,7 @@ with code compiled without that switch.
.IP "\fB\-malign\-data=\fR\fItype\fR" 4
.IX Item "-malign-data=type"
Control how \s-1GCC\s0 aligns variables. Supported values for \fItype\fR are
-\&\fBcompat\fR uses increased alignment value compatible uses \s-1GCC 4.8\s0
+\&\fBcompat\fR uses increased alignment value compatible uses \s-1GCC\s0 4.8
and earlier, \fBabi\fR uses alignment value as specified by the
psABI, and \fBcacheline\fR uses increased alignment value to match
the cache line size. \fBcompat\fR is the default.
@@ -21054,7 +21064,7 @@ Studio compilers until version 12. Later compiler versions (starting
with Studio 12 Update@tie{}1) follow the \s-1ABI\s0 used by other x86 targets, which
is the default on Solaris@tie{}10 and later. \fIOnly\fR use this option if
you need to remain compatible with existing code produced by those
-previous compiler versions or older versions of \s-1GCC.\s0
+previous compiler versions or older versions of \s-1GCC\s0.
.IP "\fB\-mpc32\fR" 4
.IX Item "-mpc32"
.PD 0
@@ -21115,7 +21125,7 @@ the one specified by \fB\-mpreferred\-stack\-boundary\fR is used.
.Sp
On Pentium and Pentium Pro, \f(CW\*(C`double\*(C'\fR and \f(CW\*(C`long double\*(C'\fR values
should be aligned to an 8\-byte boundary (see \fB\-malign\-double\fR) or
-suffer significant run time performance penalties. On Pentium \s-1III,\s0 the
+suffer significant run time performance penalties. On Pentium \s-1III\s0, the
Streaming \s-1SIMD\s0 Extension (\s-1SSE\s0) data type \f(CW\*(C`_\|_m128\*(C'\fR may not work
properly if it is not 16\-byte aligned.
.Sp
@@ -21216,11 +21226,13 @@ preferred alignment to \fB\-mpreferred\-stack\-boundary=2\fR.
.IX Item "-mtbm"
.IP "\fB\-mmpx\fR" 4
.IX Item "-mmpx"
+.IP "\fB\-mmwaitx\fR" 4
+.IX Item "-mmwaitx"
.PD
-These switches enable the use of instructions in the \s-1MMX, SSE,
-SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER, AVX512CD,
-SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A, FMA4, XOP, LWP, ABM,
-BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX\s0 or 3DNow!
+These switches enable the use of instructions in the \s-1MMX\s0, \s-1SSE\s0,
+\&\s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1AVX\s0, \s-1AVX2\s0, \s-1AVX512F\s0, \s-1AVX512PF\s0, \s-1AVX512ER\s0, \s-1AVX512CD\s0,
+\&\s-1SHA\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, F16C, \s-1FMA\s0, \s-1SSE4A\s0, \s-1FMA4\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1ABM\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, \s-1FXSR\s0, \s-1XSAVE\s0, \s-1XSAVEOPT\s0, \s-1LZCNT\s0, \s-1RTM\s0, \s-1MPX\s0, \s-1MWAITX\s0 or 3DNow!
extended instruction sets. Each has a corresponding \fB\-mno\-\fR option
to disable use of these instructions.
.Sp
@@ -21297,7 +21309,7 @@ This option enables generation of \f(CW\*(C`SAHF\*(C'\fR instructions in 64\-bit
Early Intel Pentium 4 CPUs with Intel 64 support,
prior to the introduction of Pentium 4 G1 step in December 2005,
lacked the \f(CW\*(C`LAHF\*(C'\fR and \f(CW\*(C`SAHF\*(C'\fR instructions
-which are supported by \s-1AMD64.\s0
+which are supported by \s-1AMD64\s0.
These are load and store instructions, respectively, for certain status flags.
In 64\-bit mode, the \f(CW\*(C`SAHF\*(C'\fR instruction is used to optimize \f(CW\*(C`fmod\*(C'\fR,
\&\f(CW\*(C`drem\*(C'\fR, and \f(CW\*(C`remainder\*(C'\fR built-in functions;
@@ -21373,7 +21385,7 @@ external library. Supported values for \fItype\fR are \fBsvml\fR
for the Intel short
vector math library and \fBacml\fR for the \s-1AMD\s0 math core library.
To use this option, both \fB\-ftree\-vectorize\fR and
-\&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML \s0
+\&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML\s0
ABI-compatible library must be specified at link time.
.Sp
\&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR,
@@ -21396,7 +21408,7 @@ when \fB\-mveclibabi=acml\fR is used.
.IX Item "-mabi=name"
Generate code for the specified calling convention. Permissible values
are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and
-\&\fBms\fR for the Microsoft \s-1ABI. \s0 The default is to use the Microsoft
+\&\fBms\fR for the Microsoft \s-1ABI\s0. The default is to use the Microsoft
\&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems.
You can control this behavior for specific functions by
using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR.
@@ -21511,7 +21523,7 @@ or whether the thread base pointer must be added. Whether or not this
is valid depends on the operating system, and whether it maps the
segment to cover the entire \s-1TLS\s0 area.
.Sp
-For systems that use the \s-1GNU C\s0 Library, the default is on.
+For systems that use the \s-1GNU\s0 C Library, the default is on.
.IP "\fB\-msse2avx\fR" 4
.IX Item "-msse2avx"
.PD 0
@@ -21562,7 +21574,7 @@ register when there are no variable arguments passed in vector registers.
\&\fBWarning:\fR Since \s-1RAX\s0 register is used to avoid unnecessarily
saving vector registers on stack when passing variable arguments, the
impacts of this option are callees may waste some stack space,
-misbehave or jump to a random location. \s-1GCC 4.4\s0 or newer don't have
+misbehave or jump to a random location. \s-1GCC\s0 4.4 or newer don't have
those issues, regardless the \s-1RAX\s0 register value.
.IP "\fB\-m8bit\-idiv\fR" 4
.IX Item "-m8bit-idiv"
@@ -21706,7 +21718,7 @@ appropriately.
This option is available for MinGW targets. It specifies that
the executable flag for the stack used by nested functions isn't
set. This is necessary for binaries running in kernel mode of
-Microsoft Windows, as there the User32 \s-1API,\s0 which is used to set executable
+Microsoft Windows, as there the User32 \s-1API\s0, which is used to set executable
privileges, isn't available.
.IP "\fB\-fwritable\-relocated\-rdata\fR" 4
.IX Item "-fwritable-relocated-rdata"
@@ -21791,7 +21803,7 @@ kernel code.
These options control the treatment of literal pools. The default is
\&\fB\-mno\-text\-section\-literals\fR, which places literals in a separate
section in the output file. This allows the literal pool to be placed
-in a data \s-1RAM/ROM,\s0 and it also allows the linker to combine literal
+in a data \s-1RAM/ROM\s0, and it also allows the linker to combine literal
pools from separate object files to remove redundant literals and
improve code size. With \fB\-mtext\-section\-literals\fR, the literals
are interspersed in the text section in order to keep them as close as
@@ -21837,7 +21849,7 @@ every cross-file call, not just those that really are out of range.
.IX Subsection "zSeries Options"
.PP
These are listed under
-.SS "Options for Code Generation Conventions"
+.Sh "Options for Code Generation Conventions"
.IX Subsection "Options for Code Generation Conventions"
These machine-independent options control the interface conventions
used in code generation.
@@ -21976,7 +21988,7 @@ You normally do not need to enable this option; instead, a language processor
that needs this handling enables it on your behalf.
.IP "\fB\-fasynchronous\-unwind\-tables\fR" 4
.IX Item "-fasynchronous-unwind-tables"
-Generate unwind table in \s-1DWARF 2\s0 format, if supported by target machine. The
+Generate unwind table in \s-1DWARF\s0 2 format, if supported by target machine. The
table is exact at each instruction boundary, so it can be used for stack
unwinding from asynchronous events (such as debugger or garbage collector).
.IP "\fB\-fno\-gnu\-unique\fR" 4
@@ -22047,7 +22059,7 @@ Use it to conform to a non-default application binary interface.
.IX Item "-fshort-wchar"
Override the underlying type for \f(CW\*(C`wchar_t\*(C'\fR to be \f(CW\*(C`short
unsigned int\*(C'\fR instead of the default for the target. This option is
-useful for building programs to run under \s-1WINE.\s0
+useful for building programs to run under \s-1WINE\s0.
.Sp
\&\fBWarning:\fR the \fB\-fshort\-wchar\fR switch causes \s-1GCC\s0 to generate
code that is not binary compatible with code generated without that switch.
@@ -22060,7 +22072,7 @@ such variables in different compilation units by placing the variables
in a common block.
This is the behavior specified by \fB\-fcommon\fR, and is the default
for \s-1GCC\s0 on most targets.
-On the other hand, this behavior is not required by \s-1ISO C,\s0 and on some
+On the other hand, this behavior is not required by \s-1ISO\s0 C, and on some
targets may carry a speed or code size penalty on variable references.
The \fB\-fno\-common\fR option specifies that the compiler should place
uninitialized global variables in the data section of the object file,
@@ -22116,11 +22128,11 @@ the \s-1GOT\s0 size for the linked executable exceeds a machine-specific
maximum size, you get an error message from the linker indicating that
\&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR
instead. (These maximums are 8k on the \s-1SPARC\s0 and 32k
-on the m68k and \s-1RS/6000. \s0 The x86 has no such limit.)
+on the m68k and \s-1RS/6000\s0. The x86 has no such limit.)
.Sp
Position-independent code requires special support, and therefore works
only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V
-but not for the Sun 386i. Code generated for the \s-1IBM RS/6000\s0 is always
+but not for the Sun 386i. Code generated for the \s-1IBM\s0 \s-1RS/6000\s0 is always
position-independent.
.Sp
When this flag is set, the macros \f(CW\*(C`_\|_pic_\|_\*(C'\fR and \f(CW\*(C`_\|_PIC_\|_\*(C'\fR
@@ -22130,7 +22142,7 @@ are defined to 1.
If supported for the target machine, emit position-independent code,
suitable for dynamic linking and avoiding any limit on the size of the
global offset table. This option makes a difference on the m68k,
-PowerPC and \s-1SPARC.\s0
+PowerPC and \s-1SPARC\s0.
.Sp
Position-independent code requires special support, and therefore works
only on certain machines.
@@ -22280,7 +22292,7 @@ name, such as \f(CW\*(C`vector<int> blah(const vector<int> &)\*(C'\fR, not the
internal mangled name (e.g., \f(CW\*(C`_Z4blahRSt6vectorIiSaIiEE\*(C'\fR). The
match is done on substrings: if the \fIsym\fR parameter is a substring
of the function name, it is considered to be a match. For C99 and \*(C+
-extended identifiers, the function name must be given in \s-1UTF\-8,\s0 not
+extended identifiers, the function name must be given in \s-1UTF\-8\s0, not
using universal character names.
.IP "\fB\-fstack\-check\fR" 4
.IX Item "-fstack-check"
@@ -22419,7 +22431,7 @@ always specify visibility when it is not the default; i.e., declarations
only for use within the local \s-1DSO\s0 should \fBalways\fR be marked explicitly
as hidden as so to avoid \s-1PLT\s0 indirection overheads\-\-\-making this
abundantly clear also aids readability and self-documentation of the code.
-Note that due to \s-1ISO \*(C+\s0 specification requirements, \f(CW\*(C`operator new\*(C'\fR and
+Note that due to \s-1ISO\s0 \*(C+ specification requirements, \f(CW\*(C`operator new\*(C'\fR and
\&\f(CW\*(C`operator delete\*(C'\fR must always be of default visibility.
.Sp
Be aware that headers from outside your project, in particular system
@@ -22431,7 +22443,7 @@ before including any such headers.
\&\f(CW\*(C`extern\*(C'\fR declarations are not affected by \fB\-fvisibility\fR, so
a lot of code can be recompiled with \fB\-fvisibility=hidden\fR with
no modifications. However, this means that calls to \f(CW\*(C`extern\*(C'\fR
-functions with no explicit visibility use the \s-1PLT,\s0 so it is more
+functions with no explicit visibility use the \s-1PLT\s0, so it is more
effective to use \f(CW\*(C`_\|_attribute ((visibility))\*(C'\fR and/or
\&\f(CW\*(C`#pragma GCC visibility\*(C'\fR to tell the compiler which \f(CW\*(C`extern\*(C'\fR
declarations should be treated as hidden.
@@ -22493,7 +22505,7 @@ aspects of the compilation environment.
Note that you can also specify places to search using options such as
\&\fB\-B\fR, \fB\-I\fR and \fB\-L\fR. These
take precedence over places specified using environment variables, which
-in turn take precedence over those specified by the configuration of \s-1GCC.\s0
+in turn take precedence over those specified by the configuration of \s-1GCC\s0.
.IP "\fB\s-1LANG\s0\fR" 4
.IX Item "LANG"
.PD 0
@@ -22510,7 +22522,7 @@ national conventions. \s-1GCC\s0 inspects the locale categories
\&\fB\s-1LC_CTYPE\s0\fR and \fB\s-1LC_MESSAGES\s0\fR if it has been configured to do
so. These locale categories can be set to any value supported by your
installation. A typical value is \fBen_GB.UTF\-8\fR for English in the United
-Kingdom encoded in \s-1UTF\-8.\s0
+Kingdom encoded in \s-1UTF\-8\s0.
.Sp
The \fB\s-1LC_CTYPE\s0\fR environment variable specifies character
classification. \s-1GCC\s0 uses it to determine the character boundaries in
@@ -22690,7 +22702,7 @@ and the Info entries for \fIgcc\fR, \fIcpp\fR, \fIas\fR,
.IX Header "AUTHOR"
See the Info entry for \fBgcc\fR, or
<\fBhttp://gcc.gnu.org/onlinedocs/gcc/Contributors.html\fR>,
-for contributors to \s-1GCC.\s0
+for contributors to \s-1GCC\s0.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright (c) 1988\-2015 Free Software Foundation, Inc.
diff --git a/gcc/doc/gc-analyze.1 b/gcc/doc/gc-analyze.1
index 55fe084790..db833c8c20 100644
--- a/gcc/doc/gc-analyze.1
+++ b/gcc/doc/gc-analyze.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GC-ANALYZE 1"
-.TH GC-ANALYZE 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GC-ANALYZE 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/gcc.1 b/gcc/doc/gcc.1
index dcd7f1481d..c56451f7a4 100644
--- a/gcc/doc/gcc.1
+++ b/gcc/doc/gcc.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCC 1"
-.TH GCC 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCC 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -154,7 +153,7 @@ Only the most useful options are listed here; see below for the
remainder. \fBg++\fR accepts mostly the same options as \fBgcc\fR.
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-When you invoke \s-1GCC,\s0 it normally does preprocessing, compilation,
+When you invoke \s-1GCC\s0, it normally does preprocessing, compilation,
assembly and linking. The \*(L"overall options\*(R" allow you to stop this
process at an intermediate stage. For example, the \fB\-c\fR option
says not to run the linker. Then the output consists of object files
@@ -189,7 +188,7 @@ these have both positive and negative forms; the negative form of
only one of these two forms, whichever one is not the default.
.SH "OPTIONS"
.IX Header "OPTIONS"
-.SS "Option Summary"
+.Sh "Option Summary"
.IX Subsection "Option Summary"
Here is a summary of all the options, grouped by type. Explanations are
in the following sections.
@@ -532,6 +531,7 @@ in the following sections.
\&\-momit\-leaf\-frame\-pointer \-mno\-omit\-leaf\-frame\-pointer
\&\-mtls\-dialect=desc \-mtls\-dialect=traditional
\&\-mfix\-cortex\-a53\-835769 \-mno\-fix\-cortex\-a53\-835769
+\&\-mfix\-cortex\-a53\-843419 \-mno\-fix\-cortex\-a53\-843419
\&\-march=\fR\fIname\fR \fB\-mcpu=\fR\fIname\fR \fB\-mtune=\fR\fIname\fR
.Sp
\&\fIAdapteva Epiphany Options\fR
@@ -1096,7 +1096,7 @@ See \s-1RS/6000\s0 and PowerPC Options.
\&\-maes \-mpclmul \-mfsgsbase \-mrdrnd \-mf16c \-mfma \-mprefetchwt1
\&\-mclflushopt \-mxsavec \-mxsaves
\&\-msse4a \-m3dnow \-mpopcnt \-mabm \-mbmi \-mtbm \-mfma4 \-mxop \-mlzcnt
-\&\-mbmi2 \-mfxsr \-mxsave \-mxsaveopt \-mrtm \-mlwp \-mmpx \-mthreads
+\&\-mbmi2 \-mfxsr \-mxsave \-mxsaveopt \-mrtm \-mlwp \-mmpx \-mmwaitx \-mthreads
\&\-mno\-align\-stringops \-minline\-all\-stringops
\&\-minline\-stringops\-dynamically \-mstringop\-strategy=\fR\fIalg\fR
\&\fB\-mmemcpy\-strategy=\fR\fIstrategy\fR \fB\-mmemset\-strategy=\fR\fIstrategy\fR
@@ -1155,7 +1155,7 @@ See S/390 and zSeries Options.
\&\fB\-ftrapv \-fwrapv \-fbounds\-check
\&\-fvisibility=\fR[\fBdefault\fR|\fBinternal\fR|\fBhidden\fR|\fBprotected\fR]
\&\fB\-fstrict\-volatile\-bitfields \-fsync\-libcalls\fR
-.SS "Options Controlling the Kind of Output"
+.Sh "Options Controlling the Kind of Output"
.IX Subsection "Options Controlling the Kind of Output"
Compilation can involve up to four stages: preprocessing, compilation
proper, assembly and linking, always in that order. \s-1GCC\s0 is capable of
@@ -1459,7 +1459,7 @@ option.
.IX Item "language"
Display the options supported for \fIlanguage\fR, where
\&\fIlanguage\fR is the name of one of the languages supported in this
-version of \s-1GCC.\s0
+version of \s-1GCC\s0.
.IP "\fBcommon\fR" 4
.IX Item "common"
Display the options that are common to all languages.
@@ -1556,7 +1556,7 @@ or \fB/./\fR, or make the path absolute when generating a relative
prefix.
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
-Display the version number and copyrights of the invoked \s-1GCC.\s0
+Display the version number and copyrights of the invoked \s-1GCC\s0.
.IP "\fB\-wrapper\fR" 4
.IX Item "-wrapper"
Invoke all subcommands under a wrapper program. The name of the
@@ -1578,7 +1578,7 @@ the shared object file is used to identify the plugin for the
purposes of argument parsing (See
\&\fB\-fplugin\-arg\-\fR\fIname\fR\fB\-\fR\fIkey\fR\fB=\fR\fIvalue\fR below).
Each plugin should define the callback functions specified in the
-Plugins \s-1API.\s0
+Plugins \s-1API\s0.
.IP "\fB\-fplugin\-arg\-\fR\fIname\fR\fB\-\fR\fIkey\fR\fB=\fR\fIvalue\fR" 4
.IX Item "-fplugin-arg-name-key=value"
Define an argument called \fIkey\fR with a value of \fIvalue\fR
@@ -1610,8 +1610,8 @@ option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
with a backslash. The \fIfile\fR may itself contain additional
@\fIfile\fR options; any such options will be processed recursively.
-.SS "Compiling \*(C+ Programs"
-.IX Subsection "Compiling Programs"
+.Sh "Compiling \*(C+ Programs"
+.IX Subsection "Compiling Programs"
\&\*(C+ source files conventionally use one of the suffixes \fB.C\fR,
\&\fB.cc\fR, \fB.cpp\fR, \fB.CPP\fR, \fB.c++\fR, \fB.cp\fR, or
\&\fB.cxx\fR; \*(C+ header files often use \fB.hh\fR, \fB.hpp\fR,
@@ -1634,7 +1634,7 @@ When you compile \*(C+ programs, you may specify many of the same
command-line options that you use for compiling programs in any
language; or command-line options meaningful for C and related
languages; or options that are meaningful only for \*(C+ programs.
-.SS "Options Controlling C Dialect"
+.Sh "Options Controlling C Dialect"
.IX Subsection "Options Controlling C Dialect"
The following options control the dialect of C (or languages derived
from C, such as \*(C+, Objective-C and Objective\-\*(C+) that the compiler
@@ -1644,8 +1644,8 @@ accepts:
In C mode, this is equivalent to \fB\-std=c90\fR. In \*(C+ mode, it is
equivalent to \fB\-std=c++98\fR.
.Sp
-This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO
-C90 \s0(when compiling C code), or of standard \*(C+ (when compiling \*(C+ code),
+This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO\s0
+C90 (when compiling C code), or of standard \*(C+ (when compiling \*(C+ code),
such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and
predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the
type of system you are using. It also enables the undesirable and
@@ -1655,7 +1655,7 @@ the \f(CW\*(C`inline\*(C'\fR keyword.
.Sp
The alternate keywords \f(CW\*(C`_\|_asm_\|_\*(C'\fR, \f(CW\*(C`_\|_extension_\|_\*(C'\fR,
\&\f(CW\*(C`_\|_inline_\|_\*(C'\fR and \f(CW\*(C`_\|_typeof_\|_\*(C'\fR continue to work despite
-\&\fB\-ansi\fR. You would not want to use them in an \s-1ISO C\s0 program, of
+\&\fB\-ansi\fR. You would not want to use them in an \s-1ISO\s0 C program, of
course, but it is useful to put them in header files that might be included
in compilations done with \fB\-ansi\fR. Alternate predefined macros
such as \f(CW\*(C`_\|_unix_\|_\*(C'\fR and \f(CW\*(C`_\|_vax_\|_\*(C'\fR are also available, with or
@@ -1672,7 +1672,7 @@ from declaring certain functions or defining certain macros that the
programs that might use these names for other things.
.Sp
Functions that are normally built in but do not have semantics
-defined by \s-1ISO C \s0(such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in
+defined by \s-1ISO\s0 C (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in
functions when \fB\-ansi\fR is used.
.IP "\fB\-std=\fR" 4
.IX Item "-std="
@@ -1685,9 +1685,9 @@ The compiler can accept several base standards, such as \fBc90\fR or
compiler accepts all programs following that standard plus those
using \s-1GNU\s0 extensions that do not contradict it. For example,
\&\fB\-std=c90\fR turns off certain features of \s-1GCC\s0 that are
-incompatible with \s-1ISO C90,\s0 such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR
+incompatible with \s-1ISO\s0 C90, such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR
keywords, but not other \s-1GNU\s0 extensions that do not have a meaning in
-\&\s-1ISO C90,\s0 such as omitting the middle term of a \f(CW\*(C`?:\*(C'\fR
+\&\s-1ISO\s0 C90, such as omitting the middle term of a \f(CW\*(C`?:\*(C'\fR
expression. On the other hand, when a \s-1GNU\s0 dialect of a standard is
specified, all features supported by the compiler are enabled, even when
those features change the meaning of the base standard. As a result, some
@@ -1707,11 +1707,11 @@ A value for this option must be provided; possible values are
.IP "\fBiso9899:1990\fR" 4
.IX Item "iso9899:1990"
.PD
-Support all \s-1ISO C90\s0 programs (certain \s-1GNU\s0 extensions that conflict
-with \s-1ISO C90\s0 are disabled). Same as \fB\-ansi\fR for C code.
+Support all \s-1ISO\s0 C90 programs (certain \s-1GNU\s0 extensions that conflict
+with \s-1ISO\s0 C90 are disabled). Same as \fB\-ansi\fR for C code.
.IP "\fBiso9899:199409\fR" 4
.IX Item "iso9899:199409"
-\&\s-1ISO C90\s0 as modified in amendment 1.
+\&\s-1ISO\s0 C90 as modified in amendment 1.
.IP "\fBc99\fR" 4
.IX Item "c99"
.PD 0
@@ -1722,7 +1722,7 @@ with \s-1ISO C90\s0 are disabled). Same as \fB\-ansi\fR for C code.
.IP "\fBiso9899:199x\fR" 4
.IX Item "iso9899:199x"
.PD
-\&\s-1ISO C99. \s0 This standard is substantially completely supported, modulo
+\&\s-1ISO\s0 C99. This standard is substantially completely supported, modulo
bugs and floating-point issues
(mainly but not entirely relating to optional C99 features from
Annexes F and G). See
@@ -1736,7 +1736,7 @@ names \fBc9x\fR and \fBiso9899:199x\fR are deprecated.
.IP "\fBiso9899:2011\fR" 4
.IX Item "iso9899:2011"
.PD
-\&\s-1ISO C11,\s0 the 2011 revision of the \s-1ISO C\s0 standard. This standard is
+\&\s-1ISO\s0 C11, the 2011 revision of the \s-1ISO\s0 C standard. This standard is
substantially completely supported, modulo bugs, floating-point issues
(mainly but not entirely relating to optional C11 features from
Annexes F and G) and the optional Annexes K (Bounds-checking
@@ -1747,21 +1747,21 @@ interfaces) and L (Analyzability). The name \fBc1x\fR is deprecated.
.IP "\fBgnu89\fR" 4
.IX Item "gnu89"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C90 \s0(including some C99 features).
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C90 (including some C99 features).
.IP "\fBgnu99\fR" 4
.IX Item "gnu99"
.PD 0
.IP "\fBgnu9x\fR" 4
.IX Item "gnu9x"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C99. \s0 The name \fBgnu9x\fR is deprecated.
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C99. The name \fBgnu9x\fR is deprecated.
.IP "\fBgnu11\fR" 4
.IX Item "gnu11"
.PD 0
.IP "\fBgnu1x\fR" 4
.IX Item "gnu1x"
.PD
-\&\s-1GNU\s0 dialect of \s-1ISO C11. \s0 This is the default for C code.
+\&\s-1GNU\s0 dialect of \s-1ISO\s0 C11. This is the default for C code.
The name \fBgnu1x\fR is deprecated.
.IP "\fBc++98\fR" 4
.IX Item "c++98"
@@ -1769,7 +1769,7 @@ The name \fBgnu1x\fR is deprecated.
.IP "\fBc++03\fR" 4
.IX Item "c++03"
.PD
-The 1998 \s-1ISO \*(C+\s0 standard plus the 2003 technical corrigendum and some
+The 1998 \s-1ISO\s0 \*(C+ standard plus the 2003 technical corrigendum and some
additional defect reports. Same as \fB\-ansi\fR for \*(C+ code.
.IP "\fBgnu++98\fR" 4
.IX Item "gnu++98"
@@ -1785,7 +1785,7 @@ additional defect reports. Same as \fB\-ansi\fR for \*(C+ code.
.IP "\fBc++0x\fR" 4
.IX Item "c++0x"
.PD
-The 2011 \s-1ISO \*(C+\s0 standard plus amendments.
+The 2011 \s-1ISO\s0 \*(C+ standard plus amendments.
The name \fBc++0x\fR is deprecated.
.IP "\fBgnu++11\fR" 4
.IX Item "gnu++11"
@@ -1801,7 +1801,7 @@ The name \fBgnu++0x\fR is deprecated.
.IP "\fBc++1y\fR" 4
.IX Item "c++1y"
.PD
-The 2014 \s-1ISO \*(C+\s0 standard plus amendments.
+The 2014 \s-1ISO\s0 \*(C+ standard plus amendments.
The name \fBc++1y\fR is deprecated.
.IP "\fBgnu++14\fR" 4
.IX Item "gnu++14"
@@ -1813,7 +1813,7 @@ The name \fBc++1y\fR is deprecated.
The name \fBgnu++1y\fR is deprecated.
.IP "\fBc++1z\fR" 4
.IX Item "c++1z"
-The next revision of the \s-1ISO \*(C+\s0 standard, tentatively planned for
+The next revision of the \s-1ISO\s0 \*(C+ standard, tentatively planned for
2017. Support is highly experimental, and will almost certainly
change in incompatible ways in future releases.
.IP "\fBgnu++1z\fR" 4
@@ -1875,7 +1875,7 @@ In \*(C+, this switch only affects the \f(CW\*(C`typeof\*(C'\fR keyword, since
use the \fB\-fno\-gnu\-keywords\fR flag instead, which has the same
effect. In C99 mode (\fB\-std=c99\fR or \fB\-std=gnu99\fR), this
switch only affects the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, since
-\&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO C99.\s0
+\&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO\s0 C99.
.IP "\fB\-fno\-builtin\fR" 4
.IX Item "-fno-builtin"
.PD 0
@@ -1903,7 +1903,7 @@ known not to modify global memory.
With the \fB\-fno\-builtin\-\fR\fIfunction\fR option
only the built-in function \fIfunction\fR is
disabled. \fIfunction\fR must not begin with \fB_\|_builtin_\fR. If a
-function is named that is not built-in in this version of \s-1GCC,\s0 this
+function is named that is not built-in in this version of \s-1GCC\s0, this
option is ignored. There is no corresponding
\&\fB\-fbuiltin\-\fR\fIfunction\fR option; if you wish to enable
built-in functions selectively when using \fB\-fno\-builtin\fR or
@@ -1937,7 +1937,7 @@ implies \fB\-pthread\fR, and thus is only supported on targets that
have support for \fB\-pthread\fR.
.Sp
Note that this is an experimental feature, incomplete, and subject to
-change in future versions of \s-1GCC. \s0 See
+change in future versions of \s-1GCC\s0. See
<\fBhttps://gcc.gnu.org/wiki/OpenACC\fR> for more information.
.IP "\fB\-fopenmp\fR" 4
.IX Item "-fopenmp"
@@ -1969,7 +1969,7 @@ When the option \fB\-fgnu\-tm\fR is specified, the compiler
generates code for the Linux variant of Intel's current Transactional
Memory \s-1ABI\s0 specification document (Revision 1.1, May 6 2009). This is
an experimental feature whose interface may change in future versions
-of \s-1GCC,\s0 as the official specification changes. Please note that not
+of \s-1GCC\s0, as the official specification changes. Please note that not
all architectures are supported for this feature.
.Sp
For more information on \s-1GCC\s0's support for transactional memory,
@@ -2006,8 +2006,8 @@ fields declared using a typedef. This is only
supported for C, not \*(C+.
.IP "\fB\-trigraphs\fR" 4
.IX Item "-trigraphs"
-Support \s-1ISO C\s0 trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
-options for strict \s-1ISO C\s0 conformance) implies \fB\-trigraphs\fR.
+Support \s-1ISO\s0 C trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
+options for strict \s-1ISO\s0 C conformance) implies \fB\-trigraphs\fR.
.IP "\fB\-traditional\fR" 4
.IX Item "-traditional"
.PD 0
@@ -2016,8 +2016,8 @@ options for strict \s-1ISO C\s0 conformance) implies \fB\-trigraphs\fR.
.PD
Formerly, these options caused \s-1GCC\s0 to attempt to emulate a pre-standard
C compiler. They are now only supported with the \fB\-E\fR switch.
-The preprocessor continues to support a pre-standard mode. See the \s-1GNU
-CPP\s0 manual for details.
+The preprocessor continues to support a pre-standard mode. See the \s-1GNU\s0
+\&\s-1CPP\s0 manual for details.
.IP "\fB\-fcond\-mismatch\fR" 4
.IX Item "-fcond-mismatch"
Allow conditional expressions with mismatched types in the second and
@@ -2067,8 +2067,8 @@ These options control whether a bit-field is signed or unsigned, when the
declaration does not use either \f(CW\*(C`signed\*(C'\fR or \f(CW\*(C`unsigned\*(C'\fR. By
default, such a bit-field is signed, because this is consistent: the
basic integer types such as \f(CW\*(C`int\*(C'\fR are signed types.
-.SS "Options Controlling \*(C+ Dialect"
-.IX Subsection "Options Controlling Dialect"
+.Sh "Options Controlling \*(C+ Dialect"
+.IX Subsection "Options Controlling Dialect"
This section describes the command-line options that are only meaningful
for \*(C+ programs. You can also use most of the \s-1GNU\s0 compiler options
regardless of what language your program is in. For example, you
@@ -2080,12 +2080,12 @@ might compile a file \fIfirstClass.C\fR like this:
.PP
In this example, only \fB\-frepo\fR is an option meant
only for \*(C+ programs; you can use the other options with any
-language supported by \s-1GCC.\s0
+language supported by \s-1GCC\s0.
.PP
Here is a list of options that are \fIonly\fR for compiling \*(C+ programs:
.IP "\fB\-fabi\-version=\fR\fIn\fR" 4
.IX Item "-fabi-version=n"
-Use version \fIn\fR of the \*(C+ \s-1ABI. \s0 The default is version 0.
+Use version \fIn\fR of the \*(C+ \s-1ABI\s0. The default is version 0.
.Sp
Version 0 refers to the version conforming most closely to
the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0
@@ -2179,7 +2179,7 @@ Inject friend functions into the enclosing namespace, so that they are
visible outside the scope of the class in which they are declared.
Friend functions were documented to work this way in the old Annotated
\&\*(C+ Reference Manual.
-However, in \s-1ISO \*(C+\s0 a friend function that is not declared
+However, in \s-1ISO\s0 \*(C+ a friend function that is not declared
in an enclosing scope can only be found using argument dependent
lookup. \s-1GCC\s0 defaults to the standard behavior.
.Sp
@@ -2262,12 +2262,12 @@ controlled by \f(CW\*(C`#pragma implementation\*(C'\fR. This causes linker
errors if these functions are not inlined everywhere they are called.
.IP "\fB\-fms\-extensions\fR" 4
.IX Item "-fms-extensions"
-Disable Wpedantic warnings about constructs used in \s-1MFC,\s0 such as implicit
+Disable Wpedantic warnings about constructs used in \s-1MFC\s0, such as implicit
int and getting a pointer to member function via non-standard syntax.
.IP "\fB\-fno\-nonansi\-builtins\fR" 4
.IX Item "-fno-nonansi-builtins"
Disable built-in declarations of functions that are not mandated by
-\&\s-1ANSI/ISO C. \s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR,
+\&\s-1ANSI/ISO\s0 C. These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR,
\&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions.
.IP "\fB\-fnothrow\-opt\fR" 4
.IX Item "-fnothrow-opt"
@@ -2355,7 +2355,7 @@ warning or error to \fIn\fR. The default value is 10.
.IX Item "-ftemplate-depth=n"
Set the maximum instantiation depth for template classes to \fIn\fR.
A limit on the template instantiation depth is needed to detect
-endless recursions during template class instantiation. \s-1ANSI/ISO \*(C+\s0
+endless recursions during template class instantiation. \s-1ANSI/ISO\s0 \*(C+
conforming programs must not rely on a maximum depth greater than 17
(changed to 1024 in \*(C+11). The default value is 900, as the compiler
can run out of stack space before hitting 1024 in some situations.
@@ -2386,7 +2386,7 @@ are taken in different shared objects.
The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with
\&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not
appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection
-when used within the \s-1DSO. \s0 Enabling this option can have a dramatic effect
+when used within the \s-1DSO\s0. Enabling this option can have a dramatic effect
on load and link times of a \s-1DSO\s0 as it massively reduces the size of the
dynamic export table when the library makes heavy use of templates.
.Sp
@@ -2506,10 +2506,10 @@ is used when building the \*(C+ library.)
In addition, these optimization, warning, and code generation options
have meanings only for \*(C+ programs:
.IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4
-.IX Item "-Wabi (C, Objective-C, and Objective- only)"
+.IX Item "-Wabi (C, Objective-C, and Objective- only)"
When an explicit \fB\-fabi\-version=\fR\fIn\fR option is used, causes
G++ to warn when it generates code that is probably not compatible with the
-vendor-neutral \*(C+ \s-1ABI. \s0 Since G++ now defaults to
+vendor-neutral \*(C+ \s-1ABI\s0. Since G++ now defaults to
\&\fB\-fabi\-version=0\fR, \fB\-Wabi\fR has no effect unless either
an older \s-1ABI\s0 version is selected (with \fB\-fabi\-version=\fR\fIn\fR)
or an older compatibility version is selected (with
@@ -2532,7 +2532,7 @@ level, e.g. \fB\-Wabi=2\fR to warn about changes relative to
\&\fB\-fabi\-compat\-version=\fR\fIn\fR.
.Sp
The known incompatibilities in \fB\-fabi\-version=2\fR (which was the
-default from \s-1GCC 3.4\s0 to 4.9) include:
+default from \s-1GCC\s0 3.4 to 4.9) include:
.RS 4
.IP "*" 4
A template with a non-type template parameter of reference type was
@@ -2560,7 +2560,7 @@ These mangling issues were fixed in \fB\-fabi\-version=5\fR.
Scoped enumerators passed as arguments to a variadic function are
promoted like unscoped enumerators, causing \f(CW\*(C`va_arg\*(C'\fR to complain.
On most targets this does not actually affect the parameter passing
-\&\s-1ABI,\s0 as there is no way to pass an argument smaller than \f(CW\*(C`int\*(C'\fR.
+\&\s-1ABI\s0, as there is no way to pass an argument smaller than \f(CW\*(C`int\*(C'\fR.
.Sp
Also, the \s-1ABI\s0 changed the mangling of template argument packs,
\&\f(CW\*(C`const_cast\*(C'\fR, \f(CW\*(C`static_cast\*(C'\fR, prefix increment/decrement, and
@@ -2650,10 +2650,10 @@ Warn when a narrowing conversion prohibited by \*(C+11 occurs within
.Sp
This flag is included in \fB\-Wall\fR and \fB\-Wc++11\-compat\fR.
.Sp
-With \fB\-std=c++11\fR, \fB\-Wno\-narrowing\fR suppresses for
-non-constants the diagnostic required by the standard. Note that this
-does not affect the meaning of well-formed code; narrowing conversions
-are still considered ill-formed in \s-1SFINAE\s0 context.
+With \fB\-std=c++11\fR, \fB\-Wno\-narrowing\fR suppresses the diagnostic
+required by the standard. Note that this does not affect the meaning
+of well-formed code; narrowing conversions are still considered
+ill-formed in \s-1SFINAE\s0 context.
.IP "\fB\-Wnoexcept\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wnoexcept ( and Objective- only)"
Warn when a noexcept-expression evaluates to false because of a call
@@ -2693,7 +2693,7 @@ This is on by default for all pre\-\*(C+11 dialects and all \s-1GNU\s0 dialects:
\&\fB\-std=c++98\fR, \fB\-std=gnu++98\fR, \fB\-std=gnu++11\fR,
\&\fB\-std=gnu++14\fR.
This option is off by default
-for \s-1ISO \*(C+11\s0 onwards (\fB\-std=c++11\fR, ...).
+for \s-1ISO\s0 \*(C+11 onwards (\fB\-std=c++11\fR, ...).
.PP
The following \fB\-W...\fR options are not affected by \fB\-Wall\fR.
.IP "\fB\-Weffc++\fR (\*(C+ and Objective\-\*(C+ only)" 4
@@ -2789,7 +2789,7 @@ Warn when overload resolution chooses a promotion from unsigned or
enumerated type to a signed type, over a conversion to an unsigned type of
the same size. Previous versions of G++ tried to preserve
unsignedness, but the standard mandates the current behavior.
-.SS "Options Controlling Objective-C and Objective\-\*(C+ Dialects"
+.Sh "Options Controlling Objective-C and Objective\-\*(C+ Dialects"
.IX Subsection "Options Controlling Objective-C and Objective- Dialects"
(\s-1NOTE:\s0 This manual does not describe the Objective-C and Objective\-\*(C+
languages themselves.
@@ -2805,7 +2805,7 @@ For example, you might compile a file \fIsome_class.m\fR like this:
.PP
In this example, \fB\-fgnu\-runtime\fR is an option meant only for
Objective-C and Objective\-\*(C+ programs; you can use the other options with
-any language supported by \s-1GCC.\s0
+any language supported by \s-1GCC\s0.
.PP
Note that since Objective-C is an extension of the C language, Objective-C
compilations may also use options specific to the C front-end (e.g.,
@@ -2830,7 +2830,7 @@ runtime. This is the default for most types of systems.
.IP "\fB\-fnext\-runtime\fR" 4
.IX Item "-fnext-runtime"
Generate output compatible with the NeXT runtime. This is the default
-for NeXT-based systems, including Darwin and Mac \s-1OS X. \s0 The macro
+for NeXT-based systems, including Darwin and Mac \s-1OS\s0 X. The macro
\&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is
used.
.IP "\fB\-fno\-nil\-receivers\fR" 4
@@ -2847,7 +2847,7 @@ This option is currently supported only for the NeXT runtime. In that
case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for
properties and other Objective-C 2.0 additions. Version 1 is the
traditional (32\-bit) \s-1ABI\s0 with support for properties and other
-Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI. \s0 If
+Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI\s0. If
nothing is specified, the default is Version 0 on 32\-bit target
machines, and Version 2 on 64\-bit target machines.
.IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4
@@ -2871,7 +2871,7 @@ by the runtime immediately after a new object instance is allocated;
the \f(CW\*(C`\- (void) .cxx_destruct\*(C'\fR methods are invoked immediately
before the runtime deallocates an object instance.
.Sp
-As of this writing, only the NeXT runtime on Mac \s-1OS X 10.4\s0 and later has
+As of this writing, only the NeXT runtime on Mac \s-1OS\s0 X 10.4 and later has
support for invoking the \f(CW\*(C`\- (id) .cxx_construct\*(C'\fR and
\&\f(CW\*(C`\- (void) .cxx_destruct\*(C'\fR methods.
.IP "\fB\-fobjc\-direct\-dispatch\fR" 4
@@ -2886,7 +2886,7 @@ is required to use the Objective-C keywords \f(CW@try\fR,
\&\f(CW@throw\fR, \f(CW@catch\fR, \f(CW@finally\fR and
\&\f(CW@synchronized\fR. This option is available with both the \s-1GNU\s0
runtime and the NeXT runtime (but not available in conjunction with
-the NeXT runtime on Mac \s-1OS X 10.2\s0 and earlier).
+the NeXT runtime on Mac \s-1OS\s0 X 10.2 and earlier).
.IP "\fB\-fobjc\-gc\fR" 4
.IX Item "-fobjc-gc"
Enable garbage collection (\s-1GC\s0) in Objective-C and Objective\-\*(C+
@@ -2895,23 +2895,23 @@ programs. This option is only available with the NeXT runtime; the
does not require special compiler flags.
.IP "\fB\-fobjc\-nilcheck\fR" 4
.IX Item "-fobjc-nilcheck"
-For the NeXT runtime with version 2 of the \s-1ABI,\s0 check for a nil
+For the NeXT runtime with version 2 of the \s-1ABI\s0, check for a nil
receiver in method invocations before doing the actual method call.
This is the default and can be disabled using
\&\fB\-fno\-objc\-nilcheck\fR. Class methods and super calls are never
checked for nil in this way no matter what this flag is set to.
Currently this flag does nothing when the \s-1GNU\s0 runtime, or an older
-version of the NeXT runtime \s-1ABI,\s0 is used.
+version of the NeXT runtime \s-1ABI\s0, is used.
.IP "\fB\-fobjc\-std=objc1\fR" 4
.IX Item "-fobjc-std=objc1"
Conform to the language syntax of Objective-C 1.0, the language
-recognized by \s-1GCC 4.0. \s0 This only affects the Objective-C additions to
+recognized by \s-1GCC\s0 4.0. This only affects the Objective-C additions to
the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards,
which is controlled by the separate C/\*(C+ dialect option flags. When
this option is used with the Objective-C or Objective\-\*(C+ compiler,
-any Objective-C syntax that is not recognized by \s-1GCC 4.0\s0 is rejected.
+any Objective-C syntax that is not recognized by \s-1GCC\s0 4.0 is rejected.
This is useful if you need to make sure that your Objective-C code can
-be compiled with older versions of \s-1GCC.\s0
+be compiled with older versions of \s-1GCC\s0.
.IP "\fB\-freplace\-objc\-classes\fR" 4
.IX Item "-freplace-objc-classes"
Emit a special marker instructing \fB\f(BIld\fB\|(1)\fR not to statically link in
@@ -2920,7 +2920,7 @@ run time instead. This is used in conjunction with the Fix-and-Continue
debugging mode, where the object file in question may be recompiled and
dynamically reloaded in the course of program execution, without the need
to restart the program itself. Currently, Fix-and-Continue functionality
-is only available in conjunction with the NeXT runtime on Mac \s-1OS X 10.3\s0
+is only available in conjunction with the NeXT runtime on Mac \s-1OS\s0 X 10.3
and later.
.IP "\fB\-fzero\-link\fR" 4
.IX Item "-fzero-link"
@@ -2999,7 +2999,7 @@ that methods and selectors must be declared before being used.
.IX Item "-print-objc-runtime-info"
Generate C header describing the largest structure that is passed by
value, if any.
-.SS "Options to Control Diagnostic Messages Formatting"
+.Sh "Options to Control Diagnostic Messages Formatting"
.IX Subsection "Options to Control Diagnostic Messages Formatting"
Traditionally, diagnostic messages have been formatted irrespective of
the output device's aspect (e.g. its width, ...). You can use the
@@ -3121,14 +3121,14 @@ information. The source line is truncated to \fIn\fR characters, if
the \fB\-fmessage\-length=n\fR option is given. When the output is done
to the terminal, the width is limited to the width given by the
\&\fB\s-1COLUMNS\s0\fR environment variable or, if not set, to the terminal width.
-.SS "Options to Request or Suppress Warnings"
+.Sh "Options to Request or Suppress Warnings"
.IX Subsection "Options to Request or Suppress Warnings"
Warnings are diagnostic messages that report constructions that
are not inherently erroneous but that are risky or suggest there
may have been an error.
.PP
The following language-independent options do not enable specific
-warnings but control the kinds of diagnostics produced by \s-1GCC.\s0
+warnings but control the kinds of diagnostics produced by \s-1GCC\s0.
.IP "\fB\-fsyntax\-only\fR" 4
.IX Item "-fsyntax-only"
Check the code for syntax errors, but don't do anything beyond that.
@@ -3203,14 +3203,14 @@ warns that an unrecognized option is present.
.IP "\fB\-pedantic\fR" 4
.IX Item "-pedantic"
.PD
-Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0;
+Issue all the warnings demanded by strict \s-1ISO\s0 C and \s-1ISO\s0 \*(C+;
reject all programs that use forbidden extensions, and some other
-programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+. \s0 For \s-1ISO C,\s0 follows the
-version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used.
+programs that do not follow \s-1ISO\s0 C and \s-1ISO\s0 \*(C+. For \s-1ISO\s0 C, follows the
+version of the \s-1ISO\s0 C standard specified by any \fB\-std\fR option used.
.Sp
-Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without
+Valid \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ programs should compile properly with or without
this option (though a rare few require \fB\-ansi\fR or a
-\&\fB\-std\fR option specifying the required version of \s-1ISO C\s0). However,
+\&\fB\-std\fR option specifying the required version of \s-1ISO\s0 C). However,
without this option, certain \s-1GNU\s0 extensions and traditional C and \*(C+
features are supported as well. With this option, they are rejected.
.Sp
@@ -3220,24 +3220,24 @@ warnings are also disabled in the expression that follows
\&\f(CW\*(C`_\|_extension_\|_\*(C'\fR. However, only system header files should use
these escape routes; application programs should avoid them.
.Sp
-Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO
-C\s0 conformance. They soon find that it does not do quite what they want:
+Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO\s0
+C conformance. They soon find that it does not do quite what they want:
it finds some non-ISO practices, but not all\-\-\-only those for which
-\&\s-1ISO C \s0\fIrequires\fR a diagnostic, and some others for which
+\&\s-1ISO\s0 C \fIrequires\fR a diagnostic, and some others for which
diagnostics have been added.
.Sp
-A feature to report any failure to conform to \s-1ISO C\s0 might be useful in
+A feature to report any failure to conform to \s-1ISO\s0 C might be useful in
some instances, but would require considerable additional work and would
be quite different from \fB\-Wpedantic\fR. We don't have plans to
support such a feature in the near future.
.Sp
Where the standard specified with \fB\-std\fR represents a \s-1GNU\s0
extended dialect of C, such as \fBgnu90\fR or \fBgnu99\fR, there is a
-corresponding \fIbase standard\fR, the version of \s-1ISO C\s0 on which the \s-1GNU\s0
+corresponding \fIbase standard\fR, the version of \s-1ISO\s0 C on which the \s-1GNU\s0
extended dialect is based. Warnings from \fB\-Wpedantic\fR are given
where they are required by the base standard. (It does not make sense
-for such warnings to be given only for features not in the specified \s-1GNU
-C\s0 dialect, since by definition the \s-1GNU\s0 dialects of C include all
+for such warnings to be given only for features not in the specified \s-1GNU\s0
+C dialect, since by definition the \s-1GNU\s0 dialects of C include all
features the compiler supports with the given option, and there would be
nothing to warn about.)
.IP "\fB\-pedantic\-errors\fR" 4
@@ -3409,7 +3409,7 @@ functions without the attribute specified are disabled by
\&\fB\-ffreestanding\fR or \fB\-fno\-builtin\fR.
.Sp
The formats are checked against the format features supported by \s-1GNU\s0
-libc version 2.2. These include all \s-1ISO C90\s0 and C99 features, as well
+libc version 2.2. These include all \s-1ISO\s0 C90 and C99 features, as well
as features from the Single Unix Specification and some \s-1BSD\s0 and \s-1GNU\s0
extensions. Other library implementations may not support all these
features; \s-1GCC\s0 does not support warning about features that go beyond a
@@ -3525,12 +3525,12 @@ enabled by default and it is made into an error by
Same as \fB\-Wimplicit\-int\fR and \fB\-Wimplicit\-function\-declaration\fR.
This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wignored\-qualifiers\fR (C and \*(C+ only)" 4
-.IX Item "-Wignored-qualifiers (C and only)"
+.IX Item "-Wignored-qualifiers (C and only)"
Warn if the return type of a function has a type qualifier
-such as \f(CW\*(C`const\*(C'\fR. For \s-1ISO C\s0 such a type qualifier has no effect,
+such as \f(CW\*(C`const\*(C'\fR. For \s-1ISO\s0 C such a type qualifier has no effect,
since the value returned by a function is not an lvalue.
For \*(C+, the warning is only emitted for scalar types or \f(CW\*(C`void\*(C'\fR.
-\&\s-1ISO C\s0 prohibits qualified \f(CW\*(C`void\*(C'\fR return types on function
+\&\s-1ISO\s0 C prohibits qualified \f(CW\*(C`void\*(C'\fR return types on function
definitions, so such return types always receive a warning
even without this option.
.Sp
@@ -3717,9 +3717,9 @@ expression to a type other than \f(CW\*(C`bool\*(C'\fR. For example:
.Sp
This warning is enabled by default for C and \*(C+ programs.
.IP "\fB\-Wsync\-nand\fR (C and \*(C+ only)" 4
-.IX Item "-Wsync-nand (C and only)"
+.IX Item "-Wsync-nand (C and only)"
Warn when \f(CW\*(C`_\|_sync_fetch_and_nand\*(C'\fR and \f(CW\*(C`_\|_sync_nand_and_fetch\*(C'\fR
-built-in functions are used. These functions changed semantics in \s-1GCC 4.4.\s0
+built-in functions are used. These functions changed semantics in \s-1GCC\s0 4.4.
.IP "\fB\-Wtrigraphs\fR" 4
.IX Item "-Wtrigraphs"
Warn if any trigraphs are encountered that might change the meaning of
@@ -3756,7 +3756,7 @@ This warning is enabled by \fB\-Wall\fR.
.Sp
To suppress this warning use the \f(CW\*(C`unused\*(C'\fR attribute.
.IP "\fB\-Wunused\-local\-typedefs\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4
-.IX Item "-Wunused-local-typedefs (C, Objective-C, and Objective- only)"
+.IX Item "-Wunused-local-typedefs (C, Objective-C, and Objective- only)"
Warn when a typedef locally defined in a function is not used.
This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wunused\-parameter\fR" 4
@@ -3863,7 +3863,7 @@ This warning is enabled by \fB\-Wall\fR or \fB\-Wextra\fR.
.IP "\fB\-Wunknown\-pragmas\fR" 4
.IX Item "-Wunknown-pragmas"
Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by
-\&\s-1GCC. \s0 If this command-line option is used, warnings are even issued
+\&\s-1GCC\s0. If this command-line option is used, warnings are even issued
for unknown pragmas in system header files. This is not the case if
the warnings are only enabled by the \fB\-Wall\fR command-line option.
.IP "\fB\-Wno\-pragmas\fR" 4
@@ -4141,13 +4141,13 @@ probably mistaken.
.IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4
.IX Item "-Wtraditional (C and Objective-C only)"
Warn about certain constructs that behave differently in traditional and
-\&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C
+\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
equivalent, and/or problematic constructs that should be avoided.
.RS 4
.IP "*" 4
Macro parameters that appear within string literals in the macro body.
In traditional C macro replacement takes place within string literals,
-but in \s-1ISO C\s0 it does not.
+but in \s-1ISO\s0 C it does not.
.IP "*" 4
In traditional C, some preprocessor directives did not exist.
Traditional preprocessors only considered a line to be a directive
@@ -4202,9 +4202,9 @@ versa. The absence of these prototypes when compiling with traditional
C causes serious problems. This is a subset of the possible
conversion warnings; for the full set use \fB\-Wtraditional\-conversion\fR.
.IP "*" 4
-Use of \s-1ISO C\s0 style function definitions. This warning intentionally is
+Use of \s-1ISO\s0 C style function definitions. This warning intentionally is
\&\fInot\fR issued for prototype declarations or variadic functions
-because these \s-1ISO C\s0 features appear in your code when using
+because these \s-1ISO\s0 C features appear in your code when using
libiberty's traditional C compatibility macros, \f(CW\*(C`PARAMS\*(C'\fR and
\&\f(CW\*(C`VPARAMS\*(C'\fR. This warning is also bypassed for nested functions
because that feature is already a \s-1GCC\s0 extension and thus not relevant to
@@ -4222,8 +4222,8 @@ except when the same as the default promotion.
.IP "\fB\-Wdeclaration\-after\-statement\fR (C and Objective-C only)" 4
.IX Item "-Wdeclaration-after-statement (C and Objective-C only)"
Warn when a declaration is found after a statement in a block. This
-construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default
-allowed in \s-1GCC. \s0 It is not supported by \s-1ISO C90. \s0
+construct, known from \*(C+, was introduced with \s-1ISO\s0 C99 and is by default
+allowed in \s-1GCC\s0. It is not supported by \s-1ISO\s0 C90.
.IP "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive.
@@ -4305,7 +4305,7 @@ which depend on the \s-1MS\s0 runtime.
.IP "\fB\-Wpointer\-arith\fR" 4
.IX Item "-Wpointer-arith"
Warn about anything that depends on the \*(L"size of\*(R" a function type or
-of \f(CW\*(C`void\*(C'\fR. \s-1GNU C\s0 assigns these types a size of 1, for
+of \f(CW\*(C`void\*(C'\fR. \s-1GNU\s0 C assigns these types a size of 1, for
convenience in calculations with \f(CW\*(C`void *\*(C'\fR pointers and pointers
to functions. In \*(C+, warn also when an arithmetic operation involves
\&\f(CW\*(C`NULL\*(C'\fR. This warning is also enabled by \fB\-Wpedantic\fR.
@@ -4323,14 +4323,14 @@ For example, warn if a call to a function returning an integer type
is cast to a pointer type.
.IP "\fB\-Wc90\-c99\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc90-c99-compat (C and Objective-C only)"
-Warn about features not present in \s-1ISO C90,\s0 but present in \s-1ISO C99.\s0
+Warn about features not present in \s-1ISO\s0 C90, but present in \s-1ISO\s0 C99.
For instance, warn about use of variable length arrays, \f(CW\*(C`long long\*(C'\fR
type, \f(CW\*(C`bool\*(C'\fR type, compound literals, designated initializers, and so
on. This option is independent of the standards mode. Warnings are disabled
in the expression that follows \f(CW\*(C`_\|_extension_\|_\*(C'\fR.
.IP "\fB\-Wc99\-c11\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc99-c11-compat (C and Objective-C only)"
-Warn about features not present in \s-1ISO C99,\s0 but present in \s-1ISO C11.\s0
+Warn about features not present in \s-1ISO\s0 C99, but present in \s-1ISO\s0 C11.
For instance, warn about use of anonymous structures and unions,
\&\f(CW\*(C`_Atomic\*(C'\fR type qualifier, \f(CW\*(C`_Thread_local\*(C'\fR storage-class specifier,
\&\f(CW\*(C`_Alignas\*(C'\fR specifier, \f(CW\*(C`Alignof\*(C'\fR operator, \f(CW\*(C`_Generic\*(C'\fR keyword,
@@ -4338,19 +4338,19 @@ and so on. This option is independent of the standards mode. Warnings are
disabled in the expression that follows \f(CW\*(C`_\|_extension_\|_\*(C'\fR.
.IP "\fB\-Wc++\-compat\fR (C and Objective-C only)" 4
.IX Item "-Wc++-compat (C and Objective-C only)"
-Warn about \s-1ISO C\s0 constructs that are outside of the common subset of
-\&\s-1ISO C\s0 and \s-1ISO \*(C+,\s0 e.g. request for implicit conversion from
+Warn about \s-1ISO\s0 C constructs that are outside of the common subset of
+\&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+, e.g. request for implicit conversion from
\&\f(CW\*(C`void *\*(C'\fR to a pointer to non\-\f(CW\*(C`void\*(C'\fR type.
.IP "\fB\-Wc++11\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wc++11-compat ( and Objective- only)"
-Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0
-and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords
-in \s-1ISO \*(C+ 2011. \s0 This warning turns on \fB\-Wnarrowing\fR and is
+Warn about \*(C+ constructs whose meaning differs between \s-1ISO\s0 \*(C+ 1998
+and \s-1ISO\s0 \*(C+ 2011, e.g., identifiers in \s-1ISO\s0 \*(C+ 1998 that are keywords
+in \s-1ISO\s0 \*(C+ 2011. This warning turns on \fB\-Wnarrowing\fR and is
enabled by \fB\-Wall\fR.
.IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wc++14-compat ( and Objective- only)"
-Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0
-and \s-1ISO \*(C+ 2014. \s0 This warning is enabled by \fB\-Wall\fR.
+Warn about \*(C+ constructs whose meaning differs between \s-1ISO\s0 \*(C+ 2011
+and \s-1ISO\s0 \*(C+ 2014. This warning is enabled by \fB\-Wall\fR.
.IP "\fB\-Wcast\-qual\fR" 4
.IX Item "-Wcast-qual"
Warn whenever a pointer is cast so as to remove a type qualifier from
@@ -4653,26 +4653,26 @@ Usually they indicate a typo in the user's code, as they have
implementation-defined values, and should not be used in portable code.
.IP "\fB\-Wnormalized\fR[\fB=\fR<\fBnone\fR|\fBid\fR|\fBnfc\fR|\fBnfkc\fR>]" 4
.IX Item "-Wnormalized[=<none|id|nfc|nfkc>]"
-In \s-1ISO C\s0 and \s-1ISO \*(C+,\s0 two identifiers are different if they are
+In \s-1ISO\s0 C and \s-1ISO\s0 \*(C+, two identifiers are different if they are
different sequences of characters. However, sometimes when characters
outside the basic \s-1ASCII\s0 character set are used, you can have two
different character sequences that look the same. To avoid confusion,
-the \s-1ISO 10646\s0 standard sets out some \fInormalization rules\fR which
+the \s-1ISO\s0 10646 standard sets out some \fInormalization rules\fR which
when applied ensure that two sequences that look the same are turned into
the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that
have not been normalized; this option controls that warning.
.Sp
-There are four levels of warning supported by \s-1GCC. \s0 The default is
+There are four levels of warning supported by \s-1GCC\s0. The default is
\&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is
-not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
+not in the \s-1ISO\s0 10646 \*(L"C\*(R" normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
recommended form for most uses. It is equivalent to
\&\fB\-Wnormalized\fR.
.Sp
Unfortunately, there are some characters allowed in identifiers by
-\&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in
+\&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+ that, when turned into \s-1NFC\s0, are not allowed in
identifiers. That is, there's no way to use these symbols in portable
-\&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC.
-\&\s0\fB\-Wnormalized=id\fR suppresses the warning for these characters.
+\&\s-1ISO\s0 C or \*(C+ and have all your identifiers in \s-1NFC\s0.
+\&\fB\-Wnormalized=id\fR suppresses the warning for these characters.
It is hoped that future versions of the standards involved will correct
this, which is why this option is not the default.
.Sp
@@ -4682,11 +4682,11 @@ only do this if you are using some other normalization scheme (like
\&\*(L"D\*(R"), because otherwise you can easily create bugs that are
literally impossible to see.
.Sp
-Some characters in \s-1ISO 10646\s0 have distinct meanings but look identical
+Some characters in \s-1ISO\s0 10646 have distinct meanings but look identical
in some fonts or display methodologies, especially once formatting has
-been applied. For instance \f(CW\*(C`\eu207F\*(C'\fR, \*(L"\s-1SUPERSCRIPT LATIN SMALL
-LETTER N\*(R",\s0 displays just like a regular \f(CW\*(C`n\*(C'\fR that has been
-placed in a superscript. \s-1ISO 10646\s0 defines the \fI\s-1NFKC\s0\fR
+been applied. For instance \f(CW\*(C`\eu207F\*(C'\fR, \*(L"\s-1SUPERSCRIPT\s0 \s-1LATIN\s0 \s-1SMALL\s0
+\&\s-1LETTER\s0 N\*(R", displays just like a regular \f(CW\*(C`n\*(C'\fR that has been
+placed in a superscript. \s-1ISO\s0 10646 defines the \fI\s-1NFKC\s0\fR
normalization scheme to convert all these into a standard form as
well, and \s-1GCC\s0 warns if your code is not in \s-1NFKC\s0 if you use
\&\fB\-Wnormalized=nfkc\fR. This warning is comparable to warning
@@ -4744,9 +4744,9 @@ have the packed attribute:
.IP "\fB\-Wpacked\-bitfield\-compat\fR" 4
.IX Item "-Wpacked-bitfield-compat"
The 4.1, 4.2 and 4.3 series of \s-1GCC\s0 ignore the \f(CW\*(C`packed\*(C'\fR attribute
-on bit-fields of type \f(CW\*(C`char\*(C'\fR. This has been fixed in \s-1GCC 4.4\s0 but
+on bit-fields of type \f(CW\*(C`char\*(C'\fR. This has been fixed in \s-1GCC\s0 4.4 but
the change can lead to differences in the structure layout. \s-1GCC\s0
-informs you when the offset of such a field has changed in \s-1GCC 4.4.\s0
+informs you when the offset of such a field has changed in \s-1GCC\s0 4.4.
For example there is no longer a 4\-bit padding between field \f(CW\*(C`a\*(C'\fR
and \f(CW\*(C`b\*(C'\fR in this structure:
.Sp
@@ -4793,7 +4793,7 @@ warnings produced by \fB\-Winline\fR to appear or disappear.
.IP "\fB\-Wno\-invalid\-offsetof\fR (\*(C+ and Objective\-\*(C+ only)" 4
.IX Item "-Wno-invalid-offsetof ( and Objective- only)"
Suppress warnings from applying the \f(CW\*(C`offsetof\*(C'\fR macro to a non-POD
-type. According to the 2014 \s-1ISO \*(C+\s0 standard, applying \f(CW\*(C`offsetof\*(C'\fR
+type. According to the 2014 \s-1ISO\s0 \*(C+ standard, applying \f(CW\*(C`offsetof\*(C'\fR
to a non-standard-layout type is undefined. In existing \*(C+ implementations,
however, \f(CW\*(C`offsetof\*(C'\fR typically gives meaningful results.
This flag is for users who are aware that they are
@@ -4818,12 +4818,12 @@ the search path but can't be used.
.IP "\fB\-Wlong\-long\fR" 4
.IX Item "-Wlong-long"
Warn if \f(CW\*(C`long long\*(C'\fR type is used. This is enabled by either
-\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR in \s-1ISO C90\s0 and \*(C+98
+\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR in \s-1ISO\s0 C90 and \*(C+98
modes. To inhibit the warning messages, use \fB\-Wno\-long\-long\fR.
.IP "\fB\-Wvariadic\-macros\fR" 4
.IX Item "-Wvariadic-macros"
-Warn if variadic macros are used in \s-1ISO C90\s0 mode, or if the \s-1GNU\s0
-alternate syntax is used in \s-1ISO C99\s0 mode. This is enabled by either
+Warn if variadic macros are used in \s-1ISO\s0 C90 mode, or if the \s-1GNU\s0
+alternate syntax is used in \s-1ISO\s0 C99 mode. This is enabled by either
\&\fB\-Wpedantic\fR or \fB\-Wtraditional\fR. To inhibit the warning
messages, use \fB\-Wno\-variadic\-macros\fR.
.IP "\fB\-Wvarargs\fR" 4
@@ -4887,7 +4887,7 @@ standard's minimum limit, but very portable programs should avoid
using longer strings.
.Sp
The limit applies \fIafter\fR string constant concatenation, and does
-not count the trailing \s-1NUL. \s0 In C90, the limit was 509 characters; in
+not count the trailing \s-1NUL\s0. In C90, the limit was 509 characters; in
C99, it was raised to 4095. \*(C+98 does not specify a normative
minimum maximum, so we do not diagnose overlength strings in \*(C+.
.Sp
@@ -4905,14 +4905,14 @@ from the decimal floating-point extension to C99.
Suppress warnings when a positional initializer is used to initialize
a structure that has been marked with the \f(CW\*(C`designated_init\*(C'\fR
attribute.
-.SS "Options for Debugging Your Program or \s-1GCC\s0"
+.Sh "Options for Debugging Your Program or \s-1GCC\s0"
.IX Subsection "Options for Debugging Your Program or GCC"
\&\s-1GCC\s0 has various special options that are used for debugging
either your program or \s-1GCC:\s0
.IP "\fB\-g\fR" 4
.IX Item "-g"
Produce debugging information in the operating system's native format
-(stabs, \s-1COFF, XCOFF,\s0 or \s-1DWARF 2\s0). \s-1GDB\s0 can work with this debugging
+(stabs, \s-1COFF\s0, \s-1XCOFF\s0, or \s-1DWARF\s0 2). \s-1GDB\s0 can work with this debugging
information.
.Sp
On most systems that use stabs format, \fB\-g\fR enables use of extra
@@ -4945,8 +4945,8 @@ be useful, this option requires a debugger capable of reading .dwo
files.
.IP "\fB\-ggdb\fR" 4
.IX Item "-ggdb"
-Produce debugging information for use by \s-1GDB. \s0 This means to use the
-most expressive format available (\s-1DWARF 2,\s0 stabs, or the native format
+Produce debugging information for use by \s-1GDB\s0. This means to use the
+most expressive format available (\s-1DWARF\s0 2, stabs, or the native format
if neither of those are supported), including \s-1GDB\s0 extensions if at all
possible.
.IP "\fB\-gpubnames\fR" 4
@@ -4961,8 +4961,8 @@ with a linker that can produce \s-1GDB\s0 index version 7.
.IX Item "-gstabs"
Produce debugging information in stabs format (if that is supported),
without \s-1GDB\s0 extensions. This is the format used by \s-1DBX\s0 on most \s-1BSD\s0
-systems. On \s-1MIPS,\s0 Alpha and System V Release 4 systems this option
-produces stabs debugging output that is not understood by \s-1DBX\s0 or \s-1SDB.\s0
+systems. On \s-1MIPS\s0, Alpha and System V Release 4 systems this option
+produces stabs debugging output that is not understood by \s-1DBX\s0 or \s-1SDB\s0.
On System V Release 4 systems this option requires the \s-1GNU\s0 assembler.
.IP "\fB\-feliminate\-unused\-debug\-symbols\fR" 4
.IX Item "-feliminate-unused-debug-symbols"
@@ -4999,7 +4999,7 @@ System V Release 4.
.IP "\fB\-gxcoff\fR" 4
.IX Item "-gxcoff"
Produce debugging information in \s-1XCOFF\s0 format (if that is supported).
-This is the format used by the \s-1DBX\s0 debugger on \s-1IBM RS/6000\s0 systems.
+This is the format used by the \s-1DBX\s0 debugger on \s-1IBM\s0 \s-1RS/6000\s0 systems.
.IP "\fB\-gxcoff+\fR" 4
.IX Item "-gxcoff+"
Produce debugging information in \s-1XCOFF\s0 format (if that is supported),
@@ -5014,9 +5014,9 @@ The value of \fIversion\fR may be either 2, 3, 4 or 5; the default version
for most targets is 4. \s-1DWARF\s0 Version 5 is only experimental.
.Sp
Note that with \s-1DWARF\s0 Version 2, some ports require and always
-use some non-conflicting \s-1DWARF 3\s0 extensions in the unwind tables.
+use some non-conflicting \s-1DWARF\s0 3 extensions in the unwind tables.
.Sp
-Version 4 may require \s-1GDB 7.0\s0 and \fB\-fvar\-tracking\-assignments\fR
+Version 4 may require \s-1GDB\s0 7.0 and \fB\-fvar\-tracking\-assignments\fR
for maximum benefit.
.IP "\fB\-grecord\-gcc\-switches\fR" 4
.IX Item "-grecord-gcc-switches"
@@ -5089,7 +5089,7 @@ debug information in version 1 of the \s-1DWARF\s0 format (which is very
different from version 2), and it would have been too confusing. That
debug format is long obsolete, but the option cannot be changed now.
Instead use an additional \fB\-g\fR\fIlevel\fR option to change the
-debug level for \s-1DWARF.\s0
+debug level for \s-1DWARF\s0.
.IP "\fB\-gtoggle\fR" 4
.IX Item "-gtoggle"
Turn off generation of debug info, if leaving out this option
@@ -5141,7 +5141,7 @@ at runtime. Current suboptions are:
.IX Item "-fsanitize=shift"
This option enables checking that the result of a shift operation is
not undefined. Note that what exactly is considered undefined differs
-slightly between C and \*(C+, as well as between \s-1ISO C90\s0 and C99, etc.
+slightly between C and \*(C+, as well as between \s-1ISO\s0 C90 and C99, etc.
.IP "\fB\-fsanitize=integer\-divide\-by\-zero\fR" 4
.IX Item "-fsanitize=integer-divide-by-zero"
Detect integer division by zero as well as \f(CW\*(C`INT_MIN / \-1\*(C'\fR division.
@@ -5447,9 +5447,9 @@ When this option is passed to the compiler driver, it causes the
other than debugging the compiler proper.
.IP "\fB\-feliminate\-dwarf2\-dups\fR" 4
.IX Item "-feliminate-dwarf2-dups"
-Compress \s-1DWARF 2\s0 debugging information by eliminating duplicated
+Compress \s-1DWARF\s0 2 debugging information by eliminating duplicated
information about each symbol. This option only makes sense when
-generating \s-1DWARF 2\s0 debugging information with \fB\-gdwarf\-2\fR.
+generating \s-1DWARF\s0 2 debugging information with \fB\-gdwarf\-2\fR.
.IP "\fB\-femit\-struct\-debug\-baseonly\fR" 4
.IX Item "-femit-struct-debug-baseonly"
Emit debug information for struct-like types
@@ -5461,7 +5461,7 @@ but at significant potential loss in type information to the debugger.
See \fB\-femit\-struct\-debug\-reduced\fR for a less aggressive option.
See \fB\-femit\-struct\-debug\-detailed\fR for more detailed control.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-femit\-struct\-debug\-reduced\fR" 4
.IX Item "-femit-struct-debug-reduced"
Emit debug information for struct-like types
@@ -5474,7 +5474,7 @@ with some potential loss in type information to the debugger.
See \fB\-femit\-struct\-debug\-baseonly\fR for a more aggressive option.
See \fB\-femit\-struct\-debug\-detailed\fR for more detailed control.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-femit\-struct\-debug\-detailed\fR[\fB=\fR\fIspec-list\fR]" 4
.IX Item "-femit-struct-debug-detailed[=spec-list]"
Specify the struct-like types
@@ -5520,7 +5520,7 @@ You may need to experiment to determine the best settings for your application.
.Sp
The default is \fB\-femit\-struct\-debug\-detailed=all\fR.
.Sp
-This option works only with \s-1DWARF 2.\s0
+This option works only with \s-1DWARF\s0 2.
.IP "\fB\-fno\-merge\-debug\-strings\fR" 4
.IX Item "-fno-merge-debug-strings"
Direct the linker to not merge together strings in the debugging
@@ -5534,8 +5534,8 @@ When compiling files in directory \fI\fIold\fI\fR, record debugging
information describing them as in \fI\fInew\fI\fR instead.
.IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4
.IX Item "-fno-dwarf2-cfi-asm"
-Emit \s-1DWARF 2\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section
-instead of using \s-1GAS \s0\f(CW\*(C`.cfi_*\*(C'\fR directives.
+Emit \s-1DWARF\s0 2 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section
+instead of using \s-1GAS\s0 \f(CW\*(C`.cfi_*\*(C'\fR directives.
.IP "\fB\-p\fR" 4
.IX Item "-p"
Generate extra code to write profile information suitable for the
@@ -5692,7 +5692,7 @@ For example, with \fB\-fdbg\-cnt=dce:10,tail_call:0\fR,
.IX Item "-fdisable-kind-pass=range-list"
.PD
This is a set of options that are used to explicitly disable/enable
-optimization passes. These options are intended for use for debugging \s-1GCC.\s0
+optimization passes. These options are intended for use for debugging \s-1GCC\s0.
Compiler users should use regular options for enabling/disabling
passes instead.
.RS 4
@@ -6165,7 +6165,7 @@ by some other path.
When dumping pretty-printed trees, this option inhibits dumping the
bodies of control structures.
.Sp
-When dumping \s-1RTL,\s0 print the \s-1RTL\s0 in slim (condensed) form instead of
+When dumping \s-1RTL\s0, print the \s-1RTL\s0 in slim (condensed) form instead of
the default LISP-like representation.
.IP "\fBraw\fR" 4
.IX Item "raw"
@@ -6200,7 +6200,7 @@ Enable showing virtual operands for every statement.
Enable showing line numbers for statements.
.IP "\fBuid\fR" 4
.IX Item "uid"
-Enable showing the unique \s-1ID \s0(\f(CW\*(C`DECL_UID\*(C'\fR) for each variable.
+Enable showing the unique \s-1ID\s0 (\f(CW\*(C`DECL_UID\*(C'\fR) for each variable.
.IP "\fBverbose\fR" 4
.IX Item "verbose"
Enable showing the tree dump for each statement.
@@ -6278,7 +6278,7 @@ Dump aliasing information for each function. The file name is made by
appending \fI.alias\fR to the source file name.
.IP "\fBccp\fR" 4
.IX Item "ccp"
-Dump each function after \s-1CCP. \s0 The file name is made by appending
+Dump each function after \s-1CCP\s0. The file name is made by appending
\&\fI.ccp\fR to the source file name.
.IP "\fBstoreccp\fR" 4
.IX Item "storeccp"
@@ -6693,7 +6693,7 @@ Print the compiler's built-in specs\-\-\-and don't do anything else. (This
is used when \s-1GCC\s0 itself is being built.)
.IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4
.IX Item "-fno-eliminate-unused-debug-types"
-Normally, when producing \s-1DWARF 2\s0 output, \s-1GCC\s0 avoids producing debug symbol
+Normally, when producing \s-1DWARF\s0 2 output, \s-1GCC\s0 avoids producing debug symbol
output for types that are nowhere used in the source file being compiled.
Sometimes it is useful to have \s-1GCC\s0 emit debugging
information for all types declared in a compilation
@@ -6702,7 +6702,7 @@ in that compilation unit, for example
if, in the debugger, you want to cast a value to a type that is
not actually used in your program (but is declared). More often,
however, this results in a significant amount of wasted space.
-.SS "Options That Control Optimization"
+.Sh "Options That Control Optimization"
.IX Subsection "Options That Control Optimization"
These options control various sorts of optimizations.
.PP
@@ -6898,7 +6898,7 @@ function calls and pops them all at once.
Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR.
.IP "\fB\-fforward\-propagate\fR" 4
.IX Item "-fforward-propagate"
-Perform a forward propagation pass on \s-1RTL. \s0 The pass tries to combine two
+Perform a forward propagation pass on \s-1RTL\s0. The pass tries to combine two
instructions and checks if the result can be simplified. If loop unrolling
is active, two passes are performed and the second is scheduled after
loop unrolling.
@@ -6924,7 +6924,7 @@ restore frame pointers; it also makes an extra register available
in many functions. \fBIt also makes debugging impossible on
some machines.\fR
.Sp
-On some machines, such as the \s-1VAX,\s0 this flag has no effect, because
+On some machines, such as the \s-1VAX\s0, this flag has no effect, because
the standard calling sequence automatically handles the frame pointer
and nothing is saved by pretending it doesn't exist. The
machine-description macro \f(CW\*(C`FRAME_POINTER_REQUIRED\*(C'\fR controls
@@ -7049,7 +7049,7 @@ attribute or declspec
In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR
into the object file, even if the function has been inlined into all
of its callers. This switch does not affect functions using the
-\&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90. \s0 In \*(C+, emit any and all
+\&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU\s0 C90. In \*(C+, emit any and all
inline functions into the object file.
.IP "\fB\-fkeep\-static\-consts\fR" 4
.IX Item "-fkeep-static-consts"
@@ -7116,7 +7116,7 @@ The default is \fB\-ffunction\-cse\fR
.IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4
.IX Item "-fno-zero-initialized-in-bss"
If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that
-are initialized to zero into \s-1BSS. \s0 This can save space in the resulting
+are initialized to zero into \s-1BSS\s0. This can save space in the resulting
code.
.Sp
This option turns off this behavior because some programs explicitly
@@ -7239,11 +7239,11 @@ instructions to support this. Enabled by default at \fB\-O\fR and
higher on architectures that support this.
.IP "\fB\-fdce\fR" 4
.IX Item "-fdce"
-Perform dead code elimination (\s-1DCE\s0) on \s-1RTL.\s0
+Perform dead code elimination (\s-1DCE\s0) on \s-1RTL\s0.
Enabled by default at \fB\-O\fR and higher.
.IP "\fB\-fdse\fR" 4
.IX Item "-fdse"
-Perform dead store elimination (\s-1DSE\s0) on \s-1RTL.\s0
+Perform dead store elimination (\s-1DSE\s0) on \s-1RTL\s0.
Enabled by default at \fB\-O\fR and higher.
.IP "\fB\-fif\-conversion\fR" 4
.IX Item "-fif-conversion"
@@ -7403,7 +7403,7 @@ The default value is 5. If the value \fIn\fR is greater or equal to 10,
the dump output is sent to stderr using the same format as \fIn\fR minus 10.
.IP "\fB\-flra\-remat\fR" 4
.IX Item "-flra-remat"
-Enable CFG-sensitive rematerialization in \s-1LRA. \s0 Instead of loading
+Enable CFG-sensitive rematerialization in \s-1LRA\s0. Instead of loading
values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate)
values if it is profitable.
.Sp
@@ -7562,9 +7562,9 @@ When pipelining loops during selective scheduling, also pipeline outer loops.
This option has no effect unless \fB\-fsel\-sched\-pipelining\fR is turned on.
.IP "\fB\-fsemantic\-interposition\fR" 4
.IX Item "-fsemantic-interposition"
-Some object formats, like \s-1ELF,\s0 allow interposing of symbols by the
+Some object formats, like \s-1ELF\s0, allow interposing of symbols by the
dynamic linker.
-This means that for symbols exported from the \s-1DSO,\s0 the compiler cannot perform
+This means that for symbols exported from the \s-1DSO\s0, the compiler cannot perform
interprocedural propagation, inlining and other optimizations in anticipation
that the function or variable in question may change. While this feature is
useful, for example, to rewrite memory allocation functions by a debugging
@@ -7634,7 +7634,7 @@ at \fB\-O\fR and higher.
Perform full redundancy elimination (\s-1FRE\s0) on trees. The difference
between \s-1FRE\s0 and \s-1PRE\s0 is that \s-1FRE\s0 only considers expressions
that are computed on all paths leading to the redundant computation.
-This analysis is faster than \s-1PRE,\s0 though it exposes fewer redundancies.
+This analysis is faster than \s-1PRE\s0, though it exposes fewer redundancies.
This flag is enabled by default at \fB\-O\fR and higher.
.IP "\fB\-ftree\-phiprop\fR" 4
.IX Item "-ftree-phiprop"
@@ -7705,7 +7705,7 @@ The optimization reduces code size and may disturb unwind stacks by replacing
a function by equivalent one with a different name. The optimization works
more effectively with link time optimization enabled.
.Sp
-Nevertheless the behavior is similar to Gold Linker \s-1ICF\s0 optimization, \s-1GCC ICF\s0
+Nevertheless the behavior is similar to Gold Linker \s-1ICF\s0 optimization, \s-1GCC\s0 \s-1ICF\s0
works on different levels and thus the optimizations are not same \- there are
equivalences that are found only by \s-1GCC\s0 and equivalences found only by Gold.
.Sp
@@ -7740,7 +7740,7 @@ pass only operates on local scalar variables and is enabled by default
at \fB\-O\fR and higher.
.IP "\fB\-fssa\-phiopt\fR" 4
.IX Item "-fssa-phiopt"
-Perform pattern matching on \s-1SSA PHI\s0 nodes to optimize conditional
+Perform pattern matching on \s-1SSA\s0 \s-1PHI\s0 nodes to optimize conditional
code. This pass is enabled by default at \fB\-O\fR and higher.
.IP "\fB\-ftree\-switch\-conversion\fR" 4
.IX Item "-ftree-switch-conversion"
@@ -7896,8 +7896,8 @@ to enable the Graphite loop transformation infrastructure.
Enable the identity transformation for graphite. For every SCoP we generate
the polyhedral representation and transform it back to gimple. Using
\&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the
-\&\s-1GIMPLE \-\s0> \s-1GRAPHITE \-\s0> \s-1GIMPLE\s0 transformation. Some minimal optimizations
-are also performed by the code generator \s-1ISL,\s0 like index splitting and
+\&\s-1GIMPLE\s0 \-> \s-1GRAPHITE\s0 \-> \s-1GIMPLE\s0 transformation. Some minimal optimizations
+are also performed by the code generator \s-1ISL\s0, like index splitting and
dead code elimination in loops.
.IP "\fB\-floop\-nest\-optimize\fR" 4
.IX Item "-floop-nest-optimize"
@@ -8402,7 +8402,7 @@ targets.
Constructs webs as commonly used for register allocation purposes and assign
each web individual pseudo register. This allows the register allocation pass
to operate on pseudos directly, but also strengthens several other optimization
-passes, such as \s-1CSE,\s0 loop optimizer and trivial dead code remover. It can,
+passes, such as \s-1CSE\s0, loop optimizer and trivial dead code remover. It can,
however, make debugging impossible, since variables no longer stay in a
\&\*(L"home register\*(R".
.Sp
@@ -8420,7 +8420,7 @@ information.
.IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4
.IX Item "-flto[=n]"
This option runs the standard link-time optimizer. When invoked
-with source code, it generates \s-1GIMPLE \s0(one of \s-1GCC\s0's internal
+with source code, it generates \s-1GIMPLE\s0 (one of \s-1GCC\s0's internal
representations) and writes it to special \s-1ELF\s0 sections in the object
file. When the object files are linked together, all the function
bodies are read from these \s-1ELF\s0 sections and instantiated as if they
@@ -8545,7 +8545,7 @@ link time.
.Sp
If \s-1LTO\s0 encounters objects with C linkage declared with incompatible
types in separate translation units to be linked together (undefined
-behavior according to \s-1ISO C99 6.2.7\s0), a non-fatal diagnostic may be
+behavior according to \s-1ISO\s0 C99 6.2.7), a non-fatal diagnostic may be
issued. The behavior is still undefined at run time. Similar
diagnostics may be raised for other languages.
.Sp
@@ -8568,7 +8568,7 @@ regular (non-LTO) compilation.
If object files containing \s-1GIMPLE\s0 bytecode are stored in a library archive, say
\&\fIlibfoo.a\fR, it is possible to extract and use them in an \s-1LTO\s0 link if you
are using a linker with plugin support. To create static libraries suitable
-for \s-1LTO,\s0 use \fBgcc-ar\fR and \fBgcc-ranlib\fR instead of \fBar\fR
+for \s-1LTO\s0, use \fBgcc-ar\fR and \fBgcc-ranlib\fR instead of \fBar\fR
and \fBranlib\fR;
to show the symbols of object files with \s-1GIMPLE\s0 bytecode, use
\&\fBgcc-nm\fR. Those commands require that \fBar\fR, \fBranlib\fR
@@ -8603,7 +8603,7 @@ The current implementation of \s-1LTO\s0 makes no
attempt to generate bytecode that is portable between different
types of hosts. The bytecode files are versioned and there is a
strict version check, so bytecode files generated in one version of
-\&\s-1GCC\s0 do not work with an older or newer version of \s-1GCC.\s0
+\&\s-1GCC\s0 do not work with an older or newer version of \s-1GCC\s0.
.Sp
Link-time optimization does not work well with generation of debugging
information. Combining \fB\-flto\fR with
@@ -8686,8 +8686,8 @@ and the object code. This makes them usable for both \s-1LTO\s0 linking and norm
linking. This option is effective only when compiling with \fB\-flto\fR
and is ignored at link time.
.Sp
-\&\fB\-fno\-fat\-lto\-objects\fR improves compilation time over plain \s-1LTO,\s0 but
-requires the complete toolchain to be aware of \s-1LTO.\s0 It requires a linker with
+\&\fB\-fno\-fat\-lto\-objects\fR improves compilation time over plain \s-1LTO\s0, but
+requires the complete toolchain to be aware of \s-1LTO\s0. It requires a linker with
linker plugin support for basic functionality. Additionally,
\&\fBnm\fR, \fBar\fR and \fBranlib\fR
need to support linker plugins to allow a full-featured build environment
@@ -8796,7 +8796,7 @@ E.g.
.Ve
.Sp
Then use the \fBcreate_gcov\fR tool to convert the raw profile data
-to a format that can be used by \s-1GCC. \s0 You must also supply the
+to a format that can be used by \s-1GCC\s0. You must also supply the
unstripped binary for your program to this tool.
See <\fBhttps://github.com/google/autofdo\fR>.
.Sp
@@ -8826,15 +8826,15 @@ them to store all pertinent intermediate computations into variables.
.IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4
.IX Item "-fexcess-precision=style"
This option allows further control over excess precision on machines
-where floating-point registers have more precision than the \s-1IEEE
-\&\s0\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not
+where floating-point registers have more precision than the \s-1IEEE\s0
+\&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not
support operations rounding to those types. By default,
\&\fB\-fexcess\-precision=fast\fR is in effect; this means that
operations are carried out in the precision of the registers and that
it is unpredictable when rounding to the types specified in the source
code takes place. When compiling C, if
\&\fB\-fexcess\-precision=standard\fR is specified then excess
-precision follows the rules specified in \s-1ISO C99\s0; in particular,
+precision follows the rules specified in \s-1ISO\s0 C99; in particular,
both casts and assignments cause values to be rounded to their
semantic types (whereas \fB\-ffloat\-store\fR only affects
assignments). This option is enabled by default for C if a strict
@@ -8898,7 +8898,7 @@ The default is \fB\-fno\-unsafe\-math\-optimizations\fR.
.IP "\fB\-fassociative\-math\fR" 4
.IX Item "-fassociative-math"
Allow re-association of operands in series of floating-point operations.
-This violates the \s-1ISO C\s0 and \*(C+ language standard by possibly changing
+This violates the \s-1ISO\s0 C and \*(C+ language standard by possibly changing
computation result. \s-1NOTE:\s0 re-ordering may change the sign of zero as
well as ignore NaNs and inhibit or create underflow or overflow (and
thus cannot be used on code that relies on rounding behavior like
@@ -9001,8 +9001,8 @@ whether the result of a complex multiplication or division is \f(CW\*(C`NaN
default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by
\&\fB\-ffast\-math\fR.
.Sp
-This option controls the default setting of the \s-1ISO C99
-\&\s0\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to
+This option controls the default setting of the \s-1ISO\s0 C99
+\&\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to
all languages.
.IP "\fB\-fcx\-fortran\-rules\fR" 4
.IX Item "-fcx-fortran-rules"
@@ -9273,7 +9273,7 @@ optimization is not done.
.IP "\fBmax-gcse-insertion-ratio\fR" 4
.IX Item "max-gcse-insertion-ratio"
If the ratio of expression insertions to deletions is larger than this value
-for any expression, then \s-1RTL PRE\s0 inserts or removes the expression and thus
+for any expression, then \s-1RTL\s0 \s-1PRE\s0 inserts or removes the expression and thus
leaves partially redundant computations in the instruction stream. The default value is 20.
.IP "\fBmax-pending-list-length\fR" 4
.IX Item "max-pending-list-length"
@@ -9288,7 +9288,7 @@ when modulo scheduling a loop. Larger values can exponentially increase
compilation time.
.IP "\fBmax-inline-insns-single\fR" 4
.IX Item "max-inline-insns-single"
-Several parameters control the tree inliner used in \s-1GCC.\s0
+Several parameters control the tree inliner used in \s-1GCC\s0.
This number sets the maximum number of instructions (counted in \s-1GCC\s0's
internal representation) in a single function that the tree inliner
considers for inlining. This only affects functions declared
@@ -9644,7 +9644,7 @@ Tuning this may improve compilation speed; it has no effect on code
generation.
.Sp
The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when
-\&\s-1RAM \s0>= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is
+\&\s-1RAM\s0 >= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\s0\*(R" is
the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If
\&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower
bound of 30% is used. Setting this parameter and
@@ -9659,7 +9659,7 @@ by \fBggc-min-expand\fR% beyond \fBggc-min-heapsize\fR. Again,
tuning this may improve compilation speed, and has no effect on code
generation.
.Sp
-The default is the smaller of \s-1RAM/8, RLIMIT_RSS,\s0 or a limit that
+The default is the smaller of \s-1RAM/8\s0, \s-1RLIMIT_RSS\s0, or a limit that
tries to ensure that \s-1RLIMIT_DATA\s0 or \s-1RLIMIT_AS\s0 are not exceeded, but
with a lower bound of 4096 (four megabytes) and an upper bound of
131072 (128 megabytes). If \s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a
@@ -9884,7 +9884,7 @@ This value is the best found from numerous experiments.
This optimization is called inheritance. \s-1EBB\s0 is used as a region to
do this optimization. The parameter defines a minimal fall-through
edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in
-\&\s-1LRA. \s0 The default value of the parameter is 40. The value was chosen
+\&\s-1LRA\s0. The default value of the parameter is 40. The value was chosen
from numerous runs of \s-1SPEC2000\s0 on x86\-64.
.IP "\fBloop-invariant-max-bbs-in-loop\fR" 4
.IX Item "loop-invariant-max-bbs-in-loop"
@@ -10026,7 +10026,7 @@ The number of partitions should exceed the number of CPUs used for compilation.
The default value is 32.
.IP "\fBlto-minpartition\fR" 4
.IX Item "lto-minpartition"
-Size of minimal partition for \s-1WHOPR \s0(in estimated instructions).
+Size of minimal partition for \s-1WHOPR\s0 (in estimated instructions).
This prevents expenses of splitting very small programs into too many
partitions.
.IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4
@@ -10138,7 +10138,7 @@ automaton. The default is 50.
.RE
.RS 4
.RE
-.SS "Options Controlling the Preprocessor"
+.Sh "Options Controlling the Preprocessor"
.IX Subsection "Options Controlling the Preprocessor"
These options control the C preprocessor, which is run on each C source
file before actual compilation.
@@ -10262,7 +10262,7 @@ get trigraph conversion without warnings, but get the other
.IP "\fB\-Wtraditional\fR" 4
.IX Item "-Wtraditional"
Warn about certain constructs that behave differently in traditional and
-\&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C
+\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
equivalent, and problematic constructs which should be avoided.
.IP "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
@@ -10315,7 +10315,7 @@ in finding bugs in your own code, therefore suppressed. If you are
responsible for the system library, you may want to see them.
.IP "\fB\-w\fR" 4
.IX Item "-w"
-Suppress all warnings, including those which \s-1GNU CPP\s0 issues by default.
+Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default.
.IP "\fB\-pedantic\fR" 4
.IX Item "-pedantic"
Issue all the mandatory diagnostics listed in the C standard. Some of
@@ -10455,10 +10455,10 @@ This option allows use of a precompiled header together with \fB\-E\fR. It inse
\&\f(CW\*(C`#pragma GCC pch_preprocess "\f(CIfilename\f(CW"\*(C'\fR in the output to mark
the place where the precompiled header was found, and its \fIfilename\fR.
When \fB\-fpreprocessed\fR is in use, \s-1GCC\s0 recognizes this \f(CW\*(C`#pragma\*(C'\fR
-and loads the \s-1PCH.\s0
+and loads the \s-1PCH\s0.
.Sp
This option is off by default, because the resulting preprocessed output
-is only really suitable as input to \s-1GCC. \s0 It is switched on by
+is only really suitable as input to \s-1GCC\s0. It is switched on by
\&\fB\-save\-temps\fR.
.Sp
You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is
@@ -10511,7 +10511,7 @@ may be one of:
.el .IP "\f(CWiso9899:1990\fR" 4
.IX Item "iso9899:1990"
.PD
-The \s-1ISO C\s0 standard from 1990. \fBc90\fR is the customary shorthand for
+The \s-1ISO\s0 C standard from 1990. \fBc90\fR is the customary shorthand for
this version of the standard.
.Sp
The \fB\-ansi\fR option is equivalent to \fB\-std=c90\fR.
@@ -10533,7 +10533,7 @@ The 1990 C standard, as amended in 1994.
.el .IP "\f(CWc9x\fR" 4
.IX Item "c9x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 1999. Before
+The revised \s-1ISO\s0 C standard, published in December 1999. Before
publication, this was known as C9X.
.ie n .IP """iso9899:2011""" 4
.el .IP "\f(CWiso9899:2011\fR" 4
@@ -10546,7 +10546,7 @@ publication, this was known as C9X.
.el .IP "\f(CWc1x\fR" 4
.IX Item "c1x"
.PD
-The revised \s-1ISO C\s0 standard, published in December 2011. Before
+The revised \s-1ISO\s0 C standard, published in December 2011. Before
publication, this was known as C1X.
.ie n .IP """gnu90""" 4
.el .IP "\f(CWgnu90\fR" 4
@@ -10578,7 +10578,7 @@ The 2011 C standard plus \s-1GNU\s0 extensions.
.ie n .IP """c++98""" 4
.el .IP "\f(CWc++98\fR" 4
.IX Item "c++98"
-The 1998 \s-1ISO \*(C+\s0 standard plus amendments.
+The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
.ie n .IP """gnu++98""" 4
.el .IP "\f(CWgnu++98\fR" 4
.IX Item "gnu++98"
@@ -10730,7 +10730,7 @@ line. If the value is less than 1 or greater than 100, the option is
ignored. The default is 8.
.IP "\fB\-fdebug\-cpp\fR" 4
.IX Item "-fdebug-cpp"
-This option is only useful for debugging \s-1GCC. \s0 When used with
+This option is only useful for debugging \s-1GCC\s0. When used with
\&\fB\-E\fR, dumps debugging information about location maps. Every
token in the output is preceded by the dump of the map its location
belongs to. The dump of the map holding the location of a token would
@@ -10763,12 +10763,12 @@ Note that \f(CW\*(C`\-ftrack\-macro\-expansion=2\*(C'\fR is activated by default
.IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fexec-charset=charset"
Set the execution character set, used for string and character
-constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding
+constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
.IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4
.IX Item "-fwide-exec-charset=charset"
Set the wide execution character set, used for wide string and
-character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16,\s0 whichever
+character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever
corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with
\&\fB\-fexec\-charset\fR, \fIcharset\fR can be any encoding supported
by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have
@@ -10776,9 +10776,9 @@ problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR.
.IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4
.IX Item "-finput-charset=charset"
Set the input character set, used for translation from the character
-set of the input file to the source character set used by \s-1GCC. \s0 If the
+set of the input file to the source character set used by \s-1GCC\s0. If the
locale does not specify, or \s-1GCC\s0 cannot get this information from the
-locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale
+locale, the default is \s-1UTF\-8\s0. This can be overridden by either the locale
or this command-line option. Currently the command-line option takes
precedence if there's a conflict. \fIcharset\fR can be any encoding
supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
@@ -10815,7 +10815,7 @@ Cancel an assertion with the predicate \fIpredicate\fR and answer
.IX Item "-dCHARS"
\&\fI\s-1CHARS\s0\fR is a sequence of one or more of the following characters,
and must not be preceded by a space. Other characters are interpreted
-by the compiler proper, or reserved for future versions of \s-1GCC,\s0 and so
+by the compiler proper, or reserved for future versions of \s-1GCC\s0, and so
are silently ignored. If you specify characters whose behavior
conflicts, the result is undefined.
.RS 4
@@ -10891,12 +10891,12 @@ The \fB\-CC\fR option is generally used to support lint comments.
.IP "\fB\-traditional\-cpp\fR" 4
.IX Item "-traditional-cpp"
Try to imitate the behavior of old-fashioned C preprocessors, as
-opposed to \s-1ISO C\s0 preprocessors.
+opposed to \s-1ISO\s0 C preprocessors.
.IP "\fB\-trigraphs\fR" 4
.IX Item "-trigraphs"
Process trigraph sequences.
These are three-character sequences, all starting with \fB??\fR, that
-are defined by \s-1ISO C\s0 to stand for single characters. For example,
+are defined by \s-1ISO\s0 C to stand for single characters. For example,
\&\fB??/\fR stands for \fB\e\fR, so \fB'??/n'\fR is a character
constant for a newline. By default, \s-1GCC\s0 ignores trigraphs, but in
standard-conforming modes it converts them. See the \fB\-std\fR and
@@ -10922,7 +10922,7 @@ Print text describing all the command-line options instead of
preprocessing anything.
.IP "\fB\-v\fR" 4
.IX Item "-v"
-Verbose mode. Print out \s-1GNU CPP\s0's version number at the beginning of
+Verbose mode. Print out \s-1GNU\s0 \s-1CPP\s0's version number at the beginning of
execution, and report the final form of the include path.
.IP "\fB\-H\fR" 4
.IX Item "-H"
@@ -10937,9 +10937,9 @@ header file is printed with \fB...x\fR and a valid one with \fB...!\fR .
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
.PD
-Print out \s-1GNU CPP\s0's version number. With one dash, proceed to
+Print out \s-1GNU\s0 \s-1CPP\s0's version number. With one dash, proceed to
preprocess as normal. With two dashes, exit immediately.
-.SS "Passing Options to the Assembler"
+.Sh "Passing Options to the Assembler"
.IX Subsection "Passing Options to the Assembler"
You can pass options to the assembler.
.IP "\fB\-Wa,\fR\fIoption\fR" 4
@@ -10954,7 +10954,7 @@ recognize.
.Sp
If you want to pass an option that takes an argument, you must use
\&\fB\-Xassembler\fR twice, once for the option and once for the argument.
-.SS "Options for Linking"
+.Sh "Options for Linking"
.IX Subsection "Options for Linking"
These options come into play when the compiler links object files into
an executable output file. They are meaningless if the compiler is
@@ -11241,7 +11241,7 @@ different symbols to force loading of additional library modules.
\&\fB\-z\fR is passed directly on to the linker along with the keyword
\&\fIkeyword\fR. See the section in the documentation of your linker for
permitted values and their meanings.
-.SS "Options for Directory Search"
+.Sh "Options for Directory Search"
.IX Subsection "Options for Directory Search"
These options specify directories to search for header files, for
libraries and for parts of the compiler:
@@ -11377,13 +11377,13 @@ by default, but it is often satisfactory.
\&\fB\-I\-\fR does not inhibit the use of the standard system directories
for header files. Thus, \fB\-I\-\fR and \fB\-nostdinc\fR are
independent.
-.SS "Specifying Target Machine and Compiler Version"
+.Sh "Specifying Target Machine and Compiler Version"
.IX Subsection "Specifying Target Machine and Compiler Version"
The usual way to run \s-1GCC\s0 is to run the executable called \fBgcc\fR, or
\&\fImachine\fR\fB\-gcc\fR when cross-compiling, or
\&\fImachine\fR\fB\-gcc\-\fR\fIversion\fR to run a version other than the
one that was installed last.
-.SS "Hardware Models and Configurations"
+.Sh "Hardware Models and Configurations"
.IX Subsection "Hardware Models and Configurations"
Each target machine types can have its own
special options, starting with \fB\-m\fR, to choose among various
@@ -11409,7 +11409,7 @@ but long int and pointer are 64\-bit.
.Sp
The default depends on the specific target configuration. Note that
the \s-1LP64\s0 and \s-1ILP32\s0 ABIs are not link-compatible; you must compile your
-entire program with the same \s-1ABI,\s0 and link with a compatible set of libraries.
+entire program with the same \s-1ABI\s0, and link with a compatible set of libraries.
.IP "\fB\-mbig\-endian\fR" 4
.IX Item "-mbig-endian"
Generate big-endian code. This is the default when \s-1GCC\s0 is configured for an
@@ -11465,6 +11465,15 @@ of \s-1TLS\s0 variables.
Enable or disable the workaround for the \s-1ARM\s0 Cortex\-A53 erratum number 835769.
This involves inserting a \s-1NOP\s0 instruction between memory instructions and
64\-bit integer multiply-accumulate instructions.
+.IP "\fB\-mfix\-cortex\-a53\-843419\fR" 4
+.IX Item "-mfix-cortex-a53-843419"
+.PD 0
+.IP "\fB\-mno\-fix\-cortex\-a53\-843419\fR" 4
+.IX Item "-mno-fix-cortex-a53-843419"
+.PD
+Enable or disable the workaround for the \s-1ARM\s0 Cortex\-A53 erratum number 843419.
+This erratum workaround is made at link time and this will only pass the
+corresponding flag to the linker.
.IP "\fB\-march=\fR\fIname\fR" 4
.IX Item "-march=name"
Specify the name of the target architecture, optionally suffixed by one or
@@ -11636,7 +11645,7 @@ This is the mode used for floating-point calculations with
round-to-nearest-or-even rounding mode.
.IP "\fBint\fR" 4
.IX Item "int"
-This is the mode used to perform integer calculations in the \s-1FPU,\s0 e.g.
+This is the mode used to perform integer calculations in the \s-1FPU\s0, e.g.
integer multiply, or integer multiply-and-accumulate.
.RE
.RS 4
@@ -11698,13 +11707,13 @@ values for \fIcpu\fR are
.RS 4
.IP "\fB\s-1ARC600\s0\fR" 4
.IX Item "ARC600"
-Compile for \s-1ARC600. \s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR.
+Compile for \s-1ARC600\s0. Aliases: \fB\-mA6\fR, \fB\-mARC600\fR.
.IP "\fB\s-1ARC601\s0\fR" 4
.IX Item "ARC601"
-Compile for \s-1ARC601. \s0 Alias: \fB\-mARC601\fR.
+Compile for \s-1ARC601\s0. Alias: \fB\-mARC601\fR.
.IP "\fB\s-1ARC700\s0\fR" 4
.IX Item "ARC700"
-Compile for \s-1ARC700. \s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR.
+Compile for \s-1ARC700\s0. Aliases: \fB\-mA7\fR, \fB\-mARC700\fR.
This is the default when configured with \fB\-\-with\-cpu=arc700\fR.
.RE
.RS 4
@@ -11731,7 +11740,7 @@ Generate Extended arithmetic instructions. Currently only
supported. This is always enabled for \fB\-mcpu=ARC700\fR.
.IP "\fB\-mno\-mpy\fR" 4
.IX Item "-mno-mpy"
-Do not generate mpy instructions for \s-1ARC700.\s0
+Do not generate mpy instructions for \s-1ARC700\s0.
.IP "\fB\-mmul32x16\fR" 4
.IX Item "-mmul32x16"
Generate 32x16 bit multiply and mac instructions.
@@ -11756,7 +11765,7 @@ implementation.
implementation.
.IP "\fB\-msimd\fR" 4
.IX Item "-msimd"
-Enable generation of \s-1ARC SIMD\s0 instructions via target-specific
+Enable generation of \s-1ARC\s0 \s-1SIMD\s0 instructions via target-specific
builtins. Only valid for \fB\-mcpu=ARC700\fR.
.IP "\fB\-msoft\-float\fR" 4
.IX Item "-msoft-float"
@@ -11923,7 +11932,7 @@ optimizers then assume that indexed stores exist, which is not
the case.
.IP "\fB\-mlra\fR" 4
.IX Item "-mlra"
-Enable Local Register Allocation. This is still experimental for \s-1ARC,\s0
+Enable Local Register Allocation. This is still experimental for \s-1ARC\s0,
so by default the compiler uses standard reload
(i.e. \fB\-mno\-lra\fR).
.IP "\fB\-mlra\-priority\-none\fR" 4
@@ -12029,7 +12038,7 @@ The following options are maintained for backward compatibility, but
are now deprecated and will be removed in a future release:
.IP "\fB\-margonaut\fR" 4
.IX Item "-margonaut"
-Obsolete \s-1FPX.\s0
+Obsolete \s-1FPX\s0.
.IP "\fB\-mbig\-endian\fR" 4
.IX Item "-mbig-endian"
.PD 0
@@ -12092,7 +12101,7 @@ Replaced by \fB\-mmultcost\fR.
These \fB\-m\fR options are defined for the \s-1ARM\s0 port:
.IP "\fB\-mabi=\fR\fIname\fR" 4
.IX Item "-mabi=name"
-Generate code for the specified \s-1ABI. \s0 Permissible values are: \fBapcs-gnu\fR,
+Generate code for the specified \s-1ABI\s0. Permissible values are: \fBapcs-gnu\fR,
\&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR.
.IP "\fB\-mapcs\-frame\fR" 4
.IX Item "-mapcs-frame"
@@ -12136,7 +12145,7 @@ and uses FPU-specific calling conventions.
.Sp
The default depends on the specific target configuration. Note that
the hard-float and soft-float ABIs are not link-compatible; you must
-compile your entire program with the same \s-1ABI,\s0 and link with a
+compile your entire program with the same \s-1ABI\s0, and link with a
compatible set of libraries.
.IP "\fB\-mlittle\-endian\fR" 4
.IX Item "-mlittle-endian"
@@ -12266,7 +12275,7 @@ If the selected floating-point hardware includes the \s-1NEON\s0 extension
(e.g. \fB\-mfpu\fR=\fBneon\fR), note that floating-point
operations are not generated by \s-1GCC\s0's auto-vectorization pass unless
\&\fB\-funsafe\-math\-optimizations\fR is also specified. This is
-because \s-1NEON\s0 hardware does not fully implement the \s-1IEEE 754\s0 standard for
+because \s-1NEON\s0 hardware does not fully implement the \s-1IEEE\s0 754 standard for
floating-point arithmetic (in particular denormal values are treated as
zero), so the use of \s-1NEON\s0 instructions may lead to a loss of precision.
.IP "\fB\-mfp16\-format=\fR\fIname\fR" 4
@@ -12339,7 +12348,7 @@ otherwise the default is \fBR10\fR.
.IX Item "-mpic-data-is-text-relative"
Assume that each data segments are relative to text segment at load time.
Therefore, it permits addressing data using PC-relative operations.
-This option is on by default for targets other than VxWorks \s-1RTP.\s0
+This option is on by default for targets other than VxWorks \s-1RTP\s0.
.IP "\fB\-mpoke\-function\-name\fR" 4
.IX Item "-mpoke-function-name"
Write the name of each function into the text section, directly
@@ -12463,7 +12472,7 @@ off by default.
Assume inline assembler is using unified asm syntax. The default is
currently off which implies divided syntax. Currently this option is
available only for Thumb1 and has no effect on \s-1ARM\s0 state and Thumb2.
-However, this may change in future releases of \s-1GCC. \s0 Divided syntax
+However, this may change in future releases of \s-1GCC\s0. Divided syntax
should be considered deprecated.
.IP "\fB\-mrestrict\-it\fR" 4
.IX Item "-mrestrict-it"
@@ -12532,37 +12541,37 @@ The default for this option is@tie{}\fBavr2\fR.
.ie n .IP """avr6""" 4
.el .IP "\f(CWavr6\fR" 4
.IX Item "avr6"
-\&\*(L"Enhanced\*(R" devices with 3\-byte \s-1PC,\s0 i.e. with more than 128@tie{}KiB of program memory.
+\&\*(L"Enhanced\*(R" devices with 3\-byte \s-1PC\s0, i.e. with more than 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atmega256rfr2\*(C'\fR, \f(CW\*(C`atmega2560\*(C'\fR, \f(CW\*(C`atmega2561\*(C'\fR, \f(CW\*(C`atmega2564rfr2\*(C'\fR.
.ie n .IP """avrxmega2""" 4
.el .IP "\f(CWavrxmega2\fR" 4
.IX Item "avrxmega2"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 8@tie{}KiB and up to 64@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 8@tie{}KiB and up to 64@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega16a4\*(C'\fR, \f(CW\*(C`atxmega16a4u\*(C'\fR, \f(CW\*(C`atxmega16c4\*(C'\fR, \f(CW\*(C`atxmega16d4\*(C'\fR, \f(CW\*(C`atxmega16e5\*(C'\fR, \f(CW\*(C`atxmega32a4\*(C'\fR, \f(CW\*(C`atxmega32a4u\*(C'\fR, \f(CW\*(C`atxmega32c3\*(C'\fR, \f(CW\*(C`atxmega32c4\*(C'\fR, \f(CW\*(C`atxmega32d3\*(C'\fR, \f(CW\*(C`atxmega32d4\*(C'\fR, \f(CW\*(C`atxmega32e5\*(C'\fR, \f(CW\*(C`atxmega8e5\*(C'\fR.
.ie n .IP """avrxmega4""" 4
.el .IP "\f(CWavrxmega4\fR" 4
.IX Item "avrxmega4"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a3\*(C'\fR, \f(CW\*(C`atxmega64a3u\*(C'\fR, \f(CW\*(C`atxmega64a4u\*(C'\fR, \f(CW\*(C`atxmega64b1\*(C'\fR, \f(CW\*(C`atxmega64b3\*(C'\fR, \f(CW\*(C`atxmega64c3\*(C'\fR, \f(CW\*(C`atxmega64d3\*(C'\fR, \f(CW\*(C`atxmega64d4\*(C'\fR.
.ie n .IP """avrxmega5""" 4
.el .IP "\f(CWavrxmega5\fR" 4
.IX Item "avrxmega5"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.
-\&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM\s0.
+\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR.
.ie n .IP """avrxmega6""" 4
.el .IP "\f(CWavrxmega6\fR" 4
.IX Item "avrxmega6"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 128@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a3\*(C'\fR, \f(CW\*(C`atxmega128a3u\*(C'\fR, \f(CW\*(C`atxmega128b1\*(C'\fR, \f(CW\*(C`atxmega128b3\*(C'\fR, \f(CW\*(C`atxmega128c3\*(C'\fR, \f(CW\*(C`atxmega128d3\*(C'\fR, \f(CW\*(C`atxmega128d4\*(C'\fR, \f(CW\*(C`atxmega192a3\*(C'\fR, \f(CW\*(C`atxmega192a3u\*(C'\fR, \f(CW\*(C`atxmega192c3\*(C'\fR, \f(CW\*(C`atxmega192d3\*(C'\fR, \f(CW\*(C`atxmega256a3\*(C'\fR, \f(CW\*(C`atxmega256a3b\*(C'\fR, \f(CW\*(C`atxmega256a3bu\*(C'\fR, \f(CW\*(C`atxmega256a3u\*(C'\fR, \f(CW\*(C`atxmega256c3\*(C'\fR, \f(CW\*(C`atxmega256d3\*(C'\fR, \f(CW\*(C`atxmega384c3\*(C'\fR, \f(CW\*(C`atxmega384d3\*(C'\fR.
.ie n .IP """avrxmega7""" 4
.el .IP "\f(CWavrxmega7\fR" 4
.IX Item "avrxmega7"
-\&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.
-\&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR.
+\&\*(L"\s-1XMEGA\s0\*(R" devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM\s0.
+\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR.
.ie n .IP """avrtiny""" 4
.el .IP "\f(CWavrtiny\fR" 4
.IX Item "avrtiny"
-\&\*(L"\s-1TINY\*(R"\s0 Tiny core devices with 512@tie{}B up to 4@tie{}KiB of program memory.
+\&\*(L"\s-1TINY\s0\*(R" Tiny core devices with 512@tie{}B up to 4@tie{}KiB of program memory.
\&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`attiny10\*(C'\fR, \f(CW\*(C`attiny20\*(C'\fR, \f(CW\*(C`attiny4\*(C'\fR, \f(CW\*(C`attiny40\*(C'\fR, \f(CW\*(C`attiny5\*(C'\fR, \f(CW\*(C`attiny9\*(C'\fR.
.ie n .IP """avr1""" 4
.el .IP "\f(CWavr1\fR" 4
@@ -12778,7 +12787,7 @@ command-line option.
.IX Item "-<Switch/case dispatch tables. If you do not want such dispatch>"
tables you can specify the \fB\-fno\-jump\-tables\fR command-line option.
.IP "\-<C and \*(C+ constructors/destructors called during startup/shutdown.>" 4
-.IX Item "-<C and constructors/destructors called during startup/shutdown.>"
+.IX Item "-<C and constructors/destructors called during startup/shutdown.>"
.PD 0
.ie n .IP "\-<If the tools hit a ""gs()"" modifier explained above.>" 4
.el .IP "\-<If the tools hit a \f(CWgs()\fR modifier explained above.>" 4
@@ -12973,7 +12982,7 @@ The definition of these macros is affected by \fB\-mtiny\-stack\fR.
.el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4
.IX Item "__AVR_SP8__"
.PD
-The device has the \s-1SPH \s0(high part of stack pointer) special function
+The device has the \s-1SPH\s0 (high part of stack pointer) special function
register or has an 8\-bit stack pointer, respectively.
The definition of these macros is affected by \fB\-mmcu=\fR and
in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also
@@ -13006,7 +13015,7 @@ This macro reflects the \fB\-mno\-interrupts\fR command-line option.
.el .IP "\f(CW_\|_AVR_ERRATA_SKIP_JMP_CALL_\|_\fR" 4
.IX Item "__AVR_ERRATA_SKIP_JMP_CALL__"
.PD
-Some \s-1AVR\s0 devices (\s-1AT90S8515,\s0 ATmega103) must not skip 32\-bit
+Some \s-1AVR\s0 devices (\s-1AT90S8515\s0, ATmega103) must not skip 32\-bit
instructions because of a hardware erratum. Skip instructions are
\&\f(CW\*(C`SBRS\*(C'\fR, \f(CW\*(C`SBRC\*(C'\fR, \f(CW\*(C`SBIS\*(C'\fR, \f(CW\*(C`SBIC\*(C'\fR and \f(CW\*(C`CPSE\*(C'\fR.
The second macro is only defined if \f(CW\*(C`_\|_AVR_HAVE_JMP_CALL_\|_\*(C'\fR is also
@@ -13014,7 +13023,7 @@ set.
.ie n .IP """_\|_AVR_ISA_RMW_\|_""" 4
.el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4
.IX Item "__AVR_ISA_RMW__"
-The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0).
+The device has Read-Modify-Write instructions (\s-1XCH\s0, \s-1LAC\s0, \s-1LAS\s0 and \s-1LAT\s0).
.ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW""" 4
.el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4
.IX Item "__AVR_SFR_OFFSET__=offset"
@@ -13198,8 +13207,8 @@ should be used instead of \f(CW\*(C`main\*(C'\fR.
This option can only be used in conjunction with \fB\-mmulticore\fR.
.IP "\fB\-msdram\fR" 4
.IX Item "-msdram"
-Build a standalone application for \s-1SDRAM.\s0 Proper start files and
-link scripts are used to put the application into \s-1SDRAM,\s0 and the macro
+Build a standalone application for \s-1SDRAM\s0. Proper start files and
+link scripts are used to put the application into \s-1SDRAM\s0, and the macro
\&\f(CW\*(C`_\|_BFIN_SDRAM\*(C'\fR is defined.
The loader should initialize \s-1SDRAM\s0 before loading the application.
.IP "\fB\-micplb\fR" 4
@@ -13258,7 +13267,7 @@ These options are defined specifically for the \s-1CRIS\s0 ports.
.PD
Generate code for the specified architecture. The choices for
\&\fIarchitecture-type\fR are \fBv3\fR, \fBv8\fR and \fBv10\fR for
-respectively \s-1ETRAX\s0\ 4, \s-1ETRAX\s0\ 100, and \s-1ETRAX\s0\ 100\ \s-1LX.\s0
+respectively \s-1ETRAX\s0\ 4, \s-1ETRAX\s0\ 100, and \s-1ETRAX\s0\ 100\ \s-1LX\s0.
Default is \fBv0\fR except for cris-axis-linux-gnu, where the default is
\&\fBv10\fR.
.IP "\fB\-mtune=\fR\fIarchitecture-type\fR" 4
@@ -13351,7 +13360,7 @@ or storage for local variables needs to be allocated.
With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate)
instruction sequences that load addresses for functions from the \s-1PLT\s0 part
of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the
-\&\s-1PLT. \s0 The default is \fB\-mgotplt\fR.
+\&\s-1PLT\s0. The default is \fB\-mgotplt\fR.
.IP "\fB\-melf\fR" 4
.IX Item "-melf"
Legacy no-op option only recognized with the cris-axis-elf and
@@ -13407,7 +13416,7 @@ However, \fBfar\fR is not valid with \fB\-mcr16c\fR, as the
These options are defined for all architectures running the Darwin operating
system.
.PP
-\&\s-1FSF GCC\s0 on Darwin does not create \*(L"fat\*(R" object files; it creates
+\&\s-1FSF\s0 \s-1GCC\s0 on Darwin does not create \*(L"fat\*(R" object files; it creates
an object file for the single architecture that \s-1GCC\s0 was built to
target. Apple's \s-1GCC\s0 on Darwin does create \*(L"fat\*(R" files if multiple
\&\fB\-arch\fR options are used; it does so by running the compiler or
@@ -13467,7 +13476,7 @@ warn about constructs contained within header files found via
.IX Item "-gused"
Emit debugging information for symbols that are used. For stabs
debugging format, this enables \fB\-feliminate\-unused\-debug\-symbols\fR.
-This is by default \s-1ON.\s0
+This is by default \s-1ON\s0.
.IP "\fB\-gfull\fR" 4
.IX Item "-gfull"
Emit debugging information for all symbols and types.
@@ -13543,7 +13552,7 @@ an executable when linking, using the Darwin \fIlibtool\fR command.
This causes \s-1GCC\s0's output file to have the \fB\s-1ALL\s0\fR subtype, instead of
one controlled by the \fB\-mcpu\fR or \fB\-march\fR option.
.IP "\fB\-allowable_client\fR \fIclient_name\fR" 4
-.IX Item "-allowable_client client_name"
+.IX Item "-allowable_client client_name"
.PD 0
.IP "\fB\-client_name\fR" 4
.IX Item "-client_name"
@@ -13717,7 +13726,7 @@ compilers call this option \fB\-ieee_with_no_inexact\fR.
.IP "\fB\-mieee\-with\-inexact\fR" 4
.IX Item "-mieee-with-inexact"
This is like \fB\-mieee\fR except the generated code also maintains
-the \s-1IEEE \s0\fIinexact-flag\fR. Turning on this option causes the
+the \s-1IEEE\s0 \fIinexact-flag\fR. Turning on this option causes the
generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to
\&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor
macro. On some Alpha implementations the resulting code may execute
@@ -13843,8 +13852,8 @@ before it can find the variables and constants in its own data segment.
.IP "\fB\-mno\-max\fR" 4
.IX Item "-mno-max"
.PD
-Indicate whether \s-1GCC\s0 should generate code to use the optional \s-1BWX,
-CIX, FIX\s0 and \s-1MAX\s0 instruction sets. The default is to use the instruction
+Indicate whether \s-1GCC\s0 should generate code to use the optional \s-1BWX\s0,
+\&\s-1CIX\s0, \s-1FIX\s0 and \s-1MAX\s0 instruction sets. The default is to use the instruction
sets supported by the \s-1CPU\s0 type specified via \fB\-mcpu=\fR option or that
of the \s-1CPU\s0 on which \s-1GCC\s0 was built if none is specified.
.IP "\fB\-mfloat\-vax\fR" 4
@@ -13853,7 +13862,7 @@ of the \s-1CPU\s0 on which \s-1GCC\s0 was built if none is specified.
.IP "\fB\-mfloat\-ieee\fR" 4
.IX Item "-mfloat-ieee"
.PD
-Generate code that uses (does not use) \s-1VAX F\s0 and G floating-point
+Generate code that uses (does not use) \s-1VAX\s0 F and G floating-point
arithmetic instead of \s-1IEEE\s0 single and double precision.
.IP "\fB\-mexplicit\-relocs\fR" 4
.IX Item "-mexplicit-relocs"
@@ -13908,7 +13917,7 @@ The default is \fB\-mlarge\-text\fR.
Set the instruction set and instruction scheduling parameters for
machine type \fIcpu_type\fR. You can specify either the \fB\s-1EV\s0\fR
style name or the corresponding chip number. \s-1GCC\s0 supports scheduling
-parameters for the \s-1EV4, EV5\s0 and \s-1EV6\s0 family of processors and
+parameters for the \s-1EV4\s0, \s-1EV5\s0 and \s-1EV6\s0 family of processors and
chooses the default values for the instruction set from the processor
you specify. If you do not specify a processor type, \s-1GCC\s0 defaults
to the processor on which the compiler was built.
@@ -13953,14 +13962,14 @@ Schedules as an \s-1EV5\s0 and supports the \s-1BWX\s0 and \s-1MAX\s0 extensions
.IP "\fB21264\fR" 4
.IX Item "21264"
.PD
-Schedules as an \s-1EV6\s0 and supports the \s-1BWX, FIX,\s0 and \s-1MAX\s0 extensions.
+Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions.
.IP "\fBev67\fR" 4
.IX Item "ev67"
.PD 0
.IP "\fB21264a\fR" 4
.IX Item "21264a"
.PD
-Schedules as an \s-1EV6\s0 and supports the \s-1BWX, CIX, FIX,\s0 and \s-1MAX\s0 extensions.
+Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1CIX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions.
.RE
.RS 4
.Sp
@@ -14001,9 +14010,9 @@ A decimal number representing clock cycles.
.IX Item "main"
.PD
The compiler contains estimates of the number of clock cycles for
-\&\*(L"typical\*(R" \s-1EV4 & EV5\s0 hardware for the Level 1, 2 & 3 caches
+\&\*(L"typical\*(R" \s-1EV4\s0 & \s-1EV5\s0 hardware for the Level 1, 2 & 3 caches
(also called Dcache, Scache, and Bcache), as well as to main memory.
-Note that L3 is only valid for \s-1EV5.\s0
+Note that L3 is only valid for \s-1EV5\s0.
.RE
.RS 4
.RE
@@ -14076,7 +14085,7 @@ Use multiply and add/subtract instructions.
Do not use multiply and add/subtract instructions.
.IP "\fB\-mfdpic\fR" 4
.IX Item "-mfdpic"
-Select the \s-1FDPIC ABI,\s0 which uses function descriptors to represent
+Select the \s-1FDPIC\s0 \s-1ABI\s0, which uses function descriptors to represent
pointers to functions. Without any PIC/PIE\-related options, it
implies \fB\-fPIE\fR. With \fB\-fpic\fR or \fB\-fpie\fR, it
assumes \s-1GOT\s0 entries and small data are within a 12\-bit range from the
@@ -14099,7 +14108,7 @@ Assume a large \s-1TLS\s0 segment when generating thread-local code.
Do not assume a large \s-1TLS\s0 segment when generating thread-local code.
.IP "\fB\-mgprel\-ro\fR" 4
.IX Item "-mgprel-ro"
-Enable the use of \f(CW\*(C`GPREL\*(C'\fR relocations in the \s-1FDPIC ABI\s0 for data
+Enable the use of \f(CW\*(C`GPREL\*(C'\fR relocations in the \s-1FDPIC\s0 \s-1ABI\s0 for data
that is known to be in read-only sections. It's enabled by default,
except for \fB\-fpic\fR or \fB\-fpie\fR: even though it may help
make the global offset table smaller, it trades 1 instruction for 4.
@@ -14243,7 +14252,7 @@ Select the processor type for which to generate code. Possible values are
These \fB\-m\fR options are defined for GNU/Linux targets:
.IP "\fB\-mglibc\fR" 4
.IX Item "-mglibc"
-Use the \s-1GNU C\s0 library. This is the default except
+Use the \s-1GNU\s0 C library. This is the default except
on \fB*\-*\-linux\-*uclibc*\fR and \fB*\-*\-linux\-*android*\fR targets.
.IP "\fB\-muclibc\fR" 4
.IX Item "-muclibc"
@@ -14322,8 +14331,8 @@ These \fB\-m\fR options are defined for the \s-1HPPA\s0 family of computers:
.IP "\fB\-march=\fR\fIarchitecture-type\fR" 4
.IX Item "-march=architecture-type"
Generate code for the specified architecture. The choices for
-\&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0, \s0\fB1.1\fR for \s-1PA
-1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to
+\&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA\s0 1.0, \fB1.1\fR for \s-1PA\s0
+1.1, and \fB2.0\fR for \s-1PA\s0 2.0 processors. Refer to
\&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper
architecture option for your machine. Code compiled for lower numbered
architectures runs on higher numbered architectures, but not the
@@ -14349,7 +14358,7 @@ floating-point operations, the compiler aborts.
.IP "\fB\-mdisable\-indexing\fR" 4
.IX Item "-mdisable-indexing"
Prevent the compiler from using indexing address modes. This avoids some
-rather obscure problems when compiling \s-1MIG\s0 generated code under \s-1MACH.\s0
+rather obscure problems when compiling \s-1MIG\s0 generated code under \s-1MACH\s0.
.IP "\fB\-mno\-space\-regs\fR" 4
.IX Item "-mno-space-regs"
Generate code that assumes the target has no space registers. This allows
@@ -14406,17 +14415,17 @@ cross-compilation.
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-msio\fR" 4
.IX Item "-msio"
-Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO. \s0 The default is
+Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO\s0. The default is
\&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR,
-\&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO. \s0 These
+\&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO\s0. These
options are available under HP-UX and HI-UX.
.IP "\fB\-mgnu\-ld\fR" 4
.IX Item "-mgnu-ld"
-Use options specific to \s-1GNU \s0\fBld\fR.
+Use options specific to \s-1GNU\s0 \fBld\fR.
This passes \fB\-shared\fR to \fBld\fR when
building a shared library. It is the default when \s-1GCC\s0 is configured,
explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not
@@ -14426,10 +14435,10 @@ The \fBld\fR that is called is determined by the
\&\fB\-\-with\-ld\fR configure option, \s-1GCC\s0's program search path, and
finally by the user's \fB\s-1PATH\s0\fR. The linker used by \s-1GCC\s0 can be printed
using \fBwhich `gcc \-print\-prog\-name=ld`\fR. This option is only available
-on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
+on the 64\-bit HP-UX \s-1GCC\s0, i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
.IP "\fB\-mhp\-ld\fR" 4
.IX Item "-mhp-ld"
-Use options specific to \s-1HP \s0\fBld\fR.
+Use options specific to \s-1HP\s0 \fBld\fR.
This passes \fB\-b\fR to \fBld\fR when building
a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all
links. It is the default when \s-1GCC\s0 is configured, explicitly or
@@ -14440,7 +14449,7 @@ The \fBld\fR that is called is determined by the \fB\-\-with\-ld\fR
configure option, \s-1GCC\s0's program search path, and finally by the user's
\&\fB\s-1PATH\s0\fR. The linker used by \s-1GCC\s0 can be printed using \fBwhich
`gcc \-print\-prog\-name=ld`\fR. This option is only available on the 64\-bit
-HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
+HP-UX \s-1GCC\s0, i.e. configured with \fBhppa*64*\-*\-hpux*\fR.
.IP "\fB\-mlong\-calls\fR" 4
.IX Item "-mlong-calls"
Generate code that uses long call sequences. This ensures that a call
@@ -14449,7 +14458,7 @@ long calls only when the distance from the call site to the beginning
of the function or translation unit, as the case may be, exceeds a
predefined limit set by the branch type being used. The limits for
normal calls are 7,600,000 and 240,000 bytes, respectively for the
-\&\s-1PA 2.0\s0 and \s-1PA 1.X\s0 architectures. Sibcalls are always limited at
+\&\s-1PA\s0 2.0 and \s-1PA\s0 1.X architectures. Sibcalls are always limited at
240,000 bytes.
.Sp
Distances are measured from the beginning of functions when using the
@@ -14477,7 +14486,7 @@ is available on HP-UX 10.10 and later. \fB98\fR is available on HP-UX
\&\fB95\fR for HP-UX 10.10 though to 11.00, and \fB98\fR for HP-UX 11.11
and later.
.Sp
-\&\fB\-munix=93\fR provides the same predefines as \s-1GCC 3.3\s0 and 3.4.
+\&\fB\-munix=93\fR provides the same predefines as \s-1GCC\s0 3.3 and 3.4.
\&\fB\-munix=95\fR provides additional predefines for \f(CW\*(C`XOPEN_UNIX\*(C'\fR
and \f(CW\*(C`_XOPEN_SOURCE_EXTENDED\*(C'\fR, and the startfile \fIunix95.o\fR.
\&\fB\-munix=98\fR provides additional predefines for \f(CW\*(C`_XOPEN_UNIX\*(C'\fR,
@@ -14543,7 +14552,7 @@ Generate (or don't) code for the \s-1GNU\s0 linker. This is the default.
.IP "\fB\-mno\-pic\fR" 4
.IX Item "-mno-pic"
Generate code that does not use a global pointer register. The result
-is not position independent code, and violates the \s-1IA\-64 ABI.\s0
+is not position independent code, and violates the \s-1IA\-64\s0 \s-1ABI\s0.
.IP "\fB\-mvolatile\-asm\-stop\fR" 4
.IX Item "-mvolatile-asm-stop"
.PD 0
@@ -14623,7 +14632,7 @@ instructions. The default is to use these instructions.
.IP "\fB\-mdwarf2\-asm\fR" 4
.IX Item "-mdwarf2-asm"
.PD
-Don't (or do) generate assembler code for the \s-1DWARF 2\s0 line number debugging
+Don't (or do) generate assembler code for the \s-1DWARF\s0 2 line number debugging
info. This may be useful when not using the \s-1GNU\s0 assembler.
.IP "\fB\-mearly\-stop\-bits\fR" 4
.IX Item "-mearly-stop-bits"
@@ -14647,7 +14656,7 @@ Specify bit size of immediate \s-1TLS\s0 offsets. Valid values are 14, 22, and
64.
.IP "\fB\-mtune=\fR\fIcpu-type\fR" 4
.IX Item "-mtune=cpu-type"
-Tune the instruction scheduling for a particular \s-1CPU,\s0 Valid values are
+Tune the instruction scheduling for a particular \s-1CPU\s0, Valid values are
\&\fBitanium\fR, \fBitanium1\fR, \fBmerced\fR, \fBitanium2\fR,
and \fBmckinley\fR.
.IP "\fB\-milp32\fR" 4
@@ -15096,7 +15105,7 @@ have to be emulated by software on the 68060. Use this option if your 68060
does not have code to emulate those instructions.
.IP "\fB\-mcpu32\fR" 4
.IX Item "-mcpu32"
-Generate output for a \s-1CPU32. \s0 This is the default
+Generate output for a \s-1CPU32\s0. This is the default
when the compiler is configured for CPU32\-based systems.
It is equivalent to \fB\-march=cpu32\fR.
.Sp
@@ -15105,16 +15114,16 @@ Use this option for microcontrollers with a
68336, 68340, 68341, 68349 and 68360.
.IP "\fB\-m5200\fR" 4
.IX Item "-m5200"
-Generate output for a 520X ColdFire \s-1CPU. \s0 This is the default
+Generate output for a 520X ColdFire \s-1CPU\s0. This is the default
when the compiler is configured for 520X\-based systems.
It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated
in favor of that option.
.Sp
Use this option for microcontroller with a 5200 core, including
-the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0
+the \s-1MCF5202\s0, \s-1MCF5203\s0, \s-1MCF5204\s0 and \s-1MCF5206\s0.
.IP "\fB\-m5206e\fR" 4
.IX Item "-m5206e"
-Generate output for a 5206e ColdFire \s-1CPU. \s0 The option is now
+Generate output for a 5206e ColdFire \s-1CPU\s0. The option is now
deprecated in favor of the equivalent \fB\-mcpu=5206e\fR.
.IP "\fB\-m528x\fR" 4
.IX Item "-m528x"
@@ -15123,15 +15132,15 @@ The option is now deprecated in favor of the equivalent
\&\fB\-mcpu=528x\fR.
.IP "\fB\-m5307\fR" 4
.IX Item "-m5307"
-Generate output for a ColdFire 5307 \s-1CPU. \s0 The option is now deprecated
+Generate output for a ColdFire 5307 \s-1CPU\s0. The option is now deprecated
in favor of the equivalent \fB\-mcpu=5307\fR.
.IP "\fB\-m5407\fR" 4
.IX Item "-m5407"
-Generate output for a ColdFire 5407 \s-1CPU. \s0 The option is now deprecated
+Generate output for a ColdFire 5407 \s-1CPU\s0. The option is now deprecated
in favor of the equivalent \fB\-mcpu=5407\fR.
.IP "\fB\-mcfv4e\fR" 4
.IX Item "-mcfv4e"
-Generate output for a ColdFire V4e family \s-1CPU \s0(e.g. 547x/548x).
+Generate output for a ColdFire V4e family \s-1CPU\s0 (e.g. 547x/548x).
This includes use of hardware floating-point instructions.
The option is equivalent to \fB\-mcpu=547x\fR, and is now
deprecated in favor of that option.
@@ -15158,14 +15167,14 @@ The option is equivalent to \fB\-march=68020\fR \fB\-mtune=68020\-60\fR.
.IX Item "-m68881"
.PD
Generate floating-point instructions. This is the default for 68020
-and above, and for ColdFire devices that have an \s-1FPU. \s0 It defines the
+and above, and for ColdFire devices that have an \s-1FPU\s0. It defines the
macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR
on ColdFire targets.
.IP "\fB\-msoft\-float\fR" 4
.IX Item "-msoft-float"
Do not generate floating-point instructions; use library calls instead.
This is the default for 68000, 68010, and 68832 targets. It is also
-the default for ColdFire devices that have no \s-1FPU.\s0
+the default for ColdFire devices that have no \s-1FPU\s0.
.IP "\fB\-mdiv\fR" 4
.IX Item "-mdiv"
.PD 0
@@ -15175,8 +15184,8 @@ the default for ColdFire devices that have no \s-1FPU.\s0
Generate (do not generate) ColdFire hardware divide and remainder
instructions. If \fB\-march\fR is used without \fB\-mcpu\fR,
the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0
-architectures. Otherwise, the default is taken from the target \s-1CPU
-\&\s0(either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For
+architectures. Otherwise, the default is taken from the target \s-1CPU\s0
+(either the default \s-1CPU\s0, or the one specified by \fB\-mcpu\fR). For
example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for
\&\fB\-mcpu=5206e\fR.
.Sp
@@ -15295,7 +15304,7 @@ that works if the \s-1GOT\s0 has more than 8192 entries. This code is
larger and slower than code generated without this option. On M680x0
processors, this option is not needed; \fB\-fPIC\fR suffices.
.Sp
-\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT.\s0
+\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT\s0.
While this is relatively efficient, it only works if the \s-1GOT\s0
is smaller than about 64k. Anything larger causes the linker
to report an error such as:
@@ -15437,7 +15446,7 @@ useful unless you also provide \fB\-mminmax\fR.
Selects one of the built-in core configurations. Each MeP chip has
one or more modules in it; each module has a core \s-1CPU\s0 and a variety of
coprocessors, optional instructions, and peripherals. The
-\&\f(CW\*(C`MeP\-Integrator\*(C'\fR tool, not part of \s-1GCC,\s0 provides these
+\&\f(CW\*(C`MeP\-Integrator\*(C'\fR tool, not part of \s-1GCC\s0, provides these
configurations through this option; using this option is the same as
using all the corresponding command-line options. The default
configuration is \fBdefault\fR.
@@ -15540,7 +15549,7 @@ Do not optimize block moves, use \f(CW\*(C`memcpy\*(C'\fR.
This option is deprecated. Use \fB\-fno\-zero\-initialized\-in\-bss\fR instead.
.IP "\fB\-mcpu=\fR\fIcpu-type\fR" 4
.IX Item "-mcpu=cpu-type"
-Use features of, and schedule code for, the given \s-1CPU.\s0
+Use features of, and schedule code for, the given \s-1CPU\s0.
Supported values are in the format \fBv\fR\fIX\fR\fB.\fR\fI\s-1YY\s0\fR\fB.\fR\fIZ\fR,
where \fIX\fR is a major version, \fI\s-1YY\s0\fR is the minor version, and
\&\fIZ\fR is compatibility code. Example values are \fBv3.00.a\fR,
@@ -15626,7 +15635,7 @@ configurations.
.IP "\fB\-march=\fR\fIarch\fR" 4
.IX Item "-march=arch"
Generate code that runs on \fIarch\fR, which can be the name of a
-generic \s-1MIPS ISA,\s0 or the name of a particular processor.
+generic \s-1MIPS\s0 \s-1ISA\s0, or the name of a particular processor.
The \s-1ISA\s0 names are:
\&\fBmips1\fR, \fBmips2\fR, \fBmips3\fR, \fBmips4\fR,
\&\fBmips32\fR, \fBmips32r2\fR, \fBmips32r3\fR, \fBmips32r5\fR,
@@ -15658,7 +15667,7 @@ The processor names are:
\&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR,
\&\fBxlr\fR and \fBxlp\fR.
The special value \fBfrom-abi\fR selects the
-most compatible architecture for the selected \s-1ABI \s0(that is,
+most compatible architecture for the selected \s-1ABI\s0 (that is,
\&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs).
.Sp
The native Linux/GNU toolchain also supports the value \fBnative\fR,
@@ -15754,7 +15763,7 @@ Equivalent to \fB\-march=mips64r6\fR.
.IX Item "-mno-mips16"
.PD
Generate (do not generate) \s-1MIPS16\s0 code. If \s-1GCC\s0 is targeting a
-\&\s-1MIPS32\s0 or \s-1MIPS64\s0 architecture, it makes use of the MIPS16e \s-1ASE.\s0
+\&\s-1MIPS32\s0 or \s-1MIPS64\s0 architecture, it makes use of the MIPS16e \s-1ASE\s0.
.Sp
\&\s-1MIPS16\s0 code generation can also be controlled on a per-function basis
by means of \f(CW\*(C`mips16\*(C'\fR and \f(CW\*(C`nomips16\*(C'\fR attributes.
@@ -15769,7 +15778,7 @@ not intended for ordinary use in compiling user code.
.IP "\fB\-mno\-interlink\-compressed\fR" 4
.IX Item "-mno-interlink-compressed"
.PD
-Require (do not require) that code using the standard (uncompressed) \s-1MIPS ISA\s0
+Require (do not require) that code using the standard (uncompressed) \s-1MIPS\s0 \s-1ISA\s0
be link-compatible with \s-1MIPS16\s0 and microMIPS code, and vice versa.
.Sp
For example, code using the standard \s-1ISA\s0 encoding cannot jump directly
@@ -15797,20 +15806,20 @@ and are retained for backwards compatibility.
.IP "\fB\-mabi=eabi\fR" 4
.IX Item "-mabi=eabi"
.PD
-Generate code for the given \s-1ABI.\s0
+Generate code for the given \s-1ABI\s0.
.Sp
Note that the \s-1EABI\s0 has a 32\-bit and a 64\-bit variant. \s-1GCC\s0 normally
generates 64\-bit code when you select a 64\-bit architecture, but you
can use \fB\-mgp32\fR to get 32\-bit code instead.
.Sp
-For information about the O64 \s-1ABI,\s0 see
+For information about the O64 \s-1ABI\s0, see
<\fBhttp://gcc.gnu.org/projects/mipso64\-abi.html\fR>.
.Sp
\&\s-1GCC\s0 supports a variant of the o32 \s-1ABI\s0 in which floating-point registers
are 64 rather than 32 bits wide. You can select this combination with
\&\fB\-mabi=32\fR \fB\-mfp64\fR. This \s-1ABI\s0 relies on the \f(CW\*(C`mthc1\*(C'\fR
and \f(CW\*(C`mfhc1\*(C'\fR instructions and is therefore only supported for
-\&\s-1MIPS32R2, MIPS32R3\s0 and \s-1MIPS32R5\s0 processors.
+\&\s-1MIPS32R2\s0, \s-1MIPS32R3\s0 and \s-1MIPS32R5\s0 processors.
.Sp
The register assignments for arguments and return values remain the
same, but each scalar value is passed in a single 64\-bit register
@@ -15821,11 +15830,11 @@ remains the same in that the even-numbered double-precision registers
are saved.
.Sp
Two additional variants of the o32 \s-1ABI\s0 are supported to enable
-a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX
-\&\s0(\fB\-mfpxx\fR) and \s-1FP64A \s0(\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR).
+a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX\s0
+(\fB\-mfpxx\fR) and \s-1FP64A\s0 (\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR).
The \s-1FPXX\s0 extension mandates that all code must execute correctly
when run using 32\-bit or 64\-bit registers. The code can be interlinked
-with either \s-1FP32\s0 or \s-1FP64,\s0 but not both.
+with either \s-1FP32\s0 or \s-1FP64\s0, but not both.
The \s-1FP64A\s0 extension is similar to the \s-1FP64\s0 extension but forbids the
use of odd-numbered single-precision registers. This can be used
in conjunction with the \f(CW\*(C`FRE\*(C'\fR mode of FPUs in \s-1MIPS32R5\s0
@@ -15872,7 +15881,7 @@ executables both smaller and quicker.
.PD
Assume (do not assume) that the static and dynamic linkers
support PLTs and copy relocations. This option only affects
-\&\fB\-mno\-shared \-mabicalls\fR. For the n64 \s-1ABI,\s0 this option
+\&\fB\-mno\-shared \-mabicalls\fR. For the n64 \s-1ABI\s0, this option
has no effect without \fB\-msym32\fR.
.Sp
You can make \fB\-mplt\fR the default by configuring
@@ -15887,7 +15896,7 @@ You can make \fB\-mplt\fR the default by configuring
Lift (do not lift) the usual restrictions on the size of the global
offset table.
.Sp
-\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT.\s0
+\&\s-1GCC\s0 normally uses a single instruction to load values from the \s-1GOT\s0.
While this is relatively efficient, it only works if the \s-1GOT\s0
is smaller than about 64k. Anything larger causes the linker
to report an error such as:
@@ -15955,8 +15964,8 @@ operations. This is the default.
.IX Item "-mno-odd-spreg"
.PD
Enable the use of odd-numbered single-precision floating-point registers
-for the o32 \s-1ABI. \s0 This is the default for processors that are known to
-support these registers. When using the o32 \s-1FPXX ABI, \s0\fB\-mno\-odd\-spreg\fR
+for the o32 \s-1ABI\s0. This is the default for processors that are known to
+support these registers. When using the o32 \s-1FPXX\s0 \s-1ABI\s0, \fB\-mno\-odd\-spreg\fR
is set by default.
.IP "\fB\-mabs=2008\fR" 4
.IX Item "-mabs=2008"
@@ -15965,7 +15974,7 @@ is set by default.
.IX Item "-mabs=legacy"
.PD
These options control the treatment of the special not-a-number (NaN)
-\&\s-1IEEE 754\s0 floating-point data with the \f(CW\*(C`abs.\f(CIfmt\f(CW\*(C'\fR and
+\&\s-1IEEE\s0 754 floating-point data with the \f(CW\*(C`abs.\f(CIfmt\f(CW\*(C'\fR and
\&\f(CW\*(C`neg.\f(CIfmt\f(CW\*(C'\fR machine instructions.
.Sp
By default or when \fB\-mabs=legacy\fR is used the legacy
@@ -15976,7 +15985,7 @@ manipulate the sign bit of floating-point datum manually is used
instead unless the \fB\-ffinite\-math\-only\fR option has also been
specified.
.Sp
-The \fB\-mabs=2008\fR option selects the \s-1IEEE 754\-2008\s0 treatment. In
+The \fB\-mabs=2008\fR option selects the \s-1IEEE\s0 754\-2008 treatment. In
this case these instructions are considered non-arithmetic and therefore
operating correctly in all cases, including in particular where the
input operand is a NaN. These instructions are therefore always used
@@ -15988,14 +15997,14 @@ for the respective operations.
.IX Item "-mnan=legacy"
.PD
These options control the encoding of the special not-a-number (NaN)
-\&\s-1IEEE 754\s0 floating-point data.
+\&\s-1IEEE\s0 754 floating-point data.
.Sp
The \fB\-mnan=legacy\fR option selects the legacy encoding. In this
case quiet NaNs (qNaNs) are denoted by the first bit of their trailing
significand field being 0, whereas signalling NaNs (sNaNs) are denoted
by the first bit of their trailing significand field being 1.
.Sp
-The \fB\-mnan=2008\fR option selects the \s-1IEEE 754\-2008\s0 encoding. In
+The \fB\-mnan=2008\fR option selects the \s-1IEEE\s0 754\-2008 encoding. In
this case qNaNs are denoted by the first bit of their trailing
significand field being 1, whereas sNaNs are denoted by the first bit of
their trailing significand field being 0.
@@ -16025,8 +16034,8 @@ configurations; see the installation documentation for details.
.IP "\fB\-mno\-dsp\fR" 4
.IX Item "-mno-dsp"
.PD
-Use (do not use) revision 1 of the \s-1MIPS DSP ASE.
- \s0 This option defines the
+Use (do not use) revision 1 of the \s-1MIPS\s0 \s-1DSP\s0 \s-1ASE\s0.
+ This option defines the
preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines
\&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1.
.IP "\fB\-mdspr2\fR" 4
@@ -16035,8 +16044,8 @@ preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines
.IP "\fB\-mno\-dspr2\fR" 4
.IX Item "-mno-dspr2"
.PD
-Use (do not use) revision 2 of the \s-1MIPS DSP ASE.
- \s0 This option defines the
+Use (do not use) revision 2 of the \s-1MIPS\s0 \s-1DSP\s0 \s-1ASE\s0.
+ This option defines the
preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR.
It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2.
.IP "\fB\-msmartmips\fR" 4
@@ -16045,7 +16054,7 @@ It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2.
.IP "\fB\-mno\-smartmips\fR" 4
.IX Item "-mno-smartmips"
.PD
-Use (do not use) the \s-1MIPS\s0 SmartMIPS \s-1ASE.\s0
+Use (do not use) the \s-1MIPS\s0 SmartMIPS \s-1ASE\s0.
.IP "\fB\-mpaired\-single\fR" 4
.IX Item "-mpaired-single"
.PD 0
@@ -16070,7 +16079,7 @@ hardware floating-point support to be enabled.
.IP "\fB\-mno\-mips3d\fR" 4
.IX Item "-mno-mips3d"
.PD
-Use (do not use) the \s-1MIPS\-3D ASE. \s0
+Use (do not use) the \s-1MIPS\-3D\s0 \s-1ASE\s0.
The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR.
.IP "\fB\-mmicromips\fR" 4
.IX Item "-mmicromips"
@@ -16095,7 +16104,7 @@ Use (do not use) \s-1MT\s0 Multithreading instructions.
.IP "\fB\-mno\-mcu\fR" 4
.IX Item "-mno-mcu"
.PD
-Use (do not use) the \s-1MIPS MCU ASE\s0 instructions.
+Use (do not use) the \s-1MIPS\s0 \s-1MCU\s0 \s-1ASE\s0 instructions.
.IP "\fB\-meva\fR" 4
.IX Item "-meva"
.PD 0
@@ -16127,7 +16136,7 @@ determined.
Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide.
.Sp
The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on
-the \s-1ABI. \s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0
+the \s-1ABI\s0. All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0
uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use
32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs,
or the same size as integer registers, whichever is smaller.
@@ -16138,7 +16147,7 @@ or the same size as integer registers, whichever is smaller.
.IX Item "-mno-sym32"
.PD
Assume (do not assume) that all symbols have 32\-bit values, regardless
-of the selected \s-1ABI. \s0 This option is useful in combination with
+of the selected \s-1ABI\s0. This option is useful in combination with
\&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0
to generate shorter and faster references to symbolic addresses.
.IP "\fB\-G\fR \fInum\fR" 4
@@ -16243,13 +16252,13 @@ but other instructions must not do so. This option is useful on 4KSc
and 4KSd processors when the code TLBs have the Read Inhibit bit set.
It is also useful on processors that can be configured to have a dual
instruction/data \s-1SRAM\s0 interface and that, like the M4K, automatically
-redirect PC-relative loads to the instruction \s-1RAM.\s0
+redirect PC-relative loads to the instruction \s-1RAM\s0.
.IP "\fB\-mcode\-readable=no\fR" 4
.IX Item "-mcode-readable=no"
Instructions must not access executable sections. This option can be
useful on targets that are configured to have a dual instruction/data
\&\s-1SRAM\s0 interface but that (unlike the M4K) do not automatically redirect
-PC-relative loads to the instruction \s-1RAM.\s0
+PC-relative loads to the instruction \s-1RAM\s0.
.RE
.RS 4
.RE
@@ -16291,7 +16300,7 @@ The default is \fB\-mcheck\-zero\-division\fR.
.PD
\&\s-1MIPS\s0 systems check for division by zero by generating either a
conditional trap or a break instruction. Using traps results in
-smaller code, but is only supported on \s-1MIPS II\s0 and later. Also, some
+smaller code, but is only supported on \s-1MIPS\s0 \s-1II\s0 and later. Also, some
versions of the Linux kernel have a bug that prevents trap from
generating the proper signal (\f(CW\*(C`SIGFPE\*(C'\fR). Use \fB\-mdivide\-traps\fR to
allow conditional traps on architectures that support them and
@@ -16329,7 +16338,7 @@ This option has no effect on abicalls code. The default is
.IX Item "-mno-mad"
.PD
Enable (disable) use of the \f(CW\*(C`mad\*(C'\fR, \f(CW\*(C`madu\*(C'\fR and \f(CW\*(C`mul\*(C'\fR
-instructions, as provided by the R4650 \s-1ISA.\s0
+instructions, as provided by the R4650 \s-1ISA\s0.
.IP "\fB\-mimadd\fR" 4
.IX Item "-mimadd"
.PD 0
@@ -16367,7 +16376,7 @@ assembler files (with a \fB.s\fR suffix) when assembling them.
.IX Item "-mno-fix-24k"
.PD
Work around the 24K E48 (lost data on stores during refill) errata.
-The workarounds are implemented by the assembler rather than by \s-1GCC.\s0
+The workarounds are implemented by the assembler rather than by \s-1GCC\s0.
.IP "\fB\-mfix\-r4000\fR" 4
.IX Item "-mfix-r4000"
.PD 0
@@ -16427,8 +16436,8 @@ otherwise.
.IP "\fB\-mno\-fix\-rm7000\fR" 4
.IX Item "-mno-fix-rm7000"
.PD
-Work around the \s-1RM7000 \s0\f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The
-workarounds are implemented by the assembler rather than by \s-1GCC.\s0
+Work around the \s-1RM7000\s0 \f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The
+workarounds are implemented by the assembler rather than by \s-1GCC\s0.
.IP "\fB\-mfix\-vr4120\fR" 4
.IX Item "-mfix-vr4120"
.PD 0
@@ -16454,10 +16463,10 @@ instructions. These errata are handled by the assembler, not by \s-1GCC\s0 itse
.RE
.IP "\fB\-mfix\-vr4130\fR" 4
.IX Item "-mfix-vr4130"
-Work around the \s-1VR4130 \s0\f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The
-workarounds are implemented by the assembler rather than by \s-1GCC,\s0
+Work around the \s-1VR4130\s0 \f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The
+workarounds are implemented by the assembler rather than by \s-1GCC\s0,
although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the
-\&\s-1VR4130 \s0\f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR
+\&\s-1VR4130\s0 \f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR
instructions are available instead.
.IP "\fB\-mfix\-sb1\fR" 4
.IX Item "-mfix-sb1"
@@ -16465,7 +16474,7 @@ instructions are available instead.
.IP "\fB\-mno\-fix\-sb1\fR" 4
.IX Item "-mno-fix-sb1"
.PD
-Work around certain \s-1SB\-1 CPU\s0 core errata.
+Work around certain \s-1SB\-1\s0 \s-1CPU\s0 core errata.
(This flag currently works around the \s-1SB\-1\s0 revision 2
\&\*(L"F1\*(R" and \*(L"F2\*(R" floating-point errata.)
.IP "\fB\-mr10k\-cache\-barrier=\fR\fIsetting\fR" 4
@@ -16579,7 +16588,7 @@ Specifies whether \s-1FP\s0 exceptions are enabled. This affects how
The default is that \s-1FP\s0 exceptions are
enabled.
.Sp
-For instance, on the \s-1SB\-1,\s0 if \s-1FP\s0 exceptions are disabled, and we are emitting
+For instance, on the \s-1SB\-1\s0, if \s-1FP\s0 exceptions are disabled, and we are emitting
64\-bit code, then we can use both \s-1FP\s0 pipes. Otherwise, we can only use one
\&\s-1FP\s0 pipe.
.IP "\fB\-mvr4130\-align\fR" 4
@@ -16593,7 +16602,7 @@ instructions together if the first one is 8\-byte aligned. When this
option is enabled, \s-1GCC\s0 aligns pairs of instructions that it
thinks should execute in parallel.
.Sp
-This option only has an effect when optimizing for the \s-1VR4130.\s0
+This option only has an effect when optimizing for the \s-1VR4130\s0.
It normally makes code faster, but at the expense of making it bigger.
It is enabled by default at optimization level \fB\-O3\fR.
.IP "\fB\-msynci\fR" 4
@@ -16682,7 +16691,7 @@ to the \f(CW\*(C`rE\*(C'\fR epsilon register.
.PD
Generate code that passes function parameters and return values that (in
the called function) are seen as registers \f(CW$0\fR and up, as opposed to
-the \s-1GNU ABI\s0 which uses global registers \f(CW$231\fR and up.
+the \s-1GNU\s0 \s-1ABI\s0 which uses global registers \f(CW$231\fR and up.
.IP "\fB\-mzero\-extend\fR" 4
.IX Item "-mzero-extend"
.PD 0
@@ -16766,7 +16775,7 @@ Do not generate code using features specific to the \s-1AM33\s0 processor. This
is the default.
.IP "\fB\-mam33\-2\fR" 4
.IX Item "-mam33-2"
-Generate code using features specific to the \s-1AM33/2.0\s0 processor.
+Generate code using features specific to the \s-1AM33/2\s0.0 processor.
.IP "\fB\-mam34\fR" 4
.IX Item "-mam34"
Generate code using features specific to the \s-1AM34\s0 processor.
@@ -16851,8 +16860,8 @@ header file.
The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is
known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the
430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be
-used to select the 430 \s-1ISA. \s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0
-name selects the 430X \s-1ISA.\s0
+used to select the 430 \s-1ISA\s0. Similarly the generic \fBmsp430x\fR \s-1MCU\s0
+name selects the 430X \s-1ISA\s0.
.Sp
In addition an MCU-specific linker script is added to the linker
command line. The script's name is the name of the \s-1MCU\s0 with
@@ -16865,7 +16874,7 @@ This option is also passed on to the assembler.
.IX Item "-mcpu="
Specifies the \s-1ISA\s0 to use. Accepted values are \fBmsp430\fR,
\&\fBmsp430x\fR and \fBmsp430xv2\fR. This option is deprecated. The
-\&\fB\-mmcu=\fR option should be used to select the \s-1ISA.\s0
+\&\fB\-mmcu=\fR option should be used to select the \s-1ISA\s0.
.IP "\fB\-msim\fR" 4
.IX Item "-msim"
Link to the simulator runtime libraries and linker script. Overrides
@@ -17042,7 +17051,7 @@ global pointer.
.Sp
The default is \fB\-mgpopt\fR except when \fB\-fpic\fR or
\&\fB\-fPIC\fR is specified to generate position-independent code.
-Note that the Nios \s-1II ABI\s0 does not permit GP-relative accesses from
+Note that the Nios \s-1II\s0 \s-1ABI\s0 does not permit GP-relative accesses from
shared libraries.
.Sp
You may need to specify \fB\-mno\-gpopt\fR explicitly when building
@@ -17115,7 +17124,7 @@ of the default behavior of using a library call.
.Sp
The following values of \fIinsn\fR are supported. Except as otherwise
noted, floating-point operations are expected to be implemented with
-normal \s-1IEEE 754\s0 semantics and correspond directly to the C operators or the
+normal \s-1IEEE\s0 754 semantics and correspond directly to the C operators or the
equivalent \s-1GCC\s0 built-in functions.
.Sp
Single-precision floating point:
@@ -17274,14 +17283,14 @@ configuration by using the \f(CW\*(C`target("custom\-fpu\-cfg=\f(CIname\f(CW")\*
function attribute
or pragma.
.PP
-These additional \fB\-m\fR options are available for the Altera Nios \s-1II
-ELF \s0(bare-metal) target:
+These additional \fB\-m\fR options are available for the Altera Nios \s-1II\s0
+\&\s-1ELF\s0 (bare-metal) target:
.IP "\fB\-mhal\fR" 4
.IX Item "-mhal"
-Link with \s-1HAL BSP. \s0 This suppresses linking with the GCC-provided C runtime
+Link with \s-1HAL\s0 \s-1BSP\s0. This suppresses linking with the GCC-provided C runtime
startup and termination code, and is typically used in conjunction with
\&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code
-provided by the \s-1HAL BSP.\s0
+provided by the \s-1HAL\s0 \s-1BSP\s0.
.IP "\fB\-msmallc\fR" 4
.IX Item "-msmallc"
Link with a limited version of the C library, \fB\-lsmallc\fR, rather than
@@ -17295,7 +17304,7 @@ when linking. This option is only useful in conjunction with \fB\-mhal\fR.
\&\fIsystemlib\fR is the library name of the library that provides
low-level system calls required by the C library,
e.g. \f(CW\*(C`read\*(C'\fR and \f(CW\*(C`write\*(C'\fR.
-This option is typically used to link with a library provided by a \s-1HAL BSP.\s0
+This option is typically used to link with a library provided by a \s-1HAL\s0 \s-1BSP\s0.
.PP
\fINvidia \s-1PTX\s0 Options\fR
.IX Subsection "Nvidia PTX Options"
@@ -17307,7 +17316,7 @@ These options are defined for Nvidia \s-1PTX:\s0
.IP "\fB\-m64\fR" 4
.IX Item "-m64"
.PD
-Generate code for 32\-bit or 64\-bit \s-1ABI.\s0
+Generate code for 32\-bit or 64\-bit \s-1ABI\s0.
.IP "\fB\-mmainkernel\fR" 4
.IX Item "-mmainkernel"
Link in code for a _\|_main kernel. This is for stand-alone instead of
@@ -17332,13 +17341,13 @@ Return floating-point results in ac0 (fr0 in Unix assembler syntax).
Return floating-point results in memory. This is the default.
.IP "\fB\-m40\fR" 4
.IX Item "-m40"
-Generate code for a \s-1PDP\-11/40.\s0
+Generate code for a \s-1PDP\-11/40\s0.
.IP "\fB\-m45\fR" 4
.IX Item "-m45"
-Generate code for a \s-1PDP\-11/45. \s0 This is the default.
+Generate code for a \s-1PDP\-11/45\s0. This is the default.
.IP "\fB\-m10\fR" 4
.IX Item "-m10"
-Generate code for a \s-1PDP\-11/10.\s0
+Generate code for a \s-1PDP\-11/10\s0.
.IP "\fB\-mbcopy\-builtin\fR" 4
.IX Item "-mbcopy-builtin"
Use inline \f(CW\*(C`movmemhi\*(C'\fR patterns for copying memory. This is the
@@ -17410,14 +17419,14 @@ for \fIae_type\fR are \fB\s-1ANY\s0\fR, \fB\s-1MUL\s0\fR, and \fB\s-1MAC\s0\fR.
generated with this option runs on any of the other \s-1AE\s0 types. The
code is not as efficient as it would be if compiled for a specific
\&\s-1AE\s0 type, and some types of operation (e.g., multiplication) do not
-work properly on all types of \s-1AE.\s0
+work properly on all types of \s-1AE\s0.
.Sp
-\&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type
+\&\fB\-mae=MUL\fR selects a \s-1MUL\s0 \s-1AE\s0 type. This is the most useful \s-1AE\s0 type
for compiled code, and is the default.
.Sp
-\&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE. \s0 Code compiled with this
+\&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC\s0 \s-1AE\s0. Code compiled with this
option may suffer from poor performance of byte (char) manipulation,
-since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores.
+since the \s-1DSP\s0 \s-1AE\s0 does not provide hardware support for byte load/stores.
.IP "\fB\-msymbol\-as\-address\fR" 4
.IX Item "-msymbol-as-address"
Enable the compiler to directly use a symbol name as an address in a
@@ -17430,7 +17439,7 @@ rather than being permanently enabled.
.IX Item "-mno-inefficient-warnings"
Disables warnings about the generation of inefficient code. These
warnings can be generated, for example, when compiling code that
-performs byte-level memory operations on the \s-1MAC AE\s0 type. The \s-1MAC AE\s0 has
+performs byte-level memory operations on the \s-1MAC\s0 \s-1AE\s0 type. The \s-1MAC\s0 \s-1AE\s0 has
no hardware support for byte-level memory operations, so all byte
load/stores must be synthesized from word load/store operations. This is
inefficient and a warning is generated to indicate
@@ -17472,10 +17481,10 @@ Make the \f(CW\*(C`double\*(C'\fR data type be 64 bits (\fB\-m64bit\-doubles\fR)
or 32 bits (\fB\-m32bit\-doubles\fR) in size. The default is
\&\fB\-m32bit\-doubles\fR.
.PP
-\fI\s-1IBM RS/6000\s0 and PowerPC Options\fR
+\fI\s-1IBM\s0 \s-1RS/6000\s0 and PowerPC Options\fR
.IX Subsection "IBM RS/6000 and PowerPC Options"
.PP
-These \fB\-m\fR options are defined for the \s-1IBM RS/6000\s0 and PowerPC:
+These \fB\-m\fR options are defined for the \s-1IBM\s0 \s-1RS/6000\s0 and PowerPC:
.IP "\fB\-mpowerpc\-gpopt\fR" 4
.IX Item "-mpowerpc-gpopt"
.PD 0
@@ -17520,7 +17529,7 @@ These \fB\-m\fR options are defined for the \s-1IBM RS/6000\s0 and PowerPC:
.PD
You use these options to specify which instructions are available on the
processor you are using. The default value of these options is
-determined when configuring \s-1GCC. \s0 Specifying the
+determined when configuring \s-1GCC\s0. Specifying the
\&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these
options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option
rather than the options listed above.
@@ -17603,7 +17612,7 @@ capabilities. If you wish to set an individual option to a particular
value, you may specify it after the \fB\-mcpu\fR option, like
\&\fB\-mcpu=970 \-mno\-altivec\fR.
.Sp
-On \s-1AIX,\s0 the \fB\-maltivec\fR and \fB\-mpowerpc64\fR options are
+On \s-1AIX\s0, the \fB\-maltivec\fR and \fB\-mpowerpc64\fR options are
not enabled or disabled by the \fB\-mcpu\fR option at present because
\&\s-1AIX\s0 does not have full support for these options. You may still
enable or disable them individually if you're sure it'll work in your
@@ -17691,14 +17700,14 @@ Generate code that allows \fBld\fR and \fBld.so\fR
to build executables and shared
libraries with non-executable \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections.
This is a PowerPC
-32\-bit \s-1SYSV ABI\s0 option.
+32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-mbss\-plt\fR" 4
.IX Item "-mbss-plt"
-Generate code that uses a \s-1BSS \s0\f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR
+Generate code that uses a \s-1BSS\s0 \f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR
fills in, and
requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR
sections that are both writable and executable.
-This is a PowerPC 32\-bit \s-1SYSV ABI\s0 option.
+This is a PowerPC 32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-misel\fR" 4
.IX Item "-misel"
.PD 0
@@ -17747,7 +17756,7 @@ more direct access to the \s-1VSX\s0 instruction set.
.PD
Enable the use (disable) of the built-in functions that allow direct
access to the cryptographic instructions that were added in version
-2.07 of the PowerPC \s-1ISA.\s0
+2.07 of the PowerPC \s-1ISA\s0.
.IP "\fB\-mdirect\-move\fR" 4
.IX Item "-mdirect-move"
.PD 0
@@ -17756,7 +17765,7 @@ access to the cryptographic instructions that were added in version
.PD
Generate code that uses (does not use) the instructions to move data
between the general purpose registers and the vector/scalar (\s-1VSX\s0)
-registers that were added in version 2.07 of the PowerPC \s-1ISA.\s0
+registers that were added in version 2.07 of the PowerPC \s-1ISA\s0.
.IP "\fB\-mpower8\-fusion\fR" 4
.IX Item "-mpower8-fusion"
.PD 0
@@ -17773,7 +17782,7 @@ later processors.
.IX Item "-mno-power8-vector"
.PD
Generate code that uses (does not use) the vector and scalar
-instructions that were added in version 2.07 of the PowerPC \s-1ISA. \s0 Also
+instructions that were added in version 2.07 of the PowerPC \s-1ISA\s0. Also
enable the use of built-in functions that allow more direct access to
the vector instructions.
.IP "\fB\-mquad\-memory\fR" 4
@@ -17803,7 +17812,7 @@ instructions. The \fB\-mquad\-memory\-atomic\fR option requires use of
Generate code that uses (does not use) the scalar double precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.06 of the
-PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-df\fR is turned on by default if you
+PowerPC \s-1ISA\s0. \fB\-mupper\-regs\-df\fR is turned on by default if you
use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or
\&\fB\-mvsx\fR options.
.IP "\fB\-mupper\-regs\-sf\fR" 4
@@ -17815,7 +17824,7 @@ use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or
Generate code that uses (does not use) the scalar single precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.07 of the
-PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-sf\fR is turned on by default if you
+PowerPC \s-1ISA\s0. \fB\-mupper\-regs\-sf\fR is turned on by default if you
use either of the \fB\-mcpu=power8\fR or \fB\-mpower8\-vector\fR
options.
.IP "\fB\-mupper\-regs\fR" 4
@@ -17872,12 +17881,12 @@ pointer to 64 bits, and generates code for PowerPC64, as for
.IP "\fB\-mminimal\-toc\fR" 4
.IX Item "-mminimal-toc"
.PD
-Modify generation of the \s-1TOC \s0(Table Of Contents), which is created for
+Modify generation of the \s-1TOC\s0 (Table Of Contents), which is created for
every executable file. The \fB\-mfull\-toc\fR option is selected by
default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for
each unique non-automatic variable reference in your program. \s-1GCC\s0
-also places floating-point constants in the \s-1TOC. \s0 However, only
-16,384 entries are available in the \s-1TOC.\s0
+also places floating-point constants in the \s-1TOC\s0. However, only
+16,384 entries are available in the \s-1TOC\s0.
.Sp
If you receive a linker error message that saying you have overflowed
the available \s-1TOC\s0 space, you can reduce the amount of \s-1TOC\s0 space used
@@ -17885,7 +17894,7 @@ with the \fB\-mno\-fp\-in\-toc\fR and \fB\-mno\-sum\-in\-toc\fR options.
\&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point
constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to
generate code to calculate the sum of an address and a constant at
-run time instead of putting that sum into the \s-1TOC. \s0 You may specify one
+run time instead of putting that sum into the \s-1TOC\s0. You may specify one
or both of these options. Each causes \s-1GCC\s0 to produce very slightly
slower and larger code at the expense of conserving \s-1TOC\s0 space.
.Sp
@@ -17901,7 +17910,7 @@ only on files that contain less frequently-executed code.
.IP "\fB\-maix32\fR" 4
.IX Item "-maix32"
.PD
-Enable 64\-bit \s-1AIX ABI\s0 and calling convention: 64\-bit pointers, 64\-bit
+Enable 64\-bit \s-1AIX\s0 \s-1ABI\s0 and calling convention: 64\-bit pointers, 64\-bit
\&\f(CW\*(C`long\*(C'\fR type, and the infrastructure needed to support them.
Specifying \fB\-maix64\fR implies \fB\-mpowerpc64\fR,
while \fB\-maix32\fR disables the 64\-bit \s-1ABI\s0 and
@@ -17912,8 +17921,8 @@ implies \fB\-mno\-powerpc64\fR. \s-1GCC\s0 defaults to \fB\-maix32\fR.
.IP "\fB\-mno\-xl\-compat\fR" 4
.IX Item "-mno-xl-compat"
.PD
-Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics
-when using AIX-compatible \s-1ABI. \s0 Pass floating-point arguments to
+Produce code that conforms more closely to \s-1IBM\s0 \s-1XL\s0 compiler semantics
+when using AIX-compatible \s-1ABI\s0. Pass floating-point arguments to
prototyped functions beyond the register save area (\s-1RSA\s0) on the stack
in addition to argument FPRs. Do not assume that most significant
double in 128\-bit long double value is properly rounded when comparing
@@ -17922,16 +17931,16 @@ support routines.
.Sp
The \s-1AIX\s0 calling convention was extended but not initially documented to
handle an obscure K&R C case of calling a function that takes the
-address of its arguments with fewer arguments than declared. \s-1IBM XL\s0
+address of its arguments with fewer arguments than declared. \s-1IBM\s0 \s-1XL\s0
compilers access floating-point arguments that do not fit in the
\&\s-1RSA\s0 from the stack when a subroutine is compiled without
optimization. Because always storing floating-point arguments on the
stack is inefficient and rarely needed, this option is not enabled by
-default and only is necessary when calling subroutines compiled by \s-1IBM
-XL\s0 compilers without optimization.
+default and only is necessary when calling subroutines compiled by \s-1IBM\s0
+\&\s-1XL\s0 compilers without optimization.
.IP "\fB\-mpe\fR" 4
.IX Item "-mpe"
-Support \fI\s-1IBM RS/6000 SP\s0\fR \fIParallel Environment\fR (\s-1PE\s0). Link an
+Support \fI\s-1IBM\s0 \s-1RS/6000\s0 \s-1SP\s0\fR \fIParallel Environment\fR (\s-1PE\s0). Link an
application written to use message passing with special startup code to
enable the application to run. The system must have \s-1PE\s0 installed in the
standard location (\fI/usr/lpp/ppe.poe/\fR), or the \fIspecs\fR file
@@ -17945,11 +17954,11 @@ option are incompatible.
.IP "\fB\-malign\-power\fR" 4
.IX Item "-malign-power"
.PD
-On \s-1AIX,\s0 32\-bit Darwin, and 64\-bit PowerPC GNU/Linux, the option
+On \s-1AIX\s0, 32\-bit Darwin, and 64\-bit PowerPC GNU/Linux, the option
\&\fB\-malign\-natural\fR overrides the ABI-defined alignment of larger
types, such as floating-point doubles, on their natural size-based boundary.
The option \fB\-malign\-power\fR instructs \s-1GCC\s0 to follow the ABI-specified
-alignment rules. \s-1GCC\s0 defaults to the standard alignment defined in the \s-1ABI.\s0
+alignment rules. \s-1GCC\s0 defaults to the standard alignment defined in the \s-1ABI\s0.
.Sp
On 64\-bit Darwin, natural alignment is the default, and \fB\-malign\-power\fR
is not supported.
@@ -17983,7 +17992,7 @@ Specify type of floating-point unit. Valid values for \fIname\fR are
and \fBdp_full\fR (equivalent to \fB\-mdouble\-float\fR).
.IP "\fB\-mxilinx\-fpu\fR" 4
.IX Item "-mxilinx-fpu"
-Perform optimizations for the floating-point unit on Xilinx \s-1PPC 405/440.\s0
+Perform optimizations for the floating-point unit on Xilinx \s-1PPC\s0 405/440.
.IP "\fB\-mmultiple\fR" 4
.IX Item "-mmultiple"
.PD 0
@@ -18054,7 +18063,7 @@ mapped to \fB\-ffp\-contract=off\fR.
.IX Item "-mno-mulhw"
.PD
Generate code that uses (does not use) the half-word multiply and
-multiply-accumulate instructions on the \s-1IBM 405, 440, 464\s0 and 476 processors.
+multiply-accumulate instructions on the \s-1IBM\s0 405, 440, 464 and 476 processors.
These instructions are generated by default when targeting those
processors.
.IP "\fB\-mdlmzb\fR" 4
@@ -18064,7 +18073,7 @@ processors.
.IX Item "-mno-dlmzb"
.PD
Generate code that uses (does not use) the string-search \fBdlmzb\fR
-instruction on the \s-1IBM 405, 440, 464\s0 and 476 processors. This instruction is
+instruction on the \s-1IBM\s0 405, 440, 464 and 476 processors. This instruction is
generated by default when targeting those processors.
.IP "\fB\-mno\-bit\-align\fR" 4
.IX Item "-mno-bit-align"
@@ -18144,7 +18153,7 @@ processor in big-endian mode. The \fB\-mbig\-endian\fR option is
the same as \fB\-mbig\fR.
.IP "\fB\-mdynamic\-no\-pic\fR" 4
.IX Item "-mdynamic-no-pic"
-On Darwin and Mac \s-1OS X\s0 systems, compile code so that it is not
+On Darwin and Mac \s-1OS\s0 X systems, compile code so that it is not
relocatable, but that its external references are relocatable. The
resulting code is suitable for applications, but not shared
libraries.
@@ -18250,11 +18259,11 @@ On System V.4 and embedded PowerPC systems compile code for the
OpenBSD operating system.
.IP "\fB\-maix\-struct\-return\fR" 4
.IX Item "-maix-struct-return"
-Return all structures in memory (as specified by the \s-1AIX ABI\s0).
+Return all structures in memory (as specified by the \s-1AIX\s0 \s-1ABI\s0).
.IP "\fB\-msvr4\-struct\-return\fR" 4
.IX Item "-msvr4-struct-return"
Return structures smaller than 8 bytes in registers (as specified by the
-\&\s-1SVR4 ABI\s0).
+\&\s-1SVR4\s0 \s-1ABI\s0).
.IP "\fB\-mabi=\fR\fIabi-type\fR" 4
.IX Item "-mabi=abi-type"
Extend the current \s-1ABI\s0 with a particular extension, or remove such extension.
@@ -18263,29 +18272,29 @@ Valid values are \fBaltivec\fR, \fBno-altivec\fR, \fBspe\fR,
\&\fBelfv1\fR, \fBelfv2\fR.
.IP "\fB\-mabi=spe\fR" 4
.IX Item "-mabi=spe"
-Extend the current \s-1ABI\s0 with \s-1SPE ABI\s0 extensions. This does not change
-the default \s-1ABI,\s0 instead it adds the \s-1SPE ABI\s0 extensions to the current
-\&\s-1ABI.\s0
+Extend the current \s-1ABI\s0 with \s-1SPE\s0 \s-1ABI\s0 extensions. This does not change
+the default \s-1ABI\s0, instead it adds the \s-1SPE\s0 \s-1ABI\s0 extensions to the current
+\&\s-1ABI\s0.
.IP "\fB\-mabi=no\-spe\fR" 4
.IX Item "-mabi=no-spe"
-Disable Book-E \s-1SPE ABI\s0 extensions for the current \s-1ABI.\s0
+Disable Book-E \s-1SPE\s0 \s-1ABI\s0 extensions for the current \s-1ABI\s0.
.IP "\fB\-mabi=ibmlongdouble\fR" 4
.IX Item "-mabi=ibmlongdouble"
Change the current \s-1ABI\s0 to use \s-1IBM\s0 extended-precision long double.
-This is a PowerPC 32\-bit \s-1SYSV ABI\s0 option.
+This is a PowerPC 32\-bit \s-1SYSV\s0 \s-1ABI\s0 option.
.IP "\fB\-mabi=ieeelongdouble\fR" 4
.IX Item "-mabi=ieeelongdouble"
Change the current \s-1ABI\s0 to use \s-1IEEE\s0 extended-precision long double.
This is a PowerPC 32\-bit Linux \s-1ABI\s0 option.
.IP "\fB\-mabi=elfv1\fR" 4
.IX Item "-mabi=elfv1"
-Change the current \s-1ABI\s0 to use the ELFv1 \s-1ABI.\s0
+Change the current \s-1ABI\s0 to use the ELFv1 \s-1ABI\s0.
This is the default \s-1ABI\s0 for big-endian PowerPC 64\-bit Linux.
Overriding the default \s-1ABI\s0 requires special system support and is
likely to fail in spectacular ways.
.IP "\fB\-mabi=elfv2\fR" 4
.IX Item "-mabi=elfv2"
-Change the current \s-1ABI\s0 to use the ELFv2 \s-1ABI.\s0
+Change the current \s-1ABI\s0 to use the ELFv2 \s-1ABI\s0.
This is the default \s-1ABI\s0 for little-endian PowerPC 64\-bit Linux.
Overriding the default \s-1ABI\s0 requires special system support and is
likely to fail in spectacular ways.
@@ -18439,7 +18448,7 @@ On Darwin/PPC systems, \f(CW\*(C`#pragma longcall\*(C'\fR generates \f(CW\*(C`jb
callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target
addresses represent the callee and the branch island. The
Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl
-callee\*(C'\fR if the \s-1PPC \s0\f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly;
+callee\*(C'\fR if the \s-1PPC\s0 \f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly;
otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch
island. The branch island is appended to the body of the
calling function; it computes the full 32\-bit address of the callee
@@ -18535,7 +18544,7 @@ which handle the double-precision reciprocal square root calculations.
.PD
Assume (do not assume) that the reciprocal estimate instructions
provide higher-precision estimates than is mandated by the PowerPC
-\&\s-1ABI. \s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or
+\&\s-1ABI\s0. Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or
\&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR.
The double-precision square root estimate instructions are not generated by
default on low-precision machines, since they do not provide an
@@ -18608,14 +18617,14 @@ pointer. The \fB\-mno\-save\-toc\-indirect\fR option is the default.
.PD
Generate (do not generate) code to pass structure parameters with a
maximum alignment of 64 bits, for compatibility with older versions
-of \s-1GCC.\s0
+of \s-1GCC\s0.
.Sp
-Older versions of \s-1GCC \s0(prior to 4.9.0) incorrectly did not align a
+Older versions of \s-1GCC\s0 (prior to 4.9.0) incorrectly did not align a
structure parameter on a 128\-bit boundary when that structure contained
a member requiring 128\-bit alignment. This is corrected in more
-recent versions of \s-1GCC. \s0 This option may be used to generate code
+recent versions of \s-1GCC\s0. This option may be used to generate code
that is compatible with functions compiled with older versions of
-\&\s-1GCC.\s0
+\&\s-1GCC\s0.
.Sp
The \fB\-mno\-compat\-align\-parm\fR option is the default.
.PP
@@ -18650,12 +18659,12 @@ values, however, so the \s-1FPU\s0 hardware is not used for doubles if the
.Sp
\&\fINote\fR If the \fB\-fpu\fR option is enabled then
\&\fB\-funsafe\-math\-optimizations\fR is also enabled automatically.
-This is because the \s-1RX FPU\s0 instructions are themselves unsafe.
+This is because the \s-1RX\s0 \s-1FPU\s0 instructions are themselves unsafe.
.IP "\fB\-mcpu=\fR\fIname\fR" 4
.IX Item "-mcpu=name"
-Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are
+Selects the type of \s-1RX\s0 \s-1CPU\s0 to be targeted. Currently three types are
supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and
-the specific \fB\s-1RX610\s0\fR \s-1CPU. \s0 The default is \fB\s-1RX600\s0\fR.
+the specific \fB\s-1RX610\s0\fR \s-1CPU\s0. The default is \fB\s-1RX600\s0\fR.
.Sp
The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the
\&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction.
@@ -18841,7 +18850,7 @@ type. This is the default.
Store (do not store) the address of the caller's frame as backchain pointer
into the callee's stack frame.
A backchain may be needed to allow debugging using tools that do not understand
-\&\s-1DWARF 2\s0 call frame information.
+\&\s-1DWARF\s0 2 call frame information.
When \fB\-mno\-packed\-stack\fR is in effect, the backchain pointer is stored
at the bottom of the stack frame; when \fB\-mpacked\-stack\fR is in effect,
the backchain is placed into the topmost word of the 96/160 byte register
@@ -18873,7 +18882,7 @@ register is always saved two words below the backchain.
.Sp
As long as the stack frame backchain is not used, code generated with
\&\fB\-mpacked\-stack\fR is call-compatible with code generated with
-\&\fB\-mno\-packed\-stack\fR. Note that some non-FSF releases of \s-1GCC 2.95\s0 for
+\&\fB\-mno\-packed\-stack\fR. Note that some non-FSF releases of \s-1GCC\s0 2.95 for
S/390 or zSeries generated code that uses the stack frame backchain at run
time, not just for debugging purposes. Such code is not call-compatible
with code compiled with \fB\-mpacked\-stack\fR. Also, note that the
@@ -18900,8 +18909,8 @@ which does not have this limitation.
.IX Item "-m31"
.PD
When \fB\-m31\fR is specified, generate code compliant to the
-GNU/Linux for S/390 \s-1ABI. \s0 When \fB\-m64\fR is specified, generate
-code compliant to the GNU/Linux for zSeries \s-1ABI. \s0 This allows \s-1GCC\s0 in
+GNU/Linux for S/390 \s-1ABI\s0. When \fB\-m64\fR is specified, generate
+code compliant to the GNU/Linux for zSeries \s-1ABI\s0. This allows \s-1GCC\s0 in
particular to generate 64\-bit instructions. For the \fBs390\fR
targets, the default is \fB\-m31\fR, while the \fBs390x\fR
targets default to \fB\-m64\fR.
@@ -18914,11 +18923,11 @@ targets default to \fB\-m64\fR.
When \fB\-mzarch\fR is specified, generate code using the
instructions available on z/Architecture.
When \fB\-mesa\fR is specified, generate code using the
-instructions available on \s-1ESA/390. \s0 Note that \fB\-mesa\fR is
+instructions available on \s-1ESA/390\s0. Note that \fB\-mesa\fR is
not possible with \fB\-m64\fR.
-When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0
+When generating code compliant to the GNU/Linux for S/390 \s-1ABI\s0,
the default is \fB\-mesa\fR. When generating code compliant
-to the GNU/Linux for zSeries \s-1ABI,\s0 the default is \fB\-mzarch\fR.
+to the GNU/Linux for zSeries \s-1ABI\s0, the default is \fB\-mzarch\fR.
.IP "\fB\-mmvcle\fR" 4
.IX Item "-mmvcle"
.PD 0
@@ -18942,7 +18951,8 @@ The default is to not print debug information.
Generate code that runs on \fIcpu-type\fR, which is the name of a system
representing a certain processor type. Possible values for
\&\fIcpu-type\fR are \fBg5\fR, \fBg6\fR, \fBz900\fR, \fBz990\fR,
-\&\fBz9\-109\fR, \fBz9\-ec\fR, \fBz10\fR, \fBz196\fR, and \fBzEC12\fR.
+\&\fBz9\-109\fR, \fBz9\-ec\fR, \fBz10\fR, \fBz196\fR, \fBzEC12\fR,
+and \fBz13\fR.
When generating code using the instructions available on z/Architecture,
the default is \fB\-march=z900\fR. Otherwise, the default is
\&\fB\-march=g5\fR.
@@ -18958,9 +18968,9 @@ The default is the value used for \fB\-march\fR.
.IP "\fB\-mno\-tpf\-trace\fR" 4
.IX Item "-mno-tpf-trace"
.PD
-Generate code that adds (does not add) in \s-1TPF OS\s0 specific branches to trace
+Generate code that adds (does not add) in \s-1TPF\s0 \s-1OS\s0 specific branches to trace
routines in the operating system. This option is off by default, even
-when compiling for the \s-1TPF OS.\s0
+when compiling for the \s-1TPF\s0 \s-1OS\s0.
.IP "\fB\-mfused\-madd\fR" 4
.IX Item "-mfused-madd"
.PD 0
@@ -19053,16 +19063,16 @@ Specify the \s-1SCORE7D\s0 as the target architecture.
These \fB\-m\fR options are defined for the \s-1SH\s0 implementations:
.IP "\fB\-m1\fR" 4
.IX Item "-m1"
-Generate code for the \s-1SH1.\s0
+Generate code for the \s-1SH1\s0.
.IP "\fB\-m2\fR" 4
.IX Item "-m2"
-Generate code for the \s-1SH2.\s0
+Generate code for the \s-1SH2\s0.
.IP "\fB\-m2e\fR" 4
.IX Item "-m2e"
Generate code for the SH2e.
.IP "\fB\-m2a\-nofpu\fR" 4
.IX Item "-m2a-nofpu"
-Generate code for the SH2a without \s-1FPU,\s0 or for a SH2a\-FPU in such a way
+Generate code for the SH2a without \s-1FPU\s0, or for a SH2a\-FPU in such a way
that the floating-point unit is not used.
.IP "\fB\-m2a\-single\-only\fR" 4
.IX Item "-m2a-single-only"
@@ -19078,7 +19088,7 @@ Generate code for the SH2a\-FPU assuming the floating-point unit is in
double-precision mode by default.
.IP "\fB\-m3\fR" 4
.IX Item "-m3"
-Generate code for the \s-1SH3.\s0
+Generate code for the \s-1SH3\s0.
.IP "\fB\-m3e\fR" 4
.IX Item "-m3e"
Generate code for the SH3e.
@@ -19095,10 +19105,10 @@ Generate code for the \s-1SH4\s0 assuming the floating-point unit is in
single-precision mode by default.
.IP "\fB\-m4\fR" 4
.IX Item "-m4"
-Generate code for the \s-1SH4.\s0
+Generate code for the \s-1SH4\s0.
.IP "\fB\-m4\-100\fR" 4
.IX Item "-m4-100"
-Generate code for \s-1SH4\-100.\s0
+Generate code for \s-1SH4\-100\s0.
.IP "\fB\-m4\-100\-nofpu\fR" 4
.IX Item "-m4-100-nofpu"
Generate code for \s-1SH4\-100\s0 in such a way that the
@@ -19113,7 +19123,7 @@ Generate code for \s-1SH4\-100\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-200\fR" 4
.IX Item "-m4-200"
-Generate code for \s-1SH4\-200.\s0
+Generate code for \s-1SH4\-200\s0.
.IP "\fB\-m4\-200\-nofpu\fR" 4
.IX Item "-m4-200-nofpu"
Generate code for \s-1SH4\-200\s0 without in such a way that the
@@ -19128,7 +19138,7 @@ Generate code for \s-1SH4\-200\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-300\fR" 4
.IX Item "-m4-300"
-Generate code for \s-1SH4\-300.\s0
+Generate code for \s-1SH4\-300\s0.
.IP "\fB\-m4\-300\-nofpu\fR" 4
.IX Item "-m4-300-nofpu"
Generate code for \s-1SH4\-300\s0 without in such a way that the
@@ -19143,10 +19153,10 @@ Generate code for \s-1SH4\-300\s0 in such a way that no double-precision
floating-point operations are used.
.IP "\fB\-m4\-340\fR" 4
.IX Item "-m4-340"
-Generate code for \s-1SH4\-340 \s0(no \s-1MMU,\s0 no \s-1FPU\s0).
+Generate code for \s-1SH4\-340\s0 (no \s-1MMU\s0, no \s-1FPU\s0).
.IP "\fB\-m4\-500\fR" 4
.IX Item "-m4-500"
-Generate code for \s-1SH4\-500 \s0(no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the
+Generate code for \s-1SH4\-500\s0 (no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the
assembler.
.IP "\fB\-m4a\-nofpu\fR" 4
.IX Item "-m4a-nofpu"
@@ -19210,7 +19220,7 @@ Use 32\-bit offsets in \f(CW\*(C`switch\*(C'\fR tables. The default is to use
16\-bit offsets.
.IP "\fB\-mbitops\fR" 4
.IX Item "-mbitops"
-Enable the use of bit manipulation instructions on \s-1SH2A.\s0
+Enable the use of bit manipulation instructions on \s-1SH2A\s0.
.IP "\fB\-mfmovd\fR" 4
.IX Item "-mfmovd"
Enable the use of the instruction \f(CW\*(C`fmovd\*(C'\fR. Check \fB\-mdalign\fR for
@@ -19257,7 +19267,7 @@ Dump instruction size and location in the assembly code.
.IP "\fB\-mpadstruct\fR" 4
.IX Item "-mpadstruct"
This option is deprecated. It pads structures to multiple of 4 bytes,
-which is incompatible with the \s-1SH ABI.\s0
+which is incompatible with the \s-1SH\s0 \s-1ABI\s0.
.IP "\fB\-matomic\-model=\fR\fImodel\fR" 4
.IX Item "-matomic-model=model"
Sets the model of atomic operations and additional parameters as a comma
@@ -19274,7 +19284,7 @@ Generate GNU/Linux compatible gUSA software atomic sequences for the atomic
built-in functions. The generated atomic sequences require additional support
from the interrupt/exception handling code of the system and are only suitable
for SH3* and SH4* single-core systems. This option is enabled by default when
-the target is \f(CW\*(C`sh*\-*\-linux*\*(C'\fR and SH3* or SH4*. When the target is \s-1SH4A,\s0
+the target is \f(CW\*(C`sh*\-*\-linux*\*(C'\fR and SH3* or SH4*. When the target is \s-1SH4A\s0,
this option also partially utilizes the hardware atomic instructions
\&\f(CW\*(C`movli.l\*(C'\fR and \f(CW\*(C`movco.l\*(C'\fR to create more efficient code, unless
\&\fBstrict\fR is specified.
@@ -19417,20 +19427,20 @@ For targets other than SHmedia \fIstrategy\fR can be one of:
.IX Item "call-div1"
Calls a library function that uses the single-step division instruction
\&\f(CW\*(C`div1\*(C'\fR to perform the operation. Division by zero calculates an
-unspecified result and does not trap. This is the default except for \s-1SH4,
-SH2A\s0 and SHcompact.
+unspecified result and does not trap. This is the default except for \s-1SH4\s0,
+\&\s-1SH2A\s0 and SHcompact.
.IP "\fBcall-fp\fR" 4
.IX Item "call-fp"
Calls a library function that performs the operation in double precision
floating point. Division by zero causes a floating-point exception. This is
-the default for SHcompact with \s-1FPU. \s0 Specifying this for targets that do not
+the default for SHcompact with \s-1FPU\s0. Specifying this for targets that do not
have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR.
.IP "\fBcall-table\fR" 4
.IX Item "call-table"
Calls a library function that uses a lookup table for small divisors and
the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division
by zero calculates an unspecified result and does not trap. This is the default
-for \s-1SH4. \s0 Specifying this for targets that do not have dynamic shift
+for \s-1SH4\s0. Specifying this for targets that do not have dynamic shift
instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR.
.RE
.RS 4
@@ -19464,10 +19474,10 @@ specified separated by a comma.
Enable the use of the indexed addressing mode for SHmedia32/SHcompact.
This is only safe if the hardware and/or \s-1OS\s0 implement 32\-bit wrap-around
semantics for the indexed addressing mode. The architecture allows the
-implementation of processors with 64\-bit \s-1MMU,\s0 which the \s-1OS\s0 could use to
+implementation of processors with 64\-bit \s-1MMU\s0, which the \s-1OS\s0 could use to
get 32\-bit addressing, but since no current hardware implementation supports
this or any other way to make the indexed addressing mode safe to use in
-the 32\-bit \s-1ABI,\s0 the default is \fB\-mno\-indexed\-addressing\fR.
+the 32\-bit \s-1ABI\s0, the default is \fB\-mno\-indexed\-addressing\fR.
.IP "\fB\-mgettrcost=\fR\fInumber\fR" 4
.IX Item "-mgettrcost=number"
Set the cost assumed for the \f(CW\*(C`gettr\*(C'\fR instruction to \fInumber\fR.
@@ -19504,7 +19514,7 @@ the compiler are always valid to load with
but with assembler and/or linker tricks it is possible
to generate symbols that cause \f(CW\*(C`ptabs\*(C'\fR or \f(CW\*(C`ptrel\*(C'\fR to trap.
This option is only meaningful when \fB\-mno\-pt\-fixed\fR is in effect.
-It prevents cross-basic-block \s-1CSE,\s0 hoisting and most scheduling
+It prevents cross-basic-block \s-1CSE\s0, hoisting and most scheduling
of symbol loads. The default is \fB\-mno\-invalid\-symbols\fR.
.IP "\fB\-mbranch\-cost=\fR\fInum\fR" 4
.IX Item "-mbranch-cost=num"
@@ -19521,14 +19531,14 @@ is being compiled for.
Assume (do not assume) that zero displacement conditional branch instructions
\&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the
compiler prefers zero displacement branch code sequences. This is
-enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A. \s0 It can be explicitly
+enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A\s0. It can be explicitly
disabled by specifying \fB\-mno\-zdcbranch\fR.
.IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4
.IX Item "-mcbranch-force-delay-slot"
Force the usage of delay slots for conditional branches, which stuffs the delay
slot with a \f(CW\*(C`nop\*(C'\fR if a suitable instruction can't be found. By default
this option is disabled. It can be enabled to work around hardware bugs as
-found in the original \s-1SH7055.\s0
+found in the original \s-1SH7055\s0.
.IP "\fB\-mfused\-madd\fR" 4
.IX Item "-mfused-madd"
.PD 0
@@ -19550,7 +19560,7 @@ mapped to \fB\-ffp\-contract=off\fR.
Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine
and cosine approximations. The option \fB\-mfsca\fR must be used in
combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default
-when generating code for \s-1SH4A. \s0 Using \fB\-mno\-fsca\fR disables sine and cosine
+when generating code for \s-1SH4A\s0. Using \fB\-mno\-fsca\fR disables sine and cosine
approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect.
.IP "\fB\-mfsrra\fR" 4
.IX Item "-mfsrra"
@@ -19562,7 +19572,7 @@ Allow or disallow the compiler to emit the \f(CW\*(C`fsrra\*(C'\fR instruction f
reciprocal square root approximations. The option \fB\-mfsrra\fR must be used
in combination with \fB\-funsafe\-math\-optimizations\fR and
\&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for
-\&\s-1SH4A. \s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations
+\&\s-1SH4A\s0. Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations
even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are
in effect.
.IP "\fB\-mpretend\-cmove\fR" 4
@@ -19616,7 +19626,7 @@ These \fB\-m\fR options are supported on the \s-1SPARC:\s0
.IX Item "-mapp-regs"
.PD
Specify \fB\-mapp\-regs\fR to generate output using the global registers
-2 through 4, which the \s-1SPARC SVR4 ABI\s0 reserves for applications. Like the
+2 through 4, which the \s-1SPARC\s0 \s-1SVR4\s0 \s-1ABI\s0 reserves for applications. Like the
global register 1, each global register 2 through 4 is then treated as an
allocable register that is clobbered by function calls. This is the default.
.Sp
@@ -19662,7 +19672,7 @@ cross-compilation. The embedded targets \fBsparc\-*\-aout\fR and
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-mhard\-quad\-float\fR" 4
.IX Item "-mhard-quad-float"
@@ -19672,7 +19682,7 @@ instructions.
.IX Item "-msoft-quad-float"
Generate output containing library calls for quad-word (long double)
floating-point instructions. The functions called are those specified
-in the \s-1SPARC ABI. \s0 This is the default.
+in the \s-1SPARC\s0 \s-1ABI\s0. This is the default.
.Sp
As of this writing, there are no \s-1SPARC\s0 implementations that have hardware
support for the quad-word floating-point instructions. They all invoke
@@ -19713,10 +19723,10 @@ With \fB\-mfaster\-structs\fR, the compiler assumes that structures
should have 8\-byte alignment. This enables the use of pairs of
\&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure
assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs.
-However, the use of this changed alignment directly violates the \s-1SPARC
-ABI. \s0 Thus, it's intended only for use on targets where the developer
+However, the use of this changed alignment directly violates the \s-1SPARC\s0
+\&\s-1ABI\s0. Thus, it's intended only for use on targets where the developer
acknowledges that their resulting code is not directly in line with
-the rules of the \s-1ABI.\s0
+the rules of the \s-1ABI\s0.
.IP "\fB\-mcpu=\fR\fIcpu_type\fR" 4
.IX Item "-mcpu=cpu_type"
Set the instruction set, register set, and instruction scheduling parameters
@@ -19766,22 +19776,22 @@ SPARCStation 1, 2, \s-1IPX\s0 etc.
With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0
architecture. The only difference from V7 code is that the compiler emits
the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0
-but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=supersparc\fR, the compiler additionally
+but not in \s-1SPARC\-V7\s0. With \fB\-mcpu=supersparc\fR, the compiler additionally
optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and
2000 series.
.Sp
With \fB\-mcpu=sparclite\fR, \s-1GCC\s0 generates code for the SPARClite variant of
the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step
-and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0
+and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7\s0.
With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the
-Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU. \s0 With
+Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU\s0. With
\&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu
-\&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0
+\&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU\s0.
.Sp
With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of
the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate,
integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet
-but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=tsc701\fR, the compiler additionally
+but not in \s-1SPARC\-V7\s0. With \fB\-mcpu=tsc701\fR, the compiler additionally
optimizes it for the \s-1TEMIC\s0 SPARClet chip.
.Sp
With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0
@@ -19818,7 +19828,7 @@ toolchains, \fBnative\fR can also be used.
.IP "\fB\-mno\-v8plus\fR" 4
.IX Item "-mno-v8plus"
.PD
-With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI. \s0 The
+With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+\s0 \s-1ABI\s0. The
difference from the V8 \s-1ABI\s0 is that the global and out registers are
considered 64 bits wide. This is enabled by default on Solaris in 32\-bit
mode for all \s-1SPARC\-V9\s0 processors.
@@ -20273,9 +20283,9 @@ This option suppresses generation of the \f(CW\*(C`CALLT\*(C'\fR instruction for
v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the v850
architecture.
.Sp
-This option is enabled by default when the \s-1RH850 ABI\s0 is
+This option is enabled by default when the \s-1RH850\s0 \s-1ABI\s0 is
in use (see \fB\-mrh850\-abi\fR), and disabled by default when the
-\&\s-1GCC ABI\s0 is in use. If \f(CW\*(C`CALLT\*(C'\fR instructions are being generated
+\&\s-1GCC\s0 \s-1ABI\s0 is in use. If \f(CW\*(C`CALLT\*(C'\fR instructions are being generated
then the C preprocessor symbol \f(CW\*(C`_\|_V850_CALLT_\|_\*(C'\fR is defined.
.IP "\fB\-mrelax\fR" 4
.IX Item "-mrelax"
@@ -20315,7 +20325,7 @@ selected because its use is still experimental.
.IP "\fB\-mghs\fR" 4
.IX Item "-mghs"
.PD
-Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI. \s0 This is the
+Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI\s0. This is the
default. With this version of the \s-1ABI\s0 the following rules apply:
.RS 4
.IP "*" 4
@@ -20340,7 +20350,7 @@ When this version of the \s-1ABI\s0 is enabled the C preprocessor symbol
.RE
.IP "\fB\-mgcc\-abi\fR" 4
.IX Item "-mgcc-abi"
-Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI. \s0 With this
+Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI\s0. With this
version of the \s-1ABI\s0 the following rules apply:
.RS 4
.IP "*" 4
@@ -20435,7 +20445,7 @@ Generate code containing library calls for floating-point.
\&\fB\-msoft\-float\fR changes the calling convention in the output file;
therefore, it is only useful if you compile \fIall\fR of a program with
this option. In particular, you need to compile \fIlibgcc.a\fR, the
-library that comes with \s-1GCC,\s0 with \fB\-msoft\-float\fR in order for
+library that comes with \s-1GCC\s0, with \fB\-msoft\-float\fR in order for
this to work.
.IP "\fB\-mcpu=\fR\fIcpu_type\fR" 4
.IX Item "-mcpu=cpu_type"
@@ -20463,8 +20473,8 @@ the access to general registers. This is the default.
.IP "\fB\-muser\-mode\fR" 4
.IX Item "-muser-mode"
Generate code for the user mode, where the access to some general registers
-is forbidden: on the \s-1GR5,\s0 registers r24 to r31 cannot be accessed in this
-mode; on the \s-1GR6,\s0 only registers r29 to r31 are affected.
+is forbidden: on the \s-1GR5\s0, registers r24 to r31 cannot be accessed in this
+mode; on the \s-1GR6\s0, only registers r29 to r31 are affected.
.PP
\fI\s-1VMS\s0 Options\fR
.IX Subsection "VMS Options"
@@ -20547,10 +20557,10 @@ produces code optimized for the local machine under the constraints
of the selected instruction set.
.IP "\fBi386\fR" 4
.IX Item "i386"
-Original Intel i386 \s-1CPU.\s0
+Original Intel i386 \s-1CPU\s0.
.IP "\fBi486\fR" 4
.IX Item "i486"
-Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.)
+Intel i486 \s-1CPU\s0. (No scheduling is implemented for this chip.)
.IP "\fBi586\fR" 4
.IX Item "i586"
.PD 0
@@ -20560,10 +20570,10 @@ Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.)
Intel Pentium \s-1CPU\s0 with no \s-1MMX\s0 support.
.IP "\fBpentium-mmx\fR" 4
.IX Item "pentium-mmx"
-Intel Pentium \s-1MMX CPU,\s0 based on Pentium core with \s-1MMX\s0 instruction set support.
+Intel Pentium \s-1MMX\s0 \s-1CPU\s0, based on Pentium core with \s-1MMX\s0 instruction set support.
.IP "\fBpentiumpro\fR" 4
.IX Item "pentiumpro"
-Intel Pentium Pro \s-1CPU.\s0
+Intel Pentium Pro \s-1CPU\s0.
.IP "\fBi686\fR" 4
.IX Item "i686"
When used with \fB\-march\fR, the Pentium Pro
@@ -20571,7 +20581,7 @@ instruction set is used, so the code runs on all i686 family chips.
When used with \fB\-mtune\fR, it has the same meaning as \fBgeneric\fR.
.IP "\fBpentium2\fR" 4
.IX Item "pentium2"
-Intel Pentium \s-1II CPU,\s0 based on Pentium Pro core with \s-1MMX\s0 instruction set
+Intel Pentium \s-1II\s0 \s-1CPU\s0, based on Pentium Pro core with \s-1MMX\s0 instruction set
support.
.IP "\fBpentium3\fR" 4
.IX Item "pentium3"
@@ -20579,89 +20589,89 @@ support.
.IP "\fBpentium3m\fR" 4
.IX Item "pentium3m"
.PD
-Intel Pentium \s-1III CPU,\s0 based on Pentium Pro core with \s-1MMX\s0 and \s-1SSE\s0 instruction
+Intel Pentium \s-1III\s0 \s-1CPU\s0, based on Pentium Pro core with \s-1MMX\s0 and \s-1SSE\s0 instruction
set support.
.IP "\fBpentium-m\fR" 4
.IX Item "pentium-m"
-Intel Pentium M; low-power version of Intel Pentium \s-1III CPU\s0
-with \s-1MMX, SSE\s0 and \s-1SSE2\s0 instruction set support. Used by Centrino notebooks.
+Intel Pentium M; low-power version of Intel Pentium \s-1III\s0 \s-1CPU\s0
+with \s-1MMX\s0, \s-1SSE\s0 and \s-1SSE2\s0 instruction set support. Used by Centrino notebooks.
.IP "\fBpentium4\fR" 4
.IX Item "pentium4"
.PD 0
.IP "\fBpentium4m\fR" 4
.IX Item "pentium4m"
.PD
-Intel Pentium 4 \s-1CPU\s0 with \s-1MMX, SSE\s0 and \s-1SSE2\s0 instruction set support.
+Intel Pentium 4 \s-1CPU\s0 with \s-1MMX\s0, \s-1SSE\s0 and \s-1SSE2\s0 instruction set support.
.IP "\fBprescott\fR" 4
.IX Item "prescott"
-Improved version of Intel Pentium 4 \s-1CPU\s0 with \s-1MMX, SSE, SSE2\s0 and \s-1SSE3\s0 instruction
+Improved version of Intel Pentium 4 \s-1CPU\s0 with \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0 and \s-1SSE3\s0 instruction
set support.
.IP "\fBnocona\fR" 4
.IX Item "nocona"
-Improved version of Intel Pentium 4 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE,
-SSE2\s0 and \s-1SSE3\s0 instruction set support.
+Improved version of Intel Pentium 4 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0,
+\&\s-1SSE2\s0 and \s-1SSE3\s0 instruction set support.
.IP "\fBcore2\fR" 4
.IX Item "core2"
-Intel Core 2 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3\s0 and \s-1SSSE3\s0
+Intel Core 2 \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0 and \s-1SSSE3\s0
instruction set support.
.IP "\fBnehalem\fR" 4
.IX Item "nehalem"
-Intel Nehalem \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2\s0 and \s-1POPCNT\s0 instruction set support.
+Intel Nehalem \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2 and \s-1POPCNT\s0 instruction set support.
.IP "\fBwestmere\fR" 4
.IX Item "westmere"
-Intel Westmere \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AES\s0 and \s-1PCLMUL\s0 instruction set support.
+Intel Westmere \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AES\s0 and \s-1PCLMUL\s0 instruction set support.
.IP "\fBsandybridge\fR" 4
.IX Item "sandybridge"
-Intel Sandy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AES\s0 and \s-1PCLMUL\s0 instruction set support.
+Intel Sandy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AES\s0 and \s-1PCLMUL\s0 instruction set support.
.IP "\fBivybridge\fR" 4
.IX Item "ivybridge"
-Intel Ivy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND\s0 and F16C
+Intel Ivy Bridge \s-1CPU\s0 with 64\-bit extensions, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0 and F16C
instruction set support.
.IP "\fBhaswell\fR" 4
.IX Item "haswell"
-Intel Haswell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2\s0 and F16C instruction set support.
+Intel Haswell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0 and F16C instruction set support.
.IP "\fBbroadwell\fR" 4
.IX Item "broadwell"
-Intel Broadwell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2, F16C, RDSEED, ADCX\s0 and \s-1PREFETCHW\s0 instruction set support.
+Intel Broadwell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, F16C, \s-1RDSEED\s0, \s-1ADCX\s0 and \s-1PREFETCHW\s0 instruction set support.
.IP "\fBbonnell\fR" 4
.IX Item "bonnell"
-Intel Bonnell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3\s0 and \s-1SSSE3\s0
+Intel Bonnell \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0 and \s-1SSSE3\s0
instruction set support.
.IP "\fBsilvermont\fR" 4
.IX Item "silvermont"
-Intel Silvermont \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3, SSSE3,
-SSE4.1, SSE4.2, POPCNT, AES, PCLMUL\s0 and \s-1RDRND\s0 instruction set support.
+Intel Silvermont \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0,
+\&\s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AES\s0, \s-1PCLMUL\s0 and \s-1RDRND\s0 instruction set support.
.IP "\fBknl\fR" 4
.IX Item "knl"
-Intel Knight's Landing \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE, MMX, SSE, SSE2, SSE3,
-SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA,
-BMI, BMI2, F16C, RDSEED, ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER\s0 and
+Intel Knight's Landing \s-1CPU\s0 with 64\-bit extensions, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0,
+\&\s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1POPCNT\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, \s-1FMA\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, F16C, \s-1RDSEED\s0, \s-1ADCX\s0, \s-1PREFETCHW\s0, \s-1AVX512F\s0, \s-1AVX512PF\s0, \s-1AVX512ER\s0 and
\&\s-1AVX512CD\s0 instruction set support.
.IP "\fBk6\fR" 4
.IX Item "k6"
-\&\s-1AMD K6 CPU\s0 with \s-1MMX\s0 instruction set support.
+\&\s-1AMD\s0 K6 \s-1CPU\s0 with \s-1MMX\s0 instruction set support.
.IP "\fBk6\-2\fR" 4
.IX Item "k6-2"
.PD 0
.IP "\fBk6\-3\fR" 4
.IX Item "k6-3"
.PD
-Improved versions of \s-1AMD K6 CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support.
+Improved versions of \s-1AMD\s0 K6 \s-1CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support.
.IP "\fBathlon\fR" 4
.IX Item "athlon"
.PD 0
.IP "\fBathlon-tbird\fR" 4
.IX Item "athlon-tbird"
.PD
-\&\s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX,\s0 3dNOW!, enhanced 3DNow! and \s-1SSE\s0 prefetch instructions
+\&\s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX\s0, 3dNOW!, enhanced 3DNow! and \s-1SSE\s0 prefetch instructions
support.
.IP "\fBathlon\-4\fR" 4
.IX Item "athlon-4"
@@ -20671,7 +20681,7 @@ support.
.IP "\fBathlon-mp\fR" 4
.IX Item "athlon-mp"
.PD
-Improved \s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX,\s0 3DNow!, enhanced 3DNow! and full \s-1SSE\s0
+Improved \s-1AMD\s0 Athlon \s-1CPU\s0 with \s-1MMX\s0, 3DNow!, enhanced 3DNow! and full \s-1SSE\s0
instruction set support.
.IP "\fBk8\fR" 4
.IX Item "k8"
@@ -20683,9 +20693,9 @@ instruction set support.
.IP "\fBathlon-fx\fR" 4
.IX Item "athlon-fx"
.PD
-Processors based on the \s-1AMD K8\s0 core with x86\-64 instruction set support,
+Processors based on the \s-1AMD\s0 K8 core with x86\-64 instruction set support,
including the \s-1AMD\s0 Opteron, Athlon 64, and Athlon 64 \s-1FX\s0 processors.
-(This supersets \s-1MMX, SSE, SSE2,\s0 3DNow!, enhanced 3DNow! and 64\-bit
+(This supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, 3DNow!, enhanced 3DNow! and 64\-bit
instruction set extensions.)
.IP "\fBk8\-sse3\fR" 4
.IX Item "k8-sse3"
@@ -20695,7 +20705,7 @@ instruction set extensions.)
.IP "\fBathlon64\-sse3\fR" 4
.IX Item "athlon64-sse3"
.PD
-Improved versions of \s-1AMD K8\s0 cores with \s-1SSE3\s0 instruction set support.
+Improved versions of \s-1AMD\s0 K8 cores with \s-1SSE3\s0 instruction set support.
.IP "\fBamdfam10\fR" 4
.IX Item "amdfam10"
.PD 0
@@ -20703,56 +20713,56 @@ Improved versions of \s-1AMD K8\s0 cores with \s-1SSE3\s0 instruction set suppor
.IX Item "barcelona"
.PD
CPUs based on \s-1AMD\s0 Family 10h cores with x86\-64 instruction set support. (This
-supersets \s-1MMX, SSE, SSE2, SSE3, SSE4A,\s0 3DNow!, enhanced 3DNow!, \s-1ABM\s0 and 64\-bit
+supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, 3DNow!, enhanced 3DNow!, \s-1ABM\s0 and 64\-bit
instruction set extensions.)
.IP "\fBbdver1\fR" 4
.IX Item "bdver1"
CPUs based on \s-1AMD\s0 Family 15h cores with x86\-64 instruction set support. (This
-supersets \s-1FMA4, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A,
-SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions.)
+supersets \s-1FMA4\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0,
+\&\s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set extensions.)
.IP "\fBbdver2\fR" 4
.IX Item "bdver2"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, TBM, F16C, FMA, FMA4, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX,
-SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set
+supersets \s-1BMI\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0,
+\&\s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set
extensions.)
.IP "\fBbdver3\fR" 4
.IX Item "bdver3"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES,
-PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and
+supersets \s-1BMI\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1FSGSBASE\s0, \s-1AVX\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1AES\s0,
+\&\s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1SSE4\s0.2, \s-1ABM\s0 and
64\-bit instruction set extensions.
.IP "\fBbdver4\fR" 4
.IX Item "bdver4"
\&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This
-supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP,
-AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1,
-SSE4.2, ABM\s0 and 64\-bit instruction set extensions.
+supersets \s-1BMI\s0, \s-1BMI2\s0, \s-1TBM\s0, F16C, \s-1FMA\s0, \s-1FMA4\s0, \s-1FSGSBASE\s0, \s-1AVX\s0, \s-1AVX2\s0, \s-1XOP\s0, \s-1LWP\s0,
+\&\s-1AES\s0, \s-1PCL_MUL\s0, \s-1CX16\s0, \s-1MOVBE\s0, \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1,
+\&\s-1SSE4\s0.2, \s-1ABM\s0 and 64\-bit instruction set extensions.
.IP "\fBbtver1\fR" 4
.IX Item "btver1"
CPUs based on \s-1AMD\s0 Family 14h cores with x86\-64 instruction set support. (This
-supersets \s-1MMX, SSE, SSE2, SSE3, SSSE3, SSE4A, CX16, ABM\s0 and 64\-bit
+supersets \s-1MMX\s0, \s-1SSE\s0, \s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0, \s-1SSE4A\s0, \s-1CX16\s0, \s-1ABM\s0 and 64\-bit
instruction set extensions.)
.IP "\fBbtver2\fR" 4
.IX Item "btver2"
CPUs based on \s-1AMD\s0 Family 16h cores with x86\-64 instruction set support. This
-includes \s-1MOVBE, F16C, BMI, AVX, PCL_MUL, AES, SSE4.2, SSE4.1, CX16, ABM,
-SSE4A, SSSE3, SSE3, SSE2, SSE, MMX\s0 and 64\-bit instruction set extensions.
+includes \s-1MOVBE\s0, F16C, \s-1BMI\s0, \s-1AVX\s0, \s-1PCL_MUL\s0, \s-1AES\s0, \s-1SSE4\s0.2, \s-1SSE4\s0.1, \s-1CX16\s0, \s-1ABM\s0,
+\&\s-1SSE4A\s0, \s-1SSSE3\s0, \s-1SSE3\s0, \s-1SSE2\s0, \s-1SSE\s0, \s-1MMX\s0 and 64\-bit instruction set extensions.
.IP "\fBwinchip\-c6\fR" 4
.IX Item "winchip-c6"
-\&\s-1IDT\s0 WinChip C6 \s-1CPU,\s0 dealt in same way as i486 with additional \s-1MMX\s0 instruction
+\&\s-1IDT\s0 WinChip C6 \s-1CPU\s0, dealt in same way as i486 with additional \s-1MMX\s0 instruction
set support.
.IP "\fBwinchip2\fR" 4
.IX Item "winchip2"
-\&\s-1IDT\s0 WinChip 2 \s-1CPU,\s0 dealt in same way as i486 with additional \s-1MMX\s0 and 3DNow!
+\&\s-1IDT\s0 WinChip 2 \s-1CPU\s0, dealt in same way as i486 with additional \s-1MMX\s0 and 3DNow!
instruction set support.
.IP "\fBc3\fR" 4
.IX Item "c3"
-\&\s-1VIA C3 CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support. (No scheduling is
+\&\s-1VIA\s0 C3 \s-1CPU\s0 with \s-1MMX\s0 and 3DNow! instruction set support. (No scheduling is
implemented for this chip.)
.IP "\fBc3\-2\fR" 4
.IX Item "c3-2"
-\&\s-1VIA C3\-2 \s0(Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support.
+\&\s-1VIA\s0 C3\-2 (Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support.
(No scheduling is
implemented for this chip.)
.IP "\fBgeode\fR" 4
@@ -20786,7 +20796,7 @@ of your application will have, then you should use this option.
.Sp
As new processors are deployed in the marketplace, the behavior of this
option will change. Therefore, if you upgrade to a newer version of
-\&\s-1GCC,\s0 code generation controlled by this option will change to reflect
+\&\s-1GCC\s0, code generation controlled by this option will change to reflect
the processors
that are most common at the time that version of \s-1GCC\s0 is released.
.Sp
@@ -20798,7 +20808,7 @@ processors) for which the code is optimized.
.IP "\fBintel\fR" 4
.IX Item "intel"
Produce code optimized for the most current Intel processors, which are
-Haswell and Silvermont for this version of \s-1GCC. \s0 If you know the \s-1CPU\s0
+Haswell and Silvermont for this version of \s-1GCC\s0. If you know the \s-1CPU\s0
on which your code will run, then you should use the corresponding
\&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR.
But, if you want your application performs better on both Haswell and
@@ -20806,7 +20816,7 @@ Silvermont, then you should use this option.
.Sp
As new Intel processors are deployed in the marketplace, the behavior of
this option will change. Therefore, if you upgrade to a newer version of
-\&\s-1GCC,\s0 code generation controlled by this option will change to reflect
+\&\s-1GCC\s0, code generation controlled by this option will change to reflect
the most current Intel processors at the time that version of \s-1GCC\s0 is
released.
.Sp
@@ -20891,7 +20901,7 @@ comparison is unordered.
.IX Item "-msoft-float"
Generate output containing library calls for floating point.
.Sp
-\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC.\s0
+\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC\s0.
Normally the facilities of the machine's usual C compiler are used, but
this can't be done directly in cross-compilation. You must make your
own arrangements to provide suitable library functions for
@@ -20906,8 +20916,8 @@ Do not use the \s-1FPU\s0 registers for return values of functions.
.Sp
The usual calling convention has functions return values of types
\&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there
-is no \s-1FPU. \s0 The idea is that the operating system should emulate
-an \s-1FPU.\s0
+is no \s-1FPU\s0. The idea is that the operating system should emulate
+an \s-1FPU\s0.
.Sp
The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned
in ordinary \s-1CPU\s0 registers instead.
@@ -20915,7 +20925,7 @@ in ordinary \s-1CPU\s0 registers instead.
.IX Item "-mno-fancy-math-387"
Some 387 emulators do not support the \f(CW\*(C`sin\*(C'\fR, \f(CW\*(C`cos\*(C'\fR and
\&\f(CW\*(C`sqrt\*(C'\fR instructions for the 387. Specify this option to avoid
-generating those instructions. This option is the default on FreeBSD,
+generating those instructions. This option is the default on
OpenBSD and NetBSD. This option is overridden when \fB\-march\fR
indicates that the target \s-1CPU\s0 always has an \s-1FPU\s0 and so the
instruction does not need emulation. These
@@ -20952,7 +20962,7 @@ so \fB\-m96bit\-long\-double\fR is the default in 32\-bit mode.
.Sp
Modern architectures (Pentium and newer) prefer \f(CW\*(C`long double\*(C'\fR
to be aligned to an 8\- or 16\-byte boundary. In arrays or structures
-conforming to the \s-1ABI,\s0 this is not possible. So specifying
+conforming to the \s-1ABI\s0, this is not possible. So specifying
\&\fB\-m128bit\-long\-double\fR aligns \f(CW\*(C`long double\*(C'\fR
to a 16\-byte boundary by padding the \f(CW\*(C`long double\*(C'\fR with an additional
32\-bit zero.
@@ -20963,7 +20973,7 @@ its \s-1ABI\s0 specifies that \f(CW\*(C`long double\*(C'\fR is aligned on 16\-by
Notice that neither of these options enable any extra precision over the x87
standard of 80 bits for a \f(CW\*(C`long double\*(C'\fR.
.Sp
-\&\fBWarning:\fR if you override the default value for your target \s-1ABI,\s0 this
+\&\fBWarning:\fR if you override the default value for your target \s-1ABI\s0, this
changes the size of
structures and arrays containing \f(CW\*(C`long double\*(C'\fR variables,
as well as modifying the function calling convention for functions taking
@@ -20983,7 +20993,7 @@ type. This is the default for 32\-bit Bionic C library. A size
of 128 bits makes the \f(CW\*(C`long double\*(C'\fR type equivalent to the
\&\f(CW\*(C`_\|_float128\*(C'\fR type. This is the default for 64\-bit Bionic C library.
.Sp
-\&\fBWarning:\fR if you override the default value for your target \s-1ABI,\s0 this
+\&\fBWarning:\fR if you override the default value for your target \s-1ABI\s0, this
changes the size of
structures and arrays containing \f(CW\*(C`long double\*(C'\fR variables,
as well as modifying the function calling convention for functions taking
@@ -20992,7 +21002,7 @@ with code compiled without that switch.
.IP "\fB\-malign\-data=\fR\fItype\fR" 4
.IX Item "-malign-data=type"
Control how \s-1GCC\s0 aligns variables. Supported values for \fItype\fR are
-\&\fBcompat\fR uses increased alignment value compatible uses \s-1GCC 4.8\s0
+\&\fBcompat\fR uses increased alignment value compatible uses \s-1GCC\s0 4.8
and earlier, \fBabi\fR uses alignment value as specified by the
psABI, and \fBcacheline\fR uses increased alignment value to match
the cache line size. \fBcompat\fR is the default.
@@ -21054,7 +21064,7 @@ Studio compilers until version 12. Later compiler versions (starting
with Studio 12 Update@tie{}1) follow the \s-1ABI\s0 used by other x86 targets, which
is the default on Solaris@tie{}10 and later. \fIOnly\fR use this option if
you need to remain compatible with existing code produced by those
-previous compiler versions or older versions of \s-1GCC.\s0
+previous compiler versions or older versions of \s-1GCC\s0.
.IP "\fB\-mpc32\fR" 4
.IX Item "-mpc32"
.PD 0
@@ -21115,7 +21125,7 @@ the one specified by \fB\-mpreferred\-stack\-boundary\fR is used.
.Sp
On Pentium and Pentium Pro, \f(CW\*(C`double\*(C'\fR and \f(CW\*(C`long double\*(C'\fR values
should be aligned to an 8\-byte boundary (see \fB\-malign\-double\fR) or
-suffer significant run time performance penalties. On Pentium \s-1III,\s0 the
+suffer significant run time performance penalties. On Pentium \s-1III\s0, the
Streaming \s-1SIMD\s0 Extension (\s-1SSE\s0) data type \f(CW\*(C`_\|_m128\*(C'\fR may not work
properly if it is not 16\-byte aligned.
.Sp
@@ -21216,11 +21226,13 @@ preferred alignment to \fB\-mpreferred\-stack\-boundary=2\fR.
.IX Item "-mtbm"
.IP "\fB\-mmpx\fR" 4
.IX Item "-mmpx"
+.IP "\fB\-mmwaitx\fR" 4
+.IX Item "-mmwaitx"
.PD
-These switches enable the use of instructions in the \s-1MMX, SSE,
-SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER, AVX512CD,
-SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A, FMA4, XOP, LWP, ABM,
-BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX\s0 or 3DNow!
+These switches enable the use of instructions in the \s-1MMX\s0, \s-1SSE\s0,
+\&\s-1SSE2\s0, \s-1SSE3\s0, \s-1SSSE3\s0, \s-1SSE4\s0.1, \s-1AVX\s0, \s-1AVX2\s0, \s-1AVX512F\s0, \s-1AVX512PF\s0, \s-1AVX512ER\s0, \s-1AVX512CD\s0,
+\&\s-1SHA\s0, \s-1AES\s0, \s-1PCLMUL\s0, \s-1FSGSBASE\s0, \s-1RDRND\s0, F16C, \s-1FMA\s0, \s-1SSE4A\s0, \s-1FMA4\s0, \s-1XOP\s0, \s-1LWP\s0, \s-1ABM\s0,
+\&\s-1BMI\s0, \s-1BMI2\s0, \s-1FXSR\s0, \s-1XSAVE\s0, \s-1XSAVEOPT\s0, \s-1LZCNT\s0, \s-1RTM\s0, \s-1MPX\s0, \s-1MWAITX\s0 or 3DNow!
extended instruction sets. Each has a corresponding \fB\-mno\-\fR option
to disable use of these instructions.
.Sp
@@ -21297,7 +21309,7 @@ This option enables generation of \f(CW\*(C`SAHF\*(C'\fR instructions in 64\-bit
Early Intel Pentium 4 CPUs with Intel 64 support,
prior to the introduction of Pentium 4 G1 step in December 2005,
lacked the \f(CW\*(C`LAHF\*(C'\fR and \f(CW\*(C`SAHF\*(C'\fR instructions
-which are supported by \s-1AMD64.\s0
+which are supported by \s-1AMD64\s0.
These are load and store instructions, respectively, for certain status flags.
In 64\-bit mode, the \f(CW\*(C`SAHF\*(C'\fR instruction is used to optimize \f(CW\*(C`fmod\*(C'\fR,
\&\f(CW\*(C`drem\*(C'\fR, and \f(CW\*(C`remainder\*(C'\fR built-in functions;
@@ -21373,7 +21385,7 @@ external library. Supported values for \fItype\fR are \fBsvml\fR
for the Intel short
vector math library and \fBacml\fR for the \s-1AMD\s0 math core library.
To use this option, both \fB\-ftree\-vectorize\fR and
-\&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML \s0
+\&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML\s0
ABI-compatible library must be specified at link time.
.Sp
\&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR,
@@ -21396,7 +21408,7 @@ when \fB\-mveclibabi=acml\fR is used.
.IX Item "-mabi=name"
Generate code for the specified calling convention. Permissible values
are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and
-\&\fBms\fR for the Microsoft \s-1ABI. \s0 The default is to use the Microsoft
+\&\fBms\fR for the Microsoft \s-1ABI\s0. The default is to use the Microsoft
\&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems.
You can control this behavior for specific functions by
using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR.
@@ -21511,7 +21523,7 @@ or whether the thread base pointer must be added. Whether or not this
is valid depends on the operating system, and whether it maps the
segment to cover the entire \s-1TLS\s0 area.
.Sp
-For systems that use the \s-1GNU C\s0 Library, the default is on.
+For systems that use the \s-1GNU\s0 C Library, the default is on.
.IP "\fB\-msse2avx\fR" 4
.IX Item "-msse2avx"
.PD 0
@@ -21562,7 +21574,7 @@ register when there are no variable arguments passed in vector registers.
\&\fBWarning:\fR Since \s-1RAX\s0 register is used to avoid unnecessarily
saving vector registers on stack when passing variable arguments, the
impacts of this option are callees may waste some stack space,
-misbehave or jump to a random location. \s-1GCC 4.4\s0 or newer don't have
+misbehave or jump to a random location. \s-1GCC\s0 4.4 or newer don't have
those issues, regardless the \s-1RAX\s0 register value.
.IP "\fB\-m8bit\-idiv\fR" 4
.IX Item "-m8bit-idiv"
@@ -21706,7 +21718,7 @@ appropriately.
This option is available for MinGW targets. It specifies that
the executable flag for the stack used by nested functions isn't
set. This is necessary for binaries running in kernel mode of
-Microsoft Windows, as there the User32 \s-1API,\s0 which is used to set executable
+Microsoft Windows, as there the User32 \s-1API\s0, which is used to set executable
privileges, isn't available.
.IP "\fB\-fwritable\-relocated\-rdata\fR" 4
.IX Item "-fwritable-relocated-rdata"
@@ -21791,7 +21803,7 @@ kernel code.
These options control the treatment of literal pools. The default is
\&\fB\-mno\-text\-section\-literals\fR, which places literals in a separate
section in the output file. This allows the literal pool to be placed
-in a data \s-1RAM/ROM,\s0 and it also allows the linker to combine literal
+in a data \s-1RAM/ROM\s0, and it also allows the linker to combine literal
pools from separate object files to remove redundant literals and
improve code size. With \fB\-mtext\-section\-literals\fR, the literals
are interspersed in the text section in order to keep them as close as
@@ -21837,7 +21849,7 @@ every cross-file call, not just those that really are out of range.
.IX Subsection "zSeries Options"
.PP
These are listed under
-.SS "Options for Code Generation Conventions"
+.Sh "Options for Code Generation Conventions"
.IX Subsection "Options for Code Generation Conventions"
These machine-independent options control the interface conventions
used in code generation.
@@ -21976,7 +21988,7 @@ You normally do not need to enable this option; instead, a language processor
that needs this handling enables it on your behalf.
.IP "\fB\-fasynchronous\-unwind\-tables\fR" 4
.IX Item "-fasynchronous-unwind-tables"
-Generate unwind table in \s-1DWARF 2\s0 format, if supported by target machine. The
+Generate unwind table in \s-1DWARF\s0 2 format, if supported by target machine. The
table is exact at each instruction boundary, so it can be used for stack
unwinding from asynchronous events (such as debugger or garbage collector).
.IP "\fB\-fno\-gnu\-unique\fR" 4
@@ -22047,7 +22059,7 @@ Use it to conform to a non-default application binary interface.
.IX Item "-fshort-wchar"
Override the underlying type for \f(CW\*(C`wchar_t\*(C'\fR to be \f(CW\*(C`short
unsigned int\*(C'\fR instead of the default for the target. This option is
-useful for building programs to run under \s-1WINE.\s0
+useful for building programs to run under \s-1WINE\s0.
.Sp
\&\fBWarning:\fR the \fB\-fshort\-wchar\fR switch causes \s-1GCC\s0 to generate
code that is not binary compatible with code generated without that switch.
@@ -22060,7 +22072,7 @@ such variables in different compilation units by placing the variables
in a common block.
This is the behavior specified by \fB\-fcommon\fR, and is the default
for \s-1GCC\s0 on most targets.
-On the other hand, this behavior is not required by \s-1ISO C,\s0 and on some
+On the other hand, this behavior is not required by \s-1ISO\s0 C, and on some
targets may carry a speed or code size penalty on variable references.
The \fB\-fno\-common\fR option specifies that the compiler should place
uninitialized global variables in the data section of the object file,
@@ -22116,11 +22128,11 @@ the \s-1GOT\s0 size for the linked executable exceeds a machine-specific
maximum size, you get an error message from the linker indicating that
\&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR
instead. (These maximums are 8k on the \s-1SPARC\s0 and 32k
-on the m68k and \s-1RS/6000. \s0 The x86 has no such limit.)
+on the m68k and \s-1RS/6000\s0. The x86 has no such limit.)
.Sp
Position-independent code requires special support, and therefore works
only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V
-but not for the Sun 386i. Code generated for the \s-1IBM RS/6000\s0 is always
+but not for the Sun 386i. Code generated for the \s-1IBM\s0 \s-1RS/6000\s0 is always
position-independent.
.Sp
When this flag is set, the macros \f(CW\*(C`_\|_pic_\|_\*(C'\fR and \f(CW\*(C`_\|_PIC_\|_\*(C'\fR
@@ -22130,7 +22142,7 @@ are defined to 1.
If supported for the target machine, emit position-independent code,
suitable for dynamic linking and avoiding any limit on the size of the
global offset table. This option makes a difference on the m68k,
-PowerPC and \s-1SPARC.\s0
+PowerPC and \s-1SPARC\s0.
.Sp
Position-independent code requires special support, and therefore works
only on certain machines.
@@ -22280,7 +22292,7 @@ name, such as \f(CW\*(C`vector<int> blah(const vector<int> &)\*(C'\fR, not the
internal mangled name (e.g., \f(CW\*(C`_Z4blahRSt6vectorIiSaIiEE\*(C'\fR). The
match is done on substrings: if the \fIsym\fR parameter is a substring
of the function name, it is considered to be a match. For C99 and \*(C+
-extended identifiers, the function name must be given in \s-1UTF\-8,\s0 not
+extended identifiers, the function name must be given in \s-1UTF\-8\s0, not
using universal character names.
.IP "\fB\-fstack\-check\fR" 4
.IX Item "-fstack-check"
@@ -22419,7 +22431,7 @@ always specify visibility when it is not the default; i.e., declarations
only for use within the local \s-1DSO\s0 should \fBalways\fR be marked explicitly
as hidden as so to avoid \s-1PLT\s0 indirection overheads\-\-\-making this
abundantly clear also aids readability and self-documentation of the code.
-Note that due to \s-1ISO \*(C+\s0 specification requirements, \f(CW\*(C`operator new\*(C'\fR and
+Note that due to \s-1ISO\s0 \*(C+ specification requirements, \f(CW\*(C`operator new\*(C'\fR and
\&\f(CW\*(C`operator delete\*(C'\fR must always be of default visibility.
.Sp
Be aware that headers from outside your project, in particular system
@@ -22431,7 +22443,7 @@ before including any such headers.
\&\f(CW\*(C`extern\*(C'\fR declarations are not affected by \fB\-fvisibility\fR, so
a lot of code can be recompiled with \fB\-fvisibility=hidden\fR with
no modifications. However, this means that calls to \f(CW\*(C`extern\*(C'\fR
-functions with no explicit visibility use the \s-1PLT,\s0 so it is more
+functions with no explicit visibility use the \s-1PLT\s0, so it is more
effective to use \f(CW\*(C`_\|_attribute ((visibility))\*(C'\fR and/or
\&\f(CW\*(C`#pragma GCC visibility\*(C'\fR to tell the compiler which \f(CW\*(C`extern\*(C'\fR
declarations should be treated as hidden.
@@ -22493,7 +22505,7 @@ aspects of the compilation environment.
Note that you can also specify places to search using options such as
\&\fB\-B\fR, \fB\-I\fR and \fB\-L\fR. These
take precedence over places specified using environment variables, which
-in turn take precedence over those specified by the configuration of \s-1GCC.\s0
+in turn take precedence over those specified by the configuration of \s-1GCC\s0.
.IP "\fB\s-1LANG\s0\fR" 4
.IX Item "LANG"
.PD 0
@@ -22510,7 +22522,7 @@ national conventions. \s-1GCC\s0 inspects the locale categories
\&\fB\s-1LC_CTYPE\s0\fR and \fB\s-1LC_MESSAGES\s0\fR if it has been configured to do
so. These locale categories can be set to any value supported by your
installation. A typical value is \fBen_GB.UTF\-8\fR for English in the United
-Kingdom encoded in \s-1UTF\-8.\s0
+Kingdom encoded in \s-1UTF\-8\s0.
.Sp
The \fB\s-1LC_CTYPE\s0\fR environment variable specifies character
classification. \s-1GCC\s0 uses it to determine the character boundaries in
@@ -22690,7 +22702,7 @@ and the Info entries for \fIgcc\fR, \fIcpp\fR, \fIas\fR,
.IX Header "AUTHOR"
See the Info entry for \fBgcc\fR, or
<\fBhttp://gcc.gnu.org/onlinedocs/gcc/Contributors.html\fR>,
-for contributors to \s-1GCC.\s0
+for contributors to \s-1GCC\s0.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright (c) 1988\-2015 Free Software Foundation, Inc.
diff --git a/gcc/doc/gcc.info b/gcc/doc/gcc.info
index f263c5092e..334d733c8d 100644
--- a/gcc/doc/gcc.info
+++ b/gcc/doc/gcc.info
@@ -1,4 +1,5 @@
-This is gcc.info, produced by makeinfo version 5.2 from gcc.texi.
+This is doc/gcc.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/doc/gcc.texi.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -16,17 +17,17 @@ Free Documentation License".
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU software.
-Copies published by the Free Software Foundation raise funds for GNU
-development.
+ You have freedom to copy and modify this GNU Manual, like GNU
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
* gcc: (gcc). The GNU Compiler Collection.
* g++: (gcc). The GNU C++ compiler.
-* gcov: (gcc) Gcov. 'gcov'--a test coverage program.
-* gcov-tool: (gcc) Gcov-tool. 'gcov-tool'--an offline gcda profile processing program.
+* gcov: (gcc) Gcov. `gcov'--a test coverage program.
+* gcov-tool: (gcc) Gcov-tool. `gcov-tool'--an offline gcda profile processing program.
END-INFO-DIR-ENTRY
-
This file documents the use of the GNU compilers.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -45,9 +46,10 @@ Free Documentation License".
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU software.
-Copies published by the Free Software Foundation raise funds for GNU
-development.
+ You have freedom to copy and modify this GNU Manual, like GNU
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+

File: gcc.info, Node: Top, Next: G++ and GCC, Up: (DIR)
@@ -57,7 +59,7 @@ Introduction
This manual documents how to use the GNU compilers, as well as their
features and incompatibilities, and how to report bugs. It corresponds
-to the compilers (GCC) version 5.1.0. The internals of the GNU
+to the compilers (GCC) version 5.2.0. The internals of the GNU
compilers, including how to port them to new targets and some
information about how to write front ends for new languages, are
documented in a separate manual. *Note Introduction: (gccint)Top.
@@ -66,15 +68,15 @@ documented in a separate manual. *Note Introduction: (gccint)Top.
* G++ and GCC:: You can compile C or C++ programs.
* Standards:: Language standards supported by GCC.
-* Invoking GCC:: Command options supported by 'gcc'.
+* Invoking GCC:: Command options supported by `gcc'.
* C Implementation:: How GCC implements the ISO C specification.
* C++ Implementation:: How GCC implements the ISO C++ specification.
* C Extensions:: GNU extensions to the C language family.
* C++ Extensions:: GNU extensions to the C++ language.
* Objective-C:: GNU Objective-C runtime features.
* Compatibility:: Binary Compatibility
-* Gcov:: 'gcov'--a test coverage program.
-* Gcov-tool:: 'gcov-tool'--an offline gcda profile processing program.
+* Gcov:: `gcov'---a test coverage program.
+* Gcov-tool:: `gcov-tool'---an offline gcda profile processing program.
* Trouble:: If you have trouble using GCC.
* Bugs:: How, why and where to report bugs.
* Service:: How To Get Help with GCC
@@ -92,7 +94,7 @@ documented in a separate manual. *Note Introduction: (gccint)Top.
* Keyword Index:: Index of concepts and symbol names.

-File: gcc.info, Node: G++ and GCC, Next: Standards, Up: Top
+File: gcc.info, Node: G++ and GCC, Next: Standards, Prev: Top, Up: Top
1 Programming Languages Supported by GCC
****************************************
@@ -155,12 +157,12 @@ published in 1990. This standard was ratified as an ISO standard
(ISO/IEC 9899:1990) later in 1990. There were no technical differences
between these publications, although the sections of the ANSI standard
were renumbered and became clauses in the ISO standard. This standard,
-in both its forms, is commonly known as "C89", or occasionally as "C90",
-from the dates of ratification. The ANSI standard, but not the ISO
-standard, also came with a Rationale document. To select this standard
-in GCC, use one of the options '-ansi', '-std=c90' or
-'-std=iso9899:1990'; to obtain all the diagnostics required by the
-standard, you should also specify '-pedantic' (or '-pedantic-errors' if
+in both its forms, is commonly known as "C89", or occasionally as
+"C90", from the dates of ratification. The ANSI standard, but not the
+ISO standard, also came with a Rationale document. To select this
+standard in GCC, use one of the options `-ansi', `-std=c90' or
+`-std=iso9899:1990'; to obtain all the diagnostics required by the
+standard, you should also specify `-pedantic' (or `-pedantic-errors' if
you want them to be errors rather than warnings). *Note Options
Controlling C Dialect: C Dialect Options.
@@ -169,19 +171,19 @@ Corrigenda published in 1994 and 1996. GCC does not support the
uncorrected version.
An amendment to the 1990 standard was published in 1995. This
-amendment added digraphs and '__STDC_VERSION__' to the language, but
+amendment added digraphs and `__STDC_VERSION__' to the language, but
otherwise concerned the library. This amendment is commonly known as
"AMD1"; the amended standard is sometimes known as "C94" or "C95". To
-select this standard in GCC, use the option '-std=iso9899:199409' (with,
-as for other standard versions, '-pedantic' to receive all required
-diagnostics).
+select this standard in GCC, use the option `-std=iso9899:199409'
+(with, as for other standard versions, `-pedantic' to receive all
+required diagnostics).
A new edition of the ISO C standard was published in 1999 as ISO/IEC
9899:1999, and is commonly known as "C99". GCC has substantially
complete support for this standard version; see
-<http://gcc.gnu.org/c99status.html> for details. To select this
-standard, use '-std=c99' or '-std=iso9899:1999'. (While in development,
-drafts of this standard version were referred to as "C9X".)
+`http://gcc.gnu.org/c99status.html' for details. To select this
+standard, use `-std=c99' or `-std=iso9899:1999'. (While in
+development, drafts of this standard version were referred to as "C9X".)
Errors in the 1999 ISO C standard were corrected in three Technical
Corrigenda published in 2001, 2004 and 2007. GCC does not support the
@@ -189,38 +191,39 @@ uncorrected version.
A fourth version of the C standard, known as "C11", was published in
2011 as ISO/IEC 9899:2011. GCC has substantially complete support for
-this standard, enabled with '-std=c11' or '-std=iso9899:2011'. (While
+this standard, enabled with `-std=c11' or `-std=iso9899:2011'. (While
in development, drafts of this standard version were referred to as
"C1X".)
- By default, GCC provides some extensions to the C language that on rare
-occasions conflict with the C standard. *Note Extensions to the C
-Language Family: C Extensions. Use of the '-std' options listed above
+ By default, GCC provides some extensions to the C language that on
+rare occasions conflict with the C standard. *Note Extensions to the C
+Language Family: C Extensions. Use of the `-std' options listed above
will disable these extensions where they conflict with the C standard
version selected. You may also select an extended version of the C
-language explicitly with '-std=gnu90' (for C90 with GNU extensions),
-'-std=gnu99' (for C99 with GNU extensions) or '-std=gnu11' (for C11 with
-GNU extensions). The default, if no C language dialect options are
-given, is '-std=gnu11'. Some features that are part of the C99 standard
-are accepted as extensions in C90 mode, and some features that are part
-of the C11 standard are accepted as extensions in C90 and C99 modes.
+language explicitly with `-std=gnu90' (for C90 with GNU extensions),
+`-std=gnu99' (for C99 with GNU extensions) or `-std=gnu11' (for C11
+with GNU extensions). The default, if no C language dialect options
+are given, is `-std=gnu11'. Some features that are part of the C99
+standard are accepted as extensions in C90 mode, and some features that
+are part of the C11 standard are accepted as extensions in C90 and C99
+modes.
The ISO C standard defines (in clause 4) two classes of conforming
-implementation. A "conforming hosted implementation" supports the whole
-standard including all the library facilities; a "conforming
-freestanding implementation" is only required to provide certain library
-facilities: those in '<float.h>', '<limits.h>', '<stdarg.h>', and
-'<stddef.h>'; since AMD1, also those in '<iso646.h>'; since C99, also
-those in '<stdbool.h>' and '<stdint.h>'; and since C11, also those in
-'<stdalign.h>' and '<stdnoreturn.h>'. In addition, complex types, added
-in C99, are not required for freestanding implementations. The standard
-also defines two environments for programs, a "freestanding
+implementation. A "conforming hosted implementation" supports the
+whole standard including all the library facilities; a "conforming
+freestanding implementation" is only required to provide certain
+library facilities: those in `<float.h>', `<limits.h>', `<stdarg.h>',
+and `<stddef.h>'; since AMD1, also those in `<iso646.h>'; since C99,
+also those in `<stdbool.h>' and `<stdint.h>'; and since C11, also those
+in `<stdalign.h>' and `<stdnoreturn.h>'. In addition, complex types,
+added in C99, are not required for freestanding implementations. The
+standard also defines two environments for programs, a "freestanding
environment", required of all implementations and which may not have
library facilities beyond those required of freestanding
implementations, where the handling of program startup and termination
are implementation-defined, and a "hosted environment", which is not
required, in which all the library facilities are provided and startup
-is through a function 'int main (void)' or 'int main (int, char *[])'.
+is through a function `int main (void)' or `int main (int, char *[])'.
An OS kernel would be a freestanding environment; a program using the
facilities of an operating system would normally be in a hosted
implementation.
@@ -228,11 +231,11 @@ implementation.
GCC aims towards being usable as a conforming freestanding
implementation, or as the compiler for a conforming hosted
implementation. By default, it will act as the compiler for a hosted
-implementation, defining '__STDC_HOSTED__' as '1' and presuming that
+implementation, defining `__STDC_HOSTED__' as `1' and presuming that
when the names of ISO C functions are used, they have the semantics
defined in the standard. To make it act as a conforming freestanding
implementation for a freestanding environment, use the option
-'-ffreestanding'; it will then define '__STDC_HOSTED__' to '0' and not
+`-ffreestanding'; it will then define `__STDC_HOSTED__' to `0' and not
make assumptions about the meanings of function names from the standard
library, with exceptions noted below. To build an OS kernel, you may
well still need to make your own arrangements for linking and startup.
@@ -241,18 +244,19 @@ well still need to make your own arrangements for linking and startup.
GCC does not provide the library facilities required only of hosted
implementations, nor yet all the facilities required by C99 of
freestanding implementations on all platforms; to use the facilities of
-a hosted environment, you will need to find them elsewhere (for example,
-in the GNU C library). *Note Standard Libraries: Standard Libraries.
+a hosted environment, you will need to find them elsewhere (for
+example, in the GNU C library). *Note Standard Libraries: Standard
+Libraries.
Most of the compiler support routines used by GCC are present in
-'libgcc', but there are a few exceptions. GCC requires the freestanding
-environment provide 'memcpy', 'memmove', 'memset' and 'memcmp'.
-Finally, if '__builtin_trap' is used, and the target does not implement
-the 'trap' pattern, then GCC will emit a call to 'abort'.
+`libgcc', but there are a few exceptions. GCC requires the
+freestanding environment provide `memcpy', `memmove', `memset' and
+`memcmp'. Finally, if `__builtin_trap' is used, and the target does
+not implement the `trap' pattern, then GCC will emit a call to `abort'.
For references to Technical Corrigenda, Rationale documents and
information concerning the history of C that is available online, see
-<http://gcc.gnu.org/readings.html>
+`http://gcc.gnu.org/readings.html'
2.2 C++ Language
================
@@ -262,100 +266,102 @@ experimental support for the second ISO C++ standard (2011).
The original ISO C++ standard was published as the ISO standard
(ISO/IEC 14882:1998) and amended by a Technical Corrigenda published in
-2003 (ISO/IEC 14882:2003). These standards are referred to as C++98 and
-C++03, respectively. GCC implements the majority of C++98 ('export' is
+2003 (ISO/IEC 14882:2003). These standards are referred to as C++98 and
+C++03, respectively. GCC implements the majority of C++98 (`export' is
a notable exception) and most of the changes in C++03. To select this
-standard in GCC, use one of the options '-ansi', '-std=c++98', or
-'-std=c++03'; to obtain all the diagnostics required by the standard,
-you should also specify '-pedantic' (or '-pedantic-errors' if you want
+standard in GCC, use one of the options `-ansi', `-std=c++98', or
+`-std=c++03'; to obtain all the diagnostics required by the standard,
+you should also specify `-pedantic' (or `-pedantic-errors' if you want
them to be errors rather than warnings).
- A revised ISO C++ standard was published in 2011 as ISO/IEC 14882:2011,
-and is referred to as C++11; before its publication it was commonly
-referred to as C++0x. C++11 contains several changes to the C++
-language, most of which have been implemented in an experimental C++11
-mode in GCC. For information regarding the C++11 features available in
-the experimental C++11 mode, see
-<http://gcc.gnu.org/projects/cxx0x.html>. To select this standard in
-GCC, use the option '-std=c++11'; to obtain all the diagnostics required
-by the standard, you should also specify '-pedantic' (or
-'-pedantic-errors' if you want them to be errors rather than warnings).
+ A revised ISO C++ standard was published in 2011 as ISO/IEC
+14882:2011, and is referred to as C++11; before its publication it was
+commonly referred to as C++0x. C++11 contains several changes to the
+C++ language, most of which have been implemented in an experimental
+C++11 mode in GCC. For information regarding the C++11 features
+available in the experimental C++11 mode, see
+`http://gcc.gnu.org/projects/cxx0x.html'. To select this standard in
+GCC, use the option `-std=c++11'; to obtain all the diagnostics
+required by the standard, you should also specify `-pedantic' (or
+`-pedantic-errors' if you want them to be errors rather than warnings).
More information about the C++ standards is available on the ISO C++
-committee's web site at <http://www.open-std.org/jtc1/sc22/wg21/>.
+committee's web site at `http://www.open-std.org/jtc1/sc22/wg21/'.
By default, GCC provides some extensions to the C++ language; *Note
-Options Controlling C++ Dialect: C++ Dialect Options. Use of the '-std'
-option listed above will disable these extensions. You may also select
-an extended version of the C++ language explicitly with '-std=gnu++98'
-(for C++98 with GNU extensions) or '-std=gnu++11' (for C++11 with GNU
-extensions). The default, if no C++ language dialect options are given,
-is '-std=gnu++98'.
+Options Controlling C++ Dialect: C++ Dialect Options. Use of the
+`-std' option listed above will disable these extensions. You may also
+select an extended version of the C++ language explicitly with
+`-std=gnu++98' (for C++98 with GNU extensions) or `-std=gnu++11' (for
+C++11 with GNU extensions). The default, if no C++ language dialect
+options are given, is `-std=gnu++98'.
2.3 Objective-C and Objective-C++ Languages
===========================================
-GCC supports "traditional" Objective-C (also known as "Objective-C 1.0")
-and contains support for the Objective-C exception and synchronization
-syntax. It has also support for a number of "Objective-C 2.0" language
-extensions, including properties, fast enumeration (only for
-Objective-C), method attributes and the @optional and @required keywords
-in protocols. GCC supports Objective-C++ and features available in
-Objective-C are also available in Objective-C++.
+GCC supports "traditional" Objective-C (also known as "Objective-C
+1.0") and contains support for the Objective-C exception and
+synchronization syntax. It has also support for a number of
+"Objective-C 2.0" language extensions, including properties, fast
+enumeration (only for Objective-C), method attributes and the @optional
+and @required keywords in protocols. GCC supports Objective-C++ and
+features available in Objective-C are also available in Objective-C++.
GCC by default uses the GNU Objective-C runtime library, which is part
-of GCC and is not the same as the Apple/NeXT Objective-C runtime library
-used on Apple systems. There are a number of differences documented in
-this manual. The options '-fgnu-runtime' and '-fnext-runtime' allow you
-to switch between producing output that works with the GNU Objective-C
-runtime library and output that works with the Apple/NeXT Objective-C
-runtime library.
+of GCC and is not the same as the Apple/NeXT Objective-C runtime
+library used on Apple systems. There are a number of differences
+documented in this manual. The options `-fgnu-runtime' and
+`-fnext-runtime' allow you to switch between producing output that
+works with the GNU Objective-C runtime library and output that works
+with the Apple/NeXT Objective-C runtime library.
There is no formal written standard for Objective-C or Objective-C++.
The authoritative manual on traditional Objective-C (1.0) is
-"Object-Oriented Programming and the Objective-C Language", available at
-a number of web sites:
- * <http://www.gnustep.org/resources/documentation/ObjectivCBook.pdf>
+"Object-Oriented Programming and the Objective-C Language", available
+at a number of web sites:
+ * `http://www.gnustep.org/resources/documentation/ObjectivCBook.pdf'
is the original NeXTstep document;
- * <http://objc.toodarkpark.net> is the same document in another
+
+ * `http://objc.toodarkpark.net' is the same document in another
format;
- *
- <http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/ObjectiveC/>
+
+ *
+ `http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/ObjectiveC/'
has an updated version but make sure you search for "Object
Oriented Programming and the Objective-C Programming Language 1.0",
not documentation on the newer "Objective-C 2.0" language
The Objective-C exception and synchronization syntax (that is, the
keywords @try, @throw, @catch, @finally and @synchronized) is supported
-by GCC and is enabled with the option '-fobjc-exceptions'. The syntax
+by GCC and is enabled with the option `-fobjc-exceptions'. The syntax
is briefly documented in this manual and in the Objective-C 2.0 manuals
from Apple.
The Objective-C 2.0 language extensions and features are automatically
enabled; they include properties (via the @property, @synthesize and
@dynamic keywords), fast enumeration (not available in Objective-C++),
-attributes for methods (such as deprecated, noreturn, sentinel, format),
-the unused attribute for method arguments, the @package keyword for
-instance variables and the @optional and @required keywords in
-protocols. You can disable all these Objective-C 2.0 language
-extensions with the option '-fobjc-std=objc1', which causes the compiler
-to recognize the same Objective-C language syntax recognized by GCC 4.0,
-and to produce an error if one of the new features is used.
+attributes for methods (such as deprecated, noreturn, sentinel,
+format), the unused attribute for method arguments, the @package
+keyword for instance variables and the @optional and @required keywords
+in protocols. You can disable all these Objective-C 2.0 language
+extensions with the option `-fobjc-std=objc1', which causes the
+compiler to recognize the same Objective-C language syntax recognized
+by GCC 4.0, and to produce an error if one of the new features is used.
GCC has currently no support for non-fragile instance variables.
The authoritative manual on Objective-C 2.0 is available from Apple:
- *
- <http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/ObjectiveC/>
+ *
+ `http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/ObjectiveC/'
For more information concerning the history of Objective-C that is
-available online, see <http://gcc.gnu.org/readings.html>
+available online, see `http://gcc.gnu.org/readings.html'
2.4 Go Language
===============
As of the GCC 4.7.1 release, GCC supports the Go 1 language standard,
-described at <http://golang.org/doc/go1.html>.
+described at `http://golang.org/doc/go1.html'.
2.5 References for Other Languages
==================================
@@ -367,7 +373,7 @@ conformance and compatibility of the Ada compiler.
supported by GNU Fortran.
*Note Compatibility with the Java Platform: (gcj)Compatibility, for
-details of compatibility between 'gcj' and the Java Platform.
+details of compatibility between `gcj' and the Java Platform.

File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards, Up: Top
@@ -377,9 +383,9 @@ File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards,
When you invoke GCC, it normally does preprocessing, compilation,
assembly and linking. The "overall options" allow you to stop this
-process at an intermediate stage. For example, the '-c' option says not
-to run the linker. Then the output consists of object files output by
-the assembler.
+process at an intermediate stage. For example, the `-c' option says
+not to run the linker. Then the output consists of object files output
+by the assembler.
Other options are passed on to one stage of processing. Some options
control the preprocessor and others the compiler itself. Yet other
@@ -395,20 +401,20 @@ that option with all supported languages.
*Note Compiling C++ Programs: Invoking G++, for a summary of special
options for compiling C++ programs.
- The 'gcc' program accepts options and file names as operands. Many
+ The `gcc' program accepts options and file names as operands. Many
options have multi-letter names; therefore multiple single-letter
-options may _not_ be grouped: '-dv' is very different from '-d -v'.
+options may _not_ be grouped: `-dv' is very different from `-d -v'.
You can mix options and other arguments. For the most part, the order
you use doesn't matter. Order does matter when you use several options
-of the same kind; for example, if you specify '-L' more than once, the
-directories are searched in the order specified. Also, the placement of
-the '-l' option is significant.
-
- Many options have long names starting with '-f' or with '-W'--for
-example, '-fmove-loop-invariants', '-Wformat' and so on. Most of these
-have both positive and negative forms; the negative form of '-ffoo' is
-'-fno-foo'. This manual documents only one of these two forms,
+of the same kind; for example, if you specify `-L' more than once, the
+directories are searched in the order specified. Also, the placement
+of the `-l' option is significant.
+
+ Many options have long names starting with `-f' or with `-W'--for
+example, `-fmove-loop-invariants', `-Wformat' and so on. Most of these
+have both positive and negative forms; the negative form of `-ffoo' is
+`-fno-foo'. This manual documents only one of these two forms,
whichever one is not the default.
*Note Option Index::, for an index to GCC's options.
@@ -807,6 +813,7 @@ _Machine Dependent Options_
-momit-leaf-frame-pointer -mno-omit-leaf-frame-pointer
-mtls-dialect=desc -mtls-dialect=traditional
-mfix-cortex-a53-835769 -mno-fix-cortex-a53-835769
+ -mfix-cortex-a53-843419 -mno-fix-cortex-a53-843419
-march=NAME -mcpu=NAME -mtune=NAME
_Adapteva Epiphany Options_
@@ -1370,7 +1377,7 @@ _Machine Dependent Options_
-maes -mpclmul -mfsgsbase -mrdrnd -mf16c -mfma -mprefetchwt1
-mclflushopt -mxsavec -mxsaves
-msse4a -m3dnow -mpopcnt -mabm -mbmi -mtbm -mfma4 -mxop -mlzcnt
- -mbmi2 -mfxsr -mxsave -mxsaveopt -mrtm -mlwp -mmpx -mthreads
+ -mbmi2 -mfxsr -mxsave -mxsaveopt -mrtm -mlwp -mmpx -mmwaitx -mthreads
-mno-align-stringops -minline-all-stringops
-minline-stringops-dynamically -mstringop-strategy=ALG
-mmemcpy-strategy=STRATEGY -mmemset-strategy=STRATEGY
@@ -1430,6 +1437,7 @@ _Code Generation Options_
-fvisibility=[default|internal|hidden|protected]
-fstrict-volatile-bitfields -fsync-libcalls
+

File: gcc.info, Node: Overall Options, Next: Invoking G++, Prev: Option Summary, Up: Invoking GCC
@@ -1439,130 +1447,130 @@ File: gcc.info, Node: Overall Options, Next: Invoking G++, Prev: Option Summa
Compilation can involve up to four stages: preprocessing, compilation
proper, assembly and linking, always in that order. GCC is capable of
preprocessing and compiling several files either into several assembler
-input files, or into one assembler input file; then each assembler input
-file produces an object file, and linking combines all the object files
-(those newly compiled, and those specified as input) into an executable
-file.
+input files, or into one assembler input file; then each assembler
+input file produces an object file, and linking combines all the object
+files (those newly compiled, and those specified as input) into an
+executable file.
For any given input file, the file name suffix determines what kind of
compilation is done:
-'FILE.c'
+`FILE.c'
C source code that must be preprocessed.
-'FILE.i'
+`FILE.i'
C source code that should not be preprocessed.
-'FILE.ii'
+`FILE.ii'
C++ source code that should not be preprocessed.
-'FILE.m'
+`FILE.m'
Objective-C source code. Note that you must link with the
- 'libobjc' library to make an Objective-C program work.
+ `libobjc' library to make an Objective-C program work.
-'FILE.mi'
+`FILE.mi'
Objective-C source code that should not be preprocessed.
-'FILE.mm'
-'FILE.M'
+`FILE.mm'
+`FILE.M'
Objective-C++ source code. Note that you must link with the
- 'libobjc' library to make an Objective-C++ program work. Note that
- '.M' refers to a literal capital M.
+ `libobjc' library to make an Objective-C++ program work. Note
+ that `.M' refers to a literal capital M.
-'FILE.mii'
+`FILE.mii'
Objective-C++ source code that should not be preprocessed.
-'FILE.h'
+`FILE.h'
C, C++, Objective-C or Objective-C++ header file to be turned into
a precompiled header (default), or C, C++ header file to be turned
- into an Ada spec (via the '-fdump-ada-spec' switch).
-
-'FILE.cc'
-'FILE.cp'
-'FILE.cxx'
-'FILE.cpp'
-'FILE.CPP'
-'FILE.c++'
-'FILE.C'
- C++ source code that must be preprocessed. Note that in '.cxx',
- the last two letters must both be literally 'x'. Likewise, '.C'
+ into an Ada spec (via the `-fdump-ada-spec' switch).
+
+`FILE.cc'
+`FILE.cp'
+`FILE.cxx'
+`FILE.cpp'
+`FILE.CPP'
+`FILE.c++'
+`FILE.C'
+ C++ source code that must be preprocessed. Note that in `.cxx',
+ the last two letters must both be literally `x'. Likewise, `.C'
refers to a literal capital C.
-'FILE.mm'
-'FILE.M'
+`FILE.mm'
+`FILE.M'
Objective-C++ source code that must be preprocessed.
-'FILE.mii'
+`FILE.mii'
Objective-C++ source code that should not be preprocessed.
-'FILE.hh'
-'FILE.H'
-'FILE.hp'
-'FILE.hxx'
-'FILE.hpp'
-'FILE.HPP'
-'FILE.h++'
-'FILE.tcc'
+`FILE.hh'
+`FILE.H'
+`FILE.hp'
+`FILE.hxx'
+`FILE.hpp'
+`FILE.HPP'
+`FILE.h++'
+`FILE.tcc'
C++ header file to be turned into a precompiled header or Ada spec.
-'FILE.f'
-'FILE.for'
-'FILE.ftn'
+`FILE.f'
+`FILE.for'
+`FILE.ftn'
Fixed form Fortran source code that should not be preprocessed.
-'FILE.F'
-'FILE.FOR'
-'FILE.fpp'
-'FILE.FPP'
-'FILE.FTN'
+`FILE.F'
+`FILE.FOR'
+`FILE.fpp'
+`FILE.FPP'
+`FILE.FTN'
Fixed form Fortran source code that must be preprocessed (with the
traditional preprocessor).
-'FILE.f90'
-'FILE.f95'
-'FILE.f03'
-'FILE.f08'
+`FILE.f90'
+`FILE.f95'
+`FILE.f03'
+`FILE.f08'
Free form Fortran source code that should not be preprocessed.
-'FILE.F90'
-'FILE.F95'
-'FILE.F03'
-'FILE.F08'
+`FILE.F90'
+`FILE.F95'
+`FILE.F03'
+`FILE.F08'
Free form Fortran source code that must be preprocessed (with the
traditional preprocessor).
-'FILE.go'
+`FILE.go'
Go source code.
-'FILE.ads'
+`FILE.ads'
Ada source code file that contains a library unit declaration (a
declaration of a package, subprogram, or generic, or a generic
instantiation), or a library unit renaming declaration (a package,
generic, or subprogram renaming declaration). Such files are also
called "specs".
-'FILE.adb'
+`FILE.adb'
Ada source code file containing a library unit body (a subprogram
or package body). Such files are also called "bodies".
-'FILE.s'
+`FILE.s'
Assembler code.
-'FILE.S'
-'FILE.sx'
+`FILE.S'
+`FILE.sx'
Assembler code that must be preprocessed.
-'OTHER'
- An object file to be fed straight into linking. Any file name with
- no recognized suffix is treated this way.
+`OTHER'
+ An object file to be fed straight into linking. Any file name
+ with no recognized suffix is treated this way.
- You can specify the input language explicitly with the '-x' option:
+ You can specify the input language explicitly with the `-x' option:
-'-x LANGUAGE'
+`-x LANGUAGE'
Specify explicitly the LANGUAGE for the following input files
(rather than letting the compiler choose a default based on the
file name suffix). This option applies to all following input
- files until the next '-x' option. Possible values for LANGUAGE
+ files until the next `-x' option. Possible values for LANGUAGE
are:
c c-header cpp-output
c++ c++-header c++-cpp-output
@@ -1574,139 +1582,139 @@ compilation is done:
go
java
-'-x none'
+`-x none'
Turn off any specification of a language, so that subsequent files
are handled according to their file name suffixes (as they are if
- '-x' has not been used at all).
+ `-x' has not been used at all).
-'-pass-exit-codes'
- Normally the 'gcc' program exits with the code of 1 if any phase of
- the compiler returns a non-success return code. If you specify
- '-pass-exit-codes', the 'gcc' program instead returns with the
+`-pass-exit-codes'
+ Normally the `gcc' program exits with the code of 1 if any phase
+ of the compiler returns a non-success return code. If you specify
+ `-pass-exit-codes', the `gcc' program instead returns with the
numerically highest error produced by any phase returning an error
indication. The C, C++, and Fortran front ends return 4 if an
internal compiler error is encountered.
- If you only want some of the stages of compilation, you can use '-x'
-(or filename suffixes) to tell 'gcc' where to start, and one of the
-options '-c', '-S', or '-E' to say where 'gcc' is to stop. Note that
-some combinations (for example, '-x cpp-output -E') instruct 'gcc' to do
-nothing at all.
+ If you only want some of the stages of compilation, you can use `-x'
+(or filename suffixes) to tell `gcc' where to start, and one of the
+options `-c', `-S', or `-E' to say where `gcc' is to stop. Note that
+some combinations (for example, `-x cpp-output -E') instruct `gcc' to
+do nothing at all.
-'-c'
+`-c'
Compile or assemble the source files, but do not link. The linking
stage simply is not done. The ultimate output is in the form of an
object file for each source file.
By default, the object file name for a source file is made by
- replacing the suffix '.c', '.i', '.s', etc., with '.o'.
+ replacing the suffix `.c', `.i', `.s', etc., with `.o'.
Unrecognized input files, not requiring compilation or assembly,
are ignored.
-'-S'
+`-S'
Stop after the stage of compilation proper; do not assemble. The
output is in the form of an assembler code file for each
non-assembler input file specified.
By default, the assembler file name for a source file is made by
- replacing the suffix '.c', '.i', etc., with '.s'.
+ replacing the suffix `.c', `.i', etc., with `.s'.
Input files that don't require compilation are ignored.
-'-E'
- Stop after the preprocessing stage; do not run the compiler proper.
- The output is in the form of preprocessed source code, which is
- sent to the standard output.
+`-E'
+ Stop after the preprocessing stage; do not run the compiler
+ proper. The output is in the form of preprocessed source code,
+ which is sent to the standard output.
Input files that don't require preprocessing are ignored.
-'-o FILE'
- Place output in file FILE. This applies to whatever sort of output
- is being produced, whether it be an executable file, an object
- file, an assembler file or preprocessed C code.
+`-o FILE'
+ Place output in file FILE. This applies to whatever sort of
+ output is being produced, whether it be an executable file, an
+ object file, an assembler file or preprocessed C code.
- If '-o' is not specified, the default is to put an executable file
- in 'a.out', the object file for 'SOURCE.SUFFIX' in 'SOURCE.o', its
- assembler file in 'SOURCE.s', a precompiled header file in
- 'SOURCE.SUFFIX.gch', and all preprocessed C source on standard
+ If `-o' is not specified, the default is to put an executable file
+ in `a.out', the object file for `SOURCE.SUFFIX' in `SOURCE.o', its
+ assembler file in `SOURCE.s', a precompiled header file in
+ `SOURCE.SUFFIX.gch', and all preprocessed C source on standard
output.
-'-v'
+`-v'
Print (on standard error output) the commands executed to run the
stages of compilation. Also print the version number of the
compiler driver program and of the preprocessor and the compiler
proper.
-'-###'
- Like '-v' except the commands are not executed and arguments are
- quoted unless they contain only alphanumeric characters or './-_'.
+`-###'
+ Like `-v' except the commands are not executed and arguments are
+ quoted unless they contain only alphanumeric characters or `./-_'.
This is useful for shell scripts to capture the driver-generated
command lines.
-'-pipe'
+`-pipe'
Use pipes rather than temporary files for communication between the
various stages of compilation. This fails to work on some systems
where the assembler is unable to read from a pipe; but the GNU
assembler has no trouble.
-'--help'
+`--help'
Print (on the standard output) a description of the command-line
- options understood by 'gcc'. If the '-v' option is also specified
- then '--help' is also passed on to the various processes invoked by
- 'gcc', so that they can display the command-line options they
- accept. If the '-Wextra' option has also been specified (prior to
- the '--help' option), then command-line options that have no
+ options understood by `gcc'. If the `-v' option is also specified
+ then `--help' is also passed on to the various processes invoked
+ by `gcc', so that they can display the command-line options they
+ accept. If the `-Wextra' option has also been specified (prior to
+ the `--help' option), then command-line options that have no
documentation associated with them are also displayed.
-'--target-help'
+`--target-help'
Print (on the standard output) a description of target-specific
command-line options for each tool. For some targets extra
target-specific information may also be printed.
-'--help={CLASS|[^]QUALIFIER}[,...]'
+`--help={CLASS|[^]QUALIFIER}[,...]'
Print (on the standard output) a description of the command-line
options understood by the compiler that fit into all specified
classes and qualifiers. These are the supported classes:
- 'optimizers'
+ `optimizers'
Display all of the optimization options supported by the
compiler.
- 'warnings'
+ `warnings'
Display all of the options controlling warning messages
produced by the compiler.
- 'target'
- Display target-specific options. Unlike the '--target-help'
+ `target'
+ Display target-specific options. Unlike the `--target-help'
option however, target-specific options of the linker and
assembler are not displayed. This is because those tools do
- not currently support the extended '--help=' syntax.
+ not currently support the extended `--help=' syntax.
- 'params'
- Display the values recognized by the '--param' option.
+ `params'
+ Display the values recognized by the `--param' option.
- LANGUAGE
+ LANGUAGE
Display the options supported for LANGUAGE, where LANGUAGE is
the name of one of the languages supported in this version of
GCC.
- 'common'
+ `common'
Display the options that are common to all languages.
These are the supported qualifiers:
- 'undocumented'
+ `undocumented'
Display only those options that are undocumented.
- 'joined'
+ `joined'
Display options taking an argument that appears after an equal
sign in the same continuous piece of text, such as:
- '--help=target'.
+ `--help=target'.
- 'separate'
+ `separate'
Display options taking an argument that appears as a separate
- word following the original option, such as: '-o output-file'.
+ word following the original option, such as: `-o output-file'.
Thus for example to display all the undocumented target-specific
switches supported by the compiler, use:
@@ -1714,13 +1722,13 @@ nothing at all.
--help=target,undocumented
The sense of a qualifier can be inverted by prefixing it with the
- '^' character, so for example to display all binary warning options
- (i.e., ones that are either on or off and that do not take an
- argument) that have a description, use:
+ `^' character, so for example to display all binary warning
+ options (i.e., ones that are either on or off and that do not take
+ an argument) that have a description, use:
--help=warnings,^joined,^undocumented
- The argument to '--help=' should not consist solely of inverted
+ The argument to `--help=' should not consist solely of inverted
qualifiers.
Combining several classes is possible, although this usually
@@ -1731,18 +1739,18 @@ nothing at all.
--help=target,optimizers
- The '--help=' option can be repeated on the command line. Each
+ The `--help=' option can be repeated on the command line. Each
successive use displays its requested class of options, skipping
those that have already been displayed.
- If the '-Q' option appears on the command line before the '--help='
- option, then the descriptive text displayed by '--help=' is
- changed. Instead of describing the displayed options, an
+ If the `-Q' option appears on the command line before the
+ `--help=' option, then the descriptive text displayed by `--help='
+ is changed. Instead of describing the displayed options, an
indication is given as to whether the option is enabled, disabled
or set to a specific value (assuming that the compiler knows this
- at the point where the '--help=' option is used).
+ at the point where the `--help=' option is used).
- Here is a truncated example from the ARM port of 'gcc':
+ Here is a truncated example from the ARM port of `gcc':
% gcc -Q -mabi=2 --help=target -c
The following options are target specific:
@@ -1752,72 +1760,75 @@ nothing at all.
The output is sensitive to the effects of previous command-line
options, so for example it is possible to find out which
- optimizations are enabled at '-O2' by using:
+ optimizations are enabled at `-O2' by using:
-Q -O2 --help=optimizers
Alternatively you can discover which binary optimizations are
- enabled by '-O3' by using:
+ enabled by `-O3' by using:
gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts
gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts
diff /tmp/O2-opts /tmp/O3-opts | grep enabled
-'-no-canonical-prefixes'
- Do not expand any symbolic links, resolve references to '/../' or
- '/./', or make the path absolute when generating a relative prefix.
+`-no-canonical-prefixes'
+ Do not expand any symbolic links, resolve references to `/../' or
+ `/./', or make the path absolute when generating a relative prefix.
-'--version'
+`--version'
Display the version number and copyrights of the invoked GCC.
-'-wrapper'
+`-wrapper'
Invoke all subcommands under a wrapper program. The name of the
wrapper program and its parameters are passed as a comma separated
list.
gcc -c t.c -wrapper gdb,--args
- This invokes all subprograms of 'gcc' under 'gdb --args', thus the
- invocation of 'cc1' is 'gdb --args cc1 ...'.
+ This invokes all subprograms of `gcc' under `gdb --args', thus the
+ invocation of `cc1' is `gdb --args cc1 ...'.
-'-fplugin=NAME.so'
- Load the plugin code in file NAME.so, assumed to be a shared object
- to be dlopen'd by the compiler. The base name of the shared object
- file is used to identify the plugin for the purposes of argument
- parsing (See '-fplugin-arg-NAME-KEY=VALUE' below). Each plugin
- should define the callback functions specified in the Plugins API.
+`-fplugin=NAME.so'
+ Load the plugin code in file NAME.so, assumed to be a shared
+ object to be dlopen'd by the compiler. The base name of the
+ shared object file is used to identify the plugin for the purposes
+ of argument parsing (See `-fplugin-arg-NAME-KEY=VALUE' below).
+ Each plugin should define the callback functions specified in the
+ Plugins API.
-'-fplugin-arg-NAME-KEY=VALUE'
+`-fplugin-arg-NAME-KEY=VALUE'
Define an argument called KEY with a value of VALUE for the plugin
called NAME.
-'-fdump-ada-spec[-slim]'
+`-fdump-ada-spec[-slim]'
For C and C++ source and include files, generate corresponding Ada
- specs. *Note (gnat_ugn)Generating Ada Bindings for C and C++
- headers::, which provides detailed documentation on this feature.
+ specs. *Note Generating Ada Bindings for C and C++ headers:
+ (gnat_ugn)Generating Ada Bindings for C and C++ headers, which
+ provides detailed documentation on this feature.
-'-fada-spec-parent=UNIT'
- In conjunction with '-fdump-ada-spec[-slim]' above, generate Ada
+`-fada-spec-parent=UNIT'
+ In conjunction with `-fdump-ada-spec[-slim]' above, generate Ada
specs as child units of parent UNIT.
-'-fdump-go-spec=FILE'
+`-fdump-go-spec=FILE'
For input files in any language, generate corresponding Go
- declarations in FILE. This generates Go 'const', 'type', 'var',
- and 'func' declarations which may be a useful way to start writing
+ declarations in FILE. This generates Go `const', `type', `var',
+ and `func' declarations which may be a useful way to start writing
a Go interface to code written in some other language.
-'@FILE'
- Read command-line options from FILE. The options read are inserted
- in place of the original @FILE option. If FILE does not exist, or
- cannot be read, then the option will be treated literally, and not
- removed.
+`@FILE'
+ Read command-line options from FILE. The options read are
+ inserted in place of the original @FILE option. If FILE does not
+ exist, or cannot be read, then the option will be treated
+ literally, and not removed.
Options in FILE are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
- option in either single or double quotes. Any character (including
- a backslash) may be included by prefixing the character to be
- included with a backslash. The FILE may itself contain additional
- @FILE options; any such options will be processed recursively.
+ option in either single or double quotes. Any character
+ (including a backslash) may be included by prefixing the character
+ to be included with a backslash. The FILE may itself contain
+ additional @FILE options; any such options will be processed
+ recursively.

File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Options, Up: Invoking GCC
@@ -1825,21 +1836,21 @@ File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Op
3.3 Compiling C++ Programs
==========================
-C++ source files conventionally use one of the suffixes '.C', '.cc',
-'.cpp', '.CPP', '.c++', '.cp', or '.cxx'; C++ header files often use
-'.hh', '.hpp', '.H', or (for shared template code) '.tcc'; and
-preprocessed C++ files use the suffix '.ii'. GCC recognizes files with
+C++ source files conventionally use one of the suffixes `.C', `.cc',
+`.cpp', `.CPP', `.c++', `.cp', or `.cxx'; C++ header files often use
+`.hh', `.hpp', `.H', or (for shared template code) `.tcc'; and
+preprocessed C++ files use the suffix `.ii'. GCC recognizes files with
these names and compiles them as C++ programs even if you call the
-compiler the same way as for compiling C programs (usually with the name
-'gcc').
+compiler the same way as for compiling C programs (usually with the
+name `gcc').
- However, the use of 'gcc' does not add the C++ library. 'g++' is a
+ However, the use of `gcc' does not add the C++ library. `g++' is a
program that calls GCC and automatically specifies linking against the
-C++ library. It treats '.c', '.h' and '.i' files as C++ source files
-instead of C source files unless '-x' is used. This program is also
-useful when precompiling a C header file with a '.h' extension for use
-in C++ compilations. On many systems, 'g++' is also installed with the
-name 'c++'.
+C++ library. It treats `.c', `.h' and `.i' files as C++ source files
+instead of C source files unless `-x' is used. This program is also
+useful when precompiling a C header file with a `.h' extension for use
+in C++ compilations. On many systems, `g++' is also installed with the
+name `c++'.
When you compile C++ programs, you may specify many of the same
command-line options that you use for compiling programs in any
@@ -1860,294 +1871,295 @@ The following options control the dialect of C (or languages derived
from C, such as C++, Objective-C and Objective-C++) that the compiler
accepts:
-'-ansi'
- In C mode, this is equivalent to '-std=c90'. In C++ mode, it is
- equivalent to '-std=c++98'.
+`-ansi'
+ In C mode, this is equivalent to `-std=c90'. In C++ mode, it is
+ equivalent to `-std=c++98'.
This turns off certain features of GCC that are incompatible with
- ISO C90 (when compiling C code), or of standard C++ (when compiling
- C++ code), such as the 'asm' and 'typeof' keywords, and predefined
- macros such as 'unix' and 'vax' that identify the type of system
- you are using. It also enables the undesirable and rarely used ISO
- trigraph feature. For the C compiler, it disables recognition of
- C++ style '//' comments as well as the 'inline' keyword.
-
- The alternate keywords '__asm__', '__extension__', '__inline__' and
- '__typeof__' continue to work despite '-ansi'. You would not want
- to use them in an ISO C program, of course, but it is useful to put
- them in header files that might be included in compilations done
- with '-ansi'. Alternate predefined macros such as '__unix__' and
- '__vax__' are also available, with or without '-ansi'.
-
- The '-ansi' option does not cause non-ISO programs to be rejected
- gratuitously. For that, '-Wpedantic' is required in addition to
- '-ansi'. *Note Warning Options::.
-
- The macro '__STRICT_ANSI__' is predefined when the '-ansi' option
+ ISO C90 (when compiling C code), or of standard C++ (when
+ compiling C++ code), such as the `asm' and `typeof' keywords, and
+ predefined macros such as `unix' and `vax' that identify the type
+ of system you are using. It also enables the undesirable and
+ rarely used ISO trigraph feature. For the C compiler, it disables
+ recognition of C++ style `//' comments as well as the `inline'
+ keyword.
+
+ The alternate keywords `__asm__', `__extension__', `__inline__'
+ and `__typeof__' continue to work despite `-ansi'. You would not
+ want to use them in an ISO C program, of course, but it is useful
+ to put them in header files that might be included in compilations
+ done with `-ansi'. Alternate predefined macros such as `__unix__'
+ and `__vax__' are also available, with or without `-ansi'.
+
+ The `-ansi' option does not cause non-ISO programs to be rejected
+ gratuitously. For that, `-Wpedantic' is required in addition to
+ `-ansi'. *Note Warning Options::.
+
+ The macro `__STRICT_ANSI__' is predefined when the `-ansi' option
is used. Some header files may notice this macro and refrain from
- declaring certain functions or defining certain macros that the ISO
- standard doesn't call for; this is to avoid interfering with any
- programs that might use these names for other things.
+ declaring certain functions or defining certain macros that the
+ ISO standard doesn't call for; this is to avoid interfering with
+ any programs that might use these names for other things.
Functions that are normally built in but do not have semantics
- defined by ISO C (such as 'alloca' and 'ffs') are not built-in
- functions when '-ansi' is used. *Note Other built-in functions
+ defined by ISO C (such as `alloca' and `ffs') are not built-in
+ functions when `-ansi' is used. *Note Other built-in functions
provided by GCC: Other Builtins, for details of the functions
affected.
-'-std='
- Determine the language standard. *Note Language Standards
+`-std='
+ Determine the language standard. *Note Language Standards
Supported by GCC: Standards, for details of these standard
- versions. This option is currently only supported when compiling C
- or C++.
-
- The compiler can accept several base standards, such as 'c90' or
- 'c++98', and GNU dialects of those standards, such as 'gnu90' or
- 'gnu++98'. When a base standard is specified, the compiler accepts
- all programs following that standard plus those using GNU
- extensions that do not contradict it. For example, '-std=c90'
+ versions. This option is currently only supported when compiling
+ C or C++.
+
+ The compiler can accept several base standards, such as `c90' or
+ `c++98', and GNU dialects of those standards, such as `gnu90' or
+ `gnu++98'. When a base standard is specified, the compiler
+ accepts all programs following that standard plus those using GNU
+ extensions that do not contradict it. For example, `-std=c90'
turns off certain features of GCC that are incompatible with ISO
- C90, such as the 'asm' and 'typeof' keywords, but not other GNU
+ C90, such as the `asm' and `typeof' keywords, but not other GNU
extensions that do not have a meaning in ISO C90, such as omitting
- the middle term of a '?:' expression. On the other hand, when a
+ the middle term of a `?:' expression. On the other hand, when a
GNU dialect of a standard is specified, all features supported by
the compiler are enabled, even when those features change the
meaning of the base standard. As a result, some strict-conforming
programs may be rejected. The particular standard is used by
- '-Wpedantic' to identify which features are GNU extensions given
- that version of the standard. For example '-std=gnu90 -Wpedantic'
- warns about C++ style '//' comments, while '-std=gnu99 -Wpedantic'
+ `-Wpedantic' to identify which features are GNU extensions given
+ that version of the standard. For example `-std=gnu90 -Wpedantic'
+ warns about C++ style `//' comments, while `-std=gnu99 -Wpedantic'
does not.
A value for this option must be provided; possible values are
- 'c90'
- 'c89'
- 'iso9899:1990'
+ `c90'
+ `c89'
+ `iso9899:1990'
Support all ISO C90 programs (certain GNU extensions that
- conflict with ISO C90 are disabled). Same as '-ansi' for C
+ conflict with ISO C90 are disabled). Same as `-ansi' for C
code.
- 'iso9899:199409'
+ `iso9899:199409'
ISO C90 as modified in amendment 1.
- 'c99'
- 'c9x'
- 'iso9899:1999'
- 'iso9899:199x'
- ISO C99. This standard is substantially completely supported,
- modulo bugs and floating-point issues (mainly but not entirely
- relating to optional C99 features from Annexes F and G). See <http://gcc.gnu.org/c99status.html>
- for more information. The names 'c9x' and 'iso9899:199x' are
+ `c99'
+ `c9x'
+ `iso9899:1999'
+ `iso9899:199x'
+ ISO C99. This standard is substantially completely
+ supported, modulo bugs and floating-point issues (mainly but
+ not entirely relating to optional C99 features from Annexes F
+ and G). See `http://gcc.gnu.org/c99status.html' for more
+ information. The names `c9x' and `iso9899:199x' are
deprecated.
- 'c11'
- 'c1x'
- 'iso9899:2011'
+ `c11'
+ `c1x'
+ `iso9899:2011'
ISO C11, the 2011 revision of the ISO C standard. This
standard is substantially completely supported, modulo bugs,
floating-point issues (mainly but not entirely relating to
optional C11 features from Annexes F and G) and the optional
Annexes K (Bounds-checking interfaces) and L (Analyzability).
- The name 'c1x' is deprecated.
+ The name `c1x' is deprecated.
- 'gnu90'
- 'gnu89'
+ `gnu90'
+ `gnu89'
GNU dialect of ISO C90 (including some C99 features).
- 'gnu99'
- 'gnu9x'
- GNU dialect of ISO C99. The name 'gnu9x' is deprecated.
+ `gnu99'
+ `gnu9x'
+ GNU dialect of ISO C99. The name `gnu9x' is deprecated.
- 'gnu11'
- 'gnu1x'
+ `gnu11'
+ `gnu1x'
GNU dialect of ISO C11. This is the default for C code. The
- name 'gnu1x' is deprecated.
+ name `gnu1x' is deprecated.
- 'c++98'
- 'c++03'
+ `c++98'
+ `c++03'
The 1998 ISO C++ standard plus the 2003 technical corrigendum
- and some additional defect reports. Same as '-ansi' for C++
+ and some additional defect reports. Same as `-ansi' for C++
code.
- 'gnu++98'
- 'gnu++03'
- GNU dialect of '-std=c++98'. This is the default for C++
+ `gnu++98'
+ `gnu++03'
+ GNU dialect of `-std=c++98'. This is the default for C++
code.
- 'c++11'
- 'c++0x'
- The 2011 ISO C++ standard plus amendments. The name 'c++0x'
+ `c++11'
+ `c++0x'
+ The 2011 ISO C++ standard plus amendments. The name `c++0x'
is deprecated.
- 'gnu++11'
- 'gnu++0x'
- GNU dialect of '-std=c++11'. The name 'gnu++0x' is
+ `gnu++11'
+ `gnu++0x'
+ GNU dialect of `-std=c++11'. The name `gnu++0x' is
deprecated.
- 'c++14'
- 'c++1y'
- The 2014 ISO C++ standard plus amendments. The name 'c++1y'
+ `c++14'
+ `c++1y'
+ The 2014 ISO C++ standard plus amendments. The name `c++1y'
is deprecated.
- 'gnu++14'
- 'gnu++1y'
- GNU dialect of '-std=c++14'. The name 'gnu++1y' is
+ `gnu++14'
+ `gnu++1y'
+ GNU dialect of `-std=c++14'. The name `gnu++1y' is
deprecated.
- 'c++1z'
- The next revision of the ISO C++ standard, tentatively planned
- for 2017. Support is highly experimental, and will almost
- certainly change in incompatible ways in future releases.
+ `c++1z'
+ The next revision of the ISO C++ standard, tentatively
+ planned for 2017. Support is highly experimental, and will
+ almost certainly change in incompatible ways in future
+ releases.
- 'gnu++1z'
- GNU dialect of '-std=c++1z'. Support is highly experimental,
+ `gnu++1z'
+ GNU dialect of `-std=c++1z'. Support is highly experimental,
and will almost certainly change in incompatible ways in
future releases.
-'-fgnu89-inline'
- The option '-fgnu89-inline' tells GCC to use the traditional GNU
- semantics for 'inline' functions when in C99 mode. *Note An Inline
- Function is As Fast As a Macro: Inline. Using this option is
- roughly equivalent to adding the 'gnu_inline' function attribute to
- all inline functions (*note Function Attributes::).
+`-fgnu89-inline'
+ The option `-fgnu89-inline' tells GCC to use the traditional GNU
+ semantics for `inline' functions when in C99 mode. *Note An
+ Inline Function is As Fast As a Macro: Inline. Using this option
+ is roughly equivalent to adding the `gnu_inline' function
+ attribute to all inline functions (*note Function Attributes::).
- The option '-fno-gnu89-inline' explicitly tells GCC to use the C99
- semantics for 'inline' when in C99 or gnu99 mode (i.e., it
+ The option `-fno-gnu89-inline' explicitly tells GCC to use the C99
+ semantics for `inline' when in C99 or gnu99 mode (i.e., it
specifies the default behavior). This option is not supported in
- '-std=c90' or '-std=gnu90' mode.
+ `-std=c90' or `-std=gnu90' mode.
- The preprocessor macros '__GNUC_GNU_INLINE__' and
- '__GNUC_STDC_INLINE__' may be used to check which semantics are in
- effect for 'inline' functions. *Note (cpp)Common Predefined
- Macros::.
+ The preprocessor macros `__GNUC_GNU_INLINE__' and
+ `__GNUC_STDC_INLINE__' may be used to check which semantics are in
+ effect for `inline' functions. *Note Common Predefined Macros:
+ (cpp)Common Predefined Macros.
-'-aux-info FILENAME'
+`-aux-info FILENAME'
Output to the given filename prototyped declarations for all
functions declared and/or defined in a translation unit, including
those in header files. This option is silently ignored in any
language other than C.
Besides declarations, the file indicates, in comments, the origin
- of each declaration (source file and line), whether the declaration
- was implicit, prototyped or unprototyped ('I', 'N' for new or 'O'
- for old, respectively, in the first character after the line number
- and the colon), and whether it came from a declaration or a
- definition ('C' or 'F', respectively, in the following character).
- In the case of function definitions, a K&R-style list of arguments
- followed by their declarations is also provided, inside comments,
- after the declaration.
-
-'-fallow-parameterless-variadic-functions'
+ of each declaration (source file and line), whether the
+ declaration was implicit, prototyped or unprototyped (`I', `N' for
+ new or `O' for old, respectively, in the first character after the
+ line number and the colon), and whether it came from a declaration
+ or a definition (`C' or `F', respectively, in the following
+ character). In the case of function definitions, a K&R-style list
+ of arguments followed by their declarations is also provided,
+ inside comments, after the declaration.
+
+`-fallow-parameterless-variadic-functions'
Accept variadic functions without named parameters.
Although it is possible to define such a function, this is not very
useful as it is not possible to read the arguments. This is only
supported for C as this construct is allowed by C++.
-'-fno-asm'
- Do not recognize 'asm', 'inline' or 'typeof' as a keyword, so that
+`-fno-asm'
+ Do not recognize `asm', `inline' or `typeof' as a keyword, so that
code can use these words as identifiers. You can use the keywords
- '__asm__', '__inline__' and '__typeof__' instead. '-ansi' implies
- '-fno-asm'.
-
- In C++, this switch only affects the 'typeof' keyword, since 'asm'
- and 'inline' are standard keywords. You may want to use the
- '-fno-gnu-keywords' flag instead, which has the same effect. In
- C99 mode ('-std=c99' or '-std=gnu99'), this switch only affects the
- 'asm' and 'typeof' keywords, since 'inline' is a standard keyword
- in ISO C99.
-
-'-fno-builtin'
-'-fno-builtin-FUNCTION'
+ `__asm__', `__inline__' and `__typeof__' instead. `-ansi' implies
+ `-fno-asm'.
+
+ In C++, this switch only affects the `typeof' keyword, since `asm'
+ and `inline' are standard keywords. You may want to use the
+ `-fno-gnu-keywords' flag instead, which has the same effect. In
+ C99 mode (`-std=c99' or `-std=gnu99'), this switch only affects
+ the `asm' and `typeof' keywords, since `inline' is a standard
+ keyword in ISO C99.
+
+`-fno-builtin'
+`-fno-builtin-FUNCTION'
Don't recognize built-in functions that do not begin with
- '__builtin_' as prefix. *Note Other built-in functions provided by
- GCC: Other Builtins, for details of the functions affected,
- including those which are not built-in functions when '-ansi' or
- '-std' options for strict ISO C conformance are used because they
+ `__builtin_' as prefix. *Note Other built-in functions provided
+ by GCC: Other Builtins, for details of the functions affected,
+ including those which are not built-in functions when `-ansi' or
+ `-std' options for strict ISO C conformance are used because they
do not have an ISO standard meaning.
GCC normally generates special code to handle certain built-in
- functions more efficiently; for instance, calls to 'alloca' may
+ functions more efficiently; for instance, calls to `alloca' may
become single instructions which adjust the stack directly, and
- calls to 'memcpy' may become inline copy loops. The resulting code
- is often both smaller and faster, but since the function calls no
- longer appear as such, you cannot set a breakpoint on those calls,
- nor can you change the behavior of the functions by linking with a
- different library. In addition, when a function is recognized as a
- built-in function, GCC may use information about that function to
- warn about problems with calls to that function, or to generate
- more efficient code, even if the resulting code still contains
- calls to that function. For example, warnings are given with
- '-Wformat' for bad calls to 'printf' when 'printf' is built in and
- 'strlen' is known not to modify global memory.
-
- With the '-fno-builtin-FUNCTION' option only the built-in function
- FUNCTION is disabled. FUNCTION must not begin with '__builtin_'.
- If a function is named that is not built-in in this version of GCC,
- this option is ignored. There is no corresponding
- '-fbuiltin-FUNCTION' option; if you wish to enable built-in
- functions selectively when using '-fno-builtin' or
- '-ffreestanding', you may define macros such as:
+ calls to `memcpy' may become inline copy loops. The resulting
+ code is often both smaller and faster, but since the function
+ calls no longer appear as such, you cannot set a breakpoint on
+ those calls, nor can you change the behavior of the functions by
+ linking with a different library. In addition, when a function is
+ recognized as a built-in function, GCC may use information about
+ that function to warn about problems with calls to that function,
+ or to generate more efficient code, even if the resulting code
+ still contains calls to that function. For example, warnings are
+ given with `-Wformat' for bad calls to `printf' when `printf' is
+ built in and `strlen' is known not to modify global memory.
+
+ With the `-fno-builtin-FUNCTION' option only the built-in function
+ FUNCTION is disabled. FUNCTION must not begin with `__builtin_'.
+ If a function is named that is not built-in in this version of
+ GCC, this option is ignored. There is no corresponding
+ `-fbuiltin-FUNCTION' option; if you wish to enable built-in
+ functions selectively when using `-fno-builtin' or
+ `-ffreestanding', you may define macros such as:
#define abs(n) __builtin_abs ((n))
#define strcpy(d, s) __builtin_strcpy ((d), (s))
-'-fhosted'
-
+`-fhosted'
Assert that compilation targets a hosted environment. This implies
- '-fbuiltin'. A hosted environment is one in which the entire
- standard library is available, and in which 'main' has a return
- type of 'int'. Examples are nearly everything except a kernel.
- This is equivalent to '-fno-freestanding'.
-
-'-ffreestanding'
+ `-fbuiltin'. A hosted environment is one in which the entire
+ standard library is available, and in which `main' has a return
+ type of `int'. Examples are nearly everything except a kernel.
+ This is equivalent to `-fno-freestanding'.
+`-ffreestanding'
Assert that compilation targets a freestanding environment. This
- implies '-fno-builtin'. A freestanding environment is one in which
- the standard library may not exist, and program startup may not
- necessarily be at 'main'. The most obvious example is an OS
- kernel. This is equivalent to '-fno-hosted'.
+ implies `-fno-builtin'. A freestanding environment is one in
+ which the standard library may not exist, and program startup may
+ not necessarily be at `main'. The most obvious example is an OS
+ kernel. This is equivalent to `-fno-hosted'.
*Note Language Standards Supported by GCC: Standards, for details
of freestanding and hosted environments.
-'-fopenacc'
- Enable handling of OpenACC directives '#pragma acc' in C/C++ and
- '!$acc' in Fortran. When '-fopenacc' is specified, the compiler
+`-fopenacc'
+ Enable handling of OpenACC directives `#pragma acc' in C/C++ and
+ `!$acc' in Fortran. When `-fopenacc' is specified, the compiler
generates accelerated code according to the OpenACC Application
- Programming Interface v2.0 <http://www.openacc.org/>. This option
- implies '-pthread', and thus is only supported on targets that have
- support for '-pthread'.
+ Programming Interface v2.0 `http://www.openacc.org/'. This option
+ implies `-pthread', and thus is only supported on targets that
+ have support for `-pthread'.
Note that this is an experimental feature, incomplete, and subject
- to change in future versions of GCC. See <https://gcc.gnu.org/wiki/OpenACC>
- for more information.
-
-'-fopenmp'
- Enable handling of OpenMP directives '#pragma omp' in C/C++ and
- '!$omp' in Fortran. When '-fopenmp' is specified, the compiler
- generates parallel code according to the OpenMP Application Program
- Interface v4.0 <http://www.openmp.org/>. This option implies
- '-pthread', and thus is only supported on targets that have support
- for '-pthread'. '-fopenmp' implies '-fopenmp-simd'.
-
-'-fopenmp-simd'
- Enable handling of OpenMP's SIMD directives with '#pragma omp' in
- C/C++ and '!$omp' in Fortran. Other OpenMP directives are ignored.
-
-'-fcilkplus'
+ to change in future versions of GCC. See
+ `https://gcc.gnu.org/wiki/OpenACC' for more information.
+
+`-fopenmp'
+ Enable handling of OpenMP directives `#pragma omp' in C/C++ and
+ `!$omp' in Fortran. When `-fopenmp' is specified, the compiler
+ generates parallel code according to the OpenMP Application
+ Program Interface v4.0 `http://www.openmp.org/'. This option
+ implies `-pthread', and thus is only supported on targets that
+ have support for `-pthread'. `-fopenmp' implies `-fopenmp-simd'.
+
+`-fopenmp-simd'
+ Enable handling of OpenMP's SIMD directives with `#pragma omp' in
+ C/C++ and `!$omp' in Fortran. Other OpenMP directives are ignored.
+
+`-fcilkplus'
Enable the usage of Cilk Plus language extension features for
- C/C++. When the option '-fcilkplus' is specified, enable the usage
- of the Cilk Plus Language extension features for C/C++. The
+ C/C++. When the option `-fcilkplus' is specified, enable the
+ usage of the Cilk Plus Language extension features for C/C++. The
present implementation follows ABI version 1.2. This is an
experimental feature that is only partially complete, and whose
interface may change in future versions of GCC as the official
- specification changes. Currently, all features but '_Cilk_for'
+ specification changes. Currently, all features but `_Cilk_for'
have been implemented.
-'-fgnu-tm'
- When the option '-fgnu-tm' is specified, the compiler generates
+`-fgnu-tm'
+ When the option `-fgnu-tm' is specified, the compiler generates
code for the Linux variant of Intel's current Transactional Memory
ABI specification document (Revision 1.1, May 6 2009). This is an
experimental feature whose interface may change in future versions
@@ -2159,9 +2171,9 @@ accepts:
libitm.
Note that the transactional memory feature is not supported with
- non-call exceptions ('-fnon-call-exceptions').
+ non-call exceptions (`-fnon-call-exceptions').
-'-fms-extensions'
+`-fms-extensions'
Accept some non-standard constructs used in Microsoft header files.
In C++ code, this allows member names in structures to be similar
@@ -2179,70 +2191,70 @@ accepts:
Note that this option is off for all targets but x86 targets using
ms-abi.
-'-fplan9-extensions'
+`-fplan9-extensions'
Accept some non-standard constructs used in Plan 9 code.
- This enables '-fms-extensions', permits passing pointers to
+ This enables `-fms-extensions', permits passing pointers to
structures with anonymous fields to functions that expect pointers
to elements of the type of the field, and permits referring to
anonymous fields declared using a typedef. *Note Unnamed
struct/union fields within structs/unions: Unnamed Fields, for
details. This is only supported for C, not C++.
-'-trigraphs'
- Support ISO C trigraphs. The '-ansi' option (and '-std' options
- for strict ISO C conformance) implies '-trigraphs'.
+`-trigraphs'
+ Support ISO C trigraphs. The `-ansi' option (and `-std' options
+ for strict ISO C conformance) implies `-trigraphs'.
-'-traditional'
-'-traditional-cpp'
+`-traditional'
+`-traditional-cpp'
Formerly, these options caused GCC to attempt to emulate a
- pre-standard C compiler. They are now only supported with the '-E'
- switch. The preprocessor continues to support a pre-standard mode.
- See the GNU CPP manual for details.
+ pre-standard C compiler. They are now only supported with the
+ `-E' switch. The preprocessor continues to support a pre-standard
+ mode. See the GNU CPP manual for details.
-'-fcond-mismatch'
+`-fcond-mismatch'
Allow conditional expressions with mismatched types in the second
and third arguments. The value of such an expression is void.
This option is not supported for C++.
-'-flax-vector-conversions'
+`-flax-vector-conversions'
Allow implicit conversions between vectors with differing numbers
of elements and/or incompatible element types. This option should
not be used for new code.
-'-funsigned-char'
- Let the type 'char' be unsigned, like 'unsigned char'.
+`-funsigned-char'
+ Let the type `char' be unsigned, like `unsigned char'.
- Each kind of machine has a default for what 'char' should be. It
- is either like 'unsigned char' by default or like 'signed char' by
+ Each kind of machine has a default for what `char' should be. It
+ is either like `unsigned char' by default or like `signed char' by
default.
- Ideally, a portable program should always use 'signed char' or
- 'unsigned char' when it depends on the signedness of an object.
- But many programs have been written to use plain 'char' and expect
+ Ideally, a portable program should always use `signed char' or
+ `unsigned char' when it depends on the signedness of an object.
+ But many programs have been written to use plain `char' and expect
it to be signed, or expect it to be unsigned, depending on the
machines they were written for. This option, and its inverse, let
you make such a program work with the opposite default.
- The type 'char' is always a distinct type from each of 'signed
- char' or 'unsigned char', even though its behavior is always just
+ The type `char' is always a distinct type from each of `signed
+ char' or `unsigned char', even though its behavior is always just
like one of those two.
-'-fsigned-char'
- Let the type 'char' be signed, like 'signed char'.
+`-fsigned-char'
+ Let the type `char' be signed, like `signed char'.
- Note that this is equivalent to '-fno-unsigned-char', which is the
- negative form of '-funsigned-char'. Likewise, the option
- '-fno-signed-char' is equivalent to '-funsigned-char'.
+ Note that this is equivalent to `-fno-unsigned-char', which is the
+ negative form of `-funsigned-char'. Likewise, the option
+ `-fno-signed-char' is equivalent to `-funsigned-char'.
-'-fsigned-bitfields'
-'-funsigned-bitfields'
-'-fno-signed-bitfields'
-'-fno-unsigned-bitfields'
+`-fsigned-bitfields'
+`-funsigned-bitfields'
+`-fno-signed-bitfields'
+`-fno-unsigned-bitfields'
These options control whether a bit-field is signed or unsigned,
- when the declaration does not use either 'signed' or 'unsigned'.
- By default, such a bit-field is signed, because this is consistent:
- the basic integer types such as 'int' are signed types.
+ when the declaration does not use either `signed' or `unsigned'.
+ By default, such a bit-field is signed, because this is
+ consistent: the basic integer types such as `int' are signed types.

File: gcc.info, Node: C++ Dialect Options, Next: Objective-C and Objective-C++ Dialect Options, Prev: C Dialect Options, Up: Invoking GCC
@@ -2253,16 +2265,17 @@ File: gcc.info, Node: C++ Dialect Options, Next: Objective-C and Objective-C++
This section describes the command-line options that are only meaningful
for C++ programs. You can also use most of the GNU compiler options
regardless of what language your program is in. For example, you might
-compile a file 'firstClass.C' like this:
+compile a file `firstClass.C' like this:
g++ -g -frepo -O -c firstClass.C
-In this example, only '-frepo' is an option meant only for C++ programs;
-you can use the other options with any language supported by GCC.
+In this example, only `-frepo' is an option meant only for C++
+programs; you can use the other options with any language supported by
+GCC.
Here is a list of options that are _only_ for compiling C++ programs:
-'-fabi-version=N'
+`-fabi-version=N'
Use version N of the C++ ABI. The default is version 0.
Version 0 refers to the version conforming most closely to the C++
@@ -2299,42 +2312,42 @@ you can use the other options with any language supported by GCC.
substitution behavior of function types with
function-cv-qualifiers.
- See also '-Wabi'.
+ See also `-Wabi'.
-'-fabi-compat-version=N'
+`-fabi-compat-version=N'
On targets that support strong aliases, G++ works around mangling
changes by creating an alias with the correct mangled name when
defining a symbol with an incorrect mangled name. This switch
specifies which ABI version to use for the alias.
- With '-fabi-version=0' (the default), this defaults to 2. If
+ With `-fabi-version=0' (the default), this defaults to 2. If
another ABI version is explicitly selected, this defaults to 0.
- The compatibility version is also set by '-Wabi=N'.
+ The compatibility version is also set by `-Wabi=N'.
-'-fno-access-control'
+`-fno-access-control'
Turn off all access checking. This switch is mainly useful for
working around bugs in the access control code.
-'-fcheck-new'
- Check that the pointer returned by 'operator new' is non-null
+`-fcheck-new'
+ Check that the pointer returned by `operator new' is non-null
before attempting to modify the storage allocated. This check is
normally unnecessary because the C++ standard specifies that
- 'operator new' only returns '0' if it is declared 'throw()', in
- which case the compiler always checks the return value even without
- this option. In all other cases, when 'operator new' has a
- non-empty exception specification, memory exhaustion is signalled
- by throwing 'std::bad_alloc'. See also 'new (nothrow)'.
+ `operator new' only returns `0' if it is declared `throw()', in
+ which case the compiler always checks the return value even
+ without this option. In all other cases, when `operator new' has
+ a non-empty exception specification, memory exhaustion is
+ signalled by throwing `std::bad_alloc'. See also `new (nothrow)'.
-'-fconstexpr-depth=N'
+`-fconstexpr-depth=N'
Set the maximum nested evaluation depth for C++11 constexpr
functions to N. A limit is needed to detect endless recursion
during constant expression evaluation. The minimum specified by
the standard is 512.
-'-fdeduce-init-list'
+`-fdeduce-init-list'
Enable deduction of a template type parameter as
- 'std::initializer_list' from a brace-enclosed initializer list,
+ `std::initializer_list' from a brace-enclosed initializer list,
i.e.
template <class T> auto forward(T t) -> decltype (realfn (t))
@@ -2353,59 +2366,60 @@ you can use the other options with any language supported by GCC.
option is deprecated, and may be removed in a future version of
G++.
-'-ffriend-injection'
+`-ffriend-injection'
Inject friend functions into the enclosing namespace, so that they
are visible outside the scope of the class in which they are
- declared. Friend functions were documented to work this way in the
- old Annotated C++ Reference Manual. However, in ISO C++ a friend
- function that is not declared in an enclosing scope can only be
- found using argument dependent lookup. GCC defaults to the
- standard behavior.
+ declared. Friend functions were documented to work this way in
+ the old Annotated C++ Reference Manual. However, in ISO C++ a
+ friend function that is not declared in an enclosing scope can
+ only be found using argument dependent lookup. GCC defaults to
+ the standard behavior.
This option is for compatibility, and may be removed in a future
release of G++.
-'-fno-elide-constructors'
+`-fno-elide-constructors'
The C++ standard allows an implementation to omit creating a
temporary that is only used to initialize another object of the
same type. Specifying this option disables that optimization, and
forces G++ to call the copy constructor in all cases.
-'-fno-enforce-eh-specs'
+`-fno-enforce-eh-specs'
Don't generate code to check for violation of exception
- specifications at run time. This option violates the C++ standard,
- but may be useful for reducing code size in production builds, much
- like defining 'NDEBUG'. This does not give user code permission to
- throw exceptions in violation of the exception specifications; the
- compiler still optimizes based on the specifications, so throwing
- an unexpected exception results in undefined behavior at run time.
-
-'-fextern-tls-init'
-'-fno-extern-tls-init'
- The C++11 and OpenMP standards allow 'thread_local' and
- 'threadprivate' variables to have dynamic (runtime) initialization.
- To support this, any use of such a variable goes through a wrapper
- function that performs any necessary initialization. When the use
- and definition of the variable are in the same translation unit,
- this overhead can be optimized away, but when the use is in a
- different translation unit there is significant overhead even if
- the variable doesn't actually need dynamic initialization. If the
- programmer can be sure that no use of the variable in a
- non-defining TU needs to trigger dynamic initialization (either
- because the variable is statically initialized, or a use of the
- variable in the defining TU will be executed before any uses in
- another TU), they can avoid this overhead with the
- '-fno-extern-tls-init' option.
+ specifications at run time. This option violates the C++
+ standard, but may be useful for reducing code size in production
+ builds, much like defining `NDEBUG'. This does not give user code
+ permission to throw exceptions in violation of the exception
+ specifications; the compiler still optimizes based on the
+ specifications, so throwing an unexpected exception results in
+ undefined behavior at run time.
+
+`-fextern-tls-init'
+`-fno-extern-tls-init'
+ The C++11 and OpenMP standards allow `thread_local' and
+ `threadprivate' variables to have dynamic (runtime)
+ initialization. To support this, any use of such a variable goes
+ through a wrapper function that performs any necessary
+ initialization. When the use and definition of the variable are
+ in the same translation unit, this overhead can be optimized away,
+ but when the use is in a different translation unit there is
+ significant overhead even if the variable doesn't actually need
+ dynamic initialization. If the programmer can be sure that no use
+ of the variable in a non-defining TU needs to trigger dynamic
+ initialization (either because the variable is statically
+ initialized, or a use of the variable in the defining TU will be
+ executed before any uses in another TU), they can avoid this
+ overhead with the `-fno-extern-tls-init' option.
On targets that support symbol aliases, the default is
- '-fextern-tls-init'. On targets that do not support symbol
- aliases, the default is '-fno-extern-tls-init'.
-
-'-ffor-scope'
-'-fno-for-scope'
- If '-ffor-scope' is specified, the scope of variables declared in a
- for-init-statement is limited to the 'for' loop itself, as
- specified by the C++ standard. If '-fno-for-scope' is specified,
+ `-fextern-tls-init'. On targets that do not support symbol
+ aliases, the default is `-fno-extern-tls-init'.
+
+`-ffor-scope'
+`-fno-for-scope'
+ If `-ffor-scope' is specified, the scope of variables declared in
+ a for-init-statement is limited to the `for' loop itself, as
+ specified by the C++ standard. If `-fno-for-scope' is specified,
the scope of variables declared in a for-init-statement extends to
the end of the enclosing scope, as was the case in old versions of
G++, and other (traditional) implementations of C++.
@@ -2414,155 +2428,155 @@ you can use the other options with any language supported by GCC.
but to allow and give a warning for old-style code that would
otherwise be invalid, or have different behavior.
-'-fno-gnu-keywords'
- Do not recognize 'typeof' as a keyword, so that code can use this
- word as an identifier. You can use the keyword '__typeof__'
- instead. '-ansi' implies '-fno-gnu-keywords'.
+`-fno-gnu-keywords'
+ Do not recognize `typeof' as a keyword, so that code can use this
+ word as an identifier. You can use the keyword `__typeof__'
+ instead. `-ansi' implies `-fno-gnu-keywords'.
-'-fno-implicit-templates'
+`-fno-implicit-templates'
Never emit code for non-inline templates that are instantiated
implicitly (i.e. by use); only emit code for explicit
instantiations. *Note Template Instantiation::, for more
information.
-'-fno-implicit-inline-templates'
+`-fno-implicit-inline-templates'
Don't emit code for implicit instantiations of inline templates,
either. The default is to handle inlines differently so that
compiles with and without optimization need the same set of
explicit instantiations.
-'-fno-implement-inlines'
+`-fno-implement-inlines'
To save space, do not emit out-of-line copies of inline functions
- controlled by '#pragma implementation'. This causes linker errors
+ controlled by `#pragma implementation'. This causes linker errors
if these functions are not inlined everywhere they are called.
-'-fms-extensions'
+`-fms-extensions'
Disable Wpedantic warnings about constructs used in MFC, such as
implicit int and getting a pointer to member function via
non-standard syntax.
-'-fno-nonansi-builtins'
+`-fno-nonansi-builtins'
Disable built-in declarations of functions that are not mandated by
- ANSI/ISO C. These include 'ffs', 'alloca', '_exit', 'index',
- 'bzero', 'conjf', and other related functions.
+ ANSI/ISO C. These include `ffs', `alloca', `_exit', `index',
+ `bzero', `conjf', and other related functions.
-'-fnothrow-opt'
- Treat a 'throw()' exception specification as if it were a
- 'noexcept' specification to reduce or eliminate the text size
+`-fnothrow-opt'
+ Treat a `throw()' exception specification as if it were a
+ `noexcept' specification to reduce or eliminate the text size
overhead relative to a function with no exception specification.
If the function has local variables of types with non-trivial
destructors, the exception specification actually makes the
function smaller because the EH cleanups for those variables can be
optimized away. The semantic effect is that an exception thrown
- out of a function with such an exception specification results in a
- call to 'terminate' rather than 'unexpected'.
+ out of a function with such an exception specification results in
+ a call to `terminate' rather than `unexpected'.
-'-fno-operator-names'
- Do not treat the operator name keywords 'and', 'bitand', 'bitor',
- 'compl', 'not', 'or' and 'xor' as synonyms as keywords.
+`-fno-operator-names'
+ Do not treat the operator name keywords `and', `bitand', `bitor',
+ `compl', `not', `or' and `xor' as synonyms as keywords.
-'-fno-optional-diags'
- Disable diagnostics that the standard says a compiler does not need
- to issue. Currently, the only such diagnostic issued by G++ is the
- one for a name having multiple meanings within a class.
+`-fno-optional-diags'
+ Disable diagnostics that the standard says a compiler does not
+ need to issue. Currently, the only such diagnostic issued by G++
+ is the one for a name having multiple meanings within a class.
-'-fpermissive'
+`-fpermissive'
Downgrade some diagnostics about nonconformant code from errors to
- warnings. Thus, using '-fpermissive' allows some nonconforming
+ warnings. Thus, using `-fpermissive' allows some nonconforming
code to compile.
-'-fno-pretty-templates'
+`-fno-pretty-templates'
When an error message refers to a specialization of a function
template, the compiler normally prints the signature of the
template followed by the template arguments and any typedefs or
- typenames in the signature (e.g. 'void f(T) [with T = int]' rather
- than 'void f(int)') so that it's clear which template is involved.
+ typenames in the signature (e.g. `void f(T) [with T = int]' rather
+ than `void f(int)') so that it's clear which template is involved.
When an error message refers to a specialization of a class
template, the compiler omits any template arguments that match the
default template arguments for that template. If either of these
behaviors make it harder to understand the error message rather
- than easier, you can use '-fno-pretty-templates' to disable them.
+ than easier, you can use `-fno-pretty-templates' to disable them.
-'-frepo'
+`-frepo'
Enable automatic template instantiation at link time. This option
- also implies '-fno-implicit-templates'. *Note Template
+ also implies `-fno-implicit-templates'. *Note Template
Instantiation::, for more information.
-'-fno-rtti'
+`-fno-rtti'
Disable generation of information about every class with virtual
functions for use by the C++ run-time type identification features
- ('dynamic_cast' and 'typeid'). If you don't use those parts of the
- language, you can save some space by using this flag. Note that
- exception handling uses the same information, but G++ generates it
- as needed. The 'dynamic_cast' operator can still be used for casts
- that do not require run-time type information, i.e. casts to 'void
- *' or to unambiguous base classes.
-
-'-fsized-deallocation'
+ (`dynamic_cast' and `typeid'). If you don't use those parts of
+ the language, you can save some space by using this flag. Note
+ that exception handling uses the same information, but G++
+ generates it as needed. The `dynamic_cast' operator can still be
+ used for casts that do not require run-time type information, i.e.
+ casts to `void *' or to unambiguous base classes.
+
+`-fsized-deallocation'
Enable the built-in global declarations
void operator delete (void *, std::size_t) noexcept;
void operator delete[] (void *, std::size_t) noexcept;
as introduced in C++14. This is useful for user-defined
replacement deallocation functions that, for example, use the size
of the object to make deallocation faster. Enabled by default
- under '-std=c++14' and above. The flag '-Wsized-deallocation'
+ under `-std=c++14' and above. The flag `-Wsized-deallocation'
warns about places that might want to add a definition.
-'-fstats'
+`-fstats'
Emit statistics about front-end processing at the end of the
compilation. This information is generally only useful to the G++
development team.
-'-fstrict-enums'
+`-fstrict-enums'
Allow the compiler to optimize using the assumption that a value of
enumerated type can only be one of the values of the enumeration
(as defined in the C++ standard; basically, a value that can be
represented in the minimum number of bits needed to represent all
the enumerators). This assumption may not be valid if the program
- uses a cast to convert an arbitrary integer value to the enumerated
- type.
+ uses a cast to convert an arbitrary integer value to the
+ enumerated type.
-'-ftemplate-backtrace-limit=N'
+`-ftemplate-backtrace-limit=N'
Set the maximum number of template instantiation notes for a single
warning or error to N. The default value is 10.
-'-ftemplate-depth=N'
+`-ftemplate-depth=N'
Set the maximum instantiation depth for template classes to N. A
limit on the template instantiation depth is needed to detect
endless recursions during template class instantiation. ANSI/ISO
C++ conforming programs must not rely on a maximum depth greater
than 17 (changed to 1024 in C++11). The default value is 900, as
- the compiler can run out of stack space before hitting 1024 in some
- situations.
+ the compiler can run out of stack space before hitting 1024 in
+ some situations.
-'-fno-threadsafe-statics'
+`-fno-threadsafe-statics'
Do not emit the extra code to use the routines specified in the C++
ABI for thread-safe initialization of local statics. You can use
this option to reduce code size slightly in code that doesn't need
to be thread-safe.
-'-fuse-cxa-atexit'
+`-fuse-cxa-atexit'
Register destructors for objects with static storage duration with
- the '__cxa_atexit' function rather than the 'atexit' function.
+ the `__cxa_atexit' function rather than the `atexit' function.
This option is required for fully standards-compliant handling of
static destructors, but only works if your C library supports
- '__cxa_atexit'.
+ `__cxa_atexit'.
-'-fno-use-cxa-get-exception-ptr'
- Don't use the '__cxa_get_exception_ptr' runtime routine. This
- causes 'std::uncaught_exception' to be incorrect, but is necessary
+`-fno-use-cxa-get-exception-ptr'
+ Don't use the `__cxa_get_exception_ptr' runtime routine. This
+ causes `std::uncaught_exception' to be incorrect, but is necessary
if the runtime routine is not available.
-'-fvisibility-inlines-hidden'
+`-fvisibility-inlines-hidden'
This switch declares that the user does not attempt to compare
pointers to inline functions or methods where the addresses of the
two functions are taken in different shared objects.
The effect of this is that GCC may, effectively, mark inline
- methods with '__attribute__ ((visibility ("hidden")))' so that they
- do not appear in the export table of a DSO and do not require a PLT
- indirection when used within the DSO. Enabling this option can
- have a dramatic effect on load and link times of a DSO as it
+ methods with `__attribute__ ((visibility ("hidden")))' so that
+ they do not appear in the export table of a DSO and do not require
+ a PLT indirection when used within the DSO. Enabling this option
+ can have a dramatic effect on load and link times of a DSO as it
massively reduces the size of the dynamic export table when the
library makes heavy use of templates.
@@ -2581,14 +2595,14 @@ you can use the other options with any language supported by GCC.
option as their linkage might otherwise cross a shared library
boundary. *Note Template Instantiation::.
-'-fvisibility-ms-compat'
+`-fvisibility-ms-compat'
This flag attempts to use visibility settings to make GCC's C++
linkage model compatible with that of Microsoft Visual Studio.
The flag makes these changes to GCC's linkage model:
- 1. It sets the default visibility to 'hidden', like
- '-fvisibility=hidden'.
+ 1. It sets the default visibility to `hidden', like
+ `-fvisibility=hidden'.
2. Types, but not their members, are not hidden by default.
@@ -2597,7 +2611,7 @@ you can use the other options with any language supported by GCC.
shared object: those declarations are permitted if they are
permitted when this option is not used.
- In new code it is better to use '-fvisibility=hidden' and export
+ In new code it is better to use `-fvisibility=hidden' and export
those classes that are intended to be externally visible.
Unfortunately it is possible for code to rely, perhaps
accidentally, on the Visual Studio behavior.
@@ -2610,81 +2624,81 @@ you can use the other options with any language supported by GCC.
given, it is a violation of the ODR to define types with the same
name differently.
-'-fvtable-verify=[std|preinit|none]'
- Turn on (or off, if using '-fvtable-verify=none') the security
- feature that verifies at run time, for every virtual call, that the
- vtable pointer through which the call is made is valid for the type
- of the object, and has not been corrupted or overwritten. If an
- invalid vtable pointer is detected at run time, an error is
+`-fvtable-verify=[std|preinit|none]'
+ Turn on (or off, if using `-fvtable-verify=none') the security
+ feature that verifies at run time, for every virtual call, that
+ the vtable pointer through which the call is made is valid for the
+ type of the object, and has not been corrupted or overwritten. If
+ an invalid vtable pointer is detected at run time, an error is
reported and execution of the program is immediately halted.
This option causes run-time data structures to be built at program
startup, which are used for verifying the vtable pointers. The
- options 'std' and 'preinit' control the timing of when these data
+ options `std' and `preinit' control the timing of when these data
structures are built. In both cases the data structures are built
- before execution reaches 'main'. Using '-fvtable-verify=std'
+ before execution reaches `main'. Using `-fvtable-verify=std'
causes the data structures to be built after shared libraries have
- been loaded and initialized. '-fvtable-verify=preinit' causes them
- to be built before shared libraries have been loaded and
+ been loaded and initialized. `-fvtable-verify=preinit' causes
+ them to be built before shared libraries have been loaded and
initialized.
If this option appears multiple times in the command line with
- different values specified, 'none' takes highest priority over both
- 'std' and 'preinit'; 'preinit' takes priority over 'std'.
+ different values specified, `none' takes highest priority over
+ both `std' and `preinit'; `preinit' takes priority over `std'.
-'-fvtv-debug'
- When used in conjunction with '-fvtable-verify=std' or
- '-fvtable-verify=preinit', causes debug versions of the runtime
+`-fvtv-debug'
+ When used in conjunction with `-fvtable-verify=std' or
+ `-fvtable-verify=preinit', causes debug versions of the runtime
functions for the vtable verification feature to be called. This
- flag also causes the compiler to log information about which vtable
- pointers it finds for each class. This information is written to a
- file named 'vtv_set_ptr_data.log' in the directory named by the
- environment variable 'VTV_LOGS_DIR' if that is defined or the
- current working directory otherwise.
+ flag also causes the compiler to log information about which
+ vtable pointers it finds for each class. This information is
+ written to a file named `vtv_set_ptr_data.log' in the directory
+ named by the environment variable `VTV_LOGS_DIR' if that is
+ defined or the current working directory otherwise.
- Note: This feature _appends_ data to the log file. If you want a
+ Note: This feature _appends_ data to the log file. If you want a
fresh log file, be sure to delete any existing one.
-'-fvtv-counts'
+`-fvtv-counts'
This is a debugging flag. When used in conjunction with
- '-fvtable-verify=std' or '-fvtable-verify=preinit', this causes the
- compiler to keep track of the total number of virtual calls it
+ `-fvtable-verify=std' or `-fvtable-verify=preinit', this causes
+ the compiler to keep track of the total number of virtual calls it
encounters and the number of verifications it inserts. It also
counts the number of calls to certain run-time library functions
that it inserts and logs this information for each compilation
unit. The compiler writes this information to a file named
- 'vtv_count_data.log' in the directory named by the environment
- variable 'VTV_LOGS_DIR' if that is defined or the current working
- directory otherwise. It also counts the size of the vtable pointer
- sets for each class, and writes this information to
- 'vtv_class_set_sizes.log' in the same directory.
+ `vtv_count_data.log' in the directory named by the environment
+ variable `VTV_LOGS_DIR' if that is defined or the current working
+ directory otherwise. It also counts the size of the vtable
+ pointer sets for each class, and writes this information to
+ `vtv_class_set_sizes.log' in the same directory.
- Note: This feature _appends_ data to the log files. To get fresh
+ Note: This feature _appends_ data to the log files. To get fresh
log files, be sure to delete any existing ones.
-'-fno-weak'
+`-fno-weak'
Do not use weak symbol support, even if it is provided by the
linker. By default, G++ uses weak symbols if they are available.
This option exists only for testing, and should not be used by
end-users; it results in inferior code and has no benefits. This
option may be removed in a future release of G++.
-'-nostdinc++'
- Do not search for header files in the standard directories specific
- to C++, but do still search the other standard directories. (This
- option is used when building the C++ library.)
+`-nostdinc++'
+ Do not search for header files in the standard directories
+ specific to C++, but do still search the other standard
+ directories. (This option is used when building the C++ library.)
In addition, these optimization, warning, and code generation options
have meanings only for C++ programs:
-'-Wabi (C, Objective-C, C++ and Objective-C++ only)'
- When an explicit '-fabi-version=N' option is used, causes G++ to
+`-Wabi (C, Objective-C, C++ and Objective-C++ only)'
+ When an explicit `-fabi-version=N' option is used, causes G++ to
warn when it generates code that is probably not compatible with
the vendor-neutral C++ ABI. Since G++ now defaults to
- '-fabi-version=0', '-Wabi' has no effect unless either an older ABI
- version is selected (with '-fabi-version=N') or an older
- compatibility version is selected (with '-Wabi=N' or
- '-fabi-compat-version=N').
+ `-fabi-version=0', `-Wabi' has no effect unless either an older
+ ABI version is selected (with `-fabi-version=N') or an older
+ compatibility version is selected (with `-Wabi=N' or
+ `-fabi-compat-version=N').
Although an effort has been made to warn about all such cases,
there are probably some cases that are not warned about, even
@@ -2696,12 +2710,12 @@ have meanings only for C++ programs:
concerned about the fact that code generated by G++ may not be
binary compatible with code generated by other compilers.
- '-Wabi' can also be used with an explicit version number to warn
- about compatibility with a particular '-fabi-version' level, e.g.
- '-Wabi=2' to warn about changes relative to '-fabi-version=2'.
- Specifying a version number also sets '-fabi-compat-version=N'.
+ `-Wabi' can also be used with an explicit version number to warn
+ about compatibility with a particular `-fabi-version' level, e.g.
+ `-Wabi=2' to warn about changes relative to `-fabi-version=2'.
+ Specifying a version number also sets `-fabi-compat-version=N'.
- The known incompatibilities in '-fabi-version=2' (which was the
+ The known incompatibilities in `-fabi-version=2' (which was the
default from GCC 3.4 to 4.9) include:
* A template with a non-type template parameter of reference
@@ -2710,81 +2724,83 @@ have meanings only for C++ programs:
template <int &> struct S {};
void n (S<N>) {2}
- This was fixed in '-fabi-version=3'.
+ This was fixed in `-fabi-version=3'.
- * SIMD vector types declared using '__attribute ((vector_size))'
- were mangled in a non-standard way that does not allow for
- overloading of functions taking vectors of different sizes.
+ * SIMD vector types declared using `__attribute
+ ((vector_size))' were mangled in a non-standard way that does
+ not allow for overloading of functions taking vectors of
+ different sizes.
- The mangling was changed in '-fabi-version=4'.
+ The mangling was changed in `-fabi-version=4'.
- * '__attribute ((const))' and 'noreturn' were mangled as type
- qualifiers, and 'decltype' of a plain declaration was folded
+ * `__attribute ((const))' and `noreturn' were mangled as type
+ qualifiers, and `decltype' of a plain declaration was folded
away.
- These mangling issues were fixed in '-fabi-version=5'.
+ These mangling issues were fixed in `-fabi-version=5'.
* Scoped enumerators passed as arguments to a variadic function
- are promoted like unscoped enumerators, causing 'va_arg' to
+ are promoted like unscoped enumerators, causing `va_arg' to
complain. On most targets this does not actually affect the
parameter passing ABI, as there is no way to pass an argument
- smaller than 'int'.
+ smaller than `int'.
Also, the ABI changed the mangling of template argument packs,
- 'const_cast', 'static_cast', prefix increment/decrement, and a
- class scope function used as a template argument.
+ `const_cast', `static_cast', prefix increment/decrement, and
+ a class scope function used as a template argument.
- These issues were corrected in '-fabi-version=6'.
+ These issues were corrected in `-fabi-version=6'.
* Lambdas in default argument scope were mangled incorrectly,
- and the ABI changed the mangling of 'nullptr_t'.
+ and the ABI changed the mangling of `nullptr_t'.
- These issues were corrected in '-fabi-version=7'.
+ These issues were corrected in `-fabi-version=7'.
* When mangling a function type with function-cv-qualifiers, the
un-qualified function type was incorrectly treated as a
substitution candidate.
- This was fixed in '-fabi-version=8'.
+ This was fixed in `-fabi-version=8'.
- It also warns about psABI-related changes. The known psABI changes
- at this point include:
+ It also warns about psABI-related changes. The known psABI
+ changes at this point include:
- * For SysV/x86-64, unions with 'long double' members are passed
- in memory as specified in psABI. For example:
+ * For SysV/x86-64, unions with `long double' members are passed
+ in memory as specified in psABI. For example:
union U {
long double ld;
int i;
};
- 'union U' is always passed in memory.
+ `union U' is always passed in memory.
-'-Wabi-tag (C++ and Objective-C++ only)'
+
+`-Wabi-tag (C++ and Objective-C++ only)'
Warn when a type with an ABI tag is used in a context that does not
have that ABI tag. See *note C++ Attributes:: for more information
about ABI tags.
-'-Wctor-dtor-privacy (C++ and Objective-C++ only)'
+`-Wctor-dtor-privacy (C++ and Objective-C++ only)'
Warn when a class seems unusable because all the constructors or
destructors in that class are private, and it has neither friends
nor public static member functions. Also warn if there are no
non-private methods, and there's at least one private member
function that isn't a constructor or destructor.
-'-Wdelete-non-virtual-dtor (C++ and Objective-C++ only)'
- Warn when 'delete' is used to destroy an instance of a class that
- has virtual functions and non-virtual destructor. It is unsafe to
+`-Wdelete-non-virtual-dtor (C++ and Objective-C++ only)'
+ Warn when `delete' is used to destroy an instance of a class that
+ has virtual functions and non-virtual destructor. It is unsafe to
delete an instance of a derived class through a pointer to a base
class if the base class does not have a virtual destructor. This
- warning is enabled by '-Wall'.
+ warning is enabled by `-Wall'.
-'-Wliteral-suffix (C++ and Objective-C++ only)'
+`-Wliteral-suffix (C++ and Objective-C++ only)'
Warn when a string or character literal is followed by a ud-suffix
which does not begin with an underscore. As a conforming
extension, GCC treats such suffixes as separate preprocessing
tokens in order to maintain backwards compatibility with code that
- uses formatting macros from '<inttypes.h>'. For example:
+ uses formatting macros from `<inttypes.h>'. For example:
#define __STDC_FORMAT_MACROS
#include <inttypes.h>
@@ -2795,39 +2811,39 @@ have meanings only for C++ programs:
printf("My int64: %"PRId64"\n", i64);
}
- In this case, 'PRId64' is treated as a separate preprocessing
+ In this case, `PRId64' is treated as a separate preprocessing
token.
This warning is enabled by default.
-'-Wnarrowing (C++ and Objective-C++ only)'
+`-Wnarrowing (C++ and Objective-C++ only)'
Warn when a narrowing conversion prohibited by C++11 occurs within
- '{ }', e.g.
+ `{ }', e.g.
int i = { 2.2 }; // error: narrowing from double to int
- This flag is included in '-Wall' and '-Wc++11-compat'.
+ This flag is included in `-Wall' and `-Wc++11-compat'.
- With '-std=c++11', '-Wno-narrowing' suppresses for non-constants
- the diagnostic required by the standard. Note that this does not
- affect the meaning of well-formed code; narrowing conversions are
- still considered ill-formed in SFINAE context.
+ With `-std=c++11', `-Wno-narrowing' suppresses the diagnostic
+ required by the standard. Note that this does not affect the
+ meaning of well-formed code; narrowing conversions are still
+ considered ill-formed in SFINAE context.
-'-Wnoexcept (C++ and Objective-C++ only)'
+`-Wnoexcept (C++ and Objective-C++ only)'
Warn when a noexcept-expression evaluates to false because of a
call to a function that does not have a non-throwing exception
- specification (i.e. 'throw()' or 'noexcept') but is known by the
+ specification (i.e. `throw()' or `noexcept') but is known by the
compiler to never throw an exception.
-'-Wnon-virtual-dtor (C++ and Objective-C++ only)'
+`-Wnon-virtual-dtor (C++ and Objective-C++ only)'
Warn when a class has virtual functions and an accessible
non-virtual destructor itself or in an accessible polymorphic base
class, in which case it is possible but unsafe to delete an
instance of a derived class through a pointer to the class itself
- or base class. This warning is automatically enabled if '-Weffc++'
- is specified.
+ or base class. This warning is automatically enabled if
+ `-Weffc++' is specified.
-'-Wreorder (C++ and Objective-C++ only)'
+`-Wreorder (C++ and Objective-C++ only)'
Warn when the order of member initializers given in the code does
not match the order in which they must be executed. For instance:
@@ -2837,31 +2853,31 @@ have meanings only for C++ programs:
A(): j (0), i (1) { }
};
- The compiler rearranges the member initializers for 'i' and 'j' to
+ The compiler rearranges the member initializers for `i' and `j' to
match the declaration order of the members, emitting a warning to
- that effect. This warning is enabled by '-Wall'.
+ that effect. This warning is enabled by `-Wall'.
-'-fext-numeric-literals (C++ and Objective-C++ only)'
+`-fext-numeric-literals (C++ and Objective-C++ only)'
Accept imaginary, fixed-point, or machine-defined literal number
suffixes as GNU extensions. When this option is turned off these
suffixes are treated as C++11 user-defined literal numeric
- suffixes. This is on by default for all pre-C++11 dialects and all
- GNU dialects: '-std=c++98', '-std=gnu++98', '-std=gnu++11',
- '-std=gnu++14'. This option is off by default for ISO C++11
- onwards ('-std=c++11', ...).
+ suffixes. This is on by default for all pre-C++11 dialects and
+ all GNU dialects: `-std=c++98', `-std=gnu++98', `-std=gnu++11',
+ `-std=gnu++14'. This option is off by default for ISO C++11
+ onwards (`-std=c++11', ...).
- The following '-W...' options are not affected by '-Wall'.
+ The following `-W...' options are not affected by `-Wall'.
-'-Weffc++ (C++ and Objective-C++ only)'
+`-Weffc++ (C++ and Objective-C++ only)'
Warn about violations of the following style guidelines from Scott
- Meyers' 'Effective C++' series of books:
+ Meyers' `Effective C++' series of books:
* Define a copy constructor and an assignment operator for
classes with dynamically-allocated memory.
* Prefer initialization to assignment in constructors.
- * Have 'operator=' return a reference to '*this'.
+ * Have `operator=' return a reference to `*this'.
* Don't try to return a reference when you must return an
object.
@@ -2869,47 +2885,49 @@ have meanings only for C++ programs:
* Distinguish between prefix and postfix forms of increment and
decrement operators.
- * Never overload '&&', '||', or ','.
+ * Never overload `&&', `||', or `,'.
+
- This option also enables '-Wnon-virtual-dtor', which is also one of
- the effective C++ recommendations. However, the check is extended
- to warn about the lack of virtual destructor in accessible
+ This option also enables `-Wnon-virtual-dtor', which is also one
+ of the effective C++ recommendations. However, the check is
+ extended to warn about the lack of virtual destructor in accessible
non-polymorphic bases classes too.
When selecting this option, be aware that the standard library
- headers do not obey all of these guidelines; use 'grep -v' to
+ headers do not obey all of these guidelines; use `grep -v' to
filter out those warnings.
-'-Wstrict-null-sentinel (C++ and Objective-C++ only)'
- Warn about the use of an uncasted 'NULL' as sentinel. When
- compiling only with GCC this is a valid sentinel, as 'NULL' is
- defined to '__null'. Although it is a null pointer constant rather
- than a null pointer, it is guaranteed to be of the same size as a
- pointer. But this use is not portable across different compilers.
+`-Wstrict-null-sentinel (C++ and Objective-C++ only)'
+ Warn about the use of an uncasted `NULL' as sentinel. When
+ compiling only with GCC this is a valid sentinel, as `NULL' is
+ defined to `__null'. Although it is a null pointer constant
+ rather than a null pointer, it is guaranteed to be of the same
+ size as a pointer. But this use is not portable across different
+ compilers.
-'-Wno-non-template-friend (C++ and Objective-C++ only)'
+`-Wno-non-template-friend (C++ and Objective-C++ only)'
Disable warnings when non-templatized friend functions are declared
within a template. Since the advent of explicit template
specification support in G++, if the name of the friend is an
- unqualified-id (i.e., 'friend foo(int)'), the C++ language
+ unqualified-id (i.e., `friend foo(int)'), the C++ language
specification demands that the friend declare or define an
ordinary, nontemplate function. (Section 14.5.3). Before G++
implemented explicit specification, unqualified-ids could be
interpreted as a particular specialization of a templatized
function. Because this non-conforming behavior is no longer the
- default behavior for G++, '-Wnon-template-friend' allows the
+ default behavior for G++, `-Wnon-template-friend' allows the
compiler to check existing code for potential trouble spots and is
on by default. This new compiler behavior can be turned off with
- '-Wno-non-template-friend', which keeps the conformant compiler
+ `-Wno-non-template-friend', which keeps the conformant compiler
code but disables the helpful warning.
-'-Wold-style-cast (C++ and Objective-C++ only)'
+`-Wold-style-cast (C++ and Objective-C++ only)'
Warn if an old-style (C-style) cast to a non-void type is used
- within a C++ program. The new-style casts ('dynamic_cast',
- 'static_cast', 'reinterpret_cast', and 'const_cast') are less
+ within a C++ program. The new-style casts (`dynamic_cast',
+ `static_cast', `reinterpret_cast', and `const_cast') are less
vulnerable to unintended effects and much easier to search for.
-'-Woverloaded-virtual (C++ and Objective-C++ only)'
+`-Woverloaded-virtual (C++ and Objective-C++ only)'
Warn when a function declaration hides virtual functions from a
base class. For example, in:
@@ -2921,18 +2939,18 @@ have meanings only for C++ programs:
void f(int);
};
- the 'A' class version of 'f' is hidden in 'B', and code like:
+ the `A' class version of `f' is hidden in `B', and code like:
B* b;
b->f();
fails to compile.
-'-Wno-pmf-conversions (C++ and Objective-C++ only)'
+`-Wno-pmf-conversions (C++ and Objective-C++ only)'
Disable the diagnostic for converting a bound pointer to member
function to a plain pointer.
-'-Wsign-promo (C++ and Objective-C++ only)'
+`-Wsign-promo (C++ and Objective-C++ only)'
Warn when overload resolution chooses a promotion from unsigned or
enumerated type to a signed type, over a conversion to an unsigned
type of the same size. Previous versions of G++ tried to preserve
@@ -2949,215 +2967,216 @@ languages themselves. *Note Language Standards Supported by GCC:
Standards, for references.)
This section describes the command-line options that are only
-meaningful for Objective-C and Objective-C++ programs. You can also use
-most of the language-independent GNU compiler options. For example, you
-might compile a file 'some_class.m' like this:
+meaningful for Objective-C and Objective-C++ programs. You can also
+use most of the language-independent GNU compiler options. For
+example, you might compile a file `some_class.m' like this:
gcc -g -fgnu-runtime -O -c some_class.m
-In this example, '-fgnu-runtime' is an option meant only for Objective-C
-and Objective-C++ programs; you can use the other options with any
-language supported by GCC.
+In this example, `-fgnu-runtime' is an option meant only for
+Objective-C and Objective-C++ programs; you can use the other options
+with any language supported by GCC.
Note that since Objective-C is an extension of the C language,
Objective-C compilations may also use options specific to the C
-front-end (e.g., '-Wtraditional'). Similarly, Objective-C++
-compilations may use C++-specific options (e.g., '-Wabi').
+front-end (e.g., `-Wtraditional'). Similarly, Objective-C++
+compilations may use C++-specific options (e.g., `-Wabi').
- Here is a list of options that are _only_ for compiling Objective-C and
-Objective-C++ programs:
+ Here is a list of options that are _only_ for compiling Objective-C
+and Objective-C++ programs:
-'-fconstant-string-class=CLASS-NAME'
+`-fconstant-string-class=CLASS-NAME'
Use CLASS-NAME as the name of the class to instantiate for each
- literal string specified with the syntax '@"..."'. The default
- class name is 'NXConstantString' if the GNU runtime is being used,
- and 'NSConstantString' if the NeXT runtime is being used (see
- below). The '-fconstant-cfstrings' option, if also present,
- overrides the '-fconstant-string-class' setting and cause '@"..."'
+ literal string specified with the syntax `@"..."'. The default
+ class name is `NXConstantString' if the GNU runtime is being used,
+ and `NSConstantString' if the NeXT runtime is being used (see
+ below). The `-fconstant-cfstrings' option, if also present,
+ overrides the `-fconstant-string-class' setting and cause `@"..."'
literals to be laid out as constant CoreFoundation strings.
-'-fgnu-runtime'
+`-fgnu-runtime'
Generate object code compatible with the standard GNU Objective-C
runtime. This is the default for most types of systems.
-'-fnext-runtime'
+`-fnext-runtime'
Generate output compatible with the NeXT runtime. This is the
- default for NeXT-based systems, including Darwin and Mac OS X. The
- macro '__NEXT_RUNTIME__' is predefined if (and only if) this option
- is used.
+ default for NeXT-based systems, including Darwin and Mac OS X.
+ The macro `__NEXT_RUNTIME__' is predefined if (and only if) this
+ option is used.
-'-fno-nil-receivers'
- Assume that all Objective-C message dispatches ('[receiver
+`-fno-nil-receivers'
+ Assume that all Objective-C message dispatches (`[receiver
message:arg]') in this translation unit ensure that the receiver is
- not 'nil'. This allows for more efficient entry points in the
+ not `nil'. This allows for more efficient entry points in the
runtime to be used. This option is only available in conjunction
with the NeXT runtime and ABI version 0 or 1.
-'-fobjc-abi-version=N'
+`-fobjc-abi-version=N'
Use version N of the Objective-C ABI for the selected runtime.
This option is currently supported only for the NeXT runtime. In
that case, Version 0 is the traditional (32-bit) ABI without
support for properties and other Objective-C 2.0 additions.
Version 1 is the traditional (32-bit) ABI with support for
properties and other Objective-C 2.0 additions. Version 2 is the
- modern (64-bit) ABI. If nothing is specified, the default is
- Version 0 on 32-bit target machines, and Version 2 on 64-bit target
- machines.
+ modern (64-bit) ABI. If nothing is specified, the default is
+ Version 0 on 32-bit target machines, and Version 2 on 64-bit
+ target machines.
-'-fobjc-call-cxx-cdtors'
+`-fobjc-call-cxx-cdtors'
For each Objective-C class, check if any of its instance variables
is a C++ object with a non-trivial default constructor. If so,
- synthesize a special '- (id) .cxx_construct' instance method which
+ synthesize a special `- (id) .cxx_construct' instance method which
runs non-trivial default constructors on any such instance
- variables, in order, and then return 'self'. Similarly, check if
+ variables, in order, and then return `self'. Similarly, check if
any instance variable is a C++ object with a non-trivial
- destructor, and if so, synthesize a special '- (void)
+ destructor, and if so, synthesize a special `- (void)
.cxx_destruct' method which runs all such default destructors, in
reverse order.
- The '- (id) .cxx_construct' and '- (void) .cxx_destruct' methods
- thusly generated only operate on instance variables declared in the
- current Objective-C class, and not those inherited from
+ The `- (id) .cxx_construct' and `- (void) .cxx_destruct' methods
+ thusly generated only operate on instance variables declared in
+ the current Objective-C class, and not those inherited from
superclasses. It is the responsibility of the Objective-C runtime
to invoke all such methods in an object's inheritance hierarchy.
- The '- (id) .cxx_construct' methods are invoked by the runtime
- immediately after a new object instance is allocated; the '- (void)
- .cxx_destruct' methods are invoked immediately before the runtime
- deallocates an object instance.
+ The `- (id) .cxx_construct' methods are invoked by the runtime
+ immediately after a new object instance is allocated; the `-
+ (void) .cxx_destruct' methods are invoked immediately before the
+ runtime deallocates an object instance.
As of this writing, only the NeXT runtime on Mac OS X 10.4 and
- later has support for invoking the '- (id) .cxx_construct' and '-
+ later has support for invoking the `- (id) .cxx_construct' and `-
(void) .cxx_destruct' methods.
-'-fobjc-direct-dispatch'
+`-fobjc-direct-dispatch'
Allow fast jumps to the message dispatcher. On Darwin this is
accomplished via the comm page.
-'-fobjc-exceptions'
+`-fobjc-exceptions'
Enable syntactic support for structured exception handling in
Objective-C, similar to what is offered by C++ and Java. This
- option is required to use the Objective-C keywords '@try',
- '@throw', '@catch', '@finally' and '@synchronized'. This option is
- available with both the GNU runtime and the NeXT runtime (but not
- available in conjunction with the NeXT runtime on Mac OS X 10.2 and
- earlier).
+ option is required to use the Objective-C keywords `@try',
+ `@throw', `@catch', `@finally' and `@synchronized'. This option
+ is available with both the GNU runtime and the NeXT runtime (but
+ not available in conjunction with the NeXT runtime on Mac OS X
+ 10.2 and earlier).
-'-fobjc-gc'
+`-fobjc-gc'
Enable garbage collection (GC) in Objective-C and Objective-C++
programs. This option is only available with the NeXT runtime; the
GNU runtime has a different garbage collection implementation that
does not require special compiler flags.
-'-fobjc-nilcheck'
+`-fobjc-nilcheck'
For the NeXT runtime with version 2 of the ABI, check for a nil
receiver in method invocations before doing the actual method call.
- This is the default and can be disabled using '-fno-objc-nilcheck'.
- Class methods and super calls are never checked for nil in this way
- no matter what this flag is set to. Currently this flag does
- nothing when the GNU runtime, or an older version of the NeXT
- runtime ABI, is used.
+ This is the default and can be disabled using
+ `-fno-objc-nilcheck'. Class methods and super calls are never
+ checked for nil in this way no matter what this flag is set to.
+ Currently this flag does nothing when the GNU runtime, or an older
+ version of the NeXT runtime ABI, is used.
-'-fobjc-std=objc1'
+`-fobjc-std=objc1'
Conform to the language syntax of Objective-C 1.0, the language
- recognized by GCC 4.0. This only affects the Objective-C additions
- to the C/C++ language; it does not affect conformance to C/C++
- standards, which is controlled by the separate C/C++ dialect option
- flags. When this option is used with the Objective-C or
+ recognized by GCC 4.0. This only affects the Objective-C
+ additions to the C/C++ language; it does not affect conformance to
+ C/C++ standards, which is controlled by the separate C/C++ dialect
+ option flags. When this option is used with the Objective-C or
Objective-C++ compiler, any Objective-C syntax that is not
recognized by GCC 4.0 is rejected. This is useful if you need to
make sure that your Objective-C code can be compiled with older
versions of GCC.
-'-freplace-objc-classes'
- Emit a special marker instructing 'ld(1)' not to statically link in
- the resulting object file, and allow 'dyld(1)' to load it in at run
- time instead. This is used in conjunction with the
+`-freplace-objc-classes'
+ Emit a special marker instructing `ld(1)' not to statically link in
+ the resulting object file, and allow `dyld(1)' to load it in at
+ run time instead. This is used in conjunction with the
Fix-and-Continue debugging mode, where the object file in question
- may be recompiled and dynamically reloaded in the course of program
- execution, without the need to restart the program itself.
+ may be recompiled and dynamically reloaded in the course of
+ program execution, without the need to restart the program itself.
Currently, Fix-and-Continue functionality is only available in
conjunction with the NeXT runtime on Mac OS X 10.3 and later.
-'-fzero-link'
+`-fzero-link'
When compiling for the NeXT runtime, the compiler ordinarily
- replaces calls to 'objc_getClass("...")' (when the name of the
+ replaces calls to `objc_getClass("...")' (when the name of the
class is known at compile time) with static class references that
get initialized at load time, which improves run-time performance.
- Specifying the '-fzero-link' flag suppresses this behavior and
- causes calls to 'objc_getClass("...")' to be retained. This is
+ Specifying the `-fzero-link' flag suppresses this behavior and
+ causes calls to `objc_getClass("...")' to be retained. This is
useful in Zero-Link debugging mode, since it allows for individual
- class implementations to be modified during program execution. The
- GNU runtime currently always retains calls to
- 'objc_get_class("...")' regardless of command-line options.
+ class implementations to be modified during program execution.
+ The GNU runtime currently always retains calls to
+ `objc_get_class("...")' regardless of command-line options.
-'-fno-local-ivars'
+`-fno-local-ivars'
By default instance variables in Objective-C can be accessed as if
they were local variables from within the methods of the class
they're declared in. This can lead to shadowing between instance
variables and other variables declared either locally inside a
class method or globally with the same name. Specifying the
- '-fno-local-ivars' flag disables this behavior thus avoiding
+ `-fno-local-ivars' flag disables this behavior thus avoiding
variable shadowing issues.
-'-fivar-visibility=[public|protected|private|package]'
+`-fivar-visibility=[public|protected|private|package]'
Set the default instance variable visibility to the specified
- option so that instance variables declared outside the scope of any
- access modifier directives default to the specified visibility.
+ option so that instance variables declared outside the scope of
+ any access modifier directives default to the specified visibility.
-'-gen-decls'
- Dump interface declarations for all classes seen in the source file
- to a file named 'SOURCENAME.decl'.
+`-gen-decls'
+ Dump interface declarations for all classes seen in the source
+ file to a file named `SOURCENAME.decl'.
-'-Wassign-intercept (Objective-C and Objective-C++ only)'
+`-Wassign-intercept (Objective-C and Objective-C++ only)'
Warn whenever an Objective-C assignment is being intercepted by the
garbage collector.
-'-Wno-protocol (Objective-C and Objective-C++ only)'
- If a class is declared to implement a protocol, a warning is issued
- for every method in the protocol that is not implemented by the
- class. The default behavior is to issue a warning for every method
- not explicitly implemented in the class, even if a method
+`-Wno-protocol (Objective-C and Objective-C++ only)'
+ If a class is declared to implement a protocol, a warning is
+ issued for every method in the protocol that is not implemented by
+ the class. The default behavior is to issue a warning for every
+ method not explicitly implemented in the class, even if a method
implementation is inherited from the superclass. If you use the
- '-Wno-protocol' option, then methods inherited from the superclass
+ `-Wno-protocol' option, then methods inherited from the superclass
are considered to be implemented, and no warning is issued for
them.
-'-Wselector (Objective-C and Objective-C++ only)'
+`-Wselector (Objective-C and Objective-C++ only)'
Warn if multiple methods of different types for the same selector
are found during compilation. The check is performed on the list
of methods in the final stage of compilation. Additionally, a
check is performed for each selector appearing in a
- '@selector(...)' expression, and a corresponding method for that
+ `@selector(...)' expression, and a corresponding method for that
selector has been found during compilation. Because these checks
scan the method table only at the end of compilation, these
warnings are not produced if the final stage of compilation is not
reached, for example because an error is found during compilation,
- or because the '-fsyntax-only' option is being used.
+ or because the `-fsyntax-only' option is being used.
-'-Wstrict-selector-match (Objective-C and Objective-C++ only)'
+`-Wstrict-selector-match (Objective-C and Objective-C++ only)'
Warn if multiple methods with differing argument and/or return
types are found for a given selector when attempting to send a
- message using this selector to a receiver of type 'id' or 'Class'.
- When this flag is off (which is the default behavior), the compiler
- omits such warnings if any differences found are confined to types
- that share the same size and alignment.
+ message using this selector to a receiver of type `id' or `Class'.
+ When this flag is off (which is the default behavior), the
+ compiler omits such warnings if any differences found are confined
+ to types that share the same size and alignment.
-'-Wundeclared-selector (Objective-C and Objective-C++ only)'
- Warn if a '@selector(...)' expression referring to an undeclared
+`-Wundeclared-selector (Objective-C and Objective-C++ only)'
+ Warn if a `@selector(...)' expression referring to an undeclared
selector is found. A selector is considered undeclared if no
- method with that name has been declared before the '@selector(...)'
- expression, either explicitly in an '@interface' or '@protocol'
- declaration, or implicitly in an '@implementation' section. This
- option always performs its checks as soon as a '@selector(...)'
- expression is found, while '-Wselector' only performs its checks in
- the final stage of compilation. This also enforces the coding
- style convention that methods and selectors must be declared before
- being used.
-
-'-print-objc-runtime-info'
+ method with that name has been declared before the
+ `@selector(...)' expression, either explicitly in an `@interface'
+ or `@protocol' declaration, or implicitly in an `@implementation'
+ section. This option always performs its checks as soon as a
+ `@selector(...)' expression is found, while `-Wselector' only
+ performs its checks in the final stage of compilation. This also
+ enforces the coding style convention that methods and selectors
+ must be declared before being used.
+
+`-print-objc-runtime-info'
Generate C header describing the largest structure that is passed
by value, if any.
+

File: gcc.info, Node: Language Independent Options, Next: Warning Options, Prev: Objective-C and Objective-C++ Dialect Options, Up: Invoking GCC
@@ -3167,98 +3186,99 @@ File: gcc.info, Node: Language Independent Options, Next: Warning Options, Pr
Traditionally, diagnostic messages have been formatted irrespective of
the output device's aspect (e.g. its width, ...). You can use the
options described below to control the formatting algorithm for
-diagnostic messages, e.g. how many characters per line, how often source
-location information should be reported. Note that some language front
-ends may not honor these options.
+diagnostic messages, e.g. how many characters per line, how often
+source location information should be reported. Note that some
+language front ends may not honor these options.
-'-fmessage-length=N'
+`-fmessage-length=N'
Try to format error messages so that they fit on lines of about N
characters. If N is zero, then no line-wrapping is done; each
error message appears on a single line. This is the default for
all front ends.
-'-fdiagnostics-show-location=once'
+`-fdiagnostics-show-location=once'
Only meaningful in line-wrapping mode. Instructs the diagnostic
messages reporter to emit source location information _once_; that
is, in case the message is too long to fit on a single physical
line and has to be wrapped, the source location won't be emitted
- (as prefix) again, over and over, in subsequent continuation lines.
- This is the default behavior.
+ (as prefix) again, over and over, in subsequent continuation
+ lines. This is the default behavior.
-'-fdiagnostics-show-location=every-line'
+`-fdiagnostics-show-location=every-line'
Only meaningful in line-wrapping mode. Instructs the diagnostic
messages reporter to emit the same source location information (as
prefix) for physical lines that result from the process of breaking
a message which is too long to fit on a single line.
-'-fdiagnostics-color[=WHEN]'
-'-fno-diagnostics-color'
- Use color in diagnostics. WHEN is 'never', 'always', or 'auto'.
- The default depends on how the compiler has been configured, it can
- be any of the above WHEN options or also 'never' if 'GCC_COLORS'
- environment variable isn't present in the environment, and 'auto'
- otherwise. 'auto' means to use color only when the standard error
- is a terminal. The forms '-fdiagnostics-color' and
- '-fno-diagnostics-color' are aliases for
- '-fdiagnostics-color=always' and '-fdiagnostics-color=never',
+`-fdiagnostics-color[=WHEN]'
+`-fno-diagnostics-color'
+ Use color in diagnostics. WHEN is `never', `always', or `auto'.
+ The default depends on how the compiler has been configured, it
+ can be any of the above WHEN options or also `never' if
+ `GCC_COLORS' environment variable isn't present in the environment,
+ and `auto' otherwise. `auto' means to use color only when the
+ standard error is a terminal. The forms `-fdiagnostics-color' and
+ `-fno-diagnostics-color' are aliases for
+ `-fdiagnostics-color=always' and `-fdiagnostics-color=never',
respectively.
- The colors are defined by the environment variable 'GCC_COLORS'.
+ The colors are defined by the environment variable `GCC_COLORS'.
Its value is a colon-separated list of capabilities and Select
- Graphic Rendition (SGR) substrings. SGR commands are interpreted
+ Graphic Rendition (SGR) substrings. SGR commands are interpreted
by the terminal or terminal emulator. (See the section in the
documentation of your text terminal for permitted values and their
meanings as character attributes.) These substring values are
integers in decimal representation and can be concatenated with
- semicolons. Common values to concatenate include '1' for bold, '4'
- for underline, '5' for blink, '7' for inverse, '39' for default
- foreground color, '30' to '37' for foreground colors, '90' to '97'
- for 16-color mode foreground colors, '38;5;0' to '38;5;255' for
- 88-color and 256-color modes foreground colors, '49' for default
- background color, '40' to '47' for background colors, '100' to
- '107' for 16-color mode background colors, and '48;5;0' to
- '48;5;255' for 88-color and 256-color modes background colors.
-
- The default 'GCC_COLORS' is
+ semicolons. Common values to concatenate include `1' for bold,
+ `4' for underline, `5' for blink, `7' for inverse, `39' for
+ default foreground color, `30' to `37' for foreground colors, `90'
+ to `97' for 16-color mode foreground colors, `38;5;0' to `38;5;255'
+ for 88-color and 256-color modes foreground colors, `49' for
+ default background color, `40' to `47' for background colors,
+ `100' to `107' for 16-color mode background colors, and `48;5;0'
+ to `48;5;255' for 88-color and 256-color modes background colors.
+
+ The default `GCC_COLORS' is
error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01
- where '01;31' is bold red, '01;35' is bold magenta, '01;36' is bold
- cyan, '01;32' is bold green and '01' is bold. Setting 'GCC_COLORS'
- to the empty string disables colors. Supported capabilities are as
- follows.
+ where `01;31' is bold red, `01;35' is bold magenta, `01;36' is
+ bold cyan, `01;32' is bold green and `01' is bold. Setting
+ `GCC_COLORS' to the empty string disables colors. Supported
+ capabilities are as follows.
- 'error='
+ `error='
SGR substring for error: markers.
- 'warning='
+ `warning='
SGR substring for warning: markers.
- 'note='
+ `note='
SGR substring for note: markers.
- 'caret='
+ `caret='
SGR substring for caret line.
- 'locus='
- SGR substring for location information, 'file:line' or
- 'file:line:column' etc.
+ `locus='
+ SGR substring for location information, `file:line' or
+ `file:line:column' etc.
- 'quote='
+ `quote='
SGR substring for information printed within quotes.
-'-fno-diagnostics-show-option'
+`-fno-diagnostics-show-option'
By default, each diagnostic emitted includes text indicating the
command-line option that directly controls the diagnostic (if such
an option is known to the diagnostic machinery). Specifying the
- '-fno-diagnostics-show-option' flag suppresses that behavior.
+ `-fno-diagnostics-show-option' flag suppresses that behavior.
-'-fno-diagnostics-show-caret'
+`-fno-diagnostics-show-caret'
By default, each diagnostic emitted includes the original source
- line and a caret '^' indicating the column. This option suppresses
- this information. The source line is truncated to N characters, if
- the '-fmessage-length=n' option is given. When the output is done
- to the terminal, the width is limited to the width given by the
- 'COLUMNS' environment variable or, if not set, to the terminal
- width.
+ line and a caret '^' indicating the column. This option
+ suppresses this information. The source line is truncated to N
+ characters, if the `-fmessage-length=n' option is given. When the
+ output is done to the terminal, the width is limited to the width
+ given by the `COLUMNS' environment variable or, if not set, to the
+ terminal width.
+

File: gcc.info, Node: Warning Options, Next: Debugging Options, Prev: Language Independent Options, Up: Invoking GCC
@@ -3273,123 +3293,126 @@ an error.
The following language-independent options do not enable specific
warnings but control the kinds of diagnostics produced by GCC.
-'-fsyntax-only'
+`-fsyntax-only'
Check the code for syntax errors, but don't do anything beyond
that.
-'-fmax-errors=N'
+`-fmax-errors=N'
Limits the maximum number of error messages to N, at which point
GCC bails out rather than attempting to continue processing the
source code. If N is 0 (the default), there is no limit on the
- number of error messages produced. If '-Wfatal-errors' is also
- specified, then '-Wfatal-errors' takes precedence over this option.
+ number of error messages produced. If `-Wfatal-errors' is also
+ specified, then `-Wfatal-errors' takes precedence over this option.
-'-w'
+`-w'
Inhibit all warning messages.
-'-Werror'
+`-Werror'
Make all warnings into errors.
-'-Werror='
+`-Werror='
Make the specified warning into an error. The specifier for a
- warning is appended; for example '-Werror=switch' turns the
- warnings controlled by '-Wswitch' into errors. This switch takes a
- negative form, to be used to negate '-Werror' for specific
- warnings; for example '-Wno-error=switch' makes '-Wswitch' warnings
- not be errors, even when '-Werror' is in effect.
+ warning is appended; for example `-Werror=switch' turns the
+ warnings controlled by `-Wswitch' into errors. This switch takes a
+ negative form, to be used to negate `-Werror' for specific
+ warnings; for example `-Wno-error=switch' makes `-Wswitch'
+ warnings not be errors, even when `-Werror' is in effect.
The warning message for each controllable warning includes the
option that controls the warning. That option can then be used
- with '-Werror=' and '-Wno-error=' as described above. (Printing of
- the option in the warning message can be disabled using the
- '-fno-diagnostics-show-option' flag.)
+ with `-Werror=' and `-Wno-error=' as described above. (Printing
+ of the option in the warning message can be disabled using the
+ `-fno-diagnostics-show-option' flag.)
- Note that specifying '-Werror='FOO automatically implies '-W'FOO.
- However, '-Wno-error='FOO does not imply anything.
+ Note that specifying `-Werror='FOO automatically implies `-W'FOO.
+ However, `-Wno-error='FOO does not imply anything.
-'-Wfatal-errors'
+`-Wfatal-errors'
This option causes the compiler to abort compilation on the first
error occurred rather than trying to keep going and printing
further error messages.
+
You can request many specific warnings with options beginning with
-'-W', for example '-Wimplicit' to request warnings on implicit
+`-W', for example `-Wimplicit' to request warnings on implicit
declarations. Each of these specific warning options also has a
-negative form beginning '-Wno-' to turn off warnings; for example,
-'-Wno-implicit'. This manual lists only one of the two forms, whichever
-is not the default. For further language-specific options also refer to
-*note C++ Dialect Options:: and *note Objective-C and Objective-C++
-Dialect Options::.
-
- Some options, such as '-Wall' and '-Wextra', turn on other options,
-such as '-Wunused', which may turn on further options, such as
-'-Wunused-value'. The combined effect of positive and negative forms is
+negative form beginning `-Wno-' to turn off warnings; for example,
+`-Wno-implicit'. This manual lists only one of the two forms,
+whichever is not the default. For further language-specific options
+also refer to *note C++ Dialect Options:: and *note Objective-C and
+Objective-C++ Dialect Options::.
+
+ Some options, such as `-Wall' and `-Wextra', turn on other options,
+such as `-Wunused', which may turn on further options, such as
+`-Wunused-value'. The combined effect of positive and negative forms is
that more specific options have priority over less specific ones,
-independently of their position in the command-line. For options of the
-same specificity, the last one takes effect. Options enabled or
-disabled via pragmas (*note Diagnostic Pragmas::) take effect as if they
-appeared at the end of the command-line.
+independently of their position in the command-line. For options of the
+same specificity, the last one takes effect. Options enabled or
+disabled via pragmas (*note Diagnostic Pragmas::) take effect as if
+they appeared at the end of the command-line.
When an unrecognized warning option is requested (e.g.,
-'-Wunknown-warning'), GCC emits a diagnostic stating that the option is
-not recognized. However, if the '-Wno-' form is used, the behavior is
-slightly different: no diagnostic is produced for '-Wno-unknown-warning'
-unless other diagnostics are being produced. This allows the use of new
-'-Wno-' options with old compilers, but if something goes wrong, the
-compiler warns that an unrecognized option is present.
-
-'-Wpedantic'
-'-pedantic'
- Issue all the warnings demanded by strict ISO C and ISO C++; reject
- all programs that use forbidden extensions, and some other programs
- that do not follow ISO C and ISO C++. For ISO C, follows the
- version of the ISO C standard specified by any '-std' option used.
+`-Wunknown-warning'), GCC emits a diagnostic stating that the option is
+not recognized. However, if the `-Wno-' form is used, the behavior is
+slightly different: no diagnostic is produced for
+`-Wno-unknown-warning' unless other diagnostics are being produced.
+This allows the use of new `-Wno-' options with old compilers, but if
+something goes wrong, the compiler warns that an unrecognized option is
+present.
+
+`-Wpedantic'
+`-pedantic'
+ Issue all the warnings demanded by strict ISO C and ISO C++;
+ reject all programs that use forbidden extensions, and some other
+ programs that do not follow ISO C and ISO C++. For ISO C, follows
+ the version of the ISO C standard specified by any `-std' option
+ used.
Valid ISO C and ISO C++ programs should compile properly with or
- without this option (though a rare few require '-ansi' or a '-std'
- option specifying the required version of ISO C). However, without
- this option, certain GNU extensions and traditional C and C++
- features are supported as well. With this option, they are
+ without this option (though a rare few require `-ansi' or a `-std'
+ option specifying the required version of ISO C). However,
+ without this option, certain GNU extensions and traditional C and
+ C++ features are supported as well. With this option, they are
rejected.
- '-Wpedantic' does not cause warning messages for use of the
- alternate keywords whose names begin and end with '__'. Pedantic
+ `-Wpedantic' does not cause warning messages for use of the
+ alternate keywords whose names begin and end with `__'. Pedantic
warnings are also disabled in the expression that follows
- '__extension__'. However, only system header files should use
- these escape routes; application programs should avoid them. *Note
- Alternate Keywords::.
+ `__extension__'. However, only system header files should use
+ these escape routes; application programs should avoid them.
+ *Note Alternate Keywords::.
- Some users try to use '-Wpedantic' to check programs for strict ISO
+ Some users try to use `-Wpedantic' to check programs for strict ISO
C conformance. They soon find that it does not do quite what they
want: it finds some non-ISO practices, but not all--only those for
which ISO C _requires_ a diagnostic, and some others for which
diagnostics have been added.
- A feature to report any failure to conform to ISO C might be useful
- in some instances, but would require considerable additional work
- and would be quite different from '-Wpedantic'. We don't have
- plans to support such a feature in the near future.
+ A feature to report any failure to conform to ISO C might be
+ useful in some instances, but would require considerable
+ additional work and would be quite different from `-Wpedantic'.
+ We don't have plans to support such a feature in the near future.
- Where the standard specified with '-std' represents a GNU extended
- dialect of C, such as 'gnu90' or 'gnu99', there is a corresponding
+ Where the standard specified with `-std' represents a GNU extended
+ dialect of C, such as `gnu90' or `gnu99', there is a corresponding
"base standard", the version of ISO C on which the GNU extended
- dialect is based. Warnings from '-Wpedantic' are given where they
+ dialect is based. Warnings from `-Wpedantic' are given where they
are required by the base standard. (It does not make sense for
such warnings to be given only for features not in the specified
GNU C dialect, since by definition the GNU dialects of C include
- all features the compiler supports with the given option, and there
- would be nothing to warn about.)
+ all features the compiler supports with the given option, and
+ there would be nothing to warn about.)
-'-pedantic-errors'
- Give an error whenever the "base standard" (see '-Wpedantic')
+`-pedantic-errors'
+ Give an error whenever the "base standard" (see `-Wpedantic')
requires a diagnostic, in some cases where there is undefined
behavior at compile-time and in some other cases that do not
prevent compilation of programs that are valid according to the
- standard. This is not equivalent to '-Werror=pedantic', since
+ standard. This is not equivalent to `-Werror=pedantic', since
there are errors enabled by this option and not enabled by the
latter and vice versa.
-'-Wall'
+`-Wall'
This enables all the warnings about constructions that some users
consider questionable, and that are easy to avoid (or modify to
prevent the warning), even in conjunction with macros. This also
@@ -3397,10 +3420,10 @@ compiler warns that an unrecognized option is present.
Dialect Options:: and *note Objective-C and Objective-C++ Dialect
Options::.
- '-Wall' turns on the following warning flags:
+ `-Wall' turns on the following warning flags:
-Waddress
- -Warray-bounds=1 (only with -O2)
+ -Warray-bounds=1 (only with `-O2')
-Wc++11-compat -Wc++14-compat
-Wchar-subscripts
-Wenum-compare (in C/ObjC; this is on by default in C++)
@@ -3408,7 +3431,7 @@ compiler warns that an unrecognized option is present.
-Wimplicit-function-declaration (C and Objective-C only)
-Wcomment
-Wformat
- -Wmain (only for C/ObjC and unless -ffreestanding)
+ -Wmain (only for C/ObjC and unless `-ffreestanding')
-Wmaybe-uninitialized
-Wmissing-braces (only for C/ObjC)
-Wnonnull
@@ -3431,18 +3454,17 @@ compiler warns that an unrecognized option is present.
-Wunused-variable
-Wvolatile-register-var
-
- Note that some warning flags are not implied by '-Wall'. Some of
+ Note that some warning flags are not implied by `-Wall'. Some of
them warn about constructions that users generally do not consider
questionable, but which occasionally you might wish to check for;
- others warn about constructions that are necessary or hard to avoid
- in some cases, and there is no simple way to modify the code to
- suppress the warning. Some of them are enabled by '-Wextra' but
+ others warn about constructions that are necessary or hard to
+ avoid in some cases, and there is no simple way to modify the code
+ to suppress the warning. Some of them are enabled by `-Wextra' but
many of them must be enabled individually.
-'-Wextra'
+`-Wextra'
This enables some extra warning flags that are not enabled by
- '-Wall'. (This option used to be called '-W'. The older name is
+ `-Wall'. (This option used to be called `-W'. The older name is
still supported, but the newer name is more descriptive.)
-Wclobbered
@@ -3455,15 +3477,14 @@ compiler warns that an unrecognized option is present.
-Wsign-compare
-Wtype-limits
-Wuninitialized
- -Wunused-parameter (only with -Wunused or -Wall)
- -Wunused-but-set-parameter (only with -Wunused or -Wall)
+ -Wunused-parameter (only with `-Wunused' or `-Wall')
+ -Wunused-but-set-parameter (only with `-Wunused' or `-Wall')
+ The option `-Wextra' also prints warning messages for the
+ following cases:
- The option '-Wextra' also prints warning messages for the following
- cases:
-
- * A pointer is compared against integer zero with '<', '<=',
- '>', or '>='.
+ * A pointer is compared against integer zero with `<', `<=',
+ `>', or `>='.
* (C++ only) An enumerator and a non-enumerator both appear in a
conditional expression.
@@ -3471,230 +3492,234 @@ compiler warns that an unrecognized option is present.
* (C++ only) Ambiguous virtual bases.
* (C++ only) Subscripting an array that has been declared
- 'register'.
+ `register'.
* (C++ only) Taking the address of a variable that has been
- declared 'register'.
+ declared `register'.
* (C++ only) A base class is not initialized in a derived
class's copy constructor.
-'-Wchar-subscripts'
- Warn if an array subscript has type 'char'. This is a common cause
+
+`-Wchar-subscripts'
+ Warn if an array subscript has type `char'. This is a common cause
of error, as programmers often forget that this type is signed on
- some machines. This warning is enabled by '-Wall'.
+ some machines. This warning is enabled by `-Wall'.
-'-Wcomment'
- Warn whenever a comment-start sequence '/*' appears in a '/*'
- comment, or whenever a Backslash-Newline appears in a '//' comment.
- This warning is enabled by '-Wall'.
+`-Wcomment'
+ Warn whenever a comment-start sequence `/*' appears in a `/*'
+ comment, or whenever a Backslash-Newline appears in a `//' comment.
+ This warning is enabled by `-Wall'.
-'-Wno-coverage-mismatch'
+`-Wno-coverage-mismatch'
Warn if feedback profiles do not match when using the
- '-fprofile-use' option. If a source file is changed between
- compiling with '-fprofile-gen' and with '-fprofile-use', the files
- with the profile feedback can fail to match the source file and GCC
- cannot use the profile feedback information. By default, this
+ `-fprofile-use' option. If a source file is changed between
+ compiling with `-fprofile-gen' and with `-fprofile-use', the files
+ with the profile feedback can fail to match the source file and
+ GCC cannot use the profile feedback information. By default, this
warning is enabled and is treated as an error.
- '-Wno-coverage-mismatch' can be used to disable the warning or
- '-Wno-error=coverage-mismatch' can be used to disable the error.
- Disabling the error for this warning can result in poorly optimized
- code and is useful only in the case of very minor changes such as
- bug fixes to an existing code-base. Completely disabling the
- warning is not recommended.
-
-'-Wno-cpp'
+ `-Wno-coverage-mismatch' can be used to disable the warning or
+ `-Wno-error=coverage-mismatch' can be used to disable the error.
+ Disabling the error for this warning can result in poorly
+ optimized code and is useful only in the case of very minor
+ changes such as bug fixes to an existing code-base. Completely
+ disabling the warning is not recommended.
+
+`-Wno-cpp'
(C, Objective-C, C++, Objective-C++ and Fortran only)
- Suppress warning messages emitted by '#warning' directives.
+ Suppress warning messages emitted by `#warning' directives.
-'-Wdouble-promotion (C, C++, Objective-C and Objective-C++ only)'
- Give a warning when a value of type 'float' is implicitly promoted
- to 'double'. CPUs with a 32-bit "single-precision" floating-point
- unit implement 'float' in hardware, but emulate 'double' in
- software. On such a machine, doing computations using 'double'
+`-Wdouble-promotion (C, C++, Objective-C and Objective-C++ only)'
+ Give a warning when a value of type `float' is implicitly promoted
+ to `double'. CPUs with a 32-bit "single-precision" floating-point
+ unit implement `float' in hardware, but emulate `double' in
+ software. On such a machine, doing computations using `double'
values is much more expensive because of the overhead required for
software emulation.
- It is easy to accidentally do computations with 'double' because
- floating-point literals are implicitly of type 'double'. For
+ It is easy to accidentally do computations with `double' because
+ floating-point literals are implicitly of type `double'. For
example, in:
float area(float radius)
{
return 3.14159 * radius * radius;
}
- the compiler performs the entire computation with 'double' because
- the floating-point literal is a 'double'.
+ the compiler performs the entire computation with `double' because
+ the floating-point literal is a `double'.
-'-Wformat'
-'-Wformat=N'
- Check calls to 'printf' and 'scanf', etc., to make sure that the
+`-Wformat'
+`-Wformat=N'
+ Check calls to `printf' and `scanf', etc., to make sure that the
arguments supplied have types appropriate to the format string
specified, and that the conversions specified in the format string
- make sense. This includes standard functions, and others specified
- by format attributes (*note Function Attributes::), in the
- 'printf', 'scanf', 'strftime' and 'strfmon' (an X/Open extension,
- not in the C standard) families (or other target-specific
- families). Which functions are checked without format attributes
- having been specified depends on the standard version selected, and
- such checks of functions without the attribute specified are
- disabled by '-ffreestanding' or '-fno-builtin'.
+ make sense. This includes standard functions, and others
+ specified by format attributes (*note Function Attributes::), in
+ the `printf', `scanf', `strftime' and `strfmon' (an X/Open
+ extension, not in the C standard) families (or other
+ target-specific families). Which functions are checked without
+ format attributes having been specified depends on the standard
+ version selected, and such checks of functions without the
+ attribute specified are disabled by `-ffreestanding' or
+ `-fno-builtin'.
The formats are checked against the format features supported by
GNU libc version 2.2. These include all ISO C90 and C99 features,
- as well as features from the Single Unix Specification and some BSD
- and GNU extensions. Other library implementations may not support
- all these features; GCC does not support warning about features
- that go beyond a particular library's limitations. However, if
- '-Wpedantic' is used with '-Wformat', warnings are given about
- format features not in the selected standard version (but not for
- 'strfmon' formats, since those are not in any version of the C
- standard). *Note Options Controlling C Dialect: C Dialect Options.
-
- '-Wformat=1'
- '-Wformat'
- Option '-Wformat' is equivalent to '-Wformat=1', and
- '-Wno-format' is equivalent to '-Wformat=0'. Since '-Wformat'
- also checks for null format arguments for several functions,
- '-Wformat' also implies '-Wnonnull'. Some aspects of this
- level of format checking can be disabled by the options:
- '-Wno-format-contains-nul', '-Wno-format-extra-args', and
- '-Wno-format-zero-length'. '-Wformat' is enabled by '-Wall'.
-
- '-Wno-format-contains-nul'
- If '-Wformat' is specified, do not warn about format strings
+ as well as features from the Single Unix Specification and some
+ BSD and GNU extensions. Other library implementations may not
+ support all these features; GCC does not support warning about
+ features that go beyond a particular library's limitations.
+ However, if `-Wpedantic' is used with `-Wformat', warnings are
+ given about format features not in the selected standard version
+ (but not for `strfmon' formats, since those are not in any version
+ of the C standard). *Note Options Controlling C Dialect: C
+ Dialect Options.
+
+ `-Wformat=1'
+ `-Wformat'
+ Option `-Wformat' is equivalent to `-Wformat=1', and
+ `-Wno-format' is equivalent to `-Wformat=0'. Since
+ `-Wformat' also checks for null format arguments for several
+ functions, `-Wformat' also implies `-Wnonnull'. Some aspects
+ of this level of format checking can be disabled by the
+ options: `-Wno-format-contains-nul',
+ `-Wno-format-extra-args', and `-Wno-format-zero-length'.
+ `-Wformat' is enabled by `-Wall'.
+
+ `-Wno-format-contains-nul'
+ If `-Wformat' is specified, do not warn about format strings
that contain NUL bytes.
- '-Wno-format-extra-args'
- If '-Wformat' is specified, do not warn about excess arguments
- to a 'printf' or 'scanf' format function. The C standard
- specifies that such arguments are ignored.
+ `-Wno-format-extra-args'
+ If `-Wformat' is specified, do not warn about excess
+ arguments to a `printf' or `scanf' format function. The C
+ standard specifies that such arguments are ignored.
Where the unused arguments lie between used arguments that are
- specified with '$' operand number specifications, normally
+ specified with `$' operand number specifications, normally
warnings are still given, since the implementation could not
- know what type to pass to 'va_arg' to skip the unused
- arguments. However, in the case of 'scanf' formats, this
+ know what type to pass to `va_arg' to skip the unused
+ arguments. However, in the case of `scanf' formats, this
option suppresses the warning if the unused arguments are all
pointers, since the Single Unix Specification says that such
unused arguments are allowed.
- '-Wno-format-zero-length'
- If '-Wformat' is specified, do not warn about zero-length
+ `-Wno-format-zero-length'
+ If `-Wformat' is specified, do not warn about zero-length
formats. The C standard specifies that zero-length formats
are allowed.
- '-Wformat=2'
- Enable '-Wformat' plus additional format checks. Currently
- equivalent to '-Wformat -Wformat-nonliteral -Wformat-security
+ `-Wformat=2'
+ Enable `-Wformat' plus additional format checks. Currently
+ equivalent to `-Wformat -Wformat-nonliteral -Wformat-security
-Wformat-y2k'.
- '-Wformat-nonliteral'
- If '-Wformat' is specified, also warn if the format string is
+ `-Wformat-nonliteral'
+ If `-Wformat' is specified, also warn if the format string is
not a string literal and so cannot be checked, unless the
- format function takes its format arguments as a 'va_list'.
+ format function takes its format arguments as a `va_list'.
- '-Wformat-security'
- If '-Wformat' is specified, also warn about uses of format
+ `-Wformat-security'
+ If `-Wformat' is specified, also warn about uses of format
functions that represent possible security problems. At
- present, this warns about calls to 'printf' and 'scanf'
+ present, this warns about calls to `printf' and `scanf'
functions where the format string is not a string literal and
- there are no format arguments, as in 'printf (foo);'. This
+ there are no format arguments, as in `printf (foo);'. This
may be a security hole if the format string came from
- untrusted input and contains '%n'. (This is currently a
- subset of what '-Wformat-nonliteral' warns about, but in
- future warnings may be added to '-Wformat-security' that are
- not included in '-Wformat-nonliteral'.)
+ untrusted input and contains `%n'. (This is currently a
+ subset of what `-Wformat-nonliteral' warns about, but in
+ future warnings may be added to `-Wformat-security' that are
+ not included in `-Wformat-nonliteral'.)
- '-Wformat-signedness'
- If '-Wformat' is specified, also warn if the format string
+ `-Wformat-signedness'
+ If `-Wformat' is specified, also warn if the format string
requires an unsigned argument and the argument is signed and
vice versa.
- '-Wformat-y2k'
- If '-Wformat' is specified, also warn about 'strftime' formats
- that may yield only a two-digit year.
+ `-Wformat-y2k'
+ If `-Wformat' is specified, also warn about `strftime'
+ formats that may yield only a two-digit year.
-'-Wnonnull'
- Warn about passing a null pointer for arguments marked as requiring
- a non-null value by the 'nonnull' function attribute.
+`-Wnonnull'
+ Warn about passing a null pointer for arguments marked as
+ requiring a non-null value by the `nonnull' function attribute.
- '-Wnonnull' is included in '-Wall' and '-Wformat'. It can be
- disabled with the '-Wno-nonnull' option.
+ `-Wnonnull' is included in `-Wall' and `-Wformat'. It can be
+ disabled with the `-Wno-nonnull' option.
-'-Winit-self (C, C++, Objective-C and Objective-C++ only)'
+`-Winit-self (C, C++, Objective-C and Objective-C++ only)'
Warn about uninitialized variables that are initialized with
themselves. Note this option can only be used with the
- '-Wuninitialized' option.
+ `-Wuninitialized' option.
- For example, GCC warns about 'i' being uninitialized in the
- following snippet only when '-Winit-self' has been specified:
+ For example, GCC warns about `i' being uninitialized in the
+ following snippet only when `-Winit-self' has been specified:
int f()
{
int i = i;
return i;
}
- This warning is enabled by '-Wall' in C++.
+ This warning is enabled by `-Wall' in C++.
-'-Wimplicit-int (C and Objective-C only)'
+`-Wimplicit-int (C and Objective-C only)'
Warn when a declaration does not specify a type. This warning is
- enabled by '-Wall'.
+ enabled by `-Wall'.
-'-Wimplicit-function-declaration (C and Objective-C only)'
+`-Wimplicit-function-declaration (C and Objective-C only)'
Give a warning whenever a function is used before being declared.
- In C99 mode ('-std=c99' or '-std=gnu99'), this warning is enabled
- by default and it is made into an error by '-pedantic-errors'.
- This warning is also enabled by '-Wall'.
+ In C99 mode (`-std=c99' or `-std=gnu99'), this warning is enabled
+ by default and it is made into an error by `-pedantic-errors'.
+ This warning is also enabled by `-Wall'.
-'-Wimplicit (C and Objective-C only)'
- Same as '-Wimplicit-int' and '-Wimplicit-function-declaration'.
- This warning is enabled by '-Wall'.
+`-Wimplicit (C and Objective-C only)'
+ Same as `-Wimplicit-int' and `-Wimplicit-function-declaration'.
+ This warning is enabled by `-Wall'.
-'-Wignored-qualifiers (C and C++ only)'
+`-Wignored-qualifiers (C and C++ only)'
Warn if the return type of a function has a type qualifier such as
- 'const'. For ISO C such a type qualifier has no effect, since the
+ `const'. For ISO C such a type qualifier has no effect, since the
value returned by a function is not an lvalue. For C++, the
- warning is only emitted for scalar types or 'void'. ISO C
- prohibits qualified 'void' return types on function definitions, so
- such return types always receive a warning even without this
+ warning is only emitted for scalar types or `void'. ISO C
+ prohibits qualified `void' return types on function definitions,
+ so such return types always receive a warning even without this
option.
- This warning is also enabled by '-Wextra'.
+ This warning is also enabled by `-Wextra'.
-'-Wmain'
- Warn if the type of 'main' is suspicious. 'main' should be a
+`-Wmain'
+ Warn if the type of `main' is suspicious. `main' should be a
function with external linkage, returning int, taking either zero
arguments, two, or three arguments of appropriate types. This
warning is enabled by default in C++ and is enabled by either
- '-Wall' or '-Wpedantic'.
+ `-Wall' or `-Wpedantic'.
-'-Wmissing-braces'
+`-Wmissing-braces'
Warn if an aggregate or union initializer is not fully bracketed.
- In the following example, the initializer for 'a' is not fully
- bracketed, but that for 'b' is fully bracketed. This warning is
- enabled by '-Wall' in C.
+ In the following example, the initializer for `a' is not fully
+ bracketed, but that for `b' is fully bracketed. This warning is
+ enabled by `-Wall' in C.
int a[2][2] = { 0, 1, 2, 3 };
int b[2][2] = { { 0, 1 }, { 2, 3 } };
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wmissing-include-dirs (C, C++, Objective-C and Objective-C++ only)'
+`-Wmissing-include-dirs (C, C++, Objective-C and Objective-C++ only)'
Warn if a user-supplied include directory does not exist.
-'-Wparentheses'
+`-Wparentheses'
Warn if parentheses are omitted in certain contexts, such as when
there is an assignment in a context where a truth value is
expected, or when operators are nested whose precedence people
often get confused about.
- Also warn if a comparison like 'x<=y<=z' appears; this is
- equivalent to '(x<=y ? 1 : 0) <= z', which is a different
+ Also warn if a comparison like `x<=y<=z' appears; this is
+ equivalent to `(x<=y ? 1 : 0) <= z', which is a different
interpretation from that of ordinary mathematical notation.
Also warn about constructions where there may be confusion to which
- 'if' statement an 'else' branch belongs. Here is an example of
+ `if' statement an `else' branch belongs. Here is an example of
such a case:
{
@@ -3705,14 +3730,14 @@ compiler warns that an unrecognized option is present.
bar ();
}
- In C/C++, every 'else' branch belongs to the innermost possible
- 'if' statement, which in this example is 'if (b)'. This is often
+ In C/C++, every `else' branch belongs to the innermost possible
+ `if' statement, which in this example is `if (b)'. This is often
not what the programmer expected, as illustrated in the above
example by indentation the programmer chose. When there is the
potential for this confusion, GCC issues a warning when this flag
is specified. To eliminate the warning, add explicit braces around
- the innermost 'if' statement so there is no way the 'else' can
- belong to the enclosing 'if'. The resulting code looks like this:
+ the innermost `if' statement so there is no way the `else' can
+ belong to the enclosing `if'. The resulting code looks like this:
{
if (a)
@@ -3724,15 +3749,15 @@ compiler warns that an unrecognized option is present.
}
}
- Also warn for dangerous uses of the GNU extension to '?:' with
- omitted middle operand. When the condition in the '?': operator is
+ Also warn for dangerous uses of the GNU extension to `?:' with
+ omitted middle operand. When the condition in the `?': operator is
a boolean expression, the omitted value is always 1. Often
- programmers expect it to be a value computed inside the conditional
- expression instead.
+ programmers expect it to be a value computed inside the
+ conditional expression instead.
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wsequence-point'
+`-Wsequence-point'
Warn about code that may have undefined semantics because of
violations of sequence point rules in the C and C++ standards.
@@ -3742,30 +3767,30 @@ compiler warns that an unrecognized option is present.
program: those executed before the sequence point, and those
executed after it. These occur after the evaluation of a full
expression (one which is not part of a larger expression), after
- the evaluation of the first operand of a '&&', '||', '? :' or ','
+ the evaluation of the first operand of a `&&', `||', `? :' or `,'
(comma) operator, before a function is called (but after the
evaluation of its arguments and the expression denoting the called
- function), and in certain other places. Other than as expressed by
- the sequence point rules, the order of evaluation of subexpressions
- of an expression is not specified. All these rules describe only a
- partial order rather than a total order, since, for example, if two
- functions are called within one expression with no sequence point
- between them, the order in which the functions are called is not
- specified. However, the standards committee have ruled that
- function calls do not overlap.
+ function), and in certain other places. Other than as expressed
+ by the sequence point rules, the order of evaluation of
+ subexpressions of an expression is not specified. All these rules
+ describe only a partial order rather than a total order, since,
+ for example, if two functions are called within one expression
+ with no sequence point between them, the order in which the
+ functions are called is not specified. However, the standards
+ committee have ruled that function calls do not overlap.
It is not specified when between sequence points modifications to
- the values of objects take effect. Programs whose behavior depends
- on this have undefined behavior; the C and C++ standards specify
- that "Between the previous and next sequence point an object shall
- have its stored value modified at most once by the evaluation of an
- expression. Furthermore, the prior value shall be read only to
- determine the value to be stored.". If a program breaks these
- rules, the results on any particular implementation are entirely
- unpredictable.
-
- Examples of code with undefined behavior are 'a = a++;', 'a[n] =
- b[n++]' and 'a[i++] = i;'. Some more complicated cases are not
+ the values of objects take effect. Programs whose behavior
+ depends on this have undefined behavior; the C and C++ standards
+ specify that "Between the previous and next sequence point an
+ object shall have its stored value modified at most once by the
+ evaluation of an expression. Furthermore, the prior value shall
+ be read only to determine the value to be stored.". If a program
+ breaks these rules, the results on any particular implementation
+ are entirely unpredictable.
+
+ Examples of code with undefined behavior are `a = a++;', `a[n] =
+ b[n++]' and `a[i++] = i;'. Some more complicated cases are not
diagnosed by this option, and it may give an occasional false
positive result, but in general it has been found fairly effective
at detecting this sort of problem in programs.
@@ -3774,161 +3799,163 @@ compiler warns that an unrecognized option is present.
over the precise meaning of the sequence point rules in subtle
cases. Links to discussions of the problem, including proposed
formal definitions, may be found on the GCC readings page, at
- <http://gcc.gnu.org/readings.html>.
+ `http://gcc.gnu.org/readings.html'.
- This warning is enabled by '-Wall' for C and C++.
+ This warning is enabled by `-Wall' for C and C++.
-'-Wno-return-local-addr'
+`-Wno-return-local-addr'
Do not warn about returning a pointer (or in C++, a reference) to a
variable that goes out of scope after the function returns.
-'-Wreturn-type'
+`-Wreturn-type'
Warn whenever a function is defined with a return type that
- defaults to 'int'. Also warn about any 'return' statement with no
- return value in a function whose return type is not 'void' (falling
- off the end of the function body is considered returning without a
- value), and about a 'return' statement with an expression in a
- function whose return type is 'void'.
+ defaults to `int'. Also warn about any `return' statement with no
+ return value in a function whose return type is not `void'
+ (falling off the end of the function body is considered returning
+ without a value), and about a `return' statement with an
+ expression in a function whose return type is `void'.
For C++, a function without return type always produces a
- diagnostic message, even when '-Wno-return-type' is specified. The
- only exceptions are 'main' and functions defined in system headers.
+ diagnostic message, even when `-Wno-return-type' is specified.
+ The only exceptions are `main' and functions defined in system
+ headers.
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wshift-count-negative'
- Warn if shift count is negative. This warning is enabled by
+`-Wshift-count-negative'
+ Warn if shift count is negative. This warning is enabled by
default.
-'-Wshift-count-overflow'
- Warn if shift count >= width of type. This warning is enabled by
+`-Wshift-count-overflow'
+ Warn if shift count >= width of type. This warning is enabled by
default.
-'-Wswitch'
- Warn whenever a 'switch' statement has an index of enumerated type
- and lacks a 'case' for one or more of the named codes of that
- enumeration. (The presence of a 'default' label prevents this
- warning.) 'case' labels outside the enumeration range also provoke
- warnings when this option is used (even if there is a 'default'
- label). This warning is enabled by '-Wall'.
-
-'-Wswitch-default'
- Warn whenever a 'switch' statement does not have a 'default' case.
-
-'-Wswitch-enum'
- Warn whenever a 'switch' statement has an index of enumerated type
- and lacks a 'case' for one or more of the named codes of that
- enumeration. 'case' labels outside the enumeration range also
+`-Wswitch'
+ Warn whenever a `switch' statement has an index of enumerated type
+ and lacks a `case' for one or more of the named codes of that
+ enumeration. (The presence of a `default' label prevents this
+ warning.) `case' labels outside the enumeration range also
+ provoke warnings when this option is used (even if there is a
+ `default' label). This warning is enabled by `-Wall'.
+
+`-Wswitch-default'
+ Warn whenever a `switch' statement does not have a `default' case.
+
+`-Wswitch-enum'
+ Warn whenever a `switch' statement has an index of enumerated type
+ and lacks a `case' for one or more of the named codes of that
+ enumeration. `case' labels outside the enumeration range also
provoke warnings when this option is used. The only difference
- between '-Wswitch' and this option is that this option gives a
+ between `-Wswitch' and this option is that this option gives a
warning about an omitted enumeration code even if there is a
- 'default' label.
+ `default' label.
-'-Wswitch-bool'
- Warn whenever a 'switch' statement has an index of boolean type.
+`-Wswitch-bool'
+ Warn whenever a `switch' statement has an index of boolean type.
It is possible to suppress this warning by casting the controlling
- expression to a type other than 'bool'. For example:
+ expression to a type other than `bool'. For example:
switch ((int) (a == 4))
{
...
}
This warning is enabled by default for C and C++ programs.
-'-Wsync-nand (C and C++ only)'
- Warn when '__sync_fetch_and_nand' and '__sync_nand_and_fetch'
+`-Wsync-nand (C and C++ only)'
+ Warn when `__sync_fetch_and_nand' and `__sync_nand_and_fetch'
built-in functions are used. These functions changed semantics in
GCC 4.4.
-'-Wtrigraphs'
- Warn if any trigraphs are encountered that might change the meaning
- of the program (trigraphs within comments are not warned about).
- This warning is enabled by '-Wall'.
+`-Wtrigraphs'
+ Warn if any trigraphs are encountered that might change the
+ meaning of the program (trigraphs within comments are not warned
+ about). This warning is enabled by `-Wall'.
-'-Wunused-but-set-parameter'
+`-Wunused-but-set-parameter'
Warn whenever a function parameter is assigned to, but otherwise
unused (aside from its declaration).
- To suppress this warning use the 'unused' attribute (*note Variable
- Attributes::).
+ To suppress this warning use the `unused' attribute (*note
+ Variable Attributes::).
- This warning is also enabled by '-Wunused' together with '-Wextra'.
+ This warning is also enabled by `-Wunused' together with `-Wextra'.
-'-Wunused-but-set-variable'
+`-Wunused-but-set-variable'
Warn whenever a local variable is assigned to, but otherwise unused
- (aside from its declaration). This warning is enabled by '-Wall'.
+ (aside from its declaration). This warning is enabled by `-Wall'.
- To suppress this warning use the 'unused' attribute (*note Variable
- Attributes::).
+ To suppress this warning use the `unused' attribute (*note
+ Variable Attributes::).
- This warning is also enabled by '-Wunused', which is enabled by
- '-Wall'.
+ This warning is also enabled by `-Wunused', which is enabled by
+ `-Wall'.
-'-Wunused-function'
+`-Wunused-function'
Warn whenever a static function is declared but not defined or a
non-inline static function is unused. This warning is enabled by
- '-Wall'.
+ `-Wall'.
-'-Wunused-label'
+`-Wunused-label'
Warn whenever a label is declared but not used. This warning is
- enabled by '-Wall'.
+ enabled by `-Wall'.
- To suppress this warning use the 'unused' attribute (*note Variable
- Attributes::).
+ To suppress this warning use the `unused' attribute (*note
+ Variable Attributes::).
-'-Wunused-local-typedefs (C, Objective-C, C++ and Objective-C++ only)'
+`-Wunused-local-typedefs (C, Objective-C, C++ and Objective-C++ only)'
Warn when a typedef locally defined in a function is not used.
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wunused-parameter'
+`-Wunused-parameter'
Warn whenever a function parameter is unused aside from its
declaration.
- To suppress this warning use the 'unused' attribute (*note Variable
- Attributes::).
+ To suppress this warning use the `unused' attribute (*note
+ Variable Attributes::).
-'-Wno-unused-result'
+`-Wno-unused-result'
Do not warn if a caller of a function marked with attribute
- 'warn_unused_result' (*note Function Attributes::) does not use its
- return value. The default is '-Wunused-result'.
+ `warn_unused_result' (*note Function Attributes::) does not use
+ its return value. The default is `-Wunused-result'.
-'-Wunused-variable'
+`-Wunused-variable'
Warn whenever a local variable or non-constant static variable is
unused aside from its declaration. This warning is enabled by
- '-Wall'.
+ `-Wall'.
- To suppress this warning use the 'unused' attribute (*note Variable
- Attributes::).
+ To suppress this warning use the `unused' attribute (*note
+ Variable Attributes::).
-'-Wunused-value'
+`-Wunused-value'
Warn whenever a statement computes a result that is explicitly not
- used. To suppress this warning cast the unused expression to
- 'void'. This includes an expression-statement or the left-hand
- side of a comma expression that contains no side effects. For
- example, an expression such as 'x[i,j]' causes a warning, while
- 'x[(void)i,j]' does not.
+ used. To suppress this warning cast the unused expression to
+ `void'. This includes an expression-statement or the left-hand
+ side of a comma expression that contains no side effects. For
+ example, an expression such as `x[i,j]' causes a warning, while
+ `x[(void)i,j]' does not.
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wunused'
- All the above '-Wunused' options combined.
+`-Wunused'
+ All the above `-Wunused' options combined.
In order to get a warning about an unused function parameter, you
- must either specify '-Wextra -Wunused' (note that '-Wall' implies
- '-Wunused'), or separately specify '-Wunused-parameter'.
+ must either specify `-Wextra -Wunused' (note that `-Wall' implies
+ `-Wunused'), or separately specify `-Wunused-parameter'.
-'-Wuninitialized'
+`-Wuninitialized'
Warn if an automatic variable is used without first being
- initialized or if a variable may be clobbered by a 'setjmp' call.
- In C++, warn if a non-static reference or non-static 'const' member
+ initialized or if a variable may be clobbered by a `setjmp' call.
+ In C++, warn if a non-static reference or non-static `const' member
appears in a class without constructors.
- If you want to warn about code that uses the uninitialized value of
- the variable in its own initializer, use the '-Winit-self' option.
+ If you want to warn about code that uses the uninitialized value
+ of the variable in its own initializer, use the `-Winit-self'
+ option.
These warnings occur for individual uninitialized or clobbered
elements of structure, union or array variables as well as for
variables that are uninitialized or clobbered as a whole. They do
- not occur for variables or elements declared 'volatile'. Because
+ not occur for variables or elements declared `volatile'. Because
these warnings depend on optimization, the exact variables or
elements for which there are warnings depends on the precise
optimization options and version of GCC used.
@@ -3938,15 +3965,15 @@ compiler warns that an unrecognized option is present.
computations may be deleted by data flow analysis before the
warnings are printed.
-'-Wmaybe-uninitialized'
+`-Wmaybe-uninitialized'
For an automatic variable, if there exists a path from the function
entry to a use of the variable that is initialized, but there exist
some other paths for which the variable is not initialized, the
- compiler emits a warning if it cannot prove the uninitialized paths
- are not executed at run time. These warnings are made optional
- because GCC is not smart enough to see all the reasons why the code
- might be correct in spite of appearing to have an error. Here is
- one example of how this can happen:
+ compiler emits a warning if it cannot prove the uninitialized
+ paths are not executed at run time. These warnings are made
+ optional because GCC is not smart enough to see all the reasons
+ why the code might be correct in spite of appearing to have an
+ error. Here is one example of how this can happen:
{
int x;
@@ -3961,79 +3988,80 @@ compiler warns that an unrecognized option is present.
foo (x);
}
- If the value of 'y' is always 1, 2 or 3, then 'x' is always
- initialized, but GCC doesn't know this. To suppress the warning,
+ If the value of `y' is always 1, 2 or 3, then `x' is always
+ initialized, but GCC doesn't know this. To suppress the warning,
you need to provide a default case with assert(0) or similar code.
- This option also warns when a non-volatile automatic variable might
- be changed by a call to 'longjmp'. These warnings as well are
- possible only in optimizing compilation.
+ This option also warns when a non-volatile automatic variable
+ might be changed by a call to `longjmp'. These warnings as well
+ are possible only in optimizing compilation.
- The compiler sees only the calls to 'setjmp'. It cannot know where
- 'longjmp' will be called; in fact, a signal handler could call it
- at any point in the code. As a result, you may get a warning even
- when there is in fact no problem because 'longjmp' cannot in fact
- be called at the place that would cause a problem.
+ The compiler sees only the calls to `setjmp'. It cannot know
+ where `longjmp' will be called; in fact, a signal handler could
+ call it at any point in the code. As a result, you may get a
+ warning even when there is in fact no problem because `longjmp'
+ cannot in fact be called at the place that would cause a problem.
Some spurious warnings can be avoided if you declare all the
- functions you use that never return as 'noreturn'. *Note Function
+ functions you use that never return as `noreturn'. *Note Function
Attributes::.
- This warning is enabled by '-Wall' or '-Wextra'.
+ This warning is enabled by `-Wall' or `-Wextra'.
-'-Wunknown-pragmas'
- Warn when a '#pragma' directive is encountered that is not
+`-Wunknown-pragmas'
+ Warn when a `#pragma' directive is encountered that is not
understood by GCC. If this command-line option is used, warnings
are even issued for unknown pragmas in system header files. This
- is not the case if the warnings are only enabled by the '-Wall'
+ is not the case if the warnings are only enabled by the `-Wall'
command-line option.
-'-Wno-pragmas'
+`-Wno-pragmas'
Do not warn about misuses of pragmas, such as incorrect parameters,
invalid syntax, or conflicts between pragmas. See also
- '-Wunknown-pragmas'.
+ `-Wunknown-pragmas'.
-'-Wstrict-aliasing'
- This option is only active when '-fstrict-aliasing' is active. It
+`-Wstrict-aliasing'
+ This option is only active when `-fstrict-aliasing' is active. It
warns about code that might break the strict aliasing rules that
- the compiler is using for optimization. The warning does not catch
- all cases, but does attempt to catch the more common pitfalls. It
- is included in '-Wall'. It is equivalent to '-Wstrict-aliasing=3'
+ the compiler is using for optimization. The warning does not
+ catch all cases, but does attempt to catch the more common
+ pitfalls. It is included in `-Wall'. It is equivalent to
+ `-Wstrict-aliasing=3'
-'-Wstrict-aliasing=n'
- This option is only active when '-fstrict-aliasing' is active. It
+`-Wstrict-aliasing=n'
+ This option is only active when `-fstrict-aliasing' is active. It
warns about code that might break the strict aliasing rules that
the compiler is using for optimization. Higher levels correspond
to higher accuracy (fewer false positives). Higher levels also
- correspond to more effort, similar to the way '-O' works.
- '-Wstrict-aliasing' is equivalent to '-Wstrict-aliasing=3'.
+ correspond to more effort, similar to the way `-O' works.
+ `-Wstrict-aliasing' is equivalent to `-Wstrict-aliasing=3'.
Level 1: Most aggressive, quick, least accurate. Possibly useful
- when higher levels do not warn but '-fstrict-aliasing' still breaks
- the code, as it has very few false negatives. However, it has many
- false positives. Warns for all pointer conversions between
- possibly incompatible types, even if never dereferenced. Runs in
- the front end only.
+ when higher levels do not warn but `-fstrict-aliasing' still
+ breaks the code, as it has very few false negatives. However, it
+ has many false positives. Warns for all pointer conversions
+ between possibly incompatible types, even if never dereferenced.
+ Runs in the front end only.
Level 2: Aggressive, quick, not too precise. May still have many
false positives (not as many as level 1 though), and few false
negatives (but possibly more than level 1). Unlike level 1, it
- only warns when an address is taken. Warns about incomplete types.
- Runs in the front end only.
+ only warns when an address is taken. Warns about incomplete
+ types. Runs in the front end only.
- Level 3 (default for '-Wstrict-aliasing'): Should have very few
+ Level 3 (default for `-Wstrict-aliasing'): Should have very few
false positives and few false negatives. Slightly slower than
levels 1 or 2 when optimization is enabled. Takes care of the
common pun+dereference pattern in the front end:
- '*(int*)&some_float'. If optimization is enabled, it also runs in
+ `*(int*)&some_float'. If optimization is enabled, it also runs in
the back end, where it deals with multiple statement cases using
flow-sensitive points-to information. Only warns when the
converted pointer is dereferenced. Does not warn about incomplete
types.
-'-Wstrict-overflow'
-'-Wstrict-overflow=N'
- This option is only active when '-fstrict-overflow' is active. It
+`-Wstrict-overflow'
+`-Wstrict-overflow=N'
+ This option is only active when `-fstrict-overflow' is active. It
warns about cases where the compiler optimizes based on the
assumption that signed overflow does not occur. Note that it does
not warn about all cases where the code might overflow: it only
@@ -4050,168 +4078,168 @@ compiler warns that an unrecognized option is present.
loop requires, in particular when determining whether a loop will
be executed at all.
- '-Wstrict-overflow=1'
- Warn about cases that are both questionable and easy to avoid.
- For example, with '-fstrict-overflow', the compiler simplifies
- 'x + 1 > x' to '1'. This level of '-Wstrict-overflow' is
- enabled by '-Wall'; higher levels are not, and must be
- explicitly requested.
+ `-Wstrict-overflow=1'
+ Warn about cases that are both questionable and easy to
+ avoid. For example, with `-fstrict-overflow', the compiler
+ simplifies `x + 1 > x' to `1'. This level of
+ `-Wstrict-overflow' is enabled by `-Wall'; higher levels are
+ not, and must be explicitly requested.
- '-Wstrict-overflow=2'
+ `-Wstrict-overflow=2'
Also warn about other cases where a comparison is simplified
- to a constant. For example: 'abs (x) >= 0'. This can only be
- simplified when '-fstrict-overflow' is in effect, because 'abs
- (INT_MIN)' overflows to 'INT_MIN', which is less than zero.
- '-Wstrict-overflow' (with no level) is the same as
- '-Wstrict-overflow=2'.
+ to a constant. For example: `abs (x) >= 0'. This can only be
+ simplified when `-fstrict-overflow' is in effect, because
+ `abs (INT_MIN)' overflows to `INT_MIN', which is less than
+ zero. `-Wstrict-overflow' (with no level) is the same as
+ `-Wstrict-overflow=2'.
- '-Wstrict-overflow=3'
+ `-Wstrict-overflow=3'
Also warn about other cases where a comparison is simplified.
- For example: 'x + 1 > 1' is simplified to 'x > 0'.
-
- '-Wstrict-overflow=4'
- Also warn about other simplifications not covered by the above
- cases. For example: '(x * 10) / 5' is simplified to 'x * 2'.
-
- '-Wstrict-overflow=5'
- Also warn about cases where the compiler reduces the magnitude
- of a constant involved in a comparison. For example: 'x + 2 >
- y' is simplified to 'x + 1 >= y'. This is reported only at
- the highest warning level because this simplification applies
- to many comparisons, so this warning level gives a very large
- number of false positives.
-
-'-Wsuggest-attribute=[pure|const|noreturn|format]'
- Warn for cases where adding an attribute may be beneficial. The
+ For example: `x + 1 > 1' is simplified to `x > 0'.
+
+ `-Wstrict-overflow=4'
+ Also warn about other simplifications not covered by the
+ above cases. For example: `(x * 10) / 5' is simplified to `x
+ * 2'.
+
+ `-Wstrict-overflow=5'
+ Also warn about cases where the compiler reduces the
+ magnitude of a constant involved in a comparison. For
+ example: `x + 2 > y' is simplified to `x + 1 >= y'. This is
+ reported only at the highest warning level because this
+ simplification applies to many comparisons, so this warning
+ level gives a very large number of false positives.
+
+`-Wsuggest-attribute=[pure|const|noreturn|format]'
+ Warn for cases where adding an attribute may be beneficial. The
attributes currently supported are listed below.
- '-Wsuggest-attribute=pure'
- '-Wsuggest-attribute=const'
- '-Wsuggest-attribute=noreturn'
-
+ `-Wsuggest-attribute=pure'
+ `-Wsuggest-attribute=const'
+ `-Wsuggest-attribute=noreturn'
Warn about functions that might be candidates for attributes
- 'pure', 'const' or 'noreturn'. The compiler only warns for
+ `pure', `const' or `noreturn'. The compiler only warns for
functions visible in other compilation units or (in the case
- of 'pure' and 'const') if it cannot prove that the function
- returns normally. A function returns normally if it doesn't
+ of `pure' and `const') if it cannot prove that the function
+ returns normally. A function returns normally if it doesn't
contain an infinite loop or return abnormally by throwing,
- calling 'abort' or trapping. This analysis requires option
- '-fipa-pure-const', which is enabled by default at '-O' and
+ calling `abort' or trapping. This analysis requires option
+ `-fipa-pure-const', which is enabled by default at `-O' and
higher. Higher optimization levels improve the accuracy of
the analysis.
- '-Wsuggest-attribute=format'
- '-Wmissing-format-attribute'
-
+ `-Wsuggest-attribute=format'
+ `-Wmissing-format-attribute'
Warn about function pointers that might be candidates for
- 'format' attributes. Note these are only possible candidates,
- not absolute ones. GCC guesses that function pointers with
- 'format' attributes that are used in assignment,
- initialization, parameter passing or return statements should
- have a corresponding 'format' attribute in the resulting type.
- I.e. the left-hand side of the assignment or initialization,
- the type of the parameter variable, or the return type of the
- containing function respectively should also have a 'format'
- attribute to avoid the warning.
+ `format' attributes. Note these are only possible
+ candidates, not absolute ones. GCC guesses that function
+ pointers with `format' attributes that are used in
+ assignment, initialization, parameter passing or return
+ statements should have a corresponding `format' attribute in
+ the resulting type. I.e. the left-hand side of the
+ assignment or initialization, the type of the parameter
+ variable, or the return type of the containing function
+ respectively should also have a `format' attribute to avoid
+ the warning.
GCC also warns about function definitions that might be
- candidates for 'format' attributes. Again, these are only
- possible candidates. GCC guesses that 'format' attributes
+ candidates for `format' attributes. Again, these are only
+ possible candidates. GCC guesses that `format' attributes
might be appropriate for any function that calls a function
- like 'vprintf' or 'vscanf', but this might not always be the
- case, and some functions for which 'format' attributes are
+ like `vprintf' or `vscanf', but this might not always be the
+ case, and some functions for which `format' attributes are
appropriate may not be detected.
-'-Wsuggest-final-types'
+`-Wsuggest-final-types'
Warn about types with virtual methods where code quality would be
- improved if the type were declared with the C++11 'final'
+ improved if the type were declared with the C++11 `final'
specifier, or, if possible, declared in an anonymous namespace.
This allows GCC to more aggressively devirtualize the polymorphic
- calls. This warning is more effective with link time optimization,
+ calls. This warning is more effective with link time optimization,
where the information about the class hierarchy graph is more
complete.
-'-Wsuggest-final-methods'
+`-Wsuggest-final-methods'
Warn about virtual methods where code quality would be improved if
- the method were declared with the C++11 'final' specifier, or, if
+ the method were declared with the C++11 `final' specifier, or, if
possible, its type were declared in an anonymous namespace or with
- the 'final' specifier. This warning is more effective with link
+ the `final' specifier. This warning is more effective with link
time optimization, where the information about the class hierarchy
- graph is more complete. It is recommended to first consider
- suggestions of '-Wsuggest-final-types' and then rebuild with new
+ graph is more complete. It is recommended to first consider
+ suggestions of `-Wsuggest-final-types' and then rebuild with new
annotations.
-'-Wsuggest-override'
+`-Wsuggest-override'
Warn about overriding virtual functions that are not marked with
the override keyword.
-'-Warray-bounds'
-'-Warray-bounds=N'
- This option is only active when '-ftree-vrp' is active (default for
- '-O2' and above). It warns about subscripts to arrays that are
- always out of bounds. This warning is enabled by '-Wall'.
+`-Warray-bounds'
+`-Warray-bounds=N'
+ This option is only active when `-ftree-vrp' is active (default
+ for `-O2' and above). It warns about subscripts to arrays that are
+ always out of bounds. This warning is enabled by `-Wall'.
- '-Warray-bounds=1'
- This is the warning level of '-Warray-bounds' and is enabled
- by '-Wall'; higher levels are not, and must be explicitly
+ `-Warray-bounds=1'
+ This is the warning level of `-Warray-bounds' and is enabled
+ by `-Wall'; higher levels are not, and must be explicitly
requested.
- '-Warray-bounds=2'
+ `-Warray-bounds=2'
This warning level also warns about out of bounds access for
arrays at the end of a struct and for arrays accessed through
- pointers. This warning level may give a larger number of
+ pointers. This warning level may give a larger number of
false positives and is deactivated by default.
-'-Wbool-compare'
+`-Wbool-compare'
Warn about boolean expression compared with an integer value
- different from 'true'/'false'. For instance, the following
+ different from `true'/`false'. For instance, the following
comparison is always false:
int n = 5;
...
if ((n > 1) == 2) { ... }
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Wno-discarded-qualifiers (C and Objective-C only)'
+`-Wno-discarded-qualifiers (C and Objective-C only)'
Do not warn if type qualifiers on pointers are being discarded.
- Typically, the compiler warns if a 'const char *' variable is
- passed to a function that takes a 'char *' parameter. This option
+ Typically, the compiler warns if a `const char *' variable is
+ passed to a function that takes a `char *' parameter. This option
can be used to suppress such a warning.
-'-Wno-discarded-array-qualifiers (C and Objective-C only)'
+`-Wno-discarded-array-qualifiers (C and Objective-C only)'
Do not warn if type qualifiers on arrays which are pointer targets
- are being discarded. Typically, the compiler warns if a 'const int
- (*)[]' variable is passed to a function that takes a 'int (*)[]'
+ are being discarded. Typically, the compiler warns if a `const int
+ (*)[]' variable is passed to a function that takes a `int (*)[]'
parameter. This option can be used to suppress such a warning.
-'-Wno-incompatible-pointer-types (C and Objective-C only)'
+`-Wno-incompatible-pointer-types (C and Objective-C only)'
Do not warn when there is a conversion between pointers that have
incompatible types. This warning is for cases not covered by
- '-Wno-pointer-sign', which warns for pointer argument passing or
+ `-Wno-pointer-sign', which warns for pointer argument passing or
assignment with different signedness.
-'-Wno-int-conversion (C and Objective-C only)'
+`-Wno-int-conversion (C and Objective-C only)'
Do not warn about incompatible integer to pointer and pointer to
integer conversions. This warning is about implicit conversions;
- for explicit conversions the warnings '-Wno-int-to-pointer-cast'
- and '-Wno-pointer-to-int-cast' may be used.
+ for explicit conversions the warnings `-Wno-int-to-pointer-cast'
+ and `-Wno-pointer-to-int-cast' may be used.
-'-Wno-div-by-zero'
+`-Wno-div-by-zero'
Do not warn about compile-time integer division by zero.
- Floating-point division by zero is not warned about, as it can be a
- legitimate way of obtaining infinities and NaNs.
+ Floating-point division by zero is not warned about, as it can be
+ a legitimate way of obtaining infinities and NaNs.
-'-Wsystem-headers'
+`-Wsystem-headers'
Print warning messages for constructs found in system header files.
Warnings from system headers are normally suppressed, on the
assumption that they usually do not indicate real problems and
would only make the compiler output harder to read. Using this
command-line option tells GCC to emit warnings from system headers
- as if they occurred in user code. However, note that using '-Wall'
- in conjunction with this option does _not_ warn about unknown
- pragmas in system headers--for that, '-Wunknown-pragmas' must also
- be used.
+ as if they occurred in user code. However, note that using
+ `-Wall' in conjunction with this option does _not_ warn about
+ unknown pragmas in system headers--for that, `-Wunknown-pragmas'
+ must also be used.
-'-Wtrampolines'
+`-Wtrampolines'
Warn about trampolines generated for pointers to nested functions.
A trampoline is a small piece of data or code that is created at
run time on the stack when the address of a nested function is
@@ -4221,7 +4249,7 @@ compiler warns that an unrecognized option is present.
and thus requires the stack to be made executable in order for the
program to work properly.
-'-Wfloat-equal'
+`-Wfloat-equal'
Warn if floating-point values are used in equality comparisons.
The idea behind this is that sometimes it is convenient (for the
@@ -4230,13 +4258,13 @@ compiler warns that an unrecognized option is present.
need to compute (by analyzing the code, or in some other way) the
maximum or likely maximum error that the computation introduces,
and allow for it when performing comparisons (and when producing
- output, but that's a different problem). In particular, instead of
- testing for equality, you should check to see whether the two
+ output, but that's a different problem). In particular, instead
+ of testing for equality, you should check to see whether the two
values have ranges that overlap; and this is done with the
relational operators, so equality comparisons are probably
mistaken.
-'-Wtraditional (C and Objective-C only)'
+`-Wtraditional (C and Objective-C only)'
Warn about certain constructs that behave differently in
traditional and ISO C. Also warn about ISO C constructs that have
no traditional C equivalent, and/or problematic constructs that
@@ -4248,34 +4276,35 @@ compiler warns that an unrecognized option is present.
* In traditional C, some preprocessor directives did not exist.
Traditional preprocessors only considered a line to be a
- directive if the '#' appeared in column 1 on the line.
- Therefore '-Wtraditional' warns about directives that
- traditional C understands but ignores because the '#' does not
- appear as the first character on the line. It also suggests
- you hide directives like '#pragma' not understood by
+ directive if the `#' appeared in column 1 on the line.
+ Therefore `-Wtraditional' warns about directives that
+ traditional C understands but ignores because the `#' does
+ not appear as the first character on the line. It also
+ suggests you hide directives like `#pragma' not understood by
traditional C by indenting them. Some traditional
- implementations do not recognize '#elif', so this option
+ implementations do not recognize `#elif', so this option
suggests avoiding it altogether.
* A function-like macro that appears without arguments.
* The unary plus operator.
- * The 'U' integer constant suffix, or the 'F' or 'L'
- floating-point constant suffixes. (Traditional C does support
- the 'L' suffix on integer constants.) Note, these suffixes
- appear in macros defined in the system headers of most modern
- systems, e.g. the '_MIN'/'_MAX' macros in '<limits.h>'. Use
- of these macros in user code might normally lead to spurious
- warnings, however GCC's integrated preprocessor has enough
- context to avoid warning in these cases.
+ * The `U' integer constant suffix, or the `F' or `L'
+ floating-point constant suffixes. (Traditional C does
+ support the `L' suffix on integer constants.) Note, these
+ suffixes appear in macros defined in the system headers of
+ most modern systems, e.g. the `_MIN'/`_MAX' macros in
+ `<limits.h>'. Use of these macros in user code might
+ normally lead to spurious warnings, however GCC's integrated
+ preprocessor has enough context to avoid warning in these
+ cases.
* A function declared external in one block and then used after
the end of the block.
- * A 'switch' statement has an operand of type 'long'.
+ * A `switch' statement has an operand of type `long'.
- * A non-'static' function declaration follows a 'static' one.
+ * A non-`static' function declaration follows a `static' one.
This construct is not accepted by some traditional C
compilers.
@@ -4295,161 +4324,165 @@ compiler warns that an unrecognized option is present.
* Initialization of unions. If the initializer is zero, the
warning is omitted. This is done under the assumption that
the zero initializer in user code appears conditioned on e.g.
- '__STDC__' to avoid missing initializer warnings and relies on
- default initialization to zero in the traditional C case.
+ `__STDC__' to avoid missing initializer warnings and relies
+ on default initialization to zero in the traditional C case.
* Conversions by prototypes between fixed/floating-point values
and vice versa. The absence of these prototypes when
- compiling with traditional C causes serious problems. This is
- a subset of the possible conversion warnings; for the full set
- use '-Wtraditional-conversion'.
+ compiling with traditional C causes serious problems. This
+ is a subset of the possible conversion warnings; for the full
+ set use `-Wtraditional-conversion'.
* Use of ISO C style function definitions. This warning
intentionally is _not_ issued for prototype declarations or
- variadic functions because these ISO C features appear in your
- code when using libiberty's traditional C compatibility
- macros, 'PARAMS' and 'VPARAMS'. This warning is also bypassed
- for nested functions because that feature is already a GCC
- extension and thus not relevant to traditional C
+ variadic functions because these ISO C features appear in
+ your code when using libiberty's traditional C compatibility
+ macros, `PARAMS' and `VPARAMS'. This warning is also
+ bypassed for nested functions because that feature is already
+ a GCC extension and thus not relevant to traditional C
compatibility.
-'-Wtraditional-conversion (C and Objective-C only)'
- Warn if a prototype causes a type conversion that is different from
- what would happen to the same argument in the absence of a
+`-Wtraditional-conversion (C and Objective-C only)'
+ Warn if a prototype causes a type conversion that is different
+ from what would happen to the same argument in the absence of a
prototype. This includes conversions of fixed point to floating
- and vice versa, and conversions changing the width or signedness of
- a fixed-point argument except when the same as the default
+ and vice versa, and conversions changing the width or signedness
+ of a fixed-point argument except when the same as the default
promotion.
-'-Wdeclaration-after-statement (C and Objective-C only)'
+`-Wdeclaration-after-statement (C and Objective-C only)'
Warn when a declaration is found after a statement in a block.
This construct, known from C++, was introduced with ISO C99 and is
by default allowed in GCC. It is not supported by ISO C90. *Note
Mixed Declarations::.
-'-Wundef'
- Warn if an undefined identifier is evaluated in an '#if' directive.
+`-Wundef'
+ Warn if an undefined identifier is evaluated in an `#if' directive.
-'-Wno-endif-labels'
- Do not warn whenever an '#else' or an '#endif' are followed by
+`-Wno-endif-labels'
+ Do not warn whenever an `#else' or an `#endif' are followed by
text.
-'-Wshadow'
+`-Wshadow'
Warn whenever a local variable or type declaration shadows another
variable, parameter, type, class member (in C++), or instance
variable (in Objective-C) or whenever a built-in function is
- shadowed. Note that in C++, the compiler warns if a local variable
+ shadowed. Note that in C++, the compiler warns if a local variable
shadows an explicit typedef, but not if it shadows a
struct/class/enum.
-'-Wno-shadow-ivar (Objective-C only)'
+`-Wno-shadow-ivar (Objective-C only)'
Do not warn whenever a local variable shadows an instance variable
in an Objective-C method.
-'-Wlarger-than=LEN'
+`-Wlarger-than=LEN'
Warn whenever an object of larger than LEN bytes is defined.
-'-Wframe-larger-than=LEN'
- Warn if the size of a function frame is larger than LEN bytes. The
- computation done to determine the stack frame size is approximate
- and not conservative. The actual requirements may be somewhat
- greater than LEN even if you do not get a warning. In addition,
- any space allocated via 'alloca', variable-length arrays, or
- related constructs is not included by the compiler when determining
- whether or not to issue a warning.
+`-Wframe-larger-than=LEN'
+ Warn if the size of a function frame is larger than LEN bytes.
+ The computation done to determine the stack frame size is
+ approximate and not conservative. The actual requirements may be
+ somewhat greater than LEN even if you do not get a warning. In
+ addition, any space allocated via `alloca', variable-length
+ arrays, or related constructs is not included by the compiler when
+ determining whether or not to issue a warning.
-'-Wno-free-nonheap-object'
+`-Wno-free-nonheap-object'
Do not warn when attempting to free an object that was not
allocated on the heap.
-'-Wstack-usage=LEN'
+`-Wstack-usage=LEN'
Warn if the stack usage of a function might be larger than LEN
bytes. The computation done to determine the stack usage is
- conservative. Any space allocated via 'alloca', variable-length
+ conservative. Any space allocated via `alloca', variable-length
arrays, or related constructs is included by the compiler when
determining whether or not to issue a warning.
- The message is in keeping with the output of '-fstack-usage'.
+ The message is in keeping with the output of `-fstack-usage'.
* If the stack usage is fully static but exceeds the specified
amount, it's:
warning: stack usage is 1120 bytes
+
* If the stack usage is (partly) dynamic but bounded, it's:
warning: stack usage might be 1648 bytes
+
* If the stack usage is (partly) dynamic and not bounded, it's:
warning: stack usage might be unbounded
-'-Wunsafe-loop-optimizations'
+`-Wunsafe-loop-optimizations'
Warn if the loop cannot be optimized because the compiler cannot
assume anything on the bounds of the loop indices. With
- '-funsafe-loop-optimizations' warn if the compiler makes such
+ `-funsafe-loop-optimizations' warn if the compiler makes such
assumptions.
-'-Wno-pedantic-ms-format (MinGW targets only)'
- When used in combination with '-Wformat' and '-pedantic' without
+`-Wno-pedantic-ms-format (MinGW targets only)'
+ When used in combination with `-Wformat' and `-pedantic' without
GNU extensions, this option disables the warnings about non-ISO
- 'printf' / 'scanf' format width specifiers 'I32', 'I64', and 'I'
+ `printf' / `scanf' format width specifiers `I32', `I64', and `I'
used on Windows targets, which depend on the MS runtime.
-'-Wpointer-arith'
+`-Wpointer-arith'
Warn about anything that depends on the "size of" a function type
- or of 'void'. GNU C assigns these types a size of 1, for
- convenience in calculations with 'void *' pointers and pointers to
+ or of `void'. GNU C assigns these types a size of 1, for
+ convenience in calculations with `void *' pointers and pointers to
functions. In C++, warn also when an arithmetic operation involves
- 'NULL'. This warning is also enabled by '-Wpedantic'.
+ `NULL'. This warning is also enabled by `-Wpedantic'.
-'-Wtype-limits'
+`-Wtype-limits'
Warn if a comparison is always true or always false due to the
limited range of the data type, but do not warn for constant
- expressions. For example, warn if an unsigned variable is compared
- against zero with '<' or '>='. This warning is also enabled by
- '-Wextra'.
+ expressions. For example, warn if an unsigned variable is
+ compared against zero with `<' or `>='. This warning is also
+ enabled by `-Wextra'.
-'-Wbad-function-cast (C and Objective-C only)'
+`-Wbad-function-cast (C and Objective-C only)'
Warn when a function call is cast to a non-matching type. For
example, warn if a call to a function returning an integer type is
cast to a pointer type.
-'-Wc90-c99-compat (C and Objective-C only)'
+`-Wc90-c99-compat (C and Objective-C only)'
Warn about features not present in ISO C90, but present in ISO C99.
- For instance, warn about use of variable length arrays, 'long long'
- type, 'bool' type, compound literals, designated initializers, and
- so on. This option is independent of the standards mode. Warnings
- are disabled in the expression that follows '__extension__'.
+ For instance, warn about use of variable length arrays, `long long'
+ type, `bool' type, compound literals, designated initializers, and
+ so on. This option is independent of the standards mode.
+ Warnings are disabled in the expression that follows
+ `__extension__'.
-'-Wc99-c11-compat (C and Objective-C only)'
+`-Wc99-c11-compat (C and Objective-C only)'
Warn about features not present in ISO C99, but present in ISO C11.
For instance, warn about use of anonymous structures and unions,
- '_Atomic' type qualifier, '_Thread_local' storage-class specifier,
- '_Alignas' specifier, 'Alignof' operator, '_Generic' keyword, and
- so on. This option is independent of the standards mode. Warnings
- are disabled in the expression that follows '__extension__'.
+ `_Atomic' type qualifier, `_Thread_local' storage-class specifier,
+ `_Alignas' specifier, `Alignof' operator, `_Generic' keyword, and
+ so on. This option is independent of the standards mode.
+ Warnings are disabled in the expression that follows
+ `__extension__'.
-'-Wc++-compat (C and Objective-C only)'
+`-Wc++-compat (C and Objective-C only)'
Warn about ISO C constructs that are outside of the common subset
of ISO C and ISO C++, e.g. request for implicit conversion from
- 'void *' to a pointer to non-'void' type.
+ `void *' to a pointer to non-`void' type.
-'-Wc++11-compat (C++ and Objective-C++ only)'
+`-Wc++11-compat (C++ and Objective-C++ only)'
Warn about C++ constructs whose meaning differs between ISO C++
1998 and ISO C++ 2011, e.g., identifiers in ISO C++ 1998 that are
- keywords in ISO C++ 2011. This warning turns on '-Wnarrowing' and
- is enabled by '-Wall'.
+ keywords in ISO C++ 2011. This warning turns on `-Wnarrowing' and
+ is enabled by `-Wall'.
-'-Wc++14-compat (C++ and Objective-C++ only)'
+`-Wc++14-compat (C++ and Objective-C++ only)'
Warn about C++ constructs whose meaning differs between ISO C++
- 2011 and ISO C++ 2014. This warning is enabled by '-Wall'.
+ 2011 and ISO C++ 2014. This warning is enabled by `-Wall'.
-'-Wcast-qual'
+`-Wcast-qual'
Warn whenever a pointer is cast so as to remove a type qualifier
- from the target type. For example, warn if a 'const char *' is
- cast to an ordinary 'char *'.
+ from the target type. For example, warn if a `const char *' is
+ cast to an ordinary `char *'.
Also warn when making a cast that introduces a type qualifier in an
- unsafe way. For example, casting 'char **' to 'const char **' is
+ unsafe way. For example, casting `char **' to `const char **' is
unsafe, as in this example:
/* p is char ** value. */
@@ -4459,111 +4492,112 @@ compiler warns that an unrecognized option is present.
/* Now char** pointer points to read-only memory. */
**p = 'b';
-'-Wcast-align'
- Warn whenever a pointer is cast such that the required alignment of
- the target is increased. For example, warn if a 'char *' is cast
- to an 'int *' on machines where integers can only be accessed at
- two- or four-byte boundaries.
-
-'-Wwrite-strings'
- When compiling C, give string constants the type 'const
- char[LENGTH]' so that copying the address of one into a non-'const'
- 'char *' pointer produces a warning. These warnings help you find
- at compile time code that can try to write into a string constant,
- but only if you have been very careful about using 'const' in
- declarations and prototypes. Otherwise, it is just a nuisance.
- This is why we did not make '-Wall' request these warnings.
+`-Wcast-align'
+ Warn whenever a pointer is cast such that the required alignment
+ of the target is increased. For example, warn if a `char *' is
+ cast to an `int *' on machines where integers can only be accessed
+ at two- or four-byte boundaries.
+
+`-Wwrite-strings'
+ When compiling C, give string constants the type `const
+ char[LENGTH]' so that copying the address of one into a
+ non-`const' `char *' pointer produces a warning. These warnings
+ help you find at compile time code that can try to write into a
+ string constant, but only if you have been very careful about
+ using `const' in declarations and prototypes. Otherwise, it is
+ just a nuisance. This is why we did not make `-Wall' request these
+ warnings.
When compiling C++, warn about the deprecated conversion from
- string literals to 'char *'. This warning is enabled by default
+ string literals to `char *'. This warning is enabled by default
for C++ programs.
-'-Wclobbered'
- Warn for variables that might be changed by 'longjmp' or 'vfork'.
- This warning is also enabled by '-Wextra'.
+`-Wclobbered'
+ Warn for variables that might be changed by `longjmp' or `vfork'.
+ This warning is also enabled by `-Wextra'.
-'-Wconditionally-supported (C++ and Objective-C++ only)'
+`-Wconditionally-supported (C++ and Objective-C++ only)'
Warn for conditionally-supported (C++11 [intro.defs]) constructs.
-'-Wconversion'
- Warn for implicit conversions that may alter a value. This
- includes conversions between real and integer, like 'abs (x)' when
- 'x' is 'double'; conversions between signed and unsigned, like
- 'unsigned ui = -1'; and conversions to smaller types, like 'sqrtf
- (M_PI)'. Do not warn for explicit casts like 'abs ((int) x)' and
- 'ui = (unsigned) -1', or if the value is not changed by the
- conversion like in 'abs (2.0)'. Warnings about conversions between
- signed and unsigned integers can be disabled by using
- '-Wno-sign-conversion'.
+`-Wconversion'
+ Warn for implicit conversions that may alter a value. This includes
+ conversions between real and integer, like `abs (x)' when `x' is
+ `double'; conversions between signed and unsigned, like `unsigned
+ ui = -1'; and conversions to smaller types, like `sqrtf (M_PI)'.
+ Do not warn for explicit casts like `abs ((int) x)' and `ui =
+ (unsigned) -1', or if the value is not changed by the conversion
+ like in `abs (2.0)'. Warnings about conversions between signed
+ and unsigned integers can be disabled by using
+ `-Wno-sign-conversion'.
For C++, also warn for confusing overload resolution for
user-defined conversions; and conversions that never use a type
- conversion operator: conversions to 'void', the same type, a base
- class or a reference to them. Warnings about conversions between
+ conversion operator: conversions to `void', the same type, a base
+ class or a reference to them. Warnings about conversions between
signed and unsigned integers are disabled by default in C++ unless
- '-Wsign-conversion' is explicitly enabled.
+ `-Wsign-conversion' is explicitly enabled.
-'-Wno-conversion-null (C++ and Objective-C++ only)'
- Do not warn for conversions between 'NULL' and non-pointer types.
- '-Wconversion-null' is enabled by default.
+`-Wno-conversion-null (C++ and Objective-C++ only)'
+ Do not warn for conversions between `NULL' and non-pointer types.
+ `-Wconversion-null' is enabled by default.
-'-Wzero-as-null-pointer-constant (C++ and Objective-C++ only)'
+`-Wzero-as-null-pointer-constant (C++ and Objective-C++ only)'
Warn when a literal '0' is used as null pointer constant. This can
- be useful to facilitate the conversion to 'nullptr' in C++11.
+ be useful to facilitate the conversion to `nullptr' in C++11.
-'-Wdate-time'
- Warn when macros '__TIME__', '__DATE__' or '__TIMESTAMP__' are
+`-Wdate-time'
+ Warn when macros `__TIME__', `__DATE__' or `__TIMESTAMP__' are
encountered as they might prevent bit-wise-identical reproducible
compilations.
-'-Wdelete-incomplete (C++ and Objective-C++ only)'
+`-Wdelete-incomplete (C++ and Objective-C++ only)'
Warn when deleting a pointer to incomplete type, which may cause
undefined behavior at runtime. This warning is enabled by default.
-'-Wuseless-cast (C++ and Objective-C++ only)'
+`-Wuseless-cast (C++ and Objective-C++ only)'
Warn when an expression is casted to its own type.
-'-Wempty-body'
- Warn if an empty body occurs in an 'if', 'else' or 'do while'
- statement. This warning is also enabled by '-Wextra'.
+`-Wempty-body'
+ Warn if an empty body occurs in an `if', `else' or `do while'
+ statement. This warning is also enabled by `-Wextra'.
-'-Wenum-compare'
+`-Wenum-compare'
Warn about a comparison between values of different enumerated
types. In C++ enumeral mismatches in conditional expressions are
also diagnosed and the warning is enabled by default. In C this
- warning is enabled by '-Wall'.
+ warning is enabled by `-Wall'.
-'-Wjump-misses-init (C, Objective-C only)'
- Warn if a 'goto' statement or a 'switch' statement jumps forward
+`-Wjump-misses-init (C, Objective-C only)'
+ Warn if a `goto' statement or a `switch' statement jumps forward
across the initialization of a variable, or jumps backward to a
label after the variable has been initialized. This only warns
about variables that are initialized when they are declared. This
warning is only supported for C and Objective-C; in C++ this sort
of branch is an error in any case.
- '-Wjump-misses-init' is included in '-Wc++-compat'. It can be
- disabled with the '-Wno-jump-misses-init' option.
+ `-Wjump-misses-init' is included in `-Wc++-compat'. It can be
+ disabled with the `-Wno-jump-misses-init' option.
-'-Wsign-compare'
+`-Wsign-compare'
Warn when a comparison between signed and unsigned values could
produce an incorrect result when the signed value is converted to
- unsigned. This warning is also enabled by '-Wextra'; to get the
- other warnings of '-Wextra' without this warning, use '-Wextra
+ unsigned. This warning is also enabled by `-Wextra'; to get the
+ other warnings of `-Wextra' without this warning, use `-Wextra
-Wno-sign-compare'.
-'-Wsign-conversion'
+`-Wsign-conversion'
Warn for implicit conversions that may change the sign of an
integer value, like assigning a signed integer expression to an
- unsigned integer variable. An explicit cast silences the warning.
- In C, this option is enabled also by '-Wconversion'.
+ unsigned integer variable. An explicit cast silences the warning.
+ In C, this option is enabled also by `-Wconversion'.
-'-Wfloat-conversion'
+`-Wfloat-conversion'
Warn for implicit conversions that reduce the precision of a real
value. This includes conversions from real to integer, and from
higher precision real to lower precision real values. This option
- is also enabled by '-Wconversion'.
+ is also enabled by `-Wconversion'.
-'-Wsized-deallocation (C++ and Objective-C++ only)'
+`-Wsized-deallocation (C++ and Objective-C++ only)'
Warn about a definition of an unsized deallocation function
void operator delete (void *) noexcept;
void operator delete[] (void *) noexcept;
@@ -4571,52 +4605,52 @@ compiler warns that an unrecognized option is present.
function
void operator delete (void *, std::size_t) noexcept;
void operator delete[] (void *, std::size_t) noexcept;
- or vice versa. Enabled by '-Wextra' along with
- '-fsized-deallocation'.
+ or vice versa. Enabled by `-Wextra' along with
+ `-fsized-deallocation'.
-'-Wsizeof-pointer-memaccess'
+`-Wsizeof-pointer-memaccess'
Warn for suspicious length parameters to certain string and memory
- built-in functions if the argument uses 'sizeof'. This warning
- warns e.g. about 'memset (ptr, 0, sizeof (ptr));' if 'ptr' is not
+ built-in functions if the argument uses `sizeof'. This warning
+ warns e.g. about `memset (ptr, 0, sizeof (ptr));' if `ptr' is not
an array, but a pointer, and suggests a possible fix, or about
- 'memcpy (&foo, ptr, sizeof (&foo));'. This warning is enabled by
- '-Wall'.
+ `memcpy (&foo, ptr, sizeof (&foo));'. This warning is enabled by
+ `-Wall'.
-'-Wsizeof-array-argument'
- Warn when the 'sizeof' operator is applied to a parameter that is
+`-Wsizeof-array-argument'
+ Warn when the `sizeof' operator is applied to a parameter that is
declared as an array in a function definition. This warning is
enabled by default for C and C++ programs.
-'-Wmemset-transposed-args'
- Warn for suspicious calls to the 'memset' built-in function, if the
+`-Wmemset-transposed-args'
+ Warn for suspicious calls to the `memset' built-in function, if the
second argument is not zero and the third argument is zero. This
- warns e.g. about 'memset (buf, sizeof buf, 0)' where most probably
- 'memset (buf, 0, sizeof buf)' was meant instead. The diagnostics
+ warns e.g. about `memset (buf, sizeof buf, 0)' where most probably
+ `memset (buf, 0, sizeof buf)' was meant instead. The diagnostics
is only emitted if the third argument is literal zero. If it is
some expression that is folded to zero, a cast of zero to some
type, etc., it is far less likely that the user has mistakenly
- exchanged the arguments and no warning is emitted. This warning is
- enabled by '-Wall'.
-
-'-Waddress'
- Warn about suspicious uses of memory addresses. These include
- using the address of a function in a conditional expression, such
- as 'void func(void); if (func)', and comparisons against the memory
- address of a string literal, such as 'if (x == "abc")'. Such uses
+ exchanged the arguments and no warning is emitted. This warning
+ is enabled by `-Wall'.
+
+`-Waddress'
+ Warn about suspicious uses of memory addresses. These include using
+ the address of a function in a conditional expression, such as
+ `void func(void); if (func)', and comparisons against the memory
+ address of a string literal, such as `if (x == "abc")'. Such uses
typically indicate a programmer error: the address of a function
always evaluates to true, so their use in a conditional usually
indicate that the programmer forgot the parentheses in a function
call; and comparisons against string literals result in unspecified
behavior and are not portable in C, so they usually indicate that
- the programmer intended to use 'strcmp'. This warning is enabled
- by '-Wall'.
+ the programmer intended to use `strcmp'. This warning is enabled
+ by `-Wall'.
-'-Wlogical-op'
+`-Wlogical-op'
Warn about suspicious uses of logical operators in expressions.
This includes using logical operators in contexts where a bit-wise
operator is likely to be expected.
-'-Wlogical-not-parentheses'
+`-Wlogical-not-parentheses'
Warn about logical not used on the left hand side operand of a
comparison. This option does not warn if the RHS operand is of a
boolean type. Its purpose is to detect suspicious code like the
@@ -4629,54 +4663,54 @@ compiler warns that an unrecognized option is present.
parentheses:
if ((!a) > 1) { ... }
- This warning is enabled by '-Wall'.
+ This warning is enabled by `-Wall'.
-'-Waggregate-return'
+`-Waggregate-return'
Warn if any functions that return structures or unions are defined
or called. (In languages where you can return an array, this also
elicits a warning.)
-'-Wno-aggressive-loop-optimizations'
+`-Wno-aggressive-loop-optimizations'
Warn if in a loop with constant number of iterations the compiler
detects undefined behavior in some statement during one or more of
the iterations.
-'-Wno-attributes'
- Do not warn if an unexpected '__attribute__' is used, such as
+`-Wno-attributes'
+ Do not warn if an unexpected `__attribute__' is used, such as
unrecognized attributes, function attributes applied to variables,
etc. This does not stop errors for incorrect use of supported
attributes.
-'-Wno-builtin-macro-redefined'
+`-Wno-builtin-macro-redefined'
Do not warn if certain built-in macros are redefined. This
- suppresses warnings for redefinition of '__TIMESTAMP__',
- '__TIME__', '__DATE__', '__FILE__', and '__BASE_FILE__'.
+ suppresses warnings for redefinition of `__TIMESTAMP__',
+ `__TIME__', `__DATE__', `__FILE__', and `__BASE_FILE__'.
-'-Wstrict-prototypes (C and Objective-C only)'
+`-Wstrict-prototypes (C and Objective-C only)'
Warn if a function is declared or defined without specifying the
argument types. (An old-style function definition is permitted
without a warning if preceded by a declaration that specifies the
argument types.)
-'-Wold-style-declaration (C and Objective-C only)'
+`-Wold-style-declaration (C and Objective-C only)'
Warn for obsolescent usages, according to the C Standard, in a
- declaration. For example, warn if storage-class specifiers like
- 'static' are not the first things in a declaration. This warning
- is also enabled by '-Wextra'.
+ declaration. For example, warn if storage-class specifiers like
+ `static' are not the first things in a declaration. This warning
+ is also enabled by `-Wextra'.
-'-Wold-style-definition (C and Objective-C only)'
+`-Wold-style-definition (C and Objective-C only)'
Warn if an old-style function definition is used. A warning is
given even if there is a previous prototype.
-'-Wmissing-parameter-type (C and Objective-C only)'
+`-Wmissing-parameter-type (C and Objective-C only)'
A function parameter is declared without a type specifier in
K&R-style functions:
void foo(bar) { }
- This warning is also enabled by '-Wextra'.
+ This warning is also enabled by `-Wextra'.
-'-Wmissing-prototypes (C and Objective-C only)'
+`-Wmissing-prototypes (C and Objective-C only)'
Warn if a global function is defined without a previous prototype
declaration. This warning is issued even if the definition itself
provides a prototype. Use this option to detect global functions
@@ -4684,22 +4718,22 @@ compiler warns that an unrecognized option is present.
This option is not valid for C++ because all function declarations
provide prototypes and a non-matching declaration declares an
overload rather than conflict with an earlier declaration. Use
- '-Wmissing-declarations' to detect missing declarations in C++.
+ `-Wmissing-declarations' to detect missing declarations in C++.
-'-Wmissing-declarations'
+`-Wmissing-declarations'
Warn if a global function is defined without a previous
declaration. Do so even if the definition itself provides a
- prototype. Use this option to detect global functions that are not
- declared in header files. In C, no warnings are issued for
+ prototype. Use this option to detect global functions that are
+ not declared in header files. In C, no warnings are issued for
functions with previous non-prototype declarations; use
- '-Wmissing-prototypes' to detect missing prototypes. In C++, no
+ `-Wmissing-prototypes' to detect missing prototypes. In C++, no
warnings are issued for function templates, or for inline
functions, or for functions in anonymous namespaces.
-'-Wmissing-field-initializers'
+`-Wmissing-field-initializers'
Warn if a structure's initializer has some fields missing. For
- example, the following code causes such a warning, because 'x.h' is
- implicitly zero:
+ example, the following code causes such a warning, because `x.h'
+ is implicitly zero:
struct s { int f, g, h; };
struct s x = { 3, 4 };
@@ -4716,97 +4750,98 @@ compiler warns that an unrecognized option is present.
struct s { int f, g, h; };
s x = { };
- This warning is included in '-Wextra'. To get other '-Wextra'
- warnings without this one, use '-Wextra
+ This warning is included in `-Wextra'. To get other `-Wextra'
+ warnings without this one, use `-Wextra
-Wno-missing-field-initializers'.
-'-Wno-multichar'
- Do not warn if a multicharacter constant (''FOOF'') is used.
+`-Wno-multichar'
+ Do not warn if a multicharacter constant (`'FOOF'') is used.
Usually they indicate a typo in the user's code, as they have
implementation-defined values, and should not be used in portable
code.
-'-Wnormalized[=<none|id|nfc|nfkc>]'
+`-Wnormalized[=<none|id|nfc|nfkc>]'
In ISO C and ISO C++, two identifiers are different if they are
different sequences of characters. However, sometimes when
characters outside the basic ASCII character set are used, you can
have two different character sequences that look the same. To
avoid confusion, the ISO 10646 standard sets out some
"normalization rules" which when applied ensure that two sequences
- that look the same are turned into the same sequence. GCC can warn
- you if you are using identifiers that have not been normalized;
- this option controls that warning.
+ that look the same are turned into the same sequence. GCC can
+ warn you if you are using identifiers that have not been
+ normalized; this option controls that warning.
There are four levels of warning supported by GCC. The default is
- '-Wnormalized=nfc', which warns about any identifier that is not in
- the ISO 10646 "C" normalized form, "NFC". NFC is the recommended
- form for most uses. It is equivalent to '-Wnormalized'.
+ `-Wnormalized=nfc', which warns about any identifier that is not
+ in the ISO 10646 "C" normalized form, "NFC". NFC is the
+ recommended form for most uses. It is equivalent to
+ `-Wnormalized'.
Unfortunately, there are some characters allowed in identifiers by
ISO C and ISO C++ that, when turned into NFC, are not allowed in
identifiers. That is, there's no way to use these symbols in
portable ISO C or C++ and have all your identifiers in NFC.
- '-Wnormalized=id' suppresses the warning for these characters. It
+ `-Wnormalized=id' suppresses the warning for these characters. It
is hoped that future versions of the standards involved will
correct this, which is why this option is not the default.
You can switch the warning off for all characters by writing
- '-Wnormalized=none' or '-Wno-normalized'. You should only do this
+ `-Wnormalized=none' or `-Wno-normalized'. You should only do this
if you are using some other normalization scheme (like "D"),
because otherwise you can easily create bugs that are literally
impossible to see.
Some characters in ISO 10646 have distinct meanings but look
identical in some fonts or display methodologies, especially once
- formatting has been applied. For instance '\u207F', "SUPERSCRIPT
- LATIN SMALL LETTER N", displays just like a regular 'n' that has
+ formatting has been applied. For instance `\u207F', "SUPERSCRIPT
+ LATIN SMALL LETTER N", displays just like a regular `n' that has
been placed in a superscript. ISO 10646 defines the "NFKC"
normalization scheme to convert all these into a standard form as
well, and GCC warns if your code is not in NFKC if you use
- '-Wnormalized=nfkc'. This warning is comparable to warning about
+ `-Wnormalized=nfkc'. This warning is comparable to warning about
every identifier that contains the letter O because it might be
confused with the digit 0, and so is not the default, but may be
useful as a local coding convention if the programming environment
cannot be fixed to display these characters distinctly.
-'-Wno-deprecated'
+`-Wno-deprecated'
Do not warn about usage of deprecated features. *Note Deprecated
Features::.
-'-Wno-deprecated-declarations'
+`-Wno-deprecated-declarations'
Do not warn about uses of functions (*note Function Attributes::),
variables (*note Variable Attributes::), and types (*note Type
- Attributes::) marked as deprecated by using the 'deprecated'
+ Attributes::) marked as deprecated by using the `deprecated'
attribute.
-'-Wno-overflow'
+`-Wno-overflow'
Do not warn about compile-time overflow in constant expressions.
-'-Wno-odr'
+`-Wno-odr'
Warn about One Definition Rule violations during link-time
- optimization. Requires '-flto-odr-type-merging' to be enabled.
+ optimization. Requires `-flto-odr-type-merging' to be enabled.
Enabled by default.
-'-Wopenmp-simd'
+`-Wopenmp-simd'
Warn if the vectorizer cost model overrides the OpenMP or the Cilk
- Plus simd directive set by user. The '-fsimd-cost-model=unlimited'
+ Plus simd directive set by user. The `-fsimd-cost-model=unlimited'
option can be used to relax the cost model.
-'-Woverride-init (C and Objective-C only)'
+`-Woverride-init (C and Objective-C only)'
Warn if an initialized field without side effects is overridden
when using designated initializers (*note Designated Initializers:
Designated Inits.).
- This warning is included in '-Wextra'. To get other '-Wextra'
- warnings without this one, use '-Wextra -Wno-override-init'.
+ This warning is included in `-Wextra'. To get other `-Wextra'
+ warnings without this one, use `-Wextra -Wno-override-init'.
-'-Wpacked'
+`-Wpacked'
Warn if a structure is given the packed attribute, but the packed
attribute has no effect on the layout or size of the structure.
Such structures may be mis-aligned for little benefit. For
- instance, in this code, the variable 'f.x' in 'struct bar' is
- misaligned even though 'struct bar' does not itself have the packed
- attribute:
+ instance, in this code, the variable `f.x' in `struct bar' is
+ misaligned even though `struct bar' does not itself have the
+ packed attribute:
struct foo {
int x;
@@ -4817,13 +4852,13 @@ compiler warns that an unrecognized option is present.
struct foo f;
};
-'-Wpacked-bitfield-compat'
- The 4.1, 4.2 and 4.3 series of GCC ignore the 'packed' attribute on
- bit-fields of type 'char'. This has been fixed in GCC 4.4 but the
- change can lead to differences in the structure layout. GCC
+`-Wpacked-bitfield-compat'
+ The 4.1, 4.2 and 4.3 series of GCC ignore the `packed' attribute
+ on bit-fields of type `char'. This has been fixed in GCC 4.4 but
+ the change can lead to differences in the structure layout. GCC
informs you when the offset of such a field has changed in GCC 4.4.
- For example there is no longer a 4-bit padding between field 'a'
- and 'b' in this structure:
+ For example there is no longer a 4-bit padding between field `a'
+ and `b' in this structure:
struct foo
{
@@ -4832,28 +4867,29 @@ compiler warns that an unrecognized option is present.
} __attribute__ ((packed));
This warning is enabled by default. Use
- '-Wno-packed-bitfield-compat' to disable this warning.
+ `-Wno-packed-bitfield-compat' to disable this warning.
-'-Wpadded'
+`-Wpadded'
Warn if padding is included in a structure, either to align an
element of the structure or to align the whole structure.
Sometimes when this happens it is possible to rearrange the fields
of the structure to reduce the padding and so make the structure
smaller.
-'-Wredundant-decls'
- Warn if anything is declared more than once in the same scope, even
- in cases where multiple declaration is valid and changes nothing.
+`-Wredundant-decls'
+ Warn if anything is declared more than once in the same scope,
+ even in cases where multiple declaration is valid and changes
+ nothing.
-'-Wnested-externs (C and Objective-C only)'
- Warn if an 'extern' declaration is encountered within a function.
+`-Wnested-externs (C and Objective-C only)'
+ Warn if an `extern' declaration is encountered within a function.
-'-Wno-inherited-variadic-ctor'
+`-Wno-inherited-variadic-ctor'
Suppress warnings about use of C++11 inheriting constructors when
the base class inherited from has a C variadic constructor; the
warning is on by default because the ellipsis is not inherited.
-'-Winline'
+`-Winline'
Warn if a function that is declared as inline cannot be inlined.
Even with this option, the compiler does not warn about failures to
inline functions declared in system headers.
@@ -4863,61 +4899,61 @@ compiler warns that an unrecognized option is present.
account the size of the function being inlined and the amount of
inlining that has already been done in the current function.
Therefore, seemingly insignificant changes in the source program
- can cause the warnings produced by '-Winline' to appear or
+ can cause the warnings produced by `-Winline' to appear or
disappear.
-'-Wno-invalid-offsetof (C++ and Objective-C++ only)'
- Suppress warnings from applying the 'offsetof' macro to a non-POD
- type. According to the 2014 ISO C++ standard, applying 'offsetof'
+`-Wno-invalid-offsetof (C++ and Objective-C++ only)'
+ Suppress warnings from applying the `offsetof' macro to a non-POD
+ type. According to the 2014 ISO C++ standard, applying `offsetof'
to a non-standard-layout type is undefined. In existing C++
- implementations, however, 'offsetof' typically gives meaningful
+ implementations, however, `offsetof' typically gives meaningful
results. This flag is for users who are aware that they are
- writing nonportable code and who have deliberately chosen to ignore
- the warning about it.
+ writing nonportable code and who have deliberately chosen to
+ ignore the warning about it.
- The restrictions on 'offsetof' may be relaxed in a future version
+ The restrictions on `offsetof' may be relaxed in a future version
of the C++ standard.
-'-Wno-int-to-pointer-cast'
+`-Wno-int-to-pointer-cast'
Suppress warnings from casts to pointer type of an integer of a
- different size. In C++, casting to a pointer type of smaller size
- is an error. 'Wint-to-pointer-cast' is enabled by default.
+ different size. In C++, casting to a pointer type of smaller size
+ is an error. `Wint-to-pointer-cast' is enabled by default.
-'-Wno-pointer-to-int-cast (C and Objective-C only)'
+`-Wno-pointer-to-int-cast (C and Objective-C only)'
Suppress warnings from casts from a pointer to an integer type of a
different size.
-'-Winvalid-pch'
- Warn if a precompiled header (*note Precompiled Headers::) is found
- in the search path but can't be used.
+`-Winvalid-pch'
+ Warn if a precompiled header (*note Precompiled Headers::) is
+ found in the search path but can't be used.
-'-Wlong-long'
- Warn if 'long long' type is used. This is enabled by either
- '-Wpedantic' or '-Wtraditional' in ISO C90 and C++98 modes. To
- inhibit the warning messages, use '-Wno-long-long'.
+`-Wlong-long'
+ Warn if `long long' type is used. This is enabled by either
+ `-Wpedantic' or `-Wtraditional' in ISO C90 and C++98 modes. To
+ inhibit the warning messages, use `-Wno-long-long'.
-'-Wvariadic-macros'
+`-Wvariadic-macros'
Warn if variadic macros are used in ISO C90 mode, or if the GNU
alternate syntax is used in ISO C99 mode. This is enabled by
- either '-Wpedantic' or '-Wtraditional'. To inhibit the warning
- messages, use '-Wno-variadic-macros'.
+ either `-Wpedantic' or `-Wtraditional'. To inhibit the warning
+ messages, use `-Wno-variadic-macros'.
-'-Wvarargs'
+`-Wvarargs'
Warn upon questionable usage of the macros used to handle variable
- arguments like 'va_start'. This is default. To inhibit the
- warning messages, use '-Wno-varargs'.
+ arguments like `va_start'. This is default. To inhibit the
+ warning messages, use `-Wno-varargs'.
-'-Wvector-operation-performance'
+`-Wvector-operation-performance'
Warn if vector operation is not implemented via SIMD capabilities
of the architecture. Mainly useful for the performance tuning.
- Vector operation can be implemented 'piecewise', which means that
- the scalar operation is performed on every vector element; 'in
+ Vector operation can be implemented `piecewise', which means that
+ the scalar operation is performed on every vector element; `in
parallel', which means that the vector operation is implemented
using scalars of wider type, which normally is more performance
- efficient; and 'as a single scalar', which means that vector fits
+ efficient; and `as a single scalar', which means that vector fits
into a scalar type.
-'-Wno-virtual-move-assign'
+`-Wno-virtual-move-assign'
Suppress warnings about inheriting from a virtual base with a
non-trivial C++11 move assignment operator. This is dangerous
because if the virtual base is reachable along more than one path,
@@ -4926,17 +4962,17 @@ compiler warns that an unrecognized option is present.
to avoid moving from a moved-from object, this warning can be
disabled.
-'-Wvla'
- Warn if variable length array is used in the code. '-Wno-vla'
- prevents the '-Wpedantic' warning of the variable length array.
+`-Wvla'
+ Warn if variable length array is used in the code. `-Wno-vla'
+ prevents the `-Wpedantic' warning of the variable length array.
-'-Wvolatile-register-var'
+`-Wvolatile-register-var'
Warn if a register variable is declared volatile. The volatile
modifier does not inhibit all optimizations that may eliminate
- reads and/or writes to register variables. This warning is enabled
- by '-Wall'.
+ reads and/or writes to register variables. This warning is
+ enabled by `-Wall'.
-'-Wdisabled-optimization'
+`-Wdisabled-optimization'
Warn if a requested optimization pass is disabled. This warning
does not generally indicate that there is anything wrong with your
code; it merely indicates that GCC's optimizers are unable to
@@ -4945,18 +4981,18 @@ compiler warns that an unrecognized option is present.
the optimization itself is likely to take inordinate amounts of
time.
-'-Wpointer-sign (C and Objective-C only)'
+`-Wpointer-sign (C and Objective-C only)'
Warn for pointer argument passing or assignment with different
signedness. This option is only supported for C and Objective-C.
- It is implied by '-Wall' and by '-Wpedantic', which can be disabled
- with '-Wno-pointer-sign'.
+ It is implied by `-Wall' and by `-Wpedantic', which can be
+ disabled with `-Wno-pointer-sign'.
-'-Wstack-protector'
- This option is only active when '-fstack-protector' is active. It
+`-Wstack-protector'
+ This option is only active when `-fstack-protector' is active. It
warns about functions that are not protected against stack
smashing.
-'-Woverlength-strings'
+`-Woverlength-strings'
Warn about string constants that are longer than the "minimum
maximum" length specified in the C standard. Modern compilers
generally allow string constants that are much longer than the
@@ -4968,21 +5004,21 @@ compiler warns that an unrecognized option is present.
in C99, it was raised to 4095. C++98 does not specify a normative
minimum maximum, so we do not diagnose overlength strings in C++.
- This option is implied by '-Wpedantic', and can be disabled with
- '-Wno-overlength-strings'.
-
-'-Wunsuffixed-float-constants (C and Objective-C only)'
+ This option is implied by `-Wpedantic', and can be disabled with
+ `-Wno-overlength-strings'.
+`-Wunsuffixed-float-constants (C and Objective-C only)'
Issue a warning for any floating constant that does not have a
- suffix. When used together with '-Wsystem-headers' it warns about
+ suffix. When used together with `-Wsystem-headers' it warns about
such constants in system header files. This can be useful when
- preparing code to use with the 'FLOAT_CONST_DECIMAL64' pragma from
+ preparing code to use with the `FLOAT_CONST_DECIMAL64' pragma from
the decimal floating-point extension to C99.
-'-Wno-designated-init (C and Objective-C only)'
+`-Wno-designated-init (C and Objective-C only)'
Suppress warnings when a positional initializer is used to
initialize a structure that has been marked with the
- 'designated_init' attribute.
+ `designated_init' attribute.
+

File: gcc.info, Node: Debugging Options, Next: Optimize Options, Prev: Warning Options, Up: Invoking GCC
@@ -4993,20 +5029,20 @@ File: gcc.info, Node: Debugging Options, Next: Optimize Options, Prev: Warnin
GCC has various special options that are used for debugging either your
program or GCC:
-'-g'
+`-g'
Produce debugging information in the operating system's native
format (stabs, COFF, XCOFF, or DWARF 2). GDB can work with this
debugging information.
- On most systems that use stabs format, '-g' enables use of extra
+ On most systems that use stabs format, `-g' enables use of extra
debugging information that only GDB can use; this extra information
makes debugging work better in GDB but probably makes other
debuggers crash or refuse to read the program. If you want to
control for certain whether to generate the extra information, use
- '-gstabs+', '-gstabs', '-gxcoff+', '-gxcoff', or '-gvms' (see
+ `-gstabs+', `-gstabs', `-gxcoff+', `-gxcoff', or `-gvms' (see
below).
- GCC allows you to use '-g' with '-O'. The shortcuts taken by
+ GCC allows you to use `-g' with `-O'. The shortcuts taken by
optimized code may occasionally produce surprising results: some
variables you declared may not exist at all; flow of control may
briefly move where you did not expect it; some statements may not
@@ -5021,73 +5057,73 @@ program or GCC:
The following options are useful when GCC is generated with the
capability for more than one debugging format.
-'-gsplit-dwarf'
+`-gsplit-dwarf'
Separate as much dwarf debugging information as possible into a
separate output file with the extension .dwo. This option allows
the build system to avoid linking files with debug information. To
be useful, this option requires a debugger capable of reading .dwo
files.
-'-ggdb'
+`-ggdb'
Produce debugging information for use by GDB. This means to use
- the most expressive format available (DWARF 2, stabs, or the native
- format if neither of those are supported), including GDB extensions
- if at all possible.
+ the most expressive format available (DWARF 2, stabs, or the
+ native format if neither of those are supported), including GDB
+ extensions if at all possible.
-'-gpubnames'
+`-gpubnames'
Generate dwarf .debug_pubnames and .debug_pubtypes sections.
-'-ggnu-pubnames'
+`-ggnu-pubnames'
Generate .debug_pubnames and .debug_pubtypes sections in a format
suitable for conversion into a GDB index. This option is only
useful with a linker that can produce GDB index version 7.
-'-gstabs'
+`-gstabs'
Produce debugging information in stabs format (if that is
- supported), without GDB extensions. This is the format used by DBX
- on most BSD systems. On MIPS, Alpha and System V Release 4 systems
- this option produces stabs debugging output that is not understood
- by DBX or SDB. On System V Release 4 systems this option requires
- the GNU assembler.
+ supported), without GDB extensions. This is the format used by
+ DBX on most BSD systems. On MIPS, Alpha and System V Release 4
+ systems this option produces stabs debugging output that is not
+ understood by DBX or SDB. On System V Release 4 systems this
+ option requires the GNU assembler.
-'-feliminate-unused-debug-symbols'
+`-feliminate-unused-debug-symbols'
Produce debugging information in stabs format (if that is
supported), for only symbols that are actually used.
-'-femit-class-debug-always'
+`-femit-class-debug-always'
Instead of emitting debugging information for a C++ class in only
- one object file, emit it in all object files using the class. This
- option should be used only with debuggers that are unable to handle
- the way GCC normally emits debugging information for classes
- because using this option increases the size of debugging
+ one object file, emit it in all object files using the class.
+ This option should be used only with debuggers that are unable to
+ handle the way GCC normally emits debugging information for
+ classes because using this option increases the size of debugging
information by as much as a factor of two.
-'-fdebug-types-section'
+`-fdebug-types-section'
When using DWARF Version 4 or higher, type DIEs can be put into
- their own '.debug_types' section instead of making them part of the
- '.debug_info' section. It is more efficient to put them in a
+ their own `.debug_types' section instead of making them part of the
+ `.debug_info' section. It is more efficient to put them in a
separate comdat sections since the linker can then remove
- duplicates. But not all DWARF consumers support '.debug_types'
- sections yet and on some objects '.debug_types' produces larger
+ duplicates. But not all DWARF consumers support `.debug_types'
+ sections yet and on some objects `.debug_types' produces larger
instead of smaller debugging information.
-'-gstabs+'
+`-gstabs+'
Produce debugging information in stabs format (if that is
supported), using GNU extensions understood only by the GNU
debugger (GDB). The use of these extensions is likely to make
other debuggers crash or refuse to read the program.
-'-gcoff'
+`-gcoff'
Produce debugging information in COFF format (if that is
supported). This is the format used by SDB on most System V
systems prior to System V Release 4.
-'-gxcoff'
+`-gxcoff'
Produce debugging information in XCOFF format (if that is
supported). This is the format used by the DBX debugger on IBM
RS/6000 systems.
-'-gxcoff+'
+`-gxcoff+'
Produce debugging information in XCOFF format (if that is
supported), using GNU extensions understood only by the GNU
debugger (GDB). The use of these extensions is likely to make
@@ -5095,7 +5131,7 @@ program or GCC:
assemblers other than the GNU assembler (GAS) to fail with an
error.
-'-gdwarf-VERSION'
+`-gdwarf-VERSION'
Produce debugging information in DWARF format (if that is
supported). The value of VERSION may be either 2, 3, 4 or 5; the
default version for most targets is 4. DWARF Version 5 is only
@@ -5104,144 +5140,144 @@ program or GCC:
Note that with DWARF Version 2, some ports require and always use
some non-conflicting DWARF 3 extensions in the unwind tables.
- Version 4 may require GDB 7.0 and '-fvar-tracking-assignments' for
+ Version 4 may require GDB 7.0 and `-fvar-tracking-assignments' for
maximum benefit.
-'-grecord-gcc-switches'
+`-grecord-gcc-switches'
This switch causes the command-line options used to invoke the
compiler that may affect code generation to be appended to the
DW_AT_producer attribute in DWARF debugging information. The
options are concatenated with spaces separating them from each
other and from the compiler version. See also
- '-frecord-gcc-switches' for another way of storing compiler options
- into the object file. This is the default.
+ `-frecord-gcc-switches' for another way of storing compiler
+ options into the object file. This is the default.
-'-gno-record-gcc-switches'
+`-gno-record-gcc-switches'
Disallow appending command-line options to the DW_AT_producer
attribute in DWARF debugging information.
-'-gstrict-dwarf'
+`-gstrict-dwarf'
Disallow using extensions of later DWARF standard version than
- selected with '-gdwarf-VERSION'. On most targets using
+ selected with `-gdwarf-VERSION'. On most targets using
non-conflicting DWARF extensions from later standard versions is
allowed.
-'-gno-strict-dwarf'
+`-gno-strict-dwarf'
Allow using extensions of later DWARF standard version than
- selected with '-gdwarf-VERSION'.
+ selected with `-gdwarf-VERSION'.
-'-gz[=TYPE]'
+`-gz[=TYPE]'
Produce compressed debug sections in DWARF format, if that is
supported. If TYPE is not given, the default type depends on the
capabilities of the assembler and linker used. TYPE may be one of
- 'none' (don't compress debug sections), 'zlib' (use zlib
- compression in ELF gABI format), or 'zlib-gnu' (use zlib
+ `none' (don't compress debug sections), `zlib' (use zlib
+ compression in ELF gABI format), or `zlib-gnu' (use zlib
compression in traditional GNU format). If the linker doesn't
support writing compressed debug sections, the option is rejected.
- Otherwise, if the assembler does not support them, '-gz' is
+ Otherwise, if the assembler does not support them, `-gz' is
silently ignored when producing object files.
-'-gvms'
+`-gvms'
Produce debugging information in Alpha/VMS debug format (if that is
supported). This is the format used by DEBUG on Alpha/VMS systems.
-'-gLEVEL'
-'-ggdbLEVEL'
-'-gstabsLEVEL'
-'-gcoffLEVEL'
-'-gxcoffLEVEL'
-'-gvmsLEVEL'
+`-gLEVEL'
+`-ggdbLEVEL'
+`-gstabsLEVEL'
+`-gcoffLEVEL'
+`-gxcoffLEVEL'
+`-gvmsLEVEL'
Request debugging information and also use LEVEL to specify how
much information. The default level is 2.
- Level 0 produces no debug information at all. Thus, '-g0' negates
- '-g'.
+ Level 0 produces no debug information at all. Thus, `-g0' negates
+ `-g'.
Level 1 produces minimal information, enough for making backtraces
in parts of the program that you don't plan to debug. This
- includes descriptions of functions and external variables, and line
- number tables, but no information about local variables.
+ includes descriptions of functions and external variables, and
+ line number tables, but no information about local variables.
Level 3 includes extra information, such as all the macro
definitions present in the program. Some debuggers support macro
- expansion when you use '-g3'.
+ expansion when you use `-g3'.
- '-gdwarf-2' does not accept a concatenated debug level, because GCC
- used to support an option '-gdwarf' that meant to generate debug
- information in version 1 of the DWARF format (which is very
+ `-gdwarf-2' does not accept a concatenated debug level, because
+ GCC used to support an option `-gdwarf' that meant to generate
+ debug information in version 1 of the DWARF format (which is very
different from version 2), and it would have been too confusing.
That debug format is long obsolete, but the option cannot be
- changed now. Instead use an additional '-gLEVEL' option to change
+ changed now. Instead use an additional `-gLEVEL' option to change
the debug level for DWARF.
-'-gtoggle'
+`-gtoggle'
Turn off generation of debug info, if leaving out this option
generates it, or turn it on at level 2 otherwise. The position of
this argument in the command line does not matter; it takes effect
- after all other options are processed, and it does so only once, no
- matter how many times it is given. This is mainly intended to be
- used with '-fcompare-debug'.
+ after all other options are processed, and it does so only once,
+ no matter how many times it is given. This is mainly intended to
+ be used with `-fcompare-debug'.
-'-fsanitize=address'
+`-fsanitize=address'
Enable AddressSanitizer, a fast memory error detector. Memory
access instructions are instrumented to detect out-of-bounds and
use-after-free bugs. See
- <http://code.google.com/p/address-sanitizer/> for more details.
- The run-time behavior can be influenced using the 'ASAN_OPTIONS'
+ `http://code.google.com/p/address-sanitizer/' for more details.
+ The run-time behavior can be influenced using the `ASAN_OPTIONS'
environment variable; see
- <https://code.google.com/p/address-sanitizer/wiki/Flags#Run-time_flags>
+ `https://code.google.com/p/address-sanitizer/wiki/Flags#Run-time_flags'
for a list of supported options.
-'-fsanitize=kernel-address'
+`-fsanitize=kernel-address'
Enable AddressSanitizer for Linux kernel. See
- <http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel>
+ `http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel'
for more details.
-'-fsanitize=thread'
+`-fsanitize=thread'
Enable ThreadSanitizer, a fast data race detector. Memory access
instructions are instrumented to detect data race bugs. See
- <http://code.google.com/p/thread-sanitizer/> for more details. The
- run-time behavior can be influenced using the 'TSAN_OPTIONS'
+ `http://code.google.com/p/thread-sanitizer/' for more details. The
+ run-time behavior can be influenced using the `TSAN_OPTIONS'
environment variable; see
- <https://code.google.com/p/thread-sanitizer/wiki/Flags> for a list
+ `https://code.google.com/p/thread-sanitizer/wiki/Flags' for a list
of supported options.
-'-fsanitize=leak'
+`-fsanitize=leak'
Enable LeakSanitizer, a memory leak detector. This option only
matters for linking of executables and if neither
- '-fsanitize=address' nor '-fsanitize=thread' is used. In that case
- the executable is linked against a library that overrides 'malloc'
- and other allocator functions. See
- <https://code.google.com/p/address-sanitizer/wiki/LeakSanitizer>
+ `-fsanitize=address' nor `-fsanitize=thread' is used. In that
+ case the executable is linked against a library that overrides
+ `malloc' and other allocator functions. See
+ `https://code.google.com/p/address-sanitizer/wiki/LeakSanitizer'
for more details. The run-time behavior can be influenced using
- the 'LSAN_OPTIONS' environment variable.
+ the `LSAN_OPTIONS' environment variable.
-'-fsanitize=undefined'
+`-fsanitize=undefined'
Enable UndefinedBehaviorSanitizer, a fast undefined behavior
detector. Various computations are instrumented to detect
undefined behavior at runtime. Current suboptions are:
- '-fsanitize=shift'
+ `-fsanitize=shift'
This option enables checking that the result of a shift
operation is not undefined. Note that what exactly is
considered undefined differs slightly between C and C++, as
well as between ISO C90 and C99, etc.
- '-fsanitize=integer-divide-by-zero'
- Detect integer division by zero as well as 'INT_MIN / -1'
+ `-fsanitize=integer-divide-by-zero'
+ Detect integer division by zero as well as `INT_MIN / -1'
division.
- '-fsanitize=unreachable'
+ `-fsanitize=unreachable'
With this option, the compiler turns the
- '__builtin_unreachable' call into a diagnostics message call
- instead. When reaching the '__builtin_unreachable' call, the
+ `__builtin_unreachable' call into a diagnostics message call
+ instead. When reaching the `__builtin_unreachable' call, the
behavior is undefined.
- '-fsanitize=vla-bound'
- This option instructs the compiler to check that the size of a
- variable length array is positive.
+ `-fsanitize=vla-bound'
+ This option instructs the compiler to check that the size of
+ a variable length array is positive.
- '-fsanitize=null'
+ `-fsanitize=null'
This option enables pointer checking. Particularly, the
application built with this option turned on will issue an
error message when it tries to dereference a NULL pointer, or
@@ -5249,115 +5285,110 @@ program or GCC:
NULL pointer, or if a method is invoked on an object pointed
by a NULL pointer.
- '-fsanitize=return'
- This option enables return statement checking. Programs built
- with this option turned on will issue an error message when
- the end of a non-void function is reached without actually
- returning a value. This option works in C++ only.
+ `-fsanitize=return'
+ This option enables return statement checking. Programs
+ built with this option turned on will issue an error message
+ when the end of a non-void function is reached without
+ actually returning a value. This option works in C++ only.
- '-fsanitize=signed-integer-overflow'
+ `-fsanitize=signed-integer-overflow'
This option enables signed integer overflow checking. We
- check that the result of '+', '*', and both unary and binary
- '-' does not overflow in the signed arithmetics. Note,
+ check that the result of `+', `*', and both unary and binary
+ `-' does not overflow in the signed arithmetics. Note,
integer promotion rules must be taken into account. That is,
the following is not an overflow:
signed char a = SCHAR_MAX;
a++;
- '-fsanitize=bounds'
+ `-fsanitize=bounds'
This option enables instrumentation of array bounds. Various
out of bounds accesses are detected. Flexible array members,
flexible array member-like arrays, and initializers of
variables with static storage are not instrumented.
- '-fsanitize=alignment'
-
+ `-fsanitize=alignment'
This option enables checking of alignment of pointers when
they are dereferenced, or when a reference is bound to
- insufficiently aligned target, or when a method or constructor
- is invoked on insufficiently aligned object.
+ insufficiently aligned target, or when a method or
+ constructor is invoked on insufficiently aligned object.
- '-fsanitize=object-size'
- This option enables instrumentation of memory references using
- the '__builtin_object_size' function. Various out of bounds
- pointer accesses are detected.
+ `-fsanitize=object-size'
+ This option enables instrumentation of memory references
+ using the `__builtin_object_size' function. Various out of
+ bounds pointer accesses are detected.
- '-fsanitize=float-divide-by-zero'
+ `-fsanitize=float-divide-by-zero'
Detect floating-point division by zero. Unlike other similar
- options, '-fsanitize=float-divide-by-zero' is not enabled by
- '-fsanitize=undefined', since floating-point division by zero
+ options, `-fsanitize=float-divide-by-zero' is not enabled by
+ `-fsanitize=undefined', since floating-point division by zero
can be a legitimate way of obtaining infinities and NaNs.
- '-fsanitize=float-cast-overflow'
+ `-fsanitize=float-cast-overflow'
This option enables floating-point type to integer conversion
- checking. We check that the result of the conversion does not
- overflow. Unlike other similar options,
- '-fsanitize=float-cast-overflow' is not enabled by
- '-fsanitize=undefined'. This option does not work well with
- 'FE_INVALID' exceptions enabled.
-
- '-fsanitize=nonnull-attribute'
-
- This option enables instrumentation of calls, checking whether
- null values are not passed to arguments marked as requiring a
- non-null value by the 'nonnull' function attribute.
-
- '-fsanitize=returns-nonnull-attribute'
-
+ checking. We check that the result of the conversion does
+ not overflow. Unlike other similar options,
+ `-fsanitize=float-cast-overflow' is not enabled by
+ `-fsanitize=undefined'. This option does not work well with
+ `FE_INVALID' exceptions enabled.
+
+ `-fsanitize=nonnull-attribute'
+ This option enables instrumentation of calls, checking
+ whether null values are not passed to arguments marked as
+ requiring a non-null value by the `nonnull' function
+ attribute.
+
+ `-fsanitize=returns-nonnull-attribute'
This option enables instrumentation of return statements in
- functions marked with 'returns_nonnull' function attribute, to
- detect returning of null values from such functions.
-
- '-fsanitize=bool'
+ functions marked with `returns_nonnull' function attribute,
+ to detect returning of null values from such functions.
+ `-fsanitize=bool'
This option enables instrumentation of loads from bool. If a
value other than 0/1 is loaded, a run-time error is issued.
- '-fsanitize=enum'
-
+ `-fsanitize=enum'
This option enables instrumentation of loads from an enum
type. If a value outside the range of values for the enum
type is loaded, a run-time error is issued.
- '-fsanitize=vptr'
-
+ `-fsanitize=vptr'
This option enables instrumentation of C++ member function
calls, member accesses and some conversions between pointers
to base and derived classes, to verify the referenced object
has the correct dynamic type.
- While '-ftrapv' causes traps for signed overflows to be emitted,
- '-fsanitize=undefined' gives a diagnostic message. This currently
- works only for the C family of languages.
-'-fno-sanitize=all'
+ While `-ftrapv' causes traps for signed overflows to be emitted,
+ `-fsanitize=undefined' gives a diagnostic message. This currently
+ works only for the C family of languages.
+`-fno-sanitize=all'
This option disables all previously enabled sanitizers.
- '-fsanitize=all' is not allowed, as some sanitizers cannot be used
+ `-fsanitize=all' is not allowed, as some sanitizers cannot be used
together.
-'-fasan-shadow-offset=NUMBER'
+`-fasan-shadow-offset=NUMBER'
This option forces GCC to use custom shadow offset in
AddressSanitizer checks. It is useful for experimenting with
different shadow memory layouts in Kernel AddressSanitizer.
-'-fsanitize-recover[=OPTS]'
- '-fsanitize-recover=' controls error recovery mode for sanitizers
+`-fsanitize-recover[=OPTS]'
+ `-fsanitize-recover=' controls error recovery mode for sanitizers
mentioned in comma-separated list of OPTS. Enabling this option
for a sanitizer component causes it to attempt to continue running
the program as if no error happened. This means multiple runtime
errors can be reported in a single program run, and the exit code
of the program may indicate success even when errors have been
- reported. The '-fno-sanitize-recover=' option can be used to alter
+ reported. The `-fno-sanitize-recover=' option can be used to alter
this behavior: only the first detected error is reported and
program then exits with a non-zero exit code.
- Currently this feature only works for '-fsanitize=undefined' (and
- its suboptions except for '-fsanitize=unreachable' and
- '-fsanitize=return'), '-fsanitize=float-cast-overflow',
- '-fsanitize=float-divide-by-zero' and '-fsanitize=kernel-address'.
+ Currently this feature only works for `-fsanitize=undefined' (and
+ its suboptions except for `-fsanitize=unreachable' and
+ `-fsanitize=return'), `-fsanitize=float-cast-overflow',
+ `-fsanitize=float-divide-by-zero' and `-fsanitize=kernel-address'.
For these sanitizers error recovery is turned on by default.
- '-fsanitize-recover=all' and '-fno-sanitize-recover=all' is also
+ `-fsanitize-recover=all' and `-fno-sanitize-recover=all' is also
accepted, the former enables recovery for all sanitizers that
support it, the latter disables recovery for all sanitizers that
support it.
@@ -5365,28 +5396,28 @@ program or GCC:
Syntax without explicit OPTS parameter is deprecated. It is
equivalent to
-fsanitize-recover=undefined,float-cast-overflow,float-divide-by-zero
- Similarly '-fno-sanitize-recover' is equivalent to
+ Similarly `-fno-sanitize-recover' is equivalent to
-fno-sanitize-recover=undefined,float-cast-overflow,float-divide-by-zero
-'-fsanitize-undefined-trap-on-error'
- The '-fsanitize-undefined-trap-on-error' option instructs the
- compiler to report undefined behavior using '__builtin_trap' rather
- than a 'libubsan' library routine. The advantage of this is that
- the 'libubsan' library is not needed and is not linked in, so this
- is usable even in freestanding environments.
+`-fsanitize-undefined-trap-on-error'
+ The `-fsanitize-undefined-trap-on-error' option instructs the
+ compiler to report undefined behavior using `__builtin_trap'
+ rather than a `libubsan' library routine. The advantage of this
+ is that the `libubsan' library is not needed and is not linked in,
+ so this is usable even in freestanding environments.
-'-fcheck-pointer-bounds'
+`-fcheck-pointer-bounds'
Enable Pointer Bounds Checker instrumentation. Each memory
reference is instrumented with checks of the pointer used for
memory access against bounds associated with that pointer.
Currently there is only an implementation for Intel MPX available,
- thus x86 target and '-mmpx' are required to enable this feature.
+ thus x86 target and `-mmpx' are required to enable this feature.
MPX-based instrumentation requires a runtime library to enable MPX
in hardware and handle bounds violation signals. By default when
- '-fcheck-pointer-bounds' and '-mmpx' options are used to link a
- program, the GCC driver links against the 'libmpx' runtime library
- and 'libmpxwrappers' library. It also passes '-z bndplt' to a
+ `-fcheck-pointer-bounds' and `-mmpx' options are used to link a
+ program, the GCC driver links against the `libmpx' runtime library
+ and `libmpxwrappers' library. It also passes '-z bndplt' to a
linker in case it supports this option (which is checked on libmpx
configuration). Note that old versions of linker may ignore
option. Gold linker doesn't support '-z bndplt' option. With no
@@ -5394,169 +5425,169 @@ program or GCC:
passed bounds reducing overall protection level. It's highly
recommended to use linker with '-z bndplt' support. In case such
linker is not available it is adviced to always use
- '-static-libmpxwrappers' for better protection level or use
- '-static' to completely avoid external calls to dynamic libraries.
- MPX-based instrumentation may be used for debugging and also may be
- included in production code to increase program security.
+ `-static-libmpxwrappers' for better protection level or use
+ `-static' to completely avoid external calls to dynamic libraries.
+ MPX-based instrumentation may be used for debugging and also may
+ be included in production code to increase program security.
Depending on usage, you may have different requirements for the
- runtime library. The current version of the MPX runtime library is
- more oriented for use as a debugging tool. MPX runtime library
- usage implies '-lpthread'. See also '-static-libmpx'. The runtime
- library behavior can be influenced using various 'CHKP_RT_*'
- environment variables. See
- <https://gcc.gnu.org/wiki/Intel%20MPX%20support%20in%20the%20GCC%20compiler>
+ runtime library. The current version of the MPX runtime library
+ is more oriented for use as a debugging tool. MPX runtime library
+ usage implies `-lpthread'. See also `-static-libmpx'. The
+ runtime library behavior can be influenced using various
+ `CHKP_RT_*' environment variables. See
+ `https://gcc.gnu.org/wiki/Intel%20MPX%20support%20in%20the%20GCC%20compiler'
for more details.
- Generated instrumentation may be controlled by various '-fchkp-*'
- options and by the 'bnd_variable_size' structure field attribute
- (*note Type Attributes::) and 'bnd_legacy', and 'bnd_instrument'
+ Generated instrumentation may be controlled by various `-fchkp-*'
+ options and by the `bnd_variable_size' structure field attribute
+ (*note Type Attributes::) and `bnd_legacy', and `bnd_instrument'
function attributes (*note Function Attributes::). GCC also
- provides a number of built-in functions for controlling the Pointer
- Bounds Checker. *Note Pointer Bounds Checker builtins::, for more
- information.
+ provides a number of built-in functions for controlling the
+ Pointer Bounds Checker. *Note Pointer Bounds Checker builtins::,
+ for more information.
-'-fchkp-check-incomplete-type'
+`-fchkp-check-incomplete-type'
Generate pointer bounds checks for variables with incomplete type.
Enabled by default.
-'-fchkp-narrow-bounds'
+`-fchkp-narrow-bounds'
Controls bounds used by Pointer Bounds Checker for pointers to
- object fields. If narrowing is enabled then field bounds are used.
- Otherwise object bounds are used. See also
- '-fchkp-narrow-to-innermost-array' and
- '-fchkp-first-field-has-own-bounds'. Enabled by default.
+ object fields. If narrowing is enabled then field bounds are
+ used. Otherwise object bounds are used. See also
+ `-fchkp-narrow-to-innermost-array' and
+ `-fchkp-first-field-has-own-bounds'. Enabled by default.
-'-fchkp-first-field-has-own-bounds'
+`-fchkp-first-field-has-own-bounds'
Forces Pointer Bounds Checker to use narrowed bounds for the
address of the first field in the structure. By default a pointer
to the first field has the same bounds as a pointer to the whole
structure.
-'-fchkp-narrow-to-innermost-array'
- Forces Pointer Bounds Checker to use bounds of the innermost arrays
- in case of nested static array access. By default this option is
- disabled and bounds of the outermost array are used.
+`-fchkp-narrow-to-innermost-array'
+ Forces Pointer Bounds Checker to use bounds of the innermost
+ arrays in case of nested static array access. By default this
+ option is disabled and bounds of the outermost array are used.
-'-fchkp-optimize'
+`-fchkp-optimize'
Enables Pointer Bounds Checker optimizations. Enabled by default
- at optimization levels '-O', '-O2', '-O3'.
+ at optimization levels `-O', `-O2', `-O3'.
-'-fchkp-use-fast-string-functions'
- Enables use of '*_nobnd' versions of string functions (not copying
+`-fchkp-use-fast-string-functions'
+ Enables use of `*_nobnd' versions of string functions (not copying
bounds) by Pointer Bounds Checker. Disabled by default.
-'-fchkp-use-nochk-string-functions'
- Enables use of '*_nochk' versions of string functions (not checking
- bounds) by Pointer Bounds Checker. Disabled by default.
+`-fchkp-use-nochk-string-functions'
+ Enables use of `*_nochk' versions of string functions (not
+ checking bounds) by Pointer Bounds Checker. Disabled by default.
-'-fchkp-use-static-bounds'
+`-fchkp-use-static-bounds'
Allow Pointer Bounds Checker to generate static bounds holding
bounds of static variables. Enabled by default.
-'-fchkp-use-static-const-bounds'
+`-fchkp-use-static-const-bounds'
Use statically-initialized bounds for constant bounds instead of
generating them each time they are required. By default enabled
- when '-fchkp-use-static-bounds' is enabled.
+ when `-fchkp-use-static-bounds' is enabled.
-'-fchkp-treat-zero-dynamic-size-as-infinite'
+`-fchkp-treat-zero-dynamic-size-as-infinite'
With this option, objects with incomplete type whose
dynamically-obtained size is zero are treated as having infinite
- size instead by Pointer Bounds Checker. This option may be helpful
- if a program is linked with a library missing size information for
- some symbols. Disabled by default.
+ size instead by Pointer Bounds Checker. This option may be
+ helpful if a program is linked with a library missing size
+ information for some symbols. Disabled by default.
-'-fchkp-check-read'
+`-fchkp-check-read'
Instructs Pointer Bounds Checker to generate checks for all read
accesses to memory. Enabled by default.
-'-fchkp-check-write'
+`-fchkp-check-write'
Instructs Pointer Bounds Checker to generate checks for all write
accesses to memory. Enabled by default.
-'-fchkp-store-bounds'
+`-fchkp-store-bounds'
Instructs Pointer Bounds Checker to generate bounds stores for
pointer writes. Enabled by default.
-'-fchkp-instrument-calls'
+`-fchkp-instrument-calls'
Instructs Pointer Bounds Checker to pass pointer bounds to calls.
Enabled by default.
-'-fchkp-instrument-marked-only'
+`-fchkp-instrument-marked-only'
Instructs Pointer Bounds Checker to instrument only functions
- marked with the 'bnd_instrument' attribute (*note Function
+ marked with the `bnd_instrument' attribute (*note Function
Attributes::). Disabled by default.
-'-fchkp-use-wrappers'
+`-fchkp-use-wrappers'
Allows Pointer Bounds Checker to replace calls to built-in
functions with calls to wrapper functions. When
- '-fchkp-use-wrappers' is used to link a program, the GCC driver
- automatically links against 'libmpxwrappers'. See also
- '-static-libmpxwrappers'. Enabled by default.
+ `-fchkp-use-wrappers' is used to link a program, the GCC driver
+ automatically links against `libmpxwrappers'. See also
+ `-static-libmpxwrappers'. Enabled by default.
-'-fdump-final-insns[=FILE]'
+`-fdump-final-insns[=FILE]'
Dump the final internal representation (RTL) to FILE. If the
- optional argument is omitted (or if FILE is '.'), the name of the
- dump file is determined by appending '.gkd' to the compilation
+ optional argument is omitted (or if FILE is `.'), the name of the
+ dump file is determined by appending `.gkd' to the compilation
output file name.
-'-fcompare-debug[=OPTS]'
+`-fcompare-debug[=OPTS]'
If no error occurs during compilation, run the compiler a second
- time, adding OPTS and '-fcompare-debug-second' to the arguments
+ time, adding OPTS and `-fcompare-debug-second' to the arguments
passed to the second compilation. Dump the final internal
representation in both compilations, and print an error if they
differ.
- If the equal sign is omitted, the default '-gtoggle' is used.
+ If the equal sign is omitted, the default `-gtoggle' is used.
- The environment variable 'GCC_COMPARE_DEBUG', if defined, non-empty
- and nonzero, implicitly enables '-fcompare-debug'. If
- 'GCC_COMPARE_DEBUG' is defined to a string starting with a dash,
- then it is used for OPTS, otherwise the default '-gtoggle' is used.
+ The environment variable `GCC_COMPARE_DEBUG', if defined, non-empty
+ and nonzero, implicitly enables `-fcompare-debug'. If
+ `GCC_COMPARE_DEBUG' is defined to a string starting with a dash,
+ then it is used for OPTS, otherwise the default `-gtoggle' is used.
- '-fcompare-debug=', with the equal sign but without OPTS, is
- equivalent to '-fno-compare-debug', which disables the dumping of
+ `-fcompare-debug=', with the equal sign but without OPTS, is
+ equivalent to `-fno-compare-debug', which disables the dumping of
the final representation and the second compilation, preventing
- even 'GCC_COMPARE_DEBUG' from taking effect.
+ even `GCC_COMPARE_DEBUG' from taking effect.
- To verify full coverage during '-fcompare-debug' testing, set
- 'GCC_COMPARE_DEBUG' to say '-fcompare-debug-not-overridden', which
+ To verify full coverage during `-fcompare-debug' testing, set
+ `GCC_COMPARE_DEBUG' to say `-fcompare-debug-not-overridden', which
GCC rejects as an invalid option in any actual compilation (rather
than preprocessing, assembly or linking). To get just a warning,
- setting 'GCC_COMPARE_DEBUG' to '-w%n-fcompare-debug not overridden'
- will do.
+ setting `GCC_COMPARE_DEBUG' to `-w%n-fcompare-debug not
+ overridden' will do.
-'-fcompare-debug-second'
+`-fcompare-debug-second'
This option is implicitly passed to the compiler for the second
- compilation requested by '-fcompare-debug', along with options to
+ compilation requested by `-fcompare-debug', along with options to
silence warnings, and omitting other options that would cause
side-effect compiler outputs to files or to the standard output.
Dump files and preserved temporary files are renamed so as to
- contain the '.gk' additional extension during the second
+ contain the `.gk' additional extension during the second
compilation, to avoid overwriting those generated by the first.
When this option is passed to the compiler driver, it causes the
_first_ compilation to be skipped, which makes it useful for little
other than debugging the compiler proper.
-'-feliminate-dwarf2-dups'
+`-feliminate-dwarf2-dups'
Compress DWARF 2 debugging information by eliminating duplicated
information about each symbol. This option only makes sense when
- generating DWARF 2 debugging information with '-gdwarf-2'.
+ generating DWARF 2 debugging information with `-gdwarf-2'.
-'-femit-struct-debug-baseonly'
+`-femit-struct-debug-baseonly'
Emit debug information for struct-like types only when the base
name of the compilation source file matches the base name of file
in which the struct is defined.
This option substantially reduces the size of debugging
information, but at significant potential loss in type information
- to the debugger. See '-femit-struct-debug-reduced' for a less
- aggressive option. See '-femit-struct-debug-detailed' for more
+ to the debugger. See `-femit-struct-debug-reduced' for a less
+ aggressive option. See `-femit-struct-debug-detailed' for more
detailed control.
This option works only with DWARF 2.
-'-femit-struct-debug-reduced'
+`-femit-struct-debug-reduced'
Emit debug information for struct-like types only when the base
name of the compilation source file matches the base name of file
in which the type is defined, unless the struct is a template or
@@ -5564,261 +5595,265 @@ program or GCC:
This option significantly reduces the size of debugging
information, with some potential loss in type information to the
- debugger. See '-femit-struct-debug-baseonly' for a more aggressive
- option. See '-femit-struct-debug-detailed' for more detailed
- control.
+ debugger. See `-femit-struct-debug-baseonly' for a more
+ aggressive option. See `-femit-struct-debug-detailed' for more
+ detailed control.
This option works only with DWARF 2.
-'-femit-struct-debug-detailed[=SPEC-LIST]'
+`-femit-struct-debug-detailed[=SPEC-LIST]'
Specify the struct-like types for which the compiler generates
debug information. The intent is to reduce duplicate struct debug
information between different object files within the same program.
- This option is a detailed version of '-femit-struct-debug-reduced'
- and '-femit-struct-debug-baseonly', which serves for most needs.
+ This option is a detailed version of `-femit-struct-debug-reduced'
+ and `-femit-struct-debug-baseonly', which serves for most needs.
A specification has the syntax
- ['dir:'|'ind:']['ord:'|'gen:']('any'|'sys'|'base'|'none')
+ [`dir:'|`ind:'][`ord:'|`gen:'](`any'|`sys'|`base'|`none')
The optional first word limits the specification to structs that
- are used directly ('dir:') or used indirectly ('ind:'). A struct
+ are used directly (`dir:') or used indirectly (`ind:'). A struct
type is used directly when it is the type of a variable, member.
- Indirect uses arise through pointers to structs. That is, when use
- of an incomplete struct is valid, the use is indirect. An example
- is 'struct one direct; struct two * indirect;'.
+ Indirect uses arise through pointers to structs. That is, when
+ use of an incomplete struct is valid, the use is indirect. An
+ example is `struct one direct; struct two * indirect;'.
The optional second word limits the specification to ordinary
- structs ('ord:') or generic structs ('gen:'). Generic structs are
+ structs (`ord:') or generic structs (`gen:'). Generic structs are
a bit complicated to explain. For C++, these are non-explicit
- specializations of template classes, or non-template classes within
- the above. Other programming languages have generics, but
- '-femit-struct-debug-detailed' does not yet implement them.
+ specializations of template classes, or non-template classes
+ within the above. Other programming languages have generics, but
+ `-femit-struct-debug-detailed' does not yet implement them.
The third word specifies the source files for those structs for
which the compiler should emit debug information. The values
- 'none' and 'any' have the normal meaning. The value 'base' means
+ `none' and `any' have the normal meaning. The value `base' means
that the base of name of the file in which the type declaration
appears must match the base of the name of the main compilation
- file. In practice, this means that when compiling 'foo.c', debug
+ file. In practice, this means that when compiling `foo.c', debug
information is generated for types declared in that file and
- 'foo.h', but not other header files. The value 'sys' means those
- types satisfying 'base' or declared in system or compiler headers.
+ `foo.h', but not other header files. The value `sys' means those
+ types satisfying `base' or declared in system or compiler headers.
You may need to experiment to determine the best settings for your
application.
- The default is '-femit-struct-debug-detailed=all'.
+ The default is `-femit-struct-debug-detailed=all'.
This option works only with DWARF 2.
-'-fno-merge-debug-strings'
+`-fno-merge-debug-strings'
Direct the linker to not merge together strings in the debugging
information that are identical in different object files. Merging
is not supported by all assemblers or linkers. Merging decreases
- the size of the debug information in the output file at the cost of
- increasing link processing time. Merging is enabled by default.
+ the size of the debug information in the output file at the cost
+ of increasing link processing time. Merging is enabled by default.
-'-fdebug-prefix-map=OLD=NEW'
- When compiling files in directory 'OLD', record debugging
- information describing them as in 'NEW' instead.
+`-fdebug-prefix-map=OLD=NEW'
+ When compiling files in directory `OLD', record debugging
+ information describing them as in `NEW' instead.
-'-fno-dwarf2-cfi-asm'
- Emit DWARF 2 unwind info as compiler generated '.eh_frame' section
- instead of using GAS '.cfi_*' directives.
+`-fno-dwarf2-cfi-asm'
+ Emit DWARF 2 unwind info as compiler generated `.eh_frame' section
+ instead of using GAS `.cfi_*' directives.
-'-p'
+`-p'
Generate extra code to write profile information suitable for the
- analysis program 'prof'. You must use this option when compiling
+ analysis program `prof'. You must use this option when compiling
the source files you want data about, and you must also use it when
linking.
-'-pg'
+`-pg'
Generate extra code to write profile information suitable for the
- analysis program 'gprof'. You must use this option when compiling
+ analysis program `gprof'. You must use this option when compiling
the source files you want data about, and you must also use it when
linking.
-'-Q'
+`-Q'
Makes the compiler print out each function name as it is compiled,
and print some statistics about each pass when it finishes.
-'-ftime-report'
- Makes the compiler print some statistics about the time consumed by
- each pass when it finishes.
+`-ftime-report'
+ Makes the compiler print some statistics about the time consumed
+ by each pass when it finishes.
-'-fmem-report'
+`-fmem-report'
Makes the compiler print some statistics about permanent memory
allocation when it finishes.
-'-fmem-report-wpa'
+`-fmem-report-wpa'
Makes the compiler print some statistics about permanent memory
allocation for the WPA phase only.
-'-fpre-ipa-mem-report'
-'-fpost-ipa-mem-report'
+`-fpre-ipa-mem-report'
+
+`-fpost-ipa-mem-report'
Makes the compiler print some statistics about permanent memory
allocation before or after interprocedural optimization.
-'-fprofile-report'
+`-fprofile-report'
Makes the compiler print some statistics about consistency of the
(estimated) profile and effect of individual passes.
-'-fstack-usage'
+`-fstack-usage'
Makes the compiler output stack usage information for the program,
on a per-function basis. The filename for the dump is made by
- appending '.su' to the AUXNAME. AUXNAME is generated from the name
- of the output file, if explicitly specified and it is not an
+ appending `.su' to the AUXNAME. AUXNAME is generated from the
+ name of the output file, if explicitly specified and it is not an
executable, otherwise it is the basename of the source file. An
entry is made up of three fields:
* The name of the function.
+
* A number of bytes.
- * One or more qualifiers: 'static', 'dynamic', 'bounded'.
- The qualifier 'static' means that the function manipulates the
+ * One or more qualifiers: `static', `dynamic', `bounded'.
+
+ The qualifier `static' means that the function manipulates the
stack statically: a fixed number of bytes are allocated for the
frame on function entry and released on function exit; no stack
adjustments are otherwise made in the function. The second field
is this fixed number of bytes.
- The qualifier 'dynamic' means that the function manipulates the
+ The qualifier `dynamic' means that the function manipulates the
stack dynamically: in addition to the static allocation described
above, stack adjustments are made in the body of the function, for
example to push/pop arguments around function calls. If the
- qualifier 'bounded' is also present, the amount of these
+ qualifier `bounded' is also present, the amount of these
adjustments is bounded at compile time and the second field is an
upper bound of the total amount of stack used by the function. If
it is not present, the amount of these adjustments is not bounded
at compile time and the second field only represents the bounded
part.
-'-fprofile-arcs'
+`-fprofile-arcs'
Add code so that program flow "arcs" are instrumented. During
execution the program records how many times each branch and call
is executed and how many times it is taken or returns. When the
compiled program exits it saves this data to a file called
- 'AUXNAME.gcda' for each source file. The data may be used for
- profile-directed optimizations ('-fbranch-probabilities'), or for
- test coverage analysis ('-ftest-coverage'). Each object file's
+ `AUXNAME.gcda' for each source file. The data may be used for
+ profile-directed optimizations (`-fbranch-probabilities'), or for
+ test coverage analysis (`-ftest-coverage'). Each object file's
AUXNAME is generated from the name of the output file, if
explicitly specified and it is not the final executable, otherwise
- it is the basename of the source file. In both cases any suffix is
- removed (e.g. 'foo.gcda' for input file 'dir/foo.c', or
- 'dir/foo.gcda' for output file specified as '-o dir/foo.o'). *Note
- Cross-profiling::.
-
-'--coverage'
+ it is the basename of the source file. In both cases any suffix
+ is removed (e.g. `foo.gcda' for input file `dir/foo.c', or
+ `dir/foo.gcda' for output file specified as `-o dir/foo.o').
+ *Note Cross-profiling::.
+`--coverage'
This option is used to compile and link code instrumented for
- coverage analysis. The option is a synonym for '-fprofile-arcs'
- '-ftest-coverage' (when compiling) and '-lgcov' (when linking).
+ coverage analysis. The option is a synonym for `-fprofile-arcs'
+ `-ftest-coverage' (when compiling) and `-lgcov' (when linking).
See the documentation for those options for more details.
- * Compile the source files with '-fprofile-arcs' plus
+ * Compile the source files with `-fprofile-arcs' plus
optimization and code generation options. For test coverage
- analysis, use the additional '-ftest-coverage' option. You do
- not need to profile every source file in a program.
+ analysis, use the additional `-ftest-coverage' option. You
+ do not need to profile every source file in a program.
- * Link your object files with '-lgcov' or '-fprofile-arcs' (the
+ * Link your object files with `-lgcov' or `-fprofile-arcs' (the
latter implies the former).
* Run the program on a representative workload to generate the
arc profile information. This may be repeated any number of
times. You can run concurrent instances of your program, and
- provided that the file system supports locking, the data files
- will be correctly updated. Also 'fork' calls are detected and
- correctly handled (double counting will not happen).
+ provided that the file system supports locking, the data
+ files will be correctly updated. Also `fork' calls are
+ detected and correctly handled (double counting will not
+ happen).
* For profile-directed optimizations, compile the source files
again with the same optimization and code generation options
- plus '-fbranch-probabilities' (*note Options that Control
+ plus `-fbranch-probabilities' (*note Options that Control
Optimization: Optimize Options.).
- * For test coverage analysis, use 'gcov' to produce human
- readable information from the '.gcno' and '.gcda' files.
- Refer to the 'gcov' documentation for further information.
+ * For test coverage analysis, use `gcov' to produce human
+ readable information from the `.gcno' and `.gcda' files.
+ Refer to the `gcov' documentation for further information.
- With '-fprofile-arcs', for each function of your program GCC
+
+ With `-fprofile-arcs', for each function of your program GCC
creates a program flow graph, then finds a spanning tree for the
graph. Only arcs that are not on the spanning tree have to be
instrumented: the compiler adds code to count the number of times
- that these arcs are executed. When an arc is the only exit or only
- entrance to a block, the instrumentation code can be added to the
- block; otherwise, a new basic block must be created to hold the
- instrumentation code.
-
-'-ftest-coverage'
- Produce a notes file that the 'gcov' code-coverage utility (*note
- 'gcov'--a Test Coverage Program: Gcov.) can use to show program
- coverage. Each source file's note file is called 'AUXNAME.gcno'.
- Refer to the '-fprofile-arcs' option above for a description of
+ that these arcs are executed. When an arc is the only exit or
+ only entrance to a block, the instrumentation code can be added to
+ the block; otherwise, a new basic block must be created to hold
+ the instrumentation code.
+
+`-ftest-coverage'
+ Produce a notes file that the `gcov' code-coverage utility (*note
+ `gcov'--a Test Coverage Program: Gcov.) can use to show program
+ coverage. Each source file's note file is called `AUXNAME.gcno'.
+ Refer to the `-fprofile-arcs' option above for a description of
AUXNAME and instructions on how to generate test coverage data.
Coverage data matches the source files more closely if you do not
optimize.
-'-fdbg-cnt-list'
+`-fdbg-cnt-list'
Print the name and the counter upper bound for all debug counters.
-'-fdbg-cnt=COUNTER-VALUE-LIST'
+`-fdbg-cnt=COUNTER-VALUE-LIST'
Set the internal debug counter upper bound. COUNTER-VALUE-LIST is
a comma-separated list of NAME:VALUE pairs which sets the upper
- bound of each debug counter NAME to VALUE. All debug counters have
- the initial upper bound of 'UINT_MAX'; thus 'dbg_cnt' returns true
- always unless the upper bound is set by this option. For example,
- with '-fdbg-cnt=dce:10,tail_call:0', 'dbg_cnt(dce)' returns true
- only for first 10 invocations.
-
-'-fenable-KIND-PASS'
-'-fdisable-KIND-PASS=RANGE-LIST'
-
+ bound of each debug counter NAME to VALUE. All debug counters
+ have the initial upper bound of `UINT_MAX'; thus `dbg_cnt' returns
+ true always unless the upper bound is set by this option. For
+ example, with `-fdbg-cnt=dce:10,tail_call:0', `dbg_cnt(dce)'
+ returns true only for first 10 invocations.
+
+`-fenable-KIND-PASS'
+`-fdisable-KIND-PASS=RANGE-LIST'
This is a set of options that are used to explicitly disable/enable
optimization passes. These options are intended for use for
- debugging GCC. Compiler users should use regular options for
+ debugging GCC. Compiler users should use regular options for
enabling/disabling passes instead.
- '-fdisable-ipa-PASS'
- Disable IPA pass PASS. PASS is the pass name. If the same
- pass is statically invoked in the compiler multiple times, the
- pass name should be appended with a sequential number starting
- from 1.
+ `-fdisable-ipa-PASS'
+ Disable IPA pass PASS. PASS is the pass name. If the same
+ pass is statically invoked in the compiler multiple times,
+ the pass name should be appended with a sequential number
+ starting from 1.
- '-fdisable-rtl-PASS'
- '-fdisable-rtl-PASS=RANGE-LIST'
+ `-fdisable-rtl-PASS'
+ `-fdisable-rtl-PASS=RANGE-LIST'
Disable RTL pass PASS. PASS is the pass name. If the same
- pass is statically invoked in the compiler multiple times, the
- pass name should be appended with a sequential number starting
- from 1. RANGE-LIST is a comma-separated list of function
- ranges or assembler names. Each range is a number pair
- separated by a colon. The range is inclusive in both ends.
- If the range is trivial, the number pair can be simplified as
- a single number. If the function's call graph node's UID
- falls within one of the specified ranges, the PASS is disabled
- for that function. The UID is shown in the function header of
- a dump file, and the pass names can be dumped by using option
- '-fdump-passes'.
-
- '-fdisable-tree-PASS'
- '-fdisable-tree-PASS=RANGE-LIST'
- Disable tree pass PASS. See '-fdisable-rtl' for the
+ pass is statically invoked in the compiler multiple times,
+ the pass name should be appended with a sequential number
+ starting from 1. RANGE-LIST is a comma-separated list of
+ function ranges or assembler names. Each range is a number
+ pair separated by a colon. The range is inclusive in both
+ ends. If the range is trivial, the number pair can be
+ simplified as a single number. If the function's call graph
+ node's UID falls within one of the specified ranges, the PASS
+ is disabled for that function. The UID is shown in the
+ function header of a dump file, and the pass names can be
+ dumped by using option `-fdump-passes'.
+
+ `-fdisable-tree-PASS'
+ `-fdisable-tree-PASS=RANGE-LIST'
+ Disable tree pass PASS. See `-fdisable-rtl' for the
description of option arguments.
- '-fenable-ipa-PASS'
+ `-fenable-ipa-PASS'
Enable IPA pass PASS. PASS is the pass name. If the same
- pass is statically invoked in the compiler multiple times, the
- pass name should be appended with a sequential number starting
- from 1.
+ pass is statically invoked in the compiler multiple times,
+ the pass name should be appended with a sequential number
+ starting from 1.
- '-fenable-rtl-PASS'
- '-fenable-rtl-PASS=RANGE-LIST'
- Enable RTL pass PASS. See '-fdisable-rtl' for option argument
+ `-fenable-rtl-PASS'
+ `-fenable-rtl-PASS=RANGE-LIST'
+ Enable RTL pass PASS. See `-fdisable-rtl' for option argument
description and examples.
- '-fenable-tree-PASS'
- '-fenable-tree-PASS=RANGE-LIST'
- Enable tree pass PASS. See '-fdisable-rtl' for the
+ `-fenable-tree-PASS'
+ `-fenable-tree-PASS=RANGE-LIST'
+ Enable tree pass PASS. See `-fdisable-rtl' for the
description of option arguments.
+
Here are some examples showing uses of these options.
@@ -5837,333 +5872,335 @@ program or GCC:
# enable tree full unroll
-fenable-tree-unroll
-
-'-dLETTERS'
-'-fdump-rtl-PASS'
-'-fdump-rtl-PASS=FILENAME'
+`-dLETTERS'
+`-fdump-rtl-PASS'
+`-fdump-rtl-PASS=FILENAME'
Says to make debugging dumps during compilation at times specified
by LETTERS. This is used for debugging the RTL-based passes of the
compiler. The file names for most of the dumps are made by
appending a pass number and a word to the DUMPNAME, and the files
- are created in the directory of the output file. In case of
- '=FILENAME' option, the dump is output on the given file instead of
- the pass numbered dump files. Note that the pass number is
+ are created in the directory of the output file. In case of
+ `=FILENAME' option, the dump is output on the given file instead
+ of the pass numbered dump files. Note that the pass number is
computed statically as passes get registered into the pass manager.
- Thus the numbering is not related to the dynamic order of execution
- of passes. In particular, a pass installed by a plugin could have
- a number over 200 even if it executed quite early. DUMPNAME is
- generated from the name of the output file, if explicitly specified
- and it is not an executable, otherwise it is the basename of the
- source file. These switches may have different effects when '-E'
- is used for preprocessing.
-
- Debug dumps can be enabled with a '-fdump-rtl' switch or some '-d'
+ Thus the numbering is not related to the dynamic order of
+ execution of passes. In particular, a pass installed by a plugin
+ could have a number over 200 even if it executed quite early.
+ DUMPNAME is generated from the name of the output file, if
+ explicitly specified and it is not an executable, otherwise it is
+ the basename of the source file. These switches may have different
+ effects when `-E' is used for preprocessing.
+
+ Debug dumps can be enabled with a `-fdump-rtl' switch or some `-d'
option LETTERS. Here are the possible letters for use in PASS and
LETTERS, and their meanings:
- '-fdump-rtl-alignments'
+ `-fdump-rtl-alignments'
Dump after branch alignments have been computed.
- '-fdump-rtl-asmcons'
+ `-fdump-rtl-asmcons'
Dump after fixing rtl statements that have unsatisfied in/out
constraints.
- '-fdump-rtl-auto_inc_dec'
+ `-fdump-rtl-auto_inc_dec'
Dump after auto-inc-dec discovery. This pass is only run on
architectures that have auto inc or auto dec instructions.
- '-fdump-rtl-barriers'
+ `-fdump-rtl-barriers'
Dump after cleaning up the barrier instructions.
- '-fdump-rtl-bbpart'
+ `-fdump-rtl-bbpart'
Dump after partitioning hot and cold basic blocks.
- '-fdump-rtl-bbro'
+ `-fdump-rtl-bbro'
Dump after block reordering.
- '-fdump-rtl-btl1'
- '-fdump-rtl-btl2'
- '-fdump-rtl-btl1' and '-fdump-rtl-btl2' enable dumping after
+ `-fdump-rtl-btl1'
+ `-fdump-rtl-btl2'
+ `-fdump-rtl-btl1' and `-fdump-rtl-btl2' enable dumping after
the two branch target load optimization passes.
- '-fdump-rtl-bypass'
+ `-fdump-rtl-bypass'
Dump after jump bypassing and control flow optimizations.
- '-fdump-rtl-combine'
+ `-fdump-rtl-combine'
Dump after the RTL instruction combination pass.
- '-fdump-rtl-compgotos'
+ `-fdump-rtl-compgotos'
Dump after duplicating the computed gotos.
- '-fdump-rtl-ce1'
- '-fdump-rtl-ce2'
- '-fdump-rtl-ce3'
- '-fdump-rtl-ce1', '-fdump-rtl-ce2', and '-fdump-rtl-ce3'
+ `-fdump-rtl-ce1'
+ `-fdump-rtl-ce2'
+ `-fdump-rtl-ce3'
+ `-fdump-rtl-ce1', `-fdump-rtl-ce2', and `-fdump-rtl-ce3'
enable dumping after the three if conversion passes.
- '-fdump-rtl-cprop_hardreg'
+ `-fdump-rtl-cprop_hardreg'
Dump after hard register copy propagation.
- '-fdump-rtl-csa'
+ `-fdump-rtl-csa'
Dump after combining stack adjustments.
- '-fdump-rtl-cse1'
- '-fdump-rtl-cse2'
- '-fdump-rtl-cse1' and '-fdump-rtl-cse2' enable dumping after
+ `-fdump-rtl-cse1'
+ `-fdump-rtl-cse2'
+ `-fdump-rtl-cse1' and `-fdump-rtl-cse2' enable dumping after
the two common subexpression elimination passes.
- '-fdump-rtl-dce'
+ `-fdump-rtl-dce'
Dump after the standalone dead code elimination passes.
- '-fdump-rtl-dbr'
+ `-fdump-rtl-dbr'
Dump after delayed branch scheduling.
- '-fdump-rtl-dce1'
- '-fdump-rtl-dce2'
- '-fdump-rtl-dce1' and '-fdump-rtl-dce2' enable dumping after
+ `-fdump-rtl-dce1'
+ `-fdump-rtl-dce2'
+ `-fdump-rtl-dce1' and `-fdump-rtl-dce2' enable dumping after
the two dead store elimination passes.
- '-fdump-rtl-eh'
+ `-fdump-rtl-eh'
Dump after finalization of EH handling code.
- '-fdump-rtl-eh_ranges'
+ `-fdump-rtl-eh_ranges'
Dump after conversion of EH handling range regions.
- '-fdump-rtl-expand'
+ `-fdump-rtl-expand'
Dump after RTL generation.
- '-fdump-rtl-fwprop1'
- '-fdump-rtl-fwprop2'
- '-fdump-rtl-fwprop1' and '-fdump-rtl-fwprop2' enable dumping
+ `-fdump-rtl-fwprop1'
+ `-fdump-rtl-fwprop2'
+ `-fdump-rtl-fwprop1' and `-fdump-rtl-fwprop2' enable dumping
after the two forward propagation passes.
- '-fdump-rtl-gcse1'
- '-fdump-rtl-gcse2'
- '-fdump-rtl-gcse1' and '-fdump-rtl-gcse2' enable dumping after
- global common subexpression elimination.
+ `-fdump-rtl-gcse1'
+ `-fdump-rtl-gcse2'
+ `-fdump-rtl-gcse1' and `-fdump-rtl-gcse2' enable dumping
+ after global common subexpression elimination.
- '-fdump-rtl-init-regs'
+ `-fdump-rtl-init-regs'
Dump after the initialization of the registers.
- '-fdump-rtl-initvals'
+ `-fdump-rtl-initvals'
Dump after the computation of the initial value sets.
- '-fdump-rtl-into_cfglayout'
+ `-fdump-rtl-into_cfglayout'
Dump after converting to cfglayout mode.
- '-fdump-rtl-ira'
+ `-fdump-rtl-ira'
Dump after iterated register allocation.
- '-fdump-rtl-jump'
+ `-fdump-rtl-jump'
Dump after the second jump optimization.
- '-fdump-rtl-loop2'
- '-fdump-rtl-loop2' enables dumping after the rtl loop
+ `-fdump-rtl-loop2'
+ `-fdump-rtl-loop2' enables dumping after the rtl loop
optimization passes.
- '-fdump-rtl-mach'
+ `-fdump-rtl-mach'
Dump after performing the machine dependent reorganization
pass, if that pass exists.
- '-fdump-rtl-mode_sw'
+ `-fdump-rtl-mode_sw'
Dump after removing redundant mode switches.
- '-fdump-rtl-rnreg'
+ `-fdump-rtl-rnreg'
Dump after register renumbering.
- '-fdump-rtl-outof_cfglayout'
+ `-fdump-rtl-outof_cfglayout'
Dump after converting from cfglayout mode.
- '-fdump-rtl-peephole2'
+ `-fdump-rtl-peephole2'
Dump after the peephole pass.
- '-fdump-rtl-postreload'
+ `-fdump-rtl-postreload'
Dump after post-reload optimizations.
- '-fdump-rtl-pro_and_epilogue'
+ `-fdump-rtl-pro_and_epilogue'
Dump after generating the function prologues and epilogues.
- '-fdump-rtl-sched1'
- '-fdump-rtl-sched2'
- '-fdump-rtl-sched1' and '-fdump-rtl-sched2' enable dumping
+ `-fdump-rtl-sched1'
+ `-fdump-rtl-sched2'
+ `-fdump-rtl-sched1' and `-fdump-rtl-sched2' enable dumping
after the basic block scheduling passes.
- '-fdump-rtl-ree'
+ `-fdump-rtl-ree'
Dump after sign/zero extension elimination.
- '-fdump-rtl-seqabstr'
+ `-fdump-rtl-seqabstr'
Dump after common sequence discovery.
- '-fdump-rtl-shorten'
+ `-fdump-rtl-shorten'
Dump after shortening branches.
- '-fdump-rtl-sibling'
+ `-fdump-rtl-sibling'
Dump after sibling call optimizations.
- '-fdump-rtl-split1'
- '-fdump-rtl-split2'
- '-fdump-rtl-split3'
- '-fdump-rtl-split4'
- '-fdump-rtl-split5'
+ `-fdump-rtl-split1'
+ `-fdump-rtl-split2'
+ `-fdump-rtl-split3'
+ `-fdump-rtl-split4'
+ `-fdump-rtl-split5'
These options enable dumping after five rounds of instruction
splitting.
- '-fdump-rtl-sms'
+ `-fdump-rtl-sms'
Dump after modulo scheduling. This pass is only run on some
architectures.
- '-fdump-rtl-stack'
+ `-fdump-rtl-stack'
Dump after conversion from GCC's "flat register file"
registers to the x87's stack-like registers. This pass is
only run on x86 variants.
- '-fdump-rtl-subreg1'
- '-fdump-rtl-subreg2'
- '-fdump-rtl-subreg1' and '-fdump-rtl-subreg2' enable dumping
+ `-fdump-rtl-subreg1'
+ `-fdump-rtl-subreg2'
+ `-fdump-rtl-subreg1' and `-fdump-rtl-subreg2' enable dumping
after the two subreg expansion passes.
- '-fdump-rtl-unshare'
+ `-fdump-rtl-unshare'
Dump after all rtl has been unshared.
- '-fdump-rtl-vartrack'
+ `-fdump-rtl-vartrack'
Dump after variable tracking.
- '-fdump-rtl-vregs'
+ `-fdump-rtl-vregs'
Dump after converting virtual registers to hard registers.
- '-fdump-rtl-web'
+ `-fdump-rtl-web'
Dump after live range splitting.
- '-fdump-rtl-regclass'
- '-fdump-rtl-subregs_of_mode_init'
- '-fdump-rtl-subregs_of_mode_finish'
- '-fdump-rtl-dfinit'
- '-fdump-rtl-dfinish'
+ `-fdump-rtl-regclass'
+ `-fdump-rtl-subregs_of_mode_init'
+ `-fdump-rtl-subregs_of_mode_finish'
+ `-fdump-rtl-dfinit'
+ `-fdump-rtl-dfinish'
These dumps are defined but always produce empty files.
- '-da'
- '-fdump-rtl-all'
+ `-da'
+ `-fdump-rtl-all'
Produce all the dumps listed above.
- '-dA'
+ `-dA'
Annotate the assembler output with miscellaneous debugging
information.
- '-dD'
+ `-dD'
Dump all macro definitions, at the end of preprocessing, in
addition to normal output.
- '-dH'
+ `-dH'
Produce a core dump whenever an error occurs.
- '-dp'
+ `-dp'
Annotate the assembler output with a comment indicating which
pattern and alternative is used. The length of each
instruction is also printed.
- '-dP'
+ `-dP'
Dump the RTL in the assembler output as a comment before each
- instruction. Also turns on '-dp' annotation.
+ instruction. Also turns on `-dp' annotation.
- '-dx'
+ `-dx'
Just generate RTL for a function instead of compiling it.
- Usually used with '-fdump-rtl-expand'.
+ Usually used with `-fdump-rtl-expand'.
-'-fdump-noaddr'
- When doing debugging dumps, suppress address output. This makes it
- more feasible to use diff on debugging dumps for compiler
+`-fdump-noaddr'
+ When doing debugging dumps, suppress address output. This makes
+ it more feasible to use diff on debugging dumps for compiler
invocations with different compiler binaries and/or different text
/ bss / data / heap / stack / dso start locations.
-'-freport-bug'
+`-freport-bug'
Collect and dump debug information into temporary file if ICE in
C/C++ compiler occured.
-'-fdump-unnumbered'
+`-fdump-unnumbered'
When doing debugging dumps, suppress instruction numbers and
address output. This makes it more feasible to use diff on
- debugging dumps for compiler invocations with different options, in
- particular with and without '-g'.
+ debugging dumps for compiler invocations with different options,
+ in particular with and without `-g'.
-'-fdump-unnumbered-links'
- When doing debugging dumps (see '-d' option above), suppress
+`-fdump-unnumbered-links'
+ When doing debugging dumps (see `-d' option above), suppress
instruction numbers for the links to the previous and next
instructions in a sequence.
-'-fdump-translation-unit (C++ only)'
-'-fdump-translation-unit-OPTIONS (C++ only)'
+`-fdump-translation-unit (C++ only)'
+`-fdump-translation-unit-OPTIONS (C++ only)'
Dump a representation of the tree structure for the entire
translation unit to a file. The file name is made by appending
- '.tu' to the source file name, and the file is created in the same
- directory as the output file. If the '-OPTIONS' form is used,
+ `.tu' to the source file name, and the file is created in the same
+ directory as the output file. If the `-OPTIONS' form is used,
OPTIONS controls the details of the dump as described for the
- '-fdump-tree' options.
+ `-fdump-tree' options.
-'-fdump-class-hierarchy (C++ only)'
-'-fdump-class-hierarchy-OPTIONS (C++ only)'
+`-fdump-class-hierarchy (C++ only)'
+`-fdump-class-hierarchy-OPTIONS (C++ only)'
Dump a representation of each class's hierarchy and virtual
function table layout to a file. The file name is made by
- appending '.class' to the source file name, and the file is created
- in the same directory as the output file. If the '-OPTIONS' form
- is used, OPTIONS controls the details of the dump as described for
- the '-fdump-tree' options.
+ appending `.class' to the source file name, and the file is
+ created in the same directory as the output file. If the
+ `-OPTIONS' form is used, OPTIONS controls the details of the dump
+ as described for the `-fdump-tree' options.
-'-fdump-ipa-SWITCH'
+`-fdump-ipa-SWITCH'
Control the dumping at various stages of inter-procedural analysis
language tree to a file. The file name is generated by appending a
switch specific suffix to the source file name, and the file is
created in the same directory as the output file. The following
dumps are possible:
- 'all'
+ `all'
Enables all inter-procedural analysis dumps.
- 'cgraph'
+ `cgraph'
Dumps information about call-graph optimization, unused
function removal, and inlining decisions.
- 'inline'
+ `inline'
Dump after function inlining.
-'-fdump-passes'
+
+`-fdump-passes'
Dump the list of optimization passes that are turned on and off by
the current command-line options.
-'-fdump-statistics-OPTION'
+`-fdump-statistics-OPTION'
Enable and control dumping of pass statistics in a separate file.
The file name is generated by appending a suffix ending in
- '.statistics' to the source file name, and the file is created in
- the same directory as the output file. If the '-OPTION' form is
- used, '-stats' causes counters to be summed over the whole
- compilation unit while '-details' dumps every event as the passes
+ `.statistics' to the source file name, and the file is created in
+ the same directory as the output file. If the `-OPTION' form is
+ used, `-stats' causes counters to be summed over the whole
+ compilation unit while `-details' dumps every event as the passes
generate them. The default with no option is to sum counters for
each function compiled.
-'-fdump-tree-SWITCH'
-'-fdump-tree-SWITCH-OPTIONS'
-'-fdump-tree-SWITCH-OPTIONS=FILENAME'
+`-fdump-tree-SWITCH'
+`-fdump-tree-SWITCH-OPTIONS'
+`-fdump-tree-SWITCH-OPTIONS=FILENAME'
Control the dumping at various stages of processing the
intermediate language tree to a file. The file name is generated
by appending a switch-specific suffix to the source file name, and
- the file is created in the same directory as the output file. In
- case of '=FILENAME' option, the dump is output on the given file
- instead of the auto named dump files. If the '-OPTIONS' form is
- used, OPTIONS is a list of '-' separated options which control the
+ the file is created in the same directory as the output file. In
+ case of `=FILENAME' option, the dump is output on the given file
+ instead of the auto named dump files. If the `-OPTIONS' form is
+ used, OPTIONS is a list of `-' separated options which control the
details of the dump. Not all options are applicable to all dumps;
those that are not meaningful are ignored. The following options
are available
- 'address'
+ `address'
Print the address of each node. Usually this is not
meaningful as it changes according to the environment and
- source file. Its primary use is for tying up a dump file with
- a debug environment.
- 'asmname'
- If 'DECL_ASSEMBLER_NAME' has been set for a given decl, use
- that in the dump instead of 'DECL_NAME'. Its primary use is
+ source file. Its primary use is for tying up a dump file
+ with a debug environment.
+
+ `asmname'
+ If `DECL_ASSEMBLER_NAME' has been set for a given decl, use
+ that in the dump instead of `DECL_NAME'. Its primary use is
ease of use working backward from mangled names in the
assembly file.
- 'slim'
+
+ `slim'
When dumping front-end intermediate representations, inhibit
dumping of members of a scope or body of a function merely
because that scope has been reached. Only dump such items
@@ -6174,246 +6211,269 @@ program or GCC:
When dumping RTL, print the RTL in slim (condensed) form
instead of the default LISP-like representation.
- 'raw'
+
+ `raw'
Print a raw representation of the tree. By default, trees are
pretty-printed into a C-like representation.
- 'details'
- Enable more detailed dumps (not honored by every dump option).
- Also include information from the optimization passes.
- 'stats'
+
+ `details'
+ Enable more detailed dumps (not honored by every dump
+ option). Also include information from the optimization
+ passes.
+
+ `stats'
Enable dumping various statistics about the pass (not honored
by every dump option).
- 'blocks'
+
+ `blocks'
Enable showing basic block boundaries (disabled in raw dumps).
- 'graph'
+
+ `graph'
For each of the other indicated dump files
- ('-fdump-rtl-PASS'), dump a representation of the control flow
- graph suitable for viewing with GraphViz to
- 'FILE.PASSID.PASS.dot'. Each function in the file is
+ (`-fdump-rtl-PASS'), dump a representation of the control
+ flow graph suitable for viewing with GraphViz to
+ `FILE.PASSID.PASS.dot'. Each function in the file is
pretty-printed as a subgraph, so that GraphViz can render them
all in a single plot.
- This option currently only works for RTL dumps, and the RTL is
- always dumped in slim form.
- 'vops'
+ This option currently only works for RTL dumps, and the RTL
+ is always dumped in slim form.
+
+ `vops'
Enable showing virtual operands for every statement.
- 'lineno'
+
+ `lineno'
Enable showing line numbers for statements.
- 'uid'
- Enable showing the unique ID ('DECL_UID') for each variable.
- 'verbose'
+
+ `uid'
+ Enable showing the unique ID (`DECL_UID') for each variable.
+
+ `verbose'
Enable showing the tree dump for each statement.
- 'eh'
+
+ `eh'
Enable showing the EH region number holding each statement.
- 'scev'
+
+ `scev'
Enable showing scalar evolution analysis details.
- 'optimized'
+
+ `optimized'
Enable showing optimization information (only available in
certain passes).
- 'missed'
- Enable showing missed optimization information (only available
- in certain passes).
- 'note'
- Enable other detailed optimization information (only available
- in certain passes).
- '=FILENAME'
+
+ `missed'
+ Enable showing missed optimization information (only
+ available in certain passes).
+
+ `note'
+ Enable other detailed optimization information (only
+ available in certain passes).
+
+ `=FILENAME'
Instead of an auto named dump file, output into the given file
- name. The file names 'stdout' and 'stderr' are treated
+ name. The file names `stdout' and `stderr' are treated
specially and are considered already open standard streams.
For example,
gcc -O2 -ftree-vectorize -fdump-tree-vect-blocks=foo.dump
-fdump-tree-pre=stderr file.c
- outputs vectorizer dump into 'foo.dump', while the PRE dump is
- output on to 'stderr'. If two conflicting dump filenames are
+ outputs vectorizer dump into `foo.dump', while the PRE dump is
+ output on to `stderr'. If two conflicting dump filenames are
given for the same pass, then the latter option overrides the
earlier one.
- 'all'
- Turn on all options, except 'raw', 'slim', 'verbose' and
- 'lineno'.
+ `all'
+ Turn on all options, except `raw', `slim', `verbose' and
+ `lineno'.
- 'optall'
- Turn on all optimization options, i.e., 'optimized', 'missed',
- and 'note'.
+ `optall'
+ Turn on all optimization options, i.e., `optimized',
+ `missed', and `note'.
The following tree dumps are possible:
+ `original'
+ Dump before any tree based optimization, to `FILE.original'.
- 'original'
- Dump before any tree based optimization, to 'FILE.original'.
+ `optimized'
+ Dump after all tree based optimization, to `FILE.optimized'.
- 'optimized'
- Dump after all tree based optimization, to 'FILE.optimized'.
-
- 'gimple'
- Dump each function before and after the gimplification pass to
- a file. The file name is made by appending '.gimple' to the
- source file name.
+ `gimple'
+ Dump each function before and after the gimplification pass
+ to a file. The file name is made by appending `.gimple' to
+ the source file name.
- 'cfg'
+ `cfg'
Dump the control flow graph of each function to a file. The
- file name is made by appending '.cfg' to the source file name.
+ file name is made by appending `.cfg' to the source file name.
- 'ch'
+ `ch'
Dump each function after copying loop headers. The file name
- is made by appending '.ch' to the source file name.
+ is made by appending `.ch' to the source file name.
- 'ssa'
- Dump SSA related information to a file. The file name is made
- by appending '.ssa' to the source file name.
+ `ssa'
+ Dump SSA related information to a file. The file name is
+ made by appending `.ssa' to the source file name.
- 'alias'
- Dump aliasing information for each function. The file name is
- made by appending '.alias' to the source file name.
+ `alias'
+ Dump aliasing information for each function. The file name
+ is made by appending `.alias' to the source file name.
- 'ccp'
+ `ccp'
Dump each function after CCP. The file name is made by
- appending '.ccp' to the source file name.
+ appending `.ccp' to the source file name.
- 'storeccp'
+ `storeccp'
Dump each function after STORE-CCP. The file name is made by
- appending '.storeccp' to the source file name.
+ appending `.storeccp' to the source file name.
- 'pre'
+ `pre'
Dump trees after partial redundancy elimination. The file
- name is made by appending '.pre' to the source file name.
+ name is made by appending `.pre' to the source file name.
- 'fre'
+ `fre'
Dump trees after full redundancy elimination. The file name
- is made by appending '.fre' to the source file name.
+ is made by appending `.fre' to the source file name.
- 'copyprop'
+ `copyprop'
Dump trees after copy propagation. The file name is made by
- appending '.copyprop' to the source file name.
+ appending `.copyprop' to the source file name.
- 'store_copyprop'
+ `store_copyprop'
Dump trees after store copy-propagation. The file name is
- made by appending '.store_copyprop' to the source file name.
+ made by appending `.store_copyprop' to the source file name.
- 'dce'
- Dump each function after dead code elimination. The file name
- is made by appending '.dce' to the source file name.
+ `dce'
+ Dump each function after dead code elimination. The file
+ name is made by appending `.dce' to the source file name.
- 'sra'
+ `sra'
Dump each function after performing scalar replacement of
- aggregates. The file name is made by appending '.sra' to the
+ aggregates. The file name is made by appending `.sra' to the
source file name.
- 'sink'
+ `sink'
Dump each function after performing code sinking. The file
- name is made by appending '.sink' to the source file name.
+ name is made by appending `.sink' to the source file name.
- 'dom'
+ `dom'
Dump each function after applying dominator tree
- optimizations. The file name is made by appending '.dom' to
+ optimizations. The file name is made by appending `.dom' to
the source file name.
- 'dse'
- Dump each function after applying dead store elimination. The
- file name is made by appending '.dse' to the source file name.
+ `dse'
+ Dump each function after applying dead store elimination.
+ The file name is made by appending `.dse' to the source file
+ name.
- 'phiopt'
+ `phiopt'
Dump each function after optimizing PHI nodes into
straightline code. The file name is made by appending
- '.phiopt' to the source file name.
+ `.phiopt' to the source file name.
- 'forwprop'
+ `forwprop'
Dump each function after forward propagating single use
- variables. The file name is made by appending '.forwprop' to
+ variables. The file name is made by appending `.forwprop' to
the source file name.
- 'copyrename'
+ `copyrename'
Dump each function after applying the copy rename
optimization. The file name is made by appending
- '.copyrename' to the source file name.
+ `.copyrename' to the source file name.
- 'nrv'
+ `nrv'
Dump each function after applying the named return value
optimization on generic trees. The file name is made by
- appending '.nrv' to the source file name.
+ appending `.nrv' to the source file name.
- 'vect'
- Dump each function after applying vectorization of loops. The
- file name is made by appending '.vect' to the source file
+ `vect'
+ Dump each function after applying vectorization of loops.
+ The file name is made by appending `.vect' to the source file
name.
- 'slp'
+ `slp'
Dump each function after applying vectorization of basic
- blocks. The file name is made by appending '.slp' to the
+ blocks. The file name is made by appending `.slp' to the
source file name.
- 'vrp'
- Dump each function after Value Range Propagation (VRP). The
- file name is made by appending '.vrp' to the source file name.
+ `vrp'
+ Dump each function after Value Range Propagation (VRP). The
+ file name is made by appending `.vrp' to the source file name.
- 'all'
- Enable all the available tree dumps with the flags provided in
- this option.
+ `all'
+ Enable all the available tree dumps with the flags provided
+ in this option.
-'-fopt-info'
-'-fopt-info-OPTIONS'
-'-fopt-info-OPTIONS=FILENAME'
- Controls optimization dumps from various optimization passes. If
- the '-OPTIONS' form is used, OPTIONS is a list of '-' separated
+`-fopt-info'
+`-fopt-info-OPTIONS'
+`-fopt-info-OPTIONS=FILENAME'
+ Controls optimization dumps from various optimization passes. If
+ the `-OPTIONS' form is used, OPTIONS is a list of `-' separated
option keywords to select the dump details and optimizations.
The OPTIONS can be divided into two groups: options describing the
verbosity of the dump, and options describing which optimizations
- should be included. The options from both the groups can be freely
- mixed as they are non-overlapping. However, in case of any
+ should be included. The options from both the groups can be freely
+ mixed as they are non-overlapping. However, in case of any
conflicts, the later options override the earlier options on the
command line.
The following options control the dump verbosity:
- 'optimized'
+ `optimized'
Print information when an optimization is successfully
- applied. It is up to a pass to decide which information is
- relevant. For example, the vectorizer passes print the source
+ applied. It is up to a pass to decide which information is
+ relevant. For example, the vectorizer passes print the source
location of loops which are successfully vectorized.
- 'missed'
- Print information about missed optimizations. Individual
+
+ `missed'
+ Print information about missed optimizations. Individual
passes control which information to include in the output.
- 'note'
+
+ `note'
Print verbose information about optimizations, such as certain
transformations, more detailed messages about decisions etc.
- 'all'
- Print detailed optimization information. This includes
- 'optimized', 'missed', and 'note'.
+
+ `all'
+ Print detailed optimization information. This includes
+ `optimized', `missed', and `note'.
One or more of the following option keywords can be used to
describe a group of optimizations:
- 'ipa'
+ `ipa'
Enable dumps from all interprocedural optimizations.
- 'loop'
+
+ `loop'
Enable dumps from all loop optimizations.
- 'inline'
+
+ `inline'
Enable dumps from all inlining optimizations.
- 'vec'
+
+ `vec'
Enable dumps from all vectorization optimizations.
- 'optall'
- Enable dumps from all optimizations. This is a superset of
+
+ `optall'
+ Enable dumps from all optimizations. This is a superset of
the optimization groups listed above.
- If OPTIONS is omitted, it defaults to 'optimized-optall', which
+ If OPTIONS is omitted, it defaults to `optimized-optall', which
means to dump all info about successful optimizations from all the
passes.
- If the FILENAME is provided, then the dumps from all the applicable
- optimizations are concatenated into the FILENAME. Otherwise the
- dump is output onto 'stderr'. Though multiple '-fopt-info' options
- are accepted, only one of them can include a FILENAME. If other
- filenames are provided then all but the first such option are
- ignored.
+ If the FILENAME is provided, then the dumps from all the
+ applicable optimizations are concatenated into the FILENAME.
+ Otherwise the dump is output onto `stderr'. Though multiple
+ `-fopt-info' options are accepted, only one of them can include a
+ FILENAME. If other filenames are provided then all but the first
+ such option are ignored.
Note that the output FILENAME is overwritten in case of multiple
- translation units. If a combined output from multiple translation
- units is desired, 'stderr' should be used instead.
+ translation units. If a combined output from multiple translation
+ units is desired, `stderr' should be used instead.
In the following example, the optimization info is output to
- 'stderr':
+ `stderr':
gcc -O3 -fopt-info
@@ -6421,89 +6481,89 @@ program or GCC:
gcc -O3 -fopt-info-missed=missed.all
outputs missed optimization report from all the passes into
- 'missed.all', and this one:
+ `missed.all', and this one:
gcc -O2 -ftree-vectorize -fopt-info-vec-missed
prints information about missed optimization opportunities from
- vectorization passes on 'stderr'. Note that
- '-fopt-info-vec-missed' is equivalent to '-fopt-info-missed-vec'.
+ vectorization passes on `stderr'. Note that
+ `-fopt-info-vec-missed' is equivalent to `-fopt-info-missed-vec'.
As another example,
gcc -O3 -fopt-info-inline-optimized-missed=inline.txt
- outputs information about missed optimizations as well as optimized
- locations from all the inlining passes into 'inline.txt'.
+ outputs information about missed optimizations as well as
+ optimized locations from all the inlining passes into `inline.txt'.
Finally, consider:
gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt
- Here the two output filenames 'vec.miss' and 'loop.opt' are in
- conflict since only one output file is allowed. In this case, only
+ Here the two output filenames `vec.miss' and `loop.opt' are in
+ conflict since only one output file is allowed. In this case, only
the first option takes effect and the subsequent options are
- ignored. Thus only 'vec.miss' is produced which contains dumps
+ ignored. Thus only `vec.miss' is produced which contains dumps
from the vectorizer about missed opportunities.
-'-frandom-seed=NUMBER'
+`-frandom-seed=NUMBER'
This option provides a seed that GCC uses in place of random
numbers in generating certain symbol names that have to be
different in every compiled file. It is also used to place unique
stamps in coverage data files and the object files that produce
- them. You can use the '-frandom-seed' option to produce
+ them. You can use the `-frandom-seed' option to produce
reproducibly identical object files.
The NUMBER should be different for every file you compile.
-'-fsched-verbose=N'
+`-fsched-verbose=N'
On targets that use instruction scheduling, this option controls
the amount of debugging output the scheduler prints. This
information is written to standard error, unless
- '-fdump-rtl-sched1' or '-fdump-rtl-sched2' is specified, in which
- case it is output to the usual dump listing file, '.sched1' or
- '.sched2' respectively. However for N greater than nine, the
+ `-fdump-rtl-sched1' or `-fdump-rtl-sched2' is specified, in which
+ case it is output to the usual dump listing file, `.sched1' or
+ `.sched2' respectively. However for N greater than nine, the
output is always printed to standard error.
- For N greater than zero, '-fsched-verbose' outputs the same
- information as '-fdump-rtl-sched1' and '-fdump-rtl-sched2'. For N
+ For N greater than zero, `-fsched-verbose' outputs the same
+ information as `-fdump-rtl-sched1' and `-fdump-rtl-sched2'. For N
greater than one, it also output basic block probabilities,
detailed ready list information and unit/insn info. For N greater
than two, it includes RTL at abort point, control-flow and regions
- info. And for N over four, '-fsched-verbose' also includes
+ info. And for N over four, `-fsched-verbose' also includes
dependence info.
-'-save-temps'
-'-save-temps=cwd'
+`-save-temps'
+`-save-temps=cwd'
Store the usual "temporary" intermediate files permanently; place
them in the current directory and name them based on the source
- file. Thus, compiling 'foo.c' with '-c -save-temps' produces files
- 'foo.i' and 'foo.s', as well as 'foo.o'. This creates a
- preprocessed 'foo.i' output file even though the compiler now
+ file. Thus, compiling `foo.c' with `-c -save-temps' produces files
+ `foo.i' and `foo.s', as well as `foo.o'. This creates a
+ preprocessed `foo.i' output file even though the compiler now
normally uses an integrated preprocessor.
- When used in combination with the '-x' command-line option,
- '-save-temps' is sensible enough to avoid over writing an input
+ When used in combination with the `-x' command-line option,
+ `-save-temps' is sensible enough to avoid over writing an input
source file with the same extension as an intermediate file. The
corresponding intermediate file may be obtained by renaming the
- source file before using '-save-temps'.
+ source file before using `-save-temps'.
If you invoke GCC in parallel, compiling several different source
files that share a common base name in different subdirectories or
the same source file compiled for multiple output destinations, it
- is likely that the different parallel compilers will interfere with
- each other, and overwrite the temporary files. For instance:
+ is likely that the different parallel compilers will interfere
+ with each other, and overwrite the temporary files. For instance:
gcc -save-temps -o outdir1/foo.o indir1/foo.c&
gcc -save-temps -o outdir2/foo.o indir2/foo.c&
- may result in 'foo.i' and 'foo.o' being written to simultaneously
+ may result in `foo.i' and `foo.o' being written to simultaneously
by both compilers.
-'-save-temps=obj'
+`-save-temps=obj'
Store the usual "temporary" intermediate files permanently. If the
- '-o' option is used, the temporary files are based on the object
- file. If the '-o' option is not used, the '-save-temps=obj' switch
- behaves like '-save-temps'.
+ `-o' option is used, the temporary files are based on the object
+ file. If the `-o' option is not used, the `-save-temps=obj'
+ switch behaves like `-save-temps'.
For example:
@@ -6511,10 +6571,10 @@ program or GCC:
gcc -save-temps=obj -c bar.c -o dir/xbar.o
gcc -save-temps=obj foobar.c -o dir2/yfoobar
- creates 'foo.i', 'foo.s', 'dir/xbar.i', 'dir/xbar.s',
- 'dir2/yfoobar.i', 'dir2/yfoobar.s', and 'dir2/yfoobar.o'.
+ creates `foo.i', `foo.s', `dir/xbar.i', `dir/xbar.s',
+ `dir2/yfoobar.i', `dir2/yfoobar.s', and `dir2/yfoobar.o'.
-'-time[=FILE]'
+`-time[=FILE]'
Report the CPU time taken by each subprocess in the compilation
sequence. For C source files, this is the compiler proper and
assembler (plus the linker if linking is done).
@@ -6530,8 +6590,8 @@ program or GCC:
time", time spent executing operating system routines on behalf of
the program. Both numbers are in seconds.
- With the specification of an output file, the output is appended to
- the named file, and it looks like this:
+ With the specification of an output file, the output is appended
+ to the named file, and it looks like this:
0.12 0.01 cc1 OPTIONS
0.00 0.01 as OPTIONS
@@ -6541,120 +6601,120 @@ program or GCC:
one can later tell what file was being compiled, and with which
options.
-'-fvar-tracking'
- Run variable tracking pass. It computes where variables are stored
- at each position in code. Better debugging information is then
- generated (if the debugging information format supports this
+`-fvar-tracking'
+ Run variable tracking pass. It computes where variables are
+ stored at each position in code. Better debugging information is
+ then generated (if the debugging information format supports this
information).
- It is enabled by default when compiling with optimization ('-Os',
- '-O', '-O2', ...), debugging information ('-g') and the debug info
+ It is enabled by default when compiling with optimization (`-Os',
+ `-O', `-O2', ...), debugging information (`-g') and the debug info
format supports it.
-'-fvar-tracking-assignments'
+`-fvar-tracking-assignments'
Annotate assignments to user variables early in the compilation and
attempt to carry the annotations over throughout the compilation
all the way to the end, in an attempt to improve debug information
- while optimizing. Use of '-gdwarf-4' is recommended along with it.
+ while optimizing. Use of `-gdwarf-4' is recommended along with it.
It can be enabled even if var-tracking is disabled, in which case
annotations are created and maintained, but discarded at the end.
- By default, this flag is enabled together with '-fvar-tracking',
+ By default, this flag is enabled together with `-fvar-tracking',
except when selective scheduling is enabled.
-'-fvar-tracking-assignments-toggle'
- Toggle '-fvar-tracking-assignments', in the same way that
- '-gtoggle' toggles '-g'.
+`-fvar-tracking-assignments-toggle'
+ Toggle `-fvar-tracking-assignments', in the same way that
+ `-gtoggle' toggles `-g'.
-'-print-file-name=LIBRARY'
- Print the full absolute name of the library file LIBRARY that would
- be used when linking--and don't do anything else. With this
+`-print-file-name=LIBRARY'
+ Print the full absolute name of the library file LIBRARY that
+ would be used when linking--and don't do anything else. With this
option, GCC does not compile or link anything; it just prints the
file name.
-'-print-multi-directory'
+`-print-multi-directory'
Print the directory name corresponding to the multilib selected by
any other switches present in the command line. This directory is
- supposed to exist in 'GCC_EXEC_PREFIX'.
+ supposed to exist in `GCC_EXEC_PREFIX'.
-'-print-multi-lib'
+`-print-multi-lib'
Print the mapping from multilib directory names to compiler
switches that enable them. The directory name is separated from
- the switches by ';', and each switch starts with an '@' instead of
- the '-', without spaces between multiple switches. This is
+ the switches by `;', and each switch starts with an `@' instead of
+ the `-', without spaces between multiple switches. This is
supposed to ease shell processing.
-'-print-multi-os-directory'
+`-print-multi-os-directory'
Print the path to OS libraries for the selected multilib, relative
- to some 'lib' subdirectory. If OS libraries are present in the
- 'lib' subdirectory and no multilibs are used, this is usually just
- '.', if OS libraries are present in 'libSUFFIX' sibling directories
- this prints e.g. '../lib64', '../lib' or '../lib32', or if OS
- libraries are present in 'lib/SUBDIR' subdirectories it prints e.g.
- 'amd64', 'sparcv9' or 'ev6'.
+ to some `lib' subdirectory. If OS libraries are present in the
+ `lib' subdirectory and no multilibs are used, this is usually just
+ `.', if OS libraries are present in `libSUFFIX' sibling
+ directories this prints e.g. `../lib64', `../lib' or `../lib32',
+ or if OS libraries are present in `lib/SUBDIR' subdirectories it
+ prints e.g. `amd64', `sparcv9' or `ev6'.
-'-print-multiarch'
- Print the path to OS libraries for the selected multiarch, relative
- to some 'lib' subdirectory.
+`-print-multiarch'
+ Print the path to OS libraries for the selected multiarch,
+ relative to some `lib' subdirectory.
-'-print-prog-name=PROGRAM'
- Like '-print-file-name', but searches for a program such as 'cpp'.
+`-print-prog-name=PROGRAM'
+ Like `-print-file-name', but searches for a program such as `cpp'.
-'-print-libgcc-file-name'
- Same as '-print-file-name=libgcc.a'.
+`-print-libgcc-file-name'
+ Same as `-print-file-name=libgcc.a'.
- This is useful when you use '-nostdlib' or '-nodefaultlibs' but you
- do want to link with 'libgcc.a'. You can do:
+ This is useful when you use `-nostdlib' or `-nodefaultlibs' but
+ you do want to link with `libgcc.a'. You can do:
gcc -nostdlib FILES... `gcc -print-libgcc-file-name`
-'-print-search-dirs'
+`-print-search-dirs'
Print the name of the configured installation directory and a list
- of program and library directories 'gcc' searches--and don't do
+ of program and library directories `gcc' searches--and don't do
anything else.
- This is useful when 'gcc' prints the error message 'installation
+ This is useful when `gcc' prints the error message `installation
problem, cannot exec cpp0: No such file or directory'. To resolve
- this you either need to put 'cpp0' and the other compiler
- components where 'gcc' expects to find them, or you can set the
- environment variable 'GCC_EXEC_PREFIX' to the directory where you
- installed them. Don't forget the trailing '/'. *Note Environment
+ this you either need to put `cpp0' and the other compiler
+ components where `gcc' expects to find them, or you can set the
+ environment variable `GCC_EXEC_PREFIX' to the directory where you
+ installed them. Don't forget the trailing `/'. *Note Environment
Variables::.
-'-print-sysroot'
- Print the target sysroot directory that is used during compilation.
- This is the target sysroot specified either at configure time or
- using the '--sysroot' option, possibly with an extra suffix that
- depends on compilation options. If no target sysroot is specified,
- the option prints nothing.
+`-print-sysroot'
+ Print the target sysroot directory that is used during
+ compilation. This is the target sysroot specified either at
+ configure time or using the `--sysroot' option, possibly with an
+ extra suffix that depends on compilation options. If no target
+ sysroot is specified, the option prints nothing.
-'-print-sysroot-headers-suffix'
+`-print-sysroot-headers-suffix'
Print the suffix added to the target sysroot when searching for
headers, or give an error if the compiler is not configured with
such a suffix--and don't do anything else.
-'-dumpmachine'
+`-dumpmachine'
Print the compiler's target machine (for example,
- 'i686-pc-linux-gnu')--and don't do anything else.
+ `i686-pc-linux-gnu')--and don't do anything else.
-'-dumpversion'
- Print the compiler version (for example, '3.0')--and don't do
+`-dumpversion'
+ Print the compiler version (for example, `3.0')--and don't do
anything else.
-'-dumpspecs'
+`-dumpspecs'
Print the compiler's built-in specs--and don't do anything else.
(This is used when GCC itself is being built.) *Note Spec Files::.
-'-fno-eliminate-unused-debug-types'
- Normally, when producing DWARF 2 output, GCC avoids producing debug
- symbol output for types that are nowhere used in the source file
- being compiled. Sometimes it is useful to have GCC emit debugging
- information for all types declared in a compilation unit,
- regardless of whether or not they are actually used in that
- compilation unit, for example if, in the debugger, you want to cast
- a value to a type that is not actually used in your program (but is
- declared). More often, however, this results in a significant
- amount of wasted space.
+`-fno-eliminate-unused-debug-types'
+ Normally, when producing DWARF 2 output, GCC avoids producing
+ debug symbol output for types that are nowhere used in the source
+ file being compiled. Sometimes it is useful to have GCC emit
+ debugging information for all types declared in a compilation
+ unit, regardless of whether or not they are actually used in that
+ compilation unit, for example if, in the debugger, you want to
+ cast a value to a type that is not actually used in your program
+ (but is declared). More often, however, this results in a
+ significant amount of wasted space.

File: gcc.info, Node: Optimize Options, Next: Preprocessor Options, Prev: Debugging Options, Up: Invoking GCC
@@ -6671,38 +6731,38 @@ between statements, you can then assign a new value to any variable or
change the program counter to any other statement in the function and
get exactly the results you expect from the source code.
- Turning on optimization flags makes the compiler attempt to improve the
-performance and/or code size at the expense of compilation time and
+ Turning on optimization flags makes the compiler attempt to improve
+the performance and/or code size at the expense of compilation time and
possibly the ability to debug the program.
The compiler performs optimization based on the knowledge it has of the
program. Compiling multiple files at once to a single output file mode
-allows the compiler to use information gained from all of the files when
-compiling each of them.
+allows the compiler to use information gained from all of the files
+when compiling each of them.
Not all optimizations are controlled directly by a flag. Only
optimizations that have a flag are listed in this section.
- Most optimizations are only enabled if an '-O' level is set on the
+ Most optimizations are only enabled if an `-O' level is set on the
command line. Otherwise they are disabled, even if individual
optimization flags are specified.
Depending on the target and how GCC was configured, a slightly
-different set of optimizations may be enabled at each '-O' level than
-those listed here. You can invoke GCC with '-Q --help=optimizers' to
+different set of optimizations may be enabled at each `-O' level than
+those listed here. You can invoke GCC with `-Q --help=optimizers' to
find out the exact set of optimizations that are enabled at each level.
*Note Overall Options::, for examples.
-'-O'
-'-O1'
+`-O'
+`-O1'
Optimize. Optimizing compilation takes somewhat more time, and a
lot more memory for a large function.
- With '-O', the compiler tries to reduce code size and execution
+ With `-O', the compiler tries to reduce code size and execution
time, without performing any optimizations that take a great deal
of compilation time.
- '-O' turns on the following optimization flags:
+ `-O' turns on the following optimization flags:
-fauto-inc-dec
-fbranch-count-reg
-fcombine-stack-adjustments
@@ -6743,16 +6803,16 @@ find out the exact set of optimizations that are enabled at each level.
-ftree-ter
-funit-at-a-time
- '-O' also turns on '-fomit-frame-pointer' on machines where doing
+ `-O' also turns on `-fomit-frame-pointer' on machines where doing
so does not interfere with debugging.
-'-O2'
+`-O2'
Optimize even more. GCC performs nearly all supported
optimizations that do not involve a space-speed tradeoff. As
- compared to '-O', this option increases both compilation time and
+ compared to `-O', this option increases both compilation time and
the performance of the generated code.
- '-O2' turns on all optimization flags specified by '-O'. It also
+ `-O2' turns on all optimization flags specified by `-O'. It also
turns on the following optimization flags:
-fthread-jumps
-falign-functions -falign-jumps
@@ -6788,197 +6848,201 @@ find out the exact set of optimizations that are enabled at each level.
-ftree-vrp
-fipa-ra
- Please note the warning under '-fgcse' about invoking '-O2' on
+ Please note the warning under `-fgcse' about invoking `-O2' on
programs that use computed gotos.
-'-O3'
- Optimize yet more. '-O3' turns on all optimizations specified by
- '-O2' and also turns on the '-finline-functions',
- '-funswitch-loops', '-fpredictive-commoning',
- '-fgcse-after-reload', '-ftree-loop-vectorize',
- '-ftree-loop-distribute-patterns', '-ftree-slp-vectorize',
- '-fvect-cost-model', '-ftree-partial-pre' and '-fipa-cp-clone'
+`-O3'
+ Optimize yet more. `-O3' turns on all optimizations specified by
+ `-O2' and also turns on the `-finline-functions',
+ `-funswitch-loops', `-fpredictive-commoning',
+ `-fgcse-after-reload', `-ftree-loop-vectorize',
+ `-ftree-loop-distribute-patterns', `-ftree-slp-vectorize',
+ `-fvect-cost-model', `-ftree-partial-pre' and `-fipa-cp-clone'
options.
-'-O0'
+`-O0'
Reduce compilation time and make debugging produce the expected
results. This is the default.
-'-Os'
- Optimize for size. '-Os' enables all '-O2' optimizations that do
+`-Os'
+ Optimize for size. `-Os' enables all `-O2' optimizations that do
not typically increase code size. It also performs further
optimizations designed to reduce code size.
- '-Os' disables the following optimization flags:
+ `-Os' disables the following optimization flags:
-falign-functions -falign-jumps -falign-loops
-falign-labels -freorder-blocks -freorder-blocks-and-partition
-fprefetch-loop-arrays
-'-Ofast'
- Disregard strict standards compliance. '-Ofast' enables all '-O3'
+`-Ofast'
+ Disregard strict standards compliance. `-Ofast' enables all `-O3'
optimizations. It also enables optimizations that are not valid
- for all standard-compliant programs. It turns on '-ffast-math' and
- the Fortran-specific '-fno-protect-parens' and '-fstack-arrays'.
-
-'-Og'
- Optimize debugging experience. '-Og' enables optimizations that do
- not interfere with debugging. It should be the optimization level
- of choice for the standard edit-compile-debug cycle, offering a
- reasonable level of optimization while maintaining fast compilation
- and a good debugging experience.
-
- If you use multiple '-O' options, with or without level numbers,
+ for all standard-compliant programs. It turns on `-ffast-math'
+ and the Fortran-specific `-fno-protect-parens' and
+ `-fstack-arrays'.
+
+`-Og'
+ Optimize debugging experience. `-Og' enables optimizations that
+ do not interfere with debugging. It should be the optimization
+ level of choice for the standard edit-compile-debug cycle, offering
+ a reasonable level of optimization while maintaining fast
+ compilation and a good debugging experience.
+
+ If you use multiple `-O' options, with or without level numbers,
the last such option is the one that is effective.
- Options of the form '-fFLAG' specify machine-independent flags. Most
+ Options of the form `-fFLAG' specify machine-independent flags. Most
flags have both positive and negative forms; the negative form of
-'-ffoo' is '-fno-foo'. In the table below, only one of the forms is
-listed--the one you typically use. You can figure out the other form by
-either removing 'no-' or adding it.
+`-ffoo' is `-fno-foo'. In the table below, only one of the forms is
+listed--the one you typically use. You can figure out the other form
+by either removing `no-' or adding it.
The following options control specific optimizations. They are either
-activated by '-O' options or are related to ones that are. You can use
+activated by `-O' options or are related to ones that are. You can use
the following flags in the rare cases when "fine-tuning" of
optimizations to be performed is desired.
-'-fno-defer-pop'
+`-fno-defer-pop'
Always pop the arguments to each function call as soon as that
function returns. For machines that must pop arguments after a
function call, the compiler normally lets arguments accumulate on
the stack for several function calls and pops them all at once.
- Disabled at levels '-O', '-O2', '-O3', '-Os'.
+ Disabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fforward-propagate'
+`-fforward-propagate'
Perform a forward propagation pass on RTL. The pass tries to
combine two instructions and checks if the result can be
simplified. If loop unrolling is active, two passes are performed
and the second is scheduled after loop unrolling.
- This option is enabled by default at optimization levels '-O',
- '-O2', '-O3', '-Os'.
+ This option is enabled by default at optimization levels `-O',
+ `-O2', `-O3', `-Os'.
-'-ffp-contract=STYLE'
- '-ffp-contract=off' disables floating-point expression contraction.
- '-ffp-contract=fast' enables floating-point expression contraction
+`-ffp-contract=STYLE'
+ `-ffp-contract=off' disables floating-point expression contraction.
+ `-ffp-contract=fast' enables floating-point expression contraction
such as forming of fused multiply-add operations if the target has
- native support for them. '-ffp-contract=on' enables floating-point
- expression contraction if allowed by the language standard. This
- is currently not implemented and treated equal to
- '-ffp-contract=off'.
+ native support for them. `-ffp-contract=on' enables
+ floating-point expression contraction if allowed by the language
+ standard. This is currently not implemented and treated equal to
+ `-ffp-contract=off'.
- The default is '-ffp-contract=fast'.
+ The default is `-ffp-contract=fast'.
-'-fomit-frame-pointer'
- Don't keep the frame pointer in a register for functions that don't
- need one. This avoids the instructions to save, set up and restore
- frame pointers; it also makes an extra register available in many
- functions. *It also makes debugging impossible on some machines.*
+`-fomit-frame-pointer'
+ Don't keep the frame pointer in a register for functions that
+ don't need one. This avoids the instructions to save, set up and
+ restore frame pointers; it also makes an extra register available
+ in many functions. *It also makes debugging impossible on some
+ machines.*
On some machines, such as the VAX, this flag has no effect, because
the standard calling sequence automatically handles the frame
pointer and nothing is saved by pretending it doesn't exist. The
- machine-description macro 'FRAME_POINTER_REQUIRED' controls whether
- a target machine supports this flag. *Note Register Usage:
- (gccint)Registers.
+ machine-description macro `FRAME_POINTER_REQUIRED' controls
+ whether a target machine supports this flag. *Note Register
+ Usage: (gccint)Registers.
The default setting (when not optimizing for size) for 32-bit
GNU/Linux x86 and 32-bit Darwin x86 targets is
- '-fomit-frame-pointer'. You can configure GCC with the
- '--enable-frame-pointer' configure option to change the default.
+ `-fomit-frame-pointer'. You can configure GCC with the
+ `--enable-frame-pointer' configure option to change the default.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-foptimize-sibling-calls'
+`-foptimize-sibling-calls'
Optimize sibling and tail recursive calls.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-foptimize-strlen'
- Optimize various standard C string functions (e.g. 'strlen',
- 'strchr' or 'strcpy') and their '_FORTIFY_SOURCE' counterparts into
- faster alternatives.
+`-foptimize-strlen'
+ Optimize various standard C string functions (e.g. `strlen',
+ `strchr' or `strcpy') and their `_FORTIFY_SOURCE' counterparts
+ into faster alternatives.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-fno-inline'
- Do not expand any functions inline apart from those marked with the
- 'always_inline' attribute. This is the default when not
+`-fno-inline'
+ Do not expand any functions inline apart from those marked with
+ the `always_inline' attribute. This is the default when not
optimizing.
- Single functions can be exempted from inlining by marking them with
- the 'noinline' attribute.
+ Single functions can be exempted from inlining by marking them
+ with the `noinline' attribute.
-'-finline-small-functions'
+`-finline-small-functions'
Integrate functions into their callers when their body is smaller
than expected function call code (so overall size of program gets
smaller). The compiler heuristically decides which functions are
simple enough to be worth integrating in this way. This inlining
applies to all functions, even those not declared inline.
- Enabled at level '-O2'.
+ Enabled at level `-O2'.
-'-findirect-inlining'
+`-findirect-inlining'
Inline also indirect calls that are discovered to be known at
compile time thanks to previous inlining. This option has any
effect only when inlining itself is turned on by the
- '-finline-functions' or '-finline-small-functions' options.
+ `-finline-functions' or `-finline-small-functions' options.
- Enabled at level '-O2'.
+ Enabled at level `-O2'.
-'-finline-functions'
+`-finline-functions'
Consider all functions for inlining, even if they are not declared
inline. The compiler heuristically decides which functions are
worth integrating in this way.
If all calls to a given function are integrated, and the function
- is declared 'static', then the function is normally not output as
+ is declared `static', then the function is normally not output as
assembler code in its own right.
- Enabled at level '-O3'.
+ Enabled at level `-O3'.
-'-finline-functions-called-once'
- Consider all 'static' functions called once for inlining into their
- caller even if they are not marked 'inline'. If a call to a given
+`-finline-functions-called-once'
+ Consider all `static' functions called once for inlining into their
+ caller even if they are not marked `inline'. If a call to a given
function is integrated, then the function is not output as
assembler code in its own right.
- Enabled at levels '-O1', '-O2', '-O3' and '-Os'.
+ Enabled at levels `-O1', `-O2', `-O3' and `-Os'.
-'-fearly-inlining'
- Inline functions marked by 'always_inline' and functions whose body
- seems smaller than the function call overhead early before doing
- '-fprofile-generate' instrumentation and real inlining pass. Doing
- so makes profiling significantly cheaper and usually inlining
- faster on programs having large chains of nested wrapper functions.
+`-fearly-inlining'
+ Inline functions marked by `always_inline' and functions whose
+ body seems smaller than the function call overhead early before
+ doing `-fprofile-generate' instrumentation and real inlining pass.
+ Doing so makes profiling significantly cheaper and usually
+ inlining faster on programs having large chains of nested wrapper
+ functions.
Enabled by default.
-'-fipa-sra'
+`-fipa-sra'
Perform interprocedural scalar replacement of aggregates, removal
of unused parameters and replacement of parameters passed by
reference by parameters passed by value.
- Enabled at levels '-O2', '-O3' and '-Os'.
+ Enabled at levels `-O2', `-O3' and `-Os'.
-'-finline-limit=N'
+`-finline-limit=N'
By default, GCC limits the size of functions that can be inlined.
This flag allows coarse control of this limit. N is the size of
functions that can be inlined in number of pseudo instructions.
Inlining is actually controlled by a number of parameters, which
- may be specified individually by using '--param NAME=VALUE'. The
- '-finline-limit=N' option sets some of these parameters as follows:
+ may be specified individually by using `--param NAME=VALUE'. The
+ `-finline-limit=N' option sets some of these parameters as follows:
- 'max-inline-insns-single'
+ `max-inline-insns-single'
is set to N/2.
- 'max-inline-insns-auto'
+
+ `max-inline-insns-auto'
is set to N/2.
See below for a documentation of the individual parameters
controlling inlining and for the defaults of these parameters.
- _Note:_ there may be no value to '-finline-limit' that results in
+ _Note:_ there may be no value to `-finline-limit' that results in
default behavior.
_Note:_ pseudo instruction represents, in this particular context,
@@ -6986,62 +7050,62 @@ optimizations to be performed is desired.
represent a count of assembly instructions and as such its exact
meaning might change from one release to an another.
-'-fno-keep-inline-dllexport'
- This is a more fine-grained version of '-fkeep-inline-functions',
+`-fno-keep-inline-dllexport'
+ This is a more fine-grained version of `-fkeep-inline-functions',
which applies only to functions that are declared using the
- 'dllexport' attribute or declspec (*Note Declaring Attributes of
+ `dllexport' attribute or declspec (*Note Declaring Attributes of
Functions: Function Attributes.)
-'-fkeep-inline-functions'
- In C, emit 'static' functions that are declared 'inline' into the
+`-fkeep-inline-functions'
+ In C, emit `static' functions that are declared `inline' into the
object file, even if the function has been inlined into all of its
- callers. This switch does not affect functions using the 'extern
+ callers. This switch does not affect functions using the `extern
inline' extension in GNU C90. In C++, emit any and all inline
functions into the object file.
-'-fkeep-static-consts'
- Emit variables declared 'static const' when optimization isn't
+`-fkeep-static-consts'
+ Emit variables declared `static const' when optimization isn't
turned on, even if the variables aren't referenced.
GCC enables this option by default. If you want to force the
compiler to check if a variable is referenced, regardless of
whether or not optimization is turned on, use the
- '-fno-keep-static-consts' option.
+ `-fno-keep-static-consts' option.
-'-fmerge-constants'
+`-fmerge-constants'
Attempt to merge identical constants (string constants and
floating-point constants) across compilation units.
This option is the default for optimized compilation if the
- assembler and linker support it. Use '-fno-merge-constants' to
+ assembler and linker support it. Use `-fno-merge-constants' to
inhibit this behavior.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fmerge-all-constants'
+`-fmerge-all-constants'
Attempt to merge identical constants and identical variables.
- This option implies '-fmerge-constants'. In addition to
- '-fmerge-constants' this considers e.g. even constant initialized
+ This option implies `-fmerge-constants'. In addition to
+ `-fmerge-constants' this considers e.g. even constant initialized
arrays or initialized constant variables with integral or
floating-point types. Languages like C or C++ require each
variable, including multiple instances of the same variable in
recursive calls, to have distinct locations, so using this option
results in non-conforming behavior.
-'-fmodulo-sched'
+`-fmodulo-sched'
Perform swing modulo scheduling immediately before the first
scheduling pass. This pass looks at innermost loops and reorders
their instructions by overlapping different iterations.
-'-fmodulo-sched-allow-regmoves'
+`-fmodulo-sched-allow-regmoves'
Perform more aggressive SMS-based modulo scheduling with register
- moves allowed. By setting this flag certain anti-dependences edges
- are deleted, which triggers the generation of reg-moves based on
- the life-range analysis. This option is effective only with
- '-fmodulo-sched' enabled.
+ moves allowed. By setting this flag certain anti-dependences
+ edges are deleted, which triggers the generation of reg-moves
+ based on the life-range analysis. This option is effective only
+ with `-fmodulo-sched' enabled.
-'-fno-branch-count-reg'
+`-fno-branch-count-reg'
Do not use "decrement and branch" instructions on a count register,
but instead generate a sequence of instructions that decrement a
register, compare it against zero, then branch based upon the
@@ -7049,11 +7113,11 @@ optimizations to be performed is desired.
support such instructions, which include x86, PowerPC, IA-64 and
S/390.
- Enabled by default at '-O1' and higher.
+ Enabled by default at `-O1' and higher.
- The default is '-fbranch-count-reg'.
+ The default is `-fbranch-count-reg'.
-'-fno-function-cse'
+`-fno-function-cse'
Do not put function addresses in registers; make each instruction
that calls a constant function contain the function's address
explicitly.
@@ -7062,155 +7126,155 @@ optimizations to be performed is desired.
that alter the assembler output may be confused by the
optimizations performed when this option is not used.
- The default is '-ffunction-cse'
+ The default is `-ffunction-cse'
-'-fno-zero-initialized-in-bss'
- If the target supports a BSS section, GCC by default puts variables
- that are initialized to zero into BSS. This can save space in the
- resulting code.
+`-fno-zero-initialized-in-bss'
+ If the target supports a BSS section, GCC by default puts
+ variables that are initialized to zero into BSS. This can save
+ space in the resulting code.
This option turns off this behavior because some programs
explicitly rely on variables going to the data section--e.g., so
that the resulting executable can find the beginning of that
section and/or make assumptions based on that.
- The default is '-fzero-initialized-in-bss'.
+ The default is `-fzero-initialized-in-bss'.
-'-fthread-jumps'
+`-fthread-jumps'
Perform optimizations that check to see if a jump branches to a
location where another comparison subsumed by the first is found.
If so, the first branch is redirected to either the destination of
- the second branch or a point immediately following it, depending on
- whether the condition is known to be true or false.
+ the second branch or a point immediately following it, depending
+ on whether the condition is known to be true or false.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fsplit-wide-types'
- When using a type that occupies multiple registers, such as 'long
+`-fsplit-wide-types'
+ When using a type that occupies multiple registers, such as `long
long' on a 32-bit system, split the registers apart and allocate
them independently. This normally generates better code for those
types, but may make debugging more difficult.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fcse-follow-jumps'
+`-fcse-follow-jumps'
In common subexpression elimination (CSE), scan through jump
instructions when the target of the jump is not reached by any
- other path. For example, when CSE encounters an 'if' statement
- with an 'else' clause, CSE follows the jump when the condition
+ other path. For example, when CSE encounters an `if' statement
+ with an `else' clause, CSE follows the jump when the condition
tested is false.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fcse-skip-blocks'
- This is similar to '-fcse-follow-jumps', but causes CSE to follow
+`-fcse-skip-blocks'
+ This is similar to `-fcse-follow-jumps', but causes CSE to follow
jumps that conditionally skip over blocks. When CSE encounters a
- simple 'if' statement with no else clause, '-fcse-skip-blocks'
- causes CSE to follow the jump around the body of the 'if'.
+ simple `if' statement with no else clause, `-fcse-skip-blocks'
+ causes CSE to follow the jump around the body of the `if'.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-frerun-cse-after-loop'
+`-frerun-cse-after-loop'
Re-run common subexpression elimination after loop optimizations
are performed.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fgcse'
+`-fgcse'
Perform a global common subexpression elimination pass. This pass
also performs global constant and copy propagation.
_Note:_ When compiling a program using computed gotos, a GCC
extension, you may get better run-time performance if you disable
the global common subexpression elimination pass by adding
- '-fno-gcse' to the command line.
+ `-fno-gcse' to the command line.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fgcse-lm'
- When '-fgcse-lm' is enabled, global common subexpression
+`-fgcse-lm'
+ When `-fgcse-lm' is enabled, global common subexpression
elimination attempts to move loads that are only killed by stores
into themselves. This allows a loop containing a load/store
- sequence to be changed to a load outside the loop, and a copy/store
- within the loop.
+ sequence to be changed to a load outside the loop, and a
+ copy/store within the loop.
- Enabled by default when '-fgcse' is enabled.
+ Enabled by default when `-fgcse' is enabled.
-'-fgcse-sm'
- When '-fgcse-sm' is enabled, a store motion pass is run after
+`-fgcse-sm'
+ When `-fgcse-sm' is enabled, a store motion pass is run after
global common subexpression elimination. This pass attempts to
move stores out of loops. When used in conjunction with
- '-fgcse-lm', loops containing a load/store sequence can be changed
+ `-fgcse-lm', loops containing a load/store sequence can be changed
to a load before the loop and a store after the loop.
Not enabled at any optimization level.
-'-fgcse-las'
- When '-fgcse-las' is enabled, the global common subexpression
+`-fgcse-las'
+ When `-fgcse-las' is enabled, the global common subexpression
elimination pass eliminates redundant loads that come after stores
to the same memory location (both partial and full redundancies).
Not enabled at any optimization level.
-'-fgcse-after-reload'
- When '-fgcse-after-reload' is enabled, a redundant load elimination
+`-fgcse-after-reload'
+ When `-fgcse-after-reload' is enabled, a redundant load elimination
pass is performed after reload. The purpose of this pass is to
clean up redundant spilling.
-'-faggressive-loop-optimizations'
+`-faggressive-loop-optimizations'
This option tells the loop optimizer to use language constraints to
- derive bounds for the number of iterations of a loop. This assumes
- that loop code does not invoke undefined behavior by for example
- causing signed integer overflows or out-of-bound array accesses.
- The bounds for the number of iterations of a loop are used to guide
- loop unrolling and peeling and loop exit test optimizations. This
- option is enabled by default.
-
-'-funsafe-loop-optimizations'
- This option tells the loop optimizer to assume that loop indices do
- not overflow, and that loops with nontrivial exit condition are not
- infinite. This enables a wider range of loop optimizations even if
- the loop optimizer itself cannot prove that these assumptions are
- valid. If you use '-Wunsafe-loop-optimizations', the compiler
- warns you if it finds this kind of loop.
-
-'-fcrossjumping'
+ derive bounds for the number of iterations of a loop. This
+ assumes that loop code does not invoke undefined behavior by for
+ example causing signed integer overflows or out-of-bound array
+ accesses. The bounds for the number of iterations of a loop are
+ used to guide loop unrolling and peeling and loop exit test
+ optimizations. This option is enabled by default.
+
+`-funsafe-loop-optimizations'
+ This option tells the loop optimizer to assume that loop indices
+ do not overflow, and that loops with nontrivial exit condition are
+ not infinite. This enables a wider range of loop optimizations
+ even if the loop optimizer itself cannot prove that these
+ assumptions are valid. If you use `-Wunsafe-loop-optimizations',
+ the compiler warns you if it finds this kind of loop.
+
+`-fcrossjumping'
Perform cross-jumping transformation. This transformation unifies
- equivalent code and saves code size. The resulting code may or may
- not perform better than without cross-jumping.
+ equivalent code and saves code size. The resulting code may or
+ may not perform better than without cross-jumping.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fauto-inc-dec'
+`-fauto-inc-dec'
Combine increments or decrements of addresses with memory accesses.
This pass is always skipped on architectures that do not have
- instructions to support this. Enabled by default at '-O' and
+ instructions to support this. Enabled by default at `-O' and
higher on architectures that support this.
-'-fdce'
+`-fdce'
Perform dead code elimination (DCE) on RTL. Enabled by default at
- '-O' and higher.
+ `-O' and higher.
-'-fdse'
- Perform dead store elimination (DSE) on RTL. Enabled by default at
- '-O' and higher.
+`-fdse'
+ Perform dead store elimination (DSE) on RTL. Enabled by default
+ at `-O' and higher.
-'-fif-conversion'
+`-fif-conversion'
Attempt to transform conditional jumps into branch-less
- equivalents. This includes use of conditional moves, min, max, set
- flags and abs instructions, and some tricks doable by standard
- arithmetics. The use of conditional execution on chips where it is
- available is controlled by '-fif-conversion2'.
+ equivalents. This includes use of conditional moves, min, max,
+ set flags and abs instructions, and some tricks doable by standard
+ arithmetics. The use of conditional execution on chips where it
+ is available is controlled by `-fif-conversion2'.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fif-conversion2'
+`-fif-conversion2'
Use conditional execution (where available) to transform
conditional jumps into branch-less equivalents.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fdeclone-ctor-dtor'
+`-fdeclone-ctor-dtor'
The C++ ABI requires multiple entry points for constructors and
destructors: one for a base subobject, one for a complete object,
and one for a virtual destructor that calls operator delete
@@ -7219,440 +7283,441 @@ optimizations to be performed is desired.
function. With this option, the base and complete variants are
changed to be thunks that call a common implementation.
- Enabled by '-Os'.
+ Enabled by `-Os'.
-'-fdelete-null-pointer-checks'
+`-fdelete-null-pointer-checks'
Assume that programs cannot safely dereference null pointers, and
that no code or data element resides there. This enables simple
constant folding optimizations at all optimization levels. In
- addition, other optimization passes in GCC use this flag to control
- global dataflow analyses that eliminate useless checks for null
- pointers; these assume that if a pointer is checked after it has
- already been dereferenced, it cannot be null.
+ addition, other optimization passes in GCC use this flag to
+ control global dataflow analyses that eliminate useless checks for
+ null pointers; these assume that if a pointer is checked after it
+ has already been dereferenced, it cannot be null.
Note however that in some environments this assumption is not true.
- Use '-fno-delete-null-pointer-checks' to disable this optimization
+ Use `-fno-delete-null-pointer-checks' to disable this optimization
for programs that depend on that behavior.
Some targets, especially embedded ones, disable this option at all
- levels. Otherwise it is enabled at all levels: '-O0', '-O1',
- '-O2', '-O3', '-Os'. Passes that use the information are enabled
+ levels. Otherwise it is enabled at all levels: `-O0', `-O1',
+ `-O2', `-O3', `-Os'. Passes that use the information are enabled
independently at different optimization levels.
-'-fdevirtualize'
+`-fdevirtualize'
Attempt to convert calls to virtual functions to direct calls.
This is done both within a procedure and interprocedurally as part
- of indirect inlining ('-findirect-inlining') and interprocedural
- constant propagation ('-fipa-cp'). Enabled at levels '-O2', '-O3',
- '-Os'.
-
-'-fdevirtualize-speculatively'
- Attempt to convert calls to virtual functions to speculative direct
- calls. Based on the analysis of the type inheritance graph,
- determine for a given call the set of likely targets. If the set
- is small, preferably of size 1, change the call into a conditional
- deciding between direct and indirect calls. The speculative calls
- enable more optimizations, such as inlining. When they seem
- useless after further optimization, they are converted back into
- original form.
-
-'-fdevirtualize-at-ltrans'
+ of indirect inlining (`-findirect-inlining') and interprocedural
+ constant propagation (`-fipa-cp'). Enabled at levels `-O2',
+ `-O3', `-Os'.
+
+`-fdevirtualize-speculatively'
+ Attempt to convert calls to virtual functions to speculative
+ direct calls. Based on the analysis of the type inheritance
+ graph, determine for a given call the set of likely targets. If
+ the set is small, preferably of size 1, change the call into a
+ conditional deciding between direct and indirect calls. The
+ speculative calls enable more optimizations, such as inlining.
+ When they seem useless after further optimization, they are
+ converted back into original form.
+
+`-fdevirtualize-at-ltrans'
Stream extra information needed for aggressive devirtualization
when running the link-time optimizer in local transformation mode.
This option enables more devirtualization but significantly
- increases the size of streamed data. For this reason it is
+ increases the size of streamed data. For this reason it is
disabled by default.
-'-fexpensive-optimizations'
+`-fexpensive-optimizations'
Perform a number of minor optimizations that are relatively
expensive.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-free'
+`-free'
Attempt to remove redundant extension instructions. This is
especially helpful for the x86-64 architecture, which implicitly
zero-extends in 64-bit registers after writing to their lower
32-bit half.
- Enabled for Alpha, AArch64 and x86 at levels '-O2', '-O3', '-Os'.
+ Enabled for Alpha, AArch64 and x86 at levels `-O2', `-O3', `-Os'.
-'-fno-lifetime-dse'
+`-fno-lifetime-dse'
In C++ the value of an object is only affected by changes within
its lifetime: when the constructor begins, the object has an
indeterminate value, and any changes during the lifetime of the
object are dead when the object is destroyed. Normally dead store
- elimination will take advantage of this; if your code relies on the
- value of the object storage persisting beyond the lifetime of the
- object, you can use this flag to disable this optimization.
+ elimination will take advantage of this; if your code relies on
+ the value of the object storage persisting beyond the lifetime of
+ the object, you can use this flag to disable this optimization.
-'-flive-range-shrinkage'
+`-flive-range-shrinkage'
Attempt to decrease register pressure through register live range
shrinkage. This is helpful for fast processors with small or
moderate size register sets.
-'-fira-algorithm=ALGORITHM'
+`-fira-algorithm=ALGORITHM'
Use the specified coloring algorithm for the integrated register
- allocator. The ALGORITHM argument can be 'priority', which
- specifies Chow's priority coloring, or 'CB', which specifies
+ allocator. The ALGORITHM argument can be `priority', which
+ specifies Chow's priority coloring, or `CB', which specifies
Chaitin-Briggs coloring. Chaitin-Briggs coloring is not
implemented for all architectures, but for those targets that do
support it, it is the default because it generates better code.
-'-fira-region=REGION'
+`-fira-region=REGION'
Use specified regions for the integrated register allocator. The
REGION argument should be one of the following:
- 'all'
+ `all'
Use all loops as register allocation regions. This can give
the best results for machines with a small and/or irregular
register set.
- 'mixed'
- Use all loops except for loops with small register pressure as
- the regions. This value usually gives the best results in
+ `mixed'
+ Use all loops except for loops with small register pressure
+ as the regions. This value usually gives the best results in
most cases and for most architectures, and is enabled by
- default when compiling with optimization for speed ('-O',
- '-O2', ...).
+ default when compiling with optimization for speed (`-O',
+ `-O2', ...).
- 'one'
+ `one'
Use all functions as a single region. This typically results
- in the smallest code size, and is enabled by default for '-Os'
- or '-O0'.
+ in the smallest code size, and is enabled by default for
+ `-Os' or `-O0'.
+
-'-fira-hoist-pressure'
+`-fira-hoist-pressure'
Use IRA to evaluate register pressure in the code hoisting pass for
decisions to hoist expressions. This option usually results in
smaller code, but it can slow the compiler down.
- This option is enabled at level '-Os' for all targets.
+ This option is enabled at level `-Os' for all targets.
-'-fira-loop-pressure'
+`-fira-loop-pressure'
Use IRA to evaluate register pressure in loops for decisions to
- move loop invariants. This option usually results in generation of
- faster and smaller code on machines with large register files (>=
- 32 registers), but it can slow the compiler down.
+ move loop invariants. This option usually results in generation
+ of faster and smaller code on machines with large register files
+ (>= 32 registers), but it can slow the compiler down.
- This option is enabled at level '-O3' for some targets.
+ This option is enabled at level `-O3' for some targets.
-'-fno-ira-share-save-slots'
+`-fno-ira-share-save-slots'
Disable sharing of stack slots used for saving call-used hard
registers living through a call. Each hard register gets a
separate stack slot, and as a result function stack frames are
larger.
-'-fno-ira-share-spill-slots'
+`-fno-ira-share-spill-slots'
Disable sharing of stack slots allocated for pseudo-registers.
Each pseudo-register that does not get a hard register gets a
separate stack slot, and as a result function stack frames are
larger.
-'-fira-verbose=N'
+`-fira-verbose=N'
Control the verbosity of the dump file for the integrated register
allocator. The default value is 5. If the value N is greater or
equal to 10, the dump output is sent to stderr using the same
format as N minus 10.
-'-flra-remat'
- Enable CFG-sensitive rematerialization in LRA. Instead of loading
+`-flra-remat'
+ Enable CFG-sensitive rematerialization in LRA. Instead of loading
values of spilled pseudos, LRA tries to rematerialize (recalculate)
values if it is profitable.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fdelayed-branch'
+`-fdelayed-branch'
If supported for the target machine, attempt to reorder
instructions to exploit instruction slots available after delayed
branch instructions.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fschedule-insns'
+`-fschedule-insns'
If supported for the target machine, attempt to reorder
instructions to eliminate execution stalls due to required data
being unavailable. This helps machines that have slow floating
- point or memory load instructions by allowing other instructions to
- be issued until the result of the load or floating-point
+ point or memory load instructions by allowing other instructions
+ to be issued until the result of the load or floating-point
instruction is required.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-fschedule-insns2'
- Similar to '-fschedule-insns', but requests an additional pass of
+`-fschedule-insns2'
+ Similar to `-fschedule-insns', but requests an additional pass of
instruction scheduling after register allocation has been done.
This is especially useful on machines with a relatively small
number of registers and where memory load instructions take more
than one cycle.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fno-sched-interblock'
+`-fno-sched-interblock'
Don't schedule instructions across basic blocks. This is normally
enabled by default when scheduling before register allocation, i.e.
- with '-fschedule-insns' or at '-O2' or higher.
+ with `-fschedule-insns' or at `-O2' or higher.
-'-fno-sched-spec'
+`-fno-sched-spec'
Don't allow speculative motion of non-load instructions. This is
normally enabled by default when scheduling before register
- allocation, i.e. with '-fschedule-insns' or at '-O2' or higher.
+ allocation, i.e. with `-fschedule-insns' or at `-O2' or higher.
-'-fsched-pressure'
+`-fsched-pressure'
Enable register pressure sensitive insn scheduling before register
allocation. This only makes sense when scheduling before register
- allocation is enabled, i.e. with '-fschedule-insns' or at '-O2' or
+ allocation is enabled, i.e. with `-fschedule-insns' or at `-O2' or
higher. Usage of this option can improve the generated code and
decrease its size by preventing register pressure increase above
the number of available hard registers and subsequent spills in
register allocation.
-'-fsched-spec-load'
+`-fsched-spec-load'
Allow speculative motion of some load instructions. This only
makes sense when scheduling before register allocation, i.e. with
- '-fschedule-insns' or at '-O2' or higher.
+ `-fschedule-insns' or at `-O2' or higher.
-'-fsched-spec-load-dangerous'
+`-fsched-spec-load-dangerous'
Allow speculative motion of more load instructions. This only
makes sense when scheduling before register allocation, i.e. with
- '-fschedule-insns' or at '-O2' or higher.
+ `-fschedule-insns' or at `-O2' or higher.
-'-fsched-stalled-insns'
-'-fsched-stalled-insns=N'
+`-fsched-stalled-insns'
+`-fsched-stalled-insns=N'
Define how many insns (if any) can be moved prematurely from the
queue of stalled insns into the ready list during the second
- scheduling pass. '-fno-sched-stalled-insns' means that no insns
- are moved prematurely, '-fsched-stalled-insns=0' means there is no
+ scheduling pass. `-fno-sched-stalled-insns' means that no insns
+ are moved prematurely, `-fsched-stalled-insns=0' means there is no
limit on how many queued insns can be moved prematurely.
- '-fsched-stalled-insns' without a value is equivalent to
- '-fsched-stalled-insns=1'.
+ `-fsched-stalled-insns' without a value is equivalent to
+ `-fsched-stalled-insns=1'.
-'-fsched-stalled-insns-dep'
-'-fsched-stalled-insns-dep=N'
+`-fsched-stalled-insns-dep'
+`-fsched-stalled-insns-dep=N'
Define how many insn groups (cycles) are examined for a dependency
on a stalled insn that is a candidate for premature removal from
the queue of stalled insns. This has an effect only during the
- second scheduling pass, and only if '-fsched-stalled-insns' is
- used. '-fno-sched-stalled-insns-dep' is equivalent to
- '-fsched-stalled-insns-dep=0'. '-fsched-stalled-insns-dep' without
- a value is equivalent to '-fsched-stalled-insns-dep=1'.
+ second scheduling pass, and only if `-fsched-stalled-insns' is
+ used. `-fno-sched-stalled-insns-dep' is equivalent to
+ `-fsched-stalled-insns-dep=0'. `-fsched-stalled-insns-dep'
+ without a value is equivalent to `-fsched-stalled-insns-dep=1'.
-'-fsched2-use-superblocks'
+`-fsched2-use-superblocks'
When scheduling after register allocation, use superblock
scheduling. This allows motion across basic block boundaries,
- resulting in faster schedules. This option is experimental, as not
- all machine descriptions used by GCC model the CPU closely enough
- to avoid unreliable results from the algorithm.
+ resulting in faster schedules. This option is experimental, as
+ not all machine descriptions used by GCC model the CPU closely
+ enough to avoid unreliable results from the algorithm.
This only makes sense when scheduling after register allocation,
- i.e. with '-fschedule-insns2' or at '-O2' or higher.
+ i.e. with `-fschedule-insns2' or at `-O2' or higher.
-'-fsched-group-heuristic'
+`-fsched-group-heuristic'
Enable the group heuristic in the scheduler. This heuristic favors
the instruction that belongs to a schedule group. This is enabled
- by default when scheduling is enabled, i.e. with '-fschedule-insns'
- or '-fschedule-insns2' or at '-O2' or higher.
+ by default when scheduling is enabled, i.e. with `-fschedule-insns'
+ or `-fschedule-insns2' or at `-O2' or higher.
-'-fsched-critical-path-heuristic'
+`-fsched-critical-path-heuristic'
Enable the critical-path heuristic in the scheduler. This
heuristic favors instructions on the critical path. This is
enabled by default when scheduling is enabled, i.e. with
- '-fschedule-insns' or '-fschedule-insns2' or at '-O2' or higher.
+ `-fschedule-insns' or `-fschedule-insns2' or at `-O2' or higher.
-'-fsched-spec-insn-heuristic'
+`-fsched-spec-insn-heuristic'
Enable the speculative instruction heuristic in the scheduler.
This heuristic favors speculative instructions with greater
- dependency weakness. This is enabled by default when scheduling is
- enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or at
- '-O2' or higher.
+ dependency weakness. This is enabled by default when scheduling
+ is enabled, i.e. with `-fschedule-insns' or `-fschedule-insns2'
+ or at `-O2' or higher.
-'-fsched-rank-heuristic'
+`-fsched-rank-heuristic'
Enable the rank heuristic in the scheduler. This heuristic favors
the instruction belonging to a basic block with greater size or
frequency. This is enabled by default when scheduling is enabled,
- i.e. with '-fschedule-insns' or '-fschedule-insns2' or at '-O2' or
- higher.
+ i.e. with `-fschedule-insns' or `-fschedule-insns2' or at `-O2'
+ or higher.
-'-fsched-last-insn-heuristic'
+`-fsched-last-insn-heuristic'
Enable the last-instruction heuristic in the scheduler. This
- heuristic favors the instruction that is less dependent on the last
- instruction scheduled. This is enabled by default when scheduling
- is enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or
- at '-O2' or higher.
+ heuristic favors the instruction that is less dependent on the
+ last instruction scheduled. This is enabled by default when
+ scheduling is enabled, i.e. with `-fschedule-insns' or
+ `-fschedule-insns2' or at `-O2' or higher.
-'-fsched-dep-count-heuristic'
+`-fsched-dep-count-heuristic'
Enable the dependent-count heuristic in the scheduler. This
heuristic favors the instruction that has more instructions
depending on it. This is enabled by default when scheduling is
- enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or at
- '-O2' or higher.
+ enabled, i.e. with `-fschedule-insns' or `-fschedule-insns2' or
+ at `-O2' or higher.
-'-freschedule-modulo-scheduled-loops'
- Modulo scheduling is performed before traditional scheduling. If a
- loop is modulo scheduled, later scheduling passes may change its
+`-freschedule-modulo-scheduled-loops'
+ Modulo scheduling is performed before traditional scheduling. If
+ a loop is modulo scheduled, later scheduling passes may change its
schedule. Use this option to control that behavior.
-'-fselective-scheduling'
+`-fselective-scheduling'
Schedule instructions using selective scheduling algorithm.
Selective scheduling runs instead of the first scheduler pass.
-'-fselective-scheduling2'
+`-fselective-scheduling2'
Schedule instructions using selective scheduling algorithm.
Selective scheduling runs instead of the second scheduler pass.
-'-fsel-sched-pipelining'
+`-fsel-sched-pipelining'
Enable software pipelining of innermost loops during selective
scheduling. This option has no effect unless one of
- '-fselective-scheduling' or '-fselective-scheduling2' is turned on.
+ `-fselective-scheduling' or `-fselective-scheduling2' is turned on.
-'-fsel-sched-pipelining-outer-loops'
+`-fsel-sched-pipelining-outer-loops'
When pipelining loops during selective scheduling, also pipeline
outer loops. This option has no effect unless
- '-fsel-sched-pipelining' is turned on.
+ `-fsel-sched-pipelining' is turned on.
-'-fsemantic-interposition'
+`-fsemantic-interposition'
Some object formats, like ELF, allow interposing of symbols by the
- dynamic linker. This means that for symbols exported from the DSO,
- the compiler cannot perform interprocedural propagation, inlining
- and other optimizations in anticipation that the function or
- variable in question may change. While this feature is useful, for
- example, to rewrite memory allocation functions by a debugging
- implementation, it is expensive in the terms of code quality. With
- '-fno-semantic-interposition' the compiler assumes that if
+ dynamic linker. This means that for symbols exported from the
+ DSO, the compiler cannot perform interprocedural propagation,
+ inlining and other optimizations in anticipation that the function
+ or variable in question may change. While this feature is useful,
+ for example, to rewrite memory allocation functions by a debugging
+ implementation, it is expensive in the terms of code quality.
+ With `-fno-semantic-interposition' the compiler assumes that if
interposition happens for functions the overwriting function will
- have precisely the same semantics (and side effects). Similarly if
- interposition happens for variables, the constructor of the
- variable will be the same. The flag has no effect for functions
+ have precisely the same semantics (and side effects). Similarly
+ if interposition happens for variables, the constructor of the
+ variable will be the same. The flag has no effect for functions
explicitly declared inline (where it is never allowed for
interposition to change semantics) and for symbols explicitly
declared weak.
-'-fshrink-wrap'
- Emit function prologues only before parts of the function that need
- it, rather than at the top of the function. This flag is enabled
- by default at '-O' and higher.
+`-fshrink-wrap'
+ Emit function prologues only before parts of the function that
+ need it, rather than at the top of the function. This flag is
+ enabled by default at `-O' and higher.
-'-fcaller-saves'
+`-fcaller-saves'
Enable allocation of values to registers that are clobbered by
function calls, by emitting extra instructions to save and restore
- the registers around such calls. Such allocation is done only when
- it seems to result in better code.
+ the registers around such calls. Such allocation is done only
+ when it seems to result in better code.
This option is always enabled by default on certain machines,
usually those which have no call-preserved registers to use
instead.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fcombine-stack-adjustments'
+`-fcombine-stack-adjustments'
Tracks stack adjustments (pushes and pops) and stack memory
references and then tries to find ways to combine them.
- Enabled by default at '-O1' and higher.
+ Enabled by default at `-O1' and higher.
-'-fipa-ra'
- Use caller save registers for allocation if those registers are not
- used by any called function. In that case it is not necessary to
- save and restore them around calls. This is only possible if
+`-fipa-ra'
+ Use caller save registers for allocation if those registers are
+ not used by any called function. In that case it is not necessary
+ to save and restore them around calls. This is only possible if
called functions are part of same compilation unit as current
function and they are compiled before it.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fconserve-stack'
+`-fconserve-stack'
Attempt to minimize stack usage. The compiler attempts to use less
stack space, even if that makes the program slower. This option
- implies setting the 'large-stack-frame' parameter to 100 and the
- 'large-stack-frame-growth' parameter to 400.
+ implies setting the `large-stack-frame' parameter to 100 and the
+ `large-stack-frame-growth' parameter to 400.
-'-ftree-reassoc'
- Perform reassociation on trees. This flag is enabled by default at
- '-O' and higher.
+`-ftree-reassoc'
+ Perform reassociation on trees. This flag is enabled by default
+ at `-O' and higher.
-'-ftree-pre'
+`-ftree-pre'
Perform partial redundancy elimination (PRE) on trees. This flag
- is enabled by default at '-O2' and '-O3'.
+ is enabled by default at `-O2' and `-O3'.
-'-ftree-partial-pre'
+`-ftree-partial-pre'
Make partial redundancy elimination (PRE) more aggressive. This
- flag is enabled by default at '-O3'.
+ flag is enabled by default at `-O3'.
-'-ftree-forwprop'
+`-ftree-forwprop'
Perform forward propagation on trees. This flag is enabled by
- default at '-O' and higher.
+ default at `-O' and higher.
-'-ftree-fre'
+`-ftree-fre'
Perform full redundancy elimination (FRE) on trees. The difference
- between FRE and PRE is that FRE only considers expressions that are
- computed on all paths leading to the redundant computation. This
- analysis is faster than PRE, though it exposes fewer redundancies.
- This flag is enabled by default at '-O' and higher.
+ between FRE and PRE is that FRE only considers expressions that
+ are computed on all paths leading to the redundant computation.
+ This analysis is faster than PRE, though it exposes fewer
+ redundancies. This flag is enabled by default at `-O' and higher.
-'-ftree-phiprop'
+`-ftree-phiprop'
Perform hoisting of loads from conditional pointers on trees. This
- pass is enabled by default at '-O' and higher.
+ pass is enabled by default at `-O' and higher.
-'-fhoist-adjacent-loads'
+`-fhoist-adjacent-loads'
Speculatively hoist loads from both branches of an if-then-else if
- the loads are from adjacent locations in the same structure and the
- target architecture has a conditional move instruction. This flag
- is enabled by default at '-O2' and higher.
+ the loads are from adjacent locations in the same structure and
+ the target architecture has a conditional move instruction. This
+ flag is enabled by default at `-O2' and higher.
-'-ftree-copy-prop'
+`-ftree-copy-prop'
Perform copy propagation on trees. This pass eliminates
unnecessary copy operations. This flag is enabled by default at
- '-O' and higher.
+ `-O' and higher.
-'-fipa-pure-const'
+`-fipa-pure-const'
Discover which functions are pure or constant. Enabled by default
- at '-O' and higher.
+ at `-O' and higher.
-'-fipa-reference'
+`-fipa-reference'
Discover which static variables do not escape the compilation unit.
- Enabled by default at '-O' and higher.
+ Enabled by default at `-O' and higher.
-'-fipa-pta'
+`-fipa-pta'
Perform interprocedural pointer analysis and interprocedural
modification and reference analysis. This option can cause
- excessive memory and compile-time usage on large compilation units.
- It is not enabled by default at any optimization level.
+ excessive memory and compile-time usage on large compilation
+ units. It is not enabled by default at any optimization level.
-'-fipa-profile'
+`-fipa-profile'
Perform interprocedural profile propagation. The functions called
- only from cold functions are marked as cold. Also functions
- executed once (such as 'cold', 'noreturn', static constructors or
- destructors) are identified. Cold functions and loop less parts of
+ only from cold functions are marked as cold. Also functions
+ executed once (such as `cold', `noreturn', static constructors or
+ destructors) are identified. Cold functions and loop less parts of
functions executed once are then optimized for size. Enabled by
- default at '-O' and higher.
+ default at `-O' and higher.
-'-fipa-cp'
+`-fipa-cp'
Perform interprocedural constant propagation. This optimization
analyzes the program to determine when values passed to functions
are constants and then optimizes accordingly. This optimization
can substantially increase performance if the application has
constants passed to functions. This flag is enabled by default at
- '-O2', '-Os' and '-O3'.
+ `-O2', `-Os' and `-O3'.
-'-fipa-cp-clone'
+`-fipa-cp-clone'
Perform function cloning to make interprocedural constant
propagation stronger. When enabled, interprocedural constant
propagation performs function cloning when externally visible
function can be called with constant arguments. Because this
optimization can create multiple copies of functions, it may
- significantly increase code size (see '--param
+ significantly increase code size (see `--param
ipcp-unit-growth=VALUE'). This flag is enabled by default at
- '-O3'.
+ `-O3'.
-'-fipa-cp-alignment'
+`-fipa-cp-alignment'
When enabled, this optimization propagates alignment of function
parameters to support better vectorization and string operations.
- This flag is enabled by default at '-O2' and '-Os'. It requires
- that '-fipa-cp' is enabled.
+ This flag is enabled by default at `-O2' and `-Os'. It requires
+ that `-fipa-cp' is enabled.
-'-fipa-icf'
+`-fipa-icf'
Perform Identical Code Folding for functions and read-only
variables. The optimization reduces code size and may disturb
unwind stacks by replacing a function by equivalent one with a
- different name. The optimization works more effectively with link
+ different name. The optimization works more effectively with link
time optimization enabled.
Nevertheless the behavior is similar to Gold Linker ICF
@@ -7660,97 +7725,97 @@ optimizations to be performed is desired.
optimizations are not same - there are equivalences that are found
only by GCC and equivalences found only by Gold.
- This flag is enabled by default at '-O2' and '-Os'.
+ This flag is enabled by default at `-O2' and `-Os'.
-'-fisolate-erroneous-paths-dereference'
+`-fisolate-erroneous-paths-dereference'
Detect paths that trigger erroneous or undefined behavior due to
dereferencing a null pointer. Isolate those paths from the main
control flow and turn the statement with erroneous or undefined
- behavior into a trap. This flag is enabled by default at '-O2' and
- higher.
+ behavior into a trap. This flag is enabled by default at `-O2'
+ and higher.
-'-fisolate-erroneous-paths-attribute'
+`-fisolate-erroneous-paths-attribute'
Detect paths that trigger erroneous or undefined behavior due a
- null value being used in a way forbidden by a 'returns_nonnull' or
- 'nonnull' attribute. Isolate those paths from the main control
+ null value being used in a way forbidden by a `returns_nonnull' or
+ `nonnull' attribute. Isolate those paths from the main control
flow and turn the statement with erroneous or undefined behavior
into a trap. This is not currently enabled, but may be enabled by
- '-O2' in the future.
+ `-O2' in the future.
-'-ftree-sink'
- Perform forward store motion on trees. This flag is enabled by
- default at '-O' and higher.
+`-ftree-sink'
+ Perform forward store motion on trees. This flag is enabled by
+ default at `-O' and higher.
-'-ftree-bit-ccp'
+`-ftree-bit-ccp'
Perform sparse conditional bit constant propagation on trees and
propagate pointer alignment information. This pass only operates
- on local scalar variables and is enabled by default at '-O' and
- higher. It requires that '-ftree-ccp' is enabled.
+ on local scalar variables and is enabled by default at `-O' and
+ higher. It requires that `-ftree-ccp' is enabled.
-'-ftree-ccp'
+`-ftree-ccp'
Perform sparse conditional constant propagation (CCP) on trees.
- This pass only operates on local scalar variables and is enabled by
- default at '-O' and higher.
+ This pass only operates on local scalar variables and is enabled
+ by default at `-O' and higher.
-'-fssa-phiopt'
+`-fssa-phiopt'
Perform pattern matching on SSA PHI nodes to optimize conditional
- code. This pass is enabled by default at '-O' and higher.
+ code. This pass is enabled by default at `-O' and higher.
-'-ftree-switch-conversion'
+`-ftree-switch-conversion'
Perform conversion of simple initializations in a switch to
initializations from a scalar array. This flag is enabled by
- default at '-O2' and higher.
+ default at `-O2' and higher.
-'-ftree-tail-merge'
+`-ftree-tail-merge'
Look for identical code sequences. When found, replace one with a
jump to the other. This optimization is known as tail merging or
- cross jumping. This flag is enabled by default at '-O2' and
+ cross jumping. This flag is enabled by default at `-O2' and
higher. The compilation time in this pass can be limited using
- 'max-tail-merge-comparisons' parameter and
- 'max-tail-merge-iterations' parameter.
+ `max-tail-merge-comparisons' parameter and
+ `max-tail-merge-iterations' parameter.
-'-ftree-dce'
- Perform dead code elimination (DCE) on trees. This flag is enabled
- by default at '-O' and higher.
+`-ftree-dce'
+ Perform dead code elimination (DCE) on trees. This flag is
+ enabled by default at `-O' and higher.
-'-ftree-builtin-call-dce'
+`-ftree-builtin-call-dce'
Perform conditional dead code elimination (DCE) for calls to
- built-in functions that may set 'errno' but are otherwise
- side-effect free. This flag is enabled by default at '-O2' and
- higher if '-Os' is not also specified.
+ built-in functions that may set `errno' but are otherwise
+ side-effect free. This flag is enabled by default at `-O2' and
+ higher if `-Os' is not also specified.
-'-ftree-dominator-opts'
+`-ftree-dominator-opts'
Perform a variety of simple scalar cleanups (constant/copy
propagation, redundancy elimination, range propagation and
expression simplification) based on a dominator tree traversal.
- This also performs jump threading (to reduce jumps to jumps). This
- flag is enabled by default at '-O' and higher.
+ This also performs jump threading (to reduce jumps to jumps). This
+ flag is enabled by default at `-O' and higher.
-'-ftree-dse'
+`-ftree-dse'
Perform dead store elimination (DSE) on trees. A dead store is a
store into a memory location that is later overwritten by another
store without any intervening loads. In this case the earlier
- store can be deleted. This flag is enabled by default at '-O' and
+ store can be deleted. This flag is enabled by default at `-O' and
higher.
-'-ftree-ch'
+`-ftree-ch'
Perform loop header copying on trees. This is beneficial since it
increases effectiveness of code motion optimizations. It also
- saves one jump. This flag is enabled by default at '-O' and
- higher. It is not enabled for '-Os', since it usually increases
+ saves one jump. This flag is enabled by default at `-O' and
+ higher. It is not enabled for `-Os', since it usually increases
code size.
-'-ftree-loop-optimize'
+`-ftree-loop-optimize'
Perform loop optimizations on trees. This flag is enabled by
- default at '-O' and higher.
+ default at `-O' and higher.
-'-ftree-loop-linear'
+`-ftree-loop-linear'
Perform loop interchange transformations on tree. Same as
- '-floop-interchange'. To use this code transformation, GCC has to
- be configured with '--with-isl' to enable the Graphite loop
+ `-floop-interchange'. To use this code transformation, GCC has to
+ be configured with `--with-isl' to enable the Graphite loop
transformation infrastructure.
-'-floop-interchange'
+`-floop-interchange'
Perform loop interchange transformations on loops. Interchanging
two nested loops switches the inner and outer loops. For example,
given a loop like:
@@ -7765,21 +7830,21 @@ optimizations to be performed is desired.
A(J, I) = A(J, I) * C
ENDDO
ENDDO
- which can be beneficial when 'N' is larger than the caches, because
- in Fortran, the elements of an array are stored in memory
+ which can be beneficial when `N' is larger than the caches,
+ because in Fortran, the elements of an array are stored in memory
contiguously by column, and the original loop iterates over rows,
potentially creating at each access a cache miss. This
optimization applies to all the languages supported by GCC and is
not limited to Fortran. To use this code transformation, GCC has
- to be configured with '--with-isl' to enable the Graphite loop
+ to be configured with `--with-isl' to enable the Graphite loop
transformation infrastructure.
-'-floop-strip-mine'
+`-floop-strip-mine'
Perform loop strip mining transformations on loops. Strip mining
splits a loop into two nested loops. The outer loop has strides
equal to the strip size and the inner loop has strides of the
original loop within a strip. The strip length can be changed
- using the 'loop-block-tile-size' parameter. For example, given a
+ using the `loop-block-tile-size' parameter. For example, given a
loop like:
DO I = 1, N
A(I) = A(I) + C
@@ -7790,16 +7855,16 @@ optimizations to be performed is desired.
A(I) = A(I) + C
ENDDO
ENDDO
- This optimization applies to all the languages supported by GCC and
- is not limited to Fortran. To use this code transformation, GCC
- has to be configured with '--with-isl' to enable the Graphite loop
- transformation infrastructure.
+ This optimization applies to all the languages supported by GCC
+ and is not limited to Fortran. To use this code transformation,
+ GCC has to be configured with `--with-isl' to enable the Graphite
+ loop transformation infrastructure.
-'-floop-block'
+`-floop-block'
Perform loop blocking transformations on loops. Blocking strip
mines each loop in the loop nest such that the memory accesses of
the element loops fit inside caches. The strip length can be
- changed using the 'loop-block-tile-size' parameter. For example,
+ changed using the `loop-block-tile-size' parameter. For example,
given a loop like:
DO I = 1, N
DO J = 1, M
@@ -7816,52 +7881,53 @@ optimizations to be performed is desired.
ENDDO
ENDDO
ENDDO
- which can be beneficial when 'M' is larger than the caches, because
- the innermost loop iterates over a smaller amount of data which can
- be kept in the caches. This optimization applies to all the
- languages supported by GCC and is not limited to Fortran. To use
- this code transformation, GCC has to be configured with
- '--with-isl' to enable the Graphite loop transformation
+ which can be beneficial when `M' is larger than the caches,
+ because the innermost loop iterates over a smaller amount of data
+ which can be kept in the caches. This optimization applies to all
+ the languages supported by GCC and is not limited to Fortran. To
+ use this code transformation, GCC has to be configured with
+ `--with-isl' to enable the Graphite loop transformation
infrastructure.
-'-fgraphite-identity'
- Enable the identity transformation for graphite. For every SCoP we
- generate the polyhedral representation and transform it back to
- gimple. Using '-fgraphite-identity' we can check the costs or
+`-fgraphite-identity'
+ Enable the identity transformation for graphite. For every SCoP
+ we generate the polyhedral representation and transform it back to
+ gimple. Using `-fgraphite-identity' we can check the costs or
benefits of the GIMPLE -> GRAPHITE -> GIMPLE transformation. Some
- minimal optimizations are also performed by the code generator ISL,
- like index splitting and dead code elimination in loops.
+ minimal optimizations are also performed by the code generator
+ ISL, like index splitting and dead code elimination in loops.
-'-floop-nest-optimize'
+`-floop-nest-optimize'
Enable the ISL based loop nest optimizer. This is a generic loop
nest optimizer based on the Pluto optimization algorithms. It
calculates a loop structure optimized for data-locality and
parallelism. This option is experimental.
-'-floop-unroll-and-jam'
+`-floop-unroll-and-jam'
Enable unroll and jam for the ISL based loop nest optimizer. The
- unroll factor can be changed using the 'loop-unroll-jam-size'
+ unroll factor can be changed using the `loop-unroll-jam-size'
parameter. The unrolled dimension (counting from the most inner
- one) can be changed using the 'loop-unroll-jam-depth' parameter. .
+ one) can be changed using the `loop-unroll-jam-depth' parameter.
+ .
-'-floop-parallelize-all'
+`-floop-parallelize-all'
Use the Graphite data dependence analysis to identify loops that
can be parallelized. Parallelize all the loops that can be
analyzed to not contain loop carried dependences without checking
that it is profitable to parallelize the loops.
-'-fcheck-data-deps'
+`-fcheck-data-deps'
Compare the results of several data dependence analyzers. This
option is used for debugging the data dependence analyzers.
-'-ftree-loop-if-convert'
+`-ftree-loop-if-convert'
Attempt to transform conditional jumps in the innermost loops to
branch-less equivalents. The intent is to remove control-flow from
the innermost loops in order to improve the ability of the
vectorization pass to handle these loops. This is enabled by
default if vectorization is enabled.
-'-ftree-loop-if-convert-stores'
+`-ftree-loop-if-convert-stores'
Attempt to also if-convert conditional jumps containing memory
writes. This transformation can be unsafe for multi-threaded
programs as it transforms conditional memory writes into
@@ -7874,11 +7940,11 @@ optimizations to be performed is desired.
A[i] = cond ? expr : A[i];
potentially producing data races.
-'-ftree-loop-distribution'
- Perform loop distribution. This flag can improve cache performance
- on big loop bodies and allow further loop optimizations, like
- parallelization or vectorization, to take place. For example, the
- loop
+`-ftree-loop-distribution'
+ Perform loop distribution. This flag can improve cache
+ performance on big loop bodies and allow further loop
+ optimizations, like parallelization or vectorization, to take
+ place. For example, the loop
DO I = 1, N
A(I) = B(I) + C
D(I) = E(I) * F
@@ -7891,12 +7957,12 @@ optimizations to be performed is desired.
D(I) = E(I) * F
ENDDO
-'-ftree-loop-distribute-patterns'
+`-ftree-loop-distribute-patterns'
Perform loop distribution of patterns that can be code generated
- with calls to a library. This flag is enabled by default at '-O3'.
+ with calls to a library. This flag is enabled by default at `-O3'.
- This pass distributes the initialization loops and generates a call
- to memset zero. For example, the loop
+ This pass distributes the initialization loops and generates a
+ call to memset zero. For example, the loop
DO I = 1, N
A(I) = 0
B(I) = A(I) + I
@@ -7911,161 +7977,161 @@ optimizations to be performed is desired.
and the initialization loop is transformed into a call to memset
zero.
-'-ftree-loop-im'
+`-ftree-loop-im'
Perform loop invariant motion on trees. This pass moves only
invariants that are hard to handle at RTL level (function calls,
operations that expand to nontrivial sequences of insns). With
- '-funswitch-loops' it also moves operands of conditions that are
+ `-funswitch-loops' it also moves operands of conditions that are
invariant out of the loop, so that we can use just trivial
invariantness analysis in loop unswitching. The pass also includes
store motion.
-'-ftree-loop-ivcanon'
+`-ftree-loop-ivcanon'
Create a canonical counter for number of iterations in loops for
which determining number of iterations requires complicated
analysis. Later optimizations then may determine the number
easily. Useful especially in connection with unrolling.
-'-fivopts'
+`-fivopts'
Perform induction variable optimizations (strength reduction,
induction variable merging and induction variable elimination) on
trees.
-'-ftree-parallelize-loops=n'
+`-ftree-parallelize-loops=n'
Parallelize loops, i.e., split their iteration space to run in n
threads. This is only possible for loops whose iterations are
independent and can be arbitrarily reordered. The optimization is
only profitable on multiprocessor machines, for loops that are
CPU-intensive, rather than constrained e.g. by memory bandwidth.
- This option implies '-pthread', and thus is only supported on
- targets that have support for '-pthread'.
+ This option implies `-pthread', and thus is only supported on
+ targets that have support for `-pthread'.
-'-ftree-pta'
+`-ftree-pta'
Perform function-local points-to analysis on trees. This flag is
- enabled by default at '-O' and higher.
+ enabled by default at `-O' and higher.
-'-ftree-sra'
+`-ftree-sra'
Perform scalar replacement of aggregates. This pass replaces
structure references with scalars to prevent committing structures
- to memory too early. This flag is enabled by default at '-O' and
+ to memory too early. This flag is enabled by default at `-O' and
higher.
-'-ftree-copyrename'
+`-ftree-copyrename'
Perform copy renaming on trees. This pass attempts to rename
compiler temporaries to other variables at copy locations, usually
resulting in variable names which more closely resemble the
- original variables. This flag is enabled by default at '-O' and
+ original variables. This flag is enabled by default at `-O' and
higher.
-'-ftree-coalesce-inlined-vars'
- Tell the copyrename pass (see '-ftree-copyrename') to attempt to
+`-ftree-coalesce-inlined-vars'
+ Tell the copyrename pass (see `-ftree-copyrename') to attempt to
combine small user-defined variables too, but only if they are
inlined from other functions. It is a more limited form of
- '-ftree-coalesce-vars'. This may harm debug information of such
+ `-ftree-coalesce-vars'. This may harm debug information of such
inlined variables, but it keeps variables of the inlined-into
function apart from each other, such that they are more likely to
contain the expected values in a debugging session.
-'-ftree-coalesce-vars'
- Tell the copyrename pass (see '-ftree-copyrename') to attempt to
+`-ftree-coalesce-vars'
+ Tell the copyrename pass (see `-ftree-copyrename') to attempt to
combine small user-defined variables too, instead of just compiler
temporaries. This may severely limit the ability to debug an
- optimized program compiled with '-fno-var-tracking-assignments'.
+ optimized program compiled with `-fno-var-tracking-assignments'.
In the negated form, this flag prevents SSA coalescing of user
variables, including inlined ones. This option is enabled by
default.
-'-ftree-ter'
+`-ftree-ter'
Perform temporary expression replacement during the SSA->normal
- phase. Single use/single def temporaries are replaced at their use
- location with their defining expression. This results in
- non-GIMPLE code, but gives the expanders much more complex trees to
- work on resulting in better RTL generation. This is enabled by
- default at '-O' and higher.
-
-'-ftree-slsr'
- Perform straight-line strength reduction on trees. This recognizes
- related expressions involving multiplications and replaces them by
- less expensive calculations when possible. This is enabled by
- default at '-O' and higher.
-
-'-ftree-vectorize'
- Perform vectorization on trees. This flag enables
- '-ftree-loop-vectorize' and '-ftree-slp-vectorize' if not
+ phase. Single use/single def temporaries are replaced at their
+ use location with their defining expression. This results in
+ non-GIMPLE code, but gives the expanders much more complex trees
+ to work on resulting in better RTL generation. This is enabled by
+ default at `-O' and higher.
+
+`-ftree-slsr'
+ Perform straight-line strength reduction on trees. This
+ recognizes related expressions involving multiplications and
+ replaces them by less expensive calculations when possible. This
+ is enabled by default at `-O' and higher.
+
+`-ftree-vectorize'
+ Perform vectorization on trees. This flag enables
+ `-ftree-loop-vectorize' and `-ftree-slp-vectorize' if not
explicitly specified.
-'-ftree-loop-vectorize'
- Perform loop vectorization on trees. This flag is enabled by
- default at '-O3' and when '-ftree-vectorize' is enabled.
+`-ftree-loop-vectorize'
+ Perform loop vectorization on trees. This flag is enabled by
+ default at `-O3' and when `-ftree-vectorize' is enabled.
-'-ftree-slp-vectorize'
- Perform basic block vectorization on trees. This flag is enabled
- by default at '-O3' and when '-ftree-vectorize' is enabled.
+`-ftree-slp-vectorize'
+ Perform basic block vectorization on trees. This flag is enabled
+ by default at `-O3' and when `-ftree-vectorize' is enabled.
-'-fvect-cost-model=MODEL'
+`-fvect-cost-model=MODEL'
Alter the cost model used for vectorization. The MODEL argument
- should be one of 'unlimited', 'dynamic' or 'cheap'. With the
- 'unlimited' model the vectorized code-path is assumed to be
- profitable while with the 'dynamic' model a runtime check guards
+ should be one of `unlimited', `dynamic' or `cheap'. With the
+ `unlimited' model the vectorized code-path is assumed to be
+ profitable while with the `dynamic' model a runtime check guards
the vectorized code-path to enable it only for iteration counts
that will likely execute faster than when executing the original
- scalar loop. The 'cheap' model disables vectorization of loops
+ scalar loop. The `cheap' model disables vectorization of loops
where doing so would be cost prohibitive for example due to
required runtime checks for data dependence or alignment but
- otherwise is equal to the 'dynamic' model. The default cost model
- depends on other optimization flags and is either 'dynamic' or
- 'cheap'.
+ otherwise is equal to the `dynamic' model. The default cost model
+ depends on other optimization flags and is either `dynamic' or
+ `cheap'.
-'-fsimd-cost-model=MODEL'
+`-fsimd-cost-model=MODEL'
Alter the cost model used for vectorization of loops marked with
the OpenMP or Cilk Plus simd directive. The MODEL argument should
- be one of 'unlimited', 'dynamic', 'cheap'. All values of MODEL
- have the same meaning as described in '-fvect-cost-model' and by
- default a cost model defined with '-fvect-cost-model' is used.
+ be one of `unlimited', `dynamic', `cheap'. All values of MODEL
+ have the same meaning as described in `-fvect-cost-model' and by
+ default a cost model defined with `-fvect-cost-model' is used.
-'-ftree-vrp'
+`-ftree-vrp'
Perform Value Range Propagation on trees. This is similar to the
constant propagation pass, but instead of values, ranges of values
are propagated. This allows the optimizers to remove unnecessary
- range checks like array bound checks and null pointer checks. This
- is enabled by default at '-O2' and higher. Null pointer check
- elimination is only done if '-fdelete-null-pointer-checks' is
+ range checks like array bound checks and null pointer checks.
+ This is enabled by default at `-O2' and higher. Null pointer check
+ elimination is only done if `-fdelete-null-pointer-checks' is
enabled.
-'-fsplit-ivs-in-unroller'
+`-fsplit-ivs-in-unroller'
Enables expression of values of induction variables in later
iterations of the unrolled loop using the value in the first
iteration. This breaks long dependency chains, thus improving
efficiency of the scheduling passes.
- A combination of '-fweb' and CSE is often sufficient to obtain the
- same effect. However, that is not reliable in cases where the loop
- body is more complicated than a single basic block. It also does
- not work at all on some architectures due to restrictions in the
- CSE pass.
+ A combination of `-fweb' and CSE is often sufficient to obtain the
+ same effect. However, that is not reliable in cases where the
+ loop body is more complicated than a single basic block. It also
+ does not work at all on some architectures due to restrictions in
+ the CSE pass.
This optimization is enabled by default.
-'-fvariable-expansion-in-unroller'
+`-fvariable-expansion-in-unroller'
With this option, the compiler creates multiple copies of some
- local variables when unrolling a loop, which can result in superior
- code.
+ local variables when unrolling a loop, which can result in
+ superior code.
-'-fpartial-inlining'
+`-fpartial-inlining'
Inline parts of functions. This option has any effect only when
- inlining itself is turned on by the '-finline-functions' or
- '-finline-small-functions' options.
+ inlining itself is turned on by the `-finline-functions' or
+ `-finline-small-functions' options.
- Enabled at level '-O2'.
+ Enabled at level `-O2'.
-'-fpredictive-commoning'
+`-fpredictive-commoning'
Perform predictive commoning optimization, i.e., reusing
computations (especially memory loads and stores) performed in
previous iterations of loops.
- This option is enabled at level '-O3'.
+ This option is enabled at level `-O3'.
-'-fprefetch-loop-arrays'
+`-fprefetch-loop-arrays'
If supported by the target machine, generate instructions to
prefetch memory to improve the performance of loops that access
large arrays.
@@ -8073,76 +8139,76 @@ optimizations to be performed is desired.
This option may generate better or worse code; results are highly
dependent on the structure of loops within the source code.
- Disabled at level '-Os'.
+ Disabled at level `-Os'.
-'-fno-peephole'
-'-fno-peephole2'
+`-fno-peephole'
+`-fno-peephole2'
Disable any machine-specific peephole optimizations. The
- difference between '-fno-peephole' and '-fno-peephole2' is in how
+ difference between `-fno-peephole' and `-fno-peephole2' is in how
they are implemented in the compiler; some targets use one, some
use the other, a few use both.
- '-fpeephole' is enabled by default. '-fpeephole2' enabled at
- levels '-O2', '-O3', '-Os'.
+ `-fpeephole' is enabled by default. `-fpeephole2' enabled at
+ levels `-O2', `-O3', `-Os'.
-'-fno-guess-branch-probability'
+`-fno-guess-branch-probability'
Do not guess branch probabilities using heuristics.
GCC uses heuristics to guess branch probabilities if they are not
- provided by profiling feedback ('-fprofile-arcs'). These
+ provided by profiling feedback (`-fprofile-arcs'). These
heuristics are based on the control flow graph. If some branch
- probabilities are specified by '__builtin_expect', then the
+ probabilities are specified by `__builtin_expect', then the
heuristics are used to guess branch probabilities for the rest of
- the control flow graph, taking the '__builtin_expect' info into
+ the control flow graph, taking the `__builtin_expect' info into
account. The interactions between the heuristics and
- '__builtin_expect' can be complex, and in some cases, it may be
+ `__builtin_expect' can be complex, and in some cases, it may be
useful to disable the heuristics so that the effects of
- '__builtin_expect' are easier to understand.
+ `__builtin_expect' are easier to understand.
- The default is '-fguess-branch-probability' at levels '-O', '-O2',
- '-O3', '-Os'.
+ The default is `-fguess-branch-probability' at levels `-O', `-O2',
+ `-O3', `-Os'.
-'-freorder-blocks'
+`-freorder-blocks'
Reorder basic blocks in the compiled function in order to reduce
number of taken branches and improve code locality.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-freorder-blocks-and-partition'
- In addition to reordering basic blocks in the compiled function, in
- order to reduce number of taken branches, partitions hot and cold
- basic blocks into separate sections of the assembly and .o files,
- to improve paging and cache locality performance.
+`-freorder-blocks-and-partition'
+ In addition to reordering basic blocks in the compiled function,
+ in order to reduce number of taken branches, partitions hot and
+ cold basic blocks into separate sections of the assembly and .o
+ files, to improve paging and cache locality performance.
This optimization is automatically turned off in the presence of
exception handling, for linkonce sections, for functions with a
user-defined section attribute and on any architecture that does
not support named sections.
- Enabled for x86 at levels '-O2', '-O3'.
+ Enabled for x86 at levels `-O2', `-O3'.
-'-freorder-functions'
+`-freorder-functions'
Reorder functions in the object file in order to improve code
locality. This is implemented by using special subsections
- '.text.hot' for most frequently executed functions and
- '.text.unlikely' for unlikely executed functions. Reordering is
+ `.text.hot' for most frequently executed functions and
+ `.text.unlikely' for unlikely executed functions. Reordering is
done by the linker so object file format must support named
sections and linker must place them in a reasonable way.
Also profile feedback must be available to make this option
- effective. See '-fprofile-arcs' for details.
+ effective. See `-fprofile-arcs' for details.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-fstrict-aliasing'
+`-fstrict-aliasing'
Allow the compiler to assume the strictest aliasing rules
applicable to the language being compiled. For C (and C++), this
activates optimizations based on the type of expressions. In
- particular, an object of one type is assumed never to reside at the
- same address as an object of a different type, unless the types are
- almost the same. For example, an 'unsigned int' can alias an
- 'int', but not a 'void*' or a 'double'. A character type may alias
- any other type.
+ particular, an object of one type is assumed never to reside at
+ the same address as an object of a different type, unless the
+ types are almost the same. For example, an `unsigned int' can
+ alias an `int', but not a `void*' or a `double'. A character type
+ may alias any other type.
Pay special attention to code like this:
union a_union {
@@ -8157,7 +8223,7 @@ optimizations to be performed is desired.
}
The practice of reading from a different union member than the one
most recently written to (called "type-punning") is common. Even
- with '-fstrict-aliasing', type-punning is allowed, provided the
+ with `-fstrict-aliasing', type-punning is allowed, provided the
memory is accessed through the union type. So, the code above
works as expected. *Note Structures unions enumerations and
bit-fields implementation::. However, this code might not:
@@ -8177,18 +8243,18 @@ optimizations to be performed is desired.
return ((union a_union *) &d)->i;
}
- The '-fstrict-aliasing' option is enabled at levels '-O2', '-O3',
- '-Os'.
+ The `-fstrict-aliasing' option is enabled at levels `-O2', `-O3',
+ `-Os'.
-'-fstrict-overflow'
+`-fstrict-overflow'
Allow the compiler to assume strict signed overflow rules,
depending on the language being compiled. For C (and C++) this
means that overflow when doing arithmetic with signed numbers is
undefined, which means that the compiler may assume that it does
not happen. This permits various optimizations. For example, the
- compiler assumes that an expression like 'i + 10 > i' is always
- true for signed 'i'. This assumption is only valid if signed
- overflow is undefined, as the expression is false if 'i + 10'
+ compiler assumes that an expression like `i + 10 > i' is always
+ true for signed `i'. This assumption is only valid if signed
+ overflow is undefined, as the expression is false if `i + 10'
overflows when using twos complement arithmetic. When this option
is in effect any attempt to determine whether an operation on
signed numbers overflows must be written carefully to not actually
@@ -8198,105 +8264,105 @@ optimizations to be performed is desired.
semantics: given a pointer to an object, if adding an offset to
that pointer does not produce a pointer to the same object, the
addition is undefined. This permits the compiler to conclude that
- 'p + u > p' is always true for a pointer 'p' and unsigned integer
- 'u'. This assumption is only valid because pointer wraparound is
- undefined, as the expression is false if 'p + u' overflows using
+ `p + u > p' is always true for a pointer `p' and unsigned integer
+ `u'. This assumption is only valid because pointer wraparound is
+ undefined, as the expression is false if `p + u' overflows using
twos complement arithmetic.
- See also the '-fwrapv' option. Using '-fwrapv' means that integer
- signed overflow is fully defined: it wraps. When '-fwrapv' is
- used, there is no difference between '-fstrict-overflow' and
- '-fno-strict-overflow' for integers. With '-fwrapv' certain types
+ See also the `-fwrapv' option. Using `-fwrapv' means that integer
+ signed overflow is fully defined: it wraps. When `-fwrapv' is
+ used, there is no difference between `-fstrict-overflow' and
+ `-fno-strict-overflow' for integers. With `-fwrapv' certain types
of overflow are permitted. For example, if the compiler gets an
overflow when doing arithmetic on constants, the overflowed value
- can still be used with '-fwrapv', but not otherwise.
+ can still be used with `-fwrapv', but not otherwise.
- The '-fstrict-overflow' option is enabled at levels '-O2', '-O3',
- '-Os'.
+ The `-fstrict-overflow' option is enabled at levels `-O2', `-O3',
+ `-Os'.
-'-falign-functions'
-'-falign-functions=N'
+`-falign-functions'
+`-falign-functions=N'
Align the start of functions to the next power-of-two greater than
- N, skipping up to N bytes. For instance, '-falign-functions=32'
+ N, skipping up to N bytes. For instance, `-falign-functions=32'
aligns functions to the next 32-byte boundary, but
- '-falign-functions=24' aligns to the next 32-byte boundary only if
+ `-falign-functions=24' aligns to the next 32-byte boundary only if
this can be done by skipping 23 bytes or less.
- '-fno-align-functions' and '-falign-functions=1' are equivalent and
- mean that functions are not aligned.
+ `-fno-align-functions' and `-falign-functions=1' are equivalent
+ and mean that functions are not aligned.
- Some assemblers only support this flag when N is a power of two; in
- that case, it is rounded up.
+ Some assemblers only support this flag when N is a power of two;
+ in that case, it is rounded up.
If N is not specified or is zero, use a machine-dependent default.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-falign-labels'
-'-falign-labels=N'
+`-falign-labels'
+`-falign-labels=N'
Align all branch targets to a power-of-two boundary, skipping up to
- N bytes like '-falign-functions'. This option can easily make code
- slower, because it must insert dummy operations for when the branch
- target is reached in the usual flow of the code.
+ N bytes like `-falign-functions'. This option can easily make
+ code slower, because it must insert dummy operations for when the
+ branch target is reached in the usual flow of the code.
- '-fno-align-labels' and '-falign-labels=1' are equivalent and mean
+ `-fno-align-labels' and `-falign-labels=1' are equivalent and mean
that labels are not aligned.
- If '-falign-loops' or '-falign-jumps' are applicable and are
+ If `-falign-loops' or `-falign-jumps' are applicable and are
greater than this value, then their values are used instead.
If N is not specified or is zero, use a machine-dependent default
- which is very likely to be '1', meaning no alignment.
+ which is very likely to be `1', meaning no alignment.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-falign-loops'
-'-falign-loops=N'
- Align loops to a power-of-two boundary, skipping up to N bytes like
- '-falign-functions'. If the loops are executed many times, this
- makes up for any execution of the dummy operations.
+`-falign-loops'
+`-falign-loops=N'
+ Align loops to a power-of-two boundary, skipping up to N bytes
+ like `-falign-functions'. If the loops are executed many times,
+ this makes up for any execution of the dummy operations.
- '-fno-align-loops' and '-falign-loops=1' are equivalent and mean
+ `-fno-align-loops' and `-falign-loops=1' are equivalent and mean
that loops are not aligned.
If N is not specified or is zero, use a machine-dependent default.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-falign-jumps'
-'-falign-jumps=N'
+`-falign-jumps'
+`-falign-jumps=N'
Align branch targets to a power-of-two boundary, for branch targets
where the targets can only be reached by jumping, skipping up to N
- bytes like '-falign-functions'. In this case, no dummy operations
+ bytes like `-falign-functions'. In this case, no dummy operations
need be executed.
- '-fno-align-jumps' and '-falign-jumps=1' are equivalent and mean
+ `-fno-align-jumps' and `-falign-jumps=1' are equivalent and mean
that loops are not aligned.
If N is not specified or is zero, use a machine-dependent default.
- Enabled at levels '-O2', '-O3'.
+ Enabled at levels `-O2', `-O3'.
-'-funit-at-a-time'
- This option is left for compatibility reasons. '-funit-at-a-time'
- has no effect, while '-fno-unit-at-a-time' implies
- '-fno-toplevel-reorder' and '-fno-section-anchors'.
+`-funit-at-a-time'
+ This option is left for compatibility reasons. `-funit-at-a-time'
+ has no effect, while `-fno-unit-at-a-time' implies
+ `-fno-toplevel-reorder' and `-fno-section-anchors'.
Enabled by default.
-'-fno-toplevel-reorder'
- Do not reorder top-level functions, variables, and 'asm'
+`-fno-toplevel-reorder'
+ Do not reorder top-level functions, variables, and `asm'
statements. Output them in the same order that they appear in the
input file. When this option is used, unreferenced static
variables are not removed. This option is intended to support
existing code that relies on a particular ordering. For new code,
it is better to use attributes when possible.
- Enabled at level '-O0'. When disabled explicitly, it also implies
- '-fno-section-anchors', which is otherwise enabled at '-O0' on some
+ Enabled at level `-O0'. When disabled explicitly, it also implies
+ `-fno-section-anchors', which is otherwise enabled at `-O0' on some
targets.
-'-fweb'
+`-fweb'
Constructs webs as commonly used for register allocation purposes
and assign each web individual pseudo register. This allows the
register allocation pass to operate on pseudos directly, but also
@@ -8305,20 +8371,20 @@ optimizations to be performed is desired.
debugging impossible, since variables no longer stay in a "home
register".
- Enabled by default with '-funroll-loops'.
+ Enabled by default with `-funroll-loops'.
-'-fwhole-program'
+`-fwhole-program'
Assume that the current compilation unit represents the whole
program being compiled. All public functions and variables with
- the exception of 'main' and those merged by attribute
- 'externally_visible' become static functions and in effect are
+ the exception of `main' and those merged by attribute
+ `externally_visible' become static functions and in effect are
optimized more aggressively by interprocedural optimizers.
- This option should not be used in combination with '-flto'.
+ This option should not be used in combination with `-flto'.
Instead relying on a linker plugin should provide safer and more
precise information.
-'-flto[=N]'
+`-flto[=N]'
This option runs the standard link-time optimizer. When invoked
with source code, it generates GIMPLE (one of GCC's internal
representations) and writes it to special ELF sections in the
@@ -8326,63 +8392,63 @@ optimizations to be performed is desired.
function bodies are read from these ELF sections and instantiated
as if they had been part of the same translation unit.
- To use the link-time optimizer, '-flto' and optimization options
- should be specified at compile time and during the final link. For
- example:
+ To use the link-time optimizer, `-flto' and optimization options
+ should be specified at compile time and during the final link.
+ For example:
gcc -c -O2 -flto foo.c
gcc -c -O2 -flto bar.c
gcc -o myprog -flto -O2 foo.o bar.o
The first two invocations to GCC save a bytecode representation of
- GIMPLE into special ELF sections inside 'foo.o' and 'bar.o'. The
- final invocation reads the GIMPLE bytecode from 'foo.o' and
- 'bar.o', merges the two files into a single internal image, and
- compiles the result as usual. Since both 'foo.o' and 'bar.o' are
+ GIMPLE into special ELF sections inside `foo.o' and `bar.o'. The
+ final invocation reads the GIMPLE bytecode from `foo.o' and
+ `bar.o', merges the two files into a single internal image, and
+ compiles the result as usual. Since both `foo.o' and `bar.o' are
merged into a single image, this causes all the interprocedural
analyses and optimizations in GCC to work across the two files as
if they were a single one. This means, for example, that the
- inliner is able to inline functions in 'bar.o' into functions in
- 'foo.o' and vice-versa.
+ inliner is able to inline functions in `bar.o' into functions in
+ `foo.o' and vice-versa.
Another (simpler) way to enable link-time optimization is:
gcc -o myprog -flto -O2 foo.c bar.c
- The above generates bytecode for 'foo.c' and 'bar.c', merges them
+ The above generates bytecode for `foo.c' and `bar.c', merges them
together into a single GIMPLE representation and optimizes them as
- usual to produce 'myprog'.
+ usual to produce `myprog'.
The only important thing to keep in mind is that to enable
link-time optimizations you need to use the GCC driver to perform
the link-step. GCC then automatically performs link-time
optimization if any of the objects involved were compiled with the
- '-flto' command-line option. You generally should specify the
+ `-flto' command-line option. You generally should specify the
optimization options to be used for link-time optimization though
GCC tries to be clever at guessing an optimization level to use
- from the options used at compile-time if you fail to specify one at
- link-time. You can always override the automatic decision to do
- link-time optimization at link-time by passing '-fno-lto' to the
- link command.
+ from the options used at compile-time if you fail to specify one
+ at link-time. You can always override the automatic decision to
+ do link-time optimization at link-time by passing `-fno-lto' to
+ the link command.
To make whole program optimization effective, it is necessary to
make certain whole program assumptions. The compiler needs to know
what functions and variables can be accessed by libraries and
- runtime outside of the link-time optimized unit. When supported by
- the linker, the linker plugin (see '-fuse-linker-plugin') passes
- information to the compiler about used and externally visible
- symbols. When the linker plugin is not available,
- '-fwhole-program' should be used to allow the compiler to make
+ runtime outside of the link-time optimized unit. When supported
+ by the linker, the linker plugin (see `-fuse-linker-plugin')
+ passes information to the compiler about used and externally
+ visible symbols. When the linker plugin is not available,
+ `-fwhole-program' should be used to allow the compiler to make
these assumptions, which leads to more aggressive optimization
decisions.
- When '-fuse-linker-plugin' is not enabled then, when a file is
- compiled with '-flto', the generated object file is larger than a
+ When `-fuse-linker-plugin' is not enabled then, when a file is
+ compiled with `-flto', the generated object file is larger than a
regular object file because it contains GIMPLE bytecodes and the
- usual final code (see '-ffat-lto-objects'. This means that object
- files with LTO information can be linked as normal object files; if
- '-fno-lto' is passed to the linker, no interprocedural
- optimizations are applied. Note that when '-fno-fat-lto-objects'
+ usual final code (see `-ffat-lto-objects'. This means that object
+ files with LTO information can be linked as normal object files;
+ if `-fno-lto' is passed to the linker, no interprocedural
+ optimizations are applied. Note that when `-fno-fat-lto-objects'
is enabled the compile-stage is faster but you cannot perform a
regular, non-LTO link on them.
@@ -8395,44 +8461,44 @@ optimizations to be performed is desired.
gcc -o myprog -O3 foo.o bar.o
This produces individual object files with unoptimized assembler
- code, but the resulting binary 'myprog' is optimized at '-O3'. If,
- instead, the final binary is generated with '-fno-lto', then
- 'myprog' is not optimized.
+ code, but the resulting binary `myprog' is optimized at `-O3'.
+ If, instead, the final binary is generated with `-fno-lto', then
+ `myprog' is not optimized.
When producing the final binary, GCC only applies link-time
- optimizations to those files that contain bytecode. Therefore, you
- can mix and match object files and libraries with GIMPLE bytecodes
- and final object code. GCC automatically selects which files to
- optimize in LTO mode and which files to link without further
- processing.
+ optimizations to those files that contain bytecode. Therefore,
+ you can mix and match object files and libraries with GIMPLE
+ bytecodes and final object code. GCC automatically selects which
+ files to optimize in LTO mode and which files to link without
+ further processing.
There are some code generation flags preserved by GCC when
generating bytecodes, as they need to be used during the final link
stage. Generally options specified at link-time override those
specified at compile-time.
- If you do not specify an optimization level option '-O' at
+ If you do not specify an optimization level option `-O' at
link-time then GCC computes one based on the optimization levels
used when compiling the object files. The highest optimization
level wins here.
Currently, the following options and their setting are take from
- the first object file that explicitely specified it: '-fPIC',
- '-fpic', '-fpie', '-fcommon', '-fexceptions',
- '-fnon-call-exceptions', '-fgnu-tm' and all the '-m' target flags.
+ the first object file that explicitely specified it: `-fPIC',
+ `-fpic', `-fpie', `-fcommon', `-fexceptions',
+ `-fnon-call-exceptions', `-fgnu-tm' and all the `-m' target flags.
Certain ABI changing flags are required to match in all
compilation-units and trying to override this at link-time with a
conflicting value is ignored. This includes options such as
- '-freg-struct-return' and '-fpcc-struct-return'.
+ `-freg-struct-return' and `-fpcc-struct-return'.
- Other options such as '-ffp-contract', '-fno-strict-overflow',
- '-fwrapv', '-fno-trapv' or '-fno-strict-aliasing' are passed
- through to the link stage and merged conservatively for conflicting
- translation units. Specifically '-fno-strict-overflow', '-fwrapv'
- and '-fno-trapv' take precedence and for example
- '-ffp-contract=off' takes precedence over '-ffp-contract=fast'.
- You can override them at linke-time.
+ Other options such as `-ffp-contract', `-fno-strict-overflow',
+ `-fwrapv', `-fno-trapv' or `-fno-strict-aliasing' are passed
+ through to the link stage and merged conservatively for
+ conflicting translation units. Specifically
+ `-fno-strict-overflow', `-fwrapv' and `-fno-trapv' take precedence
+ and for example `-ffp-contract=off' takes precedence over
+ `-ffp-contract=fast'. You can override them at linke-time.
It is recommended that you compile all the files participating in
the same link with the same options and also specify those options
@@ -8453,43 +8519,43 @@ optimizations to be performed is desired.
gfortran -c -flto baz.f90
g++ -o myprog -flto -O3 foo.o bar.o baz.o -lgfortran
- Notice that the final link is done with 'g++' to get the C++
- runtime libraries and '-lgfortran' is added to get the Fortran
+ Notice that the final link is done with `g++' to get the C++
+ runtime libraries and `-lgfortran' is added to get the Fortran
runtime libraries. In general, when mixing languages in LTO mode,
you should use the same link command options as when mixing
languages in a regular (non-LTO) compilation.
If object files containing GIMPLE bytecode are stored in a library
- archive, say 'libfoo.a', it is possible to extract and use them in
+ archive, say `libfoo.a', it is possible to extract and use them in
an LTO link if you are using a linker with plugin support. To
- create static libraries suitable for LTO, use 'gcc-ar' and
- 'gcc-ranlib' instead of 'ar' and 'ranlib'; to show the symbols of
- object files with GIMPLE bytecode, use 'gcc-nm'. Those commands
- require that 'ar', 'ranlib' and 'nm' have been compiled with plugin
- support. At link time, use the the flag '-fuse-linker-plugin' to
- ensure that the library participates in the LTO optimization
- process:
+ create static libraries suitable for LTO, use `gcc-ar' and
+ `gcc-ranlib' instead of `ar' and `ranlib'; to show the symbols of
+ object files with GIMPLE bytecode, use `gcc-nm'. Those commands
+ require that `ar', `ranlib' and `nm' have been compiled with
+ plugin support. At link time, use the the flag
+ `-fuse-linker-plugin' to ensure that the library participates in
+ the LTO optimization process:
gcc -o myprog -O2 -flto -fuse-linker-plugin a.o b.o -lfoo
With the linker plugin enabled, the linker extracts the needed
- GIMPLE files from 'libfoo.a' and passes them on to the running GCC
+ GIMPLE files from `libfoo.a' and passes them on to the running GCC
to make them part of the aggregated GIMPLE image to be optimized.
If you are not using a linker with plugin support and/or do not
- enable the linker plugin, then the objects inside 'libfoo.a' are
+ enable the linker plugin, then the objects inside `libfoo.a' are
extracted and linked as usual, but they do not participate in the
LTO optimization process. In order to make a static library
suitable for both LTO optimization and usual linkage, compile its
- object files with '-flto' '-ffat-lto-objects'.
+ object files with `-flto' `-ffat-lto-objects'.
Link-time optimizations do not require the presence of the whole
- program to operate. If the program does not require any symbols to
- be exported, it is possible to combine '-flto' and
- '-fwhole-program' to allow the interprocedural optimizers to use
- more aggressive assumptions which may lead to improved optimization
- opportunities. Use of '-fwhole-program' is not needed when linker
- plugin is active (see '-fuse-linker-plugin').
+ program to operate. If the program does not require any symbols
+ to be exported, it is possible to combine `-flto' and
+ `-fwhole-program' to allow the interprocedural optimizers to use
+ more aggressive assumptions which may lead to improved
+ optimization opportunities. Use of `-fwhole-program' is not
+ needed when linker plugin is active (see `-fuse-linker-plugin').
The current implementation of LTO makes no attempt to generate
bytecode that is portable between different types of hosts. The
@@ -8498,97 +8564,99 @@ optimizations to be performed is desired.
an older or newer version of GCC.
Link-time optimization does not work well with generation of
- debugging information. Combining '-flto' with '-g' is currently
+ debugging information. Combining `-flto' with `-g' is currently
experimental and expected to produce unexpected results.
- If you specify the optional N, the optimization and code generation
- done at link time is executed in parallel using N parallel jobs by
- utilizing an installed 'make' program. The environment variable
- 'MAKE' may be used to override the program used. The default value
- for N is 1.
+ If you specify the optional N, the optimization and code
+ generation done at link time is executed in parallel using N
+ parallel jobs by utilizing an installed `make' program. The
+ environment variable `MAKE' may be used to override the program
+ used. The default value for N is 1.
- You can also specify '-flto=jobserver' to use GNU make's job server
- mode to determine the number of parallel jobs. This is useful when
- the Makefile calling GCC is already executing in parallel. You
- must prepend a '+' to the command recipe in the parent Makefile for
- this to work. This option likely only works if 'MAKE' is GNU make.
+ You can also specify `-flto=jobserver' to use GNU make's job
+ server mode to determine the number of parallel jobs. This is
+ useful when the Makefile calling GCC is already executing in
+ parallel. You must prepend a `+' to the command recipe in the
+ parent Makefile for this to work. This option likely only works
+ if `MAKE' is GNU make.
-'-flto-partition=ALG'
+`-flto-partition=ALG'
Specify the partitioning algorithm used by the link-time optimizer.
- The value is either '1to1' to specify a partitioning mirroring the
- original source files or 'balanced' to specify partitioning into
- equally sized chunks (whenever possible) or 'max' to create new
- partition for every symbol where possible. Specifying 'none' as an
- algorithm disables partitioning and streaming completely. The
- default value is 'balanced'. While '1to1' can be used as an
- workaround for various code ordering issues, the 'max' partitioning
- is intended for internal testing only. The value 'one' specifies
- that exactly one partition should be used while the value 'none'
- bypasses partitioning and executes the link-time optimization step
- directly from the WPA phase.
-
-'-flto-odr-type-merging'
+ The value is either `1to1' to specify a partitioning mirroring the
+ original source files or `balanced' to specify partitioning into
+ equally sized chunks (whenever possible) or `max' to create new
+ partition for every symbol where possible. Specifying `none' as
+ an algorithm disables partitioning and streaming completely. The
+ default value is `balanced'. While `1to1' can be used as an
+ workaround for various code ordering issues, the `max'
+ partitioning is intended for internal testing only. The value
+ `one' specifies that exactly one partition should be used while
+ the value `none' bypasses partitioning and executes the link-time
+ optimization step directly from the WPA phase.
+
+`-flto-odr-type-merging'
Enable streaming of mangled types names of C++ types and their
unification at linktime. This increases size of LTO object files,
but enable diagnostics about One Definition Rule violations.
-'-flto-compression-level=N'
+`-flto-compression-level=N'
This option specifies the level of compression used for
intermediate language written to LTO object files, and is only
- meaningful in conjunction with LTO mode ('-flto'). Valid values
+ meaningful in conjunction with LTO mode (`-flto'). Valid values
are 0 (no compression) to 9 (maximum compression). Values outside
this range are clamped to either 0 or 9. If the option is not
given, a default balanced compression setting is used.
-'-flto-report'
+`-flto-report'
Prints a report with internal details on the workings of the
- link-time optimizer. The contents of this report vary from version
- to version. It is meant to be useful to GCC developers when
- processing object files in LTO mode (via '-flto').
+ link-time optimizer. The contents of this report vary from
+ version to version. It is meant to be useful to GCC developers
+ when processing object files in LTO mode (via `-flto').
Disabled by default.
-'-flto-report-wpa'
- Like '-flto-report', but only print for the WPA phase of Link Time
+`-flto-report-wpa'
+ Like `-flto-report', but only print for the WPA phase of Link Time
Optimization.
-'-fuse-linker-plugin'
+`-fuse-linker-plugin'
Enables the use of a linker plugin during link-time optimization.
This option relies on plugin support in the linker, which is
available in gold or in GNU ld 2.21 or newer.
This option enables the extraction of object files with GIMPLE
- bytecode out of library archives. This improves the quality of
+ bytecode out of library archives. This improves the quality of
optimization by exposing more code to the link-time optimizer.
This information specifies what symbols can be accessed externally
(by non-LTO object or during dynamic linking). Resulting code
quality improvements on binaries (and shared libraries that use
- hidden visibility) are similar to '-fwhole-program'. See '-flto'
+ hidden visibility) are similar to `-fwhole-program'. See `-flto'
for a description of the effect of this flag and how to use it.
This option is enabled by default when LTO support in GCC is
enabled and GCC was configured for use with a linker supporting
plugins (GNU ld 2.21 or newer or gold).
-'-ffat-lto-objects'
- Fat LTO objects are object files that contain both the intermediate
- language and the object code. This makes them usable for both LTO
- linking and normal linking. This option is effective only when
- compiling with '-flto' and is ignored at link time.
-
- '-fno-fat-lto-objects' improves compilation time over plain LTO,
- but requires the complete toolchain to be aware of LTO. It requires
- a linker with linker plugin support for basic functionality.
- Additionally, 'nm', 'ar' and 'ranlib' need to support linker
- plugins to allow a full-featured build environment (capable of
- building static libraries etc). GCC provides the 'gcc-ar',
- 'gcc-nm', 'gcc-ranlib' wrappers to pass the right options to these
- tools. With non fat LTO makefiles need to be modified to use them.
-
- The default is '-fno-fat-lto-objects' on targets with linker plugin
+`-ffat-lto-objects'
+ Fat LTO objects are object files that contain both the
+ intermediate language and the object code. This makes them usable
+ for both LTO linking and normal linking. This option is effective
+ only when compiling with `-flto' and is ignored at link time.
+
+ `-fno-fat-lto-objects' improves compilation time over plain LTO,
+ but requires the complete toolchain to be aware of LTO. It
+ requires a linker with linker plugin support for basic
+ functionality. Additionally, `nm', `ar' and `ranlib' need to
+ support linker plugins to allow a full-featured build environment
+ (capable of building static libraries etc). GCC provides the
+ `gcc-ar', `gcc-nm', `gcc-ranlib' wrappers to pass the right options
+ to these tools. With non fat LTO makefiles need to be modified to
+ use them.
+
+ The default is `-fno-fat-lto-objects' on targets with linker plugin
support.
-'-fcompare-elim'
+`-fcompare-elim'
After register allocation and post-register allocation instruction
splitting, identify arithmetic instructions that compute processor
flags similar to a comparison operation based on that arithmetic.
@@ -8598,87 +8666,85 @@ optimizations to be performed is desired.
represent the comparison operation before register allocation is
complete.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fcprop-registers'
+`-fcprop-registers'
After register allocation and post-register allocation instruction
splitting, perform a copy-propagation pass to try to reduce
scheduling dependencies and occasionally eliminate the copy.
- Enabled at levels '-O', '-O2', '-O3', '-Os'.
+ Enabled at levels `-O', `-O2', `-O3', `-Os'.
-'-fprofile-correction'
+`-fprofile-correction'
Profiles collected using an instrumented binary for multi-threaded
- programs may be inconsistent due to missed counter updates. When
+ programs may be inconsistent due to missed counter updates. When
this option is specified, GCC uses heuristics to correct or smooth
- out such inconsistencies. By default, GCC emits an error message
+ out such inconsistencies. By default, GCC emits an error message
when an inconsistent profile is detected.
-'-fprofile-dir=PATH'
-
+`-fprofile-dir=PATH'
Set the directory to search for the profile data files in to PATH.
This option affects only the profile data generated by
- '-fprofile-generate', '-ftest-coverage', '-fprofile-arcs' and used
- by '-fprofile-use' and '-fbranch-probabilities' and its related
+ `-fprofile-generate', `-ftest-coverage', `-fprofile-arcs' and used
+ by `-fprofile-use' and `-fbranch-probabilities' and its related
options. Both absolute and relative paths can be used. By
default, GCC uses the current directory as PATH, thus the profile
data file appears in the same directory as the object file.
-'-fprofile-generate'
-'-fprofile-generate=PATH'
-
+`-fprofile-generate'
+`-fprofile-generate=PATH'
Enable options usually used for instrumenting application to
produce profile useful for later recompilation with profile
- feedback based optimization. You must use '-fprofile-generate'
+ feedback based optimization. You must use `-fprofile-generate'
both when compiling and when linking your program.
- The following options are enabled: '-fprofile-arcs',
- '-fprofile-values', '-fvpt'.
+ The following options are enabled: `-fprofile-arcs',
+ `-fprofile-values', `-fvpt'.
If PATH is specified, GCC looks at the PATH to find the profile
- feedback data files. See '-fprofile-dir'.
+ feedback data files. See `-fprofile-dir'.
-'-fprofile-use'
-'-fprofile-use=PATH'
+`-fprofile-use'
+`-fprofile-use=PATH'
Enable profile feedback-directed optimizations, and the following
optimizations which are generally profitable only with profile
- feedback available: '-fbranch-probabilities', '-fvpt',
- '-funroll-loops', '-fpeel-loops', '-ftracer', '-ftree-vectorize',
- and 'ftree-loop-distribute-patterns'.
+ feedback available: `-fbranch-probabilities', `-fvpt',
+ `-funroll-loops', `-fpeel-loops', `-ftracer', `-ftree-vectorize',
+ and `ftree-loop-distribute-patterns'.
By default, GCC emits an error message if the feedback profiles do
- not match the source code. This error can be turned into a warning
- by using '-Wcoverage-mismatch'. Note this may result in poorly
- optimized code.
+ not match the source code. This error can be turned into a
+ warning by using `-Wcoverage-mismatch'. Note this may result in
+ poorly optimized code.
If PATH is specified, GCC looks at the PATH to find the profile
- feedback data files. See '-fprofile-dir'.
+ feedback data files. See `-fprofile-dir'.
-'-fauto-profile'
-'-fauto-profile=PATH'
+`-fauto-profile'
+`-fauto-profile=PATH'
Enable sampling-based feedback-directed optimizations, and the
following optimizations which are generally profitable only with
- profile feedback available: '-fbranch-probabilities', '-fvpt',
- '-funroll-loops', '-fpeel-loops', '-ftracer', '-ftree-vectorize',
- '-finline-functions', '-fipa-cp', '-fipa-cp-clone',
- '-fpredictive-commoning', '-funswitch-loops',
- '-fgcse-after-reload', and '-ftree-loop-distribute-patterns'.
+ profile feedback available: `-fbranch-probabilities', `-fvpt',
+ `-funroll-loops', `-fpeel-loops', `-ftracer', `-ftree-vectorize',
+ `-finline-functions', `-fipa-cp', `-fipa-cp-clone',
+ `-fpredictive-commoning', `-funswitch-loops',
+ `-fgcse-after-reload', and `-ftree-loop-distribute-patterns'.
PATH is the name of a file containing AutoFDO profile information.
- If omitted, it defaults to 'fbdata.afdo' in the current directory.
+ If omitted, it defaults to `fbdata.afdo' in the current directory.
Producing an AutoFDO profile data file requires running your
- program with the 'perf' utility on a supported GNU/Linux target
- system. For more information, see <https://perf.wiki.kernel.org/>.
+ program with the `perf' utility on a supported GNU/Linux target
+ system. For more information, see `https://perf.wiki.kernel.org/'.
E.g.
perf record -e br_inst_retired:near_taken -b -o perf.data \
-- your_program
- Then use the 'create_gcov' tool to convert the raw profile data to
+ Then use the `create_gcov' tool to convert the raw profile data to
a format that can be used by GCC. You must also supply the
unstripped binary for your program to this tool. See
- <https://github.com/google/autofdo>.
+ `https://github.com/google/autofdo'.
E.g.
create_gcov --binary=your_program.unstripped --profile=perf.data \
@@ -8688,267 +8754,265 @@ optimizations to be performed is desired.
floating-point arithmetic. These options trade off between speed and
correctness. All must be specifically enabled.
-'-ffloat-store'
+`-ffloat-store'
Do not store floating-point variables in registers, and inhibit
other options that might change whether a floating-point value is
taken from a register or memory.
This option prevents undesirable excess precision on machines such
as the 68000 where the floating registers (of the 68881) keep more
- precision than a 'double' is supposed to have. Similarly for the
+ precision than a `double' is supposed to have. Similarly for the
x86 architecture. For most programs, the excess precision does
only good, but a few programs rely on the precise definition of
- IEEE floating point. Use '-ffloat-store' for such programs, after
+ IEEE floating point. Use `-ffloat-store' for such programs, after
modifying them to store all pertinent intermediate computations
into variables.
-'-fexcess-precision=STYLE'
+`-fexcess-precision=STYLE'
This option allows further control over excess precision on
machines where floating-point registers have more precision than
- the IEEE 'float' and 'double' types and the processor does not
+ the IEEE `float' and `double' types and the processor does not
support operations rounding to those types. By default,
- '-fexcess-precision=fast' is in effect; this means that operations
+ `-fexcess-precision=fast' is in effect; this means that operations
are carried out in the precision of the registers and that it is
unpredictable when rounding to the types specified in the source
code takes place. When compiling C, if
- '-fexcess-precision=standard' is specified then excess precision
+ `-fexcess-precision=standard' is specified then excess precision
follows the rules specified in ISO C99; in particular, both casts
and assignments cause values to be rounded to their semantic types
- (whereas '-ffloat-store' only affects assignments). This option is
- enabled by default for C if a strict conformance option such as
- '-std=c99' is used.
-
- '-fexcess-precision=standard' is not implemented for languages
- other than C, and has no effect if '-funsafe-math-optimizations' or
- '-ffast-math' is specified. On the x86, it also has no effect if
- '-mfpmath=sse' or '-mfpmath=sse+387' is specified; in the former
- case, IEEE semantics apply without excess precision, and in the
- latter, rounding is unpredictable.
-
-'-ffast-math'
- Sets the options '-fno-math-errno', '-funsafe-math-optimizations',
- '-ffinite-math-only', '-fno-rounding-math', '-fno-signaling-nans'
- and '-fcx-limited-range'.
-
- This option causes the preprocessor macro '__FAST_MATH__' to be
+ (whereas `-ffloat-store' only affects assignments). This option
+ is enabled by default for C if a strict conformance option such as
+ `-std=c99' is used.
+
+ `-fexcess-precision=standard' is not implemented for languages
+ other than C, and has no effect if `-funsafe-math-optimizations'
+ or `-ffast-math' is specified. On the x86, it also has no effect
+ if `-mfpmath=sse' or `-mfpmath=sse+387' is specified; in the
+ former case, IEEE semantics apply without excess precision, and in
+ the latter, rounding is unpredictable.
+
+`-ffast-math'
+ Sets the options `-fno-math-errno', `-funsafe-math-optimizations',
+ `-ffinite-math-only', `-fno-rounding-math', `-fno-signaling-nans'
+ and `-fcx-limited-range'.
+
+ This option causes the preprocessor macro `__FAST_MATH__' to be
defined.
- This option is not turned on by any '-O' option besides '-Ofast'
- since it can result in incorrect output for programs that depend on
- an exact implementation of IEEE or ISO rules/specifications for
- math functions. It may, however, yield faster code for programs
+ This option is not turned on by any `-O' option besides `-Ofast'
+ since it can result in incorrect output for programs that depend
+ on an exact implementation of IEEE or ISO rules/specifications for
+ math functions. It may, however, yield faster code for programs
that do not require the guarantees of these specifications.
-'-fno-math-errno'
- Do not set 'errno' after calling math functions that are executed
- with a single instruction, e.g., 'sqrt'. A program that relies on
+`-fno-math-errno'
+ Do not set `errno' after calling math functions that are executed
+ with a single instruction, e.g., `sqrt'. A program that relies on
IEEE exceptions for math error handling may want to use this flag
for speed while maintaining IEEE arithmetic compatibility.
- This option is not turned on by any '-O' option since it can result
- in incorrect output for programs that depend on an exact
+ This option is not turned on by any `-O' option since it can
+ result in incorrect output for programs that depend on an exact
implementation of IEEE or ISO rules/specifications for math
- functions. It may, however, yield faster code for programs that do
+ functions. It may, however, yield faster code for programs that do
not require the guarantees of these specifications.
- The default is '-fmath-errno'.
+ The default is `-fmath-errno'.
- On Darwin systems, the math library never sets 'errno'. There is
+ On Darwin systems, the math library never sets `errno'. There is
therefore no reason for the compiler to consider the possibility
- that it might, and '-fno-math-errno' is the default.
-
-'-funsafe-math-optimizations'
+ that it might, and `-fno-math-errno' is the default.
+`-funsafe-math-optimizations'
Allow optimizations for floating-point arithmetic that (a) assume
that arguments and results are valid and (b) may violate IEEE or
ANSI standards. When used at link-time, it may include libraries
or startup files that change the default FPU control word or other
similar optimizations.
- This option is not turned on by any '-O' option since it can result
- in incorrect output for programs that depend on an exact
+ This option is not turned on by any `-O' option since it can
+ result in incorrect output for programs that depend on an exact
implementation of IEEE or ISO rules/specifications for math
- functions. It may, however, yield faster code for programs that do
+ functions. It may, however, yield faster code for programs that do
not require the guarantees of these specifications. Enables
- '-fno-signed-zeros', '-fno-trapping-math', '-fassociative-math' and
- '-freciprocal-math'.
+ `-fno-signed-zeros', `-fno-trapping-math', `-fassociative-math'
+ and `-freciprocal-math'.
- The default is '-fno-unsafe-math-optimizations'.
-
-'-fassociative-math'
+ The default is `-fno-unsafe-math-optimizations'.
+`-fassociative-math'
Allow re-association of operands in series of floating-point
operations. This violates the ISO C and C++ language standard by
- possibly changing computation result. NOTE: re-ordering may change
- the sign of zero as well as ignore NaNs and inhibit or create
- underflow or overflow (and thus cannot be used on code that relies
- on rounding behavior like '(x + 2**52) - 2**52'. May also reorder
- floating-point comparisons and thus may not be used when ordered
- comparisons are required. This option requires that both
- '-fno-signed-zeros' and '-fno-trapping-math' be in effect.
- Moreover, it doesn't make much sense with '-frounding-math'. For
+ possibly changing computation result. NOTE: re-ordering may
+ change the sign of zero as well as ignore NaNs and inhibit or
+ create underflow or overflow (and thus cannot be used on code that
+ relies on rounding behavior like `(x + 2**52) - 2**52'. May also
+ reorder floating-point comparisons and thus may not be used when
+ ordered comparisons are required. This option requires that both
+ `-fno-signed-zeros' and `-fno-trapping-math' be in effect.
+ Moreover, it doesn't make much sense with `-frounding-math'. For
Fortran the option is automatically enabled when both
- '-fno-signed-zeros' and '-fno-trapping-math' are in effect.
-
- The default is '-fno-associative-math'.
+ `-fno-signed-zeros' and `-fno-trapping-math' are in effect.
-'-freciprocal-math'
+ The default is `-fno-associative-math'.
+`-freciprocal-math'
Allow the reciprocal of a value to be used instead of dividing by
- the value if this enables optimizations. For example 'x / y' can
- be replaced with 'x * (1/y)', which is useful if '(1/y)' is subject
- to common subexpression elimination. Note that this loses
+ the value if this enables optimizations. For example `x / y' can
+ be replaced with `x * (1/y)', which is useful if `(1/y)' is
+ subject to common subexpression elimination. Note that this loses
precision and increases the number of flops operating on the value.
- The default is '-fno-reciprocal-math'.
+ The default is `-fno-reciprocal-math'.
-'-ffinite-math-only'
+`-ffinite-math-only'
Allow optimizations for floating-point arithmetic that assume that
arguments and results are not NaNs or +-Infs.
- This option is not turned on by any '-O' option since it can result
- in incorrect output for programs that depend on an exact
+ This option is not turned on by any `-O' option since it can
+ result in incorrect output for programs that depend on an exact
implementation of IEEE or ISO rules/specifications for math
- functions. It may, however, yield faster code for programs that do
+ functions. It may, however, yield faster code for programs that do
not require the guarantees of these specifications.
- The default is '-fno-finite-math-only'.
+ The default is `-fno-finite-math-only'.
-'-fno-signed-zeros'
+`-fno-signed-zeros'
Allow optimizations for floating-point arithmetic that ignore the
signedness of zero. IEEE arithmetic specifies the behavior of
distinct +0.0 and -0.0 values, which then prohibits simplification
of expressions such as x+0.0 or 0.0*x (even with
- '-ffinite-math-only'). This option implies that the sign of a zero
- result isn't significant.
+ `-ffinite-math-only'). This option implies that the sign of a
+ zero result isn't significant.
- The default is '-fsigned-zeros'.
+ The default is `-fsigned-zeros'.
-'-fno-trapping-math'
+`-fno-trapping-math'
Compile code assuming that floating-point operations cannot
- generate user-visible traps. These traps include division by zero,
- overflow, underflow, inexact result and invalid operation. This
- option requires that '-fno-signaling-nans' be in effect. Setting
- this option may allow faster code if one relies on "non-stop" IEEE
- arithmetic, for example.
-
- This option should never be turned on by any '-O' option since it
- can result in incorrect output for programs that depend on an exact
- implementation of IEEE or ISO rules/specifications for math
+ generate user-visible traps. These traps include division by
+ zero, overflow, underflow, inexact result and invalid operation.
+ This option requires that `-fno-signaling-nans' be in effect.
+ Setting this option may allow faster code if one relies on
+ "non-stop" IEEE arithmetic, for example.
+
+ This option should never be turned on by any `-O' option since it
+ can result in incorrect output for programs that depend on an
+ exact implementation of IEEE or ISO rules/specifications for math
functions.
- The default is '-ftrapping-math'.
+ The default is `-ftrapping-math'.
-'-frounding-math'
+`-frounding-math'
Disable transformations and optimizations that assume default
floating-point rounding behavior. This is round-to-zero for all
- floating point to integer conversions, and round-to-nearest for all
- other arithmetic truncations. This option should be specified for
- programs that change the FP rounding mode dynamically, or that may
- be executed with a non-default rounding mode. This option disables
- constant folding of floating-point expressions at compile time
- (which may be affected by rounding mode) and arithmetic
+ floating point to integer conversions, and round-to-nearest for
+ all other arithmetic truncations. This option should be specified
+ for programs that change the FP rounding mode dynamically, or that
+ may be executed with a non-default rounding mode. This option
+ disables constant folding of floating-point expressions at compile
+ time (which may be affected by rounding mode) and arithmetic
transformations that are unsafe in the presence of sign-dependent
rounding modes.
- The default is '-fno-rounding-math'.
+ The default is `-fno-rounding-math'.
This option is experimental and does not currently guarantee to
disable all GCC optimizations that are affected by rounding mode.
Future versions of GCC may provide finer control of this setting
- using C99's 'FENV_ACCESS' pragma. This command-line option will be
- used to specify the default state for 'FENV_ACCESS'.
+ using C99's `FENV_ACCESS' pragma. This command-line option will
+ be used to specify the default state for `FENV_ACCESS'.
-'-fsignaling-nans'
+`-fsignaling-nans'
Compile code assuming that IEEE signaling NaNs may generate
user-visible traps during floating-point operations. Setting this
option disables optimizations that may change the number of
exceptions visible with signaling NaNs. This option implies
- '-ftrapping-math'.
+ `-ftrapping-math'.
- This option causes the preprocessor macro '__SUPPORT_SNAN__' to be
+ This option causes the preprocessor macro `__SUPPORT_SNAN__' to be
defined.
- The default is '-fno-signaling-nans'.
+ The default is `-fno-signaling-nans'.
This option is experimental and does not currently guarantee to
disable all GCC optimizations that affect signaling NaN behavior.
-'-fsingle-precision-constant'
+`-fsingle-precision-constant'
Treat floating-point constants as single precision instead of
implicitly converting them to double-precision constants.
-'-fcx-limited-range'
+`-fcx-limited-range'
When enabled, this option states that a range reduction step is not
needed when performing complex division. Also, there is no
- checking whether the result of a complex multiplication or division
- is 'NaN + I*NaN', with an attempt to rescue the situation in that
- case. The default is '-fno-cx-limited-range', but is enabled by
- '-ffast-math'.
+ checking whether the result of a complex multiplication or
+ division is `NaN + I*NaN', with an attempt to rescue the situation
+ in that case. The default is `-fno-cx-limited-range', but is
+ enabled by `-ffast-math'.
This option controls the default setting of the ISO C99
- 'CX_LIMITED_RANGE' pragma. Nevertheless, the option applies to all
- languages.
+ `CX_LIMITED_RANGE' pragma. Nevertheless, the option applies to
+ all languages.
-'-fcx-fortran-rules'
+`-fcx-fortran-rules'
Complex multiplication and division follow Fortran rules. Range
reduction is done as part of complex division, but there is no
- checking whether the result of a complex multiplication or division
- is 'NaN + I*NaN', with an attempt to rescue the situation in that
- case.
+ checking whether the result of a complex multiplication or
+ division is `NaN + I*NaN', with an attempt to rescue the situation
+ in that case.
+
+ The default is `-fno-cx-fortran-rules'.
- The default is '-fno-cx-fortran-rules'.
The following options control optimizations that may improve
-performance, but are not enabled by any '-O' options. This section
+performance, but are not enabled by any `-O' options. This section
includes experimental options that may produce broken code.
-'-fbranch-probabilities'
- After running a program compiled with '-fprofile-arcs' (*note
- Options for Debugging Your Program or 'gcc': Debugging Options.),
- you can compile it a second time using '-fbranch-probabilities', to
- improve optimizations based on the number of times each branch was
- taken. When a program compiled with '-fprofile-arcs' exits, it
- saves arc execution counts to a file called 'SOURCENAME.gcda' for
- each source file. The information in this data file is very
+`-fbranch-probabilities'
+ After running a program compiled with `-fprofile-arcs' (*note
+ Options for Debugging Your Program or `gcc': Debugging Options.),
+ you can compile it a second time using `-fbranch-probabilities',
+ to improve optimizations based on the number of times each branch
+ was taken. When a program compiled with `-fprofile-arcs' exits,
+ it saves arc execution counts to a file called `SOURCENAME.gcda'
+ for each source file. The information in this data file is very
dependent on the structure of the generated code, so you must use
the same source code and the same optimization options for both
compilations.
- With '-fbranch-probabilities', GCC puts a 'REG_BR_PROB' note on
- each 'JUMP_INSN' and 'CALL_INSN'. These can be used to improve
+ With `-fbranch-probabilities', GCC puts a `REG_BR_PROB' note on
+ each `JUMP_INSN' and `CALL_INSN'. These can be used to improve
optimization. Currently, they are only used in one place: in
- 'reorg.c', instead of guessing which path a branch is most likely
- to take, the 'REG_BR_PROB' values are used to exactly determine
+ `reorg.c', instead of guessing which path a branch is most likely
+ to take, the `REG_BR_PROB' values are used to exactly determine
which path is taken more often.
-'-fprofile-values'
- If combined with '-fprofile-arcs', it adds code so that some data
+`-fprofile-values'
+ If combined with `-fprofile-arcs', it adds code so that some data
about values of expressions in the program is gathered.
- With '-fbranch-probabilities', it reads back the data gathered from
- profiling values of expressions for usage in optimizations.
+ With `-fbranch-probabilities', it reads back the data gathered
+ from profiling values of expressions for usage in optimizations.
- Enabled with '-fprofile-generate' and '-fprofile-use'.
+ Enabled with `-fprofile-generate' and `-fprofile-use'.
-'-fprofile-reorder-functions'
- Function reordering based on profile instrumentation collects first
- time of execution of a function and orders these functions in
- ascending order.
+`-fprofile-reorder-functions'
+ Function reordering based on profile instrumentation collects
+ first time of execution of a function and orders these functions
+ in ascending order.
- Enabled with '-fprofile-use'.
+ Enabled with `-fprofile-use'.
-'-fvpt'
- If combined with '-fprofile-arcs', this option instructs the
+`-fvpt'
+ If combined with `-fprofile-arcs', this option instructs the
compiler to add code to gather information about values of
expressions.
- With '-fbranch-probabilities', it reads back the data gathered and
+ With `-fbranch-probabilities', it reads back the data gathered and
actually performs the optimizations based on them. Currently the
optimizations include specialization of division operations using
the knowledge about the value of the denominator.
-'-frename-registers'
+`-frename-registers'
Attempt to avoid false dependencies in scheduled code by making use
of registers left over after register allocation. This
optimization most benefits processors with lots of registers.
@@ -8956,58 +9020,58 @@ includes experimental options that may produce broken code.
however, it can make debugging impossible, since variables no
longer stay in a "home register".
- Enabled by default with '-funroll-loops' and '-fpeel-loops'.
+ Enabled by default with `-funroll-loops' and `-fpeel-loops'.
-'-fschedule-fusion'
+`-fschedule-fusion'
Performs a target dependent pass over the instruction stream to
schedule instructions of same type together because target machine
can execute them more efficiently if they are adjacent to each
other in the instruction flow.
- Enabled at levels '-O2', '-O3', '-Os'.
+ Enabled at levels `-O2', `-O3', `-Os'.
-'-ftracer'
+`-ftracer'
Perform tail duplication to enlarge superblock size. This
- transformation simplifies the control flow of the function allowing
- other optimizations to do a better job.
+ transformation simplifies the control flow of the function
+ allowing other optimizations to do a better job.
- Enabled with '-fprofile-use'.
+ Enabled with `-fprofile-use'.
-'-funroll-loops'
+`-funroll-loops'
Unroll loops whose number of iterations can be determined at
- compile time or upon entry to the loop. '-funroll-loops' implies
- '-frerun-cse-after-loop', '-fweb' and '-frename-registers'. It
- also turns on complete loop peeling (i.e. complete removal of loops
- with a small constant number of iterations). This option makes
- code larger, and may or may not make it run faster.
+ compile time or upon entry to the loop. `-funroll-loops' implies
+ `-frerun-cse-after-loop', `-fweb' and `-frename-registers'. It
+ also turns on complete loop peeling (i.e. complete removal of
+ loops with a small constant number of iterations). This option
+ makes code larger, and may or may not make it run faster.
- Enabled with '-fprofile-use'.
+ Enabled with `-fprofile-use'.
-'-funroll-all-loops'
+`-funroll-all-loops'
Unroll all loops, even if their number of iterations is uncertain
when the loop is entered. This usually makes programs run more
- slowly. '-funroll-all-loops' implies the same options as
- '-funroll-loops'.
+ slowly. `-funroll-all-loops' implies the same options as
+ `-funroll-loops'.
-'-fpeel-loops'
+`-fpeel-loops'
Peels loops for which there is enough information that they do not
roll much (from profile feedback). It also turns on complete loop
peeling (i.e. complete removal of loops with small constant number
of iterations).
- Enabled with '-fprofile-use'.
+ Enabled with `-fprofile-use'.
-'-fmove-loop-invariants'
+`-fmove-loop-invariants'
Enables the loop invariant motion pass in the RTL loop optimizer.
- Enabled at level '-O1'
+ Enabled at level `-O1'
-'-funswitch-loops'
+`-funswitch-loops'
Move branches with loop invariant conditions out of the loop, with
duplicates of the loop on both branches (modified according to
result of the condition).
-'-ffunction-sections'
-'-fdata-sections'
+`-ffunction-sections'
+`-fdata-sections'
Place each function or data item into its own section in the output
file if the target supports arbitrary sections. The name of the
function or the name of the data item determines the section's name
@@ -9021,64 +9085,64 @@ includes experimental options that may produce broken code.
Only use these options when there are significant benefits from
doing so. When you specify these options, the assembler and linker
- create larger object and executable files and are also slower. You
- cannot use 'gprof' on all systems if you specify this option, and
- you may have problems with debugging if you specify both this
- option and '-g'.
+ create larger object and executable files and are also slower.
+ You cannot use `gprof' on all systems if you specify this option,
+ and you may have problems with debugging if you specify both this
+ option and `-g'.
-'-fbranch-target-load-optimize'
+`-fbranch-target-load-optimize'
Perform branch target register load optimization before prologue /
epilogue threading. The use of target registers can typically be
exposed only during reload, thus hoisting loads out of loops and
doing inter-block scheduling needs a separate optimization pass.
-'-fbranch-target-load-optimize2'
+`-fbranch-target-load-optimize2'
Perform branch target register load optimization after prologue /
epilogue threading.
-'-fbtr-bb-exclusive'
+`-fbtr-bb-exclusive'
When performing branch target register load optimization, don't
reuse branch target registers within any basic block.
-'-fstack-protector'
+`-fstack-protector'
Emit extra code to check for buffer overflows, such as stack
smashing attacks. This is done by adding a guard variable to
functions with vulnerable objects. This includes functions that
- call 'alloca', and functions with buffers larger than 8 bytes. The
- guards are initialized when a function is entered and then checked
- when the function exits. If a guard check fails, an error message
- is printed and the program exits.
+ call `alloca', and functions with buffers larger than 8 bytes.
+ The guards are initialized when a function is entered and then
+ checked when the function exits. If a guard check fails, an error
+ message is printed and the program exits.
-'-fstack-protector-all'
- Like '-fstack-protector' except that all functions are protected.
+`-fstack-protector-all'
+ Like `-fstack-protector' except that all functions are protected.
-'-fstack-protector-strong'
- Like '-fstack-protector' but includes additional functions to be
+`-fstack-protector-strong'
+ Like `-fstack-protector' but includes additional functions to be
protected -- those that have local array definitions, or have
references to local frame addresses.
-'-fstack-protector-explicit'
- Like '-fstack-protector' but only protects those functions which
- have the 'stack_protect' attribute
+`-fstack-protector-explicit'
+ Like `-fstack-protector' but only protects those functions which
+ have the `stack_protect' attribute
-'-fstdarg-opt'
+`-fstdarg-opt'
Optimize the prologue of variadic argument functions with respect
to usage of those arguments.
-'-fsection-anchors'
+`-fsection-anchors'
Try to reduce the number of symbolic address calculations by using
shared "anchor" symbols to address nearby objects. This
- transformation can help to reduce the number of GOT entries and GOT
- accesses on some targets.
+ transformation can help to reduce the number of GOT entries and
+ GOT accesses on some targets.
- For example, the implementation of the following function 'foo':
+ For example, the implementation of the following function `foo':
static int a, b, c;
int foo (void) { return a + b + c; }
usually calculates the addresses of all three variables, but if you
- compile it with '-fsection-anchors', it accesses the variables from
- a common anchor point instead. The effect is similar to the
+ compile it with `-fsection-anchors', it accesses the variables
+ from a common anchor point instead. The effect is similar to the
following pseudocode (which isn't valid C):
int foo (void)
@@ -9089,12 +9153,12 @@ includes experimental options that may produce broken code.
Not all targets support this option.
-'--param NAME=VALUE'
+`--param NAME=VALUE'
In some places, GCC uses various constants to control the amount of
optimization that is done. For example, GCC does not inline
functions that contain more than a certain number of instructions.
You can control some of these constants on the command line using
- the '--param' option.
+ the `--param' option.
The names of specific parameters, and the meaning of the values,
are tied to the internals of the compiler, and are subject to
@@ -9103,32 +9167,32 @@ includes experimental options that may produce broken code.
In each case, the VALUE is an integer. The allowable choices for
NAME are:
- 'predictable-branch-outcome'
+ `predictable-branch-outcome'
When branch is predicted to be taken with probability lower
than this threshold (in percent), then it is considered well
- predictable. The default is 10.
+ predictable. The default is 10.
- 'max-crossjump-edges'
+ `max-crossjump-edges'
The maximum number of incoming edges to consider for
- cross-jumping. The algorithm used by '-fcrossjumping' is
+ cross-jumping. The algorithm used by `-fcrossjumping' is
O(N^2) in the number of edges incoming to each block.
Increasing values mean more aggressive optimization, making
the compilation time increase with probably small improvement
in executable size.
- 'min-crossjump-insns'
- The minimum number of instructions that must be matched at the
- end of two blocks before cross-jumping is performed on them.
- This value is ignored in the case where all instructions in
- the block being cross-jumped from are matched. The default
- value is 5.
+ `min-crossjump-insns'
+ The minimum number of instructions that must be matched at
+ the end of two blocks before cross-jumping is performed on
+ them. This value is ignored in the case where all
+ instructions in the block being cross-jumped from are
+ matched. The default value is 5.
- 'max-grow-copy-bb-insns'
+ `max-grow-copy-bb-insns'
The maximum code size expansion factor when copying basic
blocks instead of jumping. The expansion is relative to a
jump instruction. The default value is 8.
- 'max-goto-duplication-insns'
+ `max-goto-duplication-insns'
The maximum number of instructions to duplicate to a block
that jumps to a computed goto. To avoid O(N^2) behavior in a
number of passes, GCC factors computed gotos early in the
@@ -9137,7 +9201,7 @@ includes experimental options that may produce broken code.
than max-goto-duplication-insns are unfactored. The default
value is 8.
- 'max-delay-slot-insn-search'
+ `max-delay-slot-insn-search'
The maximum number of instructions to consider when looking
for an instruction to fill a delay slot. If more than this
arbitrary number of instructions are searched, the time
@@ -9146,187 +9210,189 @@ includes experimental options that may produce broken code.
optimization, making the compilation time increase with
probably small improvement in execution time.
- 'max-delay-slot-live-search'
+ `max-delay-slot-live-search'
When trying to fill delay slots, the maximum number of
- instructions to consider when searching for a block with valid
- live register information. Increasing this arbitrarily chosen
- value means more aggressive optimization, increasing the
- compilation time. This parameter should be removed when the
- delay slot code is rewritten to maintain the control-flow
+ instructions to consider when searching for a block with
+ valid live register information. Increasing this arbitrarily
+ chosen value means more aggressive optimization, increasing
+ the compilation time. This parameter should be removed when
+ the delay slot code is rewritten to maintain the control-flow
graph.
- 'max-gcse-memory'
- The approximate maximum amount of memory that can be allocated
- in order to perform the global common subexpression
+ `max-gcse-memory'
+ The approximate maximum amount of memory that can be
+ allocated in order to perform the global common subexpression
elimination optimization. If more memory than specified is
required, the optimization is not done.
- 'max-gcse-insertion-ratio'
+ `max-gcse-insertion-ratio'
If the ratio of expression insertions to deletions is larger
than this value for any expression, then RTL PRE inserts or
removes the expression and thus leaves partially redundant
computations in the instruction stream. The default value is
20.
- 'max-pending-list-length'
+ `max-pending-list-length'
The maximum number of pending dependencies scheduling allows
before flushing the current state and starting over. Large
functions with few branches or calls can create excessively
large lists which needlessly consume memory and resources.
- 'max-modulo-backtrack-attempts'
+ `max-modulo-backtrack-attempts'
The maximum number of backtrack attempts the scheduler should
make when modulo scheduling a loop. Larger values can
exponentially increase compilation time.
- 'max-inline-insns-single'
- Several parameters control the tree inliner used in GCC. This
- number sets the maximum number of instructions (counted in
- GCC's internal representation) in a single function that the
- tree inliner considers for inlining. This only affects
+ `max-inline-insns-single'
+ Several parameters control the tree inliner used in GCC.
+ This number sets the maximum number of instructions (counted
+ in GCC's internal representation) in a single function that
+ the tree inliner considers for inlining. This only affects
functions declared inline and methods implemented in a class
declaration (C++). The default value is 400.
- 'max-inline-insns-auto'
- When you use '-finline-functions' (included in '-O3'), a lot
+ `max-inline-insns-auto'
+ When you use `-finline-functions' (included in `-O3'), a lot
of functions that would otherwise not be considered for
inlining by the compiler are investigated. To those
functions, a different (more restrictive) limit compared to
functions declared inline can be applied. The default value
is 40.
- 'inline-min-speedup'
+ `inline-min-speedup'
When estimated performance improvement of caller + callee
runtime exceeds this threshold (in precent), the function can
- be inlined regardless the limit on '--param
- max-inline-insns-single' and '--param max-inline-insns-auto'.
+ be inlined regardless the limit on `--param
+ max-inline-insns-single' and `--param max-inline-insns-auto'.
- 'large-function-insns'
+ `large-function-insns'
The limit specifying really large functions. For functions
- larger than this limit after inlining, inlining is constrained
- by '--param large-function-growth'. This parameter is useful
- primarily to avoid extreme compilation time caused by
- non-linear algorithms used by the back end. The default value
- is 2700.
+ larger than this limit after inlining, inlining is
+ constrained by `--param large-function-growth'. This
+ parameter is useful primarily to avoid extreme compilation
+ time caused by non-linear algorithms used by the back end.
+ The default value is 2700.
- 'large-function-growth'
+ `large-function-growth'
Specifies maximal growth of large function caused by inlining
in percents. The default value is 100 which limits large
function growth to 2.0 times the original size.
- 'large-unit-insns'
- The limit specifying large translation unit. Growth caused by
- inlining of units larger than this limit is limited by
- '--param inline-unit-growth'. For small units this might be
+ `large-unit-insns'
+ The limit specifying large translation unit. Growth caused
+ by inlining of units larger than this limit is limited by
+ `--param inline-unit-growth'. For small units this might be
too tight. For example, consider a unit consisting of
- function A that is inline and B that just calls A three times.
- If B is small relative to A, the growth of unit is 300\% and
- yet such inlining is very sane. For very large units
- consisting of small inlineable functions, however, the overall
- unit growth limit is needed to avoid exponential explosion of
- code size. Thus for smaller units, the size is increased to
- '--param large-unit-insns' before applying '--param
- inline-unit-growth'. The default is 10000.
-
- 'inline-unit-growth'
+ function A that is inline and B that just calls A three
+ times. If B is small relative to A, the growth of unit is
+ 300\% and yet such inlining is very sane. For very large
+ units consisting of small inlineable functions, however, the
+ overall unit growth limit is needed to avoid exponential
+ explosion of code size. Thus for smaller units, the size is
+ increased to `--param large-unit-insns' before applying
+ `--param inline-unit-growth'. The default is 10000.
+
+ `inline-unit-growth'
Specifies maximal overall growth of the compilation unit
- caused by inlining. The default value is 20 which limits unit
- growth to 1.2 times the original size. Cold functions (either
- marked cold via an attribute or by profile feedback) are not
- accounted into the unit size.
+ caused by inlining. The default value is 20 which limits
+ unit growth to 1.2 times the original size. Cold functions
+ (either marked cold via an attribute or by profile feedback)
+ are not accounted into the unit size.
- 'ipcp-unit-growth'
+ `ipcp-unit-growth'
Specifies maximal overall growth of the compilation unit
caused by interprocedural constant propagation. The default
- value is 10 which limits unit growth to 1.1 times the original
- size.
+ value is 10 which limits unit growth to 1.1 times the
+ original size.
- 'large-stack-frame'
+ `large-stack-frame'
The limit specifying large stack frames. While inlining the
- algorithm is trying to not grow past this limit too much. The
- default value is 256 bytes.
+ algorithm is trying to not grow past this limit too much.
+ The default value is 256 bytes.
- 'large-stack-frame-growth'
+ `large-stack-frame-growth'
Specifies maximal growth of large stack frames caused by
inlining in percents. The default value is 1000 which limits
large stack frame growth to 11 times the original size.
- 'max-inline-insns-recursive'
- 'max-inline-insns-recursive-auto'
+ `max-inline-insns-recursive'
+ `max-inline-insns-recursive-auto'
Specifies the maximum number of instructions an out-of-line
copy of a self-recursive inline function can grow into by
performing recursive inlining.
- '--param max-inline-insns-recursive' applies to functions
- declared inline. For functions not declared inline, recursive
- inlining happens only when '-finline-functions' (included in
- '-O3') is enabled; '--param max-inline-insns-recursive-auto'
- applies instead. The default value is 450.
+ `--param max-inline-insns-recursive' applies to functions
+ declared inline. For functions not declared inline,
+ recursive inlining happens only when `-finline-functions'
+ (included in `-O3') is enabled; `--param
+ max-inline-insns-recursive-auto' applies instead. The
+ default value is 450.
- 'max-inline-recursive-depth'
- 'max-inline-recursive-depth-auto'
+ `max-inline-recursive-depth'
+ `max-inline-recursive-depth-auto'
Specifies the maximum recursion depth used for recursive
inlining.
- '--param max-inline-recursive-depth' applies to functions
- declared inline. For functions not declared inline, recursive
- inlining happens only when '-finline-functions' (included in
- '-O3') is enabled; '--param max-inline-recursive-depth-auto'
- applies instead. The default value is 8.
+ `--param max-inline-recursive-depth' applies to functions
+ declared inline. For functions not declared inline,
+ recursive inlining happens only when `-finline-functions'
+ (included in `-O3') is enabled; `--param
+ max-inline-recursive-depth-auto' applies instead. The
+ default value is 8.
- 'min-inline-recursive-probability'
- Recursive inlining is profitable only for function having deep
- recursion in average and can hurt for function having little
- recursion depth by increasing the prologue size or complexity
- of function body to other optimizers.
+ `min-inline-recursive-probability'
+ Recursive inlining is profitable only for function having
+ deep recursion in average and can hurt for function having
+ little recursion depth by increasing the prologue size or
+ complexity of function body to other optimizers.
- When profile feedback is available (see '-fprofile-generate')
+ When profile feedback is available (see `-fprofile-generate')
the actual recursion depth can be guessed from probability
that function recurses via a given call expression. This
parameter limits inlining only to call expressions whose
probability exceeds the given threshold (in percents). The
default value is 10.
- 'early-inlining-insns'
+ `early-inlining-insns'
Specify growth that the early inliner can make. In effect it
increases the amount of inlining for code having a large
abstraction penalty. The default value is 14.
- 'max-early-inliner-iterations'
+ `max-early-inliner-iterations'
Limit of iterations of the early inliner. This basically
bounds the number of nested indirect calls the early inliner
can resolve. Deeper chains are still handled by late
inlining.
- 'comdat-sharing-probability'
+ `comdat-sharing-probability'
Probability (in percent) that C++ inline function with comdat
visibility are shared across multiple compilation units. The
default value is 20.
- 'profile-func-internal-id'
+ `profile-func-internal-id'
A parameter to control whether to use function internal id in
- profile database lookup. If the value is 0, the compiler uses
+ profile database lookup. If the value is 0, the compiler uses
an id that is based on function assembler name and filename,
which makes old profile data more tolerant to source changes
such as function reordering etc. The default value is 0.
- 'min-vect-loop-bound'
+ `min-vect-loop-bound'
The minimum number of iterations under which loops are not
- vectorized when '-ftree-vectorize' is used. The number of
+ vectorized when `-ftree-vectorize' is used. The number of
iterations after vectorization needs to be greater than the
value specified by this option to allow vectorization. The
default value is 0.
- 'gcse-cost-distance-ratio'
+ `gcse-cost-distance-ratio'
Scaling factor in calculation of maximum distance an
expression can be moved by GCSE optimizations. This is
currently supported only in the code hoisting pass. The
bigger the ratio, the more aggressive code hoisting is with
simple expressions, i.e., the expressions that have cost less
- than 'gcse-unrestricted-cost'. Specifying 0 disables hoisting
- of simple expressions. The default value is 10.
+ than `gcse-unrestricted-cost'. Specifying 0 disables
+ hoisting of simple expressions. The default value is 10.
- 'gcse-unrestricted-cost'
+ `gcse-unrestricted-cost'
Cost, roughly measured as the cost of a single typical machine
instruction, at which GCSE optimizations do not constrain the
distance an expression can travel. This is currently
@@ -9335,150 +9401,150 @@ includes experimental options that may produce broken code.
allows all expressions to travel unrestricted distances. The
default value is 3.
- 'max-hoist-depth'
+ `max-hoist-depth'
The depth of search in the dominator tree for expressions to
hoist. This is used to avoid quadratic behavior in hoisting
algorithm. The value of 0 does not limit on the search, but
may slow down compilation of huge functions. The default
value is 30.
- 'max-tail-merge-comparisons'
+ `max-tail-merge-comparisons'
The maximum amount of similar bbs to compare a bb with. This
- is used to avoid quadratic behavior in tree tail merging. The
- default value is 10.
+ is used to avoid quadratic behavior in tree tail merging.
+ The default value is 10.
- 'max-tail-merge-iterations'
+ `max-tail-merge-iterations'
The maximum amount of iterations of the pass over the
- function. This is used to limit compilation time in tree tail
- merging. The default value is 2.
+ function. This is used to limit compilation time in tree
+ tail merging. The default value is 2.
- 'max-unrolled-insns'
+ `max-unrolled-insns'
The maximum number of instructions that a loop may have to be
unrolled. If a loop is unrolled, this parameter also
determines how many times the loop code is unrolled.
- 'max-average-unrolled-insns'
+ `max-average-unrolled-insns'
The maximum number of instructions biased by probabilities of
their execution that a loop may have to be unrolled. If a
loop is unrolled, this parameter also determines how many
times the loop code is unrolled.
- 'max-unroll-times'
+ `max-unroll-times'
The maximum number of unrollings of a single loop.
- 'max-peeled-insns'
+ `max-peeled-insns'
The maximum number of instructions that a loop may have to be
peeled. If a loop is peeled, this parameter also determines
how many times the loop code is peeled.
- 'max-peel-times'
+ `max-peel-times'
The maximum number of peelings of a single loop.
- 'max-peel-branches'
+ `max-peel-branches'
The maximum number of branches on the hot path through the
peeled sequence.
- 'max-completely-peeled-insns'
+ `max-completely-peeled-insns'
The maximum number of insns of a completely peeled loop.
- 'max-completely-peel-times'
+ `max-completely-peel-times'
The maximum number of iterations of a loop to be suitable for
complete peeling.
- 'max-completely-peel-loop-nest-depth'
+ `max-completely-peel-loop-nest-depth'
The maximum depth of a loop nest suitable for complete
peeling.
- 'max-unswitch-insns'
+ `max-unswitch-insns'
The maximum number of insns of an unswitched loop.
- 'max-unswitch-level'
+ `max-unswitch-level'
The maximum number of branches unswitched in a single loop.
- 'lim-expensive'
+ `lim-expensive'
The minimum cost of an expensive expression in the loop
invariant motion.
- 'iv-consider-all-candidates-bound'
+ `iv-consider-all-candidates-bound'
Bound on number of candidates for induction variables, below
which all candidates are considered for each use in induction
variable optimizations. If there are more candidates than
this, only the most relevant ones are considered to avoid
quadratic time complexity.
- 'iv-max-considered-uses'
+ `iv-max-considered-uses'
The induction variable optimizations give up on loops that
contain more induction variable uses.
- 'iv-always-prune-cand-set-bound'
+ `iv-always-prune-cand-set-bound'
If the number of candidates in the set is smaller than this
value, always try to remove unnecessary ivs from the set when
adding a new one.
- 'scev-max-expr-size'
+ `scev-max-expr-size'
Bound on size of expressions used in the scalar evolutions
analyzer. Large expressions slow the analyzer.
- 'scev-max-expr-complexity'
+ `scev-max-expr-complexity'
Bound on the complexity of the expressions in the scalar
evolutions analyzer. Complex expressions slow the analyzer.
- 'omega-max-vars'
+ `omega-max-vars'
The maximum number of variables in an Omega constraint system.
The default value is 128.
- 'omega-max-geqs'
+ `omega-max-geqs'
The maximum number of inequalities in an Omega constraint
system. The default value is 256.
- 'omega-max-eqs'
+ `omega-max-eqs'
The maximum number of equalities in an Omega constraint
system. The default value is 128.
- 'omega-max-wild-cards'
- The maximum number of wildcard variables that the Omega solver
- is able to insert. The default value is 18.
+ `omega-max-wild-cards'
+ The maximum number of wildcard variables that the Omega
+ solver is able to insert. The default value is 18.
- 'omega-hash-table-size'
+ `omega-hash-table-size'
The size of the hash table in the Omega solver. The default
value is 550.
- 'omega-max-keys'
+ `omega-max-keys'
The maximal number of keys used by the Omega solver. The
default value is 500.
- 'omega-eliminate-redundant-constraints'
+ `omega-eliminate-redundant-constraints'
When set to 1, use expensive methods to eliminate all
redundant constraints. The default value is 0.
- 'vect-max-version-for-alignment-checks'
+ `vect-max-version-for-alignment-checks'
The maximum number of run-time checks that can be performed
when doing loop versioning for alignment in the vectorizer.
- 'vect-max-version-for-alias-checks'
+ `vect-max-version-for-alias-checks'
The maximum number of run-time checks that can be performed
when doing loop versioning for alias in the vectorizer.
- 'vect-max-peeling-for-alignment'
+ `vect-max-peeling-for-alignment'
The maximum number of loop peels to enhance access alignment
- for vectorizer. Value -1 means 'no limit'.
+ for vectorizer. Value -1 means 'no limit'.
- 'max-iterations-to-track'
+ `max-iterations-to-track'
The maximum number of iterations of a loop the brute-force
- algorithm for analysis of the number of iterations of the loop
- tries to evaluate.
+ algorithm for analysis of the number of iterations of the
+ loop tries to evaluate.
- 'hot-bb-count-ws-permille'
+ `hot-bb-count-ws-permille'
A basic block profile count is considered hot if it
- contributes to the given permillage (i.e. 0...1000) of the
+ contributes to the given permillage (i.e. 0...1000) of the
entire profiled execution.
- 'hot-bb-frequency-fraction'
+ `hot-bb-frequency-fraction'
Select fraction of the entry block frequency of executions of
basic block in function given basic block needs to have to be
considered hot.
- 'max-predicted-iterations'
+ `max-predicted-iterations'
The maximum number of loop iterations we predict statically.
This is useful in cases where a function contains a single
loop with known bound and another loop with unknown bound.
@@ -9487,68 +9553,62 @@ includes experimental options that may produce broken code.
means that the loop without bounds appears artificially cold
relative to the other one.
- 'builtin-expect-probability'
- Control the probability of the expression having the specified
- value. This parameter takes a percentage (i.e. 0 ... 100)
- as input. The default probability of 90 is obtained
+ `builtin-expect-probability'
+ Control the probability of the expression having the
+ specified value. This parameter takes a percentage (i.e. 0
+ ... 100) as input. The default probability of 90 is obtained
empirically.
- 'align-threshold'
-
+ `align-threshold'
Select fraction of the maximal frequency of executions of a
basic block in a function to align the basic block.
- 'align-loop-iterations'
-
+ `align-loop-iterations'
A loop expected to iterate at least the selected number of
iterations is aligned.
- 'tracer-dynamic-coverage'
- 'tracer-dynamic-coverage-feedback'
-
+ `tracer-dynamic-coverage'
+ `tracer-dynamic-coverage-feedback'
This value is used to limit superblock formation once the
given percentage of executed instructions is covered. This
limits unnecessary code size expansion.
- The 'tracer-dynamic-coverage-feedback' parameter is used only
+ The `tracer-dynamic-coverage-feedback' parameter is used only
when profile feedback is available. The real profiles (as
opposed to statically estimated ones) are much less balanced
allowing the threshold to be larger value.
- 'tracer-max-code-growth'
+ `tracer-max-code-growth'
Stop tail duplication once code growth has reached given
- percentage. This is a rather artificial limit, as most of the
- duplicates are eliminated later in cross jumping, so it may be
- set to much higher values than is the desired code growth.
-
- 'tracer-min-branch-ratio'
+ percentage. This is a rather artificial limit, as most of
+ the duplicates are eliminated later in cross jumping, so it
+ may be set to much higher values than is the desired code
+ growth.
+ `tracer-min-branch-ratio'
Stop reverse growth when the reverse probability of best edge
is less than this threshold (in percent).
- 'tracer-min-branch-ratio'
- 'tracer-min-branch-ratio-feedback'
-
+ `tracer-min-branch-ratio'
+ `tracer-min-branch-ratio-feedback'
Stop forward growth if the best edge has probability lower
than this threshold.
- Similarly to 'tracer-dynamic-coverage' two values are present,
- one for compilation for profile feedback and one for
+ Similarly to `tracer-dynamic-coverage' two values are
+ present, one for compilation for profile feedback and one for
compilation without. The value for compilation with profile
feedback needs to be more conservative (higher) in order to
make tracer effective.
- 'max-cse-path-length'
-
+ `max-cse-path-length'
The maximum number of basic blocks on path that CSE considers.
The default is 10.
- 'max-cse-insns'
+ `max-cse-insns'
The maximum number of instructions CSE processes before
flushing. The default is 1000.
- 'ggc-min-expand'
-
+ `ggc-min-expand'
GCC uses a garbage collector to manage its own memory
allocation. This parameter specifies the minimum percentage
by which the garbage collector's heap should be allowed to
@@ -9556,20 +9616,20 @@ includes experimental options that may produce broken code.
compilation speed; it has no effect on code generation.
The default is 30% + 70% * (RAM/1GB) with an upper bound of
- 100% when RAM >= 1GB. If 'getrlimit' is available, the notion
- of "RAM" is the smallest of actual RAM and 'RLIMIT_DATA' or
- 'RLIMIT_AS'. If GCC is not able to calculate RAM on a
- particular platform, the lower bound of 30% is used. Setting
- this parameter and 'ggc-min-heapsize' to zero causes a full
- collection to occur at every opportunity. This is extremely
- slow, but can be useful for debugging.
-
- 'ggc-min-heapsize'
-
+ 100% when RAM >= 1GB. If `getrlimit' is available, the
+ notion of "RAM" is the smallest of actual RAM and
+ `RLIMIT_DATA' or `RLIMIT_AS'. If GCC is not able to
+ calculate RAM on a particular platform, the lower bound of
+ 30% is used. Setting this parameter and `ggc-min-heapsize'
+ to zero causes a full collection to occur at every
+ opportunity. This is extremely slow, but can be useful for
+ debugging.
+
+ `ggc-min-heapsize'
Minimum size of the garbage collector's heap before it begins
bothering to collect garbage. The first collection occurs
- after the heap expands by 'ggc-min-expand'% beyond
- 'ggc-min-heapsize'. Again, tuning this may improve
+ after the heap expands by `ggc-min-expand'% beyond
+ `ggc-min-heapsize'. Again, tuning this may improve
compilation speed, and has no effect on code generation.
The default is the smaller of RAM/8, RLIMIT_RSS, or a limit
@@ -9579,168 +9639,168 @@ includes experimental options that may produce broken code.
to calculate RAM on a particular platform, the lower bound is
used. Setting this parameter very large effectively disables
garbage collection. Setting this parameter and
- 'ggc-min-expand' to zero causes a full collection to occur at
+ `ggc-min-expand' to zero causes a full collection to occur at
every opportunity.
- 'max-reload-search-insns'
+ `max-reload-search-insns'
The maximum number of instruction reload should look backward
for equivalent register. Increasing values mean more
aggressive optimization, making the compilation time increase
with probably slightly better performance. The default value
is 100.
- 'max-cselib-memory-locations'
- The maximum number of memory locations cselib should take into
- account. Increasing values mean more aggressive optimization,
- making the compilation time increase with probably slightly
- better performance. The default value is 500.
-
- 'reorder-blocks-duplicate'
- 'reorder-blocks-duplicate-feedback'
+ `max-cselib-memory-locations'
+ The maximum number of memory locations cselib should take
+ into account. Increasing values mean more aggressive
+ optimization, making the compilation time increase with
+ probably slightly better performance. The default value is
+ 500.
+ `reorder-blocks-duplicate'
+ `reorder-blocks-duplicate-feedback'
Used by the basic block reordering pass to decide whether to
use unconditional branch or duplicate the code on its
destination. Code is duplicated when its estimated size is
smaller than this value multiplied by the estimated size of
unconditional jump in the hot spots of the program.
- The 'reorder-block-duplicate-feedback' parameter is used only
+ The `reorder-block-duplicate-feedback' parameter is used only
when profile feedback is available. It may be set to higher
- values than 'reorder-block-duplicate' since information about
+ values than `reorder-block-duplicate' since information about
the hot spots is more accurate.
- 'max-sched-ready-insns'
+ `max-sched-ready-insns'
The maximum number of instructions ready to be issued the
scheduler should consider at any given time during the first
scheduling pass. Increasing values mean more thorough
searches, making the compilation time increase with probably
little benefit. The default value is 100.
- 'max-sched-region-blocks'
+ `max-sched-region-blocks'
The maximum number of blocks in a region to be considered for
interblock scheduling. The default value is 10.
- 'max-pipeline-region-blocks'
+ `max-pipeline-region-blocks'
The maximum number of blocks in a region to be considered for
pipelining in the selective scheduler. The default value is
15.
- 'max-sched-region-insns'
+ `max-sched-region-insns'
The maximum number of insns in a region to be considered for
interblock scheduling. The default value is 100.
- 'max-pipeline-region-insns'
+ `max-pipeline-region-insns'
The maximum number of insns in a region to be considered for
pipelining in the selective scheduler. The default value is
200.
- 'min-spec-prob'
+ `min-spec-prob'
The minimum probability (in percents) of reaching a source
block for interblock speculative scheduling. The default
value is 40.
- 'max-sched-extend-regions-iters'
+ `max-sched-extend-regions-iters'
The maximum number of iterations through CFG to extend
regions. A value of 0 (the default) disables region
extensions.
- 'max-sched-insn-conflict-delay'
+ `max-sched-insn-conflict-delay'
The maximum conflict delay for an insn to be considered for
speculative motion. The default value is 3.
- 'sched-spec-prob-cutoff'
+ `sched-spec-prob-cutoff'
The minimal probability of speculation success (in percents),
- so that speculative insns are scheduled. The default value is
- 40.
+ so that speculative insns are scheduled. The default value
+ is 40.
- 'sched-spec-state-edge-prob-cutoff'
- The minimum probability an edge must have for the scheduler to
- save its state across it. The default value is 10.
+ `sched-spec-state-edge-prob-cutoff'
+ The minimum probability an edge must have for the scheduler
+ to save its state across it. The default value is 10.
- 'sched-mem-true-dep-cost'
+ `sched-mem-true-dep-cost'
Minimal distance (in CPU cycles) between store and load
targeting same memory locations. The default value is 1.
- 'selsched-max-lookahead'
+ `selsched-max-lookahead'
The maximum size of the lookahead window of selective
scheduling. It is a depth of search for available
instructions. The default value is 50.
- 'selsched-max-sched-times'
+ `selsched-max-sched-times'
The maximum number of times that an instruction is scheduled
during selective scheduling. This is the limit on the number
of iterations through which the instruction may be pipelined.
The default value is 2.
- 'selsched-max-insns-to-rename'
- The maximum number of best instructions in the ready list that
- are considered for renaming in the selective scheduler. The
- default value is 2.
+ `selsched-max-insns-to-rename'
+ The maximum number of best instructions in the ready list
+ that are considered for renaming in the selective scheduler.
+ The default value is 2.
- 'sms-min-sc'
+ `sms-min-sc'
The minimum value of stage count that swing modulo scheduler
generates. The default value is 2.
- 'max-last-value-rtl'
+ `max-last-value-rtl'
The maximum size measured as number of RTLs that can be
- recorded in an expression in combiner for a pseudo register as
- last known value of that register. The default is 10000.
+ recorded in an expression in combiner for a pseudo register
+ as last known value of that register. The default is 10000.
- 'max-combine-insns'
+ `max-combine-insns'
The maximum number of instructions the RTL combiner tries to
- combine. The default value is 2 at '-Og' and 4 otherwise.
+ combine. The default value is 2 at `-Og' and 4 otherwise.
- 'integer-share-limit'
+ `integer-share-limit'
Small integer constants can use a shared data structure,
- reducing the compiler's memory usage and increasing its speed.
- This sets the maximum value of a shared integer constant. The
- default value is 256.
+ reducing the compiler's memory usage and increasing its
+ speed. This sets the maximum value of a shared integer
+ constant. The default value is 256.
- 'ssp-buffer-size'
+ `ssp-buffer-size'
The minimum size of buffers (i.e. arrays) that receive stack
- smashing protection when '-fstack-protection' is used.
+ smashing protection when `-fstack-protection' is used.
- 'min-size-for-stack-sharing'
+ `min-size-for-stack-sharing'
The minimum size of variables taking part in stack slot
- sharing when not optimizing. The default value is 32.
+ sharing when not optimizing. The default value is 32.
- 'max-jump-thread-duplication-stmts'
+ `max-jump-thread-duplication-stmts'
Maximum number of statements allowed in a block that needs to
be duplicated when threading jumps.
- 'max-fields-for-field-sensitive'
+ `max-fields-for-field-sensitive'
Maximum number of fields in a structure treated in a field
sensitive manner during pointer analysis. The default is zero
- for '-O0' and '-O1', and 100 for '-Os', '-O2', and '-O3'.
+ for `-O0' and `-O1', and 100 for `-Os', `-O2', and `-O3'.
- 'prefetch-latency'
+ `prefetch-latency'
Estimate on average number of instructions that are executed
before prefetch finishes. The distance prefetched ahead is
proportional to this constant. Increasing this number may
also lead to less streams being prefetched (see
- 'simultaneous-prefetches').
+ `simultaneous-prefetches').
- 'simultaneous-prefetches'
+ `simultaneous-prefetches'
Maximum number of prefetches that can run at the same time.
- 'l1-cache-line-size'
+ `l1-cache-line-size'
The size of cache line in L1 cache, in bytes.
- 'l1-cache-size'
+ `l1-cache-size'
The size of L1 cache, in kilobytes.
- 'l2-cache-size'
+ `l2-cache-size'
The size of L2 cache, in kilobytes.
- 'min-insn-to-prefetch-ratio'
+ `min-insn-to-prefetch-ratio'
The minimum ratio between the number of instructions and the
number of prefetches to enable prefetching in a loop.
- 'prefetch-min-insn-to-mem-ratio'
+ `prefetch-min-insn-to-mem-ratio'
The minimum ratio between the number of instructions and the
number of memory references to enable prefetching in a loop.
- 'use-canonical-types'
+ `use-canonical-types'
Whether the compiler should use the "canonical" type system.
By default, this should always be 1, which uses a more
efficient internal mechanism for comparing types in C++ and
@@ -9748,15 +9808,15 @@ includes experimental options that may produce broken code.
are causing compilation failures, set this value to 0 to
disable canonical types.
- 'switch-conversion-max-branch-ratio'
- Switch initialization conversion refuses to create arrays that
- are bigger than 'switch-conversion-max-branch-ratio' times the
- number of branches in the switch.
+ `switch-conversion-max-branch-ratio'
+ Switch initialization conversion refuses to create arrays
+ that are bigger than `switch-conversion-max-branch-ratio'
+ times the number of branches in the switch.
- 'max-partial-antic-length'
+ `max-partial-antic-length'
Maximum length of the partial antic set computed during the
tree partial redundancy elimination optimization
- ('-ftree-pre') when optimizing at '-O3' and above. For some
+ (`-ftree-pre') when optimizing at `-O3' and above. For some
sorts of source code the enhanced partial redundancy
elimination optimization can run away, consuming all of the
memory available on the host machine. This parameter sets a
@@ -9764,29 +9824,29 @@ includes experimental options that may produce broken code.
prevents the runaway behavior. Setting a value of 0 for this
parameter allows an unlimited set length.
- 'sccvn-max-scc-size'
+ `sccvn-max-scc-size'
Maximum size of a strongly connected component (SCC) during
SCCVN processing. If this limit is hit, SCCVN processing for
the whole function is not done and optimizations depending on
it are disabled. The default maximum SCC size is 10000.
- 'sccvn-max-alias-queries-per-access'
- Maximum number of alias-oracle queries we perform when looking
- for redundancies for loads and stores. If this limit is hit
- the search is aborted and the load or store is not considered
- redundant. The number of queries is algorithmically limited
- to the number of stores on all paths from the load to the
- function entry. The default maxmimum number of queries is
- 1000.
+ `sccvn-max-alias-queries-per-access'
+ Maximum number of alias-oracle queries we perform when
+ looking for redundancies for loads and stores. If this limit
+ is hit the search is aborted and the load or store is not
+ considered redundant. The number of queries is
+ algorithmically limited to the number of stores on all paths
+ from the load to the function entry. The default maxmimum
+ number of queries is 1000.
- 'ira-max-loops-num'
+ `ira-max-loops-num'
IRA uses regional register allocation by default. If a
function contains more loops than the number given by this
parameter, only at most the given number of the most
frequently-executed loops form regions for regional register
allocation. The default value of the parameter is 100.
- 'ira-max-conflict-table-size'
+ `ira-max-conflict-table-size'
Although IRA uses a sophisticated algorithm to compress the
conflict table, the table can still require excessive amounts
of memory for huge functions. If the conflict table for a
@@ -9796,50 +9856,50 @@ includes experimental options that may produce broken code.
building a pseudo-register conflict table. The default value
of the parameter is 2000.
- 'ira-loop-reserved-regs'
- IRA can be used to evaluate more accurate register pressure in
- loops for decisions to move loop invariants (see '-O3'). The
- number of available registers reserved for some other purposes
- is given by this parameter. The default value of the
- parameter is 2, which is the minimal number of registers
+ `ira-loop-reserved-regs'
+ IRA can be used to evaluate more accurate register pressure
+ in loops for decisions to move loop invariants (see `-O3').
+ The number of available registers reserved for some other
+ purposes is given by this parameter. The default value of
+ the parameter is 2, which is the minimal number of registers
needed by typical instructions. This value is the best found
from numerous experiments.
- 'lra-inheritance-ebb-probability-cutoff'
+ `lra-inheritance-ebb-probability-cutoff'
LRA tries to reuse values reloaded in registers in subsequent
insns. This optimization is called inheritance. EBB is used
as a region to do this optimization. The parameter defines a
minimal fall-through edge probability in percentage used to
- add BB to inheritance EBB in LRA. The default value of the
+ add BB to inheritance EBB in LRA. The default value of the
parameter is 40. The value was chosen from numerous runs of
SPEC2000 on x86-64.
- 'loop-invariant-max-bbs-in-loop'
+ `loop-invariant-max-bbs-in-loop'
Loop invariant motion can be very expensive, both in
compilation time and in amount of needed compile-time memory,
- with very large loops. Loops with more basic blocks than this
- parameter won't have loop invariant motion optimization
- performed on them. The default value of the parameter is 1000
- for '-O1' and 10000 for '-O2' and above.
+ with very large loops. Loops with more basic blocks than
+ this parameter won't have loop invariant motion optimization
+ performed on them. The default value of the parameter is
+ 1000 for `-O1' and 10000 for `-O2' and above.
- 'loop-max-datarefs-for-datadeps'
+ `loop-max-datarefs-for-datadeps'
Building data dapendencies is expensive for very large loops.
This parameter limits the number of data references in loops
- that are considered for data dependence analysis. These large
- loops are no handled by the optimizations using loop data
- dependencies. The default value is 1000.
+ that are considered for data dependence analysis. These
+ large loops are no handled by the optimizations using loop
+ data dependencies. The default value is 1000.
- 'max-vartrack-size'
+ `max-vartrack-size'
Sets a maximum number of hash table slots to use during
variable tracking dataflow analysis of any function. If this
limit is exceeded with variable tracking at assignments
enabled, analysis for that function is retried without it,
after removing all debug insns from the function. If the
limit is exceeded even without debug insns, var tracking
- analysis is completely disabled for the function. Setting the
- parameter to zero makes it unlimited.
+ analysis is completely disabled for the function. Setting
+ the parameter to zero makes it unlimited.
- 'max-vartrack-expr-depth'
+ `max-vartrack-expr-depth'
Sets a maximum number of recursion levels when attempting to
map variable names or debug temporaries to value expressions.
This trades compilation time for more complete debug
@@ -9849,232 +9909,236 @@ includes experimental options that may produce broken code.
compiler to find more complex debug expressions, but compile
time and memory use may grow. The default is 12.
- 'min-nondebug-insn-uid'
+ `min-nondebug-insn-uid'
Use uids starting at this parameter for nondebug insns. The
range below the parameter is reserved exclusively for debug
- insns created by '-fvar-tracking-assignments', but debug insns
- may get (non-overlapping) uids above it if the reserved range
- is exhausted.
+ insns created by `-fvar-tracking-assignments', but debug
+ insns may get (non-overlapping) uids above it if the reserved
+ range is exhausted.
- 'ipa-sra-ptr-growth-factor'
+ `ipa-sra-ptr-growth-factor'
IPA-SRA replaces a pointer to an aggregate with one or more
new parameters only when their cumulative size is less or
- equal to 'ipa-sra-ptr-growth-factor' times the size of the
+ equal to `ipa-sra-ptr-growth-factor' times the size of the
original pointer parameter.
- 'sra-max-scalarization-size-Ospeed'
- 'sra-max-scalarization-size-Osize'
+ `sra-max-scalarization-size-Ospeed'
+
+ `sra-max-scalarization-size-Osize'
The two Scalar Reduction of Aggregates passes (SRA and
IPA-SRA) aim to replace scalar parts of aggregates with uses
- of independent scalar variables. These parameters control the
- maximum size, in storage units, of aggregate which is
+ of independent scalar variables. These parameters control
+ the maximum size, in storage units, of aggregate which is
considered for replacement when compiling for speed
- ('sra-max-scalarization-size-Ospeed') or size
- ('sra-max-scalarization-size-Osize') respectively.
+ (`sra-max-scalarization-size-Ospeed') or size
+ (`sra-max-scalarization-size-Osize') respectively.
- 'tm-max-aggregate-size'
- When making copies of thread-local variables in a transaction,
- this parameter specifies the size in bytes after which
- variables are saved with the logging functions as opposed to
- save/restore code sequence pairs. This option only applies
- when using '-fgnu-tm'.
+ `tm-max-aggregate-size'
+ When making copies of thread-local variables in a
+ transaction, this parameter specifies the size in bytes after
+ which variables are saved with the logging functions as
+ opposed to save/restore code sequence pairs. This option
+ only applies when using `-fgnu-tm'.
- 'graphite-max-nb-scop-params'
+ `graphite-max-nb-scop-params'
To avoid exponential effects in the Graphite loop transforms,
the number of parameters in a Static Control Part (SCoP) is
bounded. The default value is 10 parameters. A variable
- whose value is unknown at compilation time and defined outside
- a SCoP is a parameter of the SCoP.
+ whose value is unknown at compilation time and defined
+ outside a SCoP is a parameter of the SCoP.
- 'graphite-max-bbs-per-function'
+ `graphite-max-bbs-per-function'
To avoid exponential effects in the detection of SCoPs, the
size of the functions analyzed by Graphite is bounded. The
default value is 100 basic blocks.
- 'loop-block-tile-size'
+ `loop-block-tile-size'
Loop blocking or strip mining transforms, enabled with
- '-floop-block' or '-floop-strip-mine', strip mine each loop in
- the loop nest by a given number of iterations. The strip
- length can be changed using the 'loop-block-tile-size'
+ `-floop-block' or `-floop-strip-mine', strip mine each loop
+ in the loop nest by a given number of iterations. The strip
+ length can be changed using the `loop-block-tile-size'
parameter. The default value is 51 iterations.
- 'loop-unroll-jam-size'
- Specify the unroll factor for the '-floop-unroll-and-jam'
+ `loop-unroll-jam-size'
+ Specify the unroll factor for the `-floop-unroll-and-jam'
option. The default value is 4.
- 'loop-unroll-jam-depth'
+ `loop-unroll-jam-depth'
Specify the dimension to be unrolled (counting from the most
- inner loop) for the '-floop-unroll-and-jam'. The default
+ inner loop) for the `-floop-unroll-and-jam'. The default
value is 2.
- 'ipa-cp-value-list-size'
+ `ipa-cp-value-list-size'
IPA-CP attempts to track all possible values and types passed
to a function's parameter in order to propagate them and
- perform devirtualization. 'ipa-cp-value-list-size' is the
+ perform devirtualization. `ipa-cp-value-list-size' is the
maximum number of values and types it stores per one formal
parameter of a function.
- 'ipa-cp-eval-threshold'
+ `ipa-cp-eval-threshold'
IPA-CP calculates its own score of cloning profitability
heuristics and performs those cloning opportunities with
- scores that exceed 'ipa-cp-eval-threshold'.
+ scores that exceed `ipa-cp-eval-threshold'.
- 'ipa-cp-recursion-penalty'
+ `ipa-cp-recursion-penalty'
Percentage penalty the recursive functions will receive when
they are evaluated for cloning.
- 'ipa-cp-single-call-penalty'
+ `ipa-cp-single-call-penalty'
Percentage penalty functions containg a single call to another
function will receive when they are evaluated for cloning.
- 'ipa-max-agg-items'
+ `ipa-max-agg-items'
IPA-CP is also capable to propagate a number of scalar values
- passed in an aggregate. 'ipa-max-agg-items' controls the
+ passed in an aggregate. `ipa-max-agg-items' controls the
maximum number of such values per one parameter.
- 'ipa-cp-loop-hint-bonus'
- When IPA-CP determines that a cloning candidate would make the
- number of iterations of a loop known, it adds a bonus of
- 'ipa-cp-loop-hint-bonus' to the profitability score of the
+ `ipa-cp-loop-hint-bonus'
+ When IPA-CP determines that a cloning candidate would make
+ the number of iterations of a loop known, it adds a bonus of
+ `ipa-cp-loop-hint-bonus' to the profitability score of the
candidate.
- 'ipa-cp-array-index-hint-bonus'
- When IPA-CP determines that a cloning candidate would make the
- index of an array access known, it adds a bonus of
- 'ipa-cp-array-index-hint-bonus' to the profitability score of
+ `ipa-cp-array-index-hint-bonus'
+ When IPA-CP determines that a cloning candidate would make
+ the index of an array access known, it adds a bonus of
+ `ipa-cp-array-index-hint-bonus' to the profitability score of
the candidate.
- 'ipa-max-aa-steps'
+ `ipa-max-aa-steps'
During its analysis of function bodies, IPA-CP employs alias
analysis in order to track values pointed to by function
parameters. In order not spend too much time analyzing huge
- functions, it gives up and consider all memory clobbered after
- examining 'ipa-max-aa-steps' statements modifying memory.
+ functions, it gives up and consider all memory clobbered
+ after examining `ipa-max-aa-steps' statements modifying
+ memory.
- 'lto-partitions'
+ `lto-partitions'
Specify desired number of partitions produced during WHOPR
compilation. The number of partitions should exceed the
number of CPUs used for compilation. The default value is 32.
- 'lto-minpartition'
+ `lto-minpartition'
Size of minimal partition for WHOPR (in estimated
- instructions). This prevents expenses of splitting very small
- programs into too many partitions.
+ instructions). This prevents expenses of splitting very
+ small programs into too many partitions.
- 'cxx-max-namespaces-for-diagnostic-help'
+ `cxx-max-namespaces-for-diagnostic-help'
The maximum number of namespaces to consult for suggestions
when C++ name lookup fails for an identifier. The default is
1000.
- 'sink-frequency-threshold'
+ `sink-frequency-threshold'
The maximum relative execution frequency (in percents) of the
- target block relative to a statement's original block to allow
- statement sinking of a statement. Larger numbers result in
- more aggressive statement sinking. The default value is 75.
- A small positive adjustment is applied for statements with
- memory operands as those are even more profitable so sink.
-
- 'max-stores-to-sink'
+ target block relative to a statement's original block to
+ allow statement sinking of a statement. Larger numbers
+ result in more aggressive statement sinking. The default
+ value is 75. A small positive adjustment is applied for
+ statements with memory operands as those are even more
+ profitable so sink.
+
+ `max-stores-to-sink'
The maximum number of conditional stores paires that can be
- sunk. Set to 0 if either vectorization ('-ftree-vectorize')
- or if-conversion ('-ftree-loop-if-convert') is disabled. The
+ sunk. Set to 0 if either vectorization (`-ftree-vectorize')
+ or if-conversion (`-ftree-loop-if-convert') is disabled. The
default is 2.
- 'allow-store-data-races'
+ `allow-store-data-races'
Allow optimizers to introduce new data races on stores. Set
to 1 to allow, otherwise to 0. This option is enabled by
- default at optimization level '-Ofast'.
+ default at optimization level `-Ofast'.
- 'case-values-threshold'
+ `case-values-threshold'
The smallest number of different values for which it is best
- to use a jump-table instead of a tree of conditional branches.
- If the value is 0, use the default for the machine. The
- default is 0.
+ to use a jump-table instead of a tree of conditional
+ branches. If the value is 0, use the default for the
+ machine. The default is 0.
- 'tree-reassoc-width'
+ `tree-reassoc-width'
Set the maximum number of instructions executed in parallel in
- reassociated tree. This parameter overrides target dependent
+ reassociated tree. This parameter overrides target dependent
heuristics used by default if has non zero value.
- 'sched-pressure-algorithm'
+ `sched-pressure-algorithm'
Choose between the two available implementations of
- '-fsched-pressure'. Algorithm 1 is the original
+ `-fsched-pressure'. Algorithm 1 is the original
implementation and is the more likely to prevent instructions
from being reordered. Algorithm 2 was designed to be a
compromise between the relatively conservative approach taken
- by algorithm 1 and the rather aggressive approach taken by the
- default scheduler. It relies more heavily on having a regular
- register file and accurate register pressure classes. See
- 'haifa-sched.c' in the GCC sources for more details.
+ by algorithm 1 and the rather aggressive approach taken by
+ the default scheduler. It relies more heavily on having a
+ regular register file and accurate register pressure classes.
+ See `haifa-sched.c' in the GCC sources for more details.
The default choice depends on the target.
- 'max-slsr-cand-scan'
+ `max-slsr-cand-scan'
Set the maximum number of existing candidates that are
considered when seeking a basis for a new straight-line
strength reduction candidate.
- 'asan-globals'
+ `asan-globals'
Enable buffer overflow detection for global objects. This
kind of protection is enabled by default if you are using
- '-fsanitize=address' option. To disable global objects
- protection use '--param asan-globals=0'.
+ `-fsanitize=address' option. To disable global objects
+ protection use `--param asan-globals=0'.
- 'asan-stack'
- Enable buffer overflow detection for stack objects. This kind
- of protection is enabled by default when
- using'-fsanitize=address'. To disable stack protection use
- '--param asan-stack=0' option.
+ `asan-stack'
+ Enable buffer overflow detection for stack objects. This
+ kind of protection is enabled by default when
+ using`-fsanitize=address'. To disable stack protection use
+ `--param asan-stack=0' option.
- 'asan-instrument-reads'
+ `asan-instrument-reads'
Enable buffer overflow detection for memory reads. This kind
of protection is enabled by default when using
- '-fsanitize=address'. To disable memory reads protection use
- '--param asan-instrument-reads=0'.
+ `-fsanitize=address'. To disable memory reads protection use
+ `--param asan-instrument-reads=0'.
- 'asan-instrument-writes'
- Enable buffer overflow detection for memory writes. This kind
- of protection is enabled by default when using
- '-fsanitize=address'. To disable memory writes protection use
- '--param asan-instrument-writes=0' option.
+ `asan-instrument-writes'
+ Enable buffer overflow detection for memory writes. This
+ kind of protection is enabled by default when using
+ `-fsanitize=address'. To disable memory writes protection use
+ `--param asan-instrument-writes=0' option.
- 'asan-memintrin'
+ `asan-memintrin'
Enable detection for built-in functions. This kind of
protection is enabled by default when using
- '-fsanitize=address'. To disable built-in functions
- protection use '--param asan-memintrin=0'.
+ `-fsanitize=address'. To disable built-in functions
+ protection use `--param asan-memintrin=0'.
- 'asan-use-after-return'
+ `asan-use-after-return'
Enable detection of use-after-return. This kind of protection
- is enabled by default when using '-fsanitize=address' option.
- To disable use-after-return detection use '--param
+ is enabled by default when using `-fsanitize=address' option.
+ To disable use-after-return detection use `--param
asan-use-after-return=0'.
- 'asan-instrumentation-with-call-threshold'
- If number of memory accesses in function being instrumented is
- greater or equal to this number, use callbacks instead of
- inline checks. E.g. to disable inline code use '--param
+ `asan-instrumentation-with-call-threshold'
+ If number of memory accesses in function being instrumented
+ is greater or equal to this number, use callbacks instead of
+ inline checks. E.g. to disable inline code use `--param
asan-instrumentation-with-call-threshold=0'.
- 'chkp-max-ctor-size'
+ `chkp-max-ctor-size'
Static constructors generated by Pointer Bounds Checker may
become very large and significantly increase compile time at
- optimization level '-O1' and higher. This parameter is a
+ optimization level `-O1' and higher. This parameter is a
maximum nubmer of statements in a single generated
constructor. Default value is 5000.
- 'max-fsm-thread-path-insns'
- Maximum number of instructions to copy when duplicating blocks
- on a finite state automaton jump thread path. The default is
- 100.
+ `max-fsm-thread-path-insns'
+ Maximum number of instructions to copy when duplicating
+ blocks on a finite state automaton jump thread path. The
+ default is 100.
- 'max-fsm-thread-length'
+ `max-fsm-thread-length'
Maximum number of basic blocks on a finite state automaton
jump thread path. The default is 10.
- 'max-fsm-thread-paths'
- Maximum number of new jump thread paths to create for a finite
- state automaton. The default is 50.
+ `max-fsm-thread-paths'
+ Maximum number of new jump thread paths to create for a
+ finite state automaton. The default is 50.
+

File: gcc.info, Node: Preprocessor Options, Next: Assembler Options, Prev: Optimize Options, Up: Invoking GCC
@@ -10085,50 +10149,50 @@ File: gcc.info, Node: Preprocessor Options, Next: Assembler Options, Prev: Op
These options control the C preprocessor, which is run on each C source
file before actual compilation.
- If you use the '-E' option, nothing is done except preprocessing. Some
-of these options make sense only together with '-E' because they cause
-the preprocessor output to be unsuitable for actual compilation.
+ If you use the `-E' option, nothing is done except preprocessing.
+Some of these options make sense only together with `-E' because they
+cause the preprocessor output to be unsuitable for actual compilation.
-'-Wp,OPTION'
- You can use '-Wp,OPTION' to bypass the compiler driver and pass
+`-Wp,OPTION'
+ You can use `-Wp,OPTION' to bypass the compiler driver and pass
OPTION directly through to the preprocessor. If OPTION contains
commas, it is split into multiple options at the commas. However,
many options are modified, translated or interpreted by the
- compiler driver before being passed to the preprocessor, and '-Wp'
+ compiler driver before being passed to the preprocessor, and `-Wp'
forcibly bypasses this phase. The preprocessor's direct interface
is undocumented and subject to change, so whenever possible you
- should avoid using '-Wp' and let the driver handle the options
+ should avoid using `-Wp' and let the driver handle the options
instead.
-'-Xpreprocessor OPTION'
+`-Xpreprocessor OPTION'
Pass OPTION as an option to the preprocessor. You can use this to
supply system-specific preprocessor options that GCC does not
recognize.
If you want to pass an option that takes an argument, you must use
- '-Xpreprocessor' twice, once for the option and once for the
+ `-Xpreprocessor' twice, once for the option and once for the
argument.
-'-no-integrated-cpp'
+`-no-integrated-cpp'
Perform preprocessing as a separate pass before compilation. By
default, GCC performs preprocessing as an integrated part of input
tokenization and parsing. If this option is provided, the
- appropriate language front end ('cc1', 'cc1plus', or 'cc1obj' for
+ appropriate language front end (`cc1', `cc1plus', or `cc1obj' for
C, C++, and Objective-C, respectively) is instead invoked twice,
once for preprocessing only and once for actual compilation of the
preprocessed input. This option may be useful in conjunction with
- the '-B' or '-wrapper' options to specify an alternate preprocessor
- or perform additional processing of the program source between
- normal preprocessing and compilation.
+ the `-B' or `-wrapper' options to specify an alternate
+ preprocessor or perform additional processing of the program
+ source between normal preprocessing and compilation.
-'-D NAME'
- Predefine NAME as a macro, with definition '1'.
+`-D NAME'
+ Predefine NAME as a macro, with definition `1'.
-'-D NAME=DEFINITION'
+`-D NAME=DEFINITION'
The contents of DEFINITION are tokenized and processed as if they
- appeared during translation phase three in a '#define' directive.
- In particular, the definition will be truncated by embedded newline
- characters.
+ appeared during translation phase three in a `#define' directive.
+ In particular, the definition will be truncated by embedded
+ newline characters.
If you are invoking the preprocessor from a shell or shell-like
program you may need to use the shell's quoting syntax to protect
@@ -10137,74 +10201,74 @@ the preprocessor output to be unsuitable for actual compilation.
If you wish to define a function-like macro on the command line,
write its argument list with surrounding parentheses before the
equals sign (if any). Parentheses are meaningful to most shells,
- so you will need to quote the option. With 'sh' and 'csh',
- '-D'NAME(ARGS...)=DEFINITION'' works.
+ so you will need to quote the option. With `sh' and `csh',
+ `-D'NAME(ARGS...)=DEFINITION'' works.
- '-D' and '-U' options are processed in the order they are given on
- the command line. All '-imacros FILE' and '-include FILE' options
- are processed after all '-D' and '-U' options.
+ `-D' and `-U' options are processed in the order they are given on
+ the command line. All `-imacros FILE' and `-include FILE' options
+ are processed after all `-D' and `-U' options.
-'-U NAME'
- Cancel any previous definition of NAME, either built in or provided
- with a '-D' option.
+`-U NAME'
+ Cancel any previous definition of NAME, either built in or
+ provided with a `-D' option.
-'-undef'
+`-undef'
Do not predefine any system-specific or GCC-specific macros. The
standard predefined macros remain defined.
-'-I DIR'
- Add the directory DIR to the list of directories to be searched for
- header files. Directories named by '-I' are searched before the
- standard system include directories. If the directory DIR is a
- standard system include directory, the option is ignored to ensure
- that the default search order for system directories and the
- special treatment of system headers are not defeated . If DIR
- begins with '=', then the '=' will be replaced by the sysroot
- prefix; see '--sysroot' and '-isysroot'.
-
-'-o FILE'
+`-I DIR'
+ Add the directory DIR to the list of directories to be searched
+ for header files. Directories named by `-I' are searched before
+ the standard system include directories. If the directory DIR is
+ a standard system include directory, the option is ignored to
+ ensure that the default search order for system directories and
+ the special treatment of system headers are not defeated . If DIR
+ begins with `=', then the `=' will be replaced by the sysroot
+ prefix; see `--sysroot' and `-isysroot'.
+
+`-o FILE'
Write output to FILE. This is the same as specifying FILE as the
- second non-option argument to 'cpp'. 'gcc' has a different
+ second non-option argument to `cpp'. `gcc' has a different
interpretation of a second non-option argument, so you must use
- '-o' to specify the output file.
+ `-o' to specify the output file.
-'-Wall'
+`-Wall'
Turns on all optional warnings which are desirable for normal code.
- At present this is '-Wcomment', '-Wtrigraphs', '-Wmultichar' and a
- warning about integer promotion causing a change of sign in '#if'
+ At present this is `-Wcomment', `-Wtrigraphs', `-Wmultichar' and a
+ warning about integer promotion causing a change of sign in `#if'
expressions. Note that many of the preprocessor's warnings are on
by default and have no options to control them.
-'-Wcomment'
-'-Wcomments'
- Warn whenever a comment-start sequence '/*' appears in a '/*'
- comment, or whenever a backslash-newline appears in a '//' comment.
+`-Wcomment'
+`-Wcomments'
+ Warn whenever a comment-start sequence `/*' appears in a `/*'
+ comment, or whenever a backslash-newline appears in a `//' comment.
(Both forms have the same effect.)
-'-Wtrigraphs'
+`-Wtrigraphs'
Most trigraphs in comments cannot affect the meaning of the
program. However, a trigraph that would form an escaped newline
- ('??/' at the end of a line) can, by changing where the comment
+ (`??/' at the end of a line) can, by changing where the comment
begins or ends. Therefore, only trigraphs that would form escaped
newlines produce warnings inside a comment.
- This option is implied by '-Wall'. If '-Wall' is not given, this
+ This option is implied by `-Wall'. If `-Wall' is not given, this
option is still enabled unless trigraphs are enabled. To get
- trigraph conversion without warnings, but get the other '-Wall'
- warnings, use '-trigraphs -Wall -Wno-trigraphs'.
+ trigraph conversion without warnings, but get the other `-Wall'
+ warnings, use `-trigraphs -Wall -Wno-trigraphs'.
-'-Wtraditional'
+`-Wtraditional'
Warn about certain constructs that behave differently in
traditional and ISO C. Also warn about ISO C constructs that have
no traditional C equivalent, and problematic constructs which
should be avoided.
-'-Wundef'
+`-Wundef'
Warn whenever an identifier which is not a macro is encountered in
- an '#if' directive, outside of 'defined'. Such identifiers are
+ an `#if' directive, outside of `defined'. Such identifiers are
replaced with zero.
-'-Wunused-macros'
+`-Wunused-macros'
Warn about macros defined in the main file that are unused. A
macro is "used" if it is expanded or tested for existence at least
once. The preprocessor will also warn if the macro has not been
@@ -10223,9 +10287,9 @@ the preprocessor output to be unsuitable for actual compilation.
#if defined the_macro_causing_the_warning
#endif
-'-Wendif-labels'
- Warn whenever an '#else' or an '#endif' are followed by text. This
- usually happens in code of the form
+`-Wendif-labels'
+ Warn whenever an `#else' or an `#endif' are followed by text.
+ This usually happens in code of the form
#if FOO
...
@@ -10233,92 +10297,92 @@ the preprocessor output to be unsuitable for actual compilation.
...
#endif FOO
- The second and third 'FOO' should be in comments, but often are not
+ The second and third `FOO' should be in comments, but often are not
in older programs. This warning is on by default.
-'-Werror'
+`-Werror'
Make all warnings into hard errors. Source code which triggers
warnings will be rejected.
-'-Wsystem-headers'
+`-Wsystem-headers'
Issue warnings for code in system headers. These are normally
unhelpful in finding bugs in your own code, therefore suppressed.
If you are responsible for the system library, you may want to see
them.
-'-w'
+`-w'
Suppress all warnings, including those which GNU CPP issues by
default.
-'-pedantic'
- Issue all the mandatory diagnostics listed in the C standard. Some
- of them are left out by default, since they trigger frequently on
- harmless code.
+`-pedantic'
+ Issue all the mandatory diagnostics listed in the C standard.
+ Some of them are left out by default, since they trigger
+ frequently on harmless code.
-'-pedantic-errors'
+`-pedantic-errors'
Issue all the mandatory diagnostics, and make all mandatory
diagnostics into errors. This includes mandatory diagnostics that
- GCC issues without '-pedantic' but treats as warnings.
+ GCC issues without `-pedantic' but treats as warnings.
-'-M'
+`-M'
Instead of outputting the result of preprocessing, output a rule
- suitable for 'make' describing the dependencies of the main source
- file. The preprocessor outputs one 'make' rule containing the
+ suitable for `make' describing the dependencies of the main source
+ file. The preprocessor outputs one `make' rule containing the
object file name for that source file, a colon, and the names of
- all the included files, including those coming from '-include' or
- '-imacros' command-line options.
+ all the included files, including those coming from `-include' or
+ `-imacros' command-line options.
- Unless specified explicitly (with '-MT' or '-MQ'), the object file
+ Unless specified explicitly (with `-MT' or `-MQ'), the object file
name consists of the name of the source file with any suffix
replaced with object file suffix and with any leading directory
parts removed. If there are many included files then the rule is
- split into several lines using '\'-newline. The rule has no
+ split into several lines using `\'-newline. The rule has no
commands.
- This option does not suppress the preprocessor's debug output, such
- as '-dM'. To avoid mixing such debug output with the dependency
- rules you should explicitly specify the dependency output file with
- '-MF', or use an environment variable like 'DEPENDENCIES_OUTPUT'
- (*note Environment Variables::). Debug output will still be sent
- to the regular output stream as normal.
+ This option does not suppress the preprocessor's debug output,
+ such as `-dM'. To avoid mixing such debug output with the
+ dependency rules you should explicitly specify the dependency
+ output file with `-MF', or use an environment variable like
+ `DEPENDENCIES_OUTPUT' (*note Environment Variables::). Debug
+ output will still be sent to the regular output stream as normal.
- Passing '-M' to the driver implies '-E', and suppresses warnings
- with an implicit '-w'.
+ Passing `-M' to the driver implies `-E', and suppresses warnings
+ with an implicit `-w'.
-'-MM'
- Like '-M' but do not mention header files that are found in system
- header directories, nor header files that are included, directly or
- indirectly, from such a header.
+`-MM'
+ Like `-M' but do not mention header files that are found in system
+ header directories, nor header files that are included, directly
+ or indirectly, from such a header.
This implies that the choice of angle brackets or double quotes in
- an '#include' directive does not in itself determine whether that
- header will appear in '-MM' dependency output. This is a slight
+ an `#include' directive does not in itself determine whether that
+ header will appear in `-MM' dependency output. This is a slight
change in semantics from GCC versions 3.0 and earlier.
-'-MF FILE'
- When used with '-M' or '-MM', specifies a file to write the
- dependencies to. If no '-MF' switch is given the preprocessor
+`-MF FILE'
+ When used with `-M' or `-MM', specifies a file to write the
+ dependencies to. If no `-MF' switch is given the preprocessor
sends the rules to the same place it would have sent preprocessed
output.
- When used with the driver options '-MD' or '-MMD', '-MF' overrides
+ When used with the driver options `-MD' or `-MMD', `-MF' overrides
the default dependency output file.
-'-MG'
- In conjunction with an option such as '-M' requesting dependency
- generation, '-MG' assumes missing header files are generated files
- and adds them to the dependency list without raising an error. The
- dependency filename is taken directly from the '#include' directive
- without prepending any path. '-MG' also suppresses preprocessed
- output, as a missing header file renders this useless.
+`-MG'
+ In conjunction with an option such as `-M' requesting dependency
+ generation, `-MG' assumes missing header files are generated files
+ and adds them to the dependency list without raising an error.
+ The dependency filename is taken directly from the `#include'
+ directive without prepending any path. `-MG' also suppresses
+ preprocessed output, as a missing header file renders this useless.
This feature is used in automatic updating of makefiles.
-'-MP'
+`-MP'
This option instructs CPP to add a phony target for each dependency
other than the main file, causing each to depend on nothing. These
- dummy rules work around errors 'make' gives if you remove header
- files without updating the 'Makefile' to match.
+ dummy rules work around errors `make' gives if you remove header
+ files without updating the `Makefile' to match.
This is typical output:
@@ -10326,52 +10390,50 @@ the preprocessor output to be unsuitable for actual compilation.
test.h:
-'-MT TARGET'
-
+`-MT TARGET'
Change the target of the rule emitted by dependency generation. By
default CPP takes the name of the main input file, deletes any
- directory components and any file suffix such as '.c', and appends
+ directory components and any file suffix such as `.c', and appends
the platform's usual object suffix. The result is the target.
- An '-MT' option will set the target to be exactly the string you
+ An `-MT' option will set the target to be exactly the string you
specify. If you want multiple targets, you can specify them as a
- single argument to '-MT', or use multiple '-MT' options.
+ single argument to `-MT', or use multiple `-MT' options.
- For example, '-MT '$(objpfx)foo.o'' might give
+ For example, `-MT '$(objpfx)foo.o'' might give
$(objpfx)foo.o: foo.c
-'-MQ TARGET'
-
- Same as '-MT', but it quotes any characters which are special to
- Make. '-MQ '$(objpfx)foo.o'' gives
+`-MQ TARGET'
+ Same as `-MT', but it quotes any characters which are special to
+ Make. `-MQ '$(objpfx)foo.o'' gives
$$(objpfx)foo.o: foo.c
The default target is automatically quoted, as if it were given
- with '-MQ'.
-
-'-MD'
- '-MD' is equivalent to '-M -MF FILE', except that '-E' is not
- implied. The driver determines FILE based on whether an '-o'
- option is given. If it is, the driver uses its argument but with a
- suffix of '.d', otherwise it takes the name of the input file,
- removes any directory components and suffix, and applies a '.d'
+ with `-MQ'.
+
+`-MD'
+ `-MD' is equivalent to `-M -MF FILE', except that `-E' is not
+ implied. The driver determines FILE based on whether an `-o'
+ option is given. If it is, the driver uses its argument but with
+ a suffix of `.d', otherwise it takes the name of the input file,
+ removes any directory components and suffix, and applies a `.d'
suffix.
- If '-MD' is used in conjunction with '-E', any '-o' switch is
+ If `-MD' is used in conjunction with `-E', any `-o' switch is
understood to specify the dependency output file (*note -MF:
- dashMF.), but if used without '-E', each '-o' is understood to
+ dashMF.), but if used without `-E', each `-o' is understood to
specify a target object file.
- Since '-E' is not implied, '-MD' can be used to generate a
+ Since `-E' is not implied, `-MD' can be used to generate a
dependency output file as a side-effect of the compilation process.
-'-MMD'
- Like '-MD' except mention only user header files, not system header
- files.
+`-MMD'
+ Like `-MD' except mention only user header files, not system
+ header files.
-'-fpch-deps'
+`-fpch-deps'
When using precompiled headers (*note Precompiled Headers::), this
flag will cause the dependency-output flags to also list the files
from the precompiled header's dependencies. If not specified only
@@ -10379,417 +10441,423 @@ the preprocessor output to be unsuitable for actual compilation.
used to create it because those files are not consulted when a
precompiled header is used.
-'-fpch-preprocess'
+`-fpch-preprocess'
This option allows use of a precompiled header (*note Precompiled
- Headers::) together with '-E'. It inserts a special '#pragma',
- '#pragma GCC pch_preprocess "FILENAME"' in the output to mark the
+ Headers::) together with `-E'. It inserts a special `#pragma',
+ `#pragma GCC pch_preprocess "FILENAME"' in the output to mark the
place where the precompiled header was found, and its FILENAME.
- When '-fpreprocessed' is in use, GCC recognizes this '#pragma' and
+ When `-fpreprocessed' is in use, GCC recognizes this `#pragma' and
loads the PCH.
This option is off by default, because the resulting preprocessed
output is only really suitable as input to GCC. It is switched on
- by '-save-temps'.
+ by `-save-temps'.
- You should not write this '#pragma' in your own code, but it is
+ You should not write this `#pragma' in your own code, but it is
safe to edit the filename if the PCH file is available in a
different location. The filename may be absolute or it may be
relative to GCC's current directory.
-'-x c'
-'-x c++'
-'-x objective-c'
-'-x assembler-with-cpp'
+`-x c'
+`-x c++'
+`-x objective-c'
+`-x assembler-with-cpp'
Specify the source language: C, C++, Objective-C, or assembly.
- This has nothing to do with standards conformance or extensions; it
- merely selects which base syntax to expect. If you give none of
- these options, cpp will deduce the language from the extension of
- the source file: '.c', '.cc', '.m', or '.S'. Some other common
+ This has nothing to do with standards conformance or extensions;
+ it merely selects which base syntax to expect. If you give none
+ of these options, cpp will deduce the language from the extension
+ of the source file: `.c', `.cc', `.m', or `.S'. Some other common
extensions for C++ and assembly are also recognized. If cpp does
not recognize the extension, it will treat the file as C; this is
the most generic mode.
- _Note:_ Previous versions of cpp accepted a '-lang' option which
+ _Note:_ Previous versions of cpp accepted a `-lang' option which
selected both the language and the standards conformance level.
- This option has been removed, because it conflicts with the '-l'
+ This option has been removed, because it conflicts with the `-l'
option.
-'-std=STANDARD'
-'-ansi'
+`-std=STANDARD'
+`-ansi'
Specify the standard to which the code should conform. Currently
CPP knows about C and C++ standards; others may be added in the
future.
STANDARD may be one of:
- 'c90'
- 'c89'
- 'iso9899:1990'
- The ISO C standard from 1990. 'c90' is the customary
+ `c90'
+ `c89'
+ `iso9899:1990'
+ The ISO C standard from 1990. `c90' is the customary
shorthand for this version of the standard.
- The '-ansi' option is equivalent to '-std=c90'.
+ The `-ansi' option is equivalent to `-std=c90'.
- 'iso9899:199409'
+ `iso9899:199409'
The 1990 C standard, as amended in 1994.
- 'iso9899:1999'
- 'c99'
- 'iso9899:199x'
- 'c9x'
+ `iso9899:1999'
+ `c99'
+ `iso9899:199x'
+ `c9x'
The revised ISO C standard, published in December 1999.
Before publication, this was known as C9X.
- 'iso9899:2011'
- 'c11'
- 'c1x'
+ `iso9899:2011'
+ `c11'
+ `c1x'
The revised ISO C standard, published in December 2011.
Before publication, this was known as C1X.
- 'gnu90'
- 'gnu89'
+ `gnu90'
+ `gnu89'
The 1990 C standard plus GNU extensions. This is the default.
- 'gnu99'
- 'gnu9x'
+ `gnu99'
+ `gnu9x'
The 1999 C standard plus GNU extensions.
- 'gnu11'
- 'gnu1x'
+ `gnu11'
+ `gnu1x'
The 2011 C standard plus GNU extensions.
- 'c++98'
+ `c++98'
The 1998 ISO C++ standard plus amendments.
- 'gnu++98'
- The same as '-std=c++98' plus GNU extensions. This is the
+ `gnu++98'
+ The same as `-std=c++98' plus GNU extensions. This is the
default for C++ code.
-'-I-'
- Split the include path. Any directories specified with '-I'
- options before '-I-' are searched only for headers requested with
- '#include "FILE"'; they are not searched for '#include <FILE>'. If
- additional directories are specified with '-I' options after the
- '-I-', those directories are searched for all '#include'
+`-I-'
+ Split the include path. Any directories specified with `-I'
+ options before `-I-' are searched only for headers requested with
+ `#include "FILE"'; they are not searched for `#include <FILE>'.
+ If additional directories are specified with `-I' options after
+ the `-I-', those directories are searched for all `#include'
directives.
- In addition, '-I-' inhibits the use of the directory of the current
- file directory as the first search directory for '#include "FILE"'.
+ In addition, `-I-' inhibits the use of the directory of the current
+ file directory as the first search directory for `#include "FILE"'.
This option has been deprecated.
-'-nostdinc'
+`-nostdinc'
Do not search the standard system directories for header files.
- Only the directories you have specified with '-I' options (and the
+ Only the directories you have specified with `-I' options (and the
directory of the current file, if appropriate) are searched.
-'-nostdinc++'
+`-nostdinc++'
Do not search for header files in the C++-specific standard
directories, but do still search the other standard directories.
(This option is used when building the C++ library.)
-'-include FILE'
- Process FILE as if '#include "file"' appeared as the first line of
- the primary source file. However, the first directory searched for
- FILE is the preprocessor's working directory _instead of_ the
+`-include FILE'
+ Process FILE as if `#include "file"' appeared as the first line of
+ the primary source file. However, the first directory searched
+ for FILE is the preprocessor's working directory _instead of_ the
directory containing the main source file. If not found there, it
- is searched for in the remainder of the '#include "..."' search
+ is searched for in the remainder of the `#include "..."' search
chain as normal.
- If multiple '-include' options are given, the files are included in
- the order they appear on the command line.
+ If multiple `-include' options are given, the files are included
+ in the order they appear on the command line.
-'-imacros FILE'
- Exactly like '-include', except that any output produced by
+`-imacros FILE'
+ Exactly like `-include', except that any output produced by
scanning FILE is thrown away. Macros it defines remain defined.
This allows you to acquire all the macros from a header without
also processing its declarations.
- All files specified by '-imacros' are processed before all files
- specified by '-include'.
+ All files specified by `-imacros' are processed before all files
+ specified by `-include'.
-'-idirafter DIR'
+`-idirafter DIR'
Search DIR for header files, but do it _after_ all directories
- specified with '-I' and the standard system directories have been
+ specified with `-I' and the standard system directories have been
exhausted. DIR is treated as a system include directory. If DIR
- begins with '=', then the '=' will be replaced by the sysroot
- prefix; see '--sysroot' and '-isysroot'.
+ begins with `=', then the `=' will be replaced by the sysroot
+ prefix; see `--sysroot' and `-isysroot'.
-'-iprefix PREFIX'
- Specify PREFIX as the prefix for subsequent '-iwithprefix' options.
- If the prefix represents a directory, you should include the final
- '/'.
+`-iprefix PREFIX'
+ Specify PREFIX as the prefix for subsequent `-iwithprefix'
+ options. If the prefix represents a directory, you should include
+ the final `/'.
-'-iwithprefix DIR'
-'-iwithprefixbefore DIR'
- Append DIR to the prefix specified previously with '-iprefix', and
+`-iwithprefix DIR'
+`-iwithprefixbefore DIR'
+ Append DIR to the prefix specified previously with `-iprefix', and
add the resulting directory to the include search path.
- '-iwithprefixbefore' puts it in the same place '-I' would;
- '-iwithprefix' puts it where '-idirafter' would.
+ `-iwithprefixbefore' puts it in the same place `-I' would;
+ `-iwithprefix' puts it where `-idirafter' would.
-'-isysroot DIR'
- This option is like the '--sysroot' option, but applies only to
+`-isysroot DIR'
+ This option is like the `--sysroot' option, but applies only to
header files (except for Darwin targets, where it applies to both
- header files and libraries). See the '--sysroot' option for more
+ header files and libraries). See the `--sysroot' option for more
information.
-'-imultilib DIR'
+`-imultilib DIR'
Use DIR as a subdirectory of the directory containing
target-specific C++ headers.
-'-isystem DIR'
+`-isystem DIR'
Search DIR for header files, after all directories specified by
- '-I' but before the standard system directories. Mark it as a
+ `-I' but before the standard system directories. Mark it as a
system directory, so that it gets the same special treatment as is
applied to the standard system directories. If DIR begins with
- '=', then the '=' will be replaced by the sysroot prefix; see
- '--sysroot' and '-isysroot'.
+ `=', then the `=' will be replaced by the sysroot prefix; see
+ `--sysroot' and `-isysroot'.
-'-iquote DIR'
- Search DIR only for header files requested with '#include "FILE"';
- they are not searched for '#include <FILE>', before all directories
- specified by '-I' and before the standard system directories. If
- DIR begins with '=', then the '=' will be replaced by the sysroot
- prefix; see '--sysroot' and '-isysroot'.
+`-iquote DIR'
+ Search DIR only for header files requested with `#include "FILE"';
+ they are not searched for `#include <FILE>', before all
+ directories specified by `-I' and before the standard system
+ directories. If DIR begins with `=', then the `=' will be replaced
+ by the sysroot prefix; see `--sysroot' and `-isysroot'.
-'-fdirectives-only'
+`-fdirectives-only'
When preprocessing, handle directives, but do not expand macros.
- The option's behavior depends on the '-E' and '-fpreprocessed'
+ The option's behavior depends on the `-E' and `-fpreprocessed'
options.
- With '-E', preprocessing is limited to the handling of directives
- such as '#define', '#ifdef', and '#error'. Other preprocessor
- operations, such as macro expansion and trigraph conversion are not
- performed. In addition, the '-dD' option is implicitly enabled.
+ With `-E', preprocessing is limited to the handling of directives
+ such as `#define', `#ifdef', and `#error'. Other preprocessor
+ operations, such as macro expansion and trigraph conversion are
+ not performed. In addition, the `-dD' option is implicitly
+ enabled.
- With '-fpreprocessed', predefinition of command line and most
- builtin macros is disabled. Macros such as '__LINE__', which are
+ With `-fpreprocessed', predefinition of command line and most
+ builtin macros is disabled. Macros such as `__LINE__', which are
contextually dependent, are handled normally. This enables
- compilation of files previously preprocessed with '-E
+ compilation of files previously preprocessed with `-E
-fdirectives-only'.
- With both '-E' and '-fpreprocessed', the rules for '-fpreprocessed'
- take precedence. This enables full preprocessing of files
- previously preprocessed with '-E -fdirectives-only'.
+ With both `-E' and `-fpreprocessed', the rules for
+ `-fpreprocessed' take precedence. This enables full preprocessing
+ of files previously preprocessed with `-E -fdirectives-only'.
-'-fdollars-in-identifiers'
- Accept '$' in identifiers.
+`-fdollars-in-identifiers'
+ Accept `$' in identifiers.
-'-fextended-identifiers'
+`-fextended-identifiers'
Accept universal character names in identifiers. This option is
enabled by default for C99 (and later C standard versions) and C++.
-'-fno-canonical-system-headers'
+`-fno-canonical-system-headers'
When preprocessing, do not shorten system header paths with
canonicalization.
-'-fpreprocessed'
+`-fpreprocessed'
Indicate to the preprocessor that the input file has already been
preprocessed. This suppresses things like macro expansion,
trigraph conversion, escaped newline splicing, and processing of
most directives. The preprocessor still recognizes and removes
- comments, so that you can pass a file preprocessed with '-C' to the
- compiler without problems. In this mode the integrated
+ comments, so that you can pass a file preprocessed with `-C' to
+ the compiler without problems. In this mode the integrated
preprocessor is little more than a tokenizer for the front ends.
- '-fpreprocessed' is implicit if the input file has one of the
- extensions '.i', '.ii' or '.mi'. These are the extensions that GCC
- uses for preprocessed files created by '-save-temps'.
+ `-fpreprocessed' is implicit if the input file has one of the
+ extensions `.i', `.ii' or `.mi'. These are the extensions that
+ GCC uses for preprocessed files created by `-save-temps'.
-'-ftabstop=WIDTH'
+`-ftabstop=WIDTH'
Set the distance between tab stops. This helps the preprocessor
report correct column numbers in warnings or errors, even if tabs
appear on the line. If the value is less than 1 or greater than
100, the option is ignored. The default is 8.
-'-fdebug-cpp'
- This option is only useful for debugging GCC. When used with '-E',
- dumps debugging information about location maps. Every token in
- the output is preceded by the dump of the map its location belongs
- to. The dump of the map holding the location of a token would be:
- {'P':/file/path;'F':/includer/path;'L':LINE_NUM;'C':COL_NUM;'S':SYSTEM_HEADER_P;'M':MAP_ADDRESS;'E':MACRO_EXPANSION_P,'loc':LOCATION}
+`-fdebug-cpp'
+ This option is only useful for debugging GCC. When used with
+ `-E', dumps debugging information about location maps. Every
+ token in the output is preceded by the dump of the map its location
+ belongs to. The dump of the map holding the location of a token
+ would be:
+ {`P':`/file/path';`F':`/includer/path';`L':LINE_NUM;`C':COL_NUM;`S':SYSTEM_HEADER_P;`M':MAP_ADDRESS;`E':MACRO_EXPANSION_P,`loc':LOCATION}
- When used without '-E', this option has no effect.
+ When used without `-E', this option has no effect.
-'-ftrack-macro-expansion[=LEVEL]'
- Track locations of tokens across macro expansions. This allows the
+`-ftrack-macro-expansion[=LEVEL]'
+ Track locations of tokens across macro expansions. This allows the
compiler to emit diagnostic about the current macro expansion stack
- when a compilation error occurs in a macro expansion. Using this
- option makes the preprocessor and the compiler consume more memory.
- The LEVEL parameter can be used to choose the level of precision of
- token location tracking thus decreasing the memory consumption if
- necessary. Value '0' of LEVEL de-activates this option just as if
- no '-ftrack-macro-expansion' was present on the command line.
- Value '1' tracks tokens locations in a degraded mode for the sake
- of minimal memory overhead. In this mode all tokens resulting from
- the expansion of an argument of a function-like macro have the same
- location. Value '2' tracks tokens locations completely. This
- value is the most memory hungry. When this option is given no
- argument, the default parameter value is '2'.
-
- Note that '-ftrack-macro-expansion=2' is activated by default.
-
-'-fexec-charset=CHARSET'
+ when a compilation error occurs in a macro expansion. Using this
+ option makes the preprocessor and the compiler consume more
+ memory. The LEVEL parameter can be used to choose the level of
+ precision of token location tracking thus decreasing the memory
+ consumption if necessary. Value `0' of LEVEL de-activates this
+ option just as if no `-ftrack-macro-expansion' was present on the
+ command line. Value `1' tracks tokens locations in a degraded mode
+ for the sake of minimal memory overhead. In this mode all tokens
+ resulting from the expansion of an argument of a function-like
+ macro have the same location. Value `2' tracks tokens locations
+ completely. This value is the most memory hungry. When this
+ option is given no argument, the default parameter value is `2'.
+
+ Note that `-ftrack-macro-expansion=2' is activated by default.
+
+`-fexec-charset=CHARSET'
Set the execution character set, used for string and character
constants. The default is UTF-8. CHARSET can be any encoding
- supported by the system's 'iconv' library routine.
+ supported by the system's `iconv' library routine.
-'-fwide-exec-charset=CHARSET'
+`-fwide-exec-charset=CHARSET'
Set the wide execution character set, used for wide string and
character constants. The default is UTF-32 or UTF-16, whichever
- corresponds to the width of 'wchar_t'. As with '-fexec-charset',
- CHARSET can be any encoding supported by the system's 'iconv'
+ corresponds to the width of `wchar_t'. As with `-fexec-charset',
+ CHARSET can be any encoding supported by the system's `iconv'
library routine; however, you will have problems with encodings
- that do not fit exactly in 'wchar_t'.
+ that do not fit exactly in `wchar_t'.
-'-finput-charset=CHARSET'
+`-finput-charset=CHARSET'
Set the input character set, used for translation from the
- character set of the input file to the source character set used by
- GCC. If the locale does not specify, or GCC cannot get this
+ character set of the input file to the source character set used
+ by GCC. If the locale does not specify, or GCC cannot get this
information from the locale, the default is UTF-8. This can be
overridden by either the locale or this command-line option.
Currently the command-line option takes precedence if there's a
conflict. CHARSET can be any encoding supported by the system's
- 'iconv' library routine.
+ `iconv' library routine.
-'-fworking-directory'
+`-fworking-directory'
Enable generation of linemarkers in the preprocessor output that
will let the compiler know the current working directory at the
time of preprocessing. When this option is enabled, the
preprocessor will emit, after the initial linemarker, a second
linemarker with the current working directory followed by two
slashes. GCC will use this directory, when it's present in the
- preprocessed input, as the directory emitted as the current working
- directory in some debugging information formats. This option is
- implicitly enabled if debugging information is enabled, but this
- can be inhibited with the negated form '-fno-working-directory'.
- If the '-P' flag is present in the command line, this option has no
- effect, since no '#line' directives are emitted whatsoever.
-
-'-fno-show-column'
+ preprocessed input, as the directory emitted as the current
+ working directory in some debugging information formats. This
+ option is implicitly enabled if debugging information is enabled,
+ but this can be inhibited with the negated form
+ `-fno-working-directory'. If the `-P' flag is present in the
+ command line, this option has no effect, since no `#line'
+ directives are emitted whatsoever.
+
+`-fno-show-column'
Do not print column numbers in diagnostics. This may be necessary
if diagnostics are being scanned by a program that does not
- understand the column numbers, such as 'dejagnu'.
+ understand the column numbers, such as `dejagnu'.
-'-A PREDICATE=ANSWER'
+`-A PREDICATE=ANSWER'
Make an assertion with the predicate PREDICATE and answer ANSWER.
- This form is preferred to the older form '-A PREDICATE(ANSWER)',
+ This form is preferred to the older form `-A PREDICATE(ANSWER)',
which is still supported, because it does not use shell special
characters.
-'-A -PREDICATE=ANSWER'
+`-A -PREDICATE=ANSWER'
Cancel an assertion with the predicate PREDICATE and answer ANSWER.
-'-dCHARS'
- CHARS is a sequence of one or more of the following characters, and
- must not be preceded by a space. Other characters are interpreted
- by the compiler proper, or reserved for future versions of GCC, and
- so are silently ignored. If you specify characters whose behavior
- conflicts, the result is undefined.
+`-dCHARS'
+ CHARS is a sequence of one or more of the following characters,
+ and must not be preceded by a space. Other characters are
+ interpreted by the compiler proper, or reserved for future
+ versions of GCC, and so are silently ignored. If you specify
+ characters whose behavior conflicts, the result is undefined.
- 'M'
- Instead of the normal output, generate a list of '#define'
+ `M'
+ Instead of the normal output, generate a list of `#define'
directives for all the macros defined during the execution of
- the preprocessor, including predefined macros. This gives you
- a way of finding out what is predefined in your version of the
- preprocessor. Assuming you have no file 'foo.h', the command
+ the preprocessor, including predefined macros. This gives
+ you a way of finding out what is predefined in your version
+ of the preprocessor. Assuming you have no file `foo.h', the
+ command
touch foo.h; cpp -dM foo.h
will show all the predefined macros.
- If you use '-dM' without the '-E' option, '-dM' is interpreted
- as a synonym for '-fdump-rtl-mach'. *Note (gcc)Debugging
- Options::.
+ If you use `-dM' without the `-E' option, `-dM' is
+ interpreted as a synonym for `-fdump-rtl-mach'. *Note
+ Debugging Options: (gcc)Debugging Options.
- 'D'
- Like 'M' except in two respects: it does _not_ include the
- predefined macros, and it outputs _both_ the '#define'
+ `D'
+ Like `M' except in two respects: it does _not_ include the
+ predefined macros, and it outputs _both_ the `#define'
directives and the result of preprocessing. Both kinds of
output go to the standard output file.
- 'N'
- Like 'D', but emit only the macro names, not their expansions.
+ `N'
+ Like `D', but emit only the macro names, not their expansions.
- 'I'
- Output '#include' directives in addition to the result of
+ `I'
+ Output `#include' directives in addition to the result of
preprocessing.
- 'U'
- Like 'D' except that only macros that are expanded, or whose
+ `U'
+ Like `D' except that only macros that are expanded, or whose
definedness is tested in preprocessor directives, are output;
the output is delayed until the use or test of the macro; and
- '#undef' directives are also output for macros tested but
+ `#undef' directives are also output for macros tested but
undefined at the time.
-'-P'
+`-P'
Inhibit generation of linemarkers in the output from the
preprocessor. This might be useful when running the preprocessor
on something that is not C code, and will be sent to a program
which might be confused by the linemarkers.
-'-C'
+`-C'
Do not discard comments. All comments are passed through to the
- output file, except for comments in processed directives, which are
- deleted along with the directive.
+ output file, except for comments in processed directives, which
+ are deleted along with the directive.
- You should be prepared for side effects when using '-C'; it causes
+ You should be prepared for side effects when using `-C'; it causes
the preprocessor to treat comments as tokens in their own right.
For example, comments appearing at the start of what would be a
directive line have the effect of turning that line into an
ordinary source line, since the first token on the line is no
- longer a '#'.
+ longer a `#'.
-'-CC'
+`-CC'
Do not discard comments, including during macro expansion. This is
- like '-C', except that comments contained within macros are also
+ like `-C', except that comments contained within macros are also
passed through to the output file where the macro is expanded.
- In addition to the side-effects of the '-C' option, the '-CC'
- option causes all C++-style comments inside a macro to be converted
- to C-style comments. This is to prevent later use of that macro
- from inadvertently commenting out the remainder of the source line.
+ In addition to the side-effects of the `-C' option, the `-CC'
+ option causes all C++-style comments inside a macro to be
+ converted to C-style comments. This is to prevent later use of
+ that macro from inadvertently commenting out the remainder of the
+ source line.
- The '-CC' option is generally used to support lint comments.
+ The `-CC' option is generally used to support lint comments.
-'-traditional-cpp'
+`-traditional-cpp'
Try to imitate the behavior of old-fashioned C preprocessors, as
opposed to ISO C preprocessors.
-'-trigraphs'
+`-trigraphs'
Process trigraph sequences. These are three-character sequences,
- all starting with '??', that are defined by ISO C to stand for
- single characters. For example, '??/' stands for '\', so ''??/n''
+ all starting with `??', that are defined by ISO C to stand for
+ single characters. For example, `??/' stands for `\', so `'??/n''
is a character constant for a newline. By default, GCC ignores
trigraphs, but in standard-conforming modes it converts them. See
- the '-std' and '-ansi' options.
+ the `-std' and `-ansi' options.
The nine trigraphs and their replacements are
Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??-
Replacement: [ ] { } # \ ^ | ~
-'-remap'
+`-remap'
Enable special code to work around file systems which only permit
very short file names, such as MS-DOS.
-'--help'
-'--target-help'
+`--help'
+`--target-help'
Print text describing all the command-line options instead of
preprocessing anything.
-'-v'
+`-v'
Verbose mode. Print out GNU CPP's version number at the beginning
of execution, and report the final form of the include path.
-'-H'
+`-H'
Print the name of each header file used, in addition to other
normal activities. Each name is indented to show how deep in the
- '#include' stack it is. Precompiled header files are also printed,
- even if they are found to be invalid; an invalid precompiled header
- file is printed with '...x' and a valid one with '...!' .
+ `#include' stack it is. Precompiled header files are also
+ printed, even if they are found to be invalid; an invalid
+ precompiled header file is printed with `...x' and a valid one
+ with `...!' .
-'-version'
-'--version'
+`-version'
+`--version'
Print out GNU CPP's version number. With one dash, proceed to
preprocess as normal. With two dashes, exit immediately.
@@ -10801,17 +10869,18 @@ File: gcc.info, Node: Assembler Options, Next: Link Options, Prev: Preprocess
You can pass options to the assembler.
-'-Wa,OPTION'
+`-Wa,OPTION'
Pass OPTION as an option to the assembler. If OPTION contains
commas, it is split into multiple options at the commas.
-'-Xassembler OPTION'
+`-Xassembler OPTION'
Pass OPTION as an option to the assembler. You can use this to
supply system-specific assembler options that GCC does not
recognize.
If you want to pass an option that takes an argument, you must use
- '-Xassembler' twice, once for the option and once for the argument.
+ `-Xassembler' twice, once for the option and once for the argument.
+

File: gcc.info, Node: Link Options, Next: Directory Options, Prev: Assembler Options, Up: Invoking GCC
@@ -10823,279 +10892,283 @@ These options come into play when the compiler links object files into
an executable output file. They are meaningless if the compiler is not
doing a link step.
-'OBJECT-FILE-NAME'
+`OBJECT-FILE-NAME'
A file name that does not end in a special recognized suffix is
considered to name an object file or library. (Object files are
distinguished from libraries by the linker according to the file
contents.) If linking is done, these object files are used as
input to the linker.
-'-c'
-'-S'
-'-E'
+`-c'
+`-S'
+`-E'
If any of these options is used, then the linker is not run, and
object file names should not be used as arguments. *Note Overall
Options::.
-'-fuse-ld=bfd'
- Use the 'bfd' linker instead of the default linker.
+`-fuse-ld=bfd'
+ Use the `bfd' linker instead of the default linker.
-'-fuse-ld=gold'
- Use the 'gold' linker instead of the default linker.
+`-fuse-ld=gold'
+ Use the `gold' linker instead of the default linker.
-'-lLIBRARY'
-'-l LIBRARY'
+`-lLIBRARY'
+`-l LIBRARY'
Search the library named LIBRARY when linking. (The second
alternative with the library as a separate argument is only for
POSIX compliance and is not recommended.)
It makes a difference where in the command you write this option;
- the linker searches and processes libraries and object files in the
- order they are specified. Thus, 'foo.o -lz bar.o' searches library
- 'z' after file 'foo.o' but before 'bar.o'. If 'bar.o' refers to
- functions in 'z', those functions may not be loaded.
+ the linker searches and processes libraries and object files in
+ the order they are specified. Thus, `foo.o -lz bar.o' searches
+ library `z' after file `foo.o' but before `bar.o'. If `bar.o'
+ refers to functions in `z', those functions may not be loaded.
The linker searches a standard list of directories for the library,
- which is actually a file named 'libLIBRARY.a'. The linker then
+ which is actually a file named `libLIBRARY.a'. The linker then
uses this file as if it had been specified precisely by name.
The directories searched include several standard system
- directories plus any that you specify with '-L'.
+ directories plus any that you specify with `-L'.
Normally the files found this way are library files--archive files
- whose members are object files. The linker handles an archive file
- by scanning through it for members which define symbols that have
- so far been referenced but not defined. But if the file that is
- found is an ordinary object file, it is linked in the usual
- fashion. The only difference between using an '-l' option and
- specifying a file name is that '-l' surrounds LIBRARY with 'lib'
- and '.a' and searches several directories.
-
-'-lobjc'
- You need this special case of the '-l' option in order to link an
+ whose members are object files. The linker handles an archive
+ file by scanning through it for members which define symbols that
+ have so far been referenced but not defined. But if the file that
+ is found is an ordinary object file, it is linked in the usual
+ fashion. The only difference between using an `-l' option and
+ specifying a file name is that `-l' surrounds LIBRARY with `lib'
+ and `.a' and searches several directories.
+
+`-lobjc'
+ You need this special case of the `-l' option in order to link an
Objective-C or Objective-C++ program.
-'-nostartfiles'
+`-nostartfiles'
Do not use the standard system startup files when linking. The
- standard system libraries are used normally, unless '-nostdlib' or
- '-nodefaultlibs' is used.
+ standard system libraries are used normally, unless `-nostdlib' or
+ `-nodefaultlibs' is used.
-'-nodefaultlibs'
+`-nodefaultlibs'
Do not use the standard system libraries when linking. Only the
libraries you specify are passed to the linker, and options
specifying linkage of the system libraries, such as
- '-static-libgcc' or '-shared-libgcc', are ignored. The standard
- startup files are used normally, unless '-nostartfiles' is used.
+ `-static-libgcc' or `-shared-libgcc', are ignored. The standard
+ startup files are used normally, unless `-nostartfiles' is used.
- The compiler may generate calls to 'memcmp', 'memset', 'memcpy' and
- 'memmove'. These entries are usually resolved by entries in libc.
- These entry points should be supplied through some other mechanism
- when this option is specified.
+ The compiler may generate calls to `memcmp', `memset', `memcpy'
+ and `memmove'. These entries are usually resolved by entries in
+ libc. These entry points should be supplied through some other
+ mechanism when this option is specified.
-'-nostdlib'
+`-nostdlib'
Do not use the standard system startup files or libraries when
linking. No startup files and only the libraries you specify are
passed to the linker, and options specifying linkage of the system
- libraries, such as '-static-libgcc' or '-shared-libgcc', are
+ libraries, such as `-static-libgcc' or `-shared-libgcc', are
ignored.
- The compiler may generate calls to 'memcmp', 'memset', 'memcpy' and
- 'memmove'. These entries are usually resolved by entries in libc.
- These entry points should be supplied through some other mechanism
- when this option is specified.
+ The compiler may generate calls to `memcmp', `memset', `memcpy'
+ and `memmove'. These entries are usually resolved by entries in
+ libc. These entry points should be supplied through some other
+ mechanism when this option is specified.
- One of the standard libraries bypassed by '-nostdlib' and
- '-nodefaultlibs' is 'libgcc.a', a library of internal subroutines
+ One of the standard libraries bypassed by `-nostdlib' and
+ `-nodefaultlibs' is `libgcc.a', a library of internal subroutines
which GCC uses to overcome shortcomings of particular machines, or
special needs for some languages. (*Note Interfacing to GCC
- Output: (gccint)Interface, for more discussion of 'libgcc.a'.) In
- most cases, you need 'libgcc.a' even when you want to avoid other
- standard libraries. In other words, when you specify '-nostdlib'
- or '-nodefaultlibs' you should usually specify '-lgcc' as well.
+ Output: (gccint)Interface, for more discussion of `libgcc.a'.) In
+ most cases, you need `libgcc.a' even when you want to avoid other
+ standard libraries. In other words, when you specify `-nostdlib'
+ or `-nodefaultlibs' you should usually specify `-lgcc' as well.
This ensures that you have no unresolved references to internal GCC
- library subroutines. (An example of such an internal subroutine is
- '__main', used to ensure C++ constructors are called; *note
- 'collect2': (gccint)Collect2.)
+ library subroutines. (An example of such an internal subroutine
+ is `__main', used to ensure C++ constructors are called; *note
+ `collect2': (gccint)Collect2.)
-'-pie'
+`-pie'
Produce a position independent executable on targets that support
- it. For predictable results, you must also specify the same set of
- options used for compilation ('-fpie', '-fPIE', or model
+ it. For predictable results, you must also specify the same set
+ of options used for compilation (`-fpie', `-fPIE', or model
suboptions) when you specify this linker option.
-'-rdynamic'
- Pass the flag '-export-dynamic' to the ELF linker, on targets that
- support it. This instructs the linker to add all symbols, not only
- used ones, to the dynamic symbol table. This option is needed for
- some uses of 'dlopen' or to allow obtaining backtraces from within
+`-rdynamic'
+ Pass the flag `-export-dynamic' to the ELF linker, on targets that
+ support it. This instructs the linker to add all symbols, not only
+ used ones, to the dynamic symbol table. This option is needed for
+ some uses of `dlopen' or to allow obtaining backtraces from within
a program.
-'-s'
+`-s'
Remove all symbol table and relocation information from the
executable.
-'-static'
- On systems that support dynamic linking, this prevents linking with
- the shared libraries. On other systems, this option has no effect.
+`-static'
+ On systems that support dynamic linking, this prevents linking
+ with the shared libraries. On other systems, this option has no
+ effect.
-'-shared'
- Produce a shared object which can then be linked with other objects
- to form an executable. Not all systems support this option. For
- predictable results, you must also specify the same set of options
- used for compilation ('-fpic', '-fPIC', or model suboptions) when
- you specify this linker option.(1)
+`-shared'
+ Produce a shared object which can then be linked with other
+ objects to form an executable. Not all systems support this
+ option. For predictable results, you must also specify the same
+ set of options used for compilation (`-fpic', `-fPIC', or model
+ suboptions) when you specify this linker option.(1)
-'-shared-libgcc'
-'-static-libgcc'
- On systems that provide 'libgcc' as a shared library, these options
+`-shared-libgcc'
+`-static-libgcc'
+ On systems that provide `libgcc' as a shared library, these options
force the use of either the shared or static version, respectively.
- If no shared version of 'libgcc' was built when the compiler was
+ If no shared version of `libgcc' was built when the compiler was
configured, these options have no effect.
There are several situations in which an application should use the
- shared 'libgcc' instead of the static version. The most common of
+ shared `libgcc' instead of the static version. The most common of
these is when the application wishes to throw and catch exceptions
across different shared libraries. In that case, each of the
libraries as well as the application itself should use the shared
- 'libgcc'.
+ `libgcc'.
Therefore, the G++ and GCJ drivers automatically add
- '-shared-libgcc' whenever you build a shared library or a main
- executable, because C++ and Java programs typically use exceptions,
- so this is the right thing to do.
-
- If, instead, you use the GCC driver to create shared libraries, you
- may find that they are not always linked with the shared 'libgcc'.
- If GCC finds, at its configuration time, that you have a non-GNU
- linker or a GNU linker that does not support option
- '--eh-frame-hdr', it links the shared version of 'libgcc' into
+ `-shared-libgcc' whenever you build a shared library or a main
+ executable, because C++ and Java programs typically use
+ exceptions, so this is the right thing to do.
+
+ If, instead, you use the GCC driver to create shared libraries,
+ you may find that they are not always linked with the shared
+ `libgcc'. If GCC finds, at its configuration time, that you have
+ a non-GNU linker or a GNU linker that does not support option
+ `--eh-frame-hdr', it links the shared version of `libgcc' into
shared libraries by default. Otherwise, it takes advantage of the
linker and optimizes away the linking with the shared version of
- 'libgcc', linking with the static version of libgcc by default.
+ `libgcc', linking with the static version of libgcc by default.
This allows exceptions to propagate through such shared libraries,
without incurring relocation costs at library load time.
However, if a library or main executable is supposed to throw or
catch exceptions, you must link it using the G++ or GCJ driver, as
appropriate for the languages used in the program, or using the
- option '-shared-libgcc', such that it is linked with the shared
- 'libgcc'.
-
-'-static-libasan'
- When the '-fsanitize=address' option is used to link a program, the
- GCC driver automatically links against 'libasan'. If 'libasan' is
- available as a shared library, and the '-static' option is not
- used, then this links against the shared version of 'libasan'. The
- '-static-libasan' option directs the GCC driver to link 'libasan'
- statically, without necessarily linking other libraries statically.
-
-'-static-libtsan'
- When the '-fsanitize=thread' option is used to link a program, the
- GCC driver automatically links against 'libtsan'. If 'libtsan' is
- available as a shared library, and the '-static' option is not
- used, then this links against the shared version of 'libtsan'. The
- '-static-libtsan' option directs the GCC driver to link 'libtsan'
- statically, without necessarily linking other libraries statically.
-
-'-static-liblsan'
- When the '-fsanitize=leak' option is used to link a program, the
- GCC driver automatically links against 'liblsan'. If 'liblsan' is
- available as a shared library, and the '-static' option is not
- used, then this links against the shared version of 'liblsan'. The
- '-static-liblsan' option directs the GCC driver to link 'liblsan'
- statically, without necessarily linking other libraries statically.
-
-'-static-libubsan'
- When the '-fsanitize=undefined' option is used to link a program,
- the GCC driver automatically links against 'libubsan'. If
- 'libubsan' is available as a shared library, and the '-static'
+ option `-shared-libgcc', such that it is linked with the shared
+ `libgcc'.
+
+`-static-libasan'
+ When the `-fsanitize=address' option is used to link a program,
+ the GCC driver automatically links against `libasan'. If
+ `libasan' is available as a shared library, and the `-static'
+ option is not used, then this links against the shared version of
+ `libasan'. The `-static-libasan' option directs the GCC driver to
+ link `libasan' statically, without necessarily linking other
+ libraries statically.
+
+`-static-libtsan'
+ When the `-fsanitize=thread' option is used to link a program, the
+ GCC driver automatically links against `libtsan'. If `libtsan' is
+ available as a shared library, and the `-static' option is not
+ used, then this links against the shared version of `libtsan'.
+ The `-static-libtsan' option directs the GCC driver to link
+ `libtsan' statically, without necessarily linking other libraries
+ statically.
+
+`-static-liblsan'
+ When the `-fsanitize=leak' option is used to link a program, the
+ GCC driver automatically links against `liblsan'. If `liblsan' is
+ available as a shared library, and the `-static' option is not
+ used, then this links against the shared version of `liblsan'.
+ The `-static-liblsan' option directs the GCC driver to link
+ `liblsan' statically, without necessarily linking other libraries
+ statically.
+
+`-static-libubsan'
+ When the `-fsanitize=undefined' option is used to link a program,
+ the GCC driver automatically links against `libubsan'. If
+ `libubsan' is available as a shared library, and the `-static'
option is not used, then this links against the shared version of
- 'libubsan'. The '-static-libubsan' option directs the GCC driver
- to link 'libubsan' statically, without necessarily linking other
+ `libubsan'. The `-static-libubsan' option directs the GCC driver
+ to link `libubsan' statically, without necessarily linking other
libraries statically.
-'-static-libmpx'
- When the '-fcheck-pointer bounds' and '-mmpx' options are used to
+`-static-libmpx'
+ When the `-fcheck-pointer bounds' and `-mmpx' options are used to
link a program, the GCC driver automatically links against
- 'libmpx'. If 'libmpx' is available as a shared library, and the
- '-static' option is not used, then this links against the shared
- version of 'libmpx'. The '-static-libmpx' option directs the GCC
- driver to link 'libmpx' statically, without necessarily linking
+ `libmpx'. If `libmpx' is available as a shared library, and the
+ `-static' option is not used, then this links against the shared
+ version of `libmpx'. The `-static-libmpx' option directs the GCC
+ driver to link `libmpx' statically, without necessarily linking
other libraries statically.
-'-static-libmpxwrappers'
- When the '-fcheck-pointer bounds' and '-mmpx' options are used to
- link a program without also using '-fno-chkp-use-wrappers', the GCC
- driver automatically links against 'libmpxwrappers'. If
- 'libmpxwrappers' is available as a shared library, and the
- '-static' option is not used, then this links against the shared
- version of 'libmpxwrappers'. The '-static-libmpxwrappers' option
- directs the GCC driver to link 'libmpxwrappers' statically, without
- necessarily linking other libraries statically.
-
-'-static-libstdc++'
- When the 'g++' program is used to link a C++ program, it normally
- automatically links against 'libstdc++'. If 'libstdc++' is
- available as a shared library, and the '-static' option is not
- used, then this links against the shared version of 'libstdc++'.
+`-static-libmpxwrappers'
+ When the `-fcheck-pointer bounds' and `-mmpx' options are used to
+ link a program without also using `-fno-chkp-use-wrappers', the
+ GCC driver automatically links against `libmpxwrappers'. If
+ `libmpxwrappers' is available as a shared library, and the
+ `-static' option is not used, then this links against the shared
+ version of `libmpxwrappers'. The `-static-libmpxwrappers' option
+ directs the GCC driver to link `libmpxwrappers' statically,
+ without necessarily linking other libraries statically.
+
+`-static-libstdc++'
+ When the `g++' program is used to link a C++ program, it normally
+ automatically links against `libstdc++'. If `libstdc++' is
+ available as a shared library, and the `-static' option is not
+ used, then this links against the shared version of `libstdc++'.
That is normally fine. However, it is sometimes useful to freeze
- the version of 'libstdc++' used by the program without going all
- the way to a fully static link. The '-static-libstdc++' option
- directs the 'g++' driver to link 'libstdc++' statically, without
+ the version of `libstdc++' used by the program without going all
+ the way to a fully static link. The `-static-libstdc++' option
+ directs the `g++' driver to link `libstdc++' statically, without
necessarily linking other libraries statically.
-'-symbolic'
+`-symbolic'
Bind references to global symbols when building a shared object.
- Warn about any unresolved references (unless overridden by the link
- editor option '-Xlinker -z -Xlinker defs'). Only a few systems
- support this option.
+ Warn about any unresolved references (unless overridden by the
+ link editor option `-Xlinker -z -Xlinker defs'). Only a few
+ systems support this option.
-'-T SCRIPT'
+`-T SCRIPT'
Use SCRIPT as the linker script. This option is supported by most
systems using the GNU linker. On some targets, such as bare-board
- targets without an operating system, the '-T' option may be
+ targets without an operating system, the `-T' option may be
required when linking to avoid references to undefined symbols.
-'-Xlinker OPTION'
- Pass OPTION as an option to the linker. You can use this to supply
- system-specific linker options that GCC does not recognize.
+`-Xlinker OPTION'
+ Pass OPTION as an option to the linker. You can use this to
+ supply system-specific linker options that GCC does not recognize.
If you want to pass an option that takes a separate argument, you
- must use '-Xlinker' twice, once for the option and once for the
- argument. For example, to pass '-assert definitions', you must
- write '-Xlinker -assert -Xlinker definitions'. It does not work to
- write '-Xlinker "-assert definitions"', because this passes the
+ must use `-Xlinker' twice, once for the option and once for the
+ argument. For example, to pass `-assert definitions', you must
+ write `-Xlinker -assert -Xlinker definitions'. It does not work
+ to write `-Xlinker "-assert definitions"', because this passes the
entire string as a single argument, which is not what the linker
expects.
When using the GNU linker, it is usually more convenient to pass
- arguments to linker options using the 'OPTION=VALUE' syntax than as
- separate arguments. For example, you can specify '-Xlinker
- -Map=output.map' rather than '-Xlinker -Map -Xlinker output.map'.
+ arguments to linker options using the `OPTION=VALUE' syntax than
+ as separate arguments. For example, you can specify `-Xlinker
+ -Map=output.map' rather than `-Xlinker -Map -Xlinker output.map'.
Other linkers may not support this syntax for command-line options.
-'-Wl,OPTION'
- Pass OPTION as an option to the linker. If OPTION contains commas,
- it is split into multiple options at the commas. You can use this
- syntax to pass an argument to the option. For example,
- '-Wl,-Map,output.map' passes '-Map output.map' to the linker. When
- using the GNU linker, you can also get the same effect with
- '-Wl,-Map=output.map'.
-
-'-u SYMBOL'
- Pretend the symbol SYMBOL is undefined, to force linking of library
- modules to define it. You can use '-u' multiple times with
+`-Wl,OPTION'
+ Pass OPTION as an option to the linker. If OPTION contains
+ commas, it is split into multiple options at the commas. You can
+ use this syntax to pass an argument to the option. For example,
+ `-Wl,-Map,output.map' passes `-Map output.map' to the linker.
+ When using the GNU linker, you can also get the same effect with
+ `-Wl,-Map=output.map'.
+
+`-u SYMBOL'
+ Pretend the symbol SYMBOL is undefined, to force linking of
+ library modules to define it. You can use `-u' multiple times with
different symbols to force loading of additional library modules.
-'-z KEYWORD'
- '-z' is passed directly on to the linker along with the keyword
- KEYWORD. See the section in the documentation of your linker for
+`-z KEYWORD'
+ `-z' is passed directly on to the linker along with the keyword
+ KEYWORD. See the section in the documentation of your linker for
permitted values and their meanings.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) On some systems, 'gcc -shared' needs to build supplementary stub
-code for constructors to work. On multi-libbed systems, 'gcc -shared'
+ (1) On some systems, `gcc -shared' needs to build supplementary stub
+code for constructors to work. On multi-libbed systems, `gcc -shared'
must select the correct support libraries to link against. Failing to
supply the correct flags may lead to subtle defects. Supplying them in
cases where they are not necessary is innocuous.
@@ -11109,133 +11182,135 @@ File: gcc.info, Node: Directory Options, Next: Spec Files, Prev: Link Options
These options specify directories to search for header files, for
libraries and for parts of the compiler:
-'-IDIR'
+`-IDIR'
Add the directory DIR to the head of the list of directories to be
searched for header files. This can be used to override a system
- header file, substituting your own version, since these directories
- are searched before the system header file directories. However,
- you should not use this option to add directories that contain
- vendor-supplied system header files (use '-isystem' for that). If
- you use more than one '-I' option, the directories are scanned in
- left-to-right order; the standard system directories come after.
+ header file, substituting your own version, since these
+ directories are searched before the system header file
+ directories. However, you should not use this option to add
+ directories that contain vendor-supplied system header files (use
+ `-isystem' for that). If you use more than one `-I' option, the
+ directories are scanned in left-to-right order; the standard
+ system directories come after.
If a standard system include directory, or a directory specified
- with '-isystem', is also specified with '-I', the '-I' option is
- ignored. The directory is still searched but as a system directory
- at its normal position in the system include chain. This is to
- ensure that GCC's procedure to fix buggy system headers and the
- ordering for the 'include_next' directive are not inadvertently
- changed. If you really need to change the search order for system
- directories, use the '-nostdinc' and/or '-isystem' options.
-
-'-iplugindir=DIR'
+ with `-isystem', is also specified with `-I', the `-I' option is
+ ignored. The directory is still searched but as a system
+ directory at its normal position in the system include chain.
+ This is to ensure that GCC's procedure to fix buggy system headers
+ and the ordering for the `include_next' directive are not
+ inadvertently changed. If you really need to change the search
+ order for system directories, use the `-nostdinc' and/or
+ `-isystem' options.
+
+`-iplugindir=DIR'
Set the directory to search for plugins that are passed by
- '-fplugin=NAME' instead of '-fplugin=PATH/NAME.so'. This option is
- not meant to be used by the user, but only passed by the driver.
+ `-fplugin=NAME' instead of `-fplugin=PATH/NAME.so'. This option
+ is not meant to be used by the user, but only passed by the driver.
-'-iquoteDIR'
+`-iquoteDIR'
Add the directory DIR to the head of the list of directories to be
- searched for header files only for the case of '#include "FILE"';
- they are not searched for '#include <FILE>', otherwise just like
- '-I'.
+ searched for header files only for the case of `#include "FILE"';
+ they are not searched for `#include <FILE>', otherwise just like
+ `-I'.
-'-LDIR'
+`-LDIR'
Add directory DIR to the list of directories to be searched for
- '-l'.
+ `-l'.
-'-BPREFIX'
+`-BPREFIX'
This option specifies where to find the executables, libraries,
include files, and data files of the compiler itself.
The compiler driver program runs one or more of the subprograms
- 'cpp', 'cc1', 'as' and 'ld'. It tries PREFIX as a prefix for each
- program it tries to run, both with and without 'MACHINE/VERSION/'
+ `cpp', `cc1', `as' and `ld'. It tries PREFIX as a prefix for each
+ program it tries to run, both with and without `MACHINE/VERSION/'
(*note Target Options::).
For each subprogram to be run, the compiler driver first tries the
- '-B' prefix, if any. If that name is not found, or if '-B' is not
- specified, the driver tries two standard prefixes, '/usr/lib/gcc/'
- and '/usr/local/lib/gcc/'. If neither of those results in a file
+ `-B' prefix, if any. If that name is not found, or if `-B' is not
+ specified, the driver tries two standard prefixes, `/usr/lib/gcc/'
+ and `/usr/local/lib/gcc/'. If neither of those results in a file
name that is found, the unmodified program name is searched for
- using the directories specified in your 'PATH' environment
+ using the directories specified in your `PATH' environment
variable.
- The compiler checks to see if the path provided by '-B' refers to a
- directory, and if necessary it adds a directory separator character
- at the end of the path.
+ The compiler checks to see if the path provided by `-B' refers to
+ a directory, and if necessary it adds a directory separator
+ character at the end of the path.
- '-B' prefixes that effectively specify directory names also apply
+ `-B' prefixes that effectively specify directory names also apply
to libraries in the linker, because the compiler translates these
- options into '-L' options for the linker. They also apply to
+ options into `-L' options for the linker. They also apply to
include files in the preprocessor, because the compiler translates
- these options into '-isystem' options for the preprocessor. In
- this case, the compiler appends 'include' to the prefix.
+ these options into `-isystem' options for the preprocessor. In
+ this case, the compiler appends `include' to the prefix.
- The runtime support file 'libgcc.a' can also be searched for using
- the '-B' prefix, if needed. If it is not found there, the two
+ The runtime support file `libgcc.a' can also be searched for using
+ the `-B' prefix, if needed. If it is not found there, the two
standard prefixes above are tried, and that is all. The file is
left out of the link if it is not found by those means.
- Another way to specify a prefix much like the '-B' prefix is to use
- the environment variable 'GCC_EXEC_PREFIX'. *Note Environment
+ Another way to specify a prefix much like the `-B' prefix is to use
+ the environment variable `GCC_EXEC_PREFIX'. *Note Environment
Variables::.
- As a special kludge, if the path provided by '-B' is
- '[dir/]stageN/', where N is a number in the range 0 to 9, then it
- is replaced by '[dir/]include'. This is to help with
+ As a special kludge, if the path provided by `-B' is
+ `[dir/]stageN/', where N is a number in the range 0 to 9, then it
+ is replaced by `[dir/]include'. This is to help with
boot-strapping the compiler.
-'-specs=FILE'
- Process FILE after the compiler reads in the standard 'specs' file,
- in order to override the defaults which the 'gcc' driver program
- uses when determining what switches to pass to 'cc1', 'cc1plus',
- 'as', 'ld', etc. More than one '-specs=FILE' can be specified on
- the command line, and they are processed in order, from left to
- right.
+`-specs=FILE'
+ Process FILE after the compiler reads in the standard `specs'
+ file, in order to override the defaults which the `gcc' driver
+ program uses when determining what switches to pass to `cc1',
+ `cc1plus', `as', `ld', etc. More than one `-specs=FILE' can be
+ specified on the command line, and they are processed in order,
+ from left to right.
-'--sysroot=DIR'
+`--sysroot=DIR'
Use DIR as the logical root directory for headers and libraries.
For example, if the compiler normally searches for headers in
- '/usr/include' and libraries in '/usr/lib', it instead searches
- 'DIR/usr/include' and 'DIR/usr/lib'.
+ `/usr/include' and libraries in `/usr/lib', it instead searches
+ `DIR/usr/include' and `DIR/usr/lib'.
- If you use both this option and the '-isysroot' option, then the
- '--sysroot' option applies to libraries, but the '-isysroot' option
- applies to header files.
+ If you use both this option and the `-isysroot' option, then the
+ `--sysroot' option applies to libraries, but the `-isysroot'
+ option applies to header files.
The GNU linker (beginning with version 2.16) has the necessary
support for this option. If your linker does not support this
- option, the header file aspect of '--sysroot' still works, but the
+ option, the header file aspect of `--sysroot' still works, but the
library aspect does not.
-'--no-sysroot-suffix'
+`--no-sysroot-suffix'
For some targets, a suffix is added to the root directory specified
- with '--sysroot', depending on the other options used, so that
- headers may for example be found in 'DIR/SUFFIX/usr/include'
- instead of 'DIR/usr/include'. This option disables the addition of
+ with `--sysroot', depending on the other options used, so that
+ headers may for example be found in `DIR/SUFFIX/usr/include'
+ instead of `DIR/usr/include'. This option disables the addition of
such a suffix.
-'-I-'
- This option has been deprecated. Please use '-iquote' instead for
- '-I' directories before the '-I-' and remove the '-I-' option. Any
- directories you specify with '-I' options before the '-I-' option
- are searched only for the case of '#include "FILE"'; they are not
- searched for '#include <FILE>'.
+`-I-'
+ This option has been deprecated. Please use `-iquote' instead for
+ `-I' directories before the `-I-' and remove the `-I-' option.
+ Any directories you specify with `-I' options before the `-I-'
+ option are searched only for the case of `#include "FILE"'; they
+ are not searched for `#include <FILE>'.
- If additional directories are specified with '-I' options after the
- '-I-' option, these directories are searched for all '#include'
- directives. (Ordinarily _all_ '-I' directories are used this way.)
+ If additional directories are specified with `-I' options after
+ the `-I-' option, these directories are searched for all `#include'
+ directives. (Ordinarily _all_ `-I' directories are used this way.)
- In addition, the '-I-' option inhibits the use of the current
+ In addition, the `-I-' option inhibits the use of the current
directory (where the current input file came from) as the first
- search directory for '#include "FILE"'. There is no way to
- override this effect of '-I-'. With '-I.' you can specify
+ search directory for `#include "FILE"'. There is no way to
+ override this effect of `-I-'. With `-I.' you can specify
searching the directory that is current when the compiler is
invoked. That is not exactly the same as what the preprocessor
does by default, but it is often satisfactory.
- '-I-' does not inhibit the use of the standard system directories
- for header files. Thus, '-I-' and '-nostdinc' are independent.
+ `-I-' does not inhibit the use of the standard system directories
+ for header files. Thus, `-I-' and `-nostdinc' are independent.

File: gcc.info, Node: Spec Files, Next: Target Options, Prev: Directory Options, Up: Invoking GCC
@@ -11243,37 +11318,39 @@ File: gcc.info, Node: Spec Files, Next: Target Options, Prev: Directory Optio
3.15 Specifying Subprocesses and the Switches to Pass to Them
=============================================================
-'gcc' is a driver program. It performs its job by invoking a sequence
+`gcc' is a driver program. It performs its job by invoking a sequence
of other programs to do the work of compiling, assembling and linking.
GCC interprets its command-line parameters and uses these to deduce
-which programs it should invoke, and which command-line options it ought
-to place on their command lines. This behavior is controlled by "spec
-strings". In most cases there is one spec string for each program that
-GCC can invoke, but a few programs have multiple spec strings to control
-their behavior. The spec strings built into GCC can be overridden by
-using the '-specs=' command-line switch to specify a spec file.
+which programs it should invoke, and which command-line options it
+ought to place on their command lines. This behavior is controlled by
+"spec strings". In most cases there is one spec string for each
+program that GCC can invoke, but a few programs have multiple spec
+strings to control their behavior. The spec strings built into GCC can
+be overridden by using the `-specs=' command-line switch to specify a
+spec file.
"Spec files" are plaintext files that are used to construct spec
strings. They consist of a sequence of directives separated by blank
lines. The type of directive is determined by the first non-whitespace
character on the line, which can be one of the following:
-'%COMMAND'
+`%COMMAND'
Issues a COMMAND to the spec file processor. The commands that can
appear here are:
- '%include <FILE>'
+ `%include <FILE>'
Search for FILE and insert its text at the current point in
the specs file.
- '%include_noerr <FILE>'
- Just like '%include', but do not generate an error message if
+ `%include_noerr <FILE>'
+ Just like `%include', but do not generate an error message if
the include file cannot be found.
- '%rename OLD_NAME NEW_NAME'
+ `%rename OLD_NAME NEW_NAME'
Rename the spec string OLD_NAME to NEW_NAME.
-'*[SPEC_NAME]:'
+
+`*[SPEC_NAME]:'
This tells the compiler to create, override or delete the named
spec string. All lines after this directive up to the next
directive or blank line are considered to be the text for the spec
@@ -11282,11 +11359,11 @@ character on the line, which can be one of the following:
Otherwise, if the spec does not currently exist a new spec is
created. If the spec does exist then its contents are overridden
by the text of this directive, unless the first character of that
- text is the '+' character, in which case the text is appended to
+ text is the `+' character, in which case the text is appended to
the spec.
-'[SUFFIX]:'
- Creates a new '[SUFFIX] spec' pair. All lines after this directive
+`[SUFFIX]:'
+ Creates a new `[SUFFIX] spec' pair. All lines after this directive
and up to the next directive or blank line are considered to make
up the spec string for the indicated suffix. When the compiler
encounters an input file with the named suffix, it processes the
@@ -11296,17 +11373,17 @@ character on the line, which can be one of the following:
.ZZ:
z-compile -input %i
- This says that any input file whose name ends in '.ZZ' should be
- passed to the program 'z-compile', which should be invoked with the
- command-line switch '-input' and with the result of performing the
- '%i' substitution. (See below.)
+ This says that any input file whose name ends in `.ZZ' should be
+ passed to the program `z-compile', which should be invoked with the
+ command-line switch `-input' and with the result of performing the
+ `%i' substitution. (See below.)
As an alternative to providing a spec string, the text following a
suffix directive can be one of the following:
- '@LANGUAGE'
+ `@LANGUAGE'
This says that the suffix is an alias for a known LANGUAGE.
- This is similar to using the '-x' command-line switch to GCC
+ This is similar to using the `-x' command-line switch to GCC
to specify a language explicitly. For example:
.ZZ:
@@ -11314,7 +11391,7 @@ character on the line, which can be one of the following:
Says that .ZZ files are, in fact, C++ source files.
- '#NAME'
+ `#NAME'
This causes an error messages saying:
NAME compiler not installed on this system.
@@ -11325,6 +11402,7 @@ character on the line, which can be one of the following:
effectively possible to override earlier entries using this
technique.
+
GCC has the following spec strings built into it. Spec files can
override these strings or create their own. Note that individual
targets can also add their own spec strings to this list.
@@ -11340,7 +11418,7 @@ targets can also add their own spec strings to this list.
libgcc Decides which GCC support library to pass to the linker
linker Sets the name of the linker
predefines Defines to be passed to the C preprocessor
- signed_char Defines to pass to CPP to say whether char is signed
+ signed_char Defines to pass to CPP to say whether `char' is signed
by default
startfile Object files to include at the start of the link
@@ -11351,292 +11429,293 @@ targets can also add their own spec strings to this list.
*lib:
--start-group -lgcc -lc -leval1 --end-group %(old_lib)
- This example renames the spec called 'lib' to 'old_lib' and then
-overrides the previous definition of 'lib' with a new one. The new
+ This example renames the spec called `lib' to `old_lib' and then
+overrides the previous definition of `lib' with a new one. The new
definition adds in some extra command-line options before including the
text of the old definition.
"Spec strings" are a list of command-line options to be passed to their
corresponding program. In addition, the spec strings can contain
-'%'-prefixed sequences to substitute variable text or to conditionally
+`%'-prefixed sequences to substitute variable text or to conditionally
insert text into the command line. Using these constructs it is
possible to generate quite complex command lines.
- Here is a table of all defined '%'-sequences for spec strings. Note
+ Here is a table of all defined `%'-sequences for spec strings. Note
that spaces are not generated automatically around the results of
expanding these sequences. Therefore you can concatenate them together
or combine them with constant text in a single argument.
-'%%'
- Substitute one '%' into the program name or argument.
+`%%'
+ Substitute one `%' into the program name or argument.
-'%i'
+`%i'
Substitute the name of the input file being processed.
-'%b'
- Substitute the basename of the input file being processed. This is
- the substring up to (and not including) the last period and not
+`%b'
+ Substitute the basename of the input file being processed. This
+ is the substring up to (and not including) the last period and not
including the directory.
-'%B'
- This is the same as '%b', but include the file suffix (text after
+`%B'
+ This is the same as `%b', but include the file suffix (text after
the last period).
-'%d'
- Marks the argument containing or following the '%d' as a temporary
+`%d'
+ Marks the argument containing or following the `%d' as a temporary
file name, so that that file is deleted if GCC exits successfully.
- Unlike '%g', this contributes no text to the argument.
+ Unlike `%g', this contributes no text to the argument.
-'%gSUFFIX'
+`%gSUFFIX'
Substitute a file name that has suffix SUFFIX and is chosen once
- per compilation, and mark the argument in the same way as '%d'. To
- reduce exposure to denial-of-service attacks, the file name is now
- chosen in a way that is hard to predict even when previously chosen
- file names are known. For example, '%g.s ... %g.o ... %g.s' might
- turn into 'ccUVUUAU.s ccXYAXZ12.o ccUVUUAU.s'. SUFFIX matches the
- regexp '[.A-Za-z]*' or the special string '%O', which is treated
- exactly as if '%O' had been preprocessed. Previously, '%g' was
- simply substituted with a file name chosen once per compilation,
- without regard to any appended suffix (which was therefore treated
- just like ordinary text), making such attacks more likely to
- succeed.
-
-'%uSUFFIX'
- Like '%g', but generates a new temporary file name each time it
+ per compilation, and mark the argument in the same way as `%d'.
+ To reduce exposure to denial-of-service attacks, the file name is
+ now chosen in a way that is hard to predict even when previously
+ chosen file names are known. For example, `%g.s ... %g.o ... %g.s'
+ might turn into `ccUVUUAU.s ccXYAXZ12.o ccUVUUAU.s'. SUFFIX
+ matches the regexp `[.A-Za-z]*' or the special string `%O', which
+ is treated exactly as if `%O' had been preprocessed. Previously,
+ `%g' was simply substituted with a file name chosen once per
+ compilation, without regard to any appended suffix (which was
+ therefore treated just like ordinary text), making such attacks
+ more likely to succeed.
+
+`%uSUFFIX'
+ Like `%g', but generates a new temporary file name each time it
appears instead of once per compilation.
-'%USUFFIX'
- Substitutes the last file name generated with '%uSUFFIX',
+`%USUFFIX'
+ Substitutes the last file name generated with `%uSUFFIX',
generating a new one if there is no such last file name. In the
- absence of any '%uSUFFIX', this is just like '%gSUFFIX', except
- they don't share the same suffix _space_, so '%g.s ... %U.s ...
+ absence of any `%uSUFFIX', this is just like `%gSUFFIX', except
+ they don't share the same suffix _space_, so `%g.s ... %U.s ...
%g.s ... %U.s' involves the generation of two distinct file names,
- one for each '%g.s' and another for each '%U.s'. Previously, '%U'
+ one for each `%g.s' and another for each `%U.s'. Previously, `%U'
was simply substituted with a file name chosen for the previous
- '%u', without regard to any appended suffix.
+ `%u', without regard to any appended suffix.
-'%jSUFFIX'
- Substitutes the name of the 'HOST_BIT_BUCKET', if any, and if it is
- writable, and if '-save-temps' is not used; otherwise, substitute
- the name of a temporary file, just like '%u'. This temporary file
+`%jSUFFIX'
+ Substitutes the name of the `HOST_BIT_BUCKET', if any, and if it is
+ writable, and if `-save-temps' is not used; otherwise, substitute
+ the name of a temporary file, just like `%u'. This temporary file
is not meant for communication between processes, but rather as a
junk disposal mechanism.
-'%|SUFFIX'
-'%mSUFFIX'
- Like '%g', except if '-pipe' is in effect. In that case '%|'
- substitutes a single dash and '%m' substitutes nothing at all.
+`%|SUFFIX'
+`%mSUFFIX'
+ Like `%g', except if `-pipe' is in effect. In that case `%|'
+ substitutes a single dash and `%m' substitutes nothing at all.
These are the two most common ways to instruct a program that it
should read from standard input or write to standard output. If
- you need something more elaborate you can use an '%{pipe:'X'}'
- construct: see for example 'f/lang-specs.h'.
+ you need something more elaborate you can use an `%{pipe:`X'}'
+ construct: see for example `f/lang-specs.h'.
-'%.SUFFIX'
+`%.SUFFIX'
Substitutes .SUFFIX for the suffixes of a matched switch's args
- when it is subsequently output with '%*'. SUFFIX is terminated by
+ when it is subsequently output with `%*'. SUFFIX is terminated by
the next space or %.
-'%w'
- Marks the argument containing or following the '%w' as the
+`%w'
+ Marks the argument containing or following the `%w' as the
designated output file of this compilation. This puts the argument
- into the sequence of arguments that '%o' substitutes.
+ into the sequence of arguments that `%o' substitutes.
-'%o'
+`%o'
Substitutes the names of all the output files, with spaces
automatically placed around them. You should write spaces around
- the '%o' as well or the results are undefined. '%o' is for use in
+ the `%o' as well or the results are undefined. `%o' is for use in
the specs for running the linker. Input files whose names have no
recognized suffix are not compiled at all, but they are included
among the output files, so they are linked.
-'%O'
- Substitutes the suffix for object files. Note that this is handled
- specially when it immediately follows '%g, %u, or %U', because of
- the need for those to form complete file names. The handling is
- such that '%O' is treated exactly as if it had already been
- substituted, except that '%g, %u, and %U' do not currently support
- additional SUFFIX characters following '%O' as they do following,
- for example, '.o'.
+`%O'
+ Substitutes the suffix for object files. Note that this is
+ handled specially when it immediately follows `%g, %u, or %U',
+ because of the need for those to form complete file names. The
+ handling is such that `%O' is treated exactly as if it had already
+ been substituted, except that `%g, %u, and %U' do not currently
+ support additional SUFFIX characters following `%O' as they do
+ following, for example, `.o'.
-'%p'
+`%p'
Substitutes the standard macro predefinitions for the current
- target machine. Use this when running 'cpp'.
+ target machine. Use this when running `cpp'.
-'%P'
- Like '%p', but puts '__' before and after the name of each
- predefined macro, except for macros that start with '__' or with
- '_L', where L is an uppercase letter. This is for ISO C.
+`%P'
+ Like `%p', but puts `__' before and after the name of each
+ predefined macro, except for macros that start with `__' or with
+ `_L', where L is an uppercase letter. This is for ISO C.
-'%I'
- Substitute any of '-iprefix' (made from 'GCC_EXEC_PREFIX'),
- '-isysroot' (made from 'TARGET_SYSTEM_ROOT'), '-isystem' (made from
- 'COMPILER_PATH' and '-B' options) and '-imultilib' as necessary.
+`%I'
+ Substitute any of `-iprefix' (made from `GCC_EXEC_PREFIX'),
+ `-isysroot' (made from `TARGET_SYSTEM_ROOT'), `-isystem' (made
+ from `COMPILER_PATH' and `-B' options) and `-imultilib' as
+ necessary.
-'%s'
+`%s'
Current argument is the name of a library or startup file of some
sort. Search for that file in a standard list of directories and
substitute the full name found. The current working directory is
included in the list of directories scanned.
-'%T'
+`%T'
Current argument is the name of a linker script. Search for that
- file in the current list of directories to scan for libraries. If
- the file is located insert a '--script' option into the command
+ file in the current list of directories to scan for libraries. If
+ the file is located insert a `--script' option into the command
line followed by the full path name found. If the file is not
found then generate an error message. Note: the current working
directory is not searched.
-'%eSTR'
+`%eSTR'
Print STR as an error message. STR is terminated by a newline.
Use this when inconsistent options are detected.
-'%(NAME)'
+`%(NAME)'
Substitute the contents of spec string NAME at this point.
-'%x{OPTION}'
- Accumulate an option for '%X'.
+`%x{OPTION}'
+ Accumulate an option for `%X'.
-'%X'
- Output the accumulated linker options specified by '-Wl' or a '%x'
+`%X'
+ Output the accumulated linker options specified by `-Wl' or a `%x'
spec string.
-'%Y'
- Output the accumulated assembler options specified by '-Wa'.
+`%Y'
+ Output the accumulated assembler options specified by `-Wa'.
-'%Z'
- Output the accumulated preprocessor options specified by '-Wp'.
+`%Z'
+ Output the accumulated preprocessor options specified by `-Wp'.
-'%a'
- Process the 'asm' spec. This is used to compute the switches to be
- passed to the assembler.
+`%a'
+ Process the `asm' spec. This is used to compute the switches to
+ be passed to the assembler.
-'%A'
- Process the 'asm_final' spec. This is a spec string for passing
+`%A'
+ Process the `asm_final' spec. This is a spec string for passing
switches to an assembler post-processor, if such a program is
needed.
-'%l'
- Process the 'link' spec. This is the spec for computing the
+`%l'
+ Process the `link' spec. This is the spec for computing the
command line passed to the linker. Typically it makes use of the
- '%L %G %S %D and %E' sequences.
+ `%L %G %S %D and %E' sequences.
-'%D'
- Dump out a '-L' option for each directory that GCC believes might
+`%D'
+ Dump out a `-L' option for each directory that GCC believes might
contain startup files. If the target supports multilibs then the
current multilib directory is prepended to each of these paths.
-'%L'
- Process the 'lib' spec. This is a spec string for deciding which
+`%L'
+ Process the `lib' spec. This is a spec string for deciding which
libraries are included on the command line to the linker.
-'%G'
- Process the 'libgcc' spec. This is a spec string for deciding
+`%G'
+ Process the `libgcc' spec. This is a spec string for deciding
which GCC support library is included on the command line to the
linker.
-'%S'
- Process the 'startfile' spec. This is a spec for deciding which
+`%S'
+ Process the `startfile' spec. This is a spec for deciding which
object files are the first ones passed to the linker. Typically
- this might be a file named 'crt0.o'.
+ this might be a file named `crt0.o'.
-'%E'
- Process the 'endfile' spec. This is a spec string that specifies
+`%E'
+ Process the `endfile' spec. This is a spec string that specifies
the last object files that are passed to the linker.
-'%C'
- Process the 'cpp' spec. This is used to construct the arguments to
- be passed to the C preprocessor.
+`%C'
+ Process the `cpp' spec. This is used to construct the arguments
+ to be passed to the C preprocessor.
-'%1'
- Process the 'cc1' spec. This is used to construct the options to
- be passed to the actual C compiler ('cc1').
+`%1'
+ Process the `cc1' spec. This is used to construct the options to
+ be passed to the actual C compiler (`cc1').
-'%2'
- Process the 'cc1plus' spec. This is used to construct the options
- to be passed to the actual C++ compiler ('cc1plus').
+`%2'
+ Process the `cc1plus' spec. This is used to construct the options
+ to be passed to the actual C++ compiler (`cc1plus').
-'%*'
- Substitute the variable part of a matched option. See below. Note
- that each comma in the substituted string is replaced by a single
- space.
+`%*'
+ Substitute the variable part of a matched option. See below.
+ Note that each comma in the substituted string is replaced by a
+ single space.
-'%<S'
- Remove all occurrences of '-S' from the command line. Note--this
- command is position dependent. '%' commands in the spec string
- before this one see '-S', '%' commands in the spec string after
+`%<`S''
+ Remove all occurrences of `-S' from the command line. Note--this
+ command is position dependent. `%' commands in the spec string
+ before this one see `-S', `%' commands in the spec string after
this one do not.
-'%:FUNCTION(ARGS)'
+`%:FUNCTION(ARGS)'
Call the named function FUNCTION, passing it ARGS. ARGS is first
processed as a nested spec string, then split into an argument
vector in the usual fashion. The function returns a string which
- is processed as if it had appeared literally as part of the current
- spec.
+ is processed as if it had appeared literally as part of the
+ current spec.
The following built-in spec functions are provided:
- 'getenv'
- The 'getenv' spec function takes two arguments: an environment
+ ``getenv''
+ The `getenv' spec function takes two arguments: an environment
variable name and a string. If the environment variable is
not defined, a fatal error is issued. Otherwise, the return
value is the value of the environment variable concatenated
- with the string. For example, if 'TOPDIR' is defined as
- '/path/to/top', then:
+ with the string. For example, if `TOPDIR' is defined as
+ `/path/to/top', then:
%:getenv(TOPDIR /include)
- expands to '/path/to/top/include'.
+ expands to `/path/to/top/include'.
- 'if-exists'
- The 'if-exists' spec function takes one argument, an absolute
- pathname to a file. If the file exists, 'if-exists' returns
+ ``if-exists''
+ The `if-exists' spec function takes one argument, an absolute
+ pathname to a file. If the file exists, `if-exists' returns
the pathname. Here is a small example of its usage:
*startfile:
crt0%O%s %:if-exists(crti%O%s) crtbegin%O%s
- 'if-exists-else'
- The 'if-exists-else' spec function is similar to the
- 'if-exists' spec function, except that it takes two arguments.
- The first argument is an absolute pathname to a file. If the
- file exists, 'if-exists-else' returns the pathname. If it
- does not exist, it returns the second argument. This way,
- 'if-exists-else' can be used to select one file or another,
- based on the existence of the first. Here is a small example
- of its usage:
+ ``if-exists-else''
+ The `if-exists-else' spec function is similar to the
+ `if-exists' spec function, except that it takes two
+ arguments. The first argument is an absolute pathname to a
+ file. If the file exists, `if-exists-else' returns the
+ pathname. If it does not exist, it returns the second
+ argument. This way, `if-exists-else' can be used to select
+ one file or another, based on the existence of the first.
+ Here is a small example of its usage:
*startfile:
crt0%O%s %:if-exists(crti%O%s) \
%:if-exists-else(crtbeginT%O%s crtbegin%O%s)
- 'replace-outfile'
- The 'replace-outfile' spec function takes two arguments. It
+ ``replace-outfile''
+ The `replace-outfile' spec function takes two arguments. It
looks for the first argument in the outfiles array and
- replaces it with the second argument. Here is a small example
- of its usage:
+ replaces it with the second argument. Here is a small
+ example of its usage:
%{fgnu-runtime:%:replace-outfile(-lobjc -lobjc-gnu)}
- 'remove-outfile'
- The 'remove-outfile' spec function takes one argument. It
- looks for the first argument in the outfiles array and removes
- it. Here is a small example its usage:
+ ``remove-outfile''
+ The `remove-outfile' spec function takes one argument. It
+ looks for the first argument in the outfiles array and
+ removes it. Here is a small example its usage:
%:remove-outfile(-lm)
- 'pass-through-libs'
- The 'pass-through-libs' spec function takes any number of
- arguments. It finds any '-l' options and any non-options
- ending in '.a' (which it assumes are the names of linker input
- library archive files) and returns a result containing all the
- found arguments each prepended by '-plugin-opt=-pass-through='
- and joined by spaces. This list is intended to be passed to
- the LTO linker plugin.
+ ``pass-through-libs''
+ The `pass-through-libs' spec function takes any number of
+ arguments. It finds any `-l' options and any non-options
+ ending in `.a' (which it assumes are the names of linker
+ input library archive files) and returns a result containing
+ all the found arguments each prepended by
+ `-plugin-opt=-pass-through=' and joined by spaces. This list
+ is intended to be passed to the LTO linker plugin.
%:pass-through-libs(%G %L %G)
- 'print-asm-header'
- The 'print-asm-header' function takes no arguments and simply
+ ``print-asm-header''
+ The `print-asm-header' function takes no arguments and simply
prints a banner like:
Assembler options
@@ -11645,77 +11724,77 @@ or combine them with constant text in a single argument.
Use "-Wa,OPTION" to pass "OPTION" to the assembler.
It is used to separate compiler options from assembler options
- in the '--target-help' output.
+ in the `--target-help' output.
-'%{S}'
- Substitutes the '-S' switch, if that switch is given to GCC. If
+`%{`S'}'
+ Substitutes the `-S' switch, if that switch is given to GCC. If
that switch is not specified, this substitutes nothing. Note that
the leading dash is omitted when specifying this option, and it is
automatically inserted if the substitution is performed. Thus the
- spec string '%{foo}' matches the command-line option '-foo' and
- outputs the command-line option '-foo'.
+ spec string `%{foo}' matches the command-line option `-foo' and
+ outputs the command-line option `-foo'.
-'%W{S}'
- Like %{'S'} but mark last argument supplied within as a file to be
+`%W{`S'}'
+ Like %{`S'} but mark last argument supplied within as a file to be
deleted on failure.
-'%{S*}'
+`%{`S'*}'
Substitutes all the switches specified to GCC whose names start
- with '-S', but which also take an argument. This is used for
- switches like '-o', '-D', '-I', etc. GCC considers '-o foo' as
- being one switch whose name starts with 'o'. %{o*} substitutes
+ with `-S', but which also take an argument. This is used for
+ switches like `-o', `-D', `-I', etc. GCC considers `-o foo' as
+ being one switch whose name starts with `o'. %{o*} substitutes
this text, including the space. Thus two arguments are generated.
-'%{S*&T*}'
- Like %{'S'*}, but preserve order of 'S' and 'T' options (the order
- of 'S' and 'T' in the spec is not significant). There can be any
+`%{`S'*&`T'*}'
+ Like %{`S'*}, but preserve order of `S' and `T' options (the order
+ of `S' and `T' in the spec is not significant). There can be any
number of ampersand-separated variables; for each the wild card is
- optional. Useful for CPP as '%{D*&U*&A*}'.
+ optional. Useful for CPP as `%{D*&U*&A*}'.
-'%{S:X}'
- Substitutes 'X', if the '-S' switch is given to GCC.
+`%{`S':`X'}'
+ Substitutes `X', if the `-S' switch is given to GCC.
-'%{!S:X}'
- Substitutes 'X', if the '-S' switch is _not_ given to GCC.
+`%{!`S':`X'}'
+ Substitutes `X', if the `-S' switch is _not_ given to GCC.
-'%{S*:X}'
- Substitutes 'X' if one or more switches whose names start with '-S'
- are specified to GCC. Normally 'X' is substituted only once, no
- matter how many such switches appeared. However, if '%*' appears
- somewhere in 'X', then 'X' is substituted once for each matching
- switch, with the '%*' replaced by the part of that switch matching
- the '*'.
+`%{`S'*:`X'}'
+ Substitutes `X' if one or more switches whose names start with
+ `-S' are specified to GCC. Normally `X' is substituted only once,
+ no matter how many such switches appeared. However, if `%*'
+ appears somewhere in `X', then `X' is substituted once for each
+ matching switch, with the `%*' replaced by the part of that switch
+ matching the `*'.
- If '%*' appears as the last part of a spec sequence then a space is
- added after the end of the last substitution. If there is more
+ If `%*' appears as the last part of a spec sequence then a space
+ is added after the end of the last substitution. If there is more
text in the sequence, however, then a space is not generated. This
- allows the '%*' substitution to be used as part of a larger string.
- For example, a spec string like this:
+ allows the `%*' substitution to be used as part of a larger
+ string. For example, a spec string like this:
%{mcu=*:--script=%*/memory.ld}
- when matching an option like '-mcu=newchip' produces:
+ when matching an option like `-mcu=newchip' produces:
--script=newchip/memory.ld
-'%{.S:X}'
- Substitutes 'X', if processing a file with suffix 'S'.
+`%{.`S':`X'}'
+ Substitutes `X', if processing a file with suffix `S'.
-'%{!.S:X}'
- Substitutes 'X', if _not_ processing a file with suffix 'S'.
+`%{!.`S':`X'}'
+ Substitutes `X', if _not_ processing a file with suffix `S'.
-'%{,S:X}'
- Substitutes 'X', if processing a file for language 'S'.
+`%{,`S':`X'}'
+ Substitutes `X', if processing a file for language `S'.
-'%{!,S:X}'
- Substitutes 'X', if not processing a file for language 'S'.
+`%{!,`S':`X'}'
+ Substitutes `X', if not processing a file for language `S'.
-'%{S|P:X}'
- Substitutes 'X' if either '-S' or '-P' is given to GCC. This may
- be combined with '!', '.', ',', and '*' sequences as well, although
- they have a stronger binding than the '|'. If '%*' appears in 'X',
- all of the alternatives must be starred, and only the first
- matching alternative is substituted.
+`%{`S'|`P':`X'}'
+ Substitutes `X' if either `-S' or `-P' is given to GCC. This may
+ be combined with `!', `.', `,', and `*' sequences as well,
+ although they have a stronger binding than the `|'. If `%*'
+ appears in `X', all of the alternatives must be starred, and only
+ the first matching alternative is substituted.
For example, a spec string like this:
@@ -11729,29 +11808,29 @@ or combine them with constant text in a single argument.
-d fred.c -foo -baz -boggle
-d jim.d -bar -baz -boggle
-'%{S:X; T:Y; :D}'
+`%{S:X; T:Y; :D}'
+ If `S' is given to GCC, substitutes `X'; else if `T' is given to
+ GCC, substitutes `Y'; else substitutes `D'. There can be as many
+ clauses as you need. This may be combined with `.', `,', `!',
+ `|', and `*' as needed.
- If 'S' is given to GCC, substitutes 'X'; else if 'T' is given to
- GCC, substitutes 'Y'; else substitutes 'D'. There can be as many
- clauses as you need. This may be combined with '.', ',', '!', '|',
- and '*' as needed.
- The conditional text 'X' in a %{'S':'X'} or similar construct may
-contain other nested '%' constructs or spaces, or even newlines. They
-are processed as usual, as described above. Trailing white space in 'X'
-is ignored. White space may also appear anywhere on the left side of
-the colon in these constructs, except between '.' or '*' and the
+ The conditional text `X' in a %{`S':`X'} or similar construct may
+contain other nested `%' constructs or spaces, or even newlines. They
+are processed as usual, as described above. Trailing white space in
+`X' is ignored. White space may also appear anywhere on the left side
+of the colon in these constructs, except between `.' or `*' and the
corresponding word.
- The '-O', '-f', '-m', and '-W' switches are handled specifically in
-these constructs. If another value of '-O' or the negated form of a
-'-f', '-m', or '-W' switch is found later in the command line, the
-earlier switch value is ignored, except with {'S'*} where 'S' is just
+ The `-O', `-f', `-m', and `-W' switches are handled specifically in
+these constructs. If another value of `-O' or the negated form of a
+`-f', `-m', or `-W' switch is found later in the command line, the
+earlier switch value is ignored, except with {`S'*} where `S' is just
one letter, which passes all matching options.
- The character '|' at the beginning of the predicate text is used to
+ The character `|' at the beginning of the predicate text is used to
indicate that a command should be piped to the following command, but
-only if '-pipe' is specified.
+only if `-pipe' is specified.
It is built into GCC which switches take arguments and which do not.
(You might think it would be useful to generalize this to allow each
@@ -11761,7 +11840,7 @@ files have been specified without knowing which switches take arguments,
and it must know which input files to compile in order to tell which
compilers to run).
- GCC also knows implicitly that arguments starting in '-l' are to be
+ GCC also knows implicitly that arguments starting in `-l' are to be
treated as compiler output files, and passed to the linker in their
proper position among the other output files.
@@ -11771,8 +11850,8 @@ File: gcc.info, Node: Target Options, Next: Submodel Options, Prev: Spec File
3.16 Specifying Target Machine and Compiler Version
===================================================
-The usual way to run GCC is to run the executable called 'gcc', or
-'MACHINE-gcc' when cross-compiling, or 'MACHINE-gcc-VERSION' to run a
+The usual way to run GCC is to run the executable called `gcc', or
+`MACHINE-gcc' when cross-compiling, or `MACHINE-gcc-VERSION' to run a
version other than the one that was installed last.

@@ -11782,7 +11861,7 @@ File: gcc.info, Node: Submodel Options, Next: Code Gen Options, Prev: Target
=======================================
Each target machine types can have its own special options, starting
-with '-m', to choose among various hardware models or
+with `-m', to choose among various hardware models or
configurations--for example, 68010 vs 68020, floating coprocessor or
none. A single installed version of the compiler can compile for any
model or configuration, according to the options specified.
@@ -11859,75 +11938,81 @@ File: gcc.info, Node: AArch64 Options, Next: Adapteva Epiphany Options, Up: S
These options are defined for AArch64 implementations:
-'-mabi=NAME'
- Generate code for the specified data model. Permissible values are
- 'ilp32' for SysV-like data model where int, long int and pointer
- are 32-bit, and 'lp64' for SysV-like data model where int is
- 32-bit, but long int and pointer are 64-bit.
+`-mabi=NAME'
+ Generate code for the specified data model. Permissible values
+ are `ilp32' for SysV-like data model where int, long int and
+ pointer are 32-bit, and `lp64' for SysV-like data model where int
+ is 32-bit, but long int and pointer are 64-bit.
The default depends on the specific target configuration. Note
that the LP64 and ILP32 ABIs are not link-compatible; you must
compile your entire program with the same ABI, and link with a
compatible set of libraries.
-'-mbig-endian'
+`-mbig-endian'
Generate big-endian code. This is the default when GCC is
- configured for an 'aarch64_be-*-*' target.
+ configured for an `aarch64_be-*-*' target.
-'-mgeneral-regs-only'
+`-mgeneral-regs-only'
Generate code which uses only the general registers.
-'-mlittle-endian'
+`-mlittle-endian'
Generate little-endian code. This is the default when GCC is
- configured for an 'aarch64-*-*' but not an 'aarch64_be-*-*' target.
+ configured for an `aarch64-*-*' but not an `aarch64_be-*-*' target.
-'-mcmodel=tiny'
+`-mcmodel=tiny'
Generate code for the tiny code model. The program and its
statically defined symbols must be within 1GB of each other.
Pointers are 64 bits. Programs can be statically or dynamically
linked. This model is not fully implemented and mostly treated as
- 'small'.
+ `small'.
-'-mcmodel=small'
+`-mcmodel=small'
Generate code for the small code model. The program and its
statically defined symbols must be within 4GB of each other.
Pointers are 64 bits. Programs can be statically or dynamically
linked. This is the default code model.
-'-mcmodel=large'
+`-mcmodel=large'
Generate code for the large code model. This makes no assumptions
about addresses and sizes of sections. Pointers are 64 bits.
Programs can be statically linked only.
-'-mstrict-align'
+`-mstrict-align'
Do not assume that unaligned memory references are handled by the
system.
-'-momit-leaf-frame-pointer'
-'-mno-omit-leaf-frame-pointer'
+`-momit-leaf-frame-pointer'
+`-mno-omit-leaf-frame-pointer'
Omit or keep the frame pointer in leaf functions. The former
behaviour is the default.
-'-mtls-dialect=desc'
+`-mtls-dialect=desc'
Use TLS descriptors as the thread-local storage mechanism for
dynamic accesses of TLS variables. This is the default.
-'-mtls-dialect=traditional'
+`-mtls-dialect=traditional'
Use traditional TLS as the thread-local storage mechanism for
dynamic accesses of TLS variables.
-'-mfix-cortex-a53-835769'
-'-mno-fix-cortex-a53-835769'
+`-mfix-cortex-a53-835769'
+`-mno-fix-cortex-a53-835769'
Enable or disable the workaround for the ARM Cortex-A53 erratum
number 835769. This involves inserting a NOP instruction between
memory instructions and 64-bit integer multiply-accumulate
instructions.
-'-march=NAME'
- Specify the name of the target architecture, optionally suffixed by
- one or more feature modifiers. This option has the form
- '-march=ARCH{+[no]FEATURE}*', where the only permissible value for
- ARCH is 'armv8-a'. The permissible values for FEATURE are
+`-mfix-cortex-a53-843419'
+`-mno-fix-cortex-a53-843419'
+ Enable or disable the workaround for the ARM Cortex-A53 erratum
+ number 843419. This erratum workaround is made at link time and
+ this will only pass the corresponding flag to the linker.
+
+`-march=NAME'
+ Specify the name of the target architecture, optionally suffixed
+ by one or more feature modifiers. This option has the form
+ `-march=ARCH{+[no]FEATURE}*', where the only permissible value for
+ ARCH is `armv8-a'. The permissible values for FEATURE are
documented in the sub-section below.
Where conflicting feature modifiers are specified, the right-most
@@ -11936,31 +12021,31 @@ These options are defined for AArch64 implementations:
GCC uses this name to determine what kind of instructions it can
emit when generating assembly code.
- Where '-march' is specified without either of '-mtune' or '-mcpu'
+ Where `-march' is specified without either of `-mtune' or `-mcpu'
also being specified, the code is tuned to perform well across a
range of target processors implementing the target architecture.
-'-mtune=NAME'
+`-mtune=NAME'
Specify the name of the target processor for which GCC should tune
the performance of the code. Permissible values for this option
- are: 'generic', 'cortex-a53', 'cortex-a57', 'cortex-a72',
- 'exynos-m1', 'thunderx', 'xgene1'.
+ are: `generic', `cortex-a53', `cortex-a57', `cortex-a72',
+ `exynos-m1', `thunderx', `xgene1'.
Additionally, this option can specify that GCC should tune the
performance of the code for a big.LITTLE system. Permissible
- values for this option are: 'cortex-a57.cortex-a53',
- 'cortex-a72.cortex-a53'.
+ values for this option are: `cortex-a57.cortex-a53',
+ `cortex-a72.cortex-a53'.
- Where none of '-mtune=', '-mcpu=' or '-march=' are specified, the
+ Where none of `-mtune=', `-mcpu=' or `-march=' are specified, the
code is tuned to perform well across a range of target processors.
This option cannot be suffixed by feature modifiers.
-'-mcpu=NAME'
+`-mcpu=NAME'
Specify the name of the target processor, optionally suffixed by
one or more feature modifiers. This option has the form
- '-mcpu=CPU{+[no]FEATURE}*', where the permissible values for CPU
- are the same as those available for '-mtune'.
+ `-mcpu=CPU{+[no]FEATURE}*', where the permissible values for CPU
+ are the same as those available for `-mtune'.
The permissible values for FEATURE are documented in the
sub-section below.
@@ -11969,28 +12054,31 @@ These options are defined for AArch64 implementations:
feature is used.
GCC uses this name to determine what kind of instructions it can
- emit when generating assembly code (as if by '-march') and to
+ emit when generating assembly code (as if by `-march') and to
determine the target processor for which to tune for performance
- (as if by '-mtune'). Where this option is used in conjunction with
- '-march' or '-mtune', those options take precedence over the
+ (as if by `-mtune'). Where this option is used in conjunction
+ with `-march' or `-mtune', those options take precedence over the
appropriate part of this option.
-3.17.1.1 '-march' and '-mcpu' Feature Modifiers
+3.17.1.1 `-march' and `-mcpu' Feature Modifiers
...............................................
-Feature modifiers used with '-march' and '-mcpu' can be one the
+Feature modifiers used with `-march' and `-mcpu' can be one the
following:
-'crc'
+`crc'
Enable CRC extension.
-'crypto'
+
+`crypto'
Enable Crypto extension. This implies Advanced SIMD is enabled.
-'fp'
+
+`fp'
Enable floating-point instructions.
-'simd'
+
+`simd'
Enable Advanced SIMD instructions. This implies floating-point
instructions are enabled. This is the default for all current
- possible values for options '-march' and '-mcpu='.
+ possible values for options `-march' and `-mcpu='.

File: gcc.info, Node: Adapteva Epiphany Options, Next: ARC Options, Prev: AArch64 Options, Up: Submodel Options
@@ -11998,41 +12086,41 @@ File: gcc.info, Node: Adapteva Epiphany Options, Next: ARC Options, Prev: AAr
3.17.2 Adapteva Epiphany Options
--------------------------------
-These '-m' options are defined for Adapteva Epiphany:
+These `-m' options are defined for Adapteva Epiphany:
-'-mhalf-reg-file'
- Don't allocate any register in the range 'r32'...'r63'. That
+`-mhalf-reg-file'
+ Don't allocate any register in the range `r32'...`r63'. That
allows code to run on hardware variants that lack these registers.
-'-mprefer-short-insn-regs'
+`-mprefer-short-insn-regs'
Preferrentially allocate registers that allow short instruction
generation. This can result in increased instruction count, so
this may either reduce or increase overall code size.
-'-mbranch-cost=NUM'
+`-mbranch-cost=NUM'
Set the cost of branches to roughly NUM "simple" instructions.
This cost is only a heuristic and is not guaranteed to produce
consistent results across releases.
-'-mcmove'
+`-mcmove'
Enable the generation of conditional moves.
-'-mnops=NUM'
+`-mnops=NUM'
Emit NUM NOPs before every other generated instruction.
-'-mno-soft-cmpsf'
- For single-precision floating-point comparisons, emit an 'fsub'
+`-mno-soft-cmpsf'
+ For single-precision floating-point comparisons, emit an `fsub'
instruction and test the flags. This is faster than a software
comparison, but can get incorrect results in the presence of NaNs,
or when two different small numbers are compared such that their
- difference is calculated as zero. The default is '-msoft-cmpsf',
+ difference is calculated as zero. The default is `-msoft-cmpsf',
which uses slower, but IEEE-compliant, software comparisons.
-'-mstack-offset=NUM'
+`-mstack-offset=NUM'
Set the offset between the top of the stack and the stack pointer.
E.g., a value of 8 means that the eight bytes in the range
- 'sp+0...sp+7' can be used by leaf functions without stack
- allocation. Values other than '8' or '16' are untested and
+ `sp+0...sp+7' can be used by leaf functions without stack
+ allocation. Values other than `8' or `16' are untested and
unlikely to work. Note also that this option changes the ABI;
compiling a program with a different stack offset than the
libraries have been compiled with generally does not work. This
@@ -12040,94 +12128,96 @@ These '-m' options are defined for Adapteva Epiphany:
offset would give you better code, but to actually use a different
stack offset to build working programs, it is recommended to
configure the toolchain with the appropriate
- '--with-stack-offset=NUM' option.
+ `--with-stack-offset=NUM' option.
-'-mno-round-nearest'
+`-mno-round-nearest'
Make the scheduler assume that the rounding mode has been set to
- truncating. The default is '-mround-nearest'.
+ truncating. The default is `-mround-nearest'.
-'-mlong-calls'
+`-mlong-calls'
If not otherwise specified by an attribute, assume all calls might
- be beyond the offset range of the 'b' / 'bl' instructions, and
+ be beyond the offset range of the `b' / `bl' instructions, and
therefore load the function address into a register before
performing a (otherwise direct) call. This is the default.
-'-mshort-calls'
- If not otherwise specified by an attribute, assume all direct calls
- are in the range of the 'b' / 'bl' instructions, so use these
- instructions for direct calls. The default is '-mlong-calls'.
+`-mshort-calls'
+ If not otherwise specified by an attribute, assume all direct
+ calls are in the range of the `b' / `bl' instructions, so use
+ these instructions for direct calls. The default is
+ `-mlong-calls'.
-'-msmall16'
+`-msmall16'
Assume addresses can be loaded as 16-bit unsigned values. This
- does not apply to function addresses for which '-mlong-calls'
+ does not apply to function addresses for which `-mlong-calls'
semantics are in effect.
-'-mfp-mode=MODE'
+`-mfp-mode=MODE'
Set the prevailing mode of the floating-point unit. This
- determines the floating-point mode that is provided and expected at
- function call and return time. Making this mode match the mode you
- predominantly need at function start can make your programs smaller
- and faster by avoiding unnecessary mode switches.
+ determines the floating-point mode that is provided and expected
+ at function call and return time. Making this mode match the mode
+ you predominantly need at function start can make your programs
+ smaller and faster by avoiding unnecessary mode switches.
MODE can be set to one the following values:
- 'caller'
+ `caller'
Any mode at function entry is valid, and retained or restored
when the function returns, and when it calls other functions.
This mode is useful for compiling libraries or other
- compilation units you might want to incorporate into different
- programs with different prevailing FPU modes, and the
- convenience of being able to use a single object file
+ compilation units you might want to incorporate into
+ different programs with different prevailing FPU modes, and
+ the convenience of being able to use a single object file
outweighs the size and speed overhead for any extra mode
switching that might be needed, compared with what would be
needed with a more specific choice of prevailing FPU mode.
- 'truncate'
+ `truncate'
This is the mode used for floating-point calculations with
truncating (i.e. round towards zero) rounding mode. That
includes conversion from floating point to integer.
- 'round-nearest'
+ `round-nearest'
This is the mode used for floating-point calculations with
round-to-nearest-or-even rounding mode.
- 'int'
+ `int'
This is the mode used to perform integer calculations in the
- FPU, e.g. integer multiply, or integer
+ FPU, e.g. integer multiply, or integer
multiply-and-accumulate.
- The default is '-mfp-mode=caller'
+ The default is `-mfp-mode=caller'
-'-mnosplit-lohi'
-'-mno-postinc'
-'-mno-postmodify'
+`-mnosplit-lohi'
+`-mno-postinc'
+`-mno-postmodify'
Code generation tweaks that disable, respectively, splitting of
32-bit loads, generation of post-increment addresses, and
generation of post-modify addresses. The defaults are
- 'msplit-lohi', '-mpost-inc', and '-mpost-modify'.
+ `msplit-lohi', `-mpost-inc', and `-mpost-modify'.
-'-mnovect-double'
+`-mnovect-double'
Change the preferred SIMD mode to SImode. The default is
- '-mvect-double', which uses DImode as preferred SIMD mode.
+ `-mvect-double', which uses DImode as preferred SIMD mode.
-'-max-vect-align=NUM'
+`-max-vect-align=NUM'
The maximum alignment for SIMD vector mode types. NUM may be 4 or
- 8. The default is 8. Note that this is an ABI change, even though
- many library function interfaces are unaffected if they don't use
- SIMD vector modes in places that affect size and/or alignment of
- relevant types.
+ 8. The default is 8. Note that this is an ABI change, even
+ though many library function interfaces are unaffected if they
+ don't use SIMD vector modes in places that affect size and/or
+ alignment of relevant types.
-'-msplit-vecmove-early'
- Split vector moves into single word moves before reload. In theory
- this can give better register allocation, but so far the reverse
- seems to be generally the case.
+`-msplit-vecmove-early'
+ Split vector moves into single word moves before reload. In
+ theory this can give better register allocation, but so far the
+ reverse seems to be generally the case.
-'-m1reg-REG'
+`-m1reg-REG'
Specify a register to hold the constant -1, which makes loading
small negative constants and certain bitmasks faster. Allowable
- values for REG are 'r43' and 'r63', which specify use of that
- register as a fixed register, and 'none', which means that no
- register is used for this purpose. The default is '-m1reg-none'.
+ values for REG are `r43' and `r63', which specify use of that
+ register as a fixed register, and `none', which means that no
+ register is used for this purpose. The default is `-m1reg-none'.
+

File: gcc.info, Node: ARC Options, Next: ARM Options, Prev: Adapteva Epiphany Options, Up: Submodel Options
@@ -12135,253 +12225,258 @@ File: gcc.info, Node: ARC Options, Next: ARM Options, Prev: Adapteva Epiphany
3.17.3 ARC Options
------------------
-The following options control the architecture variant for which code is
-being compiled:
+The following options control the architecture variant for which code
+is being compiled:
-'-mbarrel-shifter'
+`-mbarrel-shifter'
Generate instructions supported by barrel shifter. This is the
- default unless '-mcpu=ARC601' is in effect.
+ default unless `-mcpu=ARC601' is in effect.
-'-mcpu=CPU'
+`-mcpu=CPU'
Set architecture type, register usage, and instruction scheduling
parameters for CPU. There are also shortcut alias options
available for backward compatibility and convenience. Supported
values for CPU are
- 'ARC600'
- Compile for ARC600. Aliases: '-mA6', '-mARC600'.
+ `ARC600'
+ Compile for ARC600. Aliases: `-mA6', `-mARC600'.
- 'ARC601'
- Compile for ARC601. Alias: '-mARC601'.
+ `ARC601'
+ Compile for ARC601. Alias: `-mARC601'.
- 'ARC700'
- Compile for ARC700. Aliases: '-mA7', '-mARC700'. This is the
- default when configured with '--with-cpu=arc700'.
+ `ARC700'
+ Compile for ARC700. Aliases: `-mA7', `-mARC700'. This is
+ the default when configured with `--with-cpu=arc700'.
-'-mdpfp'
-'-mdpfp-compact'
+`-mdpfp'
+`-mdpfp-compact'
FPX: Generate Double Precision FPX instructions, tuned for the
compact implementation.
-'-mdpfp-fast'
+`-mdpfp-fast'
FPX: Generate Double Precision FPX instructions, tuned for the fast
implementation.
-'-mno-dpfp-lrsr'
+`-mno-dpfp-lrsr'
Disable LR and SR instructions from using FPX extension aux
registers.
-'-mea'
- Generate Extended arithmetic instructions. Currently only 'divaw',
- 'adds', 'subs', and 'sat16' are supported. This is always enabled
- for '-mcpu=ARC700'.
+`-mea'
+ Generate Extended arithmetic instructions. Currently only
+ `divaw', `adds', `subs', and `sat16' are supported. This is
+ always enabled for `-mcpu=ARC700'.
-'-mno-mpy'
+`-mno-mpy'
Do not generate mpy instructions for ARC700.
-'-mmul32x16'
+`-mmul32x16'
Generate 32x16 bit multiply and mac instructions.
-'-mmul64'
+`-mmul64'
Generate mul64 and mulu64 instructions. Only valid for
- '-mcpu=ARC600'.
+ `-mcpu=ARC600'.
-'-mnorm'
- Generate norm instruction. This is the default if '-mcpu=ARC700'
+`-mnorm'
+ Generate norm instruction. This is the default if `-mcpu=ARC700'
is in effect.
-'-mspfp'
-'-mspfp-compact'
+`-mspfp'
+`-mspfp-compact'
FPX: Generate Single Precision FPX instructions, tuned for the
compact implementation.
-'-mspfp-fast'
+`-mspfp-fast'
FPX: Generate Single Precision FPX instructions, tuned for the fast
implementation.
-'-msimd'
+`-msimd'
Enable generation of ARC SIMD instructions via target-specific
- builtins. Only valid for '-mcpu=ARC700'.
+ builtins. Only valid for `-mcpu=ARC700'.
-'-msoft-float'
+`-msoft-float'
This option ignored; it is provided for compatibility purposes
- only. Software floating point code is emitted by default, and this
- default can overridden by FPX options; 'mspfp', 'mspfp-compact', or
- 'mspfp-fast' for single precision, and 'mdpfp', 'mdpfp-compact', or
- 'mdpfp-fast' for double precision.
+ only. Software floating point code is emitted by default, and
+ this default can overridden by FPX options; `mspfp',
+ `mspfp-compact', or `mspfp-fast' for single precision, and `mdpfp',
+ `mdpfp-compact', or `mdpfp-fast' for double precision.
-'-mswap'
+`-mswap'
Generate swap instructions.
+
The following options are passed through to the assembler, and also
define preprocessor macro symbols.
-'-mdsp-packa'
+`-mdsp-packa'
Passed down to the assembler to enable the DSP Pack A extensions.
- Also sets the preprocessor symbol '__Xdsp_packa'.
+ Also sets the preprocessor symbol `__Xdsp_packa'.
-'-mdvbf'
+`-mdvbf'
Passed down to the assembler to enable the dual viterbi butterfly
- extension. Also sets the preprocessor symbol '__Xdvbf'.
+ extension. Also sets the preprocessor symbol `__Xdvbf'.
-'-mlock'
+`-mlock'
Passed down to the assembler to enable the Locked Load/Store
Conditional extension. Also sets the preprocessor symbol
- '__Xlock'.
+ `__Xlock'.
-'-mmac-d16'
+`-mmac-d16'
Passed down to the assembler. Also sets the preprocessor symbol
- '__Xxmac_d16'.
+ `__Xxmac_d16'.
-'-mmac-24'
+`-mmac-24'
Passed down to the assembler. Also sets the preprocessor symbol
- '__Xxmac_24'.
+ `__Xxmac_24'.
-'-mrtsc'
+`-mrtsc'
Passed down to the assembler to enable the 64-bit Time-Stamp
Counter extension instruction. Also sets the preprocessor symbol
- '__Xrtsc'.
+ `__Xrtsc'.
-'-mswape'
+`-mswape'
Passed down to the assembler to enable the swap byte ordering
extension instruction. Also sets the preprocessor symbol
- '__Xswape'.
+ `__Xswape'.
-'-mtelephony'
+`-mtelephony'
Passed down to the assembler to enable dual and single operand
instructions for telephony. Also sets the preprocessor symbol
- '__Xtelephony'.
+ `__Xtelephony'.
-'-mxy'
+`-mxy'
Passed down to the assembler to enable the XY Memory extension.
- Also sets the preprocessor symbol '__Xxy'.
+ Also sets the preprocessor symbol `__Xxy'.
+
The following options control how the assembly code is annotated:
-'-misize'
+`-misize'
Annotate assembler instructions with estimated addresses.
-'-mannotate-align'
+`-mannotate-align'
Explain what alignment considerations lead to the decision to make
an instruction short or long.
+
The following options are passed through to the linker:
-'-marclinux'
- Passed through to the linker, to specify use of the 'arclinux'
+`-marclinux'
+ Passed through to the linker, to specify use of the `arclinux'
emulation. This option is enabled by default in tool chains built
- for 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets when
+ for `arc-linux-uclibc' and `arceb-linux-uclibc' targets when
profiling is not requested.
-'-marclinux_prof'
- Passed through to the linker, to specify use of the 'arclinux_prof'
- emulation. This option is enabled by default in tool chains built
- for 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets when
- profiling is requested.
+`-marclinux_prof'
+ Passed through to the linker, to specify use of the
+ `arclinux_prof' emulation. This option is enabled by default in
+ tool chains built for `arc-linux-uclibc' and `arceb-linux-uclibc'
+ targets when profiling is requested.
+
The following options control the semantics of generated code:
-'-mepilogue-cfi'
+`-mepilogue-cfi'
Enable generation of call frame information for epilogues.
-'-mno-epilogue-cfi'
+`-mno-epilogue-cfi'
Disable generation of call frame information for epilogues.
-'-mlong-calls'
+`-mlong-calls'
Generate call insns as register indirect calls, thus providing
access to the full 32-bit address range.
-'-mmedium-calls'
+`-mmedium-calls'
Don't use less than 25 bit addressing range for calls, which is the
offset available for an unconditional branch-and-link instruction.
- Conditional execution of function calls is suppressed, to allow use
- of the 25-bit range, rather than the 21-bit range with conditional
- branch-and-link. This is the default for tool chains built for 'arc-linux-uclibc'
- and 'arceb-linux-uclibc' targets.
+ Conditional execution of function calls is suppressed, to allow
+ use of the 25-bit range, rather than the 21-bit range with
+ conditional branch-and-link. This is the default for tool chains
+ built for `arc-linux-uclibc' and `arceb-linux-uclibc' targets.
-'-mno-sdata'
+`-mno-sdata'
Do not generate sdata references. This is the default for tool
- chains built for 'arc-linux-uclibc' and 'arceb-linux-uclibc'
+ chains built for `arc-linux-uclibc' and `arceb-linux-uclibc'
targets.
-'-mucb-mcount'
- Instrument with mcount calls as used in UCB code. I.e. do the
+`-mucb-mcount'
+ Instrument with mcount calls as used in UCB code. I.e. do the
counting in the callee, not the caller. By default ARC
instrumentation counts in the caller.
-'-mvolatile-cache'
+`-mvolatile-cache'
Use ordinarily cached memory accesses for volatile references.
This is the default.
-'-mno-volatile-cache'
+`-mno-volatile-cache'
Enable cache bypass for volatile references.
+
The following options fine tune code generation:
-'-malign-call'
+`-malign-call'
Do alignment optimizations for call instructions.
-'-mauto-modify-reg'
+`-mauto-modify-reg'
Enable the use of pre/post modify with register displacement.
-'-mbbit-peephole'
+`-mbbit-peephole'
Enable bbit peephole2.
-'-mno-brcc'
- This option disables a target-specific pass in 'arc_reorg' to
- generate 'BRcc' instructions. It has no effect on 'BRcc'
+`-mno-brcc'
+ This option disables a target-specific pass in `arc_reorg' to
+ generate `BRcc' instructions. It has no effect on `BRcc'
generation driven by the combiner pass.
-'-mcase-vector-pcrel'
+`-mcase-vector-pcrel'
Use pc-relative switch case tables - this enables case table
- shortening. This is the default for '-Os'.
+ shortening. This is the default for `-Os'.
-'-mcompact-casesi'
- Enable compact casesi pattern. This is the default for '-Os'.
+`-mcompact-casesi'
+ Enable compact casesi pattern. This is the default for `-Os'.
-'-mno-cond-exec'
+`-mno-cond-exec'
Disable ARCompact specific pass to generate conditional execution
instructions. Due to delay slot scheduling and interactions
between operand numbers, literal sizes, instruction lengths, and
the support for conditional execution, the target-independent pass
- to generate conditional execution is often lacking, so the ARC port
- has kept a special pass around that tries to find more conditional
- execution generating opportunities after register allocation,
- branch shortening, and delay slot scheduling have been done. This
- pass generally, but not always, improves performance and code size,
- at the cost of extra compilation time, which is why there is an
- option to switch it off. If you have a problem with call
- instructions exceeding their allowable offset range because they
- are conditionalized, you should consider using '-mmedium-calls'
- instead.
-
-'-mearly-cbranchsi'
+ to generate conditional execution is often lacking, so the ARC
+ port has kept a special pass around that tries to find more
+ conditional execution generating opportunities after register
+ allocation, branch shortening, and delay slot scheduling have been
+ done. This pass generally, but not always, improves performance
+ and code size, at the cost of extra compilation time, which is why
+ there is an option to switch it off. If you have a problem with
+ call instructions exceeding their allowable offset range because
+ they are conditionalized, you should consider using
+ `-mmedium-calls' instead.
+
+`-mearly-cbranchsi'
Enable pre-reload use of the cbranchsi pattern.
-'-mexpand-adddi'
- Expand 'adddi3' and 'subdi3' at rtl generation time into 'add.f',
- 'adc' etc.
+`-mexpand-adddi'
+ Expand `adddi3' and `subdi3' at rtl generation time into `add.f',
+ `adc' etc.
-'-mindexed-loads'
+`-mindexed-loads'
Enable the use of indexed loads. This can be problematic because
some optimizers then assume that indexed stores exist, which is not
the case.
-'-mlra'
+`-mlra'
Enable Local Register Allocation. This is still experimental for
ARC, so by default the compiler uses standard reload (i.e.
- '-mno-lra').
+ `-mno-lra').
-'-mlra-priority-none'
+`-mlra-priority-none'
Don't indicate any priority for target registers.
-'-mlra-priority-compact'
+`-mlra-priority-compact'
Indicate target register priority for r0..r3 / r12..r15.
-'-mlra-priority-noncompact'
+`-mlra-priority-noncompact'
Reduce target regsiter priority for r0..r3 / r12..r15.
-'-mno-millicode'
- When optimizing for size (using '-Os'), prologues and epilogues
+`-mno-millicode'
+ When optimizing for size (using `-Os'), prologues and epilogues
that have to save or restore a large number of registers are often
shortened by using call to a special function in libgcc; this is
referred to as a _millicode_ call. As these calls can pose
@@ -12389,134 +12484,138 @@ define preprocessor macro symbols.
nonstandard way, this option is provided to turn off millicode call
generation.
-'-mmixed-code'
+`-mmixed-code'
Tweak register allocation to help 16-bit instruction generation.
- This generally has the effect of decreasing the average instruction
- size while increasing the instruction count.
+ This generally has the effect of decreasing the average
+ instruction size while increasing the instruction count.
-'-mq-class'
+`-mq-class'
Enable 'q' instruction alternatives. This is the default for
- '-Os'.
+ `-Os'.
-'-mRcq'
- Enable Rcq constraint handling - most short code generation depends
- on this. This is the default.
+`-mRcq'
+ Enable Rcq constraint handling - most short code generation
+ depends on this. This is the default.
-'-mRcw'
+`-mRcw'
Enable Rcw constraint handling - ccfsm condexec mostly depends on
this. This is the default.
-'-msize-level=LEVEL'
- Fine-tune size optimization with regards to instruction lengths and
- alignment. The recognized values for LEVEL are:
- '0'
+`-msize-level=LEVEL'
+ Fine-tune size optimization with regards to instruction lengths
+ and alignment. The recognized values for LEVEL are:
+ `0'
No size optimization. This level is deprecated and treated
- like '1'.
+ like `1'.
- '1'
+ `1'
Short instructions are used opportunistically.
- '2'
- In addition, alignment of loops and of code after barriers are
- dropped.
+ `2'
+ In addition, alignment of loops and of code after barriers
+ are dropped.
- '3'
+ `3'
In addition, optional data alignment is dropped, and the
- option 'Os' is enabled.
+ option `Os' is enabled.
+
- This defaults to '3' when '-Os' is in effect. Otherwise, the
- behavior when this is not set is equivalent to level '1'.
+ This defaults to `3' when `-Os' is in effect. Otherwise, the
+ behavior when this is not set is equivalent to level `1'.
-'-mtune=CPU'
+`-mtune=CPU'
Set instruction scheduling parameters for CPU, overriding any
- implied by '-mcpu='.
+ implied by `-mcpu='.
Supported values for CPU are
- 'ARC600'
+ `ARC600'
Tune for ARC600 cpu.
- 'ARC601'
+ `ARC601'
Tune for ARC601 cpu.
- 'ARC700'
+ `ARC700'
Tune for ARC700 cpu with standard multiplier block.
- 'ARC700-xmac'
+ `ARC700-xmac'
Tune for ARC700 cpu with XMAC block.
- 'ARC725D'
+ `ARC725D'
Tune for ARC725D cpu.
- 'ARC750D'
+ `ARC750D'
Tune for ARC750D cpu.
-'-mmultcost=NUM'
- Cost to assume for a multiply instruction, with '4' being equal to
+
+`-mmultcost=NUM'
+ Cost to assume for a multiply instruction, with `4' being equal to
a normal instruction.
-'-munalign-prob-threshold=PROBABILITY'
- Set probability threshold for unaligning branches. When tuning for
- 'ARC700' and optimizing for speed, branches without filled delay
- slot are preferably emitted unaligned and long, unless profiling
- indicates that the probability for the branch to be taken is below
- PROBABILITY. *Note Cross-profiling::. The default is
+`-munalign-prob-threshold=PROBABILITY'
+ Set probability threshold for unaligning branches. When tuning
+ for `ARC700' and optimizing for speed, branches without filled
+ delay slot are preferably emitted unaligned and long, unless
+ profiling indicates that the probability for the branch to be taken
+ is below PROBABILITY. *Note Cross-profiling::. The default is
(REG_BR_PROB_BASE/2), i.e. 5000.
+
The following options are maintained for backward compatibility, but
are now deprecated and will be removed in a future release:
-'-margonaut'
+`-margonaut'
Obsolete FPX.
-'-mbig-endian'
-'-EB'
+`-mbig-endian'
+`-EB'
Compile code for big endian targets. Use of these options is now
- deprecated. Users wanting big-endian code, should use the 'arceb-elf32'
- and 'arceb-linux-uclibc' targets when building the tool chain, for
- which big-endian is the default.
+ deprecated. Users wanting big-endian code, should use the
+ `arceb-elf32' and `arceb-linux-uclibc' targets when building the
+ tool chain, for which big-endian is the default.
-'-mlittle-endian'
-'-EL'
+`-mlittle-endian'
+`-EL'
Compile code for little endian targets. Use of these options is
- now deprecated. Users wanting little-endian code should use the 'arc-elf32'
- and 'arc-linux-uclibc' targets when building the tool chain, for
- which little-endian is the default.
+ now deprecated. Users wanting little-endian code should use the
+ `arc-elf32' and `arc-linux-uclibc' targets when building the tool
+ chain, for which little-endian is the default.
-'-mbarrel_shifter'
- Replaced by '-mbarrel-shifter'.
+`-mbarrel_shifter'
+ Replaced by `-mbarrel-shifter'.
-'-mdpfp_compact'
- Replaced by '-mdpfp-compact'.
+`-mdpfp_compact'
+ Replaced by `-mdpfp-compact'.
-'-mdpfp_fast'
- Replaced by '-mdpfp-fast'.
+`-mdpfp_fast'
+ Replaced by `-mdpfp-fast'.
-'-mdsp_packa'
- Replaced by '-mdsp-packa'.
+`-mdsp_packa'
+ Replaced by `-mdsp-packa'.
-'-mEA'
- Replaced by '-mea'.
+`-mEA'
+ Replaced by `-mea'.
-'-mmac_24'
- Replaced by '-mmac-24'.
+`-mmac_24'
+ Replaced by `-mmac-24'.
-'-mmac_d16'
- Replaced by '-mmac-d16'.
+`-mmac_d16'
+ Replaced by `-mmac-d16'.
-'-mspfp_compact'
- Replaced by '-mspfp-compact'.
+`-mspfp_compact'
+ Replaced by `-mspfp-compact'.
-'-mspfp_fast'
- Replaced by '-mspfp-fast'.
+`-mspfp_fast'
+ Replaced by `-mspfp-fast'.
-'-mtune=CPU'
- Values 'arc600', 'arc601', 'arc700' and 'arc700-xmac' for CPU are
- replaced by 'ARC600', 'ARC601', 'ARC700' and 'ARC700-xmac'
+`-mtune=CPU'
+ Values `arc600', `arc601', `arc700' and `arc700-xmac' for CPU are
+ replaced by `ARC600', `ARC601', `ARC700' and `ARC700-xmac'
respectively
-'-multcost=NUM'
- Replaced by '-mmultcost'.
+`-multcost=NUM'
+ Replaced by `-mmultcost'.
+

File: gcc.info, Node: ARM Options, Next: AVR Options, Prev: ARC Options, Up: Submodel Options
@@ -12524,48 +12623,48 @@ File: gcc.info, Node: ARM Options, Next: AVR Options, Prev: ARC Options, Up:
3.17.4 ARM Options
------------------
-These '-m' options are defined for the ARM port:
+These `-m' options are defined for the ARM port:
-'-mabi=NAME'
+`-mabi=NAME'
Generate code for the specified ABI. Permissible values are:
- 'apcs-gnu', 'atpcs', 'aapcs', 'aapcs-linux' and 'iwmmxt'.
+ `apcs-gnu', `atpcs', `aapcs', `aapcs-linux' and `iwmmxt'.
-'-mapcs-frame'
+`-mapcs-frame'
Generate a stack frame that is compliant with the ARM Procedure
Call Standard for all functions, even if this is not strictly
necessary for correct execution of the code. Specifying
- '-fomit-frame-pointer' with this option causes the stack frames not
- to be generated for leaf functions. The default is
- '-mno-apcs-frame'. This option is deprecated.
+ `-fomit-frame-pointer' with this option causes the stack frames
+ not to be generated for leaf functions. The default is
+ `-mno-apcs-frame'. This option is deprecated.
-'-mapcs'
- This is a synonym for '-mapcs-frame' and is deprecated.
+`-mapcs'
+ This is a synonym for `-mapcs-frame' and is deprecated.
-'-mthumb-interwork'
+`-mthumb-interwork'
Generate code that supports calling between the ARM and Thumb
instruction sets. Without this option, on pre-v5 architectures,
the two instruction sets cannot be reliably used inside one
- program. The default is '-mno-thumb-interwork', since slightly
- larger code is generated when '-mthumb-interwork' is specified. In
- AAPCS configurations this option is meaningless.
+ program. The default is `-mno-thumb-interwork', since slightly
+ larger code is generated when `-mthumb-interwork' is specified.
+ In AAPCS configurations this option is meaningless.
-'-mno-sched-prolog'
- Prevent the reordering of instructions in the function prologue, or
- the merging of those instruction with the instructions in the
+`-mno-sched-prolog'
+ Prevent the reordering of instructions in the function prologue,
+ or the merging of those instruction with the instructions in the
function's body. This means that all functions start with a
- recognizable set of instructions (or in fact one of a choice from a
- small set of different function prologues), and this information
+ recognizable set of instructions (or in fact one of a choice from
+ a small set of different function prologues), and this information
can be used to locate the start of functions inside an executable
- piece of code. The default is '-msched-prolog'.
+ piece of code. The default is `-msched-prolog'.
-'-mfloat-abi=NAME'
- Specifies which floating-point ABI to use. Permissible values are:
- 'soft', 'softfp' and 'hard'.
+`-mfloat-abi=NAME'
+ Specifies which floating-point ABI to use. Permissible values
+ are: `soft', `softfp' and `hard'.
- Specifying 'soft' causes GCC to generate output containing library
- calls for floating-point operations. 'softfp' allows the
+ Specifying `soft' causes GCC to generate output containing library
+ calls for floating-point operations. `softfp' allows the
generation of code using hardware floating-point instructions, but
- still uses the soft-float calling conventions. 'hard' allows
+ still uses the soft-float calling conventions. `hard' allows
generation of floating-point instructions and uses FPU-specific
calling conventions.
@@ -12574,188 +12673,189 @@ These '-m' options are defined for the ARM port:
you must compile your entire program with the same ABI, and link
with a compatible set of libraries.
-'-mlittle-endian'
+`-mlittle-endian'
Generate code for a processor running in little-endian mode. This
is the default for all standard configurations.
-'-mbig-endian'
+`-mbig-endian'
Generate code for a processor running in big-endian mode; the
default is to compile code for a little-endian processor.
-'-march=NAME'
+`-march=NAME'
This specifies the name of the target ARM architecture. GCC uses
this name to determine what kind of instructions it can emit when
generating assembly code. This option can be used in conjunction
- with or instead of the '-mcpu=' option. Permissible names are:
- 'armv2', 'armv2a', 'armv3', 'armv3m', 'armv4', 'armv4t', 'armv5',
- 'armv5t', 'armv5e', 'armv5te', 'armv6', 'armv6j', 'armv6t2',
- 'armv6z', 'armv6zk', 'armv6-m', 'armv7', 'armv7-a', 'armv7-r',
- 'armv7-m', 'armv7e-m', 'armv7ve', 'armv8-a', 'armv8-a+crc',
- 'iwmmxt', 'iwmmxt2', 'ep9312'.
-
- '-march=armv7ve' is the armv7-a architecture with virtualization
+ with or instead of the `-mcpu=' option. Permissible names are:
+ `armv2', `armv2a', `armv3', `armv3m', `armv4', `armv4t', `armv5',
+ `armv5t', `armv5e', `armv5te', `armv6', `armv6j', `armv6t2',
+ `armv6z', `armv6zk', `armv6-m', `armv7', `armv7-a', `armv7-r',
+ `armv7-m', `armv7e-m', `armv7ve', `armv8-a', `armv8-a+crc',
+ `iwmmxt', `iwmmxt2', `ep9312'.
+
+ `-march=armv7ve' is the armv7-a architecture with virtualization
extensions.
- '-march=armv8-a+crc' enables code generation for the ARMv8-A
+ `-march=armv8-a+crc' enables code generation for the ARMv8-A
architecture together with the optional CRC32 extensions.
- '-march=native' causes the compiler to auto-detect the architecture
+ `-march=native' causes the compiler to auto-detect the architecture
of the build computer. At present, this feature is only supported
on GNU/Linux, and not all architectures are recognized. If the
auto-detect is unsuccessful the option has no effect.
-'-mtune=NAME'
+`-mtune=NAME'
This option specifies the name of the target ARM processor for
which GCC should tune the performance of the code. For some ARM
implementations better performance can be obtained by using this
- option. Permissible names are: 'arm2', 'arm250', 'arm3', 'arm6',
- 'arm60', 'arm600', 'arm610', 'arm620', 'arm7', 'arm7m', 'arm7d',
- 'arm7dm', 'arm7di', 'arm7dmi', 'arm70', 'arm700', 'arm700i',
- 'arm710', 'arm710c', 'arm7100', 'arm720', 'arm7500', 'arm7500fe',
- 'arm7tdmi', 'arm7tdmi-s', 'arm710t', 'arm720t', 'arm740t',
- 'strongarm', 'strongarm110', 'strongarm1100', 'strongarm1110',
- 'arm8', 'arm810', 'arm9', 'arm9e', 'arm920', 'arm920t', 'arm922t',
- 'arm946e-s', 'arm966e-s', 'arm968e-s', 'arm926ej-s', 'arm940t',
- 'arm9tdmi', 'arm10tdmi', 'arm1020t', 'arm1026ej-s', 'arm10e',
- 'arm1020e', 'arm1022e', 'arm1136j-s', 'arm1136jf-s', 'mpcore',
- 'mpcorenovfp', 'arm1156t2-s', 'arm1156t2f-s', 'arm1176jz-s',
- 'arm1176jzf-s', 'cortex-a5', 'cortex-a7', 'cortex-a8', 'cortex-a9',
- 'cortex-a12', 'cortex-a15', 'cortex-a53', 'cortex-a57',
- 'cortex-a72', 'cortex-r4', 'cortex-r4f', 'cortex-r5', 'cortex-r7',
- 'cortex-m7', 'cortex-m4', 'cortex-m3', 'cortex-m1', 'cortex-m0',
- 'cortex-m0plus', 'cortex-m1.small-multiply',
- 'cortex-m0.small-multiply', 'cortex-m0plus.small-multiply',
- 'exynos-m1', 'marvell-pj4', 'xscale', 'iwmmxt', 'iwmmxt2',
- 'ep9312', 'fa526', 'fa626', 'fa606te', 'fa626te', 'fmp626',
- 'fa726te', 'xgene1'.
+ option. Permissible names are: `arm2', `arm250', `arm3', `arm6',
+ `arm60', `arm600', `arm610', `arm620', `arm7', `arm7m', `arm7d',
+ `arm7dm', `arm7di', `arm7dmi', `arm70', `arm700', `arm700i',
+ `arm710', `arm710c', `arm7100', `arm720', `arm7500', `arm7500fe',
+ `arm7tdmi', `arm7tdmi-s', `arm710t', `arm720t', `arm740t',
+ `strongarm', `strongarm110', `strongarm1100', `strongarm1110',
+ `arm8', `arm810', `arm9', `arm9e', `arm920', `arm920t', `arm922t',
+ `arm946e-s', `arm966e-s', `arm968e-s', `arm926ej-s', `arm940t',
+ `arm9tdmi', `arm10tdmi', `arm1020t', `arm1026ej-s', `arm10e',
+ `arm1020e', `arm1022e', `arm1136j-s', `arm1136jf-s', `mpcore',
+ `mpcorenovfp', `arm1156t2-s', `arm1156t2f-s', `arm1176jz-s',
+ `arm1176jzf-s', `cortex-a5', `cortex-a7', `cortex-a8', `cortex-a9',
+ `cortex-a12', `cortex-a15', `cortex-a53', `cortex-a57',
+ `cortex-a72', `cortex-r4', `cortex-r4f', `cortex-r5', `cortex-r7',
+ `cortex-m7', `cortex-m4', `cortex-m3', `cortex-m1', `cortex-m0',
+ `cortex-m0plus', `cortex-m1.small-multiply',
+ `cortex-m0.small-multiply', `cortex-m0plus.small-multiply',
+ `exynos-m1', `marvell-pj4', `xscale', `iwmmxt', `iwmmxt2',
+ `ep9312', `fa526', `fa626', `fa606te', `fa626te', `fmp626',
+ `fa726te', `xgene1'.
Additionally, this option can specify that GCC should tune the
- performance of the code for a big.LITTLE system. Permissible names
- are: 'cortex-a15.cortex-a7', 'cortex-a57.cortex-a53',
- 'cortex-a72.cortex-a53'.
+ performance of the code for a big.LITTLE system. Permissible
+ names are: `cortex-a15.cortex-a7', `cortex-a57.cortex-a53',
+ `cortex-a72.cortex-a53'.
- '-mtune=generic-ARCH' specifies that GCC should tune the
+ `-mtune=generic-ARCH' specifies that GCC should tune the
performance for a blend of processors within architecture ARCH.
The aim is to generate code that run well on the current most
popular processors, balancing between optimizations that benefit
some CPUs in the range, and avoiding performance pitfalls of other
- CPUs. The effects of this option may change in future GCC versions
- as CPU models come and go.
+ CPUs. The effects of this option may change in future GCC
+ versions as CPU models come and go.
- '-mtune=native' causes the compiler to auto-detect the CPU of the
+ `-mtune=native' causes the compiler to auto-detect the CPU of the
build computer. At present, this feature is only supported on
GNU/Linux, and not all architectures are recognized. If the
auto-detect is unsuccessful the option has no effect.
-'-mcpu=NAME'
- This specifies the name of the target ARM processor. GCC uses this
- name to derive the name of the target ARM architecture (as if
- specified by '-march') and the ARM processor type for which to tune
- for performance (as if specified by '-mtune'). Where this option
- is used in conjunction with '-march' or '-mtune', those options
- take precedence over the appropriate part of this option.
+`-mcpu=NAME'
+ This specifies the name of the target ARM processor. GCC uses
+ this name to derive the name of the target ARM architecture (as if
+ specified by `-march') and the ARM processor type for which to
+ tune for performance (as if specified by `-mtune'). Where this
+ option is used in conjunction with `-march' or `-mtune', those
+ options take precedence over the appropriate part of this option.
Permissible names for this option are the same as those for
- '-mtune'.
+ `-mtune'.
- '-mcpu=generic-ARCH' is also permissible, and is equivalent to
- '-march=ARCH -mtune=generic-ARCH'. See '-mtune' for more
+ `-mcpu=generic-ARCH' is also permissible, and is equivalent to
+ `-march=ARCH -mtune=generic-ARCH'. See `-mtune' for more
information.
- '-mcpu=native' causes the compiler to auto-detect the CPU of the
+ `-mcpu=native' causes the compiler to auto-detect the CPU of the
build computer. At present, this feature is only supported on
GNU/Linux, and not all architectures are recognized. If the
auto-detect is unsuccessful the option has no effect.
-'-mfpu=NAME'
- This specifies what floating-point hardware (or hardware emulation)
- is available on the target. Permissible names are: 'vfp', 'vfpv3',
- 'vfpv3-fp16', 'vfpv3-d16', 'vfpv3-d16-fp16', 'vfpv3xd',
- 'vfpv3xd-fp16', 'neon', 'neon-fp16', 'vfpv4', 'vfpv4-d16',
- 'fpv4-sp-d16', 'neon-vfpv4', 'fpv5-d16', 'fpv5-sp-d16', 'fp-armv8',
- 'neon-fp-armv8', and 'crypto-neon-fp-armv8'.
+`-mfpu=NAME'
+ This specifies what floating-point hardware (or hardware
+ emulation) is available on the target. Permissible names are:
+ `vfp', `vfpv3', `vfpv3-fp16', `vfpv3-d16', `vfpv3-d16-fp16',
+ `vfpv3xd', `vfpv3xd-fp16', `neon', `neon-fp16', `vfpv4',
+ `vfpv4-d16', `fpv4-sp-d16', `neon-vfpv4', `fpv5-d16',
+ `fpv5-sp-d16', `fp-armv8', `neon-fp-armv8', and
+ `crypto-neon-fp-armv8'.
- If '-msoft-float' is specified this specifies the format of
+ If `-msoft-float' is specified this specifies the format of
floating-point values.
If the selected floating-point hardware includes the NEON extension
- (e.g. '-mfpu'='neon'), note that floating-point operations are not
+ (e.g. `-mfpu'=`neon'), note that floating-point operations are not
generated by GCC's auto-vectorization pass unless
- '-funsafe-math-optimizations' is also specified. This is because
+ `-funsafe-math-optimizations' is also specified. This is because
NEON hardware does not fully implement the IEEE 754 standard for
floating-point arithmetic (in particular denormal values are
treated as zero), so the use of NEON instructions may lead to a
loss of precision.
-'-mfp16-format=NAME'
- Specify the format of the '__fp16' half-precision floating-point
- type. Permissible names are 'none', 'ieee', and 'alternative'; the
- default is 'none', in which case the '__fp16' type is not defined.
- *Note Half-Precision::, for more information.
+`-mfp16-format=NAME'
+ Specify the format of the `__fp16' half-precision floating-point
+ type. Permissible names are `none', `ieee', and `alternative';
+ the default is `none', in which case the `__fp16' type is not
+ defined. *Note Half-Precision::, for more information.
-'-mstructure-size-boundary=N'
+`-mstructure-size-boundary=N'
The sizes of all structures and unions are rounded up to a multiple
of the number of bits set by this option. Permissible values are
8, 32 and 64. The default value varies for different toolchains.
- For the COFF targeted toolchain the default value is 8. A value of
- 64 is only allowed if the underlying ABI supports it.
-
- Specifying a larger number can produce faster, more efficient code,
- but can also increase the size of the program. Different values
- are potentially incompatible. Code compiled with one value cannot
- necessarily expect to work with code or libraries compiled with
- another value, if they exchange information using structures or
- unions.
-
-'-mabort-on-noreturn'
- Generate a call to the function 'abort' at the end of a 'noreturn'
+ For the COFF targeted toolchain the default value is 8. A value
+ of 64 is only allowed if the underlying ABI supports it.
+
+ Specifying a larger number can produce faster, more efficient
+ code, but can also increase the size of the program. Different
+ values are potentially incompatible. Code compiled with one value
+ cannot necessarily expect to work with code or libraries compiled
+ with another value, if they exchange information using structures
+ or unions.
+
+`-mabort-on-noreturn'
+ Generate a call to the function `abort' at the end of a `noreturn'
function. It is executed if the function tries to return.
-'-mlong-calls'
-'-mno-long-calls'
+`-mlong-calls'
+`-mno-long-calls'
Tells the compiler to perform function calls by first loading the
address of the function into a register and then performing a
subroutine call on this register. This switch is needed if the
- target function lies outside of the 64-megabyte addressing range of
- the offset-based version of subroutine call instruction.
+ target function lies outside of the 64-megabyte addressing range
+ of the offset-based version of subroutine call instruction.
Even if this switch is enabled, not all function calls are turned
into long calls. The heuristic is that static functions, functions
- that have the 'short_call' attribute, functions that are inside the
- scope of a '#pragma no_long_calls' directive, and functions whose
- definitions have already been compiled within the current
- compilation unit are not turned into long calls. The exceptions to
- this rule are that weak function definitions, functions with the
- 'long_call' attribute or the 'section' attribute, and functions
- that are within the scope of a '#pragma long_calls' directive are
- always turned into long calls.
+ that have the `short_call' attribute, functions that are inside
+ the scope of a `#pragma no_long_calls' directive, and functions
+ whose definitions have already been compiled within the current
+ compilation unit are not turned into long calls. The exceptions
+ to this rule are that weak function definitions, functions with
+ the `long_call' attribute or the `section' attribute, and
+ functions that are within the scope of a `#pragma long_calls'
+ directive are always turned into long calls.
This feature is not enabled by default. Specifying
- '-mno-long-calls' restores the default behavior, as does placing
- the function calls within the scope of a '#pragma long_calls_off'
+ `-mno-long-calls' restores the default behavior, as does placing
+ the function calls within the scope of a `#pragma long_calls_off'
directive. Note these switches have no effect on how the compiler
generates code to handle function calls via function pointers.
-'-msingle-pic-base'
+`-msingle-pic-base'
Treat the register used for PIC addressing as read-only, rather
than loading it in the prologue for each function. The runtime
system is responsible for initializing this register with an
appropriate value before execution begins.
-'-mpic-register=REG'
+`-mpic-register=REG'
Specify the register to be used for PIC addressing. For standard
PIC base case, the default is any suitable register determined by
- compiler. For single PIC base case, the default is 'R9' if target
+ compiler. For single PIC base case, the default is `R9' if target
is EABI based or stack-checking is enabled, otherwise the default
- is 'R10'.
+ is `R10'.
-'-mpic-data-is-text-relative'
- Assume that each data segments are relative to text segment at load
- time. Therefore, it permits addressing data using PC-relative
- operations. This option is on by default for targets other than
- VxWorks RTP.
+`-mpic-data-is-text-relative'
+ Assume that each data segments are relative to text segment at
+ load time. Therefore, it permits addressing data using
+ PC-relative operations. This option is on by default for targets
+ other than VxWorks RTP.
-'-mpoke-function-name'
+`-mpoke-function-name'
Write the name of each function into the text section, directly
preceding the function prologue. The generated code is similar to
this:
@@ -12771,79 +12871,78 @@ These '-m' options are defined for the ARM port:
sub fp, ip, #4
When performing a stack backtrace, code can inspect the value of
- 'pc' stored at 'fp + 0'. If the trace function then looks at
- location 'pc - 12' and the top 8 bits are set, then we know that
+ `pc' stored at `fp + 0'. If the trace function then looks at
+ location `pc - 12' and the top 8 bits are set, then we know that
there is a function name embedded immediately preceding this
- location and has length '((pc[-3]) & 0xff000000)'.
-
-'-mthumb'
-'-marm'
+ location and has length `((pc[-3]) & 0xff000000)'.
+`-mthumb'
+`-marm'
Select between generating code that executes in ARM and Thumb
states. The default for most configurations is to generate code
that executes in ARM state, but the default can be changed by
- configuring GCC with the '--with-mode='STATE configure option.
+ configuring GCC with the `--with-mode='STATE configure option.
-'-mtpcs-frame'
+`-mtpcs-frame'
Generate a stack frame that is compliant with the Thumb Procedure
Call Standard for all non-leaf functions. (A leaf function is one
that does not call any other functions.) The default is
- '-mno-tpcs-frame'.
+ `-mno-tpcs-frame'.
-'-mtpcs-leaf-frame'
+`-mtpcs-leaf-frame'
Generate a stack frame that is compliant with the Thumb Procedure
- Call Standard for all leaf functions. (A leaf function is one that
- does not call any other functions.) The default is
- '-mno-apcs-leaf-frame'.
+ Call Standard for all leaf functions. (A leaf function is one
+ that does not call any other functions.) The default is
+ `-mno-apcs-leaf-frame'.
-'-mcallee-super-interworking'
+`-mcallee-super-interworking'
Gives all externally visible functions in the file being compiled
an ARM instruction set header which switches to Thumb mode before
- executing the rest of the function. This allows these functions to
- be called from non-interworking code. This option is not valid in
- AAPCS configurations because interworking is enabled by default.
+ executing the rest of the function. This allows these functions
+ to be called from non-interworking code. This option is not valid
+ in AAPCS configurations because interworking is enabled by default.
-'-mcaller-super-interworking'
+`-mcaller-super-interworking'
Allows calls via function pointers (including virtual functions) to
execute correctly regardless of whether the target code has been
- compiled for interworking or not. There is a small overhead in the
- cost of executing a function pointer if this option is enabled.
- This option is not valid in AAPCS configurations because
+ compiled for interworking or not. There is a small overhead in
+ the cost of executing a function pointer if this option is
+ enabled. This option is not valid in AAPCS configurations because
interworking is enabled by default.
-'-mtp=NAME'
- Specify the access model for the thread local storage pointer. The
- valid models are 'soft', which generates calls to
- '__aeabi_read_tp', 'cp15', which fetches the thread pointer from
- 'cp15' directly (supported in the arm6k architecture), and 'auto',
+`-mtp=NAME'
+ Specify the access model for the thread local storage pointer.
+ The valid models are `soft', which generates calls to
+ `__aeabi_read_tp', `cp15', which fetches the thread pointer from
+ `cp15' directly (supported in the arm6k architecture), and `auto',
which uses the best available method for the selected processor.
- The default setting is 'auto'.
+ The default setting is `auto'.
-'-mtls-dialect=DIALECT'
+`-mtls-dialect=DIALECT'
Specify the dialect to use for accessing thread local storage. Two
- DIALECTs are supported--'gnu' and 'gnu2'. The 'gnu' dialect
+ DIALECTs are supported--`gnu' and `gnu2'. The `gnu' dialect
selects the original GNU scheme for supporting local and global
- dynamic TLS models. The 'gnu2' dialect selects the GNU descriptor
+ dynamic TLS models. The `gnu2' dialect selects the GNU descriptor
scheme, which provides better performance for shared libraries.
The GNU descriptor scheme is compatible with the original scheme,
but does require new assembler, linker and library support.
- Initial and local exec TLS models are unaffected by this option and
- always use the original scheme.
+ Initial and local exec TLS models are unaffected by this option
+ and always use the original scheme.
-'-mword-relocations'
+`-mword-relocations'
Only generate absolute relocations on word-sized values (i.e.
R_ARM_ABS32). This is enabled by default on targets (uClinux,
SymbianOS) where the runtime loader imposes this restriction, and
- when '-fpic' or '-fPIC' is specified.
+ when `-fpic' or `-fPIC' is specified.
-'-mfix-cortex-m3-ldrd'
- Some Cortex-M3 cores can cause data corruption when 'ldrd'
+`-mfix-cortex-m3-ldrd'
+ Some Cortex-M3 cores can cause data corruption when `ldrd'
instructions with overlapping destination and base registers are
used. This option avoids generating these instructions. This
- option is enabled by default when '-mcpu=cortex-m3' is specified.
+ option is enabled by default when `-mcpu=cortex-m3' is specified.
-'-munaligned-access'
-'-mno-unaligned-access'
+`-munaligned-access'
+`-mno-unaligned-access'
Enables (or disables) reading and writing of 16- and 32- bit values
from addresses that are not 16- or 32- bit aligned. By default
unaligned access is disabled for all pre-ARMv6 and all ARMv6-M
@@ -12851,36 +12950,36 @@ These '-m' options are defined for the ARM port:
unaligned access is not enabled then words in packed data
structures are accessed a byte at a time.
- The ARM attribute 'Tag_CPU_unaligned_access' is set in the
+ The ARM attribute `Tag_CPU_unaligned_access' is set in the
generated object file to either true or false, depending upon the
setting of this option. If unaligned access is enabled then the
- preprocessor symbol '__ARM_FEATURE_UNALIGNED' is also defined.
+ preprocessor symbol `__ARM_FEATURE_UNALIGNED' is also defined.
-'-mneon-for-64bits'
- Enables using Neon to handle scalar 64-bits operations. This is
+`-mneon-for-64bits'
+ Enables using Neon to handle scalar 64-bits operations. This is
disabled by default since the cost of moving data from core
registers to Neon is high.
-'-mslow-flash-data'
+`-mslow-flash-data'
Assume loading data from flash is slower than fetching instruction.
Therefore literal load is minimized for better performance. This
- option is only supported when compiling for ARMv7 M-profile and off
- by default.
+ option is only supported when compiling for ARMv7 M-profile and
+ off by default.
-'-masm-syntax-unified'
+`-masm-syntax-unified'
Assume inline assembler is using unified asm syntax. The default
is currently off which implies divided syntax. Currently this
option is available only for Thumb1 and has no effect on ARM state
and Thumb2. However, this may change in future releases of GCC.
Divided syntax should be considered deprecated.
-'-mrestrict-it'
+`-mrestrict-it'
Restricts generation of IT blocks to conform to the rules of ARMv8.
IT blocks can only contain a single 16-bit instruction from a
- select set of instructions. This option is on by default for ARMv8
+ select set of instructions. This option is on by default for ARMv8
Thumb mode.
-'-mprint-tune-info'
+`-mprint-tune-info'
Print CPU tuning information as comment in assembler file. This is
an option used only for regression testing of the compiler and not
intended for ordinary use in compiling code. This option is
@@ -12894,144 +12993,145 @@ File: gcc.info, Node: AVR Options, Next: Blackfin Options, Prev: ARM Options,
These options are defined for AVR implementations:
-'-mmcu=MCU'
+`-mmcu=MCU'
Specify Atmel AVR instruction set architectures (ISA) or MCU type.
- The default for this option is 'avr2'.
+ The default for this option is `avr2'.
GCC supports the following AVR devices and ISAs:
- 'avr2'
+ `avr2'
"Classic" devices with up to 8 KiB of program memory.
- MCU = 'attiny22', 'attiny26', 'at90c8534', 'at90s2313',
- 'at90s2323', 'at90s2333', 'at90s2343', 'at90s4414',
- 'at90s4433', 'at90s4434', 'at90s8515', 'at90s8535'.
+ MCU = `attiny22', `attiny26', `at90c8534', `at90s2313',
+ `at90s2323', `at90s2333', `at90s2343', `at90s4414',
+ `at90s4433', `at90s4434', `at90s8515', `at90s8535'.
- 'avr25'
+ `avr25'
"Classic" devices with up to 8 KiB of program memory and with
- the 'MOVW' instruction.
- MCU = 'ata5272', 'ata6616c', 'attiny13', 'attiny13a',
- 'attiny2313', 'attiny2313a', 'attiny24', 'attiny24a',
- 'attiny25', 'attiny261', 'attiny261a', 'attiny43u',
- 'attiny4313', 'attiny44', 'attiny44a', 'attiny441',
- 'attiny45', 'attiny461', 'attiny461a', 'attiny48',
- 'attiny828', 'attiny84', 'attiny84a', 'attiny841', 'attiny85',
- 'attiny861', 'attiny861a', 'attiny87', 'attiny88',
- 'at86rf401'.
-
- 'avr3'
- "Classic" devices with 16 KiB up to 64 KiB of program memory.
- MCU = 'at43usb355', 'at76c711'.
-
- 'avr31'
+ the `MOVW' instruction.
+ MCU = `ata5272', `ata6616c', `attiny13', `attiny13a',
+ `attiny2313', `attiny2313a', `attiny24', `attiny24a',
+ `attiny25', `attiny261', `attiny261a', `attiny43u',
+ `attiny4313', `attiny44', `attiny44a', `attiny441',
+ `attiny45', `attiny461', `attiny461a', `attiny48',
+ `attiny828', `attiny84', `attiny84a', `attiny841',
+ `attiny85', `attiny861', `attiny861a', `attiny87',
+ `attiny88', `at86rf401'.
+
+ `avr3'
+ "Classic" devices with 16 KiB up to 64 KiB of program memory.
+ MCU = `at43usb355', `at76c711'.
+
+ `avr31'
"Classic" devices with 128 KiB of program memory.
- MCU = 'atmega103', 'at43usb320'.
+ MCU = `atmega103', `at43usb320'.
- 'avr35'
+ `avr35'
"Classic" devices with 16 KiB up to 64 KiB of program memory
- and with the 'MOVW' instruction.
- MCU = 'ata5505', 'ata6617c', 'ata664251', 'atmega16u2',
- 'atmega32u2', 'atmega8u2', 'attiny1634', 'attiny167',
- 'at90usb162', 'at90usb82'.
+ and with the `MOVW' instruction.
+ MCU = `ata5505', `ata6617c', `ata664251', `atmega16u2',
+ `atmega32u2', `atmega8u2', `attiny1634', `attiny167',
+ `at90usb162', `at90usb82'.
- 'avr4'
+ `avr4'
"Enhanced" devices with up to 8 KiB of program memory.
- MCU = 'ata6285', 'ata6286', 'ata6289', 'ata6612c', 'atmega48',
- 'atmega48a', 'atmega48p', 'atmega48pa', 'atmega8', 'atmega8a',
- 'atmega8hva', 'atmega8515', 'atmega8535', 'atmega88',
- 'atmega88a', 'atmega88p', 'atmega88pa', 'at90pwm1',
- 'at90pwm2', 'at90pwm2b', 'at90pwm3', 'at90pwm3b', 'at90pwm81'.
-
- 'avr5'
+ MCU = `ata6285', `ata6286', `ata6289', `ata6612c',
+ `atmega48', `atmega48a', `atmega48p', `atmega48pa',
+ `atmega8', `atmega8a', `atmega8hva', `atmega8515',
+ `atmega8535', `atmega88', `atmega88a', `atmega88p',
+ `atmega88pa', `at90pwm1', `at90pwm2', `at90pwm2b',
+ `at90pwm3', `at90pwm3b', `at90pwm81'.
+
+ `avr5'
"Enhanced" devices with 16 KiB up to 64 KiB of program memory.
-
- MCU = 'ata5702m322', 'ata5782', 'ata5790', 'ata5790n',
- 'ata5795', 'ata5831', 'ata6613c', 'ata6614q', 'atmega16',
- 'atmega16a', 'atmega16hva', 'atmega16hva2', 'atmega16hvb',
- 'atmega16hvbrevb', 'atmega16m1', 'atmega16u4', 'atmega161',
- 'atmega162', 'atmega163', 'atmega164a', 'atmega164p',
- 'atmega164pa', 'atmega165', 'atmega165a', 'atmega165p',
- 'atmega165pa', 'atmega168', 'atmega168a', 'atmega168p',
- 'atmega168pa', 'atmega169', 'atmega169a', 'atmega169p',
- 'atmega169pa', 'atmega32', 'atmega32a', 'atmega32c1',
- 'atmega32hvb', 'atmega32hvbrevb', 'atmega32m1', 'atmega32u4',
- 'atmega32u6', 'atmega323', 'atmega324a', 'atmega324p',
- 'atmega324pa', 'atmega325', 'atmega325a', 'atmega325p',
- 'atmega325pa', 'atmega3250', 'atmega3250a', 'atmega3250p',
- 'atmega3250pa', 'atmega328', 'atmega328p', 'atmega329',
- 'atmega329a', 'atmega329p', 'atmega329pa', 'atmega3290',
- 'atmega3290a', 'atmega3290p', 'atmega3290pa', 'atmega406',
- 'atmega64', 'atmega64a', 'atmega64c1', 'atmega64hve',
- 'atmega64hve2', 'atmega64m1', 'atmega64rfr2', 'atmega640',
- 'atmega644', 'atmega644a', 'atmega644p', 'atmega644pa',
- 'atmega644rfr2', 'atmega645', 'atmega645a', 'atmega645p',
- 'atmega6450', 'atmega6450a', 'atmega6450p', 'atmega649',
- 'atmega649a', 'atmega649p', 'atmega6490', 'atmega6490a',
- 'atmega6490p', 'at90can32', 'at90can64', 'at90pwm161',
- 'at90pwm216', 'at90pwm316', 'at90scr100', 'at90usb646',
- 'at90usb647', 'at94k', 'm3000'.
-
- 'avr51'
+ MCU = `ata5702m322', `ata5782', `ata5790', `ata5790n',
+ `ata5795', `ata5831', `ata6613c', `ata6614q', `atmega16',
+ `atmega16a', `atmega16hva', `atmega16hva2', `atmega16hvb',
+ `atmega16hvbrevb', `atmega16m1', `atmega16u4', `atmega161',
+ `atmega162', `atmega163', `atmega164a', `atmega164p',
+ `atmega164pa', `atmega165', `atmega165a', `atmega165p',
+ `atmega165pa', `atmega168', `atmega168a', `atmega168p',
+ `atmega168pa', `atmega169', `atmega169a', `atmega169p',
+ `atmega169pa', `atmega32', `atmega32a', `atmega32c1',
+ `atmega32hvb', `atmega32hvbrevb', `atmega32m1', `atmega32u4',
+ `atmega32u6', `atmega323', `atmega324a', `atmega324p',
+ `atmega324pa', `atmega325', `atmega325a', `atmega325p',
+ `atmega325pa', `atmega3250', `atmega3250a', `atmega3250p',
+ `atmega3250pa', `atmega328', `atmega328p', `atmega329',
+ `atmega329a', `atmega329p', `atmega329pa', `atmega3290',
+ `atmega3290a', `atmega3290p', `atmega3290pa', `atmega406',
+ `atmega64', `atmega64a', `atmega64c1', `atmega64hve',
+ `atmega64hve2', `atmega64m1', `atmega64rfr2', `atmega640',
+ `atmega644', `atmega644a', `atmega644p', `atmega644pa',
+ `atmega644rfr2', `atmega645', `atmega645a', `atmega645p',
+ `atmega6450', `atmega6450a', `atmega6450p', `atmega649',
+ `atmega649a', `atmega649p', `atmega6490', `atmega6490a',
+ `atmega6490p', `at90can32', `at90can64', `at90pwm161',
+ `at90pwm216', `at90pwm316', `at90scr100', `at90usb646',
+ `at90usb647', `at94k', `m3000'.
+
+ `avr51'
"Enhanced" devices with 128 KiB of program memory.
- MCU = 'atmega128', 'atmega128a', 'atmega128rfa1',
- 'atmega128rfr2', 'atmega1280', 'atmega1281', 'atmega1284',
- 'atmega1284p', 'atmega1284rfr2', 'at90can128', 'at90usb1286',
- 'at90usb1287'.
-
- 'avr6'
- "Enhanced" devices with 3-byte PC, i.e. with more than 128 KiB
- of program memory.
- MCU = 'atmega256rfr2', 'atmega2560', 'atmega2561',
- 'atmega2564rfr2'.
-
- 'avrxmega2'
+ MCU = `atmega128', `atmega128a', `atmega128rfa1',
+ `atmega128rfr2', `atmega1280', `atmega1281', `atmega1284',
+ `atmega1284p', `atmega1284rfr2', `at90can128', `at90usb1286',
+ `at90usb1287'.
+
+ `avr6'
+ "Enhanced" devices with 3-byte PC, i.e. with more than
+ 128 KiB of program memory.
+ MCU = `atmega256rfr2', `atmega2560', `atmega2561',
+ `atmega2564rfr2'.
+
+ `avrxmega2'
"XMEGA" devices with more than 8 KiB and up to 64 KiB of
program memory.
- MCU = 'atxmega16a4', 'atxmega16a4u', 'atxmega16c4',
- 'atxmega16d4', 'atxmega16e5', 'atxmega32a4', 'atxmega32a4u',
- 'atxmega32c3', 'atxmega32c4', 'atxmega32d3', 'atxmega32d4',
- 'atxmega32e5', 'atxmega8e5'.
+ MCU = `atxmega16a4', `atxmega16a4u', `atxmega16c4',
+ `atxmega16d4', `atxmega16e5', `atxmega32a4', `atxmega32a4u',
+ `atxmega32c3', `atxmega32c4', `atxmega32d3', `atxmega32d4',
+ `atxmega32e5', `atxmega8e5'.
- 'avrxmega4'
+ `avrxmega4'
"XMEGA" devices with more than 64 KiB and up to 128 KiB of
program memory.
- MCU = 'atxmega64a3', 'atxmega64a3u', 'atxmega64a4u',
- 'atxmega64b1', 'atxmega64b3', 'atxmega64c3', 'atxmega64d3',
- 'atxmega64d4'.
+ MCU = `atxmega64a3', `atxmega64a3u', `atxmega64a4u',
+ `atxmega64b1', `atxmega64b3', `atxmega64c3', `atxmega64d3',
+ `atxmega64d4'.
- 'avrxmega5'
+ `avrxmega5'
"XMEGA" devices with more than 64 KiB and up to 128 KiB of
program memory and more than 64 KiB of RAM.
- MCU = 'atxmega64a1', 'atxmega64a1u'.
+ MCU = `atxmega64a1', `atxmega64a1u'.
- 'avrxmega6'
+ `avrxmega6'
"XMEGA" devices with more than 128 KiB of program memory.
- MCU = 'atxmega128a3', 'atxmega128a3u', 'atxmega128b1',
- 'atxmega128b3', 'atxmega128c3', 'atxmega128d3',
- 'atxmega128d4', 'atxmega192a3', 'atxmega192a3u',
- 'atxmega192c3', 'atxmega192d3', 'atxmega256a3',
- 'atxmega256a3b', 'atxmega256a3bu', 'atxmega256a3u',
- 'atxmega256c3', 'atxmega256d3', 'atxmega384c3',
- 'atxmega384d3'.
-
- 'avrxmega7'
+ MCU = `atxmega128a3', `atxmega128a3u', `atxmega128b1',
+ `atxmega128b3', `atxmega128c3', `atxmega128d3',
+ `atxmega128d4', `atxmega192a3', `atxmega192a3u',
+ `atxmega192c3', `atxmega192d3', `atxmega256a3',
+ `atxmega256a3b', `atxmega256a3bu', `atxmega256a3u',
+ `atxmega256c3', `atxmega256d3', `atxmega384c3',
+ `atxmega384d3'.
+
+ `avrxmega7'
"XMEGA" devices with more than 128 KiB of program memory and
more than 64 KiB of RAM.
- MCU = 'atxmega128a1', 'atxmega128a1u', 'atxmega128a4u'.
+ MCU = `atxmega128a1', `atxmega128a1u', `atxmega128a4u'.
- 'avrtiny'
+ `avrtiny'
"TINY" Tiny core devices with 512 B up to 4 KiB of program
memory.
- MCU = 'attiny10', 'attiny20', 'attiny4', 'attiny40',
- 'attiny5', 'attiny9'.
+ MCU = `attiny10', `attiny20', `attiny4', `attiny40',
+ `attiny5', `attiny9'.
- 'avr1'
+ `avr1'
This ISA is implemented by the minimal AVR core and supported
for assembler only.
- MCU = 'attiny11', 'attiny12', 'attiny15', 'attiny28',
- 'at90s1200'.
+ MCU = `attiny11', `attiny12', `attiny15', `attiny28',
+ `at90s1200'.
+
-'-maccumulate-args'
+`-maccumulate-args'
Accumulate outgoing function arguments and acquire/release the
needed stack space for outgoing function arguments once in function
prologue/epilogue. Without this option, outgoing arguments are
@@ -13039,92 +13139,92 @@ These options are defined for AVR implementations:
Popping the arguments after the function call can be expensive on
AVR so that accumulating the stack space might lead to smaller
- executables because arguments need not to be removed from the stack
- after such a function call.
+ executables because arguments need not to be removed from the
+ stack after such a function call.
This option can lead to reduced code size for functions that
perform several calls to functions that get their arguments on the
stack like calls to printf-like functions.
-'-mbranch-cost=COST'
+`-mbranch-cost=COST'
Set the branch costs for conditional branch instructions to COST.
- Reasonable values for COST are small, non-negative integers. The
+ Reasonable values for COST are small, non-negative integers. The
default branch cost is 0.
-'-mcall-prologues'
+`-mcall-prologues'
Functions prologues/epilogues are expanded as calls to appropriate
subroutines. Code size is smaller.
-'-mint8'
- Assume 'int' to be 8-bit integer. This affects the sizes of all
- types: a 'char' is 1 byte, an 'int' is 1 byte, a 'long' is 2 bytes,
- and 'long long' is 4 bytes. Please note that this option does not
+`-mint8'
+ Assume `int' to be 8-bit integer. This affects the sizes of all
+ types: a `char' is 1 byte, an `int' is 1 byte, a `long' is 2 bytes,
+ and `long long' is 4 bytes. Please note that this option does not
conform to the C standards, but it results in smaller code size.
-'-mn-flash=NUM'
+`-mn-flash=NUM'
Assume that the flash memory has a size of NUM times 64 KiB.
-'-mno-interrupts'
+`-mno-interrupts'
Generated code is not compatible with hardware interrupts. Code
size is smaller.
-'-mrelax'
- Try to replace 'CALL' resp. 'JMP' instruction by the shorter
- 'RCALL' resp. 'RJMP' instruction if applicable. Setting '-mrelax'
- just adds the '--mlink-relax' option to the assembler's command
- line and the '--relax' option to the linker's command line.
+`-mrelax'
+ Try to replace `CALL' resp. `JMP' instruction by the shorter
+ `RCALL' resp. `RJMP' instruction if applicable. Setting `-mrelax'
+ just adds the `--mlink-relax' option to the assembler's command
+ line and the `--relax' option to the linker's command line.
Jump relaxing is performed by the linker because jump offsets are
- not known before code is located. Therefore, the assembler code
+ not known before code is located. Therefore, the assembler code
generated by the compiler is the same, but the instructions in the
executable may differ from instructions in the assembler code.
Relaxing must be turned on if linker stubs are needed, see the
- section on 'EIND' and linker stubs below.
+ section on `EIND' and linker stubs below.
-'-mrmw'
+`-mrmw'
Assume that the device supports the Read-Modify-Write instructions
- 'XCH', 'LAC', 'LAS' and 'LAT'.
+ `XCH', `LAC', `LAS' and `LAT'.
-'-msp8'
+`-msp8'
Treat the stack pointer register as an 8-bit register, i.e. assume
the high byte of the stack pointer is zero. In general, you don't
need to set this option by hand.
This option is used internally by the compiler to select and build
- multilibs for architectures 'avr2' and 'avr25'. These
- architectures mix devices with and without 'SPH'. For any setting
- other than '-mmcu=avr2' or '-mmcu=avr25' the compiler driver adds
+ multilibs for architectures `avr2' and `avr25'. These
+ architectures mix devices with and without `SPH'. For any setting
+ other than `-mmcu=avr2' or `-mmcu=avr25' the compiler driver adds
or removes this option from the compiler proper's command line,
because the compiler then knows if the device or architecture has
- an 8-bit stack pointer and thus no 'SPH' register or not.
+ an 8-bit stack pointer and thus no `SPH' register or not.
-'-mstrict-X'
- Use address register 'X' in a way proposed by the hardware. This
- means that 'X' is only used in indirect, post-increment or
+`-mstrict-X'
+ Use address register `X' in a way proposed by the hardware. This
+ means that `X' is only used in indirect, post-increment or
pre-decrement addressing.
- Without this option, the 'X' register may be used in the same way
- as 'Y' or 'Z' which then is emulated by additional instructions.
- For example, loading a value with 'X+const' addressing with a small
- non-negative 'const < 64' to a register RN is performed as
+ Without this option, the `X' register may be used in the same way
+ as `Y' or `Z' which then is emulated by additional instructions.
+ For example, loading a value with `X+const' addressing with a
+ small non-negative `const < 64' to a register RN is performed as
adiw r26, const ; X += const
ld RN, X ; RN = *X
sbiw r26, const ; X -= const
-'-mtiny-stack'
+`-mtiny-stack'
Only change the lower 8 bits of the stack pointer.
-'-nodevicelib'
- Don't link against AVR-LibC's device specific library 'libdev.a'.
+`-nodevicelib'
+ Don't link against AVR-LibC's device specific library `libdev.a'.
-'-Waddr-space-convert'
+`-Waddr-space-convert'
Warn about conversions between address spaces in the case where the
resulting address space is not contained in the incoming address
space.
-3.17.5.1 'EIND' and Devices with More Than 128 Ki Bytes of Flash
+3.17.5.1 `EIND' and Devices with More Than 128 Ki Bytes of Flash
................................................................
Pointers in the implementation are 16 bits wide. The address of a
@@ -13133,50 +13233,50 @@ and calls can target any code address in the range of 64 Ki words.
In order to facilitate indirect jump on devices with more than 128 Ki
bytes of program memory space, there is a special function register
-called 'EIND' that serves as most significant part of the target address
-when 'EICALL' or 'EIJMP' instructions are used.
+called `EIND' that serves as most significant part of the target address
+when `EICALL' or `EIJMP' instructions are used.
- Indirect jumps and calls on these devices are handled as follows by the
-compiler and are subject to some limitations:
+ Indirect jumps and calls on these devices are handled as follows by
+the compiler and are subject to some limitations:
- * The compiler never sets 'EIND'.
+ * The compiler never sets `EIND'.
- * The compiler uses 'EIND' implicitely in 'EICALL'/'EIJMP'
- instructions or might read 'EIND' directly in order to emulate an
- indirect call/jump by means of a 'RET' instruction.
+ * The compiler uses `EIND' implicitely in `EICALL'/`EIJMP'
+ instructions or might read `EIND' directly in order to emulate an
+ indirect call/jump by means of a `RET' instruction.
- * The compiler assumes that 'EIND' never changes during the startup
- code or during the application. In particular, 'EIND' is not
+ * The compiler assumes that `EIND' never changes during the startup
+ code or during the application. In particular, `EIND' is not
saved/restored in function or interrupt service routine
prologue/epilogue.
* For indirect calls to functions and computed goto, the linker
- generates _stubs_. Stubs are jump pads sometimes also called
- _trampolines_. Thus, the indirect call/jump jumps to such a stub.
+ generates _stubs_. Stubs are jump pads sometimes also called
+ _trampolines_. Thus, the indirect call/jump jumps to such a stub.
The stub contains a direct jump to the desired address.
* Linker relaxation must be turned on so that the linker generates
- the stubs correctly in all situations. See the compiler option
- '-mrelax' and the linker option '--relax'. There are corner cases
+ the stubs correctly in all situations. See the compiler option
+ `-mrelax' and the linker option `--relax'. There are corner cases
where the linker is supposed to generate stubs but aborts without
relaxation and without a helpful error message.
- * The default linker script is arranged for code with 'EIND = 0'. If
- code is supposed to work for a setup with 'EIND != 0', a custom
+ * The default linker script is arranged for code with `EIND = 0'.
+ If code is supposed to work for a setup with `EIND != 0', a custom
linker script has to be used in order to place the sections whose
- name start with '.trampolines' into the segment where 'EIND' points
- to.
+ name start with `.trampolines' into the segment where `EIND'
+ points to.
- * The startup code from libgcc never sets 'EIND'. Notice that
- startup code is a blend of code from libgcc and AVR-LibC. For the
- impact of AVR-LibC on 'EIND', see the
+ * The startup code from libgcc never sets `EIND'. Notice that
+ startup code is a blend of code from libgcc and AVR-LibC. For the
+ impact of AVR-LibC on `EIND', see the
AVR-LibC user manual (http://nongnu.org/avr-libc/user-manual/).
- * It is legitimate for user-specific startup code to set up 'EIND'
+ * It is legitimate for user-specific startup code to set up `EIND'
early, for example by means of initialization code located in
- section '.init3'. Such code runs prior to general startup code
+ section `.init3'. Such code runs prior to general startup code
that initializes RAM and calls constructors, but after the bit of
- startup code from AVR-LibC that sets 'EIND' to the segment where
+ startup code from AVR-LibC that sets `EIND' to the segment where
the vector table is located.
#include <avr/io.h>
@@ -13188,30 +13288,35 @@ compiler and are subject to some limitations:
"out %i0,r24" :: "n" (&EIND) : "r24","memory");
}
- The '__trampolines_start' symbol is defined in the linker script.
+ The `__trampolines_start' symbol is defined in the linker script.
* Stubs are generated automatically by the linker if the following
two conditions are met:
-
- - The address of a label is taken by means of the 'gs' modifier
+ - The address of a label is taken by means of the `gs' modifier
(short for _generate stubs_) like so:
LDI r24, lo8(gs(FUNC))
LDI r25, hi8(gs(FUNC))
+
- The final location of that label is in a code segment
_outside_ the segment where the stubs are located.
- * The compiler emits such 'gs' modifiers for code labels in the
+ * The compiler emits such `gs' modifiers for code labels in the
following situations:
- Taking address of a function or code label.
+
- Computed goto.
- - If prologue-save function is used, see '-mcall-prologues'
+
+ - If prologue-save function is used, see `-mcall-prologues'
command-line option.
- - Switch/case dispatch tables. If you do not want such dispatch
- tables you can specify the '-fno-jump-tables' command-line
+
+ - Switch/case dispatch tables. If you do not want such dispatch
+ tables you can specify the `-fno-jump-tables' command-line
option.
+
- C and C++ constructors/destructors called during
startup/shutdown.
- - If the tools hit a 'gs()' modifier explained above.
+
+ - If the tools hit a `gs()' modifier explained above.
* Jumping to non-symbolic addresses like so is _not_ supported:
@@ -13222,7 +13327,7 @@ compiler and are subject to some limitations:
}
Instead, a stub has to be set up, i.e. the function has to be
- called through a symbol ('func_4' in the example):
+ called through a symbol (`func_4' in the example):
int main (void)
{
@@ -13232,39 +13337,40 @@ compiler and are subject to some limitations:
return func_4();
}
- and the application be linked with '-Wl,--defsym,func_4=0x4'.
- Alternatively, 'func_4' can be defined in the linker script.
+ and the application be linked with `-Wl,--defsym,func_4=0x4'.
+ Alternatively, `func_4' can be defined in the linker script.
-3.17.5.2 Handling of the 'RAMPD', 'RAMPX', 'RAMPY' and 'RAMPZ' Special Function Registers
+3.17.5.2 Handling of the `RAMPD', `RAMPX', `RAMPY' and `RAMPZ' Special Function Registers
.........................................................................................
Some AVR devices support memories larger than the 64 KiB range that can
be accessed with 16-bit pointers. To access memory locations outside
-this 64 KiB range, the contentent of a 'RAMP' register is used as high
-part of the address: The 'X', 'Y', 'Z' address register is concatenated
-with the 'RAMPX', 'RAMPY', 'RAMPZ' special function register,
-respectively, to get a wide address. Similarly, 'RAMPD' is used
+this 64 KiB range, the contentent of a `RAMP' register is used as high
+part of the address: The `X', `Y', `Z' address register is concatenated
+with the `RAMPX', `RAMPY', `RAMPZ' special function register,
+respectively, to get a wide address. Similarly, `RAMPD' is used
together with direct addressing.
- * The startup code initializes the 'RAMP' special function registers
+ * The startup code initializes the `RAMP' special function registers
with zero.
* If a *note named address space: AVR Named Address Spaces. other
- than generic or '__flash' is used, then 'RAMPZ' is set as needed
+ than generic or `__flash' is used, then `RAMPZ' is set as needed
before the operation.
* If the device supports RAM larger than 64 KiB and the compiler
- needs to change 'RAMPZ' to accomplish an operation, 'RAMPZ' is
+ needs to change `RAMPZ' to accomplish an operation, `RAMPZ' is
reset to zero after the operation.
- * If the device comes with a specific 'RAMP' register, the ISR
+ * If the device comes with a specific `RAMP' register, the ISR
prologue/epilogue saves/restores that SFR and initializes it with
zero in case the ISR code might (implicitly) use it.
- * RAM larger than 64 KiB is not supported by GCC for AVR targets. If
- you use inline assembler to read from locations outside the 16-bit
- address range and change one of the 'RAMP' registers, you must
- reset it to zero after the access.
+ * RAM larger than 64 KiB is not supported by GCC for AVR targets.
+ If you use inline assembler to read from locations outside the
+ 16-bit address range and change one of the `RAMP' registers, you
+ must reset it to zero after the access.
+
3.17.5.3 AVR Built-in Macros
............................
@@ -13272,130 +13378,131 @@ together with direct addressing.
GCC defines several built-in macros so that the user code can test for
the presence or absence of features. Almost any of the following
built-in macros are deduced from device capabilities and thus triggered
-by the '-mmcu=' command-line option.
+by the `-mmcu=' command-line option.
For even more AVR-specific built-in macros see *note AVR Named Address
Spaces:: and *note AVR Built-in Functions::.
-'__AVR_ARCH__'
+`__AVR_ARCH__'
Build-in macro that resolves to a decimal number that identifies
- the architecture and depends on the '-mmcu=MCU' option. Possible
+ the architecture and depends on the `-mmcu=MCU' option. Possible
values are:
- '2', '25', '3', '31', '35', '4', '5', '51', '6'
+ `2', `25', `3', `31', `35', `4', `5', `51', `6'
- for MCU='avr2', 'avr25', 'avr3', 'avr31', 'avr35', 'avr4', 'avr5',
- 'avr51', 'avr6',
+ for MCU=`avr2', `avr25', `avr3', `avr31', `avr35', `avr4', `avr5',
+ `avr51', `avr6',
respectively and
- '100', '102', '104', '105', '106', '107'
+ `100', `102', `104', `105', `106', `107'
- for MCU='avrtiny', 'avrxmega2', 'avrxmega4', 'avrxmega5',
- 'avrxmega6', 'avrxmega7', respectively. If MCU specifies a device,
- this built-in macro is set accordingly. For example, with
- '-mmcu=atmega8' the macro is defined to '4'.
+ for MCU=`avrtiny', `avrxmega2', `avrxmega4', `avrxmega5',
+ `avrxmega6', `avrxmega7', respectively. If MCU specifies a
+ device, this built-in macro is set accordingly. For example, with
+ `-mmcu=atmega8' the macro is defined to `4'.
-'__AVR_DEVICE__'
- Setting '-mmcu=DEVICE' defines this built-in macro which reflects
- the device's name. For example, '-mmcu=atmega8' defines the
- built-in macro '__AVR_ATmega8__', '-mmcu=attiny261a' defines
- '__AVR_ATtiny261A__', etc.
+`__AVR_DEVICE__'
+ Setting `-mmcu=DEVICE' defines this built-in macro which reflects
+ the device's name. For example, `-mmcu=atmega8' defines the
+ built-in macro `__AVR_ATmega8__', `-mmcu=attiny261a' defines
+ `__AVR_ATtiny261A__', etc.
- The built-in macros' names follow the scheme '__AVR_DEVICE__' where
- DEVICE is the device name as from the AVR user manual. The
+ The built-in macros' names follow the scheme `__AVR_DEVICE__'
+ where DEVICE is the device name as from the AVR user manual. The
difference between DEVICE in the built-in macro and DEVICE in
- '-mmcu=DEVICE' is that the latter is always lowercase.
+ `-mmcu=DEVICE' is that the latter is always lowercase.
If DEVICE is not a device but only a core architecture like
- 'avr51', this macro is not defined.
+ `avr51', this macro is not defined.
-'__AVR_DEVICE_NAME__'
- Setting '-mmcu=DEVICE' defines this built-in macro to the device's
- name. For example, with '-mmcu=atmega8' the macro is defined to
- 'atmega8'.
+`__AVR_DEVICE_NAME__'
+ Setting `-mmcu=DEVICE' defines this built-in macro to the device's
+ name. For example, with `-mmcu=atmega8' the macro is defined to
+ `atmega8'.
If DEVICE is not a device but only a core architecture like
- 'avr51', this macro is not defined.
+ `avr51', this macro is not defined.
-'__AVR_XMEGA__'
+`__AVR_XMEGA__'
The device / architecture belongs to the XMEGA family of devices.
-'__AVR_HAVE_ELPM__'
- The device has the the 'ELPM' instruction.
+`__AVR_HAVE_ELPM__'
+ The device has the the `ELPM' instruction.
-'__AVR_HAVE_ELPMX__'
- The device has the 'ELPM RN,Z' and 'ELPM RN,Z+' instructions.
+`__AVR_HAVE_ELPMX__'
+ The device has the `ELPM RN,Z' and `ELPM RN,Z+' instructions.
-'__AVR_HAVE_MOVW__'
- The device has the 'MOVW' instruction to perform 16-bit
+`__AVR_HAVE_MOVW__'
+ The device has the `MOVW' instruction to perform 16-bit
register-register moves.
-'__AVR_HAVE_LPMX__'
- The device has the 'LPM RN,Z' and 'LPM RN,Z+' instructions.
+`__AVR_HAVE_LPMX__'
+ The device has the `LPM RN,Z' and `LPM RN,Z+' instructions.
-'__AVR_HAVE_MUL__'
+`__AVR_HAVE_MUL__'
The device has a hardware multiplier.
-'__AVR_HAVE_JMP_CALL__'
- The device has the 'JMP' and 'CALL' instructions. This is the case
- for devices with at least 16 KiB of program memory.
+`__AVR_HAVE_JMP_CALL__'
+ The device has the `JMP' and `CALL' instructions. This is the
+ case for devices with at least 16 KiB of program memory.
-'__AVR_HAVE_EIJMP_EICALL__'
-'__AVR_3_BYTE_PC__'
- The device has the 'EIJMP' and 'EICALL' instructions. This is the
+`__AVR_HAVE_EIJMP_EICALL__'
+`__AVR_3_BYTE_PC__'
+ The device has the `EIJMP' and `EICALL' instructions. This is the
case for devices with more than 128 KiB of program memory. This
also means that the program counter (PC) is 3 bytes wide.
-'__AVR_2_BYTE_PC__'
- The program counter (PC) is 2 bytes wide. This is the case for
+`__AVR_2_BYTE_PC__'
+ The program counter (PC) is 2 bytes wide. This is the case for
devices with up to 128 KiB of program memory.
-'__AVR_HAVE_8BIT_SP__'
-'__AVR_HAVE_16BIT_SP__'
+`__AVR_HAVE_8BIT_SP__'
+`__AVR_HAVE_16BIT_SP__'
The stack pointer (SP) register is treated as 8-bit respectively
- 16-bit register by the compiler. The definition of these macros is
- affected by '-mtiny-stack'.
+ 16-bit register by the compiler. The definition of these macros
+ is affected by `-mtiny-stack'.
-'__AVR_HAVE_SPH__'
-'__AVR_SP8__'
+`__AVR_HAVE_SPH__'
+`__AVR_SP8__'
The device has the SPH (high part of stack pointer) special
- function register or has an 8-bit stack pointer, respectively. The
- definition of these macros is affected by '-mmcu=' and in the cases
- of '-mmcu=avr2' and '-mmcu=avr25' also by '-msp8'.
-
-'__AVR_HAVE_RAMPD__'
-'__AVR_HAVE_RAMPX__'
-'__AVR_HAVE_RAMPY__'
-'__AVR_HAVE_RAMPZ__'
- The device has the 'RAMPD', 'RAMPX', 'RAMPY', 'RAMPZ' special
+ function register or has an 8-bit stack pointer, respectively.
+ The definition of these macros is affected by `-mmcu=' and in the
+ cases of `-mmcu=avr2' and `-mmcu=avr25' also by `-msp8'.
+
+`__AVR_HAVE_RAMPD__'
+`__AVR_HAVE_RAMPX__'
+`__AVR_HAVE_RAMPY__'
+`__AVR_HAVE_RAMPZ__'
+ The device has the `RAMPD', `RAMPX', `RAMPY', `RAMPZ' special
function register, respectively.
-'__NO_INTERRUPTS__'
- This macro reflects the '-mno-interrupts' command-line option.
+`__NO_INTERRUPTS__'
+ This macro reflects the `-mno-interrupts' command-line option.
-'__AVR_ERRATA_SKIP__'
-'__AVR_ERRATA_SKIP_JMP_CALL__'
+`__AVR_ERRATA_SKIP__'
+`__AVR_ERRATA_SKIP_JMP_CALL__'
Some AVR devices (AT90S8515, ATmega103) must not skip 32-bit
instructions because of a hardware erratum. Skip instructions are
- 'SBRS', 'SBRC', 'SBIS', 'SBIC' and 'CPSE'. The second macro is
- only defined if '__AVR_HAVE_JMP_CALL__' is also set.
+ `SBRS', `SBRC', `SBIS', `SBIC' and `CPSE'. The second macro is
+ only defined if `__AVR_HAVE_JMP_CALL__' is also set.
-'__AVR_ISA_RMW__'
+`__AVR_ISA_RMW__'
The device has Read-Modify-Write instructions (XCH, LAC, LAS and
LAT).
-'__AVR_SFR_OFFSET__=OFFSET'
+`__AVR_SFR_OFFSET__=OFFSET'
Instructions that can address I/O special function registers
- directly like 'IN', 'OUT', 'SBI', etc. may use a different address
- as if addressed by an instruction to access RAM like 'LD' or 'STS'.
- This offset depends on the device architecture and has to be
- subtracted from the RAM address in order to get the respective
+ directly like `IN', `OUT', `SBI', etc. may use a different address
+ as if addressed by an instruction to access RAM like `LD' or
+ `STS'. This offset depends on the device architecture and has to
+ be subtracted from the RAM address in order to get the respective
I/O address.
-'__WITH_AVRLIBC__'
+`__WITH_AVRLIBC__'
The compiler is configured to be used together with AVR-Libc. See
- the '--with-avrlibc' configure option.
+ the `--with-avrlibc' configure option.
+

File: gcc.info, Node: Blackfin Options, Next: C6X Options, Prev: AVR Options, Up: Submodel Options
@@ -13403,120 +13510,121 @@ File: gcc.info, Node: Blackfin Options, Next: C6X Options, Prev: AVR Options,
3.17.6 Blackfin Options
-----------------------
-'-mcpu=CPU[-SIREVISION]'
+`-mcpu=CPU[-SIREVISION]'
Specifies the name of the target Blackfin processor. Currently,
- CPU can be one of 'bf512', 'bf514', 'bf516', 'bf518', 'bf522',
- 'bf523', 'bf524', 'bf525', 'bf526', 'bf527', 'bf531', 'bf532',
- 'bf533', 'bf534', 'bf536', 'bf537', 'bf538', 'bf539', 'bf542',
- 'bf544', 'bf547', 'bf548', 'bf549', 'bf542m', 'bf544m', 'bf547m',
- 'bf548m', 'bf549m', 'bf561', 'bf592'.
+ CPU can be one of `bf512', `bf514', `bf516', `bf518', `bf522',
+ `bf523', `bf524', `bf525', `bf526', `bf527', `bf531', `bf532',
+ `bf533', `bf534', `bf536', `bf537', `bf538', `bf539', `bf542',
+ `bf544', `bf547', `bf548', `bf549', `bf542m', `bf544m', `bf547m',
+ `bf548m', `bf549m', `bf561', `bf592'.
The optional SIREVISION specifies the silicon revision of the
target Blackfin processor. Any workarounds available for the
- targeted silicon revision are enabled. If SIREVISION is 'none', no
- workarounds are enabled. If SIREVISION is 'any', all workarounds
- for the targeted processor are enabled. The '__SILICON_REVISION__'
- macro is defined to two hexadecimal digits representing the major
- and minor numbers in the silicon revision. If SIREVISION is
- 'none', the '__SILICON_REVISION__' is not defined. If SIREVISION
- is 'any', the '__SILICON_REVISION__' is defined to be '0xffff'. If
- this optional SIREVISION is not used, GCC assumes the latest known
- silicon revision of the targeted Blackfin processor.
+ targeted silicon revision are enabled. If SIREVISION is `none',
+ no workarounds are enabled. If SIREVISION is `any', all
+ workarounds for the targeted processor are enabled. The
+ `__SILICON_REVISION__' macro is defined to two hexadecimal digits
+ representing the major and minor numbers in the silicon revision.
+ If SIREVISION is `none', the `__SILICON_REVISION__' is not
+ defined. If SIREVISION is `any', the `__SILICON_REVISION__' is
+ defined to be `0xffff'. If this optional SIREVISION is not used,
+ GCC assumes the latest known silicon revision of the targeted
+ Blackfin processor.
GCC defines a preprocessor macro for the specified CPU. For the
- 'bfin-elf' toolchain, this option causes the hardware BSP provided
- by libgloss to be linked in if '-msim' is not given.
+ `bfin-elf' toolchain, this option causes the hardware BSP provided
+ by libgloss to be linked in if `-msim' is not given.
- Without this option, 'bf532' is used as the processor by default.
+ Without this option, `bf532' is used as the processor by default.
- Note that support for 'bf561' is incomplete. For 'bf561', only the
- preprocessor macro is defined.
+ Note that support for `bf561' is incomplete. For `bf561', only
+ the preprocessor macro is defined.
-'-msim'
+`-msim'
Specifies that the program will be run on the simulator. This
causes the simulator BSP provided by libgloss to be linked in.
- This option has effect only for 'bfin-elf' toolchain. Certain
- other options, such as '-mid-shared-library' and '-mfdpic', imply
- '-msim'.
+ This option has effect only for `bfin-elf' toolchain. Certain
+ other options, such as `-mid-shared-library' and `-mfdpic', imply
+ `-msim'.
-'-momit-leaf-frame-pointer'
+`-momit-leaf-frame-pointer'
Don't keep the frame pointer in a register for leaf functions.
This avoids the instructions to save, set up and restore frame
pointers and makes an extra register available in leaf functions.
- The option '-fomit-frame-pointer' removes the frame pointer for all
- functions, which might make debugging harder.
+ The option `-fomit-frame-pointer' removes the frame pointer for
+ all functions, which might make debugging harder.
-'-mspecld-anomaly'
+`-mspecld-anomaly'
When enabled, the compiler ensures that the generated code does not
- contain speculative loads after jump instructions. If this option
- is used, '__WORKAROUND_SPECULATIVE_LOADS' is defined.
+ contain speculative loads after jump instructions. If this option
+ is used, `__WORKAROUND_SPECULATIVE_LOADS' is defined.
-'-mno-specld-anomaly'
+`-mno-specld-anomaly'
Don't generate extra code to prevent speculative loads from
occurring.
-'-mcsync-anomaly'
+`-mcsync-anomaly'
When enabled, the compiler ensures that the generated code does not
contain CSYNC or SSYNC instructions too soon after conditional
- branches. If this option is used, '__WORKAROUND_SPECULATIVE_SYNCS'
- is defined.
+ branches. If this option is used,
+ `__WORKAROUND_SPECULATIVE_SYNCS' is defined.
-'-mno-csync-anomaly'
+`-mno-csync-anomaly'
Don't generate extra code to prevent CSYNC or SSYNC instructions
from occurring too soon after a conditional branch.
-'-mlow-64k'
+`-mlow-64k'
When enabled, the compiler is free to take advantage of the
knowledge that the entire program fits into the low 64k of memory.
-'-mno-low-64k'
+`-mno-low-64k'
Assume that the program is arbitrarily large. This is the default.
-'-mstack-check-l1'
+`-mstack-check-l1'
Do stack checking using information placed into L1 scratchpad
memory by the uClinux kernel.
-'-mid-shared-library'
+`-mid-shared-library'
Generate code that supports shared libraries via the library ID
method. This allows for execute in place and shared libraries in
an environment without virtual memory management. This option
- implies '-fPIC'. With a 'bfin-elf' target, this option implies
- '-msim'.
+ implies `-fPIC'. With a `bfin-elf' target, this option implies
+ `-msim'.
-'-mno-id-shared-library'
+`-mno-id-shared-library'
Generate code that doesn't assume ID-based shared libraries are
being used. This is the default.
-'-mleaf-id-shared-library'
+`-mleaf-id-shared-library'
Generate code that supports shared libraries via the library ID
method, but assumes that this library or executable won't link
- against any other ID shared libraries. That allows the compiler to
- use faster code for jumps and calls.
+ against any other ID shared libraries. That allows the compiler
+ to use faster code for jumps and calls.
-'-mno-leaf-id-shared-library'
+`-mno-leaf-id-shared-library'
Do not assume that the code being compiled won't link against any
ID shared libraries. Slower code is generated for jump and call
insns.
-'-mshared-library-id=n'
+`-mshared-library-id=n'
Specifies the identification number of the ID-based shared library
being compiled. Specifying a value of 0 generates more compact
code; specifying other values forces the allocation of that number
- to the current library but is no more space- or time-efficient than
- omitting this option.
+ to the current library but is no more space- or time-efficient
+ than omitting this option.
-'-msep-data'
+`-msep-data'
Generate code that allows the data segment to be located in a
different area of memory from the text segment. This allows for
execute in place in an environment without virtual memory
management by eliminating relocations against the text section.
-'-mno-sep-data'
+`-mno-sep-data'
Generate code that assumes that the data segment follows the text
segment. This is the default.
-'-mlong-calls'
-'-mno-long-calls'
+`-mlong-calls'
+`-mno-long-calls'
Tells the compiler to perform function calls by first loading the
address of the function into a register and then performing a
subroutine call on this register. This switch is needed if the
@@ -13524,56 +13632,56 @@ File: gcc.info, Node: Blackfin Options, Next: C6X Options, Prev: AVR Options,
offset-based version of subroutine call instruction.
This feature is not enabled by default. Specifying
- '-mno-long-calls' restores the default behavior. Note these
+ `-mno-long-calls' restores the default behavior. Note these
switches have no effect on how the compiler generates code to
handle function calls via function pointers.
-'-mfast-fp'
- Link with the fast floating-point library. This library relaxes
+`-mfast-fp'
+ Link with the fast floating-point library. This library relaxes
some of the IEEE floating-point standard's rules for checking
inputs against Not-a-Number (NAN), in the interest of performance.
-'-minline-plt'
+`-minline-plt'
Enable inlining of PLT entries in function calls to functions that
- are not known to bind locally. It has no effect without '-mfdpic'.
+ are not known to bind locally. It has no effect without `-mfdpic'.
-'-mmulticore'
+`-mmulticore'
Build a standalone application for multicore Blackfin processors.
This option causes proper start files and link scripts supporting
- multicore to be used, and defines the macro '__BFIN_MULTICORE'. It
- can only be used with '-mcpu=bf561[-SIREVISION]'.
+ multicore to be used, and defines the macro `__BFIN_MULTICORE'.
+ It can only be used with `-mcpu=bf561[-SIREVISION]'.
- This option can be used with '-mcorea' or '-mcoreb', which selects
- the one-application-per-core programming model. Without '-mcorea'
- or '-mcoreb', the single-application/dual-core programming model is
- used. In this model, the main function of Core B should be named
- as 'coreb_main'.
+ This option can be used with `-mcorea' or `-mcoreb', which selects
+ the one-application-per-core programming model. Without `-mcorea'
+ or `-mcoreb', the single-application/dual-core programming model
+ is used. In this model, the main function of Core B should be
+ named as `coreb_main'.
If this option is not used, the single-core application programming
model is used.
-'-mcorea'
+`-mcorea'
Build a standalone application for Core A of BF561 when using the
- one-application-per-core programming model. Proper start files and
+ one-application-per-core programming model. Proper start files and
link scripts are used to support Core A, and the macro
- '__BFIN_COREA' is defined. This option can only be used in
- conjunction with '-mmulticore'.
+ `__BFIN_COREA' is defined. This option can only be used in
+ conjunction with `-mmulticore'.
-'-mcoreb'
+`-mcoreb'
Build a standalone application for Core B of BF561 when using the
- one-application-per-core programming model. Proper start files and
+ one-application-per-core programming model. Proper start files and
link scripts are used to support Core B, and the macro
- '__BFIN_COREB' is defined. When this option is used, 'coreb_main'
- should be used instead of 'main'. This option can only be used in
- conjunction with '-mmulticore'.
+ `__BFIN_COREB' is defined. When this option is used, `coreb_main'
+ should be used instead of `main'. This option can only be used in
+ conjunction with `-mmulticore'.
-'-msdram'
+`-msdram'
Build a standalone application for SDRAM. Proper start files and
link scripts are used to put the application into SDRAM, and the
- macro '__BFIN_SDRAM' is defined. The loader should initialize
+ macro `__BFIN_SDRAM' is defined. The loader should initialize
SDRAM before loading the application.
-'-micplb'
+`-micplb'
Assume that ICPLBs are enabled at run time. This has an effect on
certain anomaly workarounds. For Linux targets, the default is to
assume ICPLBs are enabled; for standalone applications the default
@@ -13585,40 +13693,40 @@ File: gcc.info, Node: C6X Options, Next: CRIS Options, Prev: Blackfin Options
3.17.7 C6X Options
------------------
-'-march=NAME'
+`-march=NAME'
This specifies the name of the target architecture. GCC uses this
name to determine what kind of instructions it can emit when
- generating assembly code. Permissible names are: 'c62x', 'c64x',
- 'c64x+', 'c67x', 'c67x+', 'c674x'.
+ generating assembly code. Permissible names are: `c62x', `c64x',
+ `c64x+', `c67x', `c67x+', `c674x'.
-'-mbig-endian'
+`-mbig-endian'
Generate code for a big-endian target.
-'-mlittle-endian'
+`-mlittle-endian'
Generate code for a little-endian target. This is the default.
-'-msim'
+`-msim'
Choose startup files and linker script suitable for the simulator.
-'-msdata=default'
- Put small global and static data in the '.neardata' section, which
- is pointed to by register 'B14'. Put small uninitialized global
- and static data in the '.bss' section, which is adjacent to the
- '.neardata' section. Put small read-only data into the '.rodata'
+`-msdata=default'
+ Put small global and static data in the `.neardata' section, which
+ is pointed to by register `B14'. Put small uninitialized global
+ and static data in the `.bss' section, which is adjacent to the
+ `.neardata' section. Put small read-only data into the `.rodata'
section. The corresponding sections used for large pieces of data
- are '.fardata', '.far' and '.const'.
+ are `.fardata', `.far' and `.const'.
-'-msdata=all'
+`-msdata=all'
Put all data, not just small objects, into the sections reserved
- for small data, and use addressing relative to the 'B14' register
+ for small data, and use addressing relative to the `B14' register
to access them.
-'-msdata=none'
+`-msdata=none'
Make no use of the sections reserved for small data, and use
absolute addresses to access all data. Put all initialized global
- and static data in the '.fardata' section, and all uninitialized
- data in the '.far' section. Put all constant data into the
- '.const' section.
+ and static data in the `.fardata' section, and all uninitialized
+ data in the `.far' section. Put all constant data into the
+ `.const' section.

File: gcc.info, Node: CRIS Options, Next: CR16 Options, Prev: C6X Options, Up: Submodel Options
@@ -13628,99 +13736,100 @@ File: gcc.info, Node: CRIS Options, Next: CR16 Options, Prev: C6X Options, U
These options are defined specifically for the CRIS ports.
-'-march=ARCHITECTURE-TYPE'
-'-mcpu=ARCHITECTURE-TYPE'
+`-march=ARCHITECTURE-TYPE'
+`-mcpu=ARCHITECTURE-TYPE'
Generate code for the specified architecture. The choices for
- ARCHITECTURE-TYPE are 'v3', 'v8' and 'v10' for respectively
- ETRAX 4, ETRAX 100, and ETRAX 100 LX. Default is 'v0' except for
- cris-axis-linux-gnu, where the default is 'v10'.
+ ARCHITECTURE-TYPE are `v3', `v8' and `v10' for respectively
+ ETRAX 4, ETRAX 100, and ETRAX 100 LX. Default is `v0' except for
+ cris-axis-linux-gnu, where the default is `v10'.
-'-mtune=ARCHITECTURE-TYPE'
+`-mtune=ARCHITECTURE-TYPE'
Tune to ARCHITECTURE-TYPE everything applicable about the generated
code, except for the ABI and the set of available instructions.
The choices for ARCHITECTURE-TYPE are the same as for
- '-march=ARCHITECTURE-TYPE'.
+ `-march=ARCHITECTURE-TYPE'.
-'-mmax-stack-frame=N'
+`-mmax-stack-frame=N'
Warn when the stack frame of a function exceeds N bytes.
-'-metrax4'
-'-metrax100'
- The options '-metrax4' and '-metrax100' are synonyms for
- '-march=v3' and '-march=v8' respectively.
+`-metrax4'
+`-metrax100'
+ The options `-metrax4' and `-metrax100' are synonyms for
+ `-march=v3' and `-march=v8' respectively.
-'-mmul-bug-workaround'
-'-mno-mul-bug-workaround'
- Work around a bug in the 'muls' and 'mulu' instructions for CPU
+`-mmul-bug-workaround'
+`-mno-mul-bug-workaround'
+ Work around a bug in the `muls' and `mulu' instructions for CPU
models where it applies. This option is active by default.
-'-mpdebug'
+`-mpdebug'
Enable CRIS-specific verbose debug-related information in the
assembly code. This option also has the effect of turning off the
- '#NO_APP' formatted-code indicator to the assembler at the
+ `#NO_APP' formatted-code indicator to the assembler at the
beginning of the assembly file.
-'-mcc-init'
- Do not use condition-code results from previous instruction; always
- emit compare and test instructions before use of condition codes.
+`-mcc-init'
+ Do not use condition-code results from previous instruction;
+ always emit compare and test instructions before use of condition
+ codes.
-'-mno-side-effects'
+`-mno-side-effects'
Do not emit instructions with side effects in addressing modes
other than post-increment.
-'-mstack-align'
-'-mno-stack-align'
-'-mdata-align'
-'-mno-data-align'
-'-mconst-align'
-'-mno-const-align'
- These options ('no-' options) arrange (eliminate arrangements) for
+`-mstack-align'
+`-mno-stack-align'
+`-mdata-align'
+`-mno-data-align'
+`-mconst-align'
+`-mno-const-align'
+ These options (`no-' options) arrange (eliminate arrangements) for
the stack frame, individual data and constants to be aligned for
the maximum single data access size for the chosen CPU model. The
default is to arrange for 32-bit alignment. ABI details such as
structure layout are not affected by these options.
-'-m32-bit'
-'-m16-bit'
-'-m8-bit'
+`-m32-bit'
+`-m16-bit'
+`-m8-bit'
Similar to the stack- data- and const-align options above, these
- options arrange for stack frame, writable data and constants to all
- be 32-bit, 16-bit or 8-bit aligned. The default is 32-bit
+ options arrange for stack frame, writable data and constants to
+ all be 32-bit, 16-bit or 8-bit aligned. The default is 32-bit
alignment.
-'-mno-prologue-epilogue'
-'-mprologue-epilogue'
- With '-mno-prologue-epilogue', the normal function prologue and
+`-mno-prologue-epilogue'
+`-mprologue-epilogue'
+ With `-mno-prologue-epilogue', the normal function prologue and
epilogue which set up the stack frame are omitted and no return
instructions or return sequences are generated in the code. Use
this option only together with visual inspection of the compiled
- code: no warnings or errors are generated when call-saved registers
- must be saved, or storage for local variables needs to be
- allocated.
+ code: no warnings or errors are generated when call-saved
+ registers must be saved, or storage for local variables needs to
+ be allocated.
-'-mno-gotplt'
-'-mgotplt'
- With '-fpic' and '-fPIC', don't generate (do generate) instruction
+`-mno-gotplt'
+`-mgotplt'
+ With `-fpic' and `-fPIC', don't generate (do generate) instruction
sequences that load addresses for functions from the PLT part of
the GOT rather than (traditional on other architectures) calls to
- the PLT. The default is '-mgotplt'.
+ the PLT. The default is `-mgotplt'.
-'-melf'
+`-melf'
Legacy no-op option only recognized with the cris-axis-elf and
cris-axis-linux-gnu targets.
-'-mlinux'
+`-mlinux'
Legacy no-op option only recognized with the cris-axis-linux-gnu
target.
-'-sim'
+`-sim'
This option, recognized for the cris-axis-elf, arranges to link
with input-output functions from a simulator library. Code,
initialized data and zero-initialized data are allocated
consecutively.
-'-sim2'
- Like '-sim', but pass linker options to locate initialized data at
+`-sim2'
+ Like `-sim', but pass linker options to locate initialized data at
0x40000000 and zero-initialized data at 0x80000000.

@@ -13731,29 +13840,29 @@ File: gcc.info, Node: CR16 Options, Next: Darwin Options, Prev: CRIS Options,
These options are defined specifically for the CR16 ports.
-'-mmac'
- Enable the use of multiply-accumulate instructions. Disabled by
+`-mmac'
+ Enable the use of multiply-accumulate instructions. Disabled by
default.
-'-mcr16cplus'
-'-mcr16c'
- Generate code for CR16C or CR16C+ architecture. CR16C+
- architecture is default.
+`-mcr16cplus'
+`-mcr16c'
+ Generate code for CR16C or CR16C+ architecture. CR16C+ architecture
+ is default.
-'-msim'
+`-msim'
Links the library libsim.a which is in compatible with simulator.
Applicable to ELF compiler only.
-'-mint32'
+`-mint32'
Choose integer type as 32-bit wide.
-'-mbit-ops'
- Generates 'sbit'/'cbit' instructions for bit manipulations.
+`-mbit-ops'
+ Generates `sbit'/`cbit' instructions for bit manipulations.
-'-mdata-model=MODEL'
- Choose a data model. The choices for MODEL are 'near', 'far' or
- 'medium'. 'medium' is default. However, 'far' is not valid with
- '-mcr16c', as the CR16C architecture does not support the far data
+`-mdata-model=MODEL'
+ Choose a data model. The choices for MODEL are `near', `far' or
+ `medium'. `medium' is default. However, `far' is not valid with
+ `-mcr16c', as the CR16C architecture does not support the far data
model.

@@ -13767,39 +13876,39 @@ operating system.
FSF GCC on Darwin does not create "fat" object files; it creates an
object file for the single architecture that GCC was built to target.
-Apple's GCC on Darwin does create "fat" files if multiple '-arch'
+Apple's GCC on Darwin does create "fat" files if multiple `-arch'
options are used; it does so by running the compiler or linker multiple
-times and joining the results together with 'lipo'.
+times and joining the results together with `lipo'.
- The subtype of the file created (like 'ppc7400' or 'ppc970' or 'i686')
+ The subtype of the file created (like `ppc7400' or `ppc970' or `i686')
is determined by the flags that specify the ISA that GCC is targeting,
-like '-mcpu' or '-march'. The '-force_cpusubtype_ALL' option can be
+like `-mcpu' or `-march'. The `-force_cpusubtype_ALL' option can be
used to override this.
The Darwin tools vary in their behavior when presented with an ISA
-mismatch. The assembler, 'as', only permits instructions to be used
+mismatch. The assembler, `as', only permits instructions to be used
that are valid for the subtype of the file it is generating, so you
-cannot put 64-bit instructions in a 'ppc750' object file. The linker
-for shared libraries, '/usr/bin/libtool', fails and prints an error if
+cannot put 64-bit instructions in a `ppc750' object file. The linker
+for shared libraries, `/usr/bin/libtool', fails and prints an error if
asked to create a shared library with a less restrictive subtype than
-its input files (for instance, trying to put a 'ppc970' object file in a
-'ppc7400' library). The linker for executables, 'ld', quietly gives the
-executable the most restrictive subtype of any of its input files.
+its input files (for instance, trying to put a `ppc970' object file in
+a `ppc7400' library). The linker for executables, `ld', quietly gives
+the executable the most restrictive subtype of any of its input files.
-'-FDIR'
+`-FDIR'
Add the framework directory DIR to the head of the list of
directories to be searched for header files. These directories are
- interleaved with those specified by '-I' options and are scanned in
- a left-to-right order.
+ interleaved with those specified by `-I' options and are scanned
+ in a left-to-right order.
A framework directory is a directory with frameworks in it. A
- framework is a directory with a 'Headers' and/or 'PrivateHeaders'
- directory contained directly in it that ends in '.framework'. The
+ framework is a directory with a `Headers' and/or `PrivateHeaders'
+ directory contained directly in it that ends in `.framework'. The
name of a framework is the name of this directory excluding the
- '.framework'. Headers associated with the framework are found in
- one of those two directories, with 'Headers' being searched first.
+ `.framework'. Headers associated with the framework are found in
+ one of those two directories, with `Headers' being searched first.
A subframework is a framework directory that is in a framework's
- 'Frameworks' directory. Includes of subframework headers can only
+ `Frameworks' directory. Includes of subframework headers can only
appear in a header of a framework that contains the subframework,
or in a sibling subframework header. Two subframeworks are
siblings if they occur in the same framework. A subframework
@@ -13807,151 +13916,151 @@ executable the most restrictive subtype of any of its input files.
if this is violated. Currently a subframework cannot have
subframeworks; in the future, the mechanism may be extended to
support this. The standard frameworks can be found in
- '/System/Library/Frameworks' and '/Library/Frameworks'. An example
- include looks like '#include <Framework/header.h>', where
- 'Framework' denotes the name of the framework and 'header.h' is
- found in the 'PrivateHeaders' or 'Headers' directory.
-
-'-iframeworkDIR'
- Like '-F' except the directory is a treated as a system directory.
- The main difference between this '-iframework' and '-F' is that
- with '-iframework' the compiler does not warn about constructs
+ `/System/Library/Frameworks' and `/Library/Frameworks'. An
+ example include looks like `#include <Framework/header.h>', where
+ `Framework' denotes the name of the framework and `header.h' is
+ found in the `PrivateHeaders' or `Headers' directory.
+
+`-iframeworkDIR'
+ Like `-F' except the directory is a treated as a system directory.
+ The main difference between this `-iframework' and `-F' is that
+ with `-iframework' the compiler does not warn about constructs
contained within header files found via DIR. This option is valid
only for the C family of languages.
-'-gused'
+`-gused'
Emit debugging information for symbols that are used. For stabs
- debugging format, this enables '-feliminate-unused-debug-symbols'.
+ debugging format, this enables `-feliminate-unused-debug-symbols'.
This is by default ON.
-'-gfull'
+`-gfull'
Emit debugging information for all symbols and types.
-'-mmacosx-version-min=VERSION'
- The earliest version of MacOS X that this executable will run on is
- VERSION. Typical values of VERSION include '10.1', '10.2', and
- '10.3.9'.
+`-mmacosx-version-min=VERSION'
+ The earliest version of MacOS X that this executable will run on
+ is VERSION. Typical values of VERSION include `10.1', `10.2', and
+ `10.3.9'.
If the compiler was built to use the system's headers by default,
then the default for this option is the system version on which the
compiler is running, otherwise the default is to make choices that
are compatible with as many systems and code bases as possible.
-'-mkernel'
- Enable kernel development mode. The '-mkernel' option sets
- '-static', '-fno-common', '-fno-use-cxa-atexit', '-fno-exceptions',
- '-fno-non-call-exceptions', '-fapple-kext', '-fno-weak' and
- '-fno-rtti' where applicable. This mode also sets '-mno-altivec',
- '-msoft-float', '-fno-builtin' and '-mlong-branch' for PowerPC
- targets.
-
-'-mone-byte-bool'
- Override the defaults for 'bool' so that 'sizeof(bool)==1'. By
- default 'sizeof(bool)' is '4' when compiling for Darwin/PowerPC and
- '1' when compiling for Darwin/x86, so this option has no effect on
- x86.
-
- *Warning:* The '-mone-byte-bool' switch causes GCC to generate code
- that is not binary compatible with code generated without that
- switch. Using this switch may require recompiling all other
+`-mkernel'
+ Enable kernel development mode. The `-mkernel' option sets
+ `-static', `-fno-common', `-fno-use-cxa-atexit',
+ `-fno-exceptions', `-fno-non-call-exceptions', `-fapple-kext',
+ `-fno-weak' and `-fno-rtti' where applicable. This mode also sets
+ `-mno-altivec', `-msoft-float', `-fno-builtin' and `-mlong-branch'
+ for PowerPC targets.
+
+`-mone-byte-bool'
+ Override the defaults for `bool' so that `sizeof(bool)==1'. By
+ default `sizeof(bool)' is `4' when compiling for Darwin/PowerPC
+ and `1' when compiling for Darwin/x86, so this option has no
+ effect on x86.
+
+ *Warning:* The `-mone-byte-bool' switch causes GCC to generate
+ code that is not binary compatible with code generated without
+ that switch. Using this switch may require recompiling all other
modules in a program, including system libraries. Use this switch
to conform to a non-default data model.
-'-mfix-and-continue'
-'-ffix-and-continue'
-'-findirect-data'
+`-mfix-and-continue'
+`-ffix-and-continue'
+`-findirect-data'
Generate code suitable for fast turnaround development, such as to
- allow GDB to dynamically load '.o' files into already-running
- programs. '-findirect-data' and '-ffix-and-continue' are provided
+ allow GDB to dynamically load `.o' files into already-running
+ programs. `-findirect-data' and `-ffix-and-continue' are provided
for backwards compatibility.
-'-all_load'
+`-all_load'
Loads all members of static archive libraries. See man ld(1) for
more information.
-'-arch_errors_fatal'
+`-arch_errors_fatal'
Cause the errors having to do with files that have the wrong
architecture to be fatal.
-'-bind_at_load'
+`-bind_at_load'
Causes the output file to be marked such that the dynamic linker
will bind all undefined references when the file is loaded or
launched.
-'-bundle'
+`-bundle'
Produce a Mach-o bundle format file. See man ld(1) for more
information.
-'-bundle_loader EXECUTABLE'
+`-bundle_loader EXECUTABLE'
This option specifies the EXECUTABLE that will load the build
output file being linked. See man ld(1) for more information.
-'-dynamiclib'
+`-dynamiclib'
When passed this option, GCC produces a dynamic library instead of
- an executable when linking, using the Darwin 'libtool' command.
-
-'-force_cpusubtype_ALL'
- This causes GCC's output file to have the 'ALL' subtype, instead of
- one controlled by the '-mcpu' or '-march' option.
-
-'-allowable_client CLIENT_NAME'
-'-client_name'
-'-compatibility_version'
-'-current_version'
-'-dead_strip'
-'-dependency-file'
-'-dylib_file'
-'-dylinker_install_name'
-'-dynamic'
-'-exported_symbols_list'
-'-filelist'
-'-flat_namespace'
-'-force_flat_namespace'
-'-headerpad_max_install_names'
-'-image_base'
-'-init'
-'-install_name'
-'-keep_private_externs'
-'-multi_module'
-'-multiply_defined'
-'-multiply_defined_unused'
-'-noall_load'
-'-no_dead_strip_inits_and_terms'
-'-nofixprebinding'
-'-nomultidefs'
-'-noprebind'
-'-noseglinkedit'
-'-pagezero_size'
-'-prebind'
-'-prebind_all_twolevel_modules'
-'-private_bundle'
-'-read_only_relocs'
-'-sectalign'
-'-sectobjectsymbols'
-'-whyload'
-'-seg1addr'
-'-sectcreate'
-'-sectobjectsymbols'
-'-sectorder'
-'-segaddr'
-'-segs_read_only_addr'
-'-segs_read_write_addr'
-'-seg_addr_table'
-'-seg_addr_table_filename'
-'-seglinkedit'
-'-segprot'
-'-segs_read_only_addr'
-'-segs_read_write_addr'
-'-single_module'
-'-static'
-'-sub_library'
-'-sub_umbrella'
-'-twolevel_namespace'
-'-umbrella'
-'-undefined'
-'-unexported_symbols_list'
-'-weak_reference_mismatches'
-'-whatsloaded'
+ an executable when linking, using the Darwin `libtool' command.
+
+`-force_cpusubtype_ALL'
+ This causes GCC's output file to have the `ALL' subtype, instead of
+ one controlled by the `-mcpu' or `-march' option.
+
+`-allowable_client CLIENT_NAME'
+`-client_name'
+`-compatibility_version'
+`-current_version'
+`-dead_strip'
+`-dependency-file'
+`-dylib_file'
+`-dylinker_install_name'
+`-dynamic'
+`-exported_symbols_list'
+`-filelist'
+`-flat_namespace'
+`-force_flat_namespace'
+`-headerpad_max_install_names'
+`-image_base'
+`-init'
+`-install_name'
+`-keep_private_externs'
+`-multi_module'
+`-multiply_defined'
+`-multiply_defined_unused'
+`-noall_load'
+`-no_dead_strip_inits_and_terms'
+`-nofixprebinding'
+`-nomultidefs'
+`-noprebind'
+`-noseglinkedit'
+`-pagezero_size'
+`-prebind'
+`-prebind_all_twolevel_modules'
+`-private_bundle'
+`-read_only_relocs'
+`-sectalign'
+`-sectobjectsymbols'
+`-whyload'
+`-seg1addr'
+`-sectcreate'
+`-sectobjectsymbols'
+`-sectorder'
+`-segaddr'
+`-segs_read_only_addr'
+`-segs_read_write_addr'
+`-seg_addr_table'
+`-seg_addr_table_filename'
+`-seglinkedit'
+`-segprot'
+`-segs_read_only_addr'
+`-segs_read_write_addr'
+`-single_module'
+`-static'
+`-sub_library'
+`-sub_umbrella'
+`-twolevel_namespace'
+`-umbrella'
+`-undefined'
+`-unexported_symbols_list'
+`-weak_reference_mismatches'
+`-whatsloaded'
These options are passed to the Darwin linker. The Darwin linker
man page describes them in detail.
@@ -13961,143 +14070,143 @@ File: gcc.info, Node: DEC Alpha Options, Next: FR30 Options, Prev: Darwin Opt
3.17.11 DEC Alpha Options
-------------------------
-These '-m' options are defined for the DEC Alpha implementations:
+These `-m' options are defined for the DEC Alpha implementations:
-'-mno-soft-float'
-'-msoft-float'
+`-mno-soft-float'
+`-msoft-float'
Use (do not use) the hardware floating-point instructions for
- floating-point operations. When '-msoft-float' is specified,
- functions in 'libgcc.a' are used to perform floating-point
+ floating-point operations. When `-msoft-float' is specified,
+ functions in `libgcc.a' are used to perform floating-point
operations. Unless they are replaced by routines that emulate the
floating-point operations, or compiled in such a way as to call
such emulations routines, these routines issue floating-point
- operations. If you are compiling for an Alpha without
+ operations. If you are compiling for an Alpha without
floating-point operations, you must ensure that the library is
built so as not to call them.
Note that Alpha implementations without floating-point operations
are required to have floating-point registers.
-'-mfp-reg'
-'-mno-fp-regs'
+`-mfp-reg'
+`-mno-fp-regs'
Generate code that uses (does not use) the floating-point register
- set. '-mno-fp-regs' implies '-msoft-float'. If the floating-point
+ set. `-mno-fp-regs' implies `-msoft-float'. If the floating-point
register set is not used, floating-point operands are passed in
integer registers as if they were integers and floating-point
- results are passed in '$0' instead of '$f0'. This is a
+ results are passed in `$0' instead of `$f0'. This is a
non-standard calling sequence, so any function with a
floating-point argument or return value called by code compiled
- with '-mno-fp-regs' must also be compiled with that option.
+ with `-mno-fp-regs' must also be compiled with that option.
A typical use of this option is building a kernel that does not
use, and hence need not save and restore, any floating-point
registers.
-'-mieee'
- The Alpha architecture implements floating-point hardware optimized
- for maximum performance. It is mostly compliant with the IEEE
- floating-point standard. However, for full compliance, software
- assistance is required. This option generates code fully
+`-mieee'
+ The Alpha architecture implements floating-point hardware
+ optimized for maximum performance. It is mostly compliant with
+ the IEEE floating-point standard. However, for full compliance,
+ software assistance is required. This option generates code fully
IEEE-compliant code _except_ that the INEXACT-FLAG is not
maintained (see below). If this option is turned on, the
- preprocessor macro '_IEEE_FP' is defined during compilation. The
+ preprocessor macro `_IEEE_FP' is defined during compilation. The
resulting code is less efficient but is able to correctly support
denormalized numbers and exceptional IEEE values such as
not-a-number and plus/minus infinity. Other Alpha compilers call
- this option '-ieee_with_no_inexact'.
+ this option `-ieee_with_no_inexact'.
-'-mieee-with-inexact'
- This is like '-mieee' except the generated code also maintains the
+`-mieee-with-inexact'
+ This is like `-mieee' except the generated code also maintains the
IEEE INEXACT-FLAG. Turning on this option causes the generated
code to implement fully-compliant IEEE math. In addition to
- '_IEEE_FP', '_IEEE_FP_EXACT' is defined as a preprocessor macro.
+ `_IEEE_FP', `_IEEE_FP_EXACT' is defined as a preprocessor macro.
On some Alpha implementations the resulting code may execute
significantly slower than the code generated by default. Since
there is very little code that depends on the INEXACT-FLAG, you
should normally not specify this option. Other Alpha compilers
- call this option '-ieee_with_inexact'.
+ call this option `-ieee_with_inexact'.
-'-mfp-trap-mode=TRAP-MODE'
+`-mfp-trap-mode=TRAP-MODE'
This option controls what floating-point related traps are enabled.
- Other Alpha compilers call this option '-fptm TRAP-MODE'. The trap
- mode can be set to one of four values:
+ Other Alpha compilers call this option `-fptm TRAP-MODE'. The
+ trap mode can be set to one of four values:
- 'n'
- This is the default (normal) setting. The only traps that are
- enabled are the ones that cannot be disabled in software
+ `n'
+ This is the default (normal) setting. The only traps that
+ are enabled are the ones that cannot be disabled in software
(e.g., division by zero trap).
- 'u'
- In addition to the traps enabled by 'n', underflow traps are
+ `u'
+ In addition to the traps enabled by `n', underflow traps are
enabled as well.
- 'su'
- Like 'u', but the instructions are marked to be safe for
+ `su'
+ Like `u', but the instructions are marked to be safe for
software completion (see Alpha architecture manual for
details).
- 'sui'
- Like 'su', but inexact traps are enabled as well.
+ `sui'
+ Like `su', but inexact traps are enabled as well.
-'-mfp-rounding-mode=ROUNDING-MODE'
+`-mfp-rounding-mode=ROUNDING-MODE'
Selects the IEEE rounding mode. Other Alpha compilers call this
- option '-fprm ROUNDING-MODE'. The ROUNDING-MODE can be one of:
+ option `-fprm ROUNDING-MODE'. The ROUNDING-MODE can be one of:
- 'n'
- Normal IEEE rounding mode. Floating-point numbers are rounded
- towards the nearest machine number or towards the even machine
- number in case of a tie.
+ `n'
+ Normal IEEE rounding mode. Floating-point numbers are
+ rounded towards the nearest machine number or towards the
+ even machine number in case of a tie.
- 'm'
+ `m'
Round towards minus infinity.
- 'c'
+ `c'
Chopped rounding mode. Floating-point numbers are rounded
towards zero.
- 'd'
+ `d'
Dynamic rounding mode. A field in the floating-point control
register (FPCR, see Alpha architecture reference manual)
controls the rounding mode in effect. The C library
initializes this register for rounding towards plus infinity.
- Thus, unless your program modifies the FPCR, 'd' corresponds
+ Thus, unless your program modifies the FPCR, `d' corresponds
to round towards plus infinity.
-'-mtrap-precision=TRAP-PRECISION'
+`-mtrap-precision=TRAP-PRECISION'
In the Alpha architecture, floating-point traps are imprecise.
This means without software assistance it is impossible to recover
from a floating trap and program execution normally needs to be
- terminated. GCC can generate code that can assist operating system
- trap handlers in determining the exact location that caused a
- floating-point trap. Depending on the requirements of an
+ terminated. GCC can generate code that can assist operating
+ system trap handlers in determining the exact location that caused
+ a floating-point trap. Depending on the requirements of an
application, different levels of precisions can be selected:
- 'p'
+ `p'
Program precision. This option is the default and means a
trap handler can only identify which program caused a
floating-point exception.
- 'f'
+ `f'
Function precision. The trap handler can determine the
function that caused a floating-point exception.
- 'i'
+ `i'
Instruction precision. The trap handler can determine the
exact instruction that caused a floating-point exception.
Other Alpha compilers provide the equivalent options called
- '-scope_safe' and '-resumption_safe'.
+ `-scope_safe' and `-resumption_safe'.
-'-mieee-conformant'
+`-mieee-conformant'
This option marks the generated code as IEEE conformant. You must
- not use this option unless you also specify '-mtrap-precision=i'
- and either '-mfp-trap-mode=su' or '-mfp-trap-mode=sui'. Its only
- effect is to emit the line '.eflag 48' in the function prologue of
+ not use this option unless you also specify `-mtrap-precision=i'
+ and either `-mfp-trap-mode=su' or `-mfp-trap-mode=sui'. Its only
+ effect is to emit the line `.eflag 48' in the function prologue of
the generated assembly file.
-'-mbuild-constants'
- Normally GCC examines a 32- or 64-bit integer constant to see if it
- can construct it from smaller constants in two or three
+`-mbuild-constants'
+ Normally GCC examines a 32- or 64-bit integer constant to see if
+ it can construct it from smaller constants in two or three
instructions. If it cannot, it outputs the constant as a literal
and generates code to load it from the data segment at run time.
@@ -14110,138 +14219,139 @@ These '-m' options are defined for the DEC Alpha implementations:
before it can find the variables and constants in its own data
segment.
-'-mbwx'
-'-mno-bwx'
-'-mcix'
-'-mno-cix'
-'-mfix'
-'-mno-fix'
-'-mmax'
-'-mno-max'
+`-mbwx'
+`-mno-bwx'
+`-mcix'
+`-mno-cix'
+`-mfix'
+`-mno-fix'
+`-mmax'
+`-mno-max'
Indicate whether GCC should generate code to use the optional BWX,
CIX, FIX and MAX instruction sets. The default is to use the
- instruction sets supported by the CPU type specified via '-mcpu='
+ instruction sets supported by the CPU type specified via `-mcpu='
option or that of the CPU on which GCC was built if none is
specified.
-'-mfloat-vax'
-'-mfloat-ieee'
+`-mfloat-vax'
+`-mfloat-ieee'
Generate code that uses (does not use) VAX F and G floating-point
arithmetic instead of IEEE single and double precision.
-'-mexplicit-relocs'
-'-mno-explicit-relocs'
+`-mexplicit-relocs'
+`-mno-explicit-relocs'
Older Alpha assemblers provided no way to generate symbol
relocations except via assembler macros. Use of these macros does
not allow optimal instruction scheduling. GNU binutils as of
version 2.12 supports a new syntax that allows the compiler to
explicitly mark which relocations should apply to which
instructions. This option is mostly useful for debugging, as GCC
- detects the capabilities of the assembler when it is built and sets
- the default accordingly.
+ detects the capabilities of the assembler when it is built and
+ sets the default accordingly.
-'-msmall-data'
-'-mlarge-data'
- When '-mexplicit-relocs' is in effect, static data is accessed via
- "gp-relative" relocations. When '-msmall-data' is used, objects 8
+`-msmall-data'
+`-mlarge-data'
+ When `-mexplicit-relocs' is in effect, static data is accessed via
+ "gp-relative" relocations. When `-msmall-data' is used, objects 8
bytes long or smaller are placed in a "small data area" (the
- '.sdata' and '.sbss' sections) and are accessed via 16-bit
- relocations off of the '$gp' register. This limits the size of the
- small data area to 64KB, but allows the variables to be directly
- accessed via a single instruction.
+ `.sdata' and `.sbss' sections) and are accessed via 16-bit
+ relocations off of the `$gp' register. This limits the size of
+ the small data area to 64KB, but allows the variables to be
+ directly accessed via a single instruction.
- The default is '-mlarge-data'. With this option the data area is
+ The default is `-mlarge-data'. With this option the data area is
limited to just below 2GB. Programs that require more than 2GB of
- data must use 'malloc' or 'mmap' to allocate the data in the heap
+ data must use `malloc' or `mmap' to allocate the data in the heap
instead of in the program's data segment.
- When generating code for shared libraries, '-fpic' implies
- '-msmall-data' and '-fPIC' implies '-mlarge-data'.
+ When generating code for shared libraries, `-fpic' implies
+ `-msmall-data' and `-fPIC' implies `-mlarge-data'.
-'-msmall-text'
-'-mlarge-text'
- When '-msmall-text' is used, the compiler assumes that the code of
+`-msmall-text'
+`-mlarge-text'
+ When `-msmall-text' is used, the compiler assumes that the code of
the entire program (or shared library) fits in 4MB, and is thus
- reachable with a branch instruction. When '-msmall-data' is used,
- the compiler can assume that all local symbols share the same '$gp'
- value, and thus reduce the number of instructions required for a
- function call from 4 to 1.
+ reachable with a branch instruction. When `-msmall-data' is used,
+ the compiler can assume that all local symbols share the same
+ `$gp' value, and thus reduce the number of instructions required
+ for a function call from 4 to 1.
- The default is '-mlarge-text'.
+ The default is `-mlarge-text'.
-'-mcpu=CPU_TYPE'
+`-mcpu=CPU_TYPE'
Set the instruction set and instruction scheduling parameters for
- machine type CPU_TYPE. You can specify either the 'EV' style name
+ machine type CPU_TYPE. You can specify either the `EV' style name
or the corresponding chip number. GCC supports scheduling
parameters for the EV4, EV5 and EV6 family of processors and
chooses the default values for the instruction set from the
- processor you specify. If you do not specify a processor type, GCC
- defaults to the processor on which the compiler was built.
+ processor you specify. If you do not specify a processor type,
+ GCC defaults to the processor on which the compiler was built.
Supported values for CPU_TYPE are
- 'ev4'
- 'ev45'
- '21064'
+ `ev4'
+ `ev45'
+ `21064'
Schedules as an EV4 and has no instruction set extensions.
- 'ev5'
- '21164'
+ `ev5'
+ `21164'
Schedules as an EV5 and has no instruction set extensions.
- 'ev56'
- '21164a'
+ `ev56'
+ `21164a'
Schedules as an EV5 and supports the BWX extension.
- 'pca56'
- '21164pc'
- '21164PC'
+ `pca56'
+ `21164pc'
+ `21164PC'
Schedules as an EV5 and supports the BWX and MAX extensions.
- 'ev6'
- '21264'
+ `ev6'
+ `21264'
Schedules as an EV6 and supports the BWX, FIX, and MAX
extensions.
- 'ev67'
- '21264a'
+ `ev67'
+ `21264a'
Schedules as an EV6 and supports the BWX, CIX, FIX, and MAX
extensions.
- Native toolchains also support the value 'native', which selects
+ Native toolchains also support the value `native', which selects
the best architecture option for the host processor.
- '-mcpu=native' has no effect if GCC does not recognize the
+ `-mcpu=native' has no effect if GCC does not recognize the
processor.
-'-mtune=CPU_TYPE'
+`-mtune=CPU_TYPE'
Set only the instruction scheduling parameters for machine type
CPU_TYPE. The instruction set is not changed.
- Native toolchains also support the value 'native', which selects
+ Native toolchains also support the value `native', which selects
the best architecture option for the host processor.
- '-mtune=native' has no effect if GCC does not recognize the
+ `-mtune=native' has no effect if GCC does not recognize the
processor.
-'-mmemory-latency=TIME'
+`-mmemory-latency=TIME'
Sets the latency the scheduler should assume for typical memory
references as seen by the application. This number is highly
- dependent on the memory access patterns used by the application and
- the size of the external cache on the machine.
+ dependent on the memory access patterns used by the application
+ and the size of the external cache on the machine.
Valid options for TIME are
- 'NUMBER'
+ `NUMBER'
A decimal number representing clock cycles.
- 'L1'
- 'L2'
- 'L3'
- 'main'
+ `L1'
+ `L2'
+ `L3'
+ `main'
The compiler contains estimates of the number of clock cycles
for "typical" EV4 & EV5 hardware for the Level 1, 2 & 3 caches
(also called Dcache, Scache, and Bcache), as well as to main
memory. Note that L3 is only valid for EV5.
+

File: gcc.info, Node: FR30 Options, Next: FRV Options, Prev: DEC Alpha Options, Up: Submodel Options
@@ -14250,278 +14360,233 @@ File: gcc.info, Node: FR30 Options, Next: FRV Options, Prev: DEC Alpha Option
These options are defined specifically for the FR30 port.
-'-msmall-model'
+`-msmall-model'
Use the small address space model. This can produce smaller code,
but it does assume that all symbolic values and addresses fit into
a 20-bit range.
-'-mno-lsim'
+`-mno-lsim'
Assume that runtime support has been provided and so there is no
- need to include the simulator library ('libsim.a') on the linker
+ need to include the simulator library (`libsim.a') on the linker
command line.
+

File: gcc.info, Node: FRV Options, Next: GNU/Linux Options, Prev: FR30 Options, Up: Submodel Options
3.17.13 FRV Options
-------------------
-'-mgpr-32'
-
+`-mgpr-32'
Only use the first 32 general-purpose registers.
-'-mgpr-64'
-
+`-mgpr-64'
Use all 64 general-purpose registers.
-'-mfpr-32'
-
+`-mfpr-32'
Use only the first 32 floating-point registers.
-'-mfpr-64'
-
+`-mfpr-64'
Use all 64 floating-point registers.
-'-mhard-float'
-
+`-mhard-float'
Use hardware instructions for floating-point operations.
-'-msoft-float'
-
+`-msoft-float'
Use library routines for floating-point operations.
-'-malloc-cc'
-
+`-malloc-cc'
Dynamically allocate condition code registers.
-'-mfixed-cc'
-
+`-mfixed-cc'
Do not try to dynamically allocate condition code registers, only
- use 'icc0' and 'fcc0'.
-
-'-mdword'
+ use `icc0' and `fcc0'.
+`-mdword'
Change ABI to use double word insns.
-'-mno-dword'
-
+`-mno-dword'
Do not use double word instructions.
-'-mdouble'
-
+`-mdouble'
Use floating-point double instructions.
-'-mno-double'
-
+`-mno-double'
Do not use floating-point double instructions.
-'-mmedia'
-
+`-mmedia'
Use media instructions.
-'-mno-media'
-
+`-mno-media'
Do not use media instructions.
-'-mmuladd'
-
+`-mmuladd'
Use multiply and add/subtract instructions.
-'-mno-muladd'
-
+`-mno-muladd'
Do not use multiply and add/subtract instructions.
-'-mfdpic'
-
+`-mfdpic'
Select the FDPIC ABI, which uses function descriptors to represent
pointers to functions. Without any PIC/PIE-related options, it
- implies '-fPIE'. With '-fpic' or '-fpie', it assumes GOT entries
- and small data are within a 12-bit range from the GOT base address;
- with '-fPIC' or '-fPIE', GOT offsets are computed with 32 bits.
- With a 'bfin-elf' target, this option implies '-msim'.
-
-'-minline-plt'
+ implies `-fPIE'. With `-fpic' or `-fpie', it assumes GOT entries
+ and small data are within a 12-bit range from the GOT base
+ address; with `-fPIC' or `-fPIE', GOT offsets are computed with 32
+ bits. With a `bfin-elf' target, this option implies `-msim'.
+`-minline-plt'
Enable inlining of PLT entries in function calls to functions that
- are not known to bind locally. It has no effect without '-mfdpic'.
+ are not known to bind locally. It has no effect without `-mfdpic'.
It's enabled by default if optimizing for speed and compiling for
- shared libraries (i.e., '-fPIC' or '-fpic'), or when an
- optimization option such as '-O3' or above is present in the
+ shared libraries (i.e., `-fPIC' or `-fpic'), or when an
+ optimization option such as `-O3' or above is present in the
command line.
-'-mTLS'
-
+`-mTLS'
Assume a large TLS segment when generating thread-local code.
-'-mtls'
-
+`-mtls'
Do not assume a large TLS segment when generating thread-local
code.
-'-mgprel-ro'
-
- Enable the use of 'GPREL' relocations in the FDPIC ABI for data
+`-mgprel-ro'
+ Enable the use of `GPREL' relocations in the FDPIC ABI for data
that is known to be in read-only sections. It's enabled by
- default, except for '-fpic' or '-fpie': even though it may help
+ default, except for `-fpic' or `-fpie': even though it may help
make the global offset table smaller, it trades 1 instruction for
- 4. With '-fPIC' or '-fPIE', it trades 3 instructions for 4, one of
- which may be shared by multiple symbols, and it avoids the need for
- a GOT entry for the referenced symbol, so it's more likely to be a
- win. If it is not, '-mno-gprel-ro' can be used to disable it.
-
-'-multilib-library-pic'
+ 4. With `-fPIC' or `-fPIE', it trades 3 instructions for 4, one
+ of which may be shared by multiple symbols, and it avoids the need
+ for a GOT entry for the referenced symbol, so it's more likely to
+ be a win. If it is not, `-mno-gprel-ro' can be used to disable it.
+`-multilib-library-pic'
Link with the (library, not FD) pic libraries. It's implied by
- '-mlibrary-pic', as well as by '-fPIC' and '-fpic' without
- '-mfdpic'. You should never have to use it explicitly.
-
-'-mlinked-fp'
+ `-mlibrary-pic', as well as by `-fPIC' and `-fpic' without
+ `-mfdpic'. You should never have to use it explicitly.
+`-mlinked-fp'
Follow the EABI requirement of always creating a frame pointer
whenever a stack frame is allocated. This option is enabled by
- default and can be disabled with '-mno-linked-fp'.
-
-'-mlong-calls'
+ default and can be disabled with `-mno-linked-fp'.
+`-mlong-calls'
Use indirect addressing to call functions outside the current
compilation unit. This allows the functions to be placed anywhere
within the 32-bit address space.
-'-malign-labels'
-
+`-malign-labels'
Try to align labels to an 8-byte boundary by inserting NOPs into
the previous packet. This option only has an effect when VLIW
packing is enabled. It doesn't create new packets; it merely adds
NOPs to existing ones.
-'-mlibrary-pic'
-
+`-mlibrary-pic'
Generate position-independent EABI code.
-'-macc-4'
-
+`-macc-4'
Use only the first four media accumulator registers.
-'-macc-8'
-
+`-macc-8'
Use all eight media accumulator registers.
-'-mpack'
-
+`-mpack'
Pack VLIW instructions.
-'-mno-pack'
-
+`-mno-pack'
Do not pack VLIW instructions.
-'-mno-eflags'
-
+`-mno-eflags'
Do not mark ABI switches in e_flags.
-'-mcond-move'
-
+`-mcond-move'
Enable the use of conditional-move instructions (default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-cond-move'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mno-cond-move'
Disable the use of conditional-move instructions.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mscc'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mscc'
Enable the use of conditional set instructions (default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-scc'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mno-scc'
Disable the use of conditional set instructions.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mcond-exec'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mcond-exec'
Enable the use of conditional execution (default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-cond-exec'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mno-cond-exec'
Disable the use of conditional execution.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mvliw-branch'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mvliw-branch'
Run a pass to pack branches into VLIW instructions (default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-vliw-branch'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mno-vliw-branch'
Do not run a pass to pack branches into VLIW instructions.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
-'-mmulti-cond-exec'
-
- Enable optimization of '&&' and '||' in conditional execution
+`-mmulti-cond-exec'
+ Enable optimization of `&&' and `||' in conditional execution
(default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-multi-cond-exec'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
- Disable optimization of '&&' and '||' in conditional execution.
+`-mno-multi-cond-exec'
+ Disable optimization of `&&' and `||' in conditional execution.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mnested-cond-exec'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mnested-cond-exec'
Enable nested conditional execution optimizations (default).
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
-
-'-mno-nested-cond-exec'
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
+`-mno-nested-cond-exec'
Disable nested conditional execution optimizations.
- This switch is mainly for debugging the compiler and will likely be
- removed in a future version.
+ This switch is mainly for debugging the compiler and will likely
+ be removed in a future version.
-'-moptimize-membar'
-
- This switch removes redundant 'membar' instructions from the
+`-moptimize-membar'
+ This switch removes redundant `membar' instructions from the
compiler-generated code. It is enabled by default.
-'-mno-optimize-membar'
-
- This switch disables the automatic removal of redundant 'membar'
+`-mno-optimize-membar'
+ This switch disables the automatic removal of redundant `membar'
instructions from the generated code.
-'-mtomcat-stats'
-
+`-mtomcat-stats'
Cause gas to print out tomcat statistics.
-'-mcpu=CPU'
-
+`-mcpu=CPU'
Select the processor type for which to generate code. Possible
- values are 'frv', 'fr550', 'tomcat', 'fr500', 'fr450', 'fr405',
- 'fr400', 'fr300' and 'simple'.
+ values are `frv', `fr550', `tomcat', `fr500', `fr450', `fr405',
+ `fr400', `fr300' and `simple'.
+

File: gcc.info, Node: GNU/Linux Options, Next: H8/300 Options, Prev: FRV Options, Up: Submodel Options
@@ -14529,82 +14594,83 @@ File: gcc.info, Node: GNU/Linux Options, Next: H8/300 Options, Prev: FRV Opti
3.17.14 GNU/Linux Options
-------------------------
-These '-m' options are defined for GNU/Linux targets:
+These `-m' options are defined for GNU/Linux targets:
-'-mglibc'
+`-mglibc'
Use the GNU C library. This is the default except on
- '*-*-linux-*uclibc*' and '*-*-linux-*android*' targets.
+ `*-*-linux-*uclibc*' and `*-*-linux-*android*' targets.
-'-muclibc'
- Use uClibc C library. This is the default on '*-*-linux-*uclibc*'
+`-muclibc'
+ Use uClibc C library. This is the default on `*-*-linux-*uclibc*'
targets.
-'-mbionic'
- Use Bionic C library. This is the default on '*-*-linux-*android*'
- targets.
+`-mbionic'
+ Use Bionic C library. This is the default on
+ `*-*-linux-*android*' targets.
-'-mandroid'
- Compile code compatible with Android platform. This is the default
- on '*-*-linux-*android*' targets.
+`-mandroid'
+ Compile code compatible with Android platform. This is the
+ default on `*-*-linux-*android*' targets.
- When compiling, this option enables '-mbionic', '-fPIC',
- '-fno-exceptions' and '-fno-rtti' by default. When linking, this
+ When compiling, this option enables `-mbionic', `-fPIC',
+ `-fno-exceptions' and `-fno-rtti' by default. When linking, this
option makes the GCC driver pass Android-specific options to the
linker. Finally, this option causes the preprocessor macro
- '__ANDROID__' to be defined.
+ `__ANDROID__' to be defined.
-'-tno-android-cc'
- Disable compilation effects of '-mandroid', i.e., do not enable
- '-mbionic', '-fPIC', '-fno-exceptions' and '-fno-rtti' by default.
+`-tno-android-cc'
+ Disable compilation effects of `-mandroid', i.e., do not enable
+ `-mbionic', `-fPIC', `-fno-exceptions' and `-fno-rtti' by default.
-'-tno-android-ld'
- Disable linking effects of '-mandroid', i.e., pass standard Linux
+`-tno-android-ld'
+ Disable linking effects of `-mandroid', i.e., pass standard Linux
linking options to the linker.
+

File: gcc.info, Node: H8/300 Options, Next: HPPA Options, Prev: GNU/Linux Options, Up: Submodel Options
3.17.15 H8/300 Options
----------------------
-These '-m' options are defined for the H8/300 implementations:
+These `-m' options are defined for the H8/300 implementations:
-'-mrelax'
+`-mrelax'
Shorten some address references at link time, when possible; uses
- the linker option '-relax'. *Note 'ld' and the H8/300: (ld)H8/300,
- for a fuller description.
+ the linker option `-relax'. *Note `ld' and the H8/300:
+ (ld)H8/300, for a fuller description.
-'-mh'
+`-mh'
Generate code for the H8/300H.
-'-ms'
+`-ms'
Generate code for the H8S.
-'-mn'
+`-mn'
Generate code for the H8S and H8/300H in the normal mode. This
- switch must be used either with '-mh' or '-ms'.
+ switch must be used either with `-mh' or `-ms'.
-'-ms2600'
+`-ms2600'
Generate code for the H8S/2600. This switch must be used with
- '-ms'.
+ `-ms'.
-'-mexr'
+`-mexr'
Extended registers are stored on stack before execution of function
- with monitor attribute. Default option is '-mexr'. This option is
+ with monitor attribute. Default option is `-mexr'. This option is
valid only for H8S targets.
-'-mno-exr'
+`-mno-exr'
Extended registers are not stored on stack before execution of
- function with monitor attribute. Default option is '-mno-exr'.
+ function with monitor attribute. Default option is `-mno-exr'.
This option is valid only for H8S targets.
-'-mint32'
- Make 'int' data 32 bits by default.
+`-mint32'
+ Make `int' data 32 bits by default.
-'-malign-300'
+`-malign-300'
On the H8/300H and H8S, use the same alignment rules as for the
H8/300. The default for the H8/300H and H8S is to align longs and
- floats on 4-byte boundaries. '-malign-300' causes them to be
+ floats on 4-byte boundaries. `-malign-300' causes them to be
aligned on 2-byte boundaries. This option has no effect on the
H8/300.
@@ -14614,141 +14680,141 @@ File: gcc.info, Node: HPPA Options, Next: IA-64 Options, Prev: H8/300 Options
3.17.16 HPPA Options
--------------------
-These '-m' options are defined for the HPPA family of computers:
+These `-m' options are defined for the HPPA family of computers:
-'-march=ARCHITECTURE-TYPE'
+`-march=ARCHITECTURE-TYPE'
Generate code for the specified architecture. The choices for
- ARCHITECTURE-TYPE are '1.0' for PA 1.0, '1.1' for PA 1.1, and '2.0'
- for PA 2.0 processors. Refer to '/usr/lib/sched.models' on an
- HP-UX system to determine the proper architecture option for your
- machine. Code compiled for lower numbered architectures runs on
- higher numbered architectures, but not the other way around.
-
-'-mpa-risc-1-0'
-'-mpa-risc-1-1'
-'-mpa-risc-2-0'
- Synonyms for '-march=1.0', '-march=1.1', and '-march=2.0'
+ ARCHITECTURE-TYPE are `1.0' for PA 1.0, `1.1' for PA 1.1, and
+ `2.0' for PA 2.0 processors. Refer to `/usr/lib/sched.models' on
+ an HP-UX system to determine the proper architecture option for
+ your machine. Code compiled for lower numbered architectures runs
+ on higher numbered architectures, but not the other way around.
+
+`-mpa-risc-1-0'
+`-mpa-risc-1-1'
+`-mpa-risc-2-0'
+ Synonyms for `-march=1.0', `-march=1.1', and `-march=2.0'
respectively.
-'-mjump-in-delay'
+`-mjump-in-delay'
This option is ignored and provided for compatibility purposes
only.
-'-mdisable-fpregs'
+`-mdisable-fpregs'
Prevent floating-point registers from being used in any manner.
This is necessary for compiling kernels that perform lazy context
switching of floating-point registers. If you use this option and
attempt to perform floating-point operations, the compiler aborts.
-'-mdisable-indexing'
+`-mdisable-indexing'
Prevent the compiler from using indexing address modes. This
avoids some rather obscure problems when compiling MIG generated
code under MACH.
-'-mno-space-regs'
- Generate code that assumes the target has no space registers. This
- allows GCC to generate faster indirect calls and use unscaled index
- address modes.
+`-mno-space-regs'
+ Generate code that assumes the target has no space registers.
+ This allows GCC to generate faster indirect calls and use unscaled
+ index address modes.
Such code is suitable for level 0 PA systems and kernels.
-'-mfast-indirect-calls'
+`-mfast-indirect-calls'
Generate code that assumes calls never cross space boundaries.
This allows GCC to emit code that performs faster indirect calls.
This option does not work in the presence of shared libraries or
nested functions.
-'-mfixed-range=REGISTER-RANGE'
+`-mfixed-range=REGISTER-RANGE'
Generate code treating the given register range as fixed registers.
A fixed register is one that the register allocator cannot use.
This is useful when compiling kernel code. A register range is
specified as two registers separated by a dash. Multiple register
ranges can be specified separated by a comma.
-'-mlong-load-store'
+`-mlong-load-store'
Generate 3-instruction load and store sequences as sometimes
- required by the HP-UX 10 linker. This is equivalent to the '+k'
+ required by the HP-UX 10 linker. This is equivalent to the `+k'
option to the HP compilers.
-'-mportable-runtime'
+`-mportable-runtime'
Use the portable calling conventions proposed by HP for ELF
systems.
-'-mgas'
+`-mgas'
Enable the use of assembler directives only GAS understands.
-'-mschedule=CPU-TYPE'
+`-mschedule=CPU-TYPE'
Schedule code according to the constraints for the machine type
- CPU-TYPE. The choices for CPU-TYPE are '700' '7100', '7100LC',
- '7200', '7300' and '8000'. Refer to '/usr/lib/sched.models' on an
+ CPU-TYPE. The choices for CPU-TYPE are `700' `7100', `7100LC',
+ `7200', `7300' and `8000'. Refer to `/usr/lib/sched.models' on an
HP-UX system to determine the proper scheduling option for your
- machine. The default scheduling is '8000'.
+ machine. The default scheduling is `8000'.
-'-mlinker-opt'
+`-mlinker-opt'
Enable the optimization pass in the HP-UX linker. Note this makes
- symbolic debugging impossible. It also triggers a bug in the HP-UX
- 8 and HP-UX 9 linkers in which they give bogus error messages when
- linking some programs.
+ symbolic debugging impossible. It also triggers a bug in the
+ HP-UX 8 and HP-UX 9 linkers in which they give bogus error
+ messages when linking some programs.
-'-msoft-float'
+`-msoft-float'
Generate output containing library calls for floating point.
*Warning:* the requisite libraries are not available for all HPPA
- targets. Normally the facilities of the machine's usual C compiler
- are used, but this cannot be done directly in cross-compilation.
- You must make your own arrangements to provide suitable library
- functions for cross-compilation.
+ targets. Normally the facilities of the machine's usual C
+ compiler are used, but this cannot be done directly in
+ cross-compilation. You must make your own arrangements to provide
+ suitable library functions for cross-compilation.
- '-msoft-float' changes the calling convention in the output file;
+ `-msoft-float' changes the calling convention in the output file;
therefore, it is only useful if you compile _all_ of a program with
- this option. In particular, you need to compile 'libgcc.a', the
- library that comes with GCC, with '-msoft-float' in order for this
+ this option. In particular, you need to compile `libgcc.a', the
+ library that comes with GCC, with `-msoft-float' in order for this
to work.
-'-msio'
- Generate the predefine, '_SIO', for server IO. The default is
- '-mwsio'. This generates the predefines, '__hp9000s700',
- '__hp9000s700__' and '_WSIO', for workstation IO. These options
+`-msio'
+ Generate the predefine, `_SIO', for server IO. The default is
+ `-mwsio'. This generates the predefines, `__hp9000s700',
+ `__hp9000s700__' and `_WSIO', for workstation IO. These options
are available under HP-UX and HI-UX.
-'-mgnu-ld'
- Use options specific to GNU 'ld'. This passes '-shared' to 'ld'
+`-mgnu-ld'
+ Use options specific to GNU `ld'. This passes `-shared' to `ld'
when building a shared library. It is the default when GCC is
configured, explicitly or implicitly, with the GNU linker. This
- option does not affect which 'ld' is called; it only changes what
- parameters are passed to that 'ld'. The 'ld' that is called is
- determined by the '--with-ld' configure option, GCC's program
- search path, and finally by the user's 'PATH'. The linker used by
- GCC can be printed using 'which `gcc -print-prog-name=ld`'. This
+ option does not affect which `ld' is called; it only changes what
+ parameters are passed to that `ld'. The `ld' that is called is
+ determined by the `--with-ld' configure option, GCC's program
+ search path, and finally by the user's `PATH'. The linker used by
+ GCC can be printed using `which `gcc -print-prog-name=ld`'. This
option is only available on the 64-bit HP-UX GCC, i.e. configured
- with 'hppa*64*-*-hpux*'.
-
-'-mhp-ld'
- Use options specific to HP 'ld'. This passes '-b' to 'ld' when
- building a shared library and passes '+Accept TypeMismatch' to 'ld'
- on all links. It is the default when GCC is configured, explicitly
- or implicitly, with the HP linker. This option does not affect
- which 'ld' is called; it only changes what parameters are passed to
- that 'ld'. The 'ld' that is called is determined by the
- '--with-ld' configure option, GCC's program search path, and
- finally by the user's 'PATH'. The linker used by GCC can be
- printed using 'which `gcc -print-prog-name=ld`'. This option is
+ with `hppa*64*-*-hpux*'.
+
+`-mhp-ld'
+ Use options specific to HP `ld'. This passes `-b' to `ld' when
+ building a shared library and passes `+Accept TypeMismatch' to
+ `ld' on all links. It is the default when GCC is configured,
+ explicitly or implicitly, with the HP linker. This option does
+ not affect which `ld' is called; it only changes what parameters
+ are passed to that `ld'. The `ld' that is called is determined by
+ the `--with-ld' configure option, GCC's program search path, and
+ finally by the user's `PATH'. The linker used by GCC can be
+ printed using `which `gcc -print-prog-name=ld`'. This option is
only available on the 64-bit HP-UX GCC, i.e. configured with
- 'hppa*64*-*-hpux*'.
+ `hppa*64*-*-hpux*'.
-'-mlong-calls'
+`-mlong-calls'
Generate code that uses long call sequences. This ensures that a
call is always able to reach linker generated stubs. The default
- is to generate long calls only when the distance from the call site
- to the beginning of the function or translation unit, as the case
- may be, exceeds a predefined limit set by the branch type being
- used. The limits for normal calls are 7,600,000 and 240,000 bytes,
- respectively for the PA 2.0 and PA 1.X architectures. Sibcalls are
- always limited at 240,000 bytes.
+ is to generate long calls only when the distance from the call
+ site to the beginning of the function or translation unit, as the
+ case may be, exceeds a predefined limit set by the branch type
+ being used. The limits for normal calls are 7,600,000 and 240,000
+ bytes, respectively for the PA 2.0 and PA 1.X architectures.
+ Sibcalls are always limited at 240,000 bytes.
Distances are measured from the beginning of functions when using
- the '-ffunction-sections' option, or when using the '-mgas' and
- '-mno-portable-runtime' options together under HP-UX with the SOM
+ the `-ffunction-sections' option, or when using the `-mgas' and
+ `-mno-portable-runtime' options together under HP-UX with the SOM
linker.
It is normally not desirable to use this option as it degrades
@@ -14762,50 +14828,50 @@ These '-m' options are defined for the HPPA family of computers:
However, an indirect call is used on 32-bit ELF systems in pic code
and it is quite long.
-'-munix=UNIX-STD'
+`-munix=UNIX-STD'
Generate compiler predefines and select a startfile for the
- specified UNIX standard. The choices for UNIX-STD are '93', '95'
- and '98'. '93' is supported on all HP-UX versions. '95' is
- available on HP-UX 10.10 and later. '98' is available on HP-UX
- 11.11 and later. The default values are '93' for HP-UX 10.00, '95'
- for HP-UX 10.10 though to 11.00, and '98' for HP-UX 11.11 and
+ specified UNIX standard. The choices for UNIX-STD are `93', `95'
+ and `98'. `93' is supported on all HP-UX versions. `95' is
+ available on HP-UX 10.10 and later. `98' is available on HP-UX
+ 11.11 and later. The default values are `93' for HP-UX 10.00,
+ `95' for HP-UX 10.10 though to 11.00, and `98' for HP-UX 11.11 and
later.
- '-munix=93' provides the same predefines as GCC 3.3 and 3.4.
- '-munix=95' provides additional predefines for 'XOPEN_UNIX' and
- '_XOPEN_SOURCE_EXTENDED', and the startfile 'unix95.o'.
- '-munix=98' provides additional predefines for '_XOPEN_UNIX',
- '_XOPEN_SOURCE_EXTENDED', '_INCLUDE__STDC_A1_SOURCE' and
- '_INCLUDE_XOPEN_SOURCE_500', and the startfile 'unix98.o'.
+ `-munix=93' provides the same predefines as GCC 3.3 and 3.4.
+ `-munix=95' provides additional predefines for `XOPEN_UNIX' and
+ `_XOPEN_SOURCE_EXTENDED', and the startfile `unix95.o'.
+ `-munix=98' provides additional predefines for `_XOPEN_UNIX',
+ `_XOPEN_SOURCE_EXTENDED', `_INCLUDE__STDC_A1_SOURCE' and
+ `_INCLUDE_XOPEN_SOURCE_500', and the startfile `unix98.o'.
It is _important_ to note that this option changes the interfaces
for various library routines. It also affects the operational
- behavior of the C library. Thus, _extreme_ care is needed in using
- this option.
+ behavior of the C library. Thus, _extreme_ care is needed in
+ using this option.
Library code that is intended to operate with more than one UNIX
standard must test, set and restore the variable
- '__xpg4_extended_mask' as appropriate. Most GNU software doesn't
+ `__xpg4_extended_mask' as appropriate. Most GNU software doesn't
provide this capability.
-'-nolibdld'
+`-nolibdld'
Suppress the generation of link options to search libdld.sl when
- the '-static' option is specified on HP-UX 10 and later.
+ the `-static' option is specified on HP-UX 10 and later.
-'-static'
+`-static'
The HP-UX implementation of setlocale in libc has a dependency on
libdld.sl. There isn't an archive version of libdld.sl. Thus,
- when the '-static' option is specified, special link options are
+ when the `-static' option is specified, special link options are
needed to resolve this dependency.
On HP-UX 10 and later, the GCC driver adds the necessary options to
- link with libdld.sl when the '-static' option is specified. This
- causes the resulting binary to be dynamic. On the 64-bit port, the
- linkers generate dynamic binaries by default in any case. The
- '-nolibdld' option can be used to prevent the GCC driver from
+ link with libdld.sl when the `-static' option is specified. This
+ causes the resulting binary to be dynamic. On the 64-bit port,
+ the linkers generate dynamic binaries by default in any case. The
+ `-nolibdld' option can be used to prevent the GCC driver from
adding these link options.
-'-threads'
+`-threads'
Add support for multithreading with the "dce thread" library under
HP-UX. This option sets flags for both the preprocessor and
linker.
@@ -14816,263 +14882,265 @@ File: gcc.info, Node: IA-64 Options, Next: LM32 Options, Prev: HPPA Options,
3.17.17 IA-64 Options
---------------------
-These are the '-m' options defined for the Intel IA-64 architecture.
+These are the `-m' options defined for the Intel IA-64 architecture.
-'-mbig-endian'
+`-mbig-endian'
Generate code for a big-endian target. This is the default for
HP-UX.
-'-mlittle-endian'
+`-mlittle-endian'
Generate code for a little-endian target. This is the default for
AIX5 and GNU/Linux.
-'-mgnu-as'
-'-mno-gnu-as'
+`-mgnu-as'
+`-mno-gnu-as'
Generate (or don't) code for the GNU assembler. This is the
default.
-'-mgnu-ld'
-'-mno-gnu-ld'
+`-mgnu-ld'
+`-mno-gnu-ld'
Generate (or don't) code for the GNU linker. This is the default.
-'-mno-pic'
+`-mno-pic'
Generate code that does not use a global pointer register. The
result is not position independent code, and violates the IA-64
ABI.
-'-mvolatile-asm-stop'
-'-mno-volatile-asm-stop'
+`-mvolatile-asm-stop'
+`-mno-volatile-asm-stop'
Generate (or don't) a stop bit immediately before and after
volatile asm statements.
-'-mregister-names'
-'-mno-register-names'
- Generate (or don't) 'in', 'loc', and 'out' register names for the
+`-mregister-names'
+`-mno-register-names'
+ Generate (or don't) `in', `loc', and `out' register names for the
stacked registers. This may make assembler output more readable.
-'-mno-sdata'
-'-msdata'
+`-mno-sdata'
+`-msdata'
Disable (or enable) optimizations that use the small data section.
This may be useful for working around optimizer bugs.
-'-mconstant-gp'
+`-mconstant-gp'
Generate code that uses a single constant global pointer value.
This is useful when compiling kernel code.
-'-mauto-pic'
+`-mauto-pic'
Generate code that is self-relocatable. This implies
- '-mconstant-gp'. This is useful when compiling firmware code.
+ `-mconstant-gp'. This is useful when compiling firmware code.
-'-minline-float-divide-min-latency'
- Generate code for inline divides of floating-point values using the
- minimum latency algorithm.
+`-minline-float-divide-min-latency'
+ Generate code for inline divides of floating-point values using
+ the minimum latency algorithm.
-'-minline-float-divide-max-throughput'
- Generate code for inline divides of floating-point values using the
- maximum throughput algorithm.
+`-minline-float-divide-max-throughput'
+ Generate code for inline divides of floating-point values using
+ the maximum throughput algorithm.
-'-mno-inline-float-divide'
+`-mno-inline-float-divide'
Do not generate inline code for divides of floating-point values.
-'-minline-int-divide-min-latency'
+`-minline-int-divide-min-latency'
Generate code for inline divides of integer values using the
minimum latency algorithm.
-'-minline-int-divide-max-throughput'
+`-minline-int-divide-max-throughput'
Generate code for inline divides of integer values using the
maximum throughput algorithm.
-'-mno-inline-int-divide'
+`-mno-inline-int-divide'
Do not generate inline code for divides of integer values.
-'-minline-sqrt-min-latency'
+`-minline-sqrt-min-latency'
Generate code for inline square roots using the minimum latency
algorithm.
-'-minline-sqrt-max-throughput'
+`-minline-sqrt-max-throughput'
Generate code for inline square roots using the maximum throughput
algorithm.
-'-mno-inline-sqrt'
- Do not generate inline code for 'sqrt'.
+`-mno-inline-sqrt'
+ Do not generate inline code for `sqrt'.
-'-mfused-madd'
-'-mno-fused-madd'
+`-mfused-madd'
+`-mno-fused-madd'
Do (don't) generate code that uses the fused multiply/add or
multiply/subtract instructions. The default is to use these
instructions.
-'-mno-dwarf2-asm'
-'-mdwarf2-asm'
+`-mno-dwarf2-asm'
+`-mdwarf2-asm'
Don't (or do) generate assembler code for the DWARF 2 line number
debugging info. This may be useful when not using the GNU
assembler.
-'-mearly-stop-bits'
-'-mno-early-stop-bits'
+`-mearly-stop-bits'
+`-mno-early-stop-bits'
Allow stop bits to be placed earlier than immediately preceding the
instruction that triggered the stop bit. This can improve
instruction scheduling, but does not always do so.
-'-mfixed-range=REGISTER-RANGE'
+`-mfixed-range=REGISTER-RANGE'
Generate code treating the given register range as fixed registers.
A fixed register is one that the register allocator cannot use.
This is useful when compiling kernel code. A register range is
specified as two registers separated by a dash. Multiple register
ranges can be specified separated by a comma.
-'-mtls-size=TLS-SIZE'
+`-mtls-size=TLS-SIZE'
Specify bit size of immediate TLS offsets. Valid values are 14,
22, and 64.
-'-mtune=CPU-TYPE'
+`-mtune=CPU-TYPE'
Tune the instruction scheduling for a particular CPU, Valid values
- are 'itanium', 'itanium1', 'merced', 'itanium2', and 'mckinley'.
+ are `itanium', `itanium1', `merced', `itanium2', and `mckinley'.
-'-milp32'
-'-mlp64'
+`-milp32'
+`-mlp64'
Generate code for a 32-bit or 64-bit environment. The 32-bit
environment sets int, long and pointer to 32 bits. The 64-bit
environment sets int to 32 bits and long and pointer to 64 bits.
These are HP-UX specific flags.
-'-mno-sched-br-data-spec'
-'-msched-br-data-spec'
+`-mno-sched-br-data-spec'
+`-msched-br-data-spec'
(Dis/En)able data speculative scheduling before reload. This
- results in generation of 'ld.a' instructions and the corresponding
- check instructions ('ld.c' / 'chk.a'). The default is 'disable'.
+ results in generation of `ld.a' instructions and the corresponding
+ check instructions (`ld.c' / `chk.a'). The default is 'disable'.
-'-msched-ar-data-spec'
-'-mno-sched-ar-data-spec'
+`-msched-ar-data-spec'
+`-mno-sched-ar-data-spec'
(En/Dis)able data speculative scheduling after reload. This
- results in generation of 'ld.a' instructions and the corresponding
- check instructions ('ld.c' / 'chk.a'). The default is 'enable'.
+ results in generation of `ld.a' instructions and the corresponding
+ check instructions (`ld.c' / `chk.a'). The default is 'enable'.
-'-mno-sched-control-spec'
-'-msched-control-spec'
+`-mno-sched-control-spec'
+`-msched-control-spec'
(Dis/En)able control speculative scheduling. This feature is
- available only during region scheduling (i.e. before reload). This
- results in generation of the 'ld.s' instructions and the
- corresponding check instructions 'chk.s'. The default is
+ available only during region scheduling (i.e. before reload).
+ This results in generation of the `ld.s' instructions and the
+ corresponding check instructions `chk.s'. The default is
'disable'.
-'-msched-br-in-data-spec'
-'-mno-sched-br-in-data-spec'
+`-msched-br-in-data-spec'
+`-mno-sched-br-in-data-spec'
(En/Dis)able speculative scheduling of the instructions that are
dependent on the data speculative loads before reload. This is
- effective only with '-msched-br-data-spec' enabled. The default is
- 'enable'.
+ effective only with `-msched-br-data-spec' enabled. The default
+ is 'enable'.
-'-msched-ar-in-data-spec'
-'-mno-sched-ar-in-data-spec'
+`-msched-ar-in-data-spec'
+`-mno-sched-ar-in-data-spec'
(En/Dis)able speculative scheduling of the instructions that are
dependent on the data speculative loads after reload. This is
- effective only with '-msched-ar-data-spec' enabled. The default is
- 'enable'.
+ effective only with `-msched-ar-data-spec' enabled. The default
+ is 'enable'.
-'-msched-in-control-spec'
-'-mno-sched-in-control-spec'
+`-msched-in-control-spec'
+`-mno-sched-in-control-spec'
(En/Dis)able speculative scheduling of the instructions that are
- dependent on the control speculative loads. This is effective only
- with '-msched-control-spec' enabled. The default is 'enable'.
+ dependent on the control speculative loads. This is effective
+ only with `-msched-control-spec' enabled. The default is 'enable'.
-'-mno-sched-prefer-non-data-spec-insns'
-'-msched-prefer-non-data-spec-insns'
+`-mno-sched-prefer-non-data-spec-insns'
+`-msched-prefer-non-data-spec-insns'
If enabled, data-speculative instructions are chosen for schedule
only if there are no other choices at the moment. This makes the
- use of the data speculation much more conservative. The default is
- 'disable'.
+ use of the data speculation much more conservative. The default
+ is 'disable'.
-'-mno-sched-prefer-non-control-spec-insns'
-'-msched-prefer-non-control-spec-insns'
+`-mno-sched-prefer-non-control-spec-insns'
+`-msched-prefer-non-control-spec-insns'
If enabled, control-speculative instructions are chosen for
schedule only if there are no other choices at the moment. This
makes the use of the control speculation much more conservative.
The default is 'disable'.
-'-mno-sched-count-spec-in-critical-path'
-'-msched-count-spec-in-critical-path'
+`-mno-sched-count-spec-in-critical-path'
+`-msched-count-spec-in-critical-path'
If enabled, speculative dependencies are considered during
computation of the instructions priorities. This makes the use of
the speculation a bit more conservative. The default is 'disable'.
-'-msched-spec-ldc'
+`-msched-spec-ldc'
Use a simple data speculation check. This option is on by default.
-'-msched-control-spec-ldc'
+`-msched-control-spec-ldc'
Use a simple check for control speculation. This option is on by
default.
-'-msched-stop-bits-after-every-cycle'
- Place a stop bit after every cycle when scheduling. This option is
- on by default.
+`-msched-stop-bits-after-every-cycle'
+ Place a stop bit after every cycle when scheduling. This option
+ is on by default.
-'-msched-fp-mem-deps-zero-cost'
- Assume that floating-point stores and loads are not likely to cause
- a conflict when placed into the same instruction group. This
- option is disabled by default.
+`-msched-fp-mem-deps-zero-cost'
+ Assume that floating-point stores and loads are not likely to
+ cause a conflict when placed into the same instruction group.
+ This option is disabled by default.
-'-msel-sched-dont-check-control-spec'
+`-msel-sched-dont-check-control-spec'
Generate checks for control speculation in selective scheduling.
This flag is disabled by default.
-'-msched-max-memory-insns=MAX-INSNS'
+`-msched-max-memory-insns=MAX-INSNS'
Limit on the number of memory insns per instruction group, giving
- lower priority to subsequent memory insns attempting to schedule in
- the same instruction group. Frequently useful to prevent cache
+ lower priority to subsequent memory insns attempting to schedule
+ in the same instruction group. Frequently useful to prevent cache
bank conflicts. The default value is 1.
-'-msched-max-memory-insns-hard-limit'
- Makes the limit specified by 'msched-max-memory-insns' a hard
+`-msched-max-memory-insns-hard-limit'
+ Makes the limit specified by `msched-max-memory-insns' a hard
limit, disallowing more than that number in an instruction group.
Otherwise, the limit is "soft", meaning that non-memory operations
are preferred when the limit is reached, but memory operations may
still be scheduled.
+

File: gcc.info, Node: LM32 Options, Next: M32C Options, Prev: IA-64 Options, Up: Submodel Options
3.17.18 LM32 Options
--------------------
-These '-m' options are defined for the LatticeMico32 architecture:
+These `-m' options are defined for the LatticeMico32 architecture:
-'-mbarrel-shift-enabled'
+`-mbarrel-shift-enabled'
Enable barrel-shift instructions.
-'-mdivide-enabled'
+`-mdivide-enabled'
Enable divide and modulus instructions.
-'-mmultiply-enabled'
+`-mmultiply-enabled'
Enable multiply instructions.
-'-msign-extend-enabled'
+`-msign-extend-enabled'
Enable sign extend instructions.
-'-muser-enabled'
+`-muser-enabled'
Enable user-defined instructions.
+

File: gcc.info, Node: M32C Options, Next: M32R/D Options, Prev: LM32 Options, Up: Submodel Options
3.17.19 M32C Options
--------------------
-'-mcpu=NAME'
+`-mcpu=NAME'
Select the CPU for which code is generated. NAME may be one of
- 'r8c' for the R8C/Tiny series, 'm16c' for the M16C (up to /60)
- series, 'm32cm' for the M16C/80 series, or 'm32c' for the M32C/80
+ `r8c' for the R8C/Tiny series, `m16c' for the M16C (up to /60)
+ series, `m32cm' for the M16C/80 series, or `m32c' for the M32C/80
series.
-'-msim'
+`-msim'
Specifies that the program will be run on the simulator. This
- causes an alternate runtime library to be linked in which supports,
- for example, file I/O. You must not use this option when
- generating programs that will run on real hardware; you must
+ causes an alternate runtime library to be linked in which
+ supports, for example, file I/O. You must not use this option
+ when generating programs that will run on real hardware; you must
provide your own runtime library for whatever I/O functions are
needed.
-'-memregs=NUMBER'
+`-memregs=NUMBER'
Specifies the number of memory-based pseudo-registers GCC uses
during code generation. These pseudo-registers are used like real
registers, so there is a tradeoff between GCC's ability to fit the
@@ -15082,344 +15150,350 @@ File: gcc.info, Node: M32C Options, Next: M32R/D Options, Prev: LM32 Options,
that, you must not use this option with GCC's default runtime
libraries.
+

File: gcc.info, Node: M32R/D Options, Next: M680x0 Options, Prev: M32C Options, Up: Submodel Options
3.17.20 M32R/D Options
----------------------
-These '-m' options are defined for Renesas M32R/D architectures:
+These `-m' options are defined for Renesas M32R/D architectures:
-'-m32r2'
+`-m32r2'
Generate code for the M32R/2.
-'-m32rx'
+`-m32rx'
Generate code for the M32R/X.
-'-m32r'
+`-m32r'
Generate code for the M32R. This is the default.
-'-mmodel=small'
+`-mmodel=small'
Assume all objects live in the lower 16MB of memory (so that their
- addresses can be loaded with the 'ld24' instruction), and assume
- all subroutines are reachable with the 'bl' instruction. This is
+ addresses can be loaded with the `ld24' instruction), and assume
+ all subroutines are reachable with the `bl' instruction. This is
the default.
The addressability of a particular object can be set with the
- 'model' attribute.
+ `model' attribute.
-'-mmodel=medium'
+`-mmodel=medium'
Assume objects may be anywhere in the 32-bit address space (the
- compiler generates 'seth/add3' instructions to load their
- addresses), and assume all subroutines are reachable with the 'bl'
+ compiler generates `seth/add3' instructions to load their
+ addresses), and assume all subroutines are reachable with the `bl'
instruction.
-'-mmodel=large'
+`-mmodel=large'
Assume objects may be anywhere in the 32-bit address space (the
- compiler generates 'seth/add3' instructions to load their
+ compiler generates `seth/add3' instructions to load their
addresses), and assume subroutines may not be reachable with the
- 'bl' instruction (the compiler generates the much slower
- 'seth/add3/jl' instruction sequence).
+ `bl' instruction (the compiler generates the much slower
+ `seth/add3/jl' instruction sequence).
-'-msdata=none'
+`-msdata=none'
Disable use of the small data area. Variables are put into one of
- '.data', '.bss', or '.rodata' (unless the 'section' attribute has
+ `.data', `.bss', or `.rodata' (unless the `section' attribute has
been specified). This is the default.
- The small data area consists of sections '.sdata' and '.sbss'.
+ The small data area consists of sections `.sdata' and `.sbss'.
Objects may be explicitly put in the small data area with the
- 'section' attribute using one of these sections.
+ `section' attribute using one of these sections.
-'-msdata=sdata'
+`-msdata=sdata'
Put small global and static data in the small data area, but do not
generate special code to reference them.
-'-msdata=use'
+`-msdata=use'
Put small global and static data in the small data area, and
generate special instructions to reference them.
-'-G NUM'
+`-G NUM'
Put global and static objects less than or equal to NUM bytes into
the small data or BSS sections instead of the normal data or BSS
- sections. The default value of NUM is 8. The '-msdata' option
- must be set to one of 'sdata' or 'use' for this option to have any
+ sections. The default value of NUM is 8. The `-msdata' option
+ must be set to one of `sdata' or `use' for this option to have any
effect.
- All modules should be compiled with the same '-G NUM' value.
+ All modules should be compiled with the same `-G NUM' value.
Compiling with different values of NUM may or may not work; if it
doesn't the linker gives an error message--incorrect code is not
generated.
-'-mdebug'
+`-mdebug'
Makes the M32R-specific code in the compiler display some
statistics that might help in debugging programs.
-'-malign-loops'
+`-malign-loops'
Align all loops to a 32-byte boundary.
-'-mno-align-loops'
+`-mno-align-loops'
Do not enforce a 32-byte alignment for loops. This is the default.
-'-missue-rate=NUMBER'
+`-missue-rate=NUMBER'
Issue NUMBER instructions per cycle. NUMBER can only be 1 or 2.
-'-mbranch-cost=NUMBER'
+`-mbranch-cost=NUMBER'
NUMBER can only be 1 or 2. If it is 1 then branches are preferred
over conditional code, if it is 2, then the opposite applies.
-'-mflush-trap=NUMBER'
+`-mflush-trap=NUMBER'
Specifies the trap number to use to flush the cache. The default
is 12. Valid numbers are between 0 and 15 inclusive.
-'-mno-flush-trap'
+`-mno-flush-trap'
Specifies that the cache cannot be flushed by using a trap.
-'-mflush-func=NAME'
+`-mflush-func=NAME'
Specifies the name of the operating system function to call to
- flush the cache. The default is '_flush_cache', but a function
+ flush the cache. The default is `_flush_cache', but a function
call is only used if a trap is not available.
-'-mno-flush-func'
+`-mno-flush-func'
Indicates that there is no OS function for flushing the cache.
+

File: gcc.info, Node: M680x0 Options, Next: MCore Options, Prev: M32R/D Options, Up: Submodel Options
3.17.21 M680x0 Options
----------------------
-These are the '-m' options defined for M680x0 and ColdFire processors.
+These are the `-m' options defined for M680x0 and ColdFire processors.
The default settings depend on which architecture was selected when the
compiler was configured; the defaults for the most common choices are
given below.
-'-march=ARCH'
+`-march=ARCH'
Generate code for a specific M680x0 or ColdFire instruction set
architecture. Permissible values of ARCH for M680x0 architectures
- are: '68000', '68010', '68020', '68030', '68040', '68060' and
- 'cpu32'. ColdFire architectures are selected according to
+ are: `68000', `68010', `68020', `68030', `68040', `68060' and
+ `cpu32'. ColdFire architectures are selected according to
Freescale's ISA classification and the permissible values are:
- 'isaa', 'isaaplus', 'isab' and 'isac'.
+ `isaa', `isaaplus', `isab' and `isac'.
- GCC defines a macro '__mcfARCH__' whenever it is generating code
+ GCC defines a macro `__mcfARCH__' whenever it is generating code
for a ColdFire target. The ARCH in this macro is one of the
- '-march' arguments given above.
+ `-march' arguments given above.
- When used together, '-march' and '-mtune' select code that runs on
+ When used together, `-march' and `-mtune' select code that runs on
a family of similar processors but that is optimized for a
particular microarchitecture.
-'-mcpu=CPU'
+`-mcpu=CPU'
Generate code for a specific M680x0 or ColdFire processor. The
- M680x0 CPUs are: '68000', '68010', '68020', '68030', '68040',
- '68060', '68302', '68332' and 'cpu32'. The ColdFire CPUs are given
- by the table below, which also classifies the CPUs into families:
-
- *Family* *'-mcpu' arguments*
- '51' '51' '51ac' '51ag' '51cn' '51em' '51je' '51jf' '51jg'
- '51jm' '51mm' '51qe' '51qm'
- '5206' '5202' '5204' '5206'
- '5206e' '5206e'
- '5208' '5207' '5208'
- '5211a' '5210a' '5211a'
- '5213' '5211' '5212' '5213'
- '5216' '5214' '5216'
- '52235' '52230' '52231' '52232' '52233' '52234' '52235'
- '5225' '5224' '5225'
- '52259' '52252' '52254' '52255' '52256' '52258' '52259'
- '5235' '5232' '5233' '5234' '5235' '523x'
- '5249' '5249'
- '5250' '5250'
- '5271' '5270' '5271'
- '5272' '5272'
- '5275' '5274' '5275'
- '5282' '5280' '5281' '5282' '528x'
- '53017' '53011' '53012' '53013' '53014' '53015' '53016' '53017'
- '5307' '5307'
- '5329' '5327' '5328' '5329' '532x'
- '5373' '5372' '5373' '537x'
- '5407' '5407'
- '5475' '5470' '5471' '5472' '5473' '5474' '5475' '547x' '5480'
- '5481' '5482' '5483' '5484' '5485'
-
- '-mcpu=CPU' overrides '-march=ARCH' if ARCH is compatible with CPU.
- Other combinations of '-mcpu' and '-march' are rejected.
-
- GCC defines the macro '__mcf_cpu_CPU' when ColdFire target CPU is
- selected. It also defines '__mcf_family_FAMILY', where the value
+ M680x0 CPUs are: `68000', `68010', `68020', `68030', `68040',
+ `68060', `68302', `68332' and `cpu32'. The ColdFire CPUs are
+ given by the table below, which also classifies the CPUs into
+ families:
+
+ *Family* *`-mcpu' arguments*
+ `51' `51' `51ac' `51ag' `51cn' `51em' `51je' `51jf' `51jg'
+ `51jm' `51mm' `51qe' `51qm'
+ `5206' `5202' `5204' `5206'
+ `5206e' `5206e'
+ `5208' `5207' `5208'
+ `5211a' `5210a' `5211a'
+ `5213' `5211' `5212' `5213'
+ `5216' `5214' `5216'
+ `52235' `52230' `52231' `52232' `52233' `52234' `52235'
+ `5225' `5224' `5225'
+ `52259' `52252' `52254' `52255' `52256' `52258' `52259'
+ `5235' `5232' `5233' `5234' `5235' `523x'
+ `5249' `5249'
+ `5250' `5250'
+ `5271' `5270' `5271'
+ `5272' `5272'
+ `5275' `5274' `5275'
+ `5282' `5280' `5281' `5282' `528x'
+ `53017' `53011' `53012' `53013' `53014' `53015' `53016'
+ `53017'
+ `5307' `5307'
+ `5329' `5327' `5328' `5329' `532x'
+ `5373' `5372' `5373' `537x'
+ `5407' `5407'
+ `5475' `5470' `5471' `5472' `5473' `5474' `5475' `547x'
+ `5480' `5481' `5482' `5483' `5484' `5485'
+
+ `-mcpu=CPU' overrides `-march=ARCH' if ARCH is compatible with
+ CPU. Other combinations of `-mcpu' and `-march' are rejected.
+
+ GCC defines the macro `__mcf_cpu_CPU' when ColdFire target CPU is
+ selected. It also defines `__mcf_family_FAMILY', where the value
of FAMILY is given by the table above.
-'-mtune=TUNE'
+`-mtune=TUNE'
Tune the code for a particular microarchitecture within the
- constraints set by '-march' and '-mcpu'. The M680x0
- microarchitectures are: '68000', '68010', '68020', '68030',
- '68040', '68060' and 'cpu32'. The ColdFire microarchitectures are:
- 'cfv1', 'cfv2', 'cfv3', 'cfv4' and 'cfv4e'.
+ constraints set by `-march' and `-mcpu'. The M680x0
+ microarchitectures are: `68000', `68010', `68020', `68030',
+ `68040', `68060' and `cpu32'. The ColdFire microarchitectures
+ are: `cfv1', `cfv2', `cfv3', `cfv4' and `cfv4e'.
- You can also use '-mtune=68020-40' for code that needs to run
+ You can also use `-mtune=68020-40' for code that needs to run
relatively well on 68020, 68030 and 68040 targets.
- '-mtune=68020-60' is similar but includes 68060 targets as well.
- These two options select the same tuning decisions as '-m68020-40'
- and '-m68020-60' respectively.
-
- GCC defines the macros '__mcARCH' and '__mcARCH__' when tuning for
- 680x0 architecture ARCH. It also defines 'mcARCH' unless either
- '-ansi' or a non-GNU '-std' option is used. If GCC is tuning for a
- range of architectures, as selected by '-mtune=68020-40' or
- '-mtune=68020-60', it defines the macros for every architecture in
+ `-mtune=68020-60' is similar but includes 68060 targets as well.
+ These two options select the same tuning decisions as `-m68020-40'
+ and `-m68020-60' respectively.
+
+ GCC defines the macros `__mcARCH' and `__mcARCH__' when tuning for
+ 680x0 architecture ARCH. It also defines `mcARCH' unless either
+ `-ansi' or a non-GNU `-std' option is used. If GCC is tuning for
+ a range of architectures, as selected by `-mtune=68020-40' or
+ `-mtune=68020-60', it defines the macros for every architecture in
the range.
- GCC also defines the macro '__mUARCH__' when tuning for ColdFire
+ GCC also defines the macro `__mUARCH__' when tuning for ColdFire
microarchitecture UARCH, where UARCH is one of the arguments given
above.
-'-m68000'
-'-mc68000'
- Generate output for a 68000. This is the default when the compiler
- is configured for 68000-based systems. It is equivalent to
- '-march=68000'.
+`-m68000'
+`-mc68000'
+ Generate output for a 68000. This is the default when the
+ compiler is configured for 68000-based systems. It is equivalent
+ to `-march=68000'.
Use this option for microcontrollers with a 68000 or EC000 core,
including the 68008, 68302, 68306, 68307, 68322, 68328 and 68356.
-'-m68010'
- Generate output for a 68010. This is the default when the compiler
- is configured for 68010-based systems. It is equivalent to
- '-march=68010'.
+`-m68010'
+ Generate output for a 68010. This is the default when the
+ compiler is configured for 68010-based systems. It is equivalent
+ to `-march=68010'.
-'-m68020'
-'-mc68020'
- Generate output for a 68020. This is the default when the compiler
- is configured for 68020-based systems. It is equivalent to
- '-march=68020'.
+`-m68020'
+`-mc68020'
+ Generate output for a 68020. This is the default when the
+ compiler is configured for 68020-based systems. It is equivalent
+ to `-march=68020'.
-'-m68030'
- Generate output for a 68030. This is the default when the compiler
- is configured for 68030-based systems. It is equivalent to
- '-march=68030'.
+`-m68030'
+ Generate output for a 68030. This is the default when the
+ compiler is configured for 68030-based systems. It is equivalent
+ to `-march=68030'.
-'-m68040'
- Generate output for a 68040. This is the default when the compiler
- is configured for 68040-based systems. It is equivalent to
- '-march=68040'.
+`-m68040'
+ Generate output for a 68040. This is the default when the
+ compiler is configured for 68040-based systems. It is equivalent
+ to `-march=68040'.
This option inhibits the use of 68881/68882 instructions that have
to be emulated by software on the 68040. Use this option if your
68040 does not have code to emulate those instructions.
-'-m68060'
- Generate output for a 68060. This is the default when the compiler
- is configured for 68060-based systems. It is equivalent to
- '-march=68060'.
+`-m68060'
+ Generate output for a 68060. This is the default when the
+ compiler is configured for 68060-based systems. It is equivalent
+ to `-march=68060'.
This option inhibits the use of 68020 and 68881/68882 instructions
- that have to be emulated by software on the 68060. Use this option
- if your 68060 does not have code to emulate those instructions.
+ that have to be emulated by software on the 68060. Use this
+ option if your 68060 does not have code to emulate those
+ instructions.
-'-mcpu32'
- Generate output for a CPU32. This is the default when the compiler
- is configured for CPU32-based systems. It is equivalent to
- '-march=cpu32'.
+`-mcpu32'
+ Generate output for a CPU32. This is the default when the
+ compiler is configured for CPU32-based systems. It is equivalent
+ to `-march=cpu32'.
Use this option for microcontrollers with a CPU32 or CPU32+ core,
including the 68330, 68331, 68332, 68333, 68334, 68336, 68340,
68341, 68349 and 68360.
-'-m5200'
+`-m5200'
Generate output for a 520X ColdFire CPU. This is the default when
the compiler is configured for 520X-based systems. It is
- equivalent to '-mcpu=5206', and is now deprecated in favor of that
+ equivalent to `-mcpu=5206', and is now deprecated in favor of that
option.
- Use this option for microcontroller with a 5200 core, including the
- MCF5202, MCF5203, MCF5204 and MCF5206.
+ Use this option for microcontroller with a 5200 core, including
+ the MCF5202, MCF5203, MCF5204 and MCF5206.
-'-m5206e'
+`-m5206e'
Generate output for a 5206e ColdFire CPU. The option is now
- deprecated in favor of the equivalent '-mcpu=5206e'.
+ deprecated in favor of the equivalent `-mcpu=5206e'.
-'-m528x'
+`-m528x'
Generate output for a member of the ColdFire 528X family. The
- option is now deprecated in favor of the equivalent '-mcpu=528x'.
+ option is now deprecated in favor of the equivalent `-mcpu=528x'.
-'-m5307'
+`-m5307'
Generate output for a ColdFire 5307 CPU. The option is now
- deprecated in favor of the equivalent '-mcpu=5307'.
+ deprecated in favor of the equivalent `-mcpu=5307'.
-'-m5407'
+`-m5407'
Generate output for a ColdFire 5407 CPU. The option is now
- deprecated in favor of the equivalent '-mcpu=5407'.
+ deprecated in favor of the equivalent `-mcpu=5407'.
-'-mcfv4e'
+`-mcfv4e'
Generate output for a ColdFire V4e family CPU (e.g. 547x/548x).
This includes use of hardware floating-point instructions. The
- option is equivalent to '-mcpu=547x', and is now deprecated in
+ option is equivalent to `-mcpu=547x', and is now deprecated in
favor of that option.
-'-m68020-40'
+`-m68020-40'
Generate output for a 68040, without using any of the new
instructions. This results in code that can run relatively
efficiently on either a 68020/68881 or a 68030 or a 68040. The
- generated code does use the 68881 instructions that are emulated on
- the 68040.
+ generated code does use the 68881 instructions that are emulated
+ on the 68040.
- The option is equivalent to '-march=68020' '-mtune=68020-40'.
+ The option is equivalent to `-march=68020' `-mtune=68020-40'.
-'-m68020-60'
+`-m68020-60'
Generate output for a 68060, without using any of the new
instructions. This results in code that can run relatively
efficiently on either a 68020/68881 or a 68030 or a 68040. The
- generated code does use the 68881 instructions that are emulated on
- the 68060.
+ generated code does use the 68881 instructions that are emulated
+ on the 68060.
- The option is equivalent to '-march=68020' '-mtune=68020-60'.
+ The option is equivalent to `-march=68020' `-mtune=68020-60'.
-'-mhard-float'
-'-m68881'
+`-mhard-float'
+`-m68881'
Generate floating-point instructions. This is the default for
68020 and above, and for ColdFire devices that have an FPU. It
- defines the macro '__HAVE_68881__' on M680x0 targets and
- '__mcffpu__' on ColdFire targets.
+ defines the macro `__HAVE_68881__' on M680x0 targets and
+ `__mcffpu__' on ColdFire targets.
-'-msoft-float'
+`-msoft-float'
Do not generate floating-point instructions; use library calls
instead. This is the default for 68000, 68010, and 68832 targets.
It is also the default for ColdFire devices that have no FPU.
-'-mdiv'
-'-mno-div'
+`-mdiv'
+`-mno-div'
Generate (do not generate) ColdFire hardware divide and remainder
- instructions. If '-march' is used without '-mcpu', the default is
- "on" for ColdFire architectures and "off" for M680x0 architectures.
- Otherwise, the default is taken from the target CPU (either the
- default CPU, or the one specified by '-mcpu'). For example, the
- default is "off" for '-mcpu=5206' and "on" for '-mcpu=5206e'.
+ instructions. If `-march' is used without `-mcpu', the default is
+ "on" for ColdFire architectures and "off" for M680x0
+ architectures. Otherwise, the default is taken from the target CPU
+ (either the default CPU, or the one specified by `-mcpu'). For
+ example, the default is "off" for `-mcpu=5206' and "on" for
+ `-mcpu=5206e'.
- GCC defines the macro '__mcfhwdiv__' when this option is enabled.
+ GCC defines the macro `__mcfhwdiv__' when this option is enabled.
-'-mshort'
- Consider type 'int' to be 16 bits wide, like 'short int'.
+`-mshort'
+ Consider type `int' to be 16 bits wide, like `short int'.
Additionally, parameters passed on the stack are also aligned to a
16-bit boundary even on targets whose API mandates promotion to
32-bit.
-'-mno-short'
- Do not consider type 'int' to be 16 bits wide. This is the
+`-mno-short'
+ Do not consider type `int' to be 16 bits wide. This is the
default.
-'-mnobitfield'
-'-mno-bitfield'
- Do not use the bit-field instructions. The '-m68000', '-mcpu32'
- and '-m5200' options imply '-mnobitfield'.
+`-mnobitfield'
+`-mno-bitfield'
+ Do not use the bit-field instructions. The `-m68000', `-mcpu32'
+ and `-m5200' options imply `-mnobitfield'.
-'-mbitfield'
- Do use the bit-field instructions. The '-m68020' option implies
- '-mbitfield'. This is the default if you use a configuration
+`-mbitfield'
+ Do use the bit-field instructions. The `-m68020' option implies
+ `-mbitfield'. This is the default if you use a configuration
designed for a 68020.
-'-mrtd'
+`-mrtd'
Use a different function-calling convention, in which functions
- that take a fixed number of arguments return with the 'rtd'
+ that take a fixed number of arguments return with the `rtd'
instruction, which pops their arguments while returning. This
saves one instruction in the caller since there is no need to pop
the arguments there.
@@ -15429,78 +15503,78 @@ given below.
compiled with the Unix compiler.
Also, you must provide function prototypes for all functions that
- take variable numbers of arguments (including 'printf'); otherwise
+ take variable numbers of arguments (including `printf'); otherwise
incorrect code is generated for calls to those functions.
In addition, seriously incorrect code results if you call a
function with too many arguments. (Normally, extra arguments are
harmlessly ignored.)
- The 'rtd' instruction is supported by the 68010, 68020, 68030,
+ The `rtd' instruction is supported by the 68010, 68020, 68030,
68040, 68060 and CPU32 processors, but not by the 68000 or 5200.
-'-mno-rtd'
- Do not use the calling conventions selected by '-mrtd'. This is
+`-mno-rtd'
+ Do not use the calling conventions selected by `-mrtd'. This is
the default.
-'-malign-int'
-'-mno-align-int'
- Control whether GCC aligns 'int', 'long', 'long long', 'float',
- 'double', and 'long double' variables on a 32-bit boundary
- ('-malign-int') or a 16-bit boundary ('-mno-align-int'). Aligning
+`-malign-int'
+`-mno-align-int'
+ Control whether GCC aligns `int', `long', `long long', `float',
+ `double', and `long double' variables on a 32-bit boundary
+ (`-malign-int') or a 16-bit boundary (`-mno-align-int'). Aligning
variables on 32-bit boundaries produces code that runs somewhat
faster on processors with 32-bit busses at the expense of more
memory.
- *Warning:* if you use the '-malign-int' switch, GCC aligns
+ *Warning:* if you use the `-malign-int' switch, GCC aligns
structures containing the above types differently than most
published application binary interface specifications for the m68k.
-'-mpcrel'
+`-mpcrel'
Use the pc-relative addressing mode of the 68000 directly, instead
of using a global offset table. At present, this option implies
- '-fpic', allowing at most a 16-bit offset for pc-relative
- addressing. '-fPIC' is not presently supported with '-mpcrel',
+ `-fpic', allowing at most a 16-bit offset for pc-relative
+ addressing. `-fPIC' is not presently supported with `-mpcrel',
though this could be supported for 68020 and higher processors.
-'-mno-strict-align'
-'-mstrict-align'
+`-mno-strict-align'
+`-mstrict-align'
Do not (do) assume that unaligned memory references are handled by
the system.
-'-msep-data'
+`-msep-data'
Generate code that allows the data segment to be located in a
different area of memory from the text segment. This allows for
execute-in-place in an environment without virtual memory
- management. This option implies '-fPIC'.
+ management. This option implies `-fPIC'.
-'-mno-sep-data'
+`-mno-sep-data'
Generate code that assumes that the data segment follows the text
segment. This is the default.
-'-mid-shared-library'
+`-mid-shared-library'
Generate code that supports shared libraries via the library ID
method. This allows for execute-in-place and shared libraries in
an environment without virtual memory management. This option
- implies '-fPIC'.
+ implies `-fPIC'.
-'-mno-id-shared-library'
+`-mno-id-shared-library'
Generate code that doesn't assume ID-based shared libraries are
being used. This is the default.
-'-mshared-library-id=n'
+`-mshared-library-id=n'
Specifies the identification number of the ID-based shared library
being compiled. Specifying a value of 0 generates more compact
code; specifying other values forces the allocation of that number
to the current library, but is no more space- or time-efficient
than omitting this option.
-'-mxgot'
-'-mno-xgot'
+`-mxgot'
+`-mno-xgot'
When generating position-independent code for ColdFire, generate
code that works if the GOT has more than 8192 entries. This code
is larger and slower than code generated without this option. On
- M680x0 processors, this option is not needed; '-fPIC' suffices.
+ M680x0 processors, this option is not needed; `-fPIC' suffices.
GCC normally uses a single instruction to load values from the GOT.
While this is relatively efficient, it only works if the GOT is
@@ -15509,205 +15583,208 @@ given below.
relocation truncated to fit: R_68K_GOT16O foobar
- If this happens, you should recompile your code with '-mxgot'. It
+ If this happens, you should recompile your code with `-mxgot'. It
should then work with very large GOTs. However, code generated
- with '-mxgot' is less efficient, since it takes 4 instructions to
+ with `-mxgot' is less efficient, since it takes 4 instructions to
fetch the value of a global symbol.
Note that some linkers, including newer versions of the GNU linker,
can create multiple GOTs and sort GOT entries. If you have such a
- linker, you should only need to use '-mxgot' when compiling a
+ linker, you should only need to use `-mxgot' when compiling a
single object file that accesses more than 8192 GOT entries. Very
few do.
These options have no effect unless GCC is generating
position-independent code.
+

File: gcc.info, Node: MCore Options, Next: MeP Options, Prev: M680x0 Options, Up: Submodel Options
3.17.22 MCore Options
---------------------
-These are the '-m' options defined for the Motorola M*Core processors.
+These are the `-m' options defined for the Motorola M*Core processors.
-'-mhardlit'
-'-mno-hardlit'
+`-mhardlit'
+`-mno-hardlit'
Inline constants into the code stream if it can be done in two
instructions or less.
-'-mdiv'
-'-mno-div'
+`-mdiv'
+`-mno-div'
Use the divide instruction. (Enabled by default).
-'-mrelax-immediate'
-'-mno-relax-immediate'
+`-mrelax-immediate'
+`-mno-relax-immediate'
Allow arbitrary-sized immediates in bit operations.
-'-mwide-bitfields'
-'-mno-wide-bitfields'
- Always treat bit-fields as 'int'-sized.
+`-mwide-bitfields'
+`-mno-wide-bitfields'
+ Always treat bit-fields as `int'-sized.
-'-m4byte-functions'
-'-mno-4byte-functions'
+`-m4byte-functions'
+`-mno-4byte-functions'
Force all functions to be aligned to a 4-byte boundary.
-'-mcallgraph-data'
-'-mno-callgraph-data'
+`-mcallgraph-data'
+`-mno-callgraph-data'
Emit callgraph information.
-'-mslow-bytes'
-'-mno-slow-bytes'
+`-mslow-bytes'
+`-mno-slow-bytes'
Prefer word access when reading byte quantities.
-'-mlittle-endian'
-'-mbig-endian'
+`-mlittle-endian'
+`-mbig-endian'
Generate code for a little-endian target.
-'-m210'
-'-m340'
+`-m210'
+`-m340'
Generate code for the 210 processor.
-'-mno-lsim'
+`-mno-lsim'
Assume that runtime support has been provided and so omit the
- simulator library ('libsim.a)' from the linker command line.
+ simulator library (`libsim.a)' from the linker command line.
-'-mstack-increment=SIZE'
+`-mstack-increment=SIZE'
Set the maximum amount for a single stack increment operation.
Large values can increase the speed of programs that contain
functions that need a large amount of stack space, but they can
also trigger a segmentation fault if the stack is extended too
much. The default value is 0x1000.
+

File: gcc.info, Node: MeP Options, Next: MicroBlaze Options, Prev: MCore Options, Up: Submodel Options
3.17.23 MeP Options
-------------------
-'-mabsdiff'
- Enables the 'abs' instruction, which is the absolute difference
+`-mabsdiff'
+ Enables the `abs' instruction, which is the absolute difference
between two registers.
-'-mall-opts'
+`-mall-opts'
Enables all the optional instructions--average, multiply, divide,
bit operations, leading zero, absolute difference, min/max, clip,
and saturation.
-'-maverage'
- Enables the 'ave' instruction, which computes the average of two
+`-maverage'
+ Enables the `ave' instruction, which computes the average of two
registers.
-'-mbased=N'
- Variables of size N bytes or smaller are placed in the '.based'
- section by default. Based variables use the '$tp' register as a
- base register, and there is a 128-byte limit to the '.based'
+`-mbased=N'
+ Variables of size N bytes or smaller are placed in the `.based'
+ section by default. Based variables use the `$tp' register as a
+ base register, and there is a 128-byte limit to the `.based'
section.
-'-mbitops'
- Enables the bit operation instructions--bit test ('btstm'), set
- ('bsetm'), clear ('bclrm'), invert ('bnotm'), and test-and-set
- ('tas').
+`-mbitops'
+ Enables the bit operation instructions--bit test (`btstm'), set
+ (`bsetm'), clear (`bclrm'), invert (`bnotm'), and test-and-set
+ (`tas').
-'-mc=NAME'
+`-mc=NAME'
Selects which section constant data is placed in. NAME may be
- 'tiny', 'near', or 'far'.
+ `tiny', `near', or `far'.
-'-mclip'
- Enables the 'clip' instruction. Note that '-mclip' is not useful
- unless you also provide '-mminmax'.
+`-mclip'
+ Enables the `clip' instruction. Note that `-mclip' is not useful
+ unless you also provide `-mminmax'.
-'-mconfig=NAME'
+`-mconfig=NAME'
Selects one of the built-in core configurations. Each MeP chip has
- one or more modules in it; each module has a core CPU and a variety
- of coprocessors, optional instructions, and peripherals. The
- 'MeP-Integrator' tool, not part of GCC, provides these
+ one or more modules in it; each module has a core CPU and a
+ variety of coprocessors, optional instructions, and peripherals.
+ The `MeP-Integrator' tool, not part of GCC, provides these
configurations through this option; using this option is the same
as using all the corresponding command-line options. The default
- configuration is 'default'.
+ configuration is `default'.
-'-mcop'
+`-mcop'
Enables the coprocessor instructions. By default, this is a 32-bit
coprocessor. Note that the coprocessor is normally enabled via the
- '-mconfig=' option.
+ `-mconfig=' option.
-'-mcop32'
+`-mcop32'
Enables the 32-bit coprocessor's instructions.
-'-mcop64'
+`-mcop64'
Enables the 64-bit coprocessor's instructions.
-'-mivc2'
+`-mivc2'
Enables IVC2 scheduling. IVC2 is a 64-bit VLIW coprocessor.
-'-mdc'
- Causes constant variables to be placed in the '.near' section.
+`-mdc'
+ Causes constant variables to be placed in the `.near' section.
-'-mdiv'
- Enables the 'div' and 'divu' instructions.
+`-mdiv'
+ Enables the `div' and `divu' instructions.
-'-meb'
+`-meb'
Generate big-endian code.
-'-mel'
+`-mel'
Generate little-endian code.
-'-mio-volatile'
- Tells the compiler that any variable marked with the 'io' attribute
- is to be considered volatile.
+`-mio-volatile'
+ Tells the compiler that any variable marked with the `io'
+ attribute is to be considered volatile.
-'-ml'
- Causes variables to be assigned to the '.far' section by default.
+`-ml'
+ Causes variables to be assigned to the `.far' section by default.
-'-mleadz'
- Enables the 'leadz' (leading zero) instruction.
+`-mleadz'
+ Enables the `leadz' (leading zero) instruction.
-'-mm'
- Causes variables to be assigned to the '.near' section by default.
+`-mm'
+ Causes variables to be assigned to the `.near' section by default.
-'-mminmax'
- Enables the 'min' and 'max' instructions.
+`-mminmax'
+ Enables the `min' and `max' instructions.
-'-mmult'
+`-mmult'
Enables the multiplication and multiply-accumulate instructions.
-'-mno-opts'
- Disables all the optional instructions enabled by '-mall-opts'.
+`-mno-opts'
+ Disables all the optional instructions enabled by `-mall-opts'.
-'-mrepeat'
- Enables the 'repeat' and 'erepeat' instructions, used for
+`-mrepeat'
+ Enables the `repeat' and `erepeat' instructions, used for
low-overhead looping.
-'-ms'
- Causes all variables to default to the '.tiny' section. Note that
+`-ms'
+ Causes all variables to default to the `.tiny' section. Note that
there is a 65536-byte limit to this section. Accesses to these
- variables use the '%gp' base register.
+ variables use the `%gp' base register.
-'-msatur'
+`-msatur'
Enables the saturation instructions. Note that the compiler does
not currently generate these itself, but this option is included
- for compatibility with other tools, like 'as'.
+ for compatibility with other tools, like `as'.
-'-msdram'
+`-msdram'
Link the SDRAM-based runtime instead of the default ROM-based
runtime.
-'-msim'
+`-msim'
Link the simulator run-time libraries.
-'-msimnovec'
+`-msimnovec'
Link the simulator runtime libraries, excluding built-in support
for reset and exception vectors and tables.
-'-mtf'
- Causes all functions to default to the '.far' section. Without
- this option, functions default to the '.near' section.
+`-mtf'
+ Causes all functions to default to the `.far' section. Without
+ this option, functions default to the `.near' section.
+
+`-mtiny=N'
+ Variables that are N bytes or smaller are allocated to the `.tiny'
+ section. These variables use the `$gp' base register. The
+ default for this option is 4, but note that there's a 65536-byte
+ limit to the `.tiny' section.
-'-mtiny=N'
- Variables that are N bytes or smaller are allocated to the '.tiny'
- section. These variables use the '$gp' base register. The default
- for this option is 4, but note that there's a 65536-byte limit to
- the '.tiny' section.

File: gcc.info, Node: MicroBlaze Options, Next: MIPS Options, Prev: MeP Options, Up: Submodel Options
@@ -15715,91 +15792,92 @@ File: gcc.info, Node: MicroBlaze Options, Next: MIPS Options, Prev: MeP Optio
3.17.24 MicroBlaze Options
--------------------------
-'-msoft-float'
+`-msoft-float'
Use software emulation for floating point (default).
-'-mhard-float'
+`-mhard-float'
Use hardware floating-point instructions.
-'-mmemcpy'
- Do not optimize block moves, use 'memcpy'.
+`-mmemcpy'
+ Do not optimize block moves, use `memcpy'.
-'-mno-clearbss'
- This option is deprecated. Use '-fno-zero-initialized-in-bss'
+`-mno-clearbss'
+ This option is deprecated. Use `-fno-zero-initialized-in-bss'
instead.
-'-mcpu=CPU-TYPE'
- Use features of, and schedule code for, the given CPU. Supported
- values are in the format 'vX.YY.Z', where X is a major version, YY
+`-mcpu=CPU-TYPE'
+ Use features of, and schedule code for, the given CPU. Supported
+ values are in the format `vX.YY.Z', where X is a major version, YY
is the minor version, and Z is compatibility code. Example values
- are 'v3.00.a', 'v4.00.b', 'v5.00.a', 'v5.00.b', 'v5.00.b',
- 'v6.00.a'.
+ are `v3.00.a', `v4.00.b', `v5.00.a', `v5.00.b', `v5.00.b',
+ `v6.00.a'.
-'-mxl-soft-mul'
+`-mxl-soft-mul'
Use software multiply emulation (default).
-'-mxl-soft-div'
+`-mxl-soft-div'
Use software emulation for divides (default).
-'-mxl-barrel-shift'
+`-mxl-barrel-shift'
Use the hardware barrel shifter.
-'-mxl-pattern-compare'
+`-mxl-pattern-compare'
Use pattern compare instructions.
-'-msmall-divides'
+`-msmall-divides'
Use table lookup optimization for small signed integer divisions.
-'-mxl-stack-check'
- This option is deprecated. Use '-fstack-check' instead.
+`-mxl-stack-check'
+ This option is deprecated. Use `-fstack-check' instead.
-'-mxl-gp-opt'
- Use GP-relative '.sdata'/'.sbss' sections.
+`-mxl-gp-opt'
+ Use GP-relative `.sdata'/`.sbss' sections.
-'-mxl-multiply-high'
+`-mxl-multiply-high'
Use multiply high instructions for high part of 32x32 multiply.
-'-mxl-float-convert'
+`-mxl-float-convert'
Use hardware floating-point conversion instructions.
-'-mxl-float-sqrt'
+`-mxl-float-sqrt'
Use hardware floating-point square root instruction.
-'-mbig-endian'
+`-mbig-endian'
Generate code for a big-endian target.
-'-mlittle-endian'
+`-mlittle-endian'
Generate code for a little-endian target.
-'-mxl-reorder'
+`-mxl-reorder'
Use reorder instructions (swap and byte reversed load/store).
-'-mxl-mode-APP-MODEL'
+`-mxl-mode-APP-MODEL'
Select application model APP-MODEL. Valid models are
- 'executable'
- normal executable (default), uses startup code 'crt0.o'.
+ `executable'
+ normal executable (default), uses startup code `crt0.o'.
- 'xmdstub'
+ `xmdstub'
for use with Xilinx Microprocessor Debugger (XMD) based
- software intrusive debug agent called xmdstub. This uses
- startup file 'crt1.o' and sets the start address of the
+ software intrusive debug agent called xmdstub. This uses
+ startup file `crt1.o' and sets the start address of the
program to 0x800.
- 'bootstrap'
+ `bootstrap'
for applications that are loaded using a bootloader. This
- model uses startup file 'crt2.o' which does not contain a
- processor reset vector handler. This is suitable for
+ model uses startup file `crt2.o' which does not contain a
+ processor reset vector handler. This is suitable for
transferring control on a processor reset to the bootloader
rather than the application.
- 'novectors'
+ `novectors'
for applications that do not require any of the MicroBlaze
- vectors. This option may be useful for applications running
- within a monitoring application. This model uses 'crt3.o' as
+ vectors. This option may be useful for applications running
+ within a monitoring application. This model uses `crt3.o' as
a startup file.
- Option '-xl-mode-APP-MODEL' is a deprecated alias for
- '-mxl-mode-APP-MODEL'.
+ Option `-xl-mode-APP-MODEL' is a deprecated alias for
+ `-mxl-mode-APP-MODEL'.
+

File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Options, Up: Submodel Options
@@ -15807,227 +15885,231 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
3.17.25 MIPS Options
--------------------
-'-EB'
+`-EB'
Generate big-endian code.
-'-EL'
- Generate little-endian code. This is the default for 'mips*el-*-*'
+`-EL'
+ Generate little-endian code. This is the default for `mips*el-*-*'
configurations.
-'-march=ARCH'
- Generate code that runs on ARCH, which can be the name of a generic
- MIPS ISA, or the name of a particular processor. The ISA names
- are: 'mips1', 'mips2', 'mips3', 'mips4', 'mips32', 'mips32r2',
- 'mips32r3', 'mips32r5', 'mips32r6', 'mips64', 'mips64r2',
- 'mips64r3', 'mips64r5' and 'mips64r6'. The processor names are:
- '4kc', '4km', '4kp', '4ksc', '4kec', '4kem', '4kep', '4ksd', '5kc',
- '5kf', '20kc', '24kc', '24kf2_1', '24kf1_1', '24kec', '24kef2_1',
- '24kef1_1', '34kc', '34kf2_1', '34kf1_1', '34kn', '74kc',
- '74kf2_1', '74kf1_1', '74kf3_2', '1004kc', '1004kf2_1',
- '1004kf1_1', 'loongson2e', 'loongson2f', 'loongson3a', 'm4k',
- 'm14k', 'm14kc', 'm14ke', 'm14kec', 'octeon', 'octeon+', 'octeon2',
- 'octeon3', 'orion', 'p5600', 'r2000', 'r3000', 'r3900', 'r4000',
- 'r4400', 'r4600', 'r4650', 'r4700', 'r6000', 'r8000', 'rm7000',
- 'rm9000', 'r10000', 'r12000', 'r14000', 'r16000', 'sb1', 'sr71000',
- 'vr4100', 'vr4111', 'vr4120', 'vr4130', 'vr4300', 'vr5000',
- 'vr5400', 'vr5500', 'xlr' and 'xlp'. The special value 'from-abi'
- selects the most compatible architecture for the selected ABI (that
- is, 'mips1' for 32-bit ABIs and 'mips3' for 64-bit ABIs).
-
- The native Linux/GNU toolchain also supports the value 'native',
+`-march=ARCH'
+ Generate code that runs on ARCH, which can be the name of a
+ generic MIPS ISA, or the name of a particular processor. The ISA
+ names are: `mips1', `mips2', `mips3', `mips4', `mips32',
+ `mips32r2', `mips32r3', `mips32r5', `mips32r6', `mips64',
+ `mips64r2', `mips64r3', `mips64r5' and `mips64r6'. The processor
+ names are: `4kc', `4km', `4kp', `4ksc', `4kec', `4kem', `4kep',
+ `4ksd', `5kc', `5kf', `20kc', `24kc', `24kf2_1', `24kf1_1',
+ `24kec', `24kef2_1', `24kef1_1', `34kc', `34kf2_1', `34kf1_1',
+ `34kn', `74kc', `74kf2_1', `74kf1_1', `74kf3_2', `1004kc',
+ `1004kf2_1', `1004kf1_1', `loongson2e', `loongson2f', `loongson3a',
+ `m4k', `m14k', `m14kc', `m14ke', `m14kec', `octeon', `octeon+',
+ `octeon2', `octeon3', `orion', `p5600', `r2000', `r3000', `r3900',
+ `r4000', `r4400', `r4600', `r4650', `r4700', `r6000', `r8000',
+ `rm7000', `rm9000', `r10000', `r12000', `r14000', `r16000', `sb1',
+ `sr71000', `vr4100', `vr4111', `vr4120', `vr4130', `vr4300',
+ `vr5000', `vr5400', `vr5500', `xlr' and `xlp'. The special value
+ `from-abi' selects the most compatible architecture for the
+ selected ABI (that is, `mips1' for 32-bit ABIs and `mips3' for
+ 64-bit ABIs).
+
+ The native Linux/GNU toolchain also supports the value `native',
which selects the best architecture option for the host processor.
- '-march=native' has no effect if GCC does not recognize the
+ `-march=native' has no effect if GCC does not recognize the
processor.
- In processor names, a final '000' can be abbreviated as 'k' (for
- example, '-march=r2k'). Prefixes are optional, and 'vr' may be
- written 'r'.
+ In processor names, a final `000' can be abbreviated as `k' (for
+ example, `-march=r2k'). Prefixes are optional, and `vr' may be
+ written `r'.
- Names of the form 'Nf2_1' refer to processors with FPUs clocked at
- half the rate of the core, names of the form 'Nf1_1' refer to
+ Names of the form `Nf2_1' refer to processors with FPUs clocked at
+ half the rate of the core, names of the form `Nf1_1' refer to
processors with FPUs clocked at the same rate as the core, and
- names of the form 'Nf3_2' refer to processors with FPUs clocked a
+ names of the form `Nf3_2' refer to processors with FPUs clocked a
ratio of 3:2 with respect to the core. For compatibility reasons,
- 'Nf' is accepted as a synonym for 'Nf2_1' while 'Nx' and 'Bfx' are
- accepted as synonyms for 'Nf1_1'.
+ `Nf' is accepted as a synonym for `Nf2_1' while `Nx' and `Bfx' are
+ accepted as synonyms for `Nf1_1'.
GCC defines two macros based on the value of this option. The
- first is '_MIPS_ARCH', which gives the name of target architecture,
- as a string. The second has the form '_MIPS_ARCH_FOO', where FOO
- is the capitalized value of '_MIPS_ARCH'. For example,
- '-march=r2000' sets '_MIPS_ARCH' to '"r2000"' and defines the macro
- '_MIPS_ARCH_R2000'.
+ first is `_MIPS_ARCH', which gives the name of target
+ architecture, as a string. The second has the form
+ `_MIPS_ARCH_FOO', where FOO is the capitalized value of
+ `_MIPS_ARCH'. For example, `-march=r2000' sets `_MIPS_ARCH' to
+ `"r2000"' and defines the macro `_MIPS_ARCH_R2000'.
- Note that the '_MIPS_ARCH' macro uses the processor names given
+ Note that the `_MIPS_ARCH' macro uses the processor names given
above. In other words, it has the full prefix and does not
- abbreviate '000' as 'k'. In the case of 'from-abi', the macro
- names the resolved architecture (either '"mips1"' or '"mips3"').
- It names the default architecture when no '-march' option is given.
+ abbreviate `000' as `k'. In the case of `from-abi', the macro
+ names the resolved architecture (either `"mips1"' or `"mips3"').
+ It names the default architecture when no `-march' option is given.
-'-mtune=ARCH'
+`-mtune=ARCH'
Optimize for ARCH. Among other things, this option controls the
way instructions are scheduled, and the perceived cost of
arithmetic operations. The list of ARCH values is the same as for
- '-march'.
+ `-march'.
When this option is not used, GCC optimizes for the processor
- specified by '-march'. By using '-march' and '-mtune' together, it
- is possible to generate code that runs on a family of processors,
- but optimize the code for one particular member of that family.
+ specified by `-march'. By using `-march' and `-mtune' together,
+ it is possible to generate code that runs on a family of
+ processors, but optimize the code for one particular member of
+ that family.
- '-mtune' defines the macros '_MIPS_TUNE' and '_MIPS_TUNE_FOO',
- which work in the same way as the '-march' ones described above.
+ `-mtune' defines the macros `_MIPS_TUNE' and `_MIPS_TUNE_FOO',
+ which work in the same way as the `-march' ones described above.
-'-mips1'
- Equivalent to '-march=mips1'.
+`-mips1'
+ Equivalent to `-march=mips1'.
-'-mips2'
- Equivalent to '-march=mips2'.
+`-mips2'
+ Equivalent to `-march=mips2'.
-'-mips3'
- Equivalent to '-march=mips3'.
+`-mips3'
+ Equivalent to `-march=mips3'.
-'-mips4'
- Equivalent to '-march=mips4'.
+`-mips4'
+ Equivalent to `-march=mips4'.
-'-mips32'
- Equivalent to '-march=mips32'.
+`-mips32'
+ Equivalent to `-march=mips32'.
-'-mips32r3'
- Equivalent to '-march=mips32r3'.
+`-mips32r3'
+ Equivalent to `-march=mips32r3'.
-'-mips32r5'
- Equivalent to '-march=mips32r5'.
+`-mips32r5'
+ Equivalent to `-march=mips32r5'.
-'-mips32r6'
- Equivalent to '-march=mips32r6'.
+`-mips32r6'
+ Equivalent to `-march=mips32r6'.
-'-mips64'
- Equivalent to '-march=mips64'.
+`-mips64'
+ Equivalent to `-march=mips64'.
-'-mips64r2'
- Equivalent to '-march=mips64r2'.
+`-mips64r2'
+ Equivalent to `-march=mips64r2'.
-'-mips64r3'
- Equivalent to '-march=mips64r3'.
+`-mips64r3'
+ Equivalent to `-march=mips64r3'.
-'-mips64r5'
- Equivalent to '-march=mips64r5'.
+`-mips64r5'
+ Equivalent to `-march=mips64r5'.
-'-mips64r6'
- Equivalent to '-march=mips64r6'.
+`-mips64r6'
+ Equivalent to `-march=mips64r6'.
-'-mips16'
-'-mno-mips16'
+`-mips16'
+`-mno-mips16'
Generate (do not generate) MIPS16 code. If GCC is targeting a
MIPS32 or MIPS64 architecture, it makes use of the MIPS16e ASE.
MIPS16 code generation can also be controlled on a per-function
- basis by means of 'mips16' and 'nomips16' attributes. *Note
+ basis by means of `mips16' and `nomips16' attributes. *Note
Function Attributes::, for more information.
-'-mflip-mips16'
+`-mflip-mips16'
Generate MIPS16 code on alternating functions. This option is
provided for regression testing of mixed MIPS16/non-MIPS16 code
generation, and is not intended for ordinary use in compiling user
code.
-'-minterlink-compressed'
-'-mno-interlink-compressed'
+`-minterlink-compressed'
+
+`-mno-interlink-compressed'
Require (do not require) that code using the standard
(uncompressed) MIPS ISA be link-compatible with MIPS16 and
microMIPS code, and vice versa.
For example, code using the standard ISA encoding cannot jump
directly to MIPS16 or microMIPS code; it must either use a call or
- an indirect jump. '-minterlink-compressed' therefore disables
+ an indirect jump. `-minterlink-compressed' therefore disables
direct jumps unless GCC knows that the target of the jump is not
compressed.
-'-minterlink-mips16'
-'-mno-interlink-mips16'
- Aliases of '-minterlink-compressed' and
- '-mno-interlink-compressed'. These options predate the microMIPS
+`-minterlink-mips16'
+`-mno-interlink-mips16'
+ Aliases of `-minterlink-compressed' and
+ `-mno-interlink-compressed'. These options predate the microMIPS
ASE and are retained for backwards compatibility.
-'-mabi=32'
-'-mabi=o64'
-'-mabi=n32'
-'-mabi=64'
-'-mabi=eabi'
+`-mabi=32'
+`-mabi=o64'
+`-mabi=n32'
+`-mabi=64'
+`-mabi=eabi'
Generate code for the given ABI.
Note that the EABI has a 32-bit and a 64-bit variant. GCC normally
generates 64-bit code when you select a 64-bit architecture, but
- you can use '-mgp32' to get 32-bit code instead.
+ you can use `-mgp32' to get 32-bit code instead.
For information about the O64 ABI, see
- <http://gcc.gnu.org/projects/mipso64-abi.html>.
+ `http://gcc.gnu.org/projects/mipso64-abi.html'.
GCC supports a variant of the o32 ABI in which floating-point
registers are 64 rather than 32 bits wide. You can select this
- combination with '-mabi=32' '-mfp64'. This ABI relies on the
- 'mthc1' and 'mfhc1' instructions and is therefore only supported
+ combination with `-mabi=32' `-mfp64'. This ABI relies on the
+ `mthc1' and `mfhc1' instructions and is therefore only supported
for MIPS32R2, MIPS32R3 and MIPS32R5 processors.
The register assignments for arguments and return values remain the
same, but each scalar value is passed in a single 64-bit register
rather than a pair of 32-bit registers. For example, scalar
- floating-point values are returned in '$f0' only, not a '$f0'/'$f1'
- pair. The set of call-saved registers also remains the same in
- that the even-numbered double-precision registers are saved.
+ floating-point values are returned in `$f0' only, not a
+ `$f0'/`$f1' pair. The set of call-saved registers also remains
+ the same in that the even-numbered double-precision registers are
+ saved.
Two additional variants of the o32 ABI are supported to enable a
transition from 32-bit to 64-bit registers. These are FPXX
- ('-mfpxx') and FP64A ('-mfp64' '-mno-odd-spreg'). The FPXX
+ (`-mfpxx') and FP64A (`-mfp64' `-mno-odd-spreg'). The FPXX
extension mandates that all code must execute correctly when run
- using 32-bit or 64-bit registers. The code can be interlinked with
- either FP32 or FP64, but not both. The FP64A extension is similar
- to the FP64 extension but forbids the use of odd-numbered
+ using 32-bit or 64-bit registers. The code can be interlinked
+ with either FP32 or FP64, but not both. The FP64A extension is
+ similar to the FP64 extension but forbids the use of odd-numbered
single-precision registers. This can be used in conjunction with
- the 'FRE' mode of FPUs in MIPS32R5 processors and allows both FP32
+ the `FRE' mode of FPUs in MIPS32R5 processors and allows both FP32
and FP64A code to interlink and run in the same process without
changing FPU modes.
-'-mabicalls'
-'-mno-abicalls'
+`-mabicalls'
+`-mno-abicalls'
Generate (do not generate) code that is suitable for SVR4-style
- dynamic objects. '-mabicalls' is the default for SVR4-based
+ dynamic objects. `-mabicalls' is the default for SVR4-based
systems.
-'-mshared'
-'-mno-shared'
+`-mshared'
+`-mno-shared'
Generate (do not generate) code that is fully position-independent,
and that can therefore be linked into shared libraries. This
- option only affects '-mabicalls'.
+ option only affects `-mabicalls'.
- All '-mabicalls' code has traditionally been position-independent,
- regardless of options like '-fPIC' and '-fpic'. However, as an
+ All `-mabicalls' code has traditionally been position-independent,
+ regardless of options like `-fPIC' and `-fpic'. However, as an
extension, the GNU toolchain allows executables to use absolute
accesses for locally-binding symbols. It can also use shorter GP
initialization sequences and generate direct calls to
- locally-defined functions. This mode is selected by '-mno-shared'.
+ locally-defined functions. This mode is selected by `-mno-shared'.
- '-mno-shared' depends on binutils 2.16 or higher and generates
+ `-mno-shared' depends on binutils 2.16 or higher and generates
objects that can only be linked by the GNU linker. However, the
option does not affect the ABI of the final executable; it only
- affects the ABI of relocatable objects. Using '-mno-shared'
+ affects the ABI of relocatable objects. Using `-mno-shared'
generally makes executables both smaller and quicker.
- '-mshared' is the default.
+ `-mshared' is the default.
-'-mplt'
-'-mno-plt'
+`-mplt'
+`-mno-plt'
Assume (do not assume) that the static and dynamic linkers support
- PLTs and copy relocations. This option only affects '-mno-shared
+ PLTs and copy relocations. This option only affects `-mno-shared
-mabicalls'. For the n64 ABI, this option has no effect without
- '-msym32'.
+ `-msym32'.
- You can make '-mplt' the default by configuring GCC with
- '--with-mips-plt'. The default is '-mno-plt' otherwise.
+ You can make `-mplt' the default by configuring GCC with
+ `--with-mips-plt'. The default is `-mno-plt' otherwise.
-'-mxgot'
-'-mno-xgot'
+`-mxgot'
+`-mno-xgot'
Lift (do not lift) the usual restrictions on the size of the global
offset table.
@@ -16038,283 +16120,284 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
relocation truncated to fit: R_MIPS_GOT16 foobar
- If this happens, you should recompile your code with '-mxgot'.
+ If this happens, you should recompile your code with `-mxgot'.
This works with very large GOTs, although the code is also less
efficient, since it takes three instructions to fetch the value of
a global symbol.
Note that some linkers can create multiple GOTs. If you have such
- a linker, you should only need to use '-mxgot' when a single object
+ a linker, you should only need to use `-mxgot' when a single object
file accesses more than 64k's worth of GOT entries. Very few do.
These options have no effect unless GCC is generating position
independent code.
-'-mgp32'
+`-mgp32'
Assume that general-purpose registers are 32 bits wide.
-'-mgp64'
+`-mgp64'
Assume that general-purpose registers are 64 bits wide.
-'-mfp32'
+`-mfp32'
Assume that floating-point registers are 32 bits wide.
-'-mfp64'
+`-mfp64'
Assume that floating-point registers are 64 bits wide.
-'-mfpxx'
+`-mfpxx'
Do not assume the width of floating-point registers.
-'-mhard-float'
+`-mhard-float'
Use floating-point coprocessor instructions.
-'-msoft-float'
+`-msoft-float'
Do not use floating-point coprocessor instructions. Implement
floating-point calculations using library calls instead.
-'-mno-float'
- Equivalent to '-msoft-float', but additionally asserts that the
+`-mno-float'
+ Equivalent to `-msoft-float', but additionally asserts that the
program being compiled does not perform any floating-point
operations. This option is presently supported only by some
bare-metal MIPS configurations, where it may select a special set
of libraries that lack all floating-point support (including, for
- example, the floating-point 'printf' formats). If code compiled
- with '-mno-float' accidentally contains floating-point operations,
+ example, the floating-point `printf' formats). If code compiled
+ with `-mno-float' accidentally contains floating-point operations,
it is likely to suffer a link-time or run-time failure.
-'-msingle-float'
+`-msingle-float'
Assume that the floating-point coprocessor only supports
single-precision operations.
-'-mdouble-float'
+`-mdouble-float'
Assume that the floating-point coprocessor supports
double-precision operations. This is the default.
-'-modd-spreg'
-'-mno-odd-spreg'
+`-modd-spreg'
+`-mno-odd-spreg'
Enable the use of odd-numbered single-precision floating-point
- registers for the o32 ABI. This is the default for processors that
- are known to support these registers. When using the o32 FPXX ABI,
- '-mno-odd-spreg' is set by default.
+ registers for the o32 ABI. This is the default for processors
+ that are known to support these registers. When using the o32
+ FPXX ABI, `-mno-odd-spreg' is set by default.
-'-mabs=2008'
-'-mabs=legacy'
+`-mabs=2008'
+`-mabs=legacy'
These options control the treatment of the special not-a-number
- (NaN) IEEE 754 floating-point data with the 'abs.fmt' and 'neg.fmt'
- machine instructions.
+ (NaN) IEEE 754 floating-point data with the `abs.fmt' and
+ `neg.fmt' machine instructions.
- By default or when '-mabs=legacy' is used the legacy treatment is
+ By default or when `-mabs=legacy' is used the legacy treatment is
selected. In this case these instructions are considered
arithmetic and avoided where correct operation is required and the
- input operand might be a NaN. A longer sequence of instructions
+ input operand might be a NaN. A longer sequence of instructions
that manipulate the sign bit of floating-point datum manually is
- used instead unless the '-ffinite-math-only' option has also been
+ used instead unless the `-ffinite-math-only' option has also been
specified.
- The '-mabs=2008' option selects the IEEE 754-2008 treatment. In
+ The `-mabs=2008' option selects the IEEE 754-2008 treatment. In
this case these instructions are considered non-arithmetic and
- therefore operating correctly in all cases, including in particular
- where the input operand is a NaN. These instructions are therefore
- always used for the respective operations.
+ therefore operating correctly in all cases, including in
+ particular where the input operand is a NaN. These instructions
+ are therefore always used for the respective operations.
-'-mnan=2008'
-'-mnan=legacy'
+`-mnan=2008'
+`-mnan=legacy'
These options control the encoding of the special not-a-number
(NaN) IEEE 754 floating-point data.
- The '-mnan=legacy' option selects the legacy encoding. In this
+ The `-mnan=legacy' option selects the legacy encoding. In this
case quiet NaNs (qNaNs) are denoted by the first bit of their
- trailing significand field being 0, whereas signalling NaNs (sNaNs)
- are denoted by the first bit of their trailing significand field
- being 1.
+ trailing significand field being 0, whereas signalling NaNs
+ (sNaNs) are denoted by the first bit of their trailing significand
+ field being 1.
- The '-mnan=2008' option selects the IEEE 754-2008 encoding. In
+ The `-mnan=2008' option selects the IEEE 754-2008 encoding. In
this case qNaNs are denoted by the first bit of their trailing
significand field being 1, whereas sNaNs are denoted by the first
bit of their trailing significand field being 0.
- The default is '-mnan=legacy' unless GCC has been configured with
- '--with-nan=2008'.
+ The default is `-mnan=legacy' unless GCC has been configured with
+ `--with-nan=2008'.
-'-mllsc'
-'-mno-llsc'
- Use (do not use) 'll', 'sc', and 'sync' instructions to implement
+`-mllsc'
+`-mno-llsc'
+ Use (do not use) `ll', `sc', and `sync' instructions to implement
atomic memory built-in functions. When neither option is
specified, GCC uses the instructions if the target architecture
supports them.
- '-mllsc' is useful if the runtime environment can emulate the
- instructions and '-mno-llsc' can be useful when compiling for
+ `-mllsc' is useful if the runtime environment can emulate the
+ instructions and `-mno-llsc' can be useful when compiling for
nonstandard ISAs. You can make either option the default by
- configuring GCC with '--with-llsc' and '--without-llsc'
- respectively. '--with-llsc' is the default for some
+ configuring GCC with `--with-llsc' and `--without-llsc'
+ respectively. `--with-llsc' is the default for some
configurations; see the installation documentation for details.
-'-mdsp'
-'-mno-dsp'
+`-mdsp'
+`-mno-dsp'
Use (do not use) revision 1 of the MIPS DSP ASE. *Note MIPS DSP
Built-in Functions::. This option defines the preprocessor macro
- '__mips_dsp'. It also defines '__mips_dsp_rev' to 1.
+ `__mips_dsp'. It also defines `__mips_dsp_rev' to 1.
-'-mdspr2'
-'-mno-dspr2'
+`-mdspr2'
+`-mno-dspr2'
Use (do not use) revision 2 of the MIPS DSP ASE. *Note MIPS DSP
Built-in Functions::. This option defines the preprocessor macros
- '__mips_dsp' and '__mips_dspr2'. It also defines '__mips_dsp_rev'
+ `__mips_dsp' and `__mips_dspr2'. It also defines `__mips_dsp_rev'
to 2.
-'-msmartmips'
-'-mno-smartmips'
+`-msmartmips'
+`-mno-smartmips'
Use (do not use) the MIPS SmartMIPS ASE.
-'-mpaired-single'
-'-mno-paired-single'
+`-mpaired-single'
+`-mno-paired-single'
Use (do not use) paired-single floating-point instructions. *Note
MIPS Paired-Single Support::. This option requires hardware
floating-point support to be enabled.
-'-mdmx'
-'-mno-mdmx'
+`-mdmx'
+`-mno-mdmx'
Use (do not use) MIPS Digital Media Extension instructions. This
option can only be used when generating 64-bit code and requires
hardware floating-point support to be enabled.
-'-mips3d'
-'-mno-mips3d'
+`-mips3d'
+`-mno-mips3d'
Use (do not use) the MIPS-3D ASE. *Note MIPS-3D Built-in
- Functions::. The option '-mips3d' implies '-mpaired-single'.
+ Functions::. The option `-mips3d' implies `-mpaired-single'.
-'-mmicromips'
-'-mno-micromips'
+`-mmicromips'
+`-mno-micromips'
Generate (do not generate) microMIPS code.
MicroMIPS code generation can also be controlled on a per-function
- basis by means of 'micromips' and 'nomicromips' attributes. *Note
+ basis by means of `micromips' and `nomicromips' attributes. *Note
Function Attributes::, for more information.
-'-mmt'
-'-mno-mt'
+`-mmt'
+`-mno-mt'
Use (do not use) MT Multithreading instructions.
-'-mmcu'
-'-mno-mcu'
+`-mmcu'
+`-mno-mcu'
Use (do not use) the MIPS MCU ASE instructions.
-'-meva'
-'-mno-eva'
+`-meva'
+`-mno-eva'
Use (do not use) the MIPS Enhanced Virtual Addressing instructions.
-'-mvirt'
-'-mno-virt'
+`-mvirt'
+`-mno-virt'
Use (do not use) the MIPS Virtualization Application Specific
instructions.
-'-mxpa'
-'-mno-xpa'
+`-mxpa'
+`-mno-xpa'
Use (do not use) the MIPS eXtended Physical Address (XPA)
instructions.
-'-mlong64'
- Force 'long' types to be 64 bits wide. See '-mlong32' for an
+`-mlong64'
+ Force `long' types to be 64 bits wide. See `-mlong32' for an
explanation of the default and the way that the pointer size is
determined.
-'-mlong32'
- Force 'long', 'int', and pointer types to be 32 bits wide.
+`-mlong32'
+ Force `long', `int', and pointer types to be 32 bits wide.
- The default size of 'int's, 'long's and pointers depends on the
- ABI. All the supported ABIs use 32-bit 'int's. The n64 ABI uses
- 64-bit 'long's, as does the 64-bit EABI; the others use 32-bit
- 'long's. Pointers are the same size as 'long's, or the same size
+ The default size of `int's, `long's and pointers depends on the
+ ABI. All the supported ABIs use 32-bit `int's. The n64 ABI uses
+ 64-bit `long's, as does the 64-bit EABI; the others use 32-bit
+ `long's. Pointers are the same size as `long's, or the same size
as integer registers, whichever is smaller.
-'-msym32'
-'-mno-sym32'
+`-msym32'
+`-mno-sym32'
Assume (do not assume) that all symbols have 32-bit values,
regardless of the selected ABI. This option is useful in
- combination with '-mabi=64' and '-mno-abicalls' because it allows
+ combination with `-mabi=64' and `-mno-abicalls' because it allows
GCC to generate shorter and faster references to symbolic
addresses.
-'-G NUM'
+`-G NUM'
Put definitions of externally-visible data in a small data section
if that data is no bigger than NUM bytes. GCC can then generate
- more efficient accesses to the data; see '-mgpopt' for details.
+ more efficient accesses to the data; see `-mgpopt' for details.
- The default '-G' option depends on the configuration.
+ The default `-G' option depends on the configuration.
-'-mlocal-sdata'
-'-mno-local-sdata'
- Extend (do not extend) the '-G' behavior to local data too, such as
- to static variables in C. '-mlocal-sdata' is the default for all
- configurations.
+`-mlocal-sdata'
+`-mno-local-sdata'
+ Extend (do not extend) the `-G' behavior to local data too, such
+ as to static variables in C. `-mlocal-sdata' is the default for
+ all configurations.
- If the linker complains that an application is using too much small
- data, you might want to try rebuilding the less
- performance-critical parts with '-mno-local-sdata'. You might also
- want to build large libraries with '-mno-local-sdata', so that the
- libraries leave more room for the main program.
+ If the linker complains that an application is using too much
+ small data, you might want to try rebuilding the less
+ performance-critical parts with `-mno-local-sdata'. You might
+ also want to build large libraries with `-mno-local-sdata', so
+ that the libraries leave more room for the main program.
-'-mextern-sdata'
-'-mno-extern-sdata'
+`-mextern-sdata'
+`-mno-extern-sdata'
Assume (do not assume) that externally-defined data is in a small
- data section if the size of that data is within the '-G' limit.
- '-mextern-sdata' is the default for all configurations.
-
- If you compile a module MOD with '-mextern-sdata' '-G NUM'
- '-mgpopt', and MOD references a variable VAR that is no bigger than
- NUM bytes, you must make sure that VAR is placed in a small data
- section. If VAR is defined by another module, you must either
- compile that module with a high-enough '-G' setting or attach a
- 'section' attribute to VAR's definition. If VAR is common, you
- must link the application with a high-enough '-G' setting.
+ data section if the size of that data is within the `-G' limit.
+ `-mextern-sdata' is the default for all configurations.
+
+ If you compile a module MOD with `-mextern-sdata' `-G NUM'
+ `-mgpopt', and MOD references a variable VAR that is no bigger
+ than NUM bytes, you must make sure that VAR is placed in a small
+ data section. If VAR is defined by another module, you must
+ either compile that module with a high-enough `-G' setting or
+ attach a `section' attribute to VAR's definition. If VAR is
+ common, you must link the application with a high-enough `-G'
+ setting.
The easiest way of satisfying these restrictions is to compile and
- link every module with the same '-G' option. However, you may wish
- to build a library that supports several different small data
+ link every module with the same `-G' option. However, you may
+ wish to build a library that supports several different small data
limits. You can do this by compiling the library with the highest
- supported '-G' setting and additionally using '-mno-extern-sdata'
+ supported `-G' setting and additionally using `-mno-extern-sdata'
to stop the library from making assumptions about
externally-defined data.
-'-mgpopt'
-'-mno-gpopt'
- Use (do not use) GP-relative accesses for symbols that are known to
- be in a small data section; see '-G', '-mlocal-sdata' and
- '-mextern-sdata'. '-mgpopt' is the default for all configurations.
+`-mgpopt'
+`-mno-gpopt'
+ Use (do not use) GP-relative accesses for symbols that are known
+ to be in a small data section; see `-G', `-mlocal-sdata' and
+ `-mextern-sdata'. `-mgpopt' is the default for all configurations.
- '-mno-gpopt' is useful for cases where the '$gp' register might not
- hold the value of '_gp'. For example, if the code is part of a
- library that might be used in a boot monitor, programs that call
- boot monitor routines pass an unknown value in '$gp'. (In such
+ `-mno-gpopt' is useful for cases where the `$gp' register might
+ not hold the value of `_gp'. For example, if the code is part of
+ a library that might be used in a boot monitor, programs that call
+ boot monitor routines pass an unknown value in `$gp'. (In such
situations, the boot monitor itself is usually compiled with
- '-G0'.)
+ `-G0'.)
- '-mno-gpopt' implies '-mno-local-sdata' and '-mno-extern-sdata'.
+ `-mno-gpopt' implies `-mno-local-sdata' and `-mno-extern-sdata'.
-'-membedded-data'
-'-mno-embedded-data'
- Allocate variables to the read-only data section first if possible,
- then next in the small data section if possible, otherwise in data.
- This gives slightly slower code than the default, but reduces the
- amount of RAM required when executing, and thus may be preferred
- for some embedded systems.
+`-membedded-data'
+`-mno-embedded-data'
+ Allocate variables to the read-only data section first if
+ possible, then next in the small data section if possible,
+ otherwise in data. This gives slightly slower code than the
+ default, but reduces the amount of RAM required when executing,
+ and thus may be preferred for some embedded systems.
-'-muninit-const-in-rodata'
-'-mno-uninit-const-in-rodata'
- Put uninitialized 'const' variables in the read-only data section.
+`-muninit-const-in-rodata'
+`-mno-uninit-const-in-rodata'
+ Put uninitialized `const' variables in the read-only data section.
This option is only meaningful in conjunction with
- '-membedded-data'.
+ `-membedded-data'.
-'-mcode-readable=SETTING'
+`-mcode-readable=SETTING'
Specify whether GCC may generate code that reads from executable
sections. There are three possible settings:
- '-mcode-readable=yes'
+ `-mcode-readable=yes'
Instructions may freely access executable sections. This is
the default setting.
- '-mcode-readable=pcrel'
+ `-mcode-readable=pcrel'
MIPS16 PC-relative load instructions can access executable
sections, but other instructions must not do so. This option
is useful on 4KSc and 4KSd processors when the code TLBs have
@@ -16323,157 +16406,165 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
interface and that, like the M4K, automatically redirect
PC-relative loads to the instruction RAM.
- '-mcode-readable=no'
- Instructions must not access executable sections. This option
- can be useful on targets that are configured to have a dual
- instruction/data SRAM interface but that (unlike the M4K) do
- not automatically redirect PC-relative loads to the
+ `-mcode-readable=no'
+ Instructions must not access executable sections. This
+ option can be useful on targets that are configured to have a
+ dual instruction/data SRAM interface but that (unlike the
+ M4K) do not automatically redirect PC-relative loads to the
instruction RAM.
-'-msplit-addresses'
-'-mno-split-addresses'
- Enable (disable) use of the '%hi()' and '%lo()' assembler
+`-msplit-addresses'
+`-mno-split-addresses'
+ Enable (disable) use of the `%hi()' and `%lo()' assembler
relocation operators. This option has been superseded by
- '-mexplicit-relocs' but is retained for backwards compatibility.
+ `-mexplicit-relocs' but is retained for backwards compatibility.
-'-mexplicit-relocs'
-'-mno-explicit-relocs'
+`-mexplicit-relocs'
+`-mno-explicit-relocs'
Use (do not use) assembler relocation operators when dealing with
symbolic addresses. The alternative, selected by
- '-mno-explicit-relocs', is to use assembler macros instead.
+ `-mno-explicit-relocs', is to use assembler macros instead.
- '-mexplicit-relocs' is the default if GCC was configured to use an
+ `-mexplicit-relocs' is the default if GCC was configured to use an
assembler that supports relocation operators.
-'-mcheck-zero-division'
-'-mno-check-zero-division'
+`-mcheck-zero-division'
+`-mno-check-zero-division'
Trap (do not trap) on integer division by zero.
- The default is '-mcheck-zero-division'.
+ The default is `-mcheck-zero-division'.
-'-mdivide-traps'
-'-mdivide-breaks'
+`-mdivide-traps'
+`-mdivide-breaks'
MIPS systems check for division by zero by generating either a
conditional trap or a break instruction. Using traps results in
smaller code, but is only supported on MIPS II and later. Also,
some versions of the Linux kernel have a bug that prevents trap
- from generating the proper signal ('SIGFPE'). Use '-mdivide-traps'
- to allow conditional traps on architectures that support them and
- '-mdivide-breaks' to force the use of breaks.
-
- The default is usually '-mdivide-traps', but this can be overridden
- at configure time using '--with-divide=breaks'. Divide-by-zero
- checks can be completely disabled using '-mno-check-zero-division'.
-
-'-mmemcpy'
-'-mno-memcpy'
- Force (do not force) the use of 'memcpy' for non-trivial block
- moves. The default is '-mno-memcpy', which allows GCC to inline
+ from generating the proper signal (`SIGFPE'). Use
+ `-mdivide-traps' to allow conditional traps on architectures that
+ support them and `-mdivide-breaks' to force the use of breaks.
+
+ The default is usually `-mdivide-traps', but this can be
+ overridden at configure time using `--with-divide=breaks'.
+ Divide-by-zero checks can be completely disabled using
+ `-mno-check-zero-division'.
+
+`-mmemcpy'
+`-mno-memcpy'
+ Force (do not force) the use of `memcpy' for non-trivial block
+ moves. The default is `-mno-memcpy', which allows GCC to inline
most constant-sized copies.
-'-mlong-calls'
-'-mno-long-calls'
- Disable (do not disable) use of the 'jal' instruction. Calling
- functions using 'jal' is more efficient but requires the caller and
- callee to be in the same 256 megabyte segment.
+`-mlong-calls'
+`-mno-long-calls'
+ Disable (do not disable) use of the `jal' instruction. Calling
+ functions using `jal' is more efficient but requires the caller
+ and callee to be in the same 256 megabyte segment.
This option has no effect on abicalls code. The default is
- '-mno-long-calls'.
+ `-mno-long-calls'.
-'-mmad'
-'-mno-mad'
- Enable (disable) use of the 'mad', 'madu' and 'mul' instructions,
+`-mmad'
+`-mno-mad'
+ Enable (disable) use of the `mad', `madu' and `mul' instructions,
as provided by the R4650 ISA.
-'-mimadd'
-'-mno-imadd'
- Enable (disable) use of the 'madd' and 'msub' integer instructions.
- The default is '-mimadd' on architectures that support 'madd' and
- 'msub' except for the 74k architecture where it was found to
- generate slower code.
+`-mimadd'
+`-mno-imadd'
+ Enable (disable) use of the `madd' and `msub' integer
+ instructions. The default is `-mimadd' on architectures that
+ support `madd' and `msub' except for the 74k architecture where it
+ was found to generate slower code.
-'-mfused-madd'
-'-mno-fused-madd'
+`-mfused-madd'
+`-mno-fused-madd'
Enable (disable) use of the floating-point multiply-accumulate
instructions, when they are available. The default is
- '-mfused-madd'.
+ `-mfused-madd'.
On the R8000 CPU when multiply-accumulate instructions are used,
- the intermediate product is calculated to infinite precision and is
- not subject to the FCSR Flush to Zero bit. This may be undesirable
- in some circumstances. On other processors the result is
- numerically identical to the equivalent computation using separate
- multiply, add, subtract and negate instructions.
+ the intermediate product is calculated to infinite precision and
+ is not subject to the FCSR Flush to Zero bit. This may be
+ undesirable in some circumstances. On other processors the result
+ is numerically identical to the equivalent computation using
+ separate multiply, add, subtract and negate instructions.
-'-nocpp'
+`-nocpp'
Tell the MIPS assembler to not run its preprocessor over user
- assembler files (with a '.s' suffix) when assembling them.
+ assembler files (with a `.s' suffix) when assembling them.
+
+`-mfix-24k'
-'-mfix-24k'
-'-mno-fix-24k'
+`-mno-fix-24k'
Work around the 24K E48 (lost data on stores during refill) errata.
The workarounds are implemented by the assembler rather than by
GCC.
-'-mfix-r4000'
-'-mno-fix-r4000'
+`-mfix-r4000'
+`-mno-fix-r4000'
Work around certain R4000 CPU errata:
- - A double-word or a variable shift may give an incorrect result
- if executed immediately after starting an integer division.
- - A double-word or a variable shift may give an incorrect result
- if executed while an integer multiplication is in progress.
- - An integer division may give an incorrect result if started in
- a delay slot of a taken branch or a jump.
-
-'-mfix-r4400'
-'-mno-fix-r4400'
+ - A double-word or a variable shift may give an incorrect
+ result if executed immediately after starting an integer
+ division.
+
+ - A double-word or a variable shift may give an incorrect
+ result if executed while an integer multiplication is in
+ progress.
+
+ - An integer division may give an incorrect result if started
+ in a delay slot of a taken branch or a jump.
+
+`-mfix-r4400'
+`-mno-fix-r4400'
Work around certain R4400 CPU errata:
- - A double-word or a variable shift may give an incorrect result
- if executed immediately after starting an integer division.
+ - A double-word or a variable shift may give an incorrect
+ result if executed immediately after starting an integer
+ division.
-'-mfix-r10000'
-'-mno-fix-r10000'
+`-mfix-r10000'
+`-mno-fix-r10000'
Work around certain R10000 errata:
- - 'll'/'sc' sequences may not behave atomically on revisions
+ - `ll'/`sc' sequences may not behave atomically on revisions
prior to 3.0. They may deadlock on revisions 2.6 and earlier.
This option can only be used if the target architecture supports
- branch-likely instructions. '-mfix-r10000' is the default when
- '-march=r10000' is used; '-mno-fix-r10000' is the default
+ branch-likely instructions. `-mfix-r10000' is the default when
+ `-march=r10000' is used; `-mno-fix-r10000' is the default
otherwise.
-'-mfix-rm7000'
-'-mno-fix-rm7000'
- Work around the RM7000 'dmult'/'dmultu' errata. The workarounds
+`-mfix-rm7000'
+`-mno-fix-rm7000'
+ Work around the RM7000 `dmult'/`dmultu' errata. The workarounds
are implemented by the assembler rather than by GCC.
-'-mfix-vr4120'
-'-mno-fix-vr4120'
+`-mfix-vr4120'
+`-mno-fix-vr4120'
Work around certain VR4120 errata:
- - 'dmultu' does not always produce the correct result.
- - 'div' and 'ddiv' do not always produce the correct result if
+ - `dmultu' does not always produce the correct result.
+
+ - `div' and `ddiv' do not always produce the correct result if
one of the operands is negative.
The workarounds for the division errata rely on special functions
- in 'libgcc.a'. At present, these functions are only provided by
- the 'mips64vr*-elf' configurations.
+ in `libgcc.a'. At present, these functions are only provided by
+ the `mips64vr*-elf' configurations.
Other VR4120 errata require a NOP to be inserted between certain
pairs of instructions. These errata are handled by the assembler,
not by GCC itself.
-'-mfix-vr4130'
- Work around the VR4130 'mflo'/'mfhi' errata. The workarounds are
+`-mfix-vr4130'
+ Work around the VR4130 `mflo'/`mfhi' errata. The workarounds are
implemented by the assembler rather than by GCC, although GCC
- avoids using 'mflo' and 'mfhi' if the VR4130 'macc', 'macchi',
- 'dmacc' and 'dmacchi' instructions are available instead.
+ avoids using `mflo' and `mfhi' if the VR4130 `macc', `macchi',
+ `dmacc' and `dmacchi' instructions are available instead.
-'-mfix-sb1'
-'-mno-fix-sb1'
+`-mfix-sb1'
+`-mno-fix-sb1'
Work around certain SB-1 CPU core errata. (This flag currently
works around the SB-1 revision 2 "F1" and "F2" floating-point
errata.)
-'-mr10k-cache-barrier=SETTING'
+`-mr10k-cache-barrier=SETTING'
Specify whether GCC should insert cache barriers to avoid the
side-effects of speculation on R10K processors.
@@ -16485,19 +16576,19 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
This problem only affects kernel stores and, depending on the
system, kernel loads. As an example, a speculatively-executed
- store may load the target memory into cache and mark the cache line
- as dirty, even if the store itself is later aborted. If a DMA
- operation writes to the same area of memory before the "dirty" line
- is flushed, the cached data overwrites the DMA-ed data. See the
- R10K processor manual for a full description, including other
+ store may load the target memory into cache and mark the cache
+ line as dirty, even if the store itself is later aborted. If a
+ DMA operation writes to the same area of memory before the "dirty"
+ line is flushed, the cached data overwrites the DMA-ed data. See
+ the R10K processor manual for a full description, including other
potential problems.
- One workaround is to insert cache barrier instructions before every
- memory access that might be speculatively executed and that might
- have side effects even if aborted. '-mr10k-cache-barrier=SETTING'
- controls GCC's implementation of this workaround. It assumes that
- aborted accesses to any byte in the following regions does not have
- side effects:
+ One workaround is to insert cache barrier instructions before
+ every memory access that might be speculatively executed and that
+ might have side effects even if aborted.
+ `-mr10k-cache-barrier=SETTING' controls GCC's implementation of
+ this workaround. It assumes that aborted accesses to any byte in
+ the following regions does not have side effects:
1. the memory occupied by the current function's stack frame;
@@ -16513,45 +16604,45 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
void foo (void);
- then the implementation of 'foo' must allow 'j foo' and 'jal foo'
+ then the implementation of `foo' must allow `j foo' and `jal foo'
to be executed speculatively. GCC honors this restriction for
functions it compiles itself. It expects non-GCC functions (such
as hand-written assembly code) to do the same.
The option has three forms:
- '-mr10k-cache-barrier=load-store'
+ `-mr10k-cache-barrier=load-store'
Insert a cache barrier before a load or store that might be
speculatively executed and that might have side effects even
if aborted.
- '-mr10k-cache-barrier=store'
+ `-mr10k-cache-barrier=store'
Insert a cache barrier before a store that might be
speculatively executed and that might have side effects even
if aborted.
- '-mr10k-cache-barrier=none'
+ `-mr10k-cache-barrier=none'
Disable the insertion of cache barriers. This is the default
setting.
-'-mflush-func=FUNC'
-'-mno-flush-func'
+`-mflush-func=FUNC'
+`-mno-flush-func'
Specifies the function to call to flush the I and D caches, or to
not call any such function. If called, the function must take the
- same arguments as the common '_flush_func', that is, the address of
- the memory range for which the cache is being flushed, the size of
- the memory range, and the number 3 (to flush both caches). The
+ same arguments as the common `_flush_func', that is, the address
+ of the memory range for which the cache is being flushed, the size
+ of the memory range, and the number 3 (to flush both caches). The
default depends on the target GCC was configured for, but commonly
- is either '_flush_func' or '__cpu_flush'.
+ is either `_flush_func' or `__cpu_flush'.
-'mbranch-cost=NUM'
+`mbranch-cost=NUM'
Set the cost of branches to roughly NUM "simple" instructions.
This cost is only a heuristic and is not guaranteed to produce
consistent results across releases. A zero cost redundantly
- selects the default, which is based on the '-mtune' setting.
+ selects the default, which is based on the `-mtune' setting.
-'-mbranch-likely'
-'-mno-branch-likely'
+`-mbranch-likely'
+`-mno-branch-likely'
Enable or disable use of Branch Likely instructions, regardless of
the default for the selected architecture. By default, Branch
Likely instructions may be generated if they are supported by the
@@ -16561,8 +16652,8 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
default because the MIPS32 and MIPS64 architectures specifically
deprecate their use.
-'-mfp-exceptions'
-'-mno-fp-exceptions'
+`-mfp-exceptions'
+`-mno-fp-exceptions'
Specifies whether FP exceptions are enabled. This affects how FP
instructions are scheduled for some processors. The default is
that FP exceptions are enabled.
@@ -16571,8 +16662,8 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
are emitting 64-bit code, then we can use both FP pipes.
Otherwise, we can only use one FP pipe.
-'-mvr4130-align'
-'-mno-vr4130-align'
+`-mvr4130-align'
+`-mno-vr4130-align'
The VR4130 pipeline is two-way superscalar, but can only issue two
instructions together if the first one is 8-byte aligned. When
this option is enabled, GCC aligns pairs of instructions that it
@@ -16580,47 +16671,50 @@ File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Opti
This option only has an effect when optimizing for the VR4130. It
normally makes code faster, but at the expense of making it bigger.
- It is enabled by default at optimization level '-O3'.
+ It is enabled by default at optimization level `-O3'.
-'-msynci'
-'-mno-synci'
- Enable (disable) generation of 'synci' instructions on
- architectures that support it. The 'synci' instructions (if
- enabled) are generated when '__builtin___clear_cache' is compiled.
+`-msynci'
+`-mno-synci'
+ Enable (disable) generation of `synci' instructions on
+ architectures that support it. The `synci' instructions (if
+ enabled) are generated when `__builtin___clear_cache' is compiled.
- This option defaults to '-mno-synci', but the default can be
- overridden by configuring GCC with '--with-synci'.
+ This option defaults to `-mno-synci', but the default can be
+ overridden by configuring GCC with `--with-synci'.
When compiling code for single processor systems, it is generally
- safe to use 'synci'. However, on many multi-core (SMP) systems, it
+ safe to use `synci'. However, on many multi-core (SMP) systems, it
does not invalidate the instruction caches on all cores and may
lead to undefined behavior.
-'-mrelax-pic-calls'
-'-mno-relax-pic-calls'
+`-mrelax-pic-calls'
+`-mno-relax-pic-calls'
Try to turn PIC calls that are normally dispatched via register
- '$25' into direct calls. This is only possible if the linker can
+ `$25' into direct calls. This is only possible if the linker can
resolve the destination at link-time and if the destination is
within range for a direct call.
- '-mrelax-pic-calls' is the default if GCC was configured to use an
- assembler and a linker that support the '.reloc' assembly directive
- and '-mexplicit-relocs' is in effect. With '-mno-explicit-relocs',
- this optimization can be performed by the assembler and the linker
- alone without help from the compiler.
-
-'-mmcount-ra-address'
-'-mno-mcount-ra-address'
- Emit (do not emit) code that allows '_mcount' to modify the calling
- function's return address. When enabled, this option extends the
- usual '_mcount' interface with a new RA-ADDRESS parameter, which
- has type 'intptr_t *' and is passed in register '$12'. '_mcount'
- can then modify the return address by doing both of the following:
- * Returning the new address in register '$31'.
- * Storing the new address in '*RA-ADDRESS', if RA-ADDRESS is
+ `-mrelax-pic-calls' is the default if GCC was configured to use an
+ assembler and a linker that support the `.reloc' assembly
+ directive and `-mexplicit-relocs' is in effect. With
+ `-mno-explicit-relocs', this optimization can be performed by the
+ assembler and the linker alone without help from the compiler.
+
+`-mmcount-ra-address'
+`-mno-mcount-ra-address'
+ Emit (do not emit) code that allows `_mcount' to modify the
+ calling function's return address. When enabled, this option
+ extends the usual `_mcount' interface with a new RA-ADDRESS
+ parameter, which has type `intptr_t *' and is passed in register
+ `$12'. `_mcount' can then modify the return address by doing both
+ of the following:
+ * Returning the new address in register `$31'.
+
+ * Storing the new address in `*RA-ADDRESS', if RA-ADDRESS is
nonnull.
- The default is '-mno-mcount-ra-address'.
+ The default is `-mno-mcount-ra-address'.
+

File: gcc.info, Node: MMIX Options, Next: MN10300 Options, Prev: MIPS Options, Up: Submodel Options
@@ -16630,51 +16724,52 @@ File: gcc.info, Node: MMIX Options, Next: MN10300 Options, Prev: MIPS Options
These options are defined for the MMIX:
-'-mlibfuncs'
-'-mno-libfuncs'
+`-mlibfuncs'
+`-mno-libfuncs'
Specify that intrinsic library functions are being compiled,
passing all values in registers, no matter the size.
-'-mepsilon'
-'-mno-epsilon'
+`-mepsilon'
+`-mno-epsilon'
Generate floating-point comparison instructions that compare with
- respect to the 'rE' epsilon register.
+ respect to the `rE' epsilon register.
-'-mabi=mmixware'
-'-mabi=gnu'
+`-mabi=mmixware'
+`-mabi=gnu'
Generate code that passes function parameters and return values
- that (in the called function) are seen as registers '$0' and up, as
- opposed to the GNU ABI which uses global registers '$231' and up.
+ that (in the called function) are seen as registers `$0' and up,
+ as opposed to the GNU ABI which uses global registers `$231' and
+ up.
-'-mzero-extend'
-'-mno-zero-extend'
+`-mzero-extend'
+`-mno-zero-extend'
When reading data from memory in sizes shorter than 64 bits, use
(do not use) zero-extending load instructions by default, rather
than sign-extending ones.
-'-mknuthdiv'
-'-mno-knuthdiv'
+`-mknuthdiv'
+`-mno-knuthdiv'
Make the result of a division yielding a remainder have the same
- sign as the divisor. With the default, '-mno-knuthdiv', the sign
+ sign as the divisor. With the default, `-mno-knuthdiv', the sign
of the remainder follows the sign of the dividend. Both methods
are arithmetically valid, the latter being almost exclusively used.
-'-mtoplevel-symbols'
-'-mno-toplevel-symbols'
- Prepend (do not prepend) a ':' to all global symbols, so the
- assembly code can be used with the 'PREFIX' assembly directive.
+`-mtoplevel-symbols'
+`-mno-toplevel-symbols'
+ Prepend (do not prepend) a `:' to all global symbols, so the
+ assembly code can be used with the `PREFIX' assembly directive.
-'-melf'
+`-melf'
Generate an executable in the ELF format, rather than the default
- 'mmo' format used by the 'mmix' simulator.
+ `mmo' format used by the `mmix' simulator.
-'-mbranch-predict'
-'-mno-branch-predict'
+`-mbranch-predict'
+`-mno-branch-predict'
Use (do not use) the probable-branch instructions, when static
branch prediction indicates a probable branch.
-'-mbase-addresses'
-'-mno-base-addresses'
+`-mbase-addresses'
+`-mno-base-addresses'
Generate (do not generate) code that uses _base addresses_. Using
a base address automatically generates a request (handled by the
assembler and the linker) for a constant to be set up in a global
@@ -16682,11 +16777,11 @@ These options are defined for the MMIX:
requests within the range 0 to 255 from the value held in the
register. The generally leads to short and fast code, but the
number of different data items that can be addressed is limited.
- This means that a program that uses lots of static data may require
- '-mno-base-addresses'.
+ This means that a program that uses lots of static data may
+ require `-mno-base-addresses'.
-'-msingle-exit'
-'-mno-single-exit'
+`-msingle-exit'
+`-mno-single-exit'
Force (do not force) generated code to have a single exit point in
each function.
@@ -16696,72 +16791,73 @@ File: gcc.info, Node: MN10300 Options, Next: Moxie Options, Prev: MMIX Option
3.17.27 MN10300 Options
-----------------------
-These '-m' options are defined for Matsushita MN10300 architectures:
+These `-m' options are defined for Matsushita MN10300 architectures:
-'-mmult-bug'
+`-mmult-bug'
Generate code to avoid bugs in the multiply instructions for the
MN10300 processors. This is the default.
-'-mno-mult-bug'
- Do not generate code to avoid bugs in the multiply instructions for
- the MN10300 processors.
+`-mno-mult-bug'
+ Do not generate code to avoid bugs in the multiply instructions
+ for the MN10300 processors.
-'-mam33'
+`-mam33'
Generate code using features specific to the AM33 processor.
-'-mno-am33'
- Do not generate code using features specific to the AM33 processor.
- This is the default.
+`-mno-am33'
+ Do not generate code using features specific to the AM33
+ processor. This is the default.
-'-mam33-2'
+`-mam33-2'
Generate code using features specific to the AM33/2.0 processor.
-'-mam34'
+`-mam34'
Generate code using features specific to the AM34 processor.
-'-mtune=CPU-TYPE'
+`-mtune=CPU-TYPE'
Use the timing characteristics of the indicated CPU type when
scheduling instructions. This does not change the targeted
- processor type. The CPU type must be one of 'mn10300', 'am33',
- 'am33-2' or 'am34'.
+ processor type. The CPU type must be one of `mn10300', `am33',
+ `am33-2' or `am34'.
-'-mreturn-pointer-on-d0'
+`-mreturn-pointer-on-d0'
When generating a function that returns a pointer, return the
- pointer in both 'a0' and 'd0'. Otherwise, the pointer is returned
- only in 'a0', and attempts to call such functions without a
+ pointer in both `a0' and `d0'. Otherwise, the pointer is returned
+ only in `a0', and attempts to call such functions without a
prototype result in errors. Note that this option is on by
- default; use '-mno-return-pointer-on-d0' to disable it.
+ default; use `-mno-return-pointer-on-d0' to disable it.
-'-mno-crt0'
+`-mno-crt0'
Do not link in the C run-time initialization object file.
-'-mrelax'
+`-mrelax'
Indicate to the linker that it should perform a relaxation
optimization pass to shorten branches, calls and absolute memory
- addresses. This option only has an effect when used on the command
- line for the final link step.
+ addresses. This option only has an effect when used on the
+ command line for the final link step.
This option makes symbolic debugging impossible.
-'-mliw'
- Allow the compiler to generate _Long Instruction Word_ instructions
- if the target is the 'AM33' or later. This is the default. This
- option defines the preprocessor macro '__LIW__'.
+`-mliw'
+ Allow the compiler to generate _Long Instruction Word_
+ instructions if the target is the `AM33' or later. This is the
+ default. This option defines the preprocessor macro `__LIW__'.
-'-mnoliw'
+`-mnoliw'
Do not allow the compiler to generate _Long Instruction Word_
instructions. This option defines the preprocessor macro
- '__NO_LIW__'.
+ `__NO_LIW__'.
-'-msetlb'
+`-msetlb'
Allow the compiler to generate the _SETLB_ and _Lcc_ instructions
- if the target is the 'AM33' or later. This is the default. This
- option defines the preprocessor macro '__SETLB__'.
+ if the target is the `AM33' or later. This is the default. This
+ option defines the preprocessor macro `__SETLB__'.
-'-mnosetlb'
+`-mnosetlb'
Do not allow the compiler to generate _SETLB_ or _Lcc_
instructions. This option defines the preprocessor macro
- '__NO_SETLB__'.
+ `__NO_SETLB__'.
+

File: gcc.info, Node: Moxie Options, Next: MSP430 Options, Prev: MN10300 Options, Up: Submodel Options
@@ -16769,20 +16865,21 @@ File: gcc.info, Node: Moxie Options, Next: MSP430 Options, Prev: MN10300 Opti
3.17.28 Moxie Options
---------------------
-'-meb'
- Generate big-endian code. This is the default for 'moxie-*-*'
+`-meb'
+ Generate big-endian code. This is the default for `moxie-*-*'
configurations.
-'-mel'
+`-mel'
Generate little-endian code.
-'-mmul.x'
+`-mmul.x'
Generate mul.x and umul.x instructions. This is the default for
- 'moxiebox-*-*' configurations.
+ `moxiebox-*-*' configurations.
-'-mno-crt0'
+`-mno-crt0'
Do not link in the C run-time initialization object file.
+

File: gcc.info, Node: MSP430 Options, Next: NDS32 Options, Prev: Moxie Options, Up: Submodel Options
@@ -16791,66 +16888,67 @@ File: gcc.info, Node: MSP430 Options, Next: NDS32 Options, Prev: Moxie Option
These options are defined for the MSP430:
-'-masm-hex'
+`-masm-hex'
Force assembly output to always use hex constants. Normally such
constants are signed decimals, but this option is available for
testsuite and/or aesthetic purposes.
-'-mmcu='
+`-mmcu='
Select the MCU to target. This is used to create a C preprocessor
symbol based upon the MCU name, converted to upper case and pre-
- and post-fixed with '__'. This in turn is used by the 'msp430.h'
+ and post-fixed with `__'. This in turn is used by the `msp430.h'
header file to select an MCU-specific supplementary header file.
The option also sets the ISA to use. If the MCU name is one that
is known to only support the 430 ISA then that is selected,
- otherwise the 430X ISA is selected. A generic MCU name of 'msp430'
- can also be used to select the 430 ISA. Similarly the generic
- 'msp430x' MCU name selects the 430X ISA.
+ otherwise the 430X ISA is selected. A generic MCU name of
+ `msp430' can also be used to select the 430 ISA. Similarly the
+ generic `msp430x' MCU name selects the 430X ISA.
In addition an MCU-specific linker script is added to the linker
- command line. The script's name is the name of the MCU with '.ld'
- appended. Thus specifying '-mmcu=xxx' on the 'gcc' command line
- defines the C preprocessor symbol '__XXX__' and cause the linker to
- search for a script called 'xxx.ld'.
+ command line. The script's name is the name of the MCU with `.ld'
+ appended. Thus specifying `-mmcu=xxx' on the `gcc' command line
+ defines the C preprocessor symbol `__XXX__' and cause the linker
+ to search for a script called `xxx.ld'.
This option is also passed on to the assembler.
-'-mcpu='
- Specifies the ISA to use. Accepted values are 'msp430', 'msp430x'
- and 'msp430xv2'. This option is deprecated. The '-mmcu=' option
+`-mcpu='
+ Specifies the ISA to use. Accepted values are `msp430', `msp430x'
+ and `msp430xv2'. This option is deprecated. The `-mmcu=' option
should be used to select the ISA.
-'-msim'
+`-msim'
Link to the simulator runtime libraries and linker script.
- Overrides any scripts that would be selected by the '-mmcu='
+ Overrides any scripts that would be selected by the `-mmcu='
option.
-'-mlarge'
- Use large-model addressing (20-bit pointers, 32-bit 'size_t').
+`-mlarge'
+ Use large-model addressing (20-bit pointers, 32-bit `size_t').
-'-msmall'
- Use small-model addressing (16-bit pointers, 16-bit 'size_t').
+`-msmall'
+ Use small-model addressing (16-bit pointers, 16-bit `size_t').
-'-mrelax'
+`-mrelax'
This option is passed to the assembler and linker, and allows the
linker to perform certain optimizations that cannot be done until
the final link.
-'mhwmult='
+`mhwmult='
Describes the type of hardware multiply supported by the target.
- Accepted values are 'none' for no hardware multiply, '16bit' for
- the original 16-bit-only multiply supported by early MCUs. '32bit'
- for the 16/32-bit multiply supported by later MCUs and 'f5series'
- for the 16/32-bit multiply supported by F5-series MCUs. A value of
- 'auto' can also be given. This tells GCC to deduce the hardware
- multiply support based upon the MCU name provided by the '-mmcu'
- option. If no '-mmcu' option is specified then '32bit' hardware
- multiply support is assumed. 'auto' is the default setting.
+ Accepted values are `none' for no hardware multiply, `16bit' for
+ the original 16-bit-only multiply supported by early MCUs.
+ `32bit' for the 16/32-bit multiply supported by later MCUs and
+ `f5series' for the 16/32-bit multiply supported by F5-series MCUs.
+ A value of `auto' can also be given. This tells GCC to deduce the
+ hardware multiply support based upon the MCU name provided by the
+ `-mmcu' option. If no `-mmcu' option is specified then `32bit'
+ hardware multiply support is assumed. `auto' is the default
+ setting.
Hardware multiplies are normally performed by calling a library
routine. This saves space in the generated code. When compiling
- at '-O3' or higher however the hardware multiplier is invoked
+ at `-O3' or higher however the hardware multiplier is invoked
inline. This makes for bigger, but faster code.
The hardware multiply routines disable interrupts whilst running
@@ -16858,13 +16956,14 @@ These options are defined for the MSP430:
makes them safe to use inside interrupt handlers as well as in
normal code.
-'-minrt'
+`-minrt'
Enable the use of a minimum runtime environment - no static
initializers or constructors. This is intended for
memory-constrained devices. The compiler includes special symbols
in some objects that tell the linker and runtime which code
fragments are required.
+

File: gcc.info, Node: NDS32 Options, Next: Nios II Options, Prev: MSP430 Options, Up: Submodel Options
@@ -16873,72 +16972,75 @@ File: gcc.info, Node: NDS32 Options, Next: Nios II Options, Prev: MSP430 Opti
These options are defined for NDS32 implementations:
-'-mbig-endian'
+`-mbig-endian'
Generate code in big-endian mode.
-'-mlittle-endian'
+`-mlittle-endian'
Generate code in little-endian mode.
-'-mreduced-regs'
+`-mreduced-regs'
Use reduced-set registers for register allocation.
-'-mfull-regs'
+`-mfull-regs'
Use full-set registers for register allocation.
-'-mcmov'
+`-mcmov'
Generate conditional move instructions.
-'-mno-cmov'
+`-mno-cmov'
Do not generate conditional move instructions.
-'-mperf-ext'
+`-mperf-ext'
Generate performance extension instructions.
-'-mno-perf-ext'
+`-mno-perf-ext'
Do not generate performance extension instructions.
-'-mv3push'
+`-mv3push'
Generate v3 push25/pop25 instructions.
-'-mno-v3push'
+`-mno-v3push'
Do not generate v3 push25/pop25 instructions.
-'-m16-bit'
+`-m16-bit'
Generate 16-bit instructions.
-'-mno-16-bit'
+`-mno-16-bit'
Do not generate 16-bit instructions.
-'-misr-vector-size=NUM'
+`-misr-vector-size=NUM'
Specify the size of each interrupt vector, which must be 4 or 16.
-'-mcache-block-size=NUM'
+`-mcache-block-size=NUM'
Specify the size of each cache block, which must be a power of 2
between 4 and 512.
-'-march=ARCH'
+`-march=ARCH'
Specify the name of the target architecture.
-'-mcmodel=CODE-MODEL'
+`-mcmodel=CODE-MODEL'
Set the code model to one of
- 'small'
+ `small'
All the data and read-only data segments must be within 512KB
addressing space. The text segment must be within 16MB
addressing space.
- 'medium'
- The data segment must be within 512KB while the read-only data
- segment can be within 4GB addressing space. The text segment
- should be still within 16MB addressing space.
- 'large'
+
+ `medium'
+ The data segment must be within 512KB while the read-only
+ data segment can be within 4GB addressing space. The text
+ segment should be still within 16MB addressing space.
+
+ `large'
All the text and data segments can be within 4GB addressing
space.
-'-mctor-dtor'
+`-mctor-dtor'
Enable constructor/destructor feature.
-'-mrelax'
+`-mrelax'
Guide linker to relax instructions.
+

File: gcc.info, Node: Nios II Options, Next: Nvidia PTX Options, Prev: NDS32 Options, Up: Submodel Options
@@ -16947,40 +17049,41 @@ File: gcc.info, Node: Nios II Options, Next: Nvidia PTX Options, Prev: NDS32
These are the options defined for the Altera Nios II processor.
-'-G NUM'
+`-G NUM'
Put global and static objects less than or equal to NUM bytes into
the small data or BSS sections instead of the normal data or BSS
sections. The default value of NUM is 8.
-'-mgpopt=OPTION'
-'-mgpopt'
-'-mno-gpopt'
+`-mgpopt=OPTION'
+
+`-mgpopt'
+`-mno-gpopt'
Generate (do not generate) GP-relative accesses. The following
OPTION names are recognized:
- 'none'
+ `none'
Do not generate GP-relative accesses.
- 'local'
+ `local'
Generate GP-relative accesses for small data objects that are
not external or weak. Also use GP-relative addressing for
objects that have been explicitly placed in a small data
- section via a 'section' attribute.
+ section via a `section' attribute.
- 'global'
- As for 'local', but also generate GP-relative accesses for
- small data objects that are external or weak. If you use this
- option, you must ensure that all parts of your program
- (including libraries) are compiled with the same '-G' setting.
+ `global'
+ As for `local', but also generate GP-relative accesses for
+ small data objects that are external or weak. If you use
+ this option, you must ensure that all parts of your program
+ (including libraries) are compiled with the same `-G' setting.
- 'data'
+ `data'
Generate GP-relative accesses for all data objects in the
program. If you use this option, the entire data and BSS
segments of your program must fit in 64K of memory and you
must use an appropriate linker script to allocate them within
the addressible range of the global pointer.
- 'all'
+ `all'
Generate GP-relative addresses for function pointers as well
as data pointers. If you use this option, the entire text,
data, and BSS segments of your program must fit in 64K of
@@ -16988,57 +17091,58 @@ These are the options defined for the Altera Nios II processor.
allocate them within the addressible range of the global
pointer.
- '-mgpopt' is equivalent to '-mgpopt=local', and '-mno-gpopt' is
- equivalent to '-mgpopt=none'.
- The default is '-mgpopt' except when '-fpic' or '-fPIC' is
+ `-mgpopt' is equivalent to `-mgpopt=local', and `-mno-gpopt' is
+ equivalent to `-mgpopt=none'.
+
+ The default is `-mgpopt' except when `-fpic' or `-fPIC' is
specified to generate position-independent code. Note that the
Nios II ABI does not permit GP-relative accesses from shared
libraries.
- You may need to specify '-mno-gpopt' explicitly when building
+ You may need to specify `-mno-gpopt' explicitly when building
programs that include large amounts of small data, including large
GOT data sections. In this case, the 16-bit offset for GP-relative
addressing may not be large enough to allow access to the entire
small data section.
-'-mel'
-'-meb'
+`-mel'
+`-meb'
Generate little-endian (default) or big-endian (experimental) code,
respectively.
-'-mbypass-cache'
-'-mno-bypass-cache'
+`-mbypass-cache'
+`-mno-bypass-cache'
Force all load and store instructions to always bypass cache by
- using I/O variants of the instructions. The default is not to
+ using I/O variants of the instructions. The default is not to
bypass the cache.
-'-mno-cache-volatile'
-'-mcache-volatile'
+`-mno-cache-volatile'
+`-mcache-volatile'
Volatile memory access bypass the cache using the I/O variants of
- the load and store instructions. The default is not to bypass the
+ the load and store instructions. The default is not to bypass the
cache.
-'-mno-fast-sw-div'
-'-mfast-sw-div'
- Do not use table-based fast divide for small numbers. The default
- is to use the fast divide at '-O3' and above.
-
-'-mno-hw-mul'
-'-mhw-mul'
-'-mno-hw-mulx'
-'-mhw-mulx'
-'-mno-hw-div'
-'-mhw-div'
- Enable or disable emitting 'mul', 'mulx' and 'div' family of
- instructions by the compiler. The default is to emit 'mul' and not
- emit 'div' and 'mulx'.
-
-'-mcustom-INSN=N'
-'-mno-custom-INSN'
- Each '-mcustom-INSN=N' option enables use of a custom instruction
+`-mno-fast-sw-div'
+`-mfast-sw-div'
+ Do not use table-based fast divide for small numbers. The default
+ is to use the fast divide at `-O3' and above.
+
+`-mno-hw-mul'
+`-mhw-mul'
+`-mno-hw-mulx'
+`-mhw-mulx'
+`-mno-hw-div'
+`-mhw-div'
+ Enable or disable emitting `mul', `mulx' and `div' family of
+ instructions by the compiler. The default is to emit `mul' and not
+ emit `div' and `mulx'.
+
+`-mcustom-INSN=N'
+`-mno-custom-INSN'
+ Each `-mcustom-INSN=N' option enables use of a custom instruction
with encoding N when generating code that uses INSN. For example,
- '-mcustom-fadds=253' generates custom instruction 253 for
+ `-mcustom-fadds=253' generates custom instruction 253 for
single-precision floating-point add operations instead of the
default behavior of using a library call.
@@ -17049,132 +17153,132 @@ These are the options defined for the Altera Nios II processor.
Builtins::).
Single-precision floating point:
-
- 'fadds', 'fsubs', 'fdivs', 'fmuls'
+ `fadds', `fsubs', `fdivs', `fmuls'
Binary arithmetic operations.
- 'fnegs'
+ `fnegs'
Unary negation.
- 'fabss'
+ `fabss'
Unary absolute value.
- 'fcmpeqs', 'fcmpges', 'fcmpgts', 'fcmples', 'fcmplts', 'fcmpnes'
+ `fcmpeqs', `fcmpges', `fcmpgts', `fcmples', `fcmplts', `fcmpnes'
Comparison operations.
- 'fmins', 'fmaxs'
+ `fmins', `fmaxs'
Floating-point minimum and maximum. These instructions are
- only generated if '-ffinite-math-only' is specified.
+ only generated if `-ffinite-math-only' is specified.
- 'fsqrts'
+ `fsqrts'
Unary square root operation.
- 'fcoss', 'fsins', 'ftans', 'fatans', 'fexps', 'flogs'
- Floating-point trigonometric and exponential functions. These
- instructions are only generated if
- '-funsafe-math-optimizations' is also specified.
+ `fcoss', `fsins', `ftans', `fatans', `fexps', `flogs'
+ Floating-point trigonometric and exponential functions.
+ These instructions are only generated if
+ `-funsafe-math-optimizations' is also specified.
- Double-precision floating point:
- 'faddd', 'fsubd', 'fdivd', 'fmuld'
+ Double-precision floating point:
+ `faddd', `fsubd', `fdivd', `fmuld'
Binary arithmetic operations.
- 'fnegd'
+ `fnegd'
Unary negation.
- 'fabsd'
+ `fabsd'
Unary absolute value.
- 'fcmpeqd', 'fcmpged', 'fcmpgtd', 'fcmpled', 'fcmpltd', 'fcmpned'
+ `fcmpeqd', `fcmpged', `fcmpgtd', `fcmpled', `fcmpltd', `fcmpned'
Comparison operations.
- 'fmind', 'fmaxd'
+ `fmind', `fmaxd'
Double-precision minimum and maximum. These instructions are
- only generated if '-ffinite-math-only' is specified.
+ only generated if `-ffinite-math-only' is specified.
- 'fsqrtd'
+ `fsqrtd'
Unary square root operation.
- 'fcosd', 'fsind', 'ftand', 'fatand', 'fexpd', 'flogd'
+ `fcosd', `fsind', `ftand', `fatand', `fexpd', `flogd'
Double-precision trigonometric and exponential functions.
These instructions are only generated if
- '-funsafe-math-optimizations' is also specified.
+ `-funsafe-math-optimizations' is also specified.
+
Conversions:
- 'fextsd'
+ `fextsd'
Conversion from single precision to double precision.
- 'ftruncds'
+ `ftruncds'
Conversion from double precision to single precision.
- 'fixsi', 'fixsu', 'fixdi', 'fixdu'
+ `fixsi', `fixsu', `fixdi', `fixdu'
Conversion from floating point to signed or unsigned integer
types, with truncation towards zero.
- 'round'
+ `round'
Conversion from single-precision floating point to signed
integer, rounding to the nearest integer and ties away from
- zero. This corresponds to the '__builtin_lroundf' function
- when '-fno-math-errno' is used.
+ zero. This corresponds to the `__builtin_lroundf' function
+ when `-fno-math-errno' is used.
- 'floatis', 'floatus', 'floatid', 'floatud'
+ `floatis', `floatus', `floatid', `floatud'
Conversion from signed or unsigned integer types to
floating-point types.
+
In addition, all of the following transfer instructions for
internal registers X and Y must be provided to use any of the
double-precision floating-point instructions. Custom instructions
taking two double-precision source operands expect the first
- operand in the 64-bit register X. The other operand (or only
+ operand in the 64-bit register X. The other operand (or only
operand of a unary operation) is given to the custom arithmetic
- instruction with the least significant half in source register SRC1
- and the most significant half in SRC2. A custom instruction that
- returns a double-precision result returns the most significant 32
- bits in the destination register and the other half in 32-bit
- register Y. GCC automatically generates the necessary code
- sequences to write register X and/or read register Y when
+ instruction with the least significant half in source register
+ SRC1 and the most significant half in SRC2. A custom instruction
+ that returns a double-precision result returns the most
+ significant 32 bits in the destination register and the other half
+ in 32-bit register Y. GCC automatically generates the necessary
+ code sequences to write register X and/or read register Y when
double-precision floating-point instructions are used.
- 'fwrx'
+ `fwrx'
Write SRC1 into the least significant half of X and SRC2 into
the most significant half of X.
- 'fwry'
+ `fwry'
Write SRC1 into Y.
- 'frdxhi', 'frdxlo'
+ `frdxhi', `frdxlo'
Read the most or least (respectively) significant half of X
and store it in DEST.
- 'frdy'
+ `frdy'
Read the value of Y and store it into DEST.
Note that you can gain more local control over generation of Nios
- II custom instructions by using the 'target("custom-INSN=N")' and
- 'target("no-custom-INSN")' function attributes (*note Function
+ II custom instructions by using the `target("custom-INSN=N")' and
+ `target("no-custom-INSN")' function attributes (*note Function
Attributes::) or pragmas (*note Function Specific Option
Pragmas::).
-'-mcustom-fpu-cfg=NAME'
-
+`-mcustom-fpu-cfg=NAME'
This option enables a predefined, named set of custom instruction
- encodings (see '-mcustom-INSN' above). Currently, the following
+ encodings (see `-mcustom-INSN' above). Currently, the following
sets are defined:
- '-mcustom-fpu-cfg=60-1' is equivalent to:
+ `-mcustom-fpu-cfg=60-1' is equivalent to:
-mcustom-fmuls=252
-mcustom-fadds=253
-mcustom-fsubs=254
-fsingle-precision-constant
- '-mcustom-fpu-cfg=60-2' is equivalent to:
+ `-mcustom-fpu-cfg=60-2' is equivalent to:
-mcustom-fmuls=252
-mcustom-fadds=253
-mcustom-fsubs=254
-mcustom-fdivs=255
-fsingle-precision-constant
- '-mcustom-fpu-cfg=72-3' is equivalent to:
+ `-mcustom-fpu-cfg=72-3' is equivalent to:
-mcustom-floatus=243
-mcustom-fixsi=244
-mcustom-floatis=245
@@ -17188,38 +17292,41 @@ These are the options defined for the Altera Nios II processor.
-mcustom-fdivs=255
-fsingle-precision-constant
- Custom instruction assignments given by individual '-mcustom-INSN='
- options override those given by '-mcustom-fpu-cfg=', regardless of
- the order of the options on the command line.
+ Custom instruction assignments given by individual
+ `-mcustom-INSN=' options override those given by
+ `-mcustom-fpu-cfg=', regardless of the order of the options on the
+ command line.
Note that you can gain more local control over selection of a FPU
- configuration by using the 'target("custom-fpu-cfg=NAME")' function
- attribute (*note Function Attributes::) or pragma (*note Function
- Specific Option Pragmas::).
+ configuration by using the `target("custom-fpu-cfg=NAME")'
+ function attribute (*note Function Attributes::) or pragma (*note
+ Function Specific Option Pragmas::).
+
- These additional '-m' options are available for the Altera Nios II ELF
+ These additional `-m' options are available for the Altera Nios II ELF
(bare-metal) target:
-'-mhal'
- Link with HAL BSP. This suppresses linking with the GCC-provided C
- runtime startup and termination code, and is typically used in
- conjunction with '-msys-crt0=' to specify the location of the
+`-mhal'
+ Link with HAL BSP. This suppresses linking with the GCC-provided
+ C runtime startup and termination code, and is typically used in
+ conjunction with `-msys-crt0=' to specify the location of the
alternate startup code provided by the HAL BSP.
-'-msmallc'
- Link with a limited version of the C library, '-lsmallc', rather
+`-msmallc'
+ Link with a limited version of the C library, `-lsmallc', rather
than Newlib.
-'-msys-crt0=STARTFILE'
+`-msys-crt0=STARTFILE'
STARTFILE is the file name of the startfile (crt0) to use when
- linking. This option is only useful in conjunction with '-mhal'.
+ linking. This option is only useful in conjunction with `-mhal'.
-'-msys-lib=SYSTEMLIB'
+`-msys-lib=SYSTEMLIB'
SYSTEMLIB is the library name of the library that provides
- low-level system calls required by the C library, e.g. 'read' and
- 'write'. This option is typically used to link with a library
+ low-level system calls required by the C library, e.g. `read' and
+ `write'. This option is typically used to link with a library
provided by a HAL BSP.
+

File: gcc.info, Node: Nvidia PTX Options, Next: PDP-11 Options, Prev: Nios II Options, Up: Submodel Options
@@ -17228,14 +17335,15 @@ File: gcc.info, Node: Nvidia PTX Options, Next: PDP-11 Options, Prev: Nios II
These options are defined for Nvidia PTX:
-'-m32'
-'-m64'
+`-m32'
+`-m64'
Generate code for 32-bit or 64-bit ABI.
-'-mmainkernel'
+`-mmainkernel'
Link in code for a __main kernel. This is for stand-alone instead
of offloading execution.
+

File: gcc.info, Node: PDP-11 Options, Next: picoChip Options, Prev: Nvidia PTX Options, Up: Submodel Options
@@ -17244,72 +17352,72 @@ File: gcc.info, Node: PDP-11 Options, Next: picoChip Options, Prev: Nvidia PT
These options are defined for the PDP-11:
-'-mfpu'
+`-mfpu'
Use hardware FPP floating point. This is the default. (FIS
floating point on the PDP-11/40 is not supported.)
-'-msoft-float'
+`-msoft-float'
Do not use hardware floating point.
-'-mac0'
+`-mac0'
Return floating-point results in ac0 (fr0 in Unix assembler
syntax).
-'-mno-ac0'
+`-mno-ac0'
Return floating-point results in memory. This is the default.
-'-m40'
+`-m40'
Generate code for a PDP-11/40.
-'-m45'
+`-m45'
Generate code for a PDP-11/45. This is the default.
-'-m10'
+`-m10'
Generate code for a PDP-11/10.
-'-mbcopy-builtin'
- Use inline 'movmemhi' patterns for copying memory. This is the
+`-mbcopy-builtin'
+ Use inline `movmemhi' patterns for copying memory. This is the
default.
-'-mbcopy'
- Do not use inline 'movmemhi' patterns for copying memory.
+`-mbcopy'
+ Do not use inline `movmemhi' patterns for copying memory.
-'-mint16'
-'-mno-int32'
- Use 16-bit 'int'. This is the default.
+`-mint16'
+`-mno-int32'
+ Use 16-bit `int'. This is the default.
-'-mint32'
-'-mno-int16'
- Use 32-bit 'int'.
+`-mint32'
+`-mno-int16'
+ Use 32-bit `int'.
-'-mfloat64'
-'-mno-float32'
- Use 64-bit 'float'. This is the default.
+`-mfloat64'
+`-mno-float32'
+ Use 64-bit `float'. This is the default.
-'-mfloat32'
-'-mno-float64'
- Use 32-bit 'float'.
+`-mfloat32'
+`-mno-float64'
+ Use 32-bit `float'.
-'-mabshi'
- Use 'abshi2' pattern. This is the default.
+`-mabshi'
+ Use `abshi2' pattern. This is the default.
-'-mno-abshi'
- Do not use 'abshi2' pattern.
+`-mno-abshi'
+ Do not use `abshi2' pattern.
-'-mbranch-expensive'
+`-mbranch-expensive'
Pretend that branches are expensive. This is for experimenting
with code generation only.
-'-mbranch-cheap'
+`-mbranch-cheap'
Do not pretend that branches are expensive. This is the default.
-'-munix-asm'
+`-munix-asm'
Use Unix assembler syntax. This is the default when configured for
- 'pdp11-*-bsd'.
+ `pdp11-*-bsd'.
-'-mdec-asm'
+`-mdec-asm'
Use DEC assembler syntax. This is the default when configured for
- any PDP-11 target other than 'pdp11-*-bsd'.
+ any PDP-11 target other than `pdp11-*-bsd'.

File: gcc.info, Node: picoChip Options, Next: PowerPC Options, Prev: PDP-11 Options, Up: Submodel Options
@@ -17317,45 +17425,46 @@ File: gcc.info, Node: picoChip Options, Next: PowerPC Options, Prev: PDP-11 O
3.17.34 picoChip Options
------------------------
-These '-m' options are defined for picoChip implementations:
+These `-m' options are defined for picoChip implementations:
-'-mae=AE_TYPE'
+`-mae=AE_TYPE'
Set the instruction set, register set, and instruction scheduling
parameters for array element type AE_TYPE. Supported values for
- AE_TYPE are 'ANY', 'MUL', and 'MAC'.
+ AE_TYPE are `ANY', `MUL', and `MAC'.
- '-mae=ANY' selects a completely generic AE type. Code generated
+ `-mae=ANY' selects a completely generic AE type. Code generated
with this option runs on any of the other AE types. The code is
- not as efficient as it would be if compiled for a specific AE type,
- and some types of operation (e.g., multiplication) do not work
- properly on all types of AE.
+ not as efficient as it would be if compiled for a specific AE
+ type, and some types of operation (e.g., multiplication) do not
+ work properly on all types of AE.
- '-mae=MUL' selects a MUL AE type. This is the most useful AE type
+ `-mae=MUL' selects a MUL AE type. This is the most useful AE type
for compiled code, and is the default.
- '-mae=MAC' selects a DSP-style MAC AE. Code compiled with this
+ `-mae=MAC' selects a DSP-style MAC AE. Code compiled with this
option may suffer from poor performance of byte (char)
manipulation, since the DSP AE does not provide hardware support
for byte load/stores.
-'-msymbol-as-address'
+`-msymbol-as-address'
Enable the compiler to directly use a symbol name as an address in
- a load/store instruction, without first loading it into a register.
- Typically, the use of this option generates larger programs, which
- run faster than when the option isn't used. However, the results
- vary from program to program, so it is left as a user option,
- rather than being permanently enabled.
+ a load/store instruction, without first loading it into a
+ register. Typically, the use of this option generates larger
+ programs, which run faster than when the option isn't used.
+ However, the results vary from program to program, so it is left
+ as a user option, rather than being permanently enabled.
-'-mno-inefficient-warnings'
+`-mno-inefficient-warnings'
Disables warnings about the generation of inefficient code. These
warnings can be generated, for example, when compiling code that
performs byte-level memory operations on the MAC AE type. The MAC
- AE has no hardware support for byte-level memory operations, so all
- byte load/stores must be synthesized from word load/store
+ AE has no hardware support for byte-level memory operations, so
+ all byte load/stores must be synthesized from word load/store
operations. This is inefficient and a warning is generated to
- indicate that you should rewrite the code to avoid byte operations,
- or to target an AE type that has the necessary hardware support.
- This option disables these warnings.
+ indicate that you should rewrite the code to avoid byte
+ operations, or to target an AE type that has the necessary
+ hardware support. This option disables these warnings.
+

File: gcc.info, Node: PowerPC Options, Next: RL78 Options, Prev: picoChip Options, Up: Submodel Options
@@ -17371,25 +17480,26 @@ File: gcc.info, Node: RL78 Options, Next: RS/6000 and PowerPC Options, Prev:
3.17.36 RL78 Options
--------------------
-'-msim'
+`-msim'
Links in additional target libraries to support operation within a
simulator.
-'-mmul=none'
-'-mmul=g13'
-'-mmul=rl78'
+`-mmul=none'
+`-mmul=g13'
+`-mmul=rl78'
Specifies the type of hardware multiplication support to be used.
- The default is 'none', which uses software multiplication
- functions. The 'g13' option is for the hardware multiply/divide
- peripheral only on the RL78/G13 targets. The 'rl78' option is for
+ The default is `none', which uses software multiplication
+ functions. The `g13' option is for the hardware multiply/divide
+ peripheral only on the RL78/G13 targets. The `rl78' option is for
the standard hardware multiplication defined in the RL78 software
manual.
-'-m64bit-doubles'
-'-m32bit-doubles'
- Make the 'double' data type be 64 bits ('-m64bit-doubles') or 32
- bits ('-m32bit-doubles') in size. The default is
- '-m32bit-doubles'.
+`-m64bit-doubles'
+`-m32bit-doubles'
+ Make the `double' data type be 64 bits (`-m64bit-doubles') or 32
+ bits (`-m32bit-doubles') in size. The default is
+ `-m32bit-doubles'.
+

File: gcc.info, Node: RS/6000 and PowerPC Options, Next: RX Options, Prev: RL78 Options, Up: Submodel Options
@@ -17397,90 +17507,91 @@ File: gcc.info, Node: RS/6000 and PowerPC Options, Next: RX Options, Prev: RL
3.17.37 IBM RS/6000 and PowerPC Options
---------------------------------------
-These '-m' options are defined for the IBM RS/6000 and PowerPC:
-'-mpowerpc-gpopt'
-'-mno-powerpc-gpopt'
-'-mpowerpc-gfxopt'
-'-mno-powerpc-gfxopt'
-'-mpowerpc64'
-'-mno-powerpc64'
-'-mmfcrf'
-'-mno-mfcrf'
-'-mpopcntb'
-'-mno-popcntb'
-'-mpopcntd'
-'-mno-popcntd'
-'-mfprnd'
-'-mno-fprnd'
-'-mcmpb'
-'-mno-cmpb'
-'-mmfpgpr'
-'-mno-mfpgpr'
-'-mhard-dfp'
-'-mno-hard-dfp'
+These `-m' options are defined for the IBM RS/6000 and PowerPC:
+`-mpowerpc-gpopt'
+`-mno-powerpc-gpopt'
+`-mpowerpc-gfxopt'
+`-mno-powerpc-gfxopt'
+`-mpowerpc64'
+`-mno-powerpc64'
+`-mmfcrf'
+`-mno-mfcrf'
+`-mpopcntb'
+`-mno-popcntb'
+`-mpopcntd'
+`-mno-popcntd'
+`-mfprnd'
+`-mno-fprnd'
+`-mcmpb'
+`-mno-cmpb'
+`-mmfpgpr'
+`-mno-mfpgpr'
+`-mhard-dfp'
+`-mno-hard-dfp'
You use these options to specify which instructions are available
- on the processor you are using. The default value of these options
- is determined when configuring GCC. Specifying the
- '-mcpu=CPU_TYPE' overrides the specification of these options. We
- recommend you use the '-mcpu=CPU_TYPE' option rather than the
+ on the processor you are using. The default value of these
+ options is determined when configuring GCC. Specifying the
+ `-mcpu=CPU_TYPE' overrides the specification of these options. We
+ recommend you use the `-mcpu=CPU_TYPE' option rather than the
options listed above.
- Specifying '-mpowerpc-gpopt' allows GCC to use the optional PowerPC
- architecture instructions in the General Purpose group, including
- floating-point square root. Specifying '-mpowerpc-gfxopt' allows
- GCC to use the optional PowerPC architecture instructions in the
- Graphics group, including floating-point select.
-
- The '-mmfcrf' option allows GCC to generate the move from condition
- register field instruction implemented on the POWER4 processor and
- other processors that support the PowerPC V2.01 architecture. The
- '-mpopcntb' option allows GCC to generate the popcount and
- double-precision FP reciprocal estimate instruction implemented on
- the POWER5 processor and other processors that support the PowerPC
- V2.02 architecture. The '-mpopcntd' option allows GCC to generate
- the popcount instruction implemented on the POWER7 processor and
- other processors that support the PowerPC V2.06 architecture. The
- '-mfprnd' option allows GCC to generate the FP round to integer
- instructions implemented on the POWER5+ processor and other
- processors that support the PowerPC V2.03 architecture. The
- '-mcmpb' option allows GCC to generate the compare bytes
- instruction implemented on the POWER6 processor and other
- processors that support the PowerPC V2.05 architecture. The
- '-mmfpgpr' option allows GCC to generate the FP move to/from
+ Specifying `-mpowerpc-gpopt' allows GCC to use the optional
+ PowerPC architecture instructions in the General Purpose group,
+ including floating-point square root. Specifying
+ `-mpowerpc-gfxopt' allows GCC to use the optional PowerPC
+ architecture instructions in the Graphics group, including
+ floating-point select.
+
+ The `-mmfcrf' option allows GCC to generate the move from
+ condition register field instruction implemented on the POWER4
+ processor and other processors that support the PowerPC V2.01
+ architecture. The `-mpopcntb' option allows GCC to generate the
+ popcount and double-precision FP reciprocal estimate instruction
+ implemented on the POWER5 processor and other processors that
+ support the PowerPC V2.02 architecture. The `-mpopcntd' option
+ allows GCC to generate the popcount instruction implemented on the
+ POWER7 processor and other processors that support the PowerPC
+ V2.06 architecture. The `-mfprnd' option allows GCC to generate
+ the FP round to integer instructions implemented on the POWER5+
+ processor and other processors that support the PowerPC V2.03
+ architecture. The `-mcmpb' option allows GCC to generate the
+ compare bytes instruction implemented on the POWER6 processor and
+ other processors that support the PowerPC V2.05 architecture. The
+ `-mmfpgpr' option allows GCC to generate the FP move to/from
general-purpose register instructions implemented on the POWER6X
processor and other processors that support the extended PowerPC
- V2.05 architecture. The '-mhard-dfp' option allows GCC to generate
- the decimal floating-point instructions implemented on some POWER
- processors.
+ V2.05 architecture. The `-mhard-dfp' option allows GCC to
+ generate the decimal floating-point instructions implemented on
+ some POWER processors.
- The '-mpowerpc64' option allows GCC to generate the additional
+ The `-mpowerpc64' option allows GCC to generate the additional
64-bit instructions that are found in the full PowerPC64
architecture and to treat GPRs as 64-bit, doubleword quantities.
- GCC defaults to '-mno-powerpc64'.
+ GCC defaults to `-mno-powerpc64'.
-'-mcpu=CPU_TYPE'
+`-mcpu=CPU_TYPE'
Set architecture type, register usage, and instruction scheduling
parameters for machine type CPU_TYPE. Supported values for
- CPU_TYPE are '401', '403', '405', '405fp', '440', '440fp', '464',
- '464fp', '476', '476fp', '505', '601', '602', '603', '603e', '604',
- '604e', '620', '630', '740', '7400', '7450', '750', '801', '821',
- '823', '860', '970', '8540', 'a2', 'e300c2', 'e300c3', 'e500mc',
- 'e500mc64', 'e5500', 'e6500', 'ec603e', 'G3', 'G4', 'G5', 'titan',
- 'power3', 'power4', 'power5', 'power5+', 'power6', 'power6x',
- 'power7', 'power8', 'powerpc', 'powerpc64', 'powerpc64le', and
- 'rs64'.
-
- '-mcpu=powerpc', '-mcpu=powerpc64', and '-mcpu=powerpc64le' specify
- pure 32-bit PowerPC (either endian), 64-bit big endian PowerPC and
- 64-bit little endian PowerPC architecture machine types, with an
- appropriate, generic processor model assumed for scheduling
- purposes.
+ CPU_TYPE are `401', `403', `405', `405fp', `440', `440fp', `464',
+ `464fp', `476', `476fp', `505', `601', `602', `603', `603e',
+ `604', `604e', `620', `630', `740', `7400', `7450', `750', `801',
+ `821', `823', `860', `970', `8540', `a2', `e300c2', `e300c3',
+ `e500mc', `e500mc64', `e5500', `e6500', `ec603e', `G3', `G4', `G5',
+ `titan', `power3', `power4', `power5', `power5+', `power6',
+ `power6x', `power7', `power8', `powerpc', `powerpc64',
+ `powerpc64le', and `rs64'.
+
+ `-mcpu=powerpc', `-mcpu=powerpc64', and `-mcpu=powerpc64le'
+ specify pure 32-bit PowerPC (either endian), 64-bit big endian
+ PowerPC and 64-bit little endian PowerPC architecture machine
+ types, with an appropriate, generic processor model assumed for
+ scheduling purposes.
The other options specify a specific processor. Code generated
- under those options runs best on that processor, and may not run at
- all on others.
+ under those options runs best on that processor, and may not run
+ at all on others.
- The '-mcpu' options automatically enable or disable the following
+ The `-mcpu' options automatically enable or disable the following
options:
-maltivec -mfprnd -mhard-float -mmfcrf -mmultiple
@@ -17494,218 +17605,218 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
compiler versions, depending on what setting seems to produce
optimal code for that CPU; it doesn't necessarily reflect the
actual hardware's capabilities. If you wish to set an individual
- option to a particular value, you may specify it after the '-mcpu'
- option, like '-mcpu=970 -mno-altivec'.
+ option to a particular value, you may specify it after the `-mcpu'
+ option, like `-mcpu=970 -mno-altivec'.
- On AIX, the '-maltivec' and '-mpowerpc64' options are not enabled
- or disabled by the '-mcpu' option at present because AIX does not
+ On AIX, the `-maltivec' and `-mpowerpc64' options are not enabled
+ or disabled by the `-mcpu' option at present because AIX does not
have full support for these options. You may still enable or
disable them individually if you're sure it'll work in your
environment.
-'-mtune=CPU_TYPE'
+`-mtune=CPU_TYPE'
Set the instruction scheduling parameters for machine type
CPU_TYPE, but do not set the architecture type or register usage,
- as '-mcpu=CPU_TYPE' does. The same values for CPU_TYPE are used
- for '-mtune' as for '-mcpu'. If both are specified, the code
- generated uses the architecture and registers set by '-mcpu', but
- the scheduling parameters set by '-mtune'.
+ as `-mcpu=CPU_TYPE' does. The same values for CPU_TYPE are used
+ for `-mtune' as for `-mcpu'. If both are specified, the code
+ generated uses the architecture and registers set by `-mcpu', but
+ the scheduling parameters set by `-mtune'.
-'-mcmodel=small'
+`-mcmodel=small'
Generate PowerPC64 code for the small model: The TOC is limited to
64k.
-'-mcmodel=medium'
+`-mcmodel=medium'
Generate PowerPC64 code for the medium model: The TOC and other
static data may be up to a total of 4G in size.
-'-mcmodel=large'
+`-mcmodel=large'
Generate PowerPC64 code for the large model: The TOC may be up to
4G in size. Other data and code is only limited by the 64-bit
address space.
-'-maltivec'
-'-mno-altivec'
+`-maltivec'
+`-mno-altivec'
Generate code that uses (does not use) AltiVec instructions, and
also enable the use of built-in functions that allow more direct
access to the AltiVec instruction set. You may also need to set
- '-mabi=altivec' to adjust the current ABI with AltiVec ABI
+ `-mabi=altivec' to adjust the current ABI with AltiVec ABI
enhancements.
- When '-maltivec' is used, rather than '-maltivec=le' or
- '-maltivec=be', the element order for Altivec intrinsics such as
- 'vec_splat', 'vec_extract', and 'vec_insert' match array element
+ When `-maltivec' is used, rather than `-maltivec=le' or
+ `-maltivec=be', the element order for Altivec intrinsics such as
+ `vec_splat', `vec_extract', and `vec_insert' match array element
order corresponding to the endianness of the target. That is,
element zero identifies the leftmost element in a vector register
when targeting a big-endian platform, and identifies the rightmost
element in a vector register when targeting a little-endian
platform.
-'-maltivec=be'
+`-maltivec=be'
Generate Altivec instructions using big-endian element order,
regardless of whether the target is big- or little-endian. This is
the default when targeting a big-endian platform.
The element order is used to interpret element numbers in Altivec
- intrinsics such as 'vec_splat', 'vec_extract', and 'vec_insert'.
+ intrinsics such as `vec_splat', `vec_extract', and `vec_insert'.
By default, these match array element order corresponding to the
endianness for the target.
-'-maltivec=le'
+`-maltivec=le'
Generate Altivec instructions using little-endian element order,
regardless of whether the target is big- or little-endian. This is
the default when targeting a little-endian platform. This option
is currently ignored when targeting a big-endian platform.
The element order is used to interpret element numbers in Altivec
- intrinsics such as 'vec_splat', 'vec_extract', and 'vec_insert'.
+ intrinsics such as `vec_splat', `vec_extract', and `vec_insert'.
By default, these match array element order corresponding to the
endianness for the target.
-'-mvrsave'
-'-mno-vrsave'
+`-mvrsave'
+`-mno-vrsave'
Generate VRSAVE instructions when generating AltiVec code.
-'-mgen-cell-microcode'
+`-mgen-cell-microcode'
Generate Cell microcode instructions.
-'-mwarn-cell-microcode'
- Warn when a Cell microcode instruction is emitted. An example of a
- Cell microcode instruction is a variable shift.
+`-mwarn-cell-microcode'
+ Warn when a Cell microcode instruction is emitted. An example of
+ a Cell microcode instruction is a variable shift.
-'-msecure-plt'
- Generate code that allows 'ld' and 'ld.so' to build executables and
- shared libraries with non-executable '.plt' and '.got' sections.
- This is a PowerPC 32-bit SYSV ABI option.
+`-msecure-plt'
+ Generate code that allows `ld' and `ld.so' to build executables
+ and shared libraries with non-executable `.plt' and `.got'
+ sections. This is a PowerPC 32-bit SYSV ABI option.
-'-mbss-plt'
- Generate code that uses a BSS '.plt' section that 'ld.so' fills in,
- and requires '.plt' and '.got' sections that are both writable and
- executable. This is a PowerPC 32-bit SYSV ABI option.
+`-mbss-plt'
+ Generate code that uses a BSS `.plt' section that `ld.so' fills
+ in, and requires `.plt' and `.got' sections that are both writable
+ and executable. This is a PowerPC 32-bit SYSV ABI option.
-'-misel'
-'-mno-isel'
+`-misel'
+`-mno-isel'
This switch enables or disables the generation of ISEL
instructions.
-'-misel=YES/NO'
- This switch has been deprecated. Use '-misel' and '-mno-isel'
+`-misel=YES/NO'
+ This switch has been deprecated. Use `-misel' and `-mno-isel'
instead.
-'-mspe'
-'-mno-spe'
+`-mspe'
+`-mno-spe'
This switch enables or disables the generation of SPE simd
instructions.
-'-mpaired'
-'-mno-paired'
+`-mpaired'
+`-mno-paired'
This switch enables or disables the generation of PAIRED simd
instructions.
-'-mspe=YES/NO'
- This option has been deprecated. Use '-mspe' and '-mno-spe'
+`-mspe=YES/NO'
+ This option has been deprecated. Use `-mspe' and `-mno-spe'
instead.
-'-mvsx'
-'-mno-vsx'
+`-mvsx'
+`-mno-vsx'
Generate code that uses (does not use) vector/scalar (VSX)
instructions, and also enable the use of built-in functions that
allow more direct access to the VSX instruction set.
-'-mcrypto'
-'-mno-crypto'
+`-mcrypto'
+`-mno-crypto'
Enable the use (disable) of the built-in functions that allow
direct access to the cryptographic instructions that were added in
version 2.07 of the PowerPC ISA.
-'-mdirect-move'
-'-mno-direct-move'
+`-mdirect-move'
+`-mno-direct-move'
Generate code that uses (does not use) the instructions to move
data between the general purpose registers and the vector/scalar
(VSX) registers that were added in version 2.07 of the PowerPC ISA.
-'-mpower8-fusion'
-'-mno-power8-fusion'
+`-mpower8-fusion'
+`-mno-power8-fusion'
Generate code that keeps (does not keeps) some integer operations
adjacent so that the instructions can be fused together on power8
and later processors.
-'-mpower8-vector'
-'-mno-power8-vector'
+`-mpower8-vector'
+`-mno-power8-vector'
Generate code that uses (does not use) the vector and scalar
instructions that were added in version 2.07 of the PowerPC ISA.
Also enable the use of built-in functions that allow more direct
access to the vector instructions.
-'-mquad-memory'
-'-mno-quad-memory'
+`-mquad-memory'
+`-mno-quad-memory'
Generate code that uses (does not use) the non-atomic quad word
- memory instructions. The '-mquad-memory' option requires use of
+ memory instructions. The `-mquad-memory' option requires use of
64-bit mode.
-'-mquad-memory-atomic'
-'-mno-quad-memory-atomic'
+`-mquad-memory-atomic'
+`-mno-quad-memory-atomic'
Generate code that uses (does not use) the atomic quad word memory
- instructions. The '-mquad-memory-atomic' option requires use of
+ instructions. The `-mquad-memory-atomic' option requires use of
64-bit mode.
-'-mupper-regs-df'
-'-mno-upper-regs-df'
+`-mupper-regs-df'
+`-mno-upper-regs-df'
Generate code that uses (does not use) the scalar double precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.06 of the
- PowerPC ISA. '-mupper-regs-df' is turned on by default if you use
- any of the '-mcpu=power7', '-mcpu=power8', or '-mvsx' options.
+ PowerPC ISA. `-mupper-regs-df' is turned on by default if you use
+ any of the `-mcpu=power7', `-mcpu=power8', or `-mvsx' options.
-'-mupper-regs-sf'
-'-mno-upper-regs-sf'
+`-mupper-regs-sf'
+`-mno-upper-regs-sf'
Generate code that uses (does not use) the scalar single precision
instructions that target all 64 registers in the vector/scalar
floating point register set that were added in version 2.07 of the
- PowerPC ISA. '-mupper-regs-sf' is turned on by default if you use
- either of the '-mcpu=power8' or '-mpower8-vector' options.
+ PowerPC ISA. `-mupper-regs-sf' is turned on by default if you use
+ either of the `-mcpu=power8' or `-mpower8-vector' options.
-'-mupper-regs'
-'-mno-upper-regs'
- Generate code that uses (does not use) the scalar instructions that
- target all 64 registers in the vector/scalar floating point
+`-mupper-regs'
+`-mno-upper-regs'
+ Generate code that uses (does not use) the scalar instructions
+ that target all 64 registers in the vector/scalar floating point
register set, depending on the model of the machine.
- If the '-mno-upper-regs' option is used, it turns off both
- '-mupper-regs-sf' and '-mupper-regs-df' options.
+ If the `-mno-upper-regs' option is used, it turns off both
+ `-mupper-regs-sf' and `-mupper-regs-df' options.
-'-mfloat-gprs=YES/SINGLE/DOUBLE/NO'
-'-mfloat-gprs'
+`-mfloat-gprs=YES/SINGLE/DOUBLE/NO'
+`-mfloat-gprs'
This switch enables or disables the generation of floating-point
operations on the general-purpose registers for architectures that
support it.
- The argument 'yes' or 'single' enables the use of single-precision
+ The argument `yes' or `single' enables the use of single-precision
floating-point operations.
- The argument 'double' enables the use of single and
+ The argument `double' enables the use of single and
double-precision floating-point operations.
- The argument 'no' disables floating-point operations on the
+ The argument `no' disables floating-point operations on the
general-purpose registers.
This option is currently only available on the MPC854x.
-'-m32'
-'-m64'
+`-m32'
+`-m64'
Generate code for 32-bit or 64-bit environments of Darwin and SVR4
targets (including GNU/Linux). The 32-bit environment sets int,
long and pointer to 32 bits and generates code that runs on any
PowerPC variant. The 64-bit environment sets int to 32 bits and
long and pointer to 64 bits, and generates code for PowerPC64, as
- for '-mpowerpc64'.
+ for `-mpowerpc64'.
-'-mfull-toc'
-'-mno-fp-in-toc'
-'-mno-sum-in-toc'
-'-mminimal-toc'
+`-mfull-toc'
+`-mno-fp-in-toc'
+`-mno-sum-in-toc'
+`-mminimal-toc'
Modify generation of the TOC (Table Of Contents), which is created
- for every executable file. The '-mfull-toc' option is selected by
+ for every executable file. The `-mfull-toc' option is selected by
default. In that case, GCC allocates at least one TOC entry for
each unique non-automatic variable reference in your program. GCC
also places floating-point constants in the TOC. However, only
@@ -17713,32 +17824,32 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
If you receive a linker error message that saying you have
overflowed the available TOC space, you can reduce the amount of
- TOC space used with the '-mno-fp-in-toc' and '-mno-sum-in-toc'
- options. '-mno-fp-in-toc' prevents GCC from putting floating-point
- constants in the TOC and '-mno-sum-in-toc' forces GCC to generate
+ TOC space used with the `-mno-fp-in-toc' and `-mno-sum-in-toc'
+ options. `-mno-fp-in-toc' prevents GCC from putting floating-point
+ constants in the TOC and `-mno-sum-in-toc' forces GCC to generate
code to calculate the sum of an address and a constant at run time
instead of putting that sum into the TOC. You may specify one or
both of these options. Each causes GCC to produce very slightly
slower and larger code at the expense of conserving TOC space.
- If you still run out of space in the TOC even when you specify both
- of these options, specify '-mminimal-toc' instead. This option
- causes GCC to make only one TOC entry for every file. When you
- specify this option, GCC produces code that is slower and larger
- but which uses extremely little TOC space. You may wish to use
- this option only on files that contain less frequently-executed
- code.
+ If you still run out of space in the TOC even when you specify
+ both of these options, specify `-mminimal-toc' instead. This
+ option causes GCC to make only one TOC entry for every file. When
+ you specify this option, GCC produces code that is slower and
+ larger but which uses extremely little TOC space. You may wish to
+ use this option only on files that contain less
+ frequently-executed code.
-'-maix64'
-'-maix32'
+`-maix64'
+`-maix32'
Enable 64-bit AIX ABI and calling convention: 64-bit pointers,
- 64-bit 'long' type, and the infrastructure needed to support them.
- Specifying '-maix64' implies '-mpowerpc64', while '-maix32'
- disables the 64-bit ABI and implies '-mno-powerpc64'. GCC defaults
- to '-maix32'.
+ 64-bit `long' type, and the infrastructure needed to support them.
+ Specifying `-maix64' implies `-mpowerpc64', while `-maix32'
+ disables the 64-bit ABI and implies `-mno-powerpc64'. GCC
+ defaults to `-maix32'.
-'-mxl-compat'
-'-mno-xl-compat'
+`-mxl-compat'
+`-mno-xl-compat'
Produce code that conforms more closely to IBM XL compiler
semantics when using AIX-compatible ABI. Pass floating-point
arguments to prototyped functions beyond the register save area
@@ -17750,434 +17861,436 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
The AIX calling convention was extended but not initially
documented to handle an obscure K&R C case of calling a function
that takes the address of its arguments with fewer arguments than
- declared. IBM XL compilers access floating-point arguments that do
- not fit in the RSA from the stack when a subroutine is compiled
+ declared. IBM XL compilers access floating-point arguments that
+ do not fit in the RSA from the stack when a subroutine is compiled
without optimization. Because always storing floating-point
arguments on the stack is inefficient and rarely needed, this
- option is not enabled by default and only is necessary when calling
- subroutines compiled by IBM XL compilers without optimization.
+ option is not enabled by default and only is necessary when
+ calling subroutines compiled by IBM XL compilers without
+ optimization.
-'-mpe'
+`-mpe'
Support "IBM RS/6000 SP" "Parallel Environment" (PE). Link an
application written to use message passing with special startup
code to enable the application to run. The system must have PE
- installed in the standard location ('/usr/lpp/ppe.poe/'), or the
- 'specs' file must be overridden with the '-specs=' option to
+ installed in the standard location (`/usr/lpp/ppe.poe/'), or the
+ `specs' file must be overridden with the `-specs=' option to
specify the appropriate directory location. The Parallel
- Environment does not support threads, so the '-mpe' option and the
- '-pthread' option are incompatible.
+ Environment does not support threads, so the `-mpe' option and the
+ `-pthread' option are incompatible.
-'-malign-natural'
-'-malign-power'
+`-malign-natural'
+`-malign-power'
On AIX, 32-bit Darwin, and 64-bit PowerPC GNU/Linux, the option
- '-malign-natural' overrides the ABI-defined alignment of larger
+ `-malign-natural' overrides the ABI-defined alignment of larger
types, such as floating-point doubles, on their natural size-based
- boundary. The option '-malign-power' instructs GCC to follow the
+ boundary. The option `-malign-power' instructs GCC to follow the
ABI-specified alignment rules. GCC defaults to the standard
alignment defined in the ABI.
On 64-bit Darwin, natural alignment is the default, and
- '-malign-power' is not supported.
+ `-malign-power' is not supported.
-'-msoft-float'
-'-mhard-float'
+`-msoft-float'
+`-mhard-float'
Generate code that does not use (uses) the floating-point register
set. Software floating-point emulation is provided if you use the
- '-msoft-float' option, and pass the option to GCC when linking.
+ `-msoft-float' option, and pass the option to GCC when linking.
-'-msingle-float'
-'-mdouble-float'
+`-msingle-float'
+`-mdouble-float'
Generate code for single- or double-precision floating-point
- operations. '-mdouble-float' implies '-msingle-float'.
+ operations. `-mdouble-float' implies `-msingle-float'.
-'-msimple-fpu'
- Do not generate 'sqrt' and 'div' instructions for hardware
+`-msimple-fpu'
+ Do not generate `sqrt' and `div' instructions for hardware
floating-point unit.
-'-mfpu=NAME'
+`-mfpu=NAME'
Specify type of floating-point unit. Valid values for NAME are
- 'sp_lite' (equivalent to '-msingle-float -msimple-fpu'), 'dp_lite'
- (equivalent to '-mdouble-float -msimple-fpu'), 'sp_full'
- (equivalent to '-msingle-float'), and 'dp_full' (equivalent to
- '-mdouble-float').
+ `sp_lite' (equivalent to `-msingle-float -msimple-fpu'), `dp_lite'
+ (equivalent to `-mdouble-float -msimple-fpu'), `sp_full'
+ (equivalent to `-msingle-float'), and `dp_full' (equivalent to
+ `-mdouble-float').
-'-mxilinx-fpu'
+`-mxilinx-fpu'
Perform optimizations for the floating-point unit on Xilinx PPC
405/440.
-'-mmultiple'
-'-mno-multiple'
+`-mmultiple'
+`-mno-multiple'
Generate code that uses (does not use) the load multiple word
instructions and the store multiple word instructions. These
instructions are generated by default on POWER systems, and not
- generated on PowerPC systems. Do not use '-mmultiple' on
- little-endian PowerPC systems, since those instructions do not work
- when the processor is in little-endian mode. The exceptions are
- PPC740 and PPC750 which permit these instructions in little-endian
- mode.
-
-'-mstring'
-'-mno-string'
+ generated on PowerPC systems. Do not use `-mmultiple' on
+ little-endian PowerPC systems, since those instructions do not
+ work when the processor is in little-endian mode. The exceptions
+ are PPC740 and PPC750 which permit these instructions in
+ little-endian mode.
+
+`-mstring'
+`-mno-string'
Generate code that uses (does not use) the load string instructions
and the store string word instructions to save multiple registers
and do small block moves. These instructions are generated by
- default on POWER systems, and not generated on PowerPC systems. Do
- not use '-mstring' on little-endian PowerPC systems, since those
+ default on POWER systems, and not generated on PowerPC systems.
+ Do not use `-mstring' on little-endian PowerPC systems, since those
instructions do not work when the processor is in little-endian
mode. The exceptions are PPC740 and PPC750 which permit these
instructions in little-endian mode.
-'-mupdate'
-'-mno-update'
+`-mupdate'
+`-mno-update'
Generate code that uses (does not use) the load or store
instructions that update the base register to the address of the
calculated memory location. These instructions are generated by
- default. If you use '-mno-update', there is a small window between
- the time that the stack pointer is updated and the address of the
- previous frame is stored, which means code that walks the stack
- frame across interrupts or signals may get corrupted data.
+ default. If you use `-mno-update', there is a small window
+ between the time that the stack pointer is updated and the address
+ of the previous frame is stored, which means code that walks the
+ stack frame across interrupts or signals may get corrupted data.
-'-mavoid-indexed-addresses'
-'-mno-avoid-indexed-addresses'
+`-mavoid-indexed-addresses'
+`-mno-avoid-indexed-addresses'
Generate code that tries to avoid (not avoid) the use of indexed
- load or store instructions. These instructions can incur a
+ load or store instructions. These instructions can incur a
performance penalty on Power6 processors in certain situations,
such as when stepping through large arrays that cross a 16M
boundary. This option is enabled by default when targeting Power6
and disabled otherwise.
-'-mfused-madd'
-'-mno-fused-madd'
+`-mfused-madd'
+`-mno-fused-madd'
Generate code that uses (does not use) the floating-point multiply
and accumulate instructions. These instructions are generated by
default if hardware floating point is used. The machine-dependent
- '-mfused-madd' option is now mapped to the machine-independent
- '-ffp-contract=fast' option, and '-mno-fused-madd' is mapped to
- '-ffp-contract=off'.
+ `-mfused-madd' option is now mapped to the machine-independent
+ `-ffp-contract=fast' option, and `-mno-fused-madd' is mapped to
+ `-ffp-contract=off'.
-'-mmulhw'
-'-mno-mulhw'
+`-mmulhw'
+`-mno-mulhw'
Generate code that uses (does not use) the half-word multiply and
multiply-accumulate instructions on the IBM 405, 440, 464 and 476
processors. These instructions are generated by default when
targeting those processors.
-'-mdlmzb'
-'-mno-dlmzb'
- Generate code that uses (does not use) the string-search 'dlmzb'
+`-mdlmzb'
+`-mno-dlmzb'
+ Generate code that uses (does not use) the string-search `dlmzb'
instruction on the IBM 405, 440, 464 and 476 processors. This
instruction is generated by default when targeting those
processors.
-'-mno-bit-align'
-'-mbit-align'
+`-mno-bit-align'
+`-mbit-align'
On System V.4 and embedded PowerPC systems do not (do) force
structures and unions that contain bit-fields to be aligned to the
base type of the bit-field.
For example, by default a structure containing nothing but 8
- 'unsigned' bit-fields of length 1 is aligned to a 4-byte boundary
- and has a size of 4 bytes. By using '-mno-bit-align', the
+ `unsigned' bit-fields of length 1 is aligned to a 4-byte boundary
+ and has a size of 4 bytes. By using `-mno-bit-align', the
structure is aligned to a 1-byte boundary and is 1 byte in size.
-'-mno-strict-align'
-'-mstrict-align'
+`-mno-strict-align'
+`-mstrict-align'
On System V.4 and embedded PowerPC systems do not (do) assume that
unaligned memory references are handled by the system.
-'-mrelocatable'
-'-mno-relocatable'
+`-mrelocatable'
+`-mno-relocatable'
Generate code that allows (does not allow) a static executable to
be relocated to a different address at run time. A simple embedded
PowerPC system loader should relocate the entire contents of
- '.got2' and 4-byte locations listed in the '.fixup' section, a
+ `.got2' and 4-byte locations listed in the `.fixup' section, a
table of 32-bit addresses generated by this option. For this to
work, all objects linked together must be compiled with
- '-mrelocatable' or '-mrelocatable-lib'. '-mrelocatable' code
+ `-mrelocatable' or `-mrelocatable-lib'. `-mrelocatable' code
aligns the stack to an 8-byte boundary.
-'-mrelocatable-lib'
-'-mno-relocatable-lib'
- Like '-mrelocatable', '-mrelocatable-lib' generates a '.fixup'
+`-mrelocatable-lib'
+`-mno-relocatable-lib'
+ Like `-mrelocatable', `-mrelocatable-lib' generates a `.fixup'
section to allow static executables to be relocated at run time,
- but '-mrelocatable-lib' does not use the smaller stack alignment of
- '-mrelocatable'. Objects compiled with '-mrelocatable-lib' may be
- linked with objects compiled with any combination of the
- '-mrelocatable' options.
+ but `-mrelocatable-lib' does not use the smaller stack alignment
+ of `-mrelocatable'. Objects compiled with `-mrelocatable-lib' may
+ be linked with objects compiled with any combination of the
+ `-mrelocatable' options.
-'-mno-toc'
-'-mtoc'
+`-mno-toc'
+`-mtoc'
On System V.4 and embedded PowerPC systems do not (do) assume that
register 2 contains a pointer to a global area pointing to the
addresses used in the program.
-'-mlittle'
-'-mlittle-endian'
+`-mlittle'
+`-mlittle-endian'
On System V.4 and embedded PowerPC systems compile code for the
- processor in little-endian mode. The '-mlittle-endian' option is
- the same as '-mlittle'.
+ processor in little-endian mode. The `-mlittle-endian' option is
+ the same as `-mlittle'.
-'-mbig'
-'-mbig-endian'
+`-mbig'
+`-mbig-endian'
On System V.4 and embedded PowerPC systems compile code for the
- processor in big-endian mode. The '-mbig-endian' option is the
- same as '-mbig'.
+ processor in big-endian mode. The `-mbig-endian' option is the
+ same as `-mbig'.
-'-mdynamic-no-pic'
+`-mdynamic-no-pic'
On Darwin and Mac OS X systems, compile code so that it is not
relocatable, but that its external references are relocatable. The
resulting code is suitable for applications, but not shared
libraries.
-'-msingle-pic-base'
+`-msingle-pic-base'
Treat the register used for PIC addressing as read-only, rather
than loading it in the prologue for each function. The runtime
system is responsible for initializing this register with an
appropriate value before execution begins.
-'-mprioritize-restricted-insns=PRIORITY'
- This option controls the priority that is assigned to dispatch-slot
- restricted instructions during the second scheduling pass. The
- argument PRIORITY takes the value '0', '1', or '2' to assign no,
- highest, or second-highest (respectively) priority to dispatch-slot
- restricted instructions.
+`-mprioritize-restricted-insns=PRIORITY'
+ This option controls the priority that is assigned to
+ dispatch-slot restricted instructions during the second scheduling
+ pass. The argument PRIORITY takes the value `0', `1', or `2' to
+ assign no, highest, or second-highest (respectively) priority to
+ dispatch-slot restricted instructions.
-'-msched-costly-dep=DEPENDENCE_TYPE'
- This option controls which dependences are considered costly by the
- target during instruction scheduling. The argument DEPENDENCE_TYPE
- takes one of the following values:
+`-msched-costly-dep=DEPENDENCE_TYPE'
+ This option controls which dependences are considered costly by
+ the target during instruction scheduling. The argument
+ DEPENDENCE_TYPE takes one of the following values:
- 'no'
+ `no'
No dependence is costly.
- 'all'
+ `all'
All dependences are costly.
- 'true_store_to_load'
+ `true_store_to_load'
A true dependence from store to load is costly.
- 'store_to_load'
+ `store_to_load'
Any dependence from store to load is costly.
- NUMBER
+ NUMBER
Any dependence for which the latency is greater than or equal
to NUMBER is costly.
-'-minsert-sched-nops=SCHEME'
+`-minsert-sched-nops=SCHEME'
This option controls which NOP insertion scheme is used during the
second scheduling pass. The argument SCHEME takes one of the
following values:
- 'no'
+ `no'
Don't insert NOPs.
- 'pad'
+ `pad'
Pad with NOPs any dispatch group that has vacant issue slots,
according to the scheduler's grouping.
- 'regroup_exact'
+ `regroup_exact'
Insert NOPs to force costly dependent insns into separate
groups. Insert exactly as many NOPs as needed to force an
insn to a new group, according to the estimated processor
grouping.
- NUMBER
+ NUMBER
Insert NOPs to force costly dependent insns into separate
groups. Insert NUMBER NOPs to force an insn to a new group.
-'-mcall-sysv'
+`-mcall-sysv'
On System V.4 and embedded PowerPC systems compile code using
calling conventions that adhere to the March 1995 draft of the
System V Application Binary Interface, PowerPC processor
supplement. This is the default unless you configured GCC using
- 'powerpc-*-eabiaix'.
+ `powerpc-*-eabiaix'.
-'-mcall-sysv-eabi'
-'-mcall-eabi'
- Specify both '-mcall-sysv' and '-meabi' options.
+`-mcall-sysv-eabi'
+`-mcall-eabi'
+ Specify both `-mcall-sysv' and `-meabi' options.
-'-mcall-sysv-noeabi'
- Specify both '-mcall-sysv' and '-mno-eabi' options.
+`-mcall-sysv-noeabi'
+ Specify both `-mcall-sysv' and `-mno-eabi' options.
-'-mcall-aixdesc'
+`-mcall-aixdesc'
On System V.4 and embedded PowerPC systems compile code for the AIX
operating system.
-'-mcall-linux'
+`-mcall-linux'
On System V.4 and embedded PowerPC systems compile code for the
Linux-based GNU system.
-'-mcall-freebsd'
+`-mcall-freebsd'
On System V.4 and embedded PowerPC systems compile code for the
FreeBSD operating system.
-'-mcall-netbsd'
+`-mcall-netbsd'
On System V.4 and embedded PowerPC systems compile code for the
NetBSD operating system.
-'-mcall-openbsd'
+`-mcall-openbsd'
On System V.4 and embedded PowerPC systems compile code for the
OpenBSD operating system.
-'-maix-struct-return'
+`-maix-struct-return'
Return all structures in memory (as specified by the AIX ABI).
-'-msvr4-struct-return'
+`-msvr4-struct-return'
Return structures smaller than 8 bytes in registers (as specified
by the SVR4 ABI).
-'-mabi=ABI-TYPE'
+`-mabi=ABI-TYPE'
Extend the current ABI with a particular extension, or remove such
- extension. Valid values are 'altivec', 'no-altivec', 'spe',
- 'no-spe', 'ibmlongdouble', 'ieeelongdouble', 'elfv1', 'elfv2'.
+ extension. Valid values are `altivec', `no-altivec', `spe',
+ `no-spe', `ibmlongdouble', `ieeelongdouble', `elfv1', `elfv2'.
-'-mabi=spe'
+`-mabi=spe'
Extend the current ABI with SPE ABI extensions. This does not
change the default ABI, instead it adds the SPE ABI extensions to
the current ABI.
-'-mabi=no-spe'
+`-mabi=no-spe'
Disable Book-E SPE ABI extensions for the current ABI.
-'-mabi=ibmlongdouble'
+`-mabi=ibmlongdouble'
Change the current ABI to use IBM extended-precision long double.
This is a PowerPC 32-bit SYSV ABI option.
-'-mabi=ieeelongdouble'
+`-mabi=ieeelongdouble'
Change the current ABI to use IEEE extended-precision long double.
This is a PowerPC 32-bit Linux ABI option.
-'-mabi=elfv1'
- Change the current ABI to use the ELFv1 ABI. This is the default
+`-mabi=elfv1'
+ Change the current ABI to use the ELFv1 ABI. This is the default
ABI for big-endian PowerPC 64-bit Linux. Overriding the default
ABI requires special system support and is likely to fail in
spectacular ways.
-'-mabi=elfv2'
- Change the current ABI to use the ELFv2 ABI. This is the default
- ABI for little-endian PowerPC 64-bit Linux. Overriding the default
- ABI requires special system support and is likely to fail in
- spectacular ways.
+`-mabi=elfv2'
+ Change the current ABI to use the ELFv2 ABI. This is the default
+ ABI for little-endian PowerPC 64-bit Linux. Overriding the
+ default ABI requires special system support and is likely to fail
+ in spectacular ways.
-'-mprototype'
-'-mno-prototype'
+`-mprototype'
+`-mno-prototype'
On System V.4 and embedded PowerPC systems assume that all calls to
variable argument functions are properly prototyped. Otherwise,
- the compiler must insert an instruction before every non-prototyped
- call to set or clear bit 6 of the condition code register ('CR') to
- indicate whether floating-point values are passed in the
- floating-point registers in case the function takes variable
- arguments. With '-mprototype', only calls to prototyped variable
- argument functions set or clear the bit.
-
-'-msim'
+ the compiler must insert an instruction before every
+ non-prototyped call to set or clear bit 6 of the condition code
+ register (`CR') to indicate whether floating-point values are
+ passed in the floating-point registers in case the function takes
+ variable arguments. With `-mprototype', only calls to prototyped
+ variable argument functions set or clear the bit.
+
+`-msim'
On embedded PowerPC systems, assume that the startup module is
- called 'sim-crt0.o' and that the standard C libraries are
- 'libsim.a' and 'libc.a'. This is the default for
- 'powerpc-*-eabisim' configurations.
+ called `sim-crt0.o' and that the standard C libraries are
+ `libsim.a' and `libc.a'. This is the default for
+ `powerpc-*-eabisim' configurations.
-'-mmvme'
+`-mmvme'
On embedded PowerPC systems, assume that the startup module is
- called 'crt0.o' and the standard C libraries are 'libmvme.a' and
- 'libc.a'.
+ called `crt0.o' and the standard C libraries are `libmvme.a' and
+ `libc.a'.
-'-mads'
+`-mads'
On embedded PowerPC systems, assume that the startup module is
- called 'crt0.o' and the standard C libraries are 'libads.a' and
- 'libc.a'.
+ called `crt0.o' and the standard C libraries are `libads.a' and
+ `libc.a'.
-'-myellowknife'
+`-myellowknife'
On embedded PowerPC systems, assume that the startup module is
- called 'crt0.o' and the standard C libraries are 'libyk.a' and
- 'libc.a'.
+ called `crt0.o' and the standard C libraries are `libyk.a' and
+ `libc.a'.
-'-mvxworks'
+`-mvxworks'
On System V.4 and embedded PowerPC systems, specify that you are
compiling for a VxWorks system.
-'-memb'
- On embedded PowerPC systems, set the 'PPC_EMB' bit in the ELF flags
- header to indicate that 'eabi' extended relocations are used.
+`-memb'
+ On embedded PowerPC systems, set the `PPC_EMB' bit in the ELF flags
+ header to indicate that `eabi' extended relocations are used.
-'-meabi'
-'-mno-eabi'
+`-meabi'
+`-mno-eabi'
On System V.4 and embedded PowerPC systems do (do not) adhere to
the Embedded Applications Binary Interface (EABI), which is a set
of modifications to the System V.4 specifications. Selecting
- '-meabi' means that the stack is aligned to an 8-byte boundary, a
- function '__eabi' is called from 'main' to set up the EABI
- environment, and the '-msdata' option can use both 'r2' and 'r13'
- to point to two separate small data areas. Selecting '-mno-eabi'
+ `-meabi' means that the stack is aligned to an 8-byte boundary, a
+ function `__eabi' is called from `main' to set up the EABI
+ environment, and the `-msdata' option can use both `r2' and `r13'
+ to point to two separate small data areas. Selecting `-mno-eabi'
means that the stack is aligned to a 16-byte boundary, no EABI
- initialization function is called from 'main', and the '-msdata'
- option only uses 'r13' to point to a single small data area. The
- '-meabi' option is on by default if you configured GCC using one of
- the 'powerpc*-*-eabi*' options.
+ initialization function is called from `main', and the `-msdata'
+ option only uses `r13' to point to a single small data area. The
+ `-meabi' option is on by default if you configured GCC using one
+ of the `powerpc*-*-eabi*' options.
-'-msdata=eabi'
+`-msdata=eabi'
On System V.4 and embedded PowerPC systems, put small initialized
- 'const' global and static data in the '.sdata2' section, which is
- pointed to by register 'r2'. Put small initialized non-'const'
- global and static data in the '.sdata' section, which is pointed to
- by register 'r13'. Put small uninitialized global and static data
- in the '.sbss' section, which is adjacent to the '.sdata' section.
- The '-msdata=eabi' option is incompatible with the '-mrelocatable'
- option. The '-msdata=eabi' option also sets the '-memb' option.
-
-'-msdata=sysv'
+ `const' global and static data in the `.sdata2' section, which is
+ pointed to by register `r2'. Put small initialized non-`const'
+ global and static data in the `.sdata' section, which is pointed
+ to by register `r13'. Put small uninitialized global and static
+ data in the `.sbss' section, which is adjacent to the `.sdata'
+ section. The `-msdata=eabi' option is incompatible with the
+ `-mrelocatable' option. The `-msdata=eabi' option also sets the
+ `-memb' option.
+
+`-msdata=sysv'
On System V.4 and embedded PowerPC systems, put small global and
- static data in the '.sdata' section, which is pointed to by
- register 'r13'. Put small uninitialized global and static data in
- the '.sbss' section, which is adjacent to the '.sdata' section.
- The '-msdata=sysv' option is incompatible with the '-mrelocatable'
+ static data in the `.sdata' section, which is pointed to by
+ register `r13'. Put small uninitialized global and static data in
+ the `.sbss' section, which is adjacent to the `.sdata' section.
+ The `-msdata=sysv' option is incompatible with the `-mrelocatable'
option.
-'-msdata=default'
-'-msdata'
- On System V.4 and embedded PowerPC systems, if '-meabi' is used,
- compile code the same as '-msdata=eabi', otherwise compile code the
- same as '-msdata=sysv'.
+`-msdata=default'
+`-msdata'
+ On System V.4 and embedded PowerPC systems, if `-meabi' is used,
+ compile code the same as `-msdata=eabi', otherwise compile code the
+ same as `-msdata=sysv'.
-'-msdata=data'
+`-msdata=data'
On System V.4 and embedded PowerPC systems, put small global data
- in the '.sdata' section. Put small uninitialized global data in
- the '.sbss' section. Do not use register 'r13' to address small
- data however. This is the default behavior unless other '-msdata'
+ in the `.sdata' section. Put small uninitialized global data in
+ the `.sbss' section. Do not use register `r13' to address small
+ data however. This is the default behavior unless other `-msdata'
options are used.
-'-msdata=none'
-'-mno-sdata'
+`-msdata=none'
+`-mno-sdata'
On embedded PowerPC systems, put all initialized global and static
- data in the '.data' section, and all uninitialized data in the
- '.bss' section.
+ data in the `.data' section, and all uninitialized data in the
+ `.bss' section.
-'-mblock-move-inline-limit=NUM'
- Inline all block moves (such as calls to 'memcpy' or structure
- copies) less than or equal to NUM bytes. The minimum value for NUM
- is 32 bytes on 32-bit targets and 64 bytes on 64-bit targets. The
- default value is target-specific.
+`-mblock-move-inline-limit=NUM'
+ Inline all block moves (such as calls to `memcpy' or structure
+ copies) less than or equal to NUM bytes. The minimum value for
+ NUM is 32 bytes on 32-bit targets and 64 bytes on 64-bit targets.
+ The default value is target-specific.
-'-G NUM'
+`-G NUM'
On embedded PowerPC systems, put global and static items less than
or equal to NUM bytes into the small data or BSS sections instead
- of the normal data or BSS section. By default, NUM is 8. The '-G
+ of the normal data or BSS section. By default, NUM is 8. The `-G
NUM' switch is also passed to the linker. All modules should be
- compiled with the same '-G NUM' value.
+ compiled with the same `-G NUM' value.
-'-mregnames'
-'-mno-regnames'
+`-mregnames'
+`-mno-regnames'
On System V.4 and embedded PowerPC systems do (do not) emit
register names in the assembly language output using symbolic
forms.
-'-mlongcall'
-'-mno-longcall'
+`-mlongcall'
+`-mno-longcall'
By default assume that all calls are far away so that a longer and
more expensive calling sequence is required. This is required for
- calls farther than 32 megabytes (33,554,432 bytes) from the current
- location. A short call is generated if the compiler knows the call
- cannot be that far away. This setting can be overridden by the
- 'shortcall' function attribute, or by '#pragma longcall(0)'.
+ calls farther than 32 megabytes (33,554,432 bytes) from the
+ current location. A short call is generated if the compiler knows
+ the call cannot be that far away. This setting can be overridden
+ by the `shortcall' function attribute, or by `#pragma longcall(0)'.
Some linkers are capable of detecting out-of-range calls and
generating glue code on the fly. On these systems, long calls are
@@ -18186,14 +18299,15 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
planned to add this feature to the GNU linker for 32-bit PowerPC
systems as well.
- On Darwin/PPC systems, '#pragma longcall' generates 'jbsr callee,
- L42', plus a "branch island" (glue code). The two target addresses
- represent the callee and the branch island. The Darwin/PPC linker
- prefers the first address and generates a 'bl callee' if the PPC
- 'bl' instruction reaches the callee directly; otherwise, the linker
- generates 'bl L42' to call the branch island. The branch island is
- appended to the body of the calling function; it computes the full
- 32-bit address of the callee and jumps to it.
+ On Darwin/PPC systems, `#pragma longcall' generates `jbsr callee,
+ L42', plus a "branch island" (glue code). The two target
+ addresses represent the callee and the branch island. The
+ Darwin/PPC linker prefers the first address and generates a `bl
+ callee' if the PPC `bl' instruction reaches the callee directly;
+ otherwise, the linker generates `bl L42' to call the branch
+ island. The branch island is appended to the body of the calling
+ function; it computes the full 32-bit address of the callee and
+ jumps to it.
On Mach-O (Darwin) systems, this option directs the compiler emit
to the glue for every direct call, and the Darwin linker decides
@@ -18202,134 +18316,135 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
In the future, GCC may ignore all longcall specifications when the
linker is known to generate glue.
-'-mtls-markers'
-'-mno-tls-markers'
- Mark (do not mark) calls to '__tls_get_addr' with a relocation
- specifying the function argument. The relocation allows the linker
- to reliably associate function call with argument setup
+`-mtls-markers'
+`-mno-tls-markers'
+ Mark (do not mark) calls to `__tls_get_addr' with a relocation
+ specifying the function argument. The relocation allows the
+ linker to reliably associate function call with argument setup
instructions for TLS optimization, which in turn allows GCC to
better schedule the sequence.
-'-pthread'
+`-pthread'
Adds support for multithreading with the "pthreads" library. This
option sets flags for both the preprocessor and linker.
-'-mrecip'
-'-mno-recip'
+`-mrecip'
+`-mno-recip'
This option enables use of the reciprocal estimate and reciprocal
square root estimate instructions with additional Newton-Raphson
steps to increase precision instead of doing a divide or square
root and divide for floating-point arguments. You should use the
- '-ffast-math' option when using '-mrecip' (or at least
- '-funsafe-math-optimizations', '-finite-math-only',
- '-freciprocal-math' and '-fno-trapping-math'). Note that while the
- throughput of the sequence is generally higher than the throughput
- of the non-reciprocal instruction, the precision of the sequence
- can be decreased by up to 2 ulp (i.e. the inverse of 1.0 equals
- 0.99999994) for reciprocal square roots.
-
-'-mrecip=OPT'
+ `-ffast-math' option when using `-mrecip' (or at least
+ `-funsafe-math-optimizations', `-finite-math-only',
+ `-freciprocal-math' and `-fno-trapping-math'). Note that while
+ the throughput of the sequence is generally higher than the
+ throughput of the non-reciprocal instruction, the precision of the
+ sequence can be decreased by up to 2 ulp (i.e. the inverse of 1.0
+ equals 0.99999994) for reciprocal square roots.
+
+`-mrecip=OPT'
This option controls which reciprocal estimate instructions may be
used. OPT is a comma-separated list of options, which may be
- preceded by a '!' to invert the option:
+ preceded by a `!' to invert the option:
- 'all'
+ `all'
Enable all estimate instructions.
- 'default'
- Enable the default instructions, equivalent to '-mrecip'.
+ `default'
+ Enable the default instructions, equivalent to `-mrecip'.
- 'none'
- Disable all estimate instructions, equivalent to '-mno-recip'.
+ `none'
+ Disable all estimate instructions, equivalent to `-mno-recip'.
- 'div'
+ `div'
Enable the reciprocal approximation instructions for both
single and double precision.
- 'divf'
+ `divf'
Enable the single-precision reciprocal approximation
instructions.
- 'divd'
+ `divd'
Enable the double-precision reciprocal approximation
instructions.
- 'rsqrt'
+ `rsqrt'
Enable the reciprocal square root approximation instructions
for both single and double precision.
- 'rsqrtf'
+ `rsqrtf'
Enable the single-precision reciprocal square root
approximation instructions.
- 'rsqrtd'
+ `rsqrtd'
Enable the double-precision reciprocal square root
approximation instructions.
- So, for example, '-mrecip=all,!rsqrtd' enables all of the
- reciprocal estimate instructions, except for the 'FRSQRTE',
- 'XSRSQRTEDP', and 'XVRSQRTEDP' instructions which handle the
+
+ So, for example, `-mrecip=all,!rsqrtd' enables all of the
+ reciprocal estimate instructions, except for the `FRSQRTE',
+ `XSRSQRTEDP', and `XVRSQRTEDP' instructions which handle the
double-precision reciprocal square root calculations.
-'-mrecip-precision'
-'-mno-recip-precision'
+`-mrecip-precision'
+`-mno-recip-precision'
Assume (do not assume) that the reciprocal estimate instructions
provide higher-precision estimates than is mandated by the PowerPC
- ABI. Selecting '-mcpu=power6', '-mcpu=power7' or '-mcpu=power8'
- automatically selects '-mrecip-precision'. The double-precision
+ ABI. Selecting `-mcpu=power6', `-mcpu=power7' or `-mcpu=power8'
+ automatically selects `-mrecip-precision'. The double-precision
square root estimate instructions are not generated by default on
low-precision machines, since they do not provide an estimate that
converges after three steps.
-'-mveclibabi=TYPE'
+`-mveclibabi=TYPE'
Specifies the ABI type to use for vectorizing intrinsics using an
- external library. The only type supported at present is 'mass',
+ external library. The only type supported at present is `mass',
which specifies to use IBM's Mathematical Acceleration Subsystem
(MASS) libraries for vectorizing intrinsics using external
- libraries. GCC currently emits calls to 'acosd2', 'acosf4',
- 'acoshd2', 'acoshf4', 'asind2', 'asinf4', 'asinhd2', 'asinhf4',
- 'atan2d2', 'atan2f4', 'atand2', 'atanf4', 'atanhd2', 'atanhf4',
- 'cbrtd2', 'cbrtf4', 'cosd2', 'cosf4', 'coshd2', 'coshf4', 'erfcd2',
- 'erfcf4', 'erfd2', 'erff4', 'exp2d2', 'exp2f4', 'expd2', 'expf4',
- 'expm1d2', 'expm1f4', 'hypotd2', 'hypotf4', 'lgammad2', 'lgammaf4',
- 'log10d2', 'log10f4', 'log1pd2', 'log1pf4', 'log2d2', 'log2f4',
- 'logd2', 'logf4', 'powd2', 'powf4', 'sind2', 'sinf4', 'sinhd2',
- 'sinhf4', 'sqrtd2', 'sqrtf4', 'tand2', 'tanf4', 'tanhd2', and
- 'tanhf4' when generating code for power7. Both '-ftree-vectorize'
- and '-funsafe-math-optimizations' must also be enabled. The MASS
- libraries must be specified at link time.
-
-'-mfriz'
-'-mno-friz'
- Generate (do not generate) the 'friz' instruction when the
- '-funsafe-math-optimizations' option is used to optimize rounding
+ libraries. GCC currently emits calls to `acosd2', `acosf4',
+ `acoshd2', `acoshf4', `asind2', `asinf4', `asinhd2', `asinhf4',
+ `atan2d2', `atan2f4', `atand2', `atanf4', `atanhd2', `atanhf4',
+ `cbrtd2', `cbrtf4', `cosd2', `cosf4', `coshd2', `coshf4',
+ `erfcd2', `erfcf4', `erfd2', `erff4', `exp2d2', `exp2f4', `expd2',
+ `expf4', `expm1d2', `expm1f4', `hypotd2', `hypotf4', `lgammad2',
+ `lgammaf4', `log10d2', `log10f4', `log1pd2', `log1pf4', `log2d2',
+ `log2f4', `logd2', `logf4', `powd2', `powf4', `sind2', `sinf4',
+ `sinhd2', `sinhf4', `sqrtd2', `sqrtf4', `tand2', `tanf4',
+ `tanhd2', and `tanhf4' when generating code for power7. Both
+ `-ftree-vectorize' and `-funsafe-math-optimizations' must also be
+ enabled. The MASS libraries must be specified at link time.
+
+`-mfriz'
+`-mno-friz'
+ Generate (do not generate) the `friz' instruction when the
+ `-funsafe-math-optimizations' option is used to optimize rounding
of floating-point values to 64-bit integer and back to floating
- point. The 'friz' instruction does not return the same value if
+ point. The `friz' instruction does not return the same value if
the floating-point number is too large to fit in an integer.
-'-mpointers-to-nested-functions'
-'-mno-pointers-to-nested-functions'
+`-mpointers-to-nested-functions'
+`-mno-pointers-to-nested-functions'
Generate (do not generate) code to load up the static chain
- register ('r11') when calling through a pointer on AIX and 64-bit
+ register (`r11') when calling through a pointer on AIX and 64-bit
Linux systems where a function pointer points to a 3-word
descriptor giving the function address, TOC value to be loaded in
- register 'r2', and static chain value to be loaded in register
- 'r11'. The '-mpointers-to-nested-functions' is on by default. You
- cannot call through pointers to nested functions or pointers to
- functions compiled in other languages that use the static chain if
- you use '-mno-pointers-to-nested-functions'.
-
-'-msave-toc-indirect'
-'-mno-save-toc-indirect'
+ register `r2', and static chain value to be loaded in register
+ `r11'. The `-mpointers-to-nested-functions' is on by default.
+ You cannot call through pointers to nested functions or pointers
+ to functions compiled in other languages that use the static chain
+ if you use `-mno-pointers-to-nested-functions'.
+
+`-msave-toc-indirect'
+`-mno-save-toc-indirect'
Generate (do not generate) code to save the TOC value in the
reserved stack location in the function prologue if the function
calls through a pointer on AIX and 64-bit Linux systems. If the
- TOC value is not saved in the prologue, it is saved just before the
- call through the pointer. The '-mno-save-toc-indirect' option is
- the default.
+ TOC value is not saved in the prologue, it is saved just before
+ the call through the pointer. The `-mno-save-toc-indirect' option
+ is the default.
-'-mcompat-align-parm'
-'-mno-compat-align-parm'
+`-mcompat-align-parm'
+`-mno-compat-align-parm'
Generate (do not generate) code to pass structure parameters with a
maximum alignment of 64 bits, for compatibility with older versions
of GCC.
@@ -18337,11 +18452,11 @@ These '-m' options are defined for the IBM RS/6000 and PowerPC:
Older versions of GCC (prior to 4.9.0) incorrectly did not align a
structure parameter on a 128-bit boundary when that structure
contained a member requiring 128-bit alignment. This is corrected
- in more recent versions of GCC. This option may be used to generate
- code that is compatible with functions compiled with older versions
- of GCC.
+ in more recent versions of GCC. This option may be used to
+ generate code that is compatible with functions compiled with
+ older versions of GCC.
- The '-mno-compat-align-parm' option is the default.
+ The `-mno-compat-align-parm' option is the default.

File: gcc.info, Node: RX Options, Next: S/390 and zSeries Options, Prev: RS/6000 and PowerPC Options, Up: Submodel Options
@@ -18351,51 +18466,51 @@ File: gcc.info, Node: RX Options, Next: S/390 and zSeries Options, Prev: RS/6
These command-line options are defined for RX targets:
-'-m64bit-doubles'
-'-m32bit-doubles'
- Make the 'double' data type be 64 bits ('-m64bit-doubles') or 32
- bits ('-m32bit-doubles') in size. The default is
- '-m32bit-doubles'. _Note_ RX floating-point hardware only works on
- 32-bit values, which is why the default is '-m32bit-doubles'.
+`-m64bit-doubles'
+`-m32bit-doubles'
+ Make the `double' data type be 64 bits (`-m64bit-doubles') or 32
+ bits (`-m32bit-doubles') in size. The default is
+ `-m32bit-doubles'. _Note_ RX floating-point hardware only works
+ on 32-bit values, which is why the default is `-m32bit-doubles'.
-'-fpu'
-'-nofpu'
- Enables ('-fpu') or disables ('-nofpu') the use of RX
+`-fpu'
+`-nofpu'
+ Enables (`-fpu') or disables (`-nofpu') the use of RX
floating-point hardware. The default is enabled for the RX600
series and disabled for the RX200 series.
Floating-point instructions are only generated for 32-bit
- floating-point values, however, so the FPU hardware is not used for
- doubles if the '-m64bit-doubles' option is used.
+ floating-point values, however, so the FPU hardware is not used
+ for doubles if the `-m64bit-doubles' option is used.
- _Note_ If the '-fpu' option is enabled then
- '-funsafe-math-optimizations' is also enabled automatically. This
+ _Note_ If the `-fpu' option is enabled then
+ `-funsafe-math-optimizations' is also enabled automatically. This
is because the RX FPU instructions are themselves unsafe.
-'-mcpu=NAME'
+`-mcpu=NAME'
Selects the type of RX CPU to be targeted. Currently three types
- are supported, the generic 'RX600' and 'RX200' series hardware and
- the specific 'RX610' CPU. The default is 'RX600'.
+ are supported, the generic `RX600' and `RX200' series hardware and
+ the specific `RX610' CPU. The default is `RX600'.
- The only difference between 'RX600' and 'RX610' is that the 'RX610'
- does not support the 'MVTIPL' instruction.
+ The only difference between `RX600' and `RX610' is that the
+ `RX610' does not support the `MVTIPL' instruction.
- The 'RX200' series does not have a hardware floating-point unit and
- so '-nofpu' is enabled by default when this type is selected.
+ The `RX200' series does not have a hardware floating-point unit
+ and so `-nofpu' is enabled by default when this type is selected.
-'-mbig-endian-data'
-'-mlittle-endian-data'
+`-mbig-endian-data'
+`-mlittle-endian-data'
Store data (but not code) in the big-endian format. The default is
- '-mlittle-endian-data', i.e. to store data in the little-endian
+ `-mlittle-endian-data', i.e. to store data in the little-endian
format.
-'-msmall-data-limit=N'
+`-msmall-data-limit=N'
Specifies the maximum size in bytes of global and static variables
which can be placed into the small data area. Using the small data
area can lead to smaller and faster code, but the size of area is
limited and it is up to the programmer to ensure that the area does
not overflow. Also when the small data area is used one of the
- RX's registers (usually 'r13') is reserved for use pointing to this
+ RX's registers (usually `r13') is reserved for use pointing to this
area, so it is no longer available for use by the compiler. This
could result in slower and/or larger code if variables are pushed
onto the stack instead of being held in this register.
@@ -18406,25 +18521,25 @@ These command-line options are defined for RX targets:
The default value is zero, which disables this feature. Note, this
feature is not enabled by default with higher optimization levels
- ('-O2' etc) because of the potentially detrimental effects of
+ (`-O2' etc) because of the potentially detrimental effects of
reserving a register. It is up to the programmer to experiment and
discover whether this feature is of benefit to their program. See
- the description of the '-mpid' option for a description of how the
+ the description of the `-mpid' option for a description of how the
actual register to hold the small data area pointer is chosen.
-'-msim'
-'-mno-sim'
+`-msim'
+`-mno-sim'
Use the simulator runtime. The default is to use the libgloss
board-specific runtime.
-'-mas100-syntax'
-'-mno-as100-syntax'
+`-mas100-syntax'
+`-mno-as100-syntax'
When generating assembler output use a syntax that is compatible
- with Renesas's AS100 assembler. This syntax can also be handled by
- the GAS assembler, but it has some restrictions so it is not
+ with Renesas's AS100 assembler. This syntax can also be handled
+ by the GAS assembler, but it has some restrictions so it is not
generated by default.
-'-mmax-constant-size=N'
+`-mmax-constant-size=N'
Specifies the maximum size, in bytes, of a constant that can be
used as an operand in a RX instruction. Although the RX
instruction set does allow constants of up to 4 bytes in length to
@@ -18437,29 +18552,29 @@ These command-line options are defined for RX targets:
The value N can be between 0 and 4. A value of 0 (the default) or
4 means that constants of any size are allowed.
-'-mrelax'
+`-mrelax'
Enable linker relaxation. Linker relaxation is a process whereby
the linker attempts to reduce the size of a program by finding
shorter versions of various instructions. Disabled by default.
-'-mint-register=N'
+`-mint-register=N'
Specify the number of registers to reserve for fast interrupt
- handler functions. The value N can be between 0 and 4. A value of
- 1 means that register 'r13' is reserved for the exclusive use of
- fast interrupt handlers. A value of 2 reserves 'r13' and 'r12'. A
- value of 3 reserves 'r13', 'r12' and 'r11', and a value of 4
- reserves 'r13' through 'r10'. A value of 0, the default, does not
- reserve any registers.
-
-'-msave-acc-in-interrupts'
+ handler functions. The value N can be between 0 and 4. A value
+ of 1 means that register `r13' is reserved for the exclusive use
+ of fast interrupt handlers. A value of 2 reserves `r13' and
+ `r12'. A value of 3 reserves `r13', `r12' and `r11', and a value
+ of 4 reserves `r13' through `r10'. A value of 0, the default,
+ does not reserve any registers.
+
+`-msave-acc-in-interrupts'
Specifies that interrupt handler functions should preserve the
accumulator register. This is only necessary if normal code might
use the accumulator register, for example because it performs
64-bit multiplications. The default is to ignore the accumulator
as this makes the interrupt handlers faster.
-'-mpid'
-'-mno-pid'
+`-mpid'
+`-mno-pid'
Enables the generation of position independent data. When enabled
any access to constant data is done via an offset from a base
address held in a register. This allows the location of constant
@@ -18468,36 +18583,37 @@ These command-line options are defined for RX targets:
tight memory constraints. Data that can be modified is not
affected by this option.
- Note, using this feature reserves a register, usually 'r13', for
+ Note, using this feature reserves a register, usually `r13', for
the constant data base address. This can result in slower and/or
larger code, especially in complicated functions.
The actual register chosen to hold the constant data base address
- depends upon whether the '-msmall-data-limit' and/or the
- '-mint-register' command-line options are enabled. Starting with
- register 'r13' and proceeding downwards, registers are allocated
- first to satisfy the requirements of '-mint-register', then '-mpid'
- and finally '-msmall-data-limit'. Thus it is possible for the
- small data area register to be 'r8' if both '-mint-register=4' and
- '-mpid' are specified on the command line.
+ depends upon whether the `-msmall-data-limit' and/or the
+ `-mint-register' command-line options are enabled. Starting with
+ register `r13' and proceeding downwards, registers are allocated
+ first to satisfy the requirements of `-mint-register', then
+ `-mpid' and finally `-msmall-data-limit'. Thus it is possible for
+ the small data area register to be `r8' if both `-mint-register=4'
+ and `-mpid' are specified on the command line.
By default this feature is not enabled. The default can be
- restored via the '-mno-pid' command-line option.
+ restored via the `-mno-pid' command-line option.
-'-mno-warn-multiple-fast-interrupts'
-'-mwarn-multiple-fast-interrupts'
+`-mno-warn-multiple-fast-interrupts'
+`-mwarn-multiple-fast-interrupts'
Prevents GCC from issuing a warning message if it finds more than
one fast interrupt handler when it is compiling a file. The
- default is to issue a warning for each extra fast interrupt handler
- found, as the RX only supports one such interrupt.
+ default is to issue a warning for each extra fast interrupt
+ handler found, as the RX only supports one such interrupt.
+
- _Note:_ The generic GCC command-line option '-ffixed-REG' has special
-significance to the RX port when used with the 'interrupt' function
-attribute. This attribute indicates a function intended to process fast
-interrupts. GCC ensures that it only uses the registers 'r10', 'r11',
-'r12' and/or 'r13' and only provided that the normal use of the
-corresponding registers have been restricted via the '-ffixed-REG' or
-'-mint-register' command-line options.
+ _Note:_ The generic GCC command-line option `-ffixed-REG' has special
+significance to the RX port when used with the `interrupt' function
+attribute. This attribute indicates a function intended to process
+fast interrupts. GCC ensures that it only uses the registers `r10',
+`r11', `r12' and/or `r13' and only provided that the normal use of the
+corresponding registers have been restricted via the `-ffixed-REG' or
+`-mint-register' command-line options.

File: gcc.info, Node: S/390 and zSeries Options, Next: Score Options, Prev: RX Options, Up: Submodel Options
@@ -18505,181 +18621,184 @@ File: gcc.info, Node: S/390 and zSeries Options, Next: Score Options, Prev: R
3.17.39 S/390 and zSeries Options
---------------------------------
-These are the '-m' options defined for the S/390 and zSeries
+These are the `-m' options defined for the S/390 and zSeries
architecture.
-'-mhard-float'
-'-msoft-float'
+`-mhard-float'
+`-msoft-float'
Use (do not use) the hardware floating-point instructions and
- registers for floating-point operations. When '-msoft-float' is
- specified, functions in 'libgcc.a' are used to perform
- floating-point operations. When '-mhard-float' is specified, the
+ registers for floating-point operations. When `-msoft-float' is
+ specified, functions in `libgcc.a' are used to perform
+ floating-point operations. When `-mhard-float' is specified, the
compiler generates IEEE floating-point instructions. This is the
default.
-'-mhard-dfp'
-'-mno-hard-dfp'
+`-mhard-dfp'
+`-mno-hard-dfp'
Use (do not use) the hardware decimal-floating-point instructions
- for decimal-floating-point operations. When '-mno-hard-dfp' is
- specified, functions in 'libgcc.a' are used to perform
- decimal-floating-point operations. When '-mhard-dfp' is specified,
- the compiler generates decimal-floating-point hardware
- instructions. This is the default for '-march=z9-ec' or higher.
-
-'-mlong-double-64'
-'-mlong-double-128'
- These switches control the size of 'long double' type. A size of
- 64 bits makes the 'long double' type equivalent to the 'double'
- type. This is the default.
-
-'-mbackchain'
-'-mno-backchain'
- Store (do not store) the address of the caller's frame as backchain
- pointer into the callee's stack frame. A backchain may be needed
- to allow debugging using tools that do not understand DWARF 2 call
- frame information. When '-mno-packed-stack' is in effect, the
- backchain pointer is stored at the bottom of the stack frame; when
- '-mpacked-stack' is in effect, the backchain is placed into the
- topmost word of the 96/160 byte register save area.
-
- In general, code compiled with '-mbackchain' is call-compatible
- with code compiled with '-mmo-backchain'; however, use of the
+ for decimal-floating-point operations. When `-mno-hard-dfp' is
+ specified, functions in `libgcc.a' are used to perform
+ decimal-floating-point operations. When `-mhard-dfp' is
+ specified, the compiler generates decimal-floating-point hardware
+ instructions. This is the default for `-march=z9-ec' or higher.
+
+`-mlong-double-64'
+`-mlong-double-128'
+ These switches control the size of `long double' type. A size of
+ 64 bits makes the `long double' type equivalent to the `double'
+ type. This is the default.
+
+`-mbackchain'
+`-mno-backchain'
+ Store (do not store) the address of the caller's frame as
+ backchain pointer into the callee's stack frame. A backchain may
+ be needed to allow debugging using tools that do not understand
+ DWARF 2 call frame information. When `-mno-packed-stack' is in
+ effect, the backchain pointer is stored at the bottom of the stack
+ frame; when `-mpacked-stack' is in effect, the backchain is placed
+ into the topmost word of the 96/160 byte register save area.
+
+ In general, code compiled with `-mbackchain' is call-compatible
+ with code compiled with `-mmo-backchain'; however, use of the
backchain for debugging purposes usually requires that the whole
- binary is built with '-mbackchain'. Note that the combination of
- '-mbackchain', '-mpacked-stack' and '-mhard-float' is not
- supported. In order to build a linux kernel use '-msoft-float'.
+ binary is built with `-mbackchain'. Note that the combination of
+ `-mbackchain', `-mpacked-stack' and `-mhard-float' is not
+ supported. In order to build a linux kernel use `-msoft-float'.
The default is to not maintain the backchain.
-'-mpacked-stack'
-'-mno-packed-stack'
- Use (do not use) the packed stack layout. When '-mno-packed-stack'
- is specified, the compiler uses the all fields of the 96/160 byte
- register save area only for their default purpose; unused fields
- still take up stack space. When '-mpacked-stack' is specified,
- register save slots are densely packed at the top of the register
- save area; unused space is reused for other purposes, allowing for
- more efficient use of the available stack space. However, when
- '-mbackchain' is also in effect, the topmost word of the save area
- is always used to store the backchain, and the return address
- register is always saved two words below the backchain.
+`-mpacked-stack'
+`-mno-packed-stack'
+ Use (do not use) the packed stack layout. When
+ `-mno-packed-stack' is specified, the compiler uses the all fields
+ of the 96/160 byte register save area only for their default
+ purpose; unused fields still take up stack space. When
+ `-mpacked-stack' is specified, register save slots are densely
+ packed at the top of the register save area; unused space is
+ reused for other purposes, allowing for more efficient use of the
+ available stack space. However, when `-mbackchain' is also in
+ effect, the topmost word of the save area is always used to store
+ the backchain, and the return address register is always saved two
+ words below the backchain.
As long as the stack frame backchain is not used, code generated
- with '-mpacked-stack' is call-compatible with code generated with
- '-mno-packed-stack'. Note that some non-FSF releases of GCC 2.95
+ with `-mpacked-stack' is call-compatible with code generated with
+ `-mno-packed-stack'. Note that some non-FSF releases of GCC 2.95
for S/390 or zSeries generated code that uses the stack frame
backchain at run time, not just for debugging purposes. Such code
- is not call-compatible with code compiled with '-mpacked-stack'.
- Also, note that the combination of '-mbackchain', '-mpacked-stack'
- and '-mhard-float' is not supported. In order to build a linux
- kernel use '-msoft-float'.
+ is not call-compatible with code compiled with `-mpacked-stack'.
+ Also, note that the combination of `-mbackchain', `-mpacked-stack'
+ and `-mhard-float' is not supported. In order to build a linux
+ kernel use `-msoft-float'.
The default is to not use the packed stack layout.
-'-msmall-exec'
-'-mno-small-exec'
- Generate (or do not generate) code using the 'bras' instruction to
+`-msmall-exec'
+`-mno-small-exec'
+ Generate (or do not generate) code using the `bras' instruction to
do subroutine calls. This only works reliably if the total
executable size does not exceed 64k. The default is to use the
- 'basr' instruction instead, which does not have this limitation.
-
-'-m64'
-'-m31'
- When '-m31' is specified, generate code compliant to the GNU/Linux
- for S/390 ABI. When '-m64' is specified, generate code compliant
- to the GNU/Linux for zSeries ABI. This allows GCC in particular to
- generate 64-bit instructions. For the 's390' targets, the default
- is '-m31', while the 's390x' targets default to '-m64'.
-
-'-mzarch'
-'-mesa'
- When '-mzarch' is specified, generate code using the instructions
- available on z/Architecture. When '-mesa' is specified, generate
+ `basr' instruction instead, which does not have this limitation.
+
+`-m64'
+`-m31'
+ When `-m31' is specified, generate code compliant to the GNU/Linux
+ for S/390 ABI. When `-m64' is specified, generate code compliant
+ to the GNU/Linux for zSeries ABI. This allows GCC in particular
+ to generate 64-bit instructions. For the `s390' targets, the
+ default is `-m31', while the `s390x' targets default to `-m64'.
+
+`-mzarch'
+`-mesa'
+ When `-mzarch' is specified, generate code using the instructions
+ available on z/Architecture. When `-mesa' is specified, generate
code using the instructions available on ESA/390. Note that
- '-mesa' is not possible with '-m64'. When generating code
- compliant to the GNU/Linux for S/390 ABI, the default is '-mesa'.
+ `-mesa' is not possible with `-m64'. When generating code
+ compliant to the GNU/Linux for S/390 ABI, the default is `-mesa'.
When generating code compliant to the GNU/Linux for zSeries ABI,
- the default is '-mzarch'.
+ the default is `-mzarch'.
-'-mmvcle'
-'-mno-mvcle'
- Generate (or do not generate) code using the 'mvcle' instruction to
- perform block moves. When '-mno-mvcle' is specified, use a 'mvc'
- loop instead. This is the default unless optimizing for size.
+`-mmvcle'
+`-mno-mvcle'
+ Generate (or do not generate) code using the `mvcle' instruction
+ to perform block moves. When `-mno-mvcle' is specified, use a
+ `mvc' loop instead. This is the default unless optimizing for
+ size.
-'-mdebug'
-'-mno-debug'
+`-mdebug'
+`-mno-debug'
Print (or do not print) additional debug information when
compiling. The default is to not print debug information.
-'-march=CPU-TYPE'
+`-march=CPU-TYPE'
Generate code that runs on CPU-TYPE, which is the name of a system
representing a certain processor type. Possible values for
- CPU-TYPE are 'g5', 'g6', 'z900', 'z990', 'z9-109', 'z9-ec', 'z10',
- 'z196', and 'zEC12'. When generating code using the instructions
- available on z/Architecture, the default is '-march=z900'.
- Otherwise, the default is '-march=g5'.
+ CPU-TYPE are `g5', `g6', `z900', `z990', `z9-109', `z9-ec', `z10',
+ `z196', `zEC12', and `z13'. When generating code using the
+ instructions available on z/Architecture, the default is
+ `-march=z900'. Otherwise, the default is `-march=g5'.
-'-mtune=CPU-TYPE'
+`-mtune=CPU-TYPE'
Tune to CPU-TYPE everything applicable about the generated code,
- except for the ABI and the set of available instructions. The list
- of CPU-TYPE values is the same as for '-march'. The default is the
- value used for '-march'.
+ except for the ABI and the set of available instructions. The
+ list of CPU-TYPE values is the same as for `-march'. The default
+ is the value used for `-march'.
-'-mtpf-trace'
-'-mno-tpf-trace'
+`-mtpf-trace'
+`-mno-tpf-trace'
Generate code that adds (does not add) in TPF OS specific branches
to trace routines in the operating system. This option is off by
default, even when compiling for the TPF OS.
-'-mfused-madd'
-'-mno-fused-madd'
+`-mfused-madd'
+`-mno-fused-madd'
Generate code that uses (does not use) the floating-point multiply
and accumulate instructions. These instructions are generated by
default if hardware floating point is used.
-'-mwarn-framesize=FRAMESIZE'
+`-mwarn-framesize=FRAMESIZE'
Emit a warning if the current function exceeds the given frame
- size. Because this is a compile-time check it doesn't need to be a
- real problem when the program runs. It is intended to identify
+ size. Because this is a compile-time check it doesn't need to be
+ a real problem when the program runs. It is intended to identify
functions that most probably cause a stack overflow. It is useful
- to be used in an environment with limited stack size e.g. the linux
- kernel.
+ to be used in an environment with limited stack size e.g. the
+ linux kernel.
-'-mwarn-dynamicstack'
- Emit a warning if the function calls 'alloca' or uses
+`-mwarn-dynamicstack'
+ Emit a warning if the function calls `alloca' or uses
dynamically-sized arrays. This is generally a bad idea with a
limited stack size.
-'-mstack-guard=STACK-GUARD'
-'-mstack-size=STACK-SIZE'
+`-mstack-guard=STACK-GUARD'
+`-mstack-size=STACK-SIZE'
If these options are provided the S/390 back end emits additional
instructions in the function prologue that trigger a trap if the
- stack size is STACK-GUARD bytes above the STACK-SIZE (remember that
- the stack on S/390 grows downward). If the STACK-GUARD option is
- omitted the smallest power of 2 larger than the frame size of the
- compiled function is chosen. These options are intended to be used
- to help debugging stack overflow problems. The additionally
- emitted code causes only little overhead and hence can also be used
- in production-like systems without greater performance degradation.
- The given values have to be exact powers of 2 and STACK-SIZE has to
- be greater than STACK-GUARD without exceeding 64k. In order to be
- efficient the extra code makes the assumption that the stack starts
- at an address aligned to the value given by STACK-SIZE. The
- STACK-GUARD option can only be used in conjunction with STACK-SIZE.
-
-'-mhotpatch=PRE-HALFWORDS,POST-HALFWORDS'
+ stack size is STACK-GUARD bytes above the STACK-SIZE (remember
+ that the stack on S/390 grows downward). If the STACK-GUARD
+ option is omitted the smallest power of 2 larger than the frame
+ size of the compiled function is chosen. These options are
+ intended to be used to help debugging stack overflow problems.
+ The additionally emitted code causes only little overhead and
+ hence can also be used in production-like systems without greater
+ performance degradation. The given values have to be exact powers
+ of 2 and STACK-SIZE has to be greater than STACK-GUARD without
+ exceeding 64k. In order to be efficient the extra code makes the
+ assumption that the stack starts at an address aligned to the
+ value given by STACK-SIZE. The STACK-GUARD option can only be
+ used in conjunction with STACK-SIZE.
+
+`-mhotpatch=PRE-HALFWORDS,POST-HALFWORDS'
If the hotpatch option is enabled, a "hot-patching" function
prologue is generated for all functions in the compilation unit.
The funtion label is prepended with the given number of two-byte
NOP instructions (PRE-HALFWORDS, maximum 1000000). After the
- label, 2 * POST-HALFWORDS bytes are appended, using the largest NOP
- like instructions the architecture allows (maximum 1000000).
+ label, 2 * POST-HALFWORDS bytes are appended, using the largest
+ NOP like instructions the architecture allows (maximum 1000000).
If both arguments are zero, hotpatching is disabled.
This option can be overridden for individual functions with the
- 'hotpatch' attribute.
+ `hotpatch' attribute.

File: gcc.info, Node: Score Options, Next: SH Options, Prev: S/390 and zSeries Options, Up: Submodel Options
@@ -18689,33 +18808,32 @@ File: gcc.info, Node: Score Options, Next: SH Options, Prev: S/390 and zSerie
These options are defined for Score implementations:
-'-meb'
+`-meb'
Compile code for big-endian mode. This is the default.
-'-mel'
+`-mel'
Compile code for little-endian mode.
-'-mnhwloop'
- Disable generation of 'bcnz' instructions.
+`-mnhwloop'
+ Disable generation of `bcnz' instructions.
-'-muls'
+`-muls'
Enable generation of unaligned load and store instructions.
-'-mmac'
- Enable the use of multiply-accumulate instructions. Disabled by
+`-mmac'
+ Enable the use of multiply-accumulate instructions. Disabled by
default.
-'-mscore5'
+`-mscore5'
Specify the SCORE5 as the target architecture.
-'-mscore5u'
+`-mscore5u'
Specify the SCORE5U of the target architecture.
-'-mscore7'
- Specify the SCORE7 as the target architecture. This is the
- default.
+`-mscore7'
+ Specify the SCORE7 as the target architecture. This is the default.
-'-mscore7d'
+`-mscore7d'
Specify the SCORE7D as the target architecture.

@@ -18724,257 +18842,258 @@ File: gcc.info, Node: SH Options, Next: Solaris 2 Options, Prev: Score Option
3.17.41 SH Options
------------------
-These '-m' options are defined for the SH implementations:
+These `-m' options are defined for the SH implementations:
-'-m1'
+`-m1'
Generate code for the SH1.
-'-m2'
+`-m2'
Generate code for the SH2.
-'-m2e'
+`-m2e'
Generate code for the SH2e.
-'-m2a-nofpu'
- Generate code for the SH2a without FPU, or for a SH2a-FPU in such a
- way that the floating-point unit is not used.
+`-m2a-nofpu'
+ Generate code for the SH2a without FPU, or for a SH2a-FPU in such
+ a way that the floating-point unit is not used.
-'-m2a-single-only'
+`-m2a-single-only'
Generate code for the SH2a-FPU, in such a way that no
double-precision floating-point operations are used.
-'-m2a-single'
+`-m2a-single'
Generate code for the SH2a-FPU assuming the floating-point unit is
in single-precision mode by default.
-'-m2a'
+`-m2a'
Generate code for the SH2a-FPU assuming the floating-point unit is
in double-precision mode by default.
-'-m3'
+`-m3'
Generate code for the SH3.
-'-m3e'
+`-m3e'
Generate code for the SH3e.
-'-m4-nofpu'
+`-m4-nofpu'
Generate code for the SH4 without a floating-point unit.
-'-m4-single-only'
+`-m4-single-only'
Generate code for the SH4 with a floating-point unit that only
supports single-precision arithmetic.
-'-m4-single'
+`-m4-single'
Generate code for the SH4 assuming the floating-point unit is in
single-precision mode by default.
-'-m4'
+`-m4'
Generate code for the SH4.
-'-m4-100'
+`-m4-100'
Generate code for SH4-100.
-'-m4-100-nofpu'
+`-m4-100-nofpu'
Generate code for SH4-100 in such a way that the floating-point
unit is not used.
-'-m4-100-single'
+`-m4-100-single'
Generate code for SH4-100 assuming the floating-point unit is in
single-precision mode by default.
-'-m4-100-single-only'
+`-m4-100-single-only'
Generate code for SH4-100 in such a way that no double-precision
floating-point operations are used.
-'-m4-200'
+`-m4-200'
Generate code for SH4-200.
-'-m4-200-nofpu'
+`-m4-200-nofpu'
Generate code for SH4-200 without in such a way that the
floating-point unit is not used.
-'-m4-200-single'
+`-m4-200-single'
Generate code for SH4-200 assuming the floating-point unit is in
single-precision mode by default.
-'-m4-200-single-only'
+`-m4-200-single-only'
Generate code for SH4-200 in such a way that no double-precision
floating-point operations are used.
-'-m4-300'
+`-m4-300'
Generate code for SH4-300.
-'-m4-300-nofpu'
+`-m4-300-nofpu'
Generate code for SH4-300 without in such a way that the
floating-point unit is not used.
-'-m4-300-single'
+`-m4-300-single'
Generate code for SH4-300 in such a way that no double-precision
floating-point operations are used.
-'-m4-300-single-only'
+`-m4-300-single-only'
Generate code for SH4-300 in such a way that no double-precision
floating-point operations are used.
-'-m4-340'
+`-m4-340'
Generate code for SH4-340 (no MMU, no FPU).
-'-m4-500'
- Generate code for SH4-500 (no FPU). Passes '-isa=sh4-nofpu' to the
+`-m4-500'
+ Generate code for SH4-500 (no FPU). Passes `-isa=sh4-nofpu' to the
assembler.
-'-m4a-nofpu'
+`-m4a-nofpu'
Generate code for the SH4al-dsp, or for a SH4a in such a way that
the floating-point unit is not used.
-'-m4a-single-only'
+`-m4a-single-only'
Generate code for the SH4a, in such a way that no double-precision
floating-point operations are used.
-'-m4a-single'
+`-m4a-single'
Generate code for the SH4a assuming the floating-point unit is in
single-precision mode by default.
-'-m4a'
+`-m4a'
Generate code for the SH4a.
-'-m4al'
- Same as '-m4a-nofpu', except that it implicitly passes '-dsp' to
+`-m4al'
+ Same as `-m4a-nofpu', except that it implicitly passes `-dsp' to
the assembler. GCC doesn't generate any DSP instructions at the
moment.
-'-m5-32media'
+`-m5-32media'
Generate 32-bit code for SHmedia.
-'-m5-32media-nofpu'
+`-m5-32media-nofpu'
Generate 32-bit code for SHmedia in such a way that the
floating-point unit is not used.
-'-m5-64media'
+`-m5-64media'
Generate 64-bit code for SHmedia.
-'-m5-64media-nofpu'
+`-m5-64media-nofpu'
Generate 64-bit code for SHmedia in such a way that the
floating-point unit is not used.
-'-m5-compact'
+`-m5-compact'
Generate code for SHcompact.
-'-m5-compact-nofpu'
+`-m5-compact-nofpu'
Generate code for SHcompact in such a way that the floating-point
unit is not used.
-'-mb'
+`-mb'
Compile code for the processor in big-endian mode.
-'-ml'
+`-ml'
Compile code for the processor in little-endian mode.
-'-mdalign'
+`-mdalign'
Align doubles at 64-bit boundaries. Note that this changes the
calling conventions, and thus some functions from the standard C
- library do not work unless you recompile it first with '-mdalign'.
+ library do not work unless you recompile it first with `-mdalign'.
-'-mrelax'
+`-mrelax'
Shorten some address references at link time, when possible; uses
- the linker option '-relax'.
+ the linker option `-relax'.
-'-mbigtable'
- Use 32-bit offsets in 'switch' tables. The default is to use
+`-mbigtable'
+ Use 32-bit offsets in `switch' tables. The default is to use
16-bit offsets.
-'-mbitops'
+`-mbitops'
Enable the use of bit manipulation instructions on SH2A.
-'-mfmovd'
- Enable the use of the instruction 'fmovd'. Check '-mdalign' for
+`-mfmovd'
+ Enable the use of the instruction `fmovd'. Check `-mdalign' for
alignment constraints.
-'-mrenesas'
+`-mrenesas'
Comply with the calling conventions defined by Renesas.
-'-mno-renesas'
+`-mno-renesas'
Comply with the calling conventions defined for GCC before the
- Renesas conventions were available. This option is the default for
- all targets of the SH toolchain.
+ Renesas conventions were available. This option is the default
+ for all targets of the SH toolchain.
-'-mnomacsave'
- Mark the 'MAC' register as call-clobbered, even if '-mrenesas' is
+`-mnomacsave'
+ Mark the `MAC' register as call-clobbered, even if `-mrenesas' is
given.
-'-mieee'
-'-mno-ieee'
+`-mieee'
+`-mno-ieee'
Control the IEEE compliance of floating-point comparisons, which
affects the handling of cases where the result of a comparison is
- unordered. By default '-mieee' is implicitly enabled. If
- '-ffinite-math-only' is enabled '-mno-ieee' is implicitly set,
- which results in faster floating-point greater-equal and less-equal
- comparisons. The implcit settings can be overridden by specifying
- either '-mieee' or '-mno-ieee'.
+ unordered. By default `-mieee' is implicitly enabled. If
+ `-ffinite-math-only' is enabled `-mno-ieee' is implicitly set,
+ which results in faster floating-point greater-equal and
+ less-equal comparisons. The implcit settings can be overridden by
+ specifying either `-mieee' or `-mno-ieee'.
-'-minline-ic_invalidate'
+`-minline-ic_invalidate'
Inline code to invalidate instruction cache entries after setting
up nested function trampolines. This option has no effect if
- '-musermode' is in effect and the selected code generation option
- (e.g. '-m4') does not allow the use of the 'icbi' instruction. If
+ `-musermode' is in effect and the selected code generation option
+ (e.g. `-m4') does not allow the use of the `icbi' instruction. If
the selected code generation option does not allow the use of the
- 'icbi' instruction, and '-musermode' is not in effect, the inlined
+ `icbi' instruction, and `-musermode' is not in effect, the inlined
code manipulates the instruction cache address array directly with
an associative write. This not only requires privileged mode at
run time, but it also fails if the cache line had been mapped via
the TLB and has become unmapped.
-'-misize'
+`-misize'
Dump instruction size and location in the assembly code.
-'-mpadstruct'
+`-mpadstruct'
This option is deprecated. It pads structures to multiple of 4
bytes, which is incompatible with the SH ABI.
-'-matomic-model=MODEL'
+`-matomic-model=MODEL'
Sets the model of atomic operations and additional parameters as a
- comma separated list. For details on the atomic built-in functions
- see *note __atomic Builtins::. The following models and parameters
- are supported:
+ comma separated list. For details on the atomic built-in
+ functions see *note __atomic Builtins::. The following models and
+ parameters are supported:
- 'none'
+ `none'
Disable compiler generated atomic sequences and emit library
calls for atomic operations. This is the default if the
- target is not 'sh*-*-linux*'.
+ target is not `sh*-*-linux*'.
- 'soft-gusa'
+ `soft-gusa'
Generate GNU/Linux compatible gUSA software atomic sequences
for the atomic built-in functions. The generated atomic
sequences require additional support from the
interrupt/exception handling code of the system and are only
suitable for SH3* and SH4* single-core systems. This option
- is enabled by default when the target is 'sh*-*-linux*' and
+ is enabled by default when the target is `sh*-*-linux*' and
SH3* or SH4*. When the target is SH4A, this option also
- partially utilizes the hardware atomic instructions 'movli.l'
- and 'movco.l' to create more efficient code, unless 'strict'
+ partially utilizes the hardware atomic instructions `movli.l'
+ and `movco.l' to create more efficient code, unless `strict'
is specified.
- 'soft-tcb'
+ `soft-tcb'
Generate software atomic sequences that use a variable in the
thread control block. This is a variation of the gUSA
sequences which can also be used on SH1* and SH2* targets.
- The generated atomic sequences require additional support from
- the interrupt/exception handling code of the system and are
- only suitable for single-core systems. When using this model,
- the 'gbr-offset=' parameter has to be specified as well.
+ The generated atomic sequences require additional support
+ from the interrupt/exception handling code of the system and
+ are only suitable for single-core systems. When using this
+ model, the `gbr-offset=' parameter has to be specified as
+ well.
- 'soft-imask'
+ `soft-imask'
Generate software atomic sequences that temporarily disable
- interrupts by setting 'SR.IMASK = 1111'. This model works
+ interrupts by setting `SR.IMASK = 1111'. This model works
only when the program runs in privileged mode and is only
- suitable for single-core systems. Additional support from the
- interrupt/exception handling code of the system is not
+ suitable for single-core systems. Additional support from
+ the interrupt/exception handling code of the system is not
required. This model is enabled by default when the target is
- 'sh*-*-linux*' and SH1* or SH2*.
+ `sh*-*-linux*' and SH1* or SH2*.
- 'hard-llcs'
- Generate hardware atomic sequences using the 'movli.l' and
- 'movco.l' instructions only. This is only available on SH4A
+ `hard-llcs'
+ Generate hardware atomic sequences using the `movli.l' and
+ `movco.l' instructions only. This is only available on SH4A
and is suitable for multi-core systems. Since the hardware
instructions support only 32 bit atomic variables access to 8
or 16 bit variables is emulated with 32 bit accesses. Code
@@ -18984,49 +19103,51 @@ These '-m' options are defined for the SH implementations:
interrupt/exception handling code of the system is not
required for this model.
- 'gbr-offset='
+ `gbr-offset='
This parameter specifies the offset in bytes of the variable
in the thread control block structure that should be used by
- the generated atomic sequences when the 'soft-tcb' model has
+ the generated atomic sequences when the `soft-tcb' model has
been selected. For other models this parameter is ignored.
- The specified value must be an integer multiple of four and in
- the range 0-1020.
+ The specified value must be an integer multiple of four and
+ in the range 0-1020.
- 'strict'
- This parameter prevents mixed usage of multiple atomic models,
- even if they are compatible, and makes the compiler generate
- atomic sequences of the specified model only.
+ `strict'
+ This parameter prevents mixed usage of multiple atomic
+ models, even if they are compatible, and makes the compiler
+ generate atomic sequences of the specified model only.
-'-mtas'
- Generate the 'tas.b' opcode for '__atomic_test_and_set'. Notice
+
+`-mtas'
+ Generate the `tas.b' opcode for `__atomic_test_and_set'. Notice
that depending on the particular hardware and software
configuration this can degrade overall performance due to the
- operand cache line flushes that are implied by the 'tas.b'
- instruction. On multi-core SH4A processors the 'tas.b' instruction
- must be used with caution since it can result in data corruption
- for certain cache configurations.
+ operand cache line flushes that are implied by the `tas.b'
+ instruction. On multi-core SH4A processors the `tas.b'
+ instruction must be used with caution since it can result in data
+ corruption for certain cache configurations.
-'-mprefergot'
+`-mprefergot'
When generating position-independent code, emit function calls
using the Global Offset Table instead of the Procedure Linkage
Table.
-'-musermode'
-'-mno-usermode'
+`-musermode'
+`-mno-usermode'
Don't allow (allow) the compiler generating privileged mode code.
- Specifying '-musermode' also implies '-mno-inline-ic_invalidate' if
- the inlined code would not work in user mode. '-musermode' is the
- default when the target is 'sh*-*-linux*'. If the target is SH1*
- or SH2* '-musermode' has no effect, since there is no user mode.
+ Specifying `-musermode' also implies `-mno-inline-ic_invalidate'
+ if the inlined code would not work in user mode. `-musermode' is
+ the default when the target is `sh*-*-linux*'. If the target is
+ SH1* or SH2* `-musermode' has no effect, since there is no user
+ mode.
-'-multcost=NUMBER'
+`-multcost=NUMBER'
Set the cost to assume for a multiply insn.
-'-mdiv=STRATEGY'
+`-mdiv=STRATEGY'
Set the division strategy to be used for integer division
operations. For SHmedia STRATEGY can be one of:
- 'fp'
+ `fp'
Performs the operation in floating point. This has a very
high latency, but needs only a few instructions, so it might
be a good choice if your code has enough easily-exploitable
@@ -19034,38 +19155,38 @@ These '-m' options are defined for the SH implementations:
instructions together with other instructions. Division by
zero causes a floating-point exception.
- 'inv'
+ `inv'
Uses integer operations to calculate the inverse of the
divisor, and then multiplies the dividend with the inverse.
This strategy allows CSE and hoisting of the inverse
calculation. Division by zero calculates an unspecified
result, but does not trap.
- 'inv:minlat'
- A variant of 'inv' where, if no CSE or hoisting opportunities
+ `inv:minlat'
+ A variant of `inv' where, if no CSE or hoisting opportunities
have been found, or if the entire operation has been hoisted
to the same place, the last stages of the inverse calculation
are intertwined with the final multiply to reduce the overall
latency, at the expense of using a few more instructions, and
thus offering fewer scheduling opportunities with other code.
- 'call'
+ `call'
Calls a library function that usually implements the
- 'inv:minlat' strategy. This gives high code density for
- 'm5-*media-nofpu' compilations.
+ `inv:minlat' strategy. This gives high code density for
+ `m5-*media-nofpu' compilations.
- 'call2'
+ `call2'
Uses a different entry point of the same library function,
where it assumes that a pointer to a lookup table has already
been set up, which exposes the pointer load to CSE and code
hoisting optimizations.
- 'inv:call'
- 'inv:call2'
- 'inv:fp'
- Use the 'inv' algorithm for initial code generation, but if
- the code stays unoptimized, revert to the 'call', 'call2', or
- 'fp' strategies, respectively. Note that the
+ `inv:call'
+ `inv:call2'
+ `inv:fp'
+ Use the `inv' algorithm for initial code generation, but if
+ the code stays unoptimized, revert to the `call', `call2', or
+ `fp' strategies, respectively. Note that the
potentially-trapping side effect of division by zero is
carried by a separate instruction, so it is possible that all
the integer instructions are hoisted out, but the marker for
@@ -19073,65 +19194,68 @@ These '-m' options are defined for the SH implementations:
floating-point operations or a call is not possible in that
case.
- 'inv20u'
- 'inv20l'
- Variants of the 'inv:minlat' strategy. In the case that the
+ `inv20u'
+ `inv20l'
+ Variants of the `inv:minlat' strategy. In the case that the
inverse calculation is not separated from the multiply, they
speed up division where the dividend fits into 20 bits (plus
- sign where applicable) by inserting a test to skip a number of
- operations in this case; this test slows down the case of
- larger dividends. 'inv20u' assumes the case of a such a small
- dividend to be unlikely, and 'inv20l' assumes it to be likely.
+ sign where applicable) by inserting a test to skip a number
+ of operations in this case; this test slows down the case of
+ larger dividends. `inv20u' assumes the case of a such a
+ small dividend to be unlikely, and `inv20l' assumes it to be
+ likely.
+
For targets other than SHmedia STRATEGY can be one of:
- 'call-div1'
+ `call-div1'
Calls a library function that uses the single-step division
- instruction 'div1' to perform the operation. Division by zero
- calculates an unspecified result and does not trap. This is
- the default except for SH4, SH2A and SHcompact.
+ instruction `div1' to perform the operation. Division by
+ zero calculates an unspecified result and does not trap.
+ This is the default except for SH4, SH2A and SHcompact.
- 'call-fp'
- Calls a library function that performs the operation in double
- precision floating point. Division by zero causes a
+ `call-fp'
+ Calls a library function that performs the operation in
+ double precision floating point. Division by zero causes a
floating-point exception. This is the default for SHcompact
- with FPU. Specifying this for targets that do not have a
- double precision FPU defaults to 'call-div1'.
+ with FPU. Specifying this for targets that do not have a
+ double precision FPU defaults to `call-div1'.
- 'call-table'
+ `call-table'
Calls a library function that uses a lookup table for small
- divisors and the 'div1' instruction with case distinction for
+ divisors and the `div1' instruction with case distinction for
larger divisors. Division by zero calculates an unspecified
result and does not trap. This is the default for SH4.
Specifying this for targets that do not have dynamic shift
- instructions defaults to 'call-div1'.
+ instructions defaults to `call-div1'.
+
When a division strategy has not been specified the default
strategy is selected based on the current target. For SH2A the
- default strategy is to use the 'divs' and 'divu' instructions
+ default strategy is to use the `divs' and `divu' instructions
instead of library function calls.
-'-maccumulate-outgoing-args'
+`-maccumulate-outgoing-args'
Reserve space once for outgoing arguments in the function prologue
- rather than around each call. Generally beneficial for performance
- and size. Also needed for unwinding to avoid changing the stack
- frame around conditional code.
+ rather than around each call. Generally beneficial for
+ performance and size. Also needed for unwinding to avoid changing
+ the stack frame around conditional code.
-'-mdivsi3_libfunc=NAME'
+`-mdivsi3_libfunc=NAME'
Set the name of the library function used for 32-bit signed
- division to NAME. This only affects the name used in the 'call'
- and 'inv:call' division strategies, and the compiler still expects
- the same sets of input/output/clobbered registers as if this option
- were not present.
+ division to NAME. This only affects the name used in the `call'
+ and `inv:call' division strategies, and the compiler still expects
+ the same sets of input/output/clobbered registers as if this
+ option were not present.
-'-mfixed-range=REGISTER-RANGE'
+`-mfixed-range=REGISTER-RANGE'
Generate code treating the given register range as fixed registers.
A fixed register is one that the register allocator can not use.
This is useful when compiling kernel code. A register range is
specified as two registers separated by a dash. Multiple register
ranges can be specified separated by a comma.
-'-mindexed-addressing'
+`-mindexed-addressing'
Enable the use of the indexed addressing mode for
SHmedia32/SHcompact. This is only safe if the hardware and/or OS
implement 32-bit wrap-around semantics for the indexed addressing
@@ -19139,133 +19263,138 @@ These '-m' options are defined for the SH implementations:
with 64-bit MMU, which the OS could use to get 32-bit addressing,
but since no current hardware implementation supports this or any
other way to make the indexed addressing mode safe to use in the
- 32-bit ABI, the default is '-mno-indexed-addressing'.
+ 32-bit ABI, the default is `-mno-indexed-addressing'.
-'-mgettrcost=NUMBER'
- Set the cost assumed for the 'gettr' instruction to NUMBER. The
- default is 2 if '-mpt-fixed' is in effect, 100 otherwise.
+`-mgettrcost=NUMBER'
+ Set the cost assumed for the `gettr' instruction to NUMBER. The
+ default is 2 if `-mpt-fixed' is in effect, 100 otherwise.
-'-mpt-fixed'
- Assume 'pt*' instructions won't trap. This generally generates
+`-mpt-fixed'
+ Assume `pt*' instructions won't trap. This generally generates
better-scheduled code, but is unsafe on current hardware. The
- current architecture definition says that 'ptabs' and 'ptrel' trap
+ current architecture definition says that `ptabs' and `ptrel' trap
when the target anded with 3 is 3. This has the unintentional
effect of making it unsafe to schedule these instructions before a
branch, or hoist them out of a loop. For example,
- '__do_global_ctors', a part of 'libgcc' that runs constructors at
+ `__do_global_ctors', a part of `libgcc' that runs constructors at
program startup, calls functions in a list which is delimited by
- -1. With the '-mpt-fixed' option, the 'ptabs' is done before
- testing against -1. That means that all the constructors run a bit
- more quickly, but when the loop comes to the end of the list, the
- program crashes because 'ptabs' loads -1 into a target register.
+ -1. With the `-mpt-fixed' option, the `ptabs' is done before
+ testing against -1. That means that all the constructors run a
+ bit more quickly, but when the loop comes to the end of the list,
+ the program crashes because `ptabs' loads -1 into a target
+ register.
Since this option is unsafe for any hardware implementing the
- current architecture specification, the default is '-mno-pt-fixed'.
- Unless specified explicitly with '-mgettrcost', '-mno-pt-fixed'
- also implies '-mgettrcost=100'; this deters register allocation
- from using target registers for storing ordinary integers.
+ current architecture specification, the default is
+ `-mno-pt-fixed'. Unless specified explicitly with `-mgettrcost',
+ `-mno-pt-fixed' also implies `-mgettrcost=100'; this deters
+ register allocation from using target registers for storing
+ ordinary integers.
-'-minvalid-symbols'
+`-minvalid-symbols'
Assume symbols might be invalid. Ordinary function symbols
generated by the compiler are always valid to load with
- 'movi'/'shori'/'ptabs' or 'movi'/'shori'/'ptrel', but with
+ `movi'/`shori'/`ptabs' or `movi'/`shori'/`ptrel', but with
assembler and/or linker tricks it is possible to generate symbols
- that cause 'ptabs' or 'ptrel' to trap. This option is only
- meaningful when '-mno-pt-fixed' is in effect. It prevents
+ that cause `ptabs' or `ptrel' to trap. This option is only
+ meaningful when `-mno-pt-fixed' is in effect. It prevents
cross-basic-block CSE, hoisting and most scheduling of symbol
- loads. The default is '-mno-invalid-symbols'.
+ loads. The default is `-mno-invalid-symbols'.
-'-mbranch-cost=NUM'
+`-mbranch-cost=NUM'
Assume NUM to be the cost for a branch instruction. Higher numbers
make the compiler try to generate more branch-free code if
possible. If not specified the value is selected depending on the
processor type that is being compiled for.
-'-mzdcbranch'
-'-mno-zdcbranch'
+`-mzdcbranch'
+`-mno-zdcbranch'
Assume (do not assume) that zero displacement conditional branch
- instructions 'bt' and 'bf' are fast. If '-mzdcbranch' is
+ instructions `bt' and `bf' are fast. If `-mzdcbranch' is
specified, the compiler prefers zero displacement branch code
- sequences. This is enabled by default when generating code for SH4
- and SH4A. It can be explicitly disabled by specifying
- '-mno-zdcbranch'.
+ sequences. This is enabled by default when generating code for
+ SH4 and SH4A. It can be explicitly disabled by specifying
+ `-mno-zdcbranch'.
-'-mcbranch-force-delay-slot'
+`-mcbranch-force-delay-slot'
Force the usage of delay slots for conditional branches, which
- stuffs the delay slot with a 'nop' if a suitable instruction can't
+ stuffs the delay slot with a `nop' if a suitable instruction can't
be found. By default this option is disabled. It can be enabled
to work around hardware bugs as found in the original SH7055.
-'-mfused-madd'
-'-mno-fused-madd'
+`-mfused-madd'
+`-mno-fused-madd'
Generate code that uses (does not use) the floating-point multiply
and accumulate instructions. These instructions are generated by
default if hardware floating point is used. The machine-dependent
- '-mfused-madd' option is now mapped to the machine-independent
- '-ffp-contract=fast' option, and '-mno-fused-madd' is mapped to
- '-ffp-contract=off'.
-
-'-mfsca'
-'-mno-fsca'
- Allow or disallow the compiler to emit the 'fsca' instruction for
- sine and cosine approximations. The option '-mfsca' must be used
- in combination with '-funsafe-math-optimizations'. It is enabled
- by default when generating code for SH4A. Using '-mno-fsca'
+ `-mfused-madd' option is now mapped to the machine-independent
+ `-ffp-contract=fast' option, and `-mno-fused-madd' is mapped to
+ `-ffp-contract=off'.
+
+`-mfsca'
+`-mno-fsca'
+ Allow or disallow the compiler to emit the `fsca' instruction for
+ sine and cosine approximations. The option `-mfsca' must be used
+ in combination with `-funsafe-math-optimizations'. It is enabled
+ by default when generating code for SH4A. Using `-mno-fsca'
disables sine and cosine approximations even if
- '-funsafe-math-optimizations' is in effect.
-
-'-mfsrra'
-'-mno-fsrra'
- Allow or disallow the compiler to emit the 'fsrra' instruction for
- reciprocal square root approximations. The option '-mfsrra' must
- be used in combination with '-funsafe-math-optimizations' and
- '-ffinite-math-only'. It is enabled by default when generating
- code for SH4A. Using '-mno-fsrra' disables reciprocal square root
- approximations even if '-funsafe-math-optimizations' and
- '-ffinite-math-only' are in effect.
-
-'-mpretend-cmove'
+ `-funsafe-math-optimizations' is in effect.
+
+`-mfsrra'
+`-mno-fsrra'
+ Allow or disallow the compiler to emit the `fsrra' instruction for
+ reciprocal square root approximations. The option `-mfsrra' must
+ be used in combination with `-funsafe-math-optimizations' and
+ `-ffinite-math-only'. It is enabled by default when generating
+ code for SH4A. Using `-mno-fsrra' disables reciprocal square root
+ approximations even if `-funsafe-math-optimizations' and
+ `-ffinite-math-only' are in effect.
+
+`-mpretend-cmove'
Prefer zero-displacement conditional branches for conditional move
instruction patterns. This can result in faster code on the SH4
processor.
+

File: gcc.info, Node: Solaris 2 Options, Next: SPARC Options, Prev: SH Options, Up: Submodel Options
3.17.42 Solaris 2 Options
-------------------------
-These '-m' options are supported on Solaris 2:
+These `-m' options are supported on Solaris 2:
-'-mclear-hwcap'
- '-mclear-hwcap' tells the compiler to remove the hardware
+`-mclear-hwcap'
+ `-mclear-hwcap' tells the compiler to remove the hardware
capabilities generated by the Solaris assembler. This is only
- necessary when object files use ISA extensions not supported by the
- current machine, but check at runtime whether or not to use them.
+ necessary when object files use ISA extensions not supported by
+ the current machine, but check at runtime whether or not to use
+ them.
-'-mimpure-text'
- '-mimpure-text', used in addition to '-shared', tells the compiler
- to not pass '-z text' to the linker when linking a shared object.
+`-mimpure-text'
+ `-mimpure-text', used in addition to `-shared', tells the compiler
+ to not pass `-z text' to the linker when linking a shared object.
Using this option, you can link position-dependent code into a
shared object.
- '-mimpure-text' suppresses the "relocations remain against
+ `-mimpure-text' suppresses the "relocations remain against
allocatable but non-writable sections" linker error message.
However, the necessary relocations trigger copy-on-write, and the
shared object is not actually shared across processes. Instead of
- using '-mimpure-text', you should compile all source code with
- '-fpic' or '-fPIC'.
+ using `-mimpure-text', you should compile all source code with
+ `-fpic' or `-fPIC'.
+
These switches are supported in addition to the above on Solaris 2:
-'-pthreads'
+`-pthreads'
Add support for multithreading using the POSIX threads library.
This option sets flags for both the preprocessor and linker. This
- option does not affect the thread safety of object code produced by
- the compiler or that of libraries supplied with it.
+ option does not affect the thread safety of object code produced
+ by the compiler or that of libraries supplied with it.
-'-pthread'
- This is a synonym for '-pthreads'.
+`-pthread'
+ This is a synonym for `-pthreads'.

File: gcc.info, Node: SPARC Options, Next: SPU Options, Prev: Solaris 2 Options, Up: Submodel Options
@@ -19273,59 +19402,60 @@ File: gcc.info, Node: SPARC Options, Next: SPU Options, Prev: Solaris 2 Optio
3.17.43 SPARC Options
---------------------
-These '-m' options are supported on the SPARC:
+These `-m' options are supported on the SPARC:
-'-mno-app-regs'
-'-mapp-regs'
- Specify '-mapp-regs' to generate output using the global registers
+`-mno-app-regs'
+`-mapp-regs'
+ Specify `-mapp-regs' to generate output using the global registers
2 through 4, which the SPARC SVR4 ABI reserves for applications.
Like the global register 1, each global register 2 through 4 is
- then treated as an allocable register that is clobbered by function
- calls. This is the default.
+ then treated as an allocable register that is clobbered by
+ function calls. This is the default.
To be fully SVR4 ABI-compliant at the cost of some performance
- loss, specify '-mno-app-regs'. You should compile libraries and
+ loss, specify `-mno-app-regs'. You should compile libraries and
system software with this option.
-'-mflat'
-'-mno-flat'
- With '-mflat', the compiler does not generate save/restore
+`-mflat'
+`-mno-flat'
+ With `-mflat', the compiler does not generate save/restore
instructions and uses a "flat" or single register window model.
This model is compatible with the regular register window model.
- The local registers and the input registers (0-5) are still treated
- as "call-saved" registers and are saved on the stack as needed.
+ The local registers and the input registers (0-5) are still
+ treated as "call-saved" registers and are saved on the stack as
+ needed.
- With '-mno-flat' (the default), the compiler generates save/restore
+ With `-mno-flat' (the default), the compiler generates save/restore
instructions (except for leaf functions). This is the normal
operating mode.
-'-mfpu'
-'-mhard-float'
+`-mfpu'
+`-mhard-float'
Generate output containing floating-point instructions. This is
the default.
-'-mno-fpu'
-'-msoft-float'
+`-mno-fpu'
+`-msoft-float'
Generate output containing library calls for floating point.
*Warning:* the requisite libraries are not available for all SPARC
- targets. Normally the facilities of the machine's usual C compiler
- are used, but this cannot be done directly in cross-compilation.
- You must make your own arrangements to provide suitable library
- functions for cross-compilation. The embedded targets
- 'sparc-*-aout' and 'sparclite-*-*' do provide software
+ targets. Normally the facilities of the machine's usual C
+ compiler are used, but this cannot be done directly in
+ cross-compilation. You must make your own arrangements to provide
+ suitable library functions for cross-compilation. The embedded
+ targets `sparc-*-aout' and `sparclite-*-*' do provide software
floating-point support.
- '-msoft-float' changes the calling convention in the output file;
+ `-msoft-float' changes the calling convention in the output file;
therefore, it is only useful if you compile _all_ of a program with
- this option. In particular, you need to compile 'libgcc.a', the
- library that comes with GCC, with '-msoft-float' in order for this
+ this option. In particular, you need to compile `libgcc.a', the
+ library that comes with GCC, with `-msoft-float' in order for this
to work.
-'-mhard-quad-float'
+`-mhard-quad-float'
Generate output containing quad-word (long double) floating-point
instructions.
-'-msoft-quad-float'
+`-msoft-quad-float'
Generate output containing library calls for quad-word (long
double) floating-point instructions. The functions called are
those specified in the SPARC ABI. This is the default.
@@ -19335,14 +19465,14 @@ These '-m' options are supported on the SPARC:
They all invoke a trap handler for one of these instructions, and
then the trap handler emulates the effect of the instruction.
Because of the trap handler overhead, this is much slower than
- calling the ABI library routines. Thus the '-msoft-quad-float'
+ calling the ABI library routines. Thus the `-msoft-quad-float'
option is the default.
-'-mno-unaligned-doubles'
-'-munaligned-doubles'
+`-mno-unaligned-doubles'
+`-munaligned-doubles'
Assume that doubles have 8-byte alignment. This is the default.
- With '-munaligned-doubles', GCC assumes that doubles have 8-byte
+ With `-munaligned-doubles', GCC assumes that doubles have 8-byte
alignment only if they are contained in another type, or if they
have an absolute address. Otherwise, it assumes they have 4-byte
alignment. Specifying this option avoids some rare compatibility
@@ -19350,237 +19480,237 @@ These '-m' options are supported on the SPARC:
default because it results in a performance loss, especially for
floating-point code.
-'-muser-mode'
-'-mno-user-mode'
- Do not generate code that can only run in supervisor mode. This is
- relevant only for the 'casa' instruction emitted for the LEON3
- processor. The default is '-mno-user-mode'.
+`-muser-mode'
+`-mno-user-mode'
+ Do not generate code that can only run in supervisor mode. This
+ is relevant only for the `casa' instruction emitted for the LEON3
+ processor. The default is `-mno-user-mode'.
-'-mno-faster-structs'
-'-mfaster-structs'
- With '-mfaster-structs', the compiler assumes that structures
+`-mno-faster-structs'
+`-mfaster-structs'
+ With `-mfaster-structs', the compiler assumes that structures
should have 8-byte alignment. This enables the use of pairs of
- 'ldd' and 'std' instructions for copies in structure assignment, in
- place of twice as many 'ld' and 'st' pairs. However, the use of
- this changed alignment directly violates the SPARC ABI. Thus, it's
- intended only for use on targets where the developer acknowledges
- that their resulting code is not directly in line with the rules of
- the ABI.
-
-'-mcpu=CPU_TYPE'
+ `ldd' and `std' instructions for copies in structure assignment,
+ in place of twice as many `ld' and `st' pairs. However, the use
+ of this changed alignment directly violates the SPARC ABI. Thus,
+ it's intended only for use on targets where the developer
+ acknowledges that their resulting code is not directly in line with
+ the rules of the ABI.
+
+`-mcpu=CPU_TYPE'
Set the instruction set, register set, and instruction scheduling
parameters for machine type CPU_TYPE. Supported values for
- CPU_TYPE are 'v7', 'cypress', 'v8', 'supersparc', 'hypersparc',
- 'leon', 'leon3', 'leon3v7', 'sparclite', 'f930', 'f934',
- 'sparclite86x', 'sparclet', 'tsc701', 'v9', 'ultrasparc',
- 'ultrasparc3', 'niagara', 'niagara2', 'niagara3' and 'niagara4'.
+ CPU_TYPE are `v7', `cypress', `v8', `supersparc', `hypersparc',
+ `leon', `leon3', `leon3v7', `sparclite', `f930', `f934',
+ `sparclite86x', `sparclet', `tsc701', `v9', `ultrasparc',
+ `ultrasparc3', `niagara', `niagara2', `niagara3' and `niagara4'.
Native Solaris and GNU/Linux toolchains also support the value
- 'native', which selects the best architecture option for the host
- processor. '-mcpu=native' has no effect if GCC does not recognize
+ `native', which selects the best architecture option for the host
+ processor. `-mcpu=native' has no effect if GCC does not recognize
the processor.
Default instruction scheduling parameters are used for values that
- select an architecture and not an implementation. These are 'v7',
- 'v8', 'sparclite', 'sparclet', 'v9'.
+ select an architecture and not an implementation. These are `v7',
+ `v8', `sparclite', `sparclet', `v9'.
Here is a list of each supported architecture and their supported
implementations.
- v7
+ v7
cypress, leon3v7
- v8
+ v8
supersparc, hypersparc, leon, leon3
- sparclite
+ sparclite
f930, f934, sparclite86x
- sparclet
+ sparclet
tsc701
- v9
+ v9
ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4
By default (unless configured otherwise), GCC generates code for
- the V7 variant of the SPARC architecture. With '-mcpu=cypress',
+ the V7 variant of the SPARC architecture. With `-mcpu=cypress',
the compiler additionally optimizes it for the Cypress CY7C602
chip, as used in the SPARCStation/SPARCServer 3xx series. This is
also appropriate for the older SPARCStation 1, 2, IPX etc.
- With '-mcpu=v8', GCC generates code for the V8 variant of the SPARC
+ With `-mcpu=v8', GCC generates code for the V8 variant of the SPARC
architecture. The only difference from V7 code is that the
- compiler emits the integer multiply and integer divide instructions
- which exist in SPARC-V8 but not in SPARC-V7. With
- '-mcpu=supersparc', the compiler additionally optimizes it for the
+ compiler emits the integer multiply and integer divide
+ instructions which exist in SPARC-V8 but not in SPARC-V7. With
+ `-mcpu=supersparc', the compiler additionally optimizes it for the
SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000
series.
- With '-mcpu=sparclite', GCC generates code for the SPARClite
- variant of the SPARC architecture. This adds the integer multiply,
- integer divide step and scan ('ffs') instructions which exist in
- SPARClite but not in SPARC-V7. With '-mcpu=f930', the compiler
- additionally optimizes it for the Fujitsu MB86930 chip, which is
- the original SPARClite, with no FPU. With '-mcpu=f934', the
- compiler additionally optimizes it for the Fujitsu MB86934 chip,
- which is the more recent SPARClite with FPU.
+ With `-mcpu=sparclite', GCC generates code for the SPARClite
+ variant of the SPARC architecture. This adds the integer
+ multiply, integer divide step and scan (`ffs') instructions which
+ exist in SPARClite but not in SPARC-V7. With `-mcpu=f930', the
+ compiler additionally optimizes it for the Fujitsu MB86930 chip,
+ which is the original SPARClite, with no FPU. With `-mcpu=f934',
+ the compiler additionally optimizes it for the Fujitsu MB86934
+ chip, which is the more recent SPARClite with FPU.
- With '-mcpu=sparclet', GCC generates code for the SPARClet variant
+ With `-mcpu=sparclet', GCC generates code for the SPARClet variant
of the SPARC architecture. This adds the integer multiply,
- multiply/accumulate, integer divide step and scan ('ffs')
+ multiply/accumulate, integer divide step and scan (`ffs')
instructions which exist in SPARClet but not in SPARC-V7. With
- '-mcpu=tsc701', the compiler additionally optimizes it for the
+ `-mcpu=tsc701', the compiler additionally optimizes it for the
TEMIC SPARClet chip.
- With '-mcpu=v9', GCC generates code for the V9 variant of the SPARC
+ With `-mcpu=v9', GCC generates code for the V9 variant of the SPARC
architecture. This adds 64-bit integer and floating-point move
instructions, 3 additional floating-point condition code registers
- and conditional move instructions. With '-mcpu=ultrasparc', the
+ and conditional move instructions. With `-mcpu=ultrasparc', the
compiler additionally optimizes it for the Sun UltraSPARC I/II/IIi
- chips. With '-mcpu=ultrasparc3', the compiler additionally
+ chips. With `-mcpu=ultrasparc3', the compiler additionally
optimizes it for the Sun UltraSPARC III/III+/IIIi/IIIi+/IV/IV+
- chips. With '-mcpu=niagara', the compiler additionally optimizes
- it for Sun UltraSPARC T1 chips. With '-mcpu=niagara2', the
+ chips. With `-mcpu=niagara', the compiler additionally optimizes
+ it for Sun UltraSPARC T1 chips. With `-mcpu=niagara2', the
compiler additionally optimizes it for Sun UltraSPARC T2 chips.
- With '-mcpu=niagara3', the compiler additionally optimizes it for
- Sun UltraSPARC T3 chips. With '-mcpu=niagara4', the compiler
+ With `-mcpu=niagara3', the compiler additionally optimizes it for
+ Sun UltraSPARC T3 chips. With `-mcpu=niagara4', the compiler
additionally optimizes it for Sun UltraSPARC T4 chips.
-'-mtune=CPU_TYPE'
+`-mtune=CPU_TYPE'
Set the instruction scheduling parameters for machine type
CPU_TYPE, but do not set the instruction set or register set that
- the option '-mcpu=CPU_TYPE' does.
-
- The same values for '-mcpu=CPU_TYPE' can be used for
- '-mtune=CPU_TYPE', but the only useful values are those that select
- a particular CPU implementation. Those are 'cypress',
- 'supersparc', 'hypersparc', 'leon', 'leon3', 'leon3v7', 'f930',
- 'f934', 'sparclite86x', 'tsc701', 'ultrasparc', 'ultrasparc3',
- 'niagara', 'niagara2', 'niagara3' and 'niagara4'. With native
- Solaris and GNU/Linux toolchains, 'native' can also be used.
-
-'-mv8plus'
-'-mno-v8plus'
- With '-mv8plus', GCC generates code for the SPARC-V8+ ABI. The
+ the option `-mcpu=CPU_TYPE' does.
+
+ The same values for `-mcpu=CPU_TYPE' can be used for
+ `-mtune=CPU_TYPE', but the only useful values are those that
+ select a particular CPU implementation. Those are `cypress',
+ `supersparc', `hypersparc', `leon', `leon3', `leon3v7', `f930',
+ `f934', `sparclite86x', `tsc701', `ultrasparc', `ultrasparc3',
+ `niagara', `niagara2', `niagara3' and `niagara4'. With native
+ Solaris and GNU/Linux toolchains, `native' can also be used.
+
+`-mv8plus'
+`-mno-v8plus'
+ With `-mv8plus', GCC generates code for the SPARC-V8+ ABI. The
difference from the V8 ABI is that the global and out registers are
considered 64 bits wide. This is enabled by default on Solaris in
32-bit mode for all SPARC-V9 processors.
-'-mvis'
-'-mno-vis'
- With '-mvis', GCC generates code that takes advantage of the
+`-mvis'
+`-mno-vis'
+ With `-mvis', GCC generates code that takes advantage of the
UltraSPARC Visual Instruction Set extensions. The default is
- '-mno-vis'.
+ `-mno-vis'.
-'-mvis2'
-'-mno-vis2'
- With '-mvis2', GCC generates code that takes advantage of version
+`-mvis2'
+`-mno-vis2'
+ With `-mvis2', GCC generates code that takes advantage of version
2.0 of the UltraSPARC Visual Instruction Set extensions. The
- default is '-mvis2' when targeting a cpu that supports such
- instructions, such as UltraSPARC-III and later. Setting '-mvis2'
- also sets '-mvis'.
+ default is `-mvis2' when targeting a cpu that supports such
+ instructions, such as UltraSPARC-III and later. Setting `-mvis2'
+ also sets `-mvis'.
-'-mvis3'
-'-mno-vis3'
- With '-mvis3', GCC generates code that takes advantage of version
+`-mvis3'
+`-mno-vis3'
+ With `-mvis3', GCC generates code that takes advantage of version
3.0 of the UltraSPARC Visual Instruction Set extensions. The
- default is '-mvis3' when targeting a cpu that supports such
- instructions, such as niagara-3 and later. Setting '-mvis3' also
- sets '-mvis2' and '-mvis'.
+ default is `-mvis3' when targeting a cpu that supports such
+ instructions, such as niagara-3 and later. Setting `-mvis3' also
+ sets `-mvis2' and `-mvis'.
-'-mcbcond'
-'-mno-cbcond'
- With '-mcbcond', GCC generates code that takes advantage of
+`-mcbcond'
+`-mno-cbcond'
+ With `-mcbcond', GCC generates code that takes advantage of
compare-and-branch instructions, as defined in the Sparc
- Architecture 2011. The default is '-mcbcond' when targeting a cpu
+ Architecture 2011. The default is `-mcbcond' when targeting a cpu
that supports such instructions, such as niagara-4 and later.
-'-mpopc'
-'-mno-popc'
- With '-mpopc', GCC generates code that takes advantage of the
- UltraSPARC population count instruction. The default is '-mpopc'
+`-mpopc'
+`-mno-popc'
+ With `-mpopc', GCC generates code that takes advantage of the
+ UltraSPARC population count instruction. The default is `-mpopc'
when targeting a cpu that supports such instructions, such as
Niagara-2 and later.
-'-mfmaf'
-'-mno-fmaf'
- With '-mfmaf', GCC generates code that takes advantage of the
+`-mfmaf'
+`-mno-fmaf'
+ With `-mfmaf', GCC generates code that takes advantage of the
UltraSPARC Fused Multiply-Add Floating-point extensions. The
- default is '-mfmaf' when targeting a cpu that supports such
+ default is `-mfmaf' when targeting a cpu that supports such
instructions, such as Niagara-3 and later.
-'-mfix-at697f'
+`-mfix-at697f'
Enable the documented workaround for the single erratum of the
Atmel AT697F processor (which corresponds to erratum #13 of the
AT697E processor).
-'-mfix-ut699'
- Enable the documented workarounds for the floating-point errata and
- the data cache nullify errata of the UT699 processor.
+`-mfix-ut699'
+ Enable the documented workarounds for the floating-point errata
+ and the data cache nullify errata of the UT699 processor.
- These '-m' options are supported in addition to the above on SPARC-V9
+ These `-m' options are supported in addition to the above on SPARC-V9
processors in 64-bit environments:
-'-m32'
-'-m64'
+`-m32'
+`-m64'
Generate code for a 32-bit or 64-bit environment. The 32-bit
environment sets int, long and pointer to 32 bits. The 64-bit
environment sets int to 32 bits and long and pointer to 64 bits.
-'-mcmodel=WHICH'
+`-mcmodel=WHICH'
Set the code model to one of
- 'medlow'
+ `medlow'
The Medium/Low code model: 64-bit addresses, programs must be
linked in the low 32 bits of memory. Programs can be
statically or dynamically linked.
- 'medmid'
+ `medmid'
The Medium/Middle code model: 64-bit addresses, programs must
be linked in the low 44 bits of memory, the text and data
segments must be less than 2GB in size and the data segment
must be located within 2GB of the text segment.
- 'medany'
- The Medium/Anywhere code model: 64-bit addresses, programs may
- be linked anywhere in memory, the text and data segments must
- be less than 2GB in size and the data segment must be located
- within 2GB of the text segment.
+ `medany'
+ The Medium/Anywhere code model: 64-bit addresses, programs
+ may be linked anywhere in memory, the text and data segments
+ must be less than 2GB in size and the data segment must be
+ located within 2GB of the text segment.
- 'embmedany'
+ `embmedany'
The Medium/Anywhere code model for embedded systems: 64-bit
addresses, the text and data segments must be less than 2GB in
size, both starting anywhere in memory (determined at link
- time). The global register %g4 points to the base of the data
- segment. Programs are statically linked and PIC is not
+ time). The global register %g4 points to the base of the
+ data segment. Programs are statically linked and PIC is not
supported.
-'-mmemory-model=MEM-MODEL'
+`-mmemory-model=MEM-MODEL'
Set the memory model in force on the processor to one of
- 'default'
+ `default'
The default memory model for the processor and operating
system.
- 'rmo'
+ `rmo'
Relaxed Memory Order
- 'pso'
+ `pso'
Partial Store Order
- 'tso'
+ `tso'
Total Store Order
- 'sc'
+ `sc'
Sequential Consistency
- These memory models are formally defined in Appendix D of the Sparc
- V9 architecture manual, as set in the processor's 'PSTATE.MM'
- field.
+ These memory models are formally defined in Appendix D of the
+ Sparc V9 architecture manual, as set in the processor's
+ `PSTATE.MM' field.
-'-mstack-bias'
-'-mno-stack-bias'
- With '-mstack-bias', GCC assumes that the stack pointer, and frame
+`-mstack-bias'
+`-mno-stack-bias'
+ With `-mstack-bias', GCC assumes that the stack pointer, and frame
pointer if present, are offset by -2047 which must be added back
when making stack frame references. This is the default in 64-bit
mode. Otherwise, assume no such offset is present.
@@ -19591,116 +19721,112 @@ File: gcc.info, Node: SPU Options, Next: System V Options, Prev: SPARC Option
3.17.44 SPU Options
-------------------
-These '-m' options are supported on the SPU:
-
-'-mwarn-reloc'
-'-merror-reloc'
+These `-m' options are supported on the SPU:
+`-mwarn-reloc'
+`-merror-reloc'
The loader for SPU does not handle dynamic relocations. By
default, GCC gives an error when it generates code that requires a
- dynamic relocation. '-mno-error-reloc' disables the error,
- '-mwarn-reloc' generates a warning instead.
-
-'-msafe-dma'
-'-munsafe-dma'
+ dynamic relocation. `-mno-error-reloc' disables the error,
+ `-mwarn-reloc' generates a warning instead.
+`-msafe-dma'
+`-munsafe-dma'
Instructions that initiate or test completion of DMA must not be
reordered with respect to loads and stores of the memory that is
- being accessed. With '-munsafe-dma' you must use the 'volatile'
+ being accessed. With `-munsafe-dma' you must use the `volatile'
keyword to protect memory accesses, but that can lead to
- inefficient code in places where the memory is known to not change.
- Rather than mark the memory as volatile, you can use '-msafe-dma'
- to tell the compiler to treat the DMA instructions as potentially
- affecting all memory.
-
-'-mbranch-hints'
+ inefficient code in places where the memory is known to not
+ change. Rather than mark the memory as volatile, you can use
+ `-msafe-dma' to tell the compiler to treat the DMA instructions as
+ potentially affecting all memory.
+`-mbranch-hints'
By default, GCC generates a branch hint instruction to avoid
pipeline stalls for always-taken or probably-taken branches. A
hint is not generated closer than 8 instructions away from its
branch. There is little reason to disable them, except for
debugging purposes, or to make an object a little bit smaller.
-'-msmall-mem'
-'-mlarge-mem'
-
+`-msmall-mem'
+`-mlarge-mem'
By default, GCC generates code assuming that addresses are never
- larger than 18 bits. With '-mlarge-mem' code is generated that
+ larger than 18 bits. With `-mlarge-mem' code is generated that
assumes a full 32-bit address.
-'-mstdmain'
-
+`-mstdmain'
By default, GCC links against startup code that assumes the
SPU-style main function interface (which has an unconventional
- parameter list). With '-mstdmain', GCC links your program against
- startup code that assumes a C99-style interface to 'main',
- including a local copy of 'argv' strings.
+ parameter list). With `-mstdmain', GCC links your program against
+ startup code that assumes a C99-style interface to `main',
+ including a local copy of `argv' strings.
-'-mfixed-range=REGISTER-RANGE'
+`-mfixed-range=REGISTER-RANGE'
Generate code treating the given register range as fixed registers.
A fixed register is one that the register allocator cannot use.
This is useful when compiling kernel code. A register range is
specified as two registers separated by a dash. Multiple register
ranges can be specified separated by a comma.
-'-mea32'
-'-mea64'
+`-mea32'
+`-mea64'
Compile code assuming that pointers to the PPU address space
- accessed via the '__ea' named address space qualifier are either 32
- or 64 bits wide. The default is 32 bits. As this is an
+ accessed via the `__ea' named address space qualifier are either
+ 32 or 64 bits wide. The default is 32 bits. As this is an
ABI-changing option, all object code in an executable must be
compiled with the same setting.
-'-maddress-space-conversion'
-'-mno-address-space-conversion'
- Allow/disallow treating the '__ea' address space as superset of the
- generic address space. This enables explicit type casts between
- '__ea' and generic pointer as well as implicit conversions of
- generic pointers to '__ea' pointers. The default is to allow
+`-maddress-space-conversion'
+`-mno-address-space-conversion'
+ Allow/disallow treating the `__ea' address space as superset of
+ the generic address space. This enables explicit type casts
+ between `__ea' and generic pointer as well as implicit conversions
+ of generic pointers to `__ea' pointers. The default is to allow
address space pointer conversions.
-'-mcache-size=CACHE-SIZE'
+`-mcache-size=CACHE-SIZE'
This option controls the version of libgcc that the compiler links
- to an executable and selects a software-managed cache for accessing
- variables in the '__ea' address space with a particular cache size.
- Possible options for CACHE-SIZE are '8', '16', '32', '64' and
- '128'. The default cache size is 64KB.
+ to an executable and selects a software-managed cache for
+ accessing variables in the `__ea' address space with a particular
+ cache size. Possible options for CACHE-SIZE are `8', `16', `32',
+ `64' and `128'. The default cache size is 64KB.
-'-matomic-updates'
-'-mno-atomic-updates'
+`-matomic-updates'
+`-mno-atomic-updates'
This option controls the version of libgcc that the compiler links
to an executable and selects whether atomic updates to the
software-managed cache of PPU-side variables are used. If you use
atomic updates, changes to a PPU variable from SPU code using the
- '__ea' named address space qualifier do not interfere with changes
+ `__ea' named address space qualifier do not interfere with changes
to other PPU variables residing in the same cache line from PPU
code. If you do not use atomic updates, such interference may
occur; however, writing back cache lines is more efficient. The
default behavior is to use atomic updates.
-'-mdual-nops'
-'-mdual-nops=N'
+`-mdual-nops'
+`-mdual-nops=N'
By default, GCC inserts nops to increase dual issue when it expects
it to increase performance. N can be a value from 0 to 10. A
smaller N inserts fewer nops. 10 is the default, 0 is the same as
- '-mno-dual-nops'. Disabled with '-Os'.
+ `-mno-dual-nops'. Disabled with `-Os'.
-'-mhint-max-nops=N'
+`-mhint-max-nops=N'
Maximum number of nops to insert for a branch hint. A branch hint
must be at least 8 instructions away from the branch it is
affecting. GCC inserts up to N nops to enforce this, otherwise it
does not generate the branch hint.
-'-mhint-max-distance=N'
+`-mhint-max-distance=N'
The encoding of the branch hint instruction limits the hint to be
- within 256 instructions of the branch it is affecting. By default,
- GCC makes sure it is within 125.
+ within 256 instructions of the branch it is affecting. By
+ default, GCC makes sure it is within 125.
-'-msafe-hints'
+`-msafe-hints'
Work around a hardware bug that causes the SPU to stall
- indefinitely. By default, GCC inserts the 'hbrp' instruction to
+ indefinitely. By default, GCC inserts the `hbrp' instruction to
make sure this stall won't happen.
+

File: gcc.info, Node: System V Options, Next: TILE-Gx Options, Prev: SPU Options, Up: Submodel Options
@@ -19710,23 +19836,23 @@ File: gcc.info, Node: System V Options, Next: TILE-Gx Options, Prev: SPU Opti
These additional options are available on System V Release 4 for
compatibility with other compilers on those systems:
-'-G'
- Create a shared object. It is recommended that '-symbolic' or
- '-shared' be used instead.
+`-G'
+ Create a shared object. It is recommended that `-symbolic' or
+ `-shared' be used instead.
-'-Qy'
+`-Qy'
Identify the versions of each tool used by the compiler, in a
- '.ident' assembler directive in the output.
+ `.ident' assembler directive in the output.
-'-Qn'
- Refrain from adding '.ident' directives to the output file (this is
+`-Qn'
+ Refrain from adding `.ident' directives to the output file (this is
the default).
-'-YP,DIRS'
- Search the directories DIRS, and no others, for libraries specified
- with '-l'.
+`-YP,DIRS'
+ Search the directories DIRS, and no others, for libraries
+ specified with `-l'.
-'-Ym,DIR'
+`-Ym,DIR'
Look in the directory DIR to find the M4 preprocessor. The
assembler uses this option.
@@ -19736,29 +19862,29 @@ File: gcc.info, Node: TILE-Gx Options, Next: TILEPro Options, Prev: System V
3.17.46 TILE-Gx Options
-----------------------
-These '-m' options are supported on the TILE-Gx:
+These `-m' options are supported on the TILE-Gx:
-'-mcmodel=small'
+`-mcmodel=small'
Generate code for the small model. The distance for direct calls
is limited to 500M in either direction. PC-relative addresses are
32 bits. Absolute addresses support the full address range.
-'-mcmodel=large'
+`-mcmodel=large'
Generate code for the large model. There is no limitation on call
distance, pc-relative addresses, or absolute addresses.
-'-mcpu=NAME'
+`-mcpu=NAME'
Selects the type of CPU to be targeted. Currently the only
- supported type is 'tilegx'.
+ supported type is `tilegx'.
-'-m32'
-'-m64'
+`-m32'
+`-m64'
Generate code for a 32-bit or 64-bit environment. The 32-bit
environment sets int, long, and pointer to 32 bits. The 64-bit
environment sets int to 32 bits and long and pointer to 64 bits.
-'-mbig-endian'
-'-mlittle-endian'
+`-mbig-endian'
+`-mlittle-endian'
Generate code in big/little endian mode, respectively.

@@ -19767,13 +19893,13 @@ File: gcc.info, Node: TILEPro Options, Next: V850 Options, Prev: TILE-Gx Opti
3.17.47 TILEPro Options
-----------------------
-These '-m' options are supported on the TILEPro:
+These `-m' options are supported on the TILEPro:
-'-mcpu=NAME'
+`-mcpu=NAME'
Selects the type of CPU to be targeted. Currently the only
- supported type is 'tilepro'.
+ supported type is `tilepro'.
-'-m32'
+`-m32'
Generate code for a 32-bit environment, which sets int, long, and
pointer to 32 bits. This is the only supported behavior so the
flag is essentially ignored.
@@ -19784,128 +19910,128 @@ File: gcc.info, Node: V850 Options, Next: VAX Options, Prev: TILEPro Options,
3.17.48 V850 Options
--------------------
-These '-m' options are defined for V850 implementations:
+These `-m' options are defined for V850 implementations:
-'-mlong-calls'
-'-mno-long-calls'
+`-mlong-calls'
+`-mno-long-calls'
Treat all calls as being far away (near). If calls are assumed to
be far away, the compiler always loads the function's address into
a register, and calls indirect through the pointer.
-'-mno-ep'
-'-mep'
+`-mno-ep'
+`-mep'
Do not optimize (do optimize) basic blocks that use the same index
- pointer 4 or more times to copy pointer into the 'ep' register, and
- use the shorter 'sld' and 'sst' instructions. The '-mep' option is
- on by default if you optimize.
+ pointer 4 or more times to copy pointer into the `ep' register, and
+ use the shorter `sld' and `sst' instructions. The `-mep' option
+ is on by default if you optimize.
-'-mno-prolog-function'
-'-mprolog-function'
+`-mno-prolog-function'
+`-mprolog-function'
Do not use (do use) external functions to save and restore
- registers at the prologue and epilogue of a function. The external
- functions are slower, but use less code space if more than one
- function saves the same number of registers. The
- '-mprolog-function' option is on by default if you optimize.
+ registers at the prologue and epilogue of a function. The
+ external functions are slower, but use less code space if more
+ than one function saves the same number of registers. The
+ `-mprolog-function' option is on by default if you optimize.
-'-mspace'
+`-mspace'
Try to make the code as small as possible. At present, this just
- turns on the '-mep' and '-mprolog-function' options.
+ turns on the `-mep' and `-mprolog-function' options.
-'-mtda=N'
+`-mtda=N'
Put static or global variables whose size is N bytes or less into
- the tiny data area that register 'ep' points to. The tiny data
+ the tiny data area that register `ep' points to. The tiny data
area can hold up to 256 bytes in total (128 bytes for byte
references).
-'-msda=N'
+`-msda=N'
Put static or global variables whose size is N bytes or less into
- the small data area that register 'gp' points to. The small data
+ the small data area that register `gp' points to. The small data
area can hold up to 64 kilobytes.
-'-mzda=N'
+`-mzda=N'
Put static or global variables whose size is N bytes or less into
the first 32 kilobytes of memory.
-'-mv850'
+`-mv850'
Specify that the target processor is the V850.
-'-mv850e3v5'
+`-mv850e3v5'
Specify that the target processor is the V850E3V5. The
- preprocessor constant '__v850e3v5__' is defined if this option is
+ preprocessor constant `__v850e3v5__' is defined if this option is
used.
-'-mv850e2v4'
+`-mv850e2v4'
Specify that the target processor is the V850E3V5. This is an
- alias for the '-mv850e3v5' option.
+ alias for the `-mv850e3v5' option.
-'-mv850e2v3'
+`-mv850e2v3'
Specify that the target processor is the V850E2V3. The
- preprocessor constant '__v850e2v3__' is defined if this option is
+ preprocessor constant `__v850e2v3__' is defined if this option is
used.
-'-mv850e2'
+`-mv850e2'
Specify that the target processor is the V850E2. The preprocessor
- constant '__v850e2__' is defined if this option is used.
+ constant `__v850e2__' is defined if this option is used.
-'-mv850e1'
+`-mv850e1'
Specify that the target processor is the V850E1. The preprocessor
- constants '__v850e1__' and '__v850e__' are defined if this option
+ constants `__v850e1__' and `__v850e__' are defined if this option
is used.
-'-mv850es'
- Specify that the target processor is the V850ES. This is an alias
- for the '-mv850e1' option.
+`-mv850es'
+ Specify that the target processor is the V850ES. This is an alias
+ for the `-mv850e1' option.
-'-mv850e'
+`-mv850e'
Specify that the target processor is the V850E. The preprocessor
- constant '__v850e__' is defined if this option is used.
+ constant `__v850e__' is defined if this option is used.
- If neither '-mv850' nor '-mv850e' nor '-mv850e1' nor '-mv850e2' nor
- '-mv850e2v3' nor '-mv850e3v5' are defined then a default target
- processor is chosen and the relevant '__v850*__' preprocessor
- constant is defined.
+ If neither `-mv850' nor `-mv850e' nor `-mv850e1' nor `-mv850e2'
+ nor `-mv850e2v3' nor `-mv850e3v5' are defined then a default
+ target processor is chosen and the relevant `__v850*__'
+ preprocessor constant is defined.
- The preprocessor constants '__v850' and '__v851__' are always
+ The preprocessor constants `__v850' and `__v851__' are always
defined, regardless of which processor variant is the target.
-'-mdisable-callt'
-'-mno-disable-callt'
- This option suppresses generation of the 'CALLT' instruction for
+`-mdisable-callt'
+`-mno-disable-callt'
+ This option suppresses generation of the `CALLT' instruction for
the v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the
v850 architecture.
- This option is enabled by default when the RH850 ABI is in use (see
- '-mrh850-abi'), and disabled by default when the GCC ABI is in use.
- If 'CALLT' instructions are being generated then the C preprocessor
- symbol '__V850_CALLT__' is defined.
+ This option is enabled by default when the RH850 ABI is in use
+ (see `-mrh850-abi'), and disabled by default when the GCC ABI is
+ in use. If `CALLT' instructions are being generated then the C
+ preprocessor symbol `__V850_CALLT__' is defined.
-'-mrelax'
-'-mno-relax'
- Pass on (or do not pass on) the '-mrelax' command-line option to
+`-mrelax'
+`-mno-relax'
+ Pass on (or do not pass on) the `-mrelax' command-line option to
the assembler.
-'-mlong-jumps'
-'-mno-long-jumps'
+`-mlong-jumps'
+`-mno-long-jumps'
Disable (or re-enable) the generation of PC-relative jump
instructions.
-'-msoft-float'
-'-mhard-float'
+`-msoft-float'
+`-mhard-float'
Disable (or re-enable) the generation of hardware floating point
instructions. This option is only significant when the target
- architecture is 'V850E2V3' or higher. If hardware floating point
+ architecture is `V850E2V3' or higher. If hardware floating point
instructions are being generated then the C preprocessor symbol
- '__FPU_OK__' is defined, otherwise the symbol '__NO_FPU__' is
+ `__FPU_OK__' is defined, otherwise the symbol `__NO_FPU__' is
defined.
-'-mloop'
+`-mloop'
Enables the use of the e3v5 LOOP instruction. The use of this
instruction is not enabled by default when the e3v5 architecture is
selected because its use is still experimental.
-'-mrh850-abi'
-'-mghs'
- Enables support for the RH850 version of the V850 ABI. This is the
+`-mrh850-abi'
+`-mghs'
+ Enables support for the RH850 version of the V850 ABI. This is the
default. With this version of the ABI the following rules apply:
* Integer sized structures and unions are returned via a memory
@@ -19916,21 +20042,21 @@ These '-m' options are defined for V850 implementations:
* Functions are aligned to 16-bit boundaries.
- * The '-m8byte-align' command-line option is supported.
+ * The `-m8byte-align' command-line option is supported.
- * The '-mdisable-callt' command-line option is enabled by
- default. The '-mno-disable-callt' command-line option is not
+ * The `-mdisable-callt' command-line option is enabled by
+ default. The `-mno-disable-callt' command-line option is not
supported.
When this version of the ABI is enabled the C preprocessor symbol
- '__V850_RH850_ABI__' is defined.
+ `__V850_RH850_ABI__' is defined.
-'-mgcc-abi'
- Enables support for the old GCC version of the V850 ABI. With this
+`-mgcc-abi'
+ Enables support for the old GCC version of the V850 ABI. With this
version of the ABI the following rules apply:
* Integer sized structures and unions are returned in register
- 'r10'.
+ `r10'.
* Large structures and unions (more than 8 bytes in size) are
passed by reference.
@@ -19938,50 +20064,51 @@ These '-m' options are defined for V850 implementations:
* Functions are aligned to 32-bit boundaries, unless optimizing
for size.
- * The '-m8byte-align' command-line option is not supported.
+ * The `-m8byte-align' command-line option is not supported.
- * The '-mdisable-callt' command-line option is supported but not
+ * The `-mdisable-callt' command-line option is supported but not
enabled by default.
When this version of the ABI is enabled the C preprocessor symbol
- '__V850_GCC_ABI__' is defined.
+ `__V850_GCC_ABI__' is defined.
-'-m8byte-align'
-'-mno-8byte-align'
- Enables support for 'double' and 'long long' types to be aligned on
- 8-byte boundaries. The default is to restrict the alignment of all
- objects to at most 4-bytes. When '-m8byte-align' is in effect the
- C preprocessor symbol '__V850_8BYTE_ALIGN__' is defined.
+`-m8byte-align'
+`-mno-8byte-align'
+ Enables support for `double' and `long long' types to be aligned
+ on 8-byte boundaries. The default is to restrict the alignment of
+ all objects to at most 4-bytes. When `-m8byte-align' is in effect
+ the C preprocessor symbol `__V850_8BYTE_ALIGN__' is defined.
-'-mbig-switch'
- Generate code suitable for big switch tables. Use this option only
- if the assembler/linker complain about out of range branches within
- a switch table.
+`-mbig-switch'
+ Generate code suitable for big switch tables. Use this option
+ only if the assembler/linker complain about out of range branches
+ within a switch table.
-'-mapp-regs'
+`-mapp-regs'
This option causes r2 and r5 to be used in the code generated by
the compiler. This setting is the default.
-'-mno-app-regs'
+`-mno-app-regs'
This option causes r2 and r5 to be treated as fixed registers.
+

File: gcc.info, Node: VAX Options, Next: Visium Options, Prev: V850 Options, Up: Submodel Options
3.17.49 VAX Options
-------------------
-These '-m' options are defined for the VAX:
+These `-m' options are defined for the VAX:
-'-munix'
- Do not output certain jump instructions ('aobleq' and so on) that
+`-munix'
+ Do not output certain jump instructions (`aobleq' and so on) that
the Unix assembler for the VAX cannot handle across long ranges.
-'-mgnu'
+`-mgnu'
Do output those jump instructions, on the assumption that the GNU
assembler is being used.
-'-mg'
+`-mg'
Output code for G-format floating-point numbers instead of
D-format.
@@ -19991,57 +20118,57 @@ File: gcc.info, Node: Visium Options, Next: VMS Options, Prev: VAX Options,
3.17.50 Visium Options
----------------------
-'-mdebug'
+`-mdebug'
A program which performs file I/O and is destined to run on an MCM
target should be linked with this option. It causes the libraries
libc.a and libdebug.a to be linked. The program should be run on
the target under the control of the GDB remote debugging stub.
-'-msim'
+`-msim'
A program which performs file I/O and is destined to run on the
simulator should be linked with option. This causes libraries
libc.a and libsim.a to be linked.
-'-mfpu'
-'-mhard-float'
+`-mfpu'
+`-mhard-float'
Generate code containing floating-point instructions. This is the
default.
-'-mno-fpu'
-'-msoft-float'
+`-mno-fpu'
+`-msoft-float'
Generate code containing library calls for floating-point.
- '-msoft-float' changes the calling convention in the output file;
+ `-msoft-float' changes the calling convention in the output file;
therefore, it is only useful if you compile _all_ of a program with
- this option. In particular, you need to compile 'libgcc.a', the
- library that comes with GCC, with '-msoft-float' in order for this
+ this option. In particular, you need to compile `libgcc.a', the
+ library that comes with GCC, with `-msoft-float' in order for this
to work.
-'-mcpu=CPU_TYPE'
+`-mcpu=CPU_TYPE'
Set the instruction set, register set, and instruction scheduling
parameters for machine type CPU_TYPE. Supported values for
- CPU_TYPE are 'mcm', 'gr5' and 'gr6'.
+ CPU_TYPE are `mcm', `gr5' and `gr6'.
- 'mcm' is a synonym of 'gr5' present for backward compatibility.
+ `mcm' is a synonym of `gr5' present for backward compatibility.
By default (unless configured otherwise), GCC generates code for
the GR5 variant of the Visium architecture.
- With '-mcpu=gr6', GCC generates code for the GR6 variant of the
- Visium architecture. The only difference from GR5 code is that the
- compiler will generate block move instructions.
+ With `-mcpu=gr6', GCC generates code for the GR6 variant of the
+ Visium architecture. The only difference from GR5 code is that
+ the compiler will generate block move instructions.
-'-mtune=CPU_TYPE'
+`-mtune=CPU_TYPE'
Set the instruction scheduling parameters for machine type
CPU_TYPE, but do not set the instruction set or register set that
- the option '-mcpu=CPU_TYPE' would.
+ the option `-mcpu=CPU_TYPE' would.
-'-msv-mode'
+`-msv-mode'
Generate code for the supervisor mode, where there are no
restrictions on the access to general registers. This is the
default.
-'-muser-mode'
+`-muser-mode'
Generate code for the user mode, where the access to some general
registers is forbidden: on the GR5, registers r24 to r31 cannot be
accessed in this mode; on the GR6, only registers r29 to r31 are
@@ -20053,24 +20180,24 @@ File: gcc.info, Node: VMS Options, Next: VxWorks Options, Prev: Visium Option
3.17.51 VMS Options
-------------------
-These '-m' options are defined for the VMS implementations:
+These `-m' options are defined for the VMS implementations:
-'-mvms-return-codes'
- Return VMS condition codes from 'main'. The default is to return
+`-mvms-return-codes'
+ Return VMS condition codes from `main'. The default is to return
POSIX-style condition (e.g. error) codes.
-'-mdebug-main=PREFIX'
+`-mdebug-main=PREFIX'
Flag the first routine whose name starts with PREFIX as the main
routine for the debugger.
-'-mmalloc64'
+`-mmalloc64'
Default to 64-bit memory allocation routines.
-'-mpointer-size=SIZE'
- Set the default size of pointers. Possible options for SIZE are
- '32' or 'short' for 32 bit pointers, '64' or 'long' for 64 bit
- pointers, and 'no' for supporting only 32 bit pointers. The later
- option disables 'pragma pointer_size'.
+`-mpointer-size=SIZE'
+ Set the default size of pointers. Possible options for SIZE are
+ `32' or `short' for 32 bit pointers, `64' or `long' for 64 bit
+ pointers, and `no' for supporting only 32 bit pointers. The later
+ option disables `pragma pointer_size'.

File: gcc.info, Node: VxWorks Options, Next: x86 Options, Prev: VMS Options, Up: Submodel Options
@@ -20082,28 +20209,28 @@ The options in this section are defined for all VxWorks targets.
Options specific to the target hardware are listed with the other
options for that target.
-'-mrtp'
+`-mrtp'
GCC can generate code for both VxWorks kernels and real time
processes (RTPs). This option switches from the former to the
- latter. It also defines the preprocessor macro '__RTP__'.
+ latter. It also defines the preprocessor macro `__RTP__'.
-'-non-static'
+`-non-static'
Link an RTP executable against shared libraries rather than static
- libraries. The options '-static' and '-shared' can also be used
- for RTPs (*note Link Options::); '-static' is the default.
+ libraries. The options `-static' and `-shared' can also be used
+ for RTPs (*note Link Options::); `-static' is the default.
-'-Bstatic'
-'-Bdynamic'
+`-Bstatic'
+`-Bdynamic'
These options are passed down to the linker. They are defined for
compatibility with Diab.
-'-Xbind-lazy'
+`-Xbind-lazy'
Enable lazy binding of function calls. This option is equivalent
- to '-Wl,-z,now' and is defined for compatibility with Diab.
+ to `-Wl,-z,now' and is defined for compatibility with Diab.
-'-Xbind-now'
- Disable lazy binding of function calls. This option is the default
- and is defined for compatibility with Diab.
+`-Xbind-now'
+ Disable lazy binding of function calls. This option is the
+ default and is defined for compatibility with Diab.

File: gcc.info, Node: x86 Options, Next: x86 Windows Options, Prev: VxWorks Options, Up: Submodel Options
@@ -20111,241 +20238,246 @@ File: gcc.info, Node: x86 Options, Next: x86 Windows Options, Prev: VxWorks O
3.17.53 x86 Options
-------------------
-These '-m' options are defined for the x86 family of computers.
+These `-m' options are defined for the x86 family of computers.
-'-march=CPU-TYPE'
+`-march=CPU-TYPE'
Generate instructions for the machine type CPU-TYPE. In contrast
- to '-mtune=CPU-TYPE', which merely tunes the generated code for the
- specified CPU-TYPE, '-march=CPU-TYPE' allows GCC to generate code
- that may not run at all on processors other than the one indicated.
- Specifying '-march=CPU-TYPE' implies '-mtune=CPU-TYPE'.
+ to `-mtune=CPU-TYPE', which merely tunes the generated code for
+ the specified CPU-TYPE, `-march=CPU-TYPE' allows GCC to generate
+ code that may not run at all on processors other than the one
+ indicated. Specifying `-march=CPU-TYPE' implies `-mtune=CPU-TYPE'.
The choices for CPU-TYPE are:
- 'native'
+ `native'
This selects the CPU to generate code for at compilation time
by determining the processor type of the compiling machine.
- Using '-march=native' enables all instruction subsets
- supported by the local machine (hence the result might not run
- on different machines). Using '-mtune=native' produces code
- optimized for the local machine under the constraints of the
- selected instruction set.
+ Using `-march=native' enables all instruction subsets
+ supported by the local machine (hence the result might not
+ run on different machines). Using `-mtune=native' produces
+ code optimized for the local machine under the constraints of
+ the selected instruction set.
- 'i386'
+ `i386'
Original Intel i386 CPU.
- 'i486'
+ `i486'
Intel i486 CPU. (No scheduling is implemented for this chip.)
- 'i586'
- 'pentium'
+ `i586'
+ `pentium'
Intel Pentium CPU with no MMX support.
- 'pentium-mmx'
+ `pentium-mmx'
Intel Pentium MMX CPU, based on Pentium core with MMX
instruction set support.
- 'pentiumpro'
+ `pentiumpro'
Intel Pentium Pro CPU.
- 'i686'
- When used with '-march', the Pentium Pro instruction set is
+ `i686'
+ When used with `-march', the Pentium Pro instruction set is
used, so the code runs on all i686 family chips. When used
- with '-mtune', it has the same meaning as 'generic'.
+ with `-mtune', it has the same meaning as `generic'.
- 'pentium2'
+ `pentium2'
Intel Pentium II CPU, based on Pentium Pro core with MMX
instruction set support.
- 'pentium3'
- 'pentium3m'
+ `pentium3'
+ `pentium3m'
Intel Pentium III CPU, based on Pentium Pro core with MMX and
SSE instruction set support.
- 'pentium-m'
+ `pentium-m'
Intel Pentium M; low-power version of Intel Pentium III CPU
with MMX, SSE and SSE2 instruction set support. Used by
Centrino notebooks.
- 'pentium4'
- 'pentium4m'
+ `pentium4'
+ `pentium4m'
Intel Pentium 4 CPU with MMX, SSE and SSE2 instruction set
support.
- 'prescott'
+ `prescott'
Improved version of Intel Pentium 4 CPU with MMX, SSE, SSE2
and SSE3 instruction set support.
- 'nocona'
+ `nocona'
Improved version of Intel Pentium 4 CPU with 64-bit
extensions, MMX, SSE, SSE2 and SSE3 instruction set support.
- 'core2'
+ `core2'
Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3
and SSSE3 instruction set support.
- 'nehalem'
+ `nehalem'
Intel Nehalem CPU with 64-bit extensions, MMX, SSE, SSE2,
SSE3, SSSE3, SSE4.1, SSE4.2 and POPCNT instruction set
support.
- 'westmere'
+ `westmere'
Intel Westmere CPU with 64-bit extensions, MMX, SSE, SSE2,
SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES and PCLMUL
instruction set support.
- 'sandybridge'
- Intel Sandy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2,
- SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and PCLMUL
- instruction set support.
+ `sandybridge'
+ Intel Sandy Bridge CPU with 64-bit extensions, MMX, SSE,
+ SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and
+ PCLMUL instruction set support.
- 'ivybridge'
+ `ivybridge'
Intel Ivy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2,
SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL,
FSGSBASE, RDRND and F16C instruction set support.
- 'haswell'
+ `haswell'
Intel Haswell CPU with 64-bit extensions, MOVBE, MMX, SSE,
SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES,
PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2 and F16C instruction
set support.
- 'broadwell'
+ `broadwell'
Intel Broadwell CPU with 64-bit extensions, MOVBE, MMX, SSE,
SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES,
PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ADCX
and PREFETCHW instruction set support.
- 'bonnell'
+ `bonnell'
Intel Bonnell CPU with 64-bit extensions, MOVBE, MMX, SSE,
SSE2, SSE3 and SSSE3 instruction set support.
- 'silvermont'
+ `silvermont'
Intel Silvermont CPU with 64-bit extensions, MOVBE, MMX, SSE,
SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES, PCLMUL and
RDRND instruction set support.
- 'knl'
- Intel Knight's Landing CPU with 64-bit extensions, MOVBE, MMX,
- SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2,
- AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED,
- ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER and AVX512CD
- instruction set support.
+ `knl'
+ Intel Knight's Landing CPU with 64-bit extensions, MOVBE,
+ MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX,
+ AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C,
+ RDSEED, ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER and
+ AVX512CD instruction set support.
- 'k6'
+ `k6'
AMD K6 CPU with MMX instruction set support.
- 'k6-2'
- 'k6-3'
+ `k6-2'
+ `k6-3'
Improved versions of AMD K6 CPU with MMX and 3DNow!
instruction set support.
- 'athlon'
- 'athlon-tbird'
+ `athlon'
+ `athlon-tbird'
AMD Athlon CPU with MMX, 3dNOW!, enhanced 3DNow! and SSE
prefetch instructions support.
- 'athlon-4'
- 'athlon-xp'
- 'athlon-mp'
+ `athlon-4'
+ `athlon-xp'
+ `athlon-mp'
Improved AMD Athlon CPU with MMX, 3DNow!, enhanced 3DNow! and
full SSE instruction set support.
- 'k8'
- 'opteron'
- 'athlon64'
- 'athlon-fx'
+ `k8'
+ `opteron'
+ `athlon64'
+ `athlon-fx'
Processors based on the AMD K8 core with x86-64 instruction
set support, including the AMD Opteron, Athlon 64, and Athlon
64 FX processors. (This supersets MMX, SSE, SSE2, 3DNow!,
enhanced 3DNow! and 64-bit instruction set extensions.)
- 'k8-sse3'
- 'opteron-sse3'
- 'athlon64-sse3'
+ `k8-sse3'
+ `opteron-sse3'
+ `athlon64-sse3'
Improved versions of AMD K8 cores with SSE3 instruction set
support.
- 'amdfam10'
- 'barcelona'
- CPUs based on AMD Family 10h cores with x86-64 instruction set
- support. (This supersets MMX, SSE, SSE2, SSE3, SSE4A, 3DNow!,
- enhanced 3DNow!, ABM and 64-bit instruction set extensions.)
-
- 'bdver1'
- CPUs based on AMD Family 15h cores with x86-64 instruction set
- support. (This supersets FMA4, AVX, XOP, LWP, AES, PCL_MUL,
- CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM
- and 64-bit instruction set extensions.)
- 'bdver2'
- AMD Family 15h core based CPUs with x86-64 instruction set
- support. (This supersets BMI, TBM, F16C, FMA, FMA4, AVX, XOP,
- LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3,
- SSE4.1, SSE4.2, ABM and 64-bit instruction set extensions.)
- 'bdver3'
+ `amdfam10'
+ `barcelona'
+ CPUs based on AMD Family 10h cores with x86-64 instruction
+ set support. (This supersets MMX, SSE, SSE2, SSE3, SSE4A,
+ 3DNow!, enhanced 3DNow!, ABM and 64-bit instruction set
+ extensions.)
+
+ `bdver1'
+ CPUs based on AMD Family 15h cores with x86-64 instruction
+ set support. (This supersets FMA4, AVX, XOP, LWP, AES,
+ PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1,
+ SSE4.2, ABM and 64-bit instruction set extensions.)
+
+ `bdver2'
AMD Family 15h core based CPUs with x86-64 instruction set
- support. (This supersets BMI, TBM, F16C, FMA, FMA4, FSGSBASE,
- AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3,
- SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set
- extensions.
- 'bdver4'
+ support. (This supersets BMI, TBM, F16C, FMA, FMA4, AVX,
+ XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A,
+ SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set
+ extensions.)
+
+ `bdver3'
AMD Family 15h core based CPUs with x86-64 instruction set
- support. (This supersets BMI, BMI2, TBM, F16C, FMA, FMA4,
- FSGSBASE, AVX, AVX2, XOP, LWP, AES, PCL_MUL, CX16, MOVBE, MMX,
- SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit
+ support. (This supersets BMI, TBM, F16C, FMA, FMA4,
+ FSGSBASE, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2,
+ SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit
instruction set extensions.
- 'btver1'
- CPUs based on AMD Family 14h cores with x86-64 instruction set
- support. (This supersets MMX, SSE, SSE2, SSE3, SSSE3, SSE4A,
- CX16, ABM and 64-bit instruction set extensions.)
-
- 'btver2'
- CPUs based on AMD Family 16h cores with x86-64 instruction set
- support. This includes MOVBE, F16C, BMI, AVX, PCL_MUL, AES,
- SSE4.2, SSE4.1, CX16, ABM, SSE4A, SSSE3, SSE3, SSE2, SSE, MMX
- and 64-bit instruction set extensions.
-
- 'winchip-c6'
+ `bdver4'
+ AMD Family 15h core based CPUs with x86-64 instruction set
+ support. (This supersets BMI, BMI2, TBM, F16C, FMA, FMA4,
+ FSGSBASE, AVX, AVX2, XOP, LWP, AES, PCL_MUL, CX16, MOVBE,
+ MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and
+ 64-bit instruction set extensions.
+
+ `btver1'
+ CPUs based on AMD Family 14h cores with x86-64 instruction
+ set support. (This supersets MMX, SSE, SSE2, SSE3, SSSE3,
+ SSE4A, CX16, ABM and 64-bit instruction set extensions.)
+
+ `btver2'
+ CPUs based on AMD Family 16h cores with x86-64 instruction
+ set support. This includes MOVBE, F16C, BMI, AVX, PCL_MUL,
+ AES, SSE4.2, SSE4.1, CX16, ABM, SSE4A, SSSE3, SSE3, SSE2,
+ SSE, MMX and 64-bit instruction set extensions.
+
+ `winchip-c6'
IDT WinChip C6 CPU, dealt in same way as i486 with additional
MMX instruction set support.
- 'winchip2'
+ `winchip2'
IDT WinChip 2 CPU, dealt in same way as i486 with additional
- MMX and 3DNow! instruction set support.
+ MMX and 3DNow! instruction set support.
- 'c3'
+ `c3'
VIA C3 CPU with MMX and 3DNow! instruction set support. (No
scheduling is implemented for this chip.)
- 'c3-2'
+ `c3-2'
VIA C3-2 (Nehemiah/C5XL) CPU with MMX and SSE instruction set
support. (No scheduling is implemented for this chip.)
- 'geode'
+ `geode'
AMD Geode embedded processor with MMX and 3DNow! instruction
set support.
-'-mtune=CPU-TYPE'
+`-mtune=CPU-TYPE'
Tune to CPU-TYPE everything applicable about the generated code,
except for the ABI and the set of available instructions. While
- picking a specific CPU-TYPE schedules things appropriately for that
- particular chip, the compiler does not generate any code that
+ picking a specific CPU-TYPE schedules things appropriately for
+ that particular chip, the compiler does not generate any code that
cannot run on the default machine type unless you use a
- '-march=CPU-TYPE' option. For example, if GCC is configured for
- i686-pc-linux-gnu then '-mtune=pentium4' generates code that is
+ `-march=CPU-TYPE' option. For example, if GCC is configured for
+ i686-pc-linux-gnu then `-mtune=pentium4' generates code that is
tuned for Pentium 4 but still runs on i686 machines.
- The choices for CPU-TYPE are the same as for '-march'. In
- addition, '-mtune' supports 2 extra choices for CPU-TYPE:
+ The choices for CPU-TYPE are the same as for `-march'. In
+ addition, `-mtune' supports 2 extra choices for CPU-TYPE:
- 'generic'
+ `generic'
Produce code optimized for the most common IA32/AMD64/EM64T
processors. If you know the CPU on which your code will run,
- then you should use the corresponding '-mtune' or '-march'
- option instead of '-mtune=generic'. But, if you do not know
- exactly what CPU users of your application will have, then you
- should use this option.
+ then you should use the corresponding `-mtune' or `-march'
+ option instead of `-mtune=generic'. But, if you do not know
+ exactly what CPU users of your application will have, then
+ you should use this option.
As new processors are deployed in the marketplace, the
behavior of this option will change. Therefore, if you
@@ -20353,18 +20485,19 @@ These '-m' options are defined for the x86 family of computers.
by this option will change to reflect the processors that are
most common at the time that version of GCC is released.
- There is no '-march=generic' option because '-march' indicates
- the instruction set the compiler can use, and there is no
- generic instruction set applicable to all processors. In
- contrast, '-mtune' indicates the processor (or, in this case,
- collection of processors) for which the code is optimized.
+ There is no `-march=generic' option because `-march'
+ indicates the instruction set the compiler can use, and there
+ is no generic instruction set applicable to all processors.
+ In contrast, `-mtune' indicates the processor (or, in this
+ case, collection of processors) for which the code is
+ optimized.
- 'intel'
+ `intel'
Produce code optimized for the most current Intel processors,
- which are Haswell and Silvermont for this version of GCC. If
+ which are Haswell and Silvermont for this version of GCC. If
you know the CPU on which your code will run, then you should
- use the corresponding '-mtune' or '-march' option instead of
- '-mtune=intel'. But, if you want your application performs
+ use the corresponding `-mtune' or `-march' option instead of
+ `-mtune=intel'. But, if you want your application performs
better on both Haswell and Silvermont, then you should use
this option.
@@ -20374,56 +20507,56 @@ These '-m' options are defined for the x86 family of computers.
by this option will change to reflect the most current Intel
processors at the time that version of GCC is released.
- There is no '-march=intel' option because '-march' indicates
+ There is no `-march=intel' option because `-march' indicates
the instruction set the compiler can use, and there is no
common instruction set applicable to all processors. In
- contrast, '-mtune' indicates the processor (or, in this case,
+ contrast, `-mtune' indicates the processor (or, in this case,
collection of processors) for which the code is optimized.
-'-mcpu=CPU-TYPE'
- A deprecated synonym for '-mtune'.
+`-mcpu=CPU-TYPE'
+ A deprecated synonym for `-mtune'.
-'-mfpmath=UNIT'
+`-mfpmath=UNIT'
Generate floating-point arithmetic for selected unit UNIT. The
choices for UNIT are:
- '387'
- Use the standard 387 floating-point coprocessor present on the
- majority of chips and emulated otherwise. Code compiled with
- this option runs almost everywhere. The temporary results are
- computed in 80-bit precision instead of the precision
- specified by the type, resulting in slightly different results
- compared to most of other chips. See '-ffloat-store' for more
- detailed description.
+ `387'
+ Use the standard 387 floating-point coprocessor present on
+ the majority of chips and emulated otherwise. Code compiled
+ with this option runs almost everywhere. The temporary
+ results are computed in 80-bit precision instead of the
+ precision specified by the type, resulting in slightly
+ different results compared to most of other chips. See
+ `-ffloat-store' for more detailed description.
This is the default choice for x86-32 targets.
- 'sse'
+ `sse'
Use scalar floating-point instructions present in the SSE
- instruction set. This instruction set is supported by Pentium
- III and newer chips, and in the AMD line by Athlon-4, Athlon
- XP and Athlon MP chips. The earlier version of the SSE
+ instruction set. This instruction set is supported by
+ Pentium III and newer chips, and in the AMD line by Athlon-4,
+ Athlon XP and Athlon MP chips. The earlier version of the SSE
instruction set supports only single-precision arithmetic,
thus the double and extended-precision arithmetic are still
done using 387. A later version, present only in Pentium 4
and AMD x86-64 chips, supports double-precision arithmetic
too.
- For the x86-32 compiler, you must use '-march=CPU-TYPE',
- '-msse' or '-msse2' switches to enable SSE extensions and make
- this option effective. For the x86-64 compiler, these
+ For the x86-32 compiler, you must use `-march=CPU-TYPE',
+ `-msse' or `-msse2' switches to enable SSE extensions and
+ make this option effective. For the x86-64 compiler, these
extensions are enabled by default.
The resulting code should be considerably faster in the
- majority of cases and avoid the numerical instability problems
- of 387 code, but may break some existing code that expects
- temporaries to be 80 bits.
+ majority of cases and avoid the numerical instability
+ problems of 387 code, but may break some existing code that
+ expects temporaries to be 80 bits.
This is the default choice for the x86-64 compiler.
- 'sse,387'
- 'sse+387'
- 'both'
+ `sse,387'
+ `sse+387'
+ `both'
Attempt to utilize both instruction sets at once. This
effectively doubles the amount of available registers, and on
chips with separate execution units for 387 and SSE the
@@ -20432,185 +20565,184 @@ These '-m' options are defined for the x86 family of computers.
not model separate functional units well, resulting in
unstable performance.
-'-masm=DIALECT'
+`-masm=DIALECT'
Output assembly instructions using selected DIALECT. Also affects
- which dialect is used for basic 'asm' (*note Basic Asm::) and
- extended 'asm' (*note Extended Asm::). Supported choices (in
- dialect order) are 'att' or 'intel'. The default is 'att'. Darwin
- does not support 'intel'.
+ which dialect is used for basic `asm' (*note Basic Asm::) and
+ extended `asm' (*note Extended Asm::). Supported choices (in
+ dialect order) are `att' or `intel'. The default is `att'. Darwin
+ does not support `intel'.
-'-mieee-fp'
-'-mno-ieee-fp'
+`-mieee-fp'
+`-mno-ieee-fp'
Control whether or not the compiler uses IEEE floating-point
comparisons. These correctly handle the case where the result of a
comparison is unordered.
-'-msoft-float'
+`-msoft-float'
Generate output containing library calls for floating point.
*Warning:* the requisite libraries are not part of GCC. Normally
- the facilities of the machine's usual C compiler are used, but this
- can't be done directly in cross-compilation. You must make your
- own arrangements to provide suitable library functions for
+ the facilities of the machine's usual C compiler are used, but
+ this can't be done directly in cross-compilation. You must make
+ your own arrangements to provide suitable library functions for
cross-compilation.
On machines where a function returns floating-point results in the
80387 register stack, some floating-point opcodes may be emitted
- even if '-msoft-float' is used.
+ even if `-msoft-float' is used.
-'-mno-fp-ret-in-387'
+`-mno-fp-ret-in-387'
Do not use the FPU registers for return values of functions.
The usual calling convention has functions return values of types
- 'float' and 'double' in an FPU register, even if there is no FPU.
+ `float' and `double' in an FPU register, even if there is no FPU.
The idea is that the operating system should emulate an FPU.
- The option '-mno-fp-ret-in-387' causes such values to be returned
+ The option `-mno-fp-ret-in-387' causes such values to be returned
in ordinary CPU registers instead.
-'-mno-fancy-math-387'
- Some 387 emulators do not support the 'sin', 'cos' and 'sqrt'
+`-mno-fancy-math-387'
+ Some 387 emulators do not support the `sin', `cos' and `sqrt'
instructions for the 387. Specify this option to avoid generating
- those instructions. This option is the default on FreeBSD, OpenBSD
- and NetBSD. This option is overridden when '-march' indicates that
+ those instructions. This option is the default on OpenBSD and
+ NetBSD. This option is overridden when `-march' indicates that
the target CPU always has an FPU and so the instruction does not
need emulation. These instructions are not generated unless you
- also use the '-funsafe-math-optimizations' switch.
-
-'-malign-double'
-'-mno-align-double'
- Control whether GCC aligns 'double', 'long double', and 'long long'
- variables on a two-word boundary or a one-word boundary. Aligning
- 'double' variables on a two-word boundary produces code that runs
- somewhat faster on a Pentium at the expense of more memory.
+ also use the `-funsafe-math-optimizations' switch.
+
+`-malign-double'
+`-mno-align-double'
+ Control whether GCC aligns `double', `long double', and `long
+ long' variables on a two-word boundary or a one-word boundary.
+ Aligning `double' variables on a two-word boundary produces code
+ that runs somewhat faster on a Pentium at the expense of more
+ memory.
- On x86-64, '-malign-double' is enabled by default.
+ On x86-64, `-malign-double' is enabled by default.
- *Warning:* if you use the '-malign-double' switch, structures
+ *Warning:* if you use the `-malign-double' switch, structures
containing the above types are aligned differently than the
published application binary interface specifications for the
x86-32 and are not binary compatible with structures in code
compiled without that switch.
-'-m96bit-long-double'
-'-m128bit-long-double'
- These switches control the size of 'long double' type. The x86-32
+`-m96bit-long-double'
+`-m128bit-long-double'
+ These switches control the size of `long double' type. The x86-32
application binary interface specifies the size to be 96 bits, so
- '-m96bit-long-double' is the default in 32-bit mode.
+ `-m96bit-long-double' is the default in 32-bit mode.
- Modern architectures (Pentium and newer) prefer 'long double' to be
- aligned to an 8- or 16-byte boundary. In arrays or structures
+ Modern architectures (Pentium and newer) prefer `long double' to
+ be aligned to an 8- or 16-byte boundary. In arrays or structures
conforming to the ABI, this is not possible. So specifying
- '-m128bit-long-double' aligns 'long double' to a 16-byte boundary
- by padding the 'long double' with an additional 32-bit zero.
+ `-m128bit-long-double' aligns `long double' to a 16-byte boundary
+ by padding the `long double' with an additional 32-bit zero.
- In the x86-64 compiler, '-m128bit-long-double' is the default
- choice as its ABI specifies that 'long double' is aligned on
+ In the x86-64 compiler, `-m128bit-long-double' is the default
+ choice as its ABI specifies that `long double' is aligned on
16-byte boundary.
Notice that neither of these options enable any extra precision
- over the x87 standard of 80 bits for a 'long double'.
+ over the x87 standard of 80 bits for a `long double'.
*Warning:* if you override the default value for your target ABI,
- this changes the size of structures and arrays containing 'long
+ this changes the size of structures and arrays containing `long
double' variables, as well as modifying the function calling
- convention for functions taking 'long double'. Hence they are not
+ convention for functions taking `long double'. Hence they are not
binary-compatible with code compiled without that switch.
-'-mlong-double-64'
-'-mlong-double-80'
-'-mlong-double-128'
- These switches control the size of 'long double' type. A size of
- 64 bits makes the 'long double' type equivalent to the 'double'
- type. This is the default for 32-bit Bionic C library. A size of
- 128 bits makes the 'long double' type equivalent to the
- '__float128' type. This is the default for 64-bit Bionic C
- library.
+`-mlong-double-64'
+`-mlong-double-80'
+`-mlong-double-128'
+ These switches control the size of `long double' type. A size of
+ 64 bits makes the `long double' type equivalent to the `double'
+ type. This is the default for 32-bit Bionic C library. A size of
+ 128 bits makes the `long double' type equivalent to the
+ `__float128' type. This is the default for 64-bit Bionic C library.
*Warning:* if you override the default value for your target ABI,
- this changes the size of structures and arrays containing 'long
+ this changes the size of structures and arrays containing `long
double' variables, as well as modifying the function calling
- convention for functions taking 'long double'. Hence they are not
+ convention for functions taking `long double'. Hence they are not
binary-compatible with code compiled without that switch.
-'-malign-data=TYPE'
+`-malign-data=TYPE'
Control how GCC aligns variables. Supported values for TYPE are
- 'compat' uses increased alignment value compatible uses GCC 4.8 and
- earlier, 'abi' uses alignment value as specified by the psABI, and
- 'cacheline' uses increased alignment value to match the cache line
- size. 'compat' is the default.
-
-'-mlarge-data-threshold=THRESHOLD'
- When '-mcmodel=medium' is specified, data objects larger than
- THRESHOLD are placed in the large data section. This value must be
- the same across all objects linked into the binary, and defaults to
- 65535.
-
-'-mrtd'
+ `compat' uses increased alignment value compatible uses GCC 4.8
+ and earlier, `abi' uses alignment value as specified by the psABI,
+ and `cacheline' uses increased alignment value to match the cache
+ line size. `compat' is the default.
+
+`-mlarge-data-threshold=THRESHOLD'
+ When `-mcmodel=medium' is specified, data objects larger than
+ THRESHOLD are placed in the large data section. This value must
+ be the same across all objects linked into the binary, and
+ defaults to 65535.
+
+`-mrtd'
Use a different function-calling convention, in which functions
- that take a fixed number of arguments return with the 'ret NUM'
+ that take a fixed number of arguments return with the `ret NUM'
instruction, which pops their arguments while returning. This
saves one instruction in the caller since there is no need to pop
the arguments there.
You can specify that an individual function is called with this
- calling sequence with the function attribute 'stdcall'. You can
- also override the '-mrtd' option by using the function attribute
- 'cdecl'. *Note Function Attributes::.
+ calling sequence with the function attribute `stdcall'. You can
+ also override the `-mrtd' option by using the function attribute
+ `cdecl'. *Note Function Attributes::.
*Warning:* this calling convention is incompatible with the one
normally used on Unix, so you cannot use it if you need to call
libraries compiled with the Unix compiler.
Also, you must provide function prototypes for all functions that
- take variable numbers of arguments (including 'printf'); otherwise
+ take variable numbers of arguments (including `printf'); otherwise
incorrect code is generated for calls to those functions.
In addition, seriously incorrect code results if you call a
function with too many arguments. (Normally, extra arguments are
harmlessly ignored.)
-'-mregparm=NUM'
+`-mregparm=NUM'
Control how many registers are used to pass integer arguments. By
default, no registers are used to pass arguments, and at most 3
registers can be used. You can control this behavior for a
- specific function by using the function attribute 'regparm'. *Note
- Function Attributes::.
+ specific function by using the function attribute `regparm'.
+ *Note Function Attributes::.
*Warning:* if you use this switch, and NUM is nonzero, then you
must build all modules with the same value, including any
libraries. This includes the system libraries and startup modules.
-'-msseregparm'
+`-msseregparm'
Use SSE register passing conventions for float and double arguments
and return values. You can control this behavior for a specific
- function by using the function attribute 'sseregparm'. *Note
+ function by using the function attribute `sseregparm'. *Note
Function Attributes::.
*Warning:* if you use this switch then you must build all modules
with the same value, including any libraries. This includes the
system libraries and startup modules.
-'-mvect8-ret-in-mem'
+`-mvect8-ret-in-mem'
Return 8-byte vectors in memory instead of MMX registers. This is
the default on Solaris 8 and 9 and VxWorks to match the ABI of the
Sun Studio compilers until version 12. Later compiler versions
- (starting with Studio 12 Update 1) follow the ABI used by other x86
- targets, which is the default on Solaris 10 and later. _Only_ use
- this option if you need to remain compatible with existing code
- produced by those previous compiler versions or older versions of
- GCC.
-
-'-mpc32'
-'-mpc64'
-'-mpc80'
+ (starting with Studio 12 Update 1) follow the ABI used by other
+ x86 targets, which is the default on Solaris 10 and later. _Only_
+ use this option if you need to remain compatible with existing
+ code produced by those previous compiler versions or older
+ versions of GCC.
+`-mpc32'
+`-mpc64'
+`-mpc80'
Set 80387 floating-point precision to 32, 64 or 80 bits. When
- '-mpc32' is specified, the significands of results of
+ `-mpc32' is specified, the significands of results of
floating-point operations are rounded to 24 bits (single
- precision); '-mpc64' rounds the significands of results of
+ precision); `-mpc64' rounds the significands of results of
floating-point operations to 53 bits (double precision) and
- '-mpc80' rounds the significands of results of floating-point
+ `-mpc80' rounds the significands of results of floating-point
operations to 64 bits (extended double precision), which is the
default. When this option is used, floating-point operations in
higher precisions are not available to the programmer without
@@ -20618,29 +20750,30 @@ These '-m' options are defined for the x86 family of computers.
Setting the rounding of floating-point operations to less than the
default 80 bits can speed some programs by 2% or more. Note that
- some mathematical libraries assume that extended-precision (80-bit)
- floating-point operations are enabled by default; routines in such
- libraries could suffer significant loss of accuracy, typically
- through so-called "catastrophic cancellation", when this option is
- used to set the precision to less than extended precision.
-
-'-mstackrealign'
- Realign the stack at entry. On the x86, the '-mstackrealign'
+ some mathematical libraries assume that extended-precision
+ (80-bit) floating-point operations are enabled by default;
+ routines in such libraries could suffer significant loss of
+ accuracy, typically through so-called "catastrophic cancellation",
+ when this option is used to set the precision to less than
+ extended precision.
+
+`-mstackrealign'
+ Realign the stack at entry. On the x86, the `-mstackrealign'
option generates an alternate prologue and epilogue that realigns
- the run-time stack if necessary. This supports mixing legacy codes
- that keep 4-byte stack alignment with modern codes that keep
+ the run-time stack if necessary. This supports mixing legacy
+ codes that keep 4-byte stack alignment with modern codes that keep
16-byte stack alignment for SSE compatibility. See also the
- attribute 'force_align_arg_pointer', applicable to individual
+ attribute `force_align_arg_pointer', applicable to individual
functions.
-'-mpreferred-stack-boundary=NUM'
+`-mpreferred-stack-boundary=NUM'
Attempt to keep the stack boundary aligned to a 2 raised to NUM
- byte boundary. If '-mpreferred-stack-boundary' is not specified,
+ byte boundary. If `-mpreferred-stack-boundary' is not specified,
the default is 4 (16 bytes or 128 bits).
*Warning:* When generating code for the x86-64 architecture with
- SSE extensions disabled, '-mpreferred-stack-boundary=3' can be used
- to keep the stack boundary aligned to 8 byte boundary. Since
+ SSE extensions disabled, `-mpreferred-stack-boundary=3' can be
+ used to keep the stack boundary aligned to 8 byte boundary. Since
x86-64 ABI require 16 byte stack alignment, this is ABI
incompatible and intended to be used in controlled environment
where stack space is important limitation. This option leads to
@@ -20650,122 +20783,124 @@ These '-m' options are defined for the x86 family of computers.
misaligned memory access traps. In addition, variable arguments
are handled incorrectly for 16 byte aligned objects (including x87
long double and __int128), leading to wrong results. You must
- build all modules with '-mpreferred-stack-boundary=3', including
+ build all modules with `-mpreferred-stack-boundary=3', including
any libraries. This includes the system libraries and startup
modules.
-'-mincoming-stack-boundary=NUM'
+`-mincoming-stack-boundary=NUM'
Assume the incoming stack is aligned to a 2 raised to NUM byte
- boundary. If '-mincoming-stack-boundary' is not specified, the one
- specified by '-mpreferred-stack-boundary' is used.
+ boundary. If `-mincoming-stack-boundary' is not specified, the
+ one specified by `-mpreferred-stack-boundary' is used.
- On Pentium and Pentium Pro, 'double' and 'long double' values
- should be aligned to an 8-byte boundary (see '-malign-double') or
- suffer significant run time performance penalties. On Pentium III,
- the Streaming SIMD Extension (SSE) data type '__m128' may not work
- properly if it is not 16-byte aligned.
+ On Pentium and Pentium Pro, `double' and `long double' values
+ should be aligned to an 8-byte boundary (see `-malign-double') or
+ suffer significant run time performance penalties. On Pentium
+ III, the Streaming SIMD Extension (SSE) data type `__m128' may not
+ work properly if it is not 16-byte aligned.
To ensure proper alignment of this values on the stack, the stack
- boundary must be as aligned as that required by any value stored on
- the stack. Further, every function must be generated such that it
- keeps the stack aligned. Thus calling a function compiled with a
- higher preferred stack boundary from a function compiled with a
- lower preferred stack boundary most likely misaligns the stack. It
- is recommended that libraries that use callbacks always use the
+ boundary must be as aligned as that required by any value stored
+ on the stack. Further, every function must be generated such that
+ it keeps the stack aligned. Thus calling a function compiled with
+ a higher preferred stack boundary from a function compiled with a
+ lower preferred stack boundary most likely misaligns the stack.
+ It is recommended that libraries that use callbacks always use the
default setting.
This extra alignment does consume extra stack space, and generally
increases code size. Code that is sensitive to stack space usage,
such as embedded systems and operating system kernels, may want to
- reduce the preferred alignment to '-mpreferred-stack-boundary=2'.
-
-'-mmmx'
-'-msse'
-'-msse2'
-'-msse3'
-'-mssse3'
-'-msse4'
-'-msse4a'
-'-msse4.1'
-'-msse4.2'
-'-mavx'
-'-mavx2'
-'-mavx512f'
-'-mavx512pf'
-'-mavx512er'
-'-mavx512cd'
-'-msha'
-'-maes'
-'-mpclmul'
-'-mclfushopt'
-'-mfsgsbase'
-'-mrdrnd'
-'-mf16c'
-'-mfma'
-'-mfma4'
-'-mno-fma4'
-'-mprefetchwt1'
-'-mxop'
-'-mlwp'
-'-m3dnow'
-'-mpopcnt'
-'-mabm'
-'-mbmi'
-'-mbmi2'
-'-mlzcnt'
-'-mfxsr'
-'-mxsave'
-'-mxsaveopt'
-'-mxsavec'
-'-mxsaves'
-'-mrtm'
-'-mtbm'
-'-mmpx'
+ reduce the preferred alignment to `-mpreferred-stack-boundary=2'.
+
+`-mmmx'
+`-msse'
+`-msse2'
+`-msse3'
+`-mssse3'
+`-msse4'
+`-msse4a'
+`-msse4.1'
+`-msse4.2'
+`-mavx'
+`-mavx2'
+`-mavx512f'
+`-mavx512pf'
+`-mavx512er'
+`-mavx512cd'
+`-msha'
+`-maes'
+`-mpclmul'
+`-mclfushopt'
+`-mfsgsbase'
+`-mrdrnd'
+`-mf16c'
+`-mfma'
+`-mfma4'
+`-mno-fma4'
+`-mprefetchwt1'
+`-mxop'
+`-mlwp'
+`-m3dnow'
+`-mpopcnt'
+`-mabm'
+`-mbmi'
+`-mbmi2'
+`-mlzcnt'
+`-mfxsr'
+`-mxsave'
+`-mxsaveopt'
+`-mxsavec'
+`-mxsaves'
+`-mrtm'
+`-mtbm'
+`-mmpx'
+`-mmwaitx'
These switches enable the use of instructions in the MMX, SSE,
SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER,
AVX512CD, SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A,
FMA4, XOP, LWP, ABM, BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM,
- MPX or 3DNow! extended instruction sets. Each has a corresponding
- '-mno-' option to disable use of these instructions.
+ MPX, MWAITX or 3DNow! extended instruction sets. Each has a
+ corresponding `-mno-' option to disable use of these instructions.
These extensions are also available as built-in functions: see
*note x86 Built-in Functions::, for details of the functions
enabled and disabled by these switches.
To generate SSE/SSE2 instructions automatically from floating-point
- code (as opposed to 387 instructions), see '-mfpmath=sse'.
+ code (as opposed to 387 instructions), see `-mfpmath=sse'.
- GCC depresses SSEx instructions when '-mavx' is used. Instead, it
+ GCC depresses SSEx instructions when `-mavx' is used. Instead, it
generates new AVX instructions or AVX equivalence for all SSEx
instructions when needed.
These options enable GCC to use these extended instructions in
- generated code, even without '-mfpmath=sse'. Applications that
+ generated code, even without `-mfpmath=sse'. Applications that
perform run-time CPU detection must compile separate files for each
supported architecture, using the appropriate flags. In
particular, the file containing the CPU detection code should be
compiled without these options.
-'-mdump-tune-features'
+`-mdump-tune-features'
This option instructs GCC to dump the names of the x86 performance
- tuning features and default settings. The names can be used in
- '-mtune-ctrl=FEATURE-LIST'.
-
-'-mtune-ctrl=FEATURE-LIST'
- This option is used to do fine grain control of x86 code generation
- features. FEATURE-LIST is a comma separated list of FEATURE names.
- See also '-mdump-tune-features'. When specified, the FEATURE is
- turned on if it is not preceded with '^', otherwise, it is turned
- off. '-mtune-ctrl=FEATURE-LIST' is intended to be used by GCC
- developers. Using it may lead to code paths not covered by testing
- and can potentially result in compiler ICEs or runtime errors.
-
-'-mno-default'
- This option instructs GCC to turn off all tunable features. See
- also '-mtune-ctrl=FEATURE-LIST' and '-mdump-tune-features'.
-
-'-mcld'
- This option instructs GCC to emit a 'cld' instruction in the
+ tuning features and default settings. The names can be used in
+ `-mtune-ctrl=FEATURE-LIST'.
+
+`-mtune-ctrl=FEATURE-LIST'
+ This option is used to do fine grain control of x86 code
+ generation features. FEATURE-LIST is a comma separated list of
+ FEATURE names. See also `-mdump-tune-features'. When specified,
+ the FEATURE is turned on if it is not preceded with `^',
+ otherwise, it is turned off. `-mtune-ctrl=FEATURE-LIST' is
+ intended to be used by GCC developers. Using it may lead to code
+ paths not covered by testing and can potentially result in
+ compiler ICEs or runtime errors.
+
+`-mno-default'
+ This option instructs GCC to turn off all tunable features. See
+ also `-mtune-ctrl=FEATURE-LIST' and `-mdump-tune-features'.
+
+`-mcld'
+ This option instructs GCC to emit a `cld' instruction in the
prologue of functions that use string instructions. String
instructions depend on the DF flag to select between autoincrement
or autodecrement mode. While the ABI specifies the DF flag to be
@@ -20774,343 +20909,346 @@ These '-m' options are defined for the x86 family of computers.
dispatchers. The exception handler can be invoked with the DF flag
set, which leads to wrong direction mode when string instructions
are used. This option can be enabled by default on 32-bit x86
- targets by configuring GCC with the '--enable-cld' configure
- option. Generation of 'cld' instructions can be suppressed with
- the '-mno-cld' compiler option in this case.
+ targets by configuring GCC with the `--enable-cld' configure
+ option. Generation of `cld' instructions can be suppressed with
+ the `-mno-cld' compiler option in this case.
-'-mvzeroupper'
- This option instructs GCC to emit a 'vzeroupper' instruction before
- a transfer of control flow out of the function to minimize the AVX
- to SSE transition penalty as well as remove unnecessary 'zeroupper'
- intrinsics.
+`-mvzeroupper'
+ This option instructs GCC to emit a `vzeroupper' instruction
+ before a transfer of control flow out of the function to minimize
+ the AVX to SSE transition penalty as well as remove unnecessary
+ `zeroupper' intrinsics.
-'-mprefer-avx128'
+`-mprefer-avx128'
This option instructs GCC to use 128-bit AVX instructions instead
of 256-bit AVX instructions in the auto-vectorizer.
-'-mcx16'
- This option enables GCC to generate 'CMPXCHG16B' instructions.
- 'CMPXCHG16B' allows for atomic operations on 128-bit double
- quadword (or oword) data types. This is useful for high-resolution
- counters that can be updated by multiple processors (or cores).
- This instruction is generated as part of atomic built-in functions:
- see *note __sync Builtins:: or *note __atomic Builtins:: for
- details.
-
-'-msahf'
- This option enables generation of 'SAHF' instructions in 64-bit
+`-mcx16'
+ This option enables GCC to generate `CMPXCHG16B' instructions.
+ `CMPXCHG16B' allows for atomic operations on 128-bit double
+ quadword (or oword) data types. This is useful for
+ high-resolution counters that can be updated by multiple
+ processors (or cores). This instruction is generated as part of
+ atomic built-in functions: see *note __sync Builtins:: or *note
+ __atomic Builtins:: for details.
+
+`-msahf'
+ This option enables generation of `SAHF' instructions in 64-bit
code. Early Intel Pentium 4 CPUs with Intel 64 support, prior to
the introduction of Pentium 4 G1 step in December 2005, lacked the
- 'LAHF' and 'SAHF' instructions which are supported by AMD64. These
- are load and store instructions, respectively, for certain status
- flags. In 64-bit mode, the 'SAHF' instruction is used to optimize
- 'fmod', 'drem', and 'remainder' built-in functions; see *note Other
- Builtins:: for details.
-
-'-mmovbe'
- This option enables use of the 'movbe' instruction to implement
- '__builtin_bswap32' and '__builtin_bswap64'.
-
-'-mcrc32'
- This option enables built-in functions '__builtin_ia32_crc32qi',
- '__builtin_ia32_crc32hi', '__builtin_ia32_crc32si' and
- '__builtin_ia32_crc32di' to generate the 'crc32' machine
+ `LAHF' and `SAHF' instructions which are supported by AMD64.
+ These are load and store instructions, respectively, for certain
+ status flags. In 64-bit mode, the `SAHF' instruction is used to
+ optimize `fmod', `drem', and `remainder' built-in functions; see
+ *note Other Builtins:: for details.
+
+`-mmovbe'
+ This option enables use of the `movbe' instruction to implement
+ `__builtin_bswap32' and `__builtin_bswap64'.
+
+`-mcrc32'
+ This option enables built-in functions `__builtin_ia32_crc32qi',
+ `__builtin_ia32_crc32hi', `__builtin_ia32_crc32si' and
+ `__builtin_ia32_crc32di' to generate the `crc32' machine
instruction.
-'-mrecip'
- This option enables use of 'RCPSS' and 'RSQRTSS' instructions (and
- their vectorized variants 'RCPPS' and 'RSQRTPS') with an additional
- Newton-Raphson step to increase precision instead of 'DIVSS' and
- 'SQRTSS' (and their vectorized variants) for single-precision
- floating-point arguments. These instructions are generated only
- when '-funsafe-math-optimizations' is enabled together with
- '-finite-math-only' and '-fno-trapping-math'. Note that while the
- throughput of the sequence is higher than the throughput of the
- non-reciprocal instruction, the precision of the sequence can be
- decreased by up to 2 ulp (i.e. the inverse of 1.0 equals
- 0.99999994).
-
- Note that GCC implements '1.0f/sqrtf(X)' in terms of 'RSQRTSS' (or
- 'RSQRTPS') already with '-ffast-math' (or the above option
- combination), and doesn't need '-mrecip'.
+`-mrecip'
+ This option enables use of `RCPSS' and `RSQRTSS' instructions (and
+ their vectorized variants `RCPPS' and `RSQRTPS') with an
+ additional Newton-Raphson step to increase precision instead of
+ `DIVSS' and `SQRTSS' (and their vectorized variants) for
+ single-precision floating-point arguments. These instructions are
+ generated only when `-funsafe-math-optimizations' is enabled
+ together with `-finite-math-only' and `-fno-trapping-math'. Note
+ that while the throughput of the sequence is higher than the
+ throughput of the non-reciprocal instruction, the precision of the
+ sequence can be decreased by up to 2 ulp (i.e. the inverse of 1.0
+ equals 0.99999994).
+
+ Note that GCC implements `1.0f/sqrtf(X)' in terms of `RSQRTSS' (or
+ `RSQRTPS') already with `-ffast-math' (or the above option
+ combination), and doesn't need `-mrecip'.
Also note that GCC emits the above sequence with additional
Newton-Raphson step for vectorized single-float division and
- vectorized 'sqrtf(X)' already with '-ffast-math' (or the above
- option combination), and doesn't need '-mrecip'.
+ vectorized `sqrtf(X)' already with `-ffast-math' (or the above
+ option combination), and doesn't need `-mrecip'.
-'-mrecip=OPT'
+`-mrecip=OPT'
This option controls which reciprocal estimate instructions may be
used. OPT is a comma-separated list of options, which may be
- preceded by a '!' to invert the option:
+ preceded by a `!' to invert the option:
- 'all'
+ `all'
Enable all estimate instructions.
- 'default'
- Enable the default instructions, equivalent to '-mrecip'.
+ `default'
+ Enable the default instructions, equivalent to `-mrecip'.
- 'none'
- Disable all estimate instructions, equivalent to '-mno-recip'.
+ `none'
+ Disable all estimate instructions, equivalent to `-mno-recip'.
- 'div'
+ `div'
Enable the approximation for scalar division.
- 'vec-div'
+ `vec-div'
Enable the approximation for vectorized division.
- 'sqrt'
+ `sqrt'
Enable the approximation for scalar square root.
- 'vec-sqrt'
+ `vec-sqrt'
Enable the approximation for vectorized square root.
- So, for example, '-mrecip=all,!sqrt' enables all of the reciprocal
+ So, for example, `-mrecip=all,!sqrt' enables all of the reciprocal
approximations, except for square root.
-'-mveclibabi=TYPE'
+`-mveclibabi=TYPE'
Specifies the ABI type to use for vectorizing intrinsics using an
- external library. Supported values for TYPE are 'svml' for the
- Intel short vector math library and 'acml' for the AMD math core
- library. To use this option, both '-ftree-vectorize' and
- '-funsafe-math-optimizations' have to be enabled, and an SVML or
+ external library. Supported values for TYPE are `svml' for the
+ Intel short vector math library and `acml' for the AMD math core
+ library. To use this option, both `-ftree-vectorize' and
+ `-funsafe-math-optimizations' have to be enabled, and an SVML or
ACML ABI-compatible library must be specified at link time.
- GCC currently emits calls to 'vmldExp2', 'vmldLn2', 'vmldLog102',
- 'vmldLog102', 'vmldPow2', 'vmldTanh2', 'vmldTan2', 'vmldAtan2',
- 'vmldAtanh2', 'vmldCbrt2', 'vmldSinh2', 'vmldSin2', 'vmldAsinh2',
- 'vmldAsin2', 'vmldCosh2', 'vmldCos2', 'vmldAcosh2', 'vmldAcos2',
- 'vmlsExp4', 'vmlsLn4', 'vmlsLog104', 'vmlsLog104', 'vmlsPow4',
- 'vmlsTanh4', 'vmlsTan4', 'vmlsAtan4', 'vmlsAtanh4', 'vmlsCbrt4',
- 'vmlsSinh4', 'vmlsSin4', 'vmlsAsinh4', 'vmlsAsin4', 'vmlsCosh4',
- 'vmlsCos4', 'vmlsAcosh4' and 'vmlsAcos4' for corresponding function
- type when '-mveclibabi=svml' is used, and '__vrd2_sin',
- '__vrd2_cos', '__vrd2_exp', '__vrd2_log', '__vrd2_log2',
- '__vrd2_log10', '__vrs4_sinf', '__vrs4_cosf', '__vrs4_expf',
- '__vrs4_logf', '__vrs4_log2f', '__vrs4_log10f' and '__vrs4_powf'
- for the corresponding function type when '-mveclibabi=acml' is
+ GCC currently emits calls to `vmldExp2', `vmldLn2', `vmldLog102',
+ `vmldLog102', `vmldPow2', `vmldTanh2', `vmldTan2', `vmldAtan2',
+ `vmldAtanh2', `vmldCbrt2', `vmldSinh2', `vmldSin2', `vmldAsinh2',
+ `vmldAsin2', `vmldCosh2', `vmldCos2', `vmldAcosh2', `vmldAcos2',
+ `vmlsExp4', `vmlsLn4', `vmlsLog104', `vmlsLog104', `vmlsPow4',
+ `vmlsTanh4', `vmlsTan4', `vmlsAtan4', `vmlsAtanh4', `vmlsCbrt4',
+ `vmlsSinh4', `vmlsSin4', `vmlsAsinh4', `vmlsAsin4', `vmlsCosh4',
+ `vmlsCos4', `vmlsAcosh4' and `vmlsAcos4' for corresponding
+ function type when `-mveclibabi=svml' is used, and `__vrd2_sin',
+ `__vrd2_cos', `__vrd2_exp', `__vrd2_log', `__vrd2_log2',
+ `__vrd2_log10', `__vrs4_sinf', `__vrs4_cosf', `__vrs4_expf',
+ `__vrs4_logf', `__vrs4_log2f', `__vrs4_log10f' and `__vrs4_powf'
+ for the corresponding function type when `-mveclibabi=acml' is
used.
-'-mabi=NAME'
+`-mabi=NAME'
Generate code for the specified calling convention. Permissible
- values are 'sysv' for the ABI used on GNU/Linux and other systems,
- and 'ms' for the Microsoft ABI. The default is to use the Microsoft
- ABI when targeting Microsoft Windows and the SysV ABI on all other
- systems. You can control this behavior for specific functions by
- using the function attributes 'ms_abi' and 'sysv_abi'. *Note
- Function Attributes::.
-
-'-mtls-dialect=TYPE'
- Generate code to access thread-local storage using the 'gnu' or
- 'gnu2' conventions. 'gnu' is the conservative default; 'gnu2' is
+ values are `sysv' for the ABI used on GNU/Linux and other systems,
+ and `ms' for the Microsoft ABI. The default is to use the
+ Microsoft ABI when targeting Microsoft Windows and the SysV ABI on
+ all other systems. You can control this behavior for specific
+ functions by using the function attributes `ms_abi' and `sysv_abi'.
+ *Note Function Attributes::.
+
+`-mtls-dialect=TYPE'
+ Generate code to access thread-local storage using the `gnu' or
+ `gnu2' conventions. `gnu' is the conservative default; `gnu2' is
more efficient, but it may add compile- and run-time requirements
that cannot be satisfied on all systems.
-'-mpush-args'
-'-mno-push-args'
+`-mpush-args'
+`-mno-push-args'
Use PUSH operations to store outgoing parameters. This method is
- shorter and usually equally fast as method using SUB/MOV operations
- and is enabled by default. In some cases disabling it may improve
- performance because of improved scheduling and reduced
+ shorter and usually equally fast as method using SUB/MOV
+ operations and is enabled by default. In some cases disabling it
+ may improve performance because of improved scheduling and reduced
dependencies.
-'-maccumulate-outgoing-args'
+`-maccumulate-outgoing-args'
If enabled, the maximum amount of space required for outgoing
arguments is computed in the function prologue. This is faster on
most modern CPUs because of reduced dependencies, improved
scheduling and reduced stack usage when the preferred stack
boundary is not equal to 2. The drawback is a notable increase in
- code size. This switch implies '-mno-push-args'.
+ code size. This switch implies `-mno-push-args'.
-'-mthreads'
- Support thread-safe exception handling on MinGW. Programs that rely
- on thread-safe exception handling must compile and link all code
- with the '-mthreads' option. When compiling, '-mthreads' defines
- '-D_MT'; when linking, it links in a special thread helper library
- '-lmingwthrd' which cleans up per-thread exception-handling data.
+`-mthreads'
+ Support thread-safe exception handling on MinGW. Programs that
+ rely on thread-safe exception handling must compile and link all
+ code with the `-mthreads' option. When compiling, `-mthreads'
+ defines `-D_MT'; when linking, it links in a special thread helper
+ library `-lmingwthrd' which cleans up per-thread
+ exception-handling data.
-'-mno-align-stringops'
+`-mno-align-stringops'
Do not align the destination of inlined string operations. This
switch reduces code size and improves performance in case the
destination is already aligned, but GCC doesn't know about it.
-'-minline-all-stringops'
+`-minline-all-stringops'
By default GCC inlines string operations only when the destination
is known to be aligned to least a 4-byte boundary. This enables
more inlining and increases code size, but may improve performance
- of code that depends on fast 'memcpy', 'strlen', and 'memset' for
+ of code that depends on fast `memcpy', `strlen', and `memset' for
short lengths.
-'-minline-stringops-dynamically'
+`-minline-stringops-dynamically'
For string operations of unknown size, use run-time checks with
inline code for small blocks and a library call for large blocks.
-'-mstringop-strategy=ALG'
+`-mstringop-strategy=ALG'
Override the internal decision heuristic for the particular
algorithm to use for inlining string operations. The allowed
values for ALG are:
- 'rep_byte'
- 'rep_4byte'
- 'rep_8byte'
- Expand using i386 'rep' prefix of the specified size.
+ `rep_byte'
+ `rep_4byte'
+ `rep_8byte'
+ Expand using i386 `rep' prefix of the specified size.
- 'byte_loop'
- 'loop'
- 'unrolled_loop'
+ `byte_loop'
+ `loop'
+ `unrolled_loop'
Expand into an inline loop.
- 'libcall'
+ `libcall'
Always use a library call.
-'-mmemcpy-strategy=STRATEGY'
+`-mmemcpy-strategy=STRATEGY'
Override the internal decision heuristic to decide if
- '__builtin_memcpy' should be inlined and what inline algorithm to
- use when the expected size of the copy operation is known.
- STRATEGY is a comma-separated list of ALG:MAX_SIZE:DEST_ALIGN
- triplets. ALG is specified in '-mstringop-strategy', MAX_SIZE
- specifies the max byte size with which inline algorithm ALG is
- allowed. For the last triplet, the MAX_SIZE must be '-1'. The
- MAX_SIZE of the triplets in the list must be specified in
- increasing order. The minimal byte size for ALG is '0' for the
- first triplet and 'MAX_SIZE + 1' of the preceding range.
-
-'-mmemset-strategy=STRATEGY'
- The option is similar to '-mmemcpy-strategy=' except that it is to
- control '__builtin_memset' expansion.
-
-'-momit-leaf-frame-pointer'
+ `__builtin_memcpy' should be inlined and what inline algorithm to
+ use when the expected size of the copy operation is known. STRATEGY
+ is a comma-separated list of ALG:MAX_SIZE:DEST_ALIGN triplets.
+ ALG is specified in `-mstringop-strategy', MAX_SIZE specifies the
+ max byte size with which inline algorithm ALG is allowed. For the
+ last triplet, the MAX_SIZE must be `-1'. The MAX_SIZE of the
+ triplets in the list must be specified in increasing order. The
+ minimal byte size for ALG is `0' for the first triplet and
+ `MAX_SIZE + 1' of the preceding range.
+
+`-mmemset-strategy=STRATEGY'
+ The option is similar to `-mmemcpy-strategy=' except that it is to
+ control `__builtin_memset' expansion.
+
+`-momit-leaf-frame-pointer'
Don't keep the frame pointer in a register for leaf functions.
This avoids the instructions to save, set up, and restore frame
pointers and makes an extra register available in leaf functions.
- The option '-fomit-leaf-frame-pointer' removes the frame pointer
+ The option `-fomit-leaf-frame-pointer' removes the frame pointer
for leaf functions, which might make debugging harder.
-'-mtls-direct-seg-refs'
-'-mno-tls-direct-seg-refs'
+`-mtls-direct-seg-refs'
+`-mno-tls-direct-seg-refs'
Controls whether TLS variables may be accessed with offsets from
- the TLS segment register ('%gs' for 32-bit, '%fs' for 64-bit), or
+ the TLS segment register (`%gs' for 32-bit, `%fs' for 64-bit), or
whether the thread base pointer must be added. Whether or not this
is valid depends on the operating system, and whether it maps the
segment to cover the entire TLS area.
For systems that use the GNU C Library, the default is on.
-'-msse2avx'
-'-mno-sse2avx'
+`-msse2avx'
+`-mno-sse2avx'
Specify that the assembler should encode SSE instructions with VEX
- prefix. The option '-mavx' turns this on by default.
+ prefix. The option `-mavx' turns this on by default.
-'-mfentry'
-'-mno-fentry'
- If profiling is active ('-pg'), put the profiling counter call
+`-mfentry'
+`-mno-fentry'
+ If profiling is active (`-pg'), put the profiling counter call
before the prologue. Note: On x86 architectures the attribute
- 'ms_hook_prologue' isn't possible at the moment for '-mfentry' and
- '-pg'.
+ `ms_hook_prologue' isn't possible at the moment for `-mfentry' and
+ `-pg'.
-'-mrecord-mcount'
-'-mno-record-mcount'
- If profiling is active ('-pg'), generate a __mcount_loc section
- that contains pointers to each profiling call. This is useful for
+`-mrecord-mcount'
+`-mno-record-mcount'
+ If profiling is active (`-pg'), generate a __mcount_loc section
+ that contains pointers to each profiling call. This is useful for
automatically patching and out calls.
-'-mnop-mcount'
-'-mno-nop-mcount'
- If profiling is active ('-pg'), generate the calls to the profiling
- functions as nops. This is useful when they should be patched in
- later dynamically. This is likely only useful together with
- '-mrecord-mcount'.
+`-mnop-mcount'
+`-mno-nop-mcount'
+ If profiling is active (`-pg'), generate the calls to the
+ profiling functions as nops. This is useful when they should be
+ patched in later dynamically. This is likely only useful together
+ with `-mrecord-mcount'.
-'-mskip-rax-setup'
-'-mno-skip-rax-setup'
+`-mskip-rax-setup'
+`-mno-skip-rax-setup'
When generating code for the x86-64 architecture with SSE
- extensions disabled, '-skip-rax-setup' can be used to skip setting
+ extensions disabled, `-skip-rax-setup' can be used to skip setting
up RAX register when there are no variable arguments passed in
vector registers.
- *Warning:* Since RAX register is used to avoid unnecessarily saving
- vector registers on stack when passing variable arguments, the
- impacts of this option are callees may waste some stack space,
+ *Warning:* Since RAX register is used to avoid unnecessarily
+ saving vector registers on stack when passing variable arguments,
+ the impacts of this option are callees may waste some stack space,
misbehave or jump to a random location. GCC 4.4 or newer don't
have those issues, regardless the RAX register value.
-'-m8bit-idiv'
-'-mno-8bit-idiv'
+`-m8bit-idiv'
+`-mno-8bit-idiv'
On some processors, like Intel Atom, 8-bit unsigned integer divide
is much faster than 32-bit/64-bit integer divide. This option
generates a run-time check. If both dividend and divisor are
within range of 0 to 255, 8-bit unsigned integer divide is used
instead of 32-bit/64-bit integer divide.
-'-mavx256-split-unaligned-load'
-'-mavx256-split-unaligned-store'
+`-mavx256-split-unaligned-load'
+`-mavx256-split-unaligned-store'
Split 32-byte AVX unaligned load and store.
-'-mstack-protector-guard=GUARD'
+`-mstack-protector-guard=GUARD'
Generate stack protection code using canary at GUARD. Supported
- locations are 'global' for global canary or 'tls' for per-thread
- canary in the TLS block (the default). This option has effect only
- when '-fstack-protector' or '-fstack-protector-all' is specified.
+ locations are `global' for global canary or `tls' for per-thread
+ canary in the TLS block (the default). This option has effect
+ only when `-fstack-protector' or `-fstack-protector-all' is
+ specified.
- These '-m' switches are supported in addition to the above on x86-64
+
+ These `-m' switches are supported in addition to the above on x86-64
processors in 64-bit environments.
-'-m32'
-'-m64'
-'-mx32'
-'-m16'
+`-m32'
+`-m64'
+`-mx32'
+`-m16'
Generate code for a 16-bit, 32-bit or 64-bit environment. The
- '-m32' option sets 'int', 'long', and pointer types to 32 bits, and
+ `-m32' option sets `int', `long', and pointer types to 32 bits, and
generates code that runs on any i386 system.
- The '-m64' option sets 'int' to 32 bits and 'long' and pointer
+ The `-m64' option sets `int' to 32 bits and `long' and pointer
types to 64 bits, and generates code for the x86-64 architecture.
- For Darwin only the '-m64' option also turns off the '-fno-pic' and
- '-mdynamic-no-pic' options.
+ For Darwin only the `-m64' option also turns off the `-fno-pic'
+ and `-mdynamic-no-pic' options.
- The '-mx32' option sets 'int', 'long', and pointer types to 32
+ The `-mx32' option sets `int', `long', and pointer types to 32
bits, and generates code for the x86-64 architecture.
- The '-m16' option is the same as '-m32', except for that it outputs
- the '.code16gcc' assembly directive at the beginning of the
- assembly output so that the binary can run in 16-bit mode.
+ The `-m16' option is the same as `-m32', except for that it
+ outputs the `.code16gcc' assembly directive at the beginning of
+ the assembly output so that the binary can run in 16-bit mode.
-'-mno-red-zone'
- Do not use a so-called "red zone" for x86-64 code. The red zone is
- mandated by the x86-64 ABI; it is a 128-byte area beyond the
+`-mno-red-zone'
+ Do not use a so-called "red zone" for x86-64 code. The red zone
+ is mandated by the x86-64 ABI; it is a 128-byte area beyond the
location of the stack pointer that is not modified by signal or
interrupt handlers and therefore can be used for temporary data
- without adjusting the stack pointer. The flag '-mno-red-zone'
+ without adjusting the stack pointer. The flag `-mno-red-zone'
disables this red zone.
-'-mcmodel=small'
- Generate code for the small code model: the program and its symbols
- must be linked in the lower 2 GB of the address space. Pointers
- are 64 bits. Programs can be statically or dynamically linked.
- This is the default code model.
+`-mcmodel=small'
+ Generate code for the small code model: the program and its
+ symbols must be linked in the lower 2 GB of the address space.
+ Pointers are 64 bits. Programs can be statically or dynamically
+ linked. This is the default code model.
-'-mcmodel=kernel'
+`-mcmodel=kernel'
Generate code for the kernel code model. The kernel runs in the
negative 2 GB of the address space. This model has to be used for
Linux kernel code.
-'-mcmodel=medium'
+`-mcmodel=medium'
Generate code for the medium model: the program is linked in the
lower 2 GB of the address space. Small symbols are also placed
- there. Symbols with sizes larger than '-mlarge-data-threshold' are
- put into large data or BSS sections and can be located above 2GB.
- Programs can be statically or dynamically linked.
+ there. Symbols with sizes larger than `-mlarge-data-threshold'
+ are put into large data or BSS sections and can be located above
+ 2GB. Programs can be statically or dynamically linked.
-'-mcmodel=large'
+`-mcmodel=large'
Generate code for the large model. This model makes no assumptions
about addresses and sizes of sections.
-'-maddress-mode=long'
+`-maddress-mode=long'
Generate code for long address mode. This is only supported for
64-bit and x32 environments. It is the default address mode for
64-bit environments.
-'-maddress-mode=short'
+`-maddress-mode=short'
Generate code for short address mode. This is only supported for
32-bit and x32 environments. It is the default address mode for
32-bit and x32 environments.
@@ -21123,62 +21261,63 @@ File: gcc.info, Node: x86 Windows Options, Next: Xstormy16 Options, Prev: x86
These additional options are available for Microsoft Windows targets:
-'-mconsole'
+`-mconsole'
This option specifies that a console application is to be
- generated, by instructing the linker to set the PE header subsystem
- type required for console applications. This option is available
- for Cygwin and MinGW targets and is enabled by default on those
- targets.
+ generated, by instructing the linker to set the PE header
+ subsystem type required for console applications. This option is
+ available for Cygwin and MinGW targets and is enabled by default
+ on those targets.
-'-mdll'
+`-mdll'
This option is available for Cygwin and MinGW targets. It
specifies that a DLL--a dynamic link library--is to be generated,
enabling the selection of the required runtime startup object and
entry point.
-'-mnop-fun-dllimport'
+`-mnop-fun-dllimport'
This option is available for Cygwin and MinGW targets. It
- specifies that the 'dllimport' attribute should be ignored.
+ specifies that the `dllimport' attribute should be ignored.
-'-mthread'
- This option is available for MinGW targets. It specifies that
+`-mthread'
+ This option is available for MinGW targets. It specifies that
MinGW-specific thread support is to be used.
-'-municode'
+`-municode'
This option is available for MinGW-w64 targets. It causes the
- 'UNICODE' preprocessor macro to be predefined, and chooses
+ `UNICODE' preprocessor macro to be predefined, and chooses
Unicode-capable runtime startup code.
-'-mwin32'
+`-mwin32'
This option is available for Cygwin and MinGW targets. It
specifies that the typical Microsoft Windows predefined macros are
to be set in the pre-processor, but does not influence the choice
of runtime library/startup code.
-'-mwindows'
+`-mwindows'
This option is available for Cygwin and MinGW targets. It
specifies that a GUI application is to be generated by instructing
the linker to set the PE header subsystem type appropriately.
-'-fno-set-stack-executable'
- This option is available for MinGW targets. It specifies that the
+`-fno-set-stack-executable'
+ This option is available for MinGW targets. It specifies that the
executable flag for the stack used by nested functions isn't set.
This is necessary for binaries running in kernel mode of Microsoft
Windows, as there the User32 API, which is used to set executable
privileges, isn't available.
-'-fwritable-relocated-rdata'
+`-fwritable-relocated-rdata'
This option is available for MinGW and Cygwin targets. It
specifies that relocated-data in read-only section is put into
.data section. This is a necessary for older runtimes not
supporting modification of .rdata sections for pseudo-relocation.
-'-mpe-aligned-commons'
+`-mpe-aligned-commons'
This option is available for Cygwin and MinGW targets. It
- specifies that the GNU extension to the PE file format that permits
- the correct alignment of COMMON variables should be used when
- generating code. It is enabled by default if GCC detects that the
- target assembler found during configuration supports the feature.
+ specifies that the GNU extension to the PE file format that
+ permits the correct alignment of COMMON variables should be used
+ when generating code. It is enabled by default if GCC detects
+ that the target assembler found during configuration supports the
+ feature.
See also under *note x86 Options:: for standard options.
@@ -21190,7 +21329,7 @@ File: gcc.info, Node: Xstormy16 Options, Next: Xtensa Options, Prev: x86 Wind
These options are defined for Xstormy16:
-'-msim'
+`-msim'
Choose startup files and linker script suitable for the simulator.

@@ -21201,84 +21340,84 @@ File: gcc.info, Node: Xtensa Options, Next: zSeries Options, Prev: Xstormy16
These options are supported for Xtensa targets:
-'-mconst16'
-'-mno-const16'
- Enable or disable use of 'CONST16' instructions for loading
- constant values. The 'CONST16' instruction is currently not a
- standard option from Tensilica. When enabled, 'CONST16'
- instructions are always used in place of the standard 'L32R'
- instructions. The use of 'CONST16' is enabled by default only if
- the 'L32R' instruction is not available.
-
-'-mfused-madd'
-'-mno-fused-madd'
+`-mconst16'
+`-mno-const16'
+ Enable or disable use of `CONST16' instructions for loading
+ constant values. The `CONST16' instruction is currently not a
+ standard option from Tensilica. When enabled, `CONST16'
+ instructions are always used in place of the standard `L32R'
+ instructions. The use of `CONST16' is enabled by default only if
+ the `L32R' instruction is not available.
+
+`-mfused-madd'
+`-mno-fused-madd'
Enable or disable use of fused multiply/add and multiply/subtract
instructions in the floating-point option. This has no effect if
the floating-point option is not also enabled. Disabling fused
- multiply/add and multiply/subtract instructions forces the compiler
- to use separate instructions for the multiply and add/subtract
- operations. This may be desirable in some cases where strict IEEE
- 754-compliant results are required: the fused multiply add/subtract
- instructions do not round the intermediate result, thereby
- producing results with _more_ bits of precision than specified by
- the IEEE standard. Disabling fused multiply add/subtract
- instructions also ensures that the program output is not sensitive
- to the compiler's ability to combine multiply and add/subtract
- operations.
-
-'-mserialize-volatile'
-'-mno-serialize-volatile'
- When this option is enabled, GCC inserts 'MEMW' instructions before
- 'volatile' memory references to guarantee sequential consistency.
- The default is '-mserialize-volatile'. Use
- '-mno-serialize-volatile' to omit the 'MEMW' instructions.
-
-'-mforce-no-pic'
+ multiply/add and multiply/subtract instructions forces the
+ compiler to use separate instructions for the multiply and
+ add/subtract operations. This may be desirable in some cases
+ where strict IEEE 754-compliant results are required: the fused
+ multiply add/subtract instructions do not round the intermediate
+ result, thereby producing results with _more_ bits of precision
+ than specified by the IEEE standard. Disabling fused multiply
+ add/subtract instructions also ensures that the program output is
+ not sensitive to the compiler's ability to combine multiply and
+ add/subtract operations.
+
+`-mserialize-volatile'
+`-mno-serialize-volatile'
+ When this option is enabled, GCC inserts `MEMW' instructions before
+ `volatile' memory references to guarantee sequential consistency.
+ The default is `-mserialize-volatile'. Use
+ `-mno-serialize-volatile' to omit the `MEMW' instructions.
+
+`-mforce-no-pic'
For targets, like GNU/Linux, where all user-mode Xtensa code must
be position-independent code (PIC), this option disables PIC for
compiling kernel code.
-'-mtext-section-literals'
-'-mno-text-section-literals'
+`-mtext-section-literals'
+`-mno-text-section-literals'
These options control the treatment of literal pools. The default
- is '-mno-text-section-literals', which places literals in a
+ is `-mno-text-section-literals', which places literals in a
separate section in the output file. This allows the literal pool
to be placed in a data RAM/ROM, and it also allows the linker to
combine literal pools from separate object files to remove
redundant literals and improve code size. With
- '-mtext-section-literals', the literals are interspersed in the
+ `-mtext-section-literals', the literals are interspersed in the
text section in order to keep them as close as possible to their
references. This may be necessary for large assembly files.
-'-mtarget-align'
-'-mno-target-align'
+`-mtarget-align'
+`-mno-target-align'
When this option is enabled, GCC instructs the assembler to
automatically align instructions to reduce branch penalties at the
expense of some code density. The assembler attempts to widen
density instructions to align branch targets and the instructions
following call instructions. If there are not enough preceding
safe density instructions to align a target, no widening is
- performed. The default is '-mtarget-align'. These options do not
- affect the treatment of auto-aligned instructions like 'LOOP',
+ performed. The default is `-mtarget-align'. These options do not
+ affect the treatment of auto-aligned instructions like `LOOP',
which the assembler always aligns, either by widening density
instructions or by inserting NOP instructions.
-'-mlongcalls'
-'-mno-longcalls'
+`-mlongcalls'
+`-mno-longcalls'
When this option is enabled, GCC instructs the assembler to
translate direct calls to indirect calls unless it can determine
that the target of a direct call is in the range allowed by the
call instruction. This translation typically occurs for calls to
functions in other source files. Specifically, the assembler
- translates a direct 'CALL' instruction into an 'L32R' followed by a
- 'CALLX' instruction. The default is '-mno-longcalls'. This option
- should be used in programs where the call target can potentially be
- out of range. This option is implemented in the assembler, not the
- compiler, so the assembly code generated by GCC still shows direct
- call instructions--look at the disassembled object code to see the
- actual instructions. Note that the assembler uses an indirect call
- for every cross-file call, not just those that really are out of
- range.
+ translates a direct `CALL' instruction into an `L32R' followed by
+ a `CALLX' instruction. The default is `-mno-longcalls'. This
+ option should be used in programs where the call target can
+ potentially be out of range. This option is implemented in the
+ assembler, not the compiler, so the assembly code generated by GCC
+ still shows direct call instructions--look at the disassembled
+ object code to see the actual instructions. Note that the
+ assembler uses an indirect call for every cross-file call, not
+ just those that really are out of range.

File: gcc.info, Node: zSeries Options, Prev: Xtensa Options, Up: Submodel Options
@@ -21294,35 +21433,35 @@ File: gcc.info, Node: Code Gen Options, Next: Environment Variables, Prev: Su
3.18 Options for Code Generation Conventions
============================================
-These machine-independent options control the interface conventions used
-in code generation.
+These machine-independent options control the interface conventions
+used in code generation.
Most of them have both positive and negative forms; the negative form
-of '-ffoo' is '-fno-foo'. In the table below, only one of the forms is
+of `-ffoo' is `-fno-foo'. In the table below, only one of the forms is
listed--the one that is not the default. You can figure out the other
-form by either removing 'no-' or adding it.
+form by either removing `no-' or adding it.
-'-fbounds-check'
+`-fbounds-check'
For front ends that support it, generate additional code to check
that indices used to access arrays are within the declared range.
This is currently only supported by the Java and Fortran front
ends, where this option defaults to true and false respectively.
-'-fstack-reuse=REUSE-LEVEL'
- This option controls stack space reuse for user declared local/auto
- variables and compiler generated temporaries. REUSE_LEVEL can be
- 'all', 'named_vars', or 'none'. 'all' enables stack reuse for all
- local variables and temporaries, 'named_vars' enables the reuse
- only for user defined local variables with names, and 'none'
- disables stack reuse completely. The default value is 'all'. The
- option is needed when the program extends the lifetime of a scoped
- local variable or a compiler generated temporary beyond the end
- point defined by the language. When a lifetime of a variable ends,
- and if the variable lives in memory, the optimizing compiler has
- the freedom to reuse its stack space with other temporaries or
- scoped local variables whose live range does not overlap with it.
- Legacy code extending local lifetime is likely to break with the
- stack reuse optimization.
+`-fstack-reuse=REUSE-LEVEL'
+ This option controls stack space reuse for user declared
+ local/auto variables and compiler generated temporaries.
+ REUSE_LEVEL can be `all', `named_vars', or `none'. `all' enables
+ stack reuse for all local variables and temporaries, `named_vars'
+ enables the reuse only for user defined local variables with
+ names, and `none' disables stack reuse completely. The default
+ value is `all'. The option is needed when the program extends the
+ lifetime of a scoped local variable or a compiler generated
+ temporary beyond the end point defined by the language. When a
+ lifetime of a variable ends, and if the variable lives in memory,
+ the optimizing compiler has the freedom to reuse its stack space
+ with other temporaries or scoped local variables whose live range
+ does not overlap with it. Legacy code extending local lifetime is
+ likely to break with the stack reuse optimization.
For example,
@@ -21373,22 +21512,21 @@ form by either removing 'no-' or adding it.
// is reused with a. What is the value of ap->i?
}
-
The lifetime of a compiler generated temporary is well defined by
- the C++ standard. When a lifetime of a temporary ends, and if the
+ the C++ standard. When a lifetime of a temporary ends, and if the
temporary lives in memory, the optimizing compiler has the freedom
to reuse its stack space with other temporaries or scoped local
- variables whose live range does not overlap with it. However some
+ variables whose live range does not overlap with it. However some
of the legacy code relies on the behavior of older compilers in
which temporaries' stack space is not reused, the aggressive stack
- reuse can lead to runtime errors. This option is used to control
+ reuse can lead to runtime errors. This option is used to control
the temporary stack reuse optimization.
-'-ftrapv'
+`-ftrapv'
This option generates traps for signed overflow on addition,
subtraction, multiplication operations.
-'-fwrapv'
+`-fwrapv'
This option instructs the compiler to assume that signed arithmetic
overflow of addition, subtraction and multiplication wraps around
using twos-complement representation. This flag enables some
@@ -21396,29 +21534,30 @@ form by either removing 'no-' or adding it.
default for the Java front end, as required by the Java language
specification.
-'-fexceptions'
+`-fexceptions'
Enable exception handling. Generates extra code needed to
- propagate exceptions. For some targets, this implies GCC generates
- frame unwind information for all functions, which can produce
- significant data size overhead, although it does not affect
- execution. If you do not specify this option, GCC enables it by
- default for languages like C++ that normally require exception
- handling, and disables it for languages like C that do not normally
- require it. However, you may need to enable this option when
- compiling C code that needs to interoperate properly with exception
- handlers written in C++. You may also wish to disable this option
- if you are compiling older C++ programs that don't use exception
- handling.
-
-'-fnon-call-exceptions'
+ propagate exceptions. For some targets, this implies GCC
+ generates frame unwind information for all functions, which can
+ produce significant data size overhead, although it does not
+ affect execution. If you do not specify this option, GCC enables
+ it by default for languages like C++ that normally require
+ exception handling, and disables it for languages like C that do
+ not normally require it. However, you may need to enable this
+ option when compiling C code that needs to interoperate properly
+ with exception handlers written in C++. You may also wish to
+ disable this option if you are compiling older C++ programs that
+ don't use exception handling.
+
+`-fnon-call-exceptions'
Generate code that allows trapping instructions to throw
exceptions. Note that this requires platform-specific runtime
support that does not exist everywhere. Moreover, it only allows
- _trapping_ instructions to throw exceptions, i.e. memory references
- or floating-point instructions. It does not allow exceptions to be
- thrown from arbitrary signal handlers such as 'SIGALRM'.
+ _trapping_ instructions to throw exceptions, i.e. memory
+ references or floating-point instructions. It does not allow
+ exceptions to be thrown from arbitrary signal handlers such as
+ `SIGALRM'.
-'-fdelete-dead-exceptions'
+`-fdelete-dead-exceptions'
Consider that instructions that may throw exceptions but don't
otherwise contribute to the execution of the program can be
optimized away. This option is enabled by default for the Ada
@@ -21426,38 +21565,38 @@ form by either removing 'no-' or adding it.
Optimization passes that cause dead exceptions to be removed are
enabled independently at different optimization levels.
-'-funwind-tables'
- Similar to '-fexceptions', except that it just generates any needed
+`-funwind-tables'
+ Similar to `-fexceptions', except that it just generates any needed
static data, but does not affect the generated code in any other
way. You normally do not need to enable this option; instead, a
language processor that needs this handling enables it on your
behalf.
-'-fasynchronous-unwind-tables'
+`-fasynchronous-unwind-tables'
Generate unwind table in DWARF 2 format, if supported by target
machine. The table is exact at each instruction boundary, so it
can be used for stack unwinding from asynchronous events (such as
debugger or garbage collector).
-'-fno-gnu-unique'
+`-fno-gnu-unique'
On systems with recent GNU assembler and C library, the C++
- compiler uses the 'STB_GNU_UNIQUE' binding to make sure that
+ compiler uses the `STB_GNU_UNIQUE' binding to make sure that
definitions of template static data members and static local
variables in inline functions are unique even in the presence of
- 'RTLD_LOCAL'; this is necessary to avoid problems with a library
- used by two different 'RTLD_LOCAL' plugins depending on a
+ `RTLD_LOCAL'; this is necessary to avoid problems with a library
+ used by two different `RTLD_LOCAL' plugins depending on a
definition in one of them and therefore disagreeing with the other
- one about the binding of the symbol. But this causes 'dlclose' to
+ one about the binding of the symbol. But this causes `dlclose' to
be ignored for affected DSOs; if your program relies on
- reinitialization of a DSO via 'dlclose' and 'dlopen', you can use
- '-fno-gnu-unique'.
+ reinitialization of a DSO via `dlclose' and `dlopen', you can use
+ `-fno-gnu-unique'.
-'-fpcc-struct-return'
- Return "short" 'struct' and 'union' values in memory like longer
- ones, rather than in registers. This convention is less efficient,
- but it has the advantage of allowing intercallability between
- GCC-compiled files and files compiled with other compilers,
- particularly the Portable C Compiler (pcc).
+`-fpcc-struct-return'
+ Return "short" `struct' and `union' values in memory like longer
+ ones, rather than in registers. This convention is less
+ efficient, but it has the advantage of allowing intercallability
+ between GCC-compiled files and files compiled with other
+ compilers, particularly the Portable C Compiler (pcc).
The precise convention for returning structures in memory depends
on the target configuration macros.
@@ -21465,108 +21604,109 @@ form by either removing 'no-' or adding it.
Short structures and unions are those whose size and alignment
match that of some integer type.
- *Warning:* code compiled with the '-fpcc-struct-return' switch is
+ *Warning:* code compiled with the `-fpcc-struct-return' switch is
not binary compatible with code compiled with the
- '-freg-struct-return' switch. Use it to conform to a non-default
+ `-freg-struct-return' switch. Use it to conform to a non-default
application binary interface.
-'-freg-struct-return'
- Return 'struct' and 'union' values in registers when possible.
+`-freg-struct-return'
+ Return `struct' and `union' values in registers when possible.
This is more efficient for small structures than
- '-fpcc-struct-return'.
+ `-fpcc-struct-return'.
- If you specify neither '-fpcc-struct-return' nor
- '-freg-struct-return', GCC defaults to whichever convention is
+ If you specify neither `-fpcc-struct-return' nor
+ `-freg-struct-return', GCC defaults to whichever convention is
standard for the target. If there is no standard convention, GCC
- defaults to '-fpcc-struct-return', except on targets where GCC is
+ defaults to `-fpcc-struct-return', except on targets where GCC is
the principal compiler. In those cases, we can choose the
standard, and we chose the more efficient register return
alternative.
- *Warning:* code compiled with the '-freg-struct-return' switch is
+ *Warning:* code compiled with the `-freg-struct-return' switch is
not binary compatible with code compiled with the
- '-fpcc-struct-return' switch. Use it to conform to a non-default
+ `-fpcc-struct-return' switch. Use it to conform to a non-default
application binary interface.
-'-fshort-enums'
- Allocate to an 'enum' type only as many bytes as it needs for the
- declared range of possible values. Specifically, the 'enum' type
+`-fshort-enums'
+ Allocate to an `enum' type only as many bytes as it needs for the
+ declared range of possible values. Specifically, the `enum' type
is equivalent to the smallest integer type that has enough room.
- *Warning:* the '-fshort-enums' switch causes GCC to generate code
+ *Warning:* the `-fshort-enums' switch causes GCC to generate code
that is not binary compatible with code generated without that
switch. Use it to conform to a non-default application binary
interface.
-'-fshort-double'
- Use the same size for 'double' as for 'float'.
+`-fshort-double'
+ Use the same size for `double' as for `float'.
- *Warning:* the '-fshort-double' switch causes GCC to generate code
+ *Warning:* the `-fshort-double' switch causes GCC to generate code
that is not binary compatible with code generated without that
switch. Use it to conform to a non-default application binary
interface.
-'-fshort-wchar'
- Override the underlying type for 'wchar_t' to be 'short unsigned
+`-fshort-wchar'
+ Override the underlying type for `wchar_t' to be `short unsigned
int' instead of the default for the target. This option is useful
for building programs to run under WINE.
- *Warning:* the '-fshort-wchar' switch causes GCC to generate code
+ *Warning:* the `-fshort-wchar' switch causes GCC to generate code
that is not binary compatible with code generated without that
switch. Use it to conform to a non-default application binary
interface.
-'-fno-common'
+`-fno-common'
In C code, controls the placement of uninitialized global
variables. Unix C compilers have traditionally permitted multiple
definitions of such variables in different compilation units by
placing the variables in a common block. This is the behavior
- specified by '-fcommon', and is the default for GCC on most
+ specified by `-fcommon', and is the default for GCC on most
targets. On the other hand, this behavior is not required by ISO
C, and on some targets may carry a speed or code size penalty on
- variable references. The '-fno-common' option specifies that the
+ variable references. The `-fno-common' option specifies that the
compiler should place uninitialized global variables in the data
section of the object file, rather than generating them as common
blocks. This has the effect that if the same variable is declared
- (without 'extern') in two different compilations, you get a
+ (without `extern') in two different compilations, you get a
multiple-definition error when you link them. In this case, you
- must compile with '-fcommon' instead. Compiling with '-fno-common'
- is useful on targets for which it provides better performance, or
- if you wish to verify that the program will work on other systems
- that always treat uninitialized variable declarations this way.
+ must compile with `-fcommon' instead. Compiling with
+ `-fno-common' is useful on targets for which it provides better
+ performance, or if you wish to verify that the program will work
+ on other systems that always treat uninitialized variable
+ declarations this way.
-'-fno-ident'
- Ignore the '#ident' directive.
+`-fno-ident'
+ Ignore the `#ident' directive.
-'-finhibit-size-directive'
- Don't output a '.size' assembler directive, or anything else that
+`-finhibit-size-directive'
+ Don't output a `.size' assembler directive, or anything else that
would cause trouble if the function is split in the middle, and the
two halves are placed at locations far apart in memory. This
- option is used when compiling 'crtstuff.c'; you should not need to
+ option is used when compiling `crtstuff.c'; you should not need to
use it for anything else.
-'-fverbose-asm'
+`-fverbose-asm'
Put extra commentary information in the generated assembly code to
make it more readable. This option is generally only of use to
those who actually need to read the generated assembly code
(perhaps while debugging the compiler itself).
- '-fno-verbose-asm', the default, causes the extra information to be
- omitted and is useful when comparing two assembler files.
+ `-fno-verbose-asm', the default, causes the extra information to
+ be omitted and is useful when comparing two assembler files.
-'-frecord-gcc-switches'
+`-frecord-gcc-switches'
This switch causes the command line used to invoke the compiler to
be recorded into the object file that is being created. This
switch is only implemented on some targets and the exact format of
the recording is target and binary file format dependent, but it
usually takes the form of a section containing ASCII text. This
- switch is related to the '-fverbose-asm' switch, but that switch
+ switch is related to the `-fverbose-asm' switch, but that switch
only records information in the assembler output file as comments,
so it never reaches the object file. See also
- '-grecord-gcc-switches' for another way of storing compiler options
- into the object file.
+ `-grecord-gcc-switches' for another way of storing compiler
+ options into the object file.
-'-fpic'
+`-fpic'
Generate position-independent code (PIC) suitable for use in a
shared library, if supported for the target machine. Such code
accesses all constant addresses through a global offset table
@@ -21574,8 +21714,8 @@ form by either removing 'no-' or adding it.
program starts (the dynamic loader is not part of GCC; it is part
of the operating system). If the GOT size for the linked
executable exceeds a machine-specific maximum size, you get an
- error message from the linker indicating that '-fpic' does not
- work; in that case, recompile with '-fPIC' instead. (These
+ error message from the linker indicating that `-fpic' does not
+ work; in that case, recompile with `-fPIC' instead. (These
maximums are 8k on the SPARC and 32k on the m68k and RS/6000. The
x86 has no such limit.)
@@ -21584,52 +21724,53 @@ form by either removing 'no-' or adding it.
System V but not for the Sun 386i. Code generated for the IBM
RS/6000 is always position-independent.
- When this flag is set, the macros '__pic__' and '__PIC__' are
+ When this flag is set, the macros `__pic__' and `__PIC__' are
defined to 1.
-'-fPIC'
+`-fPIC'
If supported for the target machine, emit position-independent
code, suitable for dynamic linking and avoiding any limit on the
- size of the global offset table. This option makes a difference on
- the m68k, PowerPC and SPARC.
+ size of the global offset table. This option makes a difference
+ on the m68k, PowerPC and SPARC.
Position-independent code requires special support, and therefore
works only on certain machines.
- When this flag is set, the macros '__pic__' and '__PIC__' are
+ When this flag is set, the macros `__pic__' and `__PIC__' are
defined to 2.
-'-fpie'
-'-fPIE'
- These options are similar to '-fpic' and '-fPIC', but generated
+`-fpie'
+`-fPIE'
+ These options are similar to `-fpic' and `-fPIC', but generated
position independent code can be only linked into executables.
- Usually these options are used when '-pie' GCC option is used
+ Usually these options are used when `-pie' GCC option is used
during linking.
- '-fpie' and '-fPIE' both define the macros '__pie__' and '__PIE__'.
- The macros have the value 1 for '-fpie' and 2 for '-fPIE'.
+ `-fpie' and `-fPIE' both define the macros `__pie__' and
+ `__PIE__'. The macros have the value 1 for `-fpie' and 2 for
+ `-fPIE'.
-'-fno-jump-tables'
+`-fno-jump-tables'
Do not use jump tables for switch statements even where it would be
more efficient than other code generation strategies. This option
- is of use in conjunction with '-fpic' or '-fPIC' for building code
+ is of use in conjunction with `-fpic' or `-fPIC' for building code
that forms part of a dynamic linker and cannot reference the
address of a jump table. On some targets, jump tables do not
require a GOT and this option is not needed.
-'-ffixed-REG'
+`-ffixed-REG'
Treat the register named REG as a fixed register; generated code
should never refer to it (except perhaps as a stack pointer, frame
pointer or in some other fixed role).
REG must be the name of a register. The register names accepted
- are machine-specific and are defined in the 'REGISTER_NAMES' macro
+ are machine-specific and are defined in the `REGISTER_NAMES' macro
in the machine description macro file.
This flag does not have a negative form, because it specifies a
three-way choice.
-'-fcall-used-REG'
+`-fcall-used-REG'
Treat the register named REG as an allocable register that is
clobbered by function calls. It may be allocated for temporaries
or variables that do not live across a call. Functions compiled
@@ -21643,7 +21784,7 @@ form by either removing 'no-' or adding it.
This flag does not have a negative form, because it specifies a
three-way choice.
-'-fcall-saved-REG'
+`-fcall-saved-REG'
Treat the register named REG as an allocable register saved by
functions. It may be allocated even for temporaries or variables
that live across a call. Functions compiled this way save and
@@ -21660,7 +21801,7 @@ form by either removing 'no-' or adding it.
This flag does not have a negative form, because it specifies a
three-way choice.
-'-fpack-struct[=N]'
+`-fpack-struct[=N]'
Without a value specified, pack all structure members together
without holes. When a value is specified (which must be a small
power of two), pack structure members according to this value,
@@ -21668,17 +21809,17 @@ form by either removing 'no-' or adding it.
alignment requirements larger than this are output potentially
unaligned at the next fitting location.
- *Warning:* the '-fpack-struct' switch causes GCC to generate code
+ *Warning:* the `-fpack-struct' switch causes GCC to generate code
that is not binary compatible with code generated without that
switch. Additionally, it makes the code suboptimal. Use it to
conform to a non-default application binary interface.
-'-finstrument-functions'
+`-finstrument-functions'
Generate instrumentation calls for entry and exit to functions.
Just after function entry and just before function exit, the
following profiling functions are called with the address of the
current function and its call site. (On some platforms,
- '__builtin_return_address' does not work beyond the current
+ `__builtin_return_address' does not work beyond the current
function, so the call site information may not be available to the
profiling functions otherwise.)
@@ -21691,27 +21832,27 @@ form by either removing 'no-' or adding it.
function, which may be looked up exactly in the symbol table.
This instrumentation is also done for functions expanded inline in
- other functions. The profiling calls indicate where, conceptually,
- the inline function is entered and exited. This means that
- addressable versions of such functions must be available. If all
- your uses of a function are expanded inline, this may mean an
- additional expansion of code size. If you use 'extern inline' in
- your C code, an addressable version of such functions must be
- provided. (This is normally the case anyway, but if you get lucky
- and the optimizer always expands the functions inline, you might
- have gotten away without providing static copies.)
-
- A function may be given the attribute 'no_instrument_function', in
+ other functions. The profiling calls indicate where,
+ conceptually, the inline function is entered and exited. This
+ means that addressable versions of such functions must be
+ available. If all your uses of a function are expanded inline,
+ this may mean an additional expansion of code size. If you use
+ `extern inline' in your C code, an addressable version of such
+ functions must be provided. (This is normally the case anyway,
+ but if you get lucky and the optimizer always expands the
+ functions inline, you might have gotten away without providing
+ static copies.)
+
+ A function may be given the attribute `no_instrument_function', in
which case this instrumentation is not done. This can be used, for
example, for the profiling functions listed above, high-priority
interrupt routines, and any functions from which the profiling
functions cannot safely be called (perhaps signal handlers, if the
profiling routines generate output or allocate memory).
-'-finstrument-functions-exclude-file-list=FILE,FILE,...'
-
+`-finstrument-functions-exclude-file-list=FILE,FILE,...'
Set the list of functions that are excluded from instrumentation
- (see the description of '-finstrument-functions'). If the file
+ (see the description of `-finstrument-functions'). If the file
that contains a function definition matches with one of FILE, then
that function is not instrumented. The match is done on
substrings: if the FILE parameter is a substring of the file name,
@@ -21722,42 +21863,42 @@ form by either removing 'no-' or adding it.
-finstrument-functions-exclude-file-list=/bits/stl,include/sys
excludes any inline function defined in files whose pathnames
- contain '/bits/stl' or 'include/sys'.
+ contain `/bits/stl' or `include/sys'.
- If, for some reason, you want to include letter ',' in one of SYM,
- write '\,'. For example,
- '-finstrument-functions-exclude-file-list='\,\,tmp'' (note the
+ If, for some reason, you want to include letter `,' in one of SYM,
+ write `\,'. For example,
+ `-finstrument-functions-exclude-file-list='\,\,tmp'' (note the
single quote surrounding the option).
-'-finstrument-functions-exclude-function-list=SYM,SYM,...'
-
- This is similar to '-finstrument-functions-exclude-file-list', but
+`-finstrument-functions-exclude-function-list=SYM,SYM,...'
+ This is similar to `-finstrument-functions-exclude-file-list', but
this option sets the list of function names to be excluded from
instrumentation. The function name to be matched is its
- user-visible name, such as 'vector<int> blah(const vector<int> &)',
- not the internal mangled name (e.g., '_Z4blahRSt6vectorIiSaIiEE').
- The match is done on substrings: if the SYM parameter is a
- substring of the function name, it is considered to be a match.
- For C99 and C++ extended identifiers, the function name must be
- given in UTF-8, not using universal character names.
-
-'-fstack-check'
+ user-visible name, such as `vector<int> blah(const vector<int>
+ &)', not the internal mangled name (e.g.,
+ `_Z4blahRSt6vectorIiSaIiEE'). The match is done on substrings: if
+ the SYM parameter is a substring of the function name, it is
+ considered to be a match. For C99 and C++ extended identifiers,
+ the function name must be given in UTF-8, not using universal
+ character names.
+
+`-fstack-check'
Generate code to verify that you do not go beyond the boundary of
the stack. You should specify this flag if you are running in an
environment with multiple threads, but you only rarely need to
- specify it in a single-threaded environment since stack overflow is
- automatically detected on nearly all systems if there is only one
- stack.
+ specify it in a single-threaded environment since stack overflow
+ is automatically detected on nearly all systems if there is only
+ one stack.
Note that this switch does not actually cause checking to be done;
the operating system or the language runtime must do that. The
switch causes generation of code to ensure that they see the stack
being extended.
- You can additionally specify a string parameter: 'no' means no
- checking, 'generic' means force the use of old-style checking,
- 'specific' means use the best checking method and is equivalent to
- bare '-fstack-check'.
+ You can additionally specify a string parameter: `no' means no
+ checking, `generic' means force the use of old-style checking,
+ `specific' means use the best checking method and is equivalent to
+ bare `-fstack-check'.
Old-style checking is a generic mechanism that requires no specific
target support in the compiler but comes with the following
@@ -21767,19 +21908,20 @@ form by either removing 'no-' or adding it.
always allocated dynamically if their size exceeds a fixed
threshold.
- 2. Fixed limit on the size of the static frame of functions: when
- it is topped by a particular function, stack checking is not
- reliable and a warning is issued by the compiler.
+ 2. Fixed limit on the size of the static frame of functions:
+ when it is topped by a particular function, stack checking is
+ not reliable and a warning is issued by the compiler.
- 3. Inefficiency: because of both the modified allocation strategy
- and the generic implementation, code performance is hampered.
+ 3. Inefficiency: because of both the modified allocation
+ strategy and the generic implementation, code performance is
+ hampered.
Note that old-style stack checking is also the fallback method for
- 'specific' if no target support has been added in the compiler.
+ `specific' if no target support has been added in the compiler.
-'-fstack-limit-register=REG'
-'-fstack-limit-symbol=SYM'
-'-fno-stack-limit'
+`-fstack-limit-register=REG'
+`-fstack-limit-symbol=SYM'
+`-fno-stack-limit'
Generate code to ensure that the stack does not grow beyond a
certain value, either the value of a register or the address of a
symbol. If a larger stack is required, a signal is raised at run
@@ -21787,13 +21929,13 @@ form by either removing 'no-' or adding it.
overruns the boundary, so it is possible to catch the signal
without taking special precautions.
- For instance, if the stack starts at absolute address '0x80000000'
+ For instance, if the stack starts at absolute address `0x80000000'
and grows downwards, you can use the flags
- '-fstack-limit-symbol=__stack_limit' and
- '-Wl,--defsym,__stack_limit=0x7ffe0000' to enforce a stack limit of
- 128KB. Note that this may only work with the GNU linker.
+ `-fstack-limit-symbol=__stack_limit' and
+ `-Wl,--defsym,__stack_limit=0x7ffe0000' to enforce a stack limit
+ of 128KB. Note that this may only work with the GNU linker.
-'-fsplit-stack'
+`-fsplit-stack'
Generate code to automatically split the stack before it overflows.
The resulting program has a discontiguous stack which can only
overflow if the program is unable to allocate any more memory.
@@ -21802,38 +21944,38 @@ form by either removing 'no-' or adding it.
thread. This is currently only implemented for the x86 targets
running GNU/Linux.
- When code compiled with '-fsplit-stack' calls code compiled without
- '-fsplit-stack', there may not be much stack space available for
- the latter code to run. If compiling all code, including library
- code, with '-fsplit-stack' is not an option, then the linker can
- fix up these calls so that the code compiled without
- '-fsplit-stack' always has a large stack. Support for this is
- implemented in the gold linker in GNU binutils release 2.21 and
- later.
-
-'-fleading-underscore'
- This option and its counterpart, '-fno-leading-underscore',
+ When code compiled with `-fsplit-stack' calls code compiled
+ without `-fsplit-stack', there may not be much stack space
+ available for the latter code to run. If compiling all code,
+ including library code, with `-fsplit-stack' is not an option,
+ then the linker can fix up these calls so that the code compiled
+ without `-fsplit-stack' always has a large stack. Support for
+ this is implemented in the gold linker in GNU binutils release 2.21
+ and later.
+
+`-fleading-underscore'
+ This option and its counterpart, `-fno-leading-underscore',
forcibly change the way C symbols are represented in the object
file. One use is to help link with legacy assembly code.
- *Warning:* the '-fleading-underscore' switch causes GCC to generate
- code that is not binary compatible with code generated without that
- switch. Use it to conform to a non-default application binary
- interface. Not all targets provide complete support for this
- switch.
+ *Warning:* the `-fleading-underscore' switch causes GCC to
+ generate code that is not binary compatible with code generated
+ without that switch. Use it to conform to a non-default
+ application binary interface. Not all targets provide complete
+ support for this switch.
-'-ftls-model=MODEL'
+`-ftls-model=MODEL'
Alter the thread-local storage model to be used (*note
Thread-Local::). The MODEL argument should be one of
- 'global-dynamic', 'local-dynamic', 'initial-exec' or 'local-exec'.
+ `global-dynamic', `local-dynamic', `initial-exec' or `local-exec'.
Note that the choice is subject to optimization: the compiler may
use a more efficient model for symbols not visible outside of the
- translation unit, or if '-fpic' is not given on the command line.
+ translation unit, or if `-fpic' is not given on the command line.
- The default without '-fpic' is 'initial-exec'; with '-fpic' the
- default is 'global-dynamic'.
+ The default without `-fpic' is `initial-exec'; with `-fpic' the
+ default is `global-dynamic'.
-'-fvisibility=[default|internal|hidden|protected]'
+`-fvisibility=[default|internal|hidden|protected]'
Set the default ELF image symbol visibility to the specified
option--all symbols are marked with this unless overridden within
the code. Using this feature can very substantially improve
@@ -21842,29 +21984,29 @@ form by either removing 'no-' or adding it.
clashes. It is *strongly* recommended that you use this in any
shared objects you distribute.
- Despite the nomenclature, 'default' always means public; i.e.,
+ Despite the nomenclature, `default' always means public; i.e.,
available to be linked against from outside the shared object.
- 'protected' and 'internal' are pretty useless in real-world usage
- so the only other commonly used option is 'hidden'. The default if
- '-fvisibility' isn't specified is 'default', i.e., make every
+ `protected' and `internal' are pretty useless in real-world usage
+ so the only other commonly used option is `hidden'. The default
+ if `-fvisibility' isn't specified is `default', i.e., make every
symbol public.
A good explanation of the benefits offered by ensuring ELF symbols
have the correct visibility is given by "How To Write Shared
Libraries" by Ulrich Drepper (which can be found at
- <http://www.akkadia.org/drepper/>)--however a superior solution
+ `http://www.akkadia.org/drepper/')--however a superior solution
made possible by this option to marking things hidden when the
default is public is to make the default hidden and mark things
public. This is the norm with DLLs on Windows and with
- '-fvisibility=hidden' and '__attribute__ ((visibility("default")))'
- instead of '__declspec(dllexport)' you get almost identical
- semantics with identical syntax. This is a great boon to those
- working with cross-platform projects.
+ `-fvisibility=hidden' and `__attribute__
+ ((visibility("default")))' instead of `__declspec(dllexport)' you
+ get almost identical semantics with identical syntax. This is a
+ great boon to those working with cross-platform projects.
For those adding visibility support to existing code, you may find
- '#pragma GCC visibility' of use. This works by you enclosing the
+ `#pragma GCC visibility' of use. This works by you enclosing the
declarations you wish to set visibility for with (for example)
- '#pragma GCC visibility push(hidden)' and '#pragma GCC visibility
+ `#pragma GCC visibility push(hidden)' and `#pragma GCC visibility
pop'. Bear in mind that symbol visibility should be viewed *as
part of the API interface contract* and thus all new code should
always specify visibility when it is not the default; i.e.,
@@ -21872,41 +22014,43 @@ form by either removing 'no-' or adding it.
marked explicitly as hidden as so to avoid PLT indirection
overheads--making this abundantly clear also aids readability and
self-documentation of the code. Note that due to ISO C++
- specification requirements, 'operator new' and 'operator delete'
+ specification requirements, `operator new' and `operator delete'
must always be of default visibility.
Be aware that headers from outside your project, in particular
system headers and headers from any other library you use, may not
- be expecting to be compiled with visibility other than the default.
- You may need to explicitly say '#pragma GCC visibility
+ be expecting to be compiled with visibility other than the
+ default. You may need to explicitly say `#pragma GCC visibility
push(default)' before including any such headers.
- 'extern' declarations are not affected by '-fvisibility', so a lot
- of code can be recompiled with '-fvisibility=hidden' with no
- modifications. However, this means that calls to 'extern'
+ `extern' declarations are not affected by `-fvisibility', so a lot
+ of code can be recompiled with `-fvisibility=hidden' with no
+ modifications. However, this means that calls to `extern'
functions with no explicit visibility use the PLT, so it is more
- effective to use '__attribute ((visibility))' and/or '#pragma GCC
- visibility' to tell the compiler which 'extern' declarations should
- be treated as hidden.
+ effective to use `__attribute ((visibility))' and/or `#pragma GCC
+ visibility' to tell the compiler which `extern' declarations
+ should be treated as hidden.
- Note that '-fvisibility' does affect C++ vague linkage entities.
- This means that, for instance, an exception class that is be thrown
- between DSOs must be explicitly marked with default visibility so
- that the 'type_info' nodes are unified between the DSOs.
+ Note that `-fvisibility' does affect C++ vague linkage entities.
+ This means that, for instance, an exception class that is be
+ thrown between DSOs must be explicitly marked with default
+ visibility so that the `type_info' nodes are unified between the
+ DSOs.
An overview of these techniques, their benefits and how to use them
- is at <http://gcc.gnu.org/wiki/Visibility>.
+ is at `http://gcc.gnu.org/wiki/Visibility'.
-'-fstrict-volatile-bitfields'
+`-fstrict-volatile-bitfields'
This option should be used if accesses to volatile bit-fields (or
other structure fields, although the compiler usually honors those
types anyway) should use a single access of the width of the
field's type, aligned to a natural alignment if possible. For
example, targets with memory-mapped peripheral registers might
require all such accesses to be 16 bits wide; with this flag you
- can declare all peripheral bit-fields as 'unsigned short' (assuming
- short is 16 bits on these targets) to force GCC to use 16-bit
- accesses instead of, perhaps, a more efficient 32-bit access.
+ can declare all peripheral bit-fields as `unsigned short'
+ (assuming short is 16 bits on these targets) to force GCC to use
+ 16-bit accesses instead of, perhaps, a more efficient 32-bit
+ access.
If this option is disabled, the compiler uses the most efficient
instruction. In the previous example, that might be a 32-bit load
@@ -21914,14 +22058,14 @@ form by either removing 'no-' or adding it.
any portion of the bit-field, or memory-mapped registers unrelated
to the one being updated.
- In some cases, such as when the 'packed' attribute is applied to a
+ In some cases, such as when the `packed' attribute is applied to a
structure field, it may not be possible to access the field with a
single read or write that is correctly aligned for the target
machine. In this case GCC falls back to generating multiple
- accesses rather than code that will fault or truncate the result at
- run time.
+ accesses rather than code that will fault or truncate the result
+ at run time.
- Note: Due to restrictions of the C/C++11 memory model, write
+ Note: Due to restrictions of the C/C++11 memory model, write
accesses are not allowed to touch non bit-field members. It is
therefore recommended to define all bits of the field's type as
bit-field members.
@@ -21929,14 +22073,15 @@ form by either removing 'no-' or adding it.
The default value of this option is determined by the application
binary interface for the target processor.
-'-fsync-libcalls'
+`-fsync-libcalls'
This option controls whether any out-of-line instance of the
- '__sync' family of functions may be used to implement the C++11
- '__atomic' family of functions.
+ `__sync' family of functions may be used to implement the C++11
+ `__atomic' family of functions.
The default value of this option is enabled, thus the only useful
- form of the option is '-fno-sync-libcalls'. This option is used in
- the implementation of the 'libatomic' runtime library.
+ form of the option is `-fno-sync-libcalls'. This option is used in
+ the implementation of the `libatomic' runtime library.
+

File: gcc.info, Node: Environment Variables, Next: Precompiled Headers, Prev: Code Gen Options, Up: Invoking GCC
@@ -21946,173 +22091,175 @@ File: gcc.info, Node: Environment Variables, Next: Precompiled Headers, Prev:
This section describes several environment variables that affect how GCC
operates. Some of them work by specifying directories or prefixes to
-use when searching for various kinds of files. Some are used to specify
-other aspects of the compilation environment.
+use when searching for various kinds of files. Some are used to
+specify other aspects of the compilation environment.
Note that you can also specify places to search using options such as
-'-B', '-I' and '-L' (*note Directory Options::). These take precedence
+`-B', `-I' and `-L' (*note Directory Options::). These take precedence
over places specified using environment variables, which in turn take
precedence over those specified by the configuration of GCC. *Note
-Controlling the Compilation Driver 'gcc': (gccint)Driver.
+Controlling the Compilation Driver `gcc': (gccint)Driver.
-'LANG'
-'LC_CTYPE'
-'LC_MESSAGES'
-'LC_ALL'
+`LANG'
+`LC_CTYPE'
+`LC_MESSAGES'
+`LC_ALL'
These environment variables control the way that GCC uses
localization information which allows GCC to work with different
national conventions. GCC inspects the locale categories
- 'LC_CTYPE' and 'LC_MESSAGES' if it has been configured to do so.
+ `LC_CTYPE' and `LC_MESSAGES' if it has been configured to do so.
These locale categories can be set to any value supported by your
- installation. A typical value is 'en_GB.UTF-8' for English in the
+ installation. A typical value is `en_GB.UTF-8' for English in the
United Kingdom encoded in UTF-8.
- The 'LC_CTYPE' environment variable specifies character
+ The `LC_CTYPE' environment variable specifies character
classification. GCC uses it to determine the character boundaries
in a string; this is needed for some multibyte encodings that
contain quote and escape characters that are otherwise interpreted
as a string end or escape.
- The 'LC_MESSAGES' environment variable specifies the language to
+ The `LC_MESSAGES' environment variable specifies the language to
use in diagnostic messages.
- If the 'LC_ALL' environment variable is set, it overrides the value
- of 'LC_CTYPE' and 'LC_MESSAGES'; otherwise, 'LC_CTYPE' and
- 'LC_MESSAGES' default to the value of the 'LANG' environment
+ If the `LC_ALL' environment variable is set, it overrides the value
+ of `LC_CTYPE' and `LC_MESSAGES'; otherwise, `LC_CTYPE' and
+ `LC_MESSAGES' default to the value of the `LANG' environment
variable. If none of these variables are set, GCC defaults to
traditional C English behavior.
-'TMPDIR'
- If 'TMPDIR' is set, it specifies the directory to use for temporary
+`TMPDIR'
+ If `TMPDIR' is set, it specifies the directory to use for temporary
files. GCC uses temporary files to hold the output of one stage of
compilation which is to be used as input to the next stage: for
example, the output of the preprocessor, which is the input to the
compiler proper.
-'GCC_COMPARE_DEBUG'
- Setting 'GCC_COMPARE_DEBUG' is nearly equivalent to passing
- '-fcompare-debug' to the compiler driver. See the documentation of
- this option for more details.
+`GCC_COMPARE_DEBUG'
+ Setting `GCC_COMPARE_DEBUG' is nearly equivalent to passing
+ `-fcompare-debug' to the compiler driver. See the documentation
+ of this option for more details.
-'GCC_EXEC_PREFIX'
- If 'GCC_EXEC_PREFIX' is set, it specifies a prefix to use in the
+`GCC_EXEC_PREFIX'
+ If `GCC_EXEC_PREFIX' is set, it specifies a prefix to use in the
names of the subprograms executed by the compiler. No slash is
added when this prefix is combined with the name of a subprogram,
but you can specify a prefix that ends with a slash if you wish.
- If 'GCC_EXEC_PREFIX' is not set, GCC attempts to figure out an
+ If `GCC_EXEC_PREFIX' is not set, GCC attempts to figure out an
appropriate prefix to use based on the pathname it is invoked with.
If GCC cannot find the subprogram using the specified prefix, it
tries looking in the usual places for the subprogram.
- The default value of 'GCC_EXEC_PREFIX' is 'PREFIX/lib/gcc/' where
- PREFIX is the prefix to the installed compiler. In many cases
- PREFIX is the value of 'prefix' when you ran the 'configure'
+ The default value of `GCC_EXEC_PREFIX' is `PREFIX/lib/gcc/' where
+ PREFIX is the prefix to the installed compiler. In many cases
+ PREFIX is the value of `prefix' when you ran the `configure'
script.
- Other prefixes specified with '-B' take precedence over this
+ Other prefixes specified with `-B' take precedence over this
prefix.
- This prefix is also used for finding files such as 'crt0.o' that
+ This prefix is also used for finding files such as `crt0.o' that
are used for linking.
In addition, the prefix is used in an unusual way in finding the
directories to search for header files. For each of the standard
- directories whose name normally begins with '/usr/local/lib/gcc'
- (more precisely, with the value of 'GCC_INCLUDE_DIR'), GCC tries
+ directories whose name normally begins with `/usr/local/lib/gcc'
+ (more precisely, with the value of `GCC_INCLUDE_DIR'), GCC tries
replacing that beginning with the specified prefix to produce an
- alternate directory name. Thus, with '-Bfoo/', GCC searches
- 'foo/bar' just before it searches the standard directory
- '/usr/local/lib/bar'. If a standard directory begins with the
+ alternate directory name. Thus, with `-Bfoo/', GCC searches
+ `foo/bar' just before it searches the standard directory
+ `/usr/local/lib/bar'. If a standard directory begins with the
configured PREFIX then the value of PREFIX is replaced by
- 'GCC_EXEC_PREFIX' when looking for header files.
+ `GCC_EXEC_PREFIX' when looking for header files.
-'COMPILER_PATH'
- The value of 'COMPILER_PATH' is a colon-separated list of
- directories, much like 'PATH'. GCC tries the directories thus
+`COMPILER_PATH'
+ The value of `COMPILER_PATH' is a colon-separated list of
+ directories, much like `PATH'. GCC tries the directories thus
specified when searching for subprograms, if it can't find the
- subprograms using 'GCC_EXEC_PREFIX'.
+ subprograms using `GCC_EXEC_PREFIX'.
-'LIBRARY_PATH'
- The value of 'LIBRARY_PATH' is a colon-separated list of
- directories, much like 'PATH'. When configured as a native
+`LIBRARY_PATH'
+ The value of `LIBRARY_PATH' is a colon-separated list of
+ directories, much like `PATH'. When configured as a native
compiler, GCC tries the directories thus specified when searching
for special linker files, if it can't find them using
- 'GCC_EXEC_PREFIX'. Linking using GCC also uses these directories
- when searching for ordinary libraries for the '-l' option (but
- directories specified with '-L' come first).
+ `GCC_EXEC_PREFIX'. Linking using GCC also uses these directories
+ when searching for ordinary libraries for the `-l' option (but
+ directories specified with `-L' come first).
-'LANG'
+`LANG'
This variable is used to pass locale information to the compiler.
One way in which this information is used is to determine the
character set to be used when character literals, string literals
and comments are parsed in C and C++. When the compiler is
configured to allow multibyte characters, the following values for
- 'LANG' are recognized:
+ `LANG' are recognized:
- 'C-JIS'
+ `C-JIS'
Recognize JIS characters.
- 'C-SJIS'
+
+ `C-SJIS'
Recognize SJIS characters.
- 'C-EUCJP'
+
+ `C-EUCJP'
Recognize EUCJP characters.
- If 'LANG' is not defined, or if it has some other value, then the
- compiler uses 'mblen' and 'mbtowc' as defined by the default locale
- to recognize and translate multibyte characters.
+ If `LANG' is not defined, or if it has some other value, then the
+ compiler uses `mblen' and `mbtowc' as defined by the default
+ locale to recognize and translate multibyte characters.
Some additional environment variables affect the behavior of the
preprocessor.
-'CPATH'
-'C_INCLUDE_PATH'
-'CPLUS_INCLUDE_PATH'
-'OBJC_INCLUDE_PATH'
+`CPATH'
+`C_INCLUDE_PATH'
+`CPLUS_INCLUDE_PATH'
+`OBJC_INCLUDE_PATH'
Each variable's value is a list of directories separated by a
- special character, much like 'PATH', in which to look for header
- files. The special character, 'PATH_SEPARATOR', is
+ special character, much like `PATH', in which to look for header
+ files. The special character, `PATH_SEPARATOR', is
target-dependent and determined at GCC build time. For Microsoft
Windows-based targets it is a semicolon, and for almost all other
targets it is a colon.
- 'CPATH' specifies a list of directories to be searched as if
- specified with '-I', but after any paths given with '-I' options on
- the command line. This environment variable is used regardless of
- which language is being preprocessed.
+ `CPATH' specifies a list of directories to be searched as if
+ specified with `-I', but after any paths given with `-I' options
+ on the command line. This environment variable is used regardless
+ of which language is being preprocessed.
The remaining environment variables apply only when preprocessing
the particular language indicated. Each specifies a list of
- directories to be searched as if specified with '-isystem', but
- after any paths given with '-isystem' options on the command line.
+ directories to be searched as if specified with `-isystem', but
+ after any paths given with `-isystem' options on the command line.
In all these variables, an empty element instructs the compiler to
- search its current working directory. Empty elements can appear at
- the beginning or end of a path. For instance, if the value of
- 'CPATH' is ':/special/include', that has the same effect as
- '-I. -I/special/include'.
+ search its current working directory. Empty elements can appear
+ at the beginning or end of a path. For instance, if the value of
+ `CPATH' is `:/special/include', that has the same effect as
+ `-I. -I/special/include'.
-'DEPENDENCIES_OUTPUT'
+`DEPENDENCIES_OUTPUT'
If this variable is set, its value specifies how to output
dependencies for Make based on the non-system header files
processed by the compiler. System header files are ignored in the
dependency output.
- The value of 'DEPENDENCIES_OUTPUT' can be just a file name, in
+ The value of `DEPENDENCIES_OUTPUT' can be just a file name, in
which case the Make rules are written to that file, guessing the
target name from the source file name. Or the value can have the
- form 'FILE TARGET', in which case the rules are written to file
+ form `FILE TARGET', in which case the rules are written to file
FILE using TARGET as the target name.
In other words, this environment variable is equivalent to
- combining the options '-MM' and '-MF' (*note Preprocessor
- Options::), with an optional '-MT' switch too.
+ combining the options `-MM' and `-MF' (*note Preprocessor
+ Options::), with an optional `-MT' switch too.
-'SUNPRO_DEPENDENCIES'
- This variable is the same as 'DEPENDENCIES_OUTPUT' (see above),
- except that system header files are not ignored, so it implies '-M'
- rather than '-MM'. However, the dependence on the main input file
- is omitted. *Note Preprocessor Options::.
+`SUNPRO_DEPENDENCIES'
+ This variable is the same as `DEPENDENCIES_OUTPUT' (see above),
+ except that system header files are not ignored, so it implies
+ `-M' rather than `-MM'. However, the dependence on the main input
+ file is omitted. *Note Preprocessor Options::.

File: gcc.info, Node: Precompiled Headers, Prev: Environment Variables, Up: Invoking GCC
@@ -22127,45 +22274,46 @@ build the project. To make builds faster, GCC allows you to
"precompile" a header file.
To create a precompiled header file, simply compile it as you would any
-other file, if necessary using the '-x' option to make the driver treat
-it as a C or C++ header file. You may want to use a tool like 'make' to
-keep the precompiled header up-to-date when the headers it contains
+other file, if necessary using the `-x' option to make the driver treat
+it as a C or C++ header file. You may want to use a tool like `make'
+to keep the precompiled header up-to-date when the headers it contains
change.
- A precompiled header file is searched for when '#include' is seen in
+ A precompiled header file is searched for when `#include' is seen in
the compilation. As it searches for the included file (*note Search
Path: (cpp)Search Path.) the compiler looks for a precompiled header in
each directory just before it looks for the include file in that
directory. The name searched for is the name specified in the
-'#include' with '.gch' appended. If the precompiled header file can't
+`#include' with `.gch' appended. If the precompiled header file can't
be used, it is ignored.
- For instance, if you have '#include "all.h"', and you have 'all.h.gch'
-in the same directory as 'all.h', then the precompiled header file is
+ For instance, if you have `#include "all.h"', and you have `all.h.gch'
+in the same directory as `all.h', then the precompiled header file is
used if possible, and the original header is used otherwise.
Alternatively, you might decide to put the precompiled header file in a
-directory and use '-I' to ensure that directory is searched before (or
+directory and use `-I' to ensure that directory is searched before (or
instead of) the directory containing the original header. Then, if you
want to check that the precompiled header file is always used, you can
put a file of the same name as the original header in this directory
-containing an '#error' command.
-
- This also works with '-include'. So yet another way to use precompiled
-headers, good for projects not designed with precompiled header files in
-mind, is to simply take most of the header files used by a project,
-include them from another header file, precompile that header file, and
-'-include' the precompiled header. If the header files have guards
-against multiple inclusion, they are skipped because they've already
-been included (in the precompiled header).
-
- If you need to precompile the same header file for different languages,
-targets, or compiler options, you can instead make a _directory_ named
-like 'all.h.gch', and put each precompiled header in the directory,
-perhaps using '-o'. It doesn't matter what you call the files in the
-directory; every precompiled header in the directory is considered. The
-first precompiled header encountered in the directory that is valid for
-this compilation is used; they're searched in no particular order.
+containing an `#error' command.
+
+ This also works with `-include'. So yet another way to use
+precompiled headers, good for projects not designed with precompiled
+header files in mind, is to simply take most of the header files used by
+a project, include them from another header file, precompile that header
+file, and `-include' the precompiled header. If the header files have
+guards against multiple inclusion, they are skipped because they've
+already been included (in the precompiled header).
+
+ If you need to precompile the same header file for different
+languages, targets, or compiler options, you can instead make a
+_directory_ named like `all.h.gch', and put each precompiled header in
+the directory, perhaps using `-o'. It doesn't matter what you call the
+files in the directory; every precompiled header in the directory is
+considered. The first precompiled header encountered in the directory
+that is valid for this compilation is used; they're searched in no
+particular order.
There are many other possibilities, limited only by your imagination,
good sense, and the constraints of your build system.
@@ -22192,18 +22340,19 @@ good sense, and the constraints of your build system.
usually means that they don't appear in the precompiled header at
all.
- The '-D' option is one way to define a macro before a precompiled
- header is included; using a '#define' can also do it. There are
- also some options that define macros implicitly, like '-O' and
- '-Wdeprecated'; the same rule applies to macros defined this way.
+ The `-D' option is one way to define a macro before a precompiled
+ header is included; using a `#define' can also do it. There are
+ also some options that define macros implicitly, like `-O' and
+ `-Wdeprecated'; the same rule applies to macros defined this way.
* If debugging information is output when using the precompiled
- header, using '-g' or similar, the same kind of debugging
+ header, using `-g' or similar, the same kind of debugging
information must have been output when building the precompiled
- header. However, a precompiled header built using '-g' can be used
- in a compilation when no debugging information is being output.
+ header. However, a precompiled header built using `-g' can be
+ used in a compilation when no debugging information is being
+ output.
- * The same '-m' options must generally be used when building and
+ * The same `-m' options must generally be used when building and
using the precompiled header. *Note Submodel Options::, for any
cases where this rule is relaxed.
@@ -22212,18 +22361,19 @@ good sense, and the constraints of your build system.
-fexceptions
- * Some other command-line options starting with '-f', '-p', or '-O'
+ * Some other command-line options starting with `-f', `-p', or `-O'
must be defined in the same way as when the precompiled header was
generated. At present, it's not clear which options are safe to
change and which are not; the safest choice is to use exactly the
- same options when generating and using the precompiled header. The
- following are known to be safe:
+ same options when generating and using the precompiled header.
+ The following are known to be safe:
-fmessage-length= -fpreprocessed -fsched-interblock
-fsched-spec -fsched-spec-load -fsched-spec-load-dangerous
-fsched-verbose=NUMBER -fschedule-insns -fvisibility=
-pedantic-errors
+
For all of these except the last, the compiler automatically ignores
the precompiled header if the conditions aren't met. If you find an
option combination that doesn't work and doesn't cause the precompiled
@@ -22231,10 +22381,10 @@ header to be ignored, please consider filing a bug report, see *note
Bugs::.
If you do use differing options when generating and using the
-precompiled header, the actual behavior is a mixture of the behavior for
-the options. For instance, if you use '-g' to generate the precompiled
-header but not when using it, you may or may not get debugging
-information for routines in the precompiled header.
+precompiled header, the actual behavior is a mixture of the behavior
+for the options. For instance, if you use `-g' to generate the
+precompiled header but not when using it, you may or may not get
+debugging information for routines in the precompiled header.

File: gcc.info, Node: C Implementation, Next: C++ Implementation, Prev: Invoking GCC, Up: Top
@@ -22252,12 +22402,12 @@ version of the standard.
Some choices depend on the externally determined ABI for the platform
(including standard character encodings) which GCC follows; these are
listed as "determined by ABI" below. *Note Binary Compatibility:
-Compatibility, and <http://gcc.gnu.org/readings.html>. Some choices are
-documented in the preprocessor manual. *Note Implementation-defined
-behavior: (cpp)Implementation-defined behavior. Some choices are made
-by the library and operating system (or other environment when compiling
-for a freestanding environment); refer to their documentation for
-details.
+Compatibility, and `http://gcc.gnu.org/readings.html'. Some choices
+are documented in the preprocessor manual. *Note
+Implementation-defined behavior: (cpp)Implementation-defined behavior.
+Some choices are made by the library and operating system (or other
+environment when compiling for a freestanding environment); refer to
+their documentation for details.
* Menu:
@@ -22284,18 +22434,19 @@ File: gcc.info, Node: Translation implementation, Next: Environment implementa
4.1 Translation
===============
- * 'How a diagnostic is identified (C90 3.7, C99 and C11 3.10, C90,
+ * `How a diagnostic is identified (C90 3.7, C99 and C11 3.10, C90,
C99 and C11 5.1.1.3).'
Diagnostics consist of all the output sent to stderr by GCC.
- * 'Whether each nonempty sequence of white-space characters other
+ * `Whether each nonempty sequence of white-space characters other
than new-line is retained or replaced by one space character in
translation phase 3 (C90, C99 and C11 5.1.1.2).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
+

File: gcc.info, Node: Environment implementation, Next: Identifiers implementation, Prev: Translation implementation, Up: C Implementation
@@ -22305,135 +22456,138 @@ File: gcc.info, Node: Environment implementation, Next: Identifiers implementa
The behavior of most of these points are dependent on the implementation
of the C library, and are not defined by GCC itself.
- * 'The mapping between physical source file multibyte characters and
+ * `The mapping between physical source file multibyte characters and
the source character set in translation phase 1 (C90, C99 and C11
5.1.1.2).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
+

File: gcc.info, Node: Identifiers implementation, Next: Characters implementation, Prev: Environment implementation, Up: C Implementation
4.3 Identifiers
===============
- * 'Which additional multibyte characters may appear in identifiers
+ * `Which additional multibyte characters may appear in identifiers
and their correspondence to universal character names (C99 and C11
6.4.2).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'The number of significant initial characters in an identifier (C90
- 6.1.2, C90, C99 and C11 5.2.4.1, C99 and C11 6.4.2).'
+ * `The number of significant initial characters in an identifier
+ (C90 6.1.2, C90, C99 and C11 5.2.4.1, C99 and C11 6.4.2).'
For internal names, all characters are significant. For external
names, the number of significant characters are defined by the
linker; for almost all targets, all characters are significant.
- * 'Whether case distinctions are significant in an identifier with
+ * `Whether case distinctions are significant in an identifier with
external linkage (C90 6.1.2).'
This is a property of the linker. C99 and C11 require that case
distinctions are always significant in identifiers with external
linkage and systems without this property are not supported by GCC.
+

File: gcc.info, Node: Characters implementation, Next: Integers implementation, Prev: Identifiers implementation, Up: C Implementation
4.4 Characters
==============
- * 'The number of bits in a byte (C90 3.4, C99 and C11 3.6).'
+ * `The number of bits in a byte (C90 3.4, C99 and C11 3.6).'
Determined by ABI.
- * 'The values of the members of the execution character set (C90, C99
- and C11 5.2.1).'
+ * `The values of the members of the execution character set (C90,
+ C99 and C11 5.2.1).'
Determined by ABI.
- * 'The unique value of the member of the execution character set
- produced for each of the standard alphabetic escape sequences (C90,
- C99 and C11 5.2.2).'
+ * `The unique value of the member of the execution character set
+ produced for each of the standard alphabetic escape sequences
+ (C90, C99 and C11 5.2.2).'
Determined by ABI.
- * 'The value of a 'char' object into which has been stored any
+ * `The value of a `char' object into which has been stored any
character other than a member of the basic execution character set
(C90 6.1.2.5, C99 and C11 6.2.5).'
Determined by ABI.
- * 'Which of 'signed char' or 'unsigned char' has the same range,
- representation, and behavior as "plain" 'char' (C90 6.1.2.5, C90
+ * `Which of `signed char' or `unsigned char' has the same range,
+ representation, and behavior as "plain" `char' (C90 6.1.2.5, C90
6.2.1.1, C99 and C11 6.2.5, C99 and C11 6.3.1.1).'
- Determined by ABI. The options '-funsigned-char' and
- '-fsigned-char' change the default. *Note Options Controlling C
+ Determined by ABI. The options `-funsigned-char' and
+ `-fsigned-char' change the default. *Note Options Controlling C
Dialect: C Dialect Options.
- * 'The mapping of members of the source character set (in character
+ * `The mapping of members of the source character set (in character
constants and string literals) to members of the execution
character set (C90 6.1.3.4, C99 and C11 6.4.4.4, C90, C99 and C11
5.1.1.2).'
Determined by ABI.
- * 'The value of an integer character constant containing more than
+ * `The value of an integer character constant containing more than
one character or containing a character or escape sequence that
- does not map to a single-byte execution character (C90 6.1.3.4, C99
- and C11 6.4.4.4).'
+ does not map to a single-byte execution character (C90 6.1.3.4,
+ C99 and C11 6.4.4.4).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'The value of a wide character constant containing more than one
+ * `The value of a wide character constant containing more than one
multibyte character or a single multibyte character that maps to
multiple members of the extended execution character set, or
- containing a multibyte character or escape sequence not represented
- in the extended execution character set (C90 6.1.3.4, C99 and C11
- 6.4.4.4).'
+ containing a multibyte character or escape sequence not
+ represented in the extended execution character set (C90 6.1.3.4,
+ C99 and C11 6.4.4.4).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'The current locale used to convert a wide character constant
- consisting of a single multibyte character that maps to a member of
- the extended execution character set into a corresponding wide
+ * `The current locale used to convert a wide character constant
+ consisting of a single multibyte character that maps to a member
+ of the extended execution character set into a corresponding wide
character code (C90 6.1.3.4, C99 and C11 6.4.4.4).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'Whether differently-prefixed wide string literal tokens can be
+ * `Whether differently-prefixed wide string literal tokens can be
concatenated and, if so, the treatment of the resulting multibyte
character sequence (C11 6.4.5).'
Such tokens may not be concatenated.
- * 'The current locale used to convert a wide string literal into
+ * `The current locale used to convert a wide string literal into
corresponding wide character codes (C90 6.1.4, C99 and C11 6.4.5).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'The value of a string literal containing a multibyte character or
- escape sequence not represented in the execution character set (C90
- 6.1.4, C99 and C11 6.4.5).'
+ * `The value of a string literal containing a multibyte character or
+ escape sequence not represented in the execution character set
+ (C90 6.1.4, C99 and C11 6.4.5).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
behavior.
- * 'The encoding of any of 'wchar_t', 'char16_t', and 'char32_t' where
- the corresponding standard encoding macro ('__STDC_ISO_10646__',
- '__STDC_UTF_16__', or '__STDC_UTF_32__') is not defined (C11
- 6.10.8.2).'
+ * `The encoding of any of `wchar_t', `char16_t', and `char32_t'
+ where the corresponding standard encoding macro
+ (`__STDC_ISO_10646__', `__STDC_UTF_16__', or `__STDC_UTF_32__') is
+ not defined (C11 6.10.8.2).'
*Note Implementation-defined behavior: (cpp)Implementation-defined
- behavior. 'char16_t' and 'char32_t' literals are always encoded in
- UTF-16 and UTF-32 respectively.
+ behavior. `char16_t' and `char32_t' literals are always encoded
+ in UTF-16 and UTF-32 respectively.
+

File: gcc.info, Node: Integers implementation, Next: Floating point implementation, Prev: Characters implementation, Up: C Implementation
@@ -22441,12 +22595,12 @@ File: gcc.info, Node: Integers implementation, Next: Floating point implementa
4.5 Integers
============
- * 'Any extended integer types that exist in the implementation (C99
+ * `Any extended integer types that exist in the implementation (C99
and C11 6.2.5).'
GCC does not support any extended integer types.
- * 'Whether signed integer types are represented using sign and
+ * `Whether signed integer types are represented using sign and
magnitude, two's complement, or one's complement, and whether the
extraordinary value is a trap representation or an ordinary value
(C99 and C11 6.2.6.2).'
@@ -22454,124 +22608,126 @@ File: gcc.info, Node: Integers implementation, Next: Floating point implementa
GCC supports only two's complement integer types, and all bit
patterns are ordinary values.
- * 'The rank of any extended integer type relative to another extended
+ * `The rank of any extended integer type relative to another extended
integer type with the same precision (C99 and C11 6.3.1.1).'
GCC does not support any extended integer types.
- * 'The result of, or the signal raised by, converting an integer to a
+ * `The result of, or the signal raised by, converting an integer to a
signed integer type when the value cannot be represented in an
object of that type (C90 6.2.1.2, C99 and C11 6.3.1.3).'
For conversion to a type of width N, the value is reduced modulo
2^N to be within range of the type; no signal is raised.
- * 'The results of some bitwise operations on signed integers (C90
+ * `The results of some bitwise operations on signed integers (C90
6.3, C99 and C11 6.5).'
Bitwise operators act on the representation of the value including
both the sign and value bits, where the sign bit is considered
- immediately above the highest-value value bit. Signed '>>' acts on
- negative numbers by sign extension.
+ immediately above the highest-value value bit. Signed `>>' acts
+ on negative numbers by sign extension.
GCC does not use the latitude given in C99 and C11 only to treat
- certain aspects of signed '<<' as undefined, but this is subject to
+ certain aspects of signed `<<' as undefined, but this is subject to
change.
- * 'The sign of the remainder on integer division (C90 6.3.5).'
+ * `The sign of the remainder on integer division (C90 6.3.5).'
GCC always follows the C99 and C11 requirement that the result of
division is truncated towards zero.
+

File: gcc.info, Node: Floating point implementation, Next: Arrays and pointers implementation, Prev: Integers implementation, Up: C Implementation
4.6 Floating Point
==================
- * 'The accuracy of the floating-point operations and of the library
- functions in '<math.h>' and '<complex.h>' that return
+ * `The accuracy of the floating-point operations and of the library
+ functions in `<math.h>' and `<complex.h>' that return
floating-point results (C90, C99 and C11 5.2.4.2.2).'
The accuracy is unknown.
- * 'The rounding behaviors characterized by non-standard values of
- 'FLT_ROUNDS' (C90, C99 and C11 5.2.4.2.2).'
+ * `The rounding behaviors characterized by non-standard values of
+ `FLT_ROUNDS' (C90, C99 and C11 5.2.4.2.2).'
GCC does not use such values.
- * 'The evaluation methods characterized by non-standard negative
- values of 'FLT_EVAL_METHOD' (C99 and C11 5.2.4.2.2).'
+ * `The evaluation methods characterized by non-standard negative
+ values of `FLT_EVAL_METHOD' (C99 and C11 5.2.4.2.2).'
GCC does not use such values.
- * 'The direction of rounding when an integer is converted to a
+ * `The direction of rounding when an integer is converted to a
floating-point number that cannot exactly represent the original
value (C90 6.2.1.3, C99 and C11 6.3.1.4).'
C99 Annex F is followed.
- * 'The direction of rounding when a floating-point number is
- converted to a narrower floating-point number (C90 6.2.1.4, C99 and
- C11 6.3.1.5).'
+ * `The direction of rounding when a floating-point number is
+ converted to a narrower floating-point number (C90 6.2.1.4, C99
+ and C11 6.3.1.5).'
C99 Annex F is followed.
- * 'How the nearest representable value or the larger or smaller
+ * `How the nearest representable value or the larger or smaller
representable value immediately adjacent to the nearest
representable value is chosen for certain floating constants (C90
6.1.3.1, C99 and C11 6.4.4.2).'
C99 Annex F is followed.
- * 'Whether and how floating expressions are contracted when not
- disallowed by the 'FP_CONTRACT' pragma (C99 and C11 6.5).'
+ * `Whether and how floating expressions are contracted when not
+ disallowed by the `FP_CONTRACT' pragma (C99 and C11 6.5).'
- Expressions are currently only contracted if '-ffp-contract=fast',
- '-funsafe-math-optimizations' or '-ffast-math' are used. This is
+ Expressions are currently only contracted if `-ffp-contract=fast',
+ `-funsafe-math-optimizations' or `-ffast-math' are used. This is
subject to change.
- * 'The default state for the 'FENV_ACCESS' pragma (C99 and C11
+ * `The default state for the `FENV_ACCESS' pragma (C99 and C11
7.6.1).'
This pragma is not implemented, but the default is to "off" unless
- '-frounding-math' is used in which case it is "on".
+ `-frounding-math' is used in which case it is "on".
- * 'Additional floating-point exceptions, rounding modes,
+ * `Additional floating-point exceptions, rounding modes,
environments, and classifications, and their macro names (C99 and
C11 7.6, C99 and C11 7.12).'
This is dependent on the implementation of the C library, and is
not defined by GCC itself.
- * 'The default state for the 'FP_CONTRACT' pragma (C99 and C11
+ * `The default state for the `FP_CONTRACT' pragma (C99 and C11
7.12.2).'
This pragma is not implemented. Expressions are currently only
- contracted if '-ffp-contract=fast', '-funsafe-math-optimizations'
- or '-ffast-math' are used. This is subject to change.
+ contracted if `-ffp-contract=fast', `-funsafe-math-optimizations'
+ or `-ffast-math' are used. This is subject to change.
- * 'Whether the "inexact" floating-point exception can be raised when
+ * `Whether the "inexact" floating-point exception can be raised when
the rounded result actually does equal the mathematical result in
an IEC 60559 conformant implementation (C99 F.9).'
This is dependent on the implementation of the C library, and is
not defined by GCC itself.
- * 'Whether the "underflow" (and "inexact") floating-point exception
- can be raised when a result is tiny but not inexact in an IEC 60559
- conformant implementation (C99 F.9).'
+ * `Whether the "underflow" (and "inexact") floating-point exception
+ can be raised when a result is tiny but not inexact in an IEC
+ 60559 conformant implementation (C99 F.9).'
This is dependent on the implementation of the C library, and is
not defined by GCC itself.
+

File: gcc.info, Node: Arrays and pointers implementation, Next: Hints implementation, Prev: Floating point implementation, Up: C Implementation
4.7 Arrays and Pointers
=======================
- * 'The result of converting a pointer to an integer or vice versa
+ * `The result of converting a pointer to an integer or vice versa
(C90 6.3.4, C99 and C11 6.3.2.3).'
A cast from pointer to integer discards most-significant bits if
@@ -22591,16 +22747,17 @@ File: gcc.info, Node: Arrays and pointers implementation, Next: Hints implemen
integer arithmetic to avoid the undefined behavior of pointer
arithmetic as proscribed in C99 and C11 6.5.6/8.
- * 'The size of the result of subtracting two pointers to elements of
+ * `The size of the result of subtracting two pointers to elements of
the same array (C90 6.3.6, C99 and C11 6.5.6).'
The value is as specified in the standard and the type is
determined by the ABI.
- ---------- Footnotes ----------
- (1) Future versions of GCC may zero-extend, or use a target-defined
-'ptr_extend' pattern. Do not rely on sign extension.
+ ---------- Footnotes ----------
+
+ (1) Future versions of GCC may zero-extend, or use a target-defined
+`ptr_extend' pattern. Do not rely on sign extension.

File: gcc.info, Node: Hints implementation, Next: Structures unions enumerations and bit-fields implementation, Prev: Arrays and pointers implementation, Up: C Implementation
@@ -22608,91 +22765,94 @@ File: gcc.info, Node: Hints implementation, Next: Structures unions enumeratio
4.8 Hints
=========
- * 'The extent to which suggestions made by using the 'register'
+ * `The extent to which suggestions made by using the `register'
storage-class specifier are effective (C90 6.5.1, C99 and C11
6.7.1).'
- The 'register' specifier affects code generation only in these
+ The `register' specifier affects code generation only in these
ways:
* When used as part of the register variable extension, see
*note Explicit Reg Vars::.
- * When '-O0' is in use, the compiler allocates distinct stack
- memory for all variables that do not have the 'register'
- storage-class specifier; if 'register' is specified, the
+ * When `-O0' is in use, the compiler allocates distinct stack
+ memory for all variables that do not have the `register'
+ storage-class specifier; if `register' is specified, the
variable may have a shorter lifespan than the code would
indicate and may never be placed in memory.
- * On some rare x86 targets, 'setjmp' doesn't save the registers
+ * On some rare x86 targets, `setjmp' doesn't save the registers
in all circumstances. In those cases, GCC doesn't allocate
- any variables in registers unless they are marked 'register'.
+ any variables in registers unless they are marked `register'.
+
- * 'The extent to which suggestions made by using the inline function
+ * `The extent to which suggestions made by using the inline function
specifier are effective (C99 and C11 6.7.4).'
- GCC will not inline any functions if the '-fno-inline' option is
- used or if '-O0' is used. Otherwise, GCC may still be unable to
- inline a function for many reasons; the '-Winline' option may be
+ GCC will not inline any functions if the `-fno-inline' option is
+ used or if `-O0' is used. Otherwise, GCC may still be unable to
+ inline a function for many reasons; the `-Winline' option may be
used to determine if a function has not been inlined and why not.
+

File: gcc.info, Node: Structures unions enumerations and bit-fields implementation, Next: Qualifiers implementation, Prev: Hints implementation, Up: C Implementation
4.9 Structures, Unions, Enumerations, and Bit-Fields
====================================================
- * 'A member of a union object is accessed using a member of a
+ * `A member of a union object is accessed using a member of a
different type (C90 6.3.2.3).'
The relevant bytes of the representation of the object are treated
as an object of the type used for the access. *Note
Type-punning::. This may be a trap representation.
- * 'Whether a "plain" 'int' bit-field is treated as a 'signed int'
- bit-field or as an 'unsigned int' bit-field (C90 6.5.2, C90
+ * `Whether a "plain" `int' bit-field is treated as a `signed int'
+ bit-field or as an `unsigned int' bit-field (C90 6.5.2, C90
6.5.2.1, C99 and C11 6.7.2, C99 and C11 6.7.2.1).'
- By default it is treated as 'signed int' but this may be changed by
- the '-funsigned-bitfields' option.
+ By default it is treated as `signed int' but this may be changed
+ by the `-funsigned-bitfields' option.
- * 'Allowable bit-field types other than '_Bool', 'signed int', and
- 'unsigned int' (C99 and C11 6.7.2.1).'
+ * `Allowable bit-field types other than `_Bool', `signed int', and
+ `unsigned int' (C99 and C11 6.7.2.1).'
- Other integer types, such as 'long int', and enumerated types are
+ Other integer types, such as `long int', and enumerated types are
permitted even in strictly conforming mode.
- * 'Whether atomic types are permitted for bit-fields (C11 6.7.2.1).'
+ * `Whether atomic types are permitted for bit-fields (C11 6.7.2.1).'
Atomic types are not permitted for bit-fields.
- * 'Whether a bit-field can straddle a storage-unit boundary (C90
+ * `Whether a bit-field can straddle a storage-unit boundary (C90
6.5.2.1, C99 and C11 6.7.2.1).'
Determined by ABI.
- * 'The order of allocation of bit-fields within a unit (C90 6.5.2.1,
+ * `The order of allocation of bit-fields within a unit (C90 6.5.2.1,
C99 and C11 6.7.2.1).'
Determined by ABI.
- * 'The alignment of non-bit-field members of structures (C90 6.5.2.1,
- C99 and C11 6.7.2.1).'
+ * `The alignment of non-bit-field members of structures (C90
+ 6.5.2.1, C99 and C11 6.7.2.1).'
Determined by ABI.
- * 'The integer type compatible with each enumerated type (C90
+ * `The integer type compatible with each enumerated type (C90
6.5.2.2, C99 and C11 6.7.2.2).'
- Normally, the type is 'unsigned int' if there are no negative
- values in the enumeration, otherwise 'int'. If '-fshort-enums' is
+ Normally, the type is `unsigned int' if there are no negative
+ values in the enumeration, otherwise `int'. If `-fshort-enums' is
specified, then if there are negative values it is the first of
- 'signed char', 'short' and 'int' that can represent all the values,
- otherwise it is the first of 'unsigned char', 'unsigned short' and
- 'unsigned int' that can represent all the values.
+ `signed char', `short' and `int' that can represent all the
+ values, otherwise it is the first of `unsigned char', `unsigned
+ short' and `unsigned int' that can represent all the values.
+
+ On some targets, `-fshort-enums' is the default; this is
+ determined by the ABI.
- On some targets, '-fshort-enums' is the default; this is determined
- by the ABI.

File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementation, Prev: Structures unions enumerations and bit-fields implementation, Up: C Implementation
@@ -22700,12 +22860,12 @@ File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementat
4.10 Qualifiers
===============
- * 'What constitutes an access to an object that has
+ * `What constitutes an access to an object that has
volatile-qualified type (C90 6.5.3, C99 and C11 6.7.3).'
Such an object is normally accessed by pointers and used for
- accessing hardware. In most expressions, it is intuitively obvious
- what is a read and what is a write. For example
+ accessing hardware. In most expressions, it is intuitively
+ obvious what is a read and what is a write. For example
volatile int *dst = SOMEVALUE;
volatile int *src = SOMEOTHERVALUE;
@@ -22714,7 +22874,7 @@ File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementat
will cause a read of the volatile object pointed to by SRC and
store the value into the volatile object pointed to by DST. There
is no guarantee that these reads and writes are atomic, especially
- for objects larger than 'int'.
+ for objects larger than `int'.
However, if the volatile storage is not being modified, and the
value of the volatile storage is not used, then the situation is
@@ -22724,7 +22884,7 @@ File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementat
*src;
According to the C standard, such an expression is an rvalue whose
- type is the unqualified version of its original type, i.e. 'int'.
+ type is the unqualified version of its original type, i.e. `int'.
Whether GCC interprets this as a read of the volatile object being
pointed to or only as a request to evaluate the expression for its
side-effects depends on this type.
@@ -22735,28 +22895,31 @@ File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementat
by GCC as a read of the volatile object; in the other cases, the
expression is only evaluated for its side-effects.
+

File: gcc.info, Node: Declarators implementation, Next: Statements implementation, Prev: Qualifiers implementation, Up: C Implementation
4.11 Declarators
================
- * 'The maximum number of declarators that may modify an arithmetic,
+ * `The maximum number of declarators that may modify an arithmetic,
structure or union type (C90 6.5.4).'
GCC is only limited by available memory.
+

File: gcc.info, Node: Statements implementation, Next: Preprocessing directives implementation, Prev: Declarators implementation, Up: C Implementation
4.12 Statements
===============
- * 'The maximum number of 'case' values in a 'switch' statement (C90
+ * `The maximum number of `case' values in a `switch' statement (C90
6.6.4.2).'
GCC is only limited by available memory.
+

File: gcc.info, Node: Preprocessing directives implementation, Next: Library functions implementation, Prev: Statements implementation, Up: C Implementation
@@ -22767,50 +22930,51 @@ File: gcc.info, Node: Preprocessing directives implementation, Next: Library f
behavior, for details of these aspects of implementation-defined
behavior.
- * 'The locations within '#pragma' directives where header name
+ * `The locations within `#pragma' directives where header name
preprocessing tokens are recognized (C11 6.4, C11 6.4.7).'
- * 'How sequences in both forms of header names are mapped to headers
+ * `How sequences in both forms of header names are mapped to headers
or external source file names (C90 6.1.7, C99 and C11 6.4.7).'
- * 'Whether the value of a character constant in a constant expression
+ * `Whether the value of a character constant in a constant expression
that controls conditional inclusion matches the value of the same
character constant in the execution character set (C90 6.8.1, C99
and C11 6.10.1).'
- * 'Whether the value of a single-character character constant in a
+ * `Whether the value of a single-character character constant in a
constant expression that controls conditional inclusion may have a
negative value (C90 6.8.1, C99 and C11 6.10.1).'
- * 'The places that are searched for an included '<>' delimited
+ * `The places that are searched for an included `<>' delimited
header, and how the places are specified or the header is
identified (C90 6.8.2, C99 and C11 6.10.2).'
- * 'How the named source file is searched for in an included '""'
+ * `How the named source file is searched for in an included `""'
delimited header (C90 6.8.2, C99 and C11 6.10.2).'
- * 'The method by which preprocessing tokens (possibly resulting from
- macro expansion) in a '#include' directive are combined into a
+ * `The method by which preprocessing tokens (possibly resulting from
+ macro expansion) in a `#include' directive are combined into a
header name (C90 6.8.2, C99 and C11 6.10.2).'
- * 'The nesting limit for '#include' processing (C90 6.8.2, C99 and
+ * `The nesting limit for `#include' processing (C90 6.8.2, C99 and
C11 6.10.2).'
- * 'Whether the '#' operator inserts a '\' character before the '\'
+ * `Whether the `#' operator inserts a `\' character before the `\'
character that begins a universal character name in a character
constant or string literal (C99 and C11 6.10.3.2).'
- * 'The behavior on each recognized non-'STDC #pragma' directive (C90
+ * `The behavior on each recognized non-`STDC #pragma' directive (C90
6.8.6, C99 and C11 6.10.6).'
- *Note Pragmas: (cpp)Pragmas, for details of pragmas accepted by GCC
- on all targets. *Note Pragmas Accepted by GCC: Pragmas, for
+ *Note Pragmas: (cpp)Pragmas, for details of pragmas accepted by
+ GCC on all targets. *Note Pragmas Accepted by GCC: Pragmas, for
details of target-specific pragmas.
- * 'The definitions for '__DATE__' and '__TIME__' when respectively,
+ * `The definitions for `__DATE__' and `__TIME__' when respectively,
the date and time of translation are not available (C90 6.8.8, C99
6.10.8, C11 6.10.8.1).'
+

File: gcc.info, Node: Library functions implementation, Next: Architecture implementation, Prev: Preprocessing directives implementation, Up: C Implementation
@@ -22820,26 +22984,27 @@ File: gcc.info, Node: Library functions implementation, Next: Architecture imp
The behavior of most of these points are dependent on the implementation
of the C library, and are not defined by GCC itself.
- * 'The null pointer constant to which the macro 'NULL' expands (C90
+ * `The null pointer constant to which the macro `NULL' expands (C90
7.1.6, C99 7.17, C11 7.19).'
- In '<stddef.h>', 'NULL' expands to '((void *)0)'. GCC does not
- provide the other headers which define 'NULL' and some library
+ In `<stddef.h>', `NULL' expands to `((void *)0)'. GCC does not
+ provide the other headers which define `NULL' and some library
implementations may use other definitions in those headers.
+

File: gcc.info, Node: Architecture implementation, Next: Locale-specific behavior implementation, Prev: Library functions implementation, Up: C Implementation
4.15 Architecture
=================
- * 'The values or expressions assigned to the macros specified in the
- headers '<float.h>', '<limits.h>', and '<stdint.h>' (C90, C99 and
+ * `The values or expressions assigned to the macros specified in the
+ headers `<float.h>', `<limits.h>', and `<stdint.h>' (C90, C99 and
C11 5.2.4.2, C99 7.18.2, C99 7.18.3, C11 7.20.2, C11 7.20.3).'
Determined by ABI.
- * 'The result of attempting to indirectly access an object with
+ * `The result of attempting to indirectly access an object with
automatic or thread storage duration from a thread other than the
one with which it is associated (C11 6.2.4).'
@@ -22847,29 +23012,30 @@ File: gcc.info, Node: Architecture implementation, Next: Locale-specific behav
synchronization for concurrent accesses as for concurrent accesses
to any object.
- * 'The number, order, and encoding of bytes in any object (when not
+ * `The number, order, and encoding of bytes in any object (when not
explicitly specified in this International Standard) (C99 and C11
6.2.6.1).'
Determined by ABI.
- * 'Whether any extended alignments are supported and the contexts in
+ * `Whether any extended alignments are supported and the contexts in
which they are supported (C11 6.2.8).'
- Extended alignments up to 2^{28} (bytes) are supported for objects
- of automatic storage duration. Alignments supported for objects of
- static and thread storage duration are determined by the ABI.
+ Extended alignments up to 2^28 (bytes) are supported for objects
+ of automatic storage duration. Alignments supported for objects
+ of static and thread storage duration are determined by the ABI.
- * 'Valid alignment values other than those returned by an _Alignof
+ * `Valid alignment values other than those returned by an _Alignof
expression for fundamental types, if any (C11 6.2.8).'
- Valid alignments are powers of 2 up to and including 2^{28}.
+ Valid alignments are powers of 2 up to and including 2^28.
- * 'The value of the result of the 'sizeof' and '_Alignof' operators
+ * `The value of the result of the `sizeof' and `_Alignof' operators
(C90 6.3.3.4, C99 and C11 6.5.3.4).'
Determined by ABI.
+

File: gcc.info, Node: Locale-specific behavior implementation, Prev: Architecture implementation, Up: C Implementation
@@ -22889,19 +23055,19 @@ A conforming implementation of ISO C++ is required to document its
choice of behavior in each of the areas that are designated
"implementation defined". The following lists all such areas, along
with the section numbers from the ISO/IEC 14882:1998 and ISO/IEC
-14882:2003 standards. Some areas are only implementation-defined in one
-version of the standard.
+14882:2003 standards. Some areas are only implementation-defined in
+one version of the standard.
Some choices depend on the externally determined ABI for the platform
(including standard character encodings) which GCC follows; these are
listed as "determined by ABI" below. *Note Binary Compatibility:
-Compatibility, and <http://gcc.gnu.org/readings.html>. Some choices are
-documented in the preprocessor manual. *Note Implementation-defined
-behavior: (cpp)Implementation-defined behavior. Some choices are
-documented in the corresponding document for the C language. *Note C
-Implementation::. Some choices are made by the library and operating
-system (or other environment when compiling for a freestanding
-environment); refer to their documentation for details.
+Compatibility, and `http://gcc.gnu.org/readings.html'. Some choices
+are documented in the preprocessor manual. *Note
+Implementation-defined behavior: (cpp)Implementation-defined behavior.
+Some choices are documented in the corresponding document for the C
+language. *Note C Implementation::. Some choices are made by the
+library and operating system (or other environment when compiling for a
+freestanding environment); refer to their documentation for details.
* Menu:
@@ -22914,29 +23080,31 @@ File: gcc.info, Node: Conditionally-supported behavior, Next: Exception handli
5.1 Conditionally-Supported Behavior
====================================
-'Each implementation shall include documentation that identifies all
+`Each implementation shall include documentation that identifies all
conditionally-supported constructs that it does not support (C++0x
1.4).'
- * 'Whether an argument of class type with a non-trivial copy
+ * `Whether an argument of class type with a non-trivial copy
constructor or destructor can be passed to ... (C++0x 5.2.2).'
Such argument passing is supported, using the same
pass-by-invisible-reference approach used for normal function
arguments of such types.
+

File: gcc.info, Node: Exception handling, Prev: Conditionally-supported behavior, Up: C++ Implementation
5.2 Exception Handling
======================
- * 'In the situation where no matching handler is found, it is
+ * `In the situation where no matching handler is found, it is
implementation-defined whether or not the stack is unwound before
std::terminate() is called (C++98 15.5.1).'
The stack is not unwound before std::terminate is called.
+

File: gcc.info, Node: C Extensions, Next: C++ Extensions, Prev: C++ Implementation, Up: Top
@@ -22944,10 +23112,10 @@ File: gcc.info, Node: C Extensions, Next: C++ Extensions, Prev: C++ Implement
*************************************
GNU C provides several language features not found in ISO standard C.
-(The '-pedantic' option directs GCC to print a warning message if any of
-these features is used.) To test for the availability of these features
-in conditional compilation, check for a predefined macro '__GNUC__',
-which is always defined under GCC.
+(The `-pedantic' option directs GCC to print a warning message if any
+of these features is used.) To test for the availability of these
+features in conditional compilation, check for a predefined macro
+`__GNUC__', which is always defined under GCC.
These extensions are available in C and Objective-C. Most of them are
also available in C++. *Note Extensions to the C++ Language: C++
@@ -22963,10 +23131,10 @@ extensions, accepted by GCC in C90 mode and in C++.
* Labels as Values:: Getting pointers to labels, and computed gotos.
* Nested Functions:: As in Algol and Pascal, lexical scoping of functions.
* Constructing Calls:: Dispatching a call to another function.
-* Typeof:: 'typeof': referring to the type of an expression.
-* Conditionals:: Omitting the middle operand of a '?:' expression.
-* __int128:: 128-bit integers--'__int128'.
-* Long Long:: Double-word integers--'long long int'.
+* Typeof:: `typeof': referring to the type of an expression.
+* Conditionals:: Omitting the middle operand of a `?:' expression.
+* __int128:: 128-bit integers---`__int128'.
+* Long Long:: Double-word integers---`long long int'.
* Complex:: Data types for complex numbers.
* Floating Types:: Additional Floating Types.
* Half-Precision:: Half-Precision Floating Point.
@@ -22980,13 +23148,13 @@ extensions, accepted by GCC in C90 mode and in C++.
* Variadic Macros:: Macros with a variable number of arguments.
* Escaped Newlines:: Slightly looser rules for escaped newlines.
* Subscripting:: Any array can be subscripted, even if not an lvalue.
-* Pointer Arith:: Arithmetic on 'void'-pointers and function pointers.
+* Pointer Arith:: Arithmetic on `void'-pointers and function pointers.
* Pointers to Arrays:: Pointers to arrays with qualifiers work as expected.
* Initializers:: Non-constant initializers.
* Compound Literals:: Compound literals give structures, unions
or arrays as values.
* Designated Inits:: Labeling elements of initializers.
-* Case Ranges:: 'case 1 ... 9' and such.
+* Case Ranges:: `case 1 ... 9' and such.
* Cast to Union:: Casting to union type from any member of the union.
* Mixed Declarations:: Mixing declarations and code.
* Function Attributes:: Declaring that functions have no side effects,
@@ -22996,20 +23164,20 @@ extensions, accepted by GCC in C90 mode and in C++.
* Function Prototypes:: Prototype declarations and old-style definitions.
* C++ Comments:: C++ comments are recognized.
* Dollar Signs:: Dollar sign is allowed in identifiers.
-* Character Escapes:: '\e' stands for the character <ESC>.
+* Character Escapes:: `\e' stands for the character <ESC>.
* Variable Attributes:: Specifying attributes of variables.
* Type Attributes:: Specifying attributes of types.
* Alignment:: Inquiring about the alignment of a type or variable.
* Inline:: Defining inline functions (as fast as macros).
* Volatiles:: What constitutes an access to a volatile object.
* Using Assembly Language with C:: Instructions and extensions for interfacing C with assembler.
-* Alternate Keywords:: '__const__', '__asm__', etc., for header files.
-* Incomplete Enums:: 'enum foo;', with details to follow.
+* Alternate Keywords:: `__const__', `__asm__', etc., for header files.
+* Incomplete Enums:: `enum foo;', with details to follow.
* Function Names:: Printable strings which are the name of the current
function.
* Return Address:: Getting the return or frame address of a function.
* Vector Extensions:: Using vector instructions through built-in functions.
-* Offsetof:: Special syntax for implementing 'offsetof'.
+* Offsetof:: Special syntax for implementing `offsetof'.
* __sync Builtins:: Legacy built-in functions for atomic memory access.
* __atomic Builtins:: Atomic built-in functions with memory model.
* Integer Overflow Builtins:: Built-in functions to perform arithmetics and
@@ -23025,7 +23193,7 @@ extensions, accepted by GCC in C90 mode and in C++.
* Pragmas:: Pragmas accepted by GCC.
* Unnamed Fields:: Unnamed struct/union fields within structs/unions.
* Thread-Local:: Per-thread variables.
-* Binary constants:: Binary constants using the '0b' prefix.
+* Binary constants:: Binary constants using the `0b' prefix.

File: gcc.info, Node: Statement Exprs, Next: Local Labels, Up: C Extensions
@@ -23047,12 +23215,12 @@ example:
z; })
is a valid (though slightly more complex than necessary) expression for
-the absolute value of 'foo ()'.
+the absolute value of `foo ()'.
The last thing in the compound statement should be an expression
followed by a semicolon; the value of this subexpression serves as the
value of the entire construct. (If you use some other kind of statement
-last within the braces, the construct has type 'void', and thus
+last within the braces, the construct has type `void', and thus
effectively no value.)
This feature is especially useful in making macro definitions "safe"
@@ -23064,7 +23232,7 @@ follows:
But this definition computes either A or B twice, with bad results if
the operand has side effects. In GNU C, if you know the type of the
-operands (here taken as 'int'), you can define the macro safely as
+operands (here taken as `int'), you can define the macro safely as
follows:
#define maxint(a,b) \
@@ -23075,27 +23243,27 @@ the value of an enumeration constant, the width of a bit-field, or the
initial value of a static variable.
If you don't know the type of the operand, you can still do this, but
-you must use 'typeof' or '__auto_type' (*note Typeof::).
+you must use `typeof' or `__auto_type' (*note Typeof::).
In G++, the result value of a statement expression undergoes array and
function pointer decay, and is returned by value to the enclosing
-expression. For instance, if 'A' is a class, then
+expression. For instance, if `A' is a class, then
A a;
({a;}).Foo ()
-constructs a temporary 'A' object to hold the result of the statement
-expression, and that is used to invoke 'Foo'. Therefore the 'this'
-pointer observed by 'Foo' is not the address of 'a'.
+constructs a temporary `A' object to hold the result of the statement
+expression, and that is used to invoke `Foo'. Therefore the `this'
+pointer observed by `Foo' is not the address of `a'.
In a statement expression, any temporaries created within a statement
-are destroyed at that statement's end. This makes statement expressions
-inside macros slightly different from function calls. In the latter
-case temporaries introduced during argument evaluation are destroyed at
-the end of the statement that includes the function call. In the
-statement expression case they are destroyed during the statement
-expression. For instance,
+are destroyed at that statement's end. This makes statement
+expressions inside macros slightly different from function calls. In
+the latter case temporaries introduced during argument evaluation are
+destroyed at the end of the statement that includes the function call.
+In the statement expression case they are destroyed during the
+statement expression. For instance,
#define macro(a) ({__typeof__(a) b = (a); b + 3; })
template<typename T> T function(T a) { T b = a; return b + 3; }
@@ -23106,9 +23274,9 @@ expression. For instance,
function (X ());
}
-has different places where temporaries are destroyed. For the 'macro'
-case, the temporary 'X' is destroyed just after the initialization of
-'b'. In the 'function' case that temporary is destroyed when the
+has different places where temporaries are destroyed. For the `macro'
+case, the temporary `X' is destroyed just after the initialization of
+`b'. In the `function' case that temporary is destroyed when the
function returns.
These considerations mean that it is probably a bad idea to use
@@ -23117,10 +23285,10 @@ work with C++. (Note that some versions of the GNU C Library contained
header files using statement expressions that lead to precisely this
bug.)
- Jumping into a statement expression with 'goto' or using a 'switch'
-statement outside the statement expression with a 'case' or 'default'
+ Jumping into a statement expression with `goto' or using a `switch'
+statement outside the statement expression with a `case' or `default'
label inside the statement expression is not permitted. Jumping into a
-statement expression with a computed 'goto' (*note Labels as Values::)
+statement expression with a computed `goto' (*note Labels as Values::)
has undefined behavior. Jumping out of a statement expression is
permitted, but if the statement expression is part of a larger
expression then it is unspecified which other subexpressions of that
@@ -23132,9 +23300,9 @@ evaluation of other parts of the containing expression. For example,
foo (), (({ bar1 (); goto a; 0; }) + bar2 ()), baz();
-calls 'foo' and 'bar1' and does not call 'baz' but may or may not call
-'bar2'. If 'bar2' is called, it is called after 'foo' and before
-'bar1'.
+calls `foo' and `bar1' and does not call `baz' but may or may not call
+`bar2'. If `bar2' is called, it is called after `foo' and before
+`bar1'.

File: gcc.info, Node: Local Labels, Next: Labels as Values, Prev: Statement Exprs, Up: C Extensions
@@ -23144,7 +23312,7 @@ File: gcc.info, Node: Local Labels, Next: Labels as Values, Prev: Statement E
GCC allows you to declare "local labels" in any nested block scope. A
local label is just like an ordinary label, but you can only reference
-it (with a 'goto' statement, or by taking its address) within the block
+it (with a `goto' statement, or by taking its address) within the block
in which it is declared.
A local label declaration looks like this:
@@ -23158,12 +23326,12 @@ or
Local label declarations must come at the beginning of the block,
before any ordinary declarations or statements.
- The label declaration defines the label _name_, but does not define the
-label itself. You must do this in the usual way, with 'LABEL:', within
-the statements of the statement expression.
+ The label declaration defines the label _name_, but does not define
+the label itself. You must do this in the usual way, with `LABEL:',
+within the statements of the statement expression.
The local label feature is useful for complex macros. If a macro
-contains nested loops, a 'goto' can be useful for breaking out of them.
+contains nested loops, a `goto' can be useful for breaking out of them.
However, an ordinary label whose scope is the whole function cannot be
used: if the macro can be expanded several times in one function, the
label is multiply defined in that function. A local label avoids this
@@ -23212,21 +23380,21 @@ File: gcc.info, Node: Labels as Values, Next: Nested Functions, Prev: Local L
6.3 Labels as Values
====================
-You can get the address of a label defined in the current function (or a
-containing function) with the unary operator '&&'. The value has type
-'void *'. This value is a constant and can be used wherever a constant
-of that type is valid. For example:
+You can get the address of a label defined in the current function (or
+a containing function) with the unary operator `&&'. The value has
+type `void *'. This value is a constant and can be used wherever a
+constant of that type is valid. For example:
void *ptr;
/* ... */
ptr = &&foo;
To use these values, you need to be able to jump to one. This is done
-with the computed goto statement(1), 'goto *EXP;'. For example,
+with the computed goto statement(1), `goto *EXP;'. For example,
goto *ptr;
-Any expression of type 'void *' is allowed.
+Any expression of type `void *' is allowed.
One way of using these constants is in initializing a static array that
serves as a jump table:
@@ -23241,13 +23409,13 @@ Note that this does not check whether the subscript is in bounds--array
indexing in C never does that.
Such an array of label values serves a purpose much like that of the
-'switch' statement. The 'switch' statement is cleaner, so use that
-rather than an array unless the problem does not fit a 'switch'
+`switch' statement. The `switch' statement is cleaner, so use that
+rather than an array unless the problem does not fit a `switch'
statement very well.
Another use of label values is in an interpreter for threaded code.
-The labels within the interpreter function can be stored in the threaded
-code for super-fast dispatching.
+The labels within the interpreter function can be stored in the
+threaded code for super-fast dispatching.
You may not use this mechanism to jump to code in a different function.
If you do that, totally unpredictable things happen. The best way to
@@ -23266,15 +23434,16 @@ allows the data to be read-only. This alternative with label
differences is not supported for the AVR target, please use the first
approach for AVR programs.
- The '&&foo' expressions for the same label might have different values
-if the containing function is inlined or cloned. If a program relies on
-them being always the same, '__attribute__((__noinline__,__noclone__))'
-should be used to prevent inlining and cloning. If '&&foo' is used in a
-static variable initializer, inlining and cloning is forbidden.
+ The `&&foo' expressions for the same label might have different values
+if the containing function is inlined or cloned. If a program relies
+on them being always the same,
+`__attribute__((__noinline__,__noclone__))' should be used to prevent
+inlining and cloning. If `&&foo' is used in a static variable
+initializer, inlining and cloning is forbidden.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) The analogous feature in Fortran is called an assigned goto, but
+ (1) The analogous feature in Fortran is called an assigned goto, but
that name seems inappropriate in C, where one can do more than simply
store label addresses in label variables.
@@ -23289,7 +23458,7 @@ Nested functions are supported as an extension in GNU C, but are not
supported by GNU C++.
The nested function's name is local to the block where it is defined.
-For example, here we define a nested function named 'square', and call
+For example, here we define a nested function named `square', and call
it twice:
foo (double a, double b)
@@ -23302,7 +23471,7 @@ it twice:
The nested function can access all the variables of the containing
function that are visible at the point of its definition. This is
called "lexical scoping". For example, here we show a nested function
-which uses an inherited variable named 'offset':
+which uses an inherited variable named `offset':
bar (int *array, int offset, int size)
{
@@ -23330,29 +23499,29 @@ function:
intermediate (store, size);
}
- Here, the function 'intermediate' receives the address of 'store' as an
-argument. If 'intermediate' calls 'store', the arguments given to
-'store' are used to store into 'array'. But this technique works only
-so long as the containing function ('hack', in this example) does not
+ Here, the function `intermediate' receives the address of `store' as
+an argument. If `intermediate' calls `store', the arguments given to
+`store' are used to store into `array'. But this technique works only
+so long as the containing function (`hack', in this example) does not
exit.
If you try to call the nested function through its address after the
-containing function exits, all hell breaks loose. If you try to call it
-after a containing scope level exits, and if it refers to some of the
-variables that are no longer in scope, you may be lucky, but it's not
-wise to take the risk. If, however, the nested function does not refer
-to anything that has gone out of scope, you should be safe.
+containing function exits, all hell breaks loose. If you try to call
+it after a containing scope level exits, and if it refers to some of
+the variables that are no longer in scope, you may be lucky, but it's
+not wise to take the risk. If, however, the nested function does not
+refer to anything that has gone out of scope, you should be safe.
GCC implements taking the address of a nested function using a
technique called "trampolines". This technique was described in
-'Lexical Closures for C++' (Thomas M. Breuel, USENIX C++ Conference
+`Lexical Closures for C++' (Thomas M. Breuel, USENIX C++ Conference
Proceedings, October 17-21, 1988).
A nested function can jump to a label inherited from a containing
function, provided the label is explicitly declared in the containing
function (*note Local Labels::). Such a jump returns instantly to the
-containing function, exiting the nested function that did the 'goto' and
-any intermediate functions as well. Here is an example:
+containing function, exiting the nested function that did the `goto'
+and any intermediate functions as well. Here is an example:
bar (int *array, int offset, int size)
{
@@ -23370,15 +23539,15 @@ any intermediate functions as well. Here is an example:
/* ... */
return 0;
- /* Control comes here from 'access'
+ /* Control comes here from `access'
if it detects an error. */
failure:
return -1;
}
- A nested function always has no linkage. Declaring one with 'extern'
-or 'static' is erroneous. If you need to declare the nested function
-before its definition, use 'auto' (which is otherwise meaningless for
+ A nested function always has no linkage. Declaring one with `extern'
+or `static' is erroneous. If you need to declare the nested function
+before its definition, use `auto' (which is otherwise meaningless for
function declarations).
bar (int *array, int offset, int size)
@@ -23416,8 +23585,8 @@ acting as mere forwarders for their arguments.
-- Built-in Function: void * __builtin_apply_args ()
This built-in function returns a pointer to data describing how to
- perform a call with the same arguments as are passed to the current
- function.
+ perform a call with the same arguments as are passed to the
+ current function.
The function saves the arg pointer register, structure value
address, and all registers that might be used to pass arguments to
@@ -23430,7 +23599,7 @@ acting as mere forwarders for their arguments.
parameters described by ARGUMENTS and SIZE.
The value of ARGUMENTS should be the value returned by
- '__builtin_apply_args'. The argument SIZE specifies the size of
+ `__builtin_apply_args'. The argument SIZE specifies the size of
the stack argument data, in bytes.
This function returns a pointer to data describing how to return
@@ -23438,25 +23607,25 @@ acting as mere forwarders for their arguments.
block of memory allocated on the stack.
It is not always simple to compute the proper value for SIZE. The
- value is used by '__builtin_apply' to compute the amount of data
+ value is used by `__builtin_apply' to compute the amount of data
that should be pushed on the stack and copied from the incoming
argument area.
-- Built-in Function: void __builtin_return (void *RESULT)
This built-in function returns the value described by RESULT from
the containing function. You should specify, for RESULT, a value
- returned by '__builtin_apply'.
+ returned by `__builtin_apply'.
- -- Built-in Function: __builtin_va_arg_pack ()
+ -- Built-in Function: __builtin_va_arg_pack ()
This built-in function represents all anonymous arguments of an
inline function. It can be used only in inline functions that are
always inlined, never compiled as a separate function, such as
- those using '__attribute__ ((__always_inline__))' or '__attribute__
- ((__gnu_inline__))' extern inline functions. It must be only
- passed as last argument to some other function with variable
- arguments. This is useful for writing small wrapper inlines for
- variable argument functions, when using preprocessor macros is
- undesirable. For example:
+ those using `__attribute__ ((__always_inline__))' or
+ `__attribute__ ((__gnu_inline__))' extern inline functions. It
+ must be only passed as last argument to some other function with
+ variable arguments. This is useful for writing small wrapper
+ inlines for variable argument functions, when using preprocessor
+ macros is undesirable. For example:
extern int myprintf (FILE *f, const char *format, ...);
extern inline __attribute__ ((__gnu_inline__)) int
myprintf (FILE *f, const char *format, ...)
@@ -23474,10 +23643,10 @@ acting as mere forwarders for their arguments.
This built-in function returns the number of anonymous arguments of
an inline function. It can be used only in inline functions that
are always inlined, never compiled as a separate function, such as
- those using '__attribute__ ((__always_inline__))' or '__attribute__
- ((__gnu_inline__))' extern inline functions. For example following
- does link- or run-time checking of open arguments for optimized
- code:
+ those using `__attribute__ ((__always_inline__))' or
+ `__attribute__ ((__gnu_inline__))' extern inline functions. For
+ example following does link- or run-time checking of open
+ arguments for optimized code:
#ifdef __OPTIMIZE__
extern inline __attribute__((__gnu_inline__)) int
myopen (const char *path, int oflag, ...)
@@ -23505,40 +23674,40 @@ acting as mere forwarders for their arguments.

File: gcc.info, Node: Typeof, Next: Conditionals, Prev: Constructing Calls, Up: C Extensions
-6.6 Referring to a Type with 'typeof'
+6.6 Referring to a Type with `typeof'
=====================================
-Another way to refer to the type of an expression is with 'typeof'. The
-syntax of using of this keyword looks like 'sizeof', but the construct
-acts semantically like a type name defined with 'typedef'.
+Another way to refer to the type of an expression is with `typeof'.
+The syntax of using of this keyword looks like `sizeof', but the
+construct acts semantically like a type name defined with `typedef'.
- There are two ways of writing the argument to 'typeof': with an
+ There are two ways of writing the argument to `typeof': with an
expression or with a type. Here is an example with an expression:
typeof (x[0](1))
-This assumes that 'x' is an array of pointers to functions; the type
+This assumes that `x' is an array of pointers to functions; the type
described is that of the values of the functions.
Here is an example with a typename as the argument:
typeof (int *)
-Here the type described is that of pointers to 'int'.
+Here the type described is that of pointers to `int'.
If you are writing a header file that must work when included in ISO C
-programs, write '__typeof__' instead of 'typeof'. *Note Alternate
+programs, write `__typeof__' instead of `typeof'. *Note Alternate
Keywords::.
- A 'typeof' construct can be used anywhere a typedef name can be used.
+ A `typeof' construct can be used anywhere a typedef name can be used.
For example, you can use it in a declaration, in a cast, or inside of
-'sizeof' or 'typeof'.
+`sizeof' or `typeof'.
- The operand of 'typeof' is evaluated for its side effects if and only
+ The operand of `typeof' is evaluated for its side effects if and only
if it is an expression of variably modified type or the name of such a
type.
- 'typeof' is often useful in conjunction with statement expressions
+ `typeof' is often useful in conjunction with statement expressions
(*note Statement Exprs::). Here is how the two together can be used to
define a safe "maximum" macro which operates on any arithmetic type and
evaluates each of its arguments exactly once:
@@ -23550,22 +23719,22 @@ evaluates each of its arguments exactly once:
The reason for using names that start with underscores for the local
variables is to avoid conflicts with variable names that occur within
-the expressions that are substituted for 'a' and 'b'. Eventually we
+the expressions that are substituted for `a' and `b'. Eventually we
hope to design a new form of declaration syntax that allows you to
-declare variables whose scopes start only after their initializers; this
-will be a more reliable way to prevent such conflicts.
+declare variables whose scopes start only after their initializers;
+this will be a more reliable way to prevent such conflicts.
-Some more examples of the use of 'typeof':
+Some more examples of the use of `typeof':
- * This declares 'y' with the type of what 'x' points to.
+ * This declares `y' with the type of what `x' points to.
typeof (*x) y;
- * This declares 'y' as an array of such values.
+ * This declares `y' as an array of such values.
typeof (*x) y[4];
- * This declares 'y' as an array of pointers to characters:
+ * This declares `y' as an array of pointers to characters:
typeof (typeof (char *)[4]) y;
@@ -23573,7 +23742,7 @@ Some more examples of the use of 'typeof':
char *y[4];
- To see the meaning of the declaration using 'typeof', and why it
+ To see the meaning of the declaration using `typeof', and why it
might be a useful way to write, rewrite it with these macros:
#define pointer(T) typeof(T *)
@@ -23583,32 +23752,32 @@ Some more examples of the use of 'typeof':
array (pointer (char), 4) y;
- Thus, 'array (pointer (char), 4)' is the type of arrays of 4
- pointers to 'char'.
+ Thus, `array (pointer (char), 4)' is the type of arrays of 4
+ pointers to `char'.
In GNU C, but not GNU C++, you may also declare the type of a variable
-as '__auto_type'. In that case, the declaration must declare only one
+as `__auto_type'. In that case, the declaration must declare only one
variable, whose declarator must just be an identifier, the declaration
must be initialized, and the type of the variable is determined by the
initializer; the name of the variable is not in scope until after the
-initializer. (In C++, you should use C++11 'auto' for this purpose.)
-Using '__auto_type', the "maximum" macro above could be written as:
+initializer. (In C++, you should use C++11 `auto' for this purpose.)
+Using `__auto_type', the "maximum" macro above could be written as:
#define max(a,b) \
({ __auto_type _a = (a); \
__auto_type _b = (b); \
_a > _b ? _a : _b; })
- Using '__auto_type' instead of 'typeof' has two advantages:
+ Using `__auto_type' instead of `typeof' has two advantages:
* Each argument to the macro appears only once in the expansion of
the macro. This prevents the size of the macro expansion growing
- exponentially when calls to such macros are nested inside arguments
- of such macros.
+ exponentially when calls to such macros are nested inside
+ arguments of such macros.
* If the argument to the macro has variably modified type, it is
- evaluated only once when using '__auto_type', but twice if 'typeof'
- is used.
+ evaluated only once when using `__auto_type', but twice if
+ `typeof' is used.

File: gcc.info, Node: Conditionals, Next: __int128, Prev: Typeof, Up: C Extensions
@@ -23624,7 +23793,7 @@ expression.
x ? : y
-has the value of 'x' if that is nonzero; otherwise, the value of 'y'.
+has the value of `x' if that is nonzero; otherwise, the value of `y'.
This example is perfectly equivalent to
@@ -23633,9 +23802,9 @@ has the value of 'x' if that is nonzero; otherwise, the value of 'y'.
In this simple case, the ability to omit the middle operand is not
especially useful. When it becomes useful is when the first operand
does, or may (if it is a macro argument), contain a side effect. Then
-repeating the operand in the middle would perform the side effect twice.
-Omitting the middle operand uses the value already computed without the
-undesirable effects of recomputing it.
+repeating the operand in the middle would perform the side effect
+twice. Omitting the middle operand uses the value already computed
+without the undesirable effects of recomputing it.

File: gcc.info, Node: __int128, Next: Long Long, Prev: Conditionals, Up: C Extensions
@@ -23643,12 +23812,12 @@ File: gcc.info, Node: __int128, Next: Long Long, Prev: Conditionals, Up: C E
6.8 128-bit Integers
====================
-As an extension the integer scalar type '__int128' is supported for
-targets which have an integer mode wide enough to hold 128 bits. Simply
-write '__int128' for a signed 128-bit integer, or 'unsigned __int128'
-for an unsigned 128-bit integer. There is no support in GCC for
-expressing an integer constant of type '__int128' for targets with 'long
-long' integer less than 128 bits wide.
+As an extension the integer scalar type `__int128' is supported for
+targets which have an integer mode wide enough to hold 128 bits.
+Simply write `__int128' for a signed 128-bit integer, or `unsigned
+__int128' for an unsigned 128-bit integer. There is no support in GCC
+for expressing an integer constant of type `__int128' for targets with
+`long long' integer less than 128 bits wide.

File: gcc.info, Node: Long Long, Next: Complex, Prev: __int128, Up: C Extensions
@@ -23658,26 +23827,27 @@ File: gcc.info, Node: Long Long, Next: Complex, Prev: __int128, Up: C Extens
ISO C99 supports data types for integers that are at least 64 bits wide,
and as an extension GCC supports them in C90 mode and in C++. Simply
-write 'long long int' for a signed integer, or 'unsigned long long int'
-for an unsigned integer. To make an integer constant of type 'long long
-int', add the suffix 'LL' to the integer. To make an integer constant
-of type 'unsigned long long int', add the suffix 'ULL' to the integer.
+write `long long int' for a signed integer, or `unsigned long long int'
+for an unsigned integer. To make an integer constant of type `long
+long int', add the suffix `LL' to the integer. To make an integer
+constant of type `unsigned long long int', add the suffix `ULL' to the
+integer.
You can use these types in arithmetic like any other integer types.
-Addition, subtraction, and bitwise boolean operations on these types are
-open-coded on all types of machines. Multiplication is open-coded if
-the machine supports a fullword-to-doubleword widening multiply
+Addition, subtraction, and bitwise boolean operations on these types
+are open-coded on all types of machines. Multiplication is open-coded
+if the machine supports a fullword-to-doubleword widening multiply
instruction. Division and shifts are open-coded only on machines that
provide special support. The operations that are not open-coded use
special library routines that come with GCC.
- There may be pitfalls when you use 'long long' types for function
-arguments without function prototypes. If a function expects type 'int'
-for its argument, and you pass a value of type 'long long int',
+ There may be pitfalls when you use `long long' types for function
+arguments without function prototypes. If a function expects type
+`int' for its argument, and you pass a value of type `long long int',
confusion results because the caller and the subroutine disagree about
-the number of bytes for the argument. Likewise, if the function expects
-'long long int' and you pass 'int'. The best way to avoid such problems
-is to use prototypes.
+the number of bytes for the argument. Likewise, if the function
+expects `long long int' and you pass `int'. The best way to avoid such
+problems is to use prototypes.

File: gcc.info, Node: Complex, Next: Floating Types, Prev: Long Long, Up: C Extensions
@@ -23686,37 +23856,37 @@ File: gcc.info, Node: Complex, Next: Floating Types, Prev: Long Long, Up: C
====================
ISO C99 supports complex floating data types, and as an extension GCC
-supports them in C90 mode and in C++. GCC also supports complex integer
-data types which are not part of ISO C99. You can declare complex types
-using the keyword '_Complex'. As an extension, the older GNU keyword
-'__complex__' is also supported.
-
- For example, '_Complex double x;' declares 'x' as a variable whose real
-part and imaginary part are both of type 'double'. '_Complex short int
-y;' declares 'y' to have real and imaginary parts of type 'short int';
-this is not likely to be useful, but it shows that the set of complex
-types is complete.
-
- To write a constant with a complex data type, use the suffix 'i' or 'j'
-(either one; they are equivalent). For example, '2.5fi' has type
-'_Complex float' and '3i' has type '_Complex int'. Such a constant
+supports them in C90 mode and in C++. GCC also supports complex
+integer data types which are not part of ISO C99. You can declare
+complex types using the keyword `_Complex'. As an extension, the older
+GNU keyword `__complex__' is also supported.
+
+ For example, `_Complex double x;' declares `x' as a variable whose
+real part and imaginary part are both of type `double'. `_Complex
+short int y;' declares `y' to have real and imaginary parts of type
+`short int'; this is not likely to be useful, but it shows that the set
+of complex types is complete.
+
+ To write a constant with a complex data type, use the suffix `i' or
+`j' (either one; they are equivalent). For example, `2.5fi' has type
+`_Complex float' and `3i' has type `_Complex int'. Such a constant
always has a pure imaginary value, but you can form any complex value
you like by adding one to a real constant. This is a GNU extension; if
you have an ISO C99 conforming C library (such as the GNU C Library),
and want to construct complex constants of floating type, you should
-include '<complex.h>' and use the macros 'I' or '_Complex_I' instead.
+include `<complex.h>' and use the macros `I' or `_Complex_I' instead.
To extract the real part of a complex-valued expression EXP, write
-'__real__ EXP'. Likewise, use '__imag__' to extract the imaginary part.
-This is a GNU extension; for values of floating type, you should use the
-ISO C99 functions 'crealf', 'creal', 'creall', 'cimagf', 'cimag' and
-'cimagl', declared in '<complex.h>' and also provided as built-in
-functions by GCC.
-
- The operator '~' performs complex conjugation when used on a value with
-a complex type. This is a GNU extension; for values of floating type,
-you should use the ISO C99 functions 'conjf', 'conj' and 'conjl',
-declared in '<complex.h>' and also provided as built-in functions by
+`__real__ EXP'. Likewise, use `__imag__' to extract the imaginary
+part. This is a GNU extension; for values of floating type, you should
+use the ISO C99 functions `crealf', `creal', `creall', `cimagf',
+`cimag' and `cimagl', declared in `<complex.h>' and also provided as
+built-in functions by GCC.
+
+ The operator `~' performs complex conjugation when used on a value
+with a complex type. This is a GNU extension; for values of floating
+type, you should use the ISO C99 functions `conjf', `conj' and `conjl',
+declared in `<complex.h>' and also provided as built-in functions by
GCC.
GCC can allocate complex automatic variables in a noncontiguous
@@ -23725,8 +23895,8 @@ the imaginary part is on the stack (or vice versa). Only the DWARF 2
debug info format can represent this, so use of DWARF 2 is recommended.
If you are using the stabs debug info format, GCC describes a
noncontiguous complex variable as if it were two separate variables of
-noncomplex type. If the variable's actual name is 'foo', the two
-fictitious variables are named 'foo$real' and 'foo$imag'. You can
+noncomplex type. If the variable's actual name is `foo', the two
+fictitious variables are named `foo$real' and `foo$imag'. You can
examine and set these two fictitious variables with your debugger.

@@ -23735,22 +23905,22 @@ File: gcc.info, Node: Floating Types, Next: Half-Precision, Prev: Complex, U
6.11 Additional Floating Types
==============================
-As an extension, GNU C supports additional floating types, '__float80'
-and '__float128' to support 80-bit ('XFmode') and 128-bit ('TFmode')
+As an extension, GNU C supports additional floating types, `__float80'
+and `__float128' to support 80-bit (`XFmode') and 128-bit (`TFmode')
floating types. Support for additional types includes the arithmetic
operators: add, subtract, multiply, divide; unary arithmetic operators;
relational operators; equality operators; and conversions to and from
-integer and other floating types. Use a suffix 'w' or 'W' in a literal
-constant of type '__float80' and 'q' or 'Q' for '_float128'. You can
+integer and other floating types. Use a suffix `w' or `W' in a literal
+constant of type `__float80' and `q' or `Q' for `_float128'. You can
declare complex types using the corresponding internal complex type,
-'XCmode' for '__float80' type and 'TCmode' for '__float128' type:
+`XCmode' for `__float80' type and `TCmode' for `__float128' type:
typedef _Complex float __attribute__((mode(TC))) _Complex128;
typedef _Complex float __attribute__((mode(XC))) _Complex80;
- Not all targets support additional floating-point types. '__float80'
-and '__float128' types are supported on x86 and IA-64 targets. The
-'__float128' type is supported on hppa HP-UX targets.
+ Not all targets support additional floating-point types. `__float80'
+and `__float128' types are supported on x86 and IA-64 targets. The
+`__float128' type is supported on hppa HP-UX targets.

File: gcc.info, Node: Half-Precision, Next: Decimal Float, Prev: Floating Types, Up: C Extensions
@@ -23759,44 +23929,45 @@ File: gcc.info, Node: Half-Precision, Next: Decimal Float, Prev: Floating Typ
==================================
On ARM targets, GCC supports half-precision (16-bit) floating point via
-the '__fp16' type. You must enable this type explicitly with the
-'-mfp16-format' command-line option in order to use it.
+the `__fp16' type. You must enable this type explicitly with the
+`-mfp16-format' command-line option in order to use it.
ARM supports two incompatible representations for half-precision
floating-point values. You must choose one of the representations and
use it consistently in your program.
- Specifying '-mfp16-format=ieee' selects the IEEE 754-2008 format. This
-format can represent normalized values in the range of 2^{-14} to 65504.
-There are 11 bits of significand precision, approximately 3 decimal
-digits.
+ Specifying `-mfp16-format=ieee' selects the IEEE 754-2008 format.
+This format can represent normalized values in the range of 2^-14 to
+65504. There are 11 bits of significand precision, approximately 3
+decimal digits.
- Specifying '-mfp16-format=alternative' selects the ARM alternative
-format. This representation is similar to the IEEE format, but does not
-support infinities or NaNs. Instead, the range of exponents is
+ Specifying `-mfp16-format=alternative' selects the ARM alternative
+format. This representation is similar to the IEEE format, but does
+not support infinities or NaNs. Instead, the range of exponents is
extended, so that this format can represent normalized values in the
-range of 2^{-14} to 131008.
+range of 2^-14 to 131008.
- The '__fp16' type is a storage format only. For purposes of arithmetic
-and other operations, '__fp16' values in C or C++ expressions are
-automatically promoted to 'float'. In addition, you cannot declare a
-function with a return value or parameters of type '__fp16'.
+ The `__fp16' type is a storage format only. For purposes of
+arithmetic and other operations, `__fp16' values in C or C++
+expressions are automatically promoted to `float'. In addition, you
+cannot declare a function with a return value or parameters of type
+`__fp16'.
- Note that conversions from 'double' to '__fp16' involve an intermediate
-conversion to 'float'. Because of rounding, this can sometimes produce
-a different result than a direct conversion.
+ Note that conversions from `double' to `__fp16' involve an
+intermediate conversion to `float'. Because of rounding, this can
+sometimes produce a different result than a direct conversion.
- ARM provides hardware support for conversions between '__fp16' and
-'float' values as an extension to VFP and NEON (Advanced SIMD). GCC
+ ARM provides hardware support for conversions between `__fp16' and
+`float' values as an extension to VFP and NEON (Advanced SIMD). GCC
generates code using these hardware instructions if you compile with
options to select an FPU that provides them; for example,
-'-mfpu=neon-fp16 -mfloat-abi=softfp', in addition to the '-mfp16-format'
-option to select a half-precision format.
+`-mfpu=neon-fp16 -mfloat-abi=softfp', in addition to the
+`-mfp16-format' option to select a half-precision format.
- Language-level support for the '__fp16' data type is independent of
+ Language-level support for the `__fp16' data type is independent of
whether GCC generates code using hardware floating-point instructions.
In cases where hardware support is not specified, GCC implements
-conversions between '__fp16' and 'float' values as library calls.
+conversions between `__fp16' and `float' values as library calls.

File: gcc.info, Node: Decimal Float, Next: Hex Floats, Prev: Half-Precision, Up: C Extensions
@@ -23804,23 +23975,23 @@ File: gcc.info, Node: Decimal Float, Next: Hex Floats, Prev: Half-Precision,
6.13 Decimal Floating Types
===========================
-As an extension, GNU C supports decimal floating types as defined in the
-N1312 draft of ISO/IEC WDTR24732. Support for decimal floating types in
-GCC will evolve as the draft technical report changes. Calling
-conventions for any target might also change. Not all targets support
-decimal floating types.
+As an extension, GNU C supports decimal floating types as defined in
+the N1312 draft of ISO/IEC WDTR24732. Support for decimal floating
+types in GCC will evolve as the draft technical report changes.
+Calling conventions for any target might also change. Not all targets
+support decimal floating types.
- The decimal floating types are '_Decimal32', '_Decimal64', and
-'_Decimal128'. They use a radix of ten, unlike the floating types
-'float', 'double', and 'long double' whose radix is not specified by the
-C standard but is usually two.
+ The decimal floating types are `_Decimal32', `_Decimal64', and
+`_Decimal128'. They use a radix of ten, unlike the floating types
+`float', `double', and `long double' whose radix is not specified by
+the C standard but is usually two.
Support for decimal floating types includes the arithmetic operators
add, subtract, multiply, divide; unary arithmetic operators; relational
operators; equality operators; and conversions to and from integer and
-other floating types. Use a suffix 'df' or 'DF' in a literal constant
-of type '_Decimal32', 'dd' or 'DD' for '_Decimal64', and 'dl' or 'DL'
-for '_Decimal128'.
+other floating types. Use a suffix `df' or `DF' in a literal constant
+of type `_Decimal32', `dd' or `DD' for `_Decimal64', and `dl' or `DL'
+for `_Decimal128'.
GCC support of decimal float as specified by the draft technical report
is incomplete:
@@ -23831,12 +24002,12 @@ is incomplete:
technical report.
* GCC does not provide the C library functionality associated with
- 'math.h', 'fenv.h', 'stdio.h', 'stdlib.h', and 'wchar.h', which
+ `math.h', `fenv.h', `stdio.h', `stdlib.h', and `wchar.h', which
must come from a separate C library implementation. Because of
- this the GNU C compiler does not define macro '__STDC_DEC_FP__' to
+ this the GNU C compiler does not define macro `__STDC_DEC_FP__' to
indicate that the implementation conforms to the technical report.
- Types '_Decimal32', '_Decimal64', and '_Decimal128' are supported by
+ Types `_Decimal32', `_Decimal64', and `_Decimal128' are supported by
the DWARF 2 debug information format.

@@ -23846,20 +24017,20 @@ File: gcc.info, Node: Hex Floats, Next: Fixed-Point, Prev: Decimal Float, Up
===============
ISO C99 supports floating-point numbers written not only in the usual
-decimal notation, such as '1.55e1', but also numbers such as '0x1.fp3'
-written in hexadecimal format. As a GNU extension, GCC supports this in
-C90 mode (except in some cases when strictly conforming) and in C++. In
-that format the '0x' hex introducer and the 'p' or 'P' exponent field
-are mandatory. The exponent is a decimal number that indicates the
-power of 2 by which the significant part is multiplied. Thus '0x1.f' is
-1 15/16, 'p3' multiplies it by 8, and the value of '0x1.fp3' is the same
-as '1.55e1'.
+decimal notation, such as `1.55e1', but also numbers such as `0x1.fp3'
+written in hexadecimal format. As a GNU extension, GCC supports this
+in C90 mode (except in some cases when strictly conforming) and in C++.
+In that format the `0x' hex introducer and the `p' or `P' exponent
+field are mandatory. The exponent is a decimal number that indicates
+the power of 2 by which the significant part is multiplied. Thus
+`0x1.f' is 1 15/16, `p3' multiplies it by 8, and the value of `0x1.fp3'
+is the same as `1.55e1'.
Unlike for floating-point numbers in the decimal notation the exponent
is always required in the hexadecimal notation. Otherwise the compiler
-would not be able to resolve the ambiguity of, e.g., '0x1.f'. This
-could mean '1.0f' or '1.9375' since 'f' is also the extension for
-floating-point constants of type 'float'.
+would not be able to resolve the ambiguity of, e.g., `0x1.f'. This
+could mean `1.0f' or `1.9375' since `f' is also the extension for
+floating-point constants of type `float'.

File: gcc.info, Node: Fixed-Point, Next: Named Address Spaces, Prev: Hex Floats, Up: C Extensions
@@ -23873,55 +24044,77 @@ will evolve as the draft technical report changes. Calling conventions
for any target might also change. Not all targets support fixed-point
types.
- The fixed-point types are 'short _Fract', '_Fract', 'long _Fract',
-'long long _Fract', 'unsigned short _Fract', 'unsigned _Fract',
-'unsigned long _Fract', 'unsigned long long _Fract', '_Sat short
-_Fract', '_Sat _Fract', '_Sat long _Fract', '_Sat long long _Fract',
-'_Sat unsigned short _Fract', '_Sat unsigned _Fract', '_Sat unsigned
-long _Fract', '_Sat unsigned long long _Fract', 'short _Accum',
-'_Accum', 'long _Accum', 'long long _Accum', 'unsigned short _Accum',
-'unsigned _Accum', 'unsigned long _Accum', 'unsigned long long _Accum',
-'_Sat short _Accum', '_Sat _Accum', '_Sat long _Accum', '_Sat long long
-_Accum', '_Sat unsigned short _Accum', '_Sat unsigned _Accum', '_Sat
-unsigned long _Accum', '_Sat unsigned long long _Accum'.
+ The fixed-point types are `short _Fract', `_Fract', `long _Fract',
+`long long _Fract', `unsigned short _Fract', `unsigned _Fract',
+`unsigned long _Fract', `unsigned long long _Fract', `_Sat short
+_Fract', `_Sat _Fract', `_Sat long _Fract', `_Sat long long _Fract',
+`_Sat unsigned short _Fract', `_Sat unsigned _Fract', `_Sat unsigned
+long _Fract', `_Sat unsigned long long _Fract', `short _Accum',
+`_Accum', `long _Accum', `long long _Accum', `unsigned short _Accum',
+`unsigned _Accum', `unsigned long _Accum', `unsigned long long _Accum',
+`_Sat short _Accum', `_Sat _Accum', `_Sat long _Accum', `_Sat long long
+_Accum', `_Sat unsigned short _Accum', `_Sat unsigned _Accum', `_Sat
+unsigned long _Accum', `_Sat unsigned long long _Accum'.
Fixed-point data values contain fractional and optional integral parts.
The format of fixed-point data varies and depends on the target machine.
Support for fixed-point types includes:
- * prefix and postfix increment and decrement operators ('++', '--')
- * unary arithmetic operators ('+', '-', '!')
- * binary arithmetic operators ('+', '-', '*', '/')
- * binary shift operators ('<<', '>>')
- * relational operators ('<', '<=', '>=', '>')
- * equality operators ('==', '!=')
- * assignment operators ('+=', '-=', '*=', '/=', '<<=', '>>=')
+ * prefix and postfix increment and decrement operators (`++', `--')
+
+ * unary arithmetic operators (`+', `-', `!')
+
+ * binary arithmetic operators (`+', `-', `*', `/')
+
+ * binary shift operators (`<<', `>>')
+
+ * relational operators (`<', `<=', `>=', `>')
+
+ * equality operators (`==', `!=')
+
+ * assignment operators (`+=', `-=', `*=', `/=', `<<=', `>>=')
+
* conversions to and from integer, floating-point, or fixed-point
types
Use a suffix in a fixed-point literal constant:
- * 'hr' or 'HR' for 'short _Fract' and '_Sat short _Fract'
- * 'r' or 'R' for '_Fract' and '_Sat _Fract'
- * 'lr' or 'LR' for 'long _Fract' and '_Sat long _Fract'
- * 'llr' or 'LLR' for 'long long _Fract' and '_Sat long long _Fract'
- * 'uhr' or 'UHR' for 'unsigned short _Fract' and '_Sat unsigned short
- _Fract'
- * 'ur' or 'UR' for 'unsigned _Fract' and '_Sat unsigned _Fract'
- * 'ulr' or 'ULR' for 'unsigned long _Fract' and '_Sat unsigned long
+ * `hr' or `HR' for `short _Fract' and `_Sat short _Fract'
+
+ * `r' or `R' for `_Fract' and `_Sat _Fract'
+
+ * `lr' or `LR' for `long _Fract' and `_Sat long _Fract'
+
+ * `llr' or `LLR' for `long long _Fract' and `_Sat long long _Fract'
+
+ * `uhr' or `UHR' for `unsigned short _Fract' and `_Sat unsigned
+ short _Fract'
+
+ * `ur' or `UR' for `unsigned _Fract' and `_Sat unsigned _Fract'
+
+ * `ulr' or `ULR' for `unsigned long _Fract' and `_Sat unsigned long
_Fract'
- * 'ullr' or 'ULLR' for 'unsigned long long _Fract' and '_Sat unsigned
- long long _Fract'
- * 'hk' or 'HK' for 'short _Accum' and '_Sat short _Accum'
- * 'k' or 'K' for '_Accum' and '_Sat _Accum'
- * 'lk' or 'LK' for 'long _Accum' and '_Sat long _Accum'
- * 'llk' or 'LLK' for 'long long _Accum' and '_Sat long long _Accum'
- * 'uhk' or 'UHK' for 'unsigned short _Accum' and '_Sat unsigned short
- _Accum'
- * 'uk' or 'UK' for 'unsigned _Accum' and '_Sat unsigned _Accum'
- * 'ulk' or 'ULK' for 'unsigned long _Accum' and '_Sat unsigned long
+
+ * `ullr' or `ULLR' for `unsigned long long _Fract' and `_Sat
+ unsigned long long _Fract'
+
+ * `hk' or `HK' for `short _Accum' and `_Sat short _Accum'
+
+ * `k' or `K' for `_Accum' and `_Sat _Accum'
+
+ * `lk' or `LK' for `long _Accum' and `_Sat long _Accum'
+
+ * `llk' or `LLK' for `long long _Accum' and `_Sat long long _Accum'
+
+ * `uhk' or `UHK' for `unsigned short _Accum' and `_Sat unsigned
+ short _Accum'
+
+ * `uk' or `UK' for `unsigned _Accum' and `_Sat unsigned _Accum'
+
+ * `ulk' or `ULK' for `unsigned long _Accum' and `_Sat unsigned long
_Accum'
- * 'ullk' or 'ULLK' for 'unsigned long long _Accum' and '_Sat unsigned
- long long _Accum'
+
+ * `ullk' or `ULLK' for `unsigned long long _Accum' and `_Sat
+ unsigned long long _Accum'
GCC support of fixed-point types as specified by the draft technical
report is incomplete:
@@ -23941,12 +24134,12 @@ File: gcc.info, Node: Named Address Spaces, Next: Zero Length, Prev: Fixed-Po
As an extension, GNU C supports named address spaces as defined in the
N1275 draft of ISO/IEC DTR 18037. Support for named address spaces in
GCC will evolve as the draft technical report changes. Calling
-conventions for any target might also change. At present, only the AVR,
-SPU, M32C, and RL78 targets support address spaces other than the
+conventions for any target might also change. At present, only the
+AVR, SPU, M32C, and RL78 targets support address spaces other than the
generic address space.
Address space identifiers may be used exactly like any other C type
-qualifier (e.g., 'const' or 'volatile'). See the N1275 document for
+qualifier (e.g., `const' or `volatile'). See the N1275 document for
more details.
6.16.1 AVR Named Address Spaces
@@ -23954,38 +24147,38 @@ more details.
On the AVR target, there are several address spaces that can be used in
order to put read-only data into the flash memory and access that data
-by means of the special instructions 'LPM' or 'ELPM' needed to read from
-flash.
+by means of the special instructions `LPM' or `ELPM' needed to read
+from flash.
Per default, any data including read-only data is located in RAM (the
generic address space) so that non-generic address spaces are needed to
locate read-only data in flash memory _and_ to generate the right
instructions to access this data without using (inline) assembler code.
-'__flash'
- The '__flash' qualifier locates data in the '.progmem.data'
- section. Data is read using the 'LPM' instruction. Pointers to
+`__flash'
+ The `__flash' qualifier locates data in the `.progmem.data'
+ section. Data is read using the `LPM' instruction. Pointers to
this address space are 16 bits wide.
-'__flash1'
-'__flash2'
-'__flash3'
-'__flash4'
-'__flash5'
+`__flash1'
+`__flash2'
+`__flash3'
+`__flash4'
+`__flash5'
These are 16-bit address spaces locating data in section
- '.progmemN.data' where N refers to address space '__flashN'. The
- compiler sets the 'RAMPZ' segment register appropriately before
- reading data by means of the 'ELPM' instruction.
+ `.progmemN.data' where N refers to address space `__flashN'. The
+ compiler sets the `RAMPZ' segment register appropriately before
+ reading data by means of the `ELPM' instruction.
-'__memx'
+`__memx'
This is a 24-bit address space that linearizes flash and RAM: If
- the high bit of the address is set, data is read from RAM using the
- lower two bytes as RAM address. If the high bit of the address is
- clear, data is read from flash with 'RAMPZ' set according to the
- high byte of the address. *Note '__builtin_avr_flash_segment': AVR
- Built-in Functions.
+ the high bit of the address is set, data is read from RAM using
+ the lower two bytes as RAM address. If the high bit of the
+ address is clear, data is read from flash with `RAMPZ' set
+ according to the high byte of the address. *Note
+ `__builtin_avr_flash_segment': AVR Built-in Functions.
- Objects in this address space are located in '.progmemx.data'.
+ Objects in this address space are located in `.progmemx.data'.
Example
@@ -24033,33 +24226,33 @@ not:
}
#endif /* __FLASH */
-Notice that attribute *note 'progmem': AVR Variable Attributes. locates
-data in flash but accesses to these data read from generic address
-space, i.e. from RAM, so that you need special accessors like
-'pgm_read_byte' from AVR-LibC (http://nongnu.org/avr-libc/user-manual/)
-together with attribute 'progmem'.
+Notice that attribute *note `progmem': AVR Variable Attributes.
+locates data in flash but accesses to these data read from generic
+address space, i.e. from RAM, so that you need special accessors like
+`pgm_read_byte' from AVR-LibC (http://nongnu.org/avr-libc/user-manual/)
+together with attribute `progmem'.
Limitations and caveats
- * Reading across the 64 KiB section boundary of the '__flash' or
- '__flashN' address spaces shows undefined behavior. The only
- address space that supports reading across the 64 KiB flash segment
- boundaries is '__memx'.
+ * Reading across the 64 KiB section boundary of the `__flash' or
+ `__flashN' address spaces shows undefined behavior. The only
+ address space that supports reading across the 64 KiB flash
+ segment boundaries is `__memx'.
- * If you use one of the '__flashN' address spaces you must arrange
- your linker script to locate the '.progmemN.data' sections
+ * If you use one of the `__flashN' address spaces you must arrange
+ your linker script to locate the `.progmemN.data' sections
according to your needs.
* Any data or pointers to the non-generic address spaces must be
- qualified as 'const', i.e. as read-only data. This still applies
+ qualified as `const', i.e. as read-only data. This still applies
if the data in one of these address spaces like software version
- number or calibration lookup table are intended to be changed after
- load time by, say, a boot loader. In this case the right
- qualification is 'const' 'volatile' so that the compiler must not
+ number or calibration lookup table are intended to be changed
+ after load time by, say, a boot loader. In this case the right
+ qualification is `const' `volatile' so that the compiler must not
optimize away known values or insert them as immediates into
operands of instructions.
- * The following code initializes a variable 'pfoo' located in static
+ * The following code initializes a variable `pfoo' located in static
storage with a 24-bit address:
extern const __memx char foo;
const __memx void *pfoo = &foo;
@@ -24067,18 +24260,19 @@ Limitations and caveats
Such code requires at least binutils 2.23, see
PR13503 (http://sourceware.org/PR13503).
+
6.16.2 M32C Named Address Spaces
--------------------------------
On the M32C target, with the R8C and M16C CPU variants, variables
-qualified with '__far' are accessed using 32-bit addresses in order to
-access memory beyond the first 64 Ki bytes. If '__far' is used with the
-M32CM or M32C CPU variants, it has no effect.
+qualified with `__far' are accessed using 32-bit addresses in order to
+access memory beyond the first 64 Ki bytes. If `__far' is used with
+the M32CM or M32C CPU variants, it has no effect.
6.16.3 RL78 Named Address Spaces
--------------------------------
-On the RL78 target, variables qualified with '__far' are accessed with
+On the RL78 target, variables qualified with `__far' are accessed with
32-bit pointers (20-bit addresses) rather than the default 16-bit
addresses. Non-far variables are assumed to appear in the topmost
64 KiB of the address space.
@@ -24087,14 +24281,14 @@ addresses. Non-far variables are assumed to appear in the topmost
-------------------------------
On the SPU target variables may be declared as belonging to another
-address space by qualifying the type with the '__ea' address space
+address space by qualifying the type with the `__ea' address space
identifier:
extern int __ea i;
-The compiler generates special code to access the variable 'i'. It may
-use runtime library support, or generate special machine instructions to
-access that address space.
+The compiler generates special code to access the variable `i'. It may
+use runtime library support, or generate special machine instructions
+to access that address space.

File: gcc.info, Node: Zero Length, Next: Empty Structures, Prev: Named Address Spaces, Up: C Extensions
@@ -24115,35 +24309,36 @@ variable-length object:
malloc (sizeof (struct line) + this_length);
thisline->length = this_length;
- In ISO C90, you would have to give 'contents' a length of 1, which
-means either you waste space or complicate the argument to 'malloc'.
+ In ISO C90, you would have to give `contents' a length of 1, which
+means either you waste space or complicate the argument to `malloc'.
In ISO C99, you would use a "flexible array member", which is slightly
different in syntax and semantics:
- * Flexible array members are written as 'contents[]' without the '0'.
+ * Flexible array members are written as `contents[]' without the `0'.
- * Flexible array members have incomplete type, and so the 'sizeof'
+ * Flexible array members have incomplete type, and so the `sizeof'
operator may not be applied. As a quirk of the original
- implementation of zero-length arrays, 'sizeof' evaluates to zero.
+ implementation of zero-length arrays, `sizeof' evaluates to zero.
* Flexible array members may only appear as the last member of a
- 'struct' that is otherwise non-empty.
+ `struct' that is otherwise non-empty.
* A structure containing a flexible array member, or a union
containing such a structure (possibly recursively), may not be a
member of a structure or an element of an array. (However, these
uses are permitted by GCC as extensions.)
- Non-empty initialization of zero-length arrays is treated like any case
-where there are more initializer elements than the array holds, in that
-a suitable warning about "excess elements in array" is given, and the
-excess elements (all of them, in this case) are ignored.
+ Non-empty initialization of zero-length arrays is treated like any
+case where there are more initializer elements than the array holds, in
+that a suitable warning about "excess elements in array" is given, and
+the excess elements (all of them, in this case) are ignored.
GCC allows static initialization of flexible array members. This is
-equivalent to defining a new structure containing the original structure
-followed by an array of sufficient size to contain the data. E.g. in
-the following, 'f1' is constructed as if it were declared like 'f2'.
+equivalent to defining a new structure containing the original
+structure followed by an array of sufficient size to contain the data.
+E.g. in the following, `f1' is constructed as if it were declared like
+`f2'.
struct f1 {
int x; int y[];
@@ -24153,18 +24348,18 @@ the following, 'f1' is constructed as if it were declared like 'f2'.
struct f1 f1; int data[3];
} f2 = { { 1 }, { 2, 3, 4 } };
-The convenience of this extension is that 'f1' has the desired type,
-eliminating the need to consistently refer to 'f2.f1'.
+The convenience of this extension is that `f1' has the desired type,
+eliminating the need to consistently refer to `f2.f1'.
This has symmetry with normal static arrays, in that an array of
-unknown size is also written with '[]'.
+unknown size is also written with `[]'.
Of course, this extension only makes sense if the extra data comes at
-the end of a top-level object, as otherwise we would be overwriting data
-at subsequent offsets. To avoid undue complication and confusion with
-initialization of deeply nested arrays, we simply disallow any non-empty
-initialization except when the structure is the top-level object. For
-example:
+the end of a top-level object, as otherwise we would be overwriting
+data at subsequent offsets. To avoid undue complication and confusion
+with initialization of deeply nested arrays, we simply disallow any
+non-empty initialization except when the structure is the top-level
+object. For example:
struct foo { int x; int y[]; };
struct bar { struct foo z; };
@@ -24186,8 +24381,8 @@ GCC permits a C structure to have no members:
};
The structure has size zero. In C++, empty structures are part of the
-language. G++ treats empty structures as if they had a single member of
-type 'char'.
+language. G++ treats empty structures as if they had a single member
+of type `char'.

File: gcc.info, Node: Variable Length, Next: Variadic Macros, Prev: Empty Structures, Up: C Extensions
@@ -24224,17 +24419,17 @@ structure or a union. For example:
struct S { int x[n]; };
}
- You can use the function 'alloca' to get an effect much like
-variable-length arrays. The function 'alloca' is available in many
+ You can use the function `alloca' to get an effect much like
+variable-length arrays. The function `alloca' is available in many
other C implementations (but not in all). On the other hand,
variable-length arrays are more elegant.
There are other differences between these two methods. Space allocated
-with 'alloca' exists until the containing _function_ returns. The space
-for a variable-length array is deallocated as soon as the array name's
-scope ends. (If you use both variable-length arrays and 'alloca' in the
-same function, deallocation of a variable-length array also deallocates
-anything more recently allocated with 'alloca'.)
+with `alloca' exists until the containing _function_ returns. The
+space for a variable-length array is deallocated as soon as the array
+name's scope ends. (If you use both variable-length arrays and
+`alloca' in the same function, deallocation of a variable-length array
+also deallocates anything more recently allocated with `alloca'.)
You can also use variable-length arrays as arguments to functions:
@@ -24246,7 +24441,7 @@ anything more recently allocated with 'alloca'.)
The length of an array is computed once when the storage is allocated
and is remembered for the scope of the array in case you access it with
-'sizeof'.
+`sizeof'.
If you want to pass the array first and the length afterward, you can
use a forward declaration in the parameter list--another GNU extension.
@@ -24257,9 +24452,9 @@ use a forward declaration in the parameter list--another GNU extension.
/* ... */
}
- The 'int len' before the semicolon is a "parameter forward
-declaration", and it serves the purpose of making the name 'len' known
-when the declaration of 'data' is parsed.
+ The `int len' before the semicolon is a "parameter forward
+declaration", and it serves the purpose of making the name `len' known
+when the declaration of `data' is parsed.
You can write any number of such parameter forward declarations in the
parameter list. They can be separated by commas or semicolons, but the
@@ -24281,11 +24476,11 @@ example:
#define debug(format, ...) fprintf (stderr, format, __VA_ARGS__)
-Here '...' is a "variable argument". In the invocation of such a macro,
-it represents the zero or more tokens until the closing parenthesis that
-ends the invocation, including any commas. This set of tokens replaces
-the identifier '__VA_ARGS__' in the macro body wherever it appears. See
-the CPP manual for more information.
+Here `...' is a "variable argument". In the invocation of such a
+macro, it represents the zero or more tokens until the closing
+parenthesis that ends the invocation, including any commas. This set of
+tokens replaces the identifier `__VA_ARGS__' in the macro body wherever
+it appears. See the CPP manual for more information.
GCC has long supported variadic macros, and used a different syntax
that allowed you to give a name to the variable arguments just like any
@@ -24301,8 +24496,8 @@ be used with either of the above forms of macro definition.
In standard C, you are not allowed to leave the variable argument out
entirely; but you are allowed to pass an empty argument. For example,
-this invocation is invalid in ISO C, because there is no comma after the
-string:
+this invocation is invalid in ISO C, because there is no comma after
+the string:
debug ("A message")
@@ -24312,12 +24507,12 @@ the expansion of the macro still has the extra comma after the format
string.
To help solve this problem, CPP behaves specially for variable
-arguments used with the token paste operator, '##'. If instead you
+arguments used with the token paste operator, `##'. If instead you
write
#define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__)
-and if the variable arguments are omitted or empty, the '##' operator
+and if the variable arguments are omitted or empty, the `##' operator
causes the preprocessor to remove the comma before it. If you do
provide some variable arguments in your macro invocation, GNU CPP does
not complain about the paste operation and instead places the variable
@@ -24330,16 +24525,16 @@ File: gcc.info, Node: Escaped Newlines, Next: Subscripting, Prev: Variadic Ma
6.21 Slightly Looser Rules for Escaped Newlines
===============================================
-The preprocessor treatment of escaped newlines is more relaxed than that
-specified by the C90 standard, which requires the newline to immediately
-follow a backslash. GCC's implementation allows whitespace in the form
-of spaces, horizontal and vertical tabs, and form feeds between the
-backslash and the subsequent newline. The preprocessor issues a
-warning, but treats it as a valid escaped newline and combines the two
-lines to form a single logical line. This works within comments and
-tokens, as well as between tokens. Comments are _not_ treated as
-whitespace for the purposes of this relaxation, since they have not yet
-been replaced with spaces.
+The preprocessor treatment of escaped newlines is more relaxed than
+that specified by the C90 standard, which requires the newline to
+immediately follow a backslash. GCC's implementation allows whitespace
+in the form of spaces, horizontal and vertical tabs, and form feeds
+between the backslash and the subsequent newline. The preprocessor
+issues a warning, but treats it as a valid escaped newline and combines
+the two lines to form a single logical line. This works within
+comments and tokens, as well as between tokens. Comments are _not_
+treated as whitespace for the purposes of this relaxation, since they
+have not yet been replaced with spaces.

File: gcc.info, Node: Subscripting, Next: Pointer Arith, Prev: Escaped Newlines, Up: C Extensions
@@ -24347,12 +24542,12 @@ File: gcc.info, Node: Subscripting, Next: Pointer Arith, Prev: Escaped Newlin
6.22 Non-Lvalue Arrays May Have Subscripts
==========================================
-In ISO C99, arrays that are not lvalues still decay to pointers, and may
-be subscripted, although they may not be modified or used after the next
-sequence point and the unary '&' operator may not be applied to them.
-As an extension, GNU C allows such arrays to be subscripted in C90 mode,
-though otherwise they do not decay to pointers outside C99 mode. For
-example, this is valid in GNU C though not valid in C90:
+In ISO C99, arrays that are not lvalues still decay to pointers, and
+may be subscripted, although they may not be modified or used after the
+next sequence point and the unary `&' operator may not be applied to
+them. As an extension, GNU C allows such arrays to be subscripted in
+C90 mode, though otherwise they do not decay to pointers outside C99
+mode. For example, this is valid in GNU C though not valid in C90:
struct foo {int a[4];};
@@ -24366,18 +24561,18 @@ example, this is valid in GNU C though not valid in C90:

File: gcc.info, Node: Pointer Arith, Next: Pointers to Arrays, Prev: Subscripting, Up: C Extensions
-6.23 Arithmetic on 'void'- and Function-Pointers
+6.23 Arithmetic on `void'- and Function-Pointers
================================================
In GNU C, addition and subtraction operations are supported on pointers
-to 'void' and on pointers to functions. This is done by treating the
-size of a 'void' or of a function as 1.
+to `void' and on pointers to functions. This is done by treating the
+size of a `void' or of a function as 1.
- A consequence of this is that 'sizeof' is also allowed on 'void' and on
-function types, and returns 1.
+ A consequence of this is that `sizeof' is also allowed on `void' and
+on function types, and returns 1.
- The option '-Wpointer-arith' requests a warning if these extensions are
-used.
+ The option `-Wpointer-arith' requests a warning if these extensions
+are used.

File: gcc.info, Node: Pointers to Arrays, Next: Initializers, Prev: Pointer Arith, Up: C Extensions
@@ -24385,11 +24580,12 @@ File: gcc.info, Node: Pointers to Arrays, Next: Initializers, Prev: Pointer A
6.24 Pointers to Arrays with Qualifiers Work as Expected
========================================================
-In GNU C, pointers to arrays with qualifiers work similar to pointers to
-other qualified types. For example, a value of type 'int (*)[5]' can be
-used to initialize a variable of type 'const int (*)[5]'. These types
-are incompatible in ISO C because the 'const' qualifier is formally
-attached to the element type of the array and not the array itself.
+In GNU C, pointers to arrays with qualifiers work similar to pointers
+to other qualified types. For example, a value of type `int (*)[5]' can
+be used to initialize a variable of type `const int (*)[5]'. These
+types are incompatible in ISO C because the `const' qualifier is
+formally attached to the element type of the array and not the array
+itself.
extern void
transpose (int N, int M, double out[M][N], const double in[N][M]);
@@ -24404,10 +24600,10 @@ File: gcc.info, Node: Initializers, Next: Compound Literals, Prev: Pointers t
6.25 Non-Constant Initializers
==============================
-As in standard C++ and ISO C99, the elements of an aggregate initializer
-for an automatic variable are not required to be constant expressions in
-GNU C. Here is an example of an initializer with run-time varying
-elements:
+As in standard C++ and ISO C99, the elements of an aggregate
+initializer for an automatic variable are not required to be constant
+expressions in GNU C. Here is an example of an initializer with
+run-time varying elements:
foo (float f, float g)
{
@@ -24428,12 +24624,12 @@ initializer; it is an lvalue. As an extension, GCC supports compound
literals in C90 mode and in C++, though the semantics are somewhat
different in C++.
- Usually, the specified type is a structure. Assume that 'struct foo'
-and 'structure' are declared as shown:
+ Usually, the specified type is a structure. Assume that `struct foo'
+and `structure' are declared as shown:
struct foo {int a; char b[2];} structure;
-Here is an example of constructing a 'struct foo' with a compound
+Here is an example of constructing a `struct foo' with a compound
literal:
structure = ((struct foo) {x + y, 'a', 0});
@@ -24458,13 +24654,13 @@ initializer, as shown here:
but then the compound literal is equivalent to a cast.
As a GNU extension, GCC allows initialization of objects with static
-storage duration by compound literals (which is not possible in ISO C99,
-because the initializer is not a constant). It is handled as if the
-object is initialized only with the bracket enclosed list if the types
-of the compound literal and the object match. The initializer list of
-the compound literal must be constant. If the object being initialized
-has array type of unknown size, the size is determined by compound
-literal size.
+storage duration by compound literals (which is not possible in ISO
+C99, because the initializer is not a constant). It is handled as if
+the object is initialized only with the bracket enclosed list if the
+types of the compound literal and the object match. The initializer
+list of the compound literal must be constant. If the object being
+initialized has array type of unknown size, the size is determined by
+compound literal size.
static struct foo x = (struct foo) {1, 'a', 'b'};
static int y[] = (int []) {1, 2, 3};
@@ -24477,18 +24673,19 @@ The above lines are equivalent to the following:
In C, a compound literal designates an unnamed object with static or
automatic storage duration. In C++, a compound literal designates a
-temporary object, which only lives until the end of its full-expression.
-As a result, well-defined C code that takes the address of a subobject
-of a compound literal can be undefined in C++, so the C++ compiler
-rejects the conversion of a temporary array to a pointer. For instance,
-if the array compound literal example above appeared inside a function,
-any subsequent use of 'foo' in C++ has undefined behavior because the
-lifetime of the array ends after the declaration of 'foo'.
+temporary object, which only lives until the end of its
+full-expression. As a result, well-defined C code that takes the
+address of a subobject of a compound literal can be undefined in C++,
+so the C++ compiler rejects the conversion of a temporary array to a
+pointer. For instance, if the array compound literal example above
+appeared inside a function, any subsequent use of `foo' in C++ has
+undefined behavior because the lifetime of the array ends after the
+declaration of `foo'.
As an optimization, the C++ compiler sometimes gives array compound
literals longer lifetimes: when the array either appears outside a
-function or has const-qualified type. If 'foo' and its initializer had
-elements of 'char *const' type rather than 'char *', or if 'foo' were a
+function or has const-qualified type. If `foo' and its initializer had
+elements of `char *const' type rather than `char *', or if `foo' were a
global variable, the array would have static storage duration. But it
is probably safest just to avoid the use of array compound literals in
code compiled as C++.
@@ -24508,7 +24705,7 @@ indices or structure field names they apply to, and GNU C allows this as
an extension in C90 mode as well. This extension is not implemented in
GNU C++.
- To specify an array index, write '[INDEX] =' before the element value.
+ To specify an array index, write `[INDEX] =' before the element value.
For example,
int a[6] = { [4] = 29, [2] = 15 };
@@ -24521,10 +24718,10 @@ The index values must be constant expressions, even if the array being
initialized is automatic.
An alternative syntax for this that has been obsolete since GCC 2.5 but
-GCC still accepts is to write '[INDEX]' before the element value, with
-no '='.
+GCC still accepts is to write `[INDEX]' before the element value, with
+no `='.
- To initialize a range of elements to the same value, write '[FIRST ...
+ To initialize a range of elements to the same value, write `[FIRST ...
LAST] = VALUE'. This is a GNU extension. For example,
int widths[] = { [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 };
@@ -24536,7 +24733,7 @@ Note that the length of the array is the highest value specified plus
one.
In a structure initializer, specify the name of a field to initialize
-with '.FIELDNAME =' before the element value. For example, given the
+with `.FIELDNAME =' before the element value. For example, given the
following structure,
struct point { int x, y; };
@@ -24550,25 +24747,25 @@ is equivalent to
struct point p = { xvalue, yvalue };
Another syntax that has the same meaning, obsolete since GCC 2.5, is
-'FIELDNAME:', as shown here:
+`FIELDNAME:', as shown here:
struct point p = { y: yvalue, x: xvalue };
Omitted field members are implicitly initialized the same as objects
that have static storage duration.
- The '[INDEX]' or '.FIELDNAME' is known as a "designator". You can also
-use a designator (or the obsolete colon syntax) when initializing a
-union, to specify which element of the union should be used. For
+ The `[INDEX]' or `.FIELDNAME' is known as a "designator". You can
+also use a designator (or the obsolete colon syntax) when initializing
+a union, to specify which element of the union should be used. For
example,
union foo { int i; double d; };
union foo f = { .d = 4 };
-converts 4 to a 'double' to store it in the union using the second
-element. By contrast, casting 4 to type 'union foo' stores it into the
-union as the integer 'i', since it is an integer. (*Note Cast to
+converts 4 to a `double' to store it in the union using the second
+element. By contrast, casting 4 to type `union foo' stores it into the
+union as the integer `i', since it is an integer. (*Note Cast to
Union::.)
You can combine this technique of naming elements with ordinary C
@@ -24582,17 +24779,19 @@ is equivalent to
int a[6] = { 0, v1, v2, 0, v4, 0 };
- Labeling the elements of an array initializer is especially useful when
-the indices are characters or belong to an 'enum' type. For example:
+ Labeling the elements of an array initializer is especially useful
+when the indices are characters or belong to an `enum' type. For
+example:
int whitespace[256]
= { [' '] = 1, ['\t'] = 1, ['\h'] = 1,
['\f'] = 1, ['\n'] = 1, ['\r'] = 1 };
- You can also write a series of '.FIELDNAME' and '[INDEX]' designators
-before an '=' to specify a nested subobject to initialize; the list is
-taken relative to the subobject corresponding to the closest surrounding
-brace pair. For example, with the 'struct point' declaration above:
+ You can also write a series of `.FIELDNAME' and `[INDEX]' designators
+before an `=' to specify a nested subobject to initialize; the list is
+taken relative to the subobject corresponding to the closest
+surrounding brace pair. For example, with the `struct point'
+declaration above:
struct point ptarray[10] = { [2].y = yv2, [2].x = xv2, [0].x = xv0 };
@@ -24607,19 +24806,19 @@ File: gcc.info, Node: Case Ranges, Next: Cast to Union, Prev: Designated Init
6.28 Case Ranges
================
-You can specify a range of consecutive values in a single 'case' label,
+You can specify a range of consecutive values in a single `case' label,
like this:
case LOW ... HIGH:
-This has the same effect as the proper number of individual 'case'
+This has the same effect as the proper number of individual `case'
labels, one for each integer value from LOW to HIGH, inclusive.
This feature is especially useful for ranges of ASCII character codes:
case 'A' ... 'Z':
- *Be careful:* Write spaces around the '...', for otherwise it may be
+ *Be careful:* Write spaces around the `...', for otherwise it may be
parsed wrong when you use it with integer values. For example, write
this:
@@ -24636,10 +24835,10 @@ File: gcc.info, Node: Cast to Union, Next: Mixed Declarations, Prev: Case Ran
=========================
A cast to union type is similar to other casts, except that the type
-specified is a union type. You can specify the type either with 'union
-TAG' or with a typedef name. A cast to union is actually a constructor,
-not a cast, and hence does not yield an lvalue like normal casts.
-(*Note Compound Literals::.)
+specified is a union type. You can specify the type either with `union
+TAG' or with a typedef name. A cast to union is actually a
+constructor, not a cast, and hence does not yield an lvalue like normal
+casts. (*Note Compound Literals::.)
The types that may be cast to the union type are those of the members
of the union. Thus, given the following union and variables:
@@ -24648,7 +24847,7 @@ of the union. Thus, given the following union and variables:
int x;
double y;
-both 'x' and 'y' can be cast to type 'union foo'.
+both `x' and `y' can be cast to type `union foo'.
Using the cast as the right-hand side of an assignment to a variable of
union type is equivalent to storing in a member of the union:
@@ -24692,94 +24891,94 @@ In GNU C, you declare certain things about functions called in your
program which help the compiler optimize function calls and check your
code more carefully.
- The keyword '__attribute__' allows you to specify special attributes
+ The keyword `__attribute__' allows you to specify special attributes
when making a declaration. This keyword is followed by an attribute
specification inside double parentheses. The following attributes are
-currently defined for functions on all targets: 'aligned', 'alloc_size',
-'alloc_align', 'assume_aligned', 'noreturn', 'returns_twice',
-'noinline', 'noclone', 'no_icf', 'always_inline', 'flatten', 'pure',
-'const', 'nothrow', 'sentinel', 'format', 'format_arg',
-'no_instrument_function', 'no_split_stack', 'section', 'constructor',
-'destructor', 'used', 'unused', 'deprecated', 'weak', 'malloc', 'alias',
-'ifunc', 'warn_unused_result', 'nonnull', 'returns_nonnull',
-'gnu_inline', 'externally_visible', 'hot', 'cold', 'artificial',
-'no_sanitize_address', 'no_address_safety_analysis',
-'no_sanitize_thread', 'no_sanitize_undefined', 'no_reorder',
-'bnd_legacy', 'bnd_instrument', 'stack_protect', 'error' and 'warning'.
+currently defined for functions on all targets: `aligned',
+`alloc_size', `alloc_align', `assume_aligned', `noreturn',
+`returns_twice', `noinline', `noclone', `no_icf', `always_inline',
+`flatten', `pure', `const', `nothrow', `sentinel', `format',
+`format_arg', `no_instrument_function', `no_split_stack', `section',
+`constructor', `destructor', `used', `unused', `deprecated', `weak',
+`malloc', `alias', `ifunc', `warn_unused_result', `nonnull',
+`returns_nonnull', `gnu_inline', `externally_visible', `hot', `cold',
+`artificial', `no_sanitize_address', `no_address_safety_analysis',
+`no_sanitize_thread', `no_sanitize_undefined', `no_reorder',
+`bnd_legacy', `bnd_instrument', `stack_protect', `error' and `warning'.
Several other attributes are defined for functions on particular target
-systems. Other attributes, including 'section' are supported for
+systems. Other attributes, including `section' are supported for
variables declarations (*note Variable Attributes::), labels (*note
Label Attributes::) and for types (*note Type Attributes::).
GCC plugins may provide their own attributes.
- You may also specify attributes with '__' preceding and following each
+ You may also specify attributes with `__' preceding and following each
keyword. This allows you to use them in header files without being
-concerned about a possible macro of the same name. For example, you may
-use '__noreturn__' instead of 'noreturn'.
+concerned about a possible macro of the same name. For example, you
+may use `__noreturn__' instead of `noreturn'.
*Note Attribute Syntax::, for details of the exact syntax for using
attributes.
-'alias ("TARGET")'
- The 'alias' attribute causes the declaration to be emitted as an
+`alias ("TARGET")'
+ The `alias' attribute causes the declaration to be emitted as an
alias for another symbol, which must be specified. For instance,
void __f () { /* Do something. */; }
void f () __attribute__ ((weak, alias ("__f")));
- defines 'f' to be a weak alias for '__f'. In C++, the mangled name
- for the target must be used. It is an error if '__f' is not
+ defines `f' to be a weak alias for `__f'. In C++, the mangled
+ name for the target must be used. It is an error if `__f' is not
defined in the same translation unit.
Not all target machines support this attribute.
-'aligned (ALIGNMENT)'
+`aligned (ALIGNMENT)'
This attribute specifies a minimum alignment for the function,
measured in bytes.
You cannot use this attribute to decrease the alignment of a
function, only to increase it. However, when you explicitly
specify a function alignment this overrides the effect of the
- '-falign-functions' (*note Optimize Options::) option for this
+ `-falign-functions' (*note Optimize Options::) option for this
function.
- Note that the effectiveness of 'aligned' attributes may be limited
+ Note that the effectiveness of `aligned' attributes may be limited
by inherent limitations in your linker. On many systems, the
linker is only able to arrange for functions to be aligned up to a
certain maximum alignment. (For some linkers, the maximum
supported alignment may be very very small.) See your linker
documentation for further information.
- The 'aligned' attribute can also be used for variables and fields
+ The `aligned' attribute can also be used for variables and fields
(*note Variable Attributes::.)
-'alloc_size'
- The 'alloc_size' attribute is used to tell the compiler that the
+`alloc_size'
+ The `alloc_size' attribute is used to tell the compiler that the
function return value points to memory, where the size is given by
one or two of the functions parameters. GCC uses this information
- to improve the correctness of '__builtin_object_size'.
+ to improve the correctness of `__builtin_object_size'.
- The function parameter(s) denoting the allocated size are specified
- by one or two integer arguments supplied to the attribute. The
- allocated size is either the value of the single function argument
- specified or the product of the two function arguments specified.
- Argument numbering starts at one.
+ The function parameter(s) denoting the allocated size are
+ specified by one or two integer arguments supplied to the
+ attribute. The allocated size is either the value of the single
+ function argument specified or the product of the two function
+ arguments specified. Argument numbering starts at one.
For instance,
void* my_calloc(size_t, size_t) __attribute__((alloc_size(1,2)))
void* my_realloc(void*, size_t) __attribute__((alloc_size(2)))
- declares that 'my_calloc' returns memory of the size given by the
- product of parameter 1 and 2 and that 'my_realloc' returns memory
+ declares that `my_calloc' returns memory of the size given by the
+ product of parameter 1 and 2 and that `my_realloc' returns memory
of the size given by parameter 2.
-'alloc_align'
- The 'alloc_align' attribute is used to tell the compiler that the
+`alloc_align'
+ The `alloc_align' attribute is used to tell the compiler that the
function return value points to memory, where the returned pointer
- minimum alignment is given by one of the functions parameters. GCC
- uses this information to improve pointer alignment analysis.
+ minimum alignment is given by one of the functions parameters.
+ GCC uses this information to improve pointer alignment analysis.
The function parameter denoting the allocated alignment is
specified by one integer argument, whose number is the argument of
@@ -24789,11 +24988,11 @@ attributes.
void* my_memalign(size_t, size_t) __attribute__((alloc_align(1)))
- declares that 'my_memalign' returns memory with minimum alignment
+ declares that `my_memalign' returns memory with minimum alignment
given by parameter 1.
-'assume_aligned'
- The 'assume_aligned' attribute is used to tell the compiler that
+`assume_aligned'
+ The `assume_aligned' attribute is used to tell the compiler that
the function return value points to memory, where the returned
pointer minimum alignment is given by the first argument. If the
attribute has two arguments, the second argument is misalignment
@@ -24804,10 +25003,10 @@ attributes.
void* my_alloc1(size_t) __attribute__((assume_aligned(16)))
void* my_alloc2(size_t) __attribute__((assume_aligned(32, 8)))
- declares that 'my_alloc1' returns 16-byte aligned pointer and that
- 'my_alloc2' returns a pointer whose value modulo 32 is equal to 8.
+ declares that `my_alloc1' returns 16-byte aligned pointer and that
+ `my_alloc2' returns a pointer whose value modulo 32 is equal to 8.
-'always_inline'
+`always_inline'
Generally, functions are not inlined unless optimization is
specified. For functions declared inline, this attribute inlines
the function independent of any restrictions that otherwise apply
@@ -24817,111 +25016,113 @@ attributes.
and a failure to inline an indirect call may or may not be
diagnosed.
-'gnu_inline'
+`gnu_inline'
This attribute should be used with a function that is also declared
- with the 'inline' keyword. It directs GCC to treat the function as
- if it were defined in gnu90 mode even when compiling in C99 or
+ with the `inline' keyword. It directs GCC to treat the function
+ as if it were defined in gnu90 mode even when compiling in C99 or
gnu99 mode.
- If the function is declared 'extern', then this definition of the
+ If the function is declared `extern', then this definition of the
function is used only for inlining. In no case is the function
compiled as a standalone function, not even if you take its address
explicitly. Such an address becomes an external reference, as if
you had only declared the function, and had not defined it. This
has almost the effect of a macro. The way to use this is to put a
function definition in a header file with this attribute, and put
- another copy of the function, without 'extern', in a library file.
- The definition in the header file causes most calls to the function
- to be inlined. If any uses of the function remain, they refer to
- the single copy in the library. Note that the two definitions of
- the functions need not be precisely the same, although if they do
- not have the same effect your program may behave oddly.
-
- In C, if the function is neither 'extern' nor 'static', then the
+ another copy of the function, without `extern', in a library file.
+ The definition in the header file causes most calls to the
+ function to be inlined. If any uses of the function remain, they
+ refer to the single copy in the library. Note that the two
+ definitions of the functions need not be precisely the same,
+ although if they do not have the same effect your program may
+ behave oddly.
+
+ In C, if the function is neither `extern' nor `static', then the
function is compiled as a standalone function, as well as being
inlined where possible.
- This is how GCC traditionally handled functions declared 'inline'.
- Since ISO C99 specifies a different semantics for 'inline', this
+ This is how GCC traditionally handled functions declared `inline'.
+ Since ISO C99 specifies a different semantics for `inline', this
function attribute is provided as a transition measure and as a
useful feature in its own right. This attribute is available in
- GCC 4.1.3 and later. It is available if either of the preprocessor
- macros '__GNUC_GNU_INLINE__' or '__GNUC_STDC_INLINE__' are defined.
- *Note An Inline Function is As Fast As a Macro: Inline.
+ GCC 4.1.3 and later. It is available if either of the
+ preprocessor macros `__GNUC_GNU_INLINE__' or
+ `__GNUC_STDC_INLINE__' are defined. *Note An Inline Function is
+ As Fast As a Macro: Inline.
- In C++, this attribute does not depend on 'extern' in any way, but
- it still requires the 'inline' keyword to enable its special
+ In C++, this attribute does not depend on `extern' in any way, but
+ it still requires the `inline' keyword to enable its special
behavior.
-'artificial'
+`artificial'
This attribute is useful for small inline wrappers that if possible
should appear during debugging as a unit. Depending on the debug
info format it either means marking the function as artificial or
using the caller location for all instructions within the inlined
body.
-'bank_switch'
+`bank_switch'
When added to an interrupt handler with the M32C port, causes the
prologue and epilogue to use bank switching to preserve the
registers rather than saving them on the stack.
-'flatten'
+`flatten'
Generally, inlining into a function is limited. For a function
marked with this attribute, every call inside this function is
inlined, if possible. Whether the function itself is considered
for inlining depends on its size and the current inlining
parameters.
-'error ("MESSAGE")'
+`error ("MESSAGE")'
If this attribute is used on a function declaration and a call to
such a function is not eliminated through dead code elimination or
other optimizations, an error that includes MESSAGE is diagnosed.
This is useful for compile-time checking, especially together with
- '__builtin_constant_p' and inline functions where checking the
- inline function arguments is not possible through 'extern char
- [(condition) ? 1 : -1];' tricks. While it is possible to leave the
- function undefined and thus invoke a link failure, when using this
- attribute the problem is diagnosed earlier and with exact location
- of the call even in presence of inline functions or when not
- emitting debugging information.
-
-'warning ("MESSAGE")'
+ `__builtin_constant_p' and inline functions where checking the
+ inline function arguments is not possible through `extern char
+ [(condition) ? 1 : -1];' tricks. While it is possible to leave
+ the function undefined and thus invoke a link failure, when using
+ this attribute the problem is diagnosed earlier and with exact
+ location of the call even in presence of inline functions or when
+ not emitting debugging information.
+
+`warning ("MESSAGE")'
If this attribute is used on a function declaration and a call to
such a function is not eliminated through dead code elimination or
other optimizations, a warning that includes MESSAGE is diagnosed.
This is useful for compile-time checking, especially together with
- '__builtin_constant_p' and inline functions. While it is possible
- to define the function with a message in '.gnu.warning*' section,
- when using this attribute the problem is diagnosed earlier and with
- exact location of the call even in presence of inline functions or
- when not emitting debugging information.
-
-'cdecl'
- On the x86-32 targets, the 'cdecl' attribute causes the compiler to
+ `__builtin_constant_p' and inline functions. While it is possible
+ to define the function with a message in `.gnu.warning*' section,
+ when using this attribute the problem is diagnosed earlier and
+ with exact location of the call even in presence of inline
+ functions or when not emitting debugging information.
+
+`cdecl'
+ On the x86-32 targets, the `cdecl' attribute causes the compiler to
assume that the calling function pops off the stack space used to
pass arguments. This is useful to override the effects of the
- '-mrtd' switch.
+ `-mrtd' switch.
-'const'
+`const'
Many functions do not examine any values except their arguments,
and have no effects except the return value. Basically this is
- just slightly more strict class than the 'pure' attribute below,
+ just slightly more strict class than the `pure' attribute below,
since function is not allowed to read global memory.
Note that a function that has pointer arguments and examines the
- data pointed to must _not_ be declared 'const'. Likewise, a
- function that calls a non-'const' function usually must not be
- 'const'. It does not make sense for a 'const' function to return
- 'void'.
-
-'constructor'
-'destructor'
-'constructor (PRIORITY)'
-'destructor (PRIORITY)'
- The 'constructor' attribute causes the function to be called
- automatically before execution enters 'main ()'. Similarly, the
- 'destructor' attribute causes the function to be called
- automatically after 'main ()' completes or 'exit ()' is called.
+ data pointed to must _not_ be declared `const'. Likewise, a
+ function that calls a non-`const' function usually must not be
+ `const'. It does not make sense for a `const' function to return
+ `void'.
+
+`constructor'
+`destructor'
+`constructor (PRIORITY)'
+`destructor (PRIORITY)'
+ The `constructor' attribute causes the function to be called
+ automatically before execution enters `main ()'. Similarly, the
+ `destructor' attribute causes the function to be called
+ automatically after `main ()' completes or `exit ()' is called.
Functions with these attributes are useful for initializing data
that is used implicitly during the execution of the program.
@@ -24938,9 +25139,9 @@ attributes.
These attributes are not currently implemented for Objective-C.
-'deprecated'
-'deprecated (MSG)'
- The 'deprecated' attribute results in a warning if the function is
+`deprecated'
+`deprecated (MSG)'
+ The `deprecated' attribute results in a warning if the function is
used anywhere in the source file. This is useful when identifying
functions that are expected to be removed in a future version of a
program. The warning also includes the location of the declaration
@@ -24956,33 +25157,35 @@ attributes.
argument, which must be a string, is printed in the warning if
present.
- The 'deprecated' attribute can also be used for variables and types
- (*note Variable Attributes::, *note Type Attributes::.)
+ The `deprecated' attribute can also be used for variables and
+ types (*note Variable Attributes::, *note Type Attributes::.)
-'disinterrupt'
+`disinterrupt'
On Epiphany and MeP targets, this attribute causes the compiler to
emit instructions to disable interrupts for the duration of the
given function.
-'dllexport'
- On Microsoft Windows targets and Symbian OS targets the 'dllexport'
- attribute causes the compiler to provide a global pointer to a
- pointer in a DLL, so that it can be referenced with the 'dllimport'
- attribute. On Microsoft Windows targets, the pointer name is
- formed by combining '_imp__' and the function or variable name.
+`dllexport'
+ On Microsoft Windows targets and Symbian OS targets the
+ `dllexport' attribute causes the compiler to provide a global
+ pointer to a pointer in a DLL, so that it can be referenced with
+ the `dllimport' attribute. On Microsoft Windows targets, the
+ pointer name is formed by combining `_imp__' and the function or
+ variable name.
- You can use '__declspec(dllexport)' as a synonym for '__attribute__
- ((dllexport))' for compatibility with other compilers.
+ You can use `__declspec(dllexport)' as a synonym for
+ `__attribute__ ((dllexport))' for compatibility with other
+ compilers.
- On systems that support the 'visibility' attribute, this attribute
+ On systems that support the `visibility' attribute, this attribute
also implies "default" visibility. It is an error to explicitly
specify any other visibility.
GCC's default behavior is to emit all inline functions with the
- 'dllexport' attribute. Since this can cause object file-size
- bloat, you can use '-fno-keep-inline-dllexport', which tells GCC to
+ `dllexport' attribute. Since this can cause object file-size
+ bloat, you can use `-fno-keep-inline-dllexport', which tells GCC to
ignore the attribute for inlined functions unless the
- '-fkeep-inline-functions' flag is used instead.
+ `-fkeep-inline-functions' flag is used instead.
The attribute is ignored for undefined symbols.
@@ -24993,117 +25196,117 @@ attributes.
For Microsoft Windows targets there are alternative methods for
including the symbol in the DLL's export table such as using a
- '.def' file with an 'EXPORTS' section or, with GNU ld, using the
- '--export-all' linker flag.
+ `.def' file with an `EXPORTS' section or, with GNU ld, using the
+ `--export-all' linker flag.
-'dllimport'
- On Microsoft Windows and Symbian OS targets, the 'dllimport'
+`dllimport'
+ On Microsoft Windows and Symbian OS targets, the `dllimport'
attribute causes the compiler to reference a function or variable
via a global pointer to a pointer that is set up by the DLL
- exporting the symbol. The attribute implies 'extern'. On
+ exporting the symbol. The attribute implies `extern'. On
Microsoft Windows targets, the pointer name is formed by combining
- '_imp__' and the function or variable name.
+ `_imp__' and the function or variable name.
- You can use '__declspec(dllimport)' as a synonym for '__attribute__
- ((dllimport))' for compatibility with other compilers.
+ You can use `__declspec(dllimport)' as a synonym for
+ `__attribute__ ((dllimport))' for compatibility with other
+ compilers.
- On systems that support the 'visibility' attribute, this attribute
+ On systems that support the `visibility' attribute, this attribute
also implies "default" visibility. It is an error to explicitly
specify any other visibility.
Currently, the attribute is ignored for inlined functions. If the
attribute is applied to a symbol _definition_, an error is
- reported. If a symbol previously declared 'dllimport' is later
+ reported. If a symbol previously declared `dllimport' is later
defined, the attribute is ignored in subsequent references, and a
warning is emitted. The attribute is also overridden by a
- subsequent declaration as 'dllexport'.
+ subsequent declaration as `dllexport'.
- When applied to C++ classes, the attribute marks non-inlined member
- functions and static data members as imports. However, the
+ When applied to C++ classes, the attribute marks non-inlined
+ member functions and static data members as imports. However, the
attribute is ignored for virtual methods to allow creation of
vtables using thunks.
- On the SH Symbian OS target the 'dllimport' attribute also has
+ On the SH Symbian OS target the `dllimport' attribute also has
another affect--it can cause the vtable and run-time type
information for a class to be exported. This happens when the
class has a dllimported constructor or a non-inline, non-pure
- virtual function and, for either of those two conditions, the class
- also has an inline constructor or destructor and has a key function
- that is defined in the current translation unit.
+ virtual function and, for either of those two conditions, the
+ class also has an inline constructor or destructor and has a key
+ function that is defined in the current translation unit.
- For Microsoft Windows targets the use of the 'dllimport' attribute
+ For Microsoft Windows targets the use of the `dllimport' attribute
on functions is not necessary, but provides a small performance
benefit by eliminating a thunk in the DLL. The use of the
- 'dllimport' attribute on imported variables can be avoided by
- passing the '--enable-auto-import' switch to the GNU linker. As
+ `dllimport' attribute on imported variables can be avoided by
+ passing the `--enable-auto-import' switch to the GNU linker. As
with functions, using the attribute for a variable eliminates a
thunk in the DLL.
One drawback to using this attribute is that a pointer to a
- _variable_ marked as 'dllimport' cannot be used as a constant
- address. However, a pointer to a _function_ with the 'dllimport'
+ _variable_ marked as `dllimport' cannot be used as a constant
+ address. However, a pointer to a _function_ with the `dllimport'
attribute can be used as a constant initializer; in this case, the
address of a stub function in the import lib is referenced. On
Microsoft Windows targets, the attribute can be disabled for
- functions by setting the '-mnop-fun-dllimport' flag.
+ functions by setting the `-mnop-fun-dllimport' flag.
-'exception'
+`exception'
Use this attribute on the NDS32 target to indicate that the
specified function is an exception handler. The compiler will
generate corresponding sections for use in an exception handler.
-'exception_handler'
+`exception_handler'
Use this attribute on the Blackfin to indicate that the specified
function is an exception handler. The compiler generates function
entry and exit sequences suitable for use in an exception handler
when this attribute is present.
-'externally_visible'
+`externally_visible'
This attribute, attached to a global variable or function,
- nullifies the effect of the '-fwhole-program' command-line option,
+ nullifies the effect of the `-fwhole-program' command-line option,
so the object remains visible outside the current compilation unit.
- If '-fwhole-program' is used together with '-flto' and 'gold' is
- used as the linker plugin, 'externally_visible' attributes are
- automatically added to functions (not variable yet due to a current
- 'gold' issue) that are accessed outside of LTO objects according to
- resolution file produced by 'gold'. For other linkers that cannot
- generate resolution file, explicit 'externally_visible' attributes
- are still necessary.
-
-'far'
+ If `-fwhole-program' is used together with `-flto' and `gold' is
+ used as the linker plugin, `externally_visible' attributes are
+ automatically added to functions (not variable yet due to a
+ current `gold' issue) that are accessed outside of LTO objects
+ according to resolution file produced by `gold'. For other
+ linkers that cannot generate resolution file, explicit
+ `externally_visible' attributes are still necessary.
+`far'
On MeP targets this causes the compiler to use a calling convention
that assumes the called function is too far away for the built-in
addressing modes.
-'fast_interrupt'
+`fast_interrupt'
Use this attribute on the M32C and RX ports to indicate that the
specified function is a fast interrupt handler. This is just like
- the 'interrupt' attribute, except that 'freit' is used to return
- instead of 'reit'.
+ the `interrupt' attribute, except that `freit' is used to return
+ instead of `reit'.
-'fastcall'
- On x86-32 targets, the 'fastcall' attribute causes the compiler to
+`fastcall'
+ On x86-32 targets, the `fastcall' attribute causes the compiler to
pass the first argument (if of integral type) in the register ECX
and the second argument (if of integral type) in the register EDX.
Subsequent and other typed arguments are passed on the stack. The
- called function pops the arguments off the stack. If the number of
- arguments is variable all arguments are pushed on the stack.
+ called function pops the arguments off the stack. If the number
+ of arguments is variable all arguments are pushed on the stack.
-'thiscall'
- On x86-32 targets, the 'thiscall' attribute causes the compiler to
+`thiscall'
+ On x86-32 targets, the `thiscall' attribute causes the compiler to
pass the first argument (if of integral type) in the register ECX.
- Subsequent and other typed arguments are passed on the stack. The
- called function pops the arguments off the stack. If the number of
- arguments is variable all arguments are pushed on the stack. The
- 'thiscall' attribute is intended for C++ non-static member
- functions. As a GCC extension, this calling convention can be used
- for C functions and for static member methods.
-
-'format (ARCHETYPE, STRING-INDEX, FIRST-TO-CHECK)'
- The 'format' attribute specifies that a function takes 'printf',
- 'scanf', 'strftime' or 'strfmon' style arguments that should be
+ Subsequent and other typed arguments are passed on the stack. The
+ called function pops the arguments off the stack. If the number
+ of arguments is variable all arguments are pushed on the stack.
+ The `thiscall' attribute is intended for C++ non-static member
+ functions. As a GCC extension, this calling convention can be
+ used for C functions and for static member methods.
+
+`format (ARCHETYPE, STRING-INDEX, FIRST-TO-CHECK)'
+ The `format' attribute specifies that a function takes `printf',
+ `scanf', `strftime' or `strfmon' style arguments that should be
type-checked against a format string. For example, the
declaration:
@@ -25111,127 +25314,129 @@ attributes.
my_printf (void *my_object, const char *my_format, ...)
__attribute__ ((format (printf, 2, 3)));
- causes the compiler to check the arguments in calls to 'my_printf'
- for consistency with the 'printf' style format string argument
- 'my_format'.
+ causes the compiler to check the arguments in calls to `my_printf'
+ for consistency with the `printf' style format string argument
+ `my_format'.
The parameter ARCHETYPE determines how the format string is
- interpreted, and should be 'printf', 'scanf', 'strftime',
- 'gnu_printf', 'gnu_scanf', 'gnu_strftime' or 'strfmon'. (You can
- also use '__printf__', '__scanf__', '__strftime__' or
- '__strfmon__'.) On MinGW targets, 'ms_printf', 'ms_scanf', and
- 'ms_strftime' are also present. ARCHETYPE values such as 'printf'
+ interpreted, and should be `printf', `scanf', `strftime',
+ `gnu_printf', `gnu_scanf', `gnu_strftime' or `strfmon'. (You can
+ also use `__printf__', `__scanf__', `__strftime__' or
+ `__strfmon__'.) On MinGW targets, `ms_printf', `ms_scanf', and
+ `ms_strftime' are also present. ARCHETYPE values such as `printf'
refer to the formats accepted by the system's C runtime library,
- while values prefixed with 'gnu_' always refer to the formats
+ while values prefixed with `gnu_' always refer to the formats
accepted by the GNU C Library. On Microsoft Windows targets,
- values prefixed with 'ms_' refer to the formats accepted by the
- 'msvcrt.dll' library. The parameter STRING-INDEX specifies which
+ values prefixed with `ms_' refer to the formats accepted by the
+ `msvcrt.dll' library. The parameter STRING-INDEX specifies which
argument is the format string argument (starting from 1), while
- FIRST-TO-CHECK is the number of the first argument to check against
- the format string. For functions where the arguments are not
- available to be checked (such as 'vprintf'), specify the third
+ FIRST-TO-CHECK is the number of the first argument to check
+ against the format string. For functions where the arguments are
+ not available to be checked (such as `vprintf'), specify the third
parameter as zero. In this case the compiler only checks the
- format string for consistency. For 'strftime' formats, the third
+ format string for consistency. For `strftime' formats, the third
parameter is required to be zero. Since non-static C++ methods
- have an implicit 'this' argument, the arguments of such methods
+ have an implicit `this' argument, the arguments of such methods
should be counted from two, not one, when giving values for
STRING-INDEX and FIRST-TO-CHECK.
- In the example above, the format string ('my_format') is the second
- argument of the function 'my_print', and the arguments to check
+ In the example above, the format string (`my_format') is the second
+ argument of the function `my_print', and the arguments to check
start with the third argument, so the correct parameters for the
format attribute are 2 and 3.
- The 'format' attribute allows you to identify your own functions
+ The `format' attribute allows you to identify your own functions
that take format strings as arguments, so that GCC can check the
calls to these functions for errors. The compiler always (unless
- '-ffreestanding' or '-fno-builtin' is used) checks formats for the
- standard library functions 'printf', 'fprintf', 'sprintf', 'scanf',
- 'fscanf', 'sscanf', 'strftime', 'vprintf', 'vfprintf' and
- 'vsprintf' whenever such warnings are requested (using '-Wformat'),
- so there is no need to modify the header file 'stdio.h'. In C99
- mode, the functions 'snprintf', 'vsnprintf', 'vscanf', 'vfscanf'
- and 'vsscanf' are also checked. Except in strictly conforming C
- standard modes, the X/Open function 'strfmon' is also checked as
- are 'printf_unlocked' and 'fprintf_unlocked'. *Note Options
- Controlling C Dialect: C Dialect Options.
-
- For Objective-C dialects, 'NSString' (or '__NSString__') is
+ `-ffreestanding' or `-fno-builtin' is used) checks formats for the
+ standard library functions `printf', `fprintf', `sprintf',
+ `scanf', `fscanf', `sscanf', `strftime', `vprintf', `vfprintf' and
+ `vsprintf' whenever such warnings are requested (using
+ `-Wformat'), so there is no need to modify the header file
+ `stdio.h'. In C99 mode, the functions `snprintf', `vsnprintf',
+ `vscanf', `vfscanf' and `vsscanf' are also checked. Except in
+ strictly conforming C standard modes, the X/Open function
+ `strfmon' is also checked as are `printf_unlocked' and
+ `fprintf_unlocked'. *Note Options Controlling C Dialect: C
+ Dialect Options.
+
+ For Objective-C dialects, `NSString' (or `__NSString__') is
recognized in the same context. Declarations including these
- format attributes are parsed for correct syntax, however the result
- of checking of such format strings is not yet defined, and is not
- carried out by this version of the compiler.
+ format attributes are parsed for correct syntax, however the
+ result of checking of such format strings is not yet defined, and
+ is not carried out by this version of the compiler.
The target may also provide additional types of format checks.
*Note Format Checks Specific to Particular Target Machines: Target
Format Checks.
-'format_arg (STRING-INDEX)'
- The 'format_arg' attribute specifies that a function takes a format
- string for a 'printf', 'scanf', 'strftime' or 'strfmon' style
- function and modifies it (for example, to translate it into another
- language), so the result can be passed to a 'printf', 'scanf',
- 'strftime' or 'strfmon' style function (with the remaining
- arguments to the format function the same as they would have been
- for the unmodified string). For example, the declaration:
+`format_arg (STRING-INDEX)'
+ The `format_arg' attribute specifies that a function takes a format
+ string for a `printf', `scanf', `strftime' or `strfmon' style
+ function and modifies it (for example, to translate it into
+ another language), so the result can be passed to a `printf',
+ `scanf', `strftime' or `strfmon' style function (with the
+ remaining arguments to the format function the same as they would
+ have been for the unmodified string). For example, the
+ declaration:
extern char *
my_dgettext (char *my_domain, const char *my_format)
__attribute__ ((format_arg (2)));
- causes the compiler to check the arguments in calls to a 'printf',
- 'scanf', 'strftime' or 'strfmon' type function, whose format string
- argument is a call to the 'my_dgettext' function, for consistency
- with the format string argument 'my_format'. If the 'format_arg'
- attribute had not been specified, all the compiler could tell in
- such calls to format functions would be that the format string
- argument is not constant; this would generate a warning when
- '-Wformat-nonliteral' is used, but the calls could not be checked
- without the attribute.
+ causes the compiler to check the arguments in calls to a `printf',
+ `scanf', `strftime' or `strfmon' type function, whose format
+ string argument is a call to the `my_dgettext' function, for
+ consistency with the format string argument `my_format'. If the
+ `format_arg' attribute had not been specified, all the compiler
+ could tell in such calls to format functions would be that the
+ format string argument is not constant; this would generate a
+ warning when `-Wformat-nonliteral' is used, but the calls could
+ not be checked without the attribute.
The parameter STRING-INDEX specifies which argument is the format
string argument (starting from one). Since non-static C++ methods
- have an implicit 'this' argument, the arguments of such methods
+ have an implicit `this' argument, the arguments of such methods
should be counted from two.
- The 'format_arg' attribute allows you to identify your own
+ The `format_arg' attribute allows you to identify your own
functions that modify format strings, so that GCC can check the
- calls to 'printf', 'scanf', 'strftime' or 'strfmon' type function
+ calls to `printf', `scanf', `strftime' or `strfmon' type function
whose operands are a call to one of your own function. The
- compiler always treats 'gettext', 'dgettext', and 'dcgettext' in
+ compiler always treats `gettext', `dgettext', and `dcgettext' in
this manner except when strict ISO C support is requested by
- '-ansi' or an appropriate '-std' option, or '-ffreestanding' or
- '-fno-builtin' is used. *Note Options Controlling C Dialect: C
+ `-ansi' or an appropriate `-std' option, or `-ffreestanding' or
+ `-fno-builtin' is used. *Note Options Controlling C Dialect: C
Dialect Options.
- For Objective-C dialects, the 'format-arg' attribute may refer to
- an 'NSString' reference for compatibility with the 'format'
+ For Objective-C dialects, the `format-arg' attribute may refer to
+ an `NSString' reference for compatibility with the `format'
attribute above.
- The target may also allow additional types in 'format-arg'
+ The target may also allow additional types in `format-arg'
attributes. *Note Format Checks Specific to Particular Target
Machines: Target Format Checks.
-'function_vector'
- Use this attribute on the H8/300, H8/300H, and H8S to indicate that
- the specified function should be called through the function
+`function_vector'
+ Use this attribute on the H8/300, H8/300H, and H8S to indicate
+ that the specified function should be called through the function
vector. Calling a function through the function vector reduces
- code size, however; the function vector has a limited size (maximum
- 128 entries on the H8/300 and 64 entries on the H8/300H and H8S)
- and shares space with the interrupt vector.
+ code size, however; the function vector has a limited size
+ (maximum 128 entries on the H8/300 and 64 entries on the H8/300H
+ and H8S) and shares space with the interrupt vector.
On SH2A targets, this attribute declares a function to be called
using the TBR relative addressing mode. The argument to this
attribute is the entry number of the same function in a vector
table containing all the TBR relative addressable functions. For
- correct operation the TBR must be setup accordingly to point to the
- start of the vector table before any functions with this attribute
- are invoked. Usually a good place to do the initialization is the
- startup routine. The TBR relative vector table can have at max 256
- function entries. The jumps to these functions are generated using
- a SH2A specific, non delayed branch instruction JSR/N @(disp8,TBR).
- You must use GAS and GLD from GNU binutils version 2.7 or later for
- this attribute to work correctly.
+ correct operation the TBR must be setup accordingly to point to
+ the start of the vector table before any functions with this
+ attribute are invoked. Usually a good place to do the
+ initialization is the startup routine. The TBR relative vector
+ table can have at max 256 function entries. The jumps to these
+ functions are generated using a SH2A specific, non delayed branch
+ instruction JSR/N @(disp8,TBR). You must use GAS and GLD from GNU
+ binutils version 2.7 or later for this attribute to work correctly.
Please refer the example of M16C target, to see the use of this
attribute while declaring a function,
@@ -25241,13 +25446,13 @@ attributes.
being made to the same function, it saves 2 bytes of code per each
of these calls.
- On M16C/M32C targets, the 'function_vector' attribute declares a
- special page subroutine call function. Use of this attribute
+ On M16C/M32C targets, the `function_vector' attribute declares a
+ special page subroutine call function. Use of this attribute
reduces the code size by 2 bytes for each call generated to the
- subroutine. The argument to the attribute is the vector number
+ subroutine. The argument to the attribute is the vector number
entry from the special page vector table which contains the 16
- low-order bits of the subroutine's entry address. Each vector
- table has special page number (18 to 255) that is used in 'jsrs'
+ low-order bits of the subroutine's entry address. Each vector
+ table has special page number (18 to 255) that is used in `jsrs'
instructions. Jump addresses of the routines are generated by
adding 0x0F0000 (in case of M16C targets) or 0xFF0000 (in case of
M32C targets), to the 2-byte addresses set in the vector table.
@@ -25256,7 +25461,7 @@ attributes.
0x0FFFFF (for M16C) and 0xFF0000 to 0xFFFFFF (for M32C).
In the following example 2 bytes are saved for each call to
- function 'foo'.
+ function `foo'.
void foo (void) __attribute__((function_vector(0x18)));
void foo (void)
@@ -25273,19 +25478,19 @@ attributes.
This attribute is ignored for R8C target.
-'ifunc ("RESOLVER")'
- The 'ifunc' attribute is used to mark a function as an indirect
+`ifunc ("RESOLVER")'
+ The `ifunc' attribute is used to mark a function as an indirect
function using the STT_GNU_IFUNC symbol type extension to the ELF
standard. This allows the resolution of the symbol value to be
determined dynamically at load time, and an optimized version of
the routine can be selected for the particular processor or other
system characteristics determined then. To use this attribute,
- first define the implementation functions available, and a resolver
- function that returns a pointer to the selected implementation
- function. The implementation functions' declarations must match
- the API of the function being implemented, the resolver's
- declaration is be a function returning pointer to void function
- returning void:
+ first define the implementation functions available, and a
+ resolver function that returns a pointer to the selected
+ implementation function. The implementation functions'
+ declarations must match the API of the function being implemented,
+ the resolver's declaration is be a function returning pointer to
+ void function returning void:
void *my_memcpy (void *dst, const void *src, size_t len)
{
@@ -25313,32 +25518,33 @@ attributes.
higher and GNU C Library version 2.11.1 are required to use this
feature.
-'interrupt'
+`interrupt'
Use this attribute on the ARC, ARM, AVR, CR16, Epiphany, M32C,
M32R/D, m68k, MeP, MIPS, MSP430, NDS32, RL78, RX, Visium and
Xstormy16 ports to indicate that the specified function is an
interrupt handler. The compiler generates function entry and exit
sequences suitable for use in an interrupt handler when this
- attribute is present. With Epiphany targets it may also generate a
- special section with code to initialize the interrupt vector table.
+ attribute is present. With Epiphany targets it may also generate
+ a special section with code to initialize the interrupt vector
+ table.
Note, interrupt handlers for the Blackfin, H8/300, H8/300H, H8S,
MicroBlaze, and SH processors can be specified via the
- 'interrupt_handler' attribute.
+ `interrupt_handler' attribute.
Note, on the ARC, you must specify the kind of interrupt to be
handled in a parameter to the interrupt attribute like this:
void f () __attribute__ ((interrupt ("ilink1")));
- Permissible values for this parameter are: 'ilink1' and 'ilink2'.
+ Permissible values for this parameter are: `ilink1' and `ilink2'.
Note, on the AVR, the hardware globally disables interrupts when an
interrupt is executed. The first instruction of an interrupt
- handler declared with this attribute is a 'SEI' instruction to
- re-enable interrupts. See also the 'signal' function attribute
- that does not insert a 'SEI' instruction. If both 'signal' and
- 'interrupt' are specified for the same function, 'signal' is
+ handler declared with this attribute is a `SEI' instruction to
+ re-enable interrupts. See also the `signal' function attribute
+ that does not insert a `SEI' instruction. If both `signal' and
+ `interrupt' are specified for the same function, `signal' is
silently ignored.
Note, for the ARM, you can specify the kind of interrupt to be
@@ -25347,65 +25553,66 @@ attributes.
void f () __attribute__ ((interrupt ("IRQ")));
- Permissible values for this parameter are: 'IRQ', 'FIQ', 'SWI',
- 'ABORT' and 'UNDEF'.
+ Permissible values for this parameter are: `IRQ', `FIQ', `SWI',
+ `ABORT' and `UNDEF'.
On ARMv7-M the interrupt type is ignored, and the attribute means
the function may be called with a word-aligned stack pointer.
Note, for the MSP430 you can provide an argument to the interrupt
attribute which specifies a name or number. If the argument is a
- number it indicates the slot in the interrupt vector table (0 - 31)
- to which this handler should be assigned. If the argument is a
- name it is treated as a symbolic name for the vector slot. These
- names should match up with appropriate entries in the linker
- script. By default the names 'watchdog' for vector 26, 'nmi' for
- vector 30 and 'reset' for vector 31 are recognized.
+ number it indicates the slot in the interrupt vector table (0 -
+ 31) to which this handler should be assigned. If the argument is
+ a name it is treated as a symbolic name for the vector slot.
+ These names should match up with appropriate entries in the linker
+ script. By default the names `watchdog' for vector 26, `nmi' for
+ vector 30 and `reset' for vector 31 are recognized.
You can also use the following function attributes to modify how
normal functions interact with interrupt functions:
- 'critical'
+ `critical'
Critical functions disable interrupts upon entry and restore
the previous interrupt state upon exit. Critical functions
- cannot also have the 'naked' or 'reentrant' attributes. They
- can have the 'interrupt' attribute.
+ cannot also have the `naked' or `reentrant' attributes. They
+ can have the `interrupt' attribute.
- 'reentrant'
+ `reentrant'
Reentrant functions disable interrupts upon entry and enable
them upon exit. Reentrant functions cannot also have the
- 'naked' or 'critical' attributes. They can have the
- 'interrupt' attribute.
+ `naked' or `critical' attributes. They can have the
+ `interrupt' attribute.
- 'wakeup'
+ `wakeup'
This attribute only applies to interrupt functions. It is
silently ignored if applied to a non-interrupt function. A
wakeup interrupt function will rouse the processor from any
low-power state that it might be in when the function exits.
+
On Epiphany targets one or more optional parameters can be added
like this:
void __attribute__ ((interrupt ("dma0, dma1"))) universal_dma_handler ();
- Permissible values for these parameters are: 'reset',
- 'software_exception', 'page_miss', 'timer0', 'timer1', 'message',
- 'dma0', 'dma1', 'wand' and 'swi'. Multiple parameters indicate
+ Permissible values for these parameters are: `reset',
+ `software_exception', `page_miss', `timer0', `timer1', `message',
+ `dma0', `dma1', `wand' and `swi'. Multiple parameters indicate
that multiple entries in the interrupt vector table should be
- initialized for this function, i.e. for each parameter NAME, a jump
- to the function is emitted in the section ivt_entry_NAME. The
- parameter(s) may be omitted entirely, in which case no interrupt
- vector table entry is provided.
+ initialized for this function, i.e. for each parameter NAME, a
+ jump to the function is emitted in the section ivt_entry_NAME.
+ The parameter(s) may be omitted entirely, in which case no
+ interrupt vector table entry is provided.
Note, on Epiphany targets, interrupts are enabled inside the
- function unless the 'disinterrupt' attribute is also specified.
+ function unless the `disinterrupt' attribute is also specified.
On Epiphany targets, you can also use the following attribute to
modify the behavior of an interrupt handler:
- 'forwarder_section'
+ `forwarder_section'
The interrupt handler may be in external memory which cannot
- be reached by a branch instruction, so generate a local memory
- trampoline to transfer control. The single parameter
+ be reached by a branch instruction, so generate a local
+ memory trampoline to transfer control. The single parameter
identifies the section where the trampoline is placed.
The following examples are all valid uses of these attributes on
@@ -25418,20 +25625,20 @@ attributes.
void __attribute__ ((interrupt ("dma0, dma1"), forwarder_section ("tramp")))
external_dma_handler ();
- On MIPS targets, you can use the following attributes to modify the
- behavior of an interrupt handler:
- 'use_shadow_register_set'
+ On MIPS targets, you can use the following attributes to modify
+ the behavior of an interrupt handler:
+ `use_shadow_register_set'
Assume that the handler uses a shadow register set, instead of
the main general-purpose registers.
- 'keep_interrupts_masked'
+ `keep_interrupts_masked'
Keep interrupts masked for the whole function. Without this
- attribute, GCC tries to reenable interrupts for as much of the
- function as it can.
+ attribute, GCC tries to reenable interrupts for as much of
+ the function as it can.
- 'use_debug_exception_return'
- Return using the 'deret' instruction. Interrupt handlers that
- don't have this attribute return using 'eret' instead.
+ `use_debug_exception_return'
+ Return using the `deret' instruction. Interrupt handlers
+ that don't have this attribute return using `eret' instead.
You can use any combination of these attributes, as shown below:
void __attribute__ ((interrupt)) v0 ();
@@ -25452,32 +25659,36 @@ attributes.
function is an interrupt handler. The compiler generates
corresponding sections for use in an interrupt handler. You can
use the following attributes to modify the behavior:
- 'nested'
+ `nested'
This interrupt service routine is interruptible.
- 'not_nested'
+
+ `not_nested'
This interrupt service routine is not interruptible.
- 'nested_ready'
+
+ `nested_ready'
This interrupt service routine is interruptible after
- 'PSW.GIE' (global interrupt enable) is set. This allows
+ `PSW.GIE' (global interrupt enable) is set. This allows
interrupt service routine to finish some short critical code
before enabling interrupts.
- 'save_all'
+
+ `save_all'
The system will help save all registers into stack before
entering interrupt handler.
- 'partial_save'
+
+ `partial_save'
The system will help save caller registers into stack before
entering interrupt handler.
- On RL78, use 'brk_interrupt' instead of 'interrupt' for handlers
- intended to be used with the 'BRK' opcode (i.e. those that must end
- with 'RETB' instead of 'RETI').
+ On RL78, use `brk_interrupt' instead of `interrupt' for handlers
+ intended to be used with the `BRK' opcode (i.e. those that must
+ end with `RETB' instead of `RETI').
On RX targets, you may specify one or more vector numbers as
arguments to the attribute, as well as naming an alternate table
name. Parameters are handled sequentially, so one handler can be
- assigned to multiple entries in multiple tables. One may also pass
- the magic string '"$default"' which causes the function to be used
- for any unfilled slots in the current table.
+ assigned to multiple entries in multiple tables. One may also
+ pass the magic string `"$default"' which causes the function to be
+ used for any unfilled slots in the current table.
This example shows a simple assignment of a function to one vector
in the default table (note that preprocessor macros may be used for
@@ -25486,205 +25697,201 @@ attributes.
This example assigns a function to two slots in the default table
(using preprocessor macros defined elsewhere) and makes it the
- default for the 'dct' table:
+ default for the `dct' table:
void __attribute__ ((interrupt (RXD1_VECT,RXD2_VECT,"dct","$default")))
txd1_handler ();
-'interrupt_handler'
- Use this attribute on the Blackfin, m68k, H8/300, H8/300H, H8S, and
- SH to indicate that the specified function is an interrupt handler.
- The compiler generates function entry and exit sequences suitable
- for use in an interrupt handler when this attribute is present.
+`interrupt_handler'
+ Use this attribute on the Blackfin, m68k, H8/300, H8/300H, H8S,
+ and SH to indicate that the specified function is an interrupt
+ handler. The compiler generates function entry and exit sequences
+ suitable for use in an interrupt handler when this attribute is
+ present.
-'interrupt_thread'
+`interrupt_thread'
Use this attribute on fido, a subarchitecture of the m68k, to
indicate that the specified function is an interrupt handler that
is designed to run as a thread. The compiler omits generate
prologue/epilogue sequences and replaces the return instruction
- with a 'sleep' instruction. This attribute is available only on
+ with a `sleep' instruction. This attribute is available only on
fido.
-'isr'
+`isr'
Use this attribute on ARM to write Interrupt Service Routines.
- This is an alias to the 'interrupt' attribute above.
+ This is an alias to the `interrupt' attribute above.
-'kspisusp'
- When used together with 'interrupt_handler', 'exception_handler' or
- 'nmi_handler', code is generated to load the stack pointer from the
- USP register in the function prologue.
+`kspisusp'
+ When used together with `interrupt_handler', `exception_handler'
+ or `nmi_handler', code is generated to load the stack pointer from
+ the USP register in the function prologue.
-'l1_text'
+`l1_text'
This attribute specifies a function to be placed into L1
- Instruction SRAM. The function is put into a specific section
- named '.l1.text'. With '-mfdpic', function calls with a such
+ Instruction SRAM. The function is put into a specific section
+ named `.l1.text'. With `-mfdpic', function calls with a such
function as the callee or caller uses inlined PLT.
-'l2'
+`l2'
On the Blackfin, this attribute specifies a function to be placed
into L2 SRAM. The function is put into a specific section named
- '.l1.text'. With '-mfdpic', callers of such functions use an
+ `.l1.text'. With `-mfdpic', callers of such functions use an
inlined PLT.
-'leaf'
+`leaf'
Calls to external functions with this attribute must return to the
current compilation unit only by return or by exception handling.
In particular, leaf functions are not allowed to call callback
- function passed to it from the current compilation unit or directly
- call functions exported by the unit or longjmp into the unit. Leaf
- function might still call functions from other compilation units
- and thus they are not necessarily leaf in the sense that they
- contain no function calls at all.
-
- The attribute is intended for library functions to improve dataflow
- analysis. The compiler takes the hint that any data not escaping
- the current compilation unit can not be used or modified by the
- leaf function. For example, the 'sin' function is a leaf function,
- but 'qsort' is not.
+ function passed to it from the current compilation unit or
+ directly call functions exported by the unit or longjmp into the
+ unit. Leaf function might still call functions from other
+ compilation units and thus they are not necessarily leaf in the
+ sense that they contain no function calls at all.
+
+ The attribute is intended for library functions to improve
+ dataflow analysis. The compiler takes the hint that any data not
+ escaping the current compilation unit can not be used or modified
+ by the leaf function. For example, the `sin' function is a leaf
+ function, but `qsort' is not.
Note that leaf functions might invoke signals and signal handlers
might be defined in the current compilation unit and use static
variables. The only compliant way to write such a signal handler
- is to declare such variables 'volatile'.
+ is to declare such variables `volatile'.
- The attribute has no effect on functions defined within the current
- compilation unit. This is to allow easy merging of multiple
- compilation units into one, for example, by using the link-time
- optimization. For this reason the attribute is not allowed on
- types to annotate indirect calls.
+ The attribute has no effect on functions defined within the
+ current compilation unit. This is to allow easy merging of
+ multiple compilation units into one, for example, by using the
+ link-time optimization. For this reason the attribute is not
+ allowed on types to annotate indirect calls.
-'long_call'
-'medium_call'
-'short_call'
+`long_call'
+`medium_call'
+`short_call'
These attributes specify how a particular function is called on
- ARC, ARM and Epiphany - with 'medium_call' being specific to ARC.
- These attributes override the '-mlong-calls' (*note ARM Options::
- and *note ARC Options::) and '-mmedium-calls' (*note ARC Options::)
- command-line switches and '#pragma long_calls' settings. For ARM,
- the 'long_call' attribute indicates that the function might be far
+ ARC, ARM and Epiphany - with `medium_call' being specific to ARC.
+ These attributes override the `-mlong-calls' (*note ARM Options::
+ and *note ARC Options::) and `-mmedium-calls' (*note ARC Options::)
+ command-line switches and `#pragma long_calls' settings. For ARM,
+ the `long_call' attribute indicates that the function might be far
away from the call site and require a different (more expensive)
- calling sequence. The 'short_call' attribute always places the
- offset to the function from the call site into the 'BL' instruction
- directly.
-
- For ARC, a function marked with the 'long_call' attribute is always
- called using register-indirect jump-and-link instructions, thereby
- enabling the called function to be placed anywhere within the
- 32-bit address space. A function marked with the 'medium_call'
+ calling sequence. The `short_call' attribute always places the
+ offset to the function from the call site into the `BL'
+ instruction directly.
+
+ For ARC, a function marked with the `long_call' attribute is
+ always called using register-indirect jump-and-link instructions,
+ thereby enabling the called function to be placed anywhere within
+ the 32-bit address space. A function marked with the `medium_call'
attribute will always be close enough to be called with an
unconditional branch-and-link instruction, which has a 25-bit
- offset from the call site. A function marked with the 'short_call'
+ offset from the call site. A function marked with the `short_call'
attribute will always be close enough to be called with a
conditional branch-and-link instruction, which has a 21-bit offset
from the call site.
-'longcall'
-'shortcall'
- On Blackfin and PowerPC, the 'longcall' attribute indicates that
+`longcall'
+`shortcall'
+ On Blackfin and PowerPC, the `longcall' attribute indicates that
the function might be far away from the call site and require a
- different (more expensive) calling sequence. The 'shortcall'
+ different (more expensive) calling sequence. The `shortcall'
attribute indicates that the function is always close enough for
- the shorter calling sequence to be used. These attributes override
- both the '-mlongcall' switch and, on the RS/6000 and PowerPC, the
- '#pragma longcall' setting.
+ the shorter calling sequence to be used. These attributes
+ override both the `-mlongcall' switch and, on the RS/6000 and
+ PowerPC, the `#pragma longcall' setting.
*Note RS/6000 and PowerPC Options::, for more information on
whether long calls are necessary.
-'long_call'
-'near'
-'far'
+`long_call'
+`near'
+`far'
These attributes specify how a particular function is called on
- MIPS. The attributes override the '-mlong-calls' (*note MIPS
- Options::) command-line switch. The 'long_call' and 'far'
+ MIPS. The attributes override the `-mlong-calls' (*note MIPS
+ Options::) command-line switch. The `long_call' and `far'
attributes are synonyms, and cause the compiler to always call the
function by first loading its address into a register, and then
- using the contents of that register. The 'near' attribute has the
+ using the contents of that register. The `near' attribute has the
opposite effect; it specifies that non-PIC calls should be made
- using the more efficient 'jal' instruction.
+ using the more efficient `jal' instruction.
-'malloc'
- This tells the compiler that a function is 'malloc'-like, i.e.,
+`malloc'
+ This tells the compiler that a function is `malloc'-like, i.e.,
that the pointer P returned by the function cannot alias any other
pointer valid when the function returns, and moreover no pointers
to valid objects occur in any storage addressed by P.
Using this attribute can improve optimization. Functions like
- 'malloc' and 'calloc' have this property because they return a
+ `malloc' and `calloc' have this property because they return a
pointer to uninitialized or zeroed-out storage. However, functions
- like 'realloc' do not have this property, as they can return a
+ like `realloc' do not have this property, as they can return a
pointer to storage containing pointers.
-'mips16'
-'nomips16'
-
- On MIPS targets, you can use the 'mips16' and 'nomips16' function
- attributes to locally select or turn off MIPS16 code generation. A
- function with the 'mips16' attribute is emitted as MIPS16 code,
+`mips16'
+`nomips16'
+ On MIPS targets, you can use the `mips16' and `nomips16' function
+ attributes to locally select or turn off MIPS16 code generation.
+ A function with the `mips16' attribute is emitted as MIPS16 code,
while MIPS16 code generation is disabled for functions with the
- 'nomips16' attribute. These attributes override the '-mips16' and
- '-mno-mips16' options on the command line (*note MIPS Options::).
+ `nomips16' attribute. These attributes override the `-mips16' and
+ `-mno-mips16' options on the command line (*note MIPS Options::).
When compiling files containing mixed MIPS16 and non-MIPS16 code,
- the preprocessor symbol '__mips16' reflects the setting on the
+ the preprocessor symbol `__mips16' reflects the setting on the
command line, not that within individual functions. Mixed MIPS16
and non-MIPS16 code may interact badly with some GCC extensions
- such as '__builtin_apply' (*note Constructing Calls::).
-
-'micromips, MIPS'
-'nomicromips, MIPS'
+ such as `__builtin_apply' (*note Constructing Calls::).
- On MIPS targets, you can use the 'micromips' and 'nomicromips'
+`micromips, MIPS'
+`nomicromips, MIPS'
+ On MIPS targets, you can use the `micromips' and `nomicromips'
function attributes to locally select or turn off microMIPS code
- generation. A function with the 'micromips' attribute is emitted
+ generation. A function with the `micromips' attribute is emitted
as microMIPS code, while microMIPS code generation is disabled for
- functions with the 'nomicromips' attribute. These attributes
- override the '-mmicromips' and '-mno-micromips' options on the
+ functions with the `nomicromips' attribute. These attributes
+ override the `-mmicromips' and `-mno-micromips' options on the
command line (*note MIPS Options::).
When compiling files containing mixed microMIPS and non-microMIPS
- code, the preprocessor symbol '__mips_micromips' reflects the
+ code, the preprocessor symbol `__mips_micromips' reflects the
setting on the command line, not that within individual functions.
- Mixed microMIPS and non-microMIPS code may interact badly with some
- GCC extensions such as '__builtin_apply' (*note Constructing
+ Mixed microMIPS and non-microMIPS code may interact badly with
+ some GCC extensions such as `__builtin_apply' (*note Constructing
Calls::).
-'model (MODEL-NAME)'
-
+`model (MODEL-NAME)'
On the M32R/D, use this attribute to set the addressability of an
object, and of the code generated for a function. The identifier
- MODEL-NAME is one of 'small', 'medium', or 'large', representing
+ MODEL-NAME is one of `small', `medium', or `large', representing
each of the code models.
Small model objects live in the lower 16MB of memory (so that their
- addresses can be loaded with the 'ld24' instruction), and are
- callable with the 'bl' instruction.
+ addresses can be loaded with the `ld24' instruction), and are
+ callable with the `bl' instruction.
Medium model objects may live anywhere in the 32-bit address space
- (the compiler generates 'seth/add3' instructions to load their
- addresses), and are callable with the 'bl' instruction.
+ (the compiler generates `seth/add3' instructions to load their
+ addresses), and are callable with the `bl' instruction.
Large model objects may live anywhere in the 32-bit address space
- (the compiler generates 'seth/add3' instructions to load their
- addresses), and may not be reachable with the 'bl' instruction (the
- compiler generates the much slower 'seth/add3/jl' instruction
+ (the compiler generates `seth/add3' instructions to load their
+ addresses), and may not be reachable with the `bl' instruction
+ (the compiler generates the much slower `seth/add3/jl' instruction
sequence).
-'ms_abi'
-'sysv_abi'
-
+`ms_abi'
+`sysv_abi'
On 32-bit and 64-bit x86 targets, you can use an ABI attribute to
indicate which calling convention should be used for a function.
- The 'ms_abi' attribute tells the compiler to use the Microsoft ABI,
- while the 'sysv_abi' attribute tells the compiler to use the ABI
+ The `ms_abi' attribute tells the compiler to use the Microsoft ABI,
+ while the `sysv_abi' attribute tells the compiler to use the ABI
used on GNU/Linux and other systems. The default is to use the
Microsoft ABI when targeting Windows. On all other systems, the
default is the x86/AMD ABI.
- Note, the 'ms_abi' attribute for Microsoft Windows 64-bit targets
- currently requires the '-maccumulate-outgoing-args' option.
-
-'callee_pop_aggregate_return (NUMBER)'
+ Note, the `ms_abi' attribute for Microsoft Windows 64-bit targets
+ currently requires the `-maccumulate-outgoing-args' option.
+`callee_pop_aggregate_return (NUMBER)'
On x86-32 targets, you can use this attribute to control how
aggregates are returned in memory. If the caller is responsible
for popping the hidden pointer together with the rest of the
@@ -25695,76 +25902,74 @@ attributes.
hidden pointer. However, on x86-32 Microsoft Windows targets, the
compiler assumes that the caller pops the stack for hidden pointer.
-'ms_hook_prologue'
-
+`ms_hook_prologue'
On 32-bit and 64-bit x86 targets, you can use this function
- attribute to make GCC generate the "hot-patching" function prologue
- used in Win32 API functions in Microsoft Windows XP Service Pack 2
- and newer.
-
-'hotpatch (HALFWORDS-BEFORE-FUNCTION-LABEL,HALFWORDS-AFTER-FUNCTION-LABEL)'
+ attribute to make GCC generate the "hot-patching" function
+ prologue used in Win32 API functions in Microsoft Windows XP
+ Service Pack 2 and newer.
+`hotpatch (HALFWORDS-BEFORE-FUNCTION-LABEL,HALFWORDS-AFTER-FUNCTION-LABEL)'
On S/390 System z targets, you can use this function attribute to
make GCC generate a "hot-patching" function prologue. If the
- '-mhotpatch=' command-line option is used at the same time, the
- 'hotpatch' attribute takes precedence. The first of the two
+ `-mhotpatch=' command-line option is used at the same time, the
+ `hotpatch' attribute takes precedence. The first of the two
arguments specifies the number of halfwords to be added before the
function label. A second argument can be used to specify the
- number of halfwords to be added after the function label. For both
- arguments the maximum allowed value is 1000000.
+ number of halfwords to be added after the function label. For
+ both arguments the maximum allowed value is 1000000.
If both arguments are zero, hotpatching is disabled.
-'naked'
+`naked'
This attribute is available on the ARM, AVR, MCORE, MSP430, NDS32,
RL78, RX and SPU ports. It allows the compiler to construct the
requisite function declaration, while allowing the body of the
- function to be assembly code. The specified function will not have
- prologue/epilogue sequences generated by the compiler. Only basic
- 'asm' statements can safely be included in naked functions (*note
- Basic Asm::). While using extended 'asm' or a mixture of basic
- 'asm' and C code may appear to work, they cannot be depended upon
+ function to be assembly code. The specified function will not have
+ prologue/epilogue sequences generated by the compiler. Only basic
+ `asm' statements can safely be included in naked functions (*note
+ Basic Asm::). While using extended `asm' or a mixture of basic
+ `asm' and C code may appear to work, they cannot be depended upon
to work reliably and are not supported.
-'near'
+`near'
On MeP targets this attribute causes the compiler to assume the
called function is close enough to use the normal calling
- convention, overriding the '-mtf' command-line option.
+ convention, overriding the `-mtf' command-line option.
-'nesting'
- Use this attribute together with 'interrupt_handler',
- 'exception_handler' or 'nmi_handler' to indicate that the function
+`nesting'
+ Use this attribute together with `interrupt_handler',
+ `exception_handler' or `nmi_handler' to indicate that the function
entry code should enable nested interrupts or exceptions.
-'nmi_handler'
+`nmi_handler'
Use this attribute on the Blackfin to indicate that the specified
function is an NMI handler. The compiler generates function entry
and exit sequences suitable for use in an NMI handler when this
attribute is present.
-'nocompression'
- On MIPS targets, you can use the 'nocompression' function attribute
+`nocompression'
+ On MIPS targets, you can use the `nocompression' function attribute
to locally turn off MIPS16 and microMIPS code generation. This
- attribute overrides the '-mips16' and '-mmicromips' options on the
+ attribute overrides the `-mips16' and `-mmicromips' options on the
command line (*note MIPS Options::).
-'no_instrument_function'
- If '-finstrument-functions' is given, profiling function calls are
+`no_instrument_function'
+ If `-finstrument-functions' is given, profiling function calls are
generated at entry and exit of most user-compiled functions.
Functions with this attribute are not so instrumented.
-'no_split_stack'
- If '-fsplit-stack' is given, functions have a small prologue which
+`no_split_stack'
+ If `-fsplit-stack' is given, functions have a small prologue which
decides whether to split the stack. Functions with the
- 'no_split_stack' attribute do not have that prologue, and thus may
+ `no_split_stack' attribute do not have that prologue, and thus may
run with only a small amount of stack space available.
-'stack_protect'
+`stack_protect'
This function attribute make a stack protection of the function if
- flags 'fstack-protector' or 'fstack-protector-strong' or
- 'fstack-protector-explicit' are set.
+ flags `fstack-protector' or `fstack-protector-strong' or
+ `fstack-protector-explicit' are set.
-'noinline'
+`noinline'
This function attribute prevents a function from being considered
for inlining. If the function does not have side-effects, there
are optimizations other than inlining that cause function calls to
@@ -25775,33 +25980,33 @@ attributes.
(*note Extended Asm::) in the called function, to serve as a
special side-effect.
-'noclone'
+`noclone'
This function attribute prevents a function from being considered
for cloning--a mechanism that produces specialized copies of
functions and which is (currently) performed by interprocedural
constant propagation.
-'no_icf'
- This function attribute prevents a functions from being merged with
- another semantically equivalent function.
+`no_icf'
+ This function attribute prevents a functions from being merged
+ with another semantically equivalent function.
-'nonnull (ARG-INDEX, ...)'
- The 'nonnull' attribute specifies that some function parameters
+`nonnull (ARG-INDEX, ...)'
+ The `nonnull' attribute specifies that some function parameters
should be non-null pointers. For instance, the declaration:
extern void *
my_memcpy (void *dest, const void *src, size_t len)
__attribute__((nonnull (1, 2)));
- causes the compiler to check that, in calls to 'my_memcpy',
+ causes the compiler to check that, in calls to `my_memcpy',
arguments DEST and SRC are non-null. If the compiler determines
that a null pointer is passed in an argument slot marked as
- non-null, and the '-Wnonnull' option is enabled, a warning is
+ non-null, and the `-Wnonnull' option is enabled, a warning is
issued. The compiler may also choose to make optimizations based
on the knowledge that certain function arguments will never be
null.
- If no argument index list is given to the 'nonnull' attribute, all
+ If no argument index list is given to the `nonnull' attribute, all
pointer arguments are marked as non-null. To illustrate, the
following declaration is equivalent to the previous example:
@@ -25809,16 +26014,16 @@ attributes.
my_memcpy (void *dest, const void *src, size_t len)
__attribute__((nonnull));
-'no_reorder'
- Do not reorder functions or variables marked 'no_reorder' against
+`no_reorder'
+ Do not reorder functions or variables marked `no_reorder' against
each other or top level assembler statements the executable. The
- actual order in the program will depend on the linker command line.
- Static variables marked like this are also not removed. This has a
- similar effect as the '-fno-toplevel-reorder' option, but only
- applies to the marked symbols.
+ actual order in the program will depend on the linker command
+ line. Static variables marked like this are also not removed.
+ This has a similar effect as the `-fno-toplevel-reorder' option,
+ but only applies to the marked symbols.
-'returns_nonnull'
- The 'returns_nonnull' attribute specifies that the function return
+`returns_nonnull'
+ The `returns_nonnull' attribute specifies that the function return
value should be a non-null pointer. For instance, the declaration:
extern void *
@@ -25827,11 +26032,11 @@ attributes.
lets the compiler optimize callers based on the knowledge that the
return value will never be null.
-'noreturn'
- A few standard library functions, such as 'abort' and 'exit',
+`noreturn'
+ A few standard library functions, such as `abort' and `exit',
cannot return. GCC knows this automatically. Some programs define
their own functions that never return. You can declare them
- 'noreturn' to tell the compiler this fact. For example,
+ `noreturn' to tell the compiler this fact. For example,
void fatal () __attribute__ ((noreturn));
@@ -25842,45 +26047,45 @@ attributes.
exit (1);
}
- The 'noreturn' keyword tells the compiler to assume that 'fatal'
+ The `noreturn' keyword tells the compiler to assume that `fatal'
cannot return. It can then optimize without regard to what would
- happen if 'fatal' ever did return. This makes slightly better
+ happen if `fatal' ever did return. This makes slightly better
code. More importantly, it helps avoid spurious warnings of
uninitialized variables.
- The 'noreturn' keyword does not affect the exceptional path when
- that applies: a 'noreturn'-marked function may still return to the
- caller by throwing an exception or calling 'longjmp'.
+ The `noreturn' keyword does not affect the exceptional path when
+ that applies: a `noreturn'-marked function may still return to the
+ caller by throwing an exception or calling `longjmp'.
Do not assume that registers saved by the calling function are
- restored before calling the 'noreturn' function.
+ restored before calling the `noreturn' function.
- It does not make sense for a 'noreturn' function to have a return
- type other than 'void'.
+ It does not make sense for a `noreturn' function to have a return
+ type other than `void'.
-'nothrow'
- The 'nothrow' attribute is used to inform the compiler that a
+`nothrow'
+ The `nothrow' attribute is used to inform the compiler that a
function cannot throw an exception. For example, most functions in
the standard C library can be guaranteed not to throw an exception
- with the notable exceptions of 'qsort' and 'bsearch' that take
+ with the notable exceptions of `qsort' and `bsearch' that take
function pointer arguments.
-'nosave_low_regs'
+`nosave_low_regs'
Use this attribute on SH targets to indicate that an
- 'interrupt_handler' function should not save and restore registers
+ `interrupt_handler' function should not save and restore registers
R0..R7. This can be used on SH3* and SH4* targets that have a
second R0..R7 register bank for non-reentrant interrupt handlers.
-'optimize'
- The 'optimize' attribute is used to specify that a function is to
+`optimize'
+ The `optimize' attribute is used to specify that a function is to
be compiled with different optimization options than specified on
the command line. Arguments can either be numbers or strings.
Numbers are assumed to be an optimization level. Strings that
- begin with 'O' are assumed to be an optimization option, while
- other options are assumed to be used with a '-f' prefix. You can
- also use the '#pragma GCC optimize' pragma to set the optimization
+ begin with `O' are assumed to be an optimization option, while
+ other options are assumed to be used with a `-f' prefix. You can
+ also use the `#pragma GCC optimize' pragma to set the optimization
options that affect more than one function. *Note Function
- Specific Option Pragmas::, for details about the '#pragma GCC
+ Specific Option Pragmas::, for details about the `#pragma GCC
optimize' pragma.
This can be used for instance to have frequently-executed functions
@@ -25888,81 +26093,81 @@ attributes.
faster and larger code, while other functions can be compiled with
less aggressive options.
-'OS_main'
-'OS_task'
- On AVR, functions with the 'OS_main' or 'OS_task' attribute do not
+`OS_main'
+`OS_task'
+ On AVR, functions with the `OS_main' or `OS_task' attribute do not
save/restore any call-saved register in their prologue/epilogue.
- The 'OS_main' attribute can be used when there _is guarantee_ that
+ The `OS_main' attribute can be used when there _is guarantee_ that
interrupts are disabled at the time when the function is entered.
This saves resources when the stack pointer has to be changed to
set up a frame for local variables.
- The 'OS_task' attribute can be used when there is _no guarantee_
+ The `OS_task' attribute can be used when there is _no guarantee_
that interrupts are disabled at that time when the function is
- entered like for, e.g. task functions in a multi-threading
- operating system. In that case, changing the stack pointer
+ entered like for, e.g. task functions in a multi-threading
+ operating system. In that case, changing the stack pointer
register is guarded by save/clear/restore of the global interrupt
enable flag.
- The differences to the 'naked' function attribute are:
- * 'naked' functions do not have a return instruction whereas
- 'OS_main' and 'OS_task' functions have a 'RET' or 'RETI'
+ The differences to the `naked' function attribute are:
+ * `naked' functions do not have a return instruction whereas
+ `OS_main' and `OS_task' functions have a `RET' or `RETI'
return instruction.
- * 'naked' functions do not set up a frame for local variables or
- a frame pointer whereas 'OS_main' and 'OS_task' do this as
- needed.
-'pcs'
+ * `naked' functions do not set up a frame for local variables
+ or a frame pointer whereas `OS_main' and `OS_task' do this as
+ needed.
- The 'pcs' attribute can be used to control the calling convention
- used for a function on ARM. The attribute takes an argument that
+`pcs'
+ The `pcs' attribute can be used to control the calling convention
+ used for a function on ARM. The attribute takes an argument that
specifies the calling convention to use.
When compiling using the AAPCS ABI (or a variant of it) then valid
- values for the argument are '"aapcs"' and '"aapcs-vfp"'. In order
- to use a variant other than '"aapcs"' then the compiler must be
+ values for the argument are `"aapcs"' and `"aapcs-vfp"'. In order
+ to use a variant other than `"aapcs"' then the compiler must be
permitted to use the appropriate co-processor registers (i.e., the
- VFP registers must be available in order to use '"aapcs-vfp"').
+ VFP registers must be available in order to use `"aapcs-vfp"').
For example,
/* Argument passed in r0, and result returned in r0+r1. */
double f2d (float) __attribute__((pcs("aapcs")));
- Variadic functions always use the '"aapcs"' calling convention and
+ Variadic functions always use the `"aapcs"' calling convention and
the compiler rejects attempts to specify an alternative.
-'pure'
+`pure'
Many functions have no effects except the return value and their
return value depends only on the parameters and/or global
variables. Such a function can be subject to common subexpression
elimination and loop optimization just as an arithmetic operator
would be. These functions should be declared with the attribute
- 'pure'. For example,
+ `pure'. For example,
int square (int) __attribute__ ((pure));
- says that the hypothetical function 'square' is safe to call fewer
+ says that the hypothetical function `square' is safe to call fewer
times than the program says.
- Some of common examples of pure functions are 'strlen' or 'memcmp'.
- Interesting non-pure functions are functions with infinite loops or
- those depending on volatile memory or other system resource, that
- may change between two consecutive calls (such as 'feof' in a
+ Some of common examples of pure functions are `strlen' or `memcmp'.
+ Interesting non-pure functions are functions with infinite loops
+ or those depending on volatile memory or other system resource,
+ that may change between two consecutive calls (such as `feof' in a
multithreading environment).
-'hot'
- The 'hot' attribute on a function is used to inform the compiler
+`hot'
+ The `hot' attribute on a function is used to inform the compiler
that the function is a hot spot of the compiled program. The
function is optimized more aggressively and on many targets it is
placed into a special subsection of the text section so all hot
functions appear close together, improving locality.
- When profile feedback is available, via '-fprofile-use', hot
+ When profile feedback is available, via `-fprofile-use', hot
functions are automatically detected and this attribute is ignored.
-'cold'
- The 'cold' attribute on functions is used to inform the compiler
+`cold'
+ The `cold' attribute on functions is used to inform the compiler
that the function is unlikely to be executed. The function is
optimized for size rather than speed and on many targets it is
placed into a special subsection of the text section so all cold
@@ -25970,202 +26175,203 @@ attributes.
non-cold parts of program. The paths leading to calls of cold
functions within code are marked as unlikely by the branch
prediction mechanism. It is thus useful to mark functions used to
- handle unlikely conditions, such as 'perror', as cold to improve
- optimization of hot functions that do call marked functions in rare
- occasions.
+ handle unlikely conditions, such as `perror', as cold to improve
+ optimization of hot functions that do call marked functions in
+ rare occasions.
- When profile feedback is available, via '-fprofile-use', cold
+ When profile feedback is available, via `-fprofile-use', cold
functions are automatically detected and this attribute is ignored.
-'no_sanitize_address'
-'no_address_safety_analysis'
- The 'no_sanitize_address' attribute on functions is used to inform
+`no_sanitize_address'
+`no_address_safety_analysis'
+ The `no_sanitize_address' attribute on functions is used to inform
the compiler that it should not instrument memory accesses in the
- function when compiling with the '-fsanitize=address' option. The
- 'no_address_safety_analysis' is a deprecated alias of the
- 'no_sanitize_address' attribute, new code should use
- 'no_sanitize_address'.
+ function when compiling with the `-fsanitize=address' option. The
+ `no_address_safety_analysis' is a deprecated alias of the
+ `no_sanitize_address' attribute, new code should use
+ `no_sanitize_address'.
-'no_sanitize_thread'
- The 'no_sanitize_thread' attribute on functions is used to inform
+`no_sanitize_thread'
+ The `no_sanitize_thread' attribute on functions is used to inform
the compiler that it should not instrument memory accesses in the
- function when compiling with the '-fsanitize=thread' option.
+ function when compiling with the `-fsanitize=thread' option.
-'no_sanitize_undefined'
- The 'no_sanitize_undefined' attribute on functions is used to
+`no_sanitize_undefined'
+ The `no_sanitize_undefined' attribute on functions is used to
inform the compiler that it should not check for undefined behavior
- in the function when compiling with the '-fsanitize=undefined'
+ in the function when compiling with the `-fsanitize=undefined'
option.
-'bnd_legacy'
- The 'bnd_legacy' attribute on functions is used to inform the
+`bnd_legacy'
+ The `bnd_legacy' attribute on functions is used to inform the
compiler that the function should not be instrumented when compiled
- with the '-fcheck-pointer-bounds' option.
+ with the `-fcheck-pointer-bounds' option.
-'bnd_instrument'
- The 'bnd_instrument' attribute on functions is used to inform the
+`bnd_instrument'
+ The `bnd_instrument' attribute on functions is used to inform the
compiler that the function should be instrumented when compiled
- with the '-fchkp-instrument-marked-only' option.
+ with the `-fchkp-instrument-marked-only' option.
-'regparm (NUMBER)'
- On x86-32 targets, the 'regparm' attribute causes the compiler to
- pass arguments number one to NUMBER if they are of integral type in
- registers EAX, EDX, and ECX instead of on the stack. Functions
+`regparm (NUMBER)'
+ On x86-32 targets, the `regparm' attribute causes the compiler to
+ pass arguments number one to NUMBER if they are of integral type
+ in registers EAX, EDX, and ECX instead of on the stack. Functions
that take a variable number of arguments continue to be passed all
of their arguments on the stack.
Beware that on some ELF systems this attribute is unsuitable for
global functions in shared libraries with lazy binding (which is
- the default). Lazy binding sends the first call via resolving code
- in the loader, which might assume EAX, EDX and ECX can be
+ the default). Lazy binding sends the first call via resolving
+ code in the loader, which might assume EAX, EDX and ECX can be
clobbered, as per the standard calling conventions. Solaris 8 is
affected by this. Systems with the GNU C Library version 2.1 or
higher and FreeBSD are believed to be safe since the loaders there
- save EAX, EDX and ECX. (Lazy binding can be disabled with the
+ save EAX, EDX and ECX. (Lazy binding can be disabled with the
linker or the loader if desired, to avoid the problem.)
-'reset'
+`reset'
Use this attribute on the NDS32 target to indicate that the
specified function is a reset handler. The compiler will generate
- corresponding sections for use in a reset handler. You can use the
- following attributes to provide extra exception handling:
- 'nmi'
+ corresponding sections for use in a reset handler. You can use
+ the following attributes to provide extra exception handling:
+ `nmi'
Provide a user-defined function to handle NMI exception.
- 'warm'
+
+ `warm'
Provide a user-defined function to handle warm reset
exception.
-'sseregparm'
- On x86-32 targets with SSE support, the 'sseregparm' attribute
- causes the compiler to pass up to 3 floating-point arguments in SSE
- registers instead of on the stack. Functions that take a variable
- number of arguments continue to pass all of their floating-point
- arguments on the stack.
+`sseregparm'
+ On x86-32 targets with SSE support, the `sseregparm' attribute
+ causes the compiler to pass up to 3 floating-point arguments in
+ SSE registers instead of on the stack. Functions that take a
+ variable number of arguments continue to pass all of their
+ floating-point arguments on the stack.
-'force_align_arg_pointer'
- On x86 targets, the 'force_align_arg_pointer' attribute may be
+`force_align_arg_pointer'
+ On x86 targets, the `force_align_arg_pointer' attribute may be
applied to individual function definitions, generating an alternate
prologue and epilogue that realigns the run-time stack if
necessary. This supports mixing legacy codes that run with a
4-byte aligned stack with modern codes that keep a 16-byte stack
for SSE compatibility.
-'renesas'
+`renesas'
On SH targets this attribute specifies that the function or struct
follows the Renesas ABI.
-'resbank'
+`resbank'
On the SH2A target, this attribute enables the high-speed register
saving and restoration using a register bank for
- 'interrupt_handler' routines. Saving to the bank is performed
+ `interrupt_handler' routines. Saving to the bank is performed
automatically after the CPU accepts an interrupt that uses a
register bank.
The nineteen 32-bit registers comprising general register R0 to
R14, control register GBR, and system registers MACH, MACL, and PR
- and the vector table address offset are saved into a register bank.
- Register banks are stacked in first-in last-out (FILO) sequence.
- Restoration from the bank is executed by issuing a RESBANK
- instruction.
+ and the vector table address offset are saved into a register
+ bank. Register banks are stacked in first-in last-out (FILO)
+ sequence. Restoration from the bank is executed by issuing a
+ RESBANK instruction.
-'returns_twice'
- The 'returns_twice' attribute tells the compiler that a function
+`returns_twice'
+ The `returns_twice' attribute tells the compiler that a function
may return more than one time. The compiler ensures that all
registers are dead before calling such a function and emits a
warning about the variables that may be clobbered after the second
- return from the function. Examples of such functions are 'setjmp'
- and 'vfork'. The 'longjmp'-like counterpart of such function, if
- any, might need to be marked with the 'noreturn' attribute.
+ return from the function. Examples of such functions are `setjmp'
+ and `vfork'. The `longjmp'-like counterpart of such function, if
+ any, might need to be marked with the `noreturn' attribute.
-'saveall'
+`saveall'
Use this attribute on the Blackfin, H8/300, H8/300H, and H8S to
indicate that all registers except the stack pointer should be
saved in the prologue regardless of whether they are used or not.
-'save_volatiles'
+`save_volatiles'
Use this attribute on the MicroBlaze to indicate that the function
is an interrupt handler. All volatile registers (in addition to
- non-volatile registers) are saved in the function prologue. If the
- function is a leaf function, only volatiles used by the function
- are saved. A normal function return is generated instead of a
- return from interrupt.
+ non-volatile registers) are saved in the function prologue. If
+ the function is a leaf function, only volatiles used by the
+ function are saved. A normal function return is generated instead
+ of a return from interrupt.
-'break_handler'
+`break_handler'
Use this attribute on the MicroBlaze ports to indicate that the
specified function is a break handler. The compiler generates
function entry and exit sequences suitable for use in an break
- handler when this attribute is present. The return from
- 'break_handler' is done through the 'rtbd' instead of 'rtsd'.
+ handler when this attribute is present. The return from
+ `break_handler' is done through the `rtbd' instead of `rtsd'.
void f () __attribute__ ((break_handler));
-'section ("SECTION-NAME")'
- Normally, the compiler places the code it generates in the 'text'
+`section ("SECTION-NAME")'
+ Normally, the compiler places the code it generates in the `text'
section. Sometimes, however, you need additional sections, or you
need certain particular functions to appear in special sections.
- The 'section' attribute specifies that a function lives in a
+ The `section' attribute specifies that a function lives in a
particular section. For example, the declaration:
extern void foobar (void) __attribute__ ((section ("bar")));
- puts the function 'foobar' in the 'bar' section.
+ puts the function `foobar' in the `bar' section.
Some file formats do not support arbitrary sections so the
- 'section' attribute is not available on all platforms. If you need
- to map the entire contents of a module to a particular section,
- consider using the facilities of the linker instead.
-
-'sentinel'
- This function attribute ensures that a parameter in a function call
- is an explicit 'NULL'. The attribute is only valid on variadic
- functions. By default, the sentinel is located at position zero,
- the last parameter of the function call. If an optional integer
- position argument P is supplied to the attribute, the sentinel must
- be located at position P counting backwards from the end of the
- argument list.
+ `section' attribute is not available on all platforms. If you
+ need to map the entire contents of a module to a particular
+ section, consider using the facilities of the linker instead.
+
+`sentinel'
+ This function attribute ensures that a parameter in a function
+ call is an explicit `NULL'. The attribute is only valid on
+ variadic functions. By default, the sentinel is located at
+ position zero, the last parameter of the function call. If an
+ optional integer position argument P is supplied to the attribute,
+ the sentinel must be located at position P counting backwards from
+ the end of the argument list.
__attribute__ ((sentinel))
is equivalent to
__attribute__ ((sentinel(0)))
The attribute is automatically set with a position of 0 for the
- built-in functions 'execl' and 'execlp'. The built-in function
- 'execle' has the attribute set with a position of 1.
+ built-in functions `execl' and `execlp'. The built-in function
+ `execle' has the attribute set with a position of 1.
- A valid 'NULL' in this context is defined as zero with any pointer
- type. If your system defines the 'NULL' macro with an integer type
- then you need to add an explicit cast. GCC replaces 'stddef.h'
+ A valid `NULL' in this context is defined as zero with any pointer
+ type. If your system defines the `NULL' macro with an integer type
+ then you need to add an explicit cast. GCC replaces `stddef.h'
with a copy that redefines NULL appropriately.
The warnings for missing or incorrect sentinels are enabled with
- '-Wformat'.
+ `-Wformat'.
-'short_call'
- See 'long_call'.
+`short_call'
+ See `long_call'.
-'shortcall'
- See 'longcall'.
+`shortcall'
+ See `longcall'.
-'signal'
+`signal'
Use this attribute on the AVR to indicate that the specified
function is an interrupt handler. The compiler generates function
entry and exit sequences suitable for use in an interrupt handler
when this attribute is present.
- See also the 'interrupt' function attribute.
+ See also the `interrupt' function attribute.
The AVR hardware globally disables interrupts when an interrupt is
- executed. Interrupt handler functions defined with the 'signal'
+ executed. Interrupt handler functions defined with the `signal'
attribute do not re-enable interrupts. It is save to enable
- interrupts in a 'signal' handler. This "save" only applies to the
+ interrupts in a `signal' handler. This "save" only applies to the
code generated by the compiler and not to the IRQ layout of the
application which is responsibility of the application.
- If both 'signal' and 'interrupt' are specified for the same
- function, 'signal' is silently ignored.
+ If both `signal' and `interrupt' are specified for the same
+ function, `signal' is silently ignored.
-'sp_switch'
- Use this attribute on the SH to indicate an 'interrupt_handler'
+`sp_switch'
+ Use this attribute on the SH to indicate an `interrupt_handler'
function should switch to an alternate stack. It expects a string
argument that names a global variable holding the address of the
alternate stack.
@@ -26174,340 +26380,340 @@ attributes.
void f () __attribute__ ((interrupt_handler,
sp_switch ("alt_stack")));
-'stdcall'
- On x86-32 targets, the 'stdcall' attribute causes the compiler to
+`stdcall'
+ On x86-32 targets, the `stdcall' attribute causes the compiler to
assume that the called function pops off the stack space used to
pass arguments, unless it takes a variable number of arguments.
-'syscall_linkage'
+`syscall_linkage'
This attribute is used to modify the IA-64 calling convention by
marking all input registers as live at all function exits. This
makes it possible to restart a system call after an interrupt
without having to save/restore the input registers. This also
prevents kernel data from leaking into application code.
-'target'
- The 'target' attribute is used to specify that a function is to be
+`target'
+ The `target' attribute is used to specify that a function is to be
compiled with different target options than specified on the
command line. This can be used for instance to have functions
compiled with a different ISA (instruction set architecture) than
- the default. You can also use the '#pragma GCC target' pragma to
+ the default. You can also use the `#pragma GCC target' pragma to
set more than one function to be compiled with specific target
options. *Note Function Specific Option Pragmas::, for details
- about the '#pragma GCC target' pragma.
+ about the `#pragma GCC target' pragma.
For instance on an x86, you could compile one function with
- 'target("sse4.1,arch=core2")' and another with
- 'target("sse4a,arch=amdfam10")'. This is equivalent to compiling
- the first function with '-msse4.1' and '-march=core2' options, and
- the second function with '-msse4a' and '-march=amdfam10' options.
+ `target("sse4.1,arch=core2")' and another with
+ `target("sse4a,arch=amdfam10")'. This is equivalent to compiling
+ the first function with `-msse4.1' and `-march=core2' options, and
+ the second function with `-msse4a' and `-march=amdfam10' options.
It is up to the user to make sure that a function is only invoked
on a machine that supports the particular ISA it is compiled for
- (for example by using 'cpuid' on x86 to determine what feature bits
- and architecture family are used).
+ (for example by using `cpuid' on x86 to determine what feature
+ bits and architecture family are used).
int core2_func (void) __attribute__ ((__target__ ("arch=core2")));
int sse3_func (void) __attribute__ ((__target__ ("sse3")));
- You can either use multiple strings to specify multiple options, or
- separate the options with a comma (',').
+ You can either use multiple strings to specify multiple options,
+ or separate the options with a comma (`,').
- The 'target' attribute is presently implemented for x86, PowerPC,
+ The `target' attribute is presently implemented for x86, PowerPC,
and Nios II targets only. The options supported are specific to
each target.
On the x86, the following options are allowed:
- 'abm'
- 'no-abm'
+ `abm'
+ `no-abm'
Enable/disable the generation of the advanced bit
instructions.
- 'aes'
- 'no-aes'
+ `aes'
+ `no-aes'
Enable/disable the generation of the AES instructions.
- 'default'
+ `default'
*Note Function Multiversioning::, where it is used to specify
the default function version.
- 'mmx'
- 'no-mmx'
+ `mmx'
+ `no-mmx'
Enable/disable the generation of the MMX instructions.
- 'pclmul'
- 'no-pclmul'
+ `pclmul'
+ `no-pclmul'
Enable/disable the generation of the PCLMUL instructions.
- 'popcnt'
- 'no-popcnt'
+ `popcnt'
+ `no-popcnt'
Enable/disable the generation of the POPCNT instruction.
- 'sse'
- 'no-sse'
+ `sse'
+ `no-sse'
Enable/disable the generation of the SSE instructions.
- 'sse2'
- 'no-sse2'
+ `sse2'
+ `no-sse2'
Enable/disable the generation of the SSE2 instructions.
- 'sse3'
- 'no-sse3'
+ `sse3'
+ `no-sse3'
Enable/disable the generation of the SSE3 instructions.
- 'sse4'
- 'no-sse4'
+ `sse4'
+ `no-sse4'
Enable/disable the generation of the SSE4 instructions (both
SSE4.1 and SSE4.2).
- 'sse4.1'
- 'no-sse4.1'
+ `sse4.1'
+ `no-sse4.1'
Enable/disable the generation of the sse4.1 instructions.
- 'sse4.2'
- 'no-sse4.2'
+ `sse4.2'
+ `no-sse4.2'
Enable/disable the generation of the sse4.2 instructions.
- 'sse4a'
- 'no-sse4a'
+ `sse4a'
+ `no-sse4a'
Enable/disable the generation of the SSE4A instructions.
- 'fma4'
- 'no-fma4'
+ `fma4'
+ `no-fma4'
Enable/disable the generation of the FMA4 instructions.
- 'xop'
- 'no-xop'
+ `xop'
+ `no-xop'
Enable/disable the generation of the XOP instructions.
- 'lwp'
- 'no-lwp'
+ `lwp'
+ `no-lwp'
Enable/disable the generation of the LWP instructions.
- 'ssse3'
- 'no-ssse3'
+ `ssse3'
+ `no-ssse3'
Enable/disable the generation of the SSSE3 instructions.
- 'cld'
- 'no-cld'
+ `cld'
+ `no-cld'
Enable/disable the generation of the CLD before string moves.
- 'fancy-math-387'
- 'no-fancy-math-387'
- Enable/disable the generation of the 'sin', 'cos', and 'sqrt'
+ `fancy-math-387'
+ `no-fancy-math-387'
+ Enable/disable the generation of the `sin', `cos', and `sqrt'
instructions on the 387 floating-point unit.
- 'fused-madd'
- 'no-fused-madd'
+ `fused-madd'
+ `no-fused-madd'
Enable/disable the generation of the fused multiply/add
instructions.
- 'ieee-fp'
- 'no-ieee-fp'
+ `ieee-fp'
+ `no-ieee-fp'
Enable/disable the generation of floating point that depends
on IEEE arithmetic.
- 'inline-all-stringops'
- 'no-inline-all-stringops'
+ `inline-all-stringops'
+ `no-inline-all-stringops'
Enable/disable inlining of string operations.
- 'inline-stringops-dynamically'
- 'no-inline-stringops-dynamically'
+ `inline-stringops-dynamically'
+ `no-inline-stringops-dynamically'
Enable/disable the generation of the inline code to do small
string operations and calling the library routines for large
operations.
- 'align-stringops'
- 'no-align-stringops'
+ `align-stringops'
+ `no-align-stringops'
Do/do not align destination of inlined string operations.
- 'recip'
- 'no-recip'
+ `recip'
+ `no-recip'
Enable/disable the generation of RCPSS, RCPPS, RSQRTSS and
RSQRTPS instructions followed an additional Newton-Raphson
step instead of doing a floating-point division.
- 'arch=ARCH'
- Specify the architecture to generate code for in compiling the
- function.
+ `arch=ARCH'
+ Specify the architecture to generate code for in compiling
+ the function.
- 'tune=TUNE'
+ `tune=TUNE'
Specify the architecture to tune for in compiling the
function.
- 'fpmath=FPMATH'
+ `fpmath=FPMATH'
Specify which floating-point unit to use. The
- 'target("fpmath=sse,387")' option must be specified as
- 'target("fpmath=sse+387")' because the comma would separate
+ `target("fpmath=sse,387")' option must be specified as
+ `target("fpmath=sse+387")' because the comma would separate
different options.
On the PowerPC, the following options are allowed:
- 'altivec'
- 'no-altivec'
+ `altivec'
+ `no-altivec'
Generate code that uses (does not use) AltiVec instructions.
In 32-bit code, you cannot enable AltiVec instructions unless
- '-mabi=altivec' is used on the command line.
+ `-mabi=altivec' is used on the command line.
- 'cmpb'
- 'no-cmpb'
+ `cmpb'
+ `no-cmpb'
Generate code that uses (does not use) the compare bytes
instruction implemented on the POWER6 processor and other
processors that support the PowerPC V2.05 architecture.
- 'dlmzb'
- 'no-dlmzb'
+ `dlmzb'
+ `no-dlmzb'
Generate code that uses (does not use) the string-search
- 'dlmzb' instruction on the IBM 405, 440, 464 and 476
+ `dlmzb' instruction on the IBM 405, 440, 464 and 476
processors. This instruction is generated by default when
targeting those processors.
- 'fprnd'
- 'no-fprnd'
+ `fprnd'
+ `no-fprnd'
Generate code that uses (does not use) the FP round to integer
instructions implemented on the POWER5+ processor and other
processors that support the PowerPC V2.03 architecture.
- 'hard-dfp'
- 'no-hard-dfp'
+ `hard-dfp'
+ `no-hard-dfp'
Generate code that uses (does not use) the decimal
floating-point instructions implemented on some POWER
processors.
- 'isel'
- 'no-isel'
+ `isel'
+ `no-isel'
Generate code that uses (does not use) ISEL instruction.
- 'mfcrf'
- 'no-mfcrf'
+ `mfcrf'
+ `no-mfcrf'
Generate code that uses (does not use) the move from condition
- register field instruction implemented on the POWER4 processor
- and other processors that support the PowerPC V2.01
+ register field instruction implemented on the POWER4
+ processor and other processors that support the PowerPC V2.01
architecture.
- 'mfpgpr'
- 'no-mfpgpr'
+ `mfpgpr'
+ `no-mfpgpr'
Generate code that uses (does not use) the FP move to/from
general purpose register instructions implemented on the
POWER6X processor and other processors that support the
extended PowerPC V2.05 architecture.
- 'mulhw'
- 'no-mulhw'
+ `mulhw'
+ `no-mulhw'
Generate code that uses (does not use) the half-word multiply
and multiply-accumulate instructions on the IBM 405, 440, 464
and 476 processors. These instructions are generated by
default when targeting those processors.
- 'multiple'
- 'no-multiple'
+ `multiple'
+ `no-multiple'
Generate code that uses (does not use) the load multiple word
instructions and the store multiple word instructions.
- 'update'
- 'no-update'
+ `update'
+ `no-update'
Generate code that uses (does not use) the load or store
instructions that update the base register to the address of
the calculated memory location.
- 'popcntb'
- 'no-popcntb'
+ `popcntb'
+ `no-popcntb'
Generate code that uses (does not use) the popcount and
double-precision FP reciprocal estimate instruction
implemented on the POWER5 processor and other processors that
support the PowerPC V2.02 architecture.
- 'popcntd'
- 'no-popcntd'
+ `popcntd'
+ `no-popcntd'
Generate code that uses (does not use) the popcount
instruction implemented on the POWER7 processor and other
processors that support the PowerPC V2.06 architecture.
- 'powerpc-gfxopt'
- 'no-powerpc-gfxopt'
+ `powerpc-gfxopt'
+ `no-powerpc-gfxopt'
Generate code that uses (does not use) the optional PowerPC
architecture instructions in the Graphics group, including
floating-point select.
- 'powerpc-gpopt'
- 'no-powerpc-gpopt'
+ `powerpc-gpopt'
+ `no-powerpc-gpopt'
Generate code that uses (does not use) the optional PowerPC
architecture instructions in the General Purpose group,
including floating-point square root.
- 'recip-precision'
- 'no-recip-precision'
+ `recip-precision'
+ `no-recip-precision'
Assume (do not assume) that the reciprocal estimate
instructions provide higher-precision estimates than is
mandated by the PowerPC ABI.
- 'string'
- 'no-string'
+ `string'
+ `no-string'
Generate code that uses (does not use) the load string
instructions and the store string word instructions to save
multiple registers and do small block moves.
- 'vsx'
- 'no-vsx'
+ `vsx'
+ `no-vsx'
Generate code that uses (does not use) vector/scalar (VSX)
instructions, and also enable the use of built-in functions
that allow more direct access to the VSX instruction set. In
32-bit code, you cannot enable VSX or AltiVec instructions
- unless '-mabi=altivec' is used on the command line.
+ unless `-mabi=altivec' is used on the command line.
- 'friz'
- 'no-friz'
- Generate (do not generate) the 'friz' instruction when the
- '-funsafe-math-optimizations' option is used to optimize
+ `friz'
+ `no-friz'
+ Generate (do not generate) the `friz' instruction when the
+ `-funsafe-math-optimizations' option is used to optimize
rounding a floating-point value to 64-bit integer and back to
- floating point. The 'friz' instruction does not return the
- same value if the floating-point number is too large to fit in
- an integer.
+ floating point. The `friz' instruction does not return the
+ same value if the floating-point number is too large to fit
+ in an integer.
- 'avoid-indexed-addresses'
- 'no-avoid-indexed-addresses'
+ `avoid-indexed-addresses'
+ `no-avoid-indexed-addresses'
Generate code that tries to avoid (not avoid) the use of
indexed load or store instructions.
- 'paired'
- 'no-paired'
+ `paired'
+ `no-paired'
Generate code that uses (does not use) the generation of
PAIRED simd instructions.
- 'longcall'
- 'no-longcall'
+ `longcall'
+ `no-longcall'
Generate code that assumes (does not assume) that all calls
are far away so that a longer more expensive calling sequence
is required.
- 'cpu=CPU'
+ `cpu=CPU'
Specify the architecture to generate code for when compiling
- the function. If you select the 'target("cpu=power7")'
+ the function. If you select the `target("cpu=power7")'
attribute when generating 32-bit code, VSX and AltiVec
instructions are not generated unless you use the
- '-mabi=altivec' option on the command line.
+ `-mabi=altivec' option on the command line.
- 'tune=TUNE'
+ `tune=TUNE'
Specify the architecture to tune for when compiling the
- function. If you do not specify the 'target("tune=TUNE")'
- attribute and you do specify the 'target("cpu=CPU")'
- attribute, compilation tunes for the CPU architecture, and not
- the default tuning specified on the command line.
+ function. If you do not specify the `target("tune=TUNE")'
+ attribute and you do specify the `target("cpu=CPU")'
+ attribute, compilation tunes for the CPU architecture, and
+ not the default tuning specified on the command line.
When compiling for Nios II, the following options are allowed:
- 'custom-INSN=N'
- 'no-custom-INSN'
- Each 'custom-INSN=N' attribute locally enables use of a custom
- instruction with encoding N when generating code that uses
- INSN. Similarly, 'no-custom-INSN' locally inhibits use of the
- custom instruction INSN. These target attributes correspond
- to the '-mcustom-INSN=N' and '-mno-custom-INSN' command-line
- options, and support the same set of INSN keywords. *Note
- Nios II Options::, for more information.
-
- 'custom-fpu-cfg=NAME'
- This attribute corresponds to the '-mcustom-fpu-cfg=NAME'
+ `custom-INSN=N'
+ `no-custom-INSN'
+ Each `custom-INSN=N' attribute locally enables use of a
+ custom instruction with encoding N when generating code that
+ uses INSN. Similarly, `no-custom-INSN' locally inhibits use
+ of the custom instruction INSN. These target attributes
+ correspond to the `-mcustom-INSN=N' and `-mno-custom-INSN'
+ command-line options, and support the same set of INSN
+ keywords. *Note Nios II Options::, for more information.
+
+ `custom-fpu-cfg=NAME'
+ This attribute corresponds to the `-mcustom-fpu-cfg=NAME'
command-line option, to select a predefined set of custom
instructions named NAME. *Note Nios II Options::, for more
information.
@@ -26515,41 +26721,41 @@ attributes.
On the x86 and PowerPC back ends, the inliner does not inline a
function that has different target options than the caller, unless
the callee has a subset of the target options of the caller. For
- example a function declared with 'target("sse3")' can inline a
- function with 'target("sse2")', since '-msse3' implies '-msse2'.
+ example a function declared with `target("sse3")' can inline a
+ function with `target("sse2")', since `-msse3' implies `-msse2'.
-'trap_exit'
- Use this attribute on the SH for an 'interrupt_handler' to return
- using 'trapa' instead of 'rte'. This attribute expects an integer
+`trap_exit'
+ Use this attribute on the SH for an `interrupt_handler' to return
+ using `trapa' instead of `rte'. This attribute expects an integer
argument specifying the trap number to be used.
-'trapa_handler'
+`trapa_handler'
On SH targets this function attribute is similar to
- 'interrupt_handler' but it does not save and restore all registers.
+ `interrupt_handler' but it does not save and restore all registers.
-'unused'
+`unused'
This attribute, attached to a function, means that the function is
meant to be possibly unused. GCC does not produce a warning for
this function.
-'used'
+`used'
This attribute, attached to a function, means that code must be
emitted for the function even if it appears that the function is
not referenced. This is useful, for example, when the function is
referenced only in inline assembly.
When applied to a member function of a C++ class template, the
- attribute also means that the function is instantiated if the class
- itself is instantiated.
+ attribute also means that the function is instantiated if the
+ class itself is instantiated.
-'vector'
- This RX attribute is similar to the 'interrupt' attribute,
+`vector'
+ This RX attribute is similar to the `interrupt' attribute,
including its parameters, but does not make the function an
- interrupt-handler type function (i.e. it retains the normal C
- function calling ABI). See the 'interrupt' attribute for a
+ interrupt-handler type function (i.e. it retains the normal C
+ function calling ABI). See the `interrupt' attribute for a
description of its arguments.
-'version_id'
+`version_id'
This IA-64 HP-UX attribute, attached to a global variable or
function, renames a symbol to contain a version string, thus
allowing for function level versioning. HP-UX system header files
@@ -26559,7 +26765,7 @@ attributes.
Calls to FOO are mapped to calls to FOO{20040821}.
-'visibility ("VISIBILITY_TYPE")'
+`visibility ("VISIBILITY_TYPE")'
This attribute affects the linkage of the declaration to which it
is attached. There are four supported VISIBILITY_TYPE values:
default, hidden, protected or internal visibility.
@@ -26568,10 +26774,10 @@ attributes.
f () { /* Do something. */; }
int i __attribute__ ((visibility ("hidden")));
- The possible values of VISIBILITY_TYPE correspond to the visibility
- settings in the ELF gABI.
+ The possible values of VISIBILITY_TYPE correspond to the
+ visibility settings in the ELF gABI.
- "default"
+ "default"
Default visibility is the normal case for the object file
format. This value is available for the visibility attribute
to override other options that may change the assumed
@@ -26587,32 +26793,33 @@ attributes.
Default visibility corresponds to "external linkage" in the
language.
- "hidden"
+ "hidden"
Hidden visibility indicates that the entity declared has a new
form of linkage, which we call "hidden linkage". Two
declarations of an object with hidden linkage refer to the
same object if they are in the same shared object.
- "internal"
+ "internal"
Internal visibility is like hidden visibility, but with
additional processor specific semantics. Unless otherwise
specified by the psABI, GCC defines internal visibility to
mean that a function is _never_ called from another module.
- Compare this with hidden functions which, while they cannot be
- referenced directly by other modules, can be referenced
+ Compare this with hidden functions which, while they cannot
+ be referenced directly by other modules, can be referenced
indirectly via function pointers. By indicating that a
- function cannot be called from outside the module, GCC may for
- instance omit the load of a PIC register since it is known
+ function cannot be called from outside the module, GCC may
+ for instance omit the load of a PIC register since it is known
that the calling function loaded the correct value.
- "protected"
+ "protected"
Protected visibility is like default visibility except that it
indicates that references within the defining module bind to
the definition in that module. That is, the declared entity
cannot be overridden by another module.
+
All visibilities are supported on many, but not all, ELF targets
- (supported when the assembler supports the '.visibility'
+ (supported when the assembler supports the `.visibility'
pseudo-op). Default visibility is supported everywhere. Hidden
visibility is supported on Darwin targets.
@@ -26644,7 +26851,7 @@ attributes.
This attribute applies only to the particular namespace body, not
to other definitions of the same namespace; it is equivalent to
- using '#pragma GCC visibility' before and after the namespace
+ using `#pragma GCC visibility' before and after the namespace
definition (*note Visibility Pragmas::).
In C++, if a template argument has limited visibility, this
@@ -26655,18 +26862,18 @@ attributes.
If both the template and enclosing class have explicit visibility,
the visibility from the template is used.
-'vliw'
- On MeP, the 'vliw' attribute tells the compiler to emit
+`vliw'
+ On MeP, the `vliw' attribute tells the compiler to emit
instructions in VLIW mode instead of core mode. Note that this
attribute is not allowed unless a VLIW coprocessor has been
configured and enabled through command-line options.
-'warn_unused_result'
- The 'warn_unused_result' attribute causes a warning to be emitted
+`warn_unused_result'
+ The `warn_unused_result' attribute causes a warning to be emitted
if a caller of the function with this attribute does not use its
return value. This is useful for functions where not checking the
result is either a security problem or always a bug, such as
- 'realloc'.
+ `realloc'.
int fn () __attribute__ ((warn_unused_result));
int foo ()
@@ -26678,23 +26885,23 @@ attributes.
results in warning on line 5.
-'weak'
- The 'weak' attribute causes the declaration to be emitted as a weak
+`weak'
+ The `weak' attribute causes the declaration to be emitted as a weak
symbol rather than a global. This is primarily useful in defining
library functions that can be overridden in user code, though it
can also be used with non-function declarations. Weak symbols are
supported for ELF targets, and also for a.out targets when using
the GNU assembler and linker.
-'weakref'
-'weakref ("TARGET")'
- The 'weakref' attribute marks a declaration as a weak reference.
- Without arguments, it should be accompanied by an 'alias' attribute
+`weakref'
+`weakref ("TARGET")'
+ The `weakref' attribute marks a declaration as a weak reference.
+ Without arguments, it should be accompanied by an `alias' attribute
naming the target symbol. Optionally, the TARGET may be given as
- an argument to 'weakref' itself. In either case, 'weakref'
- implicitly marks the declaration as 'weak'. Without a TARGET,
- given as an argument to 'weakref' or to 'alias', 'weakref' is
- equivalent to 'weak'.
+ an argument to `weakref' itself. In either case, `weakref'
+ implicitly marks the declaration as `weak'. Without a TARGET,
+ given as an argument to `weakref' or to `alias', `weakref' is
+ equivalent to `weak'.
static int x() __attribute__ ((weakref ("y")));
/* is equivalent to... */
@@ -26704,9 +26911,9 @@ attributes.
static int x() __attribute__ ((alias ("y")));
A weak reference is an alias that does not by itself require a
- definition to be given for the target symbol. If the target symbol
- is only referenced through weak references, then it becomes a
- 'weak' undefined symbol. If it is directly referenced, however,
+ definition to be given for the target symbol. If the target
+ symbol is only referenced through weak references, then it becomes
+ a `weak' undefined symbol. If it is directly referenced, however,
then such strong references prevail, and a definition is required
for the symbol, not necessarily in the same translation unit.
@@ -26715,33 +26922,34 @@ attributes.
symbol, declaring it as weak, compiling the two separate
translation units and performing a reloadable link on them.
- At present, a declaration to which 'weakref' is attached can only
- be 'static'.
+ At present, a declaration to which `weakref' is attached can only
+ be `static'.
+
You can specify multiple attributes in a declaration by separating them
by commas within the double parentheses or by immediately following an
attribute declaration with another attribute declaration.
- Some people object to the '__attribute__' feature, suggesting that ISO
-C's '#pragma' should be used instead. At the time '__attribute__' was
+ Some people object to the `__attribute__' feature, suggesting that ISO
+C's `#pragma' should be used instead. At the time `__attribute__' was
designed, there were two reasons for not doing this.
- 1. It is impossible to generate '#pragma' commands from a macro.
+ 1. It is impossible to generate `#pragma' commands from a macro.
- 2. There is no telling what the same '#pragma' might mean in another
+ 2. There is no telling what the same `#pragma' might mean in another
compiler.
These two reasons applied to almost any application that might have
-been proposed for '#pragma'. It was basically a mistake to use
-'#pragma' for _anything_.
+been proposed for `#pragma'. It was basically a mistake to use
+`#pragma' for _anything_.
- The ISO C99 standard includes '_Pragma', which now allows pragmas to be
-generated from macros. In addition, a '#pragma GCC' namespace is now in
-use for GCC-specific pragmas. However, it has been found convenient to
-use '__attribute__' to achieve a natural attachment of attributes to
-their corresponding declarations, whereas '#pragma GCC' is of use for
-constructs that do not naturally form part of the grammar. *Note
-Pragmas Accepted by GCC: Pragmas.
+ The ISO C99 standard includes `_Pragma', which now allows pragmas to
+be generated from macros. In addition, a `#pragma GCC' namespace is
+now in use for GCC-specific pragmas. However, it has been found
+convenient to use `__attribute__' to achieve a natural attachment of
+attributes to their corresponding declarations, whereas `#pragma GCC'
+is of use for constructs that do not naturally form part of the
+grammar. *Note Pragmas Accepted by GCC: Pragmas.

File: gcc.info, Node: Label Attributes, Next: Attribute Syntax, Prev: Function Attributes, Up: C Extensions
@@ -26754,9 +26962,9 @@ for details of the exact syntax for using attributes. Other attributes
are available for functions (*note Function Attributes::), variables
(*note Variable Attributes::) and for types (*note Type Attributes::).
- This example uses the 'cold' label attribute to indicate the
-'ErrorHandling' branch is unlikely to be taken and that the
-'ErrorHandling' label is unused:
+ This example uses the `cold' label attribute to indicate the
+`ErrorHandling' branch is unlikely to be taken and that the
+`ErrorHandling' label is unused:
asm goto ("some asm" : : : : NoError);
@@ -26771,25 +26979,26 @@ are available for functions (*note Function Attributes::), variables
printf("no error\n");
return 1;
-'unused'
+`unused'
This feature is intended for program-generated code that may
- contain unused labels, but which is compiled with '-Wall'. It is
+ contain unused labels, but which is compiled with `-Wall'. It is
not normally appropriate to use in it human-written code, though it
could be useful in cases where the code that jumps to the label is
- contained within an '#ifdef' conditional.
+ contained within an `#ifdef' conditional.
-'hot'
- The 'hot' attribute on a label is used to inform the compiler that
- the path following the label is more likely than paths that are not
- so annotated. This attribute is used in cases where
- '__builtin_expect' cannot be used, for instance with computed goto
- or 'asm goto'.
+`hot'
+ The `hot' attribute on a label is used to inform the compiler that
+ the path following the label is more likely than paths that are
+ not so annotated. This attribute is used in cases where
+ `__builtin_expect' cannot be used, for instance with computed goto
+ or `asm goto'.
-'cold'
- The 'cold' attribute on labels is used to inform the compiler that
+`cold'
+ The `cold' attribute on labels is used to inform the compiler that
the path following the label is unlikely to be executed. This
- attribute is used in cases where '__builtin_expect' cannot be used,
- for instance with computed goto or 'asm goto'.
+ attribute is used in cases where `__builtin_expect' cannot be
+ used, for instance with computed goto or `asm goto'.
+

File: gcc.info, Node: Attribute Syntax, Next: Function Prototypes, Prev: Label Attributes, Up: C Extensions
@@ -26797,7 +27006,7 @@ File: gcc.info, Node: Attribute Syntax, Next: Function Prototypes, Prev: Labe
6.33 Attribute Syntax
=====================
-This section describes the syntax with which '__attribute__' may be
+This section describes the syntax with which `__attribute__' may be
used, and the constructs to which attribute specifiers bind, for the C
language. Some details may vary for C++ and Objective-C. Because of
infelicities in the grammar for attributes, some forms described here
@@ -26806,8 +27015,8 @@ may not be successfully parsed in all cases.
There are some problems with the semantics of attributes in C++. For
example, there are no manglings for attributes, although they may affect
code generation, so problems may arise when attributed types are used in
-conjunction with templates or overloading. Similarly, 'typeid' does not
-distinguish between types with different attributes. Support for
+conjunction with templates or overloading. Similarly, `typeid' does
+not distinguish between types with different attributes. Support for
attributes in C++ may be restricted in future to attributes on
declarations only, but not on nested declarators.
@@ -26818,28 +27027,28 @@ for details of the semantics of attributes applying to structure, union
and enumerated types. *Note Label Attributes::, for details of the
semantics of attributes applying to labels.
- An "attribute specifier" is of the form '__attribute__
+ An "attribute specifier" is of the form `__attribute__
((ATTRIBUTE-LIST))'. An "attribute list" is a possibly empty
-comma-separated sequence of "attributes", where each attribute is one of
-the following:
+comma-separated sequence of "attributes", where each attribute is one
+of the following:
* Empty. Empty attributes are ignored.
- * A word (which may be an identifier such as 'unused', or a reserved
- word such as 'const').
+ * A word (which may be an identifier such as `unused', or a reserved
+ word such as `const').
* A word, followed by, in parentheses, parameters for the attribute.
These parameters take one of the following forms:
- * An identifier. For example, 'mode' attributes use this form.
+ * An identifier. For example, `mode' attributes use this form.
* An identifier followed by a comma and a non-empty
- comma-separated list of expressions. For example, 'format'
+ comma-separated list of expressions. For example, `format'
attributes use this form.
* A possibly empty comma-separated list of expressions. For
- example, 'format_arg' attributes use this form with the list
- being a single integer constant expression, and 'alias'
+ example, `format_arg' attributes use this form with the list
+ being a single integer constant expression, and `alias'
attributes use this form with the list being a single string
constant.
@@ -26850,20 +27059,20 @@ Label Attributes
................
In GNU C, an attribute specifier list may appear after the colon
-following a label, other than a 'case' or 'default' label. GNU C++ only
-permits attributes on labels if the attribute specifier is immediately
-followed by a semicolon (i.e., the label applies to an empty statement).
-If the semicolon is missing, C++ label attributes are ambiguous, as it
-is permissible for a declaration, which could begin with an attribute
-list, to be labelled in C++. Declarations cannot be labelled in C90 or
-C99, so the ambiguity does not arise there.
+following a label, other than a `case' or `default' label. GNU C++
+only permits attributes on labels if the attribute specifier is
+immediately followed by a semicolon (i.e., the label applies to an empty
+statement). If the semicolon is missing, C++ label attributes are
+ambiguous, as it is permissible for a declaration, which could begin
+with an attribute list, to be labelled in C++. Declarations cannot be
+labelled in C90 or C99, so the ambiguity does not arise there.
Type Attributes
...............
-An attribute specifier list may appear as part of a 'struct', 'union' or
-'enum' specifier. It may go either immediately after the 'struct',
-'union' or 'enum' keyword, or after the closing brace. The former
+An attribute specifier list may appear as part of a `struct', `union'
+or `enum' specifier. It may go either immediately after the `struct',
+`union' or `enum' keyword, or after the closing brace. The former
syntax is preferred. Where attribute specifiers follow the closing
brace, they are considered to relate to the structure, union or
enumerated type defined, not to any enclosing declaration the type
@@ -26888,20 +27097,21 @@ contain attribute specifiers, whether or not such a list may in that
context contain storage class specifiers. (Some attributes, however,
are essentially in the nature of storage class specifiers, and only make
sense where storage class specifiers may be used; for example,
-'section'.) There is one necessary limitation to this syntax: the first
-old-style parameter declaration in a function definition cannot begin
-with an attribute specifier, because such an attribute applies to the
-function instead by syntax described below (which, however, is not yet
-implemented in this case). In some other cases, attribute specifiers
-are permitted by this grammar but not yet supported by the compiler.
-All attribute specifiers in this place relate to the declaration as a
-whole. In the obsolescent usage where a type of 'int' is implied by the
-absence of type specifiers, such a list of specifiers and qualifiers may
-be an attribute specifier list with no other specifiers or qualifiers.
+`section'.) There is one necessary limitation to this syntax: the
+first old-style parameter declaration in a function definition cannot
+begin with an attribute specifier, because such an attribute applies to
+the function instead by syntax described below (which, however, is not
+yet implemented in this case). In some other cases, attribute
+specifiers are permitted by this grammar but not yet supported by the
+compiler. All attribute specifiers in this place relate to the
+declaration as a whole. In the obsolescent usage where a type of `int'
+is implied by the absence of type specifiers, such a list of specifiers
+and qualifiers may be an attribute specifier list with no other
+specifiers or qualifiers.
At present, the first parameter in a function prototype must have some
type specifier that is not an attribute specifier; this resolves an
-ambiguity in the interpretation of 'void f(int (__attribute__((foo))
+ambiguity in the interpretation of `void f(int (__attribute__((foo))
x))', but is subject to change. At present, if the parentheses of a
function declarator contain only attributes then those attributes are
ignored, rather than yielding an error or warning or implying a single
@@ -26917,22 +27127,22 @@ identifier before whose declarator they appear. For example, in
__attribute__((format(printf, 1, 2))) d1 (const char *, ...),
d2 (void);
-the 'noreturn' attribute applies to all the functions declared; the
-'format' attribute only applies to 'd1'.
+the `noreturn' attribute applies to all the functions declared; the
+`format' attribute only applies to `d1'.
An attribute specifier list may appear immediately before the comma,
-'=' or semicolon terminating the declaration of an identifier other than
-a function definition. Such attribute specifiers apply to the declared
-object or function. Where an assembler name for an object or function
-is specified (*note Asm Labels::), the attribute must follow the 'asm'
-specification.
+`=' or semicolon terminating the declaration of an identifier other
+than a function definition. Such attribute specifiers apply to the
+declared object or function. Where an assembler name for an object or
+function is specified (*note Asm Labels::), the attribute must follow
+the `asm' specification.
An attribute specifier list may, in future, be permitted to appear
after the declarator in a function definition (before any old-style
parameter declarations or the function body).
Attribute specifiers may be mixed with type qualifiers appearing inside
-the '[]' of a parameter array declarator, in the C99 construct by which
+the `[]' of a parameter array declarator, in the C99 construct by which
such qualifiers are applied to the pointer to which the array is
implicitly converted. Such attribute specifiers apply to the pointer,
not to the array, but at present this is not implemented and they are
@@ -26942,27 +27152,27 @@ ignored.
declarator. At present, there are some limitations in this usage: the
attributes correctly apply to the declarator, but for most individual
attributes the semantics this implies are not implemented. When
-attribute specifiers follow the '*' of a pointer declarator, they may be
-mixed with any type qualifiers present. The following describes the
+attribute specifiers follow the `*' of a pointer declarator, they may
+be mixed with any type qualifiers present. The following describes the
formal semantics of this syntax. It makes the most sense if you are
familiar with the formal specification of declarators in the ISO C
standard.
- Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration 'T D1',
-where 'T' contains declaration specifiers that specify a type TYPE (such
-as 'int') and 'D1' is a declarator that contains an identifier IDENT.
-The type specified for IDENT for derived declarators whose type does not
-include an attribute specifier is as in the ISO C standard.
-
- If 'D1' has the form '( ATTRIBUTE-SPECIFIER-LIST D )', and the
-declaration 'T D' specifies the type "DERIVED-DECLARATOR-TYPE-LIST TYPE"
-for IDENT, then 'T D1' specifies the type "DERIVED-DECLARATOR-TYPE-LIST
-ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT.
-
- If 'D1' has the form '* TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST D',
-and the declaration 'T D' specifies the type
-"DERIVED-DECLARATOR-TYPE-LIST TYPE" for IDENT, then 'T D1' specifies the
-type "DERIVED-DECLARATOR-TYPE-LIST
+ Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration `T D1',
+where `T' contains declaration specifiers that specify a type TYPE
+(such as `int') and `D1' is a declarator that contains an identifier
+IDENT. The type specified for IDENT for derived declarators whose type
+does not include an attribute specifier is as in the ISO C standard.
+
+ If `D1' has the form `( ATTRIBUTE-SPECIFIER-LIST D )', and the
+declaration `T D' specifies the type "DERIVED-DECLARATOR-TYPE-LIST
+TYPE" for IDENT, then `T D1' specifies the type
+"DERIVED-DECLARATOR-TYPE-LIST ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT.
+
+ If `D1' has the form `* TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST
+D', and the declaration `T D' specifies the type
+"DERIVED-DECLARATOR-TYPE-LIST TYPE" for IDENT, then `T D1' specifies
+the type "DERIVED-DECLARATOR-TYPE-LIST
TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST pointer to TYPE" for IDENT.
For example,
@@ -26970,13 +27180,13 @@ TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST pointer to TYPE" for IDENT.
void (__attribute__((noreturn)) ****f) (void);
specifies the type "pointer to pointer to pointer to pointer to
-non-returning function returning 'void'". As another example,
+non-returning function returning `void'". As another example,
char *__attribute__((aligned(8))) *f;
-specifies the type "pointer to 8-byte-aligned pointer to 'char'". Note
+specifies the type "pointer to 8-byte-aligned pointer to `char'". Note
again that this does not work with most attributes; for example, the
-usage of 'aligned' and 'noreturn' attributes given above is not yet
+usage of `aligned' and `noreturn' attributes given above is not yet
supported.
For compatibility with existing code written for compiler versions that
@@ -26990,8 +27200,8 @@ the attributes immediately before the identifier declared, such an
attribute applied to a function return type is treated as applying to
the function type, and such an attribute applied to an array element
type is treated as applying to the array type. If an attribute that
-only applies to function types is applied to a pointer-to-function type,
-it is treated as applying to the pointer target type; if such an
+only applies to function types is applied to a pointer-to-function
+type, it is treated as applying to the pointer target type; if such an
attribute is applied to a function return type that is not a
pointer-to-function type, it is treated as applying to the function
type.
@@ -27023,20 +27233,21 @@ old-style non-prototype definition. Consider the following example:
return x == 0;
}
- Suppose the type 'uid_t' happens to be 'short'. ISO C does not allow
+ Suppose the type `uid_t' happens to be `short'. ISO C does not allow
this example, because subword arguments in old-style non-prototype
definitions are promoted. Therefore in this example the function
-definition's argument is really an 'int', which does not match the
-prototype argument type of 'short'.
+definition's argument is really an `int', which does not match the
+prototype argument type of `short'.
This restriction of ISO C makes it hard to write code that is portable
-to traditional C compilers, because the programmer does not know whether
-the 'uid_t' type is 'short', 'int', or 'long'. Therefore, in cases like
-these GNU C allows a prototype to override a later old-style definition.
-More precisely, in GNU C, a function prototype argument type overrides
-the argument type specified by a later old-style definition if the
-former type is the same as the latter type before promotion. Thus in
-GNU C the above example is equivalent to the following:
+to traditional C compilers, because the programmer does not know
+whether the `uid_t' type is `short', `int', or `long'. Therefore, in
+cases like these GNU C allows a prototype to override a later old-style
+definition. More precisely, in GNU C, a function prototype argument
+type overrides the argument type specified by a later old-style
+definition if the former type is the same as the latter type before
+promotion. Thus in GNU C the above example is equivalent to the
+following:
int isroot (uid_t);
@@ -27055,12 +27266,12 @@ File: gcc.info, Node: C++ Comments, Next: Dollar Signs, Prev: Function Protot
6.35 C++ Style Comments
=======================
-In GNU C, you may use C++ style comments, which start with '//' and
+In GNU C, you may use C++ style comments, which start with `//' and
continue until the end of the line. Many other C implementations allow
such comments, and they are included in the 1999 C standard. However,
-C++ style comments are not recognized if you specify an '-std' option
-specifying a version of ISO C before C99, or '-ansi' (equivalent to
-'-std=c90').
+C++ style comments are not recognized if you specify an `-std' option
+specifying a version of ISO C before C99, or `-ansi' (equivalent to
+`-std=c90').

File: gcc.info, Node: Dollar Signs, Next: Character Escapes, Prev: C++ Comments, Up: C Extensions
@@ -27079,8 +27290,8 @@ File: gcc.info, Node: Character Escapes, Next: Variable Attributes, Prev: Dol
6.37 The Character <ESC> in Constants
=====================================
-You can use the sequence '\e' in a string or character constant to stand
-for the ASCII character <ESC>.
+You can use the sequence `\e' in a string or character constant to
+stand for the ASCII character <ESC>.

File: gcc.info, Node: Variable Attributes, Next: Type Attributes, Prev: Character Escapes, Up: C Extensions
@@ -27088,42 +27299,42 @@ File: gcc.info, Node: Variable Attributes, Next: Type Attributes, Prev: Chara
6.38 Specifying Attributes of Variables
=======================================
-The keyword '__attribute__' allows you to specify special attributes of
-variables or structure fields. This keyword is followed by an attribute
-specification inside double parentheses. Some attributes are currently
-defined generically for variables. Other attributes are defined for
-variables on particular target systems. Other attributes are available
-for functions (*note Function Attributes::), labels (*note Label
-Attributes::) and for types (*note Type Attributes::). Other front ends
-might define more attributes (*note Extensions to the C++ Language: C++
-Extensions.).
-
- You may also specify attributes with '__' preceding and following each
+The keyword `__attribute__' allows you to specify special attributes of
+variables or structure fields. This keyword is followed by an
+attribute specification inside double parentheses. Some attributes are
+currently defined generically for variables. Other attributes are
+defined for variables on particular target systems. Other attributes
+are available for functions (*note Function Attributes::), labels
+(*note Label Attributes::) and for types (*note Type Attributes::).
+Other front ends might define more attributes (*note Extensions to the
+C++ Language: C++ Extensions.).
+
+ You may also specify attributes with `__' preceding and following each
keyword. This allows you to use them in header files without being
-concerned about a possible macro of the same name. For example, you may
-use '__aligned__' instead of 'aligned'.
+concerned about a possible macro of the same name. For example, you
+may use `__aligned__' instead of `aligned'.
*Note Attribute Syntax::, for details of the exact syntax for using
attributes.
-'aligned (ALIGNMENT)'
+`aligned (ALIGNMENT)'
This attribute specifies a minimum alignment for the variable or
structure field, measured in bytes. For example, the declaration:
int x __attribute__ ((aligned (16))) = 0;
- causes the compiler to allocate the global variable 'x' on a
+ causes the compiler to allocate the global variable `x' on a
16-byte boundary. On a 68040, this could be used in conjunction
- with an 'asm' expression to access the 'move16' instruction which
+ with an `asm' expression to access the `move16' instruction which
requires 16-byte aligned operands.
You can also specify the alignment of structure fields. For
- example, to create a double-word aligned 'int' pair, you could
+ example, to create a double-word aligned `int' pair, you could
write:
struct foo { int x[2] __attribute__ ((aligned (8))); };
- This is an alternative to creating a union with a 'double' member,
+ This is an alternative to creating a union with a `double' member,
which forces the union to be double-word aligned.
As in the preceding examples, you can explicitly specify the
@@ -27136,7 +27347,7 @@ attributes.
supports vector operations. The default alignment is fixed for a
particular target ABI.
- GCC also provides a target specific macro '__BIGGEST_ALIGNMENT__',
+ GCC also provides a target specific macro `__BIGGEST_ALIGNMENT__',
which is the largest alignment ever used for any data type on the
target machine you are compiling for. For example, you could
write:
@@ -27144,59 +27355,60 @@ attributes.
short array[3] __attribute__ ((aligned (__BIGGEST_ALIGNMENT__)));
The compiler automatically sets the alignment for the declared
- variable or field to '__BIGGEST_ALIGNMENT__'. Doing this can often
- make copy operations more efficient, because the compiler can use
- whatever instructions copy the biggest chunks of memory when
+ variable or field to `__BIGGEST_ALIGNMENT__'. Doing this can
+ often make copy operations more efficient, because the compiler can
+ use whatever instructions copy the biggest chunks of memory when
performing copies to or from the variables or fields that you have
- aligned this way. Note that the value of '__BIGGEST_ALIGNMENT__'
+ aligned this way. Note that the value of `__BIGGEST_ALIGNMENT__'
may change depending on command-line options.
- When used on a struct, or struct member, the 'aligned' attribute
+ When used on a struct, or struct member, the `aligned' attribute
can only increase the alignment; in order to decrease it, the
- 'packed' attribute must be specified as well. When used as part of
- a typedef, the 'aligned' attribute can both increase and decrease
- alignment, and specifying the 'packed' attribute generates a
- warning.
+ `packed' attribute must be specified as well. When used as part
+ of a typedef, the `aligned' attribute can both increase and
+ decrease alignment, and specifying the `packed' attribute
+ generates a warning.
- Note that the effectiveness of 'aligned' attributes may be limited
+ Note that the effectiveness of `aligned' attributes may be limited
by inherent limitations in your linker. On many systems, the
linker is only able to arrange for variables to be aligned up to a
certain maximum alignment. (For some linkers, the maximum
supported alignment may be very very small.) If your linker is
only able to align variables up to a maximum of 8-byte alignment,
- then specifying 'aligned(16)' in an '__attribute__' still only
+ then specifying `aligned(16)' in an `__attribute__' still only
provides you with 8-byte alignment. See your linker documentation
for further information.
- The 'aligned' attribute can also be used for functions (*note
+ The `aligned' attribute can also be used for functions (*note
Function Attributes::.)
-'cleanup (CLEANUP_FUNCTION)'
- The 'cleanup' attribute runs a function when the variable goes out
+`cleanup (CLEANUP_FUNCTION)'
+ The `cleanup' attribute runs a function when the variable goes out
of scope. This attribute can only be applied to auto function
scope variables; it may not be applied to parameters or variables
with static storage duration. The function must take one
parameter, a pointer to a type compatible with the variable. The
return value of the function (if any) is ignored.
- If '-fexceptions' is enabled, then CLEANUP_FUNCTION is run during
+ If `-fexceptions' is enabled, then CLEANUP_FUNCTION is run during
the stack unwinding that happens during the processing of the
- exception. Note that the 'cleanup' attribute does not allow the
- exception to be caught, only to perform an action. It is undefined
- what happens if CLEANUP_FUNCTION does not return normally.
-
-'common'
-'nocommon'
- The 'common' attribute requests GCC to place a variable in "common"
- storage. The 'nocommon' attribute requests the opposite--to
- allocate space for it directly.
-
- These attributes override the default chosen by the '-fno-common'
- and '-fcommon' flags respectively.
-
-'deprecated'
-'deprecated (MSG)'
- The 'deprecated' attribute results in a warning if the variable is
+ exception. Note that the `cleanup' attribute does not allow the
+ exception to be caught, only to perform an action. It is
+ undefined what happens if CLEANUP_FUNCTION does not return
+ normally.
+
+`common'
+`nocommon'
+ The `common' attribute requests GCC to place a variable in
+ "common" storage. The `nocommon' attribute requests the
+ opposite--to allocate space for it directly.
+
+ These attributes override the default chosen by the `-fno-common'
+ and `-fcommon' flags respectively.
+
+`deprecated'
+`deprecated (MSG)'
+ The `deprecated' attribute results in a warning if the variable is
used anywhere in the source file. This is useful when identifying
variables that are expected to be removed in a future version of a
program. The warning also includes the location of the declaration
@@ -27212,28 +27424,28 @@ attributes.
argument, which must be a string, is printed in the warning if
present.
- The 'deprecated' attribute can also be used for functions and types
- (*note Function Attributes::, *note Type Attributes::.)
+ The `deprecated' attribute can also be used for functions and
+ types (*note Function Attributes::, *note Type Attributes::.)
-'mode (MODE)'
+`mode (MODE)'
This attribute specifies the data type for the
declaration--whichever type corresponds to the mode MODE. This in
- effect lets you request an integer or floating-point type according
- to its width.
+ effect lets you request an integer or floating-point type
+ according to its width.
- You may also specify a mode of 'byte' or '__byte__' to indicate the
- mode corresponding to a one-byte integer, 'word' or '__word__' for
- the mode of a one-word integer, and 'pointer' or '__pointer__' for
- the mode used to represent pointers.
+ You may also specify a mode of `byte' or `__byte__' to indicate
+ the mode corresponding to a one-byte integer, `word' or `__word__'
+ for the mode of a one-word integer, and `pointer' or `__pointer__'
+ for the mode used to represent pointers.
-'packed'
- The 'packed' attribute specifies that a variable or structure field
+`packed'
+ The `packed' attribute specifies that a variable or structure field
should have the smallest possible alignment--one byte for a
variable, and one bit for a field, unless you specify a larger
- value with the 'aligned' attribute.
+ value with the `aligned' attribute.
- Here is a structure in which the field 'x' is packed, so that it
- immediately follows 'a':
+ Here is a structure in which the field `x' is packed, so that it
+ immediately follows `a':
struct foo
{
@@ -27241,18 +27453,18 @@ attributes.
int x[2] __attribute__ ((packed));
};
- _Note:_ The 4.1, 4.2 and 4.3 series of GCC ignore the 'packed'
- attribute on bit-fields of type 'char'. This has been fixed in GCC
- 4.4 but the change can lead to differences in the structure layout.
- See the documentation of '-Wpacked-bitfield-compat' for more
- information.
+ _Note:_ The 4.1, 4.2 and 4.3 series of GCC ignore the `packed'
+ attribute on bit-fields of type `char'. This has been fixed in
+ GCC 4.4 but the change can lead to differences in the structure
+ layout. See the documentation of `-Wpacked-bitfield-compat' for
+ more information.
-'section ("SECTION-NAME")'
+`section ("SECTION-NAME")'
Normally, the compiler places the objects it generates in sections
- like 'data' and 'bss'. Sometimes, however, you need additional
+ like `data' and `bss'. Sometimes, however, you need additional
sections, or you need certain particular variables to appear in
special sections, for example to map to special hardware. The
- 'section' attribute specifies that a variable (or function) lives
+ `section' attribute specifies that a variable (or function) lives
in a particular section. For example, this small program uses
several specific section names:
@@ -27274,30 +27486,30 @@ attributes.
init_duart (&b);
}
- Use the 'section' attribute with _global_ variables and not _local_
- variables, as shown in the example.
+ Use the `section' attribute with _global_ variables and not
+ _local_ variables, as shown in the example.
- You may use the 'section' attribute with initialized or
+ You may use the `section' attribute with initialized or
uninitialized global variables but the linker requires each object
be defined once, with the exception that uninitialized variables
- tentatively go in the 'common' (or 'bss') section and can be
- multiply "defined". Using the 'section' attribute changes what
- section the variable goes into and may cause the linker to issue an
- error if an uninitialized variable has multiple definitions. You
- can force a variable to be initialized with the '-fno-common' flag
- or the 'nocommon' attribute.
+ tentatively go in the `common' (or `bss') section and can be
+ multiply "defined". Using the `section' attribute changes what
+ section the variable goes into and may cause the linker to issue
+ an error if an uninitialized variable has multiple definitions.
+ You can force a variable to be initialized with the `-fno-common'
+ flag or the `nocommon' attribute.
Some file formats do not support arbitrary sections so the
- 'section' attribute is not available on all platforms. If you need
- to map the entire contents of a module to a particular section,
- consider using the facilities of the linker instead.
+ `section' attribute is not available on all platforms. If you
+ need to map the entire contents of a module to a particular
+ section, consider using the facilities of the linker instead.
-'shared'
+`shared'
On Microsoft Windows, in addition to putting variable definitions
in a named section, the section can also be shared among all
running copies of an executable or DLL. For example, this small
program defines shared data by putting it in a named section
- 'shared' and marking the section shareable:
+ `shared' and marking the section shareable:
int foo __attribute__((section ("shared"), shared)) = 0;
@@ -27309,27 +27521,28 @@ attributes.
return 0;
}
- You may only use the 'shared' attribute along with 'section'
- attribute with a fully-initialized global definition because of the
- way linkers work. See 'section' attribute for more information.
+ You may only use the `shared' attribute along with `section'
+ attribute with a fully-initialized global definition because of
+ the way linkers work. See `section' attribute for more
+ information.
- The 'shared' attribute is only available on Microsoft Windows.
+ The `shared' attribute is only available on Microsoft Windows.
-'tls_model ("TLS_MODEL")'
- The 'tls_model' attribute sets thread-local storage model (*note
- Thread-Local::) of a particular '__thread' variable, overriding
- '-ftls-model=' command-line switch on a per-variable basis. The
- TLS_MODEL argument should be one of 'global-dynamic',
- 'local-dynamic', 'initial-exec' or 'local-exec'.
+`tls_model ("TLS_MODEL")'
+ The `tls_model' attribute sets thread-local storage model (*note
+ Thread-Local::) of a particular `__thread' variable, overriding
+ `-ftls-model=' command-line switch on a per-variable basis. The
+ TLS_MODEL argument should be one of `global-dynamic',
+ `local-dynamic', `initial-exec' or `local-exec'.
Not all targets support this attribute.
-'unused'
+`unused'
This attribute, attached to a variable, means that the variable is
meant to be possibly unused. GCC does not produce a warning for
this variable.
-'used'
+`used'
This attribute, attached to a variable with static storage, means
that the variable must be emitted even if it appears that the
variable is not referenced.
@@ -27338,31 +27551,32 @@ attributes.
attribute also means that the member is instantiated if the class
itself is instantiated.
-'vector_size (BYTES)'
- This attribute specifies the vector size for the variable, measured
- in bytes. For example, the declaration:
+`vector_size (BYTES)'
+ This attribute specifies the vector size for the variable,
+ measured in bytes. For example, the declaration:
int foo __attribute__ ((vector_size (16)));
- causes the compiler to set the mode for 'foo', to be 16 bytes,
- divided into 'int' sized units. Assuming a 32-bit int (a vector of
- 4 units of 4 bytes), the corresponding mode of 'foo' is V4SI.
+ causes the compiler to set the mode for `foo', to be 16 bytes,
+ divided into `int' sized units. Assuming a 32-bit int (a vector of
+ 4 units of 4 bytes), the corresponding mode of `foo' is V4SI.
This attribute is only applicable to integral and float scalars,
although arrays, pointers, and function return values are allowed
in conjunction with this construct.
- Aggregates with this attribute are invalid, even if they are of the
- same size as a corresponding scalar. For example, the declaration:
+ Aggregates with this attribute are invalid, even if they are of
+ the same size as a corresponding scalar. For example, the
+ declaration:
struct S { int a; };
struct S __attribute__ ((vector_size (16))) foo;
is invalid even if the size of the structure is the same as the
- size of the 'int'.
+ size of the `int'.
-'selectany'
- The 'selectany' attribute causes an initialized global variable to
+`selectany'
+ The `selectany' attribute causes an initialized global variable to
have link-once semantics. When multiple definitions of the
variable are encountered by the linker, the first is selected and
the remainder are discarded. Following usage by the Microsoft
@@ -27377,38 +27591,39 @@ attributes.
constructor and destructor are protected by a link-once guard
variable.
- The 'selectany' attribute is only available on Microsoft Windows
- targets. You can use '__declspec (selectany)' as a synonym for
- '__attribute__ ((selectany))' for compatibility with other
+ The `selectany' attribute is only available on Microsoft Windows
+ targets. You can use `__declspec (selectany)' as a synonym for
+ `__attribute__ ((selectany))' for compatibility with other
compilers.
-'weak'
- The 'weak' attribute is described in *note Function Attributes::.
+`weak'
+ The `weak' attribute is described in *note Function Attributes::.
-'dllimport'
- The 'dllimport' attribute is described in *note Function
+`dllimport'
+ The `dllimport' attribute is described in *note Function
Attributes::.
-'dllexport'
- The 'dllexport' attribute is described in *note Function
+`dllexport'
+ The `dllexport' attribute is described in *note Function
Attributes::.
+
6.38.1 AVR Variable Attributes
------------------------------
-'progmem'
- The 'progmem' attribute is used on the AVR to place read-only data
- in the non-volatile program memory (flash). The 'progmem'
+`progmem'
+ The `progmem' attribute is used on the AVR to place read-only data
+ in the non-volatile program memory (flash). The `progmem'
attribute accomplishes this by putting respective variables into a
- section whose name starts with '.progmem'.
+ section whose name starts with `.progmem'.
- This attribute works similar to the 'section' attribute but adds
- additional checking. Notice that just like the 'section'
- attribute, 'progmem' affects the location of the data but not how
+ This attribute works similar to the `section' attribute but adds
+ additional checking. Notice that just like the `section'
+ attribute, `progmem' affects the location of the data but not how
this data is accessed.
- In order to read data located with the 'progmem' attribute (inline)
- assembler must be used.
+ In order to read data located with the `progmem' attribute
+ (inline) assembler must be used.
/* Use custom macros from AVR-LibC (http://nongnu.org/avr-libc/user-manual/) */
#include <avr/pgmspace.h>
@@ -27427,12 +27642,12 @@ attributes.
See also the *note AVR Named Address Spaces:: section for an
alternate way to locate and access data in flash memory.
-'io'
-'io (ADDR)'
- Variables with the 'io' attribute are used to address memory-mapped
- peripherals in the io address range. If an address is specified,
- the variable is assigned that address, and the value is interpreted
- as an address in the data address space. Example:
+`io'
+`io (ADDR)'
+ Variables with the `io' attribute are used to address
+ memory-mapped peripherals in the io address range. If an address
+ is specified, the variable is assigned that address, and the value
+ is interpreted as an address in the data address space. Example:
volatile int porta __attribute__((io (0x22)));
@@ -27445,179 +27660,183 @@ attributes.
extern volatile int porta __attribute__((io));
-'io_low'
-'io_low (ADDR)'
- This is like the 'io' attribute, but additionally it informs the
+`io_low'
+`io_low (ADDR)'
+ This is like the `io' attribute, but additionally it informs the
compiler that the object lies in the lower half of the I/O area,
- allowing the use of 'cbi', 'sbi', 'sbic' and 'sbis' instructions.
+ allowing the use of `cbi', `sbi', `sbic' and `sbis' instructions.
-'address'
-'address (ADDR)'
- Variables with the 'address' attribute are used to address
+`address'
+`address (ADDR)'
+ Variables with the `address' attribute are used to address
memory-mapped peripherals that may lie outside the io address
range.
volatile int porta __attribute__((address (0x600)));
+
6.38.2 Blackfin Variable Attributes
-----------------------------------
Three attributes are currently defined for the Blackfin.
-'l1_data'
-'l1_data_A'
-'l1_data_B'
+`l1_data'
+`l1_data_A'
+`l1_data_B'
Use these attributes on the Blackfin to place the variable into L1
- Data SRAM. Variables with 'l1_data' attribute are put into the
- specific section named '.l1.data'. Those with 'l1_data_A'
- attribute are put into the specific section named '.l1.data.A'.
- Those with 'l1_data_B' attribute are put into the specific section
- named '.l1.data.B'.
+ Data SRAM. Variables with `l1_data' attribute are put into the
+ specific section named `.l1.data'. Those with `l1_data_A'
+ attribute are put into the specific section named `.l1.data.A'.
+ Those with `l1_data_B' attribute are put into the specific section
+ named `.l1.data.B'.
-'l2'
+`l2'
Use this attribute on the Blackfin to place the variable into L2
- SRAM. Variables with 'l2' attribute are put into the specific
- section named '.l2.data'.
+ SRAM. Variables with `l2' attribute are put into the specific
+ section named `.l2.data'.
6.38.3 H8/300 Variable Attributes
---------------------------------
These variable attributes are available for H8/300 targets:
-'eightbit_data'
- Use this attribute on the H8/300, H8/300H, and H8S to indicate that
- the specified variable should be placed into the eight-bit data
- section. The compiler generates more efficient code for certain
- operations on data in the eight-bit data area. Note the eight-bit
- data area is limited to 256 bytes of data.
+`eightbit_data'
+ Use this attribute on the H8/300, H8/300H, and H8S to indicate
+ that the specified variable should be placed into the eight-bit
+ data section. The compiler generates more efficient code for
+ certain operations on data in the eight-bit data area. Note the
+ eight-bit data area is limited to 256 bytes of data.
You must use GAS and GLD from GNU binutils version 2.7 or later for
this attribute to work correctly.
-'tiny_data'
+`tiny_data'
Use this attribute on the H8/300H and H8S to indicate that the
specified variable should be placed into the tiny data section.
The compiler generates more efficient code for loads and stores on
data in the tiny data section. Note the tiny data area is limited
to slightly under 32KB of data.
+
6.38.4 IA-64 Variable Attributes
--------------------------------
The IA-64 back end supports the following variable attribute:
-'model (MODEL-NAME)'
-
+`model (MODEL-NAME)'
On IA-64, use this attribute to set the addressability of an
object. At present, the only supported identifier for MODEL-NAME
- is 'small', indicating addressability via "small" (22-bit)
- addresses (so that their addresses can be loaded with the 'addl'
+ is `small', indicating addressability via "small" (22-bit)
+ addresses (so that their addresses can be loaded with the `addl'
instruction). Caveat: such addressing is by definition not
position independent and hence this attribute must not be used for
objects defined by shared libraries.
+
6.38.5 M32R/D Variable Attributes
---------------------------------
One attribute is currently defined for the M32R/D.
-'model (MODEL-NAME)'
+`model (MODEL-NAME)'
Use this attribute on the M32R/D to set the addressability of an
- object. The identifier MODEL-NAME is one of 'small', 'medium', or
- 'large', representing each of the code models.
+ object. The identifier MODEL-NAME is one of `small', `medium', or
+ `large', representing each of the code models.
Small model objects live in the lower 16MB of memory (so that their
- addresses can be loaded with the 'ld24' instruction).
+ addresses can be loaded with the `ld24' instruction).
Medium and large model objects may live anywhere in the 32-bit
- address space (the compiler generates 'seth/add3' instructions to
+ address space (the compiler generates `seth/add3' instructions to
load their addresses).
6.38.6 MeP Variable Attributes
------------------------------
-The MeP target has a number of addressing modes and busses. The 'near'
+The MeP target has a number of addressing modes and busses. The `near'
space spans the standard memory space's first 16 megabytes (24 bits).
-The 'far' space spans the entire 32-bit memory space. The 'based' space
-is a 128-byte region in the memory space that is addressed relative to
-the '$tp' register. The 'tiny' space is a 65536-byte region relative to
-the '$gp' register. In addition to these memory regions, the MeP target
-has a separate 16-bit control bus which is specified with 'cb'
-attributes.
-
-'based'
- Any variable with the 'based' attribute is assigned to the '.based'
- section, and is accessed with relative to the '$tp' register.
+The `far' space spans the entire 32-bit memory space. The `based'
+space is a 128-byte region in the memory space that is addressed
+relative to the `$tp' register. The `tiny' space is a 65536-byte
+region relative to the `$gp' register. In addition to these memory
+regions, the MeP target has a separate 16-bit control bus which is
+specified with `cb' attributes.
+
+`based'
+ Any variable with the `based' attribute is assigned to the
+ `.based' section, and is accessed with relative to the `$tp'
+ register.
-'tiny'
- Likewise, the 'tiny' attribute assigned variables to the '.tiny'
- section, relative to the '$gp' register.
+`tiny'
+ Likewise, the `tiny' attribute assigned variables to the `.tiny'
+ section, relative to the `$gp' register.
-'near'
- Variables with the 'near' attribute are assumed to have addresses
+`near'
+ Variables with the `near' attribute are assumed to have addresses
that fit in a 24-bit addressing mode. This is the default for
- large variables ('-mtiny=4' is the default) but this attribute can
- override '-mtiny=' for small variables, or override '-ml'.
+ large variables (`-mtiny=4' is the default) but this attribute can
+ override `-mtiny=' for small variables, or override `-ml'.
-'far'
- Variables with the 'far' attribute are addressed using a full
+`far'
+ Variables with the `far' attribute are addressed using a full
32-bit address. Since this covers the entire memory space, this
allows modules to make no assumptions about where variables might
be stored.
-'io'
-'io (ADDR)'
- Variables with the 'io' attribute are used to address memory-mapped
- peripherals. If an address is specified, the variable is assigned
- that address, else it is not assigned an address (it is assumed
- some other module assigns an address). Example:
+`io'
+`io (ADDR)'
+ Variables with the `io' attribute are used to address
+ memory-mapped peripherals. If an address is specified, the
+ variable is assigned that address, else it is not assigned an
+ address (it is assumed some other module assigns an address).
+ Example:
int timer_count __attribute__((io(0x123)));
-'cb'
-'cb (ADDR)'
- Variables with the 'cb' attribute are used to access the control
- bus, using special instructions. 'addr' indicates the control bus
+`cb'
+`cb (ADDR)'
+ Variables with the `cb' attribute are used to access the control
+ bus, using special instructions. `addr' indicates the control bus
address. Example:
int cpu_clock __attribute__((cb(0x123)));
+
6.38.7 PowerPC Variable Attributes
----------------------------------
Three attributes currently are defined for PowerPC configurations:
-'altivec', 'ms_struct' and 'gcc_struct'.
+`altivec', `ms_struct' and `gcc_struct'.
For full documentation of the struct attributes please see the
documentation in *note x86 Variable Attributes::.
- For documentation of 'altivec' attribute please see the documentation
+ For documentation of `altivec' attribute please see the documentation
in *note PowerPC Type Attributes::.
6.38.8 SPU Variable Attributes
------------------------------
-The SPU supports the 'spu_vector' attribute for variables. For
+The SPU supports the `spu_vector' attribute for variables. For
documentation of this attribute please see the documentation in *note
SPU Type Attributes::.
6.38.9 x86 Variable Attributes
------------------------------
-Two attributes are currently defined for x86 configurations: 'ms_struct'
-and 'gcc_struct'.
-
-'ms_struct'
-'gcc_struct'
+Two attributes are currently defined for x86 configurations:
+`ms_struct' and `gcc_struct'.
- If 'packed' is used on a structure, or if bit-fields are used, it
+`ms_struct'
+`gcc_struct'
+ If `packed' is used on a structure, or if bit-fields are used, it
may be that the Microsoft ABI lays out the structure differently
than the way GCC normally does. Particularly when moving packed
data between functions compiled with GCC and the native Microsoft
- compiler (either via function call or as data in a file), it may be
- necessary to access either format.
+ compiler (either via function call or as data in a file), it may
+ be necessary to access either format.
- Currently '-m[no-]ms-bitfields' is provided for the Microsoft
+ Currently `-m[no-]ms-bitfields' is provided for the Microsoft
Windows x86 compilers to match the native Microsoft compiler.
The Microsoft structure layout algorithm is fairly simple with the
@@ -27629,22 +27848,22 @@ and 'gcc_struct'.
which they are declared: the first member has the lowest
memory address and the last member the highest.
- 2. Every data object has an alignment requirement. The alignment
- requirement for all data except structures, unions, and arrays
- is either the size of the object or the current packing size
- (specified with either the 'aligned' attribute or the 'pack'
- pragma), whichever is less. For structures, unions, and
- arrays, the alignment requirement is the largest alignment
- requirement of its members. Every object is allocated an
- offset so that:
+ 2. Every data object has an alignment requirement. The
+ alignment requirement for all data except structures, unions,
+ and arrays is either the size of the object or the current
+ packing size (specified with either the `aligned' attribute
+ or the `pack' pragma), whichever is less. For structures,
+ unions, and arrays, the alignment requirement is the largest
+ alignment requirement of its members. Every object is
+ allocated an offset so that:
offset % alignment_requirement == 0
- 3. Adjacent bit-fields are packed into the same 1-, 2-, or 4-byte
- allocation unit if the integral types are the same size and if
- the next bit-field fits into the current allocation unit
- without crossing the boundary imposed by the common alignment
- requirements of the bit-fields.
+ 3. Adjacent bit-fields are packed into the same 1-, 2-, or
+ 4-byte allocation unit if the integral types are the same
+ size and if the next bit-field fits into the current
+ allocation unit without crossing the boundary imposed by the
+ common alignment requirements of the bit-fields.
MSVC interprets zero-length bit-fields in the following ways:
@@ -27660,13 +27879,13 @@ and 'gcc_struct'.
unsigned long bf_2 : 12;
} t1;
- The size of 't1' is 8 bytes with the zero-length bit-field.
- If the zero-length bit-field were removed, 't1''s size would
+ The size of `t1' is 8 bytes with the zero-length bit-field.
+ If the zero-length bit-field were removed, `t1''s size would
be 4 bytes.
2. If a zero-length bit-field is inserted after a bit-field,
- 'foo', and the alignment of the zero-length bit-field is
- greater than the member that follows it, 'bar', 'bar' is
+ `foo', and the alignment of the zero-length bit-field is
+ greater than the member that follows it, `bar', `bar' is
aligned as the type of the zero-length bit-field.
For example:
@@ -27685,9 +27904,9 @@ and 'gcc_struct'.
double bar;
} t3;
- For 't2', 'bar' is placed at offset 2, rather than offset 1.
- Accordingly, the size of 't2' is 4. For 't3', the zero-length
- bit-field does not affect the alignment of 'bar' or, as a
+ For `t2', `bar' is placed at offset 2, rather than offset 1.
+ Accordingly, the size of `t2' is 4. For `t3', the zero-length
+ bit-field does not affect the alignment of `bar' or, as a
result, the size of the structure.
Taking this into account, it is important to note the
@@ -27695,7 +27914,7 @@ and 'gcc_struct'.
1. If a zero-length bit-field follows a normal bit-field,
the type of the zero-length bit-field may affect the
- alignment of the structure as whole. For example, 't2'
+ alignment of the structure as whole. For example, `t2'
has a size of 4 bytes, since the zero-length bit-field
follows a normal bit-field, and is of type short.
@@ -27709,7 +27928,7 @@ and 'gcc_struct'.
long : 0;
} t4;
- Here, 't4' takes up 4 bytes.
+ Here, `t4' takes up 4 bytes.
3. Zero-length bit-fields following non-bit-field members are
ignored:
@@ -27721,20 +27940,21 @@ and 'gcc_struct'.
char bar;
} t5;
- Here, 't5' takes up 2 bytes.
+ Here, `t5' takes up 2 bytes.
6.38.10 Xstormy16 Variable Attributes
-------------------------------------
One attribute is currently defined for xstormy16 configurations:
-'below100'.
-
-'below100'
+`below100'.
- If a variable has the 'below100' attribute ('BELOW100' is allowed
+`below100'
+ If a variable has the `below100' attribute (`BELOW100' is allowed
also), GCC places the variable in the first 0x100 bytes of memory
- and use special opcodes to access it. Such variables are placed in
- either the '.bss_below100' section or the '.data_below100' section.
+ and use special opcodes to access it. Such variables are placed
+ in either the `.bss_below100' section or the `.data_below100'
+ section.
+

File: gcc.info, Node: Type Attributes, Next: Alignment, Prev: Variable Attributes, Up: C Extensions
@@ -27742,22 +27962,22 @@ File: gcc.info, Node: Type Attributes, Next: Alignment, Prev: Variable Attrib
6.39 Specifying Attributes of Types
===================================
-The keyword '__attribute__' allows you to specify special attributes of
-'struct' and 'union' types when you define such types. This keyword is
-followed by an attribute specification inside double parentheses. Eight
-attributes are currently defined for types: 'aligned', 'packed',
-'transparent_union', 'unused', 'deprecated', 'visibility', 'may_alias'
-and 'bnd_variable_size'. Other attributes are defined for functions
-(*note Function Attributes::), labels (*note Label Attributes::) and for
-variables (*note Variable Attributes::).
+The keyword `__attribute__' allows you to specify special attributes of
+`struct' and `union' types when you define such types. This keyword is
+followed by an attribute specification inside double parentheses.
+Eight attributes are currently defined for types: `aligned', `packed',
+`transparent_union', `unused', `deprecated', `visibility', `may_alias'
+and `bnd_variable_size'. Other attributes are defined for functions
+(*note Function Attributes::), labels (*note Label Attributes::) and
+for variables (*note Variable Attributes::).
- You may also specify any one of these attributes with '__' preceding
+ You may also specify any one of these attributes with `__' preceding
and following its keyword. This allows you to use these attributes in
header files without being concerned about a possible macro of the same
-name. For example, you may use '__aligned__' instead of 'aligned'.
+name. For example, you may use `__aligned__' instead of `aligned'.
You may specify type attributes in an enum, struct or union type
-declaration or definition, or for other types in a 'typedef'
+declaration or definition, or for other types in a `typedef'
declaration.
For an enum, struct or union type, you may specify attributes either
@@ -27768,7 +27988,7 @@ preferred.
*Note Attribute Syntax::, for details of the exact syntax for using
attributes.
-'aligned (ALIGNMENT)'
+`aligned (ALIGNMENT)'
This attribute specifies a minimum alignment (in bytes) for
variables of the specified type. For example, the declarations:
@@ -27776,89 +27996,89 @@ attributes.
typedef int more_aligned_int __attribute__ ((aligned (8)));
force the compiler to ensure (as far as it can) that each variable
- whose type is 'struct S' or 'more_aligned_int' is allocated and
+ whose type is `struct S' or `more_aligned_int' is allocated and
aligned _at least_ on a 8-byte boundary. On a SPARC, having all
- variables of type 'struct S' aligned to 8-byte boundaries allows
- the compiler to use the 'ldd' and 'std' (doubleword load and store)
- instructions when copying one variable of type 'struct S' to
+ variables of type `struct S' aligned to 8-byte boundaries allows
+ the compiler to use the `ldd' and `std' (doubleword load and
+ store) instructions when copying one variable of type `struct S' to
another, thus improving run-time efficiency.
- Note that the alignment of any given 'struct' or 'union' type is
+ Note that the alignment of any given `struct' or `union' type is
required by the ISO C standard to be at least a perfect multiple of
the lowest common multiple of the alignments of all of the members
- of the 'struct' or 'union' in question. This means that you _can_
- effectively adjust the alignment of a 'struct' or 'union' type by
- attaching an 'aligned' attribute to any one of the members of such
- a type, but the notation illustrated in the example above is a more
- obvious, intuitive, and readable way to request the compiler to
- adjust the alignment of an entire 'struct' or 'union' type.
+ of the `struct' or `union' in question. This means that you _can_
+ effectively adjust the alignment of a `struct' or `union' type by
+ attaching an `aligned' attribute to any one of the members of such
+ a type, but the notation illustrated in the example above is a
+ more obvious, intuitive, and readable way to request the compiler
+ to adjust the alignment of an entire `struct' or `union' type.
As in the preceding example, you can explicitly specify the
alignment (in bytes) that you wish the compiler to use for a given
- 'struct' or 'union' type. Alternatively, you can leave out the
+ `struct' or `union' type. Alternatively, you can leave out the
alignment factor and just ask the compiler to align a type to the
maximum useful alignment for the target machine you are compiling
for. For example, you could write:
struct S { short f[3]; } __attribute__ ((aligned));
- Whenever you leave out the alignment factor in an 'aligned'
+ Whenever you leave out the alignment factor in an `aligned'
attribute specification, the compiler automatically sets the
alignment for the type to the largest alignment that is ever used
for any data type on the target machine you are compiling for.
Doing this can often make copy operations more efficient, because
the compiler can use whatever instructions copy the biggest chunks
- of memory when performing copies to or from the variables that have
- types that you have aligned this way.
+ of memory when performing copies to or from the variables that
+ have types that you have aligned this way.
- In the example above, if the size of each 'short' is 2 bytes, then
- the size of the entire 'struct S' type is 6 bytes. The smallest
+ In the example above, if the size of each `short' is 2 bytes, then
+ the size of the entire `struct S' type is 6 bytes. The smallest
power of two that is greater than or equal to that is 8, so the
- compiler sets the alignment for the entire 'struct S' type to 8
+ compiler sets the alignment for the entire `struct S' type to 8
bytes.
Note that although you can ask the compiler to select a
time-efficient alignment for a given type and then declare only
- individual stand-alone objects of that type, the compiler's ability
- to select a time-efficient alignment is primarily useful only when
- you plan to create arrays of variables having the relevant
- (efficiently aligned) type. If you declare or use arrays of
- variables of an efficiently-aligned type, then it is likely that
- your program also does pointer arithmetic (or subscripting, which
- amounts to the same thing) on pointers to the relevant type, and
- the code that the compiler generates for these pointer arithmetic
- operations is often more efficient for efficiently-aligned types
- than for other types.
-
- The 'aligned' attribute can only increase the alignment; but you
- can decrease it by specifying 'packed' as well. See below.
-
- Note that the effectiveness of 'aligned' attributes may be limited
+ individual stand-alone objects of that type, the compiler's
+ ability to select a time-efficient alignment is primarily useful
+ only when you plan to create arrays of variables having the
+ relevant (efficiently aligned) type. If you declare or use arrays
+ of variables of an efficiently-aligned type, then it is likely
+ that your program also does pointer arithmetic (or subscripting,
+ which amounts to the same thing) on pointers to the relevant type,
+ and the code that the compiler generates for these pointer
+ arithmetic operations is often more efficient for
+ efficiently-aligned types than for other types.
+
+ The `aligned' attribute can only increase the alignment; but you
+ can decrease it by specifying `packed' as well. See below.
+
+ Note that the effectiveness of `aligned' attributes may be limited
by inherent limitations in your linker. On many systems, the
linker is only able to arrange for variables to be aligned up to a
certain maximum alignment. (For some linkers, the maximum
supported alignment may be very very small.) If your linker is
only able to align variables up to a maximum of 8-byte alignment,
- then specifying 'aligned(16)' in an '__attribute__' still only
+ then specifying `aligned(16)' in an `__attribute__' still only
provides you with 8-byte alignment. See your linker documentation
for further information.
-'packed'
- This attribute, attached to 'struct' or 'union' type definition,
+`packed'
+ This attribute, attached to `struct' or `union' type definition,
specifies that each member (other than zero-width bit-fields) of
the structure or union is placed to minimize the memory required.
- When attached to an 'enum' definition, it indicates that the
+ When attached to an `enum' definition, it indicates that the
smallest integral type should be used.
- Specifying this attribute for 'struct' and 'union' types is
- equivalent to specifying the 'packed' attribute on each of the
- structure or union members. Specifying the '-fshort-enums' flag on
- the line is equivalent to specifying the 'packed' attribute on all
- 'enum' definitions.
+ Specifying this attribute for `struct' and `union' types is
+ equivalent to specifying the `packed' attribute on each of the
+ structure or union members. Specifying the `-fshort-enums' flag
+ on the line is equivalent to specifying the `packed' attribute on
+ all `enum' definitions.
- In the following example 'struct my_packed_struct''s members are
- packed closely together, but the internal layout of its 's' member
- is not packed--to do that, 'struct my_unpacked_struct' needs to be
+ In the following example `struct my_packed_struct''s members are
+ packed closely together, but the internal layout of its `s' member
+ is not packed--to do that, `struct my_unpacked_struct' needs to be
packed too.
struct my_unpacked_struct
@@ -27874,13 +28094,12 @@ attributes.
struct my_unpacked_struct s;
};
- You may only specify this attribute on the definition of an 'enum',
- 'struct' or 'union', not on a 'typedef' that does not also define
+ You may only specify this attribute on the definition of an `enum',
+ `struct' or `union', not on a `typedef' that does not also define
the enumerated type, structure or union.
-'transparent_union'
-
- This attribute, attached to a 'union' type definition, indicates
+`transparent_union'
+ This attribute, attached to a `union' type definition, indicates
that any function parameter having that union type causes calls to
that function to be treated in a special way.
@@ -27890,7 +28109,7 @@ attributes.
null pointer constant or a void pointer expression; and if the
union contains a void pointer type, the corresponding argument can
be any pointer expression. If the union member type is a pointer,
- qualifiers like 'const' on the referenced type must be respected,
+ qualifiers like `const' on the referenced type must be respected,
just as with normal pointer conversions.
Second, the argument is passed to the function using the calling
@@ -27901,13 +28120,13 @@ attributes.
Transparent unions are designed for library functions that have
multiple interfaces for compatibility reasons. For example,
- suppose the 'wait' function must accept either a value of type 'int
- *' to comply with POSIX, or a value of type 'union wait *' to
- comply with the 4.1BSD interface. If 'wait''s parameter were 'void
- *', 'wait' would accept both kinds of arguments, but it would also
- accept any other pointer type and this would make argument type
- checking less useful. Instead, '<sys/wait.h>' might define the
- interface as follows:
+ suppose the `wait' function must accept either a value of type
+ `int *' to comply with POSIX, or a value of type `union wait *' to
+ comply with the 4.1BSD interface. If `wait''s parameter were
+ `void *', `wait' would accept both kinds of arguments, but it
+ would also accept any other pointer type and this would make
+ argument type checking less useful. Instead, `<sys/wait.h>' might
+ define the interface as follows:
typedef union __attribute__ ((__transparent_union__))
{
@@ -27917,22 +28136,22 @@ attributes.
pid_t wait (wait_status_ptr_t);
- This interface allows either 'int *' or 'union wait *' arguments to
- be passed, using the 'int *' calling convention. The program can
- call 'wait' with arguments of either type:
+ This interface allows either `int *' or `union wait *' arguments
+ to be passed, using the `int *' calling convention. The program
+ can call `wait' with arguments of either type:
int w1 () { int w; return wait (&w); }
int w2 () { union wait w; return wait (&w); }
- With this interface, 'wait''s implementation might look like this:
+ With this interface, `wait''s implementation might look like this:
pid_t wait (wait_status_ptr_t p)
{
return waitpid (-1, p.__ip, 0);
}
-'unused'
- When attached to a type (including a 'union' or a 'struct'), this
+`unused'
+ When attached to a type (including a `union' or a `struct'), this
attribute means that variables of that type are meant to appear
possibly unused. GCC does not produce a warning for any variables
of that type, even if the variable appears to do nothing. This is
@@ -27940,17 +28159,17 @@ attributes.
defined and then not referenced, but contain constructors and
destructors that have nontrivial bookkeeping functions.
-'deprecated'
-'deprecated (MSG)'
- The 'deprecated' attribute results in a warning if the type is used
- anywhere in the source file. This is useful when identifying types
- that are expected to be removed in a future version of a program.
- If possible, the warning also includes the location of the
- declaration of the deprecated type, to enable users to easily find
- further information about why the type is deprecated, or what they
- should do instead. Note that the warnings only occur for uses and
- then only if the type is being applied to an identifier that itself
- is not being declared as deprecated.
+`deprecated'
+`deprecated (MSG)'
+ The `deprecated' attribute results in a warning if the type is
+ used anywhere in the source file. This is useful when identifying
+ types that are expected to be removed in a future version of a
+ program. If possible, the warning also includes the location of
+ the declaration of the deprecated type, to enable users to easily
+ find further information about why the type is deprecated, or what
+ they should do instead. Note that the warnings only occur for
+ uses and then only if the type is being applied to an identifier
+ that itself is not being declared as deprecated.
typedef int T1 __attribute__ ((deprecated));
T1 x;
@@ -27965,17 +28184,17 @@ attributes.
deprecated. Similarly for line 6. The optional MSG argument,
which must be a string, is printed in the warning if present.
- The 'deprecated' attribute can also be used for functions and
+ The `deprecated' attribute can also be used for functions and
variables (*note Function Attributes::, *note Variable
Attributes::.)
-'may_alias'
+`may_alias'
Accesses through pointers to types with this attribute are not
- subject to type-based alias analysis, but are instead assumed to be
- able to alias any other type of objects. In the context of section
- 6.5 paragraph 7 of the C99 standard, an lvalue expression
+ subject to type-based alias analysis, but are instead assumed to
+ be able to alias any other type of objects. In the context of
+ section 6.5 paragraph 7 of the C99 standard, an lvalue expression
dereferencing such a pointer is treated like having a character
- type. See '-fstrict-aliasing' for more information on aliasing
+ type. See `-fstrict-aliasing' for more information on aliasing
issues. This extension exists to support some vector APIs, in
which pointers to one vector type are permitted to alias pointers
to a different vector type.
@@ -28001,36 +28220,37 @@ attributes.
exit(0);
}
- If you replaced 'short_a' with 'short' in the variable declaration,
- the above program would abort when compiled with
- '-fstrict-aliasing', which is on by default at '-O2' or above.
+ If you replaced `short_a' with `short' in the variable
+ declaration, the above program would abort when compiled with
+ `-fstrict-aliasing', which is on by default at `-O2' or above.
-'visibility'
- In C++, attribute visibility (*note Function Attributes::) can also
- be applied to class, struct, union and enum types. Unlike other
- type attributes, the attribute must appear between the initial
- keyword and the name of the type; it cannot appear after the body
- of the type.
+`visibility'
+ In C++, attribute visibility (*note Function Attributes::) can
+ also be applied to class, struct, union and enum types. Unlike
+ other type attributes, the attribute must appear between the
+ initial keyword and the name of the type; it cannot appear after
+ the body of the type.
Note that the type visibility is applied to vague linkage entities
associated with the class (vtable, typeinfo node, etc.). In
particular, if a class is thrown as an exception in one shared
object and caught in another, the class must have default
- visibility. Otherwise the two shared objects are unable to use the
- same typeinfo node and exception handling will break.
+ visibility. Otherwise the two shared objects are unable to use
+ the same typeinfo node and exception handling will break.
-'designated_init'
+`designated_init'
This attribute may only be applied to structure types. It
indicates that any initialization of an object of this type must
use designated initializers rather than positional initializers.
- The intent of this attribute is to allow the programmer to indicate
- that a structure's layout may change, and that therefore relying on
- positional initialization will result in future breakage.
+ The intent of this attribute is to allow the programmer to
+ indicate that a structure's layout may change, and that therefore
+ relying on positional initialization will result in future
+ breakage.
GCC emits warnings based on this attribute by default; use
- '-Wno-designated-init' to suppress them.
+ `-Wno-designated-init' to suppress them.
-'bnd_variable_size'
+`bnd_variable_size'
When applied to a structure field, this attribute tells Pointer
Bounds Checker that the size of this field should not be computed
using static type information. It may be used to mark
@@ -28056,17 +28276,18 @@ attributes.
S *p = (S *)malloc (sizeof(S) + 100);
p->data[10] = 0; //OK
+
To specify multiple attributes, separate them by commas within the
-double parentheses: for example, '__attribute__ ((aligned (16),
+double parentheses: for example, `__attribute__ ((aligned (16),
packed))'.
6.39.1 ARM Type Attributes
--------------------------
-On those ARM targets that support 'dllimport' (such as Symbian OS), you
-can use the 'notshared' attribute to indicate that the virtual table and
-other similar data for a class should not be exported from a DLL. For
-example:
+On those ARM targets that support `dllimport' (such as Symbian OS), you
+can use the `notshared' attribute to indicate that the virtual table
+and other similar data for a class should not be exported from a DLL.
+For example:
class __declspec(notshared) C {
public:
@@ -28077,65 +28298,64 @@ example:
__declspec(dllexport)
C::C() {}
-In this code, 'C::C' is exported from the current DLL, but the virtual
-table for 'C' is not exported. (You can use '__attribute__' instead of
-'__declspec' if you prefer, but most Symbian OS code uses '__declspec'.)
+In this code, `C::C' is exported from the current DLL, but the virtual
+table for `C' is not exported. (You can use `__attribute__' instead of
+`__declspec' if you prefer, but most Symbian OS code uses `__declspec'.)
6.39.2 MeP Type Attributes
--------------------------
Many of the MeP variable attributes may be applied to types as well.
-Specifically, the 'based', 'tiny', 'near', and 'far' attributes may be
-applied to either. The 'io' and 'cb' attributes may not be applied to
+Specifically, the `based', `tiny', `near', and `far' attributes may be
+applied to either. The `io' and `cb' attributes may not be applied to
types.
6.39.3 PowerPC Type Attributes
------------------------------
Three attributes currently are defined for PowerPC configurations:
-'altivec', 'ms_struct' and 'gcc_struct'.
+`altivec', `ms_struct' and `gcc_struct'.
- For full documentation of the 'ms_struct' and 'gcc_struct' attributes
+ For full documentation of the `ms_struct' and `gcc_struct' attributes
please see the documentation in *note x86 Type Attributes::.
- The 'altivec' attribute allows one to declare AltiVec vector data types
-supported by the AltiVec Programming Interface Manual. The attribute
-requires an argument to specify one of three vector types: 'vector__',
-'pixel__' (always followed by unsigned short), and 'bool__' (always
-followed by unsigned).
+ The `altivec' attribute allows one to declare AltiVec vector data
+types supported by the AltiVec Programming Interface Manual. The
+attribute requires an argument to specify one of three vector types:
+`vector__', `pixel__' (always followed by unsigned short), and `bool__'
+(always followed by unsigned).
__attribute__((altivec(vector__)))
__attribute__((altivec(pixel__))) unsigned short
__attribute__((altivec(bool__))) unsigned
- These attributes mainly are intended to support the '__vector',
-'__pixel', and '__bool' AltiVec keywords.
+ These attributes mainly are intended to support the `__vector',
+`__pixel', and `__bool' AltiVec keywords.
6.39.4 SPU Type Attributes
--------------------------
-The SPU supports the 'spu_vector' attribute for types. This attribute
+The SPU supports the `spu_vector' attribute for types. This attribute
allows one to declare vector data types supported by the
Sony/Toshiba/IBM SPU Language Extensions Specification. It is intended
-to support the '__vector' keyword.
+to support the `__vector' keyword.
6.39.5 x86 Type Attributes
--------------------------
-Two attributes are currently defined for x86 configurations: 'ms_struct'
-and 'gcc_struct'.
-
-'ms_struct'
-'gcc_struct'
+Two attributes are currently defined for x86 configurations:
+`ms_struct' and `gcc_struct'.
- If 'packed' is used on a structure, or if bit-fields are used it
+`ms_struct'
+`gcc_struct'
+ If `packed' is used on a structure, or if bit-fields are used it
may be that the Microsoft ABI packs them differently than GCC
normally packs them. Particularly when moving packed data between
functions compiled with GCC and the native Microsoft compiler
(either via function call or as data in a file), it may be
necessary to access either format.
- Currently '-m[no-]ms-bitfields' is provided for the Microsoft
+ Currently `-m[no-]ms-bitfields' is provided for the Microsoft
Windows x86 compilers to match the native Microsoft compiler.

@@ -28144,29 +28364,29 @@ File: gcc.info, Node: Alignment, Next: Inline, Prev: Type Attributes, Up: C
6.40 Inquiring on Alignment of Types or Variables
=================================================
-The keyword '__alignof__' allows you to inquire about how an object is
+The keyword `__alignof__' allows you to inquire about how an object is
aligned, or the minimum alignment usually required by a type. Its
-syntax is just like 'sizeof'.
+syntax is just like `sizeof'.
- For example, if the target machine requires a 'double' value to be
-aligned on an 8-byte boundary, then '__alignof__ (double)' is 8. This
+ For example, if the target machine requires a `double' value to be
+aligned on an 8-byte boundary, then `__alignof__ (double)' is 8. This
is true on many RISC machines. On more traditional machine designs,
-'__alignof__ (double)' is 4 or even 2.
+`__alignof__ (double)' is 4 or even 2.
- Some machines never actually require alignment; they allow reference to
-any data type even at an odd address. For these machines, '__alignof__'
-reports the smallest alignment that GCC gives the data type, usually as
-mandated by the target ABI.
+ Some machines never actually require alignment; they allow reference
+to any data type even at an odd address. For these machines,
+`__alignof__' reports the smallest alignment that GCC gives the data
+type, usually as mandated by the target ABI.
- If the operand of '__alignof__' is an lvalue rather than a type, its
+ If the operand of `__alignof__' is an lvalue rather than a type, its
value is the required alignment for its type, taking into account any
-minimum alignment specified with GCC's '__attribute__' extension (*note
+minimum alignment specified with GCC's `__attribute__' extension (*note
Variable Attributes::). For example, after this declaration:
struct foo { int x; char y; } foo1;
-the value of '__alignof__ (foo1.y)' is 1, even though its actual
-alignment is probably 2 or 4, the same as '__alignof__ (int)'.
+the value of `__alignof__ (foo1.y)' is 1, even though its actual
+alignment is probably 2 or 4, the same as `__alignof__ (int)'.
It is an error to ask for the alignment of an incomplete type.
@@ -28176,25 +28396,25 @@ File: gcc.info, Node: Inline, Next: Volatiles, Prev: Alignment, Up: C Extens
6.41 An Inline Function is As Fast As a Macro
=============================================
-By declaring a function inline, you can direct GCC to make calls to that
-function faster. One way GCC can achieve this is to integrate that
-function's code into the code for its callers. This makes execution
-faster by eliminating the function-call overhead; in addition, if any of
-the actual argument values are constant, their known values may permit
-simplifications at compile time so that not all of the inline function's
-code needs to be included. The effect on code size is less predictable;
-object code may be larger or smaller with function inlining, depending
-on the particular case. You can also direct GCC to try to integrate all
-"simple enough" functions into their callers with the option
-'-finline-functions'.
+By declaring a function inline, you can direct GCC to make calls to
+that function faster. One way GCC can achieve this is to integrate
+that function's code into the code for its callers. This makes
+execution faster by eliminating the function-call overhead; in
+addition, if any of the actual argument values are constant, their
+known values may permit simplifications at compile time so that not all
+of the inline function's code needs to be included. The effect on code
+size is less predictable; object code may be larger or smaller with
+function inlining, depending on the particular case. You can also
+direct GCC to try to integrate all "simple enough" functions into their
+callers with the option `-finline-functions'.
GCC implements three different semantics of declaring a function
-inline. One is available with '-std=gnu89' or '-fgnu89-inline' or when
-'gnu_inline' attribute is present on all inline declarations, another
-when '-std=c99', '-std=c11', '-std=gnu99' or '-std=gnu11' (without
-'-fgnu89-inline'), and the third is used when compiling C++.
+inline. One is available with `-std=gnu89' or `-fgnu89-inline' or when
+`gnu_inline' attribute is present on all inline declarations, another
+when `-std=c99', `-std=c11', `-std=gnu99' or `-std=gnu11' (without
+`-fgnu89-inline'), and the third is used when compiling C++.
- To declare a function inline, use the 'inline' keyword in its
+ To declare a function inline, use the `inline' keyword in its
declaration, like this:
static inline int
@@ -28204,12 +28424,12 @@ declaration, like this:
}
If you are writing a header file to be included in ISO C90 programs,
-write '__inline__' instead of 'inline'. *Note Alternate Keywords::.
+write `__inline__' instead of `inline'. *Note Alternate Keywords::.
The three types of inlining behave similarly in two important cases:
-when the 'inline' keyword is used on a 'static' function, like the
+when the `inline' keyword is used on a `static' function, like the
example above, and when a function is first declared without using the
-'inline' keyword and then is defined with 'inline', like this:
+`inline' keyword and then is defined with `inline', like this:
extern int inc (int *a);
inline int
@@ -28219,61 +28439,61 @@ example above, and when a function is first declared without using the
}
In both of these common cases, the program behaves the same as if you
-had not used the 'inline' keyword, except for its speed.
+had not used the `inline' keyword, except for its speed.
- When a function is both inline and 'static', if all calls to the
+ When a function is both inline and `static', if all calls to the
function are integrated into the caller, and the function's address is
never used, then the function's own assembler code is never referenced.
In this case, GCC does not actually output assembler code for the
-function, unless you specify the option '-fkeep-inline-functions'. Some
-calls cannot be integrated for various reasons (in particular, calls
-that precede the function's definition cannot be integrated, and neither
-can recursive calls within the definition). If there is a nonintegrated
-call, then the function is compiled to assembler code as usual. The
-function must also be compiled as usual if the program refers to its
-address, because that can't be inlined.
+function, unless you specify the option `-fkeep-inline-functions'.
+Some calls cannot be integrated for various reasons (in particular,
+calls that precede the function's definition cannot be integrated, and
+neither can recursive calls within the definition). If there is a
+nonintegrated call, then the function is compiled to assembler code as
+usual. The function must also be compiled as usual if the program
+refers to its address, because that can't be inlined.
Note that certain usages in a function definition can make it
unsuitable for inline substitution. Among these usages are: variadic
-functions, use of 'alloca', use of variable-length data types (*note
-Variable Length::), use of computed goto (*note Labels as Values::), use
-of nonlocal goto, and nested functions (*note Nested Functions::).
-Using '-Winline' warns when a function marked 'inline' could not be
+functions, use of `alloca', use of variable-length data types (*note
+Variable Length::), use of computed goto (*note Labels as Values::),
+use of nonlocal goto, and nested functions (*note Nested Functions::).
+Using `-Winline' warns when a function marked `inline' could not be
substituted, and gives the reason for the failure.
As required by ISO C++, GCC considers member functions defined within
the body of a class to be marked inline even if they are not explicitly
-declared with the 'inline' keyword. You can override this with
-'-fno-default-inline'; *note Options Controlling C++ Dialect: C++
+declared with the `inline' keyword. You can override this with
+`-fno-default-inline'; *note Options Controlling C++ Dialect: C++
Dialect Options.
GCC does not inline any functions when not optimizing unless you
-specify the 'always_inline' attribute for the function, like this:
+specify the `always_inline' attribute for the function, like this:
/* Prototype. */
inline void foo (const char) __attribute__((always_inline));
The remainder of this section is specific to GNU C90 inlining.
- When an inline function is not 'static', then the compiler must assume
+ When an inline function is not `static', then the compiler must assume
that there may be calls from other source files; since a global symbol
can be defined only once in any program, the function must not be
defined in the other source files, so the calls therein cannot be
-integrated. Therefore, a non-'static' inline function is always
+integrated. Therefore, a non-`static' inline function is always
compiled on its own in the usual fashion.
- If you specify both 'inline' and 'extern' in the function definition,
+ If you specify both `inline' and `extern' in the function definition,
then the definition is used only for inlining. In no case is the
function compiled on its own, not even if you refer to its address
explicitly. Such an address becomes an external reference, as if you
had only declared the function, and had not defined it.
- This combination of 'inline' and 'extern' has almost the effect of a
+ This combination of `inline' and `extern' has almost the effect of a
macro. The way to use it is to put a function definition in a header
file with these keywords, and put another copy of the definition
-(lacking 'inline' and 'extern') in a library file. The definition in
-the header file causes most calls to the function to be inlined. If any
-uses of the function remain, they refer to the single copy in the
+(lacking `inline' and `extern') in a library file. The definition in
+the header file causes most calls to the function to be inlined. If
+any uses of the function remain, they refer to the single copy in the
library.

@@ -28296,17 +28516,18 @@ allow you to violate the restriction on updating objects multiple times
between two sequence points.
Accesses to non-volatile objects are not ordered with respect to
-volatile accesses. You cannot use a volatile object as a memory barrier
-to order a sequence of writes to non-volatile memory. For instance:
+volatile accesses. You cannot use a volatile object as a memory
+barrier to order a sequence of writes to non-volatile memory. For
+instance:
int *ptr = SOMETHING;
volatile int vobj;
*ptr = SOMETHING;
vobj = 1;
-Unless *PTR and VOBJ can be aliased, it is not guaranteed that the write
-to *PTR occurs by the time the update of VOBJ happens. If you need this
-guarantee, you must use a stronger memory barrier such as:
+Unless *PTR and VOBJ can be aliased, it is not guaranteed that the
+write to *PTR occurs by the time the update of VOBJ happens. If you
+need this guarantee, you must use a stronger memory barrier such as:
int *ptr = SOMETHING;
volatile int vobj;
@@ -28324,9 +28545,9 @@ volatile object being pointed to.
Assignments are also expressions and have an rvalue. However when
assigning to a scalar volatile, the volatile object is not reread,
-regardless of whether the assignment expression's rvalue is used or not.
-If the assignment's rvalue is used, the value is that assigned to the
-volatile object. For instance, there is no read of VOBJ in all the
+regardless of whether the assignment expression's rvalue is used or
+not. If the assignment's rvalue is used, the value is that assigned to
+the volatile object. For instance, there is no read of VOBJ in all the
following cases:
int obj;
@@ -28353,25 +28574,25 @@ File: gcc.info, Node: Using Assembly Language with C, Next: Alternate Keywords
6.43 How to Use Inline Assembly Language in C Code
==================================================
-The 'asm' keyword allows you to embed assembler instructions within C
-code. GCC provides two forms of inline 'asm' statements. A "basic
-'asm'" statement is one with no operands (*note Basic Asm::), while an
-"extended 'asm'" statement (*note Extended Asm::) includes one or more
+The `asm' keyword allows you to embed assembler instructions within C
+code. GCC provides two forms of inline `asm' statements. A "basic
+`asm'" statement is one with no operands (*note Basic Asm::), while an
+"extended `asm'" statement (*note Extended Asm::) includes one or more
operands. The extended form is preferred for mixing C and assembly
language within a function, but to include assembly language at top
-level you must use basic 'asm'.
+level you must use basic `asm'.
- You can also use the 'asm' keyword to override the assembler name for a
-C symbol, or to place a C variable in a specific register.
+ You can also use the `asm' keyword to override the assembler name for
+a C symbol, or to place a C variable in a specific register.
* Menu:
* Basic Asm:: Inline assembler without operands.
* Extended Asm:: Inline assembler with operands.
-* Constraints:: Constraints for 'asm' operands
+* Constraints:: Constraints for `asm' operands
* Asm Labels:: Specifying the assembler name to use for a C symbol.
* Explicit Reg Vars:: Defining variables residing in specified registers.
-* Size of an asm:: How GCC calculates the size of an 'asm' block.
+* Size of an asm:: How GCC calculates the size of an `asm' block.

File: gcc.info, Node: Basic Asm, Next: Extended Asm, Up: Using Assembly Language with C
@@ -28379,94 +28600,94 @@ File: gcc.info, Node: Basic Asm, Next: Extended Asm, Up: Using Assembly Langu
6.43.1 Basic Asm -- Assembler Instructions Without Operands
-----------------------------------------------------------
-A basic 'asm' statement has the following syntax:
+A basic `asm' statement has the following syntax:
asm [ volatile ] ( ASSEMBLERINSTRUCTIONS )
- The 'asm' keyword is a GNU extension. When writing code that can be
-compiled with '-ansi' and the various '-std' options, use '__asm__'
-instead of 'asm' (*note Alternate Keywords::).
+ The `asm' keyword is a GNU extension. When writing code that can be
+compiled with `-ansi' and the various `-std' options, use `__asm__'
+instead of `asm' (*note Alternate Keywords::).
Qualifiers
..........
-'volatile'
- The optional 'volatile' qualifier has no effect. All basic 'asm'
+`volatile'
+ The optional `volatile' qualifier has no effect. All basic `asm'
blocks are implicitly volatile.
Parameters
..........
ASSEMBLERINSTRUCTIONS
- This is a literal string that specifies the assembler code. The
+ This is a literal string that specifies the assembler code. The
string can contain any instructions recognized by the assembler,
including directives. GCC does not parse the assembler
instructions themselves and does not know what they mean or even
whether they are valid assembler input.
You may place multiple assembler instructions together in a single
- 'asm' string, separated by the characters normally used in assembly
- code for the system. A combination that works in most places is a
- newline to break the line, plus a tab character (written as
- '\n\t'). Some assemblers allow semicolons as a line separator.
- However, note that some assembler dialects use semicolons to start
- a comment.
+ `asm' string, separated by the characters normally used in
+ assembly code for the system. A combination that works in most
+ places is a newline to break the line, plus a tab character
+ (written as `\n\t'). Some assemblers allow semicolons as a line
+ separator. However, note that some assembler dialects use
+ semicolons to start a comment.
Remarks
.......
-Using extended 'asm' typically produces smaller, safer, and more
+Using extended `asm' typically produces smaller, safer, and more
efficient code, and in most cases it is a better solution than basic
-'asm'. However, there are two situations where only basic 'asm' can be
+`asm'. However, there are two situations where only basic `asm' can be
used:
- * Extended 'asm' statements have to be inside a C function, so to
- write inline assembly language at file scope ("top-level"), outside
- of C functions, you must use basic 'asm'. You can use this
- technique to emit assembler directives, define assembly language
- macros that can be invoked elsewhere in the file, or write entire
- functions in assembly language.
+ * Extended `asm' statements have to be inside a C function, so to
+ write inline assembly language at file scope ("top-level"),
+ outside of C functions, you must use basic `asm'. You can use
+ this technique to emit assembler directives, define assembly
+ language macros that can be invoked elsewhere in the file, or
+ write entire functions in assembly language.
- * Functions declared with the 'naked' attribute also require basic
- 'asm' (*note Function Attributes::).
+ * Functions declared with the `naked' attribute also require basic
+ `asm' (*note Function Attributes::).
- Safely accessing C data and calling functions from basic 'asm' is more
-complex than it may appear. To access C data, it is better to use
-extended 'asm'.
+ Safely accessing C data and calling functions from basic `asm' is more
+complex than it may appear. To access C data, it is better to use
+extended `asm'.
- Do not expect a sequence of 'asm' statements to remain perfectly
-consecutive after compilation. If certain instructions need to remain
-consecutive in the output, put them in a single multi-instruction 'asm'
-statement. Note that GCC's optimizers can move 'asm' statements
+ Do not expect a sequence of `asm' statements to remain perfectly
+consecutive after compilation. If certain instructions need to remain
+consecutive in the output, put them in a single multi-instruction `asm'
+statement. Note that GCC's optimizers can move `asm' statements
relative to other code, including across jumps.
- 'asm' statements may not perform jumps into other 'asm' statements.
+ `asm' statements may not perform jumps into other `asm' statements.
GCC does not know about these jumps, and therefore cannot take account
-of them when deciding how to optimize. Jumps from 'asm' to C labels are
-only supported in extended 'asm'.
+of them when deciding how to optimize. Jumps from `asm' to C labels are
+only supported in extended `asm'.
Under certain circumstances, GCC may duplicate (or remove duplicates
-of) your assembly code when optimizing. This can lead to unexpected
-duplicate symbol errors during compilation if your assembly code defines
-symbols or labels.
+of) your assembly code when optimizing. This can lead to unexpected
+duplicate symbol errors during compilation if your assembly code
+defines symbols or labels.
Since GCC does not parse the ASSEMBLERINSTRUCTIONS, it has no
-visibility of any symbols it references. This may result in GCC
+visibility of any symbols it references. This may result in GCC
discarding those symbols as unreferenced.
- The compiler copies the assembler instructions in a basic 'asm'
+ The compiler copies the assembler instructions in a basic `asm'
verbatim to the assembly language output file, without processing
-dialects or any of the '%' operators that are available with extended
-'asm'. This results in minor differences between basic 'asm' strings
-and extended 'asm' templates. For example, to refer to registers you
-might use '%eax' in basic 'asm' and '%%eax' in extended 'asm'.
+dialects or any of the `%' operators that are available with extended
+`asm'. This results in minor differences between basic `asm' strings
+and extended `asm' templates. For example, to refer to registers you
+might use `%eax' in basic `asm' and `%%eax' in extended `asm'.
On targets such as x86 that support multiple assembler dialects, all
-basic 'asm' blocks use the assembler dialect specified by the '-masm'
-command-line option (*note x86 Options::). Basic 'asm' provides no
+basic `asm' blocks use the assembler dialect specified by the `-masm'
+command-line option (*note x86 Options::). Basic `asm' provides no
mechanism to provide different assembler strings for different dialects.
- Here is an example of basic 'asm' for i386:
+ Here is an example of basic `asm' for i386:
/* Note that this code will not compile with -masm=intel */
#define DebugBreak() asm("int $3")
@@ -28477,9 +28698,9 @@ File: gcc.info, Node: Extended Asm, Next: Constraints, Prev: Basic Asm, Up:
6.43.2 Extended Asm - Assembler Instructions with C Expression Operands
-----------------------------------------------------------------------
-With extended 'asm' you can read and write C variables from assembler
-and perform jumps from assembler code to C labels. Extended 'asm'
-syntax uses colons (':') to delimit the operand parameters after the
+With extended `asm' you can read and write C variables from assembler
+and perform jumps from assembler code to C labels. Extended `asm'
+syntax uses colons (`:') to delimit the operand parameters after the
assembler template:
asm [volatile] ( ASSEMBLERTEMPLATE
@@ -28493,22 +28714,22 @@ assembler template:
: CLOBBERS
: GOTOLABELS)
- The 'asm' keyword is a GNU extension. When writing code that can be
-compiled with '-ansi' and the various '-std' options, use '__asm__'
-instead of 'asm' (*note Alternate Keywords::).
+ The `asm' keyword is a GNU extension. When writing code that can be
+compiled with `-ansi' and the various `-std' options, use `__asm__'
+instead of `asm' (*note Alternate Keywords::).
Qualifiers
..........
-'volatile'
- The typical use of extended 'asm' statements is to manipulate input
- values to produce output values. However, your 'asm' statements
- may also produce side effects. If so, you may need to use the
- 'volatile' qualifier to disable certain optimizations. *Note
+`volatile'
+ The typical use of extended `asm' statements is to manipulate input
+ values to produce output values. However, your `asm' statements may
+ also produce side effects. If so, you may need to use the
+ `volatile' qualifier to disable certain optimizations. *Note
Volatile::.
-'goto'
- This qualifier informs the compiler that the 'asm' statement may
+`goto'
+ This qualifier informs the compiler that the `asm' statement may
perform a jump to one of the labels listed in the GOTOLABELS.
*Note GotoLabels::.
@@ -28517,17 +28738,17 @@ Parameters
ASSEMBLERTEMPLATE
This is a literal string that is the template for the assembler
- code. It is a combination of fixed text and tokens that refer to
- the input, output, and goto parameters. *Note AssemblerTemplate::.
+ code. It is a combination of fixed text and tokens that refer to
+ the input, output, and goto parameters. *Note AssemblerTemplate::.
OUTPUTOPERANDS
A comma-separated list of the C variables modified by the
- instructions in the ASSEMBLERTEMPLATE. An empty list is permitted.
- *Note OutputOperands::.
+ instructions in the ASSEMBLERTEMPLATE. An empty list is
+ permitted. *Note OutputOperands::.
INPUTOPERANDS
- A comma-separated list of C expressions read by the instructions in
- the ASSEMBLERTEMPLATE. An empty list is permitted. *Note
+ A comma-separated list of C expressions read by the instructions
+ in the ASSEMBLERTEMPLATE. An empty list is permitted. *Note
InputOperands::.
CLOBBERS
@@ -28536,11 +28757,11 @@ CLOBBERS
is permitted. *Note Clobbers::.
GOTOLABELS
- When you are using the 'goto' form of 'asm', this section contains
- the list of all C labels to which the code in the ASSEMBLERTEMPLATE
- may jump. *Note GotoLabels::.
+ When you are using the `goto' form of `asm', this section contains
+ the list of all C labels to which the code in the
+ ASSEMBLERTEMPLATE may jump. *Note GotoLabels::.
- 'asm' statements may not perform jumps into other 'asm' statements,
+ `asm' statements may not perform jumps into other `asm' statements,
only to the listed GOTOLABELS. GCC's optimizers do not know about
other jumps; therefore they cannot take account of them when
deciding how to optimize.
@@ -28550,20 +28771,20 @@ GOTOLABELS
Remarks
.......
-The 'asm' statement allows you to include assembly instructions directly
-within C code. This may help you to maximize performance in
+The `asm' statement allows you to include assembly instructions directly
+within C code. This may help you to maximize performance in
time-sensitive code or to access assembly instructions that are not
readily available to C programs.
- Note that extended 'asm' statements must be inside a function. Only
-basic 'asm' may be outside functions (*note Basic Asm::). Functions
-declared with the 'naked' attribute also require basic 'asm' (*note
+ Note that extended `asm' statements must be inside a function. Only
+basic `asm' may be outside functions (*note Basic Asm::). Functions
+declared with the `naked' attribute also require basic `asm' (*note
Function Attributes::).
- While the uses of 'asm' are many and varied, it may help to think of an
-'asm' statement as a series of low-level instructions that convert input
-parameters to output parameters. So a simple (if not particularly
-useful) example for i386 using 'asm' might look like this:
+ While the uses of `asm' are many and varied, it may help to think of an
+`asm' statement as a series of low-level instructions that convert input
+parameters to output parameters. So a simple (if not particularly
+useful) example for i386 using `asm' might look like this:
int src = 1;
int dst;
@@ -28575,26 +28796,27 @@ useful) example for i386 using 'asm' might look like this:
printf("%d\n", dst);
- This code copies 'src' to 'dst' and add 1 to 'dst'.
+ This code copies `src' to `dst' and add 1 to `dst'.
6.43.2.1 Volatile
.................
-GCC's optimizers sometimes discard 'asm' statements if they determine
-there is no need for the output variables. Also, the optimizers may
-move code out of loops if they believe that the code will always return
-the same result (i.e. none of its input values change between calls).
-Using the 'volatile' qualifier disables these optimizations. 'asm'
-statements that have no output operands, including 'asm goto'
-statements, are implicitly volatile.
+GCC's optimizers sometimes discard `asm' statements if they determine
+there is no need for the output variables. Also, the optimizers may move
+code out of loops if they believe that the code will always return the
+same result (i.e. none of its input values change between calls). Using
+the `volatile' qualifier disables these optimizations. `asm' statements
+that have no output operands, including `asm goto' statements, are
+implicitly volatile.
This i386 code demonstrates a case that does not use (or require) the
-'volatile' qualifier. If it is performing assertion checking, this code
-uses 'asm' to perform the validation. Otherwise, 'dwRes' is
-unreferenced by any code. As a result, the optimizers can discard the
-'asm' statement, which in turn removes the need for the entire 'DoCheck'
-routine. By omitting the 'volatile' qualifier when it isn't needed you
-allow the optimizers to produce the most efficient code possible.
+`volatile' qualifier. If it is performing assertion checking, this code
+uses `asm' to perform the validation. Otherwise, `dwRes' is
+unreferenced by any code. As a result, the optimizers can discard the
+`asm' statement, which in turn removes the need for the entire
+`DoCheck' routine. By omitting the `volatile' qualifier when it isn't
+needed you allow the optimizers to produce the most efficient code
+possible.
void DoCheck(uint32_t dwSomeValue)
{
@@ -28610,9 +28832,9 @@ allow the optimizers to produce the most efficient code possible.
}
The next example shows a case where the optimizers can recognize that
-the input ('dwSomeValue') never changes during the execution of the
-function and can therefore move the 'asm' outside the loop to produce
-more efficient code. Again, using 'volatile' disables this type of
+the input (`dwSomeValue') never changes during the execution of the
+function and can therefore move the `asm' outside the loop to produce
+more efficient code. Again, using `volatile' disables this type of
optimization.
void do_print(uint32_t dwSomeValue)
@@ -28632,9 +28854,9 @@ optimization.
}
The following example demonstrates a case where you need to use the
-'volatile' qualifier. It uses the x86 'rdtsc' instruction, which reads
-the computer's time-stamp counter. Without the 'volatile' qualifier,
-the optimizers might assume that the 'asm' block will always return the
+`volatile' qualifier. It uses the x86 `rdtsc' instruction, which reads
+the computer's time-stamp counter. Without the `volatile' qualifier,
+the optimizers might assume that the `asm' block will always return the
same value and therefore optimize away the second call.
uint64_t msr;
@@ -28661,29 +28883,29 @@ same value and therefore optimize away the second call.
printf("msr: %llx\n", msr);
GCC's optimizers do not treat this code like the non-volatile code in
-the earlier examples. They do not move it out of loops or omit it on
-the assumption that the result from a previous call is still valid.
+the earlier examples. They do not move it out of loops or omit it on the
+assumption that the result from a previous call is still valid.
- Note that the compiler can move even volatile 'asm' instructions
-relative to other code, including across jump instructions. For
+ Note that the compiler can move even volatile `asm' instructions
+relative to other code, including across jump instructions. For
example, on many targets there is a system register that controls the
-rounding mode of floating-point operations. Setting it with a volatile
-'asm', as in the following PowerPC example, does not work reliably.
+rounding mode of floating-point operations. Setting it with a volatile
+`asm', as in the following PowerPC example, does not work reliably.
asm volatile("mtfsf 255, %0" : : "f" (fpenv));
sum = x + y;
- The compiler may move the addition back before the volatile 'asm'. To
-make it work as expected, add an artificial dependency to the 'asm' by
+ The compiler may move the addition back before the volatile `asm'. To
+make it work as expected, add an artificial dependency to the `asm' by
referencing a variable in the subsequent code, for example:
asm volatile ("mtfsf 255,%1" : "=X" (sum) : "f" (fpenv));
sum = x + y;
Under certain circumstances, GCC may duplicate (or remove duplicates
-of) your assembly code when optimizing. This can lead to unexpected
+of) your assembly code when optimizing. This can lead to unexpected
duplicate symbol errors during compilation if your asm code defines
-symbols or labels. Using '%=' (*note AssemblerTemplate::) may help
+symbols or labels. Using `%=' (*note AssemblerTemplate::) may help
resolve this problem.
6.43.2.2 Assembler Template
@@ -28692,35 +28914,35 @@ resolve this problem.
An assembler template is a literal string containing assembler
instructions. The compiler replaces tokens in the template that refer
to inputs, outputs, and goto labels, and then outputs the resulting
-string to the assembler. The string can contain any instructions
-recognized by the assembler, including directives. GCC does not parse
+string to the assembler. The string can contain any instructions
+recognized by the assembler, including directives. GCC does not parse
the assembler instructions themselves and does not know what they mean
-or even whether they are valid assembler input. However, it does count
+or even whether they are valid assembler input. However, it does count
the statements (*note Size of an asm::).
You may place multiple assembler instructions together in a single
-'asm' string, separated by the characters normally used in assembly code
-for the system. A combination that works in most places is a newline to
-break the line, plus a tab character to move to the instruction field
-(written as '\n\t'). Some assemblers allow semicolons as a line
-separator. However, note that some assembler dialects use semicolons to
-start a comment.
-
- Do not expect a sequence of 'asm' statements to remain perfectly
-consecutive after compilation, even when you are using the 'volatile'
-qualifier. If certain instructions need to remain consecutive in the
+`asm' string, separated by the characters normally used in assembly
+code for the system. A combination that works in most places is a
+newline to break the line, plus a tab character to move to the
+instruction field (written as `\n\t'). Some assemblers allow
+semicolons as a line separator. However, note that some assembler
+dialects use semicolons to start a comment.
+
+ Do not expect a sequence of `asm' statements to remain perfectly
+consecutive after compilation, even when you are using the `volatile'
+qualifier. If certain instructions need to remain consecutive in the
output, put them in a single multi-instruction asm statement.
Accessing data from C programs without using input/output operands
(such as by using global symbols directly from the assembler template)
-may not work as expected. Similarly, calling functions directly from an
+may not work as expected. Similarly, calling functions directly from an
assembler template requires a detailed understanding of the target
assembler and ABI.
Since GCC does not parse the assembler template, it has no visibility
-of any symbols it references. This may result in GCC discarding those
-symbols as unreferenced unless they are also listed as input, output, or
-goto operands.
+of any symbols it references. This may result in GCC discarding those
+symbols as unreferenced unless they are also listed as input, output,
+or goto operands.
Special format strings
......................
@@ -28728,48 +28950,48 @@ Special format strings
In addition to the tokens described by the input, output, and goto
operands, these tokens have special meanings in the assembler template:
-'%%'
- Outputs a single '%' into the assembler code.
+`%%'
+ Outputs a single `%' into the assembler code.
-'%='
- Outputs a number that is unique to each instance of the 'asm'
- statement in the entire compilation. This option is useful when
+`%='
+ Outputs a number that is unique to each instance of the `asm'
+ statement in the entire compilation. This option is useful when
creating local labels and referring to them multiple times in a
single template that generates multiple assembler instructions.
-'%{'
-'%|'
-'%}'
- Outputs '{', '|', and '}' characters (respectively) into the
+`%{'
+`%|'
+`%}'
+ Outputs `{', `|', and `}' characters (respectively) into the
assembler code. When unescaped, these characters have special
meaning to indicate multiple assembler dialects, as described
below.
-Multiple assembler dialects in 'asm' templates
+Multiple assembler dialects in `asm' templates
..............................................
On targets such as x86, GCC supports multiple assembler dialects. The
-'-masm' option controls which dialect GCC uses as its default for inline
-assembler. The target-specific documentation for the '-masm' option
-contains the list of supported dialects, as well as the default dialect
-if the option is not specified. This information may be important to
-understand, since assembler code that works correctly when compiled
-using one dialect will likely fail if compiled using another. *Note x86
-Options::.
-
- If your code needs to support multiple assembler dialects (for example,
-if you are writing public headers that need to support a variety of
-compilation options), use constructs of this form:
+`-masm' option controls which dialect GCC uses as its default for
+inline assembler. The target-specific documentation for the `-masm'
+option contains the list of supported dialects, as well as the default
+dialect if the option is not specified. This information may be
+important to understand, since assembler code that works correctly when
+compiled using one dialect will likely fail if compiled using another.
+*Note x86 Options::.
+
+ If your code needs to support multiple assembler dialects (for
+example, if you are writing public headers that need to support a
+variety of compilation options), use constructs of this form:
{ dialect0 | dialect1 | dialect2... }
- This construct outputs 'dialect0' when using dialect #0 to compile the
-code, 'dialect1' for dialect #1, etc. If there are fewer alternatives
-within the braces than the number of dialects the compiler supports, the
-construct outputs nothing.
+ This construct outputs `dialect0' when using dialect #0 to compile the
+code, `dialect1' for dialect #1, etc. If there are fewer alternatives
+within the braces than the number of dialects the compiler supports,
+the construct outputs nothing.
- For example, if an x86 compiler supports two dialects ('att', 'intel'),
-an assembler template such as this:
+ For example, if an x86 compiler supports two dialects (`att',
+`intel'), an assembler template such as this:
"bt{l %[Offset],%[Base] | %[Base],%[Offset]}; jc %l2"
@@ -28792,11 +29014,11 @@ corresponds to either
6.43.2.3 Output Operands
........................
-An 'asm' statement has zero or more output operands indicating the names
+An `asm' statement has zero or more output operands indicating the names
of C variables modified by the assembler code.
- In this i386 example, 'old' (referred to in the template string as
-'%0') and '*Base' (as '%1') are outputs and 'Offset' ('%2') is an input:
+ In this i386 example, `old' (referred to in the template string as
+`%0') and `*Base' (as `%1') are outputs and `Offset' (`%2') is an input:
bool old;
@@ -28815,37 +29037,37 @@ of C variables modified by the assembler code.
ASMSYMBOLICNAME
Specifies a symbolic name for the operand. Reference the name in
the assembler template by enclosing it in square brackets (i.e.
- '%[Value]'). The scope of the name is the 'asm' statement that
- contains the definition. Any valid C variable name is acceptable,
- including names already defined in the surrounding code. No two
- operands within the same 'asm' statement can use the same symbolic
+ `%[Value]'). The scope of the name is the `asm' statement that
+ contains the definition. Any valid C variable name is acceptable,
+ including names already defined in the surrounding code. No two
+ operands within the same `asm' statement can use the same symbolic
name.
- When not using an ASMSYMBOLICNAME, use the (zero-based) position of
- the operand in the list of operands in the assembler template. For
- example if there are three output operands, use '%0' in the
- template to refer to the first, '%1' for the second, and '%2' for
+ When not using an ASMSYMBOLICNAME, use the (zero-based) position
+ of the operand in the list of operands in the assembler template.
+ For example if there are three output operands, use `%0' in the
+ template to refer to the first, `%1' for the second, and `%2' for
the third.
CONSTRAINT
A string constant specifying constraints on the placement of the
operand; *Note Constraints::, for details.
- Output constraints must begin with either '=' (a variable
- overwriting an existing value) or '+' (when reading and writing).
- When using '=', do not assume the location contains the existing
- value on entry to the 'asm', except when the operand is tied to an
+ Output constraints must begin with either `=' (a variable
+ overwriting an existing value) or `+' (when reading and writing).
+ When using `=', do not assume the location contains the existing
+ value on entry to the `asm', except when the operand is tied to an
input; *note Input Operands: InputOperands.
After the prefix, there must be one or more additional constraints
- (*note Constraints::) that describe where the value resides.
- Common constraints include 'r' for register and 'm' for memory.
- When you list more than one possible location (for example,
- '"=rm"'), the compiler chooses the most efficient one based on the
- current context. If you list as many alternates as the 'asm'
- statement allows, you permit the optimizers to produce the best
- possible code. If you must use a specific register, but your
- Machine Constraints do not provide sufficient control to select the
+ (*note Constraints::) that describe where the value resides. Common
+ constraints include `r' for register and `m' for memory. When you
+ list more than one possible location (for example, `"=rm"'), the
+ compiler chooses the most efficient one based on the current
+ context. If you list as many alternates as the `asm' statement
+ allows, you permit the optimizers to produce the best possible
+ code. If you must use a specific register, but your Machine
+ Constraints do not provide sufficient control to select the
specific register you want, local register variables may provide a
solution (*note Local Reg Vars::).
@@ -28854,55 +29076,56 @@ CVARIABLENAME
variable name. The enclosing parentheses are a required part of
the syntax.
+
When the compiler selects the registers to use to represent the output
operands, it does not use any of the clobbered registers (*note
Clobbers::).
- Output operand expressions must be lvalues. The compiler cannot check
+ Output operand expressions must be lvalues. The compiler cannot check
whether the operands have data types that are reasonable for the
-instruction being executed. For output expressions that are not
+instruction being executed. For output expressions that are not
directly addressable (for example a bit-field), the constraint must
-allow a register. In that case, GCC uses the register as the output of
-the 'asm', and then stores that register into the output.
+allow a register. In that case, GCC uses the register as the output of
+the `asm', and then stores that register into the output.
- Operands using the '+' constraint modifier count as two operands (that
+ Operands using the `+' constraint modifier count as two operands (that
is, both as input and output) towards the total maximum of 30 operands
-per 'asm' statement.
+per `asm' statement.
- Use the '&' constraint modifier (*note Modifiers::) on all output
+ Use the `&' constraint modifier (*note Modifiers::) on all output
operands that must not overlap an input. Otherwise, GCC may allocate
the output operand in the same register as an unrelated input operand,
on the assumption that the assembler code consumes its inputs before
-producing outputs. This assumption may be false if the assembler code
+producing outputs. This assumption may be false if the assembler code
actually consists of more than one instruction.
The same problem can occur if one output parameter (A) allows a
register constraint and another output parameter (B) allows a memory
-constraint. The code generated by GCC to access the memory address in B
-can contain registers which _might_ be shared by A, and GCC considers
-those registers to be inputs to the asm. As above, GCC assumes that
-such input registers are consumed before any outputs are written. This
+constraint. The code generated by GCC to access the memory address in
+B can contain registers which _might_ be shared by A, and GCC considers
+those registers to be inputs to the asm. As above, GCC assumes that
+such input registers are consumed before any outputs are written. This
assumption may result in incorrect behavior if the asm writes to A
-before using B. Combining the '&' modifier with the register constraint
+before using B. Combining the `&' modifier with the register constraint
on A ensures that modifying A does not affect the address referenced by
-B. Otherwise, the location of B is undefined if A is modified before
+B. Otherwise, the location of B is undefined if A is modified before
using B.
- 'asm' supports operand modifiers on operands (for example '%k2' instead
-of simply '%2'). Typically these qualifiers are hardware dependent.
-The list of supported modifiers for x86 is found at *note x86 Operand
-modifiers: x86Operandmodifiers.
+ `asm' supports operand modifiers on operands (for example `%k2'
+instead of simply `%2'). Typically these qualifiers are hardware
+dependent. The list of supported modifiers for x86 is found at *note
+x86 Operand modifiers: x86Operandmodifiers.
- If the C code that follows the 'asm' makes no use of any of the output
-operands, use 'volatile' for the 'asm' statement to prevent the
-optimizers from discarding the 'asm' statement as unneeded (see *note
+ If the C code that follows the `asm' makes no use of any of the output
+operands, use `volatile' for the `asm' statement to prevent the
+optimizers from discarding the `asm' statement as unneeded (see *note
Volatile::).
- This code makes no use of the optional ASMSYMBOLICNAME. Therefore it
-references the first output operand as '%0' (were there a second, it
-would be '%1', etc). The number of the first input operand is one
-greater than that of the last output operand. In this i386 example,
-that makes 'Mask' referenced as '%1':
+ This code makes no use of the optional ASMSYMBOLICNAME. Therefore it
+references the first output operand as `%0' (were there a second, it
+would be `%1', etc). The number of the first input operand is one
+greater than that of the last output operand. In this i386 example,
+that makes `Mask' referenced as `%1':
uint32_t Mask = 1234;
uint32_t Index;
@@ -28912,18 +29135,18 @@ that makes 'Mask' referenced as '%1':
: "r" (Mask)
: "cc");
- That code overwrites the variable 'Index' ('='), placing the value in a
-register ('r'). Using the generic 'r' constraint instead of a
+ That code overwrites the variable `Index' (`='), placing the value in
+a register (`r'). Using the generic `r' constraint instead of a
constraint for a specific register allows the compiler to pick the
-register to use, which can result in more efficient code. This may not
+register to use, which can result in more efficient code. This may not
be possible if an assembler instruction requires a specific register.
The following i386 example uses the ASMSYMBOLICNAME syntax. It
produces the same result as the code above, but some may consider it
-more readable or more maintainable since reordering index numbers is not
-necessary when adding or removing operands. The names 'aIndex' and
-'aMask' are only used in this example to emphasize which names get used
-where. It is acceptable to reuse the names 'Index' and 'Mask'.
+more readable or more maintainable since reordering index numbers is
+not necessary when adding or removing operands. The names `aIndex' and
+`aMask' are only used in this example to emphasize which names get used
+where. It is acceptable to reuse the names `Index' and `Mask'.
uint32_t Mask = 1234;
uint32_t Index;
@@ -28943,16 +29166,16 @@ where. It is acceptable to reuse the names 'Index' and 'Mask'.
: [d] "=rm" (d)
: [e] "rm" (*e));
- Here, 'd' may either be in a register or in memory. Since the compiler
-might already have the current value of the 'uint32_t' location pointed
-to by 'e' in a register, you can enable it to choose the best location
-for 'd' by specifying both constraints.
+ Here, `d' may either be in a register or in memory. Since the compiler
+might already have the current value of the `uint32_t' location pointed
+to by `e' in a register, you can enable it to choose the best location
+for `d' by specifying both constraints.
6.43.2.4 Input Operands
.......................
-Input operands make values from C variables and expressions available to
-the assembly code.
+Input operands make values from C variables and expressions available
+to the assembly code.
Operands are separated by commas. Each operand has this format:
@@ -28961,42 +29184,43 @@ the assembly code.
ASMSYMBOLICNAME
Specifies a symbolic name for the operand. Reference the name in
the assembler template by enclosing it in square brackets (i.e.
- '%[Value]'). The scope of the name is the 'asm' statement that
- contains the definition. Any valid C variable name is acceptable,
- including names already defined in the surrounding code. No two
- operands within the same 'asm' statement can use the same symbolic
+ `%[Value]'). The scope of the name is the `asm' statement that
+ contains the definition. Any valid C variable name is acceptable,
+ including names already defined in the surrounding code. No two
+ operands within the same `asm' statement can use the same symbolic
name.
- When not using an ASMSYMBOLICNAME, use the (zero-based) position of
- the operand in the list of operands in the assembler template. For
- example if there are two output operands and three inputs, use '%2'
- in the template to refer to the first input operand, '%3' for the
- second, and '%4' for the third.
+ When not using an ASMSYMBOLICNAME, use the (zero-based) position
+ of the operand in the list of operands in the assembler template.
+ For example if there are two output operands and three inputs, use
+ `%2' in the template to refer to the first input operand, `%3' for
+ the second, and `%4' for the third.
CONSTRAINT
A string constant specifying constraints on the placement of the
operand; *Note Constraints::, for details.
- Input constraint strings may not begin with either '=' or '+'.
+ Input constraint strings may not begin with either `=' or `+'.
When you list more than one possible location (for example,
- '"irm"'), the compiler chooses the most efficient one based on the
+ `"irm"'), the compiler chooses the most efficient one based on the
current context. If you must use a specific register, but your
- Machine Constraints do not provide sufficient control to select the
- specific register you want, local register variables may provide a
- solution (*note Local Reg Vars::).
+ Machine Constraints do not provide sufficient control to select
+ the specific register you want, local register variables may
+ provide a solution (*note Local Reg Vars::).
- Input constraints can also be digits (for example, '"0"'). This
- indicates that the specified input must be in the same place as the
- output constraint at the (zero-based) index in the output
+ Input constraints can also be digits (for example, `"0"'). This
+ indicates that the specified input must be in the same place as
+ the output constraint at the (zero-based) index in the output
constraint list. When using ASMSYMBOLICNAME syntax for the output
- operands, you may use these names (enclosed in brackets '[]')
+ operands, you may use these names (enclosed in brackets `[]')
instead of digits.
CEXPRESSION
- This is the C variable or expression being passed to the 'asm'
+ This is the C variable or expression being passed to the `asm'
statement as input. The enclosing parentheses are a required part
of the syntax.
+
When the compiler selects the registers to use to represent the input
operands, it does not use any of the clobbered registers (*note
Clobbers::).
@@ -29009,29 +29233,29 @@ consecutive colons where the output operands would go:
: "r" (Offset / 8));
*Warning:* Do _not_ modify the contents of input-only operands (except
-for inputs tied to outputs). The compiler assumes that on exit from the
-'asm' statement these operands contain the same values as they had
-before executing the statement. It is _not_ possible to use clobbers to
-inform the compiler that the values in these inputs are changing. One
+for inputs tied to outputs). The compiler assumes that on exit from the
+`asm' statement these operands contain the same values as they had
+before executing the statement. It is _not_ possible to use clobbers
+to inform the compiler that the values in these inputs are changing. One
common work-around is to tie the changing input variable to an output
-variable that never gets used. Note, however, that if the code that
-follows the 'asm' statement makes no use of any of the output operands,
-the GCC optimizers may discard the 'asm' statement as unneeded (see
+variable that never gets used. Note, however, that if the code that
+follows the `asm' statement makes no use of any of the output operands,
+the GCC optimizers may discard the `asm' statement as unneeded (see
*note Volatile::).
- 'asm' supports operand modifiers on operands (for example '%k2' instead
-of simply '%2'). Typically these qualifiers are hardware dependent.
-The list of supported modifiers for x86 is found at *note x86 Operand
-modifiers: x86Operandmodifiers.
+ `asm' supports operand modifiers on operands (for example `%k2'
+instead of simply `%2'). Typically these qualifiers are hardware
+dependent. The list of supported modifiers for x86 is found at *note
+x86 Operand modifiers: x86Operandmodifiers.
- In this example using the fictitious 'combine' instruction, the
-constraint '"0"' for input operand 1 says that it must occupy the same
-location as output operand 0. Only input operands may use numbers in
-constraints, and they must each refer to an output operand. Only a
+ In this example using the fictitious `combine' instruction, the
+constraint `"0"' for input operand 1 says that it must occupy the same
+location as output operand 0. Only input operands may use numbers in
+constraints, and they must each refer to an output operand. Only a
number (or the symbolic assembler name) in the constraint can guarantee
-that one operand is in the same place as another. The mere fact that
-'foo' is the value of both operands is not enough to guarantee that they
-are in the same place in the generated assembler code.
+that one operand is in the same place as another. The mere fact that
+`foo' is the value of both operands is not enough to guarantee that
+they are in the same place in the generated assembler code.
asm ("combine %2, %0"
: "=r" (foo)
@@ -29047,28 +29271,28 @@ are in the same place in the generated assembler code.
.................
While the compiler is aware of changes to entries listed in the output
-operands, the inline 'asm' code may modify more than just the outputs.
+operands, the inline `asm' code may modify more than just the outputs.
For example, calculations may require additional registers, or the
processor may overwrite a register as a side effect of a particular
assembler instruction. In order to inform the compiler of these
-changes, list them in the clobber list. Clobber list items are either
-register names or the special clobbers (listed below). Each clobber
+changes, list them in the clobber list. Clobber list items are either
+register names or the special clobbers (listed below). Each clobber
list item is a string constant enclosed in double quotes and separated
by commas.
Clobber descriptions may not in any way overlap with an input or output
-operand. For example, you may not have an operand describing a register
+operand. For example, you may not have an operand describing a register
class with one member when listing that register in the clobber list.
Variables declared to live in specific registers (*note Explicit Reg
-Vars::) and used as 'asm' input or output operands must have no part
-mentioned in the clobber description. In particular, there is no way to
-specify that input operands get modified without also specifying them as
-output operands.
-
- When the compiler selects which registers to use to represent input and
-output operands, it does not use any of the clobbered registers. As a
-result, clobbered registers are available for any use in the assembler
-code.
+Vars::) and used as `asm' input or output operands must have no part
+mentioned in the clobber description. In particular, there is no way to
+specify that input operands get modified without also specifying them
+as output operands.
+
+ When the compiler selects which registers to use to represent input
+and output operands, it does not use any of the clobbered registers. As
+a result, clobbered registers are available for any use in the
+assembler code.
Here is a realistic example for the VAX showing the use of clobbered
registers:
@@ -29080,70 +29304,72 @@ registers:
Also, there are two special clobber arguments:
-'"cc"'
- The '"cc"' clobber indicates that the assembler code modifies the
- flags register. On some machines, GCC represents the condition
- codes as a specific hardware register; '"cc"' serves to name this
+`"cc"'
+ The `"cc"' clobber indicates that the assembler code modifies the
+ flags register. On some machines, GCC represents the condition
+ codes as a specific hardware register; `"cc"' serves to name this
register. On other machines, condition code handling is different,
- and specifying '"cc"' has no effect. But it is valid no matter
+ and specifying `"cc"' has no effect. But it is valid no matter
what the target.
-'"memory"'
- The '"memory"' clobber tells the compiler that the assembly code
- performs memory reads or writes to items other than those listed in
- the input and output operands (for example, accessing the memory
- pointed to by one of the input parameters). To ensure memory
- contains correct values, GCC may need to flush specific register
- values to memory before executing the 'asm'. Further, the compiler
- does not assume that any values read from memory before an 'asm'
- remain unchanged after that 'asm'; it reloads them as needed.
- Using the '"memory"' clobber effectively forms a read/write memory
+`"memory"'
+ The `"memory"' clobber tells the compiler that the assembly code
+ performs memory reads or writes to items other than those listed
+ in the input and output operands (for example, accessing the
+ memory pointed to by one of the input parameters). To ensure
+ memory contains correct values, GCC may need to flush specific
+ register values to memory before executing the `asm'. Further, the
+ compiler does not assume that any values read from memory before an
+ `asm' remain unchanged after that `asm'; it reloads them as needed.
+ Using the `"memory"' clobber effectively forms a read/write memory
barrier for the compiler.
Note that this clobber does not prevent the _processor_ from doing
- speculative reads past the 'asm' statement. To prevent that, you
+ speculative reads past the `asm' statement. To prevent that, you
need processor-specific fence instructions.
Flushing registers to memory has performance implications and may
be an issue for time-sensitive code. You can use a trick to avoid
this if the size of the memory being accessed is known at compile
- time. For example, if accessing ten bytes of a string, use a
+ time. For example, if accessing ten bytes of a string, use a
memory input like:
- '{"m"( ({ struct { char x[10]; } *p = (void *)ptr ; *p; }) )}'.
+ `{"m"( ({ struct { char x[10]; } *p = (void *)ptr ; *p; }) )}'.
+
6.43.2.6 Goto Labels
....................
-'asm goto' allows assembly code to jump to one or more C labels. The
-GOTOLABELS section in an 'asm goto' statement contains a comma-separated
-list of all C labels to which the assembler code may jump. GCC assumes
-that 'asm' execution falls through to the next statement (if this is not
-the case, consider using the '__builtin_unreachable' intrinsic after the
-'asm' statement). Optimization of 'asm goto' may be improved by using
-the 'hot' and 'cold' label attributes (*note Label Attributes::).
+`asm goto' allows assembly code to jump to one or more C labels. The
+GOTOLABELS section in an `asm goto' statement contains a comma-separated
+list of all C labels to which the assembler code may jump. GCC assumes
+that `asm' execution falls through to the next statement (if this is
+not the case, consider using the `__builtin_unreachable' intrinsic
+after the `asm' statement). Optimization of `asm goto' may be improved
+by using the `hot' and `cold' label attributes (*note Label
+Attributes::).
- An 'asm goto' statement cannot have outputs. This is due to an
+ An `asm goto' statement cannot have outputs. This is due to an
internal restriction of the compiler: control transfer instructions
cannot have outputs. If the assembler code does modify anything, use
-the '"memory"' clobber to force the optimizers to flush all register
-values to memory and reload them if necessary after the 'asm' statement.
+the `"memory"' clobber to force the optimizers to flush all register
+values to memory and reload them if necessary after the `asm' statement.
- Also note that an 'asm goto' statement is always implicitly considered
+ Also note that an `asm goto' statement is always implicitly considered
volatile.
- To reference a label in the assembler template, prefix it with '%l'
-(lowercase 'L') followed by its (zero-based) position in GOTOLABELS plus
-the number of input operands. For example, if the 'asm' has three
-inputs and references two labels, refer to the first label as '%l3' and
-the second as '%l4').
+ To reference a label in the assembler template, prefix it with `%l'
+(lowercase `L') followed by its (zero-based) position in GOTOLABELS
+plus the number of input operands. For example, if the `asm' has three
+inputs and references two labels, refer to the first label as `%l3' and
+the second as `%l4').
Alternately, you can reference labels using the actual C label name
-enclosed in brackets. For example, to reference a label named 'carry',
-you can use '%l[carry]'. The label must still be listed in the
+enclosed in brackets. For example, to reference a label named `carry',
+you can use `%l[carry]'. The label must still be listed in the
GOTOLABELS section when using this approach.
- Here is an example of 'asm goto' for i386:
+ Here is an example of `asm goto' for i386:
asm goto (
"btl %1, %0\n\t"
@@ -29158,7 +29384,7 @@ GOTOLABELS section when using this approach.
carry:
return 1;
- The following example shows an 'asm goto' that uses a memory clobber.
+ The following example shows an `asm goto' that uses a memory clobber.
int frob(int x)
{
@@ -29177,9 +29403,9 @@ GOTOLABELS section when using this approach.
..............................
References to input, output, and goto operands in the assembler template
-of extended 'asm' statements can use modifiers to affect the way the
-operands are formatted in the code output to the assembler. For
-example, the following code uses the 'h' and 'b' modifiers for x86:
+of extended `asm' statements can use modifiers to affect the way the
+operands are formatted in the code output to the assembler. For
+example, the following code uses the `h' and `b' modifiers for x86:
uint16_t num;
asm volatile ("xchg %h0, %b0" : "+a" (num) );
@@ -29205,72 +29431,70 @@ purposes.
}
With no modifiers, this is what the output from the operands would be
-for the 'att' and 'intel' dialects of assembler:
+for the `att' and `intel' dialects of assembler:
Operand masm=att masm=intel
----------------------------------------
-'%0' '%eax' 'eax'
-'%1' '$2' '2'
-'%2' '$.L2' 'OFFSET
- FLAT:.L2'
+---------------------------------------
+`%0' `%eax' `eax'
+`%1' `$2' `2'
+`%2' `$.L2' `OFFSET FLAT:.L2'
The table below shows the list of supported modifiers and their
effects.
-Modifier Description Operand 'masm=att' 'masm=intel'
-------------------------------------------------------------------------------------------
-'z' Print the opcode suffix for the size of '%z0' 'l'
- the current integer operand (one of
- 'b'/'w'/'l'/'q').
-'b' Print the QImode name of the register. '%b0' '%al' 'al'
-'h' Print the QImode name for a "high" '%h0' '%ah' 'ah'
- register.
-'w' Print the HImode name of the register. '%w0' '%ax' 'ax'
-'k' Print the SImode name of the register. '%k0' '%eax' 'eax'
-'q' Print the DImode name of the register. '%q0' '%rax' 'rax'
-'l' Print the label name with no punctuation. '%l2' '.L2' '.L2'
-'c' Require a constant operand and print the '%c1' '2' '2'
- constant expression with no punctuation.
-
-6.43.2.8 x86 Floating-Point 'asm' Operands
+Modifier Description Operand `masm=att' `masm=intel'
+------------------------------------------------------------------------------------------
+`z' Print the opcode suffix for the size of the `%z0' `l'
+ current integer operand (one of
+ `b'/`w'/`l'/`q').
+`b' Print the QImode name of the register. `%b0' `%al' `al'
+`h' Print the QImode name for a "high" register. `%h0' `%ah' `ah'
+`w' Print the HImode name of the register. `%w0' `%ax' `ax'
+`k' Print the SImode name of the register. `%k0' `%eax' `eax'
+`q' Print the DImode name of the register. `%q0' `%rax' `rax'
+`l' Print the label name with no punctuation. `%l2' `.L2' `.L2'
+`c' Require a constant operand and print the `%c1' `2' `2'
+ constant expression with no punctuation.
+
+6.43.2.8 x86 Floating-Point `asm' Operands
..........................................
On x86 targets, there are several rules on the usage of stack-like
-registers in the operands of an 'asm'. These rules apply only to the
+registers in the operands of an `asm'. These rules apply only to the
operands that are stack-like registers:
- 1. Given a set of input registers that die in an 'asm', it is
- necessary to know which are implicitly popped by the 'asm', and
+ 1. Given a set of input registers that die in an `asm', it is
+ necessary to know which are implicitly popped by the `asm', and
which must be explicitly popped by GCC.
- An input register that is implicitly popped by the 'asm' must be
+ An input register that is implicitly popped by the `asm' must be
explicitly clobbered, unless it is constrained to match an output
operand.
- 2. For any input register that is implicitly popped by an 'asm', it is
+ 2. For any input register that is implicitly popped by an `asm', it is
necessary to know how to adjust the stack to compensate for the
- pop. If any non-popped input is closer to the top of the reg-stack
- than the implicitly popped register, it would not be possible to
- know what the stack looked like--it's not clear how the rest of the
- stack "slides up".
+ pop. If any non-popped input is closer to the top of the
+ reg-stack than the implicitly popped register, it would not be
+ possible to know what the stack looked like--it's not clear how
+ the rest of the stack "slides up".
All implicitly popped input registers must be closer to the top of
the reg-stack than any input that is not implicitly popped.
- It is possible that if an input dies in an 'asm', the compiler
+ It is possible that if an input dies in an `asm', the compiler
might use the input register for an output reload. Consider this
example:
asm ("foo" : "=t" (a) : "f" (b));
- This code says that input 'b' is not popped by the 'asm', and that
- the 'asm' pushes a result onto the reg-stack, i.e., the stack is
- one deeper after the 'asm' than it was before. But, it is possible
- that reload may think that it can use the same register for both
- the input and the output.
+ This code says that input `b' is not popped by the `asm', and that
+ the `asm' pushes a result onto the reg-stack, i.e., the stack is
+ one deeper after the `asm' than it was before. But, it is
+ possible that reload may think that it can use the same register
+ for both the input and the output.
- To prevent this from happening, if any input operand uses the 'f'
- constraint, all output register constraints must use the '&'
+ To prevent this from happening, if any input operand uses the `f'
+ constraint, all output register constraints must use the `&'
early-clobber modifier.
The example above is correctly written as:
@@ -29278,53 +29502,55 @@ operands that are stack-like registers:
asm ("foo" : "=&t" (a) : "f" (b));
3. Some operands need to be in particular places on the stack. All
- output operands fall in this category--GCC has no other way to know
- which registers the outputs appear in unless you indicate this in
- the constraints.
+ output operands fall in this category--GCC has no other way to
+ know which registers the outputs appear in unless you indicate
+ this in the constraints.
Output operands must specifically indicate which register an output
- appears in after an 'asm'. '=f' is not allowed: the operand
+ appears in after an `asm'. `=f' is not allowed: the operand
constraints must select a class with a single register.
4. Output operands may not be "inserted" between existing stack
registers. Since no 387 opcode uses a read/write operand, all
- output operands are dead before the 'asm', and are pushed by the
- 'asm'. It makes no sense to push anywhere but the top of the
+ output operands are dead before the `asm', and are pushed by the
+ `asm'. It makes no sense to push anywhere but the top of the
reg-stack.
Output operands must start at the top of the reg-stack: output
operands may not "skip" a register.
- 5. Some 'asm' statements may need extra stack space for internal
+ 5. Some `asm' statements may need extra stack space for internal
calculations. This can be guaranteed by clobbering stack registers
unrelated to the inputs and outputs.
- This 'asm' takes one input, which is internally popped, and produces
+
+ This `asm' takes one input, which is internally popped, and produces
two outputs.
asm ("fsincos" : "=t" (cos), "=u" (sin) : "0" (inp));
-This 'asm' takes two inputs, which are popped by the 'fyl2xp1' opcode,
-and replaces them with one output. The 'st(1)' clobber is necessary for
-the compiler to know that 'fyl2xp1' pops both inputs.
+This `asm' takes two inputs, which are popped by the `fyl2xp1' opcode,
+and replaces them with one output. The `st(1)' clobber is necessary
+for the compiler to know that `fyl2xp1' pops both inputs.
asm ("fyl2xp1" : "=t" (result) : "0" (x), "u" (y) : "st(1)");

File: gcc.info, Node: Constraints, Next: Asm Labels, Prev: Extended Asm, Up: Using Assembly Language with C
-6.43.3 Constraints for 'asm' Operands
+6.43.3 Constraints for `asm' Operands
-------------------------------------
Here are specific details on what constraint letters you can use with
-'asm' operands. Constraints can say whether an operand may be in a
+`asm' operands. Constraints can say whether an operand may be in a
register, and which kinds of register; whether the operand can be a
-memory reference, and which kinds of address; whether the operand may be
-an immediate constant, and which possible values it may have.
-Constraints can also require two operands to match. Side-effects aren't
-allowed in operands of inline 'asm', unless '<' or '>' constraints are
-used, because there is no guarantee that the side-effects will happen
-exactly once in an instruction that can update the addressing register.
+memory reference, and which kinds of address; whether the operand may
+be an immediate constant, and which possible values it may have.
+Constraints can also require two operands to match. Side-effects
+aren't allowed in operands of inline `asm', unless `<' or `>'
+constraints are used, because there is no guarantee that the
+side-effects will happen exactly once in an instruction that can update
+the addressing register.
* Menu:
@@ -29350,13 +29576,13 @@ whitespace
description even if they have different number of constraints and
modifiers.
-'m'
+`m'
A memory operand is allowed, with any kind of address that the
machine supports in general. Note that the letter used for the
- general memory constraint can be re-defined by a back end using the
- 'TARGET_MEM_CONSTRAINT' macro.
+ general memory constraint can be re-defined by a back end using
+ the `TARGET_MEM_CONSTRAINT' macro.
-'o'
+`o'
A memory operand is allowed, but only if the address is
"offsettable". This means that adding a small integer (actually,
the width in bytes of the operand, as determined by its machine
@@ -29372,110 +29598,112 @@ whitespace
on the other addressing modes that the machine supports.
Note that in an output operand which can be matched by another
- operand, the constraint letter 'o' is valid only when accompanied
- by both '<' (if the target machine has predecrement addressing) and
- '>' (if the target machine has preincrement addressing).
-
-'V'
- A memory operand that is not offsettable. In other words, anything
- that would fit the 'm' constraint but not the 'o' constraint.
-
-'<'
- A memory operand with autodecrement addressing (either predecrement
- or postdecrement) is allowed. In inline 'asm' this constraint is
- only allowed if the operand is used exactly once in an instruction
- that can handle the side-effects. Not using an operand with '<' in
- constraint string in the inline 'asm' pattern at all or using it in
- multiple instructions isn't valid, because the side-effects
- wouldn't be performed or would be performed more than once.
- Furthermore, on some targets the operand with '<' in constraint
- string must be accompanied by special instruction suffixes like
- '%U0' instruction suffix on PowerPC or '%P0' on IA-64.
-
-'>'
- A memory operand with autoincrement addressing (either preincrement
- or postincrement) is allowed. In inline 'asm' the same
- restrictions as for '<' apply.
-
-'r'
+ operand, the constraint letter `o' is valid only when accompanied
+ by both `<' (if the target machine has predecrement addressing)
+ and `>' (if the target machine has preincrement addressing).
+
+`V'
+ A memory operand that is not offsettable. In other words,
+ anything that would fit the `m' constraint but not the `o'
+ constraint.
+
+`<'
+ A memory operand with autodecrement addressing (either
+ predecrement or postdecrement) is allowed. In inline `asm' this
+ constraint is only allowed if the operand is used exactly once in
+ an instruction that can handle the side-effects. Not using an
+ operand with `<' in constraint string in the inline `asm' pattern
+ at all or using it in multiple instructions isn't valid, because
+ the side-effects wouldn't be performed or would be performed more
+ than once. Furthermore, on some targets the operand with `<' in
+ constraint string must be accompanied by special instruction
+ suffixes like `%U0' instruction suffix on PowerPC or `%P0' on
+ IA-64.
+
+`>'
+ A memory operand with autoincrement addressing (either
+ preincrement or postincrement) is allowed. In inline `asm' the
+ same restrictions as for `<' apply.
+
+`r'
A register operand is allowed provided that it is in a general
register.
-'i'
+`i'
An immediate integer operand (one with constant value) is allowed.
This includes symbolic constants whose values will be known only at
assembly time or later.
-'n'
+`n'
An immediate integer operand with a known numeric value is allowed.
Many systems cannot support assembly-time constants for operands
less than a word wide. Constraints for these operands should use
- 'n' rather than 'i'.
+ `n' rather than `i'.
-'I', 'J', 'K', ... 'P'
- Other letters in the range 'I' through 'P' may be defined in a
+`I', `J', `K', ... `P'
+ Other letters in the range `I' through `P' may be defined in a
machine-dependent fashion to permit immediate integer operands with
explicit integer values in specified ranges. For example, on the
- 68000, 'I' is defined to stand for the range of values 1 to 8.
+ 68000, `I' is defined to stand for the range of values 1 to 8.
This is the range permitted as a shift count in the shift
instructions.
-'E'
- An immediate floating operand (expression code 'const_double') is
+`E'
+ An immediate floating operand (expression code `const_double') is
allowed, but only if the target floating point format is the same
as that of the host machine (on which the compiler is running).
-'F'
- An immediate floating operand (expression code 'const_double' or
- 'const_vector') is allowed.
+`F'
+ An immediate floating operand (expression code `const_double' or
+ `const_vector') is allowed.
-'G', 'H'
- 'G' and 'H' may be defined in a machine-dependent fashion to permit
- immediate floating operands in particular ranges of values.
+`G', `H'
+ `G' and `H' may be defined in a machine-dependent fashion to
+ permit immediate floating operands in particular ranges of values.
-'s'
- An immediate integer operand whose value is not an explicit integer
- is allowed.
+`s'
+ An immediate integer operand whose value is not an explicit
+ integer is allowed.
This might appear strange; if an insn allows a constant operand
- with a value not known at compile time, it certainly must allow any
- known value. So why use 's' instead of 'i'? Sometimes it allows
- better code to be generated.
+ with a value not known at compile time, it certainly must allow
+ any known value. So why use `s' instead of `i'? Sometimes it
+ allows better code to be generated.
For example, on the 68000 in a fullword instruction it is possible
to use an immediate operand; but if the immediate value is between
-128 and 127, better code results from loading the value into a
- register and using the register. This is because the load into the
- register can be done with a 'moveq' instruction. We arrange for
- this to happen by defining the letter 'K' to mean "any integer
- outside the range -128 to 127", and then specifying 'Ks' in the
+ register and using the register. This is because the load into
+ the register can be done with a `moveq' instruction. We arrange
+ for this to happen by defining the letter `K' to mean "any integer
+ outside the range -128 to 127", and then specifying `Ks' in the
operand constraints.
-'g'
+`g'
Any register, memory or immediate integer operand is allowed,
except for registers that are not general registers.
-'X'
+`X'
Any operand whatsoever is allowed.
-'0', '1', '2', ... '9'
+`0', `1', `2', ... `9'
An operand that matches the specified operand number is allowed.
If a digit is used together with letters within the same
alternative, the digit should come last.
This number is allowed to be more than a single digit. If multiple
digits are encountered consecutively, they are interpreted as a
- single decimal integer. There is scant chance for ambiguity, since
- to-date it has never been desirable that '10' be interpreted as
- matching either operand 1 _or_ operand 0. Should this be desired,
- one can use multiple alternatives instead.
+ single decimal integer. There is scant chance for ambiguity,
+ since to-date it has never been desirable that `10' be interpreted
+ as matching either operand 1 _or_ operand 0. Should this be
+ desired, one can use multiple alternatives instead.
This is called a "matching constraint" and what it really means is
that the assembler has only a single operand that fills two roles
- which 'asm' distinguishes. For example, an add instruction uses
- two input operands and an output operand, but on most CISC machines
- an add instruction really has only two operands, one of them an
- input-output operand:
+ which `asm' distinguishes. For example, an add instruction uses
+ two input operands and an output operand, but on most CISC
+ machines an add instruction really has only two operands, one of
+ them an input-output operand:
addl #35,r12
@@ -29485,19 +29713,19 @@ whitespace
smaller number than the number of the operand that uses it in the
constraint.
-'p'
+`p'
An operand that is a valid memory address is allowed. This is for
"load address" and "push address" instructions.
- 'p' in the constraint must be accompanied by 'address_operand' as
- the predicate in the 'match_operand'. This predicate interprets
- the mode specified in the 'match_operand' as the mode of the memory
+ `p' in the constraint must be accompanied by `address_operand' as
+ the predicate in the `match_operand'. This predicate interprets
+ the mode specified in the `match_operand' as the mode of the memory
reference for which the address would be valid.
OTHER-LETTERS
Other letters can be defined in machine-dependent fashion to stand
for particular classes of registers or other arbitrary operand
- types. 'd', 'a' and 'f' are defined on the 68000/68020 to stand
+ types. `d', `a' and `f' are defined on the 68000/68020 to stand
for data, address and floating point registers.

@@ -29521,30 +29749,30 @@ alternative.
If all the operands fit any one alternative, the instruction is valid.
Otherwise, for each alternative, the compiler counts how many
-instructions must be added to copy the operands so that that alternative
-applies. The alternative requiring the least copying is chosen. If two
-alternatives need the same amount of copying, the one that comes first
-is chosen. These choices can be altered with the '?' and '!'
-characters:
-
-'?'
- Disparage slightly the alternative that the '?' appears in, as a
+instructions must be added to copy the operands so that that
+alternative applies. The alternative requiring the least copying is
+chosen. If two alternatives need the same amount of copying, the one
+that comes first is chosen. These choices can be altered with the `?'
+and `!' characters:
+
+`?'
+ Disparage slightly the alternative that the `?' appears in, as a
choice when no alternative applies exactly. The compiler regards
- this alternative as one unit more costly for each '?' that appears
+ this alternative as one unit more costly for each `?' that appears
in it.
-'!'
- Disparage severely the alternative that the '!' appears in. This
+`!'
+ Disparage severely the alternative that the `!' appears in. This
alternative can still be used if it fits without reloading, but if
reloading is needed, some other alternative will be used.
-'^'
- This constraint is analogous to '?' but it disparages slightly the
- alternative only if the operand with the '^' needs a reload.
+`^'
+ This constraint is analogous to `?' but it disparages slightly the
+ alternative only if the operand with the `^' needs a reload.
-'$'
- This constraint is analogous to '!' but it disparages severely the
- alternative only if the operand with the '$' needs a reload.
+`$'
+ This constraint is analogous to `!' but it disparages severely the
+ alternative only if the operand with the `$' needs a reload.

File: gcc.info, Node: Modifiers, Next: Machine Constraints, Prev: Multi-Alternative, Up: Constraints
@@ -29554,78 +29782,79 @@ File: gcc.info, Node: Modifiers, Next: Machine Constraints, Prev: Multi-Alter
Here are constraint modifier characters.
-'='
+`='
Means that this operand is written to by this instruction: the
previous value is discarded and replaced by new data.
-'+'
+`+'
Means that this operand is both read and written by the
instruction.
When the compiler fixes up the operands to satisfy the constraints,
it needs to know which operands are read by the instruction and
- which are written by it. '=' identifies an operand which is only
- written; '+' identifies an operand that is both read and written;
+ which are written by it. `=' identifies an operand which is only
+ written; `+' identifies an operand that is both read and written;
all other operands are assumed to only be read.
- If you specify '=' or '+' in a constraint, you put it in the first
+ If you specify `=' or `+' in a constraint, you put it in the first
character of the constraint string.
-'&'
+`&'
Means (in a particular alternative) that this operand is an
"earlyclobber" operand, which is written before the instruction is
- finished using the input operands. Therefore, this operand may not
- lie in a register that is read by the instruction or as part of any
- memory address.
+ finished using the input operands. Therefore, this operand may
+ not lie in a register that is read by the instruction or as part
+ of any memory address.
- '&' applies only to the alternative in which it is written. In
+ `&' applies only to the alternative in which it is written. In
constraints with multiple alternatives, sometimes one alternative
- requires '&' while others do not. See, for example, the 'movdf'
+ requires `&' while others do not. See, for example, the `movdf'
insn of the 68000.
A operand which is read by the instruction can be tied to an
earlyclobber operand if its only use as an input occurs before the
early result is written. Adding alternatives of this form often
allows GCC to produce better code when only some of the read
- operands can be affected by the earlyclobber. See, for example,
- the 'mulsi3' insn of the ARM.
+ operands can be affected by the earlyclobber. See, for example,
+ the `mulsi3' insn of the ARM.
Furthermore, if the "earlyclobber" operand is also a read/write
operand, then that operand is written only after it's used.
- '&' does not obviate the need to write '=' or '+'. As
+ `&' does not obviate the need to write `=' or `+'. As
"earlyclobber" operands are always written, a read-only
"earlyclobber" operand is ill-formed and will be rejected by the
compiler.
-'%'
+`%'
Declares the instruction to be commutative for this operand and the
following operand. This means that the compiler may interchange
the two operands if that is the cheapest way to make all operands
- fit the constraints. '%' applies to all alternatives and must
+ fit the constraints. `%' applies to all alternatives and must
appear as the first character in the constraint. Only read-only
- operands can use '%'.
+ operands can use `%'.
GCC can only handle one commutative pair in an asm; if you use
more, the compiler may fail. Note that you need not use the
- modifier if the two alternatives are strictly identical; this would
- only waste time in the reload pass. The modifier is not
+ modifier if the two alternatives are strictly identical; this
+ would only waste time in the reload pass. The modifier is not
operational after register allocation, so the result of
- 'define_peephole2' and 'define_split's performed after reload
- cannot rely on '%' to make the intended insn match.
+ `define_peephole2' and `define_split's performed after reload
+ cannot rely on `%' to make the intended insn match.
-'#'
+`#'
Says that all following characters, up to the next comma, are to be
ignored as a constraint. They are significant only for choosing
register preferences.
-'*'
+`*'
Says that the following character should be ignored when choosing
- register preferences. '*' has no effect on the meaning of the
+ register preferences. `*' has no effect on the meaning of the
constraint as a constraint, and no effect on reloading. For LRA
- '*' additionally disparages slightly the alternative if the
+ `*' additionally disparages slightly the alternative if the
following character matches the operand.
+

File: gcc.info, Node: Machine Constraints, Prev: Modifiers, Up: Constraints
@@ -29633,1454 +29862,1534 @@ File: gcc.info, Node: Machine Constraints, Prev: Modifiers, Up: Constraints
............................................
Whenever possible, you should use the general-purpose constraint letters
-in 'asm' arguments, since they will convey meaning more readily to
-people reading your code. Failing that, use the constraint letters that
-usually have very similar meanings across architectures. The most
-commonly used constraints are 'm' and 'r' (for memory and
+in `asm' arguments, since they will convey meaning more readily to
+people reading your code. Failing that, use the constraint letters
+that usually have very similar meanings across architectures. The most
+commonly used constraints are `m' and `r' (for memory and
general-purpose registers respectively; *note Simple Constraints::), and
-'I', usually the letter indicating the most common immediate-constant
+`I', usually the letter indicating the most common immediate-constant
format.
Each architecture defines additional constraints. These constraints
are used by the compiler itself for instruction generation, as well as
-for 'asm' statements; therefore, some of the constraints are not
-particularly useful for 'asm'. Here is a summary of some of the
+for `asm' statements; therefore, some of the constraints are not
+particularly useful for `asm'. Here is a summary of some of the
machine-dependent constraints available on some particular machines; it
-includes both constraints that are useful for 'asm' and constraints that
-aren't. The compiler source file mentioned in the table heading for
-each architecture is the definitive reference for the meanings of that
-architecture's constraints.
+includes both constraints that are useful for `asm' and constraints
+that aren't. The compiler source file mentioned in the table heading
+for each architecture is the definitive reference for the meanings of
+that architecture's constraints.
+
+_AArch64 family--`config/aarch64/constraints.md'_
-_AArch64 family--'config/aarch64/constraints.md'_
- 'k'
- The stack pointer register ('SP')
+ `k'
+ The stack pointer register (`SP')
- 'w'
+ `w'
Floating point or SIMD vector register
- 'I'
+ `I'
Integer constant that is valid as an immediate operand in an
- 'ADD' instruction
+ `ADD' instruction
- 'J'
+ `J'
Integer constant that is valid as an immediate operand in a
- 'SUB' instruction (once negated)
+ `SUB' instruction (once negated)
- 'K'
+ `K'
Integer constant that can be used with a 32-bit logical
instruction
- 'L'
+ `L'
Integer constant that can be used with a 64-bit logical
instruction
- 'M'
+ `M'
Integer constant that is valid as an immediate operand in a
- 32-bit 'MOV' pseudo instruction. The 'MOV' may be assembled
+ 32-bit `MOV' pseudo instruction. The `MOV' may be assembled
to one of several different machine instructions depending on
the value
- 'N'
+ `N'
Integer constant that is valid as an immediate operand in a
- 64-bit 'MOV' pseudo instruction
+ 64-bit `MOV' pseudo instruction
- 'S'
+ `S'
An absolute symbolic address or a label reference
- 'Y'
+ `Y'
Floating point constant zero
- 'Z'
+ `Z'
Integer constant zero
- 'Ush'
- The high part (bits 12 and upwards) of the pc-relative address
- of a symbol within 4GB of the instruction
+ `Ush'
+ The high part (bits 12 and upwards) of the pc-relative
+ address of a symbol within 4GB of the instruction
- 'Q'
+ `Q'
A memory address which uses a single base register with no
offset
- 'Ump'
- A memory address suitable for a load/store pair instruction in
- SI, DI, SF and DF modes
+ `Ump'
+ A memory address suitable for a load/store pair instruction
+ in SI, DI, SF and DF modes
+
-_ARC --'config/arc/constraints.md'_
- 'q'
- Registers usable in ARCompact 16-bit instructions: 'r0'-'r3',
- 'r12'-'r15'. This constraint can only match when the '-mq'
+_ARC --`config/arc/constraints.md'_
+
+ `q'
+ Registers usable in ARCompact 16-bit instructions: `r0'-`r3',
+ `r12'-`r15'. This constraint can only match when the `-mq'
option is in effect.
- 'e'
- Registers usable as base-regs of memory addresses in ARCompact
- 16-bit memory instructions: 'r0'-'r3', 'r12'-'r15', 'sp'.
- This constraint can only match when the '-mq' option is in
- effect.
- 'D'
- ARC FPX (dpfp) 64-bit registers. 'D0', 'D1'.
+ `e'
+ Registers usable as base-regs of memory addresses in
+ ARCompact 16-bit memory instructions: `r0'-`r3', `r12'-`r15',
+ `sp'. This constraint can only match when the `-mq' option
+ is in effect.
+
+ `D'
+ ARC FPX (dpfp) 64-bit registers. `D0', `D1'.
- 'I'
+ `I'
A signed 12-bit integer constant.
- 'Cal'
- constant for arithmetic/logical operations. This might be any
- constant that can be put into a long immediate by the assmbler
- or linker without involving a PIC relocation.
+ `Cal'
+ constant for arithmetic/logical operations. This might be
+ any constant that can be put into a long immediate by the
+ assmbler or linker without involving a PIC relocation.
- 'K'
+ `K'
A 3-bit unsigned integer constant.
- 'L'
+ `L'
A 6-bit unsigned integer constant.
- 'CnL'
+ `CnL'
One's complement of a 6-bit unsigned integer constant.
- 'CmL'
+ `CmL'
Two's complement of a 6-bit unsigned integer constant.
- 'M'
+ `M'
A 5-bit unsigned integer constant.
- 'O'
+ `O'
A 7-bit unsigned integer constant.
- 'P'
+ `P'
A 8-bit unsigned integer constant.
- 'H'
+ `H'
Any const_double value.
-_ARM family--'config/arm/constraints.md'_
+_ARM family--`config/arm/constraints.md'_
- 'h'
- In Thumb state, the core registers 'r8'-'r15'.
+ `h'
+ In Thumb state, the core registers `r8'-`r15'.
- 'k'
+ `k'
The stack pointer register.
- 'l'
- In Thumb State the core registers 'r0'-'r7'. In ARM state
- this is an alias for the 'r' constraint.
+ `l'
+ In Thumb State the core registers `r0'-`r7'. In ARM state
+ this is an alias for the `r' constraint.
- 't'
- VFP floating-point registers 's0'-'s31'. Used for 32 bit
+ `t'
+ VFP floating-point registers `s0'-`s31'. Used for 32 bit
values.
- 'w'
- VFP floating-point registers 'd0'-'d31' and the appropriate
- subset 'd0'-'d15' based on command line options. Used for 64
+ `w'
+ VFP floating-point registers `d0'-`d31' and the appropriate
+ subset `d0'-`d15' based on command line options. Used for 64
bit values only. Not valid for Thumb1.
- 'y'
+ `y'
The iWMMX co-processor registers.
- 'z'
+ `z'
The iWMMX GR registers.
- 'G'
+ `G'
The floating-point constant 0.0
- 'I'
+ `I'
Integer that is valid as an immediate operand in a data
- processing instruction. That is, an integer in the range 0 to
- 255 rotated by a multiple of 2
+ processing instruction. That is, an integer in the range 0
+ to 255 rotated by a multiple of 2
- 'J'
+ `J'
Integer in the range -4095 to 4095
- 'K'
- Integer that satisfies constraint 'I' when inverted (ones
+ `K'
+ Integer that satisfies constraint `I' when inverted (ones
complement)
- 'L'
- Integer that satisfies constraint 'I' when negated (twos
+ `L'
+ Integer that satisfies constraint `I' when negated (twos
complement)
- 'M'
+ `M'
Integer in the range 0 to 32
- 'Q'
+ `Q'
A memory reference where the exact address is in a single
- register (''m'' is preferable for 'asm' statements)
+ register (``m'' is preferable for `asm' statements)
- 'R'
+ `R'
An item in the constant pool
- 'S'
+ `S'
A symbol in the text segment of the current file
- 'Uv'
+ `Uv'
A memory reference suitable for VFP load/store insns
(reg+constant offset)
- 'Uy'
+ `Uy'
A memory reference suitable for iWMMXt load/store
instructions.
- 'Uq'
+ `Uq'
A memory reference suitable for the ARMv4 ldrsb instruction.
-_AVR family--'config/avr/constraints.md'_
- 'l'
+_AVR family--`config/avr/constraints.md'_
+
+ `l'
Registers from r0 to r15
- 'a'
+ `a'
Registers from r16 to r23
- 'd'
+ `d'
Registers from r16 to r31
- 'w'
+ `w'
Registers from r24 to r31. These registers can be used in
- 'adiw' command
+ `adiw' command
- 'e'
+ `e'
Pointer register (r26-r31)
- 'b'
+ `b'
Base pointer register (r28-r31)
- 'q'
+ `q'
Stack pointer register (SPH:SPL)
- 't'
+ `t'
Temporary register r0
- 'x'
+ `x'
Register pair X (r27:r26)
- 'y'
+ `y'
Register pair Y (r29:r28)
- 'z'
+ `z'
Register pair Z (r31:r30)
- 'I'
+ `I'
Constant greater than -1, less than 64
- 'J'
+ `J'
Constant greater than -64, less than 1
- 'K'
+ `K'
Constant integer 2
- 'L'
+ `L'
Constant integer 0
- 'M'
+ `M'
Constant that fits in 8 bits
- 'N'
+ `N'
Constant integer -1
- 'O'
+ `O'
Constant integer 8, 16, or 24
- 'P'
+ `P'
Constant integer 1
- 'G'
+ `G'
A floating point constant 0.0
- 'Q'
+ `Q'
A memory address based on Y or Z pointer with displacement.
-_Blackfin family--'config/bfin/constraints.md'_
- 'a'
+_Blackfin family--`config/bfin/constraints.md'_
+
+ `a'
P register
- 'd'
+ `d'
D register
- 'z'
+ `z'
A call clobbered P register.
- 'qN'
+ `qN'
A single register. If N is in the range 0 to 7, the
- corresponding D register. If it is 'A', then the register P0.
+ corresponding D register. If it is `A', then the register P0.
- 'D'
+ `D'
Even-numbered D register
- 'W'
+ `W'
Odd-numbered D register
- 'e'
+ `e'
Accumulator register.
- 'A'
+ `A'
Even-numbered accumulator register.
- 'B'
+ `B'
Odd-numbered accumulator register.
- 'b'
+ `b'
I register
- 'v'
+ `v'
B register
- 'f'
+ `f'
M register
- 'c'
- Registers used for circular buffering, i.e. I, B, or L
+ `c'
+ Registers used for circular buffering, i.e. I, B, or L
registers.
- 'C'
+ `C'
The CC register.
- 't'
+ `t'
LT0 or LT1.
- 'k'
+ `k'
LC0 or LC1.
- 'u'
+ `u'
LB0 or LB1.
- 'x'
+ `x'
Any D, P, B, M, I or L register.
- 'y'
+ `y'
Additional registers typically used only in prologues and
epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and
USP.
- 'w'
+ `w'
Any register except accumulators or CC.
- 'Ksh'
+ `Ksh'
Signed 16 bit integer (in the range -32768 to 32767)
- 'Kuh'
+ `Kuh'
Unsigned 16 bit integer (in the range 0 to 65535)
- 'Ks7'
+ `Ks7'
Signed 7 bit integer (in the range -64 to 63)
- 'Ku7'
+ `Ku7'
Unsigned 7 bit integer (in the range 0 to 127)
- 'Ku5'
+ `Ku5'
Unsigned 5 bit integer (in the range 0 to 31)
- 'Ks4'
+ `Ks4'
Signed 4 bit integer (in the range -8 to 7)
- 'Ks3'
+ `Ks3'
Signed 3 bit integer (in the range -3 to 4)
- 'Ku3'
+ `Ku3'
Unsigned 3 bit integer (in the range 0 to 7)
- 'PN'
+ `PN'
Constant N, where N is a single-digit constant in the range 0
to 4.
- 'PA'
+ `PA'
An integer equal to one of the MACFLAG_XXX constants that is
suitable for use with either accumulator.
- 'PB'
+ `PB'
An integer equal to one of the MACFLAG_XXX constants that is
suitable for use only with accumulator A1.
- 'M1'
+ `M1'
Constant 255.
- 'M2'
+ `M2'
Constant 65535.
- 'J'
+ `J'
An integer constant with exactly a single bit set.
- 'L'
+ `L'
An integer constant with all bits set except exactly one.
- 'H'
+ `H'
- 'Q'
+ `Q'
Any SYMBOL_REF.
-_CR16 Architecture--'config/cr16/cr16.h'_
+_CR16 Architecture--`config/cr16/cr16.h'_
- 'b'
+ `b'
Registers from r0 to r14 (registers without stack pointer)
- 't'
+ `t'
Register from r0 to r11 (all 16-bit registers)
- 'p'
+ `p'
Register from r12 to r15 (all 32-bit registers)
- 'I'
+ `I'
Signed constant that fits in 4 bits
- 'J'
+ `J'
Signed constant that fits in 5 bits
- 'K'
+ `K'
Signed constant that fits in 6 bits
- 'L'
+ `L'
Unsigned constant that fits in 4 bits
- 'M'
+ `M'
Signed constant that fits in 32 bits
- 'N'
+ `N'
Check for 64 bits wide constants for add/sub instructions
- 'G'
+ `G'
Floating point constant that is legal for store immediate
-_Epiphany--'config/epiphany/constraints.md'_
- 'U16'
+_Epiphany--`config/epiphany/constraints.md'_
+
+ `U16'
An unsigned 16-bit constant.
- 'K'
+ `K'
An unsigned 5-bit constant.
- 'L'
+ `L'
A signed 11-bit constant.
- 'Cm1'
- A signed 11-bit constant added to -1. Can only match when the
- '-m1reg-REG' option is active.
+ `Cm1'
+ A signed 11-bit constant added to -1. Can only match when
+ the `-m1reg-REG' option is active.
- 'Cl1'
+ `Cl1'
Left-shift of -1, i.e., a bit mask with a block of leading
ones, the rest being a block of trailing zeroes. Can only
- match when the '-m1reg-REG' option is active.
+ match when the `-m1reg-REG' option is active.
- 'Cr1'
+ `Cr1'
Right-shift of -1, i.e., a bit mask with a trailing block of
ones, the rest being zeroes. Or to put it another way, one
less than a power of two. Can only match when the
- '-m1reg-REG' option is active.
+ `-m1reg-REG' option is active.
- 'Cal'
- Constant for arithmetic/logical operations. This is like 'i',
- except that for position independent code, no symbols /
+ `Cal'
+ Constant for arithmetic/logical operations. This is like
+ `i', except that for position independent code, no symbols /
expressions needing relocations are allowed.
- 'Csy'
+ `Csy'
Symbolic constant for call/jump instruction.
- 'Rcs'
+ `Rcs'
The register class usable in short insns. This is a register
class constraint, and can thus drive register allocation.
- This constraint won't match unless '-mprefer-short-insn-regs'
+ This constraint won't match unless `-mprefer-short-insn-regs'
is in effect.
- 'Rsc'
+ `Rsc'
The the register class of registers that can be used to hold a
sibcall call address. I.e., a caller-saved register.
- 'Rct'
+ `Rct'
Core control register class.
- 'Rgs'
+ `Rgs'
The register group usable in short insns. This constraint
does not use a register class, so that it only passively
matches suitable registers, and doesn't drive register
allocation.
- 'Rra'
- Matches the return address if it can be replaced with the link
- register.
+ `Rra'
+ Matches the return address if it can be replaced with the
+ link register.
- 'Rcc'
+ `Rcc'
Matches the integer condition code register.
- 'Sra'
+ `Sra'
Matches the return address if it is in a stack slot.
- 'Cfm'
+ `Cfm'
Matches control register values to switch fp mode, which are
- encapsulated in 'UNSPEC_FP_MODE'.
+ encapsulated in `UNSPEC_FP_MODE'.
-_FRV--'config/frv/frv.h'_
- 'a'
- Register in the class 'ACC_REGS' ('acc0' to 'acc7').
+_FRV--`config/frv/frv.h'_
- 'b'
- Register in the class 'EVEN_ACC_REGS' ('acc0' to 'acc7').
+ `a'
+ Register in the class `ACC_REGS' (`acc0' to `acc7').
- 'c'
- Register in the class 'CC_REGS' ('fcc0' to 'fcc3' and 'icc0'
- to 'icc3').
+ `b'
+ Register in the class `EVEN_ACC_REGS' (`acc0' to `acc7').
- 'd'
- Register in the class 'GPR_REGS' ('gr0' to 'gr63').
+ `c'
+ Register in the class `CC_REGS' (`fcc0' to `fcc3' and `icc0'
+ to `icc3').
- 'e'
- Register in the class 'EVEN_REGS' ('gr0' to 'gr63'). Odd
- registers are excluded not in the class but through the use of
- a machine mode larger than 4 bytes.
+ `d'
+ Register in the class `GPR_REGS' (`gr0' to `gr63').
- 'f'
- Register in the class 'FPR_REGS' ('fr0' to 'fr63').
+ `e'
+ Register in the class `EVEN_REGS' (`gr0' to `gr63'). Odd
+ registers are excluded not in the class but through the use
+ of a machine mode larger than 4 bytes.
- 'h'
- Register in the class 'FEVEN_REGS' ('fr0' to 'fr63'). Odd
- registers are excluded not in the class but through the use of
- a machine mode larger than 4 bytes.
+ `f'
+ Register in the class `FPR_REGS' (`fr0' to `fr63').
- 'l'
- Register in the class 'LR_REG' (the 'lr' register).
+ `h'
+ Register in the class `FEVEN_REGS' (`fr0' to `fr63'). Odd
+ registers are excluded not in the class but through the use
+ of a machine mode larger than 4 bytes.
- 'q'
- Register in the class 'QUAD_REGS' ('gr2' to 'gr63'). Register
- numbers not divisible by 4 are excluded not in the class but
- through the use of a machine mode larger than 8 bytes.
+ `l'
+ Register in the class `LR_REG' (the `lr' register).
- 't'
- Register in the class 'ICC_REGS' ('icc0' to 'icc3').
+ `q'
+ Register in the class `QUAD_REGS' (`gr2' to `gr63').
+ Register numbers not divisible by 4 are excluded not in the
+ class but through the use of a machine mode larger than 8
+ bytes.
+
+ `t'
+ Register in the class `ICC_REGS' (`icc0' to `icc3').
- 'u'
- Register in the class 'FCC_REGS' ('fcc0' to 'fcc3').
+ `u'
+ Register in the class `FCC_REGS' (`fcc0' to `fcc3').
- 'v'
- Register in the class 'ICR_REGS' ('cc4' to 'cc7').
+ `v'
+ Register in the class `ICR_REGS' (`cc4' to `cc7').
- 'w'
- Register in the class 'FCR_REGS' ('cc0' to 'cc3').
+ `w'
+ Register in the class `FCR_REGS' (`cc0' to `cc3').
- 'x'
- Register in the class 'QUAD_FPR_REGS' ('fr0' to 'fr63').
+ `x'
+ Register in the class `QUAD_FPR_REGS' (`fr0' to `fr63').
Register numbers not divisible by 4 are excluded not in the
class but through the use of a machine mode larger than 8
bytes.
- 'z'
- Register in the class 'SPR_REGS' ('lcr' and 'lr').
+ `z'
+ Register in the class `SPR_REGS' (`lcr' and `lr').
- 'A'
- Register in the class 'QUAD_ACC_REGS' ('acc0' to 'acc7').
+ `A'
+ Register in the class `QUAD_ACC_REGS' (`acc0' to `acc7').
- 'B'
- Register in the class 'ACCG_REGS' ('accg0' to 'accg7').
+ `B'
+ Register in the class `ACCG_REGS' (`accg0' to `accg7').
- 'C'
- Register in the class 'CR_REGS' ('cc0' to 'cc7').
+ `C'
+ Register in the class `CR_REGS' (`cc0' to `cc7').
- 'G'
+ `G'
Floating point constant zero
- 'I'
+ `I'
6-bit signed integer constant
- 'J'
+ `J'
10-bit signed integer constant
- 'L'
+ `L'
16-bit signed integer constant
- 'M'
+ `M'
16-bit unsigned integer constant
- 'N'
+ `N'
12-bit signed integer constant that is negative--i.e. in the
range of -2048 to -1
- 'O'
+ `O'
Constant zero
- 'P'
- 12-bit signed integer constant that is greater than zero--i.e.
- in the range of 1 to 2047.
+ `P'
+ 12-bit signed integer constant that is greater than
+ zero--i.e. in the range of 1 to 2047.
-_Hewlett-Packard PA-RISC--'config/pa/pa.h'_
- 'a'
+
+_Hewlett-Packard PA-RISC--`config/pa/pa.h'_
+
+ `a'
General register 1
- 'f'
+ `f'
Floating point register
- 'q'
+ `q'
Shift amount register
- 'x'
+ `x'
Floating point register (deprecated)
- 'y'
+ `y'
Upper floating point register (32-bit), floating point
register (64-bit)
- 'Z'
+ `Z'
Any register
- 'I'
+ `I'
Signed 11-bit integer constant
- 'J'
+ `J'
Signed 14-bit integer constant
- 'K'
- Integer constant that can be deposited with a 'zdepi'
+ `K'
+ Integer constant that can be deposited with a `zdepi'
instruction
- 'L'
+ `L'
Signed 5-bit integer constant
- 'M'
+ `M'
Integer constant 0
- 'N'
- Integer constant that can be loaded with a 'ldil' instruction
+ `N'
+ Integer constant that can be loaded with a `ldil' instruction
- 'O'
+ `O'
Integer constant whose value plus one is a power of 2
- 'P'
- Integer constant that can be used for 'and' operations in
- 'depi' and 'extru' instructions
+ `P'
+ Integer constant that can be used for `and' operations in
+ `depi' and `extru' instructions
- 'S'
+ `S'
Integer constant 31
- 'U'
+ `U'
Integer constant 63
- 'G'
+ `G'
Floating-point constant 0.0
- 'A'
- A 'lo_sum' data-linkage-table memory operand
+ `A'
+ A `lo_sum' data-linkage-table memory operand
- 'Q'
+ `Q'
A memory operand that can be used as the destination operand
of an integer store instruction
- 'R'
+ `R'
A scaled or unscaled indexed memory operand
- 'T'
+ `T'
A memory operand for floating-point loads and stores
- 'W'
+ `W'
A register indirect memory operand
-_Intel IA-64--'config/ia64/ia64.h'_
- 'a'
- General register 'r0' to 'r3' for 'addl' instruction
+_Intel IA-64--`config/ia64/ia64.h'_
+
+ `a'
+ General register `r0' to `r3' for `addl' instruction
- 'b'
+ `b'
Branch register
- 'c'
- Predicate register ('c' as in "conditional")
+ `c'
+ Predicate register (`c' as in "conditional")
- 'd'
+ `d'
Application register residing in M-unit
- 'e'
+ `e'
Application register residing in I-unit
- 'f'
+ `f'
Floating-point register
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement and postdecrement which require
- printing with '%Pn' on IA-64.
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement and postdecrement which
+ require printing with `%Pn' on IA-64.
- 'G'
+ `G'
Floating-point constant 0.0 or 1.0
- 'I'
+ `I'
14-bit signed integer constant
- 'J'
+ `J'
22-bit signed integer constant
- 'K'
+ `K'
8-bit signed integer constant for logical instructions
- 'L'
+ `L'
8-bit adjusted signed integer constant for compare pseudo-ops
- 'M'
+ `M'
6-bit unsigned integer constant for shift counts
- 'N'
+ `N'
9-bit signed integer constant for load and store
postincrements
- 'O'
+ `O'
The constant zero
- 'P'
- 0 or -1 for 'dep' instruction
+ `P'
+ 0 or -1 for `dep' instruction
- 'Q'
+ `Q'
Non-volatile memory for floating-point loads and stores
- 'R'
- Integer constant in the range 1 to 4 for 'shladd' instruction
+ `R'
+ Integer constant in the range 1 to 4 for `shladd' instruction
- 'S'
+ `S'
Memory operand except postincrement and postdecrement. This
- is now roughly the same as 'm' when not used together with '<'
- or '>'.
+ is now roughly the same as `m' when not used together with `<'
+ or `>'.
-_M32C--'config/m32c/m32c.c'_
- 'Rsp'
- 'Rfb'
- 'Rsb'
- '$sp', '$fb', '$sb'.
+_M32C--`config/m32c/m32c.c'_
- 'Rcr'
+ `Rsp'
+ `Rfb'
+ `Rsb'
+ `$sp', `$fb', `$sb'.
+
+ `Rcr'
Any control register, when they're 16 bits wide (nothing if
control registers are 24 bits wide)
- 'Rcl'
+ `Rcl'
Any control register, when they're 24 bits wide.
- 'R0w'
- 'R1w'
- 'R2w'
- 'R3w'
+ `R0w'
+ `R1w'
+ `R2w'
+ `R3w'
$r0, $r1, $r2, $r3.
- 'R02'
+ `R02'
$r0 or $r2, or $r2r0 for 32 bit values.
- 'R13'
+ `R13'
$r1 or $r3, or $r3r1 for 32 bit values.
- 'Rdi'
+ `Rdi'
A register that can hold a 64 bit value.
- 'Rhl'
+ `Rhl'
$r0 or $r1 (registers with addressable high/low bytes)
- 'R23'
+ `R23'
$r2 or $r3
- 'Raa'
+ `Raa'
Address registers
- 'Raw'
+ `Raw'
Address registers when they're 16 bits wide.
- 'Ral'
+ `Ral'
Address registers when they're 24 bits wide.
- 'Rqi'
+ `Rqi'
Registers that can hold QI values.
- 'Rad'
+ `Rad'
Registers that can be used with displacements ($a0, $a1, $sb).
- 'Rsi'
+ `Rsi'
Registers that can hold 32 bit values.
- 'Rhi'
+ `Rhi'
Registers that can hold 16 bit values.
- 'Rhc'
+ `Rhc'
Registers chat can hold 16 bit values, including all control
registers.
- 'Rra'
+ `Rra'
$r0 through R1, plus $a0 and $a1.
- 'Rfl'
+ `Rfl'
The flags register.
- 'Rmm'
+ `Rmm'
The memory-based pseudo-registers $mem0 through $mem15.
- 'Rpi'
+ `Rpi'
Registers that can hold pointers (16 bit registers for r8c,
m16c; 24 bit registers for m32cm, m32c).
- 'Rpa'
+ `Rpa'
Matches multiple registers in a PARALLEL to form a larger
register. Used to match function return values.
- 'Is3'
+ `Is3'
-8 ... 7
- 'IS1'
+ `IS1'
-128 ... 127
- 'IS2'
+ `IS2'
-32768 ... 32767
- 'IU2'
+ `IU2'
0 ... 65535
- 'In4'
+ `In4'
-8 ... -1 or 1 ... 8
- 'In5'
+ `In5'
-16 ... -1 or 1 ... 16
- 'In6'
+ `In6'
-32 ... -1 or 1 ... 32
- 'IM2'
+ `IM2'
-65536 ... -1
- 'Ilb'
+ `Ilb'
An 8 bit value with exactly one bit set.
- 'Ilw'
+ `Ilw'
A 16 bit value with exactly one bit set.
- 'Sd'
+ `Sd'
The common src/dest memory addressing modes.
- 'Sa'
+ `Sa'
Memory addressed using $a0 or $a1.
- 'Si'
+ `Si'
Memory addressed with immediate addresses.
- 'Ss'
+ `Ss'
Memory addressed using the stack pointer ($sp).
- 'Sf'
+ `Sf'
Memory addressed using the frame base register ($fb).
- 'Ss'
+ `Ss'
Memory addressed using the small base register ($sb).
- 'S1'
+ `S1'
$r1h
-_MeP--'config/mep/constraints.md'_
+_MeP--`config/mep/constraints.md'_
- 'a'
+ `a'
The $sp register.
- 'b'
+ `b'
The $tp register.
- 'c'
+ `c'
Any control register.
- 'd'
+ `d'
Either the $hi or the $lo register.
- 'em'
+ `em'
Coprocessor registers that can be directly loaded ($c0-$c15).
- 'ex'
+ `ex'
Coprocessor registers that can be moved to each other.
- 'er'
+ `er'
Coprocessor registers that can be moved to core registers.
- 'h'
+ `h'
The $hi register.
- 'j'
+ `j'
The $rpc register.
- 'l'
+ `l'
The $lo register.
- 't'
+ `t'
Registers which can be used in $tp-relative addressing.
- 'v'
+ `v'
The $gp register.
- 'x'
+ `x'
The coprocessor registers.
- 'y'
+ `y'
The coprocessor control registers.
- 'z'
+ `z'
The $0 register.
- 'A'
+ `A'
User-defined register set A.
- 'B'
+ `B'
User-defined register set B.
- 'C'
+ `C'
User-defined register set C.
- 'D'
+ `D'
User-defined register set D.
- 'I'
+ `I'
Offsets for $gp-rel addressing.
- 'J'
+ `J'
Constants that can be used directly with boolean insns.
- 'K'
+ `K'
Constants that can be moved directly to registers.
- 'L'
+ `L'
Small constants that can be added to registers.
- 'M'
+ `M'
Long shift counts.
- 'N'
+ `N'
Small constants that can be compared to registers.
- 'O'
+ `O'
Constants that can be loaded into the top half of registers.
- 'S'
+ `S'
Signed 8-bit immediates.
- 'T'
+ `T'
Symbols encoded for $tp-rel or $gp-rel addressing.
- 'U'
+ `U'
Non-constant addresses for loading/saving coprocessor
registers.
- 'W'
+ `W'
The top half of a symbol's value.
- 'Y'
+ `Y'
A register indirect address without offset.
- 'Z'
+ `Z'
Symbolic references to the control bus.
-_MicroBlaze--'config/microblaze/constraints.md'_
- 'd'
- A general register ('r0' to 'r31').
- 'z'
- A status register ('rmsr', '$fcc1' to '$fcc7').
+_MicroBlaze--`config/microblaze/constraints.md'_
+
+ `d'
+ A general register (`r0' to `r31').
+
+ `z'
+ A status register (`rmsr', `$fcc1' to `$fcc7').
+
-_MIPS--'config/mips/constraints.md'_
- 'd'
- An address register. This is equivalent to 'r' unless
+_MIPS--`config/mips/constraints.md'_
+
+ `d'
+ An address register. This is equivalent to `r' unless
generating MIPS16 code.
- 'f'
+ `f'
A floating-point register (if available).
- 'h'
- Formerly the 'hi' register. This constraint is no longer
+ `h'
+ Formerly the `hi' register. This constraint is no longer
supported.
- 'l'
- The 'lo' register. Use this register to store values that are
+ `l'
+ The `lo' register. Use this register to store values that are
no bigger than a word.
- 'x'
- The concatenated 'hi' and 'lo' registers. Use this register
+ `x'
+ The concatenated `hi' and `lo' registers. Use this register
to store doubleword values.
- 'c'
+ `c'
A register suitable for use in an indirect jump. This will
- always be '$25' for '-mabicalls'.
+ always be `$25' for `-mabicalls'.
- 'v'
- Register '$3'. Do not use this constraint in new code; it is
+ `v'
+ Register `$3'. Do not use this constraint in new code; it is
retained only for compatibility with glibc.
- 'y'
- Equivalent to 'r'; retained for backwards compatibility.
+ `y'
+ Equivalent to `r'; retained for backwards compatibility.
- 'z'
+ `z'
A floating-point condition code register.
- 'I'
+ `I'
A signed 16-bit constant (for arithmetic instructions).
- 'J'
+ `J'
Integer zero.
- 'K'
+ `K'
An unsigned 16-bit constant (for logic instructions).
- 'L'
+ `L'
A signed 32-bit constant in which the lower 16 bits are zero.
- Such constants can be loaded using 'lui'.
+ Such constants can be loaded using `lui'.
- 'M'
- A constant that cannot be loaded using 'lui', 'addiu' or
- 'ori'.
+ `M'
+ A constant that cannot be loaded using `lui', `addiu' or
+ `ori'.
- 'N'
+ `N'
A constant in the range -65535 to -1 (inclusive).
- 'O'
+ `O'
A signed 15-bit constant.
- 'P'
+ `P'
A constant in the range 1 to 65535 (inclusive).
- 'G'
+ `G'
Floating-point zero.
- 'R'
+ `R'
An address that can be used in a non-macro load or store.
- 'ZC'
+ `ZC'
A memory operand whose address is formed by a base register
and offset that is suitable for use in instructions with the
- same addressing mode as 'll' and 'sc'.
+ same addressing mode as `ll' and `sc'.
+
+ `ZD'
+ An address suitable for a `prefetch' instruction, or for any
+ other instruction with the same addressing mode as `prefetch'.
- 'ZD'
- An address suitable for a 'prefetch' instruction, or for any
- other instruction with the same addressing mode as 'prefetch'.
+_Motorola 680x0--`config/m68k/constraints.md'_
-_Motorola 680x0--'config/m68k/constraints.md'_
- 'a'
+ `a'
Address register
- 'd'
+ `d'
Data register
- 'f'
+ `f'
68881 floating-point register, if available
- 'I'
+ `I'
Integer in the range 1 to 8
- 'J'
+ `J'
16-bit signed number
- 'K'
+ `K'
Signed number whose magnitude is greater than 0x80
- 'L'
+ `L'
Integer in the range -8 to -1
- 'M'
+ `M'
Signed number whose magnitude is greater than 0x100
- 'N'
+ `N'
Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate
- 'O'
+ `O'
16 (for rotate using swap)
- 'P'
+ `P'
Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate
- 'R'
+ `R'
Numbers that mov3q can handle
- 'G'
+ `G'
Floating point constant that is not a 68881 constant
- 'S'
+ `S'
Operands that satisfy 'm' when -mpcrel is in effect
- 'T'
+ `T'
Operands that satisfy 's' when -mpcrel is not in effect
- 'Q'
+ `Q'
Address register indirect addressing mode
- 'U'
+ `U'
Register offset addressing
- 'W'
+ `W'
const_call_operand
- 'Cs'
+ `Cs'
symbol_ref or const
- 'Ci'
+ `Ci'
const_int
- 'C0'
+ `C0'
const_int 0
- 'Cj'
+ `Cj'
Range of signed numbers that don't fit in 16 bits
- 'Cmvq'
+ `Cmvq'
Integers valid for mvq
- 'Capsw'
+ `Capsw'
Integers valid for a moveq followed by a swap
- 'Cmvz'
+ `Cmvz'
Integers valid for mvz
- 'Cmvs'
+ `Cmvs'
Integers valid for mvs
- 'Ap'
+ `Ap'
push_operand
- 'Ac'
+ `Ac'
Non-register operands allowed in clr
-_Moxie--'config/moxie/constraints.md'_
- 'A'
+
+_Moxie--`config/moxie/constraints.md'_
+
+ `A'
An absolute address
- 'B'
+ `B'
An offset address
- 'W'
+ `W'
A register indirect memory operand
- 'I'
+ `I'
A constant in the range of 0 to 255.
- 'N'
+ `N'
A constant in the range of 0 to -255.
-_MSP430-'config/msp430/constraints.md'_
- 'R12'
+_MSP430-`config/msp430/constraints.md'_
+
+ `R12'
Register R12.
- 'R13'
+ `R13'
Register R13.
- 'K'
+ `K'
Integer constant 1.
- 'L'
+ `L'
Integer constant -1^20..1^19.
- 'M'
+ `M'
Integer constant 1-4.
- 'Ya'
+ `Ya'
Memory references which do not require an extended MOVX
instruction.
- 'Yl'
+ `Yl'
Memory reference, labels only.
- 'Ys'
+ `Ys'
Memory reference, stack only.
-_NDS32--'config/nds32/constraints.md'_
- 'w'
+
+_NDS32--`config/nds32/constraints.md'_
+
+ `w'
LOW register class $r0 to $r7 constraint for V3/V3M ISA.
- 'l'
+
+ `l'
LOW register class $r0 to $r7.
- 'd'
+
+ `d'
MIDDLE register class $r0 to $r11, $r16 to $r19.
- 'h'
+
+ `h'
HIGH register class $r12 to $r14, $r20 to $r31.
- 't'
+
+ `t'
Temporary assist register $ta (i.e. $r15).
- 'k'
+
+ `k'
Stack register $sp.
- 'Iu03'
+
+ `Iu03'
Unsigned immediate 3-bit value.
- 'In03'
+
+ `In03'
Negative immediate 3-bit value in the range of -7-0.
- 'Iu04'
+
+ `Iu04'
Unsigned immediate 4-bit value.
- 'Is05'
+
+ `Is05'
Signed immediate 5-bit value.
- 'Iu05'
+
+ `Iu05'
Unsigned immediate 5-bit value.
- 'In05'
+
+ `In05'
Negative immediate 5-bit value in the range of -31-0.
- 'Ip05'
+
+ `Ip05'
Unsigned immediate 5-bit value for movpi45 instruction with
range 16-47.
- 'Iu06'
+
+ `Iu06'
Unsigned immediate 6-bit value constraint for addri36.sp
instruction.
- 'Iu08'
+
+ `Iu08'
Unsigned immediate 8-bit value.
- 'Iu09'
+
+ `Iu09'
Unsigned immediate 9-bit value.
- 'Is10'
+
+ `Is10'
Signed immediate 10-bit value.
- 'Is11'
+
+ `Is11'
Signed immediate 11-bit value.
- 'Is15'
+
+ `Is15'
Signed immediate 15-bit value.
- 'Iu15'
+
+ `Iu15'
Unsigned immediate 15-bit value.
- 'Ic15'
- A constant which is not in the range of imm15u but ok for bclr
- instruction.
- 'Ie15'
- A constant which is not in the range of imm15u but ok for bset
- instruction.
- 'It15'
- A constant which is not in the range of imm15u but ok for btgl
- instruction.
- 'Ii15'
+
+ `Ic15'
+ A constant which is not in the range of imm15u but ok for
+ bclr instruction.
+
+ `Ie15'
+ A constant which is not in the range of imm15u but ok for
+ bset instruction.
+
+ `It15'
+ A constant which is not in the range of imm15u but ok for
+ btgl instruction.
+
+ `Ii15'
A constant whose compliment value is in the range of imm15u
and ok for bitci instruction.
- 'Is16'
+
+ `Is16'
Signed immediate 16-bit value.
- 'Is17'
+
+ `Is17'
Signed immediate 17-bit value.
- 'Is19'
+
+ `Is19'
Signed immediate 19-bit value.
- 'Is20'
+
+ `Is20'
Signed immediate 20-bit value.
- 'Ihig'
+
+ `Ihig'
The immediate value that can be simply set high 20-bit.
- 'Izeb'
+
+ `Izeb'
The immediate value 0xff.
- 'Izeh'
+
+ `Izeh'
The immediate value 0xffff.
- 'Ixls'
+
+ `Ixls'
The immediate value 0x01.
- 'Ix11'
+
+ `Ix11'
The immediate value 0x7ff.
- 'Ibms'
+
+ `Ibms'
The immediate value with power of 2.
- 'Ifex'
+
+ `Ifex'
The immediate value with power of 2 minus 1.
- 'U33'
+
+ `U33'
Memory constraint for 333 format.
- 'U45'
+
+ `U45'
Memory constraint for 45 format.
- 'U37'
+
+ `U37'
Memory constraint for 37 format.
-_Nios II family--'config/nios2/constraints.md'_
+_Nios II family--`config/nios2/constraints.md'_
- 'I'
+ `I'
Integer that is valid as an immediate operand in an
- instruction taking a signed 16-bit number. Range -32768 to
+ instruction taking a signed 16-bit number. Range -32768 to
32767.
- 'J'
+ `J'
Integer that is valid as an immediate operand in an
- instruction taking an unsigned 16-bit number. Range 0 to
+ instruction taking an unsigned 16-bit number. Range 0 to
65535.
- 'K'
+ `K'
Integer that is valid as an immediate operand in an
instruction taking only the upper 16-bits of a 32-bit number.
Range 32-bit numbers with the lower 16-bits being 0.
- 'L'
+ `L'
Integer that is valid as an immediate operand for a shift
- instruction. Range 0 to 31.
+ instruction. Range 0 to 31.
- 'M'
+ `M'
Integer that is valid as an immediate operand for only the
- value 0. Can be used in conjunction with the format modifier
- 'z' to use 'r0' instead of '0' in the assembly output.
+ value 0. Can be used in conjunction with the format modifier
+ `z' to use `r0' instead of `0' in the assembly output.
- 'N'
+ `N'
Integer that is valid as an immediate operand for a custom
- instruction opcode. Range 0 to 255.
+ instruction opcode. Range 0 to 255.
- 'S'
+ `S'
Matches immediates which are addresses in the small data
- section and therefore can be added to 'gp' as a 16-bit
+ section and therefore can be added to `gp' as a 16-bit
immediate to re-create their 32-bit value.
-_PDP-11--'config/pdp11/constraints.md'_
- 'a'
- Floating point registers AC0 through AC3. These can be loaded
- from/to memory with a single instruction.
- 'd'
+_PDP-11--`config/pdp11/constraints.md'_
+
+ `a'
+ Floating point registers AC0 through AC3. These can be
+ loaded from/to memory with a single instruction.
+
+ `d'
Odd numbered general registers (R1, R3, R5). These are used
for 16-bit multiply operations.
- 'f'
+ `f'
Any of the floating point registers (AC0 through AC5).
- 'G'
+ `G'
Floating point constant 0.
- 'I'
+ `I'
An integer constant that fits in 16 bits.
- 'J'
+ `J'
An integer constant whose low order 16 bits are zero.
- 'K'
+ `K'
An integer constant that does not meet the constraints for
- codes 'I' or 'J'.
+ codes `I' or `J'.
- 'L'
+ `L'
The integer constant 1.
- 'M'
+ `M'
The integer constant -1.
- 'N'
+ `N'
The integer constant 0.
- 'O'
+ `O'
Integer constants -4 through -1 and 1 through 4; shifts by
- these amounts are handled as multiple single-bit shifts rather
- than a single variable-length shift.
+ these amounts are handled as multiple single-bit shifts
+ rather than a single variable-length shift.
- 'Q'
+ `Q'
A memory reference which requires an additional word (address
or offset) after the opcode.
- 'R'
+ `R'
A memory reference that is encoded within the opcode.
-_PowerPC and IBM RS6000--'config/rs6000/constraints.md'_
- 'b'
+
+_PowerPC and IBM RS6000--`config/rs6000/constraints.md'_
+
+ `b'
Address base register
- 'd'
+ `d'
Floating point register (containing 64-bit value)
- 'f'
+ `f'
Floating point register (containing 32-bit value)
- 'v'
+ `v'
Altivec vector register
- 'wa'
+ `wa'
Any VSX register if the -mvsx option was used or NO_REGS.
- 'wd'
+ When using any of the register constraints (`wa', `wd', `wf',
+ `wg', `wh', `wi', `wj', `wk', `wl', `wm', `ws', `wt', `wu',
+ `wv', `ww', or `wy') that take VSX registers, you must use
+ `%x<n>' in the template so that the correct register is used.
+ Otherwise the register number output in the assembly file
+ will be incorrect if an Altivec register is an operand of a
+ VSX instruction that expects VSX register numbering.
+
+ asm ("xvadddp %x0,%x1,%x2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+
+ is correct, but:
+
+ asm ("xvadddp %0,%1,%2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+
+ is not correct.
+
+ `wd'
VSX vector register to hold vector double data or NO_REGS.
- 'wf'
+ `wf'
VSX vector register to hold vector float data or NO_REGS.
- 'wg'
- If '-mmfpgpr' was used, a floating point register or NO_REGS.
+ `wg'
+ If `-mmfpgpr' was used, a floating point register or NO_REGS.
- 'wh'
+ `wh'
Floating point register if direct moves are available, or
NO_REGS.
- 'wi'
+ `wi'
FP or VSX register to hold 64-bit integers for VSX insns or
NO_REGS.
- 'wj'
- FP or VSX register to hold 64-bit integers for direct moves or
- NO_REGS.
+ `wj'
+ FP or VSX register to hold 64-bit integers for direct moves
+ or NO_REGS.
- 'wk'
+ `wk'
FP or VSX register to hold 64-bit doubles for direct moves or
NO_REGS.
- 'wl'
+ `wl'
Floating point register if the LFIWAX instruction is enabled
or NO_REGS.
- 'wm'
+ `wm'
VSX register if direct move instructions are enabled, or
NO_REGS.
- 'wn'
+ `wn'
No register (NO_REGS).
- 'wr'
- General purpose register if 64-bit instructions are enabled or
- NO_REGS.
+ `wr'
+ General purpose register if 64-bit instructions are enabled
+ or NO_REGS.
- 'ws'
+ `ws'
VSX vector register to hold scalar double values or NO_REGS.
- 'wt'
+ `wt'
VSX vector register to hold 128 bit integer or NO_REGS.
- 'wu'
- Altivec register to use for float/32-bit int loads/stores or
+ `wu'
+ Altivec register to use for float/32-bit int loads/stores or
NO_REGS.
- 'wv'
- Altivec register to use for double loads/stores or NO_REGS.
+ `wv'
+ Altivec register to use for double loads/stores or NO_REGS.
- 'ww'
- FP or VSX register to perform float operations under '-mvsx'
+ `ww'
+ FP or VSX register to perform float operations under `-mvsx'
or NO_REGS.
- 'wx'
+ `wx'
Floating point register if the STFIWX instruction is enabled
or NO_REGS.
- 'wy'
+ `wy'
FP or VSX register to perform ISA 2.07 float ops or NO_REGS.
- 'wz'
+ `wz'
Floating point register if the LFIWZX instruction is enabled
or NO_REGS.
- 'wD'
+ `wD'
Int constant that is the element number of the 64-bit scalar
in a vector.
- 'wQ'
- A memory address that will work with the 'lq' and 'stq'
+ `wQ'
+ A memory address that will work with the `lq' and `stq'
instructions.
- 'h'
- 'MQ', 'CTR', or 'LINK' register
+ `h'
+ `MQ', `CTR', or `LINK' register
- 'q'
- 'MQ' register
+ `q'
+ `MQ' register
- 'c'
- 'CTR' register
+ `c'
+ `CTR' register
- 'l'
- 'LINK' register
+ `l'
+ `LINK' register
- 'x'
- 'CR' register (condition register) number 0
+ `x'
+ `CR' register (condition register) number 0
- 'y'
- 'CR' register (condition register)
+ `y'
+ `CR' register (condition register)
- 'z'
- 'XER[CA]' carry bit (part of the XER register)
+ `z'
+ `XER[CA]' carry bit (part of the XER register)
- 'I'
+ `I'
Signed 16-bit constant
- 'J'
- Unsigned 16-bit constant shifted left 16 bits (use 'L' instead
- for 'SImode' constants)
+ `J'
+ Unsigned 16-bit constant shifted left 16 bits (use `L'
+ instead for `SImode' constants)
- 'K'
+ `K'
Unsigned 16-bit constant
- 'L'
+ `L'
Signed 16-bit constant shifted left 16 bits
- 'M'
+ `M'
Constant larger than 31
- 'N'
+ `N'
Exact power of 2
- 'O'
+ `O'
Zero
- 'P'
+ `P'
Constant whose negation is a signed 16-bit constant
- 'G'
+ `G'
Floating point constant that can be loaded into a register
with one instruction per word
- 'H'
+ `H'
Integer/Floating point constant that can be loaded into a
register using three instructions
- 'm'
- Memory operand. Normally, 'm' does not allow addresses that
- update the base register. If '<' or '>' constraint is also
+ `m'
+ Memory operand. Normally, `m' does not allow addresses that
+ update the base register. If `<' or `>' constraint is also
used, they are allowed and therefore on PowerPC targets in
- that case it is only safe to use 'm<>' in an 'asm' statement
- if that 'asm' statement accesses the operand exactly once.
- The 'asm' statement must also use '%U<OPNO>' as a placeholder
+ that case it is only safe to use `m<>' in an `asm' statement
+ if that `asm' statement accesses the operand exactly once.
+ The `asm' statement must also use `%U<OPNO>' as a placeholder
for the "update" flag in the corresponding load or store
instruction. For example:
@@ -31092,699 +31401,763 @@ _PowerPC and IBM RS6000--'config/rs6000/constraints.md'_
is not.
- 'es'
- A "stable" memory operand; that is, one which does not include
- any automodification of the base register. This used to be
- useful when 'm' allowed automodification of the base register,
- but as those are now only allowed when '<' or '>' is used,
- 'es' is basically the same as 'm' without '<' and '>'.
+ `es'
+ A "stable" memory operand; that is, one which does not
+ include any automodification of the base register. This used
+ to be useful when `m' allowed automodification of the base
+ register, but as those are now only allowed when `<' or `>'
+ is used, `es' is basically the same as `m' without `<' and
+ `>'.
- 'Q'
+ `Q'
Memory operand that is an offset from a register (it is
- usually better to use 'm' or 'es' in 'asm' statements)
+ usually better to use `m' or `es' in `asm' statements)
- 'Z'
+ `Z'
Memory operand that is an indexed or indirect from a register
- (it is usually better to use 'm' or 'es' in 'asm' statements)
+ (it is usually better to use `m' or `es' in `asm' statements)
- 'R'
+ `R'
AIX TOC entry
- 'a'
- Address operand that is an indexed or indirect from a register
- ('p' is preferable for 'asm' statements)
+ `a'
+ Address operand that is an indexed or indirect from a
+ register (`p' is preferable for `asm' statements)
- 'S'
+ `S'
Constant suitable as a 64-bit mask operand
- 'T'
+ `T'
Constant suitable as a 32-bit mask operand
- 'U'
+ `U'
System V Release 4 small data area reference
- 't'
+ `t'
AND masks that can be performed by two rldic{l, r}
instructions
- 'W'
+ `W'
Vector constant that does not require memory
- 'j'
+ `j'
Vector constant that is all zeros.
-_RL78--'config/rl78/constraints.md'_
- 'Int3'
+_RL78--`config/rl78/constraints.md'_
+
+ `Int3'
An integer constant in the range 1 ... 7.
- 'Int8'
+
+ `Int8'
An integer constant in the range 0 ... 255.
- 'J'
+
+ `J'
An integer constant in the range -255 ... 0
- 'K'
+
+ `K'
The integer constant 1.
- 'L'
+
+ `L'
The integer constant -1.
- 'M'
+
+ `M'
The integer constant 0.
- 'N'
+
+ `N'
The integer constant 2.
- 'O'
+
+ `O'
The integer constant -2.
- 'P'
+
+ `P'
An integer constant in the range 1 ... 15.
- 'Qbi'
+
+ `Qbi'
The built-in compare types-eq, ne, gtu, ltu, geu, and leu.
- 'Qsc'
+
+ `Qsc'
The synthetic compare types-gt, lt, ge, and le.
- 'Wab'
+
+ `Wab'
A memory reference with an absolute address.
- 'Wbc'
- A memory reference using 'BC' as a base register, with an
+
+ `Wbc'
+ A memory reference using `BC' as a base register, with an
optional offset.
- 'Wca'
- A memory reference using 'AX', 'BC', 'DE', or 'HL' for the
+
+ `Wca'
+ A memory reference using `AX', `BC', `DE', or `HL' for the
address, for calls.
- 'Wcv'
+
+ `Wcv'
A memory reference using any 16-bit register pair for the
address, for calls.
- 'Wd2'
- A memory reference using 'DE' as a base register, with an
+
+ `Wd2'
+ A memory reference using `DE' as a base register, with an
optional offset.
- 'Wde'
- A memory reference using 'DE' as a base register, without any
+
+ `Wde'
+ A memory reference using `DE' as a base register, without any
offset.
- 'Wfr'
+
+ `Wfr'
Any memory reference to an address in the far address space.
- 'Wh1'
- A memory reference using 'HL' as a base register, with an
+
+ `Wh1'
+ A memory reference using `HL' as a base register, with an
optional one-byte offset.
- 'Whb'
- A memory reference using 'HL' as a base register, with 'B' or
- 'C' as the index register.
- 'Whl'
- A memory reference using 'HL' as a base register, without any
+
+ `Whb'
+ A memory reference using `HL' as a base register, with `B' or
+ `C' as the index register.
+
+ `Whl'
+ A memory reference using `HL' as a base register, without any
offset.
- 'Ws1'
- A memory reference using 'SP' as a base register, with an
+
+ `Ws1'
+ A memory reference using `SP' as a base register, with an
optional one-byte offset.
- 'Y'
+
+ `Y'
Any memory reference to an address in the near address space.
- 'A'
- The 'AX' register.
- 'B'
- The 'BC' register.
- 'D'
- The 'DE' register.
- 'R'
- 'A' through 'L' registers.
- 'S'
- The 'SP' register.
- 'T'
- The 'HL' register.
- 'Z08W'
- The 16-bit 'R8' register.
- 'Z10W'
- The 16-bit 'R10' register.
- 'Zint'
- The registers reserved for interrupts ('R24' to 'R31').
- 'a'
- The 'A' register.
- 'b'
- The 'B' register.
- 'c'
- The 'C' register.
- 'd'
- The 'D' register.
- 'e'
- The 'E' register.
- 'h'
- The 'H' register.
- 'l'
- The 'L' register.
- 'v'
+
+ `A'
+ The `AX' register.
+
+ `B'
+ The `BC' register.
+
+ `D'
+ The `DE' register.
+
+ `R'
+ `A' through `L' registers.
+
+ `S'
+ The `SP' register.
+
+ `T'
+ The `HL' register.
+
+ `Z08W'
+ The 16-bit `R8' register.
+
+ `Z10W'
+ The 16-bit `R10' register.
+
+ `Zint'
+ The registers reserved for interrupts (`R24' to `R31').
+
+ `a'
+ The `A' register.
+
+ `b'
+ The `B' register.
+
+ `c'
+ The `C' register.
+
+ `d'
+ The `D' register.
+
+ `e'
+ The `E' register.
+
+ `h'
+ The `H' register.
+
+ `l'
+ The `L' register.
+
+ `v'
The virtual registers.
- 'w'
- The 'PSW' register.
- 'x'
- The 'X' register.
-_RX--'config/rx/constraints.md'_
- 'Q'
- An address which does not involve register indirect addressing
- or pre/post increment/decrement addressing.
+ `w'
+ The `PSW' register.
+
+ `x'
+ The `X' register.
+
- 'Symbol'
+_RX--`config/rx/constraints.md'_
+
+ `Q'
+ An address which does not involve register indirect
+ addressing or pre/post increment/decrement addressing.
+
+ `Symbol'
A symbol reference.
- 'Int08'
+ `Int08'
A constant in the range -256 to 255, inclusive.
- 'Sint08'
+ `Sint08'
A constant in the range -128 to 127, inclusive.
- 'Sint16'
+ `Sint16'
A constant in the range -32768 to 32767, inclusive.
- 'Sint24'
+ `Sint24'
A constant in the range -8388608 to 8388607, inclusive.
- 'Uint04'
+ `Uint04'
A constant in the range 0 to 15, inclusive.
-_S/390 and zSeries--'config/s390/s390.h'_
- 'a'
+
+_S/390 and zSeries--`config/s390/s390.h'_
+
+ `a'
Address register (general purpose register except r0)
- 'c'
+ `c'
Condition code register
- 'd'
+ `d'
Data register (arbitrary general purpose register)
- 'f'
+ `f'
Floating-point register
- 'I'
+ `I'
Unsigned 8-bit constant (0-255)
- 'J'
+ `J'
Unsigned 12-bit constant (0-4095)
- 'K'
+ `K'
Signed 16-bit constant (-32768-32767)
- 'L'
+ `L'
Value appropriate as displacement.
- '(0..4095)'
+ `(0..4095)'
for short displacement
- '(-524288..524287)'
+
+ `(-524288..524287)'
for long displacement
- 'M'
+ `M'
Constant integer with a value of 0x7fffffff.
- 'N'
+ `N'
Multiple letter constraint followed by 4 parameter letters.
- '0..9:'
+ `0..9:'
number of the part counting from most to least
significant
- 'H,Q:'
+
+ `H,Q:'
mode of the part
- 'D,S,H:'
+
+ `D,S,H:'
mode of the containing operand
- '0,F:'
+
+ `0,F:'
value of the other parts (F--all bits set)
- The constraint matches if the specified part of a constant has
- a value different from its other parts.
+ The constraint matches if the specified part of a constant
+ has a value different from its other parts.
- 'Q'
+ `Q'
Memory reference without index register and with short
displacement.
- 'R'
+ `R'
Memory reference with index register and short displacement.
- 'S'
+ `S'
Memory reference without index register but with long
displacement.
- 'T'
+ `T'
Memory reference with index register and long displacement.
- 'U'
+ `U'
Pointer with short displacement.
- 'W'
+ `W'
Pointer with long displacement.
- 'Y'
+ `Y'
Shift count operand.
-_SPARC--'config/sparc/sparc.h'_
- 'f'
- Floating-point register on the SPARC-V8 architecture and lower
- floating-point register on the SPARC-V9 architecture.
- 'e'
- Floating-point register. It is equivalent to 'f' on the
+_SPARC--`config/sparc/sparc.h'_
+
+ `f'
+ Floating-point register on the SPARC-V8 architecture and
+ lower floating-point register on the SPARC-V9 architecture.
+
+ `e'
+ Floating-point register. It is equivalent to `f' on the
SPARC-V8 architecture and contains both lower and upper
floating-point registers on the SPARC-V9 architecture.
- 'c'
+ `c'
Floating-point condition code register.
- 'd'
+ `d'
Lower floating-point register. It is only valid on the
SPARC-V9 architecture when the Visual Instruction Set is
available.
- 'b'
+ `b'
Floating-point register. It is only valid on the SPARC-V9
architecture when the Visual Instruction Set is available.
- 'h'
+ `h'
64-bit global or out register for the SPARC-V8+ architecture.
- 'C'
+ `C'
The constant all-ones, for floating-point.
- 'A'
+ `A'
Signed 5-bit constant
- 'D'
+ `D'
A vector constant
- 'I'
+ `I'
Signed 13-bit constant
- 'J'
+ `J'
Zero
- 'K'
+ `K'
32-bit constant with the low 12 bits clear (a constant that
- can be loaded with the 'sethi' instruction)
+ can be loaded with the `sethi' instruction)
- 'L'
- A constant in the range supported by 'movcc' instructions
+ `L'
+ A constant in the range supported by `movcc' instructions
(11-bit signed immediate)
- 'M'
- A constant in the range supported by 'movrcc' instructions
+ `M'
+ A constant in the range supported by `movrcc' instructions
(10-bit signed immediate)
- 'N'
- Same as 'K', except that it verifies that bits that are not in
- the lower 32-bit range are all zero. Must be used instead of
- 'K' for modes wider than 'SImode'
+ `N'
+ Same as `K', except that it verifies that bits that are not
+ in the lower 32-bit range are all zero. Must be used instead
+ of `K' for modes wider than `SImode'
- 'O'
+ `O'
The constant 4096
- 'G'
+ `G'
Floating-point zero
- 'H'
+ `H'
Signed 13-bit constant, sign-extended to 32 or 64 bits
- 'P'
+ `P'
The constant -1
- 'Q'
+ `Q'
Floating-point constant whose integral representation can be
moved into an integer register using a single sethi
instruction
- 'R'
+ `R'
Floating-point constant whose integral representation can be
moved into an integer register using a single mov instruction
- 'S'
+ `S'
Floating-point constant whose integral representation can be
- moved into an integer register using a high/lo_sum instruction
- sequence
+ moved into an integer register using a high/lo_sum
+ instruction sequence
- 'T'
+ `T'
Memory address aligned to an 8-byte boundary
- 'U'
+ `U'
Even register
- 'W'
- Memory address for 'e' constraint registers
+ `W'
+ Memory address for `e' constraint registers
- 'w'
+ `w'
Memory address with only a base register
- 'Y'
+ `Y'
Vector zero
-_SPU--'config/spu/spu.h'_
- 'a'
+
+_SPU--`config/spu/spu.h'_
+
+ `a'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is treated as a 64 bit value.
- 'c'
+ `c'
An immediate for and/xor/or instructions. const_int is
treated as a 64 bit value.
- 'd'
- An immediate for the 'iohl' instruction. const_int is treated
- as a 64 bit value.
+ `d'
+ An immediate for the `iohl' instruction. const_int is
+ treated as a 64 bit value.
- 'f'
- An immediate which can be loaded with 'fsmbi'.
+ `f'
+ An immediate which can be loaded with `fsmbi'.
- 'A'
+ `A'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is treated as a 32 bit value.
- 'B'
+ `B'
An immediate for most arithmetic instructions. const_int is
treated as a 32 bit value.
- 'C'
+ `C'
An immediate for and/xor/or instructions. const_int is
treated as a 32 bit value.
- 'D'
- An immediate for the 'iohl' instruction. const_int is treated
- as a 32 bit value.
+ `D'
+ An immediate for the `iohl' instruction. const_int is
+ treated as a 32 bit value.
- 'I'
+ `I'
A constant in the range [-64, 63] for shift/rotate
instructions.
- 'J'
+ `J'
An unsigned 7-bit constant for conversion/nop/channel
instructions.
- 'K'
+ `K'
A signed 10-bit constant for most arithmetic instructions.
- 'M'
- A signed 16 bit immediate for 'stop'.
+ `M'
+ A signed 16 bit immediate for `stop'.
- 'N'
- An unsigned 16-bit constant for 'iohl' and 'fsmbi'.
+ `N'
+ An unsigned 16-bit constant for `iohl' and `fsmbi'.
- 'O'
+ `O'
An unsigned 7-bit constant whose 3 least significant bits are
0.
- 'P'
+ `P'
An unsigned 3-bit constant for 16-byte rotates and shifts
- 'R'
+ `R'
Call operand, reg, for indirect calls
- 'S'
+ `S'
Call operand, symbol, for relative calls.
- 'T'
+ `T'
Call operand, const_int, for absolute calls.
- 'U'
+ `U'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is sign extended to 128 bit.
- 'W'
+ `W'
An immediate for shift and rotate instructions. const_int is
treated as a 32 bit value.
- 'Y'
+ `Y'
An immediate for and/xor/or instructions. const_int is sign
extended as a 128 bit.
- 'Z'
- An immediate for the 'iohl' instruction. const_int is sign
+ `Z'
+ An immediate for the `iohl' instruction. const_int is sign
extended to 128 bit.
-_TI C6X family--'config/c6x/constraints.md'_
- 'a'
+
+_TI C6X family--`config/c6x/constraints.md'_
+
+ `a'
Register file A (A0-A31).
- 'b'
+ `b'
Register file B (B0-B31).
- 'A'
+ `A'
Predicate registers in register file A (A0-A2 on C64X and
higher, A1 and A2 otherwise).
- 'B'
+ `B'
Predicate registers in register file B (B0-B2).
- 'C'
+ `C'
A call-used register in register file B (B0-B9, B16-B31).
- 'Da'
+ `Da'
Register file A, excluding predicate registers (A3-A31, plus
A0 if not C64X or higher).
- 'Db'
+ `Db'
Register file B, excluding predicate registers (B3-B31).
- 'Iu4'
+ `Iu4'
Integer constant in the range 0 ... 15.
- 'Iu5'
+ `Iu5'
Integer constant in the range 0 ... 31.
- 'In5'
+ `In5'
Integer constant in the range -31 ... 0.
- 'Is5'
+ `Is5'
Integer constant in the range -16 ... 15.
- 'I5x'
+ `I5x'
Integer constant that can be the operand of an ADDA or a SUBA
insn.
- 'IuB'
+ `IuB'
Integer constant in the range 0 ... 65535.
- 'IsB'
+ `IsB'
Integer constant in the range -32768 ... 32767.
- 'IsC'
- Integer constant in the range -2^{20} ... 2^{20} - 1.
+ `IsC'
+ Integer constant in the range -2^20 ... 2^20 - 1.
- 'Jc'
+ `Jc'
Integer constant that is a valid mask for the clr instruction.
- 'Js'
+ `Js'
Integer constant that is a valid mask for the set instruction.
- 'Q'
+ `Q'
Memory location with A base register.
- 'R'
+ `R'
Memory location with B base register.
- 'Z'
+ `Z'
Register B14 (aka DP).
-_TILE-Gx--'config/tilegx/constraints.md'_
- 'R00'
- 'R01'
- 'R02'
- 'R03'
- 'R04'
- 'R05'
- 'R06'
- 'R07'
- 'R08'
- 'R09'
- 'R10'
+
+_TILE-Gx--`config/tilegx/constraints.md'_
+
+ `R00'
+ `R01'
+ `R02'
+ `R03'
+ `R04'
+ `R05'
+ `R06'
+ `R07'
+ `R08'
+ `R09'
+ `R10'
Each of these represents a register constraint for an
individual register, from r0 to r10.
- 'I'
+ `I'
Signed 8-bit integer constant.
- 'J'
+ `J'
Signed 16-bit integer constant.
- 'K'
+ `K'
Unsigned 16-bit integer constant.
- 'L'
- Integer constant that fits in one signed byte when incremented
- by one (-129 ... 126).
+ `L'
+ Integer constant that fits in one signed byte when
+ incremented by one (-129 ... 126).
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement which requires printing with '%In' and
- '%in' on TILE-Gx. For example:
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement which requires printing with
+ `%In' and `%in' on TILE-Gx. For example:
asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val));
- 'M'
+ `M'
A bit mask suitable for the BFINS instruction.
- 'N'
+ `N'
Integer constant that is a byte tiled out eight times.
- 'O'
+ `O'
The integer zero constant.
- 'P'
+ `P'
Integer constant that is a sign-extended byte tiled out as
four shorts.
- 'Q'
+ `Q'
Integer constant that fits in one signed byte when incremented
(-129 ... 126), but excluding -1.
- 'S'
+ `S'
Integer constant that has all 1 bits consecutive and starting
at bit 0.
- 'T'
+ `T'
A 16-bit fragment of a got, tls, or pc-relative reference.
- 'U'
- Memory operand except postincrement. This is roughly the same
- as 'm' when not used together with '<' or '>'.
+ `U'
+ Memory operand except postincrement. This is roughly the
+ same as `m' when not used together with `<' or `>'.
- 'W'
+ `W'
An 8-element vector constant with identical elements.
- 'Y'
+ `Y'
A 4-element vector constant with identical elements.
- 'Z0'
+ `Z0'
The integer constant 0xffffffff.
- 'Z1'
+ `Z1'
The integer constant 0xffffffff00000000.
-_TILEPro--'config/tilepro/constraints.md'_
- 'R00'
- 'R01'
- 'R02'
- 'R03'
- 'R04'
- 'R05'
- 'R06'
- 'R07'
- 'R08'
- 'R09'
- 'R10'
+
+_TILEPro--`config/tilepro/constraints.md'_
+
+ `R00'
+ `R01'
+ `R02'
+ `R03'
+ `R04'
+ `R05'
+ `R06'
+ `R07'
+ `R08'
+ `R09'
+ `R10'
Each of these represents a register constraint for an
individual register, from r0 to r10.
- 'I'
+ `I'
Signed 8-bit integer constant.
- 'J'
+ `J'
Signed 16-bit integer constant.
- 'K'
+ `K'
Nonzero integer constant with low 16 bits zero.
- 'L'
- Integer constant that fits in one signed byte when incremented
- by one (-129 ... 126).
+ `L'
+ Integer constant that fits in one signed byte when
+ incremented by one (-129 ... 126).
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement which requires printing with '%In' and
- '%in' on TILEPro. For example:
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement which requires printing with
+ `%In' and `%in' on TILEPro. For example:
asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val));
- 'M'
+ `M'
A bit mask suitable for the MM instruction.
- 'N'
+ `N'
Integer constant that is a byte tiled out four times.
- 'O'
+ `O'
The integer zero constant.
- 'P'
- Integer constant that is a sign-extended byte tiled out as two
- shorts.
+ `P'
+ Integer constant that is a sign-extended byte tiled out as
+ two shorts.
- 'Q'
+ `Q'
Integer constant that fits in one signed byte when incremented
(-129 ... 126), but excluding -1.
- 'T'
+ `T'
A symbolic operand, or a 16-bit fragment of a got, tls, or
pc-relative reference.
- 'U'
- Memory operand except postincrement. This is roughly the same
- as 'm' when not used together with '<' or '>'.
+ `U'
+ Memory operand except postincrement. This is roughly the
+ same as `m' when not used together with `<' or `>'.
- 'W'
+ `W'
A 4-element vector constant with identical elements.
- 'Y'
+ `Y'
A 2-element vector constant with identical elements.
-_Visium--'config/visium/constraints.md'_
- 'b'
- EAM register 'mdb'
- 'c'
- EAM register 'mdc'
+_Visium--`config/visium/constraints.md'_
- 'f'
+ `b'
+ EAM register `mdb'
+
+ `c'
+ EAM register `mdc'
+
+ `f'
Floating point register
- 'l'
- General register, but not 'r29', 'r30' and 'r31'
+ `l'
+ General register, but not `r29', `r30' and `r31'
- 't'
- Register 'r1'
+ `t'
+ Register `r1'
- 'u'
- Register 'r2'
+ `u'
+ Register `r2'
- 'v'
- Register 'r3'
+ `v'
+ Register `r3'
- 'G'
+ `G'
Floating-point constant 0.0
- 'J'
- Integer constant in the range 0 .. 65535 (16-bit immediate)
+ `J'
+ Integer constant in the range 0 .. 65535 (16-bit immediate)
- 'K'
- Integer constant in the range 1 .. 31 (5-bit immediate)
+ `K'
+ Integer constant in the range 1 .. 31 (5-bit immediate)
- 'L'
- Integer constant in the range -65535 .. -1 (16-bit negative
+ `L'
+ Integer constant in the range -65535 .. -1 (16-bit negative
immediate)
- 'M'
+ `M'
Integer constant -1
- 'O'
+ `O'
Integer constant 0
- 'P'
+ `P'
Integer constant 32
-_x86 family--'config/i386/constraints.md'_
- 'R'
+_x86 family--`config/i386/constraints.md'_
+
+ `R'
Legacy register--the eight integer registers available on all
- i386 processors ('a', 'b', 'c', 'd', 'si', 'di', 'bp', 'sp').
+ i386 processors (`a', `b', `c', `d', `si', `di', `bp', `sp').
- 'q'
- Any register accessible as 'Rl'. In 32-bit mode, 'a', 'b',
- 'c', and 'd'; in 64-bit mode, any integer register.
+ `q'
+ Any register accessible as `Rl'. In 32-bit mode, `a', `b',
+ `c', and `d'; in 64-bit mode, any integer register.
- 'Q'
- Any register accessible as 'Rh': 'a', 'b', 'c', and 'd'.
+ `Q'
+ Any register accessible as `Rh': `a', `b', `c', and `d'.
- 'a'
- The 'a' register.
+ `a'
+ The `a' register.
- 'b'
- The 'b' register.
+ `b'
+ The `b' register.
- 'c'
- The 'c' register.
+ `c'
+ The `c' register.
- 'd'
- The 'd' register.
+ `d'
+ The `d' register.
- 'S'
- The 'si' register.
+ `S'
+ The `si' register.
- 'D'
- The 'di' register.
+ `D'
+ The `di' register.
- 'A'
- The 'a' and 'd' registers. This class is used for
- instructions that return double word results in the 'ax:dx'
- register pair. Single word values will be allocated either in
- 'ax' or 'dx'. For example on i386 the following implements
- 'rdtsc':
+ `A'
+ The `a' and `d' registers. This class is used for
+ instructions that return double word results in the `ax:dx'
+ register pair. Single word values will be allocated either
+ in `ax' or `dx'. For example on i386 the following
+ implements `rdtsc':
unsigned long long rdtsc (void)
{
@@ -31794,7 +32167,7 @@ _x86 family--'config/i386/constraints.md'_
}
This is not correct on x86-64 as it would allocate tick in
- either 'ax' or 'dx'. You have to use the following variant
+ either `ax' or `dx'. You have to use the following variant
instead:
unsigned long long rdtsc (void)
@@ -31804,149 +32177,155 @@ _x86 family--'config/i386/constraints.md'_
return ((unsigned long long)tickh << 32)|tickl;
}
- 'f'
+ `f'
Any 80387 floating-point (stack) register.
- 't'
- Top of 80387 floating-point stack ('%st(0)').
+ `t'
+ Top of 80387 floating-point stack (`%st(0)').
- 'u'
- Second from top of 80387 floating-point stack ('%st(1)').
+ `u'
+ Second from top of 80387 floating-point stack (`%st(1)').
- 'y'
+ `y'
Any MMX register.
- 'x'
+ `x'
Any SSE register.
- 'Yz'
- First SSE register ('%xmm0').
+ `Yz'
+ First SSE register (`%xmm0').
- 'I'
+ `I'
Integer constant in the range 0 ... 31, for 32-bit shifts.
- 'J'
+ `J'
Integer constant in the range 0 ... 63, for 64-bit shifts.
- 'K'
+ `K'
Signed 8-bit integer constant.
- 'L'
- '0xFF' or '0xFFFF', for andsi as a zero-extending move.
+ `L'
+ `0xFF' or `0xFFFF', for andsi as a zero-extending move.
- 'M'
- 0, 1, 2, or 3 (shifts for the 'lea' instruction).
+ `M'
+ 0, 1, 2, or 3 (shifts for the `lea' instruction).
- 'N'
- Unsigned 8-bit integer constant (for 'in' and 'out'
+ `N'
+ Unsigned 8-bit integer constant (for `in' and `out'
instructions).
- 'G'
+ `G'
Standard 80387 floating point constant.
- 'C'
+ `C'
Standard SSE floating point constant.
- 'e'
+ `e'
32-bit signed integer constant, or a symbolic reference known
to fit that range (for immediate operands in sign-extending
x86-64 instructions).
- 'Z'
+ `Z'
32-bit unsigned integer constant, or a symbolic reference
known to fit that range (for immediate operands in
zero-extending x86-64 instructions).
-_Xstormy16--'config/stormy16/stormy16.h'_
- 'a'
+
+_Xstormy16--`config/stormy16/stormy16.h'_
+
+ `a'
Register r0.
- 'b'
+ `b'
Register r1.
- 'c'
+ `c'
Register r2.
- 'd'
+ `d'
Register r8.
- 'e'
+ `e'
Registers r0 through r7.
- 't'
+ `t'
Registers r0 and r1.
- 'y'
+ `y'
The carry register.
- 'z'
+ `z'
Registers r8 and r9.
- 'I'
+ `I'
A constant between 0 and 3 inclusive.
- 'J'
+ `J'
A constant that has exactly one bit set.
- 'K'
+ `K'
A constant that has exactly one bit clear.
- 'L'
+ `L'
A constant between 0 and 255 inclusive.
- 'M'
+ `M'
A constant between -255 and 0 inclusive.
- 'N'
+ `N'
A constant between -3 and 0 inclusive.
- 'O'
+ `O'
A constant between 1 and 4 inclusive.
- 'P'
+ `P'
A constant between -4 and -1 inclusive.
- 'Q'
+ `Q'
A memory reference that is a stack push.
- 'R'
+ `R'
A memory reference that is a stack pop.
- 'S'
+ `S'
A memory reference that refers to a constant address of known
value.
- 'T'
+ `T'
The register indicated by Rx (not implemented yet).
- 'U'
+ `U'
A constant that is not between 2 and 15 inclusive.
- 'Z'
+ `Z'
The constant 0.
-_Xtensa--'config/xtensa/constraints.md'_
- 'a'
+
+_Xtensa--`config/xtensa/constraints.md'_
+
+ `a'
General-purpose 32-bit register
- 'b'
+ `b'
One-bit boolean register
- 'A'
+ `A'
MAC16 40-bit accumulator register
- 'I'
+ `I'
Signed 12-bit integer constant, for use in MOVI instructions
- 'J'
+ `J'
Signed 8-bit integer constant, for use in ADDI instructions
- 'K'
+ `K'
Integer constant valid for BccI instructions
- 'L'
+ `L'
Unsigned constant valid for BccUI instructions
+
+

File: gcc.info, Node: Asm Labels, Next: Explicit Reg Vars, Prev: Constraints, Up: Using Assembly Language with C
@@ -31954,13 +32333,13 @@ File: gcc.info, Node: Asm Labels, Next: Explicit Reg Vars, Prev: Constraints,
-----------------------------------------------
You can specify the name to be used in the assembler code for a C
-function or variable by writing the 'asm' (or '__asm__') keyword after
+function or variable by writing the `asm' (or `__asm__') keyword after
the declarator as follows:
int foo asm ("myfoo") = 2;
-This specifies that the name to be used for the variable 'foo' in the
-assembler code should be 'myfoo' rather than the usual '_foo'.
+This specifies that the name to be used for the variable `foo' in the
+assembler code should be `myfoo' rather than the usual `_foo'.
On systems where an underscore is normally prepended to the name of a C
function or variable, this feature allows you to define names for the
@@ -31973,9 +32352,9 @@ Reg Vars::. GCC presently accepts such code with a warning, but will
probably be changed to issue an error, rather than a warning, in the
future.
- You cannot use 'asm' in this way in a function _definition_; but you
-can get the same effect by writing a declaration for the function before
-its definition and putting 'asm' there, like this:
+ You cannot use `asm' in this way in a function _definition_; but you
+can get the same effect by writing a declaration for the function
+before its definition and putting `asm' there, like this:
extern func () asm ("FUNC");
@@ -32006,19 +32385,20 @@ register variable should be allocated.
* Local register variables in specific registers do not reserve the
registers, except at the point where they are used as input or
- output operands in an 'asm' statement and the 'asm' statement
+ output operands in an `asm' statement and the `asm' statement
itself is not deleted. The compiler's data flow analysis is
capable of determining where the specified registers contain live
values, and where they are available for other uses. Stores into
- local register variables may be deleted when they appear to be dead
- according to dataflow analysis. References to local register
+ local register variables may be deleted when they appear to be
+ dead according to dataflow analysis. References to local register
variables may be deleted or moved or simplified.
These local variables are sometimes convenient for use with the
- extended 'asm' feature (*note Extended Asm::), if you want to write
- one output of the assembler instruction directly into a particular
- register. (This works provided the register you specify fits the
- constraints specified for that operand in the 'asm'.)
+ extended `asm' feature (*note Extended Asm::), if you want to
+ write one output of the assembler instruction directly into a
+ particular register. (This works provided the register you
+ specify fits the constraints specified for that operand in the
+ `asm'.)
* Menu:
@@ -32035,19 +32415,19 @@ You can define a global register variable in GNU C like this:
register int *foo asm ("a5");
-Here 'a5' is the name of the register that should be used. Choose a
+Here `a5' is the name of the register that should be used. Choose a
register that is normally saved and restored by function calls on your
machine, so that library routines will not clobber it.
Naturally the register name is CPU-dependent, so you need to
-conditionalize your program according to CPU type. The register 'a5' is
-a good choice on a 68000 for a variable of pointer type. On machines
-with register windows, be sure to choose a "global" register that is not
-affected magically by the function call mechanism.
+conditionalize your program according to CPU type. The register `a5'
+is a good choice on a 68000 for a variable of pointer type. On
+machines with register windows, be sure to choose a "global" register
+that is not affected magically by the function call mechanism.
In addition, different operating systems on the same CPU may differ in
how they name the registers; then you need additional conditionals. For
-example, some 68000 operating systems call this register '%a5'.
+example, some 68000 operating systems call this register `%a5'.
Eventually there may be a way of asking the compiler to choose a
register automatically, but first we need to figure out how it should
@@ -32067,20 +32447,20 @@ library routines may temporarily use the register for other things
(unless you recompile them specially for the task at hand).
It is not safe for one function that uses a global register variable to
-call another such function 'foo' by way of a third function 'lose' that
+call another such function `foo' by way of a third function `lose' that
is compiled without knowledge of this variable (i.e. in a different
source file in which the variable isn't declared). This is because
-'lose' might save the register and put some other value there. For
+`lose' might save the register and put some other value there. For
example, you can't expect a global register variable to be available in
-the comparison-function that you pass to 'qsort', since 'qsort' might
+the comparison-function that you pass to `qsort', since `qsort' might
have put something else in that register. (If you are prepared to
-recompile 'qsort' with the same global register variable, you can solve
+recompile `qsort' with the same global register variable, you can solve
this problem.)
- If you want to recompile 'qsort' or other source files that do not
+ If you want to recompile `qsort' or other source files that do not
actually use your global register variable, so that they do not use that
register for any other purpose, then it suffices to specify the compiler
-option '-ffixed-REG'. You need not actually add a global register
+option `-ffixed-REG'. You need not actually add a global register
declaration to their source code.
A function that can alter the value of a global register variable
@@ -32090,13 +32470,13 @@ return. Therefore, the function that is the entry point into the part
of the program that uses the global register variable must explicitly
save and restore the value that belongs to its caller.
- On most machines, 'longjmp' restores to each global register variable
-the value it had at the time of the 'setjmp'. On some machines,
-however, 'longjmp' does not change the value of global register
-variables. To be portable, the function that called 'setjmp' should
+ On most machines, `longjmp' restores to each global register variable
+the value it had at the time of the `setjmp'. On some machines,
+however, `longjmp' does not change the value of global register
+variables. To be portable, the function that called `setjmp' should
make other arrangements to save the values of the global register
-variables, and to restore them in a 'longjmp'. This way, the same thing
-happens regardless of what 'longjmp' does.
+variables, and to restore them in a `longjmp'. This way, the same
+thing happens regardless of what `longjmp' does.
All global register variable declarations must precede all function
definitions. If such a declaration could appear after function
@@ -32107,9 +32487,9 @@ from being used for other purposes in the preceding functions.
executable file has no means to supply initial contents for a register.
On the SPARC, there are reports that g3 ... g7 are suitable registers,
-but certain library functions, such as 'getwd', as well as the
-subroutines for division and remainder, modify g3 and g4. g1 and g2 are
-local temporaries.
+but certain library functions, such as `getwd', as well as the
+subroutines for division and remainder, modify g3 and g4. g1 and g2
+are local temporaries.
On the 68000, a2 ... a5 should be suitable, as should d2 ... d7. Of
course, it does not do to use more than a few of those.
@@ -32125,9 +32505,9 @@ this:
register int *foo asm ("a5");
-Here 'a5' is the name of the register that should be used. Note that
-this is the same syntax used for defining global register variables, but
-for a local variable it appears within a function.
+Here `a5' is the name of the register that should be used. Note that
+this is the same syntax used for defining global register variables,
+but for a local variable it appears within a function.
Naturally the register name is CPU-dependent, but this is not a
problem, since specific registers are most often useful with explicit
@@ -32137,7 +32517,7 @@ type.
In addition, operating systems on one type of CPU may differ in how
they name the registers; then you need additional conditionals. For
-example, some 68000 operating systems call this register '%a5'.
+example, some 68000 operating systems call this register `%a5'.
Defining such a register variable does not reserve the register; it
remains available for other uses in places where flow control determines
@@ -32146,23 +32526,23 @@ the variable's value is not live.
This option does not guarantee that GCC generates code that has this
variable in the register you specify at all times. You may not code an
explicit reference to this register in the assembler instruction
-template part of an 'asm' statement and assume it always refers to this
+template part of an `asm' statement and assume it always refers to this
variable. However, using the variable as an input or output operand to
-the 'asm' guarantees that the specified register is used for that
+the `asm' guarantees that the specified register is used for that
operand. *Note Extended Asm::, for more information.
- Stores into local register variables may be deleted when they appear to
-be dead according to dataflow analysis. References to local register
-variables may be deleted or moved or simplified.
+ Stores into local register variables may be deleted when they appear
+to be dead according to dataflow analysis. References to local
+register variables may be deleted or moved or simplified.
As with global register variables, it is recommended that you choose a
register that is normally saved and restored by function calls on your
machine, so that library routines will not clobber it.
- Sometimes when writing inline 'asm' code, you need to make an operand
+ Sometimes when writing inline `asm' code, you need to make an operand
be a specific register, but there's no matching constraint letter for
-that register. To force the operand into that register, create a local
-variable and specify the register in the variable's declaration. Then
+that register. To force the operand into that register, create a local
+variable and specify the register in the variable's declaration. Then
use the local variable for the asm operand and specify any constraint
letter that matches the register:
@@ -32174,7 +32554,7 @@ letter that matches the register:
_Warning:_ In the above example, be aware that a register (for example
r0) can be call-clobbered by subsequent code, including function calls
and library calls for arithmetic operators on other variables (for
-example the initialization of p2). In this case, use temporary
+example the initialization of p2). In this case, use temporary
variables for expressions between the register assignments:
int t1 = ...;
@@ -32186,19 +32566,19 @@ variables for expressions between the register assignments:

File: gcc.info, Node: Size of an asm, Prev: Explicit Reg Vars, Up: Using Assembly Language with C
-6.43.6 Size of an 'asm'
+6.43.6 Size of an `asm'
-----------------------
-Some targets require that GCC track the size of each instruction used in
-order to generate correct code. Because the final length of the code
-produced by an 'asm' statement is only known by the assembler, GCC must
-make an estimate as to how big it will be. It does this by counting the
-number of instructions in the pattern of the 'asm' and multiplying that
-by the length of the longest instruction supported by that processor.
-(When working out the number of instructions, it assumes that any
-occurrence of a newline or of whatever statement separator character is
-supported by the assembler - typically ';' -- indicates the end of an
-instruction.)
+Some targets require that GCC track the size of each instruction used
+in order to generate correct code. Because the final length of the
+code produced by an `asm' statement is only known by the assembler, GCC
+must make an estimate as to how big it will be. It does this by
+counting the number of instructions in the pattern of the `asm' and
+multiplying that by the length of the longest instruction supported by
+that processor. (When working out the number of instructions, it
+assumes that any occurrence of a newline or of whatever statement
+separator character is supported by the assembler - typically `;' --
+indicates the end of an instruction.)
Normally, GCC's estimate is adequate to ensure that correct code is
generated, but it is possible to confuse the compiler if you use pseudo
@@ -32214,20 +32594,20 @@ File: gcc.info, Node: Alternate Keywords, Next: Incomplete Enums, Prev: Using
6.44 Alternate Keywords
=======================
-'-ansi' and the various '-std' options disable certain keywords. This
+`-ansi' and the various `-std' options disable certain keywords. This
causes trouble when you want to use GNU C extensions, or a
general-purpose header file that should be usable by all programs,
-including ISO C programs. The keywords 'asm', 'typeof' and 'inline' are
-not available in programs compiled with '-ansi' or '-std' (although
-'inline' can be used in a program compiled with '-std=c99' or
-'-std=c11'). The ISO C99 keyword 'restrict' is only available when
-'-std=gnu99' (which will eventually be the default) or '-std=c99' (or
-the equivalent '-std=iso9899:1999'), or an option for a later standard
+including ISO C programs. The keywords `asm', `typeof' and `inline'
+are not available in programs compiled with `-ansi' or `-std' (although
+`inline' can be used in a program compiled with `-std=c99' or
+`-std=c11'). The ISO C99 keyword `restrict' is only available when
+`-std=gnu99' (which will eventually be the default) or `-std=c99' (or
+the equivalent `-std=iso9899:1999'), or an option for a later standard
version, is used.
- The way to solve these problems is to put '__' at the beginning and end
-of each problematical keyword. For example, use '__asm__' instead of
-'asm', and '__inline__' instead of 'inline'.
+ The way to solve these problems is to put `__' at the beginning and
+end of each problematical keyword. For example, use `__asm__' instead
+of `asm', and `__inline__' instead of `inline'.
Other C compilers won't accept these alternative keywords; if you want
to compile with another compiler, you can define the alternate keywords
@@ -32238,27 +32618,27 @@ this:
#define __asm__ asm
#endif
- '-pedantic' and other options cause warnings for many GNU C extensions.
+ `-pedantic' and other options cause warnings for many GNU C extensions.
You can prevent such warnings within one expression by writing
-'__extension__' before the expression. '__extension__' has no effect
+`__extension__' before the expression. `__extension__' has no effect
aside from this.

File: gcc.info, Node: Incomplete Enums, Next: Function Names, Prev: Alternate Keywords, Up: C Extensions
-6.45 Incomplete 'enum' Types
+6.45 Incomplete `enum' Types
============================
-You can define an 'enum' tag without specifying its possible values.
+You can define an `enum' tag without specifying its possible values.
This results in an incomplete type, much like what you get if you write
-'struct foo' without describing the elements. A later declaration that
+`struct foo' without describing the elements. A later declaration that
does specify the possible values completes the type.
You can't allocate variables or storage using the type while it is
incomplete. However, you can work with pointers to that type.
This extension may not be very useful, but it makes the handling of
-'enum' more consistent with the way 'struct' and 'union' are handled.
+`enum' more consistent with the way `struct' and `union' are handled.
This extension is not supported by GNU C++.
@@ -32269,23 +32649,23 @@ File: gcc.info, Node: Function Names, Next: Return Address, Prev: Incomplete
==============================
GCC provides three magic variables that hold the name of the current
-function, as a string. The first of these is '__func__', which is part
+function, as a string. The first of these is `__func__', which is part
of the C99 standard:
- The identifier '__func__' is implicitly declared by the translator as
-if, immediately following the opening brace of each function definition,
-the declaration
+ The identifier `__func__' is implicitly declared by the translator as
+if, immediately following the opening brace of each function
+definition, the declaration
static const char __func__[] = "function-name";
appeared, where function-name is the name of the lexically-enclosing
function. This name is the unadorned name of the function.
- '__FUNCTION__' is another name for '__func__', provided for backward
+ `__FUNCTION__' is another name for `__func__', provided for backward
compatibility with old versions of GCC.
- In C, '__PRETTY_FUNCTION__' is yet another name for '__func__'.
-However, in C++, '__PRETTY_FUNCTION__' contains the type signature of
+ In C, `__PRETTY_FUNCTION__' is yet another name for `__func__'.
+However, in C++, `__PRETTY_FUNCTION__' contains the type signature of
the function as well as its bare name. For example, this program:
extern "C" {
@@ -32315,7 +32695,7 @@ gives this output:
__PRETTY_FUNCTION__ = void a::sub(int)
These identifiers are variables, not preprocessor macros, and may not
-be used to initialize 'char' arrays or be concatenated with other string
+be used to initialize `char' arrays or be concatenated with other string
literals.

@@ -32331,47 +32711,47 @@ function.
LEVEL)
This function returns the return address of the current function,
or of one of its callers. The LEVEL argument is number of frames
- to scan up the call stack. A value of '0' yields the return
- address of the current function, a value of '1' yields the return
+ to scan up the call stack. A value of `0' yields the return
+ address of the current function, a value of `1' yields the return
address of the caller of the current function, and so forth. When
inlining the expected behavior is that the function returns the
address of the function that is returned to. To work around this
- behavior use the 'noinline' function attribute.
+ behavior use the `noinline' function attribute.
The LEVEL argument must be a constant integer.
On some machines it may be impossible to determine the return
address of any function other than the current one; in such cases,
or when the top of the stack has been reached, this function
- returns '0' or a random value. In addition,
- '__builtin_frame_address' may be used to determine if the top of
+ returns `0' or a random value. In addition,
+ `__builtin_frame_address' may be used to determine if the top of
the stack has been reached.
Additional post-processing of the returned value may be needed, see
- '__builtin_extract_return_addr'.
+ `__builtin_extract_return_addr'.
This function should only be used with a nonzero argument for
debugging purposes.
-- Built-in Function: void * __builtin_extract_return_addr (void *ADDR)
- The address as returned by '__builtin_return_address' may have to
+ The address as returned by `__builtin_return_address' may have to
be fed through this function to get the actual encoded address.
- For example, on the 31-bit S/390 platform the highest bit has to be
- masked out, or on SPARC platforms an offset has to be added for the
- true next instruction to be executed.
+ For example, on the 31-bit S/390 platform the highest bit has to
+ be masked out, or on SPARC platforms an offset has to be added for
+ the true next instruction to be executed.
If no fixup is needed, this function simply passes through ADDR.
-- Built-in Function: void * __builtin_frob_return_address (void *ADDR)
- This function does the reverse of '__builtin_extract_return_addr'.
+ This function does the reverse of `__builtin_extract_return_addr'.
-- Built-in Function: void * __builtin_frame_address (unsigned int
LEVEL)
- This function is similar to '__builtin_return_address', but it
+ This function is similar to `__builtin_return_address', but it
returns the address of the function frame rather than the return
- address of the function. Calling '__builtin_frame_address' with a
- value of '0' yields the frame address of the current function, a
- value of '1' yields the frame address of the caller of the current
+ address of the function. Calling `__builtin_frame_address' with a
+ value of `0' yields the frame address of the current function, a
+ value of `1' yields the frame address of the caller of the current
function, and so forth.
The frame is the area on the stack that holds local variables and
@@ -32380,13 +32760,13 @@ function.
exact definition depends upon the processor and the calling
convention. If the processor has a dedicated frame pointer
register, and the function has a frame, then
- '__builtin_frame_address' returns the value of the frame pointer
+ `__builtin_frame_address' returns the value of the frame pointer
register.
On some machines it may be impossible to determine the frame
address of any function other than the current one; in such cases,
or when the top of the stack has been reached, this function
- returns '0' if the first frame pointer is properly initialized by
+ returns `0' if the first frame pointer is properly initialized by
the startup code.
This function should only be used with a nonzero argument for
@@ -32404,40 +32784,40 @@ same time. For example, on the x86 the MMX, 3DNow! and SSE extensions
can be used this way.
The first step in using these extensions is to provide the necessary
-data types. This should be done using an appropriate 'typedef':
+data types. This should be done using an appropriate `typedef':
typedef int v4si __attribute__ ((vector_size (16)));
-The 'int' type specifies the base type, while the attribute specifies
+The `int' type specifies the base type, while the attribute specifies
the vector size for the variable, measured in bytes. For example, the
-declaration above causes the compiler to set the mode for the 'v4si'
-type to be 16 bytes wide and divided into 'int' sized units. For a
-32-bit 'int' this means a vector of 4 units of 4 bytes, and the
-corresponding mode of 'foo' is V4SI.
+declaration above causes the compiler to set the mode for the `v4si'
+type to be 16 bytes wide and divided into `int' sized units. For a
+32-bit `int' this means a vector of 4 units of 4 bytes, and the
+corresponding mode of `foo' is V4SI.
- The 'vector_size' attribute is only applicable to integral and float
+ The `vector_size' attribute is only applicable to integral and float
scalars, although arrays, pointers, and function return values are
-allowed in conjunction with this construct. Only sizes that are a power
+allowed in conjunction with this construct. Only sizes that are a power
of two are currently allowed.
All the basic integer types can be used as base types, both as signed
-and as unsigned: 'char', 'short', 'int', 'long', 'long long'. In
-addition, 'float' and 'double' can be used to build floating-point
+and as unsigned: `char', `short', `int', `long', `long long'. In
+addition, `float' and `double' can be used to build floating-point
vector types.
Specifying a combination that is not valid for the current architecture
causes GCC to synthesize the instructions using a narrower mode. For
-example, if you specify a variable of type 'V4SI' and your architecture
+example, if you specify a variable of type `V4SI' and your architecture
does not allow for this specific SIMD type, GCC produces code that uses
-4 'SIs'.
+4 `SIs'.
The types defined in this manner can be used with a subset of normal C
operations. Currently, GCC allows using the following operators on
-these types: '+, -, *, /, unary minus, ^, |, &, ~, %'.
+these types: `+, -, *, /, unary minus, ^, |, &, ~, %'.
- The operations behave like C++ 'valarrays'. Addition is defined as the
-addition of the corresponding elements of the operands. For example, in
-the code below, each of the 4 elements in A is added to the
+ The operations behave like C++ `valarrays'. Addition is defined as
+the addition of the corresponding elements of the operands. For
+example, in the code below, each of the 4 elements in A is added to the
corresponding 4 elements in B and the resulting vector is stored in C.
typedef int v4si __attribute__ ((vector_size (16)));
@@ -32452,15 +32832,15 @@ minus or complement operators on a vector type is a vector whose
elements are the negative or complemented values of the corresponding
elements in the operand.
- It is possible to use shifting operators '<<', '>>' on integer-type
-vectors. The operation is defined as following: '{a0, a1, ..., an} >>
-{b0, b1, ..., bn} == {a0 >> b0, a1 >> b1, ..., an >> bn}'. Vector
+ It is possible to use shifting operators `<<', `>>' on integer-type
+vectors. The operation is defined as following: `{a0, a1, ..., an} >>
+{b0, b1, ..., bn} == {a0 >> b0, a1 >> b1, ..., an >> bn}'. Vector
operands must have the same number of elements.
For convenience, it is allowed to use a binary vector operation where
-one operand is a scalar. In that case the compiler transforms the
+one operand is a scalar. In that case the compiler transforms the
scalar operand into a vector where each element is the scalar from the
-operation. The transformation happens only if the scalar could be
+operation. The transformation happens only if the scalar could be
safely converted to the vector-element type. Consider the following
code.
@@ -32474,21 +32854,21 @@ code.
a = l + a; /* Error, cannot convert long to int. */
- Vectors can be subscripted as if the vector were an array with the same
-number of elements and base type. Out of bound accesses invoke
+ Vectors can be subscripted as if the vector were an array with the
+same number of elements and base type. Out of bound accesses invoke
undefined behavior at run time. Warnings for out of bound accesses for
-vector subscription can be enabled with '-Warray-bounds'.
+vector subscription can be enabled with `-Warray-bounds'.
- Vector comparison is supported with standard comparison operators: '==,
-!=, <, <=, >, >='. Comparison operands can be vector expressions of
-integer-type or real-type. Comparison between integer-type vectors and
-real-type vectors are not supported. The result of the comparison is a
-vector of the same width and number of elements as the comparison
+ Vector comparison is supported with standard comparison operators:
+`==, !=, <, <=, >, >='. Comparison operands can be vector expressions
+of integer-type or real-type. Comparison between integer-type vectors
+and real-type vectors are not supported. The result of the comparison
+is a vector of the same width and number of elements as the comparison
operands with a signed integral element type.
Vectors are compared element-wise producing 0 when comparison is false
and -1 (constant of the appropriate type where all bits are set)
-otherwise. Consider the following example.
+otherwise. Consider the following example.
typedef int v4si __attribute__ ((vector_size (16)));
@@ -32499,31 +32879,31 @@ otherwise. Consider the following example.
c = a > b; /* The result would be {0, 0,-1, 0} */
c = a == b; /* The result would be {0,-1, 0,-1} */
- In C++, the ternary operator '?:' is available. 'a?b:c', where 'b' and
-'c' are vectors of the same type and 'a' is an integer vector with the
-same number of elements of the same size as 'b' and 'c', computes all
-three arguments and creates a vector '{a[0]?b[0]:c[0], a[1]?b[1]:c[1],
-...}'. Note that unlike in OpenCL, 'a' is thus interpreted as 'a != 0'
-and not 'a < 0'. As in the case of binary operations, this syntax is
-also accepted when one of 'b' or 'c' is a scalar that is then
-transformed into a vector. If both 'b' and 'c' are scalars and the type
-of 'true?b:c' has the same size as the element type of 'a', then 'b' and
-'c' are converted to a vector type whose elements have this type and
-with the same number of elements as 'a'.
-
- In C++, the logic operators '!, &&, ||' are available for vectors.
-'!v' is equivalent to 'v == 0', 'a && b' is equivalent to 'a!=0 & b!=0'
-and 'a || b' is equivalent to 'a!=0 | b!=0'. For mixed operations
-between a scalar 's' and a vector 'v', 's && v' is equivalent to
-'s?v!=0:0' (the evaluation is short-circuit) and 'v && s' is equivalent
-to 'v!=0 & (s?-1:0)'.
-
- Vector shuffling is available using functions '__builtin_shuffle (vec,
-mask)' and '__builtin_shuffle (vec0, vec1, mask)'. Both functions
-construct a permutation of elements from one or two vectors and return a
-vector of the same type as the input vector(s). The MASK is an integral
-vector with the same width (W) and element count (N) as the output
-vector.
+ In C++, the ternary operator `?:' is available. `a?b:c', where `b' and
+`c' are vectors of the same type and `a' is an integer vector with the
+same number of elements of the same size as `b' and `c', computes all
+three arguments and creates a vector `{a[0]?b[0]:c[0], a[1]?b[1]:c[1],
+...}'. Note that unlike in OpenCL, `a' is thus interpreted as `a != 0'
+and not `a < 0'. As in the case of binary operations, this syntax is
+also accepted when one of `b' or `c' is a scalar that is then
+transformed into a vector. If both `b' and `c' are scalars and the type
+of `true?b:c' has the same size as the element type of `a', then `b'
+and `c' are converted to a vector type whose elements have this type
+and with the same number of elements as `a'.
+
+ In C++, the logic operators `!, &&, ||' are available for vectors.
+`!v' is equivalent to `v == 0', `a && b' is equivalent to `a!=0 & b!=0'
+and `a || b' is equivalent to `a!=0 | b!=0'. For mixed operations
+between a scalar `s' and a vector `v', `s && v' is equivalent to
+`s?v!=0:0' (the evaluation is short-circuit) and `v && s' is equivalent
+to `v!=0 & (s?-1:0)'.
+
+ Vector shuffling is available using functions `__builtin_shuffle (vec,
+mask)' and `__builtin_shuffle (vec0, vec1, mask)'. Both functions
+construct a permutation of elements from one or two vectors and return
+a vector of the same type as the input vector(s). The MASK is an
+integral vector with the same width (W) and element count (N) as the
+output vector.
The elements of the input vectors are numbered in memory ordering of
VEC0 beginning at 0 and VEC1 beginning at N. The elements of MASK are
@@ -32543,12 +32923,12 @@ two-operand case.
res = __builtin_shuffle (a, mask1); /* res is {1,2,2,4} */
res = __builtin_shuffle (a, b, mask2); /* res is {1,5,3,6} */
- Note that '__builtin_shuffle' is intentionally semantically compatible
-with the OpenCL 'shuffle' and 'shuffle2' functions.
+ Note that `__builtin_shuffle' is intentionally semantically compatible
+with the OpenCL `shuffle' and `shuffle2' functions.
You can declare variables and use them in function calls and returns,
-as well as in assignments and some casts. You can specify a vector type
-as a return type for a function. Vector types can also be used as
+as well as in assignments and some casts. You can specify a vector
+type as a return type for a function. Vector types can also be used as
function arguments. It is possible to cast from one vector type to
another, provided they are of the same size (in fact, you can also cast
vectors to and from other datatypes of the same size).
@@ -32559,50 +32939,50 @@ signedness without a cast.

File: gcc.info, Node: Offsetof, Next: __sync Builtins, Prev: Vector Extensions, Up: C Extensions
-6.49 Support for 'offsetof'
+6.49 Support for `offsetof'
===========================
-GCC implements for both C and C++ a syntactic extension to implement the
-'offsetof' macro.
+GCC implements for both C and C++ a syntactic extension to implement
+the `offsetof' macro.
primary:
- "__builtin_offsetof" "(" typename "," offsetof_member_designator ")"
+ "__builtin_offsetof" "(" `typename' "," offsetof_member_designator ")"
offsetof_member_designator:
- identifier
- | offsetof_member_designator "." identifier
- | offsetof_member_designator "[" expr "]"
+ `identifier'
+ | offsetof_member_designator "." `identifier'
+ | offsetof_member_designator "[" `expr' "]"
This extension is sufficient such that
#define offsetof(TYPE, MEMBER) __builtin_offsetof (TYPE, MEMBER)
-is a suitable definition of the 'offsetof' macro. In C++, TYPE may be
+is a suitable definition of the `offsetof' macro. In C++, TYPE may be
dependent. In either case, MEMBER may consist of a single identifier,
or a sequence of member accesses and array references.

File: gcc.info, Node: __sync Builtins, Next: __atomic Builtins, Prev: Offsetof, Up: C Extensions
-6.50 Legacy '__sync' Built-in Functions for Atomic Memory Access
+6.50 Legacy `__sync' Built-in Functions for Atomic Memory Access
================================================================
The following built-in functions are intended to be compatible with
-those described in the 'Intel Itanium Processor-specific Application
+those described in the `Intel Itanium Processor-specific Application
Binary Interface', section 7.4. As such, they depart from the normal
-GCC practice of using the '__builtin_' prefix, and further that they are
-overloaded such that they work on multiple types.
+GCC practice of using the `__builtin_' prefix, and further that they
+are overloaded such that they work on multiple types.
- The definition given in the Intel documentation allows only for the use
-of the types 'int', 'long', 'long long' as well as their unsigned
-counterparts. GCC allows any integral scalar or pointer type that is 1,
-2, 4 or 8 bytes in length.
+ The definition given in the Intel documentation allows only for the
+use of the types `int', `long', `long long' as well as their unsigned
+counterparts. GCC allows any integral scalar or pointer type that is
+1, 2, 4 or 8 bytes in length.
Not all operations are supported by all target processors. If a
particular operation cannot be implemented on the target processor, a
warning is generated and a call to an external function is generated.
The external function carries the same name as the built-in version,
-with an additional suffix '_N' where N is the size of the data type.
+with an additional suffix `_N' where N is the size of the data type.
In most cases, these built-in functions are considered a "full
barrier". That is, no memory operand is moved across the operation,
@@ -32612,19 +32992,19 @@ operation and from queuing stores after the operation.
All of the routines are described in the Intel documentation to take
"an optional list of variables protected by the memory barrier". It's
-not clear what is meant by that; it could mean that _only_ the following
-variables are protected, or it could mean that these variables should in
-addition be protected. At present GCC ignores this list and protects
-all variables that are globally accessible. If in the future we make
-some use of this list, an empty list will continue to mean all globally
-accessible variables.
-
-'TYPE __sync_fetch_and_add (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_fetch_and_sub (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_fetch_and_or (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_fetch_and_and (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_fetch_and_xor (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_fetch_and_nand (TYPE *ptr, TYPE value, ...)'
+not clear what is meant by that; it could mean that _only_ the
+following variables are protected, or it could mean that these variables
+should in addition be protected. At present GCC ignores this list and
+protects all variables that are globally accessible. If in the future
+we make some use of this list, an empty list will continue to mean all
+globally accessible variables.
+
+`TYPE __sync_fetch_and_add (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_fetch_and_sub (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_fetch_and_or (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_fetch_and_and (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_fetch_and_xor (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_fetch_and_nand (TYPE *ptr, TYPE value, ...)'
These built-in functions perform the operation suggested by the
name, and returns the value that had previously been in memory.
That is,
@@ -32632,48 +33012,48 @@ accessible variables.
{ tmp = *ptr; *ptr OP= value; return tmp; }
{ tmp = *ptr; *ptr = ~(tmp & value); return tmp; } // nand
- _Note:_ GCC 4.4 and later implement '__sync_fetch_and_nand' as
- '*ptr = ~(tmp & value)' instead of '*ptr = ~tmp & value'.
+ _Note:_ GCC 4.4 and later implement `__sync_fetch_and_nand' as
+ `*ptr = ~(tmp & value)' instead of `*ptr = ~tmp & value'.
-'TYPE __sync_add_and_fetch (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_sub_and_fetch (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_or_and_fetch (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_and_and_fetch (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_xor_and_fetch (TYPE *ptr, TYPE value, ...)'
-'TYPE __sync_nand_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_add_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_sub_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_or_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_and_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_xor_and_fetch (TYPE *ptr, TYPE value, ...)'
+`TYPE __sync_nand_and_fetch (TYPE *ptr, TYPE value, ...)'
These built-in functions perform the operation suggested by the
name, and return the new value. That is,
{ *ptr OP= value; return *ptr; }
{ *ptr = ~(*ptr & value); return *ptr; } // nand
- _Note:_ GCC 4.4 and later implement '__sync_nand_and_fetch' as
- '*ptr = ~(*ptr & value)' instead of '*ptr = ~*ptr & value'.
+ _Note:_ GCC 4.4 and later implement `__sync_nand_and_fetch' as
+ `*ptr = ~(*ptr & value)' instead of `*ptr = ~*ptr & value'.
-'bool __sync_bool_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)'
-'TYPE __sync_val_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)'
+`bool __sync_bool_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)'
+`TYPE __sync_val_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)'
These built-in functions perform an atomic compare and swap. That
- is, if the current value of '*PTR' is OLDVAL, then write NEWVAL
- into '*PTR'.
+ is, if the current value of `*PTR' is OLDVAL, then write NEWVAL
+ into `*PTR'.
The "bool" version returns true if the comparison is successful and
NEWVAL is written. The "val" version returns the contents of
- '*PTR' before the operation.
+ `*PTR' before the operation.
-'__sync_synchronize (...)'
+`__sync_synchronize (...)'
This built-in function issues a full memory barrier.
-'TYPE __sync_lock_test_and_set (TYPE *ptr, TYPE value, ...)'
- This built-in function, as described by Intel, is not a traditional
- test-and-set operation, but rather an atomic exchange operation.
- It writes VALUE into '*PTR', and returns the previous contents of
- '*PTR'.
+`TYPE __sync_lock_test_and_set (TYPE *ptr, TYPE value, ...)'
+ This built-in function, as described by Intel, is not a
+ traditional test-and-set operation, but rather an atomic exchange
+ operation. It writes VALUE into `*PTR', and returns the previous
+ contents of `*PTR'.
Many targets have only minimal support for such locks, and do not
support a full exchange operation. In this case, a target may
support reduced functionality here by which the _only_ valid value
to store is the immediate constant 1. The exact value actually
- stored in '*PTR' is implementation defined.
+ stored in `*PTR' is implementation defined.
This built-in function is not a full barrier, but rather an
"acquire barrier". This means that references after the operation
@@ -32681,16 +33061,16 @@ accessible variables.
previous memory stores may not be globally visible yet, and
previous memory loads may not yet be satisfied.
-'void __sync_lock_release (TYPE *ptr, ...)'
+`void __sync_lock_release (TYPE *ptr, ...)'
This built-in function releases the lock acquired by
- '__sync_lock_test_and_set'. Normally this means writing the
- constant 0 to '*PTR'.
+ `__sync_lock_test_and_set'. Normally this means writing the
+ constant 0 to `*PTR'.
- This built-in function is not a full barrier, but rather a "release
- barrier". This means that all previous memory stores are globally
- visible, and all previous memory loads have been satisfied, but
- following memory reads are not prevented from being speculated to
- before the barrier.
+ This built-in function is not a full barrier, but rather a
+ "release barrier". This means that all previous memory stores are
+ globally visible, and all previous memory loads have been
+ satisfied, but following memory reads are not prevented from being
+ speculated to before the barrier.

File: gcc.info, Node: __atomic Builtins, Next: Integer Overflow Builtins, Prev: __sync Builtins, Up: C Extensions
@@ -32699,18 +33079,18 @@ File: gcc.info, Node: __atomic Builtins, Next: Integer Overflow Builtins, Pre
================================================================
The following built-in functions approximately match the requirements
-for C++11 memory model. Many are similar to the '__sync' prefixed
+for C++11 memory model. Many are similar to the `__sync' prefixed
built-in functions, but all also have a memory model parameter. These
-are all identified by being prefixed with '__atomic', and most are
+are all identified by being prefixed with `__atomic', and most are
overloaded such that they work with multiple types.
GCC allows any integral scalar or pointer type that is 1, 2, 4, or 8
-bytes in length. 16-byte integral types are also allowed if '__int128'
+bytes in length. 16-byte integral types are also allowed if `__int128'
(*note __int128::) is supported by the architecture.
Target architectures are encouraged to provide their own patterns for
each of these built-in functions. If no target is provided, the
-original non-memory model set of '__sync' atomic built-in functions are
+original non-memory model set of `__sync' atomic built-in functions are
utilized, along with any required synchronization fences surrounding it
in order to achieve the proper behavior. Execution in this case is
subject to the same restrictions as those built-in functions.
@@ -32723,50 +33103,55 @@ to be resolved at run time.
compare_exchange) all have a generic version as well. This generic
version works on any data type. If the data type size maps to one of
the integral sizes that may have lock free support, the generic version
-utilizes the lock free built-in function. Otherwise an external call is
-left to be resolved at run time. This external call is the same format
-with the addition of a 'size_t' parameter inserted as the first
+utilizes the lock free built-in function. Otherwise an external call
+is left to be resolved at run time. This external call is the same
+format with the addition of a `size_t' parameter inserted as the first
parameter indicating the size of the object being pointed to. All
objects must be the same size.
There are 6 different memory models that can be specified. These map
-to the same names in the C++11 standard. Refer there or to the GCC wiki
-on atomic synchronization
+to the same names in the C++11 standard. Refer there or to the GCC
+wiki on atomic synchronization
(http://gcc.gnu.org/wiki/Atomic/GCCMM/AtomicSync) for more detailed
-definitions. These memory models integrate both barriers to code motion
-as well as synchronization requirements with other threads. These are
-listed in approximately ascending order of strength. It is also
-possible to use target specific flags for memory model flags, like
+definitions. These memory models integrate both barriers to code
+motion as well as synchronization requirements with other threads.
+These are listed in approximately ascending order of strength. It is
+also possible to use target specific flags for memory model flags, like
Hardware Lock Elision.
-'__ATOMIC_RELAXED'
+`__ATOMIC_RELAXED'
No barriers or synchronization.
-'__ATOMIC_CONSUME'
+
+`__ATOMIC_CONSUME'
Data dependency only for both barrier and synchronization with
another thread.
-'__ATOMIC_ACQUIRE'
+
+`__ATOMIC_ACQUIRE'
Barrier to hoisting of code and synchronizes with release (or
stronger) semantic stores from another thread.
-'__ATOMIC_RELEASE'
+
+`__ATOMIC_RELEASE'
Barrier to sinking of code and synchronizes with acquire (or
stronger) semantic loads from another thread.
-'__ATOMIC_ACQ_REL'
- Full barrier in both directions and synchronizes with acquire loads
- and release stores in another thread.
-'__ATOMIC_SEQ_CST'
- Full barrier in both directions and synchronizes with acquire loads
- and release stores in all threads.
+
+`__ATOMIC_ACQ_REL'
+ Full barrier in both directions and synchronizes with acquire
+ loads and release stores in another thread.
+
+`__ATOMIC_SEQ_CST'
+ Full barrier in both directions and synchronizes with acquire
+ loads and release stores in all threads.
When implementing patterns for these built-in functions, the memory
model parameter can be ignored as long as the pattern implements the
-most restrictive '__ATOMIC_SEQ_CST' model. Any of the other memory
-models execute correctly with this memory model but they may not execute
-as efficiently as they could with a more appropriate implementation of
-the relaxed requirements.
+most restrictive `__ATOMIC_SEQ_CST' model. Any of the other memory
+models execute correctly with this memory model but they may not
+execute as efficiently as they could with a more appropriate
+implementation of the relaxed requirements.
Note that the C++11 standard allows for the memory model parameter to
be determined at run time rather than at compile time. These built-in
-functions map any run-time value to '__ATOMIC_SEQ_CST' rather than
+functions map any run-time value to `__ATOMIC_SEQ_CST' rather than
invoke a runtime library call or inline a switch statement. This is
standard compliant, safe, and the simplest approach for now.
@@ -32777,154 +33162,163 @@ values ensures proper usage.
-- Built-in Function: TYPE __atomic_load_n (TYPE *ptr, int memmodel)
This built-in function implements an atomic load operation. It
- returns the contents of '*PTR'.
+ returns the contents of `*PTR'.
+
+ The valid memory model variants are `__ATOMIC_RELAXED',
+ `__ATOMIC_SEQ_CST', `__ATOMIC_ACQUIRE', and `__ATOMIC_CONSUME'.
- The valid memory model variants are '__ATOMIC_RELAXED',
- '__ATOMIC_SEQ_CST', '__ATOMIC_ACQUIRE', and '__ATOMIC_CONSUME'.
-- Built-in Function: void __atomic_load (TYPE *ptr, TYPE *ret, int
memmodel)
This is the generic version of an atomic load. It returns the
- contents of '*PTR' in '*RET'.
+ contents of `*PTR' in `*RET'.
+
-- Built-in Function: void __atomic_store_n (TYPE *ptr, TYPE val, int
memmodel)
This built-in function implements an atomic store operation. It
- writes 'VAL' into '*PTR'.
+ writes `VAL' into `*PTR'.
+
+ The valid memory model variants are `__ATOMIC_RELAXED',
+ `__ATOMIC_SEQ_CST', and `__ATOMIC_RELEASE'.
- The valid memory model variants are '__ATOMIC_RELAXED',
- '__ATOMIC_SEQ_CST', and '__ATOMIC_RELEASE'.
-- Built-in Function: void __atomic_store (TYPE *ptr, TYPE *val, int
memmodel)
This is the generic version of an atomic store. It stores the
- value of '*VAL' into '*PTR'.
+ value of `*VAL' into `*PTR'.
+
-- Built-in Function: TYPE __atomic_exchange_n (TYPE *ptr, TYPE val,
int memmodel)
- This built-in function implements an atomic exchange operation. It
- writes VAL into '*PTR', and returns the previous contents of
- '*PTR'.
+ This built-in function implements an atomic exchange operation.
+ It writes VAL into `*PTR', and returns the previous contents of
+ `*PTR'.
+
+ The valid memory model variants are `__ATOMIC_RELAXED',
+ `__ATOMIC_SEQ_CST', `__ATOMIC_ACQUIRE', `__ATOMIC_RELEASE', and
+ `__ATOMIC_ACQ_REL'.
- The valid memory model variants are '__ATOMIC_RELAXED',
- '__ATOMIC_SEQ_CST', '__ATOMIC_ACQUIRE', '__ATOMIC_RELEASE', and
- '__ATOMIC_ACQ_REL'.
-- Built-in Function: void __atomic_exchange (TYPE *ptr, TYPE *val,
TYPE *ret, int memmodel)
This is the generic version of an atomic exchange. It stores the
- contents of '*VAL' into '*PTR'. The original value of '*PTR' is
- copied into '*RET'.
+ contents of `*VAL' into `*PTR'. The original value of `*PTR' is
+ copied into `*RET'.
+
- -- Built-in Function: bool __atomic_compare_exchange_n (TYPE *ptr, TYPE
- *expected, TYPE desired, bool weak, int success_memmodel, int
- failure_memmodel)
+ -- Built-in Function: bool __atomic_compare_exchange_n (TYPE *ptr,
+ TYPE *expected, TYPE desired, bool weak, int
+ success_memmodel, int failure_memmodel)
This built-in function implements an atomic compare and exchange
- operation. This compares the contents of '*PTR' with the contents
- of '*EXPECTED' and if equal, writes DESIRED into '*PTR'. If they
- are not equal, the current contents of '*PTR' is written into
- '*EXPECTED'. WEAK is true for weak compare_exchange, and false for
- the strong variation. Many targets only offer the strong variation
- and ignore the parameter. When in doubt, use the strong variation.
-
- True is returned if DESIRED is written into '*PTR' and the
- execution is considered to conform to the memory model specified by
- SUCCESS_MEMMODEL. There are no restrictions on what memory model
- can be used here.
+ operation. This compares the contents of `*PTR' with the contents
+ of `*EXPECTED' and if equal, writes DESIRED into `*PTR'. If they
+ are not equal, the current contents of `*PTR' is written into
+ `*EXPECTED'. WEAK is true for weak compare_exchange, and false
+ for the strong variation. Many targets only offer the strong
+ variation and ignore the parameter. When in doubt, use the strong
+ variation.
+
+ True is returned if DESIRED is written into `*PTR' and the
+ execution is considered to conform to the memory model specified
+ by SUCCESS_MEMMODEL. There are no restrictions on what memory
+ model can be used here.
False is returned otherwise, and the execution is considered to
- conform to FAILURE_MEMMODEL. This memory model cannot be
- '__ATOMIC_RELEASE' nor '__ATOMIC_ACQ_REL'. It also cannot be a
+ conform to FAILURE_MEMMODEL. This memory model cannot be
+ `__ATOMIC_RELEASE' nor `__ATOMIC_ACQ_REL'. It also cannot be a
stronger model than that specified by SUCCESS_MEMMODEL.
+
-- Built-in Function: bool __atomic_compare_exchange (TYPE *ptr, TYPE
- *expected, TYPE *desired, bool weak, int success_memmodel, int
- failure_memmodel)
+ *expected, TYPE *desired, bool weak, int success_memmodel,
+ int failure_memmodel)
This built-in function implements the generic version of
- '__atomic_compare_exchange'. The function is virtually identical
- to '__atomic_compare_exchange_n', except the desired value is also
+ `__atomic_compare_exchange'. The function is virtually identical
+ to `__atomic_compare_exchange_n', except the desired value is also
a pointer.
- -- Built-in Function: TYPE __atomic_add_fetch (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_sub_fetch (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_and_fetch (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_xor_fetch (TYPE *ptr, TYPE val, int
- memmodel)
+
+ -- Built-in Function: TYPE __atomic_add_fetch (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_sub_fetch (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_and_fetch (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_xor_fetch (TYPE *ptr, TYPE val,
+ int memmodel)
-- Built-in Function: TYPE __atomic_or_fetch (TYPE *ptr, TYPE val, int
memmodel)
-- Built-in Function: TYPE __atomic_nand_fetch (TYPE *ptr, TYPE val,
int memmodel)
These built-in functions perform the operation suggested by the
- name, and return the result of the operation. That is,
+ name, and return the result of the operation. That is,
{ *ptr OP= val; return *ptr; }
All memory models are valid.
- -- Built-in Function: TYPE __atomic_fetch_add (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_fetch_sub (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_fetch_and (TYPE *ptr, TYPE val, int
- memmodel)
- -- Built-in Function: TYPE __atomic_fetch_xor (TYPE *ptr, TYPE val, int
- memmodel)
+
+ -- Built-in Function: TYPE __atomic_fetch_add (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_fetch_sub (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_fetch_and (TYPE *ptr, TYPE val,
+ int memmodel)
+ -- Built-in Function: TYPE __atomic_fetch_xor (TYPE *ptr, TYPE val,
+ int memmodel)
-- Built-in Function: TYPE __atomic_fetch_or (TYPE *ptr, TYPE val, int
memmodel)
-- Built-in Function: TYPE __atomic_fetch_nand (TYPE *ptr, TYPE val,
int memmodel)
These built-in functions perform the operation suggested by the
- name, and return the value that had previously been in '*PTR'.
+ name, and return the value that had previously been in `*PTR'.
That is,
{ tmp = *ptr; *ptr OP= val; return tmp; }
All memory models are valid.
+
-- Built-in Function: bool __atomic_test_and_set (void *ptr, int
memmodel)
-
This built-in function performs an atomic test-and-set operation on
- the byte at '*PTR'. The byte is set to some implementation defined
- nonzero "set" value and the return value is 'true' if and only if
- the previous contents were "set". It should be only used for
- operands of type 'bool' or 'char'. For other types only part of
- the value may be set.
+ the byte at `*PTR'. The byte is set to some implementation
+ defined nonzero "set" value and the return value is `true' if and
+ only if the previous contents were "set". It should be only used
+ for operands of type `bool' or `char'. For other types only part
+ of the value may be set.
All memory models are valid.
- -- Built-in Function: void __atomic_clear (bool *ptr, int memmodel)
+ -- Built-in Function: void __atomic_clear (bool *ptr, int memmodel)
This built-in function performs an atomic clear operation on
- '*PTR'. After the operation, '*PTR' contains 0. It should be only
- used for operands of type 'bool' or 'char' and in conjunction with
- '__atomic_test_and_set'. For other types it may only clear
- partially. If the type is not 'bool' prefer using
- '__atomic_store'.
+ `*PTR'. After the operation, `*PTR' contains 0. It should be
+ only used for operands of type `bool' or `char' and in conjunction
+ with `__atomic_test_and_set'. For other types it may only clear
+ partially. If the type is not `bool' prefer using `__atomic_store'.
- The valid memory model variants are '__ATOMIC_RELAXED',
- '__ATOMIC_SEQ_CST', and '__ATOMIC_RELEASE'.
+ The valid memory model variants are `__ATOMIC_RELAXED',
+ `__ATOMIC_SEQ_CST', and `__ATOMIC_RELEASE'.
- -- Built-in Function: void __atomic_thread_fence (int memmodel)
+ -- Built-in Function: void __atomic_thread_fence (int memmodel)
This built-in function acts as a synchronization fence between
threads based on the specified memory model.
All memory orders are valid.
- -- Built-in Function: void __atomic_signal_fence (int memmodel)
+ -- Built-in Function: void __atomic_signal_fence (int memmodel)
This built-in function acts as a synchronization fence between a
thread and signal handlers based in the same thread.
All memory orders are valid.
- -- Built-in Function: bool __atomic_always_lock_free (size_t size, void
- *ptr)
+ -- Built-in Function: bool __atomic_always_lock_free (size_t size,
+ void *ptr)
This built-in function returns true if objects of SIZE bytes always
generate lock free atomic instructions for the target architecture.
SIZE must resolve to a compile-time constant and the result also
@@ -32936,13 +33330,13 @@ values ensures proper usage.
if (_atomic_always_lock_free (sizeof (long long), 0))
+
-- Built-in Function: bool __atomic_is_lock_free (size_t size, void
*ptr)
-
This built-in function returns true if objects of SIZE bytes always
- generate lock free atomic instructions for the target architecture.
- If it is not known to be lock free a call is made to a runtime
- routine named '__atomic_is_lock_free'.
+ generate lock free atomic instructions for the target
+ architecture. If it is not known to be lock free a call is made
+ to a runtime routine named `__atomic_is_lock_free'.
PTR is an optional pointer to the object that may be used to
determine alignment. A value of 0 indicates typical alignment
@@ -32971,7 +33365,6 @@ operations together with checking whether the operations overflowed.
a, unsigned long int b, unsigned long int *res)
-- Built-in Function: bool __builtin_uaddll_overflow (unsigned long
long int a, unsigned long long int b, unsigned long int *res)
-
These built-in functions promote the first two operands into
infinite precision signed type and perform addition on those
promoted operands. The result is then cast to the type the third
@@ -32989,6 +33382,7 @@ operations together with checking whether the operations overflowed.
these built-in functions where possible, like conditional jump on
overflow after addition, conditional jump on carry etc.
+
-- Built-in Function: bool __builtin_sub_overflow (TYPE1 a, TYPE2 b,
TYPE3 *res)
-- Built-in Function: bool __builtin_ssub_overflow (int a, int b, int
@@ -33003,10 +33397,11 @@ operations together with checking whether the operations overflowed.
a, unsigned long int b, unsigned long int *res)
-- Built-in Function: bool __builtin_usubll_overflow (unsigned long
long int a, unsigned long long int b, unsigned long int *res)
-
These built-in functions are similar to the add overflow checking
- built-in functions above, except they perform subtraction, subtract
- the second argument from the first one, instead of addition.
+ built-in functions above, except they perform subtraction,
+ subtract the second argument from the first one, instead of
+ addition.
+
-- Built-in Function: bool __builtin_mul_overflow (TYPE1 a, TYPE2 b,
TYPE3 *res)
@@ -33022,11 +33417,11 @@ operations together with checking whether the operations overflowed.
a, unsigned long int b, unsigned long int *res)
-- Built-in Function: bool __builtin_umulll_overflow (unsigned long
long int a, unsigned long long int b, unsigned long int *res)
-
These built-in functions are similar to the add overflow checking
built-in functions above, except they perform multiplication,
instead of addition.
+

File: gcc.info, Node: x86 specific memory model extensions for transactional memory, Next: Object Size Checking, Prev: Integer Overflow Builtins, Up: C Extensions
@@ -33037,15 +33432,16 @@ The x86 architecture supports additional memory ordering flags to mark
lock critical sections for hardware lock elision. These must be
specified in addition to an existing memory model to atomic intrinsics.
-'__ATOMIC_HLE_ACQUIRE'
+`__ATOMIC_HLE_ACQUIRE'
Start lock elision on a lock variable. Memory model must be
- '__ATOMIC_ACQUIRE' or stronger.
-'__ATOMIC_HLE_RELEASE'
+ `__ATOMIC_ACQUIRE' or stronger.
+
+`__ATOMIC_HLE_RELEASE'
End lock elision on a lock variable. Memory model must be
- '__ATOMIC_RELEASE' or stronger.
+ `__ATOMIC_RELEASE' or stronger.
When a lock acquire fails it is required for good performance to abort
-the transaction quickly. This can be done with a '_mm_pause'
+the transaction quickly. This can be done with a `_mm_pause'
#include <immintrin.h> // For _mm_pause
@@ -33071,16 +33467,16 @@ prevent some buffer overflow attacks.
TYPE)
is a built-in construct that returns a constant number of bytes
from PTR to the end of the object PTR pointer points to (if known
- at compile time). '__builtin_object_size' never evaluates its
- arguments for side-effects. If there are any side-effects in them,
- it returns '(size_t) -1' for TYPE 0 or 1 and '(size_t) 0' for TYPE
- 2 or 3. If there are multiple objects PTR can point to and all of
- them are known at compile time, the returned number is the maximum
- of remaining byte counts in those objects if TYPE & 2 is 0 and
- minimum if nonzero. If it is not possible to determine which
- objects PTR points to at compile time, '__builtin_object_size'
- should return '(size_t) -1' for TYPE 0 or 1 and '(size_t) 0' for
- TYPE 2 or 3.
+ at compile time). `__builtin_object_size' never evaluates its
+ arguments for side-effects. If there are any side-effects in
+ them, it returns `(size_t) -1' for TYPE 0 or 1 and `(size_t) 0'
+ for TYPE 2 or 3. If there are multiple objects PTR can point to
+ and all of them are known at compile time, the returned number is
+ the maximum of remaining byte counts in those objects if TYPE & 2
+ is 0 and minimum if nonzero. If it is not possible to determine
+ which objects PTR points to at compile time,
+ `__builtin_object_size' should return `(size_t) -1' for TYPE 0 or
+ 1 and `(size_t) 0' for TYPE 2 or 3.
TYPE is an integer constant from 0 to 3. If the least significant
bit is clear, objects are whole variables, if it is set, a closest
@@ -33102,15 +33498,15 @@ prevent some buffer overflow attacks.
assert (__builtin_object_size (q, 1) == sizeof (var.b));
There are built-in functions added for many common string operation
-functions, e.g., for 'memcpy' '__builtin___memcpy_chk' built-in is
+functions, e.g., for `memcpy' `__builtin___memcpy_chk' built-in is
provided. This built-in has an additional last argument, which is the
number of bytes remaining in object the DEST argument points to or
-'(size_t) -1' if the size is not known.
+`(size_t) -1' if the size is not known.
The built-in functions are optimized into the normal string functions
-like 'memcpy' if the last argument is '(size_t) -1' or if it is known at
-compile time that the destination object will not be overflown. If the
-compiler can determine at compile time the object will be always
+like `memcpy' if the last argument is `(size_t) -1' or if it is known
+at compile time that the destination object will not be overflown. If
+the compiler can determine at compile time the object will be always
overflown, it issues a warning.
The intended use can be e.g.
@@ -33137,9 +33533,9 @@ overflown, it issues a warning.
will abort the program at run time. */
memcpy (&buf[6], "abcde", 5);
- Such built-in functions are provided for 'memcpy', 'mempcpy',
-'memmove', 'memset', 'strcpy', 'stpcpy', 'strncpy', 'strcat' and
-'strncat'.
+ Such built-in functions are provided for `memcpy', `mempcpy',
+`memmove', `memset', `strcpy', `stpcpy', `strncpy', `strcat' and
+`strncat'.
There are also checking built-in functions for formatted output
functions.
@@ -33151,22 +33547,22 @@ functions.
int __builtin___vsnprintf_chk (char *s, size_t maxlen, int flag, size_t os,
const char *fmt, va_list ap);
- The added FLAG argument is passed unchanged to '__sprintf_chk' etc.
+ The added FLAG argument is passed unchanged to `__sprintf_chk' etc.
functions and can contain implementation specific flags on what
additional security measures the checking function might take, such as
-handling '%n' differently.
+handling `%n' differently.
The OS argument is the object size S points to, like in the other
-built-in functions. There is a small difference in the behavior though,
-if OS is '(size_t) -1', the built-in functions are optimized into the
-non-checking functions only if FLAG is 0, otherwise the checking
-function is called with OS argument set to '(size_t) -1'.
+built-in functions. There is a small difference in the behavior
+though, if OS is `(size_t) -1', the built-in functions are optimized
+into the non-checking functions only if FLAG is 0, otherwise the
+checking function is called with OS argument set to `(size_t) -1'.
In addition to this, there are checking built-in functions
-'__builtin___printf_chk', '__builtin___vprintf_chk',
-'__builtin___fprintf_chk' and '__builtin___vfprintf_chk'. These have
+`__builtin___printf_chk', `__builtin___vprintf_chk',
+`__builtin___fprintf_chk' and `__builtin___vfprintf_chk'. These have
just one additional argument, FLAG, right before format string FMT. If
-the compiler is able to optimize them to 'fputc' etc. functions, it
+the compiler is able to optimize them to `fputc' etc. functions, it
does, otherwise the checking function is called and the FLAG argument
passed to it.
@@ -33179,12 +33575,11 @@ File: gcc.info, Node: Pointer Bounds Checker builtins, Next: Cilk Plus Builtin
GCC provides a set of built-in functions to control Pointer Bounds
Checker instrumentation. Note that all Pointer Bounds Checker builtins
can be used even if you compile with Pointer Bounds Checker off
-('-fno-check-pointer-bounds'). The behavior may differ in such case as
+(`-fno-check-pointer-bounds'). The behavior may differ in such case as
documented below.
- -- Built-in Function: void * __builtin___bnd_set_ptr_bounds (const void
- *Q, size_t SIZE)
-
+ -- Built-in Function: void * __builtin___bnd_set_ptr_bounds (const
+ void *Q, size_t SIZE)
This built-in function returns a new pointer with the value of Q,
and associate it with the bounds [Q, Q+SIZE-1]. With Pointer
Bounds Checker off, the built-in function just returns the first
@@ -33197,9 +33592,9 @@ documented below.
return __builtin___bnd_set_ptr_bounds (p, n);
}
+
-- Built-in Function: void * __builtin___bnd_narrow_ptr_bounds (const
void *P, const void *Q, size_t SIZE)
-
This built-in function returns a new pointer with the value of P
and associates it with the narrowed bounds formed by the
intersection of bounds associated with Q and the bounds [P, P +
@@ -33216,9 +33611,9 @@ documented below.
sizeof(object)));
}
+
-- Built-in Function: void * __builtin___bnd_copy_ptr_bounds (const
void *Q, const void *R)
-
This built-in function returns a new pointer with the value of Q,
and associates it with the bounds already associated with pointer
R. With Pointer Bounds Checker off, the built-in function just
@@ -33229,25 +33624,25 @@ documented below.
int *field_ptr = __builtin___bnd_copy_ptr_bounds (&objptr->int_field,
objptr);
+
-- Built-in Function: void * __builtin___bnd_init_ptr_bounds (const
void *Q)
-
This built-in function returns a new pointer with the value of Q,
and associates it with INIT (allowing full memory access) bounds.
- With Pointer Bounds Checker off, the built-in function just returns
- the first argument.
+ With Pointer Bounds Checker off, the built-in function just
+ returns the first argument.
+
-- Built-in Function: void * __builtin___bnd_null_ptr_bounds (const
void *Q)
-
This built-in function returns a new pointer with the value of Q,
and associates it with NULL (allowing no memory access) bounds.
- With Pointer Bounds Checker off, the built-in function just returns
- the first argument.
+ With Pointer Bounds Checker off, the built-in function just
+ returns the first argument.
- -- Built-in Function: void __builtin___bnd_store_ptr_bounds (const void
- **PTR_ADDR, const void *PTR_VAL)
+ -- Built-in Function: void __builtin___bnd_store_ptr_bounds (const
+ void **PTR_ADDR, const void *PTR_VAL)
This built-in function stores the bounds associated with pointer
PTR_VAL and location PTR_ADDR into Bounds Table. This can be
useful to propagate bounds from legacy code without touching the
@@ -33255,9 +33650,9 @@ documented below.
With Pointer Bounds Checker off, the built-in function call is
ignored.
+
-- Built-in Function: void __builtin___bnd_chk_ptr_lbounds (const void
*Q)
-
This built-in function checks if the pointer Q is within the lower
bound of its associated bounds. With Pointer Bounds Checker off,
the built-in function call is ignored.
@@ -33273,16 +33668,16 @@ documented below.
return dst;
}
+
-- Built-in Function: void __builtin___bnd_chk_ptr_ubounds (const void
*Q)
-
This built-in function checks if the pointer Q is within the upper
bound of its associated bounds. With Pointer Bounds Checker off,
the built-in function call is ignored.
+
-- Built-in Function: void __builtin___bnd_chk_ptr_bounds (const void
*Q, size_t SIZE)
-
This built-in function checks if [Q, Q + SIZE - 1] is within the
lower and upper bounds associated with Q. With Pointer Bounds
Checker off, the built-in function call is ignored.
@@ -33298,24 +33693,25 @@ documented below.
return dst;
}
+
-- Built-in Function: const void * __builtin___bnd_get_ptr_lbound
(const void *Q)
-
This built-in function returns the lower bound associated with the
pointer Q, as a pointer value. This is useful for debugging using
- 'printf'. With Pointer Bounds Checker off, the built-in function
+ `printf'. With Pointer Bounds Checker off, the built-in function
returns 0.
void *lb = __builtin___bnd_get_ptr_lbound (q);
void *ub = __builtin___bnd_get_ptr_ubound (q);
printf ("q = %p lb(q) = %p ub(q) = %p", q, lb, ub);
+
-- Built-in Function: const void * __builtin___bnd_get_ptr_ubound
(const void *Q)
+ This built-in function returns the upper bound (which is a
+ pointer) associated with the pointer Q. With Pointer Bounds
+ Checker off, the built-in function returns -1.
- This built-in function returns the upper bound (which is a pointer)
- associated with the pointer Q. With Pointer Bounds Checker off,
- the built-in function returns -1.

File: gcc.info, Node: Cilk Plus Builtins, Next: Other Builtins, Prev: Pointer Bounds Checker builtins, Up: C Extensions
@@ -33324,26 +33720,38 @@ File: gcc.info, Node: Cilk Plus Builtins, Next: Other Builtins, Prev: Pointer
==========================================================
GCC provides support for the following built-in reduction functions if
-Cilk Plus is enabled. Cilk Plus can be enabled using the '-fcilkplus'
+Cilk Plus is enabled. Cilk Plus can be enabled using the `-fcilkplus'
flag.
- * '__sec_implicit_index'
- * '__sec_reduce'
- * '__sec_reduce_add'
- * '__sec_reduce_all_nonzero'
- * '__sec_reduce_all_zero'
- * '__sec_reduce_any_nonzero'
- * '__sec_reduce_any_zero'
- * '__sec_reduce_max'
- * '__sec_reduce_min'
- * '__sec_reduce_max_ind'
- * '__sec_reduce_min_ind'
- * '__sec_reduce_mul'
- * '__sec_reduce_mutating'
+ * `__sec_implicit_index'
+
+ * `__sec_reduce'
+
+ * `__sec_reduce_add'
+
+ * `__sec_reduce_all_nonzero'
+
+ * `__sec_reduce_all_zero'
+
+ * `__sec_reduce_any_nonzero'
+
+ * `__sec_reduce_any_zero'
+
+ * `__sec_reduce_max'
+
+ * `__sec_reduce_min'
+
+ * `__sec_reduce_max_ind'
+
+ * `__sec_reduce_min_ind'
+
+ * `__sec_reduce_mul'
+
+ * `__sec_reduce_mutating'
Further details and examples about these built-in functions are
described in the Cilk Plus language manual which can be found at
-<http://www.cilkplus.org>.
+`http://www.cilkplus.org'.

File: gcc.info, Node: Other Builtins, Next: Target Builtins, Prev: Cilk Plus Builtins, Up: C Extensions
@@ -33360,103 +33768,103 @@ general use of these functions.
The remaining functions are provided for optimization purposes.
GCC includes built-in versions of many of the functions in the standard
-C library. The versions prefixed with '__builtin_' are always treated
-as having the same meaning as the C library function even if you specify
-the '-fno-builtin' option. (*note C Dialect Options::) Many of these
-functions are only optimized in certain cases; if they are not optimized
-in a particular case, a call to the library function is emitted.
-
- Outside strict ISO C mode ('-ansi', '-std=c90', '-std=c99' or
-'-std=c11'), the functions '_exit', 'alloca', 'bcmp', 'bzero',
-'dcgettext', 'dgettext', 'dremf', 'dreml', 'drem', 'exp10f', 'exp10l',
-'exp10', 'ffsll', 'ffsl', 'ffs', 'fprintf_unlocked', 'fputs_unlocked',
-'gammaf', 'gammal', 'gamma', 'gammaf_r', 'gammal_r', 'gamma_r',
-'gettext', 'index', 'isascii', 'j0f', 'j0l', 'j0', 'j1f', 'j1l', 'j1',
-'jnf', 'jnl', 'jn', 'lgammaf_r', 'lgammal_r', 'lgamma_r', 'mempcpy',
-'pow10f', 'pow10l', 'pow10', 'printf_unlocked', 'rindex', 'scalbf',
-'scalbl', 'scalb', 'signbit', 'signbitf', 'signbitl', 'signbitd32',
-'signbitd64', 'signbitd128', 'significandf', 'significandl',
-'significand', 'sincosf', 'sincosl', 'sincos', 'stpcpy', 'stpncpy',
-'strcasecmp', 'strdup', 'strfmon', 'strncasecmp', 'strndup', 'toascii',
-'y0f', 'y0l', 'y0', 'y1f', 'y1l', 'y1', 'ynf', 'ynl' and 'yn' may be
+C library. The versions prefixed with `__builtin_' are always treated
+as having the same meaning as the C library function even if you
+specify the `-fno-builtin' option. (*note C Dialect Options::) Many of
+these functions are only optimized in certain cases; if they are not
+optimized in a particular case, a call to the library function is
+emitted.
+
+ Outside strict ISO C mode (`-ansi', `-std=c90', `-std=c99' or
+`-std=c11'), the functions `_exit', `alloca', `bcmp', `bzero',
+`dcgettext', `dgettext', `dremf', `dreml', `drem', `exp10f', `exp10l',
+`exp10', `ffsll', `ffsl', `ffs', `fprintf_unlocked', `fputs_unlocked',
+`gammaf', `gammal', `gamma', `gammaf_r', `gammal_r', `gamma_r',
+`gettext', `index', `isascii', `j0f', `j0l', `j0', `j1f', `j1l', `j1',
+`jnf', `jnl', `jn', `lgammaf_r', `lgammal_r', `lgamma_r', `mempcpy',
+`pow10f', `pow10l', `pow10', `printf_unlocked', `rindex', `scalbf',
+`scalbl', `scalb', `signbit', `signbitf', `signbitl', `signbitd32',
+`signbitd64', `signbitd128', `significandf', `significandl',
+`significand', `sincosf', `sincosl', `sincos', `stpcpy', `stpncpy',
+`strcasecmp', `strdup', `strfmon', `strncasecmp', `strndup', `toascii',
+`y0f', `y0l', `y0', `y1f', `y1l', `y1', `ynf', `ynl' and `yn' may be
handled as built-in functions. All these functions have corresponding
-versions prefixed with '__builtin_', which may be used even in strict
+versions prefixed with `__builtin_', which may be used even in strict
C90 mode.
- The ISO C99 functions '_Exit', 'acoshf', 'acoshl', 'acosh', 'asinhf',
-'asinhl', 'asinh', 'atanhf', 'atanhl', 'atanh', 'cabsf', 'cabsl',
-'cabs', 'cacosf', 'cacoshf', 'cacoshl', 'cacosh', 'cacosl', 'cacos',
-'cargf', 'cargl', 'carg', 'casinf', 'casinhf', 'casinhl', 'casinh',
-'casinl', 'casin', 'catanf', 'catanhf', 'catanhl', 'catanh', 'catanl',
-'catan', 'cbrtf', 'cbrtl', 'cbrt', 'ccosf', 'ccoshf', 'ccoshl', 'ccosh',
-'ccosl', 'ccos', 'cexpf', 'cexpl', 'cexp', 'cimagf', 'cimagl', 'cimag',
-'clogf', 'clogl', 'clog', 'conjf', 'conjl', 'conj', 'copysignf',
-'copysignl', 'copysign', 'cpowf', 'cpowl', 'cpow', 'cprojf', 'cprojl',
-'cproj', 'crealf', 'creall', 'creal', 'csinf', 'csinhf', 'csinhl',
-'csinh', 'csinl', 'csin', 'csqrtf', 'csqrtl', 'csqrt', 'ctanf',
-'ctanhf', 'ctanhl', 'ctanh', 'ctanl', 'ctan', 'erfcf', 'erfcl', 'erfc',
-'erff', 'erfl', 'erf', 'exp2f', 'exp2l', 'exp2', 'expm1f', 'expm1l',
-'expm1', 'fdimf', 'fdiml', 'fdim', 'fmaf', 'fmal', 'fmaxf', 'fmaxl',
-'fmax', 'fma', 'fminf', 'fminl', 'fmin', 'hypotf', 'hypotl', 'hypot',
-'ilogbf', 'ilogbl', 'ilogb', 'imaxabs', 'isblank', 'iswblank',
-'lgammaf', 'lgammal', 'lgamma', 'llabs', 'llrintf', 'llrintl', 'llrint',
-'llroundf', 'llroundl', 'llround', 'log1pf', 'log1pl', 'log1p', 'log2f',
-'log2l', 'log2', 'logbf', 'logbl', 'logb', 'lrintf', 'lrintl', 'lrint',
-'lroundf', 'lroundl', 'lround', 'nearbyintf', 'nearbyintl', 'nearbyint',
-'nextafterf', 'nextafterl', 'nextafter', 'nexttowardf', 'nexttowardl',
-'nexttoward', 'remainderf', 'remainderl', 'remainder', 'remquof',
-'remquol', 'remquo', 'rintf', 'rintl', 'rint', 'roundf', 'roundl',
-'round', 'scalblnf', 'scalblnl', 'scalbln', 'scalbnf', 'scalbnl',
-'scalbn', 'snprintf', 'tgammaf', 'tgammal', 'tgamma', 'truncf',
-'truncl', 'trunc', 'vfscanf', 'vscanf', 'vsnprintf' and 'vsscanf' are
-handled as built-in functions except in strict ISO C90 mode ('-ansi' or
-'-std=c90').
-
- There are also built-in versions of the ISO C99 functions 'acosf',
-'acosl', 'asinf', 'asinl', 'atan2f', 'atan2l', 'atanf', 'atanl',
-'ceilf', 'ceill', 'cosf', 'coshf', 'coshl', 'cosl', 'expf', 'expl',
-'fabsf', 'fabsl', 'floorf', 'floorl', 'fmodf', 'fmodl', 'frexpf',
-'frexpl', 'ldexpf', 'ldexpl', 'log10f', 'log10l', 'logf', 'logl',
-'modfl', 'modf', 'powf', 'powl', 'sinf', 'sinhf', 'sinhl', 'sinl',
-'sqrtf', 'sqrtl', 'tanf', 'tanhf', 'tanhl' and 'tanl' that are
+ The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf',
+`asinhl', `asinh', `atanhf', `atanhl', `atanh', `cabsf', `cabsl',
+`cabs', `cacosf', `cacoshf', `cacoshl', `cacosh', `cacosl', `cacos',
+`cargf', `cargl', `carg', `casinf', `casinhf', `casinhl', `casinh',
+`casinl', `casin', `catanf', `catanhf', `catanhl', `catanh', `catanl',
+`catan', `cbrtf', `cbrtl', `cbrt', `ccosf', `ccoshf', `ccoshl',
+`ccosh', `ccosl', `ccos', `cexpf', `cexpl', `cexp', `cimagf', `cimagl',
+`cimag', `clogf', `clogl', `clog', `conjf', `conjl', `conj',
+`copysignf', `copysignl', `copysign', `cpowf', `cpowl', `cpow',
+`cprojf', `cprojl', `cproj', `crealf', `creall', `creal', `csinf',
+`csinhf', `csinhl', `csinh', `csinl', `csin', `csqrtf', `csqrtl',
+`csqrt', `ctanf', `ctanhf', `ctanhl', `ctanh', `ctanl', `ctan',
+`erfcf', `erfcl', `erfc', `erff', `erfl', `erf', `exp2f', `exp2l',
+`exp2', `expm1f', `expm1l', `expm1', `fdimf', `fdiml', `fdim', `fmaf',
+`fmal', `fmaxf', `fmaxl', `fmax', `fma', `fminf', `fminl', `fmin',
+`hypotf', `hypotl', `hypot', `ilogbf', `ilogbl', `ilogb', `imaxabs',
+`isblank', `iswblank', `lgammaf', `lgammal', `lgamma', `llabs',
+`llrintf', `llrintl', `llrint', `llroundf', `llroundl', `llround',
+`log1pf', `log1pl', `log1p', `log2f', `log2l', `log2', `logbf',
+`logbl', `logb', `lrintf', `lrintl', `lrint', `lroundf', `lroundl',
+`lround', `nearbyintf', `nearbyintl', `nearbyint', `nextafterf',
+`nextafterl', `nextafter', `nexttowardf', `nexttowardl', `nexttoward',
+`remainderf', `remainderl', `remainder', `remquof', `remquol',
+`remquo', `rintf', `rintl', `rint', `roundf', `roundl', `round',
+`scalblnf', `scalblnl', `scalbln', `scalbnf', `scalbnl', `scalbn',
+`snprintf', `tgammaf', `tgammal', `tgamma', `truncf', `truncl', `trunc',
+`vfscanf', `vscanf', `vsnprintf' and `vsscanf' are handled as built-in
+functions except in strict ISO C90 mode (`-ansi' or `-std=c90').
+
+ There are also built-in versions of the ISO C99 functions `acosf',
+`acosl', `asinf', `asinl', `atan2f', `atan2l', `atanf', `atanl',
+`ceilf', `ceill', `cosf', `coshf', `coshl', `cosl', `expf', `expl',
+`fabsf', `fabsl', `floorf', `floorl', `fmodf', `fmodl', `frexpf',
+`frexpl', `ldexpf', `ldexpl', `log10f', `log10l', `logf', `logl',
+`modfl', `modf', `powf', `powl', `sinf', `sinhf', `sinhl', `sinl',
+`sqrtf', `sqrtl', `tanf', `tanhf', `tanhl' and `tanl' that are
recognized in any mode since ISO C90 reserves these names for the
purpose to which ISO C99 puts them. All these functions have
-corresponding versions prefixed with '__builtin_'.
-
- The ISO C94 functions 'iswalnum', 'iswalpha', 'iswcntrl', 'iswdigit',
-'iswgraph', 'iswlower', 'iswprint', 'iswpunct', 'iswspace', 'iswupper',
-'iswxdigit', 'towlower' and 'towupper' are handled as built-in functions
-except in strict ISO C90 mode ('-ansi' or '-std=c90').
-
- The ISO C90 functions 'abort', 'abs', 'acos', 'asin', 'atan2', 'atan',
-'calloc', 'ceil', 'cosh', 'cos', 'exit', 'exp', 'fabs', 'floor', 'fmod',
-'fprintf', 'fputs', 'frexp', 'fscanf', 'isalnum', 'isalpha', 'iscntrl',
-'isdigit', 'isgraph', 'islower', 'isprint', 'ispunct', 'isspace',
-'isupper', 'isxdigit', 'tolower', 'toupper', 'labs', 'ldexp', 'log10',
-'log', 'malloc', 'memchr', 'memcmp', 'memcpy', 'memset', 'modf', 'pow',
-'printf', 'putchar', 'puts', 'scanf', 'sinh', 'sin', 'snprintf',
-'sprintf', 'sqrt', 'sscanf', 'strcat', 'strchr', 'strcmp', 'strcpy',
-'strcspn', 'strlen', 'strncat', 'strncmp', 'strncpy', 'strpbrk',
-'strrchr', 'strspn', 'strstr', 'tanh', 'tan', 'vfprintf', 'vprintf' and
-'vsprintf' are all recognized as built-in functions unless
-'-fno-builtin' is specified (or '-fno-builtin-FUNCTION' is specified for
-an individual function). All of these functions have corresponding
-versions prefixed with '__builtin_'.
+corresponding versions prefixed with `__builtin_'.
+
+ The ISO C94 functions `iswalnum', `iswalpha', `iswcntrl', `iswdigit',
+`iswgraph', `iswlower', `iswprint', `iswpunct', `iswspace', `iswupper',
+`iswxdigit', `towlower' and `towupper' are handled as built-in functions
+except in strict ISO C90 mode (`-ansi' or `-std=c90').
+
+ The ISO C90 functions `abort', `abs', `acos', `asin', `atan2', `atan',
+`calloc', `ceil', `cosh', `cos', `exit', `exp', `fabs', `floor', `fmod',
+`fprintf', `fputs', `frexp', `fscanf', `isalnum', `isalpha', `iscntrl',
+`isdigit', `isgraph', `islower', `isprint', `ispunct', `isspace',
+`isupper', `isxdigit', `tolower', `toupper', `labs', `ldexp', `log10',
+`log', `malloc', `memchr', `memcmp', `memcpy', `memset', `modf', `pow',
+`printf', `putchar', `puts', `scanf', `sinh', `sin', `snprintf',
+`sprintf', `sqrt', `sscanf', `strcat', `strchr', `strcmp', `strcpy',
+`strcspn', `strlen', `strncat', `strncmp', `strncpy', `strpbrk',
+`strrchr', `strspn', `strstr', `tanh', `tan', `vfprintf', `vprintf' and
+`vsprintf' are all recognized as built-in functions unless
+`-fno-builtin' is specified (or `-fno-builtin-FUNCTION' is specified
+for an individual function). All of these functions have corresponding
+versions prefixed with `__builtin_'.
GCC provides built-in versions of the ISO C99 floating-point comparison
macros that avoid raising exceptions for unordered operands. They have
-the same names as the standard macros ( 'isgreater', 'isgreaterequal',
-'isless', 'islessequal', 'islessgreater', and 'isunordered') , with
-'__builtin_' prefixed. We intend for a library implementor to be able
-to simply '#define' each standard macro to its built-in equivalent. In
-the same fashion, GCC provides 'fpclassify', 'isfinite', 'isinf_sign'
-and 'isnormal' built-ins used with '__builtin_' prefixed. The 'isinf'
-and 'isnan' built-in functions appear both with and without the
-'__builtin_' prefix.
+the same names as the standard macros ( `isgreater', `isgreaterequal',
+`isless', `islessequal', `islessgreater', and `isunordered') , with
+`__builtin_' prefixed. We intend for a library implementor to be able
+to simply `#define' each standard macro to its built-in equivalent. In
+the same fashion, GCC provides `fpclassify', `isfinite', `isinf_sign'
+and `isnormal' built-ins used with `__builtin_' prefixed. The `isinf'
+and `isnan' built-in functions appear both with and without the
+`__builtin_' prefix.
-- Built-in Function: int __builtin_types_compatible_p (TYPE1, TYPE2)
-
- You can use the built-in function '__builtin_types_compatible_p' to
+ You can use the built-in function `__builtin_types_compatible_p' to
determine whether two types are the same.
This built-in function returns 1 if the unqualified versions of the
@@ -33464,21 +33872,21 @@ and 'isnan' built-in functions appear both with and without the
compatible, 0 otherwise. The result of this built-in function can
be used in integer constant expressions.
- This built-in function ignores top level qualifiers (e.g., 'const',
- 'volatile'). For example, 'int' is equivalent to 'const int'.
+ This built-in function ignores top level qualifiers (e.g., `const',
+ `volatile'). For example, `int' is equivalent to `const int'.
- The type 'int[]' and 'int[5]' are compatible. On the other hand,
- 'int' and 'char *' are not compatible, even if the size of their
+ The type `int[]' and `int[5]' are compatible. On the other hand,
+ `int' and `char *' are not compatible, even if the size of their
types, on the particular architecture are the same. Also, the
amount of pointer indirection is taken into account when
- determining similarity. Consequently, 'short *' is not similar to
- 'short **'. Furthermore, two types that are typedefed are
+ determining similarity. Consequently, `short *' is not similar to
+ `short **'. Furthermore, two types that are typedefed are
considered compatible if their underlying types are compatible.
- An 'enum' type is not considered to be compatible with another
- 'enum' type even if both are compatible with the same integer type;
- this is what the C standard specifies. For example, 'enum {foo,
- bar}' is not similar to 'enum {hot, dog}'.
+ An `enum' type is not considered to be compatible with another
+ `enum' type even if both are compatible with the same integer
+ type; this is what the C standard specifies. For example, `enum
+ {foo, bar}' is not similar to `enum {hot, dog}'.
You typically use this function in code whose execution varies
depending on the arguments' types. For example:
@@ -33499,9 +33907,9 @@ and 'isnan' built-in functions appear both with and without the
_Note:_ This construct is only available for C.
+
-- Built-in Function: TYPE __builtin_call_with_static_chain (CALL_EXP,
POINTER_EXP)
-
The CALL_EXP expression must be a function call, and the
POINTER_EXP expression must be a pointer. The POINTER_EXP is
passed to the function call in the target's static chain location.
@@ -33510,20 +33918,21 @@ and 'isnan' built-in functions appear both with and without the
_Note:_ This builtin is only available for C. This builtin can be
used to call Go closures from C.
+
-- Built-in Function: TYPE __builtin_choose_expr (CONST_EXP, EXP1,
EXP2)
-
- You can use the built-in function '__builtin_choose_expr' to
+ You can use the built-in function `__builtin_choose_expr' to
evaluate code depending on the value of a constant expression.
This built-in function returns EXP1 if CONST_EXP, which is an
integer constant expression, is nonzero. Otherwise it returns
EXP2.
- This built-in function is analogous to the '? :' operator in C,
+ This built-in function is analogous to the `? :' operator in C,
except that the expression returned has its type unaltered by
- promotion rules. Also, the built-in function does not evaluate the
- expression that is not chosen. For example, if CONST_EXP evaluates
- to true, EXP2 is not evaluated even if it has side-effects.
+ promotion rules. Also, the built-in function does not evaluate
+ the expression that is not chosen. For example, if CONST_EXP
+ evaluates to true, EXP2 is not evaluated even if it has
+ side-effects.
This built-in function can return an lvalue if the chosen argument
is an lvalue.
@@ -33550,30 +33959,33 @@ and 'isnan' built-in functions appear both with and without the
CONST_EXP) may still generate syntax errors. This may change in
future revisions.
+
-- Built-in Function: TYPE __builtin_complex (REAL, IMAG)
+ The built-in function `__builtin_complex' is provided for use in
+ implementing the ISO C11 macros `CMPLXF', `CMPLX' and `CMPLXL'.
+ REAL and IMAG must have the same type, a real binary
+ floating-point type, and the result has the corresponding complex
+ type with real and imaginary parts REAL and IMAG. Unlike `REAL +
+ I * IMAG', this works even when infinities, NaNs and negative
+ zeros are involved.
- The built-in function '__builtin_complex' is provided for use in
- implementing the ISO C11 macros 'CMPLXF', 'CMPLX' and 'CMPLXL'.
- REAL and IMAG must have the same type, a real binary floating-point
- type, and the result has the corresponding complex type with real
- and imaginary parts REAL and IMAG. Unlike 'REAL + I * IMAG', this
- works even when infinities, NaNs and negative zeros are involved.
-- Built-in Function: int __builtin_constant_p (EXP)
- You can use the built-in function '__builtin_constant_p' to
+ You can use the built-in function `__builtin_constant_p' to
determine if a value is known to be constant at compile time and
hence that GCC can perform constant-folding on expressions
- involving that value. The argument of the function is the value to
- test. The function returns the integer 1 if the argument is known
- to be a compile-time constant and 0 if it is not known to be a
- compile-time constant. A return of 0 does not indicate that the
- value is _not_ a constant, but merely that GCC cannot prove it is a
- constant with the specified value of the '-O' option.
+ involving that value. The argument of the function is the value
+ to test. The function returns the integer 1 if the argument is
+ known to be a compile-time constant and 0 if it is not known to be
+ a compile-time constant. A return of 0 does not indicate that the
+ value is _not_ a constant, but merely that GCC cannot prove it is
+ a constant with the specified value of the `-O' option.
You typically use this function in an embedded application where
memory is a critical resource. If you have some complex
- calculation, you may want it to be folded if it involves constants,
- but need to call a function if it does not. For example:
+ calculation, you may want it to be folded if it involves
+ constants, but need to call a function if it does not. For
+ example:
#define Scale_Value(X) \
(__builtin_constant_p (X) \
@@ -33585,9 +33997,9 @@ and 'isnan' built-in functions appear both with and without the
never returns 1 when you call the inline function with a string
constant or compound literal (*note Compound Literals::) and does
not return 1 when you pass a constant numeric value to the inline
- function unless you specify the '-O' option.
+ function unless you specify the `-O' option.
- You may also use '__builtin_constant_p' in initializers for static
+ You may also use `__builtin_constant_p' in initializers for static
data. For instance, you can write
static const int table[] = {
@@ -33597,20 +34009,20 @@ and 'isnan' built-in functions appear both with and without the
This is an acceptable initializer even if EXPRESSION is not a
constant expression, including the case where
- '__builtin_constant_p' returns 1 because EXPRESSION can be folded
+ `__builtin_constant_p' returns 1 because EXPRESSION can be folded
to a constant but EXPRESSION contains operands that are not
- otherwise permitted in a static initializer (for example, '0 && foo
- ()'). GCC must be more conservative about evaluating the built-in
- in this case, because it has no opportunity to perform
+ otherwise permitted in a static initializer (for example, `0 &&
+ foo ()'). GCC must be more conservative about evaluating the
+ built-in in this case, because it has no opportunity to perform
optimization.
-- Built-in Function: long __builtin_expect (long EXP, long C)
- You may use '__builtin_expect' to provide the compiler with branch
+ You may use `__builtin_expect' to provide the compiler with branch
prediction information. In general, you should prefer to use
- actual profile feedback for this ('-fprofile-arcs'), as programmers
- are notoriously bad at predicting how their programs actually
- perform. However, there are applications in which this data is
- hard to collect.
+ actual profile feedback for this (`-fprofile-arcs'), as
+ programmers are notoriously bad at predicting how their programs
+ actually perform. However, there are applications in which this
+ data is hard to collect.
The return value is the value of EXP, which should be an integral
expression. The semantics of the built-in are that it is expected
@@ -33619,9 +34031,9 @@ and 'isnan' built-in functions appear both with and without the
if (__builtin_expect (x, 0))
foo ();
- indicates that we do not expect to call 'foo', since we expect 'x'
- to be zero. Since you are limited to integral expressions for EXP,
- you should use constructions such as
+ indicates that we do not expect to call `foo', since we expect `x'
+ to be zero. Since you are limited to integral expressions for
+ EXP, you should use constructions such as
if (__builtin_expect (ptr != NULL, 1))
foo (*ptr);
@@ -33632,20 +34044,20 @@ and 'isnan' built-in functions appear both with and without the
This function causes the program to exit abnormally. GCC
implements this function by using a target-dependent mechanism
(such as intentionally executing an illegal instruction) or by
- calling 'abort'. The mechanism used may vary from release to
+ calling `abort'. The mechanism used may vary from release to
release so you should not rely on any particular implementation.
-- Built-in Function: void __builtin_unreachable (void)
- If control flow reaches the point of the '__builtin_unreachable',
+ If control flow reaches the point of the `__builtin_unreachable',
the program is undefined. It is useful in situations where the
compiler cannot deduce the unreachability of the code.
- One such case is immediately following an 'asm' statement that
+ One such case is immediately following an `asm' statement that
either never terminates, or one that transfers control elsewhere
and never returns. In this example, without the
- '__builtin_unreachable', GCC issues a warning that control reaches
+ `__builtin_unreachable', GCC issues a warning that control reaches
the end of a non-void function. It also generates code to return
- after the 'asm'.
+ after the `asm'.
int f (int c, int v)
{
@@ -33660,14 +34072,14 @@ and 'isnan' built-in functions appear both with and without the
}
}
- Because the 'asm' statement unconditionally transfers control out
+ Because the `asm' statement unconditionally transfers control out
of the function, control never reaches the end of the function
- body. The '__builtin_unreachable' is in fact unreachable and
+ body. The `__builtin_unreachable' is in fact unreachable and
communicates this fact to the compiler.
- Another use for '__builtin_unreachable' is following a call a
+ Another use for `__builtin_unreachable' is following a call a
function that never returns but that is not declared
- '__attribute__((noreturn))', as in this example:
+ `__attribute__((noreturn))', as in this example:
void function_that_never_returns (void);
@@ -33684,6 +34096,7 @@ and 'isnan' built-in functions appear both with and without the
}
}
+
-- Built-in Function: void *__builtin_assume_aligned (const void *EXP,
size_t ALIGN, ...)
This function returns its first argument, and allows the compiler
@@ -33694,27 +34107,27 @@ and 'isnan' built-in functions appear both with and without the
void *x = __builtin_assume_aligned (arg, 16);
- means that the compiler can assume 'x', set to 'arg', is at least
+ means that the compiler can assume `x', set to `arg', is at least
16-byte aligned, while:
void *x = __builtin_assume_aligned (arg, 32, 8);
- means that the compiler can assume for 'x', set to 'arg', that
- '(char *) x - 8' is 32-byte aligned.
+ means that the compiler can assume for `x', set to `arg', that
+ `(char *) x - 8' is 32-byte aligned.
-- Built-in Function: int __builtin_LINE ()
- This function is the equivalent to the preprocessor '__LINE__'
+ This function is the equivalent to the preprocessor `__LINE__'
macro and returns the line number of the invocation of the
built-in. In a C++ default argument for a function F, it gets the
line number of the call to F.
-- Built-in Function: const char * __builtin_FUNCTION ()
- This function is the equivalent to the preprocessor '__FUNCTION__'
+ This function is the equivalent to the preprocessor `__FUNCTION__'
macro and returns the function name the invocation of the built-in
is in.
-- Built-in Function: const char * __builtin_FILE ()
- This function is the equivalent to the preprocessor '__FILE__'
+ This function is the equivalent to the preprocessor `__FILE__'
macro and returns the file name the invocation of the built-in is
in. In a C++ default argument for a function F, it gets the file
name of the call to F.
@@ -33722,21 +34135,21 @@ and 'isnan' built-in functions appear both with and without the
-- Built-in Function: void __builtin___clear_cache (char *BEGIN, char
*END)
This function is used to flush the processor's instruction cache
- for the region of memory between BEGIN inclusive and END exclusive.
- Some targets require that the instruction cache be flushed, after
- modifying memory containing code, in order to obtain deterministic
- behavior.
+ for the region of memory between BEGIN inclusive and END
+ exclusive. Some targets require that the instruction cache be
+ flushed, after modifying memory containing code, in order to obtain
+ deterministic behavior.
If the target does not require instruction cache flushes,
- '__builtin___clear_cache' has no effect. Otherwise either
+ `__builtin___clear_cache' has no effect. Otherwise either
instructions are emitted in-line to clear the instruction cache or
- a call to the '__clear_cache' function in libgcc is made.
+ a call to the `__clear_cache' function in libgcc is made.
-- Built-in Function: void __builtin_prefetch (const void *ADDR, ...)
- This function is used to minimize cache-miss latency by moving data
- into a cache before it is accessed. You can insert calls to
- '__builtin_prefetch' into code for which you know addresses of data
- in memory that is likely to be accessed soon. If the target
+ This function is used to minimize cache-miss latency by moving
+ data into a cache before it is accessed. You can insert calls to
+ `__builtin_prefetch' into code for which you know addresses of
+ data in memory that is likely to be accessed soon. If the target
supports them, data prefetch instructions are generated. If the
prefetch is done early enough before the access then the data will
be in the cache by the time it is accessed.
@@ -33764,8 +34177,8 @@ and 'isnan' built-in functions appear both with and without the
Data prefetch does not generate faults if ADDR is invalid, but the
address expression itself must be valid. For example, a prefetch
- of 'p->next' does not fault if 'p->next' is not a valid address,
- but evaluation faults if 'p' is not a valid address.
+ of `p->next' does not fault if `p->next' is not a valid address,
+ but evaluation faults if `p' is not a valid address.
If the target does not support data prefetch, the address
expression is evaluated if it includes side effects but no other
@@ -33773,14 +34186,14 @@ and 'isnan' built-in functions appear both with and without the
-- Built-in Function: double __builtin_huge_val (void)
Returns a positive infinity, if supported by the floating-point
- format, else 'DBL_MAX'. This function is suitable for implementing
- the ISO C macro 'HUGE_VAL'.
+ format, else `DBL_MAX'. This function is suitable for
+ implementing the ISO C macro `HUGE_VAL'.
-- Built-in Function: float __builtin_huge_valf (void)
- Similar to '__builtin_huge_val', except the return type is 'float'.
+ Similar to `__builtin_huge_val', except the return type is `float'.
-- Built-in Function: long double __builtin_huge_vall (void)
- Similar to '__builtin_huge_val', except the return type is 'long
+ Similar to `__builtin_huge_val', except the return type is `long
double'.
-- Built-in Function: int __builtin_fpclassify (int, int, int, int,
@@ -33788,85 +34201,85 @@ and 'isnan' built-in functions appear both with and without the
This built-in implements the C99 fpclassify functionality. The
first five int arguments should be the target library's notion of
the possible FP classes and are used for return values. They must
- be constant values and they must appear in this order: 'FP_NAN',
- 'FP_INFINITE', 'FP_NORMAL', 'FP_SUBNORMAL' and 'FP_ZERO'. The
+ be constant values and they must appear in this order: `FP_NAN',
+ `FP_INFINITE', `FP_NORMAL', `FP_SUBNORMAL' and `FP_ZERO'. The
ellipsis is for exactly one floating-point value to classify. GCC
treats the last argument as type-generic, which means it does not
do default promotion from float to double.
-- Built-in Function: double __builtin_inf (void)
- Similar to '__builtin_huge_val', except a warning is generated if
+ Similar to `__builtin_huge_val', except a warning is generated if
the target floating-point format does not support infinities.
-- Built-in Function: _Decimal32 __builtin_infd32 (void)
- Similar to '__builtin_inf', except the return type is '_Decimal32'.
+ Similar to `__builtin_inf', except the return type is `_Decimal32'.
-- Built-in Function: _Decimal64 __builtin_infd64 (void)
- Similar to '__builtin_inf', except the return type is '_Decimal64'.
+ Similar to `__builtin_inf', except the return type is `_Decimal64'.
-- Built-in Function: _Decimal128 __builtin_infd128 (void)
- Similar to '__builtin_inf', except the return type is
- '_Decimal128'.
+ Similar to `__builtin_inf', except the return type is
+ `_Decimal128'.
-- Built-in Function: float __builtin_inff (void)
- Similar to '__builtin_inf', except the return type is 'float'.
+ Similar to `__builtin_inf', except the return type is `float'.
This function is suitable for implementing the ISO C99 macro
- 'INFINITY'.
+ `INFINITY'.
-- Built-in Function: long double __builtin_infl (void)
- Similar to '__builtin_inf', except the return type is 'long
+ Similar to `__builtin_inf', except the return type is `long
double'.
-- Built-in Function: int __builtin_isinf_sign (...)
- Similar to 'isinf', except the return value is -1 for an argument
- of '-Inf' and 1 for an argument of '+Inf'. Note while the
+ Similar to `isinf', except the return value is -1 for an argument
+ of `-Inf' and 1 for an argument of `+Inf'. Note while the
parameter list is an ellipsis, this function only accepts exactly
one floating-point argument. GCC treats this parameter as
type-generic, which means it does not do default promotion from
float to double.
-- Built-in Function: double __builtin_nan (const char *str)
- This is an implementation of the ISO C99 function 'nan'.
+ This is an implementation of the ISO C99 function `nan'.
- Since ISO C99 defines this function in terms of 'strtod', which we
+ Since ISO C99 defines this function in terms of `strtod', which we
do not implement, a description of the parsing is in order. The
- string is parsed as by 'strtol'; that is, the base is recognized by
- leading '0' or '0x' prefixes. The number parsed is placed in the
- significand such that the least significant bit of the number is at
- the least significant bit of the significand. The number is
+ string is parsed as by `strtol'; that is, the base is recognized by
+ leading `0' or `0x' prefixes. The number parsed is placed in the
+ significand such that the least significant bit of the number is
+ at the least significant bit of the significand. The number is
truncated to fit the significand field provided. The significand
is forced to be a quiet NaN.
This function, if given a string literal all of which would have
- been consumed by 'strtol', is evaluated early enough that it is
+ been consumed by `strtol', is evaluated early enough that it is
considered a compile-time constant.
-- Built-in Function: _Decimal32 __builtin_nand32 (const char *str)
- Similar to '__builtin_nan', except the return type is '_Decimal32'.
+ Similar to `__builtin_nan', except the return type is `_Decimal32'.
-- Built-in Function: _Decimal64 __builtin_nand64 (const char *str)
- Similar to '__builtin_nan', except the return type is '_Decimal64'.
+ Similar to `__builtin_nan', except the return type is `_Decimal64'.
-- Built-in Function: _Decimal128 __builtin_nand128 (const char *str)
- Similar to '__builtin_nan', except the return type is
- '_Decimal128'.
+ Similar to `__builtin_nan', except the return type is
+ `_Decimal128'.
-- Built-in Function: float __builtin_nanf (const char *str)
- Similar to '__builtin_nan', except the return type is 'float'.
+ Similar to `__builtin_nan', except the return type is `float'.
-- Built-in Function: long double __builtin_nanl (const char *str)
- Similar to '__builtin_nan', except the return type is 'long
+ Similar to `__builtin_nan', except the return type is `long
double'.
-- Built-in Function: double __builtin_nans (const char *str)
- Similar to '__builtin_nan', except the significand is forced to be
- a signaling NaN. The 'nans' function is proposed by WG14 N965.
+ Similar to `__builtin_nan', except the significand is forced to be
+ a signaling NaN. The `nans' function is proposed by WG14 N965.
-- Built-in Function: float __builtin_nansf (const char *str)
- Similar to '__builtin_nans', except the return type is 'float'.
+ Similar to `__builtin_nans', except the return type is `float'.
-- Built-in Function: long double __builtin_nansl (const char *str)
- Similar to '__builtin_nans', except the return type is 'long
+ Similar to `__builtin_nans', except the return type is `long
double'.
-- Built-in Function: int __builtin_ffs (int x)
@@ -33893,74 +34306,74 @@ and 'isnan' built-in functions appear both with and without the
Returns the parity of X, i.e. the number of 1-bits in X modulo 2.
-- Built-in Function: int __builtin_ffsl (long)
- Similar to '__builtin_ffs', except the argument type is 'long'.
+ Similar to `__builtin_ffs', except the argument type is `long'.
-- Built-in Function: int __builtin_clzl (unsigned long)
- Similar to '__builtin_clz', except the argument type is 'unsigned
+ Similar to `__builtin_clz', except the argument type is `unsigned
long'.
-- Built-in Function: int __builtin_ctzl (unsigned long)
- Similar to '__builtin_ctz', except the argument type is 'unsigned
+ Similar to `__builtin_ctz', except the argument type is `unsigned
long'.
-- Built-in Function: int __builtin_clrsbl (long)
- Similar to '__builtin_clrsb', except the argument type is 'long'.
+ Similar to `__builtin_clrsb', except the argument type is `long'.
-- Built-in Function: int __builtin_popcountl (unsigned long)
- Similar to '__builtin_popcount', except the argument type is
- 'unsigned long'.
+ Similar to `__builtin_popcount', except the argument type is
+ `unsigned long'.
-- Built-in Function: int __builtin_parityl (unsigned long)
- Similar to '__builtin_parity', except the argument type is
- 'unsigned long'.
+ Similar to `__builtin_parity', except the argument type is
+ `unsigned long'.
-- Built-in Function: int __builtin_ffsll (long long)
- Similar to '__builtin_ffs', except the argument type is 'long
+ Similar to `__builtin_ffs', except the argument type is `long
long'.
-- Built-in Function: int __builtin_clzll (unsigned long long)
- Similar to '__builtin_clz', except the argument type is 'unsigned
+ Similar to `__builtin_clz', except the argument type is `unsigned
long long'.
-- Built-in Function: int __builtin_ctzll (unsigned long long)
- Similar to '__builtin_ctz', except the argument type is 'unsigned
+ Similar to `__builtin_ctz', except the argument type is `unsigned
long long'.
-- Built-in Function: int __builtin_clrsbll (long long)
- Similar to '__builtin_clrsb', except the argument type is 'long
+ Similar to `__builtin_clrsb', except the argument type is `long
long'.
-- Built-in Function: int __builtin_popcountll (unsigned long long)
- Similar to '__builtin_popcount', except the argument type is
- 'unsigned long long'.
+ Similar to `__builtin_popcount', except the argument type is
+ `unsigned long long'.
-- Built-in Function: int __builtin_parityll (unsigned long long)
- Similar to '__builtin_parity', except the argument type is
- 'unsigned long long'.
+ Similar to `__builtin_parity', except the argument type is
+ `unsigned long long'.
-- Built-in Function: double __builtin_powi (double, int)
Returns the first argument raised to the power of the second.
- Unlike the 'pow' function no guarantees about precision and
+ Unlike the `pow' function no guarantees about precision and
rounding are made.
-- Built-in Function: float __builtin_powif (float, int)
- Similar to '__builtin_powi', except the argument and return types
- are 'float'.
+ Similar to `__builtin_powi', except the argument and return types
+ are `float'.
-- Built-in Function: long double __builtin_powil (long double, int)
- Similar to '__builtin_powi', except the argument and return types
- are 'long double'.
+ Similar to `__builtin_powi', except the argument and return types
+ are `long double'.
-- Built-in Function: uint16_t __builtin_bswap16 (uint16_t x)
Returns X with the order of the bytes reversed; for example,
- '0xaabb' becomes '0xbbaa'. Byte here always means exactly 8 bits.
+ `0xaabb' becomes `0xbbaa'. Byte here always means exactly 8 bits.
-- Built-in Function: uint32_t __builtin_bswap32 (uint32_t x)
- Similar to '__builtin_bswap16', except the argument and return
+ Similar to `__builtin_bswap16', except the argument and return
types are 32 bit.
-- Built-in Function: uint64_t __builtin_bswap64 (uint64_t x)
- Similar to '__builtin_bswap32', except the argument and return
+ Similar to `__builtin_bswap32', except the argument and return
types are 64 bit.

@@ -34061,9 +34474,9 @@ generate the machine instruction that is part of the name.
long __builtin_alpha_zap (long, long)
long __builtin_alpha_zapnot (long, long)
- The following built-in functions are always with '-mmax' or '-mcpu=CPU'
-where CPU is 'pca56' or later. They all generate the machine
-instruction that is part of the name.
+ The following built-in functions are always with `-mmax' or
+`-mcpu=CPU' where CPU is `pca56' or later. They all generate the
+machine instruction that is part of the name.
long __builtin_alpha_pklb (long)
long __builtin_alpha_pkwb (long)
@@ -34079,18 +34492,18 @@ instruction that is part of the name.
long __builtin_alpha_maxsw4 (long, long)
long __builtin_alpha_perr (long, long)
- The following built-in functions are always with '-mcix' or '-mcpu=CPU'
-where CPU is 'ev67' or later. They all generate the machine instruction
-that is part of the name.
+ The following built-in functions are always with `-mcix' or
+`-mcpu=CPU' where CPU is `ev67' or later. They all generate the
+machine instruction that is part of the name.
long __builtin_alpha_cttz (long)
long __builtin_alpha_ctlz (long)
long __builtin_alpha_ctpop (long)
The following built-in functions are available on systems that use the
-OSF/1 PALcode. Normally they invoke the 'rduniq' and 'wruniq' PAL
-calls, but when invoked with '-mtls-kernel', they invoke 'rdval' and
-'wrval'.
+OSF/1 PALcode. Normally they invoke the `rduniq' and `wruniq' PAL
+calls, but when invoked with `-mtls-kernel', they invoke `rdval' and
+`wrval'.
void *__builtin_thread_pointer (void)
void __builtin_set_thread_pointer (void *)
@@ -34120,25 +34533,26 @@ generate the machine instruction that is part of the name.
void __builtin_wrctl (int, int)
The following built-in functions are always available. They all
-generate a Nios II Custom Instruction. The name of the function
-represents the types that the function takes and returns. The letter
-before the 'n' is the return type or void if absent. The 'n' represents
+generate a Nios II Custom Instruction. The name of the function
+represents the types that the function takes and returns. The letter
+before the `n' is the return type or void if absent. The `n' represents
the first parameter to all the custom instructions, the custom
-instruction number. The two letters after the 'n' represent the up to
+instruction number. The two letters after the `n' represent the up to
two parameters to the function.
The letters represent the following data types:
-'<no letter>'
- 'void' for return type and no parameter for parameter types.
+`<no letter>'
+ `void' for return type and no parameter for parameter types.
-'i'
- 'int' for return type and parameter type
+`i'
+ `int' for return type and parameter type
-'f'
- 'float' for return type and parameter type
+`f'
+ `float' for return type and parameter type
+
+`p'
+ `void *' for return type and parameter type
-'p'
- 'void *' for return type and parameter type
And the function names are:
void __builtin_custom_n (void)
@@ -34208,7 +34622,7 @@ generated to ensure this is true, but for brevity this is not described
in each case.
_Note:_ Using a built-in to generate an instruction not supported by a
-target may cause problems. At present the compiler is not guaranteed to
+target may cause problems. At present the compiler is not guaranteed to
detect such misuse, and as a result an internal compiler error may be
generated.
@@ -34241,7 +34655,7 @@ generated.
mov rREGNO, VAL
-- Built-in Function: int __builtin_arc_divaw (int A, int B)
- Only available if either '-mcpu=ARC700' or '-meA' is set.
+ Only available if either `-mcpu=ARC700' or `-meA' is set.
Generates:
divaw DEST, A, B
where the value in DEST will be the result returned from the
@@ -34252,19 +34666,19 @@ generated.
flag A
-- Built-in Function: unsigned int __builtin_arc_lr (unsigned int AUXR)
- The operand, AUXV, is the address of an auxiliary register and must
- be a compile time constant. Generates:
+ The operand, AUXV, is the address of an auxiliary register and
+ must be a compile time constant. Generates:
lr DEST, [AUXR]
Where the value in DEST will be the result returned from the
built-in.
-- Built-in Function: void __builtin_arc_mul64 (int A, int B)
- Only available with '-mmul64'. Generates:
+ Only available with `-mmul64'. Generates:
mul64 A, B
-- Built-in Function: void __builtin_arc_mulu64 (unsigned int A,
unsigned int B)
- Only available with '-mmul64'. Generates:
+ Only available with `-mmul64'. Generates:
mulu64 A, B
-- Built-in Function: void __builtin_arc_nop (void)
@@ -34272,15 +34686,15 @@ generated.
nop
-- Built-in Function: int __builtin_arc_norm (int SRC)
- Only valid if the 'norm' instruction is available through the
- '-mnorm' option or by default with '-mcpu=ARC700'. Generates:
+ Only valid if the `norm' instruction is available through the
+ `-mnorm' option or by default with `-mcpu=ARC700'. Generates:
norm DEST, SRC
Where the value in DEST will be the result returned from the
built-in.
-- Built-in Function: short int __builtin_arc_normw (short int SRC)
- Only valid if the 'normw' instruction is available through the
- '-mnorm' option or by default with '-mcpu=ARC700'. Generates:
+ Only valid if the `normw' instruction is available through the
+ `-mnorm' option or by default with `-mcpu=ARC700'. Generates:
normw DEST, SRC
Where the value in DEST will be the result returned from the
built-in.
@@ -34301,7 +34715,7 @@ generated.
sr AUXR, [VAL]
-- Built-in Function: int __builtin_arc_swap (int SRC)
- Only valid with '-mswap'. Generates:
+ Only valid with `-mswap'. Generates:
swap DEST, SRC
Where the value in DEST will be the result returned from the
built-in.
@@ -34311,21 +34725,21 @@ generated.
swi
-- Built-in Function: void __builtin_arc_sync (void)
- Only available with '-mcpu=ARC700'. Generates:
+ Only available with `-mcpu=ARC700'. Generates:
sync
-- Built-in Function: void __builtin_arc_trap_s (unsigned int C)
- Only available with '-mcpu=ARC700'. Generates:
+ Only available with `-mcpu=ARC700'. Generates:
trap_s C
-- Built-in Function: void __builtin_arc_unimp_s (void)
- Only available with '-mcpu=ARC700'. Generates:
+ Only available with `-mcpu=ARC700'. Generates:
unimp_s
- The instructions generated by the following builtins are not considered
-as candidates for scheduling. They are not moved around by the compiler
-during scheduling, and thus can be expected to appear where they are put
-in the C code:
+ The instructions generated by the following builtins are not
+considered as candidates for scheduling. They are not moved around by
+the compiler during scheduling, and thus can be expected to appear
+where they are put in the C code:
__builtin_arc_brk()
__builtin_arc_core_read()
__builtin_arc_core_write()
@@ -34343,28 +34757,28 @@ File: gcc.info, Node: ARC SIMD Built-in Functions, Next: ARM iWMMXt Built-in F
SIMD builtins provided by the compiler can be used to generate the
vector instructions. This section describes the available builtins and
-their usage in programs. With the '-msimd' option, the compiler
+their usage in programs. With the `-msimd' option, the compiler
provides 128-bit vector types, which can be specified using the
-'vector_size' attribute. The header file 'arc-simd.h' can be included
+`vector_size' attribute. The header file `arc-simd.h' can be included
to use the following predefined types:
typedef int __v4si __attribute__((vector_size(16)));
typedef short __v8hi __attribute__((vector_size(16)));
These types can be used to define 128-bit variables. The built-in
-functions listed in the following section can be used on these variables
-to generate the vector operations.
+functions listed in the following section can be used on these
+variables to generate the vector operations.
- For all builtins, '__builtin_arc_SOMEINSN', the header file
-'arc-simd.h' also provides equivalent macros called '_SOMEINSN' that can
-be used for programming ease and improved readability. The following
-macros for DMA control are also provided:
+ For all builtins, `__builtin_arc_SOMEINSN', the header file
+`arc-simd.h' also provides equivalent macros called `_SOMEINSN' that
+can be used for programming ease and improved readability. The
+following macros for DMA control are also provided:
#define _setup_dma_in_channel_reg _vdiwr
#define _setup_dma_out_channel_reg _vdowr
- The following is a complete list of all the SIMD built-ins provided for
-ARC, grouped by calling signature.
+ The following is a complete list of all the SIMD built-ins provided
+for ARC, grouped by calling signature.
- The following take two '__v8hi' arguments and return a '__v8hi' result:
+ The following take two `__v8hi' arguments and return a `__v8hi' result:
__v8hi __builtin_arc_vaddaw (__v8hi, __v8hi)
__v8hi __builtin_arc_vaddw (__v8hi, __v8hi)
__v8hi __builtin_arc_vand (__v8hi, __v8hi)
@@ -34414,8 +34828,8 @@ ARC, grouped by calling signature.
__v8hi __builtin_arc_vxor (__v8hi, __v8hi)
__v8hi __builtin_arc_vxoraw (__v8hi, __v8hi)
- The following take one '__v8hi' and one 'int' argument and return a
-'__v8hi' result:
+ The following take one `__v8hi' and one `int' argument and return a
+`__v8hi' result:
__v8hi __builtin_arc_vbaddw (__v8hi, int)
__v8hi __builtin_arc_vbmaxw (__v8hi, int)
@@ -34426,15 +34840,15 @@ ARC, grouped by calling signature.
__v8hi __builtin_arc_vbrsubw (__v8hi, int)
__v8hi __builtin_arc_vbsubw (__v8hi, int)
- The following take one '__v8hi' argument and one 'int' argument which
+ The following take one `__v8hi' argument and one `int' argument which
must be a 3-bit compile time constant indicating a register number
-I0-I7. They return a '__v8hi' result.
+I0-I7. They return a `__v8hi' result.
__v8hi __builtin_arc_vasrw (__v8hi, const int)
__v8hi __builtin_arc_vsr8 (__v8hi, const int)
__v8hi __builtin_arc_vsr8aw (__v8hi, const int)
- The following take one '__v8hi' argument and one 'int' argument which
-must be a 6-bit compile time constant. They return a '__v8hi' result.
+ The following take one `__v8hi' argument and one `int' argument which
+must be a 6-bit compile time constant. They return a `__v8hi' result.
__v8hi __builtin_arc_vasrpwbi (__v8hi, const int)
__v8hi __builtin_arc_vasrrpwbi (__v8hi, const int)
__v8hi __builtin_arc_vasrrwi (__v8hi, const int)
@@ -34443,20 +34857,20 @@ must be a 6-bit compile time constant. They return a '__v8hi' result.
__v8hi __builtin_arc_vsr8awi (__v8hi, const int)
__v8hi __builtin_arc_vsr8i (__v8hi, const int)
- The following take one '__v8hi' argument and one 'int' argument which
-must be a 8-bit compile time constant. They return a '__v8hi' result.
+ The following take one `__v8hi' argument and one `int' argument which
+must be a 8-bit compile time constant. They return a `__v8hi' result.
__v8hi __builtin_arc_vd6tapf (__v8hi, const int)
__v8hi __builtin_arc_vmvaw (__v8hi, const int)
__v8hi __builtin_arc_vmvw (__v8hi, const int)
__v8hi __builtin_arc_vmvzw (__v8hi, const int)
- The following take two 'int' arguments, the second of which which must
-be a 8-bit compile time constant. They return a '__v8hi' result:
+ The following take two `int' arguments, the second of which which must
+be a 8-bit compile time constant. They return a `__v8hi' result:
__v8hi __builtin_arc_vmovaw (int, const int)
__v8hi __builtin_arc_vmovw (int, const int)
__v8hi __builtin_arc_vmovzw (int, const int)
- The following take a single '__v8hi' argument and return a '__v8hi'
+ The following take a single `__v8hi' argument and return a `__v8hi'
result:
__v8hi __builtin_arc_vabsaw (__v8hi)
__v8hi __builtin_arc_vabsw (__v8hi)
@@ -34470,38 +34884,38 @@ result:
__v8hi __builtin_arc_vupsbaw (__v8hi)
__v8hi __builtin_arc_vupsbw (__v8hi)
- The following take two 'int' arguments and return no result:
+ The following take two `int' arguments and return no result:
void __builtin_arc_vdirun (int, int)
void __builtin_arc_vdorun (int, int)
- The following take two 'int' arguments and return no result. The first
-argument must a 3-bit compile time constant indicating one of the
+ The following take two `int' arguments and return no result. The
+first argument must a 3-bit compile time constant indicating one of the
DR0-DR7 DMA setup channels:
void __builtin_arc_vdiwr (const int, int)
void __builtin_arc_vdowr (const int, int)
- The following take an 'int' argument and return no result:
+ The following take an `int' argument and return no result:
void __builtin_arc_vendrec (int)
void __builtin_arc_vrec (int)
void __builtin_arc_vrecrun (int)
void __builtin_arc_vrun (int)
- The following take a '__v8hi' argument and two 'int' arguments and
-return a '__v8hi' result. The second argument must be a 3-bit compile
+ The following take a `__v8hi' argument and two `int' arguments and
+return a `__v8hi' result. The second argument must be a 3-bit compile
time constants, indicating one the registers I0-I7, and the third
argument must be an 8-bit compile time constant.
_Note:_ Although the equivalent hardware instructions do not take an
SIMD register as an operand, these builtins overwrite the relevant bits
-of the '__v8hi' register provided as the first argument with the value
-loaded from the '[Ib, u8]' location in the SDM.
+of the `__v8hi' register provided as the first argument with the value
+loaded from the `[Ib, u8]' location in the SDM.
__v8hi __builtin_arc_vld32 (__v8hi, const int, const int)
__v8hi __builtin_arc_vld32wh (__v8hi, const int, const int)
__v8hi __builtin_arc_vld32wl (__v8hi, const int, const int)
__v8hi __builtin_arc_vld64 (__v8hi, const int, const int)
- The following take two 'int' arguments and return a '__v8hi' result.
+ The following take two `int' arguments and return a `__v8hi' result.
The first argument must be a 3-bit compile time constants, indicating
one the registers I0-I7, and the second argument must be an 8-bit
compile time constant.
@@ -34509,7 +34923,7 @@ compile time constant.
__v8hi __builtin_arc_vld128 (const int, const int)
__v8hi __builtin_arc_vld64w (const int, const int)
- The following take a '__v8hi' argument and two 'int' arguments and
+ The following take a `__v8hi' argument and two `int' arguments and
return no result. The second argument must be a 3-bit compile time
constants, indicating one the registers I0-I7, and the third argument
must be an 8-bit compile time constant.
@@ -34517,7 +34931,7 @@ must be an 8-bit compile time constant.
void __builtin_arc_vst128 (__v8hi, const int, const int)
void __builtin_arc_vst64 (__v8hi, const int, const int)
- The following take a '__v8hi' argument and three 'int' arguments and
+ The following take a `__v8hi' argument and three `int' arguments and
return no result. The second argument must be a 3-bit compile-time
constant, identifying the 16-bit sub-register to be stored, the third
argument must be a 3-bit compile time constants, indicating one the
@@ -34534,7 +34948,7 @@ File: gcc.info, Node: ARM iWMMXt Built-in Functions, Next: ARM C Language Exte
------------------------------------
These built-in functions are available for the ARM family of processors
-when the '-mcpu=iwmmxt' switch is used:
+when the `-mcpu=iwmmxt' switch is used:
typedef int v2si __attribute__ ((vector_size (8)));
typedef short v4hi __attribute__ ((vector_size (8)));
@@ -34689,20 +35103,20 @@ File: gcc.info, Node: ARM C Language Extensions (ACLE), Next: ARM Floating Poi
GCC implements extensions for C as described in the ARM C Language
Extensions (ACLE) specification, which can be found at
-<http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf>.
+`http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf'.
As a part of ACLE, GCC implements extensions for Advanced SIMD as
described in the ARM C Language Extensions Specification. The complete
list of Advanced SIMD intrinsics can be found at
-<http://infocenter.arm.com/help/topic/com.arm.doc.ihi0073a/IHI0073A_arm_neon_intrinsics_ref.pdf>.
+`http://infocenter.arm.com/help/topic/com.arm.doc.ihi0073a/IHI0073A_arm_neon_intrinsics_ref.pdf'.
The built-in intrinsics for the Advanced SIMD extension are available
when NEON is enabled.
Currently, ARM and AArch64 back ends do not support ACLE 2.0 fully.
-Both back ends support CRC32 intrinsics from 'arm_acle.h'. The ARM back
-end's 16-bit floating-point Advanced SIMD intrinsics currently comply to
-ACLE v1.1. AArch64's back end does not have support for 16-bit floating
-point Advanced SIMD intrinsics yet.
+Both back ends support CRC32 intrinsics from `arm_acle.h'. The ARM
+back end's 16-bit floating-point Advanced SIMD intrinsics currently
+comply to ACLE v1.1. AArch64's back end does not have support for
+16-bit floating point Advanced SIMD intrinsics yet.
See *note ARM Options:: and *note AArch64 Options:: for more
information on the availability of extensions.
@@ -34725,15 +35139,15 @@ File: gcc.info, Node: AVR Built-in Functions, Next: Blackfin Built-in Function
6.58.9 AVR Built-in Functions
-----------------------------
-For each built-in function for AVR, there is an equally named, uppercase
-built-in macro defined. That way users can easily query if or if not a
-specific built-in is implemented or not. For example, if
-'__builtin_avr_nop' is available the macro '__BUILTIN_AVR_NOP' is
-defined to '1' and undefined otherwise.
+For each built-in function for AVR, there is an equally named,
+uppercase built-in macro defined. That way users can easily query if or
+if not a specific built-in is implemented or not. For example, if
+`__builtin_avr_nop' is available the macro `__BUILTIN_AVR_NOP' is
+defined to `1' and undefined otherwise.
The following built-in functions map to the respective machine
-instruction, i.e. 'nop', 'sei', 'cli', 'sleep', 'wdr', 'swap', 'fmul',
-'fmuls' resp. 'fmulsu'. The three 'fmul*' built-ins are implemented as
+instruction, i.e. `nop', `sei', `cli', `sleep', `wdr', `swap', `fmul',
+`fmuls' resp. `fmulsu'. The three `fmul*' built-ins are implemented as
library call if no hardware multiplier is available.
void __builtin_avr_nop (void)
@@ -34750,33 +35164,34 @@ library call if no hardware multiplier is available.
implements
void __builtin_avr_delay_cycles (unsigned long ticks)
-'ticks' is the number of ticks to delay execution. Note that this
+`ticks' is the number of ticks to delay execution. Note that this
built-in does not take into account the effect of interrupts that might
-increase delay time. 'ticks' must be a compile-time integer constant;
+increase delay time. `ticks' must be a compile-time integer constant;
delays with a variable number of cycles are not supported.
char __builtin_avr_flash_segment (const __memx void*)
This built-in takes a byte address to the 24-bit *note address space:
-AVR Named Address Spaces. '__memx' and returns the number of the flash
-segment (the 64 KiB chunk) where the address points to. Counting starts
-at '0'. If the address does not point to flash memory, return '-1'.
+AVR Named Address Spaces. `__memx' and returns the number of the flash
+segment (the 64 KiB chunk) where the address points to. Counting
+starts at `0'. If the address does not point to flash memory, return
+`-1'.
unsigned char __builtin_avr_insert_bits (unsigned long map, unsigned char bits, unsigned char val)
-Insert bits from BITS into VAL and return the resulting value. The
+Insert bits from BITS into VAL and return the resulting value. The
nibbles of MAP determine how the insertion is performed: Let X be the
N-th nibble of MAP
- 1. If X is '0xf', then the N-th bit of VAL is returned unaltered.
+ 1. If X is `0xf', then the N-th bit of VAL is returned unaltered.
2. If X is in the range 0...7, then the N-th result bit is set to the
X-th bit of BITS
- 3. If X is in the range 8...'0xe', then the N-th result bit is
+ 3. If X is in the range 8...`0xe', then the N-th result bit is
undefined.
One typical use case for this built-in is adjusting input and output
-values to non-contiguous port layouts. Some examples:
+values to non-contiguous port layouts. Some examples:
// same as val, bits is unused
__builtin_avr_insert_bits (0xffffffff, bits, val)
@@ -34801,7 +35216,7 @@ File: gcc.info, Node: Blackfin Built-in Functions, Next: FR-V Built-in Functio
-----------------------------------
Currently, there are two Blackfin-specific built-in functions. These
-are used for generating 'CSYNC' and 'SSYNC' machine insns without using
+are used for generating `CSYNC' and `SSYNC' machine insns without using
inline assembly; by using these built-in functions the compiler can
automatically add workarounds for hardware errata involving these
instructions. These functions are named as follows:
@@ -34816,14 +35231,14 @@ File: gcc.info, Node: FR-V Built-in Functions, Next: MIPS DSP Built-in Functio
-------------------------------
GCC provides many FR-V-specific built-in functions. In general, these
-functions are intended to be compatible with those described by 'FR-V
-Family, Softune C/C++ Compiler Manual (V6), Fujitsu Semiconductor'. The
-two exceptions are '__MDUNPACKH' and '__MBTOHE', the GCC forms of which
-pass 128-bit values by pointer rather than by value.
+functions are intended to be compatible with those described by `FR-V
+Family, Softune C/C++ Compiler Manual (V6), Fujitsu Semiconductor'.
+The two exceptions are `__MDUNPACKH' and `__MBTOHE', the GCC forms of
+which pass 128-bit values by pointer rather than by value.
- Most of the functions are named after specific FR-V instructions. Such
-functions are said to be "directly mapped" and are summarized here in
-tabular form.
+ Most of the functions are named after specific FR-V instructions.
+Such functions are said to be "directly mapped" and are summarized here
+in tabular form.
* Menu:
@@ -34845,30 +35260,30 @@ In order to make this classification clear at a glance, the arguments
and return values are given the following pseudo types:
Pseudo type Real C type Constant? Description
-'uh' 'unsigned short' No an unsigned halfword
-'uw1' 'unsigned int' No an unsigned word
-'sw1' 'int' No a signed word
-'uw2' 'unsigned long long' No an unsigned doubleword
-'sw2' 'long long' No a signed doubleword
-'const' 'int' Yes an integer constant
-'acc' 'int' Yes an ACC register number
-'iacc' 'int' Yes an IACC register number
+`uh' `unsigned short' No an unsigned halfword
+`uw1' `unsigned int' No an unsigned word
+`sw1' `int' No a signed word
+`uw2' `unsigned long long' No an unsigned doubleword
+`sw2' `long long' No a signed doubleword
+`const' `int' Yes an integer constant
+`acc' `int' Yes an ACC register number
+`iacc' `int' Yes an IACC register number
These pseudo types are not defined by GCC, they are simply a notational
convenience used in this manual.
- Arguments of type 'uh', 'uw1', 'sw1', 'uw2' and 'sw2' are evaluated at
+ Arguments of type `uh', `uw1', `sw1', `uw2' and `sw2' are evaluated at
run time. They correspond to register operands in the underlying FR-V
instructions.
- 'const' arguments represent immediate operands in the underlying FR-V
+ `const' arguments represent immediate operands in the underlying FR-V
instructions. They must be compile-time constants.
- 'acc' arguments are evaluated at compile time and specify the number of
-an accumulator register. For example, an 'acc' argument of 2 selects
-the ACC2 register.
+ `acc' arguments are evaluated at compile time and specify the number
+of an accumulator register. For example, an `acc' argument of 2
+selects the ACC2 register.
- 'iacc' arguments are similar to 'acc' arguments but specify the number
+ `iacc' arguments are similar to `acc' arguments but specify the number
of an IACC register. See *note Other Built-in Functions:: for more
details.
@@ -34881,16 +35296,16 @@ File: gcc.info, Node: Directly-mapped Integer Functions, Next: Directly-mapped
The functions listed below map directly to FR-V I-type instructions.
Function prototype Example usage Assembly output
-'sw1 __ADDSS (sw1, sw1)' 'C = __ADDSS (A, B)' 'ADDSS A,B,C'
-'sw1 __SCAN (sw1, sw1)' 'C = __SCAN (A, B)' 'SCAN A,B,C'
-'sw1 __SCUTSS (sw1)' 'B = __SCUTSS (A)' 'SCUTSS A,B'
-'sw1 __SLASS (sw1, sw1)' 'C = __SLASS (A, B)' 'SLASS A,B,C'
-'void __SMASS (sw1, sw1)' '__SMASS (A, B)' 'SMASS A,B'
-'void __SMSSS (sw1, sw1)' '__SMSSS (A, B)' 'SMSSS A,B'
-'void __SMU (sw1, sw1)' '__SMU (A, B)' 'SMU A,B'
-'sw2 __SMUL (sw1, sw1)' 'C = __SMUL (A, B)' 'SMUL A,B,C'
-'sw1 __SUBSS (sw1, sw1)' 'C = __SUBSS (A, B)' 'SUBSS A,B,C'
-'uw2 __UMUL (uw1, uw1)' 'C = __UMUL (A, B)' 'UMUL A,B,C'
+`sw1 __ADDSS (sw1, sw1)' `C = __ADDSS (A, B)' `ADDSS A,B,C'
+`sw1 __SCAN (sw1, sw1)' `C = __SCAN (A, B)' `SCAN A,B,C'
+`sw1 __SCUTSS (sw1)' `B = __SCUTSS (A)' `SCUTSS A,B'
+`sw1 __SLASS (sw1, sw1)' `C = __SLASS (A, B)' `SLASS A,B,C'
+`void __SMASS (sw1, sw1)' `__SMASS (A, B)' `SMASS A,B'
+`void __SMSSS (sw1, sw1)' `__SMSSS (A, B)' `SMSSS A,B'
+`void __SMU (sw1, sw1)' `__SMU (A, B)' `SMU A,B'
+`sw2 __SMUL (sw1, sw1)' `C = __SMUL (A, B)' `SMUL A,B,C'
+`sw1 __SUBSS (sw1, sw1)' `C = __SUBSS (A, B)' `SUBSS A,B,C'
+`uw2 __UMUL (uw1, uw1)' `C = __UMUL (A, B)' `UMUL A,B,C'

File: gcc.info, Node: Directly-mapped Media Functions, Next: Raw read/write Functions, Prev: Directly-mapped Integer Functions, Up: FR-V Built-in Functions
@@ -34901,143 +35316,99 @@ File: gcc.info, Node: Directly-mapped Media Functions, Next: Raw read/write Fu
The functions listed below map directly to FR-V M-type instructions.
Function prototype Example usage Assembly output
-'uw1 __MABSHS (sw1)' 'B = __MABSHS (A)' 'MABSHS A,B'
-'void __MADDACCS (acc, acc)' '__MADDACCS (B, A)' 'MADDACCS A,B'
-'sw1 __MADDHSS (sw1, sw1)' 'C = __MADDHSS (A, 'MADDHSS A,B,C'
- B)'
-'uw1 __MADDHUS (uw1, uw1)' 'C = __MADDHUS (A, 'MADDHUS A,B,C'
- B)'
-'uw1 __MAND (uw1, uw1)' 'C = __MAND (A, B)' 'MAND A,B,C'
-'void __MASACCS (acc, acc)' '__MASACCS (B, A)' 'MASACCS A,B'
-'uw1 __MAVEH (uw1, uw1)' 'C = __MAVEH (A, B)' 'MAVEH A,B,C'
-'uw2 __MBTOH (uw1)' 'B = __MBTOH (A)' 'MBTOH A,B'
-'void __MBTOHE (uw1 *, uw1)' '__MBTOHE (&B, A)' 'MBTOHE A,B'
-'void __MCLRACC (acc)' '__MCLRACC (A)' 'MCLRACC A'
-'void __MCLRACCA (void)' '__MCLRACCA ()' 'MCLRACCA'
-'uw1 __Mcop1 (uw1, uw1)' 'C = __Mcop1 (A, B)' 'Mcop1 A,B,C'
-'uw1 __Mcop2 (uw1, uw1)' 'C = __Mcop2 (A, B)' 'Mcop2 A,B,C'
-'uw1 __MCPLHI (uw2, const)' 'C = __MCPLHI (A, B)' 'MCPLHI A,#B,C'
-'uw1 __MCPLI (uw2, const)' 'C = __MCPLI (A, B)' 'MCPLI A,#B,C'
-'void __MCPXIS (acc, sw1, '__MCPXIS (C, A, B)' 'MCPXIS A,B,C'
-sw1)'
-'void __MCPXIU (acc, uw1, '__MCPXIU (C, A, B)' 'MCPXIU A,B,C'
-uw1)'
-'void __MCPXRS (acc, sw1, '__MCPXRS (C, A, B)' 'MCPXRS A,B,C'
-sw1)'
-'void __MCPXRU (acc, uw1, '__MCPXRU (C, A, B)' 'MCPXRU A,B,C'
-uw1)'
-'uw1 __MCUT (acc, uw1)' 'C = __MCUT (A, B)' 'MCUT A,B,C'
-'uw1 __MCUTSS (acc, sw1)' 'C = __MCUTSS (A, B)' 'MCUTSS A,B,C'
-'void __MDADDACCS (acc, acc)' '__MDADDACCS (B, A)' 'MDADDACCS A,B'
-'void __MDASACCS (acc, acc)' '__MDASACCS (B, A)' 'MDASACCS A,B'
-'uw2 __MDCUTSSI (acc, const)' 'C = __MDCUTSSI (A, 'MDCUTSSI
- B)' A,#B,C'
-'uw2 __MDPACKH (uw2, uw2)' 'C = __MDPACKH (A, 'MDPACKH A,B,C'
- B)'
-'uw2 __MDROTLI (uw2, const)' 'C = __MDROTLI (A, 'MDROTLI
- B)' A,#B,C'
-'void __MDSUBACCS (acc, acc)' '__MDSUBACCS (B, A)' 'MDSUBACCS A,B'
-'void __MDUNPACKH (uw1 *, '__MDUNPACKH (&B, A)' 'MDUNPACKH A,B'
-uw2)'
-'uw2 __MEXPDHD (uw1, const)' 'C = __MEXPDHD (A, 'MEXPDHD
- B)' A,#B,C'
-'uw1 __MEXPDHW (uw1, const)' 'C = __MEXPDHW (A, 'MEXPDHW
- B)' A,#B,C'
-'uw1 __MHDSETH (uw1, const)' 'C = __MHDSETH (A, 'MHDSETH
- B)' A,#B,C'
-'sw1 __MHDSETS (const)' 'B = __MHDSETS (A)' 'MHDSETS #A,B'
-'uw1 __MHSETHIH (uw1, const)' 'B = __MHSETHIH (B, 'MHSETHIH #A,B'
- A)'
-'sw1 __MHSETHIS (sw1, const)' 'B = __MHSETHIS (B, 'MHSETHIS #A,B'
- A)'
-'uw1 __MHSETLOH (uw1, const)' 'B = __MHSETLOH (B, 'MHSETLOH #A,B'
- A)'
-'sw1 __MHSETLOS (sw1, const)' 'B = __MHSETLOS (B, 'MHSETLOS #A,B'
- A)'
-'uw1 __MHTOB (uw2)' 'B = __MHTOB (A)' 'MHTOB A,B'
-'void __MMACHS (acc, sw1, '__MMACHS (C, A, B)' 'MMACHS A,B,C'
-sw1)'
-'void __MMACHU (acc, uw1, '__MMACHU (C, A, B)' 'MMACHU A,B,C'
-uw1)'
-'void __MMRDHS (acc, sw1, '__MMRDHS (C, A, B)' 'MMRDHS A,B,C'
-sw1)'
-'void __MMRDHU (acc, uw1, '__MMRDHU (C, A, B)' 'MMRDHU A,B,C'
-uw1)'
-'void __MMULHS (acc, sw1, '__MMULHS (C, A, B)' 'MMULHS A,B,C'
-sw1)'
-'void __MMULHU (acc, uw1, '__MMULHU (C, A, B)' 'MMULHU A,B,C'
-uw1)'
-'void __MMULXHS (acc, sw1, '__MMULXHS (C, A, B)' 'MMULXHS A,B,C'
-sw1)'
-'void __MMULXHU (acc, uw1, '__MMULXHU (C, A, B)' 'MMULXHU A,B,C'
-uw1)'
-'uw1 __MNOT (uw1)' 'B = __MNOT (A)' 'MNOT A,B'
-'uw1 __MOR (uw1, uw1)' 'C = __MOR (A, B)' 'MOR A,B,C'
-'uw1 __MPACKH (uh, uh)' 'C = __MPACKH (A, B)' 'MPACKH A,B,C'
-'sw2 __MQADDHSS (sw2, sw2)' 'C = __MQADDHSS (A, 'MQADDHSS
- B)' A,B,C'
-'uw2 __MQADDHUS (uw2, uw2)' 'C = __MQADDHUS (A, 'MQADDHUS
- B)' A,B,C'
-'void __MQCPXIS (acc, sw2, '__MQCPXIS (C, A, B)' 'MQCPXIS A,B,C'
-sw2)'
-'void __MQCPXIU (acc, uw2, '__MQCPXIU (C, A, B)' 'MQCPXIU A,B,C'
-uw2)'
-'void __MQCPXRS (acc, sw2, '__MQCPXRS (C, A, B)' 'MQCPXRS A,B,C'
-sw2)'
-'void __MQCPXRU (acc, uw2, '__MQCPXRU (C, A, B)' 'MQCPXRU A,B,C'
-uw2)'
-'sw2 __MQLCLRHS (sw2, sw2)' 'C = __MQLCLRHS (A, 'MQLCLRHS
- B)' A,B,C'
-'sw2 __MQLMTHS (sw2, sw2)' 'C = __MQLMTHS (A, 'MQLMTHS A,B,C'
- B)'
-'void __MQMACHS (acc, sw2, '__MQMACHS (C, A, B)' 'MQMACHS A,B,C'
-sw2)'
-'void __MQMACHU (acc, uw2, '__MQMACHU (C, A, B)' 'MQMACHU A,B,C'
-uw2)'
-'void __MQMACXHS (acc, sw2, '__MQMACXHS (C, A, 'MQMACXHS
-sw2)' B)' A,B,C'
-'void __MQMULHS (acc, sw2, '__MQMULHS (C, A, B)' 'MQMULHS A,B,C'
-sw2)'
-'void __MQMULHU (acc, uw2, '__MQMULHU (C, A, B)' 'MQMULHU A,B,C'
-uw2)'
-'void __MQMULXHS (acc, sw2, '__MQMULXHS (C, A, 'MQMULXHS
-sw2)' B)' A,B,C'
-'void __MQMULXHU (acc, uw2, '__MQMULXHU (C, A, 'MQMULXHU
-uw2)' B)' A,B,C'
-'sw2 __MQSATHS (sw2, sw2)' 'C = __MQSATHS (A, 'MQSATHS A,B,C'
- B)'
-'uw2 __MQSLLHI (uw2, int)' 'C = __MQSLLHI (A, 'MQSLLHI A,B,C'
- B)'
-'sw2 __MQSRAHI (sw2, int)' 'C = __MQSRAHI (A, 'MQSRAHI A,B,C'
- B)'
-'sw2 __MQSUBHSS (sw2, sw2)' 'C = __MQSUBHSS (A, 'MQSUBHSS
- B)' A,B,C'
-'uw2 __MQSUBHUS (uw2, uw2)' 'C = __MQSUBHUS (A, 'MQSUBHUS
- B)' A,B,C'
-'void __MQXMACHS (acc, sw2, '__MQXMACHS (C, A, 'MQXMACHS
-sw2)' B)' A,B,C'
-'void __MQXMACXHS (acc, sw2, '__MQXMACXHS (C, A, 'MQXMACXHS
-sw2)' B)' A,B,C'
-'uw1 __MRDACC (acc)' 'B = __MRDACC (A)' 'MRDACC A,B'
-'uw1 __MRDACCG (acc)' 'B = __MRDACCG (A)' 'MRDACCG A,B'
-'uw1 __MROTLI (uw1, const)' 'C = __MROTLI (A, B)' 'MROTLI A,#B,C'
-'uw1 __MROTRI (uw1, const)' 'C = __MROTRI (A, B)' 'MROTRI A,#B,C'
-'sw1 __MSATHS (sw1, sw1)' 'C = __MSATHS (A, B)' 'MSATHS A,B,C'
-'uw1 __MSATHU (uw1, uw1)' 'C = __MSATHU (A, B)' 'MSATHU A,B,C'
-'uw1 __MSLLHI (uw1, const)' 'C = __MSLLHI (A, B)' 'MSLLHI A,#B,C'
-'sw1 __MSRAHI (sw1, const)' 'C = __MSRAHI (A, B)' 'MSRAHI A,#B,C'
-'uw1 __MSRLHI (uw1, const)' 'C = __MSRLHI (A, B)' 'MSRLHI A,#B,C'
-'void __MSUBACCS (acc, acc)' '__MSUBACCS (B, A)' 'MSUBACCS A,B'
-'sw1 __MSUBHSS (sw1, sw1)' 'C = __MSUBHSS (A, 'MSUBHSS A,B,C'
- B)'
-'uw1 __MSUBHUS (uw1, uw1)' 'C = __MSUBHUS (A, 'MSUBHUS A,B,C'
- B)'
-'void __MTRAP (void)' '__MTRAP ()' 'MTRAP'
-'uw2 __MUNPACKH (uw1)' 'B = __MUNPACKH (A)' 'MUNPACKH A,B'
-'uw1 __MWCUT (uw2, uw1)' 'C = __MWCUT (A, B)' 'MWCUT A,B,C'
-'void __MWTACC (acc, uw1)' '__MWTACC (B, A)' 'MWTACC A,B'
-'void __MWTACCG (acc, uw1)' '__MWTACCG (B, A)' 'MWTACCG A,B'
-'uw1 __MXOR (uw1, uw1)' 'C = __MXOR (A, B)' 'MXOR A,B,C'
+`uw1 __MABSHS (sw1)' `B = __MABSHS (A)' `MABSHS A,B'
+`void __MADDACCS (acc, acc)' `__MADDACCS (B, A)' `MADDACCS A,B'
+`sw1 __MADDHSS (sw1, sw1)' `C = __MADDHSS (A, B)' `MADDHSS A,B,C'
+`uw1 __MADDHUS (uw1, uw1)' `C = __MADDHUS (A, B)' `MADDHUS A,B,C'
+`uw1 __MAND (uw1, uw1)' `C = __MAND (A, B)' `MAND A,B,C'
+`void __MASACCS (acc, acc)' `__MASACCS (B, A)' `MASACCS A,B'
+`uw1 __MAVEH (uw1, uw1)' `C = __MAVEH (A, B)' `MAVEH A,B,C'
+`uw2 __MBTOH (uw1)' `B = __MBTOH (A)' `MBTOH A,B'
+`void __MBTOHE (uw1 *, uw1)' `__MBTOHE (&B, A)' `MBTOHE A,B'
+`void __MCLRACC (acc)' `__MCLRACC (A)' `MCLRACC A'
+`void __MCLRACCA (void)' `__MCLRACCA ()' `MCLRACCA'
+`uw1 __Mcop1 (uw1, uw1)' `C = __Mcop1 (A, B)' `Mcop1 A,B,C'
+`uw1 __Mcop2 (uw1, uw1)' `C = __Mcop2 (A, B)' `Mcop2 A,B,C'
+`uw1 __MCPLHI (uw2, const)' `C = __MCPLHI (A, B)' `MCPLHI A,#B,C'
+`uw1 __MCPLI (uw2, const)' `C = __MCPLI (A, B)' `MCPLI A,#B,C'
+`void __MCPXIS (acc, sw1, sw1)' `__MCPXIS (C, A, B)' `MCPXIS A,B,C'
+`void __MCPXIU (acc, uw1, uw1)' `__MCPXIU (C, A, B)' `MCPXIU A,B,C'
+`void __MCPXRS (acc, sw1, sw1)' `__MCPXRS (C, A, B)' `MCPXRS A,B,C'
+`void __MCPXRU (acc, uw1, uw1)' `__MCPXRU (C, A, B)' `MCPXRU A,B,C'
+`uw1 __MCUT (acc, uw1)' `C = __MCUT (A, B)' `MCUT A,B,C'
+`uw1 __MCUTSS (acc, sw1)' `C = __MCUTSS (A, B)' `MCUTSS A,B,C'
+`void __MDADDACCS (acc, acc)' `__MDADDACCS (B, A)' `MDADDACCS A,B'
+`void __MDASACCS (acc, acc)' `__MDASACCS (B, A)' `MDASACCS A,B'
+`uw2 __MDCUTSSI (acc, const)' `C = __MDCUTSSI (A, B)' `MDCUTSSI A,#B,C'
+`uw2 __MDPACKH (uw2, uw2)' `C = __MDPACKH (A, B)' `MDPACKH A,B,C'
+`uw2 __MDROTLI (uw2, const)' `C = __MDROTLI (A, B)' `MDROTLI A,#B,C'
+`void __MDSUBACCS (acc, acc)' `__MDSUBACCS (B, A)' `MDSUBACCS A,B'
+`void __MDUNPACKH (uw1 *, uw2)' `__MDUNPACKH (&B, A)' `MDUNPACKH A,B'
+`uw2 __MEXPDHD (uw1, const)' `C = __MEXPDHD (A, B)' `MEXPDHD A,#B,C'
+`uw1 __MEXPDHW (uw1, const)' `C = __MEXPDHW (A, B)' `MEXPDHW A,#B,C'
+`uw1 __MHDSETH (uw1, const)' `C = __MHDSETH (A, B)' `MHDSETH A,#B,C'
+`sw1 __MHDSETS (const)' `B = __MHDSETS (A)' `MHDSETS #A,B'
+`uw1 __MHSETHIH (uw1, const)' `B = __MHSETHIH (B, A)' `MHSETHIH #A,B'
+`sw1 __MHSETHIS (sw1, const)' `B = __MHSETHIS (B, A)' `MHSETHIS #A,B'
+`uw1 __MHSETLOH (uw1, const)' `B = __MHSETLOH (B, A)' `MHSETLOH #A,B'
+`sw1 __MHSETLOS (sw1, const)' `B = __MHSETLOS (B, A)' `MHSETLOS #A,B'
+`uw1 __MHTOB (uw2)' `B = __MHTOB (A)' `MHTOB A,B'
+`void __MMACHS (acc, sw1, sw1)' `__MMACHS (C, A, B)' `MMACHS A,B,C'
+`void __MMACHU (acc, uw1, uw1)' `__MMACHU (C, A, B)' `MMACHU A,B,C'
+`void __MMRDHS (acc, sw1, sw1)' `__MMRDHS (C, A, B)' `MMRDHS A,B,C'
+`void __MMRDHU (acc, uw1, uw1)' `__MMRDHU (C, A, B)' `MMRDHU A,B,C'
+`void __MMULHS (acc, sw1, sw1)' `__MMULHS (C, A, B)' `MMULHS A,B,C'
+`void __MMULHU (acc, uw1, uw1)' `__MMULHU (C, A, B)' `MMULHU A,B,C'
+`void __MMULXHS (acc, sw1, sw1)' `__MMULXHS (C, A, B)' `MMULXHS A,B,C'
+`void __MMULXHU (acc, uw1, uw1)' `__MMULXHU (C, A, B)' `MMULXHU A,B,C'
+`uw1 __MNOT (uw1)' `B = __MNOT (A)' `MNOT A,B'
+`uw1 __MOR (uw1, uw1)' `C = __MOR (A, B)' `MOR A,B,C'
+`uw1 __MPACKH (uh, uh)' `C = __MPACKH (A, B)' `MPACKH A,B,C'
+`sw2 __MQADDHSS (sw2, sw2)' `C = __MQADDHSS (A, B)' `MQADDHSS A,B,C'
+`uw2 __MQADDHUS (uw2, uw2)' `C = __MQADDHUS (A, B)' `MQADDHUS A,B,C'
+`void __MQCPXIS (acc, sw2, sw2)' `__MQCPXIS (C, A, B)' `MQCPXIS A,B,C'
+`void __MQCPXIU (acc, uw2, uw2)' `__MQCPXIU (C, A, B)' `MQCPXIU A,B,C'
+`void __MQCPXRS (acc, sw2, sw2)' `__MQCPXRS (C, A, B)' `MQCPXRS A,B,C'
+`void __MQCPXRU (acc, uw2, uw2)' `__MQCPXRU (C, A, B)' `MQCPXRU A,B,C'
+`sw2 __MQLCLRHS (sw2, sw2)' `C = __MQLCLRHS (A, B)' `MQLCLRHS A,B,C'
+`sw2 __MQLMTHS (sw2, sw2)' `C = __MQLMTHS (A, B)' `MQLMTHS A,B,C'
+`void __MQMACHS (acc, sw2, sw2)' `__MQMACHS (C, A, B)' `MQMACHS A,B,C'
+`void __MQMACHU (acc, uw2, uw2)' `__MQMACHU (C, A, B)' `MQMACHU A,B,C'
+`void __MQMACXHS (acc, sw2, `__MQMACXHS (C, A, B)' `MQMACXHS A,B,C'
+sw2)'
+`void __MQMULHS (acc, sw2, sw2)' `__MQMULHS (C, A, B)' `MQMULHS A,B,C'
+`void __MQMULHU (acc, uw2, uw2)' `__MQMULHU (C, A, B)' `MQMULHU A,B,C'
+`void __MQMULXHS (acc, sw2, `__MQMULXHS (C, A, B)' `MQMULXHS A,B,C'
+sw2)'
+`void __MQMULXHU (acc, uw2, `__MQMULXHU (C, A, B)' `MQMULXHU A,B,C'
+uw2)'
+`sw2 __MQSATHS (sw2, sw2)' `C = __MQSATHS (A, B)' `MQSATHS A,B,C'
+`uw2 __MQSLLHI (uw2, int)' `C = __MQSLLHI (A, B)' `MQSLLHI A,B,C'
+`sw2 __MQSRAHI (sw2, int)' `C = __MQSRAHI (A, B)' `MQSRAHI A,B,C'
+`sw2 __MQSUBHSS (sw2, sw2)' `C = __MQSUBHSS (A, B)' `MQSUBHSS A,B,C'
+`uw2 __MQSUBHUS (uw2, uw2)' `C = __MQSUBHUS (A, B)' `MQSUBHUS A,B,C'
+`void __MQXMACHS (acc, sw2, `__MQXMACHS (C, A, B)' `MQXMACHS A,B,C'
+sw2)'
+`void __MQXMACXHS (acc, sw2, `__MQXMACXHS (C, A, B)' `MQXMACXHS A,B,C'
+sw2)'
+`uw1 __MRDACC (acc)' `B = __MRDACC (A)' `MRDACC A,B'
+`uw1 __MRDACCG (acc)' `B = __MRDACCG (A)' `MRDACCG A,B'
+`uw1 __MROTLI (uw1, const)' `C = __MROTLI (A, B)' `MROTLI A,#B,C'
+`uw1 __MROTRI (uw1, const)' `C = __MROTRI (A, B)' `MROTRI A,#B,C'
+`sw1 __MSATHS (sw1, sw1)' `C = __MSATHS (A, B)' `MSATHS A,B,C'
+`uw1 __MSATHU (uw1, uw1)' `C = __MSATHU (A, B)' `MSATHU A,B,C'
+`uw1 __MSLLHI (uw1, const)' `C = __MSLLHI (A, B)' `MSLLHI A,#B,C'
+`sw1 __MSRAHI (sw1, const)' `C = __MSRAHI (A, B)' `MSRAHI A,#B,C'
+`uw1 __MSRLHI (uw1, const)' `C = __MSRLHI (A, B)' `MSRLHI A,#B,C'
+`void __MSUBACCS (acc, acc)' `__MSUBACCS (B, A)' `MSUBACCS A,B'
+`sw1 __MSUBHSS (sw1, sw1)' `C = __MSUBHSS (A, B)' `MSUBHSS A,B,C'
+`uw1 __MSUBHUS (uw1, uw1)' `C = __MSUBHUS (A, B)' `MSUBHUS A,B,C'
+`void __MTRAP (void)' `__MTRAP ()' `MTRAP'
+`uw2 __MUNPACKH (uw1)' `B = __MUNPACKH (A)' `MUNPACKH A,B'
+`uw1 __MWCUT (uw2, uw1)' `C = __MWCUT (A, B)' `MWCUT A,B,C'
+`void __MWTACC (acc, uw1)' `__MWTACC (B, A)' `MWTACC A,B'
+`void __MWTACCG (acc, uw1)' `__MWTACCG (B, A)' `MWTACCG A,B'
+`uw1 __MXOR (uw1, uw1)' `C = __MXOR (A, B)' `MXOR A,B,C'

File: gcc.info, Node: Raw read/write Functions, Next: Other Built-in Functions, Prev: Directly-mapped Media Functions, Up: FR-V Built-in Functions
@@ -35046,19 +35417,25 @@ File: gcc.info, Node: Raw read/write Functions, Next: Other Built-in Functions
..................................
This sections describes built-in functions related to read and write
-instructions to access memory. These functions generate 'membar'
+instructions to access memory. These functions generate `membar'
instructions to flush the I/O load and stores where appropriate, as
described in Fujitsu's manual described above.
-'unsigned char __builtin_read8 (void *DATA)'
-'unsigned short __builtin_read16 (void *DATA)'
-'unsigned long __builtin_read32 (void *DATA)'
-'unsigned long long __builtin_read64 (void *DATA)'
+`unsigned char __builtin_read8 (void *DATA)'
+
+`unsigned short __builtin_read16 (void *DATA)'
+
+`unsigned long __builtin_read32 (void *DATA)'
+
+`unsigned long long __builtin_read64 (void *DATA)'
+
+`void __builtin_write8 (void *DATA, unsigned char DATUM)'
+
+`void __builtin_write16 (void *DATA, unsigned short DATUM)'
-'void __builtin_write8 (void *DATA, unsigned char DATUM)'
-'void __builtin_write16 (void *DATA, unsigned short DATUM)'
-'void __builtin_write32 (void *DATA, unsigned long DATUM)'
-'void __builtin_write64 (void *DATA, unsigned long long DATUM)'
+`void __builtin_write32 (void *DATA, unsigned long DATUM)'
+
+`void __builtin_write64 (void *DATA, unsigned long long DATUM)'

File: gcc.info, Node: Other Built-in Functions, Prev: Raw read/write Functions, Up: FR-V Built-in Functions
@@ -35069,28 +35446,28 @@ File: gcc.info, Node: Other Built-in Functions, Prev: Raw read/write Functions
This section describes built-in functions that are not named after a
specific FR-V instruction.
-'sw2 __IACCreadll (iacc REG)'
+`sw2 __IACCreadll (iacc REG)'
Return the full 64-bit value of IACC0. The REG argument is
reserved for future expansion and must be 0.
-'sw1 __IACCreadl (iacc REG)'
+`sw1 __IACCreadl (iacc REG)'
Return the value of IACC0H if REG is 0 and IACC0L if REG is 1.
Other values of REG are rejected as invalid.
-'void __IACCsetll (iacc REG, sw2 X)'
+`void __IACCsetll (iacc REG, sw2 X)'
Set the full 64-bit value of IACC0 to X. The REG argument is
reserved for future expansion and must be 0.
-'void __IACCsetl (iacc REG, sw1 X)'
+`void __IACCsetl (iacc REG, sw1 X)'
Set IACC0H to X if REG is 0 and IACC0L to X if REG is 1. Other
values of REG are rejected as invalid.
-'void __data_prefetch0 (const void *X)'
- Use the 'dcpl' instruction to load the contents of address X into
+`void __data_prefetch0 (const void *X)'
+ Use the `dcpl' instruction to load the contents of address X into
the data cache.
-'void __data_prefetch (const void *X)'
- Use the 'nldub' instruction to load the contents of address X into
+`void __data_prefetch (const void *X)'
+ Use the `nldub' instruction to load the contents of address X into
the data cache. The instruction is issued in slot I1.

@@ -35105,34 +35482,34 @@ media applications. It provides instructions that operate on packed
8-bit/16-bit integer data, Q7, Q15 and Q31 fractional data.
GCC supports MIPS DSP operations using both the generic vector
-extensions (*note Vector Extensions::) and a collection of MIPS-specific
-built-in functions. Both kinds of support are enabled by the '-mdsp'
-command-line option.
+extensions (*note Vector Extensions::) and a collection of
+MIPS-specific built-in functions. Both kinds of support are enabled by
+the `-mdsp' command-line option.
Revision 2 of the ASE was introduced in the second half of 2006. This
revision adds extra instructions to the original ASE, but is otherwise
backwards-compatible with it. You can select revision 2 using the
-command-line option '-mdspr2'; this option implies '-mdsp'.
+command-line option `-mdspr2'; this option implies `-mdsp'.
The SCOUNT and POS bits of the DSP control register are global. The
-WRDSP, EXTPDP, EXTPDPV and MTHLIP instructions modify the SCOUNT and POS
-bits. During optimization, the compiler does not delete these
+WRDSP, EXTPDP, EXTPDPV and MTHLIP instructions modify the SCOUNT and
+POS bits. During optimization, the compiler does not delete these
instructions and it does not delete calls to functions containing these
instructions.
- At present, GCC only provides support for operations on 32-bit vectors.
-The vector type associated with 8-bit integer data is usually called
-'v4i8', the vector type associated with Q7 is usually called 'v4q7', the
-vector type associated with 16-bit integer data is usually called
-'v2i16', and the vector type associated with Q15 is usually called
-'v2q15'. They can be defined in C as follows:
+ At present, GCC only provides support for operations on 32-bit
+vectors. The vector type associated with 8-bit integer data is usually
+called `v4i8', the vector type associated with Q7 is usually called
+`v4q7', the vector type associated with 16-bit integer data is usually
+called `v2i16', and the vector type associated with Q15 is usually
+called `v2q15'. They can be defined in C as follows:
typedef signed char v4i8 __attribute__ ((vector_size(4)));
typedef signed char v4q7 __attribute__ ((vector_size(4)));
typedef short v2i16 __attribute__ ((vector_size(4)));
typedef short v2q15 __attribute__ ((vector_size(4)));
- 'v4i8', 'v4q7', 'v2i16' and 'v2q15' values are initialized in the same
+ `v4i8', `v4q7', `v2i16' and `v2q15' values are initialized in the same
way as aggregates. For example:
v4i8 a = {1, 2, 3, 4};
@@ -35147,30 +35524,30 @@ way as aggregates. For example:
packed. On little-endian targets, the first value is the least
significant and the last value is the most significant. The opposite
order applies to big-endian targets. For example, the code above sets
-the lowest byte of 'a' to '1' on little-endian targets and '4' on
+the lowest byte of `a' to `1' on little-endian targets and `4' on
big-endian targets.
_Note:_ Q7, Q15 and Q31 values must be initialized with their integer
-representation. As shown in this example, the integer representation of
-a Q7 value can be obtained by multiplying the fractional value by
-'0x1.0p7'. The equivalent for Q15 values is to multiply by '0x1.0p15'.
-The equivalent for Q31 values is to multiply by '0x1.0p31'.
+representation. As shown in this example, the integer representation
+of a Q7 value can be obtained by multiplying the fractional value by
+`0x1.0p7'. The equivalent for Q15 values is to multiply by `0x1.0p15'.
+The equivalent for Q31 values is to multiply by `0x1.0p31'.
- The table below lists the 'v4i8' and 'v2q15' operations for which
-hardware support exists. 'a' and 'b' are 'v4i8' values, and 'c' and 'd'
-are 'v2q15' values.
+ The table below lists the `v4i8' and `v2q15' operations for which
+hardware support exists. `a' and `b' are `v4i8' values, and `c' and
+`d' are `v2q15' values.
C code MIPS instruction
-'a + b' 'addu.qb'
-'c + d' 'addq.ph'
-'a - b' 'subu.qb'
-'c - d' 'subq.ph'
+`a + b' `addu.qb'
+`c + d' `addq.ph'
+`a - b' `subu.qb'
+`c - d' `subq.ph'
- The table below lists the 'v2i16' operation for which hardware support
-exists for the DSP ASE REV 2. 'e' and 'f' are 'v2i16' values.
+ The table below lists the `v2i16' operation for which hardware support
+exists for the DSP ASE REV 2. `e' and `f' are `v2i16' values.
C code MIPS instruction
-'e * f' 'mul.ph'
+`e * f' `mul.ph'
It is easier to describe the DSP built-in functions if we first define
the following types:
@@ -35180,11 +35557,11 @@ the following types:
typedef unsigned int ui32;
typedef long long a64;
- 'q31' and 'i32' are actually the same as 'int', but we use 'q31' to
-indicate a Q31 fractional value and 'i32' to indicate a 32-bit integer
-value. Similarly, 'a64' is the same as 'long long', but we use 'a64' to
-indicate values that are placed in one of the four DSP accumulators
-('$ac0', '$ac1', '$ac2' or '$ac3').
+ `q31' and `i32' are actually the same as `int', but we use `q31' to
+indicate a Q31 fractional value and `i32' to indicate a 32-bit integer
+value. Similarly, `a64' is the same as `long long', but we use `a64'
+to indicate values that are placed in one of the four DSP accumulators
+(`$ac0', `$ac1', `$ac2' or `$ac3').
Also, some built-in functions prefer or require immediate numbers as
parameters, because the corresponding DSP instructions accept both
@@ -35201,8 +35578,8 @@ only. The immediate parameters are listed as follows.
imm_n512_511: -512 to 511.
The following built-in functions map directly to a particular MIPS DSP
-instruction. Please refer to the architecture specification for details
-on what each instruction does.
+instruction. Please refer to the architecture specification for
+details on what each instruction does.
v2q15 __builtin_mips_addq_ph (v2q15, v2q15)
v2q15 __builtin_mips_addq_s_ph (v2q15, v2q15)
@@ -35373,21 +35750,22 @@ File: gcc.info, Node: MIPS Paired-Single Support, Next: MIPS Loongson Built-in
----------------------------------
The MIPS64 architecture includes a number of instructions that operate
-on pairs of single-precision floating-point values. Each pair is packed
-into a 64-bit floating-point register, with one element being designated
-the "upper half" and the other being designated the "lower half".
+on pairs of single-precision floating-point values. Each pair is
+packed into a 64-bit floating-point register, with one element being
+designated the "upper half" and the other being designated the "lower
+half".
GCC supports paired-single operations using both the generic vector
-extensions (*note Vector Extensions::) and a collection of MIPS-specific
-built-in functions. Both kinds of support are enabled by the
-'-mpaired-single' command-line option.
+extensions (*note Vector Extensions::) and a collection of
+MIPS-specific built-in functions. Both kinds of support are enabled by
+the `-mpaired-single' command-line option.
The vector type associated with paired-single values is usually called
-'v2sf'. It can be defined in C as follows:
+`v2sf'. It can be defined in C as follows:
typedef float v2sf __attribute__ ((vector_size (8)));
- 'v2sf' values are initialized in the same way as aggregates. For
+ `v2sf' values are initialized in the same way as aggregates. For
example:
v2sf a = {1.5, 9.1};
@@ -35398,9 +35776,9 @@ example:
_Note:_ The CPU's endianness determines which value is stored in the
upper half of a register and which value is stored in the lower half.
On little-endian targets, the first value is the lower one and the
-second value is the upper one. The opposite order applies to big-endian
-targets. For example, the code above sets the lower half of 'a' to
-'1.5' on little-endian targets and '9.1' on big-endian targets.
+second value is the upper one. The opposite order applies to
+big-endian targets. For example, the code above sets the lower half of
+`a' to `1.5' on little-endian targets and `9.1' on big-endian targets.

File: gcc.info, Node: MIPS Loongson Built-in Functions, Next: Other MIPS Built-in Functions, Prev: MIPS Paired-Single Support, Up: Target Builtins
@@ -35410,15 +35788,20 @@ File: gcc.info, Node: MIPS Loongson Built-in Functions, Next: Other MIPS Built
GCC provides intrinsics to access the SIMD instructions provided by the
ST Microelectronics Loongson-2E and -2F processors. These intrinsics,
-available after inclusion of the 'loongson.h' header file, operate on
+available after inclusion of the `loongson.h' header file, operate on
the following 64-bit vector types:
- * 'uint8x8_t', a vector of eight unsigned 8-bit integers;
- * 'uint16x4_t', a vector of four unsigned 16-bit integers;
- * 'uint32x2_t', a vector of two unsigned 32-bit integers;
- * 'int8x8_t', a vector of eight signed 8-bit integers;
- * 'int16x4_t', a vector of four signed 16-bit integers;
- * 'int32x2_t', a vector of two signed 32-bit integers.
+ * `uint8x8_t', a vector of eight unsigned 8-bit integers;
+
+ * `uint16x4_t', a vector of four unsigned 16-bit integers;
+
+ * `uint32x2_t', a vector of two unsigned 32-bit integers;
+
+ * `int8x8_t', a vector of eight signed 8-bit integers;
+
+ * `int16x4_t', a vector of four signed 16-bit integers;
+
+ * `int32x2_t', a vector of two signed 32-bit integers.
The intrinsics provided are listed below; each is named after the
machine instruction to which it corresponds, with suffixes added as
@@ -35539,23 +35922,23 @@ File: gcc.info, Node: Paired-Single Arithmetic, Next: Paired-Single Built-in F
6.58.14.1 Paired-Single Arithmetic
..................................
-The table below lists the 'v2sf' operations for which hardware support
-exists. 'a', 'b' and 'c' are 'v2sf' values and 'x' is an integral
+The table below lists the `v2sf' operations for which hardware support
+exists. `a', `b' and `c' are `v2sf' values and `x' is an integral
value.
C code MIPS instruction
-'a + b' 'add.ps'
-'a - b' 'sub.ps'
-'-a' 'neg.ps'
-'a * b' 'mul.ps'
-'a * b + c' 'madd.ps'
-'a * b - c' 'msub.ps'
-'-(a * b + c)' 'nmadd.ps'
-'-(a * b - c)' 'nmsub.ps'
-'x ? a : b' 'movn.ps'/'movz.ps'
+`a + b' `add.ps'
+`a - b' `sub.ps'
+`-a' `neg.ps'
+`a * b' `mul.ps'
+`a * b + c' `madd.ps'
+`a * b - c' `msub.ps'
+`-(a * b + c)' `nmadd.ps'
+`-(a * b - c)' `nmsub.ps'
+`x ? a : b' `movn.ps'/`movz.ps'
Note that the multiply-accumulate instructions can be disabled using
-the command-line option '-mno-fused-madd'.
+the command-line option `-mno-fused-madd'.

File: gcc.info, Node: Paired-Single Built-in Functions, Next: MIPS-3D Built-in Functions, Prev: Paired-Single Arithmetic, Up: MIPS Loongson Built-in Functions
@@ -35564,66 +35947,66 @@ File: gcc.info, Node: Paired-Single Built-in Functions, Next: MIPS-3D Built-in
..........................................
The following paired-single functions map directly to a particular MIPS
-instruction. Please refer to the architecture specification for details
-on what each instruction does.
+instruction. Please refer to the architecture specification for
+details on what each instruction does.
-'v2sf __builtin_mips_pll_ps (v2sf, v2sf)'
- Pair lower lower ('pll.ps').
+`v2sf __builtin_mips_pll_ps (v2sf, v2sf)'
+ Pair lower lower (`pll.ps').
-'v2sf __builtin_mips_pul_ps (v2sf, v2sf)'
- Pair upper lower ('pul.ps').
+`v2sf __builtin_mips_pul_ps (v2sf, v2sf)'
+ Pair upper lower (`pul.ps').
-'v2sf __builtin_mips_plu_ps (v2sf, v2sf)'
- Pair lower upper ('plu.ps').
+`v2sf __builtin_mips_plu_ps (v2sf, v2sf)'
+ Pair lower upper (`plu.ps').
-'v2sf __builtin_mips_puu_ps (v2sf, v2sf)'
- Pair upper upper ('puu.ps').
+`v2sf __builtin_mips_puu_ps (v2sf, v2sf)'
+ Pair upper upper (`puu.ps').
-'v2sf __builtin_mips_cvt_ps_s (float, float)'
- Convert pair to paired single ('cvt.ps.s').
+`v2sf __builtin_mips_cvt_ps_s (float, float)'
+ Convert pair to paired single (`cvt.ps.s').
-'float __builtin_mips_cvt_s_pl (v2sf)'
- Convert pair lower to single ('cvt.s.pl').
+`float __builtin_mips_cvt_s_pl (v2sf)'
+ Convert pair lower to single (`cvt.s.pl').
-'float __builtin_mips_cvt_s_pu (v2sf)'
- Convert pair upper to single ('cvt.s.pu').
+`float __builtin_mips_cvt_s_pu (v2sf)'
+ Convert pair upper to single (`cvt.s.pu').
-'v2sf __builtin_mips_abs_ps (v2sf)'
- Absolute value ('abs.ps').
+`v2sf __builtin_mips_abs_ps (v2sf)'
+ Absolute value (`abs.ps').
-'v2sf __builtin_mips_alnv_ps (v2sf, v2sf, int)'
- Align variable ('alnv.ps').
+`v2sf __builtin_mips_alnv_ps (v2sf, v2sf, int)'
+ Align variable (`alnv.ps').
_Note:_ The value of the third parameter must be 0 or 4 modulo 8,
- otherwise the result is unpredictable. Please read the instruction
- description for details.
+ otherwise the result is unpredictable. Please read the
+ instruction description for details.
The following multi-instruction functions are also available. In each
-case, COND can be any of the 16 floating-point conditions: 'f', 'un',
-'eq', 'ueq', 'olt', 'ult', 'ole', 'ule', 'sf', 'ngle', 'seq', 'ngl',
-'lt', 'nge', 'le' or 'ngt'.
+case, COND can be any of the 16 floating-point conditions: `f', `un',
+`eq', `ueq', `olt', `ult', `ole', `ule', `sf', `ngle', `seq', `ngl',
+`lt', `nge', `le' or `ngt'.
-'v2sf __builtin_mips_movt_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
-'v2sf __builtin_mips_movf_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
- Conditional move based on floating-point comparison ('c.COND.ps',
- 'movt.ps'/'movf.ps').
+`v2sf __builtin_mips_movt_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
+`v2sf __builtin_mips_movf_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
+ Conditional move based on floating-point comparison (`c.COND.ps',
+ `movt.ps'/`movf.ps').
- The 'movt' functions return the value X computed by:
+ The `movt' functions return the value X computed by:
c.COND.ps CC,A,B
mov.ps X,C
movt.ps X,D,CC
- The 'movf' functions are similar but use 'movf.ps' instead of
- 'movt.ps'.
+ The `movf' functions are similar but use `movf.ps' instead of
+ `movt.ps'.
-'int __builtin_mips_upper_c_COND_ps (v2sf A, v2sf B)'
-'int __builtin_mips_lower_c_COND_ps (v2sf A, v2sf B)'
- Comparison of two paired-single values ('c.COND.ps',
- 'bc1t'/'bc1f').
+`int __builtin_mips_upper_c_COND_ps (v2sf A, v2sf B)'
+`int __builtin_mips_lower_c_COND_ps (v2sf A, v2sf B)'
+ Comparison of two paired-single values (`c.COND.ps',
+ `bc1t'/`bc1f').
- These functions compare A and B using 'c.COND.ps' and return either
- the upper or lower half of the result. For example:
+ These functions compare A and B using `c.COND.ps' and return
+ either the upper or lower half of the result. For example:
v2sf a, b;
if (__builtin_mips_upper_c_eq_ps (a, b))
@@ -35645,58 +36028,58 @@ File: gcc.info, Node: MIPS-3D Built-in Functions, Prev: Paired-Single Built-in
The MIPS-3D Application-Specific Extension (ASE) includes additional
paired-single instructions that are designed to improve the performance
of 3D graphics operations. Support for these instructions is controlled
-by the '-mips3d' command-line option.
+by the `-mips3d' command-line option.
The functions listed below map directly to a particular MIPS-3D
instruction. Please refer to the architecture specification for more
details on what each instruction does.
-'v2sf __builtin_mips_addr_ps (v2sf, v2sf)'
- Reduction add ('addr.ps').
+`v2sf __builtin_mips_addr_ps (v2sf, v2sf)'
+ Reduction add (`addr.ps').
-'v2sf __builtin_mips_mulr_ps (v2sf, v2sf)'
- Reduction multiply ('mulr.ps').
+`v2sf __builtin_mips_mulr_ps (v2sf, v2sf)'
+ Reduction multiply (`mulr.ps').
-'v2sf __builtin_mips_cvt_pw_ps (v2sf)'
- Convert paired single to paired word ('cvt.pw.ps').
+`v2sf __builtin_mips_cvt_pw_ps (v2sf)'
+ Convert paired single to paired word (`cvt.pw.ps').
-'v2sf __builtin_mips_cvt_ps_pw (v2sf)'
- Convert paired word to paired single ('cvt.ps.pw').
+`v2sf __builtin_mips_cvt_ps_pw (v2sf)'
+ Convert paired word to paired single (`cvt.ps.pw').
-'float __builtin_mips_recip1_s (float)'
-'double __builtin_mips_recip1_d (double)'
-'v2sf __builtin_mips_recip1_ps (v2sf)'
- Reduced-precision reciprocal (sequence step 1) ('recip1.FMT').
+`float __builtin_mips_recip1_s (float)'
+`double __builtin_mips_recip1_d (double)'
+`v2sf __builtin_mips_recip1_ps (v2sf)'
+ Reduced-precision reciprocal (sequence step 1) (`recip1.FMT').
-'float __builtin_mips_recip2_s (float, float)'
-'double __builtin_mips_recip2_d (double, double)'
-'v2sf __builtin_mips_recip2_ps (v2sf, v2sf)'
- Reduced-precision reciprocal (sequence step 2) ('recip2.FMT').
+`float __builtin_mips_recip2_s (float, float)'
+`double __builtin_mips_recip2_d (double, double)'
+`v2sf __builtin_mips_recip2_ps (v2sf, v2sf)'
+ Reduced-precision reciprocal (sequence step 2) (`recip2.FMT').
-'float __builtin_mips_rsqrt1_s (float)'
-'double __builtin_mips_rsqrt1_d (double)'
-'v2sf __builtin_mips_rsqrt1_ps (v2sf)'
+`float __builtin_mips_rsqrt1_s (float)'
+`double __builtin_mips_rsqrt1_d (double)'
+`v2sf __builtin_mips_rsqrt1_ps (v2sf)'
Reduced-precision reciprocal square root (sequence step 1)
- ('rsqrt1.FMT').
+ (`rsqrt1.FMT').
-'float __builtin_mips_rsqrt2_s (float, float)'
-'double __builtin_mips_rsqrt2_d (double, double)'
-'v2sf __builtin_mips_rsqrt2_ps (v2sf, v2sf)'
+`float __builtin_mips_rsqrt2_s (float, float)'
+`double __builtin_mips_rsqrt2_d (double, double)'
+`v2sf __builtin_mips_rsqrt2_ps (v2sf, v2sf)'
Reduced-precision reciprocal square root (sequence step 2)
- ('rsqrt2.FMT').
+ (`rsqrt2.FMT').
The following multi-instruction functions are also available. In each
-case, COND can be any of the 16 floating-point conditions: 'f', 'un',
-'eq', 'ueq', 'olt', 'ult', 'ole', 'ule', 'sf', 'ngle', 'seq', 'ngl',
-'lt', 'nge', 'le' or 'ngt'.
+case, COND can be any of the 16 floating-point conditions: `f', `un',
+`eq', `ueq', `olt', `ult', `ole', `ule', `sf', `ngle', `seq', `ngl',
+`lt', `nge', `le' or `ngt'.
-'int __builtin_mips_cabs_COND_s (float A, float B)'
-'int __builtin_mips_cabs_COND_d (double A, double B)'
- Absolute comparison of two scalar values ('cabs.COND.FMT',
- 'bc1t'/'bc1f').
+`int __builtin_mips_cabs_COND_s (float A, float B)'
+`int __builtin_mips_cabs_COND_d (double A, double B)'
+ Absolute comparison of two scalar values (`cabs.COND.FMT',
+ `bc1t'/`bc1f').
- These functions compare A and B using 'cabs.COND.s' or
- 'cabs.COND.d' and return the result as a boolean value. For
+ These functions compare A and B using `cabs.COND.s' or
+ `cabs.COND.d' and return the result as a boolean value. For
example:
float a, b;
@@ -35705,12 +36088,12 @@ case, COND can be any of the 16 floating-point conditions: 'f', 'un',
else
false ();
-'int __builtin_mips_upper_cabs_COND_ps (v2sf A, v2sf B)'
-'int __builtin_mips_lower_cabs_COND_ps (v2sf A, v2sf B)'
- Absolute comparison of two paired-single values ('cabs.COND.ps',
- 'bc1t'/'bc1f').
+`int __builtin_mips_upper_cabs_COND_ps (v2sf A, v2sf B)'
+`int __builtin_mips_lower_cabs_COND_ps (v2sf A, v2sf B)'
+ Absolute comparison of two paired-single values (`cabs.COND.ps',
+ `bc1t'/`bc1f').
- These functions compare A and B using 'cabs.COND.ps' and return
+ These functions compare A and B using `cabs.COND.ps' and return
either the upper or lower half of the result. For example:
v2sf a, b;
@@ -35724,31 +36107,31 @@ case, COND can be any of the 16 floating-point conditions: 'f', 'un',
else
lower_halves_are_unequal ();
-'v2sf __builtin_mips_movt_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
-'v2sf __builtin_mips_movf_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
- Conditional move based on absolute comparison ('cabs.COND.ps',
- 'movt.ps'/'movf.ps').
+`v2sf __builtin_mips_movt_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
+`v2sf __builtin_mips_movf_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)'
+ Conditional move based on absolute comparison (`cabs.COND.ps',
+ `movt.ps'/`movf.ps').
- The 'movt' functions return the value X computed by:
+ The `movt' functions return the value X computed by:
cabs.COND.ps CC,A,B
mov.ps X,C
movt.ps X,D,CC
- The 'movf' functions are similar but use 'movf.ps' instead of
- 'movt.ps'.
+ The `movf' functions are similar but use `movf.ps' instead of
+ `movt.ps'.
-'int __builtin_mips_any_c_COND_ps (v2sf A, v2sf B)'
-'int __builtin_mips_all_c_COND_ps (v2sf A, v2sf B)'
-'int __builtin_mips_any_cabs_COND_ps (v2sf A, v2sf B)'
-'int __builtin_mips_all_cabs_COND_ps (v2sf A, v2sf B)'
- Comparison of two paired-single values ('c.COND.ps'/'cabs.COND.ps',
- 'bc1any2t'/'bc1any2f').
+`int __builtin_mips_any_c_COND_ps (v2sf A, v2sf B)'
+`int __builtin_mips_all_c_COND_ps (v2sf A, v2sf B)'
+`int __builtin_mips_any_cabs_COND_ps (v2sf A, v2sf B)'
+`int __builtin_mips_all_cabs_COND_ps (v2sf A, v2sf B)'
+ Comparison of two paired-single values (`c.COND.ps'/`cabs.COND.ps',
+ `bc1any2t'/`bc1any2f').
- These functions compare A and B using 'c.COND.ps' or
- 'cabs.COND.ps'. The 'any' forms return true if either result is
- true and the 'all' forms return true if both results are true. For
- example:
+ These functions compare A and B using `c.COND.ps' or
+ `cabs.COND.ps'. The `any' forms return true if either result is
+ true and the `all' forms return true if both results are true.
+ For example:
v2sf a, b;
if (__builtin_mips_any_c_eq_ps (a, b))
@@ -35761,17 +36144,17 @@ case, COND can be any of the 16 floating-point conditions: 'f', 'un',
else
one_is_false ();
-'int __builtin_mips_any_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
-'int __builtin_mips_all_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
-'int __builtin_mips_any_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
-'int __builtin_mips_all_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
+`int __builtin_mips_any_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
+`int __builtin_mips_all_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
+`int __builtin_mips_any_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
+`int __builtin_mips_all_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)'
Comparison of four paired-single values
- ('c.COND.ps'/'cabs.COND.ps', 'bc1any4t'/'bc1any4f').
+ (`c.COND.ps'/`cabs.COND.ps', `bc1any4t'/`bc1any4f').
- These functions use 'c.COND.ps' or 'cabs.COND.ps' to compare A with
- B and to compare C with D. The 'any' forms return true if any of
- the four results are true and the 'all' forms return true if all
- four results are true. For example:
+ These functions use `c.COND.ps' or `cabs.COND.ps' to compare A
+ with B and to compare C with D. The `any' forms return true if
+ any of the four results are true and the `all' forms return true
+ if all four results are true. For example:
v2sf a, b, c, d;
if (__builtin_mips_any_c_eq_4s (a, b, c, d))
@@ -35792,19 +36175,19 @@ File: gcc.info, Node: Other MIPS Built-in Functions, Next: MSP430 Built-in Fun
GCC provides other MIPS-specific built-in functions:
-'void __builtin_mips_cache (int OP, const volatile void *ADDR)'
- Insert a 'cache' instruction with operands OP and ADDR. GCC
- defines the preprocessor macro '___GCC_HAVE_BUILTIN_MIPS_CACHE'
+`void __builtin_mips_cache (int OP, const volatile void *ADDR)'
+ Insert a `cache' instruction with operands OP and ADDR. GCC
+ defines the preprocessor macro `___GCC_HAVE_BUILTIN_MIPS_CACHE'
when this function is available.
-'unsigned int __builtin_mips_get_fcsr (void)'
-'void __builtin_mips_set_fcsr (unsigned int VALUE)'
+`unsigned int __builtin_mips_get_fcsr (void)'
+`void __builtin_mips_set_fcsr (unsigned int VALUE)'
Get and set the contents of the floating-point control and status
register (FPU control register 31). These functions are only
available in hard-float code but can be called in both MIPS16 and
non-MIPS16 contexts.
- '__builtin_mips_set_fcsr' can be used to change any bit of the
+ `__builtin_mips_set_fcsr' can be used to change any bit of the
register except the condition codes, which GCC assumes are
preserved.
@@ -35814,22 +36197,22 @@ File: gcc.info, Node: MSP430 Built-in Functions, Next: NDS32 Built-in Function
6.58.16 MSP430 Built-in Functions
---------------------------------
-GCC provides a couple of special builtin functions to aid in the writing
-of interrupt handlers in C.
+GCC provides a couple of special builtin functions to aid in the
+writing of interrupt handlers in C.
-'__bic_SR_register_on_exit (int MASK)'
+`__bic_SR_register_on_exit (int MASK)'
This clears the indicated bits in the saved copy of the status
register currently residing on the stack. This only works inside
- interrupt handlers and the changes to the status register will only
- take affect once the handler returns.
+ interrupt handlers and the changes to the status register will
+ only take affect once the handler returns.
-'__bis_SR_register_on_exit (int MASK)'
+`__bis_SR_register_on_exit (int MASK)'
This sets the indicated bits in the saved copy of the status
register currently residing on the stack. This only works inside
- interrupt handlers and the changes to the status register will only
- take affect once the handler returns.
+ interrupt handlers and the changes to the status register will
+ only take affect once the handler returns.
-'__delay_cycles (long long CYCLES)'
+`__delay_cycles (long long CYCLES)'
This inserts an instruction sequence that takes exactly CYCLES
cycles (between 0 and about 17E9) to complete. The inserted
sequence may use jumps, loops, or no-ops, and does not interfere
@@ -35880,33 +36263,34 @@ File: gcc.info, Node: picoChip Built-in Functions, Next: PowerPC Built-in Func
GCC provides an interface to selected machine instructions from the
picoChip instruction set.
-'int __builtin_sbc (int VALUE)'
+`int __builtin_sbc (int VALUE)'
Sign bit count. Return the number of consecutive bits in VALUE
- that have the same value as the sign bit. The result is the number
- of leading sign bits minus one, giving the number of redundant sign
- bits in VALUE.
+ that have the same value as the sign bit. The result is the
+ number of leading sign bits minus one, giving the number of
+ redundant sign bits in VALUE.
-'int __builtin_byteswap (int VALUE)'
- Byte swap. Return the result of swapping the upper and lower bytes
- of VALUE.
+`int __builtin_byteswap (int VALUE)'
+ Byte swap. Return the result of swapping the upper and lower
+ bytes of VALUE.
-'int __builtin_brev (int VALUE)'
+`int __builtin_brev (int VALUE)'
Bit reversal. Return the result of reversing the bits in VALUE.
Bit 15 is swapped with bit 0, bit 14 is swapped with bit 1, and so
on.
-'int __builtin_adds (int X, int Y)'
+`int __builtin_adds (int X, int Y)'
Saturating addition. Return the result of adding X and Y, storing
the value 32767 if the result overflows.
-'int __builtin_subs (int X, int Y)'
- Saturating subtraction. Return the result of subtracting Y from X,
- storing the value -32768 if the result overflows.
+`int __builtin_subs (int X, int Y)'
+ Saturating subtraction. Return the result of subtracting Y from
+ X, storing the value -32768 if the result overflows.
-'void __builtin_halt (void)'
+`void __builtin_halt (void)'
Halt. The processor stops execution. This built-in is useful for
implementing assertions.
+

File: gcc.info, Node: PowerPC Built-in Functions, Next: PowerPC AltiVec/VSX Built-in Functions, Prev: picoChip Built-in Functions, Up: Target Builtins
@@ -35924,25 +36308,25 @@ processors:
double __builtin_unpack_longdouble (long double, int);
long double __builtin_pack_longdouble (double, double);
- The 'vec_rsqrt', '__builtin_rsqrt', and '__builtin_rsqrtf' functions
+ The `vec_rsqrt', `__builtin_rsqrt', and `__builtin_rsqrtf' functions
generate multiple instructions to implement the reciprocal sqrt
functionality using reciprocal sqrt estimate instructions.
- The '__builtin_recipdiv', and '__builtin_recipdivf' functions generate
+ The `__builtin_recipdiv', and `__builtin_recipdivf' functions generate
multiple instructions to implement division using the reciprocal
estimate instructions.
- The '__builtin_ppc_get_timebase' and '__builtin_ppc_mftb' functions
+ The `__builtin_ppc_get_timebase' and `__builtin_ppc_mftb' functions
generate instructions to read the Time Base Register. The
-'__builtin_ppc_get_timebase' function may generate multiple instructions
-and always returns the 64 bits of the Time Base Register. The
-'__builtin_ppc_mftb' function always generates one instruction and
+`__builtin_ppc_get_timebase' function may generate multiple
+instructions and always returns the 64 bits of the Time Base Register.
+The `__builtin_ppc_mftb' function always generates one instruction and
returns the Time Base Register value as an unsigned long, throwing away
the most significant word on 32-bit environments.
The following built-in functions are available for the PowerPC family
-of processors, starting with ISA 2.06 or later ('-mcpu=power7' or
-'-mpopcntd'):
+of processors, starting with ISA 2.06 or later (`-mcpu=power7' or
+`-mpopcntd'):
long __builtin_bpermd (long, long);
int __builtin_divwe (int, int);
int __builtin_divweo (int, int);
@@ -35956,12 +36340,12 @@ of processors, starting with ISA 2.06 or later ('-mcpu=power7' or
unsigned int cbcdtd (unsigned int);
unsigned int addg6s (unsigned int, unsigned int);
- The '__builtin_divde', '__builtin_divdeo', '__builtin_divdeu',
-'__builtin_divdeou' functions require a 64-bit environment support ISA
+ The `__builtin_divde', `__builtin_divdeo', `__builtin_divdeu',
+`__builtin_divdeou' functions require a 64-bit environment support ISA
2.06 or later.
The following built-in functions are available for the PowerPC family
-of processors when hardware decimal floating point ('-mhard-dfp') is
+of processors when hardware decimal floating point (`-mhard-dfp') is
available:
_Decimal64 __builtin_dxex (_Decimal64);
_Decimal128 __builtin_dxexq (_Decimal128);
@@ -35993,7 +36377,7 @@ File: gcc.info, Node: PowerPC AltiVec/VSX Built-in Functions, Next: PowerPC Ha
GCC provides an interface for the PowerPC family of processors to access
the AltiVec operations described in Motorola's AltiVec Programming
Interface Manual. The interface is made available by including
-'<altivec.h>' and using '-maltivec' and '-mabi=altivec'. The interface
+`<altivec.h>' and using `-maltivec' and `-mabi=altivec'. The interface
supports the following vector types.
vector unsigned char
@@ -36010,15 +36394,15 @@ supports the following vector types.
vector bool int
vector float
- If '-mvsx' is used the following additional vector types are
+ If `-mvsx' is used the following additional vector types are
implemented.
vector unsigned long
vector signed long
vector double
- The long types are only implemented for 64-bit code generation, and the
-long type is only used in the floating point/integer conversion
+ The long types are only implemented for 64-bit code generation, and
+the long type is only used in the floating point/integer conversion
instructions.
GCC's implementation of the high-level language interface available
@@ -36031,18 +36415,18 @@ ways.
* A vector initializer requires no cast if the vector constant is of
the same type as the variable it is initializing.
- * If 'signed' or 'unsigned' is omitted, the signedness of the vector
+ * If `signed' or `unsigned' is omitted, the signedness of the vector
type is the default signedness of the base type. The default
varies depending on the operating system, so a portable program
should always specify the signedness.
- * Compiling with '-maltivec' adds keywords '__vector', 'vector',
- '__pixel', 'pixel', '__bool' and 'bool'. When compiling ISO C, the
- context-sensitive substitution of the keywords 'vector', 'pixel'
- and 'bool' is disabled. To use them, you must include
- '<altivec.h>' instead.
+ * Compiling with `-maltivec' adds keywords `__vector', `vector',
+ `__pixel', `pixel', `__bool' and `bool'. When compiling ISO C,
+ the context-sensitive substitution of the keywords `vector',
+ `pixel' and `bool' is disabled. To use them, you must include
+ `<altivec.h>' instead.
- * GCC allows using a 'typedef' name as the type specifier for a
+ * GCC allows using a `typedef' name as the type specifier for a
vector type.
* For C, overloaded functions are implemented with macros so the
@@ -36050,12 +36434,12 @@ ways.
vec_add ((vector signed int){1, 2, 3, 4}, foo);
- Since 'vec_add' is a macro, the vector constant in the example is
+ Since `vec_add' is a macro, the vector constant in the example is
treated as four separate arguments. Wrap the entire argument in
parentheses for this to work.
- _Note:_ Only the '<altivec.h>' interface is supported. Internally, GCC
-uses built-in functions to achieve the functionality in the
+ _Note:_ Only the `<altivec.h>' interface is supported. Internally,
+GCC uses built-in functions to achieve the functionality in the
aforementioned header file, but they are not supported and are subject
to change without notice.
@@ -36065,7 +36449,7 @@ a direct mapping between generic and specific operations, only the
generic names are shown here, although the specific operations can also
be used.
- Arguments that are documented as 'const int' require literal integral
+ Arguments that are documented as `const int' require literal integral
values within the range required for that operation.
vector signed char vec_abs (vector signed char);
@@ -38125,10 +38509,10 @@ additional functions are available:
vector unsigned char vec_xxsldi (vector unsigned char,
vector unsigned char, int);
- Note that the 'vec_ld' and 'vec_st' built-in functions always generate
-the AltiVec 'LVX' and 'STVX' instructions even if the VSX instruction
-set is available. The 'vec_vsx_ld' and 'vec_vsx_st' built-in functions
-always generate the VSX 'LXVD2X', 'LXVW4X', 'STXVD2X', and 'STXVW4X'
+ Note that the `vec_ld' and `vec_st' built-in functions always generate
+the AltiVec `LVX' and `STVX' instructions even if the VSX instruction
+set is available. The `vec_vsx_ld' and `vec_vsx_st' built-in functions
+always generate the VSX `LXVD2X', `LXVW4X', `STXVD2X', and `STXVW4X'
instructions.
If the ISA 2.07 additions to the vector/scalar (power8-vector)
@@ -38445,11 +38829,11 @@ VECTOR UNSIGNED LONG LONG.
If the ISA 2.07 additions to the vector/scalar (power8-vector)
instruction set is available, the following additional functions are
available for 64-bit targets. New vector types (VECTOR __INT128_T and
-VECTOR __UINT128_T) are available to hold the __INT128_T and __UINT128_T
-types to use these builtins.
+VECTOR __UINT128_T) are available to hold the __INT128_T and
+__UINT128_T types to use these builtins.
- The normal vector extract, and set operations work on VECTOR __INT128_T
-and VECTOR __UINT128_T types, but the index value must be 0.
+ The normal vector extract, and set operations work on VECTOR
+__INT128_T and VECTOR __UINT128_T types, but the index value must be 0.
vector __int128_t vec_vaddcuq (vector __int128_t, vector __int128_t);
vector __uint128_t vec_vaddcuq (vector __uint128_t, vector __uint128_t);
@@ -38494,8 +38878,8 @@ and VECTOR __UINT128_T types, but the index value must be 0.
int __builtin_bcdsub_gt (vector __int128_t, vector__int128_t);
int __builtin_bcdsub_ov (vector __int128_t, vector__int128_t);
- If the cryptographic instructions are enabled ('-mcrypto' or
-'-mcpu=power8'), the following builtins are enabled.
+ If the cryptographic instructions are enabled (`-mcrypto' or
+`-mcpu=power8'), the following builtins are enabled.
vector unsigned long long __builtin_crypto_vsbox (vector unsigned long long);
@@ -38548,9 +38932,9 @@ and VECTOR __UINT128_T types, but the index value must be 0.
int, int);
The second argument to the __BUILTIN_CRYPTO_VSHASIGMAD and
-__BUILTIN_CRYPTO_VSHASIGMAW builtin functions must be a constant integer
-that is 0 or 1. The third argument to these builtin functions must be a
-constant integer in the range of 0 to 15.
+__BUILTIN_CRYPTO_VSHASIGMAW builtin functions must be a constant
+integer that is 0 or 1. The third argument to these builtin functions
+must be a constant integer in the range of 0 to 15.

File: gcc.info, Node: PowerPC Hardware Transactional Memory Built-in Functions, Next: RX Built-in Functions, Prev: PowerPC AltiVec/VSX Built-in Functions, Up: Target Builtins
@@ -38568,14 +38952,20 @@ between PowerPC and S/390.
6.58.21.1 PowerPC HTM Low Level Built-in Functions
..................................................
-The following low level built-in functions are available with '-mhtm' or
-'-mcpu=CPU' where CPU is 'power8' or later. They all generate the
+The following low level built-in functions are available with `-mhtm'
+or `-mcpu=CPU' where CPU is `power8' or later. They all generate the
machine instruction that is part of the name.
- The HTM built-ins return true or false depending on their success and
-their arguments match exactly the type and order of the associated
-hardware instruction's operands. Refer to the ISA manual for a
-description of each instruction's operands.
+ The HTM builtins (with the exception of `__builtin_tbegin') return the
+full 4-bit condition register value set by their associated hardware
+instruction. The header file `htmintrin.h' defines some macros that can
+be used to decipher the return value. The `__builtin_tbegin' builtin
+returns a simple true or false value depending on whether a transaction
+was successfully started or not. The arguments of the builtins match
+exactly the type and order of the associated hardware instruction's
+operands, except for the `__builtin_tcheck' builtin, which does not
+take any input arguments. Refer to the ISA manual for a description of
+each instruction's operands.
unsigned int __builtin_tbegin (unsigned int)
unsigned int __builtin_tend (unsigned int)
@@ -38586,7 +38976,7 @@ description of each instruction's operands.
unsigned int __builtin_tabortwc (unsigned int, unsigned int, unsigned int)
unsigned int __builtin_tabortwci (unsigned int, unsigned int, int)
- unsigned int __builtin_tcheck (unsigned int)
+ unsigned int __builtin_tcheck (void)
unsigned int __builtin_treclaim (unsigned int)
unsigned int __builtin_trechkpt (void)
unsigned int __builtin_tsr (unsigned int)
@@ -38598,8 +38988,8 @@ some common extended mnemonics of the HTM instructions:
unsigned int __builtin_tresume (void)
unsigned int __builtin_tsuspend (void)
- The following set of built-in functions are available to gain access to
-the HTM specific special purpose registers.
+ The following set of built-in functions are available to gain access
+to the HTM specific special purpose registers.
unsigned long __builtin_get_texasr (void)
unsigned long __builtin_get_texasru (void)
@@ -38645,7 +39035,7 @@ the HTM specific special purpose registers.
One final built-in function has been added that returns the value of
the 2-bit Transaction State field of the Machine Status Register (MSR)
-as stored in 'CR0'.
+as stored in `CR0'.
unsigned long __builtin_ttest (void)
@@ -38673,10 +39063,10 @@ using the following code example:
.................................................
The following high level HTM interface is made available by including
-'<htmxlintrin.h>' and using '-mhtm' or '-mcpu=CPU' where CPU is 'power8'
-or later. This interface is common between PowerPC and S/390, allowing
-users to write one HTM source implementation that can be compiled and
-executed on either system.
+`<htmxlintrin.h>' and using `-mhtm' or `-mcpu=CPU' where CPU is
+`power8' or later. This interface is common between PowerPC and S/390,
+allowing users to write one HTM source implementation that can be
+compiled and executed on either system.
long __TM_simple_begin (void)
long __TM_begin (void* const TM_buff)
@@ -38708,7 +39098,7 @@ work on either PowerPC or S/390:
while (1)
{
- if (__TM_begin (TM_buff))
+ if (__TM_begin (TM_buff) == _HTM_TBEGIN_STARTED)
{
/* Transaction State Initiated. */
if (is_locked (lock))
@@ -38743,92 +39133,92 @@ the C programming language via the use of built-in functions. The
following functions are supported:
-- Built-in Function: void __builtin_rx_brk (void)
- Generates the 'brk' machine instruction.
+ Generates the `brk' machine instruction.
-- Built-in Function: void __builtin_rx_clrpsw (int)
- Generates the 'clrpsw' machine instruction to clear the specified
+ Generates the `clrpsw' machine instruction to clear the specified
bit in the processor status word.
-- Built-in Function: void __builtin_rx_int (int)
- Generates the 'int' machine instruction to generate an interrupt
+ Generates the `int' machine instruction to generate an interrupt
with the specified value.
-- Built-in Function: void __builtin_rx_machi (int, int)
- Generates the 'machi' machine instruction to add the result of
+ Generates the `machi' machine instruction to add the result of
multiplying the top 16 bits of the two arguments into the
accumulator.
-- Built-in Function: void __builtin_rx_maclo (int, int)
- Generates the 'maclo' machine instruction to add the result of
+ Generates the `maclo' machine instruction to add the result of
multiplying the bottom 16 bits of the two arguments into the
accumulator.
-- Built-in Function: void __builtin_rx_mulhi (int, int)
- Generates the 'mulhi' machine instruction to place the result of
+ Generates the `mulhi' machine instruction to place the result of
multiplying the top 16 bits of the two arguments into the
accumulator.
-- Built-in Function: void __builtin_rx_mullo (int, int)
- Generates the 'mullo' machine instruction to place the result of
+ Generates the `mullo' machine instruction to place the result of
multiplying the bottom 16 bits of the two arguments into the
accumulator.
-- Built-in Function: int __builtin_rx_mvfachi (void)
- Generates the 'mvfachi' machine instruction to read the top 32 bits
- of the accumulator.
+ Generates the `mvfachi' machine instruction to read the top 32
+ bits of the accumulator.
-- Built-in Function: int __builtin_rx_mvfacmi (void)
- Generates the 'mvfacmi' machine instruction to read the middle 32
+ Generates the `mvfacmi' machine instruction to read the middle 32
bits of the accumulator.
-- Built-in Function: int __builtin_rx_mvfc (int)
- Generates the 'mvfc' machine instruction which reads the control
+ Generates the `mvfc' machine instruction which reads the control
register specified in its argument and returns its value.
-- Built-in Function: void __builtin_rx_mvtachi (int)
- Generates the 'mvtachi' machine instruction to set the top 32 bits
+ Generates the `mvtachi' machine instruction to set the top 32 bits
of the accumulator.
-- Built-in Function: void __builtin_rx_mvtaclo (int)
- Generates the 'mvtaclo' machine instruction to set the bottom 32
+ Generates the `mvtaclo' machine instruction to set the bottom 32
bits of the accumulator.
-- Built-in Function: void __builtin_rx_mvtc (int reg, int val)
- Generates the 'mvtc' machine instruction which sets control
- register number 'reg' to 'val'.
+ Generates the `mvtc' machine instruction which sets control
+ register number `reg' to `val'.
-- Built-in Function: void __builtin_rx_mvtipl (int)
- Generates the 'mvtipl' machine instruction set the interrupt
+ Generates the `mvtipl' machine instruction set the interrupt
priority level.
-- Built-in Function: void __builtin_rx_racw (int)
- Generates the 'racw' machine instruction to round the accumulator
+ Generates the `racw' machine instruction to round the accumulator
according to the specified mode.
-- Built-in Function: int __builtin_rx_revw (int)
- Generates the 'revw' machine instruction which swaps the bytes in
+ Generates the `revw' machine instruction which swaps the bytes in
the argument so that bits 0-7 now occupy bits 8-15 and vice versa,
and also bits 16-23 occupy bits 24-31 and vice versa.
-- Built-in Function: void __builtin_rx_rmpa (void)
- Generates the 'rmpa' machine instruction which initiates a repeated
- multiply and accumulate sequence.
+ Generates the `rmpa' machine instruction which initiates a
+ repeated multiply and accumulate sequence.
-- Built-in Function: void __builtin_rx_round (float)
- Generates the 'round' machine instruction which returns the
+ Generates the `round' machine instruction which returns the
floating-point argument rounded according to the current rounding
mode set in the floating-point status word register.
-- Built-in Function: int __builtin_rx_sat (int)
- Generates the 'sat' machine instruction which returns the saturated
- value of the argument.
+ Generates the `sat' machine instruction which returns the
+ saturated value of the argument.
-- Built-in Function: void __builtin_rx_setpsw (int)
- Generates the 'setpsw' machine instruction to set the specified bit
- in the processor status word.
+ Generates the `setpsw' machine instruction to set the specified
+ bit in the processor status word.
-- Built-in Function: void __builtin_rx_wait (void)
- Generates the 'wait' machine instruction.
+ Generates the `wait' machine instruction.

File: gcc.info, Node: S/390 System z Built-in Functions, Next: SH Built-in Functions, Prev: RX Built-in Functions, Up: Target Builtins
@@ -38837,21 +39227,21 @@ File: gcc.info, Node: S/390 System z Built-in Functions, Next: SH Built-in Fun
-----------------------------------------
-- Built-in Function: int __builtin_tbegin (void*)
- Generates the 'tbegin' machine instruction starting a
+ Generates the `tbegin' machine instruction starting a
non-constraint hardware transaction. If the parameter is non-NULL
the memory area is used to store the transaction diagnostic buffer
- and will be passed as first operand to 'tbegin'. This buffer can
- be defined using the 'struct __htm_tdb' C struct defined in
- 'htmintrin.h' and must reside on a double-word boundary. The
- second tbegin operand is set to '0xff0c'. This enables
+ and will be passed as first operand to `tbegin'. This buffer can
+ be defined using the `struct __htm_tdb' C struct defined in
+ `htmintrin.h' and must reside on a double-word boundary. The
+ second tbegin operand is set to `0xff0c'. This enables
save/restore of all GPRs and disables aborts for FPR and AR
manipulations inside the transaction body. The condition code set
by the tbegin instruction is returned as integer value. The tbegin
instruction by definition overwrites the content of all FPRs. The
compiler will generate code which saves and restores the FPRs. For
- soft-float code it is recommended to used the '*_nofloat' variant.
- In order to prevent a TDB from being written it is required to pass
- an constant zero value as parameter. Passing the zero value
+ soft-float code it is recommended to used the `*_nofloat' variant.
+ In order to prevent a TDB from being written it is required to
+ pass an constant zero value as parameter. Passing the zero value
through a variable is not sufficient. Although modifications of
access registers inside the transaction will not trigger an
transaction abort it is not supported to actually modify them.
@@ -38859,79 +39249,82 @@ File: gcc.info, Node: S/390 System z Built-in Functions, Next: SH Built-in Fun
They will have undefined state when reaching the abort code.
Macros for the possible return codes of tbegin are defined in the
-'htmintrin.h' header file:
+`htmintrin.h' header file:
-'_HTM_TBEGIN_STARTED'
- 'tbegin' has been executed as part of normal processing. The
+`_HTM_TBEGIN_STARTED'
+ `tbegin' has been executed as part of normal processing. The
transaction body is supposed to be executed.
-'_HTM_TBEGIN_INDETERMINATE'
+
+`_HTM_TBEGIN_INDETERMINATE'
The transaction was aborted due to an indeterminate condition which
might be persistent.
-'_HTM_TBEGIN_TRANSIENT'
+
+`_HTM_TBEGIN_TRANSIENT'
The transaction aborted due to a transient failure. The
transaction should be re-executed in that case.
-'_HTM_TBEGIN_PERSISTENT'
+
+`_HTM_TBEGIN_PERSISTENT'
The transaction aborted due to a persistent failure. Re-execution
under same circumstances will not be productive.
-- Macro: _HTM_FIRST_USER_ABORT_CODE
- The '_HTM_FIRST_USER_ABORT_CODE' defined in 'htmintrin.h' specifies
- the first abort code which can be used for '__builtin_tabort'.
- Values below this threshold are reserved for machine use.
+ The `_HTM_FIRST_USER_ABORT_CODE' defined in `htmintrin.h'
+ specifies the first abort code which can be used for
+ `__builtin_tabort'. Values below this threshold are reserved for
+ machine use.
-- Data type: struct __htm_tdb
- The 'struct __htm_tdb' defined in 'htmintrin.h' describes the
+ The `struct __htm_tdb' defined in `htmintrin.h' describes the
structure of the transaction diagnostic block as specified in the
Principles of Operation manual chapter 5-91.
-- Built-in Function: int __builtin_tbegin_nofloat (void*)
- Same as '__builtin_tbegin' but without FPR saves and restores.
+ Same as `__builtin_tbegin' but without FPR saves and restores.
Using this variant in code making use of FPRs will leave the FPRs
in undefined state when entering the transaction abort handler
code.
-- Built-in Function: int __builtin_tbegin_retry (void*, int)
- In addition to '__builtin_tbegin' a loop for transient failures is
+ In addition to `__builtin_tbegin' a loop for transient failures is
generated. If tbegin returns a condition code of 2 the transaction
will be retried as often as specified in the second argument. The
perform processor assist instruction is used to tell the CPU about
the number of fails so far.
-- Built-in Function: int __builtin_tbegin_retry_nofloat (void*, int)
- Same as '__builtin_tbegin_retry' but without FPR saves and
+ Same as `__builtin_tbegin_retry' but without FPR saves and
restores. Using this variant in code making use of FPRs will leave
the FPRs in undefined state when entering the transaction abort
handler code.
-- Built-in Function: void __builtin_tbeginc (void)
- Generates the 'tbeginc' machine instruction starting a constraint
- hardware transaction. The second operand is set to '0xff08'.
+ Generates the `tbeginc' machine instruction starting a constraint
+ hardware transaction. The second operand is set to `0xff08'.
-- Built-in Function: int __builtin_tend (void)
- Generates the 'tend' machine instruction finishing a transaction
+ Generates the `tend' machine instruction finishing a transaction
and making the changes visible to other threads. The condition
code generated by tend is returned as integer value.
-- Built-in Function: void __builtin_tabort (int)
- Generates the 'tabort' machine instruction with the specified abort
- code. Abort codes from 0 through 255 are reserved and will result
- in an error message.
+ Generates the `tabort' machine instruction with the specified
+ abort code. Abort codes from 0 through 255 are reserved and will
+ result in an error message.
-- Built-in Function: void __builtin_tx_assist (int)
- Generates the 'ppa rX,rY,1' machine instruction. Where the integer
- parameter is loaded into rX and a value of zero is loaded into rY.
- The integer parameter specifies the number of times the transaction
- repeatedly aborted.
+ Generates the `ppa rX,rY,1' machine instruction. Where the
+ integer parameter is loaded into rX and a value of zero is loaded
+ into rY. The integer parameter specifies the number of times the
+ transaction repeatedly aborted.
-- Built-in Function: int __builtin_tx_nesting_depth (void)
- Generates the 'etnd' machine instruction. The current nesting
+ Generates the `etnd' machine instruction. The current nesting
depth is returned as integer value. For a nesting depth of 0 the
code is not executed as part of an transaction.
-- Built-in Function: void __builtin_non_tx_store (uint64_t *,
uint64_t)
-
- Generates the 'ntstg' machine instruction. The second argument is
+ Generates the `ntstg' machine instruction. The second argument is
written to the first arguments location. The store operation will
not be rolled-back in case of an transaction abort.
@@ -38945,18 +39338,19 @@ The following built-in functions are supported on the SH1, SH2, SH3 and
SH4 families of processors:
-- Built-in Function: void __builtin_set_thread_pointer (void *PTR)
- Sets the 'GBR' register to the specified value PTR. This is
+ Sets the `GBR' register to the specified value PTR. This is
usually used by system code that manages threads and execution
contexts. The compiler normally does not generate code that
- modifies the contents of 'GBR' and thus the value is preserved
- across function calls. Changing the 'GBR' value in user code must
- be done with caution, since the compiler might use 'GBR' in order
+ modifies the contents of `GBR' and thus the value is preserved
+ across function calls. Changing the `GBR' value in user code must
+ be done with caution, since the compiler might use `GBR' in order
to access thread local variables.
+
-- Built-in Function: void * __builtin_thread_pointer (void)
- Returns the value that is currently set in the 'GBR' register.
+ Returns the value that is currently set in the `GBR' register.
Memory loads and stores that use the thread pointer as a base
- address are turned into 'GBR' based displacement loads and stores,
+ address are turned into `GBR' based displacement loads and stores,
if possible. For example:
struct my_tcb
{
@@ -38965,16 +39359,15 @@ SH4 families of processors:
int get_tcb_value (void)
{
- // Generate 'mov.l @(8,gbr),r0' instruction
+ // Generate `mov.l @(8,gbr),r0' instruction
return ((my_tcb*)__builtin_thread_pointer ())->c;
}
-
-- Built-in Function: unsigned int __builtin_sh_get_fpscr (void)
- Returns the value that is currently set in the 'FPSCR' register.
+ Returns the value that is currently set in the `FPSCR' register.
-- Built-in Function: void __builtin_sh_set_fpscr (unsigned int VAL)
- Sets the 'FPSCR' register to the specified value VAL, while
+ Sets the `FPSCR' register to the specified value VAL, while
preserving the current values of the FR, SZ and PR bits.

@@ -38985,8 +39378,9 @@ File: gcc.info, Node: SPARC VIS Built-in Functions, Next: SPU Built-in Functio
GCC supports SIMD operations on the SPARC using both the generic vector
extensions (*note Vector Extensions::) as well as built-in functions for
-the SPARC Visual Instruction Set (VIS). When you use the '-mvis' switch,
-the VIS extension is exposed as the following built-in functions:
+the SPARC Visual Instruction Set (VIS). When you use the `-mvis'
+switch, the VIS extension is exposed as the following built-in
+functions:
typedef int v1si __attribute__ ((vector_size (4)));
typedef int v2si __attribute__ ((vector_size (8)));
@@ -39051,7 +39445,7 @@ the VIS extension is exposed as the following built-in functions:
long __builtin_vis_array16 (long, long);
long __builtin_vis_array32 (long, long);
- When you use the '-mvis2' switch, the VIS version 2.0 built-in
+ When you use the `-mvis2' switch, the VIS version 2.0 built-in
functions also become available:
long __builtin_vis_bmask (long, long);
@@ -39067,7 +39461,7 @@ functions also become available:
long __builtin_vis_edge32n (void *, void *);
long __builtin_vis_edge32ln (void *, void *);
- When you use the '-mvis3' switch, the VIS version 3.0 built-in
+ When you use the `-mvis3' switch, the VIS version 3.0 built-in
functions also become available:
void __builtin_vis_cmask8 (long);
@@ -39125,8 +39519,8 @@ File: gcc.info, Node: SPU Built-in Functions, Next: TI C6X Built-in Functions,
GCC provides extensions for the SPU processor as described in the
Sony/Toshiba/IBM SPU Language Extensions Specification, which can be
-found at <http://cell.scei.co.jp/> or
-<http://www.ibm.com/developerworks/power/cell/>. GCC's implementation
+found at `http://cell.scei.co.jp/' or
+`http://www.ibm.com/developerworks/power/cell/'. GCC's implementation
differs in several ways.
* The optional extension of specifying vector constants in
@@ -39135,15 +39529,15 @@ differs in several ways.
* A vector initializer requires no cast if the vector constant is of
the same type as the variable it is initializing.
- * If 'signed' or 'unsigned' is omitted, the signedness of the vector
+ * If `signed' or `unsigned' is omitted, the signedness of the vector
type is the default signedness of the base type. The default
varies depending on the operating system, so a portable program
should always specify the signedness.
- * By default, the keyword '__vector' is added. The macro 'vector' is
- defined in '<spu_intrinsics.h>' and can be undefined.
+ * By default, the keyword `__vector' is added. The macro `vector' is
+ defined in `<spu_intrinsics.h>' and can be undefined.
- * GCC allows using a 'typedef' name as the type specifier for a
+ * GCC allows using a `typedef' name as the type specifier for a
vector type.
* For C, overloaded functions are implemented with macros so the
@@ -39151,14 +39545,15 @@ differs in several ways.
spu_add ((vector signed int){1, 2, 3, 4}, foo);
- Since 'spu_add' is a macro, the vector constant in the example is
+ Since `spu_add' is a macro, the vector constant in the example is
treated as four separate arguments. Wrap the entire argument in
parentheses for this to work.
- * The extended version of '__builtin_expect' is not supported.
+ * The extended version of `__builtin_expect' is not supported.
+
_Note:_ Only the interface described in the aforementioned
-specification is supported. Internally, GCC uses built-in functions to
+specification is supported. Internally, GCC uses built-in functions to
implement the required functionality, but these are not supported and
are subject to change without notice.
@@ -39170,7 +39565,7 @@ File: gcc.info, Node: TI C6X Built-in Functions, Next: TILE-Gx Built-in Functi
GCC provides intrinsics to access certain instructions of the TI C6X
processors. These intrinsics, listed below, are available after
-inclusion of the 'c6x_intrinsics.h' header file. They map directly to
+inclusion of the `c6x_intrinsics.h' header file. They map directly to
C6X instructions.
@@ -39201,7 +39596,6 @@ C6X instructions.
int _abs (int)
int _abs2 (int)
-

File: gcc.info, Node: TILE-Gx Built-in Functions, Next: TILEPro Built-in Functions, Prev: TI C6X Built-in Functions, Up: Target Builtins
@@ -39214,7 +39608,6 @@ processor. The intrinsics are of the form:
unsigned long long __insn_OP (...)
-
Where OP is the name of the instruction. Refer to the ISA manual for
the complete list of instructions.
@@ -39231,9 +39624,9 @@ The intrinsics are:
void __tile_idn_send (unsigned long long)
void __tile_udn_send (unsigned long long)
-
- The intrinsic 'void __tile_network_barrier (void)' is used to guarantee
-that no network operations before it are reordered with those after it.
+ The intrinsic `void __tile_network_barrier (void)' is used to
+guarantee that no network operations before it are reordered with those
+after it.

File: gcc.info, Node: TILEPro Built-in Functions, Next: x86 Built-in Functions, Prev: TILE-Gx Built-in Functions, Up: Target Builtins
@@ -39247,7 +39640,6 @@ processor. The intrinsics are of the form:
unsigned __insn_OP (...)
-
where OP is the name of the instruction. Refer to the ISA manual for
the complete list of instructions.
@@ -39266,9 +39658,9 @@ The intrinsics are:
void __tile_sn_send (unsigned)
void __tile_udn_send (unsigned)
-
- The intrinsic 'void __tile_network_barrier (void)' is used to guarantee
-that no network operations before it are reordered with those after it.
+ The intrinsic `void __tile_network_barrier (void)' is used to
+guarantee that no network operations before it are reordered with those
+after it.

File: gcc.info, Node: x86 Built-in Functions, Next: x86 transactional memory intrinsics, Prev: TILEPro Built-in Functions, Up: Target Builtins
@@ -39279,33 +39671,33 @@ File: gcc.info, Node: x86 Built-in Functions, Next: x86 transactional memory i
These built-in functions are available for the x86-32 and x86-64 family
of computers, depending on the command-line switches used.
- If you specify command-line switches such as '-msse', the compiler
+ If you specify command-line switches such as `-msse', the compiler
could use the extended instruction sets even if the built-ins are not
used explicitly in the program. For this reason, applications that
perform run-time CPU detection must compile separate files for each
-supported architecture, using the appropriate flags. In particular, the
-file containing the CPU detection code should be compiled without these
-options.
+supported architecture, using the appropriate flags. In particular,
+the file containing the CPU detection code should be compiled without
+these options.
The following machine modes are available for use with MMX built-in
-functions (*note Vector Extensions::): 'V2SI' for a vector of two 32-bit
-integers, 'V4HI' for a vector of four 16-bit integers, and 'V8QI' for a
-vector of eight 8-bit integers. Some of the built-in functions operate
-on MMX registers as a whole 64-bit entity, these use 'V1DI' as their
-mode.
+functions (*note Vector Extensions::): `V2SI' for a vector of two
+32-bit integers, `V4HI' for a vector of four 16-bit integers, and
+`V8QI' for a vector of eight 8-bit integers. Some of the built-in
+functions operate on MMX registers as a whole 64-bit entity, these use
+`V1DI' as their mode.
- If 3DNow! extensions are enabled, 'V2SF' is used as a mode for a vector
+ If 3DNow! extensions are enabled, `V2SF' is used as a mode for a vector
of two 32-bit floating-point values.
- If SSE extensions are enabled, 'V4SF' is used for a vector of four
+ If SSE extensions are enabled, `V4SF' is used for a vector of four
32-bit floating-point values. Some instructions use a vector of four
-32-bit integers, these use 'V4SI'. Finally, some instructions operate
+32-bit integers, these use `V4SI'. Finally, some instructions operate
on an entire vector register, interpreting it as a 128-bit integer,
-these use mode 'TI'.
+these use mode `TI'.
In 64-bit mode, the x86-64 family of processors uses additional
-built-in functions for efficient use of 'TF' ('__float128') 128-bit
-floating point and 'TC' 128-bit complex floating-point values.
+built-in functions for efficient use of `TF' (`__float128') 128-bit
+floating point and `TC' 128-bit complex floating-point values.
The following floating-point built-in functions are available in 64-bit
mode. All of them implement the function that is part of the name.
@@ -39315,19 +39707,19 @@ mode. All of them implement the function that is part of the name.
The following built-in function is always available.
-'void __builtin_ia32_pause (void)'
- Generates the 'pause' machine instruction with a compiler memory
+`void __builtin_ia32_pause (void)'
+ Generates the `pause' machine instruction with a compiler memory
barrier.
The following floating-point built-in functions are made available in
the 64-bit mode.
-'__float128 __builtin_infq (void)'
- Similar to '__builtin_inf', except the return type is '__float128'.
+`__float128 __builtin_infq (void)'
+ Similar to `__builtin_inf', except the return type is `__float128'.
-'__float128 __builtin_huge_valq (void)'
- Similar to '__builtin_huge_val', except the return type is
- '__float128'.
+`__float128 __builtin_huge_valq (void)'
+ Similar to `__builtin_huge_val', except the return type is
+ `__float128'.
The following built-in functions are always available and can be used
to check the target platform type.
@@ -39336,14 +39728,14 @@ to check the target platform type.
This function runs the CPU detection code to check the type of CPU
and the features supported. This built-in function needs to be
invoked along with the built-in functions to check CPU type and
- features, '__builtin_cpu_is' and '__builtin_cpu_supports', only
+ features, `__builtin_cpu_is' and `__builtin_cpu_supports', only
when used in a function that is executed before any constructors
are called. The CPU detection code is automatically executed in a
very high priority constructor.
- For example, this function has to be used in 'ifunc' resolvers that
- check for CPU type using the built-in functions '__builtin_cpu_is'
- and '__builtin_cpu_supports', or in constructors on targets that
+ For example, this function has to be used in `ifunc' resolvers that
+ check for CPU type using the built-in functions `__builtin_cpu_is'
+ and `__builtin_cpu_supports', or in constructors on targets that
don't support constructor priority.
static void (*resolve_memcpy (void)) (void)
@@ -39360,66 +39752,67 @@ to check the target platform type.
void *memcpy (void *, const void *, size_t)
__attribute__ ((ifunc ("resolve_memcpy")));
+
-- Built-in Function: int __builtin_cpu_is (const char *CPUNAME)
This function returns a positive integer if the run-time CPU is of
- type CPUNAME and returns '0' otherwise. The following CPU names
+ type CPUNAME and returns `0' otherwise. The following CPU names
can be detected:
- 'intel'
+ `intel'
Intel CPU.
- 'atom'
+ `atom'
Intel Atom CPU.
- 'core2'
+ `core2'
Intel Core 2 CPU.
- 'corei7'
+ `corei7'
Intel Core i7 CPU.
- 'nehalem'
+ `nehalem'
Intel Core i7 Nehalem CPU.
- 'westmere'
+ `westmere'
Intel Core i7 Westmere CPU.
- 'sandybridge'
+ `sandybridge'
Intel Core i7 Sandy Bridge CPU.
- 'amd'
+ `amd'
AMD CPU.
- 'amdfam10h'
+ `amdfam10h'
AMD Family 10h CPU.
- 'barcelona'
+ `barcelona'
AMD Family 10h Barcelona CPU.
- 'shanghai'
+ `shanghai'
AMD Family 10h Shanghai CPU.
- 'istanbul'
+ `istanbul'
AMD Family 10h Istanbul CPU.
- 'btver1'
+ `btver1'
AMD Family 14h CPU.
- 'amdfam15h'
+ `amdfam15h'
AMD Family 15h CPU.
- 'bdver1'
+ `bdver1'
AMD Family 15h Bulldozer version 1.
- 'bdver2'
+ `bdver2'
AMD Family 15h Bulldozer version 2.
- 'bdver3'
+ `bdver3'
AMD Family 15h Bulldozer version 3.
- 'bdver4'
+ `bdver4'
AMD Family 15h Bulldozer version 4.
- 'btver2'
+ `btver2'
AMD Family 16h CPU.
Here is an example:
@@ -39434,32 +39827,43 @@ to check the target platform type.
-- Built-in Function: int __builtin_cpu_supports (const char *FEATURE)
This function returns a positive integer if the run-time CPU
- supports FEATURE and returns '0' otherwise. The following features
+ supports FEATURE and returns `0' otherwise. The following features
can be detected:
- 'cmov'
+ `cmov'
CMOV instruction.
- 'mmx'
+
+ `mmx'
MMX instructions.
- 'popcnt'
+
+ `popcnt'
POPCNT instruction.
- 'sse'
+
+ `sse'
SSE instructions.
- 'sse2'
+
+ `sse2'
SSE2 instructions.
- 'sse3'
+
+ `sse3'
SSE3 instructions.
- 'ssse3'
+
+ `ssse3'
SSSE3 instructions.
- 'sse4.1'
+
+ `sse4.1'
SSE4.1 instructions.
- 'sse4.2'
+
+ `sse4.2'
SSE4.2 instructions.
- 'avx'
+
+ `avx'
AVX instructions.
- 'avx2'
+
+ `avx2'
AVX2 instructions.
- 'avx512f'
+
+ `avx512f'
AVX512F instructions.
Here is an example:
@@ -39472,8 +39876,8 @@ to check the target platform type.
count = generic_countbits (n); //generic implementation.
}
- The following built-in functions are made available by '-mmmx'. All of
-them generate the machine instruction that is part of the name.
+ The following built-in functions are made available by `-mmmx'. All
+of them generate the machine instruction that is part of the name.
v8qi __builtin_ia32_paddb (v8qi, v8qi)
v4hi __builtin_ia32_paddw (v4hi, v4hi)
@@ -39528,10 +39932,9 @@ them generate the machine instruction that is part of the name.
v4hi __builtin_ia32_psrawi (v4hi, int)
v2si __builtin_ia32_psradi (v2si, int)
-
The following built-in functions are made available either with
-'-msse', or with a combination of '-m3dnow' and '-march=athlon'. All of
-them generate the machine instruction that is part of the name.
+`-msse', or with a combination of `-m3dnow' and `-march=athlon'. All
+of them generate the machine instruction that is part of the name.
v4hi __builtin_ia32_pmulhuw (v4hi, v4hi)
v8qi __builtin_ia32_pavgb (v8qi, v8qi)
@@ -39546,7 +39949,7 @@ them generate the machine instruction that is part of the name.
void __builtin_ia32_movntq (di *, di)
void __builtin_ia32_sfence (void)
- The following built-in functions are available when '-msse' is used.
+ The following built-in functions are available when `-msse' is used.
All of them generate the machine instruction that is part of the name.
int __builtin_ia32_comieq (v4sf, v4sf)
@@ -39618,24 +40021,30 @@ All of them generate the machine instruction that is part of the name.
void __builtin_ia32_movntps (float *, v4sf)
int __builtin_ia32_movmskps (v4sf)
- The following built-in functions are available when '-msse' is used.
-
-'v4sf __builtin_ia32_loadups (float *)'
- Generates the 'movups' machine instruction as a load from memory.
-'void __builtin_ia32_storeups (float *, v4sf)'
- Generates the 'movups' machine instruction as a store to memory.
-'v4sf __builtin_ia32_loadss (float *)'
- Generates the 'movss' machine instruction as a load from memory.
-'v4sf __builtin_ia32_loadhps (v4sf, const v2sf *)'
- Generates the 'movhps' machine instruction as a load from memory.
-'v4sf __builtin_ia32_loadlps (v4sf, const v2sf *)'
- Generates the 'movlps' machine instruction as a load from memory
-'void __builtin_ia32_storehps (v2sf *, v4sf)'
- Generates the 'movhps' machine instruction as a store to memory.
-'void __builtin_ia32_storelps (v2sf *, v4sf)'
- Generates the 'movlps' machine instruction as a store to memory.
-
- The following built-in functions are available when '-msse2' is used.
+ The following built-in functions are available when `-msse' is used.
+
+`v4sf __builtin_ia32_loadups (float *)'
+ Generates the `movups' machine instruction as a load from memory.
+
+`void __builtin_ia32_storeups (float *, v4sf)'
+ Generates the `movups' machine instruction as a store to memory.
+
+`v4sf __builtin_ia32_loadss (float *)'
+ Generates the `movss' machine instruction as a load from memory.
+
+`v4sf __builtin_ia32_loadhps (v4sf, const v2sf *)'
+ Generates the `movhps' machine instruction as a load from memory.
+
+`v4sf __builtin_ia32_loadlps (v4sf, const v2sf *)'
+ Generates the `movlps' machine instruction as a load from memory
+
+`void __builtin_ia32_storehps (v2sf *, v4sf)'
+ Generates the `movhps' machine instruction as a store to memory.
+
+`void __builtin_ia32_storelps (v2sf *, v4sf)'
+ Generates the `movlps' machine instruction as a store to memory.
+
+ The following built-in functions are available when `-msse2' is used.
All of them generate the machine instruction that is part of the name.
int __builtin_ia32_comisdeq (v2df, v2df)
@@ -39794,7 +40203,7 @@ All of them generate the machine instruction that is part of the name.
v4si __builtin_ia32_pmaddwd128 (v8hi, v8hi)
v2di __builtin_ia32_movq128 (v2di)
- The following built-in functions are available when '-msse3' is used.
+ The following built-in functions are available when `-msse3' is used.
All of them generate the machine instruction that is part of the name.
v2df __builtin_ia32_addsubpd (v2df, v2df)
@@ -39809,7 +40218,7 @@ All of them generate the machine instruction that is part of the name.
v4sf __builtin_ia32_movsldup (v4sf)
void __builtin_ia32_mwait (unsigned int, unsigned int)
- The following built-in functions are available when '-mssse3' is used.
+ The following built-in functions are available when `-mssse3' is used.
All of them generate the machine instruction that is part of the name.
v2si __builtin_ia32_phaddd (v2si, v2si)
@@ -39829,7 +40238,7 @@ All of them generate the machine instruction that is part of the name.
v2si __builtin_ia32_pabsd (v2si)
v4hi __builtin_ia32_pabsw (v4hi)
- The following built-in functions are available when '-mssse3' is used.
+ The following built-in functions are available when `-mssse3' is used.
All of them generate the machine instruction that is part of the name.
v4si __builtin_ia32_phaddd128 (v4si, v4si)
@@ -39849,8 +40258,9 @@ All of them generate the machine instruction that is part of the name.
v4si __builtin_ia32_pabsd128 (v4si)
v8hi __builtin_ia32_pabsw128 (v8hi)
- The following built-in functions are available when '-msse4.1' is used.
-All of them generate the machine instruction that is part of the name.
+ The following built-in functions are available when `-msse4.1' is
+used. All of them generate the machine instruction that is part of the
+name.
v2df __builtin_ia32_blendpd (v2df, v2df, const int)
v4sf __builtin_ia32_blendps (v4sf, v4sf, const int)
@@ -39896,31 +40306,38 @@ All of them generate the machine instruction that is part of the name.
v2df __builtin_ia32_roundsd (v2df, v2df, const int)
v4sf __builtin_ia32_roundss (v4sf, v4sf, const int)
- The following built-in functions are available when '-msse4.1' is used.
+ The following built-in functions are available when `-msse4.1' is used.
+
+`v4sf __builtin_ia32_vec_set_v4sf (v4sf, float, const int)'
+ Generates the `insertps' machine instruction.
+
+`int __builtin_ia32_vec_ext_v16qi (v16qi, const int)'
+ Generates the `pextrb' machine instruction.
+
+`v16qi __builtin_ia32_vec_set_v16qi (v16qi, int, const int)'
+ Generates the `pinsrb' machine instruction.
+
+`v4si __builtin_ia32_vec_set_v4si (v4si, int, const int)'
+ Generates the `pinsrd' machine instruction.
-'v4sf __builtin_ia32_vec_set_v4sf (v4sf, float, const int)'
- Generates the 'insertps' machine instruction.
-'int __builtin_ia32_vec_ext_v16qi (v16qi, const int)'
- Generates the 'pextrb' machine instruction.
-'v16qi __builtin_ia32_vec_set_v16qi (v16qi, int, const int)'
- Generates the 'pinsrb' machine instruction.
-'v4si __builtin_ia32_vec_set_v4si (v4si, int, const int)'
- Generates the 'pinsrd' machine instruction.
-'v2di __builtin_ia32_vec_set_v2di (v2di, long long, const int)'
- Generates the 'pinsrq' machine instruction in 64bit mode.
+`v2di __builtin_ia32_vec_set_v2di (v2di, long long, const int)'
+ Generates the `pinsrq' machine instruction in 64bit mode.
The following built-in functions are changed to generate new SSE4.1
-instructions when '-msse4.1' is used.
+instructions when `-msse4.1' is used.
-'float __builtin_ia32_vec_ext_v4sf (v4sf, const int)'
- Generates the 'extractps' machine instruction.
-'int __builtin_ia32_vec_ext_v4si (v4si, const int)'
- Generates the 'pextrd' machine instruction.
-'long long __builtin_ia32_vec_ext_v2di (v2di, const int)'
- Generates the 'pextrq' machine instruction in 64bit mode.
+`float __builtin_ia32_vec_ext_v4sf (v4sf, const int)'
+ Generates the `extractps' machine instruction.
- The following built-in functions are available when '-msse4.2' is used.
-All of them generate the machine instruction that is part of the name.
+`int __builtin_ia32_vec_ext_v4si (v4si, const int)'
+ Generates the `pextrd' machine instruction.
+
+`long long __builtin_ia32_vec_ext_v2di (v2di, const int)'
+ Generates the `pextrq' machine instruction in 64bit mode.
+
+ The following built-in functions are available when `-msse4.2' is
+used. All of them generate the machine instruction that is part of the
+name.
v16qi __builtin_ia32_pcmpestrm128 (v16qi, int, v16qi, int, const int)
int __builtin_ia32_pcmpestri128 (v16qi, int, v16qi, int, const int)
@@ -39938,29 +40355,34 @@ All of them generate the machine instruction that is part of the name.
int __builtin_ia32_pcmpistriz128 (v16qi, v16qi, const int)
v2di __builtin_ia32_pcmpgtq (v2di, v2di)
- The following built-in functions are available when '-msse4.2' is used.
+ The following built-in functions are available when `-msse4.2' is used.
+
+`unsigned int __builtin_ia32_crc32qi (unsigned int, unsigned char)'
+ Generates the `crc32b' machine instruction.
+
+`unsigned int __builtin_ia32_crc32hi (unsigned int, unsigned short)'
+ Generates the `crc32w' machine instruction.
-'unsigned int __builtin_ia32_crc32qi (unsigned int, unsigned char)'
- Generates the 'crc32b' machine instruction.
-'unsigned int __builtin_ia32_crc32hi (unsigned int, unsigned short)'
- Generates the 'crc32w' machine instruction.
-'unsigned int __builtin_ia32_crc32si (unsigned int, unsigned int)'
- Generates the 'crc32l' machine instruction.
-'unsigned long long __builtin_ia32_crc32di (unsigned long long, unsigned long long)'
- Generates the 'crc32q' machine instruction.
+`unsigned int __builtin_ia32_crc32si (unsigned int, unsigned int)'
+ Generates the `crc32l' machine instruction.
+
+`unsigned long long __builtin_ia32_crc32di (unsigned long long, unsigned long long)'
+ Generates the `crc32q' machine instruction.
The following built-in functions are changed to generate new SSE4.2
-instructions when '-msse4.2' is used.
+instructions when `-msse4.2' is used.
+
+`int __builtin_popcount (unsigned int)'
+ Generates the `popcntl' machine instruction.
-'int __builtin_popcount (unsigned int)'
- Generates the 'popcntl' machine instruction.
-'int __builtin_popcountl (unsigned long)'
- Generates the 'popcntl' or 'popcntq' machine instruction, depending
- on the size of 'unsigned long'.
-'int __builtin_popcountll (unsigned long long)'
- Generates the 'popcntq' machine instruction.
+`int __builtin_popcountl (unsigned long)'
+ Generates the `popcntl' or `popcntq' machine instruction,
+ depending on the size of `unsigned long'.
- The following built-in functions are available when '-mavx' is used.
+`int __builtin_popcountll (unsigned long long)'
+ Generates the `popcntq' machine instruction.
+
+ The following built-in functions are available when `-mavx' is used.
All of them generate the machine instruction that is part of the name.
v4df __builtin_ia32_addpd256 (v4df,v4df)
@@ -40092,7 +40514,7 @@ All of them generate the machine instruction that is part of the name.
v4df __builtin_ia32_xorpd256 (v4df,v4df)
v8sf __builtin_ia32_xorps256 (v8sf,v8sf)
- The following built-in functions are available when '-mavx2' is used.
+ The following built-in functions are available when `-mavx2' is used.
All of them generate the machine instruction that is part of the name.
v32qi __builtin_ia32_mpsadbw256 (v32qi,v32qi,int)
@@ -40267,7 +40689,7 @@ All of them generate the machine instruction that is part of the name.
v4si __builtin_ia32_gatherdiv4si (v4si, pcint,v2di,v4si,int)
v4si __builtin_ia32_gatherdiv4si256 (v4si, pcint,v4di,v4si,int)
- The following built-in functions are available when '-maes' is used.
+ The following built-in functions are available when `-maes' is used.
All of them generate the machine instruction that is part of the name.
v2di __builtin_ia32_aesenc128 (v2di, v2di)
@@ -40277,13 +40699,14 @@ All of them generate the machine instruction that is part of the name.
v2di __builtin_ia32_aeskeygenassist128 (v2di, const int)
v2di __builtin_ia32_aesimc128 (v2di)
- The following built-in function is available when '-mpclmul' is used.
+ The following built-in function is available when `-mpclmul' is used.
-'v2di __builtin_ia32_pclmulqdq128 (v2di, v2di, const int)'
- Generates the 'pclmulqdq' machine instruction.
+`v2di __builtin_ia32_pclmulqdq128 (v2di, v2di, const int)'
+ Generates the `pclmulqdq' machine instruction.
- The following built-in function is available when '-mfsgsbase' is used.
-All of them generate the machine instruction that is part of the name.
+ The following built-in function is available when `-mfsgsbase' is
+used. All of them generate the machine instruction that is part of the
+name.
unsigned int __builtin_ia32_rdfsbase32 (void)
unsigned long long __builtin_ia32_rdfsbase64 (void)
@@ -40294,14 +40717,14 @@ All of them generate the machine instruction that is part of the name.
void _writegsbase_u32 (unsigned int)
void _writegsbase_u64 (unsigned long long)
- The following built-in function is available when '-mrdrnd' is used.
+ The following built-in function is available when `-mrdrnd' is used.
All of them generate the machine instruction that is part of the name.
unsigned int __builtin_ia32_rdrand16_step (unsigned short *)
unsigned int __builtin_ia32_rdrand32_step (unsigned int *)
unsigned int __builtin_ia32_rdrand64_step (unsigned long long *)
- The following built-in functions are available when '-msse4a' is used.
+ The following built-in functions are available when `-msse4a' is used.
All of them generate the machine instruction that is part of the name.
void __builtin_ia32_movntsd (double *, v2df)
@@ -40311,7 +40734,7 @@ All of them generate the machine instruction that is part of the name.
v2di __builtin_ia32_insertq (v2di, v2di)
v2di __builtin_ia32_insertqi (v2di, v2di, const unsigned int, const unsigned int)
- The following built-in functions are available when '-mxop' is used.
+ The following built-in functions are available when `-mxop' is used.
v2df __builtin_ia32_vfrczpd (v2df)
v4sf __builtin_ia32_vfrczps (v4sf)
v2df __builtin_ia32_vfrczsd (v2df)
@@ -40437,7 +40860,7 @@ All of them generate the machine instruction that is part of the name.
v2di __builtin_ia32_vpshlq (v2di, v2di)
v8hi __builtin_ia32_vpshlw (v8hi, v8hi)
- The following built-in functions are available when '-mfma4' is used.
+ The following built-in functions are available when `-mfma4' is used.
All of them generate the machine instruction that is part of the name.
v2df __builtin_ia32_vfmaddpd (v2df, v2df, v2df)
@@ -40473,8 +40896,7 @@ All of them generate the machine instruction that is part of the name.
v4df __builtin_ia32_vfmsubaddpd256 (v4df, v4df, v4df)
v8sf __builtin_ia32_vfmsubaddps256 (v8sf, v8sf, v8sf)
-
- The following built-in functions are available when '-mlwp' is used.
+ The following built-in functions are available when `-mlwp' is used.
void __builtin_ia32_llwpcb16 (void *);
void __builtin_ia32_llwpcb32 (void *);
@@ -40489,12 +40911,12 @@ All of them generate the machine instruction that is part of the name.
unsigned char __builtin_ia32_lwpins32 (unsigned int, unsigned int, unsigned int)
unsigned char __builtin_ia32_lwpins64 (unsigned __int64, unsigned int, unsigned int)
- The following built-in functions are available when '-mbmi' is used.
+ The following built-in functions are available when `-mbmi' is used.
All of them generate the machine instruction that is part of the name.
unsigned int __builtin_ia32_bextr_u32(unsigned int, unsigned int);
unsigned long long __builtin_ia32_bextr_u64 (unsigned long long, unsigned long long);
- The following built-in functions are available when '-mbmi2' is used.
+ The following built-in functions are available when `-mbmi2' is used.
All of them generate the machine instruction that is part of the name.
unsigned int _bzhi_u32 (unsigned int, unsigned int)
unsigned int _pdep_u32 (unsigned int, unsigned int)
@@ -40503,39 +40925,39 @@ All of them generate the machine instruction that is part of the name.
unsigned long long _pdep_u64 (unsigned long long, unsigned long long)
unsigned long long _pext_u64 (unsigned long long, unsigned long long)
- The following built-in functions are available when '-mlzcnt' is used.
+ The following built-in functions are available when `-mlzcnt' is used.
All of them generate the machine instruction that is part of the name.
unsigned short __builtin_ia32_lzcnt_16(unsigned short);
unsigned int __builtin_ia32_lzcnt_u32(unsigned int);
unsigned long long __builtin_ia32_lzcnt_u64 (unsigned long long);
- The following built-in functions are available when '-mfxsr' is used.
+ The following built-in functions are available when `-mfxsr' is used.
All of them generate the machine instruction that is part of the name.
void __builtin_ia32_fxsave (void *)
void __builtin_ia32_fxrstor (void *)
void __builtin_ia32_fxsave64 (void *)
void __builtin_ia32_fxrstor64 (void *)
- The following built-in functions are available when '-mxsave' is used.
+ The following built-in functions are available when `-mxsave' is used.
All of them generate the machine instruction that is part of the name.
void __builtin_ia32_xsave (void *, long long)
void __builtin_ia32_xrstor (void *, long long)
void __builtin_ia32_xsave64 (void *, long long)
void __builtin_ia32_xrstor64 (void *, long long)
- The following built-in functions are available when '-mxsaveopt' is
+ The following built-in functions are available when `-mxsaveopt' is
used. All of them generate the machine instruction that is part of the
name.
void __builtin_ia32_xsaveopt (void *, long long)
void __builtin_ia32_xsaveopt64 (void *, long long)
- The following built-in functions are available when '-mtbm' is used.
+ The following built-in functions are available when `-mtbm' is used.
Both of them generate the immediate form of the bextr machine
instruction.
unsigned int __builtin_ia32_bextri_u32 (unsigned int, const unsigned int);
unsigned long long __builtin_ia32_bextri_u64 (unsigned long long, const unsigned long long);
- The following built-in functions are available when '-m3dnow' is used.
+ The following built-in functions are available when `-m3dnow' is used.
All of them generate the machine instruction that is part of the name.
void __builtin_ia32_femms (void)
@@ -40558,8 +40980,8 @@ All of them generate the machine instruction that is part of the name.
v2sf __builtin_ia32_pi2fd (v2si)
v4hi __builtin_ia32_pmulhrw (v4hi, v4hi)
- The following built-in functions are available when both '-m3dnow' and
-'-march=athlon' are used. All of them generate the machine instruction
+ The following built-in functions are available when both `-m3dnow' and
+`-march=athlon' are used. All of them generate the machine instruction
that is part of the name.
v2si __builtin_ia32_pf2iw (v2sf)
@@ -40569,9 +40991,9 @@ that is part of the name.
v2sf __builtin_ia32_pswapdsf (v2sf)
v2si __builtin_ia32_pswapdsi (v2si)
- The following built-in functions are available when '-mrtm' is used
-They are used for restricted transactional memory. These are the
-internal low level functions. Normally the functions in *note x86
+ The following built-in functions are available when `-mrtm' is used
+They are used for restricted transactional memory. These are the
+internal low level functions. Normally the functions in *note x86
transactional memory intrinsics:: should be used instead.
int __builtin_ia32_xbegin ()
@@ -40579,6 +41001,11 @@ transactional memory intrinsics:: should be used instead.
void __builtin_ia32_xabort (status)
int __builtin_ia32_xtest ()
+ The following built-in functions are available when `-mmwaitx' is used.
+All of them generate the machine instruction that is part of the name.
+ void __builtin_ia32_monitorx (void *, unsigned int, unsigned int)
+ void __builtin_ia32_mwaitx (unsigned int, unsigned int, unsigned int)
+

File: gcc.info, Node: x86 transactional memory intrinsics, Prev: x86 Built-in Functions, Up: Target Builtins
@@ -40587,48 +41014,54 @@ File: gcc.info, Node: x86 transactional memory intrinsics, Prev: x86 Built-in
These hardware transactional memory intrinsics for x86 allow you to use
memory transactions with RTM (Restricted Transactional Memory). This
-support is enabled with the '-mrtm' option. For using HLE (Hardware
+support is enabled with the `-mrtm' option. For using HLE (Hardware
Lock Elision) see *note x86 specific memory model extensions for
transactional memory:: instead.
- A memory transaction commits all changes to memory in an atomic way, as
-visible to other threads. If the transaction fails it is rolled back
+ A memory transaction commits all changes to memory in an atomic way,
+as visible to other threads. If the transaction fails it is rolled back
and all side effects discarded.
Generally there is no guarantee that a memory transaction ever succeeds
and suitable fallback code always needs to be supplied.
-- RTM Function: unsigned _xbegin ()
- Start a RTM (Restricted Transactional Memory) transaction. Returns
- '_XBEGIN_STARTED' when the transaction started successfully (note
- this is not 0, so the constant has to be explicitly tested).
-
- If the transaction aborts, all side-effects are undone and an abort
- code encoded as a bit mask is returned. The following macros are
- defined:
-
- '_XABORT_EXPLICIT'
- Transaction was explicitly aborted with '_xabort'. The
- parameter passed to '_xabort' is available with
- '_XABORT_CODE(status)'.
- '_XABORT_RETRY'
+ Start a RTM (Restricted Transactional Memory) transaction.
+ Returns `_XBEGIN_STARTED' when the transaction started
+ successfully (note this is not 0, so the constant has to be
+ explicitly tested).
+
+ If the transaction aborts, all side-effects are undone and an
+ abort code encoded as a bit mask is returned. The following
+ macros are defined:
+
+ `_XABORT_EXPLICIT'
+ Transaction was explicitly aborted with `_xabort'. The
+ parameter passed to `_xabort' is available with
+ `_XABORT_CODE(status)'.
+
+ `_XABORT_RETRY'
Transaction retry is possible.
- '_XABORT_CONFLICT'
+
+ `_XABORT_CONFLICT'
Transaction abort due to a memory conflict with another
thread.
- '_XABORT_CAPACITY'
+
+ `_XABORT_CAPACITY'
Transaction abort due to the transaction using too much
memory.
- '_XABORT_DEBUG'
+
+ `_XABORT_DEBUG'
Transaction abort due to a debug trap.
- '_XABORT_NESTED'
+
+ `_XABORT_NESTED'
Transaction abort in an inner nested transaction.
There is no guarantee any transaction ever succeeds, so there
always needs to be a valid fallback path.
-- RTM Function: void _xend ()
- Commit the current transaction. When no transaction is active this
+ Commit the current transaction. When no transaction is active this
faults. All memory side-effects of the transaction become visible
to other threads in an atomic manner.
@@ -40637,11 +41070,11 @@ and suitable fallback code always needs to be supplied.
otherwise 0.
-- RTM Function: void _xabort (status)
- Abort the current transaction. When no transaction is active this
+ Abort the current transaction. When no transaction is active this
is a no-op. The STATUS is an 8-bit constant; its value is encoded
- in the return value from '_xbegin'.
+ in the return value from `_xbegin'.
- Here is an example showing handling for '_XABORT_RETRY' and a fallback
+ Here is an example showing handling for `_XABORT_RETRY' and a fallback
path for other failures:
#include <immintrin.h>
@@ -40690,10 +41123,10 @@ File: gcc.info, Node: Solaris Format Checks, Next: Darwin Format Checks, Up:
6.59.1 Solaris Format Checks
----------------------------
-Solaris targets support the 'cmn_err' (or '__cmn_err__') format check.
-'cmn_err' accepts a subset of the standard 'printf' conversions, and the
-two-argument '%b' conversion for displaying bit-fields. See the Solaris
-man page for 'cmn_err' for more information.
+Solaris targets support the `cmn_err' (or `__cmn_err__') format check.
+`cmn_err' accepts a subset of the standard `printf' conversions, and
+the two-argument `%b' conversion for displaying bit-fields. See the
+Solaris man page for `cmn_err' for more information.

File: gcc.info, Node: Darwin Format Checks, Prev: Solaris Format Checks, Up: Target Format Checks
@@ -40701,17 +41134,17 @@ File: gcc.info, Node: Darwin Format Checks, Prev: Solaris Format Checks, Up:
6.59.2 Darwin Format Checks
---------------------------
-Darwin targets support the 'CFString' (or '__CFString__') in the format
+Darwin targets support the `CFString' (or `__CFString__') in the format
attribute context. Declarations made with such attribution are parsed
for correct syntax and format argument types. However, parsing of the
format string itself is currently undefined and is not carried out by
this version of the compiler.
- Additionally, 'CFStringRefs' (defined by the 'CoreFoundation' headers)
+ Additionally, `CFStringRefs' (defined by the `CoreFoundation' headers)
may also be used as format arguments. Note that the relevant headers
are only likely to be available on Darwin (OSX) installations. On such
installations, the XCode and system documentation provide descriptions
-of 'CFString', 'CFStringRefs' and associated functions.
+of `CFString', `CFStringRefs' and associated functions.

File: gcc.info, Node: Pragmas, Next: Unnamed Fields, Prev: Target Format Checks, Up: C Extensions
@@ -40720,8 +41153,8 @@ File: gcc.info, Node: Pragmas, Next: Unnamed Fields, Prev: Target Format Chec
============================
GCC supports several types of pragmas, primarily in order to compile
-code originally written for other compilers. Note that in general we do
-not recommend the use of pragmas; *Note Function Attributes::, for
+code originally written for other compilers. Note that in general we
+do not recommend the use of pragmas; *Note Function Attributes::, for
further explanation.
* Menu:
@@ -40748,17 +41181,17 @@ File: gcc.info, Node: ARM Pragmas, Next: M32C Pragmas, Up: Pragmas
------------------
The ARM target defines pragmas for controlling the default addition of
-'long_call' and 'short_call' attributes to functions. *Note Function
+`long_call' and `short_call' attributes to functions. *Note Function
Attributes::, for information about the effects of these attributes.
-'long_calls'
- Set all subsequent functions to have the 'long_call' attribute.
+`long_calls'
+ Set all subsequent functions to have the `long_call' attribute.
-'no_long_calls'
- Set all subsequent functions to have the 'short_call' attribute.
+`no_long_calls'
+ Set all subsequent functions to have the `short_call' attribute.
-'long_calls_off'
- Do not affect the 'long_call' or 'short_call' attributes of
+`long_calls_off'
+ Do not affect the `long_call' or `short_call' attributes of
subsequent functions.

@@ -40767,46 +41200,47 @@ File: gcc.info, Node: M32C Pragmas, Next: MeP Pragmas, Prev: ARM Pragmas, Up
6.60.2 M32C Pragmas
-------------------
-'GCC memregs NUMBER'
- Overrides the command-line option '-memregs=' for the current file.
- Use with care! This pragma must be before any function in the
- file, and mixing different memregs values in different objects may
- make them incompatible. This pragma is useful when a
+`GCC memregs NUMBER'
+ Overrides the command-line option `-memregs=' for the current
+ file. Use with care! This pragma must be before any function in
+ the file, and mixing different memregs values in different objects
+ may make them incompatible. This pragma is useful when a
performance-critical function uses a memreg for temporary values,
as it may allow you to reduce the number of memregs used.
-'ADDRESS NAME ADDRESS'
+`ADDRESS NAME ADDRESS'
For any declared symbols matching NAME, this does three things to
that symbol: it forces the symbol to be located at the given
address (a number), it forces the symbol to be volatile, and it
changes the symbol's scope to be static. This pragma exists for
compatibility with other compilers, but note that the common
- '1234H' numeric syntax is not supported (use '0x1234' instead).
+ `1234H' numeric syntax is not supported (use `0x1234' instead).
Example:
#pragma ADDRESS port3 0x103
char port3;
+

File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M32C Pragmas, Up: Pragmas
6.60.3 MeP Pragmas
------------------
-'custom io_volatile (on|off)'
- Overrides the command-line option '-mio-volatile' for the current
+`custom io_volatile (on|off)'
+ Overrides the command-line option `-mio-volatile' for the current
file. Note that for compatibility with future GCC releases, this
- option should only be used once before any 'io' variables in each
+ option should only be used once before any `io' variables in each
file.
-'GCC coprocessor available REGISTERS'
+`GCC coprocessor available REGISTERS'
Specifies which coprocessor registers are available to the register
allocator. REGISTERS may be a single register, register range
separated by ellipses, or comma-separated list of those. Example:
#pragma GCC coprocessor available $c0...$c10, $c28
-'GCC coprocessor call_saved REGISTERS'
+`GCC coprocessor call_saved REGISTERS'
Specifies which coprocessor registers are to be saved and restored
by any function using them. REGISTERS may be a single register,
register range separated by ellipses, or comma-separated list of
@@ -40814,9 +41248,9 @@ File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M
#pragma GCC coprocessor call_saved $c4...$c6, $c31
-'GCC coprocessor subclass '(A|B|C|D)' = REGISTERS'
+`GCC coprocessor subclass '(A|B|C|D)' = REGISTERS'
Creates and defines a register class. These register classes can
- be used by inline 'asm' constructs. REGISTERS may be a single
+ be used by inline `asm' constructs. REGISTERS may be a single
register, register range separated by ellipses, or comma-separated
list of those. Example:
@@ -40824,7 +41258,7 @@ File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M
asm ("cpfoo %0" : "=B" (x));
-'GCC disinterrupt NAME , NAME ...'
+`GCC disinterrupt NAME , NAME ...'
For the named functions, the compiler adds code to disable
interrupts for the duration of those functions. If any functions
so named are not encountered in the source, a warning is emitted
@@ -40834,7 +41268,7 @@ File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M
#pragma disinterrupt bar, grill
int foo () { ... }
-'GCC call NAME , NAME ...'
+`GCC call NAME , NAME ...'
For the named functions, the compiler always uses a
register-indirect call model when calling the named functions.
Examples:
@@ -40842,6 +41276,7 @@ File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M
extern int foo ();
#pragma call foo
+

File: gcc.info, Node: RS/6000 and PowerPC Pragmas, Next: Darwin Pragmas, Prev: MeP Pragmas, Up: Pragmas
@@ -40849,18 +41284,18 @@ File: gcc.info, Node: RS/6000 and PowerPC Pragmas, Next: Darwin Pragmas, Prev
----------------------------------
The RS/6000 and PowerPC targets define one pragma for controlling
-whether or not the 'longcall' attribute is added to function
-declarations by default. This pragma overrides the '-mlongcall' option,
-but not the 'longcall' and 'shortcall' attributes. *Note RS/6000 and
-PowerPC Options::, for more information about when long calls are and
-are not necessary.
-
-'longcall (1)'
- Apply the 'longcall' attribute to all subsequent function
+whether or not the `longcall' attribute is added to function
+declarations by default. This pragma overrides the `-mlongcall'
+option, but not the `longcall' and `shortcall' attributes. *Note
+RS/6000 and PowerPC Options::, for more information about when long
+calls are and are not necessary.
+
+`longcall (1)'
+ Apply the `longcall' attribute to all subsequent function
declarations.
-'longcall (0)'
- Do not apply the 'longcall' attribute to subsequent function
+`longcall (0)'
+ Do not apply the `longcall' attribute to subsequent function
declarations.

@@ -40873,23 +41308,23 @@ The following pragmas are available for all architectures running the
Darwin operating system. These are useful for compatibility with other
Mac OS compilers.
-'mark TOKENS...'
+`mark TOKENS...'
This pragma is accepted, but has no effect.
-'options align=ALIGNMENT'
- This pragma sets the alignment of fields in structures. The values
- of ALIGNMENT may be 'mac68k', to emulate m68k alignment, or
- 'power', to emulate PowerPC alignment. Uses of this pragma nest
- properly; to restore the previous setting, use 'reset' for the
+`options align=ALIGNMENT'
+ This pragma sets the alignment of fields in structures. The
+ values of ALIGNMENT may be `mac68k', to emulate m68k alignment, or
+ `power', to emulate PowerPC alignment. Uses of this pragma nest
+ properly; to restore the previous setting, use `reset' for the
ALIGNMENT.
-'segment TOKENS...'
+`segment TOKENS...'
This pragma is accepted, but has no effect.
-'unused (VAR [, VAR]...)'
+`unused (VAR [, VAR]...)'
This pragma declares variables to be possibly unused. GCC does not
produce warnings for the listed variables. The effect is similar
- to that of the 'unused' attribute, except that this pragma may
+ to that of the `unused' attribute, except that this pragma may
appear anywhere within the variables' scopes.

@@ -40898,30 +41333,28 @@ File: gcc.info, Node: Solaris Pragmas, Next: Symbol-Renaming Pragmas, Prev: D
6.60.6 Solaris Pragmas
----------------------
-The Solaris target supports '#pragma redefine_extname' (*note
-Symbol-Renaming Pragmas::). It also supports additional '#pragma'
+The Solaris target supports `#pragma redefine_extname' (*note
+Symbol-Renaming Pragmas::). It also supports additional `#pragma'
directives for compatibility with the system compiler.
-'align ALIGNMENT (VARIABLE [, VARIABLE]...)'
-
- Increase the minimum alignment of each VARIABLE to ALIGNMENT. This
- is the same as GCC's 'aligned' attribute *note Variable
+`align ALIGNMENT (VARIABLE [, VARIABLE]...)'
+ Increase the minimum alignment of each VARIABLE to ALIGNMENT.
+ This is the same as GCC's `aligned' attribute *note Variable
Attributes::). Macro expansion occurs on the arguments to this
pragma when compiling C and Objective-C. It does not currently
- occur when compiling C++, but this is a bug which may be fixed in a
- future release.
-
-'fini (FUNCTION [, FUNCTION]...)'
+ occur when compiling C++, but this is a bug which may be fixed in
+ a future release.
- This pragma causes each listed FUNCTION to be called after main, or
- during shared module unloading, by adding a call to the '.fini'
+`fini (FUNCTION [, FUNCTION]...)'
+ This pragma causes each listed FUNCTION to be called after main,
+ or during shared module unloading, by adding a call to the `.fini'
section.
-'init (FUNCTION [, FUNCTION]...)'
-
+`init (FUNCTION [, FUNCTION]...)'
This pragma causes each listed FUNCTION to be called during
- initialization (before 'main') or during shared module loading, by
- adding a call to the '.init' section.
+ initialization (before `main') or during shared module loading, by
+ adding a call to the `.init' section.
+

File: gcc.info, Node: Symbol-Renaming Pragmas, Next: Structure-Packing Pragmas, Prev: Solaris Pragmas, Up: Pragmas
@@ -40929,16 +41362,15 @@ File: gcc.info, Node: Symbol-Renaming Pragmas, Next: Structure-Packing Pragmas
6.60.7 Symbol-Renaming Pragmas
------------------------------
-GCC supports a '#pragma' directive that changes the name used in
-assembly for a given declaration. While this pragma is supported on all
+GCC supports a `#pragma' directive that changes the name used in
+assembly for a given declaration. While this pragma is supported on all
platforms, it is intended primarily to provide compatibility with the
-Solaris system headers. This effect can also be achieved using the asm
+Solaris system headers. This effect can also be achieved using the asm
labels extension (*note Asm Labels::).
-'redefine_extname OLDNAME NEWNAME'
-
+`redefine_extname OLDNAME NEWNAME'
This pragma gives the C function OLDNAME the assembly symbol
- NEWNAME. The preprocessor macro '__PRAGMA_REDEFINE_EXTNAME' is
+ NEWNAME. The preprocessor macro `__PRAGMA_REDEFINE_EXTNAME' is
defined if this pragma is available (currently on all platforms).
This pragma and the asm labels extension interact in a complicated
@@ -40953,11 +41385,11 @@ manner. Here are some corner cases you may want to be aware of:
3. If either of the ways of changing the assembly name of a
declaration are applied to a declaration whose assembly name has
already been determined (either by a previous use of one of these
- features, or because the compiler needed the assembly name in order
- to generate code), and the new name is different, a warning issues
- and the name does not change.
+ features, or because the compiler needed the assembly name in
+ order to generate code), and the new name is different, a warning
+ issues and the name does not change.
- 4. The OLDNAME used by '#pragma redefine_extname' is always the
+ 4. The OLDNAME used by `#pragma redefine_extname' is always the
C-language name.

@@ -40967,31 +41399,36 @@ File: gcc.info, Node: Structure-Packing Pragmas, Next: Weak Pragmas, Prev: Sy
--------------------------------
For compatibility with Microsoft Windows compilers, GCC supports a set
-of '#pragma' directives that change the maximum alignment of members of
+of `#pragma' directives that change the maximum alignment of members of
structures (other than zero-width bit-fields), unions, and classes
-subsequently defined. The N value below always is required to be a
+subsequently defined. The N value below always is required to be a
small power of two and specifies the new alignment in bytes.
- 1. '#pragma pack(N)' simply sets the new alignment.
- 2. '#pragma pack()' sets the alignment to the one that was in effect
+ 1. `#pragma pack(N)' simply sets the new alignment.
+
+ 2. `#pragma pack()' sets the alignment to the one that was in effect
when compilation started (see also command-line option
- '-fpack-struct[=N]' *note Code Gen Options::).
- 3. '#pragma pack(push[,N])' pushes the current alignment setting on an
- internal stack and then optionally sets the new alignment.
- 4. '#pragma pack(pop)' restores the alignment setting to the one saved
- at the top of the internal stack (and removes that stack entry).
- Note that '#pragma pack([N])' does not influence this internal
- stack; thus it is possible to have '#pragma pack(push)' followed by
- multiple '#pragma pack(N)' instances and finalized by a single
- '#pragma pack(pop)'.
-
- Some targets, e.g. x86 and PowerPC, support the 'ms_struct' '#pragma'
-which lays out a structure as the documented '__attribute__
+ `-fpack-struct[=N]' *note Code Gen Options::).
+
+ 3. `#pragma pack(push[,N])' pushes the current alignment setting on
+ an internal stack and then optionally sets the new alignment.
+
+ 4. `#pragma pack(pop)' restores the alignment setting to the one
+ saved at the top of the internal stack (and removes that stack
+ entry). Note that `#pragma pack([N])' does not influence this
+ internal stack; thus it is possible to have `#pragma pack(push)'
+ followed by multiple `#pragma pack(N)' instances and finalized by
+ a single `#pragma pack(pop)'.
+
+ Some targets, e.g. x86 and PowerPC, support the `ms_struct' `#pragma'
+which lays out a structure as the documented `__attribute__
((ms_struct))'.
- 1. '#pragma ms_struct on' turns on the layout for structures declared.
- 2. '#pragma ms_struct off' turns off the layout for structures
+ 1. `#pragma ms_struct on' turns on the layout for structures declared.
+
+ 2. `#pragma ms_struct off' turns off the layout for structures
declared.
- 3. '#pragma ms_struct reset' goes back to the default layout.
+
+ 3. `#pragma ms_struct reset' goes back to the default layout.

File: gcc.info, Node: Weak Pragmas, Next: Diagnostic Pragmas, Prev: Structure-Packing Pragmas, Up: Pragmas
@@ -40999,16 +41436,16 @@ File: gcc.info, Node: Weak Pragmas, Next: Diagnostic Pragmas, Prev: Structure
6.60.9 Weak Pragmas
-------------------
-For compatibility with SVR4, GCC supports a set of '#pragma' directives
+For compatibility with SVR4, GCC supports a set of `#pragma' directives
for declaring symbols to be weak, and defining weak aliases.
-'#pragma weak SYMBOL'
+`#pragma weak SYMBOL'
This pragma declares SYMBOL to be weak, as if the declaration had
the attribute of the same name. The pragma may appear before or
after the declaration of SYMBOL. It is not an error for SYMBOL to
never be defined at all.
-'#pragma weak SYMBOL1 = SYMBOL2'
+`#pragma weak SYMBOL1 = SYMBOL2'
This pragma declares SYMBOL1 to be a weak alias of SYMBOL2. It is
an error if SYMBOL2 is not defined in the current translation unit.
@@ -41020,22 +41457,21 @@ File: gcc.info, Node: Diagnostic Pragmas, Next: Visibility Pragmas, Prev: Wea
GCC allows the user to selectively enable or disable certain types of
diagnostics, and change the kind of the diagnostic. For example, a
-project's policy might require that all sources compile with '-Werror'
+project's policy might require that all sources compile with `-Werror'
but certain files might have exceptions allowing specific types of
warnings. Or, a project might selectively enable diagnostics and treat
them as errors depending on which preprocessor macros are defined.
-'#pragma GCC diagnostic KIND OPTION'
-
+`#pragma GCC diagnostic KIND OPTION'
Modifies the disposition of a diagnostic. Note that not all
diagnostics are modifiable; at the moment only warnings (normally
- controlled by '-W...') can be controlled, and not all of them. Use
- '-fdiagnostics-show-option' to determine which diagnostics are
+ controlled by `-W...') can be controlled, and not all of them.
+ Use `-fdiagnostics-show-option' to determine which diagnostics are
controllable and which option controls them.
- KIND is 'error' to treat this diagnostic as an error, 'warning' to
- treat it like a warning (even if '-Werror' is in effect), or
- 'ignored' if the diagnostic is to be ignored. OPTION is a double
+ KIND is `error' to treat this diagnostic as an error, `warning' to
+ treat it like a warning (even if `-Werror' is in effect), or
+ `ignored' if the diagnostic is to be ignored. OPTION is a double
quoted string that matches the command-line option.
#pragma GCC diagnostic warning "-Wformat"
@@ -41048,12 +41484,11 @@ them as errors depending on which preprocessor macros are defined.
pragmas occurring after a line do not affect diagnostics caused by
that line.
-'#pragma GCC diagnostic push'
-'#pragma GCC diagnostic pop'
-
+`#pragma GCC diagnostic push'
+`#pragma GCC diagnostic pop'
Causes GCC to remember the state of the diagnostics as of each
- 'push', and restore to that point at each 'pop'. If a 'pop' has no
- matching 'push', the command-line options are restored.
+ `push', and restore to that point at each `pop'. If a `pop' has
+ no matching `push', the command-line options are restored.
#pragma GCC diagnostic error "-Wuninitialized"
foo(a); /* error is given for this one */
@@ -41065,13 +41500,13 @@ them as errors depending on which preprocessor macros are defined.
#pragma GCC diagnostic pop
foo(d); /* depends on command-line options */
+
GCC also offers a simple mechanism for printing messages during
compilation.
-'#pragma message STRING'
-
- Prints STRING as a compiler message on compilation. The message is
- informational only, and is neither a compilation warning nor an
+`#pragma message STRING'
+ Prints STRING as a compiler message on compilation. The message
+ is informational only, and is neither a compilation warning nor an
error.
#pragma message "Compiling " __FILE__ "..."
@@ -41084,27 +41519,28 @@ compilation.
TODO(Remember to fix this)
- prints '/tmp/file.c:4: note: #pragma message: TODO - Remember to
+ prints `/tmp/file.c:4: note: #pragma message: TODO - Remember to
fix this'.
+

File: gcc.info, Node: Visibility Pragmas, Next: Push/Pop Macro Pragmas, Prev: Diagnostic Pragmas, Up: Pragmas
6.60.11 Visibility Pragmas
--------------------------
-'#pragma GCC visibility push(VISIBILITY)'
-'#pragma GCC visibility pop'
-
+`#pragma GCC visibility push(VISIBILITY)'
+`#pragma GCC visibility pop'
This pragma allows the user to set the visibility for multiple
declarations without having to give each a visibility attribute
(*note Function Attributes::).
- In C++, '#pragma GCC visibility' affects only namespace-scope
+ In C++, `#pragma GCC visibility' affects only namespace-scope
declarations. Class members and template specializations are not
affected; if you want to override the visibility for a particular
member or instantiation, you must use an attribute.
+

File: gcc.info, Node: Push/Pop Macro Pragmas, Next: Function Specific Option Pragmas, Prev: Visibility Pragmas, Up: Pragmas
@@ -41112,16 +41548,16 @@ File: gcc.info, Node: Push/Pop Macro Pragmas, Next: Function Specific Option P
------------------------------
For compatibility with Microsoft Windows compilers, GCC supports
-'#pragma push_macro("MACRO_NAME")' and '#pragma
+`#pragma push_macro("MACRO_NAME")' and `#pragma
pop_macro("MACRO_NAME")'.
-'#pragma push_macro("MACRO_NAME")'
- This pragma saves the value of the macro named as MACRO_NAME to the
- top of the stack for this macro.
+`#pragma push_macro("MACRO_NAME")'
+ This pragma saves the value of the macro named as MACRO_NAME to
+ the top of the stack for this macro.
-'#pragma pop_macro("MACRO_NAME")'
+`#pragma pop_macro("MACRO_NAME")'
This pragma sets the value of the macro named as MACRO_NAME to the
- value on top of the stack for this macro. If the stack for
+ value on top of the stack for this macro. If the stack for
MACRO_NAME is empty, the value of the macro remains unchanged.
For example:
@@ -41133,8 +41569,8 @@ pop_macro("MACRO_NAME")'.
#pragma pop_macro("X")
int x [X];
-In this example, the definition of X as 1 is saved by '#pragma
-push_macro' and restored by '#pragma pop_macro'.
+In this example, the definition of X as 1 is saved by `#pragma
+push_macro' and restored by `#pragma pop_macro'.

File: gcc.info, Node: Function Specific Option Pragmas, Next: Loop-Specific Pragmas, Prev: Push/Pop Macro Pragmas, Up: Pragmas
@@ -41142,41 +41578,37 @@ File: gcc.info, Node: Function Specific Option Pragmas, Next: Loop-Specific Pr
6.60.13 Function Specific Option Pragmas
----------------------------------------
-'#pragma GCC target ("STRING"...)'
-
+`#pragma GCC target ("STRING"...)'
This pragma allows you to set target specific options for functions
defined later in the source file. One or more strings can be
- specified. Each function that is defined after this point is as if
- 'attribute((target("STRING")))' was specified for that function.
- The parenthesis around the options is optional. *Note Function
- Attributes::, for more information about the 'target' attribute and
- the attribute syntax.
+ specified. Each function that is defined after this point is as
+ if `attribute((target("STRING")))' was specified for that
+ function. The parenthesis around the options is optional. *Note
+ Function Attributes::, for more information about the `target'
+ attribute and the attribute syntax.
- The '#pragma GCC target' pragma is presently implemented for x86,
+ The `#pragma GCC target' pragma is presently implemented for x86,
PowerPC, and Nios II targets only.
-'#pragma GCC optimize ("STRING"...)'
-
+`#pragma GCC optimize ("STRING"...)'
This pragma allows you to set global optimization options for
functions defined later in the source file. One or more strings
can be specified. Each function that is defined after this point
- is as if 'attribute((optimize("STRING")))' was specified for that
+ is as if `attribute((optimize("STRING")))' was specified for that
function. The parenthesis around the options is optional. *Note
- Function Attributes::, for more information about the 'optimize'
+ Function Attributes::, for more information about the `optimize'
attribute and the attribute syntax.
-'#pragma GCC push_options'
-'#pragma GCC pop_options'
-
+`#pragma GCC push_options'
+`#pragma GCC pop_options'
These pragmas maintain a stack of the current target and
optimization options. It is intended for include files where you
- temporarily want to switch to using a different '#pragma GCC
- target' or '#pragma GCC optimize' and then to pop back to the
+ temporarily want to switch to using a different `#pragma GCC
+ target' or `#pragma GCC optimize' and then to pop back to the
previous options.
-'#pragma GCC reset_options'
-
- This pragma clears the current '#pragma GCC target' and '#pragma
+`#pragma GCC reset_options'
+ This pragma clears the current `#pragma GCC target' and `#pragma
GCC optimize' to use the default switches as specified on the
command line.
@@ -41186,12 +41618,12 @@ File: gcc.info, Node: Loop-Specific Pragmas, Prev: Function Specific Option Pr
6.60.14 Loop-Specific Pragmas
-----------------------------
-'#pragma GCC ivdep'
+`#pragma GCC ivdep'
With this pragma, the programmer asserts that there are no loop-carried
-dependencies which would prevent consecutive iterations of the following
-loop from executing concurrently with SIMD (single instruction multiple
-data) instructions.
+dependencies which would prevent consecutive iterations of the
+following loop from executing concurrently with SIMD (single
+instruction multiple data) instructions.
For example, the compiler can only unconditionally vectorize the
following loop with the pragma:
@@ -41204,9 +41636,9 @@ following loop with the pragma:
a[i] = b[i] + c[i];
}
-In this example, using the 'restrict' qualifier had the same effect. In
-the following example, that would not be possible. Assume k < -m or k
->= m. Only with the pragma, the compiler knows that it can
+In this example, using the `restrict' qualifier had the same effect. In
+the following example, that would not be possible. Assume k < -m or k
+>= m. Only with the pragma, the compiler knows that it can
unconditionally vectorize the following loop:
void ignore_vec_dep (int *a, int k, int c, int m)
@@ -41236,8 +41668,8 @@ structures and unions without names. For example:
} foo;
In this example, you are able to access members of the unnamed union
-with code like 'foo.b'. Note that only unnamed structs and unions are
-allowed, you may not have, for example, an unnamed 'int'.
+with code like `foo.b'. Note that only unnamed structs and unions are
+allowed, you may not have, for example, an unnamed `int'.
You must never create such structures that cause ambiguous field
definitions. For example, in this structure:
@@ -41249,17 +41681,18 @@ definitions. For example, in this structure:
};
} foo;
-it is ambiguous which 'a' is being referred to with 'foo.a'. The
+it is ambiguous which `a' is being referred to with `foo.a'. The
compiler gives errors for such constructs.
- Unless '-fms-extensions' is used, the unnamed field must be a structure
-or union definition without a tag (for example, 'struct { int a; };').
-If '-fms-extensions' is used, the field may also be a definition with a
-tag such as 'struct foo { int a; };', a reference to a previously
-defined structure or union such as 'struct foo;', or a reference to a
-'typedef' name for a previously defined structure or union type.
+ Unless `-fms-extensions' is used, the unnamed field must be a
+structure or union definition without a tag (for example, `struct { int
+a; };'). If `-fms-extensions' is used, the field may also be a
+definition with a tag such as `struct foo { int a; };', a reference to
+a previously defined structure or union such as `struct foo;', or a
+reference to a `typedef' name for a previously defined structure or
+union type.
- The option '-fplan9-extensions' enables '-fms-extensions' as well as
+ The option `-fplan9-extensions' enables `-fms-extensions' as well as
two other extensions. First, a pointer to a structure is automatically
converted to a pointer to an anonymous field for assignments and
function calls. For example:
@@ -41269,12 +41702,12 @@ function calls. For example:
extern void f1 (struct s1 *);
void f2 (struct s2 *p) { f1 (p); }
-In the call to 'f1' inside 'f2', the pointer 'p' is converted into a
+In the call to `f1' inside `f2', the pointer `p' is converted into a
pointer to the anonymous field.
- Second, when the type of an anonymous field is a 'typedef' for a
-'struct' or 'union', code may refer to the field using the name of the
-'typedef'.
+ Second, when the type of an anonymous field is a `typedef' for a
+`struct' or `union', code may refer to the field using the name of the
+`typedef'.
typedef struct { int a; } s1;
struct s2 { s1; };
@@ -41293,22 +41726,22 @@ allocated such that there is one instance of the variable per extant
thread. The runtime model GCC uses to implement this originates in the
IA-64 processor-specific ABI, but has since been migrated to other
processors as well. It requires significant support from the linker
-('ld'), dynamic linker ('ld.so'), and system libraries ('libc.so' and
-'libpthread.so'), so it is not available everywhere.
+(`ld'), dynamic linker (`ld.so'), and system libraries (`libc.so' and
+`libpthread.so'), so it is not available everywhere.
At the user level, the extension is visible with a new storage class
-keyword: '__thread'. For example:
+keyword: `__thread'. For example:
__thread int i;
extern __thread struct state s;
static __thread char *p;
- The '__thread' specifier may be used alone, with the 'extern' or
-'static' specifiers, but with no other storage class specifier. When
-used with 'extern' or 'static', '__thread' must appear immediately after
-the other storage class specifier.
+ The `__thread' specifier may be used alone, with the `extern' or
+`static' specifiers, but with no other storage class specifier. When
+used with `extern' or `static', `__thread' must appear immediately
+after the other storage class specifier.
- The '__thread' specifier may be applied to any global, file-scoped
+ The `__thread' specifier may be applied to any global, file-scoped
static, function-scoped static, or static data member of a class. It
may not be applied to block-scoped automatic or non-static data member.
@@ -41344,7 +41777,7 @@ File: gcc.info, Node: C99 Thread-Local Edits, Next: C++98 Thread-Local Edits,
The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that
document the exact semantics of the language extension.
- * '5.1.2 Execution environments'
+ * `5.1.2 Execution environments'
Add new text after paragraph 1
@@ -41357,37 +41790,38 @@ document the exact semantics of the language extension.
terminated. However, objects with thread storage duration
shall be initialized before thread startup.
- * '6.2.4 Storage durations of objects'
+ * `6.2.4 Storage durations of objects'
Add new text before paragraph 3
An object whose identifier is declared with the storage-class
- specifier '__thread' has "thread storage duration". Its
- lifetime is the entire execution of the thread, and its stored
- value is initialized only once, prior to thread startup.
+ specifier `__thread' has "thread storage duration". Its
+ lifetime is the entire execution of the thread, and its
+ stored value is initialized only once, prior to thread
+ startup.
- * '6.4.1 Keywords'
+ * `6.4.1 Keywords'
- Add '__thread'.
+ Add `__thread'.
- * '6.7.1 Storage-class specifiers'
+ * `6.7.1 Storage-class specifiers'
- Add '__thread' to the list of storage class specifiers in paragraph
- 1.
+ Add `__thread' to the list of storage class specifiers in
+ paragraph 1.
Change paragraph 2 to
- With the exception of '__thread', at most one storage-class
- specifier may be given [...]. The '__thread' specifier may be
- used alone, or immediately following 'extern' or 'static'.
+ With the exception of `__thread', at most one storage-class
+ specifier may be given [...]. The `__thread' specifier may
+ be used alone, or immediately following `extern' or `static'.
Add new text after paragraph 6
- The declaration of an identifier for a variable that has block
- scope that specifies '__thread' shall also specify either
- 'extern' or 'static'.
+ The declaration of an identifier for a variable that has
+ block scope that specifies `__thread' shall also specify
+ either `extern' or `static'.
- The '__thread' specifier shall be used only with variables.
+ The `__thread' specifier shall be used only with variables.

File: gcc.info, Node: C++98 Thread-Local Edits, Prev: C99 Thread-Local Edits, Up: Thread-Local
@@ -41414,20 +41848,20 @@ that document the exact semantics of the language extension.
* [lex.key]
- Add '__thread'.
+ Add `__thread'.
* [basic.start.main]
Add after paragraph 5
- The thread that begins execution at the 'main' function is
+ The thread that begins execution at the `main' function is
called the "main thread". It is implementation defined how
functions beginning threads other than the main thread are
- designated or typed. A function so designated, as well as the
- 'main' function, is called a "thread startup function". It is
- implementation defined what happens if a thread startup
+ designated or typed. A function so designated, as well as
+ the `main' function, is called a "thread startup function".
+ It is implementation defined what happens if a thread startup
function returns. It is implementation defined what happens
- to other threads when any thread calls 'exit'.
+ to other threads when any thread calls `exit'.
* [basic.start.init]
@@ -41435,8 +41869,8 @@ that document the exact semantics of the language extension.
The storage for an object of thread storage duration shall be
statically initialized before the first statement of the
- thread startup function. An object of thread storage duration
- shall not require dynamic initialization.
+ thread startup function. An object of thread storage
+ duration shall not require dynamic initialization.
* [basic.start.term]
@@ -41453,20 +41887,20 @@ that document the exact semantics of the language extension.
Change paragraph 2
- Thread, static, and automatic storage durations are associated
- with objects introduced by declarations [...].
+ Thread, static, and automatic storage durations are
+ associated with objects introduced by declarations [...].
- Add '__thread' to the list of specifiers in paragraph 3.
+ Add `__thread' to the list of specifiers in paragraph 3.
* [basic.stc.thread]
New section before [basic.stc.static]
- The keyword '__thread' applied to a non-local object gives the
+ The keyword `__thread' applied to a non-local object gives the
object thread storage duration.
- A local variable or class data member declared both 'static'
- and '__thread' gives the variable or member thread storage
+ A local variable or class data member declared both `static'
+ and `__thread' gives the variable or member thread storage
duration.
* [basic.stc.static]
@@ -41478,35 +41912,35 @@ that document the exact semantics of the language extension.
* [dcl.stc]
- Add '__thread' to the list in paragraph 1.
+ Add `__thread' to the list in paragraph 1.
Change paragraph 1
- With the exception of '__thread', at most one
+ With the exception of `__thread', at most one
STORAGE-CLASS-SPECIFIER shall appear in a given
- DECL-SPECIFIER-SEQ. The '__thread' specifier may be used
- alone, or immediately following the 'extern' or 'static'
+ DECL-SPECIFIER-SEQ. The `__thread' specifier may be used
+ alone, or immediately following the `extern' or `static'
specifiers. [...]
Add after paragraph 5
- The '__thread' specifier can be applied only to the names of
+ The `__thread' specifier can be applied only to the names of
objects and to anonymous unions.
* [class.mem]
Add after paragraph 6
- Non-'static' members shall not be '__thread'.
+ Non-`static' members shall not be `__thread'.

File: gcc.info, Node: Binary constants, Prev: Thread-Local, Up: C Extensions
-6.63 Binary Constants using the '0b' Prefix
+6.63 Binary Constants using the `0b' Prefix
===========================================
Integer constants can be written as binary constants, consisting of a
-sequence of '0' and '1' digits, prefixed by '0b' or '0B'. This is
+sequence of `0' and `1' digits, prefixed by `0b' or `0B'. This is
particularly useful in environments that operate a lot on the bit level
(like microcontrollers).
@@ -41518,7 +41952,7 @@ particularly useful in environments that operate a lot on the bit level
i = 0b101010;
The type of these constants follows the same rules as for octal or
-hexadecimal integer constants, so suffixes like 'L' or 'UL' can be
+hexadecimal integer constants, so suffixes like `L' or `UL' can be
applied.

@@ -41531,8 +41965,8 @@ The GNU compiler provides these extensions to the C++ language (and you
can also use most of the C language extensions in your C++ programs).
If you want to write code that checks whether these features are
available, you can test for the GNU compiler the same way as for C
-programs: check for a predefined macro '__GNUC__'. You can also use
-'__GNUG__' to test specifically for GNU C++ (*note Predefined Macros:
+programs: check for a predefined macro `__GNUC__'. You can also use
+`__GNUG__' to test specifically for GNU C++ (*note Predefined Macros:
(cpp)Common Predefined Macros.).
* Menu:
@@ -41545,7 +41979,7 @@ programs: check for a predefined macro '__GNUC__'. You can also use
* Template Instantiation:: Methods for ensuring that exactly one copy of
each needed template instantiation is emitted.
* Bound member functions:: You can extract a function pointer to the
- method denoted by a '->*' or '.*' expression.
+ method denoted by a `->*' or `.*' expression.
* C++ Attributes:: Variable, function, and type attributes for C++ only.
* Function Multiversioning:: Declaring multiple function versions.
* Namespace Association:: Strong using-directives for namespace association.
@@ -41568,8 +42002,8 @@ lvalueness of expressions between C and C++ complicate the behavior.
G++ behaves the same as GCC for volatile access, *Note Volatiles: C
Extensions, for a description of GCC's behavior.
- The C and C++ language specifications differ when an object is accessed
-in a void context:
+ The C and C++ language specifications differ when an object is
+accessed in a void context:
volatile int *src = SOMEVALUE;
*src;
@@ -41611,9 +42045,9 @@ File: gcc.info, Node: Restricted Pointers, Next: Vague Linkage, Prev: C++ Vol
================================
As with the C front end, G++ understands the C99 feature of restricted
-pointers, specified with the '__restrict__', or '__restrict' type
-qualifier. Because you cannot compile C++ by specifying the '-std=c99'
-language flag, 'restrict' is not a keyword in C++.
+pointers, specified with the `__restrict__', or `__restrict' type
+qualifier. Because you cannot compile C++ by specifying the `-std=c99'
+language flag, `restrict' is not a keyword in C++.
In addition to allowing restricted pointers, you can specify restricted
references, which indicate that the reference is not aliased in the
@@ -41624,27 +42058,27 @@ local context.
/* ... */
}
-In the body of 'fn', RPTR points to an unaliased integer and RREF refers
-to a (different) unaliased integer.
+In the body of `fn', RPTR points to an unaliased integer and RREF
+refers to a (different) unaliased integer.
You may also specify whether a member function's THIS pointer is
-unaliased by using '__restrict__' as a member function qualifier.
+unaliased by using `__restrict__' as a member function qualifier.
void T::fn () __restrict__
{
/* ... */
}
-Within the body of 'T::fn', THIS has the effective definition 'T
+Within the body of `T::fn', THIS has the effective definition `T
*__restrict__ const this'. Notice that the interpretation of a
-'__restrict__' member function qualifier is different to that of 'const'
-or 'volatile' qualifier, in that it is applied to the pointer rather
-than the object. This is consistent with other compilers that implement
-restricted pointers.
+`__restrict__' member function qualifier is different to that of
+`const' or `volatile' qualifier, in that it is applied to the pointer
+rather than the object. This is consistent with other compilers that
+implement restricted pointers.
- As with all outermost parameter qualifiers, '__restrict__' is ignored
+ As with all outermost parameter qualifiers, `__restrict__' is ignored
in function definition matching. This means you only need to specify
-'__restrict__' in a function definition, rather than in a function
+`__restrict__' in a function definition, rather than in a function
prototype as well.

@@ -41662,16 +42096,16 @@ clever.
Inline Functions
Inline functions are typically defined in a header file which can
be included in many different compilations. Hopefully they can
- usually be inlined, but sometimes an out-of-line copy is necessary,
- if the address of the function is taken or if inlining fails. In
- general, we emit an out-of-line copy in all translation units where
- one is needed. As an exception, we only emit inline virtual
- functions with the vtable, since it always requires a copy.
+ usually be inlined, but sometimes an out-of-line copy is
+ necessary, if the address of the function is taken or if inlining
+ fails. In general, we emit an out-of-line copy in all translation
+ units where one is needed. As an exception, we only emit inline
+ virtual functions with the vtable, since it always requires a copy.
Local static variables and string constants used in an inline
- function are also considered to have vague linkage, since they must
- be shared between all inlined and out-of-line instances of the
- function.
+ function are also considered to have vague linkage, since they
+ must be shared between all inlined and out-of-line instances of
+ the function.
VTables
C++ virtual functions are implemented in most compilers using a
@@ -41688,21 +42122,22 @@ VTables
Make sure that any inline virtuals are declared inline in the class
body, even if they are not defined there.
-'type_info' objects
+`type_info' objects
C++ requires information about types to be written out in order to
- implement 'dynamic_cast', 'typeid' and exception handling. For
+ implement `dynamic_cast', `typeid' and exception handling. For
polymorphic classes (classes with virtual functions), the
- 'type_info' object is written out along with the vtable so that
- 'dynamic_cast' can determine the dynamic type of a class object at
- run time. For all other types, we write out the 'type_info' object
- when it is used: when applying 'typeid' to an expression, throwing
- an object, or referring to a type in a catch clause or exception
- specification.
+ `type_info' object is written out along with the vtable so that
+ `dynamic_cast' can determine the dynamic type of a class object at
+ run time. For all other types, we write out the `type_info'
+ object when it is used: when applying `typeid' to an expression,
+ throwing an object, or referring to a type in a catch clause or
+ exception specification.
Template Instantiations
Most everything in this section also applies to template
- instantiations, but there are other options as well. *Note Where's
- the Template?: Template Instantiation.
+ instantiations, but there are other options as well. *Note
+ Where's the Template?: Template Instantiation.
+
When used with GNU ld version 2.8 or later on an ELF system such as
GNU/Linux or Solaris 2, or on Microsoft Windows, duplicate copies of
@@ -41728,78 +42163,78 @@ File: gcc.info, Node: C++ Interface, Next: Template Instantiation, Prev: Vagu
7.4 C++ Interface and Implementation Pragmas
============================================
-'#pragma interface' and '#pragma implementation' provide the user with a
-way of explicitly directing the compiler to emit entities with vague
+`#pragma interface' and `#pragma implementation' provide the user with
+a way of explicitly directing the compiler to emit entities with vague
linkage (and debugging information) in a particular translation unit.
- _Note:_ These '#pragma's have been superceded as of GCC 2.7.2 by COMDAT
-support and the "key method" heuristic mentioned in *note Vague
+ _Note:_ These `#pragma's have been superceded as of GCC 2.7.2 by
+COMDAT support and the "key method" heuristic mentioned in *note Vague
Linkage::. Using them can actually cause your program to grow due to
unnecessary out-of-line copies of inline functions.
-'#pragma interface'
-'#pragma interface "SUBDIR/OBJECTS.h"'
- Use this directive in _header files_ that define object classes, to
- save space in most of the object files that use those classes.
+`#pragma interface'
+`#pragma interface "SUBDIR/OBJECTS.h"'
+ Use this directive in _header files_ that define object classes,
+ to save space in most of the object files that use those classes.
Normally, local copies of certain information (backup copies of
inline member functions, debugging information, and the internal
tables that implement virtual functions) must be kept in each
object file that includes class definitions. You can use this
pragma to avoid such duplication. When a header file containing
- '#pragma interface' is included in a compilation, this auxiliary
+ `#pragma interface' is included in a compilation, this auxiliary
information is not generated (unless the main input source file
- itself uses '#pragma implementation'). Instead, the object files
+ itself uses `#pragma implementation'). Instead, the object files
contain references to be resolved at link time.
The second form of this directive is useful for the case where you
have multiple headers with the same name in different directories.
- If you use this form, you must specify the same string to '#pragma
+ If you use this form, you must specify the same string to `#pragma
implementation'.
-'#pragma implementation'
-'#pragma implementation "OBJECTS.h"'
+`#pragma implementation'
+`#pragma implementation "OBJECTS.h"'
Use this pragma in a _main input file_, when you want full output
from included header files to be generated (and made globally
- visible). The included header file, in turn, should use '#pragma
+ visible). The included header file, in turn, should use `#pragma
interface'. Backup copies of inline member functions, debugging
information, and the internal tables used to implement virtual
functions are all generated in implementation files.
- If you use '#pragma implementation' with no argument, it applies to
- an include file with the same basename(1) as your source file. For
- example, in 'allclass.cc', giving just '#pragma implementation' by
- itself is equivalent to '#pragma implementation "allclass.h"'.
+ If you use `#pragma implementation' with no argument, it applies to
+ an include file with the same basename(1) as your source file.
+ For example, in `allclass.cc', giving just `#pragma implementation'
+ by itself is equivalent to `#pragma implementation "allclass.h"'.
Use the string argument if you want a single implementation file to
include code from multiple header files. (You must also use
- '#include' to include the header file; '#pragma implementation'
+ `#include' to include the header file; `#pragma implementation'
only specifies how to use the file--it doesn't actually include
it.)
There is no way to split up the contents of a single header file
into multiple implementation files.
- '#pragma implementation' and '#pragma interface' also have an effect on
-function inlining.
+ `#pragma implementation' and `#pragma interface' also have an effect
+on function inlining.
- If you define a class in a header file marked with '#pragma interface',
-the effect on an inline function defined in that class is similar to an
-explicit 'extern' declaration--the compiler emits no code at all to
-define an independent version of the function. Its definition is used
-only for inlining with its callers.
+ If you define a class in a header file marked with `#pragma
+interface', the effect on an inline function defined in that class is
+similar to an explicit `extern' declaration--the compiler emits no code
+at all to define an independent version of the function. Its
+definition is used only for inlining with its callers.
Conversely, when you include the same header file in a main source file
-that declares it as '#pragma implementation', the compiler emits code
-for the function itself; this defines a version of the function that can
-be found via pointers (or by callers compiled without inlining). If all
-calls to the function can be inlined, you can avoid emitting the
-function by compiling with '-fno-implement-inlines'. If any calls are
+that declares it as `#pragma implementation', the compiler emits code
+for the function itself; this defines a version of the function that
+can be found via pointers (or by callers compiled without inlining).
+If all calls to the function can be inlined, you can avoid emitting the
+function by compiling with `-fno-implement-inlines'. If any calls are
not inlined, you will get linker errors.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) A file's "basename" is the name stripped of all leading path
-information and of trailing suffixes, such as '.h' or '.C' or '.cc'.
+ (1) A file's "basename" is the name stripped of all leading path
+information and of trailing suffixes, such as `.h' or `.C' or `.cc'.

File: gcc.info, Node: Template Instantiation, Next: Bound member functions, Prev: C++ Interface, Up: C++ Extensions
@@ -41816,8 +42251,8 @@ problem, which are referred to as the Borland model and the Cfront
model.
Borland model
- Borland C++ solved the template instantiation problem by adding the
- code equivalent of common blocks to their linker; the compiler
+ Borland C++ solved the template instantiation problem by adding
+ the code equivalent of common blocks to their linker; the compiler
emits template instances in each translation unit that uses them,
and the linker collapses them together. The advantage of this
model is that the linker only has to consider the object files
@@ -41830,22 +42265,22 @@ Borland model
Cfront model
The AT&T C++ translator, Cfront, solved the template instantiation
problem by creating the notion of a template repository, an
- automatically maintained place where template instances are stored.
- A more modern version of the repository works as follows: As
- individual object files are built, the compiler places any template
- definitions and instantiations encountered in the repository. At
- link time, the link wrapper adds in the objects in the repository
- and compiles any needed instances that were not previously emitted.
- The advantages of this model are more optimal compilation speed and
- the ability to use the system linker; to implement the Borland
- model a compiler vendor also needs to replace the linker. The
- disadvantages are vastly increased complexity, and thus potential
- for error; for some code this can be just as transparent, but in
- practice it can been very difficult to build multiple programs in
- one directory and one program in multiple directories. Code
- written for this model tends to separate definitions of non-inline
- member templates into a separate file, which should be compiled
- separately.
+ automatically maintained place where template instances are
+ stored. A more modern version of the repository works as follows:
+ As individual object files are built, the compiler places any
+ template definitions and instantiations encountered in the
+ repository. At link time, the link wrapper adds in the objects in
+ the repository and compiles any needed instances that were not
+ previously emitted. The advantages of this model are more optimal
+ compilation speed and the ability to use the system linker; to
+ implement the Borland model a compiler vendor also needs to
+ replace the linker. The disadvantages are vastly increased
+ complexity, and thus potential for error; for some code this can be
+ just as transparent, but in practice it can been very difficult to
+ build multiple programs in one directory and one program in
+ multiple directories. Code written for this model tends to
+ separate definitions of non-inline member templates into a
+ separate file, which should be compiled separately.
When used with GNU ld version 2.8 or later on an ELF system such as
GNU/Linux or Solaris 2, or on Microsoft Windows, G++ supports the
@@ -41855,31 +42290,31 @@ model.
You have the following options for dealing with template
instantiations:
- 1. Compile your template-using code with '-frepo'. The compiler
- generates files with the extension '.rpo' listing all of the
+ 1. Compile your template-using code with `-frepo'. The compiler
+ generates files with the extension `.rpo' listing all of the
template instantiations used in the corresponding object files that
- could be instantiated there; the link wrapper, 'collect2', then
- updates the '.rpo' files to tell the compiler where to place those
+ could be instantiated there; the link wrapper, `collect2', then
+ updates the `.rpo' files to tell the compiler where to place those
instantiations and rebuild any affected object files. The
link-time overhead is negligible after the first pass, as the
compiler continues to place the instantiations in the same files.
This is your best option for application code written for the
Borland model, as it just works. Code written for the Cfront model
- needs to be modified so that the template definitions are available
- at one or more points of instantiation; usually this is as simple
- as adding '#include <tmethods.cc>' to the end of each template
- header.
+ needs to be modified so that the template definitions are
+ available at one or more points of instantiation; usually this is
+ as simple as adding `#include <tmethods.cc>' to the end of each
+ template header.
For library code, if you want the library to provide all of the
template instantiations it needs, just try to link all of its
object files together; the link will fail, but cause the
instantiations to be generated as a side effect. Be warned,
- however, that this may cause conflicts if multiple libraries try to
- provide the same instantiations. For greater control, use explicit
- instantiation as described in the next option.
+ however, that this may cause conflicts if multiple libraries try
+ to provide the same instantiations. For greater control, use
+ explicit instantiation as described in the next option.
- 2. Compile your code with '-fno-implicit-templates' to disable the
+ 2. Compile your code with `-fno-implicit-templates' to disable the
implicit generation of template instances, and explicitly
instantiate all the ones you use. This approach requires more
knowledge of exactly which instances you need than do the others,
@@ -41887,8 +42322,8 @@ instantiations:
scatter the explicit instantiations throughout your program,
perhaps putting them in the translation units where the instances
are used or the translation units that define the templates
- themselves; you can put all of the explicit instantiations you need
- into one big file; or you can create small files like
+ themselves; you can put all of the explicit instantiations you
+ need into one big file; or you can create small files like
#include "Foo.h"
#include "Foo.cc"
@@ -41901,22 +42336,22 @@ instantiations:
instantiation library from those.
If you are using Cfront-model code, you can probably get away with
- not using '-fno-implicit-templates' when compiling files that don't
- '#include' the member template definitions.
+ not using `-fno-implicit-templates' when compiling files that don't
+ `#include' the member template definitions.
If you use one big file to do the instantiations, you may want to
- compile it without '-fno-implicit-templates' so you get all of the
+ compile it without `-fno-implicit-templates' so you get all of the
instances required by your explicit instantiations (but not by any
other files) without having to specify them as well.
The ISO C++ 2011 standard allows forward declaration of explicit
- instantiations (with 'extern'). G++ supports explicit
- instantiation declarations in C++98 mode and has extended the
- template instantiation syntax to support instantiation of the
- compiler support data for a template class (i.e. the vtable)
- without instantiating any of its members (with 'inline'), and
+ instantiations (with `extern'). G++ supports explicit instantiation
+ declarations in C++98 mode and has extended the template
+ instantiation syntax to support instantiation of the compiler
+ support data for a template class (i.e. the vtable) without
+ instantiating any of its members (with `inline'), and
instantiation of only the static data members of a template class,
- without the support data or member functions (with 'static'):
+ without the support data or member functions (with `static'):
extern template int max (int, int);
inline template class Foo<int>;
@@ -41936,7 +42371,7 @@ File: gcc.info, Node: Bound member functions, Next: C++ Attributes, Prev: Tem
In C++, pointer to member functions (PMFs) are implemented using a wide
pointer of sorts to handle all the possible call mechanisms; the PMF
-needs to store information about how to adjust the 'this' pointer, and
+needs to store information about how to adjust the `this' pointer, and
if the function pointed to is virtual, where to find the vtable, and
where in the vtable to look for the member function. If you are using
PMFs in an inner loop, you should really reconsider that decision. If
@@ -41957,13 +42392,13 @@ function calls.
fptr p = (fptr)(a.*fp);
- For PMF constants (i.e. expressions of the form '&Klasse::Member'), no
+ For PMF constants (i.e. expressions of the form `&Klasse::Member'), no
object is needed to obtain the address of the function. They can be
converted to function pointers directly:
fptr p1 = (fptr)(&A::foo);
- You must specify '-Wno-pmf-conversions' to use this extension.
+ You must specify `-Wno-pmf-conversions' to use this extension.

File: gcc.info, Node: C++ Attributes, Next: Function Multiversioning, Prev: Bound member functions, Up: C++ Extensions
@@ -41973,17 +42408,17 @@ File: gcc.info, Node: C++ Attributes, Next: Function Multiversioning, Prev: B
Some attributes only make sense for C++ programs.
-'abi_tag ("TAG", ...)'
- The 'abi_tag' attribute can be applied to a function, variable, or
+`abi_tag ("TAG", ...)'
+ The `abi_tag' attribute can be applied to a function, variable, or
class declaration. It modifies the mangled name of the entity to
incorporate the tag name, in order to distinguish the function or
class from an earlier version with a different ABI; perhaps the
- class has changed size, or the function has a different return type
- that is not encoded in the mangled name.
+ class has changed size, or the function has a different return
+ type that is not encoded in the mangled name.
The attribute can also be applied to an inline namespace, but does
not affect the mangled name of the namespace; in this case it is
- only used for '-Wabi-tag' warnings and automatic tagging of
+ only used for `-Wabi-tag' warnings and automatic tagging of
functions and variables. Tagging inline namespaces is generally
preferable to tagging individual declarations, but the latter is
sometimes necessary, such as when only certain members of a class
@@ -41993,41 +42428,40 @@ Some attributes only make sense for C++ programs.
strings are sorted on output, so the order of the list is
unimportant.
- A redeclaration of an entity must not add new ABI tags, since doing
- so would change the mangled name.
+ A redeclaration of an entity must not add new ABI tags, since
+ doing so would change the mangled name.
The ABI tags apply to a name, so all instantiations and
specializations of a template have the same tags. The attribute
will be ignored if applied to an explicit specialization or
instantiation.
- The '-Wabi-tag' flag enables a warning about a class which does not
- have all the ABI tags used by its subobjects and virtual functions;
- for users with code that needs to coexist with an earlier ABI,
- using this option can help to find all affected types that need to
- be tagged.
+ The `-Wabi-tag' flag enables a warning about a class which does
+ not have all the ABI tags used by its subobjects and virtual
+ functions; for users with code that needs to coexist with an
+ earlier ABI, using this option can help to find all affected types
+ that need to be tagged.
When a type involving an ABI tag is used as the type of a variable
or return type of a function where that tag is not already present
in the signature of the function, the tag is automatically applied
- to the variable or function. '-Wabi-tag' also warns about this
+ to the variable or function. `-Wabi-tag' also warns about this
situation; this warning can be avoided by explicitly tagging the
variable or function or moving it into a tagged inline namespace.
-'init_priority (PRIORITY)'
-
+`init_priority (PRIORITY)'
In Standard C++, objects defined at namespace scope are guaranteed
to be initialized in an order in strict accordance with that of
their definitions _in a given translation unit_. No guarantee is
made for initializations across translation units. However, GNU
C++ allows users to control the order of initialization of objects
- defined at namespace scope with the 'init_priority' attribute by
+ defined at namespace scope with the `init_priority' attribute by
specifying a relative PRIORITY, a constant integral expression
currently bounded between 101 and 65535 inclusive. Lower numbers
indicate a higher priority.
- In the following example, 'A' would normally be created before 'B',
- but the 'init_priority' attribute reverses that order:
+ In the following example, `A' would normally be created before
+ `B', but the `init_priority' attribute reverses that order:
Some_Class A __attribute__ ((init_priority (2000)));
Some_Class B __attribute__ ((init_priority (543)));
@@ -42035,29 +42469,28 @@ Some attributes only make sense for C++ programs.
Note that the particular values of PRIORITY do not matter; only
their relative ordering.
-'java_interface'
-
- This type attribute informs C++ that the class is a Java interface.
- It may only be applied to classes declared within an 'extern
- "Java"' block. Calls to methods declared in this interface are
- dispatched using GCJ's interface table mechanism, instead of
- regular virtual table dispatch.
-
-'warn_unused'
+`java_interface'
+ This type attribute informs C++ that the class is a Java
+ interface. It may only be applied to classes declared within an
+ `extern "Java"' block. Calls to methods declared in this
+ interface are dispatched using GCJ's interface table mechanism,
+ instead of regular virtual table dispatch.
+`warn_unused'
For C++ types with non-trivial constructors and/or destructors it
is impossible for the compiler to determine whether a variable of
- this type is truly unused if it is not referenced. This type
+ this type is truly unused if it is not referenced. This type
attribute informs the compiler that variables of this type should
- be warned about if they appear to be unused, just like variables of
- fundamental types.
+ be warned about if they appear to be unused, just like variables
+ of fundamental types.
This attribute is appropriate for types which just represent a
- value, such as 'std::string'; it is not appropriate for types which
- control a resource, such as 'std::mutex'.
+ value, such as `std::string'; it is not appropriate for types which
+ control a resource, such as `std::mutex'.
+
+ This attribute is also accepted in C, but it is unnecessary
+ because C does not have constructors or destructors.
- This attribute is also accepted in C, but it is unnecessary because
- C does not have constructors or destructors.
See also *note Namespace Association::.
@@ -42108,15 +42541,15 @@ the execution platform. Here is an example.
return 0;
}
- In the above example, four versions of function foo are created. The
+ In the above example, four versions of function foo are created. The
first version of foo with the target attribute "default" is the default
version. This version gets executed when no other target specific
-version qualifies for execution on a particular platform. A new version
+version qualifies for execution on a particular platform. A new version
of foo is created by using the same function signature but with a
different target string. Function foo is called or a pointer to it is
taken just like a regular function. GCC takes care of doing the
-dispatching to call the right version at runtime. Refer to the GCC wiki
-on Function Multiversioning
+dispatching to call the right version at runtime. Refer to the GCC
+wiki on Function Multiversioning
(http://gcc.gnu.org/wiki/FunctionMultiVersioning) for more details.

@@ -42129,7 +42562,7 @@ File: gcc.info, Node: Namespace Association, Next: Type Traits, Prev: Functio
inline namespaces. Users should use inline namespaces instead as this
extension will be removed in future versions of G++.
- A using-directive with '__attribute ((strong))' is stronger than a
+ A using-directive with `__attribute ((strong))' is stronger than a
normal using-directive in two ways:
* Templates from the used namespace can be specialized and explicitly
@@ -42171,132 +42604,134 @@ The C++ front end implements syntactic extensions that allow
compile-time determination of various characteristics of a type (or of a
pair of types).
-'__has_nothrow_assign (type)'
- If 'type' is const qualified or is a reference type then the trait
- is false. Otherwise if '__has_trivial_assign (type)' is true then
- the trait is true, else if 'type' is a cv class or union type with
+`__has_nothrow_assign (type)'
+ If `type' is const qualified or is a reference type then the trait
+ is false. Otherwise if `__has_trivial_assign (type)' is true then
+ the trait is true, else if `type' is a cv class or union type with
copy assignment operators that are known not to throw an exception
- then the trait is true, else it is false. Requires: 'type' shall
- be a complete type, (possibly cv-qualified) 'void', or an array of
+ then the trait is true, else it is false. Requires: `type' shall
+ be a complete type, (possibly cv-qualified) `void', or an array of
unknown bound.
-'__has_nothrow_copy (type)'
- If '__has_trivial_copy (type)' is true then the trait is true, else
- if 'type' is a cv class or union type with copy constructors that
- are known not to throw an exception then the trait is true, else it
- is false. Requires: 'type' shall be a complete type, (possibly
- cv-qualified) 'void', or an array of unknown bound.
-
-'__has_nothrow_constructor (type)'
- If '__has_trivial_constructor (type)' is true then the trait is
- true, else if 'type' is a cv class or union type (or array thereof)
- with a default constructor that is known not to throw an exception
- then the trait is true, else it is false. Requires: 'type' shall
- be a complete type, (possibly cv-qualified) 'void', or an array of
+`__has_nothrow_copy (type)'
+ If `__has_trivial_copy (type)' is true then the trait is true,
+ else if `type' is a cv class or union type with copy constructors
+ that are known not to throw an exception then the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__has_nothrow_constructor (type)'
+ If `__has_trivial_constructor (type)' is true then the trait is
+ true, else if `type' is a cv class or union type (or array
+ thereof) with a default constructor that is known not to throw an
+ exception then the trait is true, else it is false. Requires:
+ `type' shall be a complete type, (possibly cv-qualified) `void',
+ or an array of unknown bound.
+
+`__has_trivial_assign (type)'
+ If `type' is const qualified or is a reference type then the trait
+ is false. Otherwise if `__is_pod (type)' is true then the trait is
+ true, else if `type' is a cv class or union type with a trivial
+ copy assignment ([class.copy]) then the trait is true, else it is
+ false. Requires: `type' shall be a complete type, (possibly
+ cv-qualified) `void', or an array of unknown bound.
+
+`__has_trivial_copy (type)'
+ If `__is_pod (type)' is true or `type' is a reference type then
+ the trait is true, else if `type' is a cv class or union type with
+ a trivial copy constructor ([class.copy]) then the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__has_trivial_constructor (type)'
+ If `__is_pod (type)' is true then the trait is true, else if
+ `type' is a cv class or union type (or array thereof) with a
+ trivial default constructor ([class.ctor]) then the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__has_trivial_destructor (type)'
+ If `__is_pod (type)' is true or `type' is a reference type then
+ the trait is true, else if `type' is a cv class or union type (or
+ array thereof) with a trivial destructor ([class.dtor]) then the
+ trait is true, else it is false. Requires: `type' shall be a
+ complete type, (possibly cv-qualified) `void', or an array of
unknown bound.
-'__has_trivial_assign (type)'
- If 'type' is const qualified or is a reference type then the trait
- is false. Otherwise if '__is_pod (type)' is true then the trait is
- true, else if 'type' is a cv class or union type with a trivial
- copy assignment ([class.copy]) then the trait is true, else it is
- false. Requires: 'type' shall be a complete type, (possibly
- cv-qualified) 'void', or an array of unknown bound.
-
-'__has_trivial_copy (type)'
- If '__is_pod (type)' is true or 'type' is a reference type then the
- trait is true, else if 'type' is a cv class or union type with a
- trivial copy constructor ([class.copy]) then the trait is true,
- else it is false. Requires: 'type' shall be a complete type,
- (possibly cv-qualified) 'void', or an array of unknown bound.
-
-'__has_trivial_constructor (type)'
- If '__is_pod (type)' is true then the trait is true, else if 'type'
- is a cv class or union type (or array thereof) with a trivial
- default constructor ([class.ctor]) then the trait is true, else it
- is false. Requires: 'type' shall be a complete type, (possibly
- cv-qualified) 'void', or an array of unknown bound.
-
-'__has_trivial_destructor (type)'
- If '__is_pod (type)' is true or 'type' is a reference type then the
- trait is true, else if 'type' is a cv class or union type (or array
- thereof) with a trivial destructor ([class.dtor]) then the trait is
- true, else it is false. Requires: 'type' shall be a complete type,
- (possibly cv-qualified) 'void', or an array of unknown bound.
-
-'__has_virtual_destructor (type)'
- If 'type' is a class type with a virtual destructor ([class.dtor])
- then the trait is true, else it is false. Requires: 'type' shall
- be a complete type, (possibly cv-qualified) 'void', or an array of
+`__has_virtual_destructor (type)'
+ If `type' is a class type with a virtual destructor ([class.dtor])
+ then the trait is true, else it is false. Requires: `type' shall
+ be a complete type, (possibly cv-qualified) `void', or an array of
unknown bound.
-'__is_abstract (type)'
- If 'type' is an abstract class ([class.abstract]) then the trait is
- true, else it is false. Requires: 'type' shall be a complete type,
- (possibly cv-qualified) 'void', or an array of unknown bound.
+`__is_abstract (type)'
+ If `type' is an abstract class ([class.abstract]) then the trait
+ is true, else it is false. Requires: `type' shall be a complete
+ type, (possibly cv-qualified) `void', or an array of unknown bound.
-'__is_base_of (base_type, derived_type)'
- If 'base_type' is a base class of 'derived_type' ([class.derived])
+`__is_base_of (base_type, derived_type)'
+ If `base_type' is a base class of `derived_type' ([class.derived])
then the trait is true, otherwise it is false. Top-level cv
- qualifications of 'base_type' and 'derived_type' are ignored. For
- the purposes of this trait, a class type is considered is own base.
- Requires: if '__is_class (base_type)' and '__is_class
- (derived_type)' are true and 'base_type' and 'derived_type' are not
- the same type (disregarding cv-qualifiers), 'derived_type' shall be
- a complete type. Diagnostic is produced if this requirement is not
- met.
-
-'__is_class (type)'
- If 'type' is a cv class type, and not a union type
+ qualifications of `base_type' and `derived_type' are ignored. For
+ the purposes of this trait, a class type is considered is own
+ base. Requires: if `__is_class (base_type)' and `__is_class
+ (derived_type)' are true and `base_type' and `derived_type' are
+ not the same type (disregarding cv-qualifiers), `derived_type'
+ shall be a complete type. Diagnostic is produced if this
+ requirement is not met.
+
+`__is_class (type)'
+ If `type' is a cv class type, and not a union type
([basic.compound]) the trait is true, else it is false.
-'__is_empty (type)'
- If '__is_class (type)' is false then the trait is false. Otherwise
- 'type' is considered empty if and only if: 'type' has no non-static
- data members, or all non-static data members, if any, are
- bit-fields of length 0, and 'type' has no virtual members, and
- 'type' has no virtual base classes, and 'type' has no base classes
- 'base_type' for which '__is_empty (base_type)' is false. Requires:
- 'type' shall be a complete type, (possibly cv-qualified) 'void', or
- an array of unknown bound.
-
-'__is_enum (type)'
- If 'type' is a cv enumeration type ([basic.compound]) the trait is
+`__is_empty (type)'
+ If `__is_class (type)' is false then the trait is false.
+ Otherwise `type' is considered empty if and only if: `type' has no
+ non-static data members, or all non-static data members, if any,
+ are bit-fields of length 0, and `type' has no virtual members, and
+ `type' has no virtual base classes, and `type' has no base classes
+ `base_type' for which `__is_empty (base_type)' is false.
+ Requires: `type' shall be a complete type, (possibly cv-qualified)
+ `void', or an array of unknown bound.
+
+`__is_enum (type)'
+ If `type' is a cv enumeration type ([basic.compound]) the trait is
true, else it is false.
-'__is_literal_type (type)'
- If 'type' is a literal type ([basic.types]) the trait is true, else
- it is false. Requires: 'type' shall be a complete type, (possibly
- cv-qualified) 'void', or an array of unknown bound.
-
-'__is_pod (type)'
- If 'type' is a cv POD type ([basic.types]) then the trait is true,
- else it is false. Requires: 'type' shall be a complete type,
- (possibly cv-qualified) 'void', or an array of unknown bound.
-
-'__is_polymorphic (type)'
- If 'type' is a polymorphic class ([class.virtual]) then the trait
- is true, else it is false. Requires: 'type' shall be a complete
- type, (possibly cv-qualified) 'void', or an array of unknown bound.
-
-'__is_standard_layout (type)'
- If 'type' is a standard-layout type ([basic.types]) the trait is
- true, else it is false. Requires: 'type' shall be a complete type,
- (possibly cv-qualified) 'void', or an array of unknown bound.
-
-'__is_trivial (type)'
- If 'type' is a trivial type ([basic.types]) the trait is true, else
- it is false. Requires: 'type' shall be a complete type, (possibly
- cv-qualified) 'void', or an array of unknown bound.
-
-'__is_union (type)'
- If 'type' is a cv union type ([basic.compound]) the trait is true,
+`__is_literal_type (type)'
+ If `type' is a literal type ([basic.types]) the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__is_pod (type)'
+ If `type' is a cv POD type ([basic.types]) then the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__is_polymorphic (type)'
+ If `type' is a polymorphic class ([class.virtual]) then the trait
+ is true, else it is false. Requires: `type' shall be a complete
+ type, (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__is_standard_layout (type)'
+ If `type' is a standard-layout type ([basic.types]) the trait is
+ true, else it is false. Requires: `type' shall be a complete
+ type, (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__is_trivial (type)'
+ If `type' is a trivial type ([basic.types]) the trait is true,
+ else it is false. Requires: `type' shall be a complete type,
+ (possibly cv-qualified) `void', or an array of unknown bound.
+
+`__is_union (type)'
+ If `type' is a cv union type ([basic.compound]) the trait is true,
else it is false.
-'__underlying_type (type)'
- The underlying type of 'type'. Requires: 'type' shall be an
+`__underlying_type (type)'
+ The underlying type of `type'. Requires: `type' shall be an
enumeration type ([dcl.enum]).
+

File: gcc.info, Node: Java Exceptions, Next: Deprecated Features, Prev: Type Traits, Up: C++ Extensions
@@ -42319,11 +42754,11 @@ problematic code is:
}
The usual effect of an incorrect guess is a link failure, complaining of
-a missing routine called '__gxx_personality_v0'.
+a missing routine called `__gxx_personality_v0'.
You can inform the compiler that Java exceptions are to be used in a
translation unit, irrespective of what it might think, by writing
-'#pragma GCC java_exceptions' at the head of the file. This '#pragma'
+`#pragma GCC java_exceptions' at the head of the file. This `#pragma'
must appear before any functions that throw or catch exceptions, or run
destructors when exceptions are thrown through them.
@@ -42348,31 +42783,31 @@ cases, the feature might be gone already.
While the list below is not exhaustive, it documents some of the
options that are now deprecated:
-'-fexternal-templates'
-'-falt-external-templates'
+`-fexternal-templates'
+`-falt-external-templates'
These are two of the many ways for G++ to implement template
instantiation. *Note Template Instantiation::. The C++ standard
clearly defines how template definitions have to be organized
across implementation units. G++ has an implicit instantiation
mechanism that should work just fine for standard-conforming code.
-'-fstrict-prototype'
-'-fno-strict-prototype'
- Previously it was possible to use an empty prototype parameter list
- to indicate an unspecified number of parameters (like C), rather
- than no parameters, as C++ demands. This feature has been removed,
- except where it is required for backwards compatibility. *Note
- Backwards Compatibility::.
-
- G++ allows a virtual function returning 'void *' to be overridden by
-one returning a different pointer type. This extension to the covariant
-return type rules is now deprecated and will be removed from a future
-version.
-
- The G++ minimum and maximum operators ('<?' and '>?') and their
-compound forms ('<?=') and '>?=') have been deprecated and are now
+`-fstrict-prototype'
+`-fno-strict-prototype'
+ Previously it was possible to use an empty prototype parameter
+ list to indicate an unspecified number of parameters (like C),
+ rather than no parameters, as C++ demands. This feature has been
+ removed, except where it is required for backwards compatibility.
+ *Note Backwards Compatibility::.
+
+ G++ allows a virtual function returning `void *' to be overridden by
+one returning a different pointer type. This extension to the
+covariant return type rules is now deprecated and will be removed from a
+future version.
+
+ The G++ minimum and maximum operators (`<?' and `>?') and their
+compound forms (`<?=') and `>?=') have been deprecated and are now
removed from G++. Code using these operators should be modified to use
-'std::min' and 'std::max' instead.
+`std::min' and `std::max' instead.
The named return value extension has been deprecated, and is now
removed from G++.
@@ -42391,11 +42826,11 @@ and other places where they are not permitted by the standard is
deprecated and will be removed from a future version of G++.
G++ allows floating-point literals to appear in integral constant
-expressions, e.g. ' enum E { e = int(2.2 * 3.7) } ' This extension is
+expressions, e.g. ` enum E { e = int(2.2 * 3.7) } ' This extension is
deprecated and will be removed from a future version.
G++ allows static data members of const floating-point type to be
-declared with an initializer in a class definition. The standard only
+declared with an initializer in a class definition. The standard only
allows initializers for static members of const integral types and const
enumeration types so this extension has been deprecated and will be
removed from a future version.
@@ -42412,20 +42847,21 @@ used to be acceptable in previous drafts of the standard, such as the
ARM [Annotated C++ Reference Manual], are no longer accepted. In order
to allow compilation of C++ written to such drafts, G++ contains some
backwards compatibilities. _All such backwards compatibility features
-are liable to disappear in future versions of G++._ They should be
-considered deprecated. *Note Deprecated Features::.
+are liable to disappear in future versions of G++._ They should be
+considered deprecated. *Note Deprecated Features::.
-'For scope'
+`For scope'
If a variable is declared at for scope, it used to remain in scope
- until the end of the scope that contained the for statement (rather
- than just within the for scope). G++ retains this, but issues a
- warning, if such a variable is accessed outside the for scope.
+ until the end of the scope that contained the for statement
+ (rather than just within the for scope). G++ retains this, but
+ issues a warning, if such a variable is accessed outside the for
+ scope.
-'Implicit C language'
- Old C system header files did not contain an 'extern "C" {...}'
+`Implicit C language'
+ Old C system header files did not contain an `extern "C" {...}'
scope to set the language. On such systems, all header files are
implicitly scoped inside a C language scope. Also, an empty
- prototype '()' is treated as an unspecified number of arguments,
+ prototype `()' is treated as an unspecified number of arguments,
rather than no arguments, as C++ demands.

@@ -42434,9 +42870,9 @@ File: gcc.info, Node: Objective-C, Next: Compatibility, Prev: C++ Extensions,
8 GNU Objective-C Features
**************************
-This document is meant to describe some of the GNU Objective-C features.
-It is not intended to teach you Objective-C. There are several resources
-on the Internet that present the language.
+This document is meant to describe some of the GNU Objective-C
+features. It is not intended to teach you Objective-C. There are
+several resources on the Internet that present the language.
* Menu:
@@ -42460,8 +42896,8 @@ File: gcc.info, Node: GNU Objective-C runtime API, Next: Executing code before
This section is specific for the GNU Objective-C runtime. If you are
using a different runtime, you can skip it.
- The GNU Objective-C runtime provides an API that allows you to interact
-with the Objective-C runtime system, querying the live runtime
+ The GNU Objective-C runtime provides an API that allows you to
+interact with the Objective-C runtime system, querying the live runtime
structures and even manipulating them. This allows you for example to
inspect and navigate classes, methods and protocols; to define new
classes or new methods, and even to modify existing classes or
@@ -42488,42 +42924,43 @@ provided by the "Objective-C 2.0" Apple/NeXT Objective-C runtime. The
API is documented in the public header files of the GNU Objective-C
runtime:
- * 'objc/objc.h': this is the basic Objective-C header file, defining
- the basic Objective-C types such as 'id', 'Class' and 'BOOL'. You
+ * `objc/objc.h': this is the basic Objective-C header file, defining
+ the basic Objective-C types such as `id', `Class' and `BOOL'. You
have to include this header to do almost anything with Objective-C.
- * 'objc/runtime.h': this header declares most of the public runtime
+ * `objc/runtime.h': this header declares most of the public runtime
API functions allowing you to inspect and manipulate the
Objective-C runtime data structures. These functions are fairly
standardized across Objective-C runtimes and are almost identical
to the Apple/NeXT Objective-C runtime ones. It does not declare
functions in some specialized areas (constructing and forwarding
message invocations, threading) which are in the other headers
- below. You have to include 'objc/objc.h' and 'objc/runtime.h' to
- use any of the functions, such as 'class_getName()', declared in
- 'objc/runtime.h'.
+ below. You have to include `objc/objc.h' and `objc/runtime.h' to
+ use any of the functions, such as `class_getName()', declared in
+ `objc/runtime.h'.
- * 'objc/message.h': this header declares public functions used to
+ * `objc/message.h': this header declares public functions used to
construct, deconstruct and forward message invocations. Because
messaging is done in quite a different way on different runtimes,
functions in this header are specific to the GNU Objective-C
runtime implementation.
- * 'objc/objc-exception.h': this header declares some public functions
- related to Objective-C exceptions. For example functions in this
- header allow you to throw an Objective-C exception from plain C/C++
- code.
+ * `objc/objc-exception.h': this header declares some public
+ functions related to Objective-C exceptions. For example
+ functions in this header allow you to throw an Objective-C
+ exception from plain C/C++ code.
- * 'objc/objc-sync.h': this header declares some public functions
- related to the Objective-C '@synchronized()' syntax, allowing you
- to emulate an Objective-C '@synchronized()' block in plain C/C++
+ * `objc/objc-sync.h': this header declares some public functions
+ related to the Objective-C `@synchronized()' syntax, allowing you
+ to emulate an Objective-C `@synchronized()' block in plain C/C++
code.
- * 'objc/thr.h': this header declares a public runtime API threading
+ * `objc/thr.h': this header declares a public runtime API threading
layer that is only provided by the GNU Objective-C runtime. It
- declares functions such as 'objc_mutex_lock()', which provide a
+ declares functions such as `objc_mutex_lock()', which provide a
platform-independent set of threading functions.
+
The header files contain detailed documentation for each function in
the GNU Objective-C runtime API.
@@ -42534,11 +42971,12 @@ File: gcc.info, Node: Traditional GNU Objective-C runtime API, Prev: Modern GN
---------------------------------------------
The GNU Objective-C runtime used to provide a different API, which we
-call the "traditional" GNU Objective-C runtime API. Functions belonging
-to this API are easy to recognize because they use a different naming
-convention, such as 'class_get_super_class()' (traditional API) instead
-of 'class_getSuperclass()' (modern API). Software using this API
-includes the file 'objc/objc-api.h' where it is declared.
+call the "traditional" GNU Objective-C runtime API. Functions
+belonging to this API are easy to recognize because they use a
+different naming convention, such as `class_get_super_class()'
+(traditional API) instead of `class_getSuperclass()' (modern API).
+Software using this API includes the file `objc/objc-api.h' where it is
+declared.
Starting with GCC 4.7.0, the traditional GNU runtime API is no longer
available.
@@ -42546,26 +42984,26 @@ available.

File: gcc.info, Node: Executing code before main, Next: Type encoding, Prev: GNU Objective-C runtime API, Up: Objective-C
-8.2 '+load': Executing Code before 'main'
+8.2 `+load': Executing Code before `main'
=========================================
This section is specific for the GNU Objective-C runtime. If you are
using a different runtime, you can skip it.
The GNU Objective-C runtime provides a way that allows you to execute
-code before the execution of the program enters the 'main' function.
+code before the execution of the program enters the `main' function.
The code is executed on a per-class and a per-category basis, through a
-special class method '+load'.
+special class method `+load'.
This facility is very useful if you want to initialize global variables
which can be accessed by the program directly, without sending a message
to the class first. The usual way to initialize global variables, in
-the '+initialize' method, might not be useful because '+initialize' is
+the `+initialize' method, might not be useful because `+initialize' is
only called when the first message is sent to a class object, which in
some cases could be too late.
- Suppose for example you have a 'FileStream' class that declares
-'Stdin', 'Stdout' and 'Stderr' as global variables, like below:
+ Suppose for example you have a `FileStream' class that declares
+`Stdin', `Stdout' and `Stderr' as global variables, like below:
FileStream *Stdin = nil;
@@ -42584,17 +43022,16 @@ some cases could be too late.
/* Other methods here */
@end
+ In this example, the initialization of `Stdin', `Stdout' and `Stderr'
+in `+initialize' occurs too late. The programmer can send a message to
+one of these objects before the variables are actually initialized,
+thus sending messages to the `nil' object. The `+initialize' method
+which actually initializes the global variables is not invoked until
+the first message is sent to the class object. The solution would
+require these variables to be initialized just before entering `main'.
- In this example, the initialization of 'Stdin', 'Stdout' and 'Stderr'
-in '+initialize' occurs too late. The programmer can send a message to
-one of these objects before the variables are actually initialized, thus
-sending messages to the 'nil' object. The '+initialize' method which
-actually initializes the global variables is not invoked until the first
-message is sent to the class object. The solution would require these
-variables to be initialized just before entering 'main'.
-
- The correct solution of the above problem is to use the '+load' method
-instead of '+initialize':
+ The correct solution of the above problem is to use the `+load' method
+instead of `+initialize':
@implementation FileStream
@@ -42609,15 +43046,14 @@ instead of '+initialize':
/* Other methods here */
@end
-
- The '+load' is a method that is not overridden by categories. If a
-class and a category of it both implement '+load', both methods are
+ The `+load' is a method that is not overridden by categories. If a
+class and a category of it both implement `+load', both methods are
invoked. This allows some additional initializations to be performed in
a category.
- This mechanism is not intended to be a replacement for '+initialize'.
-You should be aware of its limitations when you decide to use it instead
-of '+initialize'.
+ This mechanism is not intended to be a replacement for `+initialize'.
+You should be aware of its limitations when you decide to use it
+instead of `+initialize'.
* Menu:
@@ -42626,15 +43062,15 @@ of '+initialize'.

File: gcc.info, Node: What you can and what you cannot do in +load, Up: Executing code before main
-8.2.1 What You Can and Cannot Do in '+load'
+8.2.1 What You Can and Cannot Do in `+load'
-------------------------------------------
-'+load' is to be used only as a last resort. Because it is executed
+`+load' is to be used only as a last resort. Because it is executed
very early, most of the Objective-C runtime machinery will not be ready
-when '+load' is executed; hence '+load' works best for executing C code
+when `+load' is executed; hence `+load' works best for executing C code
that is independent on the Objective-C runtime.
- The '+load' implementation in the GNU runtime guarantees you the
+ The `+load' implementation in the GNU runtime guarantees you the
following things:
* you can write whatever C code you like;
@@ -42642,11 +43078,12 @@ following things:
* you can allocate and send messages to objects whose class is
implemented in the same file;
- * the '+load' implementation of all super classes of a class are
- executed before the '+load' of that class is executed;
+ * the `+load' implementation of all super classes of a class are
+ executed before the `+load' of that class is executed;
+
+ * the `+load' implementation of a class is executed before the
+ `+load' implementation of any category.
- * the '+load' implementation of a class is executed before the
- '+load' implementation of any category.
In particular, the following things, even if they can work in a
particular case, are not guaranteed:
@@ -42656,25 +43093,26 @@ particular case, are not guaranteed:
* allocation of or sending messages to objects whose classes have a
category implemented in the same file;
- * sending messages to Objective-C constant strings ('@"this is a
+ * sending messages to Objective-C constant strings (`@"this is a
constant string"');
- You should make no assumptions about receiving '+load' in sibling
-classes when you write '+load' of a class. The order in which sibling
-classes receive '+load' is not guaranteed.
- The order in which '+load' and '+initialize' are called could be
+ You should make no assumptions about receiving `+load' in sibling
+classes when you write `+load' of a class. The order in which sibling
+classes receive `+load' is not guaranteed.
+
+ The order in which `+load' and `+initialize' are called could be
problematic if this matters. If you don't allocate objects inside
-'+load', it is guaranteed that '+load' is called before '+initialize'.
-If you create an object inside '+load' the '+initialize' method of
-object's class is invoked even if '+load' was not invoked. Note if you
-explicitly call '+load' on a class, '+initialize' will be called first.
+`+load', it is guaranteed that `+load' is called before `+initialize'.
+If you create an object inside `+load' the `+initialize' method of
+object's class is invoked even if `+load' was not invoked. Note if you
+explicitly call `+load' on a class, `+initialize' will be called first.
To avoid possible problems try to implement only one of these methods.
- The '+load' method is also invoked when a bundle is dynamically loaded
+ The `+load' method is also invoked when a bundle is dynamically loaded
into your running program. This happens automatically without any
intervening operation from you. When you write bundles and you need to
-write '+load' you can safely create and send messages to objects whose
+write `+load' you can safely create and send messages to objects whose
classes already exist in the running program. The same restrictions as
above apply to classes defined in bundle.
@@ -42684,9 +43122,9 @@ File: gcc.info, Node: Type encoding, Next: Garbage Collection, Prev: Executin
8.3 Type Encoding
=================
-This is an advanced section. Type encodings are used extensively by the
-compiler and by the runtime, but you generally do not need to know about
-them to use Objective-C.
+This is an advanced section. Type encodings are used extensively by
+the compiler and by the runtime, but you generally do not need to know
+about them to use Objective-C.
The Objective-C compiler generates type encodings for all the types.
These type encodings are used at runtime to find out information about
@@ -42694,34 +43132,34 @@ selectors and methods and about objects and classes.
The types are encoded in the following way:
-'_Bool' 'B'
-'char' 'c'
-'unsigned char' 'C'
-'short' 's'
-'unsigned short' 'S'
-'int' 'i'
-'unsigned int' 'I'
-'long' 'l'
-'unsigned long' 'L'
-'long long' 'q'
-'unsigned long 'Q'
-long'
-'float' 'f'
-'double' 'd'
-'long double' 'D'
-'void' 'v'
-'id' '@'
-'Class' '#'
-'SEL' ':'
-'char*' '*'
-'enum' an 'enum' is encoded exactly as the integer type
- that the compiler uses for it, which depends on the
+`_Bool' `B'
+`char' `c'
+`unsigned char' `C'
+`short' `s'
+`unsigned short' `S'
+`int' `i'
+`unsigned int' `I'
+`long' `l'
+`unsigned long' `L'
+`long long' `q'
+`unsigned long `Q'
+long'
+`float' `f'
+`double' `d'
+`long double' `D'
+`void' `v'
+`id' `@'
+`Class' `#'
+`SEL' `:'
+`char*' `*'
+`enum' an `enum' is encoded exactly as the integer type that
+ the compiler uses for it, which depends on the
enumeration values. Often the compiler users
- 'unsigned int', which is then encoded as 'I'.
-unknown type '?'
-Complex types 'j' followed by the inner type. For example
- '_Complex double' is encoded as "jd".
-bit-fields 'b' followed by the starting position of the
+ `unsigned int', which is then encoded as `I'.
+unknown type `?'
+Complex types `j' followed by the inner type. For example
+ `_Complex double' is encoded as "jd".
+bit-fields `b' followed by the starting position of the
bit-field, the type of the bit-field and the size of
the bit-field (the bit-fields encoding was changed
from the NeXT's compiler encoding, see below)
@@ -42742,77 +43180,77 @@ bit closest to the beginning of the structure.
The non-atomic types are encoded as follows:
-pointers '^' followed by the pointed type.
-arrays '[' followed by the number of elements in the array
- followed by the type of the elements followed by ']'
-structures '{' followed by the name of the structure (or '?' if the
- structure is unnamed), the '=' sign, the type of the
- members and by '}'
-unions '(' followed by the name of the structure (or '?' if the
- union is unnamed), the '=' sign, the type of the members
- followed by ')'
-vectors '![' followed by the vector_size (the number of bytes
+pointers `^' followed by the pointed type.
+arrays `[' followed by the number of elements in the array
+ followed by the type of the elements followed by `]'
+structures `{' followed by the name of the structure (or `?' if the
+ structure is unnamed), the `=' sign, the type of the
+ members and by `}'
+unions `(' followed by the name of the structure (or `?' if the
+ union is unnamed), the `=' sign, the type of the members
+ followed by `)'
+vectors `![' followed by the vector_size (the number of bytes
composing the vector) followed by a comma, followed by
the alignment (in bytes) of the vector, followed by the
- type of the elements followed by ']'
+ type of the elements followed by `]'
Here are some types and their encodings, as they are generated by the
compiler on an i386 machine:
Objective-C type Compiler encoding
- int a[10]; '[10i]'
- struct { '{?=i[3f]b128i3b131i2c}'
- int i;
- float f[3];
- int a:3;
- int b:2;
- char c;
- }
- int a __attribute__ ((vector_size (16)));'![16,16i]' (alignment would depend on the machine)
+ int a[10]; `[10i]'
+ struct { `{?=i[3f]b128i3b131i2c}'
+ int i;
+ float f[3];
+ int a:3;
+ int b:2;
+ char c;
+ }
+ int a __attribute__ ((vector_size (16)));`![16,16i]' (alignment would depend on the machine)
- In addition to the types the compiler also encodes the type specifiers.
-The table below describes the encoding of the current Objective-C type
-specifiers:
+ In addition to the types the compiler also encodes the type
+specifiers. The table below describes the encoding of the current
+Objective-C type specifiers:
Specifier Encoding
-'const' 'r'
-'in' 'n'
-'inout' 'N'
-'out' 'o'
-'bycopy' 'O'
-'byref' 'R'
-'oneway' 'V'
+`const' `r'
+`in' `n'
+`inout' `N'
+`out' `o'
+`bycopy' `O'
+`byref' `R'
+`oneway' `V'
The type specifiers are encoded just before the type. Unlike types
however, the type specifiers are only encoded when they appear in method
argument types.
- Note how 'const' interacts with pointers:
+ Note how `const' interacts with pointers:
Objective-C type Compiler encoding
- const int 'ri'
- const int* '^ri'
- int *const 'r^i'
+ const int `ri'
+ const int* `^ri'
+ int *const `r^i'
- 'const int*' is a pointer to a 'const int', and so is encoded as '^ri'.
-'int* const', instead, is a 'const' pointer to an 'int', and so is
-encoded as 'r^i'.
+ `const int*' is a pointer to a `const int', and so is encoded as
+`^ri'. `int* const', instead, is a `const' pointer to an `int', and so
+is encoded as `r^i'.
- Finally, there is a complication when encoding 'const char *' versus
-'char * const'. Because 'char *' is encoded as '*' and not as '^c',
-there is no way to express the fact that 'r' applies to the pointer or
+ Finally, there is a complication when encoding `const char *' versus
+`char * const'. Because `char *' is encoded as `*' and not as `^c',
+there is no way to express the fact that `r' applies to the pointer or
to the pointee.
- Hence, it is assumed as a convention that 'r*' means 'const char *'
+ Hence, it is assumed as a convention that `r*' means `const char *'
(since it is what is most often meant), and there is no way to encode
-'char *const'. 'char *const' would simply be encoded as '*', and the
-'const' is lost.
+`char *const'. `char *const' would simply be encoded as `*', and the
+`const' is lost.
* Menu:
@@ -42828,8 +43266,9 @@ File: gcc.info, Node: Legacy type encoding, Next: @encode, Up: Type encoding
Unfortunately, historically GCC used to have a number of bugs in its
encoding code. The NeXT runtime expects GCC to emit type encodings in
-this historical format (compatible with GCC-3.3), so when using the NeXT
-runtime, GCC will introduce on purpose a number of incorrect encodings:
+this historical format (compatible with GCC-3.3), so when using the
+NeXT runtime, GCC will introduce on purpose a number of incorrect
+encodings:
* the read-only qualifier of the pointee gets emitted before the '^'.
The read-only qualifier of the pointer itself gets ignored, unless
@@ -42837,29 +43276,30 @@ runtime, GCC will introduce on purpose a number of incorrect encodings:
type.
* 32-bit longs are encoded as 'l' or 'L', but not always. For
- typedefs, the compiler uses 'i' or 'I' instead if encoding a struct
- field or a pointer.
+ typedefs, the compiler uses 'i' or 'I' instead if encoding a
+ struct field or a pointer.
- * 'enum's are always encoded as 'i' (int) even if they are actually
+ * `enum's are always encoded as 'i' (int) even if they are actually
unsigned or long.
+
In addition to that, the NeXT runtime uses a different encoding for
-bitfields. It encodes them as 'b' followed by the size, without a bit
+bitfields. It encodes them as `b' followed by the size, without a bit
offset or the underlying field type.

File: gcc.info, Node: @encode, Next: Method signatures, Prev: Legacy type encoding, Up: Type encoding
-8.3.2 '@encode'
+8.3.2 `@encode'
---------------
-GNU Objective-C supports the '@encode' syntax that allows you to create
-a type encoding from a C/Objective-C type. For example, '@encode(int)'
-is compiled by the compiler into '"i"'.
+GNU Objective-C supports the `@encode' syntax that allows you to create
+a type encoding from a C/Objective-C type. For example, `@encode(int)'
+is compiled by the compiler into `"i"'.
- '@encode' does not support type qualifiers other than 'const'. For
-example, '@encode(const char*)' is valid and is compiled into '"r*"',
-while '@encode(bycopy char *)' is invalid and will cause a compilation
+ `@encode' does not support type qualifiers other than `const'. For
+example, `@encode(const char*)' is valid and is compiled into `"r*"',
+while `@encode(bycopy char *)' is invalid and will cause a compilation
error.

@@ -42869,7 +43309,7 @@ File: gcc.info, Node: Method signatures, Prev: @encode, Up: Type encoding
-----------------------
This section documents the encoding of method types, which is rarely
-needed to use Objective-C. You should skip it at a first reading; the
+needed to use Objective-C. You should skip it at a first reading; the
runtime provides functions that will work on methods and can walk
through the list of parameters and interpret them for you. These
functions are part of the public "API" and are the preferred way to
@@ -42886,26 +43326,27 @@ arguments.
The "signature" is a null-terminated string, composed of the following:
* The return type, including type qualifiers. For example, a method
- returning 'int' would have 'i' here.
+ returning `int' would have `i' here.
* The total size (in bytes) required to pass all the parameters.
- This includes the two hidden parameters (the object 'self' and the
- method selector '_cmd').
+ This includes the two hidden parameters (the object `self' and the
+ method selector `_cmd').
* Each argument, with the type encoding, followed by the offset (in
bytes) of the argument in the list of parameters.
- For example, a method with no arguments and returning 'int' would have
-the signature 'i8@0:4' if the size of a pointer is 4. The signature is
-interpreted as follows: the 'i' is the return type (an 'int'), the '8'
+
+ For example, a method with no arguments and returning `int' would have
+the signature `i8@0:4' if the size of a pointer is 4. The signature is
+interpreted as follows: the `i' is the return type (an `int'), the `8'
is the total size of the parameters in bytes (two pointers each of size
-4), the '@0' is the first parameter (an object at byte offset '0') and
-':4' is the second parameter (a 'SEL' at byte offset '4').
+4), the `@0' is the first parameter (an object at byte offset `0') and
+`:4' is the second parameter (a `SEL' at byte offset `4').
You can easily find more examples by running the "strings" program on
-an Objective-C object file compiled by GCC. You'll see a lot of strings
-that look very much like 'i8@0:4'. They are signatures of Objective-C
-methods.
+an Objective-C object file compiled by GCC. You'll see a lot of
+strings that look very much like `i8@0:4'. They are signatures of
+Objective-C methods.

File: gcc.info, Node: Garbage Collection, Next: Constant string objects, Prev: Type encoding, Up: Objective-C
@@ -42921,10 +43362,10 @@ using a powerful conservative garbage collector, known as the
Boehm-Demers-Weiser conservative garbage collector.
To enable the support for it you have to configure the compiler using
-an additional argument, '--enable-objc-gc'. This will build the
+an additional argument, `--enable-objc-gc'. This will build the
boehm-gc library, and build an additional runtime library which has
several enhancements to support the garbage collector. The new library
-has a new name, 'libobjc_gc.a' to not conflict with the
+has a new name, `libobjc_gc.a' to not conflict with the
non-garbage-collected library.
When the garbage collector is used, the objects are allocated using the
@@ -42934,14 +43375,14 @@ on where pointers are located inside objects. This information is
computed once per class, immediately after the class has been
initialized.
- There is a new runtime function 'class_ivar_set_gcinvisible()' which
+ There is a new runtime function `class_ivar_set_gcinvisible()' which
can be used to declare a so-called "weak pointer" reference. Such a
pointer is basically hidden for the garbage collector; this can be
useful in certain situations, especially when you want to keep track of
the allocated objects, yet allow them to be collected. This kind of
pointers can only be members of objects, you cannot declare a global
pointer as a weak reference. Every type which is a pointer type can be
-declared a weak pointer, including 'id', 'Class' and 'SEL'.
+declared a weak pointer, including `id', `Class' and `SEL'.
Here is an example of how to use this feature. Suppose you want to
implement a class whose instances hold a weak pointer reference; the
@@ -42979,9 +43420,8 @@ following class does this:
@end
-
Weak pointers are supported through a new type character specifier
-represented by the '!' character. The 'class_ivar_set_gcinvisible()'
+represented by the `!' character. The `class_ivar_set_gcinvisible()'
function adds or removes this specifier to the string type description
of the instance variable named as argument.
@@ -42993,20 +43433,20 @@ File: gcc.info, Node: Constant string objects, Next: compatibility_alias, Pre
GNU Objective-C provides constant string objects that are generated
directly by the compiler. You declare a constant string object by
-prefixing a C constant string with the character '@':
+prefixing a C constant string with the character `@':
id myString = @"this is a constant string object";
The constant string objects are by default instances of the
-'NXConstantString' class which is provided by the GNU Objective-C
+`NXConstantString' class which is provided by the GNU Objective-C
runtime. To get the definition of this class you must include the
-'objc/NXConstStr.h' header file.
+`objc/NXConstStr.h' header file.
User defined libraries may want to implement their own constant string
class. To be able to support them, the GNU Objective-C compiler
provides a new command line options
-'-fconstant-string-class=CLASS-NAME'. The provided class should adhere
-to a strict structure, the same as 'NXConstantString''s structure:
+`-fconstant-string-class=CLASS-NAME'. The provided class should adhere
+to a strict structure, the same as `NXConstantString''s structure:
@interface MyConstantStringClass
@@ -43017,52 +43457,52 @@ to a strict structure, the same as 'NXConstantString''s structure:
}
@end
-
- 'NXConstantString' inherits from 'Object'; user class libraries may
+ `NXConstantString' inherits from `Object'; user class libraries may
choose to inherit the customized constant string class from a different
-class than 'Object'. There is no requirement in the methods the
-constant string class has to implement, but the final ivar layout of the
-class must be the compatible with the given structure.
+class than `Object'. There is no requirement in the methods the
+constant string class has to implement, but the final ivar layout of
+the class must be the compatible with the given structure.
When the compiler creates the statically allocated constant string
-object, the 'c_string' field will be filled by the compiler with the
-string; the 'length' field will be filled by the compiler with the
-string length; the 'isa' pointer will be filled with 'NULL' by the
+object, the `c_string' field will be filled by the compiler with the
+string; the `length' field will be filled by the compiler with the
+string length; the `isa' pointer will be filled with `NULL' by the
compiler, and it will later be fixed up automatically at runtime by the
GNU Objective-C runtime library to point to the class which was set by
-the '-fconstant-string-class' option when the object file is loaded (if
-you wonder how it works behind the scenes, the name of the class to use,
-and the list of static objects to fixup, are stored by the compiler in
-the object file in a place where the GNU runtime library will find them
-at runtime).
+the `-fconstant-string-class' option when the object file is loaded (if
+you wonder how it works behind the scenes, the name of the class to
+use, and the list of static objects to fixup, are stored by the
+compiler in the object file in a place where the GNU runtime library
+will find them at runtime).
- As a result, when a file is compiled with the '-fconstant-string-class'
-option, all the constant string objects will be instances of the class
-specified as argument to this option. It is possible to have multiple
-compilation units referring to different constant string classes,
-neither the compiler nor the linker impose any restrictions in doing
-this.
+ As a result, when a file is compiled with the
+`-fconstant-string-class' option, all the constant string objects will
+be instances of the class specified as argument to this option. It is
+possible to have multiple compilation units referring to different
+constant string classes, neither the compiler nor the linker impose any
+restrictions in doing this.

File: gcc.info, Node: compatibility_alias, Next: Exceptions, Prev: Constant string objects, Up: Objective-C
-8.6 'compatibility_alias'
+8.6 `compatibility_alias'
=========================
-The keyword '@compatibility_alias' allows you to define a class name as
+The keyword `@compatibility_alias' allows you to define a class name as
equivalent to another class name. For example:
@compatibility_alias WOApplication GSWApplication;
- tells the compiler that each time it encounters 'WOApplication' as a
-class name, it should replace it with 'GSWApplication' (that is,
-'WOApplication' is just an alias for 'GSWApplication').
+ tells the compiler that each time it encounters `WOApplication' as a
+class name, it should replace it with `GSWApplication' (that is,
+`WOApplication' is just an alias for `GSWApplication').
There are some constraints on how this can be used--
- * 'WOApplication' (the alias) must not be an existing class;
+ * `WOApplication' (the alias) must not be an existing class;
+
+ * `GSWApplication' (the real class) must be an existing class.
- * 'GSWApplication' (the real class) must be an existing class.

File: gcc.info, Node: Exceptions, Next: Synchronization, Prev: compatibility_alias, Up: Objective-C
@@ -43097,45 +43537,46 @@ in the following example:
...
}
- The '@throw' statement may appear anywhere in an Objective-C or
-Objective-C++ program; when used inside of a '@catch' block, the
-'@throw' may appear without an argument (as shown above), in which case
-the object caught by the '@catch' will be rethrown.
+ The `@throw' statement may appear anywhere in an Objective-C or
+Objective-C++ program; when used inside of a `@catch' block, the
+`@throw' may appear without an argument (as shown above), in which case
+the object caught by the `@catch' will be rethrown.
Note that only (pointers to) Objective-C objects may be thrown and
caught using this scheme. When an object is thrown, it will be caught
-by the nearest '@catch' clause capable of handling objects of that type,
-analogously to how 'catch' blocks work in C++ and Java. A '@catch(id
-...)' clause (as shown above) may also be provided to catch any and all
-Objective-C exceptions not caught by previous '@catch' clauses (if any).
-
- The '@finally' clause, if present, will be executed upon exit from the
-immediately preceding '@try ... @catch' section. This will happen
+by the nearest `@catch' clause capable of handling objects of that
+type, analogously to how `catch' blocks work in C++ and Java. A
+`@catch(id ...)' clause (as shown above) may also be provided to catch
+any and all Objective-C exceptions not caught by previous `@catch'
+clauses (if any).
+
+ The `@finally' clause, if present, will be executed upon exit from the
+immediately preceding `@try ... @catch' section. This will happen
regardless of whether any exceptions are thrown, caught or rethrown
-inside the '@try ... @catch' section, analogously to the behavior of the
-'finally' clause in Java.
+inside the `@try ... @catch' section, analogously to the behavior of
+the `finally' clause in Java.
There are several caveats to using the new exception mechanism:
- * The '-fobjc-exceptions' command line option must be used when
+ * The `-fobjc-exceptions' command line option must be used when
compiling Objective-C files that use exceptions.
* With the GNU runtime, exceptions are always implemented as "native"
- exceptions and it is recommended that the '-fexceptions' and
- '-shared-libgcc' options are used when linking.
+ exceptions and it is recommended that the `-fexceptions' and
+ `-shared-libgcc' options are used when linking.
* With the NeXT runtime, although currently designed to be binary
- compatible with 'NS_HANDLER'-style idioms provided by the
- 'NSException' class, the new exceptions can only be used on Mac OS
+ compatible with `NS_HANDLER'-style idioms provided by the
+ `NSException' class, the new exceptions can only be used on Mac OS
X 10.3 (Panther) and later systems, due to additional functionality
needed in the NeXT Objective-C runtime.
* As mentioned above, the new exceptions do not support handling
- types other than Objective-C objects. Furthermore, when used from
+ types other than Objective-C objects. Furthermore, when used from
Objective-C++, the Objective-C exception model does not
interoperate with C++ exceptions at this time. This means you
- cannot '@throw' an exception from Objective-C and 'catch' it in
- C++, or vice versa (i.e., 'throw ... @catch').
+ cannot `@throw' an exception from Objective-C and `catch' it in
+ C++, or vice versa (i.e., `throw ... @catch').

File: gcc.info, Node: Synchronization, Next: Fast enumeration, Prev: Exceptions, Up: Objective-C
@@ -43149,23 +43590,23 @@ GNU Objective-C provides support for synchronized blocks:
...
}
- Upon entering the '@synchronized' block, a thread of execution shall
-first check whether a lock has been placed on the corresponding 'guard'
+ Upon entering the `@synchronized' block, a thread of execution shall
+first check whether a lock has been placed on the corresponding `guard'
object by another thread. If it has, the current thread shall wait
-until the other thread relinquishes its lock. Once 'guard' becomes
-available, the current thread will place its own lock on it, execute the
-code contained in the '@synchronized' block, and finally relinquish the
-lock (thereby making 'guard' available to other threads).
+until the other thread relinquishes its lock. Once `guard' becomes
+available, the current thread will place its own lock on it, execute
+the code contained in the `@synchronized' block, and finally relinquish
+the lock (thereby making `guard' available to other threads).
- Unlike Java, Objective-C does not allow for entire methods to be marked
-'@synchronized'. Note that throwing exceptions out of '@synchronized'
-blocks is allowed, and will cause the guarding object to be unlocked
-properly.
+ Unlike Java, Objective-C does not allow for entire methods to be
+marked `@synchronized'. Note that throwing exceptions out of
+`@synchronized' blocks is allowed, and will cause the guarding object
+to be unlocked properly.
Because of the interactions between synchronization and exception
-handling, you can only use '@synchronized' when compiling with
+handling, you can only use `@synchronized' when compiling with
exceptions enabled, that is with the command line option
-'-fobjc-exceptions'.
+`-fobjc-exceptions'.

File: gcc.info, Node: Fast enumeration, Next: Messaging with the GNU Objective-C runtime, Prev: Synchronization, Up: Objective-C
@@ -43196,19 +43637,19 @@ GNU Objective-C provides support for the fast enumeration syntax:
/* Do something with 'object' */
}
- 'array' needs to be an Objective-C object (usually a collection object,
-for example an array, a dictionary or a set) which implements the "Fast
-Enumeration Protocol" (see below). If you are using a Foundation
-library such as GNUstep Base or Apple Cocoa Foundation, all collection
-objects in the library implement this protocol and can be used in this
-way.
+ `array' needs to be an Objective-C object (usually a collection
+object, for example an array, a dictionary or a set) which implements
+the "Fast Enumeration Protocol" (see below). If you are using a
+Foundation library such as GNUstep Base or Apple Cocoa Foundation, all
+collection objects in the library implement this protocol and can be
+used in this way.
- The code above would iterate over all objects in 'array'. For each of
-them, it assigns it to 'object', then executes the 'Do something with
+ The code above would iterate over all objects in `array'. For each of
+them, it assigns it to `object', then executes the `Do something with
'object'' statements.
Here is a fully worked-out example using a Foundation library (which
-provides the implementation of 'NSArray', 'NSString' and 'NSLog'):
+provides the implementation of `NSArray', `NSString' and `NSLog'):
NSArray *array = [NSArray arrayWithObjects: @"1", @"2", @"3", nil];
NSString *object;
@@ -43245,8 +43686,8 @@ A c99-like declaration syntax is also allowed:
but can save some typing.
- Note that the option '-std=c99' is not required to allow this syntax in
-Objective-C.
+ Note that the option `-std=c99' is not required to allow this syntax
+in Objective-C.

File: gcc.info, Node: Fast enumeration details, Next: Fast enumeration protocol, Prev: c99-like fast enumeration syntax, Up: Fast enumeration
@@ -43264,9 +43705,9 @@ the code
here is what happens when you run it:
- * 'COLLECTION EXPRESSION' is evaluated exactly once and the result is
- used as the collection object to iterate over. This means it is
- safe to write code such as 'for (object in [NSDictionary
+ * `COLLECTION EXPRESSION' is evaluated exactly once and the result
+ is used as the collection object to iterate over. This means it
+ is safe to write code such as `for (object in [NSDictionary
keyEnumerator]) ...'.
* the iteration is implemented by the compiler by repeatedly getting
@@ -43276,32 +43717,33 @@ the code
objects are retrieved one by one (hence the name "fast
enumeration").
- * if there are no objects in the collection, then 'OBJECT EXPRESSION'
- is set to 'nil' and the loop immediately terminates.
+ * if there are no objects in the collection, then `OBJECT
+ EXPRESSION' is set to `nil' and the loop immediately terminates.
* if there are objects in the collection, then for each object in the
- collection (in the order they are returned) 'OBJECT EXPRESSION' is
- set to the object, then 'STATEMENTS' are executed.
+ collection (in the order they are returned) `OBJECT EXPRESSION' is
+ set to the object, then `STATEMENTS' are executed.
- * 'STATEMENTS' can contain 'break' and 'continue' commands, which
+ * `STATEMENTS' can contain `break' and `continue' commands, which
will abort the iteration or skip to the next loop iteration as
expected.
* when the iteration ends because there are no more objects to
- iterate over, 'OBJECT EXPRESSION' is set to 'nil'. This allows you
- to determine whether the iteration finished because a 'break'
- command was used (in which case 'OBJECT EXPRESSION' will remain set
- to the last object that was iterated over) or because it iterated
- over all the objects (in which case 'OBJECT EXPRESSION' will be set
- to 'nil').
-
- * 'STATEMENTS' must not make any changes to the collection object; if
- they do, it is a hard error and the fast enumeration terminates by
- invoking 'objc_enumerationMutation', a runtime function that
+ iterate over, `OBJECT EXPRESSION' is set to `nil'. This allows
+ you to determine whether the iteration finished because a `break'
+ command was used (in which case `OBJECT EXPRESSION' will remain
+ set to the last object that was iterated over) or because it
+ iterated over all the objects (in which case `OBJECT EXPRESSION'
+ will be set to `nil').
+
+ * `STATEMENTS' must not make any changes to the collection object;
+ if they do, it is a hard error and the fast enumeration terminates
+ by invoking `objc_enumerationMutation', a runtime function that
normally aborts the program but which can be customized by
- Foundation libraries via 'objc_set_mutation_handler' to do
+ Foundation libraries via `objc_set_mutation_handler' to do
something different, such as raising an exception.
+

File: gcc.info, Node: Fast enumeration protocol, Prev: Fast enumeration details, Up: Fast enumeration
@@ -43315,7 +43757,7 @@ enumeration, you need to have it implement the method
objects: (id *)objects
count: (unsigned long)len;
- where 'NSFastEnumerationState' must be defined in your code as follows:
+ where `NSFastEnumerationState' must be defined in your code as follows:
typedef struct
{
@@ -43325,11 +43767,11 @@ enumeration, you need to have it implement the method
unsigned long extra[5];
} NSFastEnumerationState;
- If no 'NSFastEnumerationState' is defined in your code, the compiler
-will automatically replace 'NSFastEnumerationState *' with 'struct
+ If no `NSFastEnumerationState' is defined in your code, the compiler
+will automatically replace `NSFastEnumerationState *' with `struct
__objcFastEnumerationState *', where that type is silently defined by
the compiler in an identical way. This can be confusing and we
-recommend that you define 'NSFastEnumerationState' (as shown above)
+recommend that you define `NSFastEnumerationState' (as shown above)
instead.
The method is called repeatedly during a fast enumeration to retrieve
@@ -43337,38 +43779,38 @@ batches of objects. Each invocation of the method should retrieve the
next batch of objects.
The return value of the method is the number of objects in the current
-batch; this should not exceed 'len', which is the maximum size of a
+batch; this should not exceed `len', which is the maximum size of a
batch as requested by the caller. The batch itself is returned in the
-'itemsPtr' field of the 'NSFastEnumerationState' struct.
+`itemsPtr' field of the `NSFastEnumerationState' struct.
- To help with returning the objects, the 'objects' array is a C array
-preallocated by the caller (on the stack) of size 'len'. In many cases
-you can put the objects you want to return in that 'objects' array, then
-do 'itemsPtr = objects'. But you don't have to; if your collection
-already has the objects to return in some form of C array, it could
-return them from there instead.
+ To help with returning the objects, the `objects' array is a C array
+preallocated by the caller (on the stack) of size `len'. In many cases
+you can put the objects you want to return in that `objects' array,
+then do `itemsPtr = objects'. But you don't have to; if your
+collection already has the objects to return in some form of C array,
+it could return them from there instead.
- The 'state' and 'extra' fields of the 'NSFastEnumerationState'
+ The `state' and `extra' fields of the `NSFastEnumerationState'
structure allows your collection object to keep track of the state of
-the enumeration. In a simple array implementation, 'state' may keep
-track of the index of the last object that was returned, and 'extra' may
-be unused.
-
- The 'mutationsPtr' field of the 'NSFastEnumerationState' is used to
-keep track of mutations. It should point to a number; before working on
-each object, the fast enumeration loop will check that this number has
-not changed. If it has, a mutation has happened and the fast
-enumeration will abort. So, 'mutationsPtr' could be set to point to
+the enumeration. In a simple array implementation, `state' may keep
+track of the index of the last object that was returned, and `extra'
+may be unused.
+
+ The `mutationsPtr' field of the `NSFastEnumerationState' is used to
+keep track of mutations. It should point to a number; before working
+on each object, the fast enumeration loop will check that this number
+has not changed. If it has, a mutation has happened and the fast
+enumeration will abort. So, `mutationsPtr' could be set to point to
some sort of version number of your collection, which is increased by
-one every time there is a change (for example when an object is added or
-removed). Or, if you are content with less strict mutation checks, it
-could point to the number of objects in your collection or some other
-value that can be checked to perform an approximate check that the
-collection has not been mutated.
+one every time there is a change (for example when an object is added
+or removed). Or, if you are content with less strict mutation checks,
+it could point to the number of objects in your collection or some
+other value that can be checked to perform an approximate check that
+the collection has not been mutated.
- Finally, note how we declared the 'len' argument and the return value
-to be of type 'unsigned long'. They could also be declared to be of
-type 'unsigned int' and everything would still work.
+ Finally, note how we declared the `len' argument and the return value
+to be of type `unsigned long'. They could also be declared to be of
+type `unsigned int' and everything would still work.

File: gcc.info, Node: Messaging with the GNU Objective-C runtime, Prev: Fast enumeration, Up: Objective-C
@@ -43384,18 +43826,18 @@ designed to be portable, and so is based on standard C.
Sending a message in the GNU Objective-C runtime is composed of two
separate steps. First, there is a call to the lookup function,
-'objc_msg_lookup ()' (or, in the case of messages to super,
-'objc_msg_lookup_super ()'). This runtime function takes as argument
-the receiver and the selector of the method to be called; it returns the
-'IMP', that is a pointer to the function implementing the method. The
-second step of method invocation consists of casting this pointer
+`objc_msg_lookup ()' (or, in the case of messages to super,
+`objc_msg_lookup_super ()'). This runtime function takes as argument
+the receiver and the selector of the method to be called; it returns
+the `IMP', that is a pointer to the function implementing the method.
+The second step of method invocation consists of casting this pointer
function to the appropriate function pointer type, and calling the
function pointed to it with the right arguments.
For example, when the compiler encounters a method invocation such as
-'[object init]', it compiles it into a call to 'objc_msg_lookup (object,
-@selector(init))' followed by a cast of the returned value to the
-appropriate function pointer type, and then it calls it.
+`[object init]', it compiles it into a call to `objc_msg_lookup
+(object, @selector(init))' followed by a cast of the returned value to
+the appropriate function pointer type, and then it calls it.
* Menu:
@@ -43408,9 +43850,9 @@ File: gcc.info, Node: Dynamically registering methods, Next: Forwarding hook,
8.10.1 Dynamically Registering Methods
--------------------------------------
-If 'objc_msg_lookup()' does not find a suitable method implementation,
-because the receiver does not implement the required method, it tries to
-see if the class can dynamically register the method.
+If `objc_msg_lookup()' does not find a suitable method implementation,
+because the receiver does not implement the required method, it tries
+to see if the class can dynamically register the method.
To do so, the runtime checks if the class of the receiver implements
the method
@@ -43421,24 +43863,24 @@ the method
+ (BOOL) resolveClassMethod: (SEL)selector;
- in the case of a class method. If the class implements it, the runtime
-invokes it, passing as argument the selector of the original method, and
-if it returns 'YES', the runtime tries the lookup again, which could now
-succeed if a matching method was added dynamically by
-'+resolveInstanceMethod:' or '+resolveClassMethod:'.
+ in the case of a class method. If the class implements it, the
+runtime invokes it, passing as argument the selector of the original
+method, and if it returns `YES', the runtime tries the lookup again,
+which could now succeed if a matching method was added dynamically by
+`+resolveInstanceMethod:' or `+resolveClassMethod:'.
This allows classes to dynamically register methods (by adding them to
-the class using 'class_addMethod') when they are first called. To do
-so, a class should implement '+resolveInstanceMethod:' (or, depending on
-the case, '+resolveClassMethod:') and have it recognize the selectors of
-methods that can be registered dynamically at runtime, register them,
-and return 'YES'. It should return 'NO' for methods that it does not
-dynamically registered at runtime.
+the class using `class_addMethod') when they are first called. To do
+so, a class should implement `+resolveInstanceMethod:' (or, depending
+on the case, `+resolveClassMethod:') and have it recognize the
+selectors of methods that can be registered dynamically at runtime,
+register them, and return `YES'. It should return `NO' for methods
+that it does not dynamically registered at runtime.
- If '+resolveInstanceMethod:' (or '+resolveClassMethod:') is not
-implemented or returns 'NO', the runtime then tries the forwarding hook.
+ If `+resolveInstanceMethod:' (or `+resolveClassMethod:') is not
+implemented or returns `NO', the runtime then tries the forwarding hook.
- Support for '+resolveInstanceMethod:' and 'resolveClassMethod:' was
+ Support for `+resolveInstanceMethod:' and `resolveClassMethod:' was
added to the GNU Objective-C runtime in GCC version 4.6.

@@ -43448,53 +43890,53 @@ File: gcc.info, Node: Forwarding hook, Prev: Dynamically registering methods,
----------------------
The GNU Objective-C runtime provides a hook, called
-'__objc_msg_forward2', which is called by 'objc_msg_lookup()' when it
+`__objc_msg_forward2', which is called by `objc_msg_lookup()' when it
can't find a method implementation in the runtime tables and after
-calling '+resolveInstanceMethod:' and '+resolveClassMethod:' has been
+calling `+resolveInstanceMethod:' and `+resolveClassMethod:' has been
attempted and did not succeed in dynamically registering the method.
To configure the hook, you set the global variable
-'__objc_msg_forward2' to a function with the same argument and return
-types of 'objc_msg_lookup()'. When 'objc_msg_lookup()' can not find a
+`__objc_msg_forward2' to a function with the same argument and return
+types of `objc_msg_lookup()'. When `objc_msg_lookup()' can not find a
method implementation, it invokes the hook function you provided to get
a method implementation to return. So, in practice
-'__objc_msg_forward2' allows you to extend 'objc_msg_lookup()' by adding
-some custom code that is called to do a further lookup when no standard
-method implementation can be found using the normal lookup.
+`__objc_msg_forward2' allows you to extend `objc_msg_lookup()' by
+adding some custom code that is called to do a further lookup when no
+standard method implementation can be found using the normal lookup.
This hook is generally reserved for "Foundation" libraries such as
GNUstep Base, which use it to implement their high-level method
-forwarding API, typically based around the 'forwardInvocation:' method.
+forwarding API, typically based around the `forwardInvocation:' method.
So, unless you are implementing your own "Foundation" library, you
should not set this hook.
- In a typical forwarding implementation, the '__objc_msg_forward2' hook
+ In a typical forwarding implementation, the `__objc_msg_forward2' hook
function determines the argument and return type of the method that is
being looked up, and then creates a function that takes these arguments
and has that return type, and returns it to the caller. Creating this
function is non-trivial and is typically performed using a dedicated
-library such as 'libffi'.
+library such as `libffi'.
The forwarding method implementation thus created is returned by
-'objc_msg_lookup()' and is executed as if it was a normal method
-implementation. When the forwarding method implementation is called, it
-is usually expected to pack all arguments into some sort of object
-(typically, an 'NSInvocation' in a "Foundation" library), and hand it
-over to the programmer ('forwardInvocation:') who is then allowed to
+`objc_msg_lookup()' and is executed as if it was a normal method
+implementation. When the forwarding method implementation is called,
+it is usually expected to pack all arguments into some sort of object
+(typically, an `NSInvocation' in a "Foundation" library), and hand it
+over to the programmer (`forwardInvocation:') who is then allowed to
manipulate the method invocation using a high-level API provided by the
"Foundation" library. For example, the programmer may want to examine
the method invocation arguments and name and potentially change them
before forwarding the method invocation to one or more local objects
-('performInvocation:') or even to remote objects (by using Distributed
+(`performInvocation:') or even to remote objects (by using Distributed
Objects or some other mechanism). When all this completes, the return
value is passed back and must be returned correctly to the original
caller.
- Note that the GNU Objective-C runtime currently provides no support for
-method forwarding or method invocations other than the
-'__objc_msg_forward2' hook.
+ Note that the GNU Objective-C runtime currently provides no support
+for method forwarding or method invocations other than the
+`__objc_msg_forward2' hook.
- If the forwarding hook does not exist or returns 'NULL', the runtime
+ If the forwarding hook does not exist or returns `NULL', the runtime
currently attempts forwarding using an older, deprecated API, and if
that fails, it aborts the program. In future versions of the GNU
Objective-C runtime, the runtime will immediately abort.
@@ -43509,16 +43951,16 @@ Binary compatibility encompasses several related concepts:
"application binary interface (ABI)"
The set of runtime conventions followed by all of the tools that
- deal with binary representations of a program, including compilers,
- assemblers, linkers, and language runtime support. Some ABIs are
- formal with a written specification, possibly designed by multiple
- interested parties. Others are simply the way things are actually
- done by a particular set of tools.
+ deal with binary representations of a program, including
+ compilers, assemblers, linkers, and language runtime support.
+ Some ABIs are formal with a written specification, possibly
+ designed by multiple interested parties. Others are simply the
+ way things are actually done by a particular set of tools.
"ABI conformance"
- A compiler conforms to an ABI if it generates code that follows all
- of the specifications enumerated by that ABI. A library conforms
- to an ABI if it is implemented according to that ABI. An
+ A compiler conforms to an ABI if it generates code that follows
+ all of the specifications enumerated by that ABI. A library
+ conforms to an ABI if it is implemented according to that ABI. An
application conforms to an ABI if it is built using tools that
conform to that ABI and does not contain source code that
specifically changes behavior specified by the ABI.
@@ -43531,10 +43973,10 @@ Binary compatibility encompasses several related concepts:
Different sets of tools are interoperable if they generate files
that can be used in the same program. The set of tools includes
compilers, assemblers, linkers, libraries, header files, startup
- files, and debuggers. Binaries produced by different sets of tools
- are not interoperable unless they implement the same ABI. This
- applies to different versions of the same tools as well as tools
- from different vendors.
+ files, and debuggers. Binaries produced by different sets of
+ tools are not interoperable unless they implement the same ABI.
+ This applies to different versions of the same tools as well as
+ tools from different vendors.
"intercallability"
Whether a function in a binary built by one set of tools can call a
@@ -43542,11 +43984,12 @@ Binary compatibility encompasses several related concepts:
of interoperability.
"implementation-defined features"
- Language standards include lists of implementation-defined features
- whose behavior can vary from one implementation to another. Some
- of these features are normally covered by a platform's ABI and
- others are not. The features that are not covered by an ABI
- generally affect how a program behaves, but not intercallability.
+ Language standards include lists of implementation-defined
+ features whose behavior can vary from one implementation to
+ another. Some of these features are normally covered by a
+ platform's ABI and others are not. The features that are not
+ covered by an ABI generally affect how a program behaves, but not
+ intercallability.
"compatibility"
Conformance to the same ABI and the same behavior of
@@ -43557,18 +44000,27 @@ Binary compatibility encompasses several related concepts:
affects code generation and runtime support for:
* size and alignment of data types
+
* layout of structured types
+
* calling conventions
+
* register usage conventions
+
* interfaces for runtime arithmetic support
+
* object file formats
In addition, the application binary interface implemented by a C++
compiler affects code generation and runtime support for:
* name mangling
+
* exception handling
+
* invoking constructors and destructors
+
* layout, alignment, and padding of classes
+
* layout and alignment of virtual tables
Some GCC compilation options cause the compiler to generate code that
@@ -43592,7 +44044,7 @@ GCC releases, but it is possible that we will encounter problems that
make this difficult. Such problems could include different
interpretations of the C++ ABI by different vendors, bugs in the ABI, or
bugs in the implementation of the ABI in different compilers. GCC's
-'-Wabi' switch warns when G++ generates code that is probably not
+`-Wabi' switch warns when G++ generates code that is probably not
compatible with the C++ ABI.
The C++ library used with a C++ compiler includes the Standard C++
@@ -43606,14 +44058,14 @@ compiler and runtime support.
When G++ and another C++ compiler conform to the same C++ ABI, but the
implementations of the Standard C++ Library that they normally use do
-not follow the same ABI for the Standard C++ Library, object files built
-with those compilers can be used in the same program only if they use
-the same C++ library. This requires specifying the location of the C++
-library header files when invoking the compiler whose usual library is
-not being used. The location of GCC's C++ header files depends on how
-the GCC build was configured, but can be seen by using the G++ '-v'
-option. With default configuration options for G++ 3.3 the compile line
-for a different C++ compiler needs to include
+not follow the same ABI for the Standard C++ Library, object files
+built with those compilers can be used in the same program only if they
+use the same C++ library. This requires specifying the location of the
+C++ library header files when invoking the compiler whose usual library
+is not being used. The location of GCC's C++ header files depends on
+how the GCC build was configured, but can be seen by using the G++ `-v'
+option. With default configuration options for G++ 3.3 the compile
+line for a different C++ compiler needs to include
-IGCC_INSTALL_DIRECTORY/include/c++/3.3
@@ -43623,25 +44075,25 @@ files for that other library.
The most straightforward way to link a program to use a particular C++
library is to use a C++ driver that specifies that C++ library by
-default. The 'g++' driver, for example, tells the linker where to find
-GCC's C++ library ('libstdc++') plus the other libraries and startup
+default. The `g++' driver, for example, tells the linker where to find
+GCC's C++ library (`libstdc++') plus the other libraries and startup
files it needs, in the proper order.
If a program must use a different C++ library and it's not possible to
do the final link using a C++ driver that uses that library by default,
-it is necessary to tell 'g++' the location and name of that library. It
-might also be necessary to specify different startup files and other
+it is necessary to tell `g++' the location and name of that library.
+It might also be necessary to specify different startup files and other
runtime support libraries, and to suppress the use of GCC's support
-libraries with one or more of the options '-nostdlib', '-nostartfiles',
-and '-nodefaultlibs'.
+libraries with one or more of the options `-nostdlib', `-nostartfiles',
+and `-nodefaultlibs'.

File: gcc.info, Node: Gcov, Next: Gcov-tool, Prev: Compatibility, Up: Top
-10 'gcov'--a Test Coverage Program
+10 `gcov'--a Test Coverage Program
**********************************
-'gcov' is a tool you can use in conjunction with GCC to test code
+`gcov' is a tool you can use in conjunction with GCC to test code
coverage in your programs.
* Menu:
@@ -43655,19 +44107,19 @@ coverage in your programs.

File: gcc.info, Node: Gcov Intro, Next: Invoking Gcov, Up: Gcov
-10.1 Introduction to 'gcov'
+10.1 Introduction to `gcov'
===========================
-'gcov' is a test coverage program. Use it in concert with GCC to
-analyze your programs to help create more efficient, faster running code
-and to discover untested parts of your program. You can use 'gcov' as a
-profiling tool to help discover where your optimization efforts will
-best affect your code. You can also use 'gcov' along with the other
-profiling tool, 'gprof', to assess which parts of your code use the
-greatest amount of computing time.
+`gcov' is a test coverage program. Use it in concert with GCC to
+analyze your programs to help create more efficient, faster running
+code and to discover untested parts of your program. You can use
+`gcov' as a profiling tool to help discover where your optimization
+efforts will best affect your code. You can also use `gcov' along with
+the other profiling tool, `gprof', to assess which parts of your code
+use the greatest amount of computing time.
Profiling tools help you analyze your code's performance. Using a
-profiler such as 'gcov' or 'gprof', you can find out some basic
+profiler such as `gcov' or `gprof', you can find out some basic
performance statistics, such as:
* how often each line of code executes
@@ -43678,7 +44130,7 @@ performance statistics, such as:
Once you know these things about how your code works when compiled, you
can look at each module to see which modules should be optimized.
-'gcov' helps you determine where to work on optimization.
+`gcov' helps you determine where to work on optimization.
Software developers also use coverage testing in concert with
testsuites, to make sure software is actually good enough for a release.
@@ -43689,113 +44141,114 @@ to be added to the testsuites to create both better testing and a better
final product.
You should compile your code without optimization if you plan to use
-'gcov' because the optimization, by combining some lines of code into
+`gcov' because the optimization, by combining some lines of code into
one function, may not give you as much information as you need to look
-for 'hot spots' where the code is using a great deal of computer time.
-Likewise, because 'gcov' accumulates statistics by line (at the lowest
-resolution), it works best with a programming style that places only one
-statement on each line. If you use complicated macros that expand to
-loops or to other control structures, the statistics are less
+for `hot spots' where the code is using a great deal of computer time.
+Likewise, because `gcov' accumulates statistics by line (at the lowest
+resolution), it works best with a programming style that places only
+one statement on each line. If you use complicated macros that expand
+to loops or to other control structures, the statistics are less
helpful--they only report on the line where the macro call appears. If
your complex macros behave like functions, you can replace them with
inline functions to solve this problem.
- 'gcov' creates a logfile called 'SOURCEFILE.gcov' which indicates how
-many times each line of a source file 'SOURCEFILE.c' has executed. You
-can use these logfiles along with 'gprof' to aid in fine-tuning the
-performance of your programs. 'gprof' gives timing information you can
-use along with the information you get from 'gcov'.
+ `gcov' creates a logfile called `SOURCEFILE.gcov' which indicates how
+many times each line of a source file `SOURCEFILE.c' has executed. You
+can use these logfiles along with `gprof' to aid in fine-tuning the
+performance of your programs. `gprof' gives timing information you can
+use along with the information you get from `gcov'.
- 'gcov' works only on code compiled with GCC. It is not compatible with
-any other profiling or test coverage mechanism.
+ `gcov' works only on code compiled with GCC. It is not compatible
+with any other profiling or test coverage mechanism.

File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov Intro, Up: Gcov
-10.2 Invoking 'gcov'
+10.2 Invoking `gcov'
====================
gcov [OPTIONS] FILES
- 'gcov' accepts the following options:
+ `gcov' accepts the following options:
-'-h'
-'--help'
- Display help about using 'gcov' (on the standard output), and exit
+`-h'
+`--help'
+ Display help about using `gcov' (on the standard output), and exit
without doing any further processing.
-'-v'
-'--version'
- Display the 'gcov' version number (on the standard output), and
+`-v'
+`--version'
+ Display the `gcov' version number (on the standard output), and
exit without doing any further processing.
-'-a'
-'--all-blocks'
+`-a'
+`--all-blocks'
Write individual execution counts for every basic block. Normally
gcov outputs execution counts only for the main blocks of a line.
With this option you can determine if blocks within a single line
are not being executed.
-'-b'
-'--branch-probabilities'
+`-b'
+`--branch-probabilities'
Write branch frequencies to the output file, and write branch
- summary info to the standard output. This option allows you to see
- how often each branch in your program was taken. Unconditional
- branches will not be shown, unless the '-u' option is given.
+ summary info to the standard output. This option allows you to
+ see how often each branch in your program was taken.
+ Unconditional branches will not be shown, unless the `-u' option
+ is given.
-'-c'
-'--branch-counts'
+`-c'
+`--branch-counts'
Write branch frequencies as the number of branches taken, rather
than the percentage of branches taken.
-'-n'
-'--no-output'
- Do not create the 'gcov' output file.
+`-n'
+`--no-output'
+ Do not create the `gcov' output file.
-'-l'
-'--long-file-names'
+`-l'
+`--long-file-names'
Create long file names for included source files. For example, if
- the header file 'x.h' contains code, and was included in the file
- 'a.c', then running 'gcov' on the file 'a.c' will produce an output
- file called 'a.c##x.h.gcov' instead of 'x.h.gcov'. This can be
- useful if 'x.h' is included in multiple source files and you want
- to see the individual contributions. If you use the '-p' option,
- both the including and included file names will be complete path
- names.
-
-'-p'
-'--preserve-paths'
+ the header file `x.h' contains code, and was included in the file
+ `a.c', then running `gcov' on the file `a.c' will produce an
+ output file called `a.c##x.h.gcov' instead of `x.h.gcov'. This
+ can be useful if `x.h' is included in multiple source files and
+ you want to see the individual contributions. If you use the `-p'
+ option, both the including and included file names will be
+ complete path names.
+
+`-p'
+`--preserve-paths'
Preserve complete path information in the names of generated
- '.gcov' files. Without this option, just the filename component is
- used. With this option, all directories are used, with '/'
- characters translated to '#' characters, '.' directory components
- removed and unremoveable '..' components renamed to '^'. This is
+ `.gcov' files. Without this option, just the filename component is
+ used. With this option, all directories are used, with `/'
+ characters translated to `#' characters, `.' directory components
+ removed and unremoveable `..' components renamed to `^'. This is
useful if sourcefiles are in several different directories.
-'-r'
-'--relative-only'
+`-r'
+`--relative-only'
Only output information about source files with a relative pathname
(after source prefix elision). Absolute paths are usually system
header files and coverage of any inline functions therein is
normally uninteresting.
-'-f'
-'--function-summaries'
+`-f'
+`--function-summaries'
Output summaries for each function in addition to the file level
summary.
-'-o DIRECTORY|FILE'
-'--object-directory DIRECTORY'
-'--object-file FILE'
+`-o DIRECTORY|FILE'
+`--object-directory DIRECTORY'
+`--object-file FILE'
Specify either the directory containing the gcov data files, or the
- object path name. The '.gcno', and '.gcda' data files are searched
- for using this option. If a directory is specified, the data files
- are in that directory and named after the input file name, without
- its extension. If a file is specified here, the data files are
- named after that file, without its extension.
-
-'-s DIRECTORY'
-'--source-prefix DIRECTORY'
+ object path name. The `.gcno', and `.gcda' data files are
+ searched for using this option. If a directory is specified, the
+ data files are in that directory and named after the input file
+ name, without its extension. If a file is specified here, the
+ data files are named after that file, without its extension.
+
+`-s DIRECTORY'
+`--source-prefix DIRECTORY'
A prefix for source file names to remove when generating the output
coverage files. This option is useful when building in a separate
directory, and the pathname to the source directory is not wanted
@@ -43803,22 +44256,23 @@ File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov
detection is applied before determining whether the source file is
absolute.
-'-u'
-'--unconditional-branches'
- When branch probabilities are given, include those of unconditional
- branches. Unconditional branches are normally not interesting.
+`-u'
+`--unconditional-branches'
+ When branch probabilities are given, include those of
+ unconditional branches. Unconditional branches are normally not
+ interesting.
-'-d'
-'--display-progress'
+`-d'
+`--display-progress'
Display the progress on the standard output.
-'-i'
-'--intermediate-format'
+`-i'
+`--intermediate-format'
Output gcov file in an easy-to-parse intermediate text format that
- can be used by 'lcov' or other tools. The output is a single
- '.gcov' file per '.gcda' file. No source code is required.
+ can be used by `lcov' or other tools. The output is a single
+ `.gcov' file per `.gcda' file. No source code is required.
- The format of the intermediate '.gcov' file is plain text with one
+ The format of the intermediate `.gcov' file is plain text with one
entry per line
file:SOURCE_FILE_NAME
@@ -43835,7 +44289,7 @@ File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov
file. All entries following a FILE pertain to that source file
until the next FILE entry.
- Here is a sample when '-i' is used in conjunction with '-b' option:
+ Here is a sample when `-i' is used in conjunction with `-b' option:
file:array.cc
function:11,1,_Z3sumRKSt6vectorIPiSaIS0_EE
@@ -43847,73 +44301,75 @@ File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov
lcount:26,1
branch:28,nottaken
-'-m'
-'--demangled-names'
- Display demangled function names in output. The default is to show
+`-m'
+`--demangled-names'
+ Display demangled function names in output. The default is to show
mangled function names.
- 'gcov' should be run with the current directory the same as that when
+
+ `gcov' should be run with the current directory the same as that when
you invoked the compiler. Otherwise it will not be able to locate the
-source files. 'gcov' produces files called 'MANGLEDNAME.gcov' in the
-current directory. These contain the coverage information of the source
-file they correspond to. One '.gcov' file is produced for each source
-(or header) file containing code, which was compiled to produce the data
-files. The MANGLEDNAME part of the output file name is usually simply
-the source file name, but can be something more complicated if the '-l'
-or '-p' options are given. Refer to those options for details.
-
- If you invoke 'gcov' with multiple input files, the contributions from
-each input file are summed. Typically you would invoke it with the same
-list of files as the final link of your executable.
-
- The '.gcov' files contain the ':' separated fields along with program
+source files. `gcov' produces files called `MANGLEDNAME.gcov' in the
+current directory. These contain the coverage information of the
+source file they correspond to. One `.gcov' file is produced for each
+source (or header) file containing code, which was compiled to produce
+the data files. The MANGLEDNAME part of the output file name is
+usually simply the source file name, but can be something more
+complicated if the `-l' or `-p' options are given. Refer to those
+options for details.
+
+ If you invoke `gcov' with multiple input files, the contributions from
+each input file are summed. Typically you would invoke it with the
+same list of files as the final link of your executable.
+
+ The `.gcov' files contain the `:' separated fields along with program
source code. The format is
EXECUTION_COUNT:LINE_NUMBER:SOURCE LINE TEXT
Additional block information may succeed each line, when requested by
-command line option. The EXECUTION_COUNT is '-' for lines containing no
-code. Unexecuted lines are marked '#####' or '====', depending on
+command line option. The EXECUTION_COUNT is `-' for lines containing
+no code. Unexecuted lines are marked `#####' or `====', depending on
whether they are reachable by non-exceptional paths or only exceptional
paths such as C++ exception handlers, respectively.
- Some lines of information at the start have LINE_NUMBER of zero. These
-preamble lines are of the form
+ Some lines of information at the start have LINE_NUMBER of zero.
+These preamble lines are of the form
-:0:TAG:VALUE
The ordering and number of these preamble lines will be augmented as
-'gcov' development progresses -- do not rely on them remaining
+`gcov' development progresses -- do not rely on them remaining
unchanged. Use TAG to locate a particular preamble line.
The additional block information is of the form
TAG INFORMATION
- The INFORMATION is human readable, but designed to be simple enough for
-machine parsing too.
+ The INFORMATION is human readable, but designed to be simple enough
+for machine parsing too.
When printing percentages, 0% and 100% are only printed when the values
are _exactly_ 0% and 100% respectively. Other values which would
conventionally be rounded to 0% or 100% are instead printed as the
nearest non-boundary value.
- When using 'gcov', you must first compile your program with two special
-GCC options: '-fprofile-arcs -ftest-coverage'. This tells the compiler
-to generate additional information needed by gcov (basically a flow
-graph of the program) and also includes additional code in the object
-files for generating the extra profiling information needed by gcov.
-These additional files are placed in the directory where the object file
-is located.
+ When using `gcov', you must first compile your program with two
+special GCC options: `-fprofile-arcs -ftest-coverage'. This tells the
+compiler to generate additional information needed by gcov (basically a
+flow graph of the program) and also includes additional code in the
+object files for generating the extra profiling information needed by
+gcov. These additional files are placed in the directory where the
+object file is located.
Running the program will cause profile output to be generated. For
-each source file compiled with '-fprofile-arcs', an accompanying '.gcda'
-file will be placed in the object file directory.
+each source file compiled with `-fprofile-arcs', an accompanying
+`.gcda' file will be placed in the object file directory.
- Running 'gcov' with your program's source file names as arguments will
+ Running `gcov' with your program's source file names as arguments will
now produce a listing of the code along with frequency of execution for
-each line. For example, if your program is called 'tmp.c', this is what
-you see when you use the basic 'gcov' facility:
+each line. For example, if your program is called `tmp.c', this is
+what you see when you use the basic `gcov' facility:
$ gcc -fprofile-arcs -ftest-coverage tmp.c
$ a.out
@@ -43921,7 +44377,7 @@ you see when you use the basic 'gcov' facility:
90.00% of 10 source lines executed in file tmp.c
Creating tmp.c.gcov.
- The file 'tmp.c.gcov' contains output from 'gcov'. Here is a sample:
+ The file `tmp.c.gcov' contains output from `gcov'. Here is a sample:
-: 0:Source:tmp.c
-: 0:Graph:tmp.gcno
@@ -43946,8 +44402,8 @@ you see when you use the basic 'gcov' facility:
1: 16: return 0;
-: 17:}
- When you use the '-a' option, you will get individual block counts, and
-the output looks like this:
+ When you use the `-a' option, you will get individual block counts,
+and the output looks like this:
-: 0:Source:tmp.c
-: 0:Graph:tmp.gcno
@@ -43986,13 +44442,13 @@ contain code, unless previous blocks end on those lines. The total
execution count of a line is shown and subsequent lines show the
execution counts for individual blocks that end on that line. After
each block, the branch and call counts of the block will be shown, if
-the '-b' option is given.
+the `-b' option is given.
Because of the way GCC instruments calls, a call count can be shown
after a line with no individual blocks. As you can see, line 13
contains a basic block that was not executed.
- When you use the '-b' option, your output looks like this:
+ When you use the `-b' option, your output looks like this:
$ gcov -b tmp.c
90.00% of 10 source lines executed in file tmp.c
@@ -44001,7 +44457,7 @@ contains a basic block that was not executed.
50.00% of 2 calls executed in file tmp.c
Creating tmp.c.gcov.
- Here is a sample of a resulting 'tmp.c.gcov' file:
+ Here is a sample of a resulting `tmp.c.gcov' file:
-: 0:Source:tmp.c
-: 0:Graph:tmp.gcno
@@ -44039,12 +44495,12 @@ function's blocks were executed.
For each basic block, a line is printed after the last line of the
basic block describing the branch or call that ends the basic block.
-There can be multiple branches and calls listed for a single source line
-if there are multiple basic blocks that end on that line. In this case,
-the branches and calls are each given a number. There is no simple way
-to map these branches and calls back to source constructs. In general,
-though, the lowest numbered branch or call will correspond to the
-leftmost construct on the source line.
+There can be multiple branches and calls listed for a single source
+line if there are multiple basic blocks that end on that line. In this
+case, the branches and calls are each given a number. There is no
+simple way to map these branches and calls back to source constructs.
+In general, though, the lowest numbered branch or call will correspond
+to the leftmost construct on the source line.
For a branch, if it was executed at least once, then a percentage
indicating the number of times the branch was taken divided by the
@@ -44054,11 +44510,11 @@ message "never executed" is printed.
For a call, if it was executed at least once, then a percentage
indicating the number of times the call returned divided by the number
of times the call was executed will be printed. This will usually be
-100%, but may be less for functions that call 'exit' or 'longjmp', and
+100%, but may be less for functions that call `exit' or `longjmp', and
thus may not return every time they are called.
The execution counts are cumulative. If the example program were
-executed again without removing the '.gcda' file, the count for the
+executed again without removing the `.gcda' file, the count for the
number of times each line in the source was executed would be added to
the results of the previous run(s). This is potentially useful in
several ways. For example, it could be used to accumulate data over a
@@ -44066,9 +44522,9 @@ number of program runs as part of a test verification suite, or to
provide more accurate long-term information over a large number of
program runs.
- The data in the '.gcda' files is saved immediately before the program
-exits. For each source file compiled with '-fprofile-arcs', the
-profiling code first attempts to read in an existing '.gcda' file; if
+ The data in the `.gcda' files is saved immediately before the program
+exits. For each source file compiled with `-fprofile-arcs', the
+profiling code first attempts to read in an existing `.gcda' file; if
the file doesn't match the executable (differing number of basic block
counts) it will ignore the contents of the file. It then adds in the
new execution counts and finally writes the data to the file.
@@ -44076,15 +44532,15 @@ new execution counts and finally writes the data to the file.

File: gcc.info, Node: Gcov and Optimization, Next: Gcov Data Files, Prev: Invoking Gcov, Up: Gcov
-10.3 Using 'gcov' with GCC Optimization
+10.3 Using `gcov' with GCC Optimization
=======================================
-If you plan to use 'gcov' to help optimize your code, you must first
-compile your program with two special GCC options: '-fprofile-arcs
+If you plan to use `gcov' to help optimize your code, you must first
+compile your program with two special GCC options: `-fprofile-arcs
-ftest-coverage'. Aside from that, you can use any other GCC options;
but if you want to prove that every single line in your program was
-executed, you should not compile with optimization at the same time. On
-some machines the optimizer can eliminate some simple code lines by
+executed, you should not compile with optimization at the same time.
+On some machines the optimizer can eliminate some simple code lines by
combining them with other lines. For example, code like this:
if (a != b)
@@ -44093,9 +44549,9 @@ combining them with other lines. For example, code like this:
c = 0;
can be compiled into one instruction on some machines. In this case,
-there is no way for 'gcov' to calculate separate execution counts for
+there is no way for `gcov' to calculate separate execution counts for
each line because there isn't separate code for each line. Hence the
-'gcov' output looks like this if you compiled the program with
+`gcov' output looks like this if you compiled the program with
optimization:
100: 12:if (a != b)
@@ -44115,15 +44571,15 @@ shown depends on where the function is inlined, or if it is not inlined
at all.
If the function is not inlined, the compiler must emit an out of line
-copy of the function, in any object file that needs it. If 'fileA.o'
-and 'fileB.o' both contain out of line bodies of a particular inlineable
-function, they will also both contain coverage counts for that function.
-When 'fileA.o' and 'fileB.o' are linked together, the linker will, on
-many systems, select one of those out of line bodies for all calls to
-that function, and remove or ignore the other. Unfortunately, it will
-not remove the coverage counters for the unused function body. Hence
-when instrumented, all but one use of that function will show zero
-counts.
+copy of the function, in any object file that needs it. If `fileA.o'
+and `fileB.o' both contain out of line bodies of a particular
+inlineable function, they will also both contain coverage counts for
+that function. When `fileA.o' and `fileB.o' are linked together, the
+linker will, on many systems, select one of those out of line bodies
+for all calls to that function, and remove or ignore the other.
+Unfortunately, it will not remove the coverage counters for the unused
+function body. Hence when instrumented, all but one use of that
+function will show zero counts.
If the function is inlined in several places, the block structure in
each location might not be the same. For instance, a condition might
@@ -44131,40 +44587,40 @@ now be calculable at compile time in some instances. Because the
coverage of all the uses of the inline function will be shown for the
same source lines, the line counts themselves might seem inconsistent.
- Long-running applications can use the '_gcov_reset' and '_gcov_dump'
+ Long-running applications can use the `_gcov_reset' and `_gcov_dump'
facilities to restrict profile collection to the program region of
-interest. Calling '_gcov_reset(void)' will clear all profile counters
-to zero, and calling '_gcov_dump(void)' will cause the profile
-information collected at that point to be dumped to '.gcda' output
+interest. Calling `_gcov_reset(void)' will clear all profile counters
+to zero, and calling `_gcov_dump(void)' will cause the profile
+information collected at that point to be dumped to `.gcda' output
files.

File: gcc.info, Node: Gcov Data Files, Next: Cross-profiling, Prev: Gcov and Optimization, Up: Gcov
-10.4 Brief Description of 'gcov' Data Files
+10.4 Brief Description of `gcov' Data Files
===========================================
-'gcov' uses two files for profiling. The names of these files are
+`gcov' uses two files for profiling. The names of these files are
derived from the original _object_ file by substituting the file suffix
-with either '.gcno', or '.gcda'. The files contain coverage and profile
-data stored in a platform-independent format. The '.gcno' files are
-placed in the same directory as the object file. By default, the
-'.gcda' files are also stored in the same directory as the object file,
-but the GCC '-fprofile-dir' option may be used to store the '.gcda'
-files in a separate directory.
-
- The '.gcno' notes file is generated when the source file is compiled
-with the GCC '-ftest-coverage' option. It contains information to
+with either `.gcno', or `.gcda'. The files contain coverage and
+profile data stored in a platform-independent format. The `.gcno'
+files are placed in the same directory as the object file. By default,
+the `.gcda' files are also stored in the same directory as the object
+file, but the GCC `-fprofile-dir' option may be used to store the
+`.gcda' files in a separate directory.
+
+ The `.gcno' notes file is generated when the source file is compiled
+with the GCC `-ftest-coverage' option. It contains information to
reconstruct the basic block graphs and assign source line numbers to
blocks.
- The '.gcda' count data file is generated when a program containing
-object files built with the GCC '-fprofile-arcs' option is executed. A
-separate '.gcda' file is created for each object file compiled with this
-option. It contains arc transition counts, value profile counts, and
-some summary information.
+ The `.gcda' count data file is generated when a program containing
+object files built with the GCC `-fprofile-arcs' option is executed. A
+separate `.gcda' file is created for each object file compiled with
+this option. It contains arc transition counts, value profile counts,
+and some summary information.
- The full details of the file format is specified in 'gcov-io.h', and
+ The full details of the file format is specified in `gcov-io.h', and
functions provided in that header file should be used to access the
coverage files.
@@ -44175,46 +44631,46 @@ File: gcc.info, Node: Cross-profiling, Prev: Gcov Data Files, Up: Gcov
====================================================
Running the program will cause profile output to be generated. For each
-source file compiled with '-fprofile-arcs', an accompanying '.gcda' file
-will be placed in the object file directory. That implicitly requires
-running the program on the same system as it was built or having the
-same absolute directory structure on the target system. The program
-will try to create the needed directory structure, if it is not already
-present.
-
- To support cross-profiling, a program compiled with '-fprofile-arcs'
+source file compiled with `-fprofile-arcs', an accompanying `.gcda'
+file will be placed in the object file directory. That implicitly
+requires running the program on the same system as it was built or
+having the same absolute directory structure on the target system. The
+program will try to create the needed directory structure, if it is not
+already present.
+
+ To support cross-profiling, a program compiled with `-fprofile-arcs'
can relocate the data files based on two environment variables:
- * GCOV_PREFIX contains the prefix to add to the absolute paths in the
- object file. Prefix can be absolute, or relative. The default is
- no prefix.
+ * GCOV_PREFIX contains the prefix to add to the absolute paths in
+ the object file. Prefix can be absolute, or relative. The default
+ is no prefix.
- * GCOV_PREFIX_STRIP indicates the how many initial directory names to
- strip off the hardwired absolute paths. Default value is 0.
+ * GCOV_PREFIX_STRIP indicates the how many initial directory names
+ to strip off the hardwired absolute paths. Default value is 0.
_Note:_ If GCOV_PREFIX_STRIP is set without GCOV_PREFIX is
- undefined, then a relative path is made out of the hardwired
+ undefined, then a relative path is made out of the hardwired
absolute paths.
- For example, if the object file '/user/build/foo.o' was built with
-'-fprofile-arcs', the final executable will try to create the data file
-'/user/build/foo.gcda' when running on the target system. This will
+ For example, if the object file `/user/build/foo.o' was built with
+`-fprofile-arcs', the final executable will try to create the data file
+`/user/build/foo.gcda' when running on the target system. This will
fail if the corresponding directory does not exist and it is unable to
create it. This can be overcome by, for example, setting the
-environment as 'GCOV_PREFIX=/target/run' and 'GCOV_PREFIX_STRIP=1'.
-Such a setting will name the data file '/target/run/build/foo.gcda'.
+environment as `GCOV_PREFIX=/target/run' and `GCOV_PREFIX_STRIP=1'.
+Such a setting will name the data file `/target/run/build/foo.gcda'.
You must move the data files to the expected directory tree in order to
-use them for profile directed optimizations ('--use-profile'), or to use
-the 'gcov' tool.
+use them for profile directed optimizations (`--use-profile'), or to
+use the `gcov' tool.

File: gcc.info, Node: Gcov-tool, Next: Trouble, Prev: Gcov, Up: Top
-11 'gcov-tool'--an Offline Gcda Profile Processing Tool
+11 `gcov-tool'--an Offline Gcda Profile Processing Tool
*******************************************************
-'gcov-tool' is a tool you can use in conjunction with GCC to manipulate
+`gcov-tool' is a tool you can use in conjunction with GCC to manipulate
or process gcda profile files offline.
* Menu:
@@ -44225,21 +44681,21 @@ or process gcda profile files offline.

File: gcc.info, Node: Gcov-tool Intro, Next: Invoking Gcov-tool, Up: Gcov-tool
-11.1 Introduction to 'gcov-tool'
+11.1 Introduction to `gcov-tool'
================================
-'gcov-tool' is an offline tool to process gcc's gcda profile files.
+`gcov-tool' is an offline tool to process gcc's gcda profile files.
Current gcov-tool supports the following functionalities:
* merge two sets of profiles with weights.
- * read one set of profile and rewrite profile contents. One can
+ * read one set of profile and rewrite profile contents. One can
scale or normalize the count values.
Examples of the use cases for this tool are:
- * Collect the profiles for different set of inputs, and use this tool
- to merge them. One can specify the weight to factor in the
+ * Collect the profiles for different set of inputs, and use this
+ tool to merge them. One can specify the weight to factor in the
relative importance of each input.
* Rewrite the profile after removing a subset of the gcda files,
@@ -44249,129 +44705,130 @@ File: gcc.info, Node: Gcov-tool Intro, Next: Invoking Gcov-tool, Up: Gcov-too
the majority code as the runtime library.
Note that for the merging operation, this profile generated offline may
-contain slight different values from the online merged profile. Here
-are a list of typical differences:
+contain slight different values from the online merged profile. Here are
+a list of typical differences:
* histogram difference: This offline tool recomputes the histogram
- after merging the counters. The resulting histogram, therefore, is
- precise. The online merging does not have this capability - the
+ after merging the counters. The resulting histogram, therefore, is
+ precise. The online merging does not have this capability - the
histogram is merged from two histograms and the result is an
approximation.
* summary checksum difference: Summary checksum uses a CRC32
- operation. The value depends on the link list order of gcov-info
- objects. This order is different in gcov-tool from that in the
- online merge. It's expected to have different summary checksums.
+ operation. The value depends on the link list order of gcov-info
+ objects. This order is different in gcov-tool from that in the
+ online merge. It's expected to have different summary checksums.
It does not really matter as the compiler does not use this
checksum anywhere.
* value profile counter values difference: Some counter values for
- value profile are runtime dependent, like heap addresses. It's
+ value profile are runtime dependent, like heap addresses. It's
normal to see some difference in these kind of counters.

File: gcc.info, Node: Invoking Gcov-tool, Prev: Gcov-tool Intro, Up: Gcov-tool
-11.2 Invoking 'gcov-tool'
+11.2 Invoking `gcov-tool'
=========================
gcov-tool [GLOBAL-OPTIONS] SUB_COMMAND [SUB_COMMAND-OPTIONS] PROFILE_DIR
- 'gcov-tool' accepts the following options:
+ `gcov-tool' accepts the following options:
-'-h'
-'--help'
- Display help about using 'gcov-tool' (on the standard output), and
+`-h'
+`--help'
+ Display help about using `gcov-tool' (on the standard output), and
exit without doing any further processing.
-'-v'
-'--version'
- Display the 'gcov-tool' version number (on the standard output),
+`-v'
+`--version'
+ Display the `gcov-tool' version number (on the standard output),
and exit without doing any further processing.
-'merge'
+`merge'
Merge two profile directories.
- '-v'
- '--verbose'
+ `-v'
+ `--verbose'
Set the verbose mode.
- '-o DIRECTORY'
- '--output DIRECTORY'
- Set the output profile directory. Default output directory
+ `-o DIRECTORY'
+ `--output DIRECTORY'
+ Set the output profile directory. Default output directory
name is MERGED_PROFILE.
- '-w W1,W2'
- '--weight W1,W2'
+ `-w W1,W2'
+ `--weight W1,W2'
Set the merge weights of the DIRECTORY1 and DIRECTORY2,
- respectively. The default weights are 1 for both.
+ respectively. The default weights are 1 for both.
-'rewrite'
+`rewrite'
Read the specified profile directory and rewrite to a new
directory.
- '-v'
- '--verbose'
+ `-v'
+ `--verbose'
Set the verbose mode.
- '-o DIRECTORY'
- '--output DIRECTORY'
- Set the output profile directory. Default output name is
+ `-o DIRECTORY'
+ `--output DIRECTORY'
+ Set the output profile directory. Default output name is
REWRITE_PROFILE.
- '-s FLOAT_OR_SIMPLE-FRAC_VALUE'
- '--scale FLOAT_OR_SIMPLE-FRAC_VALUE'
- Scale the profile counters. The specified value can be in
+ `-s FLOAT_OR_SIMPLE-FRAC_VALUE'
+ `--scale FLOAT_OR_SIMPLE-FRAC_VALUE'
+ Scale the profile counters. The specified value can be in
floating point value, or simple fraction value form, such 1,
2, 2/3, and 5/3.
- '-n LONG_LONG_VALUE'
- '--normalize <long_long_value>'
- Normalize the profile. The specified value is the max counter
+ `-n LONG_LONG_VALUE'
+ `--normalize <long_long_value>'
+ Normalize the profile. The specified value is the max counter
value in the new profile.
-'overlap'
+`overlap'
Computer the overlap score between the two specified profile
directories. The overlap score is computed based on the arc
- profiles. It is defined as the sum of min (p1_counter[i] /
+ profiles. It is defined as the sum of min (p1_counter[i] /
p1_sum_all, p2_counter[i] / p2_sum_all), for all arc counter i,
where p1_counter[i] and p2_counter[i] are two matched counters and
p1_sum_all and p2_sum_all are the sum of counter values in profile
1 and profile 2, respectively.
- '-v'
- '--verbose'
+ `-v'
+ `--verbose'
Set the verbose mode.
- '-h'
- '--hotonly'
+ `-h'
+ `--hotonly'
Only print info for hot objects/functions.
- '-f'
- '--function'
+ `-f'
+ `--function'
Print function level overlap score.
- '-F'
- '--fullname'
+ `-F'
+ `--fullname'
Print full gcda filename.
- '-o'
- '--object'
+ `-o'
+ `--object'
Print object level overlap score.
- '-t FLOAT'
- '--hot_threshold <float>'
+ `-t FLOAT'
+ `--hot_threshold <float>'
Set the threshold for hot counter value.
+

File: gcc.info, Node: Trouble, Next: Bugs, Prev: Gcov-tool, Up: Top
12 Known Causes of Trouble with GCC
***********************************
-This section describes known problems that affect users of GCC. Most of
-these are not GCC bugs per se--if they were, we would fix them. But the
-result for a user may be like the result of a bug.
+This section describes known problems that affect users of GCC. Most
+of these are not GCC bugs per se--if they were, we would fix them. But
+the result for a user may be like the result of a bug.
Some of these problems are due to bugs in other software, some are
missing features that are too much work to add, and some are places
@@ -44399,9 +44856,9 @@ File: gcc.info, Node: Actual Bugs, Next: Interoperation, Up: Trouble
12.1 Actual Bugs We Haven't Fixed Yet
=====================================
- * The 'fixincludes' script interacts badly with automounters; if the
+ * The `fixincludes' script interacts badly with automounters; if the
directory of system header files is automounted, it tends to be
- unmounted while 'fixincludes' is running. This would seem to be a
+ unmounted while `fixincludes' is running. This would seem to be a
bug in the automounter. We don't know any good way to work around
it.
@@ -44412,12 +44869,12 @@ File: gcc.info, Node: Interoperation, Next: Incompatibilities, Prev: Actual B
===================
This section lists various difficulties encountered in using GCC
-together with other compilers or with the assemblers, linkers, libraries
-and debuggers on certain systems.
+together with other compilers or with the assemblers, linkers,
+libraries and debuggers on certain systems.
* On many platforms, GCC supports a different ABI for C++ than do
- other compilers, so the object files compiled by GCC cannot be used
- with object files generated by another C++ compiler.
+ other compilers, so the object files compiled by GCC cannot be
+ used with object files generated by another C++ compiler.
An area where the difference is most apparent is name mangling.
The use of different name mangling is intentional, to protect you
@@ -44434,14 +44891,14 @@ and debuggers on certain systems.
profiling causes static variable destructors (currently used only
in C++) not to be run.
- * On a SPARC, GCC aligns all values of type 'double' on an 8-byte
- boundary, and it expects every 'double' to be so aligned. The Sun
- compiler usually gives 'double' values 8-byte alignment, with one
- exception: function arguments of type 'double' may not be aligned.
+ * On a SPARC, GCC aligns all values of type `double' on an 8-byte
+ boundary, and it expects every `double' to be so aligned. The Sun
+ compiler usually gives `double' values 8-byte alignment, with one
+ exception: function arguments of type `double' may not be aligned.
As a result, if a function compiled with Sun CC takes the address
- of an argument of type 'double' and passes this pointer of type
- 'double *' to a function compiled with GCC, dereferencing the
+ of an argument of type `double' and passes this pointer of type
+ `double *' to a function compiled with GCC, dereferencing the
pointer may cause a fatal signal.
One way to solve this problem is to compile your entire program
@@ -44449,8 +44906,8 @@ and debuggers on certain systems.
compiled with Sun CC to copy the argument into a local variable;
local variables are always properly aligned. A third solution is
to modify the function that uses the pointer to dereference it via
- the following function 'access_double' instead of directly with
- '*':
+ the following function `access_double' instead of directly with
+ `*':
inline double
access_double (double *unaligned_ptr)
@@ -44468,27 +44925,27 @@ and debuggers on certain systems.
Storing into the pointer can be done likewise with the same union.
- * On Solaris, the 'malloc' function in the 'libmalloc.a' library may
+ * On Solaris, the `malloc' function in the `libmalloc.a' library may
allocate memory that is only 4 byte aligned. Since GCC on the
SPARC assumes that doubles are 8 byte aligned, this may result in a
fatal signal if doubles are stored in memory allocated by the
- 'libmalloc.a' library.
+ `libmalloc.a' library.
- The solution is to not use the 'libmalloc.a' library. Use instead
- 'malloc' and related functions from 'libc.a'; they do not have this
- problem.
+ The solution is to not use the `libmalloc.a' library. Use instead
+ `malloc' and related functions from `libc.a'; they do not have
+ this problem.
* On the HP PA machine, ADB sometimes fails to work on functions
compiled with GCC. Specifically, it fails to work on functions
- that use 'alloca' or variable-size arrays. This is because GCC
+ that use `alloca' or variable-size arrays. This is because GCC
doesn't generate HP-UX unwind descriptors for such functions. It
may even be impossible to generate them.
- * Debugging ('-g') is not supported on the HP PA machine, unless you
+ * Debugging (`-g') is not supported on the HP PA machine, unless you
use the preliminary GNU tools.
- * Taking the address of a label may generate errors from the HP-UX PA
- assembler. GAS for the PA does not have this problem.
+ * Taking the address of a label may generate errors from the HP-UX
+ PA assembler. GAS for the PA does not have this problem.
* Using floating point parameters for indirect calls to static
functions will not work when using the HP assembler. There simply
@@ -44499,12 +44956,12 @@ and debuggers on certain systems.
* In extremely rare cases involving some very large functions you may
receive errors from the HP linker complaining about an out of
bounds unconditional branch offset. This used to occur more often
- in previous versions of GCC, but is now exceptionally rare. If you
- should run into it, you can work around by making your function
- smaller.
+ in previous versions of GCC, but is now exceptionally rare. If
+ you should run into it, you can work around by making your
+ function smaller.
- * GCC compiled code sometimes emits warnings from the HP-UX assembler
- of the form:
+ * GCC compiled code sometimes emits warnings from the HP-UX
+ assembler of the form:
(warning) Use of GR3 when
frame >= 8192 may cause conflict.
@@ -44513,43 +44970,44 @@ and debuggers on certain systems.
* In extremely rare cases involving some very large functions you may
receive errors from the AIX Assembler complaining about a
- displacement that is too large. If you should run into it, you can
- work around by making your function smaller.
+ displacement that is too large. If you should run into it, you
+ can work around by making your function smaller.
- * The 'libstdc++.a' library in GCC relies on the SVR4 dynamic linker
+ * The `libstdc++.a' library in GCC relies on the SVR4 dynamic linker
semantics which merges global symbols between libraries and
applications, especially necessary for C++ streams functionality.
This is not the default behavior of AIX shared libraries and
- dynamic linking. 'libstdc++.a' is built on AIX with
+ dynamic linking. `libstdc++.a' is built on AIX with
"runtime-linking" enabled so that symbol merging can occur. To
- utilize this feature, the application linked with 'libstdc++.a'
- must include the '-Wl,-brtl' flag on the link line. G++ cannot
- impose this because this option may interfere with the semantics of
- the user program and users may not always use 'g++' to link his or
- her application. Applications are not required to use the
- '-Wl,-brtl' flag on the link line--the rest of the 'libstdc++.a'
- library which is not dependent on the symbol merging semantics will
- continue to function correctly.
+ utilize this feature, the application linked with `libstdc++.a'
+ must include the `-Wl,-brtl' flag on the link line. G++ cannot
+ impose this because this option may interfere with the semantics
+ of the user program and users may not always use `g++' to link his
+ or her application. Applications are not required to use the
+ `-Wl,-brtl' flag on the link line--the rest of the `libstdc++.a'
+ library which is not dependent on the symbol merging semantics
+ will continue to function correctly.
* An application can interpose its own definition of functions for
- functions invoked by 'libstdc++.a' with "runtime-linking" enabled
+ functions invoked by `libstdc++.a' with "runtime-linking" enabled
on AIX. To accomplish this the application must be linked with
"runtime-linking" option and the functions explicitly must be
- exported by the application ('-Wl,-brtl,-bE:exportfile').
+ exported by the application (`-Wl,-brtl,-bE:exportfile').
* AIX on the RS/6000 provides support (NLS) for environments outside
of the United States. Compilers and assemblers use NLS to support
locale-specific representations of various objects including
- floating-point numbers ('.' vs ',' for separating decimal
+ floating-point numbers (`.' vs `,' for separating decimal
fractions). There have been problems reported where the library
linked with GCC does not produce the same floating-point formats
that the assembler accepts. If you have this problem, set the
- 'LANG' environment variable to 'C' or 'En_US'.
+ `LANG' environment variable to `C' or `En_US'.
- * Even if you specify '-fdollars-in-identifiers', you cannot
- successfully use '$' in identifiers on the RS/6000 due to a
+ * Even if you specify `-fdollars-in-identifiers', you cannot
+ successfully use `$' in identifiers on the RS/6000 due to a
restriction in the IBM assembler. GAS supports these identifiers.
+

File: gcc.info, Node: Incompatibilities, Next: Fixed Headers, Prev: Interoperation, Up: Trouble
@@ -44563,23 +45021,23 @@ There are several noteworthy incompatibilities between GNU C and K&R
identical-looking string constants are used, GCC stores only one
copy of the string.
- One consequence is that you cannot call 'mktemp' with a string
- constant argument. The function 'mktemp' always alters the string
+ One consequence is that you cannot call `mktemp' with a string
+ constant argument. The function `mktemp' always alters the string
its argument points to.
- Another consequence is that 'sscanf' does not work on some very old
- systems when passed a string constant as its format control string
- or input. This is because 'sscanf' incorrectly tries to write into
- the string constant. Likewise 'fscanf' and 'scanf'.
+ Another consequence is that `sscanf' does not work on some very
+ old systems when passed a string constant as its format control
+ string or input. This is because `sscanf' incorrectly tries to
+ write into the string constant. Likewise `fscanf' and `scanf'.
The solution to these problems is to change the program to use
- 'char'-array variables with initialization strings for these
+ `char'-array variables with initialization strings for these
purposes instead of string constants.
- * '-2147483648' is positive.
+ * `-2147483648' is positive.
- This is because 2147483648 cannot fit in the type 'int', so
- (following the ISO C rules) its data type is 'unsigned long int'.
+ This is because 2147483648 cannot fit in the type `int', so
+ (following the ISO C rules) its data type is `unsigned long int'.
Negating this value yields 2147483648 again.
* GCC does not substitute macro arguments when they appear inside of
@@ -44587,10 +45045,10 @@ There are several noteworthy incompatibilities between GNU C and K&R
#define foo(a) "a"
- will produce output '"a"' regardless of what the argument A is.
+ will produce output `"a"' regardless of what the argument A is.
- * When you use 'setjmp' and 'longjmp', the only automatic variables
- guaranteed to remain valid are those declared 'volatile'. This is
+ * When you use `setjmp' and `longjmp', the only automatic variables
+ guaranteed to remain valid are those declared `volatile'. This is
a consequence of automatic register allocation. Consider this
function:
@@ -44605,16 +45063,16 @@ There are several noteworthy incompatibilities between GNU C and K&R
return a;
a = fun2 ();
- /* 'longjmp (j)' may occur in 'fun3'. */
+ /* `longjmp (j)' may occur in `fun3'. */
return a + fun3 ();
}
- Here 'a' may or may not be restored to its first value when the
- 'longjmp' occurs. If 'a' is allocated in a register, then its
+ Here `a' may or may not be restored to its first value when the
+ `longjmp' occurs. If `a' is allocated in a register, then its
first value is restored; otherwise, it keeps the last value stored
in it.
- If you use the '-W' option with the '-O' option, you will get a
+ If you use the `-W' option with the `-O' option, you will get a
warning when GCC thinks such a problem might be possible.
* Programs that use preprocessing directives in the middle of macro
@@ -44635,17 +45093,17 @@ There are several noteworthy incompatibilities between GNU C and K&R
words, they have the same scope as any other declaration in the
same place.
- In some other C compilers, an 'extern' declaration affects all the
+ In some other C compilers, an `extern' declaration affects all the
rest of the file even if it happens within a block.
- * In traditional C, you can combine 'long', etc., with a typedef
+ * In traditional C, you can combine `long', etc., with a typedef
name, as shown here:
typedef int foo;
typedef long foo bar;
- In ISO C, this is not allowed: 'long' and other type modifiers
- require an explicit 'int'.
+ In ISO C, this is not allowed: `long' and other type modifiers
+ require an explicit `int'.
* PCC allows typedef names to be used as function parameters.
@@ -44655,15 +45113,15 @@ There are several noteworthy incompatibilities between GNU C and K&R
typedef int foo;
typedef foo foo;
- * GCC treats all characters of identifiers as significant. According
- to K&R-1 (2.2), "No more than the first eight characters are
- significant, although more may be used.". Also according to K&R-1
- (2.2), "An identifier is a sequence of letters and digits; the
- first character must be a letter. The underscore _ counts as a
- letter.", but GCC also allows dollar signs in identifiers.
+ * GCC treats all characters of identifiers as significant.
+ According to K&R-1 (2.2), "No more than the first eight characters
+ are significant, although more may be used.". Also according to
+ K&R-1 (2.2), "An identifier is a sequence of letters and digits;
+ the first character must be a letter. The underscore _ counts as
+ a letter.", but GCC also allows dollar signs in identifiers.
* PCC allows whitespace in the middle of compound assignment
- operators such as '+='. GCC, following the ISO standard, does not
+ operators such as `+='. GCC, following the ISO standard, does not
allow this.
* GCC complains about unterminated character constants inside of
@@ -44677,24 +45135,24 @@ There are several noteworthy incompatibilities between GNU C and K&R
#endif
The best solution to such a problem is to put the text into an
- actual C comment delimited by '/*...*/'.
+ actual C comment delimited by `/*...*/'.
- * Many user programs contain the declaration 'long time ();'. In the
+ * Many user programs contain the declaration `long time ();'. In the
past, the system header files on many systems did not actually
- declare 'time', so it did not matter what type your program
- declared it to return. But in systems with ISO C headers, 'time'
- is declared to return 'time_t', and if that is not the same as
- 'long', then 'long time ();' is erroneous.
+ declare `time', so it did not matter what type your program
+ declared it to return. But in systems with ISO C headers, `time'
+ is declared to return `time_t', and if that is not the same as
+ `long', then `long time ();' is erroneous.
The solution is to change your program to use appropriate system
- headers ('<time.h>' on systems with ISO C headers) and not to
- declare 'time' if the system header files declare it, or failing
- that to use 'time_t' as the return type of 'time'.
+ headers (`<time.h>' on systems with ISO C headers) and not to
+ declare `time' if the system header files declare it, or failing
+ that to use `time_t' as the return type of `time'.
- * When compiling functions that return 'float', PCC converts it to a
- double. GCC actually returns a 'float'. If you are concerned with
- PCC compatibility, you should declare your functions to return
- 'double'; you might as well say what you mean.
+ * When compiling functions that return `float', PCC converts it to a
+ double. GCC actually returns a `float'. If you are concerned
+ with PCC compatibility, you should declare your functions to return
+ `double'; you might as well say what you mean.
* When compiling functions that return structures or unions, GCC
output code normally uses a method different from that used on most
@@ -44703,10 +45161,10 @@ There are several noteworthy incompatibilities between GNU C and K&R
The method used by GCC is as follows: a structure or union which is
1, 2, 4 or 8 bytes long is returned like a scalar. A structure or
- union with any other size is stored into an address supplied by the
- caller (usually in a special, fixed register, but on some machines
- it is passed on the stack). The target hook
- 'TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address.
+ union with any other size is stored into an address supplied by
+ the caller (usually in a special, fixed register, but on some
+ machines it is passed on the stack). The target hook
+ `TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address.
By contrast, PCC on most target machines returns structures and
unions of any size by copying the data into an area of static
@@ -44721,25 +45179,25 @@ There are several noteworthy incompatibilities between GNU C and K&R
memory, but still returns small structures and unions in registers.
You can tell GCC to use a compatible convention for all structure
- and union returning with the option '-fpcc-struct-return'.
+ and union returning with the option `-fpcc-struct-return'.
- * GCC complains about program fragments such as '0x74ae-0x4000' which
- appear to be two hexadecimal constants separated by the minus
+ * GCC complains about program fragments such as `0x74ae-0x4000'
+ which appear to be two hexadecimal constants separated by the minus
operator. Actually, this string is a single "preprocessing token".
- Each such token must correspond to one token in C. Since this does
- not, GCC prints an error message. Although it may appear obvious
- that what is meant is an operator and two values, the ISO C
- standard specifically requires that this be treated as erroneous.
+ Each such token must correspond to one token in C. Since this
+ does not, GCC prints an error message. Although it may appear
+ obvious that what is meant is an operator and two values, the ISO
+ C standard specifically requires that this be treated as erroneous.
A "preprocessing token" is a "preprocessing number" if it begins
with a digit and is followed by letters, underscores, digits,
- periods and 'e+', 'e-', 'E+', 'E-', 'p+', 'p-', 'P+', or 'P-'
- character sequences. (In strict C90 mode, the sequences 'p+',
- 'p-', 'P+' and 'P-' cannot appear in preprocessing numbers.)
+ periods and `e+', `e-', `E+', `E-', `p+', `p-', `P+', or `P-'
+ character sequences. (In strict C90 mode, the sequences `p+',
+ `p-', `P+' and `P-' cannot appear in preprocessing numbers.)
- To make the above program fragment valid, place whitespace in front
- of the minus sign. This whitespace will end the preprocessing
- number.
+ To make the above program fragment valid, place whitespace in
+ front of the minus sign. This whitespace will end the
+ preprocessing number.

File: gcc.info, Node: Fixed Headers, Next: Standard Libraries, Prev: Incompatibilities, Up: Trouble
@@ -44754,14 +45212,14 @@ incompatible with ISO C, and some depend on special features of other
compilers.
Installing GCC automatically creates and installs the fixed header
-files, by running a program called 'fixincludes'. Normally, you don't
+files, by running a program called `fixincludes'. Normally, you don't
need to pay attention to this. But there are cases where it doesn't do
the right thing automatically.
* If you update the system's header files, such as by installing a
new system version, the fixed header files of GCC are not
- automatically updated. They can be updated using the 'mkheaders'
- script installed in 'LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'.
+ automatically updated. They can be updated using the `mkheaders'
+ script installed in `LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'.
* On some systems, header file directories contain machine-specific
symbolic links in certain places. This makes it possible to share
@@ -44770,12 +45228,13 @@ the right thing automatically.
The programs that fix the header files do not understand this
special way of using symbolic links; therefore, the directory of
- fixed header files is good only for the machine model used to build
- it.
+ fixed header files is good only for the machine model used to
+ build it.
It is possible to make separate sets of fixed header files for the
- different machine models, and arrange a structure of symbolic links
- so as to use the proper set, but you'll have to do this by hand.
+ different machine models, and arrange a structure of symbolic
+ links so as to use the proper set, but you'll have to do this by
+ hand.

File: gcc.info, Node: Standard Libraries, Next: Disappointments, Prev: Fixed Headers, Up: Trouble
@@ -44789,21 +45248,21 @@ what this means. Beyond the library facilities required of such an
implementation, the rest of the C library is supplied by the vendor of
the operating system. If that C library doesn't conform to the C
standards, then your programs might get warnings (especially when using
-'-Wall') that you don't expect.
+`-Wall') that you don't expect.
- For example, the 'sprintf' function on SunOS 4.1.3 returns 'char *'
-while the C standard says that 'sprintf' returns an 'int'. The
-'fixincludes' program could make the prototype for this function match
+ For example, the `sprintf' function on SunOS 4.1.3 returns `char *'
+while the C standard says that `sprintf' returns an `int'. The
+`fixincludes' program could make the prototype for this function match
the Standard, but that would be wrong, since the function will still
-return 'char *'.
+return `char *'.
If you need a Standard compliant library, then you need to find one, as
-GCC does not provide one. The GNU C library (called 'glibc') provides
+GCC does not provide one. The GNU C library (called `glibc') provides
ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and
HURD-based GNU systems; no recent version of it supports other systems,
though some very old versions did. Version 2.2 of the GNU C library
-includes nearly complete C99 support. You could also ask your operating
-system vendor if newer libraries are available.
+includes nearly complete C99 support. You could also ask your
+operating system vendor if newer libraries are available.

File: gcc.info, Node: Disappointments, Next: C++ Misunderstandings, Prev: Standard Libraries, Up: Trouble
@@ -44836,27 +45295,27 @@ way around them.
int foo (struct mumble *x)
{ ... }
- This code really is erroneous, because the scope of 'struct mumble'
- in the prototype is limited to the argument list containing it. It
- does not refer to the 'struct mumble' defined with file scope
- immediately below--they are two unrelated types with similar names
- in different scopes.
+ This code really is erroneous, because the scope of `struct
+ mumble' in the prototype is limited to the argument list
+ containing it. It does not refer to the `struct mumble' defined
+ with file scope immediately below--they are two unrelated types
+ with similar names in different scopes.
- But in the definition of 'foo', the file-scope type is used because
- that is available to be inherited. Thus, the definition and the
- prototype do not match, and you get an error.
+ But in the definition of `foo', the file-scope type is used
+ because that is available to be inherited. Thus, the definition
+ and the prototype do not match, and you get an error.
This behavior may seem silly, but it's what the ISO standard
specifies. It is easy enough for you to make your code work by
- moving the definition of 'struct mumble' above the prototype. It's
- not worth being incompatible with ISO C just to avoid an error for
- the example shown above.
+ moving the definition of `struct mumble' above the prototype.
+ It's not worth being incompatible with ISO C just to avoid an
+ error for the example shown above.
* Accesses to bit-fields even in volatile objects works by accessing
larger objects, such as a byte or a word. You cannot rely on what
- size of object is accessed in order to read or write the bit-field;
- it may even vary for a given bit-field according to the precise
- usage.
+ size of object is accessed in order to read or write the
+ bit-field; it may even vary for a given bit-field according to the
+ precise usage.
If you care about controlling the amount of memory that is
accessed, use volatile but do not use bit-fields.
@@ -44869,20 +45328,20 @@ way around them.
about.
If new system header files are installed, nothing automatically
- arranges to update the corrected header files. They can be updated
- using the 'mkheaders' script installed in
- 'LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'.
+ arranges to update the corrected header files. They can be
+ updated using the `mkheaders' script installed in
+ `LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'.
* On 68000 and x86 systems, for instance, you can get paradoxical
results if you test the precise values of floating point numbers.
For example, you can find that a floating point value which is not
a NaN is not equal to itself. This results from the fact that the
- floating point registers hold a few more bits of precision than fit
- in a 'double' in memory. Compiled code moves values between memory
- and floating point registers at its convenience, and moving them
- into memory truncates them.
+ floating point registers hold a few more bits of precision than
+ fit in a `double' in memory. Compiled code moves values between
+ memory and floating point registers at its convenience, and moving
+ them into memory truncates them.
- You can partially avoid this problem by using the '-ffloat-store'
+ You can partially avoid this problem by using the `-ffloat-store'
option (*note Optimize Options::).
* On AIX and other platforms without weak symbol support, templates
@@ -44934,19 +45393,19 @@ static member; you must also _define_ it. For example:
static int bar;
};
- This declaration only establishes that the class 'Foo' has an 'int'
-named 'Foo::bar', and a member function named 'Foo::method'. But you
-still need to define _both_ 'method' and 'bar' elsewhere. According to
+ This declaration only establishes that the class `Foo' has an `int'
+named `Foo::bar', and a member function named `Foo::method'. But you
+still need to define _both_ `method' and `bar' elsewhere. According to
the ISO standard, you must supply an initializer in one (and only one)
source file, such as:
int Foo::bar = 0;
Other C++ compilers may not correctly implement the standard behavior.
-As a result, when you switch to 'g++' from one of these compilers, you
-may discover that a program that appeared to work correctly in fact does
-not conform to the standard: 'g++' reports as undefined symbols any
-static data members that lack definitions.
+As a result, when you switch to `g++' from one of these compilers, you
+may discover that a program that appeared to work correctly in fact
+does not conform to the standard: `g++' reports as undefined symbols
+any static data members that lack definitions.

File: gcc.info, Node: Name lookup, Next: Temporaries, Prev: Static Definitions, Up: C++ Misunderstandings
@@ -44974,20 +45433,20 @@ looked up at the point of instantiation. For example, consider
static const int N;
};
- Here, the names 'foo' and 'N' appear in a context that does not depend
-on the type of 'T'. The compiler will thus require that they are
-defined in the context of use in the template, not only before the point
-of instantiation, and will here use '::foo(double)' and 'A::N',
+ Here, the names `foo' and `N' appear in a context that does not depend
+on the type of `T'. The compiler will thus require that they are
+defined in the context of use in the template, not only before the
+point of instantiation, and will here use `::foo(double)' and `A::N',
respectively. In particular, it will convert the integer value to a
-'double' when passing it to '::foo(double)'.
+`double' when passing it to `::foo(double)'.
- Conversely, 'bar' and the call to 'foo' in the fourth marked line are
-used in contexts that do depend on the type of 'T', so they are only
+ Conversely, `bar' and the call to `foo' in the fourth marked line are
+used in contexts that do depend on the type of `T', so they are only
looked up at the point of instantiation, and you can provide
declarations for them after declaring the template, but before
-instantiating it. In particular, if you instantiate 'A::f<int>', the
-last line will call an overloaded '::foo(int)' if one was provided, even
-if after the declaration of 'struct A'.
+instantiating it. In particular, if you instantiate `A::f<int>', the
+last line will call an overloaded `::foo(int)' if one was provided,
+even if after the declaration of `struct A'.
This distinction between lookup of dependent and non-dependent names is
called two-stage (or dependent) name lookup. G++ implements it since
@@ -45004,21 +45463,21 @@ different from non-template codes. The most common is probably this:
int get_i() { return i; }
};
- In 'get_i()', 'i' is not used in a dependent context, so the compiler
-will look for a name declared at the enclosing namespace scope (which is
-the global scope here). It will not look into the base class, since
-that is dependent and you may declare specializations of 'Base' even
-after declaring 'Derived', so the compiler can't really know what 'i'
-would refer to. If there is no global variable 'i', then you will get
+ In `get_i()', `i' is not used in a dependent context, so the compiler
+will look for a name declared at the enclosing namespace scope (which
+is the global scope here). It will not look into the base class, since
+that is dependent and you may declare specializations of `Base' even
+after declaring `Derived', so the compiler can't really know what `i'
+would refer to. If there is no global variable `i', then you will get
an error message.
In order to make it clear that you want the member of the base class,
you need to defer lookup until instantiation time, at which the base
-class is known. For this, you need to access 'i' in a dependent
-context, by either using 'this->i' (remember that 'this' is of type
-'Derived<T>*', so is obviously dependent), or using 'Base<T>::i'.
-Alternatively, 'Base<T>::i' might be brought into scope by a
-'using'-declaration.
+class is known. For this, you need to access `i' in a dependent
+context, by either using `this->i' (remember that `this' is of type
+`Derived<T>*', so is obviously dependent), or using `Base<T>::i'.
+Alternatively, `Base<T>::i' might be brought into scope by a
+`using'-declaration.
Another, similar example involves calling member functions of a base
class:
@@ -45031,8 +45490,8 @@ class:
int g() { return f(); };
};
- Again, the call to 'f()' is not dependent on template arguments (there
-are no arguments that depend on the type 'T', and it is also not
+ Again, the call to `f()' is not dependent on template arguments (there
+are no arguments that depend on the type `T', and it is also not
otherwise specified that the call should be in a dependent context).
Thus a global declaration of such a function must be available, since
the one in the base class is not visible until instantiation time. The
@@ -45044,22 +45503,22 @@ compiler will consequently produce the following error message:
x.cc:6: error: (if you use `-fpermissive', G++ will accept your code, but
allowing the use of an undeclared name is deprecated)
- To make the code valid either use 'this->f()', or 'Base<T>::f()'.
-Using the '-fpermissive' flag will also let the compiler accept the
+ To make the code valid either use `this->f()', or `Base<T>::f()'.
+Using the `-fpermissive' flag will also let the compiler accept the
code, by marking all function calls for which no declaration is visible
at the time of definition of the template for later lookup at
-instantiation time, as if it were a dependent call. We do not recommend
-using '-fpermissive' to work around invalid code, and it will also only
-catch cases where functions in base classes are called, not where
-variables in base classes are used (as in the example above).
+instantiation time, as if it were a dependent call. We do not
+recommend using `-fpermissive' to work around invalid code, and it will
+also only catch cases where functions in base classes are called, not
+where variables in base classes are used (as in the example above).
Note that some compilers (including G++ versions prior to 3.4) get
these examples wrong and accept above code without an error. Those
compilers do not implement two-stage name lookup correctly.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) The C++ standard just uses the term "dependent" for names that
+ (1) The C++ standard just uses the term "dependent" for names that
depend on the type or value of template parameters. This shorter term
will also be used in the rest of this section.
@@ -45073,15 +45532,15 @@ It is dangerous to use pointers or references to _portions_ of a
temporary object. The compiler may very well delete the object before
you expect it to, leaving a pointer to garbage. The most common place
where this problem crops up is in classes like string classes,
-especially ones that define a conversion function to type 'char *' or
-'const char *'--which is one reason why the standard 'string' class
-requires you to call the 'c_str' member function. However, any class
-that returns a pointer to some internal structure is potentially subject
-to this problem.
+especially ones that define a conversion function to type `char *' or
+`const char *'--which is one reason why the standard `string' class
+requires you to call the `c_str' member function. However, any class
+that returns a pointer to some internal structure is potentially
+subject to this problem.
- For example, a program may use a function 'strfunc' that returns
-'string' objects, and another function 'charfunc' that operates on
-pointers to 'char':
+ For example, a program may use a function `strfunc' that returns
+`string' objects, and another function `charfunc' that operates on
+pointers to `char':
string strfunc ();
void charfunc (const char *);
@@ -45097,10 +45556,10 @@ pointers to 'char':
}
In this situation, it may seem reasonable to save a pointer to the C
-string returned by the 'c_str' member function and use that rather than
-call 'c_str' repeatedly. However, the temporary string created by the
-call to 'strfunc' is destroyed after 'p' is initialized, at which point
-'p' is left pointing to freed memory.
+string returned by the `c_str' member function and use that rather than
+call `c_str' repeatedly. However, the temporary string created by the
+call to `strfunc' is destroyed after `p' is initialized, at which point
+`p' is left pointing to freed memory.
Code like this may run successfully under some other compilers,
particularly obsolete cfront-based compilers that delete temporaries
@@ -45154,17 +45613,17 @@ such objects behave unspecified when being assigned. For example:
d1 = d2;
}
- The C++ standard specifies that 'Base::Base' is only called once when
+ The C++ standard specifies that `Base::Base' is only called once when
constructing or copy-constructing a Derived object. It is unspecified
-whether 'Base::operator=' is called more than once when the implicit
-copy-assignment for Derived objects is invoked (as it is inside 'func'
+whether `Base::operator=' is called more than once when the implicit
+copy-assignment for Derived objects is invoked (as it is inside `func'
in the example).
G++ implements the "intuitive" algorithm for copy-assignment: assign
all direct bases, then assign all members. In that algorithm, the
virtual base subobject can be encountered more than once. In the
-example, copying proceeds in the following order: 'val', 'name' (via
-'strdup'), 'bval', and 'name' again.
+example, copying proceeds in the following order: `val', `name' (via
+`strdup'), `bval', and `name' again.
If application code relies on copy-assignment, a user-defined
copy-assignment operator removes any uncertainties. With such an
@@ -45203,17 +45662,17 @@ do not make because we think GCC is better without them.
* Warning when a non-void function value is ignored.
C contains many standard functions that return a value that most
- programs choose to ignore. One obvious example is 'printf'.
+ programs choose to ignore. One obvious example is `printf'.
Warning about this practice only leads the defensive programmer to
- clutter programs with dozens of casts to 'void'. Such casts are
+ clutter programs with dozens of casts to `void'. Such casts are
required so frequently that they become visual noise. Writing
those casts becomes so automatic that they no longer convey useful
information about the intentions of the programmer. For functions
where the return value should never be ignored, use the
- 'warn_unused_result' function attribute (*note Function
+ `warn_unused_result' function attribute (*note Function
Attributes::).
- * Making '-fshort-enums' the default.
+ * Making `-fshort-enums' the default.
This would cause storage layout to be incompatible with most other
C compilers. And it doesn't seem very important, given that you
@@ -45225,16 +45684,16 @@ do not make because we think GCC is better without them.
"the ABI standard" says to do so.
The ISO C standard leaves it up to the implementation whether a
- bit-field declared plain 'int' is signed or not. This in effect
+ bit-field declared plain `int' is signed or not. This in effect
creates two alternative dialects of C.
The GNU C compiler supports both dialects; you can specify the
- signed dialect with '-fsigned-bitfields' and the unsigned dialect
- with '-funsigned-bitfields'. However, this leaves open the
+ signed dialect with `-fsigned-bitfields' and the unsigned dialect
+ with `-funsigned-bitfields'. However, this leaves open the
question of which dialect to use by default.
Currently, the preferred dialect makes plain bit-fields signed,
- because this is simplest. Since 'int' is the same as 'signed int'
+ because this is simplest. Since `int' is the same as `signed int'
in every other context, it is cleanest for them to be the same in
bit-fields as well.
@@ -45255,15 +45714,15 @@ do not make because we think GCC is better without them.
Many users appreciate the GNU C compiler because it provides an
environment that is uniform across machines. These users would be
- inconvenienced if the compiler treated plain bit-fields differently
- on certain machines.
+ inconvenienced if the compiler treated plain bit-fields
+ differently on certain machines.
Occasionally users write programs intended only for a particular
machine type. On these occasions, the users would benefit if the
GNU C compiler were to support by default the same dialect as the
other compilers on that machine. But such applications are rare.
- And users writing a program to run on more than one type of machine
- cannot possibly benefit from this kind of compatibility.
+ And users writing a program to run on more than one type of
+ machine cannot possibly benefit from this kind of compatibility.
This is why GCC does and will treat plain bit-fields in the same
fashion on all types of machines (by default).
@@ -45278,60 +45737,60 @@ do not make because we think GCC is better without them.
In this way, they write programs which have the same meaning in
both C dialects.)
- * Undefining '__STDC__' when '-ansi' is not used.
+ * Undefining `__STDC__' when `-ansi' is not used.
- Currently, GCC defines '__STDC__' unconditionally. This provides
+ Currently, GCC defines `__STDC__' unconditionally. This provides
good results in practice.
- Programmers normally use conditionals on '__STDC__' to ask whether
+ Programmers normally use conditionals on `__STDC__' to ask whether
it is safe to use certain features of ISO C, such as function
- prototypes or ISO token concatenation. Since plain 'gcc' supports
+ prototypes or ISO token concatenation. Since plain `gcc' supports
all the features of ISO C, the correct answer to these questions is
"yes".
- Some users try to use '__STDC__' to check for the availability of
- certain library facilities. This is actually incorrect usage in an
- ISO C program, because the ISO C standard says that a conforming
- freestanding implementation should define '__STDC__' even though it
- does not have the library facilities. 'gcc -ansi -pedantic' is a
+ Some users try to use `__STDC__' to check for the availability of
+ certain library facilities. This is actually incorrect usage in
+ an ISO C program, because the ISO C standard says that a conforming
+ freestanding implementation should define `__STDC__' even though it
+ does not have the library facilities. `gcc -ansi -pedantic' is a
conforming freestanding implementation, and it is therefore
- required to define '__STDC__', even though it does not come with an
- ISO C library.
+ required to define `__STDC__', even though it does not come with
+ an ISO C library.
- Sometimes people say that defining '__STDC__' in a compiler that
+ Sometimes people say that defining `__STDC__' in a compiler that
does not completely conform to the ISO C standard somehow violates
the standard. This is illogical. The standard is a standard for
- compilers that claim to support ISO C, such as 'gcc -ansi'--not for
- other compilers such as plain 'gcc'. Whatever the ISO C standard
- says is relevant to the design of plain 'gcc' without '-ansi' only
- for pragmatic reasons, not as a requirement.
+ compilers that claim to support ISO C, such as `gcc -ansi'--not
+ for other compilers such as plain `gcc'. Whatever the ISO C
+ standard says is relevant to the design of plain `gcc' without
+ `-ansi' only for pragmatic reasons, not as a requirement.
- GCC normally defines '__STDC__' to be 1, and in addition defines
- '__STRICT_ANSI__' if you specify the '-ansi' option, or a '-std'
+ GCC normally defines `__STDC__' to be 1, and in addition defines
+ `__STRICT_ANSI__' if you specify the `-ansi' option, or a `-std'
option for strict conformance to some version of ISO C. On some
hosts, system include files use a different convention, where
- '__STDC__' is normally 0, but is 1 if the user specifies strict
+ `__STDC__' is normally 0, but is 1 if the user specifies strict
conformance to the C Standard. GCC follows the host convention
when processing system include files, but when processing user
files it follows the usual GNU C convention.
- * Undefining '__STDC__' in C++.
+ * Undefining `__STDC__' in C++.
- Programs written to compile with C++-to-C translators get the value
- of '__STDC__' that goes with the C compiler that is subsequently
- used. These programs must test '__STDC__' to determine what kind
- of C preprocessor that compiler uses: whether they should
- concatenate tokens in the ISO C fashion or in the traditional
- fashion.
+ Programs written to compile with C++-to-C translators get the
+ value of `__STDC__' that goes with the C compiler that is
+ subsequently used. These programs must test `__STDC__' to
+ determine what kind of C preprocessor that compiler uses: whether
+ they should concatenate tokens in the ISO C fashion or in the
+ traditional fashion.
- These programs work properly with GNU C++ if '__STDC__' is defined.
+ These programs work properly with GNU C++ if `__STDC__' is defined.
They would not work otherwise.
- In addition, many header files are written to provide prototypes in
- ISO C but not in traditional C. Many of these header files can
- work without change in C++ provided '__STDC__' is defined. If
- '__STDC__' is not defined, they will all fail, and will all need to
- be changed to test explicitly for C++ as well.
+ In addition, many header files are written to provide prototypes
+ in ISO C but not in traditional C. Many of these header files can
+ work without change in C++ provided `__STDC__' is defined. If
+ `__STDC__' is not defined, they will all fail, and will all need
+ to be changed to test explicitly for C++ as well.
* Deleting "empty" loops.
@@ -45341,7 +45800,7 @@ do not make because we think GCC is better without them.
programs run any faster.
However, the rationale here is that optimization of a nonempty loop
- cannot produce an empty one. This held for carefully written C
+ cannot produce an empty one. This held for carefully written C
compiled with less powerful optimizers but is not always the case
for carefully written C++ or with more powerful optimizers. Thus
GCC will remove operations from loops whenever it can determine
@@ -45351,7 +45810,7 @@ do not make because we think GCC is better without them.
Be aware of this when performing timing tests, for instance the
following loop can be completely removed, provided
- 'some_expression' can provably not change any global state.
+ `some_expression' can provably not change any global state.
{
int sum = 0;
@@ -45361,7 +45820,7 @@ do not make because we think GCC is better without them.
sum += some_expression;
}
- Even though 'sum' is accumulated in the loop, no use is made of
+ Even though `sum' is accumulated in the loop, no use is made of
that summation, so the accumulation can be removed.
* Making side effects happen in the same order as in some other
@@ -45378,9 +45837,9 @@ do not make because we think GCC is better without them.
There is no guarantee (in either the C or the C++ standard language
definitions) that the increments will be evaluated in any
- particular order. Either increment might happen first. 'func'
- might get the arguments '2, 3', or it might get '3, 2', or even '2,
- 2'.
+ particular order. Either increment might happen first. `func'
+ might get the arguments `2, 3', or it might get `3, 2', or even
+ `2, 2'.
* Making certain warnings into errors by default.
@@ -45388,11 +45847,12 @@ do not make because we think GCC is better without them.
produce an error message for a certain program.
ISO C requires a "diagnostic" message for certain kinds of invalid
- programs, but a warning is defined by GCC to count as a diagnostic.
- If GCC produces a warning but not an error, that is correct ISO C
- support. If testsuites call this "failure", they should be run
- with the GCC option '-pedantic-errors', which will turn these
- warnings into errors.
+ programs, but a warning is defined by GCC to count as a
+ diagnostic. If GCC produces a warning but not an error, that is
+ correct ISO C support. If testsuites call this "failure", they
+ should be run with the GCC option `-pedantic-errors', which will
+ turn these warnings into errors.
+

File: gcc.info, Node: Warnings and Errors, Prev: Non-bugs, Up: Trouble
@@ -45410,23 +45870,23 @@ warnings. Each kind has a different purpose:
"Warnings" report other unusual conditions in your code that _may_
indicate a problem, although compilation can (and does) proceed.
Warning messages also report the source file name and line number,
- but include the text 'warning:' to distinguish them from error
+ but include the text `warning:' to distinguish them from error
messages.
Warnings may indicate danger points where you should check to make sure
that your program really does what you intend; or the use of obsolete
features; or the use of nonstandard features of GNU C or C++. Many
-warnings are issued only if you ask for them, with one of the '-W'
-options (for instance, '-Wall' requests a variety of useful warnings).
+warnings are issued only if you ask for them, with one of the `-W'
+options (for instance, `-Wall' requests a variety of useful warnings).
GCC always tries to compile your program if possible; it never
gratuitously rejects a program whose meaning is clear merely because
(for instance) it fails to conform to a standard. In some cases,
however, the C and C++ standards specify that certain extensions are
forbidden, and a diagnostic _must_ be issued by a conforming compiler.
-The '-pedantic' option tells GCC to issue warnings in such cases;
-'-pedantic-errors' says to make them errors instead. This does not mean
-that _all_ non-ISO constructs get warnings or errors.
+The `-pedantic' option tells GCC to issue warnings in such cases;
+`-pedantic-errors' says to make them errors instead. This does not
+mean that _all_ non-ISO constructs get warnings or errors.
*Note Options to Request or Suppress Warnings: Warning Options, for
more detail on these and related command-line options.
@@ -45461,7 +45921,7 @@ guidelines:
is a compiler bug. Reliable compilers never crash.
* If the compiler produces invalid assembly code, for any input
- whatever (except an 'asm' statement), that is a compiler bug,
+ whatever (except an `asm' statement), that is a compiler bug,
unless the compiler reports errors (not just warnings) which would
ordinarily prevent the assembler from being run.
@@ -45472,13 +45932,13 @@ guidelines:
program whose behavior is undefined, which happened by chance to
give the desired results with another C or C++ compiler.
- For example, in many nonoptimizing compilers, you can write 'x;' at
- the end of a function instead of 'return x;', with the same
- results. But the value of the function is undefined if 'return' is
- omitted; it is not a bug when GCC produces different results.
+ For example, in many nonoptimizing compilers, you can write `x;'
+ at the end of a function instead of `return x;', with the same
+ results. But the value of the function is undefined if `return'
+ is omitted; it is not a bug when GCC produces different results.
Problems often result from expressions with two increment
- operators, as in 'f (*p++, *p++)'. Your previous compiler might
+ operators, as in `f (*p++, *p++)'. Your previous compiler might
have interpreted that expression the way you intended; GCC might
interpret it another way. Neither compiler is wrong. The bug is
in your code.
@@ -45506,7 +45966,7 @@ File: gcc.info, Node: Bug Reporting, Prev: Bug Criteria, Up: Bugs
=================================
Bugs should be reported to the bug database at
-<http://gcc.gnu.org/bugs.html>.
+`http://gcc.gnu.org/bugs.html'.

File: gcc.info, Node: Service, Next: Contributing, Prev: Bugs, Up: Top
@@ -45526,9 +45986,9 @@ to find it:
* Look in the service directory for someone who might help you for a
fee. The service directory is found at
- <http://www.fsf.org/resources/service>.
+ `http://www.fsf.org/resources/service'.
- For further information, see <http://gcc.gnu.org/faq.html#support>.
+ For further information, see `http://gcc.gnu.org/faq.html#support'.

File: gcc.info, Node: Contributing, Next: Funding, Prev: Service, Up: Top
@@ -45538,18 +45998,18 @@ File: gcc.info, Node: Contributing, Next: Funding, Prev: Service, Up: Top
If you would like to help pretest GCC releases to assure they work well,
current development sources are available by SVN (see
-<http://gcc.gnu.org/svn.html>). Source and binary snapshots are also
-available for FTP; see <http://gcc.gnu.org/snapshots.html>.
+`http://gcc.gnu.org/svn.html'). Source and binary snapshots are also
+available for FTP; see `http://gcc.gnu.org/snapshots.html'.
If you would like to work on improvements to GCC, please read the
advice at these URLs:
- <http://gcc.gnu.org/contribute.html>
- <http://gcc.gnu.org/contributewhy.html>
+ `http://gcc.gnu.org/contribute.html'
+ `http://gcc.gnu.org/contributewhy.html'
for information on how to make useful contributions and avoid
duplication of effort. Suggested projects are listed at
-<http://gcc.gnu.org/projects/>.
+`http://gcc.gnu.org/projects/'.

File: gcc.info, Node: Funding, Next: GNU Project, Prev: Contributing, Up: Top
@@ -45568,8 +46028,8 @@ to free software developers--the Free Software Foundation, and others.
The way to convince distributors to do this is to demand it and expect
it from them. So when you compare distributors, judge them partly by
-how much they give to free software development. Show distributors they
-must compete to be the one who gives the most.
+how much they give to free software development. Show distributors
+they must compete to be the one who gives the most.
To make this approach work, you must insist on numbers that you can
compare, such as, "We will donate ten dollars to the Frobnitz project
@@ -45579,8 +46039,8 @@ for comparison.
Even a precise fraction "of the profits from this disk" is not very
meaningful, since creative accounting and unrelated business decisions
-can greatly alter what fraction of the sales price counts as profit. If
-the price you pay is $50, ten percent of the profit is probably less
+can greatly alter what fraction of the sales price counts as profit.
+If the price you pay is $50, ten percent of the profit is probably less
than a dollar; it might be a few cents, or nothing at all.
Some redistributors do development work themselves. This is useful
@@ -45590,8 +46050,8 @@ difference than others. For example, maintaining a separate version of
a program contributes very little; maintaining the standard version of a
program for the whole community contributes much. Easy new ports
contribute little, since someone else would surely do them; difficult
-ports such as adding a new CPU to the GNU Compiler Collection contribute
-more; major new features or packages contribute the most.
+ports such as adding a new CPU to the GNU Compiler Collection
+contribute more; major new features or packages contribute the most.
By establishing the idea that supporting further development is "the
proper thing to do" when distributing free software for a fee, we can
@@ -45615,8 +46075,8 @@ now widely used; though these systems are often referred to as "Linux",
they are more accurately called GNU/Linux systems.
For more information, see:
- <http://www.gnu.org/>
- <http://www.gnu.org/gnu/linux-and-gnu.html>
+ `http://www.gnu.org/'
+ `http://www.gnu.org/gnu/linux-and-gnu.html'

File: gcc.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top
@@ -45626,7 +46086,7 @@ GNU General Public License
Version 3, 29 June 2007
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
@@ -45646,27 +46106,27 @@ GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
- When we speak of free software, we are referring to freedom, not price.
-Our General Public Licenses are designed to make sure that you have the
-freedom to distribute copies of free software (and charge for them if
-you wish), that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs, and that you know you can do these things.
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
+these rights or asking you to surrender the rights. Therefore, you
+have certain responsibilities if you distribute copies of the software,
+or if you modify it: responsibilities to respect the freedom of others.
- For example, if you distribute copies of such a program, whether gratis
-or for a fee, you must pass on to the recipients the same freedoms that
-you received. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
- Developers that use the GNU GPL protect your rights with two steps: (1)
-assert copyright on the software, and (2) offer you this License giving
-you legal permission to copy, distribute and/or modify it.
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
@@ -45675,15 +46135,16 @@ changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so. This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software. The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products. If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
+modified versions of the software inside them, although the
+manufacturer can do so. This is fundamentally incompatible with the
+aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for
+individuals to use, which is precisely where it is most unacceptable.
+Therefore, we have designed this version of the GPL to prohibit the
+practice for those products. If such problems arise substantially in
+other domains, we stand ready to extend this provision to those domains
+in future versions of the GPL, as needed to protect the freedom of
+users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
@@ -45720,8 +46181,8 @@ TERMS AND CONDITIONS
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
- infringement under applicable copyright law, except executing it on
- a computer or modifying a private copy. Propagation includes
+ infringement under applicable copyright law, except executing it
+ on a computer or modifying a private copy. Propagation includes
copying, distribution (with or without modification), making
available to the public, and in some countries other activities as
well.
@@ -45735,8 +46196,8 @@ TERMS AND CONDITIONS
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to
- the extent that warranties are provided), that licensees may convey
- the work under this License, and how to view a copy of this
+ the extent that warranties are provided), that licensees may
+ convey the work under this License, and how to view a copy of this
License. If the interface presents a list of user commands or
options, such as a menu, a prominent item in the list meets this
criterion.
@@ -45744,8 +46205,8 @@ TERMS AND CONDITIONS
1. Source Code.
The "source code" for a work means the preferred form of the work
- for making modifications to it. "Object code" means any non-source
- form of a work.
+ for making modifications to it. "Object code" means any
+ non-source form of a work.
A "Standard Interface" means an interface that either is an
official standard defined by a recognized standards body, or, in
@@ -45756,10 +46217,10 @@ TERMS AND CONDITIONS
The "System Libraries" of an executable work include anything,
other than the work as a whole, that (a) is included in the normal
form of packaging a Major Component, but which is not part of that
- Major Component, and (b) serves only to enable use of the work with
- that Major Component, or to implement a Standard Interface for
- which an implementation is available to the public in source code
- form. A "Major Component", in this context, means a major
+ Major Component, and (b) serves only to enable use of the work
+ with that Major Component, or to implement a Standard Interface
+ for which an implementation is available to the public in source
+ code form. A "Major Component", in this context, means a major
essential component (kernel, window system, and so on) of the
specific operating system (if any) on which the executable work
runs, or a compiler used to produce the work, or an object code
@@ -45767,15 +46228,15 @@ TERMS AND CONDITIONS
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
- work) run the object code and to modify the work, including scripts
- to control those activities. However, it does not include the
- work's System Libraries, or general-purpose tools or generally
+ work) run the object code and to modify the work, including
+ scripts to control those activities. However, it does not include
+ the work's System Libraries, or general-purpose tools or generally
available free programs which are used unmodified in performing
those activities but which are not part of the work. For example,
- Corresponding Source includes interface definition files associated
- with source files for the work, and the source code for shared
- libraries and dynamically linked subprograms that the work is
- specifically designed to require, such as by intimate data
+ Corresponding Source includes interface definition files
+ associated with source files for the work, and the source code for
+ shared libraries and dynamically linked subprograms that the work
+ is specifically designed to require, such as by intimate data
communication or control flow between those subprograms and other
parts of the work.
@@ -45792,22 +46253,22 @@ TERMS AND CONDITIONS
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running
- a covered work is covered by this License only if the output, given
- its content, constitutes a covered work. This License acknowledges
- your rights of fair use or other equivalent, as provided by
- copyright law.
+ a covered work is covered by this License only if the output,
+ given its content, constitutes a covered work. This License
+ acknowledges your rights of fair use or other equivalent, as
+ provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise
remains in force. You may convey covered works to others for the
- sole purpose of having them make modifications exclusively for you,
- or provide you with facilities for running those works, provided
- that you comply with the terms of this License in conveying all
- material for which you do not control copyright. Those thus making
- or running the covered works for you must do so exclusively on your
- behalf, under your direction and control, on terms that prohibit
- them from making any copies of your copyrighted material outside
- their relationship with you.
+ sole purpose of having them make modifications exclusively for
+ you, or provide you with facilities for running those works,
+ provided that you comply with the terms of this License in
+ conveying all material for which you do not control copyright.
+ Those thus making or running the covered works for you must do so
+ exclusively on your behalf, under your direction and control, on
+ terms that prohibit them from making any copies of your
+ copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section
@@ -45824,8 +46285,8 @@ TERMS AND CONDITIONS
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License
- with respect to the covered work, and you disclaim any intention to
- limit operation or modification of the work as a means of
+ with respect to the covered work, and you disclaim any intention
+ to limit operation or modification of the work as a means of
enforcing, against the work's users, your or third parties' legal
rights to forbid circumvention of technological measures.
@@ -45895,8 +46356,8 @@ TERMS AND CONDITIONS
b. Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
- written offer, valid for at least three years and valid for as
- long as you offer spare parts or customer support for that
+ written offer, valid for at least three years and valid for
+ as long as you offer spare parts or customer support for that
product model, to give anyone who possesses the object code
either (1) a copy of the Corresponding Source for all the
software in the product that is covered by this License, on a
@@ -45906,31 +46367,32 @@ TERMS AND CONDITIONS
to copy the Corresponding Source from a network server at no
charge.
- c. Convey individual copies of the object code with a copy of the
- written offer to provide the Corresponding Source. This
+ c. Convey individual copies of the object code with a copy of
+ the written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially,
and only if you received the object code with such an offer,
in accord with subsection 6b.
d. Convey the object code by offering access from a designated
- place (gratis or for a charge), and offer equivalent access to
- the Corresponding Source in the same way through the same
+ place (gratis or for a charge), and offer equivalent access
+ to the Corresponding Source in the same way through the same
place at no further charge. You need not require recipients
to copy the Corresponding Source along with the object code.
If the place to copy the object code is a network server, the
- Corresponding Source may be on a different server (operated by
- you or a third party) that supports equivalent copying
- facilities, provided you maintain clear directions next to the
- object code saying where to find the Corresponding Source.
+ Corresponding Source may be on a different server (operated
+ by you or a third party) that supports equivalent copying
+ facilities, provided you maintain clear directions next to
+ the object code saying where to find the Corresponding Source.
Regardless of what server hosts the Corresponding Source, you
- remain obligated to ensure that it is available for as long as
- needed to satisfy these requirements.
+ remain obligated to ensure that it is available for as long
+ as needed to satisfy these requirements.
e. Convey the object code using peer-to-peer transmission,
provided you inform other peers where the object code and
Corresponding Source of the work are being offered to the
general public at no charge under subsection 6d.
+
A separable portion of the object code, whose source code is
excluded from the Corresponding Source as a System Library, need
not be included in conveying the object code work.
@@ -45938,8 +46400,8 @@ TERMS AND CONDITIONS
A "User Product" is either (1) a "consumer product", which means
any tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
- incorporation into a dwelling. In determining whether a product is
- a consumer product, doubtful cases shall be resolved in favor of
+ incorporation into a dwelling. In determining whether a product
+ is a consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
"normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the
@@ -45970,11 +46432,11 @@ TERMS AND CONDITIONS
The requirement to provide Installation Information does not
include a requirement to continue to provide support service,
- warranty, or updates for a work that has been modified or installed
- by the recipient, or for the User Product in which it has been
- modified or installed. Access to a network may be denied when the
- modification itself materially and adversely affects the operation
- of the network or violates the rules and protocols for
+ warranty, or updates for a work that has been modified or
+ installed by the recipient, or for the User Product in which it
+ has been modified or installed. Access to a network may be denied
+ when the modification itself materially and adversely affects the
+ operation of the network or violates the rules and protocols for
communication across the network.
Corresponding Source conveyed, and Installation Information
@@ -46004,8 +46466,8 @@ TERMS AND CONDITIONS
Notwithstanding any other provision of this License, for material
you add to a covered work, you may (if authorized by the copyright
- holders of that material) supplement the terms of this License with
- terms:
+ holders of that material) supplement the terms of this License
+ with terms:
a. Disclaiming warranty or limiting liability differently from
the terms of sections 15 and 16 of this License; or
@@ -46015,8 +46477,9 @@ TERMS AND CONDITIONS
Legal Notices displayed by works containing it; or
c. Prohibiting misrepresentation of the origin of that material,
- or requiring that modified versions of such material be marked
- in reasonable ways as different from the original version; or
+ or requiring that modified versions of such material be
+ marked in reasonable ways as different from the original
+ version; or
d. Limiting the use for publicity purposes of names of licensors
or authors of the material; or
@@ -46035,10 +46498,11 @@ TERMS AND CONDITIONS
you received it, or any part of it, contains a notice stating that
it is governed by this License along with a term that is a further
restriction, you may remove that term. If a license document
- contains a further restriction but permits relicensing or conveying
- under this License, you may add to a covered work material governed
- by the terms of that license document, provided that the further
- restriction does not survive such relicensing or conveying.
+ contains a further restriction but permits relicensing or
+ conveying under this License, you may add to a covered work
+ material governed by the terms of that license document, provided
+ that the further restriction does not survive such relicensing or
+ conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
@@ -46054,13 +46518,13 @@ TERMS AND CONDITIONS
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights
- under this License (including any patent licenses granted under the
- third paragraph of section 11).
+ under this License (including any patent licenses granted under
+ the third paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -46072,10 +46536,10 @@ TERMS AND CONDITIONS
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, you do not qualify to receive new licenses
- for the same material under section 10.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, you do not qualify to receive new
+ licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
@@ -46089,7 +46553,7 @@ TERMS AND CONDITIONS
by modifying or propagating a covered work, you indicate your
acceptance of this License to do so.
- 10. Automatic Licensing of Downstream Recipients.
+ 10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
@@ -46103,21 +46567,21 @@ TERMS AND CONDITIONS
covered work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or
- could give under the previous paragraph, plus a right to possession
- of the Corresponding Source of the work from the predecessor in
- interest, if the predecessor has it or can get it with reasonable
- efforts.
+ could give under the previous paragraph, plus a right to
+ possession of the Corresponding Source of the work from the
+ predecessor in interest, if the predecessor has it or can get it
+ with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you
- may not impose a license fee, royalty, or other charge for exercise
- of rights granted under this License, and you may not initiate
- litigation (including a cross-claim or counterclaim in a lawsuit)
- alleging that any patent claim is infringed by making, using,
- selling, offering for sale, or importing the Program or any portion
- of it.
+ may not impose a license fee, royalty, or other charge for
+ exercise of rights granted under this License, and you may not
+ initiate litigation (including a cross-claim or counterclaim in a
+ lawsuit) alleging that any patent claim is infringed by making,
+ using, selling, offering for sale, or importing the Program or any
+ portion of it.
- 11. Patents.
+ 11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based.
@@ -46137,15 +46601,15 @@ TERMS AND CONDITIONS
Each contributor grants you a non-exclusive, worldwide,
royalty-free patent license under the contributor's essential
patent claims, to make, use, sell, offer for sale, import and
- otherwise run, modify and propagate the contents of its contributor
- version.
+ otherwise run, modify and propagate the contents of its
+ contributor version.
In the following three paragraphs, a "patent license" is any
express agreement or commitment, however denominated, not to
enforce a patent (such as an express permission to practice a
- patent or covenant not to sue for patent infringement). To "grant"
- such a patent license to a party means to make such an agreement or
- commitment not to enforce a patent against the party.
+ patent or covenant not to sue for patent infringement). To
+ "grant" such a patent license to a party means to make such an
+ agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent
license, and the Corresponding Source of the work is not available
@@ -46175,35 +46639,36 @@ TERMS AND CONDITIONS
conditioned on the non-exercise of one or more of the rights that
are specifically granted under this License. You may not convey a
covered work if you are a party to an arrangement with a third
- party that is in the business of distributing software, under which
- you make payment to the third party based on the extent of your
- activity of conveying the work, and under which the third party
- grants, to any of the parties who would receive the covered work
- from you, a discriminatory patent license (a) in connection with
- copies of the covered work conveyed by you (or copies made from
- those copies), or (b) primarily for and in connection with specific
- products or compilations that contain the covered work, unless you
- entered into that arrangement, or that patent license was granted,
- prior to 28 March 2007.
+ party that is in the business of distributing software, under
+ which you make payment to the third party based on the extent of
+ your activity of conveying the work, and under which the third
+ party grants, to any of the parties who would receive the covered
+ work from you, a discriminatory patent license (a) in connection
+ with copies of the covered work conveyed by you (or copies made
+ from those copies), or (b) primarily for and in connection with
+ specific products or compilations that contain the covered work,
+ unless you entered into that arrangement, or that patent license
+ was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
- 12. No Surrender of Others' Freedom.
+ 12. No Surrender of Others' Freedom.
- If conditions are imposed on you (whether by court order, agreement
- or otherwise) that contradict the conditions of this License, they
- do not excuse you from the conditions of this License. If you
- cannot convey a covered work so as to satisfy simultaneously your
- obligations under this License and any other pertinent obligations,
- then as a consequence you may not convey it at all. For example,
- if you agree to terms that obligate you to collect a royalty for
- further conveying from those to whom you convey the Program, the
- only way you could satisfy both those terms and this License would
- be to refrain entirely from conveying the Program.
+ If conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot convey a covered work so as to satisfy
+ simultaneously your obligations under this License and any other
+ pertinent obligations, then as a consequence you may not convey it
+ at all. For example, if you agree to terms that obligate you to
+ collect a royalty for further conveying from those to whom you
+ convey the Program, the only way you could satisfy both those
+ terms and this License would be to refrain entirely from conveying
+ the Program.
- 13. Use with the GNU Affero General Public License.
+ 13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
@@ -46214,21 +46679,22 @@ TERMS AND CONDITIONS
General Public License, section 13, concerning interaction through
a network will apply to the combination as such.
- 14. Revised Versions of this License.
+ 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new
- versions of the GNU General Public License from time to time. Such
- new versions will be similar in spirit to the present version, but
- may differ in detail to address new problems or concerns.
+ versions of the GNU General Public License from time to time.
+ Such new versions will be similar in spirit to the present
+ version, but may differ in detail to address new problems or
+ concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU
General Public License "or any later version" applies to it, you
have the option of following the terms and conditions either of
- that numbered version or of any later version published by the Free
- Software Foundation. If the Program does not specify a version
- number of the GNU General Public License, you may choose any
- version ever published by the Free Software Foundation.
+ that numbered version or of any later version published by the
+ Free Software Foundation. If the Program does not specify a
+ version number of the GNU General Public License, you may choose
+ any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that
@@ -46240,24 +46706,24 @@ TERMS AND CONDITIONS
author or copyright holder as a result of your choosing to follow a
later version.
- 15. Disclaimer of Warranty.
+ 15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
- APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
+ APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
- MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
NECESSARY SERVICING, REPAIR OR CORRECTION.
- 16. Limitation of Liability.
+ 16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
- AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
- DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+ AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
+ FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
@@ -46265,7 +46731,7 @@ TERMS AND CONDITIONS
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
- 17. Interpretation of Sections 15 and 16.
+ 17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
@@ -46274,6 +46740,7 @@ TERMS AND CONDITIONS
connection with the Program, unless a warranty or assumption of
liability accompanies a copy of the Program in return for a fee.
+
END OF TERMS AND CONDITIONS
===========================
@@ -46285,9 +46752,9 @@ possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
- To do so, attach the following notices to the program. It is safest to
-attach them to the start of each source file to most effectively state
-the exclusion of warranty; and each file should have at least the
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
@@ -46304,20 +46771,20 @@ the exclusion of warranty; and each file should have at least the
General Public License for more details.
You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
+ along with this program. If not, see `http://www.gnu.org/licenses/'.
Also add information on how to contact you by electronic and paper
mail.
- If the program does terminal interaction, make it output a short notice
-like this when it starts in an interactive mode:
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
PROGRAM Copyright (C) YEAR NAME OF AUTHOR
- This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
- under certain conditions; type 'show c' for details.
+ under certain conditions; type `show c' for details.
- The hypothetical commands 'show w' and 'show c' should show the
+ The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
@@ -46325,14 +46792,14 @@ use an "about box".
You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. For more information on this, and how to apply and follow
-the GNU GPL, see <http://www.gnu.org/licenses/>.
+the GNU GPL, see `http://www.gnu.org/licenses/'.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
-please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
+please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.

File: gcc.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top
@@ -46343,7 +46810,7 @@ GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
+ `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -46368,21 +46835,21 @@ GNU Free Documentation License
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book. We
- recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it can
- be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright 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, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
- the license if you copy, modify or distribute the work in a way
- requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "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 containing the
Document or a portion of it, either copied verbatim, or with
@@ -46400,12 +46867,12 @@ GNU Free Documentation License
regarding them.
The "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 above definition of Secondary then it
- is not allowed to be designated as Invariant. The Document may
- contain zero Invariant Sections. If the Document does not identify
- any Invariant Sections then there are none.
+ 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 above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -46416,27 +46883,27 @@ GNU Free Documentation License
A "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 generic text editors or (for images composed
- of pixels) generic paint programs or (for drawings) some widely
- available drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of formats
- suitable for input to text formatters. A copy made in an otherwise
- Transparent file format whose markup, or absence 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".
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence 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".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and standard-conforming
- simple HTML, PostScript or PDF designed for human modification.
- Examples of transparent image formats include PNG, XCF and JPG.
- Opaque formats include proprietary formats that can be read and
- edited only by proprietary word processors, SGML or XML for which
- the DTD and/or processing tools are not generally available, and
- the machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -46474,8 +46941,8 @@ GNU Free Documentation License
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow the
- conditions in section 3.
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -46489,11 +46956,12 @@ GNU Free Documentation License
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on the
- covers in addition. Copying with changes limited to the covers, as
- long as they preserve the title of the Document and satisfy these
- conditions, can be treated as verbatim copying in other respects.
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -46501,39 +46969,40 @@ GNU Free Documentation License
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with
- each Opaque copy a computer-network location from which the general
- network-using public has access to download using public-standard
- network protocols a complete Transparent copy of the Document, free
- of added material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of Opaque
- copies in quantity, to ensure that this Transparent copy will
- remain thus accessible at the stated location until at least one
- year after the last time you distribute an Opaque copy (directly or
- through your agents or retailers) of that edition to the public.
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies,
- to give them a chance to provide you with an updated version of the
- Document.
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with the
- Modified Version filling the role of the Document, thus licensing
- distribution and modification of the Modified Version to whoever
- possesses a copy of it. In addition, you must do these things in
- the Modified Version:
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the
- History section of the Document). You may use the same title
- as a previous version if the original publisher of that
- version gives permission.
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -46563,30 +47032,31 @@ GNU Free Documentation License
I. Preserve the section Entitled "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, 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.
+ 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, 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.
J. Preserve the network location, if any, given in 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 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.
+ previous versions it was based on. These may be placed in
+ the "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.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section
- all the substance and tone of each of the contributor
+ 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.
- L. Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the
- equivalent are not considered part of the section titles.
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -46599,11 +47069,11 @@ GNU Free Documentation License
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain 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 be distinct from any other
- section titles.
+ 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 be distinct from any
+ other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -46612,15 +47082,15 @@ GNU Free Documentation License
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of
- the list of Cover Texts in the Modified Version. Only one passage
- of Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover, previously added
- by you or by arrangement made by the same entity you are acting on
- behalf of, you may not add another; but you may replace the old
- one, on explicit permission from the previous publisher that added
- the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -46630,8 +47100,8 @@ GNU Free Documentation License
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination all
- of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -46658,20 +47128,20 @@ GNU Free Documentation License
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the documents
- in all other respects.
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
7. AGGREGATION WITH INDEPENDENT WORKS
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
+ 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 the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -46716,8 +47186,8 @@ GNU Free Documentation License
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -46729,33 +47199,33 @@ GNU Free Documentation License
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, receipt of a copy of some or all of the
- same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, receipt of a copy of some or all of
+ the same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- <http://www.gnu.org/copyleft/>.
+ `http://www.gnu.org/copyleft/'.
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 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 Foundation. If the
- Document does not specify a version number 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
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number 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 statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
@@ -46785,6 +47255,7 @@ GNU Free Documentation License
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
+
ADDENDUM: How to use this License for your documents
====================================================
@@ -46801,7 +47272,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the "with...Texts." line with this:
+replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -46812,9 +47283,9 @@ combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of free
-software license, such as the GNU General Public License, to permit
-their use in free software.
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.

File: gcc.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top
@@ -46822,9 +47293,9 @@ File: gcc.info, Node: Contributors, Next: Option Index, Prev: GNU Free Docume
Contributors to GCC
*******************
-The GCC project would like to thank its many contributors. Without them
-the project would not have been nearly as successful as it has been.
-Any omissions in this list are accidental. Feel free to contact
+The GCC project would like to thank its many contributors. Without
+them the project would not have been nearly as successful as it has
+been. Any omissions in this list are accidental. Feel free to contact
<law@redhat.com> or <gerald@pfeifer.com> if you have been left out or
some of your contributions are not listed. Please keep this list in
alphabetical order.
@@ -46957,7 +47428,7 @@ alphabetical order.
* The GNU Classpath project for all of their merged runtime code.
* Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work,
- '--help', and other random hacking.
+ `--help', and other random hacking.
* Michael Cook for libstdc++ cleanup patches to reduce warnings.
@@ -46977,8 +47448,8 @@ alphabetical order.
* Paul Dale for his work to add uClinux platform support to the m68k
backend.
- * Dario Dariol contributed the four varieties of sample programs that
- print a copy of their source.
+ * Dario Dariol contributed the four varieties of sample programs
+ that print a copy of their source.
* Russell Davidson for fstream and stringstream fixes in libstdc++.
@@ -46993,19 +47464,19 @@ alphabetical order.
* Gabriel Dos Reis for contributions to G++, contributions and
maintenance of GCC diagnostics infrastructure, libstdc++-v3,
- including 'valarray<>', 'complex<>', maintaining the numerics
- library (including that pesky '<limits>' :-) and keeping up-to-date
- anything to do with numbers.
+ including `valarray<>', `complex<>', maintaining the numerics
+ library (including that pesky `<limits>' :-) and keeping
+ up-to-date anything to do with numbers.
* Ulrich Drepper for his work on glibc, testing of GCC using glibc,
- ISO C99 support, CFG dumping support, etc., plus support of the C++
- runtime libraries including for all kinds of C interface issues,
- contributing and maintaining 'complex<>', sanity checking and
- disbursement, configuration architecture, libio maintenance, and
- early math work.
+ ISO C99 support, CFG dumping support, etc., plus support of the
+ C++ runtime libraries including for all kinds of C interface
+ issues, contributing and maintaining `complex<>', sanity checking
+ and disbursement, configuration architecture, libio maintenance,
+ and early math work.
* Franc,ois Dumont for his work on libstdc++-v3, especially
- maintaining and improving 'debug-mode' and associative and
+ maintaining and improving `debug-mode' and associative and
unordered containers.
* Zdenek Dvorak for a new loop unroller and various fixes.
@@ -47057,10 +47528,11 @@ alphabetical order.
* Peter Gerwinski for various bug fixes and the Pascal front end.
* Kaveh R. Ghazi for his direction via the steering committee,
- amazing work to make '-W -Wall -W* -Werror' useful, and testing GCC
- on a plethora of platforms. Kaveh extends his gratitude to the
- CAIP Center at Rutgers University for providing him with computing
- resources to work on Free Software from the late 1980s to 2010.
+ amazing work to make `-W -Wall -W* -Werror' useful, and testing
+ GCC on a plethora of platforms. Kaveh extends his gratitude to
+ the CAIP Center at Rutgers University for providing him with
+ computing resources to work on Free Software from the late 1980s
+ to 2010.
* John Gilmore for a donation to the FSF earmarked improving GNU
Java.
@@ -47072,21 +47544,21 @@ alphabetical order.
support, improved leaf function register allocation, and his
direction via the steering committee.
- * Jonny Grant for improvements to 'collect2's' '--help'
+ * Jonny Grant for improvements to `collect2's' `--help'
documentation.
- * Anthony Green for his '-Os' contributions, the moxie port, and Java
- front end work.
+ * Anthony Green for his `-Os' contributions, the moxie port, and
+ Java front end work.
- * Stu Grossman for gdb hacking, allowing GCJ developers to debug Java
- code.
+ * Stu Grossman for gdb hacking, allowing GCJ developers to debug
+ Java code.
* Michael K. Gschwind contributed the port to the PDP-11.
* Richard Biener for his ongoing middle-end contributions and bug
fixes and for release management.
- * Ron Guilmette implemented the 'protoize' and 'unprotoize' tools,
+ * Ron Guilmette implemented the `protoize' and `unprotoize' tools,
the support for Dwarf symbolic debugging information, and much of
the support for System V Release 4. He has also worked heavily on
the Intel 386 and 860 support.
@@ -47105,8 +47577,8 @@ alphabetical order.
series 300.
* Michael Hayes for various thankless work he's done trying to get
- the c30/c40 ports functional. Lots of loop and unroll improvements
- and fixes.
+ the c30/c40 ports functional. Lots of loop and unroll
+ improvements and fixes.
* Dara Hazeghi for wading through myriads of target-specific bug
reports.
@@ -47140,8 +47612,8 @@ alphabetical order.
* Falk Hueffner for working on C and optimization bug reports.
- * Bernardo Innocenti for his m68k work, including merging of ColdFire
- improvements and uClinux support.
+ * Bernardo Innocenti for his m68k work, including merging of
+ ColdFire improvements and uClinux support.
* Christian Iseli for various bug fixes.
@@ -47194,13 +47666,13 @@ alphabetical order.
* Richard Kenner of the New York University Ultracomputer Research
Laboratory wrote the machine descriptions for the AMD 29000, the
DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the
- support for instruction attributes. He also made changes to better
- support RISC processors including changes to common subexpression
- elimination, strength reduction, function calling sequence
- handling, and condition code support, in addition to generalizing
- the code for frame pointer elimination and delay slot scheduling.
- Richard Kenner was also the head maintainer of GCC for several
- years.
+ support for instruction attributes. He also made changes to
+ better support RISC processors including changes to common
+ subexpression elimination, strength reduction, function calling
+ sequence handling, and condition code support, in addition to
+ generalizing the code for frame pointer elimination and delay slot
+ scheduling. Richard Kenner was also the head maintainer of GCC
+ for several years.
* Mumit Khan for various contributions to the Cygwin and Mingw32
ports and maintaining binary releases for Microsoft Windows hosts,
@@ -47226,11 +47698,11 @@ alphabetical order.
* Asher Langton and Mike Kumbera for contributing Cray pointer
support to GNU Fortran, and for other GNU Fortran improvements.
- * Jeff Law for his direction via the steering committee, coordinating
- the entire egcs project and GCC 2.95, rolling out snapshots and
- releases, handling merges from GCC2, reviewing tons of patches that
- might have fallen through the cracks else, and random but extensive
- hacking.
+ * Jeff Law for his direction via the steering committee,
+ coordinating the entire egcs project and GCC 2.95, rolling out
+ snapshots and releases, handling merges from GCC2, reviewing tons
+ of patches that might have fallen through the cracks else, and
+ random but extensive hacking.
* Walter Lee for work on the TILE-Gx and TILEPro ports.
@@ -47259,7 +47731,7 @@ alphabetical order.
* Weiwen Liu for testing and various bug fixes.
- * Manuel Lo'pez-Iba'n~ez for improving '-Wconversion' and many other
+ * Manuel Lo'pez-Iba'n~ez for improving `-Wconversion' and many other
diagnostics fixes and improvements.
* Dave Love for his ongoing work with the Fortran front end and
@@ -47276,13 +47748,14 @@ alphabetical order.
* Greg McGary for random fixes and (someday) bounded pointers.
* Andrew MacLeod for his ongoing work in building a real EH system,
- various code generation improvements, work on the global optimizer,
- etc.
+ various code generation improvements, work on the global
+ optimizer, etc.
* Vladimir Makarov for hacking some ugly i960 problems, PowerPC
- hacking improvements to compile-time performance, overall knowledge
- and direction in the area of instruction scheduling, and design and
- implementation of the automaton based instruction scheduler.
+ hacking improvements to compile-time performance, overall
+ knowledge and direction in the area of instruction scheduling, and
+ design and implementation of the automaton based instruction
+ scheduler.
* Bob Manson for his behind the scenes work on dejagnu.
@@ -47321,7 +47794,7 @@ alphabetical order.
* Mark Mitchell for his direction via the steering committee,
mountains of C++ work, load/store hoisting out of loops, alias
- analysis improvements, ISO C 'restrict' support, and serving as
+ analysis improvements, ISO C `restrict' support, and serving as
release manager from 2000 to 2011.
* Alan Modra for various GNU/Linux bits and testing.
@@ -47331,9 +47804,9 @@ alphabetical order.
* Jason Molenda for major help in the care and feeding of all the
services on the gcc.gnu.org (formerly egcs.cygnus.com)
- machine--mail, web services, ftp services, etc etc. Doing all this
- work on scrap paper and the backs of envelopes would have been...
- difficult.
+ machine--mail, web services, ftp services, etc etc. Doing all
+ this work on scrap paper and the backs of envelopes would have
+ been... difficult.
* Catherine Moore for fixing various ugly problems we have sent her
way, including the haifa bug which was killing the Alpha & PowerPC
@@ -47345,8 +47818,8 @@ alphabetical order.
initial IA-64 port.
* Stephen Moshier contributed the floating point emulator that
- assists in cross-compilation and permits support for floating point
- numbers wider than 64 bits and for ISO C99 support.
+ assists in cross-compilation and permits support for floating
+ point numbers wider than 64 bits and for ISO C99 support.
* Bill Moyer for his behind the scenes work on various issues.
@@ -47369,9 +47842,9 @@ alphabetical order.
* NeXT, Inc. donated the front end that supports the Objective-C
language.
- * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to the
- search engine setup, various documentation fixes and other small
- fixes.
+ * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to
+ the search engine setup, various documentation fixes and other
+ small fixes.
* Geoff Noer for his work on getting cygwin native builds working.
@@ -47379,8 +47852,8 @@ alphabetical order.
tracking web pages, GIMPLE tuples, and assorted fixes.
* David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64,
- FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and related
- infrastructure improvements.
+ FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and
+ related infrastructure improvements.
* Alexandre Oliva for various build infrastructure improvements,
scripts and amazing testing work, including keeping libtool issues
@@ -47392,8 +47865,8 @@ alphabetical order.
* Rainer Orth for random MIPS work, including improvements to GCC's
o32 ABI support, improvements to dejagnu's MIPS support, Java
- configuration clean-ups and porting work, and maintaining the IRIX,
- Solaris 2, and Tru64 UNIX ports.
+ configuration clean-ups and porting work, and maintaining the
+ IRIX, Solaris 2, and Tru64 UNIX ports.
* Hartmut Penner for work on the s390 port.
@@ -47443,7 +47916,7 @@ alphabetical order.
* David Ronis inspired and encouraged Craig to rewrite the G77
documentation in texinfo format by contributing a first pass at a
- translation of the old 'g77-0.5.16/f/DOC' file.
+ translation of the old `g77-0.5.16/f/DOC' file.
* Ken Rose for fixes to GCC's delay slot filling code.
@@ -47475,8 +47948,8 @@ alphabetical order.
* Tobias Schlu"ter for work on GNU Fortran.
* Bernd Schmidt for various code generation improvements and major
- work in the reload pass, serving as release manager for GCC 2.95.3,
- and work on the Blackfin and C6X ports.
+ work in the reload pass, serving as release manager for GCC
+ 2.95.3, and work on the Blackfin and C6X ports.
* Peter Schmid for constant testing of libstdc++--especially
application testing, going above and beyond what was requested for
@@ -47491,7 +47964,7 @@ alphabetical order.
* Dodji Seketeli for numerous C++ bug fixes and debug info
improvements.
- * Tim Shen for major work on '<regex>'.
+ * Tim Shen for major work on `<regex>'.
* Joel Sherrill for his direction via the steering committee, RTEMS
contributions and RTEMS testing.
@@ -47506,8 +47979,8 @@ alphabetical order.
from the LWG (thereby keeping GCC in line with updates from the
ISO).
- * Franz Sirl for his ongoing work with making the PPC port stable for
- GNU/Linux.
+ * Franz Sirl for his ongoing work with making the PPC port stable
+ for GNU/Linux.
* Andrey Slepuhin for assorted AIX hacking.
@@ -47522,12 +47995,12 @@ alphabetical order.
* Randy Smith finished the Sun FPA support.
* Ed Smith-Rowland for his continuous work on libstdc++-v3, special
- functions, '<random>', and various improvements to C++11 features.
+ functions, `<random>', and various improvements to C++11 features.
* Scott Snyder for queue, iterator, istream, and string fixes and
libstdc++ testsuite entries. Also for providing the patch to G77
- to add rudimentary support for 'INTEGER*1', 'INTEGER*2', and
- 'LOGICAL*1'.
+ to add rudimentary support for `INTEGER*1', `INTEGER*2', and
+ `LOGICAL*1'.
* Zdenek Sojka for running automated regression testing of GCC and
reporting numerous bugs.
@@ -47551,8 +48024,8 @@ alphabetical order.
* John Stracke for his Java HTTP protocol fixes.
- * Mike Stump for his Elxsi port, G++ contributions over the years and
- more recently his vxworks contributions
+ * Mike Stump for his Elxsi port, G++ contributions over the years
+ and more recently his vxworks contributions
* Jeff Sturm for Java porting help, bug fixes, and encouragement.
@@ -47606,8 +48079,8 @@ alphabetical order.
* Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML
guidance.
- * Dean Wakerley for converting the install documentation from HTML to
- texinfo in time for GCC 3.0.
+ * Dean Wakerley for converting the install documentation from HTML
+ to texinfo in time for GCC 3.0.
* Krister Walfridsson for random bug fixes.
@@ -47615,8 +48088,8 @@ alphabetical order.
* Stephen M. Webb for time and effort on making libstdc++ shadow
files work with the tricky Solaris 8+ headers, and for pushing the
- build-time header tree. Also, for starting and driving the
- '<regex>' effort.
+ build-time header tree. Also, for starting and driving the
+ `<regex>' effort.
* John Wehle for various improvements for the x86 code generator,
related infrastructure improvements to help x86 code generation,
@@ -47638,8 +48111,8 @@ alphabetical order.
* Bob Wilson from Tensilica, Inc. for the Xtensa port.
* Jim Wilson for his direction via the steering committee, tackling
- hard problems in various places that nobody else wanted to work on,
- strength reduction and other loop optimizations.
+ hard problems in various places that nobody else wanted to work
+ on, strength reduction and other loop optimizations.
* Paul Woegerer and Tal Agmon for the CRX port.
@@ -47662,6 +48135,7 @@ alphabetical order.
* Gilles Zunino for help porting Java to Irix.
+
The following people are recognized for their contributions to GNAT,
the Ada front end of GCC:
* Bernard Banner
@@ -47758,102 +48232,102 @@ the Ada front end of GCC:
* Samuel Tardieu
+
The following people are recognized for their contributions of new
features, bug reports, testing and integration of classpath/libgcj for
GCC version 4.1:
- * Lillian Angel for 'JTree' implementation and lots Free Swing
+ * Lillian Angel for `JTree' implementation and lots Free Swing
additions and bug fixes.
- * Wolfgang Baer for 'GapContent' bug fixes.
+ * Wolfgang Baer for `GapContent' bug fixes.
- * Anthony Balkissoon for 'JList', Free Swing 1.5 updates and mouse
- event fixes, lots of Free Swing work including 'JTable' editing.
+ * Anthony Balkissoon for `JList', Free Swing 1.5 updates and mouse
+ event fixes, lots of Free Swing work including `JTable' editing.
* Stuart Ballard for RMI constant fixes.
- * Goffredo Baroncelli for 'HTTPURLConnection' fixes.
+ * Goffredo Baroncelli for `HTTPURLConnection' fixes.
- * Gary Benson for 'MessageFormat' fixes.
+ * Gary Benson for `MessageFormat' fixes.
- * Daniel Bonniot for 'Serialization' fixes.
+ * Daniel Bonniot for `Serialization' fixes.
- * Chris Burdess for lots of gnu.xml and http protocol fixes, 'StAX'
- and 'DOM xml:id' support.
+ * Chris Burdess for lots of gnu.xml and http protocol fixes, `StAX'
+ and `DOM xml:id' support.
- * Ka-Hing Cheung for 'TreePath' and 'TreeSelection' fixes.
+ * Ka-Hing Cheung for `TreePath' and `TreeSelection' fixes.
* Archie Cobbs for build fixes, VM interface updates,
- 'URLClassLoader' updates.
+ `URLClassLoader' updates.
* Kelley Cook for build fixes.
- * Martin Cordova for Suggestions for better 'SocketTimeoutException'.
+ * Martin Cordova for Suggestions for better `SocketTimeoutException'.
- * David Daney for 'BitSet' bug fixes, 'HttpURLConnection' rewrite and
- improvements.
+ * David Daney for `BitSet' bug fixes, `HttpURLConnection' rewrite
+ and improvements.
* Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo
- 2D support. Lots of imageio framework additions, lots of AWT and
+ 2D support. Lots of imageio framework additions, lots of AWT and
Free Swing bug fixes.
- * Jeroen Frijters for 'ClassLoader' and nio cleanups, serialization
- fixes, better 'Proxy' support, bug fixes and IKVM integration.
+ * Jeroen Frijters for `ClassLoader' and nio cleanups, serialization
+ fixes, better `Proxy' support, bug fixes and IKVM integration.
- * Santiago Gala for 'AccessControlContext' fixes.
+ * Santiago Gala for `AccessControlContext' fixes.
- * Nicolas Geoffray for 'VMClassLoader' and 'AccessController'
+ * Nicolas Geoffray for `VMClassLoader' and `AccessController'
improvements.
- * David Gilbert for 'basic' and 'metal' icon and plaf support and
+ * David Gilbert for `basic' and `metal' icon and plaf support and
lots of documenting, Lots of Free Swing and metal theme additions.
- 'MetalIconFactory' implementation.
+ `MetalIconFactory' implementation.
- * Anthony Green for 'MIDI' framework, 'ALSA' and 'DSSI' providers.
+ * Anthony Green for `MIDI' framework, `ALSA' and `DSSI' providers.
- * Andrew Haley for 'Serialization' and 'URLClassLoader' fixes, gcj
+ * Andrew Haley for `Serialization' and `URLClassLoader' fixes, gcj
build speedups.
- * Kim Ho for 'JFileChooser' implementation.
+ * Kim Ho for `JFileChooser' implementation.
- * Andrew John Hughes for 'Locale' and net fixes, URI RFC2986 updates,
- 'Serialization' fixes, 'Properties' XML support and generic branch
- work, VMIntegration guide update.
+ * Andrew John Hughes for `Locale' and net fixes, URI RFC2986
+ updates, `Serialization' fixes, `Properties' XML support and
+ generic branch work, VMIntegration guide update.
- * Bastiaan Huisman for 'TimeZone' bug fixing.
+ * Bastiaan Huisman for `TimeZone' bug fixing.
* Andreas Jaeger for mprec updates.
- * Paul Jenner for better '-Werror' support.
+ * Paul Jenner for better `-Werror' support.
- * Ito Kazumitsu for 'NetworkInterface' implementation and updates.
+ * Ito Kazumitsu for `NetworkInterface' implementation and updates.
- * Roman Kennke for 'BoxLayout', 'GrayFilter' and 'SplitPane', plus
- bug fixes all over. Lots of Free Swing work including styled text.
+ * Roman Kennke for `BoxLayout', `GrayFilter' and `SplitPane', plus
+ bug fixes all over. Lots of Free Swing work including styled text.
- * Simon Kitching for 'String' cleanups and optimization suggestions.
+ * Simon Kitching for `String' cleanups and optimization suggestions.
- * Michael Koch for configuration fixes, 'Locale' updates, bug and
+ * Michael Koch for configuration fixes, `Locale' updates, bug and
build fixes.
* Guilhem Lavaux for configuration, thread and channel fixes and
- Kaffe integration. JCL native 'Pointer' updates. Logger bug
- fixes.
+ Kaffe integration. JCL native `Pointer' updates. Logger bug fixes.
* David Lichteblau for JCL support library global/local reference
cleanups.
* Aaron Luchko for JDWP updates and documentation fixes.
- * Ziga Mahkovec for 'Graphics2D' upgraded to Cairo 0.5 and new regex
+ * Ziga Mahkovec for `Graphics2D' upgraded to Cairo 0.5 and new regex
features.
- * Sven de Marothy for BMP imageio support, CSS and 'TextLayout'
- fixes. 'GtkImage' rewrite, 2D, awt, free swing and date/time fixes
+ * Sven de Marothy for BMP imageio support, CSS and `TextLayout'
+ fixes. `GtkImage' rewrite, 2D, awt, free swing and date/time fixes
and implementing the Qt4 peers.
- * Casey Marshall for crypto algorithm fixes, 'FileChannel' lock,
- 'SystemLogger' and 'FileHandler' rotate implementations, NIO
- 'FileChannel.map' support, security and policy updates.
+ * Casey Marshall for crypto algorithm fixes, `FileChannel' lock,
+ `SystemLogger' and `FileHandler' rotate implementations, NIO
+ `FileChannel.map' support, security and policy updates.
* Bryce McKinlay for RMI work.
@@ -47864,45 +48338,46 @@ GCC version 4.1:
* Rainer Orth for build fixes.
- * Andrew Overholt for 'File' locking fixes.
+ * Andrew Overholt for `File' locking fixes.
- * Ingo Proetel for 'Image', 'Logger' and 'URLClassLoader' updates.
+ * Ingo Proetel for `Image', `Logger' and `URLClassLoader' updates.
- * Olga Rodimina for 'MenuSelectionManager' implementation.
+ * Olga Rodimina for `MenuSelectionManager' implementation.
- * Jan Roehrich for 'BasicTreeUI' and 'JTree' fixes.
+ * Jan Roehrich for `BasicTreeUI' and `JTree' fixes.
* Julian Scheid for documentation updates and gjdoc support.
* Christian Schlichtherle for zip fixes and cleanups.
* Robert Schuster for documentation updates and beans fixes,
- 'TreeNode' enumerations and 'ActionCommand' and various fixes, XML
+ `TreeNode' enumerations and `ActionCommand' and various fixes, XML
and URL, AWT and Free Swing bug fixes.
* Keith Seitz for lots of JDWP work.
* Christian Thalinger for 64-bit cleanups, Configuration and VM
- interface fixes and 'CACAO' integration, 'fdlibm' updates.
+ interface fixes and `CACAO' integration, `fdlibm' updates.
- * Gael Thomas for 'VMClassLoader' boot packages support suggestions.
+ * Gael Thomas for `VMClassLoader' boot packages support suggestions.
- * Andreas Tobler for Darwin and Solaris testing and fixing, 'Qt4'
- support for Darwin/OS X, 'Graphics2D' support, 'gtk+' updates.
+ * Andreas Tobler for Darwin and Solaris testing and fixing, `Qt4'
+ support for Darwin/OS X, `Graphics2D' support, `gtk+' updates.
- * Dalibor Topic for better 'DEBUG' support, build cleanups and Kaffe
- integration. 'Qt4' build infrastructure, 'SHA1PRNG' and
- 'GdkPixbugDecoder' updates.
+ * Dalibor Topic for better `DEBUG' support, build cleanups and Kaffe
+ integration. `Qt4' build infrastructure, `SHA1PRNG' and
+ `GdkPixbugDecoder' updates.
* Tom Tromey for Eclipse integration, generics work, lots of bug
fixes and gcj integration including coordinating The Big Merge.
* Mark Wielaard for bug fixes, packaging and release management,
- 'Clipboard' implementation, system call interrupts and network
- timeouts and 'GdkPixpufDecoder' fixes.
+ `Clipboard' implementation, system call interrupts and network
+ timeouts and `GdkPixpufDecoder' fixes.
- In addition to the above, all of which also contributed time and energy
-in testing GCC, we would like to thank the following for their
+
+ In addition to the above, all of which also contributed time and
+energy in testing GCC, we would like to thank the following for their
contributions to testing:
* Michael Abd-El-Malek
@@ -48071,9 +48546,9 @@ File: gcc.info, Node: Option Index, Next: Keyword Index, Prev: Contributors,
Option Index
************
-GCC's command line options are indexed here without any initial '-' or
-'--'. Where an option has both positive and negative forms (such as
-'-fOPTION' and '-fno-OPTION'), relevant entries in the manual are
+GCC's command line options are indexed here without any initial `-' or
+`--'. Where an option has both positive and negative forms (such as
+`-fOPTION' and `-fno-OPTION'), relevant entries in the manual are
indexed under the most appropriate form; it may sometimes be useful to
look up both forms.
@@ -48081,154 +48556,154 @@ look up both forms.
* Menu:
* ###: Overall Options. (line 209)
-* -fipa-cp-alignment: Optimize Options. (line 986)
+* -fipa-cp-alignment: Optimize Options. (line 991)
* -Wabi-tag: C++ Dialect Options.
- (line 517)
+ (line 521)
* A: Preprocessor Options.
- (line 595)
-* allowable_client: Darwin Options. (line 196)
+ (line 596)
* all_load: Darwin Options. (line 110)
+* allowable_client: Darwin Options. (line 196)
+* ansi <1>: Non-bugs. (line 107)
+* ansi <2>: Other Builtins. (line 22)
+* ansi <3>: Preprocessor Options.
+ (line 338)
+* ansi <4>: C Dialect Options. (line 11)
* ansi: Standards. (line 16)
-* ansi <1>: C Dialect Options. (line 11)
-* ansi <2>: Preprocessor Options.
- (line 340)
-* ansi <3>: Other Builtins. (line 21)
-* ansi <4>: Non-bugs. (line 107)
* arch_errors_fatal: Darwin Options. (line 114)
-* aux-info: C Dialect Options. (line 173)
-* B: Directory Options. (line 44)
+* aux-info: C Dialect Options. (line 176)
+* B: Directory Options. (line 46)
* Bdynamic: VxWorks Options. (line 22)
* bind_at_load: Darwin Options. (line 118)
* Bstatic: VxWorks Options. (line 22)
* bundle: Darwin Options. (line 123)
* bundle_loader: Darwin Options. (line 127)
-* c: Overall Options. (line 164)
+* c: Link Options. (line 20)
* C: Preprocessor Options.
- (line 652)
-* c <1>: Link Options. (line 20)
+ (line 654)
+* c: Overall Options. (line 164)
* client_name: Darwin Options. (line 196)
* compatibility_version: Darwin Options. (line 196)
-* coverage: Debugging Options. (line 725)
+* coverage: Debugging Options. (line 723)
* current_version: Darwin Options. (line 196)
-* d: Debugging Options. (line 857)
* D: Preprocessor Options.
(line 46)
-* da: Debugging Options. (line 1059)
-* dA: Debugging Options. (line 1062)
-* dD: Debugging Options. (line 1066)
+* d: Debugging Options. (line 855)
+* dA: Debugging Options. (line 1060)
+* da: Debugging Options. (line 1057)
* dD <1>: Preprocessor Options.
- (line 626)
+ (line 628)
+* dD: Debugging Options. (line 1064)
* dead_strip: Darwin Options. (line 196)
* dependency-file: Darwin Options. (line 196)
-* dH: Debugging Options. (line 1070)
+* dH: Debugging Options. (line 1068)
* dI: Preprocessor Options.
- (line 635)
+ (line 637)
* dM: Preprocessor Options.
- (line 611)
+ (line 612)
* dN: Preprocessor Options.
- (line 632)
-* dp: Debugging Options. (line 1073)
-* dP: Debugging Options. (line 1078)
+ (line 634)
+* dP: Debugging Options. (line 1076)
+* dp: Debugging Options. (line 1071)
* dU: Preprocessor Options.
- (line 639)
-* dumpmachine: Debugging Options. (line 1650)
-* dumpspecs: Debugging Options. (line 1658)
-* dumpversion: Debugging Options. (line 1654)
-* dx: Debugging Options. (line 1082)
+ (line 641)
+* dumpmachine: Debugging Options. (line 1674)
+* dumpspecs: Debugging Options. (line 1682)
+* dumpversion: Debugging Options. (line 1678)
+* dx: Debugging Options. (line 1080)
* dylib_file: Darwin Options. (line 196)
* dylinker_install_name: Darwin Options. (line 196)
* dynamic: Darwin Options. (line 196)
* dynamiclib: Darwin Options. (line 131)
-* E: Overall Options. (line 185)
* E <1>: Link Options. (line 20)
-* EB: ARC Options. (line 345)
+* E: Overall Options. (line 185)
* EB <1>: MIPS Options. (line 7)
-* EL: ARC Options. (line 354)
+* EB: ARC Options. (line 350)
* EL <1>: MIPS Options. (line 10)
+* EL: ARC Options. (line 357)
* exported_symbols_list: Darwin Options. (line 196)
* F: Darwin Options. (line 31)
* fabi-compat-version: C++ Dialect Options.
- (line 58)
+ (line 59)
* fabi-version: C++ Dialect Options.
- (line 19)
-* fada-spec-parent: Overall Options. (line 367)
-* faggressive-loop-optimizations: Optimize Options. (line 502)
-* falign-functions: Optimize Options. (line 1560)
-* falign-jumps: Optimize Options. (line 1609)
-* falign-labels: Optimize Options. (line 1578)
-* falign-loops: Optimize Options. (line 1596)
+ (line 20)
+* fada-spec-parent: Overall Options. (line 369)
+* faggressive-loop-optimizations: Optimize Options. (line 506)
+* falign-functions: Optimize Options. (line 1566)
+* falign-jumps: Optimize Options. (line 1615)
+* falign-labels: Optimize Options. (line 1584)
+* falign-loops: Optimize Options. (line 1602)
* fallow-parameterless-variadic-functions: C Dialect Options.
- (line 189)
-* fasan-shadow-offset: Debugging Options. (line 353)
-* fassociative-math: Optimize Options. (line 2120)
+ (line 192)
+* fasan-shadow-offset: Debugging Options. (line 348)
+* fassociative-math: Optimize Options. (line 2125)
* fasynchronous-unwind-tables: Code Gen Options. (line 146)
-* fauto-inc-dec: Optimize Options. (line 526)
-* fauto-profile: Optimize Options. (line 2000)
+* fauto-inc-dec: Optimize Options. (line 530)
+* fauto-profile: Optimize Options. (line 2006)
* fbounds-check: Code Gen Options. (line 15)
-* fbranch-probabilities: Optimize Options. (line 2248)
-* fbranch-target-load-optimize: Optimize Options. (line 2371)
-* fbranch-target-load-optimize2: Optimize Options. (line 2377)
-* fbtr-bb-exclusive: Optimize Options. (line 2381)
-* fcall-saved: Code Gen Options. (line 356)
-* fcall-used: Code Gen Options. (line 342)
-* fcaller-saves: Optimize Options. (line 875)
-* fcheck-data-deps: Optimize Options. (line 1195)
+* fbranch-probabilities: Optimize Options. (line 2252)
+* fbranch-target-load-optimize: Optimize Options. (line 2375)
+* fbranch-target-load-optimize2: Optimize Options. (line 2381)
+* fbtr-bb-exclusive: Optimize Options. (line 2385)
+* fcall-saved: Code Gen Options. (line 358)
+* fcall-used: Code Gen Options. (line 344)
+* fcaller-saves: Optimize Options. (line 880)
+* fcheck-data-deps: Optimize Options. (line 1201)
* fcheck-new: C++ Dialect Options.
- (line 73)
-* fcheck-pointer-bounds: Debugging Options. (line 392)
-* fchkp-check-incomplete-type: Debugging Options. (line 432)
-* fchkp-check-read: Debugging Options. (line 482)
-* fchkp-check-write: Debugging Options. (line 486)
-* fchkp-first-field-has-own-bounds: Debugging Options. (line 443)
-* fchkp-instrument-calls: Debugging Options. (line 494)
-* fchkp-instrument-marked-only: Debugging Options. (line 498)
-* fchkp-narrow-bounds: Debugging Options. (line 436)
-* fchkp-narrow-to-innermost-array: Debugging Options. (line 449)
-* fchkp-optimize: Debugging Options. (line 454)
-* fchkp-store-bounds: Debugging Options. (line 490)
+ (line 74)
+* fcheck-pointer-bounds: Debugging Options. (line 387)
+* fchkp-check-incomplete-type: Debugging Options. (line 427)
+* fchkp-check-read: Debugging Options. (line 477)
+* fchkp-check-write: Debugging Options. (line 481)
+* fchkp-first-field-has-own-bounds: Debugging Options. (line 438)
+* fchkp-instrument-calls: Debugging Options. (line 489)
+* fchkp-instrument-marked-only: Debugging Options. (line 493)
+* fchkp-narrow-bounds: Debugging Options. (line 431)
+* fchkp-narrow-to-innermost-array: Debugging Options. (line 444)
+* fchkp-optimize: Debugging Options. (line 449)
+* fchkp-store-bounds: Debugging Options. (line 485)
* fchkp-treat-zero-dynamic-size-as-infinite: Debugging Options.
- (line 475)
-* fchkp-use-fast-string-functions: Debugging Options. (line 458)
-* fchkp-use-nochk-string-functions: Debugging Options. (line 462)
-* fchkp-use-static-bounds: Debugging Options. (line 466)
-* fchkp-use-static-const-bounds: Debugging Options. (line 470)
-* fchkp-use-wrappers: Debugging Options. (line 503)
-* fcilkplus: C Dialect Options. (line 289)
-* fcombine-stack-adjustments: Optimize Options. (line 887)
+ (line 470)
+* fchkp-use-fast-string-functions: Debugging Options. (line 453)
+* fchkp-use-nochk-string-functions: Debugging Options. (line 457)
+* fchkp-use-static-bounds: Debugging Options. (line 461)
+* fchkp-use-static-const-bounds: Debugging Options. (line 465)
+* fchkp-use-wrappers: Debugging Options. (line 498)
+* fcilkplus: C Dialect Options. (line 288)
+* fcombine-stack-adjustments: Optimize Options. (line 892)
* fcommon: Variable Attributes.
- (line 105)
-* fcompare-debug: Debugging Options. (line 516)
-* fcompare-debug-second: Debugging Options. (line 542)
-* fcompare-elim: Optimize Options. (line 1933)
-* fcond-mismatch: C Dialect Options. (line 353)
-* fconserve-stack: Optimize Options. (line 902)
+ (line 106)
+* fcompare-debug: Debugging Options. (line 511)
+* fcompare-debug-second: Debugging Options. (line 537)
+* fcompare-elim: Optimize Options. (line 1941)
+* fcond-mismatch: C Dialect Options. (line 352)
+* fconserve-stack: Optimize Options. (line 907)
* fconstant-string-class: Objective-C and Objective-C++ Dialect Options.
(line 30)
* fconstexpr-depth: C++ Dialect Options.
- (line 83)
-* fcprop-registers: Optimize Options. (line 1945)
-* fcrossjumping: Optimize Options. (line 519)
-* fcse-follow-jumps: Optimize Options. (line 438)
-* fcse-skip-blocks: Optimize Options. (line 447)
-* fcx-fortran-rules: Optimize Options. (line 2235)
-* fcx-limited-range: Optimize Options. (line 2223)
-* fdata-sections: Optimize Options. (line 2352)
-* fdbg-cnt: Debugging Options. (line 777)
-* fdbg-cnt-list: Debugging Options. (line 774)
-* fdce: Optimize Options. (line 532)
+ (line 84)
+* fcprop-registers: Optimize Options. (line 1953)
+* fcrossjumping: Optimize Options. (line 523)
+* fcse-follow-jumps: Optimize Options. (line 442)
+* fcse-skip-blocks: Optimize Options. (line 451)
+* fcx-fortran-rules: Optimize Options. (line 2238)
+* fcx-limited-range: Optimize Options. (line 2226)
+* fdata-sections: Optimize Options. (line 2356)
+* fdbg-cnt: Debugging Options. (line 776)
+* fdbg-cnt-list: Debugging Options. (line 773)
+* fdce: Optimize Options. (line 536)
* fdebug-cpp: Preprocessor Options.
- (line 526)
-* fdebug-prefix-map: Debugging Options. (line 636)
+ (line 525)
+* fdebug-prefix-map: Debugging Options. (line 631)
* fdebug-types-section: Debugging Options. (line 79)
-* fdeclone-ctor-dtor: Optimize Options. (line 555)
+* fdeclone-ctor-dtor: Optimize Options. (line 559)
* fdeduce-init-list: C++ Dialect Options.
- (line 89)
-* fdelayed-branch: Optimize Options. (line 705)
+ (line 90)
+* fdelayed-branch: Optimize Options. (line 710)
* fdelete-dead-exceptions: Code Gen Options. (line 131)
-* fdelete-null-pointer-checks: Optimize Options. (line 566)
-* fdevirtualize: Optimize Options. (line 584)
-* fdevirtualize-at-ltrans: Optimize Options. (line 601)
-* fdevirtualize-speculatively: Optimize Options. (line 591)
+* fdelete-null-pointer-checks: Optimize Options. (line 570)
+* fdevirtualize: Optimize Options. (line 588)
+* fdevirtualize-at-ltrans: Optimize Options. (line 605)
+* fdevirtualize-speculatively: Optimize Options. (line 595)
* fdiagnostics-color: Language Independent Options.
(line 35)
* fdiagnostics-show-caret: Language Independent Options.
@@ -48238,367 +48713,366 @@ look up both forms.
* fdiagnostics-show-option: Language Independent Options.
(line 88)
* fdirectives-only: Preprocessor Options.
- (line 475)
-* fdisable-: Debugging Options. (line 787)
-* fdollars-in-identifiers: Preprocessor Options.
- (line 496)
+ (line 473)
+* fdisable-: Debugging Options. (line 786)
* fdollars-in-identifiers <1>: Interoperation. (line 141)
-* fdse: Optimize Options. (line 536)
-* fdump-ada-spec: Overall Options. (line 362)
-* fdump-class-hierarchy: Debugging Options. (line 1117)
-* fdump-final-insns: Debugging Options. (line 510)
-* fdump-go-spec: Overall Options. (line 371)
-* fdump-ipa: Debugging Options. (line 1125)
-* fdump-noaddr: Debugging Options. (line 1086)
-* fdump-passes: Debugging Options. (line 1142)
-* fdump-rtl-alignments: Debugging Options. (line 878)
-* fdump-rtl-all: Debugging Options. (line 1059)
-* fdump-rtl-asmcons: Debugging Options. (line 881)
-* fdump-rtl-auto_inc_dec: Debugging Options. (line 885)
-* fdump-rtl-barriers: Debugging Options. (line 889)
-* fdump-rtl-bbpart: Debugging Options. (line 892)
-* fdump-rtl-bbro: Debugging Options. (line 895)
-* fdump-rtl-btl2: Debugging Options. (line 899)
-* fdump-rtl-btl2 <1>: Debugging Options. (line 899)
-* fdump-rtl-bypass: Debugging Options. (line 903)
-* fdump-rtl-ce1: Debugging Options. (line 914)
-* fdump-rtl-ce2: Debugging Options. (line 914)
-* fdump-rtl-ce3: Debugging Options. (line 914)
-* fdump-rtl-combine: Debugging Options. (line 906)
-* fdump-rtl-compgotos: Debugging Options. (line 909)
-* fdump-rtl-cprop_hardreg: Debugging Options. (line 918)
-* fdump-rtl-csa: Debugging Options. (line 921)
-* fdump-rtl-cse1: Debugging Options. (line 925)
-* fdump-rtl-cse2: Debugging Options. (line 925)
-* fdump-rtl-dbr: Debugging Options. (line 932)
-* fdump-rtl-dce: Debugging Options. (line 929)
-* fdump-rtl-dce1: Debugging Options. (line 936)
-* fdump-rtl-dce2: Debugging Options. (line 936)
-* fdump-rtl-dfinish: Debugging Options. (line 1055)
-* fdump-rtl-dfinit: Debugging Options. (line 1055)
-* fdump-rtl-eh: Debugging Options. (line 940)
-* fdump-rtl-eh_ranges: Debugging Options. (line 943)
-* fdump-rtl-expand: Debugging Options. (line 946)
-* fdump-rtl-fwprop1: Debugging Options. (line 950)
-* fdump-rtl-fwprop2: Debugging Options. (line 950)
-* fdump-rtl-gcse1: Debugging Options. (line 955)
-* fdump-rtl-gcse2: Debugging Options. (line 955)
-* fdump-rtl-init-regs: Debugging Options. (line 959)
-* fdump-rtl-initvals: Debugging Options. (line 962)
-* fdump-rtl-into_cfglayout: Debugging Options. (line 965)
-* fdump-rtl-ira: Debugging Options. (line 968)
-* fdump-rtl-jump: Debugging Options. (line 971)
-* fdump-rtl-loop2: Debugging Options. (line 974)
-* fdump-rtl-mach: Debugging Options. (line 978)
-* fdump-rtl-mode_sw: Debugging Options. (line 982)
-* fdump-rtl-outof_cfglayout: Debugging Options. (line 988)
-* fdump-rtl-PASS: Debugging Options. (line 857)
-* fdump-rtl-peephole2: Debugging Options. (line 991)
-* fdump-rtl-postreload: Debugging Options. (line 994)
-* fdump-rtl-pro_and_epilogue: Debugging Options. (line 997)
-* fdump-rtl-ree: Debugging Options. (line 1005)
-* fdump-rtl-regclass: Debugging Options. (line 1055)
-* fdump-rtl-rnreg: Debugging Options. (line 985)
-* fdump-rtl-sched1: Debugging Options. (line 1001)
-* fdump-rtl-sched2: Debugging Options. (line 1001)
-* fdump-rtl-seqabstr: Debugging Options. (line 1008)
-* fdump-rtl-shorten: Debugging Options. (line 1011)
-* fdump-rtl-sibling: Debugging Options. (line 1014)
-* fdump-rtl-sms: Debugging Options. (line 1025)
-* fdump-rtl-split1: Debugging Options. (line 1021)
-* fdump-rtl-split2: Debugging Options. (line 1021)
-* fdump-rtl-split3: Debugging Options. (line 1021)
-* fdump-rtl-split4: Debugging Options. (line 1021)
-* fdump-rtl-split5: Debugging Options. (line 1021)
-* fdump-rtl-stack: Debugging Options. (line 1029)
-* fdump-rtl-subreg1: Debugging Options. (line 1035)
-* fdump-rtl-subreg2: Debugging Options. (line 1035)
-* fdump-rtl-subregs_of_mode_finish: Debugging Options. (line 1055)
-* fdump-rtl-subregs_of_mode_init: Debugging Options. (line 1055)
-* fdump-rtl-unshare: Debugging Options. (line 1039)
-* fdump-rtl-vartrack: Debugging Options. (line 1042)
-* fdump-rtl-vregs: Debugging Options. (line 1045)
-* fdump-rtl-web: Debugging Options. (line 1048)
-* fdump-statistics: Debugging Options. (line 1146)
-* fdump-translation-unit: Debugging Options. (line 1108)
-* fdump-tree: Debugging Options. (line 1158)
-* fdump-tree-alias: Debugging Options. (line 1280)
-* fdump-tree-all: Debugging Options. (line 1364)
-* fdump-tree-ccp: Debugging Options. (line 1284)
-* fdump-tree-cfg: Debugging Options. (line 1268)
-* fdump-tree-ch: Debugging Options. (line 1272)
-* fdump-tree-copyprop: Debugging Options. (line 1300)
-* fdump-tree-copyrename: Debugging Options. (line 1340)
-* fdump-tree-dce: Debugging Options. (line 1308)
-* fdump-tree-dom: Debugging Options. (line 1321)
-* fdump-tree-dse: Debugging Options. (line 1326)
-* fdump-tree-forwprop: Debugging Options. (line 1335)
-* fdump-tree-fre: Debugging Options. (line 1296)
-* fdump-tree-gimple: Debugging Options. (line 1263)
-* fdump-tree-nrv: Debugging Options. (line 1345)
-* fdump-tree-optimized: Debugging Options. (line 1260)
-* fdump-tree-original: Debugging Options. (line 1257)
-* fdump-tree-phiopt: Debugging Options. (line 1330)
-* fdump-tree-pre: Debugging Options. (line 1292)
-* fdump-tree-sink: Debugging Options. (line 1317)
-* fdump-tree-slp: Debugging Options. (line 1355)
-* fdump-tree-sra: Debugging Options. (line 1312)
-* fdump-tree-ssa: Debugging Options. (line 1276)
-* fdump-tree-storeccp: Debugging Options. (line 1288)
-* fdump-tree-store_copyprop: Debugging Options. (line 1304)
-* fdump-tree-vect: Debugging Options. (line 1350)
-* fdump-tree-vrp: Debugging Options. (line 1360)
-* fdump-unnumbered: Debugging Options. (line 1096)
-* fdump-unnumbered-links: Debugging Options. (line 1102)
-* fdwarf2-cfi-asm: Debugging Options. (line 640)
-* fearly-inlining: Optimize Options. (line 290)
-* feliminate-dwarf2-dups: Debugging Options. (line 555)
+* fdollars-in-identifiers: Preprocessor Options.
+ (line 495)
+* fdse: Optimize Options. (line 540)
+* fdump-ada-spec: Overall Options. (line 363)
+* fdump-class-hierarchy: Debugging Options. (line 1115)
+* fdump-final-insns: Debugging Options. (line 505)
+* fdump-go-spec: Overall Options. (line 373)
+* fdump-ipa: Debugging Options. (line 1123)
+* fdump-noaddr: Debugging Options. (line 1084)
+* fdump-passes: Debugging Options. (line 1141)
+* fdump-rtl-alignments: Debugging Options. (line 876)
+* fdump-rtl-all: Debugging Options. (line 1057)
+* fdump-rtl-asmcons: Debugging Options. (line 879)
+* fdump-rtl-auto_inc_dec: Debugging Options. (line 883)
+* fdump-rtl-barriers: Debugging Options. (line 887)
+* fdump-rtl-bbpart: Debugging Options. (line 890)
+* fdump-rtl-bbro: Debugging Options. (line 893)
+* fdump-rtl-btl2: Debugging Options. (line 897)
+* fdump-rtl-bypass: Debugging Options. (line 901)
+* fdump-rtl-ce1: Debugging Options. (line 912)
+* fdump-rtl-ce2: Debugging Options. (line 912)
+* fdump-rtl-ce3: Debugging Options. (line 912)
+* fdump-rtl-combine: Debugging Options. (line 904)
+* fdump-rtl-compgotos: Debugging Options. (line 907)
+* fdump-rtl-cprop_hardreg: Debugging Options. (line 916)
+* fdump-rtl-csa: Debugging Options. (line 919)
+* fdump-rtl-cse1: Debugging Options. (line 923)
+* fdump-rtl-cse2: Debugging Options. (line 923)
+* fdump-rtl-dbr: Debugging Options. (line 930)
+* fdump-rtl-dce: Debugging Options. (line 927)
+* fdump-rtl-dce1: Debugging Options. (line 934)
+* fdump-rtl-dce2: Debugging Options. (line 934)
+* fdump-rtl-dfinish: Debugging Options. (line 1053)
+* fdump-rtl-dfinit: Debugging Options. (line 1053)
+* fdump-rtl-eh: Debugging Options. (line 938)
+* fdump-rtl-eh_ranges: Debugging Options. (line 941)
+* fdump-rtl-expand: Debugging Options. (line 944)
+* fdump-rtl-fwprop1: Debugging Options. (line 948)
+* fdump-rtl-fwprop2: Debugging Options. (line 948)
+* fdump-rtl-gcse1: Debugging Options. (line 953)
+* fdump-rtl-gcse2: Debugging Options. (line 953)
+* fdump-rtl-init-regs: Debugging Options. (line 957)
+* fdump-rtl-initvals: Debugging Options. (line 960)
+* fdump-rtl-into_cfglayout: Debugging Options. (line 963)
+* fdump-rtl-ira: Debugging Options. (line 966)
+* fdump-rtl-jump: Debugging Options. (line 969)
+* fdump-rtl-loop2: Debugging Options. (line 972)
+* fdump-rtl-mach: Debugging Options. (line 976)
+* fdump-rtl-mode_sw: Debugging Options. (line 980)
+* fdump-rtl-outof_cfglayout: Debugging Options. (line 986)
+* fdump-rtl-PASS: Debugging Options. (line 855)
+* fdump-rtl-peephole2: Debugging Options. (line 989)
+* fdump-rtl-postreload: Debugging Options. (line 992)
+* fdump-rtl-pro_and_epilogue: Debugging Options. (line 995)
+* fdump-rtl-ree: Debugging Options. (line 1003)
+* fdump-rtl-regclass: Debugging Options. (line 1053)
+* fdump-rtl-rnreg: Debugging Options. (line 983)
+* fdump-rtl-sched1: Debugging Options. (line 999)
+* fdump-rtl-sched2: Debugging Options. (line 999)
+* fdump-rtl-seqabstr: Debugging Options. (line 1006)
+* fdump-rtl-shorten: Debugging Options. (line 1009)
+* fdump-rtl-sibling: Debugging Options. (line 1012)
+* fdump-rtl-sms: Debugging Options. (line 1023)
+* fdump-rtl-split1: Debugging Options. (line 1019)
+* fdump-rtl-split2: Debugging Options. (line 1019)
+* fdump-rtl-split3: Debugging Options. (line 1019)
+* fdump-rtl-split4: Debugging Options. (line 1019)
+* fdump-rtl-split5: Debugging Options. (line 1019)
+* fdump-rtl-stack: Debugging Options. (line 1027)
+* fdump-rtl-subreg1: Debugging Options. (line 1033)
+* fdump-rtl-subreg2: Debugging Options. (line 1033)
+* fdump-rtl-subregs_of_mode_finish: Debugging Options. (line 1053)
+* fdump-rtl-subregs_of_mode_init: Debugging Options. (line 1053)
+* fdump-rtl-unshare: Debugging Options. (line 1037)
+* fdump-rtl-vartrack: Debugging Options. (line 1040)
+* fdump-rtl-vregs: Debugging Options. (line 1043)
+* fdump-rtl-web: Debugging Options. (line 1046)
+* fdump-statistics: Debugging Options. (line 1145)
+* fdump-translation-unit: Debugging Options. (line 1106)
+* fdump-tree: Debugging Options. (line 1157)
+* fdump-tree-alias: Debugging Options. (line 1296)
+* fdump-tree-all: Debugging Options. (line 1381)
+* fdump-tree-ccp: Debugging Options. (line 1300)
+* fdump-tree-cfg: Debugging Options. (line 1284)
+* fdump-tree-ch: Debugging Options. (line 1288)
+* fdump-tree-copyprop: Debugging Options. (line 1316)
+* fdump-tree-copyrename: Debugging Options. (line 1357)
+* fdump-tree-dce: Debugging Options. (line 1324)
+* fdump-tree-dom: Debugging Options. (line 1337)
+* fdump-tree-dse: Debugging Options. (line 1342)
+* fdump-tree-forwprop: Debugging Options. (line 1352)
+* fdump-tree-fre: Debugging Options. (line 1312)
+* fdump-tree-gimple: Debugging Options. (line 1279)
+* fdump-tree-nrv: Debugging Options. (line 1362)
+* fdump-tree-optimized: Debugging Options. (line 1276)
+* fdump-tree-original: Debugging Options. (line 1273)
+* fdump-tree-phiopt: Debugging Options. (line 1347)
+* fdump-tree-pre: Debugging Options. (line 1308)
+* fdump-tree-sink: Debugging Options. (line 1333)
+* fdump-tree-slp: Debugging Options. (line 1372)
+* fdump-tree-sra: Debugging Options. (line 1328)
+* fdump-tree-ssa: Debugging Options. (line 1292)
+* fdump-tree-store_copyprop: Debugging Options. (line 1320)
+* fdump-tree-storeccp: Debugging Options. (line 1304)
+* fdump-tree-vect: Debugging Options. (line 1367)
+* fdump-tree-vrp: Debugging Options. (line 1377)
+* fdump-unnumbered: Debugging Options. (line 1094)
+* fdump-unnumbered-links: Debugging Options. (line 1100)
+* fdwarf2-cfi-asm: Debugging Options. (line 635)
+* fearly-inlining: Optimize Options. (line 292)
+* feliminate-dwarf2-dups: Debugging Options. (line 550)
* feliminate-unused-debug-symbols: Debugging Options. (line 67)
-* feliminate-unused-debug-types: Debugging Options. (line 1662)
+* feliminate-unused-debug-types: Debugging Options. (line 1686)
* femit-class-debug-always: Debugging Options. (line 71)
-* femit-struct-debug-baseonly: Debugging Options. (line 560)
-* femit-struct-debug-detailed: Debugging Options. (line 587)
-* femit-struct-debug-reduced: Debugging Options. (line 573)
-* fenable-: Debugging Options. (line 787)
-* fexceptions: Code Gen Options. (line 109)
-* fexcess-precision: Optimize Options. (line 2047)
+* femit-struct-debug-baseonly: Debugging Options. (line 555)
+* femit-struct-debug-detailed: Debugging Options. (line 582)
+* femit-struct-debug-reduced: Debugging Options. (line 568)
+* fenable-: Debugging Options. (line 786)
+* fexceptions: Code Gen Options. (line 108)
+* fexcess-precision: Optimize Options. (line 2053)
* fexec-charset: Preprocessor Options.
(line 553)
-* fexpensive-optimizations: Optimize Options. (line 608)
+* fexpensive-optimizations: Optimize Options. (line 612)
* fext-numeric-literals: C++ Dialect Options.
- (line 598)
+ (line 602)
* fextended-identifiers: Preprocessor Options.
- (line 499)
+ (line 498)
* fextern-tls-init: C++ Dialect Options.
- (line 138)
-* ffast-math: Optimize Options. (line 2070)
-* ffat-lto-objects: Optimize Options. (line 1915)
-* ffinite-math-only: Optimize Options. (line 2147)
+ (line 140)
+* ffast-math: Optimize Options. (line 2076)
+* ffat-lto-objects: Optimize Options. (line 1922)
+* ffinite-math-only: Optimize Options. (line 2150)
* ffix-and-continue: Darwin Options. (line 104)
-* ffixed: Code Gen Options. (line 330)
-* ffloat-store: Optimize Options. (line 2033)
+* ffixed: Code Gen Options. (line 332)
* ffloat-store <1>: Disappointments. (line 77)
+* ffloat-store: Optimize Options. (line 2039)
* ffor-scope: C++ Dialect Options.
- (line 159)
-* fforward-propagate: Optimize Options. (line 194)
-* ffp-contract: Optimize Options. (line 203)
-* ffreestanding: Standards. (line 91)
-* ffreestanding <1>: C Dialect Options. (line 252)
-* ffreestanding <2>: Warning Options. (line 268)
-* ffreestanding <3>: Function Attributes.
- (line 460)
+ (line 161)
+* fforward-propagate: Optimize Options. (line 195)
+* ffp-contract: Optimize Options. (line 204)
+* ffreestanding <1>: Function Attributes.
+ (line 464)
+* ffreestanding <2>: Warning Options. (line 270)
+* ffreestanding <3>: C Dialect Options. (line 254)
+* ffreestanding: Standards. (line 92)
* ffriend-injection: C++ Dialect Options.
- (line 110)
-* ffunction-sections: Optimize Options. (line 2352)
-* fgcse: Optimize Options. (line 461)
-* fgcse-after-reload: Optimize Options. (line 497)
-* fgcse-las: Optimize Options. (line 490)
-* fgcse-lm: Optimize Options. (line 472)
-* fgcse-sm: Optimize Options. (line 481)
+ (line 111)
+* ffunction-sections: Optimize Options. (line 2356)
+* fgcse: Optimize Options. (line 465)
+* fgcse-after-reload: Optimize Options. (line 501)
+* fgcse-las: Optimize Options. (line 494)
+* fgcse-lm: Optimize Options. (line 476)
+* fgcse-sm: Optimize Options. (line 485)
* fgnu-runtime: Objective-C and Objective-C++ Dialect Options.
(line 39)
-* fgnu-tm: C Dialect Options. (line 299)
-* fgnu89-inline: C Dialect Options. (line 156)
-* fgraphite-identity: Optimize Options. (line 1169)
-* fhoist-adjacent-loads: Optimize Options. (line 935)
-* fhosted: C Dialect Options. (line 244)
-* fif-conversion: Optimize Options. (line 540)
-* fif-conversion2: Optimize Options. (line 549)
+* fgnu-tm: C Dialect Options. (line 298)
+* fgnu89-inline: C Dialect Options. (line 159)
+* fgraphite-identity: Optimize Options. (line 1174)
+* fhoist-adjacent-loads: Optimize Options. (line 940)
+* fhosted: C Dialect Options. (line 247)
+* fif-conversion: Optimize Options. (line 544)
+* fif-conversion2: Optimize Options. (line 553)
* filelist: Darwin Options. (line 196)
* findirect-data: Darwin Options. (line 104)
-* findirect-inlining: Optimize Options. (line 263)
-* finhibit-size-directive: Code Gen Options. (line 251)
-* finline-functions: Optimize Options. (line 271)
-* finline-functions-called-once: Optimize Options. (line 282)
-* finline-limit: Optimize Options. (line 306)
-* finline-small-functions: Optimize Options. (line 254)
+* findirect-inlining: Optimize Options. (line 265)
+* finhibit-size-directive: Code Gen Options. (line 252)
+* finline-functions: Optimize Options. (line 273)
+* finline-functions-called-once: Optimize Options. (line 284)
+* finline-limit: Optimize Options. (line 309)
+* finline-small-functions: Optimize Options. (line 256)
* finput-charset: Preprocessor Options.
(line 566)
-* finstrument-functions: Code Gen Options. (line 386)
* finstrument-functions <1>: Function Attributes.
- (line 1069)
-* finstrument-functions-exclude-file-list: Code Gen Options. (line 421)
+ (line 1073)
+* finstrument-functions: Code Gen Options. (line 388)
+* finstrument-functions-exclude-file-list: Code Gen Options. (line 424)
* finstrument-functions-exclude-function-list: Code Gen Options.
- (line 442)
-* fipa-cp: Optimize Options. (line 968)
-* fipa-cp-clone: Optimize Options. (line 976)
-* fipa-icf: Optimize Options. (line 993)
-* fipa-profile: Optimize Options. (line 960)
-* fipa-pta: Optimize Options. (line 954)
-* fipa-pure-const: Optimize Options. (line 946)
-* fipa-ra: Optimize Options. (line 893)
-* fipa-reference: Optimize Options. (line 950)
-* fipa-sra: Optimize Options. (line 299)
-* fira-algorithm: Optimize Options. (line 636)
-* fira-hoist-pressure: Optimize Options. (line 665)
-* fira-loop-pressure: Optimize Options. (line 672)
-* fira-region: Optimize Options. (line 644)
-* fira-verbose: Optimize Options. (line 692)
-* fisolate-erroneous-paths-attribute: Optimize Options. (line 1014)
-* fisolate-erroneous-paths-dereference: Optimize Options. (line 1007)
+ (line 444)
+* fipa-cp: Optimize Options. (line 973)
+* fipa-cp-clone: Optimize Options. (line 981)
+* fipa-icf: Optimize Options. (line 998)
+* fipa-profile: Optimize Options. (line 965)
+* fipa-pta: Optimize Options. (line 959)
+* fipa-pure-const: Optimize Options. (line 951)
+* fipa-ra: Optimize Options. (line 898)
+* fipa-reference: Optimize Options. (line 955)
+* fipa-sra: Optimize Options. (line 302)
+* fira-algorithm: Optimize Options. (line 640)
+* fira-hoist-pressure: Optimize Options. (line 670)
+* fira-loop-pressure: Optimize Options. (line 677)
+* fira-region: Optimize Options. (line 648)
+* fira-verbose: Optimize Options. (line 697)
+* fisolate-erroneous-paths-attribute: Optimize Options. (line 1019)
+* fisolate-erroneous-paths-dereference: Optimize Options. (line 1012)
* fivar-visibility: Objective-C and Objective-C++ Dialect Options.
(line 162)
-* fivopts: Optimize Options. (line 1271)
-* fkeep-inline-functions: Optimize Options. (line 337)
+* fivopts: Optimize Options. (line 1277)
* fkeep-inline-functions <1>: Inline. (line 51)
-* fkeep-static-consts: Optimize Options. (line 344)
+* fkeep-inline-functions: Optimize Options. (line 341)
+* fkeep-static-consts: Optimize Options. (line 348)
* flat_namespace: Darwin Options. (line 196)
-* flax-vector-conversions: C Dialect Options. (line 358)
-* fleading-underscore: Code Gen Options. (line 524)
-* flive-range-shrinkage: Optimize Options. (line 631)
+* flax-vector-conversions: C Dialect Options. (line 357)
+* fleading-underscore: Code Gen Options. (line 527)
+* flive-range-shrinkage: Optimize Options. (line 635)
* flocal-ivars: Objective-C and Objective-C++ Dialect Options.
(line 153)
-* floop-block: Optimize Options. (line 1140)
-* floop-interchange: Optimize Options. (line 1095)
-* floop-nest-optimize: Optimize Options. (line 1177)
-* floop-parallelize-all: Optimize Options. (line 1189)
-* floop-strip-mine: Optimize Options. (line 1119)
-* floop-unroll-and-jam: Optimize Options. (line 1183)
-* flra-remat: Optimize Options. (line 698)
-* flto: Optimize Options. (line 1663)
-* flto-compression-level: Optimize Options. (line 1877)
-* flto-odr-type-merging: Optimize Options. (line 1872)
-* flto-partition: Optimize Options. (line 1858)
-* flto-report: Optimize Options. (line 1885)
-* flto-report-wpa: Optimize Options. (line 1893)
+* floop-block: Optimize Options. (line 1145)
+* floop-interchange: Optimize Options. (line 1100)
+* floop-nest-optimize: Optimize Options. (line 1182)
+* floop-parallelize-all: Optimize Options. (line 1195)
+* floop-strip-mine: Optimize Options. (line 1124)
+* floop-unroll-and-jam: Optimize Options. (line 1188)
+* flra-remat: Optimize Options. (line 703)
+* flto: Optimize Options. (line 1669)
+* flto-compression-level: Optimize Options. (line 1884)
+* flto-odr-type-merging: Optimize Options. (line 1879)
+* flto-partition: Optimize Options. (line 1865)
+* flto-report: Optimize Options. (line 1892)
+* flto-report-wpa: Optimize Options. (line 1900)
* fmax-errors: Warning Options. (line 18)
-* fmem-report: Debugging Options. (line 664)
-* fmem-report-wpa: Debugging Options. (line 668)
-* fmerge-all-constants: Optimize Options. (line 363)
-* fmerge-constants: Optimize Options. (line 353)
-* fmerge-debug-strings: Debugging Options. (line 629)
+* fmem-report: Debugging Options. (line 659)
+* fmem-report-wpa: Debugging Options. (line 663)
+* fmerge-all-constants: Optimize Options. (line 367)
+* fmerge-constants: Optimize Options. (line 357)
+* fmerge-debug-strings: Debugging Options. (line 624)
* fmessage-length: Language Independent Options.
(line 14)
-* fmodulo-sched: Optimize Options. (line 374)
-* fmodulo-sched-allow-regmoves: Optimize Options. (line 379)
-* fmove-loop-invariants: Optimize Options. (line 2342)
-* fms-extensions: C Dialect Options. (line 314)
-* fms-extensions <1>: C++ Dialect Options.
- (line 193)
-* fms-extensions <2>: Unnamed Fields. (line 36)
+* fmodulo-sched: Optimize Options. (line 378)
+* fmodulo-sched-allow-regmoves: Optimize Options. (line 383)
+* fmove-loop-invariants: Optimize Options. (line 2346)
+* fms-extensions <1>: Unnamed Fields. (line 36)
+* fms-extensions <2>: C++ Dialect Options.
+ (line 195)
+* fms-extensions: C Dialect Options. (line 313)
* fnext-runtime: Objective-C and Objective-C++ Dialect Options.
(line 43)
* fno-access-control: C++ Dialect Options.
- (line 69)
-* fno-asm: C Dialect Options. (line 196)
-* fno-branch-count-reg: Optimize Options. (line 386)
-* fno-builtin: C Dialect Options. (line 210)
-* fno-builtin <1>: Warning Options. (line 268)
+ (line 70)
+* fno-asm: C Dialect Options. (line 199)
+* fno-branch-count-reg: Optimize Options. (line 390)
+* fno-builtin <1>: Other Builtins. (line 14)
* fno-builtin <2>: Function Attributes.
- (line 460)
-* fno-builtin <3>: Other Builtins. (line 14)
+ (line 464)
+* fno-builtin <3>: Warning Options. (line 270)
+* fno-builtin: C Dialect Options. (line 213)
* fno-canonical-system-headers: Preprocessor Options.
- (line 503)
-* fno-check-pointer-bounds: Debugging Options. (line 392)
-* fno-chkp-check-incomplete-type: Debugging Options. (line 432)
-* fno-chkp-check-read: Debugging Options. (line 482)
-* fno-chkp-check-write: Debugging Options. (line 486)
-* fno-chkp-first-field-has-own-bounds: Debugging Options. (line 443)
-* fno-chkp-instrument-calls: Debugging Options. (line 494)
-* fno-chkp-instrument-marked-only: Debugging Options. (line 498)
-* fno-chkp-narrow-bounds: Debugging Options. (line 436)
-* fno-chkp-narrow-to-innermost-array: Debugging Options. (line 449)
-* fno-chkp-optimize: Debugging Options. (line 454)
-* fno-chkp-store-bounds: Debugging Options. (line 490)
+ (line 502)
+* fno-check-pointer-bounds: Debugging Options. (line 387)
+* fno-chkp-check-incomplete-type: Debugging Options. (line 427)
+* fno-chkp-check-read: Debugging Options. (line 477)
+* fno-chkp-check-write: Debugging Options. (line 481)
+* fno-chkp-first-field-has-own-bounds: Debugging Options. (line 438)
+* fno-chkp-instrument-calls: Debugging Options. (line 489)
+* fno-chkp-instrument-marked-only: Debugging Options. (line 493)
+* fno-chkp-narrow-bounds: Debugging Options. (line 431)
+* fno-chkp-narrow-to-innermost-array: Debugging Options. (line 444)
+* fno-chkp-optimize: Debugging Options. (line 449)
+* fno-chkp-store-bounds: Debugging Options. (line 485)
* fno-chkp-treat-zero-dynamic-size-as-infinite: Debugging Options.
- (line 475)
-* fno-chkp-use-fast-string-functions: Debugging Options. (line 458)
-* fno-chkp-use-nochk-string-functions: Debugging Options. (line 462)
-* fno-chkp-use-static-bounds: Debugging Options. (line 466)
-* fno-chkp-use-static-const-bounds: Debugging Options. (line 470)
-* fno-chkp-use-wrappers: Debugging Options. (line 503)
-* fno-common: Code Gen Options. (line 229)
+ (line 470)
+* fno-chkp-use-fast-string-functions: Debugging Options. (line 453)
+* fno-chkp-use-nochk-string-functions: Debugging Options. (line 457)
+* fno-chkp-use-static-bounds: Debugging Options. (line 461)
+* fno-chkp-use-static-const-bounds: Debugging Options. (line 465)
+* fno-chkp-use-wrappers: Debugging Options. (line 498)
* fno-common <1>: Variable Attributes.
- (line 105)
-* fno-compare-debug: Debugging Options. (line 516)
+ (line 106)
+* fno-common: Code Gen Options. (line 229)
+* fno-compare-debug: Debugging Options. (line 511)
* fno-debug-types-section: Debugging Options. (line 79)
* fno-default-inline: Inline. (line 71)
-* fno-defer-pop: Optimize Options. (line 186)
+* fno-defer-pop: Optimize Options. (line 187)
* fno-diagnostics-show-caret: Language Independent Options.
(line 94)
* fno-diagnostics-show-option: Language Independent Options.
(line 88)
-* fno-dwarf2-cfi-asm: Debugging Options. (line 640)
+* fno-dwarf2-cfi-asm: Debugging Options. (line 635)
* fno-elide-constructors: C++ Dialect Options.
- (line 122)
-* fno-eliminate-unused-debug-types: Debugging Options. (line 1662)
+ (line 123)
+* fno-eliminate-unused-debug-types: Debugging Options. (line 1686)
* fno-enforce-eh-specs: C++ Dialect Options.
- (line 128)
+ (line 129)
* fno-ext-numeric-literals: C++ Dialect Options.
- (line 598)
+ (line 602)
* fno-extern-tls-init: C++ Dialect Options.
- (line 138)
+ (line 140)
* fno-for-scope: C++ Dialect Options.
- (line 159)
-* fno-function-cse: Optimize Options. (line 398)
+ (line 161)
+* fno-function-cse: Optimize Options. (line 402)
* fno-gnu-keywords: C++ Dialect Options.
- (line 171)
+ (line 173)
* fno-gnu-unique: Code Gen Options. (line 152)
-* fno-guess-branch-probability: Optimize Options. (line 1430)
-* fno-ident: Code Gen Options. (line 248)
-* fno-implement-inlines: C++ Dialect Options.
- (line 188)
+* fno-guess-branch-probability: Optimize Options. (line 1436)
+* fno-ident: Code Gen Options. (line 249)
* fno-implement-inlines <1>: C++ Interface. (line 66)
+* fno-implement-inlines: C++ Dialect Options.
+ (line 190)
* fno-implicit-inline-templates: C++ Dialect Options.
- (line 182)
-* fno-implicit-templates: C++ Dialect Options.
- (line 176)
+ (line 184)
* fno-implicit-templates <1>: Template Instantiation.
(line 78)
-* fno-inline: Optimize Options. (line 246)
-* fno-ira-share-save-slots: Optimize Options. (line 680)
-* fno-ira-share-spill-slots: Optimize Options. (line 686)
-* fno-jump-tables: Code Gen Options. (line 322)
-* fno-keep-inline-dllexport: Optimize Options. (line 331)
-* fno-lifetime-dse: Optimize Options. (line 622)
+* fno-implicit-templates: C++ Dialect Options.
+ (line 178)
+* fno-inline: Optimize Options. (line 248)
+* fno-ira-share-save-slots: Optimize Options. (line 685)
+* fno-ira-share-spill-slots: Optimize Options. (line 691)
+* fno-jump-tables: Code Gen Options. (line 324)
+* fno-keep-inline-dllexport: Optimize Options. (line 335)
+* fno-lifetime-dse: Optimize Options. (line 626)
* fno-local-ivars: Objective-C and Objective-C++ Dialect Options.
(line 153)
-* fno-math-errno: Optimize Options. (line 2084)
-* fno-merge-debug-strings: Debugging Options. (line 629)
+* fno-math-errno: Optimize Options. (line 2090)
+* fno-merge-debug-strings: Debugging Options. (line 624)
* fno-nil-receivers: Objective-C and Objective-C++ Dialect Options.
(line 49)
* fno-nonansi-builtins: C++ Dialect Options.
- (line 198)
+ (line 200)
* fno-operator-names: C++ Dialect Options.
- (line 214)
+ (line 216)
* fno-optional-diags: C++ Dialect Options.
- (line 218)
-* fno-peephole: Optimize Options. (line 1421)
-* fno-peephole2: Optimize Options. (line 1421)
+ (line 220)
+* fno-peephole: Optimize Options. (line 1427)
+* fno-peephole2: Optimize Options. (line 1427)
* fno-pretty-templates: C++ Dialect Options.
- (line 228)
+ (line 230)
* fno-rtti: C++ Dialect Options.
- (line 245)
-* fno-sanitize-recover: Debugging Options. (line 358)
-* fno-sanitize=all: Debugging Options. (line 347)
-* fno-sched-interblock: Optimize Options. (line 731)
-* fno-sched-spec: Optimize Options. (line 736)
+ (line 247)
+* fno-sanitize-recover: Debugging Options. (line 353)
+* fno-sanitize=all: Debugging Options. (line 343)
+* fno-sched-interblock: Optimize Options. (line 736)
+* fno-sched-spec: Optimize Options. (line 741)
* fno-set-stack-executable: x86 Windows Options.
(line 46)
* fno-show-column: Preprocessor Options.
- (line 590)
-* fno-signed-bitfields: C Dialect Options. (line 391)
-* fno-signed-zeros: Optimize Options. (line 2159)
-* fno-stack-limit: Code Gen Options. (line 492)
+ (line 591)
+* fno-signed-bitfields: C Dialect Options. (line 390)
+* fno-signed-zeros: Optimize Options. (line 2162)
+* fno-stack-limit: Code Gen Options. (line 495)
* fno-threadsafe-statics: C++ Dialect Options.
- (line 292)
-* fno-toplevel-reorder: Optimize Options. (line 1629)
-* fno-trapping-math: Optimize Options. (line 2169)
-* fno-unsigned-bitfields: C Dialect Options. (line 391)
+ (line 294)
+* fno-toplevel-reorder: Optimize Options. (line 1635)
+* fno-trapping-math: Optimize Options. (line 2172)
+* fno-unsigned-bitfields: C Dialect Options. (line 390)
* fno-use-cxa-get-exception-ptr: C++ Dialect Options.
- (line 305)
-* fno-var-tracking-assignments: Debugging Options. (line 1568)
-* fno-var-tracking-assignments-toggle: Debugging Options. (line 1579)
+ (line 307)
+* fno-var-tracking-assignments: Debugging Options. (line 1592)
+* fno-var-tracking-assignments-toggle: Debugging Options. (line 1603)
* fno-weak: C++ Dialect Options.
- (line 419)
+ (line 421)
* fno-working-directory: Preprocessor Options.
(line 576)
* fno-writable-relocated-rdata: x86 Windows Options.
(line 53)
-* fno-zero-initialized-in-bss: Optimize Options. (line 409)
-* fnon-call-exceptions: Code Gen Options. (line 123)
+* fno-zero-initialized-in-bss: Optimize Options. (line 413)
+* fnon-call-exceptions: Code Gen Options. (line 122)
* fnothrow-opt: C++ Dialect Options.
- (line 203)
+ (line 205)
* fobjc-abi-version: Objective-C and Objective-C++ Dialect Options.
(line 56)
* fobjc-call-cxx-cdtors: Objective-C and Objective-C++ Dialect Options.
@@ -48613,262 +49087,262 @@ look up both forms.
(line 111)
* fobjc-std: Objective-C and Objective-C++ Dialect Options.
(line 120)
-* fomit-frame-pointer: Optimize Options. (line 214)
-* fopenacc: C Dialect Options. (line 263)
+* fomit-frame-pointer: Optimize Options. (line 215)
+* fopenacc: C Dialect Options. (line 264)
* fopenmp: C Dialect Options. (line 276)
-* fopenmp-simd: C Dialect Options. (line 285)
-* fopt-info: Debugging Options. (line 1370)
-* foptimize-sibling-calls: Optimize Options. (line 234)
-* foptimize-strlen: Optimize Options. (line 239)
+* fopenmp-simd: C Dialect Options. (line 284)
+* fopt-info: Debugging Options. (line 1387)
+* foptimize-sibling-calls: Optimize Options. (line 236)
+* foptimize-strlen: Optimize Options. (line 241)
* force_cpusubtype_ALL: Darwin Options. (line 135)
* force_flat_namespace: Darwin Options. (line 196)
-* fpack-struct: Code Gen Options. (line 373)
-* fpartial-inlining: Optimize Options. (line 1396)
-* fpcc-struct-return: Code Gen Options. (line 165)
+* fpack-struct: Code Gen Options. (line 375)
+* fpartial-inlining: Optimize Options. (line 1402)
* fpcc-struct-return <1>: Incompatibilities. (line 170)
+* fpcc-struct-return: Code Gen Options. (line 165)
* fpch-deps: Preprocessor Options.
- (line 296)
+ (line 294)
* fpch-preprocess: Preprocessor Options.
- (line 304)
-* fpeel-loops: Optimize Options. (line 2334)
+ (line 302)
+* fpeel-loops: Optimize Options. (line 2338)
* fpermissive: C++ Dialect Options.
- (line 223)
-* fpic: Code Gen Options. (line 279)
-* fPIC: Code Gen Options. (line 300)
-* fpie: Code Gen Options. (line 313)
-* fPIE: Code Gen Options. (line 313)
-* fplan9-extensions: C Dialect Options. (line 332)
-* fplan9-extensions <1>: Unnamed Fields. (line 43)
+ (line 225)
+* fPIC: Code Gen Options. (line 301)
+* fpic: Code Gen Options. (line 280)
+* fPIE: Code Gen Options. (line 314)
+* fpie: Code Gen Options. (line 314)
+* fplan9-extensions <1>: Unnamed Fields. (line 44)
+* fplan9-extensions: C Dialect Options. (line 331)
* fplugin: Overall Options. (line 351)
-* fplugin-arg: Overall Options. (line 358)
-* fpost-ipa-mem-report: Debugging Options. (line 673)
-* fpre-ipa-mem-report: Debugging Options. (line 672)
-* fpredictive-commoning: Optimize Options. (line 1403)
-* fprefetch-loop-arrays: Optimize Options. (line 1410)
+* fplugin-arg: Overall Options. (line 359)
+* fpost-ipa-mem-report: Debugging Options. (line 669)
+* fpre-ipa-mem-report: Debugging Options. (line 667)
+* fpredictive-commoning: Optimize Options. (line 1409)
+* fprefetch-loop-arrays: Optimize Options. (line 1416)
* fpreprocessed: Preprocessor Options.
- (line 507)
-* fprofile-arcs: Debugging Options. (line 710)
-* fprofile-arcs <1>: Other Builtins. (line 260)
-* fprofile-correction: Optimize Options. (line 1952)
-* fprofile-dir: Optimize Options. (line 1959)
-* fprofile-generate: Optimize Options. (line 1970)
-* fprofile-reorder-functions: Optimize Options. (line 2276)
-* fprofile-report: Debugging Options. (line 677)
-* fprofile-use: Optimize Options. (line 1984)
-* fprofile-values: Optimize Options. (line 2267)
+ (line 506)
+* fprofile-arcs <1>: Other Builtins. (line 264)
+* fprofile-arcs: Debugging Options. (line 708)
+* fprofile-correction: Optimize Options. (line 1960)
+* fprofile-dir: Optimize Options. (line 1967)
+* fprofile-generate: Optimize Options. (line 1977)
+* fprofile-reorder-functions: Optimize Options. (line 2280)
+* fprofile-report: Debugging Options. (line 673)
+* fprofile-use: Optimize Options. (line 1990)
+* fprofile-values: Optimize Options. (line 2271)
* fpu: RX Options. (line 17)
-* frandom-seed: Debugging Options. (line 1462)
-* freciprocal-math: Optimize Options. (line 2137)
-* frecord-gcc-switches: Code Gen Options. (line 267)
-* free: Optimize Options. (line 614)
+* frandom-seed: Debugging Options. (line 1486)
+* freciprocal-math: Optimize Options. (line 2141)
+* frecord-gcc-switches: Code Gen Options. (line 268)
+* free: Optimize Options. (line 618)
* freg-struct-return: Code Gen Options. (line 183)
-* frename-registers: Optimize Options. (line 2293)
-* freorder-blocks: Optimize Options. (line 1447)
-* freorder-blocks-and-partition: Optimize Options. (line 1453)
-* freorder-functions: Optimize Options. (line 1466)
+* frename-registers: Optimize Options. (line 2297)
+* freorder-blocks: Optimize Options. (line 1453)
+* freorder-blocks-and-partition: Optimize Options. (line 1459)
+* freorder-functions: Optimize Options. (line 1472)
* freplace-objc-classes: Objective-C and Objective-C++ Dialect Options.
(line 131)
-* frepo: C++ Dialect Options.
- (line 240)
* frepo <1>: Template Instantiation.
(line 54)
-* freport-bug: Debugging Options. (line 1092)
-* frerun-cse-after-loop: Optimize Options. (line 455)
-* freschedule-modulo-scheduled-loops: Optimize Options. (line 830)
-* frounding-math: Optimize Options. (line 2184)
-* fsanitize-recover: Debugging Options. (line 358)
-* fsanitize-undefined-trap-on-error: Debugging Options. (line 385)
+* frepo: C++ Dialect Options.
+ (line 242)
+* freport-bug: Debugging Options. (line 1090)
+* frerun-cse-after-loop: Optimize Options. (line 459)
+* freschedule-modulo-scheduled-loops: Optimize Options. (line 835)
+* frounding-math: Optimize Options. (line 2187)
+* fsanitize-recover: Debugging Options. (line 353)
+* fsanitize-undefined-trap-on-error: Debugging Options. (line 380)
* fsanitize=address: Debugging Options. (line 199)
* fsanitize=alignment: Debugging Options. (line 287)
-* fsanitize=bool: Debugging Options. (line 325)
+* fsanitize=bool: Debugging Options. (line 323)
* fsanitize=bounds: Debugging Options. (line 281)
-* fsanitize=enum: Debugging Options. (line 330)
-* fsanitize=float-cast-overflow: Debugging Options. (line 305)
-* fsanitize=float-divide-by-zero: Debugging Options. (line 299)
+* fsanitize=enum: Debugging Options. (line 327)
+* fsanitize=float-cast-overflow: Debugging Options. (line 304)
+* fsanitize=float-divide-by-zero: Debugging Options. (line 298)
* fsanitize=integer-divide-by-zero: Debugging Options. (line 244)
* fsanitize=kernel-address: Debugging Options. (line 209)
* fsanitize=leak: Debugging Options. (line 223)
-* fsanitize=nonnull-attribute: Debugging Options. (line 313)
+* fsanitize=nonnull-attribute: Debugging Options. (line 312)
* fsanitize=null: Debugging Options. (line 258)
-* fsanitize=object-size: Debugging Options. (line 294)
+* fsanitize=object-size: Debugging Options. (line 293)
* fsanitize=return: Debugging Options. (line 266)
-* fsanitize=returns-nonnull-attribute: Debugging Options. (line 319)
+* fsanitize=returns-nonnull-attribute: Debugging Options. (line 318)
* fsanitize=shift: Debugging Options. (line 238)
* fsanitize=signed-integer-overflow: Debugging Options. (line 272)
* fsanitize=thread: Debugging Options. (line 214)
* fsanitize=undefined: Debugging Options. (line 233)
* fsanitize=unreachable: Debugging Options. (line 248)
* fsanitize=vla-bound: Debugging Options. (line 254)
-* fsanitize=vptr: Debugging Options. (line 336)
-* fsched-critical-path-heuristic: Optimize Options. (line 796)
-* fsched-dep-count-heuristic: Optimize Options. (line 823)
-* fsched-group-heuristic: Optimize Options. (line 790)
-* fsched-last-insn-heuristic: Optimize Options. (line 816)
-* fsched-pressure: Optimize Options. (line 741)
-* fsched-rank-heuristic: Optimize Options. (line 809)
-* fsched-spec-insn-heuristic: Optimize Options. (line 802)
-* fsched-spec-load: Optimize Options. (line 750)
-* fsched-spec-load-dangerous: Optimize Options. (line 755)
-* fsched-stalled-insns: Optimize Options. (line 761)
-* fsched-stalled-insns-dep: Optimize Options. (line 771)
-* fsched-verbose: Debugging Options. (line 1472)
-* fsched2-use-superblocks: Optimize Options. (line 780)
-* fschedule-fusion: Optimize Options. (line 2303)
-* fschedule-insns: Optimize Options. (line 712)
-* fschedule-insns2: Optimize Options. (line 722)
-* fsection-anchors: Optimize Options. (line 2410)
-* fsel-sched-pipelining: Optimize Options. (line 843)
-* fsel-sched-pipelining-outer-loops: Optimize Options. (line 848)
-* fselective-scheduling: Optimize Options. (line 835)
-* fselective-scheduling2: Optimize Options. (line 839)
-* fsemantic-interposition: Optimize Options. (line 853)
+* fsanitize=vptr: Debugging Options. (line 332)
+* fsched-critical-path-heuristic: Optimize Options. (line 801)
+* fsched-dep-count-heuristic: Optimize Options. (line 828)
+* fsched-group-heuristic: Optimize Options. (line 795)
+* fsched-last-insn-heuristic: Optimize Options. (line 821)
+* fsched-pressure: Optimize Options. (line 746)
+* fsched-rank-heuristic: Optimize Options. (line 814)
+* fsched-spec-insn-heuristic: Optimize Options. (line 807)
+* fsched-spec-load: Optimize Options. (line 755)
+* fsched-spec-load-dangerous: Optimize Options. (line 760)
+* fsched-stalled-insns: Optimize Options. (line 766)
+* fsched-stalled-insns-dep: Optimize Options. (line 776)
+* fsched-verbose: Debugging Options. (line 1496)
+* fsched2-use-superblocks: Optimize Options. (line 785)
+* fschedule-fusion: Optimize Options. (line 2307)
+* fschedule-insns: Optimize Options. (line 717)
+* fschedule-insns2: Optimize Options. (line 727)
+* fsection-anchors: Optimize Options. (line 2414)
+* fsel-sched-pipelining: Optimize Options. (line 848)
+* fsel-sched-pipelining-outer-loops: Optimize Options. (line 853)
+* fselective-scheduling: Optimize Options. (line 840)
+* fselective-scheduling2: Optimize Options. (line 844)
+* fsemantic-interposition: Optimize Options. (line 858)
* fshort-double: Code Gen Options. (line 211)
-* fshort-enums: Code Gen Options. (line 201)
-* fshort-enums <1>: Structures unions enumerations and bit-fields implementation.
- (line 48)
+* fshort-enums <1>: Non-bugs. (line 42)
* fshort-enums <2>: Type Attributes. (line 114)
-* fshort-enums <3>: Non-bugs. (line 42)
+* fshort-enums <3>: Structures unions enumerations and bit-fields implementation.
+ (line 48)
+* fshort-enums: Code Gen Options. (line 201)
* fshort-wchar: Code Gen Options. (line 219)
-* fshrink-wrap: Optimize Options. (line 870)
-* fsignaling-nans: Optimize Options. (line 2204)
-* fsigned-bitfields: C Dialect Options. (line 391)
+* fshrink-wrap: Optimize Options. (line 875)
+* fsignaling-nans: Optimize Options. (line 2207)
* fsigned-bitfields <1>: Non-bugs. (line 57)
-* fsigned-char: C Dialect Options. (line 381)
+* fsigned-bitfields: C Dialect Options. (line 390)
* fsigned-char <1>: Characters implementation.
(line 31)
-* fsimd-cost-model: Optimize Options. (line 1361)
-* fsingle-precision-constant: Optimize Options. (line 2219)
+* fsigned-char: C Dialect Options. (line 380)
+* fsimd-cost-model: Optimize Options. (line 1367)
+* fsingle-precision-constant: Optimize Options. (line 2222)
* fsized-deallocation: C++ Dialect Options.
- (line 255)
-* fsplit-ivs-in-unroller: Optimize Options. (line 1377)
-* fsplit-stack: Code Gen Options. (line 506)
+ (line 257)
+* fsplit-ivs-in-unroller: Optimize Options. (line 1383)
* fsplit-stack <1>: Function Attributes.
- (line 1074)
-* fsplit-wide-types: Optimize Options. (line 430)
-* fssa-phiopt: Optimize Options. (line 1037)
-* fstack-check: Code Gen Options. (line 454)
-* fstack-limit-register: Code Gen Options. (line 492)
-* fstack-limit-symbol: Code Gen Options. (line 492)
-* fstack-protector: Optimize Options. (line 2385)
-* fstack-protector-all: Optimize Options. (line 2394)
-* fstack-protector-explicit: Optimize Options. (line 2402)
-* fstack-protector-strong: Optimize Options. (line 2397)
-* fstack-usage: Debugging Options. (line 681)
+ (line 1078)
+* fsplit-stack: Code Gen Options. (line 509)
+* fsplit-wide-types: Optimize Options. (line 434)
+* fssa-phiopt: Optimize Options. (line 1042)
+* fstack-check: Code Gen Options. (line 456)
+* fstack-limit-register: Code Gen Options. (line 495)
+* fstack-limit-symbol: Code Gen Options. (line 495)
+* fstack-protector: Optimize Options. (line 2389)
+* fstack-protector-all: Optimize Options. (line 2398)
+* fstack-protector-explicit: Optimize Options. (line 2406)
+* fstack-protector-strong: Optimize Options. (line 2401)
+* fstack-usage: Debugging Options. (line 677)
* fstack_reuse: Code Gen Options. (line 21)
* fstats: C++ Dialect Options.
- (line 265)
-* fstdarg-opt: Optimize Options. (line 2406)
-* fstrict-aliasing: Optimize Options. (line 1479)
+ (line 267)
+* fstdarg-opt: Optimize Options. (line 2410)
+* fstrict-aliasing: Optimize Options. (line 1485)
* fstrict-enums: C++ Dialect Options.
- (line 270)
-* fstrict-overflow: Optimize Options. (line 1525)
-* fstrict-volatile-bitfields: Code Gen Options. (line 611)
-* fsync-libcalls: Code Gen Options. (line 643)
+ (line 272)
+* fstrict-overflow: Optimize Options. (line 1531)
+* fstrict-volatile-bitfields: Code Gen Options. (line 614)
+* fsync-libcalls: Code Gen Options. (line 647)
* fsyntax-only: Warning Options. (line 14)
* ftabstop: Preprocessor Options.
- (line 520)
+ (line 519)
* ftemplate-backtrace-limit: C++ Dialect Options.
- (line 279)
+ (line 281)
* ftemplate-depth: C++ Dialect Options.
- (line 283)
-* ftest-coverage: Debugging Options. (line 765)
-* fthread-jumps: Optimize Options. (line 421)
-* ftime-report: Debugging Options. (line 660)
-* ftls-model: Code Gen Options. (line 535)
-* ftracer: Optimize Options. (line 2311)
+ (line 285)
+* ftest-coverage: Debugging Options. (line 764)
+* fthread-jumps: Optimize Options. (line 425)
+* ftime-report: Debugging Options. (line 655)
+* ftls-model: Code Gen Options. (line 538)
+* ftracer: Optimize Options. (line 2315)
* ftrack-macro-expansion: Preprocessor Options.
(line 535)
-* ftrapv: Code Gen Options. (line 97)
-* ftree-bit-ccp: Optimize Options. (line 1026)
-* ftree-builtin-call-dce: Optimize Options. (line 1058)
-* ftree-ccp: Optimize Options. (line 1032)
-* ftree-ch: Optimize Options. (line 1078)
-* ftree-coalesce-inlined-vars: Optimize Options. (line 1302)
-* ftree-coalesce-vars: Optimize Options. (line 1311)
-* ftree-copy-prop: Optimize Options. (line 941)
-* ftree-copyrename: Optimize Options. (line 1295)
-* ftree-dce: Optimize Options. (line 1054)
-* ftree-dominator-opts: Optimize Options. (line 1064)
-* ftree-dse: Optimize Options. (line 1071)
-* ftree-forwprop: Optimize Options. (line 920)
-* ftree-fre: Optimize Options. (line 924)
-* ftree-loop-distribute-patterns: Optimize Options. (line 1236)
-* ftree-loop-distribution: Optimize Options. (line 1219)
-* ftree-loop-if-convert: Optimize Options. (line 1199)
-* ftree-loop-if-convert-stores: Optimize Options. (line 1206)
-* ftree-loop-im: Optimize Options. (line 1256)
-* ftree-loop-ivcanon: Optimize Options. (line 1265)
-* ftree-loop-linear: Optimize Options. (line 1089)
-* ftree-loop-optimize: Optimize Options. (line 1085)
-* ftree-loop-vectorize: Optimize Options. (line 1339)
-* ftree-parallelize-loops: Optimize Options. (line 1276)
-* ftree-partial-pre: Optimize Options. (line 916)
-* ftree-phiprop: Optimize Options. (line 931)
-* ftree-pre: Optimize Options. (line 912)
-* ftree-pta: Optimize Options. (line 1285)
-* ftree-reassoc: Optimize Options. (line 908)
-* ftree-sink: Optimize Options. (line 1022)
-* ftree-slp-vectorize: Optimize Options. (line 1343)
-* ftree-slsr: Optimize Options. (line 1328)
-* ftree-sra: Optimize Options. (line 1289)
-* ftree-switch-conversion: Optimize Options. (line 1041)
-* ftree-tail-merge: Optimize Options. (line 1046)
-* ftree-ter: Optimize Options. (line 1320)
-* ftree-vectorize: Optimize Options. (line 1334)
-* ftree-vrp: Optimize Options. (line 1368)
-* funit-at-a-time: Optimize Options. (line 1622)
-* funroll-all-loops: Optimize Options. (line 2328)
-* funroll-loops: Optimize Options. (line 2318)
-* funsafe-loop-optimizations: Optimize Options. (line 511)
-* funsafe-math-optimizations: Optimize Options. (line 2102)
-* funsigned-bitfields: C Dialect Options. (line 391)
-* funsigned-bitfields <1>: Structures unions enumerations and bit-fields implementation.
+* ftrapv: Code Gen Options. (line 96)
+* ftree-bit-ccp: Optimize Options. (line 1031)
+* ftree-builtin-call-dce: Optimize Options. (line 1063)
+* ftree-ccp: Optimize Options. (line 1037)
+* ftree-ch: Optimize Options. (line 1083)
+* ftree-coalesce-inlined-vars: Optimize Options. (line 1308)
+* ftree-coalesce-vars: Optimize Options. (line 1317)
+* ftree-copy-prop: Optimize Options. (line 946)
+* ftree-copyrename: Optimize Options. (line 1301)
+* ftree-dce: Optimize Options. (line 1059)
+* ftree-dominator-opts: Optimize Options. (line 1069)
+* ftree-dse: Optimize Options. (line 1076)
+* ftree-forwprop: Optimize Options. (line 925)
+* ftree-fre: Optimize Options. (line 929)
+* ftree-loop-distribute-patterns: Optimize Options. (line 1242)
+* ftree-loop-distribution: Optimize Options. (line 1225)
+* ftree-loop-if-convert: Optimize Options. (line 1205)
+* ftree-loop-if-convert-stores: Optimize Options. (line 1212)
+* ftree-loop-im: Optimize Options. (line 1262)
+* ftree-loop-ivcanon: Optimize Options. (line 1271)
+* ftree-loop-linear: Optimize Options. (line 1094)
+* ftree-loop-optimize: Optimize Options. (line 1090)
+* ftree-loop-vectorize: Optimize Options. (line 1345)
+* ftree-parallelize-loops: Optimize Options. (line 1282)
+* ftree-partial-pre: Optimize Options. (line 921)
+* ftree-phiprop: Optimize Options. (line 936)
+* ftree-pre: Optimize Options. (line 917)
+* ftree-pta: Optimize Options. (line 1291)
+* ftree-reassoc: Optimize Options. (line 913)
+* ftree-sink: Optimize Options. (line 1027)
+* ftree-slp-vectorize: Optimize Options. (line 1349)
+* ftree-slsr: Optimize Options. (line 1334)
+* ftree-sra: Optimize Options. (line 1295)
+* ftree-switch-conversion: Optimize Options. (line 1046)
+* ftree-tail-merge: Optimize Options. (line 1051)
+* ftree-ter: Optimize Options. (line 1326)
+* ftree-vectorize: Optimize Options. (line 1340)
+* ftree-vrp: Optimize Options. (line 1374)
+* funit-at-a-time: Optimize Options. (line 1628)
+* funroll-all-loops: Optimize Options. (line 2332)
+* funroll-loops: Optimize Options. (line 2322)
+* funsafe-loop-optimizations: Optimize Options. (line 515)
+* funsafe-math-optimizations: Optimize Options. (line 2108)
+* funsigned-bitfields <1>: Non-bugs. (line 57)
+* funsigned-bitfields <2>: Structures unions enumerations and bit-fields implementation.
(line 17)
-* funsigned-bitfields <2>: Non-bugs. (line 57)
-* funsigned-char: C Dialect Options. (line 363)
+* funsigned-bitfields: C Dialect Options. (line 390)
* funsigned-char <1>: Characters implementation.
(line 31)
-* funswitch-loops: Optimize Options. (line 2346)
+* funsigned-char: C Dialect Options. (line 362)
+* funswitch-loops: Optimize Options. (line 2350)
* funwind-tables: Code Gen Options. (line 139)
* fuse-cxa-atexit: C++ Dialect Options.
- (line 298)
+ (line 300)
* fuse-ld=bfd: Link Options. (line 25)
* fuse-ld=gold: Link Options. (line 28)
-* fuse-linker-plugin: Optimize Options. (line 1897)
-* fvar-tracking: Debugging Options. (line 1558)
-* fvar-tracking-assignments: Debugging Options. (line 1568)
-* fvar-tracking-assignments-toggle: Debugging Options. (line 1579)
-* fvariable-expansion-in-unroller: Optimize Options. (line 1391)
-* fvect-cost-model: Optimize Options. (line 1347)
-* fverbose-asm: Code Gen Options. (line 258)
-* fvisibility: Code Gen Options. (line 546)
+* fuse-linker-plugin: Optimize Options. (line 1904)
+* fvar-tracking: Debugging Options. (line 1582)
+* fvar-tracking-assignments: Debugging Options. (line 1592)
+* fvar-tracking-assignments-toggle: Debugging Options. (line 1603)
+* fvariable-expansion-in-unroller: Optimize Options. (line 1397)
+* fvect-cost-model: Optimize Options. (line 1353)
+* fverbose-asm: Code Gen Options. (line 259)
+* fvisibility: Code Gen Options. (line 549)
* fvisibility-inlines-hidden: C++ Dialect Options.
- (line 310)
+ (line 312)
* fvisibility-ms-compat: C++ Dialect Options.
- (line 338)
-* fvpt: Optimize Options. (line 2283)
+ (line 340)
+* fvpt: Optimize Options. (line 2287)
* fvtable-verify: C++ Dialect Options.
- (line 367)
+ (line 369)
* fvtv-counts: C++ Dialect Options.
- (line 402)
+ (line 404)
* fvtv-debug: C++ Dialect Options.
- (line 389)
-* fweb: Optimize Options. (line 1641)
-* fwhole-program: Optimize Options. (line 1652)
+ (line 391)
+* fweb: Optimize Options. (line 1647)
+* fwhole-program: Optimize Options. (line 1658)
* fwide-exec-charset: Preprocessor Options.
(line 558)
* fworking-directory: Preprocessor Options.
(line 576)
-* fwrapv: Code Gen Options. (line 101)
+* fwrapv: Code Gen Options. (line 100)
* fzero-link: Objective-C and Objective-C++ Dialect Options.
(line 141)
-* g: Debugging Options. (line 10)
+* G <1>: System V Options. (line 10)
+* G <2>: RS/6000 and PowerPC Options.
+ (line 770)
+* G <3>: Nios II Options. (line 9)
+* G <4>: MIPS Options. (line 440)
* G: M32R/D Options. (line 57)
-* G <1>: MIPS Options. (line 436)
-* G <2>: Nios II Options. (line 9)
-* G <3>: RS/6000 and PowerPC Options.
- (line 767)
-* G <4>: System V Options. (line 10)
+* g: Debugging Options. (line 10)
* gcoff: Debugging Options. (line 94)
* gdwarf-VERSION: Debugging Options. (line 112)
* gen-decls: Objective-C and Objective-C++ Dialect Options.
@@ -48891,59 +49365,59 @@ look up both forms.
* gxcoff+: Debugging Options. (line 104)
* gz: Debugging Options. (line 147)
* H: Preprocessor Options.
- (line 706)
+ (line 709)
* headerpad_max_install_names: Darwin Options. (line 196)
-* help: Overall Options. (line 221)
* help <1>: Preprocessor Options.
- (line 698)
+ (line 701)
+* help: Overall Options. (line 221)
+* I <1>: Directory Options. (line 10)
* I: Preprocessor Options.
(line 77)
-* I <1>: Directory Options. (line 10)
+* I- <1>: Directory Options. (line 118)
* I-: Preprocessor Options.
- (line 389)
-* I- <1>: Directory Options. (line 116)
+ (line 387)
* idirafter: Preprocessor Options.
- (line 431)
+ (line 429)
* iframework: Darwin Options. (line 57)
* imacros: Preprocessor Options.
- (line 422)
+ (line 420)
* image_base: Darwin Options. (line 196)
* imultilib: Preprocessor Options.
- (line 456)
+ (line 454)
* include: Preprocessor Options.
- (line 411)
+ (line 409)
* init: Darwin Options. (line 196)
* install_name: Darwin Options. (line 196)
-* iplugindir=: Directory Options. (line 29)
+* iplugindir=: Directory Options. (line 31)
* iprefix: Preprocessor Options.
- (line 438)
+ (line 436)
+* iquote <1>: Directory Options. (line 36)
* iquote: Preprocessor Options.
- (line 468)
-* iquote <1>: Directory Options. (line 34)
+ (line 466)
* isysroot: Preprocessor Options.
- (line 450)
+ (line 448)
* isystem: Preprocessor Options.
- (line 460)
+ (line 458)
* iwithprefix: Preprocessor Options.
- (line 444)
+ (line 442)
* iwithprefixbefore: Preprocessor Options.
- (line 444)
+ (line 442)
* keep_private_externs: Darwin Options. (line 196)
+* L: Directory Options. (line 42)
* l: Link Options. (line 32)
-* L: Directory Options. (line 40)
* lobjc: Link Options. (line 59)
+* m: RS/6000 and PowerPC Options.
+ (line 611)
* M: Preprocessor Options.
(line 185)
-* m: RS/6000 and PowerPC Options.
- (line 609)
* m1: SH Options. (line 9)
* m10: PDP-11 Options. (line 29)
-* m128bit-long-double: x86 Options. (line 389)
-* m16: x86 Options. (line 954)
-* m16-bit: CRIS Options. (line 64)
+* m128bit-long-double: x86 Options. (line 396)
+* m16: x86 Options. (line 965)
* m16-bit <1>: NDS32 Options. (line 39)
+* m16-bit: CRIS Options. (line 64)
* m1reg-: Adapteva Epiphany Options.
- (line 131)
+ (line 132)
* m2: SH Options. (line 12)
* m210: MCore Options. (line 43)
* m2a: SH Options. (line 30)
@@ -48952,22 +49426,22 @@ look up both forms.
* m2a-single-only: SH Options. (line 22)
* m3: SH Options. (line 34)
* m31: S/390 and zSeries Options.
- (line 86)
-* m32: Nvidia PTX Options. (line 10)
-* m32 <1>: RS/6000 and PowerPC Options.
- (line 302)
-* m32 <2>: SPARC Options. (line 256)
+ (line 87)
+* m32 <1>: x86 Options. (line 965)
+* m32 <2>: TILEPro Options. (line 13)
* m32 <3>: TILE-Gx Options. (line 23)
-* m32 <4>: TILEPro Options. (line 13)
-* m32 <5>: x86 Options. (line 954)
+* m32 <4>: SPARC Options. (line 257)
+* m32 <5>: RS/6000 and PowerPC Options.
+ (line 303)
+* m32: Nvidia PTX Options. (line 10)
* m32-bit: CRIS Options. (line 64)
-* m32bit-doubles: RL78 Options. (line 22)
* m32bit-doubles <1>: RX Options. (line 10)
+* m32bit-doubles: RL78 Options. (line 22)
* m32r: M32R/D Options. (line 15)
* m32r2: M32R/D Options. (line 9)
* m32rx: M32R/D Options. (line 12)
* m340: MCore Options. (line 43)
-* m3dnow: x86 Options. (line 603)
+* m3dnow: x86 Options. (line 609)
* m3e: SH Options. (line 37)
* m4: SH Options. (line 51)
* m4-100: SH Options. (line 54)
@@ -49001,266 +49475,263 @@ look up both forms.
* m5-64media-nofpu: SH Options. (line 136)
* m5-compact: SH Options. (line 140)
* m5-compact-nofpu: SH Options. (line 143)
-* m5200: M680x0 Options. (line 144)
-* m5206e: M680x0 Options. (line 153)
-* m528x: M680x0 Options. (line 157)
-* m5307: M680x0 Options. (line 161)
-* m5407: M680x0 Options. (line 165)
+* m5200: M680x0 Options. (line 147)
+* m5206e: M680x0 Options. (line 156)
+* m528x: M680x0 Options. (line 160)
+* m5307: M680x0 Options. (line 164)
+* m5407: M680x0 Options. (line 168)
+* m64 <1>: x86 Options. (line 965)
+* m64 <2>: TILE-Gx Options. (line 23)
+* m64 <3>: SPARC Options. (line 257)
+* m64 <4>: S/390 and zSeries Options.
+ (line 87)
+* m64 <5>: RS/6000 and PowerPC Options.
+ (line 303)
* m64: Nvidia PTX Options. (line 10)
-* m64 <1>: RS/6000 and PowerPC Options.
- (line 302)
-* m64 <2>: S/390 and zSeries Options.
- (line 86)
-* m64 <3>: SPARC Options. (line 256)
-* m64 <4>: TILE-Gx Options. (line 23)
-* m64 <5>: x86 Options. (line 954)
-* m64bit-doubles: RL78 Options. (line 22)
* m64bit-doubles <1>: RX Options. (line 10)
-* m68000: M680x0 Options. (line 93)
-* m68010: M680x0 Options. (line 101)
-* m68020: M680x0 Options. (line 107)
-* m68020-40: M680x0 Options. (line 175)
-* m68020-60: M680x0 Options. (line 184)
-* m68030: M680x0 Options. (line 112)
-* m68040: M680x0 Options. (line 117)
-* m68060: M680x0 Options. (line 126)
-* m68881: M680x0 Options. (line 194)
+* m64bit-doubles: RL78 Options. (line 22)
+* m68000: M680x0 Options. (line 95)
+* m68010: M680x0 Options. (line 103)
+* m68020: M680x0 Options. (line 109)
+* m68020-40: M680x0 Options. (line 178)
+* m68020-60: M680x0 Options. (line 187)
+* m68030: M680x0 Options. (line 114)
+* m68040: M680x0 Options. (line 119)
+* m68060: M680x0 Options. (line 128)
+* m68881: M680x0 Options. (line 197)
* m8-bit: CRIS Options. (line 64)
-* m8bit-idiv: x86 Options. (line 931)
+* m8bit-idiv: x86 Options. (line 940)
* m8byte-align: V850 Options. (line 170)
-* m96bit-long-double: x86 Options. (line 389)
+* m96bit-long-double: x86 Options. (line 396)
* mA6: ARC Options. (line 19)
* mA7: ARC Options. (line 26)
-* mabi: AArch64 Options. (line 9)
-* mabi <1>: ARM Options. (line 9)
+* mabi <1>: x86 Options. (line 795)
* mabi <2>: RS/6000 and PowerPC Options.
- (line 636)
-* mabi <3>: x86 Options. (line 787)
-* mabi=32: MIPS Options. (line 154)
-* mabi=64: MIPS Options. (line 154)
-* mabi=eabi: MIPS Options. (line 154)
+ (line 638)
+* mabi <3>: ARM Options. (line 9)
+* mabi: AArch64 Options. (line 9)
+* mabi=32: MIPS Options. (line 157)
+* mabi=64: MIPS Options. (line 157)
+* mabi=eabi: MIPS Options. (line 157)
* mabi=elfv1: RS/6000 and PowerPC Options.
- (line 657)
+ (line 659)
* mabi=elfv2: RS/6000 and PowerPC Options.
- (line 663)
+ (line 665)
* mabi=gnu: MMIX Options. (line 20)
* mabi=ibmlongdouble: RS/6000 and PowerPC Options.
- (line 649)
+ (line 651)
* mabi=ieeelongdouble: RS/6000 and PowerPC Options.
- (line 653)
+ (line 655)
* mabi=mmixware: MMIX Options. (line 20)
-* mabi=n32: MIPS Options. (line 154)
+* mabi=n32: MIPS Options. (line 157)
* mabi=no-spe: RS/6000 and PowerPC Options.
- (line 646)
-* mabi=o64: MIPS Options. (line 154)
+ (line 648)
+* mabi=o64: MIPS Options. (line 157)
* mabi=spe: RS/6000 and PowerPC Options.
- (line 641)
-* mabicalls: MIPS Options. (line 190)
-* mabm: x86 Options. (line 605)
-* mabort-on-noreturn: ARM Options. (line 190)
-* mabs=2008: MIPS Options. (line 298)
-* mabs=legacy: MIPS Options. (line 298)
+ (line 643)
+* mabicalls: MIPS Options. (line 194)
+* mabm: x86 Options. (line 611)
+* mabort-on-noreturn: ARM Options. (line 191)
+* mabs=2008: MIPS Options. (line 302)
+* mabs=legacy: MIPS Options. (line 302)
* mabsdiff: MeP Options. (line 7)
* mabshi: PDP-11 Options. (line 55)
* mac0: PDP-11 Options. (line 16)
-* macc-4: FRV Options. (line 139)
-* macc-8: FRV Options. (line 143)
-* maccumulate-args: AVR Options. (line 148)
-* maccumulate-outgoing-args: SH Options. (line 394)
-* maccumulate-outgoing-args <1>: x86 Options. (line 810)
-* maddress-mode=long: x86 Options. (line 1001)
-* maddress-mode=short: x86 Options. (line 1006)
-* maddress-space-conversion: SPU Options. (line 68)
+* macc-4: FRV Options. (line 113)
+* macc-8: FRV Options. (line 116)
+* maccumulate-args: AVR Options. (line 147)
+* maccumulate-outgoing-args <1>: x86 Options. (line 818)
+* maccumulate-outgoing-args: SH Options. (line 400)
+* maddress-mode=long: x86 Options. (line 1012)
+* maddress-mode=short: x86 Options. (line 1017)
+* maddress-space-conversion: SPU Options. (line 63)
* mads: RS/6000 and PowerPC Options.
- (line 691)
-* maes: x86 Options. (line 591)
+ (line 693)
+* maes: x86 Options. (line 597)
* maix-struct-return: RS/6000 and PowerPC Options.
- (line 629)
+ (line 631)
* maix32: RS/6000 and PowerPC Options.
- (line 340)
+ (line 341)
* maix64: RS/6000 and PowerPC Options.
- (line 340)
+ (line 341)
* malign-300: H8/300 Options. (line 41)
-* malign-call: ARC Options. (line 192)
-* malign-data: x86 Options. (line 429)
-* malign-double: x86 Options. (line 374)
-* malign-int: M680x0 Options. (line 263)
-* malign-labels: FRV Options. (line 128)
+* malign-call: ARC Options. (line 194)
+* malign-data: x86 Options. (line 435)
+* malign-double: x86 Options. (line 380)
+* malign-int: M680x0 Options. (line 267)
+* malign-labels: FRV Options. (line 104)
* malign-loops: M32R/D Options. (line 73)
* malign-natural: RS/6000 and PowerPC Options.
- (line 378)
+ (line 380)
* malign-power: RS/6000 and PowerPC Options.
- (line 378)
+ (line 380)
* mall-opts: MeP Options. (line 11)
-* malloc-cc: FRV Options. (line 31)
+* malloc-cc: FRV Options. (line 25)
* maltivec: RS/6000 and PowerPC Options.
- (line 135)
+ (line 136)
* maltivec=be: RS/6000 and PowerPC Options.
- (line 151)
+ (line 152)
* maltivec=le: RS/6000 and PowerPC Options.
- (line 161)
+ (line 162)
* mam33: MN10300 Options. (line 17)
* mam33-2: MN10300 Options. (line 24)
* mam34: MN10300 Options. (line 27)
* mandroid: GNU/Linux Options. (line 21)
-* mannotate-align: ARC Options. (line 133)
+* mannotate-align: ARC Options. (line 135)
* mapcs: ARM Options. (line 21)
* mapcs-frame: ARM Options. (line 13)
-* mapp-regs: SPARC Options. (line 10)
* mapp-regs <1>: V850 Options. (line 181)
+* mapp-regs: SPARC Options. (line 10)
* mARC600: ARC Options. (line 19)
* mARC601: ARC Options. (line 23)
* mARC700: ARC Options. (line 26)
-* march: AArch64 Options. (line 73)
-* march <1>: ARM Options. (line 65)
-* march <2>: C6X Options. (line 7)
-* march <3>: CRIS Options. (line 10)
-* march <4>: HPPA Options. (line 9)
-* march <5>: HPPA Options. (line 155)
-* march <6>: M680x0 Options. (line 12)
-* march <7>: MIPS Options. (line 14)
-* march <8>: NDS32 Options. (line 52)
-* march <9>: S/390 and zSeries Options.
- (line 114)
-* march <10>: x86 Options. (line 9)
-* marclinux: ARC Options. (line 139)
-* marclinux_prof: ARC Options. (line 146)
-* margonaut: ARC Options. (line 341)
-* marm: ARM Options. (line 260)
+* march <1>: x86 Options. (line 9)
+* march <2>: S/390 and zSeries Options.
+ (line 116)
+* march <3>: NDS32 Options. (line 52)
+* march <4>: MIPS Options. (line 14)
+* march <5>: M680x0 Options. (line 12)
+* march <6>: HPPA Options. (line 9)
+* march <7>: CRIS Options. (line 10)
+* march <8>: C6X Options. (line 7)
+* march <9>: ARM Options. (line 65)
+* march: AArch64 Options. (line 79)
+* marclinux: ARC Options. (line 142)
+* marclinux_prof: ARC Options. (line 148)
+* margonaut: ARC Options. (line 346)
+* marm: ARM Options. (line 261)
* mas100-syntax: RX Options. (line 76)
* masm-hex: MSP430 Options. (line 9)
* masm-syntax-unified: ARM Options. (line 350)
-* masm=DIALECT: x86 Options. (line 328)
+* masm=DIALECT: x86 Options. (line 334)
* matomic-model=MODEL: SH Options. (line 214)
-* matomic-updates: SPU Options. (line 83)
-* mauto-modify-reg: ARC Options. (line 195)
+* matomic-updates: SPU Options. (line 78)
+* mauto-modify-reg: ARC Options. (line 197)
* mauto-pic: IA-64 Options. (line 50)
* maverage: MeP Options. (line 16)
* mavoid-indexed-addresses: RS/6000 and PowerPC Options.
- (line 448)
-* mavx: x86 Options. (line 584)
-* mavx256-split-unaligned-load: x86 Options. (line 939)
-* mavx256-split-unaligned-store: x86 Options. (line 939)
+ (line 450)
+* mavx: x86 Options. (line 590)
+* mavx256-split-unaligned-load: x86 Options. (line 948)
+* mavx256-split-unaligned-store: x86 Options. (line 948)
* max-vect-align: Adapteva Epiphany Options.
- (line 119)
+ (line 120)
* mb: SH Options. (line 147)
* mbackchain: S/390 and zSeries Options.
(line 35)
* mbarrel-shift-enabled: LM32 Options. (line 9)
* mbarrel-shifter: ARC Options. (line 10)
-* mbarrel_shifter: ARC Options. (line 361)
-* mbase-addresses: MMIX Options. (line 53)
+* mbarrel_shifter: ARC Options. (line 363)
+* mbase-addresses: MMIX Options. (line 54)
* mbased=: MeP Options. (line 20)
-* mbbit-peephole: ARC Options. (line 198)
+* mbbit-peephole: ARC Options. (line 200)
* mbcopy: PDP-11 Options. (line 36)
* mbcopy-builtin: PDP-11 Options. (line 32)
* mbig: RS/6000 and PowerPC Options.
- (line 528)
-* mbig-endian: AArch64 Options. (line 20)
-* mbig-endian <1>: ARC Options. (line 344)
-* mbig-endian <2>: ARM Options. (line 61)
-* mbig-endian <3>: C6X Options. (line 13)
-* mbig-endian <4>: IA-64 Options. (line 9)
+ (line 530)
+* mbig-endian <1>: TILE-Gx Options. (line 29)
+* mbig-endian <2>: RS/6000 and PowerPC Options.
+ (line 530)
+* mbig-endian <3>: NDS32 Options. (line 9)
+* mbig-endian <4>: MicroBlaze Options. (line 57)
* mbig-endian <5>: MCore Options. (line 39)
-* mbig-endian <6>: MicroBlaze Options. (line 57)
-* mbig-endian <7>: NDS32 Options. (line 9)
-* mbig-endian <8>: RS/6000 and PowerPC Options.
- (line 528)
-* mbig-endian <9>: TILE-Gx Options. (line 29)
+* mbig-endian <6>: IA-64 Options. (line 9)
+* mbig-endian <7>: C6X Options. (line 13)
+* mbig-endian <8>: ARM Options. (line 61)
+* mbig-endian <9>: ARC Options. (line 349)
+* mbig-endian: AArch64 Options. (line 20)
* mbig-endian-data: RX Options. (line 42)
* mbig-switch: V850 Options. (line 176)
* mbigtable: SH Options. (line 162)
* mbionic: GNU/Linux Options. (line 17)
* mbit-align: RS/6000 and PowerPC Options.
- (line 480)
+ (line 482)
* mbit-ops: CR16 Options. (line 25)
-* mbitfield: M680x0 Options. (line 231)
-* mbitops: MeP Options. (line 26)
+* mbitfield: M680x0 Options. (line 235)
* mbitops <1>: SH Options. (line 166)
+* mbitops: MeP Options. (line 26)
* mblock-move-inline-limit: RS/6000 and PowerPC Options.
- (line 761)
-* mbmi: x86 Options. (line 606)
+ (line 764)
+* mbmi: x86 Options. (line 612)
* mbranch-cheap: PDP-11 Options. (line 65)
+* mbranch-cost <1>: MIPS Options. (line 757)
+* mbranch-cost <2>: AVR Options. (line 162)
* mbranch-cost: Adapteva Epiphany Options.
(line 18)
-* mbranch-cost <1>: AVR Options. (line 163)
-* mbranch-cost <2>: MIPS Options. (line 744)
-* mbranch-cost=NUM: SH Options. (line 458)
+* mbranch-cost=NUM: SH Options. (line 466)
* mbranch-cost=NUMBER: M32R/D Options. (line 82)
* mbranch-expensive: PDP-11 Options. (line 61)
-* mbranch-hints: SPU Options. (line 29)
-* mbranch-likely: MIPS Options. (line 751)
-* mbranch-predict: MMIX Options. (line 48)
+* mbranch-hints: SPU Options. (line 27)
+* mbranch-likely: MIPS Options. (line 764)
+* mbranch-predict: MMIX Options. (line 49)
* mbss-plt: RS/6000 and PowerPC Options.
- (line 188)
+ (line 189)
* mbuild-constants: DEC Alpha Options. (line 141)
* mbwx: DEC Alpha Options. (line 163)
-* mbypass-cache: Nios II Options. (line 70)
-* mc68000: M680x0 Options. (line 93)
-* mc68020: M680x0 Options. (line 107)
+* mbypass-cache: Nios II Options. (line 72)
+* mc68000: M680x0 Options. (line 95)
+* mc68020: M680x0 Options. (line 109)
* mc=: MeP Options. (line 31)
* mcache-block-size: NDS32 Options. (line 48)
-* mcache-size: SPU Options. (line 75)
-* mcache-volatile: Nios II Options. (line 76)
+* mcache-size: SPU Options. (line 70)
+* mcache-volatile: Nios II Options. (line 78)
* mcall-eabi: RS/6000 and PowerPC Options.
- (line 603)
+ (line 605)
* mcall-freebsd: RS/6000 and PowerPC Options.
- (line 617)
+ (line 619)
* mcall-linux: RS/6000 and PowerPC Options.
- (line 613)
+ (line 615)
* mcall-netbsd: RS/6000 and PowerPC Options.
- (line 621)
-* mcall-netbsd <1>: RS/6000 and PowerPC Options.
- (line 625)
-* mcall-prologues: AVR Options. (line 168)
+ (line 623)
+* mcall-prologues: AVR Options. (line 167)
* mcall-sysv: RS/6000 and PowerPC Options.
- (line 595)
+ (line 597)
* mcall-sysv-eabi: RS/6000 and PowerPC Options.
- (line 603)
+ (line 605)
* mcall-sysv-noeabi: RS/6000 and PowerPC Options.
- (line 606)
+ (line 608)
* mcallee-super-interworking: ARM Options. (line 279)
* mcaller-super-interworking: ARM Options. (line 286)
* mcallgraph-data: MCore Options. (line 31)
-* mcase-vector-pcrel: ARC Options. (line 206)
-* mcbcond: SPARC Options. (line 223)
-* mcbranch-force-delay-slot: SH Options. (line 473)
-* mcc-init: CRIS Options. (line 42)
-* mcfv4e: M680x0 Options. (line 169)
-* mcheck-zero-division: MIPS Options. (line 546)
+* mcase-vector-pcrel: ARC Options. (line 208)
+* mcbcond: SPARC Options. (line 224)
+* mcbranch-force-delay-slot: SH Options. (line 481)
+* mcc-init: CRIS Options. (line 41)
+* mcfv4e: M680x0 Options. (line 172)
+* mcheck-zero-division: MIPS Options. (line 551)
* mcix: DEC Alpha Options. (line 163)
-* mcld: x86 Options. (line 660)
+* mcld: x86 Options. (line 668)
* mclear-hwcap: Solaris 2 Options. (line 9)
-* mclfushopt: x86 Options. (line 593)
+* mclfushopt: x86 Options. (line 599)
* mclip: MeP Options. (line 35)
+* mcmodel <1>: SPARC Options. (line 262)
* mcmodel: NDS32 Options. (line 55)
-* mcmodel <1>: SPARC Options. (line 261)
-* mcmodel=kernel: x86 Options. (line 985)
-* mcmodel=large: AArch64 Options. (line 44)
-* mcmodel=large <1>: RS/6000 and PowerPC Options.
- (line 129)
+* mcmodel=kernel: x86 Options. (line 996)
+* mcmodel=large <1>: x86 Options. (line 1008)
* mcmodel=large <2>: TILE-Gx Options. (line 14)
-* mcmodel=large <3>: x86 Options. (line 997)
+* mcmodel=large <3>: RS/6000 and PowerPC Options.
+ (line 130)
+* mcmodel=large: AArch64 Options. (line 44)
+* mcmodel=medium <1>: x86 Options. (line 1001)
* mcmodel=medium: RS/6000 and PowerPC Options.
- (line 125)
-* mcmodel=medium <1>: x86 Options. (line 990)
-* mcmodel=small: AArch64 Options. (line 38)
-* mcmodel=small <1>: RS/6000 and PowerPC Options.
- (line 121)
+ (line 126)
+* mcmodel=small <1>: x86 Options. (line 990)
* mcmodel=small <2>: TILE-Gx Options. (line 9)
-* mcmodel=small <3>: x86 Options. (line 979)
+* mcmodel=small <3>: RS/6000 and PowerPC Options.
+ (line 122)
+* mcmodel=small: AArch64 Options. (line 38)
* mcmodel=tiny: AArch64 Options. (line 31)
* mcmov: NDS32 Options. (line 21)
* mcmove: Adapteva Epiphany Options.
(line 23)
* mcmpb: RS/6000 and PowerPC Options.
(line 27)
-* mcode-readable: MIPS Options. (line 506)
-* mcompact-casesi: ARC Options. (line 210)
+* mcode-readable: MIPS Options. (line 511)
+* mcompact-casesi: ARC Options. (line 212)
* mcompat-align-parm: RS/6000 and PowerPC Options.
- (line 939)
-* mcond-exec: FRV Options. (line 187)
-* mcond-move: FRV Options. (line 159)
+ (line 944)
+* mcond-exec: FRV Options. (line 152)
+* mcond-move: FRV Options. (line 128)
* mconfig=: MeP Options. (line 39)
* mconsole: x86 Windows Options.
(line 9)
@@ -49270,671 +49741,674 @@ look up both forms.
* mcop: MeP Options. (line 48)
* mcop32: MeP Options. (line 53)
* mcop64: MeP Options. (line 56)
-* mcorea: Blackfin Options. (line 156)
-* mcoreb: Blackfin Options. (line 163)
-* mcpu: AArch64 Options. (line 106)
-* mcpu <1>: ARC Options. (line 14)
-* mcpu <2>: ARM Options. (line 130)
-* mcpu <3>: CRIS Options. (line 10)
-* mcpu <4>: DEC Alpha Options. (line 215)
-* mcpu <5>: FRV Options. (line 258)
-* mcpu <6>: M680x0 Options. (line 28)
-* mcpu <7>: picoChip Options. (line 9)
-* mcpu <8>: RS/6000 and PowerPC Options.
- (line 68)
-* mcpu <9>: RX Options. (line 30)
-* mcpu <10>: SPARC Options. (line 101)
-* mcpu <11>: TILE-Gx Options. (line 18)
-* mcpu <12>: TILEPro Options. (line 9)
-* mcpu <13>: Visium Options. (line 33)
-* mcpu <14>: x86 Options. (line 276)
-* mcpu32: M680x0 Options. (line 135)
-* mcpu=: Blackfin Options. (line 7)
-* mcpu= <1>: M32C Options. (line 7)
+* mcorea: Blackfin Options. (line 157)
+* mcoreb: Blackfin Options. (line 164)
+* mcpu <1>: x86 Options. (line 282)
+* mcpu <2>: Visium Options. (line 33)
+* mcpu <3>: TILEPro Options. (line 9)
+* mcpu <4>: TILE-Gx Options. (line 18)
+* mcpu <5>: SPARC Options. (line 102)
+* mcpu <6>: RX Options. (line 30)
+* mcpu <7>: RS/6000 and PowerPC Options.
+ (line 69)
+* mcpu <8>: picoChip Options. (line 9)
+* mcpu <9>: M680x0 Options. (line 28)
+* mcpu <10>: FRV Options. (line 212)
+* mcpu <11>: DEC Alpha Options. (line 215)
+* mcpu <12>: CRIS Options. (line 10)
+* mcpu <13>: ARM Options. (line 130)
+* mcpu <14>: ARC Options. (line 14)
+* mcpu: AArch64 Options. (line 112)
+* mcpu32: M680x0 Options. (line 138)
+* mcpu= <1>: MSP430 Options. (line 34)
* mcpu= <2>: MicroBlaze Options. (line 20)
-* mcpu= <3>: MSP430 Options. (line 34)
+* mcpu= <3>: M32C Options. (line 7)
+* mcpu=: Blackfin Options. (line 7)
* mcr16c: CR16 Options. (line 14)
* mcr16cplus: CR16 Options. (line 14)
-* mcrc32: x86 Options. (line 707)
+* mcrc32: x86 Options. (line 715)
* mcrypto: RS/6000 and PowerPC Options.
- (line 223)
-* mcsync-anomaly: Blackfin Options. (line 59)
-* mctor-dtor: NDS32 Options. (line 69)
-* mcustom-fpu-cfg: Nios II Options. (line 217)
-* mcustom-INSN: Nios II Options. (line 97)
-* mcx16: x86 Options. (line 684)
+ (line 224)
+* mcsync-anomaly: Blackfin Options. (line 60)
+* mctor-dtor: NDS32 Options. (line 71)
+* mcustom-fpu-cfg: Nios II Options. (line 220)
+* mcustom-INSN: Nios II Options. (line 99)
+* mcx16: x86 Options. (line 692)
* MD: Preprocessor Options.
- (line 276)
+ (line 274)
* mdalign: SH Options. (line 153)
* mdata-align: CRIS Options. (line 55)
* mdata-model: CR16 Options. (line 28)
* mdc: MeP Options. (line 62)
+* mdebug <1>: Visium Options. (line 7)
+* mdebug <2>: S/390 and zSeries Options.
+ (line 112)
* mdebug: M32R/D Options. (line 69)
-* mdebug <1>: S/390 and zSeries Options.
- (line 110)
-* mdebug <2>: Visium Options. (line 7)
* mdebug-main=PREFIX: VMS Options. (line 13)
* mdec-asm: PDP-11 Options. (line 72)
* mdirect-move: RS/6000 and PowerPC Options.
- (line 229)
+ (line 230)
* mdisable-callt: V850 Options. (line 92)
* mdisable-fpregs: HPPA Options. (line 27)
* mdisable-indexing: HPPA Options. (line 33)
-* mdiv: M680x0 Options. (line 206)
-* mdiv <1>: MCore Options. (line 15)
-* mdiv <2>: MeP Options. (line 65)
-* mdiv=STRATEGY: SH Options. (line 305)
-* mdivide-breaks: MIPS Options. (line 552)
+* mdiv <1>: MeP Options. (line 65)
+* mdiv <2>: MCore Options. (line 15)
+* mdiv: M680x0 Options. (line 209)
+* mdiv=STRATEGY: SH Options. (line 308)
+* mdivide-breaks: MIPS Options. (line 557)
* mdivide-enabled: LM32 Options. (line 12)
-* mdivide-traps: MIPS Options. (line 552)
-* mdivsi3_libfunc=NAME: SH Options. (line 400)
+* mdivide-traps: MIPS Options. (line 557)
+* mdivsi3_libfunc=NAME: SH Options. (line 406)
* mdll: x86 Windows Options.
(line 16)
* mdlmzb: RS/6000 and PowerPC Options.
- (line 473)
-* mdmx: MIPS Options. (line 374)
-* mdouble: FRV Options. (line 48)
-* mdouble-float: MIPS Options. (line 286)
+ (line 475)
+* mdmx: MIPS Options. (line 378)
+* mdouble: FRV Options. (line 38)
* mdouble-float <1>: RS/6000 and PowerPC Options.
- (line 396)
+ (line 398)
+* mdouble-float: MIPS Options. (line 290)
* mdpfp: ARC Options. (line 30)
* mdpfp-compact: ARC Options. (line 31)
* mdpfp-fast: ARC Options. (line 35)
-* mdpfp_compact: ARC Options. (line 364)
-* mdpfp_fast: ARC Options. (line 367)
-* mdsp: MIPS Options. (line 351)
-* mdsp-packa: ARC Options. (line 88)
-* mdspr2: MIPS Options. (line 357)
-* mdsp_packa: ARC Options. (line 370)
-* mdual-nops: SPU Options. (line 95)
-* mdump-tune-features: x86 Options. (line 642)
-* mdvbf: ARC Options. (line 92)
+* mdpfp_compact: ARC Options. (line 366)
+* mdpfp_fast: ARC Options. (line 369)
+* mdsp: MIPS Options. (line 355)
+* mdsp-packa: ARC Options. (line 89)
+* mdsp_packa: ARC Options. (line 372)
+* mdspr2: MIPS Options. (line 361)
+* mdual-nops: SPU Options. (line 90)
+* mdump-tune-features: x86 Options. (line 649)
+* mdvbf: ARC Options. (line 93)
* mdwarf2-asm: IA-64 Options. (line 94)
-* mdword: FRV Options. (line 40)
+* mdword: FRV Options. (line 32)
* mdynamic-no-pic: RS/6000 and PowerPC Options.
- (line 533)
+ (line 535)
+* mEA: ARC Options. (line 375)
* mea: ARC Options. (line 43)
-* mEA: ARC Options. (line 373)
-* mea32: SPU Options. (line 60)
-* mea64: SPU Options. (line 60)
+* mea32: SPU Options. (line 55)
+* mea64: SPU Options. (line 55)
* meabi: RS/6000 and PowerPC Options.
- (line 710)
-* mearly-cbranchsi: ARC Options. (line 229)
+ (line 712)
+* mearly-cbranchsi: ARC Options. (line 231)
* mearly-stop-bits: IA-64 Options. (line 100)
+* meb <1>: Score Options. (line 9)
+* meb <2>: Nios II Options. (line 67)
+* meb <3>: Moxie Options. (line 7)
* meb: MeP Options. (line 68)
-* meb <1>: Moxie Options. (line 7)
-* meb <2>: Nios II Options. (line 65)
-* meb <3>: Score Options. (line 9)
+* mel <1>: Score Options. (line 12)
+* mel <2>: Nios II Options. (line 67)
+* mel <3>: Moxie Options. (line 11)
* mel: MeP Options. (line 71)
-* mel <1>: Moxie Options. (line 11)
-* mel <2>: Nios II Options. (line 65)
-* mel <3>: Score Options. (line 12)
+* melf <1>: MMIX Options. (line 44)
* melf: CRIS Options. (line 87)
-* melf <1>: MMIX Options. (line 43)
* memb: RS/6000 and PowerPC Options.
- (line 705)
-* membedded-data: MIPS Options. (line 493)
+ (line 707)
+* membedded-data: MIPS Options. (line 498)
* memregs=: M32C Options. (line 21)
* mep: V850 Options. (line 16)
-* mepilogue-cfi: ARC Options. (line 155)
+* mepilogue-cfi: ARC Options. (line 157)
* mepsilon: MMIX Options. (line 15)
* merror-reloc: SPU Options. (line 10)
* mesa: S/390 and zSeries Options.
- (line 94)
-* metrax100: CRIS Options. (line 27)
-* metrax4: CRIS Options. (line 27)
-* meva: MIPS Options. (line 401)
-* mexpand-adddi: ARC Options. (line 232)
+ (line 95)
+* metrax100: CRIS Options. (line 26)
+* metrax4: CRIS Options. (line 26)
+* meva: MIPS Options. (line 405)
+* mexpand-adddi: ARC Options. (line 234)
+* mexplicit-relocs <1>: MIPS Options. (line 542)
* mexplicit-relocs: DEC Alpha Options. (line 176)
-* mexplicit-relocs <1>: MIPS Options. (line 537)
* mexr: H8/300 Options. (line 28)
-* mextern-sdata: MIPS Options. (line 456)
+* mextern-sdata: MIPS Options. (line 460)
* MF: Preprocessor Options.
(line 220)
-* mf16c: x86 Options. (line 596)
-* mfast-fp: Blackfin Options. (line 132)
+* mf16c: x86 Options. (line 602)
+* mfast-fp: Blackfin Options. (line 133)
* mfast-indirect-calls: HPPA Options. (line 45)
-* mfast-sw-div: Nios II Options. (line 82)
-* mfaster-structs: SPARC Options. (line 91)
-* mfdpic: FRV Options. (line 72)
-* mfentry: x86 Options. (line 898)
+* mfast-sw-div: Nios II Options. (line 84)
+* mfaster-structs: SPARC Options. (line 92)
+* mfdpic: FRV Options. (line 56)
+* mfentry: x86 Options. (line 907)
* mfix: DEC Alpha Options. (line 163)
-* mfix-24k: MIPS Options. (line 610)
+* mfix-24k: MIPS Options. (line 617)
* mfix-and-continue: Darwin Options. (line 104)
-* mfix-at697f: SPARC Options. (line 243)
+* mfix-at697f: SPARC Options. (line 244)
* mfix-cortex-a53-835769: AArch64 Options. (line 67)
+* mfix-cortex-a53-843419: AArch64 Options. (line 74)
* mfix-cortex-m3-ldrd: ARM Options. (line 319)
-* mfix-r10000: MIPS Options. (line 632)
-* mfix-r4000: MIPS Options. (line 616)
-* mfix-r4400: MIPS Options. (line 626)
-* mfix-rm7000: MIPS Options. (line 643)
-* mfix-sb1: MIPS Options. (line 668)
-* mfix-ut699: SPARC Options. (line 248)
-* mfix-vr4120: MIPS Options. (line 648)
-* mfix-vr4130: MIPS Options. (line 661)
-* mfixed-cc: FRV Options. (line 35)
+* mfix-r10000: MIPS Options. (line 644)
+* mfix-r4000: MIPS Options. (line 623)
+* mfix-r4400: MIPS Options. (line 637)
+* mfix-rm7000: MIPS Options. (line 655)
+* mfix-sb1: MIPS Options. (line 681)
+* mfix-ut699: SPARC Options. (line 249)
+* mfix-vr4120: MIPS Options. (line 660)
+* mfix-vr4130: MIPS Options. (line 674)
+* mfixed-cc: FRV Options. (line 28)
+* mfixed-range <1>: SPU Options. (line 47)
+* mfixed-range <2>: SH Options. (line 413)
+* mfixed-range <3>: IA-64 Options. (line 105)
* mfixed-range: HPPA Options. (line 52)
-* mfixed-range <1>: IA-64 Options. (line 105)
-* mfixed-range <2>: SH Options. (line 407)
-* mfixed-range <3>: SPU Options. (line 52)
* mflat: SPARC Options. (line 22)
-* mflip-mips16: MIPS Options. (line 126)
+* mflip-mips16: MIPS Options. (line 128)
* mfloat-abi: ARM Options. (line 41)
* mfloat-gprs: RS/6000 and PowerPC Options.
- (line 285)
+ (line 286)
* mfloat-ieee: DEC Alpha Options. (line 171)
* mfloat-vax: DEC Alpha Options. (line 171)
* mfloat32: PDP-11 Options. (line 52)
* mfloat64: PDP-11 Options. (line 48)
-* mflush-func: MIPS Options. (line 735)
+* mflush-func: MIPS Options. (line 748)
* mflush-func=NAME: M32R/D Options. (line 93)
* mflush-trap=NUMBER: M32R/D Options. (line 86)
-* mfma: x86 Options. (line 597)
-* mfmaf: SPARC Options. (line 237)
+* mfma: x86 Options. (line 603)
+* mfmaf: SPARC Options. (line 238)
* mfmovd: SH Options. (line 169)
* mforce-no-pic: Xtensa Options. (line 41)
-* mfp-exceptions: MIPS Options. (line 762)
+* mfp-exceptions: MIPS Options. (line 775)
* mfp-mode: Adapteva Epiphany Options.
- (line 71)
+ (line 72)
* mfp-reg: DEC Alpha Options. (line 25)
* mfp-rounding-mode: DEC Alpha Options. (line 85)
* mfp-trap-mode: DEC Alpha Options. (line 63)
-* mfp16-format: ARM Options. (line 170)
-* mfp32: MIPS Options. (line 256)
-* mfp64: MIPS Options. (line 259)
-* mfpmath: Optimize Options. (line 2062)
-* mfpmath <1>: x86 Options. (line 279)
-* mfpr-32: FRV Options. (line 15)
-* mfpr-64: FRV Options. (line 19)
+* mfp16-format: ARM Options. (line 171)
+* mfp32: MIPS Options. (line 260)
+* mfp64: MIPS Options. (line 263)
+* mfpmath <1>: x86 Options. (line 285)
+* mfpmath: Optimize Options. (line 2068)
+* mfpr-32: FRV Options. (line 13)
+* mfpr-64: FRV Options. (line 16)
* mfprnd: RS/6000 and PowerPC Options.
(line 27)
+* mfpu <1>: Visium Options. (line 19)
+* mfpu <2>: SPARC Options. (line 35)
+* mfpu <3>: RS/6000 and PowerPC Options.
+ (line 406)
+* mfpu <4>: PDP-11 Options. (line 9)
* mfpu: ARM Options. (line 150)
-* mfpu <1>: PDP-11 Options. (line 9)
-* mfpu <2>: RS/6000 and PowerPC Options.
- (line 404)
-* mfpu <3>: SPARC Options. (line 34)
-* mfpu <4>: Visium Options. (line 19)
-* mfpxx: MIPS Options. (line 262)
+* mfpxx: MIPS Options. (line 266)
* mfriz: RS/6000 and PowerPC Options.
- (line 910)
-* mfsca: SH Options. (line 489)
-* mfsgsbase: x86 Options. (line 594)
-* mfsrra: SH Options. (line 498)
+ (line 915)
+* mfsca: SH Options. (line 497)
+* mfsgsbase: x86 Options. (line 600)
+* mfsrra: SH Options. (line 506)
* mfull-regs: NDS32 Options. (line 18)
* mfull-toc: RS/6000 and PowerPC Options.
- (line 313)
-* mfused-madd: IA-64 Options. (line 88)
-* mfused-madd <1>: MIPS Options. (line 593)
-* mfused-madd <2>: RS/6000 and PowerPC Options.
- (line 457)
+ (line 314)
+* mfused-madd <1>: Xtensa Options. (line 19)
+* mfused-madd <2>: SH Options. (line 488)
* mfused-madd <3>: S/390 and zSeries Options.
- (line 135)
-* mfused-madd <4>: SH Options. (line 480)
-* mfused-madd <5>: Xtensa Options. (line 19)
-* mfxsr: x86 Options. (line 609)
+ (line 137)
+* mfused-madd <4>: RS/6000 and PowerPC Options.
+ (line 459)
+* mfused-madd <5>: MIPS Options. (line 599)
+* mfused-madd: IA-64 Options. (line 88)
+* mfxsr: x86 Options. (line 615)
+* mg: VAX Options. (line 17)
* MG: Preprocessor Options.
(line 229)
-* mg: VAX Options. (line 17)
* mgas: HPPA Options. (line 68)
* mgcc-abi: V850 Options. (line 148)
* mgen-cell-microcode: RS/6000 and PowerPC Options.
- (line 176)
+ (line 177)
* mgeneral-regs-only: AArch64 Options. (line 24)
-* mgettrcost=NUMBER: SH Options. (line 424)
+* mgettrcost=NUMBER: SH Options. (line 430)
* mghs: V850 Options. (line 127)
* mglibc: GNU/Linux Options. (line 9)
* mgnu: VAX Options. (line 13)
* mgnu-as: IA-64 Options. (line 18)
-* mgnu-ld: HPPA Options. (line 104)
* mgnu-ld <1>: IA-64 Options. (line 23)
+* mgnu-ld: HPPA Options. (line 104)
* mgotplt: CRIS Options. (line 81)
-* mgp32: MIPS Options. (line 250)
-* mgp64: MIPS Options. (line 253)
-* mgpopt: MIPS Options. (line 478)
-* mgpopt <1>: Nios II Options. (line 16)
+* mgp32: MIPS Options. (line 254)
+* mgp64: MIPS Options. (line 257)
+* mgpopt <1>: Nios II Options. (line 17)
+* mgpopt: MIPS Options. (line 483)
* mgpr-32: FRV Options. (line 7)
-* mgpr-64: FRV Options. (line 11)
-* mgprel-ro: FRV Options. (line 99)
+* mgpr-64: FRV Options. (line 10)
+* mgprel-ro: FRV Options. (line 79)
* mh: H8/300 Options. (line 14)
-* mhal: Nios II Options. (line 262)
+* mhal: Nios II Options. (line 266)
* mhalf-reg-file: Adapteva Epiphany Options.
(line 9)
-* mhard-dfp: RS/6000 and PowerPC Options.
- (line 27)
* mhard-dfp <1>: S/390 and zSeries Options.
(line 20)
-* mhard-float: FRV Options. (line 23)
-* mhard-float <1>: M680x0 Options. (line 194)
-* mhard-float <2>: MicroBlaze Options. (line 10)
-* mhard-float <3>: MIPS Options. (line 265)
-* mhard-float <4>: RS/6000 and PowerPC Options.
- (line 390)
-* mhard-float <5>: S/390 and zSeries Options.
+* mhard-dfp: RS/6000 and PowerPC Options.
+ (line 27)
+* mhard-float <1>: Visium Options. (line 19)
+* mhard-float <2>: V850 Options. (line 113)
+* mhard-float <3>: SPARC Options. (line 35)
+* mhard-float <4>: S/390 and zSeries Options.
(line 11)
-* mhard-float <6>: SPARC Options. (line 34)
-* mhard-float <7>: V850 Options. (line 113)
-* mhard-float <8>: Visium Options. (line 19)
-* mhard-quad-float: SPARC Options. (line 55)
+* mhard-float <5>: RS/6000 and PowerPC Options.
+ (line 392)
+* mhard-float <6>: MIPS Options. (line 269)
+* mhard-float <7>: MicroBlaze Options. (line 10)
+* mhard-float <8>: M680x0 Options. (line 197)
+* mhard-float: FRV Options. (line 19)
+* mhard-quad-float: SPARC Options. (line 56)
* mhardlit: MCore Options. (line 10)
-* mhint-max-distance: SPU Options. (line 107)
-* mhint-max-nops: SPU Options. (line 101)
+* mhint-max-distance: SPU Options. (line 102)
+* mhint-max-nops: SPU Options. (line 96)
* mhotpatch: S/390 and zSeries Options.
- (line 170)
+ (line 173)
* mhp-ld: HPPA Options. (line 116)
-* mhw-div: Nios II Options. (line 91)
-* mhw-mul: Nios II Options. (line 91)
-* mhw-mulx: Nios II Options. (line 91)
+* mhw-div: Nios II Options. (line 93)
+* mhw-mul: Nios II Options. (line 93)
+* mhw-mulx: Nios II Options. (line 93)
* mhwmult=: MSP430 Options. (line 55)
-* micplb: Blackfin Options. (line 177)
-* mid-shared-library: Blackfin Options. (line 80)
-* mieee: DEC Alpha Options. (line 39)
+* micplb: Blackfin Options. (line 178)
+* mid-shared-library: Blackfin Options. (line 81)
* mieee <1>: SH Options. (line 186)
+* mieee: DEC Alpha Options. (line 39)
* mieee-conformant: DEC Alpha Options. (line 134)
-* mieee-fp: x86 Options. (line 336)
+* mieee-fp: x86 Options. (line 342)
* mieee-with-inexact: DEC Alpha Options. (line 52)
* milp32: IA-64 Options. (line 121)
-* mimadd: MIPS Options. (line 586)
-* mimpure-text: Solaris 2 Options. (line 15)
-* mincoming-stack-boundary: x86 Options. (line 550)
-* mindexed-addressing: SH Options. (line 414)
-* mindexed-loads: ARC Options. (line 236)
-* minline-all-stringops: x86 Options. (line 830)
+* mimadd: MIPS Options. (line 592)
+* mimpure-text: Solaris 2 Options. (line 16)
+* mincoming-stack-boundary: x86 Options. (line 556)
+* mindexed-addressing: SH Options. (line 420)
+* mindexed-loads: ARC Options. (line 238)
+* minline-all-stringops: x86 Options. (line 839)
* minline-float-divide-max-throughput: IA-64 Options. (line 58)
* minline-float-divide-min-latency: IA-64 Options. (line 54)
* minline-ic_invalidate: SH Options. (line 195)
* minline-int-divide-max-throughput: IA-64 Options. (line 69)
* minline-int-divide-min-latency: IA-64 Options. (line 65)
-* minline-plt: Blackfin Options. (line 137)
-* minline-plt <1>: FRV Options. (line 81)
+* minline-plt <1>: FRV Options. (line 64)
+* minline-plt: Blackfin Options. (line 138)
* minline-sqrt-max-throughput: IA-64 Options. (line 80)
* minline-sqrt-min-latency: IA-64 Options. (line 76)
-* minline-stringops-dynamically: x86 Options. (line 837)
-* minrt: MSP430 Options. (line 76)
+* minline-stringops-dynamically: x86 Options. (line 846)
+* minrt: MSP430 Options. (line 77)
* minsert-sched-nops: RS/6000 and PowerPC Options.
- (line 573)
+ (line 575)
* mint-register: RX Options. (line 100)
* mint16: PDP-11 Options. (line 40)
+* mint32 <1>: PDP-11 Options. (line 44)
+* mint32 <2>: H8/300 Options. (line 38)
* mint32: CR16 Options. (line 22)
-* mint32 <1>: H8/300 Options. (line 38)
-* mint32 <2>: PDP-11 Options. (line 44)
-* mint8: AVR Options. (line 172)
-* minterlink-compressed: MIPS Options. (line 133)
-* minterlink-mips16: MIPS Options. (line 145)
-* minvalid-symbols: SH Options. (line 448)
+* mint8: AVR Options. (line 171)
+* minterlink-compressed: MIPS Options. (line 136)
+* minterlink-mips16: MIPS Options. (line 148)
+* minvalid-symbols: SH Options. (line 456)
* mio-volatile: MeP Options. (line 74)
-* mips1: MIPS Options. (line 78)
-* mips16: MIPS Options. (line 118)
-* mips2: MIPS Options. (line 81)
-* mips3: MIPS Options. (line 84)
-* mips32: MIPS Options. (line 90)
-* mips32r3: MIPS Options. (line 93)
-* mips32r5: MIPS Options. (line 96)
-* mips32r6: MIPS Options. (line 99)
-* mips3d: MIPS Options. (line 380)
-* mips4: MIPS Options. (line 87)
-* mips64: MIPS Options. (line 102)
-* mips64r2: MIPS Options. (line 105)
-* mips64r3: MIPS Options. (line 108)
-* mips64r5: MIPS Options. (line 111)
-* mips64r6: MIPS Options. (line 114)
+* mips1: MIPS Options. (line 80)
+* mips16: MIPS Options. (line 120)
+* mips2: MIPS Options. (line 83)
+* mips3: MIPS Options. (line 86)
+* mips32: MIPS Options. (line 92)
+* mips32r3: MIPS Options. (line 95)
+* mips32r5: MIPS Options. (line 98)
+* mips32r6: MIPS Options. (line 101)
+* mips3d: MIPS Options. (line 384)
+* mips4: MIPS Options. (line 89)
+* mips64: MIPS Options. (line 104)
+* mips64r2: MIPS Options. (line 107)
+* mips64r3: MIPS Options. (line 110)
+* mips64r5: MIPS Options. (line 113)
+* mips64r6: MIPS Options. (line 116)
* misel: RS/6000 and PowerPC Options.
- (line 194)
-* misize: ARC Options. (line 130)
+ (line 195)
* misize <1>: SH Options. (line 207)
+* misize: ARC Options. (line 132)
* misr-vector-size: NDS32 Options. (line 45)
* missue-rate=NUMBER: M32R/D Options. (line 79)
* mivc2: MeP Options. (line 59)
* mjump-in-delay: HPPA Options. (line 23)
* mkernel: Darwin Options. (line 82)
-* mknuthdiv: MMIX Options. (line 32)
-* ml: MeP Options. (line 78)
+* mknuthdiv: MMIX Options. (line 33)
* ml <1>: SH Options. (line 150)
+* ml: MeP Options. (line 78)
* mlarge: MSP430 Options. (line 44)
* mlarge-data: DEC Alpha Options. (line 187)
-* mlarge-data-threshold: x86 Options. (line 436)
-* mlarge-mem: SPU Options. (line 38)
+* mlarge-data-threshold: x86 Options. (line 442)
+* mlarge-mem: SPU Options. (line 35)
* mlarge-text: DEC Alpha Options. (line 205)
* mleadz: MeP Options. (line 81)
-* mleaf-id-shared-library: Blackfin Options. (line 91)
+* mleaf-id-shared-library: Blackfin Options. (line 92)
* mlibfuncs: MMIX Options. (line 10)
-* mlibrary-pic: FRV Options. (line 135)
-* mlinked-fp: FRV Options. (line 116)
+* mlibrary-pic: FRV Options. (line 110)
+* mlinked-fp: FRV Options. (line 94)
* mlinker-opt: HPPA Options. (line 78)
* mlinux: CRIS Options. (line 91)
* mlittle: RS/6000 and PowerPC Options.
- (line 522)
-* mlittle-endian: AArch64 Options. (line 27)
-* mlittle-endian <1>: ARC Options. (line 353)
-* mlittle-endian <2>: ARM Options. (line 57)
-* mlittle-endian <3>: C6X Options. (line 16)
-* mlittle-endian <4>: IA-64 Options. (line 13)
+ (line 524)
+* mlittle-endian <1>: TILE-Gx Options. (line 29)
+* mlittle-endian <2>: RS/6000 and PowerPC Options.
+ (line 524)
+* mlittle-endian <3>: NDS32 Options. (line 12)
+* mlittle-endian <4>: MicroBlaze Options. (line 60)
* mlittle-endian <5>: MCore Options. (line 39)
-* mlittle-endian <6>: MicroBlaze Options. (line 60)
-* mlittle-endian <7>: NDS32 Options. (line 12)
-* mlittle-endian <8>: RS/6000 and PowerPC Options.
- (line 522)
-* mlittle-endian <9>: TILE-Gx Options. (line 29)
+* mlittle-endian <6>: IA-64 Options. (line 13)
+* mlittle-endian <7>: C6X Options. (line 16)
+* mlittle-endian <8>: ARM Options. (line 57)
+* mlittle-endian <9>: ARC Options. (line 356)
+* mlittle-endian: AArch64 Options. (line 27)
* mlittle-endian-data: RX Options. (line 42)
* mliw: MN10300 Options. (line 54)
-* mllsc: MIPS Options. (line 337)
-* mlocal-sdata: MIPS Options. (line 444)
-* mlock: ARC Options. (line 96)
+* mllsc: MIPS Options. (line 341)
+* mlocal-sdata: MIPS Options. (line 448)
+* mlock: ARC Options. (line 97)
+* mlong-calls <1>: V850 Options. (line 10)
+* mlong-calls <2>: MIPS Options. (line 578)
+* mlong-calls <3>: FRV Options. (line 99)
+* mlong-calls <4>: Blackfin Options. (line 121)
+* mlong-calls <5>: ARM Options. (line 196)
+* mlong-calls <6>: ARC Options. (line 163)
* mlong-calls: Adapteva Epiphany Options.
(line 55)
-* mlong-calls <1>: ARC Options. (line 161)
-* mlong-calls <2>: ARM Options. (line 195)
-* mlong-calls <3>: Blackfin Options. (line 120)
-* mlong-calls <4>: FRV Options. (line 122)
-* mlong-calls <5>: MIPS Options. (line 572)
-* mlong-calls <6>: V850 Options. (line 10)
+* mlong-double-128 <1>: x86 Options. (line 422)
* mlong-double-128: S/390 and zSeries Options.
(line 29)
-* mlong-double-128 <1>: x86 Options. (line 415)
+* mlong-double-64 <1>: x86 Options. (line 422)
* mlong-double-64: S/390 and zSeries Options.
(line 29)
-* mlong-double-64 <1>: x86 Options. (line 415)
-* mlong-double-80: x86 Options. (line 415)
+* mlong-double-80: x86 Options. (line 422)
* mlong-jumps: V850 Options. (line 108)
* mlong-load-store: HPPA Options. (line 59)
-* mlong32: MIPS Options. (line 419)
-* mlong64: MIPS Options. (line 414)
+* mlong32: MIPS Options. (line 423)
+* mlong64: MIPS Options. (line 418)
* mlongcall: RS/6000 and PowerPC Options.
- (line 781)
+ (line 784)
* mlongcalls: Xtensa Options. (line 72)
* mloop: V850 Options. (line 121)
-* mlow-64k: Blackfin Options. (line 69)
+* mlow-64k: Blackfin Options. (line 70)
* mlp64: IA-64 Options. (line 121)
-* mlra: ARC Options. (line 241)
-* mlra-priority-compact: ARC Options. (line 249)
-* mlra-priority-noncompact: ARC Options. (line 252)
-* mlra-priority-none: ARC Options. (line 246)
-* mlwp: x86 Options. (line 602)
-* mlzcnt: x86 Options. (line 608)
+* mlra: ARC Options. (line 243)
+* mlra-priority-compact: ARC Options. (line 251)
+* mlra-priority-noncompact: ARC Options. (line 254)
+* mlra-priority-none: ARC Options. (line 248)
+* mlwp: x86 Options. (line 608)
+* mlzcnt: x86 Options. (line 614)
+* mm: MeP Options. (line 84)
* MM: Preprocessor Options.
(line 210)
-* mm: MeP Options. (line 84)
-* mmac: CR16 Options. (line 9)
* mmac <1>: Score Options. (line 21)
-* mmac-24: ARC Options. (line 105)
-* mmac-d16: ARC Options. (line 101)
-* mmac_24: ARC Options. (line 376)
-* mmac_d16: ARC Options. (line 379)
-* mmad: MIPS Options. (line 581)
+* mmac: CR16 Options. (line 9)
+* mmac-24: ARC Options. (line 106)
+* mmac-d16: ARC Options. (line 102)
+* mmac_24: ARC Options. (line 378)
+* mmac_d16: ARC Options. (line 381)
+* mmad: MIPS Options. (line 587)
* mmainkernel: Nvidia PTX Options. (line 13)
* mmalloc64: VMS Options. (line 17)
* mmax: DEC Alpha Options. (line 163)
* mmax-constant-size: RX Options. (line 82)
-* mmax-stack-frame: CRIS Options. (line 23)
-* mmcount-ra-address: MIPS Options. (line 810)
+* mmax-stack-frame: CRIS Options. (line 22)
+* mmcount-ra-address: MIPS Options. (line 823)
+* mmcu <1>: MIPS Options. (line 401)
* mmcu: AVR Options. (line 9)
-* mmcu <1>: MIPS Options. (line 397)
* mmcu=: MSP430 Options. (line 14)
* MMD: Preprocessor Options.
- (line 292)
-* mmedia: FRV Options. (line 56)
-* mmedium-calls: ARC Options. (line 165)
+ (line 290)
+* mmedia: FRV Options. (line 44)
+* mmedium-calls: ARC Options. (line 167)
+* mmemcpy <1>: MIPS Options. (line 572)
* mmemcpy: MicroBlaze Options. (line 13)
-* mmemcpy <1>: MIPS Options. (line 566)
-* mmemcpy-strategy=STRATEGY: x86 Options. (line 859)
+* mmemcpy-strategy=STRATEGY: x86 Options. (line 868)
* mmemory-latency: DEC Alpha Options. (line 268)
-* mmemory-model: SPARC Options. (line 289)
-* mmemset-strategy=STRATEGY: x86 Options. (line 871)
+* mmemory-model: SPARC Options. (line 290)
+* mmemset-strategy=STRATEGY: x86 Options. (line 880)
* mmfcrf: RS/6000 and PowerPC Options.
(line 27)
* mmfpgpr: RS/6000 and PowerPC Options.
(line 27)
-* mmicromips: MIPS Options. (line 385)
+* mmicromips: MIPS Options. (line 389)
* mminimal-toc: RS/6000 and PowerPC Options.
- (line 313)
+ (line 314)
* mminmax: MeP Options. (line 87)
-* mmixed-code: ARC Options. (line 264)
-* mmmx: x86 Options. (line 575)
+* mmixed-code: ARC Options. (line 266)
+* mmmx: x86 Options. (line 581)
* mmodel=large: M32R/D Options. (line 33)
* mmodel=medium: M32R/D Options. (line 27)
* mmodel=small: M32R/D Options. (line 18)
-* mmovbe: x86 Options. (line 703)
-* mmpx: x86 Options. (line 616)
-* mmt: MIPS Options. (line 393)
+* mmovbe: x86 Options. (line 711)
+* mmpx: x86 Options. (line 622)
+* mmt: MIPS Options. (line 397)
* mmul: RL78 Options. (line 13)
-* mmul-bug-workaround: CRIS Options. (line 32)
+* mmul-bug-workaround: CRIS Options. (line 31)
* mmul.x: Moxie Options. (line 14)
* mmul32x16: ARC Options. (line 51)
* mmul64: ARC Options. (line 54)
-* mmuladd: FRV Options. (line 64)
+* mmuladd: FRV Options. (line 50)
* mmulhw: RS/6000 and PowerPC Options.
- (line 466)
+ (line 468)
* mmult: MeP Options. (line 90)
* mmult-bug: MN10300 Options. (line 9)
-* mmultcost: ARC Options. (line 326)
-* mmulti-cond-exec: FRV Options. (line 215)
-* mmulticore: Blackfin Options. (line 141)
+* mmultcost: ARC Options. (line 330)
+* mmulti-cond-exec: FRV Options. (line 176)
+* mmulticore: Blackfin Options. (line 142)
* mmultiple: RS/6000 and PowerPC Options.
- (line 416)
+ (line 418)
* mmvcle: S/390 and zSeries Options.
- (line 104)
+ (line 105)
* mmvme: RS/6000 and PowerPC Options.
- (line 686)
+ (line 688)
+* mmwaitx: x86 Options. (line 623)
* mn: H8/300 Options. (line 20)
-* mn-flash: AVR Options. (line 178)
-* mnan=2008: MIPS Options. (line 318)
-* mnan=legacy: MIPS Options. (line 318)
+* mn-flash: AVR Options. (line 177)
+* mnan=2008: MIPS Options. (line 322)
+* mnan=legacy: MIPS Options. (line 322)
* mneon-for-64bits: ARM Options. (line 339)
-* mnested-cond-exec: FRV Options. (line 230)
+* mnested-cond-exec: FRV Options. (line 189)
* mnhwloop: Score Options. (line 15)
* mno-16-bit: NDS32 Options. (line 42)
* mno-4byte-functions: MCore Options. (line 27)
* mno-8byte-align: V850 Options. (line 170)
-* mno-abicalls: MIPS Options. (line 190)
+* mno-abicalls: MIPS Options. (line 194)
* mno-abshi: PDP-11 Options. (line 58)
* mno-ac0: PDP-11 Options. (line 20)
-* mno-address-space-conversion: SPU Options. (line 68)
-* mno-align-double: x86 Options. (line 374)
-* mno-align-int: M680x0 Options. (line 263)
+* mno-address-space-conversion: SPU Options. (line 63)
+* mno-align-double: x86 Options. (line 380)
+* mno-align-int: M680x0 Options. (line 267)
* mno-align-loops: M32R/D Options. (line 76)
-* mno-align-stringops: x86 Options. (line 825)
+* mno-align-stringops: x86 Options. (line 834)
* mno-altivec: RS/6000 and PowerPC Options.
- (line 135)
+ (line 136)
* mno-am33: MN10300 Options. (line 20)
-* mno-app-regs: SPARC Options. (line 10)
* mno-app-regs <1>: V850 Options. (line 185)
+* mno-app-regs: SPARC Options. (line 10)
* mno-as100-syntax: RX Options. (line 76)
-* mno-atomic-updates: SPU Options. (line 83)
+* mno-atomic-updates: SPU Options. (line 78)
* mno-avoid-indexed-addresses: RS/6000 and PowerPC Options.
- (line 448)
+ (line 450)
* mno-backchain: S/390 and zSeries Options.
(line 35)
-* mno-base-addresses: MMIX Options. (line 53)
+* mno-base-addresses: MMIX Options. (line 54)
* mno-bit-align: RS/6000 and PowerPC Options.
- (line 480)
-* mno-bitfield: M680x0 Options. (line 227)
-* mno-branch-likely: MIPS Options. (line 751)
-* mno-branch-predict: MMIX Options. (line 48)
-* mno-brcc: ARC Options. (line 201)
+ (line 482)
+* mno-bitfield: M680x0 Options. (line 231)
+* mno-branch-likely: MIPS Options. (line 764)
+* mno-branch-predict: MMIX Options. (line 49)
+* mno-brcc: ARC Options. (line 203)
* mno-bwx: DEC Alpha Options. (line 163)
-* mno-bypass-cache: Nios II Options. (line 70)
-* mno-cache-volatile: Nios II Options. (line 76)
+* mno-bypass-cache: Nios II Options. (line 72)
+* mno-cache-volatile: Nios II Options. (line 78)
* mno-callgraph-data: MCore Options. (line 31)
-* mno-cbcond: SPARC Options. (line 223)
-* mno-check-zero-division: MIPS Options. (line 546)
+* mno-cbcond: SPARC Options. (line 224)
+* mno-check-zero-division: MIPS Options. (line 551)
* mno-cix: DEC Alpha Options. (line 163)
* mno-clearbss: MicroBlaze Options. (line 16)
* mno-cmov: NDS32 Options. (line 24)
* mno-cmpb: RS/6000 and PowerPC Options.
(line 27)
-* mno-cond-exec: ARC Options. (line 213)
-* mno-cond-exec <1>: FRV Options. (line 194)
-* mno-cond-move: FRV Options. (line 166)
+* mno-cond-exec <1>: FRV Options. (line 158)
+* mno-cond-exec: ARC Options. (line 215)
+* mno-cond-move: FRV Options. (line 134)
* mno-const-align: CRIS Options. (line 55)
* mno-const16: Xtensa Options. (line 10)
-* mno-crt0: MN10300 Options. (line 43)
* mno-crt0 <1>: Moxie Options. (line 18)
+* mno-crt0: MN10300 Options. (line 43)
* mno-crypto: RS/6000 and PowerPC Options.
- (line 223)
-* mno-csync-anomaly: Blackfin Options. (line 65)
-* mno-custom-INSN: Nios II Options. (line 97)
+ (line 224)
+* mno-csync-anomaly: Blackfin Options. (line 66)
+* mno-custom-INSN: Nios II Options. (line 99)
* mno-data-align: CRIS Options. (line 55)
* mno-debug: S/390 and zSeries Options.
- (line 110)
-* mno-default: x86 Options. (line 656)
+ (line 112)
+* mno-default: x86 Options. (line 664)
* mno-direct-move: RS/6000 and PowerPC Options.
- (line 229)
+ (line 230)
* mno-disable-callt: V850 Options. (line 92)
-* mno-div: M680x0 Options. (line 206)
* mno-div <1>: MCore Options. (line 15)
+* mno-div: M680x0 Options. (line 209)
* mno-dlmzb: RS/6000 and PowerPC Options.
- (line 473)
-* mno-double: FRV Options. (line 52)
+ (line 475)
+* mno-double: FRV Options. (line 41)
* mno-dpfp-lrsr: ARC Options. (line 39)
-* mno-dsp: MIPS Options. (line 351)
-* mno-dspr2: MIPS Options. (line 357)
+* mno-dsp: MIPS Options. (line 355)
+* mno-dspr2: MIPS Options. (line 361)
* mno-dwarf2-asm: IA-64 Options. (line 94)
-* mno-dword: FRV Options. (line 44)
+* mno-dword: FRV Options. (line 35)
* mno-eabi: RS/6000 and PowerPC Options.
- (line 710)
+ (line 712)
* mno-early-stop-bits: IA-64 Options. (line 100)
-* mno-eflags: FRV Options. (line 155)
-* mno-embedded-data: MIPS Options. (line 493)
+* mno-eflags: FRV Options. (line 125)
+* mno-embedded-data: MIPS Options. (line 498)
* mno-ep: V850 Options. (line 16)
-* mno-epilogue-cfi: ARC Options. (line 158)
+* mno-epilogue-cfi: ARC Options. (line 160)
* mno-epsilon: MMIX Options. (line 15)
-* mno-eva: MIPS Options. (line 401)
+* mno-eva: MIPS Options. (line 405)
+* mno-explicit-relocs <1>: MIPS Options. (line 542)
* mno-explicit-relocs: DEC Alpha Options. (line 176)
-* mno-explicit-relocs <1>: MIPS Options. (line 537)
* mno-exr: H8/300 Options. (line 33)
-* mno-extern-sdata: MIPS Options. (line 456)
-* mno-fancy-math-387: x86 Options. (line 364)
-* mno-fast-sw-div: Nios II Options. (line 82)
-* mno-faster-structs: SPARC Options. (line 91)
+* mno-extern-sdata: MIPS Options. (line 460)
+* mno-fancy-math-387: x86 Options. (line 370)
+* mno-fast-sw-div: Nios II Options. (line 84)
+* mno-faster-structs: SPARC Options. (line 92)
* mno-fix: DEC Alpha Options. (line 163)
-* mno-fix-24k: MIPS Options. (line 610)
+* mno-fix-24k: MIPS Options. (line 617)
* mno-fix-cortex-a53-835769: AArch64 Options. (line 67)
-* mno-fix-r10000: MIPS Options. (line 632)
-* mno-fix-r4000: MIPS Options. (line 616)
-* mno-fix-r4400: MIPS Options. (line 626)
+* mno-fix-cortex-a53-843419: AArch64 Options. (line 74)
+* mno-fix-r10000: MIPS Options. (line 644)
+* mno-fix-r4000: MIPS Options. (line 623)
+* mno-fix-r4400: MIPS Options. (line 637)
* mno-flat: SPARC Options. (line 22)
-* mno-float: MIPS Options. (line 272)
+* mno-float: MIPS Options. (line 276)
* mno-float32: PDP-11 Options. (line 48)
* mno-float64: PDP-11 Options. (line 52)
* mno-flush-func: M32R/D Options. (line 98)
* mno-flush-trap: M32R/D Options. (line 90)
-* mno-fmaf: SPARC Options. (line 237)
+* mno-fmaf: SPARC Options. (line 238)
* mno-fp-in-toc: RS/6000 and PowerPC Options.
- (line 313)
+ (line 314)
* mno-fp-regs: DEC Alpha Options. (line 25)
-* mno-fp-ret-in-387: x86 Options. (line 354)
+* mno-fp-ret-in-387: x86 Options. (line 360)
* mno-fprnd: RS/6000 and PowerPC Options.
(line 27)
-* mno-fpu: SPARC Options. (line 39)
* mno-fpu <1>: Visium Options. (line 24)
-* mno-fsca: SH Options. (line 489)
-* mno-fsrra: SH Options. (line 498)
-* mno-fused-madd: IA-64 Options. (line 88)
-* mno-fused-madd <1>: MIPS Options. (line 593)
-* mno-fused-madd <2>: RS/6000 and PowerPC Options.
- (line 457)
+* mno-fpu: SPARC Options. (line 40)
+* mno-fsca: SH Options. (line 497)
+* mno-fsrra: SH Options. (line 506)
+* mno-fused-madd <1>: Xtensa Options. (line 19)
+* mno-fused-madd <2>: SH Options. (line 488)
* mno-fused-madd <3>: S/390 and zSeries Options.
- (line 135)
-* mno-fused-madd <4>: SH Options. (line 480)
-* mno-fused-madd <5>: Xtensa Options. (line 19)
+ (line 137)
+* mno-fused-madd <4>: RS/6000 and PowerPC Options.
+ (line 459)
+* mno-fused-madd <5>: MIPS Options. (line 599)
+* mno-fused-madd: IA-64 Options. (line 88)
* mno-gnu-as: IA-64 Options. (line 18)
* mno-gnu-ld: IA-64 Options. (line 23)
* mno-gotplt: CRIS Options. (line 81)
-* mno-gpopt: MIPS Options. (line 478)
-* mno-gpopt <1>: Nios II Options. (line 16)
-* mno-hard-dfp: RS/6000 and PowerPC Options.
- (line 27)
+* mno-gpopt <1>: Nios II Options. (line 17)
+* mno-gpopt: MIPS Options. (line 483)
* mno-hard-dfp <1>: S/390 and zSeries Options.
(line 20)
+* mno-hard-dfp: RS/6000 and PowerPC Options.
+ (line 27)
* mno-hardlit: MCore Options. (line 10)
-* mno-hw-div: Nios II Options. (line 91)
-* mno-hw-mul: Nios II Options. (line 91)
-* mno-hw-mulx: Nios II Options. (line 91)
-* mno-id-shared-library: Blackfin Options. (line 87)
+* mno-hw-div: Nios II Options. (line 93)
+* mno-hw-mul: Nios II Options. (line 93)
+* mno-hw-mulx: Nios II Options. (line 93)
+* mno-id-shared-library: Blackfin Options. (line 88)
* mno-ieee: SH Options. (line 186)
-* mno-ieee-fp: x86 Options. (line 336)
-* mno-imadd: MIPS Options. (line 586)
+* mno-ieee-fp: x86 Options. (line 342)
+* mno-imadd: MIPS Options. (line 592)
* mno-inline-float-divide: IA-64 Options. (line 62)
* mno-inline-int-divide: IA-64 Options. (line 73)
* mno-inline-sqrt: IA-64 Options. (line 84)
* mno-int16: PDP-11 Options. (line 44)
* mno-int32: PDP-11 Options. (line 40)
-* mno-interlink-compressed: MIPS Options. (line 133)
-* mno-interlink-mips16: MIPS Options. (line 145)
-* mno-interrupts: AVR Options. (line 181)
+* mno-interlink-compressed: MIPS Options. (line 136)
+* mno-interlink-mips16: MIPS Options. (line 148)
+* mno-interrupts: AVR Options. (line 180)
* mno-isel: RS/6000 and PowerPC Options.
- (line 194)
-* mno-knuthdiv: MMIX Options. (line 32)
-* mno-leaf-id-shared-library: Blackfin Options. (line 97)
+ (line 195)
+* mno-knuthdiv: MMIX Options. (line 33)
+* mno-leaf-id-shared-library: Blackfin Options. (line 98)
* mno-libfuncs: MMIX Options. (line 10)
-* mno-llsc: MIPS Options. (line 337)
-* mno-local-sdata: MIPS Options. (line 444)
-* mno-long-calls: ARM Options. (line 195)
-* mno-long-calls <1>: Blackfin Options. (line 120)
-* mno-long-calls <2>: HPPA Options. (line 129)
-* mno-long-calls <3>: MIPS Options. (line 572)
-* mno-long-calls <4>: V850 Options. (line 10)
+* mno-llsc: MIPS Options. (line 341)
+* mno-local-sdata: MIPS Options. (line 448)
+* mno-long-calls <1>: V850 Options. (line 10)
+* mno-long-calls <2>: MIPS Options. (line 578)
+* mno-long-calls <3>: HPPA Options. (line 129)
+* mno-long-calls <4>: Blackfin Options. (line 121)
+* mno-long-calls: ARM Options. (line 196)
* mno-long-jumps: V850 Options. (line 108)
* mno-longcall: RS/6000 and PowerPC Options.
- (line 781)
+ (line 784)
* mno-longcalls: Xtensa Options. (line 72)
-* mno-low-64k: Blackfin Options. (line 73)
-* mno-lsim: FR30 Options. (line 14)
+* mno-low-64k: Blackfin Options. (line 74)
* mno-lsim <1>: MCore Options. (line 46)
-* mno-mad: MIPS Options. (line 581)
+* mno-lsim: FR30 Options. (line 14)
+* mno-mad: MIPS Options. (line 587)
* mno-max: DEC Alpha Options. (line 163)
-* mno-mcount-ra-address: MIPS Options. (line 810)
-* mno-mcu: MIPS Options. (line 397)
-* mno-mdmx: MIPS Options. (line 374)
-* mno-media: FRV Options. (line 60)
-* mno-memcpy: MIPS Options. (line 566)
+* mno-mcount-ra-address: MIPS Options. (line 823)
+* mno-mcu: MIPS Options. (line 401)
+* mno-mdmx: MIPS Options. (line 378)
+* mno-media: FRV Options. (line 47)
+* mno-memcpy: MIPS Options. (line 572)
* mno-mfcrf: RS/6000 and PowerPC Options.
(line 27)
* mno-mfpgpr: RS/6000 and PowerPC Options.
(line 27)
-* mno-millicode: ARC Options. (line 255)
-* mno-mips16: MIPS Options. (line 118)
-* mno-mips3d: MIPS Options. (line 380)
-* mno-mmicromips: MIPS Options. (line 385)
+* mno-millicode: ARC Options. (line 257)
+* mno-mips16: MIPS Options. (line 120)
+* mno-mips3d: MIPS Options. (line 384)
+* mno-mmicromips: MIPS Options. (line 389)
* mno-mpy: ARC Options. (line 48)
-* mno-mt: MIPS Options. (line 393)
-* mno-mul-bug-workaround: CRIS Options. (line 32)
-* mno-muladd: FRV Options. (line 68)
+* mno-mt: MIPS Options. (line 397)
+* mno-mul-bug-workaround: CRIS Options. (line 31)
+* mno-muladd: FRV Options. (line 53)
* mno-mulhw: RS/6000 and PowerPC Options.
- (line 466)
+ (line 468)
* mno-mult-bug: MN10300 Options. (line 13)
-* mno-multi-cond-exec: FRV Options. (line 223)
+* mno-multi-cond-exec: FRV Options. (line 183)
* mno-multiple: RS/6000 and PowerPC Options.
- (line 416)
+ (line 418)
* mno-mvcle: S/390 and zSeries Options.
- (line 104)
-* mno-nested-cond-exec: FRV Options. (line 237)
-* mno-odd-spreg: MIPS Options. (line 291)
+ (line 105)
+* mno-nested-cond-exec: FRV Options. (line 195)
+* mno-odd-spreg: MIPS Options. (line 295)
* mno-omit-leaf-frame-pointer: AArch64 Options. (line 54)
-* mno-optimize-membar: FRV Options. (line 249)
+* mno-optimize-membar: FRV Options. (line 205)
* mno-opts: MeP Options. (line 93)
-* mno-pack: FRV Options. (line 151)
+* mno-pack: FRV Options. (line 122)
* mno-packed-stack: S/390 and zSeries Options.
(line 54)
* mno-paired: RS/6000 and PowerPC Options.
- (line 208)
-* mno-paired-single: MIPS Options. (line 368)
+ (line 209)
+* mno-paired-single: MIPS Options. (line 372)
* mno-perf-ext: NDS32 Options. (line 30)
* mno-pic: IA-64 Options. (line 26)
* mno-pid: RX Options. (line 117)
-* mno-plt: MIPS Options. (line 217)
-* mno-popc: SPARC Options. (line 230)
+* mno-plt: MIPS Options. (line 221)
+* mno-popc: SPARC Options. (line 231)
* mno-popcntb: RS/6000 and PowerPC Options.
(line 27)
* mno-popcntd: RS/6000 and PowerPC Options.
(line 27)
* mno-postinc: Adapteva Epiphany Options.
- (line 109)
+ (line 110)
* mno-postmodify: Adapteva Epiphany Options.
- (line 109)
+ (line 110)
* mno-power8-fusion: RS/6000 and PowerPC Options.
- (line 235)
+ (line 236)
* mno-power8-vector: RS/6000 and PowerPC Options.
- (line 241)
+ (line 242)
* mno-powerpc-gfxopt: RS/6000 and PowerPC Options.
(line 27)
* mno-powerpc-gpopt: RS/6000 and PowerPC Options.
@@ -49944,27 +50418,27 @@ look up both forms.
* mno-prolog-function: V850 Options. (line 23)
* mno-prologue-epilogue: CRIS Options. (line 71)
* mno-prototype: RS/6000 and PowerPC Options.
- (line 670)
-* mno-push-args: x86 Options. (line 803)
+ (line 672)
+* mno-push-args: x86 Options. (line 811)
* mno-quad-memory: RS/6000 and PowerPC Options.
- (line 248)
+ (line 249)
* mno-quad-memory-atomic: RS/6000 and PowerPC Options.
- (line 254)
-* mno-red-zone: x86 Options. (line 971)
+ (line 255)
+* mno-red-zone: x86 Options. (line 982)
* mno-register-names: IA-64 Options. (line 37)
* mno-regnames: RS/6000 and PowerPC Options.
- (line 775)
+ (line 778)
* mno-relax: V850 Options. (line 103)
* mno-relax-immediate: MCore Options. (line 19)
* mno-relocatable: RS/6000 and PowerPC Options.
- (line 496)
+ (line 498)
* mno-relocatable-lib: RS/6000 and PowerPC Options.
- (line 507)
+ (line 509)
* mno-renesas: SH Options. (line 176)
* mno-round-nearest: Adapteva Epiphany Options.
(line 51)
-* mno-rtd: M680x0 Options. (line 258)
-* mno-scc: FRV Options. (line 180)
+* mno-rtd: M680x0 Options. (line 262)
+* mno-scc: FRV Options. (line 146)
* mno-sched-ar-data-spec: IA-64 Options. (line 134)
* mno-sched-ar-in-data-spec: IA-64 Options. (line 155)
* mno-sched-br-data-spec: IA-64 Options. (line 128)
@@ -49975,236 +50449,236 @@ look up both forms.
* mno-sched-prefer-non-control-spec-insns: IA-64 Options. (line 175)
* mno-sched-prefer-non-data-spec-insns: IA-64 Options. (line 168)
* mno-sched-prolog: ARM Options. (line 32)
-* mno-sdata: ARC Options. (line 174)
-* mno-sdata <1>: IA-64 Options. (line 42)
-* mno-sdata <2>: RS/6000 and PowerPC Options.
- (line 756)
-* mno-sep-data: Blackfin Options. (line 115)
+* mno-sdata <1>: RS/6000 and PowerPC Options.
+ (line 759)
+* mno-sdata <2>: IA-64 Options. (line 42)
+* mno-sdata: ARC Options. (line 175)
+* mno-sep-data: Blackfin Options. (line 116)
* mno-serialize-volatile: Xtensa Options. (line 35)
-* mno-short: M680x0 Options. (line 222)
+* mno-short: M680x0 Options. (line 226)
* mno-side-effects: CRIS Options. (line 46)
* mno-sim: RX Options. (line 71)
-* mno-single-exit: MMIX Options. (line 65)
+* mno-single-exit: MMIX Options. (line 66)
* mno-slow-bytes: MCore Options. (line 35)
* mno-small-exec: S/390 and zSeries Options.
- (line 79)
-* mno-smartmips: MIPS Options. (line 364)
+ (line 80)
+* mno-smartmips: MIPS Options. (line 368)
* mno-soft-cmpsf: Adapteva Epiphany Options.
(line 29)
* mno-soft-float: DEC Alpha Options. (line 10)
* mno-space-regs: HPPA Options. (line 38)
* mno-spe: RS/6000 and PowerPC Options.
- (line 203)
-* mno-specld-anomaly: Blackfin Options. (line 55)
-* mno-split-addresses: MIPS Options. (line 531)
+ (line 204)
+* mno-specld-anomaly: Blackfin Options. (line 56)
+* mno-split-addresses: MIPS Options. (line 536)
* mno-stack-align: CRIS Options. (line 55)
-* mno-stack-bias: SPARC Options. (line 313)
-* mno-strict-align: M680x0 Options. (line 283)
+* mno-stack-bias: SPARC Options. (line 314)
* mno-strict-align <1>: RS/6000 and PowerPC Options.
- (line 491)
+ (line 493)
+* mno-strict-align: M680x0 Options. (line 287)
* mno-string: RS/6000 and PowerPC Options.
- (line 427)
+ (line 429)
* mno-sum-in-toc: RS/6000 and PowerPC Options.
- (line 313)
-* mno-sym32: MIPS Options. (line 429)
+ (line 314)
+* mno-sym32: MIPS Options. (line 433)
* mno-target-align: Xtensa Options. (line 59)
* mno-text-section-literals: Xtensa Options. (line 47)
* mno-tls-markers: RS/6000 and PowerPC Options.
- (line 813)
+ (line 817)
* mno-toc: RS/6000 and PowerPC Options.
- (line 516)
-* mno-toplevel-symbols: MMIX Options. (line 39)
+ (line 518)
+* mno-toplevel-symbols: MMIX Options. (line 40)
* mno-tpf-trace: S/390 and zSeries Options.
- (line 129)
+ (line 131)
* mno-unaligned-access: ARM Options. (line 326)
-* mno-unaligned-doubles: SPARC Options. (line 73)
-* mno-uninit-const-in-rodata: MIPS Options. (line 501)
+* mno-unaligned-doubles: SPARC Options. (line 74)
+* mno-uninit-const-in-rodata: MIPS Options. (line 506)
* mno-update: RS/6000 and PowerPC Options.
- (line 438)
+ (line 440)
* mno-upper-regs: RS/6000 and PowerPC Options.
- (line 276)
+ (line 277)
* mno-upper-regs-df: RS/6000 and PowerPC Options.
- (line 260)
+ (line 261)
* mno-upper-regs-sf: RS/6000 and PowerPC Options.
- (line 268)
-* mno-user-mode: SPARC Options. (line 85)
-* mno-usermode: SH Options. (line 295)
+ (line 269)
+* mno-user-mode: SPARC Options. (line 86)
+* mno-usermode: SH Options. (line 297)
* mno-v3push: NDS32 Options. (line 36)
-* mno-v8plus: SPARC Options. (line 194)
+* mno-v8plus: SPARC Options. (line 195)
* mno-vect-double: Adapteva Epiphany Options.
- (line 115)
-* mno-virt: MIPS Options. (line 405)
-* mno-vis: SPARC Options. (line 201)
-* mno-vis2: SPARC Options. (line 207)
-* mno-vis3: SPARC Options. (line 215)
-* mno-vliw-branch: FRV Options. (line 208)
+ (line 116)
+* mno-virt: MIPS Options. (line 409)
+* mno-vis: SPARC Options. (line 202)
+* mno-vis2: SPARC Options. (line 208)
+* mno-vis3: SPARC Options. (line 216)
+* mno-vliw-branch: FRV Options. (line 170)
* mno-volatile-asm-stop: IA-64 Options. (line 32)
-* mno-volatile-cache: ARC Options. (line 188)
+* mno-volatile-cache: ARC Options. (line 189)
* mno-vrsave: RS/6000 and PowerPC Options.
- (line 173)
+ (line 174)
* mno-vsx: RS/6000 and PowerPC Options.
- (line 217)
+ (line 218)
* mno-warn-multiple-fast-interrupts: RX Options. (line 143)
* mno-wide-bitfields: MCore Options. (line 23)
-* mno-xgot: M680x0 Options. (line 315)
-* mno-xgot <1>: MIPS Options. (line 227)
+* mno-xgot <1>: MIPS Options. (line 231)
+* mno-xgot: M680x0 Options. (line 319)
* mno-xl-compat: RS/6000 and PowerPC Options.
- (line 348)
-* mno-xpa: MIPS Options. (line 410)
-* mno-zdcbranch: SH Options. (line 465)
-* mno-zero-extend: MMIX Options. (line 26)
-* mnobitfield: M680x0 Options. (line 227)
+ (line 349)
+* mno-xpa: MIPS Options. (line 414)
+* mno-zdcbranch: SH Options. (line 473)
+* mno-zero-extend: MMIX Options. (line 27)
+* mnobitfield: M680x0 Options. (line 231)
* mnoliw: MN10300 Options. (line 59)
* mnomacsave: SH Options. (line 181)
* mnop-fun-dllimport: x86 Windows Options.
(line 22)
-* mnop-mcount: x86 Options. (line 911)
+* mnop-mcount: x86 Options. (line 920)
* mnops: Adapteva Epiphany Options.
(line 26)
* mnorm: ARC Options. (line 58)
* mnosetlb: MN10300 Options. (line 69)
* mnosplit-lohi: Adapteva Epiphany Options.
- (line 109)
-* modd-spreg: MIPS Options. (line 291)
+ (line 110)
+* modd-spreg: MIPS Options. (line 295)
+* momit-leaf-frame-pointer <1>: x86 Options. (line 884)
+* momit-leaf-frame-pointer <2>: Blackfin Options. (line 44)
* momit-leaf-frame-pointer: AArch64 Options. (line 54)
-* momit-leaf-frame-pointer <1>: Blackfin Options. (line 43)
-* momit-leaf-frame-pointer <2>: x86 Options. (line 875)
* mone-byte-bool: Darwin Options. (line 90)
-* moptimize-membar: FRV Options. (line 244)
+* moptimize-membar: FRV Options. (line 201)
* MP: Preprocessor Options.
(line 239)
* mpa-risc-1-0: HPPA Options. (line 19)
* mpa-risc-1-1: HPPA Options. (line 19)
* mpa-risc-2-0: HPPA Options. (line 19)
-* mpack: FRV Options. (line 147)
+* mpack: FRV Options. (line 119)
* mpacked-stack: S/390 and zSeries Options.
(line 54)
* mpadstruct: SH Options. (line 210)
* mpaired: RS/6000 and PowerPC Options.
- (line 208)
-* mpaired-single: MIPS Options. (line 368)
-* mpc32: x86 Options. (line 499)
-* mpc64: x86 Options. (line 499)
-* mpc80: x86 Options. (line 499)
-* mpclmul: x86 Options. (line 592)
-* mpcrel: M680x0 Options. (line 275)
-* mpdebug: CRIS Options. (line 36)
+ (line 209)
+* mpaired-single: MIPS Options. (line 372)
+* mpc32: x86 Options. (line 505)
+* mpc64: x86 Options. (line 505)
+* mpc80: x86 Options. (line 505)
+* mpclmul: x86 Options. (line 598)
+* mpcrel: M680x0 Options. (line 279)
+* mpdebug: CRIS Options. (line 35)
* mpe: RS/6000 and PowerPC Options.
- (line 367)
+ (line 369)
* mpe-aligned-commons: x86 Windows Options.
(line 59)
* mperf-ext: NDS32 Options. (line 27)
-* mpic-data-is-text-relative: ARM Options. (line 232)
-* mpic-register: ARM Options. (line 225)
+* mpic-data-is-text-relative: ARM Options. (line 233)
+* mpic-register: ARM Options. (line 226)
* mpid: RX Options. (line 117)
-* mplt: MIPS Options. (line 217)
+* mplt: MIPS Options. (line 221)
* mpointer-size=SIZE: VMS Options. (line 20)
* mpointers-to-nested-functions: RS/6000 and PowerPC Options.
- (line 918)
-* mpoke-function-name: ARM Options. (line 238)
-* mpopc: SPARC Options. (line 230)
-* mpopcnt: x86 Options. (line 604)
+ (line 923)
+* mpoke-function-name: ARM Options. (line 239)
+* mpopc: SPARC Options. (line 231)
+* mpopcnt: x86 Options. (line 610)
* mpopcntb: RS/6000 and PowerPC Options.
(line 27)
* mpopcntd: RS/6000 and PowerPC Options.
(line 27)
* mportable-runtime: HPPA Options. (line 64)
* mpower8-fusion: RS/6000 and PowerPC Options.
- (line 235)
+ (line 236)
* mpower8-vector: RS/6000 and PowerPC Options.
- (line 241)
+ (line 242)
* mpowerpc-gfxopt: RS/6000 and PowerPC Options.
(line 27)
* mpowerpc-gpopt: RS/6000 and PowerPC Options.
(line 27)
* mpowerpc64: RS/6000 and PowerPC Options.
(line 27)
-* mprefer-avx128: x86 Options. (line 680)
+* mprefer-avx128: x86 Options. (line 688)
* mprefer-short-insn-regs: Adapteva Epiphany Options.
(line 13)
-* mprefergot: SH Options. (line 289)
-* mpreferred-stack-boundary: x86 Options. (line 529)
-* mprefetchwt1: x86 Options. (line 600)
-* mpretend-cmove: SH Options. (line 507)
+* mprefergot: SH Options. (line 291)
+* mpreferred-stack-boundary: x86 Options. (line 535)
+* mprefetchwt1: x86 Options. (line 606)
+* mpretend-cmove: SH Options. (line 515)
* mprint-tune-info: ARM Options. (line 363)
* mprioritize-restricted-insns: RS/6000 and PowerPC Options.
- (line 545)
+ (line 547)
* mprolog-function: V850 Options. (line 23)
* mprologue-epilogue: CRIS Options. (line 71)
* mprototype: RS/6000 and PowerPC Options.
- (line 670)
-* mpt-fixed: SH Options. (line 428)
-* mpush-args: x86 Options. (line 803)
+ (line 672)
+* mpt-fixed: SH Options. (line 434)
+* mpush-args: x86 Options. (line 811)
* MQ: Preprocessor Options.
- (line 266)
-* mq-class: ARC Options. (line 269)
+ (line 265)
+* mq-class: ARC Options. (line 271)
* mquad-memory: RS/6000 and PowerPC Options.
- (line 248)
+ (line 249)
* mquad-memory-atomic: RS/6000 and PowerPC Options.
- (line 254)
-* mr10k-cache-barrier: MIPS Options. (line 673)
-* mRcq: ARC Options. (line 273)
-* mRcw: ARC Options. (line 277)
-* mrdrnd: x86 Options. (line 595)
+ (line 255)
+* mr10k-cache-barrier: MIPS Options. (line 686)
+* mRcq: ARC Options. (line 275)
+* mRcw: ARC Options. (line 279)
+* mrdrnd: x86 Options. (line 601)
+* mrecip <1>: x86 Options. (line 721)
* mrecip: RS/6000 and PowerPC Options.
- (line 825)
-* mrecip <1>: x86 Options. (line 713)
+ (line 829)
* mrecip-precision: RS/6000 and PowerPC Options.
- (line 882)
+ (line 887)
+* mrecip=opt <1>: x86 Options. (line 743)
* mrecip=opt: RS/6000 and PowerPC Options.
- (line 838)
-* mrecip=opt <1>: x86 Options. (line 735)
-* mrecord-mcount: x86 Options. (line 905)
+ (line 842)
+* mrecord-mcount: x86 Options. (line 914)
* mreduced-regs: NDS32 Options. (line 15)
* mregister-names: IA-64 Options. (line 37)
* mregnames: RS/6000 and PowerPC Options.
- (line 775)
-* mregparm: x86 Options. (line 466)
-* mrelax: AVR Options. (line 185)
-* mrelax <1>: H8/300 Options. (line 9)
-* mrelax <2>: MN10300 Options. (line 46)
-* mrelax <3>: MSP430 Options. (line 50)
-* mrelax <4>: NDS32 Options. (line 72)
-* mrelax <5>: RX Options. (line 95)
-* mrelax <6>: SH Options. (line 158)
-* mrelax <7>: V850 Options. (line 103)
+ (line 778)
+* mregparm: x86 Options. (line 472)
+* mrelax <1>: V850 Options. (line 103)
+* mrelax <2>: SH Options. (line 158)
+* mrelax <3>: RX Options. (line 95)
+* mrelax <4>: NDS32 Options. (line 74)
+* mrelax <5>: MSP430 Options. (line 50)
+* mrelax <6>: MN10300 Options. (line 46)
+* mrelax <7>: H8/300 Options. (line 9)
+* mrelax: AVR Options. (line 184)
* mrelax-immediate: MCore Options. (line 19)
-* mrelax-pic-calls: MIPS Options. (line 797)
+* mrelax-pic-calls: MIPS Options. (line 810)
* mrelocatable: RS/6000 and PowerPC Options.
- (line 496)
+ (line 498)
* mrelocatable-lib: RS/6000 and PowerPC Options.
- (line 507)
+ (line 509)
* mrenesas: SH Options. (line 173)
* mrepeat: MeP Options. (line 96)
* mrestrict-it: ARM Options. (line 357)
* mreturn-pointer-on-d0: MN10300 Options. (line 36)
* mrh850-abi: V850 Options. (line 127)
-* mrmw: AVR Options. (line 199)
-* mrtd: M680x0 Options. (line 236)
-* mrtd <1>: x86 Options. (line 442)
-* mrtd <2>: Function Attributes.
- (line 215)
-* mrtm: x86 Options. (line 614)
+* mrmw: AVR Options. (line 198)
+* mrtd <1>: Function Attributes.
+ (line 217)
+* mrtd <2>: x86 Options. (line 448)
+* mrtd: M680x0 Options. (line 240)
+* mrtm: x86 Options. (line 620)
* mrtp: VxWorks Options. (line 11)
-* mrtsc: ARC Options. (line 109)
-* ms: H8/300 Options. (line 17)
+* mrtsc: ARC Options. (line 110)
* ms <1>: MeP Options. (line 100)
+* ms: H8/300 Options. (line 17)
* ms2600: H8/300 Options. (line 24)
-* msafe-dma: SPU Options. (line 18)
-* msafe-hints: SPU Options. (line 112)
-* msahf: x86 Options. (line 693)
+* msafe-dma: SPU Options. (line 17)
+* msafe-hints: SPU Options. (line 107)
+* msahf: x86 Options. (line 701)
* msatur: MeP Options. (line 105)
* msave-acc-in-interrupts: RX Options. (line 109)
* msave-toc-indirect: RS/6000 and PowerPC Options.
- (line 930)
-* mscc: FRV Options. (line 173)
+ (line 935)
+* mscc: FRV Options. (line 140)
* msched-ar-data-spec: IA-64 Options. (line 134)
* msched-ar-in-data-spec: IA-64 Options. (line 155)
* msched-br-data-spec: IA-64 Options. (line 128)
* msched-br-in-data-spec: IA-64 Options. (line 148)
* msched-control-spec: IA-64 Options. (line 140)
* msched-costly-dep: RS/6000 and PowerPC Options.
- (line 552)
+ (line 554)
* msched-count-spec-in-critical-path: IA-64 Options. (line 182)
* msched-fp-mem-deps-zero-cost: IA-64 Options. (line 198)
* msched-in-control-spec: IA-64 Options. (line 162)
@@ -50213,71 +50687,70 @@ look up both forms.
* msched-prefer-non-control-spec-insns: IA-64 Options. (line 175)
* msched-prefer-non-data-spec-insns: IA-64 Options. (line 168)
* msched-spec-ldc: IA-64 Options. (line 187)
-* msched-spec-ldc <1>: IA-64 Options. (line 190)
* msched-stop-bits-after-every-cycle: IA-64 Options. (line 194)
* mschedule: HPPA Options. (line 71)
* mscore5: Score Options. (line 25)
* mscore5u: Score Options. (line 28)
* mscore7: Score Options. (line 31)
-* mscore7d: Score Options. (line 35)
+* mscore7d: Score Options. (line 34)
* msda: V850 Options. (line 40)
-* msdata: IA-64 Options. (line 42)
* msdata <1>: RS/6000 and PowerPC Options.
- (line 743)
+ (line 746)
+* msdata: IA-64 Options. (line 42)
* msdata=all: C6X Options. (line 30)
* msdata=data: RS/6000 and PowerPC Options.
- (line 748)
-* msdata=default: C6X Options. (line 22)
+ (line 751)
* msdata=default <1>: RS/6000 and PowerPC Options.
- (line 743)
+ (line 746)
+* msdata=default: C6X Options. (line 22)
* msdata=eabi: RS/6000 and PowerPC Options.
- (line 724)
+ (line 726)
+* msdata=none <1>: RS/6000 and PowerPC Options.
+ (line 759)
+* msdata=none <2>: M32R/D Options. (line 40)
* msdata=none: C6X Options. (line 35)
-* msdata=none <1>: M32R/D Options. (line 40)
-* msdata=none <2>: RS/6000 and PowerPC Options.
- (line 756)
* msdata=sdata: M32R/D Options. (line 49)
* msdata=sysv: RS/6000 and PowerPC Options.
- (line 734)
+ (line 737)
* msdata=use: M32R/D Options. (line 53)
-* msdram: Blackfin Options. (line 171)
* msdram <1>: MeP Options. (line 110)
+* msdram: Blackfin Options. (line 172)
* msecure-plt: RS/6000 and PowerPC Options.
- (line 183)
+ (line 184)
* msel-sched-dont-check-control-spec: IA-64 Options. (line 203)
-* msep-data: Blackfin Options. (line 109)
+* msep-data: Blackfin Options. (line 110)
* mserialize-volatile: Xtensa Options. (line 35)
* msetlb: MN10300 Options. (line 64)
-* msha: x86 Options. (line 590)
-* mshared-library-id: Blackfin Options. (line 102)
-* mshort: M680x0 Options. (line 216)
+* msha: x86 Options. (line 596)
+* mshared-library-id: Blackfin Options. (line 103)
+* mshort: M680x0 Options. (line 220)
* msign-extend-enabled: LM32 Options. (line 18)
-* msim: Blackfin Options. (line 36)
-* msim <1>: C6X Options. (line 19)
-* msim <2>: CR16 Options. (line 18)
-* msim <3>: M32C Options. (line 13)
-* msim <4>: MeP Options. (line 114)
-* msim <5>: MSP430 Options. (line 39)
-* msim <6>: RL78 Options. (line 7)
-* msim <7>: RS/6000 and PowerPC Options.
- (line 680)
-* msim <8>: RX Options. (line 71)
-* msim <9>: Visium Options. (line 13)
-* msim <10>: Xstormy16 Options. (line 9)
+* msim <1>: Xstormy16 Options. (line 9)
+* msim <2>: Visium Options. (line 13)
+* msim <3>: RX Options. (line 71)
+* msim <4>: RS/6000 and PowerPC Options.
+ (line 682)
+* msim <5>: RL78 Options. (line 7)
+* msim <6>: MSP430 Options. (line 39)
+* msim <7>: MeP Options. (line 114)
+* msim <8>: M32C Options. (line 13)
+* msim <9>: CR16 Options. (line 18)
+* msim <10>: C6X Options. (line 19)
+* msim: Blackfin Options. (line 37)
* msimd: ARC Options. (line 71)
* msimnovec: MeP Options. (line 117)
* msimple-fpu: RS/6000 and PowerPC Options.
- (line 400)
-* msingle-exit: MMIX Options. (line 65)
-* msingle-float: MIPS Options. (line 282)
+ (line 402)
+* msingle-exit: MMIX Options. (line 66)
* msingle-float <1>: RS/6000 and PowerPC Options.
- (line 396)
-* msingle-pic-base: ARM Options. (line 219)
+ (line 398)
+* msingle-float: MIPS Options. (line 286)
* msingle-pic-base <1>: RS/6000 and PowerPC Options.
- (line 539)
+ (line 541)
+* msingle-pic-base: ARM Options. (line 220)
* msio: HPPA Options. (line 98)
-* msize-level: ARC Options. (line 281)
-* mskip-rax-setup: x86 Options. (line 918)
+* msize-level: ARC Options. (line 283)
+* mskip-rax-setup: x86 Options. (line 927)
* mslow-bytes: MCore Options. (line 35)
* mslow-flash-data: ARM Options. (line 344)
* msmall: MSP430 Options. (line 47)
@@ -50285,163 +50758,162 @@ look up both forms.
* msmall-data-limit: RX Options. (line 47)
* msmall-divides: MicroBlaze Options. (line 39)
* msmall-exec: S/390 and zSeries Options.
- (line 79)
-* msmall-mem: SPU Options. (line 38)
+ (line 80)
+* msmall-mem: SPU Options. (line 35)
* msmall-model: FR30 Options. (line 9)
* msmall-text: DEC Alpha Options. (line 205)
* msmall16: Adapteva Epiphany Options.
- (line 66)
-* msmallc: Nios II Options. (line 268)
-* msmartmips: MIPS Options. (line 364)
-* msoft-float: ARC Options. (line 75)
-* msoft-float <1>: DEC Alpha Options. (line 10)
-* msoft-float <2>: FRV Options. (line 27)
-* msoft-float <3>: HPPA Options. (line 84)
-* msoft-float <4>: M680x0 Options. (line 200)
-* msoft-float <5>: MicroBlaze Options. (line 7)
-* msoft-float <6>: MIPS Options. (line 268)
-* msoft-float <7>: PDP-11 Options. (line 13)
-* msoft-float <8>: RS/6000 and PowerPC Options.
- (line 390)
-* msoft-float <9>: S/390 and zSeries Options.
+ (line 67)
+* msmallc: Nios II Options. (line 272)
+* msmartmips: MIPS Options. (line 368)
+* msoft-float <1>: x86 Options. (line 347)
+* msoft-float <2>: Visium Options. (line 24)
+* msoft-float <3>: V850 Options. (line 113)
+* msoft-float <4>: SPARC Options. (line 40)
+* msoft-float <5>: S/390 and zSeries Options.
(line 11)
-* msoft-float <10>: SPARC Options. (line 39)
-* msoft-float <11>: V850 Options. (line 113)
-* msoft-float <12>: Visium Options. (line 24)
-* msoft-float <13>: x86 Options. (line 341)
-* msoft-quad-float: SPARC Options. (line 59)
-* msp8: AVR Options. (line 203)
+* msoft-float <6>: RS/6000 and PowerPC Options.
+ (line 392)
+* msoft-float <7>: PDP-11 Options. (line 13)
+* msoft-float <8>: MIPS Options. (line 272)
+* msoft-float <9>: MicroBlaze Options. (line 7)
+* msoft-float <10>: M680x0 Options. (line 203)
+* msoft-float <11>: HPPA Options. (line 84)
+* msoft-float <12>: FRV Options. (line 22)
+* msoft-float <13>: DEC Alpha Options. (line 10)
+* msoft-float: ARC Options. (line 75)
+* msoft-quad-float: SPARC Options. (line 60)
+* msp8: AVR Options. (line 202)
* mspace: V850 Options. (line 30)
* mspe: RS/6000 and PowerPC Options.
- (line 203)
-* mspecld-anomaly: Blackfin Options. (line 50)
+ (line 204)
+* mspecld-anomaly: Blackfin Options. (line 51)
* mspfp: ARC Options. (line 62)
* mspfp-compact: ARC Options. (line 63)
* mspfp-fast: ARC Options. (line 67)
-* mspfp_compact: ARC Options. (line 382)
-* mspfp_fast: ARC Options. (line 385)
-* msplit-addresses: MIPS Options. (line 531)
+* mspfp_compact: ARC Options. (line 384)
+* mspfp_fast: ARC Options. (line 387)
+* msplit-addresses: MIPS Options. (line 536)
* msplit-vecmove-early: Adapteva Epiphany Options.
- (line 126)
-* msse: x86 Options. (line 576)
-* msse2avx: x86 Options. (line 893)
-* msseregparm: x86 Options. (line 477)
+ (line 127)
+* msse: x86 Options. (line 582)
+* msse2avx: x86 Options. (line 902)
+* msseregparm: x86 Options. (line 483)
* mstack-align: CRIS Options. (line 55)
-* mstack-bias: SPARC Options. (line 313)
-* mstack-check-l1: Blackfin Options. (line 76)
+* mstack-bias: SPARC Options. (line 314)
+* mstack-check-l1: Blackfin Options. (line 77)
* mstack-guard: S/390 and zSeries Options.
- (line 154)
+ (line 156)
* mstack-increment: MCore Options. (line 50)
* mstack-offset: Adapteva Epiphany Options.
(line 37)
-* mstack-protector-guard=GUARD: x86 Options. (line 942)
+* mstack-protector-guard=GUARD: x86 Options. (line 951)
* mstack-size: S/390 and zSeries Options.
- (line 154)
-* mstackrealign: x86 Options. (line 520)
-* mstdmain: SPU Options. (line 44)
+ (line 156)
+* mstackrealign: x86 Options. (line 526)
+* mstdmain: SPU Options. (line 40)
+* mstrict-align <1>: RS/6000 and PowerPC Options.
+ (line 493)
+* mstrict-align <2>: M680x0 Options. (line 287)
* mstrict-align: AArch64 Options. (line 49)
-* mstrict-align <1>: M680x0 Options. (line 283)
-* mstrict-align <2>: RS/6000 and PowerPC Options.
- (line 491)
-* mstrict-X: AVR Options. (line 216)
+* mstrict-X: AVR Options. (line 215)
* mstring: RS/6000 and PowerPC Options.
- (line 427)
-* mstringop-strategy=ALG: x86 Options. (line 841)
-* mstructure-size-boundary: ARM Options. (line 176)
+ (line 429)
+* mstringop-strategy=ALG: x86 Options. (line 850)
+* mstructure-size-boundary: ARM Options. (line 177)
* msv-mode: Visium Options. (line 52)
* msvr4-struct-return: RS/6000 and PowerPC Options.
- (line 632)
+ (line 634)
* mswap: ARC Options. (line 82)
-* mswape: ARC Options. (line 114)
-* msym32: MIPS Options. (line 429)
-* msynci: MIPS Options. (line 783)
-* msys-crt0: Nios II Options. (line 272)
-* msys-lib: Nios II Options. (line 276)
+* mswape: ARC Options. (line 115)
+* msym32: MIPS Options. (line 433)
+* msynci: MIPS Options. (line 796)
+* msys-crt0: Nios II Options. (line 276)
+* msys-lib: Nios II Options. (line 280)
* MT: Preprocessor Options.
(line 251)
* mtarget-align: Xtensa Options. (line 59)
-* mtas: SH Options. (line 280)
-* mtbm: x86 Options. (line 615)
+* mtas: SH Options. (line 282)
+* mtbm: x86 Options. (line 621)
* mtda: V850 Options. (line 34)
-* mtelephony: ARC Options. (line 119)
+* mtelephony: ARC Options. (line 120)
* mtext-section-literals: Xtensa Options. (line 47)
* mtf: MeP Options. (line 121)
* mthread: x86 Windows Options.
(line 26)
-* mthreads: x86 Options. (line 818)
-* mthumb: ARM Options. (line 260)
+* mthreads: x86 Options. (line 826)
+* mthumb: ARM Options. (line 261)
* mthumb-interwork: ARM Options. (line 24)
-* mtiny-stack: AVR Options. (line 230)
+* mtiny-stack: AVR Options. (line 229)
* mtiny=: MeP Options. (line 125)
-* mTLS: FRV Options. (line 90)
-* mtls: FRV Options. (line 94)
+* mtls: FRV Options. (line 75)
+* mTLS: FRV Options. (line 72)
+* mtls-dialect <1>: x86 Options. (line 804)
* mtls-dialect: ARM Options. (line 302)
-* mtls-dialect <1>: x86 Options. (line 796)
* mtls-dialect=desc: AArch64 Options. (line 58)
* mtls-dialect=traditional: AArch64 Options. (line 62)
-* mtls-direct-seg-refs: x86 Options. (line 883)
+* mtls-direct-seg-refs: x86 Options. (line 892)
* mtls-markers: RS/6000 and PowerPC Options.
- (line 813)
+ (line 817)
* mtls-size: IA-64 Options. (line 112)
* mtoc: RS/6000 and PowerPC Options.
- (line 516)
-* mtomcat-stats: FRV Options. (line 254)
-* mtoplevel-symbols: MMIX Options. (line 39)
+ (line 518)
+* mtomcat-stats: FRV Options. (line 209)
+* mtoplevel-symbols: MMIX Options. (line 40)
* mtp: ARM Options. (line 294)
* mtpcs-frame: ARM Options. (line 267)
* mtpcs-leaf-frame: ARM Options. (line 273)
* mtpf-trace: S/390 and zSeries Options.
- (line 129)
+ (line 131)
* mtrap-precision: DEC Alpha Options. (line 109)
-* mtune: AArch64 Options. (line 90)
-* mtune <1>: ARC Options. (line 302)
-* mtune <2>: ARC Options. (line 388)
-* mtune <3>: ARM Options. (line 87)
-* mtune <4>: CRIS Options. (line 17)
-* mtune <5>: DEC Alpha Options. (line 259)
-* mtune <6>: IA-64 Options. (line 116)
-* mtune <7>: M680x0 Options. (line 68)
-* mtune <8>: MIPS Options. (line 64)
-* mtune <9>: MN10300 Options. (line 30)
-* mtune <10>: RS/6000 and PowerPC Options.
- (line 113)
-* mtune <11>: S/390 and zSeries Options.
- (line 122)
-* mtune <12>: SPARC Options. (line 180)
-* mtune <13>: Visium Options. (line 47)
-* mtune <14>: x86 Options. (line 222)
-* mtune-ctrl=FEATURE-LIST: x86 Options. (line 647)
-* mucb-mcount: ARC Options. (line 179)
+* mtune <1>: x86 Options. (line 227)
+* mtune <2>: Visium Options. (line 47)
+* mtune <3>: SPARC Options. (line 181)
+* mtune <4>: S/390 and zSeries Options.
+ (line 124)
+* mtune <5>: RS/6000 and PowerPC Options.
+ (line 114)
+* mtune <6>: MN10300 Options. (line 30)
+* mtune <7>: MIPS Options. (line 65)
+* mtune <8>: M680x0 Options. (line 70)
+* mtune <9>: IA-64 Options. (line 116)
+* mtune <10>: DEC Alpha Options. (line 259)
+* mtune <11>: CRIS Options. (line 16)
+* mtune <12>: ARM Options. (line 87)
+* mtune <13>: ARC Options. (line 305)
+* mtune: AArch64 Options. (line 96)
+* mtune-ctrl=FEATURE-LIST: x86 Options. (line 654)
+* mucb-mcount: ARC Options. (line 180)
* muclibc: GNU/Linux Options. (line 13)
* muls: Score Options. (line 18)
-* multcost: ARC Options. (line 393)
-* multcost=NUMBER: SH Options. (line 302)
-* multilib-library-pic: FRV Options. (line 110)
+* multcost: ARC Options. (line 395)
+* multcost=NUMBER: SH Options. (line 305)
+* multi_module: Darwin Options. (line 196)
+* multilib-library-pic: FRV Options. (line 89)
* multiply-enabled: LM32 Options. (line 15)
* multiply_defined: Darwin Options. (line 196)
* multiply_defined_unused: Darwin Options. (line 196)
-* multi_module: Darwin Options. (line 196)
-* munalign-prob-threshold: ARC Options. (line 330)
+* munalign-prob-threshold: ARC Options. (line 334)
* munaligned-access: ARM Options. (line 326)
-* munaligned-doubles: SPARC Options. (line 73)
+* munaligned-doubles: SPARC Options. (line 74)
* municode: x86 Windows Options.
(line 30)
-* muninit-const-in-rodata: MIPS Options. (line 501)
+* muninit-const-in-rodata: MIPS Options. (line 506)
* munix: VAX Options. (line 9)
* munix-asm: PDP-11 Options. (line 68)
-* munsafe-dma: SPU Options. (line 18)
+* munsafe-dma: SPU Options. (line 17)
* mupdate: RS/6000 and PowerPC Options.
- (line 438)
+ (line 440)
* mupper-regs: RS/6000 and PowerPC Options.
- (line 276)
+ (line 277)
* mupper-regs-df: RS/6000 and PowerPC Options.
- (line 260)
+ (line 261)
* mupper-regs-sf: RS/6000 and PowerPC Options.
- (line 268)
+ (line 269)
* muser-enabled: LM32 Options. (line 21)
-* muser-mode: SPARC Options. (line 85)
* muser-mode <1>: Visium Options. (line 57)
-* musermode: SH Options. (line 295)
+* muser-mode: SPARC Options. (line 86)
+* musermode: SH Options. (line 297)
* mv3push: NDS32 Options. (line 33)
* mv850: V850 Options. (line 49)
* mv850e: V850 Options. (line 79)
@@ -50451,33 +50923,33 @@ look up both forms.
* mv850e2v4: V850 Options. (line 57)
* mv850e3v5: V850 Options. (line 52)
* mv850es: V850 Options. (line 75)
-* mv8plus: SPARC Options. (line 194)
+* mv8plus: SPARC Options. (line 195)
+* mveclibabi <1>: x86 Options. (line 772)
* mveclibabi: RS/6000 and PowerPC Options.
- (line 891)
-* mveclibabi <1>: x86 Options. (line 764)
-* mvect8-ret-in-mem: x86 Options. (line 487)
-* mvirt: MIPS Options. (line 405)
-* mvis: SPARC Options. (line 201)
-* mvis2: SPARC Options. (line 207)
-* mvis3: SPARC Options. (line 215)
-* mvliw-branch: FRV Options. (line 201)
+ (line 896)
+* mvect8-ret-in-mem: x86 Options. (line 493)
+* mvirt: MIPS Options. (line 409)
+* mvis: SPARC Options. (line 202)
+* mvis2: SPARC Options. (line 208)
+* mvis3: SPARC Options. (line 216)
+* mvliw-branch: FRV Options. (line 164)
* mvms-return-codes: VMS Options. (line 9)
* mvolatile-asm-stop: IA-64 Options. (line 32)
-* mvolatile-cache: ARC Options. (line 184)
-* mvr4130-align: MIPS Options. (line 772)
+* mvolatile-cache: ARC Options. (line 185)
+* mvr4130-align: MIPS Options. (line 785)
* mvrsave: RS/6000 and PowerPC Options.
- (line 173)
+ (line 174)
* mvsx: RS/6000 and PowerPC Options.
- (line 217)
+ (line 218)
* mvxworks: RS/6000 and PowerPC Options.
- (line 701)
-* mvzeroupper: x86 Options. (line 674)
+ (line 703)
+* mvzeroupper: x86 Options. (line 682)
* mwarn-cell-microcode: RS/6000 and PowerPC Options.
- (line 179)
+ (line 180)
* mwarn-dynamicstack: S/390 and zSeries Options.
- (line 148)
+ (line 150)
* mwarn-framesize: S/390 and zSeries Options.
- (line 140)
+ (line 142)
* mwarn-multiple-fast-interrupts: RX Options. (line 143)
* mwarn-reloc: SPU Options. (line 10)
* mwide-bitfields: MCore Options. (line 23)
@@ -50486,14 +50958,14 @@ look up both forms.
* mwindows: x86 Windows Options.
(line 41)
* mword-relocations: ARM Options. (line 313)
-* mx32: x86 Options. (line 954)
-* mxgot: M680x0 Options. (line 315)
-* mxgot <1>: MIPS Options. (line 227)
+* mx32: x86 Options. (line 965)
+* mxgot <1>: MIPS Options. (line 231)
+* mxgot: M680x0 Options. (line 319)
* mxilinx-fpu: RS/6000 and PowerPC Options.
- (line 411)
+ (line 413)
* mxl-barrel-shift: MicroBlaze Options. (line 33)
* mxl-compat: RS/6000 and PowerPC Options.
- (line 348)
+ (line 349)
* mxl-float-convert: MicroBlaze Options. (line 51)
* mxl-float-sqrt: MicroBlaze Options. (line 54)
* mxl-gp-opt: MicroBlaze Options. (line 45)
@@ -50503,28 +50975,29 @@ look up both forms.
* mxl-soft-div: MicroBlaze Options. (line 30)
* mxl-soft-mul: MicroBlaze Options. (line 27)
* mxl-stack-check: MicroBlaze Options. (line 42)
-* mxop: x86 Options. (line 601)
-* mxpa: MIPS Options. (line 410)
-* mxsave: x86 Options. (line 610)
-* mxsavec: x86 Options. (line 612)
-* mxsaveopt: x86 Options. (line 611)
-* mxsaves: x86 Options. (line 613)
-* mxy: ARC Options. (line 124)
+* mxop: x86 Options. (line 607)
+* mxpa: MIPS Options. (line 414)
+* mxsave: x86 Options. (line 616)
+* mxsavec: x86 Options. (line 618)
+* mxsaveopt: x86 Options. (line 617)
+* mxsaves: x86 Options. (line 619)
+* mxy: ARC Options. (line 125)
* myellowknife: RS/6000 and PowerPC Options.
- (line 696)
+ (line 698)
* mzarch: S/390 and zSeries Options.
- (line 94)
+ (line 95)
* mzda: V850 Options. (line 45)
-* mzdcbranch: SH Options. (line 465)
-* mzero-extend: MMIX Options. (line 26)
+* mzdcbranch: SH Options. (line 473)
+* mzero-extend: MMIX Options. (line 27)
* no-canonical-prefixes: Overall Options. (line 334)
* no-integrated-cpp: Preprocessor Options.
(line 34)
-* no-sysroot-suffix: Directory Options. (line 109)
+* no-sysroot-suffix: Directory Options. (line 111)
+* no_dead_strip_inits_and_terms: Darwin Options. (line 196)
* noall_load: Darwin Options. (line 196)
-* nocpp: MIPS Options. (line 605)
+* nocpp: MIPS Options. (line 611)
* nodefaultlibs: Link Options. (line 68)
-* nodevicelib: AVR Options. (line 233)
+* nodevicelib: AVR Options. (line 232)
* nofixprebinding: Darwin Options. (line 196)
* nofpu: RX Options. (line 17)
* nolibdld: HPPA Options. (line 181)
@@ -50534,615 +51007,602 @@ look up both forms.
* noseglinkedit: Darwin Options. (line 196)
* nostartfiles: Link Options. (line 63)
* nostdinc: Preprocessor Options.
- (line 401)
-* nostdinc++: C++ Dialect Options.
- (line 426)
+ (line 399)
* nostdinc++ <1>: Preprocessor Options.
- (line 406)
+ (line 404)
+* nostdinc++: C++ Dialect Options.
+ (line 428)
* nostdlib: Link Options. (line 80)
-* no_dead_strip_inits_and_terms: Darwin Options. (line 196)
-* o: Overall Options. (line 192)
-* O: Optimize Options. (line 39)
-* o <1>: Preprocessor Options.
+* o: Preprocessor Options.
(line 87)
+* O: Optimize Options. (line 39)
+* o: Overall Options. (line 192)
* O0: Optimize Options. (line 145)
* O1: Optimize Options. (line 39)
* O2: Optimize Options. (line 91)
* O3: Optimize Options. (line 136)
* Ofast: Optimize Options. (line 159)
-* Og: Optimize Options. (line 165)
+* Og: Optimize Options. (line 166)
* Os: Optimize Options. (line 149)
-* p: Debugging Options. (line 644)
* P: Preprocessor Options.
- (line 646)
+ (line 648)
+* p: Debugging Options. (line 639)
* pagezero_size: Darwin Options. (line 196)
-* param: Optimize Options. (line 2434)
+* param: Optimize Options. (line 2438)
* pass-exit-codes: Overall Options. (line 150)
-* pedantic: Standards. (line 16)
-* pedantic <1>: Warning Options. (line 80)
-* pedantic <2>: Preprocessor Options.
- (line 175)
+* pedantic <1>: Warnings and Errors.
+ (line 25)
+* pedantic <2>: Alternate Keywords. (line 30)
* pedantic <3>: C Extensions. (line 6)
-* pedantic <4>: Alternate Keywords. (line 30)
-* pedantic <5>: Warnings and Errors.
+* pedantic <4>: Preprocessor Options.
+ (line 175)
+* pedantic <5>: Warning Options. (line 82)
+* pedantic: Standards. (line 16)
+* pedantic-errors <1>: Warnings and Errors.
(line 25)
-* pedantic-errors: Standards. (line 16)
-* pedantic-errors <1>: Warning Options. (line 121)
-* pedantic-errors <2>: Preprocessor Options.
+* pedantic-errors <2>: Non-bugs. (line 216)
+* pedantic-errors <3>: Preprocessor Options.
(line 180)
-* pedantic-errors <3>: Non-bugs. (line 216)
-* pedantic-errors <4>: Warnings and Errors.
- (line 25)
-* pg: Debugging Options. (line 650)
+* pedantic-errors <4>: Warning Options. (line 124)
+* pedantic-errors: Standards. (line 16)
+* pg: Debugging Options. (line 645)
* pie: Link Options. (line 105)
* pipe: Overall Options. (line 215)
* prebind: Darwin Options. (line 196)
* prebind_all_twolevel_modules: Darwin Options. (line 196)
-* print-file-name: Debugging Options. (line 1583)
-* print-libgcc-file-name: Debugging Options. (line 1617)
-* print-multi-directory: Debugging Options. (line 1589)
-* print-multi-lib: Debugging Options. (line 1594)
-* print-multi-os-directory: Debugging Options. (line 1601)
-* print-multiarch: Debugging Options. (line 1610)
+* print-file-name: Debugging Options. (line 1607)
+* print-libgcc-file-name: Debugging Options. (line 1641)
+* print-multi-directory: Debugging Options. (line 1613)
+* print-multi-lib: Debugging Options. (line 1618)
+* print-multi-os-directory: Debugging Options. (line 1625)
+* print-multiarch: Debugging Options. (line 1634)
* print-objc-runtime-info: Objective-C and Objective-C++ Dialect Options.
(line 217)
-* print-prog-name: Debugging Options. (line 1614)
-* print-search-dirs: Debugging Options. (line 1625)
-* print-sysroot: Debugging Options. (line 1638)
-* print-sysroot-headers-suffix: Debugging Options. (line 1645)
+* print-prog-name: Debugging Options. (line 1638)
+* print-search-dirs: Debugging Options. (line 1649)
+* print-sysroot: Debugging Options. (line 1662)
+* print-sysroot-headers-suffix: Debugging Options. (line 1669)
* private_bundle: Darwin Options. (line 196)
+* pthread <1>: Solaris 2 Options. (line 38)
* pthread: RS/6000 and PowerPC Options.
- (line 820)
-* pthread <1>: Solaris 2 Options. (line 36)
-* pthreads: Solaris 2 Options. (line 30)
-* Q: Debugging Options. (line 656)
+ (line 824)
+* pthreads: Solaris 2 Options. (line 32)
+* Q: Debugging Options. (line 651)
* Qn: System V Options. (line 18)
* Qy: System V Options. (line 14)
* rdynamic: Link Options. (line 111)
* read_only_relocs: Darwin Options. (line 196)
* remap: Preprocessor Options.
- (line 693)
-* S: Overall Options. (line 175)
-* S <1>: Link Options. (line 20)
+ (line 696)
* s: Link Options. (line 118)
-* save-temps: Debugging Options. (line 1490)
-* save-temps=obj: Debugging Options. (line 1516)
+* S <1>: Link Options. (line 20)
+* S: Overall Options. (line 175)
+* save-temps: Debugging Options. (line 1514)
+* save-temps=obj: Debugging Options. (line 1540)
* sectalign: Darwin Options. (line 196)
* sectcreate: Darwin Options. (line 196)
* sectobjectsymbols: Darwin Options. (line 196)
-* sectobjectsymbols <1>: Darwin Options. (line 196)
* sectorder: Darwin Options. (line 196)
* seg1addr: Darwin Options. (line 196)
+* seg_addr_table: Darwin Options. (line 196)
+* seg_addr_table_filename: Darwin Options. (line 196)
* segaddr: Darwin Options. (line 196)
* seglinkedit: Darwin Options. (line 196)
* segprot: Darwin Options. (line 196)
* segs_read_only_addr: Darwin Options. (line 196)
-* segs_read_only_addr <1>: Darwin Options. (line 196)
* segs_read_write_addr: Darwin Options. (line 196)
-* segs_read_write_addr <1>: Darwin Options. (line 196)
-* seg_addr_table: Darwin Options. (line 196)
-* seg_addr_table_filename: Darwin Options. (line 196)
-* shared: Link Options. (line 126)
-* shared-libgcc: Link Options. (line 134)
+* shared: Link Options. (line 127)
+* shared-libgcc: Link Options. (line 135)
* short-calls: Adapteva Epiphany Options.
(line 61)
* sim: CRIS Options. (line 95)
* sim2: CRIS Options. (line 101)
* single_module: Darwin Options. (line 196)
-* specs: Directory Options. (line 86)
+* specs: Directory Options. (line 88)
+* static <1>: HPPA Options. (line 185)
+* static <2>: Darwin Options. (line 196)
* static: Link Options. (line 122)
-* static <1>: Darwin Options. (line 196)
-* static <2>: HPPA Options. (line 185)
-* static-libasan: Link Options. (line 169)
-* static-libgcc: Link Options. (line 134)
-* static-liblsan: Link Options. (line 185)
-* static-libmpx: Link Options. (line 202)
-* static-libmpxwrappers: Link Options. (line 211)
-* static-libstdc++: Link Options. (line 221)
-* static-libtsan: Link Options. (line 177)
-* static-libubsan: Link Options. (line 193)
+* static-libasan: Link Options. (line 170)
+* static-libgcc: Link Options. (line 135)
+* static-liblsan: Link Options. (line 188)
+* static-libmpx: Link Options. (line 206)
+* static-libmpxwrappers: Link Options. (line 215)
+* static-libstdc++: Link Options. (line 225)
+* static-libtsan: Link Options. (line 179)
+* static-libubsan: Link Options. (line 197)
+* std <1>: Non-bugs. (line 107)
+* std <2>: Other Builtins. (line 22)
+* std <3>: C Dialect Options. (line 47)
* std: Standards. (line 16)
-* std <1>: C Dialect Options. (line 46)
-* std <2>: Other Builtins. (line 21)
-* std <3>: Non-bugs. (line 107)
* std=: Preprocessor Options.
- (line 340)
+ (line 338)
* sub_library: Darwin Options. (line 196)
* sub_umbrella: Darwin Options. (line 196)
-* symbolic: Link Options. (line 232)
-* sysroot: Directory Options. (line 94)
-* T: Link Options. (line 238)
-* target-help: Overall Options. (line 230)
+* symbolic: Link Options. (line 236)
+* sysroot: Directory Options. (line 96)
+* T: Link Options. (line 242)
* target-help <1>: Preprocessor Options.
- (line 698)
+ (line 701)
+* target-help: Overall Options. (line 230)
* threads: HPPA Options. (line 198)
-* time: Debugging Options. (line 1531)
+* time: Debugging Options. (line 1555)
* tno-android-cc: GNU/Linux Options. (line 31)
* tno-android-ld: GNU/Linux Options. (line 35)
-* traditional: C Dialect Options. (line 347)
* traditional <1>: Incompatibilities. (line 6)
-* traditional-cpp: C Dialect Options. (line 347)
+* traditional: C Dialect Options. (line 346)
* traditional-cpp <1>: Preprocessor Options.
- (line 676)
-* trigraphs: C Dialect Options. (line 342)
+ (line 679)
+* traditional-cpp: C Dialect Options. (line 346)
* trigraphs <1>: Preprocessor Options.
- (line 680)
+ (line 683)
+* trigraphs: C Dialect Options. (line 341)
* twolevel_namespace: Darwin Options. (line 196)
+* u: Link Options. (line 274)
* U: Preprocessor Options.
(line 69)
-* u: Link Options. (line 270)
* umbrella: Darwin Options. (line 196)
* undef: Preprocessor Options.
(line 73)
* undefined: Darwin Options. (line 196)
* unexported_symbols_list: Darwin Options. (line 196)
-* v: Overall Options. (line 203)
* v <1>: Preprocessor Options.
- (line 702)
-* version: Overall Options. (line 338)
+ (line 705)
+* v: Overall Options. (line 203)
* version <1>: Preprocessor Options.
- (line 714)
-* w: Warning Options. (line 25)
-* W: Warning Options. (line 181)
-* W <1>: Warning Options. (line 1437)
-* W <2>: Warning Options. (line 1533)
-* w <1>: Preprocessor Options.
+ (line 718)
+* version: Overall Options. (line 338)
+* W: Incompatibilities. (line 64)
+* w: Preprocessor Options.
(line 171)
-* W <3>: Incompatibilities. (line 64)
+* W: Warning Options. (line 183)
+* w: Warning Options. (line 25)
* Wa: Assembler Options. (line 9)
* Wabi: C++ Dialect Options.
- (line 434)
+ (line 436)
* Wabi-tag: C++ Dialect Options.
- (line 517)
-* Waddr-space-convert: AVR Options. (line 236)
-* Waddress: Warning Options. (line 1339)
-* Waggregate-return: Warning Options. (line 1372)
-* Waggressive-loop-optimizations: Warning Options. (line 1377)
-* Wall: Warning Options. (line 130)
-* Wall <1>: Preprocessor Options.
+ (line 521)
+* Waddr-space-convert: AVR Options. (line 235)
+* Waddress: Warning Options. (line 1353)
+* Waggregate-return: Warning Options. (line 1386)
+* Waggressive-loop-optimizations: Warning Options. (line 1391)
+* Wall <1>: Standard Libraries. (line 6)
+* Wall <2>: Preprocessor Options.
(line 93)
-* Wall <2>: Standard Libraries. (line 6)
-* Warray-bounds: Warning Options. (line 887)
+* Wall: Warning Options. (line 133)
+* Warray-bounds: Warning Options. (line 895)
* Wassign-intercept: Objective-C and Objective-C++ Dialect Options.
(line 171)
-* Wattributes: Warning Options. (line 1382)
-* Wbad-function-cast: Warning Options. (line 1149)
-* Wbool-compare: Warning Options. (line 903)
-* Wbuiltin-macro-redefined: Warning Options. (line 1388)
-* Wc++-compat: Warning Options. (line 1169)
-* Wc++11-compat: Warning Options. (line 1174)
-* Wc++14-compat: Warning Options. (line 1180)
-* Wc90-c99-compat: Warning Options. (line 1154)
-* Wc99-c11-compat: Warning Options. (line 1161)
-* Wcast-align: Warning Options. (line 1200)
-* Wcast-qual: Warning Options. (line 1184)
-* Wchar-subscripts: Warning Options. (line 220)
-* Wclobbered: Warning Options. (line 1219)
-* Wcomment: Warning Options. (line 225)
+* Wattributes: Warning Options. (line 1396)
+* Wbad-function-cast: Warning Options. (line 1160)
+* Wbool-compare: Warning Options. (line 911)
+* Wbuiltin-macro-redefined: Warning Options. (line 1402)
+* Wc++-compat: Warning Options. (line 1182)
+* Wc++11-compat: Warning Options. (line 1187)
+* Wc++14-compat: Warning Options. (line 1193)
+* Wc90-c99-compat: Warning Options. (line 1165)
+* Wc99-c11-compat: Warning Options. (line 1173)
+* Wcast-align: Warning Options. (line 1213)
+* Wcast-qual: Warning Options. (line 1197)
+* Wchar-subscripts: Warning Options. (line 222)
+* Wclobbered: Warning Options. (line 1233)
* Wcomment <1>: Preprocessor Options.
(line 101)
+* Wcomment: Warning Options. (line 227)
* Wcomments: Preprocessor Options.
(line 101)
-* Wconditionally-supported: Warning Options. (line 1223)
-* Wconversion: Warning Options. (line 1226)
-* Wconversion-null: Warning Options. (line 1244)
+* Wconditionally-supported: Warning Options. (line 1237)
+* Wconversion: Warning Options. (line 1240)
+* Wconversion-null: Warning Options. (line 1258)
* Wctor-dtor-privacy: C++ Dialect Options.
- (line 522)
-* Wdate-time: Warning Options. (line 1252)
-* Wdeclaration-after-statement: Warning Options. (line 1062)
-* Wdelete-incomplete: Warning Options. (line 1257)
+ (line 526)
+* Wdate-time: Warning Options. (line 1266)
+* Wdeclaration-after-statement: Warning Options. (line 1071)
+* Wdelete-incomplete: Warning Options. (line 1271)
* Wdelete-non-virtual-dtor: C++ Dialect Options.
- (line 529)
-* Wdeprecated: Warning Options. (line 1510)
-* Wdeprecated-declarations: Warning Options. (line 1514)
-* Wdisabled-optimization: Warning Options. (line 1677)
-* Wdiscarded-array-qualifiers: Warning Options. (line 918)
-* Wdiscarded-qualifiers: Warning Options. (line 912)
-* Wdiv-by-zero: Warning Options. (line 936)
-* Wdouble-promotion: Warning Options. (line 249)
+ (line 533)
+* Wdeprecated: Warning Options. (line 1525)
+* Wdeprecated-declarations: Warning Options. (line 1529)
+* Wdisabled-optimization: Warning Options. (line 1693)
+* Wdiscarded-array-qualifiers: Warning Options. (line 926)
+* Wdiscarded-qualifiers: Warning Options. (line 920)
+* Wdiv-by-zero: Warning Options. (line 944)
+* Wdouble-promotion: Warning Options. (line 251)
* weak_reference_mismatches: Darwin Options. (line 196)
* Weffc++: C++ Dialect Options.
- (line 609)
-* Wempty-body: Warning Options. (line 1264)
-* Wendif-labels: Warning Options. (line 1071)
+ (line 613)
+* Wempty-body: Warning Options. (line 1278)
* Wendif-labels <1>: Preprocessor Options.
(line 148)
-* Wenum-compare: Warning Options. (line 1268)
-* Werror: Warning Options. (line 28)
+* Wendif-labels: Warning Options. (line 1080)
+* Wenum-compare: Warning Options. (line 1282)
* Werror <1>: Preprocessor Options.
(line 161)
+* Werror: Warning Options. (line 28)
* Werror=: Warning Options. (line 31)
-* Wextra: Warning Options. (line 181)
-* Wextra <1>: Warning Options. (line 1437)
-* Wextra <2>: Warning Options. (line 1533)
+* Wextra: Warning Options. (line 183)
* Wfatal-errors: Warning Options. (line 48)
-* Wfloat-conversion: Warning Options. (line 1298)
-* Wfloat-equal: Warning Options. (line 962)
-* Wformat: Warning Options. (line 268)
-* Wformat <1>: Warning Options. (line 293)
-* Wformat <2>: Warning Options. (line 842)
-* Wformat <3>: Function Attributes.
- (line 420)
-* Wformat-contains-nul: Warning Options. (line 302)
-* Wformat-extra-args: Warning Options. (line 306)
-* Wformat-nonliteral: Warning Options. (line 330)
+* Wfloat-conversion: Warning Options. (line 1312)
+* Wfloat-equal: Warning Options. (line 970)
+* Wformat <1>: Function Attributes.
+ (line 424)
+* Wformat: Warning Options. (line 270)
+* Wformat-contains-nul: Warning Options. (line 307)
+* Wformat-extra-args: Warning Options. (line 311)
* Wformat-nonliteral <1>: Function Attributes.
- (line 485)
-* Wformat-security: Warning Options. (line 335)
-* Wformat-signedness: Warning Options. (line 347)
-* Wformat-y2k: Warning Options. (line 352)
-* Wformat-zero-length: Warning Options. (line 320)
-* Wformat=: Warning Options. (line 268)
-* Wformat=1: Warning Options. (line 293)
-* Wformat=2: Warning Options. (line 325)
-* Wframe-larger-than: Warning Options. (line 1090)
-* Wfree-nonheap-object: Warning Options. (line 1099)
+ (line 490)
+* Wformat-nonliteral: Warning Options. (line 335)
+* Wformat-security: Warning Options. (line 340)
+* Wformat-signedness: Warning Options. (line 352)
+* Wformat-y2k: Warning Options. (line 357)
+* Wformat-zero-length: Warning Options. (line 325)
+* Wformat=: Warning Options. (line 270)
+* Wformat=1: Warning Options. (line 297)
+* Wformat=2: Warning Options. (line 330)
+* Wframe-larger-than: Warning Options. (line 1099)
+* Wfree-nonheap-object: Warning Options. (line 1108)
* whatsloaded: Darwin Options. (line 196)
* whyload: Darwin Options. (line 196)
-* Wignored-qualifiers: Warning Options. (line 392)
-* Wimplicit: Warning Options. (line 388)
-* Wimplicit-function-declaration: Warning Options. (line 382)
-* Wimplicit-int: Warning Options. (line 378)
-* Wincompatible-pointer-types: Warning Options. (line 924)
-* Winherited-variadic-ctor: Warning Options. (line 1589)
-* Winit-self: Warning Options. (line 363)
-* Winline: Warning Options. (line 1594)
+* Wignored-qualifiers: Warning Options. (line 397)
+* Wimplicit: Warning Options. (line 393)
+* Wimplicit-function-declaration: Warning Options. (line 387)
+* Wimplicit-int: Warning Options. (line 383)
+* Wincompatible-pointer-types: Warning Options. (line 932)
+* Winherited-variadic-ctor: Warning Options. (line 1605)
+* Winit-self: Warning Options. (line 368)
* Winline <1>: Inline. (line 63)
-* Wint-conversion: Warning Options. (line 930)
-* Wint-to-pointer-cast: Warning Options. (line 1619)
-* Winvalid-offsetof: Warning Options. (line 1607)
-* Winvalid-pch: Warning Options. (line 1628)
-* Wjump-misses-init: Warning Options. (line 1274)
-* Wl: Link Options. (line 262)
-* Wlarger-than-LEN: Warning Options. (line 1087)
-* Wlarger-than=LEN: Warning Options. (line 1087)
+* Winline: Warning Options. (line 1610)
+* Wint-conversion: Warning Options. (line 938)
+* Wint-to-pointer-cast: Warning Options. (line 1635)
+* Winvalid-offsetof: Warning Options. (line 1623)
+* Winvalid-pch: Warning Options. (line 1644)
+* Wjump-misses-init: Warning Options. (line 1288)
+* Wl: Link Options. (line 266)
+* Wlarger-than-LEN: Warning Options. (line 1096)
+* Wlarger-than=LEN: Warning Options. (line 1096)
* Wliteral-suffix: C++ Dialect Options.
- (line 536)
-* Wlogical-not-parentheses: Warning Options. (line 1357)
-* Wlogical-op: Warning Options. (line 1352)
-* Wlong-long: Warning Options. (line 1632)
-* Wmain: Warning Options. (line 403)
-* Wmaybe-uninitialized: Warning Options. (line 679)
-* Wmemset-transposed-args: Warning Options. (line 1328)
-* Wmissing-braces: Warning Options. (line 410)
-* Wmissing-declarations: Warning Options. (line 1427)
-* Wmissing-field-initializers: Warning Options. (line 1437)
-* Wmissing-format-attribute: Warning Options. (line 842)
-* Wmissing-include-dirs: Warning Options. (line 421)
-* Wmissing-parameter-type: Warning Options. (line 1409)
-* Wmissing-prototypes: Warning Options. (line 1417)
-* Wmultichar: Warning Options. (line 1461)
+ (line 540)
+* Wlogical-not-parentheses: Warning Options. (line 1371)
+* Wlogical-op: Warning Options. (line 1366)
+* Wlong-long: Warning Options. (line 1648)
+* Wmain: Warning Options. (line 408)
+* Wmaybe-uninitialized: Warning Options. (line 686)
+* Wmemset-transposed-args: Warning Options. (line 1342)
+* Wmissing-braces: Warning Options. (line 415)
+* Wmissing-declarations: Warning Options. (line 1441)
+* Wmissing-field-initializers: Warning Options. (line 1451)
+* Wmissing-format-attribute: Warning Options. (line 850)
+* Wmissing-include-dirs: Warning Options. (line 426)
+* Wmissing-parameter-type: Warning Options. (line 1423)
+* Wmissing-prototypes: Warning Options. (line 1431)
+* Wmultichar: Warning Options. (line 1475)
* Wnarrowing: C++ Dialect Options.
- (line 557)
-* Wnested-externs: Warning Options. (line 1586)
+ (line 561)
+* Wnested-externs: Warning Options. (line 1602)
* Wno-abi: C++ Dialect Options.
- (line 434)
-* Wno-address: Warning Options. (line 1339)
-* Wno-aggregate-return: Warning Options. (line 1372)
-* Wno-aggressive-loop-optimizations: Warning Options. (line 1377)
-* Wno-all: Warning Options. (line 130)
-* Wno-array-bounds: Warning Options. (line 887)
+ (line 436)
+* Wno-address: Warning Options. (line 1353)
+* Wno-aggregate-return: Warning Options. (line 1386)
+* Wno-aggressive-loop-optimizations: Warning Options. (line 1391)
+* Wno-all: Warning Options. (line 133)
+* Wno-array-bounds: Warning Options. (line 895)
* Wno-assign-intercept: Objective-C and Objective-C++ Dialect Options.
(line 171)
-* Wno-attributes: Warning Options. (line 1382)
-* Wno-bad-function-cast: Warning Options. (line 1149)
-* Wno-bool-compare: Warning Options. (line 903)
-* Wno-builtin-macro-redefined: Warning Options. (line 1388)
-* Wno-c90-c99-compat: Warning Options. (line 1154)
-* Wno-c99-c11-compat: Warning Options. (line 1161)
-* Wno-cast-align: Warning Options. (line 1200)
-* Wno-cast-qual: Warning Options. (line 1184)
-* Wno-char-subscripts: Warning Options. (line 220)
-* Wno-clobbered: Warning Options. (line 1219)
-* Wno-comment: Warning Options. (line 225)
-* Wno-conditionally-supported: Warning Options. (line 1223)
-* Wno-conversion: Warning Options. (line 1226)
-* Wno-conversion-null: Warning Options. (line 1244)
-* Wno-coverage-mismatch: Warning Options. (line 230)
+* Wno-attributes: Warning Options. (line 1396)
+* Wno-bad-function-cast: Warning Options. (line 1160)
+* Wno-bool-compare: Warning Options. (line 911)
+* Wno-builtin-macro-redefined: Warning Options. (line 1402)
+* Wno-c90-c99-compat: Warning Options. (line 1165)
+* Wno-c99-c11-compat: Warning Options. (line 1173)
+* Wno-cast-align: Warning Options. (line 1213)
+* Wno-cast-qual: Warning Options. (line 1197)
+* Wno-char-subscripts: Warning Options. (line 222)
+* Wno-clobbered: Warning Options. (line 1233)
+* Wno-comment: Warning Options. (line 227)
+* Wno-conditionally-supported: Warning Options. (line 1237)
+* Wno-conversion: Warning Options. (line 1240)
+* Wno-conversion-null: Warning Options. (line 1258)
+* Wno-coverage-mismatch: Warning Options. (line 232)
* Wno-ctor-dtor-privacy: C++ Dialect Options.
- (line 522)
-* Wno-date-time: Warning Options. (line 1252)
-* Wno-declaration-after-statement: Warning Options. (line 1062)
-* Wno-delete-incomplete: Warning Options. (line 1257)
+ (line 526)
+* Wno-date-time: Warning Options. (line 1266)
+* Wno-declaration-after-statement: Warning Options. (line 1071)
+* Wno-delete-incomplete: Warning Options. (line 1271)
* Wno-delete-non-virtual-dtor: C++ Dialect Options.
- (line 529)
-* Wno-deprecated: Warning Options. (line 1510)
-* Wno-deprecated-declarations: Warning Options. (line 1514)
-* Wno-disabled-optimization: Warning Options. (line 1677)
-* Wno-discarded-array-qualifiers: Warning Options. (line 918)
-* Wno-discarded-qualifiers: Warning Options. (line 912)
-* Wno-div-by-zero: Warning Options. (line 936)
-* Wno-double-promotion: Warning Options. (line 249)
+ (line 533)
+* Wno-deprecated: Warning Options. (line 1525)
+* Wno-deprecated-declarations: Warning Options. (line 1529)
+* Wno-disabled-optimization: Warning Options. (line 1693)
+* Wno-discarded-array-qualifiers: Warning Options. (line 926)
+* Wno-discarded-qualifiers: Warning Options. (line 920)
+* Wno-div-by-zero: Warning Options. (line 944)
+* Wno-double-promotion: Warning Options. (line 251)
* Wno-effc++: C++ Dialect Options.
- (line 609)
-* Wno-empty-body: Warning Options. (line 1264)
-* Wno-endif-labels: Warning Options. (line 1071)
-* Wno-enum-compare: Warning Options. (line 1268)
+ (line 613)
+* Wno-empty-body: Warning Options. (line 1278)
+* Wno-endif-labels: Warning Options. (line 1080)
+* Wno-enum-compare: Warning Options. (line 1282)
* Wno-error: Warning Options. (line 28)
* Wno-error=: Warning Options. (line 31)
-* Wno-extra: Warning Options. (line 181)
-* Wno-extra <1>: Warning Options. (line 1437)
-* Wno-extra <2>: Warning Options. (line 1533)
+* Wno-extra: Warning Options. (line 183)
* Wno-fatal-errors: Warning Options. (line 48)
-* Wno-float-conversion: Warning Options. (line 1298)
-* Wno-float-equal: Warning Options. (line 962)
-* Wno-format: Warning Options. (line 268)
-* Wno-format <1>: Warning Options. (line 842)
-* Wno-format-contains-nul: Warning Options. (line 302)
-* Wno-format-extra-args: Warning Options. (line 306)
-* Wno-format-nonliteral: Warning Options. (line 330)
-* Wno-format-security: Warning Options. (line 335)
-* Wno-format-signedness: Warning Options. (line 347)
-* Wno-format-y2k: Warning Options. (line 352)
-* Wno-format-zero-length: Warning Options. (line 320)
-* Wno-free-nonheap-object: Warning Options. (line 1099)
-* Wno-ignored-qualifiers: Warning Options. (line 392)
-* Wno-implicit: Warning Options. (line 388)
-* Wno-implicit-function-declaration: Warning Options. (line 382)
-* Wno-implicit-int: Warning Options. (line 378)
-* Wno-incompatible-pointer-types: Warning Options. (line 924)
-* Wno-inherited-variadic-ctor: Warning Options. (line 1589)
-* Wno-init-self: Warning Options. (line 363)
-* Wno-inline: Warning Options. (line 1594)
-* Wno-int-conversion: Warning Options. (line 930)
-* Wno-int-to-pointer-cast: Warning Options. (line 1619)
-* Wno-invalid-offsetof: Warning Options. (line 1607)
-* Wno-invalid-pch: Warning Options. (line 1628)
-* Wno-jump-misses-init: Warning Options. (line 1274)
+* Wno-float-conversion: Warning Options. (line 1312)
+* Wno-float-equal: Warning Options. (line 970)
+* Wno-format: Warning Options. (line 270)
+* Wno-format-contains-nul: Warning Options. (line 307)
+* Wno-format-extra-args: Warning Options. (line 311)
+* Wno-format-nonliteral: Warning Options. (line 335)
+* Wno-format-security: Warning Options. (line 340)
+* Wno-format-signedness: Warning Options. (line 352)
+* Wno-format-y2k: Warning Options. (line 357)
+* Wno-format-zero-length: Warning Options. (line 325)
+* Wno-free-nonheap-object: Warning Options. (line 1108)
+* Wno-ignored-qualifiers: Warning Options. (line 397)
+* Wno-implicit: Warning Options. (line 393)
+* Wno-implicit-function-declaration: Warning Options. (line 387)
+* Wno-implicit-int: Warning Options. (line 383)
+* Wno-incompatible-pointer-types: Warning Options. (line 932)
+* Wno-inherited-variadic-ctor: Warning Options. (line 1605)
+* Wno-init-self: Warning Options. (line 368)
+* Wno-inline: Warning Options. (line 1610)
+* Wno-int-conversion: Warning Options. (line 938)
+* Wno-int-to-pointer-cast: Warning Options. (line 1635)
+* Wno-invalid-offsetof: Warning Options. (line 1623)
+* Wno-invalid-pch: Warning Options. (line 1644)
+* Wno-jump-misses-init: Warning Options. (line 1288)
* Wno-literal-suffix: C++ Dialect Options.
- (line 536)
-* Wno-logical-not-parentheses: Warning Options. (line 1357)
-* Wno-logical-op: Warning Options. (line 1352)
-* Wno-long-long: Warning Options. (line 1632)
-* Wno-main: Warning Options. (line 403)
-* Wno-maybe-uninitialized: Warning Options. (line 679)
-* Wno-memset-transposed-args: Warning Options. (line 1328)
-* Wno-missing-braces: Warning Options. (line 410)
-* Wno-missing-declarations: Warning Options. (line 1427)
-* Wno-missing-field-initializers: Warning Options. (line 1437)
-* Wno-missing-format-attribute: Warning Options. (line 842)
-* Wno-missing-include-dirs: Warning Options. (line 421)
-* Wno-missing-parameter-type: Warning Options. (line 1409)
-* Wno-missing-prototypes: Warning Options. (line 1417)
-* Wno-multichar: Warning Options. (line 1461)
+ (line 540)
+* Wno-logical-not-parentheses: Warning Options. (line 1371)
+* Wno-logical-op: Warning Options. (line 1366)
+* Wno-long-long: Warning Options. (line 1648)
+* Wno-main: Warning Options. (line 408)
+* Wno-maybe-uninitialized: Warning Options. (line 686)
+* Wno-memset-transposed-args: Warning Options. (line 1342)
+* Wno-missing-braces: Warning Options. (line 415)
+* Wno-missing-declarations: Warning Options. (line 1441)
+* Wno-missing-field-initializers: Warning Options. (line 1451)
+* Wno-missing-format-attribute: Warning Options. (line 850)
+* Wno-missing-include-dirs: Warning Options. (line 426)
+* Wno-missing-parameter-type: Warning Options. (line 1423)
+* Wno-missing-prototypes: Warning Options. (line 1431)
+* Wno-multichar: Warning Options. (line 1475)
* Wno-narrowing: C++ Dialect Options.
- (line 557)
-* Wno-nested-externs: Warning Options. (line 1586)
+ (line 561)
+* Wno-nested-externs: Warning Options. (line 1602)
* Wno-noexcept: C++ Dialect Options.
- (line 570)
+ (line 574)
* Wno-non-template-friend: C++ Dialect Options.
- (line 644)
+ (line 650)
* Wno-non-virtual-dtor: C++ Dialect Options.
- (line 576)
-* Wno-nonnull: Warning Options. (line 356)
-* Wno-normalized: Warning Options. (line 1467)
-* Wno-odr: Warning Options. (line 1523)
+ (line 580)
+* Wno-nonnull: Warning Options. (line 361)
+* Wno-normalized: Warning Options. (line 1481)
+* Wno-odr: Warning Options. (line 1538)
* Wno-old-style-cast: C++ Dialect Options.
- (line 660)
-* Wno-old-style-declaration: Warning Options. (line 1399)
-* Wno-old-style-definition: Warning Options. (line 1405)
-* Wno-overflow: Warning Options. (line 1520)
-* Wno-overlength-strings: Warning Options. (line 1697)
-* Wno-overloaded-virtual: C++ Dialect Options.
(line 666)
-* Wno-override-init: Warning Options. (line 1533)
-* Wno-packed: Warning Options. (line 1541)
-* Wno-packed-bitfield-compat: Warning Options. (line 1558)
-* Wno-padded: Warning Options. (line 1575)
-* Wno-parentheses: Warning Options. (line 424)
-* Wno-pedantic-ms-format: Warning Options. (line 1129)
-* Wno-pmf-conversions: C++ Dialect Options.
- (line 685)
+* Wno-old-style-declaration: Warning Options. (line 1413)
+* Wno-old-style-definition: Warning Options. (line 1419)
+* Wno-overflow: Warning Options. (line 1535)
+* Wno-overlength-strings: Warning Options. (line 1713)
+* Wno-overloaded-virtual: C++ Dialect Options.
+ (line 672)
+* Wno-override-init: Warning Options. (line 1548)
+* Wno-packed: Warning Options. (line 1556)
+* Wno-packed-bitfield-compat: Warning Options. (line 1573)
+* Wno-padded: Warning Options. (line 1590)
+* Wno-parentheses: Warning Options. (line 429)
+* Wno-pedantic-ms-format: Warning Options. (line 1140)
* Wno-pmf-conversions <1>: Bound member functions.
(line 35)
-* Wno-pointer-arith: Warning Options. (line 1135)
-* Wno-pointer-sign: Warning Options. (line 1686)
-* Wno-pointer-to-int-cast: Warning Options. (line 1624)
-* Wno-pragmas: Warning Options. (line 729)
+* Wno-pmf-conversions: C++ Dialect Options.
+ (line 691)
+* Wno-pointer-arith: Warning Options. (line 1146)
+* Wno-pointer-sign: Warning Options. (line 1702)
+* Wno-pointer-to-int-cast: Warning Options. (line 1640)
+* Wno-pragmas: Warning Options. (line 736)
* Wno-protocol: Objective-C and Objective-C++ Dialect Options.
(line 175)
-* Wno-redundant-decls: Warning Options. (line 1582)
+* Wno-redundant-decls: Warning Options. (line 1597)
* Wno-reorder: C++ Dialect Options.
- (line 584)
-* Wno-return-local-addr: Warning Options. (line 519)
-* Wno-return-type: Warning Options. (line 523)
+ (line 588)
+* Wno-return-local-addr: Warning Options. (line 524)
+* Wno-return-type: Warning Options. (line 528)
* Wno-selector: Objective-C and Objective-C++ Dialect Options.
(line 185)
-* Wno-sequence-point: Warning Options. (line 473)
-* Wno-shadow: Warning Options. (line 1075)
-* Wno-shadow-ivar: Warning Options. (line 1083)
-* Wno-shift-count-negative: Warning Options. (line 537)
-* Wno-shift-count-overflow: Warning Options. (line 541)
-* Wno-sign-compare: Warning Options. (line 1285)
-* Wno-sign-conversion: Warning Options. (line 1292)
+* Wno-sequence-point: Warning Options. (line 478)
+* Wno-shadow: Warning Options. (line 1084)
+* Wno-shadow-ivar: Warning Options. (line 1092)
+* Wno-shift-count-negative: Warning Options. (line 543)
+* Wno-shift-count-overflow: Warning Options. (line 547)
+* Wno-sign-compare: Warning Options. (line 1299)
+* Wno-sign-conversion: Warning Options. (line 1306)
* Wno-sign-promo: C++ Dialect Options.
- (line 689)
-* Wno-sized-deallocation: Warning Options. (line 1304)
-* Wno-sizeof-array-argument: Warning Options. (line 1323)
-* Wno-sizeof-pointer-memaccess: Warning Options. (line 1315)
-* Wno-stack-protector: Warning Options. (line 1692)
-* Wno-strict-aliasing: Warning Options. (line 734)
+ (line 695)
+* Wno-sized-deallocation: Warning Options. (line 1318)
+* Wno-sizeof-array-argument: Warning Options. (line 1337)
+* Wno-sizeof-pointer-memaccess: Warning Options. (line 1329)
+* Wno-stack-protector: Warning Options. (line 1708)
+* Wno-strict-aliasing: Warning Options. (line 741)
* Wno-strict-null-sentinel: C++ Dialect Options.
- (line 637)
-* Wno-strict-overflow: Warning Options. (line 773)
-* Wno-strict-prototypes: Warning Options. (line 1393)
+ (line 642)
+* Wno-strict-overflow: Warning Options. (line 781)
+* Wno-strict-prototypes: Warning Options. (line 1407)
* Wno-strict-selector-match: Objective-C and Objective-C++ Dialect Options.
(line 197)
-* Wno-suggest-attribute=: Warning Options. (line 822)
-* Wno-suggest-attribute=const: Warning Options. (line 828)
-* Wno-suggest-attribute=format: Warning Options. (line 842)
-* Wno-suggest-attribute=noreturn: Warning Options. (line 828)
-* Wno-suggest-attribute=pure: Warning Options. (line 828)
-* Wno-suggest-final-methods: Warning Options. (line 872)
-* Wno-suggest-final-types: Warning Options. (line 863)
-* Wno-switch: Warning Options. (line 545)
-* Wno-switch-bool: Warning Options. (line 565)
-* Wno-switch-default: Warning Options. (line 553)
-* Wno-switch-enum: Warning Options. (line 556)
-* Wno-sync-nand: Warning Options. (line 575)
-* Wno-system-headers: Warning Options. (line 941)
-* Wno-traditional: Warning Options. (line 977)
-* Wno-traditional-conversion: Warning Options. (line 1054)
-* Wno-trampolines: Warning Options. (line 952)
-* Wno-trigraphs: Warning Options. (line 580)
-* Wno-type-limits: Warning Options. (line 1142)
+* Wno-suggest-attribute=: Warning Options. (line 831)
+* Wno-suggest-attribute=const: Warning Options. (line 837)
+* Wno-suggest-attribute=format: Warning Options. (line 850)
+* Wno-suggest-attribute=noreturn: Warning Options. (line 837)
+* Wno-suggest-attribute=pure: Warning Options. (line 837)
+* Wno-suggest-final-methods: Warning Options. (line 880)
+* Wno-suggest-final-types: Warning Options. (line 871)
+* Wno-switch: Warning Options. (line 551)
+* Wno-switch-bool: Warning Options. (line 571)
+* Wno-switch-default: Warning Options. (line 559)
+* Wno-switch-enum: Warning Options. (line 562)
+* Wno-sync-nand: Warning Options. (line 581)
+* Wno-system-headers: Warning Options. (line 949)
+* Wno-traditional: Warning Options. (line 985)
+* Wno-traditional-conversion: Warning Options. (line 1063)
+* Wno-trampolines: Warning Options. (line 960)
+* Wno-trigraphs: Warning Options. (line 586)
+* Wno-type-limits: Warning Options. (line 1153)
* Wno-undeclared-selector: Objective-C and Objective-C++ Dialect Options.
(line 205)
-* Wno-undef: Warning Options. (line 1068)
-* Wno-uninitialized: Warning Options. (line 657)
-* Wno-unknown-pragmas: Warning Options. (line 722)
-* Wno-unsafe-loop-optimizations: Warning Options. (line 1123)
-* Wno-unused: Warning Options. (line 650)
-* Wno-unused-but-set-parameter: Warning Options. (line 585)
-* Wno-unused-but-set-variable: Warning Options. (line 594)
-* Wno-unused-function: Warning Options. (line 604)
-* Wno-unused-label: Warning Options. (line 609)
-* Wno-unused-parameter: Warning Options. (line 620)
-* Wno-unused-result: Warning Options. (line 627)
-* Wno-unused-value: Warning Options. (line 640)
-* Wno-unused-variable: Warning Options. (line 632)
-* Wno-useless-cast: Warning Options. (line 1261)
-* Wno-varargs: Warning Options. (line 1643)
-* Wno-variadic-macros: Warning Options. (line 1637)
-* Wno-vector-operation-performance: Warning Options. (line 1648)
-* Wno-virtual-move-assign: Warning Options. (line 1658)
-* Wno-vla: Warning Options. (line 1667)
-* Wno-volatile-register-var: Warning Options. (line 1671)
-* Wno-write-strings: Warning Options. (line 1206)
-* Wno-zero-as-null-pointer-constant: Warning Options. (line 1248)
+* Wno-undef: Warning Options. (line 1077)
+* Wno-uninitialized: Warning Options. (line 663)
+* Wno-unknown-pragmas: Warning Options. (line 729)
+* Wno-unsafe-loop-optimizations: Warning Options. (line 1134)
+* Wno-unused: Warning Options. (line 656)
+* Wno-unused-but-set-parameter: Warning Options. (line 591)
+* Wno-unused-but-set-variable: Warning Options. (line 600)
+* Wno-unused-function: Warning Options. (line 610)
+* Wno-unused-label: Warning Options. (line 615)
+* Wno-unused-parameter: Warning Options. (line 626)
+* Wno-unused-result: Warning Options. (line 633)
+* Wno-unused-value: Warning Options. (line 646)
+* Wno-unused-variable: Warning Options. (line 638)
+* Wno-useless-cast: Warning Options. (line 1275)
+* Wno-varargs: Warning Options. (line 1659)
+* Wno-variadic-macros: Warning Options. (line 1653)
+* Wno-vector-operation-performance: Warning Options. (line 1664)
+* Wno-virtual-move-assign: Warning Options. (line 1674)
+* Wno-vla: Warning Options. (line 1683)
+* Wno-volatile-register-var: Warning Options. (line 1687)
+* Wno-write-strings: Warning Options. (line 1219)
+* Wno-zero-as-null-pointer-constant: Warning Options. (line 1262)
* Wnoexcept: C++ Dialect Options.
- (line 570)
+ (line 574)
* Wnon-template-friend: C++ Dialect Options.
- (line 644)
+ (line 650)
* Wnon-virtual-dtor: C++ Dialect Options.
- (line 576)
-* Wnonnull: Warning Options. (line 356)
-* Wnormalized: Warning Options. (line 1467)
-* Wnormalized=: Warning Options. (line 1467)
-* Wodr: Warning Options. (line 1523)
+ (line 580)
+* Wnonnull: Warning Options. (line 361)
+* Wnormalized: Warning Options. (line 1481)
+* Wnormalized=: Warning Options. (line 1481)
+* Wodr: Warning Options. (line 1538)
* Wold-style-cast: C++ Dialect Options.
- (line 660)
-* Wold-style-declaration: Warning Options. (line 1399)
-* Wold-style-definition: Warning Options. (line 1405)
-* Wopenm-simd: Warning Options. (line 1528)
-* Woverflow: Warning Options. (line 1520)
-* Woverlength-strings: Warning Options. (line 1697)
-* Woverloaded-virtual: C++ Dialect Options.
(line 666)
-* Woverride-init: Warning Options. (line 1533)
+* Wold-style-declaration: Warning Options. (line 1413)
+* Wold-style-definition: Warning Options. (line 1419)
+* Wopenm-simd: Warning Options. (line 1543)
+* Woverflow: Warning Options. (line 1535)
+* Woverlength-strings: Warning Options. (line 1713)
+* Woverloaded-virtual: C++ Dialect Options.
+ (line 672)
+* Woverride-init: Warning Options. (line 1548)
* Wp: Preprocessor Options.
(line 14)
-* Wpacked: Warning Options. (line 1541)
-* Wpacked-bitfield-compat: Warning Options. (line 1558)
-* Wpadded: Warning Options. (line 1575)
-* Wparentheses: Warning Options. (line 424)
-* Wpedantic: Warning Options. (line 80)
-* Wpedantic-ms-format: Warning Options. (line 1129)
+* Wpacked: Warning Options. (line 1556)
+* Wpacked-bitfield-compat: Warning Options. (line 1573)
+* Wpadded: Warning Options. (line 1590)
+* Wparentheses: Warning Options. (line 429)
+* Wpedantic: Warning Options. (line 82)
+* Wpedantic-ms-format: Warning Options. (line 1140)
* Wpmf-conversions: C++ Dialect Options.
- (line 685)
-* Wpointer-arith: Warning Options. (line 1135)
+ (line 691)
* Wpointer-arith <1>: Pointer Arith. (line 13)
-* Wpointer-sign: Warning Options. (line 1686)
-* Wpointer-to-int-cast: Warning Options. (line 1624)
-* Wpragmas: Warning Options. (line 729)
+* Wpointer-arith: Warning Options. (line 1146)
+* Wpointer-sign: Warning Options. (line 1702)
+* Wpointer-to-int-cast: Warning Options. (line 1640)
+* Wpragmas: Warning Options. (line 736)
* Wprotocol: Objective-C and Objective-C++ Dialect Options.
(line 175)
* wrapper: Overall Options. (line 341)
-* Wredundant-decls: Warning Options. (line 1582)
+* Wredundant-decls: Warning Options. (line 1597)
* Wreorder: C++ Dialect Options.
- (line 584)
-* Wreturn-local-addr: Warning Options. (line 519)
-* Wreturn-type: Warning Options. (line 523)
+ (line 588)
+* Wreturn-local-addr: Warning Options. (line 524)
+* Wreturn-type: Warning Options. (line 528)
* Wselector: Objective-C and Objective-C++ Dialect Options.
(line 185)
-* Wsequence-point: Warning Options. (line 473)
-* Wshadow: Warning Options. (line 1075)
-* Wshadow-ivar: Warning Options. (line 1083)
-* Wshift-count-negative: Warning Options. (line 537)
-* Wshift-count-overflow: Warning Options. (line 541)
-* Wsign-compare: Warning Options. (line 1285)
-* Wsign-conversion: Warning Options. (line 1292)
+* Wsequence-point: Warning Options. (line 478)
+* Wshadow: Warning Options. (line 1084)
+* Wshadow-ivar: Warning Options. (line 1092)
+* Wshift-count-negative: Warning Options. (line 543)
+* Wshift-count-overflow: Warning Options. (line 547)
+* Wsign-compare: Warning Options. (line 1299)
+* Wsign-conversion: Warning Options. (line 1306)
* Wsign-promo: C++ Dialect Options.
- (line 689)
-* Wsized-deallocation: Warning Options. (line 1304)
-* Wsizeof-array-argument: Warning Options. (line 1323)
-* Wsizeof-pointer-memaccess: Warning Options. (line 1315)
-* Wstack-protector: Warning Options. (line 1692)
-* Wstack-usage: Warning Options. (line 1103)
-* Wstrict-aliasing: Warning Options. (line 734)
-* Wstrict-aliasing=n: Warning Options. (line 741)
+ (line 695)
+* Wsized-deallocation: Warning Options. (line 1318)
+* Wsizeof-array-argument: Warning Options. (line 1337)
+* Wsizeof-pointer-memaccess: Warning Options. (line 1329)
+* Wstack-protector: Warning Options. (line 1708)
+* Wstack-usage: Warning Options. (line 1112)
+* Wstrict-aliasing: Warning Options. (line 741)
+* Wstrict-aliasing=n: Warning Options. (line 749)
* Wstrict-null-sentinel: C++ Dialect Options.
- (line 637)
-* Wstrict-overflow: Warning Options. (line 773)
-* Wstrict-prototypes: Warning Options. (line 1393)
+ (line 642)
+* Wstrict-overflow: Warning Options. (line 781)
+* Wstrict-prototypes: Warning Options. (line 1407)
* Wstrict-selector-match: Objective-C and Objective-C++ Dialect Options.
(line 197)
-* Wsuggest-attribute=: Warning Options. (line 822)
-* Wsuggest-attribute=const: Warning Options. (line 828)
-* Wsuggest-attribute=format: Warning Options. (line 842)
-* Wsuggest-attribute=noreturn: Warning Options. (line 828)
-* Wsuggest-attribute=pure: Warning Options. (line 828)
-* Wsuggest-final-methods: Warning Options. (line 872)
-* Wsuggest-final-types: Warning Options. (line 863)
-* Wswitch: Warning Options. (line 545)
-* Wswitch-bool: Warning Options. (line 565)
-* Wswitch-default: Warning Options. (line 553)
-* Wswitch-enum: Warning Options. (line 556)
-* Wsync-nand: Warning Options. (line 575)
-* Wsystem-headers: Warning Options. (line 941)
+* Wsuggest-attribute=: Warning Options. (line 831)
+* Wsuggest-attribute=const: Warning Options. (line 837)
+* Wsuggest-attribute=format: Warning Options. (line 850)
+* Wsuggest-attribute=noreturn: Warning Options. (line 837)
+* Wsuggest-attribute=pure: Warning Options. (line 837)
+* Wsuggest-final-methods: Warning Options. (line 880)
+* Wsuggest-final-types: Warning Options. (line 871)
+* Wswitch: Warning Options. (line 551)
+* Wswitch-bool: Warning Options. (line 571)
+* Wswitch-default: Warning Options. (line 559)
+* Wswitch-enum: Warning Options. (line 562)
+* Wsync-nand: Warning Options. (line 581)
* Wsystem-headers <1>: Preprocessor Options.
(line 165)
-* Wtraditional: Warning Options. (line 977)
+* Wsystem-headers: Warning Options. (line 949)
* Wtraditional <1>: Preprocessor Options.
(line 118)
-* Wtraditional-conversion: Warning Options. (line 1054)
-* Wtrampolines: Warning Options. (line 952)
-* Wtrigraphs: Warning Options. (line 580)
+* Wtraditional: Warning Options. (line 985)
+* Wtraditional-conversion: Warning Options. (line 1063)
+* Wtrampolines: Warning Options. (line 960)
* Wtrigraphs <1>: Preprocessor Options.
(line 106)
-* Wtype-limits: Warning Options. (line 1142)
+* Wtrigraphs: Warning Options. (line 586)
+* Wtype-limits: Warning Options. (line 1153)
* Wundeclared-selector: Objective-C and Objective-C++ Dialect Options.
(line 205)
-* Wundef: Warning Options. (line 1068)
* Wundef <1>: Preprocessor Options.
(line 124)
-* Wuninitialized: Warning Options. (line 657)
-* Wunknown-pragmas: Warning Options. (line 722)
-* Wunsafe-loop-optimizations: Warning Options. (line 1123)
-* Wunsuffixed-float-constants: Warning Options. (line 1712)
-* Wunused: Warning Options. (line 650)
-* Wunused-but-set-parameter: Warning Options. (line 585)
-* Wunused-but-set-variable: Warning Options. (line 594)
-* Wunused-function: Warning Options. (line 604)
-* Wunused-label: Warning Options. (line 609)
-* Wunused-local-typedefs: Warning Options. (line 616)
+* Wundef: Warning Options. (line 1077)
+* Wuninitialized: Warning Options. (line 663)
+* Wunknown-pragmas: Warning Options. (line 729)
+* Wunsafe-loop-optimizations: Warning Options. (line 1134)
+* Wunsuffixed-float-constants: Warning Options. (line 1728)
+* Wunused: Warning Options. (line 656)
+* Wunused-but-set-parameter: Warning Options. (line 591)
+* Wunused-but-set-variable: Warning Options. (line 600)
+* Wunused-function: Warning Options. (line 610)
+* Wunused-label: Warning Options. (line 615)
+* Wunused-local-typedefs: Warning Options. (line 622)
* Wunused-macros: Preprocessor Options.
(line 129)
-* Wunused-parameter: Warning Options. (line 620)
-* Wunused-result: Warning Options. (line 627)
-* Wunused-value: Warning Options. (line 640)
-* Wunused-variable: Warning Options. (line 632)
-* Wuseless-cast: Warning Options. (line 1261)
-* Wvarargs: Warning Options. (line 1643)
-* Wvariadic-macros: Warning Options. (line 1637)
-* Wvector-operation-performance: Warning Options. (line 1648)
-* Wvirtual-move-assign: Warning Options. (line 1658)
-* Wvla: Warning Options. (line 1667)
-* Wvolatile-register-var: Warning Options. (line 1671)
-* Wwrite-strings: Warning Options. (line 1206)
-* Wzero-as-null-pointer-constant: Warning Options. (line 1248)
-* x: Overall Options. (line 126)
+* Wunused-parameter: Warning Options. (line 626)
+* Wunused-result: Warning Options. (line 633)
+* Wunused-value: Warning Options. (line 646)
+* Wunused-variable: Warning Options. (line 638)
+* Wuseless-cast: Warning Options. (line 1275)
+* Wvarargs: Warning Options. (line 1659)
+* Wvariadic-macros: Warning Options. (line 1653)
+* Wvector-operation-performance: Warning Options. (line 1664)
+* Wvirtual-move-assign: Warning Options. (line 1674)
+* Wvla: Warning Options. (line 1683)
+* Wvolatile-register-var: Warning Options. (line 1687)
+* Wwrite-strings: Warning Options. (line 1219)
+* Wzero-as-null-pointer-constant: Warning Options. (line 1262)
* x <1>: Preprocessor Options.
- (line 324)
+ (line 322)
+* x: Overall Options. (line 126)
* Xassembler: Assembler Options. (line 13)
* Xbind-lazy: VxWorks Options. (line 26)
* Xbind-now: VxWorks Options. (line 30)
-* Xlinker: Link Options. (line 244)
+* Xlinker: Link Options. (line 248)
* Xpreprocessor: Preprocessor Options.
(line 25)
* Ym: System V Options. (line 26)
* YP: System V Options. (line 22)
-* z: Link Options. (line 275)
+* z: Link Options. (line 279)

File: gcc.info, Node: Keyword Index, Prev: Option Index, Up: Top
@@ -51153,464 +51613,415 @@ Keyword Index
* Menu:
-* '!' in constraint: Multi-Alternative. (line 33)
-* '#' in constraint: Modifiers. (line 68)
-* '#pragma': Pragmas. (line 6)
+* ! in constraint: Multi-Alternative. (line 33)
+* # in constraint: Modifiers. (line 68)
+* #pragma: Pragmas. (line 6)
* #pragma implementation: C++ Interface. (line 36)
-* '#pragma implementation', implied: C++ Interface. (line 43)
+* #pragma implementation, implied: C++ Interface. (line 43)
* #pragma interface: C++ Interface. (line 17)
-* '#pragma', reason for not using: Function Attributes.
- (line 2042)
+* #pragma, reason for not using: Function Attributes.
+ (line 2049)
* $: Dollar Signs. (line 6)
-* '$' in constraint: Multi-Alternative. (line 42)
-* '%' in constraint: Modifiers. (line 52)
-* '%include': Spec Files. (line 26)
-* '%include_noerr': Spec Files. (line 30)
-* '%rename': Spec Files. (line 34)
-* '&' in constraint: Modifiers. (line 25)
-* ''': Incompatibilities. (line 116)
-* '*' in constraint: Modifiers. (line 73)
-* *__builtin_assume_aligned: Other Builtins. (line 339)
-* '+' in constraint: Modifiers. (line 12)
-* '-lgcc', use with '-nodefaultlibs': Link Options. (line 91)
-* '-lgcc', use with '-nostdlib': Link Options. (line 91)
-* '-march' feature modifiers: AArch64 Options. (line 127)
-* '-mcpu' feature modifiers: AArch64 Options. (line 127)
-* '-nodefaultlibs' and unresolved references: Link Options. (line 91)
-* '-nostdlib' and unresolved references: Link Options. (line 91)
+* $ in constraint: Multi-Alternative. (line 42)
+* % in constraint: Modifiers. (line 52)
+* %include: Spec Files. (line 27)
+* %include_noerr: Spec Files. (line 31)
+* %rename: Spec Files. (line 35)
+* & in constraint: Modifiers. (line 25)
+* ': Incompatibilities. (line 116)
+* * in constraint: Modifiers. (line 73)
+* *__builtin_assume_aligned: Other Builtins. (line 346)
+* + in constraint: Modifiers. (line 12)
+* -lgcc, use with -nodefaultlibs: Link Options. (line 91)
+* -lgcc, use with -nostdlib: Link Options. (line 91)
+* -march feature modifiers: AArch64 Options. (line 133)
+* -mcpu feature modifiers: AArch64 Options. (line 133)
+* -nodefaultlibs and unresolved references: Link Options. (line 91)
+* -nostdlib and unresolved references: Link Options. (line 91)
* .sdata/.sdata2 references (PowerPC): RS/6000 and PowerPC Options.
- (line 767)
-* '//': C++ Comments. (line 6)
-* '0' in constraint: Simple Constraints. (line 125)
-* '<' in constraint: Simple Constraints. (line 47)
-* '=' in constraint: Modifiers. (line 8)
-* '>' in constraint: Simple Constraints. (line 59)
-* '?' in constraint: Multi-Alternative. (line 27)
-* '?:' extensions: Conditionals. (line 6)
-* '?:' side effect: Conditionals. (line 20)
-* '^' in constraint: Multi-Alternative. (line 38)
-* '_' in variables in macros: Typeof. (line 46)
-* '_Accum' data type: Fixed-Point. (line 6)
-* '_Complex' keyword: Complex. (line 6)
-* '_Decimal128' data type: Decimal Float. (line 6)
-* '_Decimal32' data type: Decimal Float. (line 6)
-* '_Decimal64' data type: Decimal Float. (line 6)
-* _Exit: Other Builtins. (line 6)
-* _exit: Other Builtins. (line 6)
-* '_Fract' data type: Fixed-Point. (line 6)
-* _HTM_FIRST_USER_ABORT_CODE: S/390 System z Built-in Functions.
- (line 44)
-* '_Sat' data type: Fixed-Point. (line 6)
-* _xabort: x86 transactional memory intrinsics.
- (line 57)
-* _xbegin: x86 transactional memory intrinsics.
- (line 19)
-* _xend: x86 transactional memory intrinsics.
- (line 48)
-* _xtest: x86 transactional memory intrinsics.
- (line 53)
-* __atomic_add_fetch: __atomic Builtins. (line 153)
-* __atomic_always_lock_free: __atomic Builtins. (line 230)
-* __atomic_and_fetch: __atomic Builtins. (line 157)
-* __atomic_clear: __atomic Builtins. (line 204)
-* __atomic_compare_exchange: __atomic Builtins. (line 145)
-* __atomic_compare_exchange_n: __atomic Builtins. (line 124)
-* __atomic_exchange: __atomic Builtins. (line 118)
-* __atomic_exchange_n: __atomic Builtins. (line 108)
-* __atomic_fetch_add: __atomic Builtins. (line 172)
-* __atomic_fetch_and: __atomic Builtins. (line 176)
-* __atomic_fetch_nand: __atomic Builtins. (line 182)
-* __atomic_fetch_or: __atomic Builtins. (line 180)
-* __atomic_fetch_sub: __atomic Builtins. (line 174)
-* __atomic_fetch_xor: __atomic Builtins. (line 178)
-* __atomic_is_lock_free: __atomic Builtins. (line 244)
-* __atomic_load: __atomic Builtins. (line 90)
-* __atomic_load_n: __atomic Builtins. (line 83)
-* __atomic_nand_fetch: __atomic Builtins. (line 163)
-* __atomic_or_fetch: __atomic Builtins. (line 161)
-* __atomic_signal_fence: __atomic Builtins. (line 223)
-* __atomic_store: __atomic Builtins. (line 103)
-* __atomic_store_n: __atomic Builtins. (line 95)
-* __atomic_sub_fetch: __atomic Builtins. (line 155)
-* __atomic_test_and_set: __atomic Builtins. (line 192)
-* __atomic_thread_fence: __atomic Builtins. (line 216)
-* __atomic_xor_fetch: __atomic Builtins. (line 159)
+ (line 770)
+* //: C++ Comments. (line 6)
+* 0 in constraint: Simple Constraints. (line 127)
+* < in constraint: Simple Constraints. (line 48)
+* = in constraint: Modifiers. (line 8)
+* > in constraint: Simple Constraints. (line 61)
+* ? in constraint: Multi-Alternative. (line 27)
+* ?: extensions: Conditionals. (line 6)
+* ?: side effect: Conditionals. (line 20)
+* ^ in constraint: Multi-Alternative. (line 38)
+* _ in variables in macros: Typeof. (line 46)
+* __atomic_add_fetch: __atomic Builtins. (line 169)
+* __atomic_always_lock_free: __atomic Builtins. (line 247)
+* __atomic_and_fetch: __atomic Builtins. (line 173)
+* __atomic_clear: __atomic Builtins. (line 221)
+* __atomic_compare_exchange: __atomic Builtins. (line 161)
+* __atomic_compare_exchange_n: __atomic Builtins. (line 138)
+* __atomic_exchange: __atomic Builtins. (line 130)
+* __atomic_exchange_n: __atomic Builtins. (line 119)
+* __atomic_fetch_add: __atomic Builtins. (line 189)
+* __atomic_fetch_and: __atomic Builtins. (line 193)
+* __atomic_fetch_nand: __atomic Builtins. (line 199)
+* __atomic_fetch_or: __atomic Builtins. (line 197)
+* __atomic_fetch_sub: __atomic Builtins. (line 191)
+* __atomic_fetch_xor: __atomic Builtins. (line 195)
+* __atomic_is_lock_free: __atomic Builtins. (line 261)
+* __atomic_load: __atomic Builtins. (line 98)
+* __atomic_load_n: __atomic Builtins. (line 89)
+* __atomic_nand_fetch: __atomic Builtins. (line 179)
+* __atomic_or_fetch: __atomic Builtins. (line 177)
+* __atomic_signal_fence: __atomic Builtins. (line 239)
+* __atomic_store: __atomic Builtins. (line 113)
+* __atomic_store_n: __atomic Builtins. (line 104)
+* __atomic_sub_fetch: __atomic Builtins. (line 171)
+* __atomic_test_and_set: __atomic Builtins. (line 210)
+* __atomic_thread_fence: __atomic Builtins. (line 232)
+* __atomic_xor_fetch: __atomic Builtins. (line 175)
+* __builtin___bnd_chk_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_chk_ptr_lbounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_chk_ptr_ubounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_copy_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_get_ptr_lbound: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_get_ptr_ubound: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_init_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_narrow_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_null_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_set_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___bnd_store_ptr_bounds: Pointer Bounds Checker builtins.
+ (line 6)
+* __builtin___clear_cache: Other Builtins. (line 381)
+* __builtin___fprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___memcpy_chk: Object Size Checking.
+ (line 6)
+* __builtin___memmove_chk: Object Size Checking.
+ (line 6)
+* __builtin___mempcpy_chk: Object Size Checking.
+ (line 6)
+* __builtin___memset_chk: Object Size Checking.
+ (line 6)
+* __builtin___printf_chk: Object Size Checking.
+ (line 6)
+* __builtin___snprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___sprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___stpcpy_chk: Object Size Checking.
+ (line 6)
+* __builtin___strcat_chk: Object Size Checking.
+ (line 6)
+* __builtin___strcpy_chk: Object Size Checking.
+ (line 6)
+* __builtin___strncat_chk: Object Size Checking.
+ (line 6)
+* __builtin___strncpy_chk: Object Size Checking.
+ (line 6)
+* __builtin___vfprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___vprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___vsnprintf_chk: Object Size Checking.
+ (line 6)
+* __builtin___vsprintf_chk: Object Size Checking.
+ (line 6)
* __builtin_add_overflow: Integer Overflow Builtins.
- (line 9)
-* __builtin_apply: Constructing Calls. (line 29)
-* __builtin_apply_args: Constructing Calls. (line 19)
+ (line 11)
+* __builtin_apply: Constructing Calls. (line 31)
+* __builtin_apply_args: Constructing Calls. (line 20)
* __builtin_arc_aligned: ARC Built-in Functions.
- (line 18)
+ (line 20)
* __builtin_arc_brk: ARC Built-in Functions.
- (line 28)
+ (line 29)
* __builtin_arc_core_read: ARC Built-in Functions.
- (line 32)
+ (line 34)
* __builtin_arc_core_write: ARC Built-in Functions.
- (line 39)
+ (line 41)
* __builtin_arc_divaw: ARC Built-in Functions.
- (line 46)
+ (line 47)
* __builtin_arc_flag: ARC Built-in Functions.
- (line 53)
+ (line 54)
* __builtin_arc_lr: ARC Built-in Functions.
- (line 57)
+ (line 58)
* __builtin_arc_mul64: ARC Built-in Functions.
- (line 64)
+ (line 65)
* __builtin_arc_mulu64: ARC Built-in Functions.
- (line 68)
+ (line 70)
* __builtin_arc_nop: ARC Built-in Functions.
- (line 73)
+ (line 74)
* __builtin_arc_norm: ARC Built-in Functions.
- (line 77)
+ (line 78)
* __builtin_arc_normw: ARC Built-in Functions.
- (line 84)
+ (line 85)
* __builtin_arc_rtie: ARC Built-in Functions.
- (line 91)
+ (line 92)
* __builtin_arc_sleep: ARC Built-in Functions.
- (line 95)
+ (line 96)
* __builtin_arc_sr: ARC Built-in Functions.
- (line 99)
+ (line 101)
* __builtin_arc_swap: ARC Built-in Functions.
- (line 106)
+ (line 107)
* __builtin_arc_swi: ARC Built-in Functions.
- (line 112)
+ (line 113)
* __builtin_arc_sync: ARC Built-in Functions.
- (line 116)
+ (line 117)
* __builtin_arc_trap_s: ARC Built-in Functions.
- (line 120)
+ (line 121)
* __builtin_arc_unimp_s: ARC Built-in Functions.
- (line 124)
-* __builtin_bswap16: Other Builtins. (line 606)
-* __builtin_bswap32: Other Builtins. (line 610)
-* __builtin_bswap64: Other Builtins. (line 614)
+ (line 125)
+* __builtin_bswap16: Other Builtins. (line 612)
+* __builtin_bswap32: Other Builtins. (line 616)
+* __builtin_bswap64: Other Builtins. (line 620)
* __builtin_call_with_static_chain: Other Builtins. (line 6)
-* __builtin_call_with_static_chain <1>: Other Builtins. (line 154)
-* __builtin_choose_expr: Other Builtins. (line 165)
-* __builtin_clrsb: Other Builtins. (line 536)
-* __builtin_clrsbl: Other Builtins. (line 558)
-* __builtin_clrsbll: Other Builtins. (line 581)
-* __builtin_clz: Other Builtins. (line 528)
-* __builtin_clzl: Other Builtins. (line 550)
-* __builtin_clzll: Other Builtins. (line 573)
-* __builtin_complex: Other Builtins. (line 205)
-* __builtin_constant_p: Other Builtins. (line 214)
+* __builtin_choose_expr: Other Builtins. (line 168)
+* __builtin_clrsb: Other Builtins. (line 542)
+* __builtin_clrsbl: Other Builtins. (line 564)
+* __builtin_clrsbll: Other Builtins. (line 587)
+* __builtin_clz: Other Builtins. (line 534)
+* __builtin_clzl: Other Builtins. (line 556)
+* __builtin_clzll: Other Builtins. (line 579)
+* __builtin_complex: Other Builtins. (line 208)
+* __builtin_constant_p: Other Builtins. (line 218)
* __builtin_cpu_init: x86 Built-in Functions.
- (line 62)
+ (line 63)
* __builtin_cpu_is: x86 Built-in Functions.
- (line 90)
+ (line 92)
* __builtin_cpu_supports: x86 Built-in Functions.
- (line 162)
-* __builtin_ctz: Other Builtins. (line 532)
-* __builtin_ctzl: Other Builtins. (line 554)
-* __builtin_ctzll: Other Builtins. (line 577)
-* __builtin_expect: Other Builtins. (line 259)
-* __builtin_extract_return_addr: Return Address. (line 35)
-* __builtin_ffs: Other Builtins. (line 524)
-* __builtin_ffsl: Other Builtins. (line 547)
-* __builtin_ffsll: Other Builtins. (line 569)
-* __builtin_FILE: Other Builtins. (line 368)
+ (line 164)
+* __builtin_ctz: Other Builtins. (line 538)
+* __builtin_ctzl: Other Builtins. (line 560)
+* __builtin_ctzll: Other Builtins. (line 583)
+* __builtin_expect: Other Builtins. (line 264)
+* __builtin_extract_return_addr: Return Address. (line 36)
+* __builtin_ffs: Other Builtins. (line 530)
+* __builtin_ffsl: Other Builtins. (line 553)
+* __builtin_ffsll: Other Builtins. (line 575)
+* __builtin_FILE: Other Builtins. (line 374)
* __builtin_fpclassify: Other Builtins. (line 6)
-* __builtin_fpclassify <1>: Other Builtins. (line 438)
-* __builtin_frame_address: Return Address. (line 47)
-* __builtin_frob_return_address: Return Address. (line 44)
-* __builtin_FUNCTION: Other Builtins. (line 363)
-* __builtin_huge_val: Other Builtins. (line 426)
-* __builtin_huge_valf: Other Builtins. (line 431)
-* __builtin_huge_vall: Other Builtins. (line 434)
+* __builtin_frame_address: Return Address. (line 49)
+* __builtin_frob_return_address: Return Address. (line 45)
+* __builtin_FUNCTION: Other Builtins. (line 369)
+* __builtin_huge_val: Other Builtins. (line 432)
+* __builtin_huge_valf: Other Builtins. (line 437)
+* __builtin_huge_vall: Other Builtins. (line 440)
* __builtin_huge_valq: x86 Built-in Functions.
(line 57)
-* __builtin_inf: Other Builtins. (line 449)
-* __builtin_infd128: Other Builtins. (line 459)
-* __builtin_infd32: Other Builtins. (line 453)
-* __builtin_infd64: Other Builtins. (line 456)
-* __builtin_inff: Other Builtins. (line 463)
-* __builtin_infl: Other Builtins. (line 468)
+* __builtin_inf: Other Builtins. (line 455)
+* __builtin_infd128: Other Builtins. (line 465)
+* __builtin_infd32: Other Builtins. (line 459)
+* __builtin_infd64: Other Builtins. (line 462)
+* __builtin_inff: Other Builtins. (line 469)
+* __builtin_infl: Other Builtins. (line 474)
* __builtin_infq: x86 Built-in Functions.
- (line 54)
+ (line 53)
* __builtin_isfinite: Other Builtins. (line 6)
* __builtin_isgreater: Other Builtins. (line 6)
* __builtin_isgreaterequal: Other Builtins. (line 6)
* __builtin_isinf_sign: Other Builtins. (line 6)
-* __builtin_isinf_sign <1>: Other Builtins. (line 472)
* __builtin_isless: Other Builtins. (line 6)
* __builtin_islessequal: Other Builtins. (line 6)
* __builtin_islessgreater: Other Builtins. (line 6)
* __builtin_isnormal: Other Builtins. (line 6)
* __builtin_isunordered: Other Builtins. (line 6)
-* __builtin_LINE: Other Builtins. (line 357)
+* __builtin_LINE: Other Builtins. (line 363)
* __builtin_mul_overflow: Integer Overflow Builtins.
- (line 60)
-* __builtin_nan: Other Builtins. (line 480)
-* __builtin_nand128: Other Builtins. (line 502)
-* __builtin_nand32: Other Builtins. (line 496)
-* __builtin_nand64: Other Builtins. (line 499)
-* __builtin_nanf: Other Builtins. (line 506)
-* __builtin_nanl: Other Builtins. (line 509)
-* __builtin_nans: Other Builtins. (line 513)
-* __builtin_nansf: Other Builtins. (line 517)
-* __builtin_nansl: Other Builtins. (line 520)
+ (line 63)
+* __builtin_nan: Other Builtins. (line 486)
+* __builtin_nand128: Other Builtins. (line 508)
+* __builtin_nand32: Other Builtins. (line 502)
+* __builtin_nand64: Other Builtins. (line 505)
+* __builtin_nanf: Other Builtins. (line 512)
+* __builtin_nanl: Other Builtins. (line 515)
+* __builtin_nans: Other Builtins. (line 519)
+* __builtin_nansf: Other Builtins. (line 523)
+* __builtin_nansl: Other Builtins. (line 526)
* __builtin_nds32_isb: NDS32 Built-in Functions.
- (line 12)
+ (line 13)
* __builtin_nds32_isync: NDS32 Built-in Functions.
- (line 8)
+ (line 9)
* __builtin_nds32_mfsr: NDS32 Built-in Functions.
- (line 15)
+ (line 16)
* __builtin_nds32_mfusr: NDS32 Built-in Functions.
- (line 18)
+ (line 19)
* __builtin_nds32_mtsr: NDS32 Built-in Functions.
- (line 21)
+ (line 22)
* __builtin_nds32_mtusr: NDS32 Built-in Functions.
- (line 24)
+ (line 25)
* __builtin_nds32_setgie_dis: NDS32 Built-in Functions.
- (line 30)
+ (line 31)
* __builtin_nds32_setgie_en: NDS32 Built-in Functions.
- (line 27)
+ (line 28)
* __builtin_non_tx_store: S/390 System z Built-in Functions.
- (line 98)
+ (line 104)
* __builtin_object_size: Object Size Checking.
(line 6)
-* __builtin_object_size <1>: Object Size Checking.
- (line 9)
* __builtin_offsetof: Offsetof. (line 6)
-* __builtin_parity: Other Builtins. (line 544)
-* __builtin_parityl: Other Builtins. (line 565)
-* __builtin_parityll: Other Builtins. (line 589)
-* __builtin_popcount: Other Builtins. (line 541)
-* __builtin_popcountl: Other Builtins. (line 561)
-* __builtin_popcountll: Other Builtins. (line 585)
+* __builtin_parity: Other Builtins. (line 550)
+* __builtin_parityl: Other Builtins. (line 571)
+* __builtin_parityll: Other Builtins. (line 595)
+* __builtin_popcount: Other Builtins. (line 547)
+* __builtin_popcountl: Other Builtins. (line 567)
+* __builtin_popcountll: Other Builtins. (line 591)
* __builtin_powi: Other Builtins. (line 6)
-* __builtin_powi <1>: Other Builtins. (line 593)
* __builtin_powif: Other Builtins. (line 6)
-* __builtin_powif <1>: Other Builtins. (line 598)
* __builtin_powil: Other Builtins. (line 6)
-* __builtin_powil <1>: Other Builtins. (line 602)
-* __builtin_prefetch: Other Builtins. (line 387)
-* __builtin_return: Constructing Calls. (line 47)
-* __builtin_return_address: Return Address. (line 9)
+* __builtin_prefetch: Other Builtins. (line 393)
+* __builtin_return: Constructing Calls. (line 48)
+* __builtin_return_address: Return Address. (line 11)
* __builtin_rx_brk: RX Built-in Functions.
- (line 10)
+ (line 11)
* __builtin_rx_clrpsw: RX Built-in Functions.
- (line 13)
+ (line 14)
* __builtin_rx_int: RX Built-in Functions.
- (line 17)
+ (line 18)
* __builtin_rx_machi: RX Built-in Functions.
- (line 21)
+ (line 22)
* __builtin_rx_maclo: RX Built-in Functions.
- (line 26)
+ (line 27)
* __builtin_rx_mulhi: RX Built-in Functions.
- (line 31)
+ (line 32)
* __builtin_rx_mullo: RX Built-in Functions.
- (line 36)
+ (line 37)
* __builtin_rx_mvfachi: RX Built-in Functions.
- (line 41)
+ (line 42)
* __builtin_rx_mvfacmi: RX Built-in Functions.
- (line 45)
+ (line 46)
* __builtin_rx_mvfc: RX Built-in Functions.
- (line 49)
+ (line 50)
* __builtin_rx_mvtachi: RX Built-in Functions.
- (line 53)
+ (line 54)
* __builtin_rx_mvtaclo: RX Built-in Functions.
- (line 57)
+ (line 58)
* __builtin_rx_mvtc: RX Built-in Functions.
- (line 61)
+ (line 62)
* __builtin_rx_mvtipl: RX Built-in Functions.
- (line 65)
+ (line 66)
* __builtin_rx_racw: RX Built-in Functions.
- (line 69)
+ (line 70)
* __builtin_rx_revw: RX Built-in Functions.
- (line 73)
+ (line 74)
* __builtin_rx_rmpa: RX Built-in Functions.
- (line 78)
+ (line 79)
* __builtin_rx_round: RX Built-in Functions.
- (line 82)
+ (line 83)
* __builtin_rx_sat: RX Built-in Functions.
- (line 87)
+ (line 88)
* __builtin_rx_setpsw: RX Built-in Functions.
- (line 91)
+ (line 92)
* __builtin_rx_wait: RX Built-in Functions.
- (line 95)
-* __builtin_saddll_overflow: Integer Overflow Builtins.
- (line 15)
-* __builtin_saddl_overflow: Integer Overflow Builtins.
- (line 13)
+ (line 96)
* __builtin_sadd_overflow: Integer Overflow Builtins.
- (line 11)
+ (line 13)
+* __builtin_saddl_overflow: Integer Overflow Builtins.
+ (line 15)
+* __builtin_saddll_overflow: Integer Overflow Builtins.
+ (line 17)
* __builtin_set_thread_pointer: SH Built-in Functions.
- (line 9)
+ (line 10)
* __builtin_sh_get_fpscr: SH Built-in Functions.
- (line 35)
+ (line 36)
* __builtin_sh_set_fpscr: SH Built-in Functions.
- (line 38)
-* __builtin_smulll_overflow: Integer Overflow Builtins.
- (line 66)
-* __builtin_smull_overflow: Integer Overflow Builtins.
- (line 64)
+ (line 39)
* __builtin_smul_overflow: Integer Overflow Builtins.
- (line 62)
-* __builtin_ssubll_overflow: Integer Overflow Builtins.
- (line 47)
-* __builtin_ssubl_overflow: Integer Overflow Builtins.
- (line 45)
+ (line 65)
+* __builtin_smull_overflow: Integer Overflow Builtins.
+ (line 67)
+* __builtin_smulll_overflow: Integer Overflow Builtins.
+ (line 69)
* __builtin_ssub_overflow: Integer Overflow Builtins.
- (line 43)
+ (line 45)
+* __builtin_ssubl_overflow: Integer Overflow Builtins.
+ (line 47)
+* __builtin_ssubll_overflow: Integer Overflow Builtins.
+ (line 49)
* __builtin_sub_overflow: Integer Overflow Builtins.
- (line 41)
+ (line 43)
* __builtin_tabort: S/390 System z Built-in Functions.
- (line 82)
+ (line 87)
* __builtin_tbegin: S/390 System z Built-in Functions.
- (line 6)
-* __builtin_tbeginc: S/390 System z Built-in Functions.
- (line 73)
+ (line 7)
* __builtin_tbegin_nofloat: S/390 System z Built-in Functions.
- (line 54)
+ (line 59)
* __builtin_tbegin_retry: S/390 System z Built-in Functions.
- (line 60)
+ (line 65)
* __builtin_tbegin_retry_nofloat: S/390 System z Built-in Functions.
- (line 67)
+ (line 72)
+* __builtin_tbeginc: S/390 System z Built-in Functions.
+ (line 78)
* __builtin_tend: S/390 System z Built-in Functions.
- (line 77)
+ (line 82)
* __builtin_thread_pointer: SH Built-in Functions.
- (line 18)
-* __builtin_trap: Other Builtins. (line 283)
+ (line 20)
+* __builtin_trap: Other Builtins. (line 288)
* __builtin_tx_assist: S/390 System z Built-in Functions.
- (line 87)
+ (line 92)
* __builtin_tx_nesting_depth: S/390 System z Built-in Functions.
- (line 93)
-* __builtin_types_compatible_p: Other Builtins. (line 109)
-* __builtin_uaddll_overflow: Integer Overflow Builtins.
- (line 21)
-* __builtin_uaddl_overflow: Integer Overflow Builtins.
- (line 19)
+ (line 98)
+* __builtin_types_compatible_p: Other Builtins. (line 111)
* __builtin_uadd_overflow: Integer Overflow Builtins.
- (line 17)
-* __builtin_umulll_overflow: Integer Overflow Builtins.
- (line 72)
-* __builtin_umull_overflow: Integer Overflow Builtins.
- (line 70)
+ (line 19)
+* __builtin_uaddl_overflow: Integer Overflow Builtins.
+ (line 21)
+* __builtin_uaddll_overflow: Integer Overflow Builtins.
+ (line 23)
* __builtin_umul_overflow: Integer Overflow Builtins.
- (line 68)
-* __builtin_unreachable: Other Builtins. (line 290)
-* __builtin_usubll_overflow: Integer Overflow Builtins.
- (line 53)
-* __builtin_usubl_overflow: Integer Overflow Builtins.
- (line 51)
-* __builtin_usub_overflow: Integer Overflow Builtins.
- (line 49)
-* __builtin_va_arg_pack: Constructing Calls. (line 52)
-* __builtin_va_arg_pack_len: Constructing Calls. (line 75)
-* __builtin___bnd_chk_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_chk_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 110)
-* __builtin___bnd_chk_ptr_lbounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_chk_ptr_lbounds <1>: Pointer Bounds Checker builtins.
- (line 85)
-* __builtin___bnd_chk_ptr_ubounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_chk_ptr_ubounds <1>: Pointer Bounds Checker builtins.
- (line 103)
-* __builtin___bnd_copy_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_copy_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 46)
-* __builtin___bnd_get_ptr_lbound: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_get_ptr_lbound <1>: Pointer Bounds Checker builtins.
- (line 128)
-* __builtin___bnd_get_ptr_ubound: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_get_ptr_ubound <1>: Pointer Bounds Checker builtins.
- (line 140)
-* __builtin___bnd_init_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_init_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 59)
-* __builtin___bnd_narrow_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_narrow_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 27)
-* __builtin___bnd_null_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_null_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 67)
-* __builtin___bnd_set_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_set_ptr_bounds <1>: Pointer Bounds Checker builtins.
- (line 12)
-* __builtin___bnd_store_ptr_bounds: Pointer Bounds Checker builtins.
- (line 6)
-* __builtin___bnd_store_ptr_bounds <1>: Pointer Bounds Checker builtins.
+ (line 71)
+* __builtin_umull_overflow: Integer Overflow Builtins.
+ (line 73)
+* __builtin_umulll_overflow: Integer Overflow Builtins.
(line 75)
-* __builtin___clear_cache: Other Builtins. (line 374)
-* __builtin___fprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___memcpy_chk: Object Size Checking.
- (line 6)
-* __builtin___memmove_chk: Object Size Checking.
- (line 6)
-* __builtin___mempcpy_chk: Object Size Checking.
- (line 6)
-* __builtin___memset_chk: Object Size Checking.
- (line 6)
-* __builtin___printf_chk: Object Size Checking.
- (line 6)
-* __builtin___snprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___sprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___stpcpy_chk: Object Size Checking.
- (line 6)
-* __builtin___strcat_chk: Object Size Checking.
- (line 6)
-* __builtin___strcpy_chk: Object Size Checking.
- (line 6)
-* __builtin___strncat_chk: Object Size Checking.
- (line 6)
-* __builtin___strncpy_chk: Object Size Checking.
- (line 6)
-* __builtin___vfprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___vprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___vsnprintf_chk: Object Size Checking.
- (line 6)
-* __builtin___vsprintf_chk: Object Size Checking.
- (line 6)
-* '__complex__' keyword: Complex. (line 6)
-* '__declspec(dllexport)': Function Attributes.
- (line 283)
-* '__declspec(dllimport)': Function Attributes.
- (line 315)
-* '__ea' SPU Named Address Spaces: Named Address Spaces.
+* __builtin_unreachable: Other Builtins. (line 295)
+* __builtin_usub_overflow: Integer Overflow Builtins.
+ (line 51)
+* __builtin_usubl_overflow: Integer Overflow Builtins.
+ (line 53)
+* __builtin_usubll_overflow: Integer Overflow Builtins.
+ (line 55)
+* __builtin_va_arg_pack: Constructing Calls. (line 53)
+* __builtin_va_arg_pack_len: Constructing Calls. (line 76)
+* __complex__ keyword: Complex. (line 6)
+* __declspec(dllexport): Function Attributes.
+ (line 285)
+* __declspec(dllimport): Function Attributes.
+ (line 319)
+* __ea SPU Named Address Spaces: Named Address Spaces.
(line 155)
* __extension__: Alternate Keywords. (line 30)
-* '__far' M32C Named Address Spaces: Named Address Spaces.
- (line 138)
-* '__far' RL78 Named Address Spaces: Named Address Spaces.
+* __far M32C Named Address Spaces: Named Address Spaces.
+ (line 139)
+* __far RL78 Named Address Spaces: Named Address Spaces.
(line 147)
-* '__flash' AVR Named Address Spaces: Named Address Spaces.
+* __flash AVR Named Address Spaces: Named Address Spaces.
(line 31)
-* '__flash1' AVR Named Address Spaces: Named Address Spaces.
+* __flash1 AVR Named Address Spaces: Named Address Spaces.
(line 40)
-* '__flash2' AVR Named Address Spaces: Named Address Spaces.
+* __flash2 AVR Named Address Spaces: Named Address Spaces.
(line 40)
-* '__flash3' AVR Named Address Spaces: Named Address Spaces.
+* __flash3 AVR Named Address Spaces: Named Address Spaces.
(line 40)
-* '__flash4' AVR Named Address Spaces: Named Address Spaces.
+* __flash4 AVR Named Address Spaces: Named Address Spaces.
(line 40)
-* '__flash5' AVR Named Address Spaces: Named Address Spaces.
+* __flash5 AVR Named Address Spaces: Named Address Spaces.
(line 40)
-* '__float128' data type: Floating Types. (line 6)
-* '__float80' data type: Floating Types. (line 6)
-* '__fp16' data type: Half-Precision. (line 6)
-* '__FUNCTION__' identifier: Function Names. (line 6)
-* '__func__' identifier: Function Names. (line 6)
-* '__imag__' keyword: Complex. (line 27)
-* '__int128' data types: __int128. (line 6)
-* '__memx' AVR Named Address Spaces: Named Address Spaces.
+* __float128 data type: Floating Types. (line 6)
+* __float80 data type: Floating Types. (line 6)
+* __fp16 data type: Half-Precision. (line 6)
+* __func__ identifier: Function Names. (line 6)
+* __FUNCTION__ identifier: Function Names. (line 6)
+* __imag__ keyword: Complex. (line 27)
+* __int128 data types: __int128. (line 6)
+* __memx AVR Named Address Spaces: Named Address Spaces.
(line 46)
-* '__PRETTY_FUNCTION__' identifier: Function Names. (line 6)
-* '__real__' keyword: Complex. (line 27)
+* __PRETTY_FUNCTION__ identifier: Function Names. (line 6)
+* __real__ keyword: Complex. (line 27)
* __STDC_HOSTED__: Standards. (line 13)
* __sync_add_and_fetch: __sync Builtins. (line 60)
* __sync_and_and_fetch: __sync Builtins. (line 60)
@@ -51629,16 +52040,35 @@ Keyword Index
* __sync_synchronize: __sync Builtins. (line 80)
* __sync_val_compare_and_swap: __sync Builtins. (line 71)
* __sync_xor_and_fetch: __sync Builtins. (line 60)
-* '__thread': Thread-Local. (line 6)
+* __thread: Thread-Local. (line 6)
+* _Accum data type: Fixed-Point. (line 6)
+* _Complex keyword: Complex. (line 6)
+* _Decimal128 data type: Decimal Float. (line 6)
+* _Decimal32 data type: Decimal Float. (line 6)
+* _Decimal64 data type: Decimal Float. (line 6)
+* _exit: Other Builtins. (line 6)
+* _Exit: Other Builtins. (line 6)
+* _Fract data type: Fixed-Point. (line 6)
+* _HTM_FIRST_USER_ABORT_CODE: S/390 System z Built-in Functions.
+ (line 48)
+* _Sat data type: Fixed-Point. (line 6)
+* _xabort: x86 transactional memory intrinsics.
+ (line 64)
+* _xbegin: x86 transactional memory intrinsics.
+ (line 20)
+* _xend: x86 transactional memory intrinsics.
+ (line 55)
+* _xtest: x86 transactional memory intrinsics.
+ (line 60)
* AArch64 Options: AArch64 Options. (line 6)
* ABI: Compatibility. (line 6)
-* 'abi_tag' function attribute: C++ Attributes. (line 9)
-* 'abi_tag' type attribute: C++ Attributes. (line 9)
-* 'abi_tag' variable attribute: C++ Attributes. (line 9)
+* abi_tag function attribute: C++ Attributes. (line 9)
+* abi_tag type attribute: C++ Attributes. (line 9)
+* abi_tag variable attribute: C++ Attributes. (line 9)
* abort: Other Builtins. (line 6)
* abs: Other Builtins. (line 6)
-* accessing volatiles: Volatiles. (line 6)
* accessing volatiles <1>: C++ Volatiles. (line 6)
+* accessing volatiles: Volatiles. (line 6)
* acos: Other Builtins. (line 6)
* acosf: Other Builtins. (line 6)
* acosh: Other Builtins. (line 6)
@@ -51646,35 +52076,34 @@ Keyword Index
* acoshl: Other Builtins. (line 6)
* acosl: Other Builtins. (line 6)
* Ada: G++ and GCC. (line 6)
-* Ada <1>: G++ and GCC. (line 30)
* additional floating types: Floating Types. (line 6)
-* address constraints: Simple Constraints. (line 152)
+* address constraints: Simple Constraints. (line 154)
* address of a label: Labels as Values. (line 6)
-* 'address' variable attribute, AVR: Variable Attributes.
- (line 371)
-* address_operand: Simple Constraints. (line 156)
-* 'alias' function attribute: Function Attributes.
+* address variable attribute, AVR: Variable Attributes.
+ (line 375)
+* address_operand: Simple Constraints. (line 158)
+* alias function attribute: Function Attributes.
(line 40)
-* 'aligned' function attribute: Function Attributes.
+* aligned function attribute: Function Attributes.
(line 53)
-* 'aligned' type attribute: Type Attributes. (line 32)
-* 'aligned' variable attribute: Variable Attributes.
+* aligned type attribute: Type Attributes. (line 32)
+* aligned variable attribute: Variable Attributes.
(line 24)
* alignment: Alignment. (line 6)
-* alloca: Other Builtins. (line 6)
-* 'alloca' vs variable-length arrays: Variable Length. (line 35)
-* 'alloc_align' function attribute: Function Attributes.
+* alloc_align function attribute: Function Attributes.
(line 94)
-* 'alloc_size' function attribute: Function Attributes.
+* alloc_size function attribute: Function Attributes.
(line 73)
+* alloca: Other Builtins. (line 6)
+* alloca vs variable-length arrays: Variable Length. (line 35)
* Allow nesting in an interrupt handler on the Blackfin processor: Function Attributes.
- (line 1052)
+ (line 1056)
* Altera Nios II options: Nios II Options. (line 6)
* alternate keywords: Alternate Keywords. (line 6)
-* 'altivec' type attribute, PowerPC: Type Attributes. (line 362)
-* 'altivec' variable attribute, PowerPC: Variable Attributes.
- (line 509)
-* 'always_inline' function attribute: Function Attributes.
+* altivec type attribute, PowerPC: Type Attributes. (line 363)
+* altivec variable attribute, PowerPC: Variable Attributes.
+ (line 518)
+* always_inline function attribute: Function Attributes.
(line 126)
* AMD1: Standards. (line 13)
* ANSI C: Standards. (line 13)
@@ -51685,37 +52114,37 @@ Keyword Index
* apostrophes: Incompatibilities. (line 116)
* application binary interface: Compatibility. (line 6)
* ARC options: ARC Options. (line 6)
-* ARM options: ARM Options. (line 6)
* ARM [Annotated C++ Reference Manual]: Backwards Compatibility.
(line 6)
+* ARM options: ARM Options. (line 6)
* arrays of length zero: Zero Length. (line 6)
* arrays of variable length: Variable Length. (line 6)
* arrays, non-lvalue: Subscripting. (line 6)
-* 'artificial' function attribute: Function Attributes.
- (line 172)
+* artificial function attribute: Function Attributes.
+ (line 174)
* asin: Other Builtins. (line 6)
* asinf: Other Builtins. (line 6)
* asinh: Other Builtins. (line 6)
* asinhf: Other Builtins. (line 6)
* asinhl: Other Builtins. (line 6)
* asinl: Other Builtins. (line 6)
-* 'asm' assembler template: Extended Asm. (line 218)
-* 'asm' clobbers: Extended Asm. (line 575)
-* 'asm' constraints: Constraints. (line 6)
-* 'asm' expressions: Extended Asm. (line 480)
-* 'asm' goto labels: Extended Asm. (line 644)
-* 'asm' input operands: Extended Asm. (line 480)
-* 'asm' keyword: Using Assembly Language with C.
+* asm assembler template: Extended Asm. (line 219)
+* asm clobbers: Extended Asm. (line 578)
+* asm constraints: Constraints. (line 6)
+* asm expressions: Extended Asm. (line 482)
+* asm goto labels: Extended Asm. (line 648)
+* asm input operands: Extended Asm. (line 482)
+* asm keyword: Using Assembly Language with C.
(line 6)
-* 'asm' output operands: Extended Asm. (line 321)
-* 'asm' volatile: Extended Asm. (line 109)
+* asm output operands: Extended Asm. (line 322)
+* asm volatile: Extended Asm. (line 109)
* assembler names for identifiers: Asm Labels. (line 6)
* assembly code, invalid: Bug Criteria. (line 12)
* assembly language in C: Using Assembly Language with C.
(line 6)
* assembly language in C, basic: Basic Asm. (line 6)
* assembly language in C, extended: Extended Asm. (line 6)
-* 'assume_aligned' function attribute: Function Attributes.
+* assume_aligned function attribute: Function Attributes.
(line 111)
* atan: Other Builtins. (line 6)
* atan2: Other Builtins. (line 6)
@@ -51731,46 +52160,46 @@ Keyword Index
(line 6)
* attribute syntax: Attribute Syntax. (line 6)
* autoincrement/decrement addressing: Simple Constraints. (line 30)
-* automatic 'inline' for C++ member fns: Inline. (line 71)
+* automatic inline for C++ member fns: Inline. (line 71)
* AVR Options: AVR Options. (line 6)
* Backwards Compatibility: Backwards Compatibility.
(line 6)
-* 'bank_switch' function attribute, M32C: Function Attributes.
- (line 179)
+* bank_switch function attribute, M32C: Function Attributes.
+ (line 181)
* base class members: Name lookup. (line 6)
-* 'based' type attribute, MeP: Type Attributes. (line 348)
-* 'based' variable attribute, MeP: Variable Attributes.
- (line 464)
-* basic 'asm': Basic Asm. (line 6)
+* based type attribute, MeP: Type Attributes. (line 349)
+* based variable attribute, MeP: Variable Attributes.
+ (line 470)
+* basic asm: Basic Asm. (line 6)
* bcmp: Other Builtins. (line 6)
-* 'below100' variable attribute, Xstormy16: Variable Attributes.
- (line 648)
+* below100 variable attribute, Xstormy16: Variable Attributes.
+ (line 656)
* binary compatibility: Compatibility. (line 6)
-* Binary constants using the '0b' prefix: Binary constants. (line 6)
+* Binary constants using the 0b prefix: Binary constants. (line 6)
* Blackfin Options: Blackfin Options. (line 6)
-* 'bnd_instrument' function attribute: Function Attributes.
- (line 1323)
-* 'bnd_legacy' function attribute: Function Attributes.
- (line 1318)
-* 'bnd_variable_size' type attribute: Type Attributes. (line 295)
+* bnd_instrument function attribute: Function Attributes.
+ (line 1327)
+* bnd_legacy function attribute: Function Attributes.
+ (line 1322)
+* bnd_variable_size type attribute: Type Attributes. (line 295)
* bound pointer to member function: Bound member functions.
(line 6)
* break handler functions: Function Attributes.
- (line 1411)
-* 'break_handler' function attribute, MicroBlaze: Function Attributes.
- (line 1411)
-* 'brk_interrupt' function attribute, RL78: Function Attributes.
- (line 788)
+ (line 1416)
+* break_handler function attribute, MicroBlaze: Function Attributes.
+ (line 1416)
+* brk_interrupt function attribute, RL78: Function Attributes.
+ (line 798)
* bug criteria: Bug Criteria. (line 6)
* bugs: Bugs. (line 6)
* bugs, known: Trouble. (line 6)
-* built-in functions: C Dialect Options. (line 210)
* built-in functions <1>: Other Builtins. (line 6)
+* built-in functions: C Dialect Options. (line 213)
* bzero: Other Builtins. (line 6)
* C compilation options: Invoking GCC. (line 17)
* C intermediate output, nonexistent: G++ and GCC. (line 35)
* C language extensions: C Extensions. (line 6)
-* C language, traditional: C Dialect Options. (line 345)
+* C language, traditional: C Dialect Options. (line 344)
* C standard: Standards. (line 13)
* C standards: Standards. (line 13)
* c++: Invoking G++. (line 14)
@@ -51779,7 +52208,7 @@ Keyword Index
* C++ compilation options: Invoking GCC. (line 23)
* C++ interface and implementation headers: C++ Interface. (line 6)
* C++ language extensions: C++ Extensions. (line 6)
-* C++ member fns, automatically 'inline': Inline. (line 71)
+* C++ member fns, automatically inline: Inline. (line 71)
* C++ misunderstandings: C++ Misunderstandings.
(line 6)
* C++ options, command-line: C++ Dialect Options.
@@ -51797,6 +52226,8 @@ Keyword Index
* C95: Standards. (line 13)
* C99: Standards. (line 13)
* C9X: Standards. (line 13)
+* C_INCLUDE_PATH: Environment Variables.
+ (line 130)
* cabs: Other Builtins. (line 6)
* cabsf: Other Builtins. (line 6)
* cabsl: Other Builtins. (line 6)
@@ -51806,10 +52237,10 @@ Keyword Index
* cacoshf: Other Builtins. (line 6)
* cacoshl: Other Builtins. (line 6)
* cacosl: Other Builtins. (line 6)
-* 'callee_pop_aggregate_return' function attribute, x86: Function Attributes.
- (line 1004)
+* callee_pop_aggregate_return function attribute, x86: Function Attributes.
+ (line 1011)
* calling functions through the function vector on H8/300, M16C, M32C and SH2A processors: Function Attributes.
- (line 531)
+ (line 537)
* calloc: Other Builtins. (line 6)
* caret: Multi-Alternative. (line 38)
* caret GCC_COLORS capability: Language Independent Options.
@@ -51832,8 +52263,8 @@ Keyword Index
* catanhf: Other Builtins. (line 6)
* catanhl: Other Builtins. (line 6)
* catanl: Other Builtins. (line 6)
-* 'cb' variable attribute, MeP: Variable Attributes.
- (line 494)
+* cb variable attribute, MeP: Variable Attributes.
+ (line 502)
* cbrt: Other Builtins. (line 6)
* cbrtf: Other Builtins. (line 6)
* cbrtl: Other Builtins. (line 6)
@@ -51843,8 +52274,8 @@ Keyword Index
* ccoshf: Other Builtins. (line 6)
* ccoshl: Other Builtins. (line 6)
* ccosl: Other Builtins. (line 6)
-* 'cdecl' function attribute, x86-32: Function Attributes.
- (line 215)
+* cdecl function attribute, x86-32: Function Attributes.
+ (line 217)
* ceil: Other Builtins. (line 6)
* ceilf: Other Builtins. (line 6)
* ceill: Other Builtins. (line 6)
@@ -51855,13 +52286,13 @@ Keyword Index
(line 553)
* character set, input: Preprocessor Options.
(line 566)
-* character set, input normalization: Warning Options. (line 1467)
+* character set, input normalization: Warning Options. (line 1481)
* character set, wide execution: Preprocessor Options.
(line 558)
* cimag: Other Builtins. (line 6)
* cimagf: Other Builtins. (line 6)
* cimagl: Other Builtins. (line 6)
-* 'cleanup' variable attribute: Variable Attributes.
+* cleanup variable attribute: Variable Attributes.
(line 90)
* clog: Other Builtins. (line 6)
* clogf: Other Builtins. (line 6)
@@ -51869,15 +52300,15 @@ Keyword Index
* COBOL: G++ and GCC. (line 23)
* code generation conventions: Code Gen Options. (line 6)
* code, mixed with declarations: Mixed Declarations. (line 6)
-* 'cold' function attribute: Function Attributes.
- (line 1282)
-* 'cold' label attribute: Label Attributes. (line 43)
+* cold function attribute: Function Attributes.
+ (line 1286)
+* cold label attribute: Label Attributes. (line 43)
* command options: Invoking GCC. (line 6)
* comments, C++ style: C++ Comments. (line 6)
-* 'common' variable attribute: Variable Attributes.
- (line 105)
+* common variable attribute: Variable Attributes.
+ (line 106)
* comparison of signed and unsigned values, warning: Warning Options.
- (line 1285)
+ (line 1299)
* compiler bugs, reporting: Bug Reporting. (line 6)
* compiler compared to C++ preprocessor: G++ and GCC. (line 35)
* compiler options, C++: C++ Dialect Options.
@@ -51896,21 +52327,21 @@ Keyword Index
* conj: Other Builtins. (line 6)
* conjf: Other Builtins. (line 6)
* conjl: Other Builtins. (line 6)
-* 'const' applied to function: Function Attributes.
+* const applied to function: Function Attributes.
(line 6)
-* 'const' function attribute: Function Attributes.
- (line 221)
+* const function attribute: Function Attributes.
+ (line 223)
* const qualifier: Pointers to Arrays. (line 6)
-* constants in constraints: Simple Constraints. (line 68)
+* constants in constraints: Simple Constraints. (line 70)
* constraint modifier characters: Modifiers. (line 6)
-* constraint, matching: Simple Constraints. (line 137)
-* constraints, 'asm': Constraints. (line 6)
+* constraint, matching: Simple Constraints. (line 139)
+* constraints, asm: Constraints. (line 6)
* constraints, machine specific: Machine Constraints.
(line 6)
* constructing calls: Constructing Calls. (line 6)
* constructor expressions: Compound Literals. (line 6)
-* 'constructor' function attribute: Function Attributes.
- (line 236)
+* constructor function attribute: Function Attributes.
+ (line 238)
* contributors: Contributors. (line 6)
* copysign: Other Builtins. (line 6)
* copysignf: Other Builtins. (line 6)
@@ -51923,9 +52354,9 @@ Keyword Index
* coshl: Other Builtins. (line 6)
* cosl: Other Builtins. (line 6)
* CPATH: Environment Variables.
- (line 127)
-* CPLUS_INCLUDE_PATH: Environment Variables.
(line 129)
+* CPLUS_INCLUDE_PATH: Environment Variables.
+ (line 131)
* cpow: Other Builtins. (line 6)
* cpowf: Other Builtins. (line 6)
* cpowl: Other Builtins. (line 6)
@@ -51937,8 +52368,8 @@ Keyword Index
* crealf: Other Builtins. (line 6)
* creall: Other Builtins. (line 6)
* CRIS Options: CRIS Options. (line 6)
-* 'critical' function attribute, MSP430: Function Attributes.
- (line 684)
+* critical function attribute, MSP430: Function Attributes.
+ (line 691)
* cross compiling: Target Options. (line 6)
* csin: Other Builtins. (line 6)
* csinf: Other Builtins. (line 6)
@@ -51955,12 +52386,10 @@ Keyword Index
* ctanhf: Other Builtins. (line 6)
* ctanhl: Other Builtins. (line 6)
* ctanl: Other Builtins. (line 6)
-* C_INCLUDE_PATH: Environment Variables.
- (line 128)
* Darwin options: Darwin Options. (line 6)
* dcgettext: Other Builtins. (line 6)
-* 'dd' integer suffix: Decimal Float. (line 6)
-* 'DD' integer suffix: Decimal Float. (line 6)
+* DD integer suffix: Decimal Float. (line 6)
+* dd integer suffix: Decimal Float. (line 6)
* deallocating variable length arrays: Variable Length. (line 22)
* debugging information options: Debugging Options. (line 6)
* decimal floating types: Decimal Float. (line 6)
@@ -51972,47 +52401,45 @@ Keyword Index
* declaring static data in C++: Static Definitions. (line 6)
* defining static data in C++: Static Definitions. (line 6)
* dependencies for make as output: Environment Variables.
- (line 155)
-* dependencies for make as output <1>: Environment Variables.
- (line 171)
-* dependencies, 'make': Preprocessor Options.
+ (line 157)
+* dependencies, make: Preprocessor Options.
(line 185)
* DEPENDENCIES_OUTPUT: Environment Variables.
- (line 154)
+ (line 156)
* dependent name lookup: Name lookup. (line 6)
-* 'deprecated' function attribute: Function Attributes.
- (line 258)
-* 'deprecated' type attribute: Type Attributes. (line 206)
-* 'deprecated' variable attribute: Variable Attributes.
- (line 114)
+* deprecated function attribute: Function Attributes.
+ (line 260)
+* deprecated type attribute: Type Attributes. (line 205)
+* deprecated variable attribute: Variable Attributes.
+ (line 115)
* designated initializers: Designated Inits. (line 6)
-* 'designated_init' type attribute: Type Attributes. (line 284)
-* designator lists: Designated Inits. (line 96)
+* designated_init type attribute: Type Attributes. (line 283)
+* designator lists: Designated Inits. (line 97)
* designators: Designated Inits. (line 64)
-* 'destructor' function attribute: Function Attributes.
- (line 236)
-* 'df' integer suffix: Decimal Float. (line 6)
-* 'DF' integer suffix: Decimal Float. (line 6)
+* destructor function attribute: Function Attributes.
+ (line 238)
+* DF integer suffix: Decimal Float. (line 6)
+* df integer suffix: Decimal Float. (line 6)
* dgettext: Other Builtins. (line 6)
* diagnostic messages: Language Independent Options.
(line 6)
* dialect options: C Dialect Options. (line 6)
-* digits in constraint: Simple Constraints. (line 125)
+* digits in constraint: Simple Constraints. (line 127)
* directory options: Directory Options. (line 6)
-* 'disinterrupt' function attribute, Epiphany: Function Attributes.
- (line 278)
-* 'disinterrupt' function attribute, MeP: Function Attributes.
- (line 278)
-* 'dl' integer suffix: Decimal Float. (line 6)
-* 'DL' integer suffix: Decimal Float. (line 6)
-* 'dllexport' function attribute: Function Attributes.
- (line 283)
-* 'dllexport' variable attribute: Variable Attributes.
- (line 308)
-* 'dllimport' function attribute: Function Attributes.
- (line 315)
-* 'dllimport' variable attribute: Variable Attributes.
- (line 304)
+* disinterrupt function attribute, Epiphany: Function Attributes.
+ (line 280)
+* disinterrupt function attribute, MeP: Function Attributes.
+ (line 280)
+* DL integer suffix: Decimal Float. (line 6)
+* dl integer suffix: Decimal Float. (line 6)
+* dllexport function attribute: Function Attributes.
+ (line 285)
+* dllexport variable attribute: Variable Attributes.
+ (line 311)
+* dllimport function attribute: Function Attributes.
+ (line 319)
+* dllimport variable attribute: Variable Attributes.
+ (line 307)
* dollar sign: Multi-Alternative. (line 42)
* dollar signs in identifier names: Dollar Signs. (line 6)
* double-word arithmetic: Long Long. (line 6)
@@ -52020,15 +52447,15 @@ Keyword Index
* drem: Other Builtins. (line 6)
* dremf: Other Builtins. (line 6)
* dreml: Other Builtins. (line 6)
-* 'E' in constraint: Simple Constraints. (line 87)
+* E in constraint: Simple Constraints. (line 89)
* earlyclobber operand: Modifiers. (line 25)
* eight-bit data on the H8/300, H8/300H, and H8S: Variable Attributes.
- (line 403)
-* 'eightbit_data' variable attribute, H8/300: Variable Attributes.
- (line 403)
-* 'EIND': AVR Options. (line 243)
+ (line 408)
+* eightbit_data variable attribute, H8/300: Variable Attributes.
+ (line 408)
+* EIND: AVR Options. (line 242)
* empty structures: Empty Structures. (line 6)
-* Enable Cilk Plus: C Dialect Options. (line 289)
+* Enable Cilk Plus: C Dialect Options. (line 288)
* environment variables: Environment Variables.
(line 6)
* erf: Other Builtins. (line 6)
@@ -52037,21 +52464,21 @@ Keyword Index
* erfcl: Other Builtins. (line 6)
* erff: Other Builtins. (line 6)
* erfl: Other Builtins. (line 6)
-* 'error' function attribute: Function Attributes.
- (line 191)
+* error function attribute: Function Attributes.
+ (line 193)
* error GCC_COLORS capability: Language Independent Options.
(line 69)
* error messages: Warnings and Errors.
(line 6)
* escaped newlines: Escaped Newlines. (line 6)
-* 'exception' function attribute: Function Attributes.
- (line 366)
-* exception handler functions, Blackfin: Function Attributes.
+* exception function attribute: Function Attributes.
(line 371)
+* exception handler functions, Blackfin: Function Attributes.
+ (line 376)
* exception handler functions, NDS32: Function Attributes.
- (line 366)
-* 'exception_handler' function attribute: Function Attributes.
(line 371)
+* exception_handler function attribute: Function Attributes.
+ (line 376)
* exclamation point: Multi-Alternative. (line 33)
* exit: Other Builtins. (line 6)
* exp: Other Builtins. (line 6)
@@ -52069,31 +52496,31 @@ Keyword Index
* expm1l: Other Builtins. (line 6)
* expressions containing statements: Statement Exprs. (line 6)
* expressions, constructor: Compound Literals. (line 6)
-* extended 'asm': Extended Asm. (line 6)
-* extensible constraints: Simple Constraints. (line 161)
-* extensions, '?:': Conditionals. (line 6)
+* extended asm: Extended Asm. (line 6)
+* extensible constraints: Simple Constraints. (line 163)
+* extensions, ?:: Conditionals. (line 6)
* extensions, C language: C Extensions. (line 6)
* extensions, C++ language: C++ Extensions. (line 6)
* external declaration scope: Incompatibilities. (line 80)
-* 'externally_visible' function attribute: Function Attributes.
- (line 377)
-* 'F' in constraint: Simple Constraints. (line 92)
+* externally_visible function attribute: Function Attributes.
+ (line 382)
+* F in constraint: Simple Constraints. (line 94)
* fabs: Other Builtins. (line 6)
* fabsf: Other Builtins. (line 6)
* fabsl: Other Builtins. (line 6)
-* 'far' function attribute: Function Attributes.
- (line 390)
-* 'far' function attribute, MIPS: Function Attributes.
- (line 913)
-* 'far' type attribute, MeP: Type Attributes. (line 348)
-* 'far' variable attribute, MeP: Variable Attributes.
- (line 478)
-* 'fastcall' function attribute, x86-32: Function Attributes.
- (line 402)
-* 'fast_interrupt' function attribute, M32C: Function Attributes.
- (line 396)
-* 'fast_interrupt' function attribute, RX: Function Attributes.
- (line 396)
+* far function attribute: Function Attributes.
+ (line 395)
+* far function attribute, MIPS: Function Attributes.
+ (line 924)
+* far type attribute, MeP: Type Attributes. (line 349)
+* far variable attribute, MeP: Variable Attributes.
+ (line 485)
+* fast_interrupt function attribute, M32C: Function Attributes.
+ (line 400)
+* fast_interrupt function attribute, RX: Function Attributes.
+ (line 400)
+* fastcall function attribute, x86-32: Function Attributes.
+ (line 406)
* fatal signal: Bug Criteria. (line 9)
* fdim: Other Builtins. (line 6)
* fdimf: Other Builtins. (line 6)
@@ -52104,12 +52531,12 @@ Keyword Index
* file name suffix: Overall Options. (line 14)
* file names: Link Options. (line 10)
* fixed-point types: Fixed-Point. (line 6)
-* 'flatten' function attribute: Function Attributes.
- (line 184)
+* flatten function attribute: Function Attributes.
+ (line 186)
* flexible array members: Zero Length. (line 6)
-* 'float' as function value type: Incompatibilities. (line 141)
+* float as function value type: Incompatibilities. (line 141)
* floating point precision: Disappointments. (line 68)
-* floating-point precision: Optimize Options. (line 2037)
+* floating-point precision: Optimize Options. (line 2043)
* floor: Other Builtins. (line 6)
* floorf: Other Builtins. (line 6)
* floorl: Other Builtins. (line 6)
@@ -52125,15 +52552,15 @@ Keyword Index
* fmod: Other Builtins. (line 6)
* fmodf: Other Builtins. (line 6)
* fmodl: Other Builtins. (line 6)
-* 'force_align_arg_pointer' function attribute, x86: Function Attributes.
- (line 1363)
-* 'format' function attribute: Function Attributes.
- (line 420)
-* 'format_arg' function attribute: Function Attributes.
- (line 485)
+* force_align_arg_pointer function attribute, x86: Function Attributes.
+ (line 1368)
+* format function attribute: Function Attributes.
+ (line 424)
+* format_arg function attribute: Function Attributes.
+ (line 490)
* Fortran: G++ and GCC. (line 6)
-* 'forwarder_section' function attribute, Epiphany: Function Attributes.
- (line 723)
+* forwarder_section function attribute, Epiphany: Function Attributes.
+ (line 729)
* forwarding calls: Constructing Calls. (line 6)
* fprintf: Other Builtins. (line 6)
* fprintf_unlocked: Other Builtins. (line 6)
@@ -52147,9 +52574,9 @@ Keyword Index
* frexpl: Other Builtins. (line 6)
* FRV Options: FRV Options. (line 6)
* fscanf: Other Builtins. (line 6)
-* 'fscanf', and constant strings: Incompatibilities. (line 17)
+* fscanf, and constant strings: Incompatibilities. (line 17)
* function addressability on the M32R/D: Function Attributes.
- (line 969)
+ (line 978)
* function attributes: Function Attributes.
(line 6)
* function pointers, arithmetic: Pointer Arith. (line 6)
@@ -52158,24 +52585,28 @@ Keyword Index
* function versions: Function Multiversioning.
(line 6)
* function without prologue/epilogue code: Function Attributes.
- (line 1036)
+ (line 1040)
* function, size of pointer to: Pointer Arith. (line 6)
+* function_vector function attribute, H8/300: Function Attributes.
+ (line 537)
+* function_vector function attribute, M16C/M32C: Function Attributes.
+ (line 537)
+* function_vector function attribute, SH: Function Attributes.
+ (line 537)
* functions in arbitrary sections: Function Attributes.
(line 6)
* functions that are dynamically resolved: Function Attributes.
(line 6)
* functions that are passed arguments in registers on x86-32: Function Attributes.
(line 6)
-* functions that are passed arguments in registers on x86-32 <1>: Function Attributes.
- (line 1328)
* functions that behave like malloc: Function Attributes.
(line 6)
* functions that do not handle memory bank switching on 68HC11/68HC12: Function Attributes.
- (line 1047)
+ (line 1051)
* functions that do not pop the argument stack on x86-32: Function Attributes.
(line 6)
* functions that do pop the argument stack on x86-32: Function Attributes.
- (line 215)
+ (line 217)
* functions that have different compilation options on x86-32: Function Attributes.
(line 6)
* functions that have different optimization options: Function Attributes.
@@ -52186,34 +52617,22 @@ Keyword Index
(line 6)
* functions that pop the argument stack on x86-32: Function Attributes.
(line 6)
-* functions that pop the argument stack on x86-32 <1>: Function Attributes.
- (line 402)
-* functions that pop the argument stack on x86-32 <2>: Function Attributes.
- (line 410)
-* functions that pop the argument stack on x86-32 <3>: Function Attributes.
- (line 1495)
* functions that return more than once: Function Attributes.
(line 6)
* functions with non-null pointer arguments: Function Attributes.
(line 6)
-* functions with 'printf', 'scanf', 'strftime' or 'strfmon' style arguments: Function Attributes.
+* functions with printf, scanf, strftime or strfmon style arguments: Function Attributes.
(line 6)
-* 'function_vector' function attribute, H8/300: Function Attributes.
- (line 531)
-* 'function_vector' function attribute, M16C/M32C: Function Attributes.
- (line 531)
-* 'function_vector' function attribute, SH: Function Attributes.
- (line 531)
-* 'G' in constraint: Simple Constraints. (line 96)
-* 'g' in constraint: Simple Constraints. (line 118)
+* g in constraint: Simple Constraints. (line 120)
+* G in constraint: Simple Constraints. (line 98)
* g++: Invoking G++. (line 14)
* G++: G++ and GCC. (line 30)
* gamma: Other Builtins. (line 6)
+* gamma_r: Other Builtins. (line 6)
* gammaf: Other Builtins. (line 6)
* gammaf_r: Other Builtins. (line 6)
* gammal: Other Builtins. (line 6)
* gammal_r: Other Builtins. (line 6)
-* gamma_r: Other Builtins. (line 6)
* GCC: G++ and GCC. (line 6)
* GCC command options: Invoking GCC. (line 6)
* GCC_COLORS environment variable: Language Independent Options.
@@ -52222,59 +52641,58 @@ Keyword Index
(line 52)
* GCC_EXEC_PREFIX: Environment Variables.
(line 57)
-* 'gcc_struct' type attribute, PowerPC: Type Attributes. (line 359)
-* 'gcc_struct' type attribute, x86: Type Attributes. (line 391)
-* 'gcc_struct' variable attribute, PowerPC: Variable Attributes.
- (line 506)
-* 'gcc_struct' variable attribute, x86: Variable Attributes.
- (line 527)
-* 'gcov': Debugging Options. (line 724)
+* gcc_struct type attribute, PowerPC: Type Attributes. (line 360)
+* gcc_struct type attribute, x86: Type Attributes. (line 392)
+* gcc_struct variable attribute, PowerPC: Variable Attributes.
+ (line 515)
+* gcc_struct variable attribute, x86: Variable Attributes.
+ (line 536)
+* gcov: Debugging Options. (line 722)
* gettext: Other Builtins. (line 6)
-* global offset table: Code Gen Options. (line 279)
-* global register after 'longjmp': Global Reg Vars. (line 65)
+* global offset table: Code Gen Options. (line 280)
+* global register after longjmp: Global Reg Vars. (line 65)
* global register variables: Global Reg Vars. (line 6)
* GNAT: G++ and GCC. (line 30)
* GNU C Compiler: G++ and GCC. (line 6)
* GNU Compiler Collection: G++ and GCC. (line 6)
-* 'gnu_inline' function attribute: Function Attributes.
+* gnu_inline function attribute: Function Attributes.
(line 136)
* Go: G++ and GCC. (line 6)
* goto with computed label: Labels as Values. (line 6)
-* 'gprof': Debugging Options. (line 649)
+* gprof: Debugging Options. (line 644)
* grouping options: Invoking GCC. (line 26)
-* 'H' in constraint: Simple Constraints. (line 96)
+* H in constraint: Simple Constraints. (line 98)
* half-precision floating point: Half-Precision. (line 6)
* hardware models and configurations, specifying: Submodel Options.
(line 6)
* hex floats: Hex Floats. (line 6)
* highlight, color, colour: Language Independent Options.
(line 35)
-* 'hk' fixed-suffix: Fixed-Point. (line 6)
-* 'HK' fixed-suffix: Fixed-Point. (line 6)
+* HK fixed-suffix: Fixed-Point. (line 6)
+* hk fixed-suffix: Fixed-Point. (line 6)
+* hosted environment <1>: C Dialect Options. (line 247)
* hosted environment: Standards. (line 13)
-* hosted environment <1>: C Dialect Options. (line 244)
-* hosted environment <2>: C Dialect Options. (line 252)
* hosted implementation: Standards. (line 13)
-* 'hot' function attribute: Function Attributes.
- (line 1272)
-* 'hot' label attribute: Label Attributes. (line 36)
-* 'hotpatch' function attribute, S/390: Function Attributes.
- (line 1023)
+* hot function attribute: Function Attributes.
+ (line 1276)
+* hot label attribute: Label Attributes. (line 36)
+* hotpatch function attribute, S/390: Function Attributes.
+ (line 1028)
* HPPA Options: HPPA Options. (line 6)
-* 'hr' fixed-suffix: Fixed-Point. (line 6)
-* 'HR' fixed-suffix: Fixed-Point. (line 6)
+* HR fixed-suffix: Fixed-Point. (line 6)
+* hr fixed-suffix: Fixed-Point. (line 6)
* hypot: Other Builtins. (line 6)
* hypotf: Other Builtins. (line 6)
* hypotl: Other Builtins. (line 6)
-* 'i' in constraint: Simple Constraints. (line 68)
-* 'I' in constraint: Simple Constraints. (line 79)
+* I in constraint: Simple Constraints. (line 81)
+* i in constraint: Simple Constraints. (line 70)
* IA-64 Options: IA-64 Options. (line 6)
* IBM RS/6000 and PowerPC Options: RS/6000 and PowerPC Options.
(line 6)
* identifier names, dollar signs in: Dollar Signs. (line 6)
* identifiers, names in assembler code: Asm Labels. (line 6)
-* 'ifunc' function attribute: Function Attributes.
- (line 592)
+* ifunc function attribute: Function Attributes.
+ (line 598)
* ilogb: Other Builtins. (line 6)
* ilogbf: Other Builtins. (line 6)
* ilogbl: Other Builtins. (line 6)
@@ -52283,29 +52701,29 @@ Keyword Index
(line 6)
* implementation-defined behavior, C++ language: C++ Implementation.
(line 6)
-* implied '#pragma implementation': C++ Interface. (line 43)
+* implied #pragma implementation: C++ Interface. (line 43)
* incompatibilities of GCC: Incompatibilities. (line 6)
* increment operators: Bug Criteria. (line 17)
* index: Other Builtins. (line 6)
* indirect calls, ARC: Function Attributes.
- (line 875)
+ (line 886)
* indirect calls, ARM: Function Attributes.
- (line 875)
+ (line 886)
* indirect calls, Blackfin: Function Attributes.
- (line 899)
+ (line 910)
* indirect calls, Epiphany: Function Attributes.
- (line 875)
+ (line 886)
* indirect calls, MIPS: Function Attributes.
- (line 913)
+ (line 924)
* indirect calls, PowerPC: Function Attributes.
- (line 899)
+ (line 910)
+* init_priority variable attribute: C++ Attributes. (line 50)
* initializations in expressions: Compound Literals. (line 6)
* initializers with labeled elements: Designated Inits. (line 6)
* initializers, non-constant: Initializers. (line 6)
-* 'init_priority' variable attribute: C++ Attributes. (line 50)
* inline assembly language: Using Assembly Language with C.
(line 6)
-* 'inline' automatic for C++ member fns: Inline. (line 71)
+* inline automatic for C++ member fns: Inline. (line 71)
* inline functions: Inline. (line 6)
* inline functions, omission of: Inline. (line 51)
* inlining and C++ pragmas: C++ Interface. (line 57)
@@ -52313,58 +52731,58 @@ Keyword Index
* integrating function code: Inline. (line 6)
* interface and implementation headers, C++: C++ Interface. (line 6)
* intermediate C version, nonexistent: G++ and GCC. (line 35)
-* 'interrupt' function attribute, ARC: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, ARM: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, AVR: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, CR16: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, Epiphany: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, M32C: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, M32R/D: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, m68k: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, MeP: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, MIPS: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, MSP430: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, NDS32: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, RL78: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, RX: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, Visium: Function Attributes.
- (line 632)
-* 'interrupt' function attribute, Xstormy16: Function Attributes.
- (line 632)
-* 'interrupt_handler' function attribute, Blackfin: Function Attributes.
- (line 811)
-* 'interrupt_handler' function attribute, H8/300: Function Attributes.
- (line 811)
-* 'interrupt_handler' function attribute, m68k: Function Attributes.
- (line 811)
-* 'interrupt_handler' function attribute, SH: Function Attributes.
- (line 811)
-* 'interrupt_thread' function attribute, fido: Function Attributes.
- (line 817)
+* interrupt function attribute, ARC: Function Attributes.
+ (line 638)
+* interrupt function attribute, ARM: Function Attributes.
+ (line 638)
+* interrupt function attribute, AVR: Function Attributes.
+ (line 638)
+* interrupt function attribute, CR16: Function Attributes.
+ (line 638)
+* interrupt function attribute, Epiphany: Function Attributes.
+ (line 638)
+* interrupt function attribute, M32C: Function Attributes.
+ (line 638)
+* interrupt function attribute, M32R/D: Function Attributes.
+ (line 638)
+* interrupt function attribute, m68k: Function Attributes.
+ (line 638)
+* interrupt function attribute, MeP: Function Attributes.
+ (line 638)
+* interrupt function attribute, MIPS: Function Attributes.
+ (line 638)
+* interrupt function attribute, MSP430: Function Attributes.
+ (line 638)
+* interrupt function attribute, NDS32: Function Attributes.
+ (line 638)
+* interrupt function attribute, RL78: Function Attributes.
+ (line 638)
+* interrupt function attribute, RX: Function Attributes.
+ (line 638)
+* interrupt function attribute, Visium: Function Attributes.
+ (line 638)
+* interrupt function attribute, Xstormy16: Function Attributes.
+ (line 638)
+* interrupt_handler function attribute, Blackfin: Function Attributes.
+ (line 821)
+* interrupt_handler function attribute, H8/300: Function Attributes.
+ (line 821)
+* interrupt_handler function attribute, m68k: Function Attributes.
+ (line 821)
+* interrupt_handler function attribute, SH: Function Attributes.
+ (line 821)
+* interrupt_thread function attribute, fido: Function Attributes.
+ (line 828)
* introduction: Top. (line 6)
* invalid assembly code: Bug Criteria. (line 12)
* invalid input: Bug Criteria. (line 42)
-* invoking 'g++': Invoking G++. (line 22)
-* 'io' variable attribute, AVR: Variable Attributes.
- (line 347)
-* 'io' variable attribute, MeP: Variable Attributes.
- (line 484)
-* 'io_low' variable attribute, AVR: Variable Attributes.
- (line 365)
+* invoking g++: Invoking G++. (line 22)
+* io variable attribute, AVR: Variable Attributes.
+ (line 351)
+* io variable attribute, MeP: Variable Attributes.
+ (line 491)
+* io_low variable attribute, AVR: Variable Attributes.
+ (line 369)
* isalnum: Other Builtins. (line 6)
* isalpha: Other Builtins. (line 6)
* isascii: Other Builtins. (line 6)
@@ -52387,8 +52805,8 @@ Keyword Index
* ISO/IEC 9899: Standards. (line 13)
* isprint: Other Builtins. (line 6)
* ispunct: Other Builtins. (line 6)
-* 'isr' function attribute, ARM: Function Attributes.
- (line 825)
+* isr function attribute, ARM: Function Attributes.
+ (line 836)
* isspace: Other Builtins. (line 6)
* isupper: Other Builtins. (line 6)
* iswalnum: Other Builtins. (line 6)
@@ -52411,38 +52829,36 @@ Keyword Index
* j1f: Other Builtins. (line 6)
* j1l: Other Builtins. (line 6)
* Java: G++ and GCC. (line 6)
-* 'java_interface' type attribute: C++ Attributes. (line 71)
+* java_interface type attribute: C++ Attributes. (line 70)
* jn: Other Builtins. (line 6)
* jnf: Other Builtins. (line 6)
* jnl: Other Builtins. (line 6)
-* 'k' fixed-suffix: Fixed-Point. (line 6)
-* 'K' fixed-suffix: Fixed-Point. (line 6)
-* 'keep_interrupts_masked' function attribute, MIPS: Function Attributes.
- (line 745)
+* K fixed-suffix: Fixed-Point. (line 6)
+* k fixed-suffix: Fixed-Point. (line 6)
+* keep_interrupts_masked function attribute, MIPS: Function Attributes.
+ (line 751)
* keywords, alternate: Alternate Keywords. (line 6)
* known causes of trouble: Trouble. (line 6)
-* 'kspisusp' function attribute, Blackfin: Function Attributes.
- (line 829)
-* 'l1_data' variable attribute, Blackfin: Variable Attributes.
- (line 385)
-* 'l1_data_A' variable attribute, Blackfin: Variable Attributes.
- (line 385)
-* 'l1_data_B' variable attribute, Blackfin: Variable Attributes.
- (line 385)
-* 'l1_text' function attribute, Blackfin: Function Attributes.
- (line 834)
-* 'l2' function attribute, Blackfin: Function Attributes.
+* kspisusp function attribute, Blackfin: Function Attributes.
(line 840)
-* 'l2' variable attribute, Blackfin: Variable Attributes.
- (line 393)
+* l1_data variable attribute, Blackfin: Variable Attributes.
+ (line 390)
+* l1_data_A variable attribute, Blackfin: Variable Attributes.
+ (line 390)
+* l1_data_B variable attribute, Blackfin: Variable Attributes.
+ (line 390)
+* l1_text function attribute, Blackfin: Function Attributes.
+ (line 845)
+* l2 function attribute, Blackfin: Function Attributes.
+ (line 851)
+* l2 variable attribute, Blackfin: Variable Attributes.
+ (line 398)
* Label Attributes: Label Attributes. (line 6)
* labeled elements in initializers: Designated Inits. (line 6)
* labels as values: Labels as Values. (line 6)
* labs: Other Builtins. (line 6)
* LANG: Environment Variables.
(line 21)
-* LANG <1>: Environment Variables.
- (line 106)
* language dialect options: C Dialect Options. (line 6)
* LC_ALL: Environment Variables.
(line 21)
@@ -52453,28 +52869,28 @@ Keyword Index
* ldexp: Other Builtins. (line 6)
* ldexpf: Other Builtins. (line 6)
* ldexpl: Other Builtins. (line 6)
-* 'leaf' function attribute: Function Attributes.
- (line 846)
+* leaf function attribute: Function Attributes.
+ (line 857)
* length-zero arrays: Zero Length. (line 6)
* lgamma: Other Builtins. (line 6)
+* lgamma_r: Other Builtins. (line 6)
* lgammaf: Other Builtins. (line 6)
* lgammaf_r: Other Builtins. (line 6)
* lgammal: Other Builtins. (line 6)
* lgammal_r: Other Builtins. (line 6)
-* lgamma_r: Other Builtins. (line 6)
* Libraries: Link Options. (line 30)
* LIBRARY_PATH: Environment Variables.
(line 97)
* link options: Link Options. (line 6)
-* linker script: Link Options. (line 238)
-* 'lk' fixed-suffix: Fixed-Point. (line 6)
-* 'LK' fixed-suffix: Fixed-Point. (line 6)
-* 'LL' integer suffix: Long Long. (line 6)
+* linker script: Link Options. (line 242)
+* LK fixed-suffix: Fixed-Point. (line 6)
+* lk fixed-suffix: Fixed-Point. (line 6)
+* LL integer suffix: Long Long. (line 6)
* llabs: Other Builtins. (line 6)
-* 'llk' fixed-suffix: Fixed-Point. (line 6)
-* 'LLK' fixed-suffix: Fixed-Point. (line 6)
-* 'llr' fixed-suffix: Fixed-Point. (line 6)
-* 'LLR' fixed-suffix: Fixed-Point. (line 6)
+* LLK fixed-suffix: Fixed-Point. (line 6)
+* llk fixed-suffix: Fixed-Point. (line 6)
+* LLR fixed-suffix: Fixed-Point. (line 6)
+* llr fixed-suffix: Fixed-Point. (line 6)
* llrint: Other Builtins. (line 6)
* llrintf: Other Builtins. (line 6)
* llrintl: Other Builtins. (line 6)
@@ -52482,7 +52898,7 @@ Keyword Index
* llroundf: Other Builtins. (line 6)
* llroundl: Other Builtins. (line 6)
* LM32 options: LM32 Options. (line 6)
-* load address instruction: Simple Constraints. (line 152)
+* load address instruction: Simple Constraints. (line 154)
* local labels: Local Labels. (line 6)
* local variables in macros: Typeof. (line 46)
* local variables, specifying registers: Local Reg Vars. (line 6)
@@ -52507,31 +52923,31 @@ Keyword Index
* logbl: Other Builtins. (line 6)
* logf: Other Builtins. (line 6)
* logl: Other Builtins. (line 6)
-* 'long long' data types: Long Long. (line 6)
-* 'longcall' function attribute, Blackfin: Function Attributes.
- (line 899)
-* 'longcall' function attribute, PowerPC: Function Attributes.
- (line 899)
+* long long data types: Long Long. (line 6)
+* long_call function attribute, ARC: Function Attributes.
+ (line 886)
+* long_call function attribute, ARM: Function Attributes.
+ (line 886)
+* long_call function attribute, Epiphany: Function Attributes.
+ (line 886)
+* long_call function attribute, MIPS: Function Attributes.
+ (line 924)
+* longcall function attribute, Blackfin: Function Attributes.
+ (line 910)
+* longcall function attribute, PowerPC: Function Attributes.
+ (line 910)
* longjmp: Global Reg Vars. (line 65)
-* 'longjmp' incompatibilities: Incompatibilities. (line 39)
-* 'longjmp' warnings: Warning Options. (line 705)
-* 'long_call' function attribute, ARC: Function Attributes.
- (line 875)
-* 'long_call' function attribute, ARM: Function Attributes.
- (line 875)
-* 'long_call' function attribute, Epiphany: Function Attributes.
- (line 875)
-* 'long_call' function attribute, MIPS: Function Attributes.
- (line 913)
-* 'lr' fixed-suffix: Fixed-Point. (line 6)
-* 'LR' fixed-suffix: Fixed-Point. (line 6)
+* longjmp incompatibilities: Incompatibilities. (line 39)
+* longjmp warnings: Warning Options. (line 712)
+* LR fixed-suffix: Fixed-Point. (line 6)
+* lr fixed-suffix: Fixed-Point. (line 6)
* lrint: Other Builtins. (line 6)
* lrintf: Other Builtins. (line 6)
* lrintl: Other Builtins. (line 6)
* lround: Other Builtins. (line 6)
* lroundf: Other Builtins. (line 6)
* lroundl: Other Builtins. (line 6)
-* 'm' in constraint: Simple Constraints. (line 17)
+* m in constraint: Simple Constraints. (line 17)
* M32C options: M32C Options. (line 6)
* M32R/D options: M32R/D Options. (line 6)
* M680x0 options: M680x0 Options. (line 6)
@@ -52544,17 +52960,17 @@ Keyword Index
* macros, local variables in: Typeof. (line 46)
* macros, statements in expressions: Statement Exprs. (line 6)
* macros, types of arguments: Typeof. (line 6)
-* 'make': Preprocessor Options.
+* make: Preprocessor Options.
(line 185)
* malloc: Other Builtins. (line 6)
-* 'malloc' function attribute: Function Attributes.
- (line 923)
-* matching constraint: Simple Constraints. (line 137)
-* 'may_alias' type attribute: Type Attributes. (line 234)
+* malloc function attribute: Function Attributes.
+ (line 934)
+* matching constraint: Simple Constraints. (line 139)
+* may_alias type attribute: Type Attributes. (line 233)
* MCore options: MCore Options. (line 6)
-* 'medium_call' function attribute, ARC: Function Attributes.
- (line 875)
-* member fns, automatically 'inline': Inline. (line 71)
+* medium_call function attribute, ARC: Function Attributes.
+ (line 886)
+* member fns, automatically inline: Inline. (line 71)
* memchr: Other Builtins. (line 6)
* memcmp: Other Builtins. (line 6)
* memcpy: Other Builtins. (line 6)
@@ -52569,85 +52985,85 @@ Keyword Index
* messages, warning and error: Warnings and Errors.
(line 6)
* MicroBlaze Options: MicroBlaze Options. (line 6)
-* 'micromips' function attribute: Function Attributes.
- (line 952)
+* micromips function attribute: Function Attributes.
+ (line 962)
* middle-operands, omitted: Conditionals. (line 6)
* MIPS options: MIPS Options. (line 6)
-* 'mips16' function attribute, MIPS: Function Attributes.
- (line 936)
+* mips16 function attribute, MIPS: Function Attributes.
+ (line 947)
* misunderstandings in C++: C++ Misunderstandings.
(line 6)
* mixed declarations and code: Mixed Declarations. (line 6)
* mixing assembly language and C: Using Assembly Language with C.
(line 6)
-* 'mktemp', and constant strings: Incompatibilities. (line 13)
+* mktemp, and constant strings: Incompatibilities. (line 13)
* MMIX Options: MMIX Options. (line 6)
* MN10300 options: MN10300 Options. (line 6)
-* 'mode' variable attribute: Variable Attributes.
- (line 134)
-* 'model' function attribute, M32R/D: Function Attributes.
- (line 969)
-* 'model' variable attribute, IA-64: Variable Attributes.
- (line 425)
-* 'model-name' variable attribute, M32R/D: Variable Attributes.
- (line 440)
+* mode variable attribute: Variable Attributes.
+ (line 135)
+* model function attribute, M32R/D: Function Attributes.
+ (line 978)
+* model variable attribute, IA-64: Variable Attributes.
+ (line 431)
+* model-name variable attribute, M32R/D: Variable Attributes.
+ (line 446)
* modf: Other Builtins. (line 6)
* modff: Other Builtins. (line 6)
* modfl: Other Builtins. (line 6)
* modifiers in constraints: Modifiers. (line 6)
* Moxie Options: Moxie Options. (line 6)
+* ms_abi function attribute, x86: Function Attributes.
+ (line 999)
+* ms_hook_prologue function attribute, x86: Function Attributes.
+ (line 1022)
+* ms_struct type attribute, PowerPC: Type Attributes. (line 360)
+* ms_struct type attribute, x86: Type Attributes. (line 392)
+* ms_struct variable attribute, PowerPC: Variable Attributes.
+ (line 515)
+* ms_struct variable attribute, x86: Variable Attributes.
+ (line 536)
* MSP430 Options: MSP430 Options. (line 6)
-* 'ms_abi' function attribute, x86: Function Attributes.
- (line 991)
-* 'ms_hook_prologue' function attribute, x86: Function Attributes.
- (line 1016)
-* 'ms_struct' type attribute, PowerPC: Type Attributes. (line 359)
-* 'ms_struct' type attribute, x86: Type Attributes. (line 391)
-* 'ms_struct' variable attribute, PowerPC: Variable Attributes.
- (line 506)
-* 'ms_struct' variable attribute, x86: Variable Attributes.
- (line 527)
* multiple alternative constraints: Multi-Alternative. (line 6)
* multiprecision arithmetic: Long Long. (line 6)
-* 'n' in constraint: Simple Constraints. (line 73)
-* 'naked' function attribute, ARM: Function Attributes.
- (line 1036)
-* 'naked' function attribute, AVR: Function Attributes.
- (line 1036)
-* 'naked' function attribute, MCORE: Function Attributes.
- (line 1036)
-* 'naked' function attribute, MSP430: Function Attributes.
- (line 1036)
-* 'naked' function attribute, NDS32: Function Attributes.
- (line 1036)
-* 'naked' function attribute, RL78: Function Attributes.
- (line 1036)
-* 'naked' function attribute, RX: Function Attributes.
- (line 1036)
-* 'naked' function attribute, SPU: Function Attributes.
- (line 1036)
+* n in constraint: Simple Constraints. (line 75)
+* naked function attribute, ARM: Function Attributes.
+ (line 1040)
+* naked function attribute, AVR: Function Attributes.
+ (line 1040)
+* naked function attribute, MCORE: Function Attributes.
+ (line 1040)
+* naked function attribute, MSP430: Function Attributes.
+ (line 1040)
+* naked function attribute, NDS32: Function Attributes.
+ (line 1040)
+* naked function attribute, RL78: Function Attributes.
+ (line 1040)
+* naked function attribute, RX: Function Attributes.
+ (line 1040)
+* naked function attribute, SPU: Function Attributes.
+ (line 1040)
* Named Address Spaces: Named Address Spaces.
(line 6)
* names used in assembler code: Asm Labels. (line 6)
* naming convention, implementation headers: C++ Interface. (line 43)
* NDS32 Options: NDS32 Options. (line 6)
-* 'near' function attribute, MeP: Function Attributes.
- (line 1047)
-* 'near' function attribute, MIPS: Function Attributes.
- (line 913)
-* 'near' type attribute, MeP: Type Attributes. (line 348)
-* 'near' variable attribute, MeP: Variable Attributes.
- (line 472)
+* near function attribute, MeP: Function Attributes.
+ (line 1051)
+* near function attribute, MIPS: Function Attributes.
+ (line 924)
+* near type attribute, MeP: Type Attributes. (line 349)
+* near variable attribute, MeP: Variable Attributes.
+ (line 479)
* nearbyint: Other Builtins. (line 6)
* nearbyintf: Other Builtins. (line 6)
* nearbyintl: Other Builtins. (line 6)
-* 'nested' function attribute, NDS32: Function Attributes.
- (line 773)
+* nested function attribute, NDS32: Function Attributes.
+ (line 779)
* nested functions: Nested Functions. (line 6)
-* 'nested_ready' function attribute, NDS32: Function Attributes.
- (line 777)
-* 'nesting' function attribute, Blackfin: Function Attributes.
- (line 1052)
+* nested_ready function attribute, NDS32: Function Attributes.
+ (line 785)
+* nesting function attribute, Blackfin: Function Attributes.
+ (line 1056)
* newlines (escaped): Escaped Newlines. (line 6)
* nextafter: Other Builtins. (line 6)
* nextafterf: Other Builtins. (line 6)
@@ -52655,78 +53071,78 @@ Keyword Index
* nexttoward: Other Builtins. (line 6)
* nexttowardf: Other Builtins. (line 6)
* nexttowardl: Other Builtins. (line 6)
-* NFC: Warning Options. (line 1467)
-* NFKC: Warning Options. (line 1467)
+* NFC: Warning Options. (line 1481)
+* NFKC: Warning Options. (line 1481)
* Nios II options: Nios II Options. (line 6)
-* 'nmi' function attribute, NDS32: Function Attributes.
- (line 1350)
+* nmi function attribute, NDS32: Function Attributes.
+ (line 1354)
* NMI handler functions on the Blackfin processor: Function Attributes.
- (line 1057)
-* 'nmi_handler' function attribute, Blackfin: Function Attributes.
- (line 1057)
-* 'noclone' function attribute: Function Attributes.
- (line 1096)
-* 'nocommon' variable attribute: Variable Attributes.
- (line 105)
-* 'nocompression' function attribute, MIPS: Function Attributes.
- (line 1063)
-* 'noinline' function attribute: Function Attributes.
- (line 1085)
-* 'nomicromips' function attribute: Function Attributes.
- (line 952)
-* 'nomips16' function attribute, MIPS: Function Attributes.
- (line 936)
+ (line 1061)
+* nmi_handler function attribute, Blackfin: Function Attributes.
+ (line 1061)
+* no_icf function attribute: Function Attributes.
+ (line 1106)
+* no_instrument_function function attribute: Function Attributes.
+ (line 1073)
+* no_reorder function attribute: Function Attributes.
+ (line 1134)
+* no_sanitize_address function attribute: Function Attributes.
+ (line 1303)
+* no_sanitize_thread function attribute: Function Attributes.
+ (line 1311)
+* no_sanitize_undefined function attribute: Function Attributes.
+ (line 1316)
+* no_split_stack function attribute: Function Attributes.
+ (line 1078)
+* noclone function attribute: Function Attributes.
+ (line 1100)
+* nocommon variable attribute: Variable Attributes.
+ (line 106)
+* nocompression function attribute, MIPS: Function Attributes.
+ (line 1067)
+* noinline function attribute: Function Attributes.
+ (line 1089)
+* nomicromips function attribute: Function Attributes.
+ (line 962)
+* nomips16 function attribute, MIPS: Function Attributes.
+ (line 947)
* non-constant initializers: Initializers. (line 6)
* non-static inline function: Inline. (line 85)
-* 'nonnull' function attribute: Function Attributes.
- (line 1106)
-* 'noreturn' function attribute: Function Attributes.
- (line 1148)
-* 'nosave_low_regs' function attribute, SH: Function Attributes.
- (line 1186)
+* nonnull function attribute: Function Attributes.
+ (line 1110)
+* noreturn function attribute: Function Attributes.
+ (line 1152)
+* nosave_low_regs function attribute, SH: Function Attributes.
+ (line 1190)
+* not_nested function attribute, NDS32: Function Attributes.
+ (line 782)
* note GCC_COLORS capability: Language Independent Options.
(line 75)
-* 'nothrow' function attribute: Function Attributes.
- (line 1179)
-* 'notshared' type attribute, ARM: Type Attributes. (line 327)
-* 'not_nested' function attribute, NDS32: Function Attributes.
- (line 775)
-* 'no_icf' function attribute: Function Attributes.
- (line 1102)
-* 'no_instrument_function' function attribute: Function Attributes.
- (line 1069)
-* 'no_reorder' function attribute: Function Attributes.
- (line 1130)
-* 'no_sanitize_address' function attribute: Function Attributes.
- (line 1299)
-* 'no_sanitize_thread' function attribute: Function Attributes.
- (line 1307)
-* 'no_sanitize_undefined' function attribute: Function Attributes.
- (line 1312)
-* 'no_split_stack' function attribute: Function Attributes.
- (line 1074)
+* nothrow function attribute: Function Attributes.
+ (line 1183)
+* notshared type attribute, ARM: Type Attributes. (line 328)
* Nvidia PTX options: Nvidia PTX Options. (line 6)
* nvptx options: Nvidia PTX Options. (line 6)
-* 'o' in constraint: Simple Constraints. (line 23)
+* o in constraint: Simple Constraints. (line 23)
* OBJC_INCLUDE_PATH: Environment Variables.
- (line 130)
+ (line 132)
+* Objective-C <1>: Standards. (line 163)
* Objective-C: G++ and GCC. (line 6)
-* Objective-C <1>: Standards. (line 161)
* Objective-C and Objective-C++ options, command-line: Objective-C and Objective-C++ Dialect Options.
(line 6)
+* Objective-C++ <1>: Standards. (line 163)
* Objective-C++: G++ and GCC. (line 6)
-* Objective-C++ <1>: Standards. (line 161)
* offsettable address: Simple Constraints. (line 23)
* old-style function definitions: Function Prototypes.
(line 6)
* omitted middle-operands: Conditionals. (line 6)
* open coding: Inline. (line 6)
-* OpenACC accelerator programming: C Dialect Options. (line 263)
+* OpenACC accelerator programming: C Dialect Options. (line 264)
* OpenMP parallel: C Dialect Options. (line 276)
-* OpenMP SIMD: C Dialect Options. (line 285)
-* operand constraints, 'asm': Constraints. (line 6)
-* 'optimize' function attribute: Function Attributes.
- (line 1192)
+* OpenMP SIMD: C Dialect Options. (line 284)
+* operand constraints, asm: Constraints. (line 6)
+* optimize function attribute: Function Attributes.
+ (line 1196)
* optimize options: Optimize Options. (line 6)
* options to control diagnostics formatting: Language Independent Options.
(line 6)
@@ -52748,37 +53164,37 @@ Keyword Index
(line 6)
* order of evaluation, side effects: Non-bugs. (line 196)
* order of options: Invoking GCC. (line 30)
-* 'OS_main' function attribute, AVR: Function Attributes.
- (line 1210)
-* 'OS_task' function attribute, AVR: Function Attributes.
- (line 1210)
-* other register constraints: Simple Constraints. (line 161)
+* OS_main function attribute, AVR: Function Attributes.
+ (line 1214)
+* OS_task function attribute, AVR: Function Attributes.
+ (line 1214)
+* other register constraints: Simple Constraints. (line 163)
* output file option: Overall Options. (line 191)
* overloaded virtual function, warning: C++ Dialect Options.
- (line 666)
-* 'p' in constraint: Simple Constraints. (line 152)
-* 'packed' type attribute: Type Attributes. (line 108)
-* 'packed' variable attribute: Variable Attributes.
- (line 145)
+ (line 672)
+* p in constraint: Simple Constraints. (line 154)
+* packed type attribute: Type Attributes. (line 108)
+* packed variable attribute: Variable Attributes.
+ (line 146)
* parameter forward declaration: Variable Length. (line 68)
-* 'partial_save' function attribute, NDS32: Function Attributes.
- (line 785)
+* partial_save function attribute, NDS32: Function Attributes.
+ (line 795)
* Pascal: G++ and GCC. (line 23)
-* 'pcs' function attribute, ARM: Function Attributes.
- (line 1234)
+* pcs function attribute, ARM: Function Attributes.
+ (line 1239)
* PDP-11 Options: PDP-11 Options. (line 6)
-* PIC: Code Gen Options. (line 279)
+* PIC: Code Gen Options. (line 280)
* picoChip options: picoChip Options. (line 6)
* pmf: Bound member functions.
(line 6)
* pointer arguments: Function Attributes.
- (line 226)
-* Pointer Bounds Checker attributes: Function Attributes.
- (line 1318)
+ (line 228)
* Pointer Bounds Checker attributes <1>: Type Attributes. (line 295)
+* Pointer Bounds Checker attributes: Function Attributes.
+ (line 1322)
* Pointer Bounds Checker builtins: Pointer Bounds Checker builtins.
(line 6)
-* Pointer Bounds Checker options: Debugging Options. (line 392)
+* Pointer Bounds Checker options: Debugging Options. (line 387)
* pointer to member function: Bound member functions.
(line 6)
* pointers to arrays: Pointers to Arrays. (line 6)
@@ -52793,13 +53209,13 @@ Keyword Index
* pragma GCC ivdep: Loop-Specific Pragmas.
(line 7)
* pragma GCC optimize: Function Specific Option Pragmas.
- (line 20)
+ (line 19)
* pragma GCC pop_options: Function Specific Option Pragmas.
- (line 31)
+ (line 29)
* pragma GCC push_options: Function Specific Option Pragmas.
- (line 31)
+ (line 29)
* pragma GCC reset_options: Function Specific Option Pragmas.
- (line 39)
+ (line 36)
* pragma GCC target: Function Specific Option Pragmas.
(line 7)
* pragma, address: M32C Pragmas. (line 15)
@@ -52810,14 +53226,13 @@ Keyword Index
* pragma, coprocessor subclass: MeP Pragmas. (line 28)
* pragma, custom io_volatile: MeP Pragmas. (line 7)
* pragma, diagnostic: Diagnostic Pragmas. (line 14)
-* pragma, diagnostic <1>: Diagnostic Pragmas. (line 57)
* pragma, disinterrupt: MeP Pragmas. (line 38)
-* pragma, fini: Solaris Pragmas. (line 20)
-* pragma, init: Solaris Pragmas. (line 26)
-* pragma, longcall: RS/6000 and PowerPC Pragmas.
- (line 14)
+* pragma, fini: Solaris Pragmas. (line 19)
+* pragma, init: Solaris Pragmas. (line 24)
* pragma, long_calls: ARM Pragmas. (line 11)
* pragma, long_calls_off: ARM Pragmas. (line 17)
+* pragma, longcall: RS/6000 and PowerPC Pragmas.
+ (line 14)
* pragma, mark: Darwin Pragmas. (line 11)
* pragma, memregs: M32C Pragmas. (line 7)
* pragma, no_long_calls: ARM Pragmas. (line 14)
@@ -52827,7 +53242,7 @@ Keyword Index
* pragma, push_macro: Push/Pop Macro Pragmas.
(line 11)
* pragma, reason for not using: Function Attributes.
- (line 2042)
+ (line 2049)
* pragma, redefine_extname: Symbol-Renaming Pragmas.
(line 13)
* pragma, segment: Darwin Pragmas. (line 21)
@@ -52837,7 +53252,7 @@ Keyword Index
* pragmas: Pragmas. (line 6)
* pragmas in C++, effect on inlining: C++ Interface. (line 57)
* pragmas, interface and implementation: C++ Interface. (line 6)
-* pragmas, warning of unknown: Warning Options. (line 722)
+* pragmas, warning of unknown: Warning Options. (line 729)
* precompiled headers: Precompiled Headers.
(line 6)
* preprocessing numbers: Incompatibilities. (line 173)
@@ -52846,59 +53261,59 @@ Keyword Index
(line 6)
* printf: Other Builtins. (line 6)
* printf_unlocked: Other Builtins. (line 6)
-* 'prof': Debugging Options. (line 643)
-* 'progmem' variable attribute, AVR: Variable Attributes.
- (line 315)
+* prof: Debugging Options. (line 638)
+* progmem variable attribute, AVR: Variable Attributes.
+ (line 319)
* promotion of formal parameters: Function Prototypes.
(line 6)
-* 'pure' function attribute: Function Attributes.
- (line 1253)
-* push address instruction: Simple Constraints. (line 152)
+* pure function attribute: Function Attributes.
+ (line 1257)
+* push address instruction: Simple Constraints. (line 154)
* putchar: Other Builtins. (line 6)
* puts: Other Builtins. (line 6)
-* 'q' floating point suffix: Floating Types. (line 6)
-* 'Q' floating point suffix: Floating Types. (line 6)
-* 'qsort', and global register variables: Global Reg Vars. (line 41)
+* Q floating point suffix: Floating Types. (line 6)
+* q floating point suffix: Floating Types. (line 6)
+* qsort, and global register variables: Global Reg Vars. (line 41)
* question mark: Multi-Alternative. (line 27)
* quote GCC_COLORS capability: Language Independent Options.
(line 85)
-* 'r' fixed-suffix: Fixed-Point. (line 6)
-* 'R' fixed-suffix: Fixed-Point. (line 6)
-* 'r' in constraint: Simple Constraints. (line 64)
-* 'RAMPD': AVR Options. (line 354)
-* 'RAMPX': AVR Options. (line 354)
-* 'RAMPY': AVR Options. (line 354)
-* 'RAMPZ': AVR Options. (line 354)
+* R fixed-suffix: Fixed-Point. (line 6)
+* r fixed-suffix: Fixed-Point. (line 6)
+* r in constraint: Simple Constraints. (line 66)
+* RAMPD: AVR Options. (line 358)
+* RAMPX: AVR Options. (line 358)
+* RAMPY: AVR Options. (line 358)
+* RAMPZ: AVR Options. (line 358)
* ranges in case statements: Case Ranges. (line 6)
* read-only strings: Incompatibilities. (line 9)
-* 'reentrant' function attribute, MSP430: Function Attributes.
- (line 690)
-* register variable after 'longjmp': Global Reg Vars. (line 65)
+* reentrant function attribute, MSP430: Function Attributes.
+ (line 697)
+* register variable after longjmp: Global Reg Vars. (line 65)
* registers for local variables: Local Reg Vars. (line 6)
-* registers in constraints: Simple Constraints. (line 64)
+* registers in constraints: Simple Constraints. (line 66)
* registers, global allocation: Explicit Reg Vars. (line 6)
* registers, global variables in: Global Reg Vars. (line 6)
-* 'regparm' function attribute, x86: Function Attributes.
- (line 1328)
-* relocation truncated to fit (ColdFire): M680x0 Options. (line 325)
-* relocation truncated to fit (MIPS): MIPS Options. (line 235)
+* regparm function attribute, x86: Function Attributes.
+ (line 1332)
+* relocation truncated to fit (ColdFire): M680x0 Options. (line 329)
+* relocation truncated to fit (MIPS): MIPS Options. (line 239)
* remainder: Other Builtins. (line 6)
* remainderf: Other Builtins. (line 6)
* remainderl: Other Builtins. (line 6)
* remquo: Other Builtins. (line 6)
* remquof: Other Builtins. (line 6)
* remquol: Other Builtins. (line 6)
-* 'renesas' function attribute, SH: Function Attributes.
- (line 1371)
+* renesas function attribute, SH: Function Attributes.
+ (line 1376)
* reordering, warning: C++ Dialect Options.
- (line 584)
+ (line 588)
* reporting bugs: Bugs. (line 6)
-* 'resbank' function attribute, SH: Function Attributes.
- (line 1375)
-* 'reset' function attribute, NDS32: Function Attributes.
- (line 1345)
+* resbank function attribute, SH: Function Attributes.
+ (line 1380)
+* reset function attribute, NDS32: Function Attributes.
+ (line 1349)
* reset handler functions: Function Attributes.
- (line 1345)
+ (line 1349)
* rest argument (in macro): Variadic Macros. (line 6)
* restricted pointers: Restricted Pointers.
(line 6)
@@ -52906,10 +53321,10 @@ Keyword Index
(line 6)
* restricted this pointer: Restricted Pointers.
(line 6)
-* 'returns_nonnull' function attribute: Function Attributes.
- (line 1138)
-* 'returns_twice' function attribute: Function Attributes.
- (line 1389)
+* returns_nonnull function attribute: Function Attributes.
+ (line 1142)
+* returns_twice function attribute: Function Attributes.
+ (line 1394)
* rindex: Other Builtins. (line 6)
* rint: Other Builtins. (line 6)
* rintf: Other Builtins. (line 6)
@@ -52923,62 +53338,61 @@ Keyword Index
* RTTI: Vague Linkage. (line 42)
* run-time options: Code Gen Options. (line 6)
* RX Options: RX Options. (line 6)
-* 's' in constraint: Simple Constraints. (line 100)
+* s in constraint: Simple Constraints. (line 102)
* S/390 and zSeries Options: S/390 and zSeries Options.
(line 6)
* save all registers on the Blackfin, H8/300, H8/300H, and H8S: Function Attributes.
- (line 1398)
-* 'saveall' function attribute, Blackfin: Function Attributes.
- (line 1398)
-* 'saveall' function attribute, H8/300: Function Attributes.
- (line 1398)
-* 'save_all' function attribute, NDS32: Function Attributes.
- (line 782)
-* 'save_volatiles' function attribute, MicroBlaze: Function Attributes.
+ (line 1403)
+* save_all function attribute, NDS32: Function Attributes.
+ (line 791)
+* save_volatiles function attribute, MicroBlaze: Function Attributes.
+ (line 1408)
+* saveall function attribute, Blackfin: Function Attributes.
+ (line 1403)
+* saveall function attribute, H8/300: Function Attributes.
(line 1403)
* scalb: Other Builtins. (line 6)
* scalbf: Other Builtins. (line 6)
* scalbl: Other Builtins. (line 6)
* scalbln: Other Builtins. (line 6)
* scalblnf: Other Builtins. (line 6)
-* scalblnf <1>: Other Builtins. (line 6)
* scalbn: Other Builtins. (line 6)
* scalbnf: Other Builtins. (line 6)
-* 'scanf', and constant strings: Incompatibilities. (line 17)
+* scanf, and constant strings: Incompatibilities. (line 17)
* scanfnl: Other Builtins. (line 6)
* scope of a variable length array: Variable Length. (line 22)
* scope of declaration: Disappointments. (line 21)
* scope of external declarations: Incompatibilities. (line 80)
* Score Options: Score Options. (line 6)
* search path: Directory Options. (line 6)
-* 'section' function attribute: Function Attributes.
- (line 1420)
-* 'section' variable attribute: Variable Attributes.
- (line 166)
-* 'selectany' variable attribute: Variable Attributes.
- (line 280)
-* 'sentinel' function attribute: Function Attributes.
- (line 1436)
+* section function attribute: Function Attributes.
+ (line 1425)
+* section variable attribute: Variable Attributes.
+ (line 167)
+* selectany variable attribute: Variable Attributes.
+ (line 283)
+* sentinel function attribute: Function Attributes.
+ (line 1441)
* setjmp: Global Reg Vars. (line 65)
-* 'setjmp' incompatibilities: Incompatibilities. (line 39)
+* setjmp incompatibilities: Incompatibilities. (line 39)
* shared strings: Incompatibilities. (line 9)
-* 'shared' variable attribute: Variable Attributes.
- (line 211)
-* 'shortcall' function attribute, Blackfin: Function Attributes.
- (line 899)
-* 'shortcall' function attribute, PowerPC: Function Attributes.
- (line 899)
-* 'short_call' function attribute, ARC: Function Attributes.
- (line 875)
-* 'short_call' function attribute, ARM: Function Attributes.
- (line 875)
-* 'short_call' function attribute, Epiphany: Function Attributes.
- (line 875)
-* side effect in '?:': Conditionals. (line 20)
+* shared variable attribute: Variable Attributes.
+ (line 212)
+* short_call function attribute, ARC: Function Attributes.
+ (line 886)
+* short_call function attribute, ARM: Function Attributes.
+ (line 886)
+* short_call function attribute, Epiphany: Function Attributes.
+ (line 886)
+* shortcall function attribute, Blackfin: Function Attributes.
+ (line 910)
+* shortcall function attribute, PowerPC: Function Attributes.
+ (line 910)
+* side effect in ?:: Conditionals. (line 20)
* side effects, macro argument: Statement Exprs. (line 35)
* side effects, order of evaluation: Non-bugs. (line 196)
-* 'signal' function attribute, AVR: Function Attributes.
- (line 1467)
+* signal function attribute, AVR: Function Attributes.
+ (line 1472)
* signbit: Other Builtins. (line 6)
* signbitd128: Other Builtins. (line 6)
* signbitd32: Other Builtins. (line 6)
@@ -52986,11 +53400,11 @@ Keyword Index
* signbitf: Other Builtins. (line 6)
* signbitl: Other Builtins. (line 6)
* signed and unsigned values, comparison warning: Warning Options.
- (line 1285)
+ (line 1299)
* significand: Other Builtins. (line 6)
* significandf: Other Builtins. (line 6)
* significandl: Other Builtins. (line 6)
-* SIMD: C Dialect Options. (line 285)
+* SIMD: C Dialect Options. (line 284)
* simple constraints: Simple Constraints. (line 6)
* sin: Other Builtins. (line 6)
* sincos: Other Builtins. (line 6)
@@ -53002,12 +53416,14 @@ Keyword Index
* sinhl: Other Builtins. (line 6)
* sinl: Other Builtins. (line 6)
* sizeof: Typeof. (line 6)
-* smaller data references: M32R/D Options. (line 57)
* smaller data references <1>: Nios II Options. (line 9)
+* smaller data references: M32R/D Options. (line 57)
* smaller data references (PowerPC): RS/6000 and PowerPC Options.
- (line 767)
+ (line 770)
* snprintf: Other Builtins. (line 6)
* Solaris 2 options: Solaris 2 Options. (line 6)
+* sp_switch function attribute, SH: Function Attributes.
+ (line 1490)
* SPARC options: SPARC Options. (line 6)
* Spec Files: Spec Files. (line 6)
* specified registers: Explicit Reg Vars. (line 6)
@@ -53020,25 +53436,23 @@ Keyword Index
(line 6)
* sprintf: Other Builtins. (line 6)
* SPU options: SPU Options. (line 6)
-* 'spu_vector' type attribute, SPU: Type Attributes. (line 378)
-* 'spu_vector' variable attribute, SPU: Variable Attributes.
- (line 515)
-* 'sp_switch' function attribute, SH: Function Attributes.
- (line 1485)
+* spu_vector type attribute, SPU: Type Attributes. (line 379)
+* spu_vector variable attribute, SPU: Variable Attributes.
+ (line 524)
* sqrt: Other Builtins. (line 6)
* sqrtf: Other Builtins. (line 6)
* sqrtl: Other Builtins. (line 6)
* sscanf: Other Builtins. (line 6)
-* 'sscanf', and constant strings: Incompatibilities. (line 17)
-* 'sseregparm' function attribute, x86: Function Attributes.
- (line 1356)
-* 'stack_protect' function attribute: Function Attributes.
- (line 1080)
+* sscanf, and constant strings: Incompatibilities. (line 17)
+* sseregparm function attribute, x86: Function Attributes.
+ (line 1361)
+* stack_protect function attribute: Function Attributes.
+ (line 1084)
* statements inside expressions: Statement Exprs. (line 6)
* static data in C++, declaring and defining: Static Definitions.
(line 6)
-* 'stdcall' function attribute, x86-32: Function Attributes.
- (line 1495)
+* stdcall function attribute, x86-32: Function Attributes.
+ (line 1500)
* stpcpy: Other Builtins. (line 6)
* stpncpy: Other Builtins. (line 6)
* strcasecmp: Other Builtins. (line 6)
@@ -53061,9 +53475,9 @@ Keyword Index
* strrchr: Other Builtins. (line 6)
* strspn: Other Builtins. (line 6)
* strstr: Other Builtins. (line 6)
-* 'struct': Unnamed Fields. (line 6)
+* struct: Unnamed Fields. (line 6)
* struct __htm_tdb: S/390 System z Built-in Functions.
- (line 49)
+ (line 54)
* structures: Incompatibilities. (line 146)
* structures, constructor expression: Compound Literals. (line 6)
* submodel options: Submodel Options. (line 6)
@@ -53071,136 +53485,136 @@ Keyword Index
* subscripting and function values: Subscripting. (line 6)
* suffixes for C++ source: Invoking G++. (line 6)
* SUNPRO_DEPENDENCIES: Environment Variables.
- (line 170)
+ (line 172)
* suppressing warnings: Warning Options. (line 6)
* surprises in C++: C++ Misunderstandings.
(line 6)
* syntax checking: Warning Options. (line 13)
-* 'syscall_linkage' function attribute, IA-64: Function Attributes.
- (line 1500)
-* system headers, warnings from: Warning Options. (line 941)
-* 'sysv_abi' function attribute, x86: Function Attributes.
- (line 991)
+* syscall_linkage function attribute, IA-64: Function Attributes.
+ (line 1505)
+* system headers, warnings from: Warning Options. (line 949)
+* sysv_abi function attribute, x86: Function Attributes.
+ (line 999)
* tan: Other Builtins. (line 6)
* tanf: Other Builtins. (line 6)
* tanh: Other Builtins. (line 6)
* tanhf: Other Builtins. (line 6)
* tanhl: Other Builtins. (line 6)
* tanl: Other Builtins. (line 6)
-* 'target' function attribute: Function Attributes.
- (line 1507)
+* target function attribute: Function Attributes.
+ (line 1512)
* target machine, specifying: Target Options. (line 6)
* target options: Target Options. (line 6)
-* 'target("abm")' function attribute, x86: Function Attributes.
- (line 1540)
-* 'target("aes")' function attribute, x86: Function Attributes.
+* target("abm") function attribute, x86: Function Attributes.
(line 1545)
-* 'target("align-stringops")' function attribute, x86: Function Attributes.
- (line 1639)
-* 'target("altivec")' function attribute, PowerPC: Function Attributes.
- (line 1665)
-* 'target("arch=ARCH")' function attribute, x86: Function Attributes.
- (line 1648)
-* 'target("avoid-indexed-addresses")' function attribute, PowerPC: Function Attributes.
- (line 1786)
-* 'target("cld")' function attribute, x86: Function Attributes.
- (line 1610)
-* 'target("cmpb")' function attribute, PowerPC: Function Attributes.
- (line 1671)
-* 'target("cpu=CPU")' function attribute, PowerPC: Function Attributes.
- (line 1801)
-* 'target("custom-fpu-cfg=NAME")' function attribute, Nios II: Function Attributes.
- (line 1827)
-* 'target("custom-INSN=N")' function attribute, Nios II: Function Attributes.
- (line 1818)
-* 'target("default")' function attribute, x86: Function Attributes.
- (line 1548)
-* 'target("dlmzb")' function attribute, PowerPC: Function Attributes.
- (line 1677)
-* 'target("fancy-math-387")' function attribute, x86: Function Attributes.
- (line 1614)
-* 'target("fma4")' function attribute, x86: Function Attributes.
- (line 1594)
-* 'target("fpmath=FPMATH")' function attribute, x86: Function Attributes.
- (line 1656)
-* 'target("fprnd")' function attribute, PowerPC: Function Attributes.
- (line 1684)
-* 'target("friz")' function attribute, PowerPC: Function Attributes.
- (line 1777)
-* 'target("fused-madd")' function attribute, x86: Function Attributes.
+* target("aes") function attribute, x86: Function Attributes.
+ (line 1550)
+* target("align-stringops") function attribute, x86: Function Attributes.
+ (line 1644)
+* target("altivec") function attribute, PowerPC: Function Attributes.
+ (line 1670)
+* target("arch=ARCH") function attribute, x86: Function Attributes.
+ (line 1653)
+* target("avoid-indexed-addresses") function attribute, PowerPC: Function Attributes.
+ (line 1791)
+* target("cld") function attribute, x86: Function Attributes.
+ (line 1615)
+* target("cmpb") function attribute, PowerPC: Function Attributes.
+ (line 1676)
+* target("cpu=CPU") function attribute, PowerPC: Function Attributes.
+ (line 1806)
+* target("custom-fpu-cfg=NAME") function attribute, Nios II: Function Attributes.
+ (line 1832)
+* target("custom-INSN=N") function attribute, Nios II: Function Attributes.
+ (line 1823)
+* target("default") function attribute, x86: Function Attributes.
+ (line 1553)
+* target("dlmzb") function attribute, PowerPC: Function Attributes.
+ (line 1682)
+* target("fancy-math-387") function attribute, x86: Function Attributes.
(line 1619)
-* 'target("hard-dfp")' function attribute, PowerPC: Function Attributes.
- (line 1690)
-* 'target("ieee-fp")' function attribute, x86: Function Attributes.
+* target("fma4") function attribute, x86: Function Attributes.
+ (line 1599)
+* target("fpmath=FPMATH") function attribute, x86: Function Attributes.
+ (line 1661)
+* target("fprnd") function attribute, PowerPC: Function Attributes.
+ (line 1689)
+* target("friz") function attribute, PowerPC: Function Attributes.
+ (line 1782)
+* target("fused-madd") function attribute, x86: Function Attributes.
(line 1624)
-* 'target("inline-all-stringops")' function attribute, x86: Function Attributes.
+* target("hard-dfp") function attribute, PowerPC: Function Attributes.
+ (line 1695)
+* target("ieee-fp") function attribute, x86: Function Attributes.
(line 1629)
-* 'target("inline-stringops-dynamically")' function attribute, x86: Function Attributes.
- (line 1633)
-* 'target("isel")' function attribute, PowerPC: Function Attributes.
- (line 1696)
-* 'target("longcall")' function attribute, PowerPC: Function Attributes.
+* target("inline-all-stringops") function attribute, x86: Function Attributes.
+ (line 1634)
+* target("inline-stringops-dynamically") function attribute, x86: Function Attributes.
+ (line 1638)
+* target("isel") function attribute, PowerPC: Function Attributes.
+ (line 1701)
+* target("longcall") function attribute, PowerPC: Function Attributes.
+ (line 1801)
+* target("lwp") function attribute, x86: Function Attributes.
+ (line 1607)
+* target("mfcrf") function attribute, PowerPC: Function Attributes.
+ (line 1705)
+* target("mfpgpr") function attribute, PowerPC: Function Attributes.
+ (line 1712)
+* target("mmx") function attribute, x86: Function Attributes.
+ (line 1558)
+* target("mulhw") function attribute, PowerPC: Function Attributes.
+ (line 1719)
+* target("multiple") function attribute, PowerPC: Function Attributes.
+ (line 1726)
+* target("no-custom-INSN") function attribute, Nios II: Function Attributes.
+ (line 1823)
+* target("paired") function attribute, PowerPC: Function Attributes.
(line 1796)
-* 'target("lwp")' function attribute, x86: Function Attributes.
- (line 1602)
-* 'target("mfcrf")' function attribute, PowerPC: Function Attributes.
- (line 1700)
-* 'target("mfpgpr")' function attribute, PowerPC: Function Attributes.
- (line 1707)
-* 'target("mmx")' function attribute, x86: Function Attributes.
- (line 1553)
-* 'target("mulhw")' function attribute, PowerPC: Function Attributes.
- (line 1714)
-* 'target("multiple")' function attribute, PowerPC: Function Attributes.
- (line 1721)
-* 'target("no-custom-INSN")' function attribute, Nios II: Function Attributes.
- (line 1818)
-* 'target("paired")' function attribute, PowerPC: Function Attributes.
- (line 1791)
-* 'target("pclmul")' function attribute, x86: Function Attributes.
- (line 1557)
-* 'target("popcnt")' function attribute, x86: Function Attributes.
- (line 1561)
-* 'target("popcntb")' function attribute, PowerPC: Function Attributes.
- (line 1732)
-* 'target("popcntd")' function attribute, PowerPC: Function Attributes.
- (line 1739)
-* 'target("powerpc-gfxopt")' function attribute, PowerPC: Function Attributes.
- (line 1745)
-* 'target("powerpc-gpopt")' function attribute, PowerPC: Function Attributes.
- (line 1751)
-* 'target("recip")' function attribute, x86: Function Attributes.
- (line 1643)
-* 'target("recip-precision")' function attribute, PowerPC: Function Attributes.
- (line 1757)
-* 'target("sse")' function attribute, x86: Function Attributes.
- (line 1565)
-* 'target("sse2")' function attribute, x86: Function Attributes.
- (line 1569)
-* 'target("sse3")' function attribute, x86: Function Attributes.
- (line 1573)
-* 'target("sse4")' function attribute, x86: Function Attributes.
- (line 1577)
-* 'target("sse4.1")' function attribute, x86: Function Attributes.
+* target("pclmul") function attribute, x86: Function Attributes.
+ (line 1562)
+* target("popcnt") function attribute, x86: Function Attributes.
+ (line 1566)
+* target("popcntb") function attribute, PowerPC: Function Attributes.
+ (line 1737)
+* target("popcntd") function attribute, PowerPC: Function Attributes.
+ (line 1744)
+* target("powerpc-gfxopt") function attribute, PowerPC: Function Attributes.
+ (line 1750)
+* target("powerpc-gpopt") function attribute, PowerPC: Function Attributes.
+ (line 1756)
+* target("recip") function attribute, x86: Function Attributes.
+ (line 1648)
+* target("recip-precision") function attribute, PowerPC: Function Attributes.
+ (line 1762)
+* target("sse") function attribute, x86: Function Attributes.
+ (line 1570)
+* target("sse2") function attribute, x86: Function Attributes.
+ (line 1574)
+* target("sse3") function attribute, x86: Function Attributes.
+ (line 1578)
+* target("sse4") function attribute, x86: Function Attributes.
(line 1582)
-* 'target("sse4.2")' function attribute, x86: Function Attributes.
- (line 1586)
-* 'target("sse4a")' function attribute, x86: Function Attributes.
- (line 1590)
-* 'target("ssse3")' function attribute, x86: Function Attributes.
- (line 1606)
-* 'target("string")' function attribute, PowerPC: Function Attributes.
- (line 1763)
-* 'target("tune=TUNE")' function attribute, PowerPC: Function Attributes.
- (line 1808)
-* 'target("tune=TUNE")' function attribute, x86: Function Attributes.
- (line 1652)
-* 'target("update")' function attribute, PowerPC: Function Attributes.
- (line 1726)
-* 'target("vsx")' function attribute, PowerPC: Function Attributes.
- (line 1769)
-* 'target("xop")' function attribute, x86: Function Attributes.
- (line 1598)
+* target("sse4.1") function attribute, x86: Function Attributes.
+ (line 1587)
+* target("sse4.2") function attribute, x86: Function Attributes.
+ (line 1591)
+* target("sse4a") function attribute, x86: Function Attributes.
+ (line 1595)
+* target("ssse3") function attribute, x86: Function Attributes.
+ (line 1611)
+* target("string") function attribute, PowerPC: Function Attributes.
+ (line 1768)
+* target("tune=TUNE") function attribute, PowerPC: Function Attributes.
+ (line 1813)
+* target("tune=TUNE") function attribute, x86: Function Attributes.
+ (line 1657)
+* target("update") function attribute, PowerPC: Function Attributes.
+ (line 1731)
+* target("vsx") function attribute, PowerPC: Function Attributes.
+ (line 1774)
+* target("xop") function attribute, x86: Function Attributes.
+ (line 1603)
* TC1: Standards. (line 13)
* TC2: Standards. (line 13)
* TC3: Standards. (line 13)
@@ -53214,22 +53628,22 @@ Keyword Index
* tgamma: Other Builtins. (line 6)
* tgammaf: Other Builtins. (line 6)
* tgammal: Other Builtins. (line 6)
-* 'thiscall' function attribute, x86-32: Function Attributes.
- (line 410)
+* thiscall function attribute, x86-32: Function Attributes.
+ (line 414)
* Thread-Local Storage: Thread-Local. (line 6)
* thunks: Nested Functions. (line 6)
* TILE-Gx options: TILE-Gx Options. (line 6)
* TILEPro options: TILEPro Options. (line 6)
* tiny data section on the H8/300H and H8S: Variable Attributes.
- (line 413)
-* 'tiny' type attribute, MeP: Type Attributes. (line 348)
-* 'tiny' variable attribute, MeP: Variable Attributes.
- (line 468)
-* 'tiny_data' variable attribute, H8/300: Variable Attributes.
- (line 413)
+ (line 418)
+* tiny type attribute, MeP: Type Attributes. (line 349)
+* tiny variable attribute, MeP: Variable Attributes.
+ (line 475)
+* tiny_data variable attribute, H8/300: Variable Attributes.
+ (line 418)
* TLS: Thread-Local. (line 6)
-* 'tls_model' variable attribute: Variable Attributes.
- (line 234)
+* tls_model variable attribute: Variable Attributes.
+ (line 236)
* TMPDIR: Environment Variables.
(line 45)
* toascii: Other Builtins. (line 6)
@@ -53237,69 +53651,69 @@ Keyword Index
* toupper: Other Builtins. (line 6)
* towlower: Other Builtins. (line 6)
* towupper: Other Builtins. (line 6)
-* traditional C language: C Dialect Options. (line 345)
-* 'transparent_union' type attribute: Type Attributes. (line 143)
-* 'trapa_handler' function attribute, SH: Function Attributes.
+* traditional C language: C Dialect Options. (line 344)
+* transparent_union type attribute: Type Attributes. (line 143)
+* trap_exit function attribute, SH: Function Attributes.
(line 1844)
-* 'trap_exit' function attribute, SH: Function Attributes.
- (line 1839)
+* trapa_handler function attribute, SH: Function Attributes.
+ (line 1849)
* trunc: Other Builtins. (line 6)
* truncf: Other Builtins. (line 6)
* truncl: Other Builtins. (line 6)
* two-stage name lookup: Name lookup. (line 6)
* type alignment: Alignment. (line 6)
* type attributes: Type Attributes. (line 6)
+* type_info: Vague Linkage. (line 42)
* typedef names as function parameters: Incompatibilities. (line 97)
* typeof: Typeof. (line 6)
-* 'type_info': Vague Linkage. (line 42)
-* 'uhk' fixed-suffix: Fixed-Point. (line 6)
-* 'UHK' fixed-suffix: Fixed-Point. (line 6)
-* 'uhr' fixed-suffix: Fixed-Point. (line 6)
-* 'UHR' fixed-suffix: Fixed-Point. (line 6)
-* 'uk' fixed-suffix: Fixed-Point. (line 6)
-* 'UK' fixed-suffix: Fixed-Point. (line 6)
-* 'ulk' fixed-suffix: Fixed-Point. (line 6)
-* 'ULK' fixed-suffix: Fixed-Point. (line 6)
-* 'ULL' integer suffix: Long Long. (line 6)
-* 'ullk' fixed-suffix: Fixed-Point. (line 6)
-* 'ULLK' fixed-suffix: Fixed-Point. (line 6)
-* 'ullr' fixed-suffix: Fixed-Point. (line 6)
-* 'ULLR' fixed-suffix: Fixed-Point. (line 6)
-* 'ulr' fixed-suffix: Fixed-Point. (line 6)
-* 'ULR' fixed-suffix: Fixed-Point. (line 6)
+* UHK fixed-suffix: Fixed-Point. (line 6)
+* uhk fixed-suffix: Fixed-Point. (line 6)
+* UHR fixed-suffix: Fixed-Point. (line 6)
+* uhr fixed-suffix: Fixed-Point. (line 6)
+* UK fixed-suffix: Fixed-Point. (line 6)
+* uk fixed-suffix: Fixed-Point. (line 6)
+* ULK fixed-suffix: Fixed-Point. (line 6)
+* ulk fixed-suffix: Fixed-Point. (line 6)
+* ULL integer suffix: Long Long. (line 6)
+* ULLK fixed-suffix: Fixed-Point. (line 6)
+* ullk fixed-suffix: Fixed-Point. (line 6)
+* ULLR fixed-suffix: Fixed-Point. (line 6)
+* ullr fixed-suffix: Fixed-Point. (line 6)
+* ULR fixed-suffix: Fixed-Point. (line 6)
+* ulr fixed-suffix: Fixed-Point. (line 6)
* undefined behavior: Bug Criteria. (line 17)
* undefined function value: Bug Criteria. (line 17)
* underscores in variables in macros: Typeof. (line 46)
-* 'union': Unnamed Fields. (line 6)
+* union: Unnamed Fields. (line 6)
* union, casting to a: Cast to Union. (line 6)
* unions: Incompatibilities. (line 146)
-* unknown pragmas, warning: Warning Options. (line 722)
-* unresolved references and '-nodefaultlibs': Link Options. (line 91)
-* unresolved references and '-nostdlib': Link Options. (line 91)
-* 'unused' function attribute: Function Attributes.
- (line 1848)
-* 'unused' label attribute: Label Attributes. (line 29)
-* 'unused' type attribute: Type Attributes. (line 196)
-* 'unused' variable attribute: Variable Attributes.
- (line 243)
-* 'ur' fixed-suffix: Fixed-Point. (line 6)
-* 'UR' fixed-suffix: Fixed-Point. (line 6)
-* 'used' function attribute: Function Attributes.
+* unknown pragmas, warning: Warning Options. (line 729)
+* unresolved references and -nodefaultlibs: Link Options. (line 91)
+* unresolved references and -nostdlib: Link Options. (line 91)
+* unused function attribute: Function Attributes.
(line 1853)
-* 'used' variable attribute: Variable Attributes.
- (line 248)
+* unused label attribute: Label Attributes. (line 29)
+* unused type attribute: Type Attributes. (line 195)
+* unused variable attribute: Variable Attributes.
+ (line 245)
+* UR fixed-suffix: Fixed-Point. (line 6)
+* ur fixed-suffix: Fixed-Point. (line 6)
+* use_debug_exception_return function attribute, MIPS: Function Attributes.
+ (line 756)
+* use_shadow_register_set function attribute, MIPS: Function Attributes.
+ (line 747)
+* used function attribute: Function Attributes.
+ (line 1858)
+* used variable attribute: Variable Attributes.
+ (line 250)
* User stack pointer in interrupts on the Blackfin: Function Attributes.
- (line 829)
-* 'use_debug_exception_return' function attribute, MIPS: Function Attributes.
- (line 750)
-* 'use_shadow_register_set' function attribute, MIPS: Function Attributes.
- (line 741)
-* 'V' in constraint: Simple Constraints. (line 43)
+ (line 840)
+* V in constraint: Simple Constraints. (line 43)
* V850 Options: V850 Options. (line 6)
* vague linkage: Vague Linkage. (line 6)
-* value after 'longjmp': Global Reg Vars. (line 65)
+* value after longjmp: Global Reg Vars. (line 65)
* variable addressability on the M32R/D: Variable Attributes.
- (line 440)
+ (line 446)
* variable alignment: Alignment. (line 6)
* variable attributes: Variable Attributes.
(line 6)
@@ -53311,32 +53725,32 @@ Keyword Index
* variables, local, in macros: Typeof. (line 46)
* variadic macros: Variadic Macros. (line 6)
* VAX options: VAX Options. (line 6)
-* 'vector' function attribute, RX: Function Attributes.
- (line 1863)
-* 'vector_size' variable attribute: Variable Attributes.
- (line 257)
-* 'version_id' function attribute, IA-64: Function Attributes.
- (line 1870)
+* vector function attribute, RX: Function Attributes.
+ (line 1868)
+* vector_size variable attribute: Variable Attributes.
+ (line 259)
+* version_id function attribute, IA-64: Function Attributes.
+ (line 1875)
* vfprintf: Other Builtins. (line 6)
* vfscanf: Other Builtins. (line 6)
-* 'visibility' function attribute: Function Attributes.
- (line 1880)
-* 'visibility' type attribute: Type Attributes. (line 270)
+* visibility function attribute: Function Attributes.
+ (line 1885)
+* visibility type attribute: Type Attributes. (line 269)
* Visium options: Visium Options. (line 6)
* VLAs: Variable Length. (line 6)
-* 'vliw' function attribute, MeP: Function Attributes.
- (line 1976)
+* vliw function attribute, MeP: Function Attributes.
+ (line 1982)
* void pointers, arithmetic: Pointer Arith. (line 6)
* void, size of pointer to: Pointer Arith. (line 6)
-* volatile access: Volatiles. (line 6)
* volatile access <1>: C++ Volatiles. (line 6)
-* 'volatile' applied to function: Function Attributes.
+* volatile access: Volatiles. (line 6)
+* volatile applied to function: Function Attributes.
(line 6)
-* volatile 'asm': Extended Asm. (line 109)
-* volatile read: Volatiles. (line 6)
+* volatile asm: Extended Asm. (line 109)
* volatile read <1>: C++ Volatiles. (line 6)
-* volatile write: Volatiles. (line 6)
+* volatile read: Volatiles. (line 6)
* volatile write <1>: C++ Volatiles. (line 6)
+* volatile write: Volatiles. (line 6)
* vprintf: Other Builtins. (line 6)
* vscanf: Other Builtins. (line 6)
* vsnprintf: Other Builtins. (line 6)
@@ -53344,40 +53758,40 @@ Keyword Index
* vsscanf: Other Builtins. (line 6)
* vtable: Vague Linkage. (line 27)
* VxWorks Options: VxWorks Options. (line 6)
-* 'w' floating point suffix: Floating Types. (line 6)
-* 'W' floating point suffix: Floating Types. (line 6)
-* 'wakeup' function attribute, MSP430: Function Attributes.
- (line 696)
-* 'warm' function attribute, NDS32: Function Attributes.
- (line 1352)
+* W floating point suffix: Floating Types. (line 6)
+* w floating point suffix: Floating Types. (line 6)
+* wakeup function attribute, MSP430: Function Attributes.
+ (line 703)
+* warm function attribute, NDS32: Function Attributes.
+ (line 1357)
+* warn_unused type attribute: C++ Attributes. (line 77)
+* warn_unused_result function attribute: Function Attributes.
+ (line 1988)
* warning for comparison of signed and unsigned values: Warning Options.
- (line 1285)
+ (line 1299)
* warning for overloaded virtual function: C++ Dialect Options.
- (line 666)
+ (line 672)
* warning for reordering of member initializers: C++ Dialect Options.
- (line 584)
-* warning for unknown pragmas: Warning Options. (line 722)
-* 'warning' function attribute: Function Attributes.
- (line 204)
+ (line 588)
+* warning for unknown pragmas: Warning Options. (line 729)
+* warning function attribute: Function Attributes.
+ (line 206)
* warning GCC_COLORS capability: Language Independent Options.
(line 72)
* warning messages: Warning Options. (line 6)
-* warnings from system headers: Warning Options. (line 941)
+* warnings from system headers: Warning Options. (line 949)
* warnings vs errors: Warnings and Errors.
(line 6)
-* 'warn_unused' type attribute: C++ Attributes. (line 79)
-* 'warn_unused_result' function attribute: Function Attributes.
- (line 1982)
-* 'weak' function attribute: Function Attributes.
- (line 1999)
-* 'weak' variable attribute: Variable Attributes.
- (line 301)
-* 'weakref' function attribute: Function Attributes.
- (line 2008)
+* weak function attribute: Function Attributes.
+ (line 2005)
+* weak variable attribute: Variable Attributes.
+ (line 304)
+* weakref function attribute: Function Attributes.
+ (line 2014)
* whitespace: Incompatibilities. (line 112)
* Windows Options for x86: x86 Windows Options.
(line 6)
-* 'X' in constraint: Simple Constraints. (line 122)
+* X in constraint: Simple Constraints. (line 124)
* X3.159-1989: Standards. (line 13)
* x86 Options: x86 Options. (line 6)
* x86 Windows Options: x86 Windows Options.
@@ -53400,337 +53814,337 @@ Keyword Index

Tag Table:
-Node: Top1969
-Node: G++ and GCC3794
-Node: Standards5851
-Node: Invoking GCC17943
-Node: Option Summary21688
-Node: Overall Options65954
-Node: Invoking G++80141
-Node: C Dialect Options81664
-Node: C++ Dialect Options98918
-Node: Objective-C and Objective-C++ Dialect Options130459
-Node: Language Independent Options141694
-Node: Warning Options146518
-Node: Debugging Options224900
-Node: Optimize Options296216
-Ref: Type-punning359459
-Node: Preprocessor Options448378
-Ref: Wtrigraphs453161
-Ref: dashMF457911
-Ref: fdollars-in-identifiers468792
-Node: Assembler Options478993
-Node: Link Options479684
-Ref: Link Options-Footnote-1493197
-Node: Directory Options493533
-Node: Spec Files500087
-Node: Target Options521903
-Node: Submodel Options522302
-Node: AArch64 Options524067
-Node: Adapteva Epiphany Options529546
-Node: ARC Options535494
-Node: ARM Options547938
-Node: AVR Options565624
-Node: Blackfin Options586932
-Node: C6X Options594950
-Node: CRIS Options596493
-Node: CR16 Options600232
-Node: Darwin Options601143
-Node: DEC Alpha Options608583
-Node: FR30 Options620199
-Node: FRV Options620763
-Node: GNU/Linux Options627527
-Node: H8/300 Options628787
-Node: HPPA Options630239
-Node: IA-64 Options639429
-Node: LM32 Options647476
-Node: M32C Options647999
-Node: M32R/D Options649272
-Node: M680x0 Options652817
-Node: MCore Options666852
-Node: MeP Options668354
-Node: MicroBlaze Options672314
-Node: MIPS Options675116
-Node: MMIX Options708573
-Node: MN10300 Options711050
-Node: Moxie Options713591
-Node: MSP430 Options714078
-Node: NDS32 Options717577
-Node: Nios II Options719471
-Node: Nvidia PTX Options729670
-Node: PDP-11 Options730061
-Node: picoChip Options731758
-Node: PowerPC Options733896
-Node: RL78 Options734117
-Node: RS/6000 and PowerPC Options734964
-Node: RX Options775285
-Node: S/390 and zSeries Options782633
-Node: Score Options791170
-Node: SH Options792019
-Node: Solaris 2 Options812890
-Node: SPARC Options814412
-Node: SPU Options827701
-Node: System V Options832640
-Node: TILE-Gx Options833466
-Node: TILEPro Options834484
-Node: V850 Options834988
-Node: VAX Options841675
-Node: Visium Options842213
-Node: VMS Options844521
-Node: VxWorks Options845337
-Node: x86 Options846489
-Node: x86 Windows Options890100
-Node: Xstormy16 Options892897
-Node: Xtensa Options893191
-Node: zSeries Options897516
-Node: Code Gen Options897712
-Node: Environment Variables928496
-Node: Precompiled Headers936499
-Node: C Implementation942502
-Node: Translation implementation944192
-Node: Environment implementation944783
-Node: Identifiers implementation945337
-Node: Characters implementation946423
-Node: Integers implementation950073
-Node: Floating point implementation951958
-Node: Arrays and pointers implementation955021
-Ref: Arrays and pointers implementation-Footnote-1956481
-Node: Hints implementation956607
-Node: Structures unions enumerations and bit-fields implementation958092
-Node: Qualifiers implementation960316
-Node: Declarators implementation962096
-Node: Statements implementation962437
-Node: Preprocessing directives implementation962763
-Node: Library functions implementation965084
-Node: Architecture implementation965733
-Node: Locale-specific behavior implementation967378
-Node: C++ Implementation967683
-Node: Conditionally-supported behavior968966
-Node: Exception handling969583
-Node: C Extensions969991
-Node: Statement Exprs975147
-Node: Local Labels979624
-Node: Labels as Values982597
-Ref: Labels as Values-Footnote-1985124
-Node: Nested Functions985309
-Node: Constructing Calls989267
-Node: Typeof993984
-Node: Conditionals997913
-Node: __int128998802
-Node: Long Long999327
-Node: Complex1000803
-Node: Floating Types1003391
-Node: Half-Precision1004511
-Node: Decimal Float1006696
-Node: Hex Floats1008552
-Node: Fixed-Point1009589
-Node: Named Address Spaces1012849
-Ref: AVR Named Address Spaces1013530
-Node: Zero Length1018738
-Node: Empty Structures1021778
-Node: Variable Length1022184
-Node: Variadic Macros1025040
-Node: Escaped Newlines1027418
-Node: Subscripting1028279
-Node: Pointer Arith1029004
-Node: Pointers to Arrays1029578
-Node: Initializers1030323
-Node: Compound Literals1030824
-Node: Designated Inits1034170
-Node: Case Ranges1037908
-Node: Cast to Union1038589
-Node: Mixed Declarations1039679
-Node: Function Attributes1040189
-Node: Label Attributes1134121
-Node: Attribute Syntax1135964
-Node: Function Prototypes1146175
-Node: C++ Comments1147955
-Node: Dollar Signs1148474
-Node: Character Escapes1148939
-Node: Variable Attributes1149233
-Ref: AVR Variable Attributes1162939
-Ref: MeP Variable Attributes1168303
-Ref: x86 Variable Attributes1170863
-Node: Type Attributes1175899
-Ref: MeP Type Attributes1191144
-Ref: PowerPC Type Attributes1191418
-Ref: SPU Type Attributes1192279
-Ref: x86 Type Attributes1192570
-Node: Alignment1193259
-Node: Inline1194629
-Node: Volatiles1199605
-Node: Using Assembly Language with C1202504
-Node: Basic Asm1203708
-Node: Extended Asm1207852
-Ref: Volatile1211656
-Ref: AssemblerTemplate1215741
-Ref: OutputOperands1219979
-Ref: InputOperands1226898
-Ref: Clobbers1231134
-Ref: GotoLabels1234440
-Ref: x86Operandmodifiers1236575
-Ref: x86floatingpointasmoperands1238746
-Node: Constraints1242075
-Node: Simple Constraints1243181
-Node: Multi-Alternative1250495
-Node: Modifiers1252502
-Node: Machine Constraints1256006
-Node: Asm Labels1312344
-Node: Explicit Reg Vars1314042
-Node: Global Reg Vars1315658
-Node: Local Reg Vars1320158
-Node: Size of an asm1323281
-Node: Alternate Keywords1324525
-Node: Incomplete Enums1326024
-Node: Function Names1326780
-Node: Return Address1328383
-Node: Vector Extensions1331890
-Node: Offsetof1339185
-Node: __sync Builtins1340018
-Node: __atomic Builtins1345493
-Node: Integer Overflow Builtins1357091
-Node: x86 specific memory model extensions for transactional memory1361216
-Node: Object Size Checking1362485
-Node: Pointer Bounds Checker builtins1367991
-Node: Cilk Plus Builtins1373997
-Node: Other Builtins1374902
-Node: Target Builtins1404529
-Node: AArch64 Built-in Functions1406021
-Node: Alpha Built-in Functions1406476
-Node: Altera Nios II Built-in Functions1409524
-Node: ARC Built-in Functions1413511
-Node: ARC SIMD Built-in Functions1418723
-Node: ARM iWMMXt Built-in Functions1427619
-Node: ARM C Language Extensions (ACLE)1434615
-Node: ARM Floating Point Status and Control Intrinsics1435892
-Node: AVR Built-in Functions1436368
-Node: Blackfin Built-in Functions1439475
-Node: FR-V Built-in Functions1440094
-Node: Argument Types1440962
-Node: Directly-mapped Integer Functions1442716
-Node: Directly-mapped Media Functions1443800
-Node: Raw read/write Functions1452006
-Node: Other Built-in Functions1452914
-Node: MIPS DSP Built-in Functions1454100
-Node: MIPS Paired-Single Support1466597
-Node: MIPS Loongson Built-in Functions1468096
-Node: Paired-Single Arithmetic1474611
-Node: Paired-Single Built-in Functions1475559
-Node: MIPS-3D Built-in Functions1478226
-Node: Other MIPS Built-in Functions1483604
-Node: MSP430 Built-in Functions1484609
-Node: NDS32 Built-in Functions1486010
-Node: picoChip Built-in Functions1487303
-Node: PowerPC Built-in Functions1488646
-Node: PowerPC AltiVec/VSX Built-in Functions1492354
-Node: PowerPC Hardware Transactional Memory Built-in Functions1632145
-Node: RX Built-in Functions1638686
-Node: S/390 System z Built-in Functions1642719
-Node: SH Built-in Functions1647948
-Node: SPARC VIS Built-in Functions1649676
-Node: SPU Built-in Functions1655279
-Node: TI C6X Built-in Functions1657096
-Node: TILE-Gx Built-in Functions1658121
-Node: TILEPro Built-in Functions1659240
-Node: x86 Built-in Functions1660340
-Node: x86 transactional memory intrinsics1719585
-Node: Target Format Checks1722805
-Node: Solaris Format Checks1723237
-Node: Darwin Format Checks1723663
-Node: Pragmas1724481
-Node: ARM Pragmas1725217
-Node: M32C Pragmas1725820
-Node: MeP Pragmas1726892
-Node: RS/6000 and PowerPC Pragmas1728960
-Node: Darwin Pragmas1729701
-Node: Solaris Pragmas1730768
-Node: Symbol-Renaming Pragmas1731932
-Node: Structure-Packing Pragmas1733549
-Node: Weak Pragmas1735193
-Node: Diagnostic Pragmas1735927
-Node: Visibility Pragmas1739036
-Node: Push/Pop Macro Pragmas1739721
-Node: Function Specific Option Pragmas1740694
-Node: Loop-Specific Pragmas1742542
-Node: Unnamed Fields1743635
-Node: Thread-Local1745832
-Node: C99 Thread-Local Edits1747937
-Node: C++98 Thread-Local Edits1749935
-Node: Binary constants1753380
-Node: C++ Extensions1754051
-Node: C++ Volatiles1755762
-Node: Restricted Pointers1758110
-Node: Vague Linkage1759701
-Node: C++ Interface1763324
-Ref: C++ Interface-Footnote-11767121
-Node: Template Instantiation1767259
-Node: Bound member functions1773844
-Node: C++ Attributes1775376
-Node: Function Multiversioning1779815
-Node: Namespace Association1781632
-Node: Type Traits1783012
-Node: Java Exceptions1789495
-Node: Deprecated Features1790885
-Node: Backwards Compatibility1793852
-Node: Objective-C1795199
-Node: GNU Objective-C runtime API1795806
-Node: Modern GNU Objective-C runtime API1796813
-Node: Traditional GNU Objective-C runtime API1799249
-Node: Executing code before main1799976
-Node: What you can and what you cannot do in +load1802720
-Node: Type encoding1805090
-Node: Legacy type encoding1810117
-Node: @encode1811207
-Node: Method signatures1811752
-Node: Garbage Collection1813744
-Node: Constant string objects1816434
-Node: compatibility_alias1818943
-Node: Exceptions1819668
-Node: Synchronization1822378
-Node: Fast enumeration1823562
-Node: Using fast enumeration1823874
-Node: c99-like fast enumeration syntax1825085
-Node: Fast enumeration details1825788
-Node: Fast enumeration protocol1828128
-Node: Messaging with the GNU Objective-C runtime1831280
-Node: Dynamically registering methods1832652
-Node: Forwarding hook1834343
-Node: Compatibility1837383
-Node: Gcov1843939
-Node: Gcov Intro1844474
-Node: Invoking Gcov1847192
-Node: Gcov and Optimization1861432
-Node: Gcov Data Files1864434
-Node: Cross-profiling1865829
-Node: Gcov-tool1867683
-Node: Gcov-tool Intro1868106
-Node: Invoking Gcov-tool1870076
-Node: Trouble1872655
-Node: Actual Bugs1874072
-Node: Interoperation1874519
-Node: Incompatibilities1881410
-Node: Fixed Headers1889562
-Node: Standard Libraries1891220
-Node: Disappointments1892592
-Node: C++ Misunderstandings1896951
-Node: Static Definitions1897762
-Node: Name lookup1898815
-Ref: Name lookup-Footnote-11903595
-Node: Temporaries1903784
-Node: Copy Assignment1905760
-Node: Non-bugs1907567
-Node: Warnings and Errors1918073
-Node: Bugs1919835
-Node: Bug Criteria1920302
-Node: Bug Reporting1922512
-Node: Service1922733
-Node: Contributing1923552
-Node: Funding1924292
-Node: GNU Project1926782
-Node: Copying1927428
-Node: GNU Free Documentation License1964937
-Node: Contributors1990055
-Node: Option Index2028820
-Node: Keyword Index2250669
+Node: Top2022
+Node: G++ and GCC3849
+Node: Standards5918
+Node: Invoking GCC18008
+Node: Option Summary21753
+Node: Overall Options66091
+Node: Invoking G++80329
+Node: C Dialect Options81852
+Node: C++ Dialect Options99118
+Node: Objective-C and Objective-C++ Dialect Options130662
+Node: Language Independent Options141898
+Node: Warning Options146716
+Node: Debugging Options225149
+Node: Optimize Options296345
+Ref: Type-punning359608
+Node: Preprocessor Options448399
+Ref: Wtrigraphs453181
+Ref: dashMF457929
+Ref: fdollars-in-identifiers468793
+Node: Assembler Options479036
+Node: Link Options479728
+Ref: Link Options-Footnote-1493256
+Node: Directory Options493590
+Node: Spec Files500152
+Node: Target Options522023
+Node: Submodel Options522422
+Node: AArch64 Options524187
+Node: Adapteva Epiphany Options529927
+Node: ARC Options535878
+Node: ARM Options548317
+Node: AVR Options566004
+Node: Blackfin Options587298
+Node: C6X Options595313
+Node: CRIS Options596856
+Node: CR16 Options600600
+Node: Darwin Options601507
+Node: DEC Alpha Options608948
+Node: FR30 Options620536
+Node: FRV Options621101
+Node: GNU/Linux Options627820
+Node: H8/300 Options629081
+Node: HPPA Options630531
+Node: IA-64 Options639720
+Node: LM32 Options647765
+Node: M32C Options648289
+Node: M32R/D Options649563
+Node: M680x0 Options653109
+Node: MCore Options667155
+Node: MeP Options668658
+Node: MicroBlaze Options672618
+Node: MIPS Options675414
+Node: MMIX Options708935
+Node: MN10300 Options711417
+Node: Moxie Options713960
+Node: MSP430 Options714448
+Node: NDS32 Options717952
+Node: Nios II Options719846
+Node: Nvidia PTX Options730023
+Node: PDP-11 Options730415
+Node: picoChip Options732112
+Node: PowerPC Options734253
+Node: RL78 Options734474
+Node: RS/6000 and PowerPC Options735322
+Node: RX Options775650
+Node: S/390 and zSeries Options783000
+Node: Score Options791558
+Node: SH Options792400
+Node: Solaris 2 Options813294
+Node: SPARC Options814822
+Node: SPU Options828103
+Node: System V Options833040
+Node: TILE-Gx Options833866
+Node: TILEPro Options834884
+Node: V850 Options835388
+Node: VAX Options842080
+Node: Visium Options842618
+Node: VMS Options844926
+Node: VxWorks Options845740
+Node: x86 Options846892
+Node: x86 Windows Options890475
+Node: Xstormy16 Options893275
+Node: Xtensa Options893569
+Node: zSeries Options897894
+Node: Code Gen Options898090
+Node: Environment Variables928914
+Node: Precompiled Headers936915
+Node: C Implementation942923
+Node: Translation implementation944612
+Node: Environment implementation945204
+Node: Identifiers implementation945759
+Node: Characters implementation946846
+Node: Integers implementation950497
+Node: Floating point implementation952383
+Node: Arrays and pointers implementation955448
+Ref: Arrays and pointers implementation-Footnote-1956907
+Node: Hints implementation957031
+Node: Structures unions enumerations and bit-fields implementation958518
+Node: Qualifiers implementation960743
+Node: Declarators implementation962523
+Node: Statements implementation962865
+Node: Preprocessing directives implementation963192
+Node: Library functions implementation965514
+Node: Architecture implementation966164
+Node: Locale-specific behavior implementation967806
+Node: C++ Implementation968111
+Node: Conditionally-supported behavior969393
+Node: Exception handling970011
+Node: C Extensions970420
+Node: Statement Exprs975578
+Node: Local Labels980054
+Node: Labels as Values983027
+Ref: Labels as Values-Footnote-1985552
+Node: Nested Functions985735
+Node: Constructing Calls989693
+Node: Typeof994411
+Node: Conditionals998339
+Node: __int128999229
+Node: Long Long999753
+Node: Complex1001229
+Node: Floating Types1003818
+Node: Half-Precision1004938
+Node: Decimal Float1007120
+Node: Hex Floats1008975
+Node: Fixed-Point1010011
+Node: Named Address Spaces1013293
+Ref: AVR Named Address Spaces1013974
+Node: Zero Length1019180
+Node: Empty Structures1022219
+Node: Variable Length1022625
+Node: Variadic Macros1025481
+Node: Escaped Newlines1027859
+Node: Subscripting1028720
+Node: Pointer Arith1029446
+Node: Pointers to Arrays1030020
+Node: Initializers1030764
+Node: Compound Literals1031265
+Node: Designated Inits1034612
+Node: Case Ranges1038350
+Node: Cast to Union1039031
+Node: Mixed Declarations1040122
+Node: Function Attributes1040632
+Node: Label Attributes1134480
+Node: Attribute Syntax1136324
+Node: Function Prototypes1146538
+Node: C++ Comments1148319
+Node: Dollar Signs1148838
+Node: Character Escapes1149303
+Node: Variable Attributes1149597
+Ref: AVR Variable Attributes1163318
+Ref: MeP Variable Attributes1168683
+Ref: x86 Variable Attributes1171253
+Node: Type Attributes1176292
+Ref: MeP Type Attributes1191541
+Ref: PowerPC Type Attributes1191815
+Ref: SPU Type Attributes1192676
+Ref: x86 Type Attributes1192967
+Node: Alignment1193655
+Node: Inline1195025
+Node: Volatiles1200000
+Node: Using Assembly Language with C1202900
+Node: Basic Asm1204104
+Node: Extended Asm1208238
+Ref: Volatile1212035
+Ref: AssemblerTemplate1216107
+Ref: OutputOperands1220332
+Ref: InputOperands1227234
+Ref: Clobbers1231459
+Ref: GotoLabels1234755
+Ref: x86Operandmodifiers1236888
+Ref: x86floatingpointasmoperands1239132
+Node: Constraints1242462
+Node: Simple Constraints1243568
+Node: Multi-Alternative1250893
+Node: Modifiers1252900
+Node: Machine Constraints1256404
+Node: Asm Labels1312867
+Node: Explicit Reg Vars1314565
+Node: Global Reg Vars1316186
+Node: Local Reg Vars1320686
+Node: Size of an asm1323806
+Node: Alternate Keywords1325051
+Node: Incomplete Enums1326550
+Node: Function Names1327306
+Node: Return Address1328909
+Node: Vector Extensions1332416
+Node: Offsetof1339701
+Node: __sync Builtins1340542
+Node: __atomic Builtins1346018
+Node: Integer Overflow Builtins1357621
+Node: x86 specific memory model extensions for transactional memory1361751
+Node: Object Size Checking1363020
+Node: Pointer Bounds Checker builtins1368526
+Node: Cilk Plus Builtins1374532
+Node: Other Builtins1375448
+Node: Target Builtins1405092
+Node: AArch64 Built-in Functions1406584
+Node: Alpha Built-in Functions1407039
+Node: Altera Nios II Built-in Functions1410087
+Node: ARC Built-in Functions1414072
+Node: ARC SIMD Built-in Functions1419283
+Node: ARM iWMMXt Built-in Functions1428179
+Node: ARM C Language Extensions (ACLE)1435175
+Node: ARM Floating Point Status and Control Intrinsics1436452
+Node: AVR Built-in Functions1436928
+Node: Blackfin Built-in Functions1440027
+Node: FR-V Built-in Functions1440646
+Node: Argument Types1441512
+Node: Directly-mapped Integer Functions1443266
+Node: Directly-mapped Media Functions1444350
+Node: Raw read/write Functions1451384
+Node: Other Built-in Functions1452298
+Node: MIPS DSP Built-in Functions1453484
+Node: MIPS Paired-Single Support1465982
+Node: MIPS Loongson Built-in Functions1467481
+Node: Paired-Single Arithmetic1474001
+Node: Paired-Single Built-in Functions1474949
+Node: MIPS-3D Built-in Functions1477616
+Node: Other MIPS Built-in Functions1482993
+Node: MSP430 Built-in Functions1483998
+Node: NDS32 Built-in Functions1485399
+Node: picoChip Built-in Functions1486692
+Node: PowerPC Built-in Functions1488036
+Node: PowerPC AltiVec/VSX Built-in Functions1491743
+Node: PowerPC Hardware Transactional Memory Built-in Functions1631534
+Node: RX Built-in Functions1638507
+Node: S/390 System z Built-in Functions1642540
+Node: SH Built-in Functions1647777
+Node: SPARC VIS Built-in Functions1649505
+Node: SPU Built-in Functions1655109
+Node: TI C6X Built-in Functions1656925
+Node: TILE-Gx Built-in Functions1657949
+Node: TILEPro Built-in Functions1659066
+Node: x86 Built-in Functions1660164
+Node: x86 transactional memory intrinsics1719699
+Node: Target Format Checks1722919
+Node: Solaris Format Checks1723351
+Node: Darwin Format Checks1723777
+Node: Pragmas1724595
+Node: ARM Pragmas1725331
+Node: M32C Pragmas1725934
+Node: MeP Pragmas1727008
+Node: RS/6000 and PowerPC Pragmas1729077
+Node: Darwin Pragmas1729818
+Node: Solaris Pragmas1730885
+Node: Symbol-Renaming Pragmas1732046
+Node: Structure-Packing Pragmas1733660
+Node: Weak Pragmas1735309
+Node: Diagnostic Pragmas1736043
+Node: Visibility Pragmas1739150
+Node: Push/Pop Macro Pragmas1739835
+Node: Function Specific Option Pragmas1740807
+Node: Loop-Specific Pragmas1742652
+Node: Unnamed Fields1743742
+Node: Thread-Local1745940
+Node: C99 Thread-Local Edits1748045
+Node: C++98 Thread-Local Edits1750057
+Node: Binary constants1753501
+Node: C++ Extensions1754172
+Node: C++ Volatiles1755883
+Node: Restricted Pointers1758231
+Node: Vague Linkage1759822
+Node: C++ Interface1763446
+Ref: C++ Interface-Footnote-11767239
+Node: Template Instantiation1767375
+Node: Bound member functions1773961
+Node: C++ Attributes1775493
+Node: Function Multiversioning1779930
+Node: Namespace Association1781745
+Node: Type Traits1783125
+Node: Java Exceptions1789613
+Node: Deprecated Features1791003
+Node: Backwards Compatibility1793968
+Node: Objective-C1795320
+Node: GNU Objective-C runtime API1795929
+Node: Modern GNU Objective-C runtime API1796936
+Node: Traditional GNU Objective-C runtime API1799373
+Node: Executing code before main1800101
+Node: What you can and what you cannot do in +load1802843
+Node: Type encoding1805215
+Node: Legacy type encoding1810291
+Node: @encode1811382
+Node: Method signatures1811927
+Node: Garbage Collection1813922
+Node: Constant string objects1816611
+Node: compatibility_alias1819119
+Node: Exceptions1819845
+Node: Synchronization1822556
+Node: Fast enumeration1823740
+Node: Using fast enumeration1824052
+Node: c99-like fast enumeration syntax1825263
+Node: Fast enumeration details1825966
+Node: Fast enumeration protocol1828307
+Node: Messaging with the GNU Objective-C runtime1831459
+Node: Dynamically registering methods1832830
+Node: Forwarding hook1834521
+Node: Compatibility1837561
+Node: Gcov1844128
+Node: Gcov Intro1844663
+Node: Invoking Gcov1847381
+Node: Gcov and Optimization1861627
+Node: Gcov Data Files1864627
+Node: Cross-profiling1866022
+Node: Gcov-tool1867873
+Node: Gcov-tool Intro1868296
+Node: Invoking Gcov-tool1870257
+Node: Trouble1872805
+Node: Actual Bugs1874222
+Node: Interoperation1874669
+Node: Incompatibilities1881561
+Node: Fixed Headers1889712
+Node: Standard Libraries1891375
+Node: Disappointments1892747
+Node: C++ Misunderstandings1897105
+Node: Static Definitions1897916
+Node: Name lookup1898969
+Ref: Name lookup-Footnote-11903747
+Node: Temporaries1903934
+Node: Copy Assignment1905910
+Node: Non-bugs1907717
+Node: Warnings and Errors1918224
+Node: Bugs1919986
+Node: Bug Criteria1920453
+Node: Bug Reporting1922663
+Node: Service1922884
+Node: Contributing1923703
+Node: Funding1924443
+Node: GNU Project1926932
+Node: Copying1927578
+Node: GNU Free Documentation License1965106
+Node: Contributors1990243
+Node: Option Index2029011
+Node: Keyword Index2249768

End Tag Table
diff --git a/gcc/doc/gccinstall.info b/gcc/doc/gccinstall.info
index bdf2e81398..d6cf84462e 100644
--- a/gcc/doc/gccinstall.info
+++ b/gcc/doc/gccinstall.info
@@ -1,5 +1,5 @@
-This is gccinstall.info, produced by makeinfo version 5.2 from
-install.texi.
+This is doc/gccinstall.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/doc/install.texi.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -17,12 +17,8 @@ is included in the section entitled "GNU Free Documentation License".
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
-INFO-DIR-SECTION Software development
-START-INFO-DIR-ENTRY
-* gccinstall: (gccinstall). Installing the GNU Compiler Collection.
-END-INFO-DIR-ENTRY
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -40,8 +36,13 @@ is included in the section entitled "GNU Free Documentation License".
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+
+INFO-DIR-SECTION Software development
+START-INFO-DIR-ENTRY
+* gccinstall: (gccinstall). Installing the GNU Compiler Collection.
+END-INFO-DIR-ENTRY

File: gccinstall.info, Node: Top, Up: (dir)
@@ -66,13 +67,13 @@ File: gccinstall.info, Node: Installing GCC, Next: Binaries, Up: Top
1 Installing GCC
****************
-The latest version of this document is always available at
+ The latest version of this document is always available at
http://gcc.gnu.org/install/. It refers to the current development
sources, instructions for specific released versions are included with
the sources.
- This document describes the generic installation procedure for GCC as
-well as detailing some target specific installation instructions.
+ This document describes the generic installation procedure for GCC
+as well as detailing some target specific installation instructions.
GCC includes several components that previously were separate
distributions with their own installation instructions. This document
@@ -82,9 +83,9 @@ supersedes all package-specific installation instructions.
host/target specific installation notes: Specific. We recommend you
browse the entire generic installation instructions before you proceed.
- Lists of successful builds for released versions of GCC are available
-at <http://gcc.gnu.org/buildstat.html>. These lists are updated as new
-information becomes available.
+ Lists of successful builds for released versions of GCC are
+available at `http://gcc.gnu.org/buildstat.html'. These lists are
+updated as new information becomes available.
The installation procedure itself is broken into five steps.
@@ -97,12 +98,12 @@ information becomes available.
* Testing:: (optional)
* Final install::
- Please note that GCC does not support 'make uninstall' and probably
+ Please note that GCC does not support `make uninstall' and probably
won't do so in the near future as this would open a can of worms.
-Instead, we suggest that you install GCC into a directory of its own and
-simply remove that directory when you do not need that specific version
-of GCC any longer, and, if shared libraries are installed there as well,
-no more binaries exist that use them.
+Instead, we suggest that you install GCC into a directory of its own
+and simply remove that directory when you do not need that specific
+version of GCC any longer, and, if shared libraries are installed there
+as well, no more binaries exist that use them.

File: gccinstall.info, Node: Prerequisites, Next: Downloading the source, Up: Installing GCC
@@ -110,8 +111,8 @@ File: gccinstall.info, Node: Prerequisites, Next: Downloading the source, Up:
2 Prerequisites
***************
-GCC requires that various tools and packages be available for use in the
-build procedure. Modifying GCC sources requires additional tools
+ GCC requires that various tools and packages be available for use in
+the build procedure. Modifying GCC sources requires additional tools
described below.
Tools/packages necessary for building GCC
@@ -124,269 +125,245 @@ ISO C++98 compiler
C compiler.
To build all languages in a cross-compiler or other configuration
- where 3-stage bootstrap is not performed, you need to start with an
- existing GCC binary (version 3.4 or later) because source code for
- language frontends other than C might use GCC extensions.
+ where 3-stage bootstrap is not performed, you need to start with
+ an existing GCC binary (version 3.4 or later) because source code
+ for language frontends other than C might use GCC extensions.
Note that to bootstrap GCC with versions of GCC earlier than 3.4,
- you may need to use '--disable-stage1-checking', though
+ you may need to use `--disable-stage1-checking', though
bootstrapping the compiler with such earlier compilers is strongly
discouraged.
C standard library and headers
-
In order to build GCC, the C standard library and headers must be
present for all target variants for which target libraries will be
built (and not only the variant of the host C++ compiler).
- This affects the popular 'x86_64-unknown-linux-gnu' platform (among
- other multilib targets), for which 64-bit ('x86_64') and 32-bit
- ('i386') libc headers are usually packaged separately. If you do a
- build of a native compiler on 'x86_64-unknown-linux-gnu', make sure
- you either have the 32-bit libc developer package properly
- installed (the exact name of the package depends on your distro) or
- you must build GCC as a 64-bit only compiler by configuring with
- the option '--disable-multilib'. Otherwise, you may encounter an
- error such as 'fatal error: gnu/stubs-32.h: No such file'
+ This affects the popular `x86_64-unknown-linux-gnu' platform (among
+ other multilib targets), for which 64-bit (`x86_64') and 32-bit
+ (`i386') libc headers are usually packaged separately. If you do a
+ build of a native compiler on `x86_64-unknown-linux-gnu', make
+ sure you either have the 32-bit libc developer package properly
+ installed (the exact name of the package depends on your distro)
+ or you must build GCC as a 64-bit only compiler by configuring
+ with the option `--disable-multilib'. Otherwise, you may
+ encounter an error such as `fatal error: gnu/stubs-32.h: No such
+ file'
GNAT
-
In order to build the Ada compiler (GNAT) you must already have
GNAT installed because portions of the Ada frontend are written in
Ada (with GNAT extensions.) Refer to the Ada installation
instructions for more specific information.
A "working" POSIX compatible shell, or GNU bash
-
- Necessary when running 'configure' because some '/bin/sh' shells
+ Necessary when running `configure' because some `/bin/sh' shells
have bugs and may crash when configuring the target libraries. In
- other cases, '/bin/sh' or 'ksh' have disastrous corner-case
- performance problems. This can cause target 'configure' runs to
+ other cases, `/bin/sh' or `ksh' have disastrous corner-case
+ performance problems. This can cause target `configure' runs to
literally take days to complete in some cases.
- So on some platforms '/bin/ksh' is sufficient, on others it isn't.
- See the host/target specific instructions for your platform, or use
- 'bash' to be sure. Then set 'CONFIG_SHELL' in your environment to
- your "good" shell prior to running 'configure'/'make'.
+ So on some platforms `/bin/ksh' is sufficient, on others it isn't.
+ See the host/target specific instructions for your platform, or
+ use `bash' to be sure. Then set `CONFIG_SHELL' in your
+ environment to your "good" shell prior to running
+ `configure'/`make'.
- 'zsh' is not a fully compliant POSIX shell and will not work when
+ `zsh' is not a fully compliant POSIX shell and will not work when
configuring GCC.
A POSIX or SVR4 awk
-
Necessary for creating some of the generated source files for GCC.
If in doubt, use a recent GNU awk version, as some of the older
ones are broken. GNU awk version 3.1.5 is known to work.
GNU binutils
-
Necessary in some circumstances, optional in others. See the
host/target specific instructions for your platform for the exact
requirements.
gzip version 1.2.4 (or later) or
bzip2 version 1.0.2 (or later)
-
- Necessary to uncompress GCC 'tar' files when source code is
+ Necessary to uncompress GCC `tar' files when source code is
obtained via FTP mirror sites.
GNU make version 3.80 (or later)
-
You must have GNU make installed to build GCC.
GNU tar version 1.14 (or later)
-
Necessary (only on some platforms) to untar the source code. Many
- systems' 'tar' programs will also work, only try GNU 'tar' if you
+ systems' `tar' programs will also work, only try GNU `tar' if you
have problems.
Perl version 5.6.1 (or later)
+ Necessary when targeting Darwin, building `libstdc++', and not
+ using `--disable-symvers'. Necessary when targeting Solaris 2
+ with Sun `ld' and not using `--disable-symvers'. The bundled
+ `perl' in Solaris 8 and up works.
- Necessary when targeting Darwin, building 'libstdc++', and not
- using '--disable-symvers'. Necessary when targeting Solaris 2 with
- Sun 'ld' and not using '--disable-symvers'. The bundled 'perl' in
- Solaris 8 and up works.
-
- Necessary when regenerating 'Makefile' dependencies in libiberty.
- Necessary when regenerating 'libiberty/functions.texi'. Necessary
+ Necessary when regenerating `Makefile' dependencies in libiberty.
+ Necessary when regenerating `libiberty/functions.texi'. Necessary
when generating manpages from Texinfo manuals. Used by various
scripts to generate some files included in SVN (mainly
Unicode-related and rarely changing) from source tables.
-'jar', or InfoZIP ('zip' and 'unzip')
-
+`jar', or InfoZIP (`zip' and `unzip')
Necessary to build libgcj, the GCJ runtime.
+
Several support libraries are necessary to build GCC, some are
required, others optional. While any sufficiently new version of
required tools usually work, library requirements are generally
stricter. Newer versions may work in some cases, but it's safer to use
-the exact versions documented. We appreciate bug reports about problems
-with newer versions, though. If your OS vendor provides packages for
-the support libraries then using those packages may be the simplest way
-to install the libraries.
+the exact versions documented. We appreciate bug reports about
+problems with newer versions, though. If your OS vendor provides
+packages for the support libraries then using those packages may be the
+simplest way to install the libraries.
GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
-
Necessary to build GCC. If a GMP source distribution is found in a
- subdirectory of your GCC sources named 'gmp', it will be built
- together with GCC. Alternatively, if GMP is already installed but
+ subdirectory of your GCC sources named `gmp', it will be built
+ together with GCC. Alternatively, if GMP is already installed but
it is not in your library search path, you will have to configure
- with the '--with-gmp' configure option. See also '--with-gmp-lib'
- and '--with-gmp-include'.
+ with the `--with-gmp' configure option. See also `--with-gmp-lib'
+ and `--with-gmp-include'.
MPFR Library version 2.4.2 (or later)
-
Necessary to build GCC. It can be downloaded from
- <http://www.mpfr.org/>. If an MPFR source distribution is found in
- a subdirectory of your GCC sources named 'mpfr', it will be built
- together with GCC. Alternatively, if MPFR is already installed but
- it is not in your default library search path, the '--with-mpfr'
- configure option should be used. See also '--with-mpfr-lib' and
- '--with-mpfr-include'.
+ `http://www.mpfr.org/'. If an MPFR source distribution is found
+ in a subdirectory of your GCC sources named `mpfr', it will be
+ built together with GCC. Alternatively, if MPFR is already
+ installed but it is not in your default library search path, the
+ `--with-mpfr' configure option should be used. See also
+ `--with-mpfr-lib' and `--with-mpfr-include'.
MPC Library version 0.8.1 (or later)
-
Necessary to build GCC. It can be downloaded from
- <http://www.multiprecision.org/>. If an MPC source distribution is
- found in a subdirectory of your GCC sources named 'mpc', it will be
- built together with GCC. Alternatively, if MPC is already installed
- but it is not in your default library search path, the '--with-mpc'
- configure option should be used. See also '--with-mpc-lib' and
- '--with-mpc-include'.
+ `http://www.multiprecision.org/'. If an MPC source distribution
+ is found in a subdirectory of your GCC sources named `mpc', it
+ will be built together with GCC. Alternatively, if MPC is already
+ installed but it is not in your default library search path, the
+ `--with-mpc' configure option should be used. See also
+ `--with-mpc-lib' and `--with-mpc-include'.
ISL Library version 0.14 (or 0.12.2)
-
Necessary to build GCC with the Graphite loop optimizations. It
- can be downloaded from <ftp://gcc.gnu.org/pub/gcc/infrastructure/>
- as 'isl-0.12.2.tar.bz2'. If an ISL source distribution is found in
- a subdirectory of your GCC sources named 'isl', it will be built
- together with GCC. Alternatively, the '--with-isl' configure option
- should be used if ISL is not installed in your default library
- search path.
+ can be downloaded from `ftp://gcc.gnu.org/pub/gcc/infrastructure/'
+ as `isl-0.12.2.tar.bz2'. If an ISL source distribution is found
+ in a subdirectory of your GCC sources named `isl', it will be
+ built together with GCC. Alternatively, the `--with-isl' configure
+ option should be used if ISL is not installed in your default
+ library search path.
+
Tools/packages necessary for modifying GCC
==========================================
autoconf version 2.64
GNU m4 version 1.4.6 (or later)
-
- Necessary when modifying 'configure.ac', 'aclocal.m4', etc. to
- regenerate 'configure' and 'config.in' files.
+ Necessary when modifying `configure.ac', `aclocal.m4', etc. to
+ regenerate `configure' and `config.in' files.
automake version 1.11.1
-
- Necessary when modifying a 'Makefile.am' file to regenerate its
- associated 'Makefile.in'.
+ Necessary when modifying a `Makefile.am' file to regenerate its
+ associated `Makefile.in'.
Much of GCC does not use automake, so directly edit the
- 'Makefile.in' file. Specifically this applies to the 'gcc',
- 'intl', 'libcpp', 'libiberty', 'libobjc' directories as well as any
- of their subdirectories.
+ `Makefile.in' file. Specifically this applies to the `gcc',
+ `intl', `libcpp', `libiberty', `libobjc' directories as well as
+ any of their subdirectories.
For directories that use automake, GCC requires the latest release
- in the 1.11 series, which is currently 1.11.1. When regenerating a
- directory to a newer version, please update all the directories
+ in the 1.11 series, which is currently 1.11.1. When regenerating
+ a directory to a newer version, please update all the directories
using an older 1.11 to the latest released version.
gettext version 0.14.5 (or later)
-
- Needed to regenerate 'gcc.pot'.
+ Needed to regenerate `gcc.pot'.
gperf version 2.7.2 (or later)
-
- Necessary when modifying 'gperf' input files, e.g.
- 'gcc/cp/cfns.gperf' to regenerate its associated header file, e.g.
- 'gcc/cp/cfns.h'.
+ Necessary when modifying `gperf' input files, e.g.
+ `gcc/cp/cfns.gperf' to regenerate its associated header file, e.g.
+ `gcc/cp/cfns.h'.
DejaGnu 1.4.4
Expect
Tcl
-
Necessary to run the GCC testsuite; see the section on testing for
details. Tcl 8.6 has a known regression in RE pattern handling
that make parts of the testsuite fail. See
- <http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f>
+ `http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f'
for more information. This bug has been fixed in 8.6.1.
autogen version 5.5.4 (or later) and
guile version 1.4.1 (or later)
+ Necessary to regenerate `fixinc/fixincl.x' from
+ `fixinc/inclhack.def' and `fixinc/*.tpl'.
- Necessary to regenerate 'fixinc/fixincl.x' from
- 'fixinc/inclhack.def' and 'fixinc/*.tpl'.
-
- Necessary to run 'make check' for 'fixinc'.
+ Necessary to run `make check' for `fixinc'.
- Necessary to regenerate the top level 'Makefile.in' file from
- 'Makefile.tpl' and 'Makefile.def'.
+ Necessary to regenerate the top level `Makefile.in' file from
+ `Makefile.tpl' and `Makefile.def'.
Flex version 2.5.4 (or later)
-
- Necessary when modifying '*.l' files.
+ Necessary when modifying `*.l' files.
Necessary to build GCC during development because the generated
output files are not included in the SVN repository. They are
included in releases.
Texinfo version 4.7 (or later)
-
- Necessary for running 'makeinfo' when modifying '*.texi' files to
+ Necessary for running `makeinfo' when modifying `*.texi' files to
test your changes.
- Necessary for running 'make dvi' or 'make pdf' to create printable
+ Necessary for running `make dvi' or `make pdf' to create printable
documentation in DVI or PDF format. Texinfo version 4.8 or later
- is required for 'make pdf'.
+ is required for `make pdf'.
Necessary to build GCC documentation during development because the
generated output files are not included in the SVN repository.
They are included in releases.
TeX (any working version)
-
- Necessary for running 'texi2dvi' and 'texi2pdf', which are used
- when running 'make dvi' or 'make pdf' to create DVI or PDF files,
+ Necessary for running `texi2dvi' and `texi2pdf', which are used
+ when running `make dvi' or `make pdf' to create DVI or PDF files,
respectively.
Sphinx version 1.0 (or later)
-
- Necessary to regenerate 'jit/docs/_build/texinfo' from the '.rst'
- files in the directories below 'jit/docs'.
+ Necessary to regenerate `jit/docs/_build/texinfo' from the `.rst'
+ files in the directories below `jit/docs'.
SVN (any version)
SSH (any version)
-
Necessary to access the SVN repository. Public releases and weekly
snapshots of the development sources are also available via FTP.
GNU diffutils version 2.7 (or later)
-
Useful when submitting patches for the GCC source code.
patch version 2.5.4 (or later)
-
- Necessary when applying patches, created with 'diff', to one's own
+ Necessary when applying patches, created with `diff', to one's own
sources.
ecj1
gjavah
-
- If you wish to modify '.java' files in libjava, you will need to
- configure with '--enable-java-maintainer-mode', and you will need
- to have executables named 'ecj1' and 'gjavah' in your path. The
- 'ecj1' executable should run the Eclipse Java compiler via the
+ If you wish to modify `.java' files in libjava, you will need to
+ configure with `--enable-java-maintainer-mode', and you will need
+ to have executables named `ecj1' and `gjavah' in your path. The
+ `ecj1' executable should run the Eclipse Java compiler via the
GCC-specific entry point. You can download a suitable jar from
- <ftp://sourceware.org/pub/java/>, or by running the script
- 'contrib/download_ecj'.
+ `ftp://sourceware.org/pub/java/', or by running the script
+ `contrib/download_ecj'.
antlr.jar version 2.7.1 (or later)
antlr binary
-
- If you wish to build the 'gjdoc' binary in libjava, you will need
- to have an 'antlr.jar' library available. The library is searched
+ If you wish to build the `gjdoc' binary in libjava, you will need
+ to have an `antlr.jar' library available. The library is searched
for in system locations but can be specified with
- '--with-antlr-jar=' instead. When configuring with
- '--enable-java-maintainer-mode', you will need to have one of the
- executables named 'cantlr', 'runantlr' or 'antlr' in your path.
+ `--with-antlr-jar=' instead. When configuring with
+ `--enable-java-maintainer-mode', you will need to have one of the
+ executables named `cantlr', `runantlr' or `antlr' in your path.
+

File: gccinstall.info, Node: Downloading the source, Next: Configuration, Prev: Prerequisites, Up: Installing GCC
@@ -394,33 +371,33 @@ File: gccinstall.info, Node: Downloading the source, Next: Configuration, Pre
3 Downloading GCC
*****************
-GCC is distributed via SVN and FTP tarballs compressed with 'gzip' or
-'bzip2'.
+ GCC is distributed via SVN and FTP tarballs compressed with `gzip' or
+`bzip2'.
Please refer to the releases web page for information on how to
obtain GCC.
The source distribution includes the C, C++, Objective-C, Fortran,
Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as
-runtime libraries for C++, Objective-C, Fortran, and Java. For previous
-versions these were downloadable as separate components such as the core
-GCC distribution, which included the C language front end and shared
-components, and language-specific distributions including the language
-front end and the language runtime (where appropriate).
+runtime libraries for C++, Objective-C, Fortran, and Java. For
+previous versions these were downloadable as separate components such
+as the core GCC distribution, which included the C language front end
+and shared components, and language-specific distributions including the
+language front end and the language runtime (where appropriate).
If you also intend to build binutils (either to upgrade an existing
-installation or for use in place of the corresponding tools of your OS),
-unpack the binutils distribution either in the same directory or a
+installation or for use in place of the corresponding tools of your
+OS), unpack the binutils distribution either in the same directory or a
separate one. In the latter case, add symbolic links to any components
-of the binutils you intend to build alongside the compiler ('bfd',
-'binutils', 'gas', 'gprof', 'ld', 'opcodes', ...) to the directory
+of the binutils you intend to build alongside the compiler (`bfd',
+`binutils', `gas', `gprof', `ld', `opcodes', ...) to the directory
containing the GCC sources.
Likewise the GMP, MPFR and MPC libraries can be automatically built
-together with GCC. Unpack the GMP, MPFR and/or MPC source distributions
-in the directory containing the GCC sources and rename their directories
-to 'gmp', 'mpfr' and 'mpc', respectively (or use symbolic links with the
-same name).
+together with GCC. Unpack the GMP, MPFR and/or MPC source
+distributions in the directory containing the GCC sources and rename
+their directories to `gmp', `mpfr' and `mpc', respectively (or use
+symbolic links with the same name).

File: gccinstall.info, Node: Configuration, Next: Building, Prev: Downloading the source, Up: Installing GCC
@@ -428,22 +405,22 @@ File: gccinstall.info, Node: Configuration, Next: Building, Prev: Downloading
4 Installing GCC: Configuration
*******************************
-Like most GNU software, GCC must be configured before it can be built.
-This document describes the recommended configuration procedure for both
-native and cross targets.
+ Like most GNU software, GCC must be configured before it can be
+built. This document describes the recommended configuration procedure
+for both native and cross targets.
We use SRCDIR to refer to the toplevel source directory for GCC; we
use OBJDIR to refer to the toplevel build/object directory.
If you obtained the sources via SVN, SRCDIR must refer to the top
-'gcc' directory, the one where the 'MAINTAINERS' file can be found, and
-not its 'gcc' subdirectory, otherwise the build will fail.
+`gcc' directory, the one where the `MAINTAINERS' file can be found, and
+not its `gcc' subdirectory, otherwise the build will fail.
If either SRCDIR or OBJDIR is located on an automounted NFS file
-system, the shell's built-in 'pwd' command will return temporary
-pathnames. Using these can lead to various sorts of build problems. To
-avoid this issue, set the 'PWDCMD' environment variable to an
-automounter-aware 'pwd' command, e.g., 'pawd' or 'amq -w', during the
+system, the shell's built-in `pwd' command will return temporary
+pathnames. Using these can lead to various sorts of build problems.
+To avoid this issue, set the `PWDCMD' environment variable to an
+automounter-aware `pwd' command, e.g., `pawd' or `amq -w', during the
configuration and build phases.
First, we *highly* recommend that GCC be built into a separate
@@ -453,16 +430,16 @@ OBJDIR should still work, but doesn't get extensive testing; building
where OBJDIR is a subdirectory of SRCDIR is unsupported.
If you have previously built GCC in the same directory for a
-different target machine, do 'make distclean' to delete all files that
-might be invalid. One of the files this deletes is 'Makefile'; if 'make
-distclean' complains that 'Makefile' does not exist or issues a message
-like "don't know how to make distclean" it probably means that the
-directory is already suitably clean. However, with the recommended
+different target machine, do `make distclean' to delete all files that
+might be invalid. One of the files this deletes is `Makefile'; if
+`make distclean' complains that `Makefile' does not exist or issues a
+message like "don't know how to make distclean" it probably means that
+the directory is already suitably clean. However, with the recommended
method of building in a separate OBJDIR, you should simply use a
different OBJDIR for each target.
- Second, when configuring a native system, either 'cc' or 'gcc' must
-be in your path or you must set 'CC' in your environment before running
+ Second, when configuring a native system, either `cc' or `gcc' must
+be in your path or you must set `CC' in your environment before running
configure. Otherwise the configuration scripts may fail.
To configure GCC:
@@ -475,18 +452,18 @@ Distributor options
===================
If you will be distributing binary versions of GCC, with modifications
-to the source code, you should use the options described in this section
-to make clear that your version contains modifications.
+to the source code, you should use the options described in this
+section to make clear that your version contains modifications.
-'--with-pkgversion=VERSION'
+`--with-pkgversion=VERSION'
Specify a string that identifies your package. You may wish to
include a build number or build date. This version string will be
- included in the output of 'gcc --version'. This suffix does not
- replace the default version string, only the 'GCC' part.
+ included in the output of `gcc --version'. This suffix does not
+ replace the default version string, only the `GCC' part.
- The default value is 'GCC'.
+ The default value is `GCC'.
-'--with-bugurl=URL'
+`--with-bugurl=URL'
Specify the URL that users should visit if they wish to report a
bug. You are of course welcome to forward bugs reported to you to
the FSF, if you determine that they are not bugs in your
@@ -494,6 +471,7 @@ to make clear that your version contains modifications.
The default value refers to the FSF's GCC bug tracker.
+
Target specification
====================
@@ -502,135 +480,137 @@ Target specification
do not provide a configure target when configuring a native
compiler.
- * TARGET must be specified as '--target=TARGET' when configuring a
+ * TARGET must be specified as `--target=TARGET' when configuring a
cross compiler; examples of valid targets would be m68k-elf,
sh-elf, etc.
- * Specifying just TARGET instead of '--target=TARGET' implies that
+ * Specifying just TARGET instead of `--target=TARGET' implies that
the host defaults to TARGET.
Options specification
=====================
Use OPTIONS to override several configure time options for GCC. A list
-of supported OPTIONS follows; 'configure --help' may list other options,
-but those not listed below may not work and should not normally be used.
+of supported OPTIONS follows; `configure --help' may list other
+options, but those not listed below may not work and should not
+normally be used.
- Note that each '--enable' option has a corresponding '--disable'
-option and that each '--with' option has a corresponding '--without'
+ Note that each `--enable' option has a corresponding `--disable'
+option and that each `--with' option has a corresponding `--without'
option.
-'--prefix=DIRNAME'
+`--prefix=DIRNAME'
Specify the toplevel installation directory. This is the
recommended way to install the tools into a directory other than
the default. The toplevel installation directory defaults to
- '/usr/local'.
+ `/usr/local'.
We *highly* recommend against DIRNAME being the same or a
subdirectory of OBJDIR or vice versa. If specifying a directory
beneath a user's home directory tree, some shells will not expand
- DIRNAME correctly if it contains the '~' metacharacter; use '$HOME'
- instead.
+ DIRNAME correctly if it contains the `~' metacharacter; use
+ `$HOME' instead.
- The following standard 'autoconf' options are supported. Normally
+ The following standard `autoconf' options are supported. Normally
you should not need to use these options.
- '--exec-prefix=DIRNAME'
+ `--exec-prefix=DIRNAME'
Specify the toplevel installation directory for
- architecture-dependent files. The default is 'PREFIX'.
+ architecture-dependent files. The default is `PREFIX'.
- '--bindir=DIRNAME'
+ `--bindir=DIRNAME'
Specify the installation directory for the executables called
- by users (such as 'gcc' and 'g++'). The default is
- 'EXEC-PREFIX/bin'.
+ by users (such as `gcc' and `g++'). The default is
+ `EXEC-PREFIX/bin'.
- '--libdir=DIRNAME'
+ `--libdir=DIRNAME'
Specify the installation directory for object code libraries
and internal data files of GCC. The default is
- 'EXEC-PREFIX/lib'.
+ `EXEC-PREFIX/lib'.
- '--libexecdir=DIRNAME'
- Specify the installation directory for internal executables of
- GCC. The default is 'EXEC-PREFIX/libexec'.
+ `--libexecdir=DIRNAME'
+ Specify the installation directory for internal executables
+ of GCC. The default is `EXEC-PREFIX/libexec'.
- '--with-slibdir=DIRNAME'
+ `--with-slibdir=DIRNAME'
Specify the installation directory for the shared libgcc
- library. The default is 'LIBDIR'.
+ library. The default is `LIBDIR'.
- '--datarootdir=DIRNAME'
+ `--datarootdir=DIRNAME'
Specify the root of the directory tree for read-only
architecture-independent data files referenced by GCC. The
- default is 'PREFIX/share'.
+ default is `PREFIX/share'.
- '--infodir=DIRNAME'
+ `--infodir=DIRNAME'
Specify the installation directory for documentation in info
- format. The default is 'DATAROOTDIR/info'.
+ format. The default is `DATAROOTDIR/info'.
- '--datadir=DIRNAME'
+ `--datadir=DIRNAME'
Specify the installation directory for some
architecture-independent data files referenced by GCC. The
- default is 'DATAROOTDIR'.
+ default is `DATAROOTDIR'.
- '--docdir=DIRNAME'
+ `--docdir=DIRNAME'
Specify the installation directory for documentation files
- (other than Info) for GCC. The default is 'DATAROOTDIR/doc'.
+ (other than Info) for GCC. The default is `DATAROOTDIR/doc'.
- '--htmldir=DIRNAME'
+ `--htmldir=DIRNAME'
Specify the installation directory for HTML documentation
- files. The default is 'DOCDIR'.
+ files. The default is `DOCDIR'.
- '--pdfdir=DIRNAME'
+ `--pdfdir=DIRNAME'
Specify the installation directory for PDF documentation
- files. The default is 'DOCDIR'.
+ files. The default is `DOCDIR'.
- '--mandir=DIRNAME'
+ `--mandir=DIRNAME'
Specify the installation directory for manual pages. The
- default is 'DATAROOTDIR/man'. (Note that the manual pages are
- only extracts from the full GCC manuals, which are provided in
- Texinfo format. The manpages are derived by an automatic
- conversion process from parts of the full manual.)
+ default is `DATAROOTDIR/man'. (Note that the manual pages
+ are only extracts from the full GCC manuals, which are
+ provided in Texinfo format. The manpages are derived by an
+ automatic conversion process from parts of the full manual.)
- '--with-gxx-include-dir=DIRNAME'
+ `--with-gxx-include-dir=DIRNAME'
Specify the installation directory for G++ header files. The
default depends on other configuration options, and differs
between cross and native configurations.
- '--with-specs=SPECS'
- Specify additional command line driver SPECS. This can be
+ `--with-specs=SPECS'
+ Specify additional command line driver SPECS. This can be
useful if you need to turn on a non-standard feature by
default without modifying the compiler's source code, for
instance
- '--with-specs=%{!fcommon:%{!fno-common:-fno-common}}'. *Note
+ `--with-specs=%{!fcommon:%{!fno-common:-fno-common}}'. *Note
Specifying subprocesses and the switches to pass to them:
(gcc)Spec Files,
-'--program-prefix=PREFIX'
+
+`--program-prefix=PREFIX'
GCC supports some transformations of the names of its programs when
installing them. This option prepends PREFIX to the names of
programs to install in BINDIR (see above). For example, specifying
- '--program-prefix=foo-' would result in 'gcc' being installed as
- '/usr/local/bin/foo-gcc'.
+ `--program-prefix=foo-' would result in `gcc' being installed as
+ `/usr/local/bin/foo-gcc'.
-'--program-suffix=SUFFIX'
+`--program-suffix=SUFFIX'
Appends SUFFIX to the names of programs to install in BINDIR (see
- above). For example, specifying '--program-suffix=-3.1' would
- result in 'gcc' being installed as '/usr/local/bin/gcc-3.1'.
+ above). For example, specifying `--program-suffix=-3.1' would
+ result in `gcc' being installed as `/usr/local/bin/gcc-3.1'.
-'--program-transform-name=PATTERN'
- Applies the 'sed' script PATTERN to be applied to the names of
+`--program-transform-name=PATTERN'
+ Applies the `sed' script PATTERN to be applied to the names of
programs to install in BINDIR (see above). PATTERN has to consist
- of one or more basic 'sed' editing commands, separated by
- semicolons. For example, if you want the 'gcc' program name to be
- transformed to the installed program '/usr/local/bin/myowngcc' and
- the 'g++' program name to be transformed to
- '/usr/local/bin/gspecial++' without changing other program names,
+ of one or more basic `sed' editing commands, separated by
+ semicolons. For example, if you want the `gcc' program name to be
+ transformed to the installed program `/usr/local/bin/myowngcc' and
+ the `g++' program name to be transformed to
+ `/usr/local/bin/gspecial++' without changing other program names,
you could use the pattern
- '--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/''
+ `--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/''
to achieve this effect.
All three options can be combined and used together, resulting in
more complex conversion patterns. As a basic rule, PREFIX (and
- SUFFIX) are prepended (appended) before further transformations can
- happen with a special transformation script PATTERN.
+ SUFFIX) are prepended (appended) before further transformations
+ can happen with a special transformation script PATTERN.
As currently implemented, this option only takes effect for native
builds; cross compiler binaries' names are not transformed even
@@ -639,95 +619,95 @@ option.
For native builds, some of the installed programs are also
installed with the target alias in front of their name, as in
- 'i686-pc-linux-gnu-gcc'. All of the above transformations happen
+ `i686-pc-linux-gnu-gcc'. All of the above transformations happen
before the target alias is prepended to the name--so, specifying
- '--program-prefix=foo-' and 'program-suffix=-3.1', the resulting
+ `--program-prefix=foo-' and `program-suffix=-3.1', the resulting
binary would be installed as
- '/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'.
+ `/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'.
As a last shortcoming, none of the installed Ada programs are
transformed yet, which will be fixed in some time.
-'--with-local-prefix=DIRNAME'
+`--with-local-prefix=DIRNAME'
Specify the installation directory for local include files. The
- default is '/usr/local'. Specify this option if you want the
- compiler to search directory 'DIRNAME/include' for locally
- installed header files _instead_ of '/usr/local/include'.
+ default is `/usr/local'. Specify this option if you want the
+ compiler to search directory `DIRNAME/include' for locally
+ installed header files _instead_ of `/usr/local/include'.
- You should specify '--with-local-prefix' *only* if your site has a
- different convention (not '/usr/local') for where to put
+ You should specify `--with-local-prefix' *only* if your site has a
+ different convention (not `/usr/local') for where to put
site-specific files.
- The default value for '--with-local-prefix' is '/usr/local'
- regardless of the value of '--prefix'. Specifying '--prefix' has
+ The default value for `--with-local-prefix' is `/usr/local'
+ regardless of the value of `--prefix'. Specifying `--prefix' has
no effect on which directory GCC searches for local header files.
This may seem counterintuitive, but actually it is logical.
- The purpose of '--prefix' is to specify where to _install GCC_. The
- local header files in '/usr/local/include'--if you put any in that
- directory--are not part of GCC. They are part of other
+ The purpose of `--prefix' is to specify where to _install GCC_.
+ The local header files in `/usr/local/include'--if you put any in
+ that directory--are not part of GCC. They are part of other
programs--perhaps many others. (GCC installs its own header files
- in another directory which is based on the '--prefix' value.)
+ in another directory which is based on the `--prefix' value.)
Both the local-prefix include directory and the GCC-prefix include
- directory are part of GCC's "system include" directories. Although
- these two directories are not fixed, they need to be searched in
- the proper order for the correct processing of the include_next
- directive. The local-prefix include directory is searched before
- the GCC-prefix include directory. Another characteristic of system
- include directories is that pedantic warnings are turned off for
- headers in these directories.
-
- Some autoconf macros add '-I DIRECTORY' options to the compiler
+ directory are part of GCC's "system include" directories.
+ Although these two directories are not fixed, they need to be
+ searched in the proper order for the correct processing of the
+ include_next directive. The local-prefix include directory is
+ searched before the GCC-prefix include directory. Another
+ characteristic of system include directories is that pedantic
+ warnings are turned off for headers in these directories.
+
+ Some autoconf macros add `-I DIRECTORY' options to the compiler
command line, to ensure that directories containing installed
packages' headers are searched. When DIRECTORY is one of GCC's
system include directories, GCC will ignore the option so that
system directories continue to be processed in the correct order.
- This may result in a search order different from what was specified
- but the directory will still be searched.
+ This may result in a search order different from what was
+ specified but the directory will still be searched.
GCC automatically searches for ordinary libraries using
- 'GCC_EXEC_PREFIX'. Thus, when the same installation prefix is used
- for both GCC and packages, GCC will automatically search for both
- headers and libraries. This provides a configuration that is easy
- to use. GCC behaves in a manner similar to that when it is
- installed as a system compiler in '/usr'.
+ `GCC_EXEC_PREFIX'. Thus, when the same installation prefix is
+ used for both GCC and packages, GCC will automatically search for
+ both headers and libraries. This provides a configuration that is
+ easy to use. GCC behaves in a manner similar to that when it is
+ installed as a system compiler in `/usr'.
Sites that need to install multiple versions of GCC may not want to
use the above simple configuration. It is possible to use the
- '--program-prefix', '--program-suffix' and
- '--program-transform-name' options to install multiple versions
+ `--program-prefix', `--program-suffix' and
+ `--program-transform-name' options to install multiple versions
into a single directory, but it may be simpler to use different
- prefixes and the '--with-local-prefix' option to specify the
- location of the site-specific files for each version. It will then
- be necessary for users to specify explicitly the location of local
- site libraries (e.g., with 'LIBRARY_PATH').
+ prefixes and the `--with-local-prefix' option to specify the
+ location of the site-specific files for each version. It will
+ then be necessary for users to specify explicitly the location of
+ local site libraries (e.g., with `LIBRARY_PATH').
- The same value can be used for both '--with-local-prefix' and
- '--prefix' provided it is not '/usr'. This can be used to avoid
- the default search of '/usr/local/include'.
+ The same value can be used for both `--with-local-prefix' and
+ `--prefix' provided it is not `/usr'. This can be used to avoid
+ the default search of `/usr/local/include'.
- *Do not* specify '/usr' as the '--with-local-prefix'! The
- directory you use for '--with-local-prefix' *must not* contain any
+ *Do not* specify `/usr' as the `--with-local-prefix'! The
+ directory you use for `--with-local-prefix' *must not* contain any
of the system's standard header files. If it did contain them,
certain programs would be miscompiled (including GNU Emacs, on
certain targets), because this would override and nullify the
- header file corrections made by the 'fixincludes' script.
+ header file corrections made by the `fixincludes' script.
Indications are that people who use this option use it based on
- mistaken ideas of what it is for. People use it as if it specified
- where to install part of GCC. Perhaps they make this assumption
- because installing GCC creates the directory.
+ mistaken ideas of what it is for. People use it as if it
+ specified where to install part of GCC. Perhaps they make this
+ assumption because installing GCC creates the directory.
-'--with-native-system-header-dir=DIRNAME'
+`--with-native-system-header-dir=DIRNAME'
Specifies that DIRNAME is the directory that contains native system
- header files, rather than '/usr/include'. This option is most
+ header files, rather than `/usr/include'. This option is most
useful if you are creating a compiler that should be isolated from
the system as much as possible. It is most commonly used with the
- '--with-sysroot' option and will cause GCC to search DIRNAME inside
- the system root specified by that option.
+ `--with-sysroot' option and will cause GCC to search DIRNAME
+ inside the system root specified by that option.
-'--enable-shared[=PACKAGE[,...]]'
+`--enable-shared[=PACKAGE[,...]]'
Build shared versions of libraries, if shared libraries are
supported on the target platform. Unlike GCC 2.95.x and earlier,
shared libraries are enabled by default on all platforms that
@@ -735,19 +715,19 @@ option.
If a list of packages is given as an argument, build shared
libraries only for the listed packages. For other packages, only
- static libraries will be built. Package names currently recognized
- in the GCC tree are 'libgcc' (also known as 'gcc'), 'libstdc++'
- (not 'libstdc++-v3'), 'libffi', 'zlib', 'boehm-gc', 'ada',
- 'libada', 'libjava', 'libgo', and 'libobjc'. Note 'libiberty' does
- not support shared libraries at all.
+ static libraries will be built. Package names currently
+ recognized in the GCC tree are `libgcc' (also known as `gcc'),
+ `libstdc++' (not `libstdc++-v3'), `libffi', `zlib', `boehm-gc',
+ `ada', `libada', `libjava', `libgo', and `libobjc'. Note
+ `libiberty' does not support shared libraries at all.
- Use '--disable-shared' to build only static libraries. Note that
- '--disable-shared' does not accept a list of package names as
- argument, only '--enable-shared' does.
+ Use `--disable-shared' to build only static libraries. Note that
+ `--disable-shared' does not accept a list of package names as
+ argument, only `--enable-shared' does.
- Contrast with '--enable-host-shared', which affects _host_ code.
+ Contrast with `--enable-host-shared', which affects _host_ code.
-'--enable-host-shared'
+`--enable-host-shared'
Specify that the _host_ code should be built into
position-independent machine code (with -fPIC), allowing it to be
used within shared libraries, but yielding a slightly slower
@@ -755,165 +735,170 @@ option.
This option is required when building the libgccjit.so library.
- Contrast with '--enable-shared', which affects _target_ libraries.
+ Contrast with `--enable-shared', which affects _target_ libraries.
-'--with-gnu-as'
- Specify that the compiler should assume that the assembler it finds
- is the GNU assembler. However, this does not modify the rules to
- find an assembler and will result in confusion if the assembler
- found is not actually the GNU assembler. (Confusion may also
- result if the compiler finds the GNU assembler but has not been
- configured with '--with-gnu-as'.) If you have more than one
- assembler installed on your system, you may want to use this option
- in connection with '--with-as=PATHNAME' or
- '--with-build-time-tools=PATHNAME'.
+`--with-gnu-as'
+ Specify that the compiler should assume that the assembler it
+ finds is the GNU assembler. However, this does not modify the
+ rules to find an assembler and will result in confusion if the
+ assembler found is not actually the GNU assembler. (Confusion may
+ also result if the compiler finds the GNU assembler but has not
+ been configured with `--with-gnu-as'.) If you have more than one
+ assembler installed on your system, you may want to use this
+ option in connection with `--with-as=PATHNAME' or
+ `--with-build-time-tools=PATHNAME'.
The following systems are the only ones where it makes a difference
whether you use the GNU assembler. On any other system,
- '--with-gnu-as' has no effect.
+ `--with-gnu-as' has no effect.
- * 'hppa1.0-ANY-ANY'
- * 'hppa1.1-ANY-ANY'
- * 'sparc-sun-solaris2.ANY'
- * 'sparc64-ANY-solaris2.ANY'
+ * `hppa1.0-ANY-ANY'
-'--with-as=PATHNAME'
+ * `hppa1.1-ANY-ANY'
+
+ * `sparc-sun-solaris2.ANY'
+
+ * `sparc64-ANY-solaris2.ANY'
+
+`--with-as=PATHNAME'
Specify that the compiler should use the assembler pointed to by
PATHNAME, rather than the one found by the standard rules to find
an assembler, which are:
* Unless GCC is being built with a cross compiler, check the
- 'LIBEXEC/gcc/TARGET/VERSION' directory. LIBEXEC defaults to
- 'EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which
- defaults to '/usr/local' unless overridden by the
- '--prefix=PATHNAME' switch described above. TARGET is the
- target system triple, such as 'sparc-sun-solaris2.7', and
+ `LIBEXEC/gcc/TARGET/VERSION' directory. LIBEXEC defaults to
+ `EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which
+ defaults to `/usr/local' unless overridden by the
+ `--prefix=PATHNAME' switch described above. TARGET is the
+ target system triple, such as `sparc-sun-solaris2.7', and
VERSION denotes the GCC version, such as 3.0.
* If the target system is the same that you are building on,
check operating system specific directories (e.g.
- '/usr/ccs/bin' on Sun Solaris 2).
+ `/usr/ccs/bin' on Sun Solaris 2).
- * Check in the 'PATH' for a tool whose name is prefixed by the
+ * Check in the `PATH' for a tool whose name is prefixed by the
target system triple.
- * Check in the 'PATH' for a tool whose name is not prefixed by
- the target system triple, if the host and target system triple
- are the same (in other words, we use a host tool if it can be
- used for the target as well).
+ * Check in the `PATH' for a tool whose name is not prefixed by
+ the target system triple, if the host and target system
+ triple are the same (in other words, we use a host tool if it
+ can be used for the target as well).
- You may want to use '--with-as' if no assembler is installed in the
- directories listed above, or if you have multiple assemblers
+ You may want to use `--with-as' if no assembler is installed in
+ the directories listed above, or if you have multiple assemblers
installed and want to choose one that is not found by the above
rules.
-'--with-gnu-ld'
- Same as '--with-gnu-as' but for the linker.
+`--with-gnu-ld'
+ Same as `--with-gnu-as' but for the linker.
-'--with-ld=PATHNAME'
- Same as '--with-as' but for the linker.
+`--with-ld=PATHNAME'
+ Same as `--with-as' but for the linker.
-'--with-stabs'
+`--with-stabs'
Specify that stabs debugging information should be used instead of
- whatever format the host normally uses. Normally GCC uses the same
- debug format as the host system.
+ whatever format the host normally uses. Normally GCC uses the
+ same debug format as the host system.
On MIPS based systems and on Alphas, you must specify whether you
want GCC to create the normal ECOFF debugging format, or to use
BSD-style stabs passed through the ECOFF symbol table. The normal
- ECOFF debug format cannot fully handle languages other than C. BSD
- stabs format can handle other languages, but it only works with the
- GNU debugger GDB.
+ ECOFF debug format cannot fully handle languages other than C.
+ BSD stabs format can handle other languages, but it only works
+ with the GNU debugger GDB.
Normally, GCC uses the ECOFF debugging format by default; if you
- prefer BSD stabs, specify '--with-stabs' when you configure GCC.
+ prefer BSD stabs, specify `--with-stabs' when you configure GCC.
No matter which default you choose when you configure GCC, the user
- can use the '-gcoff' and '-gstabs+' options to specify explicitly
+ can use the `-gcoff' and `-gstabs+' options to specify explicitly
the debug format for a particular compilation.
- '--with-stabs' is meaningful on the ISC system on the 386, also, if
- '--with-gas' is used. It selects use of stabs debugging
+ `--with-stabs' is meaningful on the ISC system on the 386, also, if
+ `--with-gas' is used. It selects use of stabs debugging
information embedded in COFF output. This kind of debugging
information supports C++ well; ordinary COFF debugging information
does not.
- '--with-stabs' is also meaningful on 386 systems running SVR4. It
+ `--with-stabs' is also meaningful on 386 systems running SVR4. It
selects use of stabs debugging information embedded in ELF output.
The C++ compiler currently (2.6.0) does not support the DWARF
debugging information normally used on 386 SVR4 platforms; stabs
provide a workable alternative. This requires gas and gdb, as the
normal SVR4 tools can not generate or interpret stabs.
-'--with-tls=DIALECT'
+`--with-tls=DIALECT'
Specify the default TLS dialect, for systems were there is a
- choice. For ARM targets, possible values for DIALECT are 'gnu' or
- 'gnu2', which select between the original GNU dialect and the GNU
+ choice. For ARM targets, possible values for DIALECT are `gnu' or
+ `gnu2', which select between the original GNU dialect and the GNU
TLS descriptor-based dialect.
-'--enable-multiarch'
+`--enable-multiarch'
Specify whether to enable or disable multiarch support. The
default is to check for glibc start files in a multiarch location,
and enable it if the files are found. The auto detection is
enabled for native builds, and for cross builds configured with
- '--with-sysroot', and without '--with-native-system-header-dir'.
+ `--with-sysroot', and without `--with-native-system-header-dir'.
More documentation about multiarch can be found at
- <http://wiki.debian.org/Multiarch>.
+ `http://wiki.debian.org/Multiarch'.
-'--enable-vtable-verify'
+`--enable-vtable-verify'
Specify whether to enable or disable the vtable verification
feature. Enabling this feature causes libstdc++ to be built with
- its virtual calls in verifiable mode. This means that, when linked
- with libvtv, every virtual call in libstdc++ will verify the vtable
- pointer through which the call will be made before actually making
- the call. If not linked with libvtv, the verifier will call stub
- functions (in libstdc++ itself) and do nothing. If vtable
- verification is disabled, then libstdc++ is not built with its
- virtual calls in verifiable mode at all. However the libvtv
- library will still be built (see '--disable-libvtv' to turn off
- building libvtv). '--disable-vtable-verify' is the default.
-
-'--disable-multilib'
+ its virtual calls in verifiable mode. This means that, when
+ linked with libvtv, every virtual call in libstdc++ will verify
+ the vtable pointer through which the call will be made before
+ actually making the call. If not linked with libvtv, the verifier
+ will call stub functions (in libstdc++ itself) and do nothing. If
+ vtable verification is disabled, then libstdc++ is not built with
+ its virtual calls in verifiable mode at all. However the libvtv
+ library will still be built (see `--disable-libvtv' to turn off
+ building libvtv). `--disable-vtable-verify' is the default.
+
+`--disable-multilib'
Specify that multiple target libraries to support different target
variants, calling conventions, etc. should not be built. The
default is to build a predefined set of them.
- Some targets provide finer-grained control over which multilibs are
- built (e.g., '--disable-softfloat'):
- 'arm-*-*'
+ Some targets provide finer-grained control over which multilibs
+ are built (e.g., `--disable-softfloat'):
+ `arm-*-*'
fpu, 26bit, underscore, interwork, biendian, nofmult.
- 'm68*-*-*'
+ `m68*-*-*'
softfloat, m68881, m68000, m68020.
- 'mips*-*-*'
+ `mips*-*-*'
single-float, biendian, softfloat.
- 'powerpc*-*-*, rs6000*-*-*'
+ `powerpc*-*-*, rs6000*-*-*'
aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos,
biendian, sysv, aix.
-'--with-multilib-list=LIST'
-'--without-multilib-list'
+
+`--with-multilib-list=LIST'
+`--without-multilib-list'
Specify what multilibs to build. Currently only implemented for
sh*-*-* and x86-64-*-linux*.
- 'sh*-*-*'
- LIST is a comma separated list of CPU names. These must be of
- the form 'sh*' or 'm*' (in which case they match the compiler
- option for that processor). The list should not contain any
- endian options - these are handled by '--with-endian'.
+ `sh*-*-*'
+ LIST is a comma separated list of CPU names. These must be
+ of the form `sh*' or `m*' (in which case they match the
+ compiler option for that processor). The list should not
+ contain any endian options - these are handled by
+ `--with-endian'.
If LIST is empty, then there will be no multilibs for extra
processors. The multilib for the secondary endian remains
enabled.
- As a special case, if an entry in the list starts with a '!'
+ As a special case, if an entry in the list starts with a `!'
(exclamation point), then it is added to the list of excluded
multilibs. Entries of this sort should be compatible with
- 'MULTILIB_EXCLUDES' (once the leading '!' has been stripped).
+ `MULTILIB_EXCLUDES' (once the leading `!' has been stripped).
- If '--with-multilib-list' is not given, then a default set of
- multilibs is selected based on the value of '--target'. This
+ If `--with-multilib-list' is not given, then a default set of
+ multilibs is selected based on the value of `--target'. This
is usually the complete set of libraries, but some targets
imply a more specialized subset.
@@ -926,33 +911,36 @@ option.
--with-cpu=sh4a --with-endian=little,big \
--with-multilib-list=sh4al,!mb/m4al
- 'x86-64-*-linux*'
- LIST is a comma separated list of 'm32', 'm64' and 'mx32' to
+ `x86-64-*-linux*'
+ LIST is a comma separated list of `m32', `m64' and `mx32' to
enable 32-bit, 64-bit and x32 run-time libraries,
respectively. If LIST is empty, then there will be no
multilibs and only the default run-time library will be
enabled.
- If '--with-multilib-list' is not given, then only 32-bit and
+ If `--with-multilib-list' is not given, then only 32-bit and
64-bit run-time libraries will be enabled.
-'--with-endian=ENDIANS'
+`--with-endian=ENDIANS'
Specify what endians to use. Currently only implemented for
sh*-*-*.
ENDIANS may be one of the following:
- 'big'
+ `big'
Use big endian exclusively.
- 'little'
+
+ `little'
Use little endian exclusively.
- 'big,little'
+
+ `big,little'
Use big endian by default. Provide a multilib for little
endian.
- 'little,big'
+
+ `little,big'
Use little endian by default. Provide a multilib for big
endian.
-'--enable-threads'
+`--enable-threads'
Specify that the target supports threads. This affects the
Objective-C compiler and runtime library, and exception handling
for other languages like C++ and Java. On some systems, this is
@@ -962,229 +950,243 @@ option.
model available will be configured for use. Beware that on some
systems, GCC has not been taught what threading models are
generally available for the system. In this case,
- '--enable-threads' is an alias for '--enable-threads=single'.
+ `--enable-threads' is an alias for `--enable-threads=single'.
-'--disable-threads'
+`--disable-threads'
Specify that threading support should be disabled for the system.
- This is an alias for '--enable-threads=single'.
+ This is an alias for `--enable-threads=single'.
-'--enable-threads=LIB'
+`--enable-threads=LIB'
Specify that LIB is the thread support library. This affects the
Objective-C compiler and runtime library, and exception handling
for other languages like C++ and Java. The possibilities for LIB
are:
- 'aix'
+ `aix'
AIX thread support.
- 'dce'
+
+ `dce'
DCE thread support.
- 'lynx'
+
+ `lynx'
LynxOS thread support.
- 'mipssde'
+
+ `mipssde'
MIPS SDE thread support.
- 'no'
- This is an alias for 'single'.
- 'posix'
+
+ `no'
+ This is an alias for `single'.
+
+ `posix'
Generic POSIX/Unix98 thread support.
- 'rtems'
+
+ `rtems'
RTEMS thread support.
- 'single'
+
+ `single'
Disable thread support, should work for all platforms.
- 'tpf'
+
+ `tpf'
TPF thread support.
- 'vxworks'
+
+ `vxworks'
VxWorks thread support.
- 'win32'
+
+ `win32'
Microsoft Win32 API thread support.
-'--enable-tls'
+`--enable-tls'
Specify that the target supports TLS (Thread Local Storage).
Usually configure can correctly determine if TLS is supported. In
cases where it guesses incorrectly, TLS can be explicitly enabled
- or disabled with '--enable-tls' or '--disable-tls'. This can
- happen if the assembler supports TLS but the C library does not, or
- if the assumptions made by the configure test are incorrect.
+ or disabled with `--enable-tls' or `--disable-tls'. This can
+ happen if the assembler supports TLS but the C library does not,
+ or if the assumptions made by the configure test are incorrect.
-'--disable-tls'
- Specify that the target does not support TLS. This is an alias for
- '--enable-tls=no'.
+`--disable-tls'
+ Specify that the target does not support TLS. This is an alias
+ for `--enable-tls=no'.
-'--with-cpu=CPU'
-'--with-cpu-32=CPU'
-'--with-cpu-64=CPU'
+`--with-cpu=CPU'
+`--with-cpu-32=CPU'
+`--with-cpu-64=CPU'
Specify which cpu variant the compiler should generate code for by
- default. CPU will be used as the default value of the '-mcpu='
+ default. CPU will be used as the default value of the `-mcpu='
switch. This option is only supported on some targets, including
- ARC, ARM, i386, M68k, PowerPC, and SPARC. It is mandatory for ARC.
- The '--with-cpu-32' and '--with-cpu-64' options specify separate
- default CPUs for 32-bit and 64-bit modes; these options are only
- supported for i386, x86-64 and PowerPC.
-
-'--with-schedule=CPU'
-'--with-arch=CPU'
-'--with-arch-32=CPU'
-'--with-arch-64=CPU'
-'--with-tune=CPU'
-'--with-tune-32=CPU'
-'--with-tune-64=CPU'
-'--with-abi=ABI'
-'--with-fpu=TYPE'
-'--with-float=TYPE'
+ ARC, ARM, i386, M68k, PowerPC, and SPARC. It is mandatory for
+ ARC. The `--with-cpu-32' and `--with-cpu-64' options specify
+ separate default CPUs for 32-bit and 64-bit modes; these options
+ are only supported for i386, x86-64 and PowerPC.
+
+`--with-schedule=CPU'
+`--with-arch=CPU'
+`--with-arch-32=CPU'
+`--with-arch-64=CPU'
+`--with-tune=CPU'
+`--with-tune-32=CPU'
+`--with-tune-64=CPU'
+`--with-abi=ABI'
+`--with-fpu=TYPE'
+`--with-float=TYPE'
These configure options provide default values for the
- '-mschedule=', '-march=', '-mtune=', '-mabi=', and '-mfpu=' options
- and for '-mhard-float' or '-msoft-float'. As with '--with-cpu',
- which switches will be accepted and acceptable values of the
- arguments depend on the target.
+ `-mschedule=', `-march=', `-mtune=', `-mabi=', and `-mfpu='
+ options and for `-mhard-float' or `-msoft-float'. As with
+ `--with-cpu', which switches will be accepted and acceptable values
+ of the arguments depend on the target.
-'--with-mode=MODE'
- Specify if the compiler should default to '-marm' or '-mthumb'.
+`--with-mode=MODE'
+ Specify if the compiler should default to `-marm' or `-mthumb'.
This option is only supported on ARM targets.
-'--with-stack-offset=NUM'
- This option sets the default for the -mstack-offset=NUM option, and
- will thus generally also control the setting of this option for
+`--with-stack-offset=NUM'
+ This option sets the default for the -mstack-offset=NUM option,
+ and will thus generally also control the setting of this option for
libraries. This option is only supported on Epiphany targets.
-'--with-fpmath=ISA'
- This options sets '-mfpmath=sse' by default and specifies the
+`--with-fpmath=ISA'
+ This options sets `-mfpmath=sse' by default and specifies the
default ISA for floating-point arithmetics. You can select either
- 'sse' which enables '-msse2' or 'avx' which enables '-mavx' by
+ `sse' which enables `-msse2' or `avx' which enables `-mavx' by
default. This option is only supported on i386 and x86-64 targets.
-'--with-fp-32=MODE'
- On MIPS targets, set the default value for the '-mfp' option when
- using the o32 ABI. The possibilities for MODE are:
- '32'
- Use the o32 FP32 ABI extension, as with the '-mfp32'
+`--with-fp-32=MODE'
+ On MIPS targets, set the default value for the `-mfp' option when
+ using the o32 ABI. The possibilities for MODE are:
+ `32'
+ Use the o32 FP32 ABI extension, as with the `-mfp32'
command-line option.
- 'xx'
- Use the o32 FPXX ABI extension, as with the '-mfpxx'
+
+ `xx'
+ Use the o32 FPXX ABI extension, as with the `-mfpxx'
command-line option.
- '64'
- Use the o32 FP64 ABI extension, as with the '-mfp64'
+
+ `64'
+ Use the o32 FP64 ABI extension, as with the `-mfp64'
command-line option.
In the absence of this configuration option the default is to use
the o32 FP32 ABI extension.
-'--with-odd-spreg-32'
- On MIPS targets, set the '-modd-spreg' option by default when using
+`--with-odd-spreg-32'
+ On MIPS targets, set the `-modd-spreg' option by default when using
the o32 ABI.
-'--without-odd-spreg-32'
- On MIPS targets, set the '-mno-odd-spreg' option by default when
- using the o32 ABI. This is normally used in conjunction with
- '--with-fp-32=64' in order to target the o32 FP64A ABI extension.
+`--without-odd-spreg-32'
+ On MIPS targets, set the `-mno-odd-spreg' option by default when
+ using the o32 ABI. This is normally used in conjunction with
+ `--with-fp-32=64' in order to target the o32 FP64A ABI extension.
-'--with-nan=ENCODING'
+`--with-nan=ENCODING'
On MIPS targets, set the default encoding convention to use for the
special not-a-number (NaN) IEEE 754 floating-point data. The
possibilities for ENCODING are:
- 'legacy'
- Use the legacy encoding, as with the '-mnan=legacy'
+ `legacy'
+ Use the legacy encoding, as with the `-mnan=legacy'
command-line option.
- '2008'
- Use the 754-2008 encoding, as with the '-mnan=2008'
+
+ `2008'
+ Use the 754-2008 encoding, as with the `-mnan=2008'
command-line option.
To use this configuration option you must have an assembler version
- installed that supports the '-mnan=' command-line option too. In
+ installed that supports the `-mnan=' command-line option too. In
the absence of this configuration option the default convention is
- the legacy encoding, as when neither of the '-mnan=2008' and
- '-mnan=legacy' command-line options has been used.
+ the legacy encoding, as when neither of the `-mnan=2008' and
+ `-mnan=legacy' command-line options has been used.
-'--with-divide=TYPE'
+`--with-divide=TYPE'
Specify how the compiler should generate code for checking for
division by zero. This option is only supported on the MIPS
target. The possibilities for TYPE are:
- 'traps'
+ `traps'
Division by zero checks use conditional traps (this is the
default on systems that support conditional traps).
- 'breaks'
+
+ `breaks'
Division by zero checks use the break instruction.
-'--with-llsc'
- On MIPS targets, make '-mllsc' the default when no '-mno-llsc'
+`--with-llsc'
+ On MIPS targets, make `-mllsc' the default when no `-mno-llsc'
option is passed. This is the default for Linux-based targets, as
the kernel will emulate them if the ISA does not provide them.
-'--without-llsc'
- On MIPS targets, make '-mno-llsc' the default when no '-mllsc'
+`--without-llsc'
+ On MIPS targets, make `-mno-llsc' the default when no `-mllsc'
option is passed.
-'--with-synci'
- On MIPS targets, make '-msynci' the default when no '-mno-synci'
+`--with-synci'
+ On MIPS targets, make `-msynci' the default when no `-mno-synci'
option is passed.
-'--without-synci'
- On MIPS targets, make '-mno-synci' the default when no '-msynci'
+`--without-synci'
+ On MIPS targets, make `-mno-synci' the default when no `-msynci'
option is passed. This is the default.
-'--with-mips-plt'
+`--with-mips-plt'
On MIPS targets, make use of copy relocations and PLTs. These
- features are extensions to the traditional SVR4-based MIPS ABIs and
- require support from GNU binutils and the runtime C library.
+ features are extensions to the traditional SVR4-based MIPS ABIs
+ and require support from GNU binutils and the runtime C library.
-'--enable-__cxa_atexit'
+`--enable-__cxa_atexit'
Define if you want to use __cxa_atexit, rather than atexit, to
register C++ destructors for local statics and global objects.
This is essential for fully standards-compliant handling of
destructors, but requires __cxa_atexit in libc. This option is
currently only available on systems with GNU libc. When enabled,
- this will cause '-fuse-cxa-atexit' to be passed by default.
+ this will cause `-fuse-cxa-atexit' to be passed by default.
-'--enable-gnu-indirect-function'
- Define if you want to enable the 'ifunc' attribute. This option is
+`--enable-gnu-indirect-function'
+ Define if you want to enable the `ifunc' attribute. This option is
currently only available on systems with GNU libc on certain
targets.
-'--enable-target-optspace'
+`--enable-target-optspace'
Specify that target libraries should be optimized for code space
instead of code speed. This is the default for the m32r platform.
-'--with-cpp-install-dir=DIRNAME'
- Specify that the user visible 'cpp' program should be installed in
- 'PREFIX/DIRNAME/cpp', in addition to BINDIR.
+`--with-cpp-install-dir=DIRNAME'
+ Specify that the user visible `cpp' program should be installed in
+ `PREFIX/DIRNAME/cpp', in addition to BINDIR.
-'--enable-comdat'
+`--enable-comdat'
Enable COMDAT group support. This is primarily used to override
the automatically detected value.
-'--enable-initfini-array'
- Force the use of sections '.init_array' and '.fini_array' (instead
- of '.init' and '.fini') for constructors and destructors. Option
- '--disable-initfini-array' has the opposite effect. If neither
- option is specified, the configure script will try to guess whether
- the '.init_array' and '.fini_array' sections are supported and, if
- they are, use them.
+`--enable-initfini-array'
+ Force the use of sections `.init_array' and `.fini_array' (instead
+ of `.init' and `.fini') for constructors and destructors. Option
+ `--disable-initfini-array' has the opposite effect. If neither
+ option is specified, the configure script will try to guess
+ whether the `.init_array' and `.fini_array' sections are supported
+ and, if they are, use them.
-'--enable-link-mutex'
+`--enable-link-mutex'
When building GCC, use a mutex to avoid linking the compilers for
multiple languages at the same time, to avoid thrashing on build
- systems with limited free memory. The default is not to use such a
- mutex.
+ systems with limited free memory. The default is not to use such
+ a mutex.
-'--enable-maintainer-mode'
+`--enable-maintainer-mode'
The build rules that regenerate the Autoconf and Automake output
- files as well as the GCC master message catalog 'gcc.pot' are
+ files as well as the GCC master message catalog `gcc.pot' are
normally disabled. This is because it can only be rebuilt if the
complete source tree is present. If you have changed the sources
and want to rebuild the catalog, configuring with
- '--enable-maintainer-mode' will enable this. Note that you need a
- recent version of the 'gettext' tools to do so.
+ `--enable-maintainer-mode' will enable this. Note that you need a
+ recent version of the `gettext' tools to do so.
-'--disable-bootstrap'
+`--disable-bootstrap'
For a native build, the default configuration is to perform a
- 3-stage bootstrap of the compiler when 'make' is invoked, testing
- that GCC can compile itself correctly. If you want to disable this
- process, you can configure with '--disable-bootstrap'.
+ 3-stage bootstrap of the compiler when `make' is invoked, testing
+ that GCC can compile itself correctly. If you want to disable
+ this process, you can configure with `--disable-bootstrap'.
-'--enable-bootstrap'
+`--enable-bootstrap'
In special cases, you may want to perform a 3-stage build even if
the target and host triplets are different. This is possible when
the host can run code compiled for the target (e.g. host is
i686-linux, target is i486-linux). Starting from GCC 4.2, to do
- this you have to configure explicitly with '--enable-bootstrap'.
+ this you have to configure explicitly with `--enable-bootstrap'.
-'--enable-generated-files-in-srcdir'
+`--enable-generated-files-in-srcdir'
Neither the .c and .h files that are generated from Bison and flex
nor the info manuals and man pages that are built from the .texi
files are present in the SVN development tree. When building GCC
@@ -1192,181 +1194,203 @@ option.
generated files are placed in your build directory, which allows
for the source to be in a readonly directory.
- If you configure with '--enable-generated-files-in-srcdir' then
+ If you configure with `--enable-generated-files-in-srcdir' then
those generated files will go into the source directory. This is
mainly intended for generating release or prerelease tarballs of
the GCC sources, since it is not a requirement that the users of
source releases to have flex, Bison, or makeinfo.
-'--enable-version-specific-runtime-libs'
+`--enable-version-specific-runtime-libs'
Specify that runtime libraries should be installed in the compiler
- specific subdirectory ('LIBDIR/gcc') rather than the usual places.
- In addition, 'libstdc++''s include files will be installed into
- 'LIBDIR' unless you overruled it by using
- '--with-gxx-include-dir=DIRNAME'. Using this option is
+ specific subdirectory (`LIBDIR/gcc') rather than the usual places.
+ In addition, `libstdc++''s include files will be installed into
+ `LIBDIR' unless you overruled it by using
+ `--with-gxx-include-dir=DIRNAME'. Using this option is
particularly useful if you intend to use several versions of GCC in
- parallel. This is currently supported by 'libgfortran', 'libjava',
- 'libstdc++', and 'libobjc'.
-
-'--with-aix-soname='aix', 'svr4' or 'both''
- Traditional AIX shared library versioning (versioned 'Shared
- Object' files as members of unversioned 'Archive Library' files
- named 'lib.a') causes numerous headaches for package managers.
- However, 'Import Files' as members of 'Archive Library' files allow
- for *filename-based versioning* of shared libraries as seen on
- Linux/SVR4, where this is called the "SONAME". But as they prevent
- static linking, 'Import Files' may be used with 'Runtime Linking'
- only, where the linker does search for 'libNAME.so' before
- 'libNAME.a' library filenames with the '-lNAME' linker flag.
+ parallel. This is currently supported by `libgfortran',
+ `libjava', `libstdc++', and `libobjc'.
+
+`--with-aix-soname=`aix', `svr4' or `both''
+ Traditional AIX shared library versioning (versioned `Shared
+ Object' files as members of unversioned `Archive Library' files
+ named `lib.a') causes numerous headaches for package managers.
+ However, `Import Files' as members of `Archive Library' files
+ allow for *filename-based versioning* of shared libraries as seen
+ on Linux/SVR4, where this is called the "SONAME". But as they
+ prevent static linking, `Import Files' may be used with `Runtime
+ Linking' only, where the linker does search for `libNAME.so'
+ before `libNAME.a' library filenames with the `-lNAME' linker flag.
For detailed information please refer to the AIX ld Command
reference.
As long as shared library creation is enabled, upon:
- '--with-aix-soname=aix'
- '--with-aix-soname=both'
- A (traditional AIX) 'Shared Archive Library' file is created:
- * using the 'libNAME.a' filename scheme
- * with the 'Shared Object' file as archive member named
- 'libNAME.so.V' (except for 'libgcc_s', where the 'Shared
- Object' file is named 'shr.o' for backwards
+ `--with-aix-soname=aix'
+
+ `--with-aix-soname=both'
+ A (traditional AIX) `Shared Archive Library' file is created:
+ * using the `libNAME.a' filename scheme
+
+ * with the `Shared Object' file as archive member named
+ `libNAME.so.V' (except for `libgcc_s', where the `Shared
+ Object' file is named `shr.o' for backwards
compatibility), which
- is used for runtime loading from inside the
- 'libNAME.a' file
+ `libNAME.a' file
+
- is used for dynamic loading via
- 'dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)'
+ `dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)'
+
- is used for shared linking
- - is used for static linking, so no separate 'Static
- Archive Library' file is needed
- '--with-aix-soname=both'
- '--with-aix-soname=svr4'
- A (second) 'Shared Archive Library' file is created:
- * using the 'libNAME.so.V' filename scheme
- * with the 'Shared Object' file as archive member named
- 'shr.o', which
- - is created with the '-G linker flag'
- - has the 'F_LOADONLY' flag set
+
+ - is used for static linking, so no separate `Static
+ Archive Library' file is needed
+
+
+ `--with-aix-soname=both'
+
+ `--with-aix-soname=svr4'
+ A (second) `Shared Archive Library' file is created:
+ * using the `libNAME.so.V' filename scheme
+
+ * with the `Shared Object' file as archive member named
+ `shr.o', which
+ - is created with the `-G linker flag'
+
+ - has the `F_LOADONLY' flag set
+
- is used for runtime loading from inside the
- 'libNAME.so.V' file
+ `libNAME.so.V' file
+
- is used for dynamic loading via
- 'dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER)'
- * with the 'Import File' as archive member named 'shr.imp',
+ `dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER)'
+
+
+ * with the `Import File' as archive member named `shr.imp',
which
- - refers to 'libNAME.so.V(shr.o)' as the "SONAME", to
- be recorded in the 'Loader Section' of subsequent
- binaries
- - indicates whether 'libNAME.so.V(shr.o)' is 32 or 64
+ - refers to `libNAME.so.V(shr.o)' as the "SONAME", to
+ be recorded in the `Loader Section' of
+ subsequent binaries
+
+ - indicates whether `libNAME.so.V(shr.o)' is 32 or 64
bit
+
- lists all the public symbols exported by
- 'lib.so.V(shr.o)', eventually decorated with the
- ''weak' Keyword'
+ `lib.so.V(shr.o)', eventually decorated with the
+ ``weak' Keyword'
+
- is necessary for shared linking against
- 'lib.so.V(shr.o)'
- A symbolic link using the 'libNAME.so' filename scheme is
+ `lib.so.V(shr.o)'
+
+ A symbolic link using the `libNAME.so' filename scheme is
created:
- * pointing to the 'libNAME.so.V' 'Shared Archive Library'
+ * pointing to the `libNAME.so.V' `Shared Archive Library'
file
- * to permit the 'ld Command' to find 'lib.so.V(shr.imp)'
- via the '-lNAME' argument (requires 'Runtime Linking' to
- be enabled)
- * to permit dynamic loading of 'lib.so.V(shr.o)' without
- the need to specify the version number via
- 'dlopen("libNAME.so(shr.o)", RTLD_MEMBER)'
+
+ * to permit the `ld Command' to find `lib.so.V(shr.imp)'
+ via the `-lNAME' argument (requires `Runtime Linking'
+ to be enabled)
+
+ * to permit dynamic loading of `lib.so.V(shr.o)' without
+ the need to specify the version number via
+ `dlopen("libNAME.so(shr.o)", RTLD_MEMBER)'
As long as static library creation is enabled, upon:
- '--with-aix-soname=svr4'
- A 'Static Archive Library' is created:
- * using the 'libNAME.a' filename scheme
- * with all the 'Static Object' files as archive members,
+ `--with-aix-soname=svr4'
+ A `Static Archive Library' is created:
+ * using the `libNAME.a' filename scheme
+
+ * with all the `Static Object' files as archive members,
which
- are used for static linking
- While the aix-soname='svr4' option does not create 'Shared Object'
- files as members of unversioned 'Archive Library' files any more,
- package managers still are responsible to transfer 'Shared Object'
+
+ While the aix-soname=`svr4' option does not create `Shared Object'
+ files as members of unversioned `Archive Library' files any more,
+ package managers still are responsible to transfer `Shared Object'
files found as member of a previously installed unversioned
- 'Archive Library' file into the newly installed 'Archive Library'
+ `Archive Library' file into the newly installed `Archive Library'
file with the same filename.
- _WARNING:_ Creating 'Shared Object' files with 'Runtime Linking'
- enabled may bloat the TOC, eventually leading to 'TOC overflow'
- errors, requiring the use of either the '-Wl,-bbigtoc' linker flag
- (seen to break with the 'GDB' debugger) or some of the TOC-related
- compiler flags, *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and
- PowerPC Options.
+ _WARNING:_ Creating `Shared Object' files with `Runtime Linking'
+ enabled may bloat the TOC, eventually leading to `TOC overflow'
+ errors, requiring the use of either the `-Wl,-bbigtoc' linker flag
+ (seen to break with the `GDB' debugger) or some of the TOC-related
+ compiler flags, *Note RS/6000 and PowerPC Options: (gcc)RS/6000
+ and PowerPC Options.
- '--with-aix-soname' is currently supported by 'libgcc_s' only, so
+ `--with-aix-soname' is currently supported by `libgcc_s' only, so
this option is still experimental and not for normal use yet.
- Default is the traditional behaviour '--with-aix-soname='aix''.
+ Default is the traditional behaviour `--with-aix-soname=`aix''.
-'--enable-languages=LANG1,LANG2,...'
+`--enable-languages=LANG1,LANG2,...'
Specify that only a particular subset of compilers and their
runtime libraries should be built. For a list of valid values for
- LANGN you can issue the following command in the 'gcc' directory of
- your GCC source tree:
+ LANGN you can issue the following command in the `gcc' directory
+ of your GCC source tree:
grep language= */config-lang.in
- Currently, you can use any of the following: 'all', 'ada', 'c',
- 'c++', 'fortran', 'go', 'java', 'objc', 'obj-c++'. Building the
+ Currently, you can use any of the following: `all', `ada', `c',
+ `c++', `fortran', `go', `java', `objc', `obj-c++'. Building the
Ada compiler has special requirements, see below. If you do not
- pass this flag, or specify the option 'all', then all default
- languages available in the 'gcc' sub-tree will be configured. Ada,
- Go and Objective-C++ are not default languages; the rest are.
+ pass this flag, or specify the option `all', then all default
+ languages available in the `gcc' sub-tree will be configured.
+ Ada, Go and Objective-C++ are not default languages; the rest are.
-'--enable-stage1-languages=LANG1,LANG2,...'
+`--enable-stage1-languages=LANG1,LANG2,...'
Specify that a particular subset of compilers and their runtime
- libraries should be built with the system C compiler during stage 1
- of the bootstrap process, rather than only in later stages with the
- bootstrapped C compiler. The list of valid values is the same as
- for '--enable-languages', and the option 'all' will select all of
- the languages enabled by '--enable-languages'. This option is
+ libraries should be built with the system C compiler during stage
+ 1 of the bootstrap process, rather than only in later stages with
+ the bootstrapped C compiler. The list of valid values is the same
+ as for `--enable-languages', and the option `all' will select all
+ of the languages enabled by `--enable-languages'. This option is
primarily useful for GCC development; for instance, when a
development version of the compiler cannot bootstrap due to
- compiler bugs, or when one is debugging front ends other than the C
- front end. When this option is used, one can then build the target
- libraries for the specified languages with the stage-1 compiler by
- using 'make stage1-bubble all-target', or run the testsuite on the
- stage-1 compiler for the specified languages using 'make
- stage1-start check-gcc'.
-
-'--disable-libada'
+ compiler bugs, or when one is debugging front ends other than the
+ C front end. When this option is used, one can then build the
+ target libraries for the specified languages with the stage-1
+ compiler by using `make stage1-bubble all-target', or run the
+ testsuite on the stage-1 compiler for the specified languages
+ using `make stage1-start check-gcc'.
+
+`--disable-libada'
Specify that the run-time libraries and tools used by GNAT should
not be built. This can be useful for debugging, or for
compatibility with previous Ada build procedures, when it was
- required to explicitly do a 'make -C gcc gnatlib_and_tools'.
+ required to explicitly do a `make -C gcc gnatlib_and_tools'.
-'--disable-libsanitizer'
+`--disable-libsanitizer'
Specify that the run-time libraries for the various sanitizers
should not be built.
-'--disable-libssp'
+`--disable-libssp'
Specify that the run-time libraries for stack smashing protection
should not be built.
-'--disable-libquadmath'
+`--disable-libquadmath'
Specify that the GCC quad-precision math library should not be
built. On some systems, the library is required to be linkable
when building the Fortran front end, unless
- '--disable-libquadmath-support' is used.
+ `--disable-libquadmath-support' is used.
-'--disable-libquadmath-support'
- Specify that the Fortran front end and 'libgfortran' do not add
- support for 'libquadmath' on systems supporting it.
+`--disable-libquadmath-support'
+ Specify that the Fortran front end and `libgfortran' do not add
+ support for `libquadmath' on systems supporting it.
-'--disable-libgomp'
+`--disable-libgomp'
Specify that the GNU Offloading and Multi Processing Runtime
Library should not be built.
-'--disable-libvtv'
+`--disable-libvtv'
Specify that the run-time libraries used by vtable verification
should not be built.
-'--with-dwarf2'
+`--with-dwarf2'
Specify that the compiler should use DWARF 2 debugging information
as the default.
-'--enable-targets=all'
-'--enable-targets=TARGET_LIST'
+`--enable-targets=all'
+`--enable-targets=TARGET_LIST'
Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
These are compilers that are able to generate either 64-bit or
32-bit code. Typically, the corresponding 32-bit target, e.g.
@@ -1379,295 +1403,297 @@ option.
affects sparc-linux, powerpc-linux, x86-linux, mips-linux and
s390-linux.
-'--enable-secureplt'
- This option enables '-msecure-plt' by default for powerpc-linux.
+`--enable-secureplt'
+ This option enables `-msecure-plt' by default for powerpc-linux.
*Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC
Options,
-'--enable-cld'
- This option enables '-mcld' by default for 32-bit x86 targets.
+`--enable-cld'
+ This option enables `-mcld' by default for 32-bit x86 targets.
*Note i386 and x86-64 Options: (gcc)i386 and x86-64 Options,
-'--enable-win32-registry'
-'--enable-win32-registry=KEY'
-'--disable-win32-registry'
- The '--enable-win32-registry' option enables Microsoft
+`--enable-win32-registry'
+`--enable-win32-registry=KEY'
+`--disable-win32-registry'
+ The `--enable-win32-registry' option enables Microsoft
Windows-hosted GCC to look up installations paths in the registry
using the following key:
- HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY
+ `HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY'
KEY defaults to GCC version number, and can be overridden by the
- '--enable-win32-registry=KEY' option. Vendors and distributors who
- use custom installers are encouraged to provide a different key,
- perhaps one comprised of vendor name and GCC version number, to
- avoid conflict with existing installations. This feature is
+ `--enable-win32-registry=KEY' option. Vendors and distributors
+ who use custom installers are encouraged to provide a different
+ key, perhaps one comprised of vendor name and GCC version number,
+ to avoid conflict with existing installations. This feature is
enabled by default, and can be disabled by
- '--disable-win32-registry' option. This option has no effect on
+ `--disable-win32-registry' option. This option has no effect on
the other hosts.
-'--nfp'
+`--nfp'
Specify that the machine does not have a floating point unit. This
- option only applies to 'm68k-sun-sunosN'. On any other system,
- '--nfp' has no effect.
+ option only applies to `m68k-sun-sunosN'. On any other system,
+ `--nfp' has no effect.
-'--enable-werror'
-'--disable-werror'
-'--enable-werror=yes'
-'--enable-werror=no'
+`--enable-werror'
+`--disable-werror'
+`--enable-werror=yes'
+`--enable-werror=no'
When you specify this option, it controls whether certain files in
- the compiler are built with '-Werror' in bootstrap stage2 and
- later. If you don't specify it, '-Werror' is turned on for the
+ the compiler are built with `-Werror' in bootstrap stage2 and
+ later. If you don't specify it, `-Werror' is turned on for the
main development trunk. However it defaults to off for release
branches and final releases. The specific files which get
- '-Werror' are controlled by the Makefiles.
+ `-Werror' are controlled by the Makefiles.
-'--enable-checking'
-'--enable-checking=LIST'
+`--enable-checking'
+`--enable-checking=LIST'
When you specify this option, the compiler is built to perform
- internal consistency checks of the requested complexity. This does
- not change the generated code, but adds error checking within the
- compiler. This will slow down the compiler and may only work
- properly if you are building the compiler with GCC. This is 'yes'
- by default when building from SVN or snapshots, but 'release' for
- releases. The default for building the stage1 compiler is 'yes'.
+ internal consistency checks of the requested complexity. This
+ does not change the generated code, but adds error checking within
+ the compiler. This will slow down the compiler and may only work
+ properly if you are building the compiler with GCC. This is `yes'
+ by default when building from SVN or snapshots, but `release' for
+ releases. The default for building the stage1 compiler is `yes'.
More control over the checks may be had by specifying LIST. The
- categories of checks available are 'yes' (most common checks
- 'assert,misc,tree,gc,rtlflag,runtime'), 'no' (no checks at all),
- 'all' (all but 'valgrind'), 'release' (cheapest checks
- 'assert,runtime') or 'none' (same as 'no'). Individual checks can
- be enabled with these flags 'assert', 'df', 'fold', 'gc', 'gcac'
- 'misc', 'rtl', 'rtlflag', 'runtime', 'tree', and 'valgrind'.
-
- The 'valgrind' check requires the external 'valgrind' simulator,
- available from <http://valgrind.org/>. The 'df', 'rtl', 'gcac' and
- 'valgrind' checks are very expensive. To disable all checking,
- '--disable-checking' or '--enable-checking=none' must be explicitly
- requested. Disabling assertions will make the compiler and runtime
- slightly faster but increase the risk of undetected internal errors
- causing wrong code to be generated.
-
-'--disable-stage1-checking'
-'--enable-stage1-checking'
-'--enable-stage1-checking=LIST'
- If no '--enable-checking' option is specified the stage1 compiler
- will be built with 'yes' checking enabled, otherwise the stage1
- checking flags are the same as specified by '--enable-checking'.
+ categories of checks available are `yes' (most common checks
+ `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at all),
+ `all' (all but `valgrind'), `release' (cheapest checks
+ `assert,runtime') or `none' (same as `no'). Individual checks can
+ be enabled with these flags `assert', `df', `fold', `gc', `gcac'
+ `misc', `rtl', `rtlflag', `runtime', `tree', and `valgrind'.
+
+ The `valgrind' check requires the external `valgrind' simulator,
+ available from `http://valgrind.org/'. The `df', `rtl', `gcac'
+ and `valgrind' checks are very expensive. To disable all
+ checking, `--disable-checking' or `--enable-checking=none' must be
+ explicitly requested. Disabling assertions will make the compiler
+ and runtime slightly faster but increase the risk of undetected
+ internal errors causing wrong code to be generated.
+
+`--disable-stage1-checking'
+`--enable-stage1-checking'
+`--enable-stage1-checking=LIST'
+ If no `--enable-checking' option is specified the stage1 compiler
+ will be built with `yes' checking enabled, otherwise the stage1
+ checking flags are the same as specified by `--enable-checking'.
To build the stage1 compiler with different checking options use
- '--enable-stage1-checking'. The list of checking options is the
- same as for '--enable-checking'. If your system is too slow or too
- small to bootstrap a released compiler with checking for stage1
- enabled, you can use '--disable-stage1-checking' to disable
+ `--enable-stage1-checking'. The list of checking options is the
+ same as for `--enable-checking'. If your system is too slow or
+ too small to bootstrap a released compiler with checking for
+ stage1 enabled, you can use `--disable-stage1-checking' to disable
checking for the stage1 compiler.
-'--enable-coverage'
-'--enable-coverage=LEVEL'
+`--enable-coverage'
+`--enable-coverage=LEVEL'
With this option, the compiler is built to collect self coverage
information, every time it is run. This is for internal
development purposes, and only works when the compiler is being
built with gcc. The LEVEL argument controls whether the compiler
- is built optimized or not, values are 'opt' and 'noopt'. For
- coverage analysis you want to disable optimization, for performance
- analysis you want to enable optimization. When coverage is
- enabled, the default level is without optimization.
+ is built optimized or not, values are `opt' and `noopt'. For
+ coverage analysis you want to disable optimization, for
+ performance analysis you want to enable optimization. When
+ coverage is enabled, the default level is without optimization.
-'--enable-gather-detailed-mem-stats'
+`--enable-gather-detailed-mem-stats'
When this option is specified more detailed information on memory
allocation is gathered. This information is printed when using
- '-fmem-report'.
+ `-fmem-report'.
-'--enable-nls'
-'--disable-nls'
- The '--enable-nls' option enables Native Language Support (NLS),
+`--enable-nls'
+`--disable-nls'
+ The `--enable-nls' option enables Native Language Support (NLS),
which lets GCC output diagnostics in languages other than American
English. Native Language Support is enabled by default if not
- doing a canadian cross build. The '--disable-nls' option disables
+ doing a canadian cross build. The `--disable-nls' option disables
NLS.
-'--with-included-gettext'
- If NLS is enabled, the '--with-included-gettext' option causes the
- build procedure to prefer its copy of GNU 'gettext'.
+`--with-included-gettext'
+ If NLS is enabled, the `--with-included-gettext' option causes the
+ build procedure to prefer its copy of GNU `gettext'.
-'--with-catgets'
- If NLS is enabled, and if the host lacks 'gettext' but has the
- inferior 'catgets' interface, the GCC build procedure normally
- ignores 'catgets' and instead uses GCC's copy of the GNU 'gettext'
- library. The '--with-catgets' option causes the build procedure to
- use the host's 'catgets' in this situation.
+`--with-catgets'
+ If NLS is enabled, and if the host lacks `gettext' but has the
+ inferior `catgets' interface, the GCC build procedure normally
+ ignores `catgets' and instead uses GCC's copy of the GNU `gettext'
+ library. The `--with-catgets' option causes the build procedure
+ to use the host's `catgets' in this situation.
-'--with-libiconv-prefix=DIR'
- Search for libiconv header files in 'DIR/include' and libiconv
- library files in 'DIR/lib'.
+`--with-libiconv-prefix=DIR'
+ Search for libiconv header files in `DIR/include' and libiconv
+ library files in `DIR/lib'.
-'--enable-obsolete'
+`--enable-obsolete'
Enable configuration for an obsoleted system. If you attempt to
configure GCC for a system (build, host, or target) which has been
obsoleted, and you do not specify this flag, configure will halt
with an error message.
- All support for systems which have been obsoleted in one release of
- GCC is removed entirely in the next major release, unless someone
- steps forward to maintain the port.
+ All support for systems which have been obsoleted in one release
+ of GCC is removed entirely in the next major release, unless
+ someone steps forward to maintain the port.
-'--enable-decimal-float'
-'--enable-decimal-float=yes'
-'--enable-decimal-float=no'
-'--enable-decimal-float=bid'
-'--enable-decimal-float=dpd'
-'--disable-decimal-float'
+`--enable-decimal-float'
+`--enable-decimal-float=yes'
+`--enable-decimal-float=no'
+`--enable-decimal-float=bid'
+`--enable-decimal-float=dpd'
+`--disable-decimal-float'
Enable (or disable) support for the C decimal floating point
extension that is in the IEEE 754-2008 standard. This is enabled
by default only on PowerPC, i386, and x86_64 GNU/Linux systems.
Other systems may also support it, but require the user to
specifically enable it. You can optionally control which decimal
- floating point format is used (either 'bid' or 'dpd'). The 'bid'
+ floating point format is used (either `bid' or `dpd'). The `bid'
(binary integer decimal) format is default on i386 and x86_64
- systems, and the 'dpd' (densely packed decimal) format is default
+ systems, and the `dpd' (densely packed decimal) format is default
on PowerPC systems.
-'--enable-fixed-point'
-'--disable-fixed-point'
+`--enable-fixed-point'
+`--disable-fixed-point'
Enable (or disable) support for C fixed-point arithmetic. This
option is enabled by default for some targets (such as MIPS) which
have hardware-support for fixed-point operations. On other
targets, you may enable this option manually.
-'--with-long-double-128'
- Specify if 'long double' type should be 128-bit by default on
+`--with-long-double-128'
+ Specify if `long double' type should be 128-bit by default on
selected GNU/Linux architectures. If using
- '--without-long-double-128', 'long double' will be by default
- 64-bit, the same as 'double' type. When neither of these configure
- options are used, the default will be 128-bit 'long double' when
- built against GNU C Library 2.4 and later, 64-bit 'long double'
- otherwise.
-
-'--with-gmp=PATHNAME'
-'--with-gmp-include=PATHNAME'
-'--with-gmp-lib=PATHNAME'
-'--with-mpfr=PATHNAME'
-'--with-mpfr-include=PATHNAME'
-'--with-mpfr-lib=PATHNAME'
-'--with-mpc=PATHNAME'
-'--with-mpc-include=PATHNAME'
-'--with-mpc-lib=PATHNAME'
+ `--without-long-double-128', `long double' will be by default
+ 64-bit, the same as `double' type. When neither of these
+ configure options are used, the default will be 128-bit `long
+ double' when built against GNU C Library 2.4 and later, 64-bit
+ `long double' otherwise.
+
+`--with-gmp=PATHNAME'
+`--with-gmp-include=PATHNAME'
+`--with-gmp-lib=PATHNAME'
+`--with-mpfr=PATHNAME'
+`--with-mpfr-include=PATHNAME'
+`--with-mpfr-lib=PATHNAME'
+`--with-mpc=PATHNAME'
+`--with-mpc-include=PATHNAME'
+`--with-mpc-lib=PATHNAME'
If you want to build GCC but do not have the GMP library, the MPFR
library and/or the MPC library installed in a standard location and
do not have their sources present in the GCC source tree then you
can explicitly specify the directory where they are installed
- ('--with-gmp=GMPINSTALLDIR', '--with-mpfr=MPFRINSTALLDIR',
- '--with-mpc=MPCINSTALLDIR'). The '--with-gmp=GMPINSTALLDIR' option
- is shorthand for '--with-gmp-lib=GMPINSTALLDIR/lib' and
- '--with-gmp-include=GMPINSTALLDIR/include'. Likewise the
- '--with-mpfr=MPFRINSTALLDIR' option is shorthand for
- '--with-mpfr-lib=MPFRINSTALLDIR/lib' and
- '--with-mpfr-include=MPFRINSTALLDIR/include', also the
- '--with-mpc=MPCINSTALLDIR' option is shorthand for
- '--with-mpc-lib=MPCINSTALLDIR/lib' and
- '--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand
+ (`--with-gmp=GMPINSTALLDIR', `--with-mpfr=MPFRINSTALLDIR',
+ `--with-mpc=MPCINSTALLDIR'). The `--with-gmp=GMPINSTALLDIR'
+ option is shorthand for `--with-gmp-lib=GMPINSTALLDIR/lib' and
+ `--with-gmp-include=GMPINSTALLDIR/include'. Likewise the
+ `--with-mpfr=MPFRINSTALLDIR' option is shorthand for
+ `--with-mpfr-lib=MPFRINSTALLDIR/lib' and
+ `--with-mpfr-include=MPFRINSTALLDIR/include', also the
+ `--with-mpc=MPCINSTALLDIR' option is shorthand for
+ `--with-mpc-lib=MPCINSTALLDIR/lib' and
+ `--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand
assumptions are not correct, you can use the explicit include and
lib options directly. You might also need to ensure the shared
libraries can be found by the dynamic linker when building and
using GCC, for example by setting the runtime shared library path
- variable ('LD_LIBRARY_PATH' on GNU/Linux and Solaris systems).
+ variable (`LD_LIBRARY_PATH' on GNU/Linux and Solaris systems).
These flags are applicable to the host platform only. When
building a cross compiler, they will not be used to configure
target libraries.
-'--with-isl=PATHNAME'
-'--with-isl-include=PATHNAME'
-'--with-isl-lib=PATHNAME'
- If you do not have the ISL library installed in a standard location
- and you want to build GCC, you can explicitly specify the directory
- where it is installed ('--with-isl=ISLINSTALLDIR'). The
- '--with-isl=ISLINSTALLDIR' option is shorthand for
- '--with-isl-lib=ISLINSTALLDIR/lib' and
- '--with-isl-include=ISLINSTALLDIR/include'. If this shorthand
- assumption is not correct, you can use the explicit include and lib
- options directly.
+`--with-isl=PATHNAME'
+`--with-isl-include=PATHNAME'
+`--with-isl-lib=PATHNAME'
+ If you do not have the ISL library installed in a standard
+ location and you want to build GCC, you can explicitly specify the
+ directory where it is installed (`--with-isl=ISLINSTALLDIR'). The
+ `--with-isl=ISLINSTALLDIR' option is shorthand for
+ `--with-isl-lib=ISLINSTALLDIR/lib' and
+ `--with-isl-include=ISLINSTALLDIR/include'. If this shorthand
+ assumption is not correct, you can use the explicit include and
+ lib options directly.
These flags are applicable to the host platform only. When
building a cross compiler, they will not be used to configure
target libraries.
-'--with-host-libstdcxx=LINKER-ARGS'
+`--with-host-libstdcxx=LINKER-ARGS'
If you are linking with a static copy of PPL, you can use this
option to specify how the linker should find the standard C++
- library used internally by PPL. Typical values of LINKER-ARGS might
- be '-lstdc++' or '-Wl,-Bstatic,-lstdc++,-Bdynamic -lm'. If you are
- linking with a shared copy of PPL, you probably do not need this
- option; shared library dependencies will cause the linker to search
- for the standard C++ library automatically.
+ library used internally by PPL. Typical values of LINKER-ARGS
+ might be `-lstdc++' or `-Wl,-Bstatic,-lstdc++,-Bdynamic -lm'. If
+ you are linking with a shared copy of PPL, you probably do not
+ need this option; shared library dependencies will cause the
+ linker to search for the standard C++ library automatically.
-'--with-stage1-ldflags=FLAGS'
+`--with-stage1-ldflags=FLAGS'
This option may be used to set linker flags to be used when linking
- stage 1 of GCC. These are also used when linking GCC if configured
- with '--disable-bootstrap'. By default no special flags are used.
+ stage 1 of GCC. These are also used when linking GCC if
+ configured with `--disable-bootstrap'. By default no special
+ flags are used.
-'--with-stage1-libs=LIBS'
+`--with-stage1-libs=LIBS'
This option may be used to set libraries to be used when linking
- stage 1 of GCC. These are also used when linking GCC if configured
- with '--disable-bootstrap'. The default is the argument to
- '--with-host-libstdcxx', if specified.
+ stage 1 of GCC. These are also used when linking GCC if
+ configured with `--disable-bootstrap'. The default is the
+ argument to `--with-host-libstdcxx', if specified.
-'--with-boot-ldflags=FLAGS'
+`--with-boot-ldflags=FLAGS'
This option may be used to set linker flags to be used when linking
- stage 2 and later when bootstrapping GCC. If neither
+ stage 2 and later when bootstrapping GCC. If neither
-with-boot-libs nor -with-host-libstdcxx is set to a value, then
- the default is '-static-libstdc++ -static-libgcc'.
+ the default is `-static-libstdc++ -static-libgcc'.
-'--with-boot-libs=LIBS'
+`--with-boot-libs=LIBS'
This option may be used to set libraries to be used when linking
- stage 2 and later when bootstrapping GCC. The default is the
- argument to '--with-host-libstdcxx', if specified.
-
-'--with-debug-prefix-map=MAP'
- Convert source directory names using '-fdebug-prefix-map' when
- building runtime libraries. 'MAP' is a space-separated list of
- maps of the form 'OLD=NEW'.
-
-'--enable-linker-build-id'
- Tells GCC to pass '--build-id' option to the linker for all final
- links (links performed without the '-r' or '--relocatable' option),
- if the linker supports it. If you specify
- '--enable-linker-build-id', but your linker does not support
- '--build-id' option, a warning is issued and the
- '--enable-linker-build-id' option is ignored. The default is off.
-
-'--with-linker-hash-style=CHOICE'
- Tells GCC to pass '--hash-style=CHOICE' option to the linker for
- all final links. CHOICE can be one of 'sysv', 'gnu', and 'both'
- where 'sysv' is the default.
-
-'--enable-gnu-unique-object'
-'--disable-gnu-unique-object'
+ stage 2 and later when bootstrapping GCC. The default is the
+ argument to `--with-host-libstdcxx', if specified.
+
+`--with-debug-prefix-map=MAP'
+ Convert source directory names using `-fdebug-prefix-map' when
+ building runtime libraries. `MAP' is a space-separated list of
+ maps of the form `OLD=NEW'.
+
+`--enable-linker-build-id'
+ Tells GCC to pass `--build-id' option to the linker for all final
+ links (links performed without the `-r' or `--relocatable'
+ option), if the linker supports it. If you specify
+ `--enable-linker-build-id', but your linker does not support
+ `--build-id' option, a warning is issued and the
+ `--enable-linker-build-id' option is ignored. The default is off.
+
+`--with-linker-hash-style=CHOICE'
+ Tells GCC to pass `--hash-style=CHOICE' option to the linker for
+ all final links. CHOICE can be one of `sysv', `gnu', and `both'
+ where `sysv' is the default.
+
+`--enable-gnu-unique-object'
+`--disable-gnu-unique-object'
Tells GCC to use the gnu_unique_object relocation for C++ template
static data members and inline function local statics. Enabled by
- default for a toolchain with an assembler that accepts it and GLIBC
- 2.11 or above, otherwise disabled.
-
-'--with-diagnostics-color=CHOICE'
- Tells GCC to use CHOICE as the default for '-fdiagnostics-color='
- option (if not used explicitly on the command line). CHOICE can be
- one of 'never', 'auto', 'always', and 'auto-if-env' where 'auto' is
- the default. 'auto-if-env' means that '-fdiagnostics-color=auto'
- will be the default if 'GCC_COLORS' is present and non-empty in the
- environment, and '-fdiagnostics-color=never' otherwise.
-
-'--enable-lto'
-'--disable-lto'
- Enable support for link-time optimization (LTO). This is enabled by
- default, and may be disabled using '--disable-lto'.
-
-'--enable-linker-plugin-configure-flags=FLAGS'
-'--enable-linker-plugin-flags=FLAGS'
+ default for a toolchain with an assembler that accepts it and
+ GLIBC 2.11 or above, otherwise disabled.
+
+`--with-diagnostics-color=CHOICE'
+ Tells GCC to use CHOICE as the default for `-fdiagnostics-color='
+ option (if not used explicitly on the command line). CHOICE can
+ be one of `never', `auto', `always', and `auto-if-env' where
+ `auto' is the default. `auto-if-env' means that
+ `-fdiagnostics-color=auto' will be the default if `GCC_COLORS' is
+ present and non-empty in the environment, and
+ `-fdiagnostics-color=never' otherwise.
+
+`--enable-lto'
+`--disable-lto'
+ Enable support for link-time optimization (LTO). This is enabled
+ by default, and may be disabled using `--disable-lto'.
+
+`--enable-linker-plugin-configure-flags=FLAGS'
+`--enable-linker-plugin-flags=FLAGS'
By default, linker plugins (such as the LTO plugin) are built for
the host system architecture. For the case that the linker has a
different (but run-time compatible) architecture, these flags can
be specified to build plugins that are compatible to the linker.
For example, if you are building GCC for a 64-bit x86_64
- ('x86_64-unknown-linux-gnu') host system, but have a 32-bit x86
- GNU/Linux ('i686-pc-linux-gnu') linker executable (which is
+ (`x86_64-unknown-linux-gnu') host system, but have a 32-bit x86
+ GNU/Linux (`i686-pc-linux-gnu') linker executable (which is
executable on the former system), you can configure GCC as follows
for getting compatible linker plugins:
@@ -1676,22 +1702,22 @@ option.
--enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \
--enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib'
-'--with-plugin-ld=PATHNAME'
+`--with-plugin-ld=PATHNAME'
Enable an alternate linker to be used at link-time optimization
- (LTO) link time when '-fuse-linker-plugin' is enabled. This linker
- should have plugin support such as gold starting with version 2.20
- or GNU ld starting with version 2.21. See '-fuse-linker-plugin'
- for details.
-
-'--enable-canonical-system-headers'
-'--disable-canonical-system-headers'
- Enable system header path canonicalization for 'libcpp'. This can
+ (LTO) link time when `-fuse-linker-plugin' is enabled. This
+ linker should have plugin support such as gold starting with
+ version 2.20 or GNU ld starting with version 2.21. See
+ `-fuse-linker-plugin' for details.
+
+`--enable-canonical-system-headers'
+`--disable-canonical-system-headers'
+ Enable system header path canonicalization for `libcpp'. This can
produce shorter header file paths in diagnostics and dependency
- output files, but these changed header paths may conflict with some
- compilation environments. Enabled by default, and may be disabled
- using '--disable-canonical-system-headers'.
+ output files, but these changed header paths may conflict with
+ some compilation environments. Enabled by default, and may be
+ disabled using `--disable-canonical-system-headers'.
-'--with-glibc-version=MAJOR.MINOR'
+`--with-glibc-version=MAJOR.MINOR'
Tell GCC that when the GNU C Library (glibc) is used on the target
it will be version MAJOR.MINOR or later. Normally this can be
detected from the C library's header files, but this option may be
@@ -1703,15 +1729,15 @@ option.
glibc. However, such configurations may not work well as not all
the relevant configuration in GCC is on a per-multilib basis.
-'--enable-as-accelerator-for=TARGET'
- Build as offload target compiler. Specify offload host triple by
+`--enable-as-accelerator-for=TARGET'
+ Build as offload target compiler. Specify offload host triple by
TARGET.
-'--enable-offload-targets=TARGET1[=PATH1],...,TARGETN[=PATHN]'
+`--enable-offload-targets=TARGET1[=PATH1],...,TARGETN[=PATHN]'
Enable offloading to targets TARGET1, ..., TARGETN. Offload
compilers are expected to be already installed. Default search
- path for them is 'EXEC-PREFIX', but it can be changed by specifying
- paths PATH1, ..., PATHN.
+ path for them is `EXEC-PREFIX', but it can be changed by
+ specifying paths PATH1, ..., PATHN.
% SRCDIR/configure \
--enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu
@@ -1721,363 +1747,367 @@ Cross-Compiler-Specific Options
The following options only apply to building cross compilers.
-'--with-sysroot'
-'--with-sysroot=DIR'
+`--with-sysroot'
+`--with-sysroot=DIR'
Tells GCC to consider DIR as the root of a tree that contains (a
subset of) the root filesystem of the target operating system.
Target system headers, libraries and run-time object files will be
searched for in there. More specifically, this acts as if
- '--sysroot=DIR' was added to the default options of the built
+ `--sysroot=DIR' was added to the default options of the built
compiler. The specified directory is not copied into the install
- tree, unlike the options '--with-headers' and '--with-libs' that
- this option obsoletes. The default value, in case '--with-sysroot'
- is not given an argument, is '${gcc_tooldir}/sys-root'. If the
- specified directory is a subdirectory of '${exec_prefix}', then it
- will be found relative to the GCC binaries if the installation tree
- is moved.
+ tree, unlike the options `--with-headers' and `--with-libs' that
+ this option obsoletes. The default value, in case
+ `--with-sysroot' is not given an argument, is
+ `${gcc_tooldir}/sys-root'. If the specified directory is a
+ subdirectory of `${exec_prefix}', then it will be found relative to
+ the GCC binaries if the installation tree is moved.
This option affects the system root for the compiler used to build
target libraries (which runs on the build system) and the compiler
- newly installed with 'make install'; it does not affect the
+ newly installed with `make install'; it does not affect the
compiler which is used to build GCC itself.
- If you specify the '--with-native-system-header-dir=DIRNAME' option
- then the compiler will search that directory within DIRNAME for
- native system headers rather than the default '/usr/include'.
-
-'--with-build-sysroot'
-'--with-build-sysroot=DIR'
- Tells GCC to consider DIR as the system root (see '--with-sysroot')
- while building target libraries, instead of the directory specified
- with '--with-sysroot'. This option is only useful when you are
- already using '--with-sysroot'. You can use '--with-build-sysroot'
- when you are configuring with '--prefix' set to a directory that is
- different from the one in which you are installing GCC and your
- target libraries.
+ If you specify the `--with-native-system-header-dir=DIRNAME'
+ option then the compiler will search that directory within DIRNAME
+ for native system headers rather than the default `/usr/include'.
+
+`--with-build-sysroot'
+`--with-build-sysroot=DIR'
+ Tells GCC to consider DIR as the system root (see
+ `--with-sysroot') while building target libraries, instead of the
+ directory specified with `--with-sysroot'. This option is only
+ useful when you are already using `--with-sysroot'. You can use
+ `--with-build-sysroot' when you are configuring with `--prefix'
+ set to a directory that is different from the one in which you are
+ installing GCC and your target libraries.
This option affects the system root for the compiler used to build
target libraries (which runs on the build system); it does not
affect the compiler which is used to build GCC itself.
- If you specify the '--with-native-system-header-dir=DIRNAME' option
- then the compiler will search that directory within DIRNAME for
- native system headers rather than the default '/usr/include'.
+ If you specify the `--with-native-system-header-dir=DIRNAME'
+ option then the compiler will search that directory within DIRNAME
+ for native system headers rather than the default `/usr/include'.
-'--with-headers'
-'--with-headers=DIR'
- Deprecated in favor of '--with-sysroot'. Specifies that target
+`--with-headers'
+`--with-headers=DIR'
+ Deprecated in favor of `--with-sysroot'. Specifies that target
headers are available when building a cross compiler. The DIR
argument specifies a directory which has the target include files.
- These include files will be copied into the 'gcc' install
+ These include files will be copied into the `gcc' install
directory. _This option with the DIR argument is required_ when
- building a cross compiler, if 'PREFIX/TARGET/sys-include' doesn't
- pre-exist. If 'PREFIX/TARGET/sys-include' does pre-exist, the DIR
- argument may be omitted. 'fixincludes' will be run on these files
+ building a cross compiler, if `PREFIX/TARGET/sys-include' doesn't
+ pre-exist. If `PREFIX/TARGET/sys-include' does pre-exist, the DIR
+ argument may be omitted. `fixincludes' will be run on these files
to make them compatible with GCC.
-'--without-headers'
+`--without-headers'
Tells GCC not use any target headers from a libc when building a
cross compiler. When crossing to GNU/Linux, you need the headers
so GCC can build the exception handling for libgcc.
-'--with-libs'
-'--with-libs="DIR1 DIR2 ... DIRN"'
- Deprecated in favor of '--with-sysroot'. Specifies a list of
+`--with-libs'
+`--with-libs="DIR1 DIR2 ... DIRN"'
+ Deprecated in favor of `--with-sysroot'. Specifies a list of
directories which contain the target runtime libraries. These
- libraries will be copied into the 'gcc' install directory. If the
+ libraries will be copied into the `gcc' install directory. If the
directory list is omitted, this option has no effect.
-'--with-newlib'
- Specifies that 'newlib' is being used as the target C library.
- This causes '__eprintf' to be omitted from 'libgcc.a' on the
- assumption that it will be provided by 'newlib'.
+`--with-newlib'
+ Specifies that `newlib' is being used as the target C library.
+ This causes `__eprintf' to be omitted from `libgcc.a' on the
+ assumption that it will be provided by `newlib'.
-'--with-avrlibc'
- Specifies that 'AVR-Libc' is being used as the target C library.
- This causes float support functions like '__addsf3' to be omitted
- from 'libgcc.a' on the assumption that it will be provided by
- 'libm.a'. For more technical details, cf. PR54461. This option
+`--with-avrlibc'
+ Specifies that `AVR-Libc' is being used as the target C library.
+ This causes float support functions like `__addsf3' to be omitted
+ from `libgcc.a' on the assumption that it will be provided by
+ `libm.a'. For more technical details, cf. PR54461. This option
is only supported for the AVR target. It is not supported for
RTEMS configurations, which currently use newlib. The option is
supported since version 4.7.2 and is the default in 4.8.0 and
newer.
-'--with-nds32-lib=LIBRARY'
- Specifies that LIBRARY setting is used for building 'libgcc.a'.
- Currently, the valid LIBRARY is 'newlib' or 'mculib'. This option
+`--with-nds32-lib=LIBRARY'
+ Specifies that LIBRARY setting is used for building `libgcc.a'.
+ Currently, the valid LIBRARY is `newlib' or `mculib'. This option
is only supported for the NDS32 target.
-'--with-build-time-tools=DIR'
- Specifies where to find the set of target tools (assembler, linker,
- etc.) that will be used while building GCC itself. This option
- can be useful if the directory layouts are different between the
- system you are building GCC on, and the system where you will
- deploy it.
+`--with-build-time-tools=DIR'
+ Specifies where to find the set of target tools (assembler,
+ linker, etc.) that will be used while building GCC itself. This
+ option can be useful if the directory layouts are different
+ between the system you are building GCC on, and the system where
+ you will deploy it.
- For example, on an 'ia64-hp-hpux' system, you may have the GNU
- assembler and linker in '/usr/bin', and the native tools in a
+ For example, on an `ia64-hp-hpux' system, you may have the GNU
+ assembler and linker in `/usr/bin', and the native tools in a
different path, and build a toolchain that expects to find the
- native tools in '/usr/bin'.
+ native tools in `/usr/bin'.
- When you use this option, you should ensure that DIR includes 'ar',
- 'as', 'ld', 'nm', 'ranlib' and 'strip' if necessary, and possibly
- 'objdump'. Otherwise, GCC may use an inconsistent set of tools.
+ When you use this option, you should ensure that DIR includes
+ `ar', `as', `ld', `nm', `ranlib' and `strip' if necessary, and
+ possibly `objdump'. Otherwise, GCC may use an inconsistent set of
+ tools.
Java-Specific Options
---------------------
The following option applies to the build of the Java front end.
-'--disable-libgcj'
+`--disable-libgcj'
Specify that the run-time libraries used by GCJ should not be
built. This is useful in case you intend to use GCJ with some
other run-time, or you're going to install it separately, or it
just happens not to build on your particular machine. In general,
- if the Java front end is enabled, the GCJ libraries will be enabled
- too, unless they're known to not work on the target platform. If
- GCJ is enabled but 'libgcj' isn't built, you may need to port it;
- in this case, before modifying the top-level 'configure.in' so that
- 'libgcj' is enabled by default on this platform, you may use
- '--enable-libgcj' to override the default.
+ if the Java front end is enabled, the GCJ libraries will be
+ enabled too, unless they're known to not work on the target
+ platform. If GCJ is enabled but `libgcj' isn't built, you may
+ need to port it; in this case, before modifying the top-level
+ `configure.in' so that `libgcj' is enabled by default on this
+ platform, you may use `--enable-libgcj' to override the default.
- The following options apply to building 'libgcj'.
+
+ The following options apply to building `libgcj'.
General Options
...............
-'--enable-java-maintainer-mode'
- By default the 'libjava' build will not attempt to compile the
- '.java' source files to '.class'. Instead, it will use the
- '.class' files from the source tree. If you use this option you
- must have executables named 'ecj1' and 'gjavah' in your path for
- use by the build. You must use this option if you intend to modify
- any '.java' files in 'libjava'.
-
-'--with-java-home=DIRNAME'
- This 'libjava' option overrides the default value of the
- 'java.home' system property. It is also used to set
- 'sun.boot.class.path' to 'DIRNAME/lib/rt.jar'. By default
- 'java.home' is set to 'PREFIX' and 'sun.boot.class.path' to
- 'DATADIR/java/libgcj-VERSION.jar'.
-
-'--with-ecj-jar=FILENAME'
+`--enable-java-maintainer-mode'
+ By default the `libjava' build will not attempt to compile the
+ `.java' source files to `.class'. Instead, it will use the
+ `.class' files from the source tree. If you use this option you
+ must have executables named `ecj1' and `gjavah' in your path for
+ use by the build. You must use this option if you intend to
+ modify any `.java' files in `libjava'.
+
+`--with-java-home=DIRNAME'
+ This `libjava' option overrides the default value of the
+ `java.home' system property. It is also used to set
+ `sun.boot.class.path' to `DIRNAME/lib/rt.jar'. By default
+ `java.home' is set to `PREFIX' and `sun.boot.class.path' to
+ `DATADIR/java/libgcj-VERSION.jar'.
+
+`--with-ecj-jar=FILENAME'
This option can be used to specify the location of an external jar
file containing the Eclipse Java compiler. A specially modified
- version of this compiler is used by 'gcj' to parse '.java' source
- files. If this option is given, the 'libjava' build will create
- and install an 'ecj1' executable which uses this jar file at
+ version of this compiler is used by `gcj' to parse `.java' source
+ files. If this option is given, the `libjava' build will create
+ and install an `ecj1' executable which uses this jar file at
runtime.
- If this option is not given, but an 'ecj.jar' file is found in the
- topmost source tree at configure time, then the 'libgcj' build will
- create and install 'ecj1', and will also install the discovered
- 'ecj.jar' into a suitable place in the install tree.
+ If this option is not given, but an `ecj.jar' file is found in the
+ topmost source tree at configure time, then the `libgcj' build
+ will create and install `ecj1', and will also install the
+ discovered `ecj.jar' into a suitable place in the install tree.
- If 'ecj1' is not installed, then the user will have to supply one
- on his path in order for 'gcj' to properly parse '.java' source
+ If `ecj1' is not installed, then the user will have to supply one
+ on his path in order for `gcj' to properly parse `.java' source
files. A suitable jar is available from
- <ftp://sourceware.org/pub/java/>.
+ `ftp://sourceware.org/pub/java/'.
-'--disable-getenv-properties'
- Don't set system properties from 'GCJ_PROPERTIES'.
+`--disable-getenv-properties'
+ Don't set system properties from `GCJ_PROPERTIES'.
-'--enable-hash-synchronization'
- Use a global hash table for monitor locks. Ordinarily, 'libgcj''s
- 'configure' script automatically makes the correct choice for this
+`--enable-hash-synchronization'
+ Use a global hash table for monitor locks. Ordinarily, `libgcj''s
+ `configure' script automatically makes the correct choice for this
option for your platform. Only use this if you know you need the
library to be configured differently.
-'--enable-interpreter'
+`--enable-interpreter'
Enable the Java interpreter. The interpreter is automatically
enabled by default on all platforms that support it. This option
- is really only useful if you want to disable the interpreter (using
- '--disable-interpreter').
+ is really only useful if you want to disable the interpreter
+ (using `--disable-interpreter').
-'--disable-java-net'
+`--disable-java-net'
Disable java.net. This disables the native part of java.net only,
using non-functional stubs for native method implementations.
-'--disable-jvmpi'
+`--disable-jvmpi'
Disable JVMPI support.
-'--disable-libgcj-bc'
+`--disable-libgcj-bc'
Disable BC ABI compilation of certain parts of libgcj. By default,
- some portions of libgcj are compiled with '-findirect-dispatch' and
- '-fno-indirect-classes', allowing them to be overridden at
+ some portions of libgcj are compiled with `-findirect-dispatch'
+ and `-fno-indirect-classes', allowing them to be overridden at
run-time.
- If '--disable-libgcj-bc' is specified, libgcj is built without
+ If `--disable-libgcj-bc' is specified, libgcj is built without
these options. This allows the compile-time linker to resolve
dependencies when statically linking to libgcj. However it makes
it impossible to override the affected portions of libgcj at
run-time.
-'--enable-reduced-reflection'
- Build most of libgcj with '-freduced-reflection'. This reduces the
- size of libgcj at the expense of not being able to do accurate
+`--enable-reduced-reflection'
+ Build most of libgcj with `-freduced-reflection'. This reduces
+ the size of libgcj at the expense of not being able to do accurate
reflection on the classes it contains. This option is safe if you
know that code using libgcj will never use reflection on the
standard runtime classes in libgcj (including using serialization,
RMI or CORBA).
-'--with-ecos'
+`--with-ecos'
Enable runtime eCos target support.
-'--without-libffi'
- Don't use 'libffi'. This will disable the interpreter and JNI
- support as well, as these require 'libffi' to work.
+`--without-libffi'
+ Don't use `libffi'. This will disable the interpreter and JNI
+ support as well, as these require `libffi' to work.
-'--enable-libgcj-debug'
+`--enable-libgcj-debug'
Enable runtime debugging code.
-'--enable-libgcj-multifile'
- If specified, causes all '.java' source files to be compiled into
- '.class' files in one invocation of 'gcj'. This can speed up build
- time, but is more resource-intensive. If this option is
- unspecified or disabled, 'gcj' is invoked once for each '.java'
- file to compile into a '.class' file.
+`--enable-libgcj-multifile'
+ If specified, causes all `.java' source files to be compiled into
+ `.class' files in one invocation of `gcj'. This can speed up
+ build time, but is more resource-intensive. If this option is
+ unspecified or disabled, `gcj' is invoked once for each `.java'
+ file to compile into a `.class' file.
-'--with-libiconv-prefix=DIR'
- Search for libiconv in 'DIR/include' and 'DIR/lib'.
+`--with-libiconv-prefix=DIR'
+ Search for libiconv in `DIR/include' and `DIR/lib'.
-'--enable-sjlj-exceptions'
- Force use of the 'setjmp'/'longjmp'-based scheme for exceptions.
- 'configure' ordinarily picks the correct value based on the
+`--enable-sjlj-exceptions'
+ Force use of the `setjmp'/`longjmp'-based scheme for exceptions.
+ `configure' ordinarily picks the correct value based on the
platform. Only use this option if you are sure you need a
different setting.
-'--with-system-zlib'
- Use installed 'zlib' rather than that included with GCC.
+`--with-system-zlib'
+ Use installed `zlib' rather than that included with GCC.
-'--with-win32-nlsapi=ansi, unicows or unicode'
- Indicates how MinGW 'libgcj' translates between UNICODE characters
+`--with-win32-nlsapi=ansi, unicows or unicode'
+ Indicates how MinGW `libgcj' translates between UNICODE characters
and the Win32 API.
-'--enable-java-home'
+`--enable-java-home'
If enabled, this creates a JPackage compatible SDK environment
during install. Note that if -enable-java-home is used,
-with-arch-directory=ARCH must also be specified.
-'--with-arch-directory=ARCH'
- Specifies the name to use for the 'jre/lib/ARCH' directory in the
- SDK environment created when -enable-java-home is passed. Typical
+`--with-arch-directory=ARCH'
+ Specifies the name to use for the `jre/lib/ARCH' directory in the
+ SDK environment created when -enable-java-home is passed. Typical
names for this directory include i386, amd64, ia64, etc.
-'--with-os-directory=DIR'
- Specifies the OS directory for the SDK include directory. This is
+`--with-os-directory=DIR'
+ Specifies the OS directory for the SDK include directory. This is
set to auto detect, and is typically 'linux'.
-'--with-origin-name=NAME'
- Specifies the JPackage origin name. This defaults to the 'gcj' in
+`--with-origin-name=NAME'
+ Specifies the JPackage origin name. This defaults to the 'gcj' in
java-1.5.0-gcj.
-'--with-arch-suffix=SUFFIX'
- Specifies the suffix for the sdk directory. Defaults to the empty
+`--with-arch-suffix=SUFFIX'
+ Specifies the suffix for the sdk directory. Defaults to the empty
string. Examples include '.x86_64' in
'java-1.5.0-gcj-1.5.0.0.x86_64'.
-'--with-jvm-root-dir=DIR'
+`--with-jvm-root-dir=DIR'
Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
-'--with-jvm-jar-dir=DIR'
- Specifies where to install jars. Default is
+`--with-jvm-jar-dir=DIR'
+ Specifies where to install jars. Default is
$(prefix)/lib/jvm-exports.
-'--with-python-dir=DIR'
- Specifies where to install the Python modules used for aot-compile.
- DIR should not include the prefix used in installation. For
- example, if the Python modules are to be installed in
- /usr/lib/python2.5/site-packages, then
- -with-python-dir=/lib/python2.5/site-packages should be passed. If
+`--with-python-dir=DIR'
+ Specifies where to install the Python modules used for
+ aot-compile. DIR should not include the prefix used in
+ installation. For example, if the Python modules are to be
+ installed in /usr/lib/python2.5/site-packages, then
+ -with-python-dir=/lib/python2.5/site-packages should be passed. If
this is not specified, then the Python modules are installed in
$(prefix)/share/python.
-'--enable-aot-compile-rpm'
+`--enable-aot-compile-rpm'
Adds aot-compile-rpm to the list of installed scripts.
-'--enable-browser-plugin'
+`--enable-browser-plugin'
Build the gcjwebplugin web browser plugin.
-'--enable-static-libjava'
- Build static libraries in libjava. The default is to only build
+`--enable-static-libjava'
+ Build static libraries in libjava. The default is to only build
shared libraries.
- 'ansi'
- Use the single-byte 'char' and the Win32 A functions natively,
+ `ansi'
+ Use the single-byte `char' and the Win32 A functions natively,
translating to and from UNICODE when using these functions.
If unspecified, this is the default.
- 'unicows'
- Use the 'WCHAR' and Win32 W functions natively. Adds
- '-lunicows' to 'libgcj.spec' to link with 'libunicows'.
- 'unicows.dll' needs to be deployed on Microsoft Windows 9X
- machines running built executables. 'libunicows.a', an
- open-source import library around Microsoft's 'unicows.dll',
- is obtained from <http://libunicows.sourceforge.net/>, which
- also gives details on getting 'unicows.dll' from Microsoft.
-
- 'unicode'
- Use the 'WCHAR' and Win32 W functions natively. Does _not_
- add '-lunicows' to 'libgcj.spec'. The built executables will
+ `unicows'
+ Use the `WCHAR' and Win32 W functions natively. Adds
+ `-lunicows' to `libgcj.spec' to link with `libunicows'.
+ `unicows.dll' needs to be deployed on Microsoft Windows 9X
+ machines running built executables. `libunicows.a', an
+ open-source import library around Microsoft's `unicows.dll',
+ is obtained from `http://libunicows.sourceforge.net/', which
+ also gives details on getting `unicows.dll' from Microsoft.
+
+ `unicode'
+ Use the `WCHAR' and Win32 W functions natively. Does _not_
+ add `-lunicows' to `libgcj.spec'. The built executables will
only run on Microsoft Windows NT and above.
AWT-Specific Options
....................
-'--with-x'
+`--with-x'
Use the X Window System.
-'--enable-java-awt=PEER(S)'
+`--enable-java-awt=PEER(S)'
Specifies the AWT peer library or libraries to build alongside
- 'libgcj'. If this option is unspecified or disabled, AWT will be
- non-functional. Current valid values are 'gtk' and 'xlib'.
+ `libgcj'. If this option is unspecified or disabled, AWT will be
+ non-functional. Current valid values are `gtk' and `xlib'.
Multiple libraries should be separated by a comma (i.e.
- '--enable-java-awt=gtk,xlib').
+ `--enable-java-awt=gtk,xlib').
-'--enable-gtk-cairo'
+`--enable-gtk-cairo'
Build the cairo Graphics2D implementation on GTK.
-'--enable-java-gc=TYPE'
- Choose garbage collector. Defaults to 'boehm' if unspecified.
+`--enable-java-gc=TYPE'
+ Choose garbage collector. Defaults to `boehm' if unspecified.
-'--disable-gtktest'
+`--disable-gtktest'
Do not try to compile and run a test GTK+ program.
-'--disable-glibtest'
+`--disable-glibtest'
Do not try to compile and run a test GLIB program.
-'--with-libart-prefix=PFX'
+`--with-libart-prefix=PFX'
Prefix where libart is installed (optional).
-'--with-libart-exec-prefix=PFX'
+`--with-libart-exec-prefix=PFX'
Exec prefix where libart is installed (optional).
-'--disable-libarttest'
+`--disable-libarttest'
Do not try to compile and run a test libart program.
-Overriding 'configure' test results
+
+Overriding `configure' test results
...................................
Sometimes, it might be necessary to override the result of some
-'configure' test, for example in order to ease porting to a new system
-or work around a bug in a test. The toplevel 'configure' script
+`configure' test, for example in order to ease porting to a new system
+or work around a bug in a test. The toplevel `configure' script
provides three variables for this:
-'build_configargs'
- The contents of this variable is passed to all build 'configure'
+`build_configargs'
+ The contents of this variable is passed to all build `configure'
scripts.
-'host_configargs'
- The contents of this variable is passed to all host 'configure'
+`host_configargs'
+ The contents of this variable is passed to all host `configure'
scripts.
-'target_configargs'
- The contents of this variable is passed to all target 'configure'
+`target_configargs'
+ The contents of this variable is passed to all target `configure'
scripts.
- In order to avoid shell and 'make' quoting issues for complex
-overrides, you can pass a setting for 'CONFIG_SITE' and set variables in
-the site file.
+
+ In order to avoid shell and `make' quoting issues for complex
+overrides, you can pass a setting for `CONFIG_SITE' and set variables
+in the site file.

File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, Up: Installing GCC
@@ -2085,11 +2115,11 @@ File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, U
5 Building
**********
-Now that GCC is configured, you are ready to build the compiler and
+ Now that GCC is configured, you are ready to build the compiler and
runtime libraries.
Some commands executed when making the compiler may fail (return a
-nonzero status) and be ignored by 'make'. These failures, which are
+nonzero status) and be ignored by `make'. These failures, which are
often due to files that were not found, are expected, and can safely be
ignored.
@@ -2097,10 +2127,10 @@ ignored.
Unless you are a GCC developer, you can generally ignore these warnings
unless they cause compilation to fail. Developers should attempt to fix
any warnings encountered, however they can temporarily continue past
-warnings-as-errors by specifying the configure flag '--disable-werror'.
+warnings-as-errors by specifying the configure flag `--disable-werror'.
On certain old systems, defining certain environment variables such
-as 'CC' can interfere with the functioning of 'make'.
+as `CC' can interfere with the functioning of `make'.
If you encounter seemingly strange errors when trying to build the
compiler in a directory other than the source directory, it could be
@@ -2108,20 +2138,20 @@ because you have previously configured the compiler in the source
directory. Make sure you have done all the necessary preparations.
If you build GCC on a BSD system using a directory stored in an old
-System V file system, problems may occur in running 'fixincludes' if the
+System V file system, problems may occur in running `fixincludes' if the
System V file system doesn't support symbolic links. These problems
-result in a failure to fix the declaration of 'size_t' in 'sys/types.h'.
-If you find that 'size_t' is a signed type and that type mismatches
-occur, this could be the cause.
+result in a failure to fix the declaration of `size_t' in
+`sys/types.h'. If you find that `size_t' is a signed type and that
+type mismatches occur, this could be the cause.
The solution is not to use such a directory for building GCC.
Similarly, when building from SVN or snapshots, or if you modify
-'*.l' files, you need the Flex lexical analyzer generator installed. If
-you do not modify '*.l' files, releases contain the Flex-generated files
-and you do not need Flex installed to build them. There is still one
-Flex-based lexical analyzer (part of the build machinery, not of GCC
-itself) that is used even if you only build the C front end.
+`*.l' files, you need the Flex lexical analyzer generator installed.
+If you do not modify `*.l' files, releases contain the Flex-generated
+files and you do not need Flex installed to build them. There is still
+one Flex-based lexical analyzer (part of the build machinery, not of
+GCC itself) that is used even if you only build the C front end.
When building from SVN or snapshots, or if you modify Texinfo
documentation, you need version 4.7 or later of Texinfo installed if you
@@ -2132,10 +2162,10 @@ documentation pre-built for the unmodified documentation in the release.
==============================
For a native build, the default configuration is to perform a 3-stage
-bootstrap of the compiler when 'make' is invoked. This will build the
+bootstrap of the compiler when `make' is invoked. This will build the
entire GCC system and ensure that it compiles itself correctly. It can
-be disabled with the '--disable-bootstrap' parameter to 'configure', but
-bootstrapping is suggested because the compiler will be tested more
+be disabled with the `--disable-bootstrap' parameter to `configure',
+but bootstrapping is suggested because the compiler will be tested more
completely and could also have better performance.
The bootstrapping process will complete the following steps:
@@ -2150,18 +2180,19 @@ completely and could also have better performance.
* Perform a comparison test of the stage2 and stage3 compilers.
- * Build runtime libraries using the stage3 compiler from the previous
- step.
+ * Build runtime libraries using the stage3 compiler from the
+ previous step.
+
- If you are short on disk space you might consider 'make
+ If you are short on disk space you might consider `make
bootstrap-lean' instead. The sequence of compilation is the same
described above, but object files from the stage1 and stage2 of the
3-stage bootstrap of the compiler are deleted as soon as they are no
longer needed.
If you wish to use non-default GCC flags when compiling the stage2
-and stage3 compilers, set 'BOOT_CFLAGS' on the command line when doing
-'make'. For example, if you want to save additional space during the
+and stage3 compilers, set `BOOT_CFLAGS' on the command line when doing
+`make'. For example, if you want to save additional space during the
bootstrap and in the final installation as well, you can build the
compiler binaries without debugging information as in the following
example. This will save roughly 40% of disk space both for the
@@ -2170,127 +2201,131 @@ debugging information.)
make BOOT_CFLAGS='-O' bootstrap
- You can place non-default optimization flags into 'BOOT_CFLAGS'; they
-are less well tested here than the default of '-g -O2', but should still
-work. In a few cases, you may find that you need to specify special
-flags such as '-msoft-float' here to complete the bootstrap; or, if the
-native compiler miscompiles the stage1 compiler, you may need to work
-around this, by choosing 'BOOT_CFLAGS' to avoid the parts of the stage1
-compiler that were miscompiled, or by using 'make bootstrap4' to
+ You can place non-default optimization flags into `BOOT_CFLAGS'; they
+are less well tested here than the default of `-g -O2', but should
+still work. In a few cases, you may find that you need to specify
+special flags such as `-msoft-float' here to complete the bootstrap; or,
+if the native compiler miscompiles the stage1 compiler, you may need to
+work around this, by choosing `BOOT_CFLAGS' to avoid the parts of the
+stage1 compiler that were miscompiled, or by using `make bootstrap4' to
increase the number of stages of bootstrap.
- 'BOOT_CFLAGS' does not apply to bootstrapped target libraries. Since
-these are always compiled with the compiler currently being
-bootstrapped, you can use 'CFLAGS_FOR_TARGET' to modify their
+ `BOOT_CFLAGS' does not apply to bootstrapped target libraries.
+Since these are always compiled with the compiler currently being
+bootstrapped, you can use `CFLAGS_FOR_TARGET' to modify their
compilation flags, as for non-bootstrapped target libraries. Again, if
the native compiler miscompiles the stage1 compiler, you may need to
work around this by avoiding non-working parts of the stage1 compiler.
-Use 'STAGE1_TFLAGS' to this end.
+Use `STAGE1_TFLAGS' to this end.
- If you used the flag '--enable-languages=...' to restrict the
-compilers to be built, only those you've actually enabled will be built.
-This will of course only build those runtime libraries, for which the
-particular compiler has been built. Please note, that re-defining
-'LANGUAGES' when calling 'make' *does not* work anymore!
+ If you used the flag `--enable-languages=...' to restrict the
+compilers to be built, only those you've actually enabled will be
+built. This will of course only build those runtime libraries, for
+which the particular compiler has been built. Please note, that
+re-defining `LANGUAGES' when calling `make' *does not* work anymore!
If the comparison of stage2 and stage3 fails, this normally indicates
that the stage2 compiler has compiled GCC incorrectly, and is therefore
a potentially serious bug which you should investigate and report. (On
a few systems, meaningful comparison of object files is impossible; they
-always appear "different". If you encounter this problem, you will need
-to disable comparison in the 'Makefile'.)
+always appear "different". If you encounter this problem, you will
+need to disable comparison in the `Makefile'.)
If you do not want to bootstrap your compiler, you can configure with
-'--disable-bootstrap'. In particular cases, you may want to bootstrap
+`--disable-bootstrap'. In particular cases, you may want to bootstrap
your compiler even if the target system is not the same as the one you
are building on: for example, you could build a
-'powerpc-unknown-linux-gnu' toolchain on a 'powerpc64-unknown-linux-gnu'
-host. In this case, pass '--enable-bootstrap' to the configure script.
+`powerpc-unknown-linux-gnu' toolchain on a
+`powerpc64-unknown-linux-gnu' host. In this case, pass
+`--enable-bootstrap' to the configure script.
- 'BUILD_CONFIG' can be used to bring in additional customization to
+ `BUILD_CONFIG' can be used to bring in additional customization to
the build. It can be set to a whitespace-separated list of names. For
-each such 'NAME', top-level 'config/NAME.mk' will be included by the
-top-level 'Makefile', bringing in any settings it contains. The default
-'BUILD_CONFIG' can be set using the configure option
-'--with-build-config=NAME...'. Some examples of supported build
+each such `NAME', top-level `config/`NAME'.mk' will be included by the
+top-level `Makefile', bringing in any settings it contains. The
+default `BUILD_CONFIG' can be set using the configure option
+`--with-build-config=`NAME'...'. Some examples of supported build
configurations are:
-'bootstrap-O1'
- Removes any '-O'-started option from 'BOOT_CFLAGS', and adds '-O1'
- to it. 'BUILD_CONFIG=bootstrap-O1' is equivalent to
- 'BOOT_CFLAGS='-g -O1''.
+`bootstrap-O1'
+ Removes any `-O'-started option from `BOOT_CFLAGS', and adds `-O1'
+ to it. `BUILD_CONFIG=bootstrap-O1' is equivalent to
+ `BOOT_CFLAGS='-g -O1''.
-'bootstrap-O3'
- Analogous to 'bootstrap-O1'.
+`bootstrap-O3'
+ Analogous to `bootstrap-O1'.
-'bootstrap-lto'
+`bootstrap-lto'
Enables Link-Time Optimization for host tools during bootstrapping.
- 'BUILD_CONFIG=bootstrap-lto' is equivalent to adding '-flto' to
- 'BOOT_CFLAGS'. This option assumes that the host supports the
- linker plugin (e.g. GNU ld version 2.21 or later or GNU gold
+ `BUILD_CONFIG=bootstrap-lto' is equivalent to adding `-flto' to
+ `BOOT_CFLAGS'. This option assumes that the host supports the
+ linker plugin (e.g. GNU ld version 2.21 or later or GNU gold
version 2.21 or later).
-'bootstrap-lto-noplugin'
- This option is similar to 'bootstrap-lto', but is intended for
+`bootstrap-lto-noplugin'
+ This option is similar to `bootstrap-lto', but is intended for
hosts that do not support the linker plugin. Without the linker
plugin static libraries are not compiled with link-time
optimizations. Since the GCC middle end and back end are in
- 'libbackend.a' this means that only the front end is actually LTO
+ `libbackend.a' this means that only the front end is actually LTO
optimized.
-'bootstrap-debug'
+`bootstrap-debug'
Verifies that the compiler generates the same executable code,
- whether or not it is asked to emit debug information. To this end,
- this option builds stage2 host programs without debug information,
- and uses 'contrib/compare-debug' to compare them with the stripped
- stage3 object files. If 'BOOT_CFLAGS' is overridden so as to not
- enable debug information, stage2 will have it, and stage3 won't.
- This option is enabled by default when GCC bootstrapping is
- enabled, if 'strip' can turn object files compiled with and without
- debug info into identical object files. In addition to better test
- coverage, this option makes default bootstraps faster and leaner.
-
-'bootstrap-debug-big'
+ whether or not it is asked to emit debug information. To this
+ end, this option builds stage2 host programs without debug
+ information, and uses `contrib/compare-debug' to compare them with
+ the stripped stage3 object files. If `BOOT_CFLAGS' is overridden
+ so as to not enable debug information, stage2 will have it, and
+ stage3 won't. This option is enabled by default when GCC
+ bootstrapping is enabled, if `strip' can turn object files
+ compiled with and without debug info into identical object files.
+ In addition to better test coverage, this option makes default
+ bootstraps faster and leaner.
+
+`bootstrap-debug-big'
Rather than comparing stripped object files, as in
- 'bootstrap-debug', this option saves internal compiler dumps during
- stage2 and stage3 and compares them as well, which helps catch
- additional potential problems, but at a great cost in terms of disk
- space. It can be specified in addition to 'bootstrap-debug'.
-
-'bootstrap-debug-lean'
- This option saves disk space compared with 'bootstrap-debug-big',
+ `bootstrap-debug', this option saves internal compiler dumps
+ during stage2 and stage3 and compares them as well, which helps
+ catch additional potential problems, but at a great cost in terms
+ of disk space. It can be specified in addition to
+ `bootstrap-debug'.
+
+`bootstrap-debug-lean'
+ This option saves disk space compared with `bootstrap-debug-big',
but at the expense of some recompilation. Instead of saving the
dumps of stage2 and stage3 until the final compare, it uses
- '-fcompare-debug' to generate, compare and remove the dumps during
+ `-fcompare-debug' to generate, compare and remove the dumps during
stage3, repeating the compilation that already took place in
stage2, whose dumps were not saved.
-'bootstrap-debug-lib'
+`bootstrap-debug-lib'
This option tests executable code invariance over debug information
- generation on target libraries, just like 'bootstrap-debug-lean'
+ generation on target libraries, just like `bootstrap-debug-lean'
tests it on host programs. It builds stage3 libraries with
- '-fcompare-debug', and it can be used along with any of the
- 'bootstrap-debug' options above.
+ `-fcompare-debug', and it can be used along with any of the
+ `bootstrap-debug' options above.
- There aren't '-lean' or '-big' counterparts to this option because
+ There aren't `-lean' or `-big' counterparts to this option because
most libraries are only build in stage3, so bootstrap compares
would not get significant coverage. Moreover, the few libraries
built in stage2 are used in stage3 host programs, so we wouldn't
want to compile stage2 libraries with different options for
comparison purposes.
-'bootstrap-debug-ckovw'
+`bootstrap-debug-ckovw'
Arranges for error messages to be issued if the compiler built on
- any stage is run without the option '-fcompare-debug'. This is
- useful to verify the full '-fcompare-debug' testing coverage. It
- must be used along with 'bootstrap-debug-lean' and
- 'bootstrap-debug-lib'.
+ any stage is run without the option `-fcompare-debug'. This is
+ useful to verify the full `-fcompare-debug' testing coverage. It
+ must be used along with `bootstrap-debug-lean' and
+ `bootstrap-debug-lib'.
-'bootstrap-time'
+`bootstrap-time'
Arranges for the run time of each program started by the GCC
- driver, built in any stage, to be logged to 'time.log', in the top
+ driver, built in any stage, to be logged to `time.log', in the top
level of the build tree.
+
5.2 Building a cross compiler
=============================
@@ -2298,20 +2333,20 @@ When building a cross compiler, it is not generally possible to do a
3-stage bootstrap of the compiler. This makes for an interesting
problem as parts of GCC can only be built with GCC.
- To build a cross compiler, we recommend first building and installing
-a native compiler. You can then use the native GCC compiler to build
-the cross compiler. The installed native compiler needs to be GCC
-version 2.95 or later.
+ To build a cross compiler, we recommend first building and
+installing a native compiler. You can then use the native GCC compiler
+to build the cross compiler. The installed native compiler needs to be
+GCC version 2.95 or later.
If the cross compiler is to be built with support for the Java
programming language and the ability to compile .java source files is
desired, the installed native compiler used to build the cross compiler
-needs to be the same GCC version as the cross compiler. In addition the
-cross compiler needs to be configured with '--with-ecj-jar=...'.
+needs to be the same GCC version as the cross compiler. In addition
+the cross compiler needs to be configured with `--with-ecj-jar=...'.
Assuming you have already installed a native copy of GCC and
-configured your cross compiler, issue the command 'make', which performs
-the following steps:
+configured your cross compiler, issue the command `make', which
+performs the following steps:
* Build host tools necessary to build the compiler.
@@ -2328,20 +2363,20 @@ the following steps:
If you are not building GNU binutils in the same source tree as GCC,
you will need a cross-assembler and cross-linker installed before
-configuring GCC. Put them in the directory 'PREFIX/TARGET/bin'. Here
+configuring GCC. Put them in the directory `PREFIX/TARGET/bin'. Here
is a table of the tools you should put in this directory:
-'as'
+`as'
This should be the cross-assembler.
-'ld'
+`ld'
This should be the cross-linker.
-'ar'
+`ar'
This should be the cross-archiver: a program which can manipulate
archive files (linker libraries) in the target machine's format.
-'ranlib'
+`ranlib'
This should be a program to construct a symbol table in an archive
file.
@@ -2350,72 +2385,72 @@ and copy or link them to the proper place to for the cross-compiler to
find them when run later.
The easiest way to provide these files is to build the Binutils
-package. Configure it with the same '--host' and '--target' options
+package. Configure it with the same `--host' and `--target' options
that you use for configuring GCC, then build and install them. They
install their executables automatically into the proper directory.
Alas, they do not support all the targets that GCC supports.
If you are not building a C library in the same source tree as GCC,
you should also provide the target libraries and headers before
-configuring GCC, specifying the directories with '--with-sysroot' or
-'--with-headers' and '--with-libs'. Many targets also require "start
-files" such as 'crt0.o' and 'crtn.o' which are linked into each
-executable. There may be several alternatives for 'crt0.o', for use
+configuring GCC, specifying the directories with `--with-sysroot' or
+`--with-headers' and `--with-libs'. Many targets also require "start
+files" such as `crt0.o' and `crtn.o' which are linked into each
+executable. There may be several alternatives for `crt0.o', for use
with profiling or other compilation options. Check your target's
-definition of 'STARTFILE_SPEC' to find out what start files it uses.
+definition of `STARTFILE_SPEC' to find out what start files it uses.
5.3 Building in parallel
========================
GNU Make 3.80 and above, which is necessary to build GCC, support
-building in parallel. To activate this, you can use 'make -j 2' instead
-of 'make'. You can also specify a bigger number, and in most cases
-using a value greater than the number of processors in your machine will
-result in fewer and shorter I/O latency hits, thus improving overall
-throughput; this is especially true for slow drives and network
-filesystems.
+building in parallel. To activate this, you can use `make -j 2'
+instead of `make'. You can also specify a bigger number, and in most
+cases using a value greater than the number of processors in your
+machine will result in fewer and shorter I/O latency hits, thus
+improving overall throughput; this is especially true for slow drives
+and network filesystems.
5.4 Building the Ada compiler
=============================
In order to build GNAT, the Ada compiler, you need a working GNAT
compiler (GCC version 4.0 or later). This includes GNAT tools such as
-'gnatmake' and 'gnatlink', since the Ada front end is written in Ada and
+`gnatmake' and `gnatlink', since the Ada front end is written in Ada and
uses some GNAT-specific extensions.
In order to build a cross compiler, it is suggested to install the
new compiler as native first, and then use it to build the cross
compiler.
- 'configure' does not test whether the GNAT installation works and has
-a sufficiently recent version; if too old a GNAT version is installed,
-the build will fail unless '--enable-languages' is used to disable
-building the Ada front end.
+ `configure' does not test whether the GNAT installation works and
+has a sufficiently recent version; if too old a GNAT version is
+installed, the build will fail unless `--enable-languages' is used to
+disable building the Ada front end.
- 'ADA_INCLUDE_PATH' and 'ADA_OBJECT_PATH' environment variables must
+ `ADA_INCLUDE_PATH' and `ADA_OBJECT_PATH' environment variables must
not be set when building the Ada compiler, the Ada tools, or the Ada
-runtime libraries. You can check that your build environment is clean
-by verifying that 'gnatls -v' lists only one explicit path in each
+runtime libraries. You can check that your build environment is clean
+by verifying that `gnatls -v' lists only one explicit path in each
section.
5.5 Building with profile feedback
==================================
It is possible to use profile feedback to optimize the compiler itself.
-This should result in a faster compiler binary. Experiments done on x86
-using gcc 3.3 showed approximately 7 percent speedup on compiling C
-programs. To bootstrap the compiler with profile feedback, use 'make
+This should result in a faster compiler binary. Experiments done on
+x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C
+programs. To bootstrap the compiler with profile feedback, use `make
profiledbootstrap'.
- When 'make profiledbootstrap' is run, it will first build a 'stage1'
-compiler. This compiler is used to build a 'stageprofile' compiler
+ When `make profiledbootstrap' is run, it will first build a `stage1'
+compiler. This compiler is used to build a `stageprofile' compiler
instrumented to collect execution counts of instruction and branch
probabilities. Then runtime libraries are compiled with profile
-collected. Finally a 'stagefeedback' compiler is built using the
+collected. Finally a `stagefeedback' compiler is built using the
information collected.
Unlike standard bootstrap, several additional restrictions apply.
-The compiler used to build 'stage1' needs to support a 64-bit integral
+The compiler used to build `stage1' needs to support a 64-bit integral
type. It is recommended to only use GCC for this.

@@ -2424,14 +2459,14 @@ File: gccinstall.info, Node: Testing, Next: Final install, Prev: Building, U
6 Installing GCC: Testing
*************************
-Before you install GCC, we encourage you to run the testsuites and to
+ Before you install GCC, we encourage you to run the testsuites and to
compare your results with results from a similar configuration that have
been submitted to the gcc-testresults mailing list. Some of these
archived results are linked from the build status lists at
-<http://gcc.gnu.org/buildstat.html>, although not everyone who reports a
-successful build runs the testsuites and submits the results. This step
-is optional and may require you to download additional software, but it
-can give you confidence in your new GCC installation or point out
+`http://gcc.gnu.org/buildstat.html', although not everyone who reports
+a successful build runs the testsuites and submits the results. This
+step is optional and may require you to download additional software,
+but it can give you confidence in your new GCC installation or point out
problems before you install and start using your new GCC.
First, you must have downloaded the testsuites. These are part of
@@ -2441,10 +2476,10 @@ any front ends, you must download the testsuites separately.
Second, you must have the testing tools installed. This includes
DejaGnu, Tcl, and Expect; the DejaGnu site has links to these.
- If the directories where 'runtest' and 'expect' were installed are
-not in the 'PATH', you may need to set the following environment
-variables appropriately, as in the following example (which assumes that
-DejaGnu has been installed under '/usr/local'):
+ If the directories where `runtest' and `expect' were installed are
+not in the `PATH', you may need to set the following environment
+variables appropriately, as in the following example (which assumes
+that DejaGnu has been installed under `/usr/local'):
TCL_LIBRARY = /usr/local/share/tcl8.0
DEJAGNULIBS = /usr/local/share/dejagnu
@@ -2456,55 +2491,56 @@ portability in the DejaGnu code.)
Finally, you can run the testsuite (which may take a long time):
cd OBJDIR; make -k check
- This will test various components of GCC, such as compiler front ends
-and runtime libraries. While running the testsuite, DejaGnu might emit
-some harmless messages resembling 'WARNING: Couldn't find the global
-config file.' or 'WARNING: Couldn't find tool init file' that can be
-ignored.
+ This will test various components of GCC, such as compiler front
+ends and runtime libraries. While running the testsuite, DejaGnu might
+emit some harmless messages resembling `WARNING: Couldn't find the
+global config file.' or `WARNING: Couldn't find tool init file' that
+can be ignored.
If you are testing a cross-compiler, you may want to run the
testsuite on a simulator as described at
-<http://gcc.gnu.org/simtest-howto.html>.
+`http://gcc.gnu.org/simtest-howto.html'.
6.1 How can you run the testsuite on selected tests?
====================================================
-In order to run sets of tests selectively, there are targets 'make
-check-gcc' and language specific 'make check-c', 'make check-c++', 'make
-check-fortran', 'make check-java', 'make check-ada', 'make check-objc',
-'make check-obj-c++', 'make check-lto' in the 'gcc' subdirectory of the
-object directory. You can also just run 'make check' in a subdirectory
-of the object directory.
+In order to run sets of tests selectively, there are targets `make
+check-gcc' and language specific `make check-c', `make check-c++',
+`make check-fortran', `make check-java', `make check-ada', `make
+check-objc', `make check-obj-c++', `make check-lto' in the `gcc'
+subdirectory of the object directory. You can also just run `make
+check' in a subdirectory of the object directory.
- A more selective way to just run all 'gcc' execute tests in the
+ A more selective way to just run all `gcc' execute tests in the
testsuite is to use
make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS"
- Likewise, in order to run only the 'g++' "old-deja" tests in the
-testsuite with filenames matching '9805*', you would use
+ Likewise, in order to run only the `g++' "old-deja" tests in the
+testsuite with filenames matching `9805*', you would use
make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS"
- The '*.exp' files are located in the testsuite directories of the GCC
-source, the most important ones being 'compile.exp', 'execute.exp',
-'dg.exp' and 'old-deja.exp'. To get a list of the possible '*.exp'
-files, pipe the output of 'make check' into a file and look at the
-'Running ... .exp' lines.
+ The `*.exp' files are located in the testsuite directories of the GCC
+source, the most important ones being `compile.exp', `execute.exp',
+`dg.exp' and `old-deja.exp'. To get a list of the possible `*.exp'
+files, pipe the output of `make check' into a file and look at the
+`Running ... .exp' lines.
6.2 Passing options and running multiple testsuites
===================================================
You can pass multiple options to the testsuite using the
-'--target_board' option of DejaGNU, either passed as part of
-'RUNTESTFLAGS', or directly to 'runtest' if you prefer to work outside
+`--target_board' option of DejaGNU, either passed as part of
+`RUNTESTFLAGS', or directly to `runtest' if you prefer to work outside
the makefiles. For example,
make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
- will run the standard 'g++' testsuites ("unix" is the target name for
-a standard native testsuite situation), passing '-O3 -fmerge-constants'
-to the compiler on every test, i.e., slashes separate options.
+ will run the standard `g++' testsuites ("unix" is the target name
+for a standard native testsuite situation), passing `-O3
+-fmerge-constants' to the compiler on every test, i.e., slashes
+separate options.
You can run the testsuites multiple times using combinations of
options with a syntax similar to the brace expansion of popular shells:
@@ -2513,7 +2549,7 @@ options with a syntax similar to the brace expansion of popular shells:
(Note the empty option caused by the trailing comma in the final
group.) The following will run each testsuite eight times using the
-'arm-sim' target, as if you had specified all possible combinations
+`arm-sim' target, as if you had specified all possible combinations
yourself:
--target_board='arm-sim/-mhard-float/-O1 \
@@ -2530,13 +2566,13 @@ This list:
..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
- will generate four combinations, all involving '-Wextra'.
+ will generate four combinations, all involving `-Wextra'.
The disadvantage to this method is that the testsuites are run in
serial, which is a waste on multiprocessor systems. For users with GNU
Make and a shell which performs brace expansion, you can run the
testsuites in parallel by having the shell perform the combinations and
-'make' do the parallel runs. Instead of using '--target_board', use a
+`make' do the parallel runs. Instead of using `--target_board', use a
special makefile target:
make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
@@ -2547,36 +2583,42 @@ special makefile target:
will run three concurrent "make-gcc" testsuites, eventually testing
all ten combinations as described above. Note that this is currently
-only supported in the 'gcc' subdirectory. (To see how this works, try
-typing 'echo' before the example given here.)
+only supported in the `gcc' subdirectory. (To see how this works, try
+typing `echo' before the example given here.)
6.3 Additional testing for Java Class Libraries
===============================================
-The Java runtime tests can be executed via 'make check' in the
-'TARGET/libjava/testsuite' directory in the build tree.
+The Java runtime tests can be executed via `make check' in the
+`TARGET/libjava/testsuite' directory in the build tree.
The Mauve Project provides a suite of tests for the Java Class
Libraries. This suite can be run as part of libgcj testing by placing
the Mauve tree within the libjava testsuite at
-'libjava/testsuite/libjava.mauve/mauve', or by specifying the location
-of that tree when invoking 'make', as in 'make MAUVEDIR=~/mauve check'.
+`libjava/testsuite/libjava.mauve/mauve', or by specifying the location
+of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'.
6.4 How to interpret test results
=================================
-The result of running the testsuite are various '*.sum' and '*.log'
-files in the testsuite subdirectories. The '*.log' files contain a
+The result of running the testsuite are various `*.sum' and `*.log'
+files in the testsuite subdirectories. The `*.log' files contain a
detailed log of the compiler invocations and the corresponding results,
-the '*.sum' files summarize the results. These summaries contain status
-codes for all tests:
+the `*.sum' files summarize the results. These summaries contain
+status codes for all tests:
* PASS: the test passed as expected
+
* XPASS: the test unexpectedly passed
+
* FAIL: the test unexpectedly failed
+
* XFAIL: the test failed as expected
+
* UNSUPPORTED: the test is not supported on this platform
+
* ERROR: the testsuite detected an error
+
* WARNING: the testsuite detected a possible problem
It is normal for some tests to report unexpected failures. At the
@@ -2588,15 +2630,15 @@ fixed in future releases.
===========================
If you want to report the results to the GCC project, use the
-'contrib/test_summary' shell script. Start it in the OBJDIR with
+`contrib/test_summary' shell script. Start it in the OBJDIR with
SRCDIR/contrib/test_summary -p your_commentary.txt \
-m gcc-testresults@gcc.gnu.org |sh
- This script uses the 'Mail' program to send the results, so make sure
-it is in your 'PATH'. The file 'your_commentary.txt' is prepended to
-the testsuite summary and should contain any special remarks you have on
-your results or your build environment. Please do not edit the
+ This script uses the `Mail' program to send the results, so make
+sure it is in your `PATH'. The file `your_commentary.txt' is prepended
+to the testsuite summary and should contain any special remarks you
+have on your results or your build environment. Please do not edit the
testsuite result block or the subject line, as these messages may be
automatically processed.
@@ -2606,8 +2648,8 @@ File: gccinstall.info, Node: Final install, Prev: Testing, Up: Installing GCC
7 Installing GCC: Final installation
************************************
-Now that GCC has been built (and optionally tested), you can install it
-with
+ Now that GCC has been built (and optionally tested), you can install
+it with
cd OBJDIR && make install
We strongly recommend to install into a target directory where there
@@ -2617,38 +2659,38 @@ that depend on this debugging information (catching Ada exceptions for
instance).
That step completes the installation of GCC; user level binaries can
-be found in 'PREFIX/bin' where PREFIX is the value you specified with
-the '--prefix' to configure (or '/usr/local' by default). (If you
-specified '--bindir', that directory will be used instead; otherwise, if
-you specified '--exec-prefix', 'EXEC-PREFIX/bin' will be used.) Headers
-for the C++ and Java libraries are installed in 'PREFIX/include';
-libraries in 'LIBDIR' (normally 'PREFIX/lib'); internal parts of the
-compiler in 'LIBDIR/gcc' and 'LIBEXECDIR/gcc'; documentation in info
-format in 'INFODIR' (normally 'PREFIX/info').
+be found in `PREFIX/bin' where PREFIX is the value you specified with
+the `--prefix' to configure (or `/usr/local' by default). (If you
+specified `--bindir', that directory will be used instead; otherwise,
+if you specified `--exec-prefix', `EXEC-PREFIX/bin' will be used.)
+Headers for the C++ and Java libraries are installed in
+`PREFIX/include'; libraries in `LIBDIR' (normally `PREFIX/lib');
+internal parts of the compiler in `LIBDIR/gcc' and `LIBEXECDIR/gcc';
+documentation in info format in `INFODIR' (normally `PREFIX/info').
When installing cross-compilers, GCC's executables are not only
-installed into 'BINDIR', that is, 'EXEC-PREFIX/bin', but additionally
-into 'EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
+installed into `BINDIR', that is, `EXEC-PREFIX/bin', but additionally
+into `EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
Typically, such "tooldirs" hold target-specific binutils, including
assembler and linker.
- Installation into a temporary staging area or into a 'chroot' jail
+ Installation into a temporary staging area or into a `chroot' jail
can be achieved with the command
make DESTDIR=PATH-TO-ROOTDIR install
where PATH-TO-ROOTDIR is the absolute path of a directory relative to
which all installation paths will be interpreted. Note that the
-directory specified by 'DESTDIR' need not exist yet; it will be created
+directory specified by `DESTDIR' need not exist yet; it will be created
if necessary.
- There is a subtle point with tooldirs and 'DESTDIR': If you relocate
-a cross-compiler installation with e.g. 'DESTDIR=ROOTDIR', then the
-directory 'ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
+ There is a subtle point with tooldirs and `DESTDIR': If you relocate
+a cross-compiler installation with e.g. `DESTDIR=ROOTDIR', then the
+directory `ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
duplicated GCC executables only if it already exists, it will not be
-created otherwise. This is regarded as a feature, not as a bug, because
-it gives slightly more control to the packagers using the 'DESTDIR'
-feature.
+created otherwise. This is regarded as a feature, not as a bug,
+because it gives slightly more control to the packagers using the
+`DESTDIR' feature.
You can install stripped programs and libraries with
@@ -2656,65 +2698,66 @@ feature.
If you are bootstrapping a released version of GCC then please
quickly review the build status page for your release, available from
-<http://gcc.gnu.org/buildstat.html>. If your system is not listed for
+`http://gcc.gnu.org/buildstat.html'. If your system is not listed for
the version of GCC that you built, send a note to <gcc@gcc.gnu.org>
indicating that you successfully built and installed GCC. Include the
following information:
- * Output from running 'SRCDIR/config.guess'. Do not send that file
+ * Output from running `SRCDIR/config.guess'. Do not send that file
itself, just the one-line output from running it.
- * The output of 'gcc -v' for your newly installed 'gcc'. This tells
+ * The output of `gcc -v' for your newly installed `gcc'. This tells
us which version of GCC you built and the options you passed to
configure.
- * Whether you enabled all languages or a subset of them. If you used
- a full distribution then this information is part of the configure
- options in the output of 'gcc -v', but if you downloaded the "core"
- compiler plus additional front ends then it isn't apparent which
- ones you built unless you tell us about it.
+ * Whether you enabled all languages or a subset of them. If you
+ used a full distribution then this information is part of the
+ configure options in the output of `gcc -v', but if you downloaded
+ the "core" compiler plus additional front ends then it isn't
+ apparent which ones you built unless you tell us about it.
* If the build was for GNU/Linux, also include:
- * The distribution name and version (e.g., Red Hat 7.1 or Debian
- 2.2.3); this information should be available from
- '/etc/issue'.
+ * The distribution name and version (e.g., Red Hat 7.1 or
+ Debian 2.2.3); this information should be available from
+ `/etc/issue'.
- * The version of the Linux kernel, available from 'uname
- --version' or 'uname -a'.
+ * The version of the Linux kernel, available from `uname
+ --version' or `uname -a'.
* The version of glibc you used; for RPM-based systems like Red
- Hat, Mandrake, and SuSE type 'rpm -q glibc' to get the glibc
- version, and on systems like Debian and Progeny use 'dpkg -l
+ Hat, Mandrake, and SuSE type `rpm -q glibc' to get the glibc
+ version, and on systems like Debian and Progeny use `dpkg -l
libc6'.
- For other systems, you can include similar information if you think
- it is relevant.
+ For other systems, you can include similar information if you
+ think it is relevant.
* Any other information that you think would be useful to people
- building GCC on the same configuration. The new entry in the build
- status list will include a link to the archived copy of your
+ building GCC on the same configuration. The new entry in the
+ build status list will include a link to the archived copy of your
message.
- We'd also like to know if the *note host/target specific installation
-notes: Specific. didn't include your host/target information or if that
-information is incomplete or out of date. Send a note to
-<gcc@gcc.gnu.org> detailing how the information should be changed.
+ We'd also like to know if the *note host/target specific
+installation notes: Specific. didn't include your host/target
+information or if that information is incomplete or out of date. Send
+a note to <gcc@gcc.gnu.org> detailing how the information should be
+changed.
If you find a bug, please report it following the bug reporting
guidelines.
- If you want to print the GCC manuals, do 'cd OBJDIR; make dvi'. You
-will need to have 'texi2dvi' (version at least 4.7) and TeX installed.
-This creates a number of '.dvi' files in subdirectories of 'OBJDIR';
-these may be converted for printing with programs such as 'dvips'.
-Alternately, by using 'make pdf' in place of 'make dvi', you can create
-documentation in the form of '.pdf' files; this requires 'texi2pdf',
+ If you want to print the GCC manuals, do `cd OBJDIR; make dvi'. You
+will need to have `texi2dvi' (version at least 4.7) and TeX installed.
+This creates a number of `.dvi' files in subdirectories of `OBJDIR';
+these may be converted for printing with programs such as `dvips'.
+Alternately, by using `make pdf' in place of `make dvi', you can create
+documentation in the form of `.pdf' files; this requires `texi2pdf',
which is included with Texinfo version 4.8 and later. You can also buy
printed manuals from the Free Software Foundation, though such manuals
may not be for the most recent version of GCC.
- If you would like to generate online HTML documentation, do 'cd
+ If you would like to generate online HTML documentation, do `cd
OBJDIR; make html' and HTML will be generated for the gcc manuals in
-'OBJDIR/gcc/HTML'.
+`OBJDIR/gcc/HTML'.

File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC, Up: Top
@@ -2722,10 +2765,10 @@ File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC,
8 Installing GCC: Binaries
**************************
-We are often asked about pre-compiled versions of GCC. While we cannot
-provide these for all platforms, below you'll find links to binaries for
-various platforms where creating them by yourself is not easy due to
-various reasons.
+ We are often asked about pre-compiled versions of GCC. While we
+cannot provide these for all platforms, below you'll find links to
+binaries for various platforms where creating them by yourself is not
+easy due to various reasons.
Please note that we did not create these binaries, nor do we support
them. If you have any problems installing them, please contact their
@@ -2758,6 +2801,7 @@ makers.
* Microsoft Windows:
* The Cygwin project;
+
* The MinGW project.
* The Written Word offers binaries for AIX 4.3.3, 5.1 and 5.2,
@@ -2775,8 +2819,8 @@ File: gccinstall.info, Node: Specific, Next: Old, Prev: Binaries, Up: Top
9 Host/target specific installation notes for GCC
*************************************************
-Please read this document carefully _before_ installing the GNU Compiler
-Collection on your machine.
+ Please read this document carefully _before_ installing the GNU
+Compiler Collection on your machine.
Note that this list of install notes is _not_ a list of supported
hosts or targets. Not all supported hosts and targets are listed here,
@@ -2786,20 +2830,31 @@ have to.
aarch64*-*-*
============
-Binutils pre 2.24 does not have support for selecting '-mabi' and does
+Binutils pre 2.24 does not have support for selecting `-mabi' and does
not support ILP32. If it is used to build GCC 4.9 or later, GCC will
-not support option '-mabi=ilp32'.
+not support option `-mabi=ilp32'.
To enable a workaround for the Cortex-A53 erratum number 835769 by
default (for all CPUs regardless of -mcpu option given) at configure
-time use the '--enable-fix-cortex-a53-835769' option. This will enable
-the fix by default and can be explicitly disabled during during
-compilation by passing the '-mno-fix-cortex-a53-835769' option.
-Conversely, '--disable-fix-cortex-a53-835769' will disable the
-workaround by default. The workaround is disabled by default if neither
-of '--enable-fix-cortex-a53-835769' or '--disable-fix-cortex-a53-835769'
+time use the `--enable-fix-cortex-a53-835769' option. This will enable
+the fix by default and can be explicitly disabled during compilation by
+passing the `-mno-fix-cortex-a53-835769' option. Conversely,
+`--disable-fix-cortex-a53-835769' will disable the workaround by
+default. The workaround is disabled by default if neither of
+`--enable-fix-cortex-a53-835769' or `--disable-fix-cortex-a53-835769'
is given at configure time.
+ To enable a workaround for the Cortex-A53 erratum number 843419 by
+default (for all CPUs regardless of -mcpu option given) at configure
+time use the `--enable-fix-cortex-a53-843419' option. This workaround
+is applied at link time. Enabling the workaround will cause GCC to
+pass the relevant option to the linker. It can be explicitly disabled
+during compilation by passing the `-mno-fix-cortex-a53-843419' option.
+Conversely, `--disable-fix-cortex-a53-843419' will disable the
+workaround by default. The workaround is disabled by default if
+neither of `--enable-fix-cortex-a53-843419' or
+`--disable-fix-cortex-a53-843419' is given at configure time.
+
alpha*-*-*
==========
@@ -2822,25 +2877,25 @@ systems.
Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC
4.6, support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC
-3.2, versions before 'alpha*-dec-osf4' are no longer supported. (These
+3.2, versions before `alpha*-dec-osf4' are no longer supported. (These
are the versions which identify themselves as DEC OSF/1.)
amd64-*-solaris2.1[0-9]*
========================
-This is a synonym for 'x86_64-*-solaris2.1[0-9]*'.
+This is a synonym for `x86_64-*-solaris2.1[0-9]*'.
arc-*-elf32
===========
-Use 'configure --target=arc-elf32 --with-cpu=CPU
+Use `configure --target=arc-elf32 --with-cpu=CPU
--enable-languages="c,c++"' to configure GCC, with CPU being one of
-'arc600', 'arc601', or 'arc700'.
+`arc600', `arc601', or `arc700'.
arc-linux-uclibc
================
-Use 'configure --target=arc-linux-uclibc --with-cpu=arc700
+Use `configure --target=arc-linux-uclibc --with-cpu=arc700
--enable-languages="c,c++"' to configure GCC.
arm-*-eabi
@@ -2848,7 +2903,7 @@ arm-*-eabi
ARM-family processors. Subtargets that use the ELF object format
require GNU binutils 2.13 or newer. Such subtargets include:
-'arm-*-netbsdelf', 'arm-*-*linux-*' and 'arm-*-rtemseabi'.
+`arm-*-netbsdelf', `arm-*-*linux-*' and `arm-*-rtemseabi'.
avr
===
@@ -2857,12 +2912,13 @@ ATMEL AVR-family micro controllers. These are used in embedded
applications. There are no standard Unix configurations. *Note AVR
Options: (gcc)AVR Options, for the list of supported MCU types.
- Use 'configure --target=avr --enable-languages="c"' to configure GCC.
+ Use `configure --target=avr --enable-languages="c"' to configure GCC.
Further installation notes and other useful information about AVR
tools can also be obtained from:
* http://www.nongnu.org/avr/
+
* http://www.amelek.gda.pl/avr/
We _strongly_ recommend using binutils 2.13 or newer.
@@ -2875,24 +2931,24 @@ tools can also be obtained from:
Blackfin
========
-The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options:
+The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options:
(gcc)Blackfin Options,
More information, and a version of binutils with support for this
-processor, is available at <http://blackfin.uclinux.org>
+processor, is available at `http://blackfin.uclinux.org'
CR16
====
-The CR16 CompactRISC architecture is a 16-bit architecture. This
+The CR16 CompactRISC architecture is a 16-bit architecture. This
architecture is used in embedded applications.
*Note CR16 Options: (gcc)CR16 Options,
- Use 'configure --target=cr16-elf --enable-languages=c,c++' to
+ Use `configure --target=cr16-elf --enable-languages=c,c++' to
configure GCC for building a CR16 elf cross-compiler.
- Use 'configure --target=cr16-uclinux --enable-languages=c,c++' to
+ Use `configure --target=cr16-uclinux --enable-languages=c,c++' to
configure GCC for building a CR16 uclinux cross-compiler.
CRIS
@@ -2905,20 +2961,21 @@ system-on-a-chip series. These are used in embedded applications.
options.
There are a few different CRIS targets:
-'cris-axis-elf'
+`cris-axis-elf'
Mainly for monolithic embedded systems. Includes a multilib for
- the 'v10' core used in 'ETRAX 100 LX'.
-'cris-axis-linux-gnu'
+ the `v10' core used in `ETRAX 100 LX'.
+
+`cris-axis-linux-gnu'
A GNU/Linux port for the CRIS architecture, currently targeting
- 'ETRAX 100 LX' by default.
+ `ETRAX 100 LX' by default.
- For 'cris-axis-elf' you need binutils 2.11 or newer. For
-'cris-axis-linux-gnu' you need binutils 2.12 or newer.
+ For `cris-axis-elf' you need binutils 2.11 or newer. For
+`cris-axis-linux-gnu' you need binutils 2.12 or newer.
Pre-packaged tools can be obtained from
-<ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/>. More
+`ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/'. More
information about this platform is available at
-<http://developer.axis.com/>.
+`http://developer.axis.com/'.
DOS
===
@@ -2945,30 +3002,31 @@ Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD
In order to better utilize FreeBSD base system functionality and
match the configuration of the system compiler, GCC 4.5 and above as
well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is
-present on FreeBSD 7 or later) and the use of '__cxa_atexit' by default
-(on FreeBSD 6 or later). The use of 'dl_iterate_phdr' inside
-'libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC
+present on FreeBSD 7 or later) and the use of `__cxa_atexit' by default
+(on FreeBSD 6 or later). The use of `dl_iterate_phdr' inside
+`libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC
4.5 and above.
We support FreeBSD using the ELF file format with DWARF 2 debugging
-for all CPU architectures. You may use '-gstabs' instead of '-g', if
+for all CPU architectures. You may use `-gstabs' instead of `-g', if
you really want the old debugging format. There are no known issues
-with mixing object files and libraries with different debugging formats.
-Otherwise, this release of GCC should now match more of the
+with mixing object files and libraries with different debugging
+formats. Otherwise, this release of GCC should now match more of the
configuration used in the stock FreeBSD configuration of GCC. In
-particular, '--enable-threads' is now configured by default. However,
+particular, `--enable-threads' is now configured by default. However,
as a general user, do not attempt to replace the system compiler with
-this release. Known to bootstrap and check with good results on FreeBSD
-7.2-STABLE. In the past, known to bootstrap and check with good results
-on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and 5-CURRENT.
+this release. Known to bootstrap and check with good results on
+FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with
+good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and
+5-CURRENT.
- The version of binutils installed in '/usr/bin' probably works with
+ The version of binutils installed in `/usr/bin' probably works with
this release of GCC. Bootstrapping against the latest GNU binutils
-and/or the version found in '/usr/ports/devel/binutils' has been known
+and/or the version found in `/usr/ports/devel/binutils' has been known
to enable additional features and improve overall testsuite results.
However, it is currently known that boehm-gc (which itself is required
-for java) may not configure properly on FreeBSD prior to the FreeBSD 7.0
-release with GNU binutils after 2.16.1.
+for java) may not configure properly on FreeBSD prior to the FreeBSD
+7.0 release with GNU binutils after 2.16.1.
h8300-hms
=========
@@ -2990,18 +3048,18 @@ Support for HP-UX version 9 and older was discontinued in GCC 3.4.
We require using gas/binutils on all hppa platforms. Version 2.19 or
later is recommended.
- It may be helpful to configure GCC with the '--with-gnu-as' and
-'--with-as=...' options to ensure that GCC can find GAS.
+ It may be helpful to configure GCC with the `--with-gnu-as' and
+`--with-as=...' options to ensure that GCC can find GAS.
- The HP assembler should not be used with GCC. It is rarely tested and
-may not work. It shouldn't be used with any languages other than C due
-to its many limitations.
+ The HP assembler should not be used with GCC. It is rarely tested
+and may not work. It shouldn't be used with any languages other than C
+due to its many limitations.
- Specifically, '-g' does not work (HP-UX uses a peculiar debugging
+ Specifically, `-g' does not work (HP-UX uses a peculiar debugging
format which GCC does not know about). It also inserts timestamps into
-each object file it creates, causing the 3-stage comparison test to fail
-during a bootstrap. You should be able to continue by saying 'make
-all-host all-target' after getting the failure from 'make'.
+each object file it creates, causing the 3-stage comparison test to
+fail during a bootstrap. You should be able to continue by saying
+`make all-host all-target' after getting the failure from `make'.
Various GCC features are not supported. For example, it does not
support weak symbols or alias definitions. As a result, explicit
@@ -3012,7 +3070,7 @@ difficult if not impossible to build many C++ applications.
PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
architecture specified for the target machine when configuring.
PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the
-target is a 'hppa1*' machine.
+target is a `hppa1*' machine.
The PROCESSOR_8000 model is not well suited to older processors.
Thus, it is important to completely specify the machine architecture
@@ -3020,23 +3078,23 @@ when configuring if you want a model other than PROCESSOR_8000. The
macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
default scheduling model is desired.
- As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 through
-11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. This
-namespace change might cause problems when bootstrapping with an earlier
-version of GCC or the HP compiler as essentially the same namespace is
-required for an entire build. This problem can be avoided in a number
-of ways. With HP cc, 'UNIX_STD' can be set to '95' or '98'. Another
-way is to add an appropriate set of predefines to 'CC'. The description
-for the 'munix=' option contains a list of the predefines used with each
-standard.
+ As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
+through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
+This namespace change might cause problems when bootstrapping with an
+earlier version of GCC or the HP compiler as essentially the same
+namespace is required for an entire build. This problem can be avoided
+in a number of ways. With HP cc, `UNIX_STD' can be set to `95' or
+`98'. Another way is to add an appropriate set of predefines to `CC'.
+The description for the `munix=' option contains a list of the
+predefines used with each standard.
- More specific information to 'hppa*-hp-hpux*' targets follows.
+ More specific information to `hppa*-hp-hpux*' targets follows.
hppa*-hp-hpux10
===============
For hpux10.20, we _highly_ recommend you pick up the latest sed patch
-'PHCO_19798' from HP.
+`PHCO_19798' from HP.
The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces
are used for one-only code and data. This resolves many of the previous
@@ -3050,13 +3108,13 @@ hppa*-hp-hpux11
GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
be used to compile GCC 3.0 and up.
- The libffi and libjava libraries haven't been ported to 64-bit
-HP-UX and don't build.
+ The libffi and libjava libraries haven't been ported to 64-bit HP-UX
+and don't build.
Refer to binaries for information about obtaining precompiled GCC
binaries for HP-UX. Precompiled binaries must be obtained to build the
-Ada language as it can't be bootstrapped using C. Ada is only available
-for the 32-bit PA-RISC runtime.
+Ada language as it can't be bootstrapped using C. Ada is only
+available for the 32-bit PA-RISC runtime.
Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
The bundled compiler supports only traditional C; you will need either
@@ -3067,7 +3125,7 @@ compiler, but the process requires several steps. GCC 3.3 can then be
used to build later versions. The fastjar program contains ISO C code
and can't be built with the HP bundled compiler. This problem can be
avoided by not building the Java language. For example, use the
-'--enable-languages="c,c++,f77,objc"' option in your configure command.
+`--enable-languages="c,c++,f77,objc"' option in your configure command.
There are several possible approaches to building the distribution.
Binutils can be built first using the HP tools. Then, the GCC
@@ -3078,79 +3136,79 @@ start from a binary distribution.
On 64-bit capable systems, there are two distinct targets. Different
installation prefixes must be used if both are to be installed on the
-same system. The 'hppa[1-2]*-hp-hpux11*' target generates code for the
+same system. The `hppa[1-2]*-hp-hpux11*' target generates code for the
32-bit PA-RISC runtime architecture and uses the HP linker. The
-'hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0
+`hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0
architecture.
The script config.guess now selects the target type based on the
-compiler detected during configuration. You must define 'PATH' or 'CC'
+compiler detected during configuration. You must define `PATH' or `CC'
so that configure finds an appropriate compiler for the initial
-bootstrap. When 'CC' is used, the definition should contain the options
-that are needed whenever 'CC' is used.
+bootstrap. When `CC' is used, the definition should contain the
+options that are needed whenever `CC' is used.
Specifically, options that determine the runtime architecture must be
-in 'CC' to correctly select the target for the build. It is also
-convenient to place many other compiler options in 'CC'. For example,
-'CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can be
-used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit
-K&R/bundled mode. The '+DA2.0W' option will result in the automatic
-selection of the 'hppa64-hp-hpux11*' target. The macro definition table
-of cpp needs to be increased for a successful build with the HP
+in `CC' to correctly select the target for the build. It is also
+convenient to place many other compiler options in `CC'. For example,
+`CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can
+be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit
+K&R/bundled mode. The `+DA2.0W' option will result in the automatic
+selection of the `hppa64-hp-hpux11*' target. The macro definition
+table of cpp needs to be increased for a successful build with the HP
compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when
-building with the bundled compiler, or when using the '-Ac' option.
-These defines aren't necessary with '-Ae'.
+building with the bundled compiler, or when using the `-Ac' option.
+These defines aren't necessary with `-Ae'.
- It is best to explicitly configure the 'hppa64-hp-hpux11*' target
-with the '--with-ld=...' option. This overrides the standard search for
-ld. The two linkers supported on this target require different
+ It is best to explicitly configure the `hppa64-hp-hpux11*' target
+with the `--with-ld=...' option. This overrides the standard search
+for ld. The two linkers supported on this target require different
commands. The default linker is determined during configuration. As a
result, it's not possible to switch linkers in the middle of a GCC
build. This has been reported to sometimes occur in unified builds of
binutils and GCC.
A recent linker patch must be installed for the correct operation of
-GCC 3.3 and later. 'PHSS_26559' and 'PHSS_24304' are the oldest linker
+GCC 3.3 and later. `PHSS_26559' and `PHSS_24304' are the oldest linker
patches that are known to work. They are for HP-UX 11.00 and 11.11,
-respectively. 'PHSS_24303', the companion to 'PHSS_24304', might be
+respectively. `PHSS_24303', the companion to `PHSS_24304', might be
usable but it hasn't been tested. These patches have been superseded.
-Consult the HP patch database to obtain the currently recommended linker
-patch for your system.
+Consult the HP patch database to obtain the currently recommended
+linker patch for your system.
The patches are necessary for the support of weak symbols on the
32-bit port, and for the running of initializers and finalizers. Weak
symbols are implemented using SOM secondary definition symbols. Prior
to HP-UX 11, there are bugs in the linker support for secondary symbols.
The patches correct a problem of linker core dumps creating shared
-libraries containing secondary symbols, as well as various other linking
-issues involving secondary symbols.
+libraries containing secondary symbols, as well as various other
+linking issues involving secondary symbols.
GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
run initializers and finalizers on the 64-bit port. The 32-bit port
-uses the linker '+init' and '+fini' options for the same purpose. The
-patches correct various problems with the +init/+fini options, including
-program core dumps. Binutils 2.14 corrects a problem on the 64-bit port
-resulting from HP's non-standard use of the .init and .fini sections for
-array initializers and finalizers.
+uses the linker `+init' and `+fini' options for the same purpose. The
+patches correct various problems with the +init/+fini options,
+including program core dumps. Binutils 2.14 corrects a problem on the
+64-bit port resulting from HP's non-standard use of the .init and .fini
+sections for array initializers and finalizers.
Although the HP and GNU linkers are both supported for the
-'hppa64-hp-hpux11*' target, it is strongly recommended that the HP
+`hppa64-hp-hpux11*' target, it is strongly recommended that the HP
linker be used for link editing on this target.
At this time, the GNU linker does not support the creation of long
branch stubs. As a result, it can't successfully link binaries
containing branch offsets larger than 8 megabytes. In addition, there
are problems linking shared libraries, linking executables with
-'-static', and with dwarf2 unwind and exception support. It also
+`-static', and with dwarf2 unwind and exception support. It also
doesn't provide stubs for internal calls to global functions in shared
libraries, so these calls can't be overloaded.
The HP dynamic loader does not support GNU symbol versioning, so
symbol versioning is not supported. It may be necessary to disable
-symbol versioning with '--disable-symvers' when using GNU ld.
+symbol versioning with `--disable-symvers' when using GNU ld.
POSIX threads are the default. The optional DCE thread library is
-not supported, so '--enable-threads=dce' does not work.
+not supported, so `--enable-threads=dce' does not work.
*-*-linux-gnu
=============
@@ -3173,57 +3231,57 @@ i?86-*-solaris2.10
==================
Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
-with GCC 4.7, there is also a 64-bit 'amd64-*-solaris2.1[0-9]*' or
-'x86_64-*-solaris2.1[0-9]*' configuration that corresponds to
-'sparcv9-sun-solaris2*'.
+with GCC 4.7, there is also a 64-bit `amd64-*-solaris2.1[0-9]*' or
+`x86_64-*-solaris2.1[0-9]*' configuration that corresponds to
+`sparcv9-sun-solaris2*'.
It is recommended that you configure GCC to use the GNU assembler, in
-'/usr/sfw/bin/gas'. The versions included in Solaris 10, from GNU
+`/usr/sfw/bin/gas'. The versions included in Solaris 10, from GNU
binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
although the current version, from GNU binutils 2.22, is known to work,
-too. Recent versions of the Sun assembler in '/usr/ccs/bin/as' work
+too. Recent versions of the Sun assembler in `/usr/ccs/bin/as' work
almost as well, though.
For linking, the Sun linker, is preferred. If you want to use the
-GNU linker instead, which is available in '/usr/sfw/bin/gld', note that
+GNU linker instead, which is available in `/usr/sfw/bin/gld', note that
due to a packaging bug the version in Solaris 10, from GNU binutils
2.15, cannot be used, while the version in Solaris 11, from GNU binutils
2.19, works, as does the latest version, from GNU binutils 2.22.
- To use GNU 'as', configure with the options '--with-gnu-as
+ To use GNU `as', configure with the options `--with-gnu-as
--with-as=/usr/sfw/bin/gas'. It may be necessary to configure with
-'--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun
-'ld'.
+`--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun
+`ld'.
ia64-*-linux
============
-IA-64 processor (also known as IPF, or Itanium Processor Family) running
-GNU/Linux.
+IA-64 processor (also known as IPF, or Itanium Processor Family)
+running GNU/Linux.
If you are using the installed system libunwind library with
-'--with-system-libunwind', then you must use libunwind 0.98 or later.
+`--with-system-libunwind', then you must use libunwind 0.98 or later.
None of the following versions of GCC has an ABI that is compatible
-with any of the other versions in this list, with the exception that Red
-Hat 2.96 and Trillian 000171 are compatible with each other: 3.1, 3.0.2,
-3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily affects
-C++ programs and programs that create shared libraries. GCC 3.1 or
-later is recommended for compiling linux, the kernel. As of version 3.1
-GCC is believed to be fully ABI compliant, and hence no more major ABI
-changes are expected.
+with any of the other versions in this list, with the exception that
+Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.1,
+3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily
+affects C++ programs and programs that create shared libraries. GCC
+3.1 or later is recommended for compiling linux, the kernel. As of
+version 3.1 GCC is believed to be fully ABI compliant, and hence no
+more major ABI changes are expected.
ia64-*-hpux*
============
Building GCC on this target requires the GNU Assembler. The bundled HP
assembler will not work. To prevent GCC from using the wrong assembler,
-the option '--with-gnu-as' may be necessary.
+the option `--with-gnu-as' may be necessary.
The GCC libunwind library has not been ported to HPUX. This means
-that for GCC versions 3.2.3 and earlier, '--enable-libunwind-exceptions'
+that for GCC versions 3.2.3 and earlier, `--enable-libunwind-exceptions'
is required to build GCC. For GCC 3.3 and later, this is the default.
-For gcc 3.4.3 and later, '--enable-libunwind-exceptions' is removed and
+For gcc 3.4.3 and later, `--enable-libunwind-exceptions' is removed and
the system libunwind library will always be used.
*-ibm-aix*
@@ -3234,7 +3292,7 @@ Support for AIX version 4.2 and older was discontinued in GCC 4.5.
"out of memory" bootstrap failures may indicate a problem with
process resource limits (ulimit). Hard limits are configured in the
-'/etc/security/limits' system configuration file.
+`/etc/security/limits' system configuration file.
GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
with an earlier release of GCC is recommended. Bootstrapping with XLC
@@ -3245,11 +3303,11 @@ LDR_CNTRL environment variable, e.g.,
% export LDR_CNTRL
One can start with a pre-compiled version of GCC to build from
-sources. One may delete GCC's "fixed" header files when starting with a
-version of GCC built for an earlier release of AIX.
+sources. One may delete GCC's "fixed" header files when starting with
+a version of GCC built for an earlier release of AIX.
To speed up the configuration phases of bootstrapping and installing
-GCC, one may use GNU Bash instead of AIX '/bin/sh', e.g.,
+GCC, one may use GNU Bash instead of AIX `/bin/sh', e.g.,
% CONFIG_SHELL=/opt/freeware/bin/bash
% export CONFIG_SHELL
@@ -3260,20 +3318,20 @@ SRCDIR/configure.
Because GCC on AIX is built as a 32-bit executable by default,
(although it can generate 64-bit programs) the GMP and MPFR libraries
-required by gfortran must be 32-bit libraries. Building GMP and MPFR as
-static archive libraries works better than shared libraries.
+required by gfortran must be 32-bit libraries. Building GMP and MPFR
+as static archive libraries works better than shared libraries.
- Errors involving 'alloca' when building GCC generally are due to an
-incorrect definition of 'CC' in the Makefile or mixing files compiled
+ Errors involving `alloca' when building GCC generally are due to an
+incorrect definition of `CC' in the Makefile or mixing files compiled
with the native C compiler and GCC. During the stage1 phase of the
-build, the native AIX compiler *must* be invoked as 'cc' (not 'xlc').
-Once 'configure' has been informed of 'xlc', one needs to use 'make
-distclean' to remove the configure cache files and ensure that 'CC'
+build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
+Once `configure' has been informed of `xlc', one needs to use `make
+distclean' to remove the configure cache files and ensure that `CC'
environment variable does not provide a definition that will confuse
-'configure'. If this error occurs during stage2 or later, then the
+`configure'. If this error occurs during stage2 or later, then the
problem most likely is the version of Make (see above).
- The native 'as' and 'ld' are recommended for bootstrapping on AIX.
+ The native `as' and `ld' are recommended for bootstrapping on AIX.
The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the
minimum level that supports bootstrap on AIX 5. The GNU Assembler has
not been updated to support AIX 6 or AIX 7. The native AIX tools do
@@ -3284,39 +3342,39 @@ assembler change that sometimes produces corrupt assembly files causing
AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause
compilation failures with existing GCC installations. An AIX iFix for
AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR IZ98477 for
-AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3
-TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX 6.1
-TL07 and AIX 7.1 TL01 should include the fix.
+AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3
+TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX
+6.1 TL07 and AIX 7.1 TL01 should include the fix.
- Building 'libstdc++.a' requires a fix for an AIX Assembler bug APAR
-IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix for
-another AIX Assembler bug and a co-dependent AIX Archiver fix referenced
-as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
+ Building `libstdc++.a' requires a fix for an AIX Assembler bug APAR
+IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix
+for another AIX Assembler bug and a co-dependent AIX Archiver fix
+referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
- 'libstdc++' in GCC 3.4 increments the major version number of the
-shared object and GCC installation places the 'libstdc++.a' shared
+ `libstdc++' in GCC 3.4 increments the major version number of the
+shared object and GCC installation places the `libstdc++.a' shared
library in a common location which will overwrite the and GCC 3.3
-version of the shared library. Applications either need to be re-linked
-against the new shared library or the GCC 3.1 and GCC 3.3 versions of
-the 'libstdc++' shared object needs to be available to the AIX runtime
-loader. The GCC 3.1 'libstdc++.so.4', if present, and GCC 3.3
-'libstdc++.so.5' shared objects can be installed for runtime dynamic
-loading using the following steps to set the 'F_LOADONLY' flag in the
-shared object for _each_ multilib 'libstdc++.a' installed:
-
- Extract the shared objects from the currently installed 'libstdc++.a'
-archive:
+version of the shared library. Applications either need to be
+re-linked against the new shared library or the GCC 3.1 and GCC 3.3
+versions of the `libstdc++' shared object needs to be available to the
+AIX runtime loader. The GCC 3.1 `libstdc++.so.4', if present, and GCC
+3.3 `libstdc++.so.5' shared objects can be installed for runtime
+dynamic loading using the following steps to set the `F_LOADONLY' flag
+in the shared object for _each_ multilib `libstdc++.a' installed:
+
+ Extract the shared objects from the currently installed
+`libstdc++.a' archive:
% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
- Enable the 'F_LOADONLY' flag so that the shared object will be
+ Enable the `F_LOADONLY' flag so that the shared object will be
available for runtime dynamic loading, but not linking:
% strip -e libstdc++.so.4 libstdc++.so.5
- Archive the runtime-only shared object in the GCC 3.4 'libstdc++.a'
+ Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a'
archive:
% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
- Eventually, the '--with-aix-soname=svr4' configure option may drop
+ Eventually, the `--with-aix-soname=svr4' configure option may drop
the need for this procedure for libraries that support it.
Linking executables and shared libraries may produce warnings of
@@ -3331,13 +3389,13 @@ executable.
to parse archive libraries did not handle the new format correctly.
These routines are used by GCC and result in error messages during
linking such as "not a COFF file". The version of the routines shipped
-with AIX 4.3.1 should work for a 32-bit environment. The '-g' option of
-the archive command may be used to create archives of 32-bit objects
-using the original "small format". A correct version of the routines is
-shipped with AIX 4.3.2 and above.
+with AIX 4.3.1 should work for a 32-bit environment. The `-g' option
+of the archive command may be used to create archives of 32-bit objects
+using the original "small format". A correct version of the routines
+is shipped with AIX 4.3.2 and above.
Some versions of the AIX binder (linker) can fail with a relocation
-overflow severe error when the '-bbigtoc' option is used to link
+overflow severe error when the `-bbigtoc' option is used to link
GCC-produced object files into an executable that overflows the TOC. A
fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC)
is available from IBM Customer Support and from its
@@ -3356,15 +3414,15 @@ and from its techsupport.services.ibm.com website as PTF U453956. This
fix is incorporated in AIX 4.3.1 and above.
AIX provides National Language Support (NLS). Compilers and
-assemblers use NLS to support locale-specific representations of various
-data formats including floating-point numbers (e.g., '.' vs ',' for
-separating decimal fractions). There have been problems reported where
-GCC does not produce the same floating-point formats that the assembler
-expects. If one encounters this problem, set the 'LANG' environment
-variable to 'C' or 'En_US'.
+assemblers use NLS to support locale-specific representations of
+various data formats including floating-point numbers (e.g., `.' vs
+`,' for separating decimal fractions). There have been problems
+reported where GCC does not produce the same floating-point formats
+that the assembler expects. If one encounters this problem, set the
+`LANG' environment variable to `C' or `En_US'.
- A default can be specified with the '-mcpu=CPU_TYPE' switch and using
-the configure option '--with-cpu-CPU_TYPE'.
+ A default can be specified with the `-mcpu=CPU_TYPE' switch and
+using the configure option `--with-cpu-CPU_TYPE'.
iq2000-*-elf
============
@@ -3399,22 +3457,23 @@ systems.
m68k-*-*
========
-By default, 'm68k-*-elf*', 'm68k-*-rtems', 'm68k-*-uclinux' and
-'m68k-*-linux' build libraries for both M680x0 and ColdFire processors.
-If you only need the M680x0 libraries, you can omit the ColdFire ones by
-passing '--with-arch=m68k' to 'configure'. Alternatively, you can omit
-the M680x0 libraries by passing '--with-arch=cf' to 'configure'. These
-targets default to 5206 or 5475 code as appropriate for the target
-system when configured with '--with-arch=cf' and 68020 code otherwise.
+By default, `m68k-*-elf*', `m68k-*-rtems', `m68k-*-uclinux' and
+`m68k-*-linux' build libraries for both M680x0 and ColdFire processors.
+If you only need the M680x0 libraries, you can omit the ColdFire ones
+by passing `--with-arch=m68k' to `configure'. Alternatively, you can
+omit the M680x0 libraries by passing `--with-arch=cf' to `configure'.
+These targets default to 5206 or 5475 code as appropriate for the
+target system when configured with `--with-arch=cf' and 68020 code
+otherwise.
- The 'm68k-*-netbsd' and 'm68k-*-openbsd' targets also support the
-'--with-arch' option. They will generate ColdFire CFV4e code when
-configured with '--with-arch=cf' and 68020 code otherwise.
+ The `m68k-*-netbsd' and `m68k-*-openbsd' targets also support the
+`--with-arch' option. They will generate ColdFire CFV4e code when
+configured with `--with-arch=cf' and 68020 code otherwise.
You can override the default processors listed above by configuring
-with '--with-cpu=TARGET'. This TARGET can either be a '-mcpu' argument
-or one of the following values: 'm68000', 'm68010', 'm68020', 'm68030',
-'m68040', 'm68060', 'm68020-40' and 'm68020-60'.
+with `--with-cpu=TARGET'. This TARGET can either be a `-mcpu' argument
+or one of the following values: `m68000', `m68010', `m68020', `m68030',
+`m68040', `m68060', `m68020-40' and `m68020-60'.
GCC requires at least binutils version 2.17 on these targets.
@@ -3422,7 +3481,7 @@ m68k-*-uclinux
==============
GCC 4.3 changed the uClinux configuration so that it uses the
-'m68k-linux-gnu' ABI rather than the 'm68k-elf' ABI. It also added
+`m68k-linux-gnu' ABI rather than the `m68k-elf' ABI. It also added
improved support for C++ and flat shared libraries, both of which were
ABI changes.
@@ -3452,36 +3511,36 @@ optional, and there should not be a warning about their absence.
The libstdc++ atomic locking routines for MIPS targets requires MIPS
II and later. A patch went in just after the GCC 3.3 release to make
-'mips*-*-*' use the generic implementation instead. You can also
-configure for 'mipsel-elf' as a workaround. The 'mips*-*-linux*' target
-continues to use the MIPS II routines. More work on this is expected in
-future releases.
-
- The built-in '__sync_*' functions are available on MIPS II and later
-systems and others that support the 'll', 'sc' and 'sync' instructions.
-This can be overridden by passing '--with-llsc' or '--without-llsc' when
-configuring GCC. Since the Linux kernel emulates these instructions if
-they are missing, the default for 'mips*-*-linux*' targets is
-'--with-llsc'. The '--with-llsc' and '--without-llsc' configure options
-may be overridden at compile time by passing the '-mllsc' or '-mno-llsc'
-options to the compiler.
+`mips*-*-*' use the generic implementation instead. You can also
+configure for `mipsel-elf' as a workaround. The `mips*-*-linux*'
+target continues to use the MIPS II routines. More work on this is
+expected in future releases.
+
+ The built-in `__sync_*' functions are available on MIPS II and later
+systems and others that support the `ll', `sc' and `sync' instructions.
+This can be overridden by passing `--with-llsc' or `--without-llsc'
+when configuring GCC. Since the Linux kernel emulates these
+instructions if they are missing, the default for `mips*-*-linux*'
+targets is `--with-llsc'. The `--with-llsc' and `--without-llsc'
+configure options may be overridden at compile time by passing the
+`-mllsc' or `-mno-llsc' options to the compiler.
MIPS systems check for division by zero (unless
-'-mno-check-zero-division' is passed to the compiler) by generating
-either a conditional trap or a break instruction. Using trap results in
-smaller code, but is only supported on MIPS II and later. Also, some
-versions of the Linux kernel have a bug that prevents trap from
-generating the proper signal ('SIGFPE'). To enable the use of break,
-use the '--with-divide=breaks' 'configure' option when configuring GCC.
+`-mno-check-zero-division' is passed to the compiler) by generating
+either a conditional trap or a break instruction. Using trap results
+in smaller code, but is only supported on MIPS II and later. Also,
+some versions of the Linux kernel have a bug that prevents trap from
+generating the proper signal (`SIGFPE'). To enable the use of break,
+use the `--with-divide=breaks' `configure' option when configuring GCC.
The default is to use traps on systems that support them.
The assembler from GNU binutils 2.17 and earlier has a bug in the way
-it sorts relocations for REL targets (o32, o64, EABI). This can cause
+it sorts relocations for REL targets (o32, o64, EABI). This can cause
bad code to be generated for simple C++ programs. Also the linker from
GNU binutils versions prior to 2.17 has a bug which causes the runtime
-linker stubs in very large programs, like 'libgcj.so', to be incorrectly
-generated. GNU Binutils 2.18 and later (and snapshots made after Nov.
-9, 2006) should be free from both of these problems.
+linker stubs in very large programs, like `libgcj.so', to be
+incorrectly generated. GNU Binutils 2.18 and later (and snapshots made
+after Nov. 9, 2006) should be free from both of these problems.
mips-sgi-irix5
==============
@@ -3523,21 +3582,21 @@ Nvidia PTX target.
Instead of GNU binutils, you will need to install nvptx-tools. Tell
GCC where to find it:
-'--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin'.
+`--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin'.
A nvptx port of newlib is available at nvptx-newlib. It can be
-automatically built together with GCC. For this, add a symbolic link to
-nvptx-newlib's 'newlib' directory to the directory containing the GCC
-sources.
+automatically built together with GCC. For this, add a symbolic link
+to nvptx-newlib's `newlib' directory to the directory containing the
+GCC sources.
- Use the '--disable-sjlj-exceptions' and
-'--enable-newlib-io-long-long' options when configuring.
+ Use the `--disable-sjlj-exceptions' and
+`--enable-newlib-io-long-long' options when configuring.
powerpc-*-*
===========
-You can specify a default version for the '-mcpu=CPU_TYPE' switch by
-using the configure option '--with-cpu-CPU_TYPE'.
+You can specify a default version for the `-mcpu=CPU_TYPE' switch by
+using the configure option `--with-cpu-CPU_TYPE'.
You will need binutils 2.15 or newer for a working GCC.
@@ -3548,11 +3607,11 @@ PowerPC running Darwin (Mac OS X kernel).
Pre-installed versions of Mac OS X may not include any developer
tools, meaning that you will not be able to build GCC from source. Tool
-binaries are available at <http://opensource.apple.com/>.
+binaries are available at `http://opensource.apple.com/'.
This version of GCC requires at least cctools-590.36. The
cctools-590.36 package referenced from
-<http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html> will not work on
+`http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html' will not work on
systems older than 10.3.9 (aka darwin7.9.0).
powerpc-*-elf
@@ -3600,14 +3659,14 @@ Embedded PowerPC system in little endian mode.
rl78-*-elf
==========
-The Renesas RL78 processor. This configuration is intended for embedded
-systems.
+The Renesas RL78 processor. This configuration is intended for
+embedded systems.
rx-*-elf
========
The Renesas RX processor. See
-<http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series>
+`http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series'
for more information about this processor.
s390-*-linux*
@@ -3635,13 +3694,13 @@ in GCC 4.6.
Sun does not ship a C compiler with Solaris 2 before Solaris 10,
though you can download the Sun Studio compilers for free. In Solaris
-10 and 11, GCC 3.4.3 is available as '/usr/sfw/bin/gcc'. Solaris 11
-also provides GCC 4.5.2 as '/usr/gcc/4.5/bin/gcc'. Alternatively, you
-can install a pre-built GCC to bootstrap and install GCC. See the
+10 and 11, GCC 3.4.3 is available as `/usr/sfw/bin/gcc'. Solaris 11
+also provides GCC 4.5.2 as `/usr/gcc/4.5/bin/gcc'. Alternatively, you
+can install a pre-built GCC to bootstrap and install GCC. See the
binaries page for details.
- The Solaris 2 '/bin/sh' will often fail to configure 'libstdc++-v3',
-'boehm-gc' or 'libjava'. We therefore recommend using the following
+ The Solaris 2 `/bin/sh' will often fail to configure `libstdc++-v3',
+`boehm-gc' or `libjava'. We therefore recommend using the following
initial sequence of commands
% CONFIG_SHELL=/bin/ksh
@@ -3649,65 +3708,66 @@ initial sequence of commands
and proceed as described in the configure instructions. In addition we
strongly recommend specifying an absolute path to invoke
-'SRCDIR/configure'.
+`SRCDIR/configure'.
Solaris 2 comes with a number of optional OS packages. Some of these
-are needed to use GCC fully, namely 'SUNWarc', 'SUNWbtool', 'SUNWesu',
-'SUNWhea', 'SUNWlibm', 'SUNWsprot', and 'SUNWtoo'. If you did not
+are needed to use GCC fully, namely `SUNWarc', `SUNWbtool', `SUNWesu',
+`SUNWhea', `SUNWlibm', `SUNWsprot', and `SUNWtoo'. If you did not
install all optional packages when installing Solaris 2, you will need
to verify that the packages that GCC needs are installed.
- To check whether an optional package is installed, use the 'pkginfo'
-command. To add an optional package, use the 'pkgadd' command. For
+ To check whether an optional package is installed, use the `pkginfo'
+command. To add an optional package, use the `pkgadd' command. For
further details, see the Solaris 2 documentation.
- Trying to use the linker and other tools in '/usr/ucb' to install GCC
-has been observed to cause trouble. For example, the linker may hang
-indefinitely. The fix is to remove '/usr/ucb' from your 'PATH'.
+ Trying to use the linker and other tools in `/usr/ucb' to install
+GCC has been observed to cause trouble. For example, the linker may
+hang indefinitely. The fix is to remove `/usr/ucb' from your `PATH'.
The build process works more smoothly with the legacy Sun tools so,
-if you have '/usr/xpg4/bin' in your 'PATH', we recommend that you place
-'/usr/bin' before '/usr/xpg4/bin' for the duration of the build.
+if you have `/usr/xpg4/bin' in your `PATH', we recommend that you place
+`/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
We recommend the use of the Sun assembler or the GNU assembler, in
-conjunction with the Sun linker. The GNU 'as' versions included in
+conjunction with the Sun linker. The GNU `as' versions included in
Solaris 10, from GNU binutils 2.15, and Solaris 11, from GNU binutils
-2.19, are known to work. They can be found in '/usr/sfw/bin/gas'.
-Current versions of GNU binutils (2.22) are known to work as well. Note
-that your mileage may vary if you use a combination of the GNU tools and
-the Sun tools: while the combination GNU 'as' + Sun 'ld' should
-reasonably work, the reverse combination Sun 'as' + GNU 'ld' may fail to
-build or cause memory corruption at runtime in some cases for C++
-programs. GNU 'ld' usually works as well, although the version included
-in Solaris 10 cannot be used due to several bugs. Again, the current
-version (2.22) is known to work, but generally lacks platform specific
-features, so better stay with Sun 'ld'. To use the LTO linker plugin
-('-fuse-linker-plugin') with GNU 'ld', GNU binutils _must_ be configured
-with '--enable-largefile'.
-
- To enable symbol versioning in 'libstdc++' with Sun 'ld', you need to
-have any version of GNU 'c++filt', which is part of GNU binutils.
-'libstdc++' symbol versioning will be disabled if no appropriate version
-is found. Sun 'c++filt' from the Sun Studio compilers does _not_ work.
+2.19, are known to work. They can be found in `/usr/sfw/bin/gas'.
+Current versions of GNU binutils (2.22) are known to work as well.
+Note that your mileage may vary if you use a combination of the GNU
+tools and the Sun tools: while the combination GNU `as' + Sun `ld'
+should reasonably work, the reverse combination Sun `as' + GNU `ld' may
+fail to build or cause memory corruption at runtime in some cases for
+C++ programs. GNU `ld' usually works as well, although the version
+included in Solaris 10 cannot be used due to several bugs. Again, the
+current version (2.22) is known to work, but generally lacks platform
+specific features, so better stay with Sun `ld'. To use the LTO linker
+plugin (`-fuse-linker-plugin') with GNU `ld', GNU binutils _must_ be
+configured with `--enable-largefile'.
+
+ To enable symbol versioning in `libstdc++' with Sun `ld', you need
+to have any version of GNU `c++filt', which is part of GNU binutils.
+`libstdc++' symbol versioning will be disabled if no appropriate
+version is found. Sun `c++filt' from the Sun Studio compilers does
+_not_ work.
Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
-newer: 'g++' will complain that types are missing. These headers assume
-that omitting the type means 'int'; this assumption worked for C90 but
-is wrong for C++, and is now wrong for C99 also.
+newer: `g++' will complain that types are missing. These headers
+assume that omitting the type means `int'; this assumption worked for
+C90 but is wrong for C++, and is now wrong for C99 also.
Sun bug 4927647 sometimes causes random spurious testsuite failures
related to missing diagnostic output. This bug doesn't affect GCC
-itself, rather it is a kernel bug triggered by the 'expect' program
-which is used only by the GCC testsuite driver. When the bug causes the
-'expect' program to miss anticipated output, extra testsuite failures
-appear.
+itself, rather it is a kernel bug triggered by the `expect' program
+which is used only by the GCC testsuite driver. When the bug causes
+the `expect' program to miss anticipated output, extra testsuite
+failures appear.
sparc*-*-*
==========
This section contains general configuration information for all
-SPARC-based platforms. In addition to reading this section, please read
-all other sections that match your target.
+SPARC-based platforms. In addition to reading this section, please
+read all other sections that match your target.
Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
library and the MPC library are known to be miscompiled by earlier
@@ -3724,15 +3784,15 @@ this difference is quite significant for binaries containing debugging
information.
Starting with Solaris 7, the operating system is capable of executing
-64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this; the
-'-m64' option enables 64-bit code generation. However, if all you want
-is code tuned for the UltraSPARC CPU, you should try the
-'-mtune=ultrasparc' option instead, which produces code that, unlike
+64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this;
+the `-m64' option enables 64-bit code generation. However, if all you
+want is code tuned for the UltraSPARC CPU, you should try the
+`-mtune=ultrasparc' option instead, which produces code that, unlike
full 64-bit code, can still run on non-UltraSPARC machines.
When configuring on a Solaris 7 or later system that is running a
kernel that supports only 32-bit binaries, one must configure with
-'--disable-multilib', since we will not be able to build the 64-bit
+`--disable-multilib', since we will not be able to build the 64-bit
target libraries.
GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions
@@ -3743,32 +3803,32 @@ stage, i.e. to bootstrap that compiler with the base compiler and then
use it to bootstrap the final compiler.
GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE
-Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a
-bootstrap failure in form of a miscompilation of the stage1 compiler by
-the Sun compiler. This is Sun bug 4974440. This is fixed with patch
-112760-07.
+Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes
+a bootstrap failure in form of a miscompilation of the stage1 compiler
+by the Sun compiler. This is Sun bug 4974440. This is fixed with
+patch 112760-07.
GCC 3.4 changed the default debugging format from Stabs to DWARF-2
for 32-bit code on Solaris 7 and later. If you use the Sun assembler,
this change apparently runs afoul of Sun bug 4910101 (which is
referenced as an x86-only problem by Sun, probably because they do not
use DWARF-2). A symptom of the problem is that you cannot compile C++
-programs like 'groff' 1.19.1 without getting messages similar to the
+programs like `groff' 1.19.1 without getting messages similar to the
following:
ld: warning: relocation error: R_SPARC_UA32: ...
external symbolic relocation against non-allocatable section
.debug_info cannot be processed at runtime: relocation ignored.
-To work around this problem, compile with '-gstabs+' instead of plain
-'-g'.
+To work around this problem, compile with `-gstabs+' instead of plain
+`-g'.
When configuring the GNU Multiple Precision Library (GMP), the MPFR
library or the MPC library on a Solaris 7 or later system, the canonical
-target triplet must be specified as the 'build' parameter on the
+target triplet must be specified as the `build' parameter on the
configure line. This target triplet can be obtained by invoking
-'./config.guess' in the toplevel source directory of GCC (and not that
-of GMP or MPFR or MPC). For example on a Solaris 9 system:
+`./config.guess' in the toplevel source directory of GCC (and not that
+of GMP or MPFR or MPC). For example on a Solaris 9 system:
% ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
@@ -3776,7 +3836,7 @@ sparc-sun-solaris2.10
=====================
There is a bug in older versions of the Sun assembler which breaks
-thread-local storage (TLS). A typical error message is
+thread-local storage (TLS). A typical error message is
ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
symbol <unknown>: bad symbol type SECT: symbol type must be TLS
@@ -3788,14 +3848,14 @@ sparc-*-linux*
GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or
newer on this platform. All earlier binutils and glibc releases
-mishandled unaligned relocations on 'sparc-*-*' targets.
+mishandled unaligned relocations on `sparc-*-*' targets.
sparc64-*-solaris2*
===================
When configuring the GNU Multiple Precision Library (GMP), the MPFR
library or the MPC library, the canonical target triplet must be
-specified as the 'build' parameter on the configure line. For example
+specified as the `build' parameter on the configure line. For example
on a Solaris 9 system:
% ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
@@ -3805,19 +3865,18 @@ in order to bootstrap this target with the Sun compiler:
% CC="cc -xarch=v9 -xildoff" SRCDIR/configure [OPTIONS] [TARGET]
-'-xarch=v9' specifies the SPARC-V9 architecture to the Sun toolchain and
-'-xildoff' turns off the incremental linker.
+`-xarch=v9' specifies the SPARC-V9 architecture to the Sun toolchain
+and `-xildoff' turns off the incremental linker.
sparcv9-*-solaris2*
===================
-This is a synonym for 'sparc64-*-solaris2*'.
+This is a synonym for `sparc64-*-solaris2*'.
c6x-*-*
=======
-The C6X family of processors. This port requires binutils-2.22 or
-newer.
+The C6X family of processors. This port requires binutils-2.22 or newer.
tilegx-*-linux*
===============
@@ -3846,31 +3905,31 @@ systems.
*-*-vxworks*
============
-Support for VxWorks is in flux. At present GCC supports _only_ the very
-recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. We
-welcome patches for other architectures supported by VxWorks 5.5.
+Support for VxWorks is in flux. At present GCC supports _only_ the
+very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
+We welcome patches for other architectures supported by VxWorks 5.5.
Support for VxWorks AE would also be welcome; we believe this is merely
a matter of writing an appropriate "configlette" (see below). We are
not interested in supporting older, a.out or COFF-based, versions of
VxWorks in GCC 3.
VxWorks comes with an older version of GCC installed in
-'$WIND_BASE/host'; we recommend you do not overwrite it. Choose an
+`$WIND_BASE/host'; we recommend you do not overwrite it. Choose an
installation PREFIX entirely outside $WIND_BASE. Before running
-'configure', create the directories 'PREFIX' and 'PREFIX/bin'. Link or
-copy the appropriate assembler, linker, etc. into 'PREFIX/bin', and set
-your PATH to include that directory while running both 'configure' and
-'make'.
-
- You must give 'configure' the '--with-headers=$WIND_BASE/target/h'
-switch so that it can find the VxWorks system headers. Since VxWorks is
-a cross compilation target only, you must also specify
-'--target=TARGET'. 'configure' will attempt to create the directory
-'PREFIX/TARGET/sys-include' and copy files into it; make sure the user
-running 'configure' has sufficient privilege to do so.
+`configure', create the directories `PREFIX' and `PREFIX/bin'. Link or
+copy the appropriate assembler, linker, etc. into `PREFIX/bin', and set
+your PATH to include that directory while running both `configure' and
+`make'.
+
+ You must give `configure' the `--with-headers=$WIND_BASE/target/h'
+switch so that it can find the VxWorks system headers. Since VxWorks
+is a cross compilation target only, you must also specify
+`--target=TARGET'. `configure' will attempt to create the directory
+`PREFIX/TARGET/sys-include' and copy files into it; make sure the user
+running `configure' has sufficient privilege to do so.
GCC's exception handling runtime requires a special "configlette"
-module, 'contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that
+module, `contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that
file to add the module to your kernel build. (Future versions of
VxWorks will incorporate this module.)
@@ -3880,44 +3939,44 @@ x86_64-*-*, amd64-*-*
GCC supports the x86-64 architecture implemented by the AMD64 processor
(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
On GNU/Linux the default is a bi-arch compiler which is able to generate
-both 64-bit x86-64 and 32-bit x86 code (via the '-m32' switch).
+both 64-bit x86-64 and 32-bit x86 code (via the `-m32' switch).
x86_64-*-solaris2.1[0-9]*
=========================
GCC also supports the x86-64 architecture implemented by the AMD64
-processor ('amd64-*-*' is an alias for 'x86_64-*-*') on Solaris 10 or
-later. Unlike other systems, without special options a bi-arch compiler
-is built which generates 32-bit code by default, but can generate 64-bit
-x86-64 code with the '-m64' switch. Since GCC 4.7, there is also
-configuration that defaults to 64-bit code, but can generate 32-bit code
-with '-m32'. To configure and build this way, you have to provide all
-support libraries like 'libgmp' as 64-bit code, configure with
-'--target=x86_64-pc-solaris2.1x' and 'CC=gcc -m64'.
+processor (`amd64-*-*' is an alias for `x86_64-*-*') on Solaris 10 or
+later. Unlike other systems, without special options a bi-arch
+compiler is built which generates 32-bit code by default, but can
+generate 64-bit x86-64 code with the `-m64' switch. Since GCC 4.7,
+there is also configuration that defaults to 64-bit code, but can
+generate 32-bit code with `-m32'. To configure and build this way, you
+have to provide all support libraries like `libgmp' as 64-bit code,
+configure with `--target=x86_64-pc-solaris2.1x' and `CC=gcc -m64'.
xtensa*-*-elf
=============
-This target is intended for embedded Xtensa systems using the 'newlib' C
-library. It uses ELF but does not support shared objects.
+This target is intended for embedded Xtensa systems using the `newlib'
+C library. It uses ELF but does not support shared objects.
Designed-defined instructions specified via the Tensilica Instruction
Extension (TIE) language are only supported through inline assembly.
The Xtensa configuration information must be specified prior to
-building GCC. The 'include/xtensa-config.h' header file contains the
-configuration information. If you created your own Xtensa configuration
-with the Xtensa Processor Generator, the downloaded files include a
-customized copy of this header file, which you can use to replace the
-default header file.
+building GCC. The `include/xtensa-config.h' header file contains the
+configuration information. If you created your own Xtensa
+configuration with the Xtensa Processor Generator, the downloaded files
+include a customized copy of this header file, which you can use to
+replace the default header file.
xtensa*-*-linux*
================
This target is for Xtensa systems running GNU/Linux. It supports ELF
shared objects and the GNU C library (glibc). It also generates
-position-independent code (PIC) regardless of whether the '-fpic' or
-'-fPIC' options are used. In other respects, this target is the same as
-the 'xtensa*-*-elf' target.
+position-independent code (PIC) regardless of whether the `-fpic' or
+`-fPIC' options are used. In other respects, this target is the same
+as the `xtensa*-*-elf' target.
Microsoft Windows
=================
@@ -3939,21 +3998,24 @@ Windows XP, and Windows Vista, are supported by several different target
platforms. These targets differ in which Windows subsystem they target
and which C libraries are used.
- * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API emulation
- layer in the Win32 subsystem.
+ * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API
+ emulation layer in the Win32 subsystem.
+
* Interix *-*-interix: The Interix subsystem provides native support
for POSIX.
+
* MinGW *-*-mingw32: MinGW is a native GCC port for the Win32
subsystem that provides a subset of POSIX.
- * MKS i386-pc-mks: NuTCracker from MKS. See
- <http://www.mkssoftware.com/> for more information.
+
+ * MKS i386-pc-mks: NuTCracker from MKS. See
+ `http://www.mkssoftware.com/' for more information.
Intel 64-bit versions
---------------------
GCC contains support for x86-64 using the mingw-w64 runtime library,
-available from <http://mingw-w64.sourceforge.net/>. This library should
-be used with the target triple x86_64-pc-mingw32.
+available from `http://mingw-w64.sourceforge.net/'. This library
+should be used with the target triple x86_64-pc-mingw32.
Presently Windows for Itanium is not supported.
@@ -3975,7 +4037,7 @@ support the Interix subsystem. See above.
used.
PW32 (i386-pc-pw32) support was never completed, and the project
-seems to be inactive. See <http://pw32.sourceforge.net/> for more
+seems to be inactive. See `http://pw32.sourceforge.net/' for more
information.
UWIN support has been removed due to a lack of maintenance.
@@ -3998,7 +4060,7 @@ version 2.20 or above if building your own.
===========
The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
-and Subsystem for UNIX-based Applications (SUA). Applications compiled
+and Subsystem for UNIX-based Applications (SUA). Applications compiled
with this target run in the Interix subsystem, which is separate from
the Win32 subsystem. This target was last known to work in GCC 3.3.
@@ -4007,7 +4069,7 @@ the Win32 subsystem. This target was last known to work in GCC 3.3.
GCC will build with and support only MinGW runtime 3.12 and later.
Earlier versions of headers are incompatible with the new default
-semantics of 'extern inline' in '-std=c99' and '-std=gnu99' modes.
+semantics of `extern inline' in `-std=c99' and `-std=gnu99' modes.
Older systems
=============
@@ -4019,7 +4081,7 @@ and may suffer from bitrot.
Starting with GCC 3.1, each release has a list of "obsoleted"
systems. Support for these systems is still present in that release,
-but 'configure' will fail unless the '--enable-obsolete' option is
+but `configure' will fail unless the `--enable-obsolete' option is
given. Unless a maintainer steps forward, support for these systems
will be removed from the next release of GCC.
@@ -4030,33 +4092,33 @@ bring GCC up on such a system, if still possible with current GCC, may
require first installing an old version of GCC which did work on that
system, and using it to compile a more recent GCC, to avoid bugs in the
vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
-'old-releases' directory on the GCC mirror sites. Header bugs may
-generally be avoided using 'fixincludes', but bugs or deficiencies in
+`old-releases' directory on the GCC mirror sites. Header bugs may
+generally be avoided using `fixincludes', but bugs or deficiencies in
libraries and the operating system may still cause problems.
Support for older systems as targets for cross-compilation is less
problematic than support for them as hosts for GCC; if an enthusiast
wishes to make such a target work again (including resurrecting any of
-the targets that never worked with GCC 2, starting from the last version
-before they were removed), patches following the usual requirements
-would be likely to be accepted, since they should not affect the support
-for more modern targets.
+the targets that never worked with GCC 2, starting from the last
+version before they were removed), patches following the usual
+requirements would be likely to be accepted, since they should not
+affect the support for more modern targets.
For some systems, old versions of GNU binutils may also be useful,
-and are available from 'pub/binutils/old-releases' on sourceware.org
+and are available from `pub/binutils/old-releases' on sourceware.org
mirror sites.
Some of the information on specific systems above relates to such
older systems, but much of the information about GCC on such systems
-(which may no longer be applicable to current GCC) is to be found in the
-GCC texinfo manual.
+(which may no longer be applicable to current GCC) is to be found in
+the GCC texinfo manual.
all ELF targets (SVR4, Solaris 2, etc.)
=======================================
C++ support is significantly better on ELF targets if you use the GNU
-linker; duplicate copies of inlines, vtables and template instantiations
-will be discarded automatically.
+linker; duplicate copies of inlines, vtables and template
+instantiations will be discarded automatically.

File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev: Specific, Up: Top
@@ -4064,7 +4126,7 @@ File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev:
10 Old installation documentation
*********************************
-Note most of this information is out of date and superseded by the
+ Note most of this information is out of date and superseded by the
previous chapters of this manual. It is provided for historical
reference only, because of a lack of volunteers to merge it into the
main manual.
@@ -4078,14 +4140,14 @@ main manual.
1. If you have chosen a configuration for GCC which requires other GNU
tools (such as GAS or the GNU linker) instead of the standard
system tools, install the required tools in the build directory
- under the names 'as', 'ld' or whatever is appropriate.
+ under the names `as', `ld' or whatever is appropriate.
Alternatively, you can do subsequent compilation using a value of
- the 'PATH' environment variable such that the necessary GNU tools
+ the `PATH' environment variable such that the necessary GNU tools
come before the standard system tools.
2. Specify the host, build and target machine configurations. You do
- this when you run the 'configure' script.
+ this when you run the `configure' script.
The "build" machine is the system which you are using, the "host"
machine is the system where you want to run the resulting compiler
@@ -4094,14 +4156,14 @@ main manual.
If you are building a compiler to produce code for the machine it
runs on (a native compiler), you normally do not need to specify
- any operands to 'configure'; it will try to guess the type of
+ any operands to `configure'; it will try to guess the type of
machine you are on and use that as the build, host and target
machines. So you don't need to specify a configuration when
- building a native compiler unless 'configure' cannot figure out
+ building a native compiler unless `configure' cannot figure out
what your configuration is or guesses wrong.
In those cases, specify the build machine's "configuration name"
- with the '--host' option; the host and target will default to be
+ with the `--host' option; the host and target will default to be
the same as the host machine.
Here is an example:
@@ -4112,51 +4174,52 @@ main manual.
abbreviated.
A canonical configuration name has three parts, separated by
- dashes. It looks like this: 'CPU-COMPANY-SYSTEM'. (The three
- parts may themselves contain dashes; 'configure' can figure out
+ dashes. It looks like this: `CPU-COMPANY-SYSTEM'. (The three
+ parts may themselves contain dashes; `configure' can figure out
which dashes serve which purpose.) For example,
- 'm68k-sun-sunos4.1' specifies a Sun 3.
+ `m68k-sun-sunos4.1' specifies a Sun 3.
You can also replace parts of the configuration by nicknames or
- aliases. For example, 'sun3' stands for 'm68k-sun', so
- 'sun3-sunos4.1' is another way to specify a Sun 3.
+ aliases. For example, `sun3' stands for `m68k-sun', so
+ `sun3-sunos4.1' is another way to specify a Sun 3.
- You can specify a version number after any of the system types, and
- some of the CPU types. In most cases, the version is irrelevant,
- and will be ignored. So you might as well specify the version if
- you know it.
+ You can specify a version number after any of the system types,
+ and some of the CPU types. In most cases, the version is
+ irrelevant, and will be ignored. So you might as well specify the
+ version if you know it.
See *note Configurations::, for a list of supported configuration
names and notes on many of the configurations. You should check
the notes in that section before proceeding any further with the
installation of GCC.
+

File: gccinstall.info, Node: Configurations, Up: Old
10.1 Configurations Supported by GCC
====================================
-Here are the possible CPU types:
+ Here are the possible CPU types:
1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30,
h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860,
i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64,
- mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp,
- rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k.
+ mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle,
+ romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k.
Here are the recognized company names. As you can see, customary
abbreviations are used rather than the longer official names.
acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent,
- convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp,
- ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus,
- sequent, sgi, sony, sun, tti, unicom, wrs.
+ convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi,
+ hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron,
+ plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
The company name is meaningful only to disambiguate when the rest of
-the information supplied is insufficient. You can omit it, writing just
-'CPU-SYSTEM', if it is not needed. For example, 'vax-ultrix4.2' is
-equivalent to 'vax-dec-ultrix4.2'.
+the information supplied is insufficient. You can omit it, writing
+just `CPU-SYSTEM', if it is not needed. For example, `vax-ultrix4.2'
+is equivalent to `vax-dec-ultrix4.2'.
Here is a list of system types:
@@ -4168,29 +4231,29 @@ equivalent to 'vax-dec-ultrix4.2'.
sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks,
winnt, xenix.
-You can omit the system type; then 'configure' guesses the operating
+You can omit the system type; then `configure' guesses the operating
system from the CPU and company.
You can add a version number to the system type; this may or may not
-make a difference. For example, you can write 'bsd4.3' or 'bsd4.4' to
+make a difference. For example, you can write `bsd4.3' or `bsd4.4' to
distinguish versions of BSD. In practice, the version number is most
-needed for 'sysv3' and 'sysv4', which are often treated differently.
+needed for `sysv3' and `sysv4', which are often treated differently.
- 'linux-gnu' is the canonical name for the GNU/Linux target; however
-GCC will also accept 'linux'. The version of the kernel in use is not
-relevant on these systems. A suffix such as 'libc1' or 'aout'
+ `linux-gnu' is the canonical name for the GNU/Linux target; however
+GCC will also accept `linux'. The version of the kernel in use is not
+relevant on these systems. A suffix such as `libc1' or `aout'
distinguishes major versions of the C library; all of the suffixed
versions are obsolete.
- If you specify an impossible combination such as 'i860-dg-vms', then
-you may get an error message from 'configure', or it may ignore part of
-the information and do the best it can with the rest. 'configure'
+ If you specify an impossible combination such as `i860-dg-vms', then
+you may get an error message from `configure', or it may ignore part of
+the information and do the best it can with the rest. `configure'
always prints the canonical name for the alternative that it used. GCC
does not support all possible alternatives.
Often a particular model of machine has a name. Many machine names
are recognized as aliases for CPU/company combinations. Thus, the
-machine name 'sun3', mentioned above, is an alias for 'm68k-sun'.
+machine name `sun3', mentioned above, is an alias for `m68k-sun'.
Sometimes we accept a company name as a machine name, when the name is
popularly used for a particular machine. Here is a table of the known
machine names:
@@ -4200,8 +4263,8 @@ machine names:
encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN,
hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe,
mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc,
- powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, sun4,
- symmetry, tower-32, tower.
+ powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3,
+ sun4, symmetry, tower-32, tower.
Remember that a machine name specifies both the cpu type and the company
name.
@@ -4215,7 +4278,7 @@ GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
+ `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -4240,21 +4303,21 @@ GNU Free Documentation License
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book. We
- recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it can
- be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright 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, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
- the license if you copy, modify or distribute the work in a way
- requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "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 containing the
Document or a portion of it, either copied verbatim, or with
@@ -4272,12 +4335,12 @@ GNU Free Documentation License
regarding them.
The "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 above definition of Secondary then it
- is not allowed to be designated as Invariant. The Document may
- contain zero Invariant Sections. If the Document does not identify
- any Invariant Sections then there are none.
+ 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 above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -4288,27 +4351,27 @@ GNU Free Documentation License
A "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 generic text editors or (for images composed
- of pixels) generic paint programs or (for drawings) some widely
- available drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of formats
- suitable for input to text formatters. A copy made in an otherwise
- Transparent file format whose markup, or absence 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".
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence 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".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and standard-conforming
- simple HTML, PostScript or PDF designed for human modification.
- Examples of transparent image formats include PNG, XCF and JPG.
- Opaque formats include proprietary formats that can be read and
- edited only by proprietary word processors, SGML or XML for which
- the DTD and/or processing tools are not generally available, and
- the machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -4346,8 +4409,8 @@ GNU Free Documentation License
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow the
- conditions in section 3.
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -4361,11 +4424,12 @@ GNU Free Documentation License
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on the
- covers in addition. Copying with changes limited to the covers, as
- long as they preserve the title of the Document and satisfy these
- conditions, can be treated as verbatim copying in other respects.
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -4373,39 +4437,40 @@ GNU Free Documentation License
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with
- each Opaque copy a computer-network location from which the general
- network-using public has access to download using public-standard
- network protocols a complete Transparent copy of the Document, free
- of added material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of Opaque
- copies in quantity, to ensure that this Transparent copy will
- remain thus accessible at the stated location until at least one
- year after the last time you distribute an Opaque copy (directly or
- through your agents or retailers) of that edition to the public.
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies,
- to give them a chance to provide you with an updated version of the
- Document.
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with the
- Modified Version filling the role of the Document, thus licensing
- distribution and modification of the Modified Version to whoever
- possesses a copy of it. In addition, you must do these things in
- the Modified Version:
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the
- History section of the Document). You may use the same title
- as a previous version if the original publisher of that
- version gives permission.
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -4435,30 +4500,31 @@ GNU Free Documentation License
I. Preserve the section Entitled "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, 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.
+ 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, 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.
J. Preserve the network location, if any, given in 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 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.
+ previous versions it was based on. These may be placed in
+ the "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.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section
- all the substance and tone of each of the contributor
+ 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.
- L. Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the
- equivalent are not considered part of the section titles.
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -4471,11 +4537,11 @@ GNU Free Documentation License
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain 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 be distinct from any other
- section titles.
+ 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 be distinct from any
+ other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -4484,15 +4550,15 @@ GNU Free Documentation License
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of
- the list of Cover Texts in the Modified Version. Only one passage
- of Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover, previously added
- by you or by arrangement made by the same entity you are acting on
- behalf of, you may not add another; but you may replace the old
- one, on explicit permission from the previous publisher that added
- the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -4502,8 +4568,8 @@ GNU Free Documentation License
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination all
- of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -4530,20 +4596,20 @@ GNU Free Documentation License
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the documents
- in all other respects.
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
7. AGGREGATION WITH INDEPENDENT WORKS
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
+ 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 the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -4588,8 +4654,8 @@ GNU Free Documentation License
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -4601,33 +4667,33 @@ GNU Free Documentation License
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, receipt of a copy of some or all of the
- same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, receipt of a copy of some or all of
+ the same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- <http://www.gnu.org/copyleft/>.
+ `http://www.gnu.org/copyleft/'.
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 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 Foundation. If the
- Document does not specify a version number 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
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number 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 statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
@@ -4657,6 +4723,7 @@ GNU Free Documentation License
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
+
ADDENDUM: How to use this License for your documents
====================================================
@@ -4673,7 +4740,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -4684,9 +4751,9 @@ combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of free
-software license, such as the GNU General Public License, to permit
-their use in free software.
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.

File: gccinstall.info, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top
@@ -4698,7 +4765,7 @@ Concept Index
* Menu:
* Binaries: Binaries. (line 6)
-* 'build_configargs': Configuration. (line 1642)
+* build_configargs: Configuration. (line 1694)
* Configuration: Configuration. (line 6)
* configurations supported by GCC: Configurations. (line 6)
* Downloading GCC: Downloading the source.
@@ -4708,7 +4775,7 @@ Concept Index
* FDL, GNU Free Documentation License: GNU Free Documentation License.
(line 6)
* Host specific installation: Specific. (line 6)
-* 'host_configargs': Configuration. (line 1646)
+* host_configargs: Configuration. (line 1698)
* Installing GCC: Binaries: Binaries. (line 6)
* Installing GCC: Building: Building. (line 6)
* Installing GCC: Configuration: Configuration. (line 6)
@@ -4718,111 +4785,111 @@ Concept Index
* Specific installation notes: Specific. (line 6)
* Target specific installation: Specific. (line 6)
* Target specific installation notes: Specific. (line 6)
-* 'target_configargs': Configuration. (line 1650)
+* target_configargs: Configuration. (line 1702)
* Testing: Testing. (line 6)
* Testsuite: Testing. (line 6)

Tag Table:
-Node: Top1696
-Node: Installing GCC2254
-Node: Prerequisites3888
-Node: Downloading the source15044
-Node: Configuration16594
-Ref: with-gnu-as32054
-Ref: with-as32949
-Ref: with-gnu-ld34362
-Ref: WithAixSoname51653
-Ref: AixLdCommand52314
-Node: Building91431
-Node: Testing107323
-Node: Final install115185
-Node: Binaries120496
-Node: Specific121960
-Ref: aarch64-x-x122467
-Ref: alpha-x-x123247
-Ref: alpha-dec-osf51123736
-Ref: amd64-x-solaris210124261
-Ref: arc-x-elf32124364
-Ref: arc-linux-uclibc124540
-Ref: arm-x-eabi124681
-Ref: avr124892
-Ref: bfin125531
-Ref: cr16125772
-Ref: cris126188
-Ref: dos127003
-Ref: epiphany-x-elf127326
-Ref: x-x-freebsd127431
-Ref: h8300-hms129267
-Ref: hppa-hp-hpux129619
-Ref: hppa-hp-hpux10131991
-Ref: hppa-hp-hpux11132404
-Ref: x-x-linux-gnu138063
-Ref: ix86-x-linux138256
-Ref: ix86-x-solaris210138569
-Ref: ia64-x-linux139760
-Ref: ia64-x-hpux140530
-Ref: x-ibm-aix141085
-Ref: TransferAixShobj144268
-Ref: iq2000-x-elf148078
-Ref: lm32-x-elf148218
-Ref: lm32-x-uclinux148322
-Ref: m32c-x-elf148450
-Ref: m32r-x-elf148552
-Ref: m68k-x-x148654
-Ref: m68k-x-uclinux149692
-Ref: mep-x-elf149937
-Ref: microblaze-x-elf150047
-Ref: mips-x-x150166
-Ref: mips-sgi-irix5152560
-Ref: mips-sgi-irix6152640
-Ref: moxie-x-elf152827
-Ref: msp430-x-elf152874
-Ref: nds32le-x-elf152977
-Ref: nds32be-x-elf153049
-Ref: nvptx-x-none153118
-Ref: powerpc-x-x153645
-Ref: powerpc-x-darwin153850
-Ref: powerpc-x-elf154344
-Ref: powerpc-x-linux-gnu154429
-Ref: powerpc-x-netbsd154524
-Ref: powerpc-x-eabisim154612
-Ref: powerpc-x-eabi154738
-Ref: powerpcle-x-elf154814
-Ref: powerpcle-x-eabisim154906
-Ref: powerpcle-x-eabi155039
-Ref: rl78-x-elf155122
-Ref: rx-x-elf155228
-Ref: s390-x-linux155427
-Ref: s390x-x-linux155499
-Ref: s390x-ibm-tpf155586
-Ref: x-x-solaris2155717
-Ref: sparc-x-x159523
-Ref: sparc-sun-solaris2160025
-Ref: sparc-sun-solaris210162778
-Ref: sparc-x-linux163153
-Ref: sparc64-x-solaris2163378
-Ref: sparcv9-x-solaris2164031
-Ref: c6x-x-x164118
-Ref: tilegx-*-linux164210
-Ref: tilegxbe-*-linux164352
-Ref: tilepro-*-linux164495
-Ref: visium-x-elf164616
-Ref: x-x-vxworks164724
-Ref: x86-64-x-x166247
-Ref: x86-64-x-solaris210166575
-Ref: xtensa-x-elf167237
-Ref: xtensa-x-linux167908
-Ref: windows168249
-Ref: x-x-cygwin170182
-Ref: x-x-interix170735
-Ref: x-x-mingw32171043
-Ref: older171269
-Ref: elf173386
-Node: Old173644
-Node: Configurations176777
-Node: GNU Free Documentation License180315
-Node: Concept Index205443
+Node: Top1747
+Node: Installing GCC2305
+Node: Prerequisites3942
+Node: Downloading the source15088
+Node: Configuration16642
+Ref: with-gnu-as32093
+Ref: with-as32991
+Ref: with-gnu-ld34404
+Ref: WithAixSoname51698
+Ref: AixLdCommand52359
+Node: Building91523
+Node: Testing107432
+Node: Final install115304
+Node: Binaries120618
+Node: Specific122086
+Ref: aarch64-x-x122596
+Ref: alpha-x-x124028
+Ref: alpha-dec-osf51124517
+Ref: amd64-x-solaris210125042
+Ref: arc-x-elf32125145
+Ref: arc-linux-uclibc125321
+Ref: arm-x-eabi125462
+Ref: avr125673
+Ref: bfin126313
+Ref: cr16126555
+Ref: cris126970
+Ref: dos127786
+Ref: epiphany-x-elf128109
+Ref: x-x-freebsd128214
+Ref: h8300-hms130051
+Ref: hppa-hp-hpux130403
+Ref: hppa-hp-hpux10132774
+Ref: hppa-hp-hpux11133187
+Ref: x-x-linux-gnu138846
+Ref: ix86-x-linux139039
+Ref: ix86-x-solaris210139352
+Ref: ia64-x-linux140543
+Ref: ia64-x-hpux141313
+Ref: x-ibm-aix141868
+Ref: TransferAixShobj145050
+Ref: iq2000-x-elf148861
+Ref: lm32-x-elf149001
+Ref: lm32-x-uclinux149105
+Ref: m32c-x-elf149233
+Ref: m32r-x-elf149335
+Ref: m68k-x-x149437
+Ref: m68k-x-uclinux150475
+Ref: mep-x-elf150721
+Ref: microblaze-x-elf150831
+Ref: mips-x-x150950
+Ref: mips-sgi-irix5153346
+Ref: mips-sgi-irix6153426
+Ref: moxie-x-elf153613
+Ref: msp430-x-elf153660
+Ref: nds32le-x-elf153763
+Ref: nds32be-x-elf153835
+Ref: nvptx-x-none153904
+Ref: powerpc-x-x154431
+Ref: powerpc-x-darwin154636
+Ref: powerpc-x-elf155130
+Ref: powerpc-x-linux-gnu155215
+Ref: powerpc-x-netbsd155310
+Ref: powerpc-x-eabisim155398
+Ref: powerpc-x-eabi155524
+Ref: powerpcle-x-elf155600
+Ref: powerpcle-x-eabisim155692
+Ref: powerpcle-x-eabi155825
+Ref: rl78-x-elf155908
+Ref: rx-x-elf156014
+Ref: s390-x-linux156213
+Ref: s390x-x-linux156285
+Ref: s390x-ibm-tpf156372
+Ref: x-x-solaris2156503
+Ref: sparc-x-x160309
+Ref: sparc-sun-solaris2160811
+Ref: sparc-sun-solaris210163565
+Ref: sparc-x-linux163941
+Ref: sparc64-x-solaris2164166
+Ref: sparcv9-x-solaris2164819
+Ref: c6x-x-x164906
+Ref: tilegx-*-linux164997
+Ref: tilegxbe-*-linux165139
+Ref: tilepro-*-linux165282
+Ref: visium-x-elf165403
+Ref: x-x-vxworks165511
+Ref: x86-64-x-x167033
+Ref: x86-64-x-solaris210167361
+Ref: xtensa-x-elf168023
+Ref: xtensa-x-linux168694
+Ref: windows169035
+Ref: x-x-cygwin170972
+Ref: x-x-interix171525
+Ref: x-x-mingw32171834
+Ref: older172060
+Ref: elf174177
+Node: Old174435
+Node: Configurations177572
+Node: GNU Free Documentation License181113
+Node: Concept Index206260

End Tag Table
diff --git a/gcc/doc/gccint.info b/gcc/doc/gccint.info
index bb0e9abc19..d580dcd4e3 100644
--- a/gcc/doc/gccint.info
+++ b/gcc/doc/gccint.info
@@ -1,4 +1,5 @@
-This is gccint.info, produced by makeinfo version 5.2 from gccint.texi.
+This is doc/gccint.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/doc/gccint.texi.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -16,14 +17,14 @@ Free Documentation License".
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU software.
-Copies published by the Free Software Foundation raise funds for GNU
-development.
+ You have freedom to copy and modify this GNU Manual, like GNU
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
* gccint: (gccint). Internals of the GNU Compiler Collection.
END-INFO-DIR-ENTRY
-
This file documents the internals of the GNU compilers.
Copyright (C) 1988-2015 Free Software Foundation, Inc.
@@ -42,9 +43,10 @@ Free Documentation License".
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU software.
-Copies published by the Free Software Foundation raise funds for GNU
-development.
+ You have freedom to copy and modify this GNU Manual, like GNU
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+

File: gccint.info, Node: Top, Next: Contributing, Up: (DIR)
@@ -54,9 +56,9 @@ Introduction
This manual documents the internals of the GNU compilers, including how
to port them to new targets and some information about how to write
-front ends for new languages. It corresponds to the compilers (GCC)
-version 5.1.0. The use of the GNU compilers is documented in a separate
-manual. *Note Introduction: (gcc)Top.
+front ends for new languages. It corresponds to the compilers
+(GCC) version 5.2.0. The use of the GNU compilers is documented in a
+separate manual. *Note Introduction: (gcc)Top.
This manual is mainly a reference manual rather than a tutorial. It
discusses how to contribute to GCC (*note Contributing::), the
@@ -69,7 +71,7 @@ GCC front ends, and how support for a target system is implemented in
GCC.
Additional tutorial information is linked to from
-<http://gcc.gnu.org/readings.html>.
+`http://gcc.gnu.org/readings.html'.
* Menu:
@@ -90,9 +92,9 @@ GCC.
* Loop Analysis and Representation:: Analysis and representation of loops
* Machine Desc:: How to write machine description instruction patterns.
* Target Macros:: How to write the machine description C macros and functions.
-* Host Config:: Writing the 'xm-MACHINE.h' file.
-* Fragments:: Writing the 't-TARGET' and 'x-HOST' files.
-* Collect2:: How 'collect2' works; how it finds 'ld'.
+* Host Config:: Writing the `xm-MACHINE.h' file.
+* Fragments:: Writing the `t-TARGET' and `x-HOST' files.
+* Collect2:: How `collect2' works; how it finds `ld'.
* Header Dirs:: Understanding the standard header file directories.
* Type Information:: GCC's memory management; generating type information.
* Plugins:: Extending the compiler with plugins.
@@ -111,25 +113,25 @@ GCC.
* Concept Index:: Index of concepts and symbol names.

-File: gccint.info, Node: Contributing, Next: Portability, Up: Top
+File: gccint.info, Node: Contributing, Next: Portability, Prev: Top, Up: Top
1 Contributing to GCC Development
*********************************
If you would like to help pretest GCC releases to assure they work well,
current development sources are available by SVN (see
-<http://gcc.gnu.org/svn.html>). Source and binary snapshots are also
-available for FTP; see <http://gcc.gnu.org/snapshots.html>.
+`http://gcc.gnu.org/svn.html'). Source and binary snapshots are also
+available for FTP; see `http://gcc.gnu.org/snapshots.html'.
If you would like to work on improvements to GCC, please read the
advice at these URLs:
- <http://gcc.gnu.org/contribute.html>
- <http://gcc.gnu.org/contributewhy.html>
+ `http://gcc.gnu.org/contribute.html'
+ `http://gcc.gnu.org/contributewhy.html'
for information on how to make useful contributions and avoid
duplication of effort. Suggested projects are listed at
-<http://gcc.gnu.org/projects/>.
+`http://gcc.gnu.org/projects/'.

File: gccint.info, Node: Portability, Next: Interface, Prev: Contributing, Up: Top
@@ -137,19 +139,20 @@ File: gccint.info, Node: Portability, Next: Interface, Prev: Contributing, U
2 GCC and Portability
*********************
-GCC itself aims to be portable to any machine where 'int' is at least a
+GCC itself aims to be portable to any machine where `int' is at least a
32-bit type. It aims to target machines with a flat (non-segmented)
byte addressed data address space (the code address space can be
-separate). Target ABIs may have 8, 16, 32 or 64-bit 'int' type. 'char'
+separate). Target ABIs may have 8, 16, 32 or 64-bit `int' type. `char'
can be wider than 8 bits.
GCC gets most of the information about the target machine from a
machine description which gives an algebraic formula for each of the
machine's instructions. This is a very clean way to describe the
target. But when the compiler needs information that is difficult to
-express in this fashion, ad-hoc parameters have been defined for machine
-descriptions. The purpose of portability is to reduce the total work
-needed on the compiler; it was not of interest for its own sake.
+express in this fashion, ad-hoc parameters have been defined for
+machine descriptions. The purpose of portability is to reduce the
+total work needed on the compiler; it was not of interest for its own
+sake.
GCC does not contain machine dependent code, but it does contain code
that depends on machine parameters such as endianness (whether the most
@@ -158,12 +161,12 @@ word) and the availability of autoincrement addressing. In the
RTL-generation pass, it is often necessary to have multiple strategies
for generating code for a particular kind of syntax tree, strategies
that are usable for different combinations of parameters. Often, not
-all possible cases have been addressed, but only the common ones or only
-the ones that have been encountered. As a result, a new target may
-require additional strategies. You will know if this happens because
-the compiler will call 'abort'. Fortunately, the new strategies can be
-added in a machine-independent fashion, and will affect only the target
-machines that need them.
+all possible cases have been addressed, but only the common ones or
+only the ones that have been encountered. As a result, a new target
+may require additional strategies. You will know if this happens
+because the compiler will call `abort'. Fortunately, the new
+strategies can be added in a machine-independent fashion, and will
+affect only the target machines that need them.

File: gccint.info, Node: Interface, Next: Libgcc, Prev: Portability, Up: Top
@@ -181,12 +184,12 @@ returning such types cannot be called from code compiled with GCC, and
vice versa. This does not cause trouble often because few Unix library
routines return structures or unions.
- GCC code returns structures and unions that are 1, 2, 4 or 8 bytes long
-in the same registers used for 'int' or 'double' return values. (GCC
-typically allocates variables of such types in registers also.)
+ GCC code returns structures and unions that are 1, 2, 4 or 8 bytes
+long in the same registers used for `int' or `double' return values.
+(GCC typically allocates variables of such types in registers also.)
Structures and unions of other sizes are returned by storing them into
an address passed by the caller (usually in a register). The target
-hook 'TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address.
+hook `TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address.
By contrast, PCC on most target machines returns structures and unions
of any size by copying the data into an area of static storage, and then
@@ -217,12 +220,12 @@ are passed "by invisible reference". This means that the value is
stored in memory, and the address of the memory location is passed to
the subroutine.
- If you use 'longjmp', beware of automatic variables. ISO C says that
-automatic variables that are not declared 'volatile' have undefined
-values after a 'longjmp'. And this is all GCC promises to do, because
-it is very difficult to restore register variables correctly, and one of
-GCC's features is that it can put variables in registers without your
-asking it to.
+ If you use `longjmp', beware of automatic variables. ISO C says that
+automatic variables that are not declared `volatile' have undefined
+values after a `longjmp'. And this is all GCC promises to do, because
+it is very difficult to restore register variables correctly, and one
+of GCC's features is that it can put variables in registers without
+your asking it to.

File: gccint.info, Node: Libgcc, Next: Languages, Prev: Interface, Up: Top
@@ -230,34 +233,34 @@ File: gccint.info, Node: Libgcc, Next: Languages, Prev: Interface, Up: Top
4 The GCC low-level runtime library
***********************************
-GCC provides a low-level runtime library, 'libgcc.a' or 'libgcc_s.so.1'
+GCC provides a low-level runtime library, `libgcc.a' or `libgcc_s.so.1'
on some platforms. GCC generates calls to routines in this library
automatically, whenever it needs to perform some operation that is too
complicated to emit inline code for.
- Most of the routines in 'libgcc' handle arithmetic operations that the
+ Most of the routines in `libgcc' handle arithmetic operations that the
target processor cannot perform directly. This includes integer
multiply and divide on some machines, and all floating-point and
-fixed-point operations on other machines. 'libgcc' also includes
+fixed-point operations on other machines. `libgcc' also includes
routines for exception handling, and a handful of miscellaneous
operations.
Some of these routines can be defined in mostly machine-independent C.
-Others must be hand-written in assembly language for each processor that
-needs them.
+Others must be hand-written in assembly language for each processor
+that needs them.
- GCC will also generate calls to C library routines, such as 'memcpy'
-and 'memset', in some cases. The set of routines that GCC may possibly
-use is documented in *note (gcc)Other Builtins::.
+ GCC will also generate calls to C library routines, such as `memcpy'
+and `memset', in some cases. The set of routines that GCC may possibly
+use is documented in *note Other Builtins: (gcc)Other Builtins.
These routines take arguments and return values of a specific machine
mode, not a specific C type. *Note Machine Modes::, for an explanation
of this concept. For illustrative purposes, in this chapter the
-floating point type 'float' is assumed to correspond to 'SFmode';
-'double' to 'DFmode'; and 'long double' to both 'TFmode' and 'XFmode'.
-Similarly, the integer types 'int' and 'unsigned int' correspond to
-'SImode'; 'long' and 'unsigned long' to 'DImode'; and 'long long' and
-'unsigned long long' to 'TImode'.
+floating point type `float' is assumed to correspond to `SFmode';
+`double' to `DFmode'; and `long double' to both `TFmode' and `XFmode'.
+Similarly, the integer types `int' and `unsigned int' correspond to
+`SImode'; `long' and `unsigned long' to `DImode'; and `long long' and
+`unsigned long long' to `TImode'.
* Menu:
@@ -320,8 +323,8 @@ hardware support for arithmetic operations on some modes.
-- Runtime Function: unsigned int __udivsi3 (unsigned int A, unsigned
int B)
- -- Runtime Function: unsigned long __udivdi3 (unsigned long A, unsigned
- long B)
+ -- Runtime Function: unsigned long __udivdi3 (unsigned long A,
+ unsigned long B)
-- Runtime Function: unsigned long long __udivti3 (unsigned long long
A, unsigned long long B)
These functions return the quotient of the unsigned division of A
@@ -337,8 +340,8 @@ hardware support for arithmetic operations on some modes.
-- Runtime Function: unsigned int __umodsi3 (unsigned int A, unsigned
int B)
- -- Runtime Function: unsigned long __umoddi3 (unsigned long A, unsigned
- long B)
+ -- Runtime Function: unsigned long __umoddi3 (unsigned long A,
+ unsigned long B)
-- Runtime Function: unsigned long long __umodti3 (unsigned long long
A, unsigned long long B)
These functions return the remainder of the unsigned division of A
@@ -361,17 +364,17 @@ result using either signed or unsigned comparison.
and if A and B are equal they return 1.
-- Runtime Function: int __ucmpdi2 (unsigned long A, unsigned long B)
- -- Runtime Function: int __ucmpti2 (unsigned long long A, unsigned long
- long B)
- These functions perform an unsigned comparison of A and B. If A is
- less than B, they return 0; if A is greater than B, they return 2;
- and if A and B are equal they return 1.
+ -- Runtime Function: int __ucmpti2 (unsigned long long A, unsigned
+ long long B)
+ These functions perform an unsigned comparison of A and B. If A
+ is less than B, they return 0; if A is greater than B, they return
+ 2; and if A and B are equal they return 1.
4.1.3 Trapping arithmetic functions
-----------------------------------
The following functions implement trapping arithmetic. These functions
-call the libc function 'abort' upon signed arithmetic overflow.
+call the libc function `abort' upon signed arithmetic overflow.
-- Runtime Function: int __absvsi2 (int A)
-- Runtime Function: long __absvdi2 (long A)
@@ -379,20 +382,20 @@ call the libc function 'abort' upon signed arithmetic overflow.
-- Runtime Function: int __addvsi3 (int A, int B)
-- Runtime Function: long __addvdi3 (long A, long B)
- These functions return the sum of A and B; that is 'A + B'.
+ These functions return the sum of A and B; that is `A + B'.
-- Runtime Function: int __mulvsi3 (int A, int B)
-- Runtime Function: long __mulvdi3 (long A, long B)
- The functions return the product of A and B; that is 'A * B'.
+ The functions return the product of A and B; that is `A * B'.
-- Runtime Function: int __negvsi2 (int A)
-- Runtime Function: long __negvdi2 (long A)
- These functions return the negation of A; that is '-A'.
+ These functions return the negation of A; that is `-A'.
-- Runtime Function: int __subvsi3 (int A, int B)
-- Runtime Function: long __subvdi3 (long A, long B)
- These functions return the difference between B and A; that is 'A -
- B'.
+ These functions return the difference between B and A; that is `A
+ - B'.
4.1.4 Bit operations
--------------------
@@ -440,15 +443,15 @@ File: gccint.info, Node: Soft float library routines, Next: Decimal float libr
The software floating point library is used on machines which do not
have hardware support for floating point. It is also used whenever
-'-msoft-float' is used to disable generation of floating point
+`-msoft-float' is used to disable generation of floating point
instructions. (Not all targets support this switch.)
For compatibility with other compilers, the floating point emulation
-routines can be renamed with the 'DECLARE_LIBRARY_RENAMES' macro (*note
+routines can be renamed with the `DECLARE_LIBRARY_RENAMES' macro (*note
Library Calls::). In this section, the default names are used.
- Presently the library does not support 'XFmode', which is used for
-'long double' on some architectures.
+ Presently the library does not support `XFmode', which is used for
+`long double' on some architectures.
4.2.1 Arithmetic functions
--------------------------
@@ -549,8 +552,8 @@ Library Calls::). In this section, the default names are used.
-- Runtime Function: unsigned long long __fixunsdfti (double A)
-- Runtime Function: unsigned long long __fixunstfti (long double A)
-- Runtime Function: unsigned long long __fixunsxfti (long double A)
- These functions convert A to an unsigned long long, rounding toward
- zero. Negative values all become zero.
+ These functions convert A to an unsigned long long, rounding
+ toward zero. Negative values all become zero.
-- Runtime Function: float __floatsisf (int I)
-- Runtime Function: double __floatsidf (int I)
@@ -598,10 +601,10 @@ There are two sets of basic comparison functions.
-- Runtime Function: int __cmpdf2 (double A, double B)
-- Runtime Function: int __cmptf2 (long double A, long double B)
These functions calculate a <=> b. That is, if A is less than B,
- they return -1; if A is greater than B, they return 1; and if A and
- B are equal they return 0. If either argument is NaN they return
- 1, but you should not rely on this; if NaN is a possibility, use
- one of the higher-level comparison functions.
+ they return -1; if A is greater than B, they return 1; and if A
+ and B are equal they return 0. If either argument is NaN they
+ return 1, but you should not rely on this; if NaN is a
+ possibility, use one of the higher-level comparison functions.
-- Runtime Function: int __unordsf2 (float A, float B)
-- Runtime Function: int __unorddf2 (double A, double B)
@@ -619,16 +622,16 @@ hood, all of these routines are implemented as
return E;
return __cmpXf2 (a, b);
-where E is a constant chosen to give the proper behavior for NaN. Thus,
-the meaning of the return value is different for each set. Do not rely
-on this implementation; only the semantics documented below are
-guaranteed.
+where E is a constant chosen to give the proper behavior for NaN.
+Thus, the meaning of the return value is different for each set. Do
+not rely on this implementation; only the semantics documented below
+are guaranteed.
-- Runtime Function: int __eqsf2 (float A, float B)
-- Runtime Function: int __eqdf2 (double A, double B)
-- Runtime Function: int __eqtf2 (long double A, long double B)
- These functions return zero if neither argument is NaN, and A and B
- are equal.
+ These functions return zero if neither argument is NaN, and A and
+ B are equal.
-- Runtime Function: int __nesf2 (float A, float B)
-- Runtime Function: int __nedf2 (double A, double B)
@@ -669,8 +672,8 @@ guaranteed.
-- Runtime Function: long double __powixf2 (long double A, int B)
These functions convert raise A to the power B.
- -- Runtime Function: complex float __mulsc3 (float A, float B, float C,
- float D)
+ -- Runtime Function: complex float __mulsc3 (float A, float B, float
+ C, float D)
-- Runtime Function: complex double __muldc3 (double A, double B,
double C, double D)
-- Runtime Function: complex long double __multc3 (long double A, long
@@ -680,8 +683,8 @@ guaranteed.
These functions return the product of A + iB and C + iD, following
the rules of C99 Annex G.
- -- Runtime Function: complex float __divsc3 (float A, float B, float C,
- float D)
+ -- Runtime Function: complex float __divsc3 (float A, float B, float
+ C, float D)
-- Runtime Function: complex double __divdc3 (double A, double B,
double C, double D)
-- Runtime Function: complex long double __divtc3 (long double A, long
@@ -880,8 +883,8 @@ selected at configure time.
-- Runtime Function: unsigned long __bid_fixunsdddi (_Decimal64 A)
-- Runtime Function: unsigned long __dpd_fixunstddi (_Decimal128 A)
-- Runtime Function: unsigned long __bid_fixunstddi (_Decimal128 A)
- These functions convert A to an unsigned long. Negative values all
- become zero.
+ These functions convert A to an unsigned long. Negative values
+ all become zero.
-- Runtime Function: _Decimal32 __dpd_floatsisd (int I)
-- Runtime Function: _Decimal32 __bid_floatsisd (int I)
@@ -907,8 +910,8 @@ selected at configure time.
-- Runtime Function: _Decimal64 __bid_floatunssidd (unsigned int I)
-- Runtime Function: _Decimal128 __dpd_floatunssitd (unsigned int I)
-- Runtime Function: _Decimal128 __bid_floatunssitd (unsigned int I)
- These functions convert I, an unsigned integer, to decimal floating
- point.
+ These functions convert I, an unsigned integer, to decimal
+ floating point.
-- Runtime Function: _Decimal32 __dpd_floatunsdisd (unsigned long I)
-- Runtime Function: _Decimal32 __bid_floatunsdisd (unsigned long I)
@@ -941,10 +944,10 @@ hood, all of these routines are implemented as
return E;
return __bid_cmpXd2 (a, b);
-where E is a constant chosen to give the proper behavior for NaN. Thus,
-the meaning of the return value is different for each set. Do not rely
-on this implementation; only the semantics documented below are
-guaranteed.
+where E is a constant chosen to give the proper behavior for NaN.
+Thus, the meaning of the return value is different for each set. Do
+not rely on this implementation; only the semantics documented below
+are guaranteed.
-- Runtime Function: int __dpd_eqsd2 (_Decimal32 A, _Decimal32 B)
-- Runtime Function: int __bid_eqsd2 (_Decimal32 A, _Decimal32 B)
@@ -952,8 +955,8 @@ guaranteed.
-- Runtime Function: int __bid_eqdd2 (_Decimal64 A, _Decimal64 B)
-- Runtime Function: int __dpd_eqtd2 (_Decimal128 A, _Decimal128 B)
-- Runtime Function: int __bid_eqtd2 (_Decimal128 A, _Decimal128 B)
- These functions return zero if neither argument is NaN, and A and B
- are equal.
+ These functions return zero if neither argument is NaN, and A and
+ B are equal.
-- Runtime Function: int __dpd_nesd2 (_Decimal32 A, _Decimal32 B)
-- Runtime Function: int __bid_nesd2 (_Decimal32 A, _Decimal32 B)
@@ -1009,20 +1012,20 @@ File: gccint.info, Node: Fixed-point fractional library routines, Next: Except
The software fixed-point library implements fixed-point fractional
arithmetic, and is only activated on selected targets.
- For ease of comprehension 'fract' is an alias for the '_Fract' type,
-'accum' an alias for '_Accum', and 'sat' an alias for '_Sat'.
+ For ease of comprehension `fract' is an alias for the `_Fract' type,
+`accum' an alias for `_Accum', and `sat' an alias for `_Sat'.
For illustrative purposes, in this section the fixed-point fractional
-type 'short fract' is assumed to correspond to machine mode 'QQmode';
-'unsigned short fract' to 'UQQmode'; 'fract' to 'HQmode';
-'unsigned fract' to 'UHQmode'; 'long fract' to 'SQmode';
-'unsigned long fract' to 'USQmode'; 'long long fract' to 'DQmode'; and
-'unsigned long long fract' to 'UDQmode'. Similarly the fixed-point
-accumulator type 'short accum' corresponds to 'HAmode';
-'unsigned short accum' to 'UHAmode'; 'accum' to 'SAmode';
-'unsigned accum' to 'USAmode'; 'long accum' to 'DAmode';
-'unsigned long accum' to 'UDAmode'; 'long long accum' to 'TAmode'; and
-'unsigned long long accum' to 'UTAmode'.
+type `short fract' is assumed to correspond to machine mode `QQmode';
+`unsigned short fract' to `UQQmode'; `fract' to `HQmode';
+`unsigned fract' to `UHQmode'; `long fract' to `SQmode';
+`unsigned long fract' to `USQmode'; `long long fract' to `DQmode'; and
+`unsigned long long fract' to `UDQmode'. Similarly the fixed-point
+accumulator type `short accum' corresponds to `HAmode';
+`unsigned short accum' to `UHAmode'; `accum' to `SAmode';
+`unsigned accum' to `USAmode'; `long accum' to `DAmode';
+`unsigned long accum' to `UDAmode'; `long long accum' to `TAmode'; and
+`unsigned long long accum' to `UTAmode'.
4.4.1 Arithmetic functions
--------------------------
@@ -1037,8 +1040,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
fract A, unsigned short fract B)
-- Runtime Function: unsigned fract __adduhq3 (unsigned fract A,
unsigned fract B)
- -- Runtime Function: unsigned long fract __addusq3 (unsigned long fract
- A, unsigned long fract B)
+ -- Runtime Function: unsigned long fract __addusq3 (unsigned long
+ fract A, unsigned long fract B)
-- Runtime Function: unsigned long long fract __addudq3 (unsigned long
long fract A, unsigned long long fract B)
-- Runtime Function: short accum __addha3 (short accum A, short accum
@@ -1051,20 +1054,20 @@ accumulator type 'short accum' corresponds to 'HAmode';
accum A, unsigned short accum B)
-- Runtime Function: unsigned accum __addusa3 (unsigned accum A,
unsigned accum B)
- -- Runtime Function: unsigned long accum __adduda3 (unsigned long accum
- A, unsigned long accum B)
+ -- Runtime Function: unsigned long accum __adduda3 (unsigned long
+ accum A, unsigned long accum B)
-- Runtime Function: unsigned long long accum __adduta3 (unsigned long
long accum A, unsigned long long accum B)
These functions return the sum of A and B.
- -- Runtime Function: short fract __ssaddqq3 (short fract A, short fract
- B)
+ -- Runtime Function: short fract __ssaddqq3 (short fract A, short
+ fract B)
-- Runtime Function: fract __ssaddhq3 (fract A, fract B)
-- Runtime Function: long fract __ssaddsq3 (long fract A, long fract B)
-- Runtime Function: long long fract __ssadddq3 (long long fract A,
long long fract B)
- -- Runtime Function: short accum __ssaddha3 (short accum A, short accum
- B)
+ -- Runtime Function: short accum __ssaddha3 (short accum A, short
+ accum B)
-- Runtime Function: accum __ssaddsa3 (accum A, accum B)
-- Runtime Function: long accum __ssaddda3 (long accum A, long accum B)
-- Runtime Function: long long accum __ssaddta3 (long long accum A,
@@ -1099,8 +1102,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
fract A, unsigned short fract B)
-- Runtime Function: unsigned fract __subuhq3 (unsigned fract A,
unsigned fract B)
- -- Runtime Function: unsigned long fract __subusq3 (unsigned long fract
- A, unsigned long fract B)
+ -- Runtime Function: unsigned long fract __subusq3 (unsigned long
+ fract A, unsigned long fract B)
-- Runtime Function: unsigned long long fract __subudq3 (unsigned long
long fract A, unsigned long long fract B)
-- Runtime Function: short accum __subha3 (short accum A, short accum
@@ -1113,26 +1116,26 @@ accumulator type 'short accum' corresponds to 'HAmode';
accum A, unsigned short accum B)
-- Runtime Function: unsigned accum __subusa3 (unsigned accum A,
unsigned accum B)
- -- Runtime Function: unsigned long accum __subuda3 (unsigned long accum
- A, unsigned long accum B)
+ -- Runtime Function: unsigned long accum __subuda3 (unsigned long
+ accum A, unsigned long accum B)
-- Runtime Function: unsigned long long accum __subuta3 (unsigned long
long accum A, unsigned long long accum B)
- These functions return the difference of A and B; that is, 'A - B'.
+ These functions return the difference of A and B; that is, `A - B'.
- -- Runtime Function: short fract __sssubqq3 (short fract A, short fract
- B)
+ -- Runtime Function: short fract __sssubqq3 (short fract A, short
+ fract B)
-- Runtime Function: fract __sssubhq3 (fract A, fract B)
-- Runtime Function: long fract __sssubsq3 (long fract A, long fract B)
-- Runtime Function: long long fract __sssubdq3 (long long fract A,
long long fract B)
- -- Runtime Function: short accum __sssubha3 (short accum A, short accum
- B)
+ -- Runtime Function: short accum __sssubha3 (short accum A, short
+ accum B)
-- Runtime Function: accum __sssubsa3 (accum A, accum B)
-- Runtime Function: long accum __sssubda3 (long accum A, long accum B)
-- Runtime Function: long long accum __sssubta3 (long long accum A,
long long accum B)
These functions return the difference of A and B with signed
- saturation; that is, 'A - B'.
+ saturation; that is, `A - B'.
-- Runtime Function: unsigned short fract __ussubuqq3 (unsigned short
fract A, unsigned short fract B)
@@ -1151,7 +1154,7 @@ accumulator type 'short accum' corresponds to 'HAmode';
-- Runtime Function: unsigned long long accum __ussubuta3 (unsigned
long long accum A, unsigned long long accum B)
These functions return the difference of A and B with unsigned
- saturation; that is, 'A - B'.
+ saturation; that is, `A - B'.
-- Runtime Function: short fract __mulqq3 (short fract A, short fract
B)
@@ -1163,8 +1166,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
fract A, unsigned short fract B)
-- Runtime Function: unsigned fract __muluhq3 (unsigned fract A,
unsigned fract B)
- -- Runtime Function: unsigned long fract __mulusq3 (unsigned long fract
- A, unsigned long fract B)
+ -- Runtime Function: unsigned long fract __mulusq3 (unsigned long
+ fract A, unsigned long fract B)
-- Runtime Function: unsigned long long fract __muludq3 (unsigned long
long fract A, unsigned long long fract B)
-- Runtime Function: short accum __mulha3 (short accum A, short accum
@@ -1177,20 +1180,20 @@ accumulator type 'short accum' corresponds to 'HAmode';
accum A, unsigned short accum B)
-- Runtime Function: unsigned accum __mulusa3 (unsigned accum A,
unsigned accum B)
- -- Runtime Function: unsigned long accum __muluda3 (unsigned long accum
- A, unsigned long accum B)
+ -- Runtime Function: unsigned long accum __muluda3 (unsigned long
+ accum A, unsigned long accum B)
-- Runtime Function: unsigned long long accum __muluta3 (unsigned long
long accum A, unsigned long long accum B)
These functions return the product of A and B.
- -- Runtime Function: short fract __ssmulqq3 (short fract A, short fract
- B)
+ -- Runtime Function: short fract __ssmulqq3 (short fract A, short
+ fract B)
-- Runtime Function: fract __ssmulhq3 (fract A, fract B)
-- Runtime Function: long fract __ssmulsq3 (long fract A, long fract B)
-- Runtime Function: long long fract __ssmuldq3 (long long fract A,
long long fract B)
- -- Runtime Function: short accum __ssmulha3 (short accum A, short accum
- B)
+ -- Runtime Function: short accum __ssmulha3 (short accum A, short
+ accum B)
-- Runtime Function: accum __ssmulsa3 (accum A, accum B)
-- Runtime Function: long accum __ssmulda3 (long accum A, long accum B)
-- Runtime Function: long long accum __ssmulta3 (long long accum A,
@@ -1229,8 +1232,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
-- Runtime Function: long accum __divda3 (long accum A, long accum B)
-- Runtime Function: long long accum __divta3 (long long accum A, long
long accum B)
- These functions return the quotient of the signed division of A and
- B.
+ These functions return the quotient of the signed division of A
+ and B.
-- Runtime Function: unsigned short fract __udivuqq3 (unsigned short
fract A, unsigned short fract B)
@@ -1238,33 +1241,33 @@ accumulator type 'short accum' corresponds to 'HAmode';
unsigned fract B)
-- Runtime Function: unsigned long fract __udivusq3 (unsigned long
fract A, unsigned long fract B)
- -- Runtime Function: unsigned long long fract __udivudq3 (unsigned long
- long fract A, unsigned long long fract B)
+ -- Runtime Function: unsigned long long fract __udivudq3 (unsigned
+ long long fract A, unsigned long long fract B)
-- Runtime Function: unsigned short accum __udivuha3 (unsigned short
accum A, unsigned short accum B)
-- Runtime Function: unsigned accum __udivusa3 (unsigned accum A,
unsigned accum B)
-- Runtime Function: unsigned long accum __udivuda3 (unsigned long
accum A, unsigned long accum B)
- -- Runtime Function: unsigned long long accum __udivuta3 (unsigned long
- long accum A, unsigned long long accum B)
+ -- Runtime Function: unsigned long long accum __udivuta3 (unsigned
+ long long accum A, unsigned long long accum B)
These functions return the quotient of the unsigned division of A
and B.
- -- Runtime Function: short fract __ssdivqq3 (short fract A, short fract
- B)
+ -- Runtime Function: short fract __ssdivqq3 (short fract A, short
+ fract B)
-- Runtime Function: fract __ssdivhq3 (fract A, fract B)
-- Runtime Function: long fract __ssdivsq3 (long fract A, long fract B)
-- Runtime Function: long long fract __ssdivdq3 (long long fract A,
long long fract B)
- -- Runtime Function: short accum __ssdivha3 (short accum A, short accum
- B)
+ -- Runtime Function: short accum __ssdivha3 (short accum A, short
+ accum B)
-- Runtime Function: accum __ssdivsa3 (accum A, accum B)
-- Runtime Function: long accum __ssdivda3 (long accum A, long accum B)
-- Runtime Function: long long accum __ssdivta3 (long long accum A,
long long accum B)
- These functions return the quotient of the signed division of A and
- B with signed saturation.
+ These functions return the quotient of the signed division of A
+ and B with signed saturation.
-- Runtime Function: unsigned short fract __usdivuqq3 (unsigned short
fract A, unsigned short fract B)
@@ -1292,8 +1295,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
-- Runtime Function: unsigned short fract __neguqq2 (unsigned short
fract A)
-- Runtime Function: unsigned fract __neguhq2 (unsigned fract A)
- -- Runtime Function: unsigned long fract __negusq2 (unsigned long fract
- A)
+ -- Runtime Function: unsigned long fract __negusq2 (unsigned long
+ fract A)
-- Runtime Function: unsigned long long fract __negudq2 (unsigned long
long fract A)
-- Runtime Function: short accum __negha2 (short accum A)
@@ -1303,8 +1306,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
-- Runtime Function: unsigned short accum __neguha2 (unsigned short
accum A)
-- Runtime Function: unsigned accum __negusa2 (unsigned accum A)
- -- Runtime Function: unsigned long accum __neguda2 (unsigned long accum
- A)
+ -- Runtime Function: unsigned long accum __neguda2 (unsigned long
+ accum A)
-- Runtime Function: unsigned long long accum __neguta2 (unsigned long
long accum A)
These functions return the negation of A.
@@ -1346,8 +1349,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
B)
-- Runtime Function: unsigned long fract __ashlusq3 (unsigned long
fract A, int B)
- -- Runtime Function: unsigned long long fract __ashludq3 (unsigned long
- long fract A, int B)
+ -- Runtime Function: unsigned long long fract __ashludq3 (unsigned
+ long long fract A, int B)
-- Runtime Function: short accum __ashlha3 (short accum A, int B)
-- Runtime Function: accum __ashlsa3 (accum A, int B)
-- Runtime Function: long accum __ashlda3 (long accum A, int B)
@@ -1359,8 +1362,8 @@ accumulator type 'short accum' corresponds to 'HAmode';
B)
-- Runtime Function: unsigned long accum __ashluda3 (unsigned long
accum A, int B)
- -- Runtime Function: unsigned long long accum __ashluta3 (unsigned long
- long accum A, int B)
+ -- Runtime Function: unsigned long long accum __ashluta3 (unsigned
+ long long accum A, int B)
These functions return the result of shifting A left by B bits.
-- Runtime Function: short fract __ashrqq3 (short fract A, int B)
@@ -1382,16 +1385,16 @@ accumulator type 'short accum' corresponds to 'HAmode';
B)
-- Runtime Function: unsigned long fract __lshrusq3 (unsigned long
fract A, int B)
- -- Runtime Function: unsigned long long fract __lshrudq3 (unsigned long
- long fract A, int B)
+ -- Runtime Function: unsigned long long fract __lshrudq3 (unsigned
+ long long fract A, int B)
-- Runtime Function: unsigned short accum __lshruha3 (unsigned short
accum A, int B)
-- Runtime Function: unsigned accum __lshrusa3 (unsigned accum A, int
B)
-- Runtime Function: unsigned long accum __lshruda3 (unsigned long
accum A, int B)
- -- Runtime Function: unsigned long long accum __lshruta3 (unsigned long
- long accum A, int B)
+ -- Runtime Function: unsigned long long accum __lshruta3 (unsigned
+ long long accum A, int B)
These functions return the result of logically shifting A right by
B bits.
@@ -1404,27 +1407,27 @@ accumulator type 'short accum' corresponds to 'HAmode';
-- Runtime Function: long accum __ssashlda3 (long accum A, int B)
-- Runtime Function: long long accum __ssashlta3 (long long accum A,
int B)
- These functions return the result of shifting A left by B bits with
- signed saturation.
+ These functions return the result of shifting A left by B bits
+ with signed saturation.
-- Runtime Function: unsigned short fract __usashluqq3 (unsigned short
fract A, int B)
- -- Runtime Function: unsigned fract __usashluhq3 (unsigned fract A, int
- B)
+ -- Runtime Function: unsigned fract __usashluhq3 (unsigned fract A,
+ int B)
-- Runtime Function: unsigned long fract __usashlusq3 (unsigned long
fract A, int B)
-- Runtime Function: unsigned long long fract __usashludq3 (unsigned
long long fract A, int B)
-- Runtime Function: unsigned short accum __usashluha3 (unsigned short
accum A, int B)
- -- Runtime Function: unsigned accum __usashlusa3 (unsigned accum A, int
- B)
+ -- Runtime Function: unsigned accum __usashlusa3 (unsigned accum A,
+ int B)
-- Runtime Function: unsigned long accum __usashluda3 (unsigned long
accum A, int B)
-- Runtime Function: unsigned long long accum __usashluta3 (unsigned
long long accum A, int B)
- These functions return the result of shifting A left by B bits with
- unsigned saturation.
+ These functions return the result of shifting A left by B bits
+ with unsigned saturation.
4.4.2 Comparison functions
--------------------------
@@ -1478,13 +1481,13 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short fract __fractqquqq (short fract A)
-- Runtime Function: unsigned fract __fractqquhq (short fract A)
-- Runtime Function: unsigned long fract __fractqqusq (short fract A)
- -- Runtime Function: unsigned long long fract __fractqqudq (short fract
- A)
+ -- Runtime Function: unsigned long long fract __fractqqudq (short
+ fract A)
-- Runtime Function: unsigned short accum __fractqquha (short fract A)
-- Runtime Function: unsigned accum __fractqqusa (short fract A)
-- Runtime Function: unsigned long accum __fractqquda (short fract A)
- -- Runtime Function: unsigned long long accum __fractqquta (short fract
- A)
+ -- Runtime Function: unsigned long long accum __fractqquta (short
+ fract A)
-- Runtime Function: signed char __fractqqqi (short fract A)
-- Runtime Function: short __fractqqhi (short fract A)
-- Runtime Function: int __fractqqsi (short fract A)
@@ -1545,15 +1548,15 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: accum __fractdqsa (long long fract A)
-- Runtime Function: long accum __fractdqda (long long fract A)
-- Runtime Function: long long accum __fractdqta (long long fract A)
- -- Runtime Function: unsigned short fract __fractdquqq (long long fract
- A)
+ -- Runtime Function: unsigned short fract __fractdquqq (long long
+ fract A)
-- Runtime Function: unsigned fract __fractdquhq (long long fract A)
-- Runtime Function: unsigned long fract __fractdqusq (long long fract
A)
-- Runtime Function: unsigned long long fract __fractdqudq (long long
fract A)
- -- Runtime Function: unsigned short accum __fractdquha (long long fract
- A)
+ -- Runtime Function: unsigned short accum __fractdquha (long long
+ fract A)
-- Runtime Function: unsigned accum __fractdqusa (long long fract A)
-- Runtime Function: unsigned long accum __fractdquda (long long fract
A)
@@ -1576,13 +1579,13 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short fract __fracthauqq (short accum A)
-- Runtime Function: unsigned fract __fracthauhq (short accum A)
-- Runtime Function: unsigned long fract __fracthausq (short accum A)
- -- Runtime Function: unsigned long long fract __fracthaudq (short accum
- A)
+ -- Runtime Function: unsigned long long fract __fracthaudq (short
+ accum A)
-- Runtime Function: unsigned short accum __fracthauha (short accum A)
-- Runtime Function: unsigned accum __fracthausa (short accum A)
-- Runtime Function: unsigned long accum __fracthauda (short accum A)
- -- Runtime Function: unsigned long long accum __fracthauta (short accum
- A)
+ -- Runtime Function: unsigned long long accum __fracthauta (short
+ accum A)
-- Runtime Function: signed char __fracthaqi (short accum A)
-- Runtime Function: short __fracthahi (short accum A)
-- Runtime Function: int __fracthasi (short accum A)
@@ -1643,15 +1646,15 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: short accum __fracttaha2 (long long accum A)
-- Runtime Function: accum __fracttasa2 (long long accum A)
-- Runtime Function: long accum __fracttada2 (long long accum A)
- -- Runtime Function: unsigned short fract __fracttauqq (long long accum
- A)
+ -- Runtime Function: unsigned short fract __fracttauqq (long long
+ accum A)
-- Runtime Function: unsigned fract __fracttauhq (long long accum A)
-- Runtime Function: unsigned long fract __fracttausq (long long accum
A)
-- Runtime Function: unsigned long long fract __fracttaudq (long long
accum A)
- -- Runtime Function: unsigned short accum __fracttauha (long long accum
- A)
+ -- Runtime Function: unsigned short accum __fracttauha (long long
+ accum A)
-- Runtime Function: unsigned accum __fracttausa (long long accum A)
-- Runtime Function: unsigned long accum __fracttauda (long long accum
A)
@@ -1667,23 +1670,23 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: short fract __fractuqqqq (unsigned short fract A)
-- Runtime Function: fract __fractuqqhq (unsigned short fract A)
-- Runtime Function: long fract __fractuqqsq (unsigned short fract A)
- -- Runtime Function: long long fract __fractuqqdq (unsigned short fract
- A)
+ -- Runtime Function: long long fract __fractuqqdq (unsigned short
+ fract A)
-- Runtime Function: short accum __fractuqqha (unsigned short fract A)
-- Runtime Function: accum __fractuqqsa (unsigned short fract A)
-- Runtime Function: long accum __fractuqqda (unsigned short fract A)
- -- Runtime Function: long long accum __fractuqqta (unsigned short fract
- A)
- -- Runtime Function: unsigned fract __fractuqquhq2 (unsigned short
+ -- Runtime Function: long long accum __fractuqqta (unsigned short
fract A)
- -- Runtime Function: unsigned long fract __fractuqqusq2 (unsigned short
+ -- Runtime Function: unsigned fract __fractuqquhq2 (unsigned short
fract A)
+ -- Runtime Function: unsigned long fract __fractuqqusq2 (unsigned
+ short fract A)
-- Runtime Function: unsigned long long fract __fractuqqudq2 (unsigned
short fract A)
- -- Runtime Function: unsigned short accum __fractuqquha (unsigned short
+ -- Runtime Function: unsigned short accum __fractuqquha (unsigned
+ short fract A)
+ -- Runtime Function: unsigned accum __fractuqqusa (unsigned short
fract A)
- -- Runtime Function: unsigned accum __fractuqqusa (unsigned short fract
- A)
-- Runtime Function: unsigned long accum __fractuqquda (unsigned short
fract A)
-- Runtime Function: unsigned long long accum __fractuqquta (unsigned
@@ -1705,12 +1708,12 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: long long accum __fractuhqta (unsigned fract A)
-- Runtime Function: unsigned short fract __fractuhquqq2 (unsigned
fract A)
- -- Runtime Function: unsigned long fract __fractuhqusq2 (unsigned fract
- A)
+ -- Runtime Function: unsigned long fract __fractuhqusq2 (unsigned
+ fract A)
-- Runtime Function: unsigned long long fract __fractuhqudq2 (unsigned
fract A)
- -- Runtime Function: unsigned short accum __fractuhquha (unsigned fract
- A)
+ -- Runtime Function: unsigned short accum __fractuhquha (unsigned
+ fract A)
-- Runtime Function: unsigned accum __fractuhqusa (unsigned fract A)
-- Runtime Function: unsigned long accum __fractuhquda (unsigned fract
A)
@@ -1733,10 +1736,10 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: long accum __fractusqda (unsigned long fract A)
-- Runtime Function: long long accum __fractusqta (unsigned long fract
A)
- -- Runtime Function: unsigned short fract __fractusquqq2 (unsigned long
+ -- Runtime Function: unsigned short fract __fractusquqq2 (unsigned
+ long fract A)
+ -- Runtime Function: unsigned fract __fractusquhq2 (unsigned long
fract A)
- -- Runtime Function: unsigned fract __fractusquhq2 (unsigned long fract
- A)
-- Runtime Function: unsigned long long fract __fractusqudq2 (unsigned
long fract A)
-- Runtime Function: unsigned short accum __fractusquha (unsigned long
@@ -1754,22 +1757,22 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: long long __fractusqti (unsigned long fract A)
-- Runtime Function: float __fractusqsf (unsigned long fract A)
-- Runtime Function: double __fractusqdf (unsigned long fract A)
- -- Runtime Function: short fract __fractudqqq (unsigned long long fract
- A)
+ -- Runtime Function: short fract __fractudqqq (unsigned long long
+ fract A)
-- Runtime Function: fract __fractudqhq (unsigned long long fract A)
-- Runtime Function: long fract __fractudqsq (unsigned long long fract
A)
-- Runtime Function: long long fract __fractudqdq (unsigned long long
fract A)
- -- Runtime Function: short accum __fractudqha (unsigned long long fract
- A)
+ -- Runtime Function: short accum __fractudqha (unsigned long long
+ fract A)
-- Runtime Function: accum __fractudqsa (unsigned long long fract A)
-- Runtime Function: long accum __fractudqda (unsigned long long fract
A)
-- Runtime Function: long long accum __fractudqta (unsigned long long
fract A)
- -- Runtime Function: unsigned short fract __fractudquqq2 (unsigned long
- long fract A)
+ -- Runtime Function: unsigned short fract __fractudquqq2 (unsigned
+ long long fract A)
-- Runtime Function: unsigned fract __fractudquhq2 (unsigned long long
fract A)
-- Runtime Function: unsigned long fract __fractudqusq2 (unsigned long
@@ -1782,8 +1785,8 @@ returned result using either signed or unsigned comparison.
long fract A)
-- Runtime Function: unsigned long long accum __fractudquta (unsigned
long long fract A)
- -- Runtime Function: signed char __fractudqqi (unsigned long long fract
- A)
+ -- Runtime Function: signed char __fractudqqi (unsigned long long
+ fract A)
-- Runtime Function: short __fractudqhi (unsigned long long fract A)
-- Runtime Function: int __fractudqsi (unsigned long long fract A)
-- Runtime Function: long __fractudqdi (unsigned long long fract A)
@@ -1794,25 +1797,25 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: short fract __fractuhaqq (unsigned short accum A)
-- Runtime Function: fract __fractuhahq (unsigned short accum A)
-- Runtime Function: long fract __fractuhasq (unsigned short accum A)
- -- Runtime Function: long long fract __fractuhadq (unsigned short accum
- A)
+ -- Runtime Function: long long fract __fractuhadq (unsigned short
+ accum A)
-- Runtime Function: short accum __fractuhaha (unsigned short accum A)
-- Runtime Function: accum __fractuhasa (unsigned short accum A)
-- Runtime Function: long accum __fractuhada (unsigned short accum A)
- -- Runtime Function: long long accum __fractuhata (unsigned short accum
- A)
- -- Runtime Function: unsigned short fract __fractuhauqq (unsigned short
+ -- Runtime Function: long long accum __fractuhata (unsigned short
+ accum A)
+ -- Runtime Function: unsigned short fract __fractuhauqq (unsigned
+ short accum A)
+ -- Runtime Function: unsigned fract __fractuhauhq (unsigned short
accum A)
- -- Runtime Function: unsigned fract __fractuhauhq (unsigned short accum
- A)
-- Runtime Function: unsigned long fract __fractuhausq (unsigned short
accum A)
-- Runtime Function: unsigned long long fract __fractuhaudq (unsigned
short accum A)
-- Runtime Function: unsigned accum __fractuhausa2 (unsigned short
accum A)
- -- Runtime Function: unsigned long accum __fractuhauda2 (unsigned short
- accum A)
+ -- Runtime Function: unsigned long accum __fractuhauda2 (unsigned
+ short accum A)
-- Runtime Function: unsigned long long accum __fractuhauta2 (unsigned
short accum A)
-- Runtime Function: signed char __fractuhaqi (unsigned short accum A)
@@ -1830,8 +1833,8 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: accum __fractusasa (unsigned accum A)
-- Runtime Function: long accum __fractusada (unsigned accum A)
-- Runtime Function: long long accum __fractusata (unsigned accum A)
- -- Runtime Function: unsigned short fract __fractusauqq (unsigned accum
- A)
+ -- Runtime Function: unsigned short fract __fractusauqq (unsigned
+ accum A)
-- Runtime Function: unsigned fract __fractusauhq (unsigned accum A)
-- Runtime Function: unsigned long fract __fractusausq (unsigned accum
A)
@@ -1839,8 +1842,8 @@ returned result using either signed or unsigned comparison.
accum A)
-- Runtime Function: unsigned short accum __fractusauha2 (unsigned
accum A)
- -- Runtime Function: unsigned long accum __fractusauda2 (unsigned accum
- A)
+ -- Runtime Function: unsigned long accum __fractusauda2 (unsigned
+ accum A)
-- Runtime Function: unsigned long long accum __fractusauta2 (unsigned
accum A)
-- Runtime Function: signed char __fractusaqi (unsigned accum A)
@@ -1868,10 +1871,10 @@ returned result using either signed or unsigned comparison.
accum A)
-- Runtime Function: unsigned long long fract __fractudaudq (unsigned
long accum A)
- -- Runtime Function: unsigned short accum __fractudauha2 (unsigned long
+ -- Runtime Function: unsigned short accum __fractudauha2 (unsigned
+ long accum A)
+ -- Runtime Function: unsigned accum __fractudausa2 (unsigned long
accum A)
- -- Runtime Function: unsigned accum __fractudausa2 (unsigned long accum
- A)
-- Runtime Function: unsigned long long accum __fractudauta2 (unsigned
long accum A)
-- Runtime Function: signed char __fractudaqi (unsigned long accum A)
@@ -1881,15 +1884,15 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: long long __fractudati (unsigned long accum A)
-- Runtime Function: float __fractudasf (unsigned long accum A)
-- Runtime Function: double __fractudadf (unsigned long accum A)
- -- Runtime Function: short fract __fractutaqq (unsigned long long accum
- A)
+ -- Runtime Function: short fract __fractutaqq (unsigned long long
+ accum A)
-- Runtime Function: fract __fractutahq (unsigned long long accum A)
-- Runtime Function: long fract __fractutasq (unsigned long long accum
A)
-- Runtime Function: long long fract __fractutadq (unsigned long long
accum A)
- -- Runtime Function: short accum __fractutaha (unsigned long long accum
- A)
+ -- Runtime Function: short accum __fractutaha (unsigned long long
+ accum A)
-- Runtime Function: accum __fractutasa (unsigned long long accum A)
-- Runtime Function: long accum __fractutada (unsigned long long accum
A)
@@ -1903,14 +1906,14 @@ returned result using either signed or unsigned comparison.
long accum A)
-- Runtime Function: unsigned long long fract __fractutaudq (unsigned
long long accum A)
- -- Runtime Function: unsigned short accum __fractutauha2 (unsigned long
- long accum A)
+ -- Runtime Function: unsigned short accum __fractutauha2 (unsigned
+ long long accum A)
-- Runtime Function: unsigned accum __fractutausa2 (unsigned long long
accum A)
-- Runtime Function: unsigned long accum __fractutauda2 (unsigned long
long accum A)
- -- Runtime Function: signed char __fractutaqi (unsigned long long accum
- A)
+ -- Runtime Function: signed char __fractutaqi (unsigned long long
+ accum A)
-- Runtime Function: short __fractutahi (unsigned long long accum A)
-- Runtime Function: int __fractutasi (unsigned long long accum A)
-- Runtime Function: long __fractutadi (unsigned long long accum A)
@@ -1929,13 +1932,13 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short fract __fractqiuqq (signed char A)
-- Runtime Function: unsigned fract __fractqiuhq (signed char A)
-- Runtime Function: unsigned long fract __fractqiusq (signed char A)
- -- Runtime Function: unsigned long long fract __fractqiudq (signed char
- A)
+ -- Runtime Function: unsigned long long fract __fractqiudq (signed
+ char A)
-- Runtime Function: unsigned short accum __fractqiuha (signed char A)
-- Runtime Function: unsigned accum __fractqiusa (signed char A)
-- Runtime Function: unsigned long accum __fractqiuda (signed char A)
- -- Runtime Function: unsigned long long accum __fractqiuta (signed char
- A)
+ -- Runtime Function: unsigned long long accum __fractqiuta (signed
+ char A)
-- Runtime Function: short fract __fracthiqq (short A)
-- Runtime Function: fract __fracthihq (short A)
-- Runtime Function: long fract __fracthisq (short A)
@@ -2539,8 +2542,8 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short __fractunsdqhi (long long fract A)
-- Runtime Function: unsigned int __fractunsdqsi (long long fract A)
-- Runtime Function: unsigned long __fractunsdqdi (long long fract A)
- -- Runtime Function: unsigned long long __fractunsdqti (long long fract
- A)
+ -- Runtime Function: unsigned long long __fractunsdqti (long long
+ fract A)
-- Runtime Function: unsigned char __fractunshaqi (short accum A)
-- Runtime Function: unsigned short __fractunshahi (short accum A)
-- Runtime Function: unsigned int __fractunshasi (short accum A)
@@ -2560,38 +2563,38 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short __fractunstahi (long long accum A)
-- Runtime Function: unsigned int __fractunstasi (long long accum A)
-- Runtime Function: unsigned long __fractunstadi (long long accum A)
- -- Runtime Function: unsigned long long __fractunstati (long long accum
- A)
+ -- Runtime Function: unsigned long long __fractunstati (long long
+ accum A)
-- Runtime Function: unsigned char __fractunsuqqqi (unsigned short
fract A)
-- Runtime Function: unsigned short __fractunsuqqhi (unsigned short
fract A)
- -- Runtime Function: unsigned int __fractunsuqqsi (unsigned short fract
- A)
- -- Runtime Function: unsigned long __fractunsuqqdi (unsigned short
+ -- Runtime Function: unsigned int __fractunsuqqsi (unsigned short
fract A)
- -- Runtime Function: unsigned long long __fractunsuqqti (unsigned short
+ -- Runtime Function: unsigned long __fractunsuqqdi (unsigned short
fract A)
+ -- Runtime Function: unsigned long long __fractunsuqqti (unsigned
+ short fract A)
-- Runtime Function: unsigned char __fractunsuhqqi (unsigned fract A)
-- Runtime Function: unsigned short __fractunsuhqhi (unsigned fract A)
-- Runtime Function: unsigned int __fractunsuhqsi (unsigned fract A)
-- Runtime Function: unsigned long __fractunsuhqdi (unsigned fract A)
- -- Runtime Function: unsigned long long __fractunsuhqti (unsigned fract
- A)
- -- Runtime Function: unsigned char __fractunsusqqi (unsigned long fract
- A)
+ -- Runtime Function: unsigned long long __fractunsuhqti (unsigned
+ fract A)
+ -- Runtime Function: unsigned char __fractunsusqqi (unsigned long
+ fract A)
-- Runtime Function: unsigned short __fractunsusqhi (unsigned long
fract A)
-- Runtime Function: unsigned int __fractunsusqsi (unsigned long fract
A)
- -- Runtime Function: unsigned long __fractunsusqdi (unsigned long fract
- A)
+ -- Runtime Function: unsigned long __fractunsusqdi (unsigned long
+ fract A)
-- Runtime Function: unsigned long long __fractunsusqti (unsigned long
fract A)
-- Runtime Function: unsigned char __fractunsudqqi (unsigned long long
fract A)
- -- Runtime Function: unsigned short __fractunsudqhi (unsigned long long
- fract A)
+ -- Runtime Function: unsigned short __fractunsudqhi (unsigned long
+ long fract A)
-- Runtime Function: unsigned int __fractunsudqsi (unsigned long long
fract A)
-- Runtime Function: unsigned long __fractunsudqdi (unsigned long long
@@ -2602,32 +2605,32 @@ returned result using either signed or unsigned comparison.
accum A)
-- Runtime Function: unsigned short __fractunsuhahi (unsigned short
accum A)
- -- Runtime Function: unsigned int __fractunsuhasi (unsigned short accum
- A)
- -- Runtime Function: unsigned long __fractunsuhadi (unsigned short
+ -- Runtime Function: unsigned int __fractunsuhasi (unsigned short
accum A)
- -- Runtime Function: unsigned long long __fractunsuhati (unsigned short
+ -- Runtime Function: unsigned long __fractunsuhadi (unsigned short
accum A)
+ -- Runtime Function: unsigned long long __fractunsuhati (unsigned
+ short accum A)
-- Runtime Function: unsigned char __fractunsusaqi (unsigned accum A)
-- Runtime Function: unsigned short __fractunsusahi (unsigned accum A)
-- Runtime Function: unsigned int __fractunsusasi (unsigned accum A)
-- Runtime Function: unsigned long __fractunsusadi (unsigned accum A)
- -- Runtime Function: unsigned long long __fractunsusati (unsigned accum
- A)
- -- Runtime Function: unsigned char __fractunsudaqi (unsigned long accum
- A)
+ -- Runtime Function: unsigned long long __fractunsusati (unsigned
+ accum A)
+ -- Runtime Function: unsigned char __fractunsudaqi (unsigned long
+ accum A)
-- Runtime Function: unsigned short __fractunsudahi (unsigned long
accum A)
-- Runtime Function: unsigned int __fractunsudasi (unsigned long accum
A)
- -- Runtime Function: unsigned long __fractunsudadi (unsigned long accum
- A)
+ -- Runtime Function: unsigned long __fractunsudadi (unsigned long
+ accum A)
-- Runtime Function: unsigned long long __fractunsudati (unsigned long
accum A)
-- Runtime Function: unsigned char __fractunsutaqi (unsigned long long
accum A)
- -- Runtime Function: unsigned short __fractunsutahi (unsigned long long
- accum A)
+ -- Runtime Function: unsigned short __fractunsutahi (unsigned long
+ long accum A)
-- Runtime Function: unsigned int __fractunsutasi (unsigned long long
accum A)
-- Runtime Function: unsigned long __fractunsutadi (unsigned long long
@@ -2645,17 +2648,17 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short fract __fractunsqiuqq (unsigned
char A)
-- Runtime Function: unsigned fract __fractunsqiuhq (unsigned char A)
- -- Runtime Function: unsigned long fract __fractunsqiusq (unsigned char
- A)
- -- Runtime Function: unsigned long long fract __fractunsqiudq (unsigned
+ -- Runtime Function: unsigned long fract __fractunsqiusq (unsigned
char A)
+ -- Runtime Function: unsigned long long fract __fractunsqiudq
+ (unsigned char A)
-- Runtime Function: unsigned short accum __fractunsqiuha (unsigned
char A)
-- Runtime Function: unsigned accum __fractunsqiusa (unsigned char A)
- -- Runtime Function: unsigned long accum __fractunsqiuda (unsigned char
- A)
- -- Runtime Function: unsigned long long accum __fractunsqiuta (unsigned
+ -- Runtime Function: unsigned long accum __fractunsqiuda (unsigned
char A)
+ -- Runtime Function: unsigned long long accum __fractunsqiuta
+ (unsigned char A)
-- Runtime Function: short fract __fractunshiqq (unsigned short A)
-- Runtime Function: fract __fractunshihq (unsigned short A)
-- Runtime Function: long fract __fractunshisq (unsigned short A)
@@ -2669,15 +2672,15 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned fract __fractunshiuhq (unsigned short A)
-- Runtime Function: unsigned long fract __fractunshiusq (unsigned
short A)
- -- Runtime Function: unsigned long long fract __fractunshiudq (unsigned
- short A)
+ -- Runtime Function: unsigned long long fract __fractunshiudq
+ (unsigned short A)
-- Runtime Function: unsigned short accum __fractunshiuha (unsigned
short A)
-- Runtime Function: unsigned accum __fractunshiusa (unsigned short A)
-- Runtime Function: unsigned long accum __fractunshiuda (unsigned
short A)
- -- Runtime Function: unsigned long long accum __fractunshiuta (unsigned
- short A)
+ -- Runtime Function: unsigned long long accum __fractunshiuta
+ (unsigned short A)
-- Runtime Function: short fract __fractunssiqq (unsigned int A)
-- Runtime Function: fract __fractunssihq (unsigned int A)
-- Runtime Function: long fract __fractunssisq (unsigned int A)
@@ -2686,20 +2689,20 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: accum __fractunssisa (unsigned int A)
-- Runtime Function: long accum __fractunssida (unsigned int A)
-- Runtime Function: long long accum __fractunssita (unsigned int A)
- -- Runtime Function: unsigned short fract __fractunssiuqq (unsigned int
- A)
+ -- Runtime Function: unsigned short fract __fractunssiuqq (unsigned
+ int A)
-- Runtime Function: unsigned fract __fractunssiuhq (unsigned int A)
-- Runtime Function: unsigned long fract __fractunssiusq (unsigned int
A)
- -- Runtime Function: unsigned long long fract __fractunssiudq (unsigned
+ -- Runtime Function: unsigned long long fract __fractunssiudq
+ (unsigned int A)
+ -- Runtime Function: unsigned short accum __fractunssiuha (unsigned
int A)
- -- Runtime Function: unsigned short accum __fractunssiuha (unsigned int
- A)
-- Runtime Function: unsigned accum __fractunssiusa (unsigned int A)
-- Runtime Function: unsigned long accum __fractunssiuda (unsigned int
A)
- -- Runtime Function: unsigned long long accum __fractunssiuta (unsigned
- int A)
+ -- Runtime Function: unsigned long long accum __fractunssiuta
+ (unsigned int A)
-- Runtime Function: short fract __fractunsdiqq (unsigned long A)
-- Runtime Function: fract __fractunsdihq (unsigned long A)
-- Runtime Function: long fract __fractunsdisq (unsigned long A)
@@ -2711,43 +2714,43 @@ returned result using either signed or unsigned comparison.
-- Runtime Function: unsigned short fract __fractunsdiuqq (unsigned
long A)
-- Runtime Function: unsigned fract __fractunsdiuhq (unsigned long A)
- -- Runtime Function: unsigned long fract __fractunsdiusq (unsigned long
- A)
- -- Runtime Function: unsigned long long fract __fractunsdiudq (unsigned
+ -- Runtime Function: unsigned long fract __fractunsdiusq (unsigned
long A)
+ -- Runtime Function: unsigned long long fract __fractunsdiudq
+ (unsigned long A)
-- Runtime Function: unsigned short accum __fractunsdiuha (unsigned
long A)
-- Runtime Function: unsigned accum __fractunsdiusa (unsigned long A)
- -- Runtime Function: unsigned long accum __fractunsdiuda (unsigned long
- A)
- -- Runtime Function: unsigned long long accum __fractunsdiuta (unsigned
+ -- Runtime Function: unsigned long accum __fractunsdiuda (unsigned
long A)
+ -- Runtime Function: unsigned long long accum __fractunsdiuta
+ (unsigned long A)
-- Runtime Function: short fract __fractunstiqq (unsigned long long A)
-- Runtime Function: fract __fractunstihq (unsigned long long A)
-- Runtime Function: long fract __fractunstisq (unsigned long long A)
- -- Runtime Function: long long fract __fractunstidq (unsigned long long
- A)
+ -- Runtime Function: long long fract __fractunstidq (unsigned long
+ long A)
-- Runtime Function: short accum __fractunstiha (unsigned long long A)
-- Runtime Function: accum __fractunstisa (unsigned long long A)
-- Runtime Function: long accum __fractunstida (unsigned long long A)
- -- Runtime Function: long long accum __fractunstita (unsigned long long
- A)
+ -- Runtime Function: long long accum __fractunstita (unsigned long
+ long A)
-- Runtime Function: unsigned short fract __fractunstiuqq (unsigned
long long A)
- -- Runtime Function: unsigned fract __fractunstiuhq (unsigned long long
- A)
- -- Runtime Function: unsigned long fract __fractunstiusq (unsigned long
+ -- Runtime Function: unsigned fract __fractunstiuhq (unsigned long
long A)
- -- Runtime Function: unsigned long long fract __fractunstiudq (unsigned
+ -- Runtime Function: unsigned long fract __fractunstiusq (unsigned
long long A)
+ -- Runtime Function: unsigned long long fract __fractunstiudq
+ (unsigned long long A)
-- Runtime Function: unsigned short accum __fractunstiuha (unsigned
long long A)
- -- Runtime Function: unsigned accum __fractunstiusa (unsigned long long
- A)
- -- Runtime Function: unsigned long accum __fractunstiuda (unsigned long
+ -- Runtime Function: unsigned accum __fractunstiusa (unsigned long
long A)
- -- Runtime Function: unsigned long long accum __fractunstiuta (unsigned
+ -- Runtime Function: unsigned long accum __fractunstiuda (unsigned
long long A)
+ -- Runtime Function: unsigned long long accum __fractunstiuta
+ (unsigned long long A)
These functions convert from fractionals to unsigned
non-fractionals; and from unsigned non-fractionals to fractionals,
without saturation.
@@ -2940,7 +2943,7 @@ File: gccint.info, Node: Miscellaneous routines, Prev: Exception handling rout
-- Runtime Function: void * __splitstack_find (void *SEGMENT_ARG, void
*SP, size_t LEN, void **NEXT_SEGMENT, void **NEXT_SP, void
**INITIAL_SP)
- When using '-fsplit-stack', this call may be used to iterate over
+ When using `-fsplit-stack', this call may be used to iterate over
the stack segments. It may be called like this:
void *next_segment = NULL;
void *next_sp = NULL;
@@ -2961,15 +2964,15 @@ File: gccint.info, Node: Miscellaneous routines, Prev: Exception handling rout
with the SEGMENT_ARG and SP arguments NULL, to pass NEXT_SEGMENT,
NEXT_SP, and INITIAL_SP to a different thread, and then to suspend
one way or another. A different thread may run the subsequent
- '__splitstack_find' iterations. Of course, this will only work if
+ `__splitstack_find' iterations. Of course, this will only work if
the first thread is suspended while the second thread is calling
- '__splitstack_find'. If not, the second thread could be looking at
- the stack while it is changing, and anything could happen.
+ `__splitstack_find'. If not, the second thread could be looking
+ at the stack while it is changing, and anything could happen.
-- Variable: __morestack_segments
-- Variable: __morestack_current_segment
-- Variable: __morestack_initial_sp
- Internal variables used by the '-fsplit-stack' implementation.
+ Internal variables used by the `-fsplit-stack' implementation.

File: gccint.info, Node: Languages, Next: Source Tree, Prev: Libgcc, Up: Top
@@ -2978,7 +2981,7 @@ File: gccint.info, Node: Languages, Next: Source Tree, Prev: Libgcc, Up: Top
****************************
The interface to front ends for languages in GCC, and in particular the
-'tree' structure (*note GENERIC::), was initially designed for C, and
+`tree' structure (*note GENERIC::), was initially designed for C, and
many aspects of it are still somewhat biased towards C and C-like
languages. It is, however, reasonably well suited to other procedural
languages, and front ends for many such languages have been written for
@@ -2990,15 +2993,17 @@ GCC, has several advantages:
* GCC front ends benefit from the support for many different target
machines already present in GCC.
+
* GCC front ends benefit from all the optimizations in GCC. Some of
these, such as alias analysis, may work better when GCC is
compiling directly from source code then when it is compiling from
generated C code.
+
* Better debugging information is generated when compiling directly
from source code than when going via intermediate generated C code.
- Because of the advantages of writing a compiler as a GCC front end, GCC
-front ends have also been created for languages very different from
+ Because of the advantages of writing a compiler as a GCC front end,
+GCC front ends have also been created for languages very different from
those for which GCC was designed, such as the declarative
logic/functional language Mercury. For these reasons, it may also be
useful to implement compilers created for specialized purposes (for
@@ -3010,16 +3015,16 @@ File: gccint.info, Node: Source Tree, Next: Testsuites, Prev: Languages, Up:
6 Source Tree Structure and Build System
****************************************
-This chapter describes the structure of the GCC source tree, and how GCC
-is built. The user documentation for building and installing GCC is in
-a separate manual (<http://gcc.gnu.org/install/>), with which it is
-presumed that you are familiar.
+This chapter describes the structure of the GCC source tree, and how
+GCC is built. The user documentation for building and installing GCC
+is in a separate manual (`http://gcc.gnu.org/install/'), with which it
+is presumed that you are familiar.
* Menu:
* Configure Terms:: Configuration terminology and history.
* Top Level:: The top level source directory.
-* gcc Directory:: The 'gcc' subdirectory.
+* gcc Directory:: The `gcc' subdirectory.

File: gccint.info, Node: Configure Terms, Next: Top Level, Up: Source Tree
@@ -3036,46 +3041,47 @@ know.
There are three system names that the build knows about: the machine
you are building on ("build"), the machine that you are building for
("host"), and the machine that GCC will produce code for ("target").
-When you configure GCC, you specify these with '--build=', '--host=',
-and '--target='.
+When you configure GCC, you specify these with `--build=', `--host=',
+and `--target='.
Specifying the host without specifying the build should be avoided, as
-'configure' may (and once did) assume that the host you specify is also
+`configure' may (and once did) assume that the host you specify is also
the build, which may not be true.
- If build, host, and target are all the same, this is called a "native".
-If build and host are the same but target is different, this is called a
-"cross". If build, host, and target are all different this is called a
-"canadian" (for obscure reasons dealing with Canada's political party
-and the background of the person working on the build at that time). If
-host and target are the same, but build is different, you are using a
-cross-compiler to build a native for a different system. Some people
-call this a "host-x-host", "crossed native", or "cross-built native".
-If build and target are the same, but host is different, you are using a
-cross compiler to build a cross compiler that produces code for the
-machine you're building on. This is rare, so there is no common way of
-describing it. There is a proposal to call this a "crossback".
+ If build, host, and target are all the same, this is called a
+"native". If build and host are the same but target is different, this
+is called a "cross". If build, host, and target are all different this
+is called a "canadian" (for obscure reasons dealing with Canada's
+political party and the background of the person working on the build
+at that time). If host and target are the same, but build is
+different, you are using a cross-compiler to build a native for a
+different system. Some people call this a "host-x-host", "crossed
+native", or "cross-built native". If build and target are the same,
+but host is different, you are using a cross compiler to build a cross
+compiler that produces code for the machine you're building on. This
+is rare, so there is no common way of describing it. There is a
+proposal to call this a "crossback".
If build and host are the same, the GCC you are building will also be
-used to build the target libraries (like 'libstdc++'). If build and
+used to build the target libraries (like `libstdc++'). If build and
host are different, you must have already built and installed a cross
compiler that will be used to build the target libraries (if you
-configured with '--target=foo-bar', this compiler will be called
-'foo-bar-gcc').
+configured with `--target=foo-bar', this compiler will be called
+`foo-bar-gcc').
In the case of target libraries, the machine you're building for is the
-machine you specified with '--target'. So, build is the machine you're
+machine you specified with `--target'. So, build is the machine you're
building on (no change there), host is the machine you're building for
(the target libraries are built for the target, so host is the target
you specified), and target doesn't apply (because you're not building a
compiler, you're building libraries). The configure/make process will
-adjust these variables as needed. It also sets '$with_cross_host' to
-the original '--host' value in case you need it.
+adjust these variables as needed. It also sets `$with_cross_host' to
+the original `--host' value in case you need it.
- The 'libiberty' support library is built up to three times: once for
+ The `libiberty' support library is built up to three times: once for
the host, once for the target (even if they are the same), and once for
-the build if build and host are different. This allows it to be used by
-all programs which are generated in the course of the build process.
+the build if build and host are different. This allows it to be used
+by all programs which are generated in the course of the build process.

File: gccint.info, Node: Top Level, Next: gcc Directory, Prev: Configure Terms, Up: Source Tree
@@ -3088,130 +3094,130 @@ files and directories that are shared with other software distributions
such as that of GNU Binutils. It also contains several subdirectories
that contain parts of GCC and its runtime libraries:
-'boehm-gc'
+`boehm-gc'
The Boehm conservative garbage collector, used as part of the Java
runtime library.
-'config'
+`config'
Autoconf macros and Makefile fragments used throughout the tree.
-'contrib'
+`contrib'
Contributed scripts that may be found useful in conjunction with
- GCC. One of these, 'contrib/texi2pod.pl', is used to generate man
+ GCC. One of these, `contrib/texi2pod.pl', is used to generate man
pages from Texinfo manuals as part of the GCC build process.
-'fixincludes'
+`fixincludes'
The support for fixing system headers to work with GCC. See
- 'fixincludes/README' for more information. The headers fixed by
- this mechanism are installed in 'LIBSUBDIR/include-fixed'. Along
- with those headers, 'README-fixinc' is also installed, as
- 'LIBSUBDIR/include-fixed/README'.
+ `fixincludes/README' for more information. The headers fixed by
+ this mechanism are installed in `LIBSUBDIR/include-fixed'. Along
+ with those headers, `README-fixinc' is also installed, as
+ `LIBSUBDIR/include-fixed/README'.
-'gcc'
+`gcc'
The main sources of GCC itself (except for runtime libraries),
including optimizers, support for different target architectures,
- language front ends, and testsuites. *Note The 'gcc' Subdirectory:
- gcc Directory, for details.
+ language front ends, and testsuites. *Note The `gcc'
+ Subdirectory: gcc Directory, for details.
-'gnattools'
+`gnattools'
Support tools for GNAT.
-'include'
- Headers for the 'libiberty' library.
+`include'
+ Headers for the `libiberty' library.
-'intl'
- GNU 'libintl', from GNU 'gettext', for systems which do not include
- it in 'libc'.
+`intl'
+ GNU `libintl', from GNU `gettext', for systems which do not
+ include it in `libc'.
-'libada'
+`libada'
The Ada runtime library.
-'libatomic'
- The runtime support library for atomic operations (e.g. for
- '__sync' and '__atomic').
+`libatomic'
+ The runtime support library for atomic operations (e.g. for
+ `__sync' and `__atomic').
-'libcpp'
+`libcpp'
The C preprocessor library.
-'libdecnumber'
+`libdecnumber'
The Decimal Float support library.
-'libffi'
- The 'libffi' library, used as part of the Java runtime library.
+`libffi'
+ The `libffi' library, used as part of the Java runtime library.
-'libgcc'
+`libgcc'
The GCC runtime library.
-'libgfortran'
+`libgfortran'
The Fortran runtime library.
-'libgo'
+`libgo'
The Go runtime library. The bulk of this library is mirrored from
the master Go repository (http://code.google.com/p/go/).
-'libgomp'
+`libgomp'
The GNU Offloading and Multi Processing Runtime Library.
-'libiberty'
- The 'libiberty' library, used for portability and for some
+`libiberty'
+ The `libiberty' library, used for portability and for some
generally useful data structures and algorithms. *Note
Introduction: (libiberty)Top, for more information about this
library.
-'libitm'
+`libitm'
The runtime support library for transactional memory.
-'libjava'
+`libjava'
The Java runtime library.
-'libobjc'
+`libobjc'
The Objective-C and Objective-C++ runtime library.
-'libquadmath'
+`libquadmath'
The runtime support library for quad-precision math operations.
-'libssp'
+`libssp'
The Stack protector runtime library.
-'libstdc++-v3'
+`libstdc++-v3'
The C++ runtime library.
-'lto-plugin'
+`lto-plugin'
Plugin used by the linker if link-time optimizations are enabled.
-'maintainer-scripts'
- Scripts used by the 'gccadmin' account on 'gcc.gnu.org'.
+`maintainer-scripts'
+ Scripts used by the `gccadmin' account on `gcc.gnu.org'.
-'zlib'
- The 'zlib' compression library, used by the Java front end, as part
- of the Java runtime library, and for compressing and uncompressing
- GCC's intermediate language in LTO object files.
+`zlib'
+ The `zlib' compression library, used by the Java front end, as
+ part of the Java runtime library, and for compressing and
+ uncompressing GCC's intermediate language in LTO object files.
The build system in the top level directory, including how recursion
into subdirectories works and how building runtime libraries for
multilibs is handled, is documented in a separate manual, included with
-GNU Binutils. *Note GNU configure and build system: (configure)Top, for
-details.
+GNU Binutils. *Note GNU configure and build system: (configure)Top,
+for details.

File: gccint.info, Node: gcc Directory, Prev: Top Level, Up: Source Tree
-6.3 The 'gcc' Subdirectory
+6.3 The `gcc' Subdirectory
==========================
-The 'gcc' directory contains many files that are part of the C sources
-of GCC, other files used as part of the configuration and build process,
-and subdirectories including documentation and a testsuite. The files
-that are sources of GCC are documented in a separate chapter. *Note
-Passes and Files of the Compiler: Passes.
+The `gcc' directory contains many files that are part of the C sources
+of GCC, other files used as part of the configuration and build
+process, and subdirectories including documentation and a testsuite.
+The files that are sources of GCC are documented in a separate chapter.
+*Note Passes and Files of the Compiler: Passes.
* Menu:
-* Subdirectories:: Subdirectories of 'gcc'.
+* Subdirectories:: Subdirectories of `gcc'.
* Configuration:: The configuration process, and the files it uses.
-* Build:: The build system in the 'gcc' directory.
-* Makefile:: Targets in 'gcc/Makefile'.
-* Library Files:: Library source files and headers under 'gcc/'.
+* Build:: The build system in the `gcc' directory.
+* Makefile:: Targets in `gcc/Makefile'.
+* Library Files:: Library source files and headers under `gcc/'.
* Headers:: Headers installed by GCC.
* Documentation:: Building documentation in GCC.
* Front End:: Anatomy of a language front end.
@@ -3220,121 +3226,122 @@ Passes and Files of the Compiler: Passes.

File: gccint.info, Node: Subdirectories, Next: Configuration, Up: gcc Directory
-6.3.1 Subdirectories of 'gcc'
+6.3.1 Subdirectories of `gcc'
-----------------------------
-The 'gcc' directory contains the following subdirectories:
+The `gcc' directory contains the following subdirectories:
-'LANGUAGE'
+`LANGUAGE'
Subdirectories for various languages. Directories containing a
- file 'config-lang.in' are language subdirectories. The contents of
- the subdirectories 'c' (for C), 'cp' (for C++), 'objc' (for
- Objective-C), 'objcp' (for Objective-C++), and 'lto' (for LTO) are
+ file `config-lang.in' are language subdirectories. The contents of
+ the subdirectories `c' (for C), `cp' (for C++), `objc' (for
+ Objective-C), `objcp' (for Objective-C++), and `lto' (for LTO) are
documented in this manual (*note Passes and Files of the Compiler:
Passes.); those for other languages are not. *Note Anatomy of a
Language Front End: Front End, for details of the files in these
directories.
-'common'
- Source files shared between the compiler drivers (such as 'gcc')
- and the compilers proper (such as 'cc1'). If an architecture
+`common'
+ Source files shared between the compiler drivers (such as `gcc')
+ and the compilers proper (such as `cc1'). If an architecture
defines target hooks shared between those places, it also has a
- subdirectory in 'common/config'. *Note Target Structure::.
+ subdirectory in `common/config'. *Note Target Structure::.
-'config'
+`config'
Configuration files for supported architectures and operating
- systems. *Note Anatomy of a Target Back End: Back End, for details
- of the files in this directory.
+ systems. *Note Anatomy of a Target Back End: Back End, for
+ details of the files in this directory.
-'doc'
+`doc'
Texinfo documentation for GCC, together with automatically
generated man pages and support for converting the installation
manual to HTML. *Note Documentation::.
-'ginclude'
+`ginclude'
System headers installed by GCC, mainly those required by the C
standard of freestanding implementations. *Note Headers Installed
by GCC: Headers, for details of when these and other headers are
installed.
-'po'
+`po'
Message catalogs with translations of messages produced by GCC into
- various languages, 'LANGUAGE.po'. This directory also contains
- 'gcc.pot', the template for these message catalogues, 'exgettext',
- a wrapper around 'gettext' to extract the messages from the GCC
- sources and create 'gcc.pot', which is run by 'make gcc.pot', and
- 'EXCLUDES', a list of files from which messages should not be
+ various languages, `LANGUAGE.po'. This directory also contains
+ `gcc.pot', the template for these message catalogues, `exgettext',
+ a wrapper around `gettext' to extract the messages from the GCC
+ sources and create `gcc.pot', which is run by `make gcc.pot', and
+ `EXCLUDES', a list of files from which messages should not be
extracted.
-'testsuite'
- The GCC testsuites (except for those for runtime libraries). *Note
- Testsuites::.
+`testsuite'
+ The GCC testsuites (except for those for runtime libraries).
+ *Note Testsuites::.

File: gccint.info, Node: Configuration, Next: Build, Prev: Subdirectories, Up: gcc Directory
-6.3.2 Configuration in the 'gcc' Directory
+6.3.2 Configuration in the `gcc' Directory
------------------------------------------
-The 'gcc' directory is configured with an Autoconf-generated script
-'configure'. The 'configure' script is generated from 'configure.ac'
-and 'aclocal.m4'. From the files 'configure.ac' and 'acconfig.h',
-Autoheader generates the file 'config.in'. The file 'cstamp-h.in' is
+The `gcc' directory is configured with an Autoconf-generated script
+`configure'. The `configure' script is generated from `configure.ac'
+and `aclocal.m4'. From the files `configure.ac' and `acconfig.h',
+Autoheader generates the file `config.in'. The file `cstamp-h.in' is
used as a timestamp.
* Menu:
-* Config Fragments:: Scripts used by 'configure'.
-* System Config:: The 'config.build', 'config.host', and
- 'config.gcc' files.
-* Configuration Files:: Files created by running 'configure'.
+* Config Fragments:: Scripts used by `configure'.
+* System Config:: The `config.build', `config.host', and
+ `config.gcc' files.
+* Configuration Files:: Files created by running `configure'.

File: gccint.info, Node: Config Fragments, Next: System Config, Up: Configuration
-6.3.2.1 Scripts Used by 'configure'
+6.3.2.1 Scripts Used by `configure'
...................................
-'configure' uses some other scripts to help in its work:
+`configure' uses some other scripts to help in its work:
- * The standard GNU 'config.sub' and 'config.guess' files, kept in the
- top level directory, are used.
+ * The standard GNU `config.sub' and `config.guess' files, kept in
+ the top level directory, are used.
- * The file 'config.gcc' is used to handle configuration specific to
- the particular target machine. The file 'config.build' is used to
- handle configuration specific to the particular build machine. The
- file 'config.host' is used to handle configuration specific to the
- particular host machine. (In general, these should only be used
- for features that cannot reasonably be tested in Autoconf feature
- tests.) *Note The 'config.build'; 'config.host'; and 'config.gcc'
- Files: System Config, for details of the contents of these files.
+ * The file `config.gcc' is used to handle configuration specific to
+ the particular target machine. The file `config.build' is used to
+ handle configuration specific to the particular build machine.
+ The file `config.host' is used to handle configuration specific to
+ the particular host machine. (In general, these should only be
+ used for features that cannot reasonably be tested in Autoconf
+ feature tests.) *Note The `config.build'; `config.host'; and
+ `config.gcc' Files: System Config, for details of the contents of
+ these files.
- * Each language subdirectory has a file 'LANGUAGE/config-lang.in'
- that is used for front-end-specific configuration. *Note The Front
- End 'config-lang.in' File: Front End Config, for details of this
- file.
+ * Each language subdirectory has a file `LANGUAGE/config-lang.in'
+ that is used for front-end-specific configuration. *Note The
+ Front End `config-lang.in' File: Front End Config, for details of
+ this file.
- * A helper script 'configure.frag' is used as part of creating the
- output of 'configure'.
+ * A helper script `configure.frag' is used as part of creating the
+ output of `configure'.

File: gccint.info, Node: System Config, Next: Configuration Files, Prev: Config Fragments, Up: Configuration
-6.3.2.2 The 'config.build'; 'config.host'; and 'config.gcc' Files
+6.3.2.2 The `config.build'; `config.host'; and `config.gcc' Files
.................................................................
-The 'config.build' file contains specific rules for particular systems
+The `config.build' file contains specific rules for particular systems
which GCC is built on. This should be used as rarely as possible, as
the behavior of the build system can always be detected by autoconf.
- The 'config.host' file contains specific rules for particular systems
+ The `config.host' file contains specific rules for particular systems
which GCC will run on. This is rarely needed.
- The 'config.gcc' file contains specific rules for particular systems
+ The `config.gcc' file contains specific rules for particular systems
which GCC will generate code for. This is usually needed.
- Each file has a list of the shell variables it sets, with descriptions,
-at the top of the file.
+ Each file has a list of the shell variables it sets, with
+descriptions, at the top of the file.
FIXME: document the contents of these files, and what variables should
be set to control build, host and target configuration.
@@ -3342,61 +3349,69 @@ be set to control build, host and target configuration.

File: gccint.info, Node: Configuration Files, Prev: System Config, Up: Configuration
-6.3.2.3 Files Created by 'configure'
+6.3.2.3 Files Created by `configure'
....................................
-Here we spell out what files will be set up by 'configure' in the 'gcc'
+Here we spell out what files will be set up by `configure' in the `gcc'
directory. Some other files are created as temporary files in the
configuration process, and are not used in the subsequent build; these
are not documented.
- * 'Makefile' is constructed from 'Makefile.in', together with the
+ * `Makefile' is constructed from `Makefile.in', together with the
host and target fragments (*note Makefile Fragments: Fragments.)
- 't-TARGET' and 'x-HOST' from 'config', if any, and language
- Makefile fragments 'LANGUAGE/Make-lang.in'.
- * 'auto-host.h' contains information about the host machine
- determined by 'configure'. If the host machine is different from
- the build machine, then 'auto-build.h' is also created, containing
+ `t-TARGET' and `x-HOST' from `config', if any, and language
+ Makefile fragments `LANGUAGE/Make-lang.in'.
+
+ * `auto-host.h' contains information about the host machine
+ determined by `configure'. If the host machine is different from
+ the build machine, then `auto-build.h' is also created, containing
such information about the build machine.
- * 'config.status' is a script that may be run to recreate the current
- configuration.
- * 'configargs.h' is a header containing details of the arguments
- passed to 'configure' to configure GCC, and of the thread model
+
+ * `config.status' is a script that may be run to recreate the
+ current configuration.
+
+ * `configargs.h' is a header containing details of the arguments
+ passed to `configure' to configure GCC, and of the thread model
used.
- * 'cstamp-h' is used as a timestamp.
- * If a language 'config-lang.in' file (*note The Front End
- 'config-lang.in' File: Front End Config.) sets 'outputs', then the
- files listed in 'outputs' there are also generated.
+
+ * `cstamp-h' is used as a timestamp.
+
+ * If a language `config-lang.in' file (*note The Front End
+ `config-lang.in' File: Front End Config.) sets `outputs', then the
+ files listed in `outputs' there are also generated.
The following configuration headers are created from the Makefile,
-using 'mkconfig.sh', rather than directly by 'configure'. 'config.h',
-'bconfig.h' and 'tconfig.h' all contain the 'xm-MACHINE.h' header, if
+using `mkconfig.sh', rather than directly by `configure'. `config.h',
+`bconfig.h' and `tconfig.h' all contain the `xm-MACHINE.h' header, if
any, appropriate to the host, build and target machines respectively,
the configuration headers for the target, and some definitions; for the
host and build machines, these include the autoconfigured headers
-generated by 'configure'. The other configuration headers are
-determined by 'config.gcc'. They also contain the typedefs for 'rtx',
-'rtvec' and 'tree'.
+generated by `configure'. The other configuration headers are
+determined by `config.gcc'. They also contain the typedefs for `rtx',
+`rtvec' and `tree'.
+
+ * `config.h', for use in programs that run on the host machine.
- * 'config.h', for use in programs that run on the host machine.
- * 'bconfig.h', for use in programs that run on the build machine.
- * 'tconfig.h', for use in programs and libraries for the target
+ * `bconfig.h', for use in programs that run on the build machine.
+
+ * `tconfig.h', for use in programs and libraries for the target
machine.
- * 'tm_p.h', which includes the header 'MACHINE-protos.h' that
- contains prototypes for functions in the target 'MACHINE.c' file.
- The header 'MACHINE-protos.h' can include prototypes of functions
- that use rtl and tree data structures inside appropriate '#ifdef
- RTX_CODE' and '#ifdef TREE_CODE' conditional code segements. The
- 'MACHINE-protos.h' is included after the 'rtl.h' and/or 'tree.h'
- would have been included. The 'tm_p.h' also includes the header
- 'tm-preds.h' which is generated by 'genpreds' program during the
+
+ * `tm_p.h', which includes the header `MACHINE-protos.h' that
+ contains prototypes for functions in the target `MACHINE.c' file.
+ The header `MACHINE-protos.h' can include prototypes of functions
+ that use rtl and tree data structures inside appropriate `#ifdef
+ RTX_CODE' and `#ifdef TREE_CODE' conditional code segements. The
+ `MACHINE-protos.h' is included after the `rtl.h' and/or `tree.h'
+ would have been included. The `tm_p.h' also includes the header
+ `tm-preds.h' which is generated by `genpreds' program during the
build to define the declarations and inline functions for the
predicate functions.

File: gccint.info, Node: Build, Next: Makefile, Prev: Configuration, Up: gcc Directory
-6.3.3 Build System in the 'gcc' Directory
+6.3.3 Build System in the `gcc' Directory
-----------------------------------------
FIXME: describe the build system, including what is built in what
@@ -3410,68 +3425,68 @@ File: gccint.info, Node: Makefile, Next: Library Files, Prev: Build, Up: gcc
6.3.4 Makefile Targets
----------------------
-These targets are available from the 'gcc' directory:
+These targets are available from the `gcc' directory:
-'all'
+`all'
This is the default target. Depending on what your
build/host/target configuration is, it coordinates all the things
that need to be built.
-'doc'
+`doc'
Produce info-formatted documentation and man pages. Essentially it
- calls 'make man' and 'make info'.
+ calls `make man' and `make info'.
-'dvi'
+`dvi'
Produce DVI-formatted documentation.
-'pdf'
+`pdf'
Produce PDF-formatted documentation.
-'html'
+`html'
Produce HTML-formatted documentation.
-'man'
+`man'
Generate man pages.
-'info'
+`info'
Generate info-formatted pages.
-'mostlyclean'
+`mostlyclean'
Delete the files made while building the compiler.
-'clean'
- That, and all the other files built by 'make all'.
+`clean'
+ That, and all the other files built by `make all'.
-'distclean'
- That, and all the files created by 'configure'.
+`distclean'
+ That, and all the files created by `configure'.
-'maintainer-clean'
+`maintainer-clean'
Distclean plus any file that can be generated from other files.
Note that additional tools may be required beyond what is normally
needed to build GCC.
-'srcextra'
+`srcextra'
Generates files in the source directory that are not
version-controlled but should go into a release tarball.
-'srcinfo'
-'srcman'
+`srcinfo'
+`srcman'
Copies the info-formatted and manpage documentation into the source
directory usually for the purpose of generating a release tarball.
-'install'
+`install'
Installs GCC.
-'uninstall'
+`uninstall'
Deletes installed files, though this is not supported.
-'check'
- Run the testsuite. This creates a 'testsuite' subdirectory that
- has various '.sum' and '.log' files containing the results of the
- testing. You can run subsets with, for example, 'make check-gcc'.
- You can specify specific tests by setting 'RUNTESTFLAGS' to be the
- name of the '.exp' file, optionally followed by (for some tests) an
- equals and a file wildcard, like:
+`check'
+ Run the testsuite. This creates a `testsuite' subdirectory that
+ has various `.sum' and `.log' files containing the results of the
+ testing. You can run subsets with, for example, `make check-gcc'.
+ You can specify specific tests by setting `RUNTESTFLAGS' to be the
+ name of the `.exp' file, optionally followed by (for some tests)
+ an equals and a file wildcard, like:
make check-gcc RUNTESTFLAGS="execute.exp=19980413-*"
@@ -3484,91 +3499,92 @@ steps of the build, including bootstrapping the compiler and using the
new compiler to build target libraries.
When GCC is configured for a native configuration, the default action
-for 'make' is to do a full three-stage bootstrap. This means that GCC
+for `make' is to do a full three-stage bootstrap. This means that GCC
is built three times--once with the native compiler, once with the
-native-built compiler it just built, and once with the compiler it built
-the second time. In theory, the last two should produce the same
-results, which 'make compare' can check. Each stage is configured
+native-built compiler it just built, and once with the compiler it
+built the second time. In theory, the last two should produce the same
+results, which `make compare' can check. Each stage is configured
separately and compiled into a separate directory, to minimize problems
due to ABI incompatibilities between the native compiler and GCC.
- If you do a change, rebuilding will also start from the first stage and
-"bubble" up the change through the three stages. Each stage is taken
-from its build directory (if it had been built previously), rebuilt, and
-copied to its subdirectory. This will allow you to, for example,
-continue a bootstrap after fixing a bug which causes the stage2 build to
-crash. It does not provide as good coverage of the compiler as
-bootstrapping from scratch, but it ensures that the new code is
-syntactically correct (e.g., that you did not use GCC extensions by
-mistake), and avoids spurious bootstrap comparison failures(1).
+ If you do a change, rebuilding will also start from the first stage
+and "bubble" up the change through the three stages. Each stage is
+taken from its build directory (if it had been built previously),
+rebuilt, and copied to its subdirectory. This will allow you to, for
+example, continue a bootstrap after fixing a bug which causes the
+stage2 build to crash. It does not provide as good coverage of the
+compiler as bootstrapping from scratch, but it ensures that the new
+code is syntactically correct (e.g., that you did not use GCC extensions
+by mistake), and avoids spurious bootstrap comparison failures(1).
Other targets available from the top level include:
-'bootstrap-lean'
- Like 'bootstrap', except that the various stages are removed once
+`bootstrap-lean'
+ Like `bootstrap', except that the various stages are removed once
they're no longer needed. This saves disk space.
-'bootstrap2'
-'bootstrap2-lean'
+`bootstrap2'
+`bootstrap2-lean'
Performs only the first two stages of bootstrap. Unlike a
three-stage bootstrap, this does not perform a comparison to test
that the compiler is running properly. Note that the disk space
required by a "lean" bootstrap is approximately independent of the
number of stages.
-'stageN-bubble (N = 1...4, profile, feedback)'
+`stageN-bubble (N = 1...4, profile, feedback)'
Rebuild all the stages up to N, with the appropriate flags,
"bubbling" the changes as described above.
-'all-stageN (N = 1...4, profile, feedback)'
+`all-stageN (N = 1...4, profile, feedback)'
Assuming that stage N has already been built, rebuild it with the
appropriate flags. This is rarely needed.
-'cleanstrap'
- Remove everything ('make clean') and rebuilds ('make bootstrap').
+`cleanstrap'
+ Remove everything (`make clean') and rebuilds (`make bootstrap').
-'compare'
+`compare'
Compares the results of stages 2 and 3. This ensures that the
compiler is running properly, since it should produce the same
object files regardless of how it itself was compiled.
-'profiledbootstrap'
+`profiledbootstrap'
Builds a compiler with profiling feedback information. In this
- case, the second and third stages are named 'profile' and
- 'feedback', respectively. For more information, see *note Building
- with profile feedback: (gccinstall)Building.
+ case, the second and third stages are named `profile' and
+ `feedback', respectively. For more information, see *note
+ Building with profile feedback: (gccinstall)Building.
-'restrap'
- Restart a bootstrap, so that everything that was not built with the
- system compiler is rebuilt.
+`restrap'
+ Restart a bootstrap, so that everything that was not built with
+ the system compiler is rebuilt.
-'stageN-start (N = 1...4, profile, feedback)'
+`stageN-start (N = 1...4, profile, feedback)'
For each package that is bootstrapped, rename directories so that,
- for example, 'gcc' points to the stageN GCC, compiled with the
+ for example, `gcc' points to the stageN GCC, compiled with the
stageN-1 GCC(2).
- You will invoke this target if you need to test or debug the stageN
- GCC. If you only need to execute GCC (but you need not run 'make'
- either to rebuild it or to run test suites), you should be able to
- work directly in the 'stageN-gcc' directory. This makes it easier
- to debug multiple stages in parallel.
+ You will invoke this target if you need to test or debug the
+ stageN GCC. If you only need to execute GCC (but you need not run
+ `make' either to rebuild it or to run test suites), you should be
+ able to work directly in the `stageN-gcc' directory. This makes
+ it easier to debug multiple stages in parallel.
-'stage'
+`stage'
For each package that is bootstrapped, relocate its build directory
- to indicate its stage. For example, if the 'gcc' directory points
- to the stage2 GCC, after invoking this target it will be renamed to
- 'stage2-gcc'.
+ to indicate its stage. For example, if the `gcc' directory points
+ to the stage2 GCC, after invoking this target it will be renamed
+ to `stage2-gcc'.
+
If you wish to use non-default GCC flags when compiling the stage2 and
-stage3 compilers, set 'BOOT_CFLAGS' on the command line when doing
-'make'.
+stage3 compilers, set `BOOT_CFLAGS' on the command line when doing
+`make'.
- Usually, the first stage only builds the languages that the compiler is
-written in: typically, C and maybe Ada. If you are debugging a
+ Usually, the first stage only builds the languages that the compiler
+is written in: typically, C and maybe Ada. If you are debugging a
miscompilation of a different stage2 front-end (for example, of the
Fortran front-end), you may want to have front-ends for other languages
-in the first stage as well. To do so, set 'STAGE1_LANGUAGES' on the
-command line when doing 'make'.
+in the first stage as well. To do so, set `STAGE1_LANGUAGES' on the
+command line when doing `make'.
For example, in the aforementioned scenario of debugging a Fortran
front-end miscompilation caused by the stage1 compiler, you may need a
@@ -3577,28 +3593,28 @@ command like
make stage2-bubble STAGE1_LANGUAGES=c,fortran
Alternatively, you can use per-language targets to build and test
-languages that are not enabled by default in stage1. For example, 'make
-f951' will build a Fortran compiler even in the stage1 build directory.
+languages that are not enabled by default in stage1. For example,
+`make f951' will build a Fortran compiler even in the stage1 build
+directory.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) Except if the compiler was buggy and miscompiled some of the
-files that were not modified. In this case, it's best to use 'make
-restrap'.
+ (1) Except if the compiler was buggy and miscompiled some of the files
+that were not modified. In this case, it's best to use `make restrap'.
- (2) Customarily, the system compiler is also termed the 'stage0' GCC.
+ (2) Customarily, the system compiler is also termed the `stage0' GCC.

File: gccint.info, Node: Library Files, Next: Headers, Prev: Makefile, Up: gcc Directory
-6.3.5 Library Source Files and Headers under the 'gcc' Directory
+6.3.5 Library Source Files and Headers under the `gcc' Directory
----------------------------------------------------------------
FIXME: list here, with explanation, all the C source files and headers
-under the 'gcc' directory that aren't built into the GCC executable but
+under the `gcc' directory that aren't built into the GCC executable but
rather are part of runtime libraries and object files, such as
-'crtstuff.c' and 'unwind-dw2.c'. *Note Headers Installed by GCC:
-Headers, for more information about the 'ginclude' directory.
+`crtstuff.c' and `unwind-dw2.c'. *Note Headers Installed by GCC:
+Headers, for more information about the `ginclude' directory.

File: gccint.info, Node: Headers, Next: Documentation, Prev: Library Files, Up: gcc Directory
@@ -3610,38 +3626,38 @@ In general, GCC expects the system C library to provide most of the
headers to be used with it. However, GCC will fix those headers if
necessary to make them work with GCC, and will install some headers
required of freestanding implementations. These headers are installed
-in 'LIBSUBDIR/include'. Headers for non-C runtime libraries are also
+in `LIBSUBDIR/include'. Headers for non-C runtime libraries are also
installed by GCC; these are not documented here. (FIXME: document them
somewhere.)
- Several of the headers GCC installs are in the 'ginclude' directory.
-These headers, 'iso646.h', 'stdarg.h', 'stdbool.h', and 'stddef.h', are
-installed in 'LIBSUBDIR/include', unless the target Makefile fragment
-(*note Target Fragment::) overrides this by setting 'USER_H'.
+ Several of the headers GCC installs are in the `ginclude' directory.
+These headers, `iso646.h', `stdarg.h', `stdbool.h', and `stddef.h', are
+installed in `LIBSUBDIR/include', unless the target Makefile fragment
+(*note Target Fragment::) overrides this by setting `USER_H'.
In addition to these headers and those generated by fixing system
headers to work with GCC, some other headers may also be installed in
-'LIBSUBDIR/include'. 'config.gcc' may set 'extra_headers'; this
-specifies additional headers under 'config' to be installed on some
+`LIBSUBDIR/include'. `config.gcc' may set `extra_headers'; this
+specifies additional headers under `config' to be installed on some
systems.
- GCC installs its own version of '<float.h>', from 'ginclude/float.h'.
+ GCC installs its own version of `<float.h>', from `ginclude/float.h'.
This is done to cope with command-line options that change the
representation of floating point numbers.
- GCC also installs its own version of '<limits.h>'; this is generated
-from 'glimits.h', together with 'limitx.h' and 'limity.h' if the system
-also has its own version of '<limits.h>'. (GCC provides its own header
+ GCC also installs its own version of `<limits.h>'; this is generated
+from `glimits.h', together with `limitx.h' and `limity.h' if the system
+also has its own version of `<limits.h>'. (GCC provides its own header
because it is required of ISO C freestanding implementations, but needs
to include the system header from its own header as well because other
standards such as POSIX specify additional values to be defined in
-'<limits.h>'.) The system's '<limits.h>' header is used via
-'LIBSUBDIR/include/syslimits.h', which is copied from 'gsyslimits.h' if
+`<limits.h>'.) The system's `<limits.h>' header is used via
+`LIBSUBDIR/include/syslimits.h', which is copied from `gsyslimits.h' if
it does not need fixing to work with GCC; if it needs fixing,
-'syslimits.h' is the fixed copy.
+`syslimits.h' is the fixed copy.
- GCC can also install '<tgmath.h>'. It will do this when 'config.gcc'
-sets 'use_gcc_tgmath' to 'yes'.
+ GCC can also install `<tgmath.h>'. It will do this when `config.gcc'
+sets `use_gcc_tgmath' to `yes'.

File: gccint.info, Node: Documentation, Next: Front End, Prev: Headers, Up: gcc Directory
@@ -3651,11 +3667,11 @@ File: gccint.info, Node: Documentation, Next: Front End, Prev: Headers, Up:
The main GCC documentation is in the form of manuals in Texinfo format.
These are installed in Info format; DVI versions may be generated by
-'make dvi', PDF versions by 'make pdf', and HTML versions by 'make
+`make dvi', PDF versions by `make pdf', and HTML versions by `make
html'. In addition, some man pages are generated from the Texinfo
manuals, there are some other text files with miscellaneous
documentation, and runtime libraries have their own documentation
-outside the 'gcc' directory. FIXME: document the documentation for
+outside the `gcc' directory. FIXME: document the documentation for
runtime libraries somewhere.
* Menu:
@@ -3671,49 +3687,53 @@ File: gccint.info, Node: Texinfo Manuals, Next: Man Page Generation, Up: Docu
.......................
The manuals for GCC as a whole, and the C and C++ front ends, are in
-files 'doc/*.texi'. Other front ends have their own manuals in files
-'LANGUAGE/*.texi'. Common files 'doc/include/*.texi' are provided which
-may be included in multiple manuals; the following files are in
-'doc/include':
+files `doc/*.texi'. Other front ends have their own manuals in files
+`LANGUAGE/*.texi'. Common files `doc/include/*.texi' are provided
+which may be included in multiple manuals; the following files are in
+`doc/include':
-'fdl.texi'
+`fdl.texi'
The GNU Free Documentation License.
-'funding.texi'
+
+`funding.texi'
The section "Funding Free Software".
-'gcc-common.texi'
+
+`gcc-common.texi'
Common definitions for manuals.
-'gpl_v3.texi'
+
+`gpl_v3.texi'
The GNU General Public License.
-'texinfo.tex'
- A copy of 'texinfo.tex' known to work with the GCC manuals.
-
- DVI-formatted manuals are generated by 'make dvi', which uses
-'texi2dvi' (via the Makefile macro '$(TEXI2DVI)'). PDF-formatted
-manuals are generated by 'make pdf', which uses 'texi2pdf' (via the
-Makefile macro '$(TEXI2PDF)'). HTML formatted manuals are generated by
-'make html'. Info manuals are generated by 'make info' (which is run as
-part of a bootstrap); this generates the manuals in the source
-directory, using 'makeinfo' via the Makefile macro '$(MAKEINFO)', and
+
+`texinfo.tex'
+ A copy of `texinfo.tex' known to work with the GCC manuals.
+
+ DVI-formatted manuals are generated by `make dvi', which uses
+`texi2dvi' (via the Makefile macro `$(TEXI2DVI)'). PDF-formatted
+manuals are generated by `make pdf', which uses `texi2pdf' (via the
+Makefile macro `$(TEXI2PDF)'). HTML formatted manuals are generated by
+`make html'. Info manuals are generated by `make info' (which is run
+as part of a bootstrap); this generates the manuals in the source
+directory, using `makeinfo' via the Makefile macro `$(MAKEINFO)', and
they are included in release distributions.
Manuals are also provided on the GCC web site, in both HTML and
PostScript forms. This is done via the script
-'maintainer-scripts/update_web_docs_svn'. Each manual to be provided
-online must be listed in the definition of 'MANUALS' in that file; a
-file 'NAME.texi' must only appear once in the source tree, and the
+`maintainer-scripts/update_web_docs_svn'. Each manual to be provided
+online must be listed in the definition of `MANUALS' in that file; a
+file `NAME.texi' must only appear once in the source tree, and the
output manual must have the same name as the source file. (However,
other Texinfo files, included in manuals but not themselves the root
files of manuals, may have names that appear more than once in the
-source tree.) The manual file 'NAME.texi' should only include other
-files in its own directory or in 'doc/include'. HTML manuals will be
-generated by 'makeinfo --html', PostScript manuals by 'texi2dvi' and
-'dvips', and PDF manuals by 'texi2pdf'. All Texinfo files that are
+source tree.) The manual file `NAME.texi' should only include other
+files in its own directory or in `doc/include'. HTML manuals will be
+generated by `makeinfo --html', PostScript manuals by `texi2dvi' and
+`dvips', and PDF manuals by `texi2pdf'. All Texinfo files that are
parts of manuals must be version-controlled, even if they are generated
files, for the generation of online manuals to work.
- The installation manual, 'doc/install.texi', is also provided on the
+ The installation manual, `doc/install.texi', is also provided on the
GCC web site. The HTML version is generated by the script
-'doc/install.texi2html'.
+`doc/install.texi2html'.

File: gccint.info, Node: Man Page Generation, Next: Miscellaneous Docs, Prev: Texinfo Manuals, Up: Documentation
@@ -3722,38 +3742,40 @@ File: gccint.info, Node: Man Page Generation, Next: Miscellaneous Docs, Prev:
...........................
Because of user demand, in addition to full Texinfo manuals, man pages
-are provided which contain extracts from those manuals. These man pages
-are generated from the Texinfo manuals using 'contrib/texi2pod.pl' and
-'pod2man'. (The man page for 'g++', 'cp/g++.1', just contains a '.so'
-reference to 'gcc.1', but all the other man pages are generated from
-Texinfo manuals.)
+are provided which contain extracts from those manuals. These man
+pages are generated from the Texinfo manuals using
+`contrib/texi2pod.pl' and `pod2man'. (The man page for `g++',
+`cp/g++.1', just contains a `.so' reference to `gcc.1', but all the
+other man pages are generated from Texinfo manuals.)
Because many systems may not have the necessary tools installed to
-generate the man pages, they are only generated if the 'configure'
-script detects that recent enough tools are installed, and the Makefiles
-allow generating man pages to fail without aborting the build. Man
-pages are also included in release distributions. They are generated in
-the source directory.
-
- Magic comments in Texinfo files starting '@c man' control what parts of
-a Texinfo file go into a man page. Only a subset of Texinfo is
-supported by 'texi2pod.pl', and it may be necessary to add support for
+generate the man pages, they are only generated if the `configure'
+script detects that recent enough tools are installed, and the
+Makefiles allow generating man pages to fail without aborting the
+build. Man pages are also included in release distributions. They are
+generated in the source directory.
+
+ Magic comments in Texinfo files starting `@c man' control what parts
+of a Texinfo file go into a man page. Only a subset of Texinfo is
+supported by `texi2pod.pl', and it may be necessary to add support for
more Texinfo features to this script when generating new man pages. To
-improve the man page output, some special Texinfo macros are provided in
-'doc/include/gcc-common.texi' which 'texi2pod.pl' understands:
-
-'@gcctabopt'
- Use in the form '@table @gcctabopt' for tables of options, where
- for printed output the effect of '@code' is better than that of
- '@option' but for man page output a different effect is wanted.
-'@gccoptlist'
+improve the man page output, some special Texinfo macros are provided
+in `doc/include/gcc-common.texi' which `texi2pod.pl' understands:
+
+`@gcctabopt'
+ Use in the form `@table @gcctabopt' for tables of options, where
+ for printed output the effect of `@code' is better than that of
+ `@option' but for man page output a different effect is wanted.
+
+`@gccoptlist'
Use for summary lists of options in manuals.
-'@gol'
- Use at the end of each line inside '@gccoptlist'. This is
+
+`@gol'
+ Use at the end of each line inside `@gccoptlist'. This is
necessary to avoid problems with differences in how the
- '@gccoptlist' macro is handled by different Texinfo formatters.
+ `@gccoptlist' macro is handled by different Texinfo formatters.
- FIXME: describe the 'texi2pod.pl' input language and magic comments in
+ FIXME: describe the `texi2pod.pl' input language and magic comments in
more detail.

@@ -3763,37 +3785,44 @@ File: gccint.info, Node: Miscellaneous Docs, Prev: Man Page Generation, Up: D
...................................
In addition to the formal documentation that is installed by GCC, there
-are several other text files in the 'gcc' subdirectory with
+are several other text files in the `gcc' subdirectory with
miscellaneous documentation:
-'ABOUT-GCC-NLS'
- Notes on GCC's Native Language Support. FIXME: this should be part
- of this manual rather than a separate file.
-'ABOUT-NLS'
+`ABOUT-GCC-NLS'
+ Notes on GCC's Native Language Support. FIXME: this should be
+ part of this manual rather than a separate file.
+
+`ABOUT-NLS'
Notes on the Free Translation Project.
-'COPYING'
-'COPYING3'
+
+`COPYING'
+`COPYING3'
The GNU General Public License, Versions 2 and 3.
-'COPYING.LIB'
-'COPYING3.LIB'
+
+`COPYING.LIB'
+`COPYING3.LIB'
The GNU Lesser General Public License, Versions 2.1 and 3.
-'*ChangeLog*'
-'*/ChangeLog*'
+
+`*ChangeLog*'
+`*/ChangeLog*'
Change log files for various parts of GCC.
-'LANGUAGES'
+
+`LANGUAGES'
Details of a few changes to the GCC front-end interface. FIXME:
the information in this file should be part of general
documentation of the front-end interface in this manual.
-'ONEWS'
+
+`ONEWS'
Information about new features in old versions of GCC. (For recent
versions, the information is on the GCC web site.)
-'README.Portability'
+
+`README.Portability'
Information about portability issues when writing code in GCC.
FIXME: why isn't this part of this manual or of the GCC Coding
Conventions?
- FIXME: document such files in subdirectories, at least 'config', 'c',
-'cp', 'objc', 'testsuite'.
+ FIXME: document such files in subdirectories, at least `config', `c',
+`cp', `objc', `testsuite'.

File: gccint.info, Node: Front End, Next: Back End, Prev: Documentation, Up: gcc Directory
@@ -3803,37 +3832,49 @@ File: gccint.info, Node: Front End, Next: Back End, Prev: Documentation, Up:
A front end for a language in GCC has the following parts:
- * A directory 'LANGUAGE' under 'gcc' containing source files for that
- front end. *Note The Front End 'LANGUAGE' Directory: Front End
- Directory, for details.
+ * A directory `LANGUAGE' under `gcc' containing source files for
+ that front end. *Note The Front End `LANGUAGE' Directory: Front
+ End Directory, for details.
+
* A mention of the language in the list of supported languages in
- 'gcc/doc/install.texi'.
+ `gcc/doc/install.texi'.
+
* A mention of the name under which the language's runtime library is
- recognized by '--enable-shared=PACKAGE' in the documentation of
- that option in 'gcc/doc/install.texi'.
+ recognized by `--enable-shared=PACKAGE' in the documentation of
+ that option in `gcc/doc/install.texi'.
+
* A mention of any special prerequisites for building the front end
- in the documentation of prerequisites in 'gcc/doc/install.texi'.
+ in the documentation of prerequisites in `gcc/doc/install.texi'.
+
* Details of contributors to that front end in
- 'gcc/doc/contrib.texi'. If the details are in that front end's own
- manual then there should be a link to that manual's list in
- 'contrib.texi'.
+ `gcc/doc/contrib.texi'. If the details are in that front end's
+ own manual then there should be a link to that manual's list in
+ `contrib.texi'.
+
* Information about support for that language in
- 'gcc/doc/frontends.texi'.
+ `gcc/doc/frontends.texi'.
+
* Information about standards for that language, and the front end's
- support for them, in 'gcc/doc/standards.texi'. This may be a link
+ support for them, in `gcc/doc/standards.texi'. This may be a link
to such information in the front end's own manual.
- * Details of source file suffixes for that language and '-x LANG'
- options supported, in 'gcc/doc/invoke.texi'.
- * Entries in 'default_compilers' in 'gcc.c' for source file suffixes
+
+ * Details of source file suffixes for that language and `-x LANG'
+ options supported, in `gcc/doc/invoke.texi'.
+
+ * Entries in `default_compilers' in `gcc.c' for source file suffixes
for that language.
- * Preferably testsuites, which may be under 'gcc/testsuite' or
+
+ * Preferably testsuites, which may be under `gcc/testsuite' or
runtime library directories. FIXME: document somewhere how to
write testsuite harnesses.
- * Probably a runtime library for the language, outside the 'gcc'
+
+ * Probably a runtime library for the language, outside the `gcc'
directory. FIXME: document this further.
+
* Details of the directories of any runtime libraries in
- 'gcc/doc/sourcebuild.texi'.
- * Check targets in 'Makefile.def' for the top-level 'Makefile' to
+ `gcc/doc/sourcebuild.texi'.
+
+ * Check targets in `Makefile.def' for the top-level `Makefile' to
check just the compiler or the compiler and runtime library for the
language.
@@ -3841,209 +3882,245 @@ A front end for a language in GCC has the following parts:
following are also necessary:
* At least one Bugzilla component for bugs in that front end and
- runtime libraries. This category needs to be added to the Bugzilla
- database.
+ runtime libraries. This category needs to be added to the
+ Bugzilla database.
+
* Normally, one or more maintainers of that front end listed in
- 'MAINTAINERS'.
- * Mentions on the GCC web site in 'index.html' and 'frontends.html',
- with any relevant links on 'readings.html'. (Front ends that are
- not an official part of GCC may also be listed on 'frontends.html',
- with relevant links.)
- * A news item on 'index.html', and possibly an announcement on the
+ `MAINTAINERS'.
+
+ * Mentions on the GCC web site in `index.html' and `frontends.html',
+ with any relevant links on `readings.html'. (Front ends that are
+ not an official part of GCC may also be listed on
+ `frontends.html', with relevant links.)
+
+ * A news item on `index.html', and possibly an announcement on the
<gcc-announce@gcc.gnu.org> mailing list.
+
* The front end's manuals should be mentioned in
- 'maintainer-scripts/update_web_docs_svn' (*note Texinfo Manuals::)
+ `maintainer-scripts/update_web_docs_svn' (*note Texinfo Manuals::)
and the online manuals should be linked to from
- 'onlinedocs/index.html'.
+ `onlinedocs/index.html'.
+
* Any old releases or CVS repositories of the front end, before its
inclusion in GCC, should be made available on the GCC FTP site
- <ftp://gcc.gnu.org/pub/gcc/old-releases/>.
- * The release and snapshot script 'maintainer-scripts/gcc_release'
+ `ftp://gcc.gnu.org/pub/gcc/old-releases/'.
+
+ * The release and snapshot script `maintainer-scripts/gcc_release'
should be updated to generate appropriate tarballs for this front
end.
+
* If this front end includes its own version files that include the
- current date, 'maintainer-scripts/update_version' should be updated
- accordingly.
+ current date, `maintainer-scripts/update_version' should be
+ updated accordingly.
* Menu:
-* Front End Directory:: The front end 'LANGUAGE' directory.
-* Front End Config:: The front end 'config-lang.in' file.
-* Front End Makefile:: The front end 'Make-lang.in' file.
+* Front End Directory:: The front end `LANGUAGE' directory.
+* Front End Config:: The front end `config-lang.in' file.
+* Front End Makefile:: The front end `Make-lang.in' file.

File: gccint.info, Node: Front End Directory, Next: Front End Config, Up: Front End
-6.3.8.1 The Front End 'LANGUAGE' Directory
+6.3.8.1 The Front End `LANGUAGE' Directory
..........................................
-A front end 'LANGUAGE' directory contains the source files of that front
-end (but not of any runtime libraries, which should be outside the 'gcc'
-directory). This includes documentation, and possibly some subsidiary
-programs built alongside the front end. Certain files are special and
-other parts of the compiler depend on their names:
+A front end `LANGUAGE' directory contains the source files of that
+front end (but not of any runtime libraries, which should be outside
+the `gcc' directory). This includes documentation, and possibly some
+subsidiary programs built alongside the front end. Certain files are
+special and other parts of the compiler depend on their names:
-'config-lang.in'
+`config-lang.in'
This file is required in all language subdirectories. *Note The
- Front End 'config-lang.in' File: Front End Config, for details of
+ Front End `config-lang.in' File: Front End Config, for details of
its contents
-'Make-lang.in'
+
+`Make-lang.in'
This file is required in all language subdirectories. *Note The
- Front End 'Make-lang.in' File: Front End Makefile, for details of
+ Front End `Make-lang.in' File: Front End Makefile, for details of
its contents.
-'lang.opt'
+
+`lang.opt'
This file registers the set of switches that the front end accepts
- on the command line, and their '--help' text. *Note Options::.
-'lang-specs.h'
- This file provides entries for 'default_compilers' in 'gcc.c' which
- override the default of giving an error that a compiler for that
- language is not installed.
-'LANGUAGE-tree.def'
+ on the command line, and their `--help' text. *Note Options::.
+
+`lang-specs.h'
+ This file provides entries for `default_compilers' in `gcc.c'
+ which override the default of giving an error that a compiler for
+ that language is not installed.
+
+`LANGUAGE-tree.def'
This file, which need not exist, defines any language-specific tree
codes.

File: gccint.info, Node: Front End Config, Next: Front End Makefile, Prev: Front End Directory, Up: Front End
-6.3.8.2 The Front End 'config-lang.in' File
+6.3.8.2 The Front End `config-lang.in' File
...........................................
-Each language subdirectory contains a 'config-lang.in' file. This file
+Each language subdirectory contains a `config-lang.in' file. This file
is a shell script that may define some variables describing the
language:
-'language'
+`language'
This definition must be present, and gives the name of the language
- for some purposes such as arguments to '--enable-languages'.
-'lang_requires'
+ for some purposes such as arguments to `--enable-languages'.
+
+`lang_requires'
If defined, this variable lists (space-separated) language front
ends other than C that this front end requires to be enabled (with
- the names given being their 'language' settings). For example, the
+ the names given being their `language' settings). For example, the
Java front end depends on the C++ front end, so sets
- 'lang_requires=c++'.
-'subdir_requires'
+ `lang_requires=c++'.
+
+`subdir_requires'
If defined, this variable lists (space-separated) front end
directories other than C that this front end requires to be
present. For example, the Objective-C++ front end uses source
files from the C++ and Objective-C front ends, so sets
- 'subdir_requires="cp objc"'.
-'target_libs'
+ `subdir_requires="cp objc"'.
+
+`target_libs'
If defined, this variable lists (space-separated) targets in the
- top level 'Makefile' to build the runtime libraries for this
- language, such as 'target-libobjc'.
-'lang_dirs'
+ top level `Makefile' to build the runtime libraries for this
+ language, such as `target-libobjc'.
+
+`lang_dirs'
If defined, this variable lists (space-separated) top level
- directories (parallel to 'gcc'), apart from the runtime libraries,
+ directories (parallel to `gcc'), apart from the runtime libraries,
that should not be configured if this front end is not built.
-'build_by_default'
- If defined to 'no', this language front end is not built unless
- enabled in a '--enable-languages' argument. Otherwise, front ends
+
+`build_by_default'
+ If defined to `no', this language front end is not built unless
+ enabled in a `--enable-languages' argument. Otherwise, front ends
are built by default, subject to any special logic in
- 'configure.ac' (as is present to disable the Ada front end if the
+ `configure.ac' (as is present to disable the Ada front end if the
Ada compiler is not already installed).
-'boot_language'
- If defined to 'yes', this front end is built in stage1 of the
+
+`boot_language'
+ If defined to `yes', this front end is built in stage1 of the
bootstrap. This is only relevant to front ends written in their
own languages.
-'compilers'
+
+`compilers'
If defined, a space-separated list of compiler executables that
will be run by the driver. The names here will each end with
- '\$(exeext)'.
-'outputs'
+ `\$(exeext)'.
+
+`outputs'
If defined, a space-separated list of files that should be
- generated by 'configure' substituting values in them. This
- mechanism can be used to create a file 'LANGUAGE/Makefile' from
- 'LANGUAGE/Makefile.in', but this is deprecated, building everything
- from the single 'gcc/Makefile' is preferred.
-'gtfiles'
+ generated by `configure' substituting values in them. This
+ mechanism can be used to create a file `LANGUAGE/Makefile' from
+ `LANGUAGE/Makefile.in', but this is deprecated, building
+ everything from the single `gcc/Makefile' is preferred.
+
+`gtfiles'
If defined, a space-separated list of files that should be scanned
- by 'gengtype.c' to generate the garbage collection tables and
+ by `gengtype.c' to generate the garbage collection tables and
routines for this language. This excludes the files that are
common to all front ends. *Note Type Information::.
+

File: gccint.info, Node: Front End Makefile, Prev: Front End Config, Up: Front End
-6.3.8.3 The Front End 'Make-lang.in' File
+6.3.8.3 The Front End `Make-lang.in' File
.........................................
-Each language subdirectory contains a 'Make-lang.in' file. It contains
-targets 'LANG.HOOK' (where 'LANG' is the setting of 'language' in
-'config-lang.in') for the following values of 'HOOK', and any other
+Each language subdirectory contains a `Make-lang.in' file. It contains
+targets `LANG.HOOK' (where `LANG' is the setting of `language' in
+`config-lang.in') for the following values of `HOOK', and any other
Makefile rules required to build those targets (which may if necessary
-use other Makefiles specified in 'outputs' in 'config-lang.in', although
-this is deprecated). It also adds any testsuite targets that can use
-the standard rule in 'gcc/Makefile.in' to the variable 'lang_checks'.
-
-'all.cross'
-'start.encap'
-'rest.encap'
+use other Makefiles specified in `outputs' in `config-lang.in',
+although this is deprecated). It also adds any testsuite targets that
+can use the standard rule in `gcc/Makefile.in' to the variable
+`lang_checks'.
+
+`all.cross'
+`start.encap'
+`rest.encap'
FIXME: exactly what goes in each of these targets?
-'tags'
- Build an 'etags' 'TAGS' file in the language subdirectory in the
+
+`tags'
+ Build an `etags' `TAGS' file in the language subdirectory in the
source tree.
-'info'
+
+`info'
Build info documentation for the front end, in the build directory.
- This target is only called by 'make bootstrap' if a suitable
- version of 'makeinfo' is available, so does not need to check for
+ This target is only called by `make bootstrap' if a suitable
+ version of `makeinfo' is available, so does not need to check for
this, and should fail if an error occurs.
-'dvi'
+
+`dvi'
Build DVI documentation for the front end, in the build directory.
- This should be done using '$(TEXI2DVI)', with appropriate '-I'
+ This should be done using `$(TEXI2DVI)', with appropriate `-I'
arguments pointing to directories of included files.
-'pdf'
+
+`pdf'
Build PDF documentation for the front end, in the build directory.
- This should be done using '$(TEXI2PDF)', with appropriate '-I'
+ This should be done using `$(TEXI2PDF)', with appropriate `-I'
arguments pointing to directories of included files.
-'html'
+
+`html'
Build HTML documentation for the front end, in the build directory.
-'man'
+
+`man'
Build generated man pages for the front end from Texinfo manuals
(*note Man Page Generation::), in the build directory. This target
is only called if the necessary tools are available, but should
ignore errors so as not to stop the build if errors occur; man
pages are optional and the tools involved may be installed in a
broken way.
-'install-common'
+
+`install-common'
Install everything that is part of the front end, apart from the
- compiler executables listed in 'compilers' in 'config-lang.in'.
-'install-info'
+ compiler executables listed in `compilers' in `config-lang.in'.
+
+`install-info'
Install info documentation for the front end, if it is present in
- the source directory. This target should have dependencies on info
- files that should be installed.
-'install-man'
+ the source directory. This target should have dependencies on
+ info files that should be installed.
+
+`install-man'
Install man pages for the front end. This target should ignore
errors.
-'install-plugin'
+
+`install-plugin'
Install headers needed for plugins.
-'srcextra'
+
+`srcextra'
Copies its dependencies into the source directory. This generally
- should be used for generated files such as Bison output files which
- are not version-controlled, but should be included in any release
- tarballs. This target will be executed during a bootstrap if
- '--enable-generated-files-in-srcdir' was specified as a 'configure'
- option.
-'srcinfo'
-'srcman'
+ should be used for generated files such as Bison output files
+ which are not version-controlled, but should be included in any
+ release tarballs. This target will be executed during a bootstrap
+ if `--enable-generated-files-in-srcdir' was specified as a
+ `configure' option.
+
+`srcinfo'
+`srcman'
Copies its dependencies into the source directory. These targets
will be executed during a bootstrap if
- '--enable-generated-files-in-srcdir' was specified as a 'configure'
- option.
-'uninstall'
+ `--enable-generated-files-in-srcdir' was specified as a
+ `configure' option.
+
+`uninstall'
Uninstall files installed by installing the compiler. This is
currently documented not to be supported, so the hook need not do
anything.
-'mostlyclean'
-'clean'
-'distclean'
-'maintainer-clean'
- The language parts of the standard GNU '*clean' targets. *Note
+
+`mostlyclean'
+`clean'
+`distclean'
+`maintainer-clean'
+ The language parts of the standard GNU `*clean' targets. *Note
Standard Targets for Users: (standards)Standard Targets, for
- details of the standard targets. For GCC, 'maintainer-clean'
+ details of the standard targets. For GCC, `maintainer-clean'
should delete all generated files in the source directory that are
not version-controlled, but should not delete anything that is.
- 'Make-lang.in' must also define a variable 'LANG_OBJS' to a list of
+ `Make-lang.in' must also define a variable `LANG_OBJS' to a list of
host object files that are used by that language.

@@ -4054,68 +4131,84 @@ File: gccint.info, Node: Back End, Prev: Front End, Up: gcc Directory
A back end for a target architecture in GCC has the following parts:
- * A directory 'MACHINE' under 'gcc/config', containing a machine
- description 'MACHINE.md' file (*note Machine Descriptions: Machine
- Desc.), header files 'MACHINE.h' and 'MACHINE-protos.h' and a
- source file 'MACHINE.c' (*note Target Description Macros and
+ * A directory `MACHINE' under `gcc/config', containing a machine
+ description `MACHINE.md' file (*note Machine Descriptions: Machine
+ Desc.), header files `MACHINE.h' and `MACHINE-protos.h' and a
+ source file `MACHINE.c' (*note Target Description Macros and
Functions: Target Macros.), possibly a target Makefile fragment
- 't-MACHINE' (*note The Target Makefile Fragment: Target Fragment.),
- and maybe some other files. The names of these files may be
- changed from the defaults given by explicit specifications in
- 'config.gcc'.
- * If necessary, a file 'MACHINE-modes.def' in the 'MACHINE'
+ `t-MACHINE' (*note The Target Makefile Fragment: Target
+ Fragment.), and maybe some other files. The names of these files
+ may be changed from the defaults given by explicit specifications
+ in `config.gcc'.
+
+ * If necessary, a file `MACHINE-modes.def' in the `MACHINE'
directory, containing additional machine modes to represent
condition codes. *Note Condition Code::, for further details.
- * An optional 'MACHINE.opt' file in the 'MACHINE' directory,
+
+ * An optional `MACHINE.opt' file in the `MACHINE' directory,
containing a list of target-specific options. You can also add
- other option files using the 'extra_options' variable in
- 'config.gcc'. *Note Options::.
- * Entries in 'config.gcc' (*note The 'config.gcc' File: System
+ other option files using the `extra_options' variable in
+ `config.gcc'. *Note Options::.
+
+ * Entries in `config.gcc' (*note The `config.gcc' File: System
Config.) for the systems with this target architecture.
- * Documentation in 'gcc/doc/invoke.texi' for any command-line options
- supported by this target (*note Run-time Target Specification:
- Run-time Target.). This means both entries in the summary table of
- options and details of the individual options.
- * Documentation in 'gcc/doc/extend.texi' for any target-specific
+
+ * Documentation in `gcc/doc/invoke.texi' for any command-line
+ options supported by this target (*note Run-time Target
+ Specification: Run-time Target.). This means both entries in the
+ summary table of options and details of the individual options.
+
+ * Documentation in `gcc/doc/extend.texi' for any target-specific
attributes supported (*note Defining target-specific uses of
- '__attribute__': Target Attributes.), including where the same
+ `__attribute__': Target Attributes.), including where the same
attribute is already supported on some targets, which are
enumerated in the manual.
- * Documentation in 'gcc/doc/extend.texi' for any target-specific
+
+ * Documentation in `gcc/doc/extend.texi' for any target-specific
pragmas supported.
- * Documentation in 'gcc/doc/extend.texi' of any target-specific
+
+ * Documentation in `gcc/doc/extend.texi' of any target-specific
built-in functions supported.
- * Documentation in 'gcc/doc/extend.texi' of any target-specific
+
+ * Documentation in `gcc/doc/extend.texi' of any target-specific
format checking styles supported.
- * Documentation in 'gcc/doc/md.texi' of any target-specific
+
+ * Documentation in `gcc/doc/md.texi' of any target-specific
constraint letters (*note Constraints for Particular Machines:
Machine Constraints.).
- * A note in 'gcc/doc/contrib.texi' under the person or people who
+
+ * A note in `gcc/doc/contrib.texi' under the person or people who
contributed the target support.
- * Entries in 'gcc/doc/install.texi' for all target triplets supported
- with this target architecture, giving details of any special notes
- about installation for this target, or saying that there are no
- special notes if there are none.
- * Possibly other support outside the 'gcc' directory for runtime
- libraries. FIXME: reference docs for this. The 'libstdc++'
+
+ * Entries in `gcc/doc/install.texi' for all target triplets
+ supported with this target architecture, giving details of any
+ special notes about installation for this target, or saying that
+ there are no special notes if there are none.
+
+ * Possibly other support outside the `gcc' directory for runtime
+ libraries. FIXME: reference docs for this. The `libstdc++'
porting manual needs to be installed as info for this to work, or
to be a chapter of this manual.
If the back end is added to the official GCC source repository, the
following are also necessary:
- * An entry for the target architecture in 'readings.html' on the GCC
+ * An entry for the target architecture in `readings.html' on the GCC
web site, with any relevant links.
+
* Details of the properties of the back end and target architecture
- in 'backends.html' on the GCC web site.
+ in `backends.html' on the GCC web site.
+
* A news item about the contribution of support for that target
- architecture, in 'index.html' on the GCC web site.
+ architecture, in `index.html' on the GCC web site.
+
* Normally, one or more maintainers of that target listed in
- 'MAINTAINERS'. Some existing architectures may be unmaintained,
+ `MAINTAINERS'. Some existing architectures may be unmaintained,
but it would be unusual to add support for a target that does not
have a maintainer when support is added.
- * Target triplets covering all 'config.gcc' stanzas for the target,
- in the list in 'contrib/config-list.mk'.
+
+ * Target triplets covering all `config.gcc' stanzas for the target,
+ in the list in `contrib/config-list.mk'.

File: gccint.info, Node: Testsuites, Next: Options, Prev: Source Tree, Up: Top
@@ -4123,10 +4216,10 @@ File: gccint.info, Node: Testsuites, Next: Options, Prev: Source Tree, Up: T
7 Testsuites
************
-GCC contains several testsuites to help maintain compiler quality. Most
-of the runtime libraries and language front ends in GCC have testsuites.
-Currently only the C language testsuites are documented here; FIXME:
-document the others.
+GCC contains several testsuites to help maintain compiler quality.
+Most of the runtime libraries and language front ends in GCC have
+testsuites. Currently only the C language testsuites are documented
+here; FIXME: document the others.
* Menu:
@@ -4147,42 +4240,42 @@ File: gccint.info, Node: Test Idioms, Next: Test Directives, Up: Testsuites
7.1 Idioms Used in Testsuite Code
=================================
-In general, C testcases have a trailing '-N.c', starting with '-1.c', in
-case other testcases with similar names are added later. If the test is
-a test of some well-defined feature, it should have a name referring to
-that feature such as 'FEATURE-1.c'. If it does not test a well-defined
-feature but just happens to exercise a bug somewhere in the compiler,
-and a bug report has been filed for this bug in the GCC bug database,
-'prBUG-NUMBER-1.c' is the appropriate form of name. Otherwise (for
-miscellaneous bugs not filed in the GCC bug database), and previously
-more generally, test cases are named after the date on which they were
-added. This allows people to tell at a glance whether a test failure is
-because of a recently found bug that has not yet been fixed, or whether
-it may be a regression, but does not give any other information about
-the bug or where discussion of it may be found. Some other language
-testsuites follow similar conventions.
-
- In the 'gcc.dg' testsuite, it is often necessary to test that an error
+In general, C testcases have a trailing `-N.c', starting with `-1.c',
+in case other testcases with similar names are added later. If the
+test is a test of some well-defined feature, it should have a name
+referring to that feature such as `FEATURE-1.c'. If it does not test a
+well-defined feature but just happens to exercise a bug somewhere in
+the compiler, and a bug report has been filed for this bug in the GCC
+bug database, `prBUG-NUMBER-1.c' is the appropriate form of name.
+Otherwise (for miscellaneous bugs not filed in the GCC bug database),
+and previously more generally, test cases are named after the date on
+which they were added. This allows people to tell at a glance whether
+a test failure is because of a recently found bug that has not yet been
+fixed, or whether it may be a regression, but does not give any other
+information about the bug or where discussion of it may be found. Some
+other language testsuites follow similar conventions.
+
+ In the `gcc.dg' testsuite, it is often necessary to test that an error
is indeed a hard error and not just a warning--for example, where it is
a constraint violation in the C standard, which must become an error
-with '-pedantic-errors'. The following idiom, where the first line
-shown is line LINE of the file and the line that generates the error, is
-used for this:
+with `-pedantic-errors'. The following idiom, where the first line
+shown is line LINE of the file and the line that generates the error,
+is used for this:
/* { dg-bogus "warning" "warning in place of error" } */
/* { dg-error "REGEXP" "MESSAGE" { target *-*-* } LINE } */
It may be necessary to check that an expression is an integer constant
-expression and has a certain value. To check that 'E' has value 'V', an
-idiom similar to the following is used:
+expression and has a certain value. To check that `E' has value `V',
+an idiom similar to the following is used:
char x[((E) == (V) ? 1 : -1)];
- In 'gcc.dg' tests, '__typeof__' is sometimes used to make assertions
+ In `gcc.dg' tests, `__typeof__' is sometimes used to make assertions
about the types of expressions. See, for example,
-'gcc.dg/c99-condexpr-1.c'. The more subtle uses depend on the exact
+`gcc.dg/c99-condexpr-1.c'. The more subtle uses depend on the exact
rules for the types of conditional expressions in the C standard; see,
-for example, 'gcc.dg/c99-intconst-1.c'.
+for example, `gcc.dg/c99-intconst-1.c'.
It is useful to be able to test that optimizations are being made
properly. This cannot be done in all cases, but it can be done where
@@ -4190,8 +4283,8 @@ the optimization will lead to code being optimized away (for example,
where flow analysis or alias analysis should show that certain code
cannot be called) or to functions not being called because they have
been expanded as built-in functions. Such tests go in
-'gcc.c-torture/execute'. Where code should be optimized away, a call to
-a nonexistent function such as 'link_failure ()' may be inserted; a
+`gcc.c-torture/execute'. Where code should be optimized away, a call
+to a nonexistent function such as `link_failure ()' may be inserted; a
definition
#ifndef __OPTIMIZE__
@@ -4203,11 +4296,11 @@ definition
#endif
will also be needed so that linking still succeeds when the test is run
-without optimization. When all calls to a built-in function should have
-been optimized and no calls to the non-built-in version of the function
-should remain, that function may be defined as 'static' to call 'abort
-()' (although redeclaring a function as static may not work on all
-targets).
+without optimization. When all calls to a built-in function should
+have been optimized and no calls to the non-built-in version of the
+function should remain, that function may be defined as `static' to
+call `abort ()' (although redeclaring a function as static may not work
+on all targets).
All testcases must be portable. Target-specific testcases must have
appropriate code to avoid causing failures on unsupported systems;
@@ -4226,9 +4319,9 @@ File: gccint.info, Node: Test Directives, Next: Ada Tests, Prev: Test Idioms,
* Directives:: Syntax and descriptions of test directives.
* Selectors:: Selecting targets to which a test applies.
* Effective-Target Keywords:: Keywords describing target attributes.
-* Add Options:: Features for 'dg-add-options'
-* Require Support:: Variants of 'dg-require-SUPPORT'
-* Final Actions:: Commands for use in 'dg-final'
+* Add Options:: Features for `dg-add-options'
+* Require Support:: Variants of `dg-require-SUPPORT'
+* Final Actions:: Commands for use in `dg-final'

File: gccint.info, Node: Directives, Next: Selectors, Up: Test Directives
@@ -4237,7 +4330,7 @@ File: gccint.info, Node: Directives, Next: Selectors, Up: Test Directives
------------------------------------------------
Test directives appear within comments in a test source file and begin
-with 'dg-'. Some of these are defined within DejaGnu and others are
+with `dg-'. Some of these are defined within DejaGnu and others are
local to the GCC testsuite.
The order in which test directives appear in a test can be important:
@@ -4245,56 +4338,61 @@ directives local to GCC sometimes override information used by the
DejaGnu directives, which know nothing about the GCC directives, so the
DejaGnu directives must precede GCC directives.
- Several test directives include selectors (*note Selectors::) which are
-usually preceded by the keyword 'target' or 'xfail'.
+ Several test directives include selectors (*note Selectors::) which
+are usually preceded by the keyword `target' or `xfail'.
7.2.1.1 Specify how to build the test
.....................................
-'{ dg-do DO-WHAT-KEYWORD [{ target/xfail SELECTOR }] }'
+`{ dg-do DO-WHAT-KEYWORD [{ target/xfail SELECTOR }] }'
DO-WHAT-KEYWORD specifies how the test is compiled and whether it
is executed. It is one of:
- 'preprocess'
- Compile with '-E' to run only the preprocessor.
- 'compile'
- Compile with '-S' to produce an assembly code file.
- 'assemble'
- Compile with '-c' to produce a relocatable object file.
- 'link'
+ `preprocess'
+ Compile with `-E' to run only the preprocessor.
+
+ `compile'
+ Compile with `-S' to produce an assembly code file.
+
+ `assemble'
+ Compile with `-c' to produce a relocatable object file.
+
+ `link'
Compile, assemble, and link to produce an executable file.
- 'run'
+
+ `run'
Produce and run an executable file, which is expected to
return an exit code of 0.
- The default is 'compile'. That can be overridden for a set of
- tests by redefining 'dg-do-what-default' within the '.exp' file for
- those tests.
+ The default is `compile'. That can be overridden for a set of
+ tests by redefining `dg-do-what-default' within the `.exp' file
+ for those tests.
- If the directive includes the optional '{ target SELECTOR }' then
+ If the directive includes the optional `{ target SELECTOR }' then
the test is skipped unless the target system matches the SELECTOR.
- If DO-WHAT-KEYWORD is 'run' and the directive includes the optional
- '{ xfail SELECTOR }' and the selector is met then the test is
- expected to fail. The 'xfail' clause is ignored for other values
- of DO-WHAT-KEYWORD; those tests can use directive 'dg-xfail-if'.
+ If DO-WHAT-KEYWORD is `run' and the directive includes the
+ optional `{ xfail SELECTOR }' and the selector is met then the
+ test is expected to fail. The `xfail' clause is ignored for other
+ values of DO-WHAT-KEYWORD; those tests can use directive
+ `dg-xfail-if'.
7.2.1.2 Specify additional compiler options
...........................................
-'{ dg-options OPTIONS [{ target SELECTOR }] }'
+`{ dg-options OPTIONS [{ target SELECTOR }] }'
This DejaGnu directive provides a list of compiler options, to be
used if the target system matches SELECTOR, that replace the
default options used for this set of tests.
-'{ dg-add-options FEATURE ... }'
+`{ dg-add-options FEATURE ... }'
Add any compiler options that are needed to access certain
features. This directive does nothing on targets that enable the
features by default, or that don't provide them at all. It must
- come after all 'dg-options' directives. For supported values of
+ come after all `dg-options' directives. For supported values of
FEATURE see *note Add Options::.
-'{ dg-additional-options OPTIONS [{ target SELECTOR }] }'
+`{ dg-additional-options OPTIONS [{ target SELECTOR }] }'
This directive provides a list of compiler options, to be used if
the target system matches SELECTOR, that are added to the default
options used for this set of tests.
@@ -4305,7 +4403,7 @@ usually preceded by the keyword 'target' or 'xfail'.
The normal timeout limit, in seconds, is found by searching the
following in order:
- * the value defined by an earlier 'dg-timeout' directive in the test
+ * the value defined by an earlier `dg-timeout' directive in the test
* variable TOOL_TIMEOUT defined by the set of tests
@@ -4313,18 +4411,18 @@ following in order:
* 300
-'{ dg-timeout N [{target SELECTOR }] }'
- Set the time limit for the compilation and for the execution of the
- test to the specified number of seconds.
+`{ dg-timeout N [{target SELECTOR }] }'
+ Set the time limit for the compilation and for the execution of
+ the test to the specified number of seconds.
-'{ dg-timeout-factor X [{ target SELECTOR }] }'
- Multiply the normal time limit for compilation and execution of the
- test by the specified floating-point factor.
+`{ dg-timeout-factor X [{ target SELECTOR }] }'
+ Multiply the normal time limit for compilation and execution of
+ the test by the specified floating-point factor.
7.2.1.4 Skip a test for some targets
....................................
-'{ dg-skip-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
+`{ dg-skip-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
Arguments INCLUDE-OPTS and EXCLUDE-OPTS are lists in which each
element is a string of zero or more GCC options. Skip the test if
all of the following conditions are met:
@@ -4332,50 +4430,50 @@ following in order:
* for at least one of the option strings in INCLUDE-OPTS, every
option from that string is in the set of options with which
- the test would be compiled; use '"*"' for an INCLUDE-OPTS list
+ the test would be compiled; use `"*"' for an INCLUDE-OPTS list
that matches any options; that is the default if INCLUDE-OPTS
is not specified
* for each of the option strings in EXCLUDE-OPTS, at least one
option from that string is not in the set of options with
- which the test would be compiled; use '""' for an empty
+ which the test would be compiled; use `""' for an empty
EXCLUDE-OPTS list; that is the default if EXCLUDE-OPTS is not
specified
- For example, to skip a test if option '-Os' is present:
+ For example, to skip a test if option `-Os' is present:
/* { dg-skip-if "" { *-*-* } { "-Os" } { "" } } */
- To skip a test if both options '-O2' and '-g' are present:
+ To skip a test if both options `-O2' and `-g' are present:
/* { dg-skip-if "" { *-*-* } { "-O2 -g" } { "" } } */
- To skip a test if either '-O2' or '-O3' is present:
+ To skip a test if either `-O2' or `-O3' is present:
/* { dg-skip-if "" { *-*-* } { "-O2" "-O3" } { "" } } */
- To skip a test unless option '-Os' is present:
+ To skip a test unless option `-Os' is present:
/* { dg-skip-if "" { *-*-* } { "*" } { "-Os" } } */
- To skip a test if either '-O2' or '-O3' is used with '-g' but not
- if '-fpic' is also present:
+ To skip a test if either `-O2' or `-O3' is used with `-g' but not
+ if `-fpic' is also present:
/* { dg-skip-if "" { *-*-* } { "-O2 -g" "-O3 -g" } { "-fpic" } } */
-'{ dg-require-effective-target KEYWORD [{ SELECTOR }] }'
+`{ dg-require-effective-target KEYWORD [{ SELECTOR }] }'
Skip the test if the test target, including current multilib flags,
is not covered by the effective-target keyword. If the directive
- includes the optional '{ SELECTOR }' then the effective-target test
- is only performed if the target system matches the SELECTOR. This
- directive must appear after any 'dg-do' directive in the test and
- before any 'dg-additional-sources' directive. *Note
+ includes the optional `{ SELECTOR }' then the effective-target
+ test is only performed if the target system matches the SELECTOR.
+ This directive must appear after any `dg-do' directive in the test
+ and before any `dg-additional-sources' directive. *Note
Effective-Target Keywords::.
-'{ dg-require-SUPPORT args }'
+`{ dg-require-SUPPORT args }'
Skip the test if the target does not provide the required support.
- These directives must appear after any 'dg-do' directive in the
- test and before any 'dg-additional-sources' directive. They
+ These directives must appear after any `dg-do' directive in the
+ test and before any `dg-additional-sources' directive. They
require at least one argument, which can be an empty string if the
specific procedure does not examine the argument. *Note Require
Support::, for a complete list of these directives.
@@ -4383,89 +4481,91 @@ following in order:
7.2.1.5 Expect a test to fail for some targets
..............................................
-'{ dg-xfail-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
+`{ dg-xfail-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
Expect the test to fail if the conditions (which are the same as
- for 'dg-skip-if') are met. This does not affect the execute step.
+ for `dg-skip-if') are met. This does not affect the execute step.
-'{ dg-xfail-run-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
+`{ dg-xfail-run-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }'
Expect the execute step of a test to fail if the conditions (which
- are the same as for 'dg-skip-if') are met.
+ are the same as for `dg-skip-if') are met.
7.2.1.6 Expect the test executable to fail
..........................................
-'{ dg-shouldfail COMMENT [{ SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]]] }'
+`{ dg-shouldfail COMMENT [{ SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]]] }'
Expect the test executable to return a nonzero exit status if the
- conditions (which are the same as for 'dg-skip-if') are met.
+ conditions (which are the same as for `dg-skip-if') are met.
7.2.1.7 Verify compiler messages
................................
-'{ dg-error REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
- This DejaGnu directive appears on a source line that is expected to
- get an error message, or else specifies the source line associated
- with the message. If there is no message for that line or if the
- text of that message is not matched by REGEXP then the check fails
- and COMMENT is included in the 'FAIL' message. The check does not
- look for the string 'error' unless it is part of REGEXP.
-
-'{ dg-warning REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
- This DejaGnu directive appears on a source line that is expected to
- get a warning message, or else specifies the source line associated
- with the message. If there is no message for that line or if the
- text of that message is not matched by REGEXP then the check fails
- and COMMENT is included in the 'FAIL' message. The check does not
- look for the string 'warning' unless it is part of REGEXP.
-
-'{ dg-message REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
+`{ dg-error REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
+ This DejaGnu directive appears on a source line that is expected
+ to get an error message, or else specifies the source line
+ associated with the message. If there is no message for that line
+ or if the text of that message is not matched by REGEXP then the
+ check fails and COMMENT is included in the `FAIL' message. The
+ check does not look for the string `error' unless it is part of
+ REGEXP.
+
+`{ dg-warning REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
+ This DejaGnu directive appears on a source line that is expected
+ to get a warning message, or else specifies the source line
+ associated with the message. If there is no message for that line
+ or if the text of that message is not matched by REGEXP then the
+ check fails and COMMENT is included in the `FAIL' message. The
+ check does not look for the string `warning' unless it is part of
+ REGEXP.
+
+`{ dg-message REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
The line is expected to get a message other than an error or
warning. If there is no message for that line or if the text of
that message is not matched by REGEXP then the check fails and
- COMMENT is included in the 'FAIL' message.
+ COMMENT is included in the `FAIL' message.
-'{ dg-bogus REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
- This DejaGnu directive appears on a source line that should not get
- a message matching REGEXP, or else specifies the source line
- associated with the bogus message. It is usually used with 'xfail'
+`{ dg-bogus REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }'
+ This DejaGnu directive appears on a source line that should not
+ get a message matching REGEXP, or else specifies the source line
+ associated with the bogus message. It is usually used with `xfail'
to indicate that the message is a known problem for a particular
set of targets.
-'{ dg-excess-errors COMMENT [{ target/xfail SELECTOR }] }'
+`{ dg-excess-errors COMMENT [{ target/xfail SELECTOR }] }'
This DejaGnu directive indicates that the test is expected to fail
- due to compiler messages that are not handled by 'dg-error',
- 'dg-warning' or 'dg-bogus'. For this directive 'xfail' has the
- same effect as 'target'.
+ due to compiler messages that are not handled by `dg-error',
+ `dg-warning' or `dg-bogus'. For this directive `xfail' has the
+ same effect as `target'.
-'{ dg-prune-output REGEXP }'
+`{ dg-prune-output REGEXP }'
Prune messages matching REGEXP from the test output.
7.2.1.8 Verify output of the test executable
............................................
-'{ dg-output REGEXP [{ target/xfail SELECTOR }] }'
+`{ dg-output REGEXP [{ target/xfail SELECTOR }] }'
This DejaGnu directive compares REGEXP to the combined output that
- the test executable writes to 'stdout' and 'stderr'.
+ the test executable writes to `stdout' and `stderr'.
7.2.1.9 Specify additional files for a test
...........................................
-'{ dg-additional-files "FILELIST" }'
+`{ dg-additional-files "FILELIST" }'
Specify additional files, other than source files, that must be
copied to the system where the compiler runs.
-'{ dg-additional-sources "FILELIST" }'
+`{ dg-additional-sources "FILELIST" }'
Specify additional source files to appear in the compile line
following the main test file.
7.2.1.10 Add checks at the end of a test
........................................
-'{ dg-final { LOCAL-DIRECTIVE } }'
+`{ dg-final { LOCAL-DIRECTIVE } }'
This DejaGnu directive is placed within a comment anywhere in the
source file and is processed after the test has been compiled and
- run. Multiple 'dg-final' commands are processed in the order in
- which they appear in the source file. *Note Final Actions::, for a
- list of directives that can be used within 'dg-final'.
+ run. Multiple `dg-final' commands are processed in the order in
+ which they appear in the source file. *Note Final Actions::, for
+ a list of directives that can be used within `dg-final'.

File: gccint.info, Node: Selectors, Next: Effective-Target Keywords, Prev: Directives, Up: Test Directives
@@ -4473,25 +4573,27 @@ File: gccint.info, Node: Selectors, Next: Effective-Target Keywords, Prev: Di
7.2.2 Selecting targets to which a test applies
-----------------------------------------------
-Several test directives include SELECTORs to limit the targets for which
-a test is run or to declare that a test is expected to fail on
+Several test directives include SELECTORs to limit the targets for
+which a test is run or to declare that a test is expected to fail on
particular targets.
A selector is:
* one or more target triplets, possibly including wildcard
- characters; use '*-*-*' to match any target
+ characters; use `*-*-*' to match any target
+
* a single effective-target keyword (*note Effective-Target
Keywords::)
+
* a logical expression
Depending on the context, the selector specifies whether a test is
skipped and reported as unsupported or is expected to fail. A context
-that allows either 'target' or 'xfail' also allows '{ target SELECTOR1
+that allows either `target' or `xfail' also allows `{ target SELECTOR1
xfail SELECTOR2 }' to skip the test for targets that don't match
SELECTOR1 and the test to fail for targets that match SELECTOR2.
A selector expression appears within curly braces and uses a single
-logical operator: one of '!', '&&', or '||'. An operand is another
+logical operator: one of `!', `&&', or `||'. An operand is another
selector expression, an effective-target keyword, a single target
triplet, or a list of target triplets within quotes or curly braces.
For example:
@@ -4511,942 +4613,946 @@ particular functionality. They are used to limit tests to be run only
for particular targets, or to specify that particular sets of targets
are expected to fail some tests.
- Effective-target keywords are defined in 'lib/target-supports.exp' in
+ Effective-target keywords are defined in `lib/target-supports.exp' in
the GCC testsuite, with the exception of those that are documented as
being local to a particular test directory.
- The 'effective target' takes into account all of the compiler options
+ The `effective target' takes into account all of the compiler options
with which the test will be compiled, including the multilib options.
-By convention, keywords ending in '_nocache' can also include options
-specified for the particular test in an earlier 'dg-options' or
-'dg-add-options' directive.
+By convention, keywords ending in `_nocache' can also include options
+specified for the particular test in an earlier `dg-options' or
+`dg-add-options' directive.
7.2.3.1 Data type sizes
.......................
-'ilp32'
- Target has 32-bit 'int', 'long', and pointers.
+`ilp32'
+ Target has 32-bit `int', `long', and pointers.
-'lp64'
- Target has 32-bit 'int', 64-bit 'long' and pointers.
+`lp64'
+ Target has 32-bit `int', 64-bit `long' and pointers.
-'llp64'
- Target has 32-bit 'int' and 'long', 64-bit 'long long' and
+`llp64'
+ Target has 32-bit `int' and `long', 64-bit `long long' and
pointers.
-'double64'
- Target has 64-bit 'double'.
+`double64'
+ Target has 64-bit `double'.
-'double64plus'
- Target has 'double' that is 64 bits or longer.
+`double64plus'
+ Target has `double' that is 64 bits or longer.
-'longdouble128'
- Target has 128-bit 'long double'.
+`longdouble128'
+ Target has 128-bit `long double'.
-'int32plus'
- Target has 'int' that is at 32 bits or longer.
+`int32plus'
+ Target has `int' that is at 32 bits or longer.
-'int16'
- Target has 'int' that is 16 bits or shorter.
+`int16'
+ Target has `int' that is 16 bits or shorter.
-'long_neq_int'
- Target has 'int' and 'long' with different sizes.
+`long_neq_int'
+ Target has `int' and `long' with different sizes.
-'large_double'
- Target supports 'double' that is longer than 'float'.
+`large_double'
+ Target supports `double' that is longer than `float'.
-'large_long_double'
- Target supports 'long double' that is longer than 'double'.
+`large_long_double'
+ Target supports `long double' that is longer than `double'.
-'ptr32plus'
+`ptr32plus'
Target has pointers that are 32 bits or longer.
-'size32plus'
+`size32plus'
Target supports array and structure sizes that are 32 bits or
longer.
-'4byte_wchar_t'
- Target has 'wchar_t' that is at least 4 bytes.
+`4byte_wchar_t'
+ Target has `wchar_t' that is at least 4 bytes.
7.2.3.2 Fortran-specific attributes
...................................
-'fortran_integer_16'
- Target supports Fortran 'integer' that is 16 bytes or longer.
+`fortran_integer_16'
+ Target supports Fortran `integer' that is 16 bytes or longer.
-'fortran_large_int'
- Target supports Fortran 'integer' kinds larger than 'integer(8)'.
+`fortran_large_int'
+ Target supports Fortran `integer' kinds larger than `integer(8)'.
-'fortran_large_real'
- Target supports Fortran 'real' kinds larger than 'real(8)'.
+`fortran_large_real'
+ Target supports Fortran `real' kinds larger than `real(8)'.
7.2.3.3 Vector-specific attributes
..................................
-'vect_condition'
+`vect_condition'
Target supports vector conditional operations.
-'vect_double'
- Target supports hardware vectors of 'double'.
+`vect_double'
+ Target supports hardware vectors of `double'.
-'vect_float'
- Target supports hardware vectors of 'float'.
+`vect_float'
+ Target supports hardware vectors of `float'.
-'vect_int'
- Target supports hardware vectors of 'int'.
+`vect_int'
+ Target supports hardware vectors of `int'.
-'vect_long'
- Target supports hardware vectors of 'long'.
+`vect_long'
+ Target supports hardware vectors of `long'.
-'vect_long_long'
- Target supports hardware vectors of 'long long'.
+`vect_long_long'
+ Target supports hardware vectors of `long long'.
-'vect_aligned_arrays'
+`vect_aligned_arrays'
Target aligns arrays to vector alignment boundary.
-'vect_hw_misalign'
+`vect_hw_misalign'
Target supports a vector misalign access.
-'vect_no_align'
+`vect_no_align'
Target does not support a vector alignment mechanism.
-'vect_no_int_max'
- Target does not support a vector max instruction on 'int'.
+`vect_no_int_max'
+ Target does not support a vector max instruction on `int'.
-'vect_no_int_add'
- Target does not support a vector add instruction on 'int'.
+`vect_no_int_add'
+ Target does not support a vector add instruction on `int'.
-'vect_no_bitwise'
+`vect_no_bitwise'
Target does not support vector bitwise instructions.
-'vect_char_mult'
- Target supports 'vector char' multiplication.
+`vect_char_mult'
+ Target supports `vector char' multiplication.
-'vect_short_mult'
- Target supports 'vector short' multiplication.
+`vect_short_mult'
+ Target supports `vector short' multiplication.
-'vect_int_mult'
- Target supports 'vector int' multiplication.
+`vect_int_mult'
+ Target supports `vector int' multiplication.
-'vect_extract_even_odd'
+`vect_extract_even_odd'
Target supports vector even/odd element extraction.
-'vect_extract_even_odd_wide'
+`vect_extract_even_odd_wide'
Target supports vector even/odd element extraction of vectors with
- elements 'SImode' or larger.
+ elements `SImode' or larger.
-'vect_interleave'
+`vect_interleave'
Target supports vector interleaving.
-'vect_strided'
+`vect_strided'
Target supports vector interleaving and extract even/odd.
-'vect_strided_wide'
+`vect_strided_wide'
Target supports vector interleaving and extract even/odd for wide
element types.
-'vect_perm'
+`vect_perm'
Target supports vector permutation.
-'vect_shift'
+`vect_shift'
Target supports a hardware vector shift operation.
-'vect_widen_sum_hi_to_si'
- Target supports a vector widening summation of 'short' operands
- into 'int' results, or can promote (unpack) from 'short' to 'int'.
+`vect_widen_sum_hi_to_si'
+ Target supports a vector widening summation of `short' operands
+ into `int' results, or can promote (unpack) from `short' to `int'.
-'vect_widen_sum_qi_to_hi'
- Target supports a vector widening summation of 'char' operands into
- 'short' results, or can promote (unpack) from 'char' to 'short'.
+`vect_widen_sum_qi_to_hi'
+ Target supports a vector widening summation of `char' operands
+ into `short' results, or can promote (unpack) from `char' to
+ `short'.
-'vect_widen_sum_qi_to_si'
- Target supports a vector widening summation of 'char' operands into
- 'int' results.
+`vect_widen_sum_qi_to_si'
+ Target supports a vector widening summation of `char' operands
+ into `int' results.
-'vect_widen_mult_qi_to_hi'
- Target supports a vector widening multiplication of 'char' operands
- into 'short' results, or can promote (unpack) from 'char' to
- 'short' and perform non-widening multiplication of 'short'.
+`vect_widen_mult_qi_to_hi'
+ Target supports a vector widening multiplication of `char' operands
+ into `short' results, or can promote (unpack) from `char' to
+ `short' and perform non-widening multiplication of `short'.
-'vect_widen_mult_hi_to_si'
- Target supports a vector widening multiplication of 'short'
- operands into 'int' results, or can promote (unpack) from 'short'
- to 'int' and perform non-widening multiplication of 'int'.
+`vect_widen_mult_hi_to_si'
+ Target supports a vector widening multiplication of `short'
+ operands into `int' results, or can promote (unpack) from `short'
+ to `int' and perform non-widening multiplication of `int'.
-'vect_widen_mult_si_to_di_pattern'
- Target supports a vector widening multiplication of 'int' operands
- into 'long' results.
+`vect_widen_mult_si_to_di_pattern'
+ Target supports a vector widening multiplication of `int' operands
+ into `long' results.
-'vect_sdot_qi'
- Target supports a vector dot-product of 'signed char'.
+`vect_sdot_qi'
+ Target supports a vector dot-product of `signed char'.
-'vect_udot_qi'
- Target supports a vector dot-product of 'unsigned char'.
+`vect_udot_qi'
+ Target supports a vector dot-product of `unsigned char'.
-'vect_sdot_hi'
- Target supports a vector dot-product of 'signed short'.
+`vect_sdot_hi'
+ Target supports a vector dot-product of `signed short'.
-'vect_udot_hi'
- Target supports a vector dot-product of 'unsigned short'.
+`vect_udot_hi'
+ Target supports a vector dot-product of `unsigned short'.
-'vect_pack_trunc'
- Target supports a vector demotion (packing) of 'short' to 'char'
- and from 'int' to 'short' using modulo arithmetic.
+`vect_pack_trunc'
+ Target supports a vector demotion (packing) of `short' to `char'
+ and from `int' to `short' using modulo arithmetic.
-'vect_unpack'
- Target supports a vector promotion (unpacking) of 'char' to 'short'
- and from 'char' to 'int'.
+`vect_unpack'
+ Target supports a vector promotion (unpacking) of `char' to `short'
+ and from `char' to `int'.
-'vect_intfloat_cvt'
- Target supports conversion from 'signed int' to 'float'.
+`vect_intfloat_cvt'
+ Target supports conversion from `signed int' to `float'.
-'vect_uintfloat_cvt'
- Target supports conversion from 'unsigned int' to 'float'.
+`vect_uintfloat_cvt'
+ Target supports conversion from `unsigned int' to `float'.
-'vect_floatint_cvt'
- Target supports conversion from 'float' to 'signed int'.
+`vect_floatint_cvt'
+ Target supports conversion from `float' to `signed int'.
-'vect_floatuint_cvt'
- Target supports conversion from 'float' to 'unsigned int'.
+`vect_floatuint_cvt'
+ Target supports conversion from `float' to `unsigned int'.
7.2.3.4 Thread Local Storage attributes
.......................................
-'tls'
+`tls'
Target supports thread-local storage.
-'tls_native'
+`tls_native'
Target supports native (rather than emulated) thread-local storage.
-'tls_runtime'
+`tls_runtime'
Test system supports executing TLS executables.
7.2.3.5 Decimal floating point attributes
.........................................
-'dfp'
+`dfp'
Targets supports compiling decimal floating point extension to C.
-'dfp_nocache'
+`dfp_nocache'
Including the options used to compile this particular test, the
target supports compiling decimal floating point extension to C.
-'dfprt'
+`dfprt'
Test system can execute decimal floating point tests.
-'dfprt_nocache'
+`dfprt_nocache'
Including the options used to compile this particular test, the
test system can execute decimal floating point tests.
-'hard_dfp'
+`hard_dfp'
Target generates decimal floating point instructions with current
options.
7.2.3.6 ARM-specific attributes
...............................
-'arm32'
+`arm32'
ARM target generates 32-bit code.
-'arm_eabi'
+`arm_eabi'
ARM target adheres to the ABI for the ARM Architecture.
-'arm_hf_eabi'
+`arm_hf_eabi'
ARM target adheres to the VFP and Advanced SIMD Register Arguments
variant of the ABI for the ARM Architecture (as selected with
- '-mfloat-abi=hard').
+ `-mfloat-abi=hard').
-'arm_hard_vfp_ok'
- ARM target supports '-mfpu=vfp -mfloat-abi=hard'. Some multilibs
+`arm_hard_vfp_ok'
+ ARM target supports `-mfpu=vfp -mfloat-abi=hard'. Some multilibs
may be incompatible with these options.
-'arm_iwmmxt_ok'
- ARM target supports '-mcpu=iwmmxt'. Some multilibs may be
+`arm_iwmmxt_ok'
+ ARM target supports `-mcpu=iwmmxt'. Some multilibs may be
incompatible with this option.
-'arm_neon'
+`arm_neon'
ARM target supports generating NEON instructions.
-'arm_tune_string_ops_prefer_neon'
+`arm_tune_string_ops_prefer_neon'
Test CPU tune supports inlining string operations with NEON
instructions.
-'arm_neon_hw'
+`arm_neon_hw'
Test system supports executing NEON instructions.
-'arm_neonv2_hw'
+`arm_neonv2_hw'
Test system supports executing NEON v2 instructions.
-'arm_neon_ok'
- ARM Target supports '-mfpu=neon -mfloat-abi=softfp' or compatible
+`arm_neon_ok'
+ ARM Target supports `-mfpu=neon -mfloat-abi=softfp' or compatible
options. Some multilibs may be incompatible with these options.
-'arm_neonv2_ok'
- ARM Target supports '-mfpu=neon-vfpv4 -mfloat-abi=softfp' or
+`arm_neonv2_ok'
+ ARM Target supports `-mfpu=neon-vfpv4 -mfloat-abi=softfp' or
compatible options. Some multilibs may be incompatible with these
options.
-'arm_neon_fp16_ok'
- ARM Target supports '-mfpu=neon-fp16 -mfloat-abi=softfp' or
+`arm_neon_fp16_ok'
+ ARM Target supports `-mfpu=neon-fp16 -mfloat-abi=softfp' or
compatible options. Some multilibs may be incompatible with these
options.
-'arm_thumb1_ok'
- ARM target generates Thumb-1 code for '-mthumb'.
+`arm_thumb1_ok'
+ ARM target generates Thumb-1 code for `-mthumb'.
-'arm_thumb2_ok'
- ARM target generates Thumb-2 code for '-mthumb'.
+`arm_thumb2_ok'
+ ARM target generates Thumb-2 code for `-mthumb'.
-'arm_vfp_ok'
- ARM target supports '-mfpu=vfp -mfloat-abi=softfp'. Some multilibs
- may be incompatible with these options.
-
-'arm_vfp3_ok'
- ARM target supports '-mfpu=vfp3 -mfloat-abi=softfp'. Some
+`arm_vfp_ok'
+ ARM target supports `-mfpu=vfp -mfloat-abi=softfp'. Some
multilibs may be incompatible with these options.
-'arm_v8_vfp_ok'
- ARM target supports '-mfpu=fp-armv8 -mfloat-abi=softfp'. Some
+`arm_vfp3_ok'
+ ARM target supports `-mfpu=vfp3 -mfloat-abi=softfp'. Some
multilibs may be incompatible with these options.
-'arm_v8_neon_ok'
- ARM target supports '-mfpu=neon-fp-armv8 -mfloat-abi=softfp'. Some
+`arm_v8_vfp_ok'
+ ARM target supports `-mfpu=fp-armv8 -mfloat-abi=softfp'. Some
multilibs may be incompatible with these options.
-'arm_prefer_ldrd_strd'
- ARM target prefers 'LDRD' and 'STRD' instructions over 'LDM' and
- 'STM' instructions.
+`arm_v8_neon_ok'
+ ARM target supports `-mfpu=neon-fp-armv8 -mfloat-abi=softfp'.
+ Some multilibs may be incompatible with these options.
+
+`arm_prefer_ldrd_strd'
+ ARM target prefers `LDRD' and `STRD' instructions over `LDM' and
+ `STM' instructions.
+
7.2.3.7 MIPS-specific attributes
................................
-'mips64'
+`mips64'
MIPS target supports 64-bit instructions.
-'nomips16'
+`nomips16'
MIPS target does not produce MIPS16 code.
-'mips16_attribute'
+`mips16_attribute'
MIPS target can generate MIPS16 code.
-'mips_loongson'
+`mips_loongson'
MIPS target is a Loongson-2E or -2F target using an ABI that
supports the Loongson vector modes.
-'mips_newabi_large_long_double'
- MIPS target supports 'long double' larger than 'double' when using
+`mips_newabi_large_long_double'
+ MIPS target supports `long double' larger than `double' when using
the new ABI.
-'mpaired_single'
- MIPS target supports '-mpaired-single'.
+`mpaired_single'
+ MIPS target supports `-mpaired-single'.
7.2.3.8 PowerPC-specific attributes
...................................
-'dfp_hw'
+`dfp_hw'
PowerPC target supports executing hardware DFP instructions.
-'p8vector_hw'
+`p8vector_hw'
PowerPC target supports executing VSX instructions (ISA 2.07).
-'powerpc64'
+`powerpc64'
Test system supports executing 64-bit instructions.
-'powerpc_altivec'
+`powerpc_altivec'
PowerPC target supports AltiVec.
-'powerpc_altivec_ok'
- PowerPC target supports '-maltivec'.
+`powerpc_altivec_ok'
+ PowerPC target supports `-maltivec'.
-'powerpc_eabi_ok'
- PowerPC target supports '-meabi'.
+`powerpc_eabi_ok'
+ PowerPC target supports `-meabi'.
-'powerpc_elfv2'
- PowerPC target supports '-mabi=elfv2'.
+`powerpc_elfv2'
+ PowerPC target supports `-mabi=elfv2'.
-'powerpc_fprs'
+`powerpc_fprs'
PowerPC target supports floating-point registers.
-'powerpc_hard_double'
+`powerpc_hard_double'
PowerPC target supports hardware double-precision floating-point.
-'powerpc_htm_ok'
- PowerPC target supports '-mhtm'
+`powerpc_htm_ok'
+ PowerPC target supports `-mhtm'
-'powerpc_p8vector_ok'
- PowerPC target supports '-mpower8-vector'
+`powerpc_p8vector_ok'
+ PowerPC target supports `-mpower8-vector'
-'powerpc_ppu_ok'
- PowerPC target supports '-mcpu=cell'.
+`powerpc_ppu_ok'
+ PowerPC target supports `-mcpu=cell'.
-'powerpc_spe'
+`powerpc_spe'
PowerPC target supports PowerPC SPE.
-'powerpc_spe_nocache'
+`powerpc_spe_nocache'
Including the options used to compile this particular test, the
PowerPC target supports PowerPC SPE.
-'powerpc_spu'
+`powerpc_spu'
PowerPC target supports PowerPC SPU.
-'powerpc_vsx_ok'
- PowerPC target supports '-mvsx'.
+`powerpc_vsx_ok'
+ PowerPC target supports `-mvsx'.
-'powerpc_405_nocache'
+`powerpc_405_nocache'
Including the options used to compile this particular test, the
PowerPC target supports PowerPC 405.
-'ppc_recip_hw'
+`ppc_recip_hw'
PowerPC target supports executing reciprocal estimate instructions.
-'spu_auto_overlay'
+`spu_auto_overlay'
SPU target has toolchain that supports automatic overlay
generation.
-'vmx_hw'
+`vmx_hw'
PowerPC target supports executing AltiVec instructions.
-'vsx_hw'
+`vsx_hw'
PowerPC target supports executing VSX instructions (ISA 2.06).
7.2.3.9 Other hardware attributes
.................................
-'avx'
- Target supports compiling 'avx' instructions.
+`avx'
+ Target supports compiling `avx' instructions.
-'avx_runtime'
- Target supports the execution of 'avx' instructions.
+`avx_runtime'
+ Target supports the execution of `avx' instructions.
-'cell_hw'
+`cell_hw'
Test system can execute AltiVec and Cell PPU instructions.
-'coldfire_fpu'
+`coldfire_fpu'
Target uses a ColdFire FPU.
-'hard_float'
+`hard_float'
Target supports FPU instructions.
-'non_strict_align'
+`non_strict_align'
Target does not require strict alignment.
-'sse'
- Target supports compiling 'sse' instructions.
+`sse'
+ Target supports compiling `sse' instructions.
-'sse_runtime'
- Target supports the execution of 'sse' instructions.
+`sse_runtime'
+ Target supports the execution of `sse' instructions.
-'sse2'
- Target supports compiling 'sse2' instructions.
+`sse2'
+ Target supports compiling `sse2' instructions.
-'sse2_runtime'
- Target supports the execution of 'sse2' instructions.
+`sse2_runtime'
+ Target supports the execution of `sse2' instructions.
-'sync_char_short'
- Target supports atomic operations on 'char' and 'short'.
+`sync_char_short'
+ Target supports atomic operations on `char' and `short'.
-'sync_int_long'
- Target supports atomic operations on 'int' and 'long'.
+`sync_int_long'
+ Target supports atomic operations on `int' and `long'.
-'ultrasparc_hw'
+`ultrasparc_hw'
Test environment appears to run executables on a simulator that
- accepts only 'EM_SPARC' executables and chokes on 'EM_SPARC32PLUS'
- or 'EM_SPARCV9' executables.
+ accepts only `EM_SPARC' executables and chokes on `EM_SPARC32PLUS'
+ or `EM_SPARCV9' executables.
-'vect_cmdline_needed'
+`vect_cmdline_needed'
Target requires a command line argument to enable a SIMD
instruction set.
-'pie_copyreloc'
+`pie_copyreloc'
The x86-64 target linker supports PIE with copy reloc.
7.2.3.10 Environment attributes
...............................
-'c'
+`c'
The language for the compiler under test is C.
-'c++'
+`c++'
The language for the compiler under test is C++.
-'c99_runtime'
+`c99_runtime'
Target provides a full C99 runtime.
-'correct_iso_cpp_string_wchar_protos'
- Target 'string.h' and 'wchar.h' headers provide C++ required
- overloads for 'strchr' etc. functions.
+`correct_iso_cpp_string_wchar_protos'
+ Target `string.h' and `wchar.h' headers provide C++ required
+ overloads for `strchr' etc. functions.
-'dummy_wcsftime'
- Target uses a dummy 'wcsftime' function that always returns zero.
+`dummy_wcsftime'
+ Target uses a dummy `wcsftime' function that always returns zero.
-'fd_truncate'
+`fd_truncate'
Target can truncate a file from a file descriptor, as used by
- 'libgfortran/io/unix.c:fd_truncate'; i.e. 'ftruncate' or 'chsize'.
+ `libgfortran/io/unix.c:fd_truncate'; i.e. `ftruncate' or `chsize'.
-'freestanding'
- Target is 'freestanding' as defined in section 4 of the C99
+`freestanding'
+ Target is `freestanding' as defined in section 4 of the C99
standard. Effectively, it is a target which supports no extra
headers or libraries other than what is considered essential.
-'init_priority'
+`init_priority'
Target supports constructors with initialization priority
arguments.
-'inttypes_types'
- Target has the basic signed and unsigned types in 'inttypes.h'.
+`inttypes_types'
+ Target has the basic signed and unsigned types in `inttypes.h'.
This is for tests that GCC's notions of these types agree with
- those in the header, as some systems have only 'inttypes.h'.
+ those in the header, as some systems have only `inttypes.h'.
-'lax_strtofp'
+`lax_strtofp'
Target might have errors of a few ULP in string to floating-point
conversion functions and overflow is not always detected correctly
by those functions.
-'mempcpy'
- Target provides 'mempcpy' function.
+`mempcpy'
+ Target provides `mempcpy' function.
-'mmap'
- Target supports 'mmap'.
+`mmap'
+ Target supports `mmap'.
-'newlib'
+`newlib'
Target supports Newlib.
-'pow10'
- Target provides 'pow10' function.
+`pow10'
+ Target provides `pow10' function.
-'pthread'
- Target can compile using 'pthread.h' with no errors or warnings.
+`pthread'
+ Target can compile using `pthread.h' with no errors or warnings.
-'pthread_h'
- Target has 'pthread.h'.
+`pthread_h'
+ Target has `pthread.h'.
-'run_expensive_tests'
+`run_expensive_tests'
Expensive testcases (usually those that consume excessive amounts
of CPU time) should be run on this target. This can be enabled by
- setting the 'GCC_TEST_RUN_EXPENSIVE' environment variable to a
+ setting the `GCC_TEST_RUN_EXPENSIVE' environment variable to a
non-empty string.
-'simulator'
- Test system runs executables on a simulator (i.e. slowly) rather
- than hardware (i.e. fast).
+`simulator'
+ Test system runs executables on a simulator (i.e. slowly) rather
+ than hardware (i.e. fast).
-'stdint_types'
- Target has the basic signed and unsigned C types in 'stdint.h'.
- This will be obsolete when GCC ensures a working 'stdint.h' for all
- targets.
+`stdint_types'
+ Target has the basic signed and unsigned C types in `stdint.h'.
+ This will be obsolete when GCC ensures a working `stdint.h' for
+ all targets.
-'stpcpy'
- Target provides 'stpcpy' function.
+`stpcpy'
+ Target provides `stpcpy' function.
-'trampolines'
+`trampolines'
Target supports trampolines.
-'uclibc'
+`uclibc'
Target supports uClibc.
-'unwrapped'
+`unwrapped'
Target does not use a status wrapper.
-'vxworks_kernel'
+`vxworks_kernel'
Target is a VxWorks kernel.
-'vxworks_rtp'
+`vxworks_rtp'
Target is a VxWorks RTP.
-'wchar'
+`wchar'
Target supports wide characters.
7.2.3.11 Other attributes
.........................
-'automatic_stack_alignment'
+`automatic_stack_alignment'
Target supports automatic stack alignment.
-'cxa_atexit'
- Target uses '__cxa_atexit'.
+`cxa_atexit'
+ Target uses `__cxa_atexit'.
-'default_packed'
+`default_packed'
Target has packed layout of structure members by default.
-'fgraphite'
+`fgraphite'
Target supports Graphite optimizations.
-'fixed_point'
+`fixed_point'
Target supports fixed-point extension to C.
-'fopenacc'
- Target supports OpenACC via '-fopenacc'.
+`fopenacc'
+ Target supports OpenACC via `-fopenacc'.
-'fopenmp'
- Target supports OpenMP via '-fopenmp'.
+`fopenmp'
+ Target supports OpenMP via `-fopenmp'.
-'fpic'
- Target supports '-fpic' and '-fPIC'.
+`fpic'
+ Target supports `-fpic' and `-fPIC'.
-'freorder'
- Target supports '-freorder-blocks-and-partition'.
+`freorder'
+ Target supports `-freorder-blocks-and-partition'.
-'fstack_protector'
- Target supports '-fstack-protector'.
+`fstack_protector'
+ Target supports `-fstack-protector'.
-'gas'
- Target uses GNU 'as'.
+`gas'
+ Target uses GNU `as'.
-'gc_sections'
- Target supports '--gc-sections'.
+`gc_sections'
+ Target supports `--gc-sections'.
-'gld'
- Target uses GNU 'ld'.
+`gld'
+ Target uses GNU `ld'.
-'keeps_null_pointer_checks'
+`keeps_null_pointer_checks'
Target keeps null pointer checks, either due to the use of
- '-fno-delete-null-pointer-checks' or hardwired into the target.
+ `-fno-delete-null-pointer-checks' or hardwired into the target.
-'lto'
+`lto'
Compiler has been configured to support link-time optimization
(LTO).
-'naked_functions'
- Target supports the 'naked' function attribute.
+`naked_functions'
+ Target supports the `naked' function attribute.
-'named_sections'
+`named_sections'
Target supports named sections.
-'natural_alignment_32'
+`natural_alignment_32'
Target uses natural alignment (aligned to type size) for types of
32 bits or less.
-'target_natural_alignment_64'
+`target_natural_alignment_64'
Target uses natural alignment (aligned to type size) for types of
64 bits or less.
-'nonpic'
+`nonpic'
Target does not generate PIC by default.
-'pie_enabled'
+`pie_enabled'
Target generates PIE by default.
-'pcc_bitfield_type_matters'
- Target defines 'PCC_BITFIELD_TYPE_MATTERS'.
+`pcc_bitfield_type_matters'
+ Target defines `PCC_BITFIELD_TYPE_MATTERS'.
-'pe_aligned_commons'
- Target supports '-mpe-aligned-commons'.
+`pe_aligned_commons'
+ Target supports `-mpe-aligned-commons'.
-'pie'
- Target supports '-pie', '-fpie' and '-fPIE'.
+`pie'
+ Target supports `-pie', `-fpie' and `-fPIE'.
-'section_anchors'
+`section_anchors'
Target supports section anchors.
-'short_enums'
+`short_enums'
Target defaults to short enums.
-'static'
- Target supports '-static'.
+`static'
+ Target supports `-static'.
-'static_libgfortran'
- Target supports statically linking 'libgfortran'.
+`static_libgfortran'
+ Target supports statically linking `libgfortran'.
-'string_merging'
+`string_merging'
Target supports merging string constants at link time.
-'ucn'
+`ucn'
Target supports compiling and assembling UCN.
-'ucn_nocache'
+`ucn_nocache'
Including the options used to compile this particular test, the
target supports compiling and assembling UCN.
-'unaligned_stack'
- Target does not guarantee that its 'STACK_BOUNDARY' is greater than
+`unaligned_stack'
+ Target does not guarantee that its `STACK_BOUNDARY' is greater than
or equal to the required vector alignment.
-'vector_alignment_reachable'
+`vector_alignment_reachable'
Vector alignment is reachable for types of 32 bits or less.
-'vector_alignment_reachable_for_64bit'
+`vector_alignment_reachable_for_64bit'
Vector alignment is reachable for types of 64 bits or less.
-'wchar_t_char16_t_compatible'
- Target supports 'wchar_t' that is compatible with 'char16_t'.
+`wchar_t_char16_t_compatible'
+ Target supports `wchar_t' that is compatible with `char16_t'.
-'wchar_t_char32_t_compatible'
- Target supports 'wchar_t' that is compatible with 'char32_t'.
+`wchar_t_char32_t_compatible'
+ Target supports `wchar_t' that is compatible with `char32_t'.
-'comdat_group'
+`comdat_group'
Target uses comdat groups.
-7.2.3.12 Local to tests in 'gcc.target/i386'
+7.2.3.12 Local to tests in `gcc.target/i386'
............................................
-'3dnow'
- Target supports compiling '3dnow' instructions.
+`3dnow'
+ Target supports compiling `3dnow' instructions.
-'aes'
- Target supports compiling 'aes' instructions.
+`aes'
+ Target supports compiling `aes' instructions.
-'fma4'
- Target supports compiling 'fma4' instructions.
+`fma4'
+ Target supports compiling `fma4' instructions.
-'ms_hook_prologue'
- Target supports attribute 'ms_hook_prologue'.
+`ms_hook_prologue'
+ Target supports attribute `ms_hook_prologue'.
-'pclmul'
- Target supports compiling 'pclmul' instructions.
+`pclmul'
+ Target supports compiling `pclmul' instructions.
-'sse3'
- Target supports compiling 'sse3' instructions.
+`sse3'
+ Target supports compiling `sse3' instructions.
-'sse4'
- Target supports compiling 'sse4' instructions.
+`sse4'
+ Target supports compiling `sse4' instructions.
-'sse4a'
- Target supports compiling 'sse4a' instructions.
+`sse4a'
+ Target supports compiling `sse4a' instructions.
-'ssse3'
- Target supports compiling 'ssse3' instructions.
+`ssse3'
+ Target supports compiling `ssse3' instructions.
-'vaes'
- Target supports compiling 'vaes' instructions.
+`vaes'
+ Target supports compiling `vaes' instructions.
-'vpclmul'
- Target supports compiling 'vpclmul' instructions.
+`vpclmul'
+ Target supports compiling `vpclmul' instructions.
-'xop'
- Target supports compiling 'xop' instructions.
+`xop'
+ Target supports compiling `xop' instructions.
-7.2.3.13 Local to tests in 'gcc.target/spu/ea'
+7.2.3.13 Local to tests in `gcc.target/spu/ea'
..............................................
-'ealib'
- Target '__ea' library functions are available.
+`ealib'
+ Target `__ea' library functions are available.
-7.2.3.14 Local to tests in 'gcc.test-framework'
+7.2.3.14 Local to tests in `gcc.test-framework'
...............................................
-'no'
+`no'
Always returns 0.
-'yes'
+`yes'
Always returns 1.

File: gccint.info, Node: Add Options, Next: Require Support, Prev: Effective-Target Keywords, Up: Test Directives
-7.2.4 Features for 'dg-add-options'
+7.2.4 Features for `dg-add-options'
-----------------------------------
-The supported values of FEATURE for directive 'dg-add-options' are:
+The supported values of FEATURE for directive `dg-add-options' are:
-'arm_neon'
+`arm_neon'
NEON support. Only ARM targets support this feature, and only then
in certain modes; see the *note arm_neon_ok effective target
keyword: arm_neon_ok.
-'arm_neon_fp16'
+`arm_neon_fp16'
NEON and half-precision floating point support. Only ARM targets
- support this feature, and only then in certain modes; see the *note
- arm_neon_fp16_ok effective target keyword: arm_neon_ok.
+ support this feature, and only then in certain modes; see the
+ *note arm_neon_fp16_ok effective target keyword: arm_neon_ok.
-'arm_vfp3'
+`arm_vfp3'
arm vfp3 floating point support; see the *note arm_vfp3_ok
effective target keyword: arm_vfp3_ok.
-'bind_pic_locally'
+`bind_pic_locally'
Add the target-specific flags needed to enable functions to bind
locally when using pic/PIC passes in the testsuite.
-'c99_runtime'
+`c99_runtime'
Add the target-specific flags needed to access the C99 runtime.
-'ieee'
- Add the target-specific flags needed to enable full IEEE compliance
- mode.
+`ieee'
+ Add the target-specific flags needed to enable full IEEE
+ compliance mode.
-'mips16_attribute'
- 'mips16' function attributes. Only MIPS targets support this
+`mips16_attribute'
+ `mips16' function attributes. Only MIPS targets support this
feature, and only then in certain modes.
-'tls'
+`tls'
Add the target-specific flags needed to use thread-local storage.

File: gccint.info, Node: Require Support, Next: Final Actions, Prev: Add Options, Up: Test Directives
-7.2.5 Variants of 'dg-require-SUPPORT'
+7.2.5 Variants of `dg-require-SUPPORT'
--------------------------------------
-A few of the 'dg-require' directives take arguments.
+A few of the `dg-require' directives take arguments.
-'dg-require-iconv CODESET'
- Skip the test if the target does not support iconv. CODESET is the
- codeset to convert to.
+`dg-require-iconv CODESET'
+ Skip the test if the target does not support iconv. CODESET is
+ the codeset to convert to.
-'dg-require-profiling PROFOPT'
+`dg-require-profiling PROFOPT'
Skip the test if the target does not support profiling with option
PROFOPT.
-'dg-require-visibility VIS'
- Skip the test if the target does not support the 'visibility'
- attribute. If VIS is '""', support for 'visibility("hidden")' is
- checked, for 'visibility("VIS")' otherwise.
+`dg-require-visibility VIS'
+ Skip the test if the target does not support the `visibility'
+ attribute. If VIS is `""', support for `visibility("hidden")' is
+ checked, for `visibility("VIS")' otherwise.
- The original 'dg-require' directives were defined before there was
+ The original `dg-require' directives were defined before there was
support for effective-target keywords. The directives that do not take
arguments could be replaced with effective-target keywords.
-'dg-require-alias ""'
- Skip the test if the target does not support the 'alias' attribute.
+`dg-require-alias ""'
+ Skip the test if the target does not support the `alias' attribute.
-'dg-require-ascii-locale ""'
+`dg-require-ascii-locale ""'
Skip the test if the host does not support an ASCII locale.
-'dg-require-compat-dfp ""'
- Skip this test unless both compilers in a 'compat' testsuite
+`dg-require-compat-dfp ""'
+ Skip this test unless both compilers in a `compat' testsuite
support decimal floating point.
-'dg-require-cxa-atexit ""'
- Skip the test if the target does not support '__cxa_atexit'. This
- is equivalent to 'dg-require-effective-target cxa_atexit'.
+`dg-require-cxa-atexit ""'
+ Skip the test if the target does not support `__cxa_atexit'. This
+ is equivalent to `dg-require-effective-target cxa_atexit'.
-'dg-require-dll ""'
+`dg-require-dll ""'
Skip the test if the target does not support DLL attributes.
-'dg-require-fork ""'
- Skip the test if the target does not support 'fork'.
+`dg-require-fork ""'
+ Skip the test if the target does not support `fork'.
-'dg-require-gc-sections ""'
+`dg-require-gc-sections ""'
Skip the test if the target's linker does not support the
- '--gc-sections' flags. This is equivalent to
- 'dg-require-effective-target gc-sections'.
+ `--gc-sections' flags. This is equivalent to
+ `dg-require-effective-target gc-sections'.
-'dg-require-host-local ""'
+`dg-require-host-local ""'
Skip the test if the host is remote, rather than the same as the
build system. Some tests are incompatible with DejaGnu's handling
- of remote hosts, which involves copying the source file to the host
- and compiling it with a relative path and "'-o a.out'".
+ of remote hosts, which involves copying the source file to the
+ host and compiling it with a relative path and "`-o a.out'".
-'dg-require-mkfifo ""'
- Skip the test if the target does not support 'mkfifo'.
+`dg-require-mkfifo ""'
+ Skip the test if the target does not support `mkfifo'.
-'dg-require-named-sections ""'
+`dg-require-named-sections ""'
Skip the test is the target does not support named sections. This
- is equivalent to 'dg-require-effective-target named_sections'.
+ is equivalent to `dg-require-effective-target named_sections'.
-'dg-require-weak ""'
+`dg-require-weak ""'
Skip the test if the target does not support weak symbols.
-'dg-require-weak-override ""'
+`dg-require-weak-override ""'
Skip the test if the target does not support overriding weak
symbols.

File: gccint.info, Node: Final Actions, Prev: Require Support, Up: Test Directives
-7.2.6 Commands for use in 'dg-final'
+7.2.6 Commands for use in `dg-final'
------------------------------------
The GCC testsuite defines the following directives to be used within
-'dg-final'.
+`dg-final'.
7.2.6.1 Scan a particular file
..............................
-'scan-file FILENAME REGEXP [{ target/xfail SELECTOR }]'
+`scan-file FILENAME REGEXP [{ target/xfail SELECTOR }]'
Passes if REGEXP matches text in FILENAME.
-'scan-file-not FILENAME REGEXP [{ target/xfail SELECTOR }]'
+
+`scan-file-not FILENAME REGEXP [{ target/xfail SELECTOR }]'
Passes if REGEXP does not match text in FILENAME.
-'scan-module MODULE REGEXP [{ target/xfail SELECTOR }]'
+
+`scan-module MODULE REGEXP [{ target/xfail SELECTOR }]'
Passes if REGEXP matches in Fortran module MODULE.
7.2.6.2 Scan the assembly output
................................
-'scan-assembler REGEX [{ target/xfail SELECTOR }]'
+`scan-assembler REGEX [{ target/xfail SELECTOR }]'
Passes if REGEX matches text in the test's assembler output.
-'scan-assembler-not REGEX [{ target/xfail SELECTOR }]'
+`scan-assembler-not REGEX [{ target/xfail SELECTOR }]'
Passes if REGEX does not match text in the test's assembler output.
-'scan-assembler-times REGEX NUM [{ target/xfail SELECTOR }]'
+`scan-assembler-times REGEX NUM [{ target/xfail SELECTOR }]'
Passes if REGEX is matched exactly NUM times in the test's
assembler output.
-'scan-assembler-dem REGEX [{ target/xfail SELECTOR }]'
+`scan-assembler-dem REGEX [{ target/xfail SELECTOR }]'
Passes if REGEX matches text in the test's demangled assembler
output.
-'scan-assembler-dem-not REGEX [{ target/xfail SELECTOR }]'
+`scan-assembler-dem-not REGEX [{ target/xfail SELECTOR }]'
Passes if REGEX does not match text in the test's demangled
assembler output.
-'scan-hidden SYMBOL [{ target/xfail SELECTOR }]'
+`scan-hidden SYMBOL [{ target/xfail SELECTOR }]'
Passes if SYMBOL is defined as a hidden symbol in the test's
assembly output.
-'scan-not-hidden SYMBOL [{ target/xfail SELECTOR }]'
+`scan-not-hidden SYMBOL [{ target/xfail SELECTOR }]'
Passes if SYMBOL is not defined as a hidden symbol in the test's
assembly output.
7.2.6.3 Scan optimization dump files
....................................
-These commands are available for KIND of 'tree', 'rtl', and 'ipa'.
+These commands are available for KIND of `tree', `rtl', and `ipa'.
-'scan-KIND-dump REGEX SUFFIX [{ target/xfail SELECTOR }]'
+`scan-KIND-dump REGEX SUFFIX [{ target/xfail SELECTOR }]'
Passes if REGEX matches text in the dump file with suffix SUFFIX.
-'scan-KIND-dump-not REGEX SUFFIX [{ target/xfail SELECTOR }]'
+`scan-KIND-dump-not REGEX SUFFIX [{ target/xfail SELECTOR }]'
Passes if REGEX does not match text in the dump file with suffix
SUFFIX.
-'scan-KIND-dump-times REGEX NUM SUFFIX [{ target/xfail SELECTOR }]'
+`scan-KIND-dump-times REGEX NUM SUFFIX [{ target/xfail SELECTOR }]'
Passes if REGEX is found exactly NUM times in the dump file with
suffix SUFFIX.
-'scan-KIND-dump-dem REGEX SUFFIX [{ target/xfail SELECTOR }]'
- Passes if REGEX matches demangled text in the dump file with suffix
- SUFFIX.
+`scan-KIND-dump-dem REGEX SUFFIX [{ target/xfail SELECTOR }]'
+ Passes if REGEX matches demangled text in the dump file with
+ suffix SUFFIX.
-'scan-KIND-dump-dem-not REGEX SUFFIX [{ target/xfail SELECTOR }]'
+`scan-KIND-dump-dem-not REGEX SUFFIX [{ target/xfail SELECTOR }]'
Passes if REGEX does not match demangled text in the dump file with
suffix SUFFIX.
7.2.6.4 Verify that an output files exists or not
.................................................
-'output-exists [{ target/xfail SELECTOR }]'
+`output-exists [{ target/xfail SELECTOR }]'
Passes if compiler output file exists.
-'output-exists-not [{ target/xfail SELECTOR }]'
+`output-exists-not [{ target/xfail SELECTOR }]'
Passes if compiler output file does not exist.
7.2.6.5 Check for LTO tests
...........................
-'scan-symbol REGEXP [{ target/xfail SELECTOR }]'
+`scan-symbol REGEXP [{ target/xfail SELECTOR }]'
Passes if the pattern is present in the final executable.
-7.2.6.6 Checks for 'gcov' tests
+7.2.6.6 Checks for `gcov' tests
...............................
-'run-gcov SOURCEFILE'
- Check line counts in 'gcov' tests.
+`run-gcov SOURCEFILE'
+ Check line counts in `gcov' tests.
-'run-gcov [branches] [calls] { OPTS SOURCEFILE }'
+`run-gcov [branches] [calls] { OPTS SOURCEFILE }'
Check branch and/or call counts, in addition to line counts, in
- 'gcov' tests.
+ `gcov' tests.
7.2.6.7 Clean up generated test files
.....................................
-'cleanup-coverage-files'
+`cleanup-coverage-files'
Removes coverage data files generated for this test.
-'cleanup-ipa-dump SUFFIX'
+`cleanup-ipa-dump SUFFIX'
Removes IPA dump files generated for this test.
-'cleanup-modules "LIST-OF-EXTRA-MODULES"'
+`cleanup-modules "LIST-OF-EXTRA-MODULES"'
Removes Fortran module files generated for this test, excluding the
module names listed in keep-modules. Cleaning up module files is
usually done automatically by the testsuite by looking at the
@@ -5463,7 +5569,7 @@ These commands are available for KIND of 'tree', 'rtl', and 'ipa'.
! { dg-final { cleanup-modules "mod1 mod2" } } ! redundant
! { dg-final { keep-modules "mod3 mod4" } }
-'keep-modules "LIST-OF-MODULES-NOT-TO-DELETE"'
+`keep-modules "LIST-OF-MODULES-NOT-TO-DELETE"'
Whitespace separated list of module names that should not be
deleted by cleanup-modules. If the list of modules is empty, all
modules defined in this file are kept.
@@ -5476,20 +5582,20 @@ These commands are available for KIND of 'tree', 'rtl', and 'ipa'.
! { dg-final { keep-modules "keep1 keep2" } } ! just keep these two
! { dg-final { keep-modules "" } } ! keep all
-'cleanup-profile-file'
+`cleanup-profile-file'
Removes profiling files generated for this test.
-'cleanup-repo-files'
- Removes files generated for this test for '-frepo'.
+`cleanup-repo-files'
+ Removes files generated for this test for `-frepo'.
-'cleanup-rtl-dump SUFFIX'
+`cleanup-rtl-dump SUFFIX'
Removes RTL dump files generated for this test.
-'cleanup-saved-temps'
+`cleanup-saved-temps'
Removes files for the current test which were kept for
- '-save-temps'.
+ `-save-temps'.
-'cleanup-tree-dump SUFFIX'
+`cleanup-tree-dump SUFFIX'
Removes tree dump files matching SUFFIX which were generated for
this test.
@@ -5500,32 +5606,32 @@ File: gccint.info, Node: Ada Tests, Next: C Tests, Prev: Test Directives, Up
===========================
The Ada testsuite includes executable tests from the ACATS testsuite,
-publicly available at <http://www.ada-auth.org/acats.html>.
+publicly available at `http://www.ada-auth.org/acats.html'.
- These tests are integrated in the GCC testsuite in the 'ada/acats'
-directory, and enabled automatically when running 'make check', assuming
+ These tests are integrated in the GCC testsuite in the `ada/acats'
+directory, and enabled automatically when running `make check', assuming
the Ada language has been enabled when configuring GCC.
- You can also run the Ada testsuite independently, using 'make
+ You can also run the Ada testsuite independently, using `make
check-ada', or run a subset of the tests by specifying which chapter to
run, e.g.:
$ make check-ada CHAPTERS="c3 c9"
- The tests are organized by directory, each directory corresponding to a
-chapter of the Ada Reference Manual. So for example, 'c9' corresponds
+ The tests are organized by directory, each directory corresponding to
+a chapter of the Ada Reference Manual. So for example, `c9' corresponds
to chapter 9, which deals with tasking features of the language.
- There is also an extra chapter called 'gcc' containing a template for
+ There is also an extra chapter called `gcc' containing a template for
creating new executable tests, although this is deprecated in favor of
-the 'gnat.dg' testsuite.
+the `gnat.dg' testsuite.
- The tests are run using two 'sh' scripts: 'run_acats' and 'run_all.sh'.
-To run the tests using a simulator or a cross target, see the small
-customization section at the top of 'run_all.sh'.
+ The tests are run using two `sh' scripts: `run_acats' and
+`run_all.sh'. To run the tests using a simulator or a cross target,
+see the small customization section at the top of `run_all.sh'.
These tests are run using the build tree: they can be run without doing
-a 'make install'.
+a `make install'.

File: gccint.info, Node: C Tests, Next: libgcj Tests, Prev: Ada Tests, Up: Testsuites
@@ -5533,101 +5639,116 @@ File: gccint.info, Node: C Tests, Next: libgcj Tests, Prev: Ada Tests, Up: T
7.4 C Language Testsuites
=========================
-GCC contains the following C language testsuites, in the 'gcc/testsuite'
-directory:
+GCC contains the following C language testsuites, in the
+`gcc/testsuite' directory:
-'gcc.dg'
- This contains tests of particular features of the C compiler, using
- the more modern 'dg' harness. Correctness tests for various
+`gcc.dg'
+ This contains tests of particular features of the C compiler,
+ using the more modern `dg' harness. Correctness tests for various
compiler features should go here if possible.
Magic comments determine whether the file is preprocessed,
- compiled, linked or run. In these tests, error and warning message
- texts are compared against expected texts or regular expressions
- given in comments. These tests are run with the options '-ansi
- -pedantic' unless other options are given in the test. Except as
- noted below they are not run with multiple optimization options.
-'gcc.dg/compat'
+ compiled, linked or run. In these tests, error and warning
+ message texts are compared against expected texts or regular
+ expressions given in comments. These tests are run with the
+ options `-ansi -pedantic' unless other options are given in the
+ test. Except as noted below they are not run with multiple
+ optimization options.
+
+`gcc.dg/compat'
This subdirectory contains tests for binary compatibility using
- 'lib/compat.exp', which in turn uses the language-independent
+ `lib/compat.exp', which in turn uses the language-independent
support (*note Support for testing binary compatibility: compat
Testing.).
-'gcc.dg/cpp'
+
+`gcc.dg/cpp'
This subdirectory contains tests of the preprocessor.
-'gcc.dg/debug'
+
+`gcc.dg/debug'
This subdirectory contains tests for debug formats. Tests in this
subdirectory are run for each debug format that the compiler
supports.
-'gcc.dg/format'
- This subdirectory contains tests of the '-Wformat' format checking.
- Tests in this directory are run with and without '-DWIDE'.
-'gcc.dg/noncompile'
+
+`gcc.dg/format'
+ This subdirectory contains tests of the `-Wformat' format
+ checking. Tests in this directory are run with and without
+ `-DWIDE'.
+
+`gcc.dg/noncompile'
This subdirectory contains tests of code that should not compile
and does not need any special compilation options. They are run
with multiple optimization options, since sometimes invalid code
crashes the compiler with optimization.
-'gcc.dg/special'
+
+`gcc.dg/special'
FIXME: describe this.
-'gcc.c-torture'
+`gcc.c-torture'
This contains particular code fragments which have historically
broken easily. These tests are run with multiple optimization
options, so tests for features which only break at some
- optimization levels belong here. This also contains tests to check
- that certain optimizations occur. It might be worthwhile to
- separate the correctness tests cleanly from the code quality tests,
- but it hasn't been done yet.
+ optimization levels belong here. This also contains tests to
+ check that certain optimizations occur. It might be worthwhile to
+ separate the correctness tests cleanly from the code quality
+ tests, but it hasn't been done yet.
-'gcc.c-torture/compat'
+`gcc.c-torture/compat'
FIXME: describe this.
This directory should probably not be used for new tests.
-'gcc.c-torture/compile'
+
+`gcc.c-torture/compile'
This testsuite contains test cases that should compile, but do not
need to link or run. These test cases are compiled with several
different combinations of optimization options. All warnings are
disabled for these test cases, so this directory is not suitable if
you wish to test for the presence or absence of compiler warnings.
While special options can be set, and tests disabled on specific
- platforms, by the use of '.x' files, mostly these test cases should
- not contain platform dependencies. FIXME: discuss how defines such
- as 'NO_LABEL_VALUES' and 'STACK_SIZE' are used.
-'gcc.c-torture/execute'
+ platforms, by the use of `.x' files, mostly these test cases
+ should not contain platform dependencies. FIXME: discuss how
+ defines such as `NO_LABEL_VALUES' and `STACK_SIZE' are used.
+
+`gcc.c-torture/execute'
This testsuite contains test cases that should compile, link and
- run; otherwise the same comments as for 'gcc.c-torture/compile'
+ run; otherwise the same comments as for `gcc.c-torture/compile'
apply.
-'gcc.c-torture/execute/ieee'
+
+`gcc.c-torture/execute/ieee'
This contains tests which are specific to IEEE floating point.
-'gcc.c-torture/unsorted'
+
+`gcc.c-torture/unsorted'
FIXME: describe this.
This directory should probably not be used for new tests.
-'gcc.misc-tests'
+
+`gcc.misc-tests'
This directory contains C tests that require special handling.
Some of these tests have individual expect files, and others share
special-purpose expect files:
- 'bprob*.c'
- Test '-fbranch-probabilities' using
- 'gcc.misc-tests/bprob.exp', which in turn uses the generic,
+ ``bprob*.c''
+ Test `-fbranch-probabilities' using
+ `gcc.misc-tests/bprob.exp', which in turn uses the generic,
language-independent framework (*note Support for testing
profile-directed optimizations: profopt Testing.).
- 'gcov*.c'
- Test 'gcov' output using 'gcov.exp', which in turn uses the
+ ``gcov*.c''
+ Test `gcov' output using `gcov.exp', which in turn uses the
language-independent support (*note Support for testing gcov:
gcov Testing.).
- 'i386-pf-*.c'
+ ``i386-pf-*.c''
Test i386-specific support for data prefetch using
- 'i386-prefetch.exp'.
+ `i386-prefetch.exp'.
-'gcc.test-framework'
- 'dg-*.c'
+`gcc.test-framework'
+
+ ``dg-*.c''
Test the testsuite itself using
- 'gcc.test-framework/test-framework.exp'.
+ `gcc.test-framework/test-framework.exp'.
+
- FIXME: merge in 'testsuite/README.gcc' and discuss the format of test
+ FIXME: merge in `testsuite/README.gcc' and discuss the format of test
cases and magic comments more.

@@ -5636,20 +5757,20 @@ File: gccint.info, Node: libgcj Tests, Next: LTO Testing, Prev: C Tests, Up:
7.5 The Java library testsuites.
================================
-Runtime tests are executed via 'make check' in the
-'TARGET/libjava/testsuite' directory in the build tree. Additional
+Runtime tests are executed via `make check' in the
+`TARGET/libjava/testsuite' directory in the build tree. Additional
runtime tests can be checked into this testsuite.
Regression testing of the core packages in libgcj is also covered by
the Mauve testsuite. The Mauve Project develops tests for the Java
Class Libraries. These tests are run as part of libgcj testing by
placing the Mauve tree within the libjava testsuite sources at
-'libjava/testsuite/libjava.mauve/mauve', or by specifying the location
-of that tree when invoking 'make', as in 'make MAUVEDIR=~/mauve check'.
+`libjava/testsuite/libjava.mauve/mauve', or by specifying the location
+of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'.
- To detect regressions, a mechanism in 'mauve.exp' compares the failures
-for a test run against the list of expected failures in
-'libjava/testsuite/libjava.mauve/xfails' from the source hierarchy.
+ To detect regressions, a mechanism in `mauve.exp' compares the
+failures for a test run against the list of expected failures in
+`libjava/testsuite/libjava.mauve/xfails' from the source hierarchy.
Update this file when adding new failing tests to Mauve, or when fixing
bugs in libgcj that had caused Mauve test failures.
@@ -5665,78 +5786,80 @@ Tests for link-time optimizations usually require multiple source files
that are compiled separately, perhaps with different sets of options.
There are several special-purpose test directives used for these tests.
-'{ dg-lto-do DO-WHAT-KEYWORD }'
+`{ dg-lto-do DO-WHAT-KEYWORD }'
DO-WHAT-KEYWORD specifies how the test is compiled and whether it
is executed. It is one of:
- 'assemble'
- Compile with '-c' to produce a relocatable object file.
- 'link'
+ `assemble'
+ Compile with `-c' to produce a relocatable object file.
+
+ `link'
Compile, assemble, and link to produce an executable file.
- 'run'
+
+ `run'
Produce and run an executable file, which is expected to
return an exit code of 0.
- The default is 'assemble'. That can be overridden for a set of
- tests by redefining 'dg-do-what-default' within the '.exp' file for
- those tests.
+ The default is `assemble'. That can be overridden for a set of
+ tests by redefining `dg-do-what-default' within the `.exp' file
+ for those tests.
- Unlike 'dg-do', 'dg-lto-do' does not support an optional 'target'
- or 'xfail' list. Use 'dg-skip-if', 'dg-xfail-if', or
- 'dg-xfail-run-if'.
+ Unlike `dg-do', `dg-lto-do' does not support an optional `target'
+ or `xfail' list. Use `dg-skip-if', `dg-xfail-if', or
+ `dg-xfail-run-if'.
-'{ dg-lto-options { { OPTIONS } [{ OPTIONS }] } [{ target SELECTOR }]}'
+`{ dg-lto-options { { OPTIONS } [{ OPTIONS }] } [{ target SELECTOR }]}'
This directive provides a list of one or more sets of compiler
options to override LTO_OPTIONS. Each test will be compiled and
run with each of these sets of options.
-'{ dg-extra-ld-options OPTIONS [{ target SELECTOR }]}'
+`{ dg-extra-ld-options OPTIONS [{ target SELECTOR }]}'
This directive adds OPTIONS to the linker options used.
-'{ dg-suppress-ld-options OPTIONS [{ target SELECTOR }]}'
+`{ dg-suppress-ld-options OPTIONS [{ target SELECTOR }]}'
This directive removes OPTIONS from the set of linker options used.

File: gccint.info, Node: gcov Testing, Next: profopt Testing, Prev: LTO Testing, Up: Testsuites
-7.7 Support for testing 'gcov'
+7.7 Support for testing `gcov'
==============================
-Language-independent support for testing 'gcov', and for checking that
+Language-independent support for testing `gcov', and for checking that
branch profiling produces expected values, is provided by the expect
-file 'lib/gcov.exp'. 'gcov' tests also rely on procedures in
-'lib/gcc-dg.exp' to compile and run the test program. A typical 'gcov'
+file `lib/gcov.exp'. `gcov' tests also rely on procedures in
+`lib/gcc-dg.exp' to compile and run the test program. A typical `gcov'
test contains the following DejaGnu commands within comments:
{ dg-options "-fprofile-arcs -ftest-coverage" }
{ dg-do run { target native } }
{ dg-final { run-gcov sourcefile } }
- Checks of 'gcov' output can include line counts, branch percentages,
+ Checks of `gcov' output can include line counts, branch percentages,
and call return percentages. All of these checks are requested via
-commands that appear in comments in the test's source file. Commands to
-check line counts are processed by default. Commands to check branch
-percentages and call return percentages are processed if the 'run-gcov'
-command has arguments 'branches' or 'calls', respectively. For example,
-the following specifies checking both, as well as passing '-b' to
-'gcov':
+commands that appear in comments in the test's source file. Commands
+to check line counts are processed by default. Commands to check
+branch percentages and call return percentages are processed if the
+`run-gcov' command has arguments `branches' or `calls', respectively.
+For example, the following specifies checking both, as well as passing
+`-b' to `gcov':
{ dg-final { run-gcov branches calls { -b sourcefile } } }
A line count command appears within a comment on the source line that
-is expected to get the specified count and has the form 'count(CNT)'. A
-test should only check line counts for lines that will get the same
+is expected to get the specified count and has the form `count(CNT)'.
+A test should only check line counts for lines that will get the same
count for any architecture.
- Commands to check branch percentages ('branch') and call return
-percentages ('returns') are very similar to each other. A beginning
+ Commands to check branch percentages (`branch') and call return
+percentages (`returns') are very similar to each other. A beginning
command appears on or before the first of a range of lines that will
report the percentage, and the ending command follows that range of
lines. The beginning command can include a list of percentages, all of
which are expected to be found within the range. A range is terminated
-by the next command of the same kind. A command 'branch(end)' or
-'returns(end)' marks the end of a range without starting a new one. For
-example:
+by the next command of the same kind. A command `branch(end)' or
+`returns(end)' marks the end of a range without starting a new one.
+For example:
if (i > 10 && j > i && j < 20) /* branch(27 50 75) */
/* branch(end) */
@@ -5747,10 +5870,10 @@ calls reported to return. For a branch percentage, the value is either
the expected percentage or 100 minus that value, since the direction of
a branch can differ depending on the target or the optimization level.
- Not all branches and calls need to be checked. A test should not check
-for branches that might be optimized away or replaced with predicated
-instructions. Don't check for calls inserted by the compiler or ones
-that might be inlined or optimized away.
+ Not all branches and calls need to be checked. A test should not
+check for branches that might be optimized away or replaced with
+predicated instructions. Don't check for calls inserted by the
+compiler or ones that might be inlined or optimized away.
A single test can check for combinations of line counts, branch
percentages, and call return percentages. The command to check a line
@@ -5764,44 +5887,44 @@ File: gccint.info, Node: profopt Testing, Next: compat Testing, Prev: gcov Te
7.8 Support for testing profile-directed optimizations
======================================================
-The file 'profopt.exp' provides language-independent support for
+The file `profopt.exp' provides language-independent support for
checking correct execution of a test built with profile-directed
optimization. This testing requires that a test program be built and
-executed twice. The first time it is compiled to generate profile data,
-and the second time it is compiled to use the data that was generated
-during the first execution. The second execution is to verify that the
-test produces the expected results.
+executed twice. The first time it is compiled to generate profile
+data, and the second time it is compiled to use the data that was
+generated during the first execution. The second execution is to
+verify that the test produces the expected results.
To check that the optimization actually generated better code, a test
can be built and run a third time with normal optimizations to verify
that the performance is better with the profile-directed optimizations.
-'profopt.exp' has the beginnings of this kind of support.
+`profopt.exp' has the beginnings of this kind of support.
- 'profopt.exp' provides generic support for profile-directed
+ `profopt.exp' provides generic support for profile-directed
optimizations. Each set of tests that uses it provides information
about a specific optimization:
-'tool'
- tool being tested, e.g., 'gcc'
+`tool'
+ tool being tested, e.g., `gcc'
-'profile_option'
+`profile_option'
options used to generate profile data
-'feedback_option'
+`feedback_option'
options used to optimize using that profile data
-'prof_ext'
+`prof_ext'
suffix of profile data files
-'PROFOPT_OPTIONS'
+`PROFOPT_OPTIONS'
list of options with which to run each test, similar to the lists
for torture tests
-'{ dg-final-generate { LOCAL-DIRECTIVE } }'
- This directive is similar to 'dg-final', but the LOCAL-DIRECTIVE is
- run after the generation of profile data.
+`{ dg-final-generate { LOCAL-DIRECTIVE } }'
+ This directive is similar to `dg-final', but the LOCAL-DIRECTIVE
+ is run after the generation of profile data.
-'{ dg-final-use { LOCAL-DIRECTIVE } }'
+`{ dg-final-use { LOCAL-DIRECTIVE } }'
The LOCAL-DIRECTIVE is run after the profile data have been used.

@@ -5810,25 +5933,25 @@ File: gccint.info, Node: compat Testing, Next: Torture Tests, Prev: profopt T
7.9 Support for testing binary compatibility
============================================
-The file 'compat.exp' provides language-independent support for binary
+The file `compat.exp' provides language-independent support for binary
compatibility testing. It supports testing interoperability of two
compilers that follow the same ABI, or of multiple sets of compiler
options that should not affect binary compatibility. It is intended to
be used for testsuites that complement ABI testsuites.
A test supported by this framework has three parts, each in a separate
-source file: a main program and two pieces that interact with each other
-to split up the functionality being tested.
+source file: a main program and two pieces that interact with each
+other to split up the functionality being tested.
-'TESTNAME_main.SUFFIX'
+`TESTNAME_main.SUFFIX'
Contains the main program, which calls a function in file
- 'TESTNAME_x.SUFFIX'.
+ `TESTNAME_x.SUFFIX'.
-'TESTNAME_x.SUFFIX'
- Contains at least one call to a function in 'TESTNAME_y.SUFFIX'.
+`TESTNAME_x.SUFFIX'
+ Contains at least one call to a function in `TESTNAME_y.SUFFIX'.
-'TESTNAME_y.SUFFIX'
- Shares data with, or gets arguments from, 'TESTNAME_x.SUFFIX'.
+`TESTNAME_y.SUFFIX'
+ Shares data with, or gets arguments from, `TESTNAME_x.SUFFIX'.
Within each test, the main program and one functional piece are
compiled by the GCC under test. The other piece can be compiled by an
@@ -5839,33 +5962,33 @@ pair specifies options used with the GCC under test, and the second
element of the pair specifies options used with the alternate compiler.
Each test is compiled with each pair of options.
- 'compat.exp' defines default pairs of compiler options. These can be
-overridden by defining the environment variable 'COMPAT_OPTIONS' as:
+ `compat.exp' defines default pairs of compiler options. These can be
+overridden by defining the environment variable `COMPAT_OPTIONS' as:
COMPAT_OPTIONS="[list [list {TST1} {ALT1}]
...[list {TSTN} {ALTN}]]"
where TSTI and ALTI are lists of options, with TSTI used by the
compiler under test and ALTI used by the alternate compiler. For
-example, with '[list [list {-g -O0} {-O3}] [list {-fpic} {-fPIC -O2}]]',
-the test is first built with '-g -O0' by the compiler under test and
-with '-O3' by the alternate compiler. The test is built a second time
-using '-fpic' by the compiler under test and '-fPIC -O2' by the
+example, with `[list [list {-g -O0} {-O3}] [list {-fpic} {-fPIC -O2}]]',
+the test is first built with `-g -O0' by the compiler under test and
+with `-O3' by the alternate compiler. The test is built a second time
+using `-fpic' by the compiler under test and `-fPIC -O2' by the
alternate compiler.
An alternate compiler is specified by defining an environment variable
to be the full pathname of an installed compiler; for C define
-'ALT_CC_UNDER_TEST', and for C++ define 'ALT_CXX_UNDER_TEST'. These
-will be written to the 'site.exp' file used by DejaGnu. The default is
+`ALT_CC_UNDER_TEST', and for C++ define `ALT_CXX_UNDER_TEST'. These
+will be written to the `site.exp' file used by DejaGnu. The default is
to build each test with the compiler under test using the first of each
-pair of compiler options from 'COMPAT_OPTIONS'. When
-'ALT_CC_UNDER_TEST' or 'ALT_CXX_UNDER_TEST' is 'same', each test is
-built using the compiler under test but with combinations of the options
-from 'COMPAT_OPTIONS'.
+pair of compiler options from `COMPAT_OPTIONS'. When
+`ALT_CC_UNDER_TEST' or `ALT_CXX_UNDER_TEST' is `same', each test is
+built using the compiler under test but with combinations of the
+options from `COMPAT_OPTIONS'.
To run only the C++ compatibility suite using the compiler under test
and another version of GCC using specific compiler options, do the
-following from 'OBJDIR/gcc':
+following from `OBJDIR/gcc':
rm site.exp
make -k \
@@ -5884,17 +6007,17 @@ compiler under test but is present in the alternate compiler.
The binary compatibility tests support a small number of test framework
commands that appear within comments in a test file.
-'dg-require-*'
- These commands can be used in 'TESTNAME_main.SUFFIX' to skip the
+`dg-require-*'
+ These commands can be used in `TESTNAME_main.SUFFIX' to skip the
test if specific support is not available on the target.
-'dg-options'
+`dg-options'
The specified options are used for compiling this particular source
- file, appended to the options from 'COMPAT_OPTIONS'. When this
- command appears in 'TESTNAME_main.SUFFIX' the options are also used
- to link the test program.
+ file, appended to the options from `COMPAT_OPTIONS'. When this
+ command appears in `TESTNAME_main.SUFFIX' the options are also
+ used to link the test program.
-'dg-xfail-if'
+`dg-xfail-if'
This command can be used in a secondary source file to specify that
compilation is expected to fail for particular options on
particular targets.
@@ -5907,36 +6030,38 @@ File: gccint.info, Node: Torture Tests, Prev: compat Testing, Up: Testsuites
Throughout the compiler testsuite there are several directories whose
tests are run multiple times, each with a different set of options.
-These are known as torture tests. 'lib/torture-options.exp' defines
+These are known as torture tests. `lib/torture-options.exp' defines
procedures to set up these lists:
-'torture-init'
+`torture-init'
Initialize use of torture lists.
-'set-torture-options'
+
+`set-torture-options'
Set lists of torture options to use for tests with and without
loops. Optionally combine a set of torture options with a set of
other options, as is done with Objective-C runtime options.
-'torture-finish'
+
+`torture-finish'
Finalize use of torture lists.
- The '.exp' file for a set of tests that use torture options must
+ The `.exp' file for a set of tests that use torture options must
include calls to these three procedures if:
- * It calls 'gcc-dg-runtest' and overrides DG_TORTURE_OPTIONS.
+ * It calls `gcc-dg-runtest' and overrides DG_TORTURE_OPTIONS.
- * It calls ${TOOL}'-torture' or ${TOOL}'-torture-execute', where TOOL
- is 'c', 'fortran', or 'objc'.
+ * It calls ${TOOL}`-torture' or ${TOOL}`-torture-execute', where
+ TOOL is `c', `fortran', or `objc'.
- * It calls 'dg-pch'.
+ * It calls `dg-pch'.
- It is not necessary for a '.exp' file that calls 'gcc-dg-runtest' to
+ It is not necessary for a `.exp' file that calls `gcc-dg-runtest' to
call the torture procedures if the tests should use the list in
-DG_TORTURE_OPTIONS defined in 'gcc-dg.exp'.
+DG_TORTURE_OPTIONS defined in `gcc-dg.exp'.
Most uses of torture options can override the default lists by defining
TORTURE_OPTIONS or add to the default list by defining
-ADDITIONAL_TORTURE_OPTIONS. Define these in a '.dejagnurc' file or add
-them to the 'site.exp' file; for example
+ADDITIONAL_TORTURE_OPTIONS. Define these in a `.dejagnurc' file or add
+them to the `site.exp' file; for example
set ADDITIONAL_TORTURE_OPTIONS [list \
{ -O2 -ftree-loop-linear } \
@@ -5948,9 +6073,9 @@ File: gccint.info, Node: Options, Next: Passes, Prev: Testsuites, Up: Top
8 Option specification files
****************************
-Most GCC command-line options are described by special option definition
-files, the names of which conventionally end in '.opt'. This chapter
-describes the format of these files.
+Most GCC command-line options are described by special option
+definition files, the names of which conventionally end in `.opt'.
+This chapter describes the format of these files.
* Menu:
@@ -5972,126 +6097,129 @@ semicolon.
The files can contain the following types of record:
* A language definition record. These records have two fields: the
- string 'Language' and the name of the language. Once a language
+ string `Language' and the name of the language. Once a language
has been declared in this way, it can be used as an option
property. *Note Option properties::.
- * A target specific save record to save additional information.
- These records have two fields: the string 'TargetSave', and a
- declaration type to go in the 'cl_target_option' structure.
+ * A target specific save record to save additional information. These
+ records have two fields: the string `TargetSave', and a
+ declaration type to go in the `cl_target_option' structure.
* A variable record to define a variable used to store option
- information. These records have two fields: the string 'Variable',
- and a declaration of the type and name of the variable, optionally
- with an initializer (but without any trailing ';'). These records
- may be used for variables used for many options where declaring the
- initializer in a single option definition record, or duplicating it
- in many records, would be inappropriate, or for variables set in
- option handlers rather than referenced by 'Var' properties.
+ information. These records have two fields: the string
+ `Variable', and a declaration of the type and name of the
+ variable, optionally with an initializer (but without any trailing
+ `;'). These records may be used for variables used for many
+ options where declaring the initializer in a single option
+ definition record, or duplicating it in many records, would be
+ inappropriate, or for variables set in option handlers rather than
+ referenced by `Var' properties.
* A variable record to define a variable used to store option
information. These records have two fields: the string
- 'TargetVariable', and a declaration of the type and name of the
+ `TargetVariable', and a declaration of the type and name of the
variable, optionally with an initializer (but without any trailing
- ';'). 'TargetVariable' is a combination of 'Variable' and
- 'TargetSave' records in that the variable is defined in the
- 'gcc_options' structure, but these variables are also stored in the
- 'cl_target_option' structure. The variables are saved in the
+ `;'). `TargetVariable' is a combination of `Variable' and
+ `TargetSave' records in that the variable is defined in the
+ `gcc_options' structure, but these variables are also stored in
+ the `cl_target_option' structure. The variables are saved in the
target save code and restored in the target restore code.
* A variable record to record any additional files that the
- 'options.h' file should include. This is useful to provide
+ `options.h' file should include. This is useful to provide
enumeration or structure definitions needed for target variables.
- These records have two fields: the string 'HeaderInclude' and the
+ These records have two fields: the string `HeaderInclude' and the
name of the include file.
* A variable record to record any additional files that the
- 'options.c' or 'options-save.c' file should include. This is
+ `options.c' or `options-save.c' file should include. This is
useful to provide inline functions needed for target variables
- and/or '#ifdef' sequences to properly set up the initialization.
- These records have two fields: the string 'SourceInclude' and the
+ and/or `#ifdef' sequences to properly set up the initialization.
+ These records have two fields: the string `SourceInclude' and the
name of the include file.
* An enumeration record to define a set of strings that may be used
as arguments to an option or options. These records have three
- fields: the string 'Enum', a space-separated list of properties and
- help text used to describe the set of strings in '--help' output.
- Properties use the same format as option properties; the following
- are valid:
- 'Name(NAME)'
+ fields: the string `Enum', a space-separated list of properties
+ and help text used to describe the set of strings in `--help'
+ output. Properties use the same format as option properties; the
+ following are valid:
+ `Name(NAME)'
This property is required; NAME must be a name (suitable for
use in C identifiers) used to identify the set of strings in
- 'Enum' option properties.
+ `Enum' option properties.
- 'Type(TYPE)'
+ `Type(TYPE)'
This property is required; TYPE is the C type for variables
- set by options using this enumeration together with 'Var'.
+ set by options using this enumeration together with `Var'.
- 'UnknownError(MESSAGE)'
+ `UnknownError(MESSAGE)'
The message MESSAGE will be used as an error message if the
- argument is invalid; for enumerations without 'UnknownError',
+ argument is invalid; for enumerations without `UnknownError',
a generic error message is used. MESSAGE should contain a
- single '%qs' format, which will be used to format the invalid
+ single `%qs' format, which will be used to format the invalid
argument.
* An enumeration value record to define one of the strings in a set
- given in an 'Enum' record. These records have two fields: the
- string 'EnumValue' and a space-separated list of properties.
+ given in an `Enum' record. These records have two fields: the
+ string `EnumValue' and a space-separated list of properties.
Properties use the same format as option properties; the following
are valid:
- 'Enum(NAME)'
- This property is required; NAME says which 'Enum' record this
- 'EnumValue' record corresponds to.
+ `Enum(NAME)'
+ This property is required; NAME says which `Enum' record this
+ `EnumValue' record corresponds to.
- 'String(STRING)'
+ `String(STRING)'
This property is required; STRING is the string option
argument being described by this record.
- 'Value(VALUE)'
+ `Value(VALUE)'
This property is required; it says what value (representable
- as 'int') should be used for the given string.
+ as `int') should be used for the given string.
- 'Canonical'
+ `Canonical'
This property is optional. If present, it says the present
string is the canonical one among all those with the given
value. Other strings yielding that value will be mapped to
this one so specs do not need to handle them.
- 'DriverOnly'
+ `DriverOnly'
This property is optional. If present, the present string
will only be accepted by the driver. This is used for cases
- such as '-march=native' that are processed by the driver so
- that 'gcc -v' shows how the options chosen depended on the
+ such as `-march=native' that are processed by the driver so
+ that `gcc -v' shows how the options chosen depended on the
system on which the compiler was run.
* An option definition record. These records have the following
fields:
1. the name of the option, with the leading "-" removed
+
2. a space-separated list of option properties (*note Option
properties::)
- 3. the help text to use for '--help' (omitted if the second field
- contains the 'Undocumented' property).
+
+ 3. the help text to use for `--help' (omitted if the second field
+ contains the `Undocumented' property).
By default, all options beginning with "f", "W" or "m" are
implicitly assumed to take a "no-" form. This form should not be
listed separately. If an option beginning with one of these
letters does not have a "no-" form, you can use the
- 'RejectNegative' property to reject it.
+ `RejectNegative' property to reject it.
The help text is automatically line-wrapped before being displayed.
Normally the name of the option is printed on the left-hand side of
the output and the help text is printed on the right. However, if
- the help text contains a tab character, the text to the left of the
- tab is used instead of the option's name and the text to the right
- of the tab forms the help text. This allows you to elaborate on
- what type of argument the option takes.
+ the help text contains a tab character, the text to the left of
+ the tab is used instead of the option's name and the text to the
+ right of the tab forms the help text. This allows you to
+ elaborate on what type of argument the option takes.
* A target mask record. These records have one field of the form
- 'Mask(X)'. The options-processing script will automatically
- allocate a bit in 'target_flags' (*note Run-time Target::) for each
- mask name X and set the macro 'MASK_X' to the appropriate bitmask.
- It will also declare a 'TARGET_X' macro that has the value 1 when
- bit 'MASK_X' is set and 0 otherwise.
+ `Mask(X)'. The options-processing script will automatically
+ allocate a bit in `target_flags' (*note Run-time Target::) for
+ each mask name X and set the macro `MASK_X' to the appropriate
+ bitmask. It will also declare a `TARGET_X' macro that has the
+ value 1 when bit `MASK_X' is set and 0 otherwise.
They are primarily intended to declare target masks that are not
associated with user options, either because these masks represent
@@ -6106,306 +6234,309 @@ File: gccint.info, Node: Option properties, Prev: Option file format, Up: Opt
The second field of an option record can specify any of the following
properties. When an option takes an argument, it is enclosed in
-parentheses following the option property name. The parser that handles
-option files is quite simplistic, and will be tricked by any nested
-parentheses within the argument text itself; in this case, the entire
-option argument can be wrapped in curly braces within the parentheses to
-demarcate it, e.g.:
+parentheses following the option property name. The parser that
+handles option files is quite simplistic, and will be tricked by any
+nested parentheses within the argument text itself; in this case, the
+entire option argument can be wrapped in curly braces within the
+parentheses to demarcate it, e.g.:
Condition({defined (USE_CYGWIN_LIBSTDCXX_WRAPPERS)})
-'Common'
+`Common'
The option is available for all languages and targets.
-'Target'
+`Target'
The option is available for all languages but is target-specific.
-'Driver'
+`Driver'
The option is handled by the compiler driver using code not shared
- with the compilers proper ('cc1' etc.).
+ with the compilers proper (`cc1' etc.).
-'LANGUAGE'
+`LANGUAGE'
The option is available when compiling for the given language.
It is possible to specify several different languages for the same
option. Each LANGUAGE must have been declared by an earlier
- 'Language' record. *Note Option file format::.
+ `Language' record. *Note Option file format::.
-'RejectDriver'
- The option is only handled by the compilers proper ('cc1' etc.) and
- should not be accepted by the driver.
+`RejectDriver'
+ The option is only handled by the compilers proper (`cc1' etc.)
+ and should not be accepted by the driver.
-'RejectNegative'
+`RejectNegative'
The option does not have a "no-" form. All options beginning with
"f", "W" or "m" are assumed to have a "no-" form unless this
property is used.
-'Negative(OTHERNAME)'
+`Negative(OTHERNAME)'
The option will turn off another option OTHERNAME, which is the
option name with the leading "-" removed. This chain action will
- propagate through the 'Negative' property of the option to be
+ propagate through the `Negative' property of the option to be
turned off.
As a consequence, if you have a group of mutually-exclusive
- options, their 'Negative' properties should form a circular chain.
- For example, if options '-A', '-B' and '-C' are mutually exclusive,
- their respective 'Negative' properties should be 'Negative(B)',
- 'Negative(C)' and 'Negative(A)'.
-
-'Joined'
-'Separate'
- The option takes a mandatory argument. 'Joined' indicates that the
- option and argument can be included in the same 'argv' entry (as
- with '-mflush-func=NAME', for example). 'Separate' indicates that
- the option and argument can be separate 'argv' entries (as with
- '-o'). An option is allowed to have both of these properties.
-
-'JoinedOrMissing'
+ options, their `Negative' properties should form a circular chain.
+ For example, if options `-A', `-B' and `-C' are mutually
+ exclusive, their respective `Negative' properties should be
+ `Negative(B)', `Negative(C)' and `Negative(A)'.
+
+`Joined'
+`Separate'
+ The option takes a mandatory argument. `Joined' indicates that
+ the option and argument can be included in the same `argv' entry
+ (as with `-mflush-func=NAME', for example). `Separate' indicates
+ that the option and argument can be separate `argv' entries (as
+ with `-o'). An option is allowed to have both of these properties.
+
+`JoinedOrMissing'
The option takes an optional argument. If the argument is given,
- it will be part of the same 'argv' entry as the option itself.
+ it will be part of the same `argv' entry as the option itself.
- This property cannot be used alongside 'Joined' or 'Separate'.
+ This property cannot be used alongside `Joined' or `Separate'.
-'MissingArgError(MESSAGE)'
- For an option marked 'Joined' or 'Separate', the message MESSAGE
+`MissingArgError(MESSAGE)'
+ For an option marked `Joined' or `Separate', the message MESSAGE
will be used as an error message if the mandatory argument is
- missing; for options without 'MissingArgError', a generic error
- message is used. MESSAGE should contain a single '%qs' format,
+ missing; for options without `MissingArgError', a generic error
+ message is used. MESSAGE should contain a single `%qs' format,
which will be used to format the name of the option passed.
-'Args(N)'
- For an option marked 'Separate', indicate that it takes N
+`Args(N)'
+ For an option marked `Separate', indicate that it takes N
arguments. The default is 1.
-'UInteger'
+`UInteger'
The option's argument is a non-negative integer. The option parser
will check and convert the argument before passing it to the
- relevant option handler. 'UInteger' should also be used on options
- like '-falign-loops' where both '-falign-loops' and
- '-falign-loops'=N are supported to make sure the saved options are
+ relevant option handler. `UInteger' should also be used on
+ options like `-falign-loops' where both `-falign-loops' and
+ `-falign-loops'=N are supported to make sure the saved options are
given a full integer.
-'ToLower'
+`ToLower'
The option's argument should be converted to lowercase as part of
putting it in canonical form, and before comparing with the strings
- indicated by any 'Enum' property.
+ indicated by any `Enum' property.
-'NoDriverArg'
- For an option marked 'Separate', the option only takes an argument
+`NoDriverArg'
+ For an option marked `Separate', the option only takes an argument
in the compiler proper, not in the driver. This is for
compatibility with existing options that are used both directly and
- via '-Wp,'; new options should not have this property.
+ via `-Wp,'; new options should not have this property.
-'Var(VAR)'
- The state of this option should be stored in variable VAR (actually
- a macro for 'global_options.x_VAR'). The way that the state is
- stored depends on the type of option:
+`Var(VAR)'
+ The state of this option should be stored in variable VAR
+ (actually a macro for `global_options.x_VAR'). The way that the
+ state is stored depends on the type of option:
- * If the option uses the 'Mask' or 'InverseMask' properties, VAR
- is the integer variable that contains the mask.
+ * If the option uses the `Mask' or `InverseMask' properties,
+ VAR is the integer variable that contains the mask.
* If the option is a normal on/off switch, VAR is an integer
variable that is nonzero when the option is enabled. The
options parser will set the variable to 1 when the positive
form of the option is used and 0 when the "no-" form is used.
- * If the option takes an argument and has the 'UInteger'
+ * If the option takes an argument and has the `UInteger'
property, VAR is an integer variable that stores the value of
the argument.
- * If the option takes an argument and has the 'Enum' property,
- VAR is a variable (type given in the 'Type' property of the
- 'Enum' record whose 'Name' property has the same argument as
- the 'Enum' property of this option) that stores the value of
+ * If the option takes an argument and has the `Enum' property,
+ VAR is a variable (type given in the `Type' property of the
+ `Enum' record whose `Name' property has the same argument as
+ the `Enum' property of this option) that stores the value of
the argument.
- * If the option has the 'Defer' property, VAR is a pointer to a
- 'VEC(cl_deferred_option,heap)' that stores the option for
- later processing. (VAR is declared with type 'void *' and
- needs to be cast to 'VEC(cl_deferred_option,heap)' before
+ * If the option has the `Defer' property, VAR is a pointer to a
+ `VEC(cl_deferred_option,heap)' that stores the option for
+ later processing. (VAR is declared with type `void *' and
+ needs to be cast to `VEC(cl_deferred_option,heap)' before
use.)
* Otherwise, if the option takes an argument, VAR is a pointer
to the argument string. The pointer will be null if the
argument is optional and wasn't given.
- The option-processing script will usually zero-initialize VAR. You
- can modify this behavior using 'Init'.
+ The option-processing script will usually zero-initialize VAR.
+ You can modify this behavior using `Init'.
-'Var(VAR, SET)'
+`Var(VAR, SET)'
The option controls an integer variable VAR and is active when VAR
equals SET. The option parser will set VAR to SET when the
- positive form of the option is used and '!SET' when the "no-" form
+ positive form of the option is used and `!SET' when the "no-" form
is used.
VAR is declared in the same way as for the single-argument form
described above.
-'Init(VALUE)'
- The variable specified by the 'Var' property should be statically
+`Init(VALUE)'
+ The variable specified by the `Var' property should be statically
initialized to VALUE. If more than one option using the same
- variable specifies 'Init', all must specify the same initializer.
+ variable specifies `Init', all must specify the same initializer.
-'Mask(NAME)'
- The option is associated with a bit in the 'target_flags' variable
+`Mask(NAME)'
+ The option is associated with a bit in the `target_flags' variable
(*note Run-time Target::) and is active when that bit is set. You
- may also specify 'Var' to select a variable other than
- 'target_flags'.
+ may also specify `Var' to select a variable other than
+ `target_flags'.
The options-processing script will automatically allocate a unique
- bit for the option. If the option is attached to 'target_flags',
- the script will set the macro 'MASK_NAME' to the appropriate
- bitmask. It will also declare a 'TARGET_NAME' macro that has the
+ bit for the option. If the option is attached to `target_flags',
+ the script will set the macro `MASK_NAME' to the appropriate
+ bitmask. It will also declare a `TARGET_NAME' macro that has the
value 1 when the option is active and 0 otherwise. If you use
- 'Var' to attach the option to a different variable, the bitmask
- macro with be called 'OPTION_MASK_NAME'.
+ `Var' to attach the option to a different variable, the bitmask
+ macro with be called `OPTION_MASK_NAME'.
-'InverseMask(OTHERNAME)'
-'InverseMask(OTHERNAME, THISNAME)'
+`InverseMask(OTHERNAME)'
+`InverseMask(OTHERNAME, THISNAME)'
The option is the inverse of another option that has the
- 'Mask(OTHERNAME)' property. If THISNAME is given, the
- options-processing script will declare a 'TARGET_THISNAME' macro
+ `Mask(OTHERNAME)' property. If THISNAME is given, the
+ options-processing script will declare a `TARGET_THISNAME' macro
that is 1 when the option is active and 0 otherwise.
-'Enum(NAME)'
+`Enum(NAME)'
The option's argument is a string from the set of strings
- associated with the corresponding 'Enum' record. The string is
+ associated with the corresponding `Enum' record. The string is
checked and converted to the integer specified in the corresponding
- 'EnumValue' record before being passed to option handlers.
+ `EnumValue' record before being passed to option handlers.
-'Defer'
- The option should be stored in a vector, specified with 'Var', for
+`Defer'
+ The option should be stored in a vector, specified with `Var', for
later processing.
-'Alias(OPT)'
-'Alias(OPT, ARG)'
-'Alias(OPT, POSARG, NEGARG)'
- The option is an alias for '-OPT' (or the negative form of that
- option, depending on 'NegativeAlias'). In the first form, any
- argument passed to the alias is considered to be passed to '-OPT',
- and '-OPT' is considered to be negated if the alias is used in
+`Alias(OPT)'
+`Alias(OPT, ARG)'
+`Alias(OPT, POSARG, NEGARG)'
+ The option is an alias for `-OPT' (or the negative form of that
+ option, depending on `NegativeAlias'). In the first form, any
+ argument passed to the alias is considered to be passed to `-OPT',
+ and `-OPT' is considered to be negated if the alias is used in
negated form. In the second form, the alias may not be negated or
have an argument, and POSARG is considered to be passed as an
- argument to '-OPT'. In the third form, the alias may not have an
+ argument to `-OPT'. In the third form, the alias may not have an
argument, if the alias is used in the positive form then POSARG is
- considered to be passed to '-OPT', and if the alias is used in the
- negative form then NEGARG is considered to be passed to '-OPT'.
+ considered to be passed to `-OPT', and if the alias is used in the
+ negative form then NEGARG is considered to be passed to `-OPT'.
- Aliases should not specify 'Var' or 'Mask' or 'UInteger'. Aliases
+ Aliases should not specify `Var' or `Mask' or `UInteger'. Aliases
should normally specify the same languages as the target of the
alias; the flags on the target will be used to determine any
- diagnostic for use of an option for the wrong language, while those
- on the alias will be used to identify what command-line text is the
- option and what text is any argument to that option.
+ diagnostic for use of an option for the wrong language, while
+ those on the alias will be used to identify what command-line text
+ is the option and what text is any argument to that option.
- When an 'Alias' definition is used for an option, driver specs do
- not need to handle it and no 'OPT_' enumeration value is defined
+ When an `Alias' definition is used for an option, driver specs do
+ not need to handle it and no `OPT_' enumeration value is defined
for it; only the canonical form of the option will be seen in those
places.
-'NegativeAlias'
- For an option marked with 'Alias(OPT)', the option is considered to
- be an alias for the positive form of '-OPT' if negated and for the
- negative form of '-OPT' if not negated. 'NegativeAlias' may not be
- used with the forms of 'Alias' taking more than one argument.
+`NegativeAlias'
+ For an option marked with `Alias(OPT)', the option is considered
+ to be an alias for the positive form of `-OPT' if negated and for
+ the negative form of `-OPT' if not negated. `NegativeAlias' may
+ not be used with the forms of `Alias' taking more than one
+ argument.
-'Ignore'
+`Ignore'
This option is ignored apart from printing any warning specified
- using 'Warn'. The option will not be seen by specs and no 'OPT_'
+ using `Warn'. The option will not be seen by specs and no `OPT_'
enumeration value is defined for it.
-'SeparateAlias'
- For an option marked with 'Joined', 'Separate' and 'Alias', the
+`SeparateAlias'
+ For an option marked with `Joined', `Separate' and `Alias', the
option only acts as an alias when passed a separate argument; with
- a joined argument it acts as a normal option, with an 'OPT_'
- enumeration value. This is for compatibility with the Java '-d'
+ a joined argument it acts as a normal option, with an `OPT_'
+ enumeration value. This is for compatibility with the Java `-d'
option and should not be used for new options.
-'Warn(MESSAGE)'
+`Warn(MESSAGE)'
If this option is used, output the warning MESSAGE. MESSAGE is a
- format string, either taking a single operand with a '%qs' format
+ format string, either taking a single operand with a `%qs' format
which is the option name, or not taking any operands, which is
- passed to the 'warning' function. If an alias is marked 'Warn',
- the target of the alias must not also be marked 'Warn'.
+ passed to the `warning' function. If an alias is marked `Warn',
+ the target of the alias must not also be marked `Warn'.
-'Report'
- The state of the option should be printed by '-fverbose-asm'.
+`Report'
+ The state of the option should be printed by `-fverbose-asm'.
-'Warning'
- This is a warning option and should be shown as such in '--help'
+`Warning'
+ This is a warning option and should be shown as such in `--help'
output. This flag does not currently affect anything other than
- '--help'.
+ `--help'.
-'Optimization'
+`Optimization'
This is an optimization option. It should be shown as such in
- '--help' output, and any associated variable named using 'Var'
- should be saved and restored when the optimization level is changed
- with 'optimize' attributes.
+ `--help' output, and any associated variable named using `Var'
+ should be saved and restored when the optimization level is
+ changed with `optimize' attributes.
-'Undocumented'
+`Undocumented'
The option is deliberately missing documentation and should not be
- included in the '--help' output.
+ included in the `--help' output.
-'Condition(COND)'
+`Condition(COND)'
The option should only be accepted if preprocessor condition COND
is true. Note that any C declarations associated with the option
- will be present even if COND is false; COND simply controls whether
- the option is accepted and whether it is printed in the '--help'
- output.
+ will be present even if COND is false; COND simply controls
+ whether the option is accepted and whether it is printed in the
+ `--help' output.
-'Save'
- Build the 'cl_target_option' structure to hold a copy of the
- option, add the functions 'cl_target_option_save' and
- 'cl_target_option_restore' to save and restore the options.
+`Save'
+ Build the `cl_target_option' structure to hold a copy of the
+ option, add the functions `cl_target_option_save' and
+ `cl_target_option_restore' to save and restore the options.
-'SetByCombined'
+`SetByCombined'
The option may also be set by a combined option such as
- '-ffast-math'. This causes the 'gcc_options' struct to have a
- field 'frontend_set_NAME', where 'NAME' is the name of the field
- holding the value of this option (without the leading 'x_'). This
+ `-ffast-math'. This causes the `gcc_options' struct to have a
+ field `frontend_set_NAME', where `NAME' is the name of the field
+ holding the value of this option (without the leading `x_'). This
gives the front end a way to indicate that the value has been set
explicitly and should not be changed by the combined option. For
- example, some front ends use this to prevent '-ffast-math' and
- '-fno-fast-math' from changing the value of '-fmath-errno' for
- languages that do not use 'errno'.
-
-'EnabledBy(OPT)'
-'EnabledBy(OPT || OPT2)'
-'EnabledBy(OPT && OPT2)'
- If not explicitly set, the option is set to the value of '-OPT';
- multiple options can be given, separated by '||'. The third form
- using '&&' specifies that the option is only set if both OPT and
+ example, some front ends use this to prevent `-ffast-math' and
+ `-fno-fast-math' from changing the value of `-fmath-errno' for
+ languages that do not use `errno'.
+
+`EnabledBy(OPT)'
+`EnabledBy(OPT || OPT2)'
+`EnabledBy(OPT && OPT2)'
+ If not explicitly set, the option is set to the value of `-OPT';
+ multiple options can be given, separated by `||'. The third form
+ using `&&' specifies that the option is only set if both OPT and
OPT2 are set.
-'LangEnabledBy(LANGUAGE, OPT)'
-'LangEnabledBy(LANGUAGE, OPT, POSARG, NEGARG)'
+`LangEnabledBy(LANGUAGE, OPT)'
+`LangEnabledBy(LANGUAGE, OPT, POSARG, NEGARG)'
When compiling for the given language, the option is set to the
- value of '-OPT', if not explicitly set. OPT can be also a list of
- '||' separated options. In the second form, if OPT is used in the
- positive form then POSARG is considered to be passed to the option,
- and if OPT is used in the negative form then NEGARG is considered
- to be passed to the option. It is possible to specify several
- different languages. Each LANGUAGE must have been declared by an
- earlier 'Language' record. *Note Option file format::.
-
-'NoDWARFRecord'
+ value of `-OPT', if not explicitly set. OPT can be also a list of
+ `||' separated options. In the second form, if OPT is used in the
+ positive form then POSARG is considered to be passed to the
+ option, and if OPT is used in the negative form then NEGARG is
+ considered to be passed to the option. It is possible to specify
+ several different languages. Each LANGUAGE must have been
+ declared by an earlier `Language' record. *Note Option file
+ format::.
+
+`NoDWARFRecord'
The option is omitted from the producer string written by
- '-grecord-gcc-switches'.
+ `-grecord-gcc-switches'.
-'PchIgnore'
- Even if this is a target option, this option will not be recorded /
- compared to determine if a precompiled header file matches.
+`PchIgnore'
+ Even if this is a target option, this option will not be recorded
+ / compared to determine if a precompiled header file matches.
-'CPP(VAR)'
+`CPP(VAR)'
The state of this option should be kept in sync with the
preprocessor option VAR. If this property is set, then properties
- 'Var' and 'Init' must be set as well.
+ `Var' and `Init' must be set as well.
-'CppReason(CPP_W_ENUM)'
- This warning option corresponds to 'cpplib.h' warning reason code
+`CppReason(CPP_W_ENUM)'
+ This warning option corresponds to `cpplib.h' warning reason code
CPP_W_ENUM. This should only be used for warning options of the
C-family front-ends.
+

File: gccint.info, Node: Passes, Next: GENERIC, Prev: Options, Up: Top
@@ -6434,38 +6565,39 @@ File: gccint.info, Node: Parsing pass, Next: Cilk Plus Transformation, Up: Pa
================
The language front end is invoked only once, via
-'lang_hooks.parse_file', to parse the entire input. The language front
-end may use any intermediate language representation deemed appropriate.
-The C front end uses GENERIC trees (*note GENERIC::), plus a double
-handful of language specific tree codes defined in 'c-common.def'. The
-Fortran front end uses a completely different private representation.
+`lang_hooks.parse_file', to parse the entire input. The language front
+end may use any intermediate language representation deemed
+appropriate. The C front end uses GENERIC trees (*note GENERIC::), plus
+a double handful of language specific tree codes defined in
+`c-common.def'. The Fortran front end uses a completely different
+private representation.
At some point the front end must translate the representation used in
the front end to a representation understood by the language-independent
-portions of the compiler. Current practice takes one of two forms. The
-C front end manually invokes the gimplifier (*note GIMPLE::) on each
-function, and uses the gimplifier callbacks to convert the
+portions of the compiler. Current practice takes one of two forms.
+The C front end manually invokes the gimplifier (*note GIMPLE::) on
+each function, and uses the gimplifier callbacks to convert the
language-specific tree nodes directly to GIMPLE before passing the
function off to be compiled. The Fortran front end converts from a
-private representation to GENERIC, which is later lowered to GIMPLE when
-the function is compiled. Which route to choose probably depends on how
-well GENERIC (plus extensions) can be made to match up with the source
-language and necessary parsing data structures.
+private representation to GENERIC, which is later lowered to GIMPLE
+when the function is compiled. Which route to choose probably depends
+on how well GENERIC (plus extensions) can be made to match up with the
+source language and necessary parsing data structures.
BUG: Gimplification must occur before nested function lowering, and
nested function lowering must be done by the front end before passing
the data off to cgraph.
- TODO: Cgraph should control nested function lowering. It would only be
-invoked when it is certain that the outer-most function is used.
+ TODO: Cgraph should control nested function lowering. It would only
+be invoked when it is certain that the outer-most function is used.
TODO: Cgraph needs a gimplify_function callback. It should be invoked
when (1) it is certain that the function is used, (2) warning flags
specified by the user require some amount of compilation in order to
-honor, (3) the language indicates that semantic analysis is not complete
-until gimplification occurs. Hum... this sounds overly complicated.
-Perhaps we should just have the front end gimplify always; in most cases
-it's only one function call.
+honor, (3) the language indicates that semantic analysis is not
+complete until gimplification occurs. Hum... this sounds overly
+complicated. Perhaps we should just have the front end gimplify
+always; in most cases it's only one function call.
The front end needs to pass all function definitions and top level
declarations off to the middle-end so that they can be compiled and
@@ -6480,16 +6612,17 @@ all be passed as well.
In any case, the front end needs each complete top-level function or
data declaration, and each data definition should be passed to
-'rest_of_decl_compilation'. Each complete type definition should be
-passed to 'rest_of_type_compilation'. Each function definition should
-be passed to 'cgraph_finalize_function'.
+`rest_of_decl_compilation'. Each complete type definition should be
+passed to `rest_of_type_compilation'. Each function definition should
+be passed to `cgraph_finalize_function'.
TODO: I know rest_of_compilation currently has all sorts of RTL
generation semantics. I plan to move all code generation bits (both
-Tree and RTL) to compile_function. Should we hide cgraph from the front
-ends and move back to rest_of_compilation as the official interface?
-Possibly we should rename all three interfaces such that the names match
-in some meaningful way and that is more descriptive than "rest_of".
+Tree and RTL) to compile_function. Should we hide cgraph from the
+front ends and move back to rest_of_compilation as the official
+interface? Possibly we should rename all three interfaces such that
+the names match in some meaningful way and that is more descriptive
+than "rest_of".
The middle-end will, at its option, emit the function and data
definitions immediately or queue them for later processing.
@@ -6500,59 +6633,60 @@ File: gccint.info, Node: Cilk Plus Transformation, Next: Gimplification pass,
9.2 Cilk Plus Transformation
============================
-If Cilk Plus generation (flag '-fcilkplus') is enabled, all the Cilk
+If Cilk Plus generation (flag `-fcilkplus') is enabled, all the Cilk
Plus code is transformed into equivalent C and C++ functions. Majority
of this transformation occurs toward the end of the parsing and right
before the gimplification pass.
These are the major components to the Cilk Plus language extension:
* Array Notations: During parsing phase, all the array notation
- specific information is stored in 'ARRAY_NOTATION_REF' tree using
- the function 'c_parser_array_notation'. During the end of parsing,
- we check the entire function to see if there are any array notation
- specific code (using the function 'contains_array_notation_expr').
- If this function returns true, then we expand them using either
- 'expand_array_notation_exprs' or 'build_array_notation_expr'. For
- the cases where array notations are inside conditions, they are
- transformed using the function 'fix_conditional_array_notations'.
- The C language-specific routines are located in
- 'c/c-array-notation.c' and the equivalent C++ routines are in the
- file 'cp/cp-array-notation.c'. Common routines such as functions
- to initialize built-in functions are stored in
- 'array-notation-common.c'.
+ specific information is stored in `ARRAY_NOTATION_REF' tree using
+ the function `c_parser_array_notation'. During the end of
+ parsing, we check the entire function to see if there are any
+ array notation specific code (using the function
+ `contains_array_notation_expr'). If this function returns true,
+ then we expand them using either `expand_array_notation_exprs' or
+ `build_array_notation_expr'. For the cases where array notations
+ are inside conditions, they are transformed using the function
+ `fix_conditional_array_notations'. The C language-specific
+ routines are located in `c/c-array-notation.c' and the equivalent
+ C++ routines are in the file `cp/cp-array-notation.c'. Common
+ routines such as functions to initialize built-in functions are
+ stored in `array-notation-common.c'.
* Cilk keywords:
- * '_Cilk_spawn': The '_Cilk_spawn' keyword is parsed and the
+ * `_Cilk_spawn': The `_Cilk_spawn' keyword is parsed and the
function it contains is marked as a spawning function. The
spawning function is called the spawner. At the end of the
- parsing phase, appropriate built-in functions are added to the
- spawner that are defined in the Cilk runtime. The appropriate
- locations of these functions, and the internal structures are
- detailed in 'cilk_init_builtins' in the file 'cilk-common.c'.
- The pointers to Cilk functions and fields of internal
- structures are described in 'cilk.h'. The built-in functions
- are described in 'cilk-builtins.def'.
+ parsing phase, appropriate built-in functions are added to
+ the spawner that are defined in the Cilk runtime. The
+ appropriate locations of these functions, and the internal
+ structures are detailed in `cilk_init_builtins' in the file
+ `cilk-common.c'. The pointers to Cilk functions and fields
+ of internal structures are described in `cilk.h'. The
+ built-in functions are described in `cilk-builtins.def'.
During gimplification, a new "spawn-helper" function is
- created. The spawned function is replaced with a spawn helper
- function in the spawner. The spawned function-call is moved
- into the spawn helper. The main function that does these
- transformations is 'gimplify_cilk_spawn' in 'c-family/cilk.c'.
- In the spawn-helper, the gimplification function
- 'gimplify_call_expr', inserts a function call
- '__cilkrts_detach'. This function is expanded by
- 'builtin_expand_cilk_detach' located in 'c-family/cilk.c'.
-
- * '_Cilk_sync': '_Cilk_sync' is parsed like a keyword. During
- gimplification, the function 'gimplify_cilk_sync' in
- 'c-family/cilk.c', will replace this keyword with a set of
+ created. The spawned function is replaced with a spawn
+ helper function in the spawner. The spawned function-call is
+ moved into the spawn helper. The main function that does
+ these transformations is `gimplify_cilk_spawn' in
+ `c-family/cilk.c'. In the spawn-helper, the gimplification
+ function `gimplify_call_expr', inserts a function call
+ `__cilkrts_detach'. This function is expanded by
+ `builtin_expand_cilk_detach' located in `c-family/cilk.c'.
+
+ * `_Cilk_sync': `_Cilk_sync' is parsed like a keyword. During
+ gimplification, the function `gimplify_cilk_sync' in
+ `c-family/cilk.c', will replace this keyword with a set of
functions that are stored in the Cilk runtime. One of the
internal functions inserted during gimplification,
- '__cilkrts_pop_frame' must be expanded by the compiler and is
- done by 'builtin_expand_cilk_pop_frame' in 'cilk-common.c'.
+ `__cilkrts_pop_frame' must be expanded by the compiler and is
+ done by `builtin_expand_cilk_pop_frame' in `cilk-common.c'.
+
Documentation about Cilk Plus and language specification is provided
-under the "Learn" section in <http://www.cilkplus.org/>. It is worth
+under the "Learn" section in `http://www.cilkplus.org/'. It is worth
mentioning that the current implementation follows ABI 1.1.

@@ -6573,23 +6707,23 @@ intermediate language used by the front end is already fairly simple.
Usually it is easier to generate GENERIC trees plus extensions and let
the language-independent gimplifier do most of the work.
- The main entry point to this pass is 'gimplify_function_tree' located
-in 'gimplify.c'. From here we process the entire function gimplifying
+ The main entry point to this pass is `gimplify_function_tree' located
+in `gimplify.c'. From here we process the entire function gimplifying
each statement in turn. The main workhorse for this pass is
-'gimplify_expr'. Approximately everything passes through here at least
-once, and it is from here that we invoke the 'lang_hooks.gimplify_expr'
+`gimplify_expr'. Approximately everything passes through here at least
+once, and it is from here that we invoke the `lang_hooks.gimplify_expr'
callback.
The callback should examine the expression in question and return
-'GS_UNHANDLED' if the expression is not a language specific construct
+`GS_UNHANDLED' if the expression is not a language specific construct
that requires attention. Otherwise it should alter the expression in
some way to such that forward progress is made toward producing valid
GIMPLE. If the callback is certain that the transformation is complete
-and the expression is valid GIMPLE, it should return 'GS_ALL_DONE'.
-Otherwise it should return 'GS_OK', which will cause the expression to
+and the expression is valid GIMPLE, it should return `GS_ALL_DONE'.
+Otherwise it should return `GS_OK', which will cause the expression to
be processed again. If the callback encounters an error during the
transformation (because the front end is relying on the gimplification
-process to finish semantic checks), it should return 'GS_ERROR'.
+process to finish semantic checks), it should return `GS_ERROR'.

File: gccint.info, Node: Pass manager, Next: Tree SSA passes, Prev: Gimplification pass, Up: Passes
@@ -6597,20 +6731,20 @@ File: gccint.info, Node: Pass manager, Next: Tree SSA passes, Prev: Gimplific
9.4 Pass manager
================
-The pass manager is located in 'passes.c', 'tree-optimize.c' and
-'tree-pass.h'. It processes passes as described in 'passes.def'. Its
+The pass manager is located in `passes.c', `tree-optimize.c' and
+`tree-pass.h'. It processes passes as described in `passes.def'. Its
job is to run all of the individual passes in the correct order, and
take care of standard bookkeeping that applies to every pass.
The theory of operation is that each pass defines a structure that
-represents everything we need to know about that pass--when it should be
-run, how it should be run, what intermediate language form or
-on-the-side data structures it needs. We register the pass to be run in
-some particular order, and the pass manager arranges for everything to
-happen in the correct order.
+represents everything we need to know about that pass--when it should
+be run, how it should be run, what intermediate language form or
+on-the-side data structures it needs. We register the pass to be run
+in some particular order, and the pass manager arranges for everything
+to happen in the correct order.
The actuality doesn't completely live up to the theory at present.
-Command-line switches and 'timevar_id_t' enumerations must still be
+Command-line switches and `timevar_id_t' enumerations must still be
defined elsewhere. The pass manager validates constraints but does not
attempt to (re-)generate data structures or lower intermediate language
form based on the requirements of the next pass. Nevertheless, what is
@@ -6620,9 +6754,9 @@ present is useful, and a far sight better than nothing at all.
file (for GCC debugging purposes). Passes with a name starting with a
star do not dump anything. Sometimes passes are supposed to share a
dump file / option name. To still give these unique names, you can use
-a prefix that is delimited by a space from the part that is used for the
-dump file / option name. E.g. When the pass name is "ud dce", the name
-used for dump file/options is "dce".
+a prefix that is delimited by a space from the part that is used for
+the dump file / option name. E.g. When the pass name is "ud dce", the
+name used for dump file/options is "dce".
TODO: describe the global variables set up by the pass manager, and a
brief description of how a new pass should use it. I need to look at
@@ -6641,163 +6775,164 @@ run after gimplification and what source files they are located in.
This pass is an extremely simple sweep across the gimple code in
which we identify obviously dead code and remove it. Here we do
- things like simplify 'if' statements with constant conditions,
+ things like simplify `if' statements with constant conditions,
remove exception handling constructs surrounding code that
obviously cannot throw, remove lexical bindings that contain no
variables, and other assorted simplistic cleanups. The idea is to
get rid of the obvious stuff quickly rather than wait until later
when it's more work to get rid of it. This pass is located in
- 'tree-cfg.c' and described by 'pass_remove_useless_stmts'.
+ `tree-cfg.c' and described by `pass_remove_useless_stmts'.
* OpenMP lowering
- If OpenMP generation ('-fopenmp') is enabled, this pass lowers
+ If OpenMP generation (`-fopenmp') is enabled, this pass lowers
OpenMP constructs into GIMPLE.
Lowering of OpenMP constructs involves creating replacement
expressions for local variables that have been mapped using data
sharing clauses, exposing the control flow of most synchronization
directives and adding region markers to facilitate the creation of
- the control flow graph. The pass is located in 'omp-low.c' and is
- described by 'pass_lower_omp'.
+ the control flow graph. The pass is located in `omp-low.c' and is
+ described by `pass_lower_omp'.
* OpenMP expansion
- If OpenMP generation ('-fopenmp') is enabled, this pass expands
+ If OpenMP generation (`-fopenmp') is enabled, this pass expands
parallel regions into their own functions to be invoked by the
- thread library. The pass is located in 'omp-low.c' and is
- described by 'pass_expand_omp'.
+ thread library. The pass is located in `omp-low.c' and is
+ described by `pass_expand_omp'.
* Lower control flow
- This pass flattens 'if' statements ('COND_EXPR') and moves lexical
- bindings ('BIND_EXPR') out of line. After this pass, all 'if'
- statements will have exactly two 'goto' statements in its 'then'
- and 'else' arms. Lexical binding information for each statement
- will be found in 'TREE_BLOCK' rather than being inferred from its
- position under a 'BIND_EXPR'. This pass is found in 'gimple-low.c'
- and is described by 'pass_lower_cf'.
+ This pass flattens `if' statements (`COND_EXPR') and moves lexical
+ bindings (`BIND_EXPR') out of line. After this pass, all `if'
+ statements will have exactly two `goto' statements in its `then'
+ and `else' arms. Lexical binding information for each statement
+ will be found in `TREE_BLOCK' rather than being inferred from its
+ position under a `BIND_EXPR'. This pass is found in
+ `gimple-low.c' and is described by `pass_lower_cf'.
* Lower exception handling control flow
This pass decomposes high-level exception handling constructs
- ('TRY_FINALLY_EXPR' and 'TRY_CATCH_EXPR') into a form that
+ (`TRY_FINALLY_EXPR' and `TRY_CATCH_EXPR') into a form that
explicitly represents the control flow involved. After this pass,
- 'lookup_stmt_eh_region' will return a non-negative number for any
+ `lookup_stmt_eh_region' will return a non-negative number for any
statement that may have EH control flow semantics; examine
- 'tree_can_throw_internal' or 'tree_can_throw_external' for exact
+ `tree_can_throw_internal' or `tree_can_throw_external' for exact
semantics. Exact control flow may be extracted from
- 'foreach_reachable_handler'. The EH region nesting tree is defined
- in 'except.h' and built in 'except.c'. The lowering pass itself is
- in 'tree-eh.c' and is described by 'pass_lower_eh'.
+ `foreach_reachable_handler'. The EH region nesting tree is defined
+ in `except.h' and built in `except.c'. The lowering pass itself
+ is in `tree-eh.c' and is described by `pass_lower_eh'.
* Build the control flow graph
This pass decomposes a function into basic blocks and creates all
- of the edges that connect them. It is located in 'tree-cfg.c' and
- is described by 'pass_build_cfg'.
+ of the edges that connect them. It is located in `tree-cfg.c' and
+ is described by `pass_build_cfg'.
* Find all referenced variables
This pass walks the entire function and collects an array of all
- variables referenced in the function, 'referenced_vars'. The index
- at which a variable is found in the array is used as a UID for the
- variable within this function. This data is needed by the SSA
- rewriting routines. The pass is located in 'tree-dfa.c' and is
- described by 'pass_referenced_vars'.
+ variables referenced in the function, `referenced_vars'. The
+ index at which a variable is found in the array is used as a UID
+ for the variable within this function. This data is needed by the
+ SSA rewriting routines. The pass is located in `tree-dfa.c' and
+ is described by `pass_referenced_vars'.
* Enter static single assignment form
This pass rewrites the function such that it is in SSA form. After
- this pass, all 'is_gimple_reg' variables will be referenced by
- 'SSA_NAME', and all occurrences of other variables will be
- annotated with 'VDEFS' and 'VUSES'; PHI nodes will have been
+ this pass, all `is_gimple_reg' variables will be referenced by
+ `SSA_NAME', and all occurrences of other variables will be
+ annotated with `VDEFS' and `VUSES'; PHI nodes will have been
inserted as necessary for each basic block. This pass is located
- in 'tree-ssa.c' and is described by 'pass_build_ssa'.
+ in `tree-ssa.c' and is described by `pass_build_ssa'.
* Warn for uninitialized variables
- This pass scans the function for uses of 'SSA_NAME's that are fed
+ This pass scans the function for uses of `SSA_NAME's that are fed
by default definition. For non-parameter variables, such uses are
uninitialized. The pass is run twice, before and after
optimization (if turned on). In the first pass we only warn for
uses that are positively uninitialized; in the second pass we warn
for uses that are possibly uninitialized. The pass is located in
- 'tree-ssa.c' and is defined by 'pass_early_warn_uninitialized' and
- 'pass_late_warn_uninitialized'.
+ `tree-ssa.c' and is defined by `pass_early_warn_uninitialized' and
+ `pass_late_warn_uninitialized'.
* Dead code elimination
This pass scans the function for statements without side effects
whose result is unused. It does not do memory life analysis, so
- any value that is stored in memory is considered used. The pass is
- run multiple times throughout the optimization process. It is
- located in 'tree-ssa-dce.c' and is described by 'pass_dce'.
+ any value that is stored in memory is considered used. The pass
+ is run multiple times throughout the optimization process. It is
+ located in `tree-ssa-dce.c' and is described by `pass_dce'.
* Dominator optimizations
This pass performs trivial dominator-based copy and constant
propagation, expression simplification, and jump threading. It is
run multiple times throughout the optimization process. It is
- located in 'tree-ssa-dom.c' and is described by 'pass_dominator'.
+ located in `tree-ssa-dom.c' and is described by `pass_dominator'.
* Forward propagation of single-use variables
This pass attempts to remove redundant computation by substituting
variables that are used once into the expression that uses them and
seeing if the result can be simplified. It is located in
- 'tree-ssa-forwprop.c' and is described by 'pass_forwprop'.
+ `tree-ssa-forwprop.c' and is described by `pass_forwprop'.
* Copy Renaming
This pass attempts to change the name of compiler temporaries
involved in copy operations such that SSA->normal can coalesce the
- copy away. When compiler temporaries are copies of user variables,
- it also renames the compiler temporary to the user variable
- resulting in better use of user symbols. It is located in
- 'tree-ssa-copyrename.c' and is described by 'pass_copyrename'.
+ copy away. When compiler temporaries are copies of user
+ variables, it also renames the compiler temporary to the user
+ variable resulting in better use of user symbols. It is located
+ in `tree-ssa-copyrename.c' and is described by `pass_copyrename'.
* PHI node optimizations
This pass recognizes forms of PHI inputs that can be represented as
conditional expressions and rewrites them into straight line code.
- It is located in 'tree-ssa-phiopt.c' and is described by
- 'pass_phiopt'.
+ It is located in `tree-ssa-phiopt.c' and is described by
+ `pass_phiopt'.
* May-alias optimization
This pass performs a flow sensitive SSA-based points-to analysis.
The resulting may-alias, must-alias, and escape analysis
- information is used to promote variables from in-memory addressable
- objects to non-aliased variables that can be renamed into SSA form.
- We also update the 'VDEF'/'VUSE' memory tags for non-renameable
- aggregates so that we get fewer false kills. The pass is located
- in 'tree-ssa-alias.c' and is described by 'pass_may_alias'.
+ information is used to promote variables from in-memory
+ addressable objects to non-aliased variables that can be renamed
+ into SSA form. We also update the `VDEF'/`VUSE' memory tags for
+ non-renameable aggregates so that we get fewer false kills. The
+ pass is located in `tree-ssa-alias.c' and is described by
+ `pass_may_alias'.
Interprocedural points-to information is located in
- 'tree-ssa-structalias.c' and described by 'pass_ipa_pta'.
+ `tree-ssa-structalias.c' and described by `pass_ipa_pta'.
* Profiling
This pass instruments the function in order to collect runtime
- block and value profiling data. Such data may be fed back into the
- compiler on a subsequent run so as to allow optimization based on
- expected execution frequencies. The pass is located in
- 'tree-profile.c' and is described by 'pass_ipa_tree_profile'.
+ block and value profiling data. Such data may be fed back into
+ the compiler on a subsequent run so as to allow optimization based
+ on expected execution frequencies. The pass is located in
+ `tree-profile.c' and is described by `pass_ipa_tree_profile'.
* Static profile estimation
This pass implements series of heuristics to guess propababilities
of branches. The resulting predictions are turned into edge
profile by propagating branches across the control flow graphs.
- The pass is located in 'tree-profile.c' and is described by
- 'pass_profile'.
+ The pass is located in `tree-profile.c' and is described by
+ `pass_profile'.
* Lower complex arithmetic
This pass rewrites complex arithmetic operations into their
component scalar arithmetic operations. The pass is located in
- 'tree-complex.c' and is described by 'pass_lower_complex'.
+ `tree-complex.c' and is described by `pass_lower_complex'.
* Scalar replacement of aggregates
@@ -6805,109 +6940,110 @@ run after gimplification and what source files they are located in.
into a set of scalar variables. The resulting scalar variables are
rewritten into SSA form, which allows subsequent optimization
passes to do a significantly better job with them. The pass is
- located in 'tree-sra.c' and is described by 'pass_sra'.
+ located in `tree-sra.c' and is described by `pass_sra'.
* Dead store elimination
This pass eliminates stores to memory that are subsequently
overwritten by another store, without any intervening loads. The
- pass is located in 'tree-ssa-dse.c' and is described by 'pass_dse'.
+ pass is located in `tree-ssa-dse.c' and is described by `pass_dse'.
* Tail recursion elimination
This pass transforms tail recursion into a loop. It is located in
- 'tree-tailcall.c' and is described by 'pass_tail_recursion'.
+ `tree-tailcall.c' and is described by `pass_tail_recursion'.
* Forward store motion
- This pass sinks stores and assignments down the flowgraph closer to
- their use point. The pass is located in 'tree-ssa-sink.c' and is
- described by 'pass_sink_code'.
+ This pass sinks stores and assignments down the flowgraph closer
+ to their use point. The pass is located in `tree-ssa-sink.c' and
+ is described by `pass_sink_code'.
* Partial redundancy elimination
This pass eliminates partially redundant computations, as well as
- performing load motion. The pass is located in 'tree-ssa-pre.c'
- and is described by 'pass_pre'.
+ performing load motion. The pass is located in `tree-ssa-pre.c'
+ and is described by `pass_pre'.
Just before partial redundancy elimination, if
- '-funsafe-math-optimizations' is on, GCC tries to convert divisions
- to multiplications by the reciprocal. The pass is located in
- 'tree-ssa-math-opts.c' and is described by 'pass_cse_reciprocal'.
+ `-funsafe-math-optimizations' is on, GCC tries to convert
+ divisions to multiplications by the reciprocal. The pass is
+ located in `tree-ssa-math-opts.c' and is described by
+ `pass_cse_reciprocal'.
* Full redundancy elimination
This is a simpler form of PRE that only eliminates redundancies
- that occur on all paths. It is located in 'tree-ssa-pre.c' and
- described by 'pass_fre'.
+ that occur on all paths. It is located in `tree-ssa-pre.c' and
+ described by `pass_fre'.
* Loop optimization
- The main driver of the pass is placed in 'tree-ssa-loop.c' and
- described by 'pass_loop'.
+ The main driver of the pass is placed in `tree-ssa-loop.c' and
+ described by `pass_loop'.
The optimizations performed by this pass are:
Loop invariant motion. This pass moves only invariants that would
be hard to handle on RTL level (function calls, operations that
- expand to nontrivial sequences of insns). With '-funswitch-loops'
+ expand to nontrivial sequences of insns). With `-funswitch-loops'
it also moves operands of conditions that are invariant out of the
loop, so that we can use just trivial invariantness analysis in
loop unswitching. The pass also includes store motion. The pass
- is implemented in 'tree-ssa-loop-im.c'.
+ is implemented in `tree-ssa-loop-im.c'.
Canonical induction variable creation. This pass creates a simple
counter for number of iterations of the loop and replaces the exit
- condition of the loop using it, in case when a complicated analysis
- is necessary to determine the number of iterations. Later
- optimizations then may determine the number easily. The pass is
- implemented in 'tree-ssa-loop-ivcanon.c'.
+ condition of the loop using it, in case when a complicated
+ analysis is necessary to determine the number of iterations.
+ Later optimizations then may determine the number easily. The
+ pass is implemented in `tree-ssa-loop-ivcanon.c'.
Induction variable optimizations. This pass performs standard
induction variable optimizations, including strength reduction,
- induction variable merging and induction variable elimination. The
- pass is implemented in 'tree-ssa-loop-ivopts.c'.
+ induction variable merging and induction variable elimination.
+ The pass is implemented in `tree-ssa-loop-ivopts.c'.
Loop unswitching. This pass moves the conditional jumps that are
invariant out of the loops. To achieve this, a duplicate of the
loop is created for each possible outcome of conditional jump(s).
- The pass is implemented in 'tree-ssa-loop-unswitch.c'.
+ The pass is implemented in `tree-ssa-loop-unswitch.c'.
The optimizations also use various utility functions contained in
- 'tree-ssa-loop-manip.c', 'cfgloop.c', 'cfgloopanal.c' and
- 'cfgloopmanip.c'.
+ `tree-ssa-loop-manip.c', `cfgloop.c', `cfgloopanal.c' and
+ `cfgloopmanip.c'.
Vectorization. This pass transforms loops to operate on vector
types instead of scalar types. Data parallelism across loop
iterations is exploited to group data elements from consecutive
iterations into a vector and operate on them in parallel.
Depending on available target support the loop is conceptually
- unrolled by a factor 'VF' (vectorization factor), which is the
- number of elements operated upon in parallel in each iteration, and
- the 'VF' copies of each scalar operation are fused to form a vector
- operation. Additional loop transformations such as peeling and
- versioning may take place to align the number of iterations, and to
- align the memory accesses in the loop. The pass is implemented in
- 'tree-vectorizer.c' (the main driver), 'tree-vect-loop.c' and
- 'tree-vect-loop-manip.c' (loop specific parts and general loop
- utilities), 'tree-vect-slp' (loop-aware SLP functionality),
- 'tree-vect-stmts.c' and 'tree-vect-data-refs.c'. Analysis of data
- references is in 'tree-data-ref.c'.
+ unrolled by a factor `VF' (vectorization factor), which is the
+ number of elements operated upon in parallel in each iteration,
+ and the `VF' copies of each scalar operation are fused to form a
+ vector operation. Additional loop transformations such as peeling
+ and versioning may take place to align the number of iterations,
+ and to align the memory accesses in the loop. The pass is
+ implemented in `tree-vectorizer.c' (the main driver),
+ `tree-vect-loop.c' and `tree-vect-loop-manip.c' (loop specific
+ parts and general loop utilities), `tree-vect-slp' (loop-aware SLP
+ functionality), `tree-vect-stmts.c' and `tree-vect-data-refs.c'.
+ Analysis of data references is in `tree-data-ref.c'.
SLP Vectorization. This pass performs vectorization of
- straight-line code. The pass is implemented in 'tree-vectorizer.c'
- (the main driver), 'tree-vect-slp.c', 'tree-vect-stmts.c' and
- 'tree-vect-data-refs.c'.
+ straight-line code. The pass is implemented in `tree-vectorizer.c'
+ (the main driver), `tree-vect-slp.c', `tree-vect-stmts.c' and
+ `tree-vect-data-refs.c'.
Autoparallelization. This pass splits the loop iteration space to
run into several threads. The pass is implemented in
- 'tree-parloops.c'.
+ `tree-parloops.c'.
Graphite is a loop transformation framework based on the polyhedral
model. Graphite stands for Gimple Represented as Polyhedra. The
internals of this infrastructure are documented in
- <http://gcc.gnu.org/wiki/Graphite>. The passes working on this
- representation are implemented in the various 'graphite-*' files.
+ `http://gcc.gnu.org/wiki/Graphite'. The passes working on this
+ representation are implemented in the various `graphite-*' files.
* Tree level if-conversion for vectorizer
@@ -6916,29 +7052,29 @@ run after gimplification and what source files they are located in.
basic blocks in one big block. The idea is to present loop in such
form so that vectorizer can have one to one mapping between
statements and available vector operations. This pass is located
- in 'tree-if-conv.c' and is described by 'pass_if_conversion'.
+ in `tree-if-conv.c' and is described by `pass_if_conversion'.
* Conditional constant propagation
This pass relaxes a lattice of values in order to identify those
that must be constant even in the presence of conditional branches.
- The pass is located in 'tree-ssa-ccp.c' and is described by
- 'pass_ccp'.
+ The pass is located in `tree-ssa-ccp.c' and is described by
+ `pass_ccp'.
A related pass that works on memory loads and stores, and not just
- register values, is located in 'tree-ssa-ccp.c' and described by
- 'pass_store_ccp'.
+ register values, is located in `tree-ssa-ccp.c' and described by
+ `pass_store_ccp'.
* Conditional copy propagation
This is similar to constant propagation but the lattice of values
is the "copy-of" relation. It eliminates redundant copies from the
- code. The pass is located in 'tree-ssa-copy.c' and described by
- 'pass_copy_prop'.
+ code. The pass is located in `tree-ssa-copy.c' and described by
+ `pass_copy_prop'.
A related pass that works on memory copies, and not just register
- copies, is located in 'tree-ssa-copy.c' and described by
- 'pass_store_copy_prop'.
+ copies, is located in `tree-ssa-copy.c' and described by
+ `pass_store_copy_prop'.
* Value range propagation
@@ -6949,27 +7085,28 @@ run after gimplification and what source files they are located in.
Range Propagation, J. R. C. Patterson, PLDI '95). In contrast to
Patterson's algorithm, this implementation does not propagate
branch probabilities nor it uses more than a single range per SSA
- name. This means that the current implementation cannot be used
+ name. This means that the current implementation cannot be used
for branch prediction (though adapting it would not be difficult).
- The pass is located in 'tree-vrp.c' and is described by 'pass_vrp'.
+ The pass is located in `tree-vrp.c' and is described by `pass_vrp'.
* Folding built-in functions
This pass simplifies built-in functions, as applicable, with
- constant arguments or with inferable string lengths. It is located
- in 'tree-ssa-ccp.c' and is described by 'pass_fold_builtins'.
+ constant arguments or with inferable string lengths. It is
+ located in `tree-ssa-ccp.c' and is described by
+ `pass_fold_builtins'.
* Split critical edges
This pass identifies critical edges and inserts empty basic blocks
such that the edge is no longer critical. The pass is located in
- 'tree-cfg.c' and is described by 'pass_split_crit_edges'.
+ `tree-cfg.c' and is described by `pass_split_crit_edges'.
* Control dependence dead code elimination
This pass is a stronger form of dead code elimination that can
- eliminate unnecessary control flow statements. It is located in
- 'tree-ssa-dce.c' and is described by 'pass_cd_dce'.
+ eliminate unnecessary control flow statements. It is located in
+ `tree-ssa-dce.c' and is described by `pass_cd_dce'.
* Tail call elimination
@@ -6977,10 +7114,10 @@ run after gimplification and what source files they are located in.
jumps. No code transformation is actually applied here, but the
data and control flow problem is solved. The code transformation
requires target support, and so is delayed until RTL. In the
- meantime 'CALL_EXPR_TAILCALL' is set indicating the possibility.
- The pass is located in 'tree-tailcall.c' and is described by
- 'pass_tail_calls'. The RTL transformation is handled by
- 'fixup_tail_calls' in 'calls.c'.
+ meantime `CALL_EXPR_TAILCALL' is set indicating the possibility.
+ The pass is located in `tree-tailcall.c' and is described by
+ `pass_tail_calls'. The RTL transformation is handled by
+ `fixup_tail_calls' in `calls.c'.
* Warn for function return without value
@@ -6988,53 +7125,53 @@ run after gimplification and what source files they are located in.
not specify a value and issues a warning. Such a statement may
have been injected by falling off the end of the function. This
pass is run last so that we have as much time as possible to prove
- that the statement is not reachable. It is located in 'tree-cfg.c'
- and is described by 'pass_warn_function_return'.
+ that the statement is not reachable. It is located in
+ `tree-cfg.c' and is described by `pass_warn_function_return'.
* Leave static single assignment form
This pass rewrites the function such that it is in normal form. At
the same time, we eliminate as many single-use temporaries as
possible, so the intermediate language is no longer GIMPLE, but
- GENERIC. The pass is located in 'tree-outof-ssa.c' and is
- described by 'pass_del_ssa'.
+ GENERIC. The pass is located in `tree-outof-ssa.c' and is
+ described by `pass_del_ssa'.
* Merge PHI nodes that feed into one another
This is part of the CFG cleanup passes. It attempts to join PHI
- nodes from a forwarder CFG block into another block with PHI nodes.
- The pass is located in 'tree-cfgcleanup.c' and is described by
- 'pass_merge_phi'.
+ nodes from a forwarder CFG block into another block with PHI
+ nodes. The pass is located in `tree-cfgcleanup.c' and is
+ described by `pass_merge_phi'.
* Return value optimization
If a function always returns the same local variable, and that
local variable is an aggregate type, then the variable is replaced
with the return value for the function (i.e., the function's
- DECL_RESULT). This is equivalent to the C++ named return value
+ DECL_RESULT). This is equivalent to the C++ named return value
optimization applied to GIMPLE. The pass is located in
- 'tree-nrv.c' and is described by 'pass_nrv'.
+ `tree-nrv.c' and is described by `pass_nrv'.
* Return slot optimization
- If a function returns a memory object and is called as 'var =
+ If a function returns a memory object and is called as `var =
foo()', this pass tries to change the call so that the address of
- 'var' is sent to the caller to avoid an extra memory copy. This
- pass is located in 'tree-nrv.c' and is described by
- 'pass_return_slot'.
+ `var' is sent to the caller to avoid an extra memory copy. This
+ pass is located in `tree-nrv.c' and is described by
+ `pass_return_slot'.
- * Optimize calls to '__builtin_object_size'
+ * Optimize calls to `__builtin_object_size'
This is a propagation pass similar to CCP that tries to remove
- calls to '__builtin_object_size' when the size of the object can be
+ calls to `__builtin_object_size' when the size of the object can be
computed at compile-time. This pass is located in
- 'tree-object-size.c' and is described by 'pass_object_sizes'.
+ `tree-object-size.c' and is described by `pass_object_sizes'.
* Loop invariant motion
This pass removes expensive loop-invariant computations out of
- loops. The pass is located in 'tree-ssa-loop.c' and described by
- 'pass_lim'.
+ loops. The pass is located in `tree-ssa-loop.c' and described by
+ `pass_lim'.
* Loop nest optimizations
@@ -7043,55 +7180,56 @@ run after gimplification and what source files they are located in.
they are all geared to the optimization of data locality in array
traversals and the removal of dependencies that hamper
optimizations such as loop parallelization and vectorization. The
- pass is located in 'tree-loop-linear.c' and described by
- 'pass_linear_transform'.
+ pass is located in `tree-loop-linear.c' and described by
+ `pass_linear_transform'.
* Removal of empty loops
This pass removes loops with no code in them. The pass is located
- in 'tree-ssa-loop-ivcanon.c' and described by 'pass_empty_loop'.
+ in `tree-ssa-loop-ivcanon.c' and described by `pass_empty_loop'.
* Unrolling of small loops
This pass completely unrolls loops with few iterations. The pass
- is located in 'tree-ssa-loop-ivcanon.c' and described by
- 'pass_complete_unroll'.
+ is located in `tree-ssa-loop-ivcanon.c' and described by
+ `pass_complete_unroll'.
* Predictive commoning
This pass makes the code reuse the computations from the previous
- iterations of the loops, especially loads and stores to memory. It
- does so by storing the values of these computations to a bank of
- temporary variables that are rotated at the end of loop. To avoid
- the need for this rotation, the loop is then unrolled and the
- copies of the loop body are rewritten to use the appropriate
+ iterations of the loops, especially loads and stores to memory.
+ It does so by storing the values of these computations to a bank
+ of temporary variables that are rotated at the end of loop. To
+ avoid the need for this rotation, the loop is then unrolled and
+ the copies of the loop body are rewritten to use the appropriate
version of the temporary variable. This pass is located in
- 'tree-predcom.c' and described by 'pass_predcom'.
+ `tree-predcom.c' and described by `pass_predcom'.
* Array prefetching
This pass issues prefetch instructions for array references inside
- loops. The pass is located in 'tree-ssa-loop-prefetch.c' and
- described by 'pass_loop_prefetch'.
+ loops. The pass is located in `tree-ssa-loop-prefetch.c' and
+ described by `pass_loop_prefetch'.
* Reassociation
This pass rewrites arithmetic expressions to enable optimizations
that operate on them, like redundancy elimination and
- vectorization. The pass is located in 'tree-ssa-reassoc.c' and
- described by 'pass_reassoc'.
+ vectorization. The pass is located in `tree-ssa-reassoc.c' and
+ described by `pass_reassoc'.
- * Optimization of 'stdarg' functions
+ * Optimization of `stdarg' functions
This pass tries to avoid the saving of register arguments into the
- stack on entry to 'stdarg' functions. If the function doesn't use
- any 'va_start' macros, no registers need to be saved. If
- 'va_start' macros are used, the 'va_list' variables don't escape
+ stack on entry to `stdarg' functions. If the function doesn't use
+ any `va_start' macros, no registers need to be saved. If
+ `va_start' macros are used, the `va_list' variables don't escape
the function, it is only necessary to save registers that will be
- used in 'va_arg' macros. For instance, if 'va_arg' is only used
- with integral types in the function, floating point registers don't
- need to be saved. This pass is located in 'tree-stdarg.c' and
- described by 'pass_stdarg'.
+ used in `va_arg' macros. For instance, if `va_arg' is only used
+ with integral types in the function, floating point registers
+ don't need to be saved. This pass is located in `tree-stdarg.c'
+ and described by `pass_stdarg'.
+

File: gccint.info, Node: RTL passes, Next: Optimization info, Prev: Tree SSA passes, Up: Passes
@@ -7104,34 +7242,34 @@ passes that are run after the Tree optimization passes.
* RTL generation
- The source files for RTL generation include 'stmt.c', 'calls.c',
- 'expr.c', 'explow.c', 'expmed.c', 'function.c', 'optabs.c' and
- 'emit-rtl.c'. Also, the file 'insn-emit.c', generated from the
- machine description by the program 'genemit', is used in this pass.
- The header file 'expr.h' is used for communication within this
- pass.
+ The source files for RTL generation include `stmt.c', `calls.c',
+ `expr.c', `explow.c', `expmed.c', `function.c', `optabs.c' and
+ `emit-rtl.c'. Also, the file `insn-emit.c', generated from the
+ machine description by the program `genemit', is used in this
+ pass. The header file `expr.h' is used for communication within
+ this pass.
- The header files 'insn-flags.h' and 'insn-codes.h', generated from
- the machine description by the programs 'genflags' and 'gencodes',
- tell this pass which standard names are available for use and which
- patterns correspond to them.
+ The header files `insn-flags.h' and `insn-codes.h', generated from
+ the machine description by the programs `genflags' and `gencodes',
+ tell this pass which standard names are available for use and
+ which patterns correspond to them.
* Generation of exception landing pads
This pass generates the glue that handles communication between the
exception handling library routines and the exception handlers
- within the function. Entry points in the function that are invoked
- by the exception handling library are called "landing pads". The
- code for this pass is located in 'except.c'.
+ within the function. Entry points in the function that are
+ invoked by the exception handling library are called "landing
+ pads". The code for this pass is located in `except.c'.
* Control flow graph cleanup
- This pass removes unreachable code, simplifies jumps to next, jumps
- to jump, jumps across jumps, etc. The pass is run multiple times.
- For historical reasons, it is occasionally referred to as the "jump
- optimization pass". The bulk of the code for this pass is in
- 'cfgcleanup.c', and there are support routines in 'cfgrtl.c' and
- 'jump.c'.
+ This pass removes unreachable code, simplifies jumps to next,
+ jumps to jump, jumps across jumps, etc. The pass is run multiple
+ times. For historical reasons, it is occasionally referred to as
+ the "jump optimization pass". The bulk of the code for this pass
+ is in `cfgcleanup.c', and there are support routines in `cfgrtl.c'
+ and `jump.c'.
* Forward propagation of single-def values
@@ -7140,49 +7278,50 @@ passes that are run after the Tree optimization passes.
result can be simplified. It performs copy propagation and
addressing mode selection. The pass is run twice, with values
being propagated into loops only on the second run. The code is
- located in 'fwprop.c'.
+ located in `fwprop.c'.
* Common subexpression elimination
This pass removes redundant computation within basic blocks, and
optimizes addressing modes based on cost. The pass is run twice.
- The code for this pass is located in 'cse.c'.
+ The code for this pass is located in `cse.c'.
* Global common subexpression elimination
- This pass performs two different types of GCSE depending on whether
- you are optimizing for size or not (LCM based GCSE tends to
- increase code size for a gain in speed, while Morel-Renvoise based
- GCSE does not). When optimizing for size, GCSE is done using
- Morel-Renvoise Partial Redundancy Elimination, with the exception
- that it does not try to move invariants out of loops--that is left
- to the loop optimization pass. If MR PRE GCSE is done, code
- hoisting (aka unification) is also done, as well as load motion.
- If you are optimizing for speed, LCM (lazy code motion) based GCSE
- is done. LCM is based on the work of Knoop, Ruthing, and Steffen.
- LCM based GCSE also does loop invariant code motion. We also
- perform load and store motion when optimizing for speed.
- Regardless of which type of GCSE is used, the GCSE pass also
- performs global constant and copy propagation. The source file for
- this pass is 'gcse.c', and the LCM routines are in 'lcm.c'.
+ This pass performs two different types of GCSE depending on
+ whether you are optimizing for size or not (LCM based GCSE tends
+ to increase code size for a gain in speed, while Morel-Renvoise
+ based GCSE does not). When optimizing for size, GCSE is done
+ using Morel-Renvoise Partial Redundancy Elimination, with the
+ exception that it does not try to move invariants out of
+ loops--that is left to the loop optimization pass. If MR PRE
+ GCSE is done, code hoisting (aka unification) is also done, as
+ well as load motion. If you are optimizing for speed, LCM (lazy
+ code motion) based GCSE is done. LCM is based on the work of
+ Knoop, Ruthing, and Steffen. LCM based GCSE also does loop
+ invariant code motion. We also perform load and store motion when
+ optimizing for speed. Regardless of which type of GCSE is used,
+ the GCSE pass also performs global constant and copy propagation.
+ The source file for this pass is `gcse.c', and the LCM routines
+ are in `lcm.c'.
* Loop optimization
This pass performs several loop related optimizations. The source
- files 'cfgloopanal.c' and 'cfgloopmanip.c' contain generic loop
- analysis and manipulation code. Initialization and finalization of
- loop structures is handled by 'loop-init.c'. A loop invariant
- motion pass is implemented in 'loop-invariant.c'. Basic block
- level optimizations--unrolling, and peeling loops-- are implemented
- in 'loop-unroll.c'. Replacing of the exit condition of loops by
- special machine-dependent instructions is handled by
- 'loop-doloop.c'.
+ files `cfgloopanal.c' and `cfgloopmanip.c' contain generic loop
+ analysis and manipulation code. Initialization and finalization
+ of loop structures is handled by `loop-init.c'. A loop invariant
+ motion pass is implemented in `loop-invariant.c'. Basic block
+ level optimizations--unrolling, and peeling loops-- are
+ implemented in `loop-unroll.c'. Replacing of the exit condition
+ of loops by special machine-dependent instructions is handled by
+ `loop-doloop.c'.
* Jump bypassing
This pass is an aggressive form of GCSE that transforms the control
flow graph of a function by propagating constants into conditional
- branch instructions. The source file for this pass is 'gcse.c'.
+ branch instructions. The source file for this pass is `gcse.c'.
* If conversion
@@ -7191,49 +7330,49 @@ passes that are run after the Tree optimization passes.
instructions, and conditional move instructions. In the very last
invocation after reload/LRA, it will generate predicated
instructions when supported by the target. The code is located in
- 'ifcvt.c'.
+ `ifcvt.c'.
* Web construction
This pass splits independent uses of each pseudo-register. This
can improve effect of the other transformation, such as CSE or
- register allocation. The code for this pass is located in 'web.c'.
+ register allocation. The code for this pass is located in `web.c'.
* Instruction combination
This pass attempts to combine groups of two or three instructions
that are related by data flow into single instructions. It
combines the RTL expressions for the instructions by substitution,
- simplifies the result using algebra, and then attempts to match the
- result against the machine description. The code is located in
- 'combine.c'.
+ simplifies the result using algebra, and then attempts to match
+ the result against the machine description. The code is located
+ in `combine.c'.
* Mode switching optimization
This pass looks for instructions that require the processor to be
in a specific "mode" and minimizes the number of mode changes
- required to satisfy all users. What these modes are, and what they
- apply to are completely target-specific. The code for this pass is
- located in 'mode-switching.c'.
+ required to satisfy all users. What these modes are, and what
+ they apply to are completely target-specific. The code for this
+ pass is located in `mode-switching.c'.
* Modulo scheduling
This pass looks at innermost loops and reorders their instructions
by overlapping different iterations. Modulo scheduling is
performed immediately before instruction scheduling. The code for
- this pass is located in 'modulo-sched.c'.
+ this pass is located in `modulo-sched.c'.
* Instruction scheduling
- This pass looks for instructions whose output will not be available
- by the time that it is used in subsequent instructions. Memory
- loads and floating point instructions often have this behavior on
- RISC machines. It re-orders instructions within a basic block to
- try to separate the definition and use of items that otherwise
- would cause pipeline stalls. This pass is performed twice, before
- and after register allocation. The code for this pass is located
- in 'haifa-sched.c', 'sched-deps.c', 'sched-ebb.c', 'sched-rgn.c'
- and 'sched-vis.c'.
+ This pass looks for instructions whose output will not be
+ available by the time that it is used in subsequent instructions.
+ Memory loads and floating point instructions often have this
+ behavior on RISC machines. It re-orders instructions within a
+ basic block to try to separate the definition and use of items
+ that otherwise would cause pipeline stalls. This pass is
+ performed twice, before and after register allocation. The code
+ for this pass is located in `haifa-sched.c', `sched-deps.c',
+ `sched-ebb.c', `sched-rgn.c' and `sched-vis.c'.
* Register allocation
@@ -7257,11 +7396,11 @@ passes that are run after the Tree optimization passes.
regions using register pressure but the user can force it to
use one region or regions corresponding to all loops.
- Source files of the allocator are 'ira.c', 'ira-build.c',
- 'ira-costs.c', 'ira-conflicts.c', 'ira-color.c', 'ira-emit.c',
- 'ira-lives', plus header files 'ira.h' and 'ira-int.h' used
- for the communication between the allocator and the rest of
- the compiler and between the IRA files.
+ Source files of the allocator are `ira.c', `ira-build.c',
+ `ira-costs.c', `ira-conflicts.c', `ira-color.c',
+ `ira-emit.c', `ira-lives', plus header files `ira.h' and
+ `ira-int.h' used for the communication between the allocator
+ and the rest of the compiler and between the IRA files.
* Reloading. This pass renumbers pseudo registers with the
hardware registers numbers they were allocated. Pseudo
@@ -7269,28 +7408,28 @@ passes that are run after the Tree optimization passes.
stack slots. Then it finds instructions that are invalid
because a value has failed to end up in a register, or has
ended up in a register of the wrong kind. It fixes up these
- instructions by reloading the problematical values temporarily
- into registers. Additional instructions are generated to do
- the copying.
+ instructions by reloading the problematical values
+ temporarily into registers. Additional instructions are
+ generated to do the copying.
The reload pass also optionally eliminates the frame pointer
and inserts instructions to save and restore call-clobbered
registers around calls.
- Source files are 'reload.c' and 'reload1.c', plus the header
- 'reload.h' used for communication between them.
+ Source files are `reload.c' and `reload1.c', plus the header
+ `reload.h' used for communication between them.
* This pass is a modern replacement of the reload pass. Source
- files are 'lra.c', 'lra-assign.c', 'lra-coalesce.c',
- 'lra-constraints.c', 'lra-eliminations.c', 'lra-lives.c',
- 'lra-remat.c', 'lra-spills.c', the header 'lra-int.h' used for
- communication between them, and the header 'lra.h' used for
- communication between LRA and the rest of compiler.
+ files are `lra.c', `lra-assign.c', `lra-coalesce.c',
+ `lra-constraints.c', `lra-eliminations.c', `lra-lives.c',
+ `lra-remat.c', `lra-spills.c', the header `lra-int.h' used
+ for communication between them, and the header `lra.h' used
+ for communication between LRA and the rest of compiler.
Unlike the reload pass, intermediate LRA decisions are
- reflected in RTL as much as possible. This reduces the number
- of target-dependent macros and hooks, leaving instruction
- constraints as the primary source of control.
+ reflected in RTL as much as possible. This reduces the
+ number of target-dependent macros and hooks, leaving
+ instruction constraints as the primary source of control.
LRA is run on targets for which TARGET_LRA_P returns true.
@@ -7300,8 +7439,8 @@ passes that are run after the Tree optimization passes.
information is not available, various types of static analysis are
performed to make the predictions normally coming from the profile
feedback (IE execution frequency, branch probability, etc). It is
- implemented in the file 'bb-reorder.c', and the various prediction
- routines are in 'predict.c'.
+ implemented in the file `bb-reorder.c', and the various prediction
+ routines are in `predict.c'.
* Variable tracking
@@ -7309,47 +7448,49 @@ passes that are run after the Tree optimization passes.
in code and generates notes describing the variable locations to
RTL code. The location lists are then generated according to these
notes to debug information if the debugging information format
- supports location lists. The code is located in 'var-tracking.c'.
+ supports location lists. The code is located in `var-tracking.c'.
* Delayed branch scheduling
This optional pass attempts to find instructions that can go into
the delay slots of other instructions, usually jumps and calls.
- The code for this pass is located in 'reorg.c'.
+ The code for this pass is located in `reorg.c'.
* Branch shortening
On many RISC machines, branch instructions have a limited range.
Thus, longer sequences of instructions must be used for long
- branches. In this pass, the compiler figures out what how far each
- instruction will be from each other instruction, and therefore
- whether the usual instructions, or the longer sequences, must be
- used for each branch. The code for this pass is located in
- 'final.c'.
+ branches. In this pass, the compiler figures out what how far
+ each instruction will be from each other instruction, and
+ therefore whether the usual instructions, or the longer sequences,
+ must be used for each branch. The code for this pass is located
+ in `final.c'.
* Register-to-stack conversion
Conversion from usage of some hard registers to usage of a register
stack may be done at this point. Currently, this is supported only
for the floating-point registers of the Intel 80387 coprocessor.
- The code for this pass is located in 'reg-stack.c'.
+ The code for this pass is located in `reg-stack.c'.
* Final
This pass outputs the assembler code for the function. The source
- files are 'final.c' plus 'insn-output.c'; the latter is generated
- automatically from the machine description by the tool 'genoutput'.
- The header file 'conditions.h' is used for communication between
+ files are `final.c' plus `insn-output.c'; the latter is generated
+ automatically from the machine description by the tool `genoutput'.
+ The header file `conditions.h' is used for communication between
these files.
* Debugging information output
This is run after final because it must output the stack slot
offsets for pseudo registers that did not get hard registers.
- Source files are 'dbxout.c' for DBX symbol table format, 'sdbout.c'
- for SDB symbol table format, 'dwarfout.c' for DWARF symbol table
- format, files 'dwarf2out.c' and 'dwarf2asm.c' for DWARF2 symbol
- table format, and 'vmsdbgout.c' for VMS debug symbol table format.
+ Source files are `dbxout.c' for DBX symbol table format,
+ `sdbout.c' for SDB symbol table format, `dwarfout.c' for DWARF
+ symbol table format, files `dwarf2out.c' and `dwarf2asm.c' for
+ DWARF2 symbol table format, and `vmsdbgout.c' for VMS debug symbol
+ table format.
+

File: gccint.info, Node: Optimization info, Prev: RTL passes, Up: Passes
@@ -7358,7 +7499,7 @@ File: gccint.info, Node: Optimization info, Prev: RTL passes, Up: Passes
=====================
This section is describes dump infrastructure which is common to both
-pass dumps as well as optimization dumps. The goal for this
+pass dumps as well as optimization dumps. The goal for this
infrastructure is to provide both gcc developers and users detailed
information about various compiler transformations and optimizations.
@@ -7377,24 +7518,24 @@ File: gccint.info, Node: Dump setup, Next: Optimization groups, Up: Optimizat
9.7.1 Dump setup
----------------
-A dump_manager class is defined in 'dumpfile.h'. Various passes
-register dumping pass-specific information via 'dump_register' in
-'passes.c'. During the registration, an optimization pass can select
-its optimization group (*note Optimization groups::). After that
+A dump_manager class is defined in `dumpfile.h'. Various passes
+register dumping pass-specific information via `dump_register' in
+`passes.c'. During the registration, an optimization pass can select
+its optimization group (*note Optimization groups::). After that
optimization information corresponding to the entire group (presumably
-from multiple passes) can be output via command-line switches. Note
+from multiple passes) can be output via command-line switches. Note
that if a pass does not fit into any of the pre-defined groups, it can
-select 'OPTGROUP_NONE'.
+select `OPTGROUP_NONE'.
Note that in general, a pass need not know its dump output file name,
-whether certain flags are enabled, etc. However, for legacy reasons,
-passes could also call 'dump_begin' which returns a stream in case the
-particular pass has optimization dumps enabled. A pass could call
-'dump_end' when the dump has ended. These methods should go away once
+whether certain flags are enabled, etc. However, for legacy reasons,
+passes could also call `dump_begin' which returns a stream in case the
+particular pass has optimization dumps enabled. A pass could call
+`dump_end' when the dump has ended. These methods should go away once
all the passes are converted to use the new dump infrastructure.
- The recommended way to setup the dump output is via 'dump_start' and
-'dump_end'.
+ The recommended way to setup the dump output is via `dump_start' and
+`dump_end'.

File: gccint.info, Node: Optimization groups, Next: Dump files and streams, Prev: Dump setup, Up: Optimization info
@@ -7402,30 +7543,31 @@ File: gccint.info, Node: Optimization groups, Next: Dump files and streams, P
9.7.2 Optimization groups
-------------------------
-The optimization passes are grouped into several categories. Currently
-defined categories in 'dumpfile.h' are
+The optimization passes are grouped into several categories. Currently
+defined categories in `dumpfile.h' are
-'OPTGROUP_IPA'
- IPA optimization passes. Enabled by '-ipa'
+`OPTGROUP_IPA'
+ IPA optimization passes. Enabled by `-ipa'
-'OPTGROUP_LOOP'
- Loop optimization passes. Enabled by '-loop'.
+`OPTGROUP_LOOP'
+ Loop optimization passes. Enabled by `-loop'.
-'OPTGROUP_INLINE'
- Inlining passes. Enabled by '-inline'.
+`OPTGROUP_INLINE'
+ Inlining passes. Enabled by `-inline'.
-'OPTGROUP_VEC'
- Vectorization passes. Enabled by '-vec'.
+`OPTGROUP_VEC'
+ Vectorization passes. Enabled by `-vec'.
-'OPTGROUP_OTHER'
+`OPTGROUP_OTHER'
All other optimization passes which do not fall into one of the
above.
-'OPTGROUP_ALL'
- All optimization passes. Enabled by '-all'.
+`OPTGROUP_ALL'
+ All optimization passes. Enabled by `-all'.
+
By using groups a user could selectively enable optimization
-information only for a group of passes. By default, the optimization
+information only for a group of passes. By default, the optimization
information for all the passes is dumped.

@@ -7435,25 +7577,24 @@ File: gccint.info, Node: Dump files and streams, Next: Dump output verbosity,
----------------------------
There are two separate output streams available for outputting
-optimization information from passes. Note that both these streams
-accept 'stderr' and 'stdout' as valid streams and thus it is possible to
-dump output to standard output or error. This is specially handy for
+optimization information from passes. Note that both these streams
+accept `stderr' and `stdout' as valid streams and thus it is possible
+to dump output to standard output or error. This is specially handy for
outputting all available information in a single file by redirecting
-'stderr'.
-
-'pstream'
- This stream is for pass-specific dump output. For example,
- '-fdump-tree-vect=foo.v' dumps tree vectorization pass output into
- the given file name 'foo.v'. If the file name is not provided, the
- default file name is based on the source file and pass number.
- Note that one could also use special file names 'stdout' and
- 'stderr' for dumping to standard output and standard error
- respectively.
-
-'alt_stream'
+`stderr'.
+
+``pstream''
+ This stream is for pass-specific dump output. For example,
+ `-fdump-tree-vect=foo.v' dumps tree vectorization pass output into
+ the given file name `foo.v'. If the file name is not provided, the
+ default file name is based on the source file and pass number. Note
+ that one could also use special file names `stdout' and `stderr'
+ for dumping to standard output and standard error respectively.
+
+``alt_stream''
This steam is used for printing optimization specific output in
- response to the '-fopt-info'. Again a file name can be given. If
- the file name is not given, it defaults to 'stderr'.
+ response to the `-fopt-info'. Again a file name can be given. If
+ the file name is not given, it defaults to `stderr'.

File: gccint.info, Node: Dump output verbosity, Next: Dump types, Prev: Dump files and streams, Up: Optimization info
@@ -7463,27 +7604,27 @@ File: gccint.info, Node: Dump output verbosity, Next: Dump types, Prev: Dump
The dump verbosity has the following options
-'optimized'
- Print information when an optimization is successfully applied. It
- is up to a pass to decide which information is relevant. For
+`optimized'
+ Print information when an optimization is successfully applied. It
+ is up to a pass to decide which information is relevant. For
example, the vectorizer passes print the source location of loops
which got successfully vectorized.
-'missed'
- Print information about missed optimizations. Individual passes
- control which information to include in the output. For example,
+`missed'
+ Print information about missed optimizations. Individual passes
+ control which information to include in the output. For example,
gcc -O2 -ftree-vectorize -fopt-info-vec-missed
will print information about missed optimization opportunities from
vectorization passes on stderr.
-'note'
+`note'
Print verbose information about optimizations, such as certain
transformations, more detailed messages about decisions etc.
-'all'
- Print detailed optimization information. This includes OPTIMIZED,
+`all'
+ Print detailed optimization information. This includes OPTIMIZED,
MISSED, and NOTE.

@@ -7492,40 +7633,44 @@ File: gccint.info, Node: Dump types, Next: Dump examples, Prev: Dump output v
9.7.5 Dump types
----------------
-'dump_printf'
-
- This is a generic method for doing formatted output. It takes an
- additional argument 'dump_kind' which signifies the type of dump.
- This method outputs information only when the dumps are enabled for
- this particular 'dump_kind'. Note that the caller doesn't need to
- know if the particular dump is enabled or not, or even the file
- name. The caller only needs to decide which dump output
- information is relevant, and under what conditions. This
- determines the associated flags.
-
- Consider the following example from 'loop-unroll.c' where an
+`dump_printf'
+ This is a generic method for doing formatted output. It takes an
+ additional argument `dump_kind' which signifies the type of dump.
+ This method outputs information only when the dumps are enabled
+ for this particular `dump_kind'. Note that the caller doesn't need
+ to know if the particular dump is enabled or not, or even the file
+ name. The caller only needs to decide which dump output
+ information is relevant, and under what conditions. This determines
+ the associated flags.
+
+ Consider the following example from `loop-unroll.c' where an
informative message about a loop (along with its location) is
printed when any of the following flags is enabled
-
- optimization messages
+
- RTL dumps
+
- detailed dumps
+
int report_flags = MSG_OPTIMIZED_LOCATIONS | TDF_RTL | TDF_DETAILS;
dump_printf_loc (report_flags, locus,
"loop turned into non-loop; it never loops.\n");
-'dump_basic_block'
+`dump_basic_block'
Output basic block.
-'dump_generic_expr'
+
+`dump_generic_expr'
Output generic expression.
-'dump_gimple_stmt'
+
+`dump_gimple_stmt'
Output gimple statement.
Note that the above methods also have variants prefixed with
- '_loc', such as 'dump_printf_loc', which are similar except they
+ `_loc', such as `dump_printf_loc', which are similar except they
also output the source location information.
+

File: gccint.info, Node: Dump examples, Prev: Dump types, Up: Optimization info
@@ -7535,34 +7680,34 @@ File: gccint.info, Node: Dump examples, Prev: Dump types, Up: Optimization in
gcc -O3 -fopt-info-missed=missed.all
outputs missed optimization report from all the passes into
-'missed.all'.
+`missed.all'.
As another example,
gcc -O3 -fopt-info-inline-optimized-missed=inline.txt
- will output information about missed optimizations as well as optimized
-locations from all the inlining passes into 'inline.txt'.
+ will output information about missed optimizations as well as
+optimized locations from all the inlining passes into `inline.txt'.
If the FILENAME is provided, then the dumps from all the applicable
-optimizations are concatenated into the 'filename'. Otherwise the dump
-is output onto 'stderr'. If OPTIONS is omitted, it defaults to
-'all-all', which means dump all available optimization info from all the
-passes. In the following example, all optimization info is output on to
-'stderr'.
+optimizations are concatenated into the `filename'. Otherwise the dump
+is output onto `stderr'. If OPTIONS is omitted, it defaults to
+`all-all', which means dump all available optimization info from all
+the passes. In the following example, all optimization info is output
+on to `stderr'.
gcc -O3 -fopt-info
- Note that '-fopt-info-vec-missed' behaves the same as
-'-fopt-info-missed-vec'.
+ Note that `-fopt-info-vec-missed' behaves the same as
+`-fopt-info-missed-vec'.
As another example, consider
gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt
- Here the two output file names 'vec.miss' and 'loop.opt' are in
-conflict since only one output file is allowed. In this case, only the
-first option takes effect and the subsequent options are ignored. Thus
-only the 'vec.miss' is produced which containts dumps from the
+ Here the two output file names `vec.miss' and `loop.opt' are in
+conflict since only one output file is allowed. In this case, only the
+first option takes effect and the subsequent options are ignored. Thus
+only the `vec.miss' is produced which containts dumps from the
vectorizer about missed opportunities.

@@ -7575,26 +7720,26 @@ The purpose of GENERIC is simply to provide a language-independent way
of representing an entire function in trees. To this end, it was
necessary to add a few new tree codes to the back end, but almost
everything was already there. If you can express it with the codes in
-'gcc/tree.def', it's GENERIC.
+`gcc/tree.def', it's GENERIC.
Early on, there was a great deal of debate about how to think about
statements in a tree IL. In GENERIC, a statement is defined as any
expression whose value, if any, is ignored. A statement will always
-have 'TREE_SIDE_EFFECTS' set (or it will be discarded), but a
-non-statement expression may also have side effects. A 'CALL_EXPR', for
-instance.
+have `TREE_SIDE_EFFECTS' set (or it will be discarded), but a
+non-statement expression may also have side effects. A `CALL_EXPR',
+for instance.
It would be possible for some local optimizations to work on the
GENERIC form of a function; indeed, the adapted tree inliner works fine
-on GENERIC, but the current compiler performs inlining after lowering to
-GIMPLE (a restricted form described in the next section). Indeed,
+on GENERIC, but the current compiler performs inlining after lowering
+to GIMPLE (a restricted form described in the next section). Indeed,
currently the frontends perform this lowering before handing off to
-'tree_rest_of_compilation', but this seems inelegant.
+`tree_rest_of_compilation', but this seems inelegant.
* Menu:
* Deficiencies:: Topics net yet covered in this document.
-* Tree overview:: All about 'tree's.
+* Tree overview:: All about `tree's.
* Types:: Fundamental and aggregate types.
* Declarations:: Type declarations and variables.
* Attributes:: Declaration and type attributes.
@@ -7621,38 +7766,38 @@ File: gccint.info, Node: Tree overview, Next: Types, Prev: Deficiencies, Up:
=============
The central data structure used by the internal representation is the
-'tree'. These nodes, while all of the C type 'tree', are of many
-varieties. A 'tree' is a pointer type, but the object to which it
+`tree'. These nodes, while all of the C type `tree', are of many
+varieties. A `tree' is a pointer type, but the object to which it
points may be of a variety of types. From this point forward, we will
-refer to trees in ordinary type, rather than in 'this font', except when
-talking about the actual C type 'tree'.
+refer to trees in ordinary type, rather than in `this font', except
+when talking about the actual C type `tree'.
You can tell what kind of node a particular tree is by using the
-'TREE_CODE' macro. Many, many macros take trees as input and return
+`TREE_CODE' macro. Many, many macros take trees as input and return
trees as output. However, most macros require a certain kind of tree
-node as input. In other words, there is a type-system for trees, but it
-is not reflected in the C type-system.
+node as input. In other words, there is a type-system for trees, but
+it is not reflected in the C type-system.
- For safety, it is useful to configure GCC with '--enable-checking'.
+ For safety, it is useful to configure GCC with `--enable-checking'.
Although this results in a significant performance penalty (since all
tree types are checked at run-time), and is therefore inappropriate in a
release version, it is extremely helpful during the development process.
Many macros behave as predicates. Many, although not all, of these
-predicates end in '_P'. Do not rely on the result type of these macros
+predicates end in `_P'. Do not rely on the result type of these macros
being of any particular type. You may, however, rely on the fact that
-the type can be compared to '0', so that statements like
+the type can be compared to `0', so that statements like
if (TEST_P (t) && !TEST_P (y))
x = 1;
-and
+ and
int i = (TEST_P (t) != 0);
-are legal. Macros that return 'int' values now may be changed to return
-'tree' values, or other pointers in the future. Even those that
-continue to return 'int' may return multiple nonzero codes where
+ are legal. Macros that return `int' values now may be changed to
+return `tree' values, or other pointers in the future. Even those that
+continue to return `int' may return multiple nonzero codes where
previously they returned only zero and one. Therefore, you should not
write code like
if (TEST_P (t) == 1)
-as this code is not guaranteed to work correctly in the future.
+ as this code is not guaranteed to work correctly in the future.
You should not take the address of values returned by the macros or
functions described here. In particular, no guarantee is given that the
@@ -7665,25 +7810,25 @@ made up entirely of uppercase letters may evaluate its arguments more
than once. You may assume that a macro or function whose name is made
up entirely of lowercase letters will evaluate its arguments only once.
- The 'error_mark_node' is a special tree. Its tree code is
-'ERROR_MARK', but since there is only ever one node with that code, the
-usual practice is to compare the tree against 'error_mark_node'. (This
+ The `error_mark_node' is a special tree. Its tree code is
+`ERROR_MARK', but since there is only ever one node with that code, the
+usual practice is to compare the tree against `error_mark_node'. (This
test is just a test for pointer equality.) If an error has occurred
-during front-end processing the flag 'errorcount' will be set. If the
-front end has encountered code it cannot handle, it will issue a message
-to the user and set 'sorrycount'. When these flags are set, any macro
-or function which normally returns a tree of a particular kind may
-instead return the 'error_mark_node'. Thus, if you intend to do any
-processing of erroneous code, you must be prepared to deal with the
-'error_mark_node'.
+during front-end processing the flag `errorcount' will be set. If the
+front end has encountered code it cannot handle, it will issue a
+message to the user and set `sorrycount'. When these flags are set,
+any macro or function which normally returns a tree of a particular
+kind may instead return the `error_mark_node'. Thus, if you intend to
+do any processing of erroneous code, you must be prepared to deal with
+the `error_mark_node'.
Occasionally, a particular tree slot (like an operand to an expression,
-or a particular field in a declaration) will be referred to as "reserved
-for the back end". These slots are used to store RTL when the tree is
-converted to RTL for use by the GCC back end. However, if that process
-is not taking place (e.g., if the front end is being hooked up to an
-intelligent editor), then those slots may be used by the back end
-presently in use.
+or a particular field in a declaration) will be referred to as
+"reserved for the back end". These slots are used to store RTL when
+the tree is converted to RTL for use by the GCC back end. However, if
+that process is not taking place (e.g., if the front end is being hooked
+up to an intelligent editor), then those slots may be used by the back
+end presently in use.
If you encounter situations that do not match this documentation, such
as tree nodes of types not mentioned here, or macros documented to
@@ -7703,69 +7848,70 @@ File: gccint.info, Node: Macros and Functions, Next: Identifiers, Up: Tree ov
10.2.1 Trees
------------
-All GENERIC trees have two fields in common. First, 'TREE_CHAIN' is a
+All GENERIC trees have two fields in common. First, `TREE_CHAIN' is a
pointer that can be used as a singly-linked list to other trees. The
-other is 'TREE_TYPE'. Many trees store the type of an expression or
+other is `TREE_TYPE'. Many trees store the type of an expression or
declaration in this field.
These are some other functions for handling trees:
-'tree_size'
+`tree_size'
Return the number of bytes a tree takes.
-'build0'
-'build1'
-'build2'
-'build3'
-'build4'
-'build5'
-'build6'
-
+`build0'
+`build1'
+`build2'
+`build3'
+`build4'
+`build5'
+`build6'
These functions build a tree and supply values to put in each
- parameter. The basic signature is 'code, type, [operands]'.
- 'code' is the 'TREE_CODE', and 'type' is a tree representing the
- 'TREE_TYPE'. These are followed by the operands, each of which is
+ parameter. The basic signature is `code, type, [operands]'.
+ `code' is the `TREE_CODE', and `type' is a tree representing the
+ `TREE_TYPE'. These are followed by the operands, each of which is
also a tree.
+

File: gccint.info, Node: Identifiers, Next: Containers, Prev: Macros and Functions, Up: Tree overview
10.2.2 Identifiers
------------------
-An 'IDENTIFIER_NODE' represents a slightly more general concept than the
-standard C or C++ concept of identifier. In particular, an
-'IDENTIFIER_NODE' may contain a '$', or other extraordinary characters.
+An `IDENTIFIER_NODE' represents a slightly more general concept than
+the standard C or C++ concept of identifier. In particular, an
+`IDENTIFIER_NODE' may contain a `$', or other extraordinary characters.
- There are never two distinct 'IDENTIFIER_NODE's representing the same
+ There are never two distinct `IDENTIFIER_NODE's representing the same
identifier. Therefore, you may use pointer equality to compare
-'IDENTIFIER_NODE's, rather than using a routine like 'strcmp'. Use
-'get_identifier' to obtain the unique 'IDENTIFIER_NODE' for a supplied
+`IDENTIFIER_NODE's, rather than using a routine like `strcmp'. Use
+`get_identifier' to obtain the unique `IDENTIFIER_NODE' for a supplied
string.
You can use the following macros to access identifiers:
-'IDENTIFIER_POINTER'
- The string represented by the identifier, represented as a 'char*'.
- This string is always 'NUL'-terminated, and contains no embedded
- 'NUL' characters.
+`IDENTIFIER_POINTER'
+ The string represented by the identifier, represented as a
+ `char*'. This string is always `NUL'-terminated, and contains no
+ embedded `NUL' characters.
-'IDENTIFIER_LENGTH'
- The length of the string returned by 'IDENTIFIER_POINTER', not
- including the trailing 'NUL'. This value of 'IDENTIFIER_LENGTH
- (x)' is always the same as 'strlen (IDENTIFIER_POINTER (x))'.
+`IDENTIFIER_LENGTH'
+ The length of the string returned by `IDENTIFIER_POINTER', not
+ including the trailing `NUL'. This value of `IDENTIFIER_LENGTH
+ (x)' is always the same as `strlen (IDENTIFIER_POINTER (x))'.
-'IDENTIFIER_OPNAME_P'
+`IDENTIFIER_OPNAME_P'
This predicate holds if the identifier represents the name of an
overloaded operator. In this case, you should not depend on the
- contents of either the 'IDENTIFIER_POINTER' or the
- 'IDENTIFIER_LENGTH'.
+ contents of either the `IDENTIFIER_POINTER' or the
+ `IDENTIFIER_LENGTH'.
-'IDENTIFIER_TYPENAME_P'
+`IDENTIFIER_TYPENAME_P'
This predicate holds if the identifier represents the name of a
- user-defined conversion operator. In this case, the 'TREE_TYPE' of
- the 'IDENTIFIER_NODE' holds the type to which the conversion
+ user-defined conversion operator. In this case, the `TREE_TYPE' of
+ the `IDENTIFIER_NODE' holds the type to which the conversion
operator converts.
+

File: gccint.info, Node: Containers, Prev: Identifiers, Up: Tree overview
@@ -7773,22 +7919,22 @@ File: gccint.info, Node: Containers, Prev: Identifiers, Up: Tree overview
-----------------
Two common container data structures can be represented directly with
-tree nodes. A 'TREE_LIST' is a singly linked list containing two trees
-per node. These are the 'TREE_PURPOSE' and 'TREE_VALUE' of each node.
-(Often, the 'TREE_PURPOSE' contains some kind of tag, or additional
-information, while the 'TREE_VALUE' contains the majority of the
-payload. In other cases, the 'TREE_PURPOSE' is simply 'NULL_TREE',
-while in still others both the 'TREE_PURPOSE' and 'TREE_VALUE' are of
-equal stature.) Given one 'TREE_LIST' node, the next node is found by
-following the 'TREE_CHAIN'. If the 'TREE_CHAIN' is 'NULL_TREE', then
+tree nodes. A `TREE_LIST' is a singly linked list containing two trees
+per node. These are the `TREE_PURPOSE' and `TREE_VALUE' of each node.
+(Often, the `TREE_PURPOSE' contains some kind of tag, or additional
+information, while the `TREE_VALUE' contains the majority of the
+payload. In other cases, the `TREE_PURPOSE' is simply `NULL_TREE',
+while in still others both the `TREE_PURPOSE' and `TREE_VALUE' are of
+equal stature.) Given one `TREE_LIST' node, the next node is found by
+following the `TREE_CHAIN'. If the `TREE_CHAIN' is `NULL_TREE', then
you have reached the end of the list.
- A 'TREE_VEC' is a simple vector. The 'TREE_VEC_LENGTH' is an integer
+ A `TREE_VEC' is a simple vector. The `TREE_VEC_LENGTH' is an integer
(not a tree) giving the number of nodes in the vector. The nodes
-themselves are accessed using the 'TREE_VEC_ELT' macro, which takes two
-arguments. The first is the 'TREE_VEC' in question; the second is an
-integer indicating which element in the vector is desired. The elements
-are indexed from zero.
+themselves are accessed using the `TREE_VEC_ELT' macro, which takes two
+arguments. The first is the `TREE_VEC' in question; the second is an
+integer indicating which element in the vector is desired. The
+elements are indexed from zero.

File: gccint.info, Node: Types, Next: Declarations, Prev: Tree overview, Up: GENERIC
@@ -7801,245 +7947,252 @@ that there is exactly one tree node corresponding to each type. There
are often multiple nodes corresponding to the same type.
For the most part, different kinds of types have different tree codes.
-(For example, pointer types use a 'POINTER_TYPE' code while arrays use
-an 'ARRAY_TYPE' code.) However, pointers to member functions use the
-'RECORD_TYPE' code. Therefore, when writing a 'switch' statement that
+(For example, pointer types use a `POINTER_TYPE' code while arrays use
+an `ARRAY_TYPE' code.) However, pointers to member functions use the
+`RECORD_TYPE' code. Therefore, when writing a `switch' statement that
depends on the code associated with a particular type, you should take
-care to handle pointers to member functions under the 'RECORD_TYPE' case
-label.
+care to handle pointers to member functions under the `RECORD_TYPE'
+case label.
The following functions and macros deal with cv-qualification of types:
-'TYPE_MAIN_VARIANT'
+`TYPE_MAIN_VARIANT'
This macro returns the unqualified version of a type. It may be
applied to an unqualified type, but it is not always the identity
function in that case.
A few other macros and functions are usable with all types:
-'TYPE_SIZE'
+`TYPE_SIZE'
The number of bits required to represent the type, represented as
- an 'INTEGER_CST'. For an incomplete type, 'TYPE_SIZE' will be
- 'NULL_TREE'.
-
-'TYPE_ALIGN'
- The alignment of the type, in bits, represented as an 'int'.
-
-'TYPE_NAME'
- This macro returns a declaration (in the form of a 'TYPE_DECL') for
- the type. (Note this macro does _not_ return an 'IDENTIFIER_NODE',
- as you might expect, given its name!) You can look at the
- 'DECL_NAME' of the 'TYPE_DECL' to obtain the actual name of the
- type. The 'TYPE_NAME' will be 'NULL_TREE' for a type that is not a
- built-in type, the result of a typedef, or a named class type.
-
-'TYPE_CANONICAL'
+ an `INTEGER_CST'. For an incomplete type, `TYPE_SIZE' will be
+ `NULL_TREE'.
+
+`TYPE_ALIGN'
+ The alignment of the type, in bits, represented as an `int'.
+
+`TYPE_NAME'
+ This macro returns a declaration (in the form of a `TYPE_DECL') for
+ the type. (Note this macro does _not_ return an
+ `IDENTIFIER_NODE', as you might expect, given its name!) You can
+ look at the `DECL_NAME' of the `TYPE_DECL' to obtain the actual
+ name of the type. The `TYPE_NAME' will be `NULL_TREE' for a type
+ that is not a built-in type, the result of a typedef, or a named
+ class type.
+
+`TYPE_CANONICAL'
This macro returns the "canonical" type for the given type node.
Canonical types are used to improve performance in the C++ and
Objective-C++ front ends by allowing efficient comparison between
- two type nodes in 'same_type_p': if the 'TYPE_CANONICAL' values of
+ two type nodes in `same_type_p': if the `TYPE_CANONICAL' values of
the types are equal, the types are equivalent; otherwise, the types
- are not equivalent. The notion of equivalence for canonical types
+ are not equivalent. The notion of equivalence for canonical types
is the same as the notion of type equivalence in the language
- itself. For instance,
+ itself. For instance,
- When 'TYPE_CANONICAL' is 'NULL_TREE', there is no canonical type
- for the given type node. In this case, comparison between this
+ When `TYPE_CANONICAL' is `NULL_TREE', there is no canonical type
+ for the given type node. In this case, comparison between this
type and any other type requires the compiler to perform a deep,
"structural" comparison to see if the two type nodes have the same
form and properties.
The canonical type for a node is always the most fundamental type
- in the equivalence class of types. For instance, 'int' is its own
- canonical type. A typedef 'I' of 'int' will have 'int' as its
- canonical type. Similarly, 'I*' and a typedef 'IP' (defined to
- 'I*') will has 'int*' as their canonical type. When building a new
- type node, be sure to set 'TYPE_CANONICAL' to the appropriate
- canonical type. If the new type is a compound type (built from
+ in the equivalence class of types. For instance, `int' is its own
+ canonical type. A typedef `I' of `int' will have `int' as its
+ canonical type. Similarly, `I*' and a typedef `IP' (defined to
+ `I*') will has `int*' as their canonical type. When building a new
+ type node, be sure to set `TYPE_CANONICAL' to the appropriate
+ canonical type. If the new type is a compound type (built from
other types), and any of those other types require structural
- equality, use 'SET_TYPE_STRUCTURAL_EQUALITY' to ensure that the new
- type also requires structural equality. Finally, if for some
- reason you cannot guarantee that 'TYPE_CANONICAL' will point to the
- canonical type, use 'SET_TYPE_STRUCTURAL_EQUALITY' to make sure
- that the new type-and any type constructed based on it-requires
- structural equality. If you suspect that the canonical type system
- is miscomparing types, pass '--param verify-canonical-types=1' to
- the compiler or configure with '--enable-checking' to force the
- compiler to verify its canonical-type comparisons against the
- structural comparisons; the compiler will then print any warnings
- if the canonical types miscompare.
-
-'TYPE_STRUCTURAL_EQUALITY_P'
+ equality, use `SET_TYPE_STRUCTURAL_EQUALITY' to ensure that the
+ new type also requires structural equality. Finally, if for some
+ reason you cannot guarantee that `TYPE_CANONICAL' will point to
+ the canonical type, use `SET_TYPE_STRUCTURAL_EQUALITY' to make
+ sure that the new type-and any type constructed based on
+ it-requires structural equality. If you suspect that the canonical
+ type system is miscomparing types, pass `--param
+ verify-canonical-types=1' to the compiler or configure with
+ `--enable-checking' to force the compiler to verify its
+ canonical-type comparisons against the structural comparisons; the
+ compiler will then print any warnings if the canonical types
+ miscompare.
+
+`TYPE_STRUCTURAL_EQUALITY_P'
This predicate holds when the node requires structural equality
- checks, e.g., when 'TYPE_CANONICAL' is 'NULL_TREE'.
+ checks, e.g., when `TYPE_CANONICAL' is `NULL_TREE'.
-'SET_TYPE_STRUCTURAL_EQUALITY'
+`SET_TYPE_STRUCTURAL_EQUALITY'
This macro states that the type node it is given requires
- structural equality checks, e.g., it sets 'TYPE_CANONICAL' to
- 'NULL_TREE'.
+ structural equality checks, e.g., it sets `TYPE_CANONICAL' to
+ `NULL_TREE'.
-'same_type_p'
+`same_type_p'
This predicate takes two types as input, and holds if they are the
- same type. For example, if one type is a 'typedef' for the other,
- or both are 'typedef's for the same type. This predicate also
+ same type. For example, if one type is a `typedef' for the other,
+ or both are `typedef's for the same type. This predicate also
holds if the two trees given as input are simply copies of one
another; i.e., there is no difference between them at the source
level, but, for whatever reason, a duplicate has been made in the
- representation. You should never use '==' (pointer equality) to
- compare types; always use 'same_type_p' instead.
+ representation. You should never use `==' (pointer equality) to
+ compare types; always use `same_type_p' instead.
Detailed below are the various kinds of types, and the macros that can
be used to access them. Although other kinds of types are used
elsewhere in G++, the types described here are the only ones that you
will encounter while examining the intermediate representation.
-'VOID_TYPE'
- Used to represent the 'void' type.
-
-'INTEGER_TYPE'
- Used to represent the various integral types, including 'char',
- 'short', 'int', 'long', and 'long long'. This code is not used for
- enumeration types, nor for the 'bool' type. The 'TYPE_PRECISION'
- is the number of bits used in the representation, represented as an
- 'unsigned int'. (Note that in the general case this is not the
- same value as 'TYPE_SIZE'; suppose that there were a 24-bit integer
- type, but that alignment requirements for the ABI required 32-bit
- alignment. Then, 'TYPE_SIZE' would be an 'INTEGER_CST' for 32,
- while 'TYPE_PRECISION' would be 24.) The integer type is unsigned
- if 'TYPE_UNSIGNED' holds; otherwise, it is signed.
-
- The 'TYPE_MIN_VALUE' is an 'INTEGER_CST' for the smallest integer
+`VOID_TYPE'
+ Used to represent the `void' type.
+
+`INTEGER_TYPE'
+ Used to represent the various integral types, including `char',
+ `short', `int', `long', and `long long'. This code is not used
+ for enumeration types, nor for the `bool' type. The
+ `TYPE_PRECISION' is the number of bits used in the representation,
+ represented as an `unsigned int'. (Note that in the general case
+ this is not the same value as `TYPE_SIZE'; suppose that there were
+ a 24-bit integer type, but that alignment requirements for the ABI
+ required 32-bit alignment. Then, `TYPE_SIZE' would be an
+ `INTEGER_CST' for 32, while `TYPE_PRECISION' would be 24.) The
+ integer type is unsigned if `TYPE_UNSIGNED' holds; otherwise, it
+ is signed.
+
+ The `TYPE_MIN_VALUE' is an `INTEGER_CST' for the smallest integer
that may be represented by this type. Similarly, the
- 'TYPE_MAX_VALUE' is an 'INTEGER_CST' for the largest integer that
+ `TYPE_MAX_VALUE' is an `INTEGER_CST' for the largest integer that
may be represented by this type.
-'REAL_TYPE'
- Used to represent the 'float', 'double', and 'long double' types.
- The number of bits in the floating-point representation is given by
- 'TYPE_PRECISION', as in the 'INTEGER_TYPE' case.
-
-'FIXED_POINT_TYPE'
- Used to represent the 'short _Fract', '_Fract', 'long _Fract',
- 'long long _Fract', 'short _Accum', '_Accum', 'long _Accum', and
- 'long long _Accum' types. The number of bits in the fixed-point
- representation is given by 'TYPE_PRECISION', as in the
- 'INTEGER_TYPE' case. There may be padding bits, fractional bits
+`REAL_TYPE'
+ Used to represent the `float', `double', and `long double' types.
+ The number of bits in the floating-point representation is given
+ by `TYPE_PRECISION', as in the `INTEGER_TYPE' case.
+
+`FIXED_POINT_TYPE'
+ Used to represent the `short _Fract', `_Fract', `long _Fract',
+ `long long _Fract', `short _Accum', `_Accum', `long _Accum', and
+ `long long _Accum' types. The number of bits in the fixed-point
+ representation is given by `TYPE_PRECISION', as in the
+ `INTEGER_TYPE' case. There may be padding bits, fractional bits
and integral bits. The number of fractional bits is given by
- 'TYPE_FBIT', and the number of integral bits is given by
- 'TYPE_IBIT'. The fixed-point type is unsigned if 'TYPE_UNSIGNED'
- holds; otherwise, it is signed. The fixed-point type is saturating
- if 'TYPE_SATURATING' holds; otherwise, it is not saturating.
-
-'COMPLEX_TYPE'
- Used to represent GCC built-in '__complex__' data types. The
- 'TREE_TYPE' is the type of the real and imaginary parts.
-
-'ENUMERAL_TYPE'
- Used to represent an enumeration type. The 'TYPE_PRECISION' gives
- (as an 'int'), the number of bits used to represent the type. If
- there are no negative enumeration constants, 'TYPE_UNSIGNED' will
+ `TYPE_FBIT', and the number of integral bits is given by
+ `TYPE_IBIT'. The fixed-point type is unsigned if `TYPE_UNSIGNED'
+ holds; otherwise, it is signed. The fixed-point type is
+ saturating if `TYPE_SATURATING' holds; otherwise, it is not
+ saturating.
+
+`COMPLEX_TYPE'
+ Used to represent GCC built-in `__complex__' data types. The
+ `TREE_TYPE' is the type of the real and imaginary parts.
+
+`ENUMERAL_TYPE'
+ Used to represent an enumeration type. The `TYPE_PRECISION' gives
+ (as an `int'), the number of bits used to represent the type. If
+ there are no negative enumeration constants, `TYPE_UNSIGNED' will
hold. The minimum and maximum enumeration constants may be
- obtained with 'TYPE_MIN_VALUE' and 'TYPE_MAX_VALUE', respectively;
- each of these macros returns an 'INTEGER_CST'.
+ obtained with `TYPE_MIN_VALUE' and `TYPE_MAX_VALUE', respectively;
+ each of these macros returns an `INTEGER_CST'.
The actual enumeration constants themselves may be obtained by
- looking at the 'TYPE_VALUES'. This macro will return a
- 'TREE_LIST', containing the constants. The 'TREE_PURPOSE' of each
- node will be an 'IDENTIFIER_NODE' giving the name of the constant;
- the 'TREE_VALUE' will be an 'INTEGER_CST' giving the value assigned
- to that constant. These constants will appear in the order in
- which they were declared. The 'TREE_TYPE' of each of these
- constants will be the type of enumeration type itself.
-
-'BOOLEAN_TYPE'
- Used to represent the 'bool' type.
-
-'POINTER_TYPE'
+ looking at the `TYPE_VALUES'. This macro will return a
+ `TREE_LIST', containing the constants. The `TREE_PURPOSE' of each
+ node will be an `IDENTIFIER_NODE' giving the name of the constant;
+ the `TREE_VALUE' will be an `INTEGER_CST' giving the value
+ assigned to that constant. These constants will appear in the
+ order in which they were declared. The `TREE_TYPE' of each of
+ these constants will be the type of enumeration type itself.
+
+`BOOLEAN_TYPE'
+ Used to represent the `bool' type.
+
+`POINTER_TYPE'
Used to represent pointer types, and pointer to data member types.
- The 'TREE_TYPE' gives the type to which this type points.
+ The `TREE_TYPE' gives the type to which this type points.
-'REFERENCE_TYPE'
- Used to represent reference types. The 'TREE_TYPE' gives the type
+`REFERENCE_TYPE'
+ Used to represent reference types. The `TREE_TYPE' gives the type
to which this type refers.
-'FUNCTION_TYPE'
+`FUNCTION_TYPE'
Used to represent the type of non-member functions and of static
- member functions. The 'TREE_TYPE' gives the return type of the
- function. The 'TYPE_ARG_TYPES' are a 'TREE_LIST' of the argument
- types. The 'TREE_VALUE' of each node in this list is the type of
- the corresponding argument; the 'TREE_PURPOSE' is an expression for
- the default argument value, if any. If the last node in the list
- is 'void_list_node' (a 'TREE_LIST' node whose 'TREE_VALUE' is the
- 'void_type_node'), then functions of this type do not take variable
- arguments. Otherwise, they do take a variable number of arguments.
-
- Note that in C (but not in C++) a function declared like 'void f()'
+ member functions. The `TREE_TYPE' gives the return type of the
+ function. The `TYPE_ARG_TYPES' are a `TREE_LIST' of the argument
+ types. The `TREE_VALUE' of each node in this list is the type of
+ the corresponding argument; the `TREE_PURPOSE' is an expression
+ for the default argument value, if any. If the last node in the
+ list is `void_list_node' (a `TREE_LIST' node whose `TREE_VALUE' is
+ the `void_type_node'), then functions of this type do not take
+ variable arguments. Otherwise, they do take a variable number of
+ arguments.
+
+ Note that in C (but not in C++) a function declared like `void f()'
is an unprototyped function taking a variable number of arguments;
- the 'TYPE_ARG_TYPES' of such a function will be 'NULL'.
+ the `TYPE_ARG_TYPES' of such a function will be `NULL'.
-'METHOD_TYPE'
+`METHOD_TYPE'
Used to represent the type of a non-static member function. Like a
- 'FUNCTION_TYPE', the return type is given by the 'TREE_TYPE'. The
- type of '*this', i.e., the class of which functions of this type
- are a member, is given by the 'TYPE_METHOD_BASETYPE'. The
- 'TYPE_ARG_TYPES' is the parameter list, as for a 'FUNCTION_TYPE',
- and includes the 'this' argument.
-
-'ARRAY_TYPE'
- Used to represent array types. The 'TREE_TYPE' gives the type of
+ `FUNCTION_TYPE', the return type is given by the `TREE_TYPE'. The
+ type of `*this', i.e., the class of which functions of this type
+ are a member, is given by the `TYPE_METHOD_BASETYPE'. The
+ `TYPE_ARG_TYPES' is the parameter list, as for a `FUNCTION_TYPE',
+ and includes the `this' argument.
+
+`ARRAY_TYPE'
+ Used to represent array types. The `TREE_TYPE' gives the type of
the elements in the array. If the array-bound is present in the
- type, the 'TYPE_DOMAIN' is an 'INTEGER_TYPE' whose 'TYPE_MIN_VALUE'
- and 'TYPE_MAX_VALUE' will be the lower and upper bounds of the
- array, respectively. The 'TYPE_MIN_VALUE' will always be an
- 'INTEGER_CST' for zero, while the 'TYPE_MAX_VALUE' will be one less
- than the number of elements in the array, i.e., the highest value
- which may be used to index an element in the array.
-
-'RECORD_TYPE'
- Used to represent 'struct' and 'class' types, as well as pointers
+ type, the `TYPE_DOMAIN' is an `INTEGER_TYPE' whose
+ `TYPE_MIN_VALUE' and `TYPE_MAX_VALUE' will be the lower and upper
+ bounds of the array, respectively. The `TYPE_MIN_VALUE' will
+ always be an `INTEGER_CST' for zero, while the `TYPE_MAX_VALUE'
+ will be one less than the number of elements in the array, i.e.,
+ the highest value which may be used to index an element in the
+ array.
+
+`RECORD_TYPE'
+ Used to represent `struct' and `class' types, as well as pointers
to member functions and similar constructs in other languages.
- 'TYPE_FIELDS' contains the items contained in this type, each of
- which can be a 'FIELD_DECL', 'VAR_DECL', 'CONST_DECL', or
- 'TYPE_DECL'. You may not make any assumptions about the ordering
+ `TYPE_FIELDS' contains the items contained in this type, each of
+ which can be a `FIELD_DECL', `VAR_DECL', `CONST_DECL', or
+ `TYPE_DECL'. You may not make any assumptions about the ordering
of the fields in the type or whether one or more of them overlap.
-'UNION_TYPE'
- Used to represent 'union' types. Similar to 'RECORD_TYPE' except
- that all 'FIELD_DECL' nodes in 'TYPE_FIELD' start at bit position
+`UNION_TYPE'
+ Used to represent `union' types. Similar to `RECORD_TYPE' except
+ that all `FIELD_DECL' nodes in `TYPE_FIELD' start at bit position
zero.
-'QUAL_UNION_TYPE'
+`QUAL_UNION_TYPE'
Used to represent part of a variant record in Ada. Similar to
- 'UNION_TYPE' except that each 'FIELD_DECL' has a 'DECL_QUALIFIER'
+ `UNION_TYPE' except that each `FIELD_DECL' has a `DECL_QUALIFIER'
field, which contains a boolean expression that indicates whether
the field is present in the object. The type will only have one
- field, so each field's 'DECL_QUALIFIER' is only evaluated if none
- of the expressions in the previous fields in 'TYPE_FIELDS' are
+ field, so each field's `DECL_QUALIFIER' is only evaluated if none
+ of the expressions in the previous fields in `TYPE_FIELDS' are
nonzero. Normally these expressions will reference a field in the
- outer object using a 'PLACEHOLDER_EXPR'.
+ outer object using a `PLACEHOLDER_EXPR'.
-'LANG_TYPE'
+`LANG_TYPE'
This node is used to represent a language-specific type. The front
end must handle it.
-'OFFSET_TYPE'
+`OFFSET_TYPE'
This node is used to represent a pointer-to-data member. For a
- data member 'X::m' the 'TYPE_OFFSET_BASETYPE' is 'X' and the
- 'TREE_TYPE' is the type of 'm'.
+ data member `X::m' the `TYPE_OFFSET_BASETYPE' is `X' and the
+ `TREE_TYPE' is the type of `m'.
+
There are variables whose values represent some of the basic types.
These include:
-'void_type_node'
- A node for 'void'.
+`void_type_node'
+ A node for `void'.
-'integer_type_node'
- A node for 'int'.
+`integer_type_node'
+ A node for `int'.
-'unsigned_type_node.'
- A node for 'unsigned int'.
+`unsigned_type_node.'
+ A node for `unsigned int'.
-'char_type_node.'
- A node for 'char'.
-It may sometimes be useful to compare one of these variables with a type
-in hand, using 'same_type_p'.
+`char_type_node.'
+ A node for `char'.
+ It may sometimes be useful to compare one of these variables with a
+type in hand, using `same_type_p'.

File: gccint.info, Node: Declarations, Next: Attributes, Prev: Types, Up: GENERIC
@@ -8049,7 +8202,7 @@ File: gccint.info, Node: Declarations, Next: Attributes, Prev: Types, Up: GE
This section covers the various kinds of declarations that appear in the
internal representation, except for declarations of functions
-(represented by 'FUNCTION_DECL' nodes), which are described in *note
+(represented by `FUNCTION_DECL' nodes), which are described in *note
Functions::.
* Menu:
@@ -8065,123 +8218,125 @@ File: gccint.info, Node: Working with declarations, Next: Internal structure,
--------------------------------
Some macros can be used with any kind of declaration. These include:
-'DECL_NAME'
- This macro returns an 'IDENTIFIER_NODE' giving the name of the
+`DECL_NAME'
+ This macro returns an `IDENTIFIER_NODE' giving the name of the
entity.
-'TREE_TYPE'
+`TREE_TYPE'
This macro returns the type of the entity declared.
-'EXPR_FILENAME'
+`EXPR_FILENAME'
This macro returns the name of the file in which the entity was
- declared, as a 'char*'. For an entity declared implicitly by the
- compiler (like '__builtin_memcpy'), this will be the string
- '"<internal>"'.
+ declared, as a `char*'. For an entity declared implicitly by the
+ compiler (like `__builtin_memcpy'), this will be the string
+ `"<internal>"'.
-'EXPR_LINENO'
+`EXPR_LINENO'
This macro returns the line number at which the entity was
- declared, as an 'int'.
+ declared, as an `int'.
-'DECL_ARTIFICIAL'
- This predicate holds if the declaration was implicitly generated by
- the compiler. For example, this predicate will hold of an
- implicitly declared member function, or of the 'TYPE_DECL'
+`DECL_ARTIFICIAL'
+ This predicate holds if the declaration was implicitly generated
+ by the compiler. For example, this predicate will hold of an
+ implicitly declared member function, or of the `TYPE_DECL'
implicitly generated for a class type. Recall that in C++ code
like:
struct S {};
is roughly equivalent to C code like:
struct S {};
typedef struct S S;
- The implicitly generated 'typedef' declaration is represented by a
- 'TYPE_DECL' for which 'DECL_ARTIFICIAL' holds.
+ The implicitly generated `typedef' declaration is represented by a
+ `TYPE_DECL' for which `DECL_ARTIFICIAL' holds.
+
The various kinds of declarations include:
-'LABEL_DECL'
+`LABEL_DECL'
These nodes are used to represent labels in function bodies. For
more information, see *note Functions::. These nodes only appear
in block scopes.
-'CONST_DECL'
- These nodes are used to represent enumeration constants. The value
- of the constant is given by 'DECL_INITIAL' which will be an
- 'INTEGER_CST' with the same type as the 'TREE_TYPE' of the
- 'CONST_DECL', i.e., an 'ENUMERAL_TYPE'.
+`CONST_DECL'
+ These nodes are used to represent enumeration constants. The
+ value of the constant is given by `DECL_INITIAL' which will be an
+ `INTEGER_CST' with the same type as the `TREE_TYPE' of the
+ `CONST_DECL', i.e., an `ENUMERAL_TYPE'.
-'RESULT_DECL'
+`RESULT_DECL'
These nodes represent the value returned by a function. When a
- value is assigned to a 'RESULT_DECL', that indicates that the value
- should be returned, via bitwise copy, by the function. You can use
- 'DECL_SIZE' and 'DECL_ALIGN' on a 'RESULT_DECL', just as with a
- 'VAR_DECL'.
-
-'TYPE_DECL'
- These nodes represent 'typedef' declarations. The 'TREE_TYPE' is
- the type declared to have the name given by 'DECL_NAME'. In some
+ value is assigned to a `RESULT_DECL', that indicates that the
+ value should be returned, via bitwise copy, by the function. You
+ can use `DECL_SIZE' and `DECL_ALIGN' on a `RESULT_DECL', just as
+ with a `VAR_DECL'.
+
+`TYPE_DECL'
+ These nodes represent `typedef' declarations. The `TREE_TYPE' is
+ the type declared to have the name given by `DECL_NAME'. In some
cases, there is no associated name.
-'VAR_DECL'
+`VAR_DECL'
These nodes represent variables with namespace or block scope, as
- well as static data members. The 'DECL_SIZE' and 'DECL_ALIGN' are
- analogous to 'TYPE_SIZE' and 'TYPE_ALIGN'. For a declaration, you
- should always use the 'DECL_SIZE' and 'DECL_ALIGN' rather than the
- 'TYPE_SIZE' and 'TYPE_ALIGN' given by the 'TREE_TYPE', since
- special attributes may have been applied to the variable to give it
- a particular size and alignment. You may use the predicates
- 'DECL_THIS_STATIC' or 'DECL_THIS_EXTERN' to test whether the
- storage class specifiers 'static' or 'extern' were used to declare
+ well as static data members. The `DECL_SIZE' and `DECL_ALIGN' are
+ analogous to `TYPE_SIZE' and `TYPE_ALIGN'. For a declaration, you
+ should always use the `DECL_SIZE' and `DECL_ALIGN' rather than the
+ `TYPE_SIZE' and `TYPE_ALIGN' given by the `TREE_TYPE', since
+ special attributes may have been applied to the variable to give
+ it a particular size and alignment. You may use the predicates
+ `DECL_THIS_STATIC' or `DECL_THIS_EXTERN' to test whether the
+ storage class specifiers `static' or `extern' were used to declare
a variable.
If this variable is initialized (but does not require a
- constructor), the 'DECL_INITIAL' will be an expression for the
+ constructor), the `DECL_INITIAL' will be an expression for the
initializer. The initializer should be evaluated, and a bitwise
- copy into the variable performed. If the 'DECL_INITIAL' is the
- 'error_mark_node', there is an initializer, but it is given by an
+ copy into the variable performed. If the `DECL_INITIAL' is the
+ `error_mark_node', there is an initializer, but it is given by an
explicit statement later in the code; no bitwise copy is required.
GCC provides an extension that allows either automatic variables,
or global variables, to be placed in particular registers. This
- extension is being used for a particular 'VAR_DECL' if
- 'DECL_REGISTER' holds for the 'VAR_DECL', and if
- 'DECL_ASSEMBLER_NAME' is not equal to 'DECL_NAME'. In that case,
- 'DECL_ASSEMBLER_NAME' is the name of the register into which the
+ extension is being used for a particular `VAR_DECL' if
+ `DECL_REGISTER' holds for the `VAR_DECL', and if
+ `DECL_ASSEMBLER_NAME' is not equal to `DECL_NAME'. In that case,
+ `DECL_ASSEMBLER_NAME' is the name of the register into which the
variable will be placed.
-'PARM_DECL'
+`PARM_DECL'
Used to represent a parameter to a function. Treat these nodes
- similarly to 'VAR_DECL' nodes. These nodes only appear in the
- 'DECL_ARGUMENTS' for a 'FUNCTION_DECL'.
+ similarly to `VAR_DECL' nodes. These nodes only appear in the
+ `DECL_ARGUMENTS' for a `FUNCTION_DECL'.
- The 'DECL_ARG_TYPE' for a 'PARM_DECL' is the type that will
+ The `DECL_ARG_TYPE' for a `PARM_DECL' is the type that will
actually be used when a value is passed to this function. It may
- be a wider type than the 'TREE_TYPE' of the parameter; for example,
- the ordinary type might be 'short' while the 'DECL_ARG_TYPE' is
- 'int'.
+ be a wider type than the `TREE_TYPE' of the parameter; for
+ example, the ordinary type might be `short' while the
+ `DECL_ARG_TYPE' is `int'.
-'DEBUG_EXPR_DECL'
+`DEBUG_EXPR_DECL'
Used to represent an anonymous debug-information temporary created
to hold an expression as it is optimized away, so that its value
can be referenced in debug bind statements.
-'FIELD_DECL'
- These nodes represent non-static data members. The 'DECL_SIZE' and
- 'DECL_ALIGN' behave as for 'VAR_DECL' nodes. The position of the
+`FIELD_DECL'
+ These nodes represent non-static data members. The `DECL_SIZE' and
+ `DECL_ALIGN' behave as for `VAR_DECL' nodes. The position of the
field within the parent record is specified by a combination of
- three attributes. 'DECL_FIELD_OFFSET' is the position, counting in
- bytes, of the 'DECL_OFFSET_ALIGN'-bit sized word containing the bit
- of the field closest to the beginning of the structure.
- 'DECL_FIELD_BIT_OFFSET' is the bit offset of the first bit of the
+ three attributes. `DECL_FIELD_OFFSET' is the position, counting
+ in bytes, of the `DECL_OFFSET_ALIGN'-bit sized word containing the
+ bit of the field closest to the beginning of the structure.
+ `DECL_FIELD_BIT_OFFSET' is the bit offset of the first bit of the
field within this word; this may be nonzero even for fields that
- are not bit-fields, since 'DECL_OFFSET_ALIGN' may be greater than
+ are not bit-fields, since `DECL_OFFSET_ALIGN' may be greater than
the natural alignment of the field's type.
- If 'DECL_C_BIT_FIELD' holds, this field is a bit-field. In a
- bit-field, 'DECL_BIT_FIELD_TYPE' also contains the type that was
- originally specified for it, while DECL_TYPE may be a modified type
- with lesser precision, according to the size of the bit field.
+ If `DECL_C_BIT_FIELD' holds, this field is a bit-field. In a
+ bit-field, `DECL_BIT_FIELD_TYPE' also contains the type that was
+ originally specified for it, while DECL_TYPE may be a modified
+ type with lesser precision, according to the size of the bit field.
-'NAMESPACE_DECL'
+`NAMESPACE_DECL'
Namespaces provide a name hierarchy for other declarations. They
- appear in the 'DECL_CONTEXT' of other '_DECL' nodes.
+ appear in the `DECL_CONTEXT' of other `_DECL' nodes.
+

File: gccint.info, Node: Internal structure, Prev: Working with declarations, Up: Declarations
@@ -8189,7 +8344,7 @@ File: gccint.info, Node: Internal structure, Prev: Working with declarations,
10.4.2 Internal structure
-------------------------
-'DECL' nodes are represented internally as a hierarchy of structures.
+`DECL' nodes are represented internally as a hierarchy of structures.
* Menu:
@@ -8204,57 +8359,58 @@ File: gccint.info, Node: Current structure hierarchy, Next: Adding new DECL no
10.4.2.1 Current structure hierarchy
....................................
-'struct tree_decl_minimal'
+`struct tree_decl_minimal'
This is the minimal structure to inherit from in order for common
- 'DECL' macros to work. The fields it contains are a unique ID,
+ `DECL' macros to work. The fields it contains are a unique ID,
source location, context, and name.
-'struct tree_decl_common'
- This structure inherits from 'struct tree_decl_minimal'. It
- contains fields that most 'DECL' nodes need, such as a field to
+`struct tree_decl_common'
+ This structure inherits from `struct tree_decl_minimal'. It
+ contains fields that most `DECL' nodes need, such as a field to
store alignment, machine mode, size, and attributes.
-'struct tree_field_decl'
- This structure inherits from 'struct tree_decl_common'. It is used
- to represent 'FIELD_DECL'.
+`struct tree_field_decl'
+ This structure inherits from `struct tree_decl_common'. It is
+ used to represent `FIELD_DECL'.
-'struct tree_label_decl'
- This structure inherits from 'struct tree_decl_common'. It is used
- to represent 'LABEL_DECL'.
+`struct tree_label_decl'
+ This structure inherits from `struct tree_decl_common'. It is
+ used to represent `LABEL_DECL'.
-'struct tree_translation_unit_decl'
- This structure inherits from 'struct tree_decl_common'. It is used
- to represent 'TRANSLATION_UNIT_DECL'.
+`struct tree_translation_unit_decl'
+ This structure inherits from `struct tree_decl_common'. It is
+ used to represent `TRANSLATION_UNIT_DECL'.
-'struct tree_decl_with_rtl'
- This structure inherits from 'struct tree_decl_common'. It
+`struct tree_decl_with_rtl'
+ This structure inherits from `struct tree_decl_common'. It
contains a field to store the low-level RTL associated with a
- 'DECL' node.
+ `DECL' node.
-'struct tree_result_decl'
- This structure inherits from 'struct tree_decl_with_rtl'. It is
- used to represent 'RESULT_DECL'.
+`struct tree_result_decl'
+ This structure inherits from `struct tree_decl_with_rtl'. It is
+ used to represent `RESULT_DECL'.
-'struct tree_const_decl'
- This structure inherits from 'struct tree_decl_with_rtl'. It is
- used to represent 'CONST_DECL'.
+`struct tree_const_decl'
+ This structure inherits from `struct tree_decl_with_rtl'. It is
+ used to represent `CONST_DECL'.
-'struct tree_parm_decl'
- This structure inherits from 'struct tree_decl_with_rtl'. It is
- used to represent 'PARM_DECL'.
+`struct tree_parm_decl'
+ This structure inherits from `struct tree_decl_with_rtl'. It is
+ used to represent `PARM_DECL'.
-'struct tree_decl_with_vis'
- This structure inherits from 'struct tree_decl_with_rtl'. It
+`struct tree_decl_with_vis'
+ This structure inherits from `struct tree_decl_with_rtl'. It
contains fields necessary to store visibility information, as well
as a section name and assembler name.
-'struct tree_var_decl'
- This structure inherits from 'struct tree_decl_with_vis'. It is
- used to represent 'VAR_DECL'.
+`struct tree_var_decl'
+ This structure inherits from `struct tree_decl_with_vis'. It is
+ used to represent `VAR_DECL'.
+
+`struct tree_function_decl'
+ This structure inherits from `struct tree_decl_with_vis'. It is
+ used to represent `FUNCTION_DECL'.
-'struct tree_function_decl'
- This structure inherits from 'struct tree_decl_with_vis'. It is
- used to represent 'FUNCTION_DECL'.

File: gccint.info, Node: Adding new DECL node types, Prev: Current structure hierarchy, Up: Internal structure
@@ -8262,77 +8418,76 @@ File: gccint.info, Node: Adding new DECL node types, Prev: Current structure h
10.4.2.2 Adding new DECL node types
...................................
-Adding a new 'DECL' tree consists of the following steps
+Adding a new `DECL' tree consists of the following steps
-Add a new tree code for the 'DECL' node
- For language specific 'DECL' nodes, there is a '.def' file in each
- frontend directory where the tree code should be added. For 'DECL'
- nodes that are part of the middle-end, the code should be added to
- 'tree.def'.
+Add a new tree code for the `DECL' node
+ For language specific `DECL' nodes, there is a `.def' file in each
+ frontend directory where the tree code should be added. For
+ `DECL' nodes that are part of the middle-end, the code should be
+ added to `tree.def'.
-Create a new structure type for the 'DECL' node
- These structures should inherit from one of the existing structures
- in the language hierarchy by using that structure as the first
- member.
+Create a new structure type for the `DECL' node
+ These structures should inherit from one of the existing
+ structures in the language hierarchy by using that structure as
+ the first member.
struct tree_foo_decl
{
struct tree_decl_with_vis common;
}
- Would create a structure name 'tree_foo_decl' that inherits from
- 'struct tree_decl_with_vis'.
+ Would create a structure name `tree_foo_decl' that inherits from
+ `struct tree_decl_with_vis'.
- For language specific 'DECL' nodes, this new structure type should
- go in the appropriate '.h' file. For 'DECL' nodes that are part of
- the middle-end, the structure type should go in 'tree.h'.
+ For language specific `DECL' nodes, this new structure type should
+ go in the appropriate `.h' file. For `DECL' nodes that are part
+ of the middle-end, the structure type should go in `tree.h'.
Add a member to the tree structure enumerator for the node
- For garbage collection and dynamic checking purposes, each 'DECL'
+ For garbage collection and dynamic checking purposes, each `DECL'
node structure type is required to have a unique enumerator value
- specified with it. For language specific 'DECL' nodes, this new
- enumerator value should go in the appropriate '.def' file. For
- 'DECL' nodes that are part of the middle-end, the enumerator values
- are specified in 'treestruct.def'.
+ specified with it. For language specific `DECL' nodes, this new
+ enumerator value should go in the appropriate `.def' file. For
+ `DECL' nodes that are part of the middle-end, the enumerator
+ values are specified in `treestruct.def'.
-Update 'union tree_node'
+Update `union tree_node'
In order to make your new structure type usable, it must be added
- to 'union tree_node'. For language specific 'DECL' nodes, a new
- entry should be added to the appropriate '.h' file of the form
+ to `union tree_node'. For language specific `DECL' nodes, a new
+ entry should be added to the appropriate `.h' file of the form
struct tree_foo_decl GTY ((tag ("TS_VAR_DECL"))) foo_decl;
- For 'DECL' nodes that are part of the middle-end, the additional
- member goes directly into 'union tree_node' in 'tree.h'.
+ For `DECL' nodes that are part of the middle-end, the additional
+ member goes directly into `union tree_node' in `tree.h'.
Update dynamic checking info
In order to be able to check whether accessing a named portion of
- 'union tree_node' is legal, and whether a certain 'DECL' node
- contains one of the enumerated 'DECL' node structures in the
+ `union tree_node' is legal, and whether a certain `DECL' node
+ contains one of the enumerated `DECL' node structures in the
hierarchy, a simple lookup table is used. This lookup table needs
to be kept up to date with the tree structure hierarchy, or else
checking and containment macros will fail inappropriately.
- For language specific 'DECL' nodes, their is an 'init_ts' function
- in an appropriate '.c' file, which initializes the lookup table.
- Code setting up the table for new 'DECL' nodes should be added
- there. For each 'DECL' tree code and enumerator value representing
- a member of the inheritance hierarchy, the table should contain 1
- if that tree code inherits (directly or indirectly) from that
- member. Thus, a 'FOO_DECL' node derived from 'struct
- decl_with_rtl', and enumerator value 'TS_FOO_DECL', would be set up
- as follows
+ For language specific `DECL' nodes, their is an `init_ts' function
+ in an appropriate `.c' file, which initializes the lookup table.
+ Code setting up the table for new `DECL' nodes should be added
+ there. For each `DECL' tree code and enumerator value
+ representing a member of the inheritance hierarchy, the table
+ should contain 1 if that tree code inherits (directly or
+ indirectly) from that member. Thus, a `FOO_DECL' node derived
+ from `struct decl_with_rtl', and enumerator value `TS_FOO_DECL',
+ would be set up as follows
tree_contains_struct[FOO_DECL][TS_FOO_DECL] = 1;
tree_contains_struct[FOO_DECL][TS_DECL_WRTL] = 1;
tree_contains_struct[FOO_DECL][TS_DECL_COMMON] = 1;
tree_contains_struct[FOO_DECL][TS_DECL_MINIMAL] = 1;
- For 'DECL' nodes that are part of the middle-end, the setup code
- goes into 'tree.c'.
+ For `DECL' nodes that are part of the middle-end, the setup code
+ goes into `tree.c'.
Add macros to access any new fields and flags
-
Each added field or flag should have a macro that is used to access
it, that performs appropriate checking to ensure only the right
- type of 'DECL' nodes access the field.
+ type of `DECL' nodes access the field.
These macros generally take the following form
#define FOO_DECL_FIELDNAME(NODE) FOO_DECL_CHECK(NODE)->foo_decl.fieldname
@@ -8342,9 +8497,10 @@ Add macros to access any new fields and flags
#define BASE_STRUCT_FIELDNAME(NODE) \
(BASE_STRUCT_CHECK(NODE)->base_struct.fieldname
- Reading them from the generated 'all-tree.def' file (which in turn
- includes all the 'tree.def' files), 'gencheck.c' is used during
- GCC's build to generate the '*_CHECK' macros for all tree codes.
+ Reading them from the generated `all-tree.def' file (which in turn
+ includes all the `tree.def' files), `gencheck.c' is used during
+ GCC's build to generate the `*_CHECK' macros for all tree codes.
+

File: gccint.info, Node: Attributes, Next: Expression trees, Prev: Declarations, Up: GENERIC
@@ -8352,15 +8508,15 @@ File: gccint.info, Node: Attributes, Next: Expression trees, Prev: Declaratio
10.5 Attributes in trees
========================
-Attributes, as specified using the '__attribute__' keyword, are
-represented internally as a 'TREE_LIST'. The 'TREE_PURPOSE' is the name
-of the attribute, as an 'IDENTIFIER_NODE'. The 'TREE_VALUE' is a
-'TREE_LIST' of the arguments of the attribute, if any, or 'NULL_TREE' if
-there are no arguments; the arguments are stored as the 'TREE_VALUE' of
-successive entries in the list, and may be identifiers or expressions.
-The 'TREE_CHAIN' of the attribute is the next attribute in a list of
-attributes applying to the same declaration or type, or 'NULL_TREE' if
-there are no further attributes in the list.
+Attributes, as specified using the `__attribute__' keyword, are
+represented internally as a `TREE_LIST'. The `TREE_PURPOSE' is the
+name of the attribute, as an `IDENTIFIER_NODE'. The `TREE_VALUE' is a
+`TREE_LIST' of the arguments of the attribute, if any, or `NULL_TREE'
+if there are no arguments; the arguments are stored as the `TREE_VALUE'
+of successive entries in the list, and may be identifiers or
+expressions. The `TREE_CHAIN' of the attribute is the next attribute
+in a list of attributes applying to the same declaration or type, or
+`NULL_TREE' if there are no further attributes in the list.
Attributes may be attached to declarations and to types; these
attributes may be accessed with the following macros. All attributes
@@ -8385,18 +8541,18 @@ mind. In particular, the expression "tree" is actually a directed
acyclic graph. (For example there may be many references to the integer
constant zero throughout the source program; many of these will be
represented by the same expression node.) You should not rely on
-certain kinds of node being shared, nor should you rely on certain kinds
-of nodes being unshared.
+certain kinds of node being shared, nor should you rely on certain
+kinds of nodes being unshared.
The following macros can be used with all expression nodes:
-'TREE_TYPE'
+`TREE_TYPE'
Returns the type of the expression. This value may not be
precisely the same type that would be given the expression in the
original program.
In what follows, some nodes that one might expect to always have type
-'bool' are documented to have either integral or boolean type. At some
+`bool' are documented to have either integral or boolean type. At some
point in the future, the C front end may also make use of this same
intermediate representation, and at this point these nodes will
certainly have integral type. The previous sentence is not meant to
@@ -8405,11 +8561,10 @@ integral type.
Below, we list the various kinds of expression nodes. Except where
noted otherwise, the operands to an expression are accessed using the
-'TREE_OPERAND' macro. For example, to access the first operand to a
-binary plus expression 'expr', use:
+`TREE_OPERAND' macro. For example, to access the first operand to a
+binary plus expression `expr', use:
TREE_OPERAND (expr, 0)
-
As this example indicates, the operands are zero-indexed.
* Menu:
@@ -8429,75 +8584,76 @@ The table below begins with constants, moves on to unary expressions,
then proceeds to binary expressions, and concludes with various other
kinds of expressions:
-'INTEGER_CST'
+`INTEGER_CST'
These nodes represent integer constants. Note that the type of
- these constants is obtained with 'TREE_TYPE'; they are not always
- of type 'int'. In particular, 'char' constants are represented
- with 'INTEGER_CST' nodes. The value of the integer constant 'e' is
- represented in an array of HOST_WIDE_INT. There are enough elements
- in the array to represent the value without taking extra elements
- for redundant 0s or -1. The number of elements used to represent
- 'e' is available via 'TREE_INT_CST_NUNITS'. Element 'i' can be
- extracted by using 'TREE_INT_CST_ELT (e, i)'. 'TREE_INT_CST_LOW'
- is a shorthand for 'TREE_INT_CST_ELT (e, 0)'.
-
- The functions 'tree_fits_shwi_p' and 'tree_fits_uhwi_p' can be used
- to tell if the value is small enough to fit in a signed
- HOST_WIDE_INT or an unsigned HOST_WIDE_INT respectively. The value
- can then be extracted using 'tree_to_shwi' and 'tree_to_uhwi'.
-
-'REAL_CST'
-
+ these constants is obtained with `TREE_TYPE'; they are not always
+ of type `int'. In particular, `char' constants are represented
+ with `INTEGER_CST' nodes. The value of the integer constant `e' is
+ represented in an array of HOST_WIDE_INT. There are enough
+ elements in the array to represent the value without taking extra
+ elements for redundant 0s or -1. The number of elements used to
+ represent `e' is available via `TREE_INT_CST_NUNITS'. Element `i'
+ can be extracted by using `TREE_INT_CST_ELT (e, i)'.
+ `TREE_INT_CST_LOW' is a shorthand for `TREE_INT_CST_ELT (e, 0)'.
+
+ The functions `tree_fits_shwi_p' and `tree_fits_uhwi_p' can be
+ used to tell if the value is small enough to fit in a signed
+ HOST_WIDE_INT or an unsigned HOST_WIDE_INT respectively. The
+ value can then be extracted using `tree_to_shwi' and
+ `tree_to_uhwi'.
+
+`REAL_CST'
FIXME: Talk about how to obtain representations of this constant,
do comparisons, and so forth.
-'FIXED_CST'
-
+`FIXED_CST'
These nodes represent fixed-point constants. The type of these
- constants is obtained with 'TREE_TYPE'. 'TREE_FIXED_CST_PTR'
- points to a 'struct fixed_value'; 'TREE_FIXED_CST' returns the
- structure itself. 'struct fixed_value' contains 'data' with the
- size of two 'HOST_BITS_PER_WIDE_INT' and 'mode' as the associated
- fixed-point machine mode for 'data'.
-
-'COMPLEX_CST'
- These nodes are used to represent complex number constants, that is
- a '__complex__' whose parts are constant nodes. The
- 'TREE_REALPART' and 'TREE_IMAGPART' return the real and the
+ constants is obtained with `TREE_TYPE'. `TREE_FIXED_CST_PTR'
+ points to a `struct fixed_value'; `TREE_FIXED_CST' returns the
+ structure itself. `struct fixed_value' contains `data' with the
+ size of two `HOST_BITS_PER_WIDE_INT' and `mode' as the associated
+ fixed-point machine mode for `data'.
+
+`COMPLEX_CST'
+ These nodes are used to represent complex number constants, that
+ is a `__complex__' whose parts are constant nodes. The
+ `TREE_REALPART' and `TREE_IMAGPART' return the real and the
imaginary parts respectively.
-'VECTOR_CST'
+`VECTOR_CST'
These nodes are used to represent vector constants, whose parts are
- constant nodes. Each individual constant node is either an integer
- or a double constant node. The first operand is a 'TREE_LIST' of
- the constant nodes and is accessed through 'TREE_VECTOR_CST_ELTS'.
-
-'STRING_CST'
- These nodes represent string-constants. The 'TREE_STRING_LENGTH'
- returns the length of the string, as an 'int'. The
- 'TREE_STRING_POINTER' is a 'char*' containing the string itself.
- The string may not be 'NUL'-terminated, and it may contain embedded
- 'NUL' characters. Therefore, the 'TREE_STRING_LENGTH' includes the
- trailing 'NUL' if it is present.
-
- For wide string constants, the 'TREE_STRING_LENGTH' is the number
- of bytes in the string, and the 'TREE_STRING_POINTER' points to an
+ constant nodes. Each individual constant node is either an
+ integer or a double constant node. The first operand is a
+ `TREE_LIST' of the constant nodes and is accessed through
+ `TREE_VECTOR_CST_ELTS'.
+
+`STRING_CST'
+ These nodes represent string-constants. The `TREE_STRING_LENGTH'
+ returns the length of the string, as an `int'. The
+ `TREE_STRING_POINTER' is a `char*' containing the string itself.
+ The string may not be `NUL'-terminated, and it may contain
+ embedded `NUL' characters. Therefore, the `TREE_STRING_LENGTH'
+ includes the trailing `NUL' if it is present.
+
+ For wide string constants, the `TREE_STRING_LENGTH' is the number
+ of bytes in the string, and the `TREE_STRING_POINTER' points to an
array of the bytes of the string, as represented on the target
system (that is, as integers in the target endianness). Wide and
- non-wide string constants are distinguished only by the 'TREE_TYPE'
- of the 'STRING_CST'.
+ non-wide string constants are distinguished only by the `TREE_TYPE'
+ of the `STRING_CST'.
FIXME: The formats of string constants are not well-defined when
the target system bytes are not the same width as host system
bytes.
+

File: gccint.info, Node: Storage References, Next: Unary and Binary Expressions, Prev: Constant expressions, Up: Expression trees
10.6.2 References to storage
----------------------------
-'ARRAY_REF'
+`ARRAY_REF'
These nodes represent array accesses. The first operand is the
array; the second is the index. To calculate the address of the
memory accessed, you must scale the index by the size of the type
@@ -8505,64 +8661,65 @@ File: gccint.info, Node: Storage References, Next: Unary and Binary Expression
type of a component of the array. The third and fourth operands
are used after gimplification to represent the lower bound and
component size but should not be used directly; call
- 'array_ref_low_bound' and 'array_ref_element_size' instead.
+ `array_ref_low_bound' and `array_ref_element_size' instead.
-'ARRAY_RANGE_REF'
+`ARRAY_RANGE_REF'
These nodes represent access to a range (or "slice") of an array.
- The operands are the same as that for 'ARRAY_REF' and have the same
+ The operands are the same as that for `ARRAY_REF' and have the same
meanings. The type of these expressions must be an array whose
- component type is the same as that of the first operand. The range
- of that array type determines the amount of data these expressions
- access.
+ component type is the same as that of the first operand. The
+ range of that array type determines the amount of data these
+ expressions access.
-'TARGET_MEM_REF'
+`TARGET_MEM_REF'
These nodes represent memory accesses whose address directly map to
an addressing mode of the target architecture. The first argument
- is 'TMR_SYMBOL' and must be a 'VAR_DECL' of an object with a fixed
- address. The second argument is 'TMR_BASE' and the third one is
- 'TMR_INDEX'. The fourth argument is 'TMR_STEP' and must be an
- 'INTEGER_CST'. The fifth argument is 'TMR_OFFSET' and must be an
- 'INTEGER_CST'. Any of the arguments may be NULL if the appropriate
- component does not appear in the address. Address of the
- 'TARGET_MEM_REF' is determined in the following way.
+ is `TMR_SYMBOL' and must be a `VAR_DECL' of an object with a fixed
+ address. The second argument is `TMR_BASE' and the third one is
+ `TMR_INDEX'. The fourth argument is `TMR_STEP' and must be an
+ `INTEGER_CST'. The fifth argument is `TMR_OFFSET' and must be an
+ `INTEGER_CST'. Any of the arguments may be NULL if the
+ appropriate component does not appear in the address. Address of
+ the `TARGET_MEM_REF' is determined in the following way.
&TMR_SYMBOL + TMR_BASE + TMR_INDEX * TMR_STEP + TMR_OFFSET
The sixth argument is the reference to the original memory access,
- which is preserved for the purposes of the RTL alias analysis. The
- seventh argument is a tag representing the results of tree level
- alias analysis.
+ which is preserved for the purposes of the RTL alias analysis.
+ The seventh argument is a tag representing the results of tree
+ level alias analysis.
-'ADDR_EXPR'
+`ADDR_EXPR'
These nodes are used to represent the address of an object. (These
expressions will always have pointer or reference type.) The
operand may be another expression, or it may be a declaration.
As an extension, GCC allows users to take the address of a label.
- In this case, the operand of the 'ADDR_EXPR' will be a
- 'LABEL_DECL'. The type of such an expression is 'void*'.
+ In this case, the operand of the `ADDR_EXPR' will be a
+ `LABEL_DECL'. The type of such an expression is `void*'.
If the object addressed is not an lvalue, a temporary is created,
and the address of the temporary is used.
-'INDIRECT_REF'
+`INDIRECT_REF'
These nodes are used to represent the object pointed to by a
pointer. The operand is the pointer being dereferenced; it will
always have pointer or reference type.
-'MEM_REF'
+`MEM_REF'
These nodes are used to represent the object pointed to by a
pointer offset by a constant. The first operand is the pointer
being dereferenced; it will always have pointer or reference type.
The second operand is a pointer constant. Its type is specifying
the type to be used for type-based alias analysis.
-'COMPONENT_REF'
+`COMPONENT_REF'
These nodes represent non-static data member accesses. The first
operand is the object (rather than a pointer to it); the second
- operand is the 'FIELD_DECL' for the data member. The third operand
- represents the byte offset of the field, but should not be used
- directly; call 'component_ref_field_offset' instead.
+ operand is the `FIELD_DECL' for the data member. The third
+ operand represents the byte offset of the field, but should not be
+ used directly; call `component_ref_field_offset' instead.
+

File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: Storage References, Up: Expression trees
@@ -8570,160 +8727,160 @@ File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: S
10.6.3 Unary and Binary Expressions
-----------------------------------
-'NEGATE_EXPR'
+`NEGATE_EXPR'
These nodes represent unary negation of the single operand, for
both integer and floating-point types. The type of negation can be
determined by looking at the type of the expression.
The behavior of this operation on signed arithmetic overflow is
- controlled by the 'flag_wrapv' and 'flag_trapv' variables.
+ controlled by the `flag_wrapv' and `flag_trapv' variables.
-'ABS_EXPR'
+`ABS_EXPR'
These nodes represent the absolute value of the single operand, for
both integer and floating-point types. This is typically used to
- implement the 'abs', 'labs' and 'llabs' builtins for integer types,
- and the 'fabs', 'fabsf' and 'fabsl' builtins for floating point
- types. The type of abs operation can be determined by looking at
- the type of the expression.
+ implement the `abs', `labs' and `llabs' builtins for integer
+ types, and the `fabs', `fabsf' and `fabsl' builtins for floating
+ point types. The type of abs operation can be determined by
+ looking at the type of the expression.
This node is not used for complex types. To represent the modulus
- or complex abs of a complex value, use the 'BUILT_IN_CABS',
- 'BUILT_IN_CABSF' or 'BUILT_IN_CABSL' builtins, as used to implement
- the C99 'cabs', 'cabsf' and 'cabsl' built-in functions.
+ or complex abs of a complex value, use the `BUILT_IN_CABS',
+ `BUILT_IN_CABSF' or `BUILT_IN_CABSL' builtins, as used to
+ implement the C99 `cabs', `cabsf' and `cabsl' built-in functions.
-'BIT_NOT_EXPR'
+`BIT_NOT_EXPR'
These nodes represent bitwise complement, and will always have
integral type. The only operand is the value to be complemented.
-'TRUTH_NOT_EXPR'
+`TRUTH_NOT_EXPR'
These nodes represent logical negation, and will always have
integral (or boolean) type. The operand is the value being
- negated. The type of the operand and that of the result are always
- of 'BOOLEAN_TYPE' or 'INTEGER_TYPE'.
+ negated. The type of the operand and that of the result are
+ always of `BOOLEAN_TYPE' or `INTEGER_TYPE'.
-'PREDECREMENT_EXPR'
-'PREINCREMENT_EXPR'
-'POSTDECREMENT_EXPR'
-'POSTINCREMENT_EXPR'
+`PREDECREMENT_EXPR'
+`PREINCREMENT_EXPR'
+`POSTDECREMENT_EXPR'
+`POSTINCREMENT_EXPR'
These nodes represent increment and decrement expressions. The
value of the single operand is computed, and the operand
- incremented or decremented. In the case of 'PREDECREMENT_EXPR' and
- 'PREINCREMENT_EXPR', the value of the expression is the value
+ incremented or decremented. In the case of `PREDECREMENT_EXPR' and
+ `PREINCREMENT_EXPR', the value of the expression is the value
resulting after the increment or decrement; in the case of
- 'POSTDECREMENT_EXPR' and 'POSTINCREMENT_EXPR' is the value before
+ `POSTDECREMENT_EXPR' and `POSTINCREMENT_EXPR' is the value before
the increment or decrement occurs. The type of the operand, like
that of the result, will be either integral, boolean, or
floating-point.
-'FIX_TRUNC_EXPR'
+`FIX_TRUNC_EXPR'
These nodes represent conversion of a floating-point value to an
integer. The single operand will have a floating-point type, while
the complete expression will have an integral (or boolean) type.
The operand is rounded towards zero.
-'FLOAT_EXPR'
+`FLOAT_EXPR'
These nodes represent conversion of an integral (or boolean) value
to a floating-point value. The single operand will have integral
type, while the complete expression will have a floating-point
type.
FIXME: How is the operand supposed to be rounded? Is this
- dependent on '-mieee'?
+ dependent on `-mieee'?
-'COMPLEX_EXPR'
+`COMPLEX_EXPR'
These nodes are used to represent complex numbers constructed from
two expressions of the same (integer or real) type. The first
operand is the real part and the second operand is the imaginary
part.
-'CONJ_EXPR'
+`CONJ_EXPR'
These nodes represent the conjugate of their operand.
-'REALPART_EXPR'
-'IMAGPART_EXPR'
+`REALPART_EXPR'
+`IMAGPART_EXPR'
These nodes represent respectively the real and the imaginary parts
of complex numbers (their sole argument).
-'NON_LVALUE_EXPR'
+`NON_LVALUE_EXPR'
These nodes indicate that their one and only operand is not an
lvalue. A back end can treat these identically to the single
operand.
-'NOP_EXPR'
+`NOP_EXPR'
These nodes are used to represent conversions that do not require
- any code-generation. For example, conversion of a 'char*' to an
- 'int*' does not require any code be generated; such a conversion is
- represented by a 'NOP_EXPR'. The single operand is the expression
+ any code-generation. For example, conversion of a `char*' to an
+ `int*' does not require any code be generated; such a conversion is
+ represented by a `NOP_EXPR'. The single operand is the expression
to be converted. The conversion from a pointer to a reference is
- also represented with a 'NOP_EXPR'.
+ also represented with a `NOP_EXPR'.
-'CONVERT_EXPR'
- These nodes are similar to 'NOP_EXPR's, but are used in those
+`CONVERT_EXPR'
+ These nodes are similar to `NOP_EXPR's, but are used in those
situations where code may need to be generated. For example, if an
- 'int*' is converted to an 'int' code may need to be generated on
+ `int*' is converted to an `int' code may need to be generated on
some platforms. These nodes are never used for C++-specific
- conversions, like conversions between pointers to different classes
- in an inheritance hierarchy. Any adjustments that need to be made
- in such cases are always indicated explicitly. Similarly, a
- user-defined conversion is never represented by a 'CONVERT_EXPR';
- instead, the function calls are made explicit.
+ conversions, like conversions between pointers to different
+ classes in an inheritance hierarchy. Any adjustments that need to
+ be made in such cases are always indicated explicitly. Similarly,
+ a user-defined conversion is never represented by a
+ `CONVERT_EXPR'; instead, the function calls are made explicit.
-'FIXED_CONVERT_EXPR'
+`FIXED_CONVERT_EXPR'
These nodes are used to represent conversions that involve
fixed-point values. For example, from a fixed-point value to
another fixed-point value, from an integer to a fixed-point value,
- from a fixed-point value to an integer, from a floating-point value
- to a fixed-point value, or from a fixed-point value to a
+ from a fixed-point value to an integer, from a floating-point
+ value to a fixed-point value, or from a fixed-point value to a
floating-point value.
-'LSHIFT_EXPR'
-'RSHIFT_EXPR'
+`LSHIFT_EXPR'
+`RSHIFT_EXPR'
These nodes represent left and right shifts, respectively. The
first operand is the value to shift; it will always be of integral
type. The second operand is an expression for the number of bits
by which to shift. Right shift should be treated as arithmetic,
- i.e., the high-order bits should be zero-filled when the expression
- has unsigned type and filled with the sign bit when the expression
- has signed type. Note that the result is undefined if the second
- operand is larger than or equal to the first operand's type size.
- Unlike most nodes, these can have a vector as first operand and a
- scalar as second operand.
-
-'BIT_IOR_EXPR'
-'BIT_XOR_EXPR'
-'BIT_AND_EXPR'
+ i.e., the high-order bits should be zero-filled when the
+ expression has unsigned type and filled with the sign bit when the
+ expression has signed type. Note that the result is undefined if
+ the second operand is larger than or equal to the first operand's
+ type size. Unlike most nodes, these can have a vector as first
+ operand and a scalar as second operand.
+
+`BIT_IOR_EXPR'
+`BIT_XOR_EXPR'
+`BIT_AND_EXPR'
These nodes represent bitwise inclusive or, bitwise exclusive or,
and bitwise and, respectively. Both operands will always have
integral type.
-'TRUTH_ANDIF_EXPR'
-'TRUTH_ORIF_EXPR'
+`TRUTH_ANDIF_EXPR'
+`TRUTH_ORIF_EXPR'
These nodes represent logical "and" and logical "or", respectively.
These operators are not strict; i.e., the second operand is
evaluated only if the value of the expression is not determined by
- evaluation of the first operand. The type of the operands and that
- of the result are always of 'BOOLEAN_TYPE' or 'INTEGER_TYPE'.
+ evaluation of the first operand. The type of the operands and
+ that of the result are always of `BOOLEAN_TYPE' or `INTEGER_TYPE'.
-'TRUTH_AND_EXPR'
-'TRUTH_OR_EXPR'
-'TRUTH_XOR_EXPR'
+`TRUTH_AND_EXPR'
+`TRUTH_OR_EXPR'
+`TRUTH_XOR_EXPR'
These nodes represent logical and, logical or, and logical
exclusive or. They are strict; both arguments are always
evaluated. There are no corresponding operators in C or C++, but
the front end will sometimes generate these expressions anyhow, if
it can tell that strictness does not matter. The type of the
- operands and that of the result are always of 'BOOLEAN_TYPE' or
- 'INTEGER_TYPE'.
+ operands and that of the result are always of `BOOLEAN_TYPE' or
+ `INTEGER_TYPE'.
-'POINTER_PLUS_EXPR'
+`POINTER_PLUS_EXPR'
This node represents pointer arithmetic. The first operand is
always a pointer/reference type. The second operand is always an
unsigned integer type compatible with sizetype. This is the only
binary arithmetic operand that can operate on pointer types.
-'PLUS_EXPR'
-'MINUS_EXPR'
-'MULT_EXPR'
+`PLUS_EXPR'
+`MINUS_EXPR'
+`MULT_EXPR'
These nodes represent various binary arithmetic operations.
Respectively, these operations are addition, subtraction (of the
second operand from the first) and multiplication. Their operands
@@ -8732,74 +8889,74 @@ File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: S
integral type.
The behavior of these operations on signed arithmetic overflow is
- controlled by the 'flag_wrapv' and 'flag_trapv' variables.
+ controlled by the `flag_wrapv' and `flag_trapv' variables.
-'MULT_HIGHPART_EXPR'
+`MULT_HIGHPART_EXPR'
This node represents the "high-part" of a widening multiplication.
For an integral type with B bits of precision, the result is the
most significant B bits of the full 2B product.
-'RDIV_EXPR'
+`RDIV_EXPR'
This node represents a floating point division operation.
-'TRUNC_DIV_EXPR'
-'FLOOR_DIV_EXPR'
-'CEIL_DIV_EXPR'
-'ROUND_DIV_EXPR'
+`TRUNC_DIV_EXPR'
+`FLOOR_DIV_EXPR'
+`CEIL_DIV_EXPR'
+`ROUND_DIV_EXPR'
These nodes represent integer division operations that return an
- integer result. 'TRUNC_DIV_EXPR' rounds towards zero,
- 'FLOOR_DIV_EXPR' rounds towards negative infinity, 'CEIL_DIV_EXPR'
- rounds towards positive infinity and 'ROUND_DIV_EXPR' rounds to the
- closest integer. Integer division in C and C++ is truncating, i.e.
- 'TRUNC_DIV_EXPR'.
+ integer result. `TRUNC_DIV_EXPR' rounds towards zero,
+ `FLOOR_DIV_EXPR' rounds towards negative infinity, `CEIL_DIV_EXPR'
+ rounds towards positive infinity and `ROUND_DIV_EXPR' rounds to
+ the closest integer. Integer division in C and C++ is truncating,
+ i.e. `TRUNC_DIV_EXPR'.
The behavior of these operations on signed arithmetic overflow,
when dividing the minimum signed integer by minus one, is
- controlled by the 'flag_wrapv' and 'flag_trapv' variables.
+ controlled by the `flag_wrapv' and `flag_trapv' variables.
-'TRUNC_MOD_EXPR'
-'FLOOR_MOD_EXPR'
-'CEIL_MOD_EXPR'
-'ROUND_MOD_EXPR'
+`TRUNC_MOD_EXPR'
+`FLOOR_MOD_EXPR'
+`CEIL_MOD_EXPR'
+`ROUND_MOD_EXPR'
These nodes represent the integer remainder or modulus operation.
- The integer modulus of two operands 'a' and 'b' is defined as 'a -
+ The integer modulus of two operands `a' and `b' is defined as `a -
(a/b)*b' where the division calculated using the corresponding
- division operator. Hence for 'TRUNC_MOD_EXPR' this definition
+ division operator. Hence for `TRUNC_MOD_EXPR' this definition
assumes division using truncation towards zero, i.e.
- 'TRUNC_DIV_EXPR'. Integer remainder in C and C++ uses truncating
- division, i.e. 'TRUNC_MOD_EXPR'.
+ `TRUNC_DIV_EXPR'. Integer remainder in C and C++ uses truncating
+ division, i.e. `TRUNC_MOD_EXPR'.
-'EXACT_DIV_EXPR'
- The 'EXACT_DIV_EXPR' code is used to represent integer divisions
+`EXACT_DIV_EXPR'
+ The `EXACT_DIV_EXPR' code is used to represent integer divisions
where the numerator is known to be an exact multiple of the
denominator. This allows the backend to choose between the faster
- of 'TRUNC_DIV_EXPR', 'CEIL_DIV_EXPR' and 'FLOOR_DIV_EXPR' for the
+ of `TRUNC_DIV_EXPR', `CEIL_DIV_EXPR' and `FLOOR_DIV_EXPR' for the
current target.
-'LT_EXPR'
-'LE_EXPR'
-'GT_EXPR'
-'GE_EXPR'
-'EQ_EXPR'
-'NE_EXPR'
+`LT_EXPR'
+`LE_EXPR'
+`GT_EXPR'
+`GE_EXPR'
+`EQ_EXPR'
+`NE_EXPR'
These nodes represent the less than, less than or equal to, greater
than, greater than or equal to, equal, and not equal comparison
operators. The first and second operands will either be both of
integral type, both of floating type or both of vector type. The
result type of these expressions will always be of integral,
boolean or signed integral vector type. These operations return
- the result type's zero value for false, the result type's one value
- for true, and a vector whose elements are zero (false) or minus one
- (true) for vectors.
+ the result type's zero value for false, the result type's one
+ value for true, and a vector whose elements are zero (false) or
+ minus one (true) for vectors.
For floating point comparisons, if we honor IEEE NaNs and either
- operand is NaN, then 'NE_EXPR' always returns true and the
+ operand is NaN, then `NE_EXPR' always returns true and the
remaining operators always return false. On some targets,
comparisons against an IEEE NaN, other than equality and
inequality, may generate a floating point exception.
-'ORDERED_EXPR'
-'UNORDERED_EXPR'
+`ORDERED_EXPR'
+`UNORDERED_EXPR'
These nodes represent non-trapping ordered and unordered comparison
operators. These operations take two floating point operands and
determine whether they are ordered or unordered relative to each
@@ -8810,50 +8967,50 @@ File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: S
type's zero value for false, and the result type's one value for
true.
-'UNLT_EXPR'
-'UNLE_EXPR'
-'UNGT_EXPR'
-'UNGE_EXPR'
-'UNEQ_EXPR'
-'LTGT_EXPR'
+`UNLT_EXPR'
+`UNLE_EXPR'
+`UNGT_EXPR'
+`UNGE_EXPR'
+`UNEQ_EXPR'
+`LTGT_EXPR'
These nodes represent the unordered comparison operators. These
operations take two floating point operands and determine whether
the operands are unordered or are less than, less than or equal to,
greater than, greater than or equal to, or equal respectively. For
- example, 'UNLT_EXPR' returns true if either operand is an IEEE NaN
+ example, `UNLT_EXPR' returns true if either operand is an IEEE NaN
or the first operand is less than the second. With the possible
- exception of 'LTGT_EXPR', all of these operations are guaranteed
+ exception of `LTGT_EXPR', all of these operations are guaranteed
not to generate a floating point exception. The result type of
these expressions will always be of integral or boolean type.
- These operations return the result type's zero value for false, and
- the result type's one value for true.
+ These operations return the result type's zero value for false,
+ and the result type's one value for true.
-'MODIFY_EXPR'
+`MODIFY_EXPR'
These nodes represent assignment. The left-hand side is the first
operand; the right-hand side is the second operand. The left-hand
- side will be a 'VAR_DECL', 'INDIRECT_REF', 'COMPONENT_REF', or
+ side will be a `VAR_DECL', `INDIRECT_REF', `COMPONENT_REF', or
other lvalue.
- These nodes are used to represent not only assignment with '=' but
- also compound assignments (like '+='), by reduction to '='
- assignment. In other words, the representation for 'i += 3' looks
- just like that for 'i = i + 3'.
+ These nodes are used to represent not only assignment with `=' but
+ also compound assignments (like `+='), by reduction to `='
+ assignment. In other words, the representation for `i += 3' looks
+ just like that for `i = i + 3'.
-'INIT_EXPR'
- These nodes are just like 'MODIFY_EXPR', but are used only when a
+`INIT_EXPR'
+ These nodes are just like `MODIFY_EXPR', but are used only when a
variable is initialized, rather than assigned to subsequently.
- This means that we can assume that the target of the initialization
- is not used in computing its own value; any reference to the lhs in
- computing the rhs is undefined.
+ This means that we can assume that the target of the
+ initialization is not used in computing its own value; any
+ reference to the lhs in computing the rhs is undefined.
-'COMPOUND_EXPR'
+`COMPOUND_EXPR'
These nodes represent comma-expressions. The first operand is an
expression whose value is computed and thrown away prior to the
evaluation of the second operand. The value of the entire
expression is the value of the second operand.
-'COND_EXPR'
- These nodes represent '?:' expressions. The first operand is of
+`COND_EXPR'
+ These nodes represent `?:' expressions. The first operand is of
boolean or integral type. If it evaluates to a nonzero value, the
second operand should be evaluated, and returned as the value of
the expression. Otherwise, the third operand is evaluated, and
@@ -8863,32 +9020,33 @@ File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: S
expression, unless it unconditionally throws an exception or calls
a noreturn function, in which case it should have void type. The
same constraints apply to the third operand. This allows array
- bounds checks to be represented conveniently as '(i >= 0 && i < 10)
- ? i : abort()'.
+ bounds checks to be represented conveniently as `(i >= 0 && i <
+ 10) ? i : abort()'.
As a GNU extension, the C language front-ends allow the second
- operand of the '?:' operator may be omitted in the source. For
- example, 'x ? : 3' is equivalent to 'x ? x : 3', assuming that 'x'
- is an expression without side-effects. In the tree representation,
- however, the second operand is always present, possibly protected
- by 'SAVE_EXPR' if the first argument does cause side-effects.
-
-'CALL_EXPR'
+ operand of the `?:' operator may be omitted in the source. For
+ example, `x ? : 3' is equivalent to `x ? x : 3', assuming that `x'
+ is an expression without side-effects. In the tree
+ representation, however, the second operand is always present,
+ possibly protected by `SAVE_EXPR' if the first argument does cause
+ side-effects.
+
+`CALL_EXPR'
These nodes are used to represent calls to functions, including
- non-static member functions. 'CALL_EXPR's are implemented as
+ non-static member functions. `CALL_EXPR's are implemented as
expression nodes with a variable number of operands. Rather than
- using 'TREE_OPERAND' to extract them, it is preferable to use the
- specialized accessor macros and functions that operate specifically
- on 'CALL_EXPR' nodes.
+ using `TREE_OPERAND' to extract them, it is preferable to use the
+ specialized accessor macros and functions that operate
+ specifically on `CALL_EXPR' nodes.
- 'CALL_EXPR_FN' returns a pointer to the function to call; it is
- always an expression whose type is a 'POINTER_TYPE'.
+ `CALL_EXPR_FN' returns a pointer to the function to call; it is
+ always an expression whose type is a `POINTER_TYPE'.
The number of arguments to the call is returned by
- 'call_expr_nargs', while the arguments themselves can be accessed
- with the 'CALL_EXPR_ARG' macro. The arguments are zero-indexed and
- numbered left-to-right. You can iterate over the arguments using
- 'FOR_EACH_CALL_EXPR_ARG', as in:
+ `call_expr_nargs', while the arguments themselves can be accessed
+ with the `CALL_EXPR_ARG' macro. The arguments are zero-indexed
+ and numbered left-to-right. You can iterate over the arguments
+ using `FOR_EACH_CALL_EXPR_ARG', as in:
tree call, arg;
call_expr_arg_iterator iter;
@@ -8897,104 +9055,103 @@ File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: S
...;
For non-static member functions, there will be an operand
- corresponding to the 'this' pointer. There will always be
+ corresponding to the `this' pointer. There will always be
expressions corresponding to all of the arguments, even if the
function is declared with default arguments and some arguments are
not explicitly provided at the call sites.
- 'CALL_EXPR's also have a 'CALL_EXPR_STATIC_CHAIN' operand that is
+ `CALL_EXPR's also have a `CALL_EXPR_STATIC_CHAIN' operand that is
used to implement nested functions. This operand is otherwise
null.
-'CLEANUP_POINT_EXPR'
+`CLEANUP_POINT_EXPR'
These nodes represent full-expressions. The single operand is an
expression to evaluate. Any destructor calls engendered by the
creation of temporaries during the evaluation of that expression
should be performed immediately after the expression is evaluated.
-'CONSTRUCTOR'
+`CONSTRUCTOR'
These nodes represent the brace-enclosed initializers for a
- structure or an array. They contain a sequence of component values
- made out of a vector of constructor_elt, which is a ('INDEX',
- 'VALUE') pair.
+ structure or an array. They contain a sequence of component
+ values made out of a vector of constructor_elt, which is a
+ (`INDEX', `VALUE') pair.
- If the 'TREE_TYPE' of the 'CONSTRUCTOR' is a 'RECORD_TYPE',
- 'UNION_TYPE' or 'QUAL_UNION_TYPE' then the 'INDEX' of each node in
- the sequence will be a 'FIELD_DECL' and the 'VALUE' will be the
+ If the `TREE_TYPE' of the `CONSTRUCTOR' is a `RECORD_TYPE',
+ `UNION_TYPE' or `QUAL_UNION_TYPE' then the `INDEX' of each node in
+ the sequence will be a `FIELD_DECL' and the `VALUE' will be the
expression used to initialize that field.
- If the 'TREE_TYPE' of the 'CONSTRUCTOR' is an 'ARRAY_TYPE', then
- the 'INDEX' of each node in the sequence will be an 'INTEGER_CST'
- or a 'RANGE_EXPR' of two 'INTEGER_CST's. A single 'INTEGER_CST'
+ If the `TREE_TYPE' of the `CONSTRUCTOR' is an `ARRAY_TYPE', then
+ the `INDEX' of each node in the sequence will be an `INTEGER_CST'
+ or a `RANGE_EXPR' of two `INTEGER_CST's. A single `INTEGER_CST'
indicates which element of the array is being assigned to. A
- 'RANGE_EXPR' indicates an inclusive range of elements to
- initialize. In both cases the 'VALUE' is the corresponding
+ `RANGE_EXPR' indicates an inclusive range of elements to
+ initialize. In both cases the `VALUE' is the corresponding
initializer. It is re-evaluated for each element of a
- 'RANGE_EXPR'. If the 'INDEX' is 'NULL_TREE', then the initializer
+ `RANGE_EXPR'. If the `INDEX' is `NULL_TREE', then the initializer
is for the next available array element.
In the front end, you should not depend on the fields appearing in
any particular order. However, in the middle end, fields must
- appear in declaration order. You should not assume that all fields
- will be represented. Unrepresented fields will be cleared
+ appear in declaration order. You should not assume that all
+ fields will be represented. Unrepresented fields will be cleared
(zeroed), unless the CONSTRUCTOR_NO_CLEARING flag is set, in which
case their value becomes undefined.
-'COMPOUND_LITERAL_EXPR'
+`COMPOUND_LITERAL_EXPR'
These nodes represent ISO C99 compound literals. The
- 'COMPOUND_LITERAL_EXPR_DECL_EXPR' is a 'DECL_EXPR' containing an
- anonymous 'VAR_DECL' for the unnamed object represented by the
- compound literal; the 'DECL_INITIAL' of that 'VAR_DECL' is a
- 'CONSTRUCTOR' representing the brace-enclosed list of initializers
- in the compound literal. That anonymous 'VAR_DECL' can also be
- accessed directly by the 'COMPOUND_LITERAL_EXPR_DECL' macro.
-
-'SAVE_EXPR'
-
- A 'SAVE_EXPR' represents an expression (possibly involving
+ `COMPOUND_LITERAL_EXPR_DECL_EXPR' is a `DECL_EXPR' containing an
+ anonymous `VAR_DECL' for the unnamed object represented by the
+ compound literal; the `DECL_INITIAL' of that `VAR_DECL' is a
+ `CONSTRUCTOR' representing the brace-enclosed list of initializers
+ in the compound literal. That anonymous `VAR_DECL' can also be
+ accessed directly by the `COMPOUND_LITERAL_EXPR_DECL' macro.
+
+`SAVE_EXPR'
+ A `SAVE_EXPR' represents an expression (possibly involving
side-effects) that is used more than once. The side-effects should
occur only the first time the expression is evaluated. Subsequent
uses should just reuse the computed value. The first operand to
- the 'SAVE_EXPR' is the expression to evaluate. The side-effects
- should be executed where the 'SAVE_EXPR' is first encountered in a
+ the `SAVE_EXPR' is the expression to evaluate. The side-effects
+ should be executed where the `SAVE_EXPR' is first encountered in a
depth-first preorder traversal of the expression tree.
-'TARGET_EXPR'
- A 'TARGET_EXPR' represents a temporary object. The first operand
- is a 'VAR_DECL' for the temporary variable. The second operand is
+`TARGET_EXPR'
+ A `TARGET_EXPR' represents a temporary object. The first operand
+ is a `VAR_DECL' for the temporary variable. The second operand is
the initializer for the temporary. The initializer is evaluated
and, if non-void, copied (bitwise) into the temporary. If the
initializer is void, that means that it will perform the
initialization itself.
- Often, a 'TARGET_EXPR' occurs on the right-hand side of an
+ Often, a `TARGET_EXPR' occurs on the right-hand side of an
assignment, or as the second operand to a comma-expression which is
- itself the right-hand side of an assignment, etc. In this case, we
- say that the 'TARGET_EXPR' is "normal"; otherwise, we say it is
- "orphaned". For a normal 'TARGET_EXPR' the temporary variable
+ itself the right-hand side of an assignment, etc. In this case,
+ we say that the `TARGET_EXPR' is "normal"; otherwise, we say it is
+ "orphaned". For a normal `TARGET_EXPR' the temporary variable
should be treated as an alias for the left-hand side of the
assignment, rather than as a new temporary variable.
- The third operand to the 'TARGET_EXPR', if present, is a
+ The third operand to the `TARGET_EXPR', if present, is a
cleanup-expression (i.e., destructor call) for the temporary. If
this expression is orphaned, then this expression must be executed
when the statement containing this expression is complete. These
cleanups must always be executed in the order opposite to that in
which they were encountered. Note that if a temporary is created
on one branch of a conditional operator (i.e., in the second or
- third operand to a 'COND_EXPR'), the cleanup must be run only if
+ third operand to a `COND_EXPR'), the cleanup must be run only if
that branch is actually executed.
-'VA_ARG_EXPR'
+`VA_ARG_EXPR'
This node is used to implement support for the C/C++ variable
- argument-list mechanism. It represents expressions like 'va_arg
- (ap, type)'. Its 'TREE_TYPE' yields the tree representation for
- 'type' and its sole argument yields the representation for 'ap'.
+ argument-list mechanism. It represents expressions like `va_arg
+ (ap, type)'. Its `TREE_TYPE' yields the tree representation for
+ `type' and its sole argument yields the representation for `ap'.
-'ANNOTATE_EXPR'
- This node is used to attach markers to an expression. The first
- operand is the annotated expression, the second is an 'INTEGER_CST'
- with a value from 'enum annot_expr_kind'.
+`ANNOTATE_EXPR'
+ This node is used to attach markers to an expression. The first
+ operand is the annotated expression, the second is an
+ `INTEGER_CST' with a value from `enum annot_expr_kind'.

File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Expression trees
@@ -9002,8 +9159,8 @@ File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Exp
10.6.4 Vectors
--------------
-'VEC_LSHIFT_EXPR'
-'VEC_RSHIFT_EXPR'
+`VEC_LSHIFT_EXPR'
+`VEC_RSHIFT_EXPR'
These nodes represent whole vector left and right shifts,
respectively. The first operand is the vector to shift; it will
always be of vector type. The second operand is an expression for
@@ -9011,53 +9168,53 @@ File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Exp
undefined if the second operand is larger than or equal to the
first operand's type size.
-'VEC_WIDEN_MULT_HI_EXPR'
-'VEC_WIDEN_MULT_LO_EXPR'
+`VEC_WIDEN_MULT_HI_EXPR'
+`VEC_WIDEN_MULT_LO_EXPR'
These nodes represent widening vector multiplication of the high
and low parts of the two input vectors, respectively. Their
- operands are vectors that contain the same number of elements ('N')
- of the same integral type. The result is a vector that contains
- half as many elements, of an integral type whose size is twice as
- wide. In the case of 'VEC_WIDEN_MULT_HI_EXPR' the high 'N/2'
- elements of the two vector are multiplied to produce the vector of
- 'N/2' products. In the case of 'VEC_WIDEN_MULT_LO_EXPR' the low
- 'N/2' elements of the two vector are multiplied to produce the
- vector of 'N/2' products.
-
-'VEC_UNPACK_HI_EXPR'
-'VEC_UNPACK_LO_EXPR'
+ operands are vectors that contain the same number of elements
+ (`N') of the same integral type. The result is a vector that
+ contains half as many elements, of an integral type whose size is
+ twice as wide. In the case of `VEC_WIDEN_MULT_HI_EXPR' the high
+ `N/2' elements of the two vector are multiplied to produce the
+ vector of `N/2' products. In the case of `VEC_WIDEN_MULT_LO_EXPR'
+ the low `N/2' elements of the two vector are multiplied to produce
+ the vector of `N/2' products.
+
+`VEC_UNPACK_HI_EXPR'
+`VEC_UNPACK_LO_EXPR'
These nodes represent unpacking of the high and low parts of the
input vector, respectively. The single operand is a vector that
- contains 'N' elements of the same integral or floating point type.
+ contains `N' elements of the same integral or floating point type.
The result is a vector that contains half as many elements, of an
integral or floating point type whose size is twice as wide. In
- the case of 'VEC_UNPACK_HI_EXPR' the high 'N/2' elements of the
+ the case of `VEC_UNPACK_HI_EXPR' the high `N/2' elements of the
vector are extracted and widened (promoted). In the case of
- 'VEC_UNPACK_LO_EXPR' the low 'N/2' elements of the vector are
+ `VEC_UNPACK_LO_EXPR' the low `N/2' elements of the vector are
extracted and widened (promoted).
-'VEC_UNPACK_FLOAT_HI_EXPR'
-'VEC_UNPACK_FLOAT_LO_EXPR'
+`VEC_UNPACK_FLOAT_HI_EXPR'
+`VEC_UNPACK_FLOAT_LO_EXPR'
These nodes represent unpacking of the high and low parts of the
input vector, where the values are converted from fixed point to
- floating point. The single operand is a vector that contains 'N'
+ floating point. The single operand is a vector that contains `N'
elements of the same integral type. The result is a vector that
contains half as many elements of a floating point type whose size
- is twice as wide. In the case of 'VEC_UNPACK_HI_EXPR' the high
- 'N/2' elements of the vector are extracted, converted and widened.
- In the case of 'VEC_UNPACK_LO_EXPR' the low 'N/2' elements of the
+ is twice as wide. In the case of `VEC_UNPACK_HI_EXPR' the high
+ `N/2' elements of the vector are extracted, converted and widened.
+ In the case of `VEC_UNPACK_LO_EXPR' the low `N/2' elements of the
vector are extracted, converted and widened.
-'VEC_PACK_TRUNC_EXPR'
- This node represents packing of truncated elements of the two input
- vectors into the output vector. Input operands are vectors that
- contain the same number of elements of the same integral or
- floating point type. The result is a vector that contains twice as
- many elements of an integral or floating point type whose size is
- half as wide. The elements of the two vectors are demoted and
+`VEC_PACK_TRUNC_EXPR'
+ This node represents packing of truncated elements of the two
+ input vectors into the output vector. Input operands are vectors
+ that contain the same number of elements of the same integral or
+ floating point type. The result is a vector that contains twice
+ as many elements of an integral or floating point type whose size
+ is half as wide. The elements of the two vectors are demoted and
merged (concatenated) to form the output vector.
-'VEC_PACK_SAT_EXPR'
+`VEC_PACK_SAT_EXPR'
This node represents packing of elements of the two input vectors
into the output vector using saturation. Input operands are
vectors that contain the same number of elements of the same
@@ -9066,7 +9223,7 @@ File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Exp
elements of the two vectors are demoted and merged (concatenated)
to form the output vector.
-'VEC_PACK_FIX_TRUNC_EXPR'
+`VEC_PACK_FIX_TRUNC_EXPR'
This node represents packing of elements of the two input vectors
into the output vector, where the values are converted from
floating point to fixed point. Input operands are vectors that
@@ -9075,27 +9232,28 @@ File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Exp
integral type whose size is half as wide. The elements of the two
vectors are merged (concatenated) to form the output vector.
-'VEC_COND_EXPR'
- These nodes represent '?:' expressions. The three operands must be
+`VEC_COND_EXPR'
+ These nodes represent `?:' expressions. The three operands must be
vectors of the same size and number of elements. The second and
third operands must have the same type as the entire expression.
- The first operand is of signed integral vector type. If an element
- of the first operand evaluates to a zero value, the corresponding
- element of the result is taken from the third operand. If it
- evaluates to a minus one value, it is taken from the second
- operand. It should never evaluate to any other value currently,
- but optimizations should not rely on that property. In contrast
- with a 'COND_EXPR', all operands are always evaluated.
-
-'SAD_EXPR'
+ The first operand is of signed integral vector type. If an
+ element of the first operand evaluates to a zero value, the
+ corresponding element of the result is taken from the third
+ operand. If it evaluates to a minus one value, it is taken from
+ the second operand. It should never evaluate to any other value
+ currently, but optimizations should not rely on that property. In
+ contrast with a `COND_EXPR', all operands are always evaluated.
+
+`SAD_EXPR'
This node represents the Sum of Absolute Differences operation.
The three operands must be vectors of integral types. The first
- and second operand must have the same type. The size of the vector
- element of the third operand must be at lease twice of the size of
- the vector element of the first and second one. The SAD is
- calculated between the first and second operands, added to the
+ and second operand must have the same type. The size of the
+ vector element of the third operand must be at lease twice of the
+ size of the vector element of the first and second one. The SAD
+ is calculated between the first and second operands, added to the
third operand, and returned.
+

File: gccint.info, Node: Statements, Next: Functions, Prev: Expression trees, Up: GENERIC
@@ -9103,8 +9261,8 @@ File: gccint.info, Node: Statements, Next: Functions, Prev: Expression trees,
===============
Most statements in GIMPLE are assignment statements, represented by
-'GIMPLE_ASSIGN'. No other C expressions can appear at statement level;
-a reference to a volatile object is converted into a 'GIMPLE_ASSIGN'.
+`GIMPLE_ASSIGN'. No other C expressions can appear at statement level;
+a reference to a volatile object is converted into a `GIMPLE_ASSIGN'.
There are also several varieties of complex statements.
@@ -9125,101 +9283,96 @@ File: gccint.info, Node: Basic Statements, Next: Blocks, Up: Statements
10.7.1 Basic Statements
-----------------------
-'ASM_EXPR'
-
+`ASM_EXPR'
Used to represent an inline assembly statement. For an inline
assembly statement like:
asm ("mov x, y");
- The 'ASM_STRING' macro will return a 'STRING_CST' node for '"mov x,
- y"'. If the original statement made use of the extended-assembly
- syntax, then 'ASM_OUTPUTS', 'ASM_INPUTS', and 'ASM_CLOBBERS' will
- be the outputs, inputs, and clobbers for the statement, represented
- as 'STRING_CST' nodes. The extended-assembly syntax looks like:
+ The `ASM_STRING' macro will return a `STRING_CST' node for `"mov
+ x, y"'. If the original statement made use of the
+ extended-assembly syntax, then `ASM_OUTPUTS', `ASM_INPUTS', and
+ `ASM_CLOBBERS' will be the outputs, inputs, and clobbers for the
+ statement, represented as `STRING_CST' nodes. The
+ extended-assembly syntax looks like:
asm ("fsinx %1,%0" : "=f" (result) : "f" (angle));
- The first string is the 'ASM_STRING', containing the instruction
+ The first string is the `ASM_STRING', containing the instruction
template. The next two strings are the output and inputs,
respectively; this statement has no clobbers. As this example
- indicates, "plain" assembly statements are merely a special case of
- extended assembly statements; they have no cv-qualifiers, outputs,
- inputs, or clobbers. All of the strings will be 'NUL'-terminated,
- and will contain no embedded 'NUL'-characters.
+ indicates, "plain" assembly statements are merely a special case
+ of extended assembly statements; they have no cv-qualifiers,
+ outputs, inputs, or clobbers. All of the strings will be
+ `NUL'-terminated, and will contain no embedded `NUL'-characters.
- If the assembly statement is declared 'volatile', or if the
+ If the assembly statement is declared `volatile', or if the
statement was not an extended assembly statement, and is therefore
- implicitly volatile, then the predicate 'ASM_VOLATILE_P' will hold
- of the 'ASM_EXPR'.
-
-'DECL_EXPR'
-
- Used to represent a local declaration. The 'DECL_EXPR_DECL' macro
- can be used to obtain the entity declared. This declaration may be
- a 'LABEL_DECL', indicating that the label declared is a local
- label. (As an extension, GCC allows the declaration of labels with
- scope.) In C, this declaration may be a 'FUNCTION_DECL',
+ implicitly volatile, then the predicate `ASM_VOLATILE_P' will hold
+ of the `ASM_EXPR'.
+
+`DECL_EXPR'
+ Used to represent a local declaration. The `DECL_EXPR_DECL' macro
+ can be used to obtain the entity declared. This declaration may
+ be a `LABEL_DECL', indicating that the label declared is a local
+ label. (As an extension, GCC allows the declaration of labels
+ with scope.) In C, this declaration may be a `FUNCTION_DECL',
indicating the use of the GCC nested function extension. For more
information, *note Functions::.
-'LABEL_EXPR'
-
- Used to represent a label. The 'LABEL_DECL' declared by this
- statement can be obtained with the 'LABEL_EXPR_LABEL' macro. The
- 'IDENTIFIER_NODE' giving the name of the label can be obtained from
- the 'LABEL_DECL' with 'DECL_NAME'.
-
-'GOTO_EXPR'
+`LABEL_EXPR'
+ Used to represent a label. The `LABEL_DECL' declared by this
+ statement can be obtained with the `LABEL_EXPR_LABEL' macro. The
+ `IDENTIFIER_NODE' giving the name of the label can be obtained from
+ the `LABEL_DECL' with `DECL_NAME'.
- Used to represent a 'goto' statement. The 'GOTO_DESTINATION' will
- usually be a 'LABEL_DECL'. However, if the "computed goto"
- extension has been used, the 'GOTO_DESTINATION' will be an
+`GOTO_EXPR'
+ Used to represent a `goto' statement. The `GOTO_DESTINATION' will
+ usually be a `LABEL_DECL'. However, if the "computed goto"
+ extension has been used, the `GOTO_DESTINATION' will be an
arbitrary expression indicating the destination. This expression
will always have pointer type.
-'RETURN_EXPR'
-
- Used to represent a 'return' statement. Operand 0 represents the
- value to return. It should either be the 'RESULT_DECL' for the
- containing function, or a 'MODIFY_EXPR' or 'INIT_EXPR' setting the
- function's 'RESULT_DECL'. It will be 'NULL_TREE' if the statement
+`RETURN_EXPR'
+ Used to represent a `return' statement. Operand 0 represents the
+ value to return. It should either be the `RESULT_DECL' for the
+ containing function, or a `MODIFY_EXPR' or `INIT_EXPR' setting the
+ function's `RESULT_DECL'. It will be `NULL_TREE' if the statement
was just
return;
-'LOOP_EXPR'
- These nodes represent "infinite" loops. The 'LOOP_EXPR_BODY'
+`LOOP_EXPR'
+ These nodes represent "infinite" loops. The `LOOP_EXPR_BODY'
represents the body of the loop. It should be executed forever,
- unless an 'EXIT_EXPR' is encountered.
+ unless an `EXIT_EXPR' is encountered.
-'EXIT_EXPR'
+`EXIT_EXPR'
These nodes represent conditional exits from the nearest enclosing
- 'LOOP_EXPR'. The single operand is the condition; if it is
- nonzero, then the loop should be exited. An 'EXIT_EXPR' will only
- appear within a 'LOOP_EXPR'.
-
-'SWITCH_STMT'
+ `LOOP_EXPR'. The single operand is the condition; if it is
+ nonzero, then the loop should be exited. An `EXIT_EXPR' will only
+ appear within a `LOOP_EXPR'.
- Used to represent a 'switch' statement. The 'SWITCH_STMT_COND' is
+`SWITCH_STMT'
+ Used to represent a `switch' statement. The `SWITCH_STMT_COND' is
the expression on which the switch is occurring. See the
- documentation for an 'IF_STMT' for more information on the
- representation used for the condition. The 'SWITCH_STMT_BODY' is
- the body of the switch statement. The 'SWITCH_STMT_TYPE' is the
+ documentation for an `IF_STMT' for more information on the
+ representation used for the condition. The `SWITCH_STMT_BODY' is
+ the body of the switch statement. The `SWITCH_STMT_TYPE' is the
original type of switch expression as given in the source, before
any compiler conversions.
-'CASE_LABEL_EXPR'
-
- Use to represent a 'case' label, range of 'case' labels, or a
- 'default' label. If 'CASE_LOW' is 'NULL_TREE', then this is a
- 'default' label. Otherwise, if 'CASE_HIGH' is 'NULL_TREE', then
- this is an ordinary 'case' label. In this case, 'CASE_LOW' is an
- expression giving the value of the label. Both 'CASE_LOW' and
- 'CASE_HIGH' are 'INTEGER_CST' nodes. These values will have the
+`CASE_LABEL_EXPR'
+ Use to represent a `case' label, range of `case' labels, or a
+ `default' label. If `CASE_LOW' is `NULL_TREE', then this is a
+ `default' label. Otherwise, if `CASE_HIGH' is `NULL_TREE', then
+ this is an ordinary `case' label. In this case, `CASE_LOW' is an
+ expression giving the value of the label. Both `CASE_LOW' and
+ `CASE_HIGH' are `INTEGER_CST' nodes. These values will have the
same type as the condition expression in the switch statement.
- Otherwise, if both 'CASE_LOW' and 'CASE_HIGH' are defined, the
+ Otherwise, if both `CASE_LOW' and `CASE_HIGH' are defined, the
statement is a range of case labels. Such statements originate
with the extension that allows users to write things of the form:
case 2 ... 5:
- The first value will be 'CASE_LOW', while the second will be
- 'CASE_HIGH'.
+ The first value will be `CASE_LOW', while the second will be
+ `CASE_HIGH'.
+

File: gccint.info, Node: Blocks, Next: Statement Sequences, Prev: Basic Statements, Up: Statements
@@ -9228,27 +9381,27 @@ File: gccint.info, Node: Blocks, Next: Statement Sequences, Prev: Basic State
-------------
Block scopes and the variables they declare in GENERIC are expressed
-using the 'BIND_EXPR' code, which in previous versions of GCC was
+using the `BIND_EXPR' code, which in previous versions of GCC was
primarily used for the C statement-expression extension.
- Variables in a block are collected into 'BIND_EXPR_VARS' in declaration
-order through their 'TREE_CHAIN' field. Any runtime initialization is
-moved out of 'DECL_INITIAL' and into a statement in the controlled
-block. When gimplifying from C or C++, this initialization replaces the
-'DECL_STMT'. These variables will never require cleanups. The scope of
-these variables is just the body
+ Variables in a block are collected into `BIND_EXPR_VARS' in
+declaration order through their `TREE_CHAIN' field. Any runtime
+initialization is moved out of `DECL_INITIAL' and into a statement in
+the controlled block. When gimplifying from C or C++, this
+initialization replaces the `DECL_STMT'. These variables will never
+require cleanups. The scope of these variables is just the body
Variable-length arrays (VLAs) complicate this process, as their size
often refers to variables initialized earlier in the block. To handle
this, we currently split the block at that point, and move the VLA into
-a new, inner 'BIND_EXPR'. This strategy may change in the future.
+a new, inner `BIND_EXPR'. This strategy may change in the future.
- A C++ program will usually contain more 'BIND_EXPR's than there are
+ A C++ program will usually contain more `BIND_EXPR's than there are
syntactic blocks in the source code, since several C++ constructs have
implicit scopes associated with them. On the other hand, although the
C++ front end uses pseudo-scopes to handle cleanups for objects with
destructors, these don't translate into the GIMPLE form; multiple
-declarations at the same level use the same 'BIND_EXPR'.
+declarations at the same level use the same `BIND_EXPR'.

File: gccint.info, Node: Statement Sequences, Next: Empty Statements, Prev: Blocks, Up: Statements
@@ -9257,8 +9410,8 @@ File: gccint.info, Node: Statement Sequences, Next: Empty Statements, Prev: B
--------------------------
Multiple statements at the same nesting level are collected into a
-'STATEMENT_LIST'. Statement lists are modified and traversed using the
-interface in 'tree-iterator.h'.
+`STATEMENT_LIST'. Statement lists are modified and traversed using the
+interface in `tree-iterator.h'.

File: gccint.info, Node: Empty Statements, Next: Jumps, Prev: Statement Sequences, Up: Statements
@@ -9266,14 +9419,14 @@ File: gccint.info, Node: Empty Statements, Next: Jumps, Prev: Statement Seque
10.7.4 Empty Statements
-----------------------
-Whenever possible, statements with no effect are discarded. But if they
-are nested within another construct which cannot be discarded for some
-reason, they are instead replaced with an empty statement, generated by
-'build_empty_stmt'. Initially, all empty statements were shared, after
-the pattern of the Java front end, but this caused a lot of trouble in
-practice.
+Whenever possible, statements with no effect are discarded. But if
+they are nested within another construct which cannot be discarded for
+some reason, they are instead replaced with an empty statement,
+generated by `build_empty_stmt'. Initially, all empty statements were
+shared, after the pattern of the Java front end, but this caused a lot
+of trouble in practice.
- An empty statement is represented as '(void)0'.
+ An empty statement is represented as `(void)0'.

File: gccint.info, Node: Jumps, Next: Cleanups, Prev: Empty Statements, Up: Statements
@@ -9281,17 +9434,17 @@ File: gccint.info, Node: Jumps, Next: Cleanups, Prev: Empty Statements, Up:
10.7.5 Jumps
------------
-Other jumps are expressed by either 'GOTO_EXPR' or 'RETURN_EXPR'.
+Other jumps are expressed by either `GOTO_EXPR' or `RETURN_EXPR'.
- The operand of a 'GOTO_EXPR' must be either a label or a variable
+ The operand of a `GOTO_EXPR' must be either a label or a variable
containing the address to jump to.
- The operand of a 'RETURN_EXPR' is either 'NULL_TREE', 'RESULT_DECL', or
-a 'MODIFY_EXPR' which sets the return value. It would be nice to move
-the 'MODIFY_EXPR' into a separate statement, but the special return
-semantics in 'expand_return' make that difficult. It may still happen
-in the future, perhaps by moving most of that logic into
-'expand_assignment'.
+ The operand of a `RETURN_EXPR' is either `NULL_TREE', `RESULT_DECL',
+or a `MODIFY_EXPR' which sets the return value. It would be nice to
+move the `MODIFY_EXPR' into a separate statement, but the special
+return semantics in `expand_return' make that difficult. It may still
+happen in the future, perhaps by moving most of that logic into
+`expand_assignment'.

File: gccint.info, Node: Cleanups, Next: OpenMP, Prev: Jumps, Up: Statements
@@ -9300,7 +9453,7 @@ File: gccint.info, Node: Cleanups, Next: OpenMP, Prev: Jumps, Up: Statements
---------------
Destructors for local C++ objects and similar dynamic cleanups are
-represented in GIMPLE by a 'TRY_FINALLY_EXPR'. 'TRY_FINALLY_EXPR' has
+represented in GIMPLE by a `TRY_FINALLY_EXPR'. `TRY_FINALLY_EXPR' has
two operands, both of which are a sequence of statements to execute.
The first sequence is executed. When it completes the second sequence
is executed.
@@ -9309,31 +9462,32 @@ is executed.
1. Execute the last statement in the sequence and fall off the end.
- 2. Execute a goto statement ('GOTO_EXPR') to an ordinary label outside
- the sequence.
+ 2. Execute a goto statement (`GOTO_EXPR') to an ordinary label
+ outside the sequence.
- 3. Execute a return statement ('RETURN_EXPR').
+ 3. Execute a return statement (`RETURN_EXPR').
4. Throw an exception. This is currently not explicitly represented
in GIMPLE.
+
The second sequence is not executed if the first sequence completes by
-calling 'setjmp' or 'exit' or any other function that does not return.
-The second sequence is also not executed if the first sequence completes
-via a non-local goto or a computed goto (in general the compiler does
-not know whether such a goto statement exits the first sequence or not,
-so we assume that it doesn't).
+calling `setjmp' or `exit' or any other function that does not return.
+The second sequence is also not executed if the first sequence
+completes via a non-local goto or a computed goto (in general the
+compiler does not know whether such a goto statement exits the first
+sequence or not, so we assume that it doesn't).
After the second sequence is executed, if it completes normally by
falling off the end, execution continues wherever the first sequence
would have continued, by falling off the end, or doing a goto, etc.
- 'TRY_FINALLY_EXPR' complicates the flow graph, since the cleanup needs
+ `TRY_FINALLY_EXPR' complicates the flow graph, since the cleanup needs
to appear on every edge out of the controlled block; this reduces the
freedom to move code across these edges. Therefore, the EH lowering
pass which runs before most of the optimization passes eliminates these
expressions by explicitly adding the cleanup to each edge. Rethrowing
-the exception is represented using 'RESX_EXPR'.
+the exception is represented using `RESX_EXPR'.

File: gccint.info, Node: OpenMP, Next: OpenACC, Prev: Cleanups, Up: Statements
@@ -9341,132 +9495,122 @@ File: gccint.info, Node: OpenMP, Next: OpenACC, Prev: Cleanups, Up: Statemen
10.7.7 OpenMP
-------------
-All the statements starting with 'OMP_' represent directives and clauses
-used by the OpenMP API <http://www.openmp.org/>.
+All the statements starting with `OMP_' represent directives and
+clauses used by the OpenMP API `http://www.openmp.org/'.
-'OMP_PARALLEL'
-
- Represents '#pragma omp parallel [clause1 ... clauseN]'. It has
+`OMP_PARALLEL'
+ Represents `#pragma omp parallel [clause1 ... clauseN]'. It has
four operands:
- Operand 'OMP_PARALLEL_BODY' is valid while in GENERIC and High
+ Operand `OMP_PARALLEL_BODY' is valid while in GENERIC and High
GIMPLE forms. It contains the body of code to be executed by all
- the threads. During GIMPLE lowering, this operand becomes 'NULL'
- and the body is emitted linearly after 'OMP_PARALLEL'.
+ the threads. During GIMPLE lowering, this operand becomes `NULL'
+ and the body is emitted linearly after `OMP_PARALLEL'.
- Operand 'OMP_PARALLEL_CLAUSES' is the list of clauses associated
+ Operand `OMP_PARALLEL_CLAUSES' is the list of clauses associated
with the directive.
- Operand 'OMP_PARALLEL_FN' is created by 'pass_lower_omp', it
- contains the 'FUNCTION_DECL' for the function that will contain the
- body of the parallel region.
+ Operand `OMP_PARALLEL_FN' is created by `pass_lower_omp', it
+ contains the `FUNCTION_DECL' for the function that will contain
+ the body of the parallel region.
- Operand 'OMP_PARALLEL_DATA_ARG' is also created by
- 'pass_lower_omp'. If there are shared variables to be communicated
- to the children threads, this operand will contain the 'VAR_DECL'
+ Operand `OMP_PARALLEL_DATA_ARG' is also created by
+ `pass_lower_omp'. If there are shared variables to be communicated
+ to the children threads, this operand will contain the `VAR_DECL'
that contains all the shared values and variables.
-'OMP_FOR'
-
- Represents '#pragma omp for [clause1 ... clauseN]'. It has six
+`OMP_FOR'
+ Represents `#pragma omp for [clause1 ... clauseN]'. It has six
operands:
- Operand 'OMP_FOR_BODY' contains the loop body.
+ Operand `OMP_FOR_BODY' contains the loop body.
- Operand 'OMP_FOR_CLAUSES' is the list of clauses associated with
+ Operand `OMP_FOR_CLAUSES' is the list of clauses associated with
the directive.
- Operand 'OMP_FOR_INIT' is the loop initialization code of the form
- 'VAR = N1'.
+ Operand `OMP_FOR_INIT' is the loop initialization code of the form
+ `VAR = N1'.
- Operand 'OMP_FOR_COND' is the loop conditional expression of the
- form 'VAR {<,>,<=,>=} N2'.
+ Operand `OMP_FOR_COND' is the loop conditional expression of the
+ form `VAR {<,>,<=,>=} N2'.
- Operand 'OMP_FOR_INCR' is the loop index increment of the form 'VAR
- {+=,-=} INCR'.
+ Operand `OMP_FOR_INCR' is the loop index increment of the form
+ `VAR {+=,-=} INCR'.
- Operand 'OMP_FOR_PRE_BODY' contains side-effect code from operands
- 'OMP_FOR_INIT', 'OMP_FOR_COND' and 'OMP_FOR_INC'. These
- side-effects are part of the 'OMP_FOR' block but must be evaluated
+ Operand `OMP_FOR_PRE_BODY' contains side-effect code from operands
+ `OMP_FOR_INIT', `OMP_FOR_COND' and `OMP_FOR_INC'. These
+ side-effects are part of the `OMP_FOR' block but must be evaluated
before the start of loop body.
- The loop index variable 'VAR' must be a signed integer variable,
- which is implicitly private to each thread. Bounds 'N1' and 'N2'
- and the increment expression 'INCR' are required to be loop
+ The loop index variable `VAR' must be a signed integer variable,
+ which is implicitly private to each thread. Bounds `N1' and `N2'
+ and the increment expression `INCR' are required to be loop
invariant integer expressions that are evaluated without any
- synchronization. The evaluation order, frequency of evaluation and
+ synchronization. The evaluation order, frequency of evaluation and
side-effects are unspecified by the standard.
-'OMP_SECTIONS'
+`OMP_SECTIONS'
+ Represents `#pragma omp sections [clause1 ... clauseN]'.
- Represents '#pragma omp sections [clause1 ... clauseN]'.
+ Operand `OMP_SECTIONS_BODY' contains the sections body, which in
+ turn contains a set of `OMP_SECTION' nodes for each of the
+ concurrent sections delimited by `#pragma omp section'.
- Operand 'OMP_SECTIONS_BODY' contains the sections body, which in
- turn contains a set of 'OMP_SECTION' nodes for each of the
- concurrent sections delimited by '#pragma omp section'.
-
- Operand 'OMP_SECTIONS_CLAUSES' is the list of clauses associated
+ Operand `OMP_SECTIONS_CLAUSES' is the list of clauses associated
with the directive.
-'OMP_SECTION'
-
- Section delimiter for 'OMP_SECTIONS'.
+`OMP_SECTION'
+ Section delimiter for `OMP_SECTIONS'.
-'OMP_SINGLE'
+`OMP_SINGLE'
+ Represents `#pragma omp single'.
- Represents '#pragma omp single'.
-
- Operand 'OMP_SINGLE_BODY' contains the body of code to be executed
+ Operand `OMP_SINGLE_BODY' contains the body of code to be executed
by a single thread.
- Operand 'OMP_SINGLE_CLAUSES' is the list of clauses associated with
- the directive.
-
-'OMP_MASTER'
+ Operand `OMP_SINGLE_CLAUSES' is the list of clauses associated
+ with the directive.
- Represents '#pragma omp master'.
+`OMP_MASTER'
+ Represents `#pragma omp master'.
- Operand 'OMP_MASTER_BODY' contains the body of code to be executed
+ Operand `OMP_MASTER_BODY' contains the body of code to be executed
by the master thread.
-'OMP_ORDERED'
-
- Represents '#pragma omp ordered'.
+`OMP_ORDERED'
+ Represents `#pragma omp ordered'.
- Operand 'OMP_ORDERED_BODY' contains the body of code to be executed
- in the sequential order dictated by the loop index variable.
-
-'OMP_CRITICAL'
+ Operand `OMP_ORDERED_BODY' contains the body of code to be
+ executed in the sequential order dictated by the loop index
+ variable.
- Represents '#pragma omp critical [name]'.
+`OMP_CRITICAL'
+ Represents `#pragma omp critical [name]'.
- Operand 'OMP_CRITICAL_BODY' is the critical section.
+ Operand `OMP_CRITICAL_BODY' is the critical section.
- Operand 'OMP_CRITICAL_NAME' is an optional identifier to label the
+ Operand `OMP_CRITICAL_NAME' is an optional identifier to label the
critical section.
-'OMP_RETURN'
-
+`OMP_RETURN'
This does not represent any OpenMP directive, it is an artificial
- marker to indicate the end of the body of an OpenMP. It is used by
- the flow graph ('tree-cfg.c') and OpenMP region building code
- ('omp-low.c').
-
-'OMP_CONTINUE'
-
- Similarly, this instruction does not represent an OpenMP directive,
- it is used by 'OMP_FOR' (and similar codes) as well as
- 'OMP_SECTIONS' to mark the place where the code needs to loop to
+ marker to indicate the end of the body of an OpenMP. It is used by
+ the flow graph (`tree-cfg.c') and OpenMP region building code
+ (`omp-low.c').
+
+`OMP_CONTINUE'
+ Similarly, this instruction does not represent an OpenMP
+ directive, it is used by `OMP_FOR' (and similar codes) as well as
+ `OMP_SECTIONS' to mark the place where the code needs to loop to
the next iteration, or the next section, respectively.
- In some cases, 'OMP_CONTINUE' is placed right before 'OMP_RETURN'.
+ In some cases, `OMP_CONTINUE' is placed right before `OMP_RETURN'.
But if there are cleanups that need to occur right after the
- looping body, it will be emitted between 'OMP_CONTINUE' and
- 'OMP_RETURN'.
+ looping body, it will be emitted between `OMP_CONTINUE' and
+ `OMP_RETURN'.
-'OMP_ATOMIC'
-
- Represents '#pragma omp atomic'.
+`OMP_ATOMIC'
+ Represents `#pragma omp atomic'.
Operand 0 is the address at which the atomic operation is to be
performed.
@@ -9477,26 +9621,26 @@ used by the OpenMP API <http://www.openmp.org/>.
compare-and-swap loop is attempted. If that also fails, a regular
critical section around the expression is used.
-'OMP_CLAUSE'
-
- Represents clauses associated with one of the 'OMP_' directives.
- Clauses are represented by separate subcodes defined in 'tree.h'.
- Clauses codes can be one of: 'OMP_CLAUSE_PRIVATE',
- 'OMP_CLAUSE_SHARED', 'OMP_CLAUSE_FIRSTPRIVATE',
- 'OMP_CLAUSE_LASTPRIVATE', 'OMP_CLAUSE_COPYIN',
- 'OMP_CLAUSE_COPYPRIVATE', 'OMP_CLAUSE_IF',
- 'OMP_CLAUSE_NUM_THREADS', 'OMP_CLAUSE_SCHEDULE',
- 'OMP_CLAUSE_NOWAIT', 'OMP_CLAUSE_ORDERED', 'OMP_CLAUSE_DEFAULT',
- 'OMP_CLAUSE_REDUCTION', 'OMP_CLAUSE_COLLAPSE', 'OMP_CLAUSE_UNTIED',
- 'OMP_CLAUSE_FINAL', and 'OMP_CLAUSE_MERGEABLE'. Each code
+`OMP_CLAUSE'
+ Represents clauses associated with one of the `OMP_' directives.
+ Clauses are represented by separate subcodes defined in `tree.h'.
+ Clauses codes can be one of: `OMP_CLAUSE_PRIVATE',
+ `OMP_CLAUSE_SHARED', `OMP_CLAUSE_FIRSTPRIVATE',
+ `OMP_CLAUSE_LASTPRIVATE', `OMP_CLAUSE_COPYIN',
+ `OMP_CLAUSE_COPYPRIVATE', `OMP_CLAUSE_IF',
+ `OMP_CLAUSE_NUM_THREADS', `OMP_CLAUSE_SCHEDULE',
+ `OMP_CLAUSE_NOWAIT', `OMP_CLAUSE_ORDERED', `OMP_CLAUSE_DEFAULT',
+ `OMP_CLAUSE_REDUCTION', `OMP_CLAUSE_COLLAPSE', `OMP_CLAUSE_UNTIED',
+ `OMP_CLAUSE_FINAL', and `OMP_CLAUSE_MERGEABLE'. Each code
represents the corresponding OpenMP clause.
- Clauses associated with the same directive are chained together via
- 'OMP_CLAUSE_CHAIN'. Those clauses that accept a list of variables
- are restricted to exactly one, accessed with 'OMP_CLAUSE_VAR'.
- Therefore, multiple variables under the same clause 'C' need to be
- represented as multiple 'C' clauses chained together. This
- facilitates adding new clauses during compilation.
+ Clauses associated with the same directive are chained together
+ via `OMP_CLAUSE_CHAIN'. Those clauses that accept a list of
+ variables are restricted to exactly one, accessed with
+ `OMP_CLAUSE_VAR'. Therefore, multiple variables under the same
+ clause `C' need to be represented as multiple `C' clauses chained
+ together. This facilitates adding new clauses during compilation.
+

File: gccint.info, Node: OpenACC, Prev: OpenMP, Up: Statements
@@ -9504,50 +9648,41 @@ File: gccint.info, Node: OpenACC, Prev: OpenMP, Up: Statements
10.7.8 OpenACC
--------------
-All the statements starting with 'OACC_' represent directives and
-clauses used by the OpenACC API <http://www.openacc.org/>.
+All the statements starting with `OACC_' represent directives and
+clauses used by the OpenACC API `http://www.openacc.org/'.
-'OACC_CACHE'
+`OACC_CACHE'
+ Represents `#pragma acc cache (var ...)'.
- Represents '#pragma acc cache (var ...)'.
+`OACC_DATA'
+ Represents `#pragma acc data [clause1 ... clauseN]'.
-'OACC_DATA'
+`OACC_DECLARE'
+ Represents `#pragma acc declare [clause1 ... clauseN]'.
- Represents '#pragma acc data [clause1 ... clauseN]'.
+`OACC_ENTER_DATA'
+ Represents `#pragma acc enter data [clause1 ... clauseN]'.
-'OACC_DECLARE'
+`OACC_EXIT_DATA'
+ Represents `#pragma acc exit data [clause1 ... clauseN]'.
- Represents '#pragma acc declare [clause1 ... clauseN]'.
+`OACC_HOST_DATA'
+ Represents `#pragma acc host_data [clause1 ... clauseN]'.
-'OACC_ENTER_DATA'
+`OACC_KERNELS'
+ Represents `#pragma acc kernels [clause1 ... clauseN]'.
- Represents '#pragma acc enter data [clause1 ... clauseN]'.
+`OACC_LOOP'
+ Represents `#pragma acc loop [clause1 ... clauseN]'.
-'OACC_EXIT_DATA'
+ See the description of the `OMP_FOR' code.
- Represents '#pragma acc exit data [clause1 ... clauseN]'.
+`OACC_PARALLEL'
+ Represents `#pragma acc parallel [clause1 ... clauseN]'.
-'OACC_HOST_DATA'
+`OACC_UPDATE'
+ Represents `#pragma acc update [clause1 ... clauseN]'.
- Represents '#pragma acc host_data [clause1 ... clauseN]'.
-
-'OACC_KERNELS'
-
- Represents '#pragma acc kernels [clause1 ... clauseN]'.
-
-'OACC_LOOP'
-
- Represents '#pragma acc loop [clause1 ... clauseN]'.
-
- See the description of the 'OMP_FOR' code.
-
-'OACC_PARALLEL'
-
- Represents '#pragma acc parallel [clause1 ... clauseN]'.
-
-'OACC_UPDATE'
-
- Represents '#pragma acc update [clause1 ... clauseN]'.

File: gccint.info, Node: Functions, Next: Language-dependent trees, Prev: Statements, Up: GENERIC
@@ -9555,7 +9690,7 @@ File: gccint.info, Node: Functions, Next: Language-dependent trees, Prev: Sta
10.8 Functions
==============
-A function is represented by a 'FUNCTION_DECL' node. It stores the
+A function is represented by a `FUNCTION_DECL' node. It stores the
basic pieces of the function such as body, parameters, and return type
as well as information on the surrounding context, visibility, and
linkage.
@@ -9573,60 +9708,60 @@ File: gccint.info, Node: Function Basics, Next: Function Properties, Up: Func
A function has four core parts: the name, the parameters, the result,
and the body. The following macros and functions access these parts of
-a 'FUNCTION_DECL' as well as other basic features:
-'DECL_NAME'
+a `FUNCTION_DECL' as well as other basic features:
+`DECL_NAME'
This macro returns the unqualified name of the function, as an
- 'IDENTIFIER_NODE'. For an instantiation of a function template,
- the 'DECL_NAME' is the unqualified name of the template, not
- something like 'f<int>'. The value of 'DECL_NAME' is undefined
+ `IDENTIFIER_NODE'. For an instantiation of a function template,
+ the `DECL_NAME' is the unqualified name of the template, not
+ something like `f<int>'. The value of `DECL_NAME' is undefined
when used on a constructor, destructor, overloaded operator, or
type-conversion operator, or any function that is implicitly
generated by the compiler. See below for macros that can be used
to distinguish these cases.
-'DECL_ASSEMBLER_NAME'
+`DECL_ASSEMBLER_NAME'
This macro returns the mangled name of the function, also an
- 'IDENTIFIER_NODE'. This name does not contain leading underscores
+ `IDENTIFIER_NODE'. This name does not contain leading underscores
on systems that prefix all identifiers with underscores. The
mangled name is computed in the same way on all platforms; if
special processing is required to deal with the object file format
- used on a particular platform, it is the responsibility of the back
- end to perform those modifications. (Of course, the back end
- should not modify 'DECL_ASSEMBLER_NAME' itself.)
+ used on a particular platform, it is the responsibility of the
+ back end to perform those modifications. (Of course, the back end
+ should not modify `DECL_ASSEMBLER_NAME' itself.)
- Using 'DECL_ASSEMBLER_NAME' will cause additional memory to be
+ Using `DECL_ASSEMBLER_NAME' will cause additional memory to be
allocated (for the mangled name of the entity) so it should be used
only when emitting assembly code. It should not be used within the
optimizers to determine whether or not two declarations are the
- same, even though some of the existing optimizers do use it in that
- way. These uses will be removed over time.
+ same, even though some of the existing optimizers do use it in
+ that way. These uses will be removed over time.
-'DECL_ARGUMENTS'
- This macro returns the 'PARM_DECL' for the first argument to the
- function. Subsequent 'PARM_DECL' nodes can be obtained by
- following the 'TREE_CHAIN' links.
+`DECL_ARGUMENTS'
+ This macro returns the `PARM_DECL' for the first argument to the
+ function. Subsequent `PARM_DECL' nodes can be obtained by
+ following the `TREE_CHAIN' links.
-'DECL_RESULT'
- This macro returns the 'RESULT_DECL' for the function.
+`DECL_RESULT'
+ This macro returns the `RESULT_DECL' for the function.
-'DECL_SAVED_TREE'
+`DECL_SAVED_TREE'
This macro returns the complete body of the function.
-'TREE_TYPE'
- This macro returns the 'FUNCTION_TYPE' or 'METHOD_TYPE' for the
+`TREE_TYPE'
+ This macro returns the `FUNCTION_TYPE' or `METHOD_TYPE' for the
function.
-'DECL_INITIAL'
+`DECL_INITIAL'
A function that has a definition in the current translation unit
- will have a non-'NULL' 'DECL_INITIAL'. However, back ends should
- not make use of the particular value given by 'DECL_INITIAL'.
+ will have a non-`NULL' `DECL_INITIAL'. However, back ends should
+ not make use of the particular value given by `DECL_INITIAL'.
- It should contain a tree of 'BLOCK' nodes that mirrors the scopes
+ It should contain a tree of `BLOCK' nodes that mirrors the scopes
that variables are bound in the function. Each block contains a
list of decls declared in a basic block, a pointer to a chain of
blocks at the next lower scope level, then a pointer to the next
- block at the same level and a backpointer to the parent 'BLOCK' or
- 'FUNCTION_DECL'. So given a function as follows:
+ block at the same level and a backpointer to the parent `BLOCK' or
+ `FUNCTION_DECL'. So given a function as follows:
void foo()
{
@@ -9656,54 +9791,55 @@ a 'FUNCTION_DECL' as well as other basic features:
BLOCK_SUPERCONTEXT(block_c) = foo;
DECL_INITIAL(foo) = block_a;
+

File: gccint.info, Node: Function Properties, Prev: Function Basics, Up: Functions
10.8.2 Function Properties
--------------------------
-To determine the scope of a function, you can use the 'DECL_CONTEXT'
-macro. This macro will return the class (either a 'RECORD_TYPE' or a
-'UNION_TYPE') or namespace (a 'NAMESPACE_DECL') of which the function is
-a member. For a virtual function, this macro returns the class in which
-the function was actually defined, not the base class in which the
-virtual declaration occurred.
+To determine the scope of a function, you can use the `DECL_CONTEXT'
+macro. This macro will return the class (either a `RECORD_TYPE' or a
+`UNION_TYPE') or namespace (a `NAMESPACE_DECL') of which the function
+is a member. For a virtual function, this macro returns the class in
+which the function was actually defined, not the base class in which
+the virtual declaration occurred.
- In C, the 'DECL_CONTEXT' for a function maybe another function. This
+ In C, the `DECL_CONTEXT' for a function maybe another function. This
representation indicates that the GNU nested function extension is in
use. For details on the semantics of nested functions, see the GCC
Manual. The nested function can refer to local variables in its
containing function. Such references are not explicitly marked in the
-tree structure; back ends must look at the 'DECL_CONTEXT' for the
-referenced 'VAR_DECL'. If the 'DECL_CONTEXT' for the referenced
-'VAR_DECL' is not the same as the function currently being processed,
-and neither 'DECL_EXTERNAL' nor 'TREE_STATIC' hold, then the reference
+tree structure; back ends must look at the `DECL_CONTEXT' for the
+referenced `VAR_DECL'. If the `DECL_CONTEXT' for the referenced
+`VAR_DECL' is not the same as the function currently being processed,
+and neither `DECL_EXTERNAL' nor `TREE_STATIC' hold, then the reference
is to a local variable in a containing function, and the back end must
take appropriate action.
-'DECL_EXTERNAL'
+`DECL_EXTERNAL'
This predicate holds if the function is undefined.
-'TREE_PUBLIC'
+`TREE_PUBLIC'
This predicate holds if the function has external linkage.
-'TREE_STATIC'
+`TREE_STATIC'
This predicate holds if the function has been defined.
-'TREE_THIS_VOLATILE'
+`TREE_THIS_VOLATILE'
This predicate holds if the function does not return normally.
-'TREE_READONLY'
+`TREE_READONLY'
This predicate holds if the function can only read its arguments.
-'DECL_PURE_P'
+`DECL_PURE_P'
This predicate holds if the function can only read its arguments,
but may also read global memory.
-'DECL_VIRTUAL_P'
+`DECL_VIRTUAL_P'
This predicate holds if the function is virtual.
-'DECL_ARTIFICIAL'
+`DECL_ARTIFICIAL'
This macro holds if the function was implicitly generated by the
compiler, rather than explicitly declared. In addition to
implicitly generated class member functions, this macro holds for
@@ -9711,17 +9847,18 @@ take appropriate action.
and destruction, to compute run-time type information, and so
forth.
-'DECL_FUNCTION_SPECIFIC_TARGET'
+`DECL_FUNCTION_SPECIFIC_TARGET'
This macro returns a tree node that holds the target options that
- are to be used to compile this particular function or 'NULL_TREE'
- if the function is to be compiled with the target options specified
- on the command line.
+ are to be used to compile this particular function or `NULL_TREE'
+ if the function is to be compiled with the target options
+ specified on the command line.
-'DECL_FUNCTION_SPECIFIC_OPTIMIZATION'
+`DECL_FUNCTION_SPECIFIC_OPTIMIZATION'
This macro returns a tree node that holds the optimization options
that are to be used to compile this particular function or
- 'NULL_TREE' if the function is to be compiled with the optimization
- options specified on the command line.
+ `NULL_TREE' if the function is to be compiled with the
+ optimization options specified on the command line.
+

File: gccint.info, Node: Language-dependent trees, Next: C and C++ Trees, Prev: Functions, Up: GENERIC
@@ -9730,17 +9867,17 @@ File: gccint.info, Node: Language-dependent trees, Next: C and C++ Trees, Pre
=============================
Front ends may wish to keep some state associated with various GENERIC
-trees while parsing. To support this, trees provide a set of flags that
-may be used by the front end. They are accessed using
-'TREE_LANG_FLAG_n' where 'n' is currently 0 through 6.
+trees while parsing. To support this, trees provide a set of flags
+that may be used by the front end. They are accessed using
+`TREE_LANG_FLAG_n' where `n' is currently 0 through 6.
- If necessary, a front end can use some language-dependent tree codes in
-its GENERIC representation, so long as it provides a hook for converting
-them to GIMPLE and doesn't expect them to work with any (hypothetical)
-optimizers that run before the conversion to GIMPLE. The intermediate
-representation used while parsing C and C++ looks very little like
-GENERIC, but the C and C++ gimplifier hooks are perfectly happy to take
-it as input and spit out GIMPLE.
+ If necessary, a front end can use some language-dependent tree codes
+in its GENERIC representation, so long as it provides a hook for
+converting them to GIMPLE and doesn't expect them to work with any
+(hypothetical) optimizers that run before the conversion to GIMPLE. The
+intermediate representation used while parsing C and C++ looks very
+little like GENERIC, but the C and C++ gimplifier hooks are perfectly
+happy to take it as input and spit out GIMPLE.

File: gccint.info, Node: C and C++ Trees, Next: Java Trees, Prev: Language-dependent trees, Up: GENERIC
@@ -9796,7 +9933,7 @@ submit your patches for inclusion in GCC.
* Classes:: Classes.
* Functions for C++:: Overloading and accessors for C++.
* Statements for C++:: Statements specific to C and C++.
-* C++ Expressions:: From 'typeid' to 'throw'.
+* C++ Expressions:: From `typeid' to `throw'.

File: gccint.info, Node: Types for C++, Next: Namespaces, Up: C and C++ Trees
@@ -9810,114 +9947,118 @@ representation. The macros described here will always examine the
qualification of the underlying element type when applied to an array
type. (If the element type is itself an array, then the recursion
continues until a non-array type is found, and the qualification of this
-type is examined.) So, for example, 'CP_TYPE_CONST_P' will hold of the
-type 'const int ()[7]', denoting an array of seven 'int's.
+type is examined.) So, for example, `CP_TYPE_CONST_P' will hold of the
+type `const int ()[7]', denoting an array of seven `int's.
The following functions and macros deal with cv-qualification of types:
-'cp_type_quals'
+`cp_type_quals'
This function returns the set of type qualifiers applied to this
- type. This value is 'TYPE_UNQUALIFIED' if no qualifiers have been
- applied. The 'TYPE_QUAL_CONST' bit is set if the type is
- 'const'-qualified. The 'TYPE_QUAL_VOLATILE' bit is set if the type
- is 'volatile'-qualified. The 'TYPE_QUAL_RESTRICT' bit is set if
- the type is 'restrict'-qualified.
+ type. This value is `TYPE_UNQUALIFIED' if no qualifiers have been
+ applied. The `TYPE_QUAL_CONST' bit is set if the type is
+ `const'-qualified. The `TYPE_QUAL_VOLATILE' bit is set if the
+ type is `volatile'-qualified. The `TYPE_QUAL_RESTRICT' bit is set
+ if the type is `restrict'-qualified.
+
+`CP_TYPE_CONST_P'
+ This macro holds if the type is `const'-qualified.
-'CP_TYPE_CONST_P'
- This macro holds if the type is 'const'-qualified.
+`CP_TYPE_VOLATILE_P'
+ This macro holds if the type is `volatile'-qualified.
-'CP_TYPE_VOLATILE_P'
- This macro holds if the type is 'volatile'-qualified.
+`CP_TYPE_RESTRICT_P'
+ This macro holds if the type is `restrict'-qualified.
-'CP_TYPE_RESTRICT_P'
- This macro holds if the type is 'restrict'-qualified.
+`CP_TYPE_CONST_NON_VOLATILE_P'
+ This predicate holds for a type that is `const'-qualified, but
+ _not_ `volatile'-qualified; other cv-qualifiers are ignored as
+ well: only the `const'-ness is tested.
-'CP_TYPE_CONST_NON_VOLATILE_P'
- This predicate holds for a type that is 'const'-qualified, but
- _not_ 'volatile'-qualified; other cv-qualifiers are ignored as
- well: only the 'const'-ness is tested.
A few other macros and functions are usable with all types:
-'TYPE_SIZE'
+`TYPE_SIZE'
The number of bits required to represent the type, represented as
- an 'INTEGER_CST'. For an incomplete type, 'TYPE_SIZE' will be
- 'NULL_TREE'.
-
-'TYPE_ALIGN'
- The alignment of the type, in bits, represented as an 'int'.
-
-'TYPE_NAME'
- This macro returns a declaration (in the form of a 'TYPE_DECL') for
- the type. (Note this macro does _not_ return an 'IDENTIFIER_NODE',
- as you might expect, given its name!) You can look at the
- 'DECL_NAME' of the 'TYPE_DECL' to obtain the actual name of the
- type. The 'TYPE_NAME' will be 'NULL_TREE' for a type that is not a
- built-in type, the result of a typedef, or a named class type.
-
-'CP_INTEGRAL_TYPE'
+ an `INTEGER_CST'. For an incomplete type, `TYPE_SIZE' will be
+ `NULL_TREE'.
+
+`TYPE_ALIGN'
+ The alignment of the type, in bits, represented as an `int'.
+
+`TYPE_NAME'
+ This macro returns a declaration (in the form of a `TYPE_DECL') for
+ the type. (Note this macro does _not_ return an
+ `IDENTIFIER_NODE', as you might expect, given its name!) You can
+ look at the `DECL_NAME' of the `TYPE_DECL' to obtain the actual
+ name of the type. The `TYPE_NAME' will be `NULL_TREE' for a type
+ that is not a built-in type, the result of a typedef, or a named
+ class type.
+
+`CP_INTEGRAL_TYPE'
This predicate holds if the type is an integral type. Notice that
in C++, enumerations are _not_ integral types.
-'ARITHMETIC_TYPE_P'
+`ARITHMETIC_TYPE_P'
This predicate holds if the type is an integral type (in the C++
sense) or a floating point type.
-'CLASS_TYPE_P'
+`CLASS_TYPE_P'
This predicate holds for a class-type.
-'TYPE_BUILT_IN'
+`TYPE_BUILT_IN'
This predicate holds for a built-in type.
-'TYPE_PTRDATAMEM_P'
+`TYPE_PTRDATAMEM_P'
This predicate holds if the type is a pointer to data member.
-'TYPE_PTR_P'
- This predicate holds if the type is a pointer type, and the pointee
- is not a data member.
+`TYPE_PTR_P'
+ This predicate holds if the type is a pointer type, and the
+ pointee is not a data member.
-'TYPE_PTRFN_P'
+`TYPE_PTRFN_P'
This predicate holds for a pointer to function type.
-'TYPE_PTROB_P'
+`TYPE_PTROB_P'
This predicate holds for a pointer to object type. Note however
- that it does not hold for the generic pointer to object type 'void
- *'. You may use 'TYPE_PTROBV_P' to test for a pointer to object
- type as well as 'void *'.
+ that it does not hold for the generic pointer to object type `void
+ *'. You may use `TYPE_PTROBV_P' to test for a pointer to object
+ type as well as `void *'.
+
The table below describes types specific to C and C++ as well as
language-dependent info about GENERIC types.
-'POINTER_TYPE'
+`POINTER_TYPE'
Used to represent pointer types, and pointer to data member types.
- If 'TREE_TYPE' is a pointer to data member type, then
- 'TYPE_PTRDATAMEM_P' will hold. For a pointer to data member type
- of the form 'T X::*', 'TYPE_PTRMEM_CLASS_TYPE' will be the type
- 'X', while 'TYPE_PTRMEM_POINTED_TO_TYPE' will be the type 'T'.
-
-'RECORD_TYPE'
- Used to represent 'struct' and 'class' types in C and C++. If
- 'TYPE_PTRMEMFUNC_P' holds, then this type is a pointer-to-member
- type. In that case, the 'TYPE_PTRMEMFUNC_FN_TYPE' is a
- 'POINTER_TYPE' pointing to a 'METHOD_TYPE'. The 'METHOD_TYPE' is
+ If `TREE_TYPE' is a pointer to data member type, then
+ `TYPE_PTRDATAMEM_P' will hold. For a pointer to data member type
+ of the form `T X::*', `TYPE_PTRMEM_CLASS_TYPE' will be the type
+ `X', while `TYPE_PTRMEM_POINTED_TO_TYPE' will be the type `T'.
+
+`RECORD_TYPE'
+ Used to represent `struct' and `class' types in C and C++. If
+ `TYPE_PTRMEMFUNC_P' holds, then this type is a pointer-to-member
+ type. In that case, the `TYPE_PTRMEMFUNC_FN_TYPE' is a
+ `POINTER_TYPE' pointing to a `METHOD_TYPE'. The `METHOD_TYPE' is
the type of a function pointed to by the pointer-to-member
- function. If 'TYPE_PTRMEMFUNC_P' does not hold, this type is a
+ function. If `TYPE_PTRMEMFUNC_P' does not hold, this type is a
class type. For more information, *note Classes::.
-'UNKNOWN_TYPE'
+`UNKNOWN_TYPE'
This node is used to represent a type the knowledge of which is
insufficient for a sound processing.
-'TYPENAME_TYPE'
- Used to represent a construct of the form 'typename T::A'. The
- 'TYPE_CONTEXT' is 'T'; the 'TYPE_NAME' is an 'IDENTIFIER_NODE' for
- 'A'. If the type is specified via a template-id, then
- 'TYPENAME_TYPE_FULLNAME' yields a 'TEMPLATE_ID_EXPR'. The
- 'TREE_TYPE' is non-'NULL' if the node is implicitly generated in
+`TYPENAME_TYPE'
+ Used to represent a construct of the form `typename T::A'. The
+ `TYPE_CONTEXT' is `T'; the `TYPE_NAME' is an `IDENTIFIER_NODE' for
+ `A'. If the type is specified via a template-id, then
+ `TYPENAME_TYPE_FULLNAME' yields a `TEMPLATE_ID_EXPR'. The
+ `TREE_TYPE' is non-`NULL' if the node is implicitly generated in
support for the implicit typename extension; in which case the
- 'TREE_TYPE' is a type node for the base-class.
+ `TREE_TYPE' is a type node for the base-class.
+
+`TYPEOF_TYPE'
+ Used to represent the `__typeof__' extension. The `TYPE_FIELDS'
+ is the expression the type of which is being represented.
-'TYPEOF_TYPE'
- Used to represent the '__typeof__' extension. The 'TYPE_FIELDS' is
- the expression the type of which is being represented.

File: gccint.info, Node: Namespaces, Next: Classes, Prev: Types for C++, Up: C and C++ Trees
@@ -9926,7 +10067,7 @@ File: gccint.info, Node: Namespaces, Next: Classes, Prev: Types for C++, Up:
------------------
The root of the entire intermediate representation is the variable
-'global_namespace'. This is the namespace specified with '::' in C++
+`global_namespace'. This is the namespace specified with `::' in C++
source code. All other namespaces, types, variables, functions, and so
forth can be found starting with this namespace.
@@ -9935,60 +10076,61 @@ the representation, the global namespace is no different from any other
namespace. Thus, in what follows, we describe namespaces generally,
rather than the global namespace in particular.
- A namespace is represented by a 'NAMESPACE_DECL' node.
+ A namespace is represented by a `NAMESPACE_DECL' node.
- The following macros and functions can be used on a 'NAMESPACE_DECL':
+ The following macros and functions can be used on a `NAMESPACE_DECL':
-'DECL_NAME'
- This macro is used to obtain the 'IDENTIFIER_NODE' corresponding to
+`DECL_NAME'
+ This macro is used to obtain the `IDENTIFIER_NODE' corresponding to
the unqualified name of the name of the namespace (*note
- Identifiers::). The name of the global namespace is '::', even
- though in C++ the global namespace is unnamed. However, you should
- use comparison with 'global_namespace', rather than 'DECL_NAME' to
- determine whether or not a namespace is the global one. An unnamed
- namespace will have a 'DECL_NAME' equal to
- 'anonymous_namespace_name'. Within a single translation unit, all
+ Identifiers::). The name of the global namespace is `::', even
+ though in C++ the global namespace is unnamed. However, you
+ should use comparison with `global_namespace', rather than
+ `DECL_NAME' to determine whether or not a namespace is the global
+ one. An unnamed namespace will have a `DECL_NAME' equal to
+ `anonymous_namespace_name'. Within a single translation unit, all
unnamed namespaces will have the same name.
-'DECL_CONTEXT'
- This macro returns the enclosing namespace. The 'DECL_CONTEXT' for
- the 'global_namespace' is 'NULL_TREE'.
+`DECL_CONTEXT'
+ This macro returns the enclosing namespace. The `DECL_CONTEXT' for
+ the `global_namespace' is `NULL_TREE'.
-'DECL_NAMESPACE_ALIAS'
+`DECL_NAMESPACE_ALIAS'
If this declaration is for a namespace alias, then
- 'DECL_NAMESPACE_ALIAS' is the namespace for which this one is an
+ `DECL_NAMESPACE_ALIAS' is the namespace for which this one is an
alias.
- Do not attempt to use 'cp_namespace_decls' for a namespace which is
- an alias. Instead, follow 'DECL_NAMESPACE_ALIAS' links until you
+ Do not attempt to use `cp_namespace_decls' for a namespace which is
+ an alias. Instead, follow `DECL_NAMESPACE_ALIAS' links until you
reach an ordinary, non-alias, namespace, and call
- 'cp_namespace_decls' there.
+ `cp_namespace_decls' there.
-'DECL_NAMESPACE_STD_P'
- This predicate holds if the namespace is the special '::std'
+`DECL_NAMESPACE_STD_P'
+ This predicate holds if the namespace is the special `::std'
namespace.
-'cp_namespace_decls'
+`cp_namespace_decls'
This function will return the declarations contained in the
- namespace, including types, overloaded functions, other namespaces,
- and so forth. If there are no declarations, this function will
- return 'NULL_TREE'. The declarations are connected through their
- 'TREE_CHAIN' fields.
+ namespace, including types, overloaded functions, other
+ namespaces, and so forth. If there are no declarations, this
+ function will return `NULL_TREE'. The declarations are connected
+ through their `TREE_CHAIN' fields.
Although most entries on this list will be declarations,
- 'TREE_LIST' nodes may also appear. In this case, the 'TREE_VALUE'
- will be an 'OVERLOAD'. The value of the 'TREE_PURPOSE' is
- unspecified; back ends should ignore this value. As with the other
- kinds of declarations returned by 'cp_namespace_decls', the
- 'TREE_CHAIN' will point to the next declaration in this list.
+ `TREE_LIST' nodes may also appear. In this case, the `TREE_VALUE'
+ will be an `OVERLOAD'. The value of the `TREE_PURPOSE' is
+ unspecified; back ends should ignore this value. As with the
+ other kinds of declarations returned by `cp_namespace_decls', the
+ `TREE_CHAIN' will point to the next declaration in this list.
- For more information on the kinds of declarations that can occur on
- this list, *Note Declarations::. Some declarations will not appear
- on this list. In particular, no 'FIELD_DECL', 'LABEL_DECL', or
- 'PARM_DECL' nodes will appear here.
+ For more information on the kinds of declarations that can occur
+ on this list, *Note Declarations::. Some declarations will not
+ appear on this list. In particular, no `FIELD_DECL',
+ `LABEL_DECL', or `PARM_DECL' nodes will appear here.
This function cannot be used with namespaces that have
- 'DECL_NAMESPACE_ALIAS' set.
+ `DECL_NAMESPACE_ALIAS' set.
+

File: gccint.info, Node: Classes, Next: Functions for C++, Prev: Namespaces, Up: C and C++ Trees
@@ -9999,236 +10141,237 @@ File: gccint.info, Node: Classes, Next: Functions for C++, Prev: Namespaces,
Besides namespaces, the other high-level scoping construct in C++ is the
class. (Throughout this manual the term "class" is used to mean the
types referred to in the ANSI/ISO C++ Standard as classes; these include
-types defined with the 'class', 'struct', and 'union' keywords.)
+types defined with the `class', `struct', and `union' keywords.)
- A class type is represented by either a 'RECORD_TYPE' or a
-'UNION_TYPE'. A class declared with the 'union' tag is represented by a
-'UNION_TYPE', while classes declared with either the 'struct' or the
-'class' tag are represented by 'RECORD_TYPE's. You can use the
-'CLASSTYPE_DECLARED_CLASS' macro to discern whether or not a particular
-type is a 'class' as opposed to a 'struct'. This macro will be true
-only for classes declared with the 'class' tag.
+ A class type is represented by either a `RECORD_TYPE' or a
+`UNION_TYPE'. A class declared with the `union' tag is represented by
+a `UNION_TYPE', while classes declared with either the `struct' or the
+`class' tag are represented by `RECORD_TYPE's. You can use the
+`CLASSTYPE_DECLARED_CLASS' macro to discern whether or not a particular
+type is a `class' as opposed to a `struct'. This macro will be true
+only for classes declared with the `class' tag.
- Almost all non-function members are available on the 'TYPE_FIELDS'
+ Almost all non-function members are available on the `TYPE_FIELDS'
list. Given one member, the next can be found by following the
-'TREE_CHAIN'. You should not depend in any way on the order in which
-fields appear on this list. All nodes on this list will be 'DECL'
-nodes. A 'FIELD_DECL' is used to represent a non-static data member, a
-'VAR_DECL' is used to represent a static data member, and a 'TYPE_DECL'
-is used to represent a type. Note that the 'CONST_DECL' for an
+`TREE_CHAIN'. You should not depend in any way on the order in which
+fields appear on this list. All nodes on this list will be `DECL'
+nodes. A `FIELD_DECL' is used to represent a non-static data member, a
+`VAR_DECL' is used to represent a static data member, and a `TYPE_DECL'
+is used to represent a type. Note that the `CONST_DECL' for an
enumeration constant will appear on this list, if the enumeration type
-was declared in the class. (Of course, the 'TYPE_DECL' for the
+was declared in the class. (Of course, the `TYPE_DECL' for the
enumeration type will appear here as well.) There are no entries for
-base classes on this list. In particular, there is no 'FIELD_DECL' for
+base classes on this list. In particular, there is no `FIELD_DECL' for
the "base-class portion" of an object.
- The 'TYPE_VFIELD' is a compiler-generated field used to point to
-virtual function tables. It may or may not appear on the 'TYPE_FIELDS'
-list. However, back ends should handle the 'TYPE_VFIELD' just like all
-the entries on the 'TYPE_FIELDS' list.
+ The `TYPE_VFIELD' is a compiler-generated field used to point to
+virtual function tables. It may or may not appear on the `TYPE_FIELDS'
+list. However, back ends should handle the `TYPE_VFIELD' just like all
+the entries on the `TYPE_FIELDS' list.
- The function members are available on the 'TYPE_METHODS' list. Again,
-subsequent members are found by following the 'TREE_CHAIN' field. If a
+ The function members are available on the `TYPE_METHODS' list. Again,
+subsequent members are found by following the `TREE_CHAIN' field. If a
function is overloaded, each of the overloaded functions appears; no
-'OVERLOAD' nodes appear on the 'TYPE_METHODS' list. Implicitly declared
-functions (including default constructors, copy constructors, assignment
-operators, and destructors) will appear on this list as well.
+`OVERLOAD' nodes appear on the `TYPE_METHODS' list. Implicitly
+declared functions (including default constructors, copy constructors,
+assignment operators, and destructors) will appear on this list as well.
Every class has an associated "binfo", which can be obtained with
-'TYPE_BINFO'. Binfos are used to represent base-classes. The binfo
-given by 'TYPE_BINFO' is the degenerate case, whereby every class is
+`TYPE_BINFO'. Binfos are used to represent base-classes. The binfo
+given by `TYPE_BINFO' is the degenerate case, whereby every class is
considered to be its own base-class. The base binfos for a particular
binfo are held in a vector, whose length is obtained with
-'BINFO_N_BASE_BINFOS'. The base binfos themselves are obtained with
-'BINFO_BASE_BINFO' and 'BINFO_BASE_ITERATE'. To add a new binfo, use
-'BINFO_BASE_APPEND'. The vector of base binfos can be obtained with
-'BINFO_BASE_BINFOS', but normally you do not need to use that. The
-class type associated with a binfo is given by 'BINFO_TYPE'. It is not
-always the case that 'BINFO_TYPE (TYPE_BINFO (x))', because of typedefs
-and qualified types. Neither is it the case that 'TYPE_BINFO
-(BINFO_TYPE (y))' is the same binfo as 'y'. The reason is that if 'y'
-is a binfo representing a base-class 'B' of a derived class 'D', then
-'BINFO_TYPE (y)' will be 'B', and 'TYPE_BINFO (BINFO_TYPE (y))' will be
-'B' as its own base-class, rather than as a base-class of 'D'.
-
- The access to a base type can be found with 'BINFO_BASE_ACCESS'. This
-will produce 'access_public_node', 'access_private_node' or
-'access_protected_node'. If bases are always public,
-'BINFO_BASE_ACCESSES' may be 'NULL'.
-
- 'BINFO_VIRTUAL_P' is used to specify whether the binfo is inherited
-virtually or not. The other flags, 'BINFO_MARKED_P' and 'BINFO_FLAG_1'
-to 'BINFO_FLAG_6' can be used for language specific use.
+`BINFO_N_BASE_BINFOS'. The base binfos themselves are obtained with
+`BINFO_BASE_BINFO' and `BINFO_BASE_ITERATE'. To add a new binfo, use
+`BINFO_BASE_APPEND'. The vector of base binfos can be obtained with
+`BINFO_BASE_BINFOS', but normally you do not need to use that. The
+class type associated with a binfo is given by `BINFO_TYPE'. It is not
+always the case that `BINFO_TYPE (TYPE_BINFO (x))', because of typedefs
+and qualified types. Neither is it the case that `TYPE_BINFO
+(BINFO_TYPE (y))' is the same binfo as `y'. The reason is that if `y'
+is a binfo representing a base-class `B' of a derived class `D', then
+`BINFO_TYPE (y)' will be `B', and `TYPE_BINFO (BINFO_TYPE (y))' will be
+`B' as its own base-class, rather than as a base-class of `D'.
+
+ The access to a base type can be found with `BINFO_BASE_ACCESS'. This
+will produce `access_public_node', `access_private_node' or
+`access_protected_node'. If bases are always public,
+`BINFO_BASE_ACCESSES' may be `NULL'.
+
+ `BINFO_VIRTUAL_P' is used to specify whether the binfo is inherited
+virtually or not. The other flags, `BINFO_MARKED_P' and `BINFO_FLAG_1'
+to `BINFO_FLAG_6' can be used for language specific use.
The following macros can be used on a tree node representing a
class-type.
-'LOCAL_CLASS_P'
+`LOCAL_CLASS_P'
This predicate holds if the class is local class _i.e._ declared
inside a function body.
-'TYPE_POLYMORPHIC_P'
+`TYPE_POLYMORPHIC_P'
This predicate holds if the class has at least one virtual function
(declared or inherited).
-'TYPE_HAS_DEFAULT_CONSTRUCTOR'
+`TYPE_HAS_DEFAULT_CONSTRUCTOR'
This predicate holds whenever its argument represents a class-type
with default constructor.
-'CLASSTYPE_HAS_MUTABLE'
-'TYPE_HAS_MUTABLE_P'
+`CLASSTYPE_HAS_MUTABLE'
+`TYPE_HAS_MUTABLE_P'
These predicates hold for a class-type having a mutable data
member.
-'CLASSTYPE_NON_POD_P'
+`CLASSTYPE_NON_POD_P'
This predicate holds only for class-types that are not PODs.
-'TYPE_HAS_NEW_OPERATOR'
- This predicate holds for a class-type that defines 'operator new'.
+`TYPE_HAS_NEW_OPERATOR'
+ This predicate holds for a class-type that defines `operator new'.
-'TYPE_HAS_ARRAY_NEW_OPERATOR'
- This predicate holds for a class-type for which 'operator new[]' is
- defined.
+`TYPE_HAS_ARRAY_NEW_OPERATOR'
+ This predicate holds for a class-type for which `operator new[]'
+ is defined.
-'TYPE_OVERLOADS_CALL_EXPR'
+`TYPE_OVERLOADS_CALL_EXPR'
This predicate holds for class-type for which the function call
- 'operator()' is overloaded.
+ `operator()' is overloaded.
-'TYPE_OVERLOADS_ARRAY_REF'
- This predicate holds for a class-type that overloads 'operator[]'
+`TYPE_OVERLOADS_ARRAY_REF'
+ This predicate holds for a class-type that overloads `operator[]'
-'TYPE_OVERLOADS_ARROW'
- This predicate holds for a class-type for which 'operator->' is
+`TYPE_OVERLOADS_ARROW'
+ This predicate holds for a class-type for which `operator->' is
overloaded.
+

File: gccint.info, Node: Functions for C++, Next: Statements for C++, Prev: Classes, Up: C and C++ Trees
10.10.4 Functions for C++
-------------------------
-A function is represented by a 'FUNCTION_DECL' node. A set of
-overloaded functions is sometimes represented by an 'OVERLOAD' node.
-
- An 'OVERLOAD' node is not a declaration, so none of the 'DECL_' macros
-should be used on an 'OVERLOAD'. An 'OVERLOAD' node is similar to a
-'TREE_LIST'. Use 'OVL_CURRENT' to get the function associated with an
-'OVERLOAD' node; use 'OVL_NEXT' to get the next 'OVERLOAD' node in the
-list of overloaded functions. The macros 'OVL_CURRENT' and 'OVL_NEXT'
-are actually polymorphic; you can use them to work with 'FUNCTION_DECL'
-nodes as well as with overloads. In the case of a 'FUNCTION_DECL',
-'OVL_CURRENT' will always return the function itself, and 'OVL_NEXT'
-will always be 'NULL_TREE'.
-
- To determine the scope of a function, you can use the 'DECL_CONTEXT'
-macro. This macro will return the class (either a 'RECORD_TYPE' or a
-'UNION_TYPE') or namespace (a 'NAMESPACE_DECL') of which the function is
-a member. For a virtual function, this macro returns the class in which
-the function was actually defined, not the base class in which the
-virtual declaration occurred.
+A function is represented by a `FUNCTION_DECL' node. A set of
+overloaded functions is sometimes represented by an `OVERLOAD' node.
+
+ An `OVERLOAD' node is not a declaration, so none of the `DECL_' macros
+should be used on an `OVERLOAD'. An `OVERLOAD' node is similar to a
+`TREE_LIST'. Use `OVL_CURRENT' to get the function associated with an
+`OVERLOAD' node; use `OVL_NEXT' to get the next `OVERLOAD' node in the
+list of overloaded functions. The macros `OVL_CURRENT' and `OVL_NEXT'
+are actually polymorphic; you can use them to work with `FUNCTION_DECL'
+nodes as well as with overloads. In the case of a `FUNCTION_DECL',
+`OVL_CURRENT' will always return the function itself, and `OVL_NEXT'
+will always be `NULL_TREE'.
+
+ To determine the scope of a function, you can use the `DECL_CONTEXT'
+macro. This macro will return the class (either a `RECORD_TYPE' or a
+`UNION_TYPE') or namespace (a `NAMESPACE_DECL') of which the function
+is a member. For a virtual function, this macro returns the class in
+which the function was actually defined, not the base class in which
+the virtual declaration occurred.
If a friend function is defined in a class scope, the
-'DECL_FRIEND_CONTEXT' macro can be used to determine the class in which
+`DECL_FRIEND_CONTEXT' macro can be used to determine the class in which
it was defined. For example, in
class C { friend void f() {} };
-the 'DECL_CONTEXT' for 'f' will be the 'global_namespace', but the
-'DECL_FRIEND_CONTEXT' will be the 'RECORD_TYPE' for 'C'.
+ the `DECL_CONTEXT' for `f' will be the `global_namespace', but the
+`DECL_FRIEND_CONTEXT' will be the `RECORD_TYPE' for `C'.
- The following macros and functions can be used on a 'FUNCTION_DECL':
-'DECL_MAIN_P'
+ The following macros and functions can be used on a `FUNCTION_DECL':
+`DECL_MAIN_P'
This predicate holds for a function that is the program entry point
- '::code'.
+ `::code'.
-'DECL_LOCAL_FUNCTION_P'
+`DECL_LOCAL_FUNCTION_P'
This predicate holds if the function was declared at block scope,
even though it has a global scope.
-'DECL_ANTICIPATED'
+`DECL_ANTICIPATED'
This predicate holds if the function is a built-in function but its
prototype is not yet explicitly declared.
-'DECL_EXTERN_C_FUNCTION_P'
- This predicate holds if the function is declared as an ''extern
+`DECL_EXTERN_C_FUNCTION_P'
+ This predicate holds if the function is declared as an ``extern
"C"'' function.
-'DECL_LINKONCE_P'
- This macro holds if multiple copies of this function may be emitted
- in various translation units. It is the responsibility of the
- linker to merge the various copies. Template instantiations are
- the most common example of functions for which 'DECL_LINKONCE_P'
- holds; G++ instantiates needed templates in all translation units
- which require them, and then relies on the linker to remove
- duplicate instantiations.
+`DECL_LINKONCE_P'
+ This macro holds if multiple copies of this function may be
+ emitted in various translation units. It is the responsibility of
+ the linker to merge the various copies. Template instantiations
+ are the most common example of functions for which
+ `DECL_LINKONCE_P' holds; G++ instantiates needed templates in all
+ translation units which require them, and then relies on the
+ linker to remove duplicate instantiations.
FIXME: This macro is not yet implemented.
-'DECL_FUNCTION_MEMBER_P'
+`DECL_FUNCTION_MEMBER_P'
This macro holds if the function is a member of a class, rather
than a member of a namespace.
-'DECL_STATIC_FUNCTION_P'
+`DECL_STATIC_FUNCTION_P'
This predicate holds if the function a static member function.
-'DECL_NONSTATIC_MEMBER_FUNCTION_P'
+`DECL_NONSTATIC_MEMBER_FUNCTION_P'
This macro holds for a non-static member function.
-'DECL_CONST_MEMFUNC_P'
- This predicate holds for a 'const'-member function.
+`DECL_CONST_MEMFUNC_P'
+ This predicate holds for a `const'-member function.
-'DECL_VOLATILE_MEMFUNC_P'
- This predicate holds for a 'volatile'-member function.
+`DECL_VOLATILE_MEMFUNC_P'
+ This predicate holds for a `volatile'-member function.
-'DECL_CONSTRUCTOR_P'
+`DECL_CONSTRUCTOR_P'
This macro holds if the function is a constructor.
-'DECL_NONCONVERTING_P'
+`DECL_NONCONVERTING_P'
This predicate holds if the constructor is a non-converting
constructor.
-'DECL_COMPLETE_CONSTRUCTOR_P'
+`DECL_COMPLETE_CONSTRUCTOR_P'
This predicate holds for a function which is a constructor for an
object of a complete type.
-'DECL_BASE_CONSTRUCTOR_P'
+`DECL_BASE_CONSTRUCTOR_P'
This predicate holds for a function which is a constructor for a
base class sub-object.
-'DECL_COPY_CONSTRUCTOR_P'
+`DECL_COPY_CONSTRUCTOR_P'
This predicate holds for a function which is a copy-constructor.
-'DECL_DESTRUCTOR_P'
+`DECL_DESTRUCTOR_P'
This macro holds if the function is a destructor.
-'DECL_COMPLETE_DESTRUCTOR_P'
+`DECL_COMPLETE_DESTRUCTOR_P'
This predicate holds if the function is the destructor for an
object a complete type.
-'DECL_OVERLOADED_OPERATOR_P'
+`DECL_OVERLOADED_OPERATOR_P'
This macro holds if the function is an overloaded operator.
-'DECL_CONV_FN_P'
+`DECL_CONV_FN_P'
This macro holds if the function is a type-conversion operator.
-'DECL_GLOBAL_CTOR_P'
+`DECL_GLOBAL_CTOR_P'
This predicate holds if the function is a file-scope initialization
function.
-'DECL_GLOBAL_DTOR_P'
+`DECL_GLOBAL_DTOR_P'
This predicate holds if the function is a file-scope finalization
function.
-'DECL_THUNK_P'
+`DECL_THUNK_P'
This predicate holds if the function is a thunk.
- These functions represent stub code that adjusts the 'this' pointer
+ These functions represent stub code that adjusts the `this' pointer
and then jumps to another function. When the jumped-to function
returns, control is transferred directly to the caller, without
- returning to the thunk. The first parameter to the thunk is always
- the 'this' pointer; the thunk should add 'THUNK_DELTA' to this
- value. (The 'THUNK_DELTA' is an 'int', not an 'INTEGER_CST'.)
+ returning to the thunk. The first parameter to the thunk is
+ always the `this' pointer; the thunk should add `THUNK_DELTA' to
+ this value. (The `THUNK_DELTA' is an `int', not an `INTEGER_CST'.)
- Then, if 'THUNK_VCALL_OFFSET' (an 'INTEGER_CST') is nonzero the
- adjusted 'this' pointer must be adjusted again. The complete
+ Then, if `THUNK_VCALL_OFFSET' (an `INTEGER_CST') is nonzero the
+ adjusted `this' pointer must be adjusted again. The complete
calculation is given by the following pseudo-code:
this += THUNK_DELTA
@@ -10236,33 +10379,34 @@ the 'DECL_CONTEXT' for 'f' will be the 'global_namespace', but the
this += (*((ptrdiff_t **) this))[THUNK_VCALL_OFFSET]
Finally, the thunk should jump to the location given by
- 'DECL_INITIAL'; this will always be an expression for the address
+ `DECL_INITIAL'; this will always be an expression for the address
of a function.
-'DECL_NON_THUNK_FUNCTION_P'
+`DECL_NON_THUNK_FUNCTION_P'
This predicate holds if the function is _not_ a thunk function.
-'GLOBAL_INIT_PRIORITY'
- If either 'DECL_GLOBAL_CTOR_P' or 'DECL_GLOBAL_DTOR_P' holds, then
+`GLOBAL_INIT_PRIORITY'
+ If either `DECL_GLOBAL_CTOR_P' or `DECL_GLOBAL_DTOR_P' holds, then
this gives the initialization priority for the function. The
linker will arrange that all functions for which
- 'DECL_GLOBAL_CTOR_P' holds are run in increasing order of priority
- before 'main' is called. When the program exits, all functions for
- which 'DECL_GLOBAL_DTOR_P' holds are run in the reverse order.
+ `DECL_GLOBAL_CTOR_P' holds are run in increasing order of priority
+ before `main' is called. When the program exits, all functions for
+ which `DECL_GLOBAL_DTOR_P' holds are run in the reverse order.
-'TYPE_RAISES_EXCEPTIONS'
+`TYPE_RAISES_EXCEPTIONS'
This macro returns the list of exceptions that a (member-)function
- can raise. The returned list, if non 'NULL', is comprised of nodes
- whose 'TREE_VALUE' represents a type.
+ can raise. The returned list, if non `NULL', is comprised of nodes
+ whose `TREE_VALUE' represents a type.
-'TYPE_NOTHROW_P'
+`TYPE_NOTHROW_P'
This predicate holds when the exception-specification of its
- arguments is of the form ''()''.
+ arguments is of the form ``()''.
-'DECL_ARRAY_DELETE_OPERATOR_P'
- This predicate holds if the function an overloaded 'operator
+`DECL_ARRAY_DELETE_OPERATOR_P'
+ This predicate holds if the function an overloaded `operator
delete[]'.
+

File: gccint.info, Node: Statements for C++, Next: C++ Expressions, Prev: Functions for C++, Up: C and C++ Trees
@@ -10270,10 +10414,10 @@ File: gccint.info, Node: Statements for C++, Next: C++ Expressions, Prev: Fun
--------------------------
A function that has a definition in the current translation unit will
-have a non-'NULL' 'DECL_INITIAL'. However, back ends should not make
-use of the particular value given by 'DECL_INITIAL'.
+have a non-`NULL' `DECL_INITIAL'. However, back ends should not make
+use of the particular value given by `DECL_INITIAL'.
- The 'DECL_SAVED_TREE' macro will give the complete body of the
+ The `DECL_SAVED_TREE' macro will give the complete body of the
function.
10.10.5.1 Statements
@@ -10285,14 +10429,15 @@ here, together with a list of the various macros that can be used to
obtain information about them. There are a few macros that can be used
with all statements:
-'STMT_IS_FULL_EXPR_P'
+`STMT_IS_FULL_EXPR_P'
In C++, statements normally constitute "full expressions";
temporaries created during a statement are destroyed when the
statement is complete. However, G++ sometimes represents
expressions by statements; these statements will not have
- 'STMT_IS_FULL_EXPR_P' set. Temporaries created during such
+ `STMT_IS_FULL_EXPR_P' set. Temporaries created during such
statements should be destroyed when the innermost enclosing
- statement with 'STMT_IS_FULL_EXPR_P' set is exited.
+ statement with `STMT_IS_FULL_EXPR_P' set is exited.
+
Here is the list of the various statement nodes, and the macros used to
access them. This documentation describes the use of these nodes in
@@ -10300,12 +10445,12 @@ non-template functions (including instantiations of template functions).
In template functions, the same nodes are used, but sometimes in
slightly different ways.
- Many of the statements have substatements. For example, a 'while' loop
-will have a body, which is itself a statement. If the substatement is
-'NULL_TREE', it is considered equivalent to a statement consisting of a
-single ';', i.e., an expression statement in which the expression has
-been omitted. A substatement may in fact be a list of statements,
-connected via their 'TREE_CHAIN's. So, you should always process the
+ Many of the statements have substatements. For example, a `while'
+loop will have a body, which is itself a statement. If the substatement
+is `NULL_TREE', it is considered equivalent to a statement consisting
+of a single `;', i.e., an expression statement in which the expression
+has been omitted. A substatement may in fact be a list of statements,
+connected via their `TREE_CHAIN's. So, you should always process the
statement tree by looping over substatements, like this:
void process_stmt (stmt)
tree stmt;
@@ -10325,108 +10470,97 @@ statement tree by looping over substatements, like this:
stmt = TREE_CHAIN (stmt);
}
}
- In other words, while the 'then' clause of an 'if' statement in C++ can
-be only one statement (although that one statement may be a compound
-statement), the intermediate representation will sometimes use several
-statements chained together.
-
-'BREAK_STMT'
+ In other words, while the `then' clause of an `if' statement in C++
+can be only one statement (although that one statement may be a
+compound statement), the intermediate representation will sometimes use
+several statements chained together.
- Used to represent a 'break' statement. There are no additional
+`BREAK_STMT'
+ Used to represent a `break' statement. There are no additional
fields.
-'CILK_SPAWN_STMT'
-
+`CILK_SPAWN_STMT'
Used to represent a spawning function in the Cilk Plus language
extension. This tree has one field that holds the name of the
- spawning function. '_Cilk_spawn' can be written in C in the
+ spawning function. `_Cilk_spawn' can be written in C in the
following way:
- _Cilk_spawn <function_name> (<parameters>);
+ `_Cilk_spawn' <function_name> (<parameters>);
- Detailed description for usage and functionality of '_Cilk_spawn'
+ Detailed description for usage and functionality of `_Cilk_spawn'
can be found at http://www.cilkplus.org
-'CILK_SYNC_STMT'
-
+`CILK_SYNC_STMT'
This statement is part of the Cilk Plus language extension. It
indicates that the current function cannot continue in parallel
with its spawned children. There are no additional fields.
- '_Cilk_sync' can be written in C in the following way:
+ `_Cilk_sync' can be written in C in the following way:
- _Cilk_sync;
-
-'CLEANUP_STMT'
+ `_Cilk_sync';
+`CLEANUP_STMT'
Used to represent an action that should take place upon exit from
the enclosing scope. Typically, these actions are calls to
destructors for local objects, but back ends cannot rely on this
fact. If these nodes are in fact representing such destructors,
- 'CLEANUP_DECL' will be the 'VAR_DECL' destroyed. Otherwise,
- 'CLEANUP_DECL' will be 'NULL_TREE'. In any case, the
- 'CLEANUP_EXPR' is the expression to execute. The cleanups executed
- on exit from a scope should be run in the reverse order of the
- order in which the associated 'CLEANUP_STMT's were encountered.
-
-'CONTINUE_STMT'
-
- Used to represent a 'continue' statement. There are no additional
+ `CLEANUP_DECL' will be the `VAR_DECL' destroyed. Otherwise,
+ `CLEANUP_DECL' will be `NULL_TREE'. In any case, the
+ `CLEANUP_EXPR' is the expression to execute. The cleanups
+ executed on exit from a scope should be run in the reverse order
+ of the order in which the associated `CLEANUP_STMT's were
+ encountered.
+
+`CONTINUE_STMT'
+ Used to represent a `continue' statement. There are no additional
fields.
-'CTOR_STMT'
-
- Used to mark the beginning (if 'CTOR_BEGIN_P' holds) or end (if
- 'CTOR_END_P' holds of the main body of a constructor. See also
- 'SUBOBJECT' for more information on how to use these nodes.
+`CTOR_STMT'
+ Used to mark the beginning (if `CTOR_BEGIN_P' holds) or end (if
+ `CTOR_END_P' holds of the main body of a constructor. See also
+ `SUBOBJECT' for more information on how to use these nodes.
-'DO_STMT'
-
- Used to represent a 'do' loop. The body of the loop is given by
- 'DO_BODY' while the termination condition for the loop is given by
- 'DO_COND'. The condition for a 'do'-statement is always an
+`DO_STMT'
+ Used to represent a `do' loop. The body of the loop is given by
+ `DO_BODY' while the termination condition for the loop is given by
+ `DO_COND'. The condition for a `do'-statement is always an
expression.
-'EMPTY_CLASS_EXPR'
-
+`EMPTY_CLASS_EXPR'
Used to represent a temporary object of a class with no data whose
address is never taken. (All such objects are interchangeable.)
- The 'TREE_TYPE' represents the type of the object.
-
-'EXPR_STMT'
+ The `TREE_TYPE' represents the type of the object.
- Used to represent an expression statement. Use 'EXPR_STMT_EXPR' to
+`EXPR_STMT'
+ Used to represent an expression statement. Use `EXPR_STMT_EXPR' to
obtain the expression.
-'FOR_STMT'
-
- Used to represent a 'for' statement. The 'FOR_INIT_STMT' is the
- initialization statement for the loop. The 'FOR_COND' is the
- termination condition. The 'FOR_EXPR' is the expression executed
- right before the 'FOR_COND' on each loop iteration; often, this
+`FOR_STMT'
+ Used to represent a `for' statement. The `FOR_INIT_STMT' is the
+ initialization statement for the loop. The `FOR_COND' is the
+ termination condition. The `FOR_EXPR' is the expression executed
+ right before the `FOR_COND' on each loop iteration; often, this
expression increments a counter. The body of the loop is given by
- 'FOR_BODY'. Note that 'FOR_INIT_STMT' and 'FOR_BODY' return
- statements, while 'FOR_COND' and 'FOR_EXPR' return expressions.
-
-'HANDLER'
+ `FOR_BODY'. Note that `FOR_INIT_STMT' and `FOR_BODY' return
+ statements, while `FOR_COND' and `FOR_EXPR' return expressions.
- Used to represent a C++ 'catch' block. The 'HANDLER_TYPE' is the
+`HANDLER'
+ Used to represent a C++ `catch' block. The `HANDLER_TYPE' is the
type of exception that will be caught by this handler; it is equal
- (by pointer equality) to 'NULL' if this handler is for all types.
- 'HANDLER_PARMS' is the 'DECL_STMT' for the catch parameter, and
- 'HANDLER_BODY' is the code for the block itself.
+ (by pointer equality) to `NULL' if this handler is for all types.
+ `HANDLER_PARMS' is the `DECL_STMT' for the catch parameter, and
+ `HANDLER_BODY' is the code for the block itself.
-'IF_STMT'
-
- Used to represent an 'if' statement. The 'IF_COND' is the
+`IF_STMT'
+ Used to represent an `if' statement. The `IF_COND' is the
expression.
- If the condition is a 'TREE_LIST', then the 'TREE_PURPOSE' is a
- statement (usually a 'DECL_STMT'). Each time the condition is
+ If the condition is a `TREE_LIST', then the `TREE_PURPOSE' is a
+ statement (usually a `DECL_STMT'). Each time the condition is
evaluated, the statement should be executed. Then, the
- 'TREE_VALUE' should be used as the conditional expression itself.
+ `TREE_VALUE' should be used as the conditional expression itself.
This representation is used to handle C++ code like this:
- C++ distinguishes between this and 'COND_EXPR' for handling
+ C++ distinguishes between this and `COND_EXPR' for handling
templates.
if (int i = 7) ...
@@ -10434,58 +10568,56 @@ statements chained together.
where there is a new local variable (or variables) declared within
the condition.
- The 'THEN_CLAUSE' represents the statement given by the 'then'
- condition, while the 'ELSE_CLAUSE' represents the statement given
- by the 'else' condition.
-
-'SUBOBJECT'
+ The `THEN_CLAUSE' represents the statement given by the `then'
+ condition, while the `ELSE_CLAUSE' represents the statement given
+ by the `else' condition.
+`SUBOBJECT'
In a constructor, these nodes are used to mark the point at which a
- subobject of 'this' is fully constructed. If, after this point, an
- exception is thrown before a 'CTOR_STMT' with 'CTOR_END_P' set is
- encountered, the 'SUBOBJECT_CLEANUP' must be executed. The
+ subobject of `this' is fully constructed. If, after this point, an
+ exception is thrown before a `CTOR_STMT' with `CTOR_END_P' set is
+ encountered, the `SUBOBJECT_CLEANUP' must be executed. The
cleanups must be executed in the reverse order in which they
appear.
-'SWITCH_STMT'
-
- Used to represent a 'switch' statement. The 'SWITCH_STMT_COND' is
+`SWITCH_STMT'
+ Used to represent a `switch' statement. The `SWITCH_STMT_COND' is
the expression on which the switch is occurring. See the
- documentation for an 'IF_STMT' for more information on the
- representation used for the condition. The 'SWITCH_STMT_BODY' is
- the body of the switch statement. The 'SWITCH_STMT_TYPE' is the
+ documentation for an `IF_STMT' for more information on the
+ representation used for the condition. The `SWITCH_STMT_BODY' is
+ the body of the switch statement. The `SWITCH_STMT_TYPE' is the
original type of switch expression as given in the source, before
any compiler conversions.
-'TRY_BLOCK'
- Used to represent a 'try' block. The body of the try block is
- given by 'TRY_STMTS'. Each of the catch blocks is a 'HANDLER'
- node. The first handler is given by 'TRY_HANDLERS'. Subsequent
- handlers are obtained by following the 'TREE_CHAIN' link from one
+`TRY_BLOCK'
+ Used to represent a `try' block. The body of the try block is
+ given by `TRY_STMTS'. Each of the catch blocks is a `HANDLER'
+ node. The first handler is given by `TRY_HANDLERS'. Subsequent
+ handlers are obtained by following the `TREE_CHAIN' link from one
handler to the next. The body of the handler is given by
- 'HANDLER_BODY'.
-
- If 'CLEANUP_P' holds of the 'TRY_BLOCK', then the 'TRY_HANDLERS'
- will not be a 'HANDLER' node. Instead, it will be an expression
- that should be executed if an exception is thrown in the try block.
- It must rethrow the exception after executing that code. And, if
- an exception is thrown while the expression is executing,
- 'terminate' must be called.
-
-'USING_STMT'
- Used to represent a 'using' directive. The namespace is given by
- 'USING_STMT_NAMESPACE', which will be a NAMESPACE_DECL. This node
+ `HANDLER_BODY'.
+
+ If `CLEANUP_P' holds of the `TRY_BLOCK', then the `TRY_HANDLERS'
+ will not be a `HANDLER' node. Instead, it will be an expression
+ that should be executed if an exception is thrown in the try
+ block. It must rethrow the exception after executing that code.
+ And, if an exception is thrown while the expression is executing,
+ `terminate' must be called.
+
+`USING_STMT'
+ Used to represent a `using' directive. The namespace is given by
+ `USING_STMT_NAMESPACE', which will be a NAMESPACE_DECL. This node
is needed inside template functions, to implement using directives
during instantiation.
-'WHILE_STMT'
-
- Used to represent a 'while' loop. The 'WHILE_COND' is the
+`WHILE_STMT'
+ Used to represent a `while' loop. The `WHILE_COND' is the
termination condition for the loop. See the documentation for an
- 'IF_STMT' for more information on the representation used for the
+ `IF_STMT' for more information on the representation used for the
condition.
- The 'WHILE_BODY' is the body of the loop.
+ The `WHILE_BODY' is the body of the loop.
+

File: gccint.info, Node: C++ Expressions, Prev: Statements for C++, Up: C and C++ Trees
@@ -10495,46 +10627,42 @@ File: gccint.info, Node: C++ Expressions, Prev: Statements for C++, Up: C and
This section describes expressions specific to the C and C++ front ends.
-'TYPEID_EXPR'
+`TYPEID_EXPR'
+ Used to represent a `typeid' expression.
- Used to represent a 'typeid' expression.
+`NEW_EXPR'
+`VEC_NEW_EXPR'
+ Used to represent a call to `new' and `new[]' respectively.
-'NEW_EXPR'
-'VEC_NEW_EXPR'
-
- Used to represent a call to 'new' and 'new[]' respectively.
-
-'DELETE_EXPR'
-'VEC_DELETE_EXPR'
-
- Used to represent a call to 'delete' and 'delete[]' respectively.
-
-'MEMBER_REF'
+`DELETE_EXPR'
+`VEC_DELETE_EXPR'
+ Used to represent a call to `delete' and `delete[]' respectively.
+`MEMBER_REF'
Represents a reference to a member of a class.
-'THROW_EXPR'
-
- Represents an instance of 'throw' in the program. Operand 0, which
- is the expression to throw, may be 'NULL_TREE'.
+`THROW_EXPR'
+ Represents an instance of `throw' in the program. Operand 0,
+ which is the expression to throw, may be `NULL_TREE'.
-'AGGR_INIT_EXPR'
- An 'AGGR_INIT_EXPR' represents the initialization as the return
+`AGGR_INIT_EXPR'
+ An `AGGR_INIT_EXPR' represents the initialization as the return
value of a function call, or as the result of a constructor. An
- 'AGGR_INIT_EXPR' will only appear as a full-expression, or as the
- second operand of a 'TARGET_EXPR'. 'AGGR_INIT_EXPR's have a
- representation similar to that of 'CALL_EXPR's. You can use the
- 'AGGR_INIT_EXPR_FN' and 'AGGR_INIT_EXPR_ARG' macros to access the
+ `AGGR_INIT_EXPR' will only appear as a full-expression, or as the
+ second operand of a `TARGET_EXPR'. `AGGR_INIT_EXPR's have a
+ representation similar to that of `CALL_EXPR's. You can use the
+ `AGGR_INIT_EXPR_FN' and `AGGR_INIT_EXPR_ARG' macros to access the
function to call and the arguments to pass.
- If 'AGGR_INIT_VIA_CTOR_P' holds of the 'AGGR_INIT_EXPR', then the
+ If `AGGR_INIT_VIA_CTOR_P' holds of the `AGGR_INIT_EXPR', then the
initialization is via a constructor call. The address of the
- 'AGGR_INIT_EXPR_SLOT' operand, which is always a 'VAR_DECL', is
+ `AGGR_INIT_EXPR_SLOT' operand, which is always a `VAR_DECL', is
taken, and this value replaces the first argument in the argument
list.
In either case, the expression is void.
+

File: gccint.info, Node: Java Trees, Prev: C and C++ Trees, Up: GENERIC
@@ -10548,62 +10676,62 @@ File: gccint.info, Node: GIMPLE, Next: Tree SSA, Prev: GENERIC, Up: Top
*********
GIMPLE is a three-address representation derived from GENERIC by
-breaking down GENERIC expressions into tuples of no more than 3 operands
-(with some exceptions like function calls). GIMPLE was heavily
-influenced by the SIMPLE IL used by the McCAT compiler project at McGill
-University, though we have made some different choices. For one thing,
-SIMPLE doesn't support 'goto'.
+breaking down GENERIC expressions into tuples of no more than 3
+operands (with some exceptions like function calls). GIMPLE was
+heavily influenced by the SIMPLE IL used by the McCAT compiler project
+at McGill University, though we have made some different choices. For
+one thing, SIMPLE doesn't support `goto'.
Temporaries are introduced to hold intermediate values needed to
-compute complex expressions. Additionally, all the control structures
+compute complex expressions. Additionally, all the control structures
used in GENERIC are lowered into conditional jumps, lexical scopes are
removed and exception regions are converted into an on the side
exception region tree.
The compiler pass which converts GENERIC into GIMPLE is referred to as
-the 'gimplifier'. The gimplifier works recursively, generating GIMPLE
+the `gimplifier'. The gimplifier works recursively, generating GIMPLE
tuples out of the original GENERIC expressions.
One of the early implementation strategies used for the GIMPLE
representation was to use the same internal data structures used by
-front ends to represent parse trees. This simplified implementation
+front ends to represent parse trees. This simplified implementation
because we could leverage existing functionality and interfaces.
However, GIMPLE is a much more restrictive representation than abstract
syntax trees (AST), therefore it does not require the full structural
complexity provided by the main tree data structure.
The GENERIC representation of a function is stored in the
-'DECL_SAVED_TREE' field of the associated 'FUNCTION_DECL' tree node. It
-is converted to GIMPLE by a call to 'gimplify_function_tree'.
+`DECL_SAVED_TREE' field of the associated `FUNCTION_DECL' tree node.
+It is converted to GIMPLE by a call to `gimplify_function_tree'.
If a front end wants to include language-specific tree codes in the
tree representation which it provides to the back end, it must provide a
-definition of 'LANG_HOOKS_GIMPLIFY_EXPR' which knows how to convert the
-front end trees to GIMPLE. Usually such a hook will involve much of the
-same code for expanding front end trees to RTL. This function can
+definition of `LANG_HOOKS_GIMPLIFY_EXPR' which knows how to convert the
+front end trees to GIMPLE. Usually such a hook will involve much of
+the same code for expanding front end trees to RTL. This function can
return fully lowered GIMPLE, or it can return GENERIC trees and let the
main gimplifier lower them the rest of the way; this is often simpler.
GIMPLE that is not fully lowered is known as "High GIMPLE" and consists
-of the IL before the pass 'pass_lower_cf'. High GIMPLE contains some
-container statements like lexical scopes (represented by 'GIMPLE_BIND')
-and nested expressions (e.g., 'GIMPLE_TRY'), while "Low GIMPLE" exposes
-all of the implicit jumps for control and exception expressions directly
-in the IL and EH region trees.
+of the IL before the pass `pass_lower_cf'. High GIMPLE contains some
+container statements like lexical scopes (represented by `GIMPLE_BIND')
+and nested expressions (e.g., `GIMPLE_TRY'), while "Low GIMPLE" exposes
+all of the implicit jumps for control and exception expressions
+directly in the IL and EH region trees.
The C and C++ front ends currently convert directly from front end
trees to GIMPLE, and hand that off to the back end rather than first
converting to GENERIC. Their gimplifier hooks know about all the
-'_STMT' nodes and how to convert them to GENERIC forms. There was some
+`_STMT' nodes and how to convert them to GENERIC forms. There was some
work done on a genericization pass which would run first, but the
-existence of 'STMT_EXPR' meant that in order to convert all of the C
+existence of `STMT_EXPR' meant that in order to convert all of the C
statements into GENERIC equivalents would involve walking the entire
tree anyway, so it was simpler to lower all the way. This might change
in the future if someone writes an optimization pass which would work
better with higher-level trees, but currently the optimizers all expect
GIMPLE.
- You can request to dump a C-like representation of the GIMPLE form with
-the flag '-fdump-tree-gimple'.
+ You can request to dump a C-like representation of the GIMPLE form
+with the flag `-fdump-tree-gimple'.
* Menu:
@@ -10626,169 +10754,168 @@ File: gccint.info, Node: Tuple representation, Next: Class hierarchy of GIMPLE
11.1 Tuple representation
=========================
-GIMPLE instructions are tuples of variable size divided in two groups: a
-header describing the instruction and its locations, and a variable
-length body with all the operands. Tuples are organized into a
+GIMPLE instructions are tuples of variable size divided in two groups:
+a header describing the instruction and its locations, and a variable
+length body with all the operands. Tuples are organized into a
hierarchy with 3 main classes of tuples.
-11.1.1 'gimple_statement_base' (gsbase)
+11.1.1 `gimple_statement_base' (gsbase)
---------------------------------------
This is the root of the hierarchy, it holds basic information needed by
-most GIMPLE statements. There are some fields that may not be relevant
+most GIMPLE statements. There are some fields that may not be relevant
to every GIMPLE statement, but those were moved into the base structure
to take advantage of holes left by other fields (thus making the
structure more compact). The structure takes 4 words (32 bytes) on 64
bit hosts:
Field Size (bits)
-'code' 8
-'subcode' 16
-'no_warning' 1
-'visited' 1
-'nontemporal_move' 1
-'plf' 2
-'modified' 1
-'has_volatile_ops' 1
-'references_memory_p' 1
-'uid' 32
-'location' 32
-'num_ops' 32
-'bb' 64
-'block' 63
+`code' 8
+`subcode' 16
+`no_warning' 1
+`visited' 1
+`nontemporal_move' 1
+`plf' 2
+`modified' 1
+`has_volatile_ops' 1
+`references_memory_p' 1
+`uid' 32
+`location' 32
+`num_ops' 32
+`bb' 64
+`block' 63
Total size 32 bytes
- * 'code' Main identifier for a GIMPLE instruction.
+ * `code' Main identifier for a GIMPLE instruction.
- * 'subcode' Used to distinguish different variants of the same basic
- instruction or provide flags applicable to a given code. The
- 'subcode' flags field has different uses depending on the code of
+ * `subcode' Used to distinguish different variants of the same basic
+ instruction or provide flags applicable to a given code. The
+ `subcode' flags field has different uses depending on the code of
the instruction, but mostly it distinguishes instructions of the
- same family. The most prominent use of this field is in
+ same family. The most prominent use of this field is in
assignments, where subcode indicates the operation done on the RHS
- of the assignment. For example, a = b + c is encoded as
- 'GIMPLE_ASSIGN <PLUS_EXPR, a, b, c>'.
+ of the assignment. For example, a = b + c is encoded as
+ `GIMPLE_ASSIGN <PLUS_EXPR, a, b, c>'.
- * 'no_warning' Bitflag to indicate whether a warning has already been
- issued on this statement.
+ * `no_warning' Bitflag to indicate whether a warning has already
+ been issued on this statement.
- * 'visited' General purpose "visited" marker. Set and cleared by
+ * `visited' General purpose "visited" marker. Set and cleared by
each pass when needed.
- * 'nontemporal_move' Bitflag used in assignments that represent
+ * `nontemporal_move' Bitflag used in assignments that represent
non-temporal moves. Although this bitflag is only used in
assignments, it was moved into the base to take advantage of the
bit holes left by the previous fields.
- * 'plf' Pass Local Flags. This 2-bit mask can be used as general
- purpose markers by any pass. Passes are responsible for clearing
+ * `plf' Pass Local Flags. This 2-bit mask can be used as general
+ purpose markers by any pass. Passes are responsible for clearing
and setting these two flags accordingly.
- * 'modified' Bitflag to indicate whether the statement has been
+ * `modified' Bitflag to indicate whether the statement has been
modified. Used mainly by the operand scanner to determine when to
re-scan a statement for operands.
- * 'has_volatile_ops' Bitflag to indicate whether this statement
+ * `has_volatile_ops' Bitflag to indicate whether this statement
contains operands that have been marked volatile.
- * 'references_memory_p' Bitflag to indicate whether this statement
+ * `references_memory_p' Bitflag to indicate whether this statement
contains memory references (i.e., its operands are either global
variables, or pointer dereferences or anything that must reside in
memory).
- * 'uid' This is an unsigned integer used by passes that want to
- assign IDs to every statement. These IDs must be assigned and used
+ * `uid' This is an unsigned integer used by passes that want to
+ assign IDs to every statement. These IDs must be assigned and used
by each pass.
- * 'location' This is a 'location_t' identifier to specify source code
- location for this statement. It is inherited from the front end.
+ * `location' This is a `location_t' identifier to specify source code
+ location for this statement. It is inherited from the front end.
- * 'num_ops' Number of operands that this statement has. This
+ * `num_ops' Number of operands that this statement has. This
specifies the size of the operand vector embedded in the tuple.
Only used in some tuples, but it is declared in the base tuple to
take advantage of the 32-bit hole left by the previous fields.
- * 'bb' Basic block holding the instruction.
+ * `bb' Basic block holding the instruction.
- * 'block' Lexical block holding this statement. Also used for debug
+ * `block' Lexical block holding this statement. Also used for debug
information generation.
-11.1.2 'gimple_statement_with_ops'
+11.1.2 `gimple_statement_with_ops'
----------------------------------
-This tuple is actually split in two: 'gimple_statement_with_ops_base'
-and 'gimple_statement_with_ops'. This is needed to accommodate the way
-the operand vector is allocated. The operand vector is defined to be an
-array of 1 element. So, to allocate a dynamic number of operands, the
-memory allocator ('gimple_alloc') simply allocates enough memory to hold
-the structure itself plus 'N - 1' operands which run "off the end" of
-the structure. For example, to allocate space for a tuple with 3
-operands, 'gimple_alloc' reserves 'sizeof (struct
+This tuple is actually split in two: `gimple_statement_with_ops_base'
+and `gimple_statement_with_ops'. This is needed to accommodate the way
+the operand vector is allocated. The operand vector is defined to be an
+array of 1 element. So, to allocate a dynamic number of operands, the
+memory allocator (`gimple_alloc') simply allocates enough memory to
+hold the structure itself plus `N - 1' operands which run "off the end"
+of the structure. For example, to allocate space for a tuple with 3
+operands, `gimple_alloc' reserves `sizeof (struct
gimple_statement_with_ops) + 2 * sizeof (tree)' bytes.
On the other hand, several fields in this tuple need to be shared with
-the 'gimple_statement_with_memory_ops' tuple. So, these common fields
-are placed in 'gimple_statement_with_ops_base' which is then inherited
+the `gimple_statement_with_memory_ops' tuple. So, these common fields
+are placed in `gimple_statement_with_ops_base' which is then inherited
from the other two tuples.
-'gsbase' 256
-'def_ops' 64
-'use_ops' 64
-'op' 'num_ops' * 64
-Total 48 + 8 * 'num_ops' bytes
-size
+`gsbase' 256
+`def_ops' 64
+`use_ops' 64
+`op' `num_ops' * 64
+Total size 48 + 8 * `num_ops' bytes
- * 'gsbase' Inherited from 'struct gimple_statement_base'.
+ * `gsbase' Inherited from `struct gimple_statement_base'.
- * 'def_ops' Array of pointers into the operand array indicating all
+ * `def_ops' Array of pointers into the operand array indicating all
the slots that contain a variable written-to by the statement.
- This array is also used for immediate use chaining. Note that it
+ This array is also used for immediate use chaining. Note that it
would be possible to not rely on this array, but the changes
required to implement this are pretty invasive.
- * 'use_ops' Similar to 'def_ops' but for variables read by the
+ * `use_ops' Similar to `def_ops' but for variables read by the
statement.
- * 'op' Array of trees with 'num_ops' slots.
+ * `op' Array of trees with `num_ops' slots.
-11.1.3 'gimple_statement_with_memory_ops'
+11.1.3 `gimple_statement_with_memory_ops'
-----------------------------------------
-This tuple is essentially identical to 'gimple_statement_with_ops',
+This tuple is essentially identical to `gimple_statement_with_ops',
except that it contains 4 additional fields to hold vectors related
-memory stores and loads. Similar to the previous case, the structure is
-split in two to accommodate for the operand vector
-('gimple_statement_with_memory_ops_base' and
-'gimple_statement_with_memory_ops').
+memory stores and loads. Similar to the previous case, the structure
+is split in two to accommodate for the operand vector
+(`gimple_statement_with_memory_ops_base' and
+`gimple_statement_with_memory_ops').
Field Size (bits)
-'gsbase' 256
-'def_ops' 64
-'use_ops' 64
-'vdef_ops' 64
-'vuse_ops' 64
-'stores' 64
-'loads' 64
-'op' 'num_ops' * 64
-Total size 80 + 8 * 'num_ops' bytes
-
- * 'vdef_ops' Similar to 'def_ops' but for 'VDEF' operators. There is
- one entry per memory symbol written by this statement. This is
+`gsbase' 256
+`def_ops' 64
+`use_ops' 64
+`vdef_ops' 64
+`vuse_ops' 64
+`stores' 64
+`loads' 64
+`op' `num_ops' * 64
+Total size 80 + 8 * `num_ops' bytes
+
+ * `vdef_ops' Similar to `def_ops' but for `VDEF' operators. There is
+ one entry per memory symbol written by this statement. This is
used to maintain the memory SSA use-def and def-def chains.
- * 'vuse_ops' Similar to 'use_ops' but for 'VUSE' operators. There is
- one entry per memory symbol loaded by this statement. This is used
+ * `vuse_ops' Similar to `use_ops' but for `VUSE' operators. There is
+ one entry per memory symbol loaded by this statement. This is used
to maintain the memory SSA use-def chains.
- * 'stores' Bitset with all the UIDs for the symbols written-to by the
- statement. This is different than 'vdef_ops' in that all the
- affected symbols are mentioned in this set. If memory partitioning
- is enabled, the 'vdef_ops' vector will refer to memory partitions.
- Furthermore, no SSA information is stored in this set.
+ * `stores' Bitset with all the UIDs for the symbols written-to by the
+ statement. This is different than `vdef_ops' in that all the
+ affected symbols are mentioned in this set. If memory
+ partitioning is enabled, the `vdef_ops' vector will refer to memory
+ partitions. Furthermore, no SSA information is stored in this set.
- * 'loads' Similar to 'stores', but for memory loads. (Note that
- there is some amount of redundancy here, it should be possible to
- reduce memory utilization further by removing these sets).
+ * `loads' Similar to `stores', but for memory loads. (Note that there
+ is some amount of redundancy here, it should be possible to reduce
+ memory utilization further by removing these sets).
All the other tuples are defined in terms of these three basic ones.
Each tuple will add some fields.
@@ -10800,8 +10927,8 @@ File: gccint.info, Node: Class hierarchy of GIMPLE statements, Next: GIMPLE in
=========================================
The following diagram shows the C++ inheritance hierarchy of statement
-kinds, along with their relationships to 'GSS_' values (layouts) and
-'GIMPLE_' values (codes):
+kinds, along with their relationships to `GSS_' values (layouts) and
+`GIMPLE_' values (codes):
gimple_statement_base
| layout: GSS_BASE
@@ -10945,35 +11072,35 @@ File: gccint.info, Node: GIMPLE instruction set, Next: GIMPLE Exception Handli
The following table briefly describes the GIMPLE instruction set.
Instruction High GIMPLE Low GIMPLE
-'GIMPLE_ASM' x x
-'GIMPLE_ASSIGN' x x
-'GIMPLE_BIND' x
-'GIMPLE_CALL' x x
-'GIMPLE_CATCH' x
-'GIMPLE_COND' x x
-'GIMPLE_DEBUG' x x
-'GIMPLE_EH_FILTER' x
-'GIMPLE_GOTO' x x
-'GIMPLE_LABEL' x x
-'GIMPLE_NOP' x x
-'GIMPLE_OMP_ATOMIC_LOAD' x x
-'GIMPLE_OMP_ATOMIC_STORE' x x
-'GIMPLE_OMP_CONTINUE' x x
-'GIMPLE_OMP_CRITICAL' x x
-'GIMPLE_OMP_FOR' x x
-'GIMPLE_OMP_MASTER' x x
-'GIMPLE_OMP_ORDERED' x x
-'GIMPLE_OMP_PARALLEL' x x
-'GIMPLE_OMP_RETURN' x x
-'GIMPLE_OMP_SECTION' x x
-'GIMPLE_OMP_SECTIONS' x x
-'GIMPLE_OMP_SECTIONS_SWITCH' x x
-'GIMPLE_OMP_SINGLE' x x
-'GIMPLE_PHI' x
-'GIMPLE_RESX' x
-'GIMPLE_RETURN' x x
-'GIMPLE_SWITCH' x x
-'GIMPLE_TRY' x
+`GIMPLE_ASM' x x
+`GIMPLE_ASSIGN' x x
+`GIMPLE_BIND' x
+`GIMPLE_CALL' x x
+`GIMPLE_CATCH' x
+`GIMPLE_COND' x x
+`GIMPLE_DEBUG' x x
+`GIMPLE_EH_FILTER' x
+`GIMPLE_GOTO' x x
+`GIMPLE_LABEL' x x
+`GIMPLE_NOP' x x
+`GIMPLE_OMP_ATOMIC_LOAD' x x
+`GIMPLE_OMP_ATOMIC_STORE' x x
+`GIMPLE_OMP_CONTINUE' x x
+`GIMPLE_OMP_CRITICAL' x x
+`GIMPLE_OMP_FOR' x x
+`GIMPLE_OMP_MASTER' x x
+`GIMPLE_OMP_ORDERED' x x
+`GIMPLE_OMP_PARALLEL' x x
+`GIMPLE_OMP_RETURN' x x
+`GIMPLE_OMP_SECTION' x x
+`GIMPLE_OMP_SECTIONS' x x
+`GIMPLE_OMP_SECTIONS_SWITCH' x x
+`GIMPLE_OMP_SINGLE' x x
+`GIMPLE_PHI' x
+`GIMPLE_RESX' x
+`GIMPLE_RETURN' x x
+`GIMPLE_SWITCH' x x
+`GIMPLE_TRY' x

File: gccint.info, Node: GIMPLE Exception Handling, Next: Temporaries, Prev: GIMPLE instruction set, Up: GIMPLE
@@ -10982,38 +11109,39 @@ File: gccint.info, Node: GIMPLE Exception Handling, Next: Temporaries, Prev:
=======================
Other exception handling constructs are represented using
-'GIMPLE_TRY_CATCH'. 'GIMPLE_TRY_CATCH' has two operands. The first
+`GIMPLE_TRY_CATCH'. `GIMPLE_TRY_CATCH' has two operands. The first
operand is a sequence of statements to execute. If executing these
statements does not throw an exception, then the second operand is
ignored. Otherwise, if an exception is thrown, then the second operand
-of the 'GIMPLE_TRY_CATCH' is checked. The second operand may have the
+of the `GIMPLE_TRY_CATCH' is checked. The second operand may have the
following forms:
1. A sequence of statements to execute. When an exception occurs,
these statements are executed, and then the exception is rethrown.
- 2. A sequence of 'GIMPLE_CATCH' statements. Each 'GIMPLE_CATCH' has a
- list of applicable exception types and handler code. If the thrown
- exception matches one of the caught types, the associated handler
- code is executed. If the handler code falls off the bottom,
- execution continues after the original 'GIMPLE_TRY_CATCH'.
-
- 3. A 'GIMPLE_EH_FILTER' statement. This has a list of permitted
- exception types, and code to handle a match failure. If the thrown
- exception does not match one of the allowed types, the associated
- match failure code is executed. If the thrown exception does
- match, it continues unwinding the stack looking for the next
+ 2. A sequence of `GIMPLE_CATCH' statements. Each `GIMPLE_CATCH' has
+ a list of applicable exception types and handler code. If the
+ thrown exception matches one of the caught types, the associated
+ handler code is executed. If the handler code falls off the
+ bottom, execution continues after the original `GIMPLE_TRY_CATCH'.
+
+ 3. A `GIMPLE_EH_FILTER' statement. This has a list of permitted
+ exception types, and code to handle a match failure. If the
+ thrown exception does not match one of the allowed types, the
+ associated match failure code is executed. If the thrown exception
+ does match, it continues unwinding the stack looking for the next
handler.
+
Currently throwing an exception is not directly represented in GIMPLE,
since it is implemented by calling a function. At some point in the
future we will want to add some way to express that the call will throw
an exception of a known type.
Just before running the optimizers, the compiler lowers the high-level
-EH constructs above into a set of 'goto's, magic labels, and EH regions.
-Continuing to unwind at the end of a cleanup is represented with a
-'GIMPLE_RESX'.
+EH constructs above into a set of `goto's, magic labels, and EH
+regions. Continuing to unwind at the end of a cleanup is represented
+with a `GIMPLE_RESX'.

File: gccint.info, Node: Temporaries, Next: Operands, Prev: GIMPLE Exception Handling, Up: GIMPLE
@@ -11022,19 +11150,19 @@ File: gccint.info, Node: Temporaries, Next: Operands, Prev: GIMPLE Exception
================
When gimplification encounters a subexpression that is too complex, it
-creates a new temporary variable to hold the value of the subexpression,
-and adds a new statement to initialize it before the current statement.
-These special temporaries are known as 'expression temporaries', and are
-allocated using 'get_formal_tmp_var'. The compiler tries to always
-evaluate identical expressions into the same temporary, to simplify
-elimination of redundant calculations.
-
- We can only use expression temporaries when we know that it will not be
-reevaluated before its value is used, and that it will not be otherwise
-modified(1). Other temporaries can be allocated using
-'get_initialized_tmp_var' or 'create_tmp_var'.
-
- Currently, an expression like 'a = b + 5' is not reduced any further.
+creates a new temporary variable to hold the value of the
+subexpression, and adds a new statement to initialize it before the
+current statement. These special temporaries are known as `expression
+temporaries', and are allocated using `get_formal_tmp_var'. The
+compiler tries to always evaluate identical expressions into the same
+temporary, to simplify elimination of redundant calculations.
+
+ We can only use expression temporaries when we know that it will not
+be reevaluated before its value is used, and that it will not be
+otherwise modified(1). Other temporaries can be allocated using
+`get_initialized_tmp_var' or `create_tmp_var'.
+
+ Currently, an expression like `a = b + 5' is not reduced any further.
We tried converting it to something like
T1 = b + 5;
a = T1;
@@ -11044,9 +11172,9 @@ value is explicitly loaded into a temporary first. Similarly, storing
the value of an expression to a memory variable goes through a
temporary.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) These restrictions are derived from those in Morgan 4.8.
+ (1) These restrictions are derived from those in Morgan 4.8.

File: gccint.info, Node: Operands, Next: Manipulating GIMPLE statements, Prev: Temporaries, Up: GIMPLE
@@ -11056,17 +11184,18 @@ File: gccint.info, Node: Operands, Next: Manipulating GIMPLE statements, Prev
In general, expressions in GIMPLE consist of an operation and the
appropriate number of simple operands; these operands must either be a
-GIMPLE rvalue ('is_gimple_val'), i.e. a constant or a register variable.
-More complex operands are factored out into temporaries, so that
+GIMPLE rvalue (`is_gimple_val'), i.e. a constant or a register
+variable. More complex operands are factored out into temporaries, so
+that
a = b + c + d
becomes
T1 = b + c;
a = T1 + d;
- The same rule holds for arguments to a 'GIMPLE_CALL'.
+ The same rule holds for arguments to a `GIMPLE_CALL'.
The target of an assignment is usually a variable, but can also be a
-'MEM_REF' or a compound lvalue as described below.
+`MEM_REF' or a compound lvalue as described below.
* Menu:
@@ -11091,7 +11220,7 @@ File: gccint.info, Node: Compound Lvalues, Next: Conditional Expressions, Pre
-----------------------
Currently compound lvalues involving array and structure field
-references are not broken down; an expression like 'a.b[2] = 42' is not
+references are not broken down; an expression like `a.b[2] = 42' is not
reduced any further (though complex array subscripts are). This
restriction is a workaround for limitations in later optimizers; if we
were to convert this to
@@ -11099,9 +11228,9 @@ were to convert this to
T1 = &a.b;
T1[2] = 42;
- alias analysis would not remember that the reference to 'T1[2]' came by
-way of 'a.b', so it would think that the assignment could alias another
-member of 'a'; this broke 'struct-alias-1.c'. Future optimizer
+ alias analysis would not remember that the reference to `T1[2]' came
+by way of `a.b', so it would think that the assignment could alias
+another member of `a'; this broke `struct-alias-1.c'. Future optimizer
improvements may make this limitation unnecessary.

@@ -11110,8 +11239,8 @@ File: gccint.info, Node: Conditional Expressions, Next: Logical Operators, Pr
11.6.3 Conditional Expressions
------------------------------
-A C '?:' expression is converted into an 'if' statement with each branch
-assigning to the same temporary. So,
+A C `?:' expression is converted into an `if' statement with each
+branch assigning to the same temporary. So,
a = b ? c : d;
becomes
@@ -11121,12 +11250,12 @@ assigning to the same temporary. So,
T1 = d;
a = T1;
- The GIMPLE level if-conversion pass re-introduces '?:' expression, if
-appropriate. It is used to vectorize loops with conditions using vector
+ The GIMPLE level if-conversion pass re-introduces `?:' expression, if
+appropriate. It is used to vectorize loops with conditions using vector
conditional operations.
- Note that in GIMPLE, 'if' statements are represented using
-'GIMPLE_COND', as described below.
+ Note that in GIMPLE, `if' statements are represented using
+`GIMPLE_COND', as described below.

File: gccint.info, Node: Logical Operators, Prev: Conditional Expressions, Up: Operands
@@ -11134,53 +11263,53 @@ File: gccint.info, Node: Logical Operators, Prev: Conditional Expressions, Up
11.6.4 Logical Operators
------------------------
-Except when they appear in the condition operand of a 'GIMPLE_COND',
-logical 'and' and 'or' operators are simplified as follows: 'a = b && c'
-becomes
+Except when they appear in the condition operand of a `GIMPLE_COND',
+logical `and' and `or' operators are simplified as follows: `a = b &&
+c' becomes
T1 = (bool)b;
if (T1 == true)
T1 = (bool)c;
a = T1;
- Note that 'T1' in this example cannot be an expression temporary,
+ Note that `T1' in this example cannot be an expression temporary,
because it has two different assignments.
11.6.5 Manipulating operands
----------------------------
-All gimple operands are of type 'tree'. But only certain types of trees
-are allowed to be used as operand tuples. Basic validation is
-controlled by the function 'get_gimple_rhs_class', which given a tree
-code, returns an 'enum' with the following values of type 'enum
+All gimple operands are of type `tree'. But only certain types of
+trees are allowed to be used as operand tuples. Basic validation is
+controlled by the function `get_gimple_rhs_class', which given a tree
+code, returns an `enum' with the following values of type `enum
gimple_rhs_class'
- * 'GIMPLE_INVALID_RHS' The tree cannot be used as a GIMPLE operand.
+ * `GIMPLE_INVALID_RHS' The tree cannot be used as a GIMPLE operand.
- * 'GIMPLE_TERNARY_RHS' The tree is a valid GIMPLE ternary operation.
+ * `GIMPLE_TERNARY_RHS' The tree is a valid GIMPLE ternary operation.
- * 'GIMPLE_BINARY_RHS' The tree is a valid GIMPLE binary operation.
+ * `GIMPLE_BINARY_RHS' The tree is a valid GIMPLE binary operation.
- * 'GIMPLE_UNARY_RHS' The tree is a valid GIMPLE unary operation.
+ * `GIMPLE_UNARY_RHS' The tree is a valid GIMPLE unary operation.
- * 'GIMPLE_SINGLE_RHS' The tree is a single object, that cannot be
- split into simpler operands (for instance, 'SSA_NAME', 'VAR_DECL',
- 'COMPONENT_REF', etc).
+ * `GIMPLE_SINGLE_RHS' The tree is a single object, that cannot be
+ split into simpler operands (for instance, `SSA_NAME', `VAR_DECL',
+ `COMPONENT_REF', etc).
- This operand class also acts as an escape hatch for tree nodes that
- may be flattened out into the operand vector, but would need more
- than two slots on the RHS. For instance, a 'COND_EXPR' expression
- of the form '(a op b) ? x : y' could be flattened out on the
- operand vector using 4 slots, but it would also require additional
- processing to distinguish 'c = a op b' from 'c = a op b ? x : y'.
- Something similar occurs with 'ASSERT_EXPR'. In time, these
- special case tree expressions should be flattened into the operand
- vector.
+ This operand class also acts as an escape hatch for tree nodes
+ that may be flattened out into the operand vector, but would need
+ more than two slots on the RHS. For instance, a `COND_EXPR'
+ expression of the form `(a op b) ? x : y' could be flattened out
+ on the operand vector using 4 slots, but it would also require
+ additional processing to distinguish `c = a op b' from `c = a op b
+ ? x : y'. Something similar occurs with `ASSERT_EXPR'. In time,
+ these special case tree expressions should be flattened into the
+ operand vector.
- For tree nodes in the categories 'GIMPLE_TERNARY_RHS',
-'GIMPLE_BINARY_RHS' and 'GIMPLE_UNARY_RHS', they cannot be stored inside
-tuples directly. They first need to be flattened and separated into
-individual components. For instance, given the GENERIC expression
+ For tree nodes in the categories `GIMPLE_TERNARY_RHS',
+`GIMPLE_BINARY_RHS' and `GIMPLE_UNARY_RHS', they cannot be stored
+inside tuples directly. They first need to be flattened and separated
+into individual components. For instance, given the GENERIC expression
a = b + c
@@ -11188,42 +11317,43 @@ individual components. For instance, given the GENERIC expression
MODIFY_EXPR <VAR_DECL <a>, PLUS_EXPR <VAR_DECL <b>, VAR_DECL <c>>>
- In this case, the GIMPLE form for this statement is logically identical
-to its GENERIC form but in GIMPLE, the 'PLUS_EXPR' on the RHS of the
-assignment is not represented as a tree, instead the two operands are
-taken out of the 'PLUS_EXPR' sub-tree and flattened into the GIMPLE
-tuple as follows:
+ In this case, the GIMPLE form for this statement is logically
+identical to its GENERIC form but in GIMPLE, the `PLUS_EXPR' on the RHS
+of the assignment is not represented as a tree, instead the two
+operands are taken out of the `PLUS_EXPR' sub-tree and flattened into
+the GIMPLE tuple as follows:
GIMPLE_ASSIGN <PLUS_EXPR, VAR_DECL <a>, VAR_DECL <b>, VAR_DECL <c>>
11.6.6 Operand vector allocation
--------------------------------
-The operand vector is stored at the bottom of the three tuple structures
-that accept operands. This means, that depending on the code of a given
-statement, its operand vector will be at different offsets from the base
-of the structure. To access tuple operands use the following accessors
+The operand vector is stored at the bottom of the three tuple
+structures that accept operands. This means, that depending on the code
+of a given statement, its operand vector will be at different offsets
+from the base of the structure. To access tuple operands use the
+following accessors
-- GIMPLE function: unsigned gimple_num_ops (gimple g)
Returns the number of operands in statement G.
-- GIMPLE function: tree gimple_op (gimple g, unsigned i)
- Returns operand 'I' from statement 'G'.
+ Returns operand `I' from statement `G'.
-- GIMPLE function: tree * gimple_ops (gimple g)
- Returns a pointer into the operand vector for statement 'G'. This
- is computed using an internal table called 'gimple_ops_offset_'[].
- This table is indexed by the gimple code of 'G'.
+ Returns a pointer into the operand vector for statement `G'. This
+ is computed using an internal table called `gimple_ops_offset_'[].
+ This table is indexed by the gimple code of `G'.
- When the compiler is built, this table is filled-in using the sizes
- of the structures used by each statement code defined in
+ When the compiler is built, this table is filled-in using the
+ sizes of the structures used by each statement code defined in
gimple.def. Since the operand vector is at the bottom of the
- structure, for a gimple code 'C' the offset is computed as sizeof
- (struct-of 'C') - sizeof (tree).
+ structure, for a gimple code `C' the offset is computed as sizeof
+ (struct-of `C') - sizeof (tree).
This mechanism adds one memory indirection to every access when
- using 'gimple_op'(), if this becomes a bottleneck, a pass can
- choose to memoize the result from 'gimple_ops'() and use that to
+ using `gimple_op'(), if this becomes a bottleneck, a pass can
+ choose to memoize the result from `gimple_ops'() and use that to
access the operands.
11.6.7 Operand validation
@@ -11231,67 +11361,67 @@ of the structure. To access tuple operands use the following accessors
When adding a new operand to a gimple statement, the operand will be
validated according to what each tuple accepts in its operand vector.
-These predicates are called by the 'gimple_NAME_set_...()'. Each tuple
+These predicates are called by the `gimple_NAME_set_...()'. Each tuple
will use one of the following predicates (Note, this list is not
exhaustive):
-- GIMPLE function: bool is_gimple_val (tree t)
Returns true if t is a "GIMPLE value", which are all the
non-addressable stack variables (variables for which
- 'is_gimple_reg' returns true) and constants (expressions for which
- 'is_gimple_min_invariant' returns true).
+ `is_gimple_reg' returns true) and constants (expressions for which
+ `is_gimple_min_invariant' returns true).
-- GIMPLE function: bool is_gimple_addressable (tree t)
- Returns true if t is a symbol or memory reference whose address can
- be taken.
+ Returns true if t is a symbol or memory reference whose address
+ can be taken.
-- GIMPLE function: bool is_gimple_asm_val (tree t)
- Similar to 'is_gimple_val' but it also accepts hard registers.
+ Similar to `is_gimple_val' but it also accepts hard registers.
-- GIMPLE function: bool is_gimple_call_addr (tree t)
Return true if t is a valid expression to use as the function
- called by a 'GIMPLE_CALL'.
+ called by a `GIMPLE_CALL'.
-- GIMPLE function: bool is_gimple_mem_ref_addr (tree t)
- Return true if t is a valid expression to use as first operand of a
- 'MEM_REF' expression.
+ Return true if t is a valid expression to use as first operand of
+ a `MEM_REF' expression.
-- GIMPLE function: bool is_gimple_constant (tree t)
Return true if t is a valid gimple constant.
-- GIMPLE function: bool is_gimple_min_invariant (tree t)
Return true if t is a valid minimal invariant. This is different
- from constants, in that the specific value of t may not be known at
- compile time, but it is known that it doesn't change (e.g., the
+ from constants, in that the specific value of t may not be known
+ at compile time, but it is known that it doesn't change (e.g., the
address of a function local variable).
-- GIMPLE function: bool is_gimple_ip_invariant (tree t)
Return true if t is an interprocedural invariant. This means that
- t is a valid invariant in all functions (e.g. it can be an address
+ t is a valid invariant in all functions (e.g. it can be an address
of a global variable but not of a local one).
-- GIMPLE function: bool is_gimple_ip_invariant_address (tree t)
- Return true if t is an 'ADDR_EXPR' that does not change once the
+ Return true if t is an `ADDR_EXPR' that does not change once the
program is running (and which is valid in all functions).
11.6.8 Statement validation
---------------------------
-- GIMPLE function: bool is_gimple_assign (gimple g)
- Return true if the code of g is 'GIMPLE_ASSIGN'.
+ Return true if the code of g is `GIMPLE_ASSIGN'.
-- GIMPLE function: bool is_gimple_call (gimple g)
- Return true if the code of g is 'GIMPLE_CALL'.
+ Return true if the code of g is `GIMPLE_CALL'.
-- GIMPLE function: bool is_gimple_debug (gimple g)
- Return true if the code of g is 'GIMPLE_DEBUG'.
+ Return true if the code of g is `GIMPLE_DEBUG'.
-- GIMPLE function: bool gimple_assign_cast_p (const_gimple g)
- Return true if g is a 'GIMPLE_ASSIGN' that performs a type cast
+ Return true if g is a `GIMPLE_ASSIGN' that performs a type cast
operation.
-- GIMPLE function: bool gimple_debug_bind_p (gimple g)
- Return true if g is a 'GIMPLE_DEBUG' that binds the value of an
+ Return true if g is a `GIMPLE_DEBUG' that binds the value of an
expression to a variable.
-- GIMPLE function: bool is_gimple_omp (gimple g)
@@ -11303,8 +11433,8 @@ File: gccint.info, Node: Manipulating GIMPLE statements, Next: Tuple specific
11.7 Manipulating GIMPLE statements
===================================
-This section documents all the functions available to handle each of the
-GIMPLE instructions.
+This section documents all the functions available to handle each of
+the GIMPLE instructions.
11.7.1 Common accessors
-----------------------
@@ -11312,139 +11442,139 @@ GIMPLE instructions.
The following are common accessors for gimple statements.
-- GIMPLE function: enum gimple_code gimple_code (gimple g)
- Return the code for statement 'G'.
+ Return the code for statement `G'.
-- GIMPLE function: basic_block gimple_bb (gimple g)
- Return the basic block to which statement 'G' belongs to.
+ Return the basic block to which statement `G' belongs to.
-- GIMPLE function: tree gimple_block (gimple g)
- Return the lexical scope block holding statement 'G'.
+ Return the lexical scope block holding statement `G'.
-- GIMPLE function: tree gimple_expr_type (gimple stmt)
- Return the type of the main expression computed by 'STMT'. Return
- 'void_type_node' if 'STMT' computes nothing. This will only return
- something meaningful for 'GIMPLE_ASSIGN', 'GIMPLE_COND' and
- 'GIMPLE_CALL'. For all other tuple codes, it will return
- 'void_type_node'.
+ Return the type of the main expression computed by `STMT'. Return
+ `void_type_node' if `STMT' computes nothing. This will only return
+ something meaningful for `GIMPLE_ASSIGN', `GIMPLE_COND' and
+ `GIMPLE_CALL'. For all other tuple codes, it will return
+ `void_type_node'.
-- GIMPLE function: enum tree_code gimple_expr_code (gimple stmt)
- Return the tree code for the expression computed by 'STMT'. This
- is only meaningful for 'GIMPLE_CALL', 'GIMPLE_ASSIGN' and
- 'GIMPLE_COND'. If 'STMT' is 'GIMPLE_CALL', it will return
- 'CALL_EXPR'. For 'GIMPLE_COND', it returns the code of the
- comparison predicate. For 'GIMPLE_ASSIGN' it returns the code of
- the operation performed by the 'RHS' of the assignment.
+ Return the tree code for the expression computed by `STMT'. This
+ is only meaningful for `GIMPLE_CALL', `GIMPLE_ASSIGN' and
+ `GIMPLE_COND'. If `STMT' is `GIMPLE_CALL', it will return
+ `CALL_EXPR'. For `GIMPLE_COND', it returns the code of the
+ comparison predicate. For `GIMPLE_ASSIGN' it returns the code of
+ the operation performed by the `RHS' of the assignment.
-- GIMPLE function: void gimple_set_block (gimple g, tree block)
- Set the lexical scope block of 'G' to 'BLOCK'.
+ Set the lexical scope block of `G' to `BLOCK'.
-- GIMPLE function: location_t gimple_locus (gimple g)
- Return locus information for statement 'G'.
+ Return locus information for statement `G'.
-- GIMPLE function: void gimple_set_locus (gimple g, location_t locus)
- Set locus information for statement 'G'.
+ Set locus information for statement `G'.
-- GIMPLE function: bool gimple_locus_empty_p (gimple g)
- Return true if 'G' does not have locus information.
+ Return true if `G' does not have locus information.
-- GIMPLE function: bool gimple_no_warning_p (gimple stmt)
- Return true if no warnings should be emitted for statement 'STMT'.
+ Return true if no warnings should be emitted for statement `STMT'.
-- GIMPLE function: void gimple_set_visited (gimple stmt, bool
visited_p)
- Set the visited status on statement 'STMT' to 'VISITED_P'.
+ Set the visited status on statement `STMT' to `VISITED_P'.
-- GIMPLE function: bool gimple_visited_p (gimple stmt)
- Return the visited status on statement 'STMT'.
+ Return the visited status on statement `STMT'.
-- GIMPLE function: void gimple_set_plf (gimple stmt, enum plf_mask
plf, bool val_p)
- Set pass local flag 'PLF' on statement 'STMT' to 'VAL_P'.
+ Set pass local flag `PLF' on statement `STMT' to `VAL_P'.
- -- GIMPLE function: unsigned int gimple_plf (gimple stmt, enum plf_mask
- plf)
- Return the value of pass local flag 'PLF' on statement 'STMT'.
+ -- GIMPLE function: unsigned int gimple_plf (gimple stmt, enum
+ plf_mask plf)
+ Return the value of pass local flag `PLF' on statement `STMT'.
-- GIMPLE function: bool gimple_has_ops (gimple g)
- Return true if statement 'G' has register or memory operands.
+ Return true if statement `G' has register or memory operands.
-- GIMPLE function: bool gimple_has_mem_ops (gimple g)
- Return true if statement 'G' has memory operands.
+ Return true if statement `G' has memory operands.
-- GIMPLE function: unsigned gimple_num_ops (gimple g)
- Return the number of operands for statement 'G'.
+ Return the number of operands for statement `G'.
-- GIMPLE function: tree * gimple_ops (gimple g)
- Return the array of operands for statement 'G'.
+ Return the array of operands for statement `G'.
-- GIMPLE function: tree gimple_op (gimple g, unsigned i)
- Return operand 'I' for statement 'G'.
+ Return operand `I' for statement `G'.
-- GIMPLE function: tree * gimple_op_ptr (gimple g, unsigned i)
- Return a pointer to operand 'I' for statement 'G'.
+ Return a pointer to operand `I' for statement `G'.
-- GIMPLE function: void gimple_set_op (gimple g, unsigned i, tree op)
- Set operand 'I' of statement 'G' to 'OP'.
+ Set operand `I' of statement `G' to `OP'.
-- GIMPLE function: bitmap gimple_addresses_taken (gimple stmt)
Return the set of symbols that have had their address taken by
- 'STMT'.
+ `STMT'.
-- GIMPLE function: struct def_optype_d * gimple_def_ops (gimple g)
- Return the set of 'DEF' operands for statement 'G'.
+ Return the set of `DEF' operands for statement `G'.
-- GIMPLE function: void gimple_set_def_ops (gimple g, struct
def_optype_d *def)
- Set 'DEF' to be the set of 'DEF' operands for statement 'G'.
+ Set `DEF' to be the set of `DEF' operands for statement `G'.
-- GIMPLE function: struct use_optype_d * gimple_use_ops (gimple g)
- Return the set of 'USE' operands for statement 'G'.
+ Return the set of `USE' operands for statement `G'.
-- GIMPLE function: void gimple_set_use_ops (gimple g, struct
use_optype_d *use)
- Set 'USE' to be the set of 'USE' operands for statement 'G'.
+ Set `USE' to be the set of `USE' operands for statement `G'.
-- GIMPLE function: struct voptype_d * gimple_vuse_ops (gimple g)
- Return the set of 'VUSE' operands for statement 'G'.
+ Return the set of `VUSE' operands for statement `G'.
-- GIMPLE function: void gimple_set_vuse_ops (gimple g, struct
voptype_d *ops)
- Set 'OPS' to be the set of 'VUSE' operands for statement 'G'.
+ Set `OPS' to be the set of `VUSE' operands for statement `G'.
-- GIMPLE function: struct voptype_d * gimple_vdef_ops (gimple g)
- Return the set of 'VDEF' operands for statement 'G'.
+ Return the set of `VDEF' operands for statement `G'.
-- GIMPLE function: void gimple_set_vdef_ops (gimple g, struct
voptype_d *ops)
- Set 'OPS' to be the set of 'VDEF' operands for statement 'G'.
+ Set `OPS' to be the set of `VDEF' operands for statement `G'.
-- GIMPLE function: bitmap gimple_loaded_syms (gimple g)
- Return the set of symbols loaded by statement 'G'. Each element of
- the set is the 'DECL_UID' of the corresponding symbol.
+ Return the set of symbols loaded by statement `G'. Each element of
+ the set is the `DECL_UID' of the corresponding symbol.
-- GIMPLE function: bitmap gimple_stored_syms (gimple g)
- Return the set of symbols stored by statement 'G'. Each element of
- the set is the 'DECL_UID' of the corresponding symbol.
+ Return the set of symbols stored by statement `G'. Each element of
+ the set is the `DECL_UID' of the corresponding symbol.
-- GIMPLE function: bool gimple_modified_p (gimple g)
- Return true if statement 'G' has operands and the modified field
+ Return true if statement `G' has operands and the modified field
has been set.
-- GIMPLE function: bool gimple_has_volatile_ops (gimple stmt)
- Return true if statement 'STMT' contains volatile operands.
+ Return true if statement `STMT' contains volatile operands.
- -- GIMPLE function: void gimple_set_has_volatile_ops (gimple stmt, bool
- volatilep)
- Return true if statement 'STMT' contains volatile operands.
+ -- GIMPLE function: void gimple_set_has_volatile_ops (gimple stmt,
+ bool volatilep)
+ Return true if statement `STMT' contains volatile operands.
-- GIMPLE function: void update_stmt (gimple s)
- Mark statement 'S' as modified, and update it.
+ Mark statement `S' as modified, and update it.
-- GIMPLE function: void update_stmt_if_modified (gimple s)
- Update statement 'S' if it has been marked modified.
+ Update statement `S' if it has been marked modified.
-- GIMPLE function: gimple gimple_copy (gimple stmt)
- Return a deep copy of statement 'STMT'.
+ Return a deep copy of statement `STMT'.

File: gccint.info, Node: Tuple specific accessors, Next: GIMPLE sequences, Prev: Manipulating GIMPLE statements, Up: GIMPLE
@@ -11454,547 +11584,548 @@ File: gccint.info, Node: Tuple specific accessors, Next: GIMPLE sequences, Pr
* Menu:
-* 'GIMPLE_ASM'::
-* 'GIMPLE_ASSIGN'::
-* 'GIMPLE_BIND'::
-* 'GIMPLE_CALL'::
-* 'GIMPLE_CATCH'::
-* 'GIMPLE_COND'::
-* 'GIMPLE_DEBUG'::
-* 'GIMPLE_EH_FILTER'::
-* 'GIMPLE_LABEL'::
-* 'GIMPLE_GOTO'::
-* 'GIMPLE_NOP'::
-* 'GIMPLE_OMP_ATOMIC_LOAD'::
-* 'GIMPLE_OMP_ATOMIC_STORE'::
-* 'GIMPLE_OMP_CONTINUE'::
-* 'GIMPLE_OMP_CRITICAL'::
-* 'GIMPLE_OMP_FOR'::
-* 'GIMPLE_OMP_MASTER'::
-* 'GIMPLE_OMP_ORDERED'::
-* 'GIMPLE_OMP_PARALLEL'::
-* 'GIMPLE_OMP_RETURN'::
-* 'GIMPLE_OMP_SECTION'::
-* 'GIMPLE_OMP_SECTIONS'::
-* 'GIMPLE_OMP_SINGLE'::
-* 'GIMPLE_PHI'::
-* 'GIMPLE_RESX'::
-* 'GIMPLE_RETURN'::
-* 'GIMPLE_SWITCH'::
-* 'GIMPLE_TRY'::
-* 'GIMPLE_WITH_CLEANUP_EXPR'::
-
-
-File: gccint.info, Node: 'GIMPLE_ASM', Next: 'GIMPLE_ASSIGN', Up: Tuple specific accessors
-
-11.8.1 'GIMPLE_ASM'
+* `GIMPLE_ASM'::
+* `GIMPLE_ASSIGN'::
+* `GIMPLE_BIND'::
+* `GIMPLE_CALL'::
+* `GIMPLE_CATCH'::
+* `GIMPLE_COND'::
+* `GIMPLE_DEBUG'::
+* `GIMPLE_EH_FILTER'::
+* `GIMPLE_LABEL'::
+* `GIMPLE_GOTO'::
+* `GIMPLE_NOP'::
+* `GIMPLE_OMP_ATOMIC_LOAD'::
+* `GIMPLE_OMP_ATOMIC_STORE'::
+* `GIMPLE_OMP_CONTINUE'::
+* `GIMPLE_OMP_CRITICAL'::
+* `GIMPLE_OMP_FOR'::
+* `GIMPLE_OMP_MASTER'::
+* `GIMPLE_OMP_ORDERED'::
+* `GIMPLE_OMP_PARALLEL'::
+* `GIMPLE_OMP_RETURN'::
+* `GIMPLE_OMP_SECTION'::
+* `GIMPLE_OMP_SECTIONS'::
+* `GIMPLE_OMP_SINGLE'::
+* `GIMPLE_PHI'::
+* `GIMPLE_RESX'::
+* `GIMPLE_RETURN'::
+* `GIMPLE_SWITCH'::
+* `GIMPLE_TRY'::
+* `GIMPLE_WITH_CLEANUP_EXPR'::
+
+
+File: gccint.info, Node: `GIMPLE_ASM', Next: `GIMPLE_ASSIGN', Up: Tuple specific accessors
+
+11.8.1 `GIMPLE_ASM'
-------------------
-- GIMPLE function: gasm *gimple_build_asm_vec ( const char *string,
- vec<tree, va_gc> *inputs, vec<tree, va_gc> *outputs, vec<tree,
- va_gc> *clobbers, vec<tree, va_gc> *labels)
- Build a 'GIMPLE_ASM' statement. This statement is used for
- building in-line assembly constructs. 'STRING' is the assembly
- code. 'INPUTS', 'OUTPUTS', 'CLOBBERS' and 'LABELS' are the inputs,
- outputs, clobbered registers and labels.
+ vec<tree, va_gc> *inputs, vec<tree, va_gc> *outputs,
+ vec<tree, va_gc> *clobbers, vec<tree, va_gc> *labels)
+ Build a `GIMPLE_ASM' statement. This statement is used for
+ building in-line assembly constructs. `STRING' is the assembly
+ code. `INPUTS', `OUTPUTS', `CLOBBERS' and `LABELS' are the
+ inputs, outputs, clobbered registers and labels.
-- GIMPLE function: unsigned gimple_asm_ninputs (const gasm *g)
- Return the number of input operands for 'GIMPLE_ASM' 'G'.
+ Return the number of input operands for `GIMPLE_ASM' `G'.
-- GIMPLE function: unsigned gimple_asm_noutputs (const gasm *g)
- Return the number of output operands for 'GIMPLE_ASM' 'G'.
+ Return the number of output operands for `GIMPLE_ASM' `G'.
-- GIMPLE function: unsigned gimple_asm_nclobbers (const gasm *g)
- Return the number of clobber operands for 'GIMPLE_ASM' 'G'.
+ Return the number of clobber operands for `GIMPLE_ASM' `G'.
-- GIMPLE function: tree gimple_asm_input_op (const gasm *g, unsigned
index)
- Return input operand 'INDEX' of 'GIMPLE_ASM' 'G'.
+ Return input operand `INDEX' of `GIMPLE_ASM' `G'.
-- GIMPLE function: void gimple_asm_set_input_op (gasm *g, unsigned
index, tree in_op)
- Set 'IN_OP' to be input operand 'INDEX' in 'GIMPLE_ASM' 'G'.
+ Set `IN_OP' to be input operand `INDEX' in `GIMPLE_ASM' `G'.
-- GIMPLE function: tree gimple_asm_output_op (const gasm *g, unsigned
index)
- Return output operand 'INDEX' of 'GIMPLE_ASM' 'G'.
+ Return output operand `INDEX' of `GIMPLE_ASM' `G'.
-- GIMPLE function: void gimple_asm_set_output_op (gasm *g, unsigned
index, tree out_op)
- Set 'OUT_OP' to be output operand 'INDEX' in 'GIMPLE_ASM' 'G'.
+ Set `OUT_OP' to be output operand `INDEX' in `GIMPLE_ASM' `G'.
- -- GIMPLE function: tree gimple_asm_clobber_op (const gasm *g, unsigned
- index)
- Return clobber operand 'INDEX' of 'GIMPLE_ASM' 'G'.
+ -- GIMPLE function: tree gimple_asm_clobber_op (const gasm *g,
+ unsigned index)
+ Return clobber operand `INDEX' of `GIMPLE_ASM' `G'.
-- GIMPLE function: void gimple_asm_set_clobber_op (gasm *g, unsigned
index, tree clobber_op)
- Set 'CLOBBER_OP' to be clobber operand 'INDEX' in 'GIMPLE_ASM' 'G'.
+ Set `CLOBBER_OP' to be clobber operand `INDEX' in `GIMPLE_ASM' `G'.
-- GIMPLE function: const char * gimple_asm_string (const gasm *g)
Return the string representing the assembly instruction in
- 'GIMPLE_ASM' 'G'.
+ `GIMPLE_ASM' `G'.
-- GIMPLE function: bool gimple_asm_volatile_p (const gasm *g)
- Return true if 'G' is an asm statement marked volatile.
+ Return true if `G' is an asm statement marked volatile.
-- GIMPLE function: void gimple_asm_set_volatile (gasm *g, bool
volatile_p)
- Mark asm statement 'G' as volatile or non-volatile based on
- 'VOLATILE_P'.
+ Mark asm statement `G' as volatile or non-volatile based on
+ `VOLATILE_P'.

-File: gccint.info, Node: 'GIMPLE_ASSIGN', Next: 'GIMPLE_BIND', Prev: 'GIMPLE_ASM', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_ASSIGN', Next: `GIMPLE_BIND', Prev: `GIMPLE_ASM', Up: Tuple specific accessors
-11.8.2 'GIMPLE_ASSIGN'
+11.8.2 `GIMPLE_ASSIGN'
----------------------
-- GIMPLE function: gassign *gimple_build_assign (tree lhs, tree rhs)
- Build a 'GIMPLE_ASSIGN' statement. The left-hand side is an lvalue
- passed in lhs. The right-hand side can be either a unary or binary
- tree expression. The expression tree rhs will be flattened and its
- operands assigned to the corresponding operand slots in the new
- statement. This function is useful when you already have a tree
- expression that you want to convert into a tuple. However, try to
- avoid building expression trees for the sole purpose of calling
- this function. If you already have the operands in separate trees,
- it is better to use 'gimple_build_assign' with 'enum tree_code'
- argument and separate arguments for each operand.
+ Build a `GIMPLE_ASSIGN' statement. The left-hand side is an lvalue
+ passed in lhs. The right-hand side can be either a unary or
+ binary tree expression. The expression tree rhs will be flattened
+ and its operands assigned to the corresponding operand slots in
+ the new statement. This function is useful when you already have
+ a tree expression that you want to convert into a tuple. However,
+ try to avoid building expression trees for the sole purpose of
+ calling this function. If you already have the operands in
+ separate trees, it is better to use `gimple_build_assign' with
+ `enum tree_code' argument and separate arguments for each operand.
-- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum
tree_code subcode, tree op1, tree op2, tree op3)
- This function is similar to two operand 'gimple_build_assign', but
- is used to build a 'GIMPLE_ASSIGN' statement when the operands of
+ This function is similar to two operand `gimple_build_assign', but
+ is used to build a `GIMPLE_ASSIGN' statement when the operands of
the right-hand side of the assignment are already split into
different operands.
The left-hand side is an lvalue passed in lhs. Subcode is the
- 'tree_code' for the right-hand side of the assignment. Op1, op2
+ `tree_code' for the right-hand side of the assignment. Op1, op2
and op3 are the operands.
-- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum
tree_code subcode, tree op1, tree op2)
- Like the above 5 operand 'gimple_build_assign', but with the last
- argument 'NULL' - this overload should not be used for
- 'GIMPLE_TERNARY_RHS' assignments.
+ Like the above 5 operand `gimple_build_assign', but with the last
+ argument `NULL' - this overload should not be used for
+ `GIMPLE_TERNARY_RHS' assignments.
-- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum
tree_code subcode, tree op1)
- Like the above 4 operand 'gimple_build_assign', but with the last
- argument 'NULL' - this overload should be used only for
- 'GIMPLE_UNARY_RHS' and 'GIMPLE_SINGLE_RHS' assignments.
+ Like the above 4 operand `gimple_build_assign', but with the last
+ argument `NULL' - this overload should be used only for
+ `GIMPLE_UNARY_RHS' and `GIMPLE_SINGLE_RHS' assignments.
-- GIMPLE function: gimple gimplify_assign (tree dst, tree src,
gimple_seq *seq_p)
- Build a new 'GIMPLE_ASSIGN' tuple and append it to the end of
- '*SEQ_P'.
+ Build a new `GIMPLE_ASSIGN' tuple and append it to the end of
+ `*SEQ_P'.
- 'DST'/'SRC' are the destination and source respectively. You can pass
-ungimplified trees in 'DST' or 'SRC', in which case they will be
+ `DST'/`SRC' are the destination and source respectively. You can pass
+ungimplified trees in `DST' or `SRC', in which case they will be
converted to a gimple operand if necessary.
- This function returns the newly created 'GIMPLE_ASSIGN' tuple.
+ This function returns the newly created `GIMPLE_ASSIGN' tuple.
-- GIMPLE function: enum tree_code gimple_assign_rhs_code (gimple g)
- Return the code of the expression computed on the 'RHS' of
- assignment statement 'G'.
+ Return the code of the expression computed on the `RHS' of
+ assignment statement `G'.
-- GIMPLE function: enum gimple_rhs_class gimple_assign_rhs_class
(gimple g)
- Return the gimple rhs class of the code for the expression computed
- on the rhs of assignment statement 'G'. This will never return
- 'GIMPLE_INVALID_RHS'.
+ Return the gimple rhs class of the code for the expression
+ computed on the rhs of assignment statement `G'. This will never
+ return `GIMPLE_INVALID_RHS'.
-- GIMPLE function: tree gimple_assign_lhs (gimple g)
- Return the 'LHS' of assignment statement 'G'.
+ Return the `LHS' of assignment statement `G'.
-- GIMPLE function: tree * gimple_assign_lhs_ptr (gimple g)
- Return a pointer to the 'LHS' of assignment statement 'G'.
+ Return a pointer to the `LHS' of assignment statement `G'.
-- GIMPLE function: tree gimple_assign_rhs1 (gimple g)
- Return the first operand on the 'RHS' of assignment statement 'G'.
+ Return the first operand on the `RHS' of assignment statement `G'.
-- GIMPLE function: tree * gimple_assign_rhs1_ptr (gimple g)
- Return the address of the first operand on the 'RHS' of assignment
- statement 'G'.
+ Return the address of the first operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: tree gimple_assign_rhs2 (gimple g)
- Return the second operand on the 'RHS' of assignment statement 'G'.
+ Return the second operand on the `RHS' of assignment statement `G'.
-- GIMPLE function: tree * gimple_assign_rhs2_ptr (gimple g)
- Return the address of the second operand on the 'RHS' of assignment
- statement 'G'.
+ Return the address of the second operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: tree gimple_assign_rhs3 (gimple g)
- Return the third operand on the 'RHS' of assignment statement 'G'.
+ Return the third operand on the `RHS' of assignment statement `G'.
-- GIMPLE function: tree * gimple_assign_rhs3_ptr (gimple g)
- Return the address of the third operand on the 'RHS' of assignment
- statement 'G'.
+ Return the address of the third operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: void gimple_assign_set_lhs (gimple g, tree lhs)
- Set 'LHS' to be the 'LHS' operand of assignment statement 'G'.
+ Set `LHS' to be the `LHS' operand of assignment statement `G'.
-- GIMPLE function: void gimple_assign_set_rhs1 (gimple g, tree rhs)
- Set 'RHS' to be the first operand on the 'RHS' of assignment
- statement 'G'.
+ Set `RHS' to be the first operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: void gimple_assign_set_rhs2 (gimple g, tree rhs)
- Set 'RHS' to be the second operand on the 'RHS' of assignment
- statement 'G'.
+ Set `RHS' to be the second operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: void gimple_assign_set_rhs3 (gimple g, tree rhs)
- Set 'RHS' to be the third operand on the 'RHS' of assignment
- statement 'G'.
+ Set `RHS' to be the third operand on the `RHS' of assignment
+ statement `G'.
-- GIMPLE function: bool gimple_assign_cast_p (const_gimple s)
- Return true if 'S' is a type-cast assignment.
+ Return true if `S' is a type-cast assignment.

-File: gccint.info, Node: 'GIMPLE_BIND', Next: 'GIMPLE_CALL', Prev: 'GIMPLE_ASSIGN', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_BIND', Next: `GIMPLE_CALL', Prev: `GIMPLE_ASSIGN', Up: Tuple specific accessors
-11.8.3 'GIMPLE_BIND'
+11.8.3 `GIMPLE_BIND'
--------------------
-- GIMPLE function: gbind *gimple_build_bind (tree vars, gimple_seq
body)
- Build a 'GIMPLE_BIND' statement with a list of variables in 'VARS'
- and a body of statements in sequence 'BODY'.
+ Build a `GIMPLE_BIND' statement with a list of variables in `VARS'
+ and a body of statements in sequence `BODY'.
-- GIMPLE function: tree gimple_bind_vars (const gbind *g)
- Return the variables declared in the 'GIMPLE_BIND' statement 'G'.
+ Return the variables declared in the `GIMPLE_BIND' statement `G'.
-- GIMPLE function: void gimple_bind_set_vars (gbind *g, tree vars)
- Set 'VARS' to be the set of variables declared in the 'GIMPLE_BIND'
- statement 'G'.
+ Set `VARS' to be the set of variables declared in the `GIMPLE_BIND'
+ statement `G'.
-- GIMPLE function: void gimple_bind_append_vars (gbind *g, tree vars)
- Append 'VARS' to the set of variables declared in the 'GIMPLE_BIND'
- statement 'G'.
+ Append `VARS' to the set of variables declared in the `GIMPLE_BIND'
+ statement `G'.
-- GIMPLE function: gimple_seq gimple_bind_body (gbind *g)
- Return the GIMPLE sequence contained in the 'GIMPLE_BIND' statement
- 'G'.
+ Return the GIMPLE sequence contained in the `GIMPLE_BIND' statement
+ `G'.
-- GIMPLE function: void gimple_bind_set_body (gbind *g, gimple_seq
seq)
- Set 'SEQ' to be sequence contained in the 'GIMPLE_BIND' statement
- 'G'.
+ Set `SEQ' to be sequence contained in the `GIMPLE_BIND' statement
+ `G'.
-- GIMPLE function: void gimple_bind_add_stmt (gbind *gs, gimple stmt)
- Append a statement to the end of a 'GIMPLE_BIND''s body.
+ Append a statement to the end of a `GIMPLE_BIND''s body.
-- GIMPLE function: void gimple_bind_add_seq (gbind *gs, gimple_seq
seq)
- Append a sequence of statements to the end of a 'GIMPLE_BIND''s
+ Append a sequence of statements to the end of a `GIMPLE_BIND''s
body.
-- GIMPLE function: tree gimple_bind_block (const gbind *g)
- Return the 'TREE_BLOCK' node associated with 'GIMPLE_BIND'
- statement 'G'. This is analogous to the 'BIND_EXPR_BLOCK' field in
+ Return the `TREE_BLOCK' node associated with `GIMPLE_BIND'
+ statement `G'. This is analogous to the `BIND_EXPR_BLOCK' field in
trees.
-- GIMPLE function: void gimple_bind_set_block (gbind *g, tree block)
- Set 'BLOCK' to be the 'TREE_BLOCK' node associated with
- 'GIMPLE_BIND' statement 'G'.
+ Set `BLOCK' to be the `TREE_BLOCK' node associated with
+ `GIMPLE_BIND' statement `G'.

-File: gccint.info, Node: 'GIMPLE_CALL', Next: 'GIMPLE_CATCH', Prev: 'GIMPLE_BIND', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_CALL', Next: `GIMPLE_CATCH', Prev: `GIMPLE_BIND', Up: Tuple specific accessors
-11.8.4 'GIMPLE_CALL'
+11.8.4 `GIMPLE_CALL'
--------------------
-- GIMPLE function: gcall *gimple_build_call (tree fn, unsigned nargs,
...)
- Build a 'GIMPLE_CALL' statement to function 'FN'. The argument
- 'FN' must be either a 'FUNCTION_DECL' or a gimple call address as
- determined by 'is_gimple_call_addr'. 'NARGS' are the number of
- arguments. The rest of the arguments follow the argument 'NARGS',
+ Build a `GIMPLE_CALL' statement to function `FN'. The argument
+ `FN' must be either a `FUNCTION_DECL' or a gimple call address as
+ determined by `is_gimple_call_addr'. `NARGS' are the number of
+ arguments. The rest of the arguments follow the argument `NARGS',
and must be trees that are valid as rvalues in gimple (i.e., each
- operand is validated with 'is_gimple_operand').
+ operand is validated with `is_gimple_operand').
-- GIMPLE function: gcall *gimple_build_call_from_tree (tree call_expr)
- Build a 'GIMPLE_CALL' from a 'CALL_EXPR' node. The arguments and
+ Build a `GIMPLE_CALL' from a `CALL_EXPR' node. The arguments and
the function are taken from the expression directly. This routine
- assumes that 'call_expr' is already in GIMPLE form. That is, its
+ assumes that `call_expr' is already in GIMPLE form. That is, its
operands are GIMPLE values and the function call needs no further
- simplification. All the call flags in 'call_expr' are copied over
- to the new 'GIMPLE_CALL'.
+ simplification. All the call flags in `call_expr' are copied over
+ to the new `GIMPLE_CALL'.
- -- GIMPLE function: gcall *gimple_build_call_vec (tree fn, 'vec<tree>'
+ -- GIMPLE function: gcall *gimple_build_call_vec (tree fn, `vec<tree>'
args)
- Identical to 'gimple_build_call' but the arguments are stored in a
- 'vec<tree>'.
+ Identical to `gimple_build_call' but the arguments are stored in a
+ `vec<tree>'.
-- GIMPLE function: tree gimple_call_lhs (gimple g)
- Return the 'LHS' of call statement 'G'.
+ Return the `LHS' of call statement `G'.
-- GIMPLE function: tree * gimple_call_lhs_ptr (gimple g)
- Return a pointer to the 'LHS' of call statement 'G'.
+ Return a pointer to the `LHS' of call statement `G'.
-- GIMPLE function: void gimple_call_set_lhs (gimple g, tree lhs)
- Set 'LHS' to be the 'LHS' operand of call statement 'G'.
+ Set `LHS' to be the `LHS' operand of call statement `G'.
-- GIMPLE function: tree gimple_call_fn (gimple g)
Return the tree node representing the function called by call
- statement 'G'.
+ statement `G'.
-- GIMPLE function: void gimple_call_set_fn (gcall *g, tree fn)
- Set 'FN' to be the function called by call statement 'G'. This has
+ Set `FN' to be the function called by call statement `G'. This has
to be a gimple value specifying the address of the called function.
-- GIMPLE function: tree gimple_call_fndecl (gimple g)
- If a given 'GIMPLE_CALL''s callee is a 'FUNCTION_DECL', return it.
- Otherwise return 'NULL'. This function is analogous to
- 'get_callee_fndecl' in 'GENERIC'.
+ If a given `GIMPLE_CALL''s callee is a `FUNCTION_DECL', return it.
+ Otherwise return `NULL'. This function is analogous to
+ `get_callee_fndecl' in `GENERIC'.
-- GIMPLE function: tree gimple_call_set_fndecl (gimple g, tree fndecl)
- Set the called function to 'FNDECL'.
+ Set the called function to `FNDECL'.
-- GIMPLE function: tree gimple_call_return_type (const gcall *g)
- Return the type returned by call statement 'G'.
+ Return the type returned by call statement `G'.
-- GIMPLE function: tree gimple_call_chain (gimple g)
- Return the static chain for call statement 'G'.
+ Return the static chain for call statement `G'.
-- GIMPLE function: void gimple_call_set_chain (gcall *g, tree chain)
- Set 'CHAIN' to be the static chain for call statement 'G'.
+ Set `CHAIN' to be the static chain for call statement `G'.
-- GIMPLE function: unsigned gimple_call_num_args (gimple g)
- Return the number of arguments used by call statement 'G'.
+ Return the number of arguments used by call statement `G'.
-- GIMPLE function: tree gimple_call_arg (gimple g, unsigned index)
- Return the argument at position 'INDEX' for call statement 'G'.
+ Return the argument at position `INDEX' for call statement `G'.
The first argument is 0.
-- GIMPLE function: tree * gimple_call_arg_ptr (gimple g, unsigned
index)
- Return a pointer to the argument at position 'INDEX' for call
- statement 'G'.
+ Return a pointer to the argument at position `INDEX' for call
+ statement `G'.
- -- GIMPLE function: void gimple_call_set_arg (gimple g, unsigned index,
- tree arg)
- Set 'ARG' to be the argument at position 'INDEX' for call statement
- 'G'.
+ -- GIMPLE function: void gimple_call_set_arg (gimple g, unsigned
+ index, tree arg)
+ Set `ARG' to be the argument at position `INDEX' for call statement
+ `G'.
-- GIMPLE function: void gimple_call_set_tail (gcall *s)
- Mark call statement 'S' as being a tail call (i.e., a call just
- before the exit of a function). These calls are candidate for tail
+ Mark call statement `S' as being a tail call (i.e., a call just
+ before the exit of a function). These calls are candidate for tail
call optimization.
-- GIMPLE function: bool gimple_call_tail_p (gcall *s)
- Return true if 'GIMPLE_CALL' 'S' is marked as a tail call.
+ Return true if `GIMPLE_CALL' `S' is marked as a tail call.
-- GIMPLE function: bool gimple_call_noreturn_p (gimple s)
- Return true if 'S' is a noreturn call.
+ Return true if `S' is a noreturn call.
-- GIMPLE function: gimple gimple_call_copy_skip_args (gcall *stmt,
bitmap args_to_skip)
- Build a 'GIMPLE_CALL' identical to 'STMT' but skipping the
- arguments in the positions marked by the set 'ARGS_TO_SKIP'.
+ Build a `GIMPLE_CALL' identical to `STMT' but skipping the
+ arguments in the positions marked by the set `ARGS_TO_SKIP'.

-File: gccint.info, Node: 'GIMPLE_CATCH', Next: 'GIMPLE_COND', Prev: 'GIMPLE_CALL', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_CATCH', Next: `GIMPLE_COND', Prev: `GIMPLE_CALL', Up: Tuple specific accessors
-11.8.5 'GIMPLE_CATCH'
+11.8.5 `GIMPLE_CATCH'
---------------------
-- GIMPLE function: gcatch *gimple_build_catch (tree types, gimple_seq
handler)
- Build a 'GIMPLE_CATCH' statement. 'TYPES' are the tree types this
- catch handles. 'HANDLER' is a sequence of statements with the code
+ Build a `GIMPLE_CATCH' statement. `TYPES' are the tree types this
+ catch handles. `HANDLER' is a sequence of statements with the code
for the handler.
-- GIMPLE function: tree gimple_catch_types (const gcatch *g)
- Return the types handled by 'GIMPLE_CATCH' statement 'G'.
+ Return the types handled by `GIMPLE_CATCH' statement `G'.
-- GIMPLE function: tree * gimple_catch_types_ptr (gcatch *g)
- Return a pointer to the types handled by 'GIMPLE_CATCH' statement
- 'G'.
+ Return a pointer to the types handled by `GIMPLE_CATCH' statement
+ `G'.
-- GIMPLE function: gimple_seq gimple_catch_handler (gcatch *g)
Return the GIMPLE sequence representing the body of the handler of
- 'GIMPLE_CATCH' statement 'G'.
+ `GIMPLE_CATCH' statement `G'.
-- GIMPLE function: void gimple_catch_set_types (gcatch *g, tree t)
- Set 'T' to be the set of types handled by 'GIMPLE_CATCH' 'G'.
+ Set `T' to be the set of types handled by `GIMPLE_CATCH' `G'.
-- GIMPLE function: void gimple_catch_set_handler (gcatch *g,
gimple_seq handler)
- Set 'HANDLER' to be the body of 'GIMPLE_CATCH' 'G'.
+ Set `HANDLER' to be the body of `GIMPLE_CATCH' `G'.

-File: gccint.info, Node: 'GIMPLE_COND', Next: 'GIMPLE_DEBUG', Prev: 'GIMPLE_CATCH', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_COND', Next: `GIMPLE_DEBUG', Prev: `GIMPLE_CATCH', Up: Tuple specific accessors
-11.8.6 'GIMPLE_COND'
+11.8.6 `GIMPLE_COND'
--------------------
-- GIMPLE function: gcond *gimple_build_cond ( enum tree_code
pred_code, tree lhs, tree rhs, tree t_label, tree f_label)
- Build a 'GIMPLE_COND' statement. 'A' 'GIMPLE_COND' statement
- compares 'LHS' and 'RHS' and if the condition in 'PRED_CODE' is
- true, jump to the label in 't_label', otherwise jump to the label
- in 'f_label'. 'PRED_CODE' are relational operator tree codes like
- 'EQ_EXPR', 'LT_EXPR', 'LE_EXPR', 'NE_EXPR', etc.
-
- -- GIMPLE function: gcond *gimple_build_cond_from_tree (tree cond, tree
- t_label, tree f_label)
- Build a 'GIMPLE_COND' statement from the conditional expression
- tree 'COND'. 'T_LABEL' and 'F_LABEL' are as in
- 'gimple_build_cond'.
+ Build a `GIMPLE_COND' statement. `A' `GIMPLE_COND' statement
+ compares `LHS' and `RHS' and if the condition in `PRED_CODE' is
+ true, jump to the label in `t_label', otherwise jump to the label
+ in `f_label'. `PRED_CODE' are relational operator tree codes like
+ `EQ_EXPR', `LT_EXPR', `LE_EXPR', `NE_EXPR', etc.
+
+ -- GIMPLE function: gcond *gimple_build_cond_from_tree (tree cond,
+ tree t_label, tree f_label)
+ Build a `GIMPLE_COND' statement from the conditional expression
+ tree `COND'. `T_LABEL' and `F_LABEL' are as in
+ `gimple_build_cond'.
-- GIMPLE function: enum tree_code gimple_cond_code (gimple g)
Return the code of the predicate computed by conditional statement
- 'G'.
+ `G'.
- -- GIMPLE function: void gimple_cond_set_code (gcond *g, enum tree_code
- code)
- Set 'CODE' to be the predicate code for the conditional statement
- 'G'.
+ -- GIMPLE function: void gimple_cond_set_code (gcond *g, enum
+ tree_code code)
+ Set `CODE' to be the predicate code for the conditional statement
+ `G'.
-- GIMPLE function: tree gimple_cond_lhs (gimple g)
- Return the 'LHS' of the predicate computed by conditional statement
- 'G'.
+ Return the `LHS' of the predicate computed by conditional statement
+ `G'.
-- GIMPLE function: void gimple_cond_set_lhs (gcond *g, tree lhs)
- Set 'LHS' to be the 'LHS' operand of the predicate computed by
- conditional statement 'G'.
+ Set `LHS' to be the `LHS' operand of the predicate computed by
+ conditional statement `G'.
-- GIMPLE function: tree gimple_cond_rhs (gimple g)
- Return the 'RHS' operand of the predicate computed by conditional
- 'G'.
+ Return the `RHS' operand of the predicate computed by conditional
+ `G'.
-- GIMPLE function: void gimple_cond_set_rhs (gcond *g, tree rhs)
- Set 'RHS' to be the 'RHS' operand of the predicate computed by
- conditional statement 'G'.
+ Set `RHS' to be the `RHS' operand of the predicate computed by
+ conditional statement `G'.
-- GIMPLE function: tree gimple_cond_true_label (const gcond *g)
- Return the label used by conditional statement 'G' when its
+ Return the label used by conditional statement `G' when its
predicate evaluates to true.
-- GIMPLE function: void gimple_cond_set_true_label (gcond *g, tree
label)
- Set 'LABEL' to be the label used by conditional statement 'G' when
+ Set `LABEL' to be the label used by conditional statement `G' when
its predicate evaluates to true.
-- GIMPLE function: void gimple_cond_set_false_label (gcond *g, tree
label)
- Set 'LABEL' to be the label used by conditional statement 'G' when
+ Set `LABEL' to be the label used by conditional statement `G' when
its predicate evaluates to false.
-- GIMPLE function: tree gimple_cond_false_label (const gcond *g)
- Return the label used by conditional statement 'G' when its
+ Return the label used by conditional statement `G' when its
predicate evaluates to false.
-- GIMPLE function: void gimple_cond_make_false (gcond *g)
- Set the conditional 'COND_STMT' to be of the form 'if (1 == 0)'.
+ Set the conditional `COND_STMT' to be of the form 'if (1 == 0)'.
-- GIMPLE function: void gimple_cond_make_true (gcond *g)
- Set the conditional 'COND_STMT' to be of the form 'if (1 == 1)'.
+ Set the conditional `COND_STMT' to be of the form 'if (1 == 1)'.

-File: gccint.info, Node: 'GIMPLE_DEBUG', Next: 'GIMPLE_EH_FILTER', Prev: 'GIMPLE_COND', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_DEBUG', Next: `GIMPLE_EH_FILTER', Prev: `GIMPLE_COND', Up: Tuple specific accessors
-11.8.7 'GIMPLE_DEBUG'
+11.8.7 `GIMPLE_DEBUG'
---------------------
-- GIMPLE function: gdebug *gimple_build_debug_bind (tree var, tree
value, gimple stmt)
- Build a 'GIMPLE_DEBUG' statement with 'GIMPLE_DEBUG_BIND' of
- 'subcode'. The effect of this statement is to tell debug
+ Build a `GIMPLE_DEBUG' statement with `GIMPLE_DEBUG_BIND' of
+ `subcode'. The effect of this statement is to tell debug
information generation machinery that the value of user variable
- 'var' is given by 'value' at that point, and to remain with that
- value until 'var' runs out of scope, a dynamically-subsequent debug
- bind statement overrides the binding, or conflicting values reach a
- control flow merge point. Even if components of the 'value'
- expression change afterwards, the variable is supposed to retain
- the same value, though not necessarily the same location.
-
- It is expected that 'var' be most often a tree for automatic user
- variables ('VAR_DECL' or 'PARM_DECL') that satisfy the requirements
- for gimple registers, but it may also be a tree for a scalarized
- component of a user variable ('ARRAY_REF', 'COMPONENT_REF'), or a
- debug temporary ('DEBUG_EXPR_DECL').
-
- As for 'value', it can be an arbitrary tree expression, but it is
+ `var' is given by `value' at that point, and to remain with that
+ value until `var' runs out of scope, a dynamically-subsequent
+ debug bind statement overrides the binding, or conflicting values
+ reach a control flow merge point. Even if components of the
+ `value' expression change afterwards, the variable is supposed to
+ retain the same value, though not necessarily the same location.
+
+ It is expected that `var' be most often a tree for automatic user
+ variables (`VAR_DECL' or `PARM_DECL') that satisfy the
+ requirements for gimple registers, but it may also be a tree for a
+ scalarized component of a user variable (`ARRAY_REF',
+ `COMPONENT_REF'), or a debug temporary (`DEBUG_EXPR_DECL').
+
+ As for `value', it can be an arbitrary tree expression, but it is
recommended that it be in a suitable form for a gimple assignment
- 'RHS'. It is not expected that user variables that could appear as
- 'var' ever appear in 'value', because in the latter we'd have their
- 'SSA_NAME's instead, but even if they were not in SSA form, user
- variables appearing in 'value' are to be regarded as part of the
- executable code space, whereas those in 'var' are to be regarded as
- part of the source code space. There is no way to refer to the
- value bound to a user variable within a 'value' expression.
-
- If 'value' is 'GIMPLE_DEBUG_BIND_NOVALUE', debug information
- generation machinery is informed that the variable 'var' is
+ `RHS'. It is not expected that user variables that could appear
+ as `var' ever appear in `value', because in the latter we'd have
+ their `SSA_NAME's instead, but even if they were not in SSA form,
+ user variables appearing in `value' are to be regarded as part of
+ the executable code space, whereas those in `var' are to be
+ regarded as part of the source code space. There is no way to
+ refer to the value bound to a user variable within a `value'
+ expression.
+
+ If `value' is `GIMPLE_DEBUG_BIND_NOVALUE', debug information
+ generation machinery is informed that the variable `var' is
unbound, i.e., that its value is indeterminate, which sometimes
means it is really unavailable, and other times that the compiler
could not keep track of it.
- Block and location information for the newly-created stmt are taken
- from 'stmt', if given.
+ Block and location information for the newly-created stmt are
+ taken from `stmt', if given.
-- GIMPLE function: tree gimple_debug_bind_get_var (gimple stmt)
- Return the user variable VAR that is bound at 'stmt'.
+ Return the user variable VAR that is bound at `stmt'.
-- GIMPLE function: tree gimple_debug_bind_get_value (gimple stmt)
Return the value expression that is bound to a user variable at
- 'stmt'.
+ `stmt'.
-- GIMPLE function: tree * gimple_debug_bind_get_value_ptr (gimple
stmt)
Return a pointer to the value expression that is bound to a user
- variable at 'stmt'.
+ variable at `stmt'.
-- GIMPLE function: void gimple_debug_bind_set_var (gimple stmt, tree
var)
- Modify the user variable bound at 'stmt' to VAR.
+ Modify the user variable bound at `stmt' to VAR.
- -- GIMPLE function: void gimple_debug_bind_set_value (gimple stmt, tree
- var)
- Modify the value bound to the user variable bound at 'stmt' to
+ -- GIMPLE function: void gimple_debug_bind_set_value (gimple stmt,
+ tree var)
+ Modify the value bound to the user variable bound at `stmt' to
VALUE.
-- GIMPLE function: void gimple_debug_bind_reset_value (gimple stmt)
- Modify the value bound to the user variable bound at 'stmt' so that
- the variable becomes unbound.
+ Modify the value bound to the user variable bound at `stmt' so
+ that the variable becomes unbound.
-- GIMPLE function: bool gimple_debug_bind_has_value_p (gimple stmt)
- Return 'TRUE' if 'stmt' binds a user variable to a value, and
- 'FALSE' if it unbinds the variable.
+ Return `TRUE' if `stmt' binds a user variable to a value, and
+ `FALSE' if it unbinds the variable.

-File: gccint.info, Node: 'GIMPLE_EH_FILTER', Next: 'GIMPLE_LABEL', Prev: 'GIMPLE_DEBUG', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_EH_FILTER', Next: `GIMPLE_LABEL', Prev: `GIMPLE_DEBUG', Up: Tuple specific accessors
-11.8.8 'GIMPLE_EH_FILTER'
+11.8.8 `GIMPLE_EH_FILTER'
-------------------------
-- GIMPLE function: geh_filter *gimple_build_eh_filter (tree types,
gimple_seq failure)
- Build a 'GIMPLE_EH_FILTER' statement. 'TYPES' are the filter's
- types. 'FAILURE' is a sequence with the filter's failure action.
+ Build a `GIMPLE_EH_FILTER' statement. `TYPES' are the filter's
+ types. `FAILURE' is a sequence with the filter's failure action.
-- GIMPLE function: tree gimple_eh_filter_types (gimple g)
- Return the types handled by 'GIMPLE_EH_FILTER' statement 'G'.
+ Return the types handled by `GIMPLE_EH_FILTER' statement `G'.
-- GIMPLE function: tree * gimple_eh_filter_types_ptr (gimple g)
- Return a pointer to the types handled by 'GIMPLE_EH_FILTER'
- statement 'G'.
+ Return a pointer to the types handled by `GIMPLE_EH_FILTER'
+ statement `G'.
-- GIMPLE function: gimple_seq gimple_eh_filter_failure (gimple g)
- Return the sequence of statement to execute when 'GIMPLE_EH_FILTER'
+ Return the sequence of statement to execute when `GIMPLE_EH_FILTER'
statement fails.
-- GIMPLE function: void gimple_eh_filter_set_types (geh_filter *g,
tree types)
- Set 'TYPES' to be the set of types handled by 'GIMPLE_EH_FILTER'
- 'G'.
+ Set `TYPES' to be the set of types handled by `GIMPLE_EH_FILTER'
+ `G'.
-- GIMPLE function: void gimple_eh_filter_set_failure (geh_filter *g,
gimple_seq failure)
- Set 'FAILURE' to be the sequence of statements to execute on
- failure for 'GIMPLE_EH_FILTER' 'G'.
+ Set `FAILURE' to be the sequence of statements to execute on
+ failure for `GIMPLE_EH_FILTER' `G'.
-- GIMPLE function: tree gimple_eh_must_not_throw_fndecl ( geh_mnt
*eh_mnt_stmt)
@@ -12005,86 +12136,86 @@ File: gccint.info, Node: 'GIMPLE_EH_FILTER', Next: 'GIMPLE_LABEL', Prev: 'GIM
Set the function decl to be called by GS to DECL.

-File: gccint.info, Node: 'GIMPLE_LABEL', Next: 'GIMPLE_GOTO', Prev: 'GIMPLE_EH_FILTER', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_LABEL', Next: `GIMPLE_GOTO', Prev: `GIMPLE_EH_FILTER', Up: Tuple specific accessors
-11.8.9 'GIMPLE_LABEL'
+11.8.9 `GIMPLE_LABEL'
---------------------
-- GIMPLE function: glabel *gimple_build_label (tree label)
- Build a 'GIMPLE_LABEL' statement with corresponding to the tree
- label, 'LABEL'.
+ Build a `GIMPLE_LABEL' statement with corresponding to the tree
+ label, `LABEL'.
-- GIMPLE function: tree gimple_label_label (const glabel *g)
- Return the 'LABEL_DECL' node used by 'GIMPLE_LABEL' statement 'G'.
+ Return the `LABEL_DECL' node used by `GIMPLE_LABEL' statement `G'.
-- GIMPLE function: void gimple_label_set_label (glabel *g, tree label)
- Set 'LABEL' to be the 'LABEL_DECL' node used by 'GIMPLE_LABEL'
- statement 'G'.
+ Set `LABEL' to be the `LABEL_DECL' node used by `GIMPLE_LABEL'
+ statement `G'.

-File: gccint.info, Node: 'GIMPLE_GOTO', Next: 'GIMPLE_NOP', Prev: 'GIMPLE_LABEL', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_GOTO', Next: `GIMPLE_NOP', Prev: `GIMPLE_LABEL', Up: Tuple specific accessors
-11.8.10 'GIMPLE_GOTO'
+11.8.10 `GIMPLE_GOTO'
---------------------
-- GIMPLE function: ggoto *gimple_build_goto (tree dest)
- Build a 'GIMPLE_GOTO' statement to label 'DEST'.
+ Build a `GIMPLE_GOTO' statement to label `DEST'.
-- GIMPLE function: tree gimple_goto_dest (gimple g)
- Return the destination of the unconditional jump 'G'.
+ Return the destination of the unconditional jump `G'.
-- GIMPLE function: void gimple_goto_set_dest (ggoto *g, tree dest)
- Set 'DEST' to be the destination of the unconditional jump 'G'.
+ Set `DEST' to be the destination of the unconditional jump `G'.

-File: gccint.info, Node: 'GIMPLE_NOP', Next: 'GIMPLE_OMP_ATOMIC_LOAD', Prev: 'GIMPLE_GOTO', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_NOP', Next: `GIMPLE_OMP_ATOMIC_LOAD', Prev: `GIMPLE_GOTO', Up: Tuple specific accessors
-11.8.11 'GIMPLE_NOP'
+11.8.11 `GIMPLE_NOP'
--------------------
-- GIMPLE function: gimple gimple_build_nop (void)
- Build a 'GIMPLE_NOP' statement.
+ Build a `GIMPLE_NOP' statement.
-- GIMPLE function: bool gimple_nop_p (gimple g)
- Returns 'TRUE' if statement 'G' is a 'GIMPLE_NOP'.
+ Returns `TRUE' if statement `G' is a `GIMPLE_NOP'.

-File: gccint.info, Node: 'GIMPLE_OMP_ATOMIC_LOAD', Next: 'GIMPLE_OMP_ATOMIC_STORE', Prev: 'GIMPLE_NOP', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_ATOMIC_LOAD', Next: `GIMPLE_OMP_ATOMIC_STORE', Prev: `GIMPLE_NOP', Up: Tuple specific accessors
-11.8.12 'GIMPLE_OMP_ATOMIC_LOAD'
+11.8.12 `GIMPLE_OMP_ATOMIC_LOAD'
--------------------------------
-- GIMPLE function: gomp_atomic_load *gimple_build_omp_atomic_load (
tree lhs, tree rhs)
- Build a 'GIMPLE_OMP_ATOMIC_LOAD' statement. 'LHS' is the left-hand
- side of the assignment. 'RHS' is the right-hand side of the
+ Build a `GIMPLE_OMP_ATOMIC_LOAD' statement. `LHS' is the left-hand
+ side of the assignment. `RHS' is the right-hand side of the
assignment.
-- GIMPLE function: void gimple_omp_atomic_load_set_lhs (
gomp_atomic_load *g, tree lhs)
- Set the 'LHS' of an atomic load.
+ Set the `LHS' of an atomic load.
-- GIMPLE function: tree gimple_omp_atomic_load_lhs ( const
gomp_atomic_load *g)
- Get the 'LHS' of an atomic load.
+ Get the `LHS' of an atomic load.
-- GIMPLE function: void gimple_omp_atomic_load_set_rhs (
gomp_atomic_load *g, tree rhs)
- Set the 'RHS' of an atomic set.
+ Set the `RHS' of an atomic set.
-- GIMPLE function: tree gimple_omp_atomic_load_rhs ( const
gomp_atomic_load *g)
- Get the 'RHS' of an atomic set.
+ Get the `RHS' of an atomic set.

-File: gccint.info, Node: 'GIMPLE_OMP_ATOMIC_STORE', Next: 'GIMPLE_OMP_CONTINUE', Prev: 'GIMPLE_OMP_ATOMIC_LOAD', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_ATOMIC_STORE', Next: `GIMPLE_OMP_CONTINUE', Prev: `GIMPLE_OMP_ATOMIC_LOAD', Up: Tuple specific accessors
-11.8.13 'GIMPLE_OMP_ATOMIC_STORE'
+11.8.13 `GIMPLE_OMP_ATOMIC_STORE'
---------------------------------
-- GIMPLE function: gomp_atomic_store *gimple_build_omp_atomic_store (
tree val)
- Build a 'GIMPLE_OMP_ATOMIC_STORE' statement. 'VAL' is the value to
+ Build a `GIMPLE_OMP_ATOMIC_STORE' statement. `VAL' is the value to
be stored.
-- GIMPLE function: void gimple_omp_atomic_store_set_val (
@@ -12096,21 +12227,21 @@ File: gccint.info, Node: 'GIMPLE_OMP_ATOMIC_STORE', Next: 'GIMPLE_OMP_CONTINUE
Return the value being stored in an atomic store.

-File: gccint.info, Node: 'GIMPLE_OMP_CONTINUE', Next: 'GIMPLE_OMP_CRITICAL', Prev: 'GIMPLE_OMP_ATOMIC_STORE', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_CONTINUE', Next: `GIMPLE_OMP_CRITICAL', Prev: `GIMPLE_OMP_ATOMIC_STORE', Up: Tuple specific accessors
-11.8.14 'GIMPLE_OMP_CONTINUE'
+11.8.14 `GIMPLE_OMP_CONTINUE'
-----------------------------
-- GIMPLE function: gomp_continue *gimple_build_omp_continue ( tree
control_def, tree control_use)
- Build a 'GIMPLE_OMP_CONTINUE' statement. 'CONTROL_DEF' is the
- definition of the control variable. 'CONTROL_USE' is the use of
+ Build a `GIMPLE_OMP_CONTINUE' statement. `CONTROL_DEF' is the
+ definition of the control variable. `CONTROL_USE' is the use of
the control variable.
-- GIMPLE function: tree gimple_omp_continue_control_def ( const
gomp_continue *s)
Return the definition of the control variable on a
- 'GIMPLE_OMP_CONTINUE' in 'S'.
+ `GIMPLE_OMP_CONTINUE' in `S'.
-- GIMPLE function: tree gimple_omp_continue_control_def_ptr (
gomp_continue *s)
@@ -12118,13 +12249,13 @@ File: gccint.info, Node: 'GIMPLE_OMP_CONTINUE', Next: 'GIMPLE_OMP_CRITICAL',
-- GIMPLE function: tree gimple_omp_continue_set_control_def (
gomp_continue *s)
- Set the control variable definition for a 'GIMPLE_OMP_CONTINUE'
- statement in 'S'.
+ Set the control variable definition for a `GIMPLE_OMP_CONTINUE'
+ statement in `S'.
-- GIMPLE function: tree gimple_omp_continue_control_use ( const
gomp_continue *s)
- Return the use of the control variable on a 'GIMPLE_OMP_CONTINUE'
- in 'S'.
+ Return the use of the control variable on a `GIMPLE_OMP_CONTINUE'
+ in `S'.
-- GIMPLE function: tree gimple_omp_continue_control_use_ptr (
gomp_continue *s)
@@ -12132,413 +12263,413 @@ File: gccint.info, Node: 'GIMPLE_OMP_CONTINUE', Next: 'GIMPLE_OMP_CRITICAL',
-- GIMPLE function: tree gimple_omp_continue_set_control_use (
gomp_continue *s)
- Set the control variable use for a 'GIMPLE_OMP_CONTINUE' statement
- in 'S'.
+ Set the control variable use for a `GIMPLE_OMP_CONTINUE' statement
+ in `S'.

-File: gccint.info, Node: 'GIMPLE_OMP_CRITICAL', Next: 'GIMPLE_OMP_FOR', Prev: 'GIMPLE_OMP_CONTINUE', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_CRITICAL', Next: `GIMPLE_OMP_FOR', Prev: `GIMPLE_OMP_CONTINUE', Up: Tuple specific accessors
-11.8.15 'GIMPLE_OMP_CRITICAL'
+11.8.15 `GIMPLE_OMP_CRITICAL'
-----------------------------
-- GIMPLE function: gomp_critical *gimple_build_omp_critical (
gimple_seq body, tree name)
- Build a 'GIMPLE_OMP_CRITICAL' statement. 'BODY' is the sequence of
- statements for which only one thread can execute. 'NAME' is an
+ Build a `GIMPLE_OMP_CRITICAL' statement. `BODY' is the sequence of
+ statements for which only one thread can execute. `NAME' is an
optional identifier for this critical block.
- -- GIMPLE function: tree gimple_omp_critical_name ( const gomp_critical
- *g)
- Return the name associated with 'OMP_CRITICAL' statement 'G'.
+ -- GIMPLE function: tree gimple_omp_critical_name ( const
+ gomp_critical *g)
+ Return the name associated with `OMP_CRITICAL' statement `G'.
- -- GIMPLE function: tree * gimple_omp_critical_name_ptr ( gomp_critical
- *g)
- Return a pointer to the name associated with 'OMP' critical
- statement 'G'.
+ -- GIMPLE function: tree * gimple_omp_critical_name_ptr (
+ gomp_critical *g)
+ Return a pointer to the name associated with `OMP' critical
+ statement `G'.
-- GIMPLE function: void gimple_omp_critical_set_name ( gomp_critical
*g, tree name)
- Set 'NAME' to be the name associated with 'OMP' critical statement
- 'G'.
+ Set `NAME' to be the name associated with `OMP' critical statement
+ `G'.

-File: gccint.info, Node: 'GIMPLE_OMP_FOR', Next: 'GIMPLE_OMP_MASTER', Prev: 'GIMPLE_OMP_CRITICAL', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_FOR', Next: `GIMPLE_OMP_MASTER', Prev: `GIMPLE_OMP_CRITICAL', Up: Tuple specific accessors
-11.8.16 'GIMPLE_OMP_FOR'
+11.8.16 `GIMPLE_OMP_FOR'
------------------------
-- GIMPLE function: gomp_for *gimple_build_omp_for (gimple_seq body,
- tree clauses, tree index, tree initial, tree final, tree incr,
- gimple_seq pre_body, enum tree_code omp_for_cond)
- Build a 'GIMPLE_OMP_FOR' statement. 'BODY' is sequence of
- statements inside the for loop. 'CLAUSES', are any of the loop
- construct's clauses. 'PRE_BODY' is the sequence of statements that
- are loop invariant. 'INDEX' is the index variable. 'INITIAL' is
- the initial value of 'INDEX'. 'FINAL' is final value of 'INDEX'.
- OMP_FOR_COND is the predicate used to compare 'INDEX' and 'FINAL'.
- 'INCR' is the increment expression.
+ tree clauses, tree index, tree initial, tree final, tree
+ incr, gimple_seq pre_body, enum tree_code omp_for_cond)
+ Build a `GIMPLE_OMP_FOR' statement. `BODY' is sequence of
+ statements inside the for loop. `CLAUSES', are any of the loop
+ construct's clauses. `PRE_BODY' is the sequence of statements
+ that are loop invariant. `INDEX' is the index variable.
+ `INITIAL' is the initial value of `INDEX'. `FINAL' is final value
+ of `INDEX'. OMP_FOR_COND is the predicate used to compare `INDEX'
+ and `FINAL'. `INCR' is the increment expression.
-- GIMPLE function: tree gimple_omp_for_clauses (gimple g)
- Return the clauses associated with 'OMP_FOR' 'G'.
+ Return the clauses associated with `OMP_FOR' `G'.
-- GIMPLE function: tree * gimple_omp_for_clauses_ptr (gimple g)
- Return a pointer to the 'OMP_FOR' 'G'.
+ Return a pointer to the `OMP_FOR' `G'.
-- GIMPLE function: void gimple_omp_for_set_clauses (gimple g, tree
clauses)
- Set 'CLAUSES' to be the list of clauses associated with 'OMP_FOR'
- 'G'.
+ Set `CLAUSES' to be the list of clauses associated with `OMP_FOR'
+ `G'.
-- GIMPLE function: tree gimple_omp_for_index (gimple g)
- Return the index variable for 'OMP_FOR' 'G'.
+ Return the index variable for `OMP_FOR' `G'.
-- GIMPLE function: tree * gimple_omp_for_index_ptr (gimple g)
- Return a pointer to the index variable for 'OMP_FOR' 'G'.
+ Return a pointer to the index variable for `OMP_FOR' `G'.
-- GIMPLE function: void gimple_omp_for_set_index (gimple g, tree
index)
- Set 'INDEX' to be the index variable for 'OMP_FOR' 'G'.
+ Set `INDEX' to be the index variable for `OMP_FOR' `G'.
-- GIMPLE function: tree gimple_omp_for_initial (gimple g)
- Return the initial value for 'OMP_FOR' 'G'.
+ Return the initial value for `OMP_FOR' `G'.
-- GIMPLE function: tree * gimple_omp_for_initial_ptr (gimple g)
- Return a pointer to the initial value for 'OMP_FOR' 'G'.
+ Return a pointer to the initial value for `OMP_FOR' `G'.
-- GIMPLE function: void gimple_omp_for_set_initial (gimple g, tree
initial)
- Set 'INITIAL' to be the initial value for 'OMP_FOR' 'G'.
+ Set `INITIAL' to be the initial value for `OMP_FOR' `G'.
-- GIMPLE function: tree gimple_omp_for_final (gimple g)
- Return the final value for 'OMP_FOR' 'G'.
+ Return the final value for `OMP_FOR' `G'.
-- GIMPLE function: tree * gimple_omp_for_final_ptr (gimple g)
- turn a pointer to the final value for 'OMP_FOR' 'G'.
+ turn a pointer to the final value for `OMP_FOR' `G'.
-- GIMPLE function: void gimple_omp_for_set_final (gimple g, tree
final)
- Set 'FINAL' to be the final value for 'OMP_FOR' 'G'.
+ Set `FINAL' to be the final value for `OMP_FOR' `G'.
-- GIMPLE function: tree gimple_omp_for_incr (gimple g)
- Return the increment value for 'OMP_FOR' 'G'.
+ Return the increment value for `OMP_FOR' `G'.
-- GIMPLE function: tree * gimple_omp_for_incr_ptr (gimple g)
- Return a pointer to the increment value for 'OMP_FOR' 'G'.
+ Return a pointer to the increment value for `OMP_FOR' `G'.
-- GIMPLE function: void gimple_omp_for_set_incr (gimple g, tree incr)
- Set 'INCR' to be the increment value for 'OMP_FOR' 'G'.
+ Set `INCR' to be the increment value for `OMP_FOR' `G'.
-- GIMPLE function: gimple_seq gimple_omp_for_pre_body (gimple g)
- Return the sequence of statements to execute before the 'OMP_FOR'
- statement 'G' starts.
+ Return the sequence of statements to execute before the `OMP_FOR'
+ statement `G' starts.
-- GIMPLE function: void gimple_omp_for_set_pre_body (gimple g,
gimple_seq pre_body)
- Set 'PRE_BODY' to be the sequence of statements to execute before
- the 'OMP_FOR' statement 'G' starts.
+ Set `PRE_BODY' to be the sequence of statements to execute before
+ the `OMP_FOR' statement `G' starts.
-- GIMPLE function: void gimple_omp_for_set_cond (gimple g, enum
tree_code cond)
- Set 'COND' to be the condition code for 'OMP_FOR' 'G'.
+ Set `COND' to be the condition code for `OMP_FOR' `G'.
-- GIMPLE function: enum tree_code gimple_omp_for_cond (gimple g)
- Return the condition code associated with 'OMP_FOR' 'G'.
+ Return the condition code associated with `OMP_FOR' `G'.

-File: gccint.info, Node: 'GIMPLE_OMP_MASTER', Next: 'GIMPLE_OMP_ORDERED', Prev: 'GIMPLE_OMP_FOR', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_MASTER', Next: `GIMPLE_OMP_ORDERED', Prev: `GIMPLE_OMP_FOR', Up: Tuple specific accessors
-11.8.17 'GIMPLE_OMP_MASTER'
+11.8.17 `GIMPLE_OMP_MASTER'
---------------------------
-- GIMPLE function: gimple gimple_build_omp_master (gimple_seq body)
- Build a 'GIMPLE_OMP_MASTER' statement. 'BODY' is the sequence of
+ Build a `GIMPLE_OMP_MASTER' statement. `BODY' is the sequence of
statements to be executed by just the master.

-File: gccint.info, Node: 'GIMPLE_OMP_ORDERED', Next: 'GIMPLE_OMP_PARALLEL', Prev: 'GIMPLE_OMP_MASTER', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_ORDERED', Next: `GIMPLE_OMP_PARALLEL', Prev: `GIMPLE_OMP_MASTER', Up: Tuple specific accessors
-11.8.18 'GIMPLE_OMP_ORDERED'
+11.8.18 `GIMPLE_OMP_ORDERED'
----------------------------
-- GIMPLE function: gimple gimple_build_omp_ordered (gimple_seq body)
- Build a 'GIMPLE_OMP_ORDERED' statement.
+ Build a `GIMPLE_OMP_ORDERED' statement.
- 'BODY' is the sequence of statements inside a loop that will executed
+ `BODY' is the sequence of statements inside a loop that will executed
in sequence.

-File: gccint.info, Node: 'GIMPLE_OMP_PARALLEL', Next: 'GIMPLE_OMP_RETURN', Prev: 'GIMPLE_OMP_ORDERED', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_PARALLEL', Next: `GIMPLE_OMP_RETURN', Prev: `GIMPLE_OMP_ORDERED', Up: Tuple specific accessors
-11.8.19 'GIMPLE_OMP_PARALLEL'
+11.8.19 `GIMPLE_OMP_PARALLEL'
-----------------------------
- -- GIMPLE function: gomp_parallel *gimple_build_omp_parallel
- (gimple_seq body, tree clauses, tree child_fn, tree data_arg)
- Build a 'GIMPLE_OMP_PARALLEL' statement.
+ -- GIMPLE function: gomp_parallel *gimple_build_omp_parallel (
+ gimple_seq body, tree clauses, tree child_fn, tree data_arg)
+ Build a `GIMPLE_OMP_PARALLEL' statement.
- 'BODY' is sequence of statements which are executed in parallel.
-'CLAUSES', are the 'OMP' parallel construct's clauses. 'CHILD_FN' is
-the function created for the parallel threads to execute. 'DATA_ARG'
+ `BODY' is sequence of statements which are executed in parallel.
+`CLAUSES', are the `OMP' parallel construct's clauses. `CHILD_FN' is
+the function created for the parallel threads to execute. `DATA_ARG'
are the shared data argument(s).
-- GIMPLE function: bool gimple_omp_parallel_combined_p (gimple g)
- Return true if 'OMP' parallel statement 'G' has the
- 'GF_OMP_PARALLEL_COMBINED' flag set.
+ Return true if `OMP' parallel statement `G' has the
+ `GF_OMP_PARALLEL_COMBINED' flag set.
-- GIMPLE function: void gimple_omp_parallel_set_combined_p (gimple g)
- Set the 'GF_OMP_PARALLEL_COMBINED' field in 'OMP' parallel
- statement 'G'.
+ Set the `GF_OMP_PARALLEL_COMBINED' field in `OMP' parallel
+ statement `G'.
-- GIMPLE function: gimple_seq gimple_omp_body (gimple g)
- Return the body for the 'OMP' statement 'G'.
+ Return the body for the `OMP' statement `G'.
-- GIMPLE function: void gimple_omp_set_body (gimple g, gimple_seq
body)
- Set 'BODY' to be the body for the 'OMP' statement 'G'.
+ Set `BODY' to be the body for the `OMP' statement `G'.
-- GIMPLE function: tree gimple_omp_parallel_clauses (gimple g)
- Return the clauses associated with 'OMP_PARALLEL' 'G'.
+ Return the clauses associated with `OMP_PARALLEL' `G'.
-- GIMPLE function: tree * gimple_omp_parallel_clauses_ptr (
gomp_parallel *g)
- Return a pointer to the clauses associated with 'OMP_PARALLEL' 'G'.
+ Return a pointer to the clauses associated with `OMP_PARALLEL' `G'.
-- GIMPLE function: void gimple_omp_parallel_set_clauses (
gomp_parallel *g, tree clauses)
- Set 'CLAUSES' to be the list of clauses associated with
- 'OMP_PARALLEL' 'G'.
+ Set `CLAUSES' to be the list of clauses associated with
+ `OMP_PARALLEL' `G'.
-- GIMPLE function: tree gimple_omp_parallel_child_fn ( const
gomp_parallel *g)
- Return the child function used to hold the body of 'OMP_PARALLEL'
- 'G'.
+ Return the child function used to hold the body of `OMP_PARALLEL'
+ `G'.
-- GIMPLE function: tree * gimple_omp_parallel_child_fn_ptr (
gomp_parallel *g)
Return a pointer to the child function used to hold the body of
- 'OMP_PARALLEL' 'G'.
+ `OMP_PARALLEL' `G'.
-- GIMPLE function: void gimple_omp_parallel_set_child_fn (
gomp_parallel *g, tree child_fn)
- Set 'CHILD_FN' to be the child function for 'OMP_PARALLEL' 'G'.
+ Set `CHILD_FN' to be the child function for `OMP_PARALLEL' `G'.
-- GIMPLE function: tree gimple_omp_parallel_data_arg ( const
gomp_parallel *g)
Return the artificial argument used to send variables and values
- from the parent to the children threads in 'OMP_PARALLEL' 'G'.
+ from the parent to the children threads in `OMP_PARALLEL' `G'.
-- GIMPLE function: tree * gimple_omp_parallel_data_arg_ptr (
gomp_parallel *g)
- Return a pointer to the data argument for 'OMP_PARALLEL' 'G'.
+ Return a pointer to the data argument for `OMP_PARALLEL' `G'.
-- GIMPLE function: void gimple_omp_parallel_set_data_arg (
gomp_parallel *g, tree data_arg)
- Set 'DATA_ARG' to be the data argument for 'OMP_PARALLEL' 'G'.
+ Set `DATA_ARG' to be the data argument for `OMP_PARALLEL' `G'.

-File: gccint.info, Node: 'GIMPLE_OMP_RETURN', Next: 'GIMPLE_OMP_SECTION', Prev: 'GIMPLE_OMP_PARALLEL', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_RETURN', Next: `GIMPLE_OMP_SECTION', Prev: `GIMPLE_OMP_PARALLEL', Up: Tuple specific accessors
-11.8.20 'GIMPLE_OMP_RETURN'
+11.8.20 `GIMPLE_OMP_RETURN'
---------------------------
-- GIMPLE function: gimple gimple_build_omp_return (bool wait_p)
- Build a 'GIMPLE_OMP_RETURN' statement. 'WAIT_P' is true if this is
+ Build a `GIMPLE_OMP_RETURN' statement. `WAIT_P' is true if this is
a non-waiting return.
-- GIMPLE function: void gimple_omp_return_set_nowait (gimple s)
- Set the nowait flag on 'GIMPLE_OMP_RETURN' statement 'S'.
+ Set the nowait flag on `GIMPLE_OMP_RETURN' statement `S'.
-- GIMPLE function: bool gimple_omp_return_nowait_p (gimple g)
- Return true if 'OMP' return statement 'G' has the
- 'GF_OMP_RETURN_NOWAIT' flag set.
+ Return true if `OMP' return statement `G' has the
+ `GF_OMP_RETURN_NOWAIT' flag set.

-File: gccint.info, Node: 'GIMPLE_OMP_SECTION', Next: 'GIMPLE_OMP_SECTIONS', Prev: 'GIMPLE_OMP_RETURN', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_SECTION', Next: `GIMPLE_OMP_SECTIONS', Prev: `GIMPLE_OMP_RETURN', Up: Tuple specific accessors
-11.8.21 'GIMPLE_OMP_SECTION'
+11.8.21 `GIMPLE_OMP_SECTION'
----------------------------
-- GIMPLE function: gimple gimple_build_omp_section (gimple_seq body)
- Build a 'GIMPLE_OMP_SECTION' statement for a sections statement.
+ Build a `GIMPLE_OMP_SECTION' statement for a sections statement.
- 'BODY' is the sequence of statements in the section.
+ `BODY' is the sequence of statements in the section.
-- GIMPLE function: bool gimple_omp_section_last_p (gimple g)
- Return true if 'OMP' section statement 'G' has the
- 'GF_OMP_SECTION_LAST' flag set.
+ Return true if `OMP' section statement `G' has the
+ `GF_OMP_SECTION_LAST' flag set.
-- GIMPLE function: void gimple_omp_section_set_last (gimple g)
- Set the 'GF_OMP_SECTION_LAST' flag on 'G'.
+ Set the `GF_OMP_SECTION_LAST' flag on `G'.

-File: gccint.info, Node: 'GIMPLE_OMP_SECTIONS', Next: 'GIMPLE_OMP_SINGLE', Prev: 'GIMPLE_OMP_SECTION', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_SECTIONS', Next: `GIMPLE_OMP_SINGLE', Prev: `GIMPLE_OMP_SECTION', Up: Tuple specific accessors
-11.8.22 'GIMPLE_OMP_SECTIONS'
+11.8.22 `GIMPLE_OMP_SECTIONS'
-----------------------------
-- GIMPLE function: gomp_sections *gimple_build_omp_sections (
gimple_seq body, tree clauses)
- Build a 'GIMPLE_OMP_SECTIONS' statement. 'BODY' is a sequence of
- section statements. 'CLAUSES' are any of the 'OMP' sections
- construct's clauses: private, firstprivate, lastprivate, reduction,
- and nowait.
+ Build a `GIMPLE_OMP_SECTIONS' statement. `BODY' is a sequence of
+ section statements. `CLAUSES' are any of the `OMP' sections
+ construct's clauses: private, firstprivate, lastprivate,
+ reduction, and nowait.
-- GIMPLE function: gimple gimple_build_omp_sections_switch (void)
- Build a 'GIMPLE_OMP_SECTIONS_SWITCH' statement.
+ Build a `GIMPLE_OMP_SECTIONS_SWITCH' statement.
-- GIMPLE function: tree gimple_omp_sections_control (gimple g)
Return the control variable associated with the
- 'GIMPLE_OMP_SECTIONS' in 'G'.
+ `GIMPLE_OMP_SECTIONS' in `G'.
-- GIMPLE function: tree * gimple_omp_sections_control_ptr (gimple g)
Return a pointer to the clauses associated with the
- 'GIMPLE_OMP_SECTIONS' in 'G'.
+ `GIMPLE_OMP_SECTIONS' in `G'.
-- GIMPLE function: void gimple_omp_sections_set_control (gimple g,
tree control)
- Set 'CONTROL' to be the set of clauses associated with the
- 'GIMPLE_OMP_SECTIONS' in 'G'.
+ Set `CONTROL' to be the set of clauses associated with the
+ `GIMPLE_OMP_SECTIONS' in `G'.
-- GIMPLE function: tree gimple_omp_sections_clauses (gimple g)
- Return the clauses associated with 'OMP_SECTIONS' 'G'.
+ Return the clauses associated with `OMP_SECTIONS' `G'.
-- GIMPLE function: tree * gimple_omp_sections_clauses_ptr (gimple g)
- Return a pointer to the clauses associated with 'OMP_SECTIONS' 'G'.
+ Return a pointer to the clauses associated with `OMP_SECTIONS' `G'.
-- GIMPLE function: void gimple_omp_sections_set_clauses (gimple g,
tree clauses)
- Set 'CLAUSES' to be the set of clauses associated with
- 'OMP_SECTIONS' 'G'.
+ Set `CLAUSES' to be the set of clauses associated with
+ `OMP_SECTIONS' `G'.

-File: gccint.info, Node: 'GIMPLE_OMP_SINGLE', Next: 'GIMPLE_PHI', Prev: 'GIMPLE_OMP_SECTIONS', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_OMP_SINGLE', Next: `GIMPLE_PHI', Prev: `GIMPLE_OMP_SECTIONS', Up: Tuple specific accessors
-11.8.23 'GIMPLE_OMP_SINGLE'
+11.8.23 `GIMPLE_OMP_SINGLE'
---------------------------
-- GIMPLE function: gomp_single *gimple_build_omp_single ( gimple_seq
body, tree clauses)
- Build a 'GIMPLE_OMP_SINGLE' statement. 'BODY' is the sequence of
- statements that will be executed once. 'CLAUSES' are any of the
- 'OMP' single construct's clauses: private, firstprivate,
+ Build a `GIMPLE_OMP_SINGLE' statement. `BODY' is the sequence of
+ statements that will be executed once. `CLAUSES' are any of the
+ `OMP' single construct's clauses: private, firstprivate,
copyprivate, nowait.
-- GIMPLE function: tree gimple_omp_single_clauses (gimple g)
- Return the clauses associated with 'OMP_SINGLE' 'G'.
+ Return the clauses associated with `OMP_SINGLE' `G'.
-- GIMPLE function: tree * gimple_omp_single_clauses_ptr (gimple g)
- Return a pointer to the clauses associated with 'OMP_SINGLE' 'G'.
+ Return a pointer to the clauses associated with `OMP_SINGLE' `G'.
-- GIMPLE function: void gimple_omp_single_set_clauses ( gomp_single
*g, tree clauses)
- Set 'CLAUSES' to be the clauses associated with 'OMP_SINGLE' 'G'.
+ Set `CLAUSES' to be the clauses associated with `OMP_SINGLE' `G'.

-File: gccint.info, Node: 'GIMPLE_PHI', Next: 'GIMPLE_RESX', Prev: 'GIMPLE_OMP_SINGLE', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_PHI', Next: `GIMPLE_RESX', Prev: `GIMPLE_OMP_SINGLE', Up: Tuple specific accessors
-11.8.24 'GIMPLE_PHI'
+11.8.24 `GIMPLE_PHI'
--------------------
-- GIMPLE function: unsigned gimple_phi_capacity (gimple g)
- Return the maximum number of arguments supported by 'GIMPLE_PHI'
- 'G'.
+ Return the maximum number of arguments supported by `GIMPLE_PHI'
+ `G'.
-- GIMPLE function: unsigned gimple_phi_num_args (gimple g)
- Return the number of arguments in 'GIMPLE_PHI' 'G'. This must
+ Return the number of arguments in `GIMPLE_PHI' `G'. This must
always be exactly the number of incoming edges for the basic block
- holding 'G'.
+ holding `G'.
-- GIMPLE function: tree gimple_phi_result (gimple g)
- Return the 'SSA' name created by 'GIMPLE_PHI' 'G'.
+ Return the `SSA' name created by `GIMPLE_PHI' `G'.
-- GIMPLE function: tree * gimple_phi_result_ptr (gimple g)
- Return a pointer to the 'SSA' name created by 'GIMPLE_PHI' 'G'.
+ Return a pointer to the `SSA' name created by `GIMPLE_PHI' `G'.
-- GIMPLE function: void gimple_phi_set_result (gphi *g, tree result)
- Set 'RESULT' to be the 'SSA' name created by 'GIMPLE_PHI' 'G'.
+ Set `RESULT' to be the `SSA' name created by `GIMPLE_PHI' `G'.
-- GIMPLE function: struct phi_arg_d * gimple_phi_arg (gimple g, index)
- Return the 'PHI' argument corresponding to incoming edge 'INDEX'
- for 'GIMPLE_PHI' 'G'.
+ Return the `PHI' argument corresponding to incoming edge `INDEX'
+ for `GIMPLE_PHI' `G'.
-- GIMPLE function: void gimple_phi_set_arg (gphi *g, index, struct
phi_arg_d * phiarg)
- Set 'PHIARG' to be the argument corresponding to incoming edge
- 'INDEX' for 'GIMPLE_PHI' 'G'.
+ Set `PHIARG' to be the argument corresponding to incoming edge
+ `INDEX' for `GIMPLE_PHI' `G'.

-File: gccint.info, Node: 'GIMPLE_RESX', Next: 'GIMPLE_RETURN', Prev: 'GIMPLE_PHI', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_RESX', Next: `GIMPLE_RETURN', Prev: `GIMPLE_PHI', Up: Tuple specific accessors
-11.8.25 'GIMPLE_RESX'
+11.8.25 `GIMPLE_RESX'
---------------------
-- GIMPLE function: gresx *gimple_build_resx (int region)
- Build a 'GIMPLE_RESX' statement which is a statement. This
+ Build a `GIMPLE_RESX' statement which is a statement. This
statement is a placeholder for _Unwind_Resume before we know if a
- function call or a branch is needed. 'REGION' is the exception
+ function call or a branch is needed. `REGION' is the exception
region from which control is flowing.
-- GIMPLE function: int gimple_resx_region (const gresx *g)
- Return the region number for 'GIMPLE_RESX' 'G'.
+ Return the region number for `GIMPLE_RESX' `G'.
-- GIMPLE function: void gimple_resx_set_region (gresx *g, int region)
- Set 'REGION' to be the region number for 'GIMPLE_RESX' 'G'.
+ Set `REGION' to be the region number for `GIMPLE_RESX' `G'.

-File: gccint.info, Node: 'GIMPLE_RETURN', Next: 'GIMPLE_SWITCH', Prev: 'GIMPLE_RESX', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_RETURN', Next: `GIMPLE_SWITCH', Prev: `GIMPLE_RESX', Up: Tuple specific accessors
-11.8.26 'GIMPLE_RETURN'
+11.8.26 `GIMPLE_RETURN'
-----------------------
-- GIMPLE function: greturn *gimple_build_return (tree retval)
- Build a 'GIMPLE_RETURN' statement whose return value is retval.
+ Build a `GIMPLE_RETURN' statement whose return value is retval.
-- GIMPLE function: tree gimple_return_retval (const greturn *g)
- Return the return value for 'GIMPLE_RETURN' 'G'.
+ Return the return value for `GIMPLE_RETURN' `G'.
-- GIMPLE function: void gimple_return_set_retval (greturn *g, tree
retval)
- Set 'RETVAL' to be the return value for 'GIMPLE_RETURN' 'G'.
+ Set `RETVAL' to be the return value for `GIMPLE_RETURN' `G'.

-File: gccint.info, Node: 'GIMPLE_SWITCH', Next: 'GIMPLE_TRY', Prev: 'GIMPLE_RETURN', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_SWITCH', Next: `GIMPLE_TRY', Prev: `GIMPLE_RETURN', Up: Tuple specific accessors
-11.8.27 'GIMPLE_SWITCH'
+11.8.27 `GIMPLE_SWITCH'
-----------------------
-- GIMPLE function: gswitch *gimple_build_switch (tree index, tree
- default_label, 'vec'<tree> *args)
- Build a 'GIMPLE_SWITCH' statement. 'INDEX' is the index variable
- to switch on, and 'DEFAULT_LABEL' represents the default label.
- 'ARGS' is a vector of 'CASE_LABEL_EXPR' trees that contain the
+ default_label, `vec'<tree> *args)
+ Build a `GIMPLE_SWITCH' statement. `INDEX' is the index variable
+ to switch on, and `DEFAULT_LABEL' represents the default label.
+ `ARGS' is a vector of `CASE_LABEL_EXPR' trees that contain the
non-default case labels. Each label is a tree of code
- 'CASE_LABEL_EXPR'.
+ `CASE_LABEL_EXPR'.
-- GIMPLE function: unsigned gimple_switch_num_labels ( const gswitch
*g)
Return the number of labels associated with the switch statement
- 'G'.
+ `G'.
-- GIMPLE function: void gimple_switch_set_num_labels (gswitch *g,
unsigned nlabels)
- Set 'NLABELS' to be the number of labels for the switch statement
- 'G'.
+ Set `NLABELS' to be the number of labels for the switch statement
+ `G'.
-- GIMPLE function: tree gimple_switch_index (const gswitch *g)
- Return the index variable used by the switch statement 'G'.
+ Return the index variable used by the switch statement `G'.
-- GIMPLE function: void gimple_switch_set_index (gswitch *g, tree
index)
- Set 'INDEX' to be the index variable for switch statement 'G'.
+ Set `INDEX' to be the index variable for switch statement `G'.
-- GIMPLE function: tree gimple_switch_label (const gswitch *g,
unsigned index)
- Return the label numbered 'INDEX'. The default label is 0,
- followed by any labels in a switch statement.
+ Return the label numbered `INDEX'. The default label is 0, followed
+ by any labels in a switch statement.
-- GIMPLE function: void gimple_switch_set_label (gswitch *g, unsigned
index, tree label)
- Set the label number 'INDEX' to 'LABEL'. 0 is always the default
+ Set the label number `INDEX' to `LABEL'. 0 is always the default
label.
-- GIMPLE function: tree gimple_switch_default_label ( const gswitch
@@ -12550,71 +12681,71 @@ File: gccint.info, Node: 'GIMPLE_SWITCH', Next: 'GIMPLE_TRY', Prev: 'GIMPLE_R
Set the default label for a switch statement.

-File: gccint.info, Node: 'GIMPLE_TRY', Next: 'GIMPLE_WITH_CLEANUP_EXPR', Prev: 'GIMPLE_SWITCH', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_TRY', Next: `GIMPLE_WITH_CLEANUP_EXPR', Prev: `GIMPLE_SWITCH', Up: Tuple specific accessors
-11.8.28 'GIMPLE_TRY'
+11.8.28 `GIMPLE_TRY'
--------------------
- -- GIMPLE function: gtry *gimple_build_try (gimple_seq eval, gimple_seq
- cleanup, unsigned int kind)
- Build a 'GIMPLE_TRY' statement. 'EVAL' is a sequence with the
- expression to evaluate. 'CLEANUP' is a sequence of statements to
- run at clean-up time. 'KIND' is the enumeration value
- 'GIMPLE_TRY_CATCH' if this statement denotes a try/catch construct
- or 'GIMPLE_TRY_FINALLY' if this statement denotes a try/finally
+ -- GIMPLE function: gtry *gimple_build_try (gimple_seq eval,
+ gimple_seq cleanup, unsigned int kind)
+ Build a `GIMPLE_TRY' statement. `EVAL' is a sequence with the
+ expression to evaluate. `CLEANUP' is a sequence of statements to
+ run at clean-up time. `KIND' is the enumeration value
+ `GIMPLE_TRY_CATCH' if this statement denotes a try/catch construct
+ or `GIMPLE_TRY_FINALLY' if this statement denotes a try/finally
construct.
-- GIMPLE function: enum gimple_try_flags gimple_try_kind (gimple g)
- Return the kind of try block represented by 'GIMPLE_TRY' 'G'. This
- is either 'GIMPLE_TRY_CATCH' or 'GIMPLE_TRY_FINALLY'.
+ Return the kind of try block represented by `GIMPLE_TRY' `G'. This
+ is either `GIMPLE_TRY_CATCH' or `GIMPLE_TRY_FINALLY'.
-- GIMPLE function: bool gimple_try_catch_is_cleanup (gimple g)
- Return the 'GIMPLE_TRY_CATCH_IS_CLEANUP' flag.
+ Return the `GIMPLE_TRY_CATCH_IS_CLEANUP' flag.
-- GIMPLE function: gimple_seq gimple_try_eval (gimple g)
- Return the sequence of statements used as the body for 'GIMPLE_TRY'
- 'G'.
+ Return the sequence of statements used as the body for `GIMPLE_TRY'
+ `G'.
-- GIMPLE function: gimple_seq gimple_try_cleanup (gimple g)
Return the sequence of statements used as the cleanup body for
- 'GIMPLE_TRY' 'G'.
+ `GIMPLE_TRY' `G'.
-- GIMPLE function: void gimple_try_set_catch_is_cleanup (gimple g,
bool catch_is_cleanup)
- Set the 'GIMPLE_TRY_CATCH_IS_CLEANUP' flag.
+ Set the `GIMPLE_TRY_CATCH_IS_CLEANUP' flag.
-- GIMPLE function: void gimple_try_set_eval (gtry *g, gimple_seq eval)
- Set 'EVAL' to be the sequence of statements to use as the body for
- 'GIMPLE_TRY' 'G'.
+ Set `EVAL' to be the sequence of statements to use as the body for
+ `GIMPLE_TRY' `G'.
-- GIMPLE function: void gimple_try_set_cleanup (gtry *g, gimple_seq
cleanup)
- Set 'CLEANUP' to be the sequence of statements to use as the
- cleanup body for 'GIMPLE_TRY' 'G'.
+ Set `CLEANUP' to be the sequence of statements to use as the
+ cleanup body for `GIMPLE_TRY' `G'.

-File: gccint.info, Node: 'GIMPLE_WITH_CLEANUP_EXPR', Prev: 'GIMPLE_TRY', Up: Tuple specific accessors
+File: gccint.info, Node: `GIMPLE_WITH_CLEANUP_EXPR', Prev: `GIMPLE_TRY', Up: Tuple specific accessors
-11.8.29 'GIMPLE_WITH_CLEANUP_EXPR'
+11.8.29 `GIMPLE_WITH_CLEANUP_EXPR'
----------------------------------
-- GIMPLE function: gimple gimple_build_wce (gimple_seq cleanup)
- Build a 'GIMPLE_WITH_CLEANUP_EXPR' statement. 'CLEANUP' is the
+ Build a `GIMPLE_WITH_CLEANUP_EXPR' statement. `CLEANUP' is the
clean-up expression.
-- GIMPLE function: gimple_seq gimple_wce_cleanup (gimple g)
- Return the cleanup sequence for cleanup statement 'G'.
+ Return the cleanup sequence for cleanup statement `G'.
-- GIMPLE function: void gimple_wce_set_cleanup (gimple g, gimple_seq
cleanup)
- Set 'CLEANUP' to be the cleanup sequence for 'G'.
+ Set `CLEANUP' to be the cleanup sequence for `G'.
-- GIMPLE function: bool gimple_wce_cleanup_eh_only (gimple g)
- Return the 'CLEANUP_EH_ONLY' flag for a 'WCE' tuple.
+ Return the `CLEANUP_EH_ONLY' flag for a `WCE' tuple.
- -- GIMPLE function: void gimple_wce_set_cleanup_eh_only (gimple g, bool
- eh_only_p)
- Set the 'CLEANUP_EH_ONLY' flag for a 'WCE' tuple.
+ -- GIMPLE function: void gimple_wce_set_cleanup_eh_only (gimple g,
+ bool eh_only_p)
+ Set the `CLEANUP_EH_ONLY' flag for a `WCE' tuple.

File: gccint.info, Node: GIMPLE sequences, Next: Sequence iterators, Prev: Tuple specific accessors, Up: GIMPLE
@@ -12622,18 +12753,18 @@ File: gccint.info, Node: GIMPLE sequences, Next: Sequence iterators, Prev: Tu
11.9 GIMPLE sequences
=====================
-GIMPLE sequences are the tuple equivalent of 'STATEMENT_LIST''s used in
-'GENERIC'. They are used to chain statements together, and when used in
-conjunction with sequence iterators, provide a framework for iterating
-through statements.
+GIMPLE sequences are the tuple equivalent of `STATEMENT_LIST''s used in
+`GENERIC'. They are used to chain statements together, and when used
+in conjunction with sequence iterators, provide a framework for
+iterating through statements.
- GIMPLE sequences are of type struct 'gimple_sequence', but are more
+ GIMPLE sequences are of type struct `gimple_sequence', but are more
commonly passed by reference to functions dealing with sequences. The
-type for a sequence pointer is 'gimple_seq' which is the same as struct
-'gimple_sequence' *. When declaring a local sequence, you can define a
-local variable of type struct 'gimple_sequence'. When declaring a
+type for a sequence pointer is `gimple_seq' which is the same as struct
+`gimple_sequence' *. When declaring a local sequence, you can define a
+local variable of type struct `gimple_sequence'. When declaring a
sequence allocated on the garbage collected heap, use the function
-'gimple_seq_alloc' documented below.
+`gimple_seq_alloc' documented below.
There are convenience functions for iterating through sequences in the
section entitled Sequence Iterators.
@@ -12642,40 +12773,40 @@ section entitled Sequence Iterators.
-- GIMPLE function: void gimple_seq_add_stmt (gimple_seq *seq, gimple
g)
- Link a gimple statement to the end of the sequence *'SEQ' if 'G' is
- not 'NULL'. If *'SEQ' is 'NULL', allocate a sequence before
+ Link a gimple statement to the end of the sequence *`SEQ' if `G' is
+ not `NULL'. If *`SEQ' is `NULL', allocate a sequence before
linking.
-- GIMPLE function: void gimple_seq_add_seq (gimple_seq *dest,
gimple_seq src)
- Append sequence 'SRC' to the end of sequence *'DEST' if 'SRC' is
- not 'NULL'. If *'DEST' is 'NULL', allocate a new sequence before
+ Append sequence `SRC' to the end of sequence *`DEST' if `SRC' is
+ not `NULL'. If *`DEST' is `NULL', allocate a new sequence before
appending.
-- GIMPLE function: gimple_seq gimple_seq_deep_copy (gimple_seq src)
- Perform a deep copy of sequence 'SRC' and return the result.
+ Perform a deep copy of sequence `SRC' and return the result.
-- GIMPLE function: gimple_seq gimple_seq_reverse (gimple_seq seq)
- Reverse the order of the statements in the sequence 'SEQ'. Return
- 'SEQ'.
+ Reverse the order of the statements in the sequence `SEQ'. Return
+ `SEQ'.
-- GIMPLE function: gimple gimple_seq_first (gimple_seq s)
- Return the first statement in sequence 'S'.
+ Return the first statement in sequence `S'.
-- GIMPLE function: gimple gimple_seq_last (gimple_seq s)
- Return the last statement in sequence 'S'.
+ Return the last statement in sequence `S'.
-- GIMPLE function: void gimple_seq_set_last (gimple_seq s, gimple
last)
- Set the last statement in sequence 'S' to the statement in 'LAST'.
+ Set the last statement in sequence `S' to the statement in `LAST'.
-- GIMPLE function: void gimple_seq_set_first (gimple_seq s, gimple
first)
- Set the first statement in sequence 'S' to the statement in
- 'FIRST'.
+ Set the first statement in sequence `S' to the statement in
+ `FIRST'.
-- GIMPLE function: void gimple_seq_init (gimple_seq s)
- Initialize sequence 'S' to an empty sequence.
+ Initialize sequence `S' to an empty sequence.
-- GIMPLE function: gimple_seq gimple_seq_alloc (void)
Allocate a new sequence in the garbage collected store and return
@@ -12683,19 +12814,19 @@ section entitled Sequence Iterators.
-- GIMPLE function: void gimple_seq_copy (gimple_seq dest, gimple_seq
src)
- Copy the sequence 'SRC' into the sequence 'DEST'.
+ Copy the sequence `SRC' into the sequence `DEST'.
-- GIMPLE function: bool gimple_seq_empty_p (gimple_seq s)
- Return true if the sequence 'S' is empty.
+ Return true if the sequence `S' is empty.
-- GIMPLE function: gimple_seq bb_seq (basic_block bb)
- Returns the sequence of statements in 'BB'.
+ Returns the sequence of statements in `BB'.
-- GIMPLE function: void set_bb_seq (basic_block bb, gimple_seq seq)
- Sets the sequence of statements in 'BB' to 'SEQ'.
+ Sets the sequence of statements in `BB' to `SEQ'.
-- GIMPLE function: bool gimple_seq_singleton_p (gimple_seq seq)
- Determine whether 'SEQ' contains exactly one statement.
+ Determine whether `SEQ' contains exactly one statement.

File: gccint.info, Node: Sequence iterators, Next: Adding a new GIMPLE statement code, Prev: GIMPLE sequences, Up: GIMPLE
@@ -12704,15 +12835,15 @@ File: gccint.info, Node: Sequence iterators, Next: Adding a new GIMPLE stateme
========================
Sequence iterators are convenience constructs for iterating through
-statements in a sequence. Given a sequence 'SEQ', here is a typical use
-of gimple sequence iterators:
+statements in a sequence. Given a sequence `SEQ', here is a typical
+use of gimple sequence iterators:
gimple_stmt_iterator gsi;
for (gsi = gsi_start (seq); !gsi_end_p (gsi); gsi_next (&gsi))
{
gimple g = gsi_stmt (gsi);
- /* Do something with gimple statement G. */
+ /* Do something with gimple statement `G'. */
}
Backward iterations are possible:
@@ -12720,47 +12851,47 @@ of gimple sequence iterators:
for (gsi = gsi_last (seq); !gsi_end_p (gsi); gsi_prev (&gsi))
Forward and backward iterations on basic blocks are possible with
-'gsi_start_bb' and 'gsi_last_bb'.
+`gsi_start_bb' and `gsi_last_bb'.
In the documentation below we sometimes refer to enum
-'gsi_iterator_update'. The valid options for this enumeration are:
+`gsi_iterator_update'. The valid options for this enumeration are:
- * 'GSI_NEW_STMT' Only valid when a single statement is added. Move
+ * `GSI_NEW_STMT' Only valid when a single statement is added. Move
the iterator to it.
- * 'GSI_SAME_STMT' Leave the iterator at the same statement.
+ * `GSI_SAME_STMT' Leave the iterator at the same statement.
- * 'GSI_CONTINUE_LINKING' Move iterator to whatever position is
+ * `GSI_CONTINUE_LINKING' Move iterator to whatever position is
suitable for linking other statements in the same direction.
Below is a list of the functions used to manipulate and use statement
iterators.
-- GIMPLE function: gimple_stmt_iterator gsi_start (gimple_seq seq)
- Return a new iterator pointing to the sequence 'SEQ''s first
- statement. If 'SEQ' is empty, the iterator's basic block is
- 'NULL'. Use 'gsi_start_bb' instead when the iterator needs to
+ Return a new iterator pointing to the sequence `SEQ''s first
+ statement. If `SEQ' is empty, the iterator's basic block is
+ `NULL'. Use `gsi_start_bb' instead when the iterator needs to
always have the correct basic block set.
-- GIMPLE function: gimple_stmt_iterator gsi_start_bb (basic_block bb)
Return a new iterator pointing to the first statement in basic
- block 'BB'.
+ block `BB'.
-- GIMPLE function: gimple_stmt_iterator gsi_last (gimple_seq seq)
Return a new iterator initially pointing to the last statement of
- sequence 'SEQ'. If 'SEQ' is empty, the iterator's basic block is
- 'NULL'. Use 'gsi_last_bb' instead when the iterator needs to
+ sequence `SEQ'. If `SEQ' is empty, the iterator's basic block is
+ `NULL'. Use `gsi_last_bb' instead when the iterator needs to
always have the correct basic block set.
-- GIMPLE function: gimple_stmt_iterator gsi_last_bb (basic_block bb)
- Return a new iterator pointing to the last statement in basic block
- 'BB'.
+ Return a new iterator pointing to the last statement in basic
+ block `BB'.
-- GIMPLE function: bool gsi_end_p (gimple_stmt_iterator i)
- Return 'TRUE' if at the end of 'I'.
+ Return `TRUE' if at the end of `I'.
-- GIMPLE function: bool gsi_one_before_end_p (gimple_stmt_iterator i)
- Return 'TRUE' if we're one statement before the end of 'I'.
+ Return `TRUE' if we're one statement before the end of `I'.
-- GIMPLE function: void gsi_next (gimple_stmt_iterator *i)
Advance the iterator to the next gimple statement.
@@ -12774,7 +12905,7 @@ iterators.
-- GIMPLE function: gimple_stmt_iterator gsi_after_labels (basic_block
bb)
Return a block statement iterator that points to the first
- non-label statement in block 'BB'.
+ non-label statement in block `BB'.
-- GIMPLE function: gimple * gsi_stmt_ptr (gimple_stmt_iterator *i)
Return a pointer to the current stmt.
@@ -12787,108 +12918,108 @@ iterators.
-- GIMPLE function: void gsi_remove (gimple_stmt_iterator *i, bool
remove_eh_info)
- Remove the current stmt from the sequence. The iterator is updated
- to point to the next statement. When 'REMOVE_EH_INFO' is true we
- remove the statement pointed to by iterator 'I' from the 'EH'
- tables. Otherwise we do not modify the 'EH' tables. Generally,
- 'REMOVE_EH_INFO' should be true when the statement is going to be
- removed from the 'IL' and not reinserted elsewhere.
+ Remove the current stmt from the sequence. The iterator is
+ updated to point to the next statement. When `REMOVE_EH_INFO' is
+ true we remove the statement pointed to by iterator `I' from the
+ `EH' tables. Otherwise we do not modify the `EH' tables.
+ Generally, `REMOVE_EH_INFO' should be true when the statement is
+ going to be removed from the `IL' and not reinserted elsewhere.
-- GIMPLE function: void gsi_link_seq_before (gimple_stmt_iterator *i,
gimple_seq seq, enum gsi_iterator_update mode)
- Links the sequence of statements 'SEQ' before the statement pointed
- by iterator 'I'. 'MODE' indicates what to do with the iterator
- after insertion (see 'enum gsi_iterator_update' above).
+ Links the sequence of statements `SEQ' before the statement pointed
+ by iterator `I'. `MODE' indicates what to do with the iterator
+ after insertion (see `enum gsi_iterator_update' above).
-- GIMPLE function: void gsi_link_before (gimple_stmt_iterator *i,
gimple g, enum gsi_iterator_update mode)
- Links statement 'G' before the statement pointed-to by iterator
- 'I'. Updates iterator 'I' according to 'MODE'.
+ Links statement `G' before the statement pointed-to by iterator
+ `I'. Updates iterator `I' according to `MODE'.
-- GIMPLE function: void gsi_link_seq_after (gimple_stmt_iterator *i,
gimple_seq seq, enum gsi_iterator_update mode)
- Links sequence 'SEQ' after the statement pointed-to by iterator
- 'I'. 'MODE' is as in 'gsi_insert_after'.
+ Links sequence `SEQ' after the statement pointed-to by iterator
+ `I'. `MODE' is as in `gsi_insert_after'.
-- GIMPLE function: void gsi_link_after (gimple_stmt_iterator *i,
gimple g, enum gsi_iterator_update mode)
- Links statement 'G' after the statement pointed-to by iterator 'I'.
- 'MODE' is as in 'gsi_insert_after'.
+ Links statement `G' after the statement pointed-to by iterator `I'.
+ `MODE' is as in `gsi_insert_after'.
-- GIMPLE function: gimple_seq gsi_split_seq_after
(gimple_stmt_iterator i)
- Move all statements in the sequence after 'I' to a new sequence.
+ Move all statements in the sequence after `I' to a new sequence.
Return this new sequence.
-- GIMPLE function: gimple_seq gsi_split_seq_before
(gimple_stmt_iterator *i)
- Move all statements in the sequence before 'I' to a new sequence.
+ Move all statements in the sequence before `I' to a new sequence.
Return this new sequence.
-- GIMPLE function: void gsi_replace (gimple_stmt_iterator *i, gimple
stmt, bool update_eh_info)
- Replace the statement pointed-to by 'I' to 'STMT'. If
- 'UPDATE_EH_INFO' is true, the exception handling information of the
- original statement is moved to the new statement.
+ Replace the statement pointed-to by `I' to `STMT'. If
+ `UPDATE_EH_INFO' is true, the exception handling information of
+ the original statement is moved to the new statement.
-- GIMPLE function: void gsi_insert_before (gimple_stmt_iterator *i,
gimple stmt, enum gsi_iterator_update mode)
- Insert statement 'STMT' before the statement pointed-to by iterator
- 'I', update 'STMT''s basic block and scan it for new operands.
- 'MODE' specifies how to update iterator 'I' after insertion (see
- enum 'gsi_iterator_update').
+ Insert statement `STMT' before the statement pointed-to by iterator
+ `I', update `STMT''s basic block and scan it for new operands.
+ `MODE' specifies how to update iterator `I' after insertion (see
+ enum `gsi_iterator_update').
-- GIMPLE function: void gsi_insert_seq_before (gimple_stmt_iterator
*i, gimple_seq seq, enum gsi_iterator_update mode)
- Like 'gsi_insert_before', but for all the statements in 'SEQ'.
+ Like `gsi_insert_before', but for all the statements in `SEQ'.
-- GIMPLE function: void gsi_insert_after (gimple_stmt_iterator *i,
gimple stmt, enum gsi_iterator_update mode)
- Insert statement 'STMT' after the statement pointed-to by iterator
- 'I', update 'STMT''s basic block and scan it for new operands.
- 'MODE' specifies how to update iterator 'I' after insertion (see
- enum 'gsi_iterator_update').
+ Insert statement `STMT' after the statement pointed-to by iterator
+ `I', update `STMT''s basic block and scan it for new operands.
+ `MODE' specifies how to update iterator `I' after insertion (see
+ enum `gsi_iterator_update').
- -- GIMPLE function: void gsi_insert_seq_after (gimple_stmt_iterator *i,
- gimple_seq seq, enum gsi_iterator_update mode)
- Like 'gsi_insert_after', but for all the statements in 'SEQ'.
+ -- GIMPLE function: void gsi_insert_seq_after (gimple_stmt_iterator
+ *i, gimple_seq seq, enum gsi_iterator_update mode)
+ Like `gsi_insert_after', but for all the statements in `SEQ'.
-- GIMPLE function: gimple_stmt_iterator gsi_for_stmt (gimple stmt)
- Finds iterator for 'STMT'.
+ Finds iterator for `STMT'.
-- GIMPLE function: void gsi_move_after (gimple_stmt_iterator *from,
gimple_stmt_iterator *to)
- Move the statement at 'FROM' so it comes right after the statement
- at 'TO'.
+ Move the statement at `FROM' so it comes right after the statement
+ at `TO'.
-- GIMPLE function: void gsi_move_before (gimple_stmt_iterator *from,
gimple_stmt_iterator *to)
- Move the statement at 'FROM' so it comes right before the statement
- at 'TO'.
+ Move the statement at `FROM' so it comes right before the statement
+ at `TO'.
-- GIMPLE function: void gsi_move_to_bb_end (gimple_stmt_iterator
*from, basic_block bb)
- Move the statement at 'FROM' to the end of basic block 'BB'.
+ Move the statement at `FROM' to the end of basic block `BB'.
-- GIMPLE function: void gsi_insert_on_edge (edge e, gimple stmt)
- Add 'STMT' to the pending list of edge 'E'. No actual insertion is
- made until a call to 'gsi_commit_edge_inserts'() is made.
+ Add `STMT' to the pending list of edge `E'. No actual insertion is
+ made until a call to `gsi_commit_edge_inserts'() is made.
-- GIMPLE function: void gsi_insert_seq_on_edge (edge e, gimple_seq
seq)
- Add the sequence of statements in 'SEQ' to the pending list of edge
- 'E'. No actual insertion is made until a call to
- 'gsi_commit_edge_inserts'() is made.
+ Add the sequence of statements in `SEQ' to the pending list of edge
+ `E'. No actual insertion is made until a call to
+ `gsi_commit_edge_inserts'() is made.
-- GIMPLE function: basic_block gsi_insert_on_edge_immediate (edge e,
gimple stmt)
- Similar to 'gsi_insert_on_edge'+'gsi_commit_edge_inserts'. If a
+ Similar to `gsi_insert_on_edge'+`gsi_commit_edge_inserts'. If a
new block has to be created, it is returned.
-- GIMPLE function: void gsi_commit_one_edge_insert (edge e,
basic_block *new_bb)
- Commit insertions pending at edge 'E'. If a new block is created,
- set 'NEW_BB' to this block, otherwise set it to 'NULL'.
+ Commit insertions pending at edge `E'. If a new block is created,
+ set `NEW_BB' to this block, otherwise set it to `NULL'.
-- GIMPLE function: void gsi_commit_edge_inserts (void)
This routine will commit all pending edge insertions, creating any
@@ -12901,27 +13032,28 @@ File: gccint.info, Node: Adding a new GIMPLE statement code, Next: Statement a
========================================
The first step in adding a new GIMPLE statement code, is modifying the
-file 'gimple.def', which contains all the GIMPLE codes. Then you must
+file `gimple.def', which contains all the GIMPLE codes. Then you must
add a corresponding gimple_statement_base subclass located in
-'gimple.h'. This in turn, will require you to add a corresponding 'GTY'
-tag in 'gsstruct.def', and code to handle this tag in 'gss_for_code'
-which is located in 'gimple.c'.
+`gimple.h'. This in turn, will require you to add a corresponding
+`GTY' tag in `gsstruct.def', and code to handle this tag in
+`gss_for_code' which is located in `gimple.c'.
In order for the garbage collector to know the size of the structure
-you created in 'gimple.h', you need to add a case to handle your new
-GIMPLE statement in 'gimple_size' which is located in 'gimple.c'.
+you created in `gimple.h', you need to add a case to handle your new
+GIMPLE statement in `gimple_size' which is located in `gimple.c'.
You will probably want to create a function to build the new gimple
-statement in 'gimple.c'. The function should be called
-'gimple_build_NEW-TUPLE-NAME', and should return the new tuple as a
+statement in `gimple.c'. The function should be called
+`gimple_build_NEW-TUPLE-NAME', and should return the new tuple as a
pointer to the appropriate gimple_statement_base subclass.
- If your new statement requires accessors for any members or operands it
-may have, put simple inline accessors in 'gimple.h' and any non-trivial
-accessors in 'gimple.c' with a corresponding prototype in 'gimple.h'.
+ If your new statement requires accessors for any members or operands
+it may have, put simple inline accessors in `gimple.h' and any
+non-trivial accessors in `gimple.c' with a corresponding prototype in
+`gimple.h'.
You should add the new statement subclass to the class hierarchy
-diagram in 'gimple.texi'.
+diagram in `gimple.texi'.

File: gccint.info, Node: Statement and operand traversals, Prev: Adding a new GIMPLE statement code, Up: GIMPLE
@@ -12930,54 +13062,54 @@ File: gccint.info, Node: Statement and operand traversals, Prev: Adding a new
======================================
There are two functions available for walking statements and sequences:
-'walk_gimple_stmt' and 'walk_gimple_seq', accordingly, and a third
-function for walking the operands in a statement: 'walk_gimple_op'.
+`walk_gimple_stmt' and `walk_gimple_seq', accordingly, and a third
+function for walking the operands in a statement: `walk_gimple_op'.
-- GIMPLE function: tree walk_gimple_stmt (gimple_stmt_iterator *gsi,
walk_stmt_fn callback_stmt, walk_tree_fn callback_op, struct
walk_stmt_info *wi)
- This function is used to walk the current statement in 'GSI',
- optionally using traversal state stored in 'WI'. If 'WI' is
- 'NULL', no state is kept during the traversal.
+ This function is used to walk the current statement in `GSI',
+ optionally using traversal state stored in `WI'. If `WI' is
+ `NULL', no state is kept during the traversal.
- The callback 'CALLBACK_STMT' is called. If 'CALLBACK_STMT' returns
+ The callback `CALLBACK_STMT' is called. If `CALLBACK_STMT' returns
true, it means that the callback function has handled all the
operands of the statement and it is not necessary to walk its
operands.
- If 'CALLBACK_STMT' is 'NULL' or it returns false, 'CALLBACK_OP' is
- called on each operand of the statement via 'walk_gimple_op'. If
- 'walk_gimple_op' returns non-'NULL' for any operand, the remaining
+ If `CALLBACK_STMT' is `NULL' or it returns false, `CALLBACK_OP' is
+ called on each operand of the statement via `walk_gimple_op'. If
+ `walk_gimple_op' returns non-`NULL' for any operand, the remaining
operands are not scanned.
The return value is that returned by the last call to
- 'walk_gimple_op', or 'NULL_TREE' if no 'CALLBACK_OP' is specified.
+ `walk_gimple_op', or `NULL_TREE' if no `CALLBACK_OP' is specified.
-- GIMPLE function: tree walk_gimple_op (gimple stmt, walk_tree_fn
callback_op, struct walk_stmt_info *wi)
- Use this function to walk the operands of statement 'STMT'. Every
- operand is walked via 'walk_tree' with optional state information
- in 'WI'.
+ Use this function to walk the operands of statement `STMT'. Every
+ operand is walked via `walk_tree' with optional state information
+ in `WI'.
- 'CALLBACK_OP' is called on each operand of 'STMT' via 'walk_tree'.
- Additional parameters to 'walk_tree' must be stored in 'WI'. For
- each operand 'OP', 'walk_tree' is called as:
+ `CALLBACK_OP' is called on each operand of `STMT' via `walk_tree'.
+ Additional parameters to `walk_tree' must be stored in `WI'. For
+ each operand `OP', `walk_tree' is called as:
- walk_tree (&OP, CALLBACK_OP, WI, PSET)
+ walk_tree (&`OP', `CALLBACK_OP', `WI', `PSET')
- If 'CALLBACK_OP' returns non-'NULL' for an operand, the remaining
- operands are not scanned. The return value is that returned by the
- last call to 'walk_tree', or 'NULL_TREE' if no 'CALLBACK_OP' is
+ If `CALLBACK_OP' returns non-`NULL' for an operand, the remaining
+ operands are not scanned. The return value is that returned by
+ the last call to `walk_tree', or `NULL_TREE' if no `CALLBACK_OP' is
specified.
-- GIMPLE function: tree walk_gimple_seq (gimple_seq seq, walk_stmt_fn
- callback_stmt, walk_tree_fn callback_op, struct walk_stmt_info
- *wi)
- This function walks all the statements in the sequence 'SEQ'
- calling 'walk_gimple_stmt' on each one. 'WI' is as in
- 'walk_gimple_stmt'. If 'walk_gimple_stmt' returns non-'NULL', the
+ callback_stmt, walk_tree_fn callback_op, struct
+ walk_stmt_info *wi)
+ This function walks all the statements in the sequence `SEQ'
+ calling `walk_gimple_stmt' on each one. `WI' is as in
+ `walk_gimple_stmt'. If `walk_gimple_stmt' returns non-`NULL', the
walk is stopped and the value returned. Otherwise, all the
- statements are walked and 'NULL_TREE' returned.
+ statements are walked and `NULL_TREE' returned.

File: gccint.info, Node: Tree SSA, Next: RTL, Prev: GIMPLE, Up: Top
@@ -12988,25 +13120,25 @@ File: gccint.info, Node: Tree SSA, Next: RTL, Prev: GIMPLE, Up: Top
GCC uses three main intermediate languages to represent the program
during compilation: GENERIC, GIMPLE and RTL. GENERIC is a
language-independent representation generated by each front end. It is
-used to serve as an interface between the parser and optimizer. GENERIC
-is a common representation that is able to represent programs written in
-all the languages supported by GCC.
+used to serve as an interface between the parser and optimizer.
+GENERIC is a common representation that is able to represent programs
+written in all the languages supported by GCC.
GIMPLE and RTL are used to optimize the program. GIMPLE is used for
target and language independent optimizations (e.g., inlining, constant
propagation, tail call elimination, redundancy elimination, etc). Much
like GENERIC, GIMPLE is a language independent, tree based
representation. However, it differs from GENERIC in that the GIMPLE
-grammar is more restrictive: expressions contain no more than 3 operands
-(except function calls), it has no control flow structures and
-expressions with side-effects are only allowed on the right hand side of
-assignments. See the chapter describing GENERIC and GIMPLE for more
+grammar is more restrictive: expressions contain no more than 3
+operands (except function calls), it has no control flow structures and
+expressions with side-effects are only allowed on the right hand side
+of assignments. See the chapter describing GENERIC and GIMPLE for more
details.
This chapter describes the data structures and functions used in the
-GIMPLE optimizers (also known as "tree optimizers" or "middle end"). In
-particular, it focuses on all the macros, data structures, functions and
-programming constructs needed to implement optimization passes for
+GIMPLE optimizers (also known as "tree optimizers" or "middle end").
+In particular, it focuses on all the macros, data structures, functions
+and programming constructs needed to implement optimization passes for
GIMPLE.
* Menu:
@@ -13026,7 +13158,7 @@ File: gccint.info, Node: Annotations, Next: SSA Operands, Up: Tree SSA
The optimizers need to associate attributes with variables during the
optimization process. For instance, we need to know whether a variable
has aliases. All these attributes are stored in data structures called
-annotations which are then linked to the field 'ann' in 'struct
+annotations which are then linked to the field `ann' in `struct
tree_common'.

@@ -13041,42 +13173,43 @@ their operands are going to be located at various spots inside the
statement's tree. To facilitate access to the statement's operands,
they are organized into lists associated inside each statement's
annotation. Each element in an operand list is a pointer to a
-'VAR_DECL', 'PARM_DECL' or 'SSA_NAME' tree node. This provides a very
+`VAR_DECL', `PARM_DECL' or `SSA_NAME' tree node. This provides a very
convenient way of examining and replacing operands.
Data flow analysis and optimization is done on all tree nodes
-representing variables. Any node for which 'SSA_VAR_P' returns nonzero
+representing variables. Any node for which `SSA_VAR_P' returns nonzero
is considered when scanning statement operands. However, not all
-'SSA_VAR_P' variables are processed in the same way. For the purposes
+`SSA_VAR_P' variables are processed in the same way. For the purposes
of optimization, we need to distinguish between references to local
-scalar variables and references to globals, statics, structures, arrays,
-aliased variables, etc. The reason is simple, the compiler can gather
-complete data flow information for a local scalar. On the other hand, a
-global variable may be modified by a function call, it may not be
-possible to keep track of all the elements of an array or the fields of
-a structure, etc.
+scalar variables and references to globals, statics, structures,
+arrays, aliased variables, etc. The reason is simple, the compiler can
+gather complete data flow information for a local scalar. On the other
+hand, a global variable may be modified by a function call, it may not
+be possible to keep track of all the elements of an array or the fields
+of a structure, etc.
The operand scanner gathers two kinds of operands: "real" and
-"virtual". An operand for which 'is_gimple_reg' returns true is
-considered real, otherwise it is a virtual operand. We also distinguish
-between uses and definitions. An operand is used if its value is loaded
-by the statement (e.g., the operand at the RHS of an assignment). If
-the statement assigns a new value to the operand, the operand is
-considered a definition (e.g., the operand at the LHS of an assignment).
+"virtual". An operand for which `is_gimple_reg' returns true is
+considered real, otherwise it is a virtual operand. We also
+distinguish between uses and definitions. An operand is used if its
+value is loaded by the statement (e.g., the operand at the RHS of an
+assignment). If the statement assigns a new value to the operand, the
+operand is considered a definition (e.g., the operand at the LHS of an
+assignment).
Virtual and real operands also have very different data flow
-properties. Real operands are unambiguous references to the full object
-that they represent. For instance, given
+properties. Real operands are unambiguous references to the full
+object that they represent. For instance, given
{
int a, b;
a = b
}
- Since 'a' and 'b' are non-aliased locals, the statement 'a = b' will
-have one real definition and one real use because variable 'a' is
-completely modified with the contents of variable 'b'. Real definition
-are also known as "killing definitions". Similarly, the use of 'b'
+ Since `a' and `b' are non-aliased locals, the statement `a = b' will
+have one real definition and one real use because variable `a' is
+completely modified with the contents of variable `b'. Real definition
+are also known as "killing definitions". Similarly, the use of `b'
reads all its bits.
In contrast, virtual operands are used with variables that can have a
@@ -13086,10 +13219,10 @@ definitions. For globals, structures, and arrays, we can determine from
a statement whether a variable of these types has a killing definition.
If the variable does, then the statement is marked as having a "must
definition" of that variable. However, if a statement is only defining
-a part of the variable (i.e. a field in a structure), or if we know that
-a statement might define the variable but we cannot say for sure, then
-we mark that statement as having a "may definition". For instance,
-given
+a part of the variable (i.e. a field in a structure), or if we know
+that a statement might define the variable but we cannot say for sure,
+then we mark that statement as having a "may definition". For
+instance, given
{
int a, b, *p;
@@ -13102,13 +13235,14 @@ given
return *p;
}
- The assignment '*p = 5' may be a definition of 'a' or 'b'. If we
-cannot determine statically where 'p' is pointing to at the time of the
-store operation, we create virtual definitions to mark that statement as
-a potential definition site for 'a' and 'b'. Memory loads are similarly
-marked with virtual use operands. Virtual operands are shown in tree
-dumps right before the statement that contains them. To request a tree
-dump with virtual operands, use the '-vops' option to '-fdump-tree':
+ The assignment `*p = 5' may be a definition of `a' or `b'. If we
+cannot determine statically where `p' is pointing to at the time of the
+store operation, we create virtual definitions to mark that statement
+as a potential definition site for `a' and `b'. Memory loads are
+similarly marked with virtual use operands. Virtual operands are shown
+in tree dumps right before the statement that contains them. To
+request a tree dump with virtual operands, use the `-vops' option to
+`-fdump-tree':
{
int a, b, *p;
@@ -13126,54 +13260,55 @@ dump with virtual operands, use the '-vops' option to '-fdump-tree':
return *p;
}
- Notice that 'VDEF' operands have two copies of the referenced variable.
-This indicates that this is not a killing definition of that variable.
-In this case we refer to it as a "may definition" or "aliased store".
-The presence of the second copy of the variable in the 'VDEF' operand
-will become important when the function is converted into SSA form.
-This will be used to link all the non-killing definitions to prevent
-optimizations from making incorrect assumptions about them.
-
- Operands are updated as soon as the statement is finished via a call to
-'update_stmt'. If statement elements are changed via 'SET_USE' or
-'SET_DEF', then no further action is required (i.e., those macros take
+ Notice that `VDEF' operands have two copies of the referenced
+variable. This indicates that this is not a killing definition of that
+variable. In this case we refer to it as a "may definition" or
+"aliased store". The presence of the second copy of the variable in
+the `VDEF' operand will become important when the function is converted
+into SSA form. This will be used to link all the non-killing
+definitions to prevent optimizations from making incorrect assumptions
+about them.
+
+ Operands are updated as soon as the statement is finished via a call
+to `update_stmt'. If statement elements are changed via `SET_USE' or
+`SET_DEF', then no further action is required (i.e., those macros take
care of updating the statement). If changes are made by manipulating
-the statement's tree directly, then a call must be made to 'update_stmt'
-when complete. Calling one of the 'bsi_insert' routines or
-'bsi_replace' performs an implicit call to 'update_stmt'.
+the statement's tree directly, then a call must be made to
+`update_stmt' when complete. Calling one of the `bsi_insert' routines
+or `bsi_replace' performs an implicit call to `update_stmt'.
12.2.1 Operand Iterators And Access Routines
--------------------------------------------
-Operands are collected by 'tree-ssa-operands.c'. They are stored inside
-each statement's annotation and can be accessed through either the
-operand iterators or an access routine.
+Operands are collected by `tree-ssa-operands.c'. They are stored
+inside each statement's annotation and can be accessed through either
+the operand iterators or an access routine.
The following access routines are available for examining operands:
- 1. 'SINGLE_SSA_{USE,DEF,TREE}_OPERAND': These accessors will return
+ 1. `SINGLE_SSA_{USE,DEF,TREE}_OPERAND': These accessors will return
NULL unless there is exactly one operand matching the specified
- flags. If there is exactly one operand, the operand is returned as
- either a 'tree', 'def_operand_p', or 'use_operand_p'.
+ flags. If there is exactly one operand, the operand is returned
+ as either a `tree', `def_operand_p', or `use_operand_p'.
tree t = SINGLE_SSA_TREE_OPERAND (stmt, flags);
use_operand_p u = SINGLE_SSA_USE_OPERAND (stmt, SSA_ALL_VIRTUAL_USES);
def_operand_p d = SINGLE_SSA_DEF_OPERAND (stmt, SSA_OP_ALL_DEFS);
- 2. 'ZERO_SSA_OPERANDS': This macro returns true if there are no
+ 2. `ZERO_SSA_OPERANDS': This macro returns true if there are no
operands matching the specified flags.
if (ZERO_SSA_OPERANDS (stmt, SSA_OP_ALL_VIRTUALS))
return;
- 3. 'NUM_SSA_OPERANDS': This macro Returns the number of operands
+ 3. `NUM_SSA_OPERANDS': This macro Returns the number of operands
matching 'flags'. This actually executes a loop to perform the
count, so only use this if it is really needed.
int count = NUM_SSA_OPERANDS (stmt, flags)
If you wish to iterate over some or all operands, use the
-'FOR_EACH_SSA_{USE,DEF,TREE}_OPERAND' iterator. For example, to print
+`FOR_EACH_SSA_{USE,DEF,TREE}_OPERAND' iterator. For example, to print
all the operands for a statement:
void
@@ -13188,8 +13323,8 @@ all the operands for a statement:
How to choose the appropriate iterator:
- 1. Determine whether you are need to see the operand pointers, or just
- the trees, and choose the appropriate macro:
+ 1. Determine whether you are need to see the operand pointers, or
+ just the trees, and choose the appropriate macro:
Need Macro:
---- -------
@@ -13203,7 +13338,7 @@ all the operands for a statement:
3. Determine which operands you wish to use, and specify the flags of
those you are interested in. They are documented in
- 'tree-ssa-operands.h':
+ `tree-ssa-operands.h':
#define SSA_OP_USE 0x01 /* Real USE operands. */
#define SSA_OP_DEF 0x02 /* Real DEF operands. */
@@ -13218,8 +13353,8 @@ all the operands for a statement:
#define SSA_OP_ALL_DEFS (SSA_OP_VIRTUAL_DEFS | SSA_OP_DEF)
#define SSA_OP_ALL_OPERANDS (SSA_OP_ALL_USES | SSA_OP_ALL_DEFS)
- So if you want to look at the use pointers for all the 'USE' and 'VUSE'
-operands, you would do something like:
+ So if you want to look at the use pointers for all the `USE' and
+`VUSE' operands, you would do something like:
use_operand_p use_p;
ssa_op_iter iter;
@@ -13229,10 +13364,10 @@ operands, you would do something like:
process_use_ptr (use_p);
}
- The 'TREE' macro is basically the same as the 'USE' and 'DEF' macros,
-only with the use or def dereferenced via 'USE_FROM_PTR (use_p)' and
-'DEF_FROM_PTR (def_p)'. Since we aren't using operand pointers, use and
-defs flags can be mixed.
+ The `TREE' macro is basically the same as the `USE' and `DEF' macros,
+only with the use or def dereferenced via `USE_FROM_PTR (use_p)' and
+`DEF_FROM_PTR (def_p)'. Since we aren't using operand pointers, use
+and defs flags can be mixed.
tree var;
ssa_op_iter iter;
@@ -13242,17 +13377,17 @@ defs flags can be mixed.
print_generic_expr (stderr, var, TDF_SLIM);
}
- 'VDEF's are broken into two flags, one for the 'DEF' portion
-('SSA_OP_VDEF') and one for the USE portion ('SSA_OP_VUSE').
+ `VDEF's are broken into two flags, one for the `DEF' portion
+(`SSA_OP_VDEF') and one for the USE portion (`SSA_OP_VUSE').
There are many examples in the code, in addition to the documentation
-in 'tree-ssa-operands.h' and 'ssa-iterators.h'.
+in `tree-ssa-operands.h' and `ssa-iterators.h'.
There are also a couple of variants on the stmt iterators regarding PHI
nodes.
- 'FOR_EACH_PHI_ARG' Works exactly like 'FOR_EACH_SSA_USE_OPERAND',
-except it works over 'PHI' arguments instead of statement operands.
+ `FOR_EACH_PHI_ARG' Works exactly like `FOR_EACH_SSA_USE_OPERAND',
+except it works over `PHI' arguments instead of statement operands.
/* Look at every virtual PHI use. */
FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_VIRTUAL_USES)
@@ -13268,11 +13403,11 @@ except it works over 'PHI' arguments instead of statement operands.
FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_ALL_USES)
my_code;
- 'FOR_EACH_PHI_OR_STMT_{USE,DEF}' works exactly like
-'FOR_EACH_SSA_{USE,DEF}_OPERAND', except it will function on either a
-statement or a 'PHI' node. These should be used when it is appropriate
-but they are not quite as efficient as the individual 'FOR_EACH_PHI' and
-'FOR_EACH_SSA' routines.
+ `FOR_EACH_PHI_OR_STMT_{USE,DEF}' works exactly like
+`FOR_EACH_SSA_{USE,DEF}_OPERAND', except it will function on either a
+statement or a `PHI' node. These should be used when it is appropriate
+but they are not quite as efficient as the individual `FOR_EACH_PHI'
+and `FOR_EACH_SSA' routines.
FOR_EACH_PHI_OR_STMT_USE (use_operand_p, stmt, iter, flags)
{
@@ -13288,8 +13423,8 @@ but they are not quite as efficient as the individual 'FOR_EACH_PHI' and
---------------------
Immediate use information is now always available. Using the immediate
-use iterators, you may examine every use of any 'SSA_NAME'. For
-instance, to change each use of 'ssa_var' to 'ssa_var2' and call
+use iterators, you may examine every use of any `SSA_NAME'. For
+instance, to change each use of `ssa_var' to `ssa_var2' and call
fold_stmt on each stmt after that is done:
use_operand_p imm_use_p;
@@ -13304,21 +13439,21 @@ fold_stmt on each stmt after that is done:
fold_stmt (stmt);
}
- There are 2 iterators which can be used. 'FOR_EACH_IMM_USE_FAST' is
+ There are 2 iterators which can be used. `FOR_EACH_IMM_USE_FAST' is
used when the immediate uses are not changed, i.e., you are looking at
the uses, but not setting them.
If they do get changed, then care must be taken that things are not
-changed under the iterators, so use the 'FOR_EACH_IMM_USE_STMT' and
-'FOR_EACH_IMM_USE_ON_STMT' iterators. They attempt to preserve the
+changed under the iterators, so use the `FOR_EACH_IMM_USE_STMT' and
+`FOR_EACH_IMM_USE_ON_STMT' iterators. They attempt to preserve the
sanity of the use list by moving all the uses for a statement into a
controlled position, and then iterating over those uses. Then the
optimization can manipulate the stmt when all the uses have been
processed. This is a little slower than the FAST version since it adds
a placeholder element and must sort through the list a bit for each
-statement. This placeholder element must be also be removed if the loop
-is terminated early. The macro 'BREAK_FROM_IMM_USE_SAFE' is provided to
-do this :
+statement. This placeholder element must be also be removed if the
+loop is terminated early. The macro `BREAK_FROM_IMM_USE_SAFE' is
+provided to do this :
FOR_EACH_IMM_USE_STMT (stmt, iterator, ssa_var)
{
@@ -13330,31 +13465,36 @@ do this :
fold_stmt (stmt);
}
- There are checks in 'verify_ssa' which verify that the immediate use
+ There are checks in `verify_ssa' which verify that the immediate use
list is up to date, as well as checking that an optimization didn't
break from the loop without using this macro. It is safe to simply
-'break'; from a 'FOR_EACH_IMM_USE_FAST' traverse.
+'break'; from a `FOR_EACH_IMM_USE_FAST' traverse.
Some useful functions and macros:
- 1. 'has_zero_uses (ssa_var)' : Returns true if there are no uses of
- 'ssa_var'.
- 2. 'has_single_use (ssa_var)' : Returns true if there is only a single
- use of 'ssa_var'.
- 3. 'single_imm_use (ssa_var, use_operand_p *ptr, tree *stmt)' :
- Returns true if there is only a single use of 'ssa_var', and also
+ 1. `has_zero_uses (ssa_var)' : Returns true if there are no uses of
+ `ssa_var'.
+
+ 2. `has_single_use (ssa_var)' : Returns true if there is only a
+ single use of `ssa_var'.
+
+ 3. `single_imm_use (ssa_var, use_operand_p *ptr, tree *stmt)' :
+ Returns true if there is only a single use of `ssa_var', and also
returns the use pointer and statement it occurs in, in the second
and third parameters.
- 4. 'num_imm_uses (ssa_var)' : Returns the number of immediate uses of
- 'ssa_var'. It is better not to use this if possible since it
- simply utilizes a loop to count the uses.
- 5. 'PHI_ARG_INDEX_FROM_USE (use_p)' : Given a use within a 'PHI' node,
- return the index number for the use. An assert is triggered if the
- use isn't located in a 'PHI' node.
- 6. 'USE_STMT (use_p)' : Return the statement a use occurs in.
+
+ 4. `num_imm_uses (ssa_var)' : Returns the number of immediate uses of
+ `ssa_var'. It is better not to use this if possible since it simply
+ utilizes a loop to count the uses.
+
+ 5. `PHI_ARG_INDEX_FROM_USE (use_p)' : Given a use within a `PHI'
+ node, return the index number for the use. An assert is triggered
+ if the use isn't located in a `PHI' node.
+
+ 6. `USE_STMT (use_p)' : Return the statement a use occurs in.
Note that uses are not put into an immediate use list until their
-statement is actually inserted into the instruction stream via a 'bsi_*'
-routine.
+statement is actually inserted into the instruction stream via a
+`bsi_*' routine.
It is also still possible to utilize lazy updating of statements, but
this should be used only when absolutely required. Both alias analysis
@@ -13362,11 +13502,11 @@ and the dominator optimizations currently do this.
When lazy updating is being used, the immediate use information is out
of date and cannot be used reliably. Lazy updating is achieved by
-simply marking statements modified via calls to 'mark_stmt_modified'
-instead of 'update_stmt'. When lazy updating is no longer required, all
-the modified statements must have 'update_stmt' called in order to bring
-them up to date. This must be done before the optimization is finished,
-or 'verify_ssa' will trigger an abort.
+simply marking statements modified via calls to `mark_stmt_modified'
+instead of `update_stmt'. When lazy updating is no longer required,
+all the modified statements must have `update_stmt' called in order to
+bring them up to date. This must be done before the optimization is
+finished, or `verify_ssa' will trigger an abort.
This is done with a simple loop over the instruction stream:
block_stmt_iterator bsi;
@@ -13385,10 +13525,10 @@ File: gccint.info, Node: SSA, Next: Alias analysis, Prev: SSA Operands, Up:
Most of the tree optimizers rely on the data flow information provided
by the Static Single Assignment (SSA) form. We implement the SSA form
-as described in 'R. Cytron, J. Ferrante, B. Rosen, M. Wegman, and K.
-Zadeck. Efficiently Computing Static Single Assignment Form and the
-Control Dependence Graph. ACM Transactions on Programming Languages and
-Systems, 13(4):451-490, October 1991'.
+as described in `R. Cytron, J. Ferrante, B. Rosen, M. Wegman, and K.
+Zadeck. Efficiently Computing Static Single Assignment Form and the
+Control Dependence Graph. ACM Transactions on Programming Languages
+and Systems, 13(4):451-490, October 1991'.
The SSA form is based on the premise that program variables are
assigned in exactly one location in the program. Multiple assignments
@@ -13399,14 +13539,14 @@ representation so that every time a variable is assigned in the code, a
new version of the variable is created. Different versions of the same
variable are distinguished by subscripting the variable name with its
version number. Variables used in the right-hand side of expressions
-are renamed so that their version number matches that of the most recent
-assignment.
+are renamed so that their version number matches that of the most
+recent assignment.
- We represent variable versions using 'SSA_NAME' nodes. The renaming
-process in 'tree-ssa.c' wraps every real and virtual operand with an
-'SSA_NAME' node which contains the version number and the statement that
-created the 'SSA_NAME'. Only definitions and virtual definitions may
-create new 'SSA_NAME' nodes.
+ We represent variable versions using `SSA_NAME' nodes. The renaming
+process in `tree-ssa.c' wraps every real and virtual operand with an
+`SSA_NAME' node which contains the version number and the statement
+that created the `SSA_NAME'. Only definitions and virtual definitions
+may create new `SSA_NAME' nodes.
Sometimes, flow of control makes it impossible to determine the most
recent version of a variable. In these cases, the compiler inserts an
@@ -13425,19 +13565,19 @@ variable to create a new name for it. For instance,
return a_4;
Since it is not possible to determine which of the three branches will
-be taken at runtime, we don't know which of 'a_1', 'a_2' or 'a_3' to use
-at the return statement. So, the SSA renamer creates a new version
-'a_4' which is assigned the result of "merging" 'a_1', 'a_2' and 'a_3'.
+be taken at runtime, we don't know which of `a_1', `a_2' or `a_3' to
+use at the return statement. So, the SSA renamer creates a new version
+`a_4' which is assigned the result of "merging" `a_1', `a_2' and `a_3'.
Hence, PHI nodes mean "one of these operands. I don't know which".
The following functions can be used to examine PHI nodes
-- Function: gimple_phi_result (PHI)
- Returns the 'SSA_NAME' created by PHI node PHI (i.e., PHI's LHS).
+ Returns the `SSA_NAME' created by PHI node PHI (i.e., PHI's LHS).
-- Function: gimple_phi_num_args (PHI)
- Returns the number of arguments in PHI. This number is exactly the
- number of incoming edges to the basic block holding PHI.
+ Returns the number of arguments in PHI. This number is exactly
+ the number of incoming edges to the basic block holding PHI.
-- Function: gimple_phi_arg (PHI, I)
Returns Ith argument of PHI.
@@ -13446,7 +13586,7 @@ Hence, PHI nodes mean "one of these operands. I don't know which".
Returns the incoming edge for the Ith argument of PHI.
-- Function: gimple_phi_arg_def (PHI, I)
- Returns the 'SSA_NAME' for the Ith argument of PHI.
+ Returns the `SSA_NAME' for the Ith argument of PHI.
12.3.1 Preserving the SSA form
------------------------------
@@ -13463,8 +13603,8 @@ SSA form.
variables, keeping the SSA form up to date depends on whether you are
updating register or virtual names. In both cases, the general idea
behind incremental SSA updates is similar: when new SSA names are
-created, they typically are meant to replace other existing names in the
-program.
+created, they typically are meant to replace other existing names in
+the program.
For instance, given the following code:
@@ -13480,7 +13620,7 @@ program.
10 goto L0;
11 endif
- Suppose that we insert new names 'x_10' and 'x_11' (lines '4' and '8').
+ Suppose that we insert new names `x_10' and `x_11' (lines `4' and `8').
1 L0:
2 x_1 = PHI (0, x_5)
@@ -13496,65 +13636,65 @@ program.
12 goto L0;
13 endif
- We want to replace all the uses of 'x_1' with the new definitions of
-'x_10' and 'x_11'. Note that the only uses that should be replaced are
-those at lines '5', '9' and '11'. Also, the use of 'x_7' at line '9'
-should _not_ be replaced (this is why we cannot just mark symbol 'x' for
+ We want to replace all the uses of `x_1' with the new definitions of
+`x_10' and `x_11'. Note that the only uses that should be replaced are
+those at lines `5', `9' and `11'. Also, the use of `x_7' at line `9'
+should _not_ be replaced (this is why we cannot just mark symbol `x' for
renaming).
- Additionally, we may need to insert a PHI node at line '11' because
-that is a merge point for 'x_10' and 'x_11'. So the use of 'x_1' at
-line '11' will be replaced with the new PHI node. The insertion of PHI
+ Additionally, we may need to insert a PHI node at line `11' because
+that is a merge point for `x_10' and `x_11'. So the use of `x_1' at
+line `11' will be replaced with the new PHI node. The insertion of PHI
nodes is optional. They are not strictly necessary to preserve the SSA
form, and depending on what the caller inserted, they may not even be
useful for the optimizers.
Updating the SSA form is a two step process. First, the pass has to
identify which names need to be updated and/or which symbols need to be
-renamed into SSA form for the first time. When new names are introduced
-to replace existing names in the program, the mapping between the old
-and the new names are registered by calling 'register_new_name_mapping'
-(note that if your pass creates new code by duplicating basic blocks,
-the call to 'tree_duplicate_bb' will set up the necessary mappings
-automatically).
+renamed into SSA form for the first time. When new names are
+introduced to replace existing names in the program, the mapping
+between the old and the new names are registered by calling
+`register_new_name_mapping' (note that if your pass creates new code by
+duplicating basic blocks, the call to `tree_duplicate_bb' will set up
+the necessary mappings automatically).
After the replacement mappings have been registered and new symbols
-marked for renaming, a call to 'update_ssa' makes the registered
-changes. This can be done with an explicit call or by creating 'TODO'
-flags in the 'tree_opt_pass' structure for your pass. There are several
-'TODO' flags that control the behavior of 'update_ssa':
+marked for renaming, a call to `update_ssa' makes the registered
+changes. This can be done with an explicit call or by creating `TODO'
+flags in the `tree_opt_pass' structure for your pass. There are
+several `TODO' flags that control the behavior of `update_ssa':
- * 'TODO_update_ssa'. Update the SSA form inserting PHI nodes for
+ * `TODO_update_ssa'. Update the SSA form inserting PHI nodes for
newly exposed symbols and virtual names marked for updating. When
- updating real names, only insert PHI nodes for a real name 'O_j' in
- blocks reached by all the new and old definitions for 'O_j'. If
- the iterated dominance frontier for 'O_j' is not pruned, we may end
- up inserting PHI nodes in blocks that have one or more edges with
- no incoming definition for 'O_j'. This would lead to uninitialized
- warnings for 'O_j''s symbol.
-
- * 'TODO_update_ssa_no_phi'. Update the SSA form without inserting
+ updating real names, only insert PHI nodes for a real name `O_j'
+ in blocks reached by all the new and old definitions for `O_j'.
+ If the iterated dominance frontier for `O_j' is not pruned, we may
+ end up inserting PHI nodes in blocks that have one or more edges
+ with no incoming definition for `O_j'. This would lead to
+ uninitialized warnings for `O_j''s symbol.
+
+ * `TODO_update_ssa_no_phi'. Update the SSA form without inserting
any new PHI nodes at all. This is used by passes that have either
inserted all the PHI nodes themselves or passes that need only to
patch use-def and def-def chains for virtuals (e.g., DCE).
- * 'TODO_update_ssa_full_phi'. Insert PHI nodes everywhere they are
+ * `TODO_update_ssa_full_phi'. Insert PHI nodes everywhere they are
needed. No pruning of the IDF is done. This is used by passes
- that need the PHI nodes for 'O_j' even if it means that some
- arguments will come from the default definition of 'O_j''s symbol
- (e.g., 'pass_linear_transform').
+ that need the PHI nodes for `O_j' even if it means that some
+ arguments will come from the default definition of `O_j''s symbol
+ (e.g., `pass_linear_transform').
WARNING: If you need to use this flag, chances are that your pass
may be doing something wrong. Inserting PHI nodes for an old name
where not all edges carry a new replacement may lead to silent
codegen errors or spurious uninitialized warnings.
- * 'TODO_update_ssa_only_virtuals'. Passes that update the SSA form
+ * `TODO_update_ssa_only_virtuals'. Passes that update the SSA form
on their own may want to delegate the updating of virtual names to
- the generic updater. Since FUD chains are easier to maintain, this
- simplifies the work they need to do. NOTE: If this flag is used,
- any OLD->NEW mappings for real names are explicitly destroyed and
- only the symbols marked for renaming are processed.
+ the generic updater. Since FUD chains are easier to maintain,
+ this simplifies the work they need to do. NOTE: If this flag is
+ used, any OLD->NEW mappings for real names are explicitly
+ destroyed and only the symbols marked for renaming are processed.
12.3.2 Preserving the virtual SSA form
--------------------------------------
@@ -13562,8 +13702,8 @@ flags in the 'tree_opt_pass' structure for your pass. There are several
The virtual SSA form is harder to preserve than the non-virtual SSA form
mainly because the set of virtual operands for a statement may change at
what some would consider unexpected times. In general, statement
-modifications should be bracketed between calls to 'push_stmt_changes'
-and 'pop_stmt_changes'. For example,
+modifications should be bracketed between calls to `push_stmt_changes'
+and `pop_stmt_changes'. For example,
munge_stmt (tree stmt)
{
@@ -13572,43 +13712,42 @@ and 'pop_stmt_changes'. For example,
pop_stmt_changes (&stmt);
}
- The call to 'push_stmt_changes' saves the current state of the
-statement operands and the call to 'pop_stmt_changes' compares the saved
-state with the current one and does the appropriate symbol marking for
-the SSA renamer.
+ The call to `push_stmt_changes' saves the current state of the
+statement operands and the call to `pop_stmt_changes' compares the
+saved state with the current one and does the appropriate symbol
+marking for the SSA renamer.
It is possible to modify several statements at a time, provided that
-'push_stmt_changes' and 'pop_stmt_changes' are called in LIFO order, as
+`push_stmt_changes' and `pop_stmt_changes' are called in LIFO order, as
when processing a stack of statements.
Additionally, if the pass discovers that it did not need to make
-changes to the statement after calling 'push_stmt_changes', it can
+changes to the statement after calling `push_stmt_changes', it can
simply discard the topmost change buffer by calling
-'discard_stmt_changes'. This will avoid the expensive operand re-scan
+`discard_stmt_changes'. This will avoid the expensive operand re-scan
operation and the buffer comparison that determines if symbols need to
be marked for renaming.
-12.3.3 Examining 'SSA_NAME' nodes
+12.3.3 Examining `SSA_NAME' nodes
---------------------------------
-The following macros can be used to examine 'SSA_NAME' nodes
+The following macros can be used to examine `SSA_NAME' nodes
-- Macro: SSA_NAME_DEF_STMT (VAR)
- Returns the statement S that creates the 'SSA_NAME' VAR. If S is
- an empty statement (i.e., 'IS_EMPTY_STMT (S)' returns 'true'), it
+ Returns the statement S that creates the `SSA_NAME' VAR. If S is
+ an empty statement (i.e., `IS_EMPTY_STMT (S)' returns `true'), it
means that the first reference to this variable is a USE or a VUSE.
-- Macro: SSA_NAME_VERSION (VAR)
- Returns the version number of the 'SSA_NAME' object VAR.
+ Returns the version number of the `SSA_NAME' object VAR.
12.3.4 Walking the dominator tree
---------------------------------
-- Tree SSA function: void walk_dominator_tree (WALK_DATA, BB)
-
This function walks the dominator tree for the current CFG calling
a set of callback functions defined in STRUCT DOM_WALK_DATA in
- 'domwalk.h'. The call back functions you need to define give you
+ `domwalk.h'. The call back functions you need to define give you
hooks to execute custom code at various points during traversal:
1. Once to initialize any local data needed while processing BB
@@ -13647,9 +13786,9 @@ disambiguate explicit and implicit memory references.
1. Memory SSA form.
- All statements that may use memory have exactly one accompanied use
- of a virtual SSA name that represents the state of memory at the
- given point in the IL.
+ All statements that may use memory have exactly one accompanied
+ use of a virtual SSA name that represents the state of memory at
+ the given point in the IL.
All statements that may define memory have exactly one accompanied
definition of a virtual SSA name using the previous state of memory
@@ -13665,9 +13804,9 @@ disambiguate explicit and implicit memory references.
return i;
}
- The virtual SSA names in this case are '.MEM_2(D)' and '.MEM_3'.
- The store to the global variable 'i' defines '.MEM_3' invalidating
- '.MEM_2(D)'. The load from 'i' uses that new state '.MEM_3'.
+ The virtual SSA names in this case are `.MEM_2(D)' and `.MEM_3'.
+ The store to the global variable `i' defines `.MEM_3' invalidating
+ `.MEM_2(D)'. The load from `i' uses that new state `.MEM_3'.
The virtual SSA web serves as constraints to SSA optimizers
preventing illegitimate code-motion and optimization. It also
@@ -13683,28 +13822,29 @@ disambiguate explicit and implicit memory references.
what it may possibly point to.
This points-to solution for a given SSA name pointer is stored in
- the 'pt_solution' sub-structure of the 'SSA_NAME_PTR_INFO' record.
+ the `pt_solution' sub-structure of the `SSA_NAME_PTR_INFO' record.
The following accessor functions are available:
- * 'pt_solution_includes'
- * 'pt_solutions_intersect'
+ * `pt_solution_includes'
+
+ * `pt_solutions_intersect'
Points-to analysis also computes the solution for two special set
- of pointers, 'ESCAPED' and 'CALLUSED'. Those represent all memory
+ of pointers, `ESCAPED' and `CALLUSED'. Those represent all memory
that has escaped the scope of analysis or that is used by pure or
nested const calls.
3. Type-based alias analysis
Type-based alias analysis is frontend dependent though generic
- support is provided by the middle-end in 'alias.c'. TBAA code is
+ support is provided by the middle-end in `alias.c'. TBAA code is
used by both tree optimizers and RTL optimizers.
Every language that wishes to perform language-specific alias
- analysis should define a function that computes, given a 'tree'
- node, an alias set for the node. Nodes in different alias sets are
- not allowed to alias. For an example, see the C front-end function
- 'c_get_alias_set'.
+ analysis should define a function that computes, given a `tree'
+ node, an alias set for the node. Nodes in different alias sets
+ are not allowed to alias. For an example, see the C front-end
+ function `c_get_alias_set'.
4. Tree alias-oracle
@@ -13712,20 +13852,23 @@ disambiguate explicit and implicit memory references.
references and memory references against statements. The following
queries are available:
- * 'refs_may_alias_p'
- * 'ref_maybe_used_by_stmt_p'
- * 'stmt_may_clobber_ref_p'
+ * `refs_may_alias_p'
+
+ * `ref_maybe_used_by_stmt_p'
+
+ * `stmt_may_clobber_ref_p'
In addition to those two kind of statement walkers are available
walking statements related to a reference ref.
- 'walk_non_aliased_vuses' walks over dominating memory defining
+ `walk_non_aliased_vuses' walks over dominating memory defining
statements and calls back if the statement does not clobber ref
- providing the non-aliased VUSE. The walk stops at the first
- clobbering statement or if asked to. 'walk_aliased_vdefs' walks
+ providing the non-aliased VUSE. The walk stops at the first
+ clobbering statement or if asked to. `walk_aliased_vdefs' walks
over dominating memory defining statements and calls back on each
- statement clobbering ref providing its aliasing VDEF. The walk
+ statement clobbering ref providing its aliasing VDEF. The walk
stops if asked to.
+

File: gccint.info, Node: Memory model, Prev: Alias analysis, Up: Tree SSA
@@ -13746,7 +13889,7 @@ effective type to objects with a declared type as required for C++.
an lvalue having a type that is not a character type, then the
type of the lvalue becomes the effective type of the object for that
access and for subsequent accesses that do not modify the stored value.
- If a value is copied into an object using memcpy or memmove,
+ If a value is copied into an object using `memcpy' or `memmove',
or is copied as an array of character type, then the effective type
of the modified object for that access and for subsequent accesses that
do not modify the value is undetermined. For all other accesses to an
@@ -13765,8 +13908,8 @@ instructions to be output are described, pretty much one by one, in an
algebraic form that describes what the instruction does.
RTL is inspired by Lisp lists. It has both an internal form, made up
-of structures that point at other structures, and a textual form that is
-used in the machine description and in printed debugging dumps. The
+of structures that point at other structures, and a textual form that
+is used in the machine description and in printed debugging dumps. The
textual form uses nested parentheses to indicate the pointers in the
internal form.
@@ -13788,7 +13931,7 @@ internal form.
* RTL Declarations:: Declaring volatility, constancy, etc.
* Side Effects:: Expressions for storing in registers, etc.
* Incdec:: Embedded side-effects for autoincrement addressing.
-* Assembler:: Representing 'asm' with operands.
+* Assembler:: Representing `asm' with operands.
* Debug Information:: Expressions representing debugging information.
* Insns:: Expression types for entire insns.
* Calls:: RTL representation of function call insns.
@@ -13804,20 +13947,20 @@ File: gccint.info, Node: RTL Objects, Next: RTL Classes, Up: RTL
RTL uses five kinds of objects: expressions, integers, wide integers,
strings and vectors. Expressions are the most important ones. An RTL
expression ("RTX", for short) is a C structure, but it is usually
-referred to with a pointer; a type that is given the typedef name 'rtx'.
+referred to with a pointer; a type that is given the typedef name `rtx'.
- An integer is simply an 'int'; their written form uses decimal digits.
-A wide integer is an integral object whose type is 'HOST_WIDE_INT';
+ An integer is simply an `int'; their written form uses decimal digits.
+A wide integer is an integral object whose type is `HOST_WIDE_INT';
their written form uses decimal digits.
A string is a sequence of characters. In core it is represented as a
-'char *' in usual C fashion, and it is written in C syntax as well.
-However, strings in RTL may never be null. If you write an empty string
-in a machine description, it is represented in core as a null pointer
-rather than as a pointer to a null character. In certain contexts,
-these null pointers instead of strings are valid. Within RTL code,
-strings are most commonly found inside 'symbol_ref' expressions, but
-they appear in other contexts in the RTL expressions that make up
+`char *' in usual C fashion, and it is written in C syntax as well.
+However, strings in RTL may never be null. If you write an empty
+string in a machine description, it is represented in core as a null
+pointer rather than as a pointer to a null character. In certain
+contexts, these null pointers instead of strings are valid. Within RTL
+code, strings are most commonly found inside `symbol_ref' expressions,
+but they appear in other contexts in the RTL expressions that make up
machine descriptions.
In a machine description, strings are normally written with double
@@ -13837,39 +13980,39 @@ need not escape each quote character with a backslash.
A vector contains an arbitrary number of pointers to expressions. The
number of elements in the vector is explicitly present in the vector.
-The written form of a vector consists of square brackets ('[...]')
+The written form of a vector consists of square brackets (`[...]')
surrounding the elements, in sequence and with whitespace separating
them. Vectors of length zero are not created; null pointers are used
instead.
Expressions are classified by "expression codes" (also called RTX
-codes). The expression code is a name defined in 'rtl.def', which is
+codes). The expression code is a name defined in `rtl.def', which is
also (in uppercase) a C enumeration constant. The possible expression
codes and their meanings are machine-independent. The code of an RTX
-can be extracted with the macro 'GET_CODE (X)' and altered with
-'PUT_CODE (X, NEWCODE)'.
+can be extracted with the macro `GET_CODE (X)' and altered with
+`PUT_CODE (X, NEWCODE)'.
The expression code determines how many operands the expression
contains, and what kinds of objects they are. In RTL, unlike Lisp, you
cannot tell by looking at an operand what kind of object it is.
-Instead, you must know from its context--from the expression code of the
-containing expression. For example, in an expression of code 'subreg',
-the first operand is to be regarded as an expression and the second
-operand as an integer. In an expression of code 'plus', there are two
-operands, both of which are to be regarded as expressions. In a
-'symbol_ref' expression, there is one operand, which is to be regarded
-as a string.
+Instead, you must know from its context--from the expression code of
+the containing expression. For example, in an expression of code
+`subreg', the first operand is to be regarded as an expression and the
+second operand as an integer. In an expression of code `plus', there
+are two operands, both of which are to be regarded as expressions. In
+a `symbol_ref' expression, there is one operand, which is to be
+regarded as a string.
Expressions are written as parentheses containing the name of the
expression type, its flags and machine mode if any, and then the
operands of the expression (separated by spaces).
- Expression code names in the 'md' file are written in lowercase, but
+ Expression code names in the `md' file are written in lowercase, but
when they appear in C code they are written in uppercase. In this
-manual, they are shown as follows: 'const_int'.
+manual, they are shown as follows: `const_int'.
In a few contexts a null pointer is valid where an expression is
-normally wanted. The written form of this is '(nil)'.
+normally wanted. The written form of this is `(nil)'.

File: gccint.info, Node: RTL Classes, Next: Accessors, Prev: RTL Objects, Up: RTL
@@ -13878,156 +14021,156 @@ File: gccint.info, Node: RTL Classes, Next: Accessors, Prev: RTL Objects, Up
============================
The various expression codes are divided into several "classes", which
-are represented by single characters. You can determine the class of an
-RTX code with the macro 'GET_RTX_CLASS (CODE)'. Currently, 'rtl.def'
-defines these classes:
+are represented by single characters. You can determine the class of
+an RTX code with the macro `GET_RTX_CLASS (CODE)'. Currently,
+`rtl.def' defines these classes:
-'RTX_OBJ'
+`RTX_OBJ'
An RTX code that represents an actual object, such as a register
- ('REG') or a memory location ('MEM', 'SYMBOL_REF'). 'LO_SUM') is
- also included; instead, 'SUBREG' and 'STRICT_LOW_PART' are not in
- this class, but in class 'x'.
+ (`REG') or a memory location (`MEM', `SYMBOL_REF'). `LO_SUM') is
+ also included; instead, `SUBREG' and `STRICT_LOW_PART' are not in
+ this class, but in class `x'.
-'RTX_CONST_OBJ'
- An RTX code that represents a constant object. 'HIGH' is also
+`RTX_CONST_OBJ'
+ An RTX code that represents a constant object. `HIGH' is also
included in this class.
-'RTX_COMPARE'
- An RTX code for a non-symmetric comparison, such as 'GEU' or 'LT'.
+`RTX_COMPARE'
+ An RTX code for a non-symmetric comparison, such as `GEU' or `LT'.
-'RTX_COMM_COMPARE'
- An RTX code for a symmetric (commutative) comparison, such as 'EQ'
- or 'ORDERED'.
+`RTX_COMM_COMPARE'
+ An RTX code for a symmetric (commutative) comparison, such as `EQ'
+ or `ORDERED'.
-'RTX_UNARY'
- An RTX code for a unary arithmetic operation, such as 'NEG', 'NOT',
- or 'ABS'. This category also includes value extension (sign or
- zero) and conversions between integer and floating point.
+`RTX_UNARY'
+ An RTX code for a unary arithmetic operation, such as `NEG',
+ `NOT', or `ABS'. This category also includes value extension
+ (sign or zero) and conversions between integer and floating point.
-'RTX_COMM_ARITH'
- An RTX code for a commutative binary operation, such as 'PLUS' or
- 'AND'. 'NE' and 'EQ' are comparisons, so they have class '<'.
+`RTX_COMM_ARITH'
+ An RTX code for a commutative binary operation, such as `PLUS' or
+ `AND'. `NE' and `EQ' are comparisons, so they have class `<'.
-'RTX_BIN_ARITH'
+`RTX_BIN_ARITH'
An RTX code for a non-commutative binary operation, such as
- 'MINUS', 'DIV', or 'ASHIFTRT'.
+ `MINUS', `DIV', or `ASHIFTRT'.
-'RTX_BITFIELD_OPS'
+`RTX_BITFIELD_OPS'
An RTX code for a bit-field operation. Currently only
- 'ZERO_EXTRACT' and 'SIGN_EXTRACT'. These have three inputs and are
- lvalues (so they can be used for insertion as well). *Note
+ `ZERO_EXTRACT' and `SIGN_EXTRACT'. These have three inputs and
+ are lvalues (so they can be used for insertion as well). *Note
Bit-Fields::.
-'RTX_TERNARY'
+`RTX_TERNARY'
An RTX code for other three input operations. Currently only
- 'IF_THEN_ELSE', 'VEC_MERGE', 'SIGN_EXTRACT', 'ZERO_EXTRACT', and
- 'FMA'.
+ `IF_THEN_ELSE', `VEC_MERGE', `SIGN_EXTRACT', `ZERO_EXTRACT', and
+ `FMA'.
-'RTX_INSN'
- An RTX code for an entire instruction: 'INSN', 'JUMP_INSN', and
- 'CALL_INSN'. *Note Insns::.
+`RTX_INSN'
+ An RTX code for an entire instruction: `INSN', `JUMP_INSN', and
+ `CALL_INSN'. *Note Insns::.
-'RTX_MATCH'
+`RTX_MATCH'
An RTX code for something that matches in insns, such as
- 'MATCH_DUP'. These only occur in machine descriptions.
+ `MATCH_DUP'. These only occur in machine descriptions.
-'RTX_AUTOINC'
+`RTX_AUTOINC'
An RTX code for an auto-increment addressing mode, such as
- 'POST_INC'. 'XEXP (X, 0)' gives the auto-modified register.
+ `POST_INC'. `XEXP (X, 0)' gives the auto-modified register.
-'RTX_EXTRA'
+`RTX_EXTRA'
All other RTX codes. This category includes the remaining codes
- used only in machine descriptions ('DEFINE_*', etc.). It also
- includes all the codes describing side effects ('SET', 'USE',
- 'CLOBBER', etc.) and the non-insns that may appear on an insn
- chain, such as 'NOTE', 'BARRIER', and 'CODE_LABEL'. 'SUBREG' is
+ used only in machine descriptions (`DEFINE_*', etc.). It also
+ includes all the codes describing side effects (`SET', `USE',
+ `CLOBBER', etc.) and the non-insns that may appear on an insn
+ chain, such as `NOTE', `BARRIER', and `CODE_LABEL'. `SUBREG' is
also part of this class.
- For each expression code, 'rtl.def' specifies the number of contained
+ For each expression code, `rtl.def' specifies the number of contained
objects and their kinds using a sequence of characters called the
-"format" of the expression code. For example, the format of 'subreg' is
-'ei'.
+"format" of the expression code. For example, the format of `subreg'
+is `ei'.
These are the most commonly used format characters:
-'e'
+`e'
An expression (actually a pointer to an expression).
-'i'
+`i'
An integer.
-'w'
+`w'
A wide integer.
-'s'
+`s'
A string.
-'E'
+`E'
A vector of expressions.
A few other format characters are used occasionally:
-'u'
- 'u' is equivalent to 'e' except that it is printed differently in
+`u'
+ `u' is equivalent to `e' except that it is printed differently in
debugging dumps. It is used for pointers to insns.
-'n'
- 'n' is equivalent to 'i' except that it is printed differently in
+`n'
+ `n' is equivalent to `i' except that it is printed differently in
debugging dumps. It is used for the line number or code number of
- a 'note' insn.
+ a `note' insn.
-'S'
- 'S' indicates a string which is optional. In the RTL objects in
- core, 'S' is equivalent to 's', but when the object is read, from
- an 'md' file, the string value of this operand may be omitted. An
+`S'
+ `S' indicates a string which is optional. In the RTL objects in
+ core, `S' is equivalent to `s', but when the object is read, from
+ an `md' file, the string value of this operand may be omitted. An
omitted string is taken to be the null string.
-'V'
- 'V' indicates a vector which is optional. In the RTL objects in
- core, 'V' is equivalent to 'E', but when the object is read from an
- 'md' file, the vector value of this operand may be omitted. An
+`V'
+ `V' indicates a vector which is optional. In the RTL objects in
+ core, `V' is equivalent to `E', but when the object is read from
+ an `md' file, the vector value of this operand may be omitted. An
omitted vector is effectively the same as a vector of no elements.
-'B'
- 'B' indicates a pointer to basic block structure.
+`B'
+ `B' indicates a pointer to basic block structure.
-'0'
- '0' means a slot whose contents do not fit any normal category.
- '0' slots are not printed at all in dumps, and are often used in
+`0'
+ `0' means a slot whose contents do not fit any normal category.
+ `0' slots are not printed at all in dumps, and are often used in
special ways by small parts of the compiler.
There are macros to get the number of operands and the format of an
expression code:
-'GET_RTX_LENGTH (CODE)'
+`GET_RTX_LENGTH (CODE)'
Number of operands of an RTX of code CODE.
-'GET_RTX_FORMAT (CODE)'
+`GET_RTX_FORMAT (CODE)'
The format of an RTX of code CODE, as a C string.
Some classes of RTX codes always have the same format. For example, it
-is safe to assume that all comparison operations have format 'ee'.
+is safe to assume that all comparison operations have format `ee'.
-'1'
- All codes of this class have format 'e'.
+`1'
+ All codes of this class have format `e'.
-'<'
-'c'
-'2'
- All codes of these classes have format 'ee'.
+`<'
+`c'
+`2'
+ All codes of these classes have format `ee'.
-'b'
-'3'
- All codes of these classes have format 'eee'.
+`b'
+`3'
+ All codes of these classes have format `eee'.
-'i'
- All codes of this class have formats that begin with 'iuueiee'.
+`i'
+ All codes of this class have formats that begin with `iuueiee'.
*Note Insns::. Note that not all RTL objects linked onto an insn
- chain are of class 'i'.
+ chain are of class `i'.
-'o'
-'m'
-'x'
+`o'
+`m'
+`x'
You can make no assumptions about the format of these codes.

@@ -14036,8 +14179,8 @@ File: gccint.info, Node: Accessors, Next: Special Accessors, Prev: RTL Classe
13.3 Access to Operands
=======================
-Operands of expressions are accessed using the macros 'XEXP', 'XINT',
-'XWINT' and 'XSTR'. Each of these macros takes two arguments: an
+Operands of expressions are accessed using the macros `XEXP', `XINT',
+`XWINT' and `XSTR'. Each of these macros takes two arguments: an
expression-pointer (RTX) and an operand number (counting from zero).
Thus,
@@ -14047,7 +14190,7 @@ accesses operand 2 of expression X, as an expression.
XINT (X, 2)
-accesses the same operand as an integer. 'XSTR', used in the same
+accesses the same operand as an integer. `XSTR', used in the same
fashion, would access it as a string.
Any operand can be accessed as an integer, as an expression or as a
@@ -14056,34 +14199,34 @@ value actually stored in the operand. You would do this based on the
expression code of the containing expression. That is also how you
would know how many operands there are.
- For example, if X is a 'subreg' expression, you know that it has two
-operands which can be correctly accessed as 'XEXP (X, 0)' and 'XINT (X,
-1)'. If you did 'XINT (X, 0)', you would get the address of the
+ For example, if X is a `subreg' expression, you know that it has two
+operands which can be correctly accessed as `XEXP (X, 0)' and `XINT (X,
+1)'. If you did `XINT (X, 0)', you would get the address of the
expression operand but cast as an integer; that might occasionally be
-useful, but it would be cleaner to write '(int) XEXP (X, 0)'. 'XEXP (X,
-1)' would also compile without error, and would return the second,
+useful, but it would be cleaner to write `(int) XEXP (X, 0)'. `XEXP
+(X, 1)' would also compile without error, and would return the second,
integer operand cast as an expression pointer, which would probably
-result in a crash when accessed. Nothing stops you from writing 'XEXP
+result in a crash when accessed. Nothing stops you from writing `XEXP
(X, 28)' either, but this will access memory past the end of the
expression with unpredictable results.
Access to operands which are vectors is more complicated. You can use
-the macro 'XVEC' to get the vector-pointer itself, or the macros
-'XVECEXP' and 'XVECLEN' to access the elements and length of a vector.
+the macro `XVEC' to get the vector-pointer itself, or the macros
+`XVECEXP' and `XVECLEN' to access the elements and length of a vector.
-'XVEC (EXP, IDX)'
+`XVEC (EXP, IDX)'
Access the vector-pointer which is operand number IDX in EXP.
-'XVECLEN (EXP, IDX)'
+`XVECLEN (EXP, IDX)'
Access the length (number of elements) in the vector which is in
- operand number IDX in EXP. This value is an 'int'.
+ operand number IDX in EXP. This value is an `int'.
-'XVECEXP (EXP, IDX, ELTNUM)'
+`XVECEXP (EXP, IDX, ELTNUM)'
Access element number ELTNUM in the vector which is in operand
number IDX in EXP. This value is an RTX.
It is up to you to make sure that ELTNUM is not negative and is
- less than 'XVECLEN (EXP, IDX)'.
+ less than `XVECLEN (EXP, IDX)'.
All the macros defined in this section expand into lvalues and
therefore can be used to assign the operands, lengths and vector
@@ -14097,138 +14240,141 @@ File: gccint.info, Node: Special Accessors, Next: Flags, Prev: Accessors, Up
Some RTL nodes have special annotations associated with them.
-'MEM'
- 'MEM_ALIAS_SET (X)'
+`MEM'
+
+ `MEM_ALIAS_SET (X)'
If 0, X is not in any alias set, and may alias anything.
- Otherwise, X can only alias 'MEM's in a conflicting alias set.
- This value is set in a language-dependent manner in the
- front-end, and should not be altered in the back-end. In some
- front-ends, these numbers may correspond in some way to types,
- or other language-level entities, but they need not, and the
- back-end makes no such assumptions. These set numbers are
- tested with 'alias_sets_conflict_p'.
-
- 'MEM_EXPR (X)'
+ Otherwise, X can only alias `MEM's in a conflicting alias
+ set. This value is set in a language-dependent manner in the
+ front-end, and should not be altered in the back-end. In
+ some front-ends, these numbers may correspond in some way to
+ types, or other language-level entities, but they need not,
+ and the back-end makes no such assumptions. These set
+ numbers are tested with `alias_sets_conflict_p'.
+
+ `MEM_EXPR (X)'
If this register is known to hold the value of some user-level
declaration, this is that tree node. It may also be a
- 'COMPONENT_REF', in which case this is some field reference,
- and 'TREE_OPERAND (X, 0)' contains the declaration, or another
- 'COMPONENT_REF', or null if there is no compile-time object
- associated with the reference.
+ `COMPONENT_REF', in which case this is some field reference,
+ and `TREE_OPERAND (X, 0)' contains the declaration, or
+ another `COMPONENT_REF', or null if there is no compile-time
+ object associated with the reference.
- 'MEM_OFFSET_KNOWN_P (X)'
- True if the offset of the memory reference from 'MEM_EXPR' is
- known. 'MEM_OFFSET (X)' provides the offset if so.
+ `MEM_OFFSET_KNOWN_P (X)'
+ True if the offset of the memory reference from `MEM_EXPR' is
+ known. `MEM_OFFSET (X)' provides the offset if so.
- 'MEM_OFFSET (X)'
- The offset from the start of 'MEM_EXPR'. The value is only
- valid if 'MEM_OFFSET_KNOWN_P (X)' is true.
+ `MEM_OFFSET (X)'
+ The offset from the start of `MEM_EXPR'. The value is only
+ valid if `MEM_OFFSET_KNOWN_P (X)' is true.
- 'MEM_SIZE_KNOWN_P (X)'
- True if the size of the memory reference is known. 'MEM_SIZE
+ `MEM_SIZE_KNOWN_P (X)'
+ True if the size of the memory reference is known. `MEM_SIZE
(X)' provides its size if so.
- 'MEM_SIZE (X)'
+ `MEM_SIZE (X)'
The size in bytes of the memory reference. This is mostly
- relevant for 'BLKmode' references as otherwise the size is
+ relevant for `BLKmode' references as otherwise the size is
implied by the mode. The value is only valid if
- 'MEM_SIZE_KNOWN_P (X)' is true.
+ `MEM_SIZE_KNOWN_P (X)' is true.
- 'MEM_ALIGN (X)'
+ `MEM_ALIGN (X)'
The known alignment in bits of the memory reference.
- 'MEM_ADDR_SPACE (X)'
- The address space of the memory reference. This will commonly
- be zero for the generic address space.
+ `MEM_ADDR_SPACE (X)'
+ The address space of the memory reference. This will
+ commonly be zero for the generic address space.
+
+`REG'
-'REG'
- 'ORIGINAL_REGNO (X)'
- This field holds the number the register "originally" had; for
- a pseudo register turned into a hard reg this will hold the
- old pseudo register number.
+ `ORIGINAL_REGNO (X)'
+ This field holds the number the register "originally" had;
+ for a pseudo register turned into a hard reg this will hold
+ the old pseudo register number.
- 'REG_EXPR (X)'
+ `REG_EXPR (X)'
If this register is known to hold the value of some user-level
declaration, this is that tree node.
- 'REG_OFFSET (X)'
+ `REG_OFFSET (X)'
If this register is known to hold the value of some user-level
declaration, this is the offset into that logical storage.
-'SYMBOL_REF'
- 'SYMBOL_REF_DECL (X)'
- If the 'symbol_ref' X was created for a 'VAR_DECL' or a
- 'FUNCTION_DECL', that tree is recorded here. If this value is
+`SYMBOL_REF'
+
+ `SYMBOL_REF_DECL (X)'
+ If the `symbol_ref' X was created for a `VAR_DECL' or a
+ `FUNCTION_DECL', that tree is recorded here. If this value is
null, then X was created by back end code generation routines,
and there is no associated front end symbol table entry.
- 'SYMBOL_REF_DECL' may also point to a tree of class ''c'',
+ `SYMBOL_REF_DECL' may also point to a tree of class `'c'',
that is, some sort of constant. In this case, the
- 'symbol_ref' is an entry in the per-file constant pool; again,
- there is no associated front end symbol table entry.
+ `symbol_ref' is an entry in the per-file constant pool;
+ again, there is no associated front end symbol table entry.
- 'SYMBOL_REF_CONSTANT (X)'
- If 'CONSTANT_POOL_ADDRESS_P (X)' is true, this is the constant
+ `SYMBOL_REF_CONSTANT (X)'
+ If `CONSTANT_POOL_ADDRESS_P (X)' is true, this is the constant
pool entry for X. It is null otherwise.
- 'SYMBOL_REF_DATA (X)'
- A field of opaque type used to store 'SYMBOL_REF_DECL' or
- 'SYMBOL_REF_CONSTANT'.
+ `SYMBOL_REF_DATA (X)'
+ A field of opaque type used to store `SYMBOL_REF_DECL' or
+ `SYMBOL_REF_CONSTANT'.
- 'SYMBOL_REF_FLAGS (X)'
- In a 'symbol_ref', this is used to communicate various
+ `SYMBOL_REF_FLAGS (X)'
+ In a `symbol_ref', this is used to communicate various
predicates about the symbol. Some of these are common enough
to be computed by common code, some are specific to the
target. The common bits are:
- 'SYMBOL_FLAG_FUNCTION'
+ `SYMBOL_FLAG_FUNCTION'
Set if the symbol refers to a function.
- 'SYMBOL_FLAG_LOCAL'
+ `SYMBOL_FLAG_LOCAL'
Set if the symbol is local to this "module". See
- 'TARGET_BINDS_LOCAL_P'.
+ `TARGET_BINDS_LOCAL_P'.
- 'SYMBOL_FLAG_EXTERNAL'
+ `SYMBOL_FLAG_EXTERNAL'
Set if this symbol is not defined in this translation
unit. Note that this is not the inverse of
- 'SYMBOL_FLAG_LOCAL'.
+ `SYMBOL_FLAG_LOCAL'.
- 'SYMBOL_FLAG_SMALL'
+ `SYMBOL_FLAG_SMALL'
Set if the symbol is located in the small data section.
- See 'TARGET_IN_SMALL_DATA_P'.
+ See `TARGET_IN_SMALL_DATA_P'.
- 'SYMBOL_REF_TLS_MODEL (X)'
+ `SYMBOL_REF_TLS_MODEL (X)'
This is a multi-bit field accessor that returns the
- 'tls_model' to be used for a thread-local storage symbol.
- It returns zero for non-thread-local symbols.
+ `tls_model' to be used for a thread-local storage
+ symbol. It returns zero for non-thread-local symbols.
- 'SYMBOL_FLAG_HAS_BLOCK_INFO'
- Set if the symbol has 'SYMBOL_REF_BLOCK' and
- 'SYMBOL_REF_BLOCK_OFFSET' fields.
+ `SYMBOL_FLAG_HAS_BLOCK_INFO'
+ Set if the symbol has `SYMBOL_REF_BLOCK' and
+ `SYMBOL_REF_BLOCK_OFFSET' fields.
- 'SYMBOL_FLAG_ANCHOR'
+ `SYMBOL_FLAG_ANCHOR'
Set if the symbol is used as a section anchor. "Section
- anchors" are symbols that have a known position within an
- 'object_block' and that can be used to access nearby
+ anchors" are symbols that have a known position within
+ an `object_block' and that can be used to access nearby
members of that block. They are used to implement
- '-fsection-anchors'.
+ `-fsection-anchors'.
- If this flag is set, then 'SYMBOL_FLAG_HAS_BLOCK_INFO'
+ If this flag is set, then `SYMBOL_FLAG_HAS_BLOCK_INFO'
will be too.
- Bits beginning with 'SYMBOL_FLAG_MACH_DEP' are available for
+ Bits beginning with `SYMBOL_FLAG_MACH_DEP' are available for
the target's use.
-'SYMBOL_REF_BLOCK (X)'
- If 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the 'object_block'
- structure to which the symbol belongs, or 'NULL' if it has not been
- assigned a block.
+`SYMBOL_REF_BLOCK (X)'
+ If `SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the `object_block'
+ structure to which the symbol belongs, or `NULL' if it has not
+ been assigned a block.
-'SYMBOL_REF_BLOCK_OFFSET (X)'
- If 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the offset of X from
- the first object in 'SYMBOL_REF_BLOCK (X)'. The value is negative
- if X has not yet been assigned to a block, or it has not been given
- an offset within that block.
+`SYMBOL_REF_BLOCK_OFFSET (X)'
+ If `SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the offset of X from
+ the first object in `SYMBOL_REF_BLOCK (X)'. The value is negative
+ if X has not yet been assigned to a block, or it has not been
+ given an offset within that block.

File: gccint.info, Node: Flags, Next: Machine Modes, Prev: Special Accessors, Up: RTL
@@ -14236,114 +14382,114 @@ File: gccint.info, Node: Flags, Next: Machine Modes, Prev: Special Accessors,
13.5 Flags in an RTL Expression
===============================
-RTL expressions contain several flags (one-bit bit-fields) that are used
-in certain types of expression. Most often they are accessed with the
-following macros, which expand into lvalues.
+RTL expressions contain several flags (one-bit bit-fields) that are
+used in certain types of expression. Most often they are accessed with
+the following macros, which expand into lvalues.
-'CONSTANT_POOL_ADDRESS_P (X)'
- Nonzero in a 'symbol_ref' if it refers to part of the current
+`CONSTANT_POOL_ADDRESS_P (X)'
+ Nonzero in a `symbol_ref' if it refers to part of the current
function's constant pool. For most targets these addresses are in
- a '.rodata' section entirely separate from the function, but for
+ a `.rodata' section entirely separate from the function, but for
some targets the addresses are close to the beginning of the
function. In either case GCC assumes these addresses can be
addressed directly, perhaps with the help of base registers.
- Stored in the 'unchanging' field and printed as '/u'.
+ Stored in the `unchanging' field and printed as `/u'.
-'RTL_CONST_CALL_P (X)'
- In a 'call_insn' indicates that the insn represents a call to a
- const function. Stored in the 'unchanging' field and printed as
- '/u'.
+`RTL_CONST_CALL_P (X)'
+ In a `call_insn' indicates that the insn represents a call to a
+ const function. Stored in the `unchanging' field and printed as
+ `/u'.
-'RTL_PURE_CALL_P (X)'
- In a 'call_insn' indicates that the insn represents a call to a
- pure function. Stored in the 'return_val' field and printed as
- '/i'.
+`RTL_PURE_CALL_P (X)'
+ In a `call_insn' indicates that the insn represents a call to a
+ pure function. Stored in the `return_val' field and printed as
+ `/i'.
-'RTL_CONST_OR_PURE_CALL_P (X)'
- In a 'call_insn', true if 'RTL_CONST_CALL_P' or 'RTL_PURE_CALL_P'
+`RTL_CONST_OR_PURE_CALL_P (X)'
+ In a `call_insn', true if `RTL_CONST_CALL_P' or `RTL_PURE_CALL_P'
is true.
-'RTL_LOOPING_CONST_OR_PURE_CALL_P (X)'
- In a 'call_insn' indicates that the insn represents a possibly
+`RTL_LOOPING_CONST_OR_PURE_CALL_P (X)'
+ In a `call_insn' indicates that the insn represents a possibly
infinite looping call to a const or pure function. Stored in the
- 'call' field and printed as '/c'. Only true if one of
- 'RTL_CONST_CALL_P' or 'RTL_PURE_CALL_P' is true.
+ `call' field and printed as `/c'. Only true if one of
+ `RTL_CONST_CALL_P' or `RTL_PURE_CALL_P' is true.
-'INSN_ANNULLED_BRANCH_P (X)'
- In a 'jump_insn', 'call_insn', or 'insn' indicates that the branch
- is an annulling one. See the discussion under 'sequence' below.
- Stored in the 'unchanging' field and printed as '/u'.
+`INSN_ANNULLED_BRANCH_P (X)'
+ In a `jump_insn', `call_insn', or `insn' indicates that the branch
+ is an annulling one. See the discussion under `sequence' below.
+ Stored in the `unchanging' field and printed as `/u'.
-'INSN_DELETED_P (X)'
- In an 'insn', 'call_insn', 'jump_insn', 'code_label',
- 'jump_table_data', 'barrier', or 'note', nonzero if the insn has
- been deleted. Stored in the 'volatil' field and printed as '/v'.
+`INSN_DELETED_P (X)'
+ In an `insn', `call_insn', `jump_insn', `code_label',
+ `jump_table_data', `barrier', or `note', nonzero if the insn has
+ been deleted. Stored in the `volatil' field and printed as `/v'.
-'INSN_FROM_TARGET_P (X)'
- In an 'insn' or 'jump_insn' or 'call_insn' in a delay slot of a
+`INSN_FROM_TARGET_P (X)'
+ In an `insn' or `jump_insn' or `call_insn' in a delay slot of a
branch, indicates that the insn is from the target of the branch.
- If the branch insn has 'INSN_ANNULLED_BRANCH_P' set, this insn will
- only be executed if the branch is taken. For annulled branches
- with 'INSN_FROM_TARGET_P' clear, the insn will be executed only if
- the branch is not taken. When 'INSN_ANNULLED_BRANCH_P' is not set,
- this insn will always be executed. Stored in the 'in_struct' field
- and printed as '/s'.
-
-'LABEL_PRESERVE_P (X)'
- In a 'code_label' or 'note', indicates that the label is referenced
- by code or data not visible to the RTL of a given function. Labels
- referenced by a non-local goto will have this bit set. Stored in
- the 'in_struct' field and printed as '/s'.
-
-'LABEL_REF_NONLOCAL_P (X)'
- In 'label_ref' and 'reg_label' expressions, nonzero if this is a
- reference to a non-local label. Stored in the 'volatil' field and
- printed as '/v'.
-
-'MEM_KEEP_ALIAS_SET_P (X)'
- In 'mem' expressions, 1 if we should keep the alias set for this
+ If the branch insn has `INSN_ANNULLED_BRANCH_P' set, this insn
+ will only be executed if the branch is taken. For annulled
+ branches with `INSN_FROM_TARGET_P' clear, the insn will be
+ executed only if the branch is not taken. When
+ `INSN_ANNULLED_BRANCH_P' is not set, this insn will always be
+ executed. Stored in the `in_struct' field and printed as `/s'.
+
+`LABEL_PRESERVE_P (X)'
+ In a `code_label' or `note', indicates that the label is
+ referenced by code or data not visible to the RTL of a given
+ function. Labels referenced by a non-local goto will have this
+ bit set. Stored in the `in_struct' field and printed as `/s'.
+
+`LABEL_REF_NONLOCAL_P (X)'
+ In `label_ref' and `reg_label' expressions, nonzero if this is a
+ reference to a non-local label. Stored in the `volatil' field and
+ printed as `/v'.
+
+`MEM_KEEP_ALIAS_SET_P (X)'
+ In `mem' expressions, 1 if we should keep the alias set for this
mem unchanged when we access a component. Set to 1, for example,
when we are already in a non-addressable component of an aggregate.
- Stored in the 'jump' field and printed as '/j'.
+ Stored in the `jump' field and printed as `/j'.
-'MEM_VOLATILE_P (X)'
- In 'mem', 'asm_operands', and 'asm_input' expressions, nonzero for
- volatile memory references. Stored in the 'volatil' field and
- printed as '/v'.
+`MEM_VOLATILE_P (X)'
+ In `mem', `asm_operands', and `asm_input' expressions, nonzero for
+ volatile memory references. Stored in the `volatil' field and
+ printed as `/v'.
-'MEM_NOTRAP_P (X)'
- In 'mem', nonzero for memory references that will not trap. Stored
- in the 'call' field and printed as '/c'.
+`MEM_NOTRAP_P (X)'
+ In `mem', nonzero for memory references that will not trap.
+ Stored in the `call' field and printed as `/c'.
-'MEM_POINTER (X)'
- Nonzero in a 'mem' if the memory reference holds a pointer. Stored
- in the 'frame_related' field and printed as '/f'.
+`MEM_POINTER (X)'
+ Nonzero in a `mem' if the memory reference holds a pointer.
+ Stored in the `frame_related' field and printed as `/f'.
-'REG_FUNCTION_VALUE_P (X)'
- Nonzero in a 'reg' if it is the place in which this function's
+`REG_FUNCTION_VALUE_P (X)'
+ Nonzero in a `reg' if it is the place in which this function's
value is going to be returned. (This happens only in a hard
- register.) Stored in the 'return_val' field and printed as '/i'.
+ register.) Stored in the `return_val' field and printed as `/i'.
-'REG_POINTER (X)'
- Nonzero in a 'reg' if the register holds a pointer. Stored in the
- 'frame_related' field and printed as '/f'.
+`REG_POINTER (X)'
+ Nonzero in a `reg' if the register holds a pointer. Stored in the
+ `frame_related' field and printed as `/f'.
-'REG_USERVAR_P (X)'
- In a 'reg', nonzero if it corresponds to a variable present in the
+`REG_USERVAR_P (X)'
+ In a `reg', nonzero if it corresponds to a variable present in the
user's source code. Zero for temporaries generated internally by
- the compiler. Stored in the 'volatil' field and printed as '/v'.
+ the compiler. Stored in the `volatil' field and printed as `/v'.
The same hard register may be used also for collecting the values
- of functions called by this one, but 'REG_FUNCTION_VALUE_P' is zero
+ of functions called by this one, but `REG_FUNCTION_VALUE_P' is zero
in this kind of use.
-'RTX_FRAME_RELATED_P (X)'
- Nonzero in an 'insn', 'call_insn', 'jump_insn', 'barrier', or 'set'
- which is part of a function prologue and sets the stack pointer,
- sets the frame pointer, or saves a register. This flag should also
- be set on an instruction that sets up a temporary register to use
- in place of the frame pointer. Stored in the 'frame_related' field
- and printed as '/f'.
+`RTX_FRAME_RELATED_P (X)'
+ Nonzero in an `insn', `call_insn', `jump_insn', `barrier', or
+ `set' which is part of a function prologue and sets the stack
+ pointer, sets the frame pointer, or saves a register. This flag
+ should also be set on an instruction that sets up a temporary
+ register to use in place of the frame pointer. Stored in the
+ `frame_related' field and printed as `/f'.
In particular, on RISC targets where there are limits on the sizes
of immediate constants, it is sometimes impossible to reach the
@@ -14352,20 +14498,20 @@ following macros, which expand into lvalues.
save area, and the Canonical Frame Address, i.e., DWARF2's logical
frame pointer, register must (temporarily) be changed to be this
temporary register. So, the instruction that sets this temporary
- register must be marked as 'RTX_FRAME_RELATED_P'.
+ register must be marked as `RTX_FRAME_RELATED_P'.
If the marked instruction is overly complex (defined in terms of
- what 'dwarf2out_frame_debug_expr' can handle), you will also have
- to create a 'REG_FRAME_RELATED_EXPR' note and attach it to the
+ what `dwarf2out_frame_debug_expr' can handle), you will also have
+ to create a `REG_FRAME_RELATED_EXPR' note and attach it to the
instruction. This note should contain a simple expression of the
computation performed by this instruction, i.e., one that
- 'dwarf2out_frame_debug_expr' can handle.
+ `dwarf2out_frame_debug_expr' can handle.
This flag is required for exception handling support on targets
with RTL prologues.
-'MEM_READONLY_P (X)'
- Nonzero in a 'mem', if the memory is statically allocated and
+`MEM_READONLY_P (X)'
+ Nonzero in a `mem', if the memory is statically allocated and
read-only.
Read-only in this context means never modified during the lifetime
@@ -14376,208 +14522,208 @@ following macros, which expand into lvalues.
from the runtime loader to the application, this memory will never
be subsequently modified.
- Stored in the 'unchanging' field and printed as '/u'.
+ Stored in the `unchanging' field and printed as `/u'.
-'SCHED_GROUP_P (X)'
- During instruction scheduling, in an 'insn', 'call_insn',
- 'jump_insn' or 'jump_table_data', indicates that the previous insn
+`SCHED_GROUP_P (X)'
+ During instruction scheduling, in an `insn', `call_insn',
+ `jump_insn' or `jump_table_data', indicates that the previous insn
must be scheduled together with this insn. This is used to ensure
that certain groups of instructions will not be split up by the
- instruction scheduling pass, for example, 'use' insns before a
- 'call_insn' may not be separated from the 'call_insn'. Stored in
- the 'in_struct' field and printed as '/s'.
-
-'SET_IS_RETURN_P (X)'
- For a 'set', nonzero if it is for a return. Stored in the 'jump'
- field and printed as '/j'.
-
-'SIBLING_CALL_P (X)'
- For a 'call_insn', nonzero if the insn is a sibling call. Stored
- in the 'jump' field and printed as '/j'.
-
-'STRING_POOL_ADDRESS_P (X)'
- For a 'symbol_ref' expression, nonzero if it addresses this
- function's string constant pool. Stored in the 'frame_related'
- field and printed as '/f'.
-
-'SUBREG_PROMOTED_UNSIGNED_P (X)'
- Returns a value greater then zero for a 'subreg' that has
- 'SUBREG_PROMOTED_VAR_P' nonzero if the object being referenced is
- kept zero-extended, zero if it is kept sign-extended, and less then
- zero if it is extended some other way via the 'ptr_extend'
- instruction. Stored in the 'unchanging' field and 'volatil' field,
- printed as '/u' and '/v'. This macro may only be used to get the
- value it may not be used to change the value. Use
- 'SUBREG_PROMOTED_UNSIGNED_SET' to change the value.
-
-'SUBREG_PROMOTED_UNSIGNED_SET (X)'
- Set the 'unchanging' and 'volatil' fields in a 'subreg' to reflect
- zero, sign, or other extension. If 'volatil' is zero, then
- 'unchanging' as nonzero means zero extension and as zero means sign
- extension. If 'volatil' is nonzero then some other type of
- extension was done via the 'ptr_extend' instruction.
-
-'SUBREG_PROMOTED_VAR_P (X)'
- Nonzero in a 'subreg' if it was made when accessing an object that
- was promoted to a wider mode in accord with the 'PROMOTED_MODE'
+ instruction scheduling pass, for example, `use' insns before a
+ `call_insn' may not be separated from the `call_insn'. Stored in
+ the `in_struct' field and printed as `/s'.
+
+`SET_IS_RETURN_P (X)'
+ For a `set', nonzero if it is for a return. Stored in the `jump'
+ field and printed as `/j'.
+
+`SIBLING_CALL_P (X)'
+ For a `call_insn', nonzero if the insn is a sibling call. Stored
+ in the `jump' field and printed as `/j'.
+
+`STRING_POOL_ADDRESS_P (X)'
+ For a `symbol_ref' expression, nonzero if it addresses this
+ function's string constant pool. Stored in the `frame_related'
+ field and printed as `/f'.
+
+`SUBREG_PROMOTED_UNSIGNED_P (X)'
+ Returns a value greater then zero for a `subreg' that has
+ `SUBREG_PROMOTED_VAR_P' nonzero if the object being referenced is
+ kept zero-extended, zero if it is kept sign-extended, and less
+ then zero if it is extended some other way via the `ptr_extend'
+ instruction. Stored in the `unchanging' field and `volatil'
+ field, printed as `/u' and `/v'. This macro may only be used to
+ get the value it may not be used to change the value. Use
+ `SUBREG_PROMOTED_UNSIGNED_SET' to change the value.
+
+`SUBREG_PROMOTED_UNSIGNED_SET (X)'
+ Set the `unchanging' and `volatil' fields in a `subreg' to reflect
+ zero, sign, or other extension. If `volatil' is zero, then
+ `unchanging' as nonzero means zero extension and as zero means
+ sign extension. If `volatil' is nonzero then some other type of
+ extension was done via the `ptr_extend' instruction.
+
+`SUBREG_PROMOTED_VAR_P (X)'
+ Nonzero in a `subreg' if it was made when accessing an object that
+ was promoted to a wider mode in accord with the `PROMOTED_MODE'
machine description macro (*note Storage Layout::). In this case,
- the mode of the 'subreg' is the declared mode of the object and the
- mode of 'SUBREG_REG' is the mode of the register that holds the
- object. Promoted variables are always either sign- or
- zero-extended to the wider mode on every assignment. Stored in the
- 'in_struct' field and printed as '/s'.
-
-'SYMBOL_REF_USED (X)'
- In a 'symbol_ref', indicates that X has been used. This is
- normally only used to ensure that X is only declared external once.
- Stored in the 'used' field.
-
-'SYMBOL_REF_WEAK (X)'
- In a 'symbol_ref', indicates that X has been declared weak. Stored
- in the 'return_val' field and printed as '/i'.
-
-'SYMBOL_REF_FLAG (X)'
- In a 'symbol_ref', this is used as a flag for machine-specific
- purposes. Stored in the 'volatil' field and printed as '/v'.
-
- Most uses of 'SYMBOL_REF_FLAG' are historic and may be subsumed by
- 'SYMBOL_REF_FLAGS'. Certainly use of 'SYMBOL_REF_FLAGS' is
+ the mode of the `subreg' is the declared mode of the object and
+ the mode of `SUBREG_REG' is the mode of the register that holds
+ the object. Promoted variables are always either sign- or
+ zero-extended to the wider mode on every assignment. Stored in
+ the `in_struct' field and printed as `/s'.
+
+`SYMBOL_REF_USED (X)'
+ In a `symbol_ref', indicates that X has been used. This is
+ normally only used to ensure that X is only declared external
+ once. Stored in the `used' field.
+
+`SYMBOL_REF_WEAK (X)'
+ In a `symbol_ref', indicates that X has been declared weak.
+ Stored in the `return_val' field and printed as `/i'.
+
+`SYMBOL_REF_FLAG (X)'
+ In a `symbol_ref', this is used as a flag for machine-specific
+ purposes. Stored in the `volatil' field and printed as `/v'.
+
+ Most uses of `SYMBOL_REF_FLAG' are historic and may be subsumed by
+ `SYMBOL_REF_FLAGS'. Certainly use of `SYMBOL_REF_FLAGS' is
mandatory if the target requires more than one bit of storage.
-'PREFETCH_SCHEDULE_BARRIER_P (X)'
- In a 'prefetch', indicates that the prefetch is a scheduling
+`PREFETCH_SCHEDULE_BARRIER_P (X)'
+ In a `prefetch', indicates that the prefetch is a scheduling
barrier. No other INSNs will be moved over it. Stored in the
- 'volatil' field and printed as '/v'.
+ `volatil' field and printed as `/v'.
These are the fields to which the above macros refer:
-'call'
- In a 'mem', 1 means that the memory reference will not trap.
+`call'
+ In a `mem', 1 means that the memory reference will not trap.
- In a 'call', 1 means that this pure or const call may possibly
+ In a `call', 1 means that this pure or const call may possibly
infinite loop.
- In an RTL dump, this flag is represented as '/c'.
+ In an RTL dump, this flag is represented as `/c'.
-'frame_related'
- In an 'insn' or 'set' expression, 1 means that it is part of a
+`frame_related'
+ In an `insn' or `set' expression, 1 means that it is part of a
function prologue and sets the stack pointer, sets the frame
pointer, saves a register, or sets up a temporary register to use
in place of the frame pointer.
- In 'reg' expressions, 1 means that the register holds a pointer.
+ In `reg' expressions, 1 means that the register holds a pointer.
- In 'mem' expressions, 1 means that the memory reference holds a
+ In `mem' expressions, 1 means that the memory reference holds a
pointer.
- In 'symbol_ref' expressions, 1 means that the reference addresses
+ In `symbol_ref' expressions, 1 means that the reference addresses
this function's string constant pool.
- In an RTL dump, this flag is represented as '/f'.
+ In an RTL dump, this flag is represented as `/f'.
-'in_struct'
- In 'reg' expressions, it is 1 if the register has its entire life
+`in_struct'
+ In `reg' expressions, it is 1 if the register has its entire life
contained within the test expression of some loop.
- In 'subreg' expressions, 1 means that the 'subreg' is accessing an
+ In `subreg' expressions, 1 means that the `subreg' is accessing an
object that has had its mode promoted from a wider mode.
- In 'label_ref' expressions, 1 means that the referenced label is
+ In `label_ref' expressions, 1 means that the referenced label is
outside the innermost loop containing the insn in which the
- 'label_ref' was found.
+ `label_ref' was found.
- In 'code_label' expressions, it is 1 if the label may never be
- deleted. This is used for labels which are the target of non-local
- gotos. Such a label that would have been deleted is replaced with
- a 'note' of type 'NOTE_INSN_DELETED_LABEL'.
+ In `code_label' expressions, it is 1 if the label may never be
+ deleted. This is used for labels which are the target of
+ non-local gotos. Such a label that would have been deleted is
+ replaced with a `note' of type `NOTE_INSN_DELETED_LABEL'.
- In an 'insn' during dead-code elimination, 1 means that the insn is
+ In an `insn' during dead-code elimination, 1 means that the insn is
dead code.
- In an 'insn' or 'jump_insn' during reorg for an insn in the delay
+ In an `insn' or `jump_insn' during reorg for an insn in the delay
slot of a branch, 1 means that this insn is from the target of the
branch.
- In an 'insn' during instruction scheduling, 1 means that this insn
+ In an `insn' during instruction scheduling, 1 means that this insn
must be scheduled as part of a group together with the previous
insn.
- In an RTL dump, this flag is represented as '/s'.
+ In an RTL dump, this flag is represented as `/s'.
-'return_val'
- In 'reg' expressions, 1 means the register contains the value to be
- returned by the current function. On machines that pass parameters
- in registers, the same register number may be used for parameters
- as well, but this flag is not set on such uses.
+`return_val'
+ In `reg' expressions, 1 means the register contains the value to
+ be returned by the current function. On machines that pass
+ parameters in registers, the same register number may be used for
+ parameters as well, but this flag is not set on such uses.
- In 'symbol_ref' expressions, 1 means the referenced symbol is weak.
+ In `symbol_ref' expressions, 1 means the referenced symbol is weak.
- In 'call' expressions, 1 means the call is pure.
+ In `call' expressions, 1 means the call is pure.
- In an RTL dump, this flag is represented as '/i'.
+ In an RTL dump, this flag is represented as `/i'.
-'jump'
- In a 'mem' expression, 1 means we should keep the alias set for
+`jump'
+ In a `mem' expression, 1 means we should keep the alias set for
this mem unchanged when we access a component.
- In a 'set', 1 means it is for a return.
+ In a `set', 1 means it is for a return.
- In a 'call_insn', 1 means it is a sibling call.
+ In a `call_insn', 1 means it is a sibling call.
- In an RTL dump, this flag is represented as '/j'.
+ In an RTL dump, this flag is represented as `/j'.
-'unchanging'
- In 'reg' and 'mem' expressions, 1 means that the value of the
+`unchanging'
+ In `reg' and `mem' expressions, 1 means that the value of the
expression never changes.
- In 'subreg' expressions, it is 1 if the 'subreg' references an
+ In `subreg' expressions, it is 1 if the `subreg' references an
unsigned object whose mode has been promoted to a wider mode.
- In an 'insn' or 'jump_insn' in the delay slot of a branch
+ In an `insn' or `jump_insn' in the delay slot of a branch
instruction, 1 means an annulling branch should be used.
- In a 'symbol_ref' expression, 1 means that this symbol addresses
+ In a `symbol_ref' expression, 1 means that this symbol addresses
something in the per-function constant pool.
- In a 'call_insn' 1 means that this instruction is a call to a const
+ In a `call_insn' 1 means that this instruction is a call to a const
function.
- In an RTL dump, this flag is represented as '/u'.
+ In an RTL dump, this flag is represented as `/u'.
-'used'
+`used'
This flag is used directly (without an access macro) at the end of
RTL generation for a function, to count the number of times an
expression appears in insns. Expressions that appear more than
- once are copied, according to the rules for shared structure (*note
- Sharing::).
+ once are copied, according to the rules for shared structure
+ (*note Sharing::).
- For a 'reg', it is used directly (without an access macro) by the
+ For a `reg', it is used directly (without an access macro) by the
leaf register renumbering code to ensure that each register is only
renumbered once.
- In a 'symbol_ref', it indicates that an external declaration for
+ In a `symbol_ref', it indicates that an external declaration for
the symbol has already been written.
-'volatil'
- In a 'mem', 'asm_operands', or 'asm_input' expression, it is 1 if
+`volatil'
+ In a `mem', `asm_operands', or `asm_input' expression, it is 1 if
the memory reference is volatile. Volatile memory references may
not be deleted, reordered or combined.
- In a 'symbol_ref' expression, it is used for machine-specific
+ In a `symbol_ref' expression, it is used for machine-specific
purposes.
- In a 'reg' expression, it is 1 if the value is a user-level
+ In a `reg' expression, it is 1 if the value is a user-level
variable. 0 indicates an internal compiler temporary.
- In an 'insn', 1 means the insn has been deleted.
+ In an `insn', 1 means the insn has been deleted.
- In 'label_ref' and 'reg_label' expressions, 1 means a reference to
+ In `label_ref' and `reg_label' expressions, 1 means a reference to
a non-local label.
- In 'prefetch' expressions, 1 means that the containing insn is a
+ In `prefetch' expressions, 1 means that the containing insn is a
scheduling barrier.
- In an RTL dump, this flag is represented as '/v'.
+ In an RTL dump, this flag is represented as `/v'.

File: gccint.info, Node: Machine Modes, Next: Constants, Prev: Flags, Up: RTL
@@ -14587,369 +14733,370 @@ File: gccint.info, Node: Machine Modes, Next: Constants, Prev: Flags, Up: RT
A machine mode describes a size of data object and the representation
used for it. In the C code, machine modes are represented by an
-enumeration type, 'machine_mode', defined in 'machmode.def'. Each RTL
+enumeration type, `machine_mode', defined in `machmode.def'. Each RTL
expression has room for a machine mode and so do certain kinds of tree
expressions (declarations and types, to be precise).
In debugging dumps and machine descriptions, the machine mode of an RTL
expression is written after the expression code with a colon to separate
-them. The letters 'mode' which appear at the end of each machine mode
-name are omitted. For example, '(reg:SI 38)' is a 'reg' expression with
-machine mode 'SImode'. If the mode is 'VOIDmode', it is not written at
-all.
+them. The letters `mode' which appear at the end of each machine mode
+name are omitted. For example, `(reg:SI 38)' is a `reg' expression
+with machine mode `SImode'. If the mode is `VOIDmode', it is not
+written at all.
Here is a table of machine modes. The term "byte" below refers to an
-object of 'BITS_PER_UNIT' bits (*note Storage Layout::).
+object of `BITS_PER_UNIT' bits (*note Storage Layout::).
-'BImode'
+`BImode'
"Bit" mode represents a single bit, for predicate registers.
-'QImode'
+`QImode'
"Quarter-Integer" mode represents a single byte treated as an
integer.
-'HImode'
+`HImode'
"Half-Integer" mode represents a two-byte integer.
-'PSImode'
+`PSImode'
"Partial Single Integer" mode represents an integer which occupies
four bytes but which doesn't really use all four. On some
machines, this is the right mode to use for pointers.
-'SImode'
+`SImode'
"Single Integer" mode represents a four-byte integer.
-'PDImode'
+`PDImode'
"Partial Double Integer" mode represents an integer which occupies
eight bytes but which doesn't really use all eight. On some
machines, this is the right mode to use for certain pointers.
-'DImode'
+`DImode'
"Double Integer" mode represents an eight-byte integer.
-'TImode'
- "Tetra Integer" (?) mode represents a sixteen-byte integer.
+`TImode'
+ "Tetra Integer" (?) mode represents a sixteen-byte integer.
-'OImode'
- "Octa Integer" (?) mode represents a thirty-two-byte integer.
+`OImode'
+ "Octa Integer" (?) mode represents a thirty-two-byte integer.
-'XImode'
- "Hexadeca Integer" (?) mode represents a sixty-four-byte integer.
+`XImode'
+ "Hexadeca Integer" (?) mode represents a sixty-four-byte integer.
-'QFmode'
+`QFmode'
"Quarter-Floating" mode represents a quarter-precision (single
byte) floating point number.
-'HFmode'
+`HFmode'
"Half-Floating" mode represents a half-precision (two byte)
floating point number.
-'TQFmode'
- "Three-Quarter-Floating" (?) mode represents a
+`TQFmode'
+ "Three-Quarter-Floating" (?) mode represents a
three-quarter-precision (three byte) floating point number.
-'SFmode'
+`SFmode'
"Single Floating" mode represents a four byte floating point
number. In the common case, of a processor with IEEE arithmetic
and 8-bit bytes, this is a single-precision IEEE floating point
number; it can also be used for double-precision (on processors
with 16-bit bytes) and single-precision VAX and IBM types.
-'DFmode'
+`DFmode'
"Double Floating" mode represents an eight byte floating point
number. In the common case, of a processor with IEEE arithmetic
and 8-bit bytes, this is a double-precision IEEE floating point
number.
-'XFmode'
+`XFmode'
"Extended Floating" mode represents an IEEE extended floating point
number. This mode only has 80 meaningful bits (ten bytes). Some
processors require such numbers to be padded to twelve bytes,
others to sixteen; this mode is used for either.
-'SDmode'
+`SDmode'
"Single Decimal Floating" mode represents a four byte decimal
floating point number (as distinct from conventional binary
floating point).
-'DDmode'
+`DDmode'
"Double Decimal Floating" mode represents an eight byte decimal
floating point number.
-'TDmode'
+`TDmode'
"Tetra Decimal Floating" mode represents a sixteen byte decimal
floating point number all 128 of whose bits are meaningful.
-'TFmode'
+`TFmode'
"Tetra Floating" mode represents a sixteen byte floating point
number all 128 of whose bits are meaningful. One common use is the
IEEE quad-precision format.
-'QQmode'
+`QQmode'
"Quarter-Fractional" mode represents a single byte treated as a
signed fractional number. The default format is "s.7".
-'HQmode'
+`HQmode'
"Half-Fractional" mode represents a two-byte signed fractional
number. The default format is "s.15".
-'SQmode'
+`SQmode'
"Single Fractional" mode represents a four-byte signed fractional
number. The default format is "s.31".
-'DQmode'
- "Double Fractional" mode represents an eight-byte signed fractional
- number. The default format is "s.63".
+`DQmode'
+ "Double Fractional" mode represents an eight-byte signed
+ fractional number. The default format is "s.63".
-'TQmode'
- "Tetra Fractional" mode represents a sixteen-byte signed fractional
- number. The default format is "s.127".
+`TQmode'
+ "Tetra Fractional" mode represents a sixteen-byte signed
+ fractional number. The default format is "s.127".
-'UQQmode'
- "Unsigned Quarter-Fractional" mode represents a single byte treated
- as an unsigned fractional number. The default format is ".8".
+`UQQmode'
+ "Unsigned Quarter-Fractional" mode represents a single byte
+ treated as an unsigned fractional number. The default format is
+ ".8".
-'UHQmode'
+`UHQmode'
"Unsigned Half-Fractional" mode represents a two-byte unsigned
fractional number. The default format is ".16".
-'USQmode'
+`USQmode'
"Unsigned Single Fractional" mode represents a four-byte unsigned
fractional number. The default format is ".32".
-'UDQmode'
+`UDQmode'
"Unsigned Double Fractional" mode represents an eight-byte unsigned
fractional number. The default format is ".64".
-'UTQmode'
+`UTQmode'
"Unsigned Tetra Fractional" mode represents a sixteen-byte unsigned
fractional number. The default format is ".128".
-'HAmode'
+`HAmode'
"Half-Accumulator" mode represents a two-byte signed accumulator.
The default format is "s8.7".
-'SAmode'
+`SAmode'
"Single Accumulator" mode represents a four-byte signed
accumulator. The default format is "s16.15".
-'DAmode'
+`DAmode'
"Double Accumulator" mode represents an eight-byte signed
accumulator. The default format is "s32.31".
-'TAmode'
+`TAmode'
"Tetra Accumulator" mode represents a sixteen-byte signed
accumulator. The default format is "s64.63".
-'UHAmode'
+`UHAmode'
"Unsigned Half-Accumulator" mode represents a two-byte unsigned
accumulator. The default format is "8.8".
-'USAmode'
+`USAmode'
"Unsigned Single Accumulator" mode represents a four-byte unsigned
accumulator. The default format is "16.16".
-'UDAmode'
+`UDAmode'
"Unsigned Double Accumulator" mode represents an eight-byte
unsigned accumulator. The default format is "32.32".
-'UTAmode'
+`UTAmode'
"Unsigned Tetra Accumulator" mode represents a sixteen-byte
unsigned accumulator. The default format is "64.64".
-'CCmode'
+`CCmode'
"Condition Code" mode represents the value of a condition code,
which is a machine-specific set of bits used to represent the
- result of a comparison operation. Other machine-specific modes may
- also be used for the condition code. These modes are not used on
- machines that use 'cc0' (*note Condition Code::).
+ result of a comparison operation. Other machine-specific modes
+ may also be used for the condition code. These modes are not used
+ on machines that use `cc0' (*note Condition Code::).
-'BLKmode'
+`BLKmode'
"Block" mode represents values that are aggregates to which none of
the other modes apply. In RTL, only memory references can have
this mode, and only if they appear in string-move or vector
instructions. On machines which have no such instructions,
- 'BLKmode' will not appear in RTL.
+ `BLKmode' will not appear in RTL.
-'VOIDmode'
+`VOIDmode'
Void mode means the absence of a mode or an unspecified mode. For
- example, RTL expressions of code 'const_int' have mode 'VOIDmode'
+ example, RTL expressions of code `const_int' have mode `VOIDmode'
because they can be taken to have whatever mode the context
- requires. In debugging dumps of RTL, 'VOIDmode' is expressed by
+ requires. In debugging dumps of RTL, `VOIDmode' is expressed by
the absence of any mode.
-'QCmode, HCmode, SCmode, DCmode, XCmode, TCmode'
+`QCmode, HCmode, SCmode, DCmode, XCmode, TCmode'
These modes stand for a complex number represented as a pair of
- floating point values. The floating point values are in 'QFmode',
- 'HFmode', 'SFmode', 'DFmode', 'XFmode', and 'TFmode', respectively.
+ floating point values. The floating point values are in `QFmode',
+ `HFmode', `SFmode', `DFmode', `XFmode', and `TFmode', respectively.
-'CQImode, CHImode, CSImode, CDImode, CTImode, COImode'
+`CQImode, CHImode, CSImode, CDImode, CTImode, COImode'
These modes stand for a complex number represented as a pair of
- integer values. The integer values are in 'QImode', 'HImode',
- 'SImode', 'DImode', 'TImode', and 'OImode', respectively.
+ integer values. The integer values are in `QImode', `HImode',
+ `SImode', `DImode', `TImode', and `OImode', respectively.
-'BND32mode BND64mode'
+`BND32mode BND64mode'
These modes stand for bounds for pointer of 32 and 64 bit size
respectively. Mode size is double pointer mode size.
- The machine description defines 'Pmode' as a C macro which expands into
-the machine mode used for addresses. Normally this is the mode whose
-size is 'BITS_PER_WORD', 'SImode' on 32-bit machines.
+ The machine description defines `Pmode' as a C macro which expands
+into the machine mode used for addresses. Normally this is the mode
+whose size is `BITS_PER_WORD', `SImode' on 32-bit machines.
- The only modes which a machine description must support are 'QImode',
-and the modes corresponding to 'BITS_PER_WORD', 'FLOAT_TYPE_SIZE' and
-'DOUBLE_TYPE_SIZE'. The compiler will attempt to use 'DImode' for
+ The only modes which a machine description must support are `QImode',
+and the modes corresponding to `BITS_PER_WORD', `FLOAT_TYPE_SIZE' and
+`DOUBLE_TYPE_SIZE'. The compiler will attempt to use `DImode' for
8-byte structures and unions, but this can be prevented by overriding
-the definition of 'MAX_FIXED_MODE_SIZE'. Alternatively, you can have
-the compiler use 'TImode' for 16-byte structures and unions. Likewise,
-you can arrange for the C type 'short int' to avoid using 'HImode'.
+the definition of `MAX_FIXED_MODE_SIZE'. Alternatively, you can have
+the compiler use `TImode' for 16-byte structures and unions. Likewise,
+you can arrange for the C type `short int' to avoid using `HImode'.
Very few explicit references to machine modes remain in the compiler
and these few references will soon be removed. Instead, the machine
modes are divided into mode classes. These are represented by the
-enumeration type 'enum mode_class' defined in 'machmode.h'. The
+enumeration type `enum mode_class' defined in `machmode.h'. The
possible mode classes are:
-'MODE_INT'
- Integer modes. By default these are 'BImode', 'QImode', 'HImode',
- 'SImode', 'DImode', 'TImode', and 'OImode'.
+`MODE_INT'
+ Integer modes. By default these are `BImode', `QImode', `HImode',
+ `SImode', `DImode', `TImode', and `OImode'.
-'MODE_PARTIAL_INT'
- The "partial integer" modes, 'PQImode', 'PHImode', 'PSImode' and
- 'PDImode'.
+`MODE_PARTIAL_INT'
+ The "partial integer" modes, `PQImode', `PHImode', `PSImode' and
+ `PDImode'.
-'MODE_FLOAT'
- Floating point modes. By default these are 'QFmode', 'HFmode',
- 'TQFmode', 'SFmode', 'DFmode', 'XFmode' and 'TFmode'.
+`MODE_FLOAT'
+ Floating point modes. By default these are `QFmode', `HFmode',
+ `TQFmode', `SFmode', `DFmode', `XFmode' and `TFmode'.
-'MODE_DECIMAL_FLOAT'
- Decimal floating point modes. By default these are 'SDmode',
- 'DDmode' and 'TDmode'.
+`MODE_DECIMAL_FLOAT'
+ Decimal floating point modes. By default these are `SDmode',
+ `DDmode' and `TDmode'.
-'MODE_FRACT'
- Signed fractional modes. By default these are 'QQmode', 'HQmode',
- 'SQmode', 'DQmode' and 'TQmode'.
+`MODE_FRACT'
+ Signed fractional modes. By default these are `QQmode', `HQmode',
+ `SQmode', `DQmode' and `TQmode'.
-'MODE_UFRACT'
- Unsigned fractional modes. By default these are 'UQQmode',
- 'UHQmode', 'USQmode', 'UDQmode' and 'UTQmode'.
+`MODE_UFRACT'
+ Unsigned fractional modes. By default these are `UQQmode',
+ `UHQmode', `USQmode', `UDQmode' and `UTQmode'.
-'MODE_ACCUM'
- Signed accumulator modes. By default these are 'HAmode', 'SAmode',
- 'DAmode' and 'TAmode'.
+`MODE_ACCUM'
+ Signed accumulator modes. By default these are `HAmode',
+ `SAmode', `DAmode' and `TAmode'.
-'MODE_UACCUM'
- Unsigned accumulator modes. By default these are 'UHAmode',
- 'USAmode', 'UDAmode' and 'UTAmode'.
+`MODE_UACCUM'
+ Unsigned accumulator modes. By default these are `UHAmode',
+ `USAmode', `UDAmode' and `UTAmode'.
-'MODE_COMPLEX_INT'
+`MODE_COMPLEX_INT'
Complex integer modes. (These are not currently implemented).
-'MODE_COMPLEX_FLOAT'
- Complex floating point modes. By default these are 'QCmode',
- 'HCmode', 'SCmode', 'DCmode', 'XCmode', and 'TCmode'.
+`MODE_COMPLEX_FLOAT'
+ Complex floating point modes. By default these are `QCmode',
+ `HCmode', `SCmode', `DCmode', `XCmode', and `TCmode'.
-'MODE_FUNCTION'
+`MODE_FUNCTION'
Algol or Pascal function variables including a static chain.
(These are not currently implemented).
-'MODE_CC'
- Modes representing condition code values. These are 'CCmode' plus
- any 'CC_MODE' modes listed in the 'MACHINE-modes.def'. *Note Jump
+`MODE_CC'
+ Modes representing condition code values. These are `CCmode' plus
+ any `CC_MODE' modes listed in the `MACHINE-modes.def'. *Note Jump
Patterns::, also see *note Condition Code::.
-'MODE_POINTER_BOUNDS'
+`MODE_POINTER_BOUNDS'
Pointer bounds modes. Used to represent values of pointer bounds
type. Operations in these modes may be executed as NOPs depending
on hardware features and environment setup.
-'MODE_RANDOM'
+`MODE_RANDOM'
This is a catchall mode class for modes which don't fit into the
- above classes. Currently 'VOIDmode' and 'BLKmode' are in
- 'MODE_RANDOM'.
+ above classes. Currently `VOIDmode' and `BLKmode' are in
+ `MODE_RANDOM'.
Here are some C macros that relate to machine modes:
-'GET_MODE (X)'
+`GET_MODE (X)'
Returns the machine mode of the RTX X.
-'PUT_MODE (X, NEWMODE)'
+`PUT_MODE (X, NEWMODE)'
Alters the machine mode of the RTX X to be NEWMODE.
-'NUM_MACHINE_MODES'
+`NUM_MACHINE_MODES'
Stands for the number of machine modes available on the target
machine. This is one greater than the largest numeric value of any
machine mode.
-'GET_MODE_NAME (M)'
+`GET_MODE_NAME (M)'
Returns the name of mode M as a string.
-'GET_MODE_CLASS (M)'
+`GET_MODE_CLASS (M)'
Returns the mode class of mode M.
-'GET_MODE_WIDER_MODE (M)'
+`GET_MODE_WIDER_MODE (M)'
Returns the next wider natural mode. For example, the expression
- 'GET_MODE_WIDER_MODE (QImode)' returns 'HImode'.
+ `GET_MODE_WIDER_MODE (QImode)' returns `HImode'.
-'GET_MODE_SIZE (M)'
+`GET_MODE_SIZE (M)'
Returns the size in bytes of a datum of mode M.
-'GET_MODE_BITSIZE (M)'
+`GET_MODE_BITSIZE (M)'
Returns the size in bits of a datum of mode M.
-'GET_MODE_IBIT (M)'
+`GET_MODE_IBIT (M)'
Returns the number of integral bits of a datum of fixed-point mode
M.
-'GET_MODE_FBIT (M)'
+`GET_MODE_FBIT (M)'
Returns the number of fractional bits of a datum of fixed-point
mode M.
-'GET_MODE_MASK (M)'
+`GET_MODE_MASK (M)'
Returns a bitmask containing 1 for all bits in a word that fit
- within mode M. This macro can only be used for modes whose bitsize
- is less than or equal to 'HOST_BITS_PER_INT'.
+ within mode M. This macro can only be used for modes whose
+ bitsize is less than or equal to `HOST_BITS_PER_INT'.
-'GET_MODE_ALIGNMENT (M)'
+`GET_MODE_ALIGNMENT (M)'
Return the required alignment, in bits, for an object of mode M.
-'GET_MODE_UNIT_SIZE (M)'
+`GET_MODE_UNIT_SIZE (M)'
Returns the size in bytes of the subunits of a datum of mode M.
- This is the same as 'GET_MODE_SIZE' except in the case of complex
+ This is the same as `GET_MODE_SIZE' except in the case of complex
modes. For them, the unit size is the size of the real or
imaginary part.
-'GET_MODE_NUNITS (M)'
+`GET_MODE_NUNITS (M)'
Returns the number of units contained in a mode, i.e.,
- 'GET_MODE_SIZE' divided by 'GET_MODE_UNIT_SIZE'.
+ `GET_MODE_SIZE' divided by `GET_MODE_UNIT_SIZE'.
-'GET_CLASS_NARROWEST_MODE (C)'
+`GET_CLASS_NARROWEST_MODE (C)'
Returns the narrowest mode in mode class C.
- The following 3 variables are defined on every target. They can be
+ The following 3 variables are defined on every target. They can be
used to allocate buffers that are guaranteed to be large enough to hold
-any value that can be represented on the target. The first two can be
+any value that can be represented on the target. The first two can be
overridden by defining them in the target's mode.def file, however, the
value must be a constant that can determined very early in the
-compilation process. The third symbol cannot be overridden.
+compilation process. The third symbol cannot be overridden.
-'BITS_PER_UNIT'
+`BITS_PER_UNIT'
The number of bits in an addressable storage unit (byte). If you
do not define this, the default is 8.
-'MAX_BITSIZE_MODE_ANY_INT'
+`MAX_BITSIZE_MODE_ANY_INT'
The maximum bitsize of any mode that is used in integer math. This
should be overridden by the target if it uses large integers as
- containers for larger vectors but otherwise never uses the contents
- to compute integer values.
+ containers for larger vectors but otherwise never uses the
+ contents to compute integer values.
-'MAX_BITSIZE_MODE_ANY_MODE'
+`MAX_BITSIZE_MODE_ANY_MODE'
The bitsize of the largest mode on the target.
- The global variables 'byte_mode' and 'word_mode' contain modes whose
-classes are 'MODE_INT' and whose bitsizes are either 'BITS_PER_UNIT' or
-'BITS_PER_WORD', respectively. On 32-bit machines, these are 'QImode'
-and 'SImode', respectively.
+ The global variables `byte_mode' and `word_mode' contain modes whose
+classes are `MODE_INT' and whose bitsizes are either `BITS_PER_UNIT' or
+`BITS_PER_WORD', respectively. On 32-bit machines, these are `QImode'
+and `SImode', respectively.

File: gccint.info, Node: Constants, Next: Regs and Memory, Prev: Machine Modes, Up: RTL
@@ -14959,165 +15106,165 @@ File: gccint.info, Node: Constants, Next: Regs and Memory, Prev: Machine Mode
The simplest RTL expressions are those that represent constant values.
-'(const_int I)'
+`(const_int I)'
This type of expression represents the integer value I. I is
- customarily accessed with the macro 'INTVAL' as in 'INTVAL (EXP)',
- which is equivalent to 'XWINT (EXP, 0)'.
+ customarily accessed with the macro `INTVAL' as in `INTVAL (EXP)',
+ which is equivalent to `XWINT (EXP, 0)'.
Constants generated for modes with fewer bits than in
- 'HOST_WIDE_INT' must be sign extended to full width (e.g., with
- 'gen_int_mode'). For constants for modes with more bits than in
- 'HOST_WIDE_INT' the implied high order bits of that constant are
+ `HOST_WIDE_INT' must be sign extended to full width (e.g., with
+ `gen_int_mode'). For constants for modes with more bits than in
+ `HOST_WIDE_INT' the implied high order bits of that constant are
copies of the top bit. Note however that values are neither
inherently signed nor inherently unsigned; where necessary,
signedness is determined by the rtl operation instead.
There is only one expression object for the integer value zero; it
- is the value of the variable 'const0_rtx'. Likewise, the only
- expression for integer value one is found in 'const1_rtx', the only
- expression for integer value two is found in 'const2_rtx', and the
+ is the value of the variable `const0_rtx'. Likewise, the only
+ expression for integer value one is found in `const1_rtx', the only
+ expression for integer value two is found in `const2_rtx', and the
only expression for integer value negative one is found in
- 'constm1_rtx'. Any attempt to create an expression of code
- 'const_int' and value zero, one, two or negative one will return
- 'const0_rtx', 'const1_rtx', 'const2_rtx' or 'constm1_rtx' as
+ `constm1_rtx'. Any attempt to create an expression of code
+ `const_int' and value zero, one, two or negative one will return
+ `const0_rtx', `const1_rtx', `const2_rtx' or `constm1_rtx' as
appropriate.
Similarly, there is only one object for the integer whose value is
- 'STORE_FLAG_VALUE'. It is found in 'const_true_rtx'. If
- 'STORE_FLAG_VALUE' is one, 'const_true_rtx' and 'const1_rtx' will
- point to the same object. If 'STORE_FLAG_VALUE' is -1,
- 'const_true_rtx' and 'constm1_rtx' will point to the same object.
+ `STORE_FLAG_VALUE'. It is found in `const_true_rtx'. If
+ `STORE_FLAG_VALUE' is one, `const_true_rtx' and `const1_rtx' will
+ point to the same object. If `STORE_FLAG_VALUE' is -1,
+ `const_true_rtx' and `constm1_rtx' will point to the same object.
-'(const_double:M I0 I1 ...)'
+`(const_double:M I0 I1 ...)'
This represents either a floating-point constant of mode M or (on
- older ports that do not define 'TARGET_SUPPORTS_WIDE_INT') an
- integer constant too large to fit into 'HOST_BITS_PER_WIDE_INT'
+ older ports that do not define `TARGET_SUPPORTS_WIDE_INT') an
+ integer constant too large to fit into `HOST_BITS_PER_WIDE_INT'
bits but small enough to fit within twice that number of bits. In
- the latter case, M will be 'VOIDmode'. For integral values
+ the latter case, M will be `VOIDmode'. For integral values
constants for modes with more bits than twice the number in
- 'HOST_WIDE_INT' the implied high order bits of that constant are
- copies of the top bit of 'CONST_DOUBLE_HIGH'. Note however that
+ `HOST_WIDE_INT' the implied high order bits of that constant are
+ copies of the top bit of `CONST_DOUBLE_HIGH'. Note however that
integral values are neither inherently signed nor inherently
unsigned; where necessary, signedness is determined by the rtl
operation instead.
- On more modern ports, 'CONST_DOUBLE' only represents floating point
- values. New ports define 'TARGET_SUPPORTS_WIDE_INT' to make this
- designation.
+ On more modern ports, `CONST_DOUBLE' only represents floating
+ point values. New ports define `TARGET_SUPPORTS_WIDE_INT' to make
+ this designation.
- If M is 'VOIDmode', the bits of the value are stored in I0 and I1.
- I0 is customarily accessed with the macro 'CONST_DOUBLE_LOW' and I1
- with 'CONST_DOUBLE_HIGH'.
+ If M is `VOIDmode', the bits of the value are stored in I0 and I1.
+ I0 is customarily accessed with the macro `CONST_DOUBLE_LOW' and
+ I1 with `CONST_DOUBLE_HIGH'.
If the constant is floating point (regardless of its precision),
then the number of integers used to store the value depends on the
- size of 'REAL_VALUE_TYPE' (*note Floating Point::). The integers
+ size of `REAL_VALUE_TYPE' (*note Floating Point::). The integers
represent a floating point number, but not precisely in the target
- machine's or host machine's floating point format. To convert them
- to the precise bit pattern used by the target machine, use the
- macro 'REAL_VALUE_TO_TARGET_DOUBLE' and friends (*note Data
+ machine's or host machine's floating point format. To convert
+ them to the precise bit pattern used by the target machine, use
+ the macro `REAL_VALUE_TO_TARGET_DOUBLE' and friends (*note Data
Output::).
-'(const_wide_int:M NUNITS ELT0 ...)'
- This contains an array of 'HOST_WIDE_INT's that is large enough to
+`(const_wide_int:M NUNITS ELT0 ...)'
+ This contains an array of `HOST_WIDE_INT's that is large enough to
hold any constant that can be represented on the target. This form
of rtl is only used on targets that define
- 'TARGET_SUPPORTS_WIDE_INT' to be nonzero and then 'CONST_DOUBLE's
+ `TARGET_SUPPORTS_WIDE_INT' to be nonzero and then `CONST_DOUBLE's
are only used to hold floating-point values. If the target leaves
- 'TARGET_SUPPORTS_WIDE_INT' defined as 0, 'CONST_WIDE_INT's are not
- used and 'CONST_DOUBLE's are as they were before.
+ `TARGET_SUPPORTS_WIDE_INT' defined as 0, `CONST_WIDE_INT's are not
+ used and `CONST_DOUBLE's are as they were before.
The values are stored in a compressed format. The higher-order 0s
or -1s are not represented if they are just the logical sign
extension of the number that is represented.
-'CONST_WIDE_INT_VEC (CODE)'
- Returns the entire array of 'HOST_WIDE_INT's that are used to store
- the value. This macro should be rarely used.
+`CONST_WIDE_INT_VEC (CODE)'
+ Returns the entire array of `HOST_WIDE_INT's that are used to
+ store the value. This macro should be rarely used.
-'CONST_WIDE_INT_NUNITS (CODE)'
- The number of 'HOST_WIDE_INT's used to represent the number. Note
- that this generally is smaller than the number of 'HOST_WIDE_INT's
+`CONST_WIDE_INT_NUNITS (CODE)'
+ The number of `HOST_WIDE_INT's used to represent the number. Note
+ that this generally is smaller than the number of `HOST_WIDE_INT's
implied by the mode size.
-'CONST_WIDE_INT_NUNITS (CODE,I)'
- Returns the 'i'th element of the array. Element 0 is contains the
- low order bits of the constant.
+`CONST_WIDE_INT_NUNITS (CODE,I)'
+ Returns the `i'th element of the array. Element 0 is contains
+ the low order bits of the constant.
-'(const_fixed:M ...)'
- Represents a fixed-point constant of mode M. The operand is a data
- structure of type 'struct fixed_value' and is accessed with the
- macro 'CONST_FIXED_VALUE'. The high part of data is accessed with
- 'CONST_FIXED_VALUE_HIGH'; the low part is accessed with
- 'CONST_FIXED_VALUE_LOW'.
+`(const_fixed:M ...)'
+ Represents a fixed-point constant of mode M. The operand is a
+ data structure of type `struct fixed_value' and is accessed with
+ the macro `CONST_FIXED_VALUE'. The high part of data is accessed
+ with `CONST_FIXED_VALUE_HIGH'; the low part is accessed with
+ `CONST_FIXED_VALUE_LOW'.
-'(const_vector:M [X0 X1 ...])'
+`(const_vector:M [X0 X1 ...])'
Represents a vector constant. The square brackets stand for the
vector containing the constant elements. X0, X1 and so on are the
- 'const_int', 'const_double' or 'const_fixed' elements.
+ `const_int', `const_double' or `const_fixed' elements.
- The number of units in a 'const_vector' is obtained with the macro
- 'CONST_VECTOR_NUNITS' as in 'CONST_VECTOR_NUNITS (V)'.
+ The number of units in a `const_vector' is obtained with the macro
+ `CONST_VECTOR_NUNITS' as in `CONST_VECTOR_NUNITS (V)'.
Individual elements in a vector constant are accessed with the
- macro 'CONST_VECTOR_ELT' as in 'CONST_VECTOR_ELT (V, N)' where V is
- the vector constant and N is the element desired.
+ macro `CONST_VECTOR_ELT' as in `CONST_VECTOR_ELT (V, N)' where V
+ is the vector constant and N is the element desired.
-'(const_string STR)'
+`(const_string STR)'
Represents a constant string with value STR. Currently this is
used only for insn attributes (*note Insn Attributes::) since
constant strings in C are placed in memory.
-'(symbol_ref:MODE SYMBOL)'
+`(symbol_ref:MODE SYMBOL)'
Represents the value of an assembler label for data. SYMBOL is a
string that describes the name of the assembler label. If it
- starts with a '*', the label is the rest of SYMBOL not including
- the '*'. Otherwise, the label is SYMBOL, usually prefixed with
- '_'.
+ starts with a `*', the label is the rest of SYMBOL not including
+ the `*'. Otherwise, the label is SYMBOL, usually prefixed with
+ `_'.
- The 'symbol_ref' contains a mode, which is usually 'Pmode'.
+ The `symbol_ref' contains a mode, which is usually `Pmode'.
Usually that is the only mode for which a symbol is directly valid.
-'(label_ref:MODE LABEL)'
+`(label_ref:MODE LABEL)'
Represents the value of an assembler label for code. It contains
- one operand, an expression, which must be a 'code_label' or a
- 'note' of type 'NOTE_INSN_DELETED_LABEL' that appears in the
+ one operand, an expression, which must be a `code_label' or a
+ `note' of type `NOTE_INSN_DELETED_LABEL' that appears in the
instruction sequence to identify the place where the label should
go.
The reason for using a distinct expression type for code label
references is so that jump optimization can distinguish them.
- The 'label_ref' contains a mode, which is usually 'Pmode'. Usually
- that is the only mode for which a label is directly valid.
+ The `label_ref' contains a mode, which is usually `Pmode'.
+ Usually that is the only mode for which a label is directly valid.
-'(const:M EXP)'
+`(const:M EXP)'
Represents a constant that is the result of an assembly-time
arithmetic computation. The operand, EXP, is an expression that
- contains only constants ('const_int', 'symbol_ref' and 'label_ref'
- expressions) combined with 'plus' and 'minus'. However, not all
+ contains only constants (`const_int', `symbol_ref' and `label_ref'
+ expressions) combined with `plus' and `minus'. However, not all
combinations are valid, since the assembler cannot do arbitrary
arithmetic on relocatable symbols.
- M should be 'Pmode'.
-
-'(high:M EXP)'
- Represents the high-order bits of EXP, usually a 'symbol_ref'. The
- number of bits is machine-dependent and is normally the number of
- bits specified in an instruction that initializes the high order
- bits of a register. It is used with 'lo_sum' to represent the
- typical two-instruction sequence used in RISC machines to reference
- a global memory location.
-
- M should be 'Pmode'.
-
- The macro 'CONST0_RTX (MODE)' refers to an expression with value 0 in
-mode MODE. If mode MODE is of mode class 'MODE_INT', it returns
-'const0_rtx'. If mode MODE is of mode class 'MODE_FLOAT', it returns a
-'CONST_DOUBLE' expression in mode MODE. Otherwise, it returns a
-'CONST_VECTOR' expression in mode MODE. Similarly, the macro
-'CONST1_RTX (MODE)' refers to an expression with value 1 in mode MODE
-and similarly for 'CONST2_RTX'. The 'CONST1_RTX' and 'CONST2_RTX'
+ M should be `Pmode'.
+
+`(high:M EXP)'
+ Represents the high-order bits of EXP, usually a `symbol_ref'.
+ The number of bits is machine-dependent and is normally the number
+ of bits specified in an instruction that initializes the high
+ order bits of a register. It is used with `lo_sum' to represent
+ the typical two-instruction sequence used in RISC machines to
+ reference a global memory location.
+
+ M should be `Pmode'.
+
+ The macro `CONST0_RTX (MODE)' refers to an expression with value 0 in
+mode MODE. If mode MODE is of mode class `MODE_INT', it returns
+`const0_rtx'. If mode MODE is of mode class `MODE_FLOAT', it returns a
+`CONST_DOUBLE' expression in mode MODE. Otherwise, it returns a
+`CONST_VECTOR' expression in mode MODE. Similarly, the macro
+`CONST1_RTX (MODE)' refers to an expression with value 1 in mode MODE
+and similarly for `CONST2_RTX'. The `CONST1_RTX' and `CONST2_RTX'
macros are undefined for vector modes.

@@ -15129,9 +15276,9 @@ File: gccint.info, Node: Regs and Memory, Next: Arithmetic, Prev: Constants,
Here are the RTL expression types for describing access to machine
registers and to main memory.
-'(reg:M N)'
+`(reg:M N)'
For small values of the integer N (those that are less than
- 'FIRST_PSEUDO_REGISTER'), this stands for a reference to machine
+ `FIRST_PSEUDO_REGISTER'), this stands for a reference to machine
register number N: a "hard register". For larger values of N, it
stands for a temporary value or "pseudo register". The compiler's
strategy is to generate code assuming an unlimited number of such
@@ -15148,7 +15295,7 @@ registers and to main memory.
Even for a register that the machine can access in only one mode,
the mode must always be specified.
- The symbol 'FIRST_PSEUDO_REGISTER' is defined by the machine
+ The symbol `FIRST_PSEUDO_REGISTER' is defined by the machine
description, since the number of hard registers on the machine is
an invariant characteristic of the machine. Note, however, that
not all of the machine registers must be general registers. All
@@ -15159,142 +15306,144 @@ registers and to main memory.
A hard register may be accessed in various modes throughout one
function, but each pseudo register is given a natural mode and is
accessed only in that mode. When it is necessary to describe an
- access to a pseudo register using a nonnatural mode, a 'subreg'
+ access to a pseudo register using a nonnatural mode, a `subreg'
expression is used.
- A 'reg' expression with a machine mode that specifies more than one
- word of data may actually stand for several consecutive registers.
- If in addition the register number specifies a hardware register,
- then it actually represents several consecutive hardware registers
- starting with the specified one.
+ A `reg' expression with a machine mode that specifies more than
+ one word of data may actually stand for several consecutive
+ registers. If in addition the register number specifies a
+ hardware register, then it actually represents several consecutive
+ hardware registers starting with the specified one.
Each pseudo register number used in a function's RTL code is
- represented by a unique 'reg' expression.
+ represented by a unique `reg' expression.
Some pseudo register numbers, those within the range of
- 'FIRST_VIRTUAL_REGISTER' to 'LAST_VIRTUAL_REGISTER' only appear
+ `FIRST_VIRTUAL_REGISTER' to `LAST_VIRTUAL_REGISTER' only appear
during the RTL generation phase and are eliminated before the
optimization phases. These represent locations in the stack frame
- that cannot be determined until RTL generation for the function has
- been completed. The following virtual register numbers are
+ that cannot be determined until RTL generation for the function
+ has been completed. The following virtual register numbers are
defined:
- 'VIRTUAL_INCOMING_ARGS_REGNUM'
- This points to the first word of the incoming arguments passed
- on the stack. Normally these arguments are placed there by
- the caller, but the callee may have pushed some arguments that
- were previously passed in registers.
+ `VIRTUAL_INCOMING_ARGS_REGNUM'
+ This points to the first word of the incoming arguments
+ passed on the stack. Normally these arguments are placed
+ there by the caller, but the callee may have pushed some
+ arguments that were previously passed in registers.
When RTL generation is complete, this virtual register is
replaced by the sum of the register given by
- 'ARG_POINTER_REGNUM' and the value of 'FIRST_PARM_OFFSET'.
+ `ARG_POINTER_REGNUM' and the value of `FIRST_PARM_OFFSET'.
- 'VIRTUAL_STACK_VARS_REGNUM'
- If 'FRAME_GROWS_DOWNWARD' is defined to a nonzero value, this
+ `VIRTUAL_STACK_VARS_REGNUM'
+ If `FRAME_GROWS_DOWNWARD' is defined to a nonzero value, this
points to immediately above the first variable on the stack.
Otherwise, it points to the first variable on the stack.
- 'VIRTUAL_STACK_VARS_REGNUM' is replaced with the sum of the
- register given by 'FRAME_POINTER_REGNUM' and the value
- 'STARTING_FRAME_OFFSET'.
+ `VIRTUAL_STACK_VARS_REGNUM' is replaced with the sum of the
+ register given by `FRAME_POINTER_REGNUM' and the value
+ `STARTING_FRAME_OFFSET'.
- 'VIRTUAL_STACK_DYNAMIC_REGNUM'
- This points to the location of dynamically allocated memory on
- the stack immediately after the stack pointer has been
+ `VIRTUAL_STACK_DYNAMIC_REGNUM'
+ This points to the location of dynamically allocated memory
+ on the stack immediately after the stack pointer has been
adjusted by the amount of memory desired.
This virtual register is replaced by the sum of the register
- given by 'STACK_POINTER_REGNUM' and the value
- 'STACK_DYNAMIC_OFFSET'.
+ given by `STACK_POINTER_REGNUM' and the value
+ `STACK_DYNAMIC_OFFSET'.
- 'VIRTUAL_OUTGOING_ARGS_REGNUM'
+ `VIRTUAL_OUTGOING_ARGS_REGNUM'
This points to the location in the stack at which outgoing
arguments should be written when the stack is pre-pushed
(arguments pushed using push insns should always use
- 'STACK_POINTER_REGNUM').
+ `STACK_POINTER_REGNUM').
This virtual register is replaced by the sum of the register
- given by 'STACK_POINTER_REGNUM' and the value
- 'STACK_POINTER_OFFSET'.
-
-'(subreg:M1 REG:M2 BYTENUM)'
+ given by `STACK_POINTER_REGNUM' and the value
+ `STACK_POINTER_OFFSET'.
- 'subreg' expressions are used to refer to a register in a machine
+`(subreg:M1 REG:M2 BYTENUM)'
+ `subreg' expressions are used to refer to a register in a machine
mode other than its natural one, or to refer to one register of a
- multi-part 'reg' that actually refers to several registers.
+ multi-part `reg' that actually refers to several registers.
Each pseudo register has a natural mode. If it is necessary to
- operate on it in a different mode, the register must be enclosed in
- a 'subreg'.
+ operate on it in a different mode, the register must be enclosed
+ in a `subreg'.
There are currently three supported types for the first operand of
- a 'subreg':
- * pseudo registers This is the most common case. Most 'subreg's
- have pseudo 'reg's as their first operand.
+ a `subreg':
+ * pseudo registers This is the most common case. Most
+ `subreg's have pseudo `reg's as their first operand.
- * mem 'subreg's of 'mem' were common in earlier versions of GCC
+ * mem `subreg's of `mem' were common in earlier versions of GCC
and are still supported. During the reload pass these are
- replaced by plain 'mem's. On machines that do not do
- instruction scheduling, use of 'subreg's of 'mem' are still
- used, but this is no longer recommended. Such 'subreg's are
- considered to be 'register_operand's rather than
- 'memory_operand's before and during reload. Because of this,
+ replaced by plain `mem's. On machines that do not do
+ instruction scheduling, use of `subreg's of `mem' are still
+ used, but this is no longer recommended. Such `subreg's are
+ considered to be `register_operand's rather than
+ `memory_operand's before and during reload. Because of this,
the scheduling passes cannot properly schedule instructions
- with 'subreg's of 'mem', so for machines that do scheduling,
- 'subreg's of 'mem' should never be used. To support this, the
- combine and recog passes have explicit code to inhibit the
- creation of 'subreg's of 'mem' when 'INSN_SCHEDULING' is
+ with `subreg's of `mem', so for machines that do scheduling,
+ `subreg's of `mem' should never be used. To support this,
+ the combine and recog passes have explicit code to inhibit
+ the creation of `subreg's of `mem' when `INSN_SCHEDULING' is
defined.
- The use of 'subreg's of 'mem' after the reload pass is an area
+ The use of `subreg's of `mem' after the reload pass is an area
that is not well understood and should be avoided. There is
- still some code in the compiler to support this, but this code
- has possibly rotted. This use of 'subreg's is discouraged and
- will most likely not be supported in the future.
+ still some code in the compiler to support this, but this
+ code has possibly rotted. This use of `subreg's is
+ discouraged and will most likely not be supported in the
+ future.
* hard registers It is seldom necessary to wrap hard registers
- in 'subreg's; such registers would normally reduce to a single
- 'reg' rtx. This use of 'subreg's is discouraged and may not
- be supported in the future.
+ in `subreg's; such registers would normally reduce to a
+ single `reg' rtx. This use of `subreg's is discouraged and
+ may not be supported in the future.
- 'subreg's of 'subreg's are not supported. Using
- 'simplify_gen_subreg' is the recommended way to avoid this problem.
- 'subreg's come in two distinct flavors, each having its own usage
+ `subreg's of `subreg's are not supported. Using
+ `simplify_gen_subreg' is the recommended way to avoid this problem.
+
+ `subreg's come in two distinct flavors, each having its own usage
and rules:
- Paradoxical subregs
- When M1 is strictly wider than M2, the 'subreg' expression is
+ Paradoxical subregs
+ When M1 is strictly wider than M2, the `subreg' expression is
called "paradoxical". The canonical test for this class of
- 'subreg' is:
+ `subreg' is:
GET_MODE_SIZE (M1) > GET_MODE_SIZE (M2)
- Paradoxical 'subreg's can be used as both lvalues and rvalues.
+ Paradoxical `subreg's can be used as both lvalues and rvalues.
When used as an lvalue, the low-order bits of the source value
- are stored in REG and the high-order bits are discarded. When
- used as an rvalue, the low-order bits of the 'subreg' are
+ are stored in REG and the high-order bits are discarded.
+ When used as an rvalue, the low-order bits of the `subreg' are
taken from REG while the high-order bits may or may not be
defined.
The high-order bits of rvalues are in the following
circumstances:
- * 'subreg's of 'mem' When M2 is smaller than a word, the
- macro 'LOAD_EXTEND_OP', can control how the high-order
+ * `subreg's of `mem' When M2 is smaller than a word, the
+ macro `LOAD_EXTEND_OP', can control how the high-order
bits are defined.
- * 'subreg' of 'reg's The upper bits are defined when
- 'SUBREG_PROMOTED_VAR_P' is true.
- 'SUBREG_PROMOTED_UNSIGNED_P' describes what the upper
+ * `subreg' of `reg's The upper bits are defined when
+ `SUBREG_PROMOTED_VAR_P' is true.
+ `SUBREG_PROMOTED_UNSIGNED_P' describes what the upper
bits hold. Such subregs usually represent local
variables, register variables and parameter pseudo
variables that have been promoted to a wider mode.
- BYTENUM is always zero for a paradoxical 'subreg', even on
+
+ BYTENUM is always zero for a paradoxical `subreg', even on
big-endian targets.
- For example, the paradoxical 'subreg':
+ For example, the paradoxical `subreg':
(set (subreg:SI (reg:HI X) 0) Y)
@@ -15304,126 +15453,128 @@ registers and to main memory.
(set Z (subreg:SI (reg:HI X) 0))
would set the lower two bytes of Z to Y and set the upper two
- bytes to an unknown value assuming 'SUBREG_PROMOTED_VAR_P' is
+ bytes to an unknown value assuming `SUBREG_PROMOTED_VAR_P' is
false.
- Normal subregs
- When M1 is at least as narrow as M2 the 'subreg' expression is
- called "normal".
+ Normal subregs
+ When M1 is at least as narrow as M2 the `subreg' expression
+ is called "normal".
- Normal 'subreg's restrict consideration to certain bits of
+ Normal `subreg's restrict consideration to certain bits of
REG. There are two cases. If M1 is smaller than a word, the
- 'subreg' refers to the least-significant part (or "lowpart")
+ `subreg' refers to the least-significant part (or "lowpart")
of one word of REG. If M1 is word-sized or greater, the
- 'subreg' refers to one or more complete words.
+ `subreg' refers to one or more complete words.
- When used as an lvalue, 'subreg' is a word-based accessor.
- Storing to a 'subreg' modifies all the words of REG that
- overlap the 'subreg', but it leaves the other words of REG
+ When used as an lvalue, `subreg' is a word-based accessor.
+ Storing to a `subreg' modifies all the words of REG that
+ overlap the `subreg', but it leaves the other words of REG
alone.
- When storing to a normal 'subreg' that is smaller than a word,
+ When storing to a normal `subreg' that is smaller than a word,
the other bits of the referenced word are usually left in an
undefined state. This laxity makes it easier to generate
efficient code for such instructions. To represent an
instruction that preserves all the bits outside of those in
- the 'subreg', use 'strict_low_part' or 'zero_extract' around
- the 'subreg'.
+ the `subreg', use `strict_low_part' or `zero_extract' around
+ the `subreg'.
BYTENUM must identify the offset of the first byte of the
- 'subreg' from the start of REG, assuming that REG is laid out
+ `subreg' from the start of REG, assuming that REG is laid out
in memory order. The memory order of bytes is defined by two
- target macros, 'WORDS_BIG_ENDIAN' and 'BYTES_BIG_ENDIAN':
+ target macros, `WORDS_BIG_ENDIAN' and `BYTES_BIG_ENDIAN':
- * 'WORDS_BIG_ENDIAN', if set to 1, says that byte number
+ * `WORDS_BIG_ENDIAN', if set to 1, says that byte number
zero is part of the most significant word; otherwise, it
is part of the least significant word.
- * 'BYTES_BIG_ENDIAN', if set to 1, says that byte number
+ * `BYTES_BIG_ENDIAN', if set to 1, says that byte number
zero is the most significant byte within a word;
otherwise, it is the least significant byte within a
word.
- On a few targets, 'FLOAT_WORDS_BIG_ENDIAN' disagrees with
- 'WORDS_BIG_ENDIAN'. However, most parts of the compiler treat
+ On a few targets, `FLOAT_WORDS_BIG_ENDIAN' disagrees with
+ `WORDS_BIG_ENDIAN'. However, most parts of the compiler treat
floating point values as if they had the same endianness as
- integer values. This works because they handle them solely as
- a collection of integer values, with no particular numerical
- value. Only real.c and the runtime libraries care about
- 'FLOAT_WORDS_BIG_ENDIAN'.
+ integer values. This works because they handle them solely
+ as a collection of integer values, with no particular
+ numerical value. Only real.c and the runtime libraries care
+ about `FLOAT_WORDS_BIG_ENDIAN'.
Thus,
(subreg:HI (reg:SI X) 2)
- on a 'BYTES_BIG_ENDIAN', 'UNITS_PER_WORD == 4' target is the
+ on a `BYTES_BIG_ENDIAN', `UNITS_PER_WORD == 4' target is the
same as
(subreg:HI (reg:SI X) 0)
- on a little-endian, 'UNITS_PER_WORD == 4' target. Both
- 'subreg's access the lower two bytes of register X.
+ on a little-endian, `UNITS_PER_WORD == 4' target. Both
+ `subreg's access the lower two bytes of register X.
- A 'MODE_PARTIAL_INT' mode behaves as if it were as wide as the
- corresponding 'MODE_INT' mode, except that it has an unknown number
- of undefined bits. For example:
+
+ A `MODE_PARTIAL_INT' mode behaves as if it were as wide as the
+ corresponding `MODE_INT' mode, except that it has an unknown
+ number of undefined bits. For example:
(subreg:PSI (reg:SI 0) 0)
- accesses the whole of '(reg:SI 0)', but the exact relationship
- between the 'PSImode' value and the 'SImode' value is not defined.
- If we assume 'UNITS_PER_WORD <= 4', then the following two
- 'subreg's:
+ accesses the whole of `(reg:SI 0)', but the exact relationship
+ between the `PSImode' value and the `SImode' value is not defined.
+ If we assume `UNITS_PER_WORD <= 4', then the following two
+ `subreg's:
(subreg:PSI (reg:DI 0) 0)
(subreg:PSI (reg:DI 0) 4)
- represent independent 4-byte accesses to the two halves of '(reg:DI
- 0)'. Both 'subreg's have an unknown number of undefined bits.
+ represent independent 4-byte accesses to the two halves of
+ `(reg:DI 0)'. Both `subreg's have an unknown number of undefined
+ bits.
- If 'UNITS_PER_WORD <= 2' then these two 'subreg's:
+ If `UNITS_PER_WORD <= 2' then these two `subreg's:
(subreg:HI (reg:PSI 0) 0)
(subreg:HI (reg:PSI 0) 2)
represent independent 2-byte accesses that together span the whole
- of '(reg:PSI 0)'. Storing to the first 'subreg' does not affect
- the value of the second, and vice versa. '(reg:PSI 0)' has an
+ of `(reg:PSI 0)'. Storing to the first `subreg' does not affect
+ the value of the second, and vice versa. `(reg:PSI 0)' has an
unknown number of undefined bits, so the assignment:
(set (subreg:HI (reg:PSI 0) 0) (reg:HI 4))
- does not guarantee that '(subreg:HI (reg:PSI 0) 0)' has the value
- '(reg:HI 4)'.
+ does not guarantee that `(subreg:HI (reg:PSI 0) 0)' has the value
+ `(reg:HI 4)'.
The rules above apply to both pseudo REGs and hard REGs. If the
- semantics are not correct for particular combinations of M1, M2 and
- hard REG, the target-specific code must ensure that those
+ semantics are not correct for particular combinations of M1, M2
+ and hard REG, the target-specific code must ensure that those
combinations are never used. For example:
CANNOT_CHANGE_MODE_CLASS (M2, M1, CLASS)
must be true for every class CLASS that includes REG.
- The first operand of a 'subreg' expression is customarily accessed
- with the 'SUBREG_REG' macro and the second operand is customarily
- accessed with the 'SUBREG_BYTE' macro.
+ The first operand of a `subreg' expression is customarily accessed
+ with the `SUBREG_REG' macro and the second operand is customarily
+ accessed with the `SUBREG_BYTE' macro.
It has been several years since a platform in which
- 'BYTES_BIG_ENDIAN' not equal to 'WORDS_BIG_ENDIAN' has been tested.
- Anyone wishing to support such a platform in the future may be
- confronted with code rot.
+ `BYTES_BIG_ENDIAN' not equal to `WORDS_BIG_ENDIAN' has been
+ tested. Anyone wishing to support such a platform in the future
+ may be confronted with code rot.
-'(scratch:M)'
+`(scratch:M)'
This represents a scratch register that will be required for the
execution of a single instruction and not used subsequently. It is
- converted into a 'reg' by either the local register allocator or
+ converted into a `reg' by either the local register allocator or
the reload pass.
- 'scratch' is usually present inside a 'clobber' operation (*note
+ `scratch' is usually present inside a `clobber' operation (*note
Side Effects::).
-'(cc0)'
+`(cc0)'
This refers to the machine's condition code register. It has no
operands and may not have a machine mode. There are two ways to
use it:
@@ -15432,39 +15583,39 @@ registers and to main memory.
best on most machines, where each comparison sets the entire
series of flags.
- With this technique, '(cc0)' may be validly used in only two
+ With this technique, `(cc0)' may be validly used in only two
contexts: as the destination of an assignment (in test and
compare instructions) and in comparison operators comparing
- against zero ('const_int' with value zero; that is to say,
- 'const0_rtx').
+ against zero (`const_int' with value zero; that is to say,
+ `const0_rtx').
* To stand for a single flag that is the result of a single
- condition. This is useful on machines that have only a single
- flag bit, and in which comparison instructions must specify
- the condition to test.
+ condition. This is useful on machines that have only a
+ single flag bit, and in which comparison instructions must
+ specify the condition to test.
- With this technique, '(cc0)' may be validly used in only two
+ With this technique, `(cc0)' may be validly used in only two
contexts: as the destination of an assignment (in test and
compare instructions) where the source is a comparison
- operator, and as the first operand of 'if_then_else' (in a
+ operator, and as the first operand of `if_then_else' (in a
conditional branch).
- There is only one expression object of code 'cc0'; it is the value
- of the variable 'cc0_rtx'. Any attempt to create an expression of
- code 'cc0' will return 'cc0_rtx'.
+ There is only one expression object of code `cc0'; it is the value
+ of the variable `cc0_rtx'. Any attempt to create an expression of
+ code `cc0' will return `cc0_rtx'.
Instructions can set the condition code implicitly. On many
machines, nearly all instructions set the condition code based on
the value that they compute or store. It is not necessary to
record these actions explicitly in the RTL because the machine
description includes a prescription for recognizing the
- instructions that do so (by means of the macro 'NOTICE_UPDATE_CC').
- *Note Condition Code::. Only instructions whose sole purpose is to
- set the condition code, and instructions that use the condition
- code, need mention '(cc0)'.
+ instructions that do so (by means of the macro
+ `NOTICE_UPDATE_CC'). *Note Condition Code::. Only instructions
+ whose sole purpose is to set the condition code, and instructions
+ that use the condition code, need mention `(cc0)'.
On some machines, the condition code register is given a register
- number and a 'reg' is used instead of '(cc0)'. This is usually the
+ number and a `reg' is used instead of `(cc0)'. This is usually the
preferable approach if only a small subset of instructions modify
the condition code. Other machines store condition codes in
general registers; in such cases a pseudo register should be used.
@@ -15474,42 +15625,42 @@ registers and to main memory.
the condition code. This is best handled by normally generating
the instruction that does not set the condition code, and making a
pattern that both performs the arithmetic and sets the condition
- code register (which would not be '(cc0)' in this case). For
- examples, search for 'addcc' and 'andcc' in 'sparc.md'.
+ code register (which would not be `(cc0)' in this case). For
+ examples, search for `addcc' and `andcc' in `sparc.md'.
-'(pc)'
+`(pc)'
This represents the machine's program counter. It has no operands
- and may not have a machine mode. '(pc)' may be validly used only
+ and may not have a machine mode. `(pc)' may be validly used only
in certain specific contexts in jump instructions.
- There is only one expression object of code 'pc'; it is the value
- of the variable 'pc_rtx'. Any attempt to create an expression of
- code 'pc' will return 'pc_rtx'.
+ There is only one expression object of code `pc'; it is the value
+ of the variable `pc_rtx'. Any attempt to create an expression of
+ code `pc' will return `pc_rtx'.
All instructions that do not jump alter the program counter
- implicitly by incrementing it, but there is no need to mention this
- in the RTL.
+ implicitly by incrementing it, but there is no need to mention
+ this in the RTL.
-'(mem:M ADDR ALIAS)'
+`(mem:M ADDR ALIAS)'
This RTX represents a reference to main memory at an address
represented by the expression ADDR. M specifies how large a unit
of memory is accessed. ALIAS specifies an alias set for the
reference. In general two items are in different alias sets if
they cannot reference the same memory address.
- The construct '(mem:BLK (scratch))' is considered to alias all
+ The construct `(mem:BLK (scratch))' is considered to alias all
other memories. Thus it may be used as a memory barrier in
epilogue stack deallocation patterns.
-'(concatM RTX RTX)'
+`(concatM RTX RTX)'
This RTX represents the concatenation of two other RTXs. This is
- used for complex values. It should only appear in the RTL attached
- to declarations and during RTL generation. It should not appear in
- the ordinary insn chain.
+ used for complex values. It should only appear in the RTL
+ attached to declarations and during RTL generation. It should not
+ appear in the ordinary insn chain.
-'(concatnM [RTX ...])'
+`(concatnM [RTX ...])'
This RTX represents the concatenation of all the RTX to make a
- single value. Like 'concat', this should only appear in
+ single value. Like `concat', this should only appear in
declarations, and not in the insn chain.

@@ -15519,99 +15670,98 @@ File: gccint.info, Node: Arithmetic, Next: Comparisons, Prev: Regs and Memory
===================================
Unless otherwise specified, all the operands of arithmetic expressions
-must be valid for mode M. An operand is valid for mode M if it has mode
-M, or if it is a 'const_int' or 'const_double' and M is a mode of class
-'MODE_INT'.
+must be valid for mode M. An operand is valid for mode M if it has
+mode M, or if it is a `const_int' or `const_double' and M is a mode of
+class `MODE_INT'.
For commutative binary operations, constants should be placed in the
second operand.
-'(plus:M X Y)'
-'(ss_plus:M X Y)'
-'(us_plus:M X Y)'
-
+`(plus:M X Y)'
+`(ss_plus:M X Y)'
+`(us_plus:M X Y)'
These three expressions all represent the sum of the values
represented by X and Y carried out in machine mode M. They differ
- in their behavior on overflow of integer modes. 'plus' wraps round
- modulo the width of M; 'ss_plus' saturates at the maximum signed
- value representable in M; 'us_plus' saturates at the maximum
- unsigned value.
-
-'(lo_sum:M X Y)'
+ in their behavior on overflow of integer modes. `plus' wraps
+ round modulo the width of M; `ss_plus' saturates at the maximum
+ signed value representable in M; `us_plus' saturates at the
+ maximum unsigned value.
+`(lo_sum:M X Y)'
This expression represents the sum of X and the low-order bits of
- Y. It is used with 'high' (*note Constants::) to represent the
- typical two-instruction sequence used in RISC machines to reference
- a global memory location.
+ Y. It is used with `high' (*note Constants::) to represent the
+ typical two-instruction sequence used in RISC machines to
+ reference a global memory location.
The number of low order bits is machine-dependent but is normally
- the number of bits in a 'Pmode' item minus the number of bits set
- by 'high'.
-
- M should be 'Pmode'.
+ the number of bits in a `Pmode' item minus the number of bits set
+ by `high'.
-'(minus:M X Y)'
-'(ss_minus:M X Y)'
-'(us_minus:M X Y)'
+ M should be `Pmode'.
+`(minus:M X Y)'
+`(ss_minus:M X Y)'
+`(us_minus:M X Y)'
These three expressions represent the result of subtracting Y from
X, carried out in mode M. Behavior on overflow is the same as for
- the three variants of 'plus' (see above).
+ the three variants of `plus' (see above).
-'(compare:M X Y)'
+`(compare:M X Y)'
Represents the result of subtracting Y from X for purposes of
comparison. The result is computed without overflow, as if with
infinite precision.
Of course, machines can't really subtract with infinite precision.
- However, they can pretend to do so when only the sign of the result
- will be used, which is the case when the result is stored in the
- condition code. And that is the _only_ way this kind of expression
- may validly be used: as a value to be stored in the condition
- codes, either '(cc0)' or a register. *Note Comparisons::.
+ However, they can pretend to do so when only the sign of the
+ result will be used, which is the case when the result is stored
+ in the condition code. And that is the _only_ way this kind of
+ expression may validly be used: as a value to be stored in the
+ condition codes, either `(cc0)' or a register. *Note
+ Comparisons::.
The mode M is not related to the modes of X and Y, but instead is
- the mode of the condition code value. If '(cc0)' is used, it is
- 'VOIDmode'. Otherwise it is some mode in class 'MODE_CC', often
- 'CCmode'. *Note Condition Code::. If M is 'VOIDmode' or 'CCmode',
- the operation returns sufficient information (in an unspecified
- format) so that any comparison operator can be applied to the
- result of the 'COMPARE' operation. For other modes in class
- 'MODE_CC', the operation only returns a subset of this information.
-
- Normally, X and Y must have the same mode. Otherwise, 'compare' is
- valid only if the mode of X is in class 'MODE_INT' and Y is a
- 'const_int' or 'const_double' with mode 'VOIDmode'. The mode of X
+ the mode of the condition code value. If `(cc0)' is used, it is
+ `VOIDmode'. Otherwise it is some mode in class `MODE_CC', often
+ `CCmode'. *Note Condition Code::. If M is `VOIDmode' or
+ `CCmode', the operation returns sufficient information (in an
+ unspecified format) so that any comparison operator can be applied
+ to the result of the `COMPARE' operation. For other modes in
+ class `MODE_CC', the operation only returns a subset of this
+ information.
+
+ Normally, X and Y must have the same mode. Otherwise, `compare'
+ is valid only if the mode of X is in class `MODE_INT' and Y is a
+ `const_int' or `const_double' with mode `VOIDmode'. The mode of X
determines what mode the comparison is to be done in; thus it must
- not be 'VOIDmode'.
+ not be `VOIDmode'.
If one of the operands is a constant, it should be placed in the
second operand and the comparison code adjusted as appropriate.
- A 'compare' specifying two 'VOIDmode' constants is not valid since
+ A `compare' specifying two `VOIDmode' constants is not valid since
there is no way to know in what mode the comparison is to be
performed; the comparison must either be folded during the
compilation or the first operand must be loaded into a register
while its mode is still known.
-'(neg:M X)'
-'(ss_neg:M X)'
-'(us_neg:M X)'
+`(neg:M X)'
+`(ss_neg:M X)'
+`(us_neg:M X)'
These two expressions represent the negation (subtraction from
zero) of the value represented by X, carried out in mode M. They
differ in the behavior on overflow of integer modes. In the case
- of 'neg', the negation of the operand may be a number not
+ of `neg', the negation of the operand may be a number not
representable in mode M, in which case it is truncated to M.
- 'ss_neg' and 'us_neg' ensure that an out-of-bounds result saturates
- to the maximum or minimum signed or unsigned value.
+ `ss_neg' and `us_neg' ensure that an out-of-bounds result
+ saturates to the maximum or minimum signed or unsigned value.
-'(mult:M X Y)'
-'(ss_mult:M X Y)'
-'(us_mult:M X Y)'
+`(mult:M X Y)'
+`(ss_mult:M X Y)'
+`(us_mult:M X Y)'
Represents the signed product of the values represented by X and Y
- carried out in machine mode M. 'ss_mult' and 'us_mult' ensure that
- an out-of-bounds result saturates to the maximum or minimum signed
- or unsigned value.
+ carried out in machine mode M. `ss_mult' and `us_mult' ensure
+ that an out-of-bounds result saturates to the maximum or minimum
+ signed or unsigned value.
Some machines support a multiplication that generates a product
wider than the operands. Write the pattern for this as
@@ -15622,146 +15772,147 @@ second operand.
same.
For unsigned widening multiplication, use the same idiom, but with
- 'zero_extend' instead of 'sign_extend'.
+ `zero_extend' instead of `sign_extend'.
-'(fma:M X Y Z)'
- Represents the 'fma', 'fmaf', and 'fmal' builtin functions, which
- compute 'X * Y + Z' without doing an intermediate rounding step.
+`(fma:M X Y Z)'
+ Represents the `fma', `fmaf', and `fmal' builtin functions, which
+ compute `X * Y + Z' without doing an intermediate rounding step.
-'(div:M X Y)'
-'(ss_div:M X Y)'
+`(div:M X Y)'
+`(ss_div:M X Y)'
Represents the quotient in signed division of X by Y, carried out
in machine mode M. If M is a floating point mode, it represents
- the exact quotient; otherwise, the integerized quotient. 'ss_div'
+ the exact quotient; otherwise, the integerized quotient. `ss_div'
ensures that an out-of-bounds result saturates to the maximum or
minimum signed value.
Some machines have division instructions in which the operands and
quotient widths are not all the same; you should represent such
- instructions using 'truncate' and 'sign_extend' as in,
+ instructions using `truncate' and `sign_extend' as in,
(truncate:M1 (div:M2 X (sign_extend:M2 Y)))
-'(udiv:M X Y)'
-'(us_div:M X Y)'
- Like 'div' but represents unsigned division. 'us_div' ensures that
- an out-of-bounds result saturates to the maximum or minimum
+`(udiv:M X Y)'
+`(us_div:M X Y)'
+ Like `div' but represents unsigned division. `us_div' ensures
+ that an out-of-bounds result saturates to the maximum or minimum
unsigned value.
-'(mod:M X Y)'
-'(umod:M X Y)'
- Like 'div' and 'udiv' but represent the remainder instead of the
+`(mod:M X Y)'
+`(umod:M X Y)'
+ Like `div' and `udiv' but represent the remainder instead of the
quotient.
-'(smin:M X Y)'
-'(smax:M X Y)'
- Represents the smaller (for 'smin') or larger (for 'smax') of X and
- Y, interpreted as signed values in mode M. When used with floating
- point, if both operands are zeros, or if either operand is 'NaN',
- then it is unspecified which of the two operands is returned as the
- result.
-
-'(umin:M X Y)'
-'(umax:M X Y)'
- Like 'smin' and 'smax', but the values are interpreted as unsigned
+`(smin:M X Y)'
+`(smax:M X Y)'
+ Represents the smaller (for `smin') or larger (for `smax') of X
+ and Y, interpreted as signed values in mode M. When used with
+ floating point, if both operands are zeros, or if either operand
+ is `NaN', then it is unspecified which of the two operands is
+ returned as the result.
+
+`(umin:M X Y)'
+`(umax:M X Y)'
+ Like `smin' and `smax', but the values are interpreted as unsigned
integers.
-'(not:M X)'
+`(not:M X)'
Represents the bitwise complement of the value represented by X,
carried out in mode M, which must be a fixed-point machine mode.
-'(and:M X Y)'
+`(and:M X Y)'
Represents the bitwise logical-and of the values represented by X
and Y, carried out in machine mode M, which must be a fixed-point
machine mode.
-'(ior:M X Y)'
+`(ior:M X Y)'
Represents the bitwise inclusive-or of the values represented by X
and Y, carried out in machine mode M, which must be a fixed-point
mode.
-'(xor:M X Y)'
+`(xor:M X Y)'
Represents the bitwise exclusive-or of the values represented by X
and Y, carried out in machine mode M, which must be a fixed-point
mode.
-'(ashift:M X C)'
-'(ss_ashift:M X C)'
-'(us_ashift:M X C)'
+`(ashift:M X C)'
+`(ss_ashift:M X C)'
+`(us_ashift:M X C)'
These three expressions represent the result of arithmetically
shifting X left by C places. They differ in their behavior on
- overflow of integer modes. An 'ashift' operation is a plain shift
+ overflow of integer modes. An `ashift' operation is a plain shift
with no special behavior in case of a change in the sign bit;
- 'ss_ashift' and 'us_ashift' saturates to the minimum or maximum
- representable value if any of the bits shifted out differs from the
- final sign bit.
-
- X have mode M, a fixed-point machine mode. C be a fixed-point mode
- or be a constant with mode 'VOIDmode'; which mode is determined by
- the mode called for in the machine description entry for the
- left-shift instruction. For example, on the VAX, the mode of C is
- 'QImode' regardless of M.
-
-'(lshiftrt:M X C)'
-'(ashiftrt:M X C)'
- Like 'ashift' but for right shift. Unlike the case for left shift,
+ `ss_ashift' and `us_ashift' saturates to the minimum or maximum
+ representable value if any of the bits shifted out differs from
+ the final sign bit.
+
+ X have mode M, a fixed-point machine mode. C be a fixed-point
+ mode or be a constant with mode `VOIDmode'; which mode is
+ determined by the mode called for in the machine description entry
+ for the left-shift instruction. For example, on the VAX, the mode
+ of C is `QImode' regardless of M.
+
+`(lshiftrt:M X C)'
+`(ashiftrt:M X C)'
+ Like `ashift' but for right shift. Unlike the case for left shift,
these two operations are distinct.
-'(rotate:M X C)'
-'(rotatert:M X C)'
+`(rotate:M X C)'
+`(rotatert:M X C)'
Similar but represent left and right rotate. If C is a constant,
- use 'rotate'.
+ use `rotate'.
+
+`(abs:M X)'
-'(abs:M X)'
-'(ss_abs:M X)'
- Represents the absolute value of X, computed in mode M. 'ss_abs'
+`(ss_abs:M X)'
+ Represents the absolute value of X, computed in mode M. `ss_abs'
ensures that an out-of-bounds result saturates to the maximum
signed value.
-'(sqrt:M X)'
+`(sqrt:M X)'
Represents the square root of X, computed in mode M. Most often M
will be a floating point mode.
-'(ffs:M X)'
+`(ffs:M X)'
Represents one plus the index of the least significant 1-bit in X,
represented as an integer of mode M. (The value is zero if X is
- zero.) The mode of X must be M or 'VOIDmode'.
+ zero.) The mode of X must be M or `VOIDmode'.
-'(clrsb:M X)'
+`(clrsb:M X)'
Represents the number of redundant leading sign bits in X,
represented as an integer of mode M, starting at the most
significant bit position. This is one less than the number of
- leading sign bits (either 0 or 1), with no special cases. The mode
- of X must be M or 'VOIDmode'.
+ leading sign bits (either 0 or 1), with no special cases. The
+ mode of X must be M or `VOIDmode'.
-'(clz:M X)'
+`(clz:M X)'
Represents the number of leading 0-bits in X, represented as an
integer of mode M, starting at the most significant bit position.
If X is zero, the value is determined by
- 'CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Note that this is one
+ `CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Note that this is one
of the few expressions that is not invariant under widening. The
- mode of X must be M or 'VOIDmode'.
+ mode of X must be M or `VOIDmode'.
-'(ctz:M X)'
+`(ctz:M X)'
Represents the number of trailing 0-bits in X, represented as an
integer of mode M, starting at the least significant bit position.
If X is zero, the value is determined by
- 'CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Except for this case,
- 'ctz(x)' is equivalent to 'ffs(X) - 1'. The mode of X must be M or
- 'VOIDmode'.
+ `CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Except for this case,
+ `ctz(x)' is equivalent to `ffs(X) - 1'. The mode of X must be M
+ or `VOIDmode'.
-'(popcount:M X)'
+`(popcount:M X)'
Represents the number of 1-bits in X, represented as an integer of
- mode M. The mode of X must be M or 'VOIDmode'.
+ mode M. The mode of X must be M or `VOIDmode'.
-'(parity:M X)'
+`(parity:M X)'
Represents the number of 1-bits modulo 2 in X, represented as an
- integer of mode M. The mode of X must be M or 'VOIDmode'.
+ integer of mode M. The mode of X must be M or `VOIDmode'.
-'(bswap:M X)'
+`(bswap:M X)'
Represents the value X with the order of bytes reversed, carried
out in mode M, which must be a fixed-point machine mode. The mode
- of X must be M or 'VOIDmode'.
+ of X must be M or `VOIDmode'.

File: gccint.info, Node: Comparisons, Next: Bit-Fields, Prev: Arithmetic, Up: RTL
@@ -15771,25 +15922,25 @@ File: gccint.info, Node: Comparisons, Next: Bit-Fields, Prev: Arithmetic, Up
Comparison operators test a relation on two operands and are considered
to represent a machine-dependent nonzero value described by, but not
-necessarily equal to, 'STORE_FLAG_VALUE' (*note Misc::) if the relation
+necessarily equal to, `STORE_FLAG_VALUE' (*note Misc::) if the relation
holds, or zero if it does not, for comparison operators whose results
-have a 'MODE_INT' mode, 'FLOAT_STORE_FLAG_VALUE' (*note Misc::) if the
+have a `MODE_INT' mode, `FLOAT_STORE_FLAG_VALUE' (*note Misc::) if the
relation holds, or zero if it does not, for comparison operators that
return floating-point values, and a vector of either
-'VECTOR_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or of
+`VECTOR_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or of
zeros if it does not, for comparison operators that return vector
results. The mode of the comparison operation is independent of the
mode of the data being compared. If the comparison operation is being
-tested (e.g., the first operand of an 'if_then_else'), the mode must be
-'VOIDmode'.
+tested (e.g., the first operand of an `if_then_else'), the mode must be
+`VOIDmode'.
There are two ways that comparison operations may be used. The
-comparison operators may be used to compare the condition codes '(cc0)'
-against zero, as in '(eq (cc0) (const_int 0))'. Such a construct
+comparison operators may be used to compare the condition codes `(cc0)'
+against zero, as in `(eq (cc0) (const_int 0))'. Such a construct
actually refers to the result of the preceding instruction in which the
condition codes were set. The instruction setting the condition code
must be adjacent to the instruction using the condition code; only
-'note' insns may separate them.
+`note' insns may separate them.
Alternatively, a comparison operation may directly compare two data
objects. The mode of the comparison is determined by the operands; they
@@ -15798,66 +15949,66 @@ operands constant would be invalid as the machine mode could not be
deduced from it, but such a comparison should never exist in RTL due to
constant folding.
- In the example above, if '(cc0)' were last set to '(compare X Y)', the
-comparison operation is identical to '(eq X Y)'. Usually only one style
+ In the example above, if `(cc0)' were last set to `(compare X Y)', the
+comparison operation is identical to `(eq X Y)'. Usually only one style
of comparisons is supported on a particular machine, but the combine
-pass will try to merge the operations to produce the 'eq' shown in case
+pass will try to merge the operations to produce the `eq' shown in case
it exists in the context of the particular insn involved.
Inequality comparisons come in two flavors, signed and unsigned. Thus,
-there are distinct expression codes 'gt' and 'gtu' for signed and
+there are distinct expression codes `gt' and `gtu' for signed and
unsigned greater-than. These can produce different results for the same
pair of integer values: for example, 1 is signed greater-than -1 but not
unsigned greater-than, because -1 when regarded as unsigned is actually
-'0xffffffff' which is greater than 1.
+`0xffffffff' which is greater than 1.
The signed comparisons are also used for floating point values.
-Floating point comparisons are distinguished by the machine modes of the
-operands.
+Floating point comparisons are distinguished by the machine modes of
+the operands.
-'(eq:M X Y)'
- 'STORE_FLAG_VALUE' if the values represented by X and Y are equal,
+`(eq:M X Y)'
+ `STORE_FLAG_VALUE' if the values represented by X and Y are equal,
otherwise 0.
-'(ne:M X Y)'
- 'STORE_FLAG_VALUE' if the values represented by X and Y are not
+`(ne:M X Y)'
+ `STORE_FLAG_VALUE' if the values represented by X and Y are not
equal, otherwise 0.
-'(gt:M X Y)'
- 'STORE_FLAG_VALUE' if the X is greater than Y. If they are
+`(gt:M X Y)'
+ `STORE_FLAG_VALUE' if the X is greater than Y. If they are
fixed-point, the comparison is done in a signed sense.
-'(gtu:M X Y)'
- Like 'gt' but does unsigned comparison, on fixed-point numbers
+`(gtu:M X Y)'
+ Like `gt' but does unsigned comparison, on fixed-point numbers
only.
-'(lt:M X Y)'
-'(ltu:M X Y)'
- Like 'gt' and 'gtu' but test for "less than".
+`(lt:M X Y)'
+`(ltu:M X Y)'
+ Like `gt' and `gtu' but test for "less than".
-'(ge:M X Y)'
-'(geu:M X Y)'
- Like 'gt' and 'gtu' but test for "greater than or equal".
+`(ge:M X Y)'
+`(geu:M X Y)'
+ Like `gt' and `gtu' but test for "greater than or equal".
-'(le:M X Y)'
-'(leu:M X Y)'
- Like 'gt' and 'gtu' but test for "less than or equal".
+`(le:M X Y)'
+`(leu:M X Y)'
+ Like `gt' and `gtu' but test for "less than or equal".
-'(if_then_else COND THEN ELSE)'
+`(if_then_else COND THEN ELSE)'
This is not a comparison operation but is listed here because it is
always used in conjunction with a comparison operation. To be
precise, COND is a comparison expression. This expression
represents a choice, according to COND, between the value
represented by THEN and the one represented by ELSE.
- On most machines, 'if_then_else' expressions are valid only to
+ On most machines, `if_then_else' expressions are valid only to
express conditional jumps.
-'(cond [TEST1 VALUE1 TEST2 VALUE2 ...] DEFAULT)'
- Similar to 'if_then_else', but more general. Each of TEST1, TEST2,
- ... is performed in turn. The result of this expression is the
- VALUE corresponding to the first nonzero test, or DEFAULT if none
- of the tests are nonzero expressions.
+`(cond [TEST1 VALUE1 TEST2 VALUE2 ...] DEFAULT)'
+ Similar to `if_then_else', but more general. Each of TEST1,
+ TEST2, ... is performed in turn. The result of this expression is
+ the VALUE corresponding to the first nonzero test, or DEFAULT if
+ none of the tests are nonzero expressions.
This is currently not valid for instruction patterns and is
supported only for insn attributes. *Note Insn Attributes::.
@@ -15870,34 +16021,34 @@ File: gccint.info, Node: Bit-Fields, Next: Vector Operations, Prev: Compariso
Special expression codes exist to represent bit-field instructions.
-'(sign_extract:M LOC SIZE POS)'
+`(sign_extract:M LOC SIZE POS)'
This represents a reference to a sign-extended bit-field contained
or starting in LOC (a memory or register reference). The bit-field
is SIZE bits wide and starts at bit POS. The compilation option
- 'BITS_BIG_ENDIAN' says which end of the memory unit POS counts
+ `BITS_BIG_ENDIAN' says which end of the memory unit POS counts
from.
If LOC is in memory, its mode must be a single-byte integer mode.
If LOC is in a register, the mode to use is specified by the
- operand of the 'insv' or 'extv' pattern (*note Standard Names::)
+ operand of the `insv' or `extv' pattern (*note Standard Names::)
and is usually a full-word integer mode, which is the default if
none is specified.
The mode of POS is machine-specific and is also specified in the
- 'insv' or 'extv' pattern.
+ `insv' or `extv' pattern.
- The mode M is the same as the mode that would be used for LOC if it
- were a register.
+ The mode M is the same as the mode that would be used for LOC if
+ it were a register.
- A 'sign_extract' can not appear as an lvalue, or part thereof, in
+ A `sign_extract' can not appear as an lvalue, or part thereof, in
RTL.
-'(zero_extract:M LOC SIZE POS)'
- Like 'sign_extract' but refers to an unsigned or zero-extended
+`(zero_extract:M LOC SIZE POS)'
+ Like `sign_extract' but refers to an unsigned or zero-extended
bit-field. The same sequence of bits are extracted, but they are
filled to an entire word with zeros instead of by sign-extension.
- Unlike 'sign_extract', this type of expressions can be lvalues in
+ Unlike `sign_extract', this type of expressions can be lvalues in
RTL; they may appear on the left side of an assignment, indicating
insertion of a value into the specified bit-field.
@@ -15912,34 +16063,35 @@ interpreted as operating on each part of the vector independently.
Additionally, there are a few new expressions to describe specific
vector operations.
-'(vec_merge:M VEC1 VEC2 ITEMS)'
+`(vec_merge:M VEC1 VEC2 ITEMS)'
This describes a merge operation between two vectors. The result
is a vector of mode M; its elements are selected from either VEC1
or VEC2. Which elements are selected is described by ITEMS, which
- is a bit mask represented by a 'const_int'; a zero bit indicates
+ is a bit mask represented by a `const_int'; a zero bit indicates
the corresponding element in the result vector is taken from VEC2
while a set bit indicates it is taken from VEC1.
-'(vec_select:M VEC1 SELECTION)'
+`(vec_select:M VEC1 SELECTION)'
This describes an operation that selects parts of a vector. VEC1
- is the source vector, and SELECTION is a 'parallel' that contains a
- 'const_int' for each of the subparts of the result vector, giving
+ is the source vector, and SELECTION is a `parallel' that contains a
+ `const_int' for each of the subparts of the result vector, giving
the number of the source subpart that should be stored into it.
The result mode M is either the submode for a single element of
- VEC1 (if only one subpart is selected), or another vector mode with
- that element submode (if multiple subparts are selected).
+ VEC1 (if only one subpart is selected), or another vector mode
+ with that element submode (if multiple subparts are selected).
-'(vec_concat:M X1 X2)'
- Describes a vector concat operation. The result is a concatenation
- of the vectors or scalars X1 and X2; its length is the sum of the
- lengths of the two inputs.
+`(vec_concat:M X1 X2)'
+ Describes a vector concat operation. The result is a
+ concatenation of the vectors or scalars X1 and X2; its length is
+ the sum of the lengths of the two inputs.
-'(vec_duplicate:M X)'
+`(vec_duplicate:M X)'
This operation converts a scalar into a vector or a small vector
into a larger one by duplicating the input values. The output
- vector mode must have the same submodes as the input vector mode or
- the scalar modes, and the number of output parts must be an integer
- multiple of the number of input parts.
+ vector mode must have the same submodes as the input vector mode
+ or the scalar modes, and the number of output parts must be an
+ integer multiple of the number of input parts.
+

File: gccint.info, Node: Conversions, Next: RTL Declarations, Prev: Vector Operations, Up: RTL
@@ -15948,10 +16100,10 @@ File: gccint.info, Node: Conversions, Next: RTL Declarations, Prev: Vector Op
=================
All conversions between machine modes must be represented by explicit
-conversion operations. For example, an expression which is the sum of a
-byte and a full word cannot be written as '(plus:SI (reg:QI 34) (reg:SI
-80))' because the 'plus' operation requires two operands of the same
-machine mode. Therefore, the byte-sized operand is enclosed in a
+conversion operations. For example, an expression which is the sum of
+a byte and a full word cannot be written as `(plus:SI (reg:QI 34)
+(reg:SI 80))' because the `plus' operation requires two operands of the
+same machine mode. Therefore, the byte-sized operand is enclosed in a
conversion operation, as in
(plus:SI (sign_extend:SI (reg:QI 34)) (reg:SI 80))
@@ -15960,70 +16112,70 @@ conversion operation, as in
be more than one way of converting from a given starting mode to the
desired final mode. The conversion operation code says how to do it.
- For all conversion operations, X must not be 'VOIDmode' because the
+ For all conversion operations, X must not be `VOIDmode' because the
mode in which to do the conversion would not be known. The conversion
must either be done at compile-time or X must be placed into a register.
-'(sign_extend:M X)'
- Represents the result of sign-extending the value X to machine mode
- M. M must be a fixed-point mode and X a fixed-point value of a
- mode narrower than M.
+`(sign_extend:M X)'
+ Represents the result of sign-extending the value X to machine
+ mode M. M must be a fixed-point mode and X a fixed-point value of
+ a mode narrower than M.
-'(zero_extend:M X)'
- Represents the result of zero-extending the value X to machine mode
- M. M must be a fixed-point mode and X a fixed-point value of a
- mode narrower than M.
+`(zero_extend:M X)'
+ Represents the result of zero-extending the value X to machine
+ mode M. M must be a fixed-point mode and X a fixed-point value of
+ a mode narrower than M.
-'(float_extend:M X)'
+`(float_extend:M X)'
Represents the result of extending the value X to machine mode M.
M must be a floating point mode and X a floating point value of a
mode narrower than M.
-'(truncate:M X)'
+`(truncate:M X)'
Represents the result of truncating the value X to machine mode M.
M must be a fixed-point mode and X a fixed-point value of a mode
wider than M.
-'(ss_truncate:M X)'
+`(ss_truncate:M X)'
Represents the result of truncating the value X to machine mode M,
using signed saturation in the case of overflow. Both M and the
mode of X must be fixed-point modes.
-'(us_truncate:M X)'
+`(us_truncate:M X)'
Represents the result of truncating the value X to machine mode M,
using unsigned saturation in the case of overflow. Both M and the
mode of X must be fixed-point modes.
-'(float_truncate:M X)'
+`(float_truncate:M X)'
Represents the result of truncating the value X to machine mode M.
M must be a floating point mode and X a floating point value of a
mode wider than M.
-'(float:M X)'
+`(float:M X)'
Represents the result of converting fixed point value X, regarded
as signed, to floating point mode M.
-'(unsigned_float:M X)'
+`(unsigned_float:M X)'
Represents the result of converting fixed point value X, regarded
as unsigned, to floating point mode M.
-'(fix:M X)'
+`(fix:M X)'
When M is a floating-point mode, represents the result of
- converting floating point value X (valid for mode M) to an integer,
- still represented in floating point mode M, by rounding towards
- zero.
+ converting floating point value X (valid for mode M) to an
+ integer, still represented in floating point mode M, by rounding
+ towards zero.
When M is a fixed-point mode, represents the result of converting
- floating point value X to mode M, regarded as signed. How rounding
- is done is not specified, so this operation may be used validly in
- compiling C code only for integer-valued operands.
+ floating point value X to mode M, regarded as signed. How
+ rounding is done is not specified, so this operation may be used
+ validly in compiling C code only for integer-valued operands.
-'(unsigned_fix:M X)'
- Represents the result of converting floating point value X to fixed
- point mode M, regarded as unsigned. How rounding is done is not
- specified.
+`(unsigned_fix:M X)'
+ Represents the result of converting floating point value X to
+ fixed point mode M, regarded as unsigned. How rounding is done is
+ not specified.
-'(fract_convert:M X)'
+`(fract_convert:M X)'
Represents the result of converting fixed-point value X to
fixed-point mode M, signed integer value X to fixed-point mode M,
floating-point value X to fixed-point mode M, fixed-point value X
@@ -16031,20 +16183,20 @@ must either be done at compile-time or X must be placed into a register.
floating-point mode M. When overflows or underflows happen, the
results are undefined.
-'(sat_fract:M X)'
+`(sat_fract:M X)'
Represents the result of converting fixed-point value X to
fixed-point mode M, signed integer value X to fixed-point mode M,
- or floating-point value X to fixed-point mode M. When overflows or
- underflows happen, the results are saturated to the maximum or the
- minimum.
+ or floating-point value X to fixed-point mode M. When overflows
+ or underflows happen, the results are saturated to the maximum or
+ the minimum.
-'(unsigned_fract_convert:M X)'
+`(unsigned_fract_convert:M X)'
Represents the result of converting fixed-point value X to integer
mode M regarded as unsigned, or unsigned integer value X to
fixed-point mode M. When overflows or underflows happen, the
results are undefined.
-'(unsigned_sat_fract:M X)'
+`(unsigned_sat_fract:M X)'
Represents the result of converting unsigned integer value X to
fixed-point mode M. When overflows or underflows happen, the
results are saturated to the maximum or the minimum.
@@ -16058,13 +16210,13 @@ File: gccint.info, Node: RTL Declarations, Next: Side Effects, Prev: Conversi
Declaration expression codes do not represent arithmetic operations but
rather state assertions about their operands.
-'(strict_low_part (subreg:M (reg:N R) 0))'
+`(strict_low_part (subreg:M (reg:N R) 0))'
This expression code is used in only one context: as the
- destination operand of a 'set' expression. In addition, the
- operand of this expression must be a non-paradoxical 'subreg'
+ destination operand of a `set' expression. In addition, the
+ operand of this expression must be a non-paradoxical `subreg'
expression.
- The presence of 'strict_low_part' says that the part of the
+ The presence of `strict_low_part' says that the part of the
register which is meaningful in mode N, but is not part of mode M,
is not to be altered. Normally, an assignment to such a subreg is
allowed to have undefined effects on the rest of the register when
@@ -16085,125 +16237,125 @@ codes are used to represent side effects.
the codes described above, which represent values, appear only as the
operands of these.
-'(set LVAL X)'
+`(set LVAL X)'
Represents the action of storing the value of X into the place
represented by LVAL. LVAL must be an expression representing a
- place that can be stored in: 'reg' (or 'subreg', 'strict_low_part'
- or 'zero_extract'), 'mem', 'pc', 'parallel', or 'cc0'.
+ place that can be stored in: `reg' (or `subreg', `strict_low_part'
+ or `zero_extract'), `mem', `pc', `parallel', or `cc0'.
- If LVAL is a 'reg', 'subreg' or 'mem', it has a machine mode; then
+ If LVAL is a `reg', `subreg' or `mem', it has a machine mode; then
X must be valid for that mode.
- If LVAL is a 'reg' whose machine mode is less than the full width
+ If LVAL is a `reg' whose machine mode is less than the full width
of the register, then it means that the part of the register
specified by the machine mode is given the specified value and the
rest of the register receives an undefined value. Likewise, if
- LVAL is a 'subreg' whose machine mode is narrower than the mode of
+ LVAL is a `subreg' whose machine mode is narrower than the mode of
the register, the rest of the register can be changed in an
undefined way.
- If LVAL is a 'strict_low_part' of a subreg, then the part of the
- register specified by the machine mode of the 'subreg' is given the
- value X and the rest of the register is not changed.
+ If LVAL is a `strict_low_part' of a subreg, then the part of the
+ register specified by the machine mode of the `subreg' is given
+ the value X and the rest of the register is not changed.
- If LVAL is a 'zero_extract', then the referenced part of the
+ If LVAL is a `zero_extract', then the referenced part of the
bit-field (a memory or register reference) specified by the
- 'zero_extract' is given the value X and the rest of the bit-field
- is not changed. Note that 'sign_extract' can not appear in LVAL.
+ `zero_extract' is given the value X and the rest of the bit-field
+ is not changed. Note that `sign_extract' can not appear in LVAL.
- If LVAL is '(cc0)', it has no machine mode, and X may be either a
- 'compare' expression or a value that may have any mode. The latter
- case represents a "test" instruction. The expression '(set (cc0)
- (reg:M N))' is equivalent to '(set (cc0) (compare (reg:M N)
+ If LVAL is `(cc0)', it has no machine mode, and X may be either a
+ `compare' expression or a value that may have any mode. The
+ latter case represents a "test" instruction. The expression `(set
+ (cc0) (reg:M N))' is equivalent to `(set (cc0) (compare (reg:M N)
(const_int 0)))'. Use the former expression to save space during
the compilation.
- If LVAL is a 'parallel', it is used to represent the case of a
+ If LVAL is a `parallel', it is used to represent the case of a
function returning a structure in multiple registers. Each element
- of the 'parallel' is an 'expr_list' whose first operand is a 'reg'
- and whose second operand is a 'const_int' representing the offset
+ of the `parallel' is an `expr_list' whose first operand is a `reg'
+ and whose second operand is a `const_int' representing the offset
(in bytes) into the structure at which the data in that register
corresponds. The first element may be null to indicate that the
structure is also passed partly in memory.
- If LVAL is '(pc)', we have a jump instruction, and the
- possibilities for X are very limited. It may be a 'label_ref'
- expression (unconditional jump). It may be an 'if_then_else'
+ If LVAL is `(pc)', we have a jump instruction, and the
+ possibilities for X are very limited. It may be a `label_ref'
+ expression (unconditional jump). It may be an `if_then_else'
(conditional jump), in which case either the second or the third
- operand must be '(pc)' (for the case which does not jump) and the
- other of the two must be a 'label_ref' (for the case which does
- jump). X may also be a 'mem' or '(plus:SI (pc) Y)', where Y may be
- a 'reg' or a 'mem'; these unusual patterns are used to represent
- jumps through branch tables.
+ operand must be `(pc)' (for the case which does not jump) and the
+ other of the two must be a `label_ref' (for the case which does
+ jump). X may also be a `mem' or `(plus:SI (pc) Y)', where Y may
+ be a `reg' or a `mem'; these unusual patterns are used to
+ represent jumps through branch tables.
- If LVAL is neither '(cc0)' nor '(pc)', the mode of LVAL must not be
- 'VOIDmode' and the mode of X must be valid for the mode of LVAL.
+ If LVAL is neither `(cc0)' nor `(pc)', the mode of LVAL must not
+ be `VOIDmode' and the mode of X must be valid for the mode of LVAL.
- LVAL is customarily accessed with the 'SET_DEST' macro and X with
- the 'SET_SRC' macro.
+ LVAL is customarily accessed with the `SET_DEST' macro and X with
+ the `SET_SRC' macro.
-'(return)'
+`(return)'
As the sole expression in a pattern, represents a return from the
current function, on machines where this can be done with one
instruction, such as VAXen. On machines where a multi-instruction
"epilogue" must be executed in order to return from the function,
returning is done by jumping to a label which precedes the
- epilogue, and the 'return' expression code is never used.
+ epilogue, and the `return' expression code is never used.
- Inside an 'if_then_else' expression, represents the value to be
- placed in 'pc' to return to the caller.
+ Inside an `if_then_else' expression, represents the value to be
+ placed in `pc' to return to the caller.
- Note that an insn pattern of '(return)' is logically equivalent to
- '(set (pc) (return))', but the latter form is never used.
+ Note that an insn pattern of `(return)' is logically equivalent to
+ `(set (pc) (return))', but the latter form is never used.
-'(simple_return)'
- Like '(return)', but truly represents only a function return, while
- '(return)' may represent an insn that also performs other functions
- of the function epilogue. Like '(return)', this may also occur in
+`(simple_return)'
+ Like `(return)', but truly represents only a function return, while
+ `(return)' may represent an insn that also performs other functions
+ of the function epilogue. Like `(return)', this may also occur in
conditional jumps.
-'(call FUNCTION NARGS)'
- Represents a function call. FUNCTION is a 'mem' expression whose
+`(call FUNCTION NARGS)'
+ Represents a function call. FUNCTION is a `mem' expression whose
address is the address of the function to be called. NARGS is an
expression which can be used for two purposes: on some machines it
represents the number of bytes of stack argument; on others, it
represents the number of argument registers.
Each machine has a standard machine mode which FUNCTION must have.
- The machine description defines macro 'FUNCTION_MODE' to expand
+ The machine description defines macro `FUNCTION_MODE' to expand
into the requisite mode name. The purpose of this mode is to
specify what kind of addressing is allowed, on machines where the
allowed kinds of addressing depend on the machine mode being
addressed.
-'(clobber X)'
+`(clobber X)'
Represents the storing or possible storing of an unpredictable,
- undescribed value into X, which must be a 'reg', 'scratch',
- 'parallel' or 'mem' expression.
+ undescribed value into X, which must be a `reg', `scratch',
+ `parallel' or `mem' expression.
One place this is used is in string instructions that store
standard values into particular hard registers. It may not be
- worth the trouble to describe the values that are stored, but it is
- essential to inform the compiler that the registers will be
+ worth the trouble to describe the values that are stored, but it
+ is essential to inform the compiler that the registers will be
altered, lest it attempt to keep data in them across the string
instruction.
- If X is '(mem:BLK (const_int 0))' or '(mem:BLK (scratch))', it
+ If X is `(mem:BLK (const_int 0))' or `(mem:BLK (scratch))', it
means that all memory locations must be presumed clobbered. If X
- is a 'parallel', it has the same meaning as a 'parallel' in a 'set'
- expression.
-
- Note that the machine description classifies certain hard registers
- as "call-clobbered". All function call instructions are assumed by
- default to clobber these registers, so there is no need to use
- 'clobber' expressions to indicate this fact. Also, each function
- call is assumed to have the potential to alter any memory location,
- unless the function is declared 'const'.
-
- If the last group of expressions in a 'parallel' are each a
- 'clobber' expression whose arguments are 'reg' or 'match_scratch'
+ is a `parallel', it has the same meaning as a `parallel' in a
+ `set' expression.
+
+ Note that the machine description classifies certain hard
+ registers as "call-clobbered". All function call instructions are
+ assumed by default to clobber these registers, so there is no need
+ to use `clobber' expressions to indicate this fact. Also, each
+ function call is assumed to have the potential to alter any memory
+ location, unless the function is declared `const'.
+
+ If the last group of expressions in a `parallel' are each a
+ `clobber' expression whose arguments are `reg' or `match_scratch'
(*note RTL Template::) expressions, the combiner phase can add the
- appropriate 'clobber' expressions to an insn it has constructed
+ appropriate `clobber' expressions to an insn it has constructed
when doing so will cause a pattern to be matched.
This feature can be used, for example, on a machine that whose
@@ -16212,43 +16364,43 @@ operands of these.
register. Similarly, a combined instruction might require a
temporary register while the constituent instructions might not.
- When a 'clobber' expression for a register appears inside a
- 'parallel' with other side effects, the register allocator
+ When a `clobber' expression for a register appears inside a
+ `parallel' with other side effects, the register allocator
guarantees that the register is unoccupied both before and after
that insn if it is a hard register clobber. For pseudo-register
clobber, the register allocator and the reload pass do not assign
the same hard register to the clobber and the input operands if
- there is an insn alternative containing the '&' constraint (*note
+ there is an insn alternative containing the `&' constraint (*note
Modifiers::) for the clobber and the hard register is in register
classes of the clobber in the alternative. You can clobber either
- a specific hard register, a pseudo register, or a 'scratch'
+ a specific hard register, a pseudo register, or a `scratch'
expression; in the latter two cases, GCC will allocate a hard
register that is available there for use as a temporary.
For instructions that require a temporary register, you should use
- 'scratch' instead of a pseudo-register because this will allow the
- combiner phase to add the 'clobber' when required. You do this by
- coding ('clobber' ('match_scratch' ...)). If you do clobber a
- pseudo register, use one which appears nowhere else--generate a new
- one each time. Otherwise, you may confuse CSE.
+ `scratch' instead of a pseudo-register because this will allow the
+ combiner phase to add the `clobber' when required. You do this by
+ coding (`clobber' (`match_scratch' ...)). If you do clobber a
+ pseudo register, use one which appears nowhere else--generate a
+ new one each time. Otherwise, you may confuse CSE.
There is one other known use for clobbering a pseudo register in a
- 'parallel': when one of the input operands of the insn is also
+ `parallel': when one of the input operands of the insn is also
clobbered by the insn. In this case, using the same pseudo
register in the clobber and elsewhere in the insn produces the
expected results.
-'(use X)'
+`(use X)'
Represents the use of the value of X. It indicates that the value
- in X at this point in the program is needed, even though it may not
- be apparent why this is so. Therefore, the compiler will not
+ in X at this point in the program is needed, even though it may
+ not be apparent why this is so. Therefore, the compiler will not
attempt to delete previous instructions whose only effect is to
- store a value in X. X must be a 'reg' expression.
+ store a value in X. X must be a `reg' expression.
- In some situations, it may be tempting to add a 'use' of a register
- in a 'parallel' to describe a situation where the value of a
- special register will modify the behavior of the instruction. A
- hypothetical example might be a pattern for an addition that can
+ In some situations, it may be tempting to add a `use' of a
+ register in a `parallel' to describe a situation where the value
+ of a special register will modify the behavior of the instruction.
+ A hypothetical example might be a pattern for an addition that can
either wrap around or use saturating addition depending on the
value of a special control register:
@@ -16258,33 +16410,34 @@ operands of these.
This will not work, several of the optimizers only look at
expressions locally; it is very likely that if you have multiple
- insns with identical inputs to the 'unspec', they will be optimized
- away even if register 1 changes in between.
-
- This means that 'use' can _only_ be used to describe that the
- register is live. You should think twice before adding 'use'
- statements, more often you will want to use 'unspec' instead. The
- 'use' RTX is most commonly useful to describe that a fixed register
- is implicitly used in an insn. It is also safe to use in patterns
- where the compiler knows for other reasons that the result of the
- whole pattern is variable, such as 'movmemM' or 'call' patterns.
-
- During the reload phase, an insn that has a 'use' as pattern can
- carry a reg_equal note. These 'use' insns will be deleted before
+ insns with identical inputs to the `unspec', they will be
+ optimized away even if register 1 changes in between.
+
+ This means that `use' can _only_ be used to describe that the
+ register is live. You should think twice before adding `use'
+ statements, more often you will want to use `unspec' instead. The
+ `use' RTX is most commonly useful to describe that a fixed
+ register is implicitly used in an insn. It is also safe to use in
+ patterns where the compiler knows for other reasons that the result
+ of the whole pattern is variable, such as `movmemM' or `call'
+ patterns.
+
+ During the reload phase, an insn that has a `use' as pattern can
+ carry a reg_equal note. These `use' insns will be deleted before
the reload phase exits.
- During the delayed branch scheduling phase, X may be an insn. This
- indicates that X previously was located at this place in the code
- and its data dependencies need to be taken into account. These
- 'use' insns will be deleted before the delayed branch scheduling
- phase exits.
+ During the delayed branch scheduling phase, X may be an insn.
+ This indicates that X previously was located at this place in the
+ code and its data dependencies need to be taken into account.
+ These `use' insns will be deleted before the delayed branch
+ scheduling phase exits.
-'(parallel [X0 X1 ...])'
+`(parallel [X0 X1 ...])'
Represents several side effects performed in parallel. The square
- brackets stand for a vector; the operand of 'parallel' is a vector
+ brackets stand for a vector; the operand of `parallel' is a vector
of expressions. X0, X1 and so on are individual side effect
- expressions--expressions of code 'set', 'call', 'return',
- 'simple_return', 'clobber' or 'use'.
+ expressions--expressions of code `set', `call', `return',
+ `simple_return', `clobber' or `use'.
"In parallel" means that first all the values used in the
individual side-effects are computed, and second all the actual
@@ -16295,13 +16448,13 @@ operands of these.
says unambiguously that the values of hard register 1 and the
memory location addressed by it are interchanged. In both places
- where '(reg:SI 1)' appears as a memory address it refers to the
+ where `(reg:SI 1)' appears as a memory address it refers to the
value in register 1 _before_ the execution of the insn.
- It follows that it is _incorrect_ to use 'parallel' and expect the
- result of one 'set' to be available for the next one. For example,
- people sometimes attempt to represent a jump-if-zero instruction
- this way:
+ It follows that it is _incorrect_ to use `parallel' and expect the
+ result of one `set' to be available for the next one. For
+ example, people sometimes attempt to represent a jump-if-zero
+ instruction this way:
(parallel [(set (cc0) (reg:SI 34))
(set (pc) (if_then_else
@@ -16314,78 +16467,79 @@ operands of these.
on the new value that is set by this instruction.
Peephole optimization, which takes place together with final
- assembly code output, can produce insns whose patterns consist of a
- 'parallel' whose elements are the operands needed to output the
- resulting assembler code--often 'reg', 'mem' or constant
+ assembly code output, can produce insns whose patterns consist of
+ a `parallel' whose elements are the operands needed to output the
+ resulting assembler code--often `reg', `mem' or constant
expressions. This would not be well-formed RTL at any other stage
in compilation, but it is OK then because no further optimization
remains to be done. However, the definition of the macro
- 'NOTICE_UPDATE_CC', if any, must deal with such insns if you define
- any peephole optimizations.
+ `NOTICE_UPDATE_CC', if any, must deal with such insns if you
+ define any peephole optimizations.
-'(cond_exec [COND EXPR])'
+`(cond_exec [COND EXPR])'
Represents a conditionally executed expression. The EXPR is
- executed only if the COND is nonzero. The COND expression must not
- have side-effects, but the EXPR may very well have side-effects.
+ executed only if the COND is nonzero. The COND expression must
+ not have side-effects, but the EXPR may very well have
+ side-effects.
-'(sequence [INSNS ...])'
- Represents a sequence of insns. If a 'sequence' appears in the
+`(sequence [INSNS ...])'
+ Represents a sequence of insns. If a `sequence' appears in the
chain of insns, then each of the INSNS that appears in the sequence
- must be suitable for appearing in the chain of insns, i.e. must
- satisfy the 'INSN_P' predicate.
+ must be suitable for appearing in the chain of insns, i.e. must
+ satisfy the `INSN_P' predicate.
- After delay-slot scheduling is completed, an insn and all the insns
- that reside in its delay slots are grouped together into a
- 'sequence'. The insn requiring the delay slot is the first insn in
- the vector; subsequent insns are to be placed in the delay slot.
+ After delay-slot scheduling is completed, an insn and all the
+ insns that reside in its delay slots are grouped together into a
+ `sequence'. The insn requiring the delay slot is the first insn
+ in the vector; subsequent insns are to be placed in the delay slot.
- 'INSN_ANNULLED_BRANCH_P' is set on an insn in a delay slot to
+ `INSN_ANNULLED_BRANCH_P' is set on an insn in a delay slot to
indicate that a branch insn should be used that will conditionally
annul the effect of the insns in the delay slots. In such a case,
- 'INSN_FROM_TARGET_P' indicates that the insn is from the target of
+ `INSN_FROM_TARGET_P' indicates that the insn is from the target of
the branch and should be executed only if the branch is taken;
otherwise the insn should be executed only if the branch is not
taken. *Note Delay Slots::.
- Some back ends also use 'sequence' objects for purposes other than
+ Some back ends also use `sequence' objects for purposes other than
delay-slot groups. This is not supported in the common parts of
the compiler, which treat such sequences as delay-slot groups.
DWARF2 Call Frame Address (CFA) adjustments are sometimes also
- expressed using 'sequence' objects as the value of a
- 'RTX_FRAME_RELATED_P' note. This only happens if the CFA
+ expressed using `sequence' objects as the value of a
+ `RTX_FRAME_RELATED_P' note. This only happens if the CFA
adjustments cannot be easily derived from the pattern of the
instruction to which the note is attached. In such cases, the
value of the note is used instead of best-guesing the semantics of
the instruction. The back end can attach notes containing a
- 'sequence' of 'set' patterns that express the effect of the parent
+ `sequence' of `set' patterns that express the effect of the parent
instruction.
These expression codes appear in place of a side effect, as the body of
an insn, though strictly speaking they do not always describe side
effects as such:
-'(asm_input S)'
+`(asm_input S)'
Represents literal assembler code as described by the string S.
-'(unspec [OPERANDS ...] INDEX)'
-'(unspec_volatile [OPERANDS ...] INDEX)'
- Represents a machine-specific operation on OPERANDS. INDEX selects
- between multiple machine-specific operations. 'unspec_volatile' is
- used for volatile operations and operations that may trap; 'unspec'
- is used for other operations.
+`(unspec [OPERANDS ...] INDEX)'
+`(unspec_volatile [OPERANDS ...] INDEX)'
+ Represents a machine-specific operation on OPERANDS. INDEX
+ selects between multiple machine-specific operations.
+ `unspec_volatile' is used for volatile operations and operations
+ that may trap; `unspec' is used for other operations.
- These codes may appear inside a 'pattern' of an insn, inside a
- 'parallel', or inside an expression.
+ These codes may appear inside a `pattern' of an insn, inside a
+ `parallel', or inside an expression.
-'(addr_vec:M [LR0 LR1 ...])'
+`(addr_vec:M [LR0 LR1 ...])'
Represents a table of jump addresses. The vector elements LR0,
- etc., are 'label_ref' expressions. The mode M specifies how much
- space is given to each address; normally M would be 'Pmode'.
+ etc., are `label_ref' expressions. The mode M specifies how much
+ space is given to each address; normally M would be `Pmode'.
-'(addr_diff_vec:M BASE [LR0 LR1 ...] MIN MAX FLAGS)'
+`(addr_diff_vec:M BASE [LR0 LR1 ...] MIN MAX FLAGS)'
Represents a table of jump addresses expressed as offsets from
- BASE. The vector elements LR0, etc., are 'label_ref' expressions
+ BASE. The vector elements LR0, etc., are `label_ref' expressions
and so is BASE. The mode M specifies how much space is given to
each address-difference. MIN and MAX are set up by branch
shortening and hold a label with a minimum and a maximum address,
@@ -16393,13 +16547,13 @@ effects as such:
and MAX to the containing insn and of MIN and MAX to BASE. See
rtl.def for details.
-'(prefetch:M ADDR RW LOCALITY)'
+`(prefetch:M ADDR RW LOCALITY)'
Represents prefetch of memory at address ADDR. Operand RW is 1 if
the prefetch is for data to be written, 0 otherwise; targets that
do not support write prefetches should treat this as a normal
prefetch. Operand LOCALITY specifies the amount of temporal
- locality; 0 if there is none or 1, 2, or 3 for increasing levels of
- temporal locality; targets that do not support locality hints
+ locality; 0 if there is none or 1, 2, or 3 for increasing levels
+ of temporal locality; targets that do not support locality hints
should ignore this.
This insn is used to minimize cache-miss latency by moving data
@@ -16414,40 +16568,39 @@ File: gccint.info, Node: Incdec, Next: Assembler, Prev: Side Effects, Up: RT
Six special side-effect expression codes appear as memory addresses.
-'(pre_dec:M X)'
+`(pre_dec:M X)'
Represents the side effect of decrementing X by a standard amount
and represents also the value that X has after being decremented.
- X must be a 'reg' or 'mem', but most machines allow only a 'reg'.
- M must be the machine mode for pointers on the machine in use. The
- amount X is decremented by is the length in bytes of the machine
- mode of the containing memory reference of which this expression
- serves as the address. Here is an example of its use:
+ X must be a `reg' or `mem', but most machines allow only a `reg'.
+ M must be the machine mode for pointers on the machine in use.
+ The amount X is decremented by is the length in bytes of the
+ machine mode of the containing memory reference of which this
+ expression serves as the address. Here is an example of its use:
(mem:DF (pre_dec:SI (reg:SI 39)))
This says to decrement pseudo register 39 by the length of a
- 'DFmode' value and use the result to address a 'DFmode' value.
+ `DFmode' value and use the result to address a `DFmode' value.
-'(pre_inc:M X)'
+`(pre_inc:M X)'
Similar, but specifies incrementing X instead of decrementing it.
-'(post_dec:M X)'
- Represents the same side effect as 'pre_dec' but a different value.
- The value represented here is the value X has before being
+`(post_dec:M X)'
+ Represents the same side effect as `pre_dec' but a different
+ value. The value represented here is the value X has before being
decremented.
-'(post_inc:M X)'
+`(post_inc:M X)'
Similar, but specifies incrementing X instead of decrementing it.
-'(post_modify:M X Y)'
-
+`(post_modify:M X Y)'
Represents the side effect of setting X to Y and represents X
- before X is modified. X must be a 'reg' or 'mem', but most
- machines allow only a 'reg'. M must be the machine mode for
+ before X is modified. X must be a `reg' or `mem', but most
+ machines allow only a `reg'. M must be the machine mode for
pointers on the machine in use.
- The expression Y must be one of three forms: '(plus:M X Z)',
- '(minus:M X Z)', or '(plus:M X I)', where Z is an index register
+ The expression Y must be one of three forms: `(plus:M X Z)',
+ `(minus:M X Z)', or `(plus:M X I)', where Z is an index register
and I is a constant.
Here is an example of its use:
@@ -16458,15 +16611,16 @@ Six special side-effect expression codes appear as memory addresses.
This says to modify pseudo register 42 by adding the contents of
pseudo register 48 to it, after the use of what ever 42 points to.
-'(pre_modify:M X EXPR)'
+`(pre_modify:M X EXPR)'
Similar except side effects happen before the use.
These embedded side effect expressions must be used with care.
-Instruction patterns may not use them. Until the 'flow' pass of the
+Instruction patterns may not use them. Until the `flow' pass of the
compiler, they may occur only to represent pushes onto the stack. The
-'flow' pass finds cases where registers are incremented or decremented
-in one instruction and used as an address shortly before or after; these
-cases are then transformed to use pre- or post-increment or -decrement.
+`flow' pass finds cases where registers are incremented or decremented
+in one instruction and used as an address shortly before or after;
+these cases are then transformed to use pre- or post-increment or
+-decrement.
If a register used as the operand of these expressions is used in
another address in an insn, the original value of the register is used.
@@ -16476,12 +16630,12 @@ insns behave differently on different machines and hence must be treated
as ambiguous and disallowed.
An instruction that can be represented with an embedded side effect
-could also be represented using 'parallel' containing an additional
-'set' to describe how the address register is altered. This is not done
-because machines that allow these operations at all typically allow them
-wherever a memory address is called for. Describing them as additional
-parallel stores would require doubling the number of entries in the
-machine description.
+could also be represented using `parallel' containing an additional
+`set' to describe how the address register is altered. This is not
+done because machines that allow these operations at all typically
+allow them wherever a memory address is called for. Describing them as
+additional parallel stores would require doubling the number of entries
+in the machine description.

File: gccint.info, Node: Assembler, Next: Debug Information, Prev: Incdec, Up: RTL
@@ -16489,15 +16643,15 @@ File: gccint.info, Node: Assembler, Next: Debug Information, Prev: Incdec, U
13.17 Assembler Instructions as Expressions
===========================================
-The RTX code 'asm_operands' represents a value produced by a
-user-specified assembler instruction. It is used to represent an 'asm'
-statement with arguments. An 'asm' statement with a single output
+The RTX code `asm_operands' represents a value produced by a
+user-specified assembler instruction. It is used to represent an `asm'
+statement with arguments. An `asm' statement with a single output
operand, like this:
asm ("foo %1,%2,%0" : "=a" (outputvar) : "g" (x + y), "di" (*z));
-is represented using a single 'asm_operands' RTX which represents the
-value that is stored in 'outputvar':
+is represented using a single `asm_operands' RTX which represents the
+value that is stored in `outputvar':
(set RTX-FOR-OUTPUTVAR
(asm_operands "foo %1,%2,%0" "a" 0
@@ -16505,15 +16659,15 @@ value that is stored in 'outputvar':
[(asm_input:M1 "g")
(asm_input:M2 "di")]))
-Here the operands of the 'asm_operands' RTX are the assembler template
+Here the operands of the `asm_operands' RTX are the assembler template
string, the output-operand's constraint, the index-number of the output
operand among the output operands specified, a vector of input operand
-RTX's, and a vector of input-operand modes and constraints. The mode M1
-is the mode of the sum 'x+y'; M2 is that of '*z'.
+RTX's, and a vector of input-operand modes and constraints. The mode
+M1 is the mode of the sum `x+y'; M2 is that of `*z'.
- When an 'asm' statement has multiple output values, its insn has
-several such 'set' RTX's inside of a 'parallel'. Each 'set' contains an
-'asm_operands'; all of these share the same assembler template and
+ When an `asm' statement has multiple output values, its insn has
+several such `set' RTX's inside of a `parallel'. Each `set' contains
+an `asm_operands'; all of these share the same assembler template and
vectors, but each contains the constraint for the respective output
operand. They are also distinguished by the output-operand index
number, which is 0, 1, ... for successive output operands.
@@ -16524,27 +16678,28 @@ File: gccint.info, Node: Debug Information, Next: Insns, Prev: Assembler, Up
13.18 Variable Location Debug Information in RTL
================================================
-Variable tracking relies on 'MEM_EXPR' and 'REG_EXPR' annotations to
+Variable tracking relies on `MEM_EXPR' and `REG_EXPR' annotations to
determine what user variables memory and register references refer to.
Variable tracking at assignments uses these notes only when they refer
to variables that live at fixed locations (e.g., addressable variables,
-global non-automatic variables). For variables whose location may vary,
-it relies on the following types of notes.
-
-'(var_location:MODE VAR EXP STAT)'
- Binds variable 'var', a tree, to value EXP, an RTL expression. It
- appears only in 'NOTE_INSN_VAR_LOCATION' and 'DEBUG_INSN's, with
- slightly different meanings. MODE, if present, represents the mode
- of EXP, which is useful if it is a modeless expression. STAT is
- only meaningful in notes, indicating whether the variable is known
- to be initialized or uninitialized.
-
-'(debug_expr:MODE DECL)'
- Stands for the value bound to the 'DEBUG_EXPR_DECL' DECL, that
- points back to it, within value expressions in 'VAR_LOCATION'
+global non-automatic variables). For variables whose location may
+vary, it relies on the following types of notes.
+
+`(var_location:MODE VAR EXP STAT)'
+ Binds variable `var', a tree, to value EXP, an RTL expression. It
+ appears only in `NOTE_INSN_VAR_LOCATION' and `DEBUG_INSN's, with
+ slightly different meanings. MODE, if present, represents the
+ mode of EXP, which is useful if it is a modeless expression. STAT
+ is only meaningful in notes, indicating whether the variable is
+ known to be initialized or uninitialized.
+
+`(debug_expr:MODE DECL)'
+ Stands for the value bound to the `DEBUG_EXPR_DECL' DECL, that
+ points back to it, within value expressions in `VAR_LOCATION'
nodes.
+

File: gccint.info, Node: Insns, Next: Calls, Prev: Debug Information, Up: RTL
@@ -16554,7 +16709,7 @@ File: gccint.info, Node: Insns, Next: Calls, Prev: Debug Information, Up: RT
The RTL representation of the code for a function is a doubly-linked
chain of objects called "insns". Insns are expressions with special
codes that are used for no other purpose. Some insns are actual
-instructions; others represent dispatch tables for 'switch' statements;
+instructions; others represent dispatch tables for `switch' statements;
others represent labels to jump to or various sorts of declarative
information.
@@ -16563,25 +16718,25 @@ id-number that distinguishes it from all other insns in the current
function (after delayed branch scheduling, copies of an insn with the
same id-number may be present in multiple places in a function, but
these copies will always be identical and will only appear inside a
-'sequence'), and chain pointers to the preceding and following insns.
+`sequence'), and chain pointers to the preceding and following insns.
These three fields occupy the same position in every insn, independent
-of the expression code of the insn. They could be accessed with 'XEXP'
-and 'XINT', but instead three special macros are always used:
+of the expression code of the insn. They could be accessed with `XEXP'
+and `XINT', but instead three special macros are always used:
-'INSN_UID (I)'
+`INSN_UID (I)'
Accesses the unique id of insn I.
-'PREV_INSN (I)'
+`PREV_INSN (I)'
Accesses the chain pointer to the insn preceding I. If I is the
first insn, this is a null pointer.
-'NEXT_INSN (I)'
+`NEXT_INSN (I)'
Accesses the chain pointer to the insn following I. If I is the
last insn, this is a null pointer.
- The first insn in the chain is obtained by calling 'get_insns'; the
-last insn is the result of calling 'get_last_insn'. Within the chain
-delimited by these insns, the 'NEXT_INSN' and 'PREV_INSN' pointers must
+ The first insn in the chain is obtained by calling `get_insns'; the
+last insn is the result of calling `get_last_insn'. Within the chain
+delimited by these insns, the `NEXT_INSN' and `PREV_INSN' pointers must
always correspond: if INSN is not the first insn,
NEXT_INSN (PREV_INSN (INSN)) == INSN
@@ -16593,290 +16748,295 @@ is always true and if INSN is not the last insn,
is always true.
After delay slot scheduling, some of the insns in the chain might be
-'sequence' expressions, which contain a vector of insns. The value of
-'NEXT_INSN' in all but the last of these insns is the next insn in the
-vector; the value of 'NEXT_INSN' of the last insn in the vector is the
-same as the value of 'NEXT_INSN' for the 'sequence' in which it is
-contained. Similar rules apply for 'PREV_INSN'.
+`sequence' expressions, which contain a vector of insns. The value of
+`NEXT_INSN' in all but the last of these insns is the next insn in the
+vector; the value of `NEXT_INSN' of the last insn in the vector is the
+same as the value of `NEXT_INSN' for the `sequence' in which it is
+contained. Similar rules apply for `PREV_INSN'.
This means that the above invariants are not necessarily true for insns
-inside 'sequence' expressions. Specifically, if INSN is the first insn
-in a 'sequence', 'NEXT_INSN (PREV_INSN (INSN))' is the insn containing
-the 'sequence' expression, as is the value of 'PREV_INSN (NEXT_INSN
-(INSN))' if INSN is the last insn in the 'sequence' expression. You can
-use these expressions to find the containing 'sequence' expression.
+inside `sequence' expressions. Specifically, if INSN is the first insn
+in a `sequence', `NEXT_INSN (PREV_INSN (INSN))' is the insn containing
+the `sequence' expression, as is the value of `PREV_INSN (NEXT_INSN
+(INSN))' if INSN is the last insn in the `sequence' expression. You
+can use these expressions to find the containing `sequence' expression.
Every insn has one of the following expression codes:
-'insn'
- The expression code 'insn' is used for instructions that do not
- jump and do not do function calls. 'sequence' expressions are
- always contained in insns with code 'insn' even if one of those
+`insn'
+ The expression code `insn' is used for instructions that do not
+ jump and do not do function calls. `sequence' expressions are
+ always contained in insns with code `insn' even if one of those
insns should jump or do function calls.
- Insns with code 'insn' have four additional fields beyond the three
+ Insns with code `insn' have four additional fields beyond the three
mandatory ones listed above. These four are described in a table
below.
-'jump_insn'
- The expression code 'jump_insn' is used for instructions that may
- jump (or, more generally, may contain 'label_ref' expressions to
- which 'pc' can be set in that instruction). If there is an
+`jump_insn'
+ The expression code `jump_insn' is used for instructions that may
+ jump (or, more generally, may contain `label_ref' expressions to
+ which `pc' can be set in that instruction). If there is an
instruction to return from the current function, it is recorded as
- a 'jump_insn'.
+ a `jump_insn'.
- 'jump_insn' insns have the same extra fields as 'insn' insns,
+ `jump_insn' insns have the same extra fields as `insn' insns,
accessed in the same way and in addition contain a field
- 'JUMP_LABEL' which is defined once jump optimization has completed.
+ `JUMP_LABEL' which is defined once jump optimization has completed.
For simple conditional and unconditional jumps, this field contains
- the 'code_label' to which this insn will (possibly conditionally)
- branch. In a more complex jump, 'JUMP_LABEL' records one of the
+ the `code_label' to which this insn will (possibly conditionally)
+ branch. In a more complex jump, `JUMP_LABEL' records one of the
labels that the insn refers to; other jump target labels are
- recorded as 'REG_LABEL_TARGET' notes. The exception is 'addr_vec'
- and 'addr_diff_vec', where 'JUMP_LABEL' is 'NULL_RTX' and the only
+ recorded as `REG_LABEL_TARGET' notes. The exception is `addr_vec'
+ and `addr_diff_vec', where `JUMP_LABEL' is `NULL_RTX' and the only
way to find the labels is to scan the entire body of the insn.
Return insns count as jumps, but since they do not refer to any
- labels, their 'JUMP_LABEL' is 'NULL_RTX'.
+ labels, their `JUMP_LABEL' is `NULL_RTX'.
-'call_insn'
- The expression code 'call_insn' is used for instructions that may
+`call_insn'
+ The expression code `call_insn' is used for instructions that may
do function calls. It is important to distinguish these
instructions because they imply that certain registers and memory
locations may be altered unpredictably.
- 'call_insn' insns have the same extra fields as 'insn' insns,
+ `call_insn' insns have the same extra fields as `insn' insns,
accessed in the same way and in addition contain a field
- 'CALL_INSN_FUNCTION_USAGE', which contains a list (chain of
- 'expr_list' expressions) containing 'use', 'clobber' and sometimes
- 'set' expressions that denote hard registers and 'mem's used or
+ `CALL_INSN_FUNCTION_USAGE', which contains a list (chain of
+ `expr_list' expressions) containing `use', `clobber' and sometimes
+ `set' expressions that denote hard registers and `mem's used or
clobbered by the called function.
- A 'mem' generally points to a stack slot in which arguments passed
+ A `mem' generally points to a stack slot in which arguments passed
to the libcall by reference (*note TARGET_PASS_BY_REFERENCE:
Register Arguments.) are stored. If the argument is caller-copied
(*note TARGET_CALLEE_COPIES: Register Arguments.), the stack slot
- will be mentioned in 'clobber' and 'use' entries; if it's
- callee-copied, only a 'use' will appear, and the 'mem' may point to
- addresses that are not stack slots.
+ will be mentioned in `clobber' and `use' entries; if it's
+ callee-copied, only a `use' will appear, and the `mem' may point
+ to addresses that are not stack slots.
- Registers occurring inside a 'clobber' in this list augment
- registers specified in 'CALL_USED_REGISTERS' (*note Register
+ Registers occurring inside a `clobber' in this list augment
+ registers specified in `CALL_USED_REGISTERS' (*note Register
Basics::).
- If the list contains a 'set' involving two registers, it indicates
- that the function returns one of its arguments. Such a 'set' may
+ If the list contains a `set' involving two registers, it indicates
+ that the function returns one of its arguments. Such a `set' may
look like a no-op if the same register holds the argument and the
return value.
-'code_label'
- A 'code_label' insn represents a label that a jump insn can jump
+`code_label'
+ A `code_label' insn represents a label that a jump insn can jump
to. It contains two special fields of data in addition to the
- three standard ones. 'CODE_LABEL_NUMBER' is used to hold the
+ three standard ones. `CODE_LABEL_NUMBER' is used to hold the
"label number", a number that identifies this label uniquely among
all the labels in the compilation (not just in the current
function). Ultimately, the label is represented in the assembler
- output as an assembler label, usually of the form 'LN' where N is
+ output as an assembler label, usually of the form `LN' where N is
the label number.
- When a 'code_label' appears in an RTL expression, it normally
- appears within a 'label_ref' which represents the address of the
+ When a `code_label' appears in an RTL expression, it normally
+ appears within a `label_ref' which represents the address of the
label, as a number.
- Besides as a 'code_label', a label can also be represented as a
- 'note' of type 'NOTE_INSN_DELETED_LABEL'.
+ Besides as a `code_label', a label can also be represented as a
+ `note' of type `NOTE_INSN_DELETED_LABEL'.
- The field 'LABEL_NUSES' is only defined once the jump optimization
+ The field `LABEL_NUSES' is only defined once the jump optimization
phase is completed. It contains the number of times this label is
referenced in the current function.
- The field 'LABEL_KIND' differentiates four different types of
- labels: 'LABEL_NORMAL', 'LABEL_STATIC_ENTRY', 'LABEL_GLOBAL_ENTRY',
- and 'LABEL_WEAK_ENTRY'. The only labels that do not have type
- 'LABEL_NORMAL' are "alternate entry points" to the current
- function. These may be static (visible only in the containing
- translation unit), global (exposed to all translation units), or
- weak (global, but can be overridden by another symbol with the same
- name).
+ The field `LABEL_KIND' differentiates four different types of
+ labels: `LABEL_NORMAL', `LABEL_STATIC_ENTRY',
+ `LABEL_GLOBAL_ENTRY', and `LABEL_WEAK_ENTRY'. The only labels
+ that do not have type `LABEL_NORMAL' are "alternate entry points"
+ to the current function. These may be static (visible only in the
+ containing translation unit), global (exposed to all translation
+ units), or weak (global, but can be overridden by another symbol
+ with the same name).
Much of the compiler treats all four kinds of label identically.
Some of it needs to know whether or not a label is an alternate
- entry point; for this purpose, the macro 'LABEL_ALT_ENTRY_P' is
- provided. It is equivalent to testing whether 'LABEL_KIND (label)
+ entry point; for this purpose, the macro `LABEL_ALT_ENTRY_P' is
+ provided. It is equivalent to testing whether `LABEL_KIND (label)
== LABEL_NORMAL'. The only place that cares about the distinction
between static, global, and weak alternate entry points, besides
the front-end code that creates them, is the function
- 'output_alternate_entry_point', in 'final.c'.
-
- To set the kind of a label, use the 'SET_LABEL_KIND' macro.
-
-'jump_table_data'
- A 'jump_table_data' insn is a placeholder for the jump-table data
- of a 'casesi' or 'tablejump' insn. They are placed after a
- 'tablejump_p' insn. A 'jump_table_data' insn is not part o a basic
- blockm but it is associated with the basic block that ends with the
- 'tablejump_p' insn. The 'PATTERN' of a 'jump_table_data' is always
- either an 'addr_vec' or an 'addr_diff_vec', and a 'jump_table_data'
- insn is always preceded by a 'code_label'. The 'tablejump_p' insn
- refers to that 'code_label' via its 'JUMP_LABEL'.
-
-'barrier'
+ `output_alternate_entry_point', in `final.c'.
+
+ To set the kind of a label, use the `SET_LABEL_KIND' macro.
+
+`jump_table_data'
+ A `jump_table_data' insn is a placeholder for the jump-table data
+ of a `casesi' or `tablejump' insn. They are placed after a
+ `tablejump_p' insn. A `jump_table_data' insn is not part o a
+ basic blockm but it is associated with the basic block that ends
+ with the `tablejump_p' insn. The `PATTERN' of a `jump_table_data'
+ is always either an `addr_vec' or an `addr_diff_vec', and a
+ `jump_table_data' insn is always preceded by a `code_label'. The
+ `tablejump_p' insn refers to that `code_label' via its
+ `JUMP_LABEL'.
+
+`barrier'
Barriers are placed in the instruction stream when control cannot
flow past them. They are placed after unconditional jump
- instructions to indicate that the jumps are unconditional and after
- calls to 'volatile' functions, which do not return (e.g., 'exit').
- They contain no information beyond the three standard fields.
+ instructions to indicate that the jumps are unconditional and
+ after calls to `volatile' functions, which do not return (e.g.,
+ `exit'). They contain no information beyond the three standard
+ fields.
-'note'
- 'note' insns are used to represent additional debugging and
+`note'
+ `note' insns are used to represent additional debugging and
declarative information. They contain two nonstandard fields, an
- integer which is accessed with the macro 'NOTE_LINE_NUMBER' and a
- string accessed with 'NOTE_SOURCE_FILE'.
+ integer which is accessed with the macro `NOTE_LINE_NUMBER' and a
+ string accessed with `NOTE_SOURCE_FILE'.
- If 'NOTE_LINE_NUMBER' is positive, the note represents the position
- of a source line and 'NOTE_SOURCE_FILE' is the source file name
- that the line came from. These notes control generation of line
- number data in the assembler output.
+ If `NOTE_LINE_NUMBER' is positive, the note represents the
+ position of a source line and `NOTE_SOURCE_FILE' is the source
+ file name that the line came from. These notes control generation
+ of line number data in the assembler output.
- Otherwise, 'NOTE_LINE_NUMBER' is not really a line number but a
- code with one of the following values (and 'NOTE_SOURCE_FILE' must
+ Otherwise, `NOTE_LINE_NUMBER' is not really a line number but a
+ code with one of the following values (and `NOTE_SOURCE_FILE' must
contain a null pointer):
- 'NOTE_INSN_DELETED'
+ `NOTE_INSN_DELETED'
Such a note is completely ignorable. Some passes of the
compiler delete insns by altering them into notes of this
kind.
- 'NOTE_INSN_DELETED_LABEL'
- This marks what used to be a 'code_label', but was not used
- for other purposes than taking its address and was transformed
- to mark that no code jumps to it.
+ `NOTE_INSN_DELETED_LABEL'
+ This marks what used to be a `code_label', but was not used
+ for other purposes than taking its address and was
+ transformed to mark that no code jumps to it.
- 'NOTE_INSN_BLOCK_BEG'
- 'NOTE_INSN_BLOCK_END'
+ `NOTE_INSN_BLOCK_BEG'
+ `NOTE_INSN_BLOCK_END'
These types of notes indicate the position of the beginning
- and end of a level of scoping of variable names. They control
- the output of debugging information.
+ and end of a level of scoping of variable names. They
+ control the output of debugging information.
- 'NOTE_INSN_EH_REGION_BEG'
- 'NOTE_INSN_EH_REGION_END'
+ `NOTE_INSN_EH_REGION_BEG'
+ `NOTE_INSN_EH_REGION_END'
These types of notes indicate the position of the beginning
and end of a level of scoping for exception handling.
- 'NOTE_EH_HANDLER' identifies which region is associated with
+ `NOTE_EH_HANDLER' identifies which region is associated with
these notes.
- 'NOTE_INSN_FUNCTION_BEG'
+ `NOTE_INSN_FUNCTION_BEG'
Appears at the start of the function body, after the function
prologue.
- 'NOTE_INSN_VAR_LOCATION'
+ `NOTE_INSN_VAR_LOCATION'
This note is used to generate variable location debugging
information. It indicates that the user variable in its
- 'VAR_LOCATION' operand is at the location given in the RTL
+ `VAR_LOCATION' operand is at the location given in the RTL
expression, or holds a value that can be computed by
evaluating the RTL expression from that static point in the
program up to the next such note for the same user variable.
+
These codes are printed symbolically when they appear in debugging
dumps.
-'debug_insn'
- The expression code 'debug_insn' is used for pseudo-instructions
+`debug_insn'
+ The expression code `debug_insn' is used for pseudo-instructions
that hold debugging information for variable tracking at
- assignments (see '-fvar-tracking-assignments' option). They are
- the RTL representation of 'GIMPLE_DEBUG' statements (*note
- 'GIMPLE_DEBUG'::), with a 'VAR_LOCATION' operand that binds a user
- variable tree to an RTL representation of the 'value' in the
- corresponding statement. A 'DEBUG_EXPR' in it stands for the value
- bound to the corresponding 'DEBUG_EXPR_DECL'.
+ assignments (see `-fvar-tracking-assignments' option). They are
+ the RTL representation of `GIMPLE_DEBUG' statements (*note
+ `GIMPLE_DEBUG'::), with a `VAR_LOCATION' operand that binds a user
+ variable tree to an RTL representation of the `value' in the
+ corresponding statement. A `DEBUG_EXPR' in it stands for the
+ value bound to the corresponding `DEBUG_EXPR_DECL'.
Throughout optimization passes, binding information is kept in
pseudo-instruction form, so that, unlike notes, it gets the same
treatment and adjustments that regular instructions would. It is
the variable tracking pass that turns these pseudo-instructions
- into var location notes, analyzing control flow, value equivalences
- and changes to registers and memory referenced in value
- expressions, propagating the values of debug temporaries and
+ into var location notes, analyzing control flow, value
+ equivalences and changes to registers and memory referenced in
+ value expressions, propagating the values of debug temporaries and
determining expressions that can be used to compute the value of
each user variable at as many points (ranges, actually) in the
program as possible.
- Unlike 'NOTE_INSN_VAR_LOCATION', the value expression in an
- 'INSN_VAR_LOCATION' denotes a value at that specific point in the
+ Unlike `NOTE_INSN_VAR_LOCATION', the value expression in an
+ `INSN_VAR_LOCATION' denotes a value at that specific point in the
program, rather than an expression that can be evaluated at any
- later point before an overriding 'VAR_LOCATION' is encountered.
- E.g., if a user variable is bound to a 'REG' and then a subsequent
- insn modifies the 'REG', the note location would keep mapping the
+ later point before an overriding `VAR_LOCATION' is encountered.
+ E.g., if a user variable is bound to a `REG' and then a subsequent
+ insn modifies the `REG', the note location would keep mapping the
user variable to the register across the insn, whereas the insn
location would keep the variable bound to the value, so that the
variable tracking pass would emit another location note for the
variable at the point in which the register is modified.
- The machine mode of an insn is normally 'VOIDmode', but some phases use
-the mode for various purposes.
+
+ The machine mode of an insn is normally `VOIDmode', but some phases
+use the mode for various purposes.
The common subexpression elimination pass sets the mode of an insn to
-'QImode' when it is the first insn in a block that has already been
+`QImode' when it is the first insn in a block that has already been
processed.
The second Haifa scheduling pass, for targets that can multiple issue,
-sets the mode of an insn to 'TImode' when it is believed that the
-instruction begins an issue group. That is, when the instruction cannot
-issue simultaneously with the previous. This may be relied on by later
-passes, in particular machine-dependent reorg.
+sets the mode of an insn to `TImode' when it is believed that the
+instruction begins an issue group. That is, when the instruction
+cannot issue simultaneously with the previous. This may be relied on
+by later passes, in particular machine-dependent reorg.
- Here is a table of the extra fields of 'insn', 'jump_insn' and
-'call_insn' insns:
+ Here is a table of the extra fields of `insn', `jump_insn' and
+`call_insn' insns:
-'PATTERN (I)'
+`PATTERN (I)'
An expression for the side effect performed by this insn. This
- must be one of the following codes: 'set', 'call', 'use',
- 'clobber', 'return', 'simple_return', 'asm_input', 'asm_output',
- 'addr_vec', 'addr_diff_vec', 'trap_if', 'unspec',
- 'unspec_volatile', 'parallel', 'cond_exec', or 'sequence'. If it
- is a 'parallel', each element of the 'parallel' must be one these
- codes, except that 'parallel' expressions cannot be nested and
- 'addr_vec' and 'addr_diff_vec' are not permitted inside a
- 'parallel' expression.
-
-'INSN_CODE (I)'
+ must be one of the following codes: `set', `call', `use',
+ `clobber', `return', `simple_return', `asm_input', `asm_output',
+ `addr_vec', `addr_diff_vec', `trap_if', `unspec',
+ `unspec_volatile', `parallel', `cond_exec', or `sequence'. If it
+ is a `parallel', each element of the `parallel' must be one these
+ codes, except that `parallel' expressions cannot be nested and
+ `addr_vec' and `addr_diff_vec' are not permitted inside a
+ `parallel' expression.
+
+`INSN_CODE (I)'
An integer that says which pattern in the machine description
matches this insn, or -1 if the matching has not yet been
attempted.
Such matching is never attempted and this field remains -1 on an
- insn whose pattern consists of a single 'use', 'clobber',
- 'asm_input', 'addr_vec' or 'addr_diff_vec' expression.
+ insn whose pattern consists of a single `use', `clobber',
+ `asm_input', `addr_vec' or `addr_diff_vec' expression.
- Matching is also never attempted on insns that result from an 'asm'
- statement. These contain at least one 'asm_operands' expression.
- The function 'asm_noperands' returns a non-negative value for such
+ Matching is also never attempted on insns that result from an `asm'
+ statement. These contain at least one `asm_operands' expression.
+ The function `asm_noperands' returns a non-negative value for such
insns.
- In the debugging output, this field is printed as a number followed
- by a symbolic representation that locates the pattern in the 'md'
- file as some small positive or negative offset from a named
- pattern.
+ In the debugging output, this field is printed as a number
+ followed by a symbolic representation that locates the pattern in
+ the `md' file as some small positive or negative offset from a
+ named pattern.
-'LOG_LINKS (I)'
- A list (chain of 'insn_list' expressions) giving information about
+`LOG_LINKS (I)'
+ A list (chain of `insn_list' expressions) giving information about
dependencies between instructions within a basic block. Neither a
jump nor a label may come between the related insns. These are
only used by the schedulers and by combine. This is a deprecated
data structure. Def-use and use-def chains are now preferred.
-'REG_NOTES (I)'
- A list (chain of 'expr_list', 'insn_list' and 'int_list'
+`REG_NOTES (I)'
+ A list (chain of `expr_list', `insn_list' and `int_list'
expressions) giving miscellaneous information about the insn. It
is often information pertaining to the registers used in this insn.
- The 'LOG_LINKS' field of an insn is a chain of 'insn_list' expressions.
-Each of these has two operands: the first is an insn, and the second is
-another 'insn_list' expression (the next one in the chain). The last
-'insn_list' in the chain has a null pointer as second operand. The
-significant thing about the chain is which insns appear in it (as first
-operands of 'insn_list' expressions). Their order is not significant.
+ The `LOG_LINKS' field of an insn is a chain of `insn_list'
+expressions. Each of these has two operands: the first is an insn, and
+the second is another `insn_list' expression (the next one in the
+chain). The last `insn_list' in the chain has a null pointer as second
+operand. The significant thing about the chain is which insns appear
+in it (as first operands of `insn_list' expressions). Their order is
+not significant.
This list is originally set up by the flow analysis pass; it is a null
pointer until then. Flow only adds links for those data dependencies
@@ -16884,25 +17044,26 @@ which can be used for instruction combination. For each insn, the flow
analysis pass adds a link to insns which store into registers values
that are used for the first time in this insn.
- The 'REG_NOTES' field of an insn is a chain similar to the 'LOG_LINKS'
-field but it includes 'expr_list' and 'int_list' expressions in addition
-to 'insn_list' expressions. There are several kinds of register notes,
-which are distinguished by the machine mode, which in a register note is
-really understood as being an 'enum reg_note'. The first operand OP of
-the note is data whose meaning depends on the kind of note.
+ The `REG_NOTES' field of an insn is a chain similar to the `LOG_LINKS'
+field but it includes `expr_list' and `int_list' expressions in
+addition to `insn_list' expressions. There are several kinds of
+register notes, which are distinguished by the machine mode, which in a
+register note is really understood as being an `enum reg_note'. The
+first operand OP of the note is data whose meaning depends on the kind
+of note.
- The macro 'REG_NOTE_KIND (X)' returns the kind of register note. Its
-counterpart, the macro 'PUT_REG_NOTE_KIND (X, NEWKIND)' sets the
+ The macro `REG_NOTE_KIND (X)' returns the kind of register note. Its
+counterpart, the macro `PUT_REG_NOTE_KIND (X, NEWKIND)' sets the
register note type of X to be NEWKIND.
Register notes are of three classes: They may say something about an
input to an insn, they may say something about an output of an insn, or
they may create a linkage between two insns. There are also a set of
-values that are only used in 'LOG_LINKS'.
+values that are only used in `LOG_LINKS'.
These register notes annotate inputs to an insn:
-'REG_DEAD'
+`REG_DEAD'
The value in OP dies in this insn; that is to say, altering the
value immediately after this insn would not affect the future
behavior of the program.
@@ -16911,72 +17072,72 @@ values that are only used in 'LOG_LINKS'.
this insn since OP is not necessarily modified by this insn.
Rather, no subsequent instruction uses the contents of OP.
-'REG_UNUSED'
+`REG_UNUSED'
The register OP being set by this insn will not be used in a
- subsequent insn. This differs from a 'REG_DEAD' note, which
+ subsequent insn. This differs from a `REG_DEAD' note, which
indicates that the value in an input will not be used subsequently.
These two notes are independent; both may be present for the same
register.
-'REG_INC'
- The register OP is incremented (or decremented; at this level there
- is no distinction) by an embedded side effect inside this insn.
- This means it appears in a 'post_inc', 'pre_inc', 'post_dec' or
- 'pre_dec' expression.
-
-'REG_NONNEG'
- The register OP is known to have a nonnegative value when this insn
- is reached. This is used so that decrement and branch until zero
- instructions, such as the m68k dbra, can be matched.
-
- The 'REG_NONNEG' note is added to insns only if the machine
- description has a 'decrement_and_branch_until_zero' pattern.
-
-'REG_LABEL_OPERAND'
- This insn uses OP, a 'code_label' or a 'note' of type
- 'NOTE_INSN_DELETED_LABEL', but is not a 'jump_insn', or it is a
- 'jump_insn' that refers to the operand as an ordinary operand. The
- label may still eventually be a jump target, but if so in an
+`REG_INC'
+ The register OP is incremented (or decremented; at this level
+ there is no distinction) by an embedded side effect inside this
+ insn. This means it appears in a `post_inc', `pre_inc',
+ `post_dec' or `pre_dec' expression.
+
+`REG_NONNEG'
+ The register OP is known to have a nonnegative value when this
+ insn is reached. This is used so that decrement and branch until
+ zero instructions, such as the m68k dbra, can be matched.
+
+ The `REG_NONNEG' note is added to insns only if the machine
+ description has a `decrement_and_branch_until_zero' pattern.
+
+`REG_LABEL_OPERAND'
+ This insn uses OP, a `code_label' or a `note' of type
+ `NOTE_INSN_DELETED_LABEL', but is not a `jump_insn', or it is a
+ `jump_insn' that refers to the operand as an ordinary operand.
+ The label may still eventually be a jump target, but if so in an
indirect jump in a subsequent insn. The presence of this note
allows jump optimization to be aware that OP is, in fact, being
used, and flow optimization to build an accurate flow graph.
-'REG_LABEL_TARGET'
- This insn is a 'jump_insn' but not an 'addr_vec' or
- 'addr_diff_vec'. It uses OP, a 'code_label' as a direct or
+`REG_LABEL_TARGET'
+ This insn is a `jump_insn' but not an `addr_vec' or
+ `addr_diff_vec'. It uses OP, a `code_label' as a direct or
indirect jump target. Its purpose is similar to that of
- 'REG_LABEL_OPERAND'. This note is only present if the insn has
+ `REG_LABEL_OPERAND'. This note is only present if the insn has
multiple targets; the last label in the insn (in the highest
- numbered insn-field) goes into the 'JUMP_LABEL' field and does not
- have a 'REG_LABEL_TARGET' note. *Note JUMP_LABEL: Insns.
+ numbered insn-field) goes into the `JUMP_LABEL' field and does not
+ have a `REG_LABEL_TARGET' note. *Note JUMP_LABEL: Insns.
-'REG_CROSSING_JUMP'
+`REG_CROSSING_JUMP'
This insn is a branching instruction (either an unconditional jump
or an indirect jump) which crosses between hot and cold sections,
which could potentially be very far apart in the executable. The
presence of this note indicates to other optimizations that this
branching instruction should not be "collapsed" into a simpler
- branching construct. It is used when the optimization to partition
- basic blocks into hot and cold sections is turned on.
+ branching construct. It is used when the optimization to
+ partition basic blocks into hot and cold sections is turned on.
-'REG_SETJMP'
- Appears attached to each 'CALL_INSN' to 'setjmp' or a related
+`REG_SETJMP'
+ Appears attached to each `CALL_INSN' to `setjmp' or a related
function.
The following notes describe attributes of outputs of an insn:
-'REG_EQUIV'
-'REG_EQUAL'
+`REG_EQUIV'
+`REG_EQUAL'
This note is only valid on an insn that sets only one register and
indicates that that register will be equal to OP at run time; the
scope of this equivalence differs between the two types of notes.
The value which the insn explicitly copies into the register may
look different from OP, but they will be equal at run time. If the
- output of the single 'set' is a 'strict_low_part' expression, the
- note refers to the register that is contained in 'SUBREG_REG' of
- the 'subreg' expression.
+ output of the single `set' is a `strict_low_part' expression, the
+ note refers to the register that is contained in `SUBREG_REG' of
+ the `subreg' expression.
- For 'REG_EQUIV', the register is equivalent to OP throughout the
+ For `REG_EQUIV', the register is equivalent to OP throughout the
entire function, and could validly be replaced in all its
occurrences by OP. ("Validly" here refers to the data flow of the
program; simple replacement may make some insns invalid.) For
@@ -16986,22 +17147,23 @@ values that are only used in 'LOG_LINKS'.
When a parameter is copied into a pseudo-register at entry to a
function, a note of this kind records that the register is
equivalent to the stack slot where the parameter was passed.
- Although in this case the register may be set by other insns, it is
- still valid to replace the register by the stack slot throughout
- the function.
+ Although in this case the register may be set by other insns, it
+ is still valid to replace the register by the stack slot
+ throughout the function.
- A 'REG_EQUIV' note is also used on an instruction which copies a
+ A `REG_EQUIV' note is also used on an instruction which copies a
register parameter into a pseudo-register at entry to a function,
if there is a stack slot where that parameter could be stored.
Although other insns may set the pseudo-register, it is valid for
the compiler to replace the pseudo-register by stack slot
throughout the function, provided the compiler ensures that the
- stack slot is properly initialized by making the replacement in the
- initial copy instruction as well. This is used on machines for
- which the calling convention allocates stack space for register
- parameters. See 'REG_PARM_STACK_SPACE' in *note Stack Arguments::.
+ stack slot is properly initialized by making the replacement in
+ the initial copy instruction as well. This is used on machines
+ for which the calling convention allocates stack space for
+ register parameters. See `REG_PARM_STACK_SPACE' in *note Stack
+ Arguments::.
- In the case of 'REG_EQUAL', the register that is set by this insn
+ In the case of `REG_EQUAL', the register that is set by this insn
will be equal to OP at run time at the end of this insn but not
necessarily elsewhere in the function. In this case, OP is
typically an arithmetic expression. For example, when a sequence
@@ -17010,86 +17172,87 @@ values that are only used in 'LOG_LINKS'.
or copies the final value.
These two notes are used in different ways by the compiler passes.
- 'REG_EQUAL' is used by passes prior to register allocation (such as
+ `REG_EQUAL' is used by passes prior to register allocation (such as
common subexpression elimination and loop optimization) to tell
- them how to think of that value. 'REG_EQUIV' notes are used by
+ them how to think of that value. `REG_EQUIV' notes are used by
register allocation to indicate that there is an available
- substitute expression (either a constant or a 'mem' expression for
- the location of a parameter on the stack) that may be used in place
- of a register if insufficient registers are available.
+ substitute expression (either a constant or a `mem' expression for
+ the location of a parameter on the stack) that may be used in
+ place of a register if insufficient registers are available.
Except for stack homes for parameters, which are indicated by a
- 'REG_EQUIV' note and are not useful to the early optimization
+ `REG_EQUIV' note and are not useful to the early optimization
passes and pseudo registers that are equivalent to a memory
location throughout their entire life, which is not detected until
later in the compilation, all equivalences are initially indicated
- by an attached 'REG_EQUAL' note. In the early stages of register
- allocation, a 'REG_EQUAL' note is changed into a 'REG_EQUIV' note
+ by an attached `REG_EQUAL' note. In the early stages of register
+ allocation, a `REG_EQUAL' note is changed into a `REG_EQUIV' note
if OP is a constant and the insn represents the only set of its
destination register.
Thus, compiler passes prior to register allocation need only check
- for 'REG_EQUAL' notes and passes subsequent to register allocation
- need only check for 'REG_EQUIV' notes.
+ for `REG_EQUAL' notes and passes subsequent to register allocation
+ need only check for `REG_EQUIV' notes.
These notes describe linkages between insns. They occur in pairs: one
insn has one of a pair of notes that points to a second insn, which has
the inverse note pointing back to the first insn.
-'REG_CC_SETTER'
-'REG_CC_USER'
- On machines that use 'cc0', the insns which set and use 'cc0' set
- and use 'cc0' are adjacent. However, when branch delay slot
+`REG_CC_SETTER'
+`REG_CC_USER'
+ On machines that use `cc0', the insns which set and use `cc0' set
+ and use `cc0' are adjacent. However, when branch delay slot
filling is done, this may no longer be true. In this case a
- 'REG_CC_USER' note will be placed on the insn setting 'cc0' to
- point to the insn using 'cc0' and a 'REG_CC_SETTER' note will be
- placed on the insn using 'cc0' to point to the insn setting 'cc0'.
+ `REG_CC_USER' note will be placed on the insn setting `cc0' to
+ point to the insn using `cc0' and a `REG_CC_SETTER' note will be
+ placed on the insn using `cc0' to point to the insn setting `cc0'.
- These values are only used in the 'LOG_LINKS' field, and indicate the
+ These values are only used in the `LOG_LINKS' field, and indicate the
type of dependency that each link represents. Links which indicate a
data dependence (a read after write dependence) do not use any code,
-they simply have mode 'VOIDmode', and are printed without any
+they simply have mode `VOIDmode', and are printed without any
descriptive text.
-'REG_DEP_TRUE'
+`REG_DEP_TRUE'
This indicates a true dependence (a read after write dependence).
-'REG_DEP_OUTPUT'
+`REG_DEP_OUTPUT'
This indicates an output dependence (a write after write
dependence).
-'REG_DEP_ANTI'
+`REG_DEP_ANTI'
This indicates an anti dependence (a write after read dependence).
+
These notes describe information gathered from gcov profile data. They
-are stored in the 'REG_NOTES' field of an insn.
+are stored in the `REG_NOTES' field of an insn.
-'REG_BR_PROB'
+`REG_BR_PROB'
This is used to specify the ratio of branches to non-branches of a
branch insn according to the profile data. The note is represented
- as an 'int_list' expression whose integer value is between 0 and
- REG_BR_PROB_BASE. Larger values indicate a higher probability that
+ as an `int_list' expression whose integer value is between 0 and
+ REG_BR_PROB_BASE. Larger values indicate a higher probability that
the branch will be taken.
-'REG_BR_PRED'
+`REG_BR_PRED'
These notes are found in JUMP insns after delayed branch scheduling
has taken place. They indicate both the direction and the
likelihood of the JUMP. The format is a bitmask of ATTR_FLAG_*
values.
-'REG_FRAME_RELATED_EXPR'
+`REG_FRAME_RELATED_EXPR'
This is used on an RTX_FRAME_RELATED_P insn wherein the attached
expression is used in place of the actual insn pattern. This is
done in cases where the pattern is either complex or misleading.
- For convenience, the machine mode in an 'insn_list' or 'expr_list' is
+ For convenience, the machine mode in an `insn_list' or `expr_list' is
printed using these symbolic codes in debugging dumps.
- The only difference between the expression codes 'insn_list' and
-'expr_list' is that the first operand of an 'insn_list' is assumed to be
-an insn and is printed in debugging dumps as the insn's unique id; the
-first operand of an 'expr_list' is printed in the ordinary way as an
-expression.
+ The only difference between the expression codes `insn_list' and
+`expr_list' is that the first operand of an `insn_list' is assumed to
+be an insn and is printed in debugging dumps as the insn's unique id;
+the first operand of an `expr_list' is printed in the ordinary way as
+an expression.

File: gccint.info, Node: Calls, Next: Sharing, Prev: Insns, Up: RTL
@@ -17097,24 +17260,24 @@ File: gccint.info, Node: Calls, Next: Sharing, Prev: Insns, Up: RTL
13.20 RTL Representation of Function-Call Insns
===============================================
-Insns that call subroutines have the RTL expression code 'call_insn'.
+Insns that call subroutines have the RTL expression code `call_insn'.
These insns must satisfy special rules, and their bodies must use a
-special RTL expression code, 'call'.
+special RTL expression code, `call'.
- A 'call' expression has two operands, as follows:
+ A `call' expression has two operands, as follows:
(call (mem:FM ADDR) NBYTES)
Here NBYTES is an operand that represents the number of bytes of
argument data being passed to the subroutine, FM is a machine mode
-(which must equal as the definition of the 'FUNCTION_MODE' macro in the
+(which must equal as the definition of the `FUNCTION_MODE' macro in the
machine description) and ADDR represents the address of the subroutine.
- For a subroutine that returns no value, the 'call' expression as shown
+ For a subroutine that returns no value, the `call' expression as shown
above is the entire body of the insn, except that the insn might also
-contain 'use' or 'clobber' expressions.
+contain `use' or `clobber' expressions.
- For a subroutine that returns a value whose mode is not 'BLKmode', the
+ For a subroutine that returns a value whose mode is not `BLKmode', the
value is returned in a hard register. If this register's number is R,
then the body of the call insn looks like this:
@@ -17124,30 +17287,30 @@ then the body of the call insn looks like this:
This RTL expression makes it clear (to the optimizer passes) that the
appropriate register receives a useful value in this insn.
- When a subroutine returns a 'BLKmode' value, it is handled by passing
+ When a subroutine returns a `BLKmode' value, it is handled by passing
to the subroutine the address of a place to store the value. So the
call insn itself does not "return" any value, and it has the same RTL
form as a call that returns nothing.
On some machines, the call instruction itself clobbers some register,
-for example to contain the return address. 'call_insn' insns on these
-machines should have a body which is a 'parallel' that contains both the
-'call' expression and 'clobber' expressions that indicate which
+for example to contain the return address. `call_insn' insns on these
+machines should have a body which is a `parallel' that contains both
+the `call' expression and `clobber' expressions that indicate which
registers are destroyed. Similarly, if the call instruction requires
some register other than the stack pointer that is not explicitly
-mentioned in its RTL, a 'use' subexpression should mention that
+mentioned in its RTL, a `use' subexpression should mention that
register.
Functions that are called are assumed to modify all registers listed in
-the configuration macro 'CALL_USED_REGISTERS' (*note Register Basics::)
-and, with the exception of 'const' functions and library calls, to
+the configuration macro `CALL_USED_REGISTERS' (*note Register Basics::)
+and, with the exception of `const' functions and library calls, to
modify all of memory.
- Insns containing just 'use' expressions directly precede the
-'call_insn' insn to indicate which registers contain inputs to the
+ Insns containing just `use' expressions directly precede the
+`call_insn' insn to indicate which registers contain inputs to the
function. Similarly, if registers other than those in
-'CALL_USED_REGISTERS' are clobbered by the called function, insns
-containing a single 'clobber' follow immediately after the call to
+`CALL_USED_REGISTERS' are clobbered by the called function, insns
+containing a single `clobber' follow immediately after the call to
indicate which registers.

@@ -17157,49 +17320,49 @@ File: gccint.info, Node: Sharing, Next: Reading RTL, Prev: Calls, Up: RTL
===================================
The compiler assumes that certain kinds of RTL expressions are unique;
-there do not exist two distinct objects representing the same value. In
-other cases, it makes an opposite assumption: that no RTL expression
+there do not exist two distinct objects representing the same value.
+In other cases, it makes an opposite assumption: that no RTL expression
object of a certain kind appears in more than one place in the
containing structure.
These assumptions refer to a single function; except for the RTL
-objects that describe global variables and external functions, and a few
-standard objects such as small integer constants, no RTL objects are
-common to two functions.
+objects that describe global variables and external functions, and a
+few standard objects such as small integer constants, no RTL objects
+are common to two functions.
- * Each pseudo-register has only a single 'reg' object to represent
+ * Each pseudo-register has only a single `reg' object to represent
it, and therefore only a single machine mode.
- * For any symbolic label, there is only one 'symbol_ref' object
+ * For any symbolic label, there is only one `symbol_ref' object
referring to it.
- * All 'const_int' expressions with equal values are shared.
+ * All `const_int' expressions with equal values are shared.
- * There is only one 'pc' expression.
+ * There is only one `pc' expression.
- * There is only one 'cc0' expression.
+ * There is only one `cc0' expression.
- * There is only one 'const_double' expression with value 0 for each
+ * There is only one `const_double' expression with value 0 for each
floating point mode. Likewise for values 1 and 2.
- * There is only one 'const_vector' expression with value 0 for each
+ * There is only one `const_vector' expression with value 0 for each
vector mode, be it an integer or a double constant vector.
- * No 'label_ref' or 'scratch' appears in more than one place in the
+ * No `label_ref' or `scratch' appears in more than one place in the
RTL structure; in other words, it is safe to do a tree-walk of all
- the insns in the function and assume that each time a 'label_ref'
- or 'scratch' is seen it is distinct from all others that are seen.
+ the insns in the function and assume that each time a `label_ref'
+ or `scratch' is seen it is distinct from all others that are seen.
- * Only one 'mem' object is normally created for each static variable
+ * Only one `mem' object is normally created for each static variable
or stack slot, so these objects are frequently shared in all the
places they appear. However, separate but equal objects for these
variables are occasionally made.
- * When a single 'asm' statement has multiple output operands, a
- distinct 'asm_operands' expression is made for each output operand.
+ * When a single `asm' statement has multiple output operands, a
+ distinct `asm_operands' expression is made for each output operand.
However, these all share the vector which contains the sequence of
input operands. This sharing is used later on to test whether two
- 'asm_operands' expressions come from the same statement, so all
+ `asm_operands' expressions come from the same statement, so all
optimizations must carefully preserve the sharing if they copy the
vector at all.
@@ -17210,14 +17373,14 @@ common to two functions.
* During initial RTL generation, shared structure is freely
introduced. After all the RTL for a function has been generated,
- all shared structure is copied by 'unshare_all_rtl' in
- 'emit-rtl.c', after which the above rules are guaranteed to be
+ all shared structure is copied by `unshare_all_rtl' in
+ `emit-rtl.c', after which the above rules are guaranteed to be
followed.
* During the combiner pass, shared structure within an insn can exist
temporarily. However, the shared structure is copied before the
combiner is finished with the insn. This is done by calling
- 'copy_rtx_if_shared', which is a subroutine of 'unshare_all_rtl'.
+ `copy_rtx_if_shared', which is a subroutine of `unshare_all_rtl'.

File: gccint.info, Node: Reading RTL, Prev: Sharing, Up: RTL
@@ -17225,11 +17388,11 @@ File: gccint.info, Node: Reading RTL, Prev: Sharing, Up: RTL
13.22 Reading RTL
=================
-To read an RTL object from a file, call 'read_rtx'. It takes one
+To read an RTL object from a file, call `read_rtx'. It takes one
argument, a stdio stream, and returns a single RTL object. This routine
-is defined in 'read-rtl.c'. It is not available in the compiler itself,
-only the various programs that generate the compiler back end from the
-machine description.
+is defined in `read-rtl.c'. It is not available in the compiler
+itself, only the various programs that generate the compiler back end
+from the machine description.
People frequently have the idea of using RTL stored as text in a file
as an interface between a language front end and the bulk of GCC. This
@@ -17239,9 +17402,10 @@ idea is not feasible.
program is very dependent on the particular target machine. And the RTL
does not contain all the information about the program.
- The proper way to interface GCC to a new language front end is with the
-"tree" data structure, described in the files 'tree.h' and 'tree.def'.
-The documentation for this structure (*note GENERIC::) is incomplete.
+ The proper way to interface GCC to a new language front end is with
+the "tree" data structure, described in the files `tree.h' and
+`tree.def'. The documentation for this structure (*note GENERIC::) is
+incomplete.

File: gccint.info, Node: Control Flow, Next: Loop Analysis and Representation, Prev: RTL, Up: Top
@@ -17250,21 +17414,21 @@ File: gccint.info, Node: Control Flow, Next: Loop Analysis and Representation,
*********************
A control flow graph (CFG) is a data structure built on top of the
-intermediate code representation (the RTL or 'GIMPLE' instruction
+intermediate code representation (the RTL or `GIMPLE' instruction
stream) abstracting the control flow behavior of a function that is
being compiled. The CFG is a directed graph where the vertices
represent basic blocks and edges represent possible transfer of control
flow from one basic block to another. The data structures used to
-represent the control flow graph are defined in 'basic-block.h'.
+represent the control flow graph are defined in `basic-block.h'.
- In GCC, the representation of control flow is maintained throughout the
-compilation process, from constructing the CFG early in 'pass_build_cfg'
-to 'pass_free_cfg' (see 'passes.def'). The CFG takes various different
-modes and may undergo extensive manipulations, but the graph is always
-valid between its construction and its release. This way, transfer of
-information such as data flow, a measured profile, or the loop tree, can
-be propagated through the passes pipeline, and even from 'GIMPLE' to
-'RTL'.
+ In GCC, the representation of control flow is maintained throughout
+the compilation process, from constructing the CFG early in
+`pass_build_cfg' to `pass_free_cfg' (see `passes.def'). The CFG takes
+various different modes and may undergo extensive manipulations, but
+the graph is always valid between its construction and its release.
+This way, transfer of information such as data flow, a measured
+profile, or the loop tree, can be propagated through the passes
+pipeline, and even from `GIMPLE' to `RTL'.
Often the CFG may be better viewed as integral part of instruction
chain, than structure built on the top of it. Updating the compiler's
@@ -17286,50 +17450,50 @@ File: gccint.info, Node: Basic Blocks, Next: Edges, Up: Control Flow
=================
A basic block is a straight-line sequence of code with only one entry
-point and only one exit. In GCC, basic blocks are represented using the
-'basic_block' data type.
+point and only one exit. In GCC, basic blocks are represented using
+the `basic_block' data type.
Special basic blocks represent possible entry and exit points of a
-function. These blocks are called 'ENTRY_BLOCK_PTR' and
-'EXIT_BLOCK_PTR'. These blocks do not contain any code.
-
- The 'BASIC_BLOCK' array contains all basic blocks in an unspecified
-order. Each 'basic_block' structure has a field that holds a unique
-integer identifier 'index' that is the index of the block in the
-'BASIC_BLOCK' array. The total number of basic blocks in the function
-is 'n_basic_blocks'. Both the basic block indices and the total number
+function. These blocks are called `ENTRY_BLOCK_PTR' and
+`EXIT_BLOCK_PTR'. These blocks do not contain any code.
+
+ The `BASIC_BLOCK' array contains all basic blocks in an unspecified
+order. Each `basic_block' structure has a field that holds a unique
+integer identifier `index' that is the index of the block in the
+`BASIC_BLOCK' array. The total number of basic blocks in the function
+is `n_basic_blocks'. Both the basic block indices and the total number
of basic blocks may vary during the compilation process, as passes
-reorder, create, duplicate, and destroy basic blocks. The index for any
-block should never be greater than 'last_basic_block'. The indices 0
-and 1 are special codes reserved for 'ENTRY_BLOCK' and 'EXIT_BLOCK', the
-indices of 'ENTRY_BLOCK_PTR' and 'EXIT_BLOCK_PTR'.
+reorder, create, duplicate, and destroy basic blocks. The index for
+any block should never be greater than `last_basic_block'. The indices
+0 and 1 are special codes reserved for `ENTRY_BLOCK' and `EXIT_BLOCK',
+the indices of `ENTRY_BLOCK_PTR' and `EXIT_BLOCK_PTR'.
- Two pointer members of the 'basic_block' structure are the pointers
-'next_bb' and 'prev_bb'. These are used to keep doubly linked chain of
+ Two pointer members of the `basic_block' structure are the pointers
+`next_bb' and `prev_bb'. These are used to keep doubly linked chain of
basic blocks in the same order as the underlying instruction stream.
The chain of basic blocks is updated transparently by the provided API
-for manipulating the CFG. The macro 'FOR_EACH_BB' can be used to visit
-all the basic blocks in lexicographical order, except 'ENTRY_BLOCK' and
-'EXIT_BLOCK'. The macro 'FOR_ALL_BB' also visits all basic blocks in
-lexicographical order, including 'ENTRY_BLOCK' and 'EXIT_BLOCK'.
-
- The functions 'post_order_compute' and 'inverted_post_order_compute'
-can be used to compute topological orders of the CFG. The orders are
-stored as vectors of basic block indices. The 'BASIC_BLOCK' array can
+for manipulating the CFG. The macro `FOR_EACH_BB' can be used to visit
+all the basic blocks in lexicographical order, except `ENTRY_BLOCK' and
+`EXIT_BLOCK'. The macro `FOR_ALL_BB' also visits all basic blocks in
+lexicographical order, including `ENTRY_BLOCK' and `EXIT_BLOCK'.
+
+ The functions `post_order_compute' and `inverted_post_order_compute'
+can be used to compute topological orders of the CFG. The orders are
+stored as vectors of basic block indices. The `BASIC_BLOCK' array can
be used to iterate each basic block by index. Dominator traversals are
-also possible using 'walk_dominator_tree'. Given two basic blocks A and
-B, block A dominates block B if A is _always_ executed before B.
+also possible using `walk_dominator_tree'. Given two basic blocks A
+and B, block A dominates block B if A is _always_ executed before B.
- Each 'basic_block' also contains pointers to the first instruction (the
-"head") and the last instruction (the "tail") or "end" of the
+ Each `basic_block' also contains pointers to the first instruction
+(the "head") and the last instruction (the "tail") or "end" of the
instruction stream contained in a basic block. In fact, since the
-'basic_block' data type is used to represent blocks in both major
-intermediate representations of GCC ('GIMPLE' and RTL), there are
+`basic_block' data type is used to represent blocks in both major
+intermediate representations of GCC (`GIMPLE' and RTL), there are
pointers to the head and end of a basic block for both representations,
-stored in intermediate representation specific data in the 'il' field of
-'struct basic_block_def'.
+stored in intermediate representation specific data in the `il' field
+of `struct basic_block_def'.
- For RTL, these pointers are 'BB_HEAD' and 'BB_END'.
+ For RTL, these pointers are `BB_HEAD' and `BB_END'.
In the RTL representation of a function, the instruction stream
contains not only the "real" instructions, but also "notes" or "insn
@@ -17337,36 +17501,37 @@ notes" (to distinguish them from "reg notes"). Any function that moves
or duplicates the basic blocks needs to take care of updating of these
notes. Many of these notes expect that the instruction stream consists
of linear regions, so updating can sometimes be tedious. All types of
-insn notes are defined in 'insn-notes.def'.
+insn notes are defined in `insn-notes.def'.
In the RTL function representation, the instructions contained in a
-basic block always follow a 'NOTE_INSN_BASIC_BLOCK', but zero or more
-'CODE_LABEL' nodes can precede the block note. A basic block ends with
+basic block always follow a `NOTE_INSN_BASIC_BLOCK', but zero or more
+`CODE_LABEL' nodes can precede the block note. A basic block ends with
a control flow instruction or with the last instruction before the next
-'CODE_LABEL' or 'NOTE_INSN_BASIC_BLOCK'. By definition, a 'CODE_LABEL'
+`CODE_LABEL' or `NOTE_INSN_BASIC_BLOCK'. By definition, a `CODE_LABEL'
cannot appear in the middle of the instruction stream of a basic block.
In addition to notes, the jump table vectors are also represented as
"pseudo-instructions" inside the insn stream. These vectors never
appear in the basic block and should always be placed just after the
-table jump instructions referencing them. After removing the table-jump
-it is often difficult to eliminate the code computing the address and
-referencing the vector, so cleaning up these vectors is postponed until
-after liveness analysis. Thus the jump table vectors may appear in the
-insn stream unreferenced and without any purpose. Before any edge is
-made "fall-thru", the existence of such construct in the way needs to be
-checked by calling 'can_fallthru' function.
-
- For the 'GIMPLE' representation, the PHI nodes and statements contained
-in a basic block are in a 'gimple_seq' pointed to by the basic block
-intermediate language specific pointers. Abstract containers and
-iterators are used to access the PHI nodes and statements in a basic
-blocks. These iterators are called "GIMPLE statement iterators" (GSIs).
-Grep for '^gsi' in the various 'gimple-*' and 'tree-*' files. There is
-a 'gimple_stmt_iterator' type for iterating over all kinds of statement,
-and a 'gphi_iterator' subclass for iterating over PHI nodes. The
-following snippet will pretty-print all PHI nodes the statements of the
-current function in the GIMPLE representation.
+table jump instructions referencing them. After removing the
+table-jump it is often difficult to eliminate the code computing the
+address and referencing the vector, so cleaning up these vectors is
+postponed until after liveness analysis. Thus the jump table vectors
+may appear in the insn stream unreferenced and without any purpose.
+Before any edge is made "fall-thru", the existence of such construct in
+the way needs to be checked by calling `can_fallthru' function.
+
+ For the `GIMPLE' representation, the PHI nodes and statements
+contained in a basic block are in a `gimple_seq' pointed to by the
+basic block intermediate language specific pointers. Abstract
+containers and iterators are used to access the PHI nodes and
+statements in a basic blocks. These iterators are called "GIMPLE
+statement iterators" (GSIs). Grep for `^gsi' in the various `gimple-*'
+and `tree-*' files. There is a `gimple_stmt_iterator' type for
+iterating over all kinds of statement, and a `gphi_iterator' subclass
+for iterating over PHI nodes. The following snippet will pretty-print
+all PHI nodes the statements of the current function in the GIMPLE
+representation.
basic_block bb;
@@ -17396,52 +17561,53 @@ File: gccint.info, Node: Edges, Next: Profile information, Prev: Basic Blocks
Edges represent possible control flow transfers from the end of some
basic block A to the head of another basic block B. We say that A is a
predecessor of B, and B is a successor of A. Edges are represented in
-GCC with the 'edge' data type. Each 'edge' acts as a link between two
-basic blocks: The 'src' member of an edge points to the predecessor
-basic block of the 'dest' basic block. The members 'preds' and 'succs'
-of the 'basic_block' data type point to type-safe vectors of edges to
+GCC with the `edge' data type. Each `edge' acts as a link between two
+basic blocks: The `src' member of an edge points to the predecessor
+basic block of the `dest' basic block. The members `preds' and `succs'
+of the `basic_block' data type point to type-safe vectors of edges to
the predecessors and successors of the block.
When walking the edges in an edge vector, "edge iterators" should be
-used. Edge iterators are constructed using the 'edge_iterator' data
+used. Edge iterators are constructed using the `edge_iterator' data
structure and several methods are available to operate on them:
-'ei_start'
- This function initializes an 'edge_iterator' that points to the
+`ei_start'
+ This function initializes an `edge_iterator' that points to the
first edge in a vector of edges.
-'ei_last'
- This function initializes an 'edge_iterator' that points to the
+`ei_last'
+ This function initializes an `edge_iterator' that points to the
last edge in a vector of edges.
-'ei_end_p'
- This predicate is 'true' if an 'edge_iterator' represents the last
+`ei_end_p'
+ This predicate is `true' if an `edge_iterator' represents the last
edge in an edge vector.
-'ei_one_before_end_p'
- This predicate is 'true' if an 'edge_iterator' represents the
+`ei_one_before_end_p'
+ This predicate is `true' if an `edge_iterator' represents the
second last edge in an edge vector.
-'ei_next'
- This function takes a pointer to an 'edge_iterator' and makes it
+`ei_next'
+ This function takes a pointer to an `edge_iterator' and makes it
point to the next edge in the sequence.
-'ei_prev'
- This function takes a pointer to an 'edge_iterator' and makes it
+`ei_prev'
+ This function takes a pointer to an `edge_iterator' and makes it
point to the previous edge in the sequence.
-'ei_edge'
- This function returns the 'edge' currently pointed to by an
- 'edge_iterator'.
+`ei_edge'
+ This function returns the `edge' currently pointed to by an
+ `edge_iterator'.
-'ei_safe_safe'
- This function returns the 'edge' currently pointed to by an
- 'edge_iterator', but returns 'NULL' if the iterator is pointing at
+`ei_safe_safe'
+ This function returns the `edge' currently pointed to by an
+ `edge_iterator', but returns `NULL' if the iterator is pointing at
the end of the sequence. This function has been provided for
- existing code makes the assumption that a 'NULL' edge indicates the
- end of the sequence.
+ existing code makes the assumption that a `NULL' edge indicates
+ the end of the sequence.
- The convenience macro 'FOR_EACH_EDGE' can be used to visit all of the
+
+ The convenience macro `FOR_EACH_EDGE' can be used to visit all of the
edges in a sequence of predecessor or successor edges. It must not be
used when an element might be removed during the traversal, otherwise
elements will be missed. Here is an example of how to use the macro:
@@ -17457,12 +17623,12 @@ elements will be missed. Here is an example of how to use the macro:
There are various reasons why control flow may transfer from one block
to another. One possibility is that some instruction, for example a
-'CODE_LABEL', in a linearized instruction stream just always starts a
+`CODE_LABEL', in a linearized instruction stream just always starts a
new basic block. In this case a "fall-thru" edge links the basic block
-to the first following basic block. But there are several other reasons
-why edges may be created. The 'flags' field of the 'edge' data type is
-used to store information about the type of edge we are dealing with.
-Each edge is of one of the following types:
+to the first following basic block. But there are several other
+reasons why edges may be created. The `flags' field of the `edge' data
+type is used to store information about the type of edge we are dealing
+with. Each edge is of one of the following types:
_jump_
No type flags are set for edges corresponding to jump instructions.
@@ -17474,12 +17640,12 @@ _jump_
_fall-thru_
Fall-thru edges are present in case where the basic block may
continue execution to the following one without branching. These
- edges have the 'EDGE_FALLTHRU' flag set. Unlike other types of
+ edges have the `EDGE_FALLTHRU' flag set. Unlike other types of
edges, these edges must come into the basic block immediately
following in the instruction stream. The function
- 'force_nonfallthru' is available to insert an unconditional jump in
- the case that redirection is needed. Note that this may require
- creation of a new basic block.
+ `force_nonfallthru' is available to insert an unconditional jump
+ in the case that redirection is needed. Note that this may
+ require creation of a new basic block.
_exception handling_
Exception handling edges represent possible control transfers from
@@ -17488,34 +17654,34 @@ _exception handling_
Java and Ada, exceptions like division by zero or segmentation
fault are defined and thus each instruction possibly throwing this
kind of exception needs to be handled as control flow instruction.
- Exception edges have the 'EDGE_ABNORMAL' and 'EDGE_EH' flags set.
+ Exception edges have the `EDGE_ABNORMAL' and `EDGE_EH' flags set.
When updating the instruction stream it is easy to change possibly
trapping instruction to non-trapping, by simply removing the
exception edge. The opposite conversion is difficult, but should
not happen anyway. The edges can be eliminated via
- 'purge_dead_edges' call.
+ `purge_dead_edges' call.
In the RTL representation, the destination of an exception edge is
- specified by 'REG_EH_REGION' note attached to the insn. In case of
- a trapping call the 'EDGE_ABNORMAL_CALL' flag is set too. In the
- 'GIMPLE' representation, this extra flag is not set.
+ specified by `REG_EH_REGION' note attached to the insn. In case
+ of a trapping call the `EDGE_ABNORMAL_CALL' flag is set too. In
+ the `GIMPLE' representation, this extra flag is not set.
- In the RTL representation, the predicate 'may_trap_p' may be used
+ In the RTL representation, the predicate `may_trap_p' may be used
to check whether instruction still may trap or not. For the tree
- representation, the 'tree_could_trap_p' predicate is available, but
- this predicate only checks for possible memory traps, as in
+ representation, the `tree_could_trap_p' predicate is available,
+ but this predicate only checks for possible memory traps, as in
dereferencing an invalid pointer location.
_sibling calls_
Sibling calls or tail calls terminate the function in a
non-standard way and thus an edge to the exit must be present.
- 'EDGE_SIBCALL' and 'EDGE_ABNORMAL' are set in such case. These
+ `EDGE_SIBCALL' and `EDGE_ABNORMAL' are set in such case. These
edges only exist in the RTL representation.
_computed jumps_
Computed jumps contain edges to all labels in the function
- referenced from the code. All those edges have 'EDGE_ABNORMAL'
+ referenced from the code. All those edges have `EDGE_ABNORMAL'
flag set. The edges used to represent computed jumps often cause
compile time performance problems, since functions consisting of
many taken labels and many computed jumps may have _very_ dense
@@ -17552,28 +17718,28 @@ _computed jumps_
has a runtime cost in there resulting code: An extra jump.
Therefore, the computed jumps are un-factored in the later passes
of the compiler (in the pass called
- 'pass_duplicate_computed_gotos'). Be aware of that when you work
+ `pass_duplicate_computed_gotos'). Be aware of that when you work
on passes in that area. There have been numerous examples already
where the compile time for code with unfactored computed jumps
caused some serious headaches.
_nonlocal goto handlers_
- GCC allows nested functions to return into caller using a 'goto' to
- a label passed to as an argument to the callee. The labels passed
- to nested functions contain special code to cleanup after function
- call. Such sections of code are referred to as "nonlocal goto
- receivers". If a function contains such nonlocal goto receivers,
- an edge from the call to the label is created with the
- 'EDGE_ABNORMAL' and 'EDGE_ABNORMAL_CALL' flags set.
+ GCC allows nested functions to return into caller using a `goto'
+ to a label passed to as an argument to the callee. The labels
+ passed to nested functions contain special code to cleanup after
+ function call. Such sections of code are referred to as "nonlocal
+ goto receivers". If a function contains such nonlocal goto
+ receivers, an edge from the call to the label is created with the
+ `EDGE_ABNORMAL' and `EDGE_ABNORMAL_CALL' flags set.
_function entry points_
By definition, execution of function starts at basic block 0, so
- there is always an edge from the 'ENTRY_BLOCK_PTR' to basic block
- 0. There is no 'GIMPLE' representation for alternate entry points
+ there is always an edge from the `ENTRY_BLOCK_PTR' to basic block
+ 0. There is no `GIMPLE' representation for alternate entry points
at this moment. In RTL, alternate entry points are specified by
- 'CODE_LABEL' with 'LABEL_ALTERNATE_NAME' defined. This feature is
- currently used for multiple entry point prologues and is limited to
- post-reload passes only. This can be used by back-ends to emit
+ `CODE_LABEL' with `LABEL_ALTERNATE_NAME' defined. This feature is
+ currently used for multiple entry point prologues and is limited
+ to post-reload passes only. This can be used by back-ends to emit
alternate prologues for functions called from different contexts.
In future full support for multiple entry functions defined by
Fortran 90 needs to be implemented.
@@ -17581,10 +17747,11 @@ _function entry points_
_function exits_
In the pre-reload representation a function terminates after the
last instruction in the insn chain and no explicit return
- instructions are used. This corresponds to the fall-thru edge into
- exit block. After reload, optimal RTL epilogues are used that use
- explicit (conditional) return instructions that are represented by
- edges with no flags set.
+ instructions are used. This corresponds to the fall-thru edge
+ into exit block. After reload, optimal RTL epilogues are used
+ that use explicit (conditional) return instructions that are
+ represented by edges with no flags set.
+

File: gccint.info, Node: Profile information, Next: Maintaining the CFG, Prev: Edges, Up: Control Flow
@@ -17605,32 +17772,32 @@ instrumentation, executing it on a train run and reading the numbers of
executions of basic blocks and edges back to the compiler while
re-compiling the program to produce the final executable. This method
provides very accurate information about where a program spends most of
-its time on the train run. Whether it matches the average run of course
-depends on the choice of train data set, but several studies have shown
-that the behavior of a program usually changes just marginally over
-different data sets.
+its time on the train run. Whether it matches the average run of
+course depends on the choice of train data set, but several studies
+have shown that the behavior of a program usually changes just
+marginally over different data sets.
When profile feedback is not available, the compiler may be asked to
attempt to predict the behavior of each branch in the program using a
-set of heuristics (see 'predict.def' for details) and compute estimated
+set of heuristics (see `predict.def' for details) and compute estimated
frequencies of each basic block by propagating the probabilities over
the graph.
- Each 'basic_block' contains two integer fields to represent profile
-information: 'frequency' and 'count'. The 'frequency' is an estimation
+ Each `basic_block' contains two integer fields to represent profile
+information: `frequency' and `count'. The `frequency' is an estimation
how often is basic block executed within a function. It is represented
-as an integer scaled in the range from 0 to 'BB_FREQ_BASE'. The most
+as an integer scaled in the range from 0 to `BB_FREQ_BASE'. The most
frequently executed basic block in function is initially set to
-'BB_FREQ_BASE' and the rest of frequencies are scaled accordingly.
+`BB_FREQ_BASE' and the rest of frequencies are scaled accordingly.
During optimization, the frequency of the most frequent basic block can
both decrease (for instance by loop unrolling) or grow (for instance by
cross-jumping optimization), so scaling sometimes has to be performed
multiple times.
- The 'count' contains hard-counted numbers of execution measured during
+ The `count' contains hard-counted numbers of execution measured during
training runs and is nonzero only when profile feedback is available.
This value is represented as the host's widest integer (typically a 64
-bit integer) of the special type 'gcov_type'.
+bit integer) of the special type `gcov_type'.
Most optimization passes can use only the frequency information of a
basic block, but a few passes may want to know hard execution counts.
@@ -17639,16 +17806,16 @@ during updating of the profile information numerical error may
accumulate into quite large errors.
Each edge also contains a branch probability field: an integer in the
-range from 0 to 'REG_BR_PROB_BASE'. It represents probability of
-passing control from the end of the 'src' basic block to the 'dest'
+range from 0 to `REG_BR_PROB_BASE'. It represents probability of
+passing control from the end of the `src' basic block to the `dest'
basic block, i.e. the probability that control will flow along this
-edge. The 'EDGE_FREQUENCY' macro is available to compute how frequently
-a given edge is taken. There is a 'count' field for each edge as well,
-representing same information as for a basic block.
+edge. The `EDGE_FREQUENCY' macro is available to compute how
+frequently a given edge is taken. There is a `count' field for each
+edge as well, representing same information as for a basic block.
The basic block frequencies are not represented in the instruction
stream, but in the RTL representation the edge frequencies are
-represented for conditional jumps (via the 'REG_BR_PROB' macro) since
+represented for conditional jumps (via the `REG_BR_PROB' macro) since
they are used when instructions are output to the assembly file and the
flow graph is no longer maintained.
@@ -17660,19 +17827,19 @@ basic blocks.
Updating profile information is a delicate task that can unfortunately
not be easily integrated with the CFG manipulation API. Many of the
functions and hooks to modify the CFG, such as
-'redirect_edge_and_branch', do not have enough information to easily
+`redirect_edge_and_branch', do not have enough information to easily
update the profile, so updating it is in the majority of cases left up
to the caller. It is difficult to uncover bugs in the profile updating
-code, because they manifest themselves only by producing worse code, and
-checking profile consistency is not possible because of numeric error
-accumulation. Hence special attention needs to be given to this issue
-in each pass that modifies the CFG.
+code, because they manifest themselves only by producing worse code,
+and checking profile consistency is not possible because of numeric
+error accumulation. Hence special attention needs to be given to this
+issue in each pass that modifies the CFG.
- It is important to point out that 'REG_BR_PROB_BASE' and 'BB_FREQ_BASE'
-are both set low enough to be possible to compute second power of any
-frequency or probability in the flow graph, it is not possible to even
-square the 'count' field, as modern CPUs are fast enough to execute
-$2^32$ operations quickly.
+ It is important to point out that `REG_BR_PROB_BASE' and
+`BB_FREQ_BASE' are both set low enough to be possible to compute second
+power of any frequency or probability in the flow graph, it is not
+possible to even square the `count' field, as modern CPUs are fast
+enough to execute $2^32$ operations quickly.

File: gccint.info, Node: Maintaining the CFG, Next: Liveness information, Prev: Profile information, Up: Control Flow
@@ -17680,118 +17847,120 @@ File: gccint.info, Node: Maintaining the CFG, Next: Liveness information, Pre
14.4 Maintaining the CFG
========================
-An important task of each compiler pass is to keep both the control flow
-graph and all profile information up-to-date. Reconstruction of the
-control flow graph after each pass is not an option, since it may be
+An important task of each compiler pass is to keep both the control
+flow graph and all profile information up-to-date. Reconstruction of
+the control flow graph after each pass is not an option, since it may be
very expensive and lost profile information cannot be reconstructed at
all.
GCC has two major intermediate representations, and both use the
-'basic_block' and 'edge' data types to represent control flow. Both
+`basic_block' and `edge' data types to represent control flow. Both
representations share as much of the CFG maintenance code as possible.
For each representation, a set of "hooks" is defined so that each
representation can provide its own implementation of CFG manipulation
-routines when necessary. These hooks are defined in 'cfghooks.h'.
-There are hooks for almost all common CFG manipulations, including block
-splitting and merging, edge redirection and creating and deleting basic
-blocks. These hooks should provide everything you need to maintain and
-manipulate the CFG in both the RTL and 'GIMPLE' representation.
+routines when necessary. These hooks are defined in `cfghooks.h'.
+There are hooks for almost all common CFG manipulations, including
+block splitting and merging, edge redirection and creating and deleting
+basic blocks. These hooks should provide everything you need to
+maintain and manipulate the CFG in both the RTL and `GIMPLE'
+representation.
At the moment, the basic block boundaries are maintained transparently
when modifying instructions, so there rarely is a need to move them
manually (such as in case someone wants to output instruction outside
basic block explicitly).
- In the RTL representation, each instruction has a 'BLOCK_FOR_INSN'
+ In the RTL representation, each instruction has a `BLOCK_FOR_INSN'
value that represents pointer to the basic block that contains the
-instruction. In the 'GIMPLE' representation, the function 'gimple_bb'
+instruction. In the `GIMPLE' representation, the function `gimple_bb'
returns a pointer to the basic block containing the queried statement.
- When changes need to be applied to a function in its 'GIMPLE'
+ When changes need to be applied to a function in its `GIMPLE'
representation, "GIMPLE statement iterators" should be used. These
iterators provide an integrated abstraction of the flow graph and the
-instruction stream. Block statement iterators are constructed using the
-'gimple_stmt_iterator' data structure and several modifiers are
+instruction stream. Block statement iterators are constructed using
+the `gimple_stmt_iterator' data structure and several modifiers are
available, including the following:
-'gsi_start'
- This function initializes a 'gimple_stmt_iterator' that points to
+`gsi_start'
+ This function initializes a `gimple_stmt_iterator' that points to
the first non-empty statement in a basic block.
-'gsi_last'
- This function initializes a 'gimple_stmt_iterator' that points to
+`gsi_last'
+ This function initializes a `gimple_stmt_iterator' that points to
the last statement in a basic block.
-'gsi_end_p'
- This predicate is 'true' if a 'gimple_stmt_iterator' represents the
- end of a basic block.
+`gsi_end_p'
+ This predicate is `true' if a `gimple_stmt_iterator' represents
+ the end of a basic block.
-'gsi_next'
- This function takes a 'gimple_stmt_iterator' and makes it point to
+`gsi_next'
+ This function takes a `gimple_stmt_iterator' and makes it point to
its successor.
-'gsi_prev'
- This function takes a 'gimple_stmt_iterator' and makes it point to
+`gsi_prev'
+ This function takes a `gimple_stmt_iterator' and makes it point to
its predecessor.
-'gsi_insert_after'
- This function inserts a statement after the 'gimple_stmt_iterator'
+`gsi_insert_after'
+ This function inserts a statement after the `gimple_stmt_iterator'
passed in. The final parameter determines whether the statement
iterator is updated to point to the newly inserted statement, or
left pointing to the original statement.
-'gsi_insert_before'
- This function inserts a statement before the 'gimple_stmt_iterator'
+`gsi_insert_before'
+ This function inserts a statement before the `gimple_stmt_iterator'
passed in. The final parameter determines whether the statement
iterator is updated to point to the newly inserted statement, or
- left pointing to the original statement.
+ left pointing to the original statement.
-'gsi_remove'
- This function removes the 'gimple_stmt_iterator' passed in and
+`gsi_remove'
+ This function removes the `gimple_stmt_iterator' passed in and
rechains the remaining statements in a basic block, if any.
- In the RTL representation, the macros 'BB_HEAD' and 'BB_END' may be
-used to get the head and end 'rtx' of a basic block. No abstract
+ In the RTL representation, the macros `BB_HEAD' and `BB_END' may be
+used to get the head and end `rtx' of a basic block. No abstract
iterators are defined for traversing the insn chain, but you can just
-use 'NEXT_INSN' and 'PREV_INSN' instead. *Note Insns::.
+use `NEXT_INSN' and `PREV_INSN' instead. *Note Insns::.
Usually a code manipulating pass simplifies the instruction stream and
the flow of control, possibly eliminating some edges. This may for
-example happen when a conditional jump is replaced with an unconditional
-jump, but also when simplifying possibly trapping instruction to
-non-trapping while compiling Java. Updating of edges is not transparent
-and each optimization pass is required to do so manually. However only
-few cases occur in practice. The pass may call 'purge_dead_edges' on a
-given basic block to remove superfluous edges, if any.
-
- Another common scenario is redirection of branch instructions, but this
-is best modeled as redirection of edges in the control flow graph and
-thus use of 'redirect_edge_and_branch' is preferred over more low level
-functions, such as 'redirect_jump' that operate on RTL chain only. The
-CFG hooks defined in 'cfghooks.h' should provide the complete API
-required for manipulating and maintaining the CFG.
+example happen when a conditional jump is replaced with an
+unconditional jump, but also when simplifying possibly trapping
+instruction to non-trapping while compiling Java. Updating of edges is
+not transparent and each optimization pass is required to do so
+manually. However only few cases occur in practice. The pass may call
+`purge_dead_edges' on a given basic block to remove superfluous edges,
+if any.
+
+ Another common scenario is redirection of branch instructions, but
+this is best modeled as redirection of edges in the control flow graph
+and thus use of `redirect_edge_and_branch' is preferred over more low
+level functions, such as `redirect_jump' that operate on RTL chain
+only. The CFG hooks defined in `cfghooks.h' should provide the
+complete API required for manipulating and maintaining the CFG.
It is also possible that a pass has to insert control flow instruction
into the middle of a basic block, thus creating an entry point in the
middle of the basic block, which is impossible by definition: The block
-must be split to make sure it only has one entry point, i.e. the head of
-the basic block. The CFG hook 'split_block' may be used when an
-instruction in the middle of a basic block has to become the target of a
-jump or branch instruction.
+must be split to make sure it only has one entry point, i.e. the head
+of the basic block. The CFG hook `split_block' may be used when an
+instruction in the middle of a basic block has to become the target of
+a jump or branch instruction.
For a global optimizer, a common operation is to split edges in the
flow graph and insert instructions on them. In the RTL representation,
-this can be easily done using the 'insert_insn_on_edge' function that
+this can be easily done using the `insert_insn_on_edge' function that
emits an instruction "on the edge", caching it for a later
-'commit_edge_insertions' call that will take care of moving the inserted
-instructions off the edge into the instruction stream contained in a
-basic block. This includes the creation of new basic blocks where
-needed. In the 'GIMPLE' representation, the equivalent functions are
-'gsi_insert_on_edge' which inserts a block statement iterator on an
-edge, and 'gsi_commit_edge_inserts' which flushes the instruction to
-actual instruction stream.
-
- While debugging the optimization pass, the 'verify_flow_info' function
+`commit_edge_insertions' call that will take care of moving the
+inserted instructions off the edge into the instruction stream
+contained in a basic block. This includes the creation of new basic
+blocks where needed. In the `GIMPLE' representation, the equivalent
+functions are `gsi_insert_on_edge' which inserts a block statement
+iterator on an edge, and `gsi_commit_edge_inserts' which flushes the
+instruction to actual instruction stream.
+
+ While debugging the optimization pass, the `verify_flow_info' function
may be useful to find bugs in the control flow graph updating code.

@@ -17801,36 +17970,36 @@ File: gccint.info, Node: Liveness information, Prev: Maintaining the CFG, Up:
=========================
Liveness information is useful to determine whether some register is
-"live" at given point of program, i.e. that it contains a value that may
-be used at a later point in the program. This information is used, for
-instance, during register allocation, as the pseudo registers only need
-to be assigned to a unique hard register or to a stack slot if they are
-live. The hard registers and stack slots may be freely reused for other
-values when a register is dead.
+"live" at given point of program, i.e. that it contains a value that
+may be used at a later point in the program. This information is used,
+for instance, during register allocation, as the pseudo registers only
+need to be assigned to a unique hard register or to a stack slot if
+they are live. The hard registers and stack slots may be freely reused
+for other values when a register is dead.
Liveness information is available in the back end starting with
-'pass_df_initialize' and ending with 'pass_df_finish'. Three flavors of
-live analysis are available: With 'LR', it is possible to determine at
-any point 'P' in the function if the register may be used on some path
-from 'P' to the end of the function. With 'UR', it is possible to
-determine if there is a path from the beginning of the function to 'P'
-that defines the variable. 'LIVE' is the intersection of the 'LR' and
-'UR' and a variable is live at 'P' if there is both an assignment that
+`pass_df_initialize' and ending with `pass_df_finish'. Three flavors
+of live analysis are available: With `LR', it is possible to determine
+at any point `P' in the function if the register may be used on some
+path from `P' to the end of the function. With `UR', it is possible to
+determine if there is a path from the beginning of the function to `P'
+that defines the variable. `LIVE' is the intersection of the `LR' and
+`UR' and a variable is live at `P' if there is both an assignment that
reaches it from the beginning of the function and a use that can be
-reached on some path from 'P' to the end of the function.
+reached on some path from `P' to the end of the function.
- In general 'LIVE' is the most useful of the three. The macros
-'DF_[LR,UR,LIVE]_[IN,OUT]' can be used to access this information. The
+ In general `LIVE' is the most useful of the three. The macros
+`DF_[LR,UR,LIVE]_[IN,OUT]' can be used to access this information. The
macros take a basic block number and return a bitmap that is indexed by
the register number. This information is only guaranteed to be up to
-date after calls are made to 'df_analyze'. See the file 'df-core.c' for
-details on using the dataflow.
+date after calls are made to `df_analyze'. See the file `df-core.c'
+for details on using the dataflow.
The liveness information is stored partly in the RTL instruction stream
and partly in the flow graph. Local information is stored in the
-instruction stream: Each instruction may contain 'REG_DEAD' notes
+instruction stream: Each instruction may contain `REG_DEAD' notes
representing that the value of a given register is no longer needed, or
-'REG_UNUSED' notes representing that the value computed by the
+`REG_UNUSED' notes representing that the value computed by the
instruction is never used. The second is useful for instructions
computing multiple values at once.
@@ -17866,9 +18035,9 @@ File: gccint.info, Node: Loop representation, Next: Loop querying, Up: Loop A
This chapter describes the representation of loops in GCC, and functions
that can be used to build, modify and analyze this representation. Most
-of the interfaces and data structures are declared in 'cfgloop.h'. Loop
-structures are analyzed and this information disposed or updated at the
-discretion of individual passes. Still most of the generic CFG
+of the interfaces and data structures are declared in `cfgloop.h'.
+Loop structures are analyzed and this information disposed or updated
+at the discretion of individual passes. Still most of the generic CFG
manipulation routines are aware of loop structures and try to keep them
up-to-date. By this means an increasing part of the compilation
pipeline is setup to maintain loop structure across passes to allow
@@ -17888,7 +18057,7 @@ correspond to sub-loops or to control flow in a single loop. This means
that the analysis sometimes changes the CFG, and if you run it in the
middle of an optimization pass, you must be able to deal with the new
blocks. You may avoid CFG changes by passing
-'LOOPS_MAY_HAVE_MULTIPLE_LATCHES' flag to the loop discovery, note
+`LOOPS_MAY_HAVE_MULTIPLE_LATCHES' flag to the loop discovery, note
however that most other loop manipulation functions will not work
correctly for loops with multiple latch edges (the functions that only
query membership of blocks to loops and subloop relationships, or
@@ -17898,57 +18067,59 @@ enumerate and test loop exits, can be expected to work).
and reachable from its latch against the direction of edges in CFG. The
loops are organized in a containment hierarchy (tree) such that all the
loops immediately contained inside loop L are the children of L in the
-tree. This tree is represented by the 'struct loops' structure. The
+tree. This tree is represented by the `struct loops' structure. The
root of this tree is a fake loop that contains all blocks in the
-function. Each of the loops is represented in a 'struct loop'
-structure. Each loop is assigned an index ('num' field of the 'struct
+function. Each of the loops is represented in a `struct loop'
+structure. Each loop is assigned an index (`num' field of the `struct
loop' structure), and the pointer to the loop is stored in the
-corresponding field of the 'larray' vector in the loops structure. The
-indices do not have to be continuous, there may be empty ('NULL')
-entries in the 'larray' created by deleting loops. Also, there is no
+corresponding field of the `larray' vector in the loops structure. The
+indices do not have to be continuous, there may be empty (`NULL')
+entries in the `larray' created by deleting loops. Also, there is no
guarantee on the relative order of a loop and its subloops in the
numbering. The index of a loop never changes.
- The entries of the 'larray' field should not be accessed directly. The
-function 'get_loop' returns the loop description for a loop with the
-given index. 'number_of_loops' function returns number of loops in the
-function. To traverse all loops, use 'FOR_EACH_LOOP' macro. The
-'flags' argument of the macro is used to determine the direction of
+ The entries of the `larray' field should not be accessed directly.
+The function `get_loop' returns the loop description for a loop with
+the given index. `number_of_loops' function returns number of loops in
+the function. To traverse all loops, use `FOR_EACH_LOOP' macro. The
+`flags' argument of the macro is used to determine the direction of
traversal and the set of loops visited. Each loop is guaranteed to be
visited exactly once, regardless of the changes to the loop tree, and
the loops may be removed during the traversal. The newly created loops
are never traversed, if they need to be visited, this must be done
-separately after their creation. The 'FOR_EACH_LOOP' macro allocates
-temporary variables. If the 'FOR_EACH_LOOP' loop were ended using break
-or goto, they would not be released; 'FOR_EACH_LOOP_BREAK' macro must be
-used instead.
+separately after their creation. The `FOR_EACH_LOOP' macro allocates
+temporary variables. If the `FOR_EACH_LOOP' loop were ended using
+break or goto, they would not be released; `FOR_EACH_LOOP_BREAK' macro
+must be used instead.
Each basic block contains the reference to the innermost loop it
-belongs to ('loop_father'). For this reason, it is only possible to
-have one 'struct loops' structure initialized at the same time for each
-CFG. The global variable 'current_loops' contains the 'struct loops'
+belongs to (`loop_father'). For this reason, it is only possible to
+have one `struct loops' structure initialized at the same time for each
+CFG. The global variable `current_loops' contains the `struct loops'
structure. Many of the loop manipulation functions assume that
dominance information is up-to-date.
- The loops are analyzed through 'loop_optimizer_init' function. The
+ The loops are analyzed through `loop_optimizer_init' function. The
argument of this function is a set of flags represented in an integer
bitmask. These flags specify what other properties of the loop
structures should be calculated/enforced and preserved later:
- * 'LOOPS_MAY_HAVE_MULTIPLE_LATCHES': If this flag is set, no changes
- to CFG will be performed in the loop analysis, in particular, loops
- with multiple latch edges will not be disambiguated. If a loop has
- multiple latches, its latch block is set to NULL. Most of the loop
- manipulation functions will not work for loops in this shape. No
- other flags that require CFG changes can be passed to
+ * `LOOPS_MAY_HAVE_MULTIPLE_LATCHES': If this flag is set, no changes
+ to CFG will be performed in the loop analysis, in particular,
+ loops with multiple latch edges will not be disambiguated. If a
+ loop has multiple latches, its latch block is set to NULL. Most of
+ the loop manipulation functions will not work for loops in this
+ shape. No other flags that require CFG changes can be passed to
loop_optimizer_init.
- * 'LOOPS_HAVE_PREHEADERS': Forwarder blocks are created in such a way
- that each loop has only one entry edge, and additionally, the
+
+ * `LOOPS_HAVE_PREHEADERS': Forwarder blocks are created in such a
+ way that each loop has only one entry edge, and additionally, the
source block of this entry edge has only one successor. This
creates a natural place where the code can be moved out of the
loop, and ensures that the entry edge of the loop leads from its
immediate super-loop.
- * 'LOOPS_HAVE_SIMPLE_LATCHES': Forwarder blocks are created to force
+
+ * `LOOPS_HAVE_SIMPLE_LATCHES': Forwarder blocks are created to force
the latch block of each loop to have only one successor. This
ensures that the latch of the loop does not belong to any of its
sub-loops, and makes manipulation with the loops significantly
@@ -17956,38 +18127,40 @@ structures should be calculated/enforced and preserved later:
loops are in this shape. Note that with this flag, the "normal"
loop without any control flow inside and with one exit consists of
two basic blocks.
- * 'LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS': Basic blocks and edges in
+
+ * `LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS': Basic blocks and edges in
the strongly connected components that are not natural loops (have
- more than one entry block) are marked with 'BB_IRREDUCIBLE_LOOP'
- and 'EDGE_IRREDUCIBLE_LOOP' flags. The flag is not set for blocks
+ more than one entry block) are marked with `BB_IRREDUCIBLE_LOOP'
+ and `EDGE_IRREDUCIBLE_LOOP' flags. The flag is not set for blocks
and edges that belong to natural loops that are in such an
irreducible region (but it is set for the entry and exit edges of
such a loop, if they lead to/from this region).
- * 'LOOPS_HAVE_RECORDED_EXITS': The lists of exits are recorded and
+
+ * `LOOPS_HAVE_RECORDED_EXITS': The lists of exits are recorded and
updated for each loop. This makes some functions (e.g.,
- 'get_loop_exit_edges') more efficient. Some functions (e.g.,
- 'single_exit') can be used only if the lists of exits are recorded.
+ `get_loop_exit_edges') more efficient. Some functions (e.g.,
+ `single_exit') can be used only if the lists of exits are recorded.
These properties may also be computed/enforced later, using functions
-'create_preheaders', 'force_single_succ_latches',
-'mark_irreducible_loops' and 'record_loop_exits'. The properties can be
-queried using 'loops_state_satisfies_p'.
+`create_preheaders', `force_single_succ_latches',
+`mark_irreducible_loops' and `record_loop_exits'. The properties can
+be queried using `loops_state_satisfies_p'.
The memory occupied by the loops structures should be freed with
-'loop_optimizer_finalize' function. When loop structures are setup to
+`loop_optimizer_finalize' function. When loop structures are setup to
be preserved across passes this function reduces the information to be
-kept up-to-date to a minimum (only 'LOOPS_MAY_HAVE_MULTIPLE_LATCHES'
+kept up-to-date to a minimum (only `LOOPS_MAY_HAVE_MULTIPLE_LATCHES'
set).
The CFG manipulation functions in general do not update loop
structures. Specialized versions that additionally do so are provided
-for the most common tasks. On GIMPLE, 'cleanup_tree_cfg_loop' function
+for the most common tasks. On GIMPLE, `cleanup_tree_cfg_loop' function
can be used to cleanup CFG while updating the loops structures if
-'current_loops' is set.
+`current_loops' is set.
- At the moment loop structure is preserved from the start of GIMPLE loop
-optimizations until the end of RTL loop optimizations. During this time
-a loop can be tracked by its 'struct loop' and number.
+ At the moment loop structure is preserved from the start of GIMPLE
+loop optimizations until the end of RTL loop optimizations. During
+this time a loop can be tracked by its `struct loop' and number.

File: gccint.info, Node: Loop querying, Next: Loop manipulation, Prev: Loop representation, Up: Loop Analysis and Representation
@@ -17996,17 +18169,20 @@ File: gccint.info, Node: Loop querying, Next: Loop manipulation, Prev: Loop r
==================
The functions to query the information about loops are declared in
-'cfgloop.h'. Some of the information can be taken directly from the
-structures. 'loop_father' field of each basic block contains the
+`cfgloop.h'. Some of the information can be taken directly from the
+structures. `loop_father' field of each basic block contains the
innermost loop to that the block belongs. The most useful fields of
loop structure (that are kept up-to-date at all times) are:
- * 'header', 'latch': Header and latch basic blocks of the loop.
- * 'num_nodes': Number of basic blocks in the loop (including the
+ * `header', `latch': Header and latch basic blocks of the loop.
+
+ * `num_nodes': Number of basic blocks in the loop (including the
basic blocks of the sub-loops).
- * 'depth': The depth of the loop in the loops tree, i.e., the number
+
+ * `depth': The depth of the loop in the loops tree, i.e., the number
of super-loops of the loop.
- * 'outer', 'inner', 'next': The super-loop, the first sub-loop, and
+
+ * `outer', `inner', `next': The super-loop, the first sub-loop, and
the sibling of the loop in the loops tree.
There are other fields in the loop structures, many of them used only
@@ -18015,32 +18191,46 @@ they should not be accessed directly.
The most important functions to query loop structures are:
- * 'flow_loops_dump': Dumps the information about loops to a file.
- * 'verify_loop_structure': Checks consistency of the loop structures.
- * 'loop_latch_edge': Returns the latch edge of a loop.
- * 'loop_preheader_edge': If loops have preheaders, returns the
+ * `flow_loops_dump': Dumps the information about loops to a file.
+
+ * `verify_loop_structure': Checks consistency of the loop structures.
+
+ * `loop_latch_edge': Returns the latch edge of a loop.
+
+ * `loop_preheader_edge': If loops have preheaders, returns the
preheader edge of a loop.
- * 'flow_loop_nested_p': Tests whether loop is a sub-loop of another
+
+ * `flow_loop_nested_p': Tests whether loop is a sub-loop of another
loop.
- * 'flow_bb_inside_loop_p': Tests whether a basic block belongs to a
+
+ * `flow_bb_inside_loop_p': Tests whether a basic block belongs to a
loop (including its sub-loops).
- * 'find_common_loop': Finds the common super-loop of two loops.
- * 'superloop_at_depth': Returns the super-loop of a loop with the
+
+ * `find_common_loop': Finds the common super-loop of two loops.
+
+ * `superloop_at_depth': Returns the super-loop of a loop with the
given depth.
- * 'tree_num_loop_insns', 'num_loop_insns': Estimates the number of
+
+ * `tree_num_loop_insns', `num_loop_insns': Estimates the number of
insns in the loop, on GIMPLE and on RTL.
- * 'loop_exit_edge_p': Tests whether edge is an exit from a loop.
- * 'mark_loop_exit_edges': Marks all exit edges of all loops with
- 'EDGE_LOOP_EXIT' flag.
- * 'get_loop_body', 'get_loop_body_in_dom_order',
- 'get_loop_body_in_bfs_order': Enumerates the basic blocks in the
+
+ * `loop_exit_edge_p': Tests whether edge is an exit from a loop.
+
+ * `mark_loop_exit_edges': Marks all exit edges of all loops with
+ `EDGE_LOOP_EXIT' flag.
+
+ * `get_loop_body', `get_loop_body_in_dom_order',
+ `get_loop_body_in_bfs_order': Enumerates the basic blocks in the
loop in depth-first search order in reversed CFG, ordered by
dominance relation, and breath-first search order, respectively.
- * 'single_exit': Returns the single exit edge of the loop, or 'NULL'
- if the loop has more than one exit. You can only use this function
- if LOOPS_HAVE_MARKED_SINGLE_EXITS property is used.
- * 'get_loop_exit_edges': Enumerates the exit edges of a loop.
- * 'just_once_each_iteration_p': Returns true if the basic block is
+
+ * `single_exit': Returns the single exit edge of the loop, or `NULL'
+ if the loop has more than one exit. You can only use this
+ function if LOOPS_HAVE_MARKED_SINGLE_EXITS property is used.
+
+ * `get_loop_exit_edges': Enumerates the exit edges of a loop.
+
+ * `just_once_each_iteration_p': Returns true if the basic block is
executed exactly once during each iteration of a loop (that is, it
does not belong to a sub-loop, and it dominates the latch of the
loop).
@@ -18053,17 +18243,21 @@ File: gccint.info, Node: Loop manipulation, Next: LCSSA, Prev: Loop querying,
The loops tree can be manipulated using the following functions:
- * 'flow_loop_tree_node_add': Adds a node to the tree.
- * 'flow_loop_tree_node_remove': Removes a node from the tree.
- * 'add_bb_to_loop': Adds a basic block to a loop.
- * 'remove_bb_from_loops': Removes a basic block from loops.
+ * `flow_loop_tree_node_add': Adds a node to the tree.
+
+ * `flow_loop_tree_node_remove': Removes a node from the tree.
+
+ * `add_bb_to_loop': Adds a basic block to a loop.
+
+ * `remove_bb_from_loops': Removes a basic block from loops.
Most low-level CFG functions update loops automatically. The following
functions handle some more complicated cases of CFG manipulations:
- * 'remove_path': Removes an edge and all blocks it dominates.
- * 'split_loop_exit_edge': Splits exit edge of the loop, ensuring that
- PHI node arguments remain in the loop (this ensures that
+ * `remove_path': Removes an edge and all blocks it dominates.
+
+ * `split_loop_exit_edge': Splits exit edge of the loop, ensuring
+ that PHI node arguments remain in the loop (this ensures that
loop-closed SSA form is preserved). Only useful on GIMPLE.
Finally, there are some higher-level loop transformations implemented.
@@ -18071,23 +18265,26 @@ While some of them are written so that they should work on non-innermost
loops, they are mostly untested in that case, and at the moment, they
are only reliable for the innermost loops:
- * 'create_iv': Creates a new induction variable. Only works on
- GIMPLE. 'standard_iv_increment_position' can be used to find a
+ * `create_iv': Creates a new induction variable. Only works on
+ GIMPLE. `standard_iv_increment_position' can be used to find a
suitable place for the iv increment.
- * 'duplicate_loop_to_header_edge',
- 'tree_duplicate_loop_to_header_edge': These functions (on RTL and
+
+ * `duplicate_loop_to_header_edge',
+ `tree_duplicate_loop_to_header_edge': These functions (on RTL and
on GIMPLE) duplicate the body of the loop prescribed number of
times on one of the edges entering loop header, thus performing
- either loop unrolling or loop peeling. 'can_duplicate_loop_p'
- ('can_unroll_loop_p' on GIMPLE) must be true for the duplicated
+ either loop unrolling or loop peeling. `can_duplicate_loop_p'
+ (`can_unroll_loop_p' on GIMPLE) must be true for the duplicated
loop.
- * 'loop_version', 'tree_ssa_loop_version': These function create a
+
+ * `loop_version', `tree_ssa_loop_version': These function create a
copy of a loop, and a branch before them that selects one of them
depending on the prescribed condition. This is useful for
optimizations that need to verify some assumptions in runtime (one
of the copies of the loop is usually left unchanged, while the
other one is transformed in some way).
- * 'tree_unroll_loop': Unrolls the loop, including peeling the extra
+
+ * `tree_unroll_loop': Unrolls the loop, including peeling the extra
iterations to make the number of iterations divisible by unroll
factor, updating the exit condition, and removing the exits that
now cannot be taken. Works only on GIMPLE.
@@ -18099,7 +18296,7 @@ File: gccint.info, Node: LCSSA, Next: Scalar evolutions, Prev: Loop manipulat
=========================
Throughout the loop optimizations on tree level, one extra condition is
-enforced on the SSA form: No SSA name is used outside of the loop in
+enforced on the SSA form: No SSA name is used outside of the loop in
that it is defined. The SSA form satisfying this condition is called
"loop-closed SSA form" - LCSSA. To enforce LCSSA, PHI nodes must be
created at the exits of the loops for the SSA names that are used
@@ -18112,25 +18309,27 @@ held in LCSSA, in order to save memory.
are interested in the values that are defined in the loop and used
outside of it, i.e., exactly those for that we create new PHI
nodes.
+
* In induction variable analysis, it is not necessary to specify the
loop in that the analysis should be performed - the scalar
evolution analysis always returns the results with respect to the
loop in that the SSA name is defined.
+
* It makes updating of SSA form during loop transformations simpler.
- Without LCSSA, operations like loop unrolling may force creation of
- PHI nodes arbitrarily far from the loop, while in LCSSA, the SSA
- form can be updated locally. However, since we only keep real
+ Without LCSSA, operations like loop unrolling may force creation
+ of PHI nodes arbitrarily far from the loop, while in LCSSA, the
+ SSA form can be updated locally. However, since we only keep real
operands in LCSSA, we cannot use this advantage (we could have
local updating of real operands, but it is not much more efficient
- than to use generic SSA form updating for it as well; the amount of
- changes to SSA is the same).
+ than to use generic SSA form updating for it as well; the amount
+ of changes to SSA is the same).
However, it also means LCSSA must be updated. This is usually
straightforward, unless you create a new value in loop and use it
outside, or unless you manipulate loop exit edges (functions are
provided to make these manipulations simple).
-'rewrite_into_loop_closed_ssa' is used to rewrite SSA form to LCSSA, and
-'verify_loop_closed_ssa' to check that the invariant of LCSSA is
+`rewrite_into_loop_closed_ssa' is used to rewrite SSA form to LCSSA,
+and `verify_loop_closed_ssa' to check that the invariant of LCSSA is
preserved.

@@ -18144,37 +18343,37 @@ variable analysis on GIMPLE. They enable us to represent variables with
complicated behavior in a simple and consistent way (we only use it to
express values of polynomial induction variables, but it is possible to
extend it). The interfaces to SCEV analysis are declared in
-'tree-scalar-evolution.h'. To use scalar evolutions analysis,
-'scev_initialize' must be used. To stop using SCEV, 'scev_finalize'
+`tree-scalar-evolution.h'. To use scalar evolutions analysis,
+`scev_initialize' must be used. To stop using SCEV, `scev_finalize'
should be used. SCEV analysis caches results in order to save time and
memory. This cache however is made invalid by most of the loop
-transformations, including removal of code. If such a transformation is
-performed, 'scev_reset' must be called to clean the caches.
+transformations, including removal of code. If such a transformation
+is performed, `scev_reset' must be called to clean the caches.
Given an SSA name, its behavior in loops can be analyzed using the
-'analyze_scalar_evolution' function. The returned SCEV however does not
-have to be fully analyzed and it may contain references to other SSA
-names defined in the loop. To resolve these (potentially recursive)
-references, 'instantiate_parameters' or 'resolve_mixers' functions must
-be used. 'instantiate_parameters' is useful when you use the results of
-SCEV only for some analysis, and when you work with whole nest of loops
-at once. It will try replacing all SSA names by their SCEV in all
-loops, including the super-loops of the current loop, thus providing a
-complete information about the behavior of the variable in the loop
-nest. 'resolve_mixers' is useful if you work with only one loop at a
-time, and if you possibly need to create code based on the value of the
-induction variable. It will only resolve the SSA names defined in the
-current loop, leaving the SSA names defined outside unchanged, even if
-their evolution in the outer loops is known.
+`analyze_scalar_evolution' function. The returned SCEV however does
+not have to be fully analyzed and it may contain references to other
+SSA names defined in the loop. To resolve these (potentially
+recursive) references, `instantiate_parameters' or `resolve_mixers'
+functions must be used. `instantiate_parameters' is useful when you
+use the results of SCEV only for some analysis, and when you work with
+whole nest of loops at once. It will try replacing all SSA names by
+their SCEV in all loops, including the super-loops of the current loop,
+thus providing a complete information about the behavior of the
+variable in the loop nest. `resolve_mixers' is useful if you work with
+only one loop at a time, and if you possibly need to create code based
+on the value of the induction variable. It will only resolve the SSA
+names defined in the current loop, leaving the SSA names defined
+outside unchanged, even if their evolution in the outer loops is known.
The SCEV is a normal tree expression, except for the fact that it may
-contain several special tree nodes. One of them is 'SCEV_NOT_KNOWN',
+contain several special tree nodes. One of them is `SCEV_NOT_KNOWN',
used for SSA names whose value cannot be expressed. The other one is
-'POLYNOMIAL_CHREC'. Polynomial chrec has three arguments - base, step
+`POLYNOMIAL_CHREC'. Polynomial chrec has three arguments - base, step
and loop (both base and step may contain further polynomial chrecs).
Type of the expression and of base and step must be the same. A
-variable has evolution 'POLYNOMIAL_CHREC(base, step, loop)' if it is (in
-the specified loop) equivalent to 'x_1' in the following example
+variable has evolution `POLYNOMIAL_CHREC(base, step, loop)' if it is
+(in the specified loop) equivalent to `x_1' in the following example
while (...)
{
@@ -18183,7 +18382,7 @@ the specified loop) equivalent to 'x_1' in the following example
}
Note that this includes the language restrictions on the operations.
-For example, if we compile C code and 'x' has signed type, then the
+For example, if we compile C code and `x' has signed type, then the
overflow in addition would cause undefined behavior, and we may assume
that this does not happen. Hence, the value with this SCEV cannot
overflow (which restricts the number of iterations of such a loop).
@@ -18191,7 +18390,7 @@ overflow (which restricts the number of iterations of such a loop).
In many cases, one wants to restrict the attention just to affine
induction variables. In this case, the extra expressive power of SCEV
is not useful, and may complicate the optimizations. In this case,
-'simple_iv' function may be used to analyze a value - the result is a
+`simple_iv' function may be used to analyze a value - the result is a
loop-invariant base and step.

@@ -18202,38 +18401,40 @@ File: gccint.info, Node: loop-iv, Next: Number of iterations, Prev: Scalar ev
The induction variable on RTL is simple and only allows analysis of
affine induction variables, and only in one loop at once. The interface
-is declared in 'cfgloop.h'. Before analyzing induction variables in a
-loop L, 'iv_analysis_loop_init' function must be called on L. After the
-analysis (possibly calling 'iv_analysis_loop_init' for several loops) is
-finished, 'iv_analysis_done' should be called. The following functions
-can be used to access the results of the analysis:
+is declared in `cfgloop.h'. Before analyzing induction variables in a
+loop L, `iv_analysis_loop_init' function must be called on L. After
+the analysis (possibly calling `iv_analysis_loop_init' for several
+loops) is finished, `iv_analysis_done' should be called. The following
+functions can be used to access the results of the analysis:
- * 'iv_analyze': Analyzes a single register used in the given insn.
+ * `iv_analyze': Analyzes a single register used in the given insn.
If no use of the register in this insn is found, the following
insns are scanned, so that this function can be called on the insn
returned by get_condition.
- * 'iv_analyze_result': Analyzes result of the assignment in the given
- insn.
- * 'iv_analyze_expr': Analyzes a more complicated expression. All its
- operands are analyzed by 'iv_analyze', and hence they must be used
- in the specified insn or one of the following insns.
- The description of the induction variable is provided in 'struct
+ * `iv_analyze_result': Analyzes result of the assignment in the
+ given insn.
+
+ * `iv_analyze_expr': Analyzes a more complicated expression. All
+ its operands are analyzed by `iv_analyze', and hence they must be
+ used in the specified insn or one of the following insns.
+
+ The description of the induction variable is provided in `struct
rtx_iv'. In order to handle subregs, the representation is a bit
-complicated; if the value of the 'extend' field is not 'UNKNOWN', the
+complicated; if the value of the `extend' field is not `UNKNOWN', the
value of the induction variable in the i-th iteration is
delta + mult * extend_{extend_mode} (subreg_{mode} (base + i * step)),
- with the following exception: if 'first_special' is true, then the
-value in the first iteration (when 'i' is zero) is 'delta + mult *
-base'. However, if 'extend' is equal to 'UNKNOWN', then 'first_special'
-must be false, 'delta' 0, 'mult' 1 and the value in the i-th iteration
-is
+ with the following exception: if `first_special' is true, then the
+value in the first iteration (when `i' is zero) is `delta + mult *
+base'. However, if `extend' is equal to `UNKNOWN', then
+`first_special' must be false, `delta' 0, `mult' 1 and the value in the
+i-th iteration is
subreg_{mode} (base + i * step)
- The function 'get_iv_value' can be used to perform these calculations.
+ The function `get_iv_value' can be used to perform these calculations.

File: gccint.info, Node: Number of iterations, Next: Dependency analysis, Prev: loop-iv, Up: Loop Analysis and Representation
@@ -18252,39 +18453,42 @@ program; if it fails, the conditions are returned together with the
result. The following information and conditions are provided by the
analysis:
- * 'assumptions': If this condition is false, the rest of the
+ * `assumptions': If this condition is false, the rest of the
information is invalid.
- * 'noloop_assumptions' on RTL, 'may_be_zero' on GIMPLE: If this
+
+ * `noloop_assumptions' on RTL, `may_be_zero' on GIMPLE: If this
condition is true, the loop exits in the first iteration.
- * 'infinite': If this condition is true, the loop is infinite. This
+
+ * `infinite': If this condition is true, the loop is infinite. This
condition is only available on RTL. On GIMPLE, conditions for
- finiteness of the loop are included in 'assumptions'.
- * 'niter_expr' on RTL, 'niter' on GIMPLE: The expression that gives
+ finiteness of the loop are included in `assumptions'.
+
+ * `niter_expr' on RTL, `niter' on GIMPLE: The expression that gives
number of iterations. The number of iterations is defined as the
number of executions of the loop latch.
Both on GIMPLE and on RTL, it necessary for the induction variable
analysis framework to be initialized (SCEV on GIMPLE, loop-iv on RTL).
-On GIMPLE, the results are stored to 'struct tree_niter_desc' structure.
-Number of iterations before the loop is exited through a given exit can
-be determined using 'number_of_iterations_exit' function. On RTL, the
-results are returned in 'struct niter_desc' structure. The
-corresponding function is named 'check_simple_exit'. There are also
-functions that pass through all the exits of a loop and try to find one
-with easy to determine number of iterations - 'find_loop_niter' on
-GIMPLE and 'find_simple_exit' on RTL. Finally, there are functions that
-provide the same information, but additionally cache it, so that
-repeated calls to number of iterations are not so costly -
-'number_of_latch_executions' on GIMPLE and 'get_simple_loop_desc' on
-RTL.
+On GIMPLE, the results are stored to `struct tree_niter_desc'
+structure. Number of iterations before the loop is exited through a
+given exit can be determined using `number_of_iterations_exit'
+function. On RTL, the results are returned in `struct niter_desc'
+structure. The corresponding function is named `check_simple_exit'.
+There are also functions that pass through all the exits of a loop and
+try to find one with easy to determine number of iterations -
+`find_loop_niter' on GIMPLE and `find_simple_exit' on RTL. Finally,
+there are functions that provide the same information, but additionally
+cache it, so that repeated calls to number of iterations are not so
+costly - `number_of_latch_executions' on GIMPLE and
+`get_simple_loop_desc' on RTL.
Note that some of these functions may behave slightly differently than
others - some of them return only the expression for the number of
iterations, and fail if there are some assumptions. The function
-'number_of_latch_executions' works only for single-exit loops. The
-function 'number_of_cond_exit_executions' can be used to determine
+`number_of_latch_executions' works only for single-exit loops. The
+function `number_of_cond_exit_executions' can be used to determine
number of executions of the exit condition of a single-exit loop (i.e.,
-the 'number_of_latch_executions' increased by one).
+the `number_of_latch_executions' increased by one).

File: gccint.info, Node: Dependency analysis, Next: Omega, Prev: Number of iterations, Up: Loop Analysis and Representation
@@ -18293,21 +18497,21 @@ File: gccint.info, Node: Dependency analysis, Next: Omega, Prev: Number of it
=============================
The code for the data dependence analysis can be found in
-'tree-data-ref.c' and its interface and data structures are described in
-'tree-data-ref.h'. The function that computes the data dependences for
-all the array and pointer references for a given loop is
-'compute_data_dependences_for_loop'. This function is currently used by
-the linear loop transform and the vectorization passes. Before calling
-this function, one has to allocate two vectors: a first vector will
-contain the set of data references that are contained in the analyzed
-loop body, and the second vector will contain the dependence relations
-between the data references. Thus if the vector of data references is
-of size 'n', the vector containing the dependence relations will contain
-'n*n' elements. However if the analyzed loop contains side effects,
-such as calls that potentially can interfere with the data references in
-the current analyzed loop, the analysis stops while scanning the loop
-body for data references, and inserts a single 'chrec_dont_know' in the
-dependence relation array.
+`tree-data-ref.c' and its interface and data structures are described
+in `tree-data-ref.h'. The function that computes the data dependences
+for all the array and pointer references for a given loop is
+`compute_data_dependences_for_loop'. This function is currently used
+by the linear loop transform and the vectorization passes. Before
+calling this function, one has to allocate two vectors: a first vector
+will contain the set of data references that are contained in the
+analyzed loop body, and the second vector will contain the dependence
+relations between the data references. Thus if the vector of data
+references is of size `n', the vector containing the dependence
+relations will contain `n*n' elements. However if the analyzed loop
+contains side effects, such as calls that potentially can interfere
+with the data references in the current analyzed loop, the analysis
+stops while scanning the loop body for data references, and inserts a
+single `chrec_dont_know' in the dependence relation array.
The data references are discovered in a particular order during the
scanning of the loop body: the loop body is analyzed in execution order,
@@ -18319,36 +18523,36 @@ and mapping this order to the elements of this array avoids costly
queries to the loop body representation.
Three types of data references are currently handled: ARRAY_REF,
-INDIRECT_REF and COMPONENT_REF. The data structure for the data
-reference is 'data_reference', where 'data_reference_p' is a name of a
-pointer to the data reference structure. The structure contains the
+INDIRECT_REF and COMPONENT_REF. The data structure for the data
+reference is `data_reference', where `data_reference_p' is a name of a
+pointer to the data reference structure. The structure contains the
following elements:
- * 'base_object_info': Provides information about the base object of
- the data reference and its access functions. These access
- functions represent the evolution of the data reference in the loop
- relative to its base, in keeping with the classical meaning of the
- data reference access function for the support of arrays. For
- example, for a reference 'a.b[i][j]', the base object is 'a.b' and
- the access functions, one for each array subscript, are: '{i_init,
- + i_step}_1, {j_init, +, j_step}_2'.
+ * `base_object_info': Provides information about the base object of
+ the data reference and its access functions. These access functions
+ represent the evolution of the data reference in the loop relative
+ to its base, in keeping with the classical meaning of the data
+ reference access function for the support of arrays. For example,
+ for a reference `a.b[i][j]', the base object is `a.b' and the
+ access functions, one for each array subscript, are: `{i_init, +
+ i_step}_1, {j_init, +, j_step}_2'.
- * 'first_location_in_loop': Provides information about the first
+ * `first_location_in_loop': Provides information about the first
location accessed by the data reference in the loop and about the
access function used to represent evolution relative to this
- location. This data is used to support pointers, and is not used
- for arrays (for which we have base objects). Pointer accesses are
+ location. This data is used to support pointers, and is not used
+ for arrays (for which we have base objects). Pointer accesses are
represented as a one-dimensional access that starts from the first
- location accessed in the loop. For example:
+ location accessed in the loop. For example:
for1 i
for2 j
*((int *)p + i + j) = a[i][j];
- The access function of the pointer access is '{0, + 4B}_for2'
- relative to 'p + i'. The access functions of the array are
- '{i_init, + i_step}_for1' and '{j_init, +, j_step}_for2' relative
- to 'a'.
+ The access function of the pointer access is `{0, + 4B}_for2'
+ relative to `p + i'. The access functions of the array are
+ `{i_init, + i_step}_for1' and `{j_init, +, j_step}_for2' relative
+ to `a'.
Usually, the object the pointer refers to is either unknown, or we
can't prove that the access is confined to the boundaries of a
@@ -18359,50 +18563,57 @@ following elements:
references.
The current strategy for data dependence tests is as follows: If
- both 'a' and 'b' are represented as arrays, compare 'a.base_object'
- and 'b.base_object'; if they are equal, apply dependence tests (use
- access functions based on base_objects). Else if both 'a' and 'b'
- are represented as pointers, compare 'a.first_location' and
- 'b.first_location'; if they are equal, apply dependence tests (use
- access functions based on first location). However, if 'a' and 'b'
- are represented differently, only try to prove that the bases are
- definitely different.
+ both `a' and `b' are represented as arrays, compare
+ `a.base_object' and `b.base_object'; if they are equal, apply
+ dependence tests (use access functions based on base_objects).
+ Else if both `a' and `b' are represented as pointers, compare
+ `a.first_location' and `b.first_location'; if they are equal,
+ apply dependence tests (use access functions based on first
+ location). However, if `a' and `b' are represented differently,
+ only try to prove that the bases are definitely different.
* Aliasing information.
+
* Alignment information.
The structure describing the relation between two data references is
-'data_dependence_relation' and the shorter name for a pointer to such a
-structure is 'ddr_p'. This structure contains:
+`data_dependence_relation' and the shorter name for a pointer to such a
+structure is `ddr_p'. This structure contains:
* a pointer to each data reference,
- * a tree node 'are_dependent' that is set to 'chrec_known' if the
+
+ * a tree node `are_dependent' that is set to `chrec_known' if the
analysis has proved that there is no dependence between these two
- data references, 'chrec_dont_know' if the analysis was not able to
+ data references, `chrec_dont_know' if the analysis was not able to
determine any useful result and potentially there could exist a
- dependence between these data references, and 'are_dependent' is
- set to 'NULL_TREE' if there exist a dependence relation between the
+ dependence between these data references, and `are_dependent' is
+ set to `NULL_TREE' if there exist a dependence relation between the
data references, and the description of this dependence relation is
- given in the 'subscripts', 'dir_vects', and 'dist_vects' arrays,
+ given in the `subscripts', `dir_vects', and `dist_vects' arrays,
+
* a boolean that determines whether the dependence relation can be
represented by a classical distance vector,
- * an array 'subscripts' that contains a description of each subscript
- of the data references. Given two array accesses a subscript is
- the tuple composed of the access functions for a given dimension.
- For example, given 'A[f1][f2][f3]' and 'B[g1][g2][g3]', there are
- three subscripts: '(f1, g1), (f2, g2), (f3, g3)'.
- * two arrays 'dir_vects' and 'dist_vects' that contain classical
- representations of the data dependences under the form of direction
- and distance dependence vectors,
- * an array of loops 'loop_nest' that contains the loops to which the
+
+ * an array `subscripts' that contains a description of each
+ subscript of the data references. Given two array accesses a
+ subscript is the tuple composed of the access functions for a given
+ dimension. For example, given `A[f1][f2][f3]' and
+ `B[g1][g2][g3]', there are three subscripts: `(f1, g1), (f2, g2),
+ (f3, g3)'.
+
+ * two arrays `dir_vects' and `dist_vects' that contain classical
+ representations of the data dependences under the form of
+ direction and distance dependence vectors,
+
+ * an array of loops `loop_nest' that contains the loops to which the
distance and direction vectors refer to.
Several functions for pretty printing the information extracted by the
-data dependence analysis are available: 'dump_ddrs' prints with a
+data dependence analysis are available: `dump_ddrs' prints with a
maximum verbosity the details of a data dependence relations array,
-'dump_dist_dir_vectors' prints only the classical distance and direction
-vectors for a data dependence relations array, and
-'dump_data_references' prints the details of the data references
+`dump_dist_dir_vectors' prints only the classical distance and
+direction vectors for a data dependence relations array, and
+`dump_data_references' prints the details of the data references
contained in a data reference array.

@@ -18417,24 +18628,24 @@ ensuring the consistency of the results of these solvers, a data
dependence check pass has been implemented based on two different
solvers. The second method that has been integrated to GCC is based on
the Omega dependence solver, written in the 1990's by William Pugh and
-David Wonnacott. Data dependence tests can be formulated using a subset
-of the Presburger arithmetics that can be translated to linear
+David Wonnacott. Data dependence tests can be formulated using a
+subset of the Presburger arithmetics that can be translated to linear
constraint systems. These linear constraint systems can then be solved
using the Omega solver.
The Omega solver is using Fourier-Motzkin's algorithm for variable
-elimination: a linear constraint system containing 'n' variables is
-reduced to a linear constraint system with 'n-1' variables. The Omega
-solver can also be used for solving other problems that can be expressed
-under the form of a system of linear equalities and inequalities. The
-Omega solver is known to have an exponential worst case, also known
-under the name of "omega nightmare" in the literature, but in practice,
-the omega test is known to be efficient for the common data dependence
-tests.
+elimination: a linear constraint system containing `n' variables is
+reduced to a linear constraint system with `n-1' variables. The Omega
+solver can also be used for solving other problems that can be
+expressed under the form of a system of linear equalities and
+inequalities. The Omega solver is known to have an exponential worst
+case, also known under the name of "omega nightmare" in the literature,
+but in practice, the omega test is known to be efficient for the common
+data dependence tests.
The interface used by the Omega solver for describing the linear
-programming problems is described in 'omega.h', and the solver is
-'omega_solve_problem'.
+programming problems is described in `omega.h', and the solver is
+`omega_solve_problem'.

File: gccint.info, Node: Machine Desc, Next: Target Macros, Prev: Loop Analysis and Representation, Up: Top
@@ -18443,9 +18654,9 @@ File: gccint.info, Node: Machine Desc, Next: Target Macros, Prev: Loop Analys
***********************
A machine description has two parts: a file of instruction patterns
-('.md' file) and a C header file of macro definitions.
+(`.md' file) and a C header file of macro definitions.
- The '.md' file for a target machine contains a pattern for each
+ The `.md' file for a target machine contains a pattern for each
instruction that the target machine supports (or at least each
instruction that is worth telling the compiler about). It may also
contain comments. A semicolon causes the rest of the line to be a
@@ -18457,7 +18668,7 @@ comment, unless the semicolon is inside a quoted string.
* Overview:: How the machine description is used.
* Patterns:: How to write instruction patterns.
-* Example:: An explained example of a 'define_insn' pattern.
+* Example:: An explained example of a `define_insn' pattern.
* RTL Template:: The RTL template defines what insns match a pattern.
* Output Template:: The output template says how to make assembler code
from such an insn.
@@ -18478,9 +18689,9 @@ comment, unless the semicolon is inside a quoted string.
* Including Patterns:: Including Patterns in Machine Descriptions.
* Peephole Definitions::Defining machine-specific peephole optimizations.
* Insn Attributes:: Specifying the value of attributes for generated insns.
-* Conditional Execution::Generating 'define_insn' patterns for
+* Conditional Execution::Generating `define_insn' patterns for
predication.
-* Define Subst:: Generating 'define_insn' and 'define_expand'
+* Define Subst:: Generating `define_insn' and `define_expand'
patterns from other patterns.
* Constant Definitions::Defining symbolic constants that can be used in the
md file.
@@ -18502,31 +18713,32 @@ There are three main conversions that happen in the compiler:
3. The insn list is matched against the RTL templates to produce
assembler code.
+
For the generate pass, only the names of the insns matter, from either
-a named 'define_insn' or a 'define_expand'. The compiler will choose
+a named `define_insn' or a `define_expand'. The compiler will choose
the pattern with the right name and apply the operands according to the
-documentation later in this chapter, without regard for the RTL template
-or operand constraints. Note that the names the compiler looks for are
-hard-coded in the compiler--it will ignore unnamed patterns and patterns
-with names it doesn't know about, but if you don't provide a named
-pattern it needs, it will abort.
-
- If a 'define_insn' is used, the template given is inserted into the
-insn list. If a 'define_expand' is used, one of three things happens,
+documentation later in this chapter, without regard for the RTL
+template or operand constraints. Note that the names the compiler looks
+for are hard-coded in the compiler--it will ignore unnamed patterns and
+patterns with names it doesn't know about, but if you don't provide a
+named pattern it needs, it will abort.
+
+ If a `define_insn' is used, the template given is inserted into the
+insn list. If a `define_expand' is used, one of three things happens,
based on the condition logic. The condition logic may manually create
-new insns for the insn list, say via 'emit_insn()', and invoke 'DONE'.
-For certain named patterns, it may invoke 'FAIL' to tell the compiler to
-use an alternate way of performing that task. If it invokes neither
-'DONE' nor 'FAIL', the template given in the pattern is inserted, as if
-the 'define_expand' were a 'define_insn'.
+new insns for the insn list, say via `emit_insn()', and invoke `DONE'.
+For certain named patterns, it may invoke `FAIL' to tell the compiler
+to use an alternate way of performing that task. If it invokes neither
+`DONE' nor `FAIL', the template given in the pattern is inserted, as if
+the `define_expand' were a `define_insn'.
Once the insn list is generated, various optimization passes convert,
replace, and rearrange the insns in the insn list. This is where the
-'define_split' and 'define_peephole' patterns get used, for example.
+`define_split' and `define_peephole' patterns get used, for example.
Finally, the insn list's RTL is matched up with the RTL templates in
-the 'define_insn' patterns, and those patterns are used to emit the
-final assembly code. For this purpose, each named 'define_insn' acts
+the `define_insn' patterns, and those patterns are used to emit the
+final assembly code. For this purpose, each named `define_insn' acts
like it's unnamed, since the names are ignored.

@@ -18535,59 +18747,59 @@ File: gccint.info, Node: Patterns, Next: Example, Prev: Overview, Up: Machin
16.2 Everything about Instruction Patterns
==========================================
-A 'define_insn' expression is used to define instruction patterns to
-which insns may be matched. A 'define_insn' expression contains an
+A `define_insn' expression is used to define instruction patterns to
+which insns may be matched. A `define_insn' expression contains an
incomplete RTL expression, with pieces to be filled in later, operand
constraints that restrict how the pieces can be filled in, and an output
template or C code to generate the assembler output.
- A 'define_insn' is an RTL expression containing four or five operands:
+ A `define_insn' is an RTL expression containing four or five operands:
1. An optional name. The presence of a name indicate that this
instruction pattern can perform a certain standard job for the
- RTL-generation pass of the compiler. This pass knows certain names
- and will use the instruction patterns with those names, if the
- names are defined in the machine description.
+ RTL-generation pass of the compiler. This pass knows certain
+ names and will use the instruction patterns with those names, if
+ the names are defined in the machine description.
- The absence of a name is indicated by writing an empty string where
- the name should go. Nameless instruction patterns are never used
- for generating RTL code, but they may permit several simpler insns
- to be combined later on.
+ The absence of a name is indicated by writing an empty string
+ where the name should go. Nameless instruction patterns are never
+ used for generating RTL code, but they may permit several simpler
+ insns to be combined later on.
Names that are not thus known and used in RTL-generation have no
effect; they are equivalent to no name at all.
For the purpose of debugging the compiler, you may also specify a
- name beginning with the '*' character. Such a name is used only
+ name beginning with the `*' character. Such a name is used only
for identifying the instruction in RTL dumps; it is equivalent to
having a nameless pattern for all other purposes. Names beginning
- with the '*' character are not required to be unique.
+ with the `*' character are not required to be unique.
2. The "RTL template": This is a vector of incomplete RTL expressions
which describe the semantics of the instruction (*note RTL
Template::). It is incomplete because it may contain
- 'match_operand', 'match_operator', and 'match_dup' expressions that
- stand for operands of the instruction.
+ `match_operand', `match_operator', and `match_dup' expressions
+ that stand for operands of the instruction.
- If the vector has multiple elements, the RTL template is treated as
- a 'parallel' expression.
+ If the vector has multiple elements, the RTL template is treated
+ as a `parallel' expression.
3. The condition: This is a string which contains a C expression.
When the compiler attempts to match RTL against a pattern, the
- condition is evaluated. If the condition evaluates to 'true', the
- match is permitted. The condition may be an empty string, which is
- treated as always 'true'.
+ condition is evaluated. If the condition evaluates to `true', the
+ match is permitted. The condition may be an empty string, which
+ is treated as always `true'.
For a named pattern, the condition may not depend on the data in
the insn being matched, but only the target-machine-type flags.
The compiler needs to test these conditions during initialization
- in order to learn exactly which named instructions are available in
- a particular run.
+ in order to learn exactly which named instructions are available
+ in a particular run.
For nameless patterns, the condition is applied only when matching
an individual insn, and only after the insn has matched the
pattern's recognition template. The insn's operands may be found
- in the vector 'operands'.
+ in the vector `operands'.
For an insn where the condition has once matched, it cannot later
be used to control register allocation by excluding certain
@@ -18606,7 +18818,7 @@ template or C code to generate the assembler output.

File: gccint.info, Node: Example, Next: RTL Template, Prev: Patterns, Up: Machine Desc
-16.3 Example of 'define_insn'
+16.3 Example of `define_insn'
=============================
Here is an example of an instruction pattern, taken from the machine
@@ -18638,7 +18850,7 @@ This can also be written using braced strings:
This describes an instruction which sets the condition codes based on
the value of a general operand. It has no condition, so any insn with
an RTL description of the form shown may be matched to this pattern.
-The name 'tstsi' means "test a 'SImode' value" and tells the RTL
+The name `tstsi' means "test a `SImode' value" and tells the RTL
generation pass that, when it is necessary to test such a value, an insn
to do so can be constructed using this pattern.
@@ -18646,7 +18858,7 @@ to do so can be constructed using this pattern.
output template to return based on the kind of operand and the specific
type of CPU for which code is being generated.
- '"rm"' is an operand constraint. Its meaning is explained below.
+ `"rm"' is an operand constraint. Its meaning is explained below.

File: gccint.info, Node: RTL Template, Next: Output Template, Prev: Example, Up: Machine Desc
@@ -18664,98 +18876,98 @@ the operands in the insn being matched. Both of these activities are
controlled by special expression types that direct matching and
substitution of the operands.
-'(match_operand:M N PREDICATE CONSTRAINT)'
+`(match_operand:M N PREDICATE CONSTRAINT)'
This expression is a placeholder for operand number N of the insn.
When constructing an insn, operand number N will be substituted at
this point. When matching an insn, whatever appears at this
- position in the insn will be taken as operand number N; but it must
- satisfy PREDICATE or this instruction pattern will not match at
- all.
+ position in the insn will be taken as operand number N; but it
+ must satisfy PREDICATE or this instruction pattern will not match
+ at all.
Operand numbers must be chosen consecutively counting from zero in
- each instruction pattern. There may be only one 'match_operand'
+ each instruction pattern. There may be only one `match_operand'
expression in the pattern for each operand number. Usually
- operands are numbered in the order of appearance in 'match_operand'
- expressions. In the case of a 'define_expand', any operand numbers
- used only in 'match_dup' expressions have higher values than all
+ operands are numbered in the order of appearance in `match_operand'
+ expressions. In the case of a `define_expand', any operand numbers
+ used only in `match_dup' expressions have higher values than all
other operand numbers.
PREDICATE is a string that is the name of a function that accepts
two arguments, an expression and a machine mode. *Note
Predicates::. During matching, the function will be called with
the putative operand as the expression and M as the mode argument
- (if M is not specified, 'VOIDmode' will be used, which normally
+ (if M is not specified, `VOIDmode' will be used, which normally
causes PREDICATE to accept any mode). If it returns zero, this
instruction pattern fails to match. PREDICATE may be an empty
string; then it means no test is to be done on the operand, so
anything which occurs in this position is valid.
- Most of the time, PREDICATE will reject modes other than M--but not
- always. For example, the predicate 'address_operand' uses M as the
- mode of memory ref that the address should be valid for. Many
- predicates accept 'const_int' nodes even though their mode is
- 'VOIDmode'.
+ Most of the time, PREDICATE will reject modes other than M--but
+ not always. For example, the predicate `address_operand' uses M
+ as the mode of memory ref that the address should be valid for.
+ Many predicates accept `const_int' nodes even though their mode is
+ `VOIDmode'.
CONSTRAINT controls reloading and the choice of the best register
class to use for a value, as explained later (*note Constraints::).
If the constraint would be an empty string, it can be omitted.
People are often unclear on the difference between the constraint
- and the predicate. The predicate helps decide whether a given insn
- matches the pattern. The constraint plays no role in this
+ and the predicate. The predicate helps decide whether a given
+ insn matches the pattern. The constraint plays no role in this
decision; instead, it controls various decisions in the case of an
insn which does match.
-'(match_scratch:M N CONSTRAINT)'
+`(match_scratch:M N CONSTRAINT)'
This expression is also a placeholder for operand number N and
- indicates that operand must be a 'scratch' or 'reg' expression.
+ indicates that operand must be a `scratch' or `reg' expression.
When matching patterns, this is equivalent to
(match_operand:M N "scratch_operand" CONSTRAINT)
- but, when generating RTL, it produces a ('scratch':M) expression.
+ but, when generating RTL, it produces a (`scratch':M) expression.
- If the last few expressions in a 'parallel' are 'clobber'
+ If the last few expressions in a `parallel' are `clobber'
expressions whose operands are either a hard register or
- 'match_scratch', the combiner can add or delete them when
+ `match_scratch', the combiner can add or delete them when
necessary. *Note Side Effects::.
-'(match_dup N)'
+`(match_dup N)'
This expression is also a placeholder for operand number N. It is
used when the operand needs to appear more than once in the insn.
- In construction, 'match_dup' acts just like 'match_operand': the
+ In construction, `match_dup' acts just like `match_operand': the
operand is substituted into the insn being constructed. But in
- matching, 'match_dup' behaves differently. It assumes that operand
- number N has already been determined by a 'match_operand' appearing
- earlier in the recognition template, and it matches only an
- identical-looking expression.
+ matching, `match_dup' behaves differently. It assumes that operand
+ number N has already been determined by a `match_operand'
+ appearing earlier in the recognition template, and it matches only
+ an identical-looking expression.
- Note that 'match_dup' should not be used to tell the compiler that
+ Note that `match_dup' should not be used to tell the compiler that
a particular register is being used for two operands (example:
- 'add' that adds one register to another; the second register is
+ `add' that adds one register to another; the second register is
both an input operand and the output operand). Use a matching
- constraint (*note Simple Constraints::) for those. 'match_dup' is
+ constraint (*note Simple Constraints::) for those. `match_dup' is
for the cases where one operand is used in two places in the
template, such as an instruction that computes both a quotient and
a remainder, where the opcode takes two input operands but the RTL
- template has to refer to each of those twice; once for the quotient
- pattern and once for the remainder pattern.
+ template has to refer to each of those twice; once for the
+ quotient pattern and once for the remainder pattern.
-'(match_operator:M N PREDICATE [OPERANDS...])'
+`(match_operator:M N PREDICATE [OPERANDS...])'
This pattern is a kind of placeholder for a variable RTL expression
code.
When constructing an insn, it stands for an RTL expression whose
- expression code is taken from that of operand N, and whose operands
- are constructed from the patterns OPERANDS.
+ expression code is taken from that of operand N, and whose
+ operands are constructed from the patterns OPERANDS.
When matching an expression, it matches an expression if the
function PREDICATE returns nonzero on that expression _and_ the
patterns OPERANDS match the operands of the expression.
- Suppose that the function 'commutative_operator' is defined as
+ Suppose that the function `commutative_operator' is defined as
follows, to match any expression whose operator is one of the
commutative arithmetic operators of RTL and whose mode is MODE:
@@ -18778,66 +18990,66 @@ substitution of the operands.
[(match_operand:SI 1 "general_operand" "g")
(match_operand:SI 2 "general_operand" "g")])
- Here the vector '[OPERANDS...]' contains two patterns because the
+ Here the vector `[OPERANDS...]' contains two patterns because the
expressions to be matched all contain two operands.
When this pattern does match, the two operands of the commutative
operator are recorded as operands 1 and 2 of the insn. (This is
- done by the two instances of 'match_operand'.) Operand 3 of the
- insn will be the entire commutative expression: use 'GET_CODE
+ done by the two instances of `match_operand'.) Operand 3 of the
+ insn will be the entire commutative expression: use `GET_CODE
(operands[3])' to see which commutative operator was used.
- The machine mode M of 'match_operator' works like that of
- 'match_operand': it is passed as the second argument to the
+ The machine mode M of `match_operator' works like that of
+ `match_operand': it is passed as the second argument to the
predicate function, and that function is solely responsible for
deciding whether the expression to be matched "has" that mode.
When constructing an insn, argument 3 of the gen-function will
- specify the operation (i.e. the expression code) for the expression
- to be made. It should be an RTL expression, whose expression code
- is copied into a new expression whose operands are arguments 1 and
- 2 of the gen-function. The subexpressions of argument 3 are not
- used; only its expression code matters.
-
- When 'match_operator' is used in a pattern for matching an insn, it
- usually best if the operand number of the 'match_operator' is
+ specify the operation (i.e. the expression code) for the
+ expression to be made. It should be an RTL expression, whose
+ expression code is copied into a new expression whose operands are
+ arguments 1 and 2 of the gen-function. The subexpressions of
+ argument 3 are not used; only its expression code matters.
+
+ When `match_operator' is used in a pattern for matching an insn,
+ it usually best if the operand number of the `match_operator' is
higher than that of the actual operands of the insn. This improves
register allocation because the register allocator often looks at
operands 1 and 2 of insns to see if it can do register tying.
- There is no way to specify constraints in 'match_operator'. The
- operand of the insn which corresponds to the 'match_operator' never
- has any constraints because it is never reloaded as a whole.
- However, if parts of its OPERANDS are matched by 'match_operand'
+ There is no way to specify constraints in `match_operator'. The
+ operand of the insn which corresponds to the `match_operator'
+ never has any constraints because it is never reloaded as a whole.
+ However, if parts of its OPERANDS are matched by `match_operand'
patterns, those parts may have constraints of their own.
-'(match_op_dup:M N[OPERANDS...])'
- Like 'match_dup', except that it applies to operators instead of
+`(match_op_dup:M N[OPERANDS...])'
+ Like `match_dup', except that it applies to operators instead of
operands. When constructing an insn, operand number N will be
- substituted at this point. But in matching, 'match_op_dup' behaves
+ substituted at this point. But in matching, `match_op_dup' behaves
differently. It assumes that operand number N has already been
- determined by a 'match_operator' appearing earlier in the
+ determined by a `match_operator' appearing earlier in the
recognition template, and it matches only an identical-looking
expression.
-'(match_parallel N PREDICATE [SUBPAT...])'
+`(match_parallel N PREDICATE [SUBPAT...])'
This pattern is a placeholder for an insn that consists of a
- 'parallel' expression with a variable number of elements. This
+ `parallel' expression with a variable number of elements. This
expression should only appear at the top level of an insn pattern.
When constructing an insn, operand number N will be substituted at
this point. When matching an insn, it matches if the body of the
- insn is a 'parallel' expression with at least as many elements as
- the vector of SUBPAT expressions in the 'match_parallel', if each
- SUBPAT matches the corresponding element of the 'parallel', _and_
- the function PREDICATE returns nonzero on the 'parallel' that is
- the body of the insn. It is the responsibility of the predicate to
- validate elements of the 'parallel' beyond those listed in the
- 'match_parallel'.
-
- A typical use of 'match_parallel' is to match load and store
+ insn is a `parallel' expression with at least as many elements as
+ the vector of SUBPAT expressions in the `match_parallel', if each
+ SUBPAT matches the corresponding element of the `parallel', _and_
+ the function PREDICATE returns nonzero on the `parallel' that is
+ the body of the insn. It is the responsibility of the predicate
+ to validate elements of the `parallel' beyond those listed in the
+ `match_parallel'.
+
+ A typical use of `match_parallel' is to match load and store
multiple expressions, which can contain a variable number of
- elements in a 'parallel'. For example,
+ elements in a `parallel'. For example,
(define_insn ""
[(match_parallel 0 "load_multiple_operation"
@@ -18848,9 +19060,9 @@ substitution of the operands.
""
"loadm 0,0,%1,%2")
- This example comes from 'a29k.md'. The function
- 'load_multiple_operation' is defined in 'a29k.c' and checks that
- subsequent elements in the 'parallel' are the same as the 'set' in
+ This example comes from `a29k.md'. The function
+ `load_multiple_operation' is defined in `a29k.c' and checks that
+ subsequent elements in the `parallel' are the same as the `set' in
the pattern, except that they are referencing subsequent registers
and memory locations.
@@ -18867,9 +19079,10 @@ substitution of the operands.
(mem:SI (plus:SI (reg:SI 100)
(const_int 8))))])
-'(match_par_dup N [SUBPAT...])'
- Like 'match_op_dup', but for 'match_parallel' instead of
- 'match_operator'.
+`(match_par_dup N [SUBPAT...])'
+ Like `match_op_dup', but for `match_parallel' instead of
+ `match_operator'.
+

File: gccint.info, Node: Output Template, Next: Output Statement, Prev: RTL Template, Up: Machine Desc
@@ -18879,75 +19092,75 @@ File: gccint.info, Node: Output Template, Next: Output Statement, Prev: RTL T
The "output template" is a string which specifies how to output the
assembler code for an instruction pattern. Most of the template is a
-fixed string which is output literally. The character '%' is used to
+fixed string which is output literally. The character `%' is used to
specify where to substitute an operand; it can also be used to identify
places where different variants of the assembler require different
syntax.
- In the simplest case, a '%' followed by a digit N says to output
+ In the simplest case, a `%' followed by a digit N says to output
operand N at that point in the string.
- '%' followed by a letter and a digit says to output an operand in an
+ `%' followed by a letter and a digit says to output an operand in an
alternate fashion. Four letters have standard, built-in meanings
-described below. The machine description macro 'PRINT_OPERAND' can
+described below. The machine description macro `PRINT_OPERAND' can
define additional letters with nonstandard meanings.
- '%cDIGIT' can be used to substitute an operand that is a constant value
-without the syntax that normally indicates an immediate operand.
+ `%cDIGIT' can be used to substitute an operand that is a constant
+value without the syntax that normally indicates an immediate operand.
- '%nDIGIT' is like '%cDIGIT' except that the value of the constant is
+ `%nDIGIT' is like `%cDIGIT' except that the value of the constant is
negated before printing.
- '%aDIGIT' can be used to substitute an operand as if it were a memory
+ `%aDIGIT' can be used to substitute an operand as if it were a memory
reference, with the actual operand treated as the address. This may be
useful when outputting a "load address" instruction, because often the
assembler syntax for such an instruction requires you to write the
operand as if it were a memory reference.
- '%lDIGIT' is used to substitute a 'label_ref' into a jump instruction.
+ `%lDIGIT' is used to substitute a `label_ref' into a jump instruction.
- '%=' outputs a number which is unique to each instruction in the entire
-compilation. This is useful for making local labels to be referred to
-more than once in a single template that generates multiple assembler
-instructions.
+ `%=' outputs a number which is unique to each instruction in the
+entire compilation. This is useful for making local labels to be
+referred to more than once in a single template that generates multiple
+assembler instructions.
- '%' followed by a punctuation character specifies a substitution that
-does not use an operand. Only one case is standard: '%%' outputs a '%'
+ `%' followed by a punctuation character specifies a substitution that
+does not use an operand. Only one case is standard: `%%' outputs a `%'
into the assembler code. Other nonstandard cases can be defined in the
-'PRINT_OPERAND' macro. You must also define which punctuation
-characters are valid with the 'PRINT_OPERAND_PUNCT_VALID_P' macro.
+`PRINT_OPERAND' macro. You must also define which punctuation
+characters are valid with the `PRINT_OPERAND_PUNCT_VALID_P' macro.
The template may generate multiple assembler instructions. Write the
-text for the instructions, with '\;' between them.
+text for the instructions, with `\;' between them.
When the RTL contains two operands which are required by constraint to
match each other, the output template must refer only to the
-lower-numbered operand. Matching operands are not always identical, and
-the rest of the compiler arranges to put the proper RTL expression for
-printing into the lower-numbered operand.
+lower-numbered operand. Matching operands are not always identical,
+and the rest of the compiler arranges to put the proper RTL expression
+for printing into the lower-numbered operand.
- One use of nonstandard letters or punctuation following '%' is to
+ One use of nonstandard letters or punctuation following `%' is to
distinguish between different assembler languages for the same machine;
for example, Motorola syntax versus MIT syntax for the 68000. Motorola
-syntax requires periods in most opcode names, while MIT syntax does not.
-For example, the opcode 'movel' in MIT syntax is 'move.l' in Motorola
-syntax. The same file of patterns is used for both kinds of output
-syntax, but the character sequence '%.' is used in each place where
-Motorola syntax wants a period. The 'PRINT_OPERAND' macro for Motorola
-syntax defines the sequence to output a period; the macro for MIT syntax
-defines it to do nothing.
-
- As a special case, a template consisting of the single character '#'
+syntax requires periods in most opcode names, while MIT syntax does
+not. For example, the opcode `movel' in MIT syntax is `move.l' in
+Motorola syntax. The same file of patterns is used for both kinds of
+output syntax, but the character sequence `%.' is used in each place
+where Motorola syntax wants a period. The `PRINT_OPERAND' macro for
+Motorola syntax defines the sequence to output a period; the macro for
+MIT syntax defines it to do nothing.
+
+ As a special case, a template consisting of the single character `#'
instructs the compiler to first split the insn, and then output the
resulting instructions separately. This helps eliminate redundancy in
-the output templates. If you have a 'define_insn' that needs to emit
-multiple assembler instructions, and there is a matching 'define_split'
-already defined, then you can simply use '#' as the output template
+the output templates. If you have a `define_insn' that needs to emit
+multiple assembler instructions, and there is a matching `define_split'
+already defined, then you can simply use `#' as the output template
instead of writing an output template that emits the multiple assembler
instructions.
- If the macro 'ASSEMBLER_DIALECT' is defined, you can use construct of
-the form '{option0|option1|option2}' in the templates. These describe
+ If the macro `ASSEMBLER_DIALECT' is defined, you can use construct of
+the form `{option0|option1|option2}' in the templates. These describe
multiple variants of assembler language syntax. *Note Instruction
Output::.
@@ -18963,13 +19176,13 @@ single instruction pattern. For example, the opcodes may depend on the
kinds of operands; or some unfortunate combinations of operands may
require extra machine instructions.
- If the output control string starts with a '@', then it is actually a
+ If the output control string starts with a `@', then it is actually a
series of templates, each on a separate line. (Blank lines and leading
-spaces and tabs are ignored.) The templates correspond to the pattern's
-constraint alternatives (*note Multi-Alternative::). For example, if a
-target machine has a two-address add instruction 'addr' to add into a
-register and another 'addm' to add a register to memory, you might write
-this pattern:
+spaces and tabs are ignored.) The templates correspond to the
+pattern's constraint alternatives (*note Multi-Alternative::). For
+example, if a target machine has a two-address add instruction `addr'
+to add into a register and another `addm' to add a register to memory,
+you might write this pattern:
(define_insn "addsi3"
[(set (match_operand:SI 0 "general_operand" "=r,m")
@@ -18980,45 +19193,46 @@ this pattern:
addr %2,%0
addm %2,%0")
- If the output control string starts with a '*', then it is not an
+ If the output control string starts with a `*', then it is not an
output template but rather a piece of C program that should compute a
-template. It should execute a 'return' statement to return the
+template. It should execute a `return' statement to return the
template-string you want. Most such templates use C string literals,
which require doublequote characters to delimit them. To include these
-doublequote characters in the string, prefix each one with '\'.
+doublequote characters in the string, prefix each one with `\'.
If the output control string is written as a brace block instead of a
double-quoted string, it is automatically assumed to be C code. In that
case, it is not necessary to put in a leading asterisk, or to escape the
doublequotes surrounding C string literals.
- The operands may be found in the array 'operands', whose C data type is
-'rtx []'.
+ The operands may be found in the array `operands', whose C data type
+is `rtx []'.
It is very common to select different ways of generating assembler code
based on whether an immediate operand is within a certain range. Be
-careful when doing this, because the result of 'INTVAL' is an integer on
-the host machine. If the host machine has more bits in an 'int' than
-the target machine has in the mode in which the constant will be used,
-then some of the bits you get from 'INTVAL' will be superfluous. For
-proper results, you must carefully disregard the values of those bits.
+careful when doing this, because the result of `INTVAL' is an integer
+on the host machine. If the host machine has more bits in an `int'
+than the target machine has in the mode in which the constant will be
+used, then some of the bits you get from `INTVAL' will be superfluous.
+For proper results, you must carefully disregard the values of those
+bits.
It is possible to output an assembler instruction and then go on to
-output or compute more of them, using the subroutine 'output_asm_insn'.
-This receives two arguments: a template-string and a vector of operands.
-The vector may be 'operands', or it may be another array of 'rtx' that
-you declare locally and initialize yourself.
+output or compute more of them, using the subroutine `output_asm_insn'.
+This receives two arguments: a template-string and a vector of
+operands. The vector may be `operands', or it may be another array of
+`rtx' that you declare locally and initialize yourself.
When an insn pattern has multiple alternatives in its constraints,
-often the appearance of the assembler code is determined mostly by which
-alternative was matched. When this is so, the C code can test the
-variable 'which_alternative', which is the ordinal number of the
+often the appearance of the assembler code is determined mostly by
+which alternative was matched. When this is so, the C code can test
+the variable `which_alternative', which is the ordinal number of the
alternative that was actually satisfied (0 for the first, 1 for the
second alternative, etc.).
- For example, suppose there are two opcodes for storing zero, 'clrreg'
-for registers and 'clrmem' for memory locations. Here is how a pattern
-could use 'which_alternative' to choose between them:
+ For example, suppose there are two opcodes for storing zero, `clrreg'
+for registers and `clrmem' for memory locations. Here is how a pattern
+could use `which_alternative' to choose between them:
(define_insn ""
[(set (match_operand:SI 0 "general_operand" "=r,m")
@@ -19031,7 +19245,7 @@ could use 'which_alternative' to choose between them:
The example above, where the assembler code to generate was _solely_
determined by the alternative, could also have been specified as
-follows, having the output control string start with a '@':
+follows, having the output control string start with a `@':
(define_insn ""
[(set (match_operand:SI 0 "general_operand" "=r,m")
@@ -19042,7 +19256,7 @@ follows, having the output control string start with a '@':
clrmem %0")
If you just need a little bit of C code in one (or a few) alternatives,
-you can use '*' inside of a '@' multi-alternative template:
+you can use `*' inside of a `@' multi-alternative template:
(define_insn ""
[(set (match_operand:SI 0 "general_operand" "=r,<,m")
@@ -19059,18 +19273,18 @@ File: gccint.info, Node: Predicates, Next: Constraints, Prev: Output Statemen
16.7 Predicates
===============
-A predicate determines whether a 'match_operand' or 'match_operator'
+A predicate determines whether a `match_operand' or `match_operator'
expression matches, and therefore whether the surrounding instruction
-pattern will be used for that combination of operands. GCC has a number
-of machine-independent predicates, and you can define machine-specific
-predicates as needed. By convention, predicates used with
-'match_operand' have names that end in '_operand', and those used with
-'match_operator' have names that end in '_operator'.
-
- All predicates are Boolean functions (in the mathematical sense) of two
-arguments: the RTL expression that is being considered at that position
-in the instruction pattern, and the machine mode that the
-'match_operand' or 'match_operator' specifies. In this section, the
+pattern will be used for that combination of operands. GCC has a
+number of machine-independent predicates, and you can define
+machine-specific predicates as needed. By convention, predicates used
+with `match_operand' have names that end in `_operand', and those used
+with `match_operator' have names that end in `_operator'.
+
+ All predicates are Boolean functions (in the mathematical sense) of
+two arguments: the RTL expression that is being considered at that
+position in the instruction pattern, and the machine mode that the
+`match_operand' or `match_operator' specifies. In this section, the
first argument is called OP and the second argument MODE. Predicates
can be called from C as ordinary two-argument functions; this can be
useful in output templates or other machine-specific code.
@@ -19079,30 +19293,30 @@ useful in output templates or other machine-specific code.
to the hardware, as long as the constraints give reload the ability to
fix them up (*note Constraints::). However, GCC will usually generate
better code if the predicates specify the requirements of the machine
-instructions as closely as possible. Reload cannot fix up operands that
-must be constants ("immediate operands"); you must use a predicate that
-allows only constants, or else enforce the requirement in the extra
-condition.
+instructions as closely as possible. Reload cannot fix up operands
+that must be constants ("immediate operands"); you must use a predicate
+that allows only constants, or else enforce the requirement in the
+extra condition.
Most predicates handle their MODE argument in a uniform manner. If
-MODE is 'VOIDmode' (unspecified), then OP can have any mode. If MODE is
-anything else, then OP must have the same mode, unless OP is a
-'CONST_INT' or integer 'CONST_DOUBLE'. These RTL expressions always
-have 'VOIDmode', so it would be counterproductive to check that their
-mode matches. Instead, predicates that accept 'CONST_INT' and/or
-integer 'CONST_DOUBLE' check that the value stored in the constant will
+MODE is `VOIDmode' (unspecified), then OP can have any mode. If MODE
+is anything else, then OP must have the same mode, unless OP is a
+`CONST_INT' or integer `CONST_DOUBLE'. These RTL expressions always
+have `VOIDmode', so it would be counterproductive to check that their
+mode matches. Instead, predicates that accept `CONST_INT' and/or
+integer `CONST_DOUBLE' check that the value stored in the constant will
fit in the requested mode.
- Predicates with this behavior are called "normal". 'genrecog' can
+ Predicates with this behavior are called "normal". `genrecog' can
optimize the instruction recognizer based on knowledge of how normal
predicates treat modes. It can also diagnose certain kinds of common
errors in the use of normal predicates; for instance, it is almost
always an error to use a normal predicate without specifying a mode.
Predicates that do something different with their MODE argument are
-called "special". The generic predicates 'address_operand' and
-'pmode_register_operand' are special predicates. 'genrecog' does not do
-any optimizations or diagnosis when special predicates are used.
+called "special". The generic predicates `address_operand' and
+`pmode_register_operand' are special predicates. `genrecog' does not
+do any optimizations or diagnosis when special predicates are used.
* Menu:
@@ -19117,7 +19331,7 @@ File: gccint.info, Node: Machine-Independent Predicates, Next: Defining Predic
-------------------------------------
These are the generic predicates available to all back ends. They are
-defined in 'recog.c'. The first category of predicates allow only
+defined in `recog.c'. The first category of predicates allow only
constant, or "immediate", operands.
-- Function: immediate_operand
@@ -19126,27 +19340,27 @@ constant, or "immediate", operands.
must be constant.
-- Function: const_int_operand
- This predicate allows any 'CONST_INT' expression that fits in MODE.
- It is an appropriate choice for an immediate operand that does not
- allow a symbol or label.
+ This predicate allows any `CONST_INT' expression that fits in
+ MODE. It is an appropriate choice for an immediate operand that
+ does not allow a symbol or label.
-- Function: const_double_operand
- This predicate accepts any 'CONST_DOUBLE' expression that has
- exactly MODE. If MODE is 'VOIDmode', it will also accept
- 'CONST_INT'. It is intended for immediate floating point
+ This predicate accepts any `CONST_DOUBLE' expression that has
+ exactly MODE. If MODE is `VOIDmode', it will also accept
+ `CONST_INT'. It is intended for immediate floating point
constants.
The second category of predicates allow only some kind of machine
register.
-- Function: register_operand
- This predicate allows any 'REG' or 'SUBREG' expression that is
+ This predicate allows any `REG' or `SUBREG' expression that is
valid for MODE. It is often suitable for arithmetic instruction
operands on a RISC machine.
-- Function: pmode_register_operand
- This is a slight variant on 'register_operand' which works around a
- limitation in the machine-description reader.
+ This is a slight variant on `register_operand' which works around
+ a limitation in the machine-description reader.
(match_operand N "pmode_register_operand" CONSTRAINT)
@@ -19154,15 +19368,15 @@ register.
(match_operand:P N "register_operand" CONSTRAINT)
- would mean, if the machine-description reader accepted ':P' mode
- suffixes. Unfortunately, it cannot, because 'Pmode' is an alias
+ would mean, if the machine-description reader accepted `:P' mode
+ suffixes. Unfortunately, it cannot, because `Pmode' is an alias
for some other mode, and might vary with machine-specific options.
*Note Misc::.
-- Function: scratch_operand
- This predicate allows hard registers and 'SCRATCH' expressions, but
- not pseudo-registers. It is used internally by 'match_scratch'; it
- should not be used directly.
+ This predicate allows hard registers and `SCRATCH' expressions,
+ but not pseudo-registers. It is used internally by
+ `match_scratch'; it should not be used directly.
The third category of predicates allow only some kind of memory
reference.
@@ -19170,38 +19384,38 @@ reference.
-- Function: memory_operand
This predicate allows any valid reference to a quantity of mode
MODE in memory, as determined by the weak form of
- 'GO_IF_LEGITIMATE_ADDRESS' (*note Addressing Modes::).
+ `GO_IF_LEGITIMATE_ADDRESS' (*note Addressing Modes::).
-- Function: address_operand
This predicate is a little unusual; it allows any operand that is a
valid expression for the _address_ of a quantity of mode MODE,
- again determined by the weak form of 'GO_IF_LEGITIMATE_ADDRESS'.
- To first order, if '(mem:MODE (EXP))' is acceptable to
- 'memory_operand', then EXP is acceptable to 'address_operand'.
+ again determined by the weak form of `GO_IF_LEGITIMATE_ADDRESS'.
+ To first order, if `(mem:MODE (EXP))' is acceptable to
+ `memory_operand', then EXP is acceptable to `address_operand'.
Note that EXP does not necessarily have the mode MODE.
-- Function: indirect_operand
- This is a stricter form of 'memory_operand' which allows only
- memory references with a 'general_operand' as the address
+ This is a stricter form of `memory_operand' which allows only
+ memory references with a `general_operand' as the address
expression. New uses of this predicate are discouraged, because
- 'general_operand' is very permissive, so it's hard to tell what an
- 'indirect_operand' does or does not allow. If a target has
+ `general_operand' is very permissive, so it's hard to tell what an
+ `indirect_operand' does or does not allow. If a target has
different requirements for memory operands for different
instructions, it is better to define target-specific predicates
which enforce the hardware's requirements explicitly.
-- Function: push_operand
This predicate allows a memory reference suitable for pushing a
- value onto the stack. This will be a 'MEM' which refers to
- 'stack_pointer_rtx', with a side-effect in its address expression
- (*note Incdec::); which one is determined by the 'STACK_PUSH_CODE'
+ value onto the stack. This will be a `MEM' which refers to
+ `stack_pointer_rtx', with a side-effect in its address expression
+ (*note Incdec::); which one is determined by the `STACK_PUSH_CODE'
macro (*note Frame Layout::).
-- Function: pop_operand
This predicate allows a memory reference suitable for popping a
- value off the stack. Again, this will be a 'MEM' referring to
- 'stack_pointer_rtx', with a side-effect in its address expression.
- However, this time 'STACK_POP_CODE' is expected.
+ value off the stack. Again, this will be a `MEM' referring to
+ `stack_pointer_rtx', with a side-effect in its address expression.
+ However, this time `STACK_POP_CODE' is expected.
The fourth category of predicates allow some combination of the above
operands.
@@ -19222,14 +19436,14 @@ Finally, there are two generic operator predicates.
-- Function: comparison_operator
This predicate matches any expression which performs an arithmetic
- comparison in MODE; that is, 'COMPARISON_P' is true for the
+ comparison in MODE; that is, `COMPARISON_P' is true for the
expression code.
-- Function: ordered_comparison_operator
This predicate matches any expression which performs an arithmetic
comparison in MODE and whose expression code is valid for integer
- modes; that is, the expression code will be one of 'eq', 'ne',
- 'lt', 'ltu', 'le', 'leu', 'gt', 'gtu', 'ge', 'geu'.
+ modes; that is, the expression code will be one of `eq', `ne',
+ `lt', `ltu', `le', `leu', `gt', `gtu', `ge', `geu'.

File: gccint.info, Node: Defining Predicates, Prev: Machine-Independent Predicates, Up: Predicates
@@ -19239,32 +19453,33 @@ File: gccint.info, Node: Defining Predicates, Prev: Machine-Independent Predic
Many machines have requirements for their operands that cannot be
expressed precisely using the generic predicates. You can define
-additional predicates using 'define_predicate' and
-'define_special_predicate' expressions. These expressions have three
+additional predicates using `define_predicate' and
+`define_special_predicate' expressions. These expressions have three
operands:
* The name of the predicate, as it will be referred to in
- 'match_operand' or 'match_operator' expressions.
+ `match_operand' or `match_operator' expressions.
* An RTL expression which evaluates to true if the predicate allows
the operand OP, false if it does not. This expression can only use
the following RTL codes:
- 'MATCH_OPERAND'
- When written inside a predicate expression, a 'MATCH_OPERAND'
+ `MATCH_OPERAND'
+ When written inside a predicate expression, a `MATCH_OPERAND'
expression evaluates to true if the predicate it names would
- allow OP. The operand number and constraint are ignored. Due
- to limitations in 'genrecog', you can only refer to generic
- predicates and predicates that have already been defined.
+ allow OP. The operand number and constraint are ignored.
+ Due to limitations in `genrecog', you can only refer to
+ generic predicates and predicates that have already been
+ defined.
- 'MATCH_CODE'
+ `MATCH_CODE'
This expression evaluates to true if OP or a specified
subexpression of OP has one of a given list of RTX codes.
The first operand of this expression is a string constant
containing a comma-separated list of RTX code names (in lower
- case). These are the codes for which the 'MATCH_CODE' will be
- true.
+ case). These are the codes for which the `MATCH_CODE' will
+ be true.
The second operand is a string constant which indicates what
subexpression of OP to examine. If it is absent or the empty
@@ -19273,53 +19488,53 @@ operands:
character indicates a subexpression to extract from the
current expression; for the first character this is OP, for
the second and subsequent characters it is the result of the
- previous character. A digit N extracts 'XEXP (E, N)'; a
- letter L extracts 'XVECEXP (E, 0, N)' where N is the
- alphabetic ordinal of L (0 for 'a', 1 for 'b', and so on).
- The 'MATCH_CODE' then examines the RTX code of the
+ previous character. A digit N extracts `XEXP (E, N)'; a
+ letter L extracts `XVECEXP (E, 0, N)' where N is the
+ alphabetic ordinal of L (0 for `a', 1 for 'b', and so on).
+ The `MATCH_CODE' then examines the RTX code of the
subexpression extracted by the complete string. It is not
- possible to extract components of an 'rtvec' that is not at
+ possible to extract components of an `rtvec' that is not at
position 0 within its RTX object.
- 'MATCH_TEST'
+ `MATCH_TEST'
This expression has one operand, a string constant containing
a C expression. The predicate's arguments, OP and MODE, are
available with those names in the C expression. The
- 'MATCH_TEST' evaluates to true if the C expression evaluates
- to a nonzero value. 'MATCH_TEST' expressions must not have
+ `MATCH_TEST' evaluates to true if the C expression evaluates
+ to a nonzero value. `MATCH_TEST' expressions must not have
side effects.
- 'AND'
- 'IOR'
- 'NOT'
- 'IF_THEN_ELSE'
- The basic 'MATCH_' expressions can be combined using these
+ `AND'
+ `IOR'
+ `NOT'
+ `IF_THEN_ELSE'
+ The basic `MATCH_' expressions can be combined using these
logical operators, which have the semantics of the C operators
- '&&', '||', '!', and '? :' respectively. As in Common Lisp,
- you may give an 'AND' or 'IOR' expression an arbitrary number
+ `&&', `||', `!', and `? :' respectively. As in Common Lisp,
+ you may give an `AND' or `IOR' expression an arbitrary number
of arguments; this has exactly the same effect as writing a
- chain of two-argument 'AND' or 'IOR' expressions.
+ chain of two-argument `AND' or `IOR' expressions.
- * An optional block of C code, which should execute 'return true' if
- the predicate is found to match and 'return false' if it does not.
- It must not have any side effects. The predicate arguments, OP and
- MODE, are available with those names.
+ * An optional block of C code, which should execute `return true' if
+ the predicate is found to match and `return false' if it does not.
+ It must not have any side effects. The predicate arguments, OP
+ and MODE, are available with those names.
If a code block is present in a predicate definition, then the RTL
expression must evaluate to true _and_ the code block must execute
- 'return true' for the predicate to allow the operand. The RTL
- expression is evaluated first; do not re-check anything in the code
- block that was checked in the RTL expression.
+ `return true' for the predicate to allow the operand. The RTL
+ expression is evaluated first; do not re-check anything in the
+ code block that was checked in the RTL expression.
- The program 'genrecog' scans 'define_predicate' and
-'define_special_predicate' expressions to determine which RTX codes are
+ The program `genrecog' scans `define_predicate' and
+`define_special_predicate' expressions to determine which RTX codes are
possibly allowed. You should always make this explicit in the RTL
-predicate expression, using 'MATCH_OPERAND' and 'MATCH_CODE'.
+predicate expression, using `MATCH_OPERAND' and `MATCH_CODE'.
Here is an example of a simple predicate definition, from the IA64
machine description:
- ;; True if OP is a 'SYMBOL_REF' which refers to the sdata section.
+ ;; True if OP is a `SYMBOL_REF' which refers to the sdata section.
(define_predicate "small_addr_symbolic_operand"
(and (match_code "symbol_ref")
(match_test "SYMBOL_REF_SMALL_ADDR_P (op)")))
@@ -19338,25 +19553,25 @@ And here is another, showing the use of the C block.
return (regno >= FIRST_PSEUDO_REGISTER || GENERAL_REGNO_P (regno));
})
- Predicates written with 'define_predicate' automatically include a test
-that MODE is 'VOIDmode', or OP has the same mode as MODE, or OP is a
-'CONST_INT' or 'CONST_DOUBLE'. They do _not_ check specifically for
-integer 'CONST_DOUBLE', nor do they test that the value of either kind
-of constant fits in the requested mode. This is because target-specific
-predicates that take constants usually have to do more stringent value
-checks anyway. If you need the exact same treatment of 'CONST_INT' or
-'CONST_DOUBLE' that the generic predicates provide, use a
-'MATCH_OPERAND' subexpression to call 'const_int_operand',
-'const_double_operand', or 'immediate_operand'.
-
- Predicates written with 'define_special_predicate' do not get any
+ Predicates written with `define_predicate' automatically include a
+test that MODE is `VOIDmode', or OP has the same mode as MODE, or OP is
+a `CONST_INT' or `CONST_DOUBLE'. They do _not_ check specifically for
+integer `CONST_DOUBLE', nor do they test that the value of either kind
+of constant fits in the requested mode. This is because
+target-specific predicates that take constants usually have to do more
+stringent value checks anyway. If you need the exact same treatment of
+`CONST_INT' or `CONST_DOUBLE' that the generic predicates provide, use
+a `MATCH_OPERAND' subexpression to call `const_int_operand',
+`const_double_operand', or `immediate_operand'.
+
+ Predicates written with `define_special_predicate' do not get any
automatic mode checks, and are treated as having special mode handling
-by 'genrecog'.
+by `genrecog'.
- The program 'genpreds' is responsible for generating code to test
+ The program `genpreds' is responsible for generating code to test
predicates. It also writes a header file containing function
declarations for all machine-specific predicates. It is not necessary
-to declare these predicates in 'CPU-protos.h'.
+to declare these predicates in `CPU-protos.h'.

File: gccint.info, Node: Constraints, Next: Standard Names, Prev: Predicates, Up: Machine Desc
@@ -19364,7 +19579,7 @@ File: gccint.info, Node: Constraints, Next: Standard Names, Prev: Predicates,
16.8 Operand Constraints
========================
-Each 'match_operand' in an instruction pattern can specify constraints
+Each `match_operand' in an instruction pattern can specify constraints
for the operands allowed. The constraints allow you to fine-tune
matching within the set of operands allowed by the predicate.
@@ -19373,7 +19588,7 @@ kinds of register; whether the operand can be a memory reference, and
which kinds of address; whether the operand may be an immediate
constant, and which possible values it may have. Constraints can also
require two operands to match. Side-effects aren't allowed in operands
-of inline 'asm', unless '<' or '>' constraints are used, because there
+of inline `asm', unless `<' or `>' constraints are used, because there
is no guarantee that the side-effects will happen exactly once in an
instruction that can update the addressing register.
@@ -19405,13 +19620,13 @@ whitespace
description even if they have different number of constraints and
modifiers.
-'m'
+`m'
A memory operand is allowed, with any kind of address that the
machine supports in general. Note that the letter used for the
- general memory constraint can be re-defined by a back end using the
- 'TARGET_MEM_CONSTRAINT' macro.
+ general memory constraint can be re-defined by a back end using
+ the `TARGET_MEM_CONSTRAINT' macro.
-'o'
+`o'
A memory operand is allowed, but only if the address is
"offsettable". This means that adding a small integer (actually,
the width in bytes of the operand, as determined by its machine
@@ -19427,106 +19642,108 @@ whitespace
on the other addressing modes that the machine supports.
Note that in an output operand which can be matched by another
- operand, the constraint letter 'o' is valid only when accompanied
- by both '<' (if the target machine has predecrement addressing) and
- '>' (if the target machine has preincrement addressing).
-
-'V'
- A memory operand that is not offsettable. In other words, anything
- that would fit the 'm' constraint but not the 'o' constraint.
-
-'<'
- A memory operand with autodecrement addressing (either predecrement
- or postdecrement) is allowed. In inline 'asm' this constraint is
- only allowed if the operand is used exactly once in an instruction
- that can handle the side-effects. Not using an operand with '<' in
- constraint string in the inline 'asm' pattern at all or using it in
- multiple instructions isn't valid, because the side-effects
- wouldn't be performed or would be performed more than once.
- Furthermore, on some targets the operand with '<' in constraint
- string must be accompanied by special instruction suffixes like
- '%U0' instruction suffix on PowerPC or '%P0' on IA-64.
-
-'>'
- A memory operand with autoincrement addressing (either preincrement
- or postincrement) is allowed. In inline 'asm' the same
- restrictions as for '<' apply.
-
-'r'
+ operand, the constraint letter `o' is valid only when accompanied
+ by both `<' (if the target machine has predecrement addressing)
+ and `>' (if the target machine has preincrement addressing).
+
+`V'
+ A memory operand that is not offsettable. In other words,
+ anything that would fit the `m' constraint but not the `o'
+ constraint.
+
+`<'
+ A memory operand with autodecrement addressing (either
+ predecrement or postdecrement) is allowed. In inline `asm' this
+ constraint is only allowed if the operand is used exactly once in
+ an instruction that can handle the side-effects. Not using an
+ operand with `<' in constraint string in the inline `asm' pattern
+ at all or using it in multiple instructions isn't valid, because
+ the side-effects wouldn't be performed or would be performed more
+ than once. Furthermore, on some targets the operand with `<' in
+ constraint string must be accompanied by special instruction
+ suffixes like `%U0' instruction suffix on PowerPC or `%P0' on
+ IA-64.
+
+`>'
+ A memory operand with autoincrement addressing (either
+ preincrement or postincrement) is allowed. In inline `asm' the
+ same restrictions as for `<' apply.
+
+`r'
A register operand is allowed provided that it is in a general
register.
-'i'
+`i'
An immediate integer operand (one with constant value) is allowed.
This includes symbolic constants whose values will be known only at
assembly time or later.
-'n'
+`n'
An immediate integer operand with a known numeric value is allowed.
Many systems cannot support assembly-time constants for operands
less than a word wide. Constraints for these operands should use
- 'n' rather than 'i'.
+ `n' rather than `i'.
-'I', 'J', 'K', ... 'P'
- Other letters in the range 'I' through 'P' may be defined in a
+`I', `J', `K', ... `P'
+ Other letters in the range `I' through `P' may be defined in a
machine-dependent fashion to permit immediate integer operands with
explicit integer values in specified ranges. For example, on the
- 68000, 'I' is defined to stand for the range of values 1 to 8.
+ 68000, `I' is defined to stand for the range of values 1 to 8.
This is the range permitted as a shift count in the shift
instructions.
-'E'
- An immediate floating operand (expression code 'const_double') is
+`E'
+ An immediate floating operand (expression code `const_double') is
allowed, but only if the target floating point format is the same
as that of the host machine (on which the compiler is running).
-'F'
- An immediate floating operand (expression code 'const_double' or
- 'const_vector') is allowed.
+`F'
+ An immediate floating operand (expression code `const_double' or
+ `const_vector') is allowed.
-'G', 'H'
- 'G' and 'H' may be defined in a machine-dependent fashion to permit
- immediate floating operands in particular ranges of values.
+`G', `H'
+ `G' and `H' may be defined in a machine-dependent fashion to
+ permit immediate floating operands in particular ranges of values.
-'s'
- An immediate integer operand whose value is not an explicit integer
- is allowed.
+`s'
+ An immediate integer operand whose value is not an explicit
+ integer is allowed.
This might appear strange; if an insn allows a constant operand
- with a value not known at compile time, it certainly must allow any
- known value. So why use 's' instead of 'i'? Sometimes it allows
- better code to be generated.
+ with a value not known at compile time, it certainly must allow
+ any known value. So why use `s' instead of `i'? Sometimes it
+ allows better code to be generated.
For example, on the 68000 in a fullword instruction it is possible
to use an immediate operand; but if the immediate value is between
-128 and 127, better code results from loading the value into a
- register and using the register. This is because the load into the
- register can be done with a 'moveq' instruction. We arrange for
- this to happen by defining the letter 'K' to mean "any integer
- outside the range -128 to 127", and then specifying 'Ks' in the
+ register and using the register. This is because the load into
+ the register can be done with a `moveq' instruction. We arrange
+ for this to happen by defining the letter `K' to mean "any integer
+ outside the range -128 to 127", and then specifying `Ks' in the
operand constraints.
-'g'
+`g'
Any register, memory or immediate integer operand is allowed,
except for registers that are not general registers.
-'X'
+`X'
Any operand whatsoever is allowed, even if it does not satisfy
- 'general_operand'. This is normally used in the constraint of a
- 'match_scratch' when certain alternatives will not actually require
- a scratch register.
+ `general_operand'. This is normally used in the constraint of a
+ `match_scratch' when certain alternatives will not actually
+ require a scratch register.
-'0', '1', '2', ... '9'
+`0', `1', `2', ... `9'
An operand that matches the specified operand number is allowed.
If a digit is used together with letters within the same
alternative, the digit should come last.
This number is allowed to be more than a single digit. If multiple
digits are encountered consecutively, they are interpreted as a
- single decimal integer. There is scant chance for ambiguity, since
- to-date it has never been desirable that '10' be interpreted as
- matching either operand 1 _or_ operand 0. Should this be desired,
- one can use multiple alternatives instead.
+ single decimal integer. There is scant chance for ambiguity,
+ since to-date it has never been desirable that `10' be interpreted
+ as matching either operand 1 _or_ operand 0. Should this be
+ desired, one can use multiple alternatives instead.
This is called a "matching constraint" and what it really means is
that the assembler has only a single operand that fills two roles
@@ -19545,24 +19762,24 @@ whitespace
For operands to match in a particular case usually means that they
are identical-looking RTL expressions. But in a few special cases
- specific kinds of dissimilarity are allowed. For example, '*x' as
- an input operand will match '*x++' as an output operand. For
- proper results in such cases, the output template should always use
- the output-operand's number when printing the operand.
+ specific kinds of dissimilarity are allowed. For example, `*x' as
+ an input operand will match `*x++' as an output operand. For
+ proper results in such cases, the output template should always
+ use the output-operand's number when printing the operand.
-'p'
+`p'
An operand that is a valid memory address is allowed. This is for
"load address" and "push address" instructions.
- 'p' in the constraint must be accompanied by 'address_operand' as
- the predicate in the 'match_operand'. This predicate interprets
- the mode specified in the 'match_operand' as the mode of the memory
+ `p' in the constraint must be accompanied by `address_operand' as
+ the predicate in the `match_operand'. This predicate interprets
+ the mode specified in the `match_operand' as the mode of the memory
reference for which the address would be valid.
OTHER-LETTERS
Other letters can be defined in machine-dependent fashion to stand
for particular classes of registers or other arbitrary operand
- types. 'd', 'a' and 'f' are defined on the 68000/68020 to stand
+ types. `d', `a' and `f' are defined on the 68000/68020 to stand
for data, address and floating point registers.
In order to have valid assembler code, each operand must satisfy its
@@ -19601,9 +19818,9 @@ the first pattern would not apply at all, because this insn does not
contain two identical subexpressions in the right place. The pattern
would say, "That does not look like an add instruction; try other
patterns". The second pattern would say, "Yes, that's an add
-instruction, but there is something wrong with it". It would direct the
-reload pass of the compiler to generate additional insns to make the
-constraint true. The results might look like this:
+instruction, but there is something wrong with it". It would direct
+the reload pass of the compiler to generate additional insns to make
+the constraint true. The results might look like this:
(insn N2 PREV N
(set (reg:SI 3) (reg:SI 6))
@@ -19630,46 +19847,47 @@ reloading any possible operand so that it will fit.
registers is safe provided its predicate rejects registers.
An operand whose predicate accepts only constant values is safe
- provided its constraints include the letter 'i'. If any possible
- constant value is accepted, then nothing less than 'i' will do; if
+ provided its constraints include the letter `i'. If any possible
+ constant value is accepted, then nothing less than `i' will do; if
the predicate is more selective, then the constraints may also be
more selective.
* Any operand expression can be reloaded by copying it into a
register. So if an operand's constraints allow some kind of
- register, it is certain to be safe. It need not permit all classes
- of registers; the compiler knows how to copy a register into
- another register of the proper class in order to make an
+ register, it is certain to be safe. It need not permit all
+ classes of registers; the compiler knows how to copy a register
+ into another register of the proper class in order to make an
instruction valid.
* A nonoffsettable memory reference can be reloaded by copying the
- address into a register. So if the constraint uses the letter 'o',
- all memory references are taken care of.
+ address into a register. So if the constraint uses the letter
+ `o', all memory references are taken care of.
* A constant operand can be reloaded by allocating space in memory to
hold it as preinitialized data. Then the memory reference can be
used in place of the constant. So if the constraint uses the
- letters 'o' or 'm', constant operands are not a problem.
+ letters `o' or `m', constant operands are not a problem.
* If the constraint permits a constant and a pseudo register used in
- an insn was not allocated to a hard register and is equivalent to a
- constant, the register will be replaced with the constant. If the
- predicate does not permit a constant and the insn is re-recognized
- for some reason, the compiler will crash. Thus the predicate must
- always recognize any objects allowed by the constraint.
+ an insn was not allocated to a hard register and is equivalent to
+ a constant, the register will be replaced with the constant. If
+ the predicate does not permit a constant and the insn is
+ re-recognized for some reason, the compiler will crash. Thus the
+ predicate must always recognize any objects allowed by the
+ constraint.
If the operand's predicate can recognize registers, but the constraint
-does not permit them, it can make the compiler crash. When this operand
-happens to be a register, the reload pass will be stymied, because it
-does not know how to copy a register temporarily into memory.
+does not permit them, it can make the compiler crash. When this
+operand happens to be a register, the reload pass will be stymied,
+because it does not know how to copy a register temporarily into memory.
If the predicate accepts a unary operator, the constraint applies to
the operand. For example, the MIPS processor at ISA level 3 supports an
-instruction which adds two registers in 'SImode' to produce a 'DImode'
+instruction which adds two registers in `SImode' to produce a `DImode'
result, but only if the registers are correctly sign extended. This
-predicate for the input operands accepts a 'sign_extend' of an 'SImode'
-register. Write the constraint to indicate the type of register that is
-required for the operand of the 'sign_extend'.
+predicate for the input operands accepts a `sign_extend' of an `SImode'
+register. Write the constraint to indicate the type of register that
+is required for the operand of the `sign_extend'.

File: gccint.info, Node: Multi-Alternative, Next: Class Preferences, Prev: Simple Constraints, Up: Constraints
@@ -19697,46 +19915,47 @@ alternative. Here is how it is done for fullword logical-or on the
(match_operand:SI 2 "general_operand" "dKs,dmKs")))]
...)
- The first alternative has 'm' (memory) for operand 0, '0' for operand 1
-(meaning it must match operand 0), and 'dKs' for operand 2. The second
-alternative has 'd' (data register) for operand 0, '0' for operand 1,
-and 'dmKs' for operand 2. The '=' and '%' in the constraints apply to
-all the alternatives; their meaning is explained in the next section
-(*note Class Preferences::).
+ The first alternative has `m' (memory) for operand 0, `0' for operand
+1 (meaning it must match operand 0), and `dKs' for operand 2. The
+second alternative has `d' (data register) for operand 0, `0' for
+operand 1, and `dmKs' for operand 2. The `=' and `%' in the
+constraints apply to all the alternatives; their meaning is explained
+in the next section (*note Class Preferences::).
If all the operands fit any one alternative, the instruction is valid.
Otherwise, for each alternative, the compiler counts how many
-instructions must be added to copy the operands so that that alternative
-applies. The alternative requiring the least copying is chosen. If two
-alternatives need the same amount of copying, the one that comes first
-is chosen. These choices can be altered with the '?' and '!'
-characters:
-
-'?'
- Disparage slightly the alternative that the '?' appears in, as a
+instructions must be added to copy the operands so that that
+alternative applies. The alternative requiring the least copying is
+chosen. If two alternatives need the same amount of copying, the one
+that comes first is chosen. These choices can be altered with the `?'
+and `!' characters:
+
+`?'
+ Disparage slightly the alternative that the `?' appears in, as a
choice when no alternative applies exactly. The compiler regards
- this alternative as one unit more costly for each '?' that appears
+ this alternative as one unit more costly for each `?' that appears
in it.
-'!'
- Disparage severely the alternative that the '!' appears in. This
+`!'
+ Disparage severely the alternative that the `!' appears in. This
alternative can still be used if it fits without reloading, but if
reloading is needed, some other alternative will be used.
-'^'
- This constraint is analogous to '?' but it disparages slightly the
- alternative only if the operand with the '^' needs a reload.
+`^'
+ This constraint is analogous to `?' but it disparages slightly the
+ alternative only if the operand with the `^' needs a reload.
-'$'
- This constraint is analogous to '!' but it disparages severely the
- alternative only if the operand with the '$' needs a reload.
+`$'
+ This constraint is analogous to `!' but it disparages severely the
+ alternative only if the operand with the `$' needs a reload.
When an insn pattern has multiple alternatives in its constraints,
often the appearance of the assembler code is determined mostly by which
alternative was matched. When this is so, the C code for writing the
-assembler code can use the variable 'which_alternative', which is the
-ordinal number of the alternative that was actually satisfied (0 for the
-first, 1 for the second alternative, etc.). *Note Output Statement::.
+assembler code can use the variable `which_alternative', which is the
+ordinal number of the alternative that was actually satisfied (0 for
+the first, 1 for the second alternative, etc.). *Note Output
+Statement::.

File: gccint.info, Node: Class Preferences, Next: Modifiers, Prev: Multi-Alternative, Up: Constraints
@@ -19748,9 +19967,9 @@ The operand constraints have another function: they enable the compiler
to decide which kind of hardware register a pseudo register is best
allocated to. The compiler examines the constraints that apply to the
insns that use the pseudo register, looking for the machine-dependent
-letters such as 'd' and 'a' that specify classes of registers. The
+letters such as `d' and `a' that specify classes of registers. The
pseudo register is put in whichever class gets the most "votes". The
-constraint letters 'g' and 'r' also vote: they vote in favor of a
+constraint letters `g' and `r' also vote: they vote in favor of a
general register. The machine description says which registers are
considered general.
@@ -19765,57 +19984,57 @@ File: gccint.info, Node: Modifiers, Next: Machine Constraints, Prev: Class Pr
Here are constraint modifier characters.
-'='
+`='
Means that this operand is written to by this instruction: the
previous value is discarded and replaced by new data.
-'+'
+`+'
Means that this operand is both read and written by the
instruction.
When the compiler fixes up the operands to satisfy the constraints,
it needs to know which operands are read by the instruction and
- which are written by it. '=' identifies an operand which is only
- written; '+' identifies an operand that is both read and written;
+ which are written by it. `=' identifies an operand which is only
+ written; `+' identifies an operand that is both read and written;
all other operands are assumed to only be read.
- If you specify '=' or '+' in a constraint, you put it in the first
+ If you specify `=' or `+' in a constraint, you put it in the first
character of the constraint string.
-'&'
+`&'
Means (in a particular alternative) that this operand is an
"earlyclobber" operand, which is written before the instruction is
- finished using the input operands. Therefore, this operand may not
- lie in a register that is read by the instruction or as part of any
- memory address.
+ finished using the input operands. Therefore, this operand may
+ not lie in a register that is read by the instruction or as part
+ of any memory address.
- '&' applies only to the alternative in which it is written. In
+ `&' applies only to the alternative in which it is written. In
constraints with multiple alternatives, sometimes one alternative
- requires '&' while others do not. See, for example, the 'movdf'
+ requires `&' while others do not. See, for example, the `movdf'
insn of the 68000.
A operand which is read by the instruction can be tied to an
earlyclobber operand if its only use as an input occurs before the
early result is written. Adding alternatives of this form often
allows GCC to produce better code when only some of the read
- operands can be affected by the earlyclobber. See, for example,
- the 'mulsi3' insn of the ARM.
+ operands can be affected by the earlyclobber. See, for example,
+ the `mulsi3' insn of the ARM.
Furthermore, if the "earlyclobber" operand is also a read/write
operand, then that operand is written only after it's used.
- '&' does not obviate the need to write '=' or '+'. As
+ `&' does not obviate the need to write `=' or `+'. As
"earlyclobber" operands are always written, a read-only
"earlyclobber" operand is ill-formed and will be rejected by the
compiler.
-'%'
+`%'
Declares the instruction to be commutative for this operand and the
following operand. This means that the compiler may interchange
the two operands if that is the cheapest way to make all operands
- fit the constraints. '%' applies to all alternatives and must
+ fit the constraints. `%' applies to all alternatives and must
appear as the first character in the constraint. Only read-only
- operands can use '%'.
+ operands can use `%'.
This is often used in patterns for addition instructions that
really have only two operands: the result must go in one of the
@@ -19829,32 +20048,32 @@ Here are constraint modifier characters.
...)
GCC can only handle one commutative pair in an asm; if you use
more, the compiler may fail. Note that you need not use the
- modifier if the two alternatives are strictly identical; this would
- only waste time in the reload pass. The modifier is not
+ modifier if the two alternatives are strictly identical; this
+ would only waste time in the reload pass. The modifier is not
operational after register allocation, so the result of
- 'define_peephole2' and 'define_split's performed after reload
- cannot rely on '%' to make the intended insn match.
+ `define_peephole2' and `define_split's performed after reload
+ cannot rely on `%' to make the intended insn match.
-'#'
+`#'
Says that all following characters, up to the next comma, are to be
ignored as a constraint. They are significant only for choosing
register preferences.
-'*'
+`*'
Says that the following character should be ignored when choosing
- register preferences. '*' has no effect on the meaning of the
+ register preferences. `*' has no effect on the meaning of the
constraint as a constraint, and no effect on reloading. For LRA
- '*' additionally disparages slightly the alternative if the
+ `*' additionally disparages slightly the alternative if the
following character matches the operand.
Here is an example: the 68000 has an instruction to sign-extend a
halfword in a data register, and can also sign-extend a value by
- copying it into an address register. While either kind of register
- is acceptable, the constraints on an address-register destination
- are less strict, so it is best if register allocation makes an
- address register its goal. Therefore, '*' is used so that the 'd'
- constraint letter (for data register) is ignored when computing
- register preferences.
+ copying it into an address register. While either kind of
+ register is acceptable, the constraints on an address-register
+ destination are less strict, so it is best if register allocation
+ makes an address register its goal. Therefore, `*' is used so
+ that the `d' constraint letter (for data register) is ignored when
+ computing register preferences.
(define_insn "extendhisi2"
[(set (match_operand:SI 0 "general_operand" "=*d,a")
@@ -19869,1462 +20088,1542 @@ File: gccint.info, Node: Machine Constraints, Next: Disable Insn Alternatives,
------------------------------------------
Whenever possible, you should use the general-purpose constraint letters
-in 'asm' arguments, since they will convey meaning more readily to
-people reading your code. Failing that, use the constraint letters that
-usually have very similar meanings across architectures. The most
-commonly used constraints are 'm' and 'r' (for memory and
+in `asm' arguments, since they will convey meaning more readily to
+people reading your code. Failing that, use the constraint letters
+that usually have very similar meanings across architectures. The most
+commonly used constraints are `m' and `r' (for memory and
general-purpose registers respectively; *note Simple Constraints::), and
-'I', usually the letter indicating the most common immediate-constant
+`I', usually the letter indicating the most common immediate-constant
format.
Each architecture defines additional constraints. These constraints
are used by the compiler itself for instruction generation, as well as
-for 'asm' statements; therefore, some of the constraints are not
-particularly useful for 'asm'. Here is a summary of some of the
+for `asm' statements; therefore, some of the constraints are not
+particularly useful for `asm'. Here is a summary of some of the
machine-dependent constraints available on some particular machines; it
-includes both constraints that are useful for 'asm' and constraints that
-aren't. The compiler source file mentioned in the table heading for
-each architecture is the definitive reference for the meanings of that
-architecture's constraints.
+includes both constraints that are useful for `asm' and constraints
+that aren't. The compiler source file mentioned in the table heading
+for each architecture is the definitive reference for the meanings of
+that architecture's constraints.
+
+_AArch64 family--`config/aarch64/constraints.md'_
-_AArch64 family--'config/aarch64/constraints.md'_
- 'k'
- The stack pointer register ('SP')
+ `k'
+ The stack pointer register (`SP')
- 'w'
+ `w'
Floating point or SIMD vector register
- 'I'
+ `I'
Integer constant that is valid as an immediate operand in an
- 'ADD' instruction
+ `ADD' instruction
- 'J'
+ `J'
Integer constant that is valid as an immediate operand in a
- 'SUB' instruction (once negated)
+ `SUB' instruction (once negated)
- 'K'
+ `K'
Integer constant that can be used with a 32-bit logical
instruction
- 'L'
+ `L'
Integer constant that can be used with a 64-bit logical
instruction
- 'M'
+ `M'
Integer constant that is valid as an immediate operand in a
- 32-bit 'MOV' pseudo instruction. The 'MOV' may be assembled
+ 32-bit `MOV' pseudo instruction. The `MOV' may be assembled
to one of several different machine instructions depending on
the value
- 'N'
+ `N'
Integer constant that is valid as an immediate operand in a
- 64-bit 'MOV' pseudo instruction
+ 64-bit `MOV' pseudo instruction
- 'S'
+ `S'
An absolute symbolic address or a label reference
- 'Y'
+ `Y'
Floating point constant zero
- 'Z'
+ `Z'
Integer constant zero
- 'Ush'
- The high part (bits 12 and upwards) of the pc-relative address
- of a symbol within 4GB of the instruction
+ `Ush'
+ The high part (bits 12 and upwards) of the pc-relative
+ address of a symbol within 4GB of the instruction
- 'Q'
+ `Q'
A memory address which uses a single base register with no
offset
- 'Ump'
- A memory address suitable for a load/store pair instruction in
- SI, DI, SF and DF modes
+ `Ump'
+ A memory address suitable for a load/store pair instruction
+ in SI, DI, SF and DF modes
+
-_ARC --'config/arc/constraints.md'_
- 'q'
- Registers usable in ARCompact 16-bit instructions: 'r0'-'r3',
- 'r12'-'r15'. This constraint can only match when the '-mq'
+_ARC --`config/arc/constraints.md'_
+
+ `q'
+ Registers usable in ARCompact 16-bit instructions: `r0'-`r3',
+ `r12'-`r15'. This constraint can only match when the `-mq'
option is in effect.
- 'e'
- Registers usable as base-regs of memory addresses in ARCompact
- 16-bit memory instructions: 'r0'-'r3', 'r12'-'r15', 'sp'.
- This constraint can only match when the '-mq' option is in
- effect.
- 'D'
- ARC FPX (dpfp) 64-bit registers. 'D0', 'D1'.
+ `e'
+ Registers usable as base-regs of memory addresses in
+ ARCompact 16-bit memory instructions: `r0'-`r3', `r12'-`r15',
+ `sp'. This constraint can only match when the `-mq' option
+ is in effect.
+
+ `D'
+ ARC FPX (dpfp) 64-bit registers. `D0', `D1'.
- 'I'
+ `I'
A signed 12-bit integer constant.
- 'Cal'
- constant for arithmetic/logical operations. This might be any
- constant that can be put into a long immediate by the assmbler
- or linker without involving a PIC relocation.
+ `Cal'
+ constant for arithmetic/logical operations. This might be
+ any constant that can be put into a long immediate by the
+ assmbler or linker without involving a PIC relocation.
- 'K'
+ `K'
A 3-bit unsigned integer constant.
- 'L'
+ `L'
A 6-bit unsigned integer constant.
- 'CnL'
+ `CnL'
One's complement of a 6-bit unsigned integer constant.
- 'CmL'
+ `CmL'
Two's complement of a 6-bit unsigned integer constant.
- 'M'
+ `M'
A 5-bit unsigned integer constant.
- 'O'
+ `O'
A 7-bit unsigned integer constant.
- 'P'
+ `P'
A 8-bit unsigned integer constant.
- 'H'
+ `H'
Any const_double value.
-_ARM family--'config/arm/constraints.md'_
+_ARM family--`config/arm/constraints.md'_
- 'h'
- In Thumb state, the core registers 'r8'-'r15'.
+ `h'
+ In Thumb state, the core registers `r8'-`r15'.
- 'k'
+ `k'
The stack pointer register.
- 'l'
- In Thumb State the core registers 'r0'-'r7'. In ARM state
- this is an alias for the 'r' constraint.
+ `l'
+ In Thumb State the core registers `r0'-`r7'. In ARM state
+ this is an alias for the `r' constraint.
- 't'
- VFP floating-point registers 's0'-'s31'. Used for 32 bit
+ `t'
+ VFP floating-point registers `s0'-`s31'. Used for 32 bit
values.
- 'w'
- VFP floating-point registers 'd0'-'d31' and the appropriate
- subset 'd0'-'d15' based on command line options. Used for 64
+ `w'
+ VFP floating-point registers `d0'-`d31' and the appropriate
+ subset `d0'-`d15' based on command line options. Used for 64
bit values only. Not valid for Thumb1.
- 'y'
+ `y'
The iWMMX co-processor registers.
- 'z'
+ `z'
The iWMMX GR registers.
- 'G'
+ `G'
The floating-point constant 0.0
- 'I'
+ `I'
Integer that is valid as an immediate operand in a data
- processing instruction. That is, an integer in the range 0 to
- 255 rotated by a multiple of 2
+ processing instruction. That is, an integer in the range 0
+ to 255 rotated by a multiple of 2
- 'J'
+ `J'
Integer in the range -4095 to 4095
- 'K'
- Integer that satisfies constraint 'I' when inverted (ones
+ `K'
+ Integer that satisfies constraint `I' when inverted (ones
complement)
- 'L'
- Integer that satisfies constraint 'I' when negated (twos
+ `L'
+ Integer that satisfies constraint `I' when negated (twos
complement)
- 'M'
+ `M'
Integer in the range 0 to 32
- 'Q'
+ `Q'
A memory reference where the exact address is in a single
- register (''m'' is preferable for 'asm' statements)
+ register (``m'' is preferable for `asm' statements)
- 'R'
+ `R'
An item in the constant pool
- 'S'
+ `S'
A symbol in the text segment of the current file
- 'Uv'
+ `Uv'
A memory reference suitable for VFP load/store insns
(reg+constant offset)
- 'Uy'
+ `Uy'
A memory reference suitable for iWMMXt load/store
instructions.
- 'Uq'
+ `Uq'
A memory reference suitable for the ARMv4 ldrsb instruction.
-_AVR family--'config/avr/constraints.md'_
- 'l'
+_AVR family--`config/avr/constraints.md'_
+
+ `l'
Registers from r0 to r15
- 'a'
+ `a'
Registers from r16 to r23
- 'd'
+ `d'
Registers from r16 to r31
- 'w'
+ `w'
Registers from r24 to r31. These registers can be used in
- 'adiw' command
+ `adiw' command
- 'e'
+ `e'
Pointer register (r26-r31)
- 'b'
+ `b'
Base pointer register (r28-r31)
- 'q'
+ `q'
Stack pointer register (SPH:SPL)
- 't'
+ `t'
Temporary register r0
- 'x'
+ `x'
Register pair X (r27:r26)
- 'y'
+ `y'
Register pair Y (r29:r28)
- 'z'
+ `z'
Register pair Z (r31:r30)
- 'I'
+ `I'
Constant greater than -1, less than 64
- 'J'
+ `J'
Constant greater than -64, less than 1
- 'K'
+ `K'
Constant integer 2
- 'L'
+ `L'
Constant integer 0
- 'M'
+ `M'
Constant that fits in 8 bits
- 'N'
+ `N'
Constant integer -1
- 'O'
+ `O'
Constant integer 8, 16, or 24
- 'P'
+ `P'
Constant integer 1
- 'G'
+ `G'
A floating point constant 0.0
- 'Q'
+ `Q'
A memory address based on Y or Z pointer with displacement.
-_Blackfin family--'config/bfin/constraints.md'_
- 'a'
+_Blackfin family--`config/bfin/constraints.md'_
+
+ `a'
P register
- 'd'
+ `d'
D register
- 'z'
+ `z'
A call clobbered P register.
- 'qN'
+ `qN'
A single register. If N is in the range 0 to 7, the
- corresponding D register. If it is 'A', then the register P0.
+ corresponding D register. If it is `A', then the register P0.
- 'D'
+ `D'
Even-numbered D register
- 'W'
+ `W'
Odd-numbered D register
- 'e'
+ `e'
Accumulator register.
- 'A'
+ `A'
Even-numbered accumulator register.
- 'B'
+ `B'
Odd-numbered accumulator register.
- 'b'
+ `b'
I register
- 'v'
+ `v'
B register
- 'f'
+ `f'
M register
- 'c'
- Registers used for circular buffering, i.e. I, B, or L
+ `c'
+ Registers used for circular buffering, i.e. I, B, or L
registers.
- 'C'
+ `C'
The CC register.
- 't'
+ `t'
LT0 or LT1.
- 'k'
+ `k'
LC0 or LC1.
- 'u'
+ `u'
LB0 or LB1.
- 'x'
+ `x'
Any D, P, B, M, I or L register.
- 'y'
+ `y'
Additional registers typically used only in prologues and
epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and
USP.
- 'w'
+ `w'
Any register except accumulators or CC.
- 'Ksh'
+ `Ksh'
Signed 16 bit integer (in the range -32768 to 32767)
- 'Kuh'
+ `Kuh'
Unsigned 16 bit integer (in the range 0 to 65535)
- 'Ks7'
+ `Ks7'
Signed 7 bit integer (in the range -64 to 63)
- 'Ku7'
+ `Ku7'
Unsigned 7 bit integer (in the range 0 to 127)
- 'Ku5'
+ `Ku5'
Unsigned 5 bit integer (in the range 0 to 31)
- 'Ks4'
+ `Ks4'
Signed 4 bit integer (in the range -8 to 7)
- 'Ks3'
+ `Ks3'
Signed 3 bit integer (in the range -3 to 4)
- 'Ku3'
+ `Ku3'
Unsigned 3 bit integer (in the range 0 to 7)
- 'PN'
+ `PN'
Constant N, where N is a single-digit constant in the range 0
to 4.
- 'PA'
+ `PA'
An integer equal to one of the MACFLAG_XXX constants that is
suitable for use with either accumulator.
- 'PB'
+ `PB'
An integer equal to one of the MACFLAG_XXX constants that is
suitable for use only with accumulator A1.
- 'M1'
+ `M1'
Constant 255.
- 'M2'
+ `M2'
Constant 65535.
- 'J'
+ `J'
An integer constant with exactly a single bit set.
- 'L'
+ `L'
An integer constant with all bits set except exactly one.
- 'H'
+ `H'
- 'Q'
+ `Q'
Any SYMBOL_REF.
-_CR16 Architecture--'config/cr16/cr16.h'_
+_CR16 Architecture--`config/cr16/cr16.h'_
- 'b'
+ `b'
Registers from r0 to r14 (registers without stack pointer)
- 't'
+ `t'
Register from r0 to r11 (all 16-bit registers)
- 'p'
+ `p'
Register from r12 to r15 (all 32-bit registers)
- 'I'
+ `I'
Signed constant that fits in 4 bits
- 'J'
+ `J'
Signed constant that fits in 5 bits
- 'K'
+ `K'
Signed constant that fits in 6 bits
- 'L'
+ `L'
Unsigned constant that fits in 4 bits
- 'M'
+ `M'
Signed constant that fits in 32 bits
- 'N'
+ `N'
Check for 64 bits wide constants for add/sub instructions
- 'G'
+ `G'
Floating point constant that is legal for store immediate
-_Epiphany--'config/epiphany/constraints.md'_
- 'U16'
+_Epiphany--`config/epiphany/constraints.md'_
+
+ `U16'
An unsigned 16-bit constant.
- 'K'
+ `K'
An unsigned 5-bit constant.
- 'L'
+ `L'
A signed 11-bit constant.
- 'Cm1'
- A signed 11-bit constant added to -1. Can only match when the
- '-m1reg-REG' option is active.
+ `Cm1'
+ A signed 11-bit constant added to -1. Can only match when
+ the `-m1reg-REG' option is active.
- 'Cl1'
+ `Cl1'
Left-shift of -1, i.e., a bit mask with a block of leading
ones, the rest being a block of trailing zeroes. Can only
- match when the '-m1reg-REG' option is active.
+ match when the `-m1reg-REG' option is active.
- 'Cr1'
+ `Cr1'
Right-shift of -1, i.e., a bit mask with a trailing block of
ones, the rest being zeroes. Or to put it another way, one
less than a power of two. Can only match when the
- '-m1reg-REG' option is active.
+ `-m1reg-REG' option is active.
- 'Cal'
- Constant for arithmetic/logical operations. This is like 'i',
- except that for position independent code, no symbols /
+ `Cal'
+ Constant for arithmetic/logical operations. This is like
+ `i', except that for position independent code, no symbols /
expressions needing relocations are allowed.
- 'Csy'
+ `Csy'
Symbolic constant for call/jump instruction.
- 'Rcs'
+ `Rcs'
The register class usable in short insns. This is a register
class constraint, and can thus drive register allocation.
- This constraint won't match unless '-mprefer-short-insn-regs'
+ This constraint won't match unless `-mprefer-short-insn-regs'
is in effect.
- 'Rsc'
+ `Rsc'
The the register class of registers that can be used to hold a
sibcall call address. I.e., a caller-saved register.
- 'Rct'
+ `Rct'
Core control register class.
- 'Rgs'
+ `Rgs'
The register group usable in short insns. This constraint
does not use a register class, so that it only passively
matches suitable registers, and doesn't drive register
allocation.
- 'Car'
+ `Car'
Constant suitable for the addsi3_r pattern. This is a valid
offset For byte, halfword, or word addressing.
- 'Rra'
- Matches the return address if it can be replaced with the link
- register.
+ `Rra'
+ Matches the return address if it can be replaced with the
+ link register.
- 'Rcc'
+ `Rcc'
Matches the integer condition code register.
- 'Sra'
+ `Sra'
Matches the return address if it is in a stack slot.
- 'Cfm'
+ `Cfm'
Matches control register values to switch fp mode, which are
- encapsulated in 'UNSPEC_FP_MODE'.
+ encapsulated in `UNSPEC_FP_MODE'.
-_FRV--'config/frv/frv.h'_
- 'a'
- Register in the class 'ACC_REGS' ('acc0' to 'acc7').
+_FRV--`config/frv/frv.h'_
- 'b'
- Register in the class 'EVEN_ACC_REGS' ('acc0' to 'acc7').
+ `a'
+ Register in the class `ACC_REGS' (`acc0' to `acc7').
- 'c'
- Register in the class 'CC_REGS' ('fcc0' to 'fcc3' and 'icc0'
- to 'icc3').
+ `b'
+ Register in the class `EVEN_ACC_REGS' (`acc0' to `acc7').
- 'd'
- Register in the class 'GPR_REGS' ('gr0' to 'gr63').
+ `c'
+ Register in the class `CC_REGS' (`fcc0' to `fcc3' and `icc0'
+ to `icc3').
- 'e'
- Register in the class 'EVEN_REGS' ('gr0' to 'gr63'). Odd
- registers are excluded not in the class but through the use of
- a machine mode larger than 4 bytes.
+ `d'
+ Register in the class `GPR_REGS' (`gr0' to `gr63').
- 'f'
- Register in the class 'FPR_REGS' ('fr0' to 'fr63').
+ `e'
+ Register in the class `EVEN_REGS' (`gr0' to `gr63'). Odd
+ registers are excluded not in the class but through the use
+ of a machine mode larger than 4 bytes.
- 'h'
- Register in the class 'FEVEN_REGS' ('fr0' to 'fr63'). Odd
- registers are excluded not in the class but through the use of
- a machine mode larger than 4 bytes.
+ `f'
+ Register in the class `FPR_REGS' (`fr0' to `fr63').
- 'l'
- Register in the class 'LR_REG' (the 'lr' register).
+ `h'
+ Register in the class `FEVEN_REGS' (`fr0' to `fr63'). Odd
+ registers are excluded not in the class but through the use
+ of a machine mode larger than 4 bytes.
- 'q'
- Register in the class 'QUAD_REGS' ('gr2' to 'gr63'). Register
- numbers not divisible by 4 are excluded not in the class but
- through the use of a machine mode larger than 8 bytes.
+ `l'
+ Register in the class `LR_REG' (the `lr' register).
- 't'
- Register in the class 'ICC_REGS' ('icc0' to 'icc3').
+ `q'
+ Register in the class `QUAD_REGS' (`gr2' to `gr63').
+ Register numbers not divisible by 4 are excluded not in the
+ class but through the use of a machine mode larger than 8
+ bytes.
+
+ `t'
+ Register in the class `ICC_REGS' (`icc0' to `icc3').
- 'u'
- Register in the class 'FCC_REGS' ('fcc0' to 'fcc3').
+ `u'
+ Register in the class `FCC_REGS' (`fcc0' to `fcc3').
- 'v'
- Register in the class 'ICR_REGS' ('cc4' to 'cc7').
+ `v'
+ Register in the class `ICR_REGS' (`cc4' to `cc7').
- 'w'
- Register in the class 'FCR_REGS' ('cc0' to 'cc3').
+ `w'
+ Register in the class `FCR_REGS' (`cc0' to `cc3').
- 'x'
- Register in the class 'QUAD_FPR_REGS' ('fr0' to 'fr63').
+ `x'
+ Register in the class `QUAD_FPR_REGS' (`fr0' to `fr63').
Register numbers not divisible by 4 are excluded not in the
class but through the use of a machine mode larger than 8
bytes.
- 'z'
- Register in the class 'SPR_REGS' ('lcr' and 'lr').
+ `z'
+ Register in the class `SPR_REGS' (`lcr' and `lr').
- 'A'
- Register in the class 'QUAD_ACC_REGS' ('acc0' to 'acc7').
+ `A'
+ Register in the class `QUAD_ACC_REGS' (`acc0' to `acc7').
- 'B'
- Register in the class 'ACCG_REGS' ('accg0' to 'accg7').
+ `B'
+ Register in the class `ACCG_REGS' (`accg0' to `accg7').
- 'C'
- Register in the class 'CR_REGS' ('cc0' to 'cc7').
+ `C'
+ Register in the class `CR_REGS' (`cc0' to `cc7').
- 'G'
+ `G'
Floating point constant zero
- 'I'
+ `I'
6-bit signed integer constant
- 'J'
+ `J'
10-bit signed integer constant
- 'L'
+ `L'
16-bit signed integer constant
- 'M'
+ `M'
16-bit unsigned integer constant
- 'N'
+ `N'
12-bit signed integer constant that is negative--i.e. in the
range of -2048 to -1
- 'O'
+ `O'
Constant zero
- 'P'
- 12-bit signed integer constant that is greater than zero--i.e.
- in the range of 1 to 2047.
+ `P'
+ 12-bit signed integer constant that is greater than
+ zero--i.e. in the range of 1 to 2047.
+
+
+_Hewlett-Packard PA-RISC--`config/pa/pa.h'_
-_Hewlett-Packard PA-RISC--'config/pa/pa.h'_
- 'a'
+ `a'
General register 1
- 'f'
+ `f'
Floating point register
- 'q'
+ `q'
Shift amount register
- 'x'
+ `x'
Floating point register (deprecated)
- 'y'
+ `y'
Upper floating point register (32-bit), floating point
register (64-bit)
- 'Z'
+ `Z'
Any register
- 'I'
+ `I'
Signed 11-bit integer constant
- 'J'
+ `J'
Signed 14-bit integer constant
- 'K'
- Integer constant that can be deposited with a 'zdepi'
+ `K'
+ Integer constant that can be deposited with a `zdepi'
instruction
- 'L'
+ `L'
Signed 5-bit integer constant
- 'M'
+ `M'
Integer constant 0
- 'N'
- Integer constant that can be loaded with a 'ldil' instruction
+ `N'
+ Integer constant that can be loaded with a `ldil' instruction
- 'O'
+ `O'
Integer constant whose value plus one is a power of 2
- 'P'
- Integer constant that can be used for 'and' operations in
- 'depi' and 'extru' instructions
+ `P'
+ Integer constant that can be used for `and' operations in
+ `depi' and `extru' instructions
- 'S'
+ `S'
Integer constant 31
- 'U'
+ `U'
Integer constant 63
- 'G'
+ `G'
Floating-point constant 0.0
- 'A'
- A 'lo_sum' data-linkage-table memory operand
+ `A'
+ A `lo_sum' data-linkage-table memory operand
- 'Q'
+ `Q'
A memory operand that can be used as the destination operand
of an integer store instruction
- 'R'
+ `R'
A scaled or unscaled indexed memory operand
- 'T'
+ `T'
A memory operand for floating-point loads and stores
- 'W'
+ `W'
A register indirect memory operand
-_Intel IA-64--'config/ia64/ia64.h'_
- 'a'
- General register 'r0' to 'r3' for 'addl' instruction
+_Intel IA-64--`config/ia64/ia64.h'_
- 'b'
+ `a'
+ General register `r0' to `r3' for `addl' instruction
+
+ `b'
Branch register
- 'c'
- Predicate register ('c' as in "conditional")
+ `c'
+ Predicate register (`c' as in "conditional")
- 'd'
+ `d'
Application register residing in M-unit
- 'e'
+ `e'
Application register residing in I-unit
- 'f'
+ `f'
Floating-point register
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement and postdecrement which require
- printing with '%Pn' on IA-64.
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement and postdecrement which
+ require printing with `%Pn' on IA-64.
- 'G'
+ `G'
Floating-point constant 0.0 or 1.0
- 'I'
+ `I'
14-bit signed integer constant
- 'J'
+ `J'
22-bit signed integer constant
- 'K'
+ `K'
8-bit signed integer constant for logical instructions
- 'L'
+ `L'
8-bit adjusted signed integer constant for compare pseudo-ops
- 'M'
+ `M'
6-bit unsigned integer constant for shift counts
- 'N'
+ `N'
9-bit signed integer constant for load and store
postincrements
- 'O'
+ `O'
The constant zero
- 'P'
- 0 or -1 for 'dep' instruction
+ `P'
+ 0 or -1 for `dep' instruction
- 'Q'
+ `Q'
Non-volatile memory for floating-point loads and stores
- 'R'
- Integer constant in the range 1 to 4 for 'shladd' instruction
+ `R'
+ Integer constant in the range 1 to 4 for `shladd' instruction
- 'S'
+ `S'
Memory operand except postincrement and postdecrement. This
- is now roughly the same as 'm' when not used together with '<'
- or '>'.
+ is now roughly the same as `m' when not used together with `<'
+ or `>'.
+
+_M32C--`config/m32c/m32c.c'_
-_M32C--'config/m32c/m32c.c'_
- 'Rsp'
- 'Rfb'
- 'Rsb'
- '$sp', '$fb', '$sb'.
+ `Rsp'
+ `Rfb'
+ `Rsb'
+ `$sp', `$fb', `$sb'.
- 'Rcr'
+ `Rcr'
Any control register, when they're 16 bits wide (nothing if
control registers are 24 bits wide)
- 'Rcl'
+ `Rcl'
Any control register, when they're 24 bits wide.
- 'R0w'
- 'R1w'
- 'R2w'
- 'R3w'
+ `R0w'
+ `R1w'
+ `R2w'
+ `R3w'
$r0, $r1, $r2, $r3.
- 'R02'
+ `R02'
$r0 or $r2, or $r2r0 for 32 bit values.
- 'R13'
+ `R13'
$r1 or $r3, or $r3r1 for 32 bit values.
- 'Rdi'
+ `Rdi'
A register that can hold a 64 bit value.
- 'Rhl'
+ `Rhl'
$r0 or $r1 (registers with addressable high/low bytes)
- 'R23'
+ `R23'
$r2 or $r3
- 'Raa'
+ `Raa'
Address registers
- 'Raw'
+ `Raw'
Address registers when they're 16 bits wide.
- 'Ral'
+ `Ral'
Address registers when they're 24 bits wide.
- 'Rqi'
+ `Rqi'
Registers that can hold QI values.
- 'Rad'
+ `Rad'
Registers that can be used with displacements ($a0, $a1, $sb).
- 'Rsi'
+ `Rsi'
Registers that can hold 32 bit values.
- 'Rhi'
+ `Rhi'
Registers that can hold 16 bit values.
- 'Rhc'
+ `Rhc'
Registers chat can hold 16 bit values, including all control
registers.
- 'Rra'
+ `Rra'
$r0 through R1, plus $a0 and $a1.
- 'Rfl'
+ `Rfl'
The flags register.
- 'Rmm'
+ `Rmm'
The memory-based pseudo-registers $mem0 through $mem15.
- 'Rpi'
+ `Rpi'
Registers that can hold pointers (16 bit registers for r8c,
m16c; 24 bit registers for m32cm, m32c).
- 'Rpa'
+ `Rpa'
Matches multiple registers in a PARALLEL to form a larger
register. Used to match function return values.
- 'Is3'
+ `Is3'
-8 ... 7
- 'IS1'
+ `IS1'
-128 ... 127
- 'IS2'
+ `IS2'
-32768 ... 32767
- 'IU2'
+ `IU2'
0 ... 65535
- 'In4'
+ `In4'
-8 ... -1 or 1 ... 8
- 'In5'
+ `In5'
-16 ... -1 or 1 ... 16
- 'In6'
+ `In6'
-32 ... -1 or 1 ... 32
- 'IM2'
+ `IM2'
-65536 ... -1
- 'Ilb'
+ `Ilb'
An 8 bit value with exactly one bit set.
- 'Ilw'
+ `Ilw'
A 16 bit value with exactly one bit set.
- 'Sd'
+ `Sd'
The common src/dest memory addressing modes.
- 'Sa'
+ `Sa'
Memory addressed using $a0 or $a1.
- 'Si'
+ `Si'
Memory addressed with immediate addresses.
- 'Ss'
+ `Ss'
Memory addressed using the stack pointer ($sp).
- 'Sf'
+ `Sf'
Memory addressed using the frame base register ($fb).
- 'Ss'
+ `Ss'
Memory addressed using the small base register ($sb).
- 'S1'
+ `S1'
$r1h
-_MeP--'config/mep/constraints.md'_
+_MeP--`config/mep/constraints.md'_
- 'a'
+ `a'
The $sp register.
- 'b'
+ `b'
The $tp register.
- 'c'
+ `c'
Any control register.
- 'd'
+ `d'
Either the $hi or the $lo register.
- 'em'
+ `em'
Coprocessor registers that can be directly loaded ($c0-$c15).
- 'ex'
+ `ex'
Coprocessor registers that can be moved to each other.
- 'er'
+ `er'
Coprocessor registers that can be moved to core registers.
- 'h'
+ `h'
The $hi register.
- 'j'
+ `j'
The $rpc register.
- 'l'
+ `l'
The $lo register.
- 't'
+ `t'
Registers which can be used in $tp-relative addressing.
- 'v'
+ `v'
The $gp register.
- 'x'
+ `x'
The coprocessor registers.
- 'y'
+ `y'
The coprocessor control registers.
- 'z'
+ `z'
The $0 register.
- 'A'
+ `A'
User-defined register set A.
- 'B'
+ `B'
User-defined register set B.
- 'C'
+ `C'
User-defined register set C.
- 'D'
+ `D'
User-defined register set D.
- 'I'
+ `I'
Offsets for $gp-rel addressing.
- 'J'
+ `J'
Constants that can be used directly with boolean insns.
- 'K'
+ `K'
Constants that can be moved directly to registers.
- 'L'
+ `L'
Small constants that can be added to registers.
- 'M'
+ `M'
Long shift counts.
- 'N'
+ `N'
Small constants that can be compared to registers.
- 'O'
+ `O'
Constants that can be loaded into the top half of registers.
- 'S'
+ `S'
Signed 8-bit immediates.
- 'T'
+ `T'
Symbols encoded for $tp-rel or $gp-rel addressing.
- 'U'
+ `U'
Non-constant addresses for loading/saving coprocessor
registers.
- 'W'
+ `W'
The top half of a symbol's value.
- 'Y'
+ `Y'
A register indirect address without offset.
- 'Z'
+ `Z'
Symbolic references to the control bus.
-_MicroBlaze--'config/microblaze/constraints.md'_
- 'd'
- A general register ('r0' to 'r31').
- 'z'
- A status register ('rmsr', '$fcc1' to '$fcc7').
+_MicroBlaze--`config/microblaze/constraints.md'_
+
+ `d'
+ A general register (`r0' to `r31').
+
+ `z'
+ A status register (`rmsr', `$fcc1' to `$fcc7').
+
-_MIPS--'config/mips/constraints.md'_
- 'd'
- An address register. This is equivalent to 'r' unless
+_MIPS--`config/mips/constraints.md'_
+
+ `d'
+ An address register. This is equivalent to `r' unless
generating MIPS16 code.
- 'f'
+ `f'
A floating-point register (if available).
- 'h'
- Formerly the 'hi' register. This constraint is no longer
+ `h'
+ Formerly the `hi' register. This constraint is no longer
supported.
- 'l'
- The 'lo' register. Use this register to store values that are
+ `l'
+ The `lo' register. Use this register to store values that are
no bigger than a word.
- 'x'
- The concatenated 'hi' and 'lo' registers. Use this register
+ `x'
+ The concatenated `hi' and `lo' registers. Use this register
to store doubleword values.
- 'c'
+ `c'
A register suitable for use in an indirect jump. This will
- always be '$25' for '-mabicalls'.
+ always be `$25' for `-mabicalls'.
- 'v'
- Register '$3'. Do not use this constraint in new code; it is
+ `v'
+ Register `$3'. Do not use this constraint in new code; it is
retained only for compatibility with glibc.
- 'y'
- Equivalent to 'r'; retained for backwards compatibility.
+ `y'
+ Equivalent to `r'; retained for backwards compatibility.
- 'z'
+ `z'
A floating-point condition code register.
- 'I'
+ `I'
A signed 16-bit constant (for arithmetic instructions).
- 'J'
+ `J'
Integer zero.
- 'K'
+ `K'
An unsigned 16-bit constant (for logic instructions).
- 'L'
+ `L'
A signed 32-bit constant in which the lower 16 bits are zero.
- Such constants can be loaded using 'lui'.
+ Such constants can be loaded using `lui'.
- 'M'
- A constant that cannot be loaded using 'lui', 'addiu' or
- 'ori'.
+ `M'
+ A constant that cannot be loaded using `lui', `addiu' or
+ `ori'.
- 'N'
+ `N'
A constant in the range -65535 to -1 (inclusive).
- 'O'
+ `O'
A signed 15-bit constant.
- 'P'
+ `P'
A constant in the range 1 to 65535 (inclusive).
- 'G'
+ `G'
Floating-point zero.
- 'R'
+ `R'
An address that can be used in a non-macro load or store.
- 'ZC'
+ `ZC'
A memory operand whose address is formed by a base register
and offset that is suitable for use in instructions with the
- same addressing mode as 'll' and 'sc'.
+ same addressing mode as `ll' and `sc'.
+
+ `ZD'
+ An address suitable for a `prefetch' instruction, or for any
+ other instruction with the same addressing mode as `prefetch'.
- 'ZD'
- An address suitable for a 'prefetch' instruction, or for any
- other instruction with the same addressing mode as 'prefetch'.
+_Motorola 680x0--`config/m68k/constraints.md'_
-_Motorola 680x0--'config/m68k/constraints.md'_
- 'a'
+ `a'
Address register
- 'd'
+ `d'
Data register
- 'f'
+ `f'
68881 floating-point register, if available
- 'I'
+ `I'
Integer in the range 1 to 8
- 'J'
+ `J'
16-bit signed number
- 'K'
+ `K'
Signed number whose magnitude is greater than 0x80
- 'L'
+ `L'
Integer in the range -8 to -1
- 'M'
+ `M'
Signed number whose magnitude is greater than 0x100
- 'N'
+ `N'
Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate
- 'O'
+ `O'
16 (for rotate using swap)
- 'P'
+ `P'
Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate
- 'R'
+ `R'
Numbers that mov3q can handle
- 'G'
+ `G'
Floating point constant that is not a 68881 constant
- 'S'
+ `S'
Operands that satisfy 'm' when -mpcrel is in effect
- 'T'
+ `T'
Operands that satisfy 's' when -mpcrel is not in effect
- 'Q'
+ `Q'
Address register indirect addressing mode
- 'U'
+ `U'
Register offset addressing
- 'W'
+ `W'
const_call_operand
- 'Cs'
+ `Cs'
symbol_ref or const
- 'Ci'
+ `Ci'
const_int
- 'C0'
+ `C0'
const_int 0
- 'Cj'
+ `Cj'
Range of signed numbers that don't fit in 16 bits
- 'Cmvq'
+ `Cmvq'
Integers valid for mvq
- 'Capsw'
+ `Capsw'
Integers valid for a moveq followed by a swap
- 'Cmvz'
+ `Cmvz'
Integers valid for mvz
- 'Cmvs'
+ `Cmvs'
Integers valid for mvs
- 'Ap'
+ `Ap'
push_operand
- 'Ac'
+ `Ac'
Non-register operands allowed in clr
-_Moxie--'config/moxie/constraints.md'_
- 'A'
+
+_Moxie--`config/moxie/constraints.md'_
+
+ `A'
An absolute address
- 'B'
+ `B'
An offset address
- 'W'
+ `W'
A register indirect memory operand
- 'I'
+ `I'
A constant in the range of 0 to 255.
- 'N'
+ `N'
A constant in the range of 0 to -255.
-_MSP430-'config/msp430/constraints.md'_
- 'R12'
+_MSP430-`config/msp430/constraints.md'_
+
+ `R12'
Register R12.
- 'R13'
+ `R13'
Register R13.
- 'K'
+ `K'
Integer constant 1.
- 'L'
+ `L'
Integer constant -1^20..1^19.
- 'M'
+ `M'
Integer constant 1-4.
- 'Ya'
+ `Ya'
Memory references which do not require an extended MOVX
instruction.
- 'Yl'
+ `Yl'
Memory reference, labels only.
- 'Ys'
+ `Ys'
Memory reference, stack only.
-_NDS32--'config/nds32/constraints.md'_
- 'w'
+
+_NDS32--`config/nds32/constraints.md'_
+
+ `w'
LOW register class $r0 to $r7 constraint for V3/V3M ISA.
- 'l'
+
+ `l'
LOW register class $r0 to $r7.
- 'd'
+
+ `d'
MIDDLE register class $r0 to $r11, $r16 to $r19.
- 'h'
+
+ `h'
HIGH register class $r12 to $r14, $r20 to $r31.
- 't'
+
+ `t'
Temporary assist register $ta (i.e. $r15).
- 'k'
+
+ `k'
Stack register $sp.
- 'Iu03'
+
+ `Iu03'
Unsigned immediate 3-bit value.
- 'In03'
+
+ `In03'
Negative immediate 3-bit value in the range of -7-0.
- 'Iu04'
+
+ `Iu04'
Unsigned immediate 4-bit value.
- 'Is05'
+
+ `Is05'
Signed immediate 5-bit value.
- 'Iu05'
+
+ `Iu05'
Unsigned immediate 5-bit value.
- 'In05'
+
+ `In05'
Negative immediate 5-bit value in the range of -31-0.
- 'Ip05'
+
+ `Ip05'
Unsigned immediate 5-bit value for movpi45 instruction with
range 16-47.
- 'Iu06'
+
+ `Iu06'
Unsigned immediate 6-bit value constraint for addri36.sp
instruction.
- 'Iu08'
+
+ `Iu08'
Unsigned immediate 8-bit value.
- 'Iu09'
+
+ `Iu09'
Unsigned immediate 9-bit value.
- 'Is10'
+
+ `Is10'
Signed immediate 10-bit value.
- 'Is11'
+
+ `Is11'
Signed immediate 11-bit value.
- 'Is15'
+
+ `Is15'
Signed immediate 15-bit value.
- 'Iu15'
+
+ `Iu15'
Unsigned immediate 15-bit value.
- 'Ic15'
- A constant which is not in the range of imm15u but ok for bclr
- instruction.
- 'Ie15'
- A constant which is not in the range of imm15u but ok for bset
- instruction.
- 'It15'
- A constant which is not in the range of imm15u but ok for btgl
- instruction.
- 'Ii15'
+
+ `Ic15'
+ A constant which is not in the range of imm15u but ok for
+ bclr instruction.
+
+ `Ie15'
+ A constant which is not in the range of imm15u but ok for
+ bset instruction.
+
+ `It15'
+ A constant which is not in the range of imm15u but ok for
+ btgl instruction.
+
+ `Ii15'
A constant whose compliment value is in the range of imm15u
and ok for bitci instruction.
- 'Is16'
+
+ `Is16'
Signed immediate 16-bit value.
- 'Is17'
+
+ `Is17'
Signed immediate 17-bit value.
- 'Is19'
+
+ `Is19'
Signed immediate 19-bit value.
- 'Is20'
+
+ `Is20'
Signed immediate 20-bit value.
- 'Ihig'
+
+ `Ihig'
The immediate value that can be simply set high 20-bit.
- 'Izeb'
+
+ `Izeb'
The immediate value 0xff.
- 'Izeh'
+
+ `Izeh'
The immediate value 0xffff.
- 'Ixls'
+
+ `Ixls'
The immediate value 0x01.
- 'Ix11'
+
+ `Ix11'
The immediate value 0x7ff.
- 'Ibms'
+
+ `Ibms'
The immediate value with power of 2.
- 'Ifex'
+
+ `Ifex'
The immediate value with power of 2 minus 1.
- 'U33'
+
+ `U33'
Memory constraint for 333 format.
- 'U45'
+
+ `U45'
Memory constraint for 45 format.
- 'U37'
+
+ `U37'
Memory constraint for 37 format.
-_Nios II family--'config/nios2/constraints.md'_
+_Nios II family--`config/nios2/constraints.md'_
- 'I'
+ `I'
Integer that is valid as an immediate operand in an
- instruction taking a signed 16-bit number. Range -32768 to
+ instruction taking a signed 16-bit number. Range -32768 to
32767.
- 'J'
+ `J'
Integer that is valid as an immediate operand in an
- instruction taking an unsigned 16-bit number. Range 0 to
+ instruction taking an unsigned 16-bit number. Range 0 to
65535.
- 'K'
+ `K'
Integer that is valid as an immediate operand in an
instruction taking only the upper 16-bits of a 32-bit number.
Range 32-bit numbers with the lower 16-bits being 0.
- 'L'
+ `L'
Integer that is valid as an immediate operand for a shift
- instruction. Range 0 to 31.
+ instruction. Range 0 to 31.
- 'M'
+ `M'
Integer that is valid as an immediate operand for only the
- value 0. Can be used in conjunction with the format modifier
- 'z' to use 'r0' instead of '0' in the assembly output.
+ value 0. Can be used in conjunction with the format modifier
+ `z' to use `r0' instead of `0' in the assembly output.
- 'N'
+ `N'
Integer that is valid as an immediate operand for a custom
- instruction opcode. Range 0 to 255.
+ instruction opcode. Range 0 to 255.
- 'S'
+ `S'
Matches immediates which are addresses in the small data
- section and therefore can be added to 'gp' as a 16-bit
+ section and therefore can be added to `gp' as a 16-bit
immediate to re-create their 32-bit value.
- 'T'
- A 'const' wrapped 'UNSPEC' expression, representing a
+ `T'
+ A `const' wrapped `UNSPEC' expression, representing a
supported PIC or TLS relocation.
-_PDP-11--'config/pdp11/constraints.md'_
- 'a'
- Floating point registers AC0 through AC3. These can be loaded
- from/to memory with a single instruction.
- 'd'
+_PDP-11--`config/pdp11/constraints.md'_
+
+ `a'
+ Floating point registers AC0 through AC3. These can be
+ loaded from/to memory with a single instruction.
+
+ `d'
Odd numbered general registers (R1, R3, R5). These are used
for 16-bit multiply operations.
- 'f'
+ `f'
Any of the floating point registers (AC0 through AC5).
- 'G'
+ `G'
Floating point constant 0.
- 'I'
+ `I'
An integer constant that fits in 16 bits.
- 'J'
+ `J'
An integer constant whose low order 16 bits are zero.
- 'K'
+ `K'
An integer constant that does not meet the constraints for
- codes 'I' or 'J'.
+ codes `I' or `J'.
- 'L'
+ `L'
The integer constant 1.
- 'M'
+ `M'
The integer constant -1.
- 'N'
+ `N'
The integer constant 0.
- 'O'
+ `O'
Integer constants -4 through -1 and 1 through 4; shifts by
- these amounts are handled as multiple single-bit shifts rather
- than a single variable-length shift.
+ these amounts are handled as multiple single-bit shifts
+ rather than a single variable-length shift.
- 'Q'
+ `Q'
A memory reference which requires an additional word (address
or offset) after the opcode.
- 'R'
+ `R'
A memory reference that is encoded within the opcode.
-_PowerPC and IBM RS6000--'config/rs6000/constraints.md'_
- 'b'
+
+_PowerPC and IBM RS6000--`config/rs6000/constraints.md'_
+
+ `b'
Address base register
- 'd'
+ `d'
Floating point register (containing 64-bit value)
- 'f'
+ `f'
Floating point register (containing 32-bit value)
- 'v'
+ `v'
Altivec vector register
- 'wa'
+ `wa'
Any VSX register if the -mvsx option was used or NO_REGS.
- 'wd'
+ When using any of the register constraints (`wa', `wd', `wf',
+ `wg', `wh', `wi', `wj', `wk', `wl', `wm', `ws', `wt', `wu',
+ `wv', `ww', or `wy') that take VSX registers, you must use
+ `%x<n>' in the template so that the correct register is used.
+ Otherwise the register number output in the assembly file
+ will be incorrect if an Altivec register is an operand of a
+ VSX instruction that expects VSX register numbering.
+
+ asm ("xvadddp %x0,%x1,%x2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+
+ is correct, but:
+
+ asm ("xvadddp %0,%1,%2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+
+ is not correct.
+
+ `wd'
VSX vector register to hold vector double data or NO_REGS.
- 'wf'
+ `wf'
VSX vector register to hold vector float data or NO_REGS.
- 'wg'
- If '-mmfpgpr' was used, a floating point register or NO_REGS.
+ `wg'
+ If `-mmfpgpr' was used, a floating point register or NO_REGS.
- 'wh'
+ `wh'
Floating point register if direct moves are available, or
NO_REGS.
- 'wi'
+ `wi'
FP or VSX register to hold 64-bit integers for VSX insns or
NO_REGS.
- 'wj'
- FP or VSX register to hold 64-bit integers for direct moves or
- NO_REGS.
+ `wj'
+ FP or VSX register to hold 64-bit integers for direct moves
+ or NO_REGS.
- 'wk'
+ `wk'
FP or VSX register to hold 64-bit doubles for direct moves or
NO_REGS.
- 'wl'
+ `wl'
Floating point register if the LFIWAX instruction is enabled
or NO_REGS.
- 'wm'
+ `wm'
VSX register if direct move instructions are enabled, or
NO_REGS.
- 'wn'
+ `wn'
No register (NO_REGS).
- 'wr'
- General purpose register if 64-bit instructions are enabled or
- NO_REGS.
+ `wr'
+ General purpose register if 64-bit instructions are enabled
+ or NO_REGS.
- 'ws'
+ `ws'
VSX vector register to hold scalar double values or NO_REGS.
- 'wt'
+ `wt'
VSX vector register to hold 128 bit integer or NO_REGS.
- 'wu'
- Altivec register to use for float/32-bit int loads/stores or
+ `wu'
+ Altivec register to use for float/32-bit int loads/stores or
NO_REGS.
- 'wv'
- Altivec register to use for double loads/stores or NO_REGS.
+ `wv'
+ Altivec register to use for double loads/stores or NO_REGS.
- 'ww'
- FP or VSX register to perform float operations under '-mvsx'
+ `ww'
+ FP or VSX register to perform float operations under `-mvsx'
or NO_REGS.
- 'wx'
+ `wx'
Floating point register if the STFIWX instruction is enabled
or NO_REGS.
- 'wy'
+ `wy'
FP or VSX register to perform ISA 2.07 float ops or NO_REGS.
- 'wz'
+ `wz'
Floating point register if the LFIWZX instruction is enabled
or NO_REGS.
- 'wD'
+ `wD'
Int constant that is the element number of the 64-bit scalar
in a vector.
- 'wQ'
- A memory address that will work with the 'lq' and 'stq'
+ `wQ'
+ A memory address that will work with the `lq' and `stq'
instructions.
- 'h'
- 'MQ', 'CTR', or 'LINK' register
+ `h'
+ `MQ', `CTR', or `LINK' register
- 'q'
- 'MQ' register
+ `q'
+ `MQ' register
- 'c'
- 'CTR' register
+ `c'
+ `CTR' register
- 'l'
- 'LINK' register
+ `l'
+ `LINK' register
- 'x'
- 'CR' register (condition register) number 0
+ `x'
+ `CR' register (condition register) number 0
- 'y'
- 'CR' register (condition register)
+ `y'
+ `CR' register (condition register)
- 'z'
- 'XER[CA]' carry bit (part of the XER register)
+ `z'
+ `XER[CA]' carry bit (part of the XER register)
- 'I'
+ `I'
Signed 16-bit constant
- 'J'
- Unsigned 16-bit constant shifted left 16 bits (use 'L' instead
- for 'SImode' constants)
+ `J'
+ Unsigned 16-bit constant shifted left 16 bits (use `L'
+ instead for `SImode' constants)
- 'K'
+ `K'
Unsigned 16-bit constant
- 'L'
+ `L'
Signed 16-bit constant shifted left 16 bits
- 'M'
+ `M'
Constant larger than 31
- 'N'
+ `N'
Exact power of 2
- 'O'
+ `O'
Zero
- 'P'
+ `P'
Constant whose negation is a signed 16-bit constant
- 'G'
+ `G'
Floating point constant that can be loaded into a register
with one instruction per word
- 'H'
+ `H'
Integer/Floating point constant that can be loaded into a
register using three instructions
- 'm'
- Memory operand. Normally, 'm' does not allow addresses that
- update the base register. If '<' or '>' constraint is also
+ `m'
+ Memory operand. Normally, `m' does not allow addresses that
+ update the base register. If `<' or `>' constraint is also
used, they are allowed and therefore on PowerPC targets in
- that case it is only safe to use 'm<>' in an 'asm' statement
- if that 'asm' statement accesses the operand exactly once.
- The 'asm' statement must also use '%U<OPNO>' as a placeholder
+ that case it is only safe to use `m<>' in an `asm' statement
+ if that `asm' statement accesses the operand exactly once.
+ The `asm' statement must also use `%U<OPNO>' as a placeholder
for the "update" flag in the corresponding load or store
instruction. For example:
@@ -21336,725 +21635,789 @@ _PowerPC and IBM RS6000--'config/rs6000/constraints.md'_
is not.
- 'es'
- A "stable" memory operand; that is, one which does not include
- any automodification of the base register. This used to be
- useful when 'm' allowed automodification of the base register,
- but as those are now only allowed when '<' or '>' is used,
- 'es' is basically the same as 'm' without '<' and '>'.
+ `es'
+ A "stable" memory operand; that is, one which does not
+ include any automodification of the base register. This used
+ to be useful when `m' allowed automodification of the base
+ register, but as those are now only allowed when `<' or `>'
+ is used, `es' is basically the same as `m' without `<' and
+ `>'.
- 'Q'
+ `Q'
Memory operand that is an offset from a register (it is
- usually better to use 'm' or 'es' in 'asm' statements)
+ usually better to use `m' or `es' in `asm' statements)
- 'Z'
+ `Z'
Memory operand that is an indexed or indirect from a register
- (it is usually better to use 'm' or 'es' in 'asm' statements)
+ (it is usually better to use `m' or `es' in `asm' statements)
- 'R'
+ `R'
AIX TOC entry
- 'a'
- Address operand that is an indexed or indirect from a register
- ('p' is preferable for 'asm' statements)
+ `a'
+ Address operand that is an indexed or indirect from a
+ register (`p' is preferable for `asm' statements)
- 'S'
+ `S'
Constant suitable as a 64-bit mask operand
- 'T'
+ `T'
Constant suitable as a 32-bit mask operand
- 'U'
+ `U'
System V Release 4 small data area reference
- 't'
+ `t'
AND masks that can be performed by two rldic{l, r}
instructions
- 'W'
+ `W'
Vector constant that does not require memory
- 'j'
+ `j'
Vector constant that is all zeros.
-_RL78--'config/rl78/constraints.md'_
- 'Int3'
+_RL78--`config/rl78/constraints.md'_
+
+ `Int3'
An integer constant in the range 1 ... 7.
- 'Int8'
+
+ `Int8'
An integer constant in the range 0 ... 255.
- 'J'
+
+ `J'
An integer constant in the range -255 ... 0
- 'K'
+
+ `K'
The integer constant 1.
- 'L'
+
+ `L'
The integer constant -1.
- 'M'
+
+ `M'
The integer constant 0.
- 'N'
+
+ `N'
The integer constant 2.
- 'O'
+
+ `O'
The integer constant -2.
- 'P'
+
+ `P'
An integer constant in the range 1 ... 15.
- 'Qbi'
+
+ `Qbi'
The built-in compare types-eq, ne, gtu, ltu, geu, and leu.
- 'Qsc'
+
+ `Qsc'
The synthetic compare types-gt, lt, ge, and le.
- 'Wab'
+
+ `Wab'
A memory reference with an absolute address.
- 'Wbc'
- A memory reference using 'BC' as a base register, with an
+
+ `Wbc'
+ A memory reference using `BC' as a base register, with an
optional offset.
- 'Wca'
- A memory reference using 'AX', 'BC', 'DE', or 'HL' for the
+
+ `Wca'
+ A memory reference using `AX', `BC', `DE', or `HL' for the
address, for calls.
- 'Wcv'
+
+ `Wcv'
A memory reference using any 16-bit register pair for the
address, for calls.
- 'Wd2'
- A memory reference using 'DE' as a base register, with an
+
+ `Wd2'
+ A memory reference using `DE' as a base register, with an
optional offset.
- 'Wde'
- A memory reference using 'DE' as a base register, without any
+
+ `Wde'
+ A memory reference using `DE' as a base register, without any
offset.
- 'Wfr'
+
+ `Wfr'
Any memory reference to an address in the far address space.
- 'Wh1'
- A memory reference using 'HL' as a base register, with an
+
+ `Wh1'
+ A memory reference using `HL' as a base register, with an
optional one-byte offset.
- 'Whb'
- A memory reference using 'HL' as a base register, with 'B' or
- 'C' as the index register.
- 'Whl'
- A memory reference using 'HL' as a base register, without any
+
+ `Whb'
+ A memory reference using `HL' as a base register, with `B' or
+ `C' as the index register.
+
+ `Whl'
+ A memory reference using `HL' as a base register, without any
offset.
- 'Ws1'
- A memory reference using 'SP' as a base register, with an
+
+ `Ws1'
+ A memory reference using `SP' as a base register, with an
optional one-byte offset.
- 'Y'
+
+ `Y'
Any memory reference to an address in the near address space.
- 'A'
- The 'AX' register.
- 'B'
- The 'BC' register.
- 'D'
- The 'DE' register.
- 'R'
- 'A' through 'L' registers.
- 'S'
- The 'SP' register.
- 'T'
- The 'HL' register.
- 'Z08W'
- The 16-bit 'R8' register.
- 'Z10W'
- The 16-bit 'R10' register.
- 'Zint'
- The registers reserved for interrupts ('R24' to 'R31').
- 'a'
- The 'A' register.
- 'b'
- The 'B' register.
- 'c'
- The 'C' register.
- 'd'
- The 'D' register.
- 'e'
- The 'E' register.
- 'h'
- The 'H' register.
- 'l'
- The 'L' register.
- 'v'
+
+ `A'
+ The `AX' register.
+
+ `B'
+ The `BC' register.
+
+ `D'
+ The `DE' register.
+
+ `R'
+ `A' through `L' registers.
+
+ `S'
+ The `SP' register.
+
+ `T'
+ The `HL' register.
+
+ `Z08W'
+ The 16-bit `R8' register.
+
+ `Z10W'
+ The 16-bit `R10' register.
+
+ `Zint'
+ The registers reserved for interrupts (`R24' to `R31').
+
+ `a'
+ The `A' register.
+
+ `b'
+ The `B' register.
+
+ `c'
+ The `C' register.
+
+ `d'
+ The `D' register.
+
+ `e'
+ The `E' register.
+
+ `h'
+ The `H' register.
+
+ `l'
+ The `L' register.
+
+ `v'
The virtual registers.
- 'w'
- The 'PSW' register.
- 'x'
- The 'X' register.
-_RX--'config/rx/constraints.md'_
- 'Q'
- An address which does not involve register indirect addressing
- or pre/post increment/decrement addressing.
+ `w'
+ The `PSW' register.
+
+ `x'
+ The `X' register.
+
- 'Symbol'
+_RX--`config/rx/constraints.md'_
+
+ `Q'
+ An address which does not involve register indirect
+ addressing or pre/post increment/decrement addressing.
+
+ `Symbol'
A symbol reference.
- 'Int08'
+ `Int08'
A constant in the range -256 to 255, inclusive.
- 'Sint08'
+ `Sint08'
A constant in the range -128 to 127, inclusive.
- 'Sint16'
+ `Sint16'
A constant in the range -32768 to 32767, inclusive.
- 'Sint24'
+ `Sint24'
A constant in the range -8388608 to 8388607, inclusive.
- 'Uint04'
+ `Uint04'
A constant in the range 0 to 15, inclusive.
-_S/390 and zSeries--'config/s390/s390.h'_
- 'a'
+
+_S/390 and zSeries--`config/s390/s390.h'_
+
+ `a'
Address register (general purpose register except r0)
- 'c'
+ `c'
Condition code register
- 'd'
+ `d'
Data register (arbitrary general purpose register)
- 'f'
+ `f'
Floating-point register
- 'I'
+ `I'
Unsigned 8-bit constant (0-255)
- 'J'
+ `J'
Unsigned 12-bit constant (0-4095)
- 'K'
+ `K'
Signed 16-bit constant (-32768-32767)
- 'L'
+ `L'
Value appropriate as displacement.
- '(0..4095)'
+ `(0..4095)'
for short displacement
- '(-524288..524287)'
+
+ `(-524288..524287)'
for long displacement
- 'M'
+ `M'
Constant integer with a value of 0x7fffffff.
- 'N'
+ `N'
Multiple letter constraint followed by 4 parameter letters.
- '0..9:'
+ `0..9:'
number of the part counting from most to least
significant
- 'H,Q:'
+
+ `H,Q:'
mode of the part
- 'D,S,H:'
+
+ `D,S,H:'
mode of the containing operand
- '0,F:'
+
+ `0,F:'
value of the other parts (F--all bits set)
- The constraint matches if the specified part of a constant has
- a value different from its other parts.
+ The constraint matches if the specified part of a constant
+ has a value different from its other parts.
- 'Q'
+ `Q'
Memory reference without index register and with short
displacement.
- 'R'
+ `R'
Memory reference with index register and short displacement.
- 'S'
+ `S'
Memory reference without index register but with long
displacement.
- 'T'
+ `T'
Memory reference with index register and long displacement.
- 'U'
+ `U'
Pointer with short displacement.
- 'W'
+ `W'
Pointer with long displacement.
- 'Y'
+ `Y'
Shift count operand.
-_SPARC--'config/sparc/sparc.h'_
- 'f'
- Floating-point register on the SPARC-V8 architecture and lower
- floating-point register on the SPARC-V9 architecture.
- 'e'
- Floating-point register. It is equivalent to 'f' on the
+_SPARC--`config/sparc/sparc.h'_
+
+ `f'
+ Floating-point register on the SPARC-V8 architecture and
+ lower floating-point register on the SPARC-V9 architecture.
+
+ `e'
+ Floating-point register. It is equivalent to `f' on the
SPARC-V8 architecture and contains both lower and upper
floating-point registers on the SPARC-V9 architecture.
- 'c'
+ `c'
Floating-point condition code register.
- 'd'
+ `d'
Lower floating-point register. It is only valid on the
SPARC-V9 architecture when the Visual Instruction Set is
available.
- 'b'
+ `b'
Floating-point register. It is only valid on the SPARC-V9
architecture when the Visual Instruction Set is available.
- 'h'
+ `h'
64-bit global or out register for the SPARC-V8+ architecture.
- 'C'
+ `C'
The constant all-ones, for floating-point.
- 'A'
+ `A'
Signed 5-bit constant
- 'D'
+ `D'
A vector constant
- 'I'
+ `I'
Signed 13-bit constant
- 'J'
+ `J'
Zero
- 'K'
+ `K'
32-bit constant with the low 12 bits clear (a constant that
- can be loaded with the 'sethi' instruction)
+ can be loaded with the `sethi' instruction)
- 'L'
- A constant in the range supported by 'movcc' instructions
+ `L'
+ A constant in the range supported by `movcc' instructions
(11-bit signed immediate)
- 'M'
- A constant in the range supported by 'movrcc' instructions
+ `M'
+ A constant in the range supported by `movrcc' instructions
(10-bit signed immediate)
- 'N'
- Same as 'K', except that it verifies that bits that are not in
- the lower 32-bit range are all zero. Must be used instead of
- 'K' for modes wider than 'SImode'
+ `N'
+ Same as `K', except that it verifies that bits that are not
+ in the lower 32-bit range are all zero. Must be used instead
+ of `K' for modes wider than `SImode'
- 'O'
+ `O'
The constant 4096
- 'G'
+ `G'
Floating-point zero
- 'H'
+ `H'
Signed 13-bit constant, sign-extended to 32 or 64 bits
- 'P'
+ `P'
The constant -1
- 'Q'
+ `Q'
Floating-point constant whose integral representation can be
moved into an integer register using a single sethi
instruction
- 'R'
+ `R'
Floating-point constant whose integral representation can be
moved into an integer register using a single mov instruction
- 'S'
+ `S'
Floating-point constant whose integral representation can be
- moved into an integer register using a high/lo_sum instruction
- sequence
+ moved into an integer register using a high/lo_sum
+ instruction sequence
- 'T'
+ `T'
Memory address aligned to an 8-byte boundary
- 'U'
+ `U'
Even register
- 'W'
- Memory address for 'e' constraint registers
+ `W'
+ Memory address for `e' constraint registers
- 'w'
+ `w'
Memory address with only a base register
- 'Y'
+ `Y'
Vector zero
-_SPU--'config/spu/spu.h'_
- 'a'
+
+_SPU--`config/spu/spu.h'_
+
+ `a'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is treated as a 64 bit value.
- 'c'
+ `c'
An immediate for and/xor/or instructions. const_int is
treated as a 64 bit value.
- 'd'
- An immediate for the 'iohl' instruction. const_int is treated
- as a 64 bit value.
+ `d'
+ An immediate for the `iohl' instruction. const_int is
+ treated as a 64 bit value.
- 'f'
- An immediate which can be loaded with 'fsmbi'.
+ `f'
+ An immediate which can be loaded with `fsmbi'.
- 'A'
+ `A'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is treated as a 32 bit value.
- 'B'
+ `B'
An immediate for most arithmetic instructions. const_int is
treated as a 32 bit value.
- 'C'
+ `C'
An immediate for and/xor/or instructions. const_int is
treated as a 32 bit value.
- 'D'
- An immediate for the 'iohl' instruction. const_int is treated
- as a 32 bit value.
+ `D'
+ An immediate for the `iohl' instruction. const_int is
+ treated as a 32 bit value.
- 'I'
+ `I'
A constant in the range [-64, 63] for shift/rotate
instructions.
- 'J'
+ `J'
An unsigned 7-bit constant for conversion/nop/channel
instructions.
- 'K'
+ `K'
A signed 10-bit constant for most arithmetic instructions.
- 'M'
- A signed 16 bit immediate for 'stop'.
+ `M'
+ A signed 16 bit immediate for `stop'.
- 'N'
- An unsigned 16-bit constant for 'iohl' and 'fsmbi'.
+ `N'
+ An unsigned 16-bit constant for `iohl' and `fsmbi'.
- 'O'
+ `O'
An unsigned 7-bit constant whose 3 least significant bits are
0.
- 'P'
+ `P'
An unsigned 3-bit constant for 16-byte rotates and shifts
- 'R'
+ `R'
Call operand, reg, for indirect calls
- 'S'
+ `S'
Call operand, symbol, for relative calls.
- 'T'
+ `T'
Call operand, const_int, for absolute calls.
- 'U'
+ `U'
An immediate which can be loaded with the il/ila/ilh/ilhu
instructions. const_int is sign extended to 128 bit.
- 'W'
+ `W'
An immediate for shift and rotate instructions. const_int is
treated as a 32 bit value.
- 'Y'
+ `Y'
An immediate for and/xor/or instructions. const_int is sign
extended as a 128 bit.
- 'Z'
- An immediate for the 'iohl' instruction. const_int is sign
+ `Z'
+ An immediate for the `iohl' instruction. const_int is sign
extended to 128 bit.
-_TI C6X family--'config/c6x/constraints.md'_
- 'a'
+
+_TI C6X family--`config/c6x/constraints.md'_
+
+ `a'
Register file A (A0-A31).
- 'b'
+ `b'
Register file B (B0-B31).
- 'A'
+ `A'
Predicate registers in register file A (A0-A2 on C64X and
higher, A1 and A2 otherwise).
- 'B'
+ `B'
Predicate registers in register file B (B0-B2).
- 'C'
+ `C'
A call-used register in register file B (B0-B9, B16-B31).
- 'Da'
+ `Da'
Register file A, excluding predicate registers (A3-A31, plus
A0 if not C64X or higher).
- 'Db'
+ `Db'
Register file B, excluding predicate registers (B3-B31).
- 'Iu4'
+ `Iu4'
Integer constant in the range 0 ... 15.
- 'Iu5'
+ `Iu5'
Integer constant in the range 0 ... 31.
- 'In5'
+ `In5'
Integer constant in the range -31 ... 0.
- 'Is5'
+ `Is5'
Integer constant in the range -16 ... 15.
- 'I5x'
+ `I5x'
Integer constant that can be the operand of an ADDA or a SUBA
insn.
- 'IuB'
+ `IuB'
Integer constant in the range 0 ... 65535.
- 'IsB'
+ `IsB'
Integer constant in the range -32768 ... 32767.
- 'IsC'
- Integer constant in the range -2^{20} ... 2^{20} - 1.
+ `IsC'
+ Integer constant in the range -2^20 ... 2^20 - 1.
- 'Jc'
+ `Jc'
Integer constant that is a valid mask for the clr instruction.
- 'Js'
+ `Js'
Integer constant that is a valid mask for the set instruction.
- 'Q'
+ `Q'
Memory location with A base register.
- 'R'
+ `R'
Memory location with B base register.
- 'S0'
+ `S0'
On C64x+ targets, a GP-relative small data reference.
- 'S1'
- Any kind of 'SYMBOL_REF', for use in a call address.
+ `S1'
+ Any kind of `SYMBOL_REF', for use in a call address.
- 'Si'
+ `Si'
Any kind of immediate operand, unless it matches the S0
constraint.
- 'T'
+ `T'
Memory location with B base register, but not using a long
offset.
- 'W'
+ `W'
A memory operand with an address that can't be used in an
unaligned access.
- 'Z'
+ `Z'
Register B14 (aka DP).
-_TILE-Gx--'config/tilegx/constraints.md'_
- 'R00'
- 'R01'
- 'R02'
- 'R03'
- 'R04'
- 'R05'
- 'R06'
- 'R07'
- 'R08'
- 'R09'
- 'R10'
+
+_TILE-Gx--`config/tilegx/constraints.md'_
+
+ `R00'
+ `R01'
+ `R02'
+ `R03'
+ `R04'
+ `R05'
+ `R06'
+ `R07'
+ `R08'
+ `R09'
+ `R10'
Each of these represents a register constraint for an
individual register, from r0 to r10.
- 'I'
+ `I'
Signed 8-bit integer constant.
- 'J'
+ `J'
Signed 16-bit integer constant.
- 'K'
+ `K'
Unsigned 16-bit integer constant.
- 'L'
- Integer constant that fits in one signed byte when incremented
- by one (-129 ... 126).
+ `L'
+ Integer constant that fits in one signed byte when
+ incremented by one (-129 ... 126).
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement which requires printing with '%In' and
- '%in' on TILE-Gx. For example:
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement which requires printing with
+ `%In' and `%in' on TILE-Gx. For example:
asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val));
- 'M'
+ `M'
A bit mask suitable for the BFINS instruction.
- 'N'
+ `N'
Integer constant that is a byte tiled out eight times.
- 'O'
+ `O'
The integer zero constant.
- 'P'
+ `P'
Integer constant that is a sign-extended byte tiled out as
four shorts.
- 'Q'
+ `Q'
Integer constant that fits in one signed byte when incremented
(-129 ... 126), but excluding -1.
- 'S'
+ `S'
Integer constant that has all 1 bits consecutive and starting
at bit 0.
- 'T'
+ `T'
A 16-bit fragment of a got, tls, or pc-relative reference.
- 'U'
- Memory operand except postincrement. This is roughly the same
- as 'm' when not used together with '<' or '>'.
+ `U'
+ Memory operand except postincrement. This is roughly the
+ same as `m' when not used together with `<' or `>'.
- 'W'
+ `W'
An 8-element vector constant with identical elements.
- 'Y'
+ `Y'
A 4-element vector constant with identical elements.
- 'Z0'
+ `Z0'
The integer constant 0xffffffff.
- 'Z1'
+ `Z1'
The integer constant 0xffffffff00000000.
-_TILEPro--'config/tilepro/constraints.md'_
- 'R00'
- 'R01'
- 'R02'
- 'R03'
- 'R04'
- 'R05'
- 'R06'
- 'R07'
- 'R08'
- 'R09'
- 'R10'
+
+_TILEPro--`config/tilepro/constraints.md'_
+
+ `R00'
+ `R01'
+ `R02'
+ `R03'
+ `R04'
+ `R05'
+ `R06'
+ `R07'
+ `R08'
+ `R09'
+ `R10'
Each of these represents a register constraint for an
individual register, from r0 to r10.
- 'I'
+ `I'
Signed 8-bit integer constant.
- 'J'
+ `J'
Signed 16-bit integer constant.
- 'K'
+ `K'
Nonzero integer constant with low 16 bits zero.
- 'L'
- Integer constant that fits in one signed byte when incremented
- by one (-129 ... 126).
+ `L'
+ Integer constant that fits in one signed byte when
+ incremented by one (-129 ... 126).
- 'm'
- Memory operand. If used together with '<' or '>', the operand
- can have postincrement which requires printing with '%In' and
- '%in' on TILEPro. For example:
+ `m'
+ Memory operand. If used together with `<' or `>', the
+ operand can have postincrement which requires printing with
+ `%In' and `%in' on TILEPro. For example:
asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val));
- 'M'
+ `M'
A bit mask suitable for the MM instruction.
- 'N'
+ `N'
Integer constant that is a byte tiled out four times.
- 'O'
+ `O'
The integer zero constant.
- 'P'
- Integer constant that is a sign-extended byte tiled out as two
- shorts.
+ `P'
+ Integer constant that is a sign-extended byte tiled out as
+ two shorts.
- 'Q'
+ `Q'
Integer constant that fits in one signed byte when incremented
(-129 ... 126), but excluding -1.
- 'T'
+ `T'
A symbolic operand, or a 16-bit fragment of a got, tls, or
pc-relative reference.
- 'U'
- Memory operand except postincrement. This is roughly the same
- as 'm' when not used together with '<' or '>'.
+ `U'
+ Memory operand except postincrement. This is roughly the
+ same as `m' when not used together with `<' or `>'.
- 'W'
+ `W'
A 4-element vector constant with identical elements.
- 'Y'
+ `Y'
A 2-element vector constant with identical elements.
-_Visium--'config/visium/constraints.md'_
- 'b'
- EAM register 'mdb'
- 'c'
- EAM register 'mdc'
+_Visium--`config/visium/constraints.md'_
+
+ `b'
+ EAM register `mdb'
- 'f'
+ `c'
+ EAM register `mdc'
+
+ `f'
Floating point register
- 'k'
+ `k'
Register for sibcall optimization
- 'l'
- General register, but not 'r29', 'r30' and 'r31'
+ `l'
+ General register, but not `r29', `r30' and `r31'
- 't'
- Register 'r1'
+ `t'
+ Register `r1'
- 'u'
- Register 'r2'
+ `u'
+ Register `r2'
- 'v'
- Register 'r3'
+ `v'
+ Register `r3'
- 'G'
+ `G'
Floating-point constant 0.0
- 'J'
- Integer constant in the range 0 .. 65535 (16-bit immediate)
+ `J'
+ Integer constant in the range 0 .. 65535 (16-bit immediate)
- 'K'
- Integer constant in the range 1 .. 31 (5-bit immediate)
+ `K'
+ Integer constant in the range 1 .. 31 (5-bit immediate)
- 'L'
- Integer constant in the range -65535 .. -1 (16-bit negative
+ `L'
+ Integer constant in the range -65535 .. -1 (16-bit negative
immediate)
- 'M'
+ `M'
Integer constant -1
- 'O'
+ `O'
Integer constant 0
- 'P'
+ `P'
Integer constant 32
-_x86 family--'config/i386/constraints.md'_
- 'R'
+_x86 family--`config/i386/constraints.md'_
+
+ `R'
Legacy register--the eight integer registers available on all
- i386 processors ('a', 'b', 'c', 'd', 'si', 'di', 'bp', 'sp').
+ i386 processors (`a', `b', `c', `d', `si', `di', `bp', `sp').
- 'q'
- Any register accessible as 'Rl'. In 32-bit mode, 'a', 'b',
- 'c', and 'd'; in 64-bit mode, any integer register.
+ `q'
+ Any register accessible as `Rl'. In 32-bit mode, `a', `b',
+ `c', and `d'; in 64-bit mode, any integer register.
- 'Q'
- Any register accessible as 'Rh': 'a', 'b', 'c', and 'd'.
+ `Q'
+ Any register accessible as `Rh': `a', `b', `c', and `d'.
- 'l'
+ `l'
Any register that can be used as the index in a base+index
memory access: that is, any general register except the stack
pointer.
- 'a'
- The 'a' register.
+ `a'
+ The `a' register.
- 'b'
- The 'b' register.
+ `b'
+ The `b' register.
- 'c'
- The 'c' register.
+ `c'
+ The `c' register.
- 'd'
- The 'd' register.
+ `d'
+ The `d' register.
- 'S'
- The 'si' register.
+ `S'
+ The `si' register.
- 'D'
- The 'di' register.
+ `D'
+ The `di' register.
- 'A'
- The 'a' and 'd' registers. This class is used for
- instructions that return double word results in the 'ax:dx'
- register pair. Single word values will be allocated either in
- 'ax' or 'dx'. For example on i386 the following implements
- 'rdtsc':
+ `A'
+ The `a' and `d' registers. This class is used for
+ instructions that return double word results in the `ax:dx'
+ register pair. Single word values will be allocated either
+ in `ax' or `dx'. For example on i386 the following
+ implements `rdtsc':
unsigned long long rdtsc (void)
{
@@ -22064,7 +22427,7 @@ _x86 family--'config/i386/constraints.md'_
}
This is not correct on x86-64 as it would allocate tick in
- either 'ax' or 'dx'. You have to use the following variant
+ either `ax' or `dx'. You have to use the following variant
instead:
unsigned long long rdtsc (void)
@@ -22074,212 +22437,218 @@ _x86 family--'config/i386/constraints.md'_
return ((unsigned long long)tickh << 32)|tickl;
}
- 'f'
+ `f'
Any 80387 floating-point (stack) register.
- 't'
- Top of 80387 floating-point stack ('%st(0)').
+ `t'
+ Top of 80387 floating-point stack (`%st(0)').
- 'u'
- Second from top of 80387 floating-point stack ('%st(1)').
+ `u'
+ Second from top of 80387 floating-point stack (`%st(1)').
- 'y'
+ `y'
Any MMX register.
- 'x'
+ `x'
Any SSE register.
- 'Yz'
- First SSE register ('%xmm0').
+ `Yz'
+ First SSE register (`%xmm0').
- 'Y2'
+ `Y2'
Any SSE register, when SSE2 is enabled.
- 'Yi'
+ `Yi'
Any SSE register, when SSE2 and inter-unit moves are enabled.
- 'Ym'
+ `Ym'
Any MMX register, when inter-unit moves are enabled.
- 'I'
+ `I'
Integer constant in the range 0 ... 31, for 32-bit shifts.
- 'J'
+ `J'
Integer constant in the range 0 ... 63, for 64-bit shifts.
- 'K'
+ `K'
Signed 8-bit integer constant.
- 'L'
- '0xFF' or '0xFFFF', for andsi as a zero-extending move.
+ `L'
+ `0xFF' or `0xFFFF', for andsi as a zero-extending move.
- 'M'
- 0, 1, 2, or 3 (shifts for the 'lea' instruction).
+ `M'
+ 0, 1, 2, or 3 (shifts for the `lea' instruction).
- 'N'
- Unsigned 8-bit integer constant (for 'in' and 'out'
+ `N'
+ Unsigned 8-bit integer constant (for `in' and `out'
instructions).
- 'O'
+ `O'
Integer constant in the range 0 ... 127, for 128-bit shifts.
- 'G'
+ `G'
Standard 80387 floating point constant.
- 'C'
+ `C'
Standard SSE floating point constant.
- 'e'
+ `e'
32-bit signed integer constant, or a symbolic reference known
to fit that range (for immediate operands in sign-extending
x86-64 instructions).
- 'Z'
+ `Z'
32-bit unsigned integer constant, or a symbolic reference
known to fit that range (for immediate operands in
zero-extending x86-64 instructions).
-_Xstormy16--'config/stormy16/stormy16.h'_
- 'a'
+
+_Xstormy16--`config/stormy16/stormy16.h'_
+
+ `a'
Register r0.
- 'b'
+ `b'
Register r1.
- 'c'
+ `c'
Register r2.
- 'd'
+ `d'
Register r8.
- 'e'
+ `e'
Registers r0 through r7.
- 't'
+ `t'
Registers r0 and r1.
- 'y'
+ `y'
The carry register.
- 'z'
+ `z'
Registers r8 and r9.
- 'I'
+ `I'
A constant between 0 and 3 inclusive.
- 'J'
+ `J'
A constant that has exactly one bit set.
- 'K'
+ `K'
A constant that has exactly one bit clear.
- 'L'
+ `L'
A constant between 0 and 255 inclusive.
- 'M'
+ `M'
A constant between -255 and 0 inclusive.
- 'N'
+ `N'
A constant between -3 and 0 inclusive.
- 'O'
+ `O'
A constant between 1 and 4 inclusive.
- 'P'
+ `P'
A constant between -4 and -1 inclusive.
- 'Q'
+ `Q'
A memory reference that is a stack push.
- 'R'
+ `R'
A memory reference that is a stack pop.
- 'S'
+ `S'
A memory reference that refers to a constant address of known
value.
- 'T'
+ `T'
The register indicated by Rx (not implemented yet).
- 'U'
+ `U'
A constant that is not between 2 and 15 inclusive.
- 'Z'
+ `Z'
The constant 0.
-_Xtensa--'config/xtensa/constraints.md'_
- 'a'
+
+_Xtensa--`config/xtensa/constraints.md'_
+
+ `a'
General-purpose 32-bit register
- 'b'
+ `b'
One-bit boolean register
- 'A'
+ `A'
MAC16 40-bit accumulator register
- 'I'
+ `I'
Signed 12-bit integer constant, for use in MOVI instructions
- 'J'
+ `J'
Signed 8-bit integer constant, for use in ADDI instructions
- 'K'
+ `K'
Integer constant valid for BccI instructions
- 'L'
+ `L'
Unsigned constant valid for BccUI instructions
+
+

File: gccint.info, Node: Disable Insn Alternatives, Next: Define Constraints, Prev: Machine Constraints, Up: Constraints
-16.8.6 Disable insn alternatives using the 'enabled' attribute
+16.8.6 Disable insn alternatives using the `enabled' attribute
--------------------------------------------------------------
There are three insn attributes that may be used to selectively disable
instruction alternatives:
-'enabled'
+`enabled'
Says whether an alternative is available on the current subtarget.
-'preferred_for_size'
+`preferred_for_size'
Says whether an enabled alternative should be used in code that is
optimized for size.
-'preferred_for_speed'
+`preferred_for_speed'
Says whether an enabled alternative should be used in code that is
optimized for speed.
- All these attributes should use '(const_int 1)' to allow an alternative
-or '(const_int 0)' to disallow it. The attributes must be a static
-property of the subtarget; they cannot for example depend on the current
-operands, on the current optimization level, on the location of the insn
-within the body of a loop, on whether register allocation has finished,
-or on the current compiler pass.
+ All these attributes should use `(const_int 1)' to allow an alternative
+or `(const_int 0)' to disallow it. The attributes must be a static
+property of the subtarget; they cannot for example depend on the
+current operands, on the current optimization level, on the location of
+the insn within the body of a loop, on whether register allocation has
+finished, or on the current compiler pass.
- The 'enabled' attribute is a correctness property. It tells GCC to act
+ The `enabled' attribute is a correctness property. It tells GCC to act
as though the disabled alternatives were never defined in the first
place. This is useful when adding new instructions to an existing
pattern in cases where the new instructions are only available for
-certain cpu architecture levels (typically mapped to the '-march='
+certain cpu architecture levels (typically mapped to the `-march='
command-line option).
- In contrast, the 'preferred_for_size' and 'preferred_for_speed'
+ In contrast, the `preferred_for_size' and `preferred_for_speed'
attributes are strong optimization hints rather than correctness
-properties. 'preferred_for_size' tells GCC which alternatives to
+properties. `preferred_for_size' tells GCC which alternatives to
consider when adding or modifying an instruction that GCC wants to
-optimize for size. 'preferred_for_speed' does the same thing for speed.
-Note that things like code motion can lead to cases where code optimized
-for size uses alternatives that are not preferred for size, and
-similarly for speed.
+optimize for size. `preferred_for_speed' does the same thing for
+speed. Note that things like code motion can lead to cases where code
+optimized for size uses alternatives that are not preferred for size,
+and similarly for speed.
- Although 'define_insn's can in principle specify the 'enabled'
+ Although `define_insn's can in principle specify the `enabled'
attribute directly, it is often clearer to have subsiduary attributes
-for each architectural feature of interest. The 'define_insn's can then
-use these subsiduary attributes to say which alternatives require which
-features. The example below does this for 'cpu_facility'.
+for each architectural feature of interest. The `define_insn's can
+then use these subsiduary attributes to say which alternatives require
+which features. The example below does this for `cpu_facility'.
- E.g. the following two patterns could easily be merged using the
-'enabled' attribute:
+ E.g. the following two patterns could easily be merged using the
+`enabled' attribute:
(define_insn "*movdi_old"
@@ -22297,7 +22666,6 @@ features. The example below does this for 'cpu_facility'.
ldgr %0,%1
lgdr %0,%1")
-
to:
@@ -22311,8 +22679,7 @@ features. The example below does this for 'cpu_facility'.
lgdr %0,%1"
[(set_attr "cpu_facility" "*,new,new")])
-
- with the 'enabled' attribute defined like this:
+ with the `enabled' attribute defined like this:
(define_attr "cpu_facility" "standard,new" (const_string "standard"))
@@ -22324,7 +22691,6 @@ features. The example below does this for 'cpu_facility'.
(const_int 1)]
(const_int 0)))
-

File: gccint.info, Node: Define Constraints, Next: C Constraint Interface, Prev: Disable Insn Alternatives, Up: Constraints
@@ -22332,20 +22698,21 @@ File: gccint.info, Node: Define Constraints, Next: C Constraint Interface, Pr
--------------------------------------------
Machine-specific constraints fall into two categories: register and
-non-register constraints. Within the latter category, constraints which
-allow subsets of all possible memory or address operands should be
-specially marked, to give 'reload' more information.
+non-register constraints. Within the latter category, constraints
+which allow subsets of all possible memory or address operands should
+be specially marked, to give `reload' more information.
Machine-specific constraints can be given names of arbitrary length,
but they must be entirely composed of letters, digits, underscores
-('_'), and angle brackets ('< >'). Like C identifiers, they must begin
+(`_'), and angle brackets (`< >'). Like C identifiers, they must begin
with a letter or underscore.
In order to avoid ambiguity in operand constraint strings, no
-constraint can have a name that begins with any other constraint's name.
-For example, if 'x' is defined as a constraint name, 'xy' may not be,
-and vice versa. As a consequence of this rule, no constraint may begin
-with one of the generic constraint letters: 'E F V X g i m n o p r s'.
+constraint can have a name that begins with any other constraint's
+name. For example, if `x' is defined as a constraint name, `xy' may
+not be, and vice versa. As a consequence of this rule, no constraint
+may begin with one of the generic constraint letters: `E F V X g i m n
+o p r s'.
Register constraints correspond directly to register classes. *Note
Register Classes::. There is thus not much flexibility in their
@@ -22353,15 +22720,16 @@ definitions.
-- MD Expression: define_register_constraint name regclass docstring
All three arguments are string constants. NAME is the name of the
- constraint, as it will appear in 'match_operand' expressions. If
+ constraint, as it will appear in `match_operand' expressions. If
NAME is a multi-letter constraint its length shall be the same for
all constraints starting with the same letter. REGCLASS can be
- either the name of the corresponding register class (*note Register
- Classes::), or a C expression which evaluates to the appropriate
- register class. If it is an expression, it must have no side
- effects, and it cannot look at the operand. The usual use of
- expressions is to map some register constraints to 'NO_REGS' when
- the register class is not available on a given subarchitecture.
+ either the name of the corresponding register class (*note
+ Register Classes::), or a C expression which evaluates to the
+ appropriate register class. If it is an expression, it must have
+ no side effects, and it cannot look at the operand. The usual use
+ of expressions is to map some register constraints to `NO_REGS'
+ when the register class is not available on a given
+ subarchitecture.
DOCSTRING is a sentence documenting the meaning of the constraint.
Docstrings are explained further below.
@@ -22372,100 +22740,105 @@ constraint matches.
-- MD Expression: define_constraint name docstring exp
The NAME and DOCSTRING arguments are the same as for
- 'define_register_constraint', but note that the docstring comes
+ `define_register_constraint', but note that the docstring comes
immediately after the name for these expressions. EXP is an RTL
expression, obeying the same rules as the RTL expressions in
predicate definitions. *Note Defining Predicates::, for details.
If it evaluates true, the constraint matches; if it evaluates
- false, it doesn't. Constraint expressions should indicate which
+ false, it doesn't. Constraint expressions should indicate which
RTL codes they might match, just like predicate expressions.
- 'match_test' C expressions have access to the following variables:
+ `match_test' C expressions have access to the following variables:
- OP
+ OP
The RTL object defining the operand.
- MODE
+
+ MODE
The machine mode of OP.
- IVAL
- 'INTVAL (OP)', if OP is a 'const_int'.
- HVAL
- 'CONST_DOUBLE_HIGH (OP)', if OP is an integer 'const_double'.
- LVAL
- 'CONST_DOUBLE_LOW (OP)', if OP is an integer 'const_double'.
- RVAL
- 'CONST_DOUBLE_REAL_VALUE (OP)', if OP is a floating-point
- 'const_double'.
+
+ IVAL
+ `INTVAL (OP)', if OP is a `const_int'.
+
+ HVAL
+ `CONST_DOUBLE_HIGH (OP)', if OP is an integer `const_double'.
+
+ LVAL
+ `CONST_DOUBLE_LOW (OP)', if OP is an integer `const_double'.
+
+ RVAL
+ `CONST_DOUBLE_REAL_VALUE (OP)', if OP is a floating-point
+ `const_double'.
The *VAL variables should only be used once another piece of the
expression has verified that OP is the appropriate kind of RTL
object.
Most non-register constraints should be defined with
-'define_constraint'. The remaining two definition expressions are only
-appropriate for constraints that should be handled specially by 'reload'
-if they fail to match.
+`define_constraint'. The remaining two definition expressions are only
+appropriate for constraints that should be handled specially by
+`reload' if they fail to match.
-- MD Expression: define_memory_constraint name docstring exp
Use this expression for constraints that match a subset of all
- memory operands: that is, 'reload' can make them match by
- converting the operand to the form '(mem (reg X))', where X is a
+ memory operands: that is, `reload' can make them match by
+ converting the operand to the form `(mem (reg X))', where X is a
base register (from the register class specified by
- 'BASE_REG_CLASS', *note Register Classes::).
+ `BASE_REG_CLASS', *note Register Classes::).
For example, on the S/390, some instructions do not accept
- arbitrary memory references, but only those that do not make use of
- an index register. The constraint letter 'Q' is defined to
- represent a memory address of this type. If 'Q' is defined with
- 'define_memory_constraint', a 'Q' constraint can handle any memory
- operand, because 'reload' knows it can simply copy the memory
- address into a base register if required. This is analogous to the
- way an 'o' constraint can handle any memory operand.
+ arbitrary memory references, but only those that do not make use
+ of an index register. The constraint letter `Q' is defined to
+ represent a memory address of this type. If `Q' is defined with
+ `define_memory_constraint', a `Q' constraint can handle any memory
+ operand, because `reload' knows it can simply copy the memory
+ address into a base register if required. This is analogous to
+ the way an `o' constraint can handle any memory operand.
The syntax and semantics are otherwise identical to
- 'define_constraint'.
+ `define_constraint'.
-- MD Expression: define_address_constraint name docstring exp
Use this expression for constraints that match a subset of all
- address operands: that is, 'reload' can make the constraint match
- by converting the operand to the form '(reg X)', again with X a
+ address operands: that is, `reload' can make the constraint match
+ by converting the operand to the form `(reg X)', again with X a
base register.
- Constraints defined with 'define_address_constraint' can only be
- used with the 'address_operand' predicate, or machine-specific
+ Constraints defined with `define_address_constraint' can only be
+ used with the `address_operand' predicate, or machine-specific
predicates that work the same way. They are treated analogously to
- the generic 'p' constraint.
+ the generic `p' constraint.
The syntax and semantics are otherwise identical to
- 'define_constraint'.
+ `define_constraint'.
- For historical reasons, names beginning with the letters 'G H' are
-reserved for constraints that match only 'const_double's, and names
-beginning with the letters 'I J K L M N O P' are reserved for
-constraints that match only 'const_int's. This may change in the
+ For historical reasons, names beginning with the letters `G H' are
+reserved for constraints that match only `const_double's, and names
+beginning with the letters `I J K L M N O P' are reserved for
+constraints that match only `const_int's. This may change in the
future. For the time being, constraints with these names must be
-written in a stylized form, so that 'genpreds' can tell you did it
+written in a stylized form, so that `genpreds' can tell you did it
correctly:
(define_constraint "[GHIJKLMNOP]..."
"DOC..."
- (and (match_code "const_int") ; 'const_double' for G/H
- CONDITION...)) ; usually a 'match_test'
+ (and (match_code "const_int") ; `const_double' for G/H
+ CONDITION...)) ; usually a `match_test'
It is fine to use names beginning with other letters for constraints
-that match 'const_double's or 'const_int's.
+that match `const_double's or `const_int's.
Each docstring in a constraint definition should be one or more
complete sentences, marked up in Texinfo format. _They are currently
-unused._ In the future they will be copied into the GCC manual, in
+unused._ In the future they will be copied into the GCC manual, in
*note Machine Constraints::, replacing the hand-maintained tables
currently found in that section. Also, in the future the compiler may
-use this to give more helpful diagnostics when poor choice of 'asm'
+use this to give more helpful diagnostics when poor choice of `asm'
constraints causes a reload failure.
- If you put the pseudo-Texinfo directive '@internal' at the beginning of
-a docstring, then (in the future) it will appear only in the internals
-manual's version of the machine-specific constraint tables. Use this
-for constraints that should not appear in 'asm' statements.
+ If you put the pseudo-Texinfo directive `@internal' at the beginning
+of a docstring, then (in the future) it will appear only in the
+internals manual's version of the machine-specific constraint tables.
+Use this for constraints that should not appear in `asm' statements.

File: gccint.info, Node: C Constraint Interface, Prev: Define Constraints, Up: Constraints
@@ -22474,59 +22847,60 @@ File: gccint.info, Node: C Constraint Interface, Prev: Define Constraints, Up
---------------------------------
It is occasionally useful to test a constraint from C code rather than
-implicitly via the constraint string in a 'match_operand'. The
-generated file 'tm_p.h' declares a few interfaces for working with
+implicitly via the constraint string in a `match_operand'. The
+generated file `tm_p.h' declares a few interfaces for working with
constraints. At present these are defined for all constraints except
-'g' (which is equivalent to 'general_operand').
+`g' (which is equivalent to `general_operand').
Some valid constraint names are not valid C identifiers, so there is a
mangling scheme for referring to them from C. Constraint names that do
not contain angle brackets or underscores are left unchanged.
-Underscores are doubled, each '<' is replaced with '_l', and each '>'
-with '_g'. Here are some examples:
+Underscores are doubled, each `<' is replaced with `_l', and each `>'
+with `_g'. Here are some examples:
- *Original* *Mangled*
- x x
- P42x P42x
- P4_x P4__x
- P4>x P4_gx
- P4>> P4_g_g
- P4_g> P4__g_g
+ *Original* *Mangled*
+ `x' `x'
+ `P42x' `P42x'
+ `P4_x' `P4__x'
+ `P4>x' `P4_gx'
+ `P4>>' `P4_g_g'
+ `P4_g>' `P4__g_g'
Throughout this section, the variable C is either a constraint in the
-abstract sense, or a constant from 'enum constraint_num'; the variable M
-is a mangled constraint name (usually as part of a larger identifier).
+abstract sense, or a constant from `enum constraint_num'; the variable
+M is a mangled constraint name (usually as part of a larger identifier).
-- Enum: constraint_num
- For each constraint except 'g', there is a corresponding
- enumeration constant: 'CONSTRAINT_' plus the mangled name of the
- constraint. Functions that take an 'enum constraint_num' as an
+ For each constraint except `g', there is a corresponding
+ enumeration constant: `CONSTRAINT_' plus the mangled name of the
+ constraint. Functions that take an `enum constraint_num' as an
argument expect one of these constants.
- -- Function: inline bool satisfies_constraint_ M (rtx EXP)
- For each non-register constraint M except 'g', there is one of
- these functions; it returns 'true' if EXP satisfies the constraint.
- These functions are only visible if 'rtl.h' was included before
- 'tm_p.h'.
+ -- Function: inline bool satisfies_constraint_M (rtx EXP)
+ For each non-register constraint M except `g', there is one of
+ these functions; it returns `true' if EXP satisfies the
+ constraint. These functions are only visible if `rtl.h' was
+ included before `tm_p.h'.
-- Function: bool constraint_satisfied_p (rtx EXP, enum constraint_num
C)
- Like the 'satisfies_constraint_M' functions, but the constraint to
+ Like the `satisfies_constraint_M' functions, but the constraint to
test is given as an argument, C. If C specifies a register
- constraint, this function will always return 'false'.
+ constraint, this function will always return `false'.
-- Function: enum reg_class reg_class_for_constraint (enum
constraint_num C)
Returns the register class associated with C. If C is not a
register constraint, or those registers are not available for the
- currently selected subtarget, returns 'NO_REGS'.
+ currently selected subtarget, returns `NO_REGS'.
- Here is an example use of 'satisfies_constraint_M'. In peephole
-optimizations (*note Peephole Definitions::), operand constraint strings
-are ignored, so if there are relevant constraints, they must be tested
-in the C condition. In the example, the optimization is applied if
-operand 2 does _not_ satisfy the 'K' constraint. (This is a simplified
-version of a peephole definition from the i386 machine description.)
+ Here is an example use of `satisfies_constraint_M'. In peephole
+optimizations (*note Peephole Definitions::), operand constraint
+strings are ignored, so if there are relevant constraints, they must be
+tested in the C condition. In the example, the optimization is applied
+if operand 2 does _not_ satisfy the `K' constraint. (This is a
+simplified version of a peephole definition from the i386 machine
+description.)
(define_peephole2
[(match_scratch:SI 3 "r")
@@ -22552,36 +22926,36 @@ generation pass of the compiler. Giving one of these names to an
instruction pattern tells the RTL generation pass that it can use the
pattern to accomplish a certain task.
-'movM'
+`movM'
Here M stands for a two-letter machine mode name, in lowercase.
This instruction pattern moves data with that machine mode from
- operand 1 to operand 0. For example, 'movsi' moves full-word data.
+ operand 1 to operand 0. For example, `movsi' moves full-word data.
- If operand 0 is a 'subreg' with mode M of a register whose own mode
- is wider than M, the effect of this instruction is to store the
- specified value in the part of the register that corresponds to
- mode M. Bits outside of M, but which are within the same target
- word as the 'subreg' are undefined. Bits which are outside the
- target word are left unchanged.
+ If operand 0 is a `subreg' with mode M of a register whose own
+ mode is wider than M, the effect of this instruction is to store
+ the specified value in the part of the register that corresponds
+ to mode M. Bits outside of M, but which are within the same
+ target word as the `subreg' are undefined. Bits which are outside
+ the target word are left unchanged.
This class of patterns is special in several ways. First of all,
each of these names up to and including full word size _must_ be
defined, because there is no other way to copy a datum from one
place to another. If there are patterns accepting operands in
- larger modes, 'movM' must be defined for integer modes of those
+ larger modes, `movM' must be defined for integer modes of those
sizes.
Second, these patterns are not used solely in the RTL generation
pass. Even the reload pass can generate move insns to copy values
- from stack slots into temporary registers. When it does so, one of
- the operands is a hard register and the other is an operand that
- can need to be reloaded into a register.
+ from stack slots into temporary registers. When it does so, one
+ of the operands is a hard register and the other is an operand
+ that can need to be reloaded into a register.
Therefore, when given such a pair of operands, the pattern must
generate RTL which needs no reloading and needs no temporary
registers--no registers other than the operands. For example, if
- you support the pattern with a 'define_expand', then in such a case
- the 'define_expand' mustn't call 'force_reg' or any other such
+ you support the pattern with a `define_expand', then in such a
+ case the `define_expand' mustn't call `force_reg' or any other such
function which might generate new pseudo registers.
This requirement exists even for subword modes on a RISC machine
@@ -22594,11 +22968,11 @@ pattern to accomplish a certain task.
be done with the address except to use it as it stands. If it is
copied, it will not be replaced with a valid address. No attempt
should be made to make such an address into a valid address and no
- routine (such as 'change_address') that will do so may be called.
- Note that 'general_operand' will fail when applied to such an
+ routine (such as `change_address') that will do so may be called.
+ Note that `general_operand' will fail when applied to such an
address.
- The global variable 'reload_in_progress' (which must be explicitly
+ The global variable `reload_in_progress' (which must be explicitly
declared if required) can be used to determine whether such special
handling is required.
@@ -22609,75 +22983,76 @@ pattern to accomplish a certain task.
reloads.
If a scratch register is required to move an object to or from
- memory, it can be allocated using 'gen_reg_rtx' prior to life
+ memory, it can be allocated using `gen_reg_rtx' prior to life
analysis.
If there are cases which need scratch registers during or after
reload, you must provide an appropriate secondary_reload target
hook.
- The macro 'can_create_pseudo_p' can be used to determine if it is
+ The macro `can_create_pseudo_p' can be used to determine if it is
unsafe to create new pseudo registers. If this variable is
- nonzero, then it is unsafe to call 'gen_reg_rtx' to allocate a new
+ nonzero, then it is unsafe to call `gen_reg_rtx' to allocate a new
pseudo.
- The constraints on a 'movM' must permit moving any hard register to
- any other hard register provided that 'HARD_REGNO_MODE_OK' permits
- mode M in both registers and 'TARGET_REGISTER_MOVE_COST' applied to
- their classes returns a value of 2.
-
- It is obligatory to support floating point 'movM' instructions into
- and out of any registers that can hold fixed point values, because
- unions and structures (which have modes 'SImode' or 'DImode') can
- be in those registers and they may have floating point members.
-
- There may also be a need to support fixed point 'movM' instructions
- in and out of floating point registers. Unfortunately, I have
- forgotten why this was so, and I don't know whether it is still
- true. If 'HARD_REGNO_MODE_OK' rejects fixed point values in
- floating point registers, then the constraints of the fixed point
- 'movM' instructions must be designed to avoid ever trying to reload
- into a floating point register.
-
-'reload_inM'
-'reload_outM'
+ The constraints on a `movM' must permit moving any hard register
+ to any other hard register provided that `HARD_REGNO_MODE_OK'
+ permits mode M in both registers and `TARGET_REGISTER_MOVE_COST'
+ applied to their classes returns a value of 2.
+
+ It is obligatory to support floating point `movM' instructions
+ into and out of any registers that can hold fixed point values,
+ because unions and structures (which have modes `SImode' or
+ `DImode') can be in those registers and they may have floating
+ point members.
+
+ There may also be a need to support fixed point `movM'
+ instructions in and out of floating point registers.
+ Unfortunately, I have forgotten why this was so, and I don't know
+ whether it is still true. If `HARD_REGNO_MODE_OK' rejects fixed
+ point values in floating point registers, then the constraints of
+ the fixed point `movM' instructions must be designed to avoid ever
+ trying to reload into a floating point register.
+
+`reload_inM'
+`reload_outM'
These named patterns have been obsoleted by the target hook
- 'secondary_reload'.
+ `secondary_reload'.
- Like 'movM', but used when a scratch register is required to move
+ Like `movM', but used when a scratch register is required to move
between operand 0 and operand 1. Operand 2 describes the scratch
- register. See the discussion of the 'SECONDARY_RELOAD_CLASS' macro
- in *note Register Classes::.
+ register. See the discussion of the `SECONDARY_RELOAD_CLASS'
+ macro in *note Register Classes::.
- There are special restrictions on the form of the 'match_operand's
+ There are special restrictions on the form of the `match_operand's
used in these patterns. First, only the predicate for the reload
- operand is examined, i.e., 'reload_in' examines operand 1, but not
+ operand is examined, i.e., `reload_in' examines operand 1, but not
the predicates for operand 0 or 2. Second, there may be only one
alternative in the constraints. Third, only a single register
class letter may be used for the constraint; subsequent constraint
letters are ignored. As a special exception, an empty constraint
- string matches the 'ALL_REGS' register class. This may relieve
- ports of the burden of defining an 'ALL_REGS' constraint letter
+ string matches the `ALL_REGS' register class. This may relieve
+ ports of the burden of defining an `ALL_REGS' constraint letter
just for these patterns.
-'movstrictM'
- Like 'movM' except that if operand 0 is a 'subreg' with mode M of a
- register whose natural mode is wider, the 'movstrictM' instruction
- is guaranteed not to alter any of the register except the part
- which belongs to mode M.
+`movstrictM'
+ Like `movM' except that if operand 0 is a `subreg' with mode M of
+ a register whose natural mode is wider, the `movstrictM'
+ instruction is guaranteed not to alter any of the register except
+ the part which belongs to mode M.
-'movmisalignM'
+`movmisalignM'
This variant of a move pattern is designed to load or store a value
from a memory address that is not naturally aligned for its mode.
For a store, the memory will be in operand 0; for a load, the
memory will be in operand 1. The other operand is guaranteed not
- to be a memory, so that it's easy to tell whether this is a load or
- store.
+ to be a memory, so that it's easy to tell whether this is a load
+ or store.
This pattern is used by the autovectorizer, and when expanding a
- 'MISALIGNED_INDIRECT_REF' expression.
+ `MISALIGNED_INDIRECT_REF' expression.
-'load_multiple'
+`load_multiple'
Load several consecutive memory locations into consecutive
registers. Operand 0 is the first of the consecutive registers,
operand 1 is the first memory location, and operand 2 is a
@@ -22691,22 +23066,22 @@ pattern to accomplish a certain task.
On some machines, there are restrictions as to which consecutive
registers can be stored into memory, such as particular starting or
ending register numbers or only a range of valid counts. For those
- machines, use a 'define_expand' (*note Expander Definitions::) and
+ machines, use a `define_expand' (*note Expander Definitions::) and
make the pattern fail if the restrictions are not met.
- Write the generated insn as a 'parallel' with elements being a
- 'set' of one register from the appropriate memory location (you may
- also need 'use' or 'clobber' elements). Use a 'match_parallel'
- (*note RTL Template::) to recognize the insn. See 'rs6000.md' for
+ Write the generated insn as a `parallel' with elements being a
+ `set' of one register from the appropriate memory location (you may
+ also need `use' or `clobber' elements). Use a `match_parallel'
+ (*note RTL Template::) to recognize the insn. See `rs6000.md' for
examples of the use of this insn pattern.
-'store_multiple'
- Similar to 'load_multiple', but store several consecutive registers
+`store_multiple'
+ Similar to `load_multiple', but store several consecutive registers
into consecutive memory locations. Operand 0 is the first of the
consecutive memory locations, operand 1 is the first register, and
operand 2 is a constant: the number of consecutive registers.
-'vec_load_lanesMN'
+`vec_load_lanesMN'
Perform an interleaved load of several vectors from memory operand
1 into register operand 0. Both operands have mode M. The
register operand is viewed as holding consecutive vectors of mode
@@ -22718,9 +23093,9 @@ pattern to accomplish a certain task.
for (i = 0; i < c; i++)
operand0[i][j] = operand1[j * c + i];
- For example, 'vec_load_lanestiv4hi' loads 8 16-bit values from
- memory into a register of mode 'TI'. The register contains two
- consecutive vectors of mode 'V4HI'.
+ For example, `vec_load_lanestiv4hi' loads 8 16-bit values from
+ memory into a register of mode `TI'. The register contains two
+ consecutive vectors of mode `V4HI'.
This pattern can only be used if:
TARGET_ARRAY_MODE_SUPPORTED_P (N, C)
@@ -22728,8 +23103,8 @@ pattern to accomplish a certain task.
instruction for some mode N, it also supports unaligned loads for
vectors of mode N.
-'vec_store_lanesMN'
- Equivalent to 'vec_load_lanesMN', with the memory and register
+`vec_store_lanesMN'
+ Equivalent to `vec_load_lanesMN', with the memory and register
operands reversed. That is, the instruction is equivalent to:
int c = GET_MODE_SIZE (M) / GET_MODE_SIZE (N);
@@ -22739,242 +23114,246 @@ pattern to accomplish a certain task.
for a memory operand 0 and register operand 1.
-'vec_setM'
+`vec_setM'
Set given field in the vector value. Operand 0 is the vector to
modify, operand 1 is new value of field and operand 2 specify the
field index.
-'vec_extractM'
+`vec_extractM'
Extract given field from the vector value. Operand 1 is the
vector, operand 2 specify field index and operand 0 place to store
value into.
-'vec_initM'
+`vec_initM'
Initialize the vector to given values. Operand 0 is the vector to
initialize and operand 1 is parallel containing values for
individual fields.
-'vcondMN'
+`vcondMN'
Output a conditional vector move. Operand 0 is the destination to
- receive a combination of operand 1 and operand 2, which are of mode
- M, dependent on the outcome of the predicate in operand 3 which is
- a vector comparison with operands of mode N in operands 4 and 5.
- The modes M and N should have the same size. Operand 0 will be set
- to the value OP1 & MSK | OP2 & ~MSK where MSK is computed by
- element-wise evaluation of the vector comparison with a truth value
- of all-ones and a false value of all-zeros.
-
-'vec_permM'
+ receive a combination of operand 1 and operand 2, which are of
+ mode M, dependent on the outcome of the predicate in operand 3
+ which is a vector comparison with operands of mode N in operands 4
+ and 5. The modes M and N should have the same size. Operand 0
+ will be set to the value OP1 & MSK | OP2 & ~MSK where MSK is
+ computed by element-wise evaluation of the vector comparison with
+ a truth value of all-ones and a false value of all-zeros.
+
+`vec_permM'
Output a (variable) vector permutation. Operand 0 is the
- destination to receive elements from operand 1 and operand 2, which
- are of mode M. Operand 3 is the "selector". It is an integral
- mode vector of the same width and number of elements as mode M.
+ destination to receive elements from operand 1 and operand 2,
+ which are of mode M. Operand 3 is the "selector". It is an
+ integral mode vector of the same width and number of elements as
+ mode M.
The input elements are numbered from 0 in operand 1 through 2*N-1
- in operand 2. The elements of the selector must be computed modulo
- 2*N. Note that if 'rtx_equal_p(operand1, operand2)', this can be
- implemented with just operand 1 and selector elements modulo N.
+ in operand 2. The elements of the selector must be computed
+ modulo 2*N. Note that if `rtx_equal_p(operand1, operand2)', this
+ can be implemented with just operand 1 and selector elements
+ modulo N.
In order to make things easy for a number of targets, if there is
- no 'vec_perm' pattern for mode M, but there is for mode Q where Q
- is a vector of 'QImode' of the same width as M, the middle-end will
- lower the mode M 'VEC_PERM_EXPR' to mode Q.
+ no `vec_perm' pattern for mode M, but there is for mode Q where Q
+ is a vector of `QImode' of the same width as M, the middle-end
+ will lower the mode M `VEC_PERM_EXPR' to mode Q.
-'vec_perm_constM'
- Like 'vec_perm' except that the permutation is a compile-time
- constant. That is, operand 3, the "selector", is a 'CONST_VECTOR'.
+`vec_perm_constM'
+ Like `vec_perm' except that the permutation is a compile-time
+ constant. That is, operand 3, the "selector", is a `CONST_VECTOR'.
Some targets cannot perform a permutation with a variable selector,
but can efficiently perform a constant permutation. Further, the
- target hook 'vec_perm_ok' is queried to determine if the specific
- constant permutation is available efficiently; the named pattern is
- never expanded without 'vec_perm_ok' returning true.
+ target hook `vec_perm_ok' is queried to determine if the specific
+ constant permutation is available efficiently; the named pattern
+ is never expanded without `vec_perm_ok' returning true.
- There is no need for a target to supply both 'vec_permM' and
- 'vec_perm_constM' if the former can trivially implement the
+ There is no need for a target to supply both `vec_permM' and
+ `vec_perm_constM' if the former can trivially implement the
operation with, say, the vector constant loaded into a register.
-'pushM1'
+`pushM1'
Output a push instruction. Operand 0 is value to push. Used only
- when 'PUSH_ROUNDING' is defined. For historical reason, this
- pattern may be missing and in such case an 'mov' expander is used
- instead, with a 'MEM' expression forming the push operation. The
- 'mov' expander method is deprecated.
+ when `PUSH_ROUNDING' is defined. For historical reason, this
+ pattern may be missing and in such case an `mov' expander is used
+ instead, with a `MEM' expression forming the push operation. The
+ `mov' expander method is deprecated.
-'addM3'
+`addM3'
Add operand 2 and operand 1, storing the result in operand 0. All
operands must have mode M. This can be used even on two-address
machines, by means of constraints requiring operands 1 and 0 to be
the same location.
-'addptrM3'
- Like 'addM3' but is guaranteed to only be used for address
+`addptrM3'
+ Like `addM3' but is guaranteed to only be used for address
calculations. The expanded code is not allowed to clobber the
- condition code. It only needs to be defined if 'addM3' sets the
+ condition code. It only needs to be defined if `addM3' sets the
condition code. If adds used for address calculations and normal
- adds are not compatible it is required to expand a distinct pattern
- (e.g. using an unspec). The pattern is used by LRA to emit
- address calculations. 'addM3' is used if 'addptrM3' is not
+ adds are not compatible it is required to expand a distinct
+ pattern (e.g. using an unspec). The pattern is used by LRA to emit
+ address calculations. `addM3' is used if `addptrM3' is not
defined.
-'ssaddM3', 'usaddM3'
-'subM3', 'sssubM3', 'ussubM3'
-'mulM3', 'ssmulM3', 'usmulM3'
-'divM3', 'ssdivM3'
-'udivM3', 'usdivM3'
-'modM3', 'umodM3'
-'uminM3', 'umaxM3'
-'andM3', 'iorM3', 'xorM3'
+`ssaddM3', `usaddM3'
+`subM3', `sssubM3', `ussubM3'
+`mulM3', `ssmulM3', `usmulM3'
+`divM3', `ssdivM3'
+`udivM3', `usdivM3'
+`modM3', `umodM3'
+`uminM3', `umaxM3'
+`andM3', `iorM3', `xorM3'
Similar, for other arithmetic operations.
-'fmaM4'
+`fmaM4'
Multiply operand 2 and operand 1, then add operand 3, storing the
result in operand 0 without doing an intermediate rounding step.
All operands must have mode M. This pattern is used to implement
- the 'fma', 'fmaf', and 'fmal' builtin functions from the ISO C99
+ the `fma', `fmaf', and `fmal' builtin functions from the ISO C99
standard.
-'fmsM4'
- Like 'fmaM4', except operand 3 subtracted from the product instead
+`fmsM4'
+ Like `fmaM4', except operand 3 subtracted from the product instead
of added to the product. This is represented in the rtl as
(fma:M OP1 OP2 (neg:M OP3))
-'fnmaM4'
- Like 'fmaM4' except that the intermediate product is negated before
- being added to operand 3. This is represented in the rtl as
+`fnmaM4'
+ Like `fmaM4' except that the intermediate product is negated
+ before being added to operand 3. This is represented in the rtl as
(fma:M (neg:M OP1) OP2 OP3)
-'fnmsM4'
- Like 'fmsM4' except that the intermediate product is negated before
- subtracting operand 3. This is represented in the rtl as
+`fnmsM4'
+ Like `fmsM4' except that the intermediate product is negated
+ before subtracting operand 3. This is represented in the rtl as
(fma:M (neg:M OP1) OP2 (neg:M OP3))
-'sminM3', 'smaxM3'
+`sminM3', `smaxM3'
Signed minimum and maximum operations. When used with floating
- point, if both operands are zeros, or if either operand is 'NaN',
- then it is unspecified which of the two operands is returned as the
- result.
+ point, if both operands are zeros, or if either operand is `NaN',
+ then it is unspecified which of the two operands is returned as
+ the result.
-'reduc_smin_M', 'reduc_smax_M'
- Find the signed minimum/maximum of the elements of a vector. The
+`reduc_smin_M', `reduc_smax_M'
+ Find the signed minimum/maximum of the elements of a vector. The
vector is operand 1, and the result is stored in the least
- significant bits of operand 0 (also a vector). The output and
- input vector should have the same modes. These are legacy optabs,
- and platforms should prefer to implement 'reduc_smin_scal_M' and
- 'reduc_smax_scal_M'.
+ significant bits of operand 0 (also a vector). The output and
+ input vector should have the same modes. These are legacy optabs,
+ and platforms should prefer to implement `reduc_smin_scal_M' and
+ `reduc_smax_scal_M'.
-'reduc_umin_M', 'reduc_umax_M'
- Find the unsigned minimum/maximum of the elements of a vector. The
+`reduc_umin_M', `reduc_umax_M'
+ Find the unsigned minimum/maximum of the elements of a vector. The
vector is operand 1, and the result is stored in the least
- significant bits of operand 0 (also a vector). The output and
- input vector should have the same modes. These are legacy optabs,
- and platforms should prefer to implement 'reduc_umin_scal_M' and
- 'reduc_umax_scal_M'.
+ significant bits of operand 0 (also a vector). The output and
+ input vector should have the same modes. These are legacy optabs,
+ and platforms should prefer to implement `reduc_umin_scal_M' and
+ `reduc_umax_scal_M'.
-'reduc_splus_M', 'reduc_uplus_M'
- Compute the sum of the signed/unsigned elements of a vector. The
+`reduc_splus_M', `reduc_uplus_M'
+ Compute the sum of the signed/unsigned elements of a vector. The
vector is operand 1, and the result is stored in the least
- significant bits of operand 0 (also a vector). The output and
+ significant bits of operand 0 (also a vector). The output and
input vector should have the same modes. These are legacy optabs,
- and platforms should prefer to implement 'reduc_plus_scal_M'.
+ and platforms should prefer to implement `reduc_plus_scal_M'.
-'reduc_smin_scal_M', 'reduc_smax_scal_M'
- Find the signed minimum/maximum of the elements of a vector. The
+`reduc_smin_scal_M', `reduc_smax_scal_M'
+ Find the signed minimum/maximum of the elements of a vector. The
vector is operand 1, and operand 0 is the scalar result, with mode
equal to the mode of the elements of the input vector.
-'reduc_umin_scal_M', 'reduc_umax_scal_M'
- Find the unsigned minimum/maximum of the elements of a vector. The
+`reduc_umin_scal_M', `reduc_umax_scal_M'
+ Find the unsigned minimum/maximum of the elements of a vector. The
vector is operand 1, and operand 0 is the scalar result, with mode
equal to the mode of the elements of the input vector.
-'reduc_plus_scal_M'
- Compute the sum of the elements of a vector. The vector is operand
+`reduc_plus_scal_M'
+ Compute the sum of the elements of a vector. The vector is operand
1, and operand 0 is the scalar result, with mode equal to the mode
of the elements of the input vector.
-'sdot_prodM'
-'udot_prodM'
+`sdot_prodM'
+`udot_prodM'
Compute the sum of the products of two signed/unsigned elements.
- Operand 1 and operand 2 are of the same mode. Their product, which
- is of a wider mode, is computed and added to operand 3. Operand 3
- is of a mode equal or wider than the mode of the product. The
- result is placed in operand 0, which is of the same mode as operand
- 3.
-
-'ssadM'
-'usadM'
+ Operand 1 and operand 2 are of the same mode. Their product, which
+ is of a wider mode, is computed and added to operand 3. Operand 3
+ is of a mode equal or wider than the mode of the product. The
+ result is placed in operand 0, which is of the same mode as
+ operand 3.
+
+`ssadM'
+
+`usadM'
Compute the sum of absolute differences of two signed/unsigned
- elements. Operand 1 and operand 2 are of the same mode. Their
+ elements. Operand 1 and operand 2 are of the same mode. Their
absolute difference, which is of a wider mode, is computed and
- added to operand 3. Operand 3 is of a mode equal or wider than the
- mode of the absolute difference. The result is placed in operand
+ added to operand 3. Operand 3 is of a mode equal or wider than the
+ mode of the absolute difference. The result is placed in operand
0, which is of the same mode as operand 3.
-'ssum_widenM3'
-'usum_widenM3'
- Operands 0 and 2 are of the same mode, which is wider than the mode
- of operand 1. Add operand 1 to operand 2 and place the widened
- result in operand 0. (This is used express accumulation of
+`ssum_widenM3'
+`usum_widenM3'
+ Operands 0 and 2 are of the same mode, which is wider than the
+ mode of operand 1. Add operand 1 to operand 2 and place the
+ widened result in operand 0. (This is used express accumulation of
elements into an accumulator of a wider mode.)
-'vec_shr_M'
- Whole vector right shift in bits, i.e. towards element 0. Operand
+`vec_shr_M'
+ Whole vector right shift in bits, i.e. towards element 0. Operand
1 is a vector to be shifted. Operand 2 is an integer shift amount
in bits. Operand 0 is where the resulting shifted vector is
stored. The output and input vectors should have the same modes.
-'vec_pack_trunc_M'
- Narrow (demote) and merge the elements of two vectors. Operands 1
+`vec_pack_trunc_M'
+ Narrow (demote) and merge the elements of two vectors. Operands 1
and 2 are vectors of the same mode having N integral or floating
point elements of size S. Operand 0 is the resulting vector in
which 2*N elements of size N/2 are concatenated after narrowing
them down using truncation.
-'vec_pack_ssat_M', 'vec_pack_usat_M'
+`vec_pack_ssat_M', `vec_pack_usat_M'
Narrow (demote) and merge the elements of two vectors. Operands 1
and 2 are vectors of the same mode having N integral elements of
- size S. Operand 0 is the resulting vector in which the elements of
- the two input vectors are concatenated after narrowing them down
- using signed/unsigned saturating arithmetic.
+ size S. Operand 0 is the resulting vector in which the elements
+ of the two input vectors are concatenated after narrowing them
+ down using signed/unsigned saturating arithmetic.
-'vec_pack_sfix_trunc_M', 'vec_pack_ufix_trunc_M'
+`vec_pack_sfix_trunc_M', `vec_pack_ufix_trunc_M'
Narrow, convert to signed/unsigned integral type and merge the
elements of two vectors. Operands 1 and 2 are vectors of the same
mode having N floating point elements of size S. Operand 0 is the
resulting vector in which 2*N elements of size N/2 are
concatenated.
-'vec_unpacks_hi_M', 'vec_unpacks_lo_M'
+`vec_unpacks_hi_M', `vec_unpacks_lo_M'
Extract and widen (promote) the high/low part of a vector of signed
integral or floating point elements. The input vector (operand 1)
- has N elements of size S. Widen (promote) the high/low elements of
- the vector using signed or floating point extension and place the
- resulting N/2 values of size 2*S in the output vector (operand 0).
+ has N elements of size S. Widen (promote) the high/low elements
+ of the vector using signed or floating point extension and place
+ the resulting N/2 values of size 2*S in the output vector (operand
+ 0).
-'vec_unpacku_hi_M', 'vec_unpacku_lo_M'
+`vec_unpacku_hi_M', `vec_unpacku_lo_M'
Extract and widen (promote) the high/low part of a vector of
unsigned integral elements. The input vector (operand 1) has N
- elements of size S. Widen (promote) the high/low elements of the
+ elements of size S. Widen (promote) the high/low elements of the
vector using zero extension and place the resulting N/2 values of
size 2*S in the output vector (operand 0).
-'vec_unpacks_float_hi_M', 'vec_unpacks_float_lo_M'
-'vec_unpacku_float_hi_M', 'vec_unpacku_float_lo_M'
- Extract, convert to floating point type and widen the high/low part
- of a vector of signed/unsigned integral elements. The input vector
- (operand 1) has N elements of size S. Convert the high/low
+`vec_unpacks_float_hi_M', `vec_unpacks_float_lo_M'
+`vec_unpacku_float_hi_M', `vec_unpacku_float_lo_M'
+ Extract, convert to floating point type and widen the high/low
+ part of a vector of signed/unsigned integral elements. The input
+ vector (operand 1) has N elements of size S. Convert the high/low
elements of the vector using floating point conversion and place
the resulting N/2 values of size 2*S in the output vector (operand
0).
-'vec_widen_umult_hi_M', 'vec_widen_umult_lo_M'
-'vec_widen_smult_hi_M', 'vec_widen_smult_lo_M'
-'vec_widen_umult_even_M', 'vec_widen_umult_odd_M'
-'vec_widen_smult_even_M', 'vec_widen_smult_odd_M'
+`vec_widen_umult_hi_M', `vec_widen_umult_lo_M'
+`vec_widen_smult_hi_M', `vec_widen_smult_lo_M'
+`vec_widen_umult_even_M', `vec_widen_umult_odd_M'
+`vec_widen_smult_even_M', `vec_widen_smult_odd_M'
Signed/Unsigned widening multiplication. The two inputs (operands
1 and 2) are vectors with N signed/unsigned elements of size S.
Multiply the high/low or even/odd elements of the two vectors, and
@@ -22982,429 +23361,429 @@ pattern to accomplish a certain task.
A target shouldn't implement even/odd pattern pair if it is less
efficient than lo/hi one.
-'vec_widen_ushiftl_hi_M', 'vec_widen_ushiftl_lo_M'
-'vec_widen_sshiftl_hi_M', 'vec_widen_sshiftl_lo_M'
+`vec_widen_ushiftl_hi_M', `vec_widen_ushiftl_lo_M'
+`vec_widen_sshiftl_hi_M', `vec_widen_sshiftl_lo_M'
Signed/Unsigned widening shift left. The first input (operand 1)
is a vector with N signed/unsigned elements of size S. Operand 2
is a constant. Shift the high/low elements of operand 1, and put
the N/2 results of size 2*S in the output vector (operand 0).
-'mulhisi3'
- Multiply operands 1 and 2, which have mode 'HImode', and store a
- 'SImode' product in operand 0.
+`mulhisi3'
+ Multiply operands 1 and 2, which have mode `HImode', and store a
+ `SImode' product in operand 0.
-'mulqihi3', 'mulsidi3'
+`mulqihi3', `mulsidi3'
Similar widening-multiplication instructions of other widths.
-'umulqihi3', 'umulhisi3', 'umulsidi3'
+`umulqihi3', `umulhisi3', `umulsidi3'
Similar widening-multiplication instructions that do unsigned
multiplication.
-'usmulqihi3', 'usmulhisi3', 'usmulsidi3'
+`usmulqihi3', `usmulhisi3', `usmulsidi3'
Similar widening-multiplication instructions that interpret the
- first operand as unsigned and the second operand as signed, then do
- a signed multiplication.
+ first operand as unsigned and the second operand as signed, then
+ do a signed multiplication.
-'smulM3_highpart'
+`smulM3_highpart'
Perform a signed multiplication of operands 1 and 2, which have
mode M, and store the most significant half of the product in
operand 0. The least significant half of the product is discarded.
-'umulM3_highpart'
+`umulM3_highpart'
Similar, but the multiplication is unsigned.
-'maddMN4'
+`maddMN4'
Multiply operands 1 and 2, sign-extend them to mode N, add operand
- 3, and store the result in operand 0. Operands 1 and 2 have mode M
- and operands 0 and 3 have mode N. Both modes must be integer or
+ 3, and store the result in operand 0. Operands 1 and 2 have mode
+ M and operands 0 and 3 have mode N. Both modes must be integer or
fixed-point modes and N must be twice the size of M.
- In other words, 'maddMN4' is like 'mulMN3' except that it also adds
- operand 3.
+ In other words, `maddMN4' is like `mulMN3' except that it also
+ adds operand 3.
- These instructions are not allowed to 'FAIL'.
+ These instructions are not allowed to `FAIL'.
-'umaddMN4'
- Like 'maddMN4', but zero-extend the multiplication operands instead
- of sign-extending them.
+`umaddMN4'
+ Like `maddMN4', but zero-extend the multiplication operands
+ instead of sign-extending them.
-'ssmaddMN4'
- Like 'maddMN4', but all involved operations must be
+`ssmaddMN4'
+ Like `maddMN4', but all involved operations must be
signed-saturating.
-'usmaddMN4'
- Like 'umaddMN4', but all involved operations must be
+`usmaddMN4'
+ Like `umaddMN4', but all involved operations must be
unsigned-saturating.
-'msubMN4'
+`msubMN4'
Multiply operands 1 and 2, sign-extend them to mode N, subtract the
- result from operand 3, and store the result in operand 0. Operands
- 1 and 2 have mode M and operands 0 and 3 have mode N. Both modes
- must be integer or fixed-point modes and N must be twice the size
- of M.
+ result from operand 3, and store the result in operand 0.
+ Operands 1 and 2 have mode M and operands 0 and 3 have mode N.
+ Both modes must be integer or fixed-point modes and N must be twice
+ the size of M.
- In other words, 'msubMN4' is like 'mulMN3' except that it also
+ In other words, `msubMN4' is like `mulMN3' except that it also
subtracts the result from operand 3.
- These instructions are not allowed to 'FAIL'.
+ These instructions are not allowed to `FAIL'.
-'umsubMN4'
- Like 'msubMN4', but zero-extend the multiplication operands instead
- of sign-extending them.
+`umsubMN4'
+ Like `msubMN4', but zero-extend the multiplication operands
+ instead of sign-extending them.
-'ssmsubMN4'
- Like 'msubMN4', but all involved operations must be
+`ssmsubMN4'
+ Like `msubMN4', but all involved operations must be
signed-saturating.
-'usmsubMN4'
- Like 'umsubMN4', but all involved operations must be
+`usmsubMN4'
+ Like `umsubMN4', but all involved operations must be
unsigned-saturating.
-'divmodM4'
+`divmodM4'
Signed division that produces both a quotient and a remainder.
Operand 1 is divided by operand 2 to produce a quotient stored in
operand 0 and a remainder stored in operand 3.
For machines with an instruction that produces both a quotient and
- a remainder, provide a pattern for 'divmodM4' but do not provide
- patterns for 'divM3' and 'modM3'. This allows optimization in the
+ a remainder, provide a pattern for `divmodM4' but do not provide
+ patterns for `divM3' and `modM3'. This allows optimization in the
relatively common case when both the quotient and remainder are
computed.
If an instruction that just produces a quotient or just a remainder
exists and is more efficient than the instruction that produces
- both, write the output routine of 'divmodM4' to call
- 'find_reg_note' and look for a 'REG_UNUSED' note on the quotient or
- remainder and generate the appropriate instruction.
+ both, write the output routine of `divmodM4' to call
+ `find_reg_note' and look for a `REG_UNUSED' note on the quotient
+ or remainder and generate the appropriate instruction.
-'udivmodM4'
+`udivmodM4'
Similar, but does unsigned division.
-'ashlM3', 'ssashlM3', 'usashlM3'
+`ashlM3', `ssashlM3', `usashlM3'
Arithmetic-shift operand 1 left by a number of bits specified by
operand 2, and store the result in operand 0. Here M is the mode
of operand 0 and operand 1; operand 2's mode is specified by the
instruction pattern, and the compiler will convert the operand to
that mode before generating the instruction. The meaning of
out-of-range shift counts can optionally be specified by
- 'TARGET_SHIFT_TRUNCATION_MASK'. *Note
+ `TARGET_SHIFT_TRUNCATION_MASK'. *Note
TARGET_SHIFT_TRUNCATION_MASK::. Operand 2 is always a scalar type.
-'ashrM3', 'lshrM3', 'rotlM3', 'rotrM3'
- Other shift and rotate instructions, analogous to the 'ashlM3'
+`ashrM3', `lshrM3', `rotlM3', `rotrM3'
+ Other shift and rotate instructions, analogous to the `ashlM3'
instructions. Operand 2 is always a scalar type.
-'vashlM3', 'vashrM3', 'vlshrM3', 'vrotlM3', 'vrotrM3'
+`vashlM3', `vashrM3', `vlshrM3', `vrotlM3', `vrotrM3'
Vector shift and rotate instructions that take vectors as operand 2
instead of a scalar type.
-'bswapM2'
+`bswapM2'
Reverse the order of bytes of operand 1 and store the result in
operand 0.
-'negM2', 'ssnegM2', 'usnegM2'
+`negM2', `ssnegM2', `usnegM2'
Negate operand 1 and store the result in operand 0.
-'absM2'
+`absM2'
Store the absolute value of operand 1 into operand 0.
-'sqrtM2'
+`sqrtM2'
Store the square root of operand 1 into operand 0.
- The 'sqrt' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'sqrtf' built-in
+ The `sqrt' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `sqrtf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'fmodM3'
- Store the remainder of dividing operand 1 by operand 2 into operand
- 0, rounded towards zero to an integer.
+`fmodM3'
+ Store the remainder of dividing operand 1 by operand 2 into
+ operand 0, rounded towards zero to an integer.
- The 'fmod' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'fmodf' built-in
+ The `fmod' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `fmodf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'remainderM3'
- Store the remainder of dividing operand 1 by operand 2 into operand
- 0, rounded to the nearest integer.
+`remainderM3'
+ Store the remainder of dividing operand 1 by operand 2 into
+ operand 0, rounded to the nearest integer.
- The 'remainder' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'remainderf'
+ The `remainder' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `remainderf'
built-in function uses the mode which corresponds to the C data
- type 'float'.
+ type `float'.
-'cosM2'
+`cosM2'
Store the cosine of operand 1 into operand 0.
- The 'cos' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'cosf' built-in
+ The `cos' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `cosf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'sinM2'
+`sinM2'
Store the sine of operand 1 into operand 0.
- The 'sin' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'sinf' built-in
+ The `sin' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `sinf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'sincosM3'
+`sincosM3'
Store the cosine of operand 2 into operand 0 and the sine of
operand 2 into operand 1.
- The 'sin' and 'cos' built-in functions of C always use the mode
- which corresponds to the C data type 'double' and the 'sinf' and
- 'cosf' built-in function use the mode which corresponds to the C
- data type 'float'. Targets that can calculate the sine and cosine
+ The `sin' and `cos' built-in functions of C always use the mode
+ which corresponds to the C data type `double' and the `sinf' and
+ `cosf' built-in function use the mode which corresponds to the C
+ data type `float'. Targets that can calculate the sine and cosine
simultaneously can implement this pattern as opposed to
- implementing individual 'sinM2' and 'cosM2' patterns. The 'sin'
- and 'cos' built-in functions will then be expanded to the
- 'sincosM3' pattern, with one of the output values left unused.
+ implementing individual `sinM2' and `cosM2' patterns. The `sin'
+ and `cos' built-in functions will then be expanded to the
+ `sincosM3' pattern, with one of the output values left unused.
-'expM2'
+`expM2'
Store the exponential of operand 1 into operand 0.
- The 'exp' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'expf' built-in
+ The `exp' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `expf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'logM2'
+`logM2'
Store the natural logarithm of operand 1 into operand 0.
- The 'log' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'logf' built-in
+ The `log' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `logf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'powM3'
+`powM3'
Store the value of operand 1 raised to the exponent operand 2 into
operand 0.
- The 'pow' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'powf' built-in
+ The `pow' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `powf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'atan2M3'
+`atan2M3'
Store the arc tangent (inverse tangent) of operand 1 divided by
operand 2 into operand 0, using the signs of both arguments to
determine the quadrant of the result.
- The 'atan2' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'atan2f' built-in
+ The `atan2' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `atan2f' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'floorM2'
+`floorM2'
Store the largest integral value not greater than argument.
- The 'floor' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'floorf' built-in
+ The `floor' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `floorf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'btruncM2'
+`btruncM2'
Store the argument rounded to integer towards zero.
- The 'trunc' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'truncf' built-in
+ The `trunc' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `truncf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'roundM2'
+`roundM2'
Store the argument rounded to integer away from zero.
- The 'round' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'roundf' built-in
+ The `round' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `roundf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'ceilM2'
+`ceilM2'
Store the argument rounded to integer away from zero.
- The 'ceil' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'ceilf' built-in
+ The `ceil' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `ceilf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'nearbyintM2'
+`nearbyintM2'
Store the argument rounded according to the default rounding mode
- The 'nearbyint' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'nearbyintf'
+ The `nearbyint' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `nearbyintf'
built-in function uses the mode which corresponds to the C data
- type 'float'.
+ type `float'.
-'rintM2'
+`rintM2'
Store the argument rounded according to the default rounding mode
and raise the inexact exception when the result differs in value
from the argument
- The 'rint' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'rintf' built-in
+ The `rint' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `rintf' built-in
function uses the mode which corresponds to the C data type
- 'float'.
+ `float'.
-'lrintMN2'
+`lrintMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
mode N as a signed number according to the current rounding mode
and store in operand 0 (which has mode N).
-'lroundMN2'
+`lroundMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
mode N as a signed number rounding to nearest and away from zero
and store in operand 0 (which has mode N).
-'lfloorMN2'
+`lfloorMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
mode N as a signed number rounding down and store in operand 0
(which has mode N).
-'lceilMN2'
+`lceilMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
- mode N as a signed number rounding up and store in operand 0 (which
- has mode N).
+ mode N as a signed number rounding up and store in operand 0
+ (which has mode N).
-'copysignM3'
+`copysignM3'
Store a value with the magnitude of operand 1 and the sign of
operand 2 into operand 0.
- The 'copysign' built-in function of C always uses the mode which
- corresponds to the C data type 'double' and the 'copysignf'
+ The `copysign' built-in function of C always uses the mode which
+ corresponds to the C data type `double' and the `copysignf'
built-in function uses the mode which corresponds to the C data
- type 'float'.
+ type `float'.
-'ffsM2'
+`ffsM2'
Store into operand 0 one plus the index of the least significant
1-bit of operand 1. If operand 1 is zero, store zero. M is the
mode of operand 0; operand 1's mode is specified by the instruction
pattern, and the compiler will convert the operand to that mode
before generating the instruction.
- The 'ffs' built-in function of C always uses the mode which
- corresponds to the C data type 'int'.
+ The `ffs' built-in function of C always uses the mode which
+ corresponds to the C data type `int'.
-'clrsbM2'
- Count leading redundant sign bits. Store into operand 0 the number
- of redundant sign bits in operand 1, starting at the most
+`clrsbM2'
+ Count leading redundant sign bits. Store into operand 0 the
+ number of redundant sign bits in operand 1, starting at the most
significant bit position. A redundant sign bit is defined as any
- sign bit after the first. As such, this count will be one less
+ sign bit after the first. As such, this count will be one less
than the count of leading sign bits.
-'clzM2'
+`clzM2'
Store into operand 0 the number of leading 0-bits in operand 1,
starting at the most significant bit position. If operand 1 is 0,
- the 'CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if the
- result is undefined or has a useful value. M is the mode of
+ the `CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if
+ the result is undefined or has a useful value. M is the mode of
operand 0; operand 1's mode is specified by the instruction
pattern, and the compiler will convert the operand to that mode
before generating the instruction.
-'ctzM2'
+`ctzM2'
Store into operand 0 the number of trailing 0-bits in operand 1,
- starting at the least significant bit position. If operand 1 is 0,
- the 'CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if the
- result is undefined or has a useful value. M is the mode of
+ starting at the least significant bit position. If operand 1 is
+ 0, the `CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if
+ the result is undefined or has a useful value. M is the mode of
operand 0; operand 1's mode is specified by the instruction
pattern, and the compiler will convert the operand to that mode
before generating the instruction.
-'popcountM2'
+`popcountM2'
Store into operand 0 the number of 1-bits in operand 1. M is the
mode of operand 0; operand 1's mode is specified by the instruction
pattern, and the compiler will convert the operand to that mode
before generating the instruction.
-'parityM2'
+`parityM2'
Store into operand 0 the parity of operand 1, i.e. the number of
1-bits in operand 1 modulo 2. M is the mode of operand 0; operand
1's mode is specified by the instruction pattern, and the compiler
will convert the operand to that mode before generating the
instruction.
-'one_cmplM2'
+`one_cmplM2'
Store the bitwise-complement of operand 1 into operand 0.
-'movmemM'
+`movmemM'
Block move instruction. The destination and source blocks of
- memory are the first two operands, and both are 'mem:BLK's with an
- address in mode 'Pmode'.
+ memory are the first two operands, and both are `mem:BLK's with an
+ address in mode `Pmode'.
The number of bytes to move is the third operand, in mode M.
- Usually, you specify 'Pmode' for M. However, if you can generate
+ Usually, you specify `Pmode' for M. However, if you can generate
better code knowing the range of valid lengths is smaller than
those representable in a full Pmode pointer, you should provide a
pattern with a mode corresponding to the range of values you can
- handle efficiently (e.g., 'QImode' for values in the range 0-127;
- note we avoid numbers that appear negative) and also a pattern with
- 'Pmode'.
+ handle efficiently (e.g., `QImode' for values in the range 0-127;
+ note we avoid numbers that appear negative) and also a pattern
+ with `Pmode'.
The fourth operand is the known shared alignment of the source and
- destination, in the form of a 'const_int' rtx. Thus, if the
+ destination, in the form of a `const_int' rtx. Thus, if the
compiler knows that both source and destination are word-aligned,
it may provide the value 4 for this operand.
Optional operands 5 and 6 specify expected alignment and size of
block respectively. The expected alignment differs from alignment
in operand 4 in a way that the blocks are not required to be
- aligned according to it in all cases. This expected alignment is
+ aligned according to it in all cases. This expected alignment is
also in bytes, just like operand 4. Expected size, when unknown,
- is set to '(const_int -1)'.
+ is set to `(const_int -1)'.
- Descriptions of multiple 'movmemM' patterns can only be beneficial
+ Descriptions of multiple `movmemM' patterns can only be beneficial
if the patterns for smaller modes have fewer restrictions on their
first, second and fourth operands. Note that the mode M in
- 'movmemM' does not impose any restriction on the mode of
+ `movmemM' does not impose any restriction on the mode of
individually moved data units in the block.
These patterns need not give special consideration to the
possibility that the source and destination strings might overlap.
-'movstr'
- String copy instruction, with 'stpcpy' semantics. Operand 0 is an
- output operand in mode 'Pmode'. The addresses of the destination
- and source strings are operands 1 and 2, and both are 'mem:BLK's
- with addresses in mode 'Pmode'. The execution of the expansion of
+`movstr'
+ String copy instruction, with `stpcpy' semantics. Operand 0 is an
+ output operand in mode `Pmode'. The addresses of the destination
+ and source strings are operands 1 and 2, and both are `mem:BLK's
+ with addresses in mode `Pmode'. The execution of the expansion of
this pattern should store in operand 0 the address in which the
- 'NUL' terminator was stored in the destination string.
+ `NUL' terminator was stored in the destination string.
This patern has also several optional operands that are same as in
- 'setmem'.
+ `setmem'.
-'setmemM'
+`setmemM'
Block set instruction. The destination string is the first
- operand, given as a 'mem:BLK' whose address is in mode 'Pmode'.
+ operand, given as a `mem:BLK' whose address is in mode `Pmode'.
The number of bytes to set is the second operand, in mode M. The
- value to initialize the memory with is the third operand. Targets
+ value to initialize the memory with is the third operand. Targets
that only support the clearing of memory should reject any value
- that is not the constant 0. See 'movmemM' for a discussion of the
+ that is not the constant 0. See `movmemM' for a discussion of the
choice of mode.
The fourth operand is the known alignment of the destination, in
- the form of a 'const_int' rtx. Thus, if the compiler knows that
+ the form of a `const_int' rtx. Thus, if the compiler knows that
the destination is word-aligned, it may provide the value 4 for
this operand.
Optional operands 5 and 6 specify expected alignment and size of
block respectively. The expected alignment differs from alignment
in operand 4 in a way that the blocks are not required to be
- aligned according to it in all cases. This expected alignment is
+ aligned according to it in all cases. This expected alignment is
also in bytes, just like operand 4. Expected size, when unknown,
- is set to '(const_int -1)'. Operand 7 is the minimal size of the
+ is set to `(const_int -1)'. Operand 7 is the minimal size of the
block and operand 8 is the maximal size of the block (NULL if it
- can not be represented as CONST_INT). Operand 9 is the probable
- maximal size (i.e. we can not rely on it for correctness, but it
+ can not be represented as CONST_INT). Operand 9 is the probable
+ maximal size (i.e. we can not rely on it for correctness, but it
can be used for choosing proper code sequence for a given size).
- The use for multiple 'setmemM' is as for 'movmemM'.
+ The use for multiple `setmemM' is as for `movmemM'.
-'cmpstrnM'
+`cmpstrnM'
String compare instruction, with five operands. Operand 0 is the
output; it has mode M. The remaining four operands are like the
- operands of 'movmemM'. The two memory blocks specified are
+ operands of `movmemM'. The two memory blocks specified are
compared byte by byte in lexicographic order starting at the
beginning of each string. The instruction is not allowed to
prefetch more than one byte at a time since either string may end
@@ -23414,183 +23793,183 @@ pattern to accomplish a certain task.
effect of the instruction is to store a value in operand 0 whose
sign indicates the result of the comparison.
-'cmpstrM'
+`cmpstrM'
String compare instruction, without known maximum length. Operand
0 is the output; it has mode M. The second and third operand are
- the blocks of memory to be compared; both are 'mem:BLK' with an
- address in mode 'Pmode'.
+ the blocks of memory to be compared; both are `mem:BLK' with an
+ address in mode `Pmode'.
The fourth operand is the known shared alignment of the source and
- destination, in the form of a 'const_int' rtx. Thus, if the
+ destination, in the form of a `const_int' rtx. Thus, if the
compiler knows that both source and destination are word-aligned,
it may provide the value 4 for this operand.
The two memory blocks specified are compared byte by byte in
lexicographic order starting at the beginning of each string. The
- instruction is not allowed to prefetch more than one byte at a time
- since either string may end in the first byte and reading past that
- may access an invalid page or segment and cause a fault. The
- comparison will terminate when the fetched bytes are different or
- if they are equal to zero. The effect of the instruction is to
+ instruction is not allowed to prefetch more than one byte at a
+ time since either string may end in the first byte and reading
+ past that may access an invalid page or segment and cause a fault.
+ The comparison will terminate when the fetched bytes are different
+ or if they are equal to zero. The effect of the instruction is to
store a value in operand 0 whose sign indicates the result of the
comparison.
-'cmpmemM'
+`cmpmemM'
Block compare instruction, with five operands like the operands of
- 'cmpstrM'. The two memory blocks specified are compared byte by
+ `cmpstrM'. The two memory blocks specified are compared byte by
byte in lexicographic order starting at the beginning of each
- block. Unlike 'cmpstrM' the instruction can prefetch any bytes in
- the two memory blocks. Also unlike 'cmpstrM' the comparison will
+ block. Unlike `cmpstrM' the instruction can prefetch any bytes in
+ the two memory blocks. Also unlike `cmpstrM' the comparison will
not stop if both bytes are zero. The effect of the instruction is
to store a value in operand 0 whose sign indicates the result of
the comparison.
-'strlenM'
+`strlenM'
Compute the length of a string, with three operands. Operand 0 is
- the result (of mode M), operand 1 is a 'mem' referring to the first
- character of the string, operand 2 is the character to search for
- (normally zero), and operand 3 is a constant describing the known
- alignment of the beginning of the string.
+ the result (of mode M), operand 1 is a `mem' referring to the
+ first character of the string, operand 2 is the character to
+ search for (normally zero), and operand 3 is a constant describing
+ the known alignment of the beginning of the string.
-'floatMN2'
+`floatMN2'
Convert signed integer operand 1 (valid for fixed point mode M) to
floating point mode N and store in operand 0 (which has mode N).
-'floatunsMN2'
+`floatunsMN2'
Convert unsigned integer operand 1 (valid for fixed point mode M)
to floating point mode N and store in operand 0 (which has mode N).
-'fixMN2'
+`fixMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
mode N as a signed number and store in operand 0 (which has mode
N). This instruction's result is defined only when the value of
operand 1 is an integer.
If the machine description defines this pattern, it also needs to
- define the 'ftrunc' pattern.
+ define the `ftrunc' pattern.
-'fixunsMN2'
+`fixunsMN2'
Convert operand 1 (valid for floating point mode M) to fixed point
- mode N as an unsigned number and store in operand 0 (which has mode
- N). This instruction's result is defined only when the value of
- operand 1 is an integer.
+ mode N as an unsigned number and store in operand 0 (which has
+ mode N). This instruction's result is defined only when the value
+ of operand 1 is an integer.
-'ftruncM2'
+`ftruncM2'
Convert operand 1 (valid for floating point mode M) to an integer
value, still represented in floating point mode M, and store it in
operand 0 (valid for floating point mode M).
-'fix_truncMN2'
- Like 'fixMN2' but works for any floating point value of mode M by
+`fix_truncMN2'
+ Like `fixMN2' but works for any floating point value of mode M by
converting the value to an integer.
-'fixuns_truncMN2'
- Like 'fixunsMN2' but works for any floating point value of mode M
+`fixuns_truncMN2'
+ Like `fixunsMN2' but works for any floating point value of mode M
by converting the value to an integer.
-'truncMN2'
+`truncMN2'
Truncate operand 1 (valid for mode M) to mode N and store in
operand 0 (which has mode N). Both modes must be fixed point or
both floating point.
-'extendMN2'
+`extendMN2'
Sign-extend operand 1 (valid for mode M) to mode N and store in
operand 0 (which has mode N). Both modes must be fixed point or
both floating point.
-'zero_extendMN2'
+`zero_extendMN2'
Zero-extend operand 1 (valid for mode M) to mode N and store in
operand 0 (which has mode N). Both modes must be fixed point.
-'fractMN2'
- Convert operand 1 of mode M to mode N and store in operand 0 (which
- has mode N). Mode M and mode N could be fixed-point to
+`fractMN2'
+ Convert operand 1 of mode M to mode N and store in operand 0
+ (which has mode N). Mode M and mode N could be fixed-point to
fixed-point, signed integer to fixed-point, fixed-point to signed
integer, floating-point to fixed-point, or fixed-point to
floating-point. When overflows or underflows happen, the results
are undefined.
-'satfractMN2'
- Convert operand 1 of mode M to mode N and store in operand 0 (which
- has mode N). Mode M and mode N could be fixed-point to
+`satfractMN2'
+ Convert operand 1 of mode M to mode N and store in operand 0
+ (which has mode N). Mode M and mode N could be fixed-point to
fixed-point, signed integer to fixed-point, or floating-point to
fixed-point. When overflows or underflows happen, the instruction
saturates the results to the maximum or the minimum.
-'fractunsMN2'
- Convert operand 1 of mode M to mode N and store in operand 0 (which
- has mode N). Mode M and mode N could be unsigned integer to
- fixed-point, or fixed-point to unsigned integer. When overflows or
- underflows happen, the results are undefined.
+`fractunsMN2'
+ Convert operand 1 of mode M to mode N and store in operand 0
+ (which has mode N). Mode M and mode N could be unsigned integer
+ to fixed-point, or fixed-point to unsigned integer. When
+ overflows or underflows happen, the results are undefined.
-'satfractunsMN2'
+`satfractunsMN2'
Convert unsigned integer operand 1 of mode M to fixed-point mode N
and store in operand 0 (which has mode N). When overflows or
underflows happen, the instruction saturates the results to the
maximum or the minimum.
-'extvM'
+`extvM'
Extract a bit-field from register operand 1, sign-extend it, and
store it in operand 0. Operand 2 specifies the width of the field
in bits and operand 3 the starting bit, which counts from the most
- significant bit if 'BITS_BIG_ENDIAN' is true and from the least
+ significant bit if `BITS_BIG_ENDIAN' is true and from the least
significant bit otherwise.
Operands 0 and 1 both have mode M. Operands 2 and 3 have a
target-specific mode.
-'extvmisalignM'
+`extvmisalignM'
Extract a bit-field from memory operand 1, sign extend it, and
store it in operand 0. Operand 2 specifies the width in bits and
operand 3 the starting bit. The starting bit is always somewhere
- in the first byte of operand 1; it counts from the most significant
- bit if 'BITS_BIG_ENDIAN' is true and from the least significant bit
- otherwise.
+ in the first byte of operand 1; it counts from the most
+ significant bit if `BITS_BIG_ENDIAN' is true and from the least
+ significant bit otherwise.
- Operand 0 has mode M while operand 1 has 'BLK' mode. Operands 2
+ Operand 0 has mode M while operand 1 has `BLK' mode. Operands 2
and 3 have a target-specific mode.
The instruction must not read beyond the last byte of the
bit-field.
-'extzvM'
- Like 'extvM' except that the bit-field value is zero-extended.
+`extzvM'
+ Like `extvM' except that the bit-field value is zero-extended.
-'extzvmisalignM'
- Like 'extvmisalignM' except that the bit-field value is
+`extzvmisalignM'
+ Like `extvmisalignM' except that the bit-field value is
zero-extended.
-'insvM'
+`insvM'
Insert operand 3 into a bit-field of register operand 0. Operand 1
- specifies the width of the field in bits and operand 2 the starting
- bit, which counts from the most significant bit if
- 'BITS_BIG_ENDIAN' is true and from the least significant bit
+ specifies the width of the field in bits and operand 2 the
+ starting bit, which counts from the most significant bit if
+ `BITS_BIG_ENDIAN' is true and from the least significant bit
otherwise.
Operands 0 and 3 both have mode M. Operands 1 and 2 have a
target-specific mode.
-'insvmisalignM'
+`insvmisalignM'
Insert operand 3 into a bit-field of memory operand 0. Operand 1
- specifies the width of the field in bits and operand 2 the starting
- bit. The starting bit is always somewhere in the first byte of
- operand 0; it counts from the most significant bit if
- 'BITS_BIG_ENDIAN' is true and from the least significant bit
+ specifies the width of the field in bits and operand 2 the
+ starting bit. The starting bit is always somewhere in the first
+ byte of operand 0; it counts from the most significant bit if
+ `BITS_BIG_ENDIAN' is true and from the least significant bit
otherwise.
- Operand 3 has mode M while operand 0 has 'BLK' mode. Operands 1
+ Operand 3 has mode M while operand 0 has `BLK' mode. Operands 1
and 2 have a target-specific mode.
The instruction must not read or write beyond the last byte of the
bit-field.
-'extv'
+`extv'
Extract a bit-field from operand 1 (a register or memory operand),
where operand 2 specifies the width in bits and operand 3 the
starting bit, and store it in operand 0. Operand 0 must have mode
- 'word_mode'. Operand 1 may have mode 'byte_mode' or 'word_mode';
- often 'word_mode' is allowed only for registers. Operands 2 and 3
- must be valid for 'word_mode'.
+ `word_mode'. Operand 1 may have mode `byte_mode' or `word_mode';
+ often `word_mode' is allowed only for registers. Operands 2 and 3
+ must be valid for `word_mode'.
The RTL generation pass generates this instruction only with
constants for operands 2 and 3 and the constant is never zero for
@@ -23599,103 +23978,103 @@ pattern to accomplish a certain task.
The bit-field value is sign-extended to a full word integer before
it is stored in operand 0.
- This pattern is deprecated; please use 'extvM' and 'extvmisalignM'
+ This pattern is deprecated; please use `extvM' and `extvmisalignM'
instead.
-'extzv'
- Like 'extv' except that the bit-field value is zero-extended.
+`extzv'
+ Like `extv' except that the bit-field value is zero-extended.
- This pattern is deprecated; please use 'extzvM' and
- 'extzvmisalignM' instead.
+ This pattern is deprecated; please use `extzvM' and
+ `extzvmisalignM' instead.
-'insv'
- Store operand 3 (which must be valid for 'word_mode') into a
- bit-field in operand 0, where operand 1 specifies the width in bits
- and operand 2 the starting bit. Operand 0 may have mode
- 'byte_mode' or 'word_mode'; often 'word_mode' is allowed only for
- registers. Operands 1 and 2 must be valid for 'word_mode'.
+`insv'
+ Store operand 3 (which must be valid for `word_mode') into a
+ bit-field in operand 0, where operand 1 specifies the width in
+ bits and operand 2 the starting bit. Operand 0 may have mode
+ `byte_mode' or `word_mode'; often `word_mode' is allowed only for
+ registers. Operands 1 and 2 must be valid for `word_mode'.
The RTL generation pass generates this instruction only with
constants for operands 1 and 2 and the constant is never zero for
operand 1.
- This pattern is deprecated; please use 'insvM' and 'insvmisalignM'
+ This pattern is deprecated; please use `insvM' and `insvmisalignM'
instead.
-'movMODEcc'
+`movMODEcc'
Conditionally move operand 2 or operand 3 into operand 0 according
- to the comparison in operand 1. If the comparison is true, operand
- 2 is moved into operand 0, otherwise operand 3 is moved.
+ to the comparison in operand 1. If the comparison is true,
+ operand 2 is moved into operand 0, otherwise operand 3 is moved.
- The mode of the operands being compared need not be the same as the
- operands being moved. Some machines, sparc64 for example, have
- instructions that conditionally move an integer value based on the
- floating point condition codes and vice versa.
+ The mode of the operands being compared need not be the same as
+ the operands being moved. Some machines, sparc64 for example,
+ have instructions that conditionally move an integer value based
+ on the floating point condition codes and vice versa.
If the machine does not have conditional move instructions, do not
define these patterns.
-'addMODEcc'
- Similar to 'movMODEcc' but for conditional addition. Conditionally
- move operand 2 or (operands 2 + operand 3) into operand 0 according
- to the comparison in operand 1. If the comparison is false,
- operand 2 is moved into operand 0, otherwise (operand 2 + operand
- 3) is moved.
+`addMODEcc'
+ Similar to `movMODEcc' but for conditional addition. Conditionally
+ move operand 2 or (operands 2 + operand 3) into operand 0
+ according to the comparison in operand 1. If the comparison is
+ false, operand 2 is moved into operand 0, otherwise (operand 2 +
+ operand 3) is moved.
-'cstoreMODE4'
+`cstoreMODE4'
Store zero or nonzero in operand 0 according to whether a
- comparison is true. Operand 1 is a comparison operator. Operand 2
- and operand 3 are the first and second operand of the comparison,
- respectively. You specify the mode that operand 0 must have when
- you write the 'match_operand' expression. The compiler
- automatically sees which mode you have used and supplies an operand
- of that mode.
+ comparison is true. Operand 1 is a comparison operator. Operand
+ 2 and operand 3 are the first and second operand of the
+ comparison, respectively. You specify the mode that operand 0
+ must have when you write the `match_operand' expression. The
+ compiler automatically sees which mode you have used and supplies
+ an operand of that mode.
The value stored for a true condition must have 1 as its low bit,
or else must be negative. Otherwise the instruction is not
suitable and you should omit it from the machine description. You
describe to the compiler exactly which value is stored by defining
- the macro 'STORE_FLAG_VALUE' (*note Misc::). If a description
+ the macro `STORE_FLAG_VALUE' (*note Misc::). If a description
cannot be found that can be used for all the possible comparison
- operators, you should pick one and use a 'define_expand' to map all
- results onto the one you chose.
+ operators, you should pick one and use a `define_expand' to map
+ all results onto the one you chose.
- These operations may 'FAIL', but should do so only in relatively
- uncommon cases; if they would 'FAIL' for common cases involving
+ These operations may `FAIL', but should do so only in relatively
+ uncommon cases; if they would `FAIL' for common cases involving
integer comparisons, it is best to restrict the predicates to not
allow these operands. Likewise if a given comparison operator will
- always fail, independent of the operands (for floating-point modes,
- the 'ordered_comparison_operator' predicate is often useful in this
- case).
+ always fail, independent of the operands (for floating-point
+ modes, the `ordered_comparison_operator' predicate is often useful
+ in this case).
If this pattern is omitted, the compiler will generate a
conditional branch--for example, it may copy a constant one to the
- target and branching around an assignment of zero to the target--or
- a libcall. If the predicate for operand 1 only rejects some
- operators, it will also try reordering the operands and/or
- inverting the result value (e.g. by an exclusive OR). These
+ target and branching around an assignment of zero to the
+ target--or a libcall. If the predicate for operand 1 only rejects
+ some operators, it will also try reordering the operands and/or
+ inverting the result value (e.g. by an exclusive OR). These
possibilities could be cheaper or equivalent to the instructions
- used for the 'cstoreMODE4' pattern followed by those required to
- convert a positive result from 'STORE_FLAG_VALUE' to 1; in this
+ used for the `cstoreMODE4' pattern followed by those required to
+ convert a positive result from `STORE_FLAG_VALUE' to 1; in this
case, you can and should make operand 1's predicate reject some
- operators in the 'cstoreMODE4' pattern, or remove the pattern
+ operators in the `cstoreMODE4' pattern, or remove the pattern
altogether from the machine description.
-'cbranchMODE4'
+`cbranchMODE4'
Conditional branch instruction combined with a compare instruction.
Operand 0 is a comparison operator. Operand 1 and operand 2 are
the first and second operands of the comparison, respectively.
- Operand 3 is a 'label_ref' that refers to the label to jump to.
+ Operand 3 is a `label_ref' that refers to the label to jump to.
-'jump'
+`jump'
A jump inside a function; an unconditional branch. Operand 0 is
- the 'label_ref' of the label to jump to. This pattern name is
+ the `label_ref' of the label to jump to. This pattern name is
mandatory on all machines.
-'call'
+`call'
Subroutine call instruction returning no value. Operand 0 is the
function to call; operand 1 is the number of bytes of arguments
- pushed as a 'const_int'; operand 2 is the number of registers used
+ pushed as a `const_int'; operand 2 is the number of registers used
as operands.
On most machines, operand 2 is not actually stored into the RTL
@@ -23703,78 +24082,79 @@ pattern to accomplish a certain task.
need to put this information into the assembler code; they can put
it in the RTL instead of operand 1.
- Operand 0 should be a 'mem' RTX whose address is the address of the
- function. Note, however, that this address can be a 'symbol_ref'
+ Operand 0 should be a `mem' RTX whose address is the address of the
+ function. Note, however, that this address can be a `symbol_ref'
expression even if it would not be a legitimate memory address on
the target machine. If it is also not a valid argument for a call
instruction, the pattern for this operation should be a
- 'define_expand' (*note Expander Definitions::) that places the
+ `define_expand' (*note Expander Definitions::) that places the
address into a register and uses that register in the call
instruction.
-'call_value'
+`call_value'
Subroutine call instruction returning a value. Operand 0 is the
hard register in which the value is returned. There are three more
- operands, the same as the three operands of the 'call' instruction
+ operands, the same as the three operands of the `call' instruction
(but with numbers increased by one).
- Subroutines that return 'BLKmode' objects use the 'call' insn.
+ Subroutines that return `BLKmode' objects use the `call' insn.
-'call_pop', 'call_value_pop'
- Similar to 'call' and 'call_value', except used if defined and if
- 'RETURN_POPS_ARGS' is nonzero. They should emit a 'parallel' that
- contains both the function call and a 'set' to indicate the
+`call_pop', `call_value_pop'
+ Similar to `call' and `call_value', except used if defined and if
+ `RETURN_POPS_ARGS' is nonzero. They should emit a `parallel' that
+ contains both the function call and a `set' to indicate the
adjustment made to the frame pointer.
- For machines where 'RETURN_POPS_ARGS' can be nonzero, the use of
+ For machines where `RETURN_POPS_ARGS' can be nonzero, the use of
these patterns increases the number of functions for which the
frame pointer can be eliminated, if desired.
-'untyped_call'
- Subroutine call instruction returning a value of any type. Operand
- 0 is the function to call; operand 1 is a memory location where the
- result of calling the function is to be stored; operand 2 is a
- 'parallel' expression where each element is a 'set' expression that
- indicates the saving of a function return value into the result
- block.
+`untyped_call'
+ Subroutine call instruction returning a value of any type.
+ Operand 0 is the function to call; operand 1 is a memory location
+ where the result of calling the function is to be stored; operand
+ 2 is a `parallel' expression where each element is a `set'
+ expression that indicates the saving of a function return value
+ into the result block.
This instruction pattern should be defined to support
- '__builtin_apply' on machines where special instructions are needed
+ `__builtin_apply' on machines where special instructions are needed
to call a subroutine with arbitrary arguments or to save the value
returned. This instruction pattern is required on machines that
have multiple registers that can hold a return value (i.e.
- 'FUNCTION_VALUE_REGNO_P' is true for more than one register).
+ `FUNCTION_VALUE_REGNO_P' is true for more than one register).
-'return'
+`return'
Subroutine return instruction. This instruction pattern name
should be defined only if a single instruction can do all the work
of returning from a function.
- Like the 'movM' patterns, this pattern is also used after the RTL
+ Like the `movM' patterns, this pattern is also used after the RTL
generation phase. In this case it is to support machines where
- multiple instructions are usually needed to return from a function,
- but some class of functions only requires one instruction to
- implement a return. Normally, the applicable functions are those
- which do not need to save any registers or allocate stack space.
+ multiple instructions are usually needed to return from a
+ function, but some class of functions only requires one
+ instruction to implement a return. Normally, the applicable
+ functions are those which do not need to save any registers or
+ allocate stack space.
It is valid for this pattern to expand to an instruction using
- 'simple_return' if no epilogue is required.
+ `simple_return' if no epilogue is required.
-'simple_return'
+`simple_return'
Subroutine return instruction. This instruction pattern name
should be defined only if a single instruction can do all the work
of returning from a function on a path where no epilogue is
- required. This pattern is very similar to the 'return' instruction
- pattern, but it is emitted only by the shrink-wrapping optimization
- on paths where the function prologue has not been executed, and a
- function return should occur without any of the effects of the
- epilogue. Additional uses may be introduced on paths where both
- the prologue and the epilogue have executed.
+ required. This pattern is very similar to the `return'
+ instruction pattern, but it is emitted only by the shrink-wrapping
+ optimization on paths where the function prologue has not been
+ executed, and a function return should occur without any of the
+ effects of the epilogue. Additional uses may be introduced on
+ paths where both the prologue and the epilogue have executed.
For such machines, the condition specified in this pattern should
- only be true when 'reload_completed' is nonzero and the function's
+ only be true when `reload_completed' is nonzero and the function's
epilogue would only be a single instruction. For machines with
- register windows, the routine 'leaf_function_p' may be used to
+ register windows, the routine `leaf_function_p' may be used to
determine if a register window push is required.
Machines that have conditional return instructions should define
@@ -23791,33 +24171,33 @@ pattern to accomplish a certain task.
"...")
where CONDITION would normally be the same condition specified on
- the named 'return' pattern.
+ the named `return' pattern.
-'untyped_return'
+`untyped_return'
Untyped subroutine return instruction. This instruction pattern
- should be defined to support '__builtin_return' on machines where
+ should be defined to support `__builtin_return' on machines where
special instructions are needed to return a value of any type.
Operand 0 is a memory location where the result of calling a
- function with '__builtin_apply' is stored; operand 1 is a
- 'parallel' expression where each element is a 'set' expression that
- indicates the restoring of a function return value from the result
- block.
+ function with `__builtin_apply' is stored; operand 1 is a
+ `parallel' expression where each element is a `set' expression
+ that indicates the restoring of a function return value from the
+ result block.
-'nop'
+`nop'
No-op instruction. This instruction pattern name should always be
- defined to output a no-op in assembler code. '(const_int 0)' will
+ defined to output a no-op in assembler code. `(const_int 0)' will
do as an RTL pattern.
-'indirect_jump'
+`indirect_jump'
An instruction to jump to an address which is operand zero. This
pattern name is mandatory on all machines.
-'casesi'
+`casesi'
Instruction to jump through a dispatch table, including bounds
checking. This instruction takes five operands:
- 1. The index to dispatch on, which has mode 'SImode'.
+ 1. The index to dispatch on, which has mode `SImode'.
2. The lower bound for indices in the table, an integer constant.
@@ -23829,65 +24209,66 @@ pattern to accomplish a certain task.
5. A label to jump to if the index has a value outside the
bounds.
- The table is an 'addr_vec' or 'addr_diff_vec' inside of a
- 'jump_table_data'. The number of elements in the table is one plus
- the difference between the upper bound and the lower bound.
+ The table is an `addr_vec' or `addr_diff_vec' inside of a
+ `jump_table_data'. The number of elements in the table is one
+ plus the difference between the upper bound and the lower bound.
-'tablejump'
+`tablejump'
Instruction to jump to a variable address. This is a low-level
capability which can be used to implement a dispatch table when
- there is no 'casesi' pattern.
+ there is no `casesi' pattern.
This pattern requires two operands: the address or offset, and a
label which should immediately precede the jump table. If the
- macro 'CASE_VECTOR_PC_RELATIVE' evaluates to a nonzero value then
- the first operand is an offset which counts from the address of the
- table; otherwise, it is an absolute address to jump to. In either
- case, the first operand has mode 'Pmode'.
-
- The 'tablejump' insn is always the last insn before the jump table
- it uses. Its assembler code normally has no need to use the second
- operand, but you should incorporate it in the RTL pattern so that
- the jump optimizer will not delete the table as unreachable code.
-
-'decrement_and_branch_until_zero'
- Conditional branch instruction that decrements a register and jumps
- if the register is nonzero. Operand 0 is the register to decrement
- and test; operand 1 is the label to jump to if the register is
- nonzero. *Note Looping Patterns::.
+ macro `CASE_VECTOR_PC_RELATIVE' evaluates to a nonzero value then
+ the first operand is an offset which counts from the address of
+ the table; otherwise, it is an absolute address to jump to. In
+ either case, the first operand has mode `Pmode'.
+
+ The `tablejump' insn is always the last insn before the jump table
+ it uses. Its assembler code normally has no need to use the
+ second operand, but you should incorporate it in the RTL pattern so
+ that the jump optimizer will not delete the table as unreachable
+ code.
+
+`decrement_and_branch_until_zero'
+ Conditional branch instruction that decrements a register and
+ jumps if the register is nonzero. Operand 0 is the register to
+ decrement and test; operand 1 is the label to jump to if the
+ register is nonzero. *Note Looping Patterns::.
This optional instruction pattern is only used by the combiner,
typically for loops reversed by the loop optimizer when strength
reduction is enabled.
-'doloop_end'
- Conditional branch instruction that decrements a register and jumps
- if the register is nonzero. Operand 0 is the register to decrement
- and test; operand 1 is the label to jump to if the register is
- nonzero. *Note Looping Patterns::.
+`doloop_end'
+ Conditional branch instruction that decrements a register and
+ jumps if the register is nonzero. Operand 0 is the register to
+ decrement and test; operand 1 is the label to jump to if the
+ register is nonzero. *Note Looping Patterns::.
This optional instruction pattern should be defined for machines
with low-overhead looping instructions as the loop optimizer will
try to modify suitable loops to utilize it. The target hook
- 'TARGET_CAN_USE_DOLOOP_P' controls the conditions under which
+ `TARGET_CAN_USE_DOLOOP_P' controls the conditions under which
low-overhead loops can be used.
-'doloop_begin'
- Companion instruction to 'doloop_end' required for machines that
+`doloop_begin'
+ Companion instruction to `doloop_end' required for machines that
need to perform some initialization, such as loading a special
- counter register. Operand 1 is the associated 'doloop_end' pattern
- and operand 0 is the register that it decrements.
+ counter register. Operand 1 is the associated `doloop_end'
+ pattern and operand 0 is the register that it decrements.
If initialization insns do not always need to be emitted, use a
- 'define_expand' (*note Expander Definitions::) and make it fail.
+ `define_expand' (*note Expander Definitions::) and make it fail.
-'canonicalize_funcptr_for_compare'
+`canonicalize_funcptr_for_compare'
Canonicalize the function pointer in operand 1 and store the result
into operand 0.
- Operand 0 is always a 'reg' and has mode 'Pmode'; operand 1 may be
- a 'reg', 'mem', 'symbol_ref', 'const_int', etc and also has mode
- 'Pmode'.
+ Operand 0 is always a `reg' and has mode `Pmode'; operand 1 may be
+ a `reg', `mem', `symbol_ref', `const_int', etc and also has mode
+ `Pmode'.
Canonicalization of a function pointer usually involves computing
the address of the function which would be called if the function
@@ -23897,37 +24278,38 @@ pattern to accomplish a certain task.
can have different values but still call the same function when
used in an indirect call.
-'save_stack_block'
-'save_stack_function'
-'save_stack_nonlocal'
-'restore_stack_block'
-'restore_stack_function'
-'restore_stack_nonlocal'
+`save_stack_block'
+`save_stack_function'
+`save_stack_nonlocal'
+`restore_stack_block'
+`restore_stack_function'
+`restore_stack_nonlocal'
Most machines save and restore the stack pointer by copying it to
- or from an object of mode 'Pmode'. Do not define these patterns on
+ or from an object of mode `Pmode'. Do not define these patterns on
such machines.
Some machines require special handling for stack pointer saves and
restores. On those machines, define the patterns corresponding to
- the non-standard cases by using a 'define_expand' (*note Expander
+ the non-standard cases by using a `define_expand' (*note Expander
Definitions::) that produces the required insns. The three types
of saves and restores are:
- 1. 'save_stack_block' saves the stack pointer at the start of a
+ 1. `save_stack_block' saves the stack pointer at the start of a
block that allocates a variable-sized object, and
- 'restore_stack_block' restores the stack pointer when the
+ `restore_stack_block' restores the stack pointer when the
block is exited.
- 2. 'save_stack_function' and 'restore_stack_function' do a
- similar job for the outermost block of a function and are used
- when the function allocates variable-sized objects or calls
- 'alloca'. Only the epilogue uses the restored stack pointer,
- allowing a simpler save or restore sequence on some machines.
+ 2. `save_stack_function' and `restore_stack_function' do a
+ similar job for the outermost block of a function and are
+ used when the function allocates variable-sized objects or
+ calls `alloca'. Only the epilogue uses the restored stack
+ pointer, allowing a simpler save or restore sequence on some
+ machines.
- 3. 'save_stack_nonlocal' is used in functions that contain labels
+ 3. `save_stack_nonlocal' is used in functions that contain labels
branched to by nested functions. It saves the stack pointer
in such a way that the inner function can use
- 'restore_stack_nonlocal' to restore the stack pointer. The
+ `restore_stack_nonlocal' to restore the stack pointer. The
compiler generates code to restore the frame and argument
pointer registers, but some machines require saving and
restoring additional data such as register window information
@@ -23935,29 +24317,29 @@ pattern to accomplish a certain task.
and restore any such required data.
When saving the stack pointer, operand 0 is the save area and
- operand 1 is the stack pointer. The mode used to allocate the save
- area defaults to 'Pmode' but you can override that choice by
- defining the 'STACK_SAVEAREA_MODE' macro (*note Storage Layout::).
- You must specify an integral mode, or 'VOIDmode' if no save area is
- needed for a particular type of save (either because no save is
+ operand 1 is the stack pointer. The mode used to allocate the
+ save area defaults to `Pmode' but you can override that choice by
+ defining the `STACK_SAVEAREA_MODE' macro (*note Storage Layout::).
+ You must specify an integral mode, or `VOIDmode' if no save area
+ is needed for a particular type of save (either because no save is
needed or because a machine-specific save area can be used).
Operand 0 is the stack pointer and operand 1 is the save area for
- restore operations. If 'save_stack_block' is defined, operand 0
- must not be 'VOIDmode' since these saves can be arbitrarily nested.
+ restore operations. If `save_stack_block' is defined, operand 0
+ must not be `VOIDmode' since these saves can be arbitrarily nested.
- A save area is a 'mem' that is at a constant offset from
- 'virtual_stack_vars_rtx' when the stack pointer is saved for use by
- nonlocal gotos and a 'reg' in the other two cases.
+ A save area is a `mem' that is at a constant offset from
+ `virtual_stack_vars_rtx' when the stack pointer is saved for use by
+ nonlocal gotos and a `reg' in the other two cases.
-'allocate_stack'
- Subtract (or add if 'STACK_GROWS_DOWNWARD' is undefined) operand 1
+`allocate_stack'
+ Subtract (or add if `STACK_GROWS_DOWNWARD' is undefined) operand 1
from the stack pointer to create space for dynamically allocated
data.
Store the resultant pointer to this space into operand 0. If you
are allocating space from the main stack, do this by emitting a
- move insn to copy 'virtual_stack_dynamic_rtx' to operand 0. If you
- are allocating the space elsewhere, generate code to copy the
+ move insn to copy `virtual_stack_dynamic_rtx' to operand 0. If
+ you are allocating the space elsewhere, generate code to copy the
location of the space to operand 0. In the latter case, you must
ensure this space gets freed when the corresponding space on the
main stack is free.
@@ -23967,7 +24349,7 @@ pattern to accomplish a certain task.
probes or maintaining the back chain. Define this pattern to emit
those operations in addition to updating the stack pointer.
-'check_stack'
+`check_stack'
If stack checking (*note Stack Checking::) cannot be done on your
system by probing the stack, define this pattern to perform the
needed check and signal an error if the stack has overflowed. The
@@ -23976,14 +24358,14 @@ pattern to accomplish a certain task.
platforms where this pattern is needed, you would obtain the stack
limit from a global or thread-specific variable or register.
-'probe_stack_address'
+`probe_stack_address'
If stack checking (*note Stack Checking::) can be done on your
- system by probing the stack but without the need to actually access
- it, define this pattern and signal an error if the stack has
- overflowed. The single operand is the memory address in the stack
- that needs to be probed.
+ system by probing the stack but without the need to actually
+ access it, define this pattern and signal an error if the stack
+ has overflowed. The single operand is the memory address in the
+ stack that needs to be probed.
-'probe_stack'
+`probe_stack'
If stack checking (*note Stack Checking::) can be done on your
system by probing the stack but doing it with a "store zero"
instruction is not valid or optimal, define this pattern to do the
@@ -23991,7 +24373,7 @@ pattern to accomplish a certain task.
overflowed. The single operand is the memory reference in the
stack that needs to be probed.
-'nonlocal_goto'
+`nonlocal_goto'
Emit code to generate a non-local goto, e.g., a jump from one
function to a label in an outer function. This pattern has four
arguments, each representing a value to be used in the jump. The
@@ -24004,40 +24386,42 @@ pattern to accomplish a certain task.
On most machines you need not define this pattern, since GCC will
already generate the correct code, which is to load the frame
pointer and static chain, restore the stack (using the
- 'restore_stack_nonlocal' pattern, if defined), and jump indirectly
+ `restore_stack_nonlocal' pattern, if defined), and jump indirectly
to the dispatcher. You need only define this pattern if this code
will not work on your machine.
-'nonlocal_goto_receiver'
+`nonlocal_goto_receiver'
This pattern, if defined, contains code needed at the target of a
nonlocal goto after the code already generated by GCC. You will
- not normally need to define this pattern. A typical reason why you
- might need this pattern is if some value, such as a pointer to a
- global table, must be restored when the frame pointer is restored.
- Note that a nonlocal goto only occurs within a unit-of-translation,
- so a global table pointer that is shared by all functions of a
- given module need not be restored. There are no arguments.
-
-'exception_receiver'
+ not normally need to define this pattern. A typical reason why
+ you might need this pattern is if some value, such as a pointer to
+ a global table, must be restored when the frame pointer is
+ restored. Note that a nonlocal goto only occurs within a
+ unit-of-translation, so a global table pointer that is shared by
+ all functions of a given module need not be restored. There are
+ no arguments.
+
+`exception_receiver'
This pattern, if defined, contains code needed at the site of an
- exception handler that isn't needed at the site of a nonlocal goto.
- You will not normally need to define this pattern. A typical
- reason why you might need this pattern is if some value, such as a
- pointer to a global table, must be restored after control flow is
- branched to the handler of an exception. There are no arguments.
-
-'builtin_setjmp_setup'
+ exception handler that isn't needed at the site of a nonlocal
+ goto. You will not normally need to define this pattern. A
+ typical reason why you might need this pattern is if some value,
+ such as a pointer to a global table, must be restored after
+ control flow is branched to the handler of an exception. There
+ are no arguments.
+
+`builtin_setjmp_setup'
This pattern, if defined, contains additional code needed to
- initialize the 'jmp_buf'. You will not normally need to define
+ initialize the `jmp_buf'. You will not normally need to define
this pattern. A typical reason why you might need this pattern is
if some value, such as a pointer to a global table, must be
restored. Though it is preferred that the pointer value be
recalculated if possible (given the address of a label for
- instance). The single argument is a pointer to the 'jmp_buf'.
+ instance). The single argument is a pointer to the `jmp_buf'.
Note that the buffer is five words long and that the first three
are normally used by the generic mechanism.
-'builtin_setjmp_receiver'
+`builtin_setjmp_receiver'
This pattern, if defined, contains code needed at the site of a
built-in setjmp that isn't needed at the site of a nonlocal goto.
You will not normally need to define this pattern. A typical
@@ -24047,84 +24431,84 @@ pattern to accomplish a certain task.
control; this pattern may be emitted at a small offset from that
label.
-'builtin_longjmp'
+`builtin_longjmp'
This pattern, if defined, performs the entire action of the
longjmp. You will not normally need to define this pattern unless
- you also define 'builtin_setjmp_setup'. The single argument is a
- pointer to the 'jmp_buf'.
+ you also define `builtin_setjmp_setup'. The single argument is a
+ pointer to the `jmp_buf'.
-'eh_return'
- This pattern, if defined, affects the way '__builtin_eh_return',
+`eh_return'
+ This pattern, if defined, affects the way `__builtin_eh_return',
and thence the call frame exception handling library routines, are
built. It is intended to handle non-trivial actions needed along
the abnormal return path.
The address of the exception handler to which the function should
- return is passed as operand to this pattern. It will normally need
- to copied by the pattern to some special register or memory
+ return is passed as operand to this pattern. It will normally
+ need to copied by the pattern to some special register or memory
location. If the pattern needs to determine the location of the
target call frame in order to do so, it may use
- 'EH_RETURN_STACKADJ_RTX', if defined; it will have already been
+ `EH_RETURN_STACKADJ_RTX', if defined; it will have already been
assigned.
If this pattern is not defined, the default action will be to
- simply copy the return address to 'EH_RETURN_HANDLER_RTX'. Either
+ simply copy the return address to `EH_RETURN_HANDLER_RTX'. Either
that macro or this pattern needs to be defined if call frame
exception handling is to be used.
-'prologue'
+`prologue'
This pattern, if defined, emits RTL for entry to a function. The
function entry is responsible for setting up the stack frame,
initializing the frame pointer register, saving callee saved
registers, etc.
Using a prologue pattern is generally preferred over defining
- 'TARGET_ASM_FUNCTION_PROLOGUE' to emit assembly code for the
+ `TARGET_ASM_FUNCTION_PROLOGUE' to emit assembly code for the
prologue.
- The 'prologue' pattern is particularly useful for targets which
+ The `prologue' pattern is particularly useful for targets which
perform instruction scheduling.
-'window_save'
- This pattern, if defined, emits RTL for a register window save. It
- should be defined if the target machine has register windows but
- the window events are decoupled from calls to subroutines. The
- canonical example is the SPARC architecture.
+`window_save'
+ This pattern, if defined, emits RTL for a register window save.
+ It should be defined if the target machine has register windows
+ but the window events are decoupled from calls to subroutines.
+ The canonical example is the SPARC architecture.
-'epilogue'
- This pattern emits RTL for exit from a function. The function exit
- is responsible for deallocating the stack frame, restoring callee
- saved registers and emitting the return instruction.
+`epilogue'
+ This pattern emits RTL for exit from a function. The function
+ exit is responsible for deallocating the stack frame, restoring
+ callee saved registers and emitting the return instruction.
Using an epilogue pattern is generally preferred over defining
- 'TARGET_ASM_FUNCTION_EPILOGUE' to emit assembly code for the
+ `TARGET_ASM_FUNCTION_EPILOGUE' to emit assembly code for the
epilogue.
- The 'epilogue' pattern is particularly useful for targets which
+ The `epilogue' pattern is particularly useful for targets which
perform instruction scheduling or which have delay slots for their
return instruction.
-'sibcall_epilogue'
+`sibcall_epilogue'
This pattern, if defined, emits RTL for exit from a function
without the final branch back to the calling function. This
pattern will be emitted before any sibling call (aka tail call)
sites.
- The 'sibcall_epilogue' pattern must not clobber any arguments used
+ The `sibcall_epilogue' pattern must not clobber any arguments used
for parameter passing or any stack slots for arguments passed to
the current function.
-'trap'
+`trap'
This pattern, if defined, signals an error, typically by causing
some kind of signal to be raised. Among other places, it is used
- by the Java front end to signal 'invalid array index' exceptions.
+ by the Java front end to signal `invalid array index' exceptions.
-'ctrapMM4'
+`ctrapMM4'
Conditional trap instruction. Operand 0 is a piece of RTL which
performs a comparison, and operands 1 and 2 are the arms of the
comparison. Operand 3 is the trap code, an integer.
- A typical 'ctrap' pattern looks like
+ A typical `ctrap' pattern looks like
(define_insn "ctrapsi4"
[(trap_if (match_operator 0 "trap_operator"
@@ -24134,36 +24518,36 @@ pattern to accomplish a certain task.
""
"...")
-'prefetch'
+`prefetch'
This pattern, if defined, emits code for a non-faulting data
prefetch instruction. Operand 0 is the address of the memory to
prefetch. Operand 1 is a constant 1 if the prefetch is preparing
for a write to the memory address, or a constant 0 otherwise.
Operand 2 is the expected degree of temporal locality of the data
and is a value between 0 and 3, inclusive; 0 means that the data
- has no temporal locality, so it need not be left in the cache after
- the access; 3 means that the data has a high degree of temporal
- locality and should be left in all levels of cache possible; 1 and
- 2 mean, respectively, a low or moderate degree of temporal
- locality.
+ has no temporal locality, so it need not be left in the cache
+ after the access; 3 means that the data has a high degree of
+ temporal locality and should be left in all levels of cache
+ possible; 1 and 2 mean, respectively, a low or moderate degree of
+ temporal locality.
Targets that do not support write prefetches or locality hints can
ignore the values of operands 1 and 2.
-'blockage'
+`blockage'
This pattern defines a pseudo insn that prevents the instruction
scheduler and other passes from moving instructions and using
register equivalences across the boundary defined by the blockage
insn. This needs to be an UNSPEC_VOLATILE pattern or a volatile
ASM.
-'memory_barrier'
+`memory_barrier'
If the target memory model is not fully synchronous, then this
pattern should be defined to an instruction that orders both loads
and stores before the instruction with respect to loads and stores
after the instruction. This pattern has no operands.
-'sync_compare_and_swapMODE'
+`sync_compare_and_swapMODE'
This pattern, if defined, emits code for an atomic compare-and-swap
operation. Operand 1 is the memory on which the atomic operation
is performed. Operand 2 is the "old" value to be compared against
@@ -24184,28 +24568,28 @@ pattern to accomplish a certain task.
For targets where the success or failure of the compare-and-swap
operation is available via the status flags, it is possible to
avoid a separate compare operation and issue the subsequent branch
- or store-flag operation immediately after the compare-and-swap. To
- this end, GCC will look for a 'MODE_CC' set in the output of
- 'sync_compare_and_swapMODE'; if the machine description includes
- such a set, the target should also define special 'cbranchcc4'
- and/or 'cstorecc4' instructions. GCC will then be able to take the
- destination of the 'MODE_CC' set and pass it to the 'cbranchcc4' or
- 'cstorecc4' pattern as the first operand of the comparison (the
- second will be '(const_int 0)').
+ or store-flag operation immediately after the compare-and-swap.
+ To this end, GCC will look for a `MODE_CC' set in the output of
+ `sync_compare_and_swapMODE'; if the machine description includes
+ such a set, the target should also define special `cbranchcc4'
+ and/or `cstorecc4' instructions. GCC will then be able to take
+ the destination of the `MODE_CC' set and pass it to the
+ `cbranchcc4' or `cstorecc4' pattern as the first operand of the
+ comparison (the second will be `(const_int 0)').
For targets where the operating system may provide support for this
- operation via library calls, the 'sync_compare_and_swap_optab' may
+ operation via library calls, the `sync_compare_and_swap_optab' may
be initialized to a function with the same interface as the
- '__sync_val_compare_and_swap_N' built-in. If the entire set of
+ `__sync_val_compare_and_swap_N' built-in. If the entire set of
__SYNC builtins are supported via library calls, the target can
- initialize all of the optabs at once with 'init_sync_libfuncs'.
- For the purposes of C++11 'std::atomic::is_lock_free', it is
+ initialize all of the optabs at once with `init_sync_libfuncs'.
+ For the purposes of C++11 `std::atomic::is_lock_free', it is
assumed that these library calls do _not_ use any kind of
interruptable locking.
-'sync_addMODE', 'sync_subMODE'
-'sync_iorMODE', 'sync_andMODE'
-'sync_xorMODE', 'sync_nandMODE'
+`sync_addMODE', `sync_subMODE'
+`sync_iorMODE', `sync_andMODE'
+`sync_xorMODE', `sync_nandMODE'
These patterns emit code for an atomic operation on memory.
Operand 0 is the memory on which the atomic operation is performed.
Operand 1 is the second operand to the binary operator.
@@ -24218,9 +24602,9 @@ pattern to accomplish a certain task.
If these patterns are not defined, the operation will be
constructed from a compare-and-swap operation, if defined.
-'sync_old_addMODE', 'sync_old_subMODE'
-'sync_old_iorMODE', 'sync_old_andMODE'
-'sync_old_xorMODE', 'sync_old_nandMODE'
+`sync_old_addMODE', `sync_old_subMODE'
+`sync_old_iorMODE', `sync_old_andMODE'
+`sync_old_xorMODE', `sync_old_nandMODE'
These patterns emit code for an atomic operation on memory, and
return the value that the memory contained before the operation.
Operand 0 is the result value, operand 1 is the memory on which the
@@ -24235,18 +24619,18 @@ pattern to accomplish a certain task.
If these patterns are not defined, the operation will be
constructed from a compare-and-swap operation, if defined.
-'sync_new_addMODE', 'sync_new_subMODE'
-'sync_new_iorMODE', 'sync_new_andMODE'
-'sync_new_xorMODE', 'sync_new_nandMODE'
- These patterns are like their 'sync_old_OP' counterparts, except
- that they return the value that exists in the memory location after
- the operation, rather than before the operation.
+`sync_new_addMODE', `sync_new_subMODE'
+`sync_new_iorMODE', `sync_new_andMODE'
+`sync_new_xorMODE', `sync_new_nandMODE'
+ These patterns are like their `sync_old_OP' counterparts, except
+ that they return the value that exists in the memory location
+ after the operation, rather than before the operation.
-'sync_lock_test_and_setMODE'
+`sync_lock_test_and_setMODE'
This pattern takes two forms, based on the capabilities of the
target. In either case, operand 0 is the result of the operand,
- operand 1 is the memory on which the atomic operation is performed,
- and operand 2 is the value to set in the lock.
+ operand 1 is the memory on which the atomic operation is
+ performed, and operand 2 is the value to set in the lock.
In the ideal case, this operation is an atomic exchange operation,
in which the previous value in memory operand is copied into the
@@ -24254,11 +24638,11 @@ pattern to accomplish a certain task.
operand.
For less capable targets, any value operand that is not the
- constant 1 should be rejected with 'FAIL'. In this case the target
- may use an atomic test-and-set bit operation. The result operand
- should contain 1 if the bit was previously set and 0 if the bit was
- previously clear. The true contents of the memory operand are
- implementation defined.
+ constant 1 should be rejected with `FAIL'. In this case the
+ target may use an atomic test-and-set bit operation. The result
+ operand should contain 1 if the bit was previously set and 0 if
+ the bit was previously clear. The true contents of the memory
+ operand are implementation defined.
This pattern must issue any memory barrier instructions such that
the pattern as a whole acts as an acquire barrier, that is all
@@ -24268,41 +24652,41 @@ pattern to accomplish a certain task.
If this pattern is not defined, the operation will be constructed
from a compare-and-swap operation, if defined.
-'sync_lock_releaseMODE'
+`sync_lock_releaseMODE'
This pattern, if defined, releases a lock set by
- 'sync_lock_test_and_setMODE'. Operand 0 is the memory that
+ `sync_lock_test_and_setMODE'. Operand 0 is the memory that
contains the lock; operand 1 is the value to store in the lock.
If the target doesn't implement full semantics for
- 'sync_lock_test_and_setMODE', any value operand which is not the
- constant 0 should be rejected with 'FAIL', and the true contents of
- the memory operand are implementation defined.
+ `sync_lock_test_and_setMODE', any value operand which is not the
+ constant 0 should be rejected with `FAIL', and the true contents
+ of the memory operand are implementation defined.
This pattern must issue any memory barrier instructions such that
the pattern as a whole acts as a release barrier, that is the lock
is released only after all previous memory operations have
completed.
- If this pattern is not defined, then a 'memory_barrier' pattern
+ If this pattern is not defined, then a `memory_barrier' pattern
will be emitted, followed by a store of the value to the memory
operand.
-'atomic_compare_and_swapMODE'
+`atomic_compare_and_swapMODE'
This pattern, if defined, emits code for an atomic compare-and-swap
operation with memory model semantics. Operand 2 is the memory on
which the atomic operation is performed. Operand 0 is an output
operand which is set to true or false based on whether the
operation succeeded. Operand 1 is an output operand which is set
to the contents of the memory before the operation was attempted.
- Operand 3 is the value that is expected to be in memory. Operand 4
- is the value to put in memory if the expected value is found there.
- Operand 5 is set to 1 if this compare and swap is to be treated as
- a weak operation. Operand 6 is the memory model to be used if the
- operation is a success. Operand 7 is the memory model to be used
- if the operation fails.
-
- If memory referred to in operand 2 contains the value in operand 3,
- then operand 4 is stored in memory pointed to by operand 2 and
+ Operand 3 is the value that is expected to be in memory. Operand
+ 4 is the value to put in memory if the expected value is found
+ there. Operand 5 is set to 1 if this compare and swap is to be
+ treated as a weak operation. Operand 6 is the memory model to be
+ used if the operation is a success. Operand 7 is the memory model
+ to be used if the operation fails.
+
+ If memory referred to in operand 2 contains the value in operand
+ 3, then operand 4 is stored in memory pointed to by operand 2 and
fencing based on the memory model in operand 6 is issued.
If memory referred to in operand 2 does not contain the value in
@@ -24314,109 +24698,109 @@ pattern to accomplish a certain task.
operand 5 can be ignored. Note a strong implementation must be
provided.
- If this pattern is not provided, the '__atomic_compare_exchange'
- built-in functions will utilize the legacy 'sync_compare_and_swap'
- pattern with an '__ATOMIC_SEQ_CST' memory model.
+ If this pattern is not provided, the `__atomic_compare_exchange'
+ built-in functions will utilize the legacy `sync_compare_and_swap'
+ pattern with an `__ATOMIC_SEQ_CST' memory model.
-'atomic_loadMODE'
+`atomic_loadMODE'
This pattern implements an atomic load operation with memory model
semantics. Operand 1 is the memory address being loaded from.
- Operand 0 is the result of the load. Operand 2 is the memory model
- to be used for the load operation.
+ Operand 0 is the result of the load. Operand 2 is the memory
+ model to be used for the load operation.
- If not present, the '__atomic_load' built-in function will either
+ If not present, the `__atomic_load' built-in function will either
resort to a normal load with memory barriers, or a compare-and-swap
operation if a normal load would not be atomic.
-'atomic_storeMODE'
+`atomic_storeMODE'
This pattern implements an atomic store operation with memory model
semantics. Operand 0 is the memory address being stored to.
Operand 1 is the value to be written. Operand 2 is the memory
model to be used for the operation.
- If not present, the '__atomic_store' built-in function will attempt
- to perform a normal store and surround it with any required memory
- fences. If the store would not be atomic, then an
- '__atomic_exchange' is attempted with the result being ignored.
+ If not present, the `__atomic_store' built-in function will
+ attempt to perform a normal store and surround it with any
+ required memory fences. If the store would not be atomic, then an
+ `__atomic_exchange' is attempted with the result being ignored.
-'atomic_exchangeMODE'
+`atomic_exchangeMODE'
This pattern implements an atomic exchange operation with memory
- model semantics. Operand 1 is the memory location the operation is
- performed on. Operand 0 is an output operand which is set to the
- original value contained in the memory pointed to by operand 1.
- Operand 2 is the value to be stored. Operand 3 is the memory model
- to be used.
+ model semantics. Operand 1 is the memory location the operation
+ is performed on. Operand 0 is an output operand which is set to
+ the original value contained in the memory pointed to by operand
+ 1. Operand 2 is the value to be stored. Operand 3 is the memory
+ model to be used.
If this pattern is not present, the built-in function
- '__atomic_exchange' will attempt to preform the operation with a
+ `__atomic_exchange' will attempt to preform the operation with a
compare and swap loop.
-'atomic_addMODE', 'atomic_subMODE'
-'atomic_orMODE', 'atomic_andMODE'
-'atomic_xorMODE', 'atomic_nandMODE'
+`atomic_addMODE', `atomic_subMODE'
+`atomic_orMODE', `atomic_andMODE'
+`atomic_xorMODE', `atomic_nandMODE'
These patterns emit code for an atomic operation on memory with
- memory model semantics. Operand 0 is the memory on which the
+ memory model semantics. Operand 0 is the memory on which the
atomic operation is performed. Operand 1 is the second operand to
the binary operator. Operand 2 is the memory model to be used by
the operation.
If these patterns are not defined, attempts will be made to use
- legacy 'sync' patterns, or equivalent patterns which return a
+ legacy `sync' patterns, or equivalent patterns which return a
result. If none of these are available a compare-and-swap loop
will be used.
-'atomic_fetch_addMODE', 'atomic_fetch_subMODE'
-'atomic_fetch_orMODE', 'atomic_fetch_andMODE'
-'atomic_fetch_xorMODE', 'atomic_fetch_nandMODE'
+`atomic_fetch_addMODE', `atomic_fetch_subMODE'
+`atomic_fetch_orMODE', `atomic_fetch_andMODE'
+`atomic_fetch_xorMODE', `atomic_fetch_nandMODE'
These patterns emit code for an atomic operation on memory with
- memory model semantics, and return the original value. Operand 0
+ memory model semantics, and return the original value. Operand 0
is an output operand which contains the value of the memory
location before the operation was performed. Operand 1 is the
memory on which the atomic operation is performed. Operand 2 is
- the second operand to the binary operator. Operand 3 is the memory
- model to be used by the operation.
+ the second operand to the binary operator. Operand 3 is the
+ memory model to be used by the operation.
If these patterns are not defined, attempts will be made to use
- legacy 'sync' patterns. If none of these are available a
+ legacy `sync' patterns. If none of these are available a
compare-and-swap loop will be used.
-'atomic_add_fetchMODE', 'atomic_sub_fetchMODE'
-'atomic_or_fetchMODE', 'atomic_and_fetchMODE'
-'atomic_xor_fetchMODE', 'atomic_nand_fetchMODE'
+`atomic_add_fetchMODE', `atomic_sub_fetchMODE'
+`atomic_or_fetchMODE', `atomic_and_fetchMODE'
+`atomic_xor_fetchMODE', `atomic_nand_fetchMODE'
These patterns emit code for an atomic operation on memory with
- memory model semantics and return the result after the operation is
- performed. Operand 0 is an output operand which contains the value
- after the operation. Operand 1 is the memory on which the atomic
- operation is performed. Operand 2 is the second operand to the
- binary operator. Operand 3 is the memory model to be used by the
- operation.
+ memory model semantics and return the result after the operation
+ is performed. Operand 0 is an output operand which contains the
+ value after the operation. Operand 1 is the memory on which the
+ atomic operation is performed. Operand 2 is the second operand to
+ the binary operator. Operand 3 is the memory model to be used by
+ the operation.
If these patterns are not defined, attempts will be made to use
- legacy 'sync' patterns, or equivalent patterns which return the
+ legacy `sync' patterns, or equivalent patterns which return the
result before the operation followed by the arithmetic operation
required to produce the result. If none of these are available a
compare-and-swap loop will be used.
-'atomic_test_and_set'
- This pattern emits code for '__builtin_atomic_test_and_set'.
+`atomic_test_and_set'
+ This pattern emits code for `__builtin_atomic_test_and_set'.
Operand 0 is an output operand which is set to true if the previous
previous contents of the byte was "set", and false otherwise.
- Operand 1 is the 'QImode' memory to be modified. Operand 2 is the
+ Operand 1 is the `QImode' memory to be modified. Operand 2 is the
memory model to be used.
The specific value that defines "set" is implementation defined,
and is normally based on what is performed by the native atomic
test and set instruction.
-'mem_thread_fenceMODE'
+`mem_thread_fenceMODE'
This pattern emits code required to implement a thread fence with
memory model semantics. Operand 0 is the memory model to be used.
If this pattern is not specified, all memory models except
- '__ATOMIC_RELAXED' will result in issuing a 'sync_synchronize'
+ `__ATOMIC_RELAXED' will result in issuing a `sync_synchronize'
barrier pattern.
-'mem_signal_fenceMODE'
+`mem_signal_fenceMODE'
This pattern emits code required to implement a signal fence with
memory model semantics. Operand 0 is the memory model to be used.
@@ -24425,21 +24809,21 @@ pattern to accomplish a certain task.
barrier instructions.
If this pattern is not specified, all memory models except
- '__ATOMIC_RELAXED' will result in issuing a 'sync_synchronize'
+ `__ATOMIC_RELAXED' will result in issuing a `sync_synchronize'
barrier pattern.
-'get_thread_pointerMODE'
-'set_thread_pointerMODE'
+`get_thread_pointerMODE'
+`set_thread_pointerMODE'
These patterns emit code that reads/sets the TLS thread pointer.
Currently, these are only needed if the target needs to support the
- '__builtin_thread_pointer' and '__builtin_set_thread_pointer'
+ `__builtin_thread_pointer' and `__builtin_set_thread_pointer'
builtins.
The get/set patterns have a single output/input operand
- respectively, with MODE intended to be 'Pmode'.
+ respectively, with MODE intended to be `Pmode'.
-'stack_protect_set'
- This pattern, if defined, moves a 'ptr_mode' value from the memory
+`stack_protect_set'
+ This pattern, if defined, moves a `ptr_mode' value from the memory
in operand 1 to the memory in operand 0 without leaving the value
in a register afterward. This is to avoid leaking the value some
place that an attacker might use to rewrite the stack guard slot
@@ -24448,8 +24832,8 @@ pattern to accomplish a certain task.
If this pattern is not defined, then a plain move pattern is
generated.
-'stack_protect_test'
- This pattern, if defined, compares a 'ptr_mode' value from the
+`stack_protect_test'
+ This pattern, if defined, compares a `ptr_mode' value from the
memory in operand 1 with the memory in operand 0 without leaving
the value in a register afterward and branches to operand 2 if the
values were equal.
@@ -24457,13 +24841,14 @@ pattern to accomplish a certain task.
If this pattern is not defined, then a plain compare pattern and
conditional branch pattern is used.
-'clear_cache'
+`clear_cache'
This pattern, if defined, flushes the instruction cache for a
region of memory. The region is bounded to by the Pmode pointers
in operand 0 inclusive and operand 1 exclusive.
If this pattern is not defined, a call to the library function
- '__clear_cache' is used.
+ `__clear_cache' is used.
+

File: gccint.info, Node: Pattern Ordering, Next: Dependent Patterns, Prev: Standard Names, Up: Machine Desc
@@ -24477,16 +24862,17 @@ Therefore, more specific patterns (patterns that will match fewer
things) and faster instructions (those that will produce better code
when they do match) should usually go first in the description.
- In some cases the effect of ordering the patterns can be used to hide a
-pattern when it is not valid. For example, the 68000 has an instruction
-for converting a fullword to floating point and another for converting a
-byte to floating point. An instruction converting an integer to
-floating point could match either one. We put the pattern to convert
-the fullword first to make sure that one will be used rather than the
-other. (Otherwise a large integer might be generated as a single-byte
-immediate quantity, which would not work.) Instead of using this
-pattern ordering it would be possible to make the pattern for
-convert-a-byte smart enough to deal properly with any constant value.
+ In some cases the effect of ordering the patterns can be used to hide
+a pattern when it is not valid. For example, the 68000 has an
+instruction for converting a fullword to floating point and another for
+converting a byte to floating point. An instruction converting an
+integer to floating point could match either one. We put the pattern
+to convert the fullword first to make sure that one will be used rather
+than the other. (Otherwise a large integer might be generated as a
+single-byte immediate quantity, which would not work.) Instead of
+using this pattern ordering it would be possible to make the pattern
+for convert-a-byte smart enough to deal properly with any constant
+value.

File: gccint.info, Node: Dependent Patterns, Next: Jump Patterns, Prev: Pattern Ordering, Up: Machine Desc
@@ -24509,12 +24895,12 @@ Constant integers do not specify a machine mode, so an instruction to
extend a constant value could match either pattern. The pattern it
actually will match is the one that appears first in the file. For
correct results, this must be the one for the widest possible mode
-('HImode', here). If the pattern matches the 'QImode' instruction, the
+(`HImode', here). If the pattern matches the `QImode' instruction, the
results will be incorrect if the constant value does not actually fit
that mode.
- Such instructions to extend constants are rarely generated because they
-are optimized away, but they do occasionally happen in nonoptimized
+ Such instructions to extend constants are rarely generated because
+they are optimized away, but they do occasionally happen in nonoptimized
compilations.
If a constraint in a pattern allows a constant, the reload pass may
@@ -24533,28 +24919,29 @@ File: gccint.info, Node: Jump Patterns, Next: Looping Patterns, Prev: Depende
GCC does not assume anything about how the machine realizes jumps. The
machine description should define a single pattern, usually a
-'define_expand', which expands to all the required insns.
+`define_expand', which expands to all the required insns.
Usually, this would be a comparison insn to set the condition code and
a separate branch insn testing the condition code and branching or not
-according to its value. For many machines, however, separating compares
-and branches is limiting, which is why the more flexible approach with
-one 'define_expand' is used in GCC. The machine description becomes
-clearer for architectures that have compare-and-branch instructions but
-no condition code. It also works better when different sets of
-comparison operators are supported by different kinds of conditional
-branches (e.g. integer vs. floating-point), or by conditional branches
-with respect to conditional stores.
+according to its value. For many machines, however, separating
+compares and branches is limiting, which is why the more flexible
+approach with one `define_expand' is used in GCC. The machine
+description becomes clearer for architectures that have
+compare-and-branch instructions but no condition code. It also works
+better when different sets of comparison operators are supported by
+different kinds of conditional branches (e.g. integer vs.
+floating-point), or by conditional branches with respect to conditional
+stores.
Two separate insns are always used if the machine description
represents a condition code register using the legacy RTL expression
-'(cc0)', and on most machines that use a separate condition code
-register (*note Condition Code::). For machines that use '(cc0)', in
+`(cc0)', and on most machines that use a separate condition code
+register (*note Condition Code::). For machines that use `(cc0)', in
fact, the set and use of the condition code must be separate and
-adjacent(1), thus allowing flags in 'cc_status' to be used (*note
+adjacent(1), thus allowing flags in `cc_status' to be used (*note
Condition Code::) and so that the comparison and branch insns could be
-located from each other by using the functions 'prev_cc0_setter' and
-'next_cc0_user'.
+located from each other by using the functions `prev_cc0_setter' and
+`next_cc0_user'.
Even in this case having a single entry point for conditional branches
is advantageous, because it handles equally well the case where a single
@@ -24564,9 +24951,9 @@ distinct signed and unsigned flavors) as in the x86 or SPARC, and the
case where there are distinct signed and unsigned compare instructions
and only one set of conditional branch instructions as in the PowerPC.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) 'note' insns can separate them, though.
+ (1) `note' insns can separate them, though.

File: gccint.info, Node: Looping Patterns, Next: Insn Canonicalizations, Prev: Jump Patterns, Up: Machine Desc
@@ -24575,7 +24962,7 @@ File: gccint.info, Node: Looping Patterns, Next: Insn Canonicalizations, Prev
===========================================
Some machines have special jump instructions that can be utilized to
-make loops more efficient. A common example is the 68000 'dbra'
+make loops more efficient. A common example is the 68000 `dbra'
instruction which performs a decrement of a register and a branch if the
result was greater than zero. Other machines, in particular digital
signal processors (DSPs), have special block repeat instructions to
@@ -24583,20 +24970,20 @@ provide low-overhead loop support. For example, the TI TMS320C3x/C4x
DSPs have a block repeat instruction that loads special registers to
mark the top and end of a loop and to count the number of loop
iterations. This avoids the need for fetching and executing a
-'dbra'-like instruction and avoids pipeline stalls associated with the
+`dbra'-like instruction and avoids pipeline stalls associated with the
jump.
GCC has three special named patterns to support low overhead looping.
-They are 'decrement_and_branch_until_zero', 'doloop_begin', and
-'doloop_end'. The first pattern, 'decrement_and_branch_until_zero', is
+They are `decrement_and_branch_until_zero', `doloop_begin', and
+`doloop_end'. The first pattern, `decrement_and_branch_until_zero', is
not emitted during RTL generation but may be emitted during the
-instruction combination phase. This requires the assistance of the loop
-optimizer, using information collected during strength reduction, to
-reverse a loop to count down to zero. Some targets also require the
-loop optimizer to add a 'REG_NONNEG' note to indicate that the iteration
-count is always positive. This is needed if the target performs a
-signed loop termination test. For example, the 68000 uses a pattern
-similar to the following for its 'dbra' instruction:
+instruction combination phase. This requires the assistance of the
+loop optimizer, using information collected during strength reduction,
+to reverse a loop to count down to zero. Some targets also require the
+loop optimizer to add a `REG_NONNEG' note to indicate that the
+iteration count is always positive. This is needed if the target
+performs a signed loop termination test. For example, the 68000 uses a
+pattern similar to the following for its `dbra' instruction:
(define_insn "decrement_and_branch_until_zero"
[(set (pc)
@@ -24613,7 +25000,7 @@ similar to the following for its 'dbra' instruction:
"...")
Note that since the insn is both a jump insn and has an output, it must
-deal with its own reloads, hence the 'm' constraints. Also note that
+deal with its own reloads, hence the `m' constraints. Also note that
since this insn is generated by the instruction combination phase
combining two sequential insns together into an implicit parallel insn,
the iteration counter needs to be biased by the same amount as the
@@ -24633,35 +25020,36 @@ pattern will not be matched by the combiner.
"find_reg_note (insn, REG_NONNEG, 0)"
"...")
- The other two special looping patterns, 'doloop_begin' and
-'doloop_end', are emitted by the loop optimizer for certain well-behaved
-loops with a finite number of loop iterations using information
-collected during strength reduction.
+ The other two special looping patterns, `doloop_begin' and
+`doloop_end', are emitted by the loop optimizer for certain
+well-behaved loops with a finite number of loop iterations using
+information collected during strength reduction.
- The 'doloop_end' pattern describes the actual looping instruction (or
-the implicit looping operation) and the 'doloop_begin' pattern is an
+ The `doloop_end' pattern describes the actual looping instruction (or
+the implicit looping operation) and the `doloop_begin' pattern is an
optional companion pattern that can be used for initialization needed
for some low-overhead looping instructions.
Note that some machines require the actual looping instruction to be
emitted at the top of the loop (e.g., the TMS320C3x/C4x DSPs). Emitting
the true RTL for a looping instruction at the top of the loop can cause
-problems with flow analysis. So instead, a dummy 'doloop' insn is
+problems with flow analysis. So instead, a dummy `doloop' insn is
emitted at the end of the loop. The machine dependent reorg pass checks
-for the presence of this 'doloop' insn and then searches back to the top
-of the loop, where it inserts the true looping insn (provided there are
-no instructions in the loop which would cause problems). Any additional
-labels can be emitted at this point. In addition, if the desired
-special iteration counter register was not allocated, this machine
-dependent reorg pass could emit a traditional compare and jump
+for the presence of this `doloop' insn and then searches back to the
+top of the loop, where it inserts the true looping insn (provided there
+are no instructions in the loop which would cause problems). Any
+additional labels can be emitted at this point. In addition, if the
+desired special iteration counter register was not allocated, this
+machine dependent reorg pass could emit a traditional compare and jump
instruction pair.
- The essential difference between the 'decrement_and_branch_until_zero'
-and the 'doloop_end' patterns is that the loop optimizer allocates an
-additional pseudo register for the latter as an iteration counter. This
-pseudo register cannot be used within the loop (i.e., general induction
-variables cannot be derived from it), however, in many cases the loop
-induction variable may become redundant and removed by the flow pass.
+ The essential difference between the `decrement_and_branch_until_zero'
+and the `doloop_end' patterns is that the loop optimizer allocates an
+additional pseudo register for the latter as an iteration counter.
+This pseudo register cannot be used within the loop (i.e., general
+induction variables cannot be derived from it), however, in many cases
+the loop induction variable may become redundant and removed by the
+flow pass.

File: gccint.info, Node: Insn Canonicalizations, Next: Expander Definitions, Prev: Looping Patterns, Up: Machine Desc
@@ -24679,44 +25067,45 @@ number of insn patterns required.
In addition to algebraic simplifications, following canonicalizations
are performed:
- * For commutative and comparison operators, a constant is always made
- the second operand. If a machine only supports a constant as the
- second operand, only patterns that match a constant in the second
- operand need be supplied.
+ * For commutative and comparison operators, a constant is always
+ made the second operand. If a machine only supports a constant as
+ the second operand, only patterns that match a constant in the
+ second operand need be supplied.
* For associative operators, a sequence of operators will always
chain to the left; for instance, only the left operand of an
- integer 'plus' can itself be a 'plus'. 'and', 'ior', 'xor',
- 'plus', 'mult', 'smin', 'smax', 'umin', and 'umax' are associative
+ integer `plus' can itself be a `plus'. `and', `ior', `xor',
+ `plus', `mult', `smin', `smax', `umin', and `umax' are associative
when applied to integers, and sometimes to floating-point.
- * For these operators, if only one operand is a 'neg', 'not', 'mult',
- 'plus', or 'minus' expression, it will be the first operand.
+ * For these operators, if only one operand is a `neg', `not',
+ `mult', `plus', or `minus' expression, it will be the first
+ operand.
- * In combinations of 'neg', 'mult', 'plus', and 'minus', the 'neg'
+ * In combinations of `neg', `mult', `plus', and `minus', the `neg'
operations (if any) will be moved inside the operations as far as
- possible. For instance, '(neg (mult A B))' is canonicalized as
- '(mult (neg A) B)', but '(plus (mult (neg B) C) A)' is
- canonicalized as '(minus A (mult B C))'.
+ possible. For instance, `(neg (mult A B))' is canonicalized as
+ `(mult (neg A) B)', but `(plus (mult (neg B) C) A)' is
+ canonicalized as `(minus A (mult B C))'.
- * For the 'compare' operator, a constant is always the second operand
- if the first argument is a condition code register or '(cc0)'.
+ * For the `compare' operator, a constant is always the second operand
+ if the first argument is a condition code register or `(cc0)'.
- * An operand of 'neg', 'not', 'mult', 'plus', or 'minus' is made the
+ * An operand of `neg', `not', `mult', `plus', or `minus' is made the
first operand under the same conditions as above.
- * '(ltu (plus A B) B)' is converted to '(ltu (plus A B) A)'.
- Likewise with 'geu' instead of 'ltu'.
+ * `(ltu (plus A B) B)' is converted to `(ltu (plus A B) A)'.
+ Likewise with `geu' instead of `ltu'.
- * '(minus X (const_int N))' is converted to '(plus X (const_int
+ * `(minus X (const_int N))' is converted to `(plus X (const_int
-N))'.
- * Within address computations (i.e., inside 'mem'), a left shift is
+ * Within address computations (i.e., inside `mem'), a left shift is
converted into the appropriate multiplication by a power of two.
* De Morgan's Law is used to move bitwise negation inside a bitwise
logical-and or logical-or operation. If this results in only one
- operand being a 'not' expression, it will be the first one.
+ operand being a `not' expression, it will be the first one.
A machine that has an instruction that performs a bitwise
logical-and of one operand with the bitwise negation of the other
@@ -24742,7 +25131,7 @@ are performed:
logically equivalent RTL expressions.
* The only possible RTL expressions involving both bitwise
- exclusive-or and bitwise negation are '(xor:M X Y)' and '(not:M
+ exclusive-or and bitwise negation are `(xor:M X Y)' and `(not:M
(xor:M X Y))'.
* The sum of three items, one of which is a constant, will only
@@ -24750,24 +25139,25 @@ are performed:
(plus:M (plus:M X Y) CONSTANT)
- * Equality comparisons of a group of bits (usually a single bit) with
- zero will be written using 'zero_extract' rather than the
- equivalent 'and' or 'sign_extract' operations.
+ * Equality comparisons of a group of bits (usually a single bit)
+ with zero will be written using `zero_extract' rather than the
+ equivalent `and' or `sign_extract' operations.
- * '(sign_extend:M1 (mult:M2 (sign_extend:M2 X) (sign_extend:M2 Y)))'
- is converted to '(mult:M1 (sign_extend:M1 X) (sign_extend:M1 Y))',
- and likewise for 'zero_extend'.
+ * `(sign_extend:M1 (mult:M2 (sign_extend:M2 X) (sign_extend:M2 Y)))'
+ is converted to `(mult:M1 (sign_extend:M1 X) (sign_extend:M1 Y))',
+ and likewise for `zero_extend'.
+
+ * `(sign_extend:M1 (mult:M2 (ashiftrt:M2 X S) (sign_extend:M2 Y)))'
+ is converted to `(mult:M1 (sign_extend:M1 (ashiftrt:M2 X S))
+ (sign_extend:M1 Y))', and likewise for patterns using
+ `zero_extend' and `lshiftrt'. If the second operand of `mult' is
+ also a shift, then that is extended also. This transformation is
+ only applied when it can be proven that the original operation had
+ sufficient precision to prevent overflow.
- * '(sign_extend:M1 (mult:M2 (ashiftrt:M2 X S) (sign_extend:M2 Y)))'
- is converted to '(mult:M1 (sign_extend:M1 (ashiftrt:M2 X S))
- (sign_extend:M1 Y))', and likewise for patterns using 'zero_extend'
- and 'lshiftrt'. If the second operand of 'mult' is also a shift,
- then that is extended also. This transformation is only applied
- when it can be proven that the original operation had sufficient
- precision to prevent overflow.
Further canonicalization rules are defined in the function
-'commutative_operand_precedence' in 'gcc/rtlanal.c'.
+`commutative_operand_precedence' in `gcc/rtlanal.c'.

File: gccint.info, Node: Expander Definitions, Next: Insn Splitting, Prev: Insn Canonicalizations, Up: Machine Desc
@@ -24778,30 +25168,30 @@ File: gccint.info, Node: Expander Definitions, Next: Insn Splitting, Prev: In
On some target machines, some standard pattern names for RTL generation
cannot be handled with single insn, but a sequence of RTL insns can
represent them. For these target machines, you can write a
-'define_expand' to specify how to generate the sequence of RTL.
+`define_expand' to specify how to generate the sequence of RTL.
- A 'define_expand' is an RTL expression that looks almost like a
-'define_insn'; but, unlike the latter, a 'define_expand' is used only
+ A `define_expand' is an RTL expression that looks almost like a
+`define_insn'; but, unlike the latter, a `define_expand' is used only
for RTL generation and it can produce more than one RTL insn.
- A 'define_expand' RTX has four operands:
+ A `define_expand' RTX has four operands:
- * The name. Each 'define_expand' must have a name, since the only
+ * The name. Each `define_expand' must have a name, since the only
use for it is to refer to it by name.
* The RTL template. This is a vector of RTL expressions representing
- a sequence of separate instructions. Unlike 'define_insn', there
- is no implicit surrounding 'PARALLEL'.
-
- * The condition, a string containing a C expression. This expression
- is used to express how the availability of this pattern depends on
- subclasses of target machine, selected by command-line options when
- GCC is run. This is just like the condition of a 'define_insn'
- that has a standard name. Therefore, the condition (if present)
- may not depend on the data in the insn being matched, but only the
- target-machine-type flags. The compiler needs to test these
- conditions during initialization in order to learn exactly which
- named instructions are available in a particular run.
+ a sequence of separate instructions. Unlike `define_insn', there
+ is no implicit surrounding `PARALLEL'.
+
+ * The condition, a string containing a C expression. This
+ expression is used to express how the availability of this pattern
+ depends on subclasses of target machine, selected by command-line
+ options when GCC is run. This is just like the condition of a
+ `define_insn' that has a standard name. Therefore, the condition
+ (if present) may not depend on the data in the insn being matched,
+ but only the target-machine-type flags. The compiler needs to
+ test these conditions during initialization in order to learn
+ exactly which named instructions are available in a particular run.
* The preparation statements, a string containing zero or more C
statements which are to be executed before RTL code is generated
@@ -24809,14 +25199,14 @@ for RTL generation and it can produce more than one RTL insn.
Usually these statements prepare temporary registers for use as
internal operands in the RTL template, but they can also generate
- RTL insns directly by calling routines such as 'emit_insn', etc.
+ RTL insns directly by calling routines such as `emit_insn', etc.
Any such insns precede the ones that come from the RTL template.
- * Optionally, a vector containing the values of attributes. *Note
+ * Optionally, a vector containing the values of attributes. *Note
Insn Attributes::.
- Every RTL insn emitted by a 'define_expand' must match some
-'define_insn' in the machine description. Otherwise, the compiler will
+ Every RTL insn emitted by a `define_expand' must match some
+`define_insn' in the machine description. Otherwise, the compiler will
crash when trying to generate code for the insn or trying to optimize
it.
@@ -24825,51 +25215,51 @@ also describes the operands that need to be specified when this pattern
is used. In particular, it gives a predicate for each operand.
A true operand, which needs to be specified in order to generate RTL
-from the pattern, should be described with a 'match_operand' in its
+from the pattern, should be described with a `match_operand' in its
first occurrence in the RTL template. This enters information on the
operand's predicate into the tables that record such things. GCC uses
the information to preload the operand into a register if that is
required for valid RTL code. If the operand is referred to more than
-once, subsequent references should use 'match_dup'.
+once, subsequent references should use `match_dup'.
The RTL template may also refer to internal "operands" which are
temporary registers or labels used only within the sequence made by the
-'define_expand'. Internal operands are substituted into the RTL
-template with 'match_dup', never with 'match_operand'. The values of
+`define_expand'. Internal operands are substituted into the RTL
+template with `match_dup', never with `match_operand'. The values of
the internal operands are not passed in as arguments by the compiler
-when it requests use of this pattern. Instead, they are computed within
-the pattern, in the preparation statements. These statements compute
-the values and store them into the appropriate elements of 'operands' so
-that 'match_dup' can find them.
+when it requests use of this pattern. Instead, they are computed
+within the pattern, in the preparation statements. These statements
+compute the values and store them into the appropriate elements of
+`operands' so that `match_dup' can find them.
There are two special macros defined for use in the preparation
-statements: 'DONE' and 'FAIL'. Use them with a following semicolon, as
+statements: `DONE' and `FAIL'. Use them with a following semicolon, as
a statement.
-'DONE'
- Use the 'DONE' macro to end RTL generation for the pattern. The
+`DONE'
+ Use the `DONE' macro to end RTL generation for the pattern. The
only RTL insns resulting from the pattern on this occasion will be
- those already emitted by explicit calls to 'emit_insn' within the
+ those already emitted by explicit calls to `emit_insn' within the
preparation statements; the RTL template will not be generated.
-'FAIL'
+`FAIL'
Make the pattern fail on this occasion. When a pattern fails, it
means that the pattern was not truly available. The calling
routines in the compiler will try other strategies for code
generation using other patterns.
Failure is currently supported only for binary (addition,
- multiplication, shifting, etc.) and bit-field ('extv', 'extzv',
- and 'insv') operations.
+ multiplication, shifting, etc.) and bit-field (`extv', `extzv',
+ and `insv') operations.
- If the preparation falls through (invokes neither 'DONE' nor 'FAIL'),
-then the 'define_expand' acts like a 'define_insn' in that the RTL
+ If the preparation falls through (invokes neither `DONE' nor `FAIL'),
+then the `define_expand' acts like a `define_insn' in that the RTL
template is used to generate the insn.
The RTL template is not used for matching, only for generating the
-initial insn list. If the preparation statement always invokes 'DONE'
-or 'FAIL', the RTL template may be reduced to a simple list of operands,
-such as this example:
+initial insn list. If the preparation statement always invokes `DONE'
+or `FAIL', the RTL template may be reduced to a simple list of
+operands, such as this example:
(define_expand "addsi3"
[(match_operand:SI 0 "register_operand" "")
@@ -24898,16 +25288,16 @@ such as this example:
FAIL;
}")
-This example uses 'define_expand' so that it can generate an RTL insn
+This example uses `define_expand' so that it can generate an RTL insn
for shifting when the shift-count is in the supported range of 0 to 3
but fail in other cases where machine insns aren't available. When it
fails, the compiler tries another strategy using different patterns
(such as, a library call).
If the compiler were able to handle nontrivial condition-strings in
-patterns with names, then it would be possible to use a 'define_insn' in
-that case. Here is another case (zero-extension on the 68000) which
-makes more use of the power of 'define_expand':
+patterns with names, then it would be possible to use a `define_insn'
+in that case. Here is another case (zero-extension on the 68000) which
+makes more use of the power of `define_expand':
(define_expand "zero_extendhisi2"
[(set (match_operand:SI 0 "general_operand" "")
@@ -24924,16 +25314,16 @@ Here two RTL insns are generated, one to clear the entire output operand
and the other to copy the input operand into its low half. This
sequence is incorrect if the input operand refers to [the old value of]
the output operand, so the preparation statement makes sure this isn't
-so. The function 'make_safe_from' copies the 'operands[1]' into a
-temporary register if it refers to 'operands[0]'. It does this by
+so. The function `make_safe_from' copies the `operands[1]' into a
+temporary register if it refers to `operands[0]'. It does this by
emitting another RTL insn.
Finally, a third example shows the use of an internal operand.
-Zero-extension on the SPUR chip is done by 'and'-ing the result against
-a halfword mask. But this mask cannot be represented by a 'const_int'
+Zero-extension on the SPUR chip is done by `and'-ing the result against
+a halfword mask. But this mask cannot be represented by a `const_int'
because the constant value is too large to be legitimate on this
-machine. So it must be copied into a register with 'force_reg' and then
-the register used in the 'and'.
+machine. So it must be copied into a register with `force_reg' and
+then the register used in the `and'.
(define_expand "zero_extendhisi2"
[(set (match_operand:SI 0 "register_operand" "")
@@ -24945,10 +25335,10 @@ the register used in the 'and'.
"operands[2]
= force_reg (SImode, GEN_INT (65535)); ")
- _Note:_ If the 'define_expand' is used to serve a standard binary or
+ _Note:_ If the `define_expand' is used to serve a standard binary or
unary arithmetic operation or a bit-field operation, then the last insn
-it generates must not be a 'code_label', 'barrier' or 'note'. It must
-be an 'insn', 'jump_insn' or 'call_insn'. If you don't need a real insn
+it generates must not be a `code_label', `barrier' or `note'. It must
+be an `insn', `jump_insn' or `call_insn'. If you don't need a real insn
at the end, emit an insn to copy the result of the operation into
itself. Such an insn will generate no code, but it can avoid problems
in the compiler.
@@ -24959,12 +25349,12 @@ File: gccint.info, Node: Insn Splitting, Next: Including Patterns, Prev: Expa
16.16 Defining How to Split Instructions
========================================
-There are two cases where you should specify how to split a pattern into
-multiple insns. On machines that have instructions requiring delay
-slots (*note Delay Slots::) or that have instructions whose output is
-not available for multiple cycles (*note Processor pipeline
-description::), the compiler phases that optimize these cases need to be
-able to move insns into one-instruction delay slots. However, some
+There are two cases where you should specify how to split a pattern
+into multiple insns. On machines that have instructions requiring
+delay slots (*note Delay Slots::) or that have instructions whose
+output is not available for multiple cycles (*note Processor pipeline
+description::), the compiler phases that optimize these cases need to
+be able to move insns into one-instruction delay slots. However, some
insns may generate more than one machine instruction. These insns
cannot be placed into a delay slot.
@@ -24978,15 +25368,15 @@ scheduling.
The insn combiner phase also splits putative insns. If three insns are
merged into one insn with a complex expression that cannot be matched by
-some 'define_insn' pattern, the combiner phase attempts to split the
+some `define_insn' pattern, the combiner phase attempts to split the
complex pattern into two insns that are recognized. Usually it can
break the complex pattern into two patterns by splitting out some
subexpression. However, in some other cases, such as performing an
addition of a large constant in two insns on a RISC machine, the way to
split the addition into two insns is machine-dependent.
- The 'define_split' definition tells the compiler how to split a complex
-insn into several simpler insns. It looks like this:
+ The `define_split' definition tells the compiler how to split a
+complex insn into several simpler insns. It looks like this:
(define_split
[INSN-PATTERN]
@@ -24997,31 +25387,31 @@ insn into several simpler insns. It looks like this:
"PREPARATION-STATEMENTS")
INSN-PATTERN is a pattern that needs to be split and CONDITION is the
-final condition to be tested, as in a 'define_insn'. When an insn
+final condition to be tested, as in a `define_insn'. When an insn
matching INSN-PATTERN and satisfying CONDITION is found, it is replaced
in the insn list with the insns given by NEW-INSN-PATTERN-1,
NEW-INSN-PATTERN-2, etc.
The PREPARATION-STATEMENTS are similar to those statements that are
-specified for 'define_expand' (*note Expander Definitions::) and are
+specified for `define_expand' (*note Expander Definitions::) and are
executed before the new RTL is generated to prepare for the generated
code or emit some insns whose pattern is not fixed. Unlike those in
-'define_expand', however, these statements must not generate any new
+`define_expand', however, these statements must not generate any new
pseudo-registers. Once reload has completed, they also must not
allocate any space in the stack frame.
Patterns are matched against INSN-PATTERN in two different
circumstances. If an insn needs to be split for delay slot scheduling
or insn scheduling, the insn is already known to be valid, which means
-that it must have been matched by some 'define_insn' and, if
-'reload_completed' is nonzero, is known to satisfy the constraints of
-that 'define_insn'. In that case, the new insn patterns must also be
-insns that are matched by some 'define_insn' and, if 'reload_completed'
+that it must have been matched by some `define_insn' and, if
+`reload_completed' is nonzero, is known to satisfy the constraints of
+that `define_insn'. In that case, the new insn patterns must also be
+insns that are matched by some `define_insn' and, if `reload_completed'
is nonzero, must also satisfy the constraints of those definitions.
- As an example of this usage of 'define_split', consider the following
-example from 'a29k.md', which splits a 'sign_extend' from 'HImode' to
-'SImode' into a pair of shift insns:
+ As an example of this usage of `define_split', consider the following
+example from `a29k.md', which splits a `sign_extend' from `HImode' to
+`SImode' into a pair of shift insns:
(define_split
[(set (match_operand:SI 0 "gen_reg_operand" "")
@@ -25037,18 +25427,18 @@ example from 'a29k.md', which splits a 'sign_extend' from 'HImode' to
{ operands[1] = gen_lowpart (SImode, operands[1]); }")
When the combiner phase tries to split an insn pattern, it is always
-the case that the pattern is _not_ matched by any 'define_insn'. The
-combiner pass first tries to split a single 'set' expression and then
-the same 'set' expression inside a 'parallel', but followed by a
-'clobber' of a pseudo-reg to use as a scratch register. In these cases,
-the combiner expects exactly two new insn patterns to be generated. It
-will verify that these patterns match some 'define_insn' definitions, so
-you need not do this test in the 'define_split' (of course, there is no
-point in writing a 'define_split' that will never produce insns that
-match).
-
- Here is an example of this use of 'define_split', taken from
-'rs6000.md':
+the case that the pattern is _not_ matched by any `define_insn'. The
+combiner pass first tries to split a single `set' expression and then
+the same `set' expression inside a `parallel', but followed by a
+`clobber' of a pseudo-reg to use as a scratch register. In these
+cases, the combiner expects exactly two new insn patterns to be
+generated. It will verify that these patterns match some `define_insn'
+definitions, so you need not do this test in the `define_split' (of
+course, there is no point in writing a `define_split' that will never
+produce insns that match).
+
+ Here is an example of this use of `define_split', taken from
+`rs6000.md':
(define_split
[(set (match_operand:SI 0 "gen_reg_operand" "")
@@ -25069,10 +25459,10 @@ match).
operands[4] = GEN_INT (low);
}")
- Here the predicate 'non_add_cint_operand' matches any 'const_int' that
-is _not_ a valid operand of a single add insn. The add with the smaller
-displacement is written so that it can be substituted into the address
-of a subsequent operation.
+ Here the predicate `non_add_cint_operand' matches any `const_int' that
+is _not_ a valid operand of a single add insn. The add with the
+smaller displacement is written so that it can be substituted into the
+address of a subsequent operation.
An example that uses a scratch register, from the same file, generates
an equality comparison of a register and a large constant:
@@ -25101,9 +25491,9 @@ an equality comparison of a register and a large constant:
operands[5] = GEN_INT (sextc);
}")
- To avoid confusion, don't write a single 'define_split' that accepts
-some insns that match some 'define_insn' as well as some insns that
-don't. Instead, write two separate 'define_split' definitions, one for
+ To avoid confusion, don't write a single `define_split' that accepts
+some insns that match some `define_insn' as well as some insns that
+don't. Instead, write two separate `define_split' definitions, one for
the insns that are valid and one for the insns that are not valid.
The splitter is allowed to split jump instructions into sequence of
@@ -25116,16 +25506,16 @@ instruction is always valid, as compiler expect identical behavior of
new jump. When new sequence contains multiple jump instructions or new
labels, more assistance is needed. Splitter is required to create only
unconditional jumps, or simple conditional jump instructions.
-Additionally it must attach a 'REG_BR_PROB' note to each conditional
-jump. A global variable 'split_branch_probability' holds the
+Additionally it must attach a `REG_BR_PROB' note to each conditional
+jump. A global variable `split_branch_probability' holds the
probability of the original branch in case it was a simple conditional
jump, -1 otherwise. To simplify recomputing of edge frequencies, the
-new sequence is required to have only forward jumps to the newly created
-labels.
+new sequence is required to have only forward jumps to the newly
+created labels.
- For the common case where the pattern of a define_split exactly matches
-the pattern of a define_insn, use 'define_insn_and_split'. It looks
-like this:
+ For the common case where the pattern of a define_split exactly
+matches the pattern of a define_insn, use `define_insn_and_split'. It
+looks like this:
(define_insn_and_split
[INSN-PATTERN]
@@ -25138,12 +25528,11 @@ like this:
"PREPARATION-STATEMENTS"
[INSN-ATTRIBUTES])
-
INSN-PATTERN, CONDITION, OUTPUT-TEMPLATE, and INSN-ATTRIBUTES are used
-as in 'define_insn'. The NEW-INSN-PATTERN vector and the
-PREPARATION-STATEMENTS are used as in a 'define_split'. The
-SPLIT-CONDITION is also used as in 'define_split', with the additional
-behavior that if the condition starts with '&&', the condition used for
+as in `define_insn'. The NEW-INSN-PATTERN vector and the
+PREPARATION-STATEMENTS are used as in a `define_split'. The
+SPLIT-CONDITION is also used as in `define_split', with the additional
+behavior that if the condition starts with `&&', the condition used for
the split will be the constructed as a logical "and" of the split
condition with the insn condition. For example, from i386.md:
@@ -25160,14 +25549,13 @@ condition with the insn condition. For example, from i386.md:
""
[(set_attr "type" "alu1")])
-
In this case, the actual split condition will be
-'TARGET_ZERO_EXTEND_WITH_AND && !optimize_size && reload_completed'.
+`TARGET_ZERO_EXTEND_WITH_AND && !optimize_size && reload_completed'.
- The 'define_insn_and_split' construction provides exactly the same
-functionality as two separate 'define_insn' and 'define_split' patterns.
-It exists for compactness, and as a maintenance tool to prevent having
-to ensure the two patterns' templates match.
+ The `define_insn_and_split' construction provides exactly the same
+functionality as two separate `define_insn' and `define_split'
+patterns. It exists for compactness, and as a maintenance tool to
+prevent having to ensure the two patterns' templates match.

File: gccint.info, Node: Including Patterns, Next: Peephole Definitions, Prev: Insn Splitting, Up: Machine Desc
@@ -25175,8 +25563,8 @@ File: gccint.info, Node: Including Patterns, Next: Peephole Definitions, Prev
16.17 Including Patterns in Machine Descriptions.
=================================================
-The 'include' pattern tells the compiler tools where to look for
-patterns that are in files other than in the file '.md'. This is used
+The `include' pattern tells the compiler tools where to look for
+patterns that are in files other than in the file `.md'. This is used
only at build time and there is no preprocessing allowed.
It looks like:
@@ -25190,10 +25578,9 @@ only at build time and there is no preprocessing allowed.
(include "filestuff")
-
Where PATHNAME is a string that specifies the location of the file,
-specifies the include file to be in 'gcc/config/target/filestuff'. The
-directory 'gcc/config/target' is regarded as the default directory.
+specifies the include file to be in `gcc/config/target/filestuff'. The
+directory `gcc/config/target' is regarded as the default directory.
Machine descriptions may be split up into smaller more manageable
subsections and placed into subdirectories.
@@ -25203,31 +25590,28 @@ subsections and placed into subdirectories.
(include "BOGUS/filestuff")
-
the include file is specified to be in
-'gcc/config/TARGET/BOGUS/filestuff'.
+`gcc/config/TARGET/BOGUS/filestuff'.
Specifying an absolute path for the include file such as;
(include "/u2/BOGUS/filestuff")
-
is permitted but is not encouraged.
16.17.1 RTL Generation Tool Options for Directory Search
--------------------------------------------------------
-The '-IDIR' option specifies directories to search for machine
+The `-IDIR' option specifies directories to search for machine
descriptions. For example:
genrecog -I/p1/abc/proc1 -I/p2/abcd/pro2 target.md
-
Add the directory DIR to the head of the list of directories to be
searched for header files. This can be used to override a system
machine definition file, substituting your own version, since these
directories are searched before the default machine description file
-directories. If you use more than one '-I' option, the directories are
+directories. If you use more than one `-I' option, the directories are
scanned in left-to-right order; the standard default directory come
after.
@@ -25237,7 +25621,7 @@ File: gccint.info, Node: Peephole Definitions, Next: Insn Attributes, Prev: I
16.18 Machine-Specific Peephole Optimizers
==========================================
-In addition to instruction patterns the 'md' file may contain
+In addition to instruction patterns the `md' file may contain
definitions of machine-specific peephole optimizations.
The combiner does not notice certain peephole optimizations when the
@@ -25248,11 +25632,12 @@ computed in the first one. A machine-specific peephole optimizer can
detect such opportunities.
There are two forms of peephole definitions that may be used. The
-original 'define_peephole' is run at assembly output time to match insns
-and substitute assembly text. Use of 'define_peephole' is deprecated.
+original `define_peephole' is run at assembly output time to match
+insns and substitute assembly text. Use of `define_peephole' is
+deprecated.
- A newer 'define_peephole2' matches insns and substitutes new insns.
-The 'peephole2' pass is run after register allocation but before
+ A newer `define_peephole2' matches insns and substitutes new insns.
+The `peephole2' pass is run after register allocation but before
scheduling, which may result in much better code for targets that do
scheduling.
@@ -25279,7 +25664,7 @@ A definition looks like this:
The last string operand may be omitted if you are not using any
machine-specific information in this machine description. If present,
-it must obey the same rules as in a 'define_insn'.
+it must obey the same rules as in a `define_insn'.
In this skeleton, INSN-PATTERN-1 and so on are patterns to match
consecutive insns. The optimization applies to a sequence of insns when
@@ -25287,23 +25672,23 @@ INSN-PATTERN-1 matches the first one, INSN-PATTERN-2 matches the next,
and so on.
Each of the insns matched by a peephole must also match a
-'define_insn'. Peepholes are checked only at the last stage just before
-code generation, and only optionally. Therefore, any insn which would
-match a peephole but no 'define_insn' will cause a crash in code
+`define_insn'. Peepholes are checked only at the last stage just
+before code generation, and only optionally. Therefore, any insn which
+would match a peephole but no `define_insn' will cause a crash in code
generation in an unoptimized compilation, or at various optimization
stages.
- The operands of the insns are matched with 'match_operands',
-'match_operator', and 'match_dup', as usual. What is not usual is that
+ The operands of the insns are matched with `match_operands',
+`match_operator', and `match_dup', as usual. What is not usual is that
the operand numbers apply to all the insn patterns in the definition.
So, you can check for identical operands in two insns by using
-'match_operand' in one insn and 'match_dup' in the other.
+`match_operand' in one insn and `match_dup' in the other.
- The operand constraints used in 'match_operand' patterns do not have
-any direct effect on the applicability of the peephole, but they will be
-validated afterward, so make sure your constraints are general enough to
-apply whenever the peephole matches. If the peephole matches but the
-constraints are not satisfied, the compiler will crash.
+ The operand constraints used in `match_operand' patterns do not have
+any direct effect on the applicability of the peephole, but they will
+be validated afterward, so make sure your constraints are general enough
+to apply whenever the peephole matches. If the peephole matches but
+the constraints are not satisfied, the compiler will crash.
It is safe to omit constraints in all the operands of the peephole; or
you can write constraints which serve as a double-check on the criteria
@@ -25321,22 +25706,22 @@ allocation is complete. Therefore, the peephole definition can check
which operands have ended up in which kinds of registers, just by
looking at the operands.
- The way to refer to the operands in CONDITION is to write 'operands[I]'
-for operand number I (as matched by '(match_operand I ...)'). Use the
-variable 'insn' to refer to the last of the insns being matched; use
-'prev_active_insn' to find the preceding insns.
+ The way to refer to the operands in CONDITION is to write
+`operands[I]' for operand number I (as matched by `(match_operand I
+...)'). Use the variable `insn' to refer to the last of the insns
+being matched; use `prev_active_insn' to find the preceding insns.
When optimizing computations with intermediate results, you can use
CONDITION to match only when the intermediate results are not used
-elsewhere. Use the C expression 'dead_or_set_p (INSN, OP)', where INSN
+elsewhere. Use the C expression `dead_or_set_p (INSN, OP)', where INSN
is the insn in which you expect the value to be used for the last time
-(from the value of 'insn', together with use of 'prev_nonnote_insn'),
-and OP is the intermediate value (from 'operands[I]').
+(from the value of `insn', together with use of `prev_nonnote_insn'),
+and OP is the intermediate value (from `operands[I]').
Applying the optimization means replacing the sequence of insns with
one new insn. The TEMPLATE controls ultimate output of assembler code
for this combined insn. It works exactly like the template of a
-'define_insn'. Operand numbers in this template are the same ones used
+`define_insn'. Operand numbers in this template are the same ones used
in matching the original sequence of insns.
The result of a defined peephole optimizer does not need to match any
@@ -25384,13 +25769,14 @@ into
fmoved sp@+,fp0
INSN-PATTERN-1 and so on look _almost_ like the second operand of
-'define_insn'. There is one important difference: the second operand of
-'define_insn' consists of one or more RTX's enclosed in square brackets.
-Usually, there is only one: then the same action can be written as an
-element of a 'define_peephole'. But when there are multiple actions in
-a 'define_insn', they are implicitly enclosed in a 'parallel'. Then you
-must explicitly write the 'parallel', and the square brackets within it,
-in the 'define_peephole'. Thus, if an insn pattern looks like this,
+`define_insn'. There is one important difference: the second operand
+of `define_insn' consists of one or more RTX's enclosed in square
+brackets. Usually, there is only one: then the same action can be
+written as an element of a `define_peephole'. But when there are
+multiple actions in a `define_insn', they are implicitly enclosed in a
+`parallel'. Then you must explicitly write the `parallel', and the
+square brackets within it, in the `define_peephole'. Thus, if an insn
+pattern looks like this,
(define_insn "divmodsi4"
[(set (match_operand:SI 0 "general_operand" "=d")
@@ -25420,7 +25806,7 @@ File: gccint.info, Node: define_peephole2, Prev: define_peephole, Up: Peephol
16.18.2 RTL to RTL Peephole Optimizers
--------------------------------------
-The 'define_peephole2' definition tells the compiler how to substitute
+The `define_peephole2' definition tells the compiler how to substitute
one sequence of instructions for another sequence, what additional
scratch registers may be needed and what their lifetimes must be.
@@ -25434,7 +25820,7 @@ scratch registers may be needed and what their lifetimes must be.
...]
"PREPARATION-STATEMENTS")
- The definition is almost identical to 'define_split' (*note Insn
+ The definition is almost identical to `define_split' (*note Insn
Splitting::) except that the pattern to match is not a single
instruction, but a sequence of instructions.
@@ -25442,10 +25828,10 @@ instruction, but a sequence of instructions.
output template. If appropriate registers are not free, the pattern
will simply not match.
- Scratch registers are requested with a 'match_scratch' pattern at the
+ Scratch registers are requested with a `match_scratch' pattern at the
top level of the input pattern. The allocated register (initially) will
be dead at the point requested within the original sequence. If the
-scratch is used at more than a single point, a 'match_dup' pattern at
+scratch is used at more than a single point, a `match_dup' pattern at
the top level of the input pattern marks the last position in the input
sequence at which the register must be available.
@@ -25467,7 +25853,7 @@ sequence at which the register must be available.
This pattern tries to split a load from its use in the hopes that we'll
be able to schedule around the memory load latency. It allocates a
-single 'SImode' register of class 'GENERAL_REGS' ('"r"') that needs to
+single `SImode' register of class `GENERAL_REGS' (`"r"') that needs to
be live only at the point just before the arithmetic.
A real example requiring extended scratch lifetimes is harder to come
@@ -25486,9 +25872,9 @@ by, so here's a silly made-up example:
(set (match_dup 3) (match_dup 4))]
"")
-If we had not added the '(match_dup 4)' in the middle of the input
+If we had not added the `(match_dup 4)' in the middle of the input
sequence, it might have been the case that the register we chose at the
-beginning of the sequence is killed by the first or second 'set'.
+beginning of the sequence is killed by the first or second `set'.

File: gccint.info, Node: Insn Attributes, Next: Conditional Execution, Prev: Peephole Definitions, Up: Machine Desc
@@ -25497,11 +25883,11 @@ File: gccint.info, Node: Insn Attributes, Next: Conditional Execution, Prev:
============================
In addition to describing the instruction supported by the target
-machine, the 'md' file also defines a group of "attributes" and a set of
+machine, the `md' file also defines a group of "attributes" and a set of
values for each. Every generated insn is assigned a value for each
-attribute. One possible attribute would be the effect that the insn has
-on the machine's condition code. This attribute can then be used by
-'NOTICE_UPDATE_CC' to track the condition codes.
+attribute. One possible attribute would be the effect that the insn
+has on the machine's condition code. This attribute can then be used
+by `NOTICE_UPDATE_CC' to track the condition codes.
* Menu:
@@ -25521,92 +25907,92 @@ File: gccint.info, Node: Defining Attributes, Next: Expressions, Up: Insn Att
16.19.1 Defining Attributes and their Values
--------------------------------------------
-The 'define_attr' expression is used to define each attribute required
+The `define_attr' expression is used to define each attribute required
by the target machine. It looks like:
(define_attr NAME LIST-OF-VALUES DEFAULT)
NAME is a string specifying the name of the attribute being defined.
Some attributes are used in a special way by the rest of the compiler.
-The 'enabled' attribute can be used to conditionally enable or disable
-insn alternatives (*note Disable Insn Alternatives::). The 'predicable'
-attribute, together with a suitable 'define_cond_exec' (*note
+The `enabled' attribute can be used to conditionally enable or disable
+insn alternatives (*note Disable Insn Alternatives::). The `predicable'
+attribute, together with a suitable `define_cond_exec' (*note
Conditional Execution::), can be used to automatically generate
-conditional variants of instruction patterns. The 'mnemonic' attribute
+conditional variants of instruction patterns. The `mnemonic' attribute
can be used to check for the instruction mnemonic (*note Mnemonic
-Attribute::). The compiler internally uses the names 'ce_enabled' and
-'nonce_enabled', so they should not be used elsewhere as alternative
+Attribute::). The compiler internally uses the names `ce_enabled' and
+`nonce_enabled', so they should not be used elsewhere as alternative
names.
- LIST-OF-VALUES is either a string that specifies a comma-separated list
-of values that can be assigned to the attribute, or a null string to
-indicate that the attribute takes numeric values.
+ LIST-OF-VALUES is either a string that specifies a comma-separated
+list of values that can be assigned to the attribute, or a null string
+to indicate that the attribute takes numeric values.
DEFAULT is an attribute expression that gives the value of this
attribute for insns that match patterns whose definition does not
-include an explicit value for this attribute. *Note Attr Example::, for
-more information on the handling of defaults. *Note Constant
+include an explicit value for this attribute. *Note Attr Example::,
+for more information on the handling of defaults. *Note Constant
Attributes::, for information on attributes that do not depend on any
particular insn.
For each defined attribute, a number of definitions are written to the
-'insn-attr.h' file. For cases where an explicit set of values is
+`insn-attr.h' file. For cases where an explicit set of values is
specified for an attribute, the following are defined:
- * A '#define' is written for the symbol 'HAVE_ATTR_NAME'.
+ * A `#define' is written for the symbol `HAVE_ATTR_NAME'.
- * An enumerated class is defined for 'attr_NAME' with elements of the
- form 'UPPER-NAME_UPPER-VALUE' where the attribute name and value
- are first converted to uppercase.
+ * An enumerated class is defined for `attr_NAME' with elements of
+ the form `UPPER-NAME_UPPER-VALUE' where the attribute name and
+ value are first converted to uppercase.
- * A function 'get_attr_NAME' is defined that is passed an insn and
+ * A function `get_attr_NAME' is defined that is passed an insn and
returns the attribute value for that insn.
- For example, if the following is present in the 'md' file:
+ For example, if the following is present in the `md' file:
(define_attr "type" "branch,fp,load,store,arith" ...)
-the following lines will be written to the file 'insn-attr.h'.
+the following lines will be written to the file `insn-attr.h'.
#define HAVE_ATTR_type 1
enum attr_type {TYPE_BRANCH, TYPE_FP, TYPE_LOAD,
TYPE_STORE, TYPE_ARITH};
extern enum attr_type get_attr_type ();
- If the attribute takes numeric values, no 'enum' type will be defined
-and the function to obtain the attribute's value will return 'int'.
+ If the attribute takes numeric values, no `enum' type will be defined
+and the function to obtain the attribute's value will return `int'.
There are attributes which are tied to a specific meaning. These
attributes are not free to use for other purposes:
-'length'
- The 'length' attribute is used to calculate the length of emitted
+`length'
+ The `length' attribute is used to calculate the length of emitted
code chunks. This is especially important when verifying branch
- distances. *Note Insn Lengths::.
+ distances. *Note Insn Lengths::.
-'enabled'
- The 'enabled' attribute can be defined to prevent certain
+`enabled'
+ The `enabled' attribute can be defined to prevent certain
alternatives of an insn definition from being used during code
- generation. *Note Disable Insn Alternatives::.
+ generation. *Note Disable Insn Alternatives::.
-'mnemonic'
- The 'mnemonic' attribute can be defined to implement instruction
- specific checks in e.g. the pipeline description. *Note Mnemonic
+`mnemonic'
+ The `mnemonic' attribute can be defined to implement instruction
+ specific checks in e.g. the pipeline description. *Note Mnemonic
Attribute::.
For each of these special attributes, the corresponding
-'HAVE_ATTR_NAME' '#define' is also written when the attribute is not
-defined; in that case, it is defined as '0'.
+`HAVE_ATTR_NAME' `#define' is also written when the attribute is not
+defined; in that case, it is defined as `0'.
Another way of defining an attribute is to use:
(define_enum_attr "ATTR" "ENUM" DEFAULT)
- This works in just the same way as 'define_attr', except that the list
+ This works in just the same way as `define_attr', except that the list
of values is taken from a separate enumeration called ENUM (*note
-define_enum::). This form allows you to use the same list of values for
-several attributes without having to repeat the list each time. For
-example:
+define_enum::). This form allows you to use the same list of values
+for several attributes without having to repeat the list each time.
+For example:
(define_enum "processor" [
model_a
@@ -25625,9 +26011,9 @@ example:
(define_attr "tune" "model_a,model_b,..."
(const (symbol_ref "target_tune")))
- but without duplicating the processor list. The second example defines
-two separate C enums ('attr_arch' and 'attr_tune') whereas the first
-defines a single C enum ('processor').
+ but without duplicating the processor list. The second example
+defines two separate C enums (`attr_arch' and `attr_tune') whereas the
+first defines a single C enum (`processor').

File: gccint.info, Node: Expressions, Next: Tagging Insns, Prev: Defining Attributes, Up: Insn Attributes
@@ -25639,108 +26025,110 @@ RTL expressions used to define attributes use the codes described above
plus a few specific to attribute definitions, to be discussed below.
Attribute value expressions must have one of the following forms:
-'(const_int I)'
+`(const_int I)'
The integer I specifies the value of a numeric attribute. I must
be non-negative.
The value of a numeric attribute can be specified either with a
- 'const_int', or as an integer represented as a string in
- 'const_string', 'eq_attr' (see below), 'attr', 'symbol_ref', simple
- arithmetic expressions, and 'set_attr' overrides on specific
- instructions (*note Tagging Insns::).
-
-'(const_string VALUE)'
- The string VALUE specifies a constant attribute value. If VALUE is
- specified as '"*"', it means that the default value of the
+ `const_int', or as an integer represented as a string in
+ `const_string', `eq_attr' (see below), `attr', `symbol_ref',
+ simple arithmetic expressions, and `set_attr' overrides on
+ specific instructions (*note Tagging Insns::).
+
+`(const_string VALUE)'
+ The string VALUE specifies a constant attribute value. If VALUE
+ is specified as `"*"', it means that the default value of the
attribute is to be used for the insn containing this expression.
- '"*"' obviously cannot be used in the DEFAULT expression of a
- 'define_attr'.
+ `"*"' obviously cannot be used in the DEFAULT expression of a
+ `define_attr'.
If the attribute whose value is being specified is numeric, VALUE
must be a string containing a non-negative integer (normally
- 'const_int' would be used in this case). Otherwise, it must
+ `const_int' would be used in this case). Otherwise, it must
contain one of the valid values for the attribute.
-'(if_then_else TEST TRUE-VALUE FALSE-VALUE)'
+`(if_then_else TEST TRUE-VALUE FALSE-VALUE)'
TEST specifies an attribute test, whose format is defined below.
The value of this expression is TRUE-VALUE if TEST is true,
otherwise it is FALSE-VALUE.
-'(cond [TEST1 VALUE1 ...] DEFAULT)'
+`(cond [TEST1 VALUE1 ...] DEFAULT)'
The first operand of this expression is a vector containing an even
number of expressions and consisting of pairs of TEST and VALUE
- expressions. The value of the 'cond' expression is that of the
+ expressions. The value of the `cond' expression is that of the
VALUE corresponding to the first true TEST expression. If none of
- the TEST expressions are true, the value of the 'cond' expression
+ the TEST expressions are true, the value of the `cond' expression
is that of the DEFAULT expression.
TEST expressions can have one of the following forms:
-'(const_int I)'
+`(const_int I)'
This test is true if I is nonzero and false otherwise.
-'(not TEST)'
-'(ior TEST1 TEST2)'
-'(and TEST1 TEST2)'
+`(not TEST)'
+`(ior TEST1 TEST2)'
+`(and TEST1 TEST2)'
These tests are true if the indicated logical function is true.
-'(match_operand:M N PRED CONSTRAINTS)'
- This test is true if operand N of the insn whose attribute value is
- being determined has mode M (this part of the test is ignored if M
- is 'VOIDmode') and the function specified by the string PRED
- returns a nonzero value when passed operand N and mode M (this part
- of the test is ignored if PRED is the null string).
+`(match_operand:M N PRED CONSTRAINTS)'
+ This test is true if operand N of the insn whose attribute value
+ is being determined has mode M (this part of the test is ignored
+ if M is `VOIDmode') and the function specified by the string PRED
+ returns a nonzero value when passed operand N and mode M (this
+ part of the test is ignored if PRED is the null string).
The CONSTRAINTS operand is ignored and should be the null string.
-'(match_test C-EXPR)'
+`(match_test C-EXPR)'
The test is true if C expression C-EXPR is true. In non-constant
attributes, C-EXPR has access to the following variables:
- INSN
+ INSN
The rtl instruction under test.
- WHICH_ALTERNATIVE
- The 'define_insn' alternative that INSN matches. *Note Output
- Statement::.
- OPERANDS
+
+ WHICH_ALTERNATIVE
+ The `define_insn' alternative that INSN matches. *Note
+ Output Statement::.
+
+ OPERANDS
An array of INSN's rtl operands.
- C-EXPR behaves like the condition in a C 'if' statement, so there
- is no need to explicitly convert the expression into a boolean 0 or
- 1 value. For example, the following two tests are equivalent:
+ C-EXPR behaves like the condition in a C `if' statement, so there
+ is no need to explicitly convert the expression into a boolean 0
+ or 1 value. For example, the following two tests are equivalent:
(match_test "x & 2")
(match_test "(x & 2) != 0")
-'(le ARITH1 ARITH2)'
-'(leu ARITH1 ARITH2)'
-'(lt ARITH1 ARITH2)'
-'(ltu ARITH1 ARITH2)'
-'(gt ARITH1 ARITH2)'
-'(gtu ARITH1 ARITH2)'
-'(ge ARITH1 ARITH2)'
-'(geu ARITH1 ARITH2)'
-'(ne ARITH1 ARITH2)'
-'(eq ARITH1 ARITH2)'
+`(le ARITH1 ARITH2)'
+`(leu ARITH1 ARITH2)'
+`(lt ARITH1 ARITH2)'
+`(ltu ARITH1 ARITH2)'
+`(gt ARITH1 ARITH2)'
+`(gtu ARITH1 ARITH2)'
+`(ge ARITH1 ARITH2)'
+`(geu ARITH1 ARITH2)'
+`(ne ARITH1 ARITH2)'
+`(eq ARITH1 ARITH2)'
These tests are true if the indicated comparison of the two
arithmetic expressions is true. Arithmetic expressions are formed
- with 'plus', 'minus', 'mult', 'div', 'mod', 'abs', 'neg', 'and',
- 'ior', 'xor', 'not', 'ashift', 'lshiftrt', and 'ashiftrt'
+ with `plus', `minus', `mult', `div', `mod', `abs', `neg', `and',
+ `ior', `xor', `not', `ashift', `lshiftrt', and `ashiftrt'
expressions.
- 'const_int' and 'symbol_ref' are always valid terms (*note Insn
- Lengths::,for additional forms). 'symbol_ref' is a string denoting
- a C expression that yields an 'int' when evaluated by the
- 'get_attr_...' routine. It should normally be a global variable.
+ `const_int' and `symbol_ref' are always valid terms (*note Insn
+ Lengths::,for additional forms). `symbol_ref' is a string
+ denoting a C expression that yields an `int' when evaluated by the
+ `get_attr_...' routine. It should normally be a global variable.
-'(eq_attr NAME VALUE)'
+`(eq_attr NAME VALUE)'
NAME is a string specifying the name of an attribute.
VALUE is a string that is either a valid value for attribute NAME,
- a comma-separated list of values, or '!' followed by a value or
- list. If VALUE does not begin with a '!', this test is true if the
- value of the NAME attribute of the current insn is in the list
- specified by VALUE. If VALUE begins with a '!', this test is true
+ a comma-separated list of values, or `!' followed by a value or
+ list. If VALUE does not begin with a `!', this test is true if
+ the value of the NAME attribute of the current insn is in the list
+ specified by VALUE. If VALUE begins with a `!', this test is true
if the attribute's value is _not_ in the specified list.
For example,
@@ -25751,8 +26139,8 @@ Attribute value expressions must have one of the following forms:
(ior (eq_attr "type" "load") (eq_attr "type" "store"))
- If NAME specifies an attribute of 'alternative', it refers to the
- value of the compiler variable 'which_alternative' (*note Output
+ If NAME specifies an attribute of `alternative', it refers to the
+ value of the compiler variable `which_alternative' (*note Output
Statement::) and the values must be small integers. For example,
(eq_attr "alternative" "2,3")
@@ -25762,22 +26150,22 @@ Attribute value expressions must have one of the following forms:
(ior (eq (symbol_ref "which_alternative") (const_int 2))
(eq (symbol_ref "which_alternative") (const_int 3)))
- Note that, for most attributes, an 'eq_attr' test is simplified in
+ Note that, for most attributes, an `eq_attr' test is simplified in
cases where the value of the attribute being tested is known for
all insns matching a particular pattern. This is by far the most
common case.
-'(attr_flag NAME)'
- The value of an 'attr_flag' expression is true if the flag
- specified by NAME is true for the 'insn' currently being scheduled.
+`(attr_flag NAME)'
+ The value of an `attr_flag' expression is true if the flag
+ specified by NAME is true for the `insn' currently being scheduled.
NAME is a string specifying one of a fixed set of flags to test.
- Test the flags 'forward' and 'backward' to determine the direction
+ Test the flags `forward' and `backward' to determine the direction
of a conditional branch.
- This example describes a conditional branch delay slot which can be
- nullified for forward branches that are taken (annul-true) or for
- backward branches which are not taken (annul-false).
+ This example describes a conditional branch delay slot which can
+ be nullified for forward branches that are taken (annul-true) or
+ for backward branches which are not taken (annul-false).
(define_delay (eq_attr "type" "cbranch")
[(eq_attr "in_branch_delay" "true")
@@ -25786,15 +26174,15 @@ Attribute value expressions must have one of the following forms:
(and (eq_attr "in_branch_delay" "true")
(attr_flag "backward"))])
- The 'forward' and 'backward' flags are false if the current 'insn'
+ The `forward' and `backward' flags are false if the current `insn'
being scheduled is not a conditional branch.
- 'attr_flag' is only used during delay slot scheduling and has no
+ `attr_flag' is only used during delay slot scheduling and has no
meaning to other passes of the compiler.
-'(attr NAME)'
+`(attr NAME)'
The value of another attribute is returned. This is most useful
- for numeric attributes, as 'eq_attr' and 'attr_flag' produce more
+ for numeric attributes, as `eq_attr' and `attr_flag' produce more
efficient code for non-numeric attributes.

@@ -25804,56 +26192,56 @@ File: gccint.info, Node: Tagging Insns, Next: Attr Example, Prev: Expressions
-------------------------------------------
The value assigned to an attribute of an insn is primarily determined by
-which pattern is matched by that insn (or which 'define_peephole'
-generated it). Every 'define_insn' and 'define_peephole' can have an
+which pattern is matched by that insn (or which `define_peephole'
+generated it). Every `define_insn' and `define_peephole' can have an
optional last argument to specify the values of attributes for matching
-insns. The value of any attribute not specified in a particular insn is
-set to the default value for that attribute, as specified in its
-'define_attr'. Extensive use of default values for attributes permits
+insns. The value of any attribute not specified in a particular insn
+is set to the default value for that attribute, as specified in its
+`define_attr'. Extensive use of default values for attributes permits
the specification of the values for only one or two attributes in the
definition of most insn patterns, as seen in the example in the next
section.
- The optional last argument of 'define_insn' and 'define_peephole' is a
+ The optional last argument of `define_insn' and `define_peephole' is a
vector of expressions, each of which defines the value for a single
-attribute. The most general way of assigning an attribute's value is to
-use a 'set' expression whose first operand is an 'attr' expression
+attribute. The most general way of assigning an attribute's value is
+to use a `set' expression whose first operand is an `attr' expression
giving the name of the attribute being set. The second operand of the
-'set' is an attribute expression (*note Expressions::) giving the value
+`set' is an attribute expression (*note Expressions::) giving the value
of the attribute.
- When the attribute value depends on the 'alternative' attribute (i.e.,
+ When the attribute value depends on the `alternative' attribute (i.e.,
which is the applicable alternative in the constraint of the insn), the
-'set_attr_alternative' expression can be used. It allows the
+`set_attr_alternative' expression can be used. It allows the
specification of a vector of attribute expressions, one for each
alternative.
When the generality of arbitrary attribute expressions is not required,
-the simpler 'set_attr' expression can be used, which allows specifying a
-string giving either a single attribute value or a list of attribute
+the simpler `set_attr' expression can be used, which allows specifying
+a string giving either a single attribute value or a list of attribute
values, one for each alternative.
The form of each of the above specifications is shown below. In each
case, NAME is a string specifying the attribute to be set.
-'(set_attr NAME VALUE-STRING)'
+`(set_attr NAME VALUE-STRING)'
VALUE-STRING is either a string giving the desired attribute value,
or a string containing a comma-separated list giving the values for
succeeding alternatives. The number of elements must match the
number of alternatives in the constraint of the insn pattern.
- Note that it may be useful to specify '*' for some alternative, in
+ Note that it may be useful to specify `*' for some alternative, in
which case the attribute will assume its default value for insns
matching that alternative.
-'(set_attr_alternative NAME [VALUE1 VALUE2 ...])'
+`(set_attr_alternative NAME [VALUE1 VALUE2 ...])'
Depending on the alternative of the insn, the value will be one of
- the specified values. This is a shorthand for using a 'cond' with
- tests on the 'alternative' attribute.
+ the specified values. This is a shorthand for using a `cond' with
+ tests on the `alternative' attribute.
-'(set (attr NAME) VALUE)'
- The first operand of this 'set' must be the special RTL expression
- 'attr', whose sole operand is a string giving the name of the
+`(set (attr NAME) VALUE)'
+ The first operand of this `set' must be the special RTL expression
+ `attr', whose sole operand is a string giving the name of the
attribute being set. VALUE is the value of the attribute.
The following shows three different ways of representing the same
@@ -25870,25 +26258,25 @@ attribute value specification:
(eq_attr "alternative" "2") (const_string "store")]
(const_string "arith")))
- The 'define_asm_attributes' expression provides a mechanism to specify
-the attributes assigned to insns produced from an 'asm' statement. It
+ The `define_asm_attributes' expression provides a mechanism to specify
+the attributes assigned to insns produced from an `asm' statement. It
has the form:
(define_asm_attributes [ATTR-SETS])
-where ATTR-SETS is specified the same as for both the 'define_insn' and
-the 'define_peephole' expressions.
+where ATTR-SETS is specified the same as for both the `define_insn' and
+the `define_peephole' expressions.
These values will typically be the "worst case" attribute values. For
example, they might indicate that the condition code will be clobbered.
- A specification for a 'length' attribute is handled specially. The way
-to compute the length of an 'asm' insn is to multiply the length
-specified in the expression 'define_asm_attributes' by the number of
-machine instructions specified in the 'asm' statement, determined by
+ A specification for a `length' attribute is handled specially. The
+way to compute the length of an `asm' insn is to multiply the length
+specified in the expression `define_asm_attributes' by the number of
+machine instructions specified in the `asm' statement, determined by
counting the number of semicolons and newlines in the string.
-Therefore, the value of the 'length' attribute specified in a
-'define_asm_attributes' should be the maximum possible length of a
+Therefore, the value of the `length' attribute specified in a
+`define_asm_attributes' should be the maximum possible length of a
single machine instruction.

@@ -25899,7 +26287,7 @@ File: gccint.info, Node: Attr Example, Next: Insn Lengths, Prev: Tagging Insn
The judicious use of defaulting is important in the efficient use of
insn attributes. Typically, insns are divided into "types" and an
-attribute, customarily called 'type', is used to represent this value.
+attribute, customarily called `type', is used to represent this value.
This attribute is normally used only to define the default value for
other attributes. An example will clarify this usage.
@@ -25910,12 +26298,12 @@ operations, floating point operations, and branches.
Here we will concern ourselves with determining the effect of an insn
on the condition code and will limit ourselves to the following possible
-effects: The condition code can be set unpredictably (clobbered), not be
-changed, be set to agree with the results of the operation, or only
+effects: The condition code can be set unpredictably (clobbered), not
+be changed, be set to agree with the results of the operation, or only
changed if the item previously set into the condition code has been
modified.
- Here is part of a sample 'md' file for such a machine:
+ Here is part of a sample `md' file for such a machine:
(define_attr "type" "load,store,arith,fp,branch" (const_string "arith"))
@@ -25953,51 +26341,51 @@ File: gccint.info, Node: Insn Lengths, Next: Constant Attributes, Prev: Attr
For many machines, multiple types of branch instructions are provided,
each for different length branch displacements. In most cases, the
-assembler will choose the correct instruction to use. However, when the
-assembler cannot do so, GCC can when a special attribute, the 'length'
-attribute, is defined. This attribute must be defined to have numeric
-values by specifying a null string in its 'define_attr'.
+assembler will choose the correct instruction to use. However, when
+the assembler cannot do so, GCC can when a special attribute, the
+`length' attribute, is defined. This attribute must be defined to have
+numeric values by specifying a null string in its `define_attr'.
- In the case of the 'length' attribute, two additional forms of
+ In the case of the `length' attribute, two additional forms of
arithmetic terms are allowed in test expressions:
-'(match_dup N)'
+`(match_dup N)'
This refers to the address of operand N of the current insn, which
- must be a 'label_ref'.
+ must be a `label_ref'.
-'(pc)'
+`(pc)'
For non-branch instructions and backward branch instructions, this
refers to the address of the current insn. But for forward branch
instructions, this refers to the address of the next insn, because
the length of the current insn is to be computed.
For normal insns, the length will be determined by value of the
-'length' attribute. In the case of 'addr_vec' and 'addr_diff_vec' insn
+`length' attribute. In the case of `addr_vec' and `addr_diff_vec' insn
patterns, the length is computed as the number of vectors multiplied by
the size of each vector.
Lengths are measured in addressable storage units (bytes).
- Note that it is possible to call functions via the 'symbol_ref'
+ Note that it is possible to call functions via the `symbol_ref'
mechanism to compute the length of an insn. However, if you use this
mechanism you must provide dummy clauses to express the maximum length
-without using the function call. You can an example of this in the 'pa'
-machine description for the 'call_symref' pattern.
+without using the function call. You can an example of this in the
+`pa' machine description for the `call_symref' pattern.
The following macros can be used to refine the length computation:
-'ADJUST_INSN_LENGTH (INSN, LENGTH)'
+`ADJUST_INSN_LENGTH (INSN, LENGTH)'
If defined, modifies the length assigned to instruction INSN as a
function of the context in which it is used. LENGTH is an lvalue
that contains the initially computed length of the insn and should
be updated with the correct length of the insn.
This macro will normally not be required. A case in which it is
- required is the ROMP. On this machine, the size of an 'addr_vec'
+ required is the ROMP. On this machine, the size of an `addr_vec'
insn must be increased by two to compensate for the fact that
alignment may be required.
- The routine that returns 'get_attr_length' (the value of the 'length'
+ The routine that returns `get_attr_length' (the value of the `length'
attribute) can be used by the output routine to determine the form of
the branch instruction to be written, as the example below illustrates.
@@ -26005,8 +26393,8 @@ the branch instruction to be written, as the example below illustrates.
consider the IBM 360. If we adopt the convention that a register will
be set to the starting address of a function, we can jump to labels
within 4k of the start using a four-byte instruction. Otherwise, we
-need a six-byte sequence to load the address from memory and then branch
-to it.
+need a six-byte sequence to load the address from memory and then
+branch to it.
On such a machine, a pattern for a branch instruction might be
specified as follows:
@@ -26030,8 +26418,8 @@ File: gccint.info, Node: Constant Attributes, Next: Mnemonic Attribute, Prev:
16.19.6 Constant Attributes
---------------------------
-A special form of 'define_attr', where the expression for the default
-value is a 'const' expression, indicates an attribute that is constant
+A special form of `define_attr', where the expression for the default
+value is a `const' expression, indicates an attribute that is constant
for a given run of the compiler. Constant attributes may be used to
specify which variety of processor is used. For example,
@@ -26049,9 +26437,9 @@ specify which variety of processor is used. For example,
The routine generated for constant attributes has no parameters as it
does not depend on any particular insn. RTL expressions used to define
-the value of a constant attribute may use the 'symbol_ref' form, but may
-not use either the 'match_operand' form or 'eq_attr' forms involving
-insn attributes.
+the value of a constant attribute may use the `symbol_ref' form, but
+may not use either the `match_operand' form or `eq_attr' forms
+involving insn attributes.

File: gccint.info, Node: Mnemonic Attribute, Next: Delay Slots, Prev: Constant Attributes, Up: Insn Attributes
@@ -26059,28 +26447,29 @@ File: gccint.info, Node: Mnemonic Attribute, Next: Delay Slots, Prev: Constan
16.19.7 Mnemonic Attribute
--------------------------
-The 'mnemonic' attribute is a string type attribute holding the
-instruction mnemonic for an insn alternative. The attribute values will
-automatically be generated by the machine description parser if there is
-an attribute definition in the md file:
+The `mnemonic' attribute is a string type attribute holding the
+instruction mnemonic for an insn alternative. The attribute values
+will automatically be generated by the machine description parser if
+there is an attribute definition in the md file:
(define_attr "mnemonic" "unknown" (const_string "unknown"))
The default value can be freely chosen as long as it does not collide
-with any of the instruction mnemonics. This value will be used whenever
-the machine description parser is not able to determine the mnemonic
-string. This might be the case for output templates containing more
-than a single instruction as in '"mvcle\t%0,%1,0\;jo\t.-4"'.
+with any of the instruction mnemonics. This value will be used
+whenever the machine description parser is not able to determine the
+mnemonic string. This might be the case for output templates
+containing more than a single instruction as in
+`"mvcle\t%0,%1,0\;jo\t.-4"'.
- The 'mnemonic' attribute set is not generated automatically if the
+ The `mnemonic' attribute set is not generated automatically if the
instruction string is generated via C code.
- An existing 'mnemonic' attribute set in an insn definition will not be
+ An existing `mnemonic' attribute set in an insn definition will not be
overriden by the md file parser. That way it is possible to manually
set the instruction mnemonics for the cases where the md file parser
fails to determine it automatically.
- The 'mnemonic' attribute is useful for dealing with instruction
+ The `mnemonic' attribute is useful for dealing with instruction
specific properties in the pipeline description without defining
additional insn attributes.
@@ -26098,15 +26487,15 @@ File: gccint.info, Node: Delay Slots, Next: Processor pipeline description, P
The insn attribute mechanism can be used to specify the requirements for
delay slots, if any, on a target machine. An instruction is said to
require a "delay slot" if some instructions that are physically after
-the instruction are executed as if they were located before it. Classic
-examples are branch and call instructions, which often execute the
-following instruction before the branch or call is performed.
+the instruction are executed as if they were located before it.
+Classic examples are branch and call instructions, which often execute
+the following instruction before the branch or call is performed.
On some machines, conditional branch instructions can optionally
-"annul" instructions in the delay slot. This means that the instruction
-will not be executed for certain branch outcomes. Both instructions
-that annul if the branch is true and instructions that annul if the
-branch is false are supported.
+"annul" instructions in the delay slot. This means that the
+instruction will not be executed for certain branch outcomes. Both
+instructions that annul if the branch is true and instructions that
+annul if the branch is false are supported.
Delay slot scheduling differs from instruction scheduling in that
determining whether an instruction needs a delay slot is dependent only
@@ -26115,37 +26504,37 @@ instructions. See the next section for a discussion of data-dependent
instruction scheduling.
The requirement of an insn needing one or more delay slots is indicated
-via the 'define_delay' expression. It has the following form:
+via the `define_delay' expression. It has the following form:
(define_delay TEST
[DELAY-1 ANNUL-TRUE-1 ANNUL-FALSE-1
DELAY-2 ANNUL-TRUE-2 ANNUL-FALSE-2
...])
- TEST is an attribute test that indicates whether this 'define_delay'
-applies to a particular insn. If so, the number of required delay slots
-is determined by the length of the vector specified as the second
+ TEST is an attribute test that indicates whether this `define_delay'
+applies to a particular insn. If so, the number of required delay
+slots is determined by the length of the vector specified as the second
argument. An insn placed in delay slot N must satisfy attribute test
DELAY-N. ANNUL-TRUE-N is an attribute test that specifies which insns
may be annulled if the branch is true. Similarly, ANNUL-FALSE-N
-specifies which insns in the delay slot may be annulled if the branch is
-false. If annulling is not supported for that delay slot, '(nil)'
+specifies which insns in the delay slot may be annulled if the branch
+is false. If annulling is not supported for that delay slot, `(nil)'
should be coded.
For example, in the common case where branch and call insns require a
single delay slot, which may contain any insn other than a branch or
-call, the following would be placed in the 'md' file:
+call, the following would be placed in the `md' file:
(define_delay (eq_attr "type" "branch,call")
[(eq_attr "type" "!branch,call") (nil) (nil)])
- Multiple 'define_delay' expressions may be specified. In this case,
+ Multiple `define_delay' expressions may be specified. In this case,
each such expression specifies different delay slot requirements and
-there must be no insn for which tests in two 'define_delay' expressions
+there must be no insn for which tests in two `define_delay' expressions
are both true.
For example, if we have a machine that requires one delay slot for
-branches but two for calls, no delay slot can contain a branch or call
+branches but two for calls, no delay slot can contain a branch or call
insn, and any valid insn in the delay slot for the branch can be
annulled if the branch is true, we might represent this as follows:
@@ -26169,9 +26558,9 @@ superscalar RISC, and VLIW processors) have many "functional units" on
which several instructions can be executed simultaneously. An
instruction starts execution if its issue conditions are satisfied. If
not, the instruction is stalled until its conditions are satisfied.
-Such "interlock (pipeline) delay" causes interruption of the fetching of
-successor instructions (or demands nop instructions, e.g. for some MIPS
-processors).
+Such "interlock (pipeline) delay" causes interruption of the fetching
+of successor instructions (or demands nop instructions, e.g. for some
+MIPS processors).
There are two major kinds of interlock delays in modern processors.
The first one is a data dependence delay determining "instruction
@@ -26204,8 +26593,8 @@ automatically generated from the processor pipeline description. The
pipeline hazard recognizer generated from the machine description is
based on a deterministic finite state automaton (DFA): the instruction
issue is possible if there is a transition from one automaton state to
-another one. This algorithm is very fast, and furthermore, its speed is
-not dependent on processor complexity(1).
+another one. This algorithm is very fast, and furthermore, its speed
+is not dependent on processor complexity(1).
The rest of this section describes the directives that constitute an
automaton-based processor pipeline description. The order of these
@@ -26215,16 +26604,16 @@ constructions within the machine description file is not important.
generated and used for the pipeline hazards recognition. Sometimes the
generated finite state automaton used by the pipeline hazard recognizer
is large. If we use more than one automaton and bind functional units
-to the automata, the total size of the automata is usually less than the
-size of the single automaton. If there is no one such construction,
-only one finite state automaton is generated.
+to the automata, the total size of the automata is usually less than
+the size of the single automaton. If there is no one such
+construction, only one finite state automaton is generated.
(define_automaton AUTOMATA-NAMES)
- AUTOMATA-NAMES is a string giving names of the automata. The names are
-separated by commas. All the automata should have unique names. The
-automaton name is used in the constructions 'define_cpu_unit' and
-'define_query_cpu_unit'.
+ AUTOMATA-NAMES is a string giving names of the automata. The names
+are separated by commas. All the automata should have unique names.
+The automaton name is used in the constructions `define_cpu_unit' and
+`define_query_cpu_unit'.
Each processor functional unit used in the description of instruction
reservations should be described by the following construction.
@@ -26232,28 +26621,29 @@ reservations should be described by the following construction.
(define_cpu_unit UNIT-NAMES [AUTOMATON-NAME])
UNIT-NAMES is a string giving the names of the functional units
-separated by commas. Don't use name 'nothing', it is reserved for other
-goals.
+separated by commas. Don't use name `nothing', it is reserved for
+other goals.
AUTOMATON-NAME is a string giving the name of the automaton with which
the unit is bound. The automaton should be described in construction
-'define_automaton'. You should give "automaton-name", if there is a
+`define_automaton'. You should give "automaton-name", if there is a
defined automaton.
The assignment of units to automata are constrained by the uses of the
-units in insn reservations. The most important constraint is: if a unit
-reservation is present on a particular cycle of an alternative for an
-insn reservation, then some unit from the same automaton must be present
-on the same cycle for the other alternatives of the insn reservation.
-The rest of the constraints are mentioned in the description of the
-subsequent constructions.
+units in insn reservations. The most important constraint is: if a
+unit reservation is present on a particular cycle of an alternative for
+an insn reservation, then some unit from the same automaton must be
+present on the same cycle for the other alternatives of the insn
+reservation. The rest of the constraints are mentioned in the
+description of the subsequent constructions.
The following construction describes CPU functional units analogously
-to 'define_cpu_unit'. The reservation of such units can be queried for
-an automaton state. The instruction scheduler never queries reservation
-of functional units for given automaton state. So as a rule, you don't
-need this construction. This construction could be used for future code
-generation goals (e.g. to generate VLIW insn templates).
+to `define_cpu_unit'. The reservation of such units can be queried for
+an automaton state. The instruction scheduler never queries
+reservation of functional units for given automaton state. So as a
+rule, you don't need this construction. This construction could be
+used for future code generation goals (e.g. to generate VLIW insn
+templates).
(define_query_cpu_unit UNIT-NAMES [AUTOMATON-NAME])
@@ -26274,27 +26664,27 @@ There is an important difference between the old description and the
automaton based pipeline description. The latency time is used for all
dependencies when we use the old description. In the automaton based
pipeline description, the given latency time is only used for true
-dependencies. The cost of anti-dependencies is always zero and the cost
-of output dependencies is the difference between latency times of the
-producing and consuming insns (if the difference is negative, the cost
-is considered to be zero). You can always change the default costs for
-any description by using the target hook 'TARGET_SCHED_ADJUST_COST'
-(*note Scheduling::).
+dependencies. The cost of anti-dependencies is always zero and the
+cost of output dependencies is the difference between latency times of
+the producing and consuming insns (if the difference is negative, the
+cost is considered to be zero). You can always change the default
+costs for any description by using the target hook
+`TARGET_SCHED_ADJUST_COST' (*note Scheduling::).
INSN-NAME is a string giving the internal name of the insn. The
-internal names are used in constructions 'define_bypass' and in the
+internal names are used in constructions `define_bypass' and in the
automaton description file generated for debugging. The internal name
-has nothing in common with the names in 'define_insn'. It is a good
+has nothing in common with the names in `define_insn'. It is a good
practice to use insn classes described in the processor manual.
CONDITION defines what RTL insns are described by this construction.
You should remember that you will be in trouble if CONDITION for two or
-more different 'define_insn_reservation' constructions is TRUE for an
+more different `define_insn_reservation' constructions is TRUE for an
insn. In this case what reservation will be used for the insn is not
defined. Such cases are not checked during generation of the pipeline
hazards recognizer because in general recognizing that two conditions
may have the same value is quite difficult (especially if the conditions
-contain 'symbol_ref'). It is also not checked during the pipeline
+contain `symbol_ref'). It is also not checked during the pipeline
hazard recognizer work because it would slow down the recognizer
considerably.
@@ -26320,28 +26710,28 @@ expression according to the following syntax:
| "nothing"
| "(" regexp ")"
- * ',' is used for describing the start of the next cycle in the
+ * `,' is used for describing the start of the next cycle in the
reservation.
- * '|' is used for describing a reservation described by the first
+ * `|' is used for describing a reservation described by the first
regular expression *or* a reservation described by the second
regular expression *or* etc.
- * '+' is used for describing a reservation described by the first
+ * `+' is used for describing a reservation described by the first
regular expression *and* a reservation described by the second
regular expression *and* etc.
- * '*' is used for convenience and simply means a sequence in which
+ * `*' is used for convenience and simply means a sequence in which
the regular expression are repeated NUMBER times with cycle
- advancing (see ',').
+ advancing (see `,').
- * 'cpu_function_unit_name' denotes reservation of the named
+ * `cpu_function_unit_name' denotes reservation of the named
functional unit.
- * 'reservation_name' -- see description of construction
- 'define_reservation'.
+ * `reservation_name' -- see description of construction
+ `define_reservation'.
- * 'nothing' denotes no unit reservations.
+ * `nothing' denotes no unit reservations.
Sometimes unit reservations for different insns contain common parts.
In such case, you can simplify the pipeline description by describing
@@ -26351,8 +26741,8 @@ the common part by the following construction
RESERVATION-NAME is a string giving name of REGEXP. Functional unit
names and reservation names are in the same name space. So the
-reservation names should be different from the functional unit names and
-can not be the reserved name 'nothing'.
+reservation names should be different from the functional unit names
+and can not be the reserved name `nothing'.
The following construction is used to describe exceptions in the
latency time for given instruction pair. This is so called bypasses.
@@ -26361,25 +26751,25 @@ latency time for given instruction pair. This is so called bypasses.
[GUARD])
NUMBER defines when the result generated by the instructions given in
-string OUT_INSN_NAMES will be ready for the instructions given in string
-IN_INSN_NAMES. Each of these strings is a comma-separated list of
-filename-style globs and they refer to the names of
-'define_insn_reservation's. For example:
+string OUT_INSN_NAMES will be ready for the instructions given in
+string IN_INSN_NAMES. Each of these strings is a comma-separated list
+of filename-style globs and they refer to the names of
+`define_insn_reservation's. For example:
(define_bypass 1 "cpu1_load_*, cpu1_store_*" "cpu1_load_*")
- defines a bypass between instructions that start with 'cpu1_load_' or
-'cpu1_store_' and those that start with 'cpu1_load_'.
+ defines a bypass between instructions that start with `cpu1_load_' or
+`cpu1_store_' and those that start with `cpu1_load_'.
GUARD is an optional string giving the name of a C function which
defines an additional guard for the bypass. The function will get the
two insns as parameters. If the function returns zero the bypass will
be ignored for this case. The additional guard is necessary to
recognize complicated bypasses, e.g. when the consumer is only an
-address of insn 'store' (not a stored value).
+address of insn `store' (not a stored value).
If there are more one bypass with the same output and input insns, the
chosen bypass is the first bypass with a guard in description whose
-guard function returns nonzero. If there is no such bypass, then bypass
-without the guard function is chosen.
+guard function returns nonzero. If there is no such bypass, then
+bypass without the guard function is chosen.
The following five constructions are usually used to describe VLIW
processors, or more precisely, to describe a placement of small
@@ -26399,7 +26789,7 @@ commas.
comma. Currently pattern is one unit or units separated by
white-spaces.
- The first construction ('exclusion_set') means that each functional
+ The first construction (`exclusion_set') means that each functional
unit in the first string can not be reserved simultaneously with a unit
whose name is in the second string and vice versa. For example, the
construction is useful for describing processors (e.g. some SPARC
@@ -26407,60 +26797,60 @@ processors) with a fully pipelined floating point functional unit which
can execute simultaneously only single floating point insns or only
double floating point insns.
- The second construction ('presence_set') means that each functional
+ The second construction (`presence_set') means that each functional
unit in the first string can not be reserved unless at least one of
-pattern of units whose names are in the second string is reserved. This
-is an asymmetric relation. For example, it is useful for description
-that VLIW 'slot1' is reserved after 'slot0' reservation. We could
-describe it by the following construction
+pattern of units whose names are in the second string is reserved.
+This is an asymmetric relation. For example, it is useful for
+description that VLIW `slot1' is reserved after `slot0' reservation.
+We could describe it by the following construction
(presence_set "slot1" "slot0")
- Or 'slot1' is reserved only after 'slot0' and unit 'b0' reservation.
+ Or `slot1' is reserved only after `slot0' and unit `b0' reservation.
In this case we could write
(presence_set "slot1" "slot0 b0")
- The third construction ('final_presence_set') is analogous to
-'presence_set'. The difference between them is when checking is done.
+ The third construction (`final_presence_set') is analogous to
+`presence_set'. The difference between them is when checking is done.
When an instruction is issued in given automaton state reflecting all
current and planned unit reservations, the automaton state is changed.
The first state is a source state, the second one is a result state.
-Checking for 'presence_set' is done on the source state reservation,
-checking for 'final_presence_set' is done on the result reservation.
+Checking for `presence_set' is done on the source state reservation,
+checking for `final_presence_set' is done on the result reservation.
This construction is useful to describe a reservation which is actually
two subsequent reservations. For example, if we use
(presence_set "slot1" "slot0")
- the following insn will be never issued (because 'slot1' requires
-'slot0' which is absent in the source state).
+ the following insn will be never issued (because `slot1' requires
+`slot0' which is absent in the source state).
(define_reservation "insn_and_nop" "slot0 + slot1")
- but it can be issued if we use analogous 'final_presence_set'.
+ but it can be issued if we use analogous `final_presence_set'.
- The forth construction ('absence_set') means that each functional unit
+ The forth construction (`absence_set') means that each functional unit
in the first string can be reserved only if each pattern of units whose
names are in the second string is not reserved. This is an asymmetric
-relation (actually 'exclusion_set' is analogous to this one but it is
-symmetric). For example it might be useful in a VLIW description to say
-that 'slot0' cannot be reserved after either 'slot1' or 'slot2' have
-been reserved. This can be described as:
+relation (actually `exclusion_set' is analogous to this one but it is
+symmetric). For example it might be useful in a VLIW description to
+say that `slot0' cannot be reserved after either `slot1' or `slot2'
+have been reserved. This can be described as:
(absence_set "slot0" "slot1, slot2")
- Or 'slot2' can not be reserved if 'slot0' and unit 'b0' are reserved or
-'slot1' and unit 'b1' are reserved. In this case we could write
+ Or `slot2' can not be reserved if `slot0' and unit `b0' are reserved
+or `slot1' and unit `b1' are reserved. In this case we could write
(absence_set "slot2" "slot0 b0, slot1 b1")
All functional units mentioned in a set should belong to the same
automaton.
- The last construction ('final_absence_set') is analogous to
-'absence_set' but checking is done on the result (state) reservation.
-See comments for 'final_presence_set'.
+ The last construction (`final_absence_set') is analogous to
+`absence_set' but checking is done on the result (state) reservation.
+See comments for `final_presence_set'.
You can control the generator of the pipeline hazard recognizer with
the following construction.
@@ -26477,38 +26867,38 @@ Currently there are the following options:
* "time" means printing time statistics about the generation of
automata.
- * "stats" means printing statistics about the generated automata such
- as the number of DFA states, NDFA states and arcs.
+ * "stats" means printing statistics about the generated automata
+ such as the number of DFA states, NDFA states and arcs.
* "v" means a generation of the file describing the result automata.
- The file has suffix '.dfa' and can be used for the description
+ The file has suffix `.dfa' and can be used for the description
verification and debugging.
- * "w" means a generation of warning instead of error for non-critical
- errors.
+ * "w" means a generation of warning instead of error for
+ non-critical errors.
- * "no-comb-vect" prevents the automaton generator from generating two
- data structures and comparing them for space efficiency. Using a
- comb vector to represent transitions may be better, but it can be
+ * "no-comb-vect" prevents the automaton generator from generating
+ two data structures and comparing them for space efficiency. Using
+ a comb vector to represent transitions may be better, but it can be
very expensive to construct. This option is useful if the build
process spends an unacceptably long time in genautomata.
* "ndfa" makes nondeterministic finite state automata. This affects
- the treatment of operator '|' in the regular expressions. The
+ the treatment of operator `|' in the regular expressions. The
usual treatment of the operator is to try the first alternative
and, if the reservation is not possible, the second alternative.
The nondeterministic treatment means trying all alternatives, some
of them may be rejected by reservations in the subsequent insns.
* "collapse-ndfa" modifies the behaviour of the generator when
- producing an automaton. An additional state transition to collapse
- a nondeterministic NDFA state to a deterministic DFA state is
- generated. It can be triggered by passing 'const0_rtx' to
+ producing an automaton. An additional state transition to
+ collapse a nondeterministic NDFA state to a deterministic DFA
+ state is generated. It can be triggered by passing `const0_rtx' to
state_transition. In such an automaton, cycle advance transitions
are available only for these collapsed states. This option is
- useful for ports that want to use the 'ndfa' option, but also want
- to use 'define_query_cpu_unit' to assign units to insns issued in a
- cycle.
+ useful for ports that want to use the `ndfa' option, but also want
+ to use `define_query_cpu_unit' to assign units to insns issued in
+ a cycle.
* "progress" means output of a progress bar showing how many states
were generated so far for automaton being processed. This is
@@ -26518,8 +26908,8 @@ Currently there are the following options:
the huge automaton.
As an example, consider a superscalar RISC machine which can issue
-three insns (two integer insns and one floating point insn) on the cycle
-but can finish only two insns. To describe this, we define the
+three insns (two integer insns and one floating point insn) on the
+cycle but can finish only two insns. To describe this, we define the
following functional units.
(define_cpu_unit "i0_pipeline, i1_pipeline, f_pipeline")
@@ -26527,16 +26917,16 @@ following functional units.
All simple integer insns can be executed in any integer pipeline and
their result is ready in two cycles. The simple integer insns are
-issued into the first pipeline unless it is reserved, otherwise they are
-issued into the second pipeline. Integer division and multiplication
-insns can be executed only in the second integer pipeline and their
-results are ready correspondingly in 8 and 4 cycles. The integer
-division is not pipelined, i.e. the subsequent integer division insn can
-not be issued until the current division insn finished. Floating point
-insns are fully pipelined and their results are ready in 3 cycles.
-Where the result of a floating point insn is used by an integer insn, an
-additional delay of one cycle is incurred. To describe all of this we
-could specify
+issued into the first pipeline unless it is reserved, otherwise they
+are issued into the second pipeline. Integer division and
+multiplication insns can be executed only in the second integer
+pipeline and their results are ready correspondingly in 8 and 4 cycles.
+The integer division is not pipelined, i.e. the subsequent integer
+division insn can not be issued until the current division insn
+finished. Floating point insns are fully pipelined and their results
+are ready in 3 cycles. Where the result of a floating point insn is
+used by an integer insn, an additional delay of one cycle is incurred.
+To describe all of this we could specify
(define_cpu_unit "div")
@@ -26558,19 +26948,19 @@ could specify
(define_reservation "finish" "port0|port1")
- and use it in all 'define_insn_reservation' as in the following
+ and use it in all `define_insn_reservation' as in the following
construction
(define_insn_reservation "simple" 2 (eq_attr "type" "int")
"(i0_pipeline | i1_pipeline), finish")
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) However, the size of the automaton depends on processor
+ (1) However, the size of the automaton depends on processor
complexity. To limit this effect, machine descriptions can split
orthogonal parts of the machine description among several automata: but
-then, since each of these must be stepped independently, this does cause
-a small decrease in the algorithm's performance.
+then, since each of these must be stepped independently, this does
+cause a small decrease in the algorithm's performance.

File: gccint.info, Node: Conditional Execution, Next: Define Subst, Prev: Insn Attributes, Up: Machine Desc
@@ -26582,8 +26972,8 @@ A number of architectures provide for some form of conditional
execution, or predication. The hallmark of this feature is the ability
to nullify most of the instructions in the instruction set. When the
instruction set is large and not entirely symmetric, it can be quite
-tedious to describe these forms directly in the '.md' file. An
-alternative is the 'define_cond_exec' template.
+tedious to describe these forms directly in the `.md' file. An
+alternative is the `define_cond_exec' template.
(define_cond_exec
[PREDICATE-PATTERN]
@@ -26591,42 +26981,42 @@ alternative is the 'define_cond_exec' template.
"OUTPUT-TEMPLATE"
"OPTIONAL-INSN-ATTRIBUES")
- PREDICATE-PATTERN is the condition that must be true for the insn to be
-executed at runtime and should match a relational operator. One can use
-'match_operator' to match several relational operators at once. Any
-'match_operand' operands must have no more than one alternative.
+ PREDICATE-PATTERN is the condition that must be true for the insn to
+be executed at runtime and should match a relational operator. One can
+use `match_operator' to match several relational operators at once.
+Any `match_operand' operands must have no more than one alternative.
- CONDITION is a C expression that must be true for the generated pattern
-to match.
+ CONDITION is a C expression that must be true for the generated
+pattern to match.
- OUTPUT-TEMPLATE is a string similar to the 'define_insn' output
-template (*note Output Template::), except that the '*' and '@' special
+ OUTPUT-TEMPLATE is a string similar to the `define_insn' output
+template (*note Output Template::), except that the `*' and `@' special
cases do not apply. This is only useful if the assembly text for the
predicate is a simple prefix to the main insn. In order to handle the
-general case, there is a global variable 'current_insn_predicate' that
-will contain the entire predicate if the current insn is predicated, and
-will otherwise be 'NULL'.
+general case, there is a global variable `current_insn_predicate' that
+will contain the entire predicate if the current insn is predicated,
+and will otherwise be `NULL'.
OPTIONAL-INSN-ATTRIBUTES is an optional vector of attributes that gets
-appended to the insn attributes of the produced cond_exec rtx. It can
+appended to the insn attributes of the produced cond_exec rtx. It can
be used to add some distinguishing attribute to cond_exec rtxs produced
-that way. An example usage would be to use this attribute in
-conjunction with attributes on the main pattern to disable particular
-alternatives under certain conditions.
+that way. An example usage would be to use this attribute in conjunction
+with attributes on the main pattern to disable particular alternatives
+under certain conditions.
- When 'define_cond_exec' is used, an implicit reference to the
-'predicable' instruction attribute is made. *Note Insn Attributes::.
+ When `define_cond_exec' is used, an implicit reference to the
+`predicable' instruction attribute is made. *Note Insn Attributes::.
This attribute must be a boolean (i.e. have exactly two elements in its
-LIST-OF-VALUES), with the possible values being 'no' and 'yes'. The
+LIST-OF-VALUES), with the possible values being `no' and `yes'. The
default and all uses in the insns must be a simple constant, not a
complex expressions. It may, however, depend on the alternative, by
using a comma-separated list of values. If that is the case, the port
-should also define an 'enabled' attribute (*note Disable Insn
-Alternatives::), which should also allow only 'no' and 'yes' as its
+should also define an `enabled' attribute (*note Disable Insn
+Alternatives::), which should also allow only `no' and `yes' as its
values.
- For each 'define_insn' for which the 'predicable' attribute is true, a
-new 'define_insn' pattern will be generated that matches a predicated
+ For each `define_insn' for which the `predicable' attribute is true, a
+new `define_insn' pattern will be generated that matches a predicated
version of the instruction. For example,
(define_insn "addsi"
@@ -26661,11 +27051,11 @@ File: gccint.info, Node: Define Subst, Next: Constant Definitions, Prev: Cond
For some hardware architectures there are common cases when the RTL
templates for the instructions can be derived from the other RTL
-templates using simple transformations. E.g., 'i386.md' contains an RTL
-template for the ordinary 'sub' instruction-- '*subsi_1', and for the
-'sub' instruction with subsequent zero-extension--'*subsi_1_zext'. Such
-cases can be easily implemented by a single meta-template capable of
-generating a modified case based on the initial one:
+templates using simple transformations. E.g., `i386.md' contains an
+RTL template for the ordinary `sub' instruction-- `*subsi_1', and for
+the `sub' instruction with subsequent zero-extension--`*subsi_1_zext'.
+Such cases can be easily implemented by a single meta-template capable
+of generating a modified case based on the initial one:
(define_subst "NAME"
[INPUT-TEMPLATE]
@@ -26681,38 +27071,38 @@ output-template.
OUTPUT-TEMPLATE is a pattern that will be used in the resulting
template.
- 'define_subst' mechanism is tightly coupled with the notion of the
-subst attribute (*note Subst Iterators::). The use of 'define_subst' is
-triggered by a reference to a subst attribute in the transforming RTL
-template. This reference initiates duplication of the source RTL
+ `define_subst' mechanism is tightly coupled with the notion of the
+subst attribute (*note Subst Iterators::). The use of `define_subst'
+is triggered by a reference to a subst attribute in the transforming
+RTL template. This reference initiates duplication of the source RTL
template and substitution of the attributes with their values. The
source RTL template is left unchanged, while the copy is transformed by
-'define_subst'. This transformation can fail in the case when the
+`define_subst'. This transformation can fail in the case when the
source RTL template is not matched against the input-template of the
-'define_subst'. In such case the copy is deleted.
+`define_subst'. In such case the copy is deleted.
- 'define_subst' can be used only in 'define_insn' and 'define_expand',
-it cannot be used in other expressions (e.g. in
-'define_insn_and_split').
+ `define_subst' can be used only in `define_insn' and `define_expand',
+it cannot be used in other expressions (e.g. in
+`define_insn_and_split').
* Menu:
-* Define Subst Example:: Example of 'define_subst' work.
+* Define Subst Example:: Example of `define_subst' work.
* Define Subst Pattern Matching:: Process of template comparison.
* Define Subst Output Template:: Generation of output template.

File: gccint.info, Node: Define Subst Example, Next: Define Subst Pattern Matching, Up: Define Subst
-16.21.1 'define_subst' Example
+16.21.1 `define_subst' Example
------------------------------
-To illustrate how 'define_subst' works, let us examine a simple template
-transformation.
+To illustrate how `define_subst' works, let us examine a simple
+template transformation.
Suppose there are two kinds of instructions: one that touches flags and
the other that does not. The instructions of the second type could be
-generated with the following 'define_subst':
+generated with the following `define_subst':
(define_subst "add_clobber_subst"
[(set (match_operand:SI 0 "" "")
@@ -26722,11 +27112,11 @@ generated with the following 'define_subst':
(match_dup 1))
(clobber (reg:CC FLAGS_REG))]
- This 'define_subst' can be applied to any RTL pattern containing 'set'
+ This `define_subst' can be applied to any RTL pattern containing `set'
of mode SI and generates a copy with clobber when it is applied.
- Assume there is an RTL template for a 'max' instruction to be used in
-'define_subst' mentioned above:
+ Assume there is an RTL template for a `max' instruction to be used in
+`define_subst' mentioned above:
(define_insn "maxsi"
[(set (match_operand:SI 0 "register_operand" "=r")
@@ -26737,20 +27127,20 @@ of mode SI and generates a copy with clobber when it is applied.
"max\t{%2, %1, %0|%0, %1, %2}"
[...])
- To mark the RTL template for 'define_subst' application,
+ To mark the RTL template for `define_subst' application,
subst-attributes are used. They should be declared in advance:
(define_subst_attr "add_clobber_name" "add_clobber_subst" "_noclobber" "_clobber")
- Here 'add_clobber_name' is the attribute name, 'add_clobber_subst' is
-the name of the corresponding 'define_subst', the third argument
-('_noclobber') is the attribute value that would be substituted into the
-unchanged version of the source RTL template, and the last argument
-('_clobber') is the value that would be substituted into the second,
+ Here `add_clobber_name' is the attribute name, `add_clobber_subst' is
+the name of the corresponding `define_subst', the third argument
+(`_noclobber') is the attribute value that would be substituted into
+the unchanged version of the source RTL template, and the last argument
+(`_clobber') is the value that would be substituted into the second,
transformed, version of the RTL template.
Once the subst-attribute has been defined, it should be used in RTL
-templates which need to be processed by the 'define_subst'. So, the
+templates which need to be processed by the `define_subst'. So, the
original RTL template should be changed:
(define_insn "maxsi<add_clobber_name>"
@@ -26762,7 +27152,7 @@ original RTL template should be changed:
"max\t{%2, %1, %0|%0, %1, %2}"
[...])
- The result of the 'define_subst' usage would look like the following:
+ The result of the `define_subst' usage would look like the following:
(define_insn "maxsi_noclobber"
[(set (match_operand:SI 0 "register_operand" "=r")
@@ -26785,66 +27175,67 @@ original RTL template should be changed:

File: gccint.info, Node: Define Subst Pattern Matching, Next: Define Subst Output Template, Prev: Define Subst Example, Up: Define Subst
-16.21.2 Pattern Matching in 'define_subst'
+16.21.2 Pattern Matching in `define_subst'
------------------------------------------
-All expressions, allowed in 'define_insn' or 'define_expand', are
-allowed in the input-template of 'define_subst', except 'match_par_dup',
-'match_scratch', 'match_parallel'. The meanings of expressions in the
-input-template were changed:
+All expressions, allowed in `define_insn' or `define_expand', are
+allowed in the input-template of `define_subst', except
+`match_par_dup', `match_scratch', `match_parallel'. The meanings of
+expressions in the input-template were changed:
- 'match_operand' matches any expression (possibly, a subtree in
-RTL-template), if modes of the 'match_operand' and this expression are
-the same, or mode of the 'match_operand' is 'VOIDmode', or this
-expression is 'match_dup', 'match_op_dup'. If the expression is
-'match_operand' too, and predicate of 'match_operand' from the input
+ `match_operand' matches any expression (possibly, a subtree in
+RTL-template), if modes of the `match_operand' and this expression are
+the same, or mode of the `match_operand' is `VOIDmode', or this
+expression is `match_dup', `match_op_dup'. If the expression is
+`match_operand' too, and predicate of `match_operand' from the input
pattern is not empty, then the predicates are compared. That can be
used for more accurate filtering of accepted RTL-templates.
- 'match_operator' matches common operators (like 'plus', 'minus'),
-'unspec', 'unspec_volatile' operators and 'match_operator's from the
-original pattern if the modes match and 'match_operator' from the input
+ `match_operator' matches common operators (like `plus', `minus'),
+`unspec', `unspec_volatile' operators and `match_operator's from the
+original pattern if the modes match and `match_operator' from the input
pattern has the same number of operands as the operator from the
original pattern.

File: gccint.info, Node: Define Subst Output Template, Prev: Define Subst Pattern Matching, Up: Define Subst
-16.21.3 Generation of output template in 'define_subst'
+16.21.3 Generation of output template in `define_subst'
-------------------------------------------------------
-If all necessary checks for 'define_subst' application pass, a new
+If all necessary checks for `define_subst' application pass, a new
RTL-pattern, based on the output-template, is created to replace the old
template. Like in input-patterns, meanings of some RTL expressions are
-changed when they are used in output-patterns of a 'define_subst'.
-Thus, 'match_dup' is used for copying the whole expression from the
-original pattern, which matched corresponding 'match_operand' from the
+changed when they are used in output-patterns of a `define_subst'.
+Thus, `match_dup' is used for copying the whole expression from the
+original pattern, which matched corresponding `match_operand' from the
input pattern.
- 'match_dup N' is used in the output template to be replaced with the
-expression from the original pattern, which matched 'match_operand N'
-from the input pattern. As a consequence, 'match_dup' cannot be used to
-point to 'match_operand's from the output pattern, it should always
-refer to a 'match_operand' from the input pattern.
+ `match_dup N' is used in the output template to be replaced with the
+expression from the original pattern, which matched `match_operand N'
+from the input pattern. As a consequence, `match_dup' cannot be used
+to point to `match_operand's from the output pattern, it should always
+refer to a `match_operand' from the input pattern.
In the output template one can refer to the expressions from the
original pattern and create new ones. For instance, some operands could
-be added by means of standard 'match_operand'.
-
- After replacing 'match_dup' with some RTL-subtree from the original
-pattern, it could happen that several 'match_operand's in the output
-pattern have the same indexes. It is unknown, how many and what indexes
-would be used in the expression which would replace 'match_dup', so such
-conflicts in indexes are inevitable. To overcome this issue,
-'match_operands' and 'match_operators', which were introduced into the
-output pattern, are renumerated when all 'match_dup's are replaced.
-
- Number of alternatives in 'match_operand's introduced into the output
-template 'M' could differ from the number of alternatives in the
-original pattern 'N', so in the resultant pattern there would be 'N*M'
+be added by means of standard `match_operand'.
+
+ After replacing `match_dup' with some RTL-subtree from the original
+pattern, it could happen that several `match_operand's in the output
+pattern have the same indexes. It is unknown, how many and what
+indexes would be used in the expression which would replace
+`match_dup', so such conflicts in indexes are inevitable. To overcome
+this issue, `match_operands' and `match_operators', which were
+introduced into the output pattern, are renumerated when all
+`match_dup's are replaced.
+
+ Number of alternatives in `match_operand's introduced into the output
+template `M' could differ from the number of alternatives in the
+original pattern `N', so in the resultant pattern there would be `N*M'
alternatives. Thus, constraints from the original pattern would be
-duplicated 'N' times, constraints from the output pattern would be
-duplicated 'M' times, producing all possible combinations.
+duplicated `N' times, constraints from the output pattern would be
+duplicated `M' times, producing all possible combinations.

File: gccint.info, Node: Constant Definitions, Next: Iterators, Prev: Define Subst, Up: Machine Desc
@@ -26855,11 +27246,11 @@ File: gccint.info, Node: Constant Definitions, Next: Iterators, Prev: Define
Using literal constants inside instruction patterns reduces legibility
and can be a maintenance problem.
- To overcome this problem, you may use the 'define_constants'
+ To overcome this problem, you may use the `define_constants'
expression. It contains a vector of name-value pairs. From that point
on, wherever any of the names appears in the MD file, it is as if the
corresponding value had been written instead. You may use
-'define_constants' multiple times; each appearance adds more constants
+`define_constants' multiple times; each appearance adds more constants
to the table. It is an error to redefine a constant with a different
value.
@@ -26896,7 +27287,7 @@ value.
in the insn-codes.h header file as #defines.
You can also use the machine description file to define enumerations.
-Like the constants defined by 'define_constant', these enumerations are
+Like the constants defined by `define_constant', these enumerations are
visible to both the machine description file and the main C code.
The syntax is as follows:
@@ -26909,7 +27300,7 @@ visible to both the machine description file and the main C code.
])
This definition causes the equivalent of the following C code to appear
-in 'insn-constants.h':
+in `insn-constants.h':
enum NAME {
VALUE0 = 0,
@@ -26919,17 +27310,17 @@ in 'insn-constants.h':
};
#define NUM_CNAME_VALUES (N + 1)
- where CNAME is the capitalized form of NAME. It also makes each VALUEI
-available in the machine description file, just as if it had been
-declared with:
+ where CNAME is the capitalized form of NAME. It also makes each
+VALUEI available in the machine description file, just as if it had
+been declared with:
(define_constants [(VALUEI I)])
- Each VALUEI is usually an upper-case identifier and usually begins with
-CNAME.
+ Each VALUEI is usually an upper-case identifier and usually begins
+with CNAME.
- You can split the enumeration definition into as many statements as you
-like. The above example is directly equivalent to:
+ You can split the enumeration definition into as many statements as
+you like. The above example is directly equivalent to:
(define_c_enum "NAME" [VALUE0])
(define_c_enum "NAME" [VALUE1])
@@ -26937,34 +27328,34 @@ like. The above example is directly equivalent to:
(define_c_enum "NAME" [VALUEN])
Splitting the enumeration helps to improve the modularity of each
-individual '.md' file. For example, if a port defines its
-synchronization instructions in a separate 'sync.md' file, it is
+individual `.md' file. For example, if a port defines its
+synchronization instructions in a separate `sync.md' file, it is
convenient to define all synchronization-specific enumeration values in
-'sync.md' rather than in the main '.md' file.
+`sync.md' rather than in the main `.md' file.
Some enumeration names have special significance to GCC:
-'unspecv'
- If an enumeration called 'unspecv' is defined, GCC will use it when
- printing out 'unspec_volatile' expressions. For example:
+`unspecv'
+ If an enumeration called `unspecv' is defined, GCC will use it
+ when printing out `unspec_volatile' expressions. For example:
(define_c_enum "unspecv" [
UNSPECV_BLOCKAGE
])
- causes GCC to print '(unspec_volatile ... 0)' as:
+ causes GCC to print `(unspec_volatile ... 0)' as:
(unspec_volatile ... UNSPECV_BLOCKAGE)
-'unspec'
- If an enumeration called 'unspec' is defined, GCC will use it when
- printing out 'unspec' expressions. GCC will also use it when
- printing out 'unspec_volatile' expressions unless an 'unspecv'
+`unspec'
+ If an enumeration called `unspec' is defined, GCC will use it when
+ printing out `unspec' expressions. GCC will also use it when
+ printing out `unspec_volatile' expressions unless an `unspecv'
enumeration is also defined. You can therefore decide whether to
keep separate enumerations for volatile and non-volatile
expressions or whether to use the same enumeration for both.
- Another way of defining an enumeration is to use 'define_enum':
+ Another way of defining an enumeration is to use `define_enum':
(define_enum "NAME" [
VALUE0
@@ -26983,7 +27374,7 @@ convenient to define all synchronization-specific enumeration values in
])
where CVALUEI is the capitalized form of VALUEI. However, unlike
-'define_c_enum', the enumerations defined by 'define_enum' can be used
+`define_c_enum', the enumerations defined by `define_enum' can be used
in attribute specifications (*note define_enum_attr::).

@@ -27013,16 +27404,17 @@ Ports often need to define similar patterns for two or more different
modes. For example:
* If a processor has hardware support for both single and double
- floating-point arithmetic, the 'SFmode' patterns tend to be very
- similar to the 'DFmode' ones.
+ floating-point arithmetic, the `SFmode' patterns tend to be very
+ similar to the `DFmode' ones.
- * If a port uses 'SImode' pointers in one configuration and 'DImode'
- pointers in another, it will usually have very similar 'SImode' and
- 'DImode' patterns for manipulating pointers.
+ * If a port uses `SImode' pointers in one configuration and `DImode'
+ pointers in another, it will usually have very similar `SImode'
+ and `DImode' patterns for manipulating pointers.
- Mode iterators allow several patterns to be instantiated from one '.md'
-file template. They can be used with any type of rtx-based construct,
-such as a 'define_insn', 'define_split', or 'define_peephole2'.
+ Mode iterators allow several patterns to be instantiated from one
+`.md' file template. They can be used with any type of rtx-based
+construct, such as a `define_insn', `define_split', or
+`define_peephole2'.
* Menu:
@@ -27040,29 +27432,29 @@ The syntax for defining a mode iterator is:
(define_mode_iterator NAME [(MODE1 "COND1") ... (MODEN "CONDN")])
- This allows subsequent '.md' file constructs to use the mode suffix
-':NAME'. Every construct that does so will be expanded N times, once
-with every use of ':NAME' replaced by ':MODE1', once with every use
-replaced by ':MODE2', and so on. In the expansion for a particular
+ This allows subsequent `.md' file constructs to use the mode suffix
+`:NAME'. Every construct that does so will be expanded N times, once
+with every use of `:NAME' replaced by `:MODE1', once with every use
+replaced by `:MODE2', and so on. In the expansion for a particular
MODEI, every C condition will also require that CONDI be true.
For example:
(define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")])
- defines a new mode suffix ':P'. Every construct that uses ':P' will be
-expanded twice, once with every ':P' replaced by ':SI' and once with
-every ':P' replaced by ':DI'. The ':SI' version will only apply if
-'Pmode == SImode' and the ':DI' version will only apply if 'Pmode ==
+ defines a new mode suffix `:P'. Every construct that uses `:P' will
+be expanded twice, once with every `:P' replaced by `:SI' and once with
+every `:P' replaced by `:DI'. The `:SI' version will only apply if
+`Pmode == SImode' and the `:DI' version will only apply if `Pmode ==
DImode'.
- As with other '.md' conditions, an empty string is treated as "always
-true". '(MODE "")' can also be abbreviated to 'MODE'. For example:
+ As with other `.md' conditions, an empty string is treated as "always
+true". `(MODE "")' can also be abbreviated to `MODE'. For example:
(define_mode_iterator GPR [SI (DI "TARGET_64BIT")])
- means that the ':DI' expansion only applies if 'TARGET_64BIT' but that
-the ':SI' expansion has no such constraint.
+ means that the `:DI' expansion only applies if `TARGET_64BIT' but that
+the `:SI' expansion has no such constraint.
Iterators are applied in the order they are defined. This can be
significant if two iterators are used in a construct that requires
@@ -27074,25 +27466,25 @@ File: gccint.info, Node: Substitutions, Next: Examples, Prev: Defining Mode I
16.23.1.2 Substitution in Mode Iterators
........................................
-If an '.md' file construct uses mode iterators, each version of the
+If an `.md' file construct uses mode iterators, each version of the
construct will often need slightly different strings or modes. For
example:
- * When a 'define_expand' defines several 'addM3' patterns (*note
+ * When a `define_expand' defines several `addM3' patterns (*note
Standard Names::), each expander will need to use the appropriate
mode name for M.
- * When a 'define_insn' defines several instruction patterns, each
+ * When a `define_insn' defines several instruction patterns, each
instruction will often use a different assembler mnemonic.
- * When a 'define_insn' requires operands with different modes, using
+ * When a `define_insn' requires operands with different modes, using
an iterator for one of the operand modes usually requires a
specific mode for the other operand(s).
GCC supports such variations through a system of "mode attributes".
-There are two standard attributes: 'mode', which is the name of the mode
-in lower case, and 'MODE', which is the same thing in upper case. You
-can define other attributes using:
+There are two standard attributes: `mode', which is the name of the
+mode in lower case, and `MODE', which is the same thing in upper case.
+You can define other attributes using:
(define_mode_attr NAME [(MODE1 "VALUE1") ... (MODEN "VALUEN")])
@@ -27100,19 +27492,19 @@ can define other attributes using:
associated with MODEI.
When GCC replaces some :ITERATOR with :MODE, it will scan each string
-and mode in the pattern for sequences of the form '<ITERATOR:ATTR>',
-where ATTR is the name of a mode attribute. If the attribute is defined
-for MODE, the whole '<...>' sequence will be replaced by the appropriate
-attribute value.
+and mode in the pattern for sequences of the form `<ITERATOR:ATTR>',
+where ATTR is the name of a mode attribute. If the attribute is
+defined for MODE, the whole `<...>' sequence will be replaced by the
+appropriate attribute value.
- For example, suppose an '.md' file has:
+ For example, suppose an `.md' file has:
(define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")])
(define_mode_attr load [(SI "lw") (DI "ld")])
- If one of the patterns that uses ':P' contains the string
-'"<P:load>\t%0,%1"', the 'SI' version of that pattern will use
-'"lw\t%0,%1"' and the 'DI' version will use '"ld\t%0,%1"'.
+ If one of the patterns that uses `:P' contains the string
+`"<P:load>\t%0,%1"', the `SI' version of that pattern will use
+`"lw\t%0,%1"' and the `DI' version will use `"ld\t%0,%1"'.
Here is an example of using an attribute for a mode:
@@ -27121,7 +27513,7 @@ attribute value.
(define_insn ...
(sign_extend:LONG (match_operand:<LONG:SHORT> ...)) ...)
- The 'ITERATOR:' prefix may be omitted, in which case the substitution
+ The `ITERATOR:' prefix may be omitted, in which case the substitution
will be attempted for every iterator expansion.

@@ -27136,7 +27528,7 @@ and attributes (among others):
(define_mode_iterator GPR [SI (DI "TARGET_64BIT")])
(define_mode_attr d [(SI "") (DI "d")])
- and uses the following template to define both 'subsi3' and 'subdi3':
+ and uses the following template to define both `subsi3' and `subdi3':
(define_insn "sub<mode>3"
[(set (match_operand:GPR 0 "register_operand" "=d")
@@ -27189,8 +27581,8 @@ times, once with all uses of NAME replaced by CODE1, once with all uses
replaced by CODE2, and so on. *Note Defining Mode Iterators::.
It is possible to define attributes for codes as well as for modes.
-There are two standard code attributes: 'code', the name of the code in
-lower case, and 'CODE', the name of the code in upper case. Other
+There are two standard code attributes: `code', the name of the code in
+lower case, and `CODE', the name of the code in upper case. Other
attributes are defined using:
(define_code_attr NAME [(CODE1 "VALUE1") ... (CODEN "VALUEN")])
@@ -27254,15 +27646,16 @@ Iterators::.
(define_int_iterator NAME [(INT1 "COND1") ... (INTN "CONDN")])
- defines a pseudo integer constant NAME that can be instantiated as INTI
-if condition CONDI is true. Each INT must have the same rtx format.
-*Note RTL Classes::. Int iterators can appear in only those rtx fields
-that have 'i' as the specifier. This means that each INT has to be a
-constant defined using define_constant or define_c_enum.
+ defines a pseudo integer constant NAME that can be instantiated as
+INTI if condition CONDI is true. Each INT must have the same rtx
+format. *Note RTL Classes::. Int iterators can appear in only those
+rtx fields that have 'i' as the specifier. This means that each INT has
+to be a constant defined using define_constant or define_c_enum.
As with mode and code iterators, each pattern that uses NAME will be
-expanded N times, once with all uses of NAME replaced by INT1, once with
-all uses replaced by INT2, and so on. *Note Defining Mode Iterators::.
+expanded N times, once with all uses of NAME replaced by INT1, once
+with all uses replaced by INT2, and so on. *Note Defining Mode
+Iterators::.
It is possible to define attributes for ints as well as for codes and
modes. Attributes are defined using:
@@ -27285,7 +27678,6 @@ modes. Attributes are defined using:
[(set_attr "type" "neon_vqneg_vqabs")]
)
-
This is equivalent to:
(define_insn "neon_vqabs<mode>"
@@ -27308,7 +27700,6 @@ modes. Attributes are defined using:
[(set_attr "type" "neon_vqneg_vqabs")]
)
-

File: gccint.info, Node: Subst Iterators, Prev: Int Iterators, Up: Iterators
@@ -27324,14 +27715,14 @@ used in RTL-pattern.
Subst iterators transform templates in the following way: the templates
are duplicated, the subst-attributes in these templates are replaced
with the corresponding values, and a new attribute is implicitly added
-to the given 'define_insn'/'define_expand'. The name of the added
-attribute matches the name of 'define_subst'. Such attributes are
-declared implicitly, and it is not allowed to have a 'define_attr' named
-as a 'define_subst'.
+to the given `define_insn'/`define_expand'. The name of the added
+attribute matches the name of `define_subst'. Such attributes are
+declared implicitly, and it is not allowed to have a `define_attr'
+named as a `define_subst'.
- Each subst iterator is linked to a 'define_subst'. It is declared
+ Each subst iterator is linked to a `define_subst'. It is declared
implicitly by the first appearance of the corresponding
-'define_subst_attr', and it is not allowed to define it explicitly.
+`define_subst_attr', and it is not allowed to define it explicitly.
Declarations of subst-attributes have the following syntax:
@@ -27340,10 +27731,10 @@ implicitly by the first appearance of the corresponding
"NO-SUBST-VALUE"
"SUBST-APPLIED-VALUE")
- NAME is a string with which the given subst-attribute could be referred
-to.
+ NAME is a string with which the given subst-attribute could be
+referred to.
- SUBST-NAME shows which 'define_subst' should be applied to an
+ SUBST-NAME shows which `define_subst' should be applied to an
RTL-template if the given subst-attribute is present in the
RTL-template.
@@ -27359,24 +27750,24 @@ File: gccint.info, Node: Target Macros, Next: Host Config, Prev: Machine Desc
17 Target Description Macros and Functions
******************************************
-In addition to the file 'MACHINE.md', a machine description includes a C
-header file conventionally given the name 'MACHINE.h' and a C source
-file named 'MACHINE.c'. The header file defines numerous macros that
+In addition to the file `MACHINE.md', a machine description includes a
+C header file conventionally given the name `MACHINE.h' and a C source
+file named `MACHINE.c'. The header file defines numerous macros that
convey the information about the target machine that does not fit into
-the scheme of the '.md' file. The file 'tm.h' should be a link to
-'MACHINE.h'. The header file 'config.h' includes 'tm.h' and most
-compiler source files include 'config.h'. The source file defines a
-variable 'targetm', which is a structure containing pointers to
-functions and data relating to the target machine. 'MACHINE.c' should
+the scheme of the `.md' file. The file `tm.h' should be a link to
+`MACHINE.h'. The header file `config.h' includes `tm.h' and most
+compiler source files include `config.h'. The source file defines a
+variable `targetm', which is a structure containing pointers to
+functions and data relating to the target machine. `MACHINE.c' should
also contain their definitions, if they are not defined elsewhere in
-GCC, and other functions called through the macros defined in the '.h'
+GCC, and other functions called through the macros defined in the `.h'
file.
* Menu:
-* Target Structure:: The 'targetm' variable.
+* Target Structure:: The `targetm' variable.
* Driver:: Controlling how the driver runs the compilation passes.
-* Run-time Target:: Defining '-m' options like '-m68000' and '-m68020'.
+* Run-time Target:: Defining `-m' options like `-m68000' and `-m68020'.
* Per-Function Data:: Defining data structures for per-function information.
* Storage Layout:: Defining sizes and alignments of data.
* Type Layout:: Defining sizes and properties of basic user data types.
@@ -27387,7 +27778,7 @@ file.
* Trampolines:: Code set up at run time to enter a nested function.
* Library Calls:: Controlling how library routines are implicitly called.
* Addressing Modes:: Defining addressing modes valid for memory operands.
-* Anchored Addresses:: Defining how '-fsection-anchors' should work.
+* Anchored Addresses:: Defining how `-fsection-anchors' should work.
* Condition Code:: Defining how insns update the condition code.
* Costs:: Defining relative costs of different operations.
* Scheduling:: Adjusting the behavior of the instruction scheduler.
@@ -27397,7 +27788,7 @@ file.
* Debugging Info:: Defining the format of debugging output.
* Floating Point:: Handling floating point for cross-compilers.
* Mode Switching:: Insertion of mode-switching instructions.
-* Target Attributes:: Defining target-specific uses of '__attribute__'.
+* Target Attributes:: Defining target-specific uses of `__attribute__'.
* Emulated TLS:: Emulated TLS support.
* MIPS Coprocessors:: MIPS coprocessor support and how to customize it.
* PCH Target:: Validity checking for precompiled headers.
@@ -27408,18 +27799,18 @@ file.

File: gccint.info, Node: Target Structure, Next: Driver, Up: Target Macros
-17.1 The Global 'targetm' Variable
+17.1 The Global `targetm' Variable
==================================
-- Variable: struct gcc_target targetm
- The target '.c' file must define the global 'targetm' variable
+ The target `.c' file must define the global `targetm' variable
which contains pointers to functions and data relating to the
- target machine. The variable is declared in 'target.h';
- 'target-def.h' defines the macro 'TARGET_INITIALIZER' which is used
- to initialize the variable, and macros for the default initializers
- for elements of the structure. The '.c' file should override those
- macros for which the default definition is inappropriate. For
- example:
+ target machine. The variable is declared in `target.h';
+ `target-def.h' defines the macro `TARGET_INITIALIZER' which is
+ used to initialize the variable, and macros for the default
+ initializers for elements of the structure. The `.c' file should
+ override those macros for which the default definition is
+ inappropriate. For example:
#include "target.h"
#include "target-def.h"
@@ -27430,31 +27821,31 @@ File: gccint.info, Node: Target Structure, Next: Driver, Up: Target Macros
struct gcc_target targetm = TARGET_INITIALIZER;
- Where a macro should be defined in the '.c' file in this manner to form
-part of the 'targetm' structure, it is documented below as a "Target
+Where a macro should be defined in the `.c' file in this manner to form
+part of the `targetm' structure, it is documented below as a "Target
Hook" with a prototype. Many macros will change in future from being
-defined in the '.h' file to being part of the 'targetm' structure.
+defined in the `.h' file to being part of the `targetm' structure.
- Similarly, there is a 'targetcm' variable for hooks that are specific
+ Similarly, there is a `targetcm' variable for hooks that are specific
to front ends for C-family languages, documented as "C Target Hook".
-This is declared in 'c-family/c-target.h', the initializer
-'TARGETCM_INITIALIZER' in 'c-family/c-target-def.h'. If targets
-initialize 'targetcm' themselves, they should set
-'target_has_targetcm=yes' in 'config.gcc'; otherwise a default
+This is declared in `c-family/c-target.h', the initializer
+`TARGETCM_INITIALIZER' in `c-family/c-target-def.h'. If targets
+initialize `targetcm' themselves, they should set
+`target_has_targetcm=yes' in `config.gcc'; otherwise a default
definition is used.
- Similarly, there is a 'targetm_common' variable for hooks that are
+ Similarly, there is a `targetm_common' variable for hooks that are
shared between the compiler driver and the compilers proper, documented
-as "Common Target Hook". This is declared in 'common/common-target.h',
-the initializer 'TARGETM_COMMON_INITIALIZER' in
-'common/common-target-def.h'. If targets initialize 'targetm_common'
-themselves, they should set 'target_has_targetm_common=yes' in
-'config.gcc'; otherwise a default definition is used.
+as "Common Target Hook". This is declared in `common/common-target.h',
+the initializer `TARGETM_COMMON_INITIALIZER' in
+`common/common-target-def.h'. If targets initialize `targetm_common'
+themselves, they should set `target_has_targetm_common=yes' in
+`config.gcc'; otherwise a default definition is used.

File: gccint.info, Node: Driver, Next: Run-time Target, Prev: Target Structure, Up: Target Macros
-17.2 Controlling the Compilation Driver, 'gcc'
+17.2 Controlling the Compilation Driver, `gcc'
==============================================
You can control the compilation driver.
@@ -27464,11 +27855,11 @@ You can control the compilation driver.
initializer for an array of strings, with no surrounding braces.
The driver applies these specs to its own command line between
- loading default 'specs' files (but not command-line specified ones)
- and choosing the multilib directory or running any subcommands. It
- applies them in the order given, so each spec can depend on the
- options added by earlier ones. It is also possible to remove
- options using '%<OPTION' in the usual way.
+ loading default `specs' files (but not command-line specified
+ ones) and choosing the multilib directory or running any
+ subcommands. It applies them in the order given, so each spec can
+ depend on the options added by earlier ones. It is also possible
+ to remove options using `%<OPTION' in the usual way.
This macro can be useful when a port has several interdependent
target options. It provides a way of standardizing the command
@@ -27478,49 +27869,49 @@ You can control the compilation driver.
-- Macro: OPTION_DEFAULT_SPECS
A list of specs used to support configure-time default options
- (i.e. '--with' options) in the driver. It should be a suitable
+ (i.e. `--with' options) in the driver. It should be a suitable
initializer for an array of structures, each containing two
strings, without the outermost pair of surrounding braces.
The first item in the pair is the name of the default. This must
- match the code in 'config.gcc' for the target. The second item is
+ match the code in `config.gcc' for the target. The second item is
a spec to apply if a default with this name was specified. The
- string '%(VALUE)' in the spec will be replaced by the value of the
+ string `%(VALUE)' in the spec will be replaced by the value of the
default everywhere it occurs.
The driver will apply these specs to its own command line between
- loading default 'specs' files and processing 'DRIVER_SELF_SPECS',
- using the same mechanism as 'DRIVER_SELF_SPECS'.
+ loading default `specs' files and processing `DRIVER_SELF_SPECS',
+ using the same mechanism as `DRIVER_SELF_SPECS'.
Do not define this macro if it does not need to do anything.
-- Macro: CPP_SPEC
A C string constant that tells the GCC driver program options to
- pass to CPP. It can also specify how to translate options you give
- to GCC into options for GCC to pass to the CPP.
+ pass to CPP. It can also specify how to translate options you
+ give to GCC into options for GCC to pass to the CPP.
Do not define this macro if it does not need to do anything.
-- Macro: CPLUSPLUS_CPP_SPEC
- This macro is just like 'CPP_SPEC', but is used for C++, rather
+ This macro is just like `CPP_SPEC', but is used for C++, rather
than C. If you do not define this macro, then the value of
- 'CPP_SPEC' (if any) will be used instead.
+ `CPP_SPEC' (if any) will be used instead.
-- Macro: CC1_SPEC
A C string constant that tells the GCC driver program options to
- pass to 'cc1', 'cc1plus', 'f771', and the other language front
- ends. It can also specify how to translate options you give to GCC
- into options for GCC to pass to front ends.
+ pass to `cc1', `cc1plus', `f771', and the other language front
+ ends. It can also specify how to translate options you give to
+ GCC into options for GCC to pass to front ends.
Do not define this macro if it does not need to do anything.
-- Macro: CC1PLUS_SPEC
A C string constant that tells the GCC driver program options to
- pass to 'cc1plus'. It can also specify how to translate options
- you give to GCC into options for GCC to pass to the 'cc1plus'.
+ pass to `cc1plus'. It can also specify how to translate options
+ you give to GCC into options for GCC to pass to the `cc1plus'.
Do not define this macro if it does not need to do anything. Note
- that everything defined in CC1_SPEC is already passed to 'cc1plus'
+ that everything defined in CC1_SPEC is already passed to `cc1plus'
so there is no need to duplicate the contents of CC1_SPEC in
CC1PLUS_SPEC.
@@ -27528,28 +27919,28 @@ You can control the compilation driver.
A C string constant that tells the GCC driver program options to
pass to the assembler. It can also specify how to translate
options you give to GCC into options for GCC to pass to the
- assembler. See the file 'sun3.h' for an example of this.
+ assembler. See the file `sun3.h' for an example of this.
Do not define this macro if it does not need to do anything.
-- Macro: ASM_FINAL_SPEC
A C string constant that tells the GCC driver program how to run
any programs which cleanup after the normal assembler. Normally,
- this is not needed. See the file 'mips.h' for an example of this.
+ this is not needed. See the file `mips.h' for an example of this.
Do not define this macro if it does not need to do anything.
-- Macro: AS_NEEDS_DASH_FOR_PIPED_INPUT
Define this macro, with no value, if the driver should give the
- assembler an argument consisting of a single dash, '-', to instruct
- it to read from its standard input (which will be a pipe connected
- to the output of the compiler proper). This argument is given
- after any '-o' option specifying the name of the output file.
+ assembler an argument consisting of a single dash, `-', to
+ instruct it to read from its standard input (which will be a pipe
+ connected to the output of the compiler proper). This argument is
+ given after any `-o' option specifying the name of the output file.
If you do not define this macro, the assembler is assumed to read
its standard input if given no non-option arguments. If your
- assembler cannot read standard input at all, use a '%{pipe:%e}'
- construct; see 'mips.h' for instance.
+ assembler cannot read standard input at all, use a `%{pipe:%e}'
+ construct; see `mips.h' for instance.
-- Macro: LINK_SPEC
A C string constant that tells the GCC driver program options to
@@ -27559,68 +27950,68 @@ You can control the compilation driver.
Do not define this macro if it does not need to do anything.
-- Macro: LIB_SPEC
- Another C string constant used much like 'LINK_SPEC'. The
- difference between the two is that 'LIB_SPEC' is used at the end of
- the command given to the linker.
+ Another C string constant used much like `LINK_SPEC'. The
+ difference between the two is that `LIB_SPEC' is used at the end
+ of the command given to the linker.
If this macro is not defined, a default is provided that loads the
- standard C library from the usual place. See 'gcc.c'.
+ standard C library from the usual place. See `gcc.c'.
-- Macro: LIBGCC_SPEC
- Another C string constant that tells the GCC driver program how and
- when to place a reference to 'libgcc.a' into the linker command
- line. This constant is placed both before and after the value of
- 'LIB_SPEC'.
+ Another C string constant that tells the GCC driver program how
+ and when to place a reference to `libgcc.a' into the linker
+ command line. This constant is placed both before and after the
+ value of `LIB_SPEC'.
If this macro is not defined, the GCC driver provides a default
- that passes the string '-lgcc' to the linker.
+ that passes the string `-lgcc' to the linker.
-- Macro: REAL_LIBGCC_SPEC
- By default, if 'ENABLE_SHARED_LIBGCC' is defined, the 'LIBGCC_SPEC'
- is not directly used by the driver program but is instead modified
- to refer to different versions of 'libgcc.a' depending on the
- values of the command line flags '-static', '-shared',
- '-static-libgcc', and '-shared-libgcc'. On targets where these
- modifications are inappropriate, define 'REAL_LIBGCC_SPEC' instead.
- 'REAL_LIBGCC_SPEC' tells the driver how to place a reference to
- 'libgcc' on the link command line, but, unlike 'LIBGCC_SPEC', it is
- used unmodified.
+ By default, if `ENABLE_SHARED_LIBGCC' is defined, the
+ `LIBGCC_SPEC' is not directly used by the driver program but is
+ instead modified to refer to different versions of `libgcc.a'
+ depending on the values of the command line flags `-static',
+ `-shared', `-static-libgcc', and `-shared-libgcc'. On targets
+ where these modifications are inappropriate, define
+ `REAL_LIBGCC_SPEC' instead. `REAL_LIBGCC_SPEC' tells the driver
+ how to place a reference to `libgcc' on the link command line,
+ but, unlike `LIBGCC_SPEC', it is used unmodified.
-- Macro: USE_LD_AS_NEEDED
- A macro that controls the modifications to 'LIBGCC_SPEC' mentioned
- in 'REAL_LIBGCC_SPEC'. If nonzero, a spec will be generated that
- uses '--as-needed' or equivalent options and the shared 'libgcc' in
- place of the static exception handler library, when linking without
- any of '-static', '-static-libgcc', or '-shared-libgcc'.
+ A macro that controls the modifications to `LIBGCC_SPEC' mentioned
+ in `REAL_LIBGCC_SPEC'. If nonzero, a spec will be generated that
+ uses `--as-needed' or equivalent options and the shared `libgcc'
+ in place of the static exception handler library, when linking
+ without any of `-static', `-static-libgcc', or `-shared-libgcc'.
-- Macro: LINK_EH_SPEC
- If defined, this C string constant is added to 'LINK_SPEC'. When
- 'USE_LD_AS_NEEDED' is zero or undefined, it also affects the
- modifications to 'LIBGCC_SPEC' mentioned in 'REAL_LIBGCC_SPEC'.
+ If defined, this C string constant is added to `LINK_SPEC'. When
+ `USE_LD_AS_NEEDED' is zero or undefined, it also affects the
+ modifications to `LIBGCC_SPEC' mentioned in `REAL_LIBGCC_SPEC'.
-- Macro: STARTFILE_SPEC
- Another C string constant used much like 'LINK_SPEC'. The
- difference between the two is that 'STARTFILE_SPEC' is used at the
+ Another C string constant used much like `LINK_SPEC'. The
+ difference between the two is that `STARTFILE_SPEC' is used at the
very beginning of the command given to the linker.
If this macro is not defined, a default is provided that loads the
- standard C startup file from the usual place. See 'gcc.c'.
+ standard C startup file from the usual place. See `gcc.c'.
-- Macro: ENDFILE_SPEC
- Another C string constant used much like 'LINK_SPEC'. The
- difference between the two is that 'ENDFILE_SPEC' is used at the
+ Another C string constant used much like `LINK_SPEC'. The
+ difference between the two is that `ENDFILE_SPEC' is used at the
very end of the command given to the linker.
Do not define this macro if it does not need to do anything.
-- Macro: THREAD_MODEL_SPEC
- GCC '-v' will print the thread model GCC was configured to use.
+ GCC `-v' will print the thread model GCC was configured to use.
However, this doesn't work on platforms that are multilibbed on
thread models, such as AIX 4.3. On such platforms, define
- 'THREAD_MODEL_SPEC' such that it evaluates to a string without
- blanks that names one of the recognized thread models. '%*', the
+ `THREAD_MODEL_SPEC' such that it evaluates to a string without
+ blanks that names one of the recognized thread models. `%*', the
default value of this macro, will expand to the value of
- 'thread_file' set in 'config.gcc'.
+ `thread_file' set in `config.gcc'.
-- Macro: SYSROOT_SUFFIX_SPEC
Define this macro to add a suffix to the target sysroot when GCC is
@@ -27629,14 +28020,14 @@ You can control the compilation driver.
-- Macro: SYSROOT_HEADERS_SUFFIX_SPEC
Define this macro to add a headers_suffix to the target sysroot
- when GCC is configured with a sysroot. This will cause GCC to pass
- the updated sysroot+headers_suffix to CPP, causing it to search for
- usr/include, et al, within sysroot+headers_suffix.
+ when GCC is configured with a sysroot. This will cause GCC to
+ pass the updated sysroot+headers_suffix to CPP, causing it to
+ search for usr/include, et al, within sysroot+headers_suffix.
-- Macro: EXTRA_SPECS
Define this macro to provide additional specifications to put in
- the 'specs' file that can be used in various specifications like
- 'CC1_SPEC'.
+ the `specs' file that can be used in various specifications like
+ `CC1_SPEC'.
The definition should be an initializer for an array of structures,
containing a string constant, that defines the specification name,
@@ -27644,24 +28035,24 @@ You can control the compilation driver.
Do not define this macro if it does not need to do anything.
- 'EXTRA_SPECS' is useful when an architecture contains several
- related targets, which have various '..._SPECS' which are similar
+ `EXTRA_SPECS' is useful when an architecture contains several
+ related targets, which have various `..._SPECS' which are similar
to each other, and the maintainer would like one central place to
keep these definitions.
- For example, the PowerPC System V.4 targets use 'EXTRA_SPECS' to
- define either '_CALL_SYSV' when the System V calling sequence is
- used or '_CALL_AIX' when the older AIX-based calling sequence is
+ For example, the PowerPC System V.4 targets use `EXTRA_SPECS' to
+ define either `_CALL_SYSV' when the System V calling sequence is
+ used or `_CALL_AIX' when the older AIX-based calling sequence is
used.
- The 'config/rs6000/rs6000.h' target file defines:
+ The `config/rs6000/rs6000.h' target file defines:
#define EXTRA_SPECS \
{ "cpp_sysv_default", CPP_SYSV_DEFAULT },
#define CPP_SYS_DEFAULT ""
- The 'config/rs6000/sysv.h' target file defines:
+ The `config/rs6000/sysv.h' target file defines:
#undef CPP_SPEC
#define CPP_SPEC \
"%{posix: -D_POSIX_SOURCE } \
@@ -27672,83 +28063,83 @@ You can control the compilation driver.
#undef CPP_SYSV_DEFAULT
#define CPP_SYSV_DEFAULT "-D_CALL_SYSV"
- while the 'config/rs6000/eabiaix.h' target file defines
- 'CPP_SYSV_DEFAULT' as:
+ while the `config/rs6000/eabiaix.h' target file defines
+ `CPP_SYSV_DEFAULT' as:
#undef CPP_SYSV_DEFAULT
#define CPP_SYSV_DEFAULT "-D_CALL_AIX"
-- Macro: LINK_LIBGCC_SPECIAL_1
Define this macro if the driver program should find the library
- 'libgcc.a'. If you do not define this macro, the driver program
- will pass the argument '-lgcc' to tell the linker to do the search.
+ `libgcc.a'. If you do not define this macro, the driver program
+ will pass the argument `-lgcc' to tell the linker to do the search.
-- Macro: LINK_GCC_C_SEQUENCE_SPEC
The sequence in which libgcc and libc are specified to the linker.
- By default this is '%G %L %G'.
+ By default this is `%G %L %G'.
-- Macro: LINK_COMMAND_SPEC
A C string constant giving the complete command line need to
- execute the linker. When you do this, you will need to update your
- port each time a change is made to the link command line within
- 'gcc.c'. Therefore, define this macro only if you need to
+ execute the linker. When you do this, you will need to update
+ your port each time a change is made to the link command line
+ within `gcc.c'. Therefore, define this macro only if you need to
completely redefine the command line for invoking the linker and
there is no other way to accomplish the effect you need.
Overriding this macro may be avoidable by overriding
- 'LINK_GCC_C_SEQUENCE_SPEC' instead.
+ `LINK_GCC_C_SEQUENCE_SPEC' instead.
-- Common Target Hook: bool TARGET_ALWAYS_STRIP_DOTDOT
- True if '..' components should always be removed from directory
+ True if `..' components should always be removed from directory
names computed relative to GCC's internal directories, false
(default) if such components should be preserved and directory
names containing them passed to other tools such as the linker.
-- Macro: MULTILIB_DEFAULTS
- Define this macro as a C expression for the initializer of an array
- of string to tell the driver program which options are defaults for
- this target and thus do not need to be handled specially when using
- 'MULTILIB_OPTIONS'.
+ Define this macro as a C expression for the initializer of an
+ array of string to tell the driver program which options are
+ defaults for this target and thus do not need to be handled
+ specially when using `MULTILIB_OPTIONS'.
- Do not define this macro if 'MULTILIB_OPTIONS' is not defined in
+ Do not define this macro if `MULTILIB_OPTIONS' is not defined in
the target makefile fragment or if none of the options listed in
- 'MULTILIB_OPTIONS' are set by default. *Note Target Fragment::.
+ `MULTILIB_OPTIONS' are set by default. *Note Target Fragment::.
-- Macro: RELATIVE_PREFIX_NOT_LINKDIR
- Define this macro to tell 'gcc' that it should only translate a
- '-B' prefix into a '-L' linker option if the prefix indicates an
+ Define this macro to tell `gcc' that it should only translate a
+ `-B' prefix into a `-L' linker option if the prefix indicates an
absolute file name.
-- Macro: MD_EXEC_PREFIX
If defined, this macro is an additional prefix to try after
- 'STANDARD_EXEC_PREFIX'. 'MD_EXEC_PREFIX' is not searched when the
+ `STANDARD_EXEC_PREFIX'. `MD_EXEC_PREFIX' is not searched when the
compiler is built as a cross compiler. If you define
- 'MD_EXEC_PREFIX', then be sure to add it to the list of directories
- used to find the assembler in 'configure.in'.
+ `MD_EXEC_PREFIX', then be sure to add it to the list of
+ directories used to find the assembler in `configure.in'.
-- Macro: STANDARD_STARTFILE_PREFIX
Define this macro as a C string constant if you wish to override
- the standard choice of 'libdir' as the default prefix to try when
- searching for startup files such as 'crt0.o'.
- 'STANDARD_STARTFILE_PREFIX' is not searched when the compiler is
+ the standard choice of `libdir' as the default prefix to try when
+ searching for startup files such as `crt0.o'.
+ `STANDARD_STARTFILE_PREFIX' is not searched when the compiler is
built as a cross compiler.
-- Macro: STANDARD_STARTFILE_PREFIX_1
Define this macro as a C string constant if you wish to override
- the standard choice of '/lib' as a prefix to try after the default
- prefix when searching for startup files such as 'crt0.o'.
- 'STANDARD_STARTFILE_PREFIX_1' is not searched when the compiler is
+ the standard choice of `/lib' as a prefix to try after the default
+ prefix when searching for startup files such as `crt0.o'.
+ `STANDARD_STARTFILE_PREFIX_1' is not searched when the compiler is
built as a cross compiler.
-- Macro: STANDARD_STARTFILE_PREFIX_2
Define this macro as a C string constant if you wish to override
- the standard choice of '/lib' as yet another prefix to try after
+ the standard choice of `/lib' as yet another prefix to try after
the default prefix when searching for startup files such as
- 'crt0.o'. 'STANDARD_STARTFILE_PREFIX_2' is not searched when the
+ `crt0.o'. `STANDARD_STARTFILE_PREFIX_2' is not searched when the
compiler is built as a cross compiler.
-- Macro: MD_STARTFILE_PREFIX
If defined, this macro supplies an additional prefix to try after
- the standard prefixes. 'MD_EXEC_PREFIX' is not searched when the
+ the standard prefixes. `MD_EXEC_PREFIX' is not searched when the
compiler is built as a cross compiler.
-- Macro: MD_STARTFILE_PREFIX_1
@@ -27760,45 +28151,45 @@ You can control the compilation driver.
Define this macro as a C string constant if you wish to set
environment variables for programs called by the driver, such as
the assembler and loader. The driver passes the value of this
- macro to 'putenv' to initialize the necessary environment
+ macro to `putenv' to initialize the necessary environment
variables.
-- Macro: LOCAL_INCLUDE_DIR
Define this macro as a C string constant if you wish to override
- the standard choice of '/usr/local/include' as the default prefix
- to try when searching for local header files. 'LOCAL_INCLUDE_DIR'
- comes before 'NATIVE_SYSTEM_HEADER_DIR' (set in 'config.gcc',
- normally '/usr/include') in the search order.
+ the standard choice of `/usr/local/include' as the default prefix
+ to try when searching for local header files. `LOCAL_INCLUDE_DIR'
+ comes before `NATIVE_SYSTEM_HEADER_DIR' (set in `config.gcc',
+ normally `/usr/include') in the search order.
- Cross compilers do not search either '/usr/local/include' or its
+ Cross compilers do not search either `/usr/local/include' or its
replacement.
-- Macro: NATIVE_SYSTEM_HEADER_COMPONENT
- The "component" corresponding to 'NATIVE_SYSTEM_HEADER_DIR'. See
- 'INCLUDE_DEFAULTS', below, for the description of components. If
+ The "component" corresponding to `NATIVE_SYSTEM_HEADER_DIR'. See
+ `INCLUDE_DEFAULTS', below, for the description of components. If
you do not define this macro, no component is used.
-- Macro: INCLUDE_DEFAULTS
- Define this macro if you wish to override the entire default search
- path for include files. For a native compiler, the default search
- path usually consists of 'GCC_INCLUDE_DIR', 'LOCAL_INCLUDE_DIR',
- 'GPLUSPLUS_INCLUDE_DIR', and 'NATIVE_SYSTEM_HEADER_DIR'. In
- addition, 'GPLUSPLUS_INCLUDE_DIR' and 'GCC_INCLUDE_DIR' are defined
- automatically by 'Makefile', and specify private search areas for
- GCC. The directory 'GPLUSPLUS_INCLUDE_DIR' is used only for C++
- programs.
+ Define this macro if you wish to override the entire default
+ search path for include files. For a native compiler, the default
+ search path usually consists of `GCC_INCLUDE_DIR',
+ `LOCAL_INCLUDE_DIR', `GPLUSPLUS_INCLUDE_DIR', and
+ `NATIVE_SYSTEM_HEADER_DIR'. In addition, `GPLUSPLUS_INCLUDE_DIR'
+ and `GCC_INCLUDE_DIR' are defined automatically by `Makefile', and
+ specify private search areas for GCC. The directory
+ `GPLUSPLUS_INCLUDE_DIR' is used only for C++ programs.
The definition should be an initializer for an array of structures.
Each array element should have four elements: the directory name (a
string constant), the component name (also a string constant), a
- flag for C++-only directories, and a flag showing that the includes
- in the directory don't need to be wrapped in 'extern 'C'' when
- compiling C++. Mark the end of the array with a null element.
+ flag for C++-only directories, and a flag showing that the
+ includes in the directory don't need to be wrapped in `extern `C''
+ when compiling C++. Mark the end of the array with a null element.
The component name denotes what GNU package the include file is
part of, if any, in all uppercase letters. For example, it might
- be 'GCC' or 'BINUTILS'. If the package is part of a
- vendor-supplied operating system, code the component name as '0'.
+ be `GCC' or `BINUTILS'. If the package is part of a
+ vendor-supplied operating system, code the component name as `0'.
For example, here is the definition used for VAX/VMS:
@@ -27813,66 +28204,66 @@ You can control the compilation driver.
Here is the order of prefixes tried for exec files:
- 1. Any prefixes specified by the user with '-B'.
+ 1. Any prefixes specified by the user with `-B'.
- 2. The environment variable 'GCC_EXEC_PREFIX' or, if 'GCC_EXEC_PREFIX'
+ 2. The environment variable `GCC_EXEC_PREFIX' or, if `GCC_EXEC_PREFIX'
is not set and the compiler has not been installed in the
configure-time PREFIX, the location in which the compiler has
actually been installed.
3. The directories specified by the environment variable
- 'COMPILER_PATH'.
+ `COMPILER_PATH'.
- 4. The macro 'STANDARD_EXEC_PREFIX', if the compiler has been
+ 4. The macro `STANDARD_EXEC_PREFIX', if the compiler has been
installed in the configured-time PREFIX.
- 5. The location '/usr/libexec/gcc/', but only if this is a native
+ 5. The location `/usr/libexec/gcc/', but only if this is a native
compiler.
- 6. The location '/usr/lib/gcc/', but only if this is a native
+ 6. The location `/usr/lib/gcc/', but only if this is a native
compiler.
- 7. The macro 'MD_EXEC_PREFIX', if defined, but only if this is a
+ 7. The macro `MD_EXEC_PREFIX', if defined, but only if this is a
native compiler.
Here is the order of prefixes tried for startfiles:
- 1. Any prefixes specified by the user with '-B'.
+ 1. Any prefixes specified by the user with `-B'.
- 2. The environment variable 'GCC_EXEC_PREFIX' or its automatically
+ 2. The environment variable `GCC_EXEC_PREFIX' or its automatically
determined value based on the installed toolchain location.
3. The directories specified by the environment variable
- 'LIBRARY_PATH' (or port-specific name; native only, cross compilers
- do not use this).
+ `LIBRARY_PATH' (or port-specific name; native only, cross
+ compilers do not use this).
- 4. The macro 'STANDARD_EXEC_PREFIX', but only if the toolchain is
+ 4. The macro `STANDARD_EXEC_PREFIX', but only if the toolchain is
installed in the configured PREFIX or this is a native compiler.
- 5. The location '/usr/lib/gcc/', but only if this is a native
+ 5. The location `/usr/lib/gcc/', but only if this is a native
compiler.
- 6. The macro 'MD_EXEC_PREFIX', if defined, but only if this is a
+ 6. The macro `MD_EXEC_PREFIX', if defined, but only if this is a
native compiler.
- 7. The macro 'MD_STARTFILE_PREFIX', if defined, but only if this is a
+ 7. The macro `MD_STARTFILE_PREFIX', if defined, but only if this is a
native compiler, or we have a target system root.
- 8. The macro 'MD_STARTFILE_PREFIX_1', if defined, but only if this is
+ 8. The macro `MD_STARTFILE_PREFIX_1', if defined, but only if this is
a native compiler, or we have a target system root.
- 9. The macro 'STANDARD_STARTFILE_PREFIX', with any sysroot
+ 9. The macro `STANDARD_STARTFILE_PREFIX', with any sysroot
modifications. If this path is relative it will be prefixed by
- 'GCC_EXEC_PREFIX' and the machine suffix or 'STANDARD_EXEC_PREFIX'
+ `GCC_EXEC_PREFIX' and the machine suffix or `STANDARD_EXEC_PREFIX'
and the machine suffix.
- 10. The macro 'STANDARD_STARTFILE_PREFIX_1', but only if this is a
- native compiler, or we have a target system root. The default for
- this macro is '/lib/'.
+ 10. The macro `STANDARD_STARTFILE_PREFIX_1', but only if this is a
+ native compiler, or we have a target system root. The default for
+ this macro is `/lib/'.
- 11. The macro 'STANDARD_STARTFILE_PREFIX_2', but only if this is a
- native compiler, or we have a target system root. The default for
- this macro is '/usr/lib/'.
+ 11. The macro `STANDARD_STARTFILE_PREFIX_2', but only if this is a
+ native compiler, or we have a target system root. The default for
+ this macro is `/usr/lib/'.

File: gccint.info, Node: Run-time Target, Next: Per-Function Data, Prev: Driver, Up: Target Macros
@@ -27885,113 +28276,113 @@ Here are run-time target specifications.
-- Macro: TARGET_CPU_CPP_BUILTINS ()
This function-like macro expands to a block of code that defines
built-in preprocessor macros and assertions for the target CPU,
- using the functions 'builtin_define', 'builtin_define_std' and
- 'builtin_assert'. When the front end calls this macro it provides
- a trailing semicolon, and since it has finished command line option
- processing your code can use those results freely.
+ using the functions `builtin_define', `builtin_define_std' and
+ `builtin_assert'. When the front end calls this macro it provides
+ a trailing semicolon, and since it has finished command line
+ option processing your code can use those results freely.
- 'builtin_assert' takes a string in the form you pass to the
- command-line option '-A', such as 'cpu=mips', and creates the
- assertion. 'builtin_define' takes a string in the form accepted by
- option '-D' and unconditionally defines the macro.
+ `builtin_assert' takes a string in the form you pass to the
+ command-line option `-A', such as `cpu=mips', and creates the
+ assertion. `builtin_define' takes a string in the form accepted
+ by option `-D' and unconditionally defines the macro.
- 'builtin_define_std' takes a string representing the name of an
+ `builtin_define_std' takes a string representing the name of an
object-like macro. If it doesn't lie in the user's namespace,
- 'builtin_define_std' defines it unconditionally. Otherwise, it
+ `builtin_define_std' defines it unconditionally. Otherwise, it
defines a version with two leading underscores, and another version
with two leading and trailing underscores, and defines the original
only if an ISO standard was not requested on the command line. For
- example, passing 'unix' defines '__unix', '__unix__' and possibly
- 'unix'; passing '_mips' defines '__mips', '__mips__' and possibly
- '_mips', and passing '_ABI64' defines only '_ABI64'.
+ example, passing `unix' defines `__unix', `__unix__' and possibly
+ `unix'; passing `_mips' defines `__mips', `__mips__' and possibly
+ `_mips', and passing `_ABI64' defines only `_ABI64'.
You can also test for the C dialect being compiled. The variable
- 'c_language' is set to one of 'clk_c', 'clk_cplusplus' or
- 'clk_objective_c'. Note that if we are preprocessing assembler,
- this variable will be 'clk_c' but the function-like macro
- 'preprocessing_asm_p()' will return true, so you might want to
+ `c_language' is set to one of `clk_c', `clk_cplusplus' or
+ `clk_objective_c'. Note that if we are preprocessing assembler,
+ this variable will be `clk_c' but the function-like macro
+ `preprocessing_asm_p()' will return true, so you might want to
check for that first. If you need to check for strict ANSI, the
- variable 'flag_iso' can be used. The function-like macro
- 'preprocessing_trad_p()' can be used to check for traditional
+ variable `flag_iso' can be used. The function-like macro
+ `preprocessing_trad_p()' can be used to check for traditional
preprocessing.
-- Macro: TARGET_OS_CPP_BUILTINS ()
- Similarly to 'TARGET_CPU_CPP_BUILTINS' but this macro is optional
+ Similarly to `TARGET_CPU_CPP_BUILTINS' but this macro is optional
and is used for the target operating system instead.
-- Macro: TARGET_OBJFMT_CPP_BUILTINS ()
- Similarly to 'TARGET_CPU_CPP_BUILTINS' but this macro is optional
- and is used for the target object format. 'elfos.h' uses this
- macro to define '__ELF__', so you probably do not need to define it
- yourself.
+ Similarly to `TARGET_CPU_CPP_BUILTINS' but this macro is optional
+ and is used for the target object format. `elfos.h' uses this
+ macro to define `__ELF__', so you probably do not need to define
+ it yourself.
-- Variable: extern int target_flags
- This variable is declared in 'options.h', which is included before
+ This variable is declared in `options.h', which is included before
any target-specific headers.
-- Common Target Hook: int TARGET_DEFAULT_TARGET_FLAGS
- This variable specifies the initial value of 'target_flags'. Its
+ This variable specifies the initial value of `target_flags'. Its
default setting is 0.
-- Common Target Hook: bool TARGET_HANDLE_OPTION (struct gcc_options
*OPTS, struct gcc_options *OPTS_SET, const struct
cl_decoded_option *DECODED, location_t LOC)
This hook is called whenever the user specifies one of the
- target-specific options described by the '.opt' definition files
+ target-specific options described by the `.opt' definition files
(*note Options::). It has the opportunity to do some
option-specific processing and should return true if the option is
valid. The default definition does nothing but return true.
DECODED specifies the option and its arguments. OPTS and OPTS_SET
- are the 'gcc_options' structures to be used for storing option
+ are the `gcc_options' structures to be used for storing option
state, and LOC is the location at which the option was passed
- ('UNKNOWN_LOCATION' except for options passed via attributes).
+ (`UNKNOWN_LOCATION' except for options passed via attributes).
-- C Target Hook: bool TARGET_HANDLE_C_OPTION (size_t CODE, const char
*ARG, int VALUE)
This target hook is called whenever the user specifies one of the
- target-specific C language family options described by the '.opt'
+ target-specific C language family options described by the `.opt'
definition files(*note Options::). It has the opportunity to do
some option-specific processing and should return true if the
option is valid. The arguments are like for
- 'TARGET_HANDLE_OPTION'. The default definition does nothing but
+ `TARGET_HANDLE_OPTION'. The default definition does nothing but
return false.
- In general, you should use 'TARGET_HANDLE_OPTION' to handle
+ In general, you should use `TARGET_HANDLE_OPTION' to handle
options. However, if processing an option requires routines that
- are only available in the C (and related language) front ends, then
- you should use 'TARGET_HANDLE_C_OPTION' instead.
+ are only available in the C (and related language) front ends,
+ then you should use `TARGET_HANDLE_C_OPTION' instead.
-- C Target Hook: tree TARGET_OBJC_CONSTRUCT_STRING_OBJECT (tree
STRING)
Targets may provide a string object type that can be used within
- and between C, C++ and their respective Objective-C dialects. A
+ and between C, C++ and their respective Objective-C dialects. A
string object might, for example, embed encoding and length
- information. These objects are considered opaque to the compiler
- and handled as references. An ideal implementation makes the
+ information. These objects are considered opaque to the compiler
+ and handled as references. An ideal implementation makes the
composition of the string object match that of the Objective-C
- 'NSString' ('NXString' for GNUStep), allowing efficient
- interworking between C-only and Objective-C code. If a target
+ `NSString' (`NXString' for GNUStep), allowing efficient
+ interworking between C-only and Objective-C code. If a target
implements string objects then this hook should return a reference
- to such an object constructed from the normal 'C' string
- representation provided in STRING. At present, the hook is used by
+ to such an object constructed from the normal `C' string
+ representation provided in STRING. At present, the hook is used by
Objective-C only, to obtain a common-format string object when the
target provides one.
-- C Target Hook: void TARGET_OBJC_DECLARE_UNRESOLVED_CLASS_REFERENCE
(const char *CLASSNAME)
- Declare that Objective C class CLASSNAME is referenced by the
+ Declare that Objective C class CLASSNAME is referenced by the
current TU.
- -- C Target Hook: void TARGET_OBJC_DECLARE_CLASS_DEFINITION (const char
- *CLASSNAME)
- Declare that Objective C class CLASSNAME is defined by the current
- TU.
+ -- C Target Hook: void TARGET_OBJC_DECLARE_CLASS_DEFINITION (const
+ char *CLASSNAME)
+ Declare that Objective C class CLASSNAME is defined by the
+ current TU.
-- C Target Hook: bool TARGET_STRING_OBJECT_REF_TYPE_P (const_tree
STRINGREF)
If a target implements string objects then this hook should return
- 'true' if STRINGREF is a valid reference to such an object.
+ `true' if STRINGREF is a valid reference to such an object.
-- C Target Hook: void TARGET_CHECK_STRING_OBJECT_FORMAT_ARG (tree
FORMAT_ARG, tree ARGS_LIST)
@@ -28002,48 +28393,48 @@ Here are run-time target specifications.
-- Target Hook: void TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE (void)
This target function is similar to the hook
- 'TARGET_OPTION_OVERRIDE' but is called when the optimize level is
+ `TARGET_OPTION_OVERRIDE' but is called when the optimize level is
changed via an attribute or pragma or when it is reset at the end
of the code affected by the attribute or pragma. It is not called
- at the beginning of compilation when 'TARGET_OPTION_OVERRIDE' is
+ at the beginning of compilation when `TARGET_OPTION_OVERRIDE' is
called so if you want to perform these actions then, you should
- have 'TARGET_OPTION_OVERRIDE' call
- 'TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE'.
+ have `TARGET_OPTION_OVERRIDE' call
+ `TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE'.
-- Macro: C_COMMON_OVERRIDE_OPTIONS
- This is similar to the 'TARGET_OPTION_OVERRIDE' hook but is only
+ This is similar to the `TARGET_OPTION_OVERRIDE' hook but is only
used in the C language frontends (C, Objective-C, C++,
Objective-C++) and so can be used to alter option flag variables
which only exist in those frontends.
-- Common Target Hook: const struct default_options *
- TARGET_OPTION_OPTIMIZATION_TABLE
- Some machines may desire to change what optimizations are performed
- for various optimization levels. This variable, if defined,
- describes options to enable at particular sets of optimization
- levels. These options are processed once just after the
- optimization level is determined and before the remainder of the
- command options have been parsed, so may be overridden by other
+TARGET_OPTION_OPTIMIZATION_TABLE
+ Some machines may desire to change what optimizations are
+ performed for various optimization levels. This variable, if
+ defined, describes options to enable at particular sets of
+ optimization levels. These options are processed once just after
+ the optimization level is determined and before the remainder of
+ the command options have been parsed, so may be overridden by other
options passed explicitly.
This processing is run once at program startup and when the
- optimization options are changed via '#pragma GCC optimize' or by
- using the 'optimize' attribute.
+ optimization options are changed via `#pragma GCC optimize' or by
+ using the `optimize' attribute.
-- Common Target Hook: void TARGET_OPTION_INIT_STRUCT (struct
gcc_options *OPTS)
Set target-dependent initial values of fields in OPTS.
-- Common Target Hook: void TARGET_OPTION_DEFAULT_PARAMS (void)
- Set target-dependent default values for '--param' settings, using
- calls to 'set_default_param_value'.
+ Set target-dependent default values for `--param' settings, using
+ calls to `set_default_param_value'.
-- Macro: SWITCHABLE_TARGET
Some targets need to switch between substantially different
subtargets during compilation. For example, the MIPS target has
- one subtarget for the traditional MIPS architecture and another for
- MIPS16. Source code can switch between these two subarchitectures
- using the 'mips16' and 'nomips16' attributes.
+ one subtarget for the traditional MIPS architecture and another
+ for MIPS16. Source code can switch between these two
+ subarchitectures using the `mips16' and `nomips16' attributes.
Such subtargets can differ in things like the set of available
registers, the set of available instructions, the costs of various
@@ -28052,7 +28443,7 @@ Here are run-time target specifications.
subtarget takes a significant amount of time. The compiler
therefore provides a facility for maintaining several versions of
the global variables and quickly switching between them; see
- 'target-globals.h' for details.
+ `target-globals.h' for details.
Define this macro to 1 if your target needs this facility. The
default is 0.
@@ -28061,8 +28452,8 @@ Here are run-time target specifications.
(void)
Returns true if the target supports IEEE 754 floating-point
exceptions and rounding modes, false otherwise. This is intended
- to relate to the 'float' and 'double' types, but not necessarily
- 'long double'. By default, returns true if the 'adddf3'
+ to relate to the `float' and `double' types, but not necessarily
+ `long double'. By default, returns true if the `adddf3'
instruction pattern is available and false otherwise, on the
assumption that hardware floating point supports exceptions and
rounding modes but software floating point does not.
@@ -28079,46 +28470,48 @@ using statics to store the information is a bad idea, since GCC supports
nested functions, so you can be halfway through encoding one function
when another one comes along.
- GCC defines a data structure called 'struct function' which contains
+ GCC defines a data structure called `struct function' which contains
all of the data specific to an individual function. This structure
-contains a field called 'machine' whose type is 'struct machine_function
-*', which can be used by targets to point to their own specific data.
+contains a field called `machine' whose type is `struct
+machine_function *', which can be used by targets to point to their own
+specific data.
If a target needs per-function specific data it should define the type
-'struct machine_function' and also the macro 'INIT_EXPANDERS'. This
+`struct machine_function' and also the macro `INIT_EXPANDERS'. This
macro should be used to initialize the function pointer
-'init_machine_status'. This pointer is explained below.
+`init_machine_status'. This pointer is explained below.
One typical use of per-function, target specific data is to create an
RTX to hold the register containing the function's return address. This
-RTX can then be used to implement the '__builtin_return_address'
+RTX can then be used to implement the `__builtin_return_address'
function, for level 0.
Note--earlier implementations of GCC used a single data area to hold
all of the per-function information. Thus when processing of a nested
function began the old per-function data had to be pushed onto a stack,
-and when the processing was finished, it had to be popped off the stack.
-GCC used to provide function pointers called 'save_machine_status' and
-'restore_machine_status' to handle the saving and restoring of the
-target specific information. Since the single data area approach is no
-longer used, these pointers are no longer supported.
+and when the processing was finished, it had to be popped off the
+stack. GCC used to provide function pointers called
+`save_machine_status' and `restore_machine_status' to handle the saving
+and restoring of the target specific information. Since the single
+data area approach is no longer used, these pointers are no longer
+supported.
-- Macro: INIT_EXPANDERS
Macro called to initialize any target specific information. This
- macro is called once per function, before generation of any RTL has
- begun. The intention of this macro is to allow the initialization
- of the function pointer 'init_machine_status'.
+ macro is called once per function, before generation of any RTL
+ has begun. The intention of this macro is to allow the
+ initialization of the function pointer `init_machine_status'.
-- Variable: void (*)(struct function *) init_machine_status
- If this function pointer is non-'NULL' it will be called once per
+ If this function pointer is non-`NULL' it will be called once per
function, before function compilation starts, in order to allow the
- target to perform any target specific initialization of the 'struct
- function' structure. It is intended that this would be used to
- initialize the 'machine' of that structure.
+ target to perform any target specific initialization of the
+ `struct function' structure. It is intended that this would be
+ used to initialize the `machine' of that structure.
- 'struct machine_function' structures are expected to be freed by
- GC. Generally, any memory that they reference must be allocated by
- using GC allocation, including the structure itself.
+ `struct machine_function' structures are expected to be freed by
+ GC. Generally, any memory that they reference must be allocated
+ by using GC allocation, including the structure itself.

File: gccint.info, Node: Storage Layout, Next: Type Layout, Prev: Per-Function Data, Up: Target Macros
@@ -28128,7 +28521,7 @@ File: gccint.info, Node: Storage Layout, Next: Type Layout, Prev: Per-Functio
Note that the definitions of the macros in this table which are sizes or
alignments measured in bits do not need to be constant. They can be C
-expressions that refer to static variables, such as the 'target_flags'.
+expressions that refer to static variables, such as the `target_flags'.
*Note Run-time Target::.
-- Macro: BITS_BIG_ENDIAN
@@ -28141,7 +28534,7 @@ expressions that refer to static variables, such as the 'target_flags'.
constant.
This macro does not affect the way structure fields are packed into
- bytes or words; that is controlled by 'BYTES_BIG_ENDIAN'.
+ bytes or words; that is controlled by `BYTES_BIG_ENDIAN'.
-- Macro: BYTES_BIG_ENDIAN
Define this macro to have the value 1 if the most significant byte
@@ -28151,7 +28544,7 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Macro: WORDS_BIG_ENDIAN
Define this macro to have the value 1 if, in a multiword object,
the most significant word has the lowest number. This applies to
- both memory locations and registers; see 'REG_WORDS_BIG_ENDIAN' if
+ both memory locations and registers; see `REG_WORDS_BIG_ENDIAN' if
the order of words in memory is not the same as the order in
registers. This macro need not be a constant.
@@ -28159,11 +28552,11 @@ expressions that refer to static variables, such as the 'target_flags'.
On some machines, the order of words in a multiword object differs
between registers in memory. In such a situation, define this
macro to describe the order of words in a register. The macro
- 'WORDS_BIG_ENDIAN' controls the order of words in memory.
+ `WORDS_BIG_ENDIAN' controls the order of words in memory.
-- Macro: FLOAT_WORDS_BIG_ENDIAN
- Define this macro to have the value 1 if 'DFmode', 'XFmode' or
- 'TFmode' floating point numbers are stored in memory with the word
+ Define this macro to have the value 1 if `DFmode', `XFmode' or
+ `TFmode' floating point numbers are stored in memory with the word
containing the sign bit at the lowest address; otherwise define it
to have the value 0. This macro need not be a constant.
@@ -28172,12 +28565,12 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Macro: BITS_PER_WORD
Number of bits in a word. If you do not define this macro, the
- default is 'BITS_PER_UNIT * UNITS_PER_WORD'.
+ default is `BITS_PER_UNIT * UNITS_PER_WORD'.
-- Macro: MAX_BITS_PER_WORD
Maximum number of bits in a word. If this is undefined, the
- default is 'BITS_PER_WORD'. Otherwise, it is the constant value
- that is the largest value that 'BITS_PER_WORD' can have at
+ default is `BITS_PER_WORD'. Otherwise, it is the constant value
+ that is the largest value that `BITS_PER_WORD' can have at
run-time.
-- Macro: UNITS_PER_WORD
@@ -28186,36 +28579,37 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Macro: MIN_UNITS_PER_WORD
Minimum number of units in a word. If this is undefined, the
- default is 'UNITS_PER_WORD'. Otherwise, it is the constant value
- that is the smallest value that 'UNITS_PER_WORD' can have at
+ default is `UNITS_PER_WORD'. Otherwise, it is the constant value
+ that is the smallest value that `UNITS_PER_WORD' can have at
run-time.
-- Macro: POINTER_SIZE
Width of a pointer, in bits. You must specify a value no wider
- than the width of 'Pmode'. If it is not equal to the width of
- 'Pmode', you must define 'POINTERS_EXTEND_UNSIGNED'. If you do not
- specify a value the default is 'BITS_PER_WORD'.
+ than the width of `Pmode'. If it is not equal to the width of
+ `Pmode', you must define `POINTERS_EXTEND_UNSIGNED'. If you do
+ not specify a value the default is `BITS_PER_WORD'.
-- Macro: POINTERS_EXTEND_UNSIGNED
A C expression that determines how pointers should be extended from
- 'ptr_mode' to either 'Pmode' or 'word_mode'. It is greater than
+ `ptr_mode' to either `Pmode' or `word_mode'. It is greater than
zero if pointers should be zero-extended, zero if they should be
sign-extended, and negative if some other sort of conversion is
needed. In the last case, the extension is done by the target's
- 'ptr_extend' instruction.
+ `ptr_extend' instruction.
- You need not define this macro if the 'ptr_mode', 'Pmode' and
- 'word_mode' are all the same width.
+ You need not define this macro if the `ptr_mode', `Pmode' and
+ `word_mode' are all the same width.
-- Macro: PROMOTE_MODE (M, UNSIGNEDP, TYPE)
- A macro to update M and UNSIGNEDP when an object whose type is TYPE
- and which has the specified mode and signedness is to be stored in
- a register. This macro is only called when TYPE is a scalar type.
-
- On most RISC machines, which only have operations that operate on a
- full register, define this macro to set M to 'word_mode' if M is an
- integer mode narrower than 'BITS_PER_WORD'. In most cases, only
- integer modes should be widened because wider-precision
+ A macro to update M and UNSIGNEDP when an object whose type is
+ TYPE and which has the specified mode and signedness is to be
+ stored in a register. This macro is only called when TYPE is a
+ scalar type.
+
+ On most RISC machines, which only have operations that operate on
+ a full register, define this macro to set M to `word_mode' if M is
+ an integer mode narrower than `BITS_PER_WORD'. In most cases,
+ only integer modes should be widened because wider-precision
floating-point operations are usually more expensive than their
narrower counterparts.
@@ -28232,26 +28626,26 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Target Hook: machine_mode TARGET_PROMOTE_FUNCTION_MODE (const_tree
TYPE, machine_mode MODE, int *PUNSIGNEDP, const_tree FUNTYPE,
int FOR_RETURN)
- Like 'PROMOTE_MODE', but it is applied to outgoing function
- arguments or function return values. The target hook should return
- the new mode and possibly change '*PUNSIGNEDP' if the promotion
- should change signedness. This function is called only for scalar
- _or pointer_ types.
+ Like `PROMOTE_MODE', but it is applied to outgoing function
+ arguments or function return values. The target hook should
+ return the new mode and possibly change `*PUNSIGNEDP' if the
+ promotion should change signedness. This function is called only
+ for scalar _or pointer_ types.
FOR_RETURN allows to distinguish the promotion of arguments and
- return values. If it is '1', a return value is being promoted and
- 'TARGET_FUNCTION_VALUE' must perform the same promotions done here.
- If it is '2', the returned mode should be that of the register in
+ return values. If it is `1', a return value is being promoted and
+ `TARGET_FUNCTION_VALUE' must perform the same promotions done here.
+ If it is `2', the returned mode should be that of the register in
which an incoming parameter is copied, or the outgoing result is
computed; then the hook should return the same mode as
- 'promote_mode', though the signedness may be different.
+ `promote_mode', though the signedness may be different.
TYPE can be NULL when promoting function arguments of libcalls.
The default is to not promote arguments and return values. You can
also define the hook to
- 'default_promote_function_mode_always_promote' if you would like to
- apply the same rules given by 'PROMOTE_MODE'.
+ `default_promote_function_mode_always_promote' if you would like
+ to apply the same rules given by `PROMOTE_MODE'.
-- Macro: PARM_BOUNDARY
Normal alignment required for function parameters on the stack, in
@@ -28260,24 +28654,24 @@ expressions that refer to static variables, such as the 'target_flags'.
size of an integer.
-- Macro: STACK_BOUNDARY
- Define this macro to the minimum alignment enforced by hardware for
- the stack pointer on this machine. The definition is a C
+ Define this macro to the minimum alignment enforced by hardware
+ for the stack pointer on this machine. The definition is a C
expression for the desired alignment (measured in bits). This
- value is used as a default if 'PREFERRED_STACK_BOUNDARY' is not
+ value is used as a default if `PREFERRED_STACK_BOUNDARY' is not
defined. On most machines, this should be the same as
- 'PARM_BOUNDARY'.
+ `PARM_BOUNDARY'.
-- Macro: PREFERRED_STACK_BOUNDARY
Define this macro if you wish to preserve a certain alignment for
the stack pointer, greater than what the hardware enforces. The
- definition is a C expression for the desired alignment (measured in
- bits). This macro must evaluate to a value equal to or larger than
- 'STACK_BOUNDARY'.
+ definition is a C expression for the desired alignment (measured
+ in bits). This macro must evaluate to a value equal to or larger
+ than `STACK_BOUNDARY'.
-- Macro: INCOMING_STACK_BOUNDARY
Define this macro if the incoming stack boundary may be different
- from 'PREFERRED_STACK_BOUNDARY'. This macro must evaluate to a
- value equal to or larger than 'STACK_BOUNDARY'.
+ from `PREFERRED_STACK_BOUNDARY'. This macro must evaluate to a
+ value equal to or larger than `STACK_BOUNDARY'.
-- Macro: FUNCTION_BOUNDARY
Alignment required for a function entry point, in bits.
@@ -28291,70 +28685,72 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Target Hook: HOST_WIDE_INT TARGET_ABSOLUTE_BIGGEST_ALIGNMENT
If defined, this target hook specifies the absolute biggest
alignment that a type or variable can have on this machine,
- otherwise, 'BIGGEST_ALIGNMENT' is used.
+ otherwise, `BIGGEST_ALIGNMENT' is used.
-- Macro: MALLOC_ABI_ALIGNMENT
Alignment, in bits, a C conformant malloc implementation has to
- provide. If not defined, the default value is 'BITS_PER_WORD'.
+ provide. If not defined, the default value is `BITS_PER_WORD'.
-- Macro: ATTRIBUTE_ALIGNED_VALUE
- Alignment used by the '__attribute__ ((aligned))' construct. If
- not defined, the default value is 'BIGGEST_ALIGNMENT'.
+ Alignment used by the `__attribute__ ((aligned))' construct. If
+ not defined, the default value is `BIGGEST_ALIGNMENT'.
-- Macro: MINIMUM_ATOMIC_ALIGNMENT
If defined, the smallest alignment, in bits, that can be given to
an object that can be referenced in one operation, without
- disturbing any nearby object. Normally, this is 'BITS_PER_UNIT',
+ disturbing any nearby object. Normally, this is `BITS_PER_UNIT',
but may be larger on machines that don't have byte or half-word
store operations.
-- Macro: BIGGEST_FIELD_ALIGNMENT
Biggest alignment that any structure or union field can require on
this machine, in bits. If defined, this overrides
- 'BIGGEST_ALIGNMENT' for structure and union fields only, unless the
- field alignment has been set by the '__attribute__ ((aligned (N)))'
- construct.
+ `BIGGEST_ALIGNMENT' for structure and union fields only, unless
+ the field alignment has been set by the `__attribute__ ((aligned
+ (N)))' construct.
-- Macro: ADJUST_FIELD_ALIGN (FIELD, COMPUTED)
An expression for the alignment of a structure field FIELD if the
alignment computed in the usual way (including applying of
- 'BIGGEST_ALIGNMENT' and 'BIGGEST_FIELD_ALIGNMENT' to the alignment)
- is COMPUTED. It overrides alignment only if the field alignment
- has not been set by the '__attribute__ ((aligned (N)))' construct.
+ `BIGGEST_ALIGNMENT' and `BIGGEST_FIELD_ALIGNMENT' to the
+ alignment) is COMPUTED. It overrides alignment only if the field
+ alignment has not been set by the `__attribute__ ((aligned (N)))'
+ construct.
-- Macro: MAX_STACK_ALIGNMENT
Biggest stack alignment guaranteed by the backend. Use this macro
to specify the maximum alignment of a variable on stack.
- If not defined, the default value is 'STACK_BOUNDARY'.
+ If not defined, the default value is `STACK_BOUNDARY'.
+
-- Macro: MAX_OFILE_ALIGNMENT
Biggest alignment supported by the object file format of this
machine. Use this macro to limit the alignment which can be
- specified using the '__attribute__ ((aligned (N)))' construct. If
- not defined, the default value is 'BIGGEST_ALIGNMENT'.
+ specified using the `__attribute__ ((aligned (N)))' construct. If
+ not defined, the default value is `BIGGEST_ALIGNMENT'.
- On systems that use ELF, the default (in 'config/elfos.h') is the
+ On systems that use ELF, the default (in `config/elfos.h') is the
largest supported 32-bit ELF section alignment representable on a
- 32-bit host e.g. '(((uint64_t) 1 << 28) * 8)'. On 32-bit ELF the
- largest supported section alignment in bits is '(0x80000000 * 8)',
+ 32-bit host e.g. `(((uint64_t) 1 << 28) * 8)'. On 32-bit ELF the
+ largest supported section alignment in bits is `(0x80000000 * 8)',
but this is not representable on 32-bit hosts.
-- Macro: DATA_ALIGNMENT (TYPE, BASIC-ALIGN)
If defined, a C expression to compute the alignment for a variable
- in the static store. TYPE is the data type, and BASIC-ALIGN is the
- alignment that the object would ordinarily have. The value of this
- macro is used instead of that alignment to align the object.
+ in the static store. TYPE is the data type, and BASIC-ALIGN is
+ the alignment that the object would ordinarily have. The value of
+ this macro is used instead of that alignment to align the object.
If this macro is not defined, then BASIC-ALIGN is used.
One use of this macro is to increase alignment of medium-size data
to make it all fit in fewer cache lines. Another is to cause
- character arrays to be word-aligned so that 'strcpy' calls that
+ character arrays to be word-aligned so that `strcpy' calls that
copy constants to character arrays can be done inline.
-- Macro: DATA_ABI_ALIGNMENT (TYPE, BASIC-ALIGN)
- Similar to 'DATA_ALIGNMENT', but for the cases where the ABI
+ Similar to `DATA_ALIGNMENT', but for the cases where the ABI
mandates some alignment increase, instead of optimization only
purposes. E.g. AMD x86-64 psABI says that variables with array
type larger than 15 bytes must be aligned to 16 byte boundaries.
@@ -28371,7 +28767,7 @@ expressions that refer to static variables, such as the 'target_flags'.
If this macro is not defined, then BASIC-ALIGN is used.
The typical use of this macro is to increase alignment for string
- constants to be word aligned so that 'strcpy' calls that copy
+ constants to be word aligned so that `strcpy' calls that copy
constants can be done inline.
-- Macro: LOCAL_ALIGNMENT (TYPE, BASIC-ALIGN)
@@ -28390,10 +28786,10 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Target Hook: HOST_WIDE_INT TARGET_VECTOR_ALIGNMENT (const_tree TYPE)
This hook can be used to define the alignment for a vector of type
- TYPE, in order to comply with a platform ABI. The default is to
- require natural alignment for vector types. The alignment returned
- by this hook must be a power-of-two multiple of the default
- alignment of the vector element type.
+ TYPE, in order to comply with a platform ABI. The default is to
+ require natural alignment for vector types. The alignment
+ returned by this hook must be a power-of-two multiple of the
+ default alignment of the vector element type.
-- Macro: STACK_SLOT_ALIGNMENT (TYPE, MODE, BASIC-ALIGN)
If defined, a C expression to compute the alignment for stack slot.
@@ -28402,8 +28798,8 @@ expressions that refer to static variables, such as the 'target_flags'.
The value of this macro is used instead of that alignment to align
the slot.
- If this macro is not defined, then BASIC-ALIGN is used when TYPE is
- 'NULL'. Otherwise, 'LOCAL_ALIGNMENT' will be used.
+ If this macro is not defined, then BASIC-ALIGN is used when TYPE
+ is `NULL'. Otherwise, `LOCAL_ALIGNMENT' will be used.
This macro is to set alignment of stack slot to the maximum
alignment of all possible modes which the slot may have.
@@ -28415,7 +28811,7 @@ expressions that refer to static variables, such as the 'target_flags'.
If defined, a C expression to compute the alignment for a local
variable DECL.
- If this macro is not defined, then 'LOCAL_ALIGNMENT (TREE_TYPE
+ If this macro is not defined, then `LOCAL_ALIGNMENT (TREE_TYPE
(DECL), DECL_ALIGN (DECL))' is used.
One use of this macro is to increase alignment of medium-size data
@@ -28426,16 +28822,16 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Macro: MINIMUM_ALIGNMENT (EXP, MODE, ALIGN)
If defined, a C expression to compute the minimum required
- alignment for dynamic stack realignment purposes for EXP (a type or
- decl), MODE, assuming normal alignment ALIGN.
+ alignment for dynamic stack realignment purposes for EXP (a type
+ or decl), MODE, assuming normal alignment ALIGN.
If this macro is not defined, then ALIGN will be used.
-- Macro: EMPTY_FIELD_BOUNDARY
- Alignment in bits to be given to a structure bit-field that follows
- an empty field such as 'int : 0;'.
+ Alignment in bits to be given to a structure bit-field that
+ follows an empty field such as `int : 0;'.
- If 'PCC_BITFIELD_TYPE_MATTERS' is true, it overrides this macro.
+ If `PCC_BITFIELD_TYPE_MATTERS' is true, it overrides this macro.
-- Macro: STRUCTURE_SIZE_BOUNDARY
Number of bits which any structure or union's size must be a
@@ -28443,7 +28839,7 @@ expressions that refer to static variables, such as the 'target_flags'.
multiple of this.
If you do not define this macro, the default is the same as
- 'BITS_PER_UNIT'.
+ `BITS_PER_UNIT'.
-- Macro: STRICT_ALIGNMENT
Define this macro to be the value 1 if instructions will fail to
@@ -28455,15 +28851,15 @@ expressions that refer to static variables, such as the 'target_flags'.
handle alignment of bit-fields and the structures that contain
them.
- The behavior is that the type written for a named bit-field ('int',
- 'short', or other integer type) imposes an alignment for the entire
- structure, as if the structure really did contain an ordinary field
- of that type. In addition, the bit-field is placed within the
- structure so that it would fit within such a field, not crossing a
- boundary for it.
+ The behavior is that the type written for a named bit-field (`int',
+ `short', or other integer type) imposes an alignment for the entire
+ structure, as if the structure really did contain an ordinary
+ field of that type. In addition, the bit-field is placed within
+ the structure so that it would fit within such a field, not
+ crossing a boundary for it.
Thus, on most machines, a named bit-field whose type is written as
- 'int' would not cross a four-byte boundary, and would force
+ `int' would not cross a four-byte boundary, and would force
four-byte alignment for the whole structure. (The alignment used
may not be four bytes; it is controlled by the other alignment
parameters.)
@@ -28471,21 +28867,21 @@ expressions that refer to static variables, such as the 'target_flags'.
An unnamed bit-field will not affect the alignment of the
containing structure.
- If the macro is defined, its definition should be a C expression; a
- nonzero value for the expression enables this behavior.
+ If the macro is defined, its definition should be a C expression;
+ a nonzero value for the expression enables this behavior.
Note that if this macro is not defined, or its value is zero, some
bit-fields may cross more than one alignment boundary. The
- compiler can support such references if there are 'insv', 'extv',
- and 'extzv' insns that can directly reference memory.
+ compiler can support such references if there are `insv', `extv',
+ and `extzv' insns that can directly reference memory.
The other known way of making bit-fields work is to define
- 'STRUCTURE_SIZE_BOUNDARY' as large as 'BIGGEST_ALIGNMENT'. Then
+ `STRUCTURE_SIZE_BOUNDARY' as large as `BIGGEST_ALIGNMENT'. Then
every structure can be accessed with fullwords.
Unless the machine has bit-field instructions or you define
- 'STRUCTURE_SIZE_BOUNDARY' that way, you must define
- 'PCC_BITFIELD_TYPE_MATTERS' to have a nonzero value.
+ `STRUCTURE_SIZE_BOUNDARY' that way, you must define
+ `PCC_BITFIELD_TYPE_MATTERS' to have a nonzero value.
If your aim is to make GCC use the same conventions for laying out
bit-fields as are used by another compiler, here is how to
@@ -28516,29 +28912,30 @@ expressions that refer to static variables, such as the 'target_flags'.
}
If this prints 2 and 5, then the compiler's behavior is what you
- would get from 'PCC_BITFIELD_TYPE_MATTERS'.
+ would get from `PCC_BITFIELD_TYPE_MATTERS'.
-- Macro: BITFIELD_NBYTES_LIMITED
- Like 'PCC_BITFIELD_TYPE_MATTERS' except that its effect is limited
+ Like `PCC_BITFIELD_TYPE_MATTERS' except that its effect is limited
to aligning a bit-field within the structure.
-- Target Hook: bool TARGET_ALIGN_ANON_BITFIELD (void)
- When 'PCC_BITFIELD_TYPE_MATTERS' is true this hook will determine
+ When `PCC_BITFIELD_TYPE_MATTERS' is true this hook will determine
whether unnamed bitfields affect the alignment of the containing
structure. The hook should return true if the structure should
inherit the alignment requirements of an unnamed bitfield's type.
-- Target Hook: bool TARGET_NARROW_VOLATILE_BITFIELD (void)
- This target hook should return 'true' if accesses to volatile
- bitfields should use the narrowest mode possible. It should return
- 'false' if these accesses should use the bitfield container type.
+ This target hook should return `true' if accesses to volatile
+ bitfields should use the narrowest mode possible. It should
+ return `false' if these accesses should use the bitfield container
+ type.
- The default is 'false'.
+ The default is `false'.
-- Target Hook: bool TARGET_MEMBER_TYPE_FORCES_BLK (const_tree FIELD,
machine_mode MODE)
Return true if a structure, union or array containing FIELD should
- be accessed using 'BLKMODE'.
+ be accessed using `BLKMODE'.
If FIELD is the only field in the structure, MODE is its mode,
otherwise MODE is VOIDmode. MODE is provided in the case where
@@ -28553,55 +28950,55 @@ expressions that refer to static variables, such as the 'target_flags'.
usual way is COMPUTED and the alignment explicitly specified was
SPECIFIED.
- The default is to use SPECIFIED if it is larger; otherwise, use the
- smaller of COMPUTED and 'BIGGEST_ALIGNMENT'
+ The default is to use SPECIFIED if it is larger; otherwise, use
+ the smaller of COMPUTED and `BIGGEST_ALIGNMENT'
-- Macro: MAX_FIXED_MODE_SIZE
An integer expression for the size in bits of the largest integer
machine mode that should actually be used. All integer machine
- modes of this size or smaller can be used for structures and unions
- with the appropriate sizes. If this macro is undefined,
- 'GET_MODE_BITSIZE (DImode)' is assumed.
+ modes of this size or smaller can be used for structures and
+ unions with the appropriate sizes. If this macro is undefined,
+ `GET_MODE_BITSIZE (DImode)' is assumed.
-- Macro: STACK_SAVEAREA_MODE (SAVE_LEVEL)
- If defined, an expression of type 'machine_mode' that specifies the
- mode of the save area operand of a 'save_stack_LEVEL' named pattern
- (*note Standard Names::). SAVE_LEVEL is one of 'SAVE_BLOCK',
- 'SAVE_FUNCTION', or 'SAVE_NONLOCAL' and selects which of the three
- named patterns is having its mode specified.
-
- You need not define this macro if it always returns 'Pmode'. You
- would most commonly define this macro if the 'save_stack_LEVEL'
+ If defined, an expression of type `machine_mode' that specifies
+ the mode of the save area operand of a `save_stack_LEVEL' named
+ pattern (*note Standard Names::). SAVE_LEVEL is one of
+ `SAVE_BLOCK', `SAVE_FUNCTION', or `SAVE_NONLOCAL' and selects
+ which of the three named patterns is having its mode specified.
+
+ You need not define this macro if it always returns `Pmode'. You
+ would most commonly define this macro if the `save_stack_LEVEL'
patterns need to support both a 32- and a 64-bit mode.
-- Macro: STACK_SIZE_MODE
- If defined, an expression of type 'machine_mode' that specifies the
- mode of the size increment operand of an 'allocate_stack' named
- pattern (*note Standard Names::).
+ If defined, an expression of type `machine_mode' that specifies
+ the mode of the size increment operand of an `allocate_stack'
+ named pattern (*note Standard Names::).
- You need not define this macro if it always returns 'word_mode'.
- You would most commonly define this macro if the 'allocate_stack'
+ You need not define this macro if it always returns `word_mode'.
+ You would most commonly define this macro if the `allocate_stack'
pattern needs to support both a 32- and a 64-bit mode.
-- Target Hook: machine_mode TARGET_LIBGCC_CMP_RETURN_MODE (void)
This target hook should return the mode to be used for the return
value of compare instructions expanded to libgcc calls. If not
- defined 'word_mode' is returned which is the right choice for a
+ defined `word_mode' is returned which is the right choice for a
majority of targets.
-- Target Hook: machine_mode TARGET_LIBGCC_SHIFT_COUNT_MODE (void)
This target hook should return the mode to be used for the shift
count operand of shift instructions expanded to libgcc calls. If
- not defined 'word_mode' is returned which is the right choice for a
- majority of targets.
+ not defined `word_mode' is returned which is the right choice for
+ a majority of targets.
-- Target Hook: machine_mode TARGET_UNWIND_WORD_MODE (void)
- Return machine mode to be used for '_Unwind_Word' type. The
- default is to use 'word_mode'.
+ Return machine mode to be used for `_Unwind_Word' type. The
+ default is to use `word_mode'.
-- Target Hook: bool TARGET_MS_BITFIELD_LAYOUT_P (const_tree
RECORD_TYPE)
- This target hook returns 'true' if bit-fields in the given
+ This target hook returns `true' if bit-fields in the given
RECORD_TYPE are to be laid out following the rules of Microsoft
Visual C/C++, namely: (i) a bit-field won't share the same storage
unit with the previous bit-field if their underlying types have
@@ -28610,7 +29007,7 @@ expressions that refer to static variables, such as the 'target_flags'.
bit-field; (ii) a zero-sized bit-field will affect the alignment of
the whole enclosing structure, even if it is unnamed; except that
(iii) a zero-sized bit-field will be disregarded unless it follows
- another bit-field of nonzero size. If this hook returns 'true',
+ another bit-field of nonzero size. If this hook returns `true',
other macros that control bit-field layout are ignored.
When a bit-field is inserted into a packed record, the whole size
@@ -28621,8 +29018,8 @@ expressions that refer to static variables, such as the 'target_flags'.
of that size is allocated). In an unpacked record, this is the
same as using alignment, but not equivalent when packing.
- If both MS bit-fields and '__attribute__((packed))' are used, the
- latter will take precedence. If '__attribute__((packed))' is used
+ If both MS bit-fields and `__attribute__((packed))' are used, the
+ latter will take precedence. If `__attribute__((packed))' is used
on a single field when MS bit-fields are in use, it will take
precedence for that field, but the alignment of the rest of the
structure may affect its placement.
@@ -28635,8 +29032,8 @@ expressions that refer to static variables, such as the 'target_flags'.
-- Target Hook: void TARGET_EXPAND_TO_RTL_HOOK (void)
This hook is called just before expansion into rtl, allowing the
- target to perform additional initializations or analysis before the
- expansion. For example, the rs6000 port uses it to allocate a
+ target to perform additional initializations or analysis before
+ the expansion. For example, the rs6000 port uses it to allocate a
scratch stack slot for use in copying SDmode values between memory
and floating point registers whenever the function being expanded
has any SDmode usage.
@@ -28652,28 +29049,28 @@ expressions that refer to static variables, such as the 'target_flags'.
part of a C++ mangled name. The TYPE argument is the tree
structure representing the type to be mangled. The hook may be
applied to trees which are not target-specific fundamental types;
- it should return 'NULL' for all such types, as well as arguments it
- does not recognize. If the return value is not 'NULL', it must
+ it should return `NULL' for all such types, as well as arguments
+ it does not recognize. If the return value is not `NULL', it must
point to a statically-allocated string constant.
Target-specific fundamental types might be new fundamental types or
qualified versions of ordinary fundamental types. Encode new
- fundamental types as 'u N NAME', where NAME is the name used for
+ fundamental types as `u N NAME', where NAME is the name used for
the type in source code, and N is the length of NAME in decimal.
- Encode qualified versions of ordinary types as 'U N NAME CODE',
+ Encode qualified versions of ordinary types as `U N NAME CODE',
where NAME is the name used for the type qualifier in source code,
N is the length of NAME as above, and CODE is the code used to
represent the unqualified version of this type. (See
- 'write_builtin_type' in 'cp/mangle.c' for the list of codes.) In
- both cases the spaces are for clarity; do not include any spaces in
- your string.
+ `write_builtin_type' in `cp/mangle.c' for the list of codes.) In
+ both cases the spaces are for clarity; do not include any spaces
+ in your string.
This hook is applied to types prior to typedef resolution. If the
- mangled name for a particular type depends only on that type's main
- variant, you can perform typedef resolution yourself using
- 'TYPE_MAIN_VARIANT' before mangling.
+ mangled name for a particular type depends only on that type's
+ main variant, you can perform typedef resolution yourself using
+ `TYPE_MAIN_VARIANT' before mangling.
- The default version of this hook always returns 'NULL', which is
+ The default version of this hook always returns `NULL', which is
appropriate for a target that does not define any new fundamental
types.
@@ -28689,207 +29086,207 @@ the previous section, these apply to specific features of C and related
languages, rather than to fundamental aspects of storage layout.
-- Macro: INT_TYPE_SIZE
- A C expression for the size in bits of the type 'int' on the target
- machine. If you don't define this, the default is one word.
+ A C expression for the size in bits of the type `int' on the
+ target machine. If you don't define this, the default is one word.
-- Macro: SHORT_TYPE_SIZE
- A C expression for the size in bits of the type 'short' on the
+ A C expression for the size in bits of the type `short' on the
target machine. If you don't define this, the default is half a
word. (If this would be less than one storage unit, it is rounded
up to one unit.)
-- Macro: LONG_TYPE_SIZE
- A C expression for the size in bits of the type 'long' on the
+ A C expression for the size in bits of the type `long' on the
target machine. If you don't define this, the default is one word.
-- Macro: ADA_LONG_TYPE_SIZE
On some machines, the size used for the Ada equivalent of the type
- 'long' by a native Ada compiler differs from that used by C. In
+ `long' by a native Ada compiler differs from that used by C. In
that situation, define this macro to be a C expression to be used
for the size of that type. If you don't define this, the default
- is the value of 'LONG_TYPE_SIZE'.
+ is the value of `LONG_TYPE_SIZE'.
-- Macro: LONG_LONG_TYPE_SIZE
- A C expression for the size in bits of the type 'long long' on the
+ A C expression for the size in bits of the type `long long' on the
target machine. If you don't define this, the default is two
words. If you want to support GNU Ada on your machine, the value
of this macro must be at least 64.
-- Macro: CHAR_TYPE_SIZE
- A C expression for the size in bits of the type 'char' on the
+ A C expression for the size in bits of the type `char' on the
target machine. If you don't define this, the default is
- 'BITS_PER_UNIT'.
+ `BITS_PER_UNIT'.
-- Macro: BOOL_TYPE_SIZE
- A C expression for the size in bits of the C++ type 'bool' and C99
- type '_Bool' on the target machine. If you don't define this, and
- you probably shouldn't, the default is 'CHAR_TYPE_SIZE'.
+ A C expression for the size in bits of the C++ type `bool' and C99
+ type `_Bool' on the target machine. If you don't define this, and
+ you probably shouldn't, the default is `CHAR_TYPE_SIZE'.
-- Macro: FLOAT_TYPE_SIZE
- A C expression for the size in bits of the type 'float' on the
+ A C expression for the size in bits of the type `float' on the
target machine. If you don't define this, the default is one word.
-- Macro: DOUBLE_TYPE_SIZE
- A C expression for the size in bits of the type 'double' on the
+ A C expression for the size in bits of the type `double' on the
target machine. If you don't define this, the default is two
words.
-- Macro: LONG_DOUBLE_TYPE_SIZE
- A C expression for the size in bits of the type 'long double' on
+ A C expression for the size in bits of the type `long double' on
the target machine. If you don't define this, the default is two
words.
-- Macro: SHORT_FRACT_TYPE_SIZE
- A C expression for the size in bits of the type 'short _Fract' on
+ A C expression for the size in bits of the type `short _Fract' on
the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT'.
+ `BITS_PER_UNIT'.
-- Macro: FRACT_TYPE_SIZE
- A C expression for the size in bits of the type '_Fract' on the
+ A C expression for the size in bits of the type `_Fract' on the
target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 2'.
+ `BITS_PER_UNIT * 2'.
-- Macro: LONG_FRACT_TYPE_SIZE
- A C expression for the size in bits of the type 'long _Fract' on
+ A C expression for the size in bits of the type `long _Fract' on
the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 4'.
+ `BITS_PER_UNIT * 4'.
-- Macro: LONG_LONG_FRACT_TYPE_SIZE
- A C expression for the size in bits of the type 'long long _Fract'
+ A C expression for the size in bits of the type `long long _Fract'
on the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 8'.
+ `BITS_PER_UNIT * 8'.
-- Macro: SHORT_ACCUM_TYPE_SIZE
- A C expression for the size in bits of the type 'short _Accum' on
+ A C expression for the size in bits of the type `short _Accum' on
the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 2'.
+ `BITS_PER_UNIT * 2'.
-- Macro: ACCUM_TYPE_SIZE
- A C expression for the size in bits of the type '_Accum' on the
+ A C expression for the size in bits of the type `_Accum' on the
target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 4'.
+ `BITS_PER_UNIT * 4'.
-- Macro: LONG_ACCUM_TYPE_SIZE
- A C expression for the size in bits of the type 'long _Accum' on
+ A C expression for the size in bits of the type `long _Accum' on
the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 8'.
+ `BITS_PER_UNIT * 8'.
-- Macro: LONG_LONG_ACCUM_TYPE_SIZE
- A C expression for the size in bits of the type 'long long _Accum'
+ A C expression for the size in bits of the type `long long _Accum'
on the target machine. If you don't define this, the default is
- 'BITS_PER_UNIT * 16'.
+ `BITS_PER_UNIT * 16'.
-- Macro: LIBGCC2_GNU_PREFIX
- This macro corresponds to the 'TARGET_LIBFUNC_GNU_PREFIX' target
+ This macro corresponds to the `TARGET_LIBFUNC_GNU_PREFIX' target
hook and should be defined if that hook is overriden to be true.
- It causes function names in libgcc to be changed to use a '__gnu_'
- prefix for their name rather than the default '__'. A port which
- uses this macro should also arrange to use 't-gnu-prefix' in the
- libgcc 'config.host'.
+ It causes function names in libgcc to be changed to use a `__gnu_'
+ prefix for their name rather than the default `__'. A port which
+ uses this macro should also arrange to use `t-gnu-prefix' in the
+ libgcc `config.host'.
-- Macro: TARGET_FLT_EVAL_METHOD
- A C expression for the value for 'FLT_EVAL_METHOD' in 'float.h',
- assuming, if applicable, that the floating-point control word is in
- its default state. If you do not define this macro the value of
- 'FLT_EVAL_METHOD' will be zero.
+ A C expression for the value for `FLT_EVAL_METHOD' in `float.h',
+ assuming, if applicable, that the floating-point control word is
+ in its default state. If you do not define this macro the value of
+ `FLT_EVAL_METHOD' will be zero.
-- Macro: WIDEST_HARDWARE_FP_SIZE
A C expression for the size in bits of the widest floating-point
format supported by the hardware. If you define this macro, you
must specify a value less than or equal to the value of
- 'LONG_DOUBLE_TYPE_SIZE'. If you do not define this macro, the
- value of 'LONG_DOUBLE_TYPE_SIZE' is the default.
+ `LONG_DOUBLE_TYPE_SIZE'. If you do not define this macro, the
+ value of `LONG_DOUBLE_TYPE_SIZE' is the default.
-- Macro: DEFAULT_SIGNED_CHAR
An expression whose value is 1 or 0, according to whether the type
- 'char' should be signed or unsigned by default. The user can
- always override this default with the options '-fsigned-char' and
- '-funsigned-char'.
+ `char' should be signed or unsigned by default. The user can
+ always override this default with the options `-fsigned-char' and
+ `-funsigned-char'.
-- Target Hook: bool TARGET_DEFAULT_SHORT_ENUMS (void)
This target hook should return true if the compiler should give an
- 'enum' type only as many bytes as it takes to represent the range
+ `enum' type only as many bytes as it takes to represent the range
of possible values of that type. It should return false if all
- 'enum' types should be allocated like 'int'.
+ `enum' types should be allocated like `int'.
The default is to return false.
-- Macro: SIZE_TYPE
- A C expression for a string describing the name of the data type to
- use for size values. The typedef name 'size_t' is defined using
- the contents of the string.
-
- The string can contain more than one keyword. If so, separate them
- with spaces, and write first any length keyword, then 'unsigned' if
- appropriate, and finally 'int'. The string must exactly match one
- of the data type names defined in the function
- 'c_common_nodes_and_builtins' in the file 'c-family/c-common.c'.
- You may not omit 'int' or change the order--that would cause the
+ A C expression for a string describing the name of the data type
+ to use for size values. The typedef name `size_t' is defined
+ using the contents of the string.
+
+ The string can contain more than one keyword. If so, separate
+ them with spaces, and write first any length keyword, then
+ `unsigned' if appropriate, and finally `int'. The string must
+ exactly match one of the data type names defined in the function
+ `c_common_nodes_and_builtins' in the file `c-family/c-common.c'.
+ You may not omit `int' or change the order--that would cause the
compiler to crash on startup.
- If you don't define this macro, the default is '"long unsigned
+ If you don't define this macro, the default is `"long unsigned
int"'.
-- Macro: SIZETYPE
- GCC defines internal types ('sizetype', 'ssizetype', 'bitsizetype'
- and 'sbitsizetype') for expressions dealing with size. This macro
- is a C expression for a string describing the name of the data type
- from which the precision of 'sizetype' is extracted.
+ GCC defines internal types (`sizetype', `ssizetype', `bitsizetype'
+ and `sbitsizetype') for expressions dealing with size. This macro
+ is a C expression for a string describing the name of the data
+ type from which the precision of `sizetype' is extracted.
- The string has the same restrictions as 'SIZE_TYPE' string.
+ The string has the same restrictions as `SIZE_TYPE' string.
- If you don't define this macro, the default is 'SIZE_TYPE'.
+ If you don't define this macro, the default is `SIZE_TYPE'.
-- Macro: PTRDIFF_TYPE
- A C expression for a string describing the name of the data type to
- use for the result of subtracting two pointers. The typedef name
- 'ptrdiff_t' is defined using the contents of the string. See
- 'SIZE_TYPE' above for more information.
+ A C expression for a string describing the name of the data type
+ to use for the result of subtracting two pointers. The typedef
+ name `ptrdiff_t' is defined using the contents of the string. See
+ `SIZE_TYPE' above for more information.
- If you don't define this macro, the default is '"long int"'.
+ If you don't define this macro, the default is `"long int"'.
-- Macro: WCHAR_TYPE
- A C expression for a string describing the name of the data type to
- use for wide characters. The typedef name 'wchar_t' is defined
- using the contents of the string. See 'SIZE_TYPE' above for more
+ A C expression for a string describing the name of the data type
+ to use for wide characters. The typedef name `wchar_t' is defined
+ using the contents of the string. See `SIZE_TYPE' above for more
information.
- If you don't define this macro, the default is '"int"'.
+ If you don't define this macro, the default is `"int"'.
-- Macro: WCHAR_TYPE_SIZE
A C expression for the size in bits of the data type for wide
- characters. This is used in 'cpp', which cannot make use of
- 'WCHAR_TYPE'.
+ characters. This is used in `cpp', which cannot make use of
+ `WCHAR_TYPE'.
-- Macro: WINT_TYPE
A C expression for a string describing the name of the data type to
- use for wide characters passed to 'printf' and returned from
- 'getwc'. The typedef name 'wint_t' is defined using the contents
- of the string. See 'SIZE_TYPE' above for more information.
+ use for wide characters passed to `printf' and returned from
+ `getwc'. The typedef name `wint_t' is defined using the contents
+ of the string. See `SIZE_TYPE' above for more information.
- If you don't define this macro, the default is '"unsigned int"'.
+ If you don't define this macro, the default is `"unsigned int"'.
-- Macro: INTMAX_TYPE
A C expression for a string describing the name of the data type
that can represent any value of any standard or extended signed
- integer type. The typedef name 'intmax_t' is defined using the
- contents of the string. See 'SIZE_TYPE' above for more
+ integer type. The typedef name `intmax_t' is defined using the
+ contents of the string. See `SIZE_TYPE' above for more
information.
If you don't define this macro, the default is the first of
- '"int"', '"long int"', or '"long long int"' that has as much
- precision as 'long long int'.
+ `"int"', `"long int"', or `"long long int"' that has as much
+ precision as `long long int'.
-- Macro: UINTMAX_TYPE
A C expression for a string describing the name of the data type
that can represent any value of any standard or extended unsigned
- integer type. The typedef name 'uintmax_t' is defined using the
- contents of the string. See 'SIZE_TYPE' above for more
+ integer type. The typedef name `uintmax_t' is defined using the
+ contents of the string. See `SIZE_TYPE' above for more
information.
If you don't define this macro, the default is the first of
- '"unsigned int"', '"long unsigned int"', or '"long long unsigned
- int"' that has as much precision as 'long long unsigned int'.
+ `"unsigned int"', `"long unsigned int"', or `"long long unsigned
+ int"' that has as much precision as `long long unsigned int'.
-- Macro: SIG_ATOMIC_TYPE
-- Macro: INT8_TYPE
@@ -28918,18 +29315,19 @@ languages, rather than to fundamental aspects of storage layout.
-- Macro: UINT_FAST64_TYPE
-- Macro: INTPTR_TYPE
-- Macro: UINTPTR_TYPE
- C expressions for the standard types 'sig_atomic_t', 'int8_t',
- 'int16_t', 'int32_t', 'int64_t', 'uint8_t', 'uint16_t', 'uint32_t',
- 'uint64_t', 'int_least8_t', 'int_least16_t', 'int_least32_t',
- 'int_least64_t', 'uint_least8_t', 'uint_least16_t',
- 'uint_least32_t', 'uint_least64_t', 'int_fast8_t', 'int_fast16_t',
- 'int_fast32_t', 'int_fast64_t', 'uint_fast8_t', 'uint_fast16_t',
- 'uint_fast32_t', 'uint_fast64_t', 'intptr_t', and 'uintptr_t'. See
- 'SIZE_TYPE' above for more information.
+ C expressions for the standard types `sig_atomic_t', `int8_t',
+ `int16_t', `int32_t', `int64_t', `uint8_t', `uint16_t',
+ `uint32_t', `uint64_t', `int_least8_t', `int_least16_t',
+ `int_least32_t', `int_least64_t', `uint_least8_t',
+ `uint_least16_t', `uint_least32_t', `uint_least64_t',
+ `int_fast8_t', `int_fast16_t', `int_fast32_t', `int_fast64_t',
+ `uint_fast8_t', `uint_fast16_t', `uint_fast32_t', `uint_fast64_t',
+ `intptr_t', and `uintptr_t'. See `SIZE_TYPE' above for more
+ information.
If any of these macros evaluates to a null pointer, the
corresponding type is not supported; if GCC is configured to
- provide '<stdint.h>' in such a case, the header provided may not
+ provide `<stdint.h>' in such a case, the header provided may not
conform to C99, depending on the type in question. The defaults
for all of these macros are null pointers.
@@ -28952,22 +29350,22 @@ languages, rather than to fundamental aspects of storage layout.
vtable_index is odd, we can distinguish which variant of the union
is in use. But, on some platforms function pointers can be odd,
and so this doesn't work. In that case, we use the low-order bit
- of the 'delta' field, and shift the remainder of the 'delta' field
+ of the `delta' field, and shift the remainder of the `delta' field
to the left.
GCC will automatically make the right selection about where to
- store this bit using the 'FUNCTION_BOUNDARY' setting for your
+ store this bit using the `FUNCTION_BOUNDARY' setting for your
platform. However, some platforms such as ARM/Thumb have
- 'FUNCTION_BOUNDARY' set such that functions always start at even
+ `FUNCTION_BOUNDARY' set such that functions always start at even
addresses, but the lowest bit of pointers to functions indicate
whether the function at that address is in ARM or Thumb mode. If
- this is the case of your architecture, you should define this macro
- to 'ptrmemfunc_vbit_in_delta'.
+ this is the case of your architecture, you should define this
+ macro to `ptrmemfunc_vbit_in_delta'.
In general, you should not have to define this macro. On
architectures in which function addresses are always even,
- according to 'FUNCTION_BOUNDARY', GCC will automatically define
- this macro to 'ptrmemfunc_vbit_in_pfn'.
+ according to `FUNCTION_BOUNDARY', GCC will automatically define
+ this macro to `ptrmemfunc_vbit_in_pfn'.
-- Macro: TARGET_VTABLE_USES_DESCRIPTORS
Normally, the C++ compiler uses function pointers in vtables. This
@@ -28984,12 +29382,12 @@ languages, rather than to fundamental aspects of storage layout.
By default, the vtable entries are void pointers, the so the
alignment is the same as pointer alignment. The value of this
macro specifies the alignment of the vtable entry in bits. It
- should be defined only when special alignment is necessary. */
+ should be defined only when special alignment is necessary. */
-- Macro: TARGET_VTABLE_DATA_ENTRY_DISTANCE
There are a few non-descriptor entries in the vtable at offsets
below zero. If these entries must be padded (say, to preserve the
- alignment specified by 'TARGET_VTABLE_ENTRY_ALIGN'), set this to
+ alignment specified by `TARGET_VTABLE_ENTRY_ALIGN'), set this to
the number of words in each data entry.

@@ -29026,9 +29424,9 @@ Registers have various characteristics.
-- Macro: FIRST_PSEUDO_REGISTER
Number of hardware registers known to the compiler. They receive
- numbers 0 through 'FIRST_PSEUDO_REGISTER-1'; thus, the first pseudo
- register's number really is assigned the number
- 'FIRST_PSEUDO_REGISTER'.
+ numbers 0 through `FIRST_PSEUDO_REGISTER-1'; thus, the first
+ pseudo register's number really is assigned the number
+ `FIRST_PSEUDO_REGISTER'.
-- Macro: FIXED_REGISTERS
An initializer that says which registers are used for fixed
@@ -29047,26 +29445,26 @@ Registers have various characteristics.
The table initialized from this macro, and the table initialized by
the following one, may be overridden at run time either
automatically, by the actions of the macro
- 'CONDITIONAL_REGISTER_USAGE', or by the user with the command
- options '-ffixed-REG', '-fcall-used-REG' and '-fcall-saved-REG'.
+ `CONDITIONAL_REGISTER_USAGE', or by the user with the command
+ options `-ffixed-REG', `-fcall-used-REG' and `-fcall-saved-REG'.
-- Macro: CALL_USED_REGISTERS
- Like 'FIXED_REGISTERS' but has 1 for each register that is
+ Like `FIXED_REGISTERS' but has 1 for each register that is
clobbered (in general) by function calls as well as for fixed
registers. This macro therefore identifies the registers that are
not available for general allocation of values that must live
across function calls.
- If a register has 0 in 'CALL_USED_REGISTERS', the compiler
+ If a register has 0 in `CALL_USED_REGISTERS', the compiler
automatically saves it on function entry and restores it on
function exit, if the register is used within the function.
-- Macro: CALL_REALLY_USED_REGISTERS
- Like 'CALL_USED_REGISTERS' except this macro doesn't require that
- the entire set of 'FIXED_REGISTERS' be included.
- ('CALL_USED_REGISTERS' must be a superset of 'FIXED_REGISTERS').
+ Like `CALL_USED_REGISTERS' except this macro doesn't require that
+ the entire set of `FIXED_REGISTERS' be included.
+ (`CALL_USED_REGISTERS' must be a superset of `FIXED_REGISTERS').
This macro is optional. If not specified, it defaults to the value
- of 'CALL_USED_REGISTERS'.
+ of `CALL_USED_REGISTERS'.
-- Macro: HARD_REGNO_CALL_PART_CLOBBERED (REGNO, MODE)
A C expression that is nonzero if it is not permissible to store a
@@ -29076,50 +29474,50 @@ Registers have various characteristics.
do not preserve the entire contents of a register across a call.
-- Target Hook: void TARGET_CONDITIONAL_REGISTER_USAGE (void)
- This hook may conditionally modify five variables 'fixed_regs',
- 'call_used_regs', 'global_regs', 'reg_names', and
- 'reg_class_contents', to take into account any dependence of these
+ This hook may conditionally modify five variables `fixed_regs',
+ `call_used_regs', `global_regs', `reg_names', and
+ `reg_class_contents', to take into account any dependence of these
register sets on target flags. The first three of these are of
- type 'char []' (interpreted as Boolean vectors). 'global_regs' is
- a 'const char *[]', and 'reg_class_contents' is a 'HARD_REG_SET'.
- Before the macro is called, 'fixed_regs', 'call_used_regs',
- 'reg_class_contents', and 'reg_names' have been initialized from
- 'FIXED_REGISTERS', 'CALL_USED_REGISTERS', 'REG_CLASS_CONTENTS', and
- 'REGISTER_NAMES', respectively. 'global_regs' has been cleared,
- and any '-ffixed-REG', '-fcall-used-REG' and '-fcall-saved-REG'
- command options have been applied.
+ type `char []' (interpreted as Boolean vectors). `global_regs' is
+ a `const char *[]', and `reg_class_contents' is a `HARD_REG_SET'.
+ Before the macro is called, `fixed_regs', `call_used_regs',
+ `reg_class_contents', and `reg_names' have been initialized from
+ `FIXED_REGISTERS', `CALL_USED_REGISTERS', `REG_CLASS_CONTENTS',
+ and `REGISTER_NAMES', respectively. `global_regs' has been
+ cleared, and any `-ffixed-REG', `-fcall-used-REG' and
+ `-fcall-saved-REG' command options have been applied.
If the usage of an entire class of registers depends on the target
flags, you may indicate this to GCC by using this macro to modify
- 'fixed_regs' and 'call_used_regs' to 1 for each of the registers in
- the classes which should not be used by GCC. Also make
- 'define_register_constraint's return 'NO_REGS' for constraints that
- shouldn't be used.
+ `fixed_regs' and `call_used_regs' to 1 for each of the registers
+ in the classes which should not be used by GCC. Also make
+ `define_register_constraint's return `NO_REGS' for constraints
+ that shouldn't be used.
- (However, if this class is not included in 'GENERAL_REGS' and all
+ (However, if this class is not included in `GENERAL_REGS' and all
of the insn patterns whose constraints permit this class are
controlled by target switches, then GCC will automatically avoid
using these registers when the target switches are opposed to
them.)
-- Macro: INCOMING_REGNO (OUT)
- Define this macro if the target machine has register windows. This
- C expression returns the register number as seen by the called
- function corresponding to the register number OUT as seen by the
- calling function. Return OUT if register number OUT is not an
- outbound register.
+ Define this macro if the target machine has register windows.
+ This C expression returns the register number as seen by the
+ called function corresponding to the register number OUT as seen
+ by the calling function. Return OUT if register number OUT is not
+ an outbound register.
-- Macro: OUTGOING_REGNO (IN)
- Define this macro if the target machine has register windows. This
- C expression returns the register number as seen by the calling
- function corresponding to the register number IN as seen by the
- called function. Return IN if register number IN is not an inbound
- register.
+ Define this macro if the target machine has register windows.
+ This C expression returns the register number as seen by the
+ calling function corresponding to the register number IN as seen
+ by the called function. Return IN if register number IN is not an
+ inbound register.
-- Macro: LOCAL_REGNO (REGNO)
- Define this macro if the target machine has register windows. This
- C expression returns true if the register is call-saved but is in
- the register window. Unlike most call-saved registers, such
+ Define this macro if the target machine has register windows.
+ This C expression returns true if the register is call-saved but
+ is in the register window. Unlike most call-saved registers, such
registers need not be explicitly restored on function exit or
during non-local gotos.
@@ -29146,7 +29544,7 @@ Registers are allocated in order.
One use of this macro is on machines where the highest numbered
registers must always be saved and the save-multiple-registers
instruction supports only sequences of consecutive registers. On
- such machines, define 'REG_ALLOC_ORDER' to be an initializer that
+ such machines, define `REG_ALLOC_ORDER' to be an initializer that
lists the highest numbered allocable register first.
-- Macro: ADJUST_REG_ALLOC_ORDER
@@ -29154,22 +29552,23 @@ Registers are allocated in order.
allocate hard registers for pseudo-registers local to a basic
block.
- Store the desired register order in the array 'reg_alloc_order'.
+ Store the desired register order in the array `reg_alloc_order'.
Element 0 should be the register to allocate first; element 1, the
next register; and so on.
The macro body should not assume anything about the contents of
- 'reg_alloc_order' before execution of the macro.
+ `reg_alloc_order' before execution of the macro.
On most machines, it is not necessary to define this macro.
-- Macro: HONOR_REG_ALLOC_ORDER
Normally, IRA tries to estimate the costs for saving a register in
- the prologue and restoring it in the epilogue. This discourages it
- from using call-saved registers. If a machine wants to ensure that
- IRA allocates registers in the order given by REG_ALLOC_ORDER even
- if some call-saved registers appear earlier than call-used ones,
- then define this macro as a C expression to nonzero. Default is 0.
+ the prologue and restoring it in the epilogue. This discourages
+ it from using call-saved registers. If a machine wants to ensure
+ that IRA allocates registers in the order given by REG_ALLOC_ORDER
+ even if some call-saved registers appear earlier than call-used
+ ones, then define this macro as a C expression to nonzero. Default
+ is 0.
-- Macro: IRA_HARD_REGNO_ADD_COST_MULTIPLIER (REGNO)
In some case register allocation order is not enough for the
@@ -29178,7 +29577,7 @@ Registers are allocated in order.
based on REGNO. The cost of using REGNO for a pseudo will be
increased by approximately the pseudo's usage frequency times the
value returned by this macro. Not defining this macro is
- equivalent to having it always return '0.0'.
+ equivalent to having it always return `0.0'.
On most machines, it is not necessary to define this macro.
@@ -29195,9 +29594,9 @@ consecutive registers are needed for a given mode.
-- Macro: HARD_REGNO_NREGS (REGNO, MODE)
A C expression for the number of consecutive hard registers,
starting at register number REGNO, required to hold a value of mode
- MODE. This macro must never return zero, even if a register cannot
- hold the requested mode - indicate that with HARD_REGNO_MODE_OK
- and/or CANNOT_CHANGE_MODE_CLASS instead.
+ MODE. This macro must never return zero, even if a register
+ cannot hold the requested mode - indicate that with
+ HARD_REGNO_MODE_OK and/or CANNOT_CHANGE_MODE_CLASS instead.
On a machine where all registers are exactly one word, a suitable
definition of this macro is
@@ -29212,24 +29611,24 @@ consecutive registers are needed for a given mode.
in registers starting at register number REGNO (as determined by
multiplying GCC's notion of the size of the register when
containing this mode by the number of registers returned by
- 'HARD_REGNO_NREGS'). By default this is zero.
+ `HARD_REGNO_NREGS'). By default this is zero.
For example, if a floating-point value is stored in three 32-bit
registers but takes up 128 bits in memory, then this would be
nonzero.
This macros only needs to be defined if there are cases where
- 'subreg_get_info' would otherwise wrongly determine that a 'subreg'
- can be represented by an offset to the register number, when in
- fact such a 'subreg' would contain some of the padding not stored
- in registers and so not be representable.
+ `subreg_get_info' would otherwise wrongly determine that a
+ `subreg' can be represented by an offset to the register number,
+ when in fact such a `subreg' would contain some of the padding not
+ stored in registers and so not be representable.
-- Macro: HARD_REGNO_NREGS_WITH_PADDING (REGNO, MODE)
For values of REGNO and MODE for which
- 'HARD_REGNO_NREGS_HAS_PADDING' returns nonzero, a C expression
+ `HARD_REGNO_NREGS_HAS_PADDING' returns nonzero, a C expression
returning the greater number of registers required to hold the
- value including any padding. In the example above, the value would
- be four.
+ value including any padding. In the example above, the value
+ would be four.
-- Macro: REGMODE_NATURAL_SIZE (MODE)
Define this macro if the natural size of registers that hold values
@@ -29256,48 +29655,49 @@ consecutive registers are needed for a given mode.
reject odd register numbers for such modes.
The minimum requirement for a mode to be OK in a register is that
- the 'movMODE' instruction pattern support moves between the
+ the `movMODE' instruction pattern support moves between the
register and other hard register in the same class and that moving
a value into the register and back out not alter it.
- Since the same instruction used to move 'word_mode' will work for
+ Since the same instruction used to move `word_mode' will work for
all narrower integer modes, it is not necessary on any machine for
- 'HARD_REGNO_MODE_OK' to distinguish between these modes, provided
- you define patterns 'movhi', etc., to take advantage of this. This
- is useful because of the interaction between 'HARD_REGNO_MODE_OK'
- and 'MODES_TIEABLE_P'; it is very desirable for all integer modes
+ `HARD_REGNO_MODE_OK' to distinguish between these modes, provided
+ you define patterns `movhi', etc., to take advantage of this. This
+ is useful because of the interaction between `HARD_REGNO_MODE_OK'
+ and `MODES_TIEABLE_P'; it is very desirable for all integer modes
to be tieable.
Many machines have special registers for floating point arithmetic.
Often people assume that floating point machine modes are allowed
- only in floating point registers. This is not true. Any registers
- that can hold integers can safely _hold_ a floating point machine
- mode, whether or not floating arithmetic can be done on it in those
- registers. Integer move instructions can be used to move the
- values.
+ only in floating point registers. This is not true. Any
+ registers that can hold integers can safely _hold_ a floating
+ point machine mode, whether or not floating arithmetic can be done
+ on it in those registers. Integer move instructions can be used
+ to move the values.
On some machines, though, the converse is true: fixed-point machine
modes may not go in floating registers. This is true if the
floating registers normalize any value stored in them, because
storing a non-floating value there would garble it. In this case,
- 'HARD_REGNO_MODE_OK' should reject fixed-point machine modes in
+ `HARD_REGNO_MODE_OK' should reject fixed-point machine modes in
floating registers. But if the floating registers do not
automatically normalize, if you can store any bit pattern in one
- and retrieve it unchanged without a trap, then any machine mode may
- go in a floating register, so you can define this macro to say so.
+ and retrieve it unchanged without a trap, then any machine mode
+ may go in a floating register, so you can define this macro to say
+ so.
The primary significance of special floating registers is rather
that they are the registers acceptable in floating point arithmetic
instructions. However, this is of no concern to
- 'HARD_REGNO_MODE_OK'. You handle it by writing the proper
+ `HARD_REGNO_MODE_OK'. You handle it by writing the proper
constraints for those instructions.
On some machines, the floating registers are especially slow to
- access, so that it is better to store a value in a stack frame than
- in such a register if floating point arithmetic is not being done.
- As long as the floating registers are not in class 'GENERAL_REGS',
- they will not be used unless some pattern's constraint asks for
- one.
+ access, so that it is better to store a value in a stack frame
+ than in such a register if floating point arithmetic is not being
+ done. As long as the floating registers are not in class
+ `GENERAL_REGS', they will not be used unless some pattern's
+ constraint asks for one.
-- Macro: HARD_REGNO_RENAME_OK (FROM, TO)
A C expression that is nonzero if it is OK to rename a hard
@@ -29313,29 +29713,30 @@ consecutive registers are needed for a given mode.
A C expression that is nonzero if a value of mode MODE1 is
accessible in mode MODE2 without copying.
- If 'HARD_REGNO_MODE_OK (R, MODE1)' and 'HARD_REGNO_MODE_OK (R,
- MODE2)' are always the same for any R, then 'MODES_TIEABLE_P
+ If `HARD_REGNO_MODE_OK (R, MODE1)' and `HARD_REGNO_MODE_OK (R,
+ MODE2)' are always the same for any R, then `MODES_TIEABLE_P
(MODE1, MODE2)' should be nonzero. If they differ for any R, you
- should define this macro to return zero unless some other mechanism
- ensures the accessibility of the value in a narrower mode.
+ should define this macro to return zero unless some other
+ mechanism ensures the accessibility of the value in a narrower
+ mode.
You should define this macro to return nonzero in as many cases as
possible since doing so will allow GCC to perform better register
allocation.
-- Target Hook: bool TARGET_HARD_REGNO_SCRATCH_OK (unsigned int REGNO)
- This target hook should return 'true' if it is OK to use a hard
+ This target hook should return `true' if it is OK to use a hard
register REGNO as scratch reg in peephole2.
One common use of this macro is to prevent using of a register that
is not saved by a prologue in an interrupt handler.
- The default version of this hook always returns 'true'.
+ The default version of this hook always returns `true'.
-- Macro: AVOID_CCMODE_COPIES
Define this macro if the compiler should avoid copies to/from
- 'CCmode' registers. You should only define this macro if support
- for copying to/from 'CCmode' is incomplete.
+ `CCmode' registers. You should only define this macro if support
+ for copying to/from `CCmode' is incomplete.

File: gccint.info, Node: Leaf Functions, Next: Stack Registers, Prev: Values in Registers, Up: Registers
@@ -29344,16 +29745,17 @@ File: gccint.info, Node: Leaf Functions, Next: Stack Registers, Prev: Values
------------------------------
On some machines, a leaf function (i.e., one which makes no calls) can
-run more efficiently if it does not make its own register window. Often
-this means it is required to receive its arguments in the registers
-where they are passed by the caller, instead of the registers where they
-would normally arrive.
+run more efficiently if it does not make its own register window.
+Often this means it is required to receive its arguments in the
+registers where they are passed by the caller, instead of the registers
+where they would normally arrive.
The special treatment for leaf functions generally applies only when
other conditions are met; for example, often they may use only those
registers for its own variables and temporaries. We use the term "leaf
-function" to mean a function that is suitable for this special handling,
-so that functions with no calls are not necessarily "leaf functions".
+function" to mean a function that is suitable for this special
+handling, so that functions with no calls are not necessarily "leaf
+functions".
GCC assigns register numbers before it knows whether the function is
suitable for leaf function treatment. So it needs to renumber the
@@ -29365,8 +29767,8 @@ accomplish this.
contains 1 for a register that is allowable in a candidate for leaf
function treatment.
- If leaf function treatment involves renumbering the registers, then
- the registers marked here should be the ones before
+ If leaf function treatment involves renumbering the registers,
+ then the registers marked here should be the ones before
renumbering--those that GCC would ordinarily allocate. The
registers which will actually be used in the assembler code, after
renumbering, should not be marked with 1 in this vector.
@@ -29387,16 +29789,16 @@ accomplish this.
optimize the treatment of leaf functions, and registers need to be
renumbered to do this.
- 'TARGET_ASM_FUNCTION_PROLOGUE' and 'TARGET_ASM_FUNCTION_EPILOGUE' must
+ `TARGET_ASM_FUNCTION_PROLOGUE' and `TARGET_ASM_FUNCTION_EPILOGUE' must
usually treat leaf functions specially. They can test the C variable
-'current_function_is_leaf' which is nonzero for leaf functions.
-'current_function_is_leaf' is set prior to local register allocation and
-is valid for the remaining compiler passes. They can also test the C
-variable 'current_function_uses_only_leaf_regs' which is nonzero for
+`current_function_is_leaf' which is nonzero for leaf functions.
+`current_function_is_leaf' is set prior to local register allocation
+and is valid for the remaining compiler passes. They can also test the
+C variable `current_function_uses_only_leaf_regs' which is nonzero for
leaf functions which only use leaf registers.
-'current_function_uses_only_leaf_regs' is valid after all passes that
+`current_function_uses_only_leaf_regs' is valid after all passes that
modify the instructions have been run and is only useful if
-'LEAF_REGISTERS' is defined.
+`LEAF_REGISTERS' is defined.

File: gccint.info, Node: Stack Registers, Prev: Leaf Functions, Up: Registers
@@ -29413,9 +29815,9 @@ stack.
they must be consecutively numbered. Furthermore, the existing support
for stack-like registers is specific to the 80387 floating point
coprocessor. If you have a new architecture that uses stack-like
-registers, you will need to do substantial work on 'reg-stack.c' and
-write your machine description to cooperate with it, as well as defining
-these macros.
+registers, you will need to do substantial work on `reg-stack.c' and
+write your machine description to cooperate with it, as well as
+defining these macros.
-- Macro: STACK_REGS
Define this if the machine has any stack-like registers.
@@ -29429,8 +29831,8 @@ these macros.
of the stack.
-- Macro: LAST_STACK_REG
- The number of the last stack-like register. This one is the bottom
- of the stack.
+ The number of the last stack-like register. This one is the
+ bottom of the stack.

File: gccint.info, Node: Register Classes, Next: Stack and Calling, Prev: Registers, Up: Target Macros
@@ -29450,35 +29852,36 @@ register classes that are allowed as operands to particular instruction
patterns.
In general, each register will belong to several classes. In fact, one
-class must be named 'ALL_REGS' and contain all the registers. Another
-class must be named 'NO_REGS' and contain no registers. Often the union
-of two classes will be another class; however, this is not required.
+class must be named `ALL_REGS' and contain all the registers. Another
+class must be named `NO_REGS' and contain no registers. Often the
+union of two classes will be another class; however, this is not
+required.
- One of the classes must be named 'GENERAL_REGS'. There is nothing
-terribly special about the name, but the operand constraint letters 'r'
-and 'g' specify this class. If 'GENERAL_REGS' is the same as
-'ALL_REGS', just define it as a macro which expands to 'ALL_REGS'.
+ One of the classes must be named `GENERAL_REGS'. There is nothing
+terribly special about the name, but the operand constraint letters `r'
+and `g' specify this class. If `GENERAL_REGS' is the same as
+`ALL_REGS', just define it as a macro which expands to `ALL_REGS'.
- Order the classes so that if class X is contained in class Y then X has
-a lower class number than Y.
+ Order the classes so that if class X is contained in class Y then X
+has a lower class number than Y.
- The way classes other than 'GENERAL_REGS' are specified in operand
+ The way classes other than `GENERAL_REGS' are specified in operand
constraints is through machine-dependent operand constraint letters.
You can define such letters to correspond to various classes, then use
them in operand constraints.
You must define the narrowest register classes for allocatable
-registers, so that each class either has no subclasses, or that for some
-mode, the move cost between registers within the class is cheaper than
-moving a register in the class to or from memory (*note Costs::).
+registers, so that each class either has no subclasses, or that for
+some mode, the move cost between registers within the class is cheaper
+than moving a register in the class to or from memory (*note Costs::).
You should define a class for the union of two classes whenever some
instruction allows both classes. For example, if an instruction allows
-either a floating point (coprocessor) register or a general register for
-a certain operand, you should define a class 'FLOAT_OR_GENERAL_REGS'
-which includes both of them. Otherwise you will get suboptimal code, or
-even internal compiler errors when reload cannot find a register in the
-class computed via 'reg_class_subunion'.
+either a floating point (coprocessor) register or a general register
+for a certain operand, you should define a class `FLOAT_OR_GENERAL_REGS'
+which includes both of them. Otherwise you will get suboptimal code,
+or even internal compiler errors when reload cannot find a register in
+the class computed via `reg_class_subunion'.
You must also specify certain redundant information about the register
classes: for each class, which classes contain it and which ones are
@@ -29489,29 +29892,29 @@ in their union.
certain class, all the registers used must belong to that class.
Therefore, register classes cannot be used to enforce a requirement for
a register pair to start with an even-numbered register. The way to
-specify this requirement is with 'HARD_REGNO_MODE_OK'.
+specify this requirement is with `HARD_REGNO_MODE_OK'.
Register classes used for input-operands of bitwise-and or shift
instructions have a special requirement: each such class must have, for
each fixed-point machine mode, a subclass whose registers can transfer
that mode to or from memory. For example, on some machines, the
-operations for single-byte values ('QImode') are limited to certain
+operations for single-byte values (`QImode') are limited to certain
registers. When this is so, each register class that is used in a
bitwise-and or shift instruction must have a subclass consisting of
registers from which single-byte values can be loaded or stored. This
-is so that 'PREFERRED_RELOAD_CLASS' can always have a possible value to
+is so that `PREFERRED_RELOAD_CLASS' can always have a possible value to
return.
-- Data type: enum reg_class
- An enumerated type that must be defined with all the register class
- names as enumerated values. 'NO_REGS' must be first. 'ALL_REGS'
- must be the last register class, followed by one more enumerated
- value, 'LIM_REG_CLASSES', which is not a register class but rather
- tells how many classes there are.
+ An enumerated type that must be defined with all the register
+ class names as enumerated values. `NO_REGS' must be first.
+ `ALL_REGS' must be the last register class, followed by one more
+ enumerated value, `LIM_REG_CLASSES', which is not a register class
+ but rather tells how many classes there are.
- Each register class has a number, which is the value of casting the
- class name to type 'int'. The number serves as an index in many of
- the tables described below.
+ Each register class has a number, which is the value of casting
+ the class name to type `int'. The number serves as an index in
+ many of the tables described below.
-- Macro: N_REG_CLASSES
The number of distinct register classes, defined as follows:
@@ -29527,15 +29930,16 @@ return.
An initializer containing the contents of the register classes, as
integers which are bit masks. The Nth integer specifies the
contents of class N. The way the integer MASK is interpreted is
- that register R is in the class if 'MASK & (1 << R)' is 1.
+ that register R is in the class if `MASK & (1 << R)' is 1.
When the machine has more than 32 registers, an integer does not
suffice. Then the integers are replaced by sub-initializers,
- braced groupings containing several integers. Each sub-initializer
- must be suitable as an initializer for the type 'HARD_REG_SET'
- which is defined in 'hard-reg-set.h'. In this situation, the first
- integer in each sub-initializer corresponds to registers 0 through
- 31, the second integer to registers 32 through 63, and so on.
+ braced groupings containing several integers. Each
+ sub-initializer must be suitable as an initializer for the type
+ `HARD_REG_SET' which is defined in `hard-reg-set.h'. In this
+ situation, the first integer in each sub-initializer corresponds to
+ registers 0 through 31, the second integer to registers 32 through
+ 63, and so on.
-- Macro: REGNO_REG_CLASS (REGNO)
A C expression whose value is a register class containing hard
@@ -29549,10 +29953,10 @@ return.
address which is the register value plus a displacement.
-- Macro: MODE_BASE_REG_CLASS (MODE)
- This is a variation of the 'BASE_REG_CLASS' macro which allows the
+ This is a variation of the `BASE_REG_CLASS' macro which allows the
selection of a base register in a mode dependent manner. If MODE
is VOIDmode then it should return the same value as
- 'BASE_REG_CLASS'.
+ `BASE_REG_CLASS'.
-- Macro: MODE_BASE_REG_REG_CLASS (MODE)
A C expression whose value is the register class to which a valid
@@ -29567,10 +29971,10 @@ return.
base register for a memory reference in mode MODE to address space
ADDRESS_SPACE must belong. OUTER_CODE and INDEX_CODE define the
context in which the base register occurs. OUTER_CODE is the code
- of the immediately enclosing expression ('MEM' for the top level of
- an address, 'ADDRESS' for something that occurs in an
- 'address_operand'). INDEX_CODE is the code of the corresponding
- index expression if OUTER_CODE is 'PLUS'; 'SCRATCH' otherwise.
+ of the immediately enclosing expression (`MEM' for the top level
+ of an address, `ADDRESS' for something that occurs in an
+ `address_operand'). INDEX_CODE is the code of the corresponding
+ index expression if OUTER_CODE is `PLUS'; `SCRATCH' otherwise.
-- Macro: INDEX_REG_CLASS
A macro whose definition is the name of the class to which a valid
@@ -29583,14 +29987,14 @@ return.
for use as a base register in operand addresses.
-- Macro: REGNO_MODE_OK_FOR_BASE_P (NUM, MODE)
- A C expression that is just like 'REGNO_OK_FOR_BASE_P', except that
+ A C expression that is just like `REGNO_OK_FOR_BASE_P', except that
that expression may examine the mode of the memory reference in
MODE. You should define this macro if the mode of the memory
reference affects whether a register may be used as a base
register. If you define this macro, the compiler will use it
- instead of 'REGNO_OK_FOR_BASE_P'. The mode may be 'VOIDmode' for
- addresses that appear outside a 'MEM', i.e., as an
- 'address_operand'.
+ instead of `REGNO_OK_FOR_BASE_P'. The mode may be `VOIDmode' for
+ addresses that appear outside a `MEM', i.e., as an
+ `address_operand'.
-- Macro: REGNO_MODE_OK_FOR_REG_BASE_P (NUM, MODE)
A C expression which is nonzero if register number NUM is suitable
@@ -29602,21 +30006,22 @@ return.
uses.
Use of this macro is deprecated; please use the more general
- 'REGNO_MODE_CODE_OK_FOR_BASE_P'.
+ `REGNO_MODE_CODE_OK_FOR_BASE_P'.
-- Macro: REGNO_MODE_CODE_OK_FOR_BASE_P (NUM, MODE, ADDRESS_SPACE,
OUTER_CODE, INDEX_CODE)
A C expression which is nonzero if register number NUM is suitable
for use as a base register in operand addresses, accessing memory
in mode MODE in address space ADDRESS_SPACE. This is similar to
- 'REGNO_MODE_OK_FOR_BASE_P', except that that expression may examine
- the context in which the register appears in the memory reference.
- OUTER_CODE is the code of the immediately enclosing expression
- ('MEM' if at the top level of the address, 'ADDRESS' for something
- that occurs in an 'address_operand'). INDEX_CODE is the code of
- the corresponding index expression if OUTER_CODE is 'PLUS';
- 'SCRATCH' otherwise. The mode may be 'VOIDmode' for addresses that
- appear outside a 'MEM', i.e., as an 'address_operand'.
+ `REGNO_MODE_OK_FOR_BASE_P', except that that expression may
+ examine the context in which the register appears in the memory
+ reference. OUTER_CODE is the code of the immediately enclosing
+ expression (`MEM' if at the top level of the address, `ADDRESS'
+ for something that occurs in an `address_operand'). INDEX_CODE is
+ the code of the corresponding index expression if OUTER_CODE is
+ `PLUS'; `SCRATCH' otherwise. The mode may be `VOIDmode' for
+ addresses that appear outside a `MEM', i.e., as an
+ `address_operand'.
-- Macro: REGNO_OK_FOR_INDEX_P (NUM)
A C expression which is nonzero if register number NUM is suitable
@@ -29638,45 +30043,45 @@ return.
A target hook that places additional preference on the register
class to use when it is necessary to rename a register in class
RCLASS to another class, or perhaps NO_REGS, if no preferred
- register class is found or hook 'preferred_rename_class' is not
- implemented. Sometimes returning a more restrictive class makes
+ register class is found or hook `preferred_rename_class' is not
+ implemented. Sometimes returning a more restrictive class makes
better code. For example, on ARM, thumb-2 instructions using
- 'LO_REGS' may be smaller than instructions using 'GENERIC_REGS'.
- By returning 'LO_REGS' from 'preferred_rename_class', code size can
- be reduced.
+ `LO_REGS' may be smaller than instructions using `GENERIC_REGS'.
+ By returning `LO_REGS' from `preferred_rename_class', code size
+ can be reduced.
-- Target Hook: reg_class_t TARGET_PREFERRED_RELOAD_CLASS (rtx X,
reg_class_t RCLASS)
A target hook that places additional restrictions on the register
class to use when it is necessary to copy value X into a register
- in class RCLASS. The value is a register class; perhaps RCLASS, or
- perhaps another, smaller class.
+ in class RCLASS. The value is a register class; perhaps RCLASS,
+ or perhaps another, smaller class.
- The default version of this hook always returns value of 'rclass'
+ The default version of this hook always returns value of `rclass'
argument.
Sometimes returning a more restrictive class makes better code.
- For example, on the 68000, when X is an integer constant that is in
- range for a 'moveq' instruction, the value of this macro is always
- 'DATA_REGS' as long as RCLASS includes the data registers.
- Requiring a data register guarantees that a 'moveq' will be used.
-
- One case where 'TARGET_PREFERRED_RELOAD_CLASS' must not return
- RCLASS is if X is a legitimate constant which cannot be loaded into
- some register class. By returning 'NO_REGS' you can force X into a
- memory location. For example, rs6000 can load immediate values
- into general-purpose registers, but does not have an instruction
- for loading an immediate value into a floating-point register, so
- 'TARGET_PREFERRED_RELOAD_CLASS' returns 'NO_REGS' when X is a
- floating-point constant. If the constant can't be loaded into any
- kind of register, code generation will be better if
- 'TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate
- instead of using 'TARGET_PREFERRED_RELOAD_CLASS'.
-
- If an insn has pseudos in it after register allocation, reload will
- go through the alternatives and call repeatedly
- 'TARGET_PREFERRED_RELOAD_CLASS' to find the best one. Returning
- 'NO_REGS', in this case, makes reload add a '!' in front of the
+ For example, on the 68000, when X is an integer constant that is
+ in range for a `moveq' instruction, the value of this macro is
+ always `DATA_REGS' as long as RCLASS includes the data registers.
+ Requiring a data register guarantees that a `moveq' will be used.
+
+ One case where `TARGET_PREFERRED_RELOAD_CLASS' must not return
+ RCLASS is if X is a legitimate constant which cannot be loaded
+ into some register class. By returning `NO_REGS' you can force X
+ into a memory location. For example, rs6000 can load immediate
+ values into general-purpose registers, but does not have an
+ instruction for loading an immediate value into a floating-point
+ register, so `TARGET_PREFERRED_RELOAD_CLASS' returns `NO_REGS' when
+ X is a floating-point constant. If the constant can't be loaded
+ into any kind of register, code generation will be better if
+ `TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate
+ instead of using `TARGET_PREFERRED_RELOAD_CLASS'.
+
+ If an insn has pseudos in it after register allocation, reload
+ will go through the alternatives and call repeatedly
+ `TARGET_PREFERRED_RELOAD_CLASS' to find the best one. Returning
+ `NO_REGS', in this case, makes reload add a `!' in front of the
constraint: the x86 back-end uses this feature to discourage usage
of 387 registers when math is done in the SSE registers (and vice
versa).
@@ -29691,42 +30096,42 @@ return.
#define PREFERRED_RELOAD_CLASS(X,CLASS) CLASS
Sometimes returning a more restrictive class makes better code.
- For example, on the 68000, when X is an integer constant that is in
- range for a 'moveq' instruction, the value of this macro is always
- 'DATA_REGS' as long as CLASS includes the data registers.
- Requiring a data register guarantees that a 'moveq' will be used.
-
- One case where 'PREFERRED_RELOAD_CLASS' must not return CLASS is if
- X is a legitimate constant which cannot be loaded into some
- register class. By returning 'NO_REGS' you can force X into a
+ For example, on the 68000, when X is an integer constant that is
+ in range for a `moveq' instruction, the value of this macro is
+ always `DATA_REGS' as long as CLASS includes the data registers.
+ Requiring a data register guarantees that a `moveq' will be used.
+
+ One case where `PREFERRED_RELOAD_CLASS' must not return CLASS is
+ if X is a legitimate constant which cannot be loaded into some
+ register class. By returning `NO_REGS' you can force X into a
memory location. For example, rs6000 can load immediate values
into general-purpose registers, but does not have an instruction
for loading an immediate value into a floating-point register, so
- 'PREFERRED_RELOAD_CLASS' returns 'NO_REGS' when X is a
+ `PREFERRED_RELOAD_CLASS' returns `NO_REGS' when X is a
floating-point constant. If the constant can't be loaded into any
kind of register, code generation will be better if
- 'TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate
- instead of using 'TARGET_PREFERRED_RELOAD_CLASS'.
+ `TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate
+ instead of using `TARGET_PREFERRED_RELOAD_CLASS'.
- If an insn has pseudos in it after register allocation, reload will
- go through the alternatives and call repeatedly
- 'PREFERRED_RELOAD_CLASS' to find the best one. Returning
- 'NO_REGS', in this case, makes reload add a '!' in front of the
+ If an insn has pseudos in it after register allocation, reload
+ will go through the alternatives and call repeatedly
+ `PREFERRED_RELOAD_CLASS' to find the best one. Returning
+ `NO_REGS', in this case, makes reload add a `!' in front of the
constraint: the x86 back-end uses this feature to discourage usage
of 387 registers when math is done in the SSE registers (and vice
versa).
-- Target Hook: reg_class_t TARGET_PREFERRED_OUTPUT_RELOAD_CLASS (rtx
X, reg_class_t RCLASS)
- Like 'TARGET_PREFERRED_RELOAD_CLASS', but for output reloads
+ Like `TARGET_PREFERRED_RELOAD_CLASS', but for output reloads
instead of input reloads.
- The default version of this hook always returns value of 'rclass'
+ The default version of this hook always returns value of `rclass'
argument.
- You can also use 'TARGET_PREFERRED_OUTPUT_RELOAD_CLASS' to
+ You can also use `TARGET_PREFERRED_OUTPUT_RELOAD_CLASS' to
discourage reload from using some alternatives, like
- 'TARGET_PREFERRED_RELOAD_CLASS'.
+ `TARGET_PREFERRED_RELOAD_CLASS'.
-- Macro: LIMIT_RELOAD_CLASS (MODE, CLASS)
A C expression that places additional restrictions on the register
@@ -29734,7 +30139,7 @@ return.
mode MODE in a reload register for which class CLASS would
ordinarily be used.
- Unlike 'PREFERRED_RELOAD_CLASS', this macro should be used when
+ Unlike `PREFERRED_RELOAD_CLASS', this macro should be used when
there are certain modes that simply can't go in certain reload
classes.
@@ -29747,19 +30152,19 @@ return.
-- Target Hook: reg_class_t TARGET_SECONDARY_RELOAD (bool IN_P, rtx X,
reg_class_t RELOAD_CLASS, machine_mode RELOAD_MODE,
secondary_reload_info *SRI)
- Many machines have some registers that cannot be copied directly to
- or from memory or even from other types of registers. An example
- is the 'MQ' register, which on most machines, can only be copied to
- or from general registers, but not memory. Below, we shall be
- using the term 'intermediate register' when a move operation cannot
- be performed directly, but has to be done by copying the source
- into the intermediate register first, and then copying the
- intermediate register to the destination. An intermediate register
- always has the same mode as source and destination. Since it holds
- the actual value being copied, reload might apply optimizations to
- re-use an intermediate register and eliding the copy from the
- source when it can determine that the intermediate register still
- holds the required value.
+ Many machines have some registers that cannot be copied directly
+ to or from memory or even from other types of registers. An
+ example is the `MQ' register, which on most machines, can only be
+ copied to or from general registers, but not memory. Below, we
+ shall be using the term 'intermediate register' when a move
+ operation cannot be performed directly, but has to be done by
+ copying the source into the intermediate register first, and then
+ copying the intermediate register to the destination. An
+ intermediate register always has the same mode as source and
+ destination. Since it holds the actual value being copied, reload
+ might apply optimizations to re-use an intermediate register and
+ eliding the copy from the source when it can determine that the
+ intermediate register still holds the required value.
Another kind of secondary reload is required on some machines which
allow copying all registers to and from memory, but require a
@@ -29782,80 +30187,81 @@ return.
needs to be copied to rtx X in RELOAD_MODE.
If copying a register of RELOAD_CLASS from/to X requires an
- intermediate register, the hook 'secondary_reload' should return
+ intermediate register, the hook `secondary_reload' should return
the register class required for this intermediate register. If no
- intermediate register is required, it should return NO_REGS. If
+ intermediate register is required, it should return NO_REGS. If
more than one intermediate register is required, describe the one
that is closest in the copy chain to the reload register.
If scratch registers are needed, you also have to describe how to
perform the copy from/to the reload register to/from this closest
- intermediate register. Or if no intermediate register is required,
- but still a scratch register is needed, describe the copy from/to
- the reload register to/from the reload operand X.
+ intermediate register. Or if no intermediate register is
+ required, but still a scratch register is needed, describe the
+ copy from/to the reload register to/from the reload operand X.
- You do this by setting 'sri->icode' to the instruction code of a
+ You do this by setting `sri->icode' to the instruction code of a
pattern in the md file which performs the move. Operands 0 and 1
- are the output and input of this copy, respectively. Operands from
- operand 2 onward are for scratch operands. These scratch operands
- must have a mode, and a single-register-class output constraint.
+ are the output and input of this copy, respectively. Operands
+ from operand 2 onward are for scratch operands. These scratch
+ operands must have a mode, and a single-register-class output
+ constraint.
- When an intermediate register is used, the 'secondary_reload' hook
+ When an intermediate register is used, the `secondary_reload' hook
will be called again to determine how to copy the intermediate
register to/from the reload operand X, so your hook must also have
code to handle the register class of the intermediate operand.
- X might be a pseudo-register or a 'subreg' of a pseudo-register,
+ X might be a pseudo-register or a `subreg' of a pseudo-register,
which could either be in a hard register or in memory. Use
- 'true_regnum' to find out; it will return -1 if the pseudo is in
+ `true_regnum' to find out; it will return -1 if the pseudo is in
memory and the hard register number if it is in a register.
- Scratch operands in memory (constraint '"=m"' / '"=&m"') are
+ Scratch operands in memory (constraint `"=m"' / `"=&m"') are
currently not supported. For the time being, you will have to
- continue to use 'SECONDARY_MEMORY_NEEDED' for that purpose.
+ continue to use `SECONDARY_MEMORY_NEEDED' for that purpose.
- 'copy_cost' also uses this target hook to find out how values are
+ `copy_cost' also uses this target hook to find out how values are
copied. If you want it to include some extra cost for the need to
- allocate (a) scratch register(s), set 'sri->extra_cost' to the
+ allocate (a) scratch register(s), set `sri->extra_cost' to the
additional cost. Or if two dependent moves are supposed to have a
lower cost than the sum of the individual moves due to expected
fortuitous scheduling and/or special forwarding logic, you can set
- 'sri->extra_cost' to a negative amount.
+ `sri->extra_cost' to a negative amount.
-- Macro: SECONDARY_RELOAD_CLASS (CLASS, MODE, X)
-- Macro: SECONDARY_INPUT_RELOAD_CLASS (CLASS, MODE, X)
-- Macro: SECONDARY_OUTPUT_RELOAD_CLASS (CLASS, MODE, X)
These macros are obsolete, new ports should use the target hook
- 'TARGET_SECONDARY_RELOAD' instead.
+ `TARGET_SECONDARY_RELOAD' instead.
These are obsolete macros, replaced by the
- 'TARGET_SECONDARY_RELOAD' target hook. Older ports still define
+ `TARGET_SECONDARY_RELOAD' target hook. Older ports still define
these macros to indicate to the reload phase that it may need to
allocate at least one register for a reload in addition to the
register to contain the data. Specifically, if copying X to a
register CLASS in MODE requires an intermediate register, you were
- supposed to define 'SECONDARY_INPUT_RELOAD_CLASS' to return the
+ supposed to define `SECONDARY_INPUT_RELOAD_CLASS' to return the
largest register class all of whose registers can be used as
intermediate registers or scratch registers.
If copying a register CLASS in MODE to X requires an intermediate
- or scratch register, 'SECONDARY_OUTPUT_RELOAD_CLASS' was supposed
+ or scratch register, `SECONDARY_OUTPUT_RELOAD_CLASS' was supposed
to be defined be defined to return the largest register class
required. If the requirements for input and output reloads were
- the same, the macro 'SECONDARY_RELOAD_CLASS' should have been used
+ the same, the macro `SECONDARY_RELOAD_CLASS' should have been used
instead of defining both macros identically.
- The values returned by these macros are often 'GENERAL_REGS'.
- Return 'NO_REGS' if no spare register is needed; i.e., if X can be
+ The values returned by these macros are often `GENERAL_REGS'.
+ Return `NO_REGS' if no spare register is needed; i.e., if X can be
directly copied to or from a register of CLASS in MODE without
- requiring a scratch register. Do not define this macro if it would
- always return 'NO_REGS'.
+ requiring a scratch register. Do not define this macro if it
+ would always return `NO_REGS'.
If a scratch register is required (either with or without an
intermediate register), you were supposed to define patterns for
- 'reload_inM' or 'reload_outM', as required (*note Standard Names::.
- These patterns, which were normally implemented with a
- 'define_expand', should be similar to the 'movM' patterns, except
+ `reload_inM' or `reload_outM', as required (*note Standard
+ Names::. These patterns, which were normally implemented with a
+ `define_expand', should be similar to the `movM' patterns, except
that operand 2 is the scratch register.
These patterns need constraints for the reload register and scratch
@@ -29863,19 +30269,19 @@ return.
reload register (whose class is CLASS) can meet the constraint
given in the pattern, the value returned by these macros is used
for the class of the scratch register. Otherwise, two additional
- reload registers are required. Their classes are obtained from the
- constraints in the insn pattern.
+ reload registers are required. Their classes are obtained from
+ the constraints in the insn pattern.
- X might be a pseudo-register or a 'subreg' of a pseudo-register,
+ X might be a pseudo-register or a `subreg' of a pseudo-register,
which could either be in a hard register or in memory. Use
- 'true_regnum' to find out; it will return -1 if the pseudo is in
+ `true_regnum' to find out; it will return -1 if the pseudo is in
memory and the hard register number if it is in a register.
These macros should not be used in the case where a particular
class of registers can only be copied to memory and not to another
class of registers. In that case, secondary reload registers are
not needed and would not be helpful. Instead, a stack location
- must be used to perform the copy and the 'movM' pattern should use
+ must be used to perform the copy and the `movM' pattern should use
memory as an intermediate storage. This case often occurs between
floating-point and general registers.
@@ -29890,20 +30296,20 @@ return.
Do not define this macro if its value would always be zero.
-- Macro: SECONDARY_MEMORY_NEEDED_RTX (MODE)
- Normally when 'SECONDARY_MEMORY_NEEDED' is defined, the compiler
+ Normally when `SECONDARY_MEMORY_NEEDED' is defined, the compiler
allocates a stack slot for a memory location needed for register
copies. If this macro is defined, the compiler instead uses the
memory location defined by this macro.
Do not define this macro if you do not define
- 'SECONDARY_MEMORY_NEEDED'.
+ `SECONDARY_MEMORY_NEEDED'.
-- Macro: SECONDARY_MEMORY_NEEDED_MODE (MODE)
- When the compiler needs a secondary memory location to copy between
- two registers of mode MODE, it normally allocates sufficient memory
- to hold a quantity of 'BITS_PER_WORD' bits and performs the store
- and load operations in a mode that many bits wide and whose class
- is the same as that of MODE.
+ When the compiler needs a secondary memory location to copy
+ between two registers of mode MODE, it normally allocates
+ sufficient memory to hold a quantity of `BITS_PER_WORD' bits and
+ performs the store and load operations in a mode that many bits
+ wide and whose class is the same as that of MODE.
This is right thing to do on most machines because it ensures that
all bits of the register are copied and prevents accesses to the
@@ -29913,21 +30319,21 @@ return.
However, this default behavior is not correct on some machines,
such as the DEC Alpha, that store short integers in floating-point
registers differently than in integer registers. On those
- machines, the default widening will not work correctly and you must
- define this macro to suppress that widening in some cases. See the
- file 'alpha.h' for details.
+ machines, the default widening will not work correctly and you
+ must define this macro to suppress that widening in some cases.
+ See the file `alpha.h' for details.
Do not define this macro if you do not define
- 'SECONDARY_MEMORY_NEEDED' or if widening MODE to a mode that is
- 'BITS_PER_WORD' bits wide is correct for your machine.
+ `SECONDARY_MEMORY_NEEDED' or if widening MODE to a mode that is
+ `BITS_PER_WORD' bits wide is correct for your machine.
-- Target Hook: bool TARGET_CLASS_LIKELY_SPILLED_P (reg_class_t RCLASS)
- A target hook which returns 'true' if pseudos that have been
+ A target hook which returns `true' if pseudos that have been
assigned to registers of class RCLASS would likely be spilled
because registers of RCLASS are needed for spill registers.
- The default version of this target hook returns 'true' if RCLASS
- has exactly one register and 'false' otherwise. On most machines,
+ The default version of this target hook returns `true' if RCLASS
+ has exactly one register and `false' otherwise. On most machines,
this default should be used. For generally register-starved
machines, such as i386, or machines with right register
constraints, such as SH, this hook can be used to avoid excessive
@@ -29942,25 +30348,25 @@ return.
A target hook returns the maximum number of consecutive registers
of class RCLASS needed to hold a value of mode MODE.
- This is closely related to the macro 'HARD_REGNO_NREGS'. In fact,
- the value returned by 'TARGET_CLASS_MAX_NREGS (RCLASS, MODE)'
- target hook should be the maximum value of 'HARD_REGNO_NREGS
+ This is closely related to the macro `HARD_REGNO_NREGS'. In fact,
+ the value returned by `TARGET_CLASS_MAX_NREGS (RCLASS, MODE)'
+ target hook should be the maximum value of `HARD_REGNO_NREGS
(REGNO, MODE)' for all REGNO values in the class RCLASS.
This target hook helps control the handling of multiple-word values
in the reload pass.
- The default version of this target hook returns the size of MODE in
- words.
+ The default version of this target hook returns the size of MODE
+ in words.
-- Macro: CLASS_MAX_NREGS (CLASS, MODE)
A C expression for the maximum number of consecutive registers of
class CLASS needed to hold a value of mode MODE.
- This is closely related to the macro 'HARD_REGNO_NREGS'. In fact,
- the value of the macro 'CLASS_MAX_NREGS (CLASS, MODE)' should be
- the maximum value of 'HARD_REGNO_NREGS (REGNO, MODE)' for all REGNO
- values in the class CLASS.
+ This is closely related to the macro `HARD_REGNO_NREGS'. In fact,
+ the value of the macro `CLASS_MAX_NREGS (CLASS, MODE)' should be
+ the maximum value of `HARD_REGNO_NREGS (REGNO, MODE)' for all
+ REGNO values in the class CLASS.
This macro helps control the handling of multiple-word values in
the reload pass.
@@ -29973,8 +30379,8 @@ return.
into floating-point registers on the Alpha extends them to 64 bits.
Therefore loading a 64-bit object and then storing it as a 32-bit
object does not store the low-order 32 bits, as would be the case
- for a normal register. Therefore, 'alpha.h' defines
- 'CANNOT_CHANGE_MODE_CLASS' as below:
+ for a normal register. Therefore, `alpha.h' defines
+ `CANNOT_CHANGE_MODE_CLASS' as below:
#define CANNOT_CHANGE_MODE_CLASS(FROM, TO, CLASS) \
(GET_MODE_SIZE (FROM) != GET_MODE_SIZE (TO) \
@@ -29982,66 +30388,68 @@ return.
-- Target Hook: bool TARGET_LRA_P (void)
A target hook which returns true if we use LRA instead of reload
- pass. It means that LRA was ported to the target. The default
+ pass. It means that LRA was ported to the target. The default
version of this target hook returns always false.
-- Target Hook: int TARGET_REGISTER_PRIORITY (int)
A target hook which returns the register priority number to which
- the register HARD_REGNO belongs to. The bigger the number, the
+ the register HARD_REGNO belongs to. The bigger the number, the
more preferable the hard register usage (when all other conditions
- are the same). This hook can be used to prefer some hard register
- over others in LRA. For example, some x86-64 register usage needs
- additional prefix which makes instructions longer. The hook can
- return lower priority number for such registers make them less
- favorable and as result making the generated code smaller. The
- default version of this target hook returns always zero.
+ are the same). This hook can be used to prefer some hard
+ register over others in LRA. For example, some x86-64 register
+ usage needs additional prefix which makes instructions longer.
+ The hook can return lower priority number for such registers make
+ them less favorable and as result making the generated code
+ smaller. The default version of this target hook returns always
+ zero.
-- Target Hook: bool TARGET_REGISTER_USAGE_LEVELING_P (void)
A target hook which returns true if we need register usage
leveling. That means if a few hard registers are equally good for
- the assignment, we choose the least used hard register. The
- register usage leveling may be profitable for some targets. Don't
- use the usage leveling for targets with conditional execution or
- targets with big register files as it hurts if-conversion and
- cross-jumping optimizations. The default version of this target
- hook returns always false.
+ the assignment, we choose the least used hard register. The
+ register usage leveling may be profitable for some targets.
+ Don't use the usage leveling for targets with conditional
+ execution or targets with big register files as it hurts
+ if-conversion and cross-jumping optimizations. The default
+ version of this target hook returns always false.
-- Target Hook: bool TARGET_DIFFERENT_ADDR_DISPLACEMENT_P (void)
A target hook which returns true if an address with the same
- structure can have different maximal legitimate displacement. For
- example, the displacement can depend on memory mode or on operand
- combinations in the insn. The default version of this target hook
- returns always false.
+ structure can have different maximal legitimate displacement.
+ For example, the displacement can depend on memory mode or on
+ operand combinations in the insn. The default version of this
+ target hook returns always false.
-- Target Hook: bool TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P (rtx SUBST)
- A target hook which returns 'true' if SUBST can't substitute safely
- pseudos with equivalent memory values during register allocation.
- The default version of this target hook returns 'false'. On most
- machines, this default should be used. For generally machines with
- non orthogonal register usage for addressing, such as SH, this hook
- can be used to avoid excessive spilling.
-
- -- Target Hook: bool TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT (rtx *DISP,
- rtx *OFFSET, machine_mode MODE)
- A target hook which returns 'true' if *DISP is legitimezed to valid
- address displacement with subtracting *OFFSET at memory mode MODE.
- The default version of this target hook returns 'false'. This hook
- will benefit machines with limited base plus displacement
+ A target hook which returns `true' if SUBST can't substitute
+ safely pseudos with equivalent memory values during register
+ allocation. The default version of this target hook returns
+ `false'. On most machines, this default should be used. For
+ generally machines with non orthogonal register usage for
+ addressing, such as SH, this hook can be used to avoid excessive
+ spilling.
+
+ -- Target Hook: bool TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT (rtx
+ *DISP, rtx *OFFSET, machine_mode MODE)
+ A target hook which returns `true' if *DISP is legitimezed to
+ valid address displacement with subtracting *OFFSET at memory mode
+ MODE. The default version of this target hook returns `false'.
+ This hook will benefit machines with limited base plus displacement
addressing.
-- Target Hook: reg_class_t TARGET_SPILL_CLASS (reg_class_t,
MACHINE_MODE)
This hook defines a class of registers which could be used for
- spilling pseudos of the given mode and class, or 'NO_REGS' if only
- memory should be used. Not defining this hook is equivalent to
- returning 'NO_REGS' for all inputs.
+ spilling pseudos of the given mode and class, or `NO_REGS' if
+ only memory should be used. Not defining this hook is equivalent
+ to returning `NO_REGS' for all inputs.
-- Target Hook: machine_mode TARGET_CSTORE_MODE (enum insn_code ICODE)
- This hook defines the machine mode to use for the boolean result of
- conditional store patterns. The ICODE argument is the instruction
- code for the cstore being performed. Not definiting this hook is
- the same as accepting the mode encoded into operand 0 of the cstore
- expander patterns.
+ This hook defines the machine mode to use for the boolean result
+ of conditional store patterns. The ICODE argument is the
+ instruction code for the cstore being performed. Not definiting
+ this hook is the same as accepting the mode encoded into operand
+ 0 of the cstore expander patterns.

File: gccint.info, Node: Stack and Calling, Next: Varargs, Prev: Register Classes, Up: Target Macros
@@ -30081,22 +30489,22 @@ Here is the basic stack layout.
Define this macro if pushing a word onto the stack moves the stack
pointer to a smaller address.
- When we say, "define this macro if ...", it means that the compiler
- checks this macro only with '#ifdef' so the precise definition used
- does not matter.
+ When we say, "define this macro if ...", it means that the
+ compiler checks this macro only with `#ifdef' so the precise
+ definition used does not matter.
-- Macro: STACK_PUSH_CODE
This macro defines the operation used when something is pushed on
- the stack. In RTL, a push operation will be '(set (mem
+ the stack. In RTL, a push operation will be `(set (mem
(STACK_PUSH_CODE (reg sp))) ...)'
- The choices are 'PRE_DEC', 'POST_DEC', 'PRE_INC', and 'POST_INC'.
+ The choices are `PRE_DEC', `POST_DEC', `PRE_INC', and `POST_INC'.
Which of these is correct depends on the stack direction and on
whether the stack pointer points to the last item on the stack or
whether it points to the space for the next item on the stack.
- The default is 'PRE_DEC' when 'STACK_GROWS_DOWNWARD' is defined,
- which is almost always right, and 'PRE_INC' otherwise, which is
+ The default is `PRE_DEC' when `STACK_GROWS_DOWNWARD' is defined,
+ which is almost always right, and `PRE_INC' otherwise, which is
often wrong.
-- Macro: FRAME_GROWS_DOWNWARD
@@ -30111,27 +30519,28 @@ Here is the basic stack layout.
Offset from the frame pointer to the first local variable slot to
be allocated.
- If 'FRAME_GROWS_DOWNWARD', find the next slot's offset by
- subtracting the first slot's length from 'STARTING_FRAME_OFFSET'.
+ If `FRAME_GROWS_DOWNWARD', find the next slot's offset by
+ subtracting the first slot's length from `STARTING_FRAME_OFFSET'.
Otherwise, it is found by adding the length of the first slot to
- the value 'STARTING_FRAME_OFFSET'.
+ the value `STARTING_FRAME_OFFSET'.
-- Macro: STACK_ALIGNMENT_NEEDED
Define to zero to disable final alignment of the stack during
reload. The nonzero default for this macro is suitable for most
ports.
- On ports where 'STARTING_FRAME_OFFSET' is nonzero or where there is
- a register save block following the local block that doesn't
- require alignment to 'STACK_BOUNDARY', it may be beneficial to
+ On ports where `STARTING_FRAME_OFFSET' is nonzero or where there
+ is a register save block following the local block that doesn't
+ require alignment to `STACK_BOUNDARY', it may be beneficial to
disable stack alignment and do it in the backend.
-- Macro: STACK_POINTER_OFFSET
Offset from the stack pointer register to the first location at
- which outgoing arguments are placed. If not specified, the default
- value of zero is used. This is the proper value for most machines.
+ which outgoing arguments are placed. If not specified, the
+ default value of zero is used. This is the proper value for most
+ machines.
- If 'ARGS_GROW_DOWNWARD', this is the offset to the location above
+ If `ARGS_GROW_DOWNWARD', this is the offset to the location above
the first location at which outgoing arguments are placed.
-- Macro: FIRST_PARM_OFFSET (FUNDECL)
@@ -30139,25 +30548,25 @@ Here is the basic stack layout.
address. On some machines it may depend on the data type of the
function.
- If 'ARGS_GROW_DOWNWARD', this is the offset to the location above
+ If `ARGS_GROW_DOWNWARD', this is the offset to the location above
the first argument's address.
-- Macro: STACK_DYNAMIC_OFFSET (FUNDECL)
Offset from the stack pointer register to an item dynamically
- allocated on the stack, e.g., by 'alloca'.
+ allocated on the stack, e.g., by `alloca'.
- The default value for this macro is 'STACK_POINTER_OFFSET' plus the
+ The default value for this macro is `STACK_POINTER_OFFSET' plus the
length of the outgoing arguments. The default is correct for most
- machines. See 'function.c' for details.
+ machines. See `function.c' for details.
-- Macro: INITIAL_FRAME_ADDRESS_RTX
A C expression whose value is RTL representing the address of the
- initial stack frame. This address is passed to 'RETURN_ADDR_RTX'
- and 'DYNAMIC_CHAIN_ADDRESS'. If you don't define this macro, a
+ initial stack frame. This address is passed to `RETURN_ADDR_RTX'
+ and `DYNAMIC_CHAIN_ADDRESS'. If you don't define this macro, a
reasonable default value will be used. Define this macro in order
to make frame pointer elimination work in the presence of
- '__builtin_frame_address (count)' and '__builtin_return_address
- (count)' for 'count' not equal to zero.
+ `__builtin_frame_address (count)' and `__builtin_return_address
+ (count)' for `count' not equal to zero.
-- Macro: DYNAMIC_CHAIN_ADDRESS (FRAMEADDR)
A C expression whose value is RTL representing the address in a
@@ -30172,16 +30581,16 @@ Here is the basic stack layout.
-- Macro: SETUP_FRAME_ADDRESSES
If defined, a C expression that produces the machine-specific code
to setup the stack so that arbitrary frames can be accessed. For
- example, on the SPARC, we must flush all of the register windows to
- the stack before we can access arbitrary stack frames. You will
- seldom need to define this macro.
+ example, on the SPARC, we must flush all of the register windows
+ to the stack before we can access arbitrary stack frames. You
+ will seldom need to define this macro.
-- Target Hook: rtx TARGET_BUILTIN_SETJMP_FRAME_VALUE (void)
This target hook should return an rtx that is used to store the
- address of the current frame into the built in 'setjmp' buffer.
- The default value, 'virtual_stack_vars_rtx', is correct for most
+ address of the current frame into the built in `setjmp' buffer.
+ The default value, `virtual_stack_vars_rtx', is correct for most
machines. One reason you may need to define this target hook is if
- 'hard_frame_pointer_rtx' is the appropriate value on your machine.
+ `hard_frame_pointer_rtx' is the appropriate value on your machine.
-- Macro: FRAME_ADDR_RTX (FRAMEADDR)
A C expression whose value is RTL representing the value of the
@@ -30193,13 +30602,13 @@ Here is the basic stack layout.
-- Macro: RETURN_ADDR_RTX (COUNT, FRAMEADDR)
A C expression whose value is RTL representing the value of the
- return address for the frame COUNT steps up from the current frame,
- after the prologue. FRAMEADDR is the frame pointer of the COUNT
- frame, or the frame pointer of the COUNT - 1 frame if
- 'RETURN_ADDR_IN_PREVIOUS_FRAME' is nonzero.
+ return address for the frame COUNT steps up from the current
+ frame, after the prologue. FRAMEADDR is the frame pointer of the
+ COUNT frame, or the frame pointer of the COUNT - 1 frame if
+ `RETURN_ADDR_IN_PREVIOUS_FRAME' is nonzero.
The value of the expression must always be the correct address when
- COUNT is zero, but may be 'NULL_RTX' if there is no way to
+ COUNT is zero, but may be `NULL_RTX' if there is no way to
determine the return address of other frames.
-- Macro: RETURN_ADDR_IN_PREVIOUS_FRAME
@@ -30211,23 +30620,23 @@ Here is the basic stack layout.
-- Macro: INCOMING_RETURN_ADDR_RTX
A C expression whose value is RTL representing the location of the
incoming return address at the beginning of any function, before
- the prologue. This RTL is either a 'REG', indicating that the
- return value is saved in 'REG', or a 'MEM' representing a location
+ the prologue. This RTL is either a `REG', indicating that the
+ return value is saved in `REG', or a `MEM' representing a location
in the stack.
You only need to define this macro if you want to support call
frame debugging information like that provided by DWARF 2.
- If this RTL is a 'REG', you should also define
- 'DWARF_FRAME_RETURN_COLUMN' to 'DWARF_FRAME_REGNUM (REGNO)'.
+ If this RTL is a `REG', you should also define
+ `DWARF_FRAME_RETURN_COLUMN' to `DWARF_FRAME_REGNUM (REGNO)'.
-- Macro: DWARF_ALT_FRAME_RETURN_COLUMN
A C expression whose value is an integer giving a DWARF 2 column
number that may be used as an alternative return column. The
column must not correspond to any gcc hard register (that is, it
- must not be in the range of 'DWARF_FRAME_REGNUM').
+ must not be in the range of `DWARF_FRAME_REGNUM').
- This macro can be useful if 'DWARF_FRAME_RETURN_COLUMN' is set to a
+ This macro can be useful if `DWARF_FRAME_RETURN_COLUMN' is set to a
general register, but an alternative column needs to be used for
signal frames. Some targets have also used different frame return
columns over time.
@@ -30237,8 +30646,8 @@ Here is the basic stack layout.
number that is considered to always have the value zero. This
should only be defined if the target has an architected zero
register, and someone decided it was a good idea to use that
- register number to terminate the stack backtrace. New ports should
- avoid this.
+ register number to terminate the stack backtrace. New ports
+ should avoid this.
-- Target Hook: void TARGET_DWARF_HANDLE_FRAME_UNSPEC (const char
*LABEL, rtx PATTERN, int INDEX)
@@ -30250,7 +30659,7 @@ Here is the basic stack layout.
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
to let the backend emit the call frame instructions. LABEL is the
CFI label attached to the insn, PATTERN is the pattern of the insn
- and INDEX is 'UNSPEC_INDEX' or 'UNSPECV_INDEX'.
+ and INDEX is `UNSPEC_INDEX' or `UNSPECV_INDEX'.
-- Macro: INCOMING_FRAME_SP_OFFSET
A C expression whose value is an integer giving the offset, in
@@ -30267,40 +30676,40 @@ Here is the basic stack layout.
A C expression whose value is an integer giving the offset, in
bytes, from the argument pointer to the canonical frame address
(cfa). The final value should coincide with that calculated by
- 'INCOMING_FRAME_SP_OFFSET'. Which is unfortunately not usable
+ `INCOMING_FRAME_SP_OFFSET'. Which is unfortunately not usable
during virtual register instantiation.
- The default value for this macro is 'FIRST_PARM_OFFSET (fundecl) +
+ The default value for this macro is `FIRST_PARM_OFFSET (fundecl) +
crtl->args.pretend_args_size', which is correct for most machines;
in general, the arguments are found immediately before the stack
frame. Note that this is not the case on some targets that save
- registers into the caller's frame, such as SPARC and rs6000, and so
- such targets need to define this macro.
+ registers into the caller's frame, such as SPARC and rs6000, and
+ so such targets need to define this macro.
- You only need to define this macro if the default is incorrect, and
- you want to support call frame debugging information like that
+ You only need to define this macro if the default is incorrect,
+ and you want to support call frame debugging information like that
provided by DWARF 2.
-- Macro: FRAME_POINTER_CFA_OFFSET (FUNDECL)
If defined, a C expression whose value is an integer giving the
offset in bytes from the frame pointer to the canonical frame
address (cfa). The final value should coincide with that
- calculated by 'INCOMING_FRAME_SP_OFFSET'.
+ calculated by `INCOMING_FRAME_SP_OFFSET'.
Normally the CFA is calculated as an offset from the argument
- pointer, via 'ARG_POINTER_CFA_OFFSET', but if the argument pointer
+ pointer, via `ARG_POINTER_CFA_OFFSET', but if the argument pointer
is variable due to the ABI, this may not be possible. If this
macro is defined, it implies that the virtual register
instantiation should be based on the frame pointer instead of the
- argument pointer. Only one of 'FRAME_POINTER_CFA_OFFSET' and
- 'ARG_POINTER_CFA_OFFSET' should be defined.
+ argument pointer. Only one of `FRAME_POINTER_CFA_OFFSET' and
+ `ARG_POINTER_CFA_OFFSET' should be defined.
-- Macro: CFA_FRAME_BASE_OFFSET (FUNDECL)
If defined, a C expression whose value is an integer giving the
- offset in bytes from the canonical frame address (cfa) to the frame
- base used in DWARF 2 debug information. The default is zero. A
- different value may reduce the size of debug information on some
- ports.
+ offset in bytes from the canonical frame address (cfa) to the
+ frame base used in DWARF 2 debug information. The default is
+ zero. A different value may reduce the size of debug information
+ on some ports.

File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Frame Layout, Up: Stack and Calling
@@ -30309,8 +30718,8 @@ File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Fram
---------------------------------
-- Macro: EH_RETURN_DATA_REGNO (N)
- A C expression whose value is the Nth register number used for data
- by exception handlers, or 'INVALID_REGNUM' if fewer than N
+ A C expression whose value is the Nth register number used for
+ data by exception handlers, or `INVALID_REGNUM' if fewer than N
registers are usable.
The exception handling library routines communicate with the
@@ -30350,22 +30759,22 @@ File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Fram
normal return address is stored. For targets that return by
popping an address off the stack, this might be a memory address
just below the _target_ call frame rather than inside the current
- call frame. If defined, 'EH_RETURN_STACKADJ_RTX' will have already
+ call frame. If defined, `EH_RETURN_STACKADJ_RTX' will have already
been assigned, so it may be used to calculate the location of the
target call frame.
Some targets have more complex requirements than storing to an
address calculable during initial code generation. In that case
- the 'eh_return' instruction pattern should be used instead.
+ the `eh_return' instruction pattern should be used instead.
If you want to support call frame exception handling, you must
- define either this macro or the 'eh_return' instruction pattern.
+ define either this macro or the `eh_return' instruction pattern.
-- Macro: RETURN_ADDR_OFFSET
If defined, an integer-valued C expression for which rtl will be
generated to add it to the exception handler address before it is
- searched in the exception handling tables, and to subtract it again
- from the address before using it to return to the exception
+ searched in the exception handling tables, and to subtract it
+ again from the address before using it to return to the exception
handler.
-- Macro: ASM_PREFERRED_EH_DATA_FORMAT (CODE, GLOBAL)
@@ -30377,7 +30786,7 @@ File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Fram
CODE is 0 for data, 1 for code labels, 2 for function pointers.
GLOBAL is true if the symbol may be affected by dynamic
relocations. The macro should return a combination of the
- 'DW_EH_PE_*' defines as found in 'dwarf2.h'.
+ `DW_EH_PE_*' defines as found in `dwarf2.h'.
If this macro is not defined, pointers will not be encoded but
represented directly.
@@ -30386,13 +30795,13 @@ File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Fram
ADDR, DONE)
This macro allows the target to emit whatever special magic is
required to represent the encoding chosen by
- 'ASM_PREFERRED_EH_DATA_FORMAT'. Generic code takes care of
+ `ASM_PREFERRED_EH_DATA_FORMAT'. Generic code takes care of
pc-relative and indirect encodings; this must be defined if the
target uses text-relative or data-relative encodings.
This is a C statement that branches to DONE if the format was
handled. ENCODING is the format chosen, SIZE is the number of
- bytes that the format occupies, ADDR is the 'SYMBOL_REF' to be
+ bytes that the format occupies, ADDR is the `SYMBOL_REF' to be
emitted.
-- Macro: MD_FALLBACK_FRAME_STATE_FOR (CONTEXT, FS)
@@ -30401,34 +30810,36 @@ File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Fram
unwind data available. The most common reason to implement this
macro is to unwind through signal frames.
- This macro is called from 'uw_frame_state_for' in 'unwind-dw2.c',
- 'unwind-dw2-xtensa.c' and 'unwind-ia64.c'. CONTEXT is an
- '_Unwind_Context'; FS is an '_Unwind_FrameState'. Examine
- 'context->ra' for the address of the code being executed and
- 'context->cfa' for the stack pointer value. If the frame can be
+ This macro is called from `uw_frame_state_for' in `unwind-dw2.c',
+ `unwind-dw2-xtensa.c' and `unwind-ia64.c'. CONTEXT is an
+ `_Unwind_Context'; FS is an `_Unwind_FrameState'. Examine
+ `context->ra' for the address of the code being executed and
+ `context->cfa' for the stack pointer value. If the frame can be
decoded, the register save addresses should be updated in FS and
- the macro should evaluate to '_URC_NO_REASON'. If the frame cannot
- be decoded, the macro should evaluate to '_URC_END_OF_STACK'.
+ the macro should evaluate to `_URC_NO_REASON'. If the frame
+ cannot be decoded, the macro should evaluate to
+ `_URC_END_OF_STACK'.
For proper signal handling in Java this macro is accompanied by
- 'MAKE_THROW_FRAME', defined in 'libjava/include/*-signal.h'
+ `MAKE_THROW_FRAME', defined in `libjava/include/*-signal.h'
headers.
-- Macro: MD_HANDLE_UNWABI (CONTEXT, FS)
This macro allows the target to add operating system specific code
- to the call-frame unwinder to handle the IA-64 '.unwabi' unwinding
+ to the call-frame unwinder to handle the IA-64 `.unwabi' unwinding
directive, usually used for signal or interrupt frames.
- This macro is called from 'uw_update_context' in libgcc's
- 'unwind-ia64.c'. CONTEXT is an '_Unwind_Context'; FS is an
- '_Unwind_FrameState'. Examine 'fs->unwabi' for the abi and context
- in the '.unwabi' directive. If the '.unwabi' directive can be
- handled, the register save addresses should be updated in FS.
+ This macro is called from `uw_update_context' in libgcc's
+ `unwind-ia64.c'. CONTEXT is an `_Unwind_Context'; FS is an
+ `_Unwind_FrameState'. Examine `fs->unwabi' for the abi and
+ context in the `.unwabi' directive. If the `.unwabi' directive
+ can be handled, the register save addresses should be updated in
+ FS.
-- Macro: TARGET_USES_WEAK_UNWIND_INFO
A C expression that evaluates to true if the target requires unwind
- info to be given comdat linkage. Define it to be '1' if comdat
- linkage is necessary. The default is '0'.
+ info to be given comdat linkage. Define it to be `1' if comdat
+ linkage is necessary. The default is `0'.

File: gccint.info, Node: Stack Checking, Next: Frame Registers, Prev: Exception Handling, Up: Stack and Calling
@@ -30437,20 +30848,20 @@ File: gccint.info, Node: Stack Checking, Next: Frame Registers, Prev: Excepti
--------------------------------------------
GCC will check that stack references are within the boundaries of the
-stack, if the option '-fstack-check' is specified, in one of three ways:
+stack, if the option `-fstack-check' is specified, in one of three ways:
- 1. If the value of the 'STACK_CHECK_BUILTIN' macro is nonzero, GCC
+ 1. If the value of the `STACK_CHECK_BUILTIN' macro is nonzero, GCC
will assume that you have arranged for full stack checking to be
done at appropriate places in the configuration files. GCC will
not do other special processing.
- 2. If 'STACK_CHECK_BUILTIN' is zero and the value of the
- 'STACK_CHECK_STATIC_BUILTIN' macro is nonzero, GCC will assume that
- you have arranged for static stack checking (checking of the static
- stack frame of functions) to be done at appropriate places in the
- configuration files. GCC will only emit code to do dynamic stack
- checking (checking on dynamic stack allocations) using the third
- approach below.
+ 2. If `STACK_CHECK_BUILTIN' is zero and the value of the
+ `STACK_CHECK_STATIC_BUILTIN' macro is nonzero, GCC will assume
+ that you have arranged for static stack checking (checking of the
+ static stack frame of functions) to be done at appropriate places
+ in the configuration files. GCC will only emit code to do dynamic
+ stack checking (checking on dynamic stack allocations) using the
+ third approach below.
3. If neither of the above are true, GCC will generate code to
periodically "probe" the stack pointer using the values of the
@@ -30458,15 +30869,15 @@ stack, if the option '-fstack-check' is specified, in one of three ways:
If neither STACK_CHECK_BUILTIN nor STACK_CHECK_STATIC_BUILTIN is
defined, GCC will change its allocation strategy for large objects if
-the option '-fstack-check' is specified: they will always be allocated
-dynamically if their size exceeds 'STACK_CHECK_MAX_VAR_SIZE' bytes.
+the option `-fstack-check' is specified: they will always be allocated
+dynamically if their size exceeds `STACK_CHECK_MAX_VAR_SIZE' bytes.
-- Macro: STACK_CHECK_BUILTIN
A nonzero value if stack checking is done by the configuration
files in a machine-dependent manner. You should define this macro
if stack checking is required by the ABI of your machine or if you
- would like to do stack checking in some more efficient way than the
- generic approach. The default value of this macro is zero.
+ would like to do stack checking in some more efficient way than
+ the generic approach. The default value of this macro is zero.
-- Macro: STACK_CHECK_STATIC_BUILTIN
A nonzero value if static stack checking is done by the
@@ -30476,26 +30887,26 @@ dynamically if their size exceeds 'STACK_CHECK_MAX_VAR_SIZE' bytes.
value of this macro is zero.
-- Macro: STACK_CHECK_PROBE_INTERVAL_EXP
- An integer specifying the interval at which GCC must generate stack
- probe instructions, defined as 2 raised to this integer. You will
- normally define this macro so that the interval be no larger than
- the size of the "guard pages" at the end of a stack area. The
- default value of 12 (4096-byte interval) is suitable for most
- systems.
+ An integer specifying the interval at which GCC must generate
+ stack probe instructions, defined as 2 raised to this integer.
+ You will normally define this macro so that the interval be no
+ larger than the size of the "guard pages" at the end of a stack
+ area. The default value of 12 (4096-byte interval) is suitable
+ for most systems.
-- Macro: STACK_CHECK_MOVING_SP
An integer which is nonzero if GCC should move the stack pointer
page by page when doing probes. This can be necessary on systems
where the stack pointer contains the bottom address of the memory
area accessible to the executing thread at any point in time. In
- this situation an alternate signal stack is required in order to be
- able to recover from a stack overflow. The default value of this
- macro is zero.
+ this situation an alternate signal stack is required in order to
+ be able to recover from a stack overflow. The default value of
+ this macro is zero.
-- Macro: STACK_CHECK_PROTECT
The number of bytes of stack needed to recover from a stack
overflow, for languages where such a recovery is supported. The
- default value of 75 words with the 'setjmp'/'longjmp'-based
+ default value of 75 words with the `setjmp'/`longjmp'-based
exception handling mechanism and 8192 bytes with other exception
handling mechanisms should be adequate for most machines.
@@ -30506,11 +30917,11 @@ in the opposite case.
-- Macro: STACK_CHECK_MAX_FRAME_SIZE
The maximum size of a stack frame, in bytes. GCC will generate
probe instructions in non-leaf functions to ensure at least this
- many bytes of stack are available. If a stack frame is larger than
- this size, stack checking will not be reliable and GCC will issue a
- warning. The default is chosen so that GCC only generates one
- instruction on most systems. You should normally not change the
- default value of this macro.
+ many bytes of stack are available. If a stack frame is larger
+ than this size, stack checking will not be reliable and GCC will
+ issue a warning. The default is chosen so that GCC only generates
+ one instruction on most systems. You should normally not change
+ the default value of this macro.
-- Macro: STACK_CHECK_FIXED_FRAME_SIZE
GCC uses this value to generate the above warning message. It
@@ -30522,7 +30933,7 @@ in the opposite case.
-- Macro: STACK_CHECK_MAX_VAR_SIZE
The maximum size, in bytes, of an object that GCC will place in the
fixed area of the stack frame when the user specifies
- '-fstack-check'. GCC computed the default from the values of the
+ `-fstack-check'. GCC computed the default from the values of the
above macros and you will normally not need to override that
default.
@@ -30536,57 +30947,57 @@ This discusses registers that address the stack frame.
-- Macro: STACK_POINTER_REGNUM
The register number of the stack pointer register, which must also
- be a fixed register according to 'FIXED_REGISTERS'. On most
+ be a fixed register according to `FIXED_REGISTERS'. On most
machines, the hardware determines which register this is.
-- Macro: FRAME_POINTER_REGNUM
The register number of the frame pointer register, which is used to
access automatic variables in the stack frame. On some machines,
- the hardware determines which register this is. On other machines,
- you can choose any register you wish for this purpose.
+ the hardware determines which register this is. On other
+ machines, you can choose any register you wish for this purpose.
-- Macro: HARD_FRAME_POINTER_REGNUM
On some machines the offset between the frame pointer and starting
offset of the automatic variables is not known until after register
allocation has been done (for example, because the saved registers
are between these two locations). On those machines, define
- 'FRAME_POINTER_REGNUM' the number of a special, fixed register to
+ `FRAME_POINTER_REGNUM' the number of a special, fixed register to
be used internally until the offset is known, and define
- 'HARD_FRAME_POINTER_REGNUM' to be the actual hard register number
+ `HARD_FRAME_POINTER_REGNUM' to be the actual hard register number
used for the frame pointer.
You should define this macro only in the very rare circumstances
when it is not possible to calculate the offset between the frame
- pointer and the automatic variables until after register allocation
- has been completed. When this macro is defined, you must also
- indicate in your definition of 'ELIMINABLE_REGS' how to eliminate
- 'FRAME_POINTER_REGNUM' into either 'HARD_FRAME_POINTER_REGNUM' or
- 'STACK_POINTER_REGNUM'.
+ pointer and the automatic variables until after register
+ allocation has been completed. When this macro is defined, you
+ must also indicate in your definition of `ELIMINABLE_REGS' how to
+ eliminate `FRAME_POINTER_REGNUM' into either
+ `HARD_FRAME_POINTER_REGNUM' or `STACK_POINTER_REGNUM'.
Do not define this macro if it would be the same as
- 'FRAME_POINTER_REGNUM'.
+ `FRAME_POINTER_REGNUM'.
-- Macro: ARG_POINTER_REGNUM
The register number of the arg pointer register, which is used to
- access the function's argument list. On some machines, this is the
- same as the frame pointer register. On some machines, the hardware
- determines which register this is. On other machines, you can
- choose any register you wish for this purpose. If this is not the
- same register as the frame pointer register, then you must mark it
- as a fixed register according to 'FIXED_REGISTERS', or arrange to
- be able to eliminate it (*note Elimination::).
+ access the function's argument list. On some machines, this is
+ the same as the frame pointer register. On some machines, the
+ hardware determines which register this is. On other machines,
+ you can choose any register you wish for this purpose. If this is
+ not the same register as the frame pointer register, then you must
+ mark it as a fixed register according to `FIXED_REGISTERS', or
+ arrange to be able to eliminate it (*note Elimination::).
-- Macro: HARD_FRAME_POINTER_IS_FRAME_POINTER
Define this to a preprocessor constant that is nonzero if
- 'hard_frame_pointer_rtx' and 'frame_pointer_rtx' should be the
- same. The default definition is '(HARD_FRAME_POINTER_REGNUM ==
+ `hard_frame_pointer_rtx' and `frame_pointer_rtx' should be the
+ same. The default definition is `(HARD_FRAME_POINTER_REGNUM ==
FRAME_POINTER_REGNUM)'; you only need to define this macro if that
definition is not suitable for use in preprocessor conditionals.
-- Macro: HARD_FRAME_POINTER_IS_ARG_POINTER
Define this to a preprocessor constant that is nonzero if
- 'hard_frame_pointer_rtx' and 'arg_pointer_rtx' should be the same.
- The default definition is '(HARD_FRAME_POINTER_REGNUM ==
+ `hard_frame_pointer_rtx' and `arg_pointer_rtx' should be the same.
+ The default definition is `(HARD_FRAME_POINTER_REGNUM ==
ARG_POINTER_REGNUM)'; you only need to define this macro if that
definition is not suitable for use in preprocessor conditionals.
@@ -30594,10 +31005,10 @@ This discusses registers that address the stack frame.
The register number of the return address pointer register, which
is used to access the current function's return address from the
stack. On some machines, the return address is not at a fixed
- offset from the frame pointer or stack pointer or argument pointer.
- This register can be defined to point to the return address on the
- stack, and then be converted by 'ELIMINABLE_REGS' into either the
- frame pointer or stack pointer.
+ offset from the frame pointer or stack pointer or argument
+ pointer. This register can be defined to point to the return
+ address on the stack, and then be converted by `ELIMINABLE_REGS'
+ into either the frame pointer or stack pointer.
Do not define this macro unless there is no other way to get the
return address from the stack.
@@ -30605,34 +31016,34 @@ This discusses registers that address the stack frame.
-- Macro: STATIC_CHAIN_REGNUM
-- Macro: STATIC_CHAIN_INCOMING_REGNUM
Register numbers used for passing a function's static chain
- pointer. If register windows are used, the register number as seen
- by the called function is 'STATIC_CHAIN_INCOMING_REGNUM', while the
- register number as seen by the calling function is
- 'STATIC_CHAIN_REGNUM'. If these registers are the same,
- 'STATIC_CHAIN_INCOMING_REGNUM' need not be defined.
+ pointer. If register windows are used, the register number as
+ seen by the called function is `STATIC_CHAIN_INCOMING_REGNUM',
+ while the register number as seen by the calling function is
+ `STATIC_CHAIN_REGNUM'. If these registers are the same,
+ `STATIC_CHAIN_INCOMING_REGNUM' need not be defined.
The static chain register need not be a fixed register.
If the static chain is passed in memory, these macros should not be
- defined; instead, the 'TARGET_STATIC_CHAIN' hook should be used.
+ defined; instead, the `TARGET_STATIC_CHAIN' hook should be used.
-- Target Hook: rtx TARGET_STATIC_CHAIN (const_tree FNDECL_OR_TYPE,
bool INCOMING_P)
- This hook replaces the use of 'STATIC_CHAIN_REGNUM' et al for
+ This hook replaces the use of `STATIC_CHAIN_REGNUM' et al for
targets that may use different static chain locations for different
nested functions. This may be required if the target has function
attributes that affect the calling conventions of the function and
those calling conventions use different static chain locations.
- The default version of this hook uses 'STATIC_CHAIN_REGNUM' et al.
+ The default version of this hook uses `STATIC_CHAIN_REGNUM' et al.
If the static chain is passed in memory, this hook should be used
- to provide rtx giving 'mem' expressions that denote where they are
- stored. Often the 'mem' expression as seen by the caller will be
- at an offset from the stack pointer and the 'mem' expression as
- seen by the callee will be at an offset from the frame pointer.
- The variables 'stack_pointer_rtx', 'frame_pointer_rtx', and
- 'arg_pointer_rtx' will have been initialized and should be used to
+ to provide rtx giving `mem' expressions that denote where they are
+ stored. Often the `mem' expression as seen by the caller will be
+ at an offset from the stack pointer and the `mem' expression as
+ seen by the callee will be at an offset from the frame pointer. The
+ variables `stack_pointer_rtx', `frame_pointer_rtx', and
+ `arg_pointer_rtx' will have been initialized and should be used to
refer to those items.
-- Macro: DWARF_FRAME_REGISTERS
@@ -30650,18 +31061,16 @@ This discusses registers that address the stack frame.
call-saved.
If this macro is not defined, it defaults to
- 'FIRST_PSEUDO_REGISTER'.
+ `FIRST_PSEUDO_REGISTER'.
-- Macro: PRE_GCC3_DWARF_FRAME_REGISTERS
-
- This macro is similar to 'DWARF_FRAME_REGISTERS', but is provided
+ This macro is similar to `DWARF_FRAME_REGISTERS', but is provided
for backward compatibility in pre GCC 3.0 compiled code.
If this macro is not defined, it defaults to
- 'DWARF_FRAME_REGISTERS'.
+ `DWARF_FRAME_REGISTERS'.
-- Macro: DWARF_REG_TO_UNWIND_COLUMN (REGNO)
-
Define this macro if the target's representation for dwarf
registers is different than the internal representation for unwind
column. Given a dwarf register, this macro should return the
@@ -30670,33 +31079,33 @@ This discusses registers that address the stack frame.
See the PowerPC's SPE target for an example.
-- Macro: DWARF_FRAME_REGNUM (REGNO)
-
Define this macro if the target's representation for dwarf
registers used in .eh_frame or .debug_frame is different from that
used in other debug info sections. Given a GCC hard register
number, this macro should return the .eh_frame register number.
- The default is 'DBX_REGISTER_NUMBER (REGNO)'.
+ The default is `DBX_REGISTER_NUMBER (REGNO)'.
- -- Macro: DWARF2_FRAME_REG_OUT (REGNO, FOR_EH)
+ -- Macro: DWARF2_FRAME_REG_OUT (REGNO, FOR_EH)
Define this macro to map register numbers held in the call frame
- info that GCC has collected using 'DWARF_FRAME_REGNUM' to those
- that should be output in .debug_frame ('FOR_EH' is zero) and
- .eh_frame ('FOR_EH' is nonzero). The default is to return 'REGNO'.
+ info that GCC has collected using `DWARF_FRAME_REGNUM' to those
+ that should be output in .debug_frame (`FOR_EH' is zero) and
+ .eh_frame (`FOR_EH' is nonzero). The default is to return `REGNO'.
- -- Macro: REG_VALUE_IN_UNWIND_CONTEXT
+ -- Macro: REG_VALUE_IN_UNWIND_CONTEXT
Define this macro if the target stores register values as
- '_Unwind_Word' type in unwind context. It should be defined if
- target register size is larger than the size of 'void *'. The
- default is to store register values as 'void *' type.
+ `_Unwind_Word' type in unwind context. It should be defined if
+ target register size is larger than the size of `void *'. The
+ default is to store register values as `void *' type.
- -- Macro: ASSUME_EXTENDED_UNWIND_CONTEXT
+ -- Macro: ASSUME_EXTENDED_UNWIND_CONTEXT
Define this macro to be 1 if the target always uses extended unwind
context with version, args_size and by_value fields. If it is
undefined, it will be defined to 1 when
- 'REG_VALUE_IN_UNWIND_CONTEXT' is defined and 0 otherwise.
+ `REG_VALUE_IN_UNWIND_CONTEXT' is defined and 0 otherwise.
+

File: gccint.info, Node: Elimination, Next: Stack Arguments, Prev: Frame Registers, Up: Stack and Calling
@@ -30707,41 +31116,41 @@ File: gccint.info, Node: Elimination, Next: Stack Arguments, Prev: Frame Regi
This is about eliminating the frame pointer and arg pointer.
-- Target Hook: bool TARGET_FRAME_POINTER_REQUIRED (void)
- This target hook should return 'true' if a function must have and
+ This target hook should return `true' if a function must have and
use a frame pointer. This target hook is called in the reload
- pass. If its return value is 'true' the function will have a frame
- pointer.
+ pass. If its return value is `true' the function will have a
+ frame pointer.
This target hook can in principle examine the current function and
decide according to the facts, but on most machines the constant
- 'false' or the constant 'true' suffices. Use 'false' when the
+ `false' or the constant `true' suffices. Use `false' when the
machine allows code to be generated with no frame pointer, and
- doing so saves some time or space. Use 'true' when there is no
+ doing so saves some time or space. Use `true' when there is no
possible advantage to avoiding a frame pointer.
In certain cases, the compiler does not know how to produce valid
code without a frame pointer. The compiler recognizes those cases
and automatically gives the function a frame pointer regardless of
- what 'TARGET_FRAME_POINTER_REQUIRED' returns. You don't need to
+ what `TARGET_FRAME_POINTER_REQUIRED' returns. You don't need to
worry about them.
In a function that does not require a frame pointer, the frame
pointer register can be allocated for ordinary usage, unless you
- mark it as a fixed register. See 'FIXED_REGISTERS' for more
+ mark it as a fixed register. See `FIXED_REGISTERS' for more
information.
- Default return value is 'false'.
+ Default return value is `false'.
-- Macro: INITIAL_FRAME_POINTER_OFFSET (DEPTH-VAR)
A C statement to store in the variable DEPTH-VAR the difference
between the frame pointer and the stack pointer values immediately
after the function prologue. The value would be computed from
- information such as the result of 'get_frame_size ()' and the
- tables of registers 'regs_ever_live' and 'call_used_regs'.
+ information such as the result of `get_frame_size ()' and the
+ tables of registers `regs_ever_live' and `call_used_regs'.
- If 'ELIMINABLE_REGS' is defined, this macro will be not be used and
+ If `ELIMINABLE_REGS' is defined, this macro will be not be used and
need not be defined. Otherwise, it must be defined even if
- 'TARGET_FRAME_POINTER_REQUIRED' always returns true; in that case,
+ `TARGET_FRAME_POINTER_REQUIRED' always returns true; in that case,
you may set DEPTH-VAR to anything.
-- Macro: ELIMINABLE_REGS
@@ -30755,12 +31164,12 @@ This is about eliminating the frame pointer and arg pointer.
initializations, each of which specifies an original and
replacement register.
- On some machines, the position of the argument pointer is not known
- until the compilation is completed. In such a case, a separate
- hard register must be used for the argument pointer. This register
- can be eliminated by replacing it with either the frame pointer or
- the argument pointer, depending on whether or not the frame pointer
- has been eliminated.
+ On some machines, the position of the argument pointer is not
+ known until the compilation is completed. In such a case, a
+ separate hard register must be used for the argument pointer.
+ This register can be eliminated by replacing it with either the
+ frame pointer or the argument pointer, depending on whether or not
+ the frame pointer has been eliminated.
In this case, you might specify:
#define ELIMINABLE_REGS \
@@ -30773,19 +31182,19 @@ This is about eliminating the frame pointer and arg pointer.
-- Target Hook: bool TARGET_CAN_ELIMINATE (const int FROM_REG, const
int TO_REG)
- This target hook should returns 'true' if the compiler is allowed
+ This target hook should returns `true' if the compiler is allowed
to try to replace register number FROM_REG with register number
- TO_REG. This target hook need only be defined if 'ELIMINABLE_REGS'
- is defined, and will usually be 'true', since most of the cases
+ TO_REG. This target hook need only be defined if `ELIMINABLE_REGS'
+ is defined, and will usually be `true', since most of the cases
preventing register elimination are things that the compiler
already knows about.
- Default return value is 'true'.
+ Default return value is `true'.
-- Macro: INITIAL_ELIMINATION_OFFSET (FROM-REG, TO-REG, OFFSET-VAR)
- This macro is similar to 'INITIAL_FRAME_POINTER_OFFSET'. It
+ This macro is similar to `INITIAL_FRAME_POINTER_OFFSET'. It
specifies the initial difference between the specified pair of
- registers. This macro must be defined if 'ELIMINABLE_REGS' is
+ registers. This macro must be defined if `ELIMINABLE_REGS' is
defined.

@@ -30799,9 +31208,9 @@ stack. See the following section for other macros that control passing
certain arguments in registers.
-- Target Hook: bool TARGET_PROMOTE_PROTOTYPES (const_tree FNTYPE)
- This target hook returns 'true' if an argument declared in a
- prototype as an integral type smaller than 'int' should actually be
- passed as an 'int'. In addition to avoiding errors in certain
+ This target hook returns `true' if an argument declared in a
+ prototype as an integral type smaller than `int' should actually be
+ passed as an `int'. In addition to avoiding errors in certain
cases of mismatch, it also makes for better code on certain
machines. The default is to not promote prototypes.
@@ -30810,13 +31219,13 @@ certain arguments in registers.
outgoing arguments. If the target machine does not have a push
instruction, set it to zero. That directs GCC to use an alternate
strategy: to allocate the entire argument block and then store the
- arguments into it. When 'PUSH_ARGS' is nonzero, 'PUSH_ROUNDING'
+ arguments into it. When `PUSH_ARGS' is nonzero, `PUSH_ROUNDING'
must be defined too.
-- Macro: PUSH_ARGS_REVERSED
A C expression. If nonzero, function arguments will be evaluated
from last to first, rather than from first to last. If this macro
- is not defined, it defaults to 'PUSH_ARGS' on targets where the
+ is not defined, it defaults to `PUSH_ARGS' on targets where the
stack and args grow in opposite directions, and 0 otherwise.
-- Macro: PUSH_ROUNDING (NPUSHED)
@@ -30839,11 +31248,11 @@ certain arguments in registers.
-- Macro: ACCUMULATE_OUTGOING_ARGS
A C expression. If nonzero, the maximum amount of space required
for outgoing arguments will be computed and placed into
- 'crtl->outgoing_args_size'. No space will be pushed onto the stack
- for each call; instead, the function prologue should increase the
- stack frame size by this amount.
+ `crtl->outgoing_args_size'. No space will be pushed onto the
+ stack for each call; instead, the function prologue should
+ increase the stack frame size by this amount.
- Setting both 'PUSH_ARGS' and 'ACCUMULATE_OUTGOING_ARGS' is not
+ Setting both `PUSH_ARGS' and `ACCUMULATE_OUTGOING_ARGS' is not
proper.
-- Macro: REG_PARM_STACK_SPACE (FNDECL)
@@ -30851,40 +31260,40 @@ certain arguments in registers.
been allocated for arguments even when their values are passed in
registers.
- The value of this macro is the size, in bytes, of the area reserved
- for arguments passed in registers for the function represented by
- FNDECL, which can be zero if GCC is calling a library function.
- The argument FNDECL can be the FUNCTION_DECL, or the type itself of
- the function.
+ The value of this macro is the size, in bytes, of the area
+ reserved for arguments passed in registers for the function
+ represented by FNDECL, which can be zero if GCC is calling a
+ library function. The argument FNDECL can be the FUNCTION_DECL,
+ or the type itself of the function.
This space can be allocated by the caller, or be a part of the
- machine-dependent stack frame: 'OUTGOING_REG_PARM_STACK_SPACE' says
+ machine-dependent stack frame: `OUTGOING_REG_PARM_STACK_SPACE' says
which.
-- Macro: INCOMING_REG_PARM_STACK_SPACE (FNDECL)
- Like 'REG_PARM_STACK_SPACE', but for incoming register arguments.
+ Like `REG_PARM_STACK_SPACE', but for incoming register arguments.
Define this macro if space guaranteed when compiling a function
- body is different to space required when making a call, a situation
- that can arise with K&R style function definitions.
+ body is different to space required when making a call, a
+ situation that can arise with K&R style function definitions.
-- Macro: OUTGOING_REG_PARM_STACK_SPACE (FNTYPE)
Define this to a nonzero value if it is the responsibility of the
caller to allocate the area reserved for arguments passed in
- registers when calling a function of FNTYPE. FNTYPE may be NULL if
- the function called is a library function.
+ registers when calling a function of FNTYPE. FNTYPE may be NULL
+ if the function called is a library function.
- If 'ACCUMULATE_OUTGOING_ARGS' is defined, this macro controls
+ If `ACCUMULATE_OUTGOING_ARGS' is defined, this macro controls
whether the space for these arguments counts in the value of
- 'crtl->outgoing_args_size'.
+ `crtl->outgoing_args_size'.
-- Macro: STACK_PARMS_IN_REG_PARM_AREA
- Define this macro if 'REG_PARM_STACK_SPACE' is defined, but the
+ Define this macro if `REG_PARM_STACK_SPACE' is defined, but the
stack parameters don't skip the area specified by it.
- Normally, when a parameter is not passed in registers, it is placed
- on the stack beyond the 'REG_PARM_STACK_SPACE' area. Defining this
- macro suppresses this behavior and causes the parameter to be
- passed on the stack in its natural location.
+ Normally, when a parameter is not passed in registers, it is
+ placed on the stack beyond the `REG_PARM_STACK_SPACE' area.
+ Defining this macro suppresses this behavior and causes the
+ parameter to be passed on the stack in its natural location.
-- Target Hook: int TARGET_RETURN_POPS_ARGS (tree FUNDECL, tree
FUNTYPE, int SIZE)
@@ -30895,41 +31304,41 @@ certain arguments in registers.
FUNDECL is a C variable whose value is a tree node that describes
the function in question. Normally it is a node of type
- 'FUNCTION_DECL' that describes the declaration of the function.
- From this you can obtain the 'DECL_ATTRIBUTES' of the function.
+ `FUNCTION_DECL' that describes the declaration of the function.
+ From this you can obtain the `DECL_ATTRIBUTES' of the function.
FUNTYPE is a C variable whose value is a tree node that describes
the function in question. Normally it is a node of type
- 'FUNCTION_TYPE' that describes the data type of the function. From
- this it is possible to obtain the data types of the value and
+ `FUNCTION_TYPE' that describes the data type of the function.
+ From this it is possible to obtain the data types of the value and
arguments (if known).
- When a call to a library function is being considered, FUNDECL will
- contain an identifier node for the library function. Thus, if you
- need to distinguish among various library functions, you can do so
- by their names. Note that "library function" in this context means
- a function used to perform arithmetic, whose name is known
- specially in the compiler and was not mentioned in the C code being
- compiled.
+ When a call to a library function is being considered, FUNDECL
+ will contain an identifier node for the library function. Thus, if
+ you need to distinguish among various library functions, you can
+ do so by their names. Note that "library function" in this
+ context means a function used to perform arithmetic, whose name is
+ known specially in the compiler and was not mentioned in the C
+ code being compiled.
- SIZE is the number of bytes of arguments passed on the stack. If a
- variable number of bytes is passed, it is zero, and argument
+ SIZE is the number of bytes of arguments passed on the stack. If
+ a variable number of bytes is passed, it is zero, and argument
popping will always be the responsibility of the calling function.
On the VAX, all functions always pop their arguments, so the
definition of this macro is SIZE. On the 68000, using the standard
calling convention, no functions pop their arguments, so the value
of the macro is always 0 in this case. But an alternative calling
- convention is available in which functions that take a fixed number
- of arguments pop them but other functions (such as 'printf') pop
- nothing (the caller pops all). When this convention is in use,
- FUNTYPE is examined to determine whether a function takes a fixed
- number of arguments.
+ convention is available in which functions that take a fixed
+ number of arguments pop them but other functions (such as
+ `printf') pop nothing (the caller pops all). When this convention
+ is in use, FUNTYPE is examined to determine whether a function
+ takes a fixed number of arguments.
-- Macro: CALL_POPS_ARGS (CUM)
A C expression that should indicate the number of bytes a call
sequence pops off the stack. It is added to the value of
- 'RETURN_POPS_ARGS' when compiling a function call.
+ `RETURN_POPS_ARGS' when compiling a function call.
CUM is the variable in which all arguments to the called function
have been accumulated.
@@ -30938,7 +31347,7 @@ certain arguments in registers.
used that pops certain registers off the stack, depending on the
arguments that have been passed to the function. Since this is a
property of the call site, not of the called function,
- 'RETURN_POPS_ARGS' is not appropriate.
+ `RETURN_POPS_ARGS' is not appropriate.

File: gccint.info, Node: Register Arguments, Next: Scalar Return, Prev: Stack Arguments, Up: Stack and Calling
@@ -30958,74 +31367,75 @@ the stack.
The arguments are CA, which summarizes all the previous arguments;
MODE, the machine mode of the argument; TYPE, the data type of the
argument as a tree node or 0 if that is not known (which happens
- for C support library functions); and NAMED, which is 'true' for an
- ordinary argument and 'false' for nameless arguments that
- correspond to '...' in the called function's prototype. TYPE can
+ for C support library functions); and NAMED, which is `true' for
+ an ordinary argument and `false' for nameless arguments that
+ correspond to `...' in the called function's prototype. TYPE can
be an incomplete type if a syntax error has previously occurred.
- The return value is usually either a 'reg' RTX for the hard
+ The return value is usually either a `reg' RTX for the hard
register in which to pass the argument, or zero to pass the
argument on the stack.
- The return value can be a 'const_int' which means argument is
+ The return value can be a `const_int' which means argument is
passed in a target specific slot with specified number. Target
hooks should be used to store or load argument in such case. See
- 'TARGET_STORE_BOUNDS_FOR_ARG' and 'TARGET_LOAD_BOUNDS_FOR_ARG' for
+ `TARGET_STORE_BOUNDS_FOR_ARG' and `TARGET_LOAD_BOUNDS_FOR_ARG' for
more information.
- The value of the expression can also be a 'parallel' RTX. This is
- used when an argument is passed in multiple locations. The mode of
- the 'parallel' should be the mode of the entire argument. The
- 'parallel' holds any number of 'expr_list' pairs; each one
+ The value of the expression can also be a `parallel' RTX. This is
+ used when an argument is passed in multiple locations. The mode
+ of the `parallel' should be the mode of the entire argument. The
+ `parallel' holds any number of `expr_list' pairs; each one
describes where part of the argument is passed. In each
- 'expr_list' the first operand must be a 'reg' RTX for the hard
+ `expr_list' the first operand must be a `reg' RTX for the hard
register in which to pass this part of the argument, and the mode
of the register RTX indicates how large this part of the argument
- is. The second operand of the 'expr_list' is a 'const_int' which
+ is. The second operand of the `expr_list' is a `const_int' which
gives the offset in bytes into the entire argument of where this
- part starts. As a special exception the first 'expr_list' in the
- 'parallel' RTX may have a first operand of zero. This indicates
+ part starts. As a special exception the first `expr_list' in the
+ `parallel' RTX may have a first operand of zero. This indicates
that the entire argument is also stored on the stack.
- The last time this hook is called, it is called with 'MODE ==
- VOIDmode', and its result is passed to the 'call' or 'call_value'
+ The last time this hook is called, it is called with `MODE ==
+ VOIDmode', and its result is passed to the `call' or `call_value'
pattern as operands 2 and 3 respectively.
- The usual way to make the ISO library 'stdarg.h' work on a machine
+ The usual way to make the ISO library `stdarg.h' work on a machine
where some arguments are usually passed in registers, is to cause
- nameless arguments to be passed on the stack instead. This is done
- by making 'TARGET_FUNCTION_ARG' return 0 whenever NAMED is 'false'.
-
- You may use the hook 'targetm.calls.must_pass_in_stack' in the
- definition of this macro to determine if this argument is of a type
- that must be passed in the stack. If 'REG_PARM_STACK_SPACE' is not
- defined and 'TARGET_FUNCTION_ARG' returns nonzero for such an
- argument, the compiler will abort. If 'REG_PARM_STACK_SPACE' is
- defined, the argument will be computed in the stack and then loaded
- into a register.
+ nameless arguments to be passed on the stack instead. This is
+ done by making `TARGET_FUNCTION_ARG' return 0 whenever NAMED is
+ `false'.
+
+ You may use the hook `targetm.calls.must_pass_in_stack' in the
+ definition of this macro to determine if this argument is of a
+ type that must be passed in the stack. If `REG_PARM_STACK_SPACE'
+ is not defined and `TARGET_FUNCTION_ARG' returns nonzero for such
+ an argument, the compiler will abort. If `REG_PARM_STACK_SPACE' is
+ defined, the argument will be computed in the stack and then
+ loaded into a register.
-- Target Hook: bool TARGET_MUST_PASS_IN_STACK (machine_mode MODE,
const_tree TYPE)
- This target hook should return 'true' if we should not pass TYPE
- solely in registers. The file 'expr.h' defines a definition that
- is usually appropriate, refer to 'expr.h' for additional
+ This target hook should return `true' if we should not pass TYPE
+ solely in registers. The file `expr.h' defines a definition that
+ is usually appropriate, refer to `expr.h' for additional
documentation.
- -- Target Hook: rtx TARGET_FUNCTION_INCOMING_ARG (cumulative_args_t CA,
- machine_mode MODE, const_tree TYPE, bool NAMED)
+ -- Target Hook: rtx TARGET_FUNCTION_INCOMING_ARG (cumulative_args_t
+ CA, machine_mode MODE, const_tree TYPE, bool NAMED)
Define this hook if the target machine has "register windows", so
that the register in which a function sees an arguments is not
necessarily the same as the one in which the caller passed the
argument.
- For such machines, 'TARGET_FUNCTION_ARG' computes the register in
+ For such machines, `TARGET_FUNCTION_ARG' computes the register in
which the caller passes the value, and
- 'TARGET_FUNCTION_INCOMING_ARG' should be defined in a similar
+ `TARGET_FUNCTION_INCOMING_ARG' should be defined in a similar
fashion to tell the function being called where the arguments will
arrive.
- If 'TARGET_FUNCTION_INCOMING_ARG' is not defined,
- 'TARGET_FUNCTION_ARG' serves both purposes.
+ If `TARGET_FUNCTION_INCOMING_ARG' is not defined,
+ `TARGET_FUNCTION_ARG' serves both purposes.
-- Target Hook: bool TARGET_USE_PSEUDO_PIC_REG (void)
This hook should return 1 in case pseudo register should be created
@@ -31045,27 +31455,27 @@ the stack.
On some machines, certain arguments must be passed partially in
registers and partially in memory. On these machines, typically
the first few words of arguments are passed in registers, and the
- rest on the stack. If a multi-word argument (a 'double' or a
+ rest on the stack. If a multi-word argument (a `double' or a
structure) crosses that boundary, its first few words must be
passed in registers and the rest must be pushed. This macro tells
the compiler when this occurs, and how many bytes should go in
registers.
- 'TARGET_FUNCTION_ARG' for these arguments should return the first
+ `TARGET_FUNCTION_ARG' for these arguments should return the first
register to be used by the caller for this argument; likewise
- 'TARGET_FUNCTION_INCOMING_ARG', for the called function.
+ `TARGET_FUNCTION_INCOMING_ARG', for the called function.
-- Target Hook: bool TARGET_PASS_BY_REFERENCE (cumulative_args_t CUM,
machine_mode MODE, const_tree TYPE, bool NAMED)
- This target hook should return 'true' if an argument at the
+ This target hook should return `true' if an argument at the
position indicated by CUM should be passed by reference. This
predicate is queried after target independent reasons for being
- passed by reference, such as 'TREE_ADDRESSABLE (type)'.
+ passed by reference, such as `TREE_ADDRESSABLE (type)'.
- If the hook returns true, a copy of that argument is made in memory
- and a pointer to the argument is passed instead of the argument
- itself. The pointer is passed in whatever way is appropriate for
- passing a pointer to that type.
+ If the hook returns true, a copy of that argument is made in
+ memory and a pointer to the argument is passed instead of the
+ argument itself. The pointer is passed in whatever way is
+ appropriate for passing a pointer to that type.
-- Target Hook: bool TARGET_CALLEE_COPIES (cumulative_args_t CUM,
machine_mode MODE, const_tree TYPE, bool NAMED)
@@ -31082,104 +31492,104 @@ the stack.
-- Macro: CUMULATIVE_ARGS
A C type for declaring a variable that is used as the first
- argument of 'TARGET_FUNCTION_ARG' and other related values. For
- some target machines, the type 'int' suffices and can hold the
+ argument of `TARGET_FUNCTION_ARG' and other related values. For
+ some target machines, the type `int' suffices and can hold the
number of bytes of argument so far.
- There is no need to record in 'CUMULATIVE_ARGS' anything about the
+ There is no need to record in `CUMULATIVE_ARGS' anything about the
arguments that have been passed on the stack. The compiler has
other variables to keep track of that. For target machines on
which all arguments are passed on the stack, there is no need to
- store anything in 'CUMULATIVE_ARGS'; however, the data structure
- must exist and should not be empty, so use 'int'.
+ store anything in `CUMULATIVE_ARGS'; however, the data structure
+ must exist and should not be empty, so use `int'.
-- Macro: OVERRIDE_ABI_FORMAT (FNDECL)
If defined, this macro is called before generating any code for a
function, but after the CFUN descriptor for the function has been
- created. The back end may use this macro to update CFUN to reflect
- an ABI other than that which would normally be used by default. If
- the compiler is generating code for a compiler-generated function,
- FNDECL may be 'NULL'.
+ created. The back end may use this macro to update CFUN to
+ reflect an ABI other than that which would normally be used by
+ default. If the compiler is generating code for a
+ compiler-generated function, FNDECL may be `NULL'.
-- Macro: INIT_CUMULATIVE_ARGS (CUM, FNTYPE, LIBNAME, FNDECL,
N_NAMED_ARGS)
A C statement (sans semicolon) for initializing the variable CUM
for the state at the beginning of the argument list. The variable
- has type 'CUMULATIVE_ARGS'. The value of FNTYPE is the tree node
- for the data type of the function which will receive the args, or 0
- if the args are to a compiler support library function. For direct
- calls that are not libcalls, FNDECL contain the declaration node of
- the function. FNDECL is also set when 'INIT_CUMULATIVE_ARGS' is
- used to find arguments for the function being compiled.
- N_NAMED_ARGS is set to the number of named arguments, including a
- structure return address if it is passed as a parameter, when
- making a call. When processing incoming arguments, N_NAMED_ARGS is
- set to -1.
+ has type `CUMULATIVE_ARGS'. The value of FNTYPE is the tree node
+ for the data type of the function which will receive the args, or
+ 0 if the args are to a compiler support library function. For
+ direct calls that are not libcalls, FNDECL contain the declaration
+ node of the function. FNDECL is also set when
+ `INIT_CUMULATIVE_ARGS' is used to find arguments for the function
+ being compiled. N_NAMED_ARGS is set to the number of named
+ arguments, including a structure return address if it is passed as
+ a parameter, when making a call. When processing incoming
+ arguments, N_NAMED_ARGS is set to -1.
When processing a call to a compiler support library function,
- LIBNAME identifies which one. It is a 'symbol_ref' rtx which
+ LIBNAME identifies which one. It is a `symbol_ref' rtx which
contains the name of the function, as a string. LIBNAME is 0 when
an ordinary C function call is being processed. Thus, each time
this macro is called, either LIBNAME or FNTYPE is nonzero, but
never both of them at once.
-- Macro: INIT_CUMULATIVE_LIBCALL_ARGS (CUM, MODE, LIBNAME)
- Like 'INIT_CUMULATIVE_ARGS' but only used for outgoing libcalls, it
- gets a 'MODE' argument instead of FNTYPE, that would be 'NULL'.
+ Like `INIT_CUMULATIVE_ARGS' but only used for outgoing libcalls,
+ it gets a `MODE' argument instead of FNTYPE, that would be `NULL'.
INDIRECT would always be zero, too. If this macro is not defined,
- 'INIT_CUMULATIVE_ARGS (cum, NULL_RTX, libname, 0)' is used instead.
+ `INIT_CUMULATIVE_ARGS (cum, NULL_RTX, libname, 0)' is used instead.
-- Macro: INIT_CUMULATIVE_INCOMING_ARGS (CUM, FNTYPE, LIBNAME)
- Like 'INIT_CUMULATIVE_ARGS' but overrides it for the purposes of
+ Like `INIT_CUMULATIVE_ARGS' but overrides it for the purposes of
finding the arguments for the function being compiled. If this
- macro is undefined, 'INIT_CUMULATIVE_ARGS' is used instead.
+ macro is undefined, `INIT_CUMULATIVE_ARGS' is used instead.
The value passed for LIBNAME is always 0, since library routines
with special calling conventions are never compiled with GCC. The
- argument LIBNAME exists for symmetry with 'INIT_CUMULATIVE_ARGS'.
+ argument LIBNAME exists for symmetry with `INIT_CUMULATIVE_ARGS'.
- -- Target Hook: void TARGET_FUNCTION_ARG_ADVANCE (cumulative_args_t CA,
- machine_mode MODE, const_tree TYPE, bool NAMED)
+ -- Target Hook: void TARGET_FUNCTION_ARG_ADVANCE (cumulative_args_t
+ CA, machine_mode MODE, const_tree TYPE, bool NAMED)
This hook updates the summarizer variable pointed to by CA to
advance past an argument in the argument list. The values MODE,
TYPE and NAMED describe that argument. Once this is done, the
variable CUM is suitable for analyzing the _following_ argument
- with 'TARGET_FUNCTION_ARG', etc.
+ with `TARGET_FUNCTION_ARG', etc.
This hook need not do anything if the argument in question was
- passed on the stack. The compiler knows how to track the amount of
- stack space used for arguments without any special help.
+ passed on the stack. The compiler knows how to track the amount
+ of stack space used for arguments without any special help.
-- Macro: FUNCTION_ARG_OFFSET (MODE, TYPE)
If defined, a C expression that is the number of bytes to add to
the offset of the argument passed in memory. This is needed for
- the SPU, which passes 'char' and 'short' arguments in the preferred
+ the SPU, which passes `char' and `short' arguments in the preferred
slot that is in the middle of the quad word instead of starting at
the top.
-- Macro: FUNCTION_ARG_PADDING (MODE, TYPE)
If defined, a C expression which determines whether, and in which
direction, to pad out an argument with extra space. The value
- should be of type 'enum direction': either 'upward' to pad above
- the argument, 'downward' to pad below, or 'none' to inhibit
+ should be of type `enum direction': either `upward' to pad above
+ the argument, `downward' to pad below, or `none' to inhibit
padding.
The _amount_ of padding is not controlled by this macro, but by the
- target hook 'TARGET_FUNCTION_ARG_ROUND_BOUNDARY'. It is always
+ target hook `TARGET_FUNCTION_ARG_ROUND_BOUNDARY'. It is always
just enough to reach the next multiple of that boundary.
This macro has a default definition which is right for most
- systems. For little-endian machines, the default is to pad upward.
- For big-endian machines, the default is to pad downward for an
- argument of constant size shorter than an 'int', and upward
+ systems. For little-endian machines, the default is to pad
+ upward. For big-endian machines, the default is to pad downward
+ for an argument of constant size shorter than an `int', and upward
otherwise.
-- Macro: PAD_VARARGS_DOWN
If defined, a C expression which determines whether the default
implementation of va_arg will attempt to pad down before reading
the next argument, if that argument is smaller than its aligned
- space as controlled by 'PARM_BOUNDARY'. If this macro is not
- defined, all such arguments are padded down if 'BYTES_BIG_ENDIAN'
+ space as controlled by `PARM_BOUNDARY'. If this macro is not
+ defined, all such arguments are padded down if `BYTES_BIG_ENDIAN'
is true.
-- Macro: BLOCK_REG_PADDING (MODE, TYPE, FIRST)
@@ -31187,23 +31597,23 @@ the stack.
registers and memory. FIRST is nonzero if this is the only
element. Defining this macro allows better control of register
function parameters on big-endian machines, without using
- 'PARALLEL' rtl. In particular, 'MUST_PASS_IN_STACK' need not test
+ `PARALLEL' rtl. In particular, `MUST_PASS_IN_STACK' need not test
padding and mode of types in registers, as there is no longer a
- "wrong" part of a register; For example, a three byte aggregate may
- be passed in the high part of a register if so required.
+ "wrong" part of a register; For example, a three byte aggregate
+ may be passed in the high part of a register if so required.
- -- Target Hook: unsigned int TARGET_FUNCTION_ARG_BOUNDARY (machine_mode
- MODE, const_tree TYPE)
+ -- Target Hook: unsigned int TARGET_FUNCTION_ARG_BOUNDARY
+ (machine_mode MODE, const_tree TYPE)
This hook returns the alignment boundary, in bits, of an argument
with the specified mode and type. The default hook returns
- 'PARM_BOUNDARY' for all arguments.
+ `PARM_BOUNDARY' for all arguments.
-- Target Hook: unsigned int TARGET_FUNCTION_ARG_ROUND_BOUNDARY
(machine_mode MODE, const_tree TYPE)
- Normally, the size of an argument is rounded up to 'PARM_BOUNDARY',
- which is the default value for this hook. You can define this hook
- to return a different value if an argument size must be rounded to
- a larger value.
+ Normally, the size of an argument is rounded up to `PARM_BOUNDARY',
+ which is the default value for this hook. You can define this
+ hook to return a different value if an argument size must be
+ rounded to a larger value.
-- Macro: FUNCTION_ARG_REGNO_P (REGNO)
A C expression that is nonzero if REGNO is the number of a hard
@@ -31218,23 +31628,23 @@ the stack.
as two scalar parameters. By default, GCC will attempt to pack
complex arguments into the target's word size. Some ABIs require
complex arguments to be split and treated as their individual
- components. For example, on AIX64, complex floats should be passed
- in a pair of floating point registers, even though a complex float
- would fit in one 64-bit floating point register.
+ components. For example, on AIX64, complex floats should be
+ passed in a pair of floating point registers, even though a
+ complex float would fit in one 64-bit floating point register.
- The default value of this hook is 'NULL', which is treated as
+ The default value of this hook is `NULL', which is treated as
always false.
-- Target Hook: tree TARGET_BUILD_BUILTIN_VA_LIST (void)
- This hook returns a type node for 'va_list' for the target. The
- default version of the hook returns 'void*'.
+ This hook returns a type node for `va_list' for the target. The
+ default version of the hook returns `void*'.
- -- Target Hook: int TARGET_ENUM_VA_LIST_P (int IDX, const char **PNAME,
- tree *PTREE)
- This target hook is used in function 'c_common_nodes_and_builtins'
+ -- Target Hook: int TARGET_ENUM_VA_LIST_P (int IDX, const char
+ **PNAME, tree *PTREE)
+ This target hook is used in function `c_common_nodes_and_builtins'
to iterate through the target specific builtin types for va_list.
- The variable IDX is used as iterator. PNAME has to be a pointer to
- a 'const char *' and PTREE a pointer to a 'tree' typed variable.
+ The variable IDX is used as iterator. PNAME has to be a pointer to
+ a `const char *' and PTREE a pointer to a `tree' typed variable.
The arguments PNAME and PTREE are used to store the result of this
macro and are set to the name of the va_list builtin type and its
internal type. If the return value of this macro is zero, then
@@ -31244,41 +31654,42 @@ the stack.
-- Target Hook: tree TARGET_FN_ABI_VA_LIST (tree FNDECL)
This hook returns the va_list type of the calling convention
specified by FNDECL. The default version of this hook returns
- 'va_list_type_node'.
+ `va_list_type_node'.
-- Target Hook: tree TARGET_CANONICAL_VA_LIST_TYPE (tree TYPE)
This hook returns the va_list type of the calling convention
- specified by the type of TYPE. If TYPE is not a valid va_list
- type, it returns 'NULL_TREE'.
+ specified by the type of TYPE. If TYPE is not a valid va_list
+ type, it returns `NULL_TREE'.
-- Target Hook: tree TARGET_GIMPLIFY_VA_ARG_EXPR (tree VALIST, tree
TYPE, gimple_seq *PRE_P, gimple_seq *POST_P)
- This hook performs target-specific gimplification of 'VA_ARG_EXPR'.
- The first two parameters correspond to the arguments to 'va_arg';
- the latter two are as in 'gimplify.c:gimplify_expr'.
+ This hook performs target-specific gimplification of
+ `VA_ARG_EXPR'. The first two parameters correspond to the
+ arguments to `va_arg'; the latter two are as in
+ `gimplify.c:gimplify_expr'.
-- Target Hook: bool TARGET_VALID_POINTER_MODE (machine_mode MODE)
Define this to return nonzero if the port can handle pointers with
machine mode MODE. The default version of this hook returns true
- for both 'ptr_mode' and 'Pmode'.
+ for both `ptr_mode' and `Pmode'.
-- Target Hook: bool TARGET_REF_MAY_ALIAS_ERRNO (struct ao_ref *REF)
- Define this to return nonzero if the memory reference REF may alias
- with the system C library errno location. The default version of
- this hook assumes the system C library errno location is either a
- declaration of type int or accessed by dereferencing a pointer to
- int.
+ Define this to return nonzero if the memory reference REF may
+ alias with the system C library errno location. The default
+ version of this hook assumes the system C library errno location
+ is either a declaration of type int or accessed by dereferencing
+ a pointer to int.
-- Target Hook: bool TARGET_SCALAR_MODE_SUPPORTED_P (machine_mode MODE)
Define this to return nonzero if the port is prepared to handle
insns involving scalar mode MODE. For a scalar mode to be
- considered supported, all the basic arithmetic and comparisons must
- work.
+ considered supported, all the basic arithmetic and comparisons
+ must work.
- The default version of this hook returns true for any mode required
- to handle the basic C types (as defined by the port). Included
- here are the double-word arithmetic supported by the code in
- 'optabs.c'.
+ The default version of this hook returns true for any mode
+ required to handle the basic C types (as defined by the port).
+ Included here are the double-word arithmetic supported by the code
+ in `optabs.c'.
-- Target Hook: bool TARGET_VECTOR_MODE_SUPPORTED_P (machine_mode MODE)
Define this to return nonzero if the port is prepared to handle
@@ -31289,7 +31700,7 @@ the stack.
unsigned HOST_WIDE_INT NELEMS)
Return true if GCC should try to use a scalar mode to store an
array of NELEMS elements, given that each element has mode MODE.
- Returning true here overrides the usual 'MAX_FIXED_MODE' limit and
+ Returning true here overrides the usual `MAX_FIXED_MODE' limit and
allows GCC to use any defined integer mode.
One use of this hook is to support vector load and store operations
@@ -31305,24 +31716,24 @@ the stack.
int8x8_t val[3];
} int8x8x3_t;
- If this hook allows 'val' to have a scalar mode, then 'int8x8x3_t'
- can have the same mode. GCC can then store 'int8x8x3_t's in
+ If this hook allows `val' to have a scalar mode, then `int8x8x3_t'
+ can have the same mode. GCC can then store `int8x8x3_t's in
registers rather than forcing them onto the stack.
-- Target Hook: bool TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P
(machine_mode MODE)
Define this to return nonzero if libgcc provides support for the
floating-point mode MODE, which is known to pass
- 'TARGET_SCALAR_MODE_SUPPORTED_P'. The default version of this hook
- returns true for all of 'SFmode', 'DFmode', 'XFmode' and 'TFmode',
- if such modes exist.
+ `TARGET_SCALAR_MODE_SUPPORTED_P'. The default version of this
+ hook returns true for all of `SFmode', `DFmode', `XFmode' and
+ `TFmode', if such modes exist.
-- Target Hook: bool TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P
(machine_mode MODE)
Define this to return nonzero for machine modes for which the port
has small register classes. If this target hook returns nonzero
- for a given MODE, the compiler will try to minimize the lifetime of
- registers in MODE. The hook may be called with 'VOIDmode' as
+ for a given MODE, the compiler will try to minimize the lifetime
+ of registers in MODE. The hook may be called with `VOIDmode' as
argument. In this case, the hook is expected to return nonzero if
it returns nonzero for any mode.
@@ -31336,20 +31747,20 @@ the stack.
in an instruction, but the machine modes of the registers set or
used in the instruction are already known. And for some machines,
register classes are small for, say, integer registers but not for
- floating point registers. For example, the AMD x86-64 architecture
- requires specific registers for the legacy x86 integer
- instructions, but there are many SSE registers for floating point
- operations. On such targets, a good strategy may be to return
- nonzero from this hook for 'INTEGRAL_MODE_P' machine modes but zero
- for the SSE register classes.
-
- The default version of this hook returns false for any mode. It is
- always safe to redefine this hook to return with a nonzero value.
- But if you unnecessarily define it, you will reduce the amount of
- optimizations that can be performed in some cases. If you do not
- define this hook to return a nonzero value when it is required, the
- compiler will run out of spill registers and print a fatal error
- message.
+ floating point registers. For example, the AMD x86-64
+ architecture requires specific registers for the legacy x86
+ integer instructions, but there are many SSE registers for
+ floating point operations. On such targets, a good strategy may
+ be to return nonzero from this hook for `INTEGRAL_MODE_P' machine
+ modes but zero for the SSE register classes.
+
+ The default version of this hook returns false for any mode. It
+ is always safe to redefine this hook to return with a nonzero
+ value. But if you unnecessarily define it, you will reduce the
+ amount of optimizations that can be performed in some cases. If
+ you do not define this hook to return a nonzero value when it is
+ required, the compiler will run out of spill registers and print a
+ fatal error message.

File: gccint.info, Node: Scalar Return, Next: Aggregate Return, Prev: Register Arguments, Up: Stack and Calling
@@ -31362,49 +31773,48 @@ values--values that can fit in registers.
-- Target Hook: rtx TARGET_FUNCTION_VALUE (const_tree RET_TYPE,
const_tree FN_DECL_OR_TYPE, bool OUTGOING)
-
Define this to return an RTX representing the place where a
function returns or receives a value of data type RET_TYPE, a tree
node representing a data type. FN_DECL_OR_TYPE is a tree node
- representing 'FUNCTION_DECL' or 'FUNCTION_TYPE' of a function being
- called. If OUTGOING is false, the hook should compute the register
- in which the caller will see the return value. Otherwise, the hook
- should return an RTX representing the place where a function
- returns a value.
+ representing `FUNCTION_DECL' or `FUNCTION_TYPE' of a function
+ being called. If OUTGOING is false, the hook should compute the
+ register in which the caller will see the return value.
+ Otherwise, the hook should return an RTX representing the place
+ where a function returns a value.
- On many machines, only 'TYPE_MODE (RET_TYPE)' is relevant.
+ On many machines, only `TYPE_MODE (RET_TYPE)' is relevant.
(Actually, on most machines, scalar values are returned in the same
place regardless of mode.) The value of the expression is usually
- a 'reg' RTX for the hard register where the return value is stored.
- The value can also be a 'parallel' RTX, if the return value is in
- multiple places. See 'TARGET_FUNCTION_ARG' for an explanation of
- the 'parallel' form. Note that the callee will populate every
- location specified in the 'parallel', but if the first element of
- the 'parallel' contains the whole return value, callers will use
+ a `reg' RTX for the hard register where the return value is stored.
+ The value can also be a `parallel' RTX, if the return value is in
+ multiple places. See `TARGET_FUNCTION_ARG' for an explanation of
+ the `parallel' form. Note that the callee will populate every
+ location specified in the `parallel', but if the first element of
+ the `parallel' contains the whole return value, callers will use
that element as the canonical location and ignore the others. The
- m68k port uses this type of 'parallel' to return pointers in both
- '%a0' (the canonical location) and '%d0'.
+ m68k port uses this type of `parallel' to return pointers in both
+ `%a0' (the canonical location) and `%d0'.
- If 'TARGET_PROMOTE_FUNCTION_RETURN' returns true, you must apply
- the same promotion rules specified in 'PROMOTE_MODE' if VALTYPE is
+ If `TARGET_PROMOTE_FUNCTION_RETURN' returns true, you must apply
+ the same promotion rules specified in `PROMOTE_MODE' if VALTYPE is
a scalar type.
If the precise function being called is known, FUNC is a tree node
- ('FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This
- makes it possible to use a different value-returning convention for
- specific functions when all their calls are known.
+ (`FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This
+ makes it possible to use a different value-returning convention
+ for specific functions when all their calls are known.
Some target machines have "register windows" so that the register
- in which a function returns its value is not the same as the one in
- which the caller sees the value. For such machines, you should
+ in which a function returns its value is not the same as the one
+ in which the caller sees the value. For such machines, you should
return different RTX depending on OUTGOING.
- 'TARGET_FUNCTION_VALUE' is not used for return values with
+ `TARGET_FUNCTION_VALUE' is not used for return values with
aggregate data types, because these are returned in another way.
- See 'TARGET_STRUCT_VALUE_RTX' and related macros, below.
+ See `TARGET_STRUCT_VALUE_RTX' and related macros, below.
-- Macro: FUNCTION_VALUE (VALTYPE, FUNC)
- This macro has been deprecated. Use 'TARGET_FUNCTION_VALUE' for a
+ This macro has been deprecated. Use `TARGET_FUNCTION_VALUE' for a
new target instead.
-- Macro: LIBCALL_VALUE (MODE)
@@ -31434,7 +31844,7 @@ values--values that can fit in registers.
register in which the values of called function may come back.
A register whose use for returning values is limited to serving as
- the second of a pair (for a value of type 'double', say) need not
+ the second of a pair (for a value of type `double', say) need not
be recognized by this macro. So for most machines, this definition
suffices:
@@ -31445,15 +31855,15 @@ values--values that can fit in registers.
macro should recognize only the caller's register numbers.
This macro has been deprecated. Use
- 'TARGET_FUNCTION_VALUE_REGNO_P' for a new target instead.
+ `TARGET_FUNCTION_VALUE_REGNO_P' for a new target instead.
-- Target Hook: bool TARGET_FUNCTION_VALUE_REGNO_P (const unsigned int
REGNO)
- A target hook that return 'true' if REGNO is the number of a hard
+ A target hook that return `true' if REGNO is the number of a hard
register in which the values of called function may come back.
A register whose use for returning values is limited to serving as
- the second of a pair (for a value of type 'double', say) need not
+ the second of a pair (for a value of type `double', say) need not
be recognized by this target hook.
If the machine has register windows, so that the caller and the
@@ -31464,28 +31874,28 @@ values--values that can fit in registers.
used.
-- Macro: APPLY_RESULT_SIZE
- Define this macro if 'untyped_call' and 'untyped_return' need more
- space than is implied by 'FUNCTION_VALUE_REGNO_P' for saving and
+ Define this macro if `untyped_call' and `untyped_return' need more
+ space than is implied by `FUNCTION_VALUE_REGNO_P' for saving and
restoring an arbitrary return value.
-- Target Hook: bool TARGET_OMIT_STRUCT_RETURN_REG
Normally, when a function returns a structure by memory, the
address is passed as an invisible pointer argument, but the
- compiler also arranges to return the address from the function like
- it would a normal pointer return value. Define this to true if
- that behaviour is undesirable on your target.
+ compiler also arranges to return the address from the function
+ like it would a normal pointer return value. Define this to true
+ if that behaviour is undesirable on your target.
-- Target Hook: bool TARGET_RETURN_IN_MSB (const_tree TYPE)
- This hook should return true if values of type TYPE are returned at
- the most significant end of a register (in other words, if they are
- padded at the least significant end). You can assume that TYPE is
- returned in a register; the caller is required to check this.
+ This hook should return true if values of type TYPE are returned
+ at the most significant end of a register (in other words, if they
+ are padded at the least significant end). You can assume that TYPE
+ is returned in a register; the caller is required to check this.
- Note that the register provided by 'TARGET_FUNCTION_VALUE' must be
+ Note that the register provided by `TARGET_FUNCTION_VALUE' must be
able to hold the complete return value. For example, if a 1-, 2-
or 3-byte structure is returned at the most significant end of a
- 4-byte register, 'TARGET_FUNCTION_VALUE' should provide an 'SImode'
- rtx.
+ 4-byte register, `TARGET_FUNCTION_VALUE' should provide an
+ `SImode' rtx.

File: gccint.info, Node: Aggregate Return, Next: Caller Saves, Prev: Scalar Return, Up: Stack and Calling
@@ -31493,10 +31903,10 @@ File: gccint.info, Node: Aggregate Return, Next: Caller Saves, Prev: Scalar R
17.9.9 How Large Values Are Returned
------------------------------------
-When a function value's mode is 'BLKmode' (and in some other cases), the
-value is not returned according to 'TARGET_FUNCTION_VALUE' (*note Scalar
-Return::). Instead, the caller passes the address of a block of memory
-in which the value should be stored. This address is called the
+When a function value's mode is `BLKmode' (and in some other cases),
+the value is not returned according to `TARGET_FUNCTION_VALUE' (*note
+Scalar Return::). Instead, the caller passes the address of a block of
+memory in which the value should be stored. This address is called the
"structure value address".
This section describes how to control returning structure values in
@@ -31507,49 +31917,49 @@ memory.
This target hook should return a nonzero value to say to return the
function value in memory, just as large structures are always
returned. Here TYPE will be the data type of the value, and FNTYPE
- will be the type of the function doing the returning, or 'NULL' for
+ will be the type of the function doing the returning, or `NULL' for
libcalls.
- Note that values of mode 'BLKmode' must be explicitly handled by
- this function. Also, the option '-fpcc-struct-return' takes effect
- regardless of this macro. On most systems, it is possible to leave
- the hook undefined; this causes a default definition to be used,
- whose value is the constant 1 for 'BLKmode' values, and 0
+ Note that values of mode `BLKmode' must be explicitly handled by
+ this function. Also, the option `-fpcc-struct-return' takes
+ effect regardless of this macro. On most systems, it is possible
+ to leave the hook undefined; this causes a default definition to
+ be used, whose value is the constant 1 for `BLKmode' values, and 0
otherwise.
Do not use this hook to indicate that structures and unions should
always be returned in memory. You should instead use
- 'DEFAULT_PCC_STRUCT_RETURN' to indicate this.
+ `DEFAULT_PCC_STRUCT_RETURN' to indicate this.
-- Macro: DEFAULT_PCC_STRUCT_RETURN
Define this macro to be 1 if all structure and union return values
must be in memory. Since this results in slower code, this should
- be defined only if needed for compatibility with other compilers or
- with an ABI. If you define this macro to be 0, then the
+ be defined only if needed for compatibility with other compilers
+ or with an ABI. If you define this macro to be 0, then the
conventions used for structure and union return values are decided
- by the 'TARGET_RETURN_IN_MEMORY' target hook.
+ by the `TARGET_RETURN_IN_MEMORY' target hook.
If not defined, this defaults to the value 1.
-- Target Hook: rtx TARGET_STRUCT_VALUE_RTX (tree FNDECL, int INCOMING)
This target hook should return the location of the structure value
- address (normally a 'mem' or 'reg'), or 0 if the address is passed
- as an "invisible" first argument. Note that FNDECL may be 'NULL',
+ address (normally a `mem' or `reg'), or 0 if the address is passed
+ as an "invisible" first argument. Note that FNDECL may be `NULL',
for libcalls. You do not need to define this target hook if the
address is always passed as an "invisible" first argument.
On some architectures the place where the structure value address
is found by the called function is not the same place that the
- caller put it. This can be due to register windows, or it could be
- because the function prologue moves it to a different place.
- INCOMING is '1' or '2' when the location is needed in the context
- of the called function, and '0' in the context of the caller.
+ caller put it. This can be due to register windows, or it could
+ be because the function prologue moves it to a different place.
+ INCOMING is `1' or `2' when the location is needed in the context
+ of the called function, and `0' in the context of the caller.
- If INCOMING is nonzero and the address is to be found on the stack,
- return a 'mem' which refers to the frame pointer. If INCOMING is
- '2', the result is being used to fetch the structure value address
- at the beginning of a function. If you need to emit adjusting
- code, you should do it at this point.
+ If INCOMING is nonzero and the address is to be found on the
+ stack, return a `mem' which refers to the frame pointer. If
+ INCOMING is `2', the result is being used to fetch the structure
+ value address at the beginning of a function. If you need to emit
+ adjusting code, you should do it at this point.
-- Macro: PCC_STATIC_STRUCT_RETURN
Define this macro if the usual system convention on the target
@@ -31557,21 +31967,21 @@ memory.
function to return the address of a static variable containing the
value.
- Do not define this if the usual system convention is for the caller
- to pass an address to the subroutine.
+ Do not define this if the usual system convention is for the
+ caller to pass an address to the subroutine.
- This macro has effect in '-fpcc-struct-return' mode, but it does
- nothing when you use '-freg-struct-return' mode.
+ This macro has effect in `-fpcc-struct-return' mode, but it does
+ nothing when you use `-freg-struct-return' mode.
-- Target Hook: machine_mode TARGET_GET_RAW_RESULT_MODE (int REGNO)
This target hook returns the mode to be used when accessing raw
- return registers in '__builtin_return'. Define this macro if the
+ return registers in `__builtin_return'. Define this macro if the
value in REG_RAW_MODE is not correct.
-- Target Hook: machine_mode TARGET_GET_RAW_ARG_MODE (int REGNO)
This target hook returns the mode to be used when accessing raw
- argument registers in '__builtin_apply_args'. Define this macro if
- the value in REG_RAW_MODE is not correct.
+ argument registers in `__builtin_apply_args'. Define this macro
+ if the value in REG_RAW_MODE is not correct.

File: gccint.info, Node: Caller Saves, Next: Function Entry, Prev: Aggregate Return, Up: Stack and Calling
@@ -31586,9 +31996,9 @@ must live across calls.
-- Macro: HARD_REGNO_CALLER_SAVE_MODE (REGNO, NREGS)
A C expression specifying which mode is required for saving NREGS
of a pseudo-register in call-clobbered hard register REGNO. If
- REGNO is unsuitable for caller save, 'VOIDmode' should be returned.
- For most machines this macro need not be defined since GCC will
- select the smallest suitable mode.
+ REGNO is unsuitable for caller save, `VOIDmode' should be
+ returned. For most machines this macro need not be defined since
+ GCC will select the smallest suitable mode.

File: gccint.info, Node: Function Entry, Next: Profiling, Prev: Caller Saves, Up: Stack and Calling
@@ -31601,41 +32011,42 @@ This section describes the macros that output function entry
-- Target Hook: void TARGET_ASM_FUNCTION_PROLOGUE (FILE *FILE,
HOST_WIDE_INT SIZE)
- If defined, a function that outputs the assembler code for entry to
- a function. The prologue is responsible for setting up the stack
- frame, initializing the frame pointer register, saving registers
- that must be saved, and allocating SIZE additional bytes of storage
- for the local variables. SIZE is an integer. FILE is a stdio
- stream to which the assembler code should be output.
+ If defined, a function that outputs the assembler code for entry
+ to a function. The prologue is responsible for setting up the
+ stack frame, initializing the frame pointer register, saving
+ registers that must be saved, and allocating SIZE additional bytes
+ of storage for the local variables. SIZE is an integer. FILE is
+ a stdio stream to which the assembler code should be output.
The label for the beginning of the function need not be output by
this macro. That has already been done when the macro is run.
To determine which registers to save, the macro can refer to the
- array 'regs_ever_live': element R is nonzero if hard register R is
+ array `regs_ever_live': element R is nonzero if hard register R is
used anywhere within the function. This implies the function
prologue should save register R, provided it is not one of the
- call-used registers. ('TARGET_ASM_FUNCTION_EPILOGUE' must likewise
- use 'regs_ever_live'.)
+ call-used registers. (`TARGET_ASM_FUNCTION_EPILOGUE' must
+ likewise use `regs_ever_live'.)
On machines that have "register windows", the function entry code
does not save on the stack the registers that are in the windows,
even if they are supposed to be preserved by function calls;
- instead it takes appropriate steps to "push" the register stack, if
- any non-call-used registers are used in the function.
+ instead it takes appropriate steps to "push" the register stack,
+ if any non-call-used registers are used in the function.
On machines where functions may or may not have frame-pointers, the
function entry code must vary accordingly; it must set up the frame
pointer if one is wanted, and not otherwise. To determine whether
a frame pointer is in wanted, the macro can refer to the variable
- 'frame_pointer_needed'. The variable's value will be 1 at run time
- in a function that needs a frame pointer. *Note Elimination::.
+ `frame_pointer_needed'. The variable's value will be 1 at run
+ time in a function that needs a frame pointer. *Note
+ Elimination::.
The function entry code is responsible for allocating any stack
space required for the function. This stack space consists of the
regions listed below. In most cases, these regions are allocated
- in the order listed, with the last listed region closest to the top
- of the stack (the lowest address if 'STACK_GROWS_DOWNWARD' is
+ in the order listed, with the last listed region closest to the
+ top of the stack (the lowest address if `STACK_GROWS_DOWNWARD' is
defined, and the highest address if it is not defined). You can
use a different order for a machine if doing so is more convenient
or required for compatibility reasons. Except in cases where
@@ -31659,56 +32070,57 @@ This section describes the macros that output function entry
HOST_WIDE_INT SIZE)
If defined, a function that outputs the assembler code for exit
from a function. The epilogue is responsible for restoring the
- saved registers and stack pointer to their values when the function
- was called, and returning control to the caller. This macro takes
- the same arguments as the macro 'TARGET_ASM_FUNCTION_PROLOGUE', and
- the registers to restore are determined from 'regs_ever_live' and
- 'CALL_USED_REGISTERS' in the same way.
+ saved registers and stack pointer to their values when the
+ function was called, and returning control to the caller. This
+ macro takes the same arguments as the macro
+ `TARGET_ASM_FUNCTION_PROLOGUE', and the registers to restore are
+ determined from `regs_ever_live' and `CALL_USED_REGISTERS' in the
+ same way.
On some machines, there is a single instruction that does all the
work of returning from the function. On these machines, give that
- instruction the name 'return' and do not define the macro
- 'TARGET_ASM_FUNCTION_EPILOGUE' at all.
+ instruction the name `return' and do not define the macro
+ `TARGET_ASM_FUNCTION_EPILOGUE' at all.
- Do not define a pattern named 'return' if you want the
- 'TARGET_ASM_FUNCTION_EPILOGUE' to be used. If you want the target
+ Do not define a pattern named `return' if you want the
+ `TARGET_ASM_FUNCTION_EPILOGUE' to be used. If you want the target
switches to control whether return instructions or epilogues are
- used, define a 'return' pattern with a validity condition that
- tests the target switches appropriately. If the 'return' pattern's
- validity condition is false, epilogues will be used.
+ used, define a `return' pattern with a validity condition that
+ tests the target switches appropriately. If the `return'
+ pattern's validity condition is false, epilogues will be used.
On machines where functions may or may not have frame-pointers, the
function exit code must vary accordingly. Sometimes the code for
these two cases is completely different. To determine whether a
frame pointer is wanted, the macro can refer to the variable
- 'frame_pointer_needed'. The variable's value will be 1 when
+ `frame_pointer_needed'. The variable's value will be 1 when
compiling a function that needs a frame pointer.
- Normally, 'TARGET_ASM_FUNCTION_PROLOGUE' and
- 'TARGET_ASM_FUNCTION_EPILOGUE' must treat leaf functions specially.
- The C variable 'current_function_is_leaf' is nonzero for such a
+ Normally, `TARGET_ASM_FUNCTION_PROLOGUE' and
+ `TARGET_ASM_FUNCTION_EPILOGUE' must treat leaf functions specially.
+ The C variable `current_function_is_leaf' is nonzero for such a
function. *Note Leaf Functions::.
On some machines, some functions pop their arguments on exit while
others leave that for the caller to do. For example, the 68020
- when given '-mrtd' pops arguments in functions that take a fixed
+ when given `-mrtd' pops arguments in functions that take a fixed
number of arguments.
- Your definition of the macro 'RETURN_POPS_ARGS' decides which
- functions pop their own arguments. 'TARGET_ASM_FUNCTION_EPILOGUE'
+ Your definition of the macro `RETURN_POPS_ARGS' decides which
+ functions pop their own arguments. `TARGET_ASM_FUNCTION_EPILOGUE'
needs to know what was decided. The number of bytes of the current
function's arguments that this function should pop is available in
- 'crtl->args.pops_args'. *Note Scalar Return::.
+ `crtl->args.pops_args'. *Note Scalar Return::.
- * A region of 'crtl->args.pretend_args_size' bytes of uninitialized
+ * A region of `crtl->args.pretend_args_size' bytes of uninitialized
space just underneath the first argument arriving on the stack.
- (This may not be at the very start of the allocated stack region if
- the calling sequence has pushed anything else since pushing the
+ (This may not be at the very start of the allocated stack region
+ if the calling sequence has pushed anything else since pushing the
stack arguments. But usually, on such machines, nothing else has
been pushed yet, because the function prologue itself does all the
- pushing.) This region is used on machines where an argument may be
- passed partly in registers and partly in memory, and, in some cases
- to support the features in '<stdarg.h>'.
+ pushing.) This region is used on machines where an argument may
+ be passed partly in registers and partly in memory, and, in some
+ cases to support the features in `<stdarg.h>'.
* An area of memory used to save certain registers used by the
function. The size of this area, which may also include space for
@@ -31723,8 +32135,8 @@ This section describes the macros that output function entry
occur in the opposite order, with the save area closer to the top
of the stack.
- * Optionally, when 'ACCUMULATE_OUTGOING_ARGS' is defined, a region of
- 'crtl->outgoing_args_size' bytes to be used for outgoing argument
+ * Optionally, when `ACCUMULATE_OUTGOING_ARGS' is defined, a region of
+ `crtl->outgoing_args_size' bytes to be used for outgoing argument
lists of the function. *Note Stack Arguments::.
-- Macro: EXIT_IGNORE_STACK
@@ -31736,23 +32148,23 @@ This section describes the macros that output function entry
Note that this macro's value is relevant only for functions for
which frame pointers are maintained. It is never safe to delete a
- final stack adjustment in a function that has no frame pointer, and
- the compiler knows this regardless of 'EXIT_IGNORE_STACK'.
+ final stack adjustment in a function that has no frame pointer,
+ and the compiler knows this regardless of `EXIT_IGNORE_STACK'.
-- Macro: EPILOGUE_USES (REGNO)
Define this macro as a C expression that is nonzero for registers
- that are used by the epilogue or the 'return' pattern. The stack
+ that are used by the epilogue or the `return' pattern. The stack
and frame pointer registers are already assumed to be used as
needed.
-- Macro: EH_USES (REGNO)
Define this macro as a C expression that is nonzero for registers
- that are used by the exception handling mechanism, and so should be
- considered live on entry to an exception edge.
+ that are used by the exception handling mechanism, and so should
+ be considered live on entry to an exception edge.
-- Target Hook: void TARGET_ASM_OUTPUT_MI_THUNK (FILE *FILE, tree
- THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT VCALL_OFFSET,
- tree FUNCTION)
+ THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT
+ VCALL_OFFSET, tree FUNCTION)
A function that outputs the assembler code for a thunk function,
used to implement C++ virtual function calls with multiple
inheritance. The thunk acts as a wrapper around a virtual
@@ -31761,45 +32173,45 @@ This section describes the macros that output function entry
First, emit code to add the integer DELTA to the location that
contains the incoming first argument. Assume that this argument
- contains a pointer, and is the one used to pass the 'this' pointer
+ contains a pointer, and is the one used to pass the `this' pointer
in C++. This is the incoming argument _before_ the function
- prologue, e.g. '%o0' on a sparc. The addition must preserve the
+ prologue, e.g. `%o0' on a sparc. The addition must preserve the
values of all other incoming arguments.
Then, if VCALL_OFFSET is nonzero, an additional adjustment should
- be made after adding 'delta'. In particular, if P is the adjusted
+ be made after adding `delta'. In particular, if P is the adjusted
pointer, the following adjustment should be made:
p += (*((ptrdiff_t **)p))[vcall_offset/sizeof(ptrdiff_t)]
After the additions, emit code to jump to FUNCTION, which is a
- 'FUNCTION_DECL'. This is a direct pure jump, not a call, and does
+ `FUNCTION_DECL'. This is a direct pure jump, not a call, and does
not touch the return address. Hence returning from FUNCTION will
- return to whoever called the current 'thunk'.
+ return to whoever called the current `thunk'.
- The effect must be as if FUNCTION had been called directly with the
- adjusted first argument. This macro is responsible for emitting
- all of the code for a thunk function;
- 'TARGET_ASM_FUNCTION_PROLOGUE' and 'TARGET_ASM_FUNCTION_EPILOGUE'
+ The effect must be as if FUNCTION had been called directly with
+ the adjusted first argument. This macro is responsible for
+ emitting all of the code for a thunk function;
+ `TARGET_ASM_FUNCTION_PROLOGUE' and `TARGET_ASM_FUNCTION_EPILOGUE'
are not invoked.
The THUNK_FNDECL is redundant. (DELTA and FUNCTION have already
been extracted from it.) It might possibly be useful on some
targets, but probably not.
- If you do not define this macro, the target-independent code in the
- C++ front end will generate a less efficient heavyweight thunk that
- calls FUNCTION instead of jumping to it. The generic approach does
- not support varargs.
+ If you do not define this macro, the target-independent code in
+ the C++ front end will generate a less efficient heavyweight thunk
+ that calls FUNCTION instead of jumping to it. The generic
+ approach does not support varargs.
-- Target Hook: bool TARGET_ASM_CAN_OUTPUT_MI_THUNK (const_tree
- THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT VCALL_OFFSET,
- const_tree FUNCTION)
- A function that returns true if TARGET_ASM_OUTPUT_MI_THUNK would be
- able to output the assembler code for the thunk function specified
- by the arguments it is passed, and false otherwise. In the latter
- case, the generic approach will be used by the C++ front end, with
- the limitations previously exposed.
+ THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT
+ VCALL_OFFSET, const_tree FUNCTION)
+ A function that returns true if TARGET_ASM_OUTPUT_MI_THUNK would
+ be able to output the assembler code for the thunk function
+ specified by the arguments it is passed, and false otherwise. In
+ the latter case, the generic approach will be used by the C++
+ front end, with the limitations previously exposed.

File: gccint.info, Node: Profiling, Next: Tail Calls, Prev: Function Entry, Up: Stack and Calling
@@ -31811,29 +32223,29 @@ These macros will help you generate code for profiling.
-- Macro: FUNCTION_PROFILER (FILE, LABELNO)
A C statement or compound statement to output to FILE some
- assembler code to call the profiling subroutine 'mcount'.
+ assembler code to call the profiling subroutine `mcount'.
- The details of how 'mcount' expects to be called are determined by
+ The details of how `mcount' expects to be called are determined by
your operating system environment, not by GCC. To figure them out,
compile a small program for profiling using the system's installed
C compiler and look at the assembler code that results.
- Older implementations of 'mcount' expect the address of a counter
+ Older implementations of `mcount' expect the address of a counter
variable to be loaded into some register. The name of this
- variable is 'LP' followed by the number LABELNO, so you would
- generate the name using 'LP%d' in a 'fprintf'.
+ variable is `LP' followed by the number LABELNO, so you would
+ generate the name using `LP%d' in a `fprintf'.
-- Macro: PROFILE_HOOK
A C statement or compound statement to output to FILE some assembly
- code to call the profiling subroutine 'mcount' even the target does
+ code to call the profiling subroutine `mcount' even the target does
not support profiling.
-- Macro: NO_PROFILE_COUNTERS
Define this macro to be an expression with a nonzero value if the
- 'mcount' subroutine on your system does not need a counter variable
+ `mcount' subroutine on your system does not need a counter variable
allocated for each function. This is true for almost all modern
implementations. If you define this macro, you must not use the
- LABELNO argument to 'FUNCTION_PROFILER'.
+ LABELNO argument to `FUNCTION_PROFILER'.
-- Macro: PROFILE_BEFORE_PROLOGUE
Define this macro if the code for function profiling should come
@@ -31841,11 +32253,12 @@ These macros will help you generate code for profiling.
after.
-- Target Hook: bool TARGET_KEEP_LEAF_WHEN_PROFILED (void)
- This target hook returns true if the target wants the leaf flag for
- the current function to stay true even if it calls mcount. This
- might make sense for targets using the leaf flag only to determine
- whether a stack frame needs to be generated or not and for which
- the call to mcount is generated before the function prologue.
+ This target hook returns true if the target wants the leaf flag
+ for the current function to stay true even if it calls mcount.
+ This might make sense for targets using the leaf flag only to
+ determine whether a stack frame needs to be generated or not and
+ for which the call to mcount is generated before the function
+ prologue.

File: gccint.info, Node: Tail Calls, Next: Stack Smashing Protection, Prev: Profiling, Up: Stack and Calling
@@ -31856,25 +32269,25 @@ File: gccint.info, Node: Tail Calls, Next: Stack Smashing Protection, Prev: P
-- Target Hook: bool TARGET_FUNCTION_OK_FOR_SIBCALL (tree DECL, tree
EXP)
True if it is OK to do sibling call optimization for the specified
- call expression EXP. DECL will be the called function, or 'NULL'
+ call expression EXP. DECL will be the called function, or `NULL'
if this is an indirect call.
It is not uncommon for limitations of calling conventions to
prevent tail calls to functions outside the current unit of
translation, or during PIC compilation. The hook is used to
- enforce these restrictions, as the 'sibcall' md pattern can not
- fail, or fall over to a "normal" call. The criteria for successful
- sibling call optimization may vary greatly between different
- architectures.
+ enforce these restrictions, as the `sibcall' md pattern can not
+ fail, or fall over to a "normal" call. The criteria for
+ successful sibling call optimization may vary greatly between
+ different architectures.
-- Target Hook: void TARGET_EXTRA_LIVE_ON_ENTRY (bitmap REGS)
Add any hard registers to REGS that are live on entry to the
function. This hook only needs to be defined to provide registers
that cannot be found by examination of FUNCTION_ARG_REGNO_P, the
callee saved registers, STATIC_CHAIN_INCOMING_REGNUM,
- STATIC_CHAIN_REGNUM, TARGET_STRUCT_VALUE_RTX, FRAME_POINTER_REGNUM,
- EH_USES, FRAME_POINTER_REGNUM, ARG_POINTER_REGNUM, and the
- PIC_OFFSET_TABLE_REGNUM.
+ STATIC_CHAIN_REGNUM, TARGET_STRUCT_VALUE_RTX,
+ FRAME_POINTER_REGNUM, EH_USES, FRAME_POINTER_REGNUM,
+ ARG_POINTER_REGNUM, and the PIC_OFFSET_TABLE_REGNUM.
-- Target Hook: void TARGET_SET_UP_BY_PROLOGUE (struct
hard_reg_set_container *)
@@ -31895,23 +32308,23 @@ File: gccint.info, Node: Stack Smashing Protection, Next: Miscellaneous Regist
---------------------------------
-- Target Hook: tree TARGET_STACK_PROTECT_GUARD (void)
- This hook returns a 'DECL' node for the external variable to use
+ This hook returns a `DECL' node for the external variable to use
for the stack protection guard. This variable is initialized by
the runtime to some random value and is used to initialize the
guard value that is placed at the top of the local stack frame.
- The type of this variable must be 'ptr_type_node'.
+ The type of this variable must be `ptr_type_node'.
The default version of this hook creates a variable called
- '__stack_chk_guard', which is normally defined in 'libgcc2.c'.
+ `__stack_chk_guard', which is normally defined in `libgcc2.c'.
-- Target Hook: tree TARGET_STACK_PROTECT_FAIL (void)
- This hook returns a 'CALL_EXPR' that alerts the runtime that the
+ This hook returns a `CALL_EXPR' that alerts the runtime that the
stack protect guard variable has been modified. This expression
- should involve a call to a 'noreturn' function.
+ should involve a call to a `noreturn' function.
The default version of this hook invokes a function called
- '__stack_chk_fail', taking no arguments. This function is normally
- defined in 'libgcc2.c'.
+ `__stack_chk_fail', taking no arguments. This function is
+ normally defined in `libgcc2.c'.
-- Common Target Hook: bool TARGET_SUPPORTS_SPLIT_STACK (bool REPORT,
struct gcc_options *OPTS)
@@ -31932,10 +32345,10 @@ File: gccint.info, Node: Miscellaneous Register Hooks, Prev: Stack Smashing Pr
Set to true if each call that binds to a local definition
explicitly clobbers or sets all non-fixed registers modified by
performing the call. That is, by the call pattern itself, or by
- code that might be inserted by the linker (e.g. stubs, veneers,
+ code that might be inserted by the linker (e.g. stubs, veneers,
branch islands), but not including those modifiable by the callee.
The affected registers may be mentioned explicitly in the call
- pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE. The
+ pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE. The
default version of this hook is set to false. The purpose of this
hook is to enable the fipa-ra optimization.
@@ -31945,161 +32358,164 @@ File: gccint.info, Node: Varargs, Next: Trampolines, Prev: Stack and Calling,
17.10 Implementing the Varargs Macros
=====================================
-GCC comes with an implementation of '<varargs.h>' and '<stdarg.h>' that
-work without change on machines that pass arguments on the stack. Other
-machines require their own implementations of varargs, and the two
-machine independent header files must have conditionals to include it.
+GCC comes with an implementation of `<varargs.h>' and `<stdarg.h>' that
+work without change on machines that pass arguments on the stack.
+Other machines require their own implementations of varargs, and the
+two machine independent header files must have conditionals to include
+it.
- ISO '<stdarg.h>' differs from traditional '<varargs.h>' mainly in the
-calling convention for 'va_start'. The traditional implementation takes
-just one argument, which is the variable in which to store the argument
-pointer. The ISO implementation of 'va_start' takes an additional
-second argument. The user is supposed to write the last named argument
-of the function here.
+ ISO `<stdarg.h>' differs from traditional `<varargs.h>' mainly in the
+calling convention for `va_start'. The traditional implementation
+takes just one argument, which is the variable in which to store the
+argument pointer. The ISO implementation of `va_start' takes an
+additional second argument. The user is supposed to write the last
+named argument of the function here.
- However, 'va_start' should not use this argument. The way to find the
+ However, `va_start' should not use this argument. The way to find the
end of the named arguments is with the built-in functions described
below.
-- Macro: __builtin_saveregs ()
- Use this built-in function to save the argument registers in memory
- so that the varargs mechanism can access them. Both ISO and
- traditional versions of 'va_start' must use '__builtin_saveregs',
- unless you use 'TARGET_SETUP_INCOMING_VARARGS' (see below) instead.
-
- On some machines, '__builtin_saveregs' is open-coded under the
- control of the target hook 'TARGET_EXPAND_BUILTIN_SAVEREGS'. On
+ Use this built-in function to save the argument registers in
+ memory so that the varargs mechanism can access them. Both ISO
+ and traditional versions of `va_start' must use
+ `__builtin_saveregs', unless you use
+ `TARGET_SETUP_INCOMING_VARARGS' (see below) instead.
+
+ On some machines, `__builtin_saveregs' is open-coded under the
+ control of the target hook `TARGET_EXPAND_BUILTIN_SAVEREGS'. On
other machines, it calls a routine written in assembler language,
- found in 'libgcc2.c'.
+ found in `libgcc2.c'.
- Code generated for the call to '__builtin_saveregs' appears at the
+ Code generated for the call to `__builtin_saveregs' appears at the
beginning of the function, as opposed to where the call to
- '__builtin_saveregs' is written, regardless of what the code is.
+ `__builtin_saveregs' is written, regardless of what the code is.
This is because the registers must be saved before the function
starts to use them for its own purposes.
-- Macro: __builtin_next_arg (LASTARG)
This builtin returns the address of the first anonymous stack
- argument, as type 'void *'. If 'ARGS_GROW_DOWNWARD', it returns
+ argument, as type `void *'. If `ARGS_GROW_DOWNWARD', it returns
the address of the location above the first anonymous stack
- argument. Use it in 'va_start' to initialize the pointer for
- fetching arguments from the stack. Also use it in 'va_start' to
+ argument. Use it in `va_start' to initialize the pointer for
+ fetching arguments from the stack. Also use it in `va_start' to
verify that the second parameter LASTARG is the last named argument
of the current function.
-- Macro: __builtin_classify_type (OBJECT)
Since each machine has its own conventions for which data types are
- passed in which kind of register, your implementation of 'va_arg'
+ passed in which kind of register, your implementation of `va_arg'
has to embody these conventions. The easiest way to categorize the
- specified data type is to use '__builtin_classify_type' together
- with 'sizeof' and '__alignof__'.
+ specified data type is to use `__builtin_classify_type' together
+ with `sizeof' and `__alignof__'.
- '__builtin_classify_type' ignores the value of OBJECT, considering
+ `__builtin_classify_type' ignores the value of OBJECT, considering
only its data type. It returns an integer describing what kind of
type that is--integer, floating, pointer, structure, and so on.
- The file 'typeclass.h' defines an enumeration that you can use to
- interpret the values of '__builtin_classify_type'.
+ The file `typeclass.h' defines an enumeration that you can use to
+ interpret the values of `__builtin_classify_type'.
These machine description macros help implement varargs:
-- Target Hook: rtx TARGET_EXPAND_BUILTIN_SAVEREGS (void)
- If defined, this hook produces the machine-specific code for a call
- to '__builtin_saveregs'. This code will be moved to the very
+ If defined, this hook produces the machine-specific code for a
+ call to `__builtin_saveregs'. This code will be moved to the very
beginning of the function, before any parameter access are made.
The return value of this function should be an RTX that contains
- the value to use as the return of '__builtin_saveregs'.
+ the value to use as the return of `__builtin_saveregs'.
-- Target Hook: void TARGET_SETUP_INCOMING_VARARGS (cumulative_args_t
ARGS_SO_FAR, machine_mode MODE, tree TYPE, int
*PRETEND_ARGS_SIZE, int SECOND_TIME)
This target hook offers an alternative to using
- '__builtin_saveregs' and defining the hook
- 'TARGET_EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous
+ `__builtin_saveregs' and defining the hook
+ `TARGET_EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous
register arguments into the stack so that all the arguments appear
- to have been passed consecutively on the stack. Once this is done,
- you can use the standard implementation of varargs that works for
- machines that pass all their arguments on the stack.
+ to have been passed consecutively on the stack. Once this is
+ done, you can use the standard implementation of varargs that
+ works for machines that pass all their arguments on the stack.
- The argument ARGS_SO_FAR points to the 'CUMULATIVE_ARGS' data
- structure, containing the values that are obtained after processing
- the named arguments. The arguments MODE and TYPE describe the last
- named argument--its machine mode and its data type as a tree node.
+ The argument ARGS_SO_FAR points to the `CUMULATIVE_ARGS' data
+ structure, containing the values that are obtained after
+ processing the named arguments. The arguments MODE and TYPE
+ describe the last named argument--its machine mode and its data
+ type as a tree node.
The target hook should do two things: first, push onto the stack
all the argument registers _not_ used for the named arguments, and
second, store the size of the data thus pushed into the
- 'int'-valued variable pointed to by PRETEND_ARGS_SIZE. The value
+ `int'-valued variable pointed to by PRETEND_ARGS_SIZE. The value
that you store here will serve as additional offset for setting up
the stack frame.
Because you must generate code to push the anonymous arguments at
compile time without knowing their data types,
- 'TARGET_SETUP_INCOMING_VARARGS' is only useful on machines that
+ `TARGET_SETUP_INCOMING_VARARGS' is only useful on machines that
have just a single category of argument register and use it
uniformly for all data types.
- If the argument SECOND_TIME is nonzero, it means that the arguments
- of the function are being analyzed for the second time. This
- happens for an inline function, which is not actually compiled
- until the end of the source file. The hook
- 'TARGET_SETUP_INCOMING_VARARGS' should not generate any
+ If the argument SECOND_TIME is nonzero, it means that the
+ arguments of the function are being analyzed for the second time.
+ This happens for an inline function, which is not actually
+ compiled until the end of the source file. The hook
+ `TARGET_SETUP_INCOMING_VARARGS' should not generate any
instructions in this case.
-- Target Hook: bool TARGET_STRICT_ARGUMENT_NAMING (cumulative_args_t
CA)
- Define this hook to return 'true' if the location where a function
+ Define this hook to return `true' if the location where a function
argument is passed depends on whether or not it is a named
argument.
- This hook controls how the NAMED argument to 'TARGET_FUNCTION_ARG'
+ This hook controls how the NAMED argument to `TARGET_FUNCTION_ARG'
is set for varargs and stdarg functions. If this hook returns
- 'true', the NAMED argument is always true for named arguments, and
- false for unnamed arguments. If it returns 'false', but
- 'TARGET_PRETEND_OUTGOING_VARARGS_NAMED' returns 'true', then all
+ `true', the NAMED argument is always true for named arguments, and
+ false for unnamed arguments. If it returns `false', but
+ `TARGET_PRETEND_OUTGOING_VARARGS_NAMED' returns `true', then all
arguments are treated as named. Otherwise, all named arguments
except the last are treated as named.
- You need not define this hook if it always returns 'false'.
+ You need not define this hook if it always returns `false'.
-- Target Hook: void TARGET_CALL_ARGS (rtx, TREE)
While generating RTL for a function call, this target hook is
invoked once for each argument passed to the function, either a
- register returned by 'TARGET_FUNCTION_ARG' or a memory location.
+ register returned by `TARGET_FUNCTION_ARG' or a memory location.
It is called just before the point where argument registers are
stored. The type of the function to be called is also passed as
- the second argument; it is 'NULL_TREE' for libcalls. The
- 'TARGET_END_CALL_ARGS' hook is invoked just after the code to copy
- the return reg has been emitted. This functionality can be used to
- perform special setup of call argument registers if a target needs
- it. For functions without arguments, the hook is called once with
- 'pc_rtx' passed instead of an argument register. Most ports do not
- need to implement anything for this hook.
+ the second argument; it is `NULL_TREE' for libcalls. The
+ `TARGET_END_CALL_ARGS' hook is invoked just after the code to copy
+ the return reg has been emitted. This functionality can be used
+ to perform special setup of call argument registers if a target
+ needs it. For functions without arguments, the hook is called
+ once with `pc_rtx' passed instead of an argument register. Most
+ ports do not need to implement anything for this hook.
-- Target Hook: void TARGET_END_CALL_ARGS (void)
This target hook is invoked while generating RTL for a function
call, just after the point where the return reg is copied into a
- pseudo. It signals that all the call argument and return registers
- for the just emitted call are now no longer in use. Most ports do
- not need to implement anything for this hook.
+ pseudo. It signals that all the call argument and return
+ registers for the just emitted call are now no longer in use.
+ Most ports do not need to implement anything for this hook.
-- Target Hook: bool TARGET_PRETEND_OUTGOING_VARARGS_NAMED
(cumulative_args_t CA)
If you need to conditionally change ABIs so that one works with
- 'TARGET_SETUP_INCOMING_VARARGS', but the other works like neither
- 'TARGET_SETUP_INCOMING_VARARGS' nor 'TARGET_STRICT_ARGUMENT_NAMING'
- was defined, then define this hook to return 'true' if
- 'TARGET_SETUP_INCOMING_VARARGS' is used, 'false' otherwise.
- Otherwise, you should not define this hook.
+ `TARGET_SETUP_INCOMING_VARARGS', but the other works like neither
+ `TARGET_SETUP_INCOMING_VARARGS' nor
+ `TARGET_STRICT_ARGUMENT_NAMING' was defined, then define this hook
+ to return `true' if `TARGET_SETUP_INCOMING_VARARGS' is used,
+ `false' otherwise. Otherwise, you should not define this hook.
-- Target Hook: rtx TARGET_LOAD_BOUNDS_FOR_ARG (rtx SLOT, rtx ARG, rtx
SLOT_NO)
- This hook is used by expand pass to emit insn to load bounds of ARG
- passed in SLOT. Expand pass uses this hook in case bounds of ARG
- are not passed in register. If SLOT is a memory, then bounds are
- loaded as for regular pointer loaded from memory. If SLOT is not a
- memory then SLOT_NO is an integer constant holding number of the
- target dependent special slot which should be used to obtain
+ This hook is used by expand pass to emit insn to load bounds of
+ ARG passed in SLOT. Expand pass uses this hook in case bounds of
+ ARG are not passed in register. If SLOT is a memory, then bounds
+ are loaded as for regular pointer loaded from memory. If SLOT is
+ not a memory then SLOT_NO is an integer constant holding number of
+ the target dependent special slot which should be used to obtain
bounds. Hook returns RTX holding loaded bounds.
-- Target Hook: void TARGET_STORE_BOUNDS_FOR_ARG (rtx ARG, rtx SLOT,
@@ -32107,14 +32523,15 @@ below.
This hook is used by expand pass to emit insns to store BOUNDS of
ARG passed in SLOT. Expand pass uses this hook in case BOUNDS of
ARG are not passed in register. If SLOT is a memory, then BOUNDS
- are stored as for regular pointer stored in memory. If SLOT is not
- a memory then SLOT_NO is an integer constant holding number of the
- target dependent special slot which should be used to store BOUNDS.
+ are stored as for regular pointer stored in memory. If SLOT is
+ not a memory then SLOT_NO is an integer constant holding number of
+ the target dependent special slot which should be used to store
+ BOUNDS.
-- Target Hook: rtx TARGET_LOAD_RETURNED_BOUNDS (rtx SLOT)
This hook is used by expand pass to emit insn to load bounds
- returned by function call in SLOT. Hook returns RTX holding loaded
- bounds.
+ returned by function call in SLOT. Hook returns RTX holding
+ loaded bounds.
-- Target Hook: void TARGET_STORE_RETURNED_BOUNDS (rtx SLOT, rtx
BOUNDS)
@@ -32125,14 +32542,14 @@ below.
RET_TYPE, const_tree FN_DECL_OR_TYPE, bool OUTGOING)
Define this to return an RTX representing the place where a
function returns bounds for returned pointers. Arguments meaning
- is similar to 'TARGET_FUNCTION_VALUE'.
+ is similar to `TARGET_FUNCTION_VALUE'.
-- Target Hook: void TARGET_SETUP_INCOMING_VARARG_BOUNDS
(cumulative_args_t ARGS_SO_FAR, enum machine_mode MODE, tree
TYPE, int *PRETEND_ARGS_SIZE, int SECOND_TIME)
- Use it to store bounds for anonymous register arguments stored into
- the stack. Arguments meaning is similar to
- 'TARGET_SETUP_INCOMING_VARARGS'.
+ Use it to store bounds for anonymous register arguments stored
+ into the stack. Arguments meaning is similar to
+ `TARGET_SETUP_INCOMING_VARARGS'.

File: gccint.info, Node: Trampolines, Next: Library Calls, Prev: Varargs, Up: Target Macros
@@ -32140,10 +32557,10 @@ File: gccint.info, Node: Trampolines, Next: Library Calls, Prev: Varargs, Up
17.11 Trampolines for Nested Functions
======================================
-A "trampoline" is a small piece of code that is created at run time when
-the address of a nested function is taken. It normally resides on the
-stack, in the stack frame of the containing function. These macros tell
-GCC how to generate code to allocate and initialize a trampoline.
+A "trampoline" is a small piece of code that is created at run time
+when the address of a nested function is taken. It normally resides on
+the stack, in the stack frame of the containing function. These macros
+tell GCC how to generate code to allocate and initialize a trampoline.
The instructions in the trampoline must do two things: load a constant
address into the static chain register, and jump to the real address of
@@ -32163,9 +32580,9 @@ may be necessary to take out pieces of the address and store them
separately.
-- Target Hook: void TARGET_ASM_TRAMPOLINE_TEMPLATE (FILE *F)
- This hook is called by 'assemble_trampoline_template' to output, on
- the stream F, assembler code for a block of data that contains the
- constant parts of a trampoline. This code should not include a
+ This hook is called by `assemble_trampoline_template' to output,
+ on the stream F, assembler code for a block of data that contains
+ the constant parts of a trampoline. This code should not include a
label--the label is taken care of automatically.
If you do not define this hook, it means no template is needed for
@@ -32176,7 +32593,7 @@ separately.
-- Macro: TRAMPOLINE_SECTION
Return the section into which the trampoline template is to be
placed (*note Sections::). The default value is
- 'readonly_data_section'.
+ `readonly_data_section'.
-- Macro: TRAMPOLINE_SIZE
A C expression for the size in bytes of the trampoline, as an
@@ -32185,23 +32602,23 @@ separately.
-- Macro: TRAMPOLINE_ALIGNMENT
Alignment required for trampolines, in bits.
- If you don't define this macro, the value of 'FUNCTION_ALIGNMENT'
+ If you don't define this macro, the value of `FUNCTION_ALIGNMENT'
is used for aligning trampolines.
-- Target Hook: void TARGET_TRAMPOLINE_INIT (rtx M_TRAMP, tree FNDECL,
rtx STATIC_CHAIN)
This hook is called to initialize a trampoline. M_TRAMP is an RTX
for the memory block for the trampoline; FNDECL is the
- 'FUNCTION_DECL' for the nested function; STATIC_CHAIN is an RTX for
- the static chain value that should be passed to the function when
- it is called.
+ `FUNCTION_DECL' for the nested function; STATIC_CHAIN is an RTX
+ for the static chain value that should be passed to the function
+ when it is called.
- If the target defines 'TARGET_ASM_TRAMPOLINE_TEMPLATE', then the
+ If the target defines `TARGET_ASM_TRAMPOLINE_TEMPLATE', then the
first thing this hook should do is emit a block move into M_TRAMP
- from the memory block returned by 'assemble_trampoline_template'.
+ from the memory block returned by `assemble_trampoline_template'.
Note that the block move need only cover the constant parts of the
trampoline. If the target isolates the variable parts of the
- trampoline to the end, not all 'TRAMPOLINE_SIZE' bytes need be
+ trampoline to the end, not all `TRAMPOLINE_SIZE' bytes need be
copied.
If the target requires any other actions, such as flushing caches
@@ -32211,17 +32628,17 @@ separately.
-- Target Hook: rtx TARGET_TRAMPOLINE_ADJUST_ADDRESS (rtx ADDR)
This hook should perform any machine-specific adjustment in the
address of the trampoline. Its argument contains the address of
- the memory block that was passed to 'TARGET_TRAMPOLINE_INIT'. In
- case the address to be used for a function call should be different
- from the address at which the template was stored, the different
- address should be returned; otherwise ADDR should be returned
- unchanged. If this hook is not defined, ADDR will be used for
- function calls.
+ the memory block that was passed to `TARGET_TRAMPOLINE_INIT'. In
+ case the address to be used for a function call should be
+ different from the address at which the template was stored, the
+ different address should be returned; otherwise ADDR should be
+ returned unchanged. If this hook is not defined, ADDR will be
+ used for function calls.
Implementing trampolines is difficult on many machines because they
have separate instruction and data caches. Writing into a stack
-location fails to clear the memory in the instruction cache, so when the
-program jumps to that location, it executes the old contents.
+location fails to clear the memory in the instruction cache, so when
+the program jumps to that location, it executes the old contents.
Here are two possible solutions. One is to clear the relevant parts of
the instruction cache whenever a trampoline is set up. The other is to
@@ -32235,27 +32652,27 @@ the following macro.
-- Macro: CLEAR_INSN_CACHE (BEG, END)
If defined, expands to a C expression clearing the _instruction
cache_ in the specified interval. The definition of this macro
- would typically be a series of 'asm' statements. Both BEG and END
+ would typically be a series of `asm' statements. Both BEG and END
are both pointer expressions.
To use a standard subroutine, define the following macro. In addition,
you must make sure that the instructions in a trampoline fill an entire
cache line with identical instructions, or else ensure that the
beginning of the trampoline code is always aligned at the same point in
-its cache line. Look in 'm68k.h' as a guide.
+its cache line. Look in `m68k.h' as a guide.
-- Macro: TRANSFER_FROM_TRAMPOLINE
Define this macro if trampolines need a special subroutine to do
- their work. The macro should expand to a series of 'asm'
+ their work. The macro should expand to a series of `asm'
statements which will be compiled with GCC. They go in a library
- function named '__transfer_from_trampoline'.
+ function named `__transfer_from_trampoline'.
If you need to avoid executing the ordinary prologue code of a
compiled C function when you jump to the subroutine, you can do so
by placing a special label of your own in the assembler code. Use
- one 'asm' statement to generate an assembler label, and another to
- make the label global. Then trampolines can use that label to jump
- directly to your special assembler code.
+ one `asm' statement to generate an assembler label, and another to
+ make the label global. Then trampolines can use that label to
+ jump directly to your special assembler code.

File: gccint.info, Node: Library Calls, Next: Addressing Modes, Prev: Trampolines, Up: Target Macros
@@ -32267,30 +32684,30 @@ Here is an explanation of implicit calls to library routines.
-- Macro: DECLARE_LIBRARY_RENAMES
This macro, if defined, should expand to a piece of C code that
- will get expanded when compiling functions for libgcc.a. It can be
- used to provide alternate names for GCC's internal library
+ will get expanded when compiling functions for libgcc.a. It can
+ be used to provide alternate names for GCC's internal library
functions if there are ABI-mandated names that the compiler should
provide.
-- Target Hook: void TARGET_INIT_LIBFUNCS (void)
This hook should declare additional library routines or rename
- existing ones, using the functions 'set_optab_libfunc' and
- 'init_one_libfunc' defined in 'optabs.c'. 'init_optabs' calls this
- macro after initializing all the normal library routines.
+ existing ones, using the functions `set_optab_libfunc' and
+ `init_one_libfunc' defined in `optabs.c'. `init_optabs' calls
+ this macro after initializing all the normal library routines.
- The default is to do nothing. Most ports don't need to define this
- hook.
+ The default is to do nothing. Most ports don't need to define
+ this hook.
-- Target Hook: bool TARGET_LIBFUNC_GNU_PREFIX
If false (the default), internal library routines start with two
- underscores. If set to true, these routines start with '__gnu_'
- instead. E.g., '__muldi3' changes to '__gnu_muldi3'. This
- currently only affects functions defined in 'libgcc2.c'. If this
- is set to true, the 'tm.h' file must also '#define
+ underscores. If set to true, these routines start with `__gnu_'
+ instead. E.g., `__muldi3' changes to `__gnu_muldi3'. This
+ currently only affects functions defined in `libgcc2.c'. If this
+ is set to true, the `tm.h' file must also `#define
LIBGCC2_GNU_PREFIX'.
-- Macro: FLOAT_LIB_COMPARE_RETURNS_BOOL (MODE, COMPARISON)
- This macro should return 'true' if the library routine that
+ This macro should return `true' if the library routine that
implements the floating point comparison operator COMPARISON in
mode MODE will return a boolean, and FALSE if it will return a
tristate.
@@ -32300,13 +32717,13 @@ Here is an explanation of implicit calls to library routines.
ports don't need to define this macro.
-- Macro: TARGET_LIB_INT_CMP_BIASED
- This macro should evaluate to 'true' if the integer comparison
- functions (like '__cmpdi2') return 0 to indicate that the first
+ This macro should evaluate to `true' if the integer comparison
+ functions (like `__cmpdi2') return 0 to indicate that the first
operand is smaller than the second, 1 to indicate that they are
- equal, and 2 to indicate that the first operand is greater than the
- second. If this macro evaluates to 'false' the comparison
+ equal, and 2 to indicate that the first operand is greater than
+ the second. If this macro evaluates to `false' the comparison
functions return -1, 0, and 1 instead of 0, 1, and 2. If the
- target uses the routines in 'libgcc.a', you do not need to define
+ target uses the routines in `libgcc.a', you do not need to define
this macro.
-- Macro: TARGET_HAS_NO_HW_DIVIDE
@@ -32317,21 +32734,21 @@ Here is an explanation of implicit calls to library routines.
algorithm which make use of a 64-bit by 32-bit divide primitive.
-- Macro: TARGET_EDOM
- The value of 'EDOM' on the target machine, as a C integer constant
+ The value of `EDOM' on the target machine, as a C integer constant
expression. If you don't define this macro, GCC does not attempt
- to deposit the value of 'EDOM' into 'errno' directly. Look in
- '/usr/include/errno.h' to find the value of 'EDOM' on your system.
+ to deposit the value of `EDOM' into `errno' directly. Look in
+ `/usr/include/errno.h' to find the value of `EDOM' on your system.
- If you do not define 'TARGET_EDOM', then compiled code reports
- domain errors by calling the library function and letting it report
- the error. If mathematical functions on your system use 'matherr'
- when there is an error, then you should leave 'TARGET_EDOM'
- undefined so that 'matherr' is used normally.
+ If you do not define `TARGET_EDOM', then compiled code reports
+ domain errors by calling the library function and letting it
+ report the error. If mathematical functions on your system use
+ `matherr' when there is an error, then you should leave
+ `TARGET_EDOM' undefined so that `matherr' is used normally.
-- Macro: GEN_ERRNO_RTX
Define this macro as a C expression to create an rtl expression
- that refers to the global "variable" 'errno'. (On certain systems,
- 'errno' may not actually be a variable.) If you don't define this
+ that refers to the global "variable" `errno'. (On certain systems,
+ `errno' may not actually be a variable.) If you don't define this
macro, a reasonable default is used.
-- Target Hook: bool TARGET_LIBC_HAS_FUNCTION (enum function_class
@@ -32343,9 +32760,9 @@ Here is an explanation of implicit calls to library routines.
Set this macro to 1 to use the "NeXT" Objective-C message sending
conventions by default. This calling convention involves passing
the object, the selector and the method arguments all at once to
- the method-lookup library function. This is the usual setting when
- targeting Darwin/Mac OS X systems, which have the NeXT runtime
- installed.
+ the method-lookup library function. This is the usual setting
+ when targeting Darwin/Mac OS X systems, which have the NeXT
+ runtime installed.
If the macro is set to 0, the "GNU" Objective-C message sending
convention will be used by default. This convention passes just
@@ -32386,22 +32803,22 @@ This is about addressing modes.
-- Macro: CONSTANT_ADDRESS_P (X)
A C expression that is 1 if the RTX X is a constant which is a
valid address. On most machines the default definition of
- '(CONSTANT_P (X) && GET_CODE (X) != CONST_DOUBLE)' is acceptable,
+ `(CONSTANT_P (X) && GET_CODE (X) != CONST_DOUBLE)' is acceptable,
but a few machines are more restrictive as to which constant
addresses are supported.
-- Macro: CONSTANT_P (X)
- 'CONSTANT_P', which is defined by target-independent code, accepts
+ `CONSTANT_P', which is defined by target-independent code, accepts
integer-values expressions whose values are not explicitly known,
- such as 'symbol_ref', 'label_ref', and 'high' expressions and
- 'const' arithmetic expressions, in addition to 'const_int' and
- 'const_double' expressions.
+ such as `symbol_ref', `label_ref', and `high' expressions and
+ `const' arithmetic expressions, in addition to `const_int' and
+ `const_double' expressions.
-- Macro: MAX_REGS_PER_ADDRESS
A number, the maximum number of registers that can appear in a
- valid memory address. Note that it is up to you to specify a value
- equal to the maximum number that 'TARGET_LEGITIMATE_ADDRESS_P'
- would ever accept.
+ valid memory address. Note that it is up to you to specify a
+ value equal to the maximum number that
+ `TARGET_LEGITIMATE_ADDRESS_P' would ever accept.
-- Target Hook: bool TARGET_LEGITIMATE_ADDRESS_P (machine_mode MODE,
rtx X, bool STRICT)
@@ -32415,47 +32832,48 @@ This is about addressing modes.
The strict variant is used in the reload pass. It must be defined
so that any pseudo-register that has not been allocated a hard
register is considered a memory reference. This is because in
- contexts where some kind of register is required, a pseudo-register
- with no hard register must be rejected. For non-hard registers,
- the strict variant should look up the 'reg_renumber' array; it
- should then proceed using the hard register number in the array, or
- treat the pseudo as a memory reference if the array holds '-1'.
-
- The non-strict variant is used in other passes. It must be defined
- to accept all pseudo-registers in every context where some kind of
- register is required.
-
- Normally, constant addresses which are the sum of a 'symbol_ref'
- and an integer are stored inside a 'const' RTX to mark them as
+ contexts where some kind of register is required, a
+ pseudo-register with no hard register must be rejected. For
+ non-hard registers, the strict variant should look up the
+ `reg_renumber' array; it should then proceed using the hard
+ register number in the array, or treat the pseudo as a memory
+ reference if the array holds `-1'.
+
+ The non-strict variant is used in other passes. It must be
+ defined to accept all pseudo-registers in every context where some
+ kind of register is required.
+
+ Normally, constant addresses which are the sum of a `symbol_ref'
+ and an integer are stored inside a `const' RTX to mark them as
constant. Therefore, there is no need to recognize such sums
specifically as legitimate addresses. Normally you would simply
- recognize any 'const' as legitimate.
+ recognize any `const' as legitimate.
- Usually 'PRINT_OPERAND_ADDRESS' is not prepared to handle constant
- sums that are not marked with 'const'. It assumes that a naked
- 'plus' indicates indexing. If so, then you _must_ reject such
- naked constant sums as illegitimate addresses, so that none of them
- will be given to 'PRINT_OPERAND_ADDRESS'.
+ Usually `PRINT_OPERAND_ADDRESS' is not prepared to handle constant
+ sums that are not marked with `const'. It assumes that a naked
+ `plus' indicates indexing. If so, then you _must_ reject such
+ naked constant sums as illegitimate addresses, so that none of
+ them will be given to `PRINT_OPERAND_ADDRESS'.
On some machines, whether a symbolic address is legitimate depends
on the section that the address refers to. On these machines,
- define the target hook 'TARGET_ENCODE_SECTION_INFO' to store the
- information into the 'symbol_ref', and then check for it here.
- When you see a 'const', you will have to look inside it to find the
- 'symbol_ref' in order to determine the section. *Note Assembler
+ define the target hook `TARGET_ENCODE_SECTION_INFO' to store the
+ information into the `symbol_ref', and then check for it here.
+ When you see a `const', you will have to look inside it to find the
+ `symbol_ref' in order to determine the section. *Note Assembler
Format::.
Some ports are still using a deprecated legacy substitute for this
- hook, the 'GO_IF_LEGITIMATE_ADDRESS' macro. This macro has this
+ hook, the `GO_IF_LEGITIMATE_ADDRESS' macro. This macro has this
syntax:
#define GO_IF_LEGITIMATE_ADDRESS (MODE, X, LABEL)
- and should 'goto LABEL' if the address X is a valid address on the
+ and should `goto LABEL' if the address X is a valid address on the
target machine for a memory operand of mode MODE.
Compiler source files that want to use the strict variant of this
- macro define the macro 'REG_OK_STRICT'. You should use an '#ifdef
+ macro define the macro `REG_OK_STRICT'. You should use an `#ifdef
REG_OK_STRICT' conditional to define the strict variant in that
case and the non-strict variant otherwise.
@@ -32463,20 +32881,20 @@ This is about addressing modes.
files that are recompiled when changes are made.
-- Macro: TARGET_MEM_CONSTRAINT
- A single character to be used instead of the default ''m''
+ A single character to be used instead of the default `'m''
character for general memory addresses. This defines the
constraint letter which matches the memory addresses accepted by
- 'TARGET_LEGITIMATE_ADDRESS_P'. Define this macro if you want to
+ `TARGET_LEGITIMATE_ADDRESS_P'. Define this macro if you want to
support new address formats in your back end without changing the
- semantics of the ''m'' constraint. This is necessary in order to
+ semantics of the `'m'' constraint. This is necessary in order to
preserve functionality of inline assembly constructs using the
- ''m'' constraint.
+ `'m'' constraint.
-- Macro: FIND_BASE_TERM (X)
A C expression to determine the base term of address X, or to
- provide a simplified version of X from which 'alias.c' can easily
+ provide a simplified version of X from which `alias.c' can easily
find the base term. This macro is used in only two places:
- 'find_base_value' and 'find_base_term' in 'alias.c'.
+ `find_base_value' and `find_base_term' in `alias.c'.
It is always safe for this macro to not be defined. It exists so
that alias analysis can understand machine-dependent addresses.
@@ -32489,74 +32907,74 @@ This is about addressing modes.
This hook is given an invalid memory address X for an operand of
mode MODE and should try to return a valid memory address.
- X will always be the result of a call to 'break_out_memory_refs',
+ X will always be the result of a call to `break_out_memory_refs',
and OLDX will be the operand that was given to that function to
produce X.
- The code of the hook should not alter the substructure of X. If it
- transforms X into a more legitimate form, it should return the new
- X.
+ The code of the hook should not alter the substructure of X. If
+ it transforms X into a more legitimate form, it should return the
+ new X.
It is not necessary for this hook to come up with a legitimate
- address, with the exception of native TLS addresses (*note Emulated
- TLS::). The compiler has standard ways of doing so in all cases.
- In fact, if the target supports only emulated TLS, it is safe to
- omit this hook or make it return X if it cannot find a valid way to
- legitimize the address. But often a machine-dependent strategy can
- generate better code.
+ address, with the exception of native TLS addresses (*note
+ Emulated TLS::). The compiler has standard ways of doing so in
+ all cases. In fact, if the target supports only emulated TLS, it
+ is safe to omit this hook or make it return X if it cannot find a
+ valid way to legitimize the address. But often a machine-dependent
+ strategy can generate better code.
-- Macro: LEGITIMIZE_RELOAD_ADDRESS (X, MODE, OPNUM, TYPE, IND_LEVELS,
WIN)
A C compound statement that attempts to replace X, which is an
address that needs reloading, with a valid memory address for an
- operand of mode MODE. WIN will be a C statement label elsewhere in
- the code. It is not necessary to define this macro, but it might
- be useful for performance reasons.
+ operand of mode MODE. WIN will be a C statement label elsewhere
+ in the code. It is not necessary to define this macro, but it
+ might be useful for performance reasons.
For example, on the i386, it is sometimes possible to use a single
reload register instead of two by reloading a sum of two pseudo
registers into a register. On the other hand, for number of RISC
processors offsets are limited so that often an intermediate
- address needs to be generated in order to address a stack slot. By
- defining 'LEGITIMIZE_RELOAD_ADDRESS' appropriately, the
+ address needs to be generated in order to address a stack slot.
+ By defining `LEGITIMIZE_RELOAD_ADDRESS' appropriately, the
intermediate addresses generated for adjacent some stack slots can
be made identical, and thus be shared.
- _Note_: This macro should be used with caution. It is necessary to
- know something of how reload works in order to effectively use
- this, and it is quite easy to produce macros that build in too much
- knowledge of reload internals.
+ _Note_: This macro should be used with caution. It is necessary
+ to know something of how reload works in order to effectively use
+ this, and it is quite easy to produce macros that build in too
+ much knowledge of reload internals.
_Note_: This macro must be able to reload an address created by a
previous invocation of this macro. If it fails to handle such
addresses then the compiler may generate incorrect code or abort.
- The macro definition should use 'push_reload' to indicate parts
+ The macro definition should use `push_reload' to indicate parts
that need reloading; OPNUM, TYPE and IND_LEVELS are usually
- suitable to be passed unaltered to 'push_reload'.
+ suitable to be passed unaltered to `push_reload'.
The code generated by this macro must not alter the substructure of
X. If it transforms X into a more legitimate form, it should
assign X (which will always be a C variable) a new value. This
also applies to parts that you change indirectly by calling
- 'push_reload'.
+ `push_reload'.
- The macro definition may use 'strict_memory_address_p' to test if
+ The macro definition may use `strict_memory_address_p' to test if
the address has become legitimate.
If you want to change only a part of X, one standard way of doing
- this is to use 'copy_rtx'. Note, however, that it unshares only a
+ this is to use `copy_rtx'. Note, however, that it unshares only a
single level of rtl. Thus, if the part to be changed is not at the
top level, you'll need to replace first the top level. It is not
- necessary for this macro to come up with a legitimate address; but
- often a machine-dependent strategy can generate better code.
+ necessary for this macro to come up with a legitimate address;
+ but often a machine-dependent strategy can generate better code.
-- Target Hook: bool TARGET_MODE_DEPENDENT_ADDRESS_P (const_rtx ADDR,
addr_space_t ADDRSPACE)
- This hook returns 'true' if memory address ADDR in address space
- ADDRSPACE can have different meanings depending on the machine mode
- of the memory reference it is used for or if the address is valid
- for some modes but not others.
+ This hook returns `true' if memory address ADDR in address space
+ ADDRSPACE can have different meanings depending on the machine
+ mode of the memory reference it is used for or if the address is
+ valid for some modes but not others.
Autoincrement and autodecrement addresses typically have
mode-dependent effects because the amount of the increment or
@@ -32566,24 +32984,24 @@ This is about addressing modes.
You may assume that ADDR is a valid address for the machine.
- The default version of this hook returns 'false'.
+ The default version of this hook returns `false'.
-- Target Hook: bool TARGET_LEGITIMATE_CONSTANT_P (machine_mode MODE,
rtx X)
This hook returns true if X is a legitimate constant for a
MODE-mode immediate operand on the target machine. You can assume
- that X satisfies 'CONSTANT_P', so you need not check this.
+ that X satisfies `CONSTANT_P', so you need not check this.
The default definition returns true.
-- Target Hook: rtx TARGET_DELEGITIMIZE_ADDRESS (rtx X)
This hook is used to undo the possibly obfuscating effects of the
- 'LEGITIMIZE_ADDRESS' and 'LEGITIMIZE_RELOAD_ADDRESS' target macros.
- Some backend implementations of these macros wrap symbol references
- inside an 'UNSPEC' rtx to represent PIC or similar addressing
- modes. This target hook allows GCC's optimizers to understand the
- semantics of these opaque 'UNSPEC's by converting them back into
- their original form.
+ `LEGITIMIZE_ADDRESS' and `LEGITIMIZE_RELOAD_ADDRESS' target
+ macros. Some backend implementations of these macros wrap symbol
+ references inside an `UNSPEC' rtx to represent PIC or similar
+ addressing modes. This target hook allows GCC's optimizers to
+ understand the semantics of these opaque `UNSPEC's by converting
+ them back into their original form.
-- Target Hook: bool TARGET_CONST_NOT_OK_FOR_DEBUG_P (rtx X)
This hook should return true if X should not be emitted into debug
@@ -32606,13 +33024,13 @@ This is about addressing modes.
-- Target Hook: bool TARGET_USE_BLOCKS_FOR_CONSTANT_P (machine_mode
MODE, const_rtx X)
This hook should return true if pool entries for constant X can be
- placed in an 'object_block' structure. MODE is the mode of X.
+ placed in an `object_block' structure. MODE is the mode of X.
The default version returns false for all constants.
-- Target Hook: bool TARGET_USE_BLOCKS_FOR_DECL_P (const_tree DECL)
This hook should return true if pool entries for DECL should be
- placed in an 'object_block' structure.
+ placed in an `object_block' structure.
The default version returns true for all decls.
@@ -32620,11 +33038,11 @@ This is about addressing modes.
MD_FN, bool SQRT)
This hook should return the DECL of a function that implements
reciprocal of the builtin function with builtin function code FN,
- or 'NULL_TREE' if such a function is not available. MD_FN is true
+ or `NULL_TREE' if such a function is not available. MD_FN is true
when FN is a code of a machine-dependent builtin function. When
SQRT is true, additional optimizations that apply only to the
reciprocal of a square root function are performed, and only
- reciprocals of 'sqrt' function are valid.
+ reciprocals of `sqrt' function are valid.
-- Target Hook: tree TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD (void)
This hook should return the DECL of a function F that given an
@@ -32634,22 +33052,22 @@ This is about addressing modes.
The autovectorizer, when vectorizing a load operation from an
address ADDR that may be unaligned, will generate two vector loads
- from the two aligned addresses around ADDR. It then generates a
- 'REALIGN_LOAD' operation to extract the relevant data from the two
- loaded vectors. The first two arguments to 'REALIGN_LOAD', V1 and
+ from the two aligned addresses around ADDR. It then generates a
+ `REALIGN_LOAD' operation to extract the relevant data from the two
+ loaded vectors. The first two arguments to `REALIGN_LOAD', V1 and
V2, are the two vectors, each of size VS, and the third argument,
- OFF, defines how the data will be extracted from these two vectors:
- if OFF is 0, then the returned vector is V2; otherwise, the
- returned vector is composed from the last VS-OFF elements of V1
- concatenated to the first OFF elements of V2.
-
- If this hook is defined, the autovectorizer will generate a call to
- F (using the DECL tree that this hook returns) and will use the
- return value of F as the argument OFF to 'REALIGN_LOAD'.
+ OFF, defines how the data will be extracted from these two
+ vectors: if OFF is 0, then the returned vector is V2; otherwise,
+ the returned vector is composed from the last VS-OFF elements of
+ V1 concatenated to the first OFF elements of V2.
+
+ If this hook is defined, the autovectorizer will generate a call
+ to F (using the DECL tree that this hook returns) and will use the
+ return value of F as the argument OFF to `REALIGN_LOAD'.
Therefore, the mask M returned by F should comply with the
- semantics expected by 'REALIGN_LOAD' described above. If this hook
- is not defined, then ADDR will be used as the argument OFF to
- 'REALIGN_LOAD', in which case the low log2(VS) - 1 bits of ADDR
+ semantics expected by `REALIGN_LOAD' described above. If this
+ hook is not defined, then ADDR will be used as the argument OFF to
+ `REALIGN_LOAD', in which case the low log2(VS) - 1 bits of ADDR
will be considered.
-- Target Hook: int TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST (enum
@@ -32665,25 +33083,25 @@ This is about addressing modes.
-- Target Hook: bool TARGET_VECTORIZE_VEC_PERM_CONST_OK (machine_mode,
const unsigned char *SEL)
- Return true if a vector created for 'vec_perm_const' is valid.
+ Return true if a vector created for `vec_perm_const' is valid.
-- Target Hook: tree TARGET_VECTORIZE_BUILTIN_CONVERSION (unsigned
CODE, tree DEST_TYPE, tree SRC_TYPE)
This hook should return the DECL of a function that implements
conversion of the input vector of type SRC_TYPE to type DEST_TYPE.
- The value of CODE is one of the enumerators in 'enum tree_code' and
+ The value of CODE is one of the enumerators in `enum tree_code' and
specifies how the conversion is to be applied (truncation,
rounding, etc.).
If this hook is defined, the autovectorizer will use the
- 'TARGET_VECTORIZE_BUILTIN_CONVERSION' target hook when vectorizing
- conversion. Otherwise, it will return 'NULL_TREE'.
+ `TARGET_VECTORIZE_BUILTIN_CONVERSION' target hook when vectorizing
+ conversion. Otherwise, it will return `NULL_TREE'.
- -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION (tree
- FNDECL, tree VEC_TYPE_OUT, tree VEC_TYPE_IN)
+ -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION
+ (tree FNDECL, tree VEC_TYPE_OUT, tree VEC_TYPE_IN)
This hook should return the decl of a function that implements the
vectorized variant of the builtin function with builtin function
- code CODE or 'NULL_TREE' if such a function is not available. The
+ code CODE or `NULL_TREE' if such a function is not available. The
value of FNDECL is the builtin function declaration. The return
type of the vectorized function shall be of vector type
VEC_TYPE_OUT and the argument types should be VEC_TYPE_IN.
@@ -32701,15 +33119,15 @@ This is about addressing modes.
-- Target Hook: machine_mode TARGET_VECTORIZE_PREFERRED_SIMD_MODE
(machine_mode MODE)
This hook should return the preferred mode for vectorizing scalar
- mode MODE. The default is equal to 'word_mode', because the
+ mode MODE. The default is equal to `word_mode', because the
vectorizer can do some transformations even in absence of
specialized SIMD hardware.
-- Target Hook: unsigned int
- TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES (void)
+TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES (void)
This hook should return a mask of sizes that should be iterated
over after trying to autovectorize using the vector size derived
- from the mode returned by 'TARGET_VECTORIZE_PREFERRED_SIMD_MODE'.
+ from the mode returned by `TARGET_VECTORIZE_PREFERRED_SIMD_MODE'.
The default is zero which means to not iterate over other vector
sizes.
@@ -32718,31 +33136,34 @@ This is about addressing modes.
This hook should initialize target-specific data structures in
preparation for modeling the costs of vectorizing a loop or basic
block. The default allocates three unsigned integers for
- accumulating costs for the prologue, body, and epilogue of the loop
- or basic block. If LOOP_INFO is non-NULL, it identifies the loop
- being vectorized; otherwise a single block is being vectorized.
+ accumulating costs for the prologue, body, and epilogue of the
+ loop or basic block. If LOOP_INFO is non-NULL, it identifies the
+ loop being vectorized; otherwise a single block is being
+ vectorized.
-- Target Hook: unsigned TARGET_VECTORIZE_ADD_STMT_COST (void *DATA,
- int COUNT, enum vect_cost_for_stmt KIND, struct _stmt_vec_info
- *STMT_INFO, int MISALIGN, enum vect_cost_model_location WHERE)
+ int COUNT, enum vect_cost_for_stmt KIND, struct
+ _stmt_vec_info *STMT_INFO, int MISALIGN, enum
+ vect_cost_model_location WHERE)
This hook should update the target-specific DATA in response to
adding COUNT copies of the given KIND of statement to a loop or
basic block. The default adds the builtin vectorizer cost for the
- copies of the statement to the accumulator specified by WHERE, (the
- prologue, body, or epilogue) and returns the amount added. The
- return value should be viewed as a tentative cost that may later be
- revised.
-
- -- Target Hook: void TARGET_VECTORIZE_FINISH_COST (void *DATA, unsigned
- *PROLOGUE_COST, unsigned *BODY_COST, unsigned *EPILOGUE_COST)
- This hook should complete calculations of the cost of vectorizing a
- loop or basic block based on DATA, and return the prologue, body,
- and epilogue costs as unsigned integers. The default returns the
- value of the three accumulators.
+ copies of the statement to the accumulator specified by WHERE,
+ (the prologue, body, or epilogue) and returns the amount added.
+ The return value should be viewed as a tentative cost that may
+ later be revised.
+
+ -- Target Hook: void TARGET_VECTORIZE_FINISH_COST (void *DATA,
+ unsigned *PROLOGUE_COST, unsigned *BODY_COST, unsigned
+ *EPILOGUE_COST)
+ This hook should complete calculations of the cost of vectorizing
+ a loop or basic block based on DATA, and return the prologue,
+ body, and epilogue costs as unsigned integers. The default
+ returns the value of the three accumulators.
-- Target Hook: void TARGET_VECTORIZE_DESTROY_COST_DATA (void *DATA)
This hook should release DATA and any related data structures
- allocated by TARGET_VECTORIZE_INIT_COST. The default releases the
+ allocated by TARGET_VECTORIZE_INIT_COST. The default releases the
accumulator.
-- Target Hook: tree TARGET_VECTORIZE_BUILTIN_TM_LOAD (tree)
@@ -32756,9 +33177,9 @@ This is about addressing modes.
-- Target Hook: tree TARGET_VECTORIZE_BUILTIN_GATHER (const_tree
MEM_VECTYPE, const_tree INDEX_TYPE, int SCALE)
Target builtin that implements vector gather operation.
- MEM_VECTYPE is the vector type of the load and INDEX_TYPE is scalar
- type of the index, scaled by SCALE. The default is 'NULL_TREE'
- which means to not vectorize gather loads.
+ MEM_VECTYPE is the vector type of the load and INDEX_TYPE is
+ scalar type of the index, scaled by SCALE. The default is
+ `NULL_TREE' which means to not vectorize gather loads.
-- Target Hook: int TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN
(struct cgraph_node *, struct cgraph_simd_clone *, TREE, INT)
@@ -32769,7 +33190,7 @@ This is about addressing modes.
variants that should be emitted.
-- Target Hook: void TARGET_SIMD_CLONE_ADJUST (struct cgraph_node *)
- This hook should add implicit 'attribute(target("..."))' attribute
+ This hook should add implicit `attribute(target("..."))' attribute
to SIMD clone NODE if needed.
-- Target Hook: int TARGET_SIMD_CLONE_USABLE (struct cgraph_node *)
@@ -32790,8 +33211,8 @@ example, if we have:
static int a, b, c;
int foo (void) { return a + b + c; }
- the code for 'foo' will usually calculate three separate symbolic
-addresses: those of 'a', 'b' and 'c'. On some targets, it would be
+ the code for `foo' will usually calculate three separate symbolic
+addresses: those of `a', `b' and `c'. On some targets, it would be
better to calculate just one symbolic address and access the three
variables relative to it. The equivalent pseudocode would be something
like:
@@ -32802,13 +33223,13 @@ like:
return xr[&a - &x] + xr[&b - &x] + xr[&c - &x];
}
- (which isn't valid C). We refer to shared addresses like 'x' as
-"section anchors". Their use is controlled by '-fsection-anchors'.
+ (which isn't valid C). We refer to shared addresses like `x' as
+"section anchors". Their use is controlled by `-fsection-anchors'.
The hooks below describe the target properties that GCC needs to know
-in order to make effective use of section anchors. It won't use section
-anchors at all unless either 'TARGET_MIN_ANCHOR_OFFSET' or
-'TARGET_MAX_ANCHOR_OFFSET' is set to a nonzero value.
+in order to make effective use of section anchors. It won't use
+section anchors at all unless either `TARGET_MIN_ANCHOR_OFFSET' or
+`TARGET_MAX_ANCHOR_OFFSET' is set to a nonzero value.
-- Target Hook: HOST_WIDE_INT TARGET_MIN_ANCHOR_OFFSET
The minimum offset that should be applied to a section anchor. On
@@ -32817,27 +33238,28 @@ anchors at all unless either 'TARGET_MIN_ANCHOR_OFFSET' or
every mode. The default value is 0.
-- Target Hook: HOST_WIDE_INT TARGET_MAX_ANCHOR_OFFSET
- Like 'TARGET_MIN_ANCHOR_OFFSET', but the maximum (inclusive) offset
- that should be applied to section anchors. The default value is 0.
+ Like `TARGET_MIN_ANCHOR_OFFSET', but the maximum (inclusive)
+ offset that should be applied to section anchors. The default
+ value is 0.
-- Target Hook: void TARGET_ASM_OUTPUT_ANCHOR (rtx X)
Write the assembly code to define section anchor X, which is a
- 'SYMBOL_REF' for which 'SYMBOL_REF_ANCHOR_P (X)' is true. The hook
- is called with the assembly output position set to the beginning of
- 'SYMBOL_REF_BLOCK (X)'.
+ `SYMBOL_REF' for which `SYMBOL_REF_ANCHOR_P (X)' is true. The
+ hook is called with the assembly output position set to the
+ beginning of `SYMBOL_REF_BLOCK (X)'.
- If 'ASM_OUTPUT_DEF' is available, the hook's default definition
- uses it to define the symbol as '. + SYMBOL_REF_BLOCK_OFFSET (X)'.
- If 'ASM_OUTPUT_DEF' is not available, the hook's default definition
- is 'NULL', which disables the use of section anchors altogether.
+ If `ASM_OUTPUT_DEF' is available, the hook's default definition
+ uses it to define the symbol as `. + SYMBOL_REF_BLOCK_OFFSET (X)'.
+ If `ASM_OUTPUT_DEF' is not available, the hook's default definition
+ is `NULL', which disables the use of section anchors altogether.
-- Target Hook: bool TARGET_USE_ANCHORS_FOR_SYMBOL_P (const_rtx X)
Return true if GCC should attempt to use anchors to access
- 'SYMBOL_REF' X. You can assume 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)'
- and '!SYMBOL_REF_ANCHOR_P (X)'.
+ `SYMBOL_REF' X. You can assume `SYMBOL_REF_HAS_BLOCK_INFO_P (X)'
+ and `!SYMBOL_REF_ANCHOR_P (X)'.
- The default version is correct for most targets, but you might need
- to intercept this hook to handle things like target-specific
+ The default version is correct for most targets, but you might
+ need to intercept this hook to handle things like target-specific
attributes or target-specific sections.

@@ -32849,18 +33271,19 @@ File: gccint.info, Node: Condition Code, Next: Costs, Prev: Anchored Addresse
The macros in this section can be split in two families, according to
the two ways of representing condition codes in GCC.
- The first representation is the so called '(cc0)' representation (*note
-Jump Patterns::), where all instructions can have an implicit clobber of
-the condition codes. The second is the condition code register
-representation, which provides better schedulability for architectures
-that do have a condition code register, but on which most instructions
-do not affect it. The latter category includes most RISC machines.
+ The first representation is the so called `(cc0)' representation
+(*note Jump Patterns::), where all instructions can have an implicit
+clobber of the condition codes. The second is the condition code
+register representation, which provides better schedulability for
+architectures that do have a condition code register, but on which most
+instructions do not affect it. The latter category includes most RISC
+machines.
The implicit clobbering poses a strong restriction on the placement of
the definition and use of the condition code. In the past the
definition and use were always adjacent. However, recent changes to
support trapping arithmatic may result in the definition and user being
-in different blocks. Thus, there may be a 'NOTE_INSN_BASIC_BLOCK'
+in different blocks. Thus, there may be a `NOTE_INSN_BASIC_BLOCK'
between them. Additionally, the definition may be the source of
exception handling edges.
@@ -32876,10 +33299,10 @@ represent the condition code for new ports. If there is a specific
condition code register in the machine, use a hard register. If the
condition code or comparison result can be placed in any general
register, or if there are multiple condition registers, use a pseudo
-register. Registers used to store the condition code value will usually
-have a mode that is in class 'MODE_CC'.
+register. Registers used to store the condition code value will
+usually have a mode that is in class `MODE_CC'.
- Alternatively, you can use 'BImode' if the comparison operator is
+ Alternatively, you can use `BImode' if the comparison operator is
specified already in the compare instruction. In this case, you are not
interested in most macros in this section.
@@ -32891,10 +33314,10 @@ interested in most macros in this section.

File: gccint.info, Node: CC0 Condition Codes, Next: MODE_CC Condition Codes, Up: Condition Code
-17.15.1 Representation of condition codes using '(cc0)'
+17.15.1 Representation of condition codes using `(cc0)'
-------------------------------------------------------
-The file 'conditions.h' defines a variable 'cc_status' to describe how
+The file `conditions.h' defines a variable `cc_status' to describe how
the condition code was computed (in case the interpretation of the
condition code depends on the instruction that it was set by). This
variable contains the RTL expressions on which the condition code is
@@ -32902,56 +33325,56 @@ currently based, and several standard flags.
Sometimes additional machine-specific flags must be defined in the
machine description header file. It can also add additional
-machine-specific information by defining 'CC_STATUS_MDEP'.
+machine-specific information by defining `CC_STATUS_MDEP'.
-- Macro: CC_STATUS_MDEP
- C code for a data type which is used for declaring the 'mdep'
- component of 'cc_status'. It defaults to 'int'.
+ C code for a data type which is used for declaring the `mdep'
+ component of `cc_status'. It defaults to `int'.
- This macro is not used on machines that do not use 'cc0'.
+ This macro is not used on machines that do not use `cc0'.
-- Macro: CC_STATUS_MDEP_INIT
- A C expression to initialize the 'mdep' field to "empty". The
+ A C expression to initialize the `mdep' field to "empty". The
default definition does nothing, since most machines don't use the
field anyway. If you want to use the field, you should probably
define this macro to initialize it.
- This macro is not used on machines that do not use 'cc0'.
+ This macro is not used on machines that do not use `cc0'.
-- Macro: NOTICE_UPDATE_CC (EXP, INSN)
- A C compound statement to set the components of 'cc_status'
+ A C compound statement to set the components of `cc_status'
appropriately for an insn INSN whose body is EXP. It is this
macro's responsibility to recognize insns that set the condition
code as a byproduct of other activity as well as those that
- explicitly set '(cc0)'.
+ explicitly set `(cc0)'.
- This macro is not used on machines that do not use 'cc0'.
+ This macro is not used on machines that do not use `cc0'.
If there are insns that do not set the condition code but do alter
other machine registers, this macro must check to see whether they
invalidate the expressions that the condition code is recorded as
reflecting. For example, on the 68000, insns that store in address
registers do not set the condition code, which means that usually
- 'NOTICE_UPDATE_CC' can leave 'cc_status' unaltered for such insns.
+ `NOTICE_UPDATE_CC' can leave `cc_status' unaltered for such insns.
But suppose that the previous insn set the condition code based on
- location 'a4@(102)' and the current insn stores a new value in
- 'a4'. Although the condition code is not changed by this, it will
- no longer be true that it reflects the contents of 'a4@(102)'.
- Therefore, 'NOTICE_UPDATE_CC' must alter 'cc_status' in this case
+ location `a4@(102)' and the current insn stores a new value in
+ `a4'. Although the condition code is not changed by this, it will
+ no longer be true that it reflects the contents of `a4@(102)'.
+ Therefore, `NOTICE_UPDATE_CC' must alter `cc_status' in this case
to say that nothing is known about the condition code value.
- The definition of 'NOTICE_UPDATE_CC' must be prepared to deal with
+ The definition of `NOTICE_UPDATE_CC' must be prepared to deal with
the results of peephole optimization: insns whose patterns are
- 'parallel' RTXs containing various 'reg', 'mem' or constants which
+ `parallel' RTXs containing various `reg', `mem' or constants which
are just the operands. The RTL structure of these insns is not
sufficient to indicate what the insns actually do. What
- 'NOTICE_UPDATE_CC' should do when it sees one is just to run
- 'CC_STATUS_INIT'.
+ `NOTICE_UPDATE_CC' should do when it sees one is just to run
+ `CC_STATUS_INIT'.
- A possible definition of 'NOTICE_UPDATE_CC' is to call a function
+ A possible definition of `NOTICE_UPDATE_CC' is to call a function
that looks at an attribute (*note Insn Attributes::) named, for
- example, 'cc'. This avoids having detailed information about
- patterns in two places, the 'md' file and in 'NOTICE_UPDATE_CC'.
+ example, `cc'. This avoids having detailed information about
+ patterns in two places, the `md' file and in `NOTICE_UPDATE_CC'.

File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes, Up: Condition Code
@@ -32961,23 +33384,23 @@ File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes,
-- Macro: SELECT_CC_MODE (OP, X, Y)
On many machines, the condition code may be produced by other
- instructions than compares, for example the branch can use directly
- the condition code set by a subtract instruction. However, on some
- machines when the condition code is set this way some bits (such as
- the overflow bit) are not set in the same way as a test
- instruction, so that a different branch instruction must be used
- for some conditional branches. When this happens, use the machine
- mode of the condition code register to record different formats of
- the condition code register. Modes can also be used to record
- which compare instruction (e.g. a signed or an unsigned
+ instructions than compares, for example the branch can use
+ directly the condition code set by a subtract instruction.
+ However, on some machines when the condition code is set this way
+ some bits (such as the overflow bit) are not set in the same way
+ as a test instruction, so that a different branch instruction must
+ be used for some conditional branches. When this happens, use the
+ machine mode of the condition code register to record different
+ formats of the condition code register. Modes can also be used to
+ record which compare instruction (e.g. a signed or an unsigned
comparison) produced the condition codes.
- If other modes than 'CCmode' are required, add them to
- 'MACHINE-modes.def' and define 'SELECT_CC_MODE' to choose a mode
+ If other modes than `CCmode' are required, add them to
+ `MACHINE-modes.def' and define `SELECT_CC_MODE' to choose a mode
given an operand of a compare. This is needed because the modes
have to be chosen not only during RTL generation but also, for
example, by instruction combination. The result of
- 'SELECT_CC_MODE' should be consistent with the mode used in the
+ `SELECT_CC_MODE' should be consistent with the mode used in the
patterns; for example to support the case of the add on the SPARC
discussed above, we have the pattern
@@ -32990,8 +33413,8 @@ File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes,
""
"...")
- together with a 'SELECT_CC_MODE' that returns 'CC_NOOVmode' for
- comparisons whose argument is a 'plus':
+ together with a `SELECT_CC_MODE' that returns `CC_NOOVmode' for
+ comparisons whose argument is a `plus':
#define SELECT_CC_MODE(OP,X,Y) \
(GET_MODE_CLASS (GET_MODE (X)) == MODE_FLOAT \
@@ -33002,45 +33425,45 @@ File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes,
? CC_NOOVmode : CCmode))
Another reason to use modes is to retain information on which
- operands were used by the comparison; see 'REVERSIBLE_CC_MODE'
+ operands were used by the comparison; see `REVERSIBLE_CC_MODE'
later in this section.
You should define this macro if and only if you define extra CC
- modes in 'MACHINE-modes.def'.
+ modes in `MACHINE-modes.def'.
-- Target Hook: void TARGET_CANONICALIZE_COMPARISON (int *CODE, rtx
*OP0, rtx *OP1, bool OP0_PRESERVE_VALUE)
On some machines not all possible comparisons are defined, but you
can convert an invalid comparison into a valid one. For example,
- the Alpha does not have a 'GT' comparison, but you can use an 'LT'
+ the Alpha does not have a `GT' comparison, but you can use an `LT'
comparison instead and swap the order of the operands.
On such machines, implement this hook to do any required
conversions. CODE is the initial comparison code and OP0 and OP1
are the left and right operands of the comparison, respectively.
- If OP0_PRESERVE_VALUE is 'true' the implementation is not allowed
+ If OP0_PRESERVE_VALUE is `true' the implementation is not allowed
to change the value of OP0 since the value might be used in RTXs
- which aren't comparisons. E.g. the implementation is not allowed
+ which aren't comparisons. E.g. the implementation is not allowed
to swap operands in that case.
GCC will not assume that the comparison resulting from this macro
is valid but will see if the resulting insn matches a pattern in
- the 'md' file.
+ the `md' file.
You need not to implement this hook if it would never change the
comparison code or operands.
-- Macro: REVERSIBLE_CC_MODE (MODE)
A C expression whose value is one if it is always safe to reverse a
- comparison whose mode is MODE. If 'SELECT_CC_MODE' can ever return
- MODE for a floating-point inequality comparison, then
- 'REVERSIBLE_CC_MODE (MODE)' must be zero.
+ comparison whose mode is MODE. If `SELECT_CC_MODE' can ever
+ return MODE for a floating-point inequality comparison, then
+ `REVERSIBLE_CC_MODE (MODE)' must be zero.
You need not define this macro if it would always returns zero or
if the floating-point format is anything other than
- 'IEEE_FLOAT_FORMAT'. For example, here is the definition used on
+ `IEEE_FLOAT_FORMAT'. For example, here is the definition used on
the SPARC, where floating-point inequality comparisons are given
- either 'CCFPEmode' or 'CCFPmode':
+ either `CCFPEmode' or `CCFPmode':
#define REVERSIBLE_CC_MODE(MODE) \
((MODE) != CCFPEmode && (MODE) != CCFPmode)
@@ -33048,11 +33471,11 @@ File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes,
-- Macro: REVERSE_CONDITION (CODE, MODE)
A C expression whose value is reversed condition code of the CODE
for comparison done in CC_MODE MODE. The macro is used only in
- case 'REVERSIBLE_CC_MODE (MODE)' is nonzero. Define this macro in
+ case `REVERSIBLE_CC_MODE (MODE)' is nonzero. Define this macro in
case machine has some non-standard way how to reverse certain
conditionals. For instance in case all floating point conditions
- are non-trapping, compiler may freely convert unordered compares to
- ordered ones. Then definition may look like:
+ are non-trapping, compiler may freely convert unordered compares
+ to ordered ones. Then definition may look like:
#define REVERSE_CONDITION(CODE, MODE) \
((MODE) != CCFPmode ? reverse_condition (CODE) \
@@ -33060,36 +33483,36 @@ File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes,
-- Target Hook: bool TARGET_FIXED_CONDITION_CODE_REGS (unsigned int
*P1, unsigned int *P2)
- On targets which do not use '(cc0)', and which use a hard register
+ On targets which do not use `(cc0)', and which use a hard register
rather than a pseudo-register to hold condition codes, the regular
CSE passes are often not able to identify cases in which the hard
- register is set to a common value. Use this hook to enable a small
- pass which optimizes such cases. This hook should return true to
- enable this pass, and it should set the integers to which its
- arguments point to the hard register numbers used for condition
- codes. When there is only one such register, as is true on most
- systems, the integer pointed to by P2 should be set to
- 'INVALID_REGNUM'.
+ register is set to a common value. Use this hook to enable a
+ small pass which optimizes such cases. This hook should return
+ true to enable this pass, and it should set the integers to which
+ its arguments point to the hard register numbers used for
+ condition codes. When there is only one such register, as is true
+ on most systems, the integer pointed to by P2 should be set to
+ `INVALID_REGNUM'.
The default version of this hook returns false.
-- Target Hook: machine_mode TARGET_CC_MODES_COMPATIBLE (machine_mode
M1, machine_mode M2)
On targets which use multiple condition code modes in class
- 'MODE_CC', it is sometimes the case that a comparison can be
+ `MODE_CC', it is sometimes the case that a comparison can be
validly done in more than one mode. On such a system, define this
target hook to take two mode arguments and to return a mode in
which both comparisons may be validly done. If there is no such
- mode, return 'VOIDmode'.
+ mode, return `VOIDmode'.
The default version of this hook checks whether the modes are the
same. If they are, it returns that mode. If they are different,
- it returns 'VOIDmode'.
+ it returns `VOIDmode'.
-- Target Hook: unsigned int TARGET_FLAGS_REGNUM
If the target has a dedicated flags register, and it needs to use
- the post-reload comparison elimination pass, then this value should
- be set appropriately.
+ the post-reload comparison elimination pass, then this value
+ should be set appropriately.

File: gccint.info, Node: Costs, Next: Scheduling, Prev: Condition Code, Up: Target Macros
@@ -33103,7 +33526,7 @@ on the target machine.
-- Macro: REGISTER_MOVE_COST (MODE, FROM, TO)
A C expression for the cost of moving data of mode MODE from a
register in class FROM to one in class TO. The classes are
- expressed using the enumeration values such as 'GENERAL_REGS'. A
+ expressed using the enumeration values such as `GENERAL_REGS'. A
value of 2 is the default; other values are interpreted relative to
that.
@@ -33111,22 +33534,22 @@ on the target machine.
same as TO; on some machines it is expensive to move between
registers if they are not general registers.
- If reload sees an insn consisting of a single 'set' between two
- hard registers, and if 'REGISTER_MOVE_COST' applied to their
+ If reload sees an insn consisting of a single `set' between two
+ hard registers, and if `REGISTER_MOVE_COST' applied to their
classes returns a value of 2, reload does not check to ensure that
the constraints of the insn are met. Setting a cost of other than
2 will allow reload to verify that the constraints are met. You
- should do this if the 'movM' pattern's constraints do not allow
+ should do this if the `movM' pattern's constraints do not allow
such copying.
These macros are obsolete, new ports should use the target hook
- 'TARGET_REGISTER_MOVE_COST' instead.
+ `TARGET_REGISTER_MOVE_COST' instead.
-- Target Hook: int TARGET_REGISTER_MOVE_COST (machine_mode MODE,
reg_class_t FROM, reg_class_t TO)
This target hook should return the cost of moving data of mode MODE
from a register in class FROM to one in class TO. The classes are
- expressed using the enumeration values such as 'GENERAL_REGS'. A
+ expressed using the enumeration values such as `GENERAL_REGS'. A
value of 2 is the default; other values are interpreted relative to
that.
@@ -33134,12 +33557,12 @@ on the target machine.
same as TO; on some machines it is expensive to move between
registers if they are not general registers.
- If reload sees an insn consisting of a single 'set' between two
- hard registers, and if 'TARGET_REGISTER_MOVE_COST' applied to their
+ If reload sees an insn consisting of a single `set' between two
+ hard registers, and if `TARGET_REGISTER_MOVE_COST' applied to their
classes returns a value of 2, reload does not check to ensure that
the constraints of the insn are met. Setting a cost of other than
2 will allow reload to verify that the constraints are met. You
- should do this if the 'movM' pattern's constraints do not allow
+ should do this if the `movM' pattern's constraints do not allow
such copying.
The default version of this function returns 2.
@@ -33147,8 +33570,8 @@ on the target machine.
-- Macro: MEMORY_MOVE_COST (MODE, CLASS, IN)
A C expression for the cost of moving data of mode MODE between a
register of class CLASS and memory; IN is zero if the value is to
- be written to memory, nonzero if it is to be read in. This cost is
- relative to those in 'REGISTER_MOVE_COST'. If moving between
+ be written to memory, nonzero if it is to be read in. This cost
+ is relative to those in `REGISTER_MOVE_COST'. If moving between
registers and memory is more expensive than between two registers,
you should define this macro to express the relative cost.
@@ -33159,26 +33582,26 @@ on the target machine.
mechanism is more complex than copying via an intermediate, define
this macro to reflect the actual cost of the move.
- GCC defines the function 'memory_move_secondary_cost' if secondary
+ GCC defines the function `memory_move_secondary_cost' if secondary
reloads are needed. It computes the costs due to copying via a
secondary register. If your machine copies from memory using a
secondary register in the conventional way but the default base
value of 4 is not correct for your machine, define this macro to
- add some other value to the result of that function. The arguments
- to that function are the same as to this macro.
+ add some other value to the result of that function. The
+ arguments to that function are the same as to this macro.
These macros are obsolete, new ports should use the target hook
- 'TARGET_MEMORY_MOVE_COST' instead.
+ `TARGET_MEMORY_MOVE_COST' instead.
-- Target Hook: int TARGET_MEMORY_MOVE_COST (machine_mode MODE,
reg_class_t RCLASS, bool IN)
This target hook should return the cost of moving data of mode MODE
- between a register of class RCLASS and memory; IN is 'false' if the
- value is to be written to memory, 'true' if it is to be read in.
- This cost is relative to those in 'TARGET_REGISTER_MOVE_COST'. If
- moving between registers and memory is more expensive than between
- two registers, you should add this target hook to express the
- relative cost.
+ between a register of class RCLASS and memory; IN is `false' if
+ the value is to be written to memory, `true' if it is to be read
+ in. This cost is relative to those in `TARGET_REGISTER_MOVE_COST'.
+ If moving between registers and memory is more expensive than
+ between two registers, you should add this target hook to express
+ the relative cost.
If you do not add this target hook, GCC uses a default cost of 4
plus the cost of copying via a secondary reload register, if one is
@@ -33187,22 +33610,22 @@ on the target machine.
mechanism is more complex than copying via an intermediate, use
this target hook to reflect the actual cost of the move.
- GCC defines the function 'memory_move_secondary_cost' if secondary
+ GCC defines the function `memory_move_secondary_cost' if secondary
reloads are needed. It computes the costs due to copying via a
secondary register. If your machine copies from memory using a
secondary register in the conventional way but the default base
- value of 4 is not correct for your machine, use this target hook to
- add some other value to the result of that function. The arguments
- to that function are the same as to this target hook.
+ value of 4 is not correct for your machine, use this target hook
+ to add some other value to the result of that function. The
+ arguments to that function are the same as to this target hook.
-- Macro: BRANCH_COST (SPEED_P, PREDICTABLE_P)
A C expression for the cost of a branch instruction. A value of 1
is the default; other values are interpreted relative to that.
Parameter SPEED_P is true when the branch in question should be
- optimized for speed. When it is false, 'BRANCH_COST' should return
- a value optimal for code size rather than performance.
- PREDICTABLE_P is true for well-predicted branches. On many
- architectures the 'BRANCH_COST' can be reduced then.
+ optimized for speed. When it is false, `BRANCH_COST' should
+ return a value optimal for code size rather than performance.
+ PREDICTABLE_P is true for well-predicted branches. On many
+ architectures the `BRANCH_COST' can be reduced then.
Here are additional macros which do not specify precise relative costs,
but only that certain actions are more expensive than GCC would
@@ -33210,7 +33633,7 @@ ordinarily expect.
-- Macro: SLOW_BYTE_ACCESS
Define this macro as a C expression which is nonzero if accessing
- less than a word of memory (i.e. a 'char' or a 'short') is no
+ less than a word of memory (i.e. a `char' or a `short') is no
faster than accessing a word of memory, i.e., if such access
require more than one instruction or if there is no difference in
cost between byte and (aligned) word loads.
@@ -33224,20 +33647,20 @@ ordinarily expect.
structure, but to different bytes.
-- Macro: SLOW_UNALIGNED_ACCESS (MODE, ALIGNMENT)
- Define this macro to be the value 1 if memory accesses described by
- the MODE and ALIGNMENT parameters have a cost many times greater
+ Define this macro to be the value 1 if memory accesses described
+ by the MODE and ALIGNMENT parameters have a cost many times greater
than aligned accesses, for example if they are emulated in a trap
handler.
When this macro is nonzero, the compiler will act as if
- 'STRICT_ALIGNMENT' were nonzero when generating code for block
+ `STRICT_ALIGNMENT' were nonzero when generating code for block
moves. This can cause significantly more instructions to be
produced. Therefore, do not set this macro nonzero if unaligned
accesses only add a cycle or two to the time for a memory access.
If the value of this macro is always zero, it need not be defined.
If this macro is defined, it should produce a nonzero value when
- 'STRICT_ALIGNMENT' is nonzero.
+ `STRICT_ALIGNMENT' is nonzero.
-- Macro: MOVE_RATIO (SPEED)
The threshold of number of scalar memory-to-memory move insns,
@@ -33247,7 +33670,7 @@ ordinarily expect.
increased code size.
Note that on machines where the corresponding move insn is a
- 'define_expand' that emits a sequence of insns, this macro counts
+ `define_expand' that emits a sequence of insns, this macro counts
the number of such sequences.
The parameter SPEED is true if the code is currently being
@@ -33260,19 +33683,19 @@ ordinarily expect.
by_pieces_operation OP, bool SPEED_P)
GCC will attempt several strategies when asked to copy between two
areas of memory, or to set, clear or store to memory, for example
- when copying a 'struct'. The 'by_pieces' infrastructure implements
+ when copying a `struct'. The `by_pieces' infrastructure implements
such memory operations as a sequence of load, store or move insns.
- Alternate strategies are to expand the 'movmem' or 'setmem' optabs,
- to emit a library call, or to emit unit-by-unit, loop-based
- operations.
+ Alternate strategies are to expand the `movmem' or `setmem'
+ optabs, to emit a library call, or to emit unit-by-unit,
+ loop-based operations.
- This target hook should return true if, for a memory operation with
- a given SIZE and ALIGNMENT, using the 'by_pieces' infrastructure is
- expected to result in better code generation. Both SIZE and
- ALIGNMENT are measured in terms of storage units.
+ This target hook should return true if, for a memory operation
+ with a given SIZE and ALIGNMENT, using the `by_pieces'
+ infrastructure is expected to result in better code generation.
+ Both SIZE and ALIGNMENT are measured in terms of storage units.
- The parameter OP is one of: 'CLEAR_BY_PIECES', 'MOVE_BY_PIECES',
- 'SET_BY_PIECES', 'STORE_BY_PIECES'. These describe the type of
+ The parameter OP is one of: `CLEAR_BY_PIECES', `MOVE_BY_PIECES',
+ `SET_BY_PIECES', `STORE_BY_PIECES'. These describe the type of
memory operation under consideration.
The parameter SPEED_P is true if the code is currently being
@@ -33280,20 +33703,20 @@ ordinarily expect.
Returning true for higher values of SIZE can improve code
generation for speed if the target does not provide an
- implementation of the 'movmem' or 'setmem' standard names, if the
- 'movmem' or 'setmem' implementation would be more expensive than a
+ implementation of the `movmem' or `setmem' standard names, if the
+ `movmem' or `setmem' implementation would be more expensive than a
sequence of insns, or if the overhead of a library call would
dominate that of the body of the memory operation.
- Returning true for higher values of 'size' may also cause an
+ Returning true for higher values of `size' may also cause an
increase in code size, for example where the number of insns
emitted to perform a move would be greater than that of a library
call.
-- Macro: MOVE_MAX_PIECES
- A C expression used by 'move_by_pieces' to determine the largest
+ A C expression used by `move_by_pieces' to determine the largest
unit a load or store used to copy memory is. Defaults to
- 'MOVE_MAX'.
+ `MOVE_MAX'.
-- Macro: CLEAR_RATIO (SPEED)
The threshold of number of scalar move insns, _below_ which a
@@ -33317,47 +33740,47 @@ ordinarily expect.
The parameter SPEED is true if the code is currently being
optimized for speed rather than size.
- If you don't define this, it defaults to the value of 'MOVE_RATIO'.
+ If you don't define this, it defaults to the value of `MOVE_RATIO'.
-- Macro: USE_LOAD_POST_INCREMENT (MODE)
A C expression used to determine whether a load postincrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_POST_INCREMENT'.
+ `HAVE_POST_INCREMENT'.
-- Macro: USE_LOAD_POST_DECREMENT (MODE)
A C expression used to determine whether a load postdecrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_POST_DECREMENT'.
+ `HAVE_POST_DECREMENT'.
-- Macro: USE_LOAD_PRE_INCREMENT (MODE)
A C expression used to determine whether a load preincrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_PRE_INCREMENT'.
+ `HAVE_PRE_INCREMENT'.
-- Macro: USE_LOAD_PRE_DECREMENT (MODE)
A C expression used to determine whether a load predecrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_PRE_DECREMENT'.
+ `HAVE_PRE_DECREMENT'.
-- Macro: USE_STORE_POST_INCREMENT (MODE)
- A C expression used to determine whether a store postincrement is a
- good thing to use for a given mode. Defaults to the value of
- 'HAVE_POST_INCREMENT'.
+ A C expression used to determine whether a store postincrement is
+ a good thing to use for a given mode. Defaults to the value of
+ `HAVE_POST_INCREMENT'.
-- Macro: USE_STORE_POST_DECREMENT (MODE)
- A C expression used to determine whether a store postdecrement is a
- good thing to use for a given mode. Defaults to the value of
- 'HAVE_POST_DECREMENT'.
+ A C expression used to determine whether a store postdecrement is
+ a good thing to use for a given mode. Defaults to the value of
+ `HAVE_POST_DECREMENT'.
-- Macro: USE_STORE_PRE_INCREMENT (MODE)
This macro is used to determine whether a store preincrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_PRE_INCREMENT'.
+ `HAVE_PRE_INCREMENT'.
-- Macro: USE_STORE_PRE_DECREMENT (MODE)
This macro is used to determine whether a store predecrement is a
good thing to use for a given mode. Defaults to the value of
- 'HAVE_PRE_DECREMENT'.
+ `HAVE_PRE_DECREMENT'.
-- Macro: NO_FUNCTION_CSE
Define this macro if it is as good or better to call a constant
@@ -33365,50 +33788,50 @@ ordinarily expect.
-- Macro: LOGICAL_OP_NON_SHORT_CIRCUIT
Define this macro if a non-short-circuit operation produced by
- 'fold_range_test ()' is optimal. This macro defaults to true if
- 'BRANCH_COST' is greater than or equal to the value 2.
+ `fold_range_test ()' is optimal. This macro defaults to true if
+ `BRANCH_COST' is greater than or equal to the value 2.
- -- Target Hook: bool TARGET_RTX_COSTS (rtx X, int CODE, int OUTER_CODE,
- int OPNO, int *TOTAL, bool SPEED)
+ -- Target Hook: bool TARGET_RTX_COSTS (rtx X, int CODE, int
+ OUTER_CODE, int OPNO, int *TOTAL, bool SPEED)
This target hook describes the relative costs of RTL expressions.
The cost may depend on the precise form of the expression, which is
available for examination in X, and the fact that X appears as
operand OPNO of an expression with rtx code OUTER_CODE. That is,
- the hook can assume that there is some rtx Y such that 'GET_CODE
- (Y) == OUTER_CODE' and such that either (a) 'XEXP (Y, OPNO) == X'
- or (b) 'XVEC (Y, OPNO)' contains X.
+ the hook can assume that there is some rtx Y such that `GET_CODE
+ (Y) == OUTER_CODE' and such that either (a) `XEXP (Y, OPNO) == X'
+ or (b) `XVEC (Y, OPNO)' contains X.
CODE is X's expression code--redundant, since it can be obtained
- with 'GET_CODE (X)'.
+ with `GET_CODE (X)'.
- In implementing this hook, you can use the construct 'COSTS_N_INSNS
- (N)' to specify a cost equal to N fast instructions.
+ In implementing this hook, you can use the construct
+ `COSTS_N_INSNS (N)' to specify a cost equal to N fast instructions.
- On entry to the hook, '*TOTAL' contains a default estimate for the
+ On entry to the hook, `*TOTAL' contains a default estimate for the
cost of the expression. The hook should modify this value as
- necessary. Traditionally, the default costs are 'COSTS_N_INSNS
- (5)' for multiplications, 'COSTS_N_INSNS (7)' for division and
- modulus operations, and 'COSTS_N_INSNS (1)' for all other
+ necessary. Traditionally, the default costs are `COSTS_N_INSNS
+ (5)' for multiplications, `COSTS_N_INSNS (7)' for division and
+ modulus operations, and `COSTS_N_INSNS (1)' for all other
operations.
- When optimizing for code size, i.e. when 'speed' is false, this
- target hook should be used to estimate the relative size cost of an
- expression, again relative to 'COSTS_N_INSNS'.
+ When optimizing for code size, i.e. when `speed' is false, this
+ target hook should be used to estimate the relative size cost of
+ an expression, again relative to `COSTS_N_INSNS'.
The hook returns true when all subexpressions of X have been
- processed, and false when 'rtx_cost' should recurse.
+ processed, and false when `rtx_cost' should recurse.
-- Target Hook: int TARGET_ADDRESS_COST (rtx ADDRESS, machine_mode
MODE, addr_space_t AS, bool SPEED)
This hook computes the cost of an addressing mode that contains
ADDRESS. If not defined, the cost is computed from the ADDRESS
- expression and the 'TARGET_RTX_COST' hook.
+ expression and the `TARGET_RTX_COST' hook.
- For most CISC machines, the default cost is a good approximation of
- the true cost of the addressing mode. However, on RISC machines,
- all instructions normally have the same length and execution time.
- Hence all addresses will have equal costs.
+ For most CISC machines, the default cost is a good approximation
+ of the true cost of the addressing mode. However, on RISC
+ machines, all instructions normally have the same length and
+ execution time. Hence all addresses will have equal costs.
In cases where more than one form of an address is known, the form
with the lowest cost will be used. If multiple forms have the
@@ -33420,20 +33843,21 @@ ordinarily expect.
register and memory references will be indirect through that
register. On machines where the cost of the addressing mode
containing the sum is no higher than that of a simple indirect
- reference, this will produce an additional instruction and possibly
- require an additional register. Proper specification of this macro
- eliminates this overhead for such machines.
+ reference, this will produce an additional instruction and
+ possibly require an additional register. Proper specification of
+ this macro eliminates this overhead for such machines.
This hook is never called with an invalid address.
On machines where an address involving more than one register is as
cheap as an address computation involving only one register,
- defining 'TARGET_ADDRESS_COST' to reflect this can cause two
+ defining `TARGET_ADDRESS_COST' to reflect this can cause two
registers to be live over a region of code where only one would
- have been if 'TARGET_ADDRESS_COST' were not defined in that manner.
- This effect should be considered in the definition of this macro.
- Equivalent costs should probably only be given to addresses with
- different numbers of registers on machines with lots of registers.
+ have been if `TARGET_ADDRESS_COST' were not defined in that
+ manner. This effect should be considered in the definition of
+ this macro. Equivalent costs should probably only be given to
+ addresses with different numbers of registers on machines with
+ lots of registers.

File: gccint.info, Node: Scheduling, Next: Sections, Prev: Costs, Up: Target Macros
@@ -33452,26 +33876,26 @@ them: try the first ones in this list first.
Although the insn scheduler can define itself the possibility of
issue an insn on the same cycle, the value can serve as an
additional constraint to issue insns on the same simulated
- processor cycle (see hooks 'TARGET_SCHED_REORDER' and
- 'TARGET_SCHED_REORDER2'). This value must be constant over the
+ processor cycle (see hooks `TARGET_SCHED_REORDER' and
+ `TARGET_SCHED_REORDER2'). This value must be constant over the
entire compilation. If you need it to vary depending on what the
- instructions are, you must use 'TARGET_SCHED_VARIABLE_ISSUE'.
+ instructions are, you must use `TARGET_SCHED_VARIABLE_ISSUE'.
-- Target Hook: int TARGET_SCHED_VARIABLE_ISSUE (FILE *FILE, int
VERBOSE, rtx_insn *INSN, int MORE)
This hook is executed by the scheduler after it has scheduled an
insn from the ready list. It should return the number of insns
which can still be issued in the current cycle. The default is
- 'MORE - 1' for insns other than 'CLOBBER' and 'USE', which normally
- are not counted against the issue rate. You should define this
- hook if some insns take more machine resources than others, so that
- fewer insns can follow them in the same cycle. FILE is either a
- null pointer, or a stdio stream to write any debug output to.
- VERBOSE is the verbose level provided by '-fsched-verbose-N'. INSN
- is the instruction that was scheduled.
-
- -- Target Hook: int TARGET_SCHED_ADJUST_COST (rtx_insn *INSN, rtx LINK,
- rtx_insn *DEP_INSN, int COST)
+ `MORE - 1' for insns other than `CLOBBER' and `USE', which
+ normally are not counted against the issue rate. You should
+ define this hook if some insns take more machine resources than
+ others, so that fewer insns can follow them in the same cycle.
+ FILE is either a null pointer, or a stdio stream to write any
+ debug output to. VERBOSE is the verbose level provided by
+ `-fsched-verbose-N'. INSN is the instruction that was scheduled.
+
+ -- Target Hook: int TARGET_SCHED_ADJUST_COST (rtx_insn *INSN, rtx
+ LINK, rtx_insn *DEP_INSN, int COST)
This function corrects the value of COST based on the relationship
between INSN and DEP_INSN through the dependence LINK. It should
return the new value. The default is to make no adjustment to
@@ -33487,39 +33911,39 @@ them: try the first ones in this list first.
-- Target Hook: int TARGET_SCHED_ADJUST_PRIORITY (rtx_insn *INSN, int
PRIORITY)
- This hook adjusts the integer scheduling priority PRIORITY of INSN.
- It should return the new priority. Increase the priority to
+ This hook adjusts the integer scheduling priority PRIORITY of
+ INSN. It should return the new priority. Increase the priority to
execute INSN earlier, reduce the priority to execute INSN later.
- Do not define this hook if you do not need to adjust the scheduling
- priorities of insns.
+ Do not define this hook if you do not need to adjust the
+ scheduling priorities of insns.
-- Target Hook: int TARGET_SCHED_REORDER (FILE *FILE, int VERBOSE,
rtx_insn **READY, int *N_READYP, int CLOCK)
This hook is executed by the scheduler after it has scheduled the
ready list, to allow the machine description to reorder it (for
- example to combine two small instructions together on 'VLIW'
+ example to combine two small instructions together on `VLIW'
machines). FILE is either a null pointer, or a stdio stream to
write any debug output to. VERBOSE is the verbose level provided
- by '-fsched-verbose-N'. READY is a pointer to the ready list of
- instructions that are ready to be scheduled. N_READYP is a pointer
- to the number of elements in the ready list. The scheduler reads
- the ready list in reverse order, starting with READY[*N_READYP - 1]
- and going to READY[0]. CLOCK is the timer tick of the scheduler.
- You may modify the ready list and the number of ready insns. The
- return value is the number of insns that can issue this cycle;
- normally this is just 'issue_rate'. See also
- 'TARGET_SCHED_REORDER2'.
+ by `-fsched-verbose-N'. READY is a pointer to the ready list of
+ instructions that are ready to be scheduled. N_READYP is a
+ pointer to the number of elements in the ready list. The scheduler
+ reads the ready list in reverse order, starting with
+ READY[*N_READYP - 1] and going to READY[0]. CLOCK is the timer
+ tick of the scheduler. You may modify the ready list and the
+ number of ready insns. The return value is the number of insns
+ that can issue this cycle; normally this is just `issue_rate'.
+ See also `TARGET_SCHED_REORDER2'.
-- Target Hook: int TARGET_SCHED_REORDER2 (FILE *FILE, int VERBOSE,
rtx_insn **READY, int *N_READYP, int CLOCK)
- Like 'TARGET_SCHED_REORDER', but called at a different time. That
- function is called whenever the scheduler starts a new cycle. This
- one is called once per iteration over a cycle, immediately after
- 'TARGET_SCHED_VARIABLE_ISSUE'; it can reorder the ready list and
- return the number of insns to be scheduled in the same cycle.
+ Like `TARGET_SCHED_REORDER', but called at a different time. That
+ function is called whenever the scheduler starts a new cycle.
+ This one is called once per iteration over a cycle, immediately
+ after `TARGET_SCHED_VARIABLE_ISSUE'; it can reorder the ready list
+ and return the number of insns to be scheduled in the same cycle.
Defining this hook can be useful if there are frequent situations
- where scheduling one insn causes other insns to become ready in the
- same cycle. These other insns can then be taken into account
+ where scheduling one insn causes other insns to become ready in
+ the same cycle. These other insns can then be taken into account
properly.
-- Target Hook: bool TARGET_SCHED_MACRO_FUSION_P (void)
@@ -33529,12 +33953,12 @@ them: try the first ones in this list first.
-- Target Hook: bool TARGET_SCHED_MACRO_FUSION_PAIR_P (rtx_insn *PREV,
rtx_insn *CURR)
This hook is used to check whether two insns should be macro fused
- for a target microarchitecture. If this hook returns true for the
- given insn pair (PREV and CURR), the scheduler will put them into a
- sched group, and they will not be scheduled apart. The two insns
- will be either two SET insns or a compare and a conditional jump
- and this hook should validate any dependencies needed to fuse the
- two insns together.
+ for a target microarchitecture. If this hook returns true for the
+ given insn pair (PREV and CURR), the scheduler will put them into
+ a sched group, and they will not be scheduled apart. The two
+ insns will be either two SET insns or a compare and a conditional
+ jump and this hook should validate any dependencies needed to fuse
+ the two insns together.
-- Target Hook: void TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK
(rtx_insn *HEAD, rtx_insn *TAIL)
@@ -33551,33 +33975,34 @@ them: try the first ones in this list first.
This hook is executed by the scheduler at the beginning of each
block of instructions that are to be scheduled. FILE is either a
null pointer, or a stdio stream to write any debug output to.
- VERBOSE is the verbose level provided by '-fsched-verbose-N'.
+ VERBOSE is the verbose level provided by `-fsched-verbose-N'.
MAX_READY is the maximum number of insns in the current scheduling
region that can be live at the same time. This can be used to
allocate scratch space if it is needed, e.g. by
- 'TARGET_SCHED_REORDER'.
+ `TARGET_SCHED_REORDER'.
-- Target Hook: void TARGET_SCHED_FINISH (FILE *FILE, int VERBOSE)
This hook is executed by the scheduler at the end of each block of
instructions that are to be scheduled. It can be used to perform
- cleanup of any actions done by the other scheduling hooks. FILE is
- either a null pointer, or a stdio stream to write any debug output
- to. VERBOSE is the verbose level provided by '-fsched-verbose-N'.
+ cleanup of any actions done by the other scheduling hooks. FILE
+ is either a null pointer, or a stdio stream to write any debug
+ output to. VERBOSE is the verbose level provided by
+ `-fsched-verbose-N'.
- -- Target Hook: void TARGET_SCHED_INIT_GLOBAL (FILE *FILE, int VERBOSE,
- int OLD_MAX_UID)
+ -- Target Hook: void TARGET_SCHED_INIT_GLOBAL (FILE *FILE, int
+ VERBOSE, int OLD_MAX_UID)
This hook is executed by the scheduler after function level
initializations. FILE is either a null pointer, or a stdio stream
to write any debug output to. VERBOSE is the verbose level
- provided by '-fsched-verbose-N'. OLD_MAX_UID is the maximum insn
+ provided by `-fsched-verbose-N'. OLD_MAX_UID is the maximum insn
uid when scheduling begins.
-- Target Hook: void TARGET_SCHED_FINISH_GLOBAL (FILE *FILE, int
VERBOSE)
This is the cleanup hook corresponding to
- 'TARGET_SCHED_INIT_GLOBAL'. FILE is either a null pointer, or a
+ `TARGET_SCHED_INIT_GLOBAL'. FILE is either a null pointer, or a
stdio stream to write any debug output to. VERBOSE is the verbose
- level provided by '-fsched-verbose-N'.
+ level provided by `-fsched-verbose-N'.
-- Target Hook: rtx TARGET_SCHED_DFA_PRE_CYCLE_INSN (void)
The hook returns an RTL insn. The automaton state used in the
@@ -33585,32 +34010,32 @@ them: try the first ones in this list first.
when the new simulated processor cycle starts. Usage of the hook
may simplify the automaton pipeline description for some VLIW
processors. If the hook is defined, it is used only for the
- automaton based pipeline description. The default is not to change
- the state when the new simulated processor cycle starts.
+ automaton based pipeline description. The default is not to
+ change the state when the new simulated processor cycle starts.
-- Target Hook: void TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN (void)
The hook can be used to initialize data used by the previous hook.
-- Target Hook: rtx_insn * TARGET_SCHED_DFA_POST_CYCLE_INSN (void)
- The hook is analogous to 'TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used
+ The hook is analogous to `TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used
to changed the state as if the insn were scheduled when the new
simulated processor cycle finishes.
-- Target Hook: void TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN (void)
- The hook is analogous to 'TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN' but
+ The hook is analogous to `TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN' but
used to initialize data used by the previous hook.
-- Target Hook: void TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE (void)
- The hook to notify target that the current simulated cycle is about
- to finish. The hook is analogous to
- 'TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to change the state in
+ The hook to notify target that the current simulated cycle is
+ about to finish. The hook is analogous to
+ `TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to change the state in
more complicated situations - e.g., when advancing state on a
single insn is not enough.
-- Target Hook: void TARGET_SCHED_DFA_POST_ADVANCE_CYCLE (void)
The hook to notify target that new simulated cycle has just
started. The hook is analogous to
- 'TARGET_SCHED_DFA_POST_CYCLE_INSN' but used to change the state in
+ `TARGET_SCHED_DFA_POST_CYCLE_INSN' but used to change the state in
more complicated situations - e.g., when advancing state on a
single insn is not enough.
@@ -33619,13 +34044,13 @@ them: try the first ones in this list first.
This hook controls better choosing an insn from the ready insn
queue for the DFA-based insn scheduler. Usually the scheduler
chooses the first insn from the queue. If the hook returns a
- positive value, an additional scheduler code tries all permutations
- of 'TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD ()' subsequent
- ready insns to choose an insn whose issue will result in maximal
- number of issued insns on the same cycle. For the VLIW processor,
- the code could actually solve the problem of packing simple insns
- into the VLIW insn. Of course, if the rules of VLIW packing are
- described in the automaton.
+ positive value, an additional scheduler code tries all
+ permutations of `TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD
+ ()' subsequent ready insns to choose an insn whose issue will
+ result in maximal number of issued insns on the same cycle. For
+ the VLIW processor, the code could actually solve the problem of
+ packing simple insns into the VLIW insn. Of course, if the rules
+ of VLIW packing are described in the automaton.
This code also could be used for superscalar RISC processors. Let
us consider a superscalar RISC processor with 3 pipelines. Some
@@ -33643,15 +34068,14 @@ them: try the first ones in this list first.
The default is no multipass scheduling.
-- Target Hook: int
- TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD
- (rtx_insn *INSN, int READY_INDEX)
-
+TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD (rtx_insn *INSN,
+ int READY_INDEX)
This hook controls what insns from the ready insn queue will be
considered for the multipass insn scheduling. If the hook returns
zero for INSN, the insn will be considered in multipass scheduling.
Positive return values will remove INSN from consideration on the
- current round of multipass scheduling. Negative return values will
- remove INSN from consideration for given number of cycles.
+ current round of multipass scheduling. Negative return values
+ will remove INSN from consideration for given number of cycles.
Backends should be careful about returning non-zero for highest
priority instruction at position 0 in the ready list. READY_INDEX
is passed to allow backends make correct judgements.
@@ -33667,16 +34091,16 @@ them: try the first ones in this list first.
-- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE (void
*DATA, signed char *READY_TRY, int N_READY, rtx_insn *INSN,
const void *PREV_DATA)
- This hook is called when multipass scheduling evaluates instruction
- INSN.
+ This hook is called when multipass scheduling evaluates
+ instruction INSN.
-- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK
(const void *DATA, signed char *READY_TRY, int N_READY)
- This is called when multipass scheduling backtracks from evaluation
- of an instruction.
+ This is called when multipass scheduling backtracks from
+ evaluation of an instruction.
- -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END (const void
- *DATA)
+ -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END (const
+ void *DATA)
This hook notifies the target about the result of the concluded
current round of multipass scheduling.
@@ -33704,25 +34128,27 @@ them: try the first ones in this list first.
-- Target Hook: bool TARGET_SCHED_IS_COSTLY_DEPENDENCE (struct _dep
*_DEP, int COST, int DISTANCE)
- This hook is used to define which dependences are considered costly
- by the target, so costly that it is not advisable to schedule the
- insns that are involved in the dependence too close to one another.
- The parameters to this hook are as follows: The first parameter
- _DEP is the dependence being evaluated. The second parameter COST
- is the cost of the dependence as estimated by the scheduler, and
- the third parameter DISTANCE is the distance in cycles between the
- two insns. The hook returns 'true' if considering the distance
- between the two insns the dependence between them is considered
- costly by the target, and 'false' otherwise.
+ This hook is used to define which dependences are considered
+ costly by the target, so costly that it is not advisable to
+ schedule the insns that are involved in the dependence too close
+ to one another. The parameters to this hook are as follows: The
+ first parameter _DEP is the dependence being evaluated. The
+ second parameter COST is the cost of the dependence as estimated
+ by the scheduler, and the third parameter DISTANCE is the distance
+ in cycles between the two insns. The hook returns `true' if
+ considering the distance between the two insns the dependence
+ between them is considered costly by the target, and `false'
+ otherwise.
Defining this hook can be useful in multiple-issue out-of-order
- machines, where (a) it's practically hopeless to predict the actual
- data/resource delays, however: (b) there's a better chance to
- predict the actual grouping that will be formed, and (c) correctly
- emulating the grouping can be very important. In such targets one
- may want to allow issuing dependent insns closer to one
- another--i.e., closer than the dependence distance; however, not in
- cases of "costly dependences", which this hooks allows to define.
+ machines, where (a) it's practically hopeless to predict the
+ actual data/resource delays, however: (b) there's a better chance
+ to predict the actual grouping that will be formed, and (c)
+ correctly emulating the grouping can be very important. In such
+ targets one may want to allow issuing dependent insns closer to
+ one another--i.e., closer than the dependence distance; however,
+ not in cases of "costly dependences", which this hooks allows to
+ define.
-- Target Hook: void TARGET_SCHED_H_I_D_EXTENDED (void)
This hook is called by the insn scheduler after emitting a new
@@ -33737,16 +34163,16 @@ them: try the first ones in this list first.
CLEAN_P)
Initialize store pointed to by TC to hold target scheduling
context. It CLEAN_P is true then initialize TC as if scheduler is
- at the beginning of the block. Otherwise, copy the current context
- into TC.
+ at the beginning of the block. Otherwise, copy the current
+ context into TC.
-- Target Hook: void TARGET_SCHED_SET_SCHED_CONTEXT (void *TC)
Copy target scheduling context pointed to by TC to the current
context.
-- Target Hook: void TARGET_SCHED_CLEAR_SCHED_CONTEXT (void *TC)
- Deallocate internal data in target scheduling context pointed to by
- TC.
+ Deallocate internal data in target scheduling context pointed to
+ by TC.
-- Target Hook: void TARGET_SCHED_FREE_SCHED_CONTEXT (void *TC)
Deallocate a store for target scheduling context pointed to by TC.
@@ -33759,22 +34185,22 @@ them: try the first ones in this list first.
has a speculative version and, in case of successful check, to
generate that speculative pattern. The hook should return 1, if
the instruction has a speculative form, or -1, if it doesn't.
- REQUEST describes the type of requested speculation. If the return
- value equals 1 then NEW_PAT is assigned the generated speculative
- pattern.
+ REQUEST describes the type of requested speculation. If the
+ return value equals 1 then NEW_PAT is assigned the generated
+ speculative pattern.
-- Target Hook: bool TARGET_SCHED_NEEDS_BLOCK_P (unsigned int
DEP_STATUS)
This hook is called by the insn scheduler during generation of
- recovery code for INSN. It should return 'true', if the
+ recovery code for INSN. It should return `true', if the
corresponding check instruction should branch to recovery code, or
- 'false' otherwise.
+ `false' otherwise.
-- Target Hook: rtx TARGET_SCHED_GEN_SPEC_CHECK (rtx_insn *INSN,
rtx_insn *LABEL, unsigned int DS)
- This hook is called by the insn scheduler to generate a pattern for
- recovery check instruction. If MUTATE_P is zero, then INSN is a
- speculative instruction for which the check should be generated.
+ This hook is called by the insn scheduler to generate a pattern
+ for recovery check instruction. If MUTATE_P is zero, then INSN is
+ a speculative instruction for which the check should be generated.
LABEL is either a label of a basic block, where recovery code
should be emitted, or a null pointer, when requested check doesn't
branch to recovery code (a simple check). If MUTATE_P is nonzero,
@@ -33782,8 +34208,8 @@ them: try the first ones in this list first.
denoted by INSN should be generated. In this case LABEL can't be
null.
- -- Target Hook: void TARGET_SCHED_SET_SCHED_FLAGS (struct spec_info_def
- *SPEC_INFO)
+ -- Target Hook: void TARGET_SCHED_SET_SCHED_FLAGS (struct
+ spec_info_def *SPEC_INFO)
This hook is used by the insn scheduler to find out what features
should be enabled/used. The structure *SPEC_INFO should be filled
in by the target. The structure describes speculation types that
@@ -33793,10 +34219,10 @@ them: try the first ones in this list first.
This hook is called by the swing modulo scheduler to calculate a
resource-based lower bound which is based on the resources
available in the machine and the resources required by each
- instruction. The target backend can use G to calculate such bound.
- A very simple lower bound will be used in case this hook is not
- implemented: the total number of instructions divided by the issue
- rate.
+ instruction. The target backend can use G to calculate such
+ bound. A very simple lower bound will be used in case this hook
+ is not implemented: the total number of instructions divided by
+ the issue rate.
-- Target Hook: bool TARGET_SCHED_DISPATCH (rtx_insn *INSN, int X)
This hook is called by Haifa Scheduler. It returns true if
@@ -33808,20 +34234,20 @@ them: try the first ones in this list first.
specified in its second parameter.
-- Target Hook: bool TARGET_SCHED_EXPOSED_PIPELINE
- True if the processor has an exposed pipeline, which means that not
- just the order of instructions is important for correctness when
- scheduling, but also the latencies of operations.
+ True if the processor has an exposed pipeline, which means that
+ not just the order of instructions is important for correctness
+ when scheduling, but also the latencies of operations.
- -- Target Hook: int TARGET_SCHED_REASSOCIATION_WIDTH (unsigned int OPC,
- machine_mode MODE)
+ -- Target Hook: int TARGET_SCHED_REASSOCIATION_WIDTH (unsigned int
+ OPC, machine_mode MODE)
This hook is called by tree reassociator to determine a level of
parallelism required in output calculations chain.
-- Target Hook: void TARGET_SCHED_FUSION_PRIORITY (rtx_insn *INSN, int
MAX_PRI, int *FUSION_PRI, int *PRI)
This hook is called by scheduling fusion pass. It calculates
- fusion priorities for each instruction passed in by parameter. The
- priorities are returned via pointer parameters.
+ fusion priorities for each instruction passed in by parameter.
+ The priorities are returned via pointer parameters.
INSN is the instruction whose priorities need to be calculated.
MAX_PRI is the maximum priority can be returned in any cases.
@@ -33830,15 +34256,15 @@ them: try the first ones in this list first.
parameter through which INSN's priority should be calculated and
returned.
- Same FUSION_PRI should be returned for instructions which should be
- scheduled together. Different PRI should be returned for
+ Same FUSION_PRI should be returned for instructions which should
+ be scheduled together. Different PRI should be returned for
instructions with same FUSION_PRI. FUSION_PRI is the major sort
- key, PRI is the minor sort key. All instructions will be scheduled
- according to the two priorities. All priorities calculated should
- be between 0 (exclusive) and MAX_PRI (inclusive). To avoid false
- dependencies, FUSION_PRI of instructions which need to be scheduled
- together should be smaller than FUSION_PRI of irrelevant
- instructions.
+ key, PRI is the minor sort key. All instructions will be
+ scheduled according to the two priorities. All priorities
+ calculated should be between 0 (exclusive) and MAX_PRI
+ (inclusive). To avoid false dependencies, FUSION_PRI of
+ instructions which need to be scheduled together should be smaller
+ than FUSION_PRI of irrelevant instructions.
Given below example:
@@ -33902,34 +34328,34 @@ section", which holds initialized writable data; and the "bss section",
which holds uninitialized data. Some systems have other kinds of
sections.
- 'varasm.c' provides several well-known sections, such as
-'text_section', 'data_section' and 'bss_section'. The normal way of
-controlling a 'FOO_section' variable is to define the associated
-'FOO_SECTION_ASM_OP' macro, as described below. The macros are only
-read once, when 'varasm.c' initializes itself, so their values must be
+ `varasm.c' provides several well-known sections, such as
+`text_section', `data_section' and `bss_section'. The normal way of
+controlling a `FOO_section' variable is to define the associated
+`FOO_SECTION_ASM_OP' macro, as described below. The macros are only
+read once, when `varasm.c' initializes itself, so their values must be
run-time constants. They may however depend on command-line flags.
- _Note:_ Some run-time files, such 'crtstuff.c', also make use of the
-'FOO_SECTION_ASM_OP' macros, and expect them to be string literals.
+ _Note:_ Some run-time files, such `crtstuff.c', also make use of the
+`FOO_SECTION_ASM_OP' macros, and expect them to be string literals.
Some assemblers require a different string to be written every time a
section is selected. If your assembler falls into this category, you
-should define the 'TARGET_ASM_INIT_SECTIONS' hook and use
-'get_unnamed_section' to set up the sections.
+should define the `TARGET_ASM_INIT_SECTIONS' hook and use
+`get_unnamed_section' to set up the sections.
- You must always create a 'text_section', either by defining
-'TEXT_SECTION_ASM_OP' or by initializing 'text_section' in
-'TARGET_ASM_INIT_SECTIONS'. The same is true of 'data_section' and
-'DATA_SECTION_ASM_OP'. If you do not create a distinct
-'readonly_data_section', the default is to reuse 'text_section'.
+ You must always create a `text_section', either by defining
+`TEXT_SECTION_ASM_OP' or by initializing `text_section' in
+`TARGET_ASM_INIT_SECTIONS'. The same is true of `data_section' and
+`DATA_SECTION_ASM_OP'. If you do not create a distinct
+`readonly_data_section', the default is to reuse `text_section'.
- All the other 'varasm.c' sections are optional, and are null if the
+ All the other `varasm.c' sections are optional, and are null if the
target does not provide them.
-- Macro: TEXT_SECTION_ASM_OP
A C expression whose value is a string, including spacing,
- containing the assembler operation that should precede instructions
- and read-only data. Normally '"\t.text"' is right.
+ containing the assembler operation that should precede
+ instructions and read-only data. Normally `"\t.text"' is right.
-- Macro: HOT_TEXT_SECTION_NAME
If defined, a C string constant for the name of the section
@@ -33944,7 +34370,7 @@ target does not provide them.
-- Macro: DATA_SECTION_ASM_OP
A C expression whose value is a string, including spacing,
containing the assembler operation to identify the following data
- as writable initialized data. Normally '"\t.data"' is right.
+ as writable initialized data. Normally `"\t.data"' is right.
-- Macro: SDATA_SECTION_ASM_OP
If defined, a C expression whose value is a string, including
@@ -33960,9 +34386,9 @@ target does not provide them.
If defined, a C expression whose value is a string, including
spacing, containing the assembler operation to identify the
following data as uninitialized global data. If not defined, and
- 'ASM_OUTPUT_ALIGNED_BSS' not defined, uninitialized global data
- will be output in the data section if '-fno-common' is passed,
- otherwise 'ASM_OUTPUT_COMMON' will be used.
+ `ASM_OUTPUT_ALIGNED_BSS' not defined, uninitialized global data
+ will be output in the data section if `-fno-common' is passed,
+ otherwise `ASM_OUTPUT_COMMON' will be used.
-- Macro: SBSS_SECTION_ASM_OP
If defined, a C expression whose value is a string, including
@@ -33972,19 +34398,19 @@ target does not provide them.
-- Macro: TLS_COMMON_ASM_OP
If defined, a C expression whose value is a string containing the
assembler operation to identify the following data as thread-local
- common data. The default is '".tls_common"'.
+ common data. The default is `".tls_common"'.
-- Macro: TLS_SECTION_ASM_FLAG
If defined, a C expression whose value is a character constant
containing the flag used to mark a section as a TLS section. The
- default is ''T''.
+ default is `'T''.
-- Macro: INIT_SECTION_ASM_OP
If defined, a C expression whose value is a string, including
spacing, containing the assembler operation to identify the
following data as initialization code. If not defined, GCC will
assume such a section does not exist. This section has no
- corresponding 'init_section' variable; it is used entirely in
+ corresponding `init_section' variable; it is used entirely in
runtime code.
-- Macro: FINI_SECTION_ASM_OP
@@ -33992,56 +34418,56 @@ target does not provide them.
spacing, containing the assembler operation to identify the
following data as finalization code. If not defined, GCC will
assume such a section does not exist. This section has no
- corresponding 'fini_section' variable; it is used entirely in
+ corresponding `fini_section' variable; it is used entirely in
runtime code.
-- Macro: INIT_ARRAY_SECTION_ASM_OP
If defined, a C expression whose value is a string, including
spacing, containing the assembler operation to identify the
- following data as part of the '.init_array' (or equivalent)
+ following data as part of the `.init_array' (or equivalent)
section. If not defined, GCC will assume such a section does not
- exist. Do not define both this macro and 'INIT_SECTION_ASM_OP'.
+ exist. Do not define both this macro and `INIT_SECTION_ASM_OP'.
-- Macro: FINI_ARRAY_SECTION_ASM_OP
If defined, a C expression whose value is a string, including
spacing, containing the assembler operation to identify the
- following data as part of the '.fini_array' (or equivalent)
+ following data as part of the `.fini_array' (or equivalent)
section. If not defined, GCC will assume such a section does not
- exist. Do not define both this macro and 'FINI_SECTION_ASM_OP'.
+ exist. Do not define both this macro and `FINI_SECTION_ASM_OP'.
-- Macro: CRT_CALL_STATIC_FUNCTION (SECTION_OP, FUNCTION)
If defined, an ASM statement that switches to a different section
via SECTION_OP, calls FUNCTION, and switches back to the text
- section. This is used in 'crtstuff.c' if 'INIT_SECTION_ASM_OP' or
- 'FINI_SECTION_ASM_OP' to calls to initialization and finalization
+ section. This is used in `crtstuff.c' if `INIT_SECTION_ASM_OP' or
+ `FINI_SECTION_ASM_OP' to calls to initialization and finalization
functions from the init and fini sections. By default, this macro
- uses a simple function call. Some ports need hand-crafted assembly
- code to avoid dependencies on registers initialized in the function
- prologue or to ensure that constant pools don't end up too far way
- in the text section.
+ uses a simple function call. Some ports need hand-crafted
+ assembly code to avoid dependencies on registers initialized in
+ the function prologue or to ensure that constant pools don't end
+ up too far way in the text section.
-- Macro: TARGET_LIBGCC_SDATA_SECTION
If defined, a string which names the section into which small
variables defined in crtstuff and libgcc should go. This is useful
when the target has options for optimizing access to small data,
- and you want the crtstuff and libgcc routines to be conservative in
- what they expect of your application yet liberal in what your
- application expects. For example, for targets with a '.sdata'
- section (like MIPS), you could compile crtstuff with '-G 0' so that
- it doesn't require small data support from your application, but
- use this macro to put small data into '.sdata' so that your
+ and you want the crtstuff and libgcc routines to be conservative
+ in what they expect of your application yet liberal in what your
+ application expects. For example, for targets with a `.sdata'
+ section (like MIPS), you could compile crtstuff with `-G 0' so
+ that it doesn't require small data support from your application,
+ but use this macro to put small data into `.sdata' so that your
application can access these variables whether it uses small data
or not.
-- Macro: FORCE_CODE_SECTION_ALIGN
If defined, an ASM statement that aligns a code section to some
arbitrary boundary. This is used to force all fragments of the
- '.init' and '.fini' sections to have to same alignment and thus
+ `.init' and `.fini' sections to have to same alignment and thus
prevent the linker from having to add any padding.
-- Macro: JUMP_TABLES_IN_TEXT_SECTION
Define this macro to be an expression with a nonzero value if jump
- tables (for 'tablejump' insns) should be output in the text
+ tables (for `tablejump' insns) should be output in the text
section, along with the assembler instructions. Otherwise, the
readonly data section is used.
@@ -34050,8 +34476,8 @@ target does not provide them.
-- Target Hook: void TARGET_ASM_INIT_SECTIONS (void)
Define this hook if you need to do something special to set up the
- 'varasm.c' sections, or if your target has some special sections of
- its own that you need to create.
+ `varasm.c' sections, or if your target has some special sections
+ of its own that you need to create.
GCC calls this hook after processing the command line, but before
writing any assembly code, and before calling any of the
@@ -34063,82 +34489,82 @@ target does not provide them.
should be placed in a read-write section; bit 0 should be set if
local relocations should be placed in a read-write section.
- The default version of this function returns 3 when '-fpic' is in
+ The default version of this function returns 3 when `-fpic' is in
effect, and 0 otherwise. The hook is typically redefined when the
target cannot support (some kinds of) dynamic relocations in
read-only sections even in executables.
-- Target Hook: section * TARGET_ASM_SELECT_SECTION (tree EXP, int
RELOC, unsigned HOST_WIDE_INT ALIGN)
- Return the section into which EXP should be placed. You can assume
- that EXP is either a 'VAR_DECL' node or a constant of some sort.
- RELOC indicates whether the initial value of EXP requires link-time
- relocations. Bit 0 is set when variable contains local relocations
- only, while bit 1 is set for global relocations. ALIGN is the
- constant alignment in bits.
+ Return the section into which EXP should be placed. You can
+ assume that EXP is either a `VAR_DECL' node or a constant of some
+ sort. RELOC indicates whether the initial value of EXP requires
+ link-time relocations. Bit 0 is set when variable contains local
+ relocations only, while bit 1 is set for global relocations.
+ ALIGN is the constant alignment in bits.
The default version of this function takes care of putting
- read-only variables in 'readonly_data_section'.
+ read-only variables in `readonly_data_section'.
See also USE_SELECT_SECTION_FOR_FUNCTIONS.
-- Macro: USE_SELECT_SECTION_FOR_FUNCTIONS
Define this macro if you wish TARGET_ASM_SELECT_SECTION to be
- called for 'FUNCTION_DECL's as well as for variables and constants.
+ called for `FUNCTION_DECL's as well as for variables and constants.
- In the case of a 'FUNCTION_DECL', RELOC will be zero if the
- function has been determined to be likely to be called, and nonzero
- if it is unlikely to be called.
+ In the case of a `FUNCTION_DECL', RELOC will be zero if the
+ function has been determined to be likely to be called, and
+ nonzero if it is unlikely to be called.
-- Target Hook: void TARGET_ASM_UNIQUE_SECTION (tree DECL, int RELOC)
- Build up a unique section name, expressed as a 'STRING_CST' node,
- and assign it to 'DECL_SECTION_NAME (DECL)'. As with
- 'TARGET_ASM_SELECT_SECTION', RELOC indicates whether the initial
+ Build up a unique section name, expressed as a `STRING_CST' node,
+ and assign it to `DECL_SECTION_NAME (DECL)'. As with
+ `TARGET_ASM_SELECT_SECTION', RELOC indicates whether the initial
value of EXP requires link-time relocations.
The default version of this function appends the symbol name to the
ELF section name that would normally be used for the symbol. For
- example, the function 'foo' would be placed in '.text.foo'.
+ example, the function `foo' would be placed in `.text.foo'.
Whatever the actual target object format, this is often good
enough.
-- Target Hook: section * TARGET_ASM_FUNCTION_RODATA_SECTION (tree
DECL)
- Return the readonly data section associated with 'DECL_SECTION_NAME
- (DECL)'. The default version of this function selects
- '.gnu.linkonce.r.name' if the function's section is
- '.gnu.linkonce.t.name', '.rodata.name' if function is in
- '.text.name', and the normal readonly-data section otherwise.
+ Return the readonly data section associated with
+ `DECL_SECTION_NAME (DECL)'. The default version of this function
+ selects `.gnu.linkonce.r.name' if the function's section is
+ `.gnu.linkonce.t.name', `.rodata.name' if function is in
+ `.text.name', and the normal readonly-data section otherwise.
-- Target Hook: const char * TARGET_ASM_MERGEABLE_RODATA_PREFIX
- Usually, the compiler uses the prefix '".rodata"' to construct
+ Usually, the compiler uses the prefix `".rodata"' to construct
section names for mergeable constant data. Define this macro to
override the string if a different section name should be used.
-- Target Hook: section * TARGET_ASM_TM_CLONE_TABLE_SECTION (void)
Return the section that should be used for transactional memory
- clone tables.
+ clone tables.
-- Target Hook: section * TARGET_ASM_SELECT_RTX_SECTION (machine_mode
MODE, rtx X, unsigned HOST_WIDE_INT ALIGN)
- Return the section into which a constant X, of mode MODE, should be
- placed. You can assume that X is some kind of constant in RTL.
- The argument MODE is redundant except in the case of a 'const_int'
+ Return the section into which a constant X, of mode MODE, should
+ be placed. You can assume that X is some kind of constant in RTL.
+ The argument MODE is redundant except in the case of a `const_int'
rtx. ALIGN is the constant alignment in bits.
The default version of this function takes care of putting symbolic
- constants in 'flag_pic' mode in 'data_section' and everything else
- in 'readonly_data_section'.
+ constants in `flag_pic' mode in `data_section' and everything else
+ in `readonly_data_section'.
- -- Target Hook: tree TARGET_MANGLE_DECL_ASSEMBLER_NAME (tree DECL, tree
- ID)
+ -- Target Hook: tree TARGET_MANGLE_DECL_ASSEMBLER_NAME (tree DECL,
+ tree ID)
Define this hook if you need to postprocess the assembler name
- generated by target-independent code. The ID provided to this hook
- will be the computed name (e.g., the macro 'DECL_NAME' of the DECL
- in C, or the mangled name of the DECL in C++). The return value of
- the hook is an 'IDENTIFIER_NODE' for the appropriate mangled name
- on your target system. The default implementation of this hook
- just returns the ID provided.
+ generated by target-independent code. The ID provided to this
+ hook will be the computed name (e.g., the macro `DECL_NAME' of the
+ DECL in C, or the mangled name of the DECL in C++). The return
+ value of the hook is an `IDENTIFIER_NODE' for the appropriate
+ mangled name on your target system. The default implementation of
+ this hook just returns the ID provided.
-- Target Hook: void TARGET_ENCODE_SECTION_INFO (tree DECL, rtx RTL,
int NEW_DECL_P)
@@ -34149,62 +34575,62 @@ target does not provide them.
The hook is executed immediately after rtl has been created for
DECL, which may be a variable or function declaration or an entry
in the constant pool. In either case, RTL is the rtl in question.
- Do _not_ use 'DECL_RTL (DECL)' in this hook; that field may not
+ Do _not_ use `DECL_RTL (DECL)' in this hook; that field may not
have been initialized yet.
In the case of a constant, it is safe to assume that the rtl is a
- 'mem' whose address is a 'symbol_ref'. Most decls will also have
+ `mem' whose address is a `symbol_ref'. Most decls will also have
this form, but that is not guaranteed. Global register variables,
- for instance, will have a 'reg' for their rtl. (Normally the right
- thing to do with such unusual rtl is leave it alone.)
+ for instance, will have a `reg' for their rtl. (Normally the
+ right thing to do with such unusual rtl is leave it alone.)
- The NEW_DECL_P argument will be true if this is the first time that
- 'TARGET_ENCODE_SECTION_INFO' has been invoked on this decl. It
- will be false for subsequent invocations, which will happen for
+ The NEW_DECL_P argument will be true if this is the first time
+ that `TARGET_ENCODE_SECTION_INFO' has been invoked on this decl.
+ It will be false for subsequent invocations, which will happen for
duplicate declarations. Whether or not anything must be done for
the duplicate declaration depends on whether the hook examines
- 'DECL_ATTRIBUTES'. NEW_DECL_P is always true when the hook is
+ `DECL_ATTRIBUTES'. NEW_DECL_P is always true when the hook is
called for a constant.
The usual thing for this hook to do is to record flags in the
- 'symbol_ref', using 'SYMBOL_REF_FLAG' or 'SYMBOL_REF_FLAGS'.
+ `symbol_ref', using `SYMBOL_REF_FLAG' or `SYMBOL_REF_FLAGS'.
Historically, the name string was modified if it was necessary to
encode more than one bit of information, but this practice is now
- discouraged; use 'SYMBOL_REF_FLAGS'.
+ discouraged; use `SYMBOL_REF_FLAGS'.
- The default definition of this hook, 'default_encode_section_info'
- in 'varasm.c', sets a number of commonly-useful bits in
- 'SYMBOL_REF_FLAGS'. Check whether the default does what you need
+ The default definition of this hook, `default_encode_section_info'
+ in `varasm.c', sets a number of commonly-useful bits in
+ `SYMBOL_REF_FLAGS'. Check whether the default does what you need
before overriding it.
-- Target Hook: const char * TARGET_STRIP_NAME_ENCODING (const char
*NAME)
- Decode NAME and return the real name part, sans the characters that
- 'TARGET_ENCODE_SECTION_INFO' may have added.
+ Decode NAME and return the real name part, sans the characters
+ that `TARGET_ENCODE_SECTION_INFO' may have added.
-- Target Hook: bool TARGET_IN_SMALL_DATA_P (const_tree EXP)
Returns true if EXP should be placed into a "small data" section.
The default version of this hook always returns false.
-- Target Hook: bool TARGET_HAVE_SRODATA_SECTION
- Contains the value true if the target places read-only "small data"
- into a separate section. The default value is false.
+ Contains the value true if the target places read-only "small
+ data" into a separate section. The default value is false.
-- Target Hook: bool TARGET_PROFILE_BEFORE_PROLOGUE (void)
It returns true if target wants profile code emitted before
prologue.
The default version of this hook use the target macro
- 'PROFILE_BEFORE_PROLOGUE'.
+ `PROFILE_BEFORE_PROLOGUE'.
-- Target Hook: bool TARGET_BINDS_LOCAL_P (const_tree EXP)
- Returns true if EXP names an object for which name resolution rules
- must resolve to the current "module" (dynamic shared library or
- executable image).
+ Returns true if EXP names an object for which name resolution
+ rules must resolve to the current "module" (dynamic shared library
+ or executable image).
The default version of this hook implements the name resolution
- rules for ELF, which has a looser model of global name binding than
- other currently supported object file formats.
+ rules for ELF, which has a looser model of global name binding
+ than other currently supported object file formats.
-- Target Hook: bool TARGET_HAVE_TLS
Contains the value true if the target supports thread-local
@@ -34219,9 +34645,9 @@ File: gccint.info, Node: PIC, Next: Assembler Format, Prev: Sections, Up: Ta
This section describes macros that help implement generation of position
independent code. Simply defining these macros is not enough to
generate valid PIC; you must also add support to the hook
-'TARGET_LEGITIMATE_ADDRESS_P' and to the macro 'PRINT_OPERAND_ADDRESS',
-as well as 'LEGITIMIZE_ADDRESS'. You must modify the definition of
-'movsi' to do something appropriate when the source operand contains a
+`TARGET_LEGITIMATE_ADDRESS_P' and to the macro `PRINT_OPERAND_ADDRESS',
+as well as `LEGITIMIZE_ADDRESS'. You must modify the definition of
+`movsi' to do something appropriate when the source operand contains a
symbolic address. You may also need to alter the handling of switch
statements so that they use relative addresses.
@@ -34233,21 +34659,21 @@ statements so that they use relative addresses.
once, as with the stack pointer and frame pointer registers. If
this macro is not defined, it is up to the machine-dependent files
to allocate such a register (if necessary). Note that this
- register must be fixed when in use (e.g. when 'flag_pic' is true).
+ register must be fixed when in use (e.g. when `flag_pic' is true).
-- Macro: PIC_OFFSET_TABLE_REG_CALL_CLOBBERED
A C expression that is nonzero if the register defined by
- 'PIC_OFFSET_TABLE_REGNUM' is clobbered by calls. If not defined,
+ `PIC_OFFSET_TABLE_REGNUM' is clobbered by calls. If not defined,
the default is zero. Do not define this macro if
- 'PIC_OFFSET_TABLE_REGNUM' is not defined.
+ `PIC_OFFSET_TABLE_REGNUM' is not defined.
-- Macro: LEGITIMATE_PIC_OPERAND_P (X)
A C expression that is nonzero if X is a legitimate immediate
operand on the target machine when generating position independent
- code. You can assume that X satisfies 'CONSTANT_P', so you need
+ code. You can assume that X satisfies `CONSTANT_P', so you need
not check this. You can also assume FLAG_PIC is true, so you need
not check it either. You need not define this macro if all
- constants (including 'SYMBOL_REF') can be immediate operands when
+ constants (including `SYMBOL_REF') can be immediate operands when
generating position independent code.

@@ -34285,56 +34711,57 @@ File: gccint.info, Node: File Framework, Next: Data Output, Up: Assembler For
This describes the overall framework of an assembly file.
-- Target Hook: void TARGET_ASM_FILE_START (void)
- Output to 'asm_out_file' any text which the assembler expects to
+ Output to `asm_out_file' any text which the assembler expects to
find at the beginning of a file. The default behavior is
controlled by two flags, documented below. Unless your target's
- assembler is quite unusual, if you override the default, you should
- call 'default_file_start' at some point in your target hook. This
- lets other target files rely on these variables.
+ assembler is quite unusual, if you override the default, you
+ should call `default_file_start' at some point in your target
+ hook. This lets other target files rely on these variables.
-- Target Hook: bool TARGET_ASM_FILE_START_APP_OFF
- If this flag is true, the text of the macro 'ASM_APP_OFF' will be
+ If this flag is true, the text of the macro `ASM_APP_OFF' will be
printed as the very first line in the assembly file, unless
- '-fverbose-asm' is in effect. (If that macro has been defined to
+ `-fverbose-asm' is in effect. (If that macro has been defined to
the empty string, this variable has no effect.) With the normal
- definition of 'ASM_APP_OFF', the effect is to notify the GNU
+ definition of `ASM_APP_OFF', the effect is to notify the GNU
assembler that it need not bother stripping comments or extra
whitespace from its input. This allows it to work a bit faster.
The default is false. You should not set it to true unless you
- have verified that your port does not generate any extra whitespace
- or comments that will cause GAS to issue errors in NO_APP mode.
+ have verified that your port does not generate any extra
+ whitespace or comments that will cause GAS to issue errors in
+ NO_APP mode.
-- Target Hook: bool TARGET_ASM_FILE_START_FILE_DIRECTIVE
- If this flag is true, 'output_file_directive' will be called for
- the primary source file, immediately after printing 'ASM_APP_OFF'
+ If this flag is true, `output_file_directive' will be called for
+ the primary source file, immediately after printing `ASM_APP_OFF'
(if that is enabled). Most ELF assemblers expect this to be done.
The default is false.
-- Target Hook: void TARGET_ASM_FILE_END (void)
- Output to 'asm_out_file' any text which the assembler expects to
+ Output to `asm_out_file' any text which the assembler expects to
find at the end of a file. The default is to output nothing.
-- Function: void file_end_indicate_exec_stack ()
- Some systems use a common convention, the '.note.GNU-stack' special
- section, to indicate whether or not an object file relies on the
- stack being executable. If your system uses this convention, you
- should define 'TARGET_ASM_FILE_END' to this function. If you need
- to do other things in that hook, have your hook function call this
- function.
+ Some systems use a common convention, the `.note.GNU-stack'
+ special section, to indicate whether or not an object file relies
+ on the stack being executable. If your system uses this
+ convention, you should define `TARGET_ASM_FILE_END' to this
+ function. If you need to do other things in that hook, have your
+ hook function call this function.
-- Target Hook: void TARGET_ASM_LTO_START (void)
- Output to 'asm_out_file' any text which the assembler expects to
+ Output to `asm_out_file' any text which the assembler expects to
find at the start of an LTO section. The default is to output
nothing.
-- Target Hook: void TARGET_ASM_LTO_END (void)
- Output to 'asm_out_file' any text which the assembler expects to
+ Output to `asm_out_file' any text which the assembler expects to
find at the end of an LTO section. The default is to output
nothing.
-- Target Hook: void TARGET_ASM_CODE_END (void)
- Output to 'asm_out_file' any text which is needed before emitting
+ Output to `asm_out_file' any text which is needed before emitting
unwind info and debug info at the end of a file. Some targets emit
here PIC setup thunks that cannot be emitted at the end of file,
because they couldn't have unwind info then. The default is to
@@ -34342,20 +34769,20 @@ This describes the overall framework of an assembly file.
-- Macro: ASM_COMMENT_START
A C string constant describing how to begin a comment in the target
- assembler language. The compiler assumes that the comment will end
- at the end of the line.
+ assembler language. The compiler assumes that the comment will
+ end at the end of the line.
-- Macro: ASM_APP_ON
- A C string constant for text to be output before each 'asm'
- statement or group of consecutive ones. Normally this is '"#APP"',
- which is a comment that has no effect on most assemblers but tells
- the GNU assembler that it must check the lines that follow for all
- valid assembler constructs.
+ A C string constant for text to be output before each `asm'
+ statement or group of consecutive ones. Normally this is
+ `"#APP"', which is a comment that has no effect on most assemblers
+ but tells the GNU assembler that it must check the lines that
+ follow for all valid assembler constructs.
-- Macro: ASM_APP_OFF
- A C string constant for text to be output after each 'asm'
+ A C string constant for text to be output after each `asm'
statement or group of consecutive ones. Normally this is
- '"#NO_APP"', which tells the GNU assembler to resume making the
+ `"#NO_APP"', which tells the GNU assembler to resume making the
time-saving assumptions that are valid for ordinary compiler
output.
@@ -34373,37 +34800,37 @@ This describes the overall framework of an assembly file.
indicates that filename NAME is the current source file to the
stdio stream FILE.
- This target hook need not be defined if the standard form of output
- for the file format in use is appropriate.
+ This target hook need not be defined if the standard form of
+ output for the file format in use is appropriate.
-- Target Hook: void TARGET_ASM_OUTPUT_IDENT (const char *NAME)
- Output a string based on NAME, suitable for the '#ident' directive,
- or the equivalent directive or pragma in non-C-family languages.
- If this hook is not defined, nothing is output for the '#ident'
- directive.
+ Output a string based on NAME, suitable for the `#ident'
+ directive, or the equivalent directive or pragma in non-C-family
+ languages. If this hook is not defined, nothing is output for the
+ `#ident' directive.
-- Macro: OUTPUT_QUOTED_STRING (STREAM, STRING)
A C statement to output the string STRING to the stdio stream
- STREAM. If you do not call the function 'output_quoted_string' in
- your config files, GCC will only call it to output filenames to the
- assembler source. So you can use it to canonicalize the format of
- the filename using this macro.
+ STREAM. If you do not call the function `output_quoted_string' in
+ your config files, GCC will only call it to output filenames to
+ the assembler source. So you can use it to canonicalize the format
+ of the filename using this macro.
-- Target Hook: void TARGET_ASM_NAMED_SECTION (const char *NAME,
unsigned int FLAGS, tree DECL)
Output assembly directives to switch to section NAME. The section
should have attributes as specified by FLAGS, which is a bit mask
- of the 'SECTION_*' flags defined in 'output.h'. If DECL is
- non-NULL, it is the 'VAR_DECL' or 'FUNCTION_DECL' with which this
+ of the `SECTION_*' flags defined in `output.h'. If DECL is
+ non-NULL, it is the `VAR_DECL' or `FUNCTION_DECL' with which this
section is associated.
-- Target Hook: section * TARGET_ASM_FUNCTION_SECTION (tree DECL, enum
node_frequency FREQ, bool STARTUP, bool EXIT)
- Return preferred text (sub)section for function DECL. Main purpose
- of this function is to separate cold, normal and hot functions.
- STARTUP is true when function is known to be used only at startup
- (from static constructors or it is 'main()'). EXIT is true when
- function is known to be used only at exit (from static
+ Return preferred text (sub)section for function DECL. Main
+ purpose of this function is to separate cold, normal and hot
+ functions. STARTUP is true when function is known to be used only
+ at startup (from static constructors or it is `main()'). EXIT is
+ true when function is known to be used only at exit (from static
destructors). Return NULL if function should go to default text
section.
@@ -34411,32 +34838,32 @@ This describes the overall framework of an assembly file.
*FILE, tree DECL, bool NEW_IS_COLD)
Used by the target to emit any assembler directives or additional
labels needed when a function is partitioned between different
- sections. Output should be written to FILE. The function decl is
- available as DECL and the new section is 'cold' if NEW_IS_COLD is
- 'true'.
+ sections. Output should be written to FILE. The function decl
+ is available as DECL and the new section is `cold' if NEW_IS_COLD
+ is `true'.
-- Common Target Hook: bool TARGET_HAVE_NAMED_SECTIONS
This flag is true if the target supports
- 'TARGET_ASM_NAMED_SECTION'. It must not be modified by
+ `TARGET_ASM_NAMED_SECTION'. It must not be modified by
command-line option processing.
-- Target Hook: bool TARGET_HAVE_SWITCHABLE_BSS_SECTIONS
This flag is true if we can create zeroed data by switching to a
- BSS section and then using 'ASM_OUTPUT_SKIP' to allocate the space.
+ BSS section and then using `ASM_OUTPUT_SKIP' to allocate the space.
This is true on most ELF targets.
-- Target Hook: unsigned int TARGET_SECTION_TYPE_FLAGS (tree DECL,
const char *NAME, int RELOC)
Choose a set of section attributes for use by
- 'TARGET_ASM_NAMED_SECTION' based on a variable or function decl, a
+ `TARGET_ASM_NAMED_SECTION' based on a variable or function decl, a
section name, and whether or not the declaration's initializer may
contain runtime relocations. DECL may be null, in which case
read-write data should be assumed.
The default version of this function handles choosing code vs data,
- read-only vs read-write data, and 'flag_pic'. You should only need
- to override this if your target has special flags that might be set
- via '__attribute__'.
+ read-only vs read-write data, and `flag_pic'. You should only
+ need to override this if your target has special flags that might
+ be set via `__attribute__'.
-- Target Hook: int TARGET_ASM_RECORD_GCC_SWITCHES (print_switch_type
TYPE, const char *TEXT)
@@ -34445,32 +34872,32 @@ This describes the overall framework of an assembly file.
are enabled. The TYPE argument specifies what is being recorded.
It can take the following values:
- 'SWITCH_TYPE_PASSED'
+ `SWITCH_TYPE_PASSED'
TEXT is a command line switch that has been set by the user.
- 'SWITCH_TYPE_ENABLED'
+ `SWITCH_TYPE_ENABLED'
TEXT is an option which has been enabled. This might be as a
direct result of a command line switch, or because it is
enabled by default or because it has been enabled as a side
effect of a different command line switch. For example, the
- '-O2' switch enables various different individual optimization
- passes.
+ `-O2' switch enables various different individual
+ optimization passes.
- 'SWITCH_TYPE_DESCRIPTIVE'
+ `SWITCH_TYPE_DESCRIPTIVE'
TEXT is either NULL or some descriptive text which should be
ignored. If TEXT is NULL then it is being used to warn the
target hook that either recording is starting or ending. The
first time TYPE is SWITCH_TYPE_DESCRIPTIVE and TEXT is NULL,
- the warning is for start up and the second time the warning is
- for wind down. This feature is to allow the target hook to
- make any necessary preparations before it starts to record
+ the warning is for start up and the second time the warning
+ is for wind down. This feature is to allow the target hook
+ to make any necessary preparations before it starts to record
switches and to perform any necessary tidying up after it has
finished recording switches.
- 'SWITCH_TYPE_LINE_START'
+ `SWITCH_TYPE_LINE_START'
This option can be ignored by this target hook.
- 'SWITCH_TYPE_LINE_END'
+ `SWITCH_TYPE_LINE_END'
This option can be ignored by this target hook.
The hook's return value must be zero. Other return values may be
@@ -34481,11 +34908,11 @@ This describes the overall framework of an assembly file.
it records the switches as ASCII text inside a new, string
mergeable section in the assembler output file. The name of the
new section is provided by the
- 'TARGET_ASM_RECORD_GCC_SWITCHES_SECTION' target hook.
+ `TARGET_ASM_RECORD_GCC_SWITCHES_SECTION' target hook.
-- Target Hook: const char * TARGET_ASM_RECORD_GCC_SWITCHES_SECTION
This is the name of the section that will be created by the example
- ELF implementation of the 'TARGET_ASM_RECORD_GCC_SWITCHES' target
+ ELF implementation of the `TARGET_ASM_RECORD_GCC_SWITCHES' target
hook.

@@ -34504,10 +34931,10 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
-- Target Hook: const char * TARGET_ASM_UNALIGNED_DI_OP
-- Target Hook: const char * TARGET_ASM_UNALIGNED_TI_OP
These hooks specify assembly directives for creating certain kinds
- of integer object. The 'TARGET_ASM_BYTE_OP' directive creates a
- byte-sized object, the 'TARGET_ASM_ALIGNED_HI_OP' one creates an
+ of integer object. The `TARGET_ASM_BYTE_OP' directive creates a
+ byte-sized object, the `TARGET_ASM_ALIGNED_HI_OP' one creates an
aligned two-byte object, and so on. Any of the hooks may be
- 'NULL', indicating that no suitable directive is available.
+ `NULL', indicating that no suitable directive is available.
The compiler will print these strings at the start of a new line,
followed immediately by the object's initial value. In most cases,
@@ -34515,16 +34942,16 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
-- Target Hook: bool TARGET_ASM_INTEGER (rtx X, unsigned int SIZE, int
ALIGNED_P)
- The 'assemble_integer' function uses this hook to output an integer
- object. X is the object's value, SIZE is its size in bytes and
- ALIGNED_P indicates whether it is aligned. The function should
- return 'true' if it was able to output the object. If it returns
- false, 'assemble_integer' will try to split the object into smaller
- parts.
+ The `assemble_integer' function uses this hook to output an
+ integer object. X is the object's value, SIZE is its size in
+ bytes and ALIGNED_P indicates whether it is aligned. The function
+ should return `true' if it was able to output the object. If it
+ returns false, `assemble_integer' will try to split the object
+ into smaller parts.
The default implementation of this hook will use the
- 'TARGET_ASM_BYTE_OP' family of strings, returning 'false' when the
- relevant string is 'NULL'.
+ `TARGET_ASM_BYTE_OP' family of strings, returning `false' when the
+ relevant string is `NULL'.
-- Target Hook: void TARGET_ASM_DECL_END (void)
Define this hook if the target assembler requires a special marker
@@ -34532,35 +34959,35 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
-- Target Hook: bool TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA (FILE *FILE,
rtx X)
- A target hook to recognize RTX patterns that 'output_addr_const'
+ A target hook to recognize RTX patterns that `output_addr_const'
can't deal with, and output assembly code to FILE corresponding to
the pattern X. This may be used to allow machine-dependent
- 'UNSPEC's to appear within constants.
+ `UNSPEC's to appear within constants.
If target hook fails to recognize a pattern, it must return
- 'false', so that a standard error message is printed. If it prints
- an error message itself, by calling, for example,
- 'output_operand_lossage', it may just return 'true'.
+ `false', so that a standard error message is printed. If it
+ prints an error message itself, by calling, for example,
+ `output_operand_lossage', it may just return `true'.
-- Macro: ASM_OUTPUT_ASCII (STREAM, PTR, LEN)
A C statement to output to the stdio stream STREAM an assembler
instruction to assemble a string constant containing the LEN bytes
- at PTR. PTR will be a C expression of type 'char *' and LEN a C
- expression of type 'int'.
+ at PTR. PTR will be a C expression of type `char *' and LEN a C
+ expression of type `int'.
- If the assembler has a '.ascii' pseudo-op as found in the Berkeley
- Unix assembler, do not define the macro 'ASM_OUTPUT_ASCII'.
+ If the assembler has a `.ascii' pseudo-op as found in the Berkeley
+ Unix assembler, do not define the macro `ASM_OUTPUT_ASCII'.
-- Macro: ASM_OUTPUT_FDESC (STREAM, DECL, N)
A C statement to output word N of a function descriptor for DECL.
- This must be defined if 'TARGET_VTABLE_USES_DESCRIPTORS' is
+ This must be defined if `TARGET_VTABLE_USES_DESCRIPTORS' is
defined, and is otherwise unused.
-- Macro: CONSTANT_POOL_BEFORE_FUNCTION
You may define this macro as a C expression. You should define the
expression to have a nonzero value if GCC should output the
- constant pool for a function before the code for the function, or a
- zero value if GCC should output the constant pool after the
+ constant pool for a function before the code for the function, or
+ a zero value if GCC should output the constant pool after the
function. If you do not define this macro, the usual case, GCC
will output the constant pool before the function.
@@ -34575,15 +35002,16 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
If no constant-pool prefix is required, the usual case, this macro
need not be defined.
- -- Macro: ASM_OUTPUT_SPECIAL_POOL_ENTRY (FILE, X, MODE, ALIGN, LABELNO,
- JUMPTO)
+ -- Macro: ASM_OUTPUT_SPECIAL_POOL_ENTRY (FILE, X, MODE, ALIGN,
+ LABELNO, JUMPTO)
A C statement (with or without semicolon) to output a constant in
- the constant pool, if it needs special treatment. (This macro need
- not do anything for RTL expressions that can be output normally.)
+ the constant pool, if it needs special treatment. (This macro
+ need not do anything for RTL expressions that can be output
+ normally.)
The argument FILE is the standard I/O stream to output the
assembler code on. X is the RTL expression for the constant to
- output, and MODE is the machine mode (in case X is a 'const_int').
+ output, and MODE is the machine mode (in case X is a `const_int').
ALIGN is the required alignment for the value X; you should output
an assembler directive to force this much alignment.
@@ -34592,10 +35020,10 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
responsible for outputting the label definition at the proper
place. Here is how to do this:
- (*targetm.asm_out.internal_label) (FILE, "LC", LABELNO);
+ `(*targetm.asm_out.internal_label)' (FILE, "LC", LABELNO);
When you output a pool entry specially, you should end with a
- 'goto' to the label JUMPTO. This will prevent the same pool entry
+ `goto' to the label JUMPTO. This will prevent the same pool entry
from being output a second time in the usual manner.
You need not define this macro if it would do nothing.
@@ -34618,17 +35046,17 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
line separator uses multiple characters.
If you do not define this macro, the default is that only the
- character ';' is treated as a logical line separator.
+ character `;' is treated as a logical line separator.
-- Target Hook: const char * TARGET_ASM_OPEN_PAREN
-- Target Hook: const char * TARGET_ASM_CLOSE_PAREN
- These target hooks are C string constants, describing the syntax in
- the assembler for grouping arithmetic expressions. If not
+ These target hooks are C string constants, describing the syntax
+ in the assembler for grouping arithmetic expressions. If not
overridden, they default to normal parentheses, which is correct
for most assemblers.
- These macros are provided by 'real.h' for writing the definitions of
-'ASM_OUTPUT_DOUBLE' and the like:
+ These macros are provided by `real.h' for writing the definitions of
+`ASM_OUTPUT_DOUBLE' and the like:
-- Macro: REAL_VALUE_TO_TARGET_SINGLE (X, L)
-- Macro: REAL_VALUE_TO_TARGET_DOUBLE (X, L)
@@ -34636,19 +35064,19 @@ File: gccint.info, Node: Data Output, Next: Uninitialized Data, Prev: File Fr
-- Macro: REAL_VALUE_TO_TARGET_DECIMAL32 (X, L)
-- Macro: REAL_VALUE_TO_TARGET_DECIMAL64 (X, L)
-- Macro: REAL_VALUE_TO_TARGET_DECIMAL128 (X, L)
- These translate X, of type 'REAL_VALUE_TYPE', to the target's
+ These translate X, of type `REAL_VALUE_TYPE', to the target's
floating point representation, and store its bit pattern in the
- variable L. For 'REAL_VALUE_TO_TARGET_SINGLE' and
- 'REAL_VALUE_TO_TARGET_DECIMAL32', this variable should be a simple
- 'long int'. For the others, it should be an array of 'long int'.
+ variable L. For `REAL_VALUE_TO_TARGET_SINGLE' and
+ `REAL_VALUE_TO_TARGET_DECIMAL32', this variable should be a simple
+ `long int'. For the others, it should be an array of `long int'.
The number of elements in this array is determined by the size of
the desired target floating point data type: 32 bits of it go in
- each 'long int' array element. Each array element holds 32 bits of
- the result, even if 'long int' is wider than 32 bits on the host
- machine.
+ each `long int' array element. Each array element holds 32 bits
+ of the result, even if `long int' is wider than 32 bits on the
+ host machine.
The array element values are designed so that you can print them
- out using 'fprintf' in the order they should appear in the target
+ out using `fprintf' in the order they should appear in the target
machine's memory.

@@ -34661,11 +35089,11 @@ Each of the macros in this section is used to do the whole job of
outputting a single uninitialized variable.
-- Macro: ASM_OUTPUT_COMMON (STREAM, NAME, SIZE, ROUNDED)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- the assembler definition of a common-label named NAME whose size is
- SIZE bytes. The variable ROUNDED is the size rounded up to
- whatever alignment the caller wants. It is possible that SIZE may
- be zero, for instance if a struct with no other member than a
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM the assembler definition of a common-label named NAME whose
+ size is SIZE bytes. The variable ROUNDED is the size rounded up
+ to whatever alignment the caller wants. It is possible that SIZE
+ may be zero, for instance if a struct with no other member than a
zero-length array is defined. In this case, the backend must
output a symbol definition that allocates at least one byte, both
so that the address of the resulting object does not compare equal
@@ -34673,81 +35101,81 @@ outputting a single uninitialized variable.
the concept of a zero-sized common symbol, as that is how they
represent an ordinary undefined external.
- Use the expression 'assemble_name (STREAM, NAME)' to output the
- name itself; before and after that, output the additional assembler
- syntax for defining the name, and a newline.
+ Use the expression `assemble_name (STREAM, NAME)' to output the
+ name itself; before and after that, output the additional
+ assembler syntax for defining the name, and a newline.
This macro controls how the assembler definitions of uninitialized
common global variables are output.
-- Macro: ASM_OUTPUT_ALIGNED_COMMON (STREAM, NAME, SIZE, ALIGNMENT)
- Like 'ASM_OUTPUT_COMMON' except takes the required alignment as a
+ Like `ASM_OUTPUT_COMMON' except takes the required alignment as a
separate, explicit argument. If you define this macro, it is used
- in place of 'ASM_OUTPUT_COMMON', and gives you more flexibility in
+ in place of `ASM_OUTPUT_COMMON', and gives you more flexibility in
handling the required alignment of the variable. The alignment is
specified as the number of bits.
-- Macro: ASM_OUTPUT_ALIGNED_DECL_COMMON (STREAM, DECL, NAME, SIZE,
ALIGNMENT)
- Like 'ASM_OUTPUT_ALIGNED_COMMON' except that DECL of the variable
- to be output, if there is one, or 'NULL_TREE' if there is no
+ Like `ASM_OUTPUT_ALIGNED_COMMON' except that DECL of the variable
+ to be output, if there is one, or `NULL_TREE' if there is no
corresponding variable. If you define this macro, GCC will use it
- in place of both 'ASM_OUTPUT_COMMON' and
- 'ASM_OUTPUT_ALIGNED_COMMON'. Define this macro when you need to
+ in place of both `ASM_OUTPUT_COMMON' and
+ `ASM_OUTPUT_ALIGNED_COMMON'. Define this macro when you need to
see the variable's decl in order to chose what to output.
-- Macro: ASM_OUTPUT_ALIGNED_BSS (STREAM, DECL, NAME, SIZE, ALIGNMENT)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- the assembler definition of uninitialized global DECL named NAME
- whose size is SIZE bytes. The variable ALIGNMENT is the alignment
- specified as the number of bits.
-
- Try to use function 'asm_output_aligned_bss' defined in file
- 'varasm.c' when defining this macro. If unable, use the expression
- 'assemble_name (STREAM, NAME)' to output the name itself; before
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM the assembler definition of uninitialized global DECL named
+ NAME whose size is SIZE bytes. The variable ALIGNMENT is the
+ alignment specified as the number of bits.
+
+ Try to use function `asm_output_aligned_bss' defined in file
+ `varasm.c' when defining this macro. If unable, use the expression
+ `assemble_name (STREAM, NAME)' to output the name itself; before
and after that, output the additional assembler syntax for defining
the name, and a newline.
There are two ways of handling global BSS. One is to define this
- macro. The other is to have 'TARGET_ASM_SELECT_SECTION' return a
+ macro. The other is to have `TARGET_ASM_SELECT_SECTION' return a
switchable BSS section (*note
TARGET_HAVE_SWITCHABLE_BSS_SECTIONS::). You do not need to do
both.
- Some languages do not have 'common' data, and require a non-common
+ Some languages do not have `common' data, and require a non-common
form of global BSS in order to handle uninitialized globals
efficiently. C++ is one example of this. However, if the target
does not support global BSS, the front end may choose to make
globals common in order to save space in the object file.
-- Macro: ASM_OUTPUT_LOCAL (STREAM, NAME, SIZE, ROUNDED)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- the assembler definition of a local-common-label named NAME whose
- size is SIZE bytes. The variable ROUNDED is the size rounded up to
- whatever alignment the caller wants.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM the assembler definition of a local-common-label named NAME
+ whose size is SIZE bytes. The variable ROUNDED is the size
+ rounded up to whatever alignment the caller wants.
- Use the expression 'assemble_name (STREAM, NAME)' to output the
- name itself; before and after that, output the additional assembler
- syntax for defining the name, and a newline.
+ Use the expression `assemble_name (STREAM, NAME)' to output the
+ name itself; before and after that, output the additional
+ assembler syntax for defining the name, and a newline.
This macro controls how the assembler definitions of uninitialized
static variables are output.
-- Macro: ASM_OUTPUT_ALIGNED_LOCAL (STREAM, NAME, SIZE, ALIGNMENT)
- Like 'ASM_OUTPUT_LOCAL' except takes the required alignment as a
+ Like `ASM_OUTPUT_LOCAL' except takes the required alignment as a
separate, explicit argument. If you define this macro, it is used
- in place of 'ASM_OUTPUT_LOCAL', and gives you more flexibility in
+ in place of `ASM_OUTPUT_LOCAL', and gives you more flexibility in
handling the required alignment of the variable. The alignment is
specified as the number of bits.
-- Macro: ASM_OUTPUT_ALIGNED_DECL_LOCAL (STREAM, DECL, NAME, SIZE,
ALIGNMENT)
- Like 'ASM_OUTPUT_ALIGNED_DECL' except that DECL of the variable to
- be output, if there is one, or 'NULL_TREE' if there is no
+ Like `ASM_OUTPUT_ALIGNED_DECL' except that DECL of the variable to
+ be output, if there is one, or `NULL_TREE' if there is no
corresponding variable. If you define this macro, GCC will use it
- in place of both 'ASM_OUTPUT_DECL' and 'ASM_OUTPUT_ALIGNED_DECL'.
- Define this macro when you need to see the variable's decl in order
- to chose what to output.
+ in place of both `ASM_OUTPUT_DECL' and `ASM_OUTPUT_ALIGNED_DECL'.
+ Define this macro when you need to see the variable's decl in
+ order to chose what to output.

File: gccint.info, Node: Label Output, Next: Initialization, Prev: Uninitialized Data, Up: Assembler Format
@@ -34758,255 +35186,258 @@ File: gccint.info, Node: Label Output, Next: Initialization, Prev: Uninitiali
This is about outputting labels.
-- Macro: ASM_OUTPUT_LABEL (STREAM, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- the assembler definition of a label named NAME. Use the expression
- 'assemble_name (STREAM, NAME)' to output the name itself; before
- and after that, output the additional assembler syntax for defining
- the name, and a newline. A default definition of this macro is
- provided which is correct for most systems.
-
- -- Macro: ASM_OUTPUT_FUNCTION_LABEL (STREAM, NAME, DECL)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- the assembler definition of a label named NAME of a function. Use
- the expression 'assemble_name (STREAM, NAME)' to output the name
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM the assembler definition of a label named NAME. Use the
+ expression `assemble_name (STREAM, NAME)' to output the name
itself; before and after that, output the additional assembler
syntax for defining the name, and a newline. A default definition
of this macro is provided which is correct for most systems.
+ -- Macro: ASM_OUTPUT_FUNCTION_LABEL (STREAM, NAME, DECL)
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM the assembler definition of a label named NAME of a
+ function. Use the expression `assemble_name (STREAM, NAME)' to
+ output the name itself; before and after that, output the
+ additional assembler syntax for defining the name, and a newline.
+ A default definition of this macro is provided which is correct
+ for most systems.
+
If this macro is not defined, then the function name is defined in
- the usual manner as a label (by means of 'ASM_OUTPUT_LABEL').
+ the usual manner as a label (by means of `ASM_OUTPUT_LABEL').
-- Macro: ASM_OUTPUT_INTERNAL_LABEL (STREAM, NAME)
- Identical to 'ASM_OUTPUT_LABEL', except that NAME is known to refer
- to a compiler-generated label. The default definition uses
- 'assemble_name_raw', which is like 'assemble_name' except that it
+ Identical to `ASM_OUTPUT_LABEL', except that NAME is known to
+ refer to a compiler-generated label. The default definition uses
+ `assemble_name_raw', which is like `assemble_name' except that it
is more efficient.
-- Macro: SIZE_ASM_OP
A C string containing the appropriate assembler directive to
specify the size of a symbol, without any arguments. On systems
- that use ELF, the default (in 'config/elfos.h') is '"\t.size\t"';
+ that use ELF, the default (in `config/elfos.h') is `"\t.size\t"';
on other systems, the default is not to define this macro.
Define this macro only if it is correct to use the default
- definitions of 'ASM_OUTPUT_SIZE_DIRECTIVE' and
- 'ASM_OUTPUT_MEASURED_SIZE' for your system. If you need your own
+ definitions of `ASM_OUTPUT_SIZE_DIRECTIVE' and
+ `ASM_OUTPUT_MEASURED_SIZE' for your system. If you need your own
custom definitions of those macros, or if you do not need explicit
symbol sizes at all, do not define this macro.
-- Macro: ASM_OUTPUT_SIZE_DIRECTIVE (STREAM, NAME, SIZE)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- a directive telling the assembler that the size of the symbol NAME
- is SIZE. SIZE is a 'HOST_WIDE_INT'. If you define 'SIZE_ASM_OP',
- a default definition of this macro is provided.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM a directive telling the assembler that the size of the
+ symbol NAME is SIZE. SIZE is a `HOST_WIDE_INT'. If you define
+ `SIZE_ASM_OP', a default definition of this macro is provided.
-- Macro: ASM_OUTPUT_MEASURED_SIZE (STREAM, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- a directive telling the assembler to calculate the size of the
- symbol NAME by subtracting its address from the current address.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM a directive telling the assembler to calculate the size of
+ the symbol NAME by subtracting its address from the current
+ address.
- If you define 'SIZE_ASM_OP', a default definition of this macro is
+ If you define `SIZE_ASM_OP', a default definition of this macro is
provided. The default assumes that the assembler recognizes a
- special '.' symbol as referring to the current address, and can
+ special `.' symbol as referring to the current address, and can
calculate the difference between this and another symbol. If your
- assembler does not recognize '.' or cannot do calculations with it,
- you will need to redefine 'ASM_OUTPUT_MEASURED_SIZE' to use some
- other technique.
+ assembler does not recognize `.' or cannot do calculations with
+ it, you will need to redefine `ASM_OUTPUT_MEASURED_SIZE' to use
+ some other technique.
-- Macro: NO_DOLLAR_IN_LABEL
Define this macro if the assembler does not accept the character
- '$' in label names. By default constructors and destructors in G++
- have '$' in the identifiers. If this macro is defined, '.' is used
- instead.
+ `$' in label names. By default constructors and destructors in
+ G++ have `$' in the identifiers. If this macro is defined, `.' is
+ used instead.
-- Macro: NO_DOT_IN_LABEL
Define this macro if the assembler does not accept the character
- '.' in label names. By default constructors and destructors in G++
- have names that use '.'. If this macro is defined, these names are
- rewritten to avoid '.'.
+ `.' in label names. By default constructors and destructors in G++
+ have names that use `.'. If this macro is defined, these names
+ are rewritten to avoid `.'.
-- Macro: TYPE_ASM_OP
A C string containing the appropriate assembler directive to
specify the type of a symbol, without any arguments. On systems
- that use ELF, the default (in 'config/elfos.h') is '"\t.type\t"';
+ that use ELF, the default (in `config/elfos.h') is `"\t.type\t"';
on other systems, the default is not to define this macro.
Define this macro only if it is correct to use the default
- definition of 'ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you
+ definition of `ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you
need your own custom definition of this macro, or if you do not
need explicit symbol types at all, do not define this macro.
-- Macro: TYPE_OPERAND_FMT
- A C string which specifies (using 'printf' syntax) the format of
- the second operand to 'TYPE_ASM_OP'. On systems that use ELF, the
- default (in 'config/elfos.h') is '"@%s"'; on other systems, the
+ A C string which specifies (using `printf' syntax) the format of
+ the second operand to `TYPE_ASM_OP'. On systems that use ELF, the
+ default (in `config/elfos.h') is `"@%s"'; on other systems, the
default is not to define this macro.
Define this macro only if it is correct to use the default
- definition of 'ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you
+ definition of `ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you
need your own custom definition of this macro, or if you do not
need explicit symbol types at all, do not define this macro.
-- Macro: ASM_OUTPUT_TYPE_DIRECTIVE (STREAM, TYPE)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- a directive telling the assembler that the type of the symbol NAME
- is TYPE. TYPE is a C string; currently, that string is always
- either '"function"' or '"object"', but you should not count on
- this.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM a directive telling the assembler that the type of the
+ symbol NAME is TYPE. TYPE is a C string; currently, that string
+ is always either `"function"' or `"object"', but you should not
+ count on this.
- If you define 'TYPE_ASM_OP' and 'TYPE_OPERAND_FMT', a default
+ If you define `TYPE_ASM_OP' and `TYPE_OPERAND_FMT', a default
definition of this macro is provided.
-- Macro: ASM_DECLARE_FUNCTION_NAME (STREAM, NAME, DECL)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- any text necessary for declaring the name NAME of a function which
- is being defined. This macro is responsible for outputting the
- label definition (perhaps using 'ASM_OUTPUT_FUNCTION_LABEL'). The
- argument DECL is the 'FUNCTION_DECL' tree node representing the
- function.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM any text necessary for declaring the name NAME of a
+ function which is being defined. This macro is responsible for
+ outputting the label definition (perhaps using
+ `ASM_OUTPUT_FUNCTION_LABEL'). The argument DECL is the
+ `FUNCTION_DECL' tree node representing the function.
If this macro is not defined, then the function name is defined in
the usual manner as a label (by means of
- 'ASM_OUTPUT_FUNCTION_LABEL').
+ `ASM_OUTPUT_FUNCTION_LABEL').
- You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' in the definition
+ You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' in the definition
of this macro.
-- Macro: ASM_DECLARE_FUNCTION_SIZE (STREAM, NAME, DECL)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- any text necessary for declaring the size of a function which is
- being defined. The argument NAME is the name of the function. The
- argument DECL is the 'FUNCTION_DECL' tree node representing the
- function.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM any text necessary for declaring the size of a function
+ which is being defined. The argument NAME is the name of the
+ function. The argument DECL is the `FUNCTION_DECL' tree node
+ representing the function.
If this macro is not defined, then the function size is not
defined.
- You may wish to use 'ASM_OUTPUT_MEASURED_SIZE' in the definition of
- this macro.
+ You may wish to use `ASM_OUTPUT_MEASURED_SIZE' in the definition
+ of this macro.
-- Macro: ASM_DECLARE_OBJECT_NAME (STREAM, NAME, DECL)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- any text necessary for declaring the name NAME of an initialized
- variable which is being defined. This macro must output the label
- definition (perhaps using 'ASM_OUTPUT_LABEL'). The argument DECL
- is the 'VAR_DECL' tree node representing the variable.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM any text necessary for declaring the name NAME of an
+ initialized variable which is being defined. This macro must
+ output the label definition (perhaps using `ASM_OUTPUT_LABEL').
+ The argument DECL is the `VAR_DECL' tree node representing the
+ variable.
If this macro is not defined, then the variable name is defined in
- the usual manner as a label (by means of 'ASM_OUTPUT_LABEL').
+ the usual manner as a label (by means of `ASM_OUTPUT_LABEL').
- You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' and/or
- 'ASM_OUTPUT_SIZE_DIRECTIVE' in the definition of this macro.
+ You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' and/or
+ `ASM_OUTPUT_SIZE_DIRECTIVE' in the definition of this macro.
-- Target Hook: void TARGET_ASM_DECLARE_CONSTANT_NAME (FILE *FILE,
const char *NAME, const_tree EXPR, HOST_WIDE_INT SIZE)
A target hook to output to the stdio stream FILE any text necessary
for declaring the name NAME of a constant which is being defined.
- This target hook is responsible for outputting the label definition
- (perhaps using 'assemble_label'). The argument EXP is the value of
- the constant, and SIZE is the size of the constant in bytes. The
- NAME will be an internal label.
+ This target hook is responsible for outputting the label
+ definition (perhaps using `assemble_label'). The argument EXP is
+ the value of the constant, and SIZE is the size of the constant in
+ bytes. The NAME will be an internal label.
The default version of this target hook, define the NAME in the
- usual manner as a label (by means of 'assemble_label').
+ usual manner as a label (by means of `assemble_label').
- You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' in this target
+ You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' in this target
hook.
-- Macro: ASM_DECLARE_REGISTER_GLOBAL (STREAM, DECL, REGNO, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- any text necessary for claiming a register REGNO for a global
- variable DECL with name NAME.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM any text necessary for claiming a register REGNO for a
+ global variable DECL with name NAME.
If you don't define this macro, that is equivalent to defining it
to do nothing.
-- Macro: ASM_FINISH_DECLARE_OBJECT (STREAM, DECL, TOPLEVEL, ATEND)
A C statement (sans semicolon) to finish up declaring a variable
- name once the compiler has processed its initializer fully and thus
- has had a chance to determine the size of an array when controlled
- by an initializer. This is used on systems where it's necessary to
- declare something about the size of the object.
+ name once the compiler has processed its initializer fully and
+ thus has had a chance to determine the size of an array when
+ controlled by an initializer. This is used on systems where it's
+ necessary to declare something about the size of the object.
If you don't define this macro, that is equivalent to defining it
to do nothing.
- You may wish to use 'ASM_OUTPUT_SIZE_DIRECTIVE' and/or
- 'ASM_OUTPUT_MEASURED_SIZE' in the definition of this macro.
+ You may wish to use `ASM_OUTPUT_SIZE_DIRECTIVE' and/or
+ `ASM_OUTPUT_MEASURED_SIZE' in the definition of this macro.
-- Target Hook: void TARGET_ASM_GLOBALIZE_LABEL (FILE *STREAM, const
char *NAME)
- This target hook is a function to output to the stdio stream STREAM
- some commands that will make the label NAME global; that is,
- available for reference from other files.
+ This target hook is a function to output to the stdio stream
+ STREAM some commands that will make the label NAME global; that
+ is, available for reference from other files.
The default implementation relies on a proper definition of
- 'GLOBAL_ASM_OP'.
+ `GLOBAL_ASM_OP'.
- -- Target Hook: void TARGET_ASM_GLOBALIZE_DECL_NAME (FILE *STREAM, tree
- DECL)
- This target hook is a function to output to the stdio stream STREAM
- some commands that will make the name associated with DECL global;
- that is, available for reference from other files.
+ -- Target Hook: void TARGET_ASM_GLOBALIZE_DECL_NAME (FILE *STREAM,
+ tree DECL)
+ This target hook is a function to output to the stdio stream
+ STREAM some commands that will make the name associated with DECL
+ global; that is, available for reference from other files.
The default implementation uses the TARGET_ASM_GLOBALIZE_LABEL
target hook.
-- Target Hook: void TARGET_ASM_ASSEMBLE_UNDEFINED_DECL (FILE *STREAM,
const char *NAME, const_tree DECL)
- This target hook is a function to output to the stdio stream STREAM
- some commands that will declare the name associated with DECL which
- is not defined in the current translation unit. Most assemblers do
- not require anything to be output in this case.
+ This target hook is a function to output to the stdio stream
+ STREAM some commands that will declare the name associated with
+ DECL which is not defined in the current translation unit. Most
+ assemblers do not require anything to be output in this case.
-- Macro: ASM_WEAKEN_LABEL (STREAM, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- some commands that will make the label NAME weak; that is,
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM some commands that will make the label NAME weak; that is,
available for reference from other files but only used if no other
- definition is available. Use the expression 'assemble_name
+ definition is available. Use the expression `assemble_name
(STREAM, NAME)' to output the name itself; before and after that,
output the additional assembler syntax for making that name weak,
and a newline.
- If you don't define this macro or 'ASM_WEAKEN_DECL', GCC will not
- support weak symbols and you should not define the 'SUPPORTS_WEAK'
+ If you don't define this macro or `ASM_WEAKEN_DECL', GCC will not
+ support weak symbols and you should not define the `SUPPORTS_WEAK'
macro.
-- Macro: ASM_WEAKEN_DECL (STREAM, DECL, NAME, VALUE)
- Combines (and replaces) the function of 'ASM_WEAKEN_LABEL' and
- 'ASM_OUTPUT_WEAK_ALIAS', allowing access to the associated function
- or variable decl. If VALUE is not 'NULL', this C statement should
+ Combines (and replaces) the function of `ASM_WEAKEN_LABEL' and
+ `ASM_OUTPUT_WEAK_ALIAS', allowing access to the associated function
+ or variable decl. If VALUE is not `NULL', this C statement should
output to the stdio stream STREAM assembler code which defines
(equates) the weak symbol NAME to have the value VALUE. If VALUE
- is 'NULL', it should output commands to make NAME weak.
+ is `NULL', it should output commands to make NAME weak.
-- Macro: ASM_OUTPUT_WEAKREF (STREAM, DECL, NAME, VALUE)
- Outputs a directive that enables NAME to be used to refer to symbol
- VALUE with weak-symbol semantics. 'decl' is the declaration of
- 'name'.
+ Outputs a directive that enables NAME to be used to refer to
+ symbol VALUE with weak-symbol semantics. `decl' is the
+ declaration of `name'.
-- Macro: SUPPORTS_WEAK
A preprocessor constant expression which evaluates to true if the
target supports weak symbols.
- If you don't define this macro, 'defaults.h' provides a default
- definition. If either 'ASM_WEAKEN_LABEL' or 'ASM_WEAKEN_DECL' is
- defined, the default definition is '1'; otherwise, it is '0'.
+ If you don't define this macro, `defaults.h' provides a default
+ definition. If either `ASM_WEAKEN_LABEL' or `ASM_WEAKEN_DECL' is
+ defined, the default definition is `1'; otherwise, it is `0'.
-- Macro: TARGET_SUPPORTS_WEAK
A C expression which evaluates to true if the target supports weak
symbols.
- If you don't define this macro, 'defaults.h' provides a default
- definition. The default definition is '(SUPPORTS_WEAK)'. Define
+ If you don't define this macro, `defaults.h' provides a default
+ definition. The default definition is `(SUPPORTS_WEAK)'. Define
this macro if you want to control weak symbol support with a
- compiler flag such as '-melf'.
+ compiler flag such as `-melf'.
-- Macro: MAKE_DECL_ONE_ONLY (DECL)
A C statement (sans semicolon) to mark DECL to be emitted as a
public symbol such that extra copies in multiple translation units
will be discarded by the linker. Define this macro if your object
- file format provides support for this concept, such as the 'COMDAT'
+ file format provides support for this concept, such as the `COMDAT'
section flags in the Microsoft Windows PE/COFF format, and this
support requires changes to DECL, such as putting it in a separate
section.
@@ -35015,11 +35446,11 @@ This is about outputting labels.
A C expression which evaluates to true if the target supports
one-only semantics.
- If you don't define this macro, 'varasm.c' provides a default
- definition. If 'MAKE_DECL_ONE_ONLY' is defined, the default
- definition is '1'; otherwise, it is '0'. Define this macro if you
+ If you don't define this macro, `varasm.c' provides a default
+ definition. If `MAKE_DECL_ONE_ONLY' is defined, the default
+ definition is `1'; otherwise, it is `0'. Define this macro if you
want to control one-only symbol support with a compiler flag, or if
- setting the 'DECL_ONE_ONLY' flag is enough to mark a declaration to
+ setting the `DECL_ONE_ONLY' flag is enough to mark a declaration to
be emitted as one-only.
-- Target Hook: void TARGET_ASM_ASSEMBLE_VISIBILITY (tree DECL, int
@@ -35031,38 +35462,38 @@ This is about outputting labels.
-- Macro: TARGET_WEAK_NOT_IN_ARCHIVE_TOC
A C expression that evaluates to true if the target's linker
- expects that weak symbols do not appear in a static archive's table
- of contents. The default is '0'.
+ expects that weak symbols do not appear in a static archive's
+ table of contents. The default is `0'.
Leaving weak symbols out of an archive's table of contents means
that, if a symbol will only have a definition in one translation
unit and will have undefined references from other translation
units, that symbol should not be weak. Defining this macro to be
nonzero will thus have the effect that certain symbols that would
- normally be weak (explicit template instantiations, and vtables for
- polymorphic classes with noninline key methods) will instead be
- nonweak.
+ normally be weak (explicit template instantiations, and vtables
+ for polymorphic classes with noninline key methods) will instead
+ be nonweak.
The C++ ABI requires this macro to be zero. Define this macro for
targets where full C++ ABI compliance is impossible and where
- linker restrictions require weak symbols to be left out of a static
- archive's table of contents.
+ linker restrictions require weak symbols to be left out of a
+ static archive's table of contents.
-- Macro: ASM_OUTPUT_EXTERNAL (STREAM, DECL, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- any text necessary for declaring the name of an external symbol
- named NAME which is referenced in this compilation but not defined.
- The value of DECL is the tree node for the declaration.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM any text necessary for declaring the name of an external
+ symbol named NAME which is referenced in this compilation but not
+ defined. The value of DECL is the tree node for the declaration.
This macro need not be defined if it does not need to output
- anything. The GNU assembler and most Unix assemblers don't require
- anything.
+ anything. The GNU assembler and most Unix assemblers don't
+ require anything.
-- Target Hook: void TARGET_ASM_EXTERNAL_LIBCALL (rtx SYMREF)
This target hook is a function to output to ASM_OUT_FILE an
assembler pseudo-op to declare a library function name external.
The name of the library function is given by SYMREF, which is a
- 'symbol_ref'.
+ `symbol_ref'.
-- Target Hook: void TARGET_ASM_MARK_DECL_PRESERVED (const char
*SYMBOL)
@@ -35071,35 +35502,35 @@ This is about outputting labels.
uses the .no_dead_code_strip directive.
-- Macro: ASM_OUTPUT_LABELREF (STREAM, NAME)
- A C statement (sans semicolon) to output to the stdio stream STREAM
- a reference in assembler syntax to a label named NAME. This should
- add '_' to the front of the name, if that is customary on your
- operating system, as it is in most Berkeley Unix systems. This
- macro is used in 'assemble_name'.
+ A C statement (sans semicolon) to output to the stdio stream
+ STREAM a reference in assembler syntax to a label named NAME.
+ This should add `_' to the front of the name, if that is customary
+ on your operating system, as it is in most Berkeley Unix systems.
+ This macro is used in `assemble_name'.
-- Target Hook: tree TARGET_MANGLE_ASSEMBLER_NAME (const char *NAME)
- Given a symbol NAME, perform same mangling as 'varasm.c''s
- 'assemble_name', but in memory rather than to a file stream,
- returning result as an 'IDENTIFIER_NODE'. Required for correct LTO
- symtabs. The default implementation calls the
- 'TARGET_STRIP_NAME_ENCODING' hook and then prepends the
- 'USER_LABEL_PREFIX', if any.
+ Given a symbol NAME, perform same mangling as `varasm.c''s
+ `assemble_name', but in memory rather than to a file stream,
+ returning result as an `IDENTIFIER_NODE'. Required for correct
+ LTO symtabs. The default implementation calls the
+ `TARGET_STRIP_NAME_ENCODING' hook and then prepends the
+ `USER_LABEL_PREFIX', if any.
-- Macro: ASM_OUTPUT_SYMBOL_REF (STREAM, SYM)
A C statement (sans semicolon) to output a reference to
- 'SYMBOL_REF' SYM. If not defined, 'assemble_name' will be used to
+ `SYMBOL_REF' SYM. If not defined, `assemble_name' will be used to
output the name of the symbol. This macro may be used to modify
the way a symbol is referenced depending on information encoded by
- 'TARGET_ENCODE_SECTION_INFO'.
+ `TARGET_ENCODE_SECTION_INFO'.
-- Macro: ASM_OUTPUT_LABEL_REF (STREAM, BUF)
A C statement (sans semicolon) to output a reference to BUF, the
- result of 'ASM_GENERATE_INTERNAL_LABEL'. If not defined,
- 'assemble_name' will be used to output the name of the symbol.
- This macro is not used by 'output_asm_label', or the '%l' specifier
- that calls it; the intention is that this macro should be set when
- it is necessary to output a label differently when its address is
- being taken.
+ result of `ASM_GENERATE_INTERNAL_LABEL'. If not defined,
+ `assemble_name' will be used to output the name of the symbol.
+ This macro is not used by `output_asm_label', or the `%l'
+ specifier that calls it; the intention is that this macro should
+ be set when it is necessary to output a label differently when its
+ address is being taken.
-- Target Hook: void TARGET_ASM_INTERNAL_LABEL (FILE *STREAM, const
char *PREFIX, unsigned long LABELNO)
@@ -35110,50 +35541,50 @@ This is about outputting labels.
labels used for user-level functions and variables. Otherwise,
certain programs will have name conflicts with internal labels.
- It is desirable to exclude internal labels from the symbol table of
- the object file. Most assemblers have a naming convention for
- labels that should be excluded; on many systems, the letter 'L' at
+ It is desirable to exclude internal labels from the symbol table
+ of the object file. Most assemblers have a naming convention for
+ labels that should be excluded; on many systems, the letter `L' at
the beginning of a label has this effect. You should find out what
convention your system uses, and follow it.
The default version of this function utilizes
- 'ASM_GENERATE_INTERNAL_LABEL'.
+ `ASM_GENERATE_INTERNAL_LABEL'.
-- Macro: ASM_OUTPUT_DEBUG_LABEL (STREAM, PREFIX, NUM)
A C statement to output to the stdio stream STREAM a debug info
- label whose name is made from the string PREFIX and the number NUM.
- This is useful for VLIW targets, where debug info labels may need
- to be treated differently than branch target labels. On some
+ label whose name is made from the string PREFIX and the number
+ NUM. This is useful for VLIW targets, where debug info labels may
+ need to be treated differently than branch target labels. On some
systems, branch target labels must be at the beginning of
instruction bundles, but debug info labels can occur in the middle
of instruction bundles.
If this macro is not defined, then
- '(*targetm.asm_out.internal_label)' will be used.
+ `(*targetm.asm_out.internal_label)' will be used.
-- Macro: ASM_GENERATE_INTERNAL_LABEL (STRING, PREFIX, NUM)
- A C statement to store into the string STRING a label whose name is
- made from the string PREFIX and the number NUM.
+ A C statement to store into the string STRING a label whose name
+ is made from the string PREFIX and the number NUM.
- This string, when output subsequently by 'assemble_name', should
- produce the output that '(*targetm.asm_out.internal_label)' would
+ This string, when output subsequently by `assemble_name', should
+ produce the output that `(*targetm.asm_out.internal_label)' would
produce with the same PREFIX and NUM.
- If the string begins with '*', then 'assemble_name' will output the
- rest of the string unchanged. It is often convenient for
- 'ASM_GENERATE_INTERNAL_LABEL' to use '*' in this way. If the
- string doesn't start with '*', then 'ASM_OUTPUT_LABELREF' gets to
+ If the string begins with `*', then `assemble_name' will output
+ the rest of the string unchanged. It is often convenient for
+ `ASM_GENERATE_INTERNAL_LABEL' to use `*' in this way. If the
+ string doesn't start with `*', then `ASM_OUTPUT_LABELREF' gets to
output the string, and may change it. (Of course,
- 'ASM_OUTPUT_LABELREF' is also part of your machine description, so
+ `ASM_OUTPUT_LABELREF' is also part of your machine description, so
you should know what it does on your machine.)
-- Macro: ASM_FORMAT_PRIVATE_NAME (OUTVAR, NAME, NUMBER)
A C expression to assign to OUTVAR (which is a variable of type
- 'char *') a newly allocated string made from the string NAME and
+ `char *') a newly allocated string made from the string NAME and
the number NUMBER, with some suitable punctuation added. Use
- 'alloca' to get space for the string.
+ `alloca' to get space for the string.
- The string will be used as an argument to 'ASM_OUTPUT_LABELREF' to
+ The string will be used as an argument to `ASM_OUTPUT_LABELREF' to
produce an assembler label for an internal static variable whose
name is NAME. Therefore, the string must be such as to result in
valid assembler code. The argument NUMBER is different each time
@@ -35162,8 +35593,8 @@ This is about outputting labels.
Ideally this string should not be a valid C identifier, to prevent
any conflict with the user's own symbols. Most assemblers allow
- periods or percent signs in assembler symbols; putting at least one
- of these between the name and the number will suffice.
+ periods or percent signs in assembler symbols; putting at least
+ one of these between the name and the number will suffice.
If this macro is not defined, a default definition will be provided
which is correct for most systems.
@@ -35172,7 +35603,7 @@ This is about outputting labels.
A C statement to output to the stdio stream STREAM assembler code
which defines (equates) the symbol NAME to have the value VALUE.
- If 'SET_ASM_OP' is defined, a default definition is provided which
+ If `SET_ASM_OP' is defined, a default definition is provided which
is correct for most systems.
-- Macro: ASM_OUTPUT_DEF_FROM_DECLS (STREAM, DECL_OF_NAME,
@@ -35180,10 +35611,10 @@ This is about outputting labels.
A C statement to output to the stdio stream STREAM assembler code
which defines (equates) the symbol whose tree node is DECL_OF_NAME
to have the value of the tree node DECL_OF_VALUE. This macro will
- be used in preference to 'ASM_OUTPUT_DEF' if it is defined and if
+ be used in preference to `ASM_OUTPUT_DEF' if it is defined and if
the tree nodes are available.
- If 'SET_ASM_OP' is defined, a default definition is provided which
+ If `SET_ASM_OP' is defined, a default definition is provided which
is correct for most systems.
-- Macro: TARGET_DEFERRED_OUTPUT_DEFS (DECL_OF_NAME, DECL_OF_VALUE)
@@ -35192,16 +35623,16 @@ This is about outputting labels.
have the value of the tree node DECL_OF_VALUE should be emitted
near the end of the current compilation unit. The default is to
not defer output of defines. This macro affects defines output by
- 'ASM_OUTPUT_DEF' and 'ASM_OUTPUT_DEF_FROM_DECLS'.
+ `ASM_OUTPUT_DEF' and `ASM_OUTPUT_DEF_FROM_DECLS'.
-- Macro: ASM_OUTPUT_WEAK_ALIAS (STREAM, NAME, VALUE)
A C statement to output to the stdio stream STREAM assembler code
which defines (equates) the weak symbol NAME to have the value
- VALUE. If VALUE is 'NULL', it defines NAME as an undefined weak
+ VALUE. If VALUE is `NULL', it defines NAME as an undefined weak
symbol.
Define this macro if the target only supports weak aliases; define
- 'ASM_OUTPUT_DEF' instead if possible.
+ `ASM_OUTPUT_DEF' instead if possible.
-- Macro: OBJC_GEN_METHOD_LABEL (BUF, IS_INST, CLASS_NAME, CAT_NAME,
SEL_NAME)
@@ -35209,25 +35640,25 @@ This is about outputting labels.
Objective-C methods.
The default name is a unique method number followed by the name of
- the class (e.g. '_1_Foo'). For methods in categories, the name of
+ the class (e.g. `_1_Foo'). For methods in categories, the name of
the category is also included in the assembler name (e.g.
- '_1_Foo_Bar').
+ `_1_Foo_Bar').
These names are safe on most systems, but make debugging difficult
- since the method's selector is not present in the name. Therefore,
- particular systems define other ways of computing names.
+ since the method's selector is not present in the name.
+ Therefore, particular systems define other ways of computing names.
- BUF is an expression of type 'char *' which gives you a buffer in
+ BUF is an expression of type `char *' which gives you a buffer in
which to store the name; its length is as long as CLASS_NAME,
CAT_NAME and SEL_NAME put together, plus 50 characters extra.
The argument IS_INST specifies whether the method is an instance
method or a class method; CLASS_NAME is the name of the class;
- CAT_NAME is the name of the category (or 'NULL' if the method is
+ CAT_NAME is the name of the category (or `NULL' if the method is
not in a category); and SEL_NAME is the name of the selector.
- On systems where the assembler can handle quoted names, you can use
- this macro to provide more human-readable names.
+ On systems where the assembler can handle quoted names, you can
+ use this macro to provide more human-readable names.

File: gccint.info, Node: Initialization, Next: Macros for Initialization, Prev: Label Output, Up: Assembler Format
@@ -35238,7 +35669,7 @@ File: gccint.info, Node: Initialization, Next: Macros for Initialization, Pre
The compiled code for certain languages includes "constructors" (also
called "initialization routines")--functions to initialize data in the
program when the program is started. These functions need to be called
-before the program is "started"--that is to say, before 'main' is
+before the program is "started"--that is to say, before `main' is
called.
Compiling some languages generates "destructors" (also called
@@ -35255,8 +35686,8 @@ initialization and termination functions. Each way has two variants.
Much of the structure is common to all four variations.
The linker must build two lists of these functions--a list of
-initialization functions, called '__CTOR_LIST__', and a list of
-termination functions, called '__DTOR_LIST__'.
+initialization functions, called `__CTOR_LIST__', and a list of
+termination functions, called `__DTOR_LIST__'.
Each list always begins with an ignored function pointer (which may
hold 0, -1, or a count of the function pointers after it, depending on
@@ -35265,81 +35696,81 @@ pointers to constructors (or destructors), followed by a function
pointer containing zero.
Depending on the operating system and its executable file format,
-either 'crtstuff.c' or 'libgcc2.c' traverses these lists at startup time
-and exit time. Constructors are called in reverse order of the list;
-destructors in forward order.
+either `crtstuff.c' or `libgcc2.c' traverses these lists at startup
+time and exit time. Constructors are called in reverse order of the
+list; destructors in forward order.
The best way to handle static constructors works only for object file
formats which provide arbitrarily-named sections. A section is set
aside for a list of constructors, and another for a list of destructors.
-Traditionally these are called '.ctors' and '.dtors'. Each object file
+Traditionally these are called `.ctors' and `.dtors'. Each object file
that defines an initialization function also puts a word in the
constructor section to point to that function. The linker accumulates
-all these words into one contiguous '.ctors' section. Termination
+all these words into one contiguous `.ctors' section. Termination
functions are handled similarly.
- This method will be chosen as the default by 'target-def.h' if
-'TARGET_ASM_NAMED_SECTION' is defined. A target that does not support
+ This method will be chosen as the default by `target-def.h' if
+`TARGET_ASM_NAMED_SECTION' is defined. A target that does not support
arbitrary sections, but does support special designated constructor and
-destructor sections may define 'CTORS_SECTION_ASM_OP' and
-'DTORS_SECTION_ASM_OP' to achieve the same effect.
+destructor sections may define `CTORS_SECTION_ASM_OP' and
+`DTORS_SECTION_ASM_OP' to achieve the same effect.
When arbitrary sections are available, there are two variants,
-depending upon how the code in 'crtstuff.c' is called. On systems that
-support a ".init" section which is executed at program startup, parts of
-'crtstuff.c' are compiled into that section. The program is linked by
-the 'gcc' driver like this:
+depending upon how the code in `crtstuff.c' is called. On systems that
+support a ".init" section which is executed at program startup, parts
+of `crtstuff.c' are compiled into that section. The program is linked
+by the `gcc' driver like this:
ld -o OUTPUT_FILE crti.o crtbegin.o ... -lgcc crtend.o crtn.o
- The prologue of a function ('__init') appears in the '.init' section of
-'crti.o'; the epilogue appears in 'crtn.o'. Likewise for the function
-'__fini' in the ".fini" section. Normally these files are provided by
-the operating system or by the GNU C library, but are provided by GCC
-for a few targets.
+ The prologue of a function (`__init') appears in the `.init' section
+of `crti.o'; the epilogue appears in `crtn.o'. Likewise for the
+function `__fini' in the ".fini" section. Normally these files are
+provided by the operating system or by the GNU C library, but are
+provided by GCC for a few targets.
- The objects 'crtbegin.o' and 'crtend.o' are (for most targets) compiled
-from 'crtstuff.c'. They contain, among other things, code fragments
-within the '.init' and '.fini' sections that branch to routines in the
-'.text' section. The linker will pull all parts of a section together,
-which results in a complete '__init' function that invokes the routines
-we need at startup.
+ The objects `crtbegin.o' and `crtend.o' are (for most targets)
+compiled from `crtstuff.c'. They contain, among other things, code
+fragments within the `.init' and `.fini' sections that branch to
+routines in the `.text' section. The linker will pull all parts of a
+section together, which results in a complete `__init' function that
+invokes the routines we need at startup.
- To use this variant, you must define the 'INIT_SECTION_ASM_OP' macro
+ To use this variant, you must define the `INIT_SECTION_ASM_OP' macro
properly.
If no init section is available, when GCC compiles any function called
-'main' (or more accurately, any function designated as a program entry
-point by the language front end calling 'expand_main_function'), it
-inserts a procedure call to '__main' as the first executable code after
-the function prologue. The '__main' function is defined in 'libgcc2.c'
+`main' (or more accurately, any function designated as a program entry
+point by the language front end calling `expand_main_function'), it
+inserts a procedure call to `__main' as the first executable code after
+the function prologue. The `__main' function is defined in `libgcc2.c'
and runs the global constructors.
In file formats that don't support arbitrary sections, there are again
-two variants. In the simplest variant, the GNU linker (GNU 'ld') and an
-'a.out' format must be used. In this case, 'TARGET_ASM_CONSTRUCTOR' is
-defined to produce a '.stabs' entry of type 'N_SETT', referencing the
-name '__CTOR_LIST__', and with the address of the void function
+two variants. In the simplest variant, the GNU linker (GNU `ld') and
+an `a.out' format must be used. In this case, `TARGET_ASM_CONSTRUCTOR'
+is defined to produce a `.stabs' entry of type `N_SETT', referencing
+the name `__CTOR_LIST__', and with the address of the void function
containing the initialization code as its value. The GNU linker
-recognizes this as a request to add the value to a "set"; the values are
-accumulated, and are eventually placed in the executable as a vector in
-the format described above, with a leading (ignored) count and a
-trailing zero element. 'TARGET_ASM_DESTRUCTOR' is handled similarly.
-Since no init section is available, the absence of 'INIT_SECTION_ASM_OP'
-causes the compilation of 'main' to call '__main' as above, starting the
-initialization process.
+recognizes this as a request to add the value to a "set"; the values
+are accumulated, and are eventually placed in the executable as a
+vector in the format described above, with a leading (ignored) count
+and a trailing zero element. `TARGET_ASM_DESTRUCTOR' is handled
+similarly. Since no init section is available, the absence of
+`INIT_SECTION_ASM_OP' causes the compilation of `main' to call `__main'
+as above, starting the initialization process.
The last variant uses neither arbitrary sections nor the GNU linker.
This is preferable when you want to do dynamic linking and when using
-file formats which the GNU linker does not support, such as 'ECOFF'. In
-this case, 'TARGET_HAVE_CTORS_DTORS' is false, initialization and
+file formats which the GNU linker does not support, such as `ECOFF'. In
+this case, `TARGET_HAVE_CTORS_DTORS' is false, initialization and
termination functions are recognized simply by their names. This
-requires an extra program in the linkage step, called 'collect2'. This
+requires an extra program in the linkage step, called `collect2'. This
program pretends to be the linker, for use with GCC; it does its job by
running the ordinary linker, but also arranges to include the vectors of
initialization and termination functions. These functions are called
-via '__main' as described above. In order to use this method,
-'use_collect2' must be defined in the target in 'config.gcc'.
+via `__main' as described above. In order to use this method,
+`use_collect2' must be defined in the target in `config.gcc'.
The following section describes the specific macros that control and
customize the handling of initialization and termination functions.
@@ -35359,14 +35790,14 @@ and termination functions:
initialization code. If not defined, GCC will assume such a
section does not exist. When you are using special sections for
initialization and termination functions, this macro also controls
- how 'crtstuff.c' and 'libgcc2.c' arrange to run the initialization
+ how `crtstuff.c' and `libgcc2.c' arrange to run the initialization
functions.
-- Macro: HAS_INIT_SECTION
- If defined, 'main' will not call '__main' as described above. This
- macro should be defined for systems that control start-up code on a
- symbol-by-symbol basis, such as OSF/1, and should not be defined
- explicitly for systems that support 'INIT_SECTION_ASM_OP'.
+ If defined, `main' will not call `__main' as described above.
+ This macro should be defined for systems that control start-up code
+ on a symbol-by-symbol basis, such as OSF/1, and should not be
+ defined explicitly for systems that support `INIT_SECTION_ASM_OP'.
-- Macro: LD_INIT_SWITCH
If defined, a C string constant for a switch that tells the linker
@@ -35381,84 +35812,84 @@ and termination functions:
automatically called when a shared library is loaded. The function
should call FUNC, which takes no arguments. If not defined, and
the object format requires an explicit initialization function,
- then a function called '_GLOBAL__DI' will be generated.
+ then a function called `_GLOBAL__DI' will be generated.
This function and the following one are used by collect2 when
- linking a shared library that needs constructors or destructors, or
- has DWARF2 exception tables embedded in the code.
+ linking a shared library that needs constructors or destructors,
+ or has DWARF2 exception tables embedded in the code.
-- Macro: COLLECT_SHARED_FINI_FUNC (STREAM, FUNC)
If defined, a C statement that will write a function that can be
automatically called when a shared library is unloaded. The
function should call FUNC, which takes no arguments. If not
defined, and the object format requires an explicit finalization
- function, then a function called '_GLOBAL__DD' will be generated.
+ function, then a function called `_GLOBAL__DD' will be generated.
-- Macro: INVOKE__main
- If defined, 'main' will call '__main' despite the presence of
- 'INIT_SECTION_ASM_OP'. This macro should be defined for systems
+ If defined, `main' will call `__main' despite the presence of
+ `INIT_SECTION_ASM_OP'. This macro should be defined for systems
where the init section is not actually run automatically, but is
still useful for collecting the lists of constructors and
destructors.
-- Macro: SUPPORTS_INIT_PRIORITY
- If nonzero, the C++ 'init_priority' attribute is supported and the
+ If nonzero, the C++ `init_priority' attribute is supported and the
compiler should emit instructions to control the order of
initialization of objects. If zero, the compiler will issue an
- error message upon encountering an 'init_priority' attribute.
+ error message upon encountering an `init_priority' attribute.
-- Target Hook: bool TARGET_HAVE_CTORS_DTORS
This value is true if the target supports some "native" method of
collecting constructors and destructors to be run at startup and
- exit. It is false if we must use 'collect2'.
+ exit. It is false if we must use `collect2'.
-- Target Hook: void TARGET_ASM_CONSTRUCTOR (rtx SYMBOL, int PRIORITY)
If defined, a function that outputs assembler code to arrange to
call the function referenced by SYMBOL at initialization time.
- Assume that SYMBOL is a 'SYMBOL_REF' for a function taking no
+ Assume that SYMBOL is a `SYMBOL_REF' for a function taking no
arguments and with no return value. If the target supports
initialization priorities, PRIORITY is a value between 0 and
- 'MAX_INIT_PRIORITY'; otherwise it must be 'DEFAULT_INIT_PRIORITY'.
+ `MAX_INIT_PRIORITY'; otherwise it must be `DEFAULT_INIT_PRIORITY'.
If this macro is not defined by the target, a suitable default will
be chosen if (1) the target supports arbitrary section names, (2)
- the target defines 'CTORS_SECTION_ASM_OP', or (3) 'USE_COLLECT2' is
- not defined.
+ the target defines `CTORS_SECTION_ASM_OP', or (3) `USE_COLLECT2'
+ is not defined.
-- Target Hook: void TARGET_ASM_DESTRUCTOR (rtx SYMBOL, int PRIORITY)
- This is like 'TARGET_ASM_CONSTRUCTOR' but used for termination
+ This is like `TARGET_ASM_CONSTRUCTOR' but used for termination
functions rather than initialization functions.
- If 'TARGET_HAVE_CTORS_DTORS' is true, the initialization routine
+ If `TARGET_HAVE_CTORS_DTORS' is true, the initialization routine
generated for the generated object file will have static linkage.
- If your system uses 'collect2' as the means of processing constructors,
-then that program normally uses 'nm' to scan an object file for
-constructor functions to be called.
+ If your system uses `collect2' as the means of processing
+constructors, then that program normally uses `nm' to scan an object
+file for constructor functions to be called.
On certain kinds of systems, you can define this macro to make
-'collect2' work faster (and, in some cases, make it work at all):
+`collect2' work faster (and, in some cases, make it work at all):
-- Macro: OBJECT_FORMAT_COFF
Define this macro if the system uses COFF (Common Object File
- Format) object files, so that 'collect2' can assume this format and
- scan object files directly for dynamic constructor/destructor
+ Format) object files, so that `collect2' can assume this format
+ and scan object files directly for dynamic constructor/destructor
functions.
- This macro is effective only in a native compiler; 'collect2' as
- part of a cross compiler always uses 'nm' for the target machine.
+ This macro is effective only in a native compiler; `collect2' as
+ part of a cross compiler always uses `nm' for the target machine.
-- Macro: REAL_NM_FILE_NAME
Define this macro as a C string constant containing the file name
- to use to execute 'nm'. The default is to search the path normally
- for 'nm'.
+ to use to execute `nm'. The default is to search the path
+ normally for `nm'.
-- Macro: NM_FLAGS
- 'collect2' calls 'nm' to scan object files for static constructors
- and destructors and LTO info. By default, '-n' is passed. Define
- 'NM_FLAGS' to a C string constant if other options are needed to
- get the same output format as GNU 'nm -n' produces.
+ `collect2' calls `nm' to scan object files for static constructors
+ and destructors and LTO info. By default, `-n' is passed. Define
+ `NM_FLAGS' to a C string constant if other options are needed to
+ get the same output format as GNU `nm -n' produces.
If your system supports shared libraries and has a program to list the
dynamic dependencies of a given library or executable, you can define
@@ -35466,23 +35897,24 @@ these macros to enable support for running initialization and
termination functions in shared libraries:
-- Macro: LDD_SUFFIX
- Define this macro to a C string constant containing the name of the
- program which lists dynamic dependencies, like 'ldd' under SunOS 4.
+ Define this macro to a C string constant containing the name of
+ the program which lists dynamic dependencies, like `ldd' under
+ SunOS 4.
-- Macro: PARSE_LDD_OUTPUT (PTR)
Define this macro to be C code that extracts filenames from the
- output of the program denoted by 'LDD_SUFFIX'. PTR is a variable
- of type 'char *' that points to the beginning of a line of output
- from 'LDD_SUFFIX'. If the line lists a dynamic dependency, the
+ output of the program denoted by `LDD_SUFFIX'. PTR is a variable
+ of type `char *' that points to the beginning of a line of output
+ from `LDD_SUFFIX'. If the line lists a dynamic dependency, the
code must advance PTR to the beginning of the filename on that
- line. Otherwise, it must set PTR to 'NULL'.
+ line. Otherwise, it must set PTR to `NULL'.
-- Macro: SHLIB_SUFFIX
Define this macro to a C string constant containing the default
- shared library extension of the target (e.g., '".so"'). 'collect2'
+ shared library extension of the target (e.g., `".so"'). `collect2'
strips version information after this suffix when generating global
constructor and destructor names. This define is only needed on
- targets that use 'collect2' to process constructors and
+ targets that use `collect2' to process constructors and
destructors.

@@ -35500,22 +35932,22 @@ This describes assembler instruction output.
language.
-- Macro: ADDITIONAL_REGISTER_NAMES
- If defined, a C initializer for an array of structures containing a
- name and a register number. This macro defines additional names
- for hard registers, thus allowing the 'asm' option in declarations
+ If defined, a C initializer for an array of structures containing
+ a name and a register number. This macro defines additional names
+ for hard registers, thus allowing the `asm' option in declarations
to refer to registers using alternate names.
-- Macro: OVERLAPPING_REGISTER_NAMES
If defined, a C initializer for an array of structures containing a
name, a register number and a count of the number of consecutive
machine registers the name overlaps. This macro defines additional
- names for hard registers, thus allowing the 'asm' option in
+ names for hard registers, thus allowing the `asm' option in
declarations to refer to registers using alternate names. Unlike
- 'ADDITIONAL_REGISTER_NAMES', this macro should be used when the
+ `ADDITIONAL_REGISTER_NAMES', this macro should be used when the
register name implies multiple underlying registers.
This macro should be used when it is important that a clobber in an
- 'asm' statement clobbers all the underlying values implied by the
+ `asm' statement clobbers all the underlying values implied by the
register name. For example, on ARM, clobbering the
double-precision VFP register "d0" implies clobbering both
single-precision registers "s0" and "s1".
@@ -35526,21 +35958,21 @@ This describes assembler instruction output.
The definition is a C statement or statements which output an
assembler instruction opcode to the stdio stream STREAM. The
- macro-operand PTR is a variable of type 'char *' which points to
- the opcode name in its "internal" form--the form that is written in
- the machine description. The definition should output the opcode
- name to STREAM, performing any translation you desire, and
+ macro-operand PTR is a variable of type `char *' which points to
+ the opcode name in its "internal" form--the form that is written
+ in the machine description. The definition should output the
+ opcode name to STREAM, performing any translation you desire, and
increment the variable PTR to point at the end of the opcode so
that it will not be output twice.
In fact, your macro definition may process less than the entire
opcode name, or more than the opcode name; but if you want to
- process text that includes '%'-sequences to substitute operands,
+ process text that includes `%'-sequences to substitute operands,
you must take care of the substitution yourself. Just be sure to
increment PTR over whatever text should not be output normally.
If you need to look at the operand values, they can be found as the
- elements of 'recog_data.operand'.
+ elements of `recog_data.operand'.
If the macro definition does nothing, the instruction is output in
the usual way.
@@ -35551,19 +35983,19 @@ This describes assembler instruction output.
they will be output differently.
Here the argument OPVEC is the vector containing the operands
- extracted from INSN, and NOPERANDS is the number of elements of the
- vector which contain meaningful data for this insn. The contents
- of this vector are what will be used to convert the insn template
- into assembler code, so you can change the assembler output by
- changing the contents of the vector.
+ extracted from INSN, and NOPERANDS is the number of elements of
+ the vector which contain meaningful data for this insn. The
+ contents of this vector are what will be used to convert the insn
+ template into assembler code, so you can change the assembler
+ output by changing the contents of the vector.
This macro is useful when various assembler syntaxes share a single
file of instruction patterns; by defining this macro differently,
you can cause a large class of instructions to be output
differently (such as with rearranged operands). Naturally,
variations in assembler syntax affecting individual insn patterns
- ought to be handled by writing conditional output routines in those
- patterns.
+ ought to be handled by writing conditional output routines in
+ those patterns.
If this macro is not defined, it is equivalent to a null statement.
@@ -35574,11 +36006,11 @@ This describes assembler instruction output.
the assembler if necessary.
Here the argument OPVEC is the vector containing the operands
- extracted from INSN, and NOPERANDS is the number of elements of the
- vector which contain meaningful data for this insn. The contents
- of this vector are what was used to convert the insn template into
- assembler code, so you can change the assembler mode by checking
- the contents of the vector.
+ extracted from INSN, and NOPERANDS is the number of elements of
+ the vector which contain meaningful data for this insn. The
+ contents of this vector are what was used to convert the insn
+ template into assembler code, so you can change the assembler mode
+ by checking the contents of the vector.
-- Macro: PRINT_OPERAND (STREAM, X, CODE)
A C compound statement to output to stdio stream STREAM the
@@ -35588,23 +36020,24 @@ This describes assembler instruction output.
CODE is a value that can be used to specify one of several ways of
printing the operand. It is used when identical operands must be
printed differently depending on the context. CODE comes from the
- '%' specification that was used to request printing of the operand.
- If the specification was just '%DIGIT' then CODE is 0; if the
- specification was '%LTR DIGIT' then CODE is the ASCII code for LTR.
+ `%' specification that was used to request printing of the
+ operand. If the specification was just `%DIGIT' then CODE is 0;
+ if the specification was `%LTR DIGIT' then CODE is the ASCII code
+ for LTR.
If X is a register, this macro should print the register's name.
- The names can be found in an array 'reg_names' whose type is 'char
- *[]'. 'reg_names' is initialized from 'REGISTER_NAMES'.
+ The names can be found in an array `reg_names' whose type is `char
+ *[]'. `reg_names' is initialized from `REGISTER_NAMES'.
- When the machine description has a specification '%PUNCT' (a '%'
+ When the machine description has a specification `%PUNCT' (a `%'
followed by a punctuation character), this macro is called with a
null pointer for X and the punctuation character for CODE.
-- Macro: PRINT_OPERAND_PUNCT_VALID_P (CODE)
A C expression which evaluates to true if CODE is a valid
- punctuation character for use in the 'PRINT_OPERAND' macro. If
- 'PRINT_OPERAND_PUNCT_VALID_P' is not defined, it means that no
- punctuation characters (except for the standard one, '%') are used
+ punctuation character for use in the `PRINT_OPERAND' macro. If
+ `PRINT_OPERAND_PUNCT_VALID_P' is not defined, it means that no
+ punctuation characters (except for the standard one, `%') are used
in this way.
-- Macro: PRINT_OPERAND_ADDRESS (STREAM, X)
@@ -35614,13 +36047,13 @@ This describes assembler instruction output.
On some machines, the syntax for a symbolic address depends on the
section that the address refers to. On these machines, define the
- hook 'TARGET_ENCODE_SECTION_INFO' to store the information into the
- 'symbol_ref', and then check for it here. *Note Assembler
+ hook `TARGET_ENCODE_SECTION_INFO' to store the information into the
+ `symbol_ref', and then check for it here. *Note Assembler
Format::.
-- Macro: DBR_OUTPUT_SEQEND (FILE)
A C statement, to be executed after all slot-filler instructions
- have been output. If necessary, call 'dbr_sequence_length' to
+ have been output. If necessary, call `dbr_sequence_length' to
determine the number of slots filled in a sequence (zero if not
currently outputting a sequence), to decide how many no-ops to
output, or whatever.
@@ -35631,24 +36064,24 @@ This describes assembler instruction output.
Note that output routines for instructions with delay slots must be
prepared to deal with not being output as part of a sequence (i.e. when
-the scheduling pass is not run, or when no slot fillers could be found.)
-The variable 'final_sequence' is null when not processing a sequence,
-otherwise it contains the 'sequence' rtx being output.
+the scheduling pass is not run, or when no slot fillers could be
+found.) The variable `final_sequence' is null when not processing a
+sequence, otherwise it contains the `sequence' rtx being output.
-- Macro: REGISTER_PREFIX
-- Macro: LOCAL_LABEL_PREFIX
-- Macro: USER_LABEL_PREFIX
-- Macro: IMMEDIATE_PREFIX
- If defined, C string expressions to be used for the '%R', '%L',
- '%U', and '%I' options of 'asm_fprintf' (see 'final.c'). These are
- useful when a single 'md' file must support multiple assembler
- formats. In that case, the various 'tm.h' files can define these
+ If defined, C string expressions to be used for the `%R', `%L',
+ `%U', and `%I' options of `asm_fprintf' (see `final.c'). These
+ are useful when a single `md' file must support multiple assembler
+ formats. In that case, the various `tm.h' files can define these
macros differently.
-- Macro: ASM_FPRINTF_EXTENSIONS (FILE, ARGPTR, FORMAT)
- If defined this macro should expand to a series of 'case'
- statements which will be parsed inside the 'switch' statement of
- the 'asm_fprintf' function. This allows targets to define extra
+ If defined this macro should expand to a series of `case'
+ statements which will be parsed inside the `switch' statement of
+ the `asm_fprintf' function. This allows targets to define extra
printf formats which may useful when generating their assembler
statements. Note that uppercase letters are reserved for future
generic extensions to asm_fprintf, and so are not available to
@@ -35664,25 +36097,25 @@ otherwise it contains the 'sequence' rtx being output.
use, with zero as the first variant.
If this macro is defined, you may use constructs of the form
- '{option0|option1|option2...}'
- in the output templates of patterns (*note Output Template::) or in
- the first argument of 'asm_fprintf'. This construct outputs
- 'option0', 'option1', 'option2', etc., if the value of
- 'ASSEMBLER_DIALECT' is zero, one, two, etc. Any special characters
+ `{option0|option1|option2...}'
+ in the output templates of patterns (*note Output Template::) or
+ in the first argument of `asm_fprintf'. This construct outputs
+ `option0', `option1', `option2', etc., if the value of
+ `ASSEMBLER_DIALECT' is zero, one, two, etc. Any special characters
within these strings retain their usual meaning. If there are
fewer alternatives within the braces than the value of
- 'ASSEMBLER_DIALECT', the construct outputs nothing. If it's needed
- to print curly braces or '|' character in assembler output
- directly, '%{', '%}' and '%|' can be used.
+ `ASSEMBLER_DIALECT', the construct outputs nothing. If it's needed
+ to print curly braces or `|' character in assembler output
+ directly, `%{', `%}' and `%|' can be used.
- If you do not define this macro, the characters '{', '|' and '}' do
- not have any special meaning when used in templates or operands to
- 'asm_fprintf'.
+ If you do not define this macro, the characters `{', `|' and `}'
+ do not have any special meaning when used in templates or operands
+ to `asm_fprintf'.
- Define the macros 'REGISTER_PREFIX', 'LOCAL_LABEL_PREFIX',
- 'USER_LABEL_PREFIX' and 'IMMEDIATE_PREFIX' if you can express the
+ Define the macros `REGISTER_PREFIX', `LOCAL_LABEL_PREFIX',
+ `USER_LABEL_PREFIX' and `IMMEDIATE_PREFIX' if you can express the
variations in assembler language syntax with that mechanism.
- Define 'ASSEMBLER_DIALECT' and use the '{option0|option1}' syntax
+ Define `ASSEMBLER_DIALECT' and use the `{option0|option1}' syntax
if the syntax variant are larger and involve such things as
different opcodes or operand order.
@@ -35693,8 +36126,8 @@ otherwise it contains the 'sequence' rtx being output.
-- Macro: ASM_OUTPUT_REG_POP (STREAM, REGNO)
A C expression to output to STREAM some assembler code which will
- pop hard register number REGNO off of the stack. The code need not
- be optimal, since this macro is used only when profiling.
+ pop hard register number REGNO off of the stack. The code need
+ not be optimal, since this macro is used only when profiling.

File: gccint.info, Node: Dispatch Tables, Next: Exception Region Output, Prev: Instruction Output, Up: Assembler Format
@@ -35709,7 +36142,7 @@ This concerns dispatch tables.
pseudo-instruction to generate a difference between two labels.
VALUE and REL are the numbers of two internal labels. The
definitions of these labels are output using
- '(*targetm.asm_out.internal_label)', and they must be printed in
+ `(*targetm.asm_out.internal_label)', and they must be printed in
the same way here. For example,
fprintf (STREAM, "\t.word L%d-L%d\n",
@@ -35718,7 +36151,7 @@ This concerns dispatch tables.
You must provide this macro on machines where the addresses in a
dispatch table are relative to the table's own address. If
defined, GCC will also use this macro on all machines when
- producing PIC. BODY is the body of the 'ADDR_DIFF_VEC'; it is
+ producing PIC. BODY is the body of the `ADDR_DIFF_VEC'; it is
provided so that the mode and flags can be read.
-- Macro: ASM_OUTPUT_ADDR_VEC_ELT (STREAM, VALUE)
@@ -35729,30 +36162,30 @@ This concerns dispatch tables.
stream STREAM an assembler pseudo-instruction to generate a
reference to a label. VALUE is the number of an internal label
whose definition is output using
- '(*targetm.asm_out.internal_label)'. For example,
+ `(*targetm.asm_out.internal_label)'. For example,
fprintf (STREAM, "\t.word L%d\n", VALUE)
-- Macro: ASM_OUTPUT_CASE_LABEL (STREAM, PREFIX, NUM, TABLE)
Define this if the label before a jump-table needs to be output
specially. The first three arguments are the same as for
- '(*targetm.asm_out.internal_label)'; the fourth argument is the
- jump-table which follows (a 'jump_table_data' containing an
- 'addr_vec' or 'addr_diff_vec').
+ `(*targetm.asm_out.internal_label)'; the fourth argument is the
+ jump-table which follows (a `jump_table_data' containing an
+ `addr_vec' or `addr_diff_vec').
- This feature is used on system V to output a 'swbeg' statement for
+ This feature is used on system V to output a `swbeg' statement for
the table.
If this macro is not defined, these labels are output with
- '(*targetm.asm_out.internal_label)'.
+ `(*targetm.asm_out.internal_label)'.
-- Macro: ASM_OUTPUT_CASE_END (STREAM, NUM, TABLE)
Define this if something special must be output at the end of a
jump-table. The definition should be a C statement to be executed
after the assembler code for the table is written. It should write
- the appropriate code to stdio stream STREAM. The argument TABLE is
- the jump-table insn, and NUM is the label-number of the preceding
- label.
+ the appropriate code to stdio stream STREAM. The argument TABLE
+ is the jump-table insn, and NUM is the label-number of the
+ preceding label.
If this macro is not defined, nothing special is output at the end
of the jump-table.
@@ -35764,8 +36197,8 @@ This concerns dispatch tables.
should write the appropriate label, for the FDE associated with the
function declaration DECL, to the stdio stream STREAM. The third
argument, FOR_EH, is a boolean: true if this is for an exception
- table. The fourth argument, EMPTY, is a boolean: true if this is a
- placeholder label for an omitted FDE.
+ table. The fourth argument, EMPTY, is a boolean: true if this is
+ a placeholder label for an omitted FDE.
The default is that FDEs are not given nonlocal labels.
@@ -35778,21 +36211,21 @@ This concerns dispatch tables.
-- Target Hook: void TARGET_ASM_EMIT_EXCEPT_PERSONALITY (rtx
PERSONALITY)
- If the target implements 'TARGET_ASM_UNWIND_EMIT', this hook may be
- used to emit a directive to install a personality hook into the
- unwind info. This hook should not be used if dwarf2 unwind info is
- used.
+ If the target implements `TARGET_ASM_UNWIND_EMIT', this hook may
+ be used to emit a directive to install a personality hook into the
+ unwind info. This hook should not be used if dwarf2 unwind info
+ is used.
-- Target Hook: void TARGET_ASM_UNWIND_EMIT (FILE *STREAM, rtx_insn
*INSN)
This target hook emits assembly directives required to unwind the
given instruction. This is only used when
- 'TARGET_EXCEPT_UNWIND_INFO' returns 'UI_TARGET'.
+ `TARGET_EXCEPT_UNWIND_INFO' returns `UI_TARGET'.
-- Target Hook: bool TARGET_ASM_UNWIND_EMIT_BEFORE_INSN
- True if the 'TARGET_ASM_UNWIND_EMIT' hook should be called before
- the assembly for INSN has been emitted, false if the hook should be
- called afterward.
+ True if the `TARGET_ASM_UNWIND_EMIT' hook should be called before
+ the assembly for INSN has been emitted, false if the hook should
+ be called afterward.

File: gccint.info, Node: Exception Region Output, Next: Alignment Output, Prev: Dispatch Tables, Up: Assembler Format
@@ -35807,8 +36240,8 @@ region.
If defined, a C string constant for the name of the section
containing exception handling frame unwind information. If not
defined, GCC will provide a default definition if the target
- supports named sections. 'crtstuff.c' uses this macro to switch to
- the appropriate section.
+ supports named sections. `crtstuff.c' uses this macro to switch
+ to the appropriate section.
You should define this symbol if your target supports DWARF 2 frame
unwind information and the default definition does not work.
@@ -35819,7 +36252,7 @@ region.
might be necessary, for instance, if the system linker does garbage
collection and sections cannot be marked as not to be collected.
- Do not define this macro unless 'TARGET_ASM_NAMED_SECTION' is also
+ Do not define this macro unless `TARGET_ASM_NAMED_SECTION' is also
defined.
-- Macro: EH_TABLES_CAN_BE_READ_ONLY
@@ -35829,65 +36262,66 @@ region.
read-only and read-write sections into a single read-write section.
-- Macro: MASK_RETURN_ADDR
- An rtx used to mask the return address found via 'RETURN_ADDR_RTX',
- so that it does not contain any extraneous set bits in it.
+ An rtx used to mask the return address found via
+ `RETURN_ADDR_RTX', so that it does not contain any extraneous set
+ bits in it.
-- Macro: DWARF2_UNWIND_INFO
Define this macro to 0 if your target supports DWARF 2 frame unwind
information, but it does not yet work with exception handling.
Otherwise, if your target supports this information (if it defines
- 'INCOMING_RETURN_ADDR_RTX' and 'OBJECT_FORMAT_ELF'), GCC will
+ `INCOMING_RETURN_ADDR_RTX' and `OBJECT_FORMAT_ELF'), GCC will
provide a default definition of 1.
-- Common Target Hook: enum unwind_info_type TARGET_EXCEPT_UNWIND_INFO
(struct gcc_options *OPTS)
This hook defines the mechanism that will be used for exception
handling by the target. If the target has ABI specified unwind
- tables, the hook should return 'UI_TARGET'. If the target is to
- use the 'setjmp'/'longjmp'-based exception handling scheme, the
- hook should return 'UI_SJLJ'. If the target supports DWARF 2 frame
- unwind information, the hook should return 'UI_DWARF2'.
+ tables, the hook should return `UI_TARGET'. If the target is to
+ use the `setjmp'/`longjmp'-based exception handling scheme, the
+ hook should return `UI_SJLJ'. If the target supports DWARF 2
+ frame unwind information, the hook should return `UI_DWARF2'.
A target may, if exceptions are disabled, choose to return
- 'UI_NONE'. This may end up simplifying other parts of
+ `UI_NONE'. This may end up simplifying other parts of
target-specific code. The default implementation of this hook
- never returns 'UI_NONE'.
+ never returns `UI_NONE'.
Note that the value returned by this hook should be constant. It
should not depend on anything except the command-line switches
- described by OPTS. In particular, the setting 'UI_SJLJ' must be
+ described by OPTS. In particular, the setting `UI_SJLJ' must be
fixed at compiler start-up as C pre-processor macros and builtin
functions related to exception handling are set up depending on
this setting.
The default implementation of the hook first honors the
- '--enable-sjlj-exceptions' configure option, then
- 'DWARF2_UNWIND_INFO', and finally defaults to 'UI_SJLJ'. If
- 'DWARF2_UNWIND_INFO' depends on command-line options, the target
+ `--enable-sjlj-exceptions' configure option, then
+ `DWARF2_UNWIND_INFO', and finally defaults to `UI_SJLJ'. If
+ `DWARF2_UNWIND_INFO' depends on command-line options, the target
must define this hook so that OPTS is used correctly.
-- Common Target Hook: bool TARGET_UNWIND_TABLES_DEFAULT
- This variable should be set to 'true' if the target ABI requires
- unwinding tables even when exceptions are not used. It must not be
- modified by command-line option processing.
+ This variable should be set to `true' if the target ABI requires
+ unwinding tables even when exceptions are not used. It must not
+ be modified by command-line option processing.
-- Macro: DONT_USE_BUILTIN_SETJMP
- Define this macro to 1 if the 'setjmp'/'longjmp'-based scheme
- should use the 'setjmp'/'longjmp' functions from the C library
- instead of the '__builtin_setjmp'/'__builtin_longjmp' machinery.
+ Define this macro to 1 if the `setjmp'/`longjmp'-based scheme
+ should use the `setjmp'/`longjmp' functions from the C library
+ instead of the `__builtin_setjmp'/`__builtin_longjmp' machinery.
-- Macro: JMP_BUF_SIZE
- This macro has no effect unless 'DONT_USE_BUILTIN_SETJMP' is also
- defined. Define this macro if the default size of 'jmp_buf' buffer
- for the 'setjmp'/'longjmp'-based exception handling mechanism is
+ This macro has no effect unless `DONT_USE_BUILTIN_SETJMP' is also
+ defined. Define this macro if the default size of `jmp_buf' buffer
+ for the `setjmp'/`longjmp'-based exception handling mechanism is
not large enough, or if it is much too large. The default size is
- 'FIRST_PSEUDO_REGISTER * sizeof(void *)'.
+ `FIRST_PSEUDO_REGISTER * sizeof(void *)'.
-- Macro: DWARF_CIE_DATA_ALIGNMENT
This macro need only be defined if the target might save registers
in the function prologue at an offset to the stack pointer that is
- not aligned to 'UNITS_PER_WORD'. The definition should be the
- negative minimum alignment if 'STACK_GROWS_DOWNWARD' is defined,
+ not aligned to `UNITS_PER_WORD'. The definition should be the
+ negative minimum alignment if `STACK_GROWS_DOWNWARD' is defined,
and the positive minimum alignment otherwise. *Note SDB and
DWARF::. Only applicable if the target supports DWARF 2 frame
unwind information.
@@ -35895,7 +36329,7 @@ region.
-- Target Hook: bool TARGET_TERMINATE_DW2_EH_FRAME_INFO
Contains the value true if the target should add a zero word onto
the end of a Dwarf-2 frame info section when used for exception
- handling. Default value is false if 'EH_FRAME_SECTION_NAME' is
+ handling. Default value is false if `EH_FRAME_SECTION_NAME' is
defined, and true otherwise.
-- Target Hook: rtx TARGET_DWARF_REGISTER_SPAN (rtx REG)
@@ -35904,8 +36338,8 @@ region.
if the register and its mode are represented in Dwarf in
non-contiguous locations, or if the register should be represented
in more than one register in Dwarf. Otherwise, this hook should
- return 'NULL_RTX'. If not defined, the default is to return
- 'NULL_RTX'.
+ return `NULL_RTX'. If not defined, the default is to return
+ `NULL_RTX'.
-- Target Hook: machine_mode TARGET_DWARF_FRAME_REG_MODE (int REGNO)
Given a register, this hook should return the mode which the
@@ -35917,21 +36351,21 @@ region.
If some registers are represented in Dwarf-2 unwind information in
multiple pieces, define this hook to fill in information about the
sizes of those pieces in the table used by the unwinder at runtime.
- It will be called by 'expand_builtin_init_dwarf_reg_sizes' after
+ It will be called by `expand_builtin_init_dwarf_reg_sizes' after
filling in a single size corresponding to each hard register;
ADDRESS is the address of the table.
-- Target Hook: bool TARGET_ASM_TTYPE (rtx SYM)
This hook is used to output a reference from a frame unwinding
table to the type_info object identified by SYM. It should return
- 'true' if the reference was output. Returning 'false' will cause
+ `true' if the reference was output. Returning `false' will cause
the reference to be output using the normal Dwarf2 routines.
-- Target Hook: bool TARGET_ARM_EABI_UNWINDER
- This flag should be set to 'true' on targets that use an ARM EABI
- based unwinding library, and 'false' on other targets. This
+ This flag should be set to `true' on targets that use an ARM EABI
+ based unwinding library, and `false' on other targets. This
effects the format of unwinding tables, and how the unwinder in
- entered after running a cleanup. The default is 'false'.
+ entered after running a cleanup. The default is `false'.

File: gccint.info, Node: Alignment Output, Prev: Exception Region Output, Up: Assembler Format
@@ -35951,17 +36385,17 @@ This describes commands for alignment.
Unless it's necessary to inspect the LABEL parameter, it is better
to set the variable ALIGN_JUMPS in the target's
- 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
- user's selection in ALIGN_JUMPS in a 'JUMP_ALIGN' implementation.
+ `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
+ user's selection in ALIGN_JUMPS in a `JUMP_ALIGN' implementation.
-- Target Hook: int TARGET_ASM_JUMP_ALIGN_MAX_SKIP (rtx_insn *LABEL)
The maximum number of bytes to skip before LABEL when applying
- 'JUMP_ALIGN'. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is
+ `JUMP_ALIGN'. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is
defined.
-- Macro: LABEL_ALIGN_AFTER_BARRIER (LABEL)
The alignment (log base 2) to put in front of LABEL, which follows
- a 'BARRIER'.
+ a `BARRIER'.
This macro need not be defined if you don't want any special
alignment to be done at such a time. Most machine descriptions do
@@ -35970,8 +36404,8 @@ This describes commands for alignment.
-- Target Hook: int TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP
(rtx_insn *LABEL)
The maximum number of bytes to skip before LABEL when applying
- 'LABEL_ALIGN_AFTER_BARRIER'. This works only if
- 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
+ `LABEL_ALIGN_AFTER_BARRIER'. This works only if
+ `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
-- Macro: LOOP_ALIGN (LABEL)
The alignment (log base 2) to put in front of LABEL that heads a
@@ -35982,49 +36416,49 @@ This describes commands for alignment.
not currently define the macro.
Unless it's necessary to inspect the LABEL parameter, it is better
- to set the variable 'align_loops' in the target's
- 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
- user's selection in 'align_loops' in a 'LOOP_ALIGN' implementation.
+ to set the variable `align_loops' in the target's
+ `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
+ user's selection in `align_loops' in a `LOOP_ALIGN' implementation.
-- Target Hook: int TARGET_ASM_LOOP_ALIGN_MAX_SKIP (rtx_insn *LABEL)
- The maximum number of bytes to skip when applying 'LOOP_ALIGN' to
- LABEL. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
+ The maximum number of bytes to skip when applying `LOOP_ALIGN' to
+ LABEL. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
-- Macro: LABEL_ALIGN (LABEL)
The alignment (log base 2) to put in front of LABEL. If
- 'LABEL_ALIGN_AFTER_BARRIER' / 'LOOP_ALIGN' specify a different
+ `LABEL_ALIGN_AFTER_BARRIER' / `LOOP_ALIGN' specify a different
alignment, the maximum of the specified values is used.
Unless it's necessary to inspect the LABEL parameter, it is better
- to set the variable 'align_labels' in the target's
- 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
- user's selection in 'align_labels' in a 'LABEL_ALIGN'
+ to set the variable `align_labels' in the target's
+ `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the
+ user's selection in `align_labels' in a `LABEL_ALIGN'
implementation.
-- Target Hook: int TARGET_ASM_LABEL_ALIGN_MAX_SKIP (rtx_insn *LABEL)
- The maximum number of bytes to skip when applying 'LABEL_ALIGN' to
- LABEL. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
+ The maximum number of bytes to skip when applying `LABEL_ALIGN' to
+ LABEL. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined.
-- Macro: ASM_OUTPUT_SKIP (STREAM, NBYTES)
A C statement to output to the stdio stream STREAM an assembler
- instruction to advance the location counter by NBYTES bytes. Those
- bytes should be zero when loaded. NBYTES will be a C expression of
- type 'unsigned HOST_WIDE_INT'.
+ instruction to advance the location counter by NBYTES bytes.
+ Those bytes should be zero when loaded. NBYTES will be a C
+ expression of type `unsigned HOST_WIDE_INT'.
-- Macro: ASM_NO_SKIP_IN_TEXT
- Define this macro if 'ASM_OUTPUT_SKIP' should not be used in the
+ Define this macro if `ASM_OUTPUT_SKIP' should not be used in the
text section because it fails to put zeros in the bytes that are
- skipped. This is true on many Unix systems, where the pseudo-op to
- skip bytes produces no-op instructions rather than zeros when used
- in the text section.
+ skipped. This is true on many Unix systems, where the pseudo-op
+ to skip bytes produces no-op instructions rather than zeros when
+ used in the text section.
-- Macro: ASM_OUTPUT_ALIGN (STREAM, POWER)
A C statement to output to the stdio stream STREAM an assembler
command to advance the location counter to a multiple of 2 to the
- POWER bytes. POWER will be a C expression of type 'int'.
+ POWER bytes. POWER will be a C expression of type `int'.
-- Macro: ASM_OUTPUT_ALIGN_WITH_NOP (STREAM, POWER)
- Like 'ASM_OUTPUT_ALIGN', except that the "nop" instruction is used
+ Like `ASM_OUTPUT_ALIGN', except that the "nop" instruction is used
for padding, if necessary.
-- Macro: ASM_OUTPUT_MAX_SKIP_ALIGN (STREAM, POWER, MAX_SKIP)
@@ -36032,7 +36466,7 @@ This describes commands for alignment.
command to advance the location counter to a multiple of 2 to the
POWER bytes, but only if MAX_SKIP or fewer bytes are needed to
satisfy the alignment request. POWER and MAX_SKIP will be a C
- expression of type 'int'.
+ expression of type `int'.

File: gccint.info, Node: Debugging Info, Next: Floating Point, Prev: Assembler Format, Up: Target Macros
@@ -36061,20 +36495,20 @@ These macros affect all debugging formats.
-- Macro: DBX_REGISTER_NUMBER (REGNO)
A C expression that returns the DBX register number for the
- compiler register number REGNO. In the default macro provided, the
- value of this expression will be REGNO itself. But sometimes there
- are some registers that the compiler knows about and DBX does not,
- or vice versa. In such cases, some register may need to have one
- number in the compiler and another for DBX.
+ compiler register number REGNO. In the default macro provided,
+ the value of this expression will be REGNO itself. But sometimes
+ there are some registers that the compiler knows about and DBX
+ does not, or vice versa. In such cases, some register may need to
+ have one number in the compiler and another for DBX.
If two registers have consecutive numbers inside GCC, and they can
be used as a pair to hold a multiword value, then they _must_ have
- consecutive numbers after renumbering with 'DBX_REGISTER_NUMBER'.
+ consecutive numbers after renumbering with `DBX_REGISTER_NUMBER'.
Otherwise, debuggers will be unable to access such a pair, because
- they expect register pairs to be consecutive in their own numbering
- scheme.
+ they expect register pairs to be consecutive in their own
+ numbering scheme.
- If you find yourself defining 'DBX_REGISTER_NUMBER' in way that
+ If you find yourself defining `DBX_REGISTER_NUMBER' in way that
does not preserve register pairs, then what you must do instead is
redefine the actual register numbering scheme.
@@ -36085,7 +36519,7 @@ These macros affect all debugging formats.
and gives the offset from the frame-pointer. This is required for
targets that produce debugging output for DBX or COFF-style
debugging output for SDB and allow the frame-pointer to be
- eliminated when the '-g' options is used.
+ eliminated when the `-g' options is used.
-- Macro: DEBUGGER_ARG_OFFSET (OFFSET, X)
A C expression that returns the integer offset value for an
@@ -36094,21 +36528,21 @@ These macros affect all debugging formats.
-- Macro: PREFERRED_DEBUGGING_TYPE
A C expression that returns the type of debugging output GCC should
- produce when the user specifies just '-g'. Define this if you have
- arranged for GCC to support more than one format of debugging
- output. Currently, the allowable values are 'DBX_DEBUG',
- 'SDB_DEBUG', 'DWARF_DEBUG', 'DWARF2_DEBUG', 'XCOFF_DEBUG',
- 'VMS_DEBUG', and 'VMS_AND_DWARF2_DEBUG'.
+ produce when the user specifies just `-g'. Define this if you
+ have arranged for GCC to support more than one format of debugging
+ output. Currently, the allowable values are `DBX_DEBUG',
+ `SDB_DEBUG', `DWARF_DEBUG', `DWARF2_DEBUG', `XCOFF_DEBUG',
+ `VMS_DEBUG', and `VMS_AND_DWARF2_DEBUG'.
- When the user specifies '-ggdb', GCC normally also uses the value
+ When the user specifies `-ggdb', GCC normally also uses the value
of this macro to select the debugging output format, but with two
- exceptions. If 'DWARF2_DEBUGGING_INFO' is defined, GCC uses the
- value 'DWARF2_DEBUG'. Otherwise, if 'DBX_DEBUGGING_INFO' is
- defined, GCC uses 'DBX_DEBUG'.
+ exceptions. If `DWARF2_DEBUGGING_INFO' is defined, GCC uses the
+ value `DWARF2_DEBUG'. Otherwise, if `DBX_DEBUGGING_INFO' is
+ defined, GCC uses `DBX_DEBUG'.
The value of this macro only affects the default debugging output;
the user can always get a specific type of output by using
- '-gstabs', '-gcoff', '-gdwarf-2', '-gxcoff', or '-gvms'.
+ `-gstabs', `-gcoff', `-gdwarf-2', `-gxcoff', or `-gvms'.

File: gccint.info, Node: DBX Options, Next: DBX Hooks, Prev: All Debuggers, Up: Debugging Info
@@ -36119,12 +36553,12 @@ File: gccint.info, Node: DBX Options, Next: DBX Hooks, Prev: All Debuggers,
These are specific options for DBX output.
-- Macro: DBX_DEBUGGING_INFO
- Define this macro if GCC should produce debugging output for DBX in
- response to the '-g' option.
+ Define this macro if GCC should produce debugging output for DBX
+ in response to the `-g' option.
-- Macro: XCOFF_DEBUGGING_INFO
Define this macro if GCC should produce XCOFF format debugging
- output in response to the '-g' option. This is a variant of DBX
+ output in response to the `-g' option. This is a variant of DBX
format.
-- Macro: DEFAULT_GDB_EXTENSIONS
@@ -36135,37 +36569,39 @@ These are specific options for DBX output.
information if there is any occasion to.
-- Macro: DEBUG_SYMS_TEXT
- Define this macro if all '.stabs' commands should be output while
+ Define this macro if all `.stabs' commands should be output while
in the text section.
-- Macro: ASM_STABS_OP
- A C string constant, including spacing, naming the assembler pseudo
- op to use instead of '"\t.stabs\t"' to define an ordinary debugging
- symbol. If you don't define this macro, '"\t.stabs\t"' is used.
- This macro applies only to DBX debugging information format.
+ A C string constant, including spacing, naming the assembler
+ pseudo op to use instead of `"\t.stabs\t"' to define an ordinary
+ debugging symbol. If you don't define this macro, `"\t.stabs\t"'
+ is used. This macro applies only to DBX debugging information
+ format.
-- Macro: ASM_STABD_OP
- A C string constant, including spacing, naming the assembler pseudo
- op to use instead of '"\t.stabd\t"' to define a debugging symbol
- whose value is the current location. If you don't define this
- macro, '"\t.stabd\t"' is used. This macro applies only to DBX
- debugging information format.
+ A C string constant, including spacing, naming the assembler
+ pseudo op to use instead of `"\t.stabd\t"' to define a debugging
+ symbol whose value is the current location. If you don't define
+ this macro, `"\t.stabd\t"' is used. This macro applies only to
+ DBX debugging information format.
-- Macro: ASM_STABN_OP
- A C string constant, including spacing, naming the assembler pseudo
- op to use instead of '"\t.stabn\t"' to define a debugging symbol
- with no name. If you don't define this macro, '"\t.stabn\t"' is
- used. This macro applies only to DBX debugging information format.
+ A C string constant, including spacing, naming the assembler
+ pseudo op to use instead of `"\t.stabn\t"' to define a debugging
+ symbol with no name. If you don't define this macro,
+ `"\t.stabn\t"' is used. This macro applies only to DBX debugging
+ information format.
-- Macro: DBX_NO_XREFS
Define this macro if DBX on your system does not support the
- construct 'xsTAGNAME'. On some systems, this construct is used to
+ construct `xsTAGNAME'. On some systems, this construct is used to
describe a forward reference to a structure named TAGNAME. On
other systems, this construct is not supported at all.
-- Macro: DBX_CONTIN_LENGTH
A symbol name in DBX-format debugging information is normally
- continued (split into two separate '.stabs' directives) when it
+ continued (split into two separate `.stabs' directives) when it
exceeds a certain length (by default, 80 characters). On some
operating systems, DBX requires this splitting; on others,
splitting must not be done. You can inhibit splitting by defining
@@ -36174,61 +36610,61 @@ These are specific options for DBX output.
length you desire.
-- Macro: DBX_CONTIN_CHAR
- Normally continuation is indicated by adding a '\' character to the
- end of a '.stabs' string when a continuation follows. To use a
- different character instead, define this macro as a character
+ Normally continuation is indicated by adding a `\' character to
+ the end of a `.stabs' string when a continuation follows. To use
+ a different character instead, define this macro as a character
constant for the character you want to use. Do not define this
macro if backslash is correct for your system.
-- Macro: DBX_STATIC_STAB_DATA_SECTION
Define this macro if it is necessary to go to the data section
- before outputting the '.stabs' pseudo-op for a non-global static
+ before outputting the `.stabs' pseudo-op for a non-global static
variable.
-- Macro: DBX_TYPE_DECL_STABS_CODE
- The value to use in the "code" field of the '.stabs' directive for
- a typedef. The default is 'N_LSYM'.
+ The value to use in the "code" field of the `.stabs' directive for
+ a typedef. The default is `N_LSYM'.
-- Macro: DBX_STATIC_CONST_VAR_CODE
- The value to use in the "code" field of the '.stabs' directive for
+ The value to use in the "code" field of the `.stabs' directive for
a static variable located in the text section. DBX format does not
- provide any "right" way to do this. The default is 'N_FUN'.
+ provide any "right" way to do this. The default is `N_FUN'.
-- Macro: DBX_REGPARM_STABS_CODE
- The value to use in the "code" field of the '.stabs' directive for
+ The value to use in the "code" field of the `.stabs' directive for
a parameter passed in registers. DBX format does not provide any
- "right" way to do this. The default is 'N_RSYM'.
+ "right" way to do this. The default is `N_RSYM'.
-- Macro: DBX_REGPARM_STABS_LETTER
The letter to use in DBX symbol data to identify a symbol as a
parameter passed in registers. DBX format does not customarily
- provide any way to do this. The default is ''P''.
+ provide any way to do this. The default is `'P''.
-- Macro: DBX_FUNCTION_FIRST
Define this macro if the DBX information for a function and its
arguments should precede the assembler code for the function.
- Normally, in DBX format, the debugging information entirely follows
- the assembler code.
+ Normally, in DBX format, the debugging information entirely
+ follows the assembler code.
-- Macro: DBX_BLOCKS_FUNCTION_RELATIVE
Define this macro, with value 1, if the value of a symbol
- describing the scope of a block ('N_LBRAC' or 'N_RBRAC') should be
+ describing the scope of a block (`N_LBRAC' or `N_RBRAC') should be
relative to the start of the enclosing function. Normally, GCC
uses an absolute address.
-- Macro: DBX_LINES_FUNCTION_RELATIVE
Define this macro, with value 1, if the value of a symbol
- indicating the current line number ('N_SLINE') should be relative
+ indicating the current line number (`N_SLINE') should be relative
to the start of the enclosing function. Normally, GCC uses an
absolute address.
-- Macro: DBX_USE_BINCL
- Define this macro if GCC should generate 'N_BINCL' and 'N_EINCL'
+ Define this macro if GCC should generate `N_BINCL' and `N_EINCL'
stabs for included header files, as on Sun systems. This macro
- also directs GCC to output a type number as a pair of a file number
- and a type number within the file. Normally, GCC does not generate
- 'N_BINCL' or 'N_EINCL' stabs, and it outputs a single number for a
- type number.
+ also directs GCC to output a type number as a pair of a file
+ number and a type number within the file. Normally, GCC does not
+ generate `N_BINCL' or `N_EINCL' stabs, and it outputs a single
+ number for a type number.

File: gccint.info, Node: DBX Hooks, Next: File Names and DBX, Prev: DBX Options, Up: Debugging Info
@@ -36242,21 +36678,21 @@ These are hooks for DBX format.
A C statement to output DBX debugging information before code for
line number LINE of the current source file to the stdio stream
STREAM. COUNTER is the number of time the macro was invoked,
- including the current invocation; it is intended to generate unique
- labels in the assembly output.
+ including the current invocation; it is intended to generate
+ unique labels in the assembly output.
This macro should not be defined if the default output is correct,
or if it can be made correct by defining
- 'DBX_LINES_FUNCTION_RELATIVE'.
+ `DBX_LINES_FUNCTION_RELATIVE'.
-- Macro: NO_DBX_FUNCTION_END
Some stabs encapsulation formats (in particular ECOFF), cannot
- handle the '.stabs "",N_FUN,,0,0,Lscope-function-1' gdb dbx
+ handle the `.stabs "",N_FUN,,0,0,Lscope-function-1' gdb dbx
extension construct. On those machines, define this macro to turn
this feature off without disturbing the rest of the gdb extensions.
-- Macro: NO_DBX_BNSYM_ENSYM
- Some assemblers cannot handle the '.stabd BNSYM/ENSYM,0,0' gdb dbx
+ Some assemblers cannot handle the `.stabd BNSYM/ENSYM,0,0' gdb dbx
extension construct. On those machines, define this macro to turn
this feature off without disturbing the rest of the gdb extensions.
@@ -36278,9 +36714,9 @@ This describes file names in DBX format.
DBX debugging information is appropriate.
It may be necessary to refer to a label equal to the beginning of
- the text section. You can use 'assemble_name (stream,
- ltext_label_name)' to do so. If you do this, you must also set the
- variable USED_LTEXT_LABEL_NAME to 'true'.
+ the text section. You can use `assemble_name (stream,
+ ltext_label_name)' to do so. If you do this, you must also set
+ the variable USED_LTEXT_LABEL_NAME to `true'.
-- Macro: NO_DBX_MAIN_SOURCE_DIRECTORY
Define this macro, with value 1, if GCC should not emit an
@@ -36290,21 +36726,21 @@ This describes file names in DBX format.
-- Macro: NO_DBX_GCC_MARKER
Define this macro, with value 1, if GCC should not emit an
indication that this object file was compiled by GCC. The default
- is to emit an 'N_OPT' stab at the beginning of every source file,
- with 'gcc2_compiled.' for the string and value 0.
+ is to emit an `N_OPT' stab at the beginning of every source file,
+ with `gcc2_compiled.' for the string and value 0.
-- Macro: DBX_OUTPUT_MAIN_SOURCE_FILE_END (STREAM, NAME)
A C statement to output DBX debugging information at the end of
- compilation of the main source file NAME. Output should be written
- to the stdio stream STREAM.
+ compilation of the main source file NAME. Output should be
+ written to the stdio stream STREAM.
If you don't define this macro, nothing special is output at the
end of compilation, which is correct for most machines.
-- Macro: DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END
Define this macro _instead of_ defining
- 'DBX_OUTPUT_MAIN_SOURCE_FILE_END', if what needs to be output at
- the end of compilation is an 'N_SO' stab with an empty string,
+ `DBX_OUTPUT_MAIN_SOURCE_FILE_END', if what needs to be output at
+ the end of compilation is an `N_SO' stab with an empty string,
whose value is the highest absolute text address in the file.

@@ -36317,42 +36753,42 @@ Here are macros for SDB and DWARF output.
-- Macro: SDB_DEBUGGING_INFO
Define this macro if GCC should produce COFF-style debugging output
- for SDB in response to the '-g' option.
+ for SDB in response to the `-g' option.
-- Macro: DWARF2_DEBUGGING_INFO
Define this macro if GCC should produce dwarf version 2 format
- debugging output in response to the '-g' option.
+ debugging output in response to the `-g' option.
-- Target Hook: int TARGET_DWARF_CALLING_CONVENTION (const_tree
FUNCTION)
Define this to enable the dwarf attribute
- 'DW_AT_calling_convention' to be emitted for each function.
- Instead of an integer return the enum value for the 'DW_CC_'
+ `DW_AT_calling_convention' to be emitted for each function.
+ Instead of an integer return the enum value for the `DW_CC_'
tag.
To support optional call frame debugging information, you must also
- define 'INCOMING_RETURN_ADDR_RTX' and either set
- 'RTX_FRAME_RELATED_P' on the prologue insns if you use RTL for the
- prologue, or call 'dwarf2out_def_cfa' and 'dwarf2out_reg_save' as
- appropriate from 'TARGET_ASM_FUNCTION_PROLOGUE' if you don't.
+ define `INCOMING_RETURN_ADDR_RTX' and either set
+ `RTX_FRAME_RELATED_P' on the prologue insns if you use RTL for the
+ prologue, or call `dwarf2out_def_cfa' and `dwarf2out_reg_save' as
+ appropriate from `TARGET_ASM_FUNCTION_PROLOGUE' if you don't.
-- Macro: DWARF2_FRAME_INFO
Define this macro to a nonzero value if GCC should always output
- Dwarf 2 frame information. If 'TARGET_EXCEPT_UNWIND_INFO' (*note
- Exception Region Output::) returns 'UI_DWARF2', and exceptions are
- enabled, GCC will output this information not matter how you define
- 'DWARF2_FRAME_INFO'.
+ Dwarf 2 frame information. If `TARGET_EXCEPT_UNWIND_INFO' (*note
+ Exception Region Output::) returns `UI_DWARF2', and exceptions are
+ enabled, GCC will output this information not matter how you
+ define `DWARF2_FRAME_INFO'.
-- Target Hook: enum unwind_info_type TARGET_DEBUG_UNWIND_INFO (void)
This hook defines the mechanism that will be used for describing
frame unwind information to the debugger. Normally the hook will
- return 'UI_DWARF2' if DWARF 2 debug information is enabled, and
- return 'UI_NONE' otherwise.
+ return `UI_DWARF2' if DWARF 2 debug information is enabled, and
+ return `UI_NONE' otherwise.
- A target may return 'UI_DWARF2' even when DWARF 2 debug information
+ A target may return `UI_DWARF2' even when DWARF 2 debug information
is disabled in order to always output DWARF 2 frame information.
- A target may return 'UI_TARGET' if it has ABI specified unwind
+ A target may return `UI_TARGET' if it has ABI specified unwind
tables. This will suppress generation of the normal debug frame
unwind information.
@@ -36363,14 +36799,14 @@ Here are macros for SDB and DWARF output.
works.
-- Target Hook: bool TARGET_WANT_DEBUG_PUB_SECTIONS
- True if the '.debug_pubtypes' and '.debug_pubnames' sections should
- be emitted. These sections are not used on most platforms, and in
- particular GDB does not use them.
+ True if the `.debug_pubtypes' and `.debug_pubnames' sections
+ should be emitted. These sections are not used on most platforms,
+ and in particular GDB does not use them.
-- Target Hook: bool TARGET_FORCE_AT_COMP_DIR
- True if the 'DW_AT_comp_dir' attribute should be emitted for each
- compilation unit. This attribute is required for the darwin linker
- to emit debug information.
+ True if the `DW_AT_comp_dir' attribute should be emitted for each
+ compilation unit. This attribute is required for the darwin
+ linker to emit debug information.
-- Target Hook: bool TARGET_DELAY_SCHED2
True if sched2 is not to be run at its normal place. This usually
@@ -36401,8 +36837,8 @@ Here are macros for SDB and DWARF output.
-- Macro: ASM_OUTPUT_DWARF_PCREL (STREAM, SIZE, LABEL)
A C statement to issue assembly directives that create a
- self-relative reference to the given LABEL, using an integer of the
- given SIZE.
+ self-relative reference to the given LABEL, using an integer of
+ the given SIZE.
-- Macro: ASM_OUTPUT_DWARF_TABLE_REF (LABEL)
A C statement to issue assembly directives that create a reference
@@ -36416,17 +36852,17 @@ Here are macros for SDB and DWARF output.
DTP-relative reference to the given TLS symbol of the specified
size.
- -- Macro: PUT_SDB_ ...
+ -- Macro: PUT_SDB_...
Define these macros to override the assembler syntax for the
- special SDB assembler directives. See 'sdbout.c' for a list of
+ special SDB assembler directives. See `sdbout.c' for a list of
these macros and their arguments. If the standard syntax is used,
you need not define them yourself.
-- Macro: SDB_DELIM
Some assemblers do not support a semicolon as a delimiter, even
between SDB assembler directives. In that case, define this macro
- to be the delimiter to use (usually '\n'). It is not necessary to
- define a new set of 'PUT_SDB_OP' macros if this is the only change
+ to be the delimiter to use (usually `\n'). It is not necessary to
+ define a new set of `PUT_SDB_OP' macros if this is the only change
required.
-- Macro: SDB_ALLOW_UNKNOWN_REFERENCES
@@ -36442,7 +36878,7 @@ Here are macros for SDB and DWARF output.
-- Macro: SDB_OUTPUT_SOURCE_LINE (STREAM, LINE)
A C statement to output SDB debugging information before code for
line number LINE of the current source file to the stdio stream
- STREAM. The default is to emit an '.ln' directive.
+ STREAM. The default is to emit an `.ln' directive.

File: gccint.info, Node: VMS Debug, Prev: SDB and DWARF, Up: Debugging Info
@@ -36453,12 +36889,12 @@ File: gccint.info, Node: VMS Debug, Prev: SDB and DWARF, Up: Debugging Info
Here are macros for VMS debug format.
-- Macro: VMS_DEBUGGING_INFO
- Define this macro if GCC should produce debugging output for VMS in
- response to the '-g' option. The default behavior for VMS is to
- generate minimal debug info for a traceback in the absence of '-g'
- unless explicitly overridden with '-g0'. This behavior is
- controlled by 'TARGET_OPTION_OPTIMIZATION' and
- 'TARGET_OPTION_OVERRIDE'.
+ Define this macro if GCC should produce debugging output for VMS
+ in response to the `-g' option. The default behavior for VMS is
+ to generate minimal debug info for a traceback in the absence of
+ `-g' unless explicitly overridden with `-g0'. This behavior is
+ controlled by `TARGET_OPTION_OPTIMIZATION' and
+ `TARGET_OPTION_OVERRIDE'.

File: gccint.info, Node: Floating Point, Next: Mode Switching, Prev: Debugging Info, Up: Target Macros
@@ -36480,21 +36916,21 @@ the target's arithmetic. To ensure consistency, GCC always uses
emulation to work with floating point values, even when the host and
target floating point formats are identical.
- The following macros are provided by 'real.h' for the compiler to use.
+ The following macros are provided by `real.h' for the compiler to use.
All parts of the compiler which generate or optimize floating-point
calculations must use these macros. They may evaluate their operands
more than once, so operands must not have side effects.
-- Macro: REAL_VALUE_TYPE
The C data type to be used to hold a floating point value in the
- target machine's format. Typically this is a 'struct' containing
- an array of 'HOST_WIDE_INT', but all code should treat it as an
+ target machine's format. Typically this is a `struct' containing
+ an array of `HOST_WIDE_INT', but all code should treat it as an
opaque quantity.
-- Macro: int REAL_VALUES_EQUAL (REAL_VALUE_TYPE X, REAL_VALUE_TYPE Y)
Compares for equality the two values, X and Y. If the target
floating point format supports negative zeroes and/or NaNs,
- 'REAL_VALUES_EQUAL (-0.0, 0.0)' is true, and 'REAL_VALUES_EQUAL
+ `REAL_VALUES_EQUAL (-0.0, 0.0)' is true, and `REAL_VALUES_EQUAL
(NaN, NaN)' is false.
-- Macro: int REAL_VALUES_LESS (REAL_VALUE_TYPE X, REAL_VALUE_TYPE Y)
@@ -36530,13 +36966,13 @@ more than once, so operands must not have side effects.
X and Y, storing the result in OUTPUT (which must be a variable).
The operation to be performed is specified by CODE. Only the
- following codes are supported: 'PLUS_EXPR', 'MINUS_EXPR',
- 'MULT_EXPR', 'RDIV_EXPR', 'MAX_EXPR', 'MIN_EXPR'.
+ following codes are supported: `PLUS_EXPR', `MINUS_EXPR',
+ `MULT_EXPR', `RDIV_EXPR', `MAX_EXPR', `MIN_EXPR'.
- If 'REAL_ARITHMETIC' is asked to evaluate division by zero and the
+ If `REAL_ARITHMETIC' is asked to evaluate division by zero and the
target's floating point format cannot represent infinity, it will
- call 'abort'. Callers should check for this situation first, using
- 'MODE_HAS_INFINITIES'. *Note Storage Layout::.
+ call `abort'. Callers should check for this situation first, using
+ `MODE_HAS_INFINITIES'. *Note Storage Layout::.
-- Macro: REAL_VALUE_TYPE REAL_VALUE_NEGATE (REAL_VALUE_TYPE X)
Returns the negative of the floating point value X.
@@ -36553,53 +36989,53 @@ File: gccint.info, Node: Mode Switching, Next: Target Attributes, Prev: Float
The following macros control mode switching optimizations:
-- Macro: OPTIMIZE_MODE_SWITCHING (ENTITY)
- Define this macro if the port needs extra instructions inserted for
- mode switching in an optimizing compilation.
+ Define this macro if the port needs extra instructions inserted
+ for mode switching in an optimizing compilation.
For an example, the SH4 can perform both single and double
precision floating point operations, but to perform a single
precision operation, the FPSCR PR bit has to be cleared, while for
- a double precision operation, this bit has to be set. Changing the
- PR bit requires a general purpose register as a scratch register,
- hence these FPSCR sets have to be inserted before reload, i.e. you
- can't put this into instruction emitting or
- 'TARGET_MACHINE_DEPENDENT_REORG'.
+ a double precision operation, this bit has to be set. Changing
+ the PR bit requires a general purpose register as a scratch
+ register, hence these FPSCR sets have to be inserted before
+ reload, i.e. you can't put this into instruction emitting or
+ `TARGET_MACHINE_DEPENDENT_REORG'.
You can have multiple entities that are mode-switched, and select
at run time which entities actually need it.
- 'OPTIMIZE_MODE_SWITCHING' should return nonzero for any ENTITY that
- needs mode-switching. If you define this macro, you also have to
- define 'NUM_MODES_FOR_MODE_SWITCHING', 'TARGET_MODE_NEEDED',
- 'TARGET_MODE_PRIORITY' and 'TARGET_MODE_EMIT'.
- 'TARGET_MODE_AFTER', 'TARGET_MODE_ENTRY', and 'TARGET_MODE_EXIT'
- are optional.
+ `OPTIMIZE_MODE_SWITCHING' should return nonzero for any ENTITY
+ that needs mode-switching. If you define this macro, you also
+ have to define `NUM_MODES_FOR_MODE_SWITCHING',
+ `TARGET_MODE_NEEDED', `TARGET_MODE_PRIORITY' and
+ `TARGET_MODE_EMIT'. `TARGET_MODE_AFTER', `TARGET_MODE_ENTRY', and
+ `TARGET_MODE_EXIT' are optional.
-- Macro: NUM_MODES_FOR_MODE_SWITCHING
- If you define 'OPTIMIZE_MODE_SWITCHING', you have to define this as
+ If you define `OPTIMIZE_MODE_SWITCHING', you have to define this as
initializer for an array of integers. Each initializer element N
refers to an entity that needs mode switching, and specifies the
number of different modes that might need to be set for this
entity. The position of the initializer in the
- initializer--starting counting at zero--determines the integer that
- is used to refer to the mode-switched entity in question. In
+ initializer--starting counting at zero--determines the integer
+ that is used to refer to the mode-switched entity in question. In
macros that take mode arguments / yield a mode result, modes are
represented as numbers 0 ... N - 1. N is used to specify that no
mode switch is needed / supplied.
-- Target Hook: void TARGET_MODE_EMIT (int ENTITY, int MODE, int
PREV_MODE, HARD_REG_SET REGS_LIVE)
- Generate one or more insns to set ENTITY to MODE. HARD_REG_LIVE is
+ Generate one or more insns to set ENTITY to MODE. HARD_REG_LIVE is
the set of hard registers live at the point where the insn(s) are
- to be inserted. PREV_MOXDE indicates the mode to switch from.
- Sets of a lower numbered entity will be emitted before sets of a
- higher numbered entity to a mode of the same or lower priority.
+ to be inserted. PREV_MOXDE indicates the mode to switch from. Sets
+ of a lower numbered entity will be emitted before sets of a higher
+ numbered entity to a mode of the same or lower priority.
-- Target Hook: int TARGET_MODE_NEEDED (int ENTITY, rtx_insn *INSN)
ENTITY is an integer specifying a mode-switched entity. If
- 'OPTIMIZE_MODE_SWITCHING' is defined, you must define this macro to
- return an integer value not larger than the corresponding element
- in 'NUM_MODES_FOR_MODE_SWITCHING', to denote the mode that ENTITY
- must be switched into prior to the execution of INSN.
+ `OPTIMIZE_MODE_SWITCHING' is defined, you must define this macro
+ to return an integer value not larger than the corresponding
+ element in `NUM_MODES_FOR_MODE_SWITCHING', to denote the mode that
+ ENTITY must be switched into prior to the execution of INSN.
-- Target Hook: int TARGET_MODE_AFTER (int ENTITY, int MODE, rtx_insn
*INSN)
@@ -36610,41 +37046,41 @@ The following macros control mode switching optimizations:
-- Target Hook: int TARGET_MODE_ENTRY (int ENTITY)
If this macro is defined, it is evaluated for every ENTITY that
- needs mode switching. It should evaluate to an integer, which is a
- mode that ENTITY is assumed to be switched to at function entry.
- If 'TARGET_MODE_ENTRY' is defined then 'TARGET_MODE_EXIT' must be
+ needs mode switching. It should evaluate to an integer, which is
+ a mode that ENTITY is assumed to be switched to at function entry.
+ If `TARGET_MODE_ENTRY' is defined then `TARGET_MODE_EXIT' must be
defined.
-- Target Hook: int TARGET_MODE_EXIT (int ENTITY)
If this macro is defined, it is evaluated for every ENTITY that
- needs mode switching. It should evaluate to an integer, which is a
- mode that ENTITY is assumed to be switched to at function exit. If
- 'TARGET_MODE_EXIT' is defined then 'TARGET_MODE_ENTRY' must be
+ needs mode switching. It should evaluate to an integer, which is
+ a mode that ENTITY is assumed to be switched to at function exit.
+ If `TARGET_MODE_EXIT' is defined then `TARGET_MODE_ENTRY' must be
defined.
-- Target Hook: int TARGET_MODE_PRIORITY (int ENTITY, int N)
This macro specifies the order in which modes for ENTITY are
- processed. 0 is the highest priority,
- 'NUM_MODES_FOR_MODE_SWITCHING[ENTITY] - 1' the lowest. The value
+ processed. 0 is the highest priority,
+ `NUM_MODES_FOR_MODE_SWITCHING[ENTITY] - 1' the lowest. The value
of the macro should be an integer designating a mode for ENTITY.
- For any fixed ENTITY, 'mode_priority' (ENTITY, N) shall be a
- bijection in 0 ... 'num_modes_for_mode_switching[ENTITY] - 1'.
+ For any fixed ENTITY, `mode_priority' (ENTITY, N) shall be a
+ bijection in 0 ... `num_modes_for_mode_switching[ENTITY] - 1'.

File: gccint.info, Node: Target Attributes, Next: Emulated TLS, Prev: Mode Switching, Up: Target Macros
-17.24 Defining target-specific uses of '__attribute__'
+17.24 Defining target-specific uses of `__attribute__'
======================================================
Target-specific attributes may be defined for functions, data and types.
These are described using the following target hooks; they also need to
-be documented in 'extend.texi'.
+be documented in `extend.texi'.
-- Target Hook: const struct attribute_spec * TARGET_ATTRIBUTE_TABLE
- If defined, this target hook points to an array of 'struct
- attribute_spec' (defined in 'tree.h') specifying the machine
- specific attributes for this target and some of the restrictions on
- the entities to which these attributes are applied and the
+ If defined, this target hook points to an array of `struct
+ attribute_spec' (defined in `tree.h') specifying the machine
+ specific attributes for this target and some of the restrictions
+ on the entities to which these attributes are applied and the
arguments they take.
-- Target Hook: bool TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P (const_tree
@@ -36658,10 +37094,10 @@ be documented in 'extend.texi'.
-- Target Hook: int TARGET_COMP_TYPE_ATTRIBUTES (const_tree TYPE1,
const_tree TYPE2)
If defined, this target hook is a function which returns zero if
- the attributes on TYPE1 and TYPE2 are incompatible, one if they are
- compatible, and two if they are nearly compatible (which causes a
- warning to be generated). If this is not defined, machine-specific
- attributes are supposed always to be compatible.
+ the attributes on TYPE1 and TYPE2 are incompatible, one if they
+ are compatible, and two if they are nearly compatible (which
+ causes a warning to be generated). If this is not defined,
+ machine-specific attributes are supposed always to be compatible.
-- Target Hook: void TARGET_SET_DEFAULT_TYPE_ATTRIBUTES (tree TYPE)
If defined, this target hook is a function which assigns default
@@ -36671,132 +37107,132 @@ be documented in 'extend.texi'.
TYPE2)
Define this target hook if the merging of type attributes needs
special handling. If defined, the result is a list of the combined
- 'TYPE_ATTRIBUTES' of TYPE1 and TYPE2. It is assumed that
- 'comptypes' has already been called and returned 1. This function
- may call 'merge_attributes' to handle machine-independent merging.
+ `TYPE_ATTRIBUTES' of TYPE1 and TYPE2. It is assumed that
+ `comptypes' has already been called and returned 1. This function
+ may call `merge_attributes' to handle machine-independent merging.
-- Target Hook: tree TARGET_MERGE_DECL_ATTRIBUTES (tree OLDDECL, tree
NEWDECL)
Define this target hook if the merging of decl attributes needs
special handling. If defined, the result is a list of the combined
- 'DECL_ATTRIBUTES' of OLDDECL and NEWDECL. NEWDECL is a duplicate
+ `DECL_ATTRIBUTES' of OLDDECL and NEWDECL. NEWDECL is a duplicate
declaration of OLDDECL. Examples of when this is needed are when
one attribute overrides another, or when an attribute is nullified
by a subsequent definition. This function may call
- 'merge_attributes' to handle machine-independent merging.
+ `merge_attributes' to handle machine-independent merging.
- If the only target-specific handling you require is 'dllimport' for
- Microsoft Windows targets, you should define the macro
- 'TARGET_DLLIMPORT_DECL_ATTRIBUTES' to '1'. The compiler will then
- define a function called 'merge_dllimport_decl_attributes' which
+ If the only target-specific handling you require is `dllimport'
+ for Microsoft Windows targets, you should define the macro
+ `TARGET_DLLIMPORT_DECL_ATTRIBUTES' to `1'. The compiler will then
+ define a function called `merge_dllimport_decl_attributes' which
can then be defined as the expansion of
- 'TARGET_MERGE_DECL_ATTRIBUTES'. You can also add
- 'handle_dll_attribute' in the attribute table for your port to
- perform initial processing of the 'dllimport' and 'dllexport'
- attributes. This is done in 'i386/cygwin.h' and 'i386/i386.c', for
- example.
+ `TARGET_MERGE_DECL_ATTRIBUTES'. You can also add
+ `handle_dll_attribute' in the attribute table for your port to
+ perform initial processing of the `dllimport' and `dllexport'
+ attributes. This is done in `i386/cygwin.h' and `i386/i386.c',
+ for example.
-- Target Hook: bool TARGET_VALID_DLLIMPORT_ATTRIBUTE_P (const_tree
DECL)
- DECL is a variable or function with '__attribute__((dllimport))'
+ DECL is a variable or function with `__attribute__((dllimport))'
specified. Use this hook if the target needs to add extra
- validation checks to 'handle_dll_attribute'.
+ validation checks to `handle_dll_attribute'.
-- Macro: TARGET_DECLSPEC
Define this macro to a nonzero value if you want to treat
- '__declspec(X)' as equivalent to '__attribute((X))'. By default,
+ `__declspec(X)' as equivalent to `__attribute((X))'. By default,
this behavior is enabled only for targets that define
- 'TARGET_DLLIMPORT_DECL_ATTRIBUTES'. The current implementation of
- '__declspec' is via a built-in macro, but you should not rely on
+ `TARGET_DLLIMPORT_DECL_ATTRIBUTES'. The current implementation of
+ `__declspec' is via a built-in macro, but you should not rely on
this implementation detail.
-- Target Hook: void TARGET_INSERT_ATTRIBUTES (tree NODE, tree
*ATTR_PTR)
- Define this target hook if you want to be able to add attributes to
- a decl when it is being created. This is normally useful for back
- ends which wish to implement a pragma by using the attributes which
- correspond to the pragma's effect. The NODE argument is the decl
- which is being created. The ATTR_PTR argument is a pointer to the
- attribute list for this decl. The list itself should not be
- modified, since it may be shared with other decls, but attributes
- may be chained on the head of the list and '*ATTR_PTR' modified to
- point to the new attributes, or a copy of the list may be made if
- further changes are needed.
+ Define this target hook if you want to be able to add attributes
+ to a decl when it is being created. This is normally useful for
+ back ends which wish to implement a pragma by using the attributes
+ which correspond to the pragma's effect. The NODE argument is the
+ decl which is being created. The ATTR_PTR argument is a pointer
+ to the attribute list for this decl. The list itself should not
+ be modified, since it may be shared with other decls, but
+ attributes may be chained on the head of the list and `*ATTR_PTR'
+ modified to point to the new attributes, or a copy of the list may
+ be made if further changes are needed.
-- Target Hook: bool TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P (const_tree
FNDECL)
- This target hook returns 'true' if it is OK to inline FNDECL into
+ This target hook returns `true' if it is OK to inline FNDECL into
the current function, despite its having target-specific
- attributes, 'false' otherwise. By default, if a function has a
+ attributes, `false' otherwise. By default, if a function has a
target specific attribute attached to it, it will not be inlined.
- -- Target Hook: bool TARGET_OPTION_VALID_ATTRIBUTE_P (tree FNDECL, tree
- NAME, tree ARGS, int FLAGS)
- This hook is called to parse 'attribute(target("..."))', which
+ -- Target Hook: bool TARGET_OPTION_VALID_ATTRIBUTE_P (tree FNDECL,
+ tree NAME, tree ARGS, int FLAGS)
+ This hook is called to parse `attribute(target("..."))', which
allows setting target-specific options on individual functions.
These function-specific options may differ from the options
- specified on the command line. The hook should return 'true' if
+ specified on the command line. The hook should return `true' if
the options are valid.
- The hook should set the 'DECL_FUNCTION_SPECIFIC_TARGET' field in
+ The hook should set the `DECL_FUNCTION_SPECIFIC_TARGET' field in
the function declaration to hold a pointer to a target-specific
- 'struct cl_target_option' structure.
+ `struct cl_target_option' structure.
-- Target Hook: void TARGET_OPTION_SAVE (struct cl_target_option *PTR,
struct gcc_options *OPTS)
This hook is called to save any additional target-specific
- information in the 'struct cl_target_option' structure for
- function-specific options from the 'struct gcc_options' structure.
+ information in the `struct cl_target_option' structure for
+ function-specific options from the `struct gcc_options' structure.
*Note Option file format::.
-- Target Hook: void TARGET_OPTION_RESTORE (struct gcc_options *OPTS,
struct cl_target_option *PTR)
This hook is called to restore any additional target-specific
- information in the 'struct cl_target_option' structure for
- function-specific options to the 'struct gcc_options' structure.
+ information in the `struct cl_target_option' structure for
+ function-specific options to the `struct gcc_options' structure.
-- Target Hook: void TARGET_OPTION_POST_STREAM_IN (struct
cl_target_option *PTR)
This hook is called to update target-specific information in the
- 'struct cl_target_option' structure after it is streamed in from
+ `struct cl_target_option' structure after it is streamed in from
LTO bytecode.
-- Target Hook: void TARGET_OPTION_PRINT (FILE *FILE, int INDENT,
struct cl_target_option *PTR)
This hook is called to print any additional target-specific
- information in the 'struct cl_target_option' structure for
+ information in the `struct cl_target_option' structure for
function-specific options.
-- Target Hook: bool TARGET_OPTION_PRAGMA_PARSE (tree ARGS, tree
POP_TARGET)
- This target hook parses the options for '#pragma GCC target', which
+ This target hook parses the options for `#pragma GCC target', which
sets the target-specific options for functions that occur later in
- the input stream. The options accepted should be the same as those
- handled by the 'TARGET_OPTION_VALID_ATTRIBUTE_P' hook.
+ the input stream. The options accepted should be the same as
+ those handled by the `TARGET_OPTION_VALID_ATTRIBUTE_P' hook.
-- Target Hook: void TARGET_OPTION_OVERRIDE (void)
- Sometimes certain combinations of command options do not make sense
- on a particular target machine. You can override the hook
- 'TARGET_OPTION_OVERRIDE' to take account of this. This hooks is
+ Sometimes certain combinations of command options do not make
+ sense on a particular target machine. You can override the hook
+ `TARGET_OPTION_OVERRIDE' to take account of this. This hooks is
called once just after all the command options have been parsed.
Don't use this hook to turn on various extra optimizations for
- '-O'. That is what 'TARGET_OPTION_OPTIMIZATION' is for.
+ `-O'. That is what `TARGET_OPTION_OPTIMIZATION' is for.
If you need to do something whenever the optimization level is
changed via the optimize attribute or pragma, see
- 'TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE'
+ `TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE'
-- Target Hook: bool TARGET_OPTION_FUNCTION_VERSIONS (tree DECL1, tree
DECL2)
- This target hook returns 'true' if DECL1 and DECL2 are versions of
+ This target hook returns `true' if DECL1 and DECL2 are versions of
the same function. DECL1 and DECL2 are function versions if and
only if they have the same function signature and different target
specific attributes, that is, they are compiled for different
target machines.
-- Target Hook: bool TARGET_CAN_INLINE_P (tree CALLER, tree CALLEE)
- This target hook returns 'false' if the CALLER function cannot
+ This target hook returns `false' if the CALLER function cannot
inline CALLEE, based on target specific information. By default,
inlining is not allowed if the callee function has function
specific target options and the caller does not use the same
@@ -36817,8 +37253,8 @@ layer.
The emulation layer works by creating a control object for every TLS
object. To access the TLS object, a lookup function is provided which,
-when given the address of the control object, will return the address of
-the current thread's instance of the TLS object.
+when given the address of the control object, will return the address
+of the current thread's instance of the TLS object.
-- Target Hook: const char * TARGET_EMUTLS_GET_ADDRESS
Contains the name of the helper function that uses a TLS control
@@ -36828,40 +37264,40 @@ the current thread's instance of the TLS object.
-- Target Hook: const char * TARGET_EMUTLS_REGISTER_COMMON
Contains the name of the helper function that should be used at
program startup to register TLS objects that are implicitly
- initialized to zero. If this is 'NULL', all TLS objects will have
+ initialized to zero. If this is `NULL', all TLS objects will have
explicit initializers. The default causes libgcc's emulated TLS
registration function to be used.
-- Target Hook: const char * TARGET_EMUTLS_VAR_SECTION
Contains the name of the section in which TLS control variables
- should be placed. The default of 'NULL' allows these to be placed
+ should be placed. The default of `NULL' allows these to be placed
in any section.
-- Target Hook: const char * TARGET_EMUTLS_TMPL_SECTION
Contains the name of the section in which TLS initializers should
- be placed. The default of 'NULL' allows these to be placed in any
+ be placed. The default of `NULL' allows these to be placed in any
section.
-- Target Hook: const char * TARGET_EMUTLS_VAR_PREFIX
Contains the prefix to be prepended to TLS control variable names.
- The default of 'NULL' uses a target-specific prefix.
+ The default of `NULL' uses a target-specific prefix.
-- Target Hook: const char * TARGET_EMUTLS_TMPL_PREFIX
Contains the prefix to be prepended to TLS initializer objects.
- The default of 'NULL' uses a target-specific prefix.
+ The default of `NULL' uses a target-specific prefix.
-- Target Hook: tree TARGET_EMUTLS_VAR_FIELDS (tree TYPE, tree *NAME)
Specifies a function that generates the FIELD_DECLs for a TLS
control object type. TYPE is the RECORD_TYPE the fields are for
and NAME should be filled with the structure tag, if the default of
- '__emutls_object' is unsuitable. The default creates a type
+ `__emutls_object' is unsuitable. The default creates a type
suitable for libgcc's emulated TLS function.
-- Target Hook: tree TARGET_EMUTLS_VAR_INIT (tree VAR, tree DECL, tree
TMPL_ADDR)
Specifies a function that generates the CONSTRUCTOR to initialize a
- TLS control object. VAR is the TLS control object, DECL is the TLS
- object and TMPL_ADDR is the address of the initializer. The
+ TLS control object. VAR is the TLS control object, DECL is the
+ TLS object and TMPL_ADDR is the address of the initializer. The
default initializes libgcc's emulated TLS control object.
-- Target Hook: bool TARGET_EMUTLS_VAR_ALIGN_FIXED
@@ -36870,7 +37306,7 @@ the current thread's instance of the TLS object.
optimize single objects. The default is false.
-- Target Hook: bool TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS
- Specifies whether a DWARF 'DW_OP_form_tls_address' location
+ Specifies whether a DWARF `DW_OP_form_tls_address' location
descriptor may be used to describe emulated TLS control objects.

@@ -36891,7 +37327,7 @@ and memory using asm-ized variables. For example:
("c0r1" is the default name of register 1 in coprocessor 0; alternate
names may be added as described below, or the default names may be
-overridden entirely in 'SUBTARGET_CONDITIONAL_REGISTER_USAGE'.)
+overridden entirely in `SUBTARGET_CONDITIONAL_REGISTER_USAGE'.)
Coprocessor registers are assumed to be epilogue-used; sets to them
will be preserved even if it does not appear that the register is used
@@ -36909,31 +37345,31 @@ File: gccint.info, Node: PCH Target, Next: C++ ABI, Prev: MIPS Coprocessors,
-- Target Hook: void * TARGET_GET_PCH_VALIDITY (size_t *SZ)
This hook returns a pointer to the data needed by
- 'TARGET_PCH_VALID_P' and sets '*SZ' to the size of the data in
+ `TARGET_PCH_VALID_P' and sets `*SZ' to the size of the data in
bytes.
-- Target Hook: const char * TARGET_PCH_VALID_P (const void *DATA,
size_t SZ)
This hook checks whether the options used to create a PCH file are
- compatible with the current settings. It returns 'NULL' if so and
+ compatible with the current settings. It returns `NULL' if so and
a suitable error message if not. Error messages will be presented
- to the user and must be localized using '_(MSG)'.
+ to the user and must be localized using `_(MSG)'.
- DATA is the data that was returned by 'TARGET_GET_PCH_VALIDITY'
+ DATA is the data that was returned by `TARGET_GET_PCH_VALIDITY'
when the PCH file was created and SZ is the size of that data in
bytes. It's safe to assume that the data was created by the same
version of the compiler, so no format checking is needed.
- The default definition of 'default_pch_valid_p' should be suitable
+ The default definition of `default_pch_valid_p' should be suitable
for most targets.
-- Target Hook: const char * TARGET_CHECK_PCH_TARGET_FLAGS (int
PCH_FLAGS)
If this hook is nonnull, the default implementation of
- 'TARGET_PCH_VALID_P' will use it to check for compatible values of
- 'target_flags'. PCH_FLAGS specifies the value that 'target_flags'
- had when the PCH file was created. The return value is the same as
- for 'TARGET_PCH_VALID_P'.
+ `TARGET_PCH_VALID_P' will use it to check for compatible values of
+ `target_flags'. PCH_FLAGS specifies the value that `target_flags'
+ had when the PCH file was created. The return value is the same
+ as for `TARGET_PCH_VALID_P'.
-- Target Hook: void TARGET_PREPARE_PCH_SAVE (void)
Called before writing out a PCH file. If the target has some
@@ -36954,20 +37390,20 @@ File: gccint.info, Node: C++ ABI, Next: Named Address Spaces, Prev: PCH Targe
-- Target Hook: bool TARGET_CXX_GUARD_MASK_BIT (void)
This hook determines how guard variables are used. It should
- return 'false' (the default) if the first byte should be used. A
- return value of 'true' indicates that only the least significant
+ return `false' (the default) if the first byte should be used. A
+ return value of `true' indicates that only the least significant
bit should be used.
-- Target Hook: tree TARGET_CXX_GET_COOKIE_SIZE (tree TYPE)
This hook returns the size of the cookie to use when allocating an
array whose elements have the indicated TYPE. Assumes that it is
- already known that a cookie is needed. The default is 'max(sizeof
+ already known that a cookie is needed. The default is `max(sizeof
(size_t), alignof(type))', as defined in section 2.7 of the
IA64/Generic C++ ABI.
-- Target Hook: bool TARGET_CXX_COOKIE_HAS_SIZE (void)
- This hook should return 'true' if the element size should be stored
- in array cookies. The default is to return 'false'.
+ This hook should return `true' if the element size should be
+ stored in array cookies. The default is to return `false'.
-- Target Hook: int TARGET_CXX_IMPORT_EXPORT_CLASS (tree TYPE, int
IMPORT_EXPORT)
@@ -36979,9 +37415,9 @@ File: gccint.info, Node: C++ ABI, Next: Named Address Spaces, Prev: PCH Targe
the backend's targeted operating system.
-- Target Hook: bool TARGET_CXX_CDTOR_RETURNS_THIS (void)
- This hook should return 'true' if constructors and destructors
- return the address of the object created/destroyed. The default is
- to return 'false'.
+ This hook should return `true' if constructors and destructors
+ return the address of the object created/destroyed. The default
+ is to return `false'.
-- Target Hook: bool TARGET_CXX_KEY_METHOD_MAY_BE_INLINE (void)
This hook returns true if the key method for a class (i.e., the
@@ -36991,7 +37427,7 @@ File: gccint.info, Node: C++ ABI, Next: Named Address Spaces, Prev: PCH Targe
function so long as the function is not declared inline in the
class definition. Under some variants of the ABI, an inline
function can never be the key method. The default is to return
- 'true'.
+ `true'.
-- Target Hook: void TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY (tree
DECL)
@@ -37000,7 +37436,7 @@ File: gccint.info, Node: C++ ABI, Next: Named Address Spaces, Prev: PCH Targe
external linkage in this translation unit. No ELF visibility has
been explicitly specified. If the target needs to specify a
visibility other than that of the containing class, use this hook
- to set 'DECL_VISIBILITY' and 'DECL_VISIBILITY_SPECIFIED'.
+ to set `DECL_VISIBILITY' and `DECL_VISIBILITY_SPECIFIED'.
-- Target Hook: bool TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT (void)
This hook returns true (the default) if virtual tables and other
@@ -37015,26 +37451,26 @@ File: gccint.info, Node: C++ ABI, Next: Named Address Spaces, Prev: PCH Targe
be COMDAT, false if it should not be COMDAT.
-- Target Hook: bool TARGET_CXX_USE_AEABI_ATEXIT (void)
- This hook returns true if '__aeabi_atexit' (as defined by the ARM
+ This hook returns true if `__aeabi_atexit' (as defined by the ARM
EABI) should be used to register static destructors when
- '-fuse-cxa-atexit' is in effect. The default is to return false to
- use '__cxa_atexit'.
+ `-fuse-cxa-atexit' is in effect. The default is to return false
+ to use `__cxa_atexit'.
-- Target Hook: bool TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT (void)
- This hook returns true if the target 'atexit' function can be used
- in the same manner as '__cxa_atexit' to register C++ static
- destructors. This requires that 'atexit'-registered functions in
+ This hook returns true if the target `atexit' function can be used
+ in the same manner as `__cxa_atexit' to register C++ static
+ destructors. This requires that `atexit'-registered functions in
shared libraries are run in the correct order when the libraries
- are unloaded. The default is to return false.
+ are unloaded. The default is to return false.
-- Target Hook: void TARGET_CXX_ADJUST_CLASS_AT_DEFINITION (tree TYPE)
- TYPE is a C++ class (i.e., RECORD_TYPE or UNION_TYPE) that has just
- been defined. Use this hook to make adjustments to the class (eg,
- tweak visibility or perform any other required target
+ TYPE is a C++ class (i.e., RECORD_TYPE or UNION_TYPE) that has
+ just been defined. Use this hook to make adjustments to the class
+ (eg, tweak visibility or perform any other required target
modifications).
-- Target Hook: tree TARGET_CXX_DECL_MANGLING_CONTEXT (const_tree DECL)
- Return target-specific mangling context of DECL or 'NULL_TREE'.
+ Return target-specific mangling context of DECL or `NULL_TREE'.

File: gccint.info, Node: Named Address Spaces, Next: Misc, Prev: C++ ABI, Up: Target Macros
@@ -37043,22 +37479,22 @@ File: gccint.info, Node: Named Address Spaces, Next: Misc, Prev: C++ ABI, Up
=============================================
The draft technical report of the ISO/IEC JTC1 S22 WG14 N1275 standards
-committee, 'Programming Languages - C - Extensions to support embedded
+committee, `Programming Languages - C - Extensions to support embedded
processors', specifies a syntax for embedded processors to specify
alternate address spaces. You can configure a GCC port to support
section 5.1 of the draft report to add support for address spaces other
than the default address space. These address spaces are new keywords
-that are similar to the 'volatile' and 'const' type attributes.
+that are similar to the `volatile' and `const' type attributes.
Pointers to named address spaces can have a different size than
pointers to the generic address space.
- For example, the SPU port uses the '__ea' address space to refer to
+ For example, the SPU port uses the `__ea' address space to refer to
memory in the host processor, rather than memory local to the SPU
-processor. Access to memory in the '__ea' address space involves
+processor. Access to memory in the `__ea' address space involves
issuing DMA operations to move data between the host processor and the
-local processor memory address space. Pointers in the '__ea' address
-space are either 32 bits or 64 bits based on the '-mea32' or '-mea64'
+local processor memory address space. Pointers in the `__ea' address
+space are either 32 bits or 64 bits based on the `-mea32' or `-mea64'
switches (native SPU pointers are always 32 bits).
Internally, address spaces are represented as a small integer in the
@@ -37066,8 +37502,8 @@ range 0 to 15 with address space 0 being reserved for the generic
address space.
To register a named address space qualifier keyword with the C front
-end, the target may call the 'c_register_addr_space' routine. For
-example, the SPU port uses the following to declare '__ea' as the
+end, the target may call the `c_register_addr_space' routine. For
+example, the SPU port uses the following to declare `__ea' as the
keyword for named address space #1:
#define ADDR_SPACE_EA 1
c_register_addr_space ("__ea", ADDR_SPACE_EA);
@@ -37076,40 +37512,41 @@ keyword for named address space #1:
(addr_space_t ADDRESS_SPACE)
Define this to return the machine mode to use for pointers to
ADDRESS_SPACE if the target supports named address spaces. The
- default version of this hook returns 'ptr_mode' for the generic
+ default version of this hook returns `ptr_mode' for the generic
address space only.
-- Target Hook: machine_mode TARGET_ADDR_SPACE_ADDRESS_MODE
(addr_space_t ADDRESS_SPACE)
Define this to return the machine mode to use for addresses in
ADDRESS_SPACE if the target supports named address spaces. The
- default version of this hook returns 'Pmode' for the generic
+ default version of this hook returns `Pmode' for the generic
address space only.
- -- Target Hook: bool TARGET_ADDR_SPACE_VALID_POINTER_MODE (machine_mode
- MODE, addr_space_t AS)
+ -- Target Hook: bool TARGET_ADDR_SPACE_VALID_POINTER_MODE
+ (machine_mode MODE, addr_space_t AS)
Define this to return nonzero if the port can handle pointers with
machine mode MODE to address space AS. This target hook is the
- same as the 'TARGET_VALID_POINTER_MODE' target hook, except that it
- includes explicit named address space support. The default version
- of this hook returns true for the modes returned by either the
- 'TARGET_ADDR_SPACE_POINTER_MODE' or
- 'TARGET_ADDR_SPACE_ADDRESS_MODE' target hooks for the given address
- space.
+ same as the `TARGET_VALID_POINTER_MODE' target hook, except that
+ it includes explicit named address space support. The default
+ version of this hook returns true for the modes returned by either
+ the `TARGET_ADDR_SPACE_POINTER_MODE' or
+ `TARGET_ADDR_SPACE_ADDRESS_MODE' target hooks for the given
+ address space.
-- Target Hook: bool TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P
(machine_mode MODE, rtx EXP, bool STRICT, addr_space_t AS)
Define this to return true if EXP is a valid address for mode MODE
in the named address space AS. The STRICT parameter says whether
strict addressing is in effect after reload has finished. This
- target hook is the same as the 'TARGET_LEGITIMATE_ADDRESS_P' target
- hook, except that it includes explicit named address space support.
+ target hook is the same as the `TARGET_LEGITIMATE_ADDRESS_P'
+ target hook, except that it includes explicit named address space
+ support.
-- Target Hook: rtx TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS (rtx X, rtx
OLDX, machine_mode MODE, addr_space_t AS)
Define this to modify an invalid address X to be a valid address
with mode MODE in the named address space AS. This target hook is
- the same as the 'TARGET_LEGITIMIZE_ADDRESS' target hook, except
+ the same as the `TARGET_LEGITIMIZE_ADDRESS' target hook, except
that it includes explicit named address space support.
-- Target Hook: bool TARGET_ADDR_SPACE_SUBSET_P (addr_space_t SUBSET,
@@ -37128,7 +37565,7 @@ keyword for named address space #1:
a new pointer expression with type TO_TYPE that points to a
different named address space. When this hook it called, it is
guaranteed that one of the two address spaces is a subset of the
- other, as determined by the 'TARGET_ADDR_SPACE_SUBSET_P' target
+ other, as determined by the `TARGET_ADDR_SPACE_SUBSET_P' target
hook.

@@ -37143,8 +37580,8 @@ Here are several miscellaneous parameters.
Define this boolean macro to indicate whether or not your
architecture has conditional branches that can span all of memory.
It is used in conjunction with an optimization that partitions hot
- and cold basic blocks into separate sections of the executable. If
- this macro is set to false, gcc will convert any conditional
+ and cold basic blocks into separate sections of the executable.
+ If this macro is set to false, gcc will convert any conditional
branches that attempt to cross between sections into unconditional
branches or indirect jumps.
@@ -37162,11 +37599,11 @@ Here are several miscellaneous parameters.
elements of a jump-table should have.
-- Macro: CASE_VECTOR_SHORTEN_MODE (MIN_OFFSET, MAX_OFFSET, BODY)
- Optional: return the preferred mode for an 'addr_diff_vec' when the
- minimum and maximum offset are known. If you define this, it
+ Optional: return the preferred mode for an `addr_diff_vec' when
+ the minimum and maximum offset are known. If you define this, it
enables extra code in branch shortening to deal with
- 'addr_diff_vec'. To make this work, you also have to define
- 'INSN_ALIGN' and make the alignment for 'addr_diff_vec' explicit.
+ `addr_diff_vec'. To make this work, you also have to define
+ `INSN_ALIGN' and make the alignment for `addr_diff_vec' explicit.
The BODY argument is provided so that the offset_unsigned and scale
flags can be updated.
@@ -37174,14 +37611,14 @@ Here are several miscellaneous parameters.
Define this macro to be a C expression to indicate when jump-tables
should contain relative addresses. You need not define this macro
if jump-tables never contain relative addresses, or jump-tables
- should contain relative addresses only when '-fPIC' or '-fPIC' is
+ should contain relative addresses only when `-fPIC' or `-fPIC' is
in effect.
-- Target Hook: unsigned int TARGET_CASE_VALUES_THRESHOLD (void)
This function return the smallest number of different values for
which it is best to use a jump-table instead of a tree of
conditional branches. The default is four for machines with a
- 'casesi' instruction and five otherwise. This is best for most
+ `casesi' instruction and five otherwise. This is best for most
machines.
-- Macro: WORD_REGISTER_OPERATIONS
@@ -37192,30 +37629,30 @@ Here are several miscellaneous parameters.
-- Macro: LOAD_EXTEND_OP (MEM_MODE)
Define this macro to be a C expression indicating when insns that
- read memory in MEM_MODE, an integral mode narrower than a word, set
- the bits outside of MEM_MODE to be either the sign-extension or the
- zero-extension of the data read. Return 'SIGN_EXTEND' for values
- of MEM_MODE for which the insn sign-extends, 'ZERO_EXTEND' for
- which it zero-extends, and 'UNKNOWN' for other modes.
+ read memory in MEM_MODE, an integral mode narrower than a word,
+ set the bits outside of MEM_MODE to be either the sign-extension
+ or the zero-extension of the data read. Return `SIGN_EXTEND' for
+ values of MEM_MODE for which the insn sign-extends, `ZERO_EXTEND'
+ for which it zero-extends, and `UNKNOWN' for other modes.
This macro is not called with MEM_MODE non-integral or with a width
- greater than or equal to 'BITS_PER_WORD', so you may return any
+ greater than or equal to `BITS_PER_WORD', so you may return any
value in this case. Do not define this macro if it would always
- return 'UNKNOWN'. On machines where this macro is defined, you
- will normally define it as the constant 'SIGN_EXTEND' or
- 'ZERO_EXTEND'.
+ return `UNKNOWN'. On machines where this macro is defined, you
+ will normally define it as the constant `SIGN_EXTEND' or
+ `ZERO_EXTEND'.
- You may return a non-'UNKNOWN' value even if for some hard
+ You may return a non-`UNKNOWN' value even if for some hard
registers the sign extension is not performed, if for the
- 'REGNO_REG_CLASS' of these hard registers
- 'CANNOT_CHANGE_MODE_CLASS' returns nonzero when the FROM mode is
+ `REGNO_REG_CLASS' of these hard registers
+ `CANNOT_CHANGE_MODE_CLASS' returns nonzero when the FROM mode is
MEM_MODE and the TO mode is any integral mode larger than this but
- not larger than 'word_mode'.
+ not larger than `word_mode'.
- You must return 'UNKNOWN' if for some hard registers that allow
- this mode, 'CANNOT_CHANGE_MODE_CLASS' says that they cannot change
- to 'word_mode', but that they can change to another integral mode
- that is larger then MEM_MODE but still smaller than 'word_mode'.
+ You must return `UNKNOWN' if for some hard registers that allow
+ this mode, `CANNOT_CHANGE_MODE_CLASS' says that they cannot change
+ to `word_mode', but that they can change to another integral mode
+ that is larger then MEM_MODE but still smaller than `word_mode'.
-- Macro: SHORT_IMMEDIATES_SIGN_EXTEND
Define this macro if loading short immediate values into registers
@@ -37223,8 +37660,8 @@ Here are several miscellaneous parameters.
-- Target Hook: unsigned int TARGET_MIN_DIVISIONS_FOR_RECIP_MUL
(machine_mode MODE)
- When '-ffast-math' is in effect, GCC tries to optimize divisions by
- the same divisor, by turning them into multiplications by the
+ When `-ffast-math' is in effect, GCC tries to optimize divisions
+ by the same divisor, by turning them into multiplications by the
reciprocal. This target hook specifies the minimum number of
divisions that should be there for GCC to perform the optimization
for a variable of mode MODE. The default implementation returns 3
@@ -37239,22 +37676,22 @@ Here are several miscellaneous parameters.
-- Macro: MAX_MOVE_MAX
The maximum number of bytes that a single instruction can move
quickly between memory and registers or between two memory
- locations. If this is undefined, the default is 'MOVE_MAX'.
+ locations. If this is undefined, the default is `MOVE_MAX'.
Otherwise, it is the constant value that is the largest value that
- 'MOVE_MAX' can have at run-time.
+ `MOVE_MAX' can have at run-time.
-- Macro: SHIFT_COUNT_TRUNCATED
A C expression that is nonzero if on this machine the number of
bits actually used for the count of a shift operation is equal to
- the number of bits needed to represent the size of the object being
- shifted. When this macro is nonzero, the compiler will assume that
- it is safe to omit a sign-extend, zero-extend, and certain bitwise
- 'and' instructions that truncates the count of a shift operation.
- On machines that have instructions that act on bit-fields at
- variable positions, which may include 'bit test' instructions, a
- nonzero 'SHIFT_COUNT_TRUNCATED' also enables deletion of
- truncations of the values that serve as arguments to bit-field
- instructions.
+ the number of bits needed to represent the size of the object
+ being shifted. When this macro is nonzero, the compiler will
+ assume that it is safe to omit a sign-extend, zero-extend, and
+ certain bitwise `and' instructions that truncates the count of a
+ shift operation. On machines that have instructions that act on
+ bit-fields at variable positions, which may include `bit test'
+ instructions, a nonzero `SHIFT_COUNT_TRUNCATED' also enables
+ deletion of truncations of the values that serve as arguments to
+ bit-field instructions.
If both types of instructions truncate the count (for shifts) and
position (for bit-field operations), or if no variable-position
@@ -37262,12 +37699,12 @@ Here are several miscellaneous parameters.
However, on some machines, such as the 80386 and the 680x0,
truncation only applies to shift operations and not the (real or
- pretended) bit-field operations. Define 'SHIFT_COUNT_TRUNCATED' to
- be zero on such machines. Instead, add patterns to the 'md' file
- that include the implied truncation of the shift instructions.
+ pretended) bit-field operations. Define `SHIFT_COUNT_TRUNCATED'
+ to be zero on such machines. Instead, add patterns to the `md'
+ file that include the implied truncation of the shift instructions.
- You need not define this macro if it would always have the value of
- zero.
+ You need not define this macro if it would always have the value
+ of zero.
-- Target Hook: unsigned HOST_WIDE_INT TARGET_SHIFT_TRUNCATION_MASK
(machine_mode MODE)
@@ -37282,14 +37719,14 @@ Here are several miscellaneous parameters.
should return 0. A return value of 0 indicates that no particular
behavior is guaranteed.
- Note that, unlike 'SHIFT_COUNT_TRUNCATED', this function does _not_
- apply to general shift rtxes; it applies only to instructions that
- are generated by the named shift patterns.
+ Note that, unlike `SHIFT_COUNT_TRUNCATED', this function does
+ _not_ apply to general shift rtxes; it applies only to instructions
+ that are generated by the named shift patterns.
The default implementation of this function returns
- 'GET_MODE_BITSIZE (MODE) - 1' if 'SHIFT_COUNT_TRUNCATED' and 0
+ `GET_MODE_BITSIZE (MODE) - 1' if `SHIFT_COUNT_TRUNCATED' and 0
otherwise. This definition is always safe, but if
- 'SHIFT_COUNT_TRUNCATED' is false, and some shift patterns
+ `SHIFT_COUNT_TRUNCATED' is false, and some shift patterns
nevertheless truncate the shift count, you may get better code by
overriding it.
@@ -37301,43 +37738,43 @@ Here are several miscellaneous parameters.
On many machines, this expression can be 1.
- When 'TRULY_NOOP_TRUNCATION' returns 1 for a pair of sizes for
- modes for which 'MODES_TIEABLE_P' is 0, suboptimal code can result.
- If this is the case, making 'TRULY_NOOP_TRUNCATION' return 0 in
+ When `TRULY_NOOP_TRUNCATION' returns 1 for a pair of sizes for
+ modes for which `MODES_TIEABLE_P' is 0, suboptimal code can result.
+ If this is the case, making `TRULY_NOOP_TRUNCATION' return 0 in
such cases may improve things.
-- Target Hook: int TARGET_MODE_REP_EXTENDED (machine_mode MODE,
machine_mode REP_MODE)
The representation of an integral mode can be such that the values
- are always extended to a wider integral mode. Return 'SIGN_EXTEND'
- if values of MODE are represented in sign-extended form to
- REP_MODE. Return 'UNKNOWN' otherwise. (Currently, none of the
- targets use zero-extended representation this way so unlike
- 'LOAD_EXTEND_OP', 'TARGET_MODE_REP_EXTENDED' is expected to return
- either 'SIGN_EXTEND' or 'UNKNOWN'. Also no target extends MODE to
+ are always extended to a wider integral mode. Return
+ `SIGN_EXTEND' if values of MODE are represented in sign-extended
+ form to REP_MODE. Return `UNKNOWN' otherwise. (Currently, none
+ of the targets use zero-extended representation this way so unlike
+ `LOAD_EXTEND_OP', `TARGET_MODE_REP_EXTENDED' is expected to return
+ either `SIGN_EXTEND' or `UNKNOWN'. Also no target extends MODE to
REP_MODE so that REP_MODE is not the next widest integral mode and
currently we take advantage of this fact.)
- Similarly to 'LOAD_EXTEND_OP' you may return a non-'UNKNOWN' value
- even if the extension is not performed on certain hard registers as
- long as for the 'REGNO_REG_CLASS' of these hard registers
- 'CANNOT_CHANGE_MODE_CLASS' returns nonzero.
+ Similarly to `LOAD_EXTEND_OP' you may return a non-`UNKNOWN' value
+ even if the extension is not performed on certain hard registers
+ as long as for the `REGNO_REG_CLASS' of these hard registers
+ `CANNOT_CHANGE_MODE_CLASS' returns nonzero.
- Note that 'TARGET_MODE_REP_EXTENDED' and 'LOAD_EXTEND_OP' describe
- two related properties. If you define 'TARGET_MODE_REP_EXTENDED
- (mode, word_mode)' you probably also want to define 'LOAD_EXTEND_OP
- (mode)' to return the same type of extension.
+ Note that `TARGET_MODE_REP_EXTENDED' and `LOAD_EXTEND_OP' describe
+ two related properties. If you define `TARGET_MODE_REP_EXTENDED
+ (mode, word_mode)' you probably also want to define
+ `LOAD_EXTEND_OP (mode)' to return the same type of extension.
- In order to enforce the representation of 'mode',
- 'TRULY_NOOP_TRUNCATION' should return false when truncating to
- 'mode'.
+ In order to enforce the representation of `mode',
+ `TRULY_NOOP_TRUNCATION' should return false when truncating to
+ `mode'.
-- Macro: STORE_FLAG_VALUE
A C expression describing the value returned by a comparison
operator with an integral mode and stored by a store-flag
- instruction ('cstoreMODE4') when the condition is true. This
- description must apply to _all_ the 'cstoreMODE4' patterns and all
- the comparison operators whose results have a 'MODE_INT' mode.
+ instruction (`cstoreMODE4') when the condition is true. This
+ description must apply to _all_ the `cstoreMODE4' patterns and all
+ the comparison operators whose results have a `MODE_INT' mode.
A value of 1 or -1 means that the instruction implementing the
comparison operator returns exactly 1 or -1 when the comparison is
@@ -37345,17 +37782,17 @@ Here are several miscellaneous parameters.
indicates which bits of the result are guaranteed to be 1 when the
comparison is true. This value is interpreted in the mode of the
comparison operation, which is given by the mode of the first
- operand in the 'cstoreMODE4' pattern. Either the low bit or the
- sign bit of 'STORE_FLAG_VALUE' be on. Presently, only those bits
+ operand in the `cstoreMODE4' pattern. Either the low bit or the
+ sign bit of `STORE_FLAG_VALUE' be on. Presently, only those bits
are used by the compiler.
- If 'STORE_FLAG_VALUE' is neither 1 or -1, the compiler will
+ If `STORE_FLAG_VALUE' is neither 1 or -1, the compiler will
generate code that depends only on the specified bits. It can also
replace comparison operators with equivalent operations if they
cause the required bits to be set, even if the remaining bits are
undefined. For example, on a machine whose comparison operators
- return an 'SImode' value and where 'STORE_FLAG_VALUE' is defined as
- '0x80000000', saying that just the sign bit is relevant, the
+ return an `SImode' value and where `STORE_FLAG_VALUE' is defined as
+ `0x80000000', saying that just the sign bit is relevant, the
expression
(ne:SI (and:SI X (const_int POWER-OF-2)) (const_int 0))
@@ -37364,24 +37801,24 @@ Here are several miscellaneous parameters.
(ashift:SI X (const_int N))
- where N is the appropriate shift count to move the bit being tested
- into the sign bit.
+ where N is the appropriate shift count to move the bit being
+ tested into the sign bit.
There is no way to describe a machine that always sets the
- low-order bit for a true value, but does not guarantee the value of
- any other bits, but we do not know of any machine that has such an
- instruction. If you are trying to port GCC to such a machine,
+ low-order bit for a true value, but does not guarantee the value
+ of any other bits, but we do not know of any machine that has such
+ an instruction. If you are trying to port GCC to such a machine,
include an instruction to perform a logical-and of the result with
1 in the pattern for the comparison operators and let us know at
<gcc@gcc.gnu.org>.
Often, a machine will have multiple instructions that obtain a
value from a comparison (or the condition codes). Here are rules
- to guide the choice of value for 'STORE_FLAG_VALUE', and hence the
+ to guide the choice of value for `STORE_FLAG_VALUE', and hence the
instructions to be used:
* Use the shortest sequence that yields a valid definition for
- 'STORE_FLAG_VALUE'. It is more efficient for the compiler to
+ `STORE_FLAG_VALUE'. It is more efficient for the compiler to
"normalize" the value (convert it to, e.g., 1 or 0) than for
the comparison operators to do so because there may be
opportunities to combine the normalization with other
@@ -37391,71 +37828,71 @@ Here are several miscellaneous parameters.
being slightly preferred on machines with expensive jumps and
1 preferred on other machines.
- * As a second choice, choose a value of '0x80000001' if
+ * As a second choice, choose a value of `0x80000001' if
instructions exist that set both the sign and low-order bits
but do not define the others.
- * Otherwise, use a value of '0x80000000'.
+ * Otherwise, use a value of `0x80000000'.
Many machines can produce both the value chosen for
- 'STORE_FLAG_VALUE' and its negation in the same number of
+ `STORE_FLAG_VALUE' and its negation in the same number of
instructions. On those machines, you should also define a pattern
for those cases, e.g., one matching
(set A (neg:M (ne:M B C)))
- Some machines can also perform 'and' or 'plus' operations on
+ Some machines can also perform `and' or `plus' operations on
condition code values with less instructions than the corresponding
- 'cstoreMODE4' insn followed by 'and' or 'plus'. On those machines,
- define the appropriate patterns. Use the names 'incscc' and
- 'decscc', respectively, for the patterns which perform 'plus' or
- 'minus' operations on condition code values. See 'rs6000.md' for
- some examples. The GNU Superoptimizer can be used to find such
- instruction sequences on other machines.
+ `cstoreMODE4' insn followed by `and' or `plus'. On those
+ machines, define the appropriate patterns. Use the names `incscc'
+ and `decscc', respectively, for the patterns which perform `plus'
+ or `minus' operations on condition code values. See `rs6000.md'
+ for some examples. The GNU Superoptimizer can be used to find
+ such instruction sequences on other machines.
If this macro is not defined, the default value, 1, is used. You
- need not define 'STORE_FLAG_VALUE' if the machine has no store-flag
+ need not define `STORE_FLAG_VALUE' if the machine has no store-flag
instructions, or if the value generated by these instructions is 1.
-- Macro: FLOAT_STORE_FLAG_VALUE (MODE)
- A C expression that gives a nonzero 'REAL_VALUE_TYPE' value that is
+ A C expression that gives a nonzero `REAL_VALUE_TYPE' value that is
returned when comparison operators with floating-point results are
true. Define this macro on machines that have comparison
- operations that return floating-point values. If there are no such
- operations, do not define this macro.
+ operations that return floating-point values. If there are no
+ such operations, do not define this macro.
-- Macro: VECTOR_STORE_FLAG_VALUE (MODE)
A C expression that gives a rtx representing the nonzero true
element for vector comparisons. The returned rtx should be valid
- for the inner mode of MODE which is guaranteed to be a vector mode.
- Define this macro on machines that have vector comparison
+ for the inner mode of MODE which is guaranteed to be a vector
+ mode. Define this macro on machines that have vector comparison
operations that return a vector result. If there are no such
operations, do not define this macro. Typically, this macro is
- defined as 'const1_rtx' or 'constm1_rtx'. This macro may return
- 'NULL_RTX' to prevent the compiler optimizing such vector
+ defined as `const1_rtx' or `constm1_rtx'. This macro may return
+ `NULL_RTX' to prevent the compiler optimizing such vector
comparison operations for the given mode.
-- Macro: CLZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
-- Macro: CTZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
A C expression that indicates whether the architecture defines a
- value for 'clz' or 'ctz' with a zero operand. A result of '0'
- indicates the value is undefined. If the value is defined for only
- the RTL expression, the macro should evaluate to '1'; if the value
- applies also to the corresponding optab entry (which is normally
- the case if it expands directly into the corresponding RTL), then
- the macro should evaluate to '2'. In the cases where the value is
- defined, VALUE should be set to this value.
-
- If this macro is not defined, the value of 'clz' or 'ctz' at zero
+ value for `clz' or `ctz' with a zero operand. A result of `0'
+ indicates the value is undefined. If the value is defined for
+ only the RTL expression, the macro should evaluate to `1'; if the
+ value applies also to the corresponding optab entry (which is
+ normally the case if it expands directly into the corresponding
+ RTL), then the macro should evaluate to `2'. In the cases where
+ the value is defined, VALUE should be set to this value.
+
+ If this macro is not defined, the value of `clz' or `ctz' at zero
is assumed to be undefined.
- This macro must be defined if the target's expansion for 'ffs'
+ This macro must be defined if the target's expansion for `ffs'
relies on a particular value to get correct results. Otherwise it
is not necessary, though it may be used to optimize some corner
- cases, and to provide a default expansion for the 'ffs' optab.
+ cases, and to provide a default expansion for the `ffs' optab.
- Note that regardless of this macro the "definedness" of 'clz' and
- 'ctz' at zero do _not_ extend to the builtin functions visible to
+ Note that regardless of this macro the "definedness" of `clz' and
+ `ctz' at zero do _not_ extend to the builtin functions visible to
the user. Thus one may be free to adjust the value at will to
match the target expansion of these operations without fear of
breaking the API.
@@ -37463,139 +37900,140 @@ Here are several miscellaneous parameters.
-- Macro: Pmode
An alias for the machine mode for pointers. On most machines,
define this to be the integer mode corresponding to the width of a
- hardware pointer; 'SImode' on 32-bit machine or 'DImode' on 64-bit
+ hardware pointer; `SImode' on 32-bit machine or `DImode' on 64-bit
machines. On some machines you must define this to be one of the
- partial integer modes, such as 'PSImode'.
+ partial integer modes, such as `PSImode'.
- The width of 'Pmode' must be at least as large as the value of
- 'POINTER_SIZE'. If it is not equal, you must define the macro
- 'POINTERS_EXTEND_UNSIGNED' to specify how pointers are extended to
- 'Pmode'.
+ The width of `Pmode' must be at least as large as the value of
+ `POINTER_SIZE'. If it is not equal, you must define the macro
+ `POINTERS_EXTEND_UNSIGNED' to specify how pointers are extended to
+ `Pmode'.
-- Macro: FUNCTION_MODE
An alias for the machine mode used for memory references to
- functions being called, in 'call' RTL expressions. On most CISC
+ functions being called, in `call' RTL expressions. On most CISC
machines, where an instruction can begin at any byte address, this
- should be 'QImode'. On most RISC machines, where all instructions
+ should be `QImode'. On most RISC machines, where all instructions
have fixed size and alignment, this should be a mode with the same
size and alignment as the machine instruction words - typically
- 'SImode' or 'HImode'.
+ `SImode' or `HImode'.
-- Macro: STDC_0_IN_SYSTEM_HEADERS
- In normal operation, the preprocessor expands '__STDC__' to the
+ In normal operation, the preprocessor expands `__STDC__' to the
constant 1, to signify that GCC conforms to ISO Standard C. On
some hosts, like Solaris, the system compiler uses a different
- convention, where '__STDC__' is normally 0, but is 1 if the user
+ convention, where `__STDC__' is normally 0, but is 1 if the user
specifies strict conformance to the C Standard.
- Defining 'STDC_0_IN_SYSTEM_HEADERS' makes GNU CPP follows the host
- convention when processing system header files, but when processing
- user files '__STDC__' will always expand to 1.
+ Defining `STDC_0_IN_SYSTEM_HEADERS' makes GNU CPP follows the host
+ convention when processing system header files, but when
+ processing user files `__STDC__' will always expand to 1.
-- C Target Hook: const char * TARGET_C_PREINCLUDE (void)
- Define this hook to return the name of a header file to be included
- at the start of all compilations, as if it had been included with
- '#include <FILE>'. If this hook returns 'NULL', or is not defined,
- or the header is not found, or if the user specifies
- '-ffreestanding' or '-nostdinc', no header is included.
+ Define this hook to return the name of a header file to be
+ included at the start of all compilations, as if it had been
+ included with `#include <FILE>'. If this hook returns `NULL', or
+ is not defined, or the header is not found, or if the user
+ specifies `-ffreestanding' or `-nostdinc', no header is included.
- This hook can be used together with a header provided by the system
- C library to implement ISO C requirements for certain macros to be
- predefined that describe properties of the whole implementation
- rather than just the compiler.
+ This hook can be used together with a header provided by the
+ system C library to implement ISO C requirements for certain
+ macros to be predefined that describe properties of the whole
+ implementation rather than just the compiler.
-- C Target Hook: bool TARGET_CXX_IMPLICIT_EXTERN_C (const char*)
Define this hook to add target-specific C++ implicit extern C
- functions. If this function returns true for the name of a
+ functions. If this function returns true for the name of a
file-scope function, that function implicitly gets extern "C"
- linkage rather than whatever language linkage the declaration would
- normally have. An example of such function is WinMain on Win32
- targets.
+ linkage rather than whatever language linkage the declaration
+ would normally have. An example of such function is WinMain on
+ Win32 targets.
-- Macro: NO_IMPLICIT_EXTERN_C
- Define this macro if the system header files support C++ as well as
- C. This macro inhibits the usual method of using system header
+ Define this macro if the system header files support C++ as well
+ as C. This macro inhibits the usual method of using system header
files in C++, which is to pretend that the file's contents are
- enclosed in 'extern "C" {...}'.
+ enclosed in `extern "C" {...}'.
-- Macro: REGISTER_TARGET_PRAGMAS ()
Define this macro if you want to implement any target-specific
pragmas. If defined, it is a C expression which makes a series of
- calls to 'c_register_pragma' or 'c_register_pragma_with_expansion'
+ calls to `c_register_pragma' or `c_register_pragma_with_expansion'
for each pragma. The macro may also do any setup required for the
pragmas.
- The primary reason to define this macro is to provide compatibility
- with other compilers for the same target. In general, we
- discourage definition of target-specific pragmas for GCC.
+ The primary reason to define this macro is to provide
+ compatibility with other compilers for the same target. In
+ general, we discourage definition of target-specific pragmas for
+ GCC.
If the pragma can be implemented by attributes then you should
- consider defining the target hook 'TARGET_INSERT_ATTRIBUTES' as
+ consider defining the target hook `TARGET_INSERT_ATTRIBUTES' as
well.
Preprocessor macros that appear on pragma lines are not expanded.
- All '#pragma' directives that do not match any registered pragma
+ All `#pragma' directives that do not match any registered pragma
are silently ignored, unless the user specifies
- '-Wunknown-pragmas'.
+ `-Wunknown-pragmas'.
-- Function: void c_register_pragma (const char *SPACE, const char
*NAME, void (*CALLBACK) (struct cpp_reader *))
-- Function: void c_register_pragma_with_expansion (const char *SPACE,
const char *NAME, void (*CALLBACK) (struct cpp_reader *))
-
- Each call to 'c_register_pragma' or
- 'c_register_pragma_with_expansion' establishes one pragma. The
+ Each call to `c_register_pragma' or
+ `c_register_pragma_with_expansion' establishes one pragma. The
CALLBACK routine will be called when the preprocessor encounters a
pragma of the form
#pragma [SPACE] NAME ...
- SPACE is the case-sensitive namespace of the pragma, or 'NULL' to
+ SPACE is the case-sensitive namespace of the pragma, or `NULL' to
put the pragma in the global namespace. The callback routine
receives PFILE as its first argument, which can be passed on to
- cpplib's functions if necessary. You can lex tokens after the NAME
- by calling 'pragma_lex'. Tokens that are not read by the callback
- will be silently ignored. The end of the line is indicated by a
- token of type 'CPP_EOF'. Macro expansion occurs on the arguments
- of pragmas registered with 'c_register_pragma_with_expansion' but
- not on the arguments of pragmas registered with
- 'c_register_pragma'.
-
- Note that the use of 'pragma_lex' is specific to the C and C++
+ cpplib's functions if necessary. You can lex tokens after the
+ NAME by calling `pragma_lex'. Tokens that are not read by the
+ callback will be silently ignored. The end of the line is
+ indicated by a token of type `CPP_EOF'. Macro expansion occurs on
+ the arguments of pragmas registered with
+ `c_register_pragma_with_expansion' but not on the arguments of
+ pragmas registered with `c_register_pragma'.
+
+ Note that the use of `pragma_lex' is specific to the C and C++
compilers. It will not work in the Java or Fortran compilers, or
- any other language compilers for that matter. Thus if 'pragma_lex'
- is going to be called from target-specific code, it must only be
- done so when building the C and C++ compilers. This can be done by
- defining the variables 'c_target_objs' and 'cxx_target_objs' in the
- target entry in the 'config.gcc' file. These variables should name
- the target-specific, language-specific object file which contains
- the code that uses 'pragma_lex'. Note it will also be necessary to
- add a rule to the makefile fragment pointed to by 'tmake_file' that
- shows how to build this object file.
+ any other language compilers for that matter. Thus if
+ `pragma_lex' is going to be called from target-specific code, it
+ must only be done so when building the C and C++ compilers. This
+ can be done by defining the variables `c_target_objs' and
+ `cxx_target_objs' in the target entry in the `config.gcc' file.
+ These variables should name the target-specific, language-specific
+ object file which contains the code that uses `pragma_lex'. Note
+ it will also be necessary to add a rule to the makefile fragment
+ pointed to by `tmake_file' that shows how to build this object
+ file.
-- Macro: HANDLE_PRAGMA_PACK_WITH_EXPANSION
Define this macro if macros should be expanded in the arguments of
- '#pragma pack'.
+ `#pragma pack'.
-- Macro: TARGET_DEFAULT_PACK_STRUCT
If your target requires a structure packing default other than 0
(meaning the machine default), define this macro to the necessary
- value (in bytes). This must be a value that would also be valid to
- use with '#pragma pack()' (that is, a small power of two).
+ value (in bytes). This must be a value that would also be valid
+ to use with `#pragma pack()' (that is, a small power of two).
-- Macro: DOLLARS_IN_IDENTIFIERS
- Define this macro to control use of the character '$' in identifier
- names for the C family of languages. 0 means '$' is not allowed by
- default; 1 means it is allowed. 1 is the default; there is no need
- to define this macro in that case.
+ Define this macro to control use of the character `$' in
+ identifier names for the C family of languages. 0 means `$' is
+ not allowed by default; 1 means it is allowed. 1 is the default;
+ there is no need to define this macro in that case.
-- Macro: INSN_SETS_ARE_DELAYED (INSN)
Define this macro as a C expression that is nonzero if it is safe
for the delay slot scheduler to place instructions in the delay
slot of INSN, even if they appear to use a resource set or
- clobbered in INSN. INSN is always a 'jump_insn' or an 'insn'; GCC
- knows that every 'call_insn' has this behavior. On machines where
- some 'insn' or 'jump_insn' is really a function call and hence has
+ clobbered in INSN. INSN is always a `jump_insn' or an `insn'; GCC
+ knows that every `call_insn' has this behavior. On machines where
+ some `insn' or `jump_insn' is really a function call and hence has
this behavior, you should define this macro.
You need not define this macro if it would always return zero.
@@ -37604,104 +38042,103 @@ Here are several miscellaneous parameters.
Define this macro as a C expression that is nonzero if it is safe
for the delay slot scheduler to place instructions in the delay
slot of INSN, even if they appear to set or clobber a resource
- referenced in INSN. INSN is always a 'jump_insn' or an 'insn'. On
- machines where some 'insn' or 'jump_insn' is really a function call
- and its operands are registers whose use is actually in the
- subroutine it calls, you should define this macro. Doing so allows
- the delay slot scheduler to move instructions which copy arguments
- into the argument registers into the delay slot of INSN.
+ referenced in INSN. INSN is always a `jump_insn' or an `insn'.
+ On machines where some `insn' or `jump_insn' is really a function
+ call and its operands are registers whose use is actually in the
+ subroutine it calls, you should define this macro. Doing so
+ allows the delay slot scheduler to move instructions which copy
+ arguments into the argument registers into the delay slot of INSN.
You need not define this macro if it would always return zero.
-- Macro: MULTIPLE_SYMBOL_SPACES
Define this macro as a C expression that is nonzero if, in some
- cases, global symbols from one translation unit may not be bound to
- undefined symbols in another translation unit without user
+ cases, global symbols from one translation unit may not be bound
+ to undefined symbols in another translation unit without user
intervention. For instance, under Microsoft Windows symbols must
be explicitly imported from shared libraries (DLLs).
You need not define this macro if it would always evaluate to zero.
- -- Target Hook: tree TARGET_MD_ASM_CLOBBERS (tree OUTPUTS, tree INPUTS,
- tree CLOBBERS)
- This target hook should add to CLOBBERS 'STRING_CST' trees for any
+ -- Target Hook: tree TARGET_MD_ASM_CLOBBERS (tree OUTPUTS, tree
+ INPUTS, tree CLOBBERS)
+ This target hook should add to CLOBBERS `STRING_CST' trees for any
hard regs the port wishes to automatically clobber for an asm. It
- should return the result of the last 'tree_cons' used to add a
+ should return the result of the last `tree_cons' used to add a
clobber. The OUTPUTS, INPUTS and CLOBBER lists are the
corresponding parameters to the asm and may be inspected to avoid
clobbering a register that is an input or output of the asm. You
- can use 'tree_overlaps_hard_reg_set', declared in 'tree.h', to test
+ can use `tree_overlaps_hard_reg_set', declared in `tree.h', to test
for overlap with regards to asm-declared registers.
-- Macro: MATH_LIBRARY
- Define this macro as a C string constant for the linker argument to
- link in the system math library, minus the initial '"-l"', or '""'
- if the target does not have a separate math library.
+ Define this macro as a C string constant for the linker argument
+ to link in the system math library, minus the initial `"-l"', or
+ `""' if the target does not have a separate math library.
- You need only define this macro if the default of '"m"' is wrong.
+ You need only define this macro if the default of `"m"' is wrong.
-- Macro: LIBRARY_PATH_ENV
Define this macro as a C string constant for the environment
variable that specifies where the linker should look for libraries.
- You need only define this macro if the default of '"LIBRARY_PATH"'
+ You need only define this macro if the default of `"LIBRARY_PATH"'
is wrong.
-- Macro: TARGET_POSIX_IO
Define this macro if the target supports the following POSIX file
- functions, access, mkdir and file locking with fcntl / F_SETLKW.
- Defining 'TARGET_POSIX_IO' will enable the test coverage code to
+ functions, access, mkdir and file locking with fcntl / F_SETLKW.
+ Defining `TARGET_POSIX_IO' will enable the test coverage code to
use file locking when exiting a program, which avoids race
- conditions if the program has forked. It will also create
+ conditions if the program has forked. It will also create
directories at run-time for cross-profiling.
-- Macro: MAX_CONDITIONAL_EXECUTE
-
A C expression for the maximum number of instructions to execute
via conditional execution instructions instead of a branch. A
- value of 'BRANCH_COST'+1 is the default if the machine does not use
- cc0, and 1 if it does use cc0.
+ value of `BRANCH_COST'+1 is the default if the machine does not
+ use cc0, and 1 if it does use cc0.
-- Macro: IFCVT_MODIFY_TESTS (CE_INFO, TRUE_EXPR, FALSE_EXPR)
- Used if the target needs to perform machine-dependent modifications
- on the conditionals used for turning basic blocks into
- conditionally executed code. CE_INFO points to a data structure,
- 'struct ce_if_block', which contains information about the
- currently processed blocks. TRUE_EXPR and FALSE_EXPR are the tests
- that are used for converting the then-block and the else-block,
- respectively. Set either TRUE_EXPR or FALSE_EXPR to a null pointer
- if the tests cannot be converted.
+ Used if the target needs to perform machine-dependent
+ modifications on the conditionals used for turning basic blocks
+ into conditionally executed code. CE_INFO points to a data
+ structure, `struct ce_if_block', which contains information about
+ the currently processed blocks. TRUE_EXPR and FALSE_EXPR are the
+ tests that are used for converting the then-block and the
+ else-block, respectively. Set either TRUE_EXPR or FALSE_EXPR to a
+ null pointer if the tests cannot be converted.
-- Macro: IFCVT_MODIFY_MULTIPLE_TESTS (CE_INFO, BB, TRUE_EXPR,
FALSE_EXPR)
- Like 'IFCVT_MODIFY_TESTS', but used when converting more
- complicated if-statements into conditions combined by 'and' and
- 'or' operations. BB contains the basic block that contains the
+ Like `IFCVT_MODIFY_TESTS', but used when converting more
+ complicated if-statements into conditions combined by `and' and
+ `or' operations. BB contains the basic block that contains the
test that is currently being processed and about to be turned into
a condition.
-- Macro: IFCVT_MODIFY_INSN (CE_INFO, PATTERN, INSN)
A C expression to modify the PATTERN of an INSN that is to be
converted to conditional execution format. CE_INFO points to a
- data structure, 'struct ce_if_block', which contains information
+ data structure, `struct ce_if_block', which contains information
about the currently processed blocks.
-- Macro: IFCVT_MODIFY_FINAL (CE_INFO)
- A C expression to perform any final machine dependent modifications
- in converting code to conditional execution. The involved basic
- blocks can be found in the 'struct ce_if_block' structure that is
- pointed to by CE_INFO.
+ A C expression to perform any final machine dependent
+ modifications in converting code to conditional execution. The
+ involved basic blocks can be found in the `struct ce_if_block'
+ structure that is pointed to by CE_INFO.
-- Macro: IFCVT_MODIFY_CANCEL (CE_INFO)
A C expression to cancel any machine dependent modifications in
converting code to conditional execution. The involved basic
- blocks can be found in the 'struct ce_if_block' structure that is
+ blocks can be found in the `struct ce_if_block' structure that is
pointed to by CE_INFO.
-- Macro: IFCVT_MACHDEP_INIT (CE_INFO)
A C expression to initialize any machine specific data for
- if-conversion of the if-block in the 'struct ce_if_block' structure
- that is pointed to by CE_INFO.
+ if-conversion of the if-block in the `struct ce_if_block'
+ structure that is pointed to by CE_INFO.
-- Target Hook: void TARGET_MACHINE_DEPENDENT_REORG (void)
If non-null, this hook performs a target-specific pass over the
@@ -37723,16 +38160,16 @@ Here are several miscellaneous parameters.
functions that need to be defined. It should be a function that
performs the necessary setup.
- Machine specific built-in functions can be useful to expand special
- machine instructions that would otherwise not normally be generated
- because they have no equivalent in the source language (for
- example, SIMD vector instructions or prefetch instructions).
+ Machine specific built-in functions can be useful to expand
+ special machine instructions that would otherwise not normally be
+ generated because they have no equivalent in the source language
+ (for example, SIMD vector instructions or prefetch instructions).
To create a built-in function, call the function
- 'lang_hooks.builtin_function' which is defined by the language
+ `lang_hooks.builtin_function' which is defined by the language
front end. You can use any type nodes set up by
- 'build_common_tree_nodes'; only language front ends that use those
- two functions will call 'TARGET_INIT_BUILTINS'.
+ `build_common_tree_nodes'; only language front ends that use those
+ two functions will call `TARGET_INIT_BUILTINS'.
-- Target Hook: tree TARGET_BUILTIN_DECL (unsigned CODE, bool
INITIALIZE_P)
@@ -37741,14 +38178,13 @@ Here are several miscellaneous parameters.
returns the builtin function declaration for the builtin function
code CODE. If there is no such builtin and it cannot be
initialized at this time if INITIALIZE_P is true the function
- should return 'NULL_TREE'. If CODE is out of range the function
- should return 'error_mark_node'.
+ should return `NULL_TREE'. If CODE is out of range the function
+ should return `error_mark_node'.
-- Target Hook: rtx TARGET_EXPAND_BUILTIN (tree EXP, rtx TARGET, rtx
SUBTARGET, machine_mode MODE, int IGNORE)
-
Expand a call to a machine specific built-in function that was set
- up by 'TARGET_INIT_BUILTINS'. EXP is the expression for the
+ up by `TARGET_INIT_BUILTINS'. EXP is the expression for the
function call; the result should go to TARGET if that is
convenient, and have mode MODE if that is convenient. SUBTARGET
may be used as the target for computing one of EXP's operands.
@@ -37761,127 +38197,133 @@ Here are several miscellaneous parameters.
return fndecl of function implementing generic builtin whose code
is passed in FCODE. Currently following built-in functions are
obtained using this hook:
+
-- Built-in Function: __bounds_type __chkp_bndmk (const void *LB,
size_t SIZE)
- Function code - BUILT_IN_CHKP_BNDMK. This built-in function is
- used by Pointer Bounds Checker to create bound values. LB
+ Function code - BUILT_IN_CHKP_BNDMK. This built-in function
+ is used by Pointer Bounds Checker to create bound values. LB
holds low bound of the resulting bounds. SIZE holds size of
created bounds.
-- Built-in Function: void __chkp_bndstx (const void *PTR,
__bounds_type B, const void **LOC)
- Function code - 'BUILT_IN_CHKP_BNDSTX'. This built-in
+ Function code - `BUILT_IN_CHKP_BNDSTX'. This built-in
function is used by Pointer Bounds Checker to store bounds B
for pointer PTR when PTR is stored by address LOC.
-- Built-in Function: __bounds_type __chkp_bndldx (const void
**LOC, const void *PTR)
- Function code - 'BUILT_IN_CHKP_BNDLDX'. This built-in
+ Function code - `BUILT_IN_CHKP_BNDLDX'. This built-in
function is used by Pointer Bounds Checker to get bounds of
pointer PTR loaded by address LOC.
-- Built-in Function: void __chkp_bndcl (const void *PTR,
__bounds_type B)
- Function code - 'BUILT_IN_CHKP_BNDCL'. This built-in function
- is used by Pointer Bounds Checker to perform check for pointer
- PTR against lower bound of bounds B.
+ Function code - `BUILT_IN_CHKP_BNDCL'. This built-in
+ function is used by Pointer Bounds Checker to perform check
+ for pointer PTR against lower bound of bounds B.
-- Built-in Function: void __chkp_bndcu (const void *PTR,
__bounds_type B)
- Function code - 'BUILT_IN_CHKP_BNDCU'. This built-in function
- is used by Pointer Bounds Checker to perform check for pointer
- PTR against upper bound of bounds B.
+ Function code - `BUILT_IN_CHKP_BNDCU'. This built-in
+ function is used by Pointer Bounds Checker to perform check
+ for pointer PTR against upper bound of bounds B.
-- Built-in Function: __bounds_type __chkp_bndret (void *PTR)
- Function code - 'BUILT_IN_CHKP_BNDRET'. This built-in
+ Function code - `BUILT_IN_CHKP_BNDRET'. This built-in
function is used by Pointer Bounds Checker to obtain bounds
returned by a call statement. PTR passed to built-in is
- 'SSA_NAME' returned by the call.
+ `SSA_NAME' returned by the call.
-- Built-in Function: __bounds_type __chkp_intersect
(__bounds_type B1, __bounds_type B2)
- Function code - 'BUILT_IN_CHKP_INTERSECT'. This built-in
+ Function code - `BUILT_IN_CHKP_INTERSECT'. This built-in
function returns intersection of bounds B1 and B2.
-- Built-in Function: __bounds_type __chkp_narrow (const void
*PTR, __bounds_type B, size_t S)
- Function code - 'BUILT_IN_CHKP_NARROW'. This built-in
+ Function code - `BUILT_IN_CHKP_NARROW'. This built-in
function returns intersection of bounds B and [PTR, PTR + S -
- '1'].
+ `1'].
-- Built-in Function: size_t __chkp_sizeof (const void *PTR)
- Function code - 'BUILT_IN_CHKP_SIZEOF'. This built-in
- function returns size of object referenced by PTR. PTR is
- always 'ADDR_EXPR' of 'VAR_DECL'. This built-in is used by
+ Function code - `BUILT_IN_CHKP_SIZEOF'. This built-in
+ function returns size of object referenced by PTR. PTR is
+ always `ADDR_EXPR' of `VAR_DECL'. This built-in is used by
Pointer Bounds Checker when bounds of object cannot be
- computed statically (e.g. object has incomplete type).
+ computed statically (e.g. object has incomplete type).
-- Built-in Function: const void *__chkp_extract_lower
(__bounds_type B)
- Function code - 'BUILT_IN_CHKP_EXTRACT_LOWER'. This built-in
+ Function code - `BUILT_IN_CHKP_EXTRACT_LOWER'. This built-in
function returns lower bound of bounds B.
-- Built-in Function: const void *__chkp_extract_upper
(__bounds_type B)
- Function code - 'BUILT_IN_CHKP_EXTRACT_UPPER'. This built-in
+ Function code - `BUILT_IN_CHKP_EXTRACT_UPPER'. This built-in
function returns upper bound of bounds B.
+
-- Target Hook: tree TARGET_CHKP_BOUND_TYPE (void)
Return type to be used for bounds
+
-- Target Hook: enum machine_mode TARGET_CHKP_BOUND_MODE (void)
Return mode to be used for bounds.
+
-- Target Hook: tree TARGET_CHKP_MAKE_BOUNDS_CONSTANT (HOST_WIDE_INT
LB, HOST_WIDE_INT UB)
Return constant used to statically initialize constant bounds with
specified lower bound LB and upper bounds UB.
+
-- Target Hook: int TARGET_CHKP_INITIALIZE_BOUNDS (tree VAR, tree LB,
tree UB, tree *STMTS)
Generate a list of statements STMTS to initialize pointer bounds
- variable VAR with bounds LB and UB. Return the number of generated
- statements.
+ variable VAR with bounds LB and UB. Return the number of
+ generated statements.
-- Target Hook: tree TARGET_RESOLVE_OVERLOADED_BUILTIN (unsigned int
LOC, tree FNDECL, void *ARGLIST)
Select a replacement for a machine specific built-in function that
- was set up by 'TARGET_INIT_BUILTINS'. This is done _before_
+ was set up by `TARGET_INIT_BUILTINS'. This is done _before_
regular type checking, and so allows the target to implement a
crude form of function overloading. FNDECL is the declaration of
the built-in function. ARGLIST is the list of arguments passed to
the built-in function. The result is a complete expression that
- implements the operation, usually another 'CALL_EXPR'. ARGLIST
- really has type 'VEC(tree,gc)*'
-
- -- Target Hook: tree TARGET_FOLD_BUILTIN (tree FNDECL, int N_ARGS, tree
- *ARGP, bool IGNORE)
- Fold a call to a machine specific built-in function that was set up
- by 'TARGET_INIT_BUILTINS'. FNDECL is the declaration of the
- built-in function. N_ARGS is the number of arguments passed to the
- function; the arguments themselves are pointed to by ARGP. The
- result is another tree, valid for both GIMPLE and GENERIC,
+ implements the operation, usually another `CALL_EXPR'. ARGLIST
+ really has type `VEC(tree,gc)*'
+
+ -- Target Hook: tree TARGET_FOLD_BUILTIN (tree FNDECL, int N_ARGS,
+ tree *ARGP, bool IGNORE)
+ Fold a call to a machine specific built-in function that was set
+ up by `TARGET_INIT_BUILTINS'. FNDECL is the declaration of the
+ built-in function. N_ARGS is the number of arguments passed to
+ the function; the arguments themselves are pointed to by ARGP.
+ The result is another tree, valid for both GIMPLE and GENERIC,
containing a simplified expression for the call's result. If
IGNORE is true the value will be ignored.
-- Target Hook: bool TARGET_GIMPLE_FOLD_BUILTIN (gimple_stmt_iterator
*GSI)
Fold a call to a machine specific built-in function that was set up
- by 'TARGET_INIT_BUILTINS'. GSI points to the gimple statement
+ by `TARGET_INIT_BUILTINS'. GSI points to the gimple statement
holding the function call. Returns true if any change was made to
the GIMPLE stream.
-- Target Hook: int TARGET_COMPARE_VERSION_PRIORITY (tree DECL1, tree
DECL2)
- This hook is used to compare the target attributes in two functions
- to determine which function's features get higher priority. This
- is used during function multi-versioning to figure out the order in
- which two versions must be dispatched. A function version with a
- higher priority is checked for dispatching earlier. DECL1 and
- DECL2 are the two function decls that will be compared.
+ This hook is used to compare the target attributes in two
+ functions to determine which function's features get higher
+ priority. This is used during function multi-versioning to figure
+ out the order in which two versions must be dispatched. A
+ function version with a higher priority is checked for dispatching
+ earlier. DECL1 and DECL2 are the two function decls that will be
+ compared.
-- Target Hook: tree TARGET_GET_FUNCTION_VERSIONS_DISPATCHER (void
*DECL)
This hook is used to get the dispatcher function for a set of
- function versions. The dispatcher function is called to invoke the
- right function version at run-time. DECL is one version from a set
- of semantically identical versions.
+ function versions. The dispatcher function is called to invoke
+ the right function version at run-time. DECL is one version from a
+ set of semantically identical versions.
-- Target Hook: tree TARGET_GENERATE_VERSION_DISPATCHER_BODY (void
*ARG)
@@ -37894,27 +38336,26 @@ Here are several miscellaneous parameters.
&ITERATIONS, const widest_int &ITERATIONS_MAX, unsigned int
LOOP_DEPTH, bool ENTERED_AT_TOP)
Return true if it is possible to use low-overhead loops
- ('doloop_end' and 'doloop_begin') for a particular loop.
- ITERATIONS gives the exact number of iterations, or 0 if not known.
- ITERATIONS_MAX gives the maximum number of iterations, or 0 if not
- known. LOOP_DEPTH is the nesting depth of the loop, with 1 for
- innermost loops, 2 for loops that contain innermost loops, and so
- on. ENTERED_AT_TOP is true if the loop is only entered from the
- top.
-
- This hook is only used if 'doloop_end' is available. The default
+ (`doloop_end' and `doloop_begin') for a particular loop.
+ ITERATIONS gives the exact number of iterations, or 0 if not
+ known. ITERATIONS_MAX gives the maximum number of iterations, or
+ 0 if not known. LOOP_DEPTH is the nesting depth of the loop, with
+ 1 for innermost loops, 2 for loops that contain innermost loops,
+ and so on. ENTERED_AT_TOP is true if the loop is only entered
+ from the top.
+
+ This hook is only used if `doloop_end' is available. The default
implementation returns true. You can use
- 'can_use_doloop_if_innermost' if the loop must be the innermost,
+ `can_use_doloop_if_innermost' if the loop must be the innermost,
and if there are no other restrictions.
-- Target Hook: const char * TARGET_INVALID_WITHIN_DOLOOP (const
rtx_insn *INSN)
-
Take an instruction in INSN and return NULL if it is valid within a
low-overhead loop, otherwise return a string explaining why doloop
could not be applied.
- Many targets use special registers for low-overhead looping. For
+ Many targets use special registers for low-overhead looping. For
any instruction that clobbers these this function should return a
string indicating the reason why the doloop could not be applied.
By default, the RTL loop optimizer does not use a present doloop
@@ -37922,86 +38363,85 @@ Here are several miscellaneous parameters.
instructions.
-- Target Hook: bool TARGET_LEGITIMATE_COMBINED_INSN (rtx_insn *INSN)
- Take an instruction in INSN and return 'false' if the instruction
+ Take an instruction in INSN and return `false' if the instruction
is not appropriate as a combination of two or more instructions.
The default is to accept all instructions.
-- Target Hook: bool TARGET_CAN_FOLLOW_JUMP (const rtx_insn *FOLLOWER,
const rtx_insn *FOLLOWEE)
- FOLLOWER and FOLLOWEE are JUMP_INSN instructions; return true if
- FOLLOWER may be modified to follow FOLLOWEE; false, if it can't.
+ FOLLOWER and FOLLOWEE are JUMP_INSN instructions; return true if
+ FOLLOWER may be modified to follow FOLLOWEE; false, if it can't.
For example, on some targets, certain kinds of branches can't be
- made to follow through a hot/cold partitioning.
+ made to follow through a hot/cold partitioning.
-- Target Hook: bool TARGET_COMMUTATIVE_P (const_rtx X, int OUTER_CODE)
- This target hook returns 'true' if X is considered to be
+ This target hook returns `true' if X is considered to be
commutative. Usually, this is just COMMUTATIVE_P (X), but the HP
PA doesn't consider PLUS to be commutative inside a MEM.
OUTER_CODE is the rtx code of the enclosing rtl, if known,
otherwise it is UNKNOWN.
-- Target Hook: rtx TARGET_ALLOCATE_INITIAL_VALUE (rtx HARD_REG)
-
When the initial value of a hard register has been copied in a
pseudo register, it is often not necessary to actually allocate
- another register to this pseudo register, because the original hard
- register or a stack slot it has been saved into can be used.
- 'TARGET_ALLOCATE_INITIAL_VALUE' is called at the start of register
+ another register to this pseudo register, because the original
+ hard register or a stack slot it has been saved into can be used.
+ `TARGET_ALLOCATE_INITIAL_VALUE' is called at the start of register
allocation once for each hard register that had its initial value
- copied by using 'get_func_hard_reg_initial_val' or
- 'get_hard_reg_initial_val'. Possible values are 'NULL_RTX', if you
- don't want to do any special allocation, a 'REG' rtx--that would
- typically be the hard register itself, if it is known not to be
- clobbered--or a 'MEM'. If you are returning a 'MEM', this is only
- a hint for the allocator; it might decide to use another register
- anyways. You may use 'current_function_is_leaf' or 'REG_N_SETS' in
- the hook to determine if the hard register in question will not be
- clobbered. The default value of this hook is 'NULL', which
- disables any special allocation.
+ copied by using `get_func_hard_reg_initial_val' or
+ `get_hard_reg_initial_val'. Possible values are `NULL_RTX', if
+ you don't want to do any special allocation, a `REG' rtx--that
+ would typically be the hard register itself, if it is known not to
+ be clobbered--or a `MEM'. If you are returning a `MEM', this is
+ only a hint for the allocator; it might decide to use another
+ register anyways. You may use `current_function_is_leaf' or
+ `REG_N_SETS' in the hook to determine if the hard register in
+ question will not be clobbered. The default value of this hook is
+ `NULL', which disables any special allocation.
-- Target Hook: int TARGET_UNSPEC_MAY_TRAP_P (const_rtx X, unsigned
FLAGS)
- This target hook returns nonzero if X, an 'unspec' or
- 'unspec_volatile' operation, might cause a trap. Targets can use
- this hook to enhance precision of analysis for 'unspec' and
- 'unspec_volatile' operations. You may call 'may_trap_p_1' to
+ This target hook returns nonzero if X, an `unspec' or
+ `unspec_volatile' operation, might cause a trap. Targets can use
+ this hook to enhance precision of analysis for `unspec' and
+ `unspec_volatile' operations. You may call `may_trap_p_1' to
analyze inner elements of X in which case FLAGS should be passed
along.
-- Target Hook: void TARGET_SET_CURRENT_FUNCTION (tree DECL)
The compiler invokes this hook whenever it changes its current
- function context ('cfun'). You can define this function if the
+ function context (`cfun'). You can define this function if the
back end needs to perform any initialization or reset actions on a
per-function basis. For example, it may be used to implement
function attributes that affect register usage or code generation
patterns. The argument DECL is the declaration for the new
- function context, and may be null to indicate that the compiler has
- left a function context and is returning to processing at the top
- level. The default hook function does nothing.
+ function context, and may be null to indicate that the compiler
+ has left a function context and is returning to processing at the
+ top level. The default hook function does nothing.
- GCC sets 'cfun' to a dummy function context during initialization
- of some parts of the back end. The hook function is not invoked in
- this situation; you need not worry about the hook being invoked
+ GCC sets `cfun' to a dummy function context during initialization
+ of some parts of the back end. The hook function is not invoked
+ in this situation; you need not worry about the hook being invoked
recursively, or when the back end is in a partially-initialized
- state. 'cfun' might be 'NULL' to indicate processing at top level,
+ state. `cfun' might be `NULL' to indicate processing at top level,
outside of any function scope.
-- Macro: TARGET_OBJECT_SUFFIX
Define this macro to be a C string representing the suffix for
object files on your target machine. If you do not define this
- macro, GCC will use '.o' as the suffix for object files.
+ macro, GCC will use `.o' as the suffix for object files.
-- Macro: TARGET_EXECUTABLE_SUFFIX
Define this macro to be a C string representing the suffix to be
- automatically added to executable files on your target machine. If
- you do not define this macro, GCC will use the null string as the
- suffix for executable files.
+ automatically added to executable files on your target machine.
+ If you do not define this macro, GCC will use the null string as
+ the suffix for executable files.
-- Macro: COLLECT_EXPORT_LIST
- If defined, 'collect2' will scan the individual object files
+ If defined, `collect2' will scan the individual object files
specified on its command line and create an export list for the
linker. Define this macro for systems like AIX, where the linker
- discards object files that are not referenced from 'main' and uses
+ discards object files that are not referenced from `main' and uses
export lists.
-- Macro: MODIFY_JNI_METHOD_CALL (MDECL)
@@ -38009,7 +38449,7 @@ Here are several miscellaneous parameters.
method call MDECL, if Java Native Interface (JNI) methods must be
invoked differently from other methods on your target. For
example, on 32-bit Microsoft Windows, JNI methods must be invoked
- using the 'stdcall' calling convention and this macro is then
+ using the `stdcall' calling convention and this macro is then
defined as this expression:
build_type_attribute_variant (MDECL,
@@ -38018,11 +38458,11 @@ Here are several miscellaneous parameters.
NULL))
-- Target Hook: bool TARGET_CANNOT_MODIFY_JUMPS_P (void)
- This target hook returns 'true' past the point in which new jump
- instructions could be created. On machines that require a register
- for every jump such as the SHmedia ISA of SH5, this point would
- typically be reload, so this target hook should be defined to a
- function such as:
+ This target hook returns `true' past the point in which new jump
+ instructions could be created. On machines that require a
+ register for every jump such as the SHmedia ISA of SH5, this point
+ would typically be reload, so this target hook should be defined
+ to a function such as:
static bool
cannot_modify_jumps_past_reload_p ()
@@ -38033,22 +38473,23 @@ Here are several miscellaneous parameters.
-- Target Hook: reg_class_t TARGET_BRANCH_TARGET_REGISTER_CLASS (void)
This target hook returns a register class for which branch target
register optimizations should be applied. All registers in this
- class should be usable interchangeably. After reload, registers in
- this class will be re-allocated and loads will be hoisted out of
- loops and be subjected to inter-block scheduling.
+ class should be usable interchangeably. After reload, registers
+ in this class will be re-allocated and loads will be hoisted out
+ of loops and be subjected to inter-block scheduling.
-- Target Hook: bool TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED (bool
AFTER_PROLOGUE_EPILOGUE_GEN)
Branch target register optimization will by default exclude
- callee-saved registers that are not already live during the current
- function; if this target hook returns true, they will be included.
- The target code must than make sure that all target registers in
- the class returned by 'TARGET_BRANCH_TARGET_REGISTER_CLASS' that
- might need saving are saved. AFTER_PROLOGUE_EPILOGUE_GEN indicates
- if prologues and epilogues have already been generated. Note, even
- if you only return true when AFTER_PROLOGUE_EPILOGUE_GEN is false,
- you still are likely to have to make special provisions in
- 'INITIAL_ELIMINATION_OFFSET' to reserve space for caller-saved
+ callee-saved registers that are not already live during the
+ current function; if this target hook returns true, they will be
+ included. The target code must than make sure that all target
+ registers in the class returned by
+ `TARGET_BRANCH_TARGET_REGISTER_CLASS' that might need saving are
+ saved. AFTER_PROLOGUE_EPILOGUE_GEN indicates if prologues and
+ epilogues have already been generated. Note, even if you only
+ return true when AFTER_PROLOGUE_EPILOGUE_GEN is false, you still
+ are likely to have to make special provisions in
+ `INITIAL_ELIMINATION_OFFSET' to reserve space for caller-saved
target registers.
-- Target Hook: bool TARGET_HAVE_CONDITIONAL_EXECUTION (void)
@@ -38057,38 +38498,39 @@ Here are several miscellaneous parameters.
several different modes and they have different conditional
execution capability, such as ARM.
- -- Target Hook: rtx TARGET_GEN_CCMP_FIRST (rtx *PREP_SEQ, rtx *GEN_SEQ,
- int CODE, tree OP0, tree OP1)
+ -- Target Hook: rtx TARGET_GEN_CCMP_FIRST (rtx *PREP_SEQ, rtx
+ *GEN_SEQ, int CODE, tree OP0, tree OP1)
This function prepares to emit a comparison insn for the first
- compare in a sequence of conditional comparisions. It returns a
- appropriate 'CC' for passing to 'gen_ccmp_next' or 'cbranch_optab'.
- The insns to prepare the compare are saved in PREP_SEQ and the
- compare insns are saved in GEN_SEQ. They will be emitted when all
- the compares in the the conditional comparision are generated
- without error. CODE is the 'rtx_code' of the compare for OP0 and
- OP1.
+ compare in a sequence of conditional comparisions. It returns a
+ appropriate `CC' for passing to `gen_ccmp_next' or
+ `cbranch_optab'. The insns to prepare the compare are saved in
+ PREP_SEQ and the compare insns are saved in GEN_SEQ. They will
+ be emitted when all the compares in the the conditional
+ comparision are generated without error. CODE is the `rtx_code'
+ of the compare for OP0 and OP1.
-- Target Hook: rtx TARGET_GEN_CCMP_NEXT (rtx *PREP_SEQ, rtx *GEN_SEQ,
rtx PREV, int CMP_CODE, tree OP0, tree OP1, int BIT_CODE)
This function prepare to emit a conditional comparison within a
- sequence of conditional comparisons. It returns a appropriate 'CC'
- for passing to 'gen_ccmp_next' or 'cbranch_optab'. The insns to
- prepare the compare are saved in PREP_SEQ and the compare insns are
- saved in GEN_SEQ. They will be emitted when all the compares in
- the conditional comparision are generated without error. The PREV
- expression is the result of a prior call to 'gen_ccmp_first' or
- 'gen_ccmp_next'. It may return 'NULL' if the combination of PREV
- and this comparison is not supported, otherwise the result must be
- appropriate for passing to 'gen_ccmp_next' or 'cbranch_optab'.
- CODE is the 'rtx_code' of the compare for OP0 and OP1. BIT_CODE is
- 'AND' or 'IOR', which is the op on the two compares.
+ sequence of conditional comparisons. It returns a appropriate
+ `CC' for passing to `gen_ccmp_next' or `cbranch_optab'. The
+ insns to prepare the compare are saved in PREP_SEQ and the
+ compare insns are saved in GEN_SEQ. They will be emitted when
+ all the compares in the conditional comparision are generated
+ without error. The PREV expression is the result of a prior call
+ to `gen_ccmp_first' or `gen_ccmp_next'. It may return `NULL' if
+ the combination of PREV and this comparison is not supported,
+ otherwise the result must be appropriate for passing to
+ `gen_ccmp_next' or `cbranch_optab'. CODE is the `rtx_code' of
+ the compare for OP0 and OP1. BIT_CODE is `AND' or `IOR', which
+ is the op on the two compares.
-- Target Hook: unsigned TARGET_LOOP_UNROLL_ADJUST (unsigned NUNROLL,
struct loop *LOOP)
This target hook returns a new value for the number of times LOOP
- should be unrolled. The parameter NUNROLL is the number of times
- the loop is to be unrolled. The parameter LOOP is a pointer to the
- loop, which is going to be checked for unrolling. This target hook
+ should be unrolled. The parameter NUNROLL is the number of times
+ the loop is to be unrolled. The parameter LOOP is a pointer to the
+ loop, which is going to be checked for unrolling. This target hook
is required only when the target has special constraints like
maximum number of memory accesses.
@@ -38099,69 +38541,69 @@ Here are several miscellaneous parameters.
exponentiation by an integer constant inline. When this value is
defined, exponentiation requiring more than this number of
multiplications is implemented by calling the system library's
- 'pow', 'powf' or 'powl' routines. The default value places no
+ `pow', `powf' or `powl' routines. The default value places no
upper bound on the multiplication count.
-- Macro: void TARGET_EXTRA_INCLUDES (const char *SYSROOT, const char
*IPREFIX, int STDINC)
This target hook should register any extra include files for the
- target. The parameter STDINC indicates if normal include files are
- present. The parameter SYSROOT is the system root directory. The
- parameter IPREFIX is the prefix for the gcc directory.
+ target. The parameter STDINC indicates if normal include files
+ are present. The parameter SYSROOT is the system root directory.
+ The parameter IPREFIX is the prefix for the gcc directory.
-- Macro: void TARGET_EXTRA_PRE_INCLUDES (const char *SYSROOT, const
char *IPREFIX, int STDINC)
This target hook should register any extra include files for the
- target before any standard headers. The parameter STDINC indicates
- if normal include files are present. The parameter SYSROOT is the
- system root directory. The parameter IPREFIX is the prefix for the
- gcc directory.
+ target before any standard headers. The parameter STDINC
+ indicates if normal include files are present. The parameter
+ SYSROOT is the system root directory. The parameter IPREFIX is
+ the prefix for the gcc directory.
-- Macro: void TARGET_OPTF (char *PATH)
This target hook should register special include paths for the
target. The parameter PATH is the include to register. On Darwin
systems, this is used for Framework includes, which have semantics
- that are different from '-I'.
+ that are different from `-I'.
-- Macro: bool TARGET_USE_LOCAL_THUNK_ALIAS_P (tree FNDECL)
- This target macro returns 'true' if it is safe to use a local alias
- for a virtual function FNDECL when constructing thunks, 'false'
- otherwise. By default, the macro returns 'true' for all functions,
- if a target supports aliases (i.e. defines 'ASM_OUTPUT_DEF'),
- 'false' otherwise,
+ This target macro returns `true' if it is safe to use a local alias
+ for a virtual function FNDECL when constructing thunks, `false'
+ otherwise. By default, the macro returns `true' for all
+ functions, if a target supports aliases (i.e. defines
+ `ASM_OUTPUT_DEF'), `false' otherwise,
-- Macro: TARGET_FORMAT_TYPES
If defined, this macro is the name of a global variable containing
- target-specific format checking information for the '-Wformat'
+ target-specific format checking information for the `-Wformat'
option. The default is to have no target-specific format checks.
-- Macro: TARGET_N_FORMAT_TYPES
If defined, this macro is the number of entries in
- 'TARGET_FORMAT_TYPES'.
+ `TARGET_FORMAT_TYPES'.
-- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES
If defined, this macro is the name of a global variable containing
- target-specific format overrides for the '-Wformat' option. The
- default is to have no target-specific format overrides. If
- defined, 'TARGET_FORMAT_TYPES' must be defined, too.
+ target-specific format overrides for the `-Wformat' option. The
+ default is to have no target-specific format overrides. If defined,
+ `TARGET_FORMAT_TYPES' must be defined, too.
-- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT
If defined, this macro specifies the number of entries in
- 'TARGET_OVERRIDES_FORMAT_ATTRIBUTES'.
+ `TARGET_OVERRIDES_FORMAT_ATTRIBUTES'.
-- Macro: TARGET_OVERRIDES_FORMAT_INIT
If defined, this macro specifies the optional initialization
- routine for target specific customizations of the system printf and
- scanf formatter settings.
+ routine for target specific customizations of the system printf
+ and scanf formatter settings.
-- Target Hook: bool TARGET_RELAXED_ORDERING
- If set to 'true', means that the target's memory model does not
+ If set to `true', means that the target's memory model does not
guarantee that loads which do not depend on one another will access
main memory in the order of the instruction stream; if ordering is
important, an explicit memory barrier must be used. This is true
of many recent processors which implement a policy of "relaxed,"
"weak," or "release" memory consistency, such as Alpha, PowerPC,
- and ia64. The default is 'false'.
+ and ia64. The default is `false'.
-- Target Hook: const char * TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN
(const_tree TYPELIST, const_tree FUNCDECL, const_tree VAL)
@@ -38172,67 +38614,68 @@ Here are several miscellaneous parameters.
-- Target Hook: const char * TARGET_INVALID_CONVERSION (const_tree
FROMTYPE, const_tree TOTYPE)
If defined, this macro returns the diagnostic message when it is
- invalid to convert from FROMTYPE to TOTYPE, or 'NULL' if validity
+ invalid to convert from FROMTYPE to TOTYPE, or `NULL' if validity
should be determined by the front end.
-- Target Hook: const char * TARGET_INVALID_UNARY_OP (int OP,
const_tree TYPE)
If defined, this macro returns the diagnostic message when it is
invalid to apply operation OP (where unary plus is denoted by
- 'CONVERT_EXPR') to an operand of type TYPE, or 'NULL' if validity
+ `CONVERT_EXPR') to an operand of type TYPE, or `NULL' if validity
should be determined by the front end.
-- Target Hook: const char * TARGET_INVALID_BINARY_OP (int OP,
const_tree TYPE1, const_tree TYPE2)
If defined, this macro returns the diagnostic message when it is
- invalid to apply operation OP to operands of types TYPE1 and TYPE2,
- or 'NULL' if validity should be determined by the front end.
+ invalid to apply operation OP to operands of types TYPE1 and
+ TYPE2, or `NULL' if validity should be determined by the front end.
-- Target Hook: const char * TARGET_INVALID_PARAMETER_TYPE (const_tree
TYPE)
If defined, this macro returns the diagnostic message when it is
- invalid for functions to include parameters of type TYPE, or 'NULL'
- if validity should be determined by the front end. This is
+ invalid for functions to include parameters of type TYPE, or
+ `NULL' if validity should be determined by the front end. This is
currently used only by the C and C++ front ends.
-- Target Hook: const char * TARGET_INVALID_RETURN_TYPE (const_tree
TYPE)
If defined, this macro returns the diagnostic message when it is
- invalid for functions to have return type TYPE, or 'NULL' if
+ invalid for functions to have return type TYPE, or `NULL' if
validity should be determined by the front end. This is currently
used only by the C and C++ front ends.
-- Target Hook: tree TARGET_PROMOTED_TYPE (const_tree TYPE)
If defined, this target hook returns the type to which values of
TYPE should be promoted when they appear in expressions, analogous
- to the integer promotions, or 'NULL_TREE' to use the front end's
+ to the integer promotions, or `NULL_TREE' to use the front end's
normal promotion rules. This hook is useful when there are
target-specific types with special promotion rules. This is
currently used only by the C and C++ front ends.
-- Target Hook: tree TARGET_CONVERT_TO_TYPE (tree TYPE, tree EXPR)
If defined, this hook returns the result of converting EXPR to
- TYPE. It should return the converted expression, or 'NULL_TREE' to
- apply the front end's normal conversion rules. This hook is useful
- when there are target-specific types with special conversion rules.
- This is currently used only by the C and C++ front ends.
+ TYPE. It should return the converted expression, or `NULL_TREE'
+ to apply the front end's normal conversion rules. This hook is
+ useful when there are target-specific types with special
+ conversion rules. This is currently used only by the C and C++
+ front ends.
-- Macro: TARGET_USE_JCR_SECTION
This macro determines whether to use the JCR section to register
- Java classes. By default, TARGET_USE_JCR_SECTION is defined to 1
- if both SUPPORTS_WEAK and TARGET_HAVE_NAMED_SECTIONS are true, else
- 0.
+ Java classes. By default, TARGET_USE_JCR_SECTION is defined to 1
+ if both SUPPORTS_WEAK and TARGET_HAVE_NAMED_SECTIONS are true,
+ else 0.
-- Macro: OBJC_JBLEN
This macro determines the size of the objective C jump buffer for
- the NeXT runtime. By default, OBJC_JBLEN is defined to an
+ the NeXT runtime. By default, OBJC_JBLEN is defined to an
innocuous value.
-- Macro: LIBGCC2_UNWIND_ATTRIBUTE
Define this macro if any target-specific attributes need to be
- attached to the functions in 'libgcc' that provide low-level
+ attached to the functions in `libgcc' that provide low-level
support for call stack unwinding. It is used in declarations in
- 'unwind-generic.h' and the associated definitions of those
+ `unwind-generic.h' and the associated definitions of those
functions.
-- Target Hook: void TARGET_UPDATE_STACK_BOUNDARY (void)
@@ -38240,17 +38683,17 @@ Here are several miscellaneous parameters.
necessary.
-- Target Hook: rtx TARGET_GET_DRAP_RTX (void)
- This hook should return an rtx for Dynamic Realign Argument Pointer
- (DRAP) if a different argument pointer register is needed to access
- the function's argument list due to stack realignment. Return
- 'NULL' if no DRAP is needed.
+ This hook should return an rtx for Dynamic Realign Argument
+ Pointer (DRAP) if a different argument pointer register is needed
+ to access the function's argument list due to stack realignment.
+ Return `NULL' if no DRAP is needed.
-- Target Hook: bool TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS (void)
When optimization is disabled, this hook indicates whether or not
arguments should be allocated to stack slots. Normally, GCC
allocates stacks slots for arguments when not optimizing in order
to make debugging easier. However, when a function is declared
- with '__attribute__((naked))', there is no stack frame, and the
+ with `__attribute__((naked))', there is no stack frame, and the
compiler cannot safely move arguments from the registers in which
they are passed to the stack. Therefore, this hook should return
true in general, but false for naked functions. The default
@@ -38261,17 +38704,17 @@ Here are several miscellaneous parameters.
synthesize a constant. If there is another constant already in a
register that is close enough in value then it is preferable that
the new constant is computed from this register using immediate
- addition or subtraction. We accomplish this through CSE. Besides
- the value of the constant we also add a lower and an upper constant
- anchor to the available expressions. These are then queried when
- encountering new constants. The anchors are computed by rounding
- the constant up and down to a multiple of the value of
- 'TARGET_CONST_ANCHOR'. 'TARGET_CONST_ANCHOR' should be the maximum
- positive value accepted by immediate-add plus one. We currently
- assume that the value of 'TARGET_CONST_ANCHOR' is a power of 2.
- For example, on MIPS, where add-immediate takes a 16-bit signed
- value, 'TARGET_CONST_ANCHOR' is set to '0x8000'. The default value
- is zero, which disables this optimization.
+ addition or subtraction. We accomplish this through CSE. Besides
+ the value of the constant we also add a lower and an upper
+ constant anchor to the available expressions. These are then
+ queried when encountering new constants. The anchors are computed
+ by rounding the constant up and down to a multiple of the value of
+ `TARGET_CONST_ANCHOR'. `TARGET_CONST_ANCHOR' should be the
+ maximum positive value accepted by immediate-add plus one. We
+ currently assume that the value of `TARGET_CONST_ANCHOR' is a
+ power of 2. For example, on MIPS, where add-immediate takes a
+ 16-bit signed value, `TARGET_CONST_ANCHOR' is set to `0x8000'.
+ The default value is zero, which disables this optimization.
-- Target Hook: unsigned HOST_WIDE_INT TARGET_ASAN_SHADOW_OFFSET (void)
Return the offset bitwise ored into shifted address to get
@@ -38280,96 +38723,99 @@ Here are several miscellaneous parameters.
-- Target Hook: unsigned HOST_WIDE_INT TARGET_MEMMODEL_CHECK (unsigned
HOST_WIDE_INT VAL)
- Validate target specific memory model mask bits. When NULL no
+ Validate target specific memory model mask bits. When NULL no
target specific memory model bits are allowed.
-- Target Hook: unsigned char TARGET_ATOMIC_TEST_AND_SET_TRUEVAL
This value should be set if the result written by
- 'atomic_test_and_set' is not exactly 1, i.e. the 'bool' 'true'.
+ `atomic_test_and_set' is not exactly 1, i.e. the `bool' `true'.
-- Target Hook: bool TARGET_HAS_IFUNC_P (void)
- It returns true if the target supports GNU indirect functions. The
- support includes the assembler, linker and dynamic linker. The
- default value of this hook is based on target's libc.
+ It returns true if the target supports GNU indirect functions.
+ The support includes the assembler, linker and dynamic linker.
+ The default value of this hook is based on target's libc.
- -- Target Hook: unsigned int TARGET_ATOMIC_ALIGN_FOR_MODE (machine_mode
- MODE)
+ -- Target Hook: unsigned int TARGET_ATOMIC_ALIGN_FOR_MODE
+ (machine_mode MODE)
If defined, this function returns an appropriate alignment in bits
for an atomic object of machine_mode MODE. If 0 is returned then
the default alignment for the specified mode is used.
- -- Target Hook: void TARGET_ATOMIC_ASSIGN_EXPAND_FENV (tree *HOLD, tree
- *CLEAR, tree *UPDATE)
+ -- Target Hook: void TARGET_ATOMIC_ASSIGN_EXPAND_FENV (tree *HOLD,
+ tree *CLEAR, tree *UPDATE)
ISO C11 requires atomic compound assignments that may raise
floating-point exceptions to raise exceptions corresponding to the
arithmetic operation whose result was successfully stored in a
compare-and-exchange sequence. This requires code equivalent to
- calls to 'feholdexcept', 'feclearexcept' and 'feupdateenv' to be
+ calls to `feholdexcept', `feclearexcept' and `feupdateenv' to be
generated at appropriate points in the compare-and-exchange
- sequence. This hook should set '*HOLD' to an expression equivalent
- to the call to 'feholdexcept', '*CLEAR' to an expression equivalent
- to the call to 'feclearexcept' and '*UPDATE' to an expression
- equivalent to the call to 'feupdateenv'. The three expressions are
- 'NULL_TREE' on entry to the hook and may be left as 'NULL_TREE' if
- no code is required in a particular place. The default
- implementation leaves all three expressions as 'NULL_TREE'. The
- '__atomic_feraiseexcept' function from 'libatomic' may be of use as
- part of the code generated in '*UPDATE'.
+ sequence. This hook should set `*HOLD' to an expression
+ equivalent to the call to `feholdexcept', `*CLEAR' to an
+ expression equivalent to the call to `feclearexcept' and `*UPDATE'
+ to an expression equivalent to the call to `feupdateenv'. The
+ three expressions are `NULL_TREE' on entry to the hook and may be
+ left as `NULL_TREE' if no code is required in a particular place.
+ The default implementation leaves all three expressions as
+ `NULL_TREE'. The `__atomic_feraiseexcept' function from
+ `libatomic' may be of use as part of the code generated in
+ `*UPDATE'.
-- Target Hook: void TARGET_RECORD_OFFLOAD_SYMBOL (tree)
Used when offloaded functions are seen in the compilation unit and
- no named sections are available. It is called once for each symbol
- that must be recorded in the offload function and variable table.
+ no named sections are available. It is called once for each
+ symbol that must be recorded in the offload function and variable
+ table.
-- Target Hook: char * TARGET_OFFLOAD_OPTIONS (void)
Used when writing out the list of options into an LTO file. It
should translate any relevant target-specific options (such as the
- ABI in use) into one of the '-foffload' options that exist as a
+ ABI in use) into one of the `-foffload' options that exist as a
common interface to express such options. It should return a
string containing these options, separated by spaces, which the
caller will free.
- -- Macro: TARGET_SUPPORTS_WIDE_INT
- On older ports, large integers are stored in 'CONST_DOUBLE' rtl
- objects. Newer ports define 'TARGET_SUPPORTS_WIDE_INT' to be
+ -- Macro: TARGET_SUPPORTS_WIDE_INT
+ On older ports, large integers are stored in `CONST_DOUBLE' rtl
+ objects. Newer ports define `TARGET_SUPPORTS_WIDE_INT' to be
nonzero to indicate that large integers are stored in
- 'CONST_WIDE_INT' rtl objects. The 'CONST_WIDE_INT' allows very
- large integer constants to be represented. 'CONST_DOUBLE' is
- limited to twice the size of the host's 'HOST_WIDE_INT'
+ `CONST_WIDE_INT' rtl objects. The `CONST_WIDE_INT' allows very
+ large integer constants to be represented. `CONST_DOUBLE' is
+ limited to twice the size of the host's `HOST_WIDE_INT'
representation.
Converting a port mostly requires looking for the places where
- 'CONST_DOUBLE's are used with 'VOIDmode' and replacing that code
- with code that accesses 'CONST_WIDE_INT's. '"grep -i
+ `CONST_DOUBLE's are used with `VOIDmode' and replacing that code
+ with code that accesses `CONST_WIDE_INT's. `"grep -i
const_double"' at the port level gets you to 95% of the changes
- that need to be made. There are a few places that require a deeper
- look.
+ that need to be made. There are a few places that require a
+ deeper look.
- * There is no equivalent to 'hval' and 'lval' for
- 'CONST_WIDE_INT's. This would be difficult to express in the
+ * There is no equivalent to `hval' and `lval' for
+ `CONST_WIDE_INT's. This would be difficult to express in the
md language since there are a variable number of elements.
- Most ports only check that 'hval' is either 0 or -1 to see if
+ Most ports only check that `hval' is either 0 or -1 to see if
the value is small. As mentioned above, this will no longer
- be necessary since small constants are always 'CONST_INT'. Of
- course there are still a few exceptions, the alpha's
+ be necessary since small constants are always `CONST_INT'.
+ Of course there are still a few exceptions, the alpha's
constraint used by the zap instruction certainly requires
careful examination by C code. However, all the current code
does is pass the hval and lval to C code, so evolving the c
- code to look at the 'CONST_WIDE_INT' is not really a large
+ code to look at the `CONST_WIDE_INT' is not really a large
change.
* Because there is no standard template that ports use to
- materialize constants, there is likely to be some futzing that
- is unique to each port in this code.
+ materialize constants, there is likely to be some futzing
+ that is unique to each port in this code.
* The rtx costs may have to be adjusted to properly account for
- larger constants that are represented as 'CONST_WIDE_INT'.
+ larger constants that are represented as `CONST_WIDE_INT'.
All and all it does not take long to convert ports that the
maintainer is familiar with.
+

File: gccint.info, Node: Host Config, Next: Fragments, Prev: Target Macros, Up: Top
@@ -38377,23 +38823,23 @@ File: gccint.info, Node: Host Config, Next: Fragments, Prev: Target Macros,
*********************
Most details about the machine and system on which the compiler is
-actually running are detected by the 'configure' script. Some things
-are impossible for 'configure' to detect; these are described in two
-ways, either by macros defined in a file named 'xm-MACHINE.h' or by hook
-functions in the file specified by the OUT_HOST_HOOK_OBJ variable in
-'config.gcc'. (The intention is that very few hosts will need a header
-file but nearly every fully supported host will need to override some
-hooks.)
+actually running are detected by the `configure' script. Some things
+are impossible for `configure' to detect; these are described in two
+ways, either by macros defined in a file named `xm-MACHINE.h' or by
+hook functions in the file specified by the OUT_HOST_HOOK_OBJ variable
+in `config.gcc'. (The intention is that very few hosts will need a
+header file but nearly every fully supported host will need to override
+some hooks.)
If you need to define only a few macros, and they have simple
-definitions, consider using the 'xm_defines' variable in your
-'config.gcc' entry instead of creating a host configuration header.
+definitions, consider using the `xm_defines' variable in your
+`config.gcc' entry instead of creating a host configuration header.
*Note System Config::.
* Menu:
* Host Common:: Things every host probably needs implemented.
-* Filesystem:: Your host can't have the letter 'a' in filenames?
+* Filesystem:: Your host can't have the letter `a' in filenames?
* Host Misc:: Rare configuration options for hosts.

@@ -38405,7 +38851,7 @@ File: gccint.info, Node: Host Common, Next: Filesystem, Up: Host Config
Some things are just not portable, even between similar operating
systems, and are too difficult for autoconf to detect. They get
implemented using hook functions in the file specified by the
-HOST_HOOK_OBJ variable in 'config.gcc'.
+HOST_HOOK_OBJ variable in `config.gcc'.
-- Host Hook: void HOST_HOOKS_EXTRA_SIGNALS (void)
This host hook is used to set up handling for extra signals. The
@@ -38415,19 +38861,20 @@ HOST_HOOK_OBJ variable in 'config.gcc'.
FD)
This host hook returns the address of some space that is likely to
be free in some subsequent invocation of the compiler. We intend
- to load the PCH data at this address such that the data need not be
- relocated. The area should be able to hold SIZE bytes. If the
- host uses 'mmap', FD is an open file descriptor that can be used
+ to load the PCH data at this address such that the data need not
+ be relocated. The area should be able to hold SIZE bytes. If the
+ host uses `mmap', FD is an open file descriptor that can be used
for probing.
- -- Host Hook: int HOST_HOOKS_GT_PCH_USE_ADDRESS (void * ADDRESS, size_t
- SIZE, int FD, size_t OFFSET)
- This host hook is called when a PCH file is about to be loaded. We
- want to load SIZE bytes from FD at OFFSET into memory at ADDRESS.
- The given address will be the result of a previous invocation of
- 'HOST_HOOKS_GT_PCH_GET_ADDRESS'. Return -1 if we couldn't allocate
- SIZE bytes at ADDRESS. Return 0 if the memory is allocated but the
- data is not loaded. Return 1 if the hook has performed everything.
+ -- Host Hook: int HOST_HOOKS_GT_PCH_USE_ADDRESS (void * ADDRESS,
+ size_t SIZE, int FD, size_t OFFSET)
+ This host hook is called when a PCH file is about to be loaded.
+ We want to load SIZE bytes from FD at OFFSET into memory at
+ ADDRESS. The given address will be the result of a previous
+ invocation of `HOST_HOOKS_GT_PCH_GET_ADDRESS'. Return -1 if we
+ couldn't allocate SIZE bytes at ADDRESS. Return 0 if the memory
+ is allocated but the data is not loaded. Return 1 if the hook has
+ performed everything.
If the implementation uses reserved address space, free any
reserved space beyond SIZE, regardless of the return value. If no
@@ -38453,58 +38900,58 @@ File: gccint.info, Node: Filesystem, Next: Host Misc, Prev: Host Common, Up:
GCC needs to know a number of things about the semantics of the host
machine's filesystem. Filesystems with Unix and MS-DOS semantics are
-automatically detected. For other systems, you can define the following
-macros in 'xm-MACHINE.h'.
+automatically detected. For other systems, you can define the
+following macros in `xm-MACHINE.h'.
-'HAVE_DOS_BASED_FILE_SYSTEM'
- This macro is automatically defined by 'system.h' if the host file
+`HAVE_DOS_BASED_FILE_SYSTEM'
+ This macro is automatically defined by `system.h' if the host file
system obeys the semantics defined by MS-DOS instead of Unix. DOS
file systems are case insensitive, file specifications may begin
- with a drive letter, and both forward slash and backslash ('/' and
- '\') are directory separators.
+ with a drive letter, and both forward slash and backslash (`/' and
+ `\') are directory separators.
-'DIR_SEPARATOR'
-'DIR_SEPARATOR_2'
+`DIR_SEPARATOR'
+`DIR_SEPARATOR_2'
If defined, these macros expand to character constants specifying
separators for directory names within a file specification.
- 'system.h' will automatically give them appropriate values on Unix
+ `system.h' will automatically give them appropriate values on Unix
and MS-DOS file systems. If your file system is neither of these,
- define one or both appropriately in 'xm-MACHINE.h'.
+ define one or both appropriately in `xm-MACHINE.h'.
However, operating systems like VMS, where constructing a pathname
is more complicated than just stringing together directory names
separated by a special character, should not define either of these
macros.
-'PATH_SEPARATOR'
+`PATH_SEPARATOR'
If defined, this macro should expand to a character constant
specifying the separator for elements of search paths. The default
- value is a colon (':'). DOS-based systems usually, but not always,
- use semicolon (';').
+ value is a colon (`:'). DOS-based systems usually, but not
+ always, use semicolon (`;').
-'VMS'
+`VMS'
Define this macro if the host system is VMS.
-'HOST_OBJECT_SUFFIX'
+`HOST_OBJECT_SUFFIX'
Define this macro to be a C string representing the suffix for
object files on your host machine. If you do not define this
- macro, GCC will use '.o' as the suffix for object files.
+ macro, GCC will use `.o' as the suffix for object files.
-'HOST_EXECUTABLE_SUFFIX'
+`HOST_EXECUTABLE_SUFFIX'
Define this macro to be a C string representing the suffix for
executable files on your host machine. If you do not define this
macro, GCC will use the null string as the suffix for executable
files.
-'HOST_BIT_BUCKET'
+`HOST_BIT_BUCKET'
A pathname defined by the host operating system, which can be
- opened as a file and written to, but all the information written is
- discarded. This is commonly known as a "bit bucket" or "null
- device". If you do not define this macro, GCC will use '/dev/null'
- as the bit bucket. If the host does not support a bit bucket,
- define this macro to an invalid filename.
+ opened as a file and written to, but all the information written
+ is discarded. This is commonly known as a "bit bucket" or "null
+ device". If you do not define this macro, GCC will use
+ `/dev/null' as the bit bucket. If the host does not support a bit
+ bucket, define this macro to an invalid filename.
-'UPDATE_PATH_HOST_CANONICALIZE (PATH)'
+`UPDATE_PATH_HOST_CANONICALIZE (PATH)'
If defined, a C statement (sans semicolon) that performs
host-dependent canonicalization when a path used in a compilation
driver or preprocessor is canonicalized. PATH is a malloc-ed path
@@ -38512,19 +38959,19 @@ macros in 'xm-MACHINE.h'.
into a different buffer, the old path should be freed and the new
buffer should have been allocated with malloc.
-'DUMPFILE_FORMAT'
+`DUMPFILE_FORMAT'
Define this macro to be a C string representing the format to use
for constructing the index part of debugging dump file names. The
- resultant string must fit in fifteen bytes. The full filename will
- be the concatenation of: the prefix of the assembler file name, the
- string resulting from applying this format to an index number, and
- a string unique to each dump file kind, e.g. 'rtl'.
+ resultant string must fit in fifteen bytes. The full filename
+ will be the concatenation of: the prefix of the assembler file
+ name, the string resulting from applying this format to an index
+ number, and a string unique to each dump file kind, e.g. `rtl'.
- If you do not define this macro, GCC will use '.%02d.'. You should
+ If you do not define this macro, GCC will use `.%02d.'. You should
define this macro if using the default will create an invalid file
name.
-'DELETE_IF_ORDINARY'
+`DELETE_IF_ORDINARY'
Define this macro to be a C statement (sans semicolon) that
performs host-dependent removal of ordinary temp files in the
compilation driver.
@@ -38534,9 +38981,9 @@ macros in 'xm-MACHINE.h'.
reliably remove the temp file as, for example, on VMS which allows
multiple versions of a file.
-'HOST_LACKS_INODE_NUMBERS'
- Define this macro if the host filesystem does not report meaningful
- inode numbers in struct stat.
+`HOST_LACKS_INODE_NUMBERS'
+ Define this macro if the host filesystem does not report
+ meaningful inode numbers in struct stat.

File: gccint.info, Node: Host Misc, Prev: Filesystem, Up: Host Config
@@ -38544,57 +38991,57 @@ File: gccint.info, Node: Host Misc, Prev: Filesystem, Up: Host Config
18.3 Host Misc
==============
-'FATAL_EXIT_CODE'
+`FATAL_EXIT_CODE'
A C expression for the status code to be returned when the compiler
exits after serious errors. The default is the system-provided
- macro 'EXIT_FAILURE', or '1' if the system doesn't define that
+ macro `EXIT_FAILURE', or `1' if the system doesn't define that
macro. Define this macro only if these defaults are incorrect.
-'SUCCESS_EXIT_CODE'
+`SUCCESS_EXIT_CODE'
A C expression for the status code to be returned when the compiler
exits without serious errors. (Warnings are not serious errors.)
- The default is the system-provided macro 'EXIT_SUCCESS', or '0' if
+ The default is the system-provided macro `EXIT_SUCCESS', or `0' if
the system doesn't define that macro. Define this macro only if
these defaults are incorrect.
-'USE_C_ALLOCA'
+`USE_C_ALLOCA'
Define this macro if GCC should use the C implementation of
- 'alloca' provided by 'libiberty.a'. This only affects how some
+ `alloca' provided by `libiberty.a'. This only affects how some
parts of the compiler itself allocate memory. It does not change
code generation.
- When GCC is built with a compiler other than itself, the C 'alloca'
+ When GCC is built with a compiler other than itself, the C `alloca'
is always used. This is because most other implementations have
serious bugs. You should define this macro only on a system where
- no stack-based 'alloca' can possibly work. For instance, if a
+ no stack-based `alloca' can possibly work. For instance, if a
system has a small limit on the size of the stack, GCC's builtin
- 'alloca' will not work reliably.
+ `alloca' will not work reliably.
-'COLLECT2_HOST_INITIALIZATION'
+`COLLECT2_HOST_INITIALIZATION'
If defined, a C statement (sans semicolon) that performs
- host-dependent initialization when 'collect2' is being initialized.
+ host-dependent initialization when `collect2' is being initialized.
-'GCC_DRIVER_HOST_INITIALIZATION'
+`GCC_DRIVER_HOST_INITIALIZATION'
If defined, a C statement (sans semicolon) that performs
host-dependent initialization when a compilation driver is being
initialized.
-'HOST_LONG_LONG_FORMAT'
- If defined, the string used to indicate an argument of type 'long
- long' to functions like 'printf'. The default value is '"ll"'.
+`HOST_LONG_LONG_FORMAT'
+ If defined, the string used to indicate an argument of type `long
+ long' to functions like `printf'. The default value is `"ll"'.
-'HOST_LONG_FORMAT'
- If defined, the string used to indicate an argument of type 'long'
- to functions like 'printf'. The default value is '"l"'.
+`HOST_LONG_FORMAT'
+ If defined, the string used to indicate an argument of type `long'
+ to functions like `printf'. The default value is `"l"'.
-'HOST_PTR_PRINTF'
- If defined, the string used to indicate an argument of type 'void
- *' to functions like 'printf'. The default value is '"%p"'.
+`HOST_PTR_PRINTF'
+ If defined, the string used to indicate an argument of type `void
+ *' to functions like `printf'. The default value is `"%p"'.
- In addition, if 'configure' generates an incorrect definition of any of
-the macros in 'auto-host.h', you can override that definition in a host
-configuration header. If you need to do this, first see if it is
-possible to fix 'configure'.
+ In addition, if `configure' generates an incorrect definition of any
+of the macros in `auto-host.h', you can override that definition in a
+host configuration header. If you need to do this, first see if it is
+possible to fix `configure'.

File: gccint.info, Node: Fragments, Next: Collect2, Prev: Host Config, Up: Top
@@ -38602,28 +39049,28 @@ File: gccint.info, Node: Fragments, Next: Collect2, Prev: Host Config, Up: T
19 Makefile Fragments
*********************
-When you configure GCC using the 'configure' script, it will construct
-the file 'Makefile' from the template file 'Makefile.in'. When it does
-this, it can incorporate makefile fragments from the 'config' directory.
-These are used to set Makefile parameters that are not amenable to being
-calculated by autoconf. The list of fragments to incorporate is set by
-'config.gcc' (and occasionally 'config.build' and 'config.host'); *Note
-System Config::.
+When you configure GCC using the `configure' script, it will construct
+the file `Makefile' from the template file `Makefile.in'. When it does
+this, it can incorporate makefile fragments from the `config'
+directory. These are used to set Makefile parameters that are not
+amenable to being calculated by autoconf. The list of fragments to
+incorporate is set by `config.gcc' (and occasionally `config.build' and
+`config.host'); *Note System Config::.
- Fragments are named either 't-TARGET' or 'x-HOST', depending on whether
-they are relevant to configuring GCC to produce code for a particular
-target, or to configuring GCC to run on a particular host. Here TARGET
-and HOST are mnemonics which usually have some relationship to the
-canonical system name, but no formal connection.
+ Fragments are named either `t-TARGET' or `x-HOST', depending on
+whether they are relevant to configuring GCC to produce code for a
+particular target, or to configuring GCC to run on a particular host.
+Here TARGET and HOST are mnemonics which usually have some relationship
+to the canonical system name, but no formal connection.
If these files do not exist, it means nothing needs to be added for a
-given target or host. Most targets need a few 't-TARGET' fragments, but
-needing 'x-HOST' fragments is rare.
+given target or host. Most targets need a few `t-TARGET' fragments,
+but needing `x-HOST' fragments is rare.
* Menu:
-* Target Fragment:: Writing 't-TARGET' files.
-* Host Fragment:: Writing 'x-HOST' files.
+* Target Fragment:: Writing `t-TARGET' files.
+* Host Fragment:: Writing `x-HOST' files.

File: gccint.info, Node: Target Fragment, Next: Host Fragment, Up: Fragments
@@ -38633,169 +39080,169 @@ File: gccint.info, Node: Target Fragment, Next: Host Fragment, Up: Fragments
Target makefile fragments can set these Makefile variables.
-'LIBGCC2_CFLAGS'
- Compiler flags to use when compiling 'libgcc2.c'.
+`LIBGCC2_CFLAGS'
+ Compiler flags to use when compiling `libgcc2.c'.
-'LIB2FUNCS_EXTRA'
+`LIB2FUNCS_EXTRA'
A list of source file names to be compiled or assembled and
- inserted into 'libgcc.a'.
+ inserted into `libgcc.a'.
-'CRTSTUFF_T_CFLAGS'
- Special flags used when compiling 'crtstuff.c'. *Note
+`CRTSTUFF_T_CFLAGS'
+ Special flags used when compiling `crtstuff.c'. *Note
Initialization::.
-'CRTSTUFF_T_CFLAGS_S'
- Special flags used when compiling 'crtstuff.c' for shared linking.
- Used if you use 'crtbeginS.o' and 'crtendS.o' in 'EXTRA-PARTS'.
+`CRTSTUFF_T_CFLAGS_S'
+ Special flags used when compiling `crtstuff.c' for shared linking.
+ Used if you use `crtbeginS.o' and `crtendS.o' in `EXTRA-PARTS'.
*Note Initialization::.
-'MULTILIB_OPTIONS'
+`MULTILIB_OPTIONS'
For some targets, invoking GCC in different ways produces objects
that can not be linked together. For example, for some targets GCC
produces both big and little endian code. For these targets, you
- must arrange for multiple versions of 'libgcc.a' to be compiled,
+ must arrange for multiple versions of `libgcc.a' to be compiled,
one for each set of incompatible options. When GCC invokes the
- linker, it arranges to link in the right version of 'libgcc.a',
+ linker, it arranges to link in the right version of `libgcc.a',
based on the command line options used.
- The 'MULTILIB_OPTIONS' macro lists the set of options for which
- special versions of 'libgcc.a' must be built. Write options that
+ The `MULTILIB_OPTIONS' macro lists the set of options for which
+ special versions of `libgcc.a' must be built. Write options that
are mutually incompatible side by side, separated by a slash.
Write options that may be used together separated by a space. The
build procedure will build all combinations of compatible options.
- For example, if you set 'MULTILIB_OPTIONS' to 'm68000/m68020
- msoft-float', 'Makefile' will build special versions of 'libgcc.a'
- using the following sets of options: '-m68000', '-m68020',
- '-msoft-float', '-m68000 -msoft-float', and '-m68020 -msoft-float'.
+ For example, if you set `MULTILIB_OPTIONS' to `m68000/m68020
+ msoft-float', `Makefile' will build special versions of `libgcc.a'
+ using the following sets of options: `-m68000', `-m68020',
+ `-msoft-float', `-m68000 -msoft-float', and `-m68020 -msoft-float'.
-'MULTILIB_DIRNAMES'
- If 'MULTILIB_OPTIONS' is used, this variable specifies the
+`MULTILIB_DIRNAMES'
+ If `MULTILIB_OPTIONS' is used, this variable specifies the
directory names that should be used to hold the various libraries.
- Write one element in 'MULTILIB_DIRNAMES' for each element in
- 'MULTILIB_OPTIONS'. If 'MULTILIB_DIRNAMES' is not used, the
- default value will be 'MULTILIB_OPTIONS', with all slashes treated
+ Write one element in `MULTILIB_DIRNAMES' for each element in
+ `MULTILIB_OPTIONS'. If `MULTILIB_DIRNAMES' is not used, the
+ default value will be `MULTILIB_OPTIONS', with all slashes treated
as spaces.
- 'MULTILIB_DIRNAMES' describes the multilib directories using GCC
+ `MULTILIB_DIRNAMES' describes the multilib directories using GCC
conventions and is applied to directories that are part of the GCC
installation. When multilib-enabled, the compiler will add a
subdirectory of the form PREFIX/MULTILIB before each directory in
the search path for libraries and crt files.
- For example, if 'MULTILIB_OPTIONS' is set to 'm68000/m68020
- msoft-float', then the default value of 'MULTILIB_DIRNAMES' is
- 'm68000 m68020 msoft-float'. You may specify a different value if
+ For example, if `MULTILIB_OPTIONS' is set to `m68000/m68020
+ msoft-float', then the default value of `MULTILIB_DIRNAMES' is
+ `m68000 m68020 msoft-float'. You may specify a different value if
you desire a different set of directory names.
-'MULTILIB_MATCHES'
- Sometimes the same option may be written in two different ways. If
- an option is listed in 'MULTILIB_OPTIONS', GCC needs to know about
- any synonyms. In that case, set 'MULTILIB_MATCHES' to a list of
- items of the form 'option=option' to describe all relevant
- synonyms. For example, 'm68000=mc68000 m68020=mc68020'.
+`MULTILIB_MATCHES'
+ Sometimes the same option may be written in two different ways.
+ If an option is listed in `MULTILIB_OPTIONS', GCC needs to know
+ about any synonyms. In that case, set `MULTILIB_MATCHES' to a
+ list of items of the form `option=option' to describe all relevant
+ synonyms. For example, `m68000=mc68000 m68020=mc68020'.
-'MULTILIB_EXCEPTIONS'
- Sometimes when there are multiple sets of 'MULTILIB_OPTIONS' being
+`MULTILIB_EXCEPTIONS'
+ Sometimes when there are multiple sets of `MULTILIB_OPTIONS' being
specified, there are combinations that should not be built. In
- that case, set 'MULTILIB_EXCEPTIONS' to be all of the switch
+ that case, set `MULTILIB_EXCEPTIONS' to be all of the switch
exceptions in shell case syntax that should not be built.
For example the ARM processor cannot execute both hardware floating
point instructions and the reduced size THUMB instructions at the
same time, so there is no need to build libraries with both of
- these options enabled. Therefore 'MULTILIB_EXCEPTIONS' is set to:
+ these options enabled. Therefore `MULTILIB_EXCEPTIONS' is set to:
*mthumb/*mhard-float*
-'MULTILIB_REQUIRED'
+`MULTILIB_REQUIRED'
Sometimes when there are only a few combinations are required, it
- would be a big effort to come up with a 'MULTILIB_EXCEPTIONS' list
+ would be a big effort to come up with a `MULTILIB_EXCEPTIONS' list
to cover all undesired ones. In such a case, just listing all the
- required combinations in 'MULTILIB_REQUIRED' would be more
+ required combinations in `MULTILIB_REQUIRED' would be more
straightforward.
- The way to specify the entries in 'MULTILIB_REQUIRED' is same with
- the way used for 'MULTILIB_EXCEPTIONS', only this time what are
+ The way to specify the entries in `MULTILIB_REQUIRED' is same with
+ the way used for `MULTILIB_EXCEPTIONS', only this time what are
required will be specified. Suppose there are multiple sets of
- 'MULTILIB_OPTIONS' and only two combinations are required, one for
+ `MULTILIB_OPTIONS' and only two combinations are required, one for
ARMv7-M and one for ARMv7-R with hard floating-point ABI and FPU,
- the 'MULTILIB_REQUIRED' can be set to:
- MULTILIB_REQUIRED = mthumb/march=armv7-m
- MULTILIB_REQUIRED += march=armv7-r/mfloat-abi=hard/mfpu=vfpv3-d16
+ the `MULTILIB_REQUIRED' can be set to:
+ `MULTILIB_REQUIRED' = mthumb/march=armv7-m
+ `MULTILIB_REQUIRED' += march=armv7-r/mfloat-abi=hard/mfpu=vfpv3-d16
- The 'MULTILIB_REQUIRED' can be used together with
- 'MULTILIB_EXCEPTIONS'. The option combinations generated from
- 'MULTILIB_OPTIONS' will be filtered by 'MULTILIB_EXCEPTIONS' and
- then by 'MULTILIB_REQUIRED'.
+ The `MULTILIB_REQUIRED' can be used together with
+ `MULTILIB_EXCEPTIONS'. The option combinations generated from
+ `MULTILIB_OPTIONS' will be filtered by `MULTILIB_EXCEPTIONS' and
+ then by `MULTILIB_REQUIRED'.
-'MULTILIB_REUSE'
+`MULTILIB_REUSE'
Sometimes it is desirable to reuse one existing multilib for
different sets of options. Such kind of reuse can minimize the
number of multilib variants. And for some targets it is better to
reuse an existing multilib than to fall back to default multilib
when there is no corresponding multilib. This can be done by
- adding reuse rules to 'MULTILIB_REUSE'.
+ adding reuse rules to `MULTILIB_REUSE'.
A reuse rule is comprised of two parts connected by equality sign.
The left part is option set used to build multilib and the right
part is option set that will reuse this multilib. The order of
options in the left part matters and should be same with those
- specified in 'MULTILIB_REQUIRED' or aligned with order in
- 'MULTILIB_OPTIONS'. There is no such limitation for options in
+ specified in `MULTILIB_REQUIRED' or aligned with order in
+ `MULTILIB_OPTIONS'. There is no such limitation for options in
right part as we don't build multilib from them. But the equality
sign in both parts should be replaced with period.
- The 'MULTILIB_REUSE' is different from 'MULTILIB_MATCHES' in that
+ The `MULTILIB_REUSE' is different from `MULTILIB_MATCHES' in that
it sets up relations between two option sets rather than two
options. Here is an example to demo how we reuse libraries built
in Thumb mode for applications built in ARM mode:
- MULTILIB_REUSE = mthumb/march.armv7-r=marm/march.armv7-r
+ `MULTILIB_REUSE' = mthumb/march.armv7-r=marm/march.armv7-r
- Before the advent of 'MULTILIB_REUSE', GCC select multilib by
- comparing command line options with options used to build multilib.
- The 'MULTILIB_REUSE' is complementary to that way. Only when the
- original comparison matches nothing it will work to see if it is OK
- to reuse some existing multilib.
+ Before the advent of `MULTILIB_REUSE', GCC select multilib by
+ comparing command line options with options used to build
+ multilib. The `MULTILIB_REUSE' is complementary to that way.
+ Only when the original comparison matches nothing it will work to
+ see if it is OK to reuse some existing multilib.
-'MULTILIB_EXTRA_OPTS'
+`MULTILIB_EXTRA_OPTS'
Sometimes it is desirable that when building multiple versions of
- 'libgcc.a' certain options should always be passed on to the
- compiler. In that case, set 'MULTILIB_EXTRA_OPTS' to be the list
+ `libgcc.a' certain options should always be passed on to the
+ compiler. In that case, set `MULTILIB_EXTRA_OPTS' to be the list
of options to be used for all builds. If you set this, you should
- probably set 'CRTSTUFF_T_CFLAGS' to a dash followed by it.
+ probably set `CRTSTUFF_T_CFLAGS' to a dash followed by it.
-'MULTILIB_OSDIRNAMES'
- If 'MULTILIB_OPTIONS' is used, this variable specifies a list of
+`MULTILIB_OSDIRNAMES'
+ If `MULTILIB_OPTIONS' is used, this variable specifies a list of
subdirectory names, that are used to modify the search path
- depending on the chosen multilib. Unlike 'MULTILIB_DIRNAMES',
- 'MULTILIB_OSDIRNAMES' describes the multilib directories using
+ depending on the chosen multilib. Unlike `MULTILIB_DIRNAMES',
+ `MULTILIB_OSDIRNAMES' describes the multilib directories using
operating systems conventions, and is applied to the directories
- such as 'lib' or those in the 'LIBRARY_PATH' environment variable.
- The format is either the same as of 'MULTILIB_DIRNAMES', or a set
- of mappings. When it is the same as 'MULTILIB_DIRNAMES', it
+ such as `lib' or those in the `LIBRARY_PATH' environment variable.
+ The format is either the same as of `MULTILIB_DIRNAMES', or a set
+ of mappings. When it is the same as `MULTILIB_DIRNAMES', it
describes the multilib directories using operating system
conventions, rather than GCC conventions. When it is a set of
mappings of the form GCCDIR=OSDIR, the left side gives the GCC
convention and the right gives the equivalent OS defined location.
- If the OSDIR part begins with a '!', GCC will not search in the
+ If the OSDIR part begins with a `!', GCC will not search in the
non-multilib directory and use exclusively the multilib directory.
Otherwise, the compiler will examine the search path for libraries
and crt files twice; the first time it will add MULTILIB to each
directory in the search path, the second it will not.
For configurations that support both multilib and multiarch,
- 'MULTILIB_OSDIRNAMES' also encodes the multiarch name, thus
- subsuming 'MULTIARCH_DIRNAME'. The multiarch name is appended to
+ `MULTILIB_OSDIRNAMES' also encodes the multiarch name, thus
+ subsuming `MULTIARCH_DIRNAME'. The multiarch name is appended to
each directory name, separated by a colon (e.g.
- '../lib32:i386-linux-gnu').
+ `../lib32:i386-linux-gnu').
Each multiarch subdirectory will be searched before the
corresponding OS multilib directory, for example
- '/lib/i386-linux-gnu' before '/lib/../lib32'. The multiarch name
+ `/lib/i386-linux-gnu' before `/lib/../lib32'. The multiarch name
will also be used to modify the system header search path, as
- explained for 'MULTIARCH_DIRNAME'.
+ explained for `MULTIARCH_DIRNAME'.
-'MULTIARCH_DIRNAME'
+`MULTIARCH_DIRNAME'
This variable specifies the multiarch name for configurations that
are multiarch-enabled but not multilibbed configurations.
@@ -38804,34 +39251,34 @@ Target makefile fragments can set these Makefile variables.
locations. The compiler will add a multiarch subdirectory of the
form PREFIX/MULTIARCH before each directory in the library and crt
search path. It will also add two directories
- 'LOCAL_INCLUDE_DIR'/MULTIARCH and
- 'NATIVE_SYSTEM_HEADER_DIR'/MULTIARCH) to the system header search
- path, respectively before 'LOCAL_INCLUDE_DIR' and
- 'NATIVE_SYSTEM_HEADER_DIR'.
+ `LOCAL_INCLUDE_DIR'/MULTIARCH and
+ `NATIVE_SYSTEM_HEADER_DIR'/MULTIARCH) to the system header search
+ path, respectively before `LOCAL_INCLUDE_DIR' and
+ `NATIVE_SYSTEM_HEADER_DIR'.
- 'MULTIARCH_DIRNAME' is not used for configurations that support
+ `MULTIARCH_DIRNAME' is not used for configurations that support
both multilib and multiarch. In that case, multiarch names are
- encoded in 'MULTILIB_OSDIRNAMES' instead.
+ encoded in `MULTILIB_OSDIRNAMES' instead.
More documentation about multiarch can be found at
- <http://wiki.debian.org/Multiarch>.
+ `http://wiki.debian.org/Multiarch'.
-'SPECS'
- Unfortunately, setting 'MULTILIB_EXTRA_OPTS' is not enough, since
+`SPECS'
+ Unfortunately, setting `MULTILIB_EXTRA_OPTS' is not enough, since
it does not affect the build of target libraries, at least not the
build of the default multilib. One possible work-around is to use
- 'DRIVER_SELF_SPECS' to bring options from the 'specs' file as if
- they had been passed in the compiler driver command line. However,
- you don't want to be adding these options after the toolchain is
- installed, so you can instead tweak the 'specs' file that will be
- used during the toolchain build, while you still install the
- original, built-in 'specs'. The trick is to set 'SPECS' to some
- other filename (say 'specs.install'), that will then be created out
- of the built-in specs, and introduce a 'Makefile' rule to generate
- the 'specs' file that's going to be used at build time out of your
- 'specs.install'.
-
-'T_CFLAGS'
+ `DRIVER_SELF_SPECS' to bring options from the `specs' file as if
+ they had been passed in the compiler driver command line.
+ However, you don't want to be adding these options after the
+ toolchain is installed, so you can instead tweak the `specs' file
+ that will be used during the toolchain build, while you still
+ install the original, built-in `specs'. The trick is to set
+ `SPECS' to some other filename (say `specs.install'), that will
+ then be created out of the built-in specs, and introduce a
+ `Makefile' rule to generate the `specs' file that's going to be
+ used at build time out of your `specs.install'.
+
+`T_CFLAGS'
These are extra flags to pass to the C compiler. They are used
both when building GCC, and when compiling things with the
just-built GCC. This variable is deprecated and should not be
@@ -38843,79 +39290,79 @@ File: gccint.info, Node: Host Fragment, Prev: Target Fragment, Up: Fragments
19.2 Host Makefile Fragments
============================
-The use of 'x-HOST' fragments is discouraged. You should only use it
+The use of `x-HOST' fragments is discouraged. You should only use it
for makefile dependencies.

File: gccint.info, Node: Collect2, Next: Header Dirs, Prev: Fragments, Up: Top
-20 'collect2'
+20 `collect2'
*************
-GCC uses a utility called 'collect2' on nearly all systems to arrange to
-call various initialization functions at start time.
+GCC uses a utility called `collect2' on nearly all systems to arrange
+to call various initialization functions at start time.
- The program 'collect2' works by linking the program once and looking
+ The program `collect2' works by linking the program once and looking
through the linker output file for symbols with particular names
indicating they are constructor functions. If it finds any, it creates
-a new temporary '.c' file containing a table of them, compiles it, and
+a new temporary `.c' file containing a table of them, compiles it, and
links the program a second time including that file.
The actual calls to the constructors are carried out by a subroutine
-called '__main', which is called (automatically) at the beginning of the
-body of 'main' (provided 'main' was compiled with GNU CC). Calling
-'__main' is necessary, even when compiling C code, to allow linking C
-and C++ object code together. (If you use '-nostdlib', you get an
-unresolved reference to '__main', since it's defined in the standard GCC
-library. Include '-lgcc' at the end of your compiler command line to
-resolve this reference.)
-
- The program 'collect2' is installed as 'ld' in the directory where the
-passes of the compiler are installed. When 'collect2' needs to find the
-_real_ 'ld', it tries the following file names:
+called `__main', which is called (automatically) at the beginning of
+the body of `main' (provided `main' was compiled with GNU CC). Calling
+`__main' is necessary, even when compiling C code, to allow linking C
+and C++ object code together. (If you use `-nostdlib', you get an
+unresolved reference to `__main', since it's defined in the standard
+GCC library. Include `-lgcc' at the end of your compiler command line
+to resolve this reference.)
+
+ The program `collect2' is installed as `ld' in the directory where the
+passes of the compiler are installed. When `collect2' needs to find
+the _real_ `ld', it tries the following file names:
* a hard coded linker file name, if GCC was configured with the
- '--with-ld' option.
+ `--with-ld' option.
- * 'real-ld' in the directories listed in the compiler's search
+ * `real-ld' in the directories listed in the compiler's search
directories.
- * 'real-ld' in the directories listed in the environment variable
- 'PATH'.
+ * `real-ld' in the directories listed in the environment variable
+ `PATH'.
- * The file specified in the 'REAL_LD_FILE_NAME' configuration macro,
+ * The file specified in the `REAL_LD_FILE_NAME' configuration macro,
if specified.
- * 'ld' in the compiler's search directories, except that 'collect2'
+ * `ld' in the compiler's search directories, except that `collect2'
will not execute itself recursively.
- * 'ld' in 'PATH'.
+ * `ld' in `PATH'.
"The compiler's search directories" means all the directories where
-'gcc' searches for passes of the compiler. This includes directories
-that you specify with '-B'.
+`gcc' searches for passes of the compiler. This includes directories
+that you specify with `-B'.
Cross-compilers search a little differently:
- * 'real-ld' in the compiler's search directories.
+ * `real-ld' in the compiler's search directories.
- * 'TARGET-real-ld' in 'PATH'.
+ * `TARGET-real-ld' in `PATH'.
- * The file specified in the 'REAL_LD_FILE_NAME' configuration macro,
+ * The file specified in the `REAL_LD_FILE_NAME' configuration macro,
if specified.
- * 'ld' in the compiler's search directories.
+ * `ld' in the compiler's search directories.
- * 'TARGET-ld' in 'PATH'.
+ * `TARGET-ld' in `PATH'.
- 'collect2' explicitly avoids running 'ld' using the file name under
-which 'collect2' itself was invoked. In fact, it remembers up a list of
-such names--in case one copy of 'collect2' finds another copy (or
-version) of 'collect2' installed as 'ld' in a second place in the search
-path.
+ `collect2' explicitly avoids running `ld' using the file name under
+which `collect2' itself was invoked. In fact, it remembers up a list
+of such names--in case one copy of `collect2' finds another copy (or
+version) of `collect2' installed as `ld' in a second place in the
+search path.
- 'collect2' searches for the utilities 'nm' and 'strip' using the same
-algorithm as above for 'ld'.
+ `collect2' searches for the utilities `nm' and `strip' using the same
+algorithm as above for `ld'.

File: gccint.info, Node: Header Dirs, Next: Type Information, Prev: Collect2, Up: Top
@@ -38923,29 +39370,29 @@ File: gccint.info, Node: Header Dirs, Next: Type Information, Prev: Collect2,
21 Standard Header File Directories
***********************************
-'GCC_INCLUDE_DIR' means the same thing for native and cross. It is
+`GCC_INCLUDE_DIR' means the same thing for native and cross. It is
where GCC stores its private include files, and also where GCC stores
-the fixed include files. A cross compiled GCC runs 'fixincludes' on the
-header files in '$(tooldir)/include'. (If the cross compilation header
-files need to be fixed, they must be installed before GCC is built. If
-the cross compilation header files are already suitable for GCC, nothing
-special need be done).
-
- 'GPLUSPLUS_INCLUDE_DIR' means the same thing for native and cross. It
-is where 'g++' looks first for header files. The C++ library installs
+the fixed include files. A cross compiled GCC runs `fixincludes' on
+the header files in `$(tooldir)/include'. (If the cross compilation
+header files need to be fixed, they must be installed before GCC is
+built. If the cross compilation header files are already suitable for
+GCC, nothing special need be done).
+
+ `GPLUSPLUS_INCLUDE_DIR' means the same thing for native and cross. It
+is where `g++' looks first for header files. The C++ library installs
only target independent header files in that directory.
- 'LOCAL_INCLUDE_DIR' is used only by native compilers. GCC doesn't
-install anything there. It is normally '/usr/local/include'. This is
+ `LOCAL_INCLUDE_DIR' is used only by native compilers. GCC doesn't
+install anything there. It is normally `/usr/local/include'. This is
where local additions to a packaged system should place header files.
- 'CROSS_INCLUDE_DIR' is used only by cross compilers. GCC doesn't
+ `CROSS_INCLUDE_DIR' is used only by cross compilers. GCC doesn't
install anything there.
- 'TOOL_INCLUDE_DIR' is used for both native and cross compilers. It is
+ `TOOL_INCLUDE_DIR' is used for both native and cross compilers. It is
the place for other packages to install header files that GCC will use.
-For a cross-compiler, this is the equivalent of '/usr/include'. When
-you build a cross-compiler, 'fixincludes' processes any header files in
+For a cross-compiler, this is the equivalent of `/usr/include'. When
+you build a cross-compiler, `fixincludes' processes any header files in
this directory.

@@ -38961,24 +39408,26 @@ implement precompiled headers.
A full C++ parser would be too complicated for this task, so a limited
subset of C++ is interpreted and special markers are used to determine
-what parts of the source to look at. All 'struct', 'union' and
-'template' structure declarations that define data structures that are
+what parts of the source to look at. All `struct', `union' and
+`template' structure declarations that define data structures that are
allocated under control of the garbage collector must be marked. All
global variables that hold pointers to garbage-collected memory must
-also be marked. Finally, all global variables that need to be saved and
-restored by a precompiled header must be marked. (The precompiled
+also be marked. Finally, all global variables that need to be saved
+and restored by a precompiled header must be marked. (The precompiled
header mechanism can only save static variables if they're scalar.
-Complex data structures must be allocated in garbage-collected memory to
-be saved in a precompiled header.)
+Complex data structures must be allocated in garbage-collected memory
+to be saved in a precompiled header.)
The full format of a marker is
GTY (([OPTION] [(PARAM)], [OPTION] [(PARAM)] ...))
-but in most cases no options are needed. The outer double parentheses
-are still necessary, though: 'GTY(())'. Markers can appear:
+ but in most cases no options are needed. The outer double parentheses
+are still necessary, though: `GTY(())'. Markers can appear:
* In a structure definition, before the open brace;
- * In a global variable declaration, after the keyword 'static' or
- 'extern'; and
+
+ * In a global variable declaration, after the keyword `static' or
+ `extern'; and
+
* In a structure field definition, before the name of the field.
Here are some examples of marking simple data structures and globals.
@@ -38996,29 +39445,30 @@ are still necessary, though: 'GTY(())'. Markers can appear:
static GTY(()) struct TAG *LIST; /* points to GC memory */
static GTY(()) int COUNTER; /* save counter in a PCH */
- The parser understands simple typedefs such as 'typedef struct TAG
-*NAME;' and 'typedef int NAME;'. These don't need to be marked.
+ The parser understands simple typedefs such as `typedef struct TAG
+*NAME;' and `typedef int NAME;'. These don't need to be marked.
- Since 'gengtype''s understanding of C++ is limited, there are several
+ Since `gengtype''s understanding of C++ is limited, there are several
constructs and declarations that are not supported inside
classes/structures marked for automatic GC code generation. The
-following C++ constructs produce a 'gengtype' error on
+following C++ constructs produce a `gengtype' error on
structures/classes marked for automatic GC code generation:
* Type definitions inside classes/structures are not supported.
+
* Enumerations inside classes/structures are not supported.
- If you have a class or structure using any of the above constructs, you
-need to mark that class as 'GTY ((user))' and provide your own marking
-routines (see section *note User GC:: for details).
+ If you have a class or structure using any of the above constructs,
+you need to mark that class as `GTY ((user))' and provide your own
+marking routines (see section *note User GC:: for details).
It is always valid to include function definitions inside classes.
-Those are always ignored by 'gengtype', as it only cares about data
+Those are always ignored by `gengtype', as it only cares about data
members.
* Menu:
-* GTY Options:: What goes inside a 'GTY(())'.
+* GTY Options:: What goes inside a `GTY(())'.
* Inheritance and GTY:: Adding GTY to a class hierarchy.
* User GC:: Adding user-provided GC marking routines.
* GGC Roots:: Making global variables GGC roots.
@@ -39029,29 +39479,32 @@ members.

File: gccint.info, Node: GTY Options, Next: Inheritance and GTY, Up: Type Information
-22.1 The Inside of a 'GTY(())'
+22.1 The Inside of a `GTY(())'
==============================
-Sometimes the C code is not enough to fully describe the type structure.
-Extra information can be provided with 'GTY' options and additional
-markers. Some options take a parameter, which may be either a string or
-a type name, depending on the parameter. If an option takes no
-parameter, it is acceptable either to omit the parameter entirely, or to
-provide an empty string as a parameter. For example, 'GTY ((skip))' and
-'GTY ((skip ("")))' are equivalent.
+Sometimes the C code is not enough to fully describe the type
+structure. Extra information can be provided with `GTY' options and
+additional markers. Some options take a parameter, which may be either
+a string or a type name, depending on the parameter. If an option
+takes no parameter, it is acceptable either to omit the parameter
+entirely, or to provide an empty string as a parameter. For example,
+`GTY ((skip))' and `GTY ((skip ("")))' are equivalent.
When the parameter is a string, often it is a fragment of C code. Four
special escapes may be used in these strings, to refer to pieces of the
data structure being marked:
-'%h'
+`%h'
The current structure.
-'%1'
+
+`%1'
The structure that immediately contains the current structure.
-'%0'
+
+`%0'
The outermost structure that contains the current structure.
-'%a'
- A partial expression of the form '[i1][i2]...' that indexes the
+
+`%a'
+ A partial expression of the form `[i1][i2]...' that indexes the
array item currently being marked.
For instance, suppose that you have a structure of the form
@@ -39061,9 +39514,9 @@ data structure being marked:
struct B {
struct A foo[12];
};
-and 'b' is a variable of type 'struct B'. When marking 'b.foo[11]',
-'%h' would expand to 'b.foo[11]', '%0' and '%1' would both expand to
-'b', and '%a' would expand to '[11]'.
+ and `b' is a variable of type `struct B'. When marking `b.foo[11]',
+`%h' would expand to `b.foo[11]', `%0' and `%1' would both expand to
+`b', and `%a' would expand to `[11]'.
As in ordinary C, adjacent strings will be concatenated; this is
helpful when you have a complicated expression.
@@ -39073,8 +39526,7 @@ helpful when you have a complicated expression.
The available options are:
-'length ("EXPRESSION")'
-
+`length ("EXPRESSION")'
There are two places the type machinery will need to be explicitly
told the length of an array of non-atomic objects. The first case
is when a structure ends in a variable-length array, like this:
@@ -39083,52 +39535,49 @@ helpful when you have a complicated expression.
rtx GTY ((length ("%h.num_elem"))) elem[1];
};
- In this case, the 'length' option is used to override the specified
- array length (which should usually be '1'). The parameter of the
+ In this case, the `length' option is used to override the specified
+ array length (which should usually be `1'). The parameter of the
option is a fragment of C code that calculates the length.
The second case is when a structure or a global variable contains a
pointer to an array, like this:
struct gimple_omp_for_iter * GTY((length ("%h.collapse"))) iter;
- In this case, 'iter' has been allocated by writing something like
+ In this case, `iter' has been allocated by writing something like
x->iter = ggc_alloc_cleared_vec_gimple_omp_for_iter (collapse);
- and the 'collapse' provides the length of the field.
-
- This second use of 'length' also works on global variables, like:
- static GTY((length("reg_known_value_size"))) rtx *reg_known_value;
+ and the `collapse' provides the length of the field.
- Note that the 'length' option is only meant for use with arrays of
- non-atomic objects, that is, objects that contain pointers pointing
- to other GTY-managed objects. For other GC-allocated arrays and
- strings you should use 'atomic'.
+ This second use of `length' also works on global variables, like: static GTY((length("reg_known_value_size"))) rtx *reg_known_value;
-'skip'
+ Note that the `length' option is only meant for use with arrays of
+ non-atomic objects, that is, objects that contain pointers
+ pointing to other GTY-managed objects. For other GC-allocated
+ arrays and strings you should use `atomic'.
- If 'skip' is applied to a field, the type machinery will ignore it.
+`skip'
+ If `skip' is applied to a field, the type machinery will ignore it.
This is somewhat dangerous; the only safe use is in a union when
one field really isn't ever used.
Use this to mark types that need to be marked by user gc routines,
- but are not refered to in a template argument. So if you have some
- user gc type T1 and a non user gc type T2 you can give T2 the
+ but are not refered to in a template argument. So if you have
+ some user gc type T1 and a non user gc type T2 you can give T2 the
for_user option so that the marking functions for T1 can call non
mangled functions to mark T2.
-'desc ("EXPRESSION")'
-'tag ("CONSTANT")'
-'default'
-
- The type machinery needs to be told which field of a 'union' is
+`desc ("EXPRESSION")'
+`tag ("CONSTANT")'
+`default'
+ The type machinery needs to be told which field of a `union' is
currently active. This is done by giving each field a constant
- 'tag' value, and then specifying a discriminator using 'desc'. The
- value of the expression given by 'desc' is compared against each
- 'tag' value, each of which should be different. If no 'tag' is
- matched, the field marked with 'default' is used if there is one,
- otherwise no field in the union will be marked.
-
- In the 'desc' option, the "current structure" is the union that it
- discriminates. Use '%1' to mean the structure containing it.
- There are no escapes available to the 'tag' option, since it is a
+ `tag' value, and then specifying a discriminator using `desc'.
+ The value of the expression given by `desc' is compared against
+ each `tag' value, each of which should be different. If no `tag'
+ is matched, the field marked with `default' is used if there is
+ one, otherwise no field in the union will be marked.
+
+ In the `desc' option, the "current structure" is the union that it
+ discriminates. Use `%1' to mean the structure containing it.
+ There are no escapes available to the `tag' option, since it is a
constant.
For example,
@@ -39143,47 +39592,43 @@ helpful when you have a complicated expression.
};
In this example, the value of BINDING_HAS_LEVEL_P when applied to a
- 'struct tree_binding *' is presumed to be 0 or 1. If 1, the type
- mechanism will treat the field 'level' as being present and if 0,
- will treat the field 'scope' as being present.
+ `struct tree_binding *' is presumed to be 0 or 1. If 1, the type
+ mechanism will treat the field `level' as being present and if 0,
+ will treat the field `scope' as being present.
- The 'desc' and 'tag' options can also be used for inheritance to
+ The `desc' and `tag' options can also be used for inheritance to
denote which subclass an instance is. See *note Inheritance and
GTY:: for more information.
-'cache'
-
- When the 'cache' option is applied to a global variable
+`cache'
+ When the `cache' option is applied to a global variable
gt_clear_cache is called on that variable between the mark and
- sweep phases of garbage collection. The gt_clear_cache function is
- free to mark blocks as used, or to clear pointers in the variable.
-
-'deletable'
+ sweep phases of garbage collection. The gt_clear_cache function
+ is free to mark blocks as used, or to clear pointers in the
+ variable.
- 'deletable', when applied to a global variable, indicates that when
+`deletable'
+ `deletable', when applied to a global variable, indicates that when
garbage collection runs, there's no need to mark anything pointed
- to by this variable, it can just be set to 'NULL' instead. This is
- used to keep a list of free structures around for re-use.
-
-'mark_hook ("HOOK-ROUTINE-NAME")'
+ to by this variable, it can just be set to `NULL' instead. This
+ is used to keep a list of free structures around for re-use.
+`mark_hook ("HOOK-ROUTINE-NAME")'
If provided for a structure or union type, the given
HOOK-ROUTINE-NAME (between double-quotes) is the name of a routine
called when the garbage collector has just marked the data as
- reachable. This routine should not change the data, or call any
- ggc routine. Its only argument is a pointer to the just marked
- (const) structure or union.
+ reachable. This routine should not change the data, or call any ggc
+ routine. Its only argument is a pointer to the just marked (const)
+ structure or union.
-'maybe_undef'
-
- When applied to a field, 'maybe_undef' indicates that it's OK if
+`maybe_undef'
+ When applied to a field, `maybe_undef' indicates that it's OK if
the structure that this fields points to is never defined, so long
- as this field is always 'NULL'. This is used to avoid requiring
+ as this field is always `NULL'. This is used to avoid requiring
backends to define certain optional structures. It doesn't work
with language frontends.
-'nested_ptr (TYPE, "TO EXPRESSION", "FROM EXPRESSION")'
-
+`nested_ptr (TYPE, "TO EXPRESSION", "FROM EXPRESSION")'
The type machinery expects all pointers to point to the start of an
object. Sometimes for abstraction purposes it's convenient to have
a pointer which points inside an object. So long as it's possible
@@ -39191,97 +39636,93 @@ helpful when you have a complicated expression.
pointers can still be used. TYPE is the type of the original
object, the TO EXPRESSION returns the pointer given the original
object, and the FROM EXPRESSION returns the original object given
- the pointer. The pointer will be available using the '%h' escape.
-
-'chain_next ("EXPRESSION")'
-'chain_prev ("EXPRESSION")'
-'chain_circular ("EXPRESSION")'
+ the pointer. The pointer will be available using the `%h' escape.
+`chain_next ("EXPRESSION")'
+`chain_prev ("EXPRESSION")'
+`chain_circular ("EXPRESSION")'
It's helpful for the type machinery to know if objects are often
chained together in long lists; this lets it generate code that
uses less stack space by iterating along the list instead of
- recursing down it. 'chain_next' is an expression for the next item
- in the list, 'chain_prev' is an expression for the previous item.
- For singly linked lists, use only 'chain_next'; for doubly linked
- lists, use both. The machinery requires that taking the next item
- of the previous item gives the original item. 'chain_circular' is
- similar to 'chain_next', but can be used for circular single linked
- lists.
-
-'reorder ("FUNCTION NAME")'
-
+ recursing down it. `chain_next' is an expression for the next
+ item in the list, `chain_prev' is an expression for the previous
+ item. For singly linked lists, use only `chain_next'; for doubly
+ linked lists, use both. The machinery requires that taking the
+ next item of the previous item gives the original item.
+ `chain_circular' is similar to `chain_next', but can be used for
+ circular single linked lists.
+
+`reorder ("FUNCTION NAME")'
Some data structures depend on the relative ordering of pointers.
If the precompiled header machinery needs to change that ordering,
- it will call the function referenced by the 'reorder' option,
- before changing the pointers in the object that's pointed to by the
- field the option applies to. The function must take four
+ it will call the function referenced by the `reorder' option,
+ before changing the pointers in the object that's pointed to by
+ the field the option applies to. The function must take four
arguments, with the signature
- 'void *, void *, gt_pointer_operator, void *'. The first parameter
- is a pointer to the structure that contains the object being
- updated, or the object itself if there is no containing structure.
- The second parameter is a cookie that should be ignored. The third
- parameter is a routine that, given a pointer, will update it to its
- correct new value. The fourth parameter is a cookie that must be
- passed to the second parameter.
+ `void *, void *, gt_pointer_operator, void *'. The first
+ parameter is a pointer to the structure that contains the object
+ being updated, or the object itself if there is no containing
+ structure. The second parameter is a cookie that should be
+ ignored. The third parameter is a routine that, given a pointer,
+ will update it to its correct new value. The fourth parameter is
+ a cookie that must be passed to the second parameter.
PCH cannot handle data structures that depend on the absolute
- values of pointers. 'reorder' functions can be expensive. When
- possible, it is better to depend on properties of the data, like an
- ID number or the hash of a string instead.
-
-'atomic'
-
- The 'atomic' option can only be used with pointers. It informs the
- GC machinery that the memory that the pointer points to does not
- contain any pointers, and hence it should be treated by the GC and
- PCH machinery as an "atomic" block of memory that does not need to
- be examined when scanning memory for pointers. In particular, the
- machinery will not scan that memory for pointers to mark them as
- reachable (when marking pointers for GC) or to relocate them (when
- writing a PCH file).
-
- The 'atomic' option differs from the 'skip' option. 'atomic' keeps
- the memory under Garbage Collection, but makes the GC ignore the
- contents of the memory. 'skip' is more drastic in that it causes
- the pointer and the memory to be completely ignored by the Garbage
- Collector. So, memory marked as 'atomic' is automatically freed
- when no longer reachable, while memory marked as 'skip' is not.
-
- The 'atomic' option must be used with great care, because all sorts
- of problem can occur if used incorrectly, that is, if the memory
- the pointer points to does actually contain a pointer.
+ values of pointers. `reorder' functions can be expensive. When
+ possible, it is better to depend on properties of the data, like
+ an ID number or the hash of a string instead.
+
+`atomic'
+ The `atomic' option can only be used with pointers. It informs
+ the GC machinery that the memory that the pointer points to does
+ not contain any pointers, and hence it should be treated by the GC
+ and PCH machinery as an "atomic" block of memory that does not
+ need to be examined when scanning memory for pointers. In
+ particular, the machinery will not scan that memory for pointers
+ to mark them as reachable (when marking pointers for GC) or to
+ relocate them (when writing a PCH file).
+
+ The `atomic' option differs from the `skip' option. `atomic'
+ keeps the memory under Garbage Collection, but makes the GC ignore
+ the contents of the memory. `skip' is more drastic in that it
+ causes the pointer and the memory to be completely ignored by the
+ Garbage Collector. So, memory marked as `atomic' is automatically
+ freed when no longer reachable, while memory marked as `skip' is
+ not.
+
+ The `atomic' option must be used with great care, because all
+ sorts of problem can occur if used incorrectly, that is, if the
+ memory the pointer points to does actually contain a pointer.
Here is an example of how to use it:
struct GTY(()) my_struct {
int number_of_elements;
unsigned int * GTY ((atomic)) elements;
};
- In this case, 'elements' is a pointer under GC, and the memory it
+ In this case, `elements' is a pointer under GC, and the memory it
points to needs to be allocated using the Garbage Collector, and
will be freed automatically by the Garbage Collector when it is no
- longer referenced. But the memory that the pointer points to is an
- array of 'unsigned int' elements, and the GC must not try to scan
- it to find pointers to mark or relocate, which is why it is marked
- with the 'atomic' option.
+ longer referenced. But the memory that the pointer points to is
+ an array of `unsigned int' elements, and the GC must not try to
+ scan it to find pointers to mark or relocate, which is why it is
+ marked with the `atomic' option.
Note that, currently, global variables can not be marked with
- 'atomic'; only fields of a struct can. This is a known limitation.
- It would be useful to be able to mark global pointers with 'atomic'
- to make the PCH machinery aware of them so that they are saved and
- restored correctly to PCH files.
-
-'special ("NAME")'
+ `atomic'; only fields of a struct can. This is a known
+ limitation. It would be useful to be able to mark global pointers
+ with `atomic' to make the PCH machinery aware of them so that they
+ are saved and restored correctly to PCH files.
- The 'special' option is used to mark types that have to be dealt
+`special ("NAME")'
+ The `special' option is used to mark types that have to be dealt
with by special case machinery. The parameter is the name of the
- special case. See 'gengtype.c' for further details. Avoid adding
+ special case. See `gengtype.c' for further details. Avoid adding
new special cases unless there is no other alternative.
-'user'
-
- The 'user' option indicates that the code to mark structure fields
- is completely handled by user-provided routines. See section *note
- User GC:: for details on what functions need to be provided.
+`user'
+ The `user' option indicates that the code to mark structure fields
+ is completely handled by user-provided routines. See section
+ *note User GC:: for details on what functions need to be provided.

File: gccint.info, Node: Inheritance and GTY, Next: User GC, Prev: GTY Options, Up: Type Information
@@ -39295,7 +39736,9 @@ this to have gengtype autogenerate marking routines, provided:
* There must be a concrete base class, with a discriminator
expression that can be used to identify which subclass an instance
is.
+
* Only single inheritance is used.
+
* None of the classes within the hierarchy are templates.
If your class hierarchy does not fit in this pattern, you must use
@@ -39305,7 +39748,7 @@ this to have gengtype autogenerate marking routines, provided:
"desc" option. Each concrete subclass must use the "tag" option to
identify which value of the discriminator it corresponds to.
- Every class in the hierarchy must have a 'GTY(())' marker, as gengtype
+ Every class in the hierarchy must have a `GTY(())' marker, as gengtype
will only attempt to parse classes that have such a marker (1).
class GTY((desc("%h.kind"), tag("0"))) example_base
@@ -39327,14 +39770,14 @@ will only attempt to parse classes that have such a marker (1).
tree c;
};
- The generated marking routines for the above will contain a "switch" on
-"kind", visiting all appropriate fields. For example, if kind is 2, it
-will cast to "some_other_subclass" and visit fields a, b, and c.
+ The generated marking routines for the above will contain a "switch"
+on "kind", visiting all appropriate fields. For example, if kind is 2,
+it will cast to "some_other_subclass" and visit fields a, b, and c.
- ---------- Footnotes ----------
+ ---------- Footnotes ----------
- (1) Classes lacking such a marker will not be identified as being
-part of the hierarchy, and so the marking routines will not handle them,
+ (1) Classes lacking such a marker will not be identified as being part
+of the hierarchy, and so the marking routines will not handle them,
leading to a assertion failure within the marking routines due to an
unknown tag value (assuming that assertions are enabled).
@@ -39344,13 +39787,13 @@ File: gccint.info, Node: User GC, Next: GGC Roots, Prev: Inheritance and GTY,
22.3 Support for user-provided GC marking routines
==================================================
-The garbage collector supports types for which no automatic marking code
-is generated. For these types, the user is required to provide three
-functions: one to act as a marker for garbage collection, and two
+The garbage collector supports types for which no automatic marking
+code is generated. For these types, the user is required to provide
+three functions: one to act as a marker for garbage collection, and two
functions to act as marker and pointer walker for pre-compiled headers.
- Given a structure 'struct GTY((user)) my_struct', the following
-functions should be defined to mark 'my_struct':
+ Given a structure `struct GTY((user)) my_struct', the following
+functions should be defined to mark `my_struct':
void gt_ggc_mx (my_struct *p)
{
@@ -39370,28 +39813,30 @@ functions should be defined to mark 'my_struct':
op (&(tp->fld), cookie);
}
- In general, each marker 'M' should call 'M' for every pointer field in
+ In general, each marker `M' should call `M' for every pointer field in
the structure. Fields that are not allocated in GC or are not pointers
must be ignored.
- For embedded lists (e.g., structures with a 'next' or 'prev' pointer),
+ For embedded lists (e.g., structures with a `next' or `prev' pointer),
the marker must follow the chain and mark every element in it.
- Note that the rules for the pointer walker 'gt_pch_nx (my_struct *,
-gt_pointer_operator, void *)' are slightly different. In this case, the
-operation 'op' must be applied to the _address_ of every pointer field.
+ Note that the rules for the pointer walker `gt_pch_nx (my_struct *,
+gt_pointer_operator, void *)' are slightly different. In this case,
+the operation `op' must be applied to the _address_ of every pointer
+field.
22.3.1 User-provided marking routines for template types
--------------------------------------------------------
-When a template type 'TP' is marked with 'GTY', all instances of that
-type are considered user-provided types. This means that the individual
-instances of 'TP' do not need to be marked with 'GTY'. The user needs
-to provide template functions to mark all the fields of the type.
+When a template type `TP' is marked with `GTY', all instances of that
+type are considered user-provided types. This means that the
+individual instances of `TP' do not need to be marked with `GTY'. The
+user needs to provide template functions to mark all the fields of the
+type.
- The following code snippets represent all the functions that need to be
-provided. Note that type 'TP' may reference to more than one type. In
-these snippets, there is only one type 'T', but there could be more.
+ The following code snippets represent all the functions that need to
+be provided. Note that type `TP' may reference to more than one type.
+In these snippets, there is only one type `T', but there could be more.
template<typename T>
void gt_ggc_mx (TP<T> *tp)
@@ -39429,18 +39874,18 @@ these snippets, there is only one type 'T', but there could be more.
gt_pch_nx (&(tp->fld), op, cookie);
}
- Support for user-defined types is currently limited. The following
+ Support for user-defined types is currently limited. The following
restrictions apply:
- 1. Type 'TP' and all the argument types 'T' must be marked with 'GTY'.
+ 1. Type `TP' and all the argument types `T' must be marked with `GTY'.
- 2. Type 'TP' can only have type names in its argument list.
+ 2. Type `TP' can only have type names in its argument list.
- 3. The pointer walker functions are different for 'TP<T>' and 'TP<T
- *>'. In the case of 'TP<T>', references to 'T' must be handled by
- calling 'gt_pch_nx' (which will, in turn, walk all the pointers
- inside fields of 'T'). In the case of 'TP<T *>', references to 'T
- *' must be handled by calling the 'op' function on the address of
+ 3. The pointer walker functions are different for `TP<T>' and `TP<T
+ *>'. In the case of `TP<T>', references to `T' must be handled by
+ calling `gt_pch_nx' (which will, in turn, walk all the pointers
+ inside fields of `T'). In the case of `TP<T *>', references to `T
+ *' must be handled by calling the `op' function on the address of
the pointer (see the code snippets above).

@@ -39453,13 +39898,14 @@ In addition to keeping track of types, the type machinery also locates
the global variables ("roots") that the garbage collector starts at.
Roots must be declared using one of the following syntaxes:
- * 'extern GTY(([OPTIONS])) TYPE NAME;'
- * 'static GTY(([OPTIONS])) TYPE NAME;'
-The syntax
- * 'GTY(([OPTIONS])) TYPE NAME;'
-is _not_ accepted. There should be an 'extern' declaration of such a
+ * `extern GTY(([OPTIONS])) TYPE NAME;'
+
+ * `static GTY(([OPTIONS])) TYPE NAME;'
+ The syntax
+ * `GTY(([OPTIONS])) TYPE NAME;'
+ is _not_ accepted. There should be an `extern' declaration of such a
variable in a header somewhere--mark that, not the definition. Or, if
-the variable is only used in one file, make it 'static'.
+the variable is only used in one file, make it `static'.

File: gccint.info, Node: Files, Next: Invoking the garbage collector, Prev: GGC Roots, Up: Type Information
@@ -39467,55 +39913,57 @@ File: gccint.info, Node: Files, Next: Invoking the garbage collector, Prev: G
22.5 Source Files Containing Type Information
=============================================
-Whenever you add 'GTY' markers to a source file that previously had
-none, or create a new source file containing 'GTY' markers, there are
+Whenever you add `GTY' markers to a source file that previously had
+none, or create a new source file containing `GTY' markers, there are
three things you need to do:
1. You need to add the file to the list of source files the type
machinery scans. There are four cases:
a. For a back-end file, this is usually done automatically; if
- not, you should add it to 'target_gtfiles' in the appropriate
- port's entries in 'config.gcc'.
+ not, you should add it to `target_gtfiles' in the appropriate
+ port's entries in `config.gcc'.
b. For files shared by all front ends, add the filename to the
- 'GTFILES' variable in 'Makefile.in'.
+ `GTFILES' variable in `Makefile.in'.
c. For files that are part of one front end, add the filename to
- the 'gtfiles' variable defined in the appropriate
- 'config-lang.in'. Headers should appear before non-headers in
- this list.
+ the `gtfiles' variable defined in the appropriate
+ `config-lang.in'. Headers should appear before non-headers
+ in this list.
d. For files that are part of some but not all front ends, add
- the filename to the 'gtfiles' variable of _all_ the front ends
+ the filename to the `gtfiles' variable of _all_ the front ends
that use it.
2. If the file was a header file, you'll need to check that it's
included in the right place to be visible to the generated files.
- For a back-end header file, this should be done automatically. For
- a front-end header file, it needs to be included by the same file
- that includes 'gtype-LANG.h'. For other header files, it needs to
- be included in 'gtype-desc.c', which is a generated file, so add it
- to 'ifiles' in 'open_base_file' in 'gengtype.c'.
+ For a back-end header file, this should be done automatically.
+ For a front-end header file, it needs to be included by the same
+ file that includes `gtype-LANG.h'. For other header files, it
+ needs to be included in `gtype-desc.c', which is a generated file,
+ so add it to `ifiles' in `open_base_file' in `gengtype.c'.
For source files that aren't header files, the machinery will
generate a header file that should be included in the source file
- you just changed. The file will be called 'gt-PATH.h' where PATH
- is the pathname relative to the 'gcc' directory with slashes
+ you just changed. The file will be called `gt-PATH.h' where PATH
+ is the pathname relative to the `gcc' directory with slashes
replaced by -, so for example the header file to be included in
- 'cp/parser.c' is called 'gt-cp-parser.c'. The generated header
+ `cp/parser.c' is called `gt-cp-parser.c'. The generated header
file should be included after everything else in the source file.
Don't forget to mention this file as a dependency in the
- 'Makefile'!
+ `Makefile'!
+
For language frontends, there is another file that needs to be included
-somewhere. It will be called 'gtype-LANG.h', where LANG is the name of
+somewhere. It will be called `gtype-LANG.h', where LANG is the name of
the subdirectory the language is contained in.
- Plugins can add additional root tables. Run the 'gengtype' utility in
-plugin mode as 'gengtype -P pluginout.h SOURCE-DIR FILE-LIST PLUGIN*.C'
-with your plugin files PLUGIN*.C using 'GTY' to generate the PLUGINOUT.H
-file. The GCC build tree is needed to be present in that mode.
+ Plugins can add additional root tables. Run the `gengtype' utility in
+plugin mode as `gengtype -P pluginout.h SOURCE-DIR FILE-LIST PLUGIN*.C'
+with your plugin files PLUGIN*.C using `GTY' to generate the
+PLUGINOUT.H file. The GCC build tree is needed to be present in that
+mode.

File: gccint.info, Node: Invoking the garbage collector, Next: Troubleshooting, Prev: Files, Up: Type Information
@@ -39523,22 +39971,22 @@ File: gccint.info, Node: Invoking the garbage collector, Next: Troubleshooting
22.6 How to invoke the garbage collector
========================================
-The GCC garbage collector GGC is only invoked explicitly. In contrast
+The GCC garbage collector GGC is only invoked explicitly. In contrast
with many other garbage collectors, it is not implicitly invoked by
-allocation routines when a lot of memory has been consumed. So the only
-way to have GGC reclaim storage is to call the 'ggc_collect' function
-explicitly. This call is an expensive operation, as it may have to scan
-the entire heap. Beware that local variables (on the GCC call stack)
-are not followed by such an invocation (as many other garbage collectors
-do): you should reference all your data from static or external 'GTY'-ed
-variables, and it is advised to call 'ggc_collect' with a shallow call
-stack. The GGC is an exact mark and sweep garbage collector (so it does
-not scan the call stack for pointers). In practice GCC passes don't
-often call 'ggc_collect' themselves, because it is called by the pass
-manager between passes.
-
- At the time of the 'ggc_collect' call all pointers in the GC-marked
-structures must be valid or 'NULL'. In practice this means that there
+allocation routines when a lot of memory has been consumed. So the only
+way to have GGC reclaim storage is to call the `ggc_collect' function
+explicitly. This call is an expensive operation, as it may have to
+scan the entire heap. Beware that local variables (on the GCC call
+stack) are not followed by such an invocation (as many other garbage
+collectors do): you should reference all your data from static or
+external `GTY'-ed variables, and it is advised to call `ggc_collect'
+with a shallow call stack. The GGC is an exact mark and sweep garbage
+collector (so it does not scan the call stack for pointers). In
+practice GCC passes don't often call `ggc_collect' themselves, because
+it is called by the pass manager between passes.
+
+ At the time of the `ggc_collect' call all pointers in the GC-marked
+structures must be valid or `NULL'. In practice this means that there
should not be uninitialized pointer fields in the structures even if
your code never reads or writes those fields at a particular instance.
One way to ensure this is to use cleared versions of allocators unless
@@ -39554,18 +40002,19 @@ With the current garbage collector implementation, most issues should
show up as GCC compilation errors. Some of the most commonly
encountered issues are described below.
- * Gengtype does not produce allocators for a 'GTY'-marked type.
+ * Gengtype does not produce allocators for a `GTY'-marked type.
Gengtype checks if there is at least one possible path from GC
roots to at least one instance of each type before outputting
- allocators. If there is no such path, the 'GTY' markers will be
+ allocators. If there is no such path, the `GTY' markers will be
ignored and no allocators will be output. Solve this by making
sure that there exists at least one such path. If creating it is
unfeasible or raises a "code smell", consider if you really must
use GC for allocating such type.
- * Link-time errors about undefined 'gt_ggc_r_foo_bar' and
- similarly-named symbols. Check if your 'foo_bar' source file has
- '#include "gt-foo_bar.h"' as its very last line.
+ * Link-time errors about undefined `gt_ggc_r_foo_bar' and
+ similarly-named symbols. Check if your `foo_bar' source file has
+ `#include "gt-foo_bar.h"' as its very last line.
+

File: gccint.info, Node: Plugins, Next: LTO, Prev: Type Information, Up: Top
@@ -39601,23 +40050,23 @@ File: gccint.info, Node: Plugins loading, Next: Plugin API, Up: Plugins
23.1 Loading Plugins
====================
-Plugins are supported on platforms that support '-ldl -rdynamic'. They
-are loaded by the compiler using 'dlopen' and invoked at pre-determined
+Plugins are supported on platforms that support `-ldl -rdynamic'. They
+are loaded by the compiler using `dlopen' and invoked at pre-determined
locations in the compilation process.
Plugins are loaded with
- '-fplugin=/path/to/NAME.so' '-fplugin-arg-NAME-KEY1[=VALUE1]'
+ `-fplugin=/path/to/NAME.so' `-fplugin-arg-NAME-KEY1[=VALUE1]'
- The plugin arguments are parsed by GCC and passed to respective plugins
-as key-value pairs. Multiple plugins can be invoked by specifying
-multiple '-fplugin' arguments.
+ The plugin arguments are parsed by GCC and passed to respective
+plugins as key-value pairs. Multiple plugins can be invoked by
+specifying multiple `-fplugin' arguments.
A plugin can be simply given by its short name (no dots or slashes).
-When simply passing '-fplugin=NAME', the plugin is loaded from the
-'plugin' directory, so '-fplugin=NAME' is the same as '-fplugin=`gcc
--print-file-name=plugin`/NAME.so', using backquote shell syntax to query
-the 'plugin' directory.
+When simply passing `-fplugin=NAME', the plugin is loaded from the
+`plugin' directory, so `-fplugin=NAME' is the same as `-fplugin=`gcc
+-print-file-name=plugin`/NAME.so', using backquote shell syntax to
+query the `plugin' directory.

File: gccint.info, Node: Plugin API, Next: Plugins pass, Prev: Plugins loading, Up: Plugins
@@ -39626,16 +40075,16 @@ File: gccint.info, Node: Plugin API, Next: Plugins pass, Prev: Plugins loadin
===============
Plugins are activated by the compiler at specific events as defined in
-'gcc-plugin.h'. For each event of interest, the plugin should call
-'register_callback' specifying the name of the event and address of the
+`gcc-plugin.h'. For each event of interest, the plugin should call
+`register_callback' specifying the name of the event and address of the
callback function that will handle that event.
- The header 'gcc-plugin.h' must be the first gcc header to be included.
+ The header `gcc-plugin.h' must be the first gcc header to be included.
23.2.1 Plugin license check
---------------------------
-Every plugin should define the global symbol 'plugin_is_GPL_compatible'
+Every plugin should define the global symbol `plugin_is_GPL_compatible'
to assert that it has been licensed under a GPL-compatible license. If
this symbol does not exist, the compiler will emit a fatal error and
exit with the error message:
@@ -39645,28 +40094,29 @@ exit with the error message:
compilation terminated
The declared type of the symbol should be int, to match a forward
-declaration in 'gcc-plugin.h' that suppresses C++ mangling. It does not
-need to be in any allocated section, though. The compiler merely
-asserts that the symbol exists in the global scope. Something like this
-is enough:
+declaration in `gcc-plugin.h' that suppresses C++ mangling. It does
+not need to be in any allocated section, though. The compiler merely
+asserts that the symbol exists in the global scope. Something like
+this is enough:
int plugin_is_GPL_compatible;
23.2.2 Plugin initialization
----------------------------
-Every plugin should export a function called 'plugin_init' that is
-called right after the plugin is loaded. This function is responsible
+Every plugin should export a function called `plugin_init' that is
+called right after the plugin is loaded. This function is responsible
for registering all the callbacks required by the plugin and do any
other required initialization.
- This function is called from 'compile_file' right before invoking the
-parser. The arguments to 'plugin_init' are:
+ This function is called from `compile_file' right before invoking the
+parser. The arguments to `plugin_init' are:
+
+ * `plugin_info': Plugin invocation information.
- * 'plugin_info': Plugin invocation information.
- * 'version': GCC version.
+ * `version': GCC version.
- The 'plugin_info' struct is defined as follows:
+ The `plugin_info' struct is defined as follows:
struct plugin_name_args
{
@@ -39681,7 +40131,7 @@ parser. The arguments to 'plugin_init' are:
const char *help; /* Help string provided by plugin. */
}
- If initialization fails, 'plugin_init' must return a non-zero value.
+ If initialization fails, `plugin_init' must return a non-zero value.
Otherwise, it should return 0.
The version of the GCC compiler loading the plugin is described by the
@@ -39696,12 +40146,12 @@ following structure:
const char *configuration_arguments;
};
- The function 'plugin_default_version_check' takes two pointers to such
-structure and compare them field by field. It can be used by the
-plugin's 'plugin_init' function.
+ The function `plugin_default_version_check' takes two pointers to such
+structure and compare them field by field. It can be used by the
+plugin's `plugin_init' function.
The version of GCC used to compile the plugin can be found in the
-symbol 'gcc_version' defined in the header 'plugin-version.h'. The
+symbol `gcc_version' defined in the header `plugin-version.h'. The
recommended version check to perform looks like
#include "plugin-version.h"
@@ -39778,31 +40228,34 @@ Callback functions have the following prototype:
In addition, plugins can also look up the enumerator of a named event,
and / or generate new events dynamically, by calling the function
-'get_named_event_id'.
+`get_named_event_id'.
- To register a callback, the plugin calls 'register_callback' with the
+ To register a callback, the plugin calls `register_callback' with the
arguments:
- * 'char *name': Plugin name.
- * 'int event': The event code.
- * 'plugin_callback_func callback': The function that handles 'event'.
- * 'void *user_data': Pointer to plugin-specific data.
+ * `char *name': Plugin name.
+
+ * `int event': The event code.
+
+ * `plugin_callback_func callback': The function that handles `event'.
+
+ * `void *user_data': Pointer to plugin-specific data.
For the PLUGIN_PASS_MANAGER_SETUP, PLUGIN_INFO, and
-PLUGIN_REGISTER_GGC_ROOTS pseudo-events the 'callback' should be null,
-and the 'user_data' is specific.
+PLUGIN_REGISTER_GGC_ROOTS pseudo-events the `callback' should be null,
+and the `user_data' is specific.
- When the PLUGIN_PRAGMAS event is triggered (with a null pointer as data
-from GCC), plugins may register their own pragmas. Notice that pragmas
-are not available from 'lto1', so plugins used with '-flto' option to
-GCC during link-time optimization cannot use pragmas and do not even see
-functions like 'c_register_pragma' or 'pragma_lex'.
+ When the PLUGIN_PRAGMAS event is triggered (with a null pointer as
+data from GCC), plugins may register their own pragmas. Notice that
+pragmas are not available from `lto1', so plugins used with `-flto'
+option to GCC during link-time optimization cannot use pragmas and do
+not even see functions like `c_register_pragma' or `pragma_lex'.
- The PLUGIN_INCLUDE_FILE event, with a 'const char*' file path as GCC
-data, is triggered for processing of '#include' or '#line' directives.
+ The PLUGIN_INCLUDE_FILE event, with a `const char*' file path as GCC
+data, is triggered for processing of `#include' or `#line' directives.
The PLUGIN_FINISH event is the last time that plugins can call GCC
-functions, notably emit diagnostics with 'warning', 'error' etc.
+functions, notably emit diagnostics with `warning', `error' etc.

File: gccint.info, Node: Plugins pass, Next: Plugins GC, Prev: Plugin API, Up: Plugins
@@ -39810,14 +40263,14 @@ File: gccint.info, Node: Plugins pass, Next: Plugins GC, Prev: Plugin API, U
23.3 Interacting with the pass manager
======================================
-There needs to be a way to add/reorder/remove passes dynamically. This
+There needs to be a way to add/reorder/remove passes dynamically. This
is useful for both analysis plugins (plugging in after a certain pass
such as CFG or an IPA pass) and optimization plugins.
Basic support for inserting new passes or replacing existing passes is
-provided. A plugin registers a new pass with GCC by calling
-'register_callback' with the 'PLUGIN_PASS_MANAGER_SETUP' event and a
-pointer to a 'struct register_pass_info' object defined as follows
+provided. A plugin registers a new pass with GCC by calling
+`register_callback' with the `PLUGIN_PASS_MANAGER_SETUP' event and a
+pointer to a `struct register_pass_info' object defined as follows
enum pass_positioning_ops
{
@@ -39864,32 +40317,32 @@ File: gccint.info, Node: Plugins GC, Next: Plugins description, Prev: Plugins
===============================================
Some plugins may want to be informed when GGC (the GCC Garbage
-Collector) is running. They can register callbacks for the
-'PLUGIN_GGC_START' and 'PLUGIN_GGC_END' events (for which the callback
-is called with a null 'gcc_data') to be notified of the start or end of
+Collector) is running. They can register callbacks for the
+`PLUGIN_GGC_START' and `PLUGIN_GGC_END' events (for which the callback
+is called with a null `gcc_data') to be notified of the start or end of
the GCC garbage collection.
- Some plugins may need to have GGC mark additional data. This can be
-done by registering a callback (called with a null 'gcc_data') for the
-'PLUGIN_GGC_MARKING' event. Such callbacks can call the 'ggc_set_mark'
-routine, preferably through the 'ggc_mark' macro (and conversely, these
+ Some plugins may need to have GGC mark additional data. This can be
+done by registering a callback (called with a null `gcc_data') for the
+`PLUGIN_GGC_MARKING' event. Such callbacks can call the `ggc_set_mark'
+routine, preferably through the `ggc_mark' macro (and conversely, these
routines should usually not be used in plugins outside of the
-'PLUGIN_GGC_MARKING' event). Plugins that wish to hold weak references
+`PLUGIN_GGC_MARKING' event). Plugins that wish to hold weak references
to gc data may also use this event to drop weak references when the
-object is about to be collected. The 'ggc_marked_p' function can be
-used to tell if an object is marked, or is about to be collected. The
-'gt_clear_cache' overloads which some types define may also be of use in
+object is about to be collected. The `ggc_marked_p' function can be
+used to tell if an object is marked, or is about to be collected. The
+`gt_clear_cache' overloads which some types define may also be of use in
managing weak references.
- Some plugins may need to add extra GGC root tables, e.g. to handle
-their own 'GTY'-ed data. This can be done with the
-'PLUGIN_REGISTER_GGC_ROOTS' pseudo-event with a null callback and the
-extra root table (of type 'struct ggc_root_tab*') as 'user_data'.
-Running the 'gengtype -p SOURCE-DIR FILE-LIST PLUGIN*.C ...' utility
+ Some plugins may need to add extra GGC root tables, e.g. to handle
+their own `GTY'-ed data. This can be done with the
+`PLUGIN_REGISTER_GGC_ROOTS' pseudo-event with a null callback and the
+extra root table (of type `struct ggc_root_tab*') as `user_data'.
+Running the `gengtype -p SOURCE-DIR FILE-LIST PLUGIN*.C ...' utility
generates these extra root tables.
You should understand the details of memory management inside GCC
-before using 'PLUGIN_GGC_MARKING' or 'PLUGIN_REGISTER_GGC_ROOTS'.
+before using `PLUGIN_GGC_MARKING' or `PLUGIN_REGISTER_GGC_ROOTS'.

File: gccint.info, Node: Plugins description, Next: Plugins attr, Prev: Plugins GC, Up: Plugins
@@ -39897,7 +40350,7 @@ File: gccint.info, Node: Plugins description, Next: Plugins attr, Prev: Plugi
23.5 Giving information about a plugin
======================================
-A plugin should give some information to the user about itself. This
+A plugin should give some information to the user about itself. This
uses the following structure:
struct plugin_info
@@ -39906,8 +40359,8 @@ uses the following structure:
const char *help;
};
- Such a structure is passed as the 'user_data' by the plugin's init
-routine using 'register_callback' with the 'PLUGIN_INFO' pseudo-event
+ Such a structure is passed as the `user_data' by the plugin's init
+routine using `register_callback' with the `PLUGIN_INFO' pseudo-event
and a null callback.

@@ -39919,8 +40372,8 @@ File: gccint.info, Node: Plugins attr, Next: Plugins recording, Prev: Plugins
For analysis (or other) purposes it is useful to be able to add custom
attributes or pragmas.
- The 'PLUGIN_ATTRIBUTES' callback is called during attribute
-registration. Use the 'register_attribute' function to register custom
+ The `PLUGIN_ATTRIBUTES' callback is called during attribute
+registration. Use the `register_attribute' function to register custom
attributes.
/* Attribute handler callback */
@@ -39945,13 +40398,12 @@ attributes.
register_attribute (&user_attr);
}
-
- The PLUGIN_PRAGMAS callback is called once during pragmas registration.
-Use the 'c_register_pragma', 'c_register_pragma_with_data',
-'c_register_pragma_with_expansion',
-'c_register_pragma_with_expansion_and_data' functions to register custom
-pragmas and their handlers (which often want to call 'pragma_lex') from
-'c-family/c-pragma.h'.
+ The PLUGIN_PRAGMAS callback is called once during pragmas
+registration. Use the `c_register_pragma',
+`c_register_pragma_with_data', `c_register_pragma_with_expansion',
+`c_register_pragma_with_expansion_and_data' functions to register
+custom pragmas and their handlers (which often want to call
+`pragma_lex') from `c-family/c-pragma.h'.
/* Plugin callback called during pragmas registration. Registered with
register_callback (plugin_name, PLUGIN_PRAGMAS,
@@ -39964,12 +40416,12 @@ pragmas and their handlers (which often want to call 'pragma_lex') from
c_register_pragma ("GCCPLUGIN", "sayhello", handle_pragma_sayhello);
}
- It is suggested to pass '"GCCPLUGIN"' (or a short name identifying your
-plugin) as the "space" argument of your pragma.
+ It is suggested to pass `"GCCPLUGIN"' (or a short name identifying
+your plugin) as the "space" argument of your pragma.
- Pragmas registered with 'c_register_pragma_with_expansion' or
-'c_register_pragma_with_expansion_and_data' support preprocessor
-expansions. For example:
+ Pragmas registered with `c_register_pragma_with_expansion' or
+`c_register_pragma_with_expansion_and_data' support preprocessor
+expansions. For example:
#define NUMBER 10
#pragma GCCPLUGIN foothreshold (NUMBER)
@@ -39981,14 +40433,14 @@ File: gccint.info, Node: Plugins recording, Next: Plugins gate, Prev: Plugins
===============================================
The event PLUGIN_PASS_EXECUTION passes the pointer to the executed pass
-(the same as current_pass) as 'gcc_data' to the callback. You can also
+(the same as current_pass) as `gcc_data' to the callback. You can also
inspect cfun to find out about which function this pass is executed for.
Note that this event will only be invoked if the gate check (if
applicable, modified by PLUGIN_OVERRIDE_GATE) succeeds. You can use
-other hooks, like 'PLUGIN_ALL_PASSES_START', 'PLUGIN_ALL_PASSES_END',
-'PLUGIN_ALL_IPA_PASSES_START', 'PLUGIN_ALL_IPA_PASSES_END',
-'PLUGIN_EARLY_GIMPLE_PASSES_START', and/or
-'PLUGIN_EARLY_GIMPLE_PASSES_END' to manipulate global state in your
+other hooks, like `PLUGIN_ALL_PASSES_START', `PLUGIN_ALL_PASSES_END',
+`PLUGIN_ALL_IPA_PASSES_START', `PLUGIN_ALL_IPA_PASSES_END',
+`PLUGIN_EARLY_GIMPLE_PASSES_START', and/or
+`PLUGIN_EARLY_GIMPLE_PASSES_END' to manipulate global state in your
plugin(s) in order to get context for the pass execution.

@@ -39999,8 +40451,8 @@ File: gccint.info, Node: Plugins gate, Next: Plugins tracking, Prev: Plugins
After the original gate function for a pass is called, its result - the
gate status - is stored as an integer. Then the event
-'PLUGIN_OVERRIDE_GATE' is invoked, with a pointer to the gate status in
-the 'gcc_data' parameter to the callback function. A nonzero value of
+`PLUGIN_OVERRIDE_GATE' is invoked, with a pointer to the gate status in
+the `gcc_data' parameter to the callback function. A nonzero value of
the gate status means that the pass is to be executed. You can both
read and write the gate status via the passed pointer.
@@ -40013,9 +40465,9 @@ File: gccint.info, Node: Plugins tracking, Next: Plugins building, Prev: Plug
When your plugin is loaded, you can inspect the various pass lists to
determine what passes are available. However, other plugins might add
new passes. Also, future changes to GCC might cause generic passes to
-be added after plugin loading. When a pass is first added to one of the
-pass lists, the event 'PLUGIN_NEW_PASS' is invoked, with the callback
-parameter 'gcc_data' pointing to the new pass.
+be added after plugin loading. When a pass is first added to one of
+the pass lists, the event `PLUGIN_NEW_PASS' is invoked, with the
+callback parameter `gcc_data' pointing to the new pass.

File: gccint.info, Node: Plugins building, Prev: Plugins tracking, Up: Plugins
@@ -40024,22 +40476,22 @@ File: gccint.info, Node: Plugins building, Prev: Plugins tracking, Up: Plugin
==========================
If plugins are enabled, GCC installs the headers needed to build a
-plugin (somewhere in the installation tree, e.g. under '/usr/local').
-In particular a 'plugin/include' directory is installed, containing all
+plugin (somewhere in the installation tree, e.g. under `/usr/local').
+In particular a `plugin/include' directory is installed, containing all
the header files needed to build plugins.
- On most systems, you can query this 'plugin' directory by invoking 'gcc
--print-file-name=plugin' (replace if needed 'gcc' with the appropriate
-program path).
+ On most systems, you can query this `plugin' directory by invoking
+`gcc -print-file-name=plugin' (replace if needed `gcc' with the
+appropriate program path).
- Inside plugins, this 'plugin' directory name can be queried by calling
-'default_plugin_dir_name ()'.
+ Inside plugins, this `plugin' directory name can be queried by calling
+`default_plugin_dir_name ()'.
Plugins may know, when they are compiled, the GCC version for which
-'plugin-version.h' is provided. The constant macros
-'GCCPLUGIN_VERSION_MAJOR', 'GCCPLUGIN_VERSION_MINOR',
-'GCCPLUGIN_VERSION_PATCHLEVEL', 'GCCPLUGIN_VERSION' are integer numbers,
-so a plugin could ensure it is built for GCC 4.7 with
+`plugin-version.h' is provided. The constant macros
+`GCCPLUGIN_VERSION_MAJOR', `GCCPLUGIN_VERSION_MINOR',
+`GCCPLUGIN_VERSION_PATCHLEVEL', `GCCPLUGIN_VERSION' are integer
+numbers, so a plugin could ensure it is built for GCC 4.7 with
#if GCCPLUGIN_VERSION != 4007
#error this GCC plugin is for GCC 4.7
#endif
@@ -40055,14 +40507,14 @@ so a plugin could ensure it is built for GCC 4.7 with
plugin.so: $(PLUGIN_SOURCE_FILES)
$(HOST_GCC) -shared $(CXXFLAGS) $^ -o $@
- A single source file plugin may be built with 'g++ -I`gcc
+ A single source file plugin may be built with `g++ -I`gcc
-print-file-name=plugin`/include -fPIC -shared -fno-rtti -O2 plugin.c -o
-plugin.so', using backquote shell syntax to query the 'plugin'
+plugin.so', using backquote shell syntax to query the `plugin'
directory.
- When a plugin needs to use 'gengtype', be sure that both 'gengtype' and
-'gtype.state' have the same version as the GCC for which the plugin is
-built.
+ When a plugin needs to use `gengtype', be sure that both `gengtype'
+and `gtype.state' have the same version as the GCC for which the plugin
+is built.

File: gccint.info, Node: LTO, Next: Match and Simplify, Prev: Plugins, Up: Top
@@ -40072,10 +40524,10 @@ File: gccint.info, Node: LTO, Next: Match and Simplify, Prev: Plugins, Up: T
Link Time Optimization (LTO) gives GCC the capability of dumping its
internal representation (GIMPLE) to disk, so that all the different
-compilation units that make up a single executable can be optimized as a
-single module. This expands the scope of inter-procedural optimizations
-to encompass the whole program (or, rather, everything that is visible
-at link time).
+compilation units that make up a single executable can be optimized as
+a single module. This expands the scope of inter-procedural
+optimizations to encompass the whole program (or, rather, everything
+that is visible at link time).
* Menu:
@@ -40084,7 +40536,7 @@ at link time).
* IPA:: Using summary information in IPA passes.
* WHOPR:: Whole program assumptions,
linker plugin and symbol visibilities.
-* Internal flags:: Internal flags controlling 'lto1'.
+* Internal flags:: Internal flags controlling `lto1'.

File: gccint.info, Node: LTO Overview, Next: LTO object file layout, Up: LTO
@@ -40093,7 +40545,7 @@ File: gccint.info, Node: LTO Overview, Next: LTO object file layout, Up: LTO
====================
Link time optimization is implemented as a GCC front end for a bytecode
-representation of GIMPLE that is emitted in special sections of '.o'
+representation of GIMPLE that is emitted in special sections of `.o'
files. Currently, LTO support is enabled in most ELF-based systems, as
well as darwin, cygwin and mingw systems.
@@ -40105,16 +40557,16 @@ Additionally, one might be able to ship one set of fat objects which
could be used both for development and the production of optimized
builds. A, perhaps surprising, side effect of this feature is that any
mistake in the toolchain that leads to LTO information not being used
-(e.g. an older 'libtool' calling 'ld' directly). This is both an
-advantage, as the system is more robust, and a disadvantage, as the user
-is not informed that the optimization has been disabled.
+(e.g. an older `libtool' calling `ld' directly). This is both an
+advantage, as the system is more robust, and a disadvantage, as the
+user is not informed that the optimization has been disabled.
The current implementation only produces "fat" objects, effectively
doubling compilation time and increasing file sizes up to 5x the
-original size. This hides the problem that some tools, such as 'ar' and
-'nm', need to understand symbol tables of LTO sections. These tools
-were extended to use the plugin infrastructure, and with these problems
-solved, GCC will also support "slim" objects consisting of the
+original size. This hides the problem that some tools, such as `ar'
+and `nm', need to understand symbol tables of LTO sections. These
+tools were extended to use the plugin infrastructure, and with these
+problems solved, GCC will also support "slim" objects consisting of the
intermediate code alone.
At the highest level, LTO splits the compiler in two. The first half
@@ -40123,48 +40575,48 @@ data structures needed to optimize and generate code. This includes
declarations, types, the callgraph and the GIMPLE representation of
function bodies.
- When '-flto' is given during compilation of a source file, the pass
-manager executes all the passes in 'all_lto_gen_passes'. Currently,
+ When `-flto' is given during compilation of a source file, the pass
+manager executes all the passes in `all_lto_gen_passes'. Currently,
this phase is composed of two IPA passes:
- * 'pass_ipa_lto_gimple_out' This pass executes the function
- 'lto_output' in 'lto-streamer-out.c', which traverses the call
+ * `pass_ipa_lto_gimple_out' This pass executes the function
+ `lto_output' in `lto-streamer-out.c', which traverses the call
graph encoding every reachable declaration, type and function.
This generates a memory representation of all the file sections
described below.
- * 'pass_ipa_lto_finish_out' This pass executes the function
- 'produce_asm_for_decls' in 'lto-streamer-out.c', which takes the
+ * `pass_ipa_lto_finish_out' This pass executes the function
+ `produce_asm_for_decls' in `lto-streamer-out.c', which takes the
memory image built in the previous pass and encodes it in the
corresponding ELF file sections.
- The second half of LTO support is the "reader". This is implemented as
-the GCC front end 'lto1' in 'lto/lto.c'. When 'collect2' detects a link
-set of '.o'/'.a' files with LTO information and the '-flto' is enabled,
-it invokes 'lto1' which reads the set of files and aggregates them into
-a single translation unit for optimization. The main entry point for
-the reader is 'lto/lto.c':'lto_main'.
+ The second half of LTO support is the "reader". This is implemented
+as the GCC front end `lto1' in `lto/lto.c'. When `collect2' detects a
+link set of `.o'/`.a' files with LTO information and the `-flto' is
+enabled, it invokes `lto1' which reads the set of files and aggregates
+them into a single translation unit for optimization. The main entry
+point for the reader is `lto/lto.c':`lto_main'.
24.1.1 LTO modes of operation
-----------------------------
One of the main goals of the GCC link-time infrastructure was to allow
-effective compilation of large programs. For this reason GCC implements
-two link-time compilation modes.
+effective compilation of large programs. For this reason GCC
+implements two link-time compilation modes.
- 1. _LTO mode_, in which the whole program is read into the compiler at
- link-time and optimized in a similar way as if it were a single
+ 1. _LTO mode_, in which the whole program is read into the compiler
+ at link-time and optimized in a similar way as if it were a single
source-level compilation unit.
2. _WHOPR or partitioned mode_, designed to utilize multiple CPUs
and/or a distributed compilation environment to quickly link large
applications. WHOPR stands for WHOle Program optimizeR (not to be
- confused with the semantics of '-fwhole-program'). It partitions
- the aggregated callgraph from many different '.o' files and
+ confused with the semantics of `-fwhole-program'). It partitions
+ the aggregated callgraph from many different `.o' files and
distributes the compilation of the sub-graphs to different CPUs.
Note that distributed compilation is not implemented yet, but since
- the parallelism is facilitated via generating a 'Makefile', it
+ the parallelism is facilitated via generating a `Makefile', it
would be easy to implement.
WHOPR splits LTO into three main stages:
@@ -40178,9 +40630,9 @@ two link-time compilation modes.
global call-graph is generated, and a global analysis procedure
makes transformation decisions. The global call-graph is
partitioned to facilitate parallel optimization during phase 3.
- The results of the WPA stage are stored into new object files which
- contain the partitions of program expressed in the intermediate
- language and the optimization decisions.
+ The results of the WPA stage are stored into new object files
+ which contain the partitions of program expressed in the
+ intermediate language and the optimization decisions.
3. Local transformations (LTRANS) This stage executes in parallel.
All the decisions made during phase 2 are implemented locally in
@@ -40189,17 +40641,18 @@ two link-time compilation modes.
during the phase 2 may be performed on the local call-graph
partitions.
- WHOPR can be seen as an extension of the usual LTO mode of compilation.
-In LTO, WPA and LTRANS are executed within a single execution of the
-compiler, after the whole program has been read into memory.
+ WHOPR can be seen as an extension of the usual LTO mode of
+compilation. In LTO, WPA and LTRANS are executed within a single
+execution of the compiler, after the whole program has been read into
+memory.
When compiling in WHOPR mode, the callgraph is partitioned during the
-WPA stage. The whole program is split into a given number of partitions
-of roughly the same size. The compiler tries to minimize the number of
-references which cross partition boundaries. The main advantage of
-WHOPR is to allow the parallel execution of LTRANS stages, which are the
-most time-consuming part of the compilation process. Additionally, it
-avoids the need to load the whole program into memory.
+WPA stage. The whole program is split into a given number of
+partitions of roughly the same size. The compiler tries to minimize
+the number of references which cross partition boundaries. The main
+advantage of WHOPR is to allow the parallel execution of LTRANS stages,
+which are the most time-consuming part of the compilation process.
+Additionally, it avoids the need to load the whole program into memory.

File: gccint.info, Node: LTO object file layout, Next: IPA, Prev: LTO Overview, Up: LTO
@@ -40209,13 +40662,13 @@ File: gccint.info, Node: LTO object file layout, Next: IPA, Prev: LTO Overvie
LTO information is stored in several ELF sections inside object files.
Data structures and enum codes for sections are defined in
-'lto-streamer.h'.
+`lto-streamer.h'.
- These sections are emitted from 'lto-streamer-out.c' and mapped in all
-at once from 'lto/lto.c':'lto_file_read'. The individual functions
+ These sections are emitted from `lto-streamer-out.c' and mapped in all
+at once from `lto/lto.c':`lto_file_read'. The individual functions
dealing with the reading/writing of each section are described below.
- * Command line options ('.gnu.lto_.opts')
+ * Command line options (`.gnu.lto_.opts')
This section contains the command line options used to generate the
object files. This is used at link time to determine the
@@ -40228,12 +40681,12 @@ dealing with the reading/writing of each section are described below.
the options saved on all the files in a link-time set are applied
globally. No attempt is made at validating the combination of
flags (other than the usual validation done by option processing).
- This is implemented in 'lto/lto.c':'lto_read_all_file_options'.
+ This is implemented in `lto/lto.c':`lto_read_all_file_options'.
- * Symbol table ('.gnu.lto_.symtab')
+ * Symbol table (`.gnu.lto_.symtab')
This table replaces the ELF symbol table for functions and
- variables represented in the LTO IL. Symbols used and exported by
+ variables represented in the LTO IL. Symbols used and exported by
the optimized assembly code of "fat" objects might not match the
ones used and exported by the intermediate code. This table is
necessary because the intermediate code is less optimized and thus
@@ -40247,64 +40700,64 @@ dealing with the reading/writing of each section are described below.
symbol table was used.
The symbol table is emitted in
- 'lto-streamer-out.c':'produce_symtab'.
+ `lto-streamer-out.c':`produce_symtab'.
- * Global declarations and types ('.gnu.lto_.decls')
+ * Global declarations and types (`.gnu.lto_.decls')
This section contains an intermediate language dump of all
declarations and types required to represent the callgraph, static
variables and top-level debug info.
The contents of this section are emitted in
- 'lto-streamer-out.c':'produce_asm_for_decls'. Types and symbols
+ `lto-streamer-out.c':`produce_asm_for_decls'. Types and symbols
are emitted in a topological order that preserves the sharing of
pointers when the file is read back in
- ('lto.c':'read_cgraph_and_symbols').
+ (`lto.c':`read_cgraph_and_symbols').
- * The callgraph ('.gnu.lto_.cgraph')
+ * The callgraph (`.gnu.lto_.cgraph')
This section contains the basic data structure used by the GCC
inter-procedural optimization infrastructure. This section stores
an annotated multi-graph which represents the functions and call
- sites as well as the variables, aliases and top-level 'asm'
+ sites as well as the variables, aliases and top-level `asm'
statements.
- This section is emitted in 'lto-streamer-out.c':'output_cgraph' and
- read in 'lto-cgraph.c':'input_cgraph'.
+ This section is emitted in `lto-streamer-out.c':`output_cgraph'
+ and read in `lto-cgraph.c':`input_cgraph'.
- * IPA references ('.gnu.lto_.refs')
+ * IPA references (`.gnu.lto_.refs')
This section contains references between function and static
- variables. It is emitted by 'lto-cgraph.c':'output_refs' and read
- by 'lto-cgraph.c':'input_refs'.
+ variables. It is emitted by `lto-cgraph.c':`output_refs' and read
+ by `lto-cgraph.c':`input_refs'.
- * Function bodies ('.gnu.lto_.function_body.<name>')
+ * Function bodies (`.gnu.lto_.function_body.<name>')
This section contains function bodies in the intermediate language
representation. Every function body is in a separate section to
allow copying of the section independently to different object
files or reading the function on demand.
- Functions are emitted in 'lto-streamer-out.c':'output_function' and
- read in 'lto-streamer-in.c':'input_function'.
+ Functions are emitted in `lto-streamer-out.c':`output_function'
+ and read in `lto-streamer-in.c':`input_function'.
- * Static variable initializers ('.gnu.lto_.vars')
+ * Static variable initializers (`.gnu.lto_.vars')
This section contains all the symbols in the global variable pool.
- It is emitted by 'lto-cgraph.c':'output_varpool' and read in
- 'lto-cgraph.c':'input_cgraph'.
+ It is emitted by `lto-cgraph.c':`output_varpool' and read in
+ `lto-cgraph.c':`input_cgraph'.
* Summaries and optimization summaries used by IPA passes
- ('.gnu.lto_.<xxx>', where '<xxx>' is one of 'jmpfuncs', 'pureconst'
- or 'reference')
+ (`.gnu.lto_.<xxx>', where `<xxx>' is one of `jmpfuncs',
+ `pureconst' or `reference')
These sections are used by IPA passes that need to emit summary
- information during LTO generation to be read and aggregated at link
- time. Each pass is responsible for implementing two pass manager
- hooks: one for writing the summary and another for reading it in.
- The format of these sections is entirely up to each individual
- pass. The only requirement is that the writer and reader hooks
- agree on the format.
+ information during LTO generation to be read and aggregated at
+ link time. Each pass is responsible for implementing two pass
+ manager hooks: one for writing the summary and another for reading
+ it in. The format of these sections is entirely up to each
+ individual pass. The only requirement is that the writer and
+ reader hooks agree on the format.

File: gccint.info, Node: IPA, Next: WHOPR, Prev: LTO object file layout, Up: LTO
@@ -40323,46 +40776,46 @@ optimization pass is split into several stages that are executed at
different times during WHOPR compilation:
* LGEN time
- 1. _Generate summary_ ('generate_summary' in 'struct
- ipa_opt_pass_d'). This stage analyzes every function body and
- variable initializer is examined and stores relevant
+ 1. _Generate summary_ (`generate_summary' in `struct
+ ipa_opt_pass_d'). This stage analyzes every function body
+ and variable initializer is examined and stores relevant
information into a pass-specific data structure.
- 2. _Write summary_ ('write_summary' in 'struct ipa_opt_pass_d').
+ 2. _Write summary_ (`write_summary' in `struct ipa_opt_pass_d').
This stage writes all the pass-specific information generated
- by 'generate_summary'. Summaries go into their own
- 'LTO_section_*' sections that have to be declared in
- 'lto-streamer.h':'enum lto_section_type'. A new section is
- created by calling 'create_output_block' and data can be
- written using the 'lto_output_*' routines.
+ by `generate_summary'. Summaries go into their own
+ `LTO_section_*' sections that have to be declared in
+ `lto-streamer.h':`enum lto_section_type'. A new section is
+ created by calling `create_output_block' and data can be
+ written using the `lto_output_*' routines.
* WPA time
- 1. _Read summary_ ('read_summary' in 'struct ipa_opt_pass_d').
+ 1. _Read summary_ (`read_summary' in `struct ipa_opt_pass_d').
This stage reads all the pass-specific information in exactly
- the same order that it was written by 'write_summary'.
+ the same order that it was written by `write_summary'.
- 2. _Execute_ ('execute' in 'struct opt_pass'). This performs
+ 2. _Execute_ (`execute' in `struct opt_pass'). This performs
inter-procedural propagation. This must be done without
actual access to the individual function bodies or variable
- initializers. Typically, this results in a transitive closure
- operation over the summary information of all the nodes in the
- callgraph.
+ initializers. Typically, this results in a transitive
+ closure operation over the summary information of all the
+ nodes in the callgraph.
- 3. _Write optimization summary_ ('write_optimization_summary' in
- 'struct ipa_opt_pass_d'). This writes the result of the
+ 3. _Write optimization summary_ (`write_optimization_summary' in
+ `struct ipa_opt_pass_d'). This writes the result of the
inter-procedural propagation into the object file. This can
use the same data structures and helper routines used in
- 'write_summary'.
+ `write_summary'.
* LTRANS time
- 1. _Read optimization summary_ ('read_optimization_summary' in
- 'struct ipa_opt_pass_d'). The counterpart to
- 'write_optimization_summary'. This reads the interprocedural
+ 1. _Read optimization summary_ (`read_optimization_summary' in
+ `struct ipa_opt_pass_d'). The counterpart to
+ `write_optimization_summary'. This reads the interprocedural
optimization decisions in exactly the same format emitted by
- 'write_optimization_summary'.
+ `write_optimization_summary'.
- 2. _Transform_ ('function_transform' and 'variable_transform' in
- 'struct ipa_opt_pass_d'). The actual function bodies and
+ 2. _Transform_ (`function_transform' and `variable_transform' in
+ `struct ipa_opt_pass_d'). The actual function bodies and
variable initializers are updated based on the information
passed down from the _Execute_ stage.
@@ -40382,7 +40835,7 @@ LTO, WHOPR and classic non-LTO compilation.
To simplify development, the GCC pass manager differentiates between
normal inter-procedural passes and small inter-procedural passes. A
-_small inter-procedural pass_ ('SIMPLE_IPA_PASS') is a pass that does
+_small inter-procedural pass_ (`SIMPLE_IPA_PASS') is a pass that does
everything at once and thus it can not be executed during WPA in WHOPR
mode. It defines only the _Execute_ stage and during this stage it
accesses and modifies the function bodies. Such passes are useful for
@@ -40394,13 +40847,13 @@ development of a new inter-procedural pass.
24.3.1 Virtual clones
---------------------
-One of the main challenges of introducing the WHOPR compilation mode was
-addressing the interactions between optimization passes. In LTO
+One of the main challenges of introducing the WHOPR compilation mode
+was addressing the interactions between optimization passes. In LTO
compilation mode, the passes are executed in a sequence, each of which
-consists of analysis (or _Generate summary_), propagation (or _Execute_)
-and _Transform_ stages. Once the work of one pass is finished, the next
-pass sees the updated program representation and can execute. This
-makes the individual passes dependent on each other.
+consists of analysis (or _Generate summary_), propagation (or
+_Execute_) and _Transform_ stages. Once the work of one pass is
+finished, the next pass sees the updated program representation and can
+execute. This makes the individual passes dependent on each other.
In WHOPR mode all passes first execute their _Generate summary_ stage.
Then summary writing marks the end of the LGEN stage. At WPA time, the
@@ -40408,38 +40861,38 @@ summaries are read back into memory and all passes run the _Execute_
stage. Optimization summaries are streamed and sent to LTRANS, where
all the passes execute the _Transform_ stage.
- Most optimization passes split naturally into analysis, propagation and
-transformation stages. But some do not. The main problem arises when
-one pass performs changes and the following pass gets confused by seeing
-different callgraphs between the _Transform_ stage and the _Generate
-summary_ or _Execute_ stage. This means that the passes are required to
-communicate their decisions with each other.
+ Most optimization passes split naturally into analysis, propagation
+and transformation stages. But some do not. The main problem arises
+when one pass performs changes and the following pass gets confused by
+seeing different callgraphs between the _Transform_ stage and the
+_Generate summary_ or _Execute_ stage. This means that the passes are
+required to communicate their decisions with each other.
To facilitate this communication, the GCC callgraph infrastructure
implements _virtual clones_, a method of representing the changes
-performed by the optimization passes in the callgraph without needing to
-update function bodies.
+performed by the optimization passes in the callgraph without needing
+to update function bodies.
- A _virtual clone_ in the callgraph is a function that has no associated
-body, just a description of how to create its body based on a different
-function (which itself may be a virtual clone).
+ A _virtual clone_ in the callgraph is a function that has no
+associated body, just a description of how to create its body based on
+a different function (which itself may be a virtual clone).
The description of function modifications includes adjustments to the
function's signature (which allows, for example, removing or adding
-function arguments), substitutions to perform on the function body, and,
-for inlined functions, a pointer to the function that it will be inlined
-into.
+function arguments), substitutions to perform on the function body,
+and, for inlined functions, a pointer to the function that it will be
+inlined into.
It is also possible to redirect any edge of the callgraph from a
function to its virtual clone. This implies updating of the call site
to adjust for the new function signature.
- Most of the transformations performed by inter-procedural optimizations
-can be represented via virtual clones. For instance, a constant
-propagation pass can produce a virtual clone of the function which
-replaces one of its arguments by a constant. The inliner can represent
-its decisions by producing a clone of a function whose body will be
-later integrated into a given function.
+ Most of the transformations performed by inter-procedural
+optimizations can be represented via virtual clones. For instance, a
+constant propagation pass can produce a virtual clone of the function
+which replaces one of its arguments by a constant. The inliner can
+represent its decisions by producing a clone of a function whose body
+will be later integrated into a given function.
Using _virtual clones_, the program can be easily updated during the
_Execute_ stage, solving most of pass interactions problems that would
@@ -40447,13 +40900,14 @@ otherwise occur during _Transform_.
Virtual clones are later materialized in the LTRANS stage and turned
into real functions. Passes executed after the virtual clone were
-introduced also perform their _Transform_ stage on new functions, so for
-a pass there is no significant difference between operating on a real
-function or a virtual clone introduced before its _Execute_ stage.
+introduced also perform their _Transform_ stage on new functions, so
+for a pass there is no significant difference between operating on a
+real function or a virtual clone introduced before its _Execute_ stage.
- Optimization passes then work on virtual clones introduced before their
-_Execute_ stage as if they were real functions. The only difference is
-that clones are not visible during the _Generate Summary_ stage.
+ Optimization passes then work on virtual clones introduced before
+their _Execute_ stage as if they were real functions. The only
+difference is that clones are not visible during the _Generate Summary_
+stage.
To keep function summaries updated, the callgraph interface allows an
optimizer to register a callback that is called every time a new clone
@@ -40468,19 +40922,19 @@ summaries updated for the _Transform_ stage.
---------------------
GCC represents IPA references in the callgraph. For a function or
-variable 'A', the _IPA reference_ is a list of all locations where the
-address of 'A' is taken and, when 'A' is a variable, a list of all
-direct stores and reads to/from 'A'. References represent an oriented
+variable `A', the _IPA reference_ is a list of all locations where the
+address of `A' is taken and, when `A' is a variable, a list of all
+direct stores and reads to/from `A'. References represent an oriented
multi-graph on the union of nodes of the callgraph and the varpool. See
-'ipa-reference.c':'ipa_reference_write_optimization_summary' and
-'ipa-reference.c':'ipa_reference_read_optimization_summary' for details.
+`ipa-reference.c':`ipa_reference_write_optimization_summary' and
+`ipa-reference.c':`ipa_reference_read_optimization_summary' for details.
24.3.3 Jump functions
---------------------
-Suppose that an optimization pass sees a function 'A' and it knows the
+Suppose that an optimization pass sees a function `A' and it knows the
values of (some of) its arguments. The _jump function_ describes the
-value of a parameter of a given function call in function 'A' based on
+value of a parameter of a given function call in function `A' based on
this knowledge.
Jump functions are used by several optimizations, such as the
@@ -40495,55 +40949,58 @@ File: gccint.info, Node: WHOPR, Next: Internal flags, Prev: IPA, Up: LTO
=====================================================================
Link-time optimization gives relatively minor benefits when used alone.
-The problem is that propagation of inter-procedural information does not
-work well across functions and variables that are called or referenced
-by other compilation units (such as from a dynamically linked library).
-We say that such functions and variables are _externally visible_.
+The problem is that propagation of inter-procedural information does
+not work well across functions and variables that are called or
+referenced by other compilation units (such as from a dynamically
+linked library). We say that such functions and variables are
+_externally visible_.
To make the situation even more difficult, many applications organize
themselves as a set of shared libraries, and the default ELF visibility
rules allow one to overwrite any externally visible symbol with a
different symbol at runtime. This basically disables any optimizations
-across such functions and variables, because the compiler cannot be sure
-that the function body it is seeing is the same function body that will
-be used at runtime. Any function or variable not declared 'static' in
-the sources degrades the quality of inter-procedural optimization.
+across such functions and variables, because the compiler cannot be
+sure that the function body it is seeing is the same function body that
+will be used at runtime. Any function or variable not declared
+`static' in the sources degrades the quality of inter-procedural
+optimization.
To avoid this problem the compiler must assume that it sees the whole
-program when doing link-time optimization. Strictly speaking, the whole
-program is rarely visible even at link-time. Standard system libraries
-are usually linked dynamically or not provided with the link-time
-information. In GCC, the whole program option ('-fwhole-program')
-asserts that every function and variable defined in the current
-compilation unit is static, except for function 'main' (note: at link
-time, the current unit is the union of all objects compiled with LTO).
-Since some functions and variables need to be referenced externally, for
-example by another DSO or from an assembler file, GCC also provides the
-function and variable attribute 'externally_visible' which can be used
-to disable the effect of '-fwhole-program' on a specific symbol.
+program when doing link-time optimization. Strictly speaking, the
+whole program is rarely visible even at link-time. Standard system
+libraries are usually linked dynamically or not provided with the
+link-time information. In GCC, the whole program option
+(`-fwhole-program') asserts that every function and variable defined in
+the current compilation unit is static, except for function `main'
+(note: at link time, the current unit is the union of all objects
+compiled with LTO). Since some functions and variables need to be
+referenced externally, for example by another DSO or from an assembler
+file, GCC also provides the function and variable attribute
+`externally_visible' which can be used to disable the effect of
+`-fwhole-program' on a specific symbol.
The whole program mode assumptions are slightly more complex in C++,
where inline functions in headers are put into _COMDAT_ sections.
COMDAT function and variables can be defined by multiple object files
-and their bodies are unified at link-time and dynamic link-time. COMDAT
-functions are changed to local only when their address is not taken and
-thus un-sharing them with a library is not harmful. COMDAT variables
-always remain externally visible, however for readonly variables it is
-assumed that their initializers cannot be overwritten by a different
-value.
-
- GCC provides the function and variable attribute 'visibility' that can
+and their bodies are unified at link-time and dynamic link-time.
+COMDAT functions are changed to local only when their address is not
+taken and thus un-sharing them with a library is not harmful. COMDAT
+variables always remain externally visible, however for readonly
+variables it is assumed that their initializers cannot be overwritten
+by a different value.
+
+ GCC provides the function and variable attribute `visibility' that can
be used to specify the visibility of externally visible symbols (or
-alternatively an '-fdefault-visibility' command line option). ELF
-defines the 'default', 'protected', 'hidden' and 'internal'
+alternatively an `-fdefault-visibility' command line option). ELF
+defines the `default', `protected', `hidden' and `internal'
visibilities.
- The most commonly used is visibility is 'hidden'. It specifies that
+ The most commonly used is visibility is `hidden'. It specifies that
the symbol cannot be referenced from outside of the current shared
-library. Unfortunately, this information cannot be used directly by the
-link-time optimization in the compiler since the whole shared library
-also might contain non-LTO objects and those are not visible to the
-compiler.
+library. Unfortunately, this information cannot be used directly by
+the link-time optimization in the compiler since the whole shared
+library also might contain non-LTO objects and those are not visible to
+the compiler.
GCC solves this problem using linker plugins. A _linker plugin_ is an
interface to the linker that allows an external program to claim the
@@ -40551,40 +41008,40 @@ ownership of a given object file. The linker then performs the linking
procedure by querying the plugin about the symbol table of the claimed
objects and once the linking decisions are complete, the plugin is
allowed to provide the final object file before the actual linking is
-made. The linker plugin obtains the symbol resolution information which
-specifies which symbols provided by the claimed objects are bound from
-the rest of a binary being linked.
+made. The linker plugin obtains the symbol resolution information
+which specifies which symbols provided by the claimed objects are bound
+from the rest of a binary being linked.
- Currently, the linker plugin works only in combination with the Gold
+ Currently, the linker plugin works only in combination with the Gold
linker, but a GNU ld implementation is under development.
- GCC is designed to be independent of the rest of the toolchain and aims
-to support linkers without plugin support. For this reason it does not
-use the linker plugin by default. Instead, the object files are
-examined by 'collect2' before being passed to the linker and objects
-found to have LTO sections are passed to 'lto1' first. This mode does
-not work for library archives. The decision on what object files from
-the archive are needed depends on the actual linking and thus GCC would
-have to implement the linker itself. The resolution information is
-missing too and thus GCC needs to make an educated guess based on
-'-fwhole-program'. Without the linker plugin GCC also assumes that
-symbols are declared 'hidden' and not referred by non-LTO code by
+ GCC is designed to be independent of the rest of the toolchain and
+aims to support linkers without plugin support. For this reason it
+does not use the linker plugin by default. Instead, the object files
+are examined by `collect2' before being passed to the linker and
+objects found to have LTO sections are passed to `lto1' first. This
+mode does not work for library archives. The decision on what object
+files from the archive are needed depends on the actual linking and
+thus GCC would have to implement the linker itself. The resolution
+information is missing too and thus GCC needs to make an educated guess
+based on `-fwhole-program'. Without the linker plugin GCC also assumes
+that symbols are declared `hidden' and not referred by non-LTO code by
default.

File: gccint.info, Node: Internal flags, Prev: WHOPR, Up: LTO
-24.5 Internal flags controlling 'lto1'
+24.5 Internal flags controlling `lto1'
======================================
-The following flags are passed into 'lto1' and are not meant to be used
+The following flags are passed into `lto1' and are not meant to be used
directly from the command line.
* -fwpa This option runs the serial part of the link-time optimizer
performing the inter-procedural propagation (WPA mode). The
compiler reads in summary information from all inputs and performs
- an analysis based on summary information only. It generates object
- files for subsequent runs of the link-time optimizer where
+ an analysis based on summary information only. It generates
+ object files for subsequent runs of the link-time optimizer where
individual object files are optimized using both summary
information from the WPA mode and the actual function bodies. It
then drives the LTRANS phase.
@@ -40594,13 +41051,13 @@ directly from the command line.
previous run of the LTO in WPA mode. In the LTRANS mode, LTO
optimizes an object and produces the final assembly.
- * -fltrans-output-list=FILE This option specifies a file to which the
- names of LTRANS output files are written. This option is only
- meaningful in conjunction with '-fwpa'.
+ * -fltrans-output-list=FILE This option specifies a file to which
+ the names of LTRANS output files are written. This option is only
+ meaningful in conjunction with `-fwpa'.
- * -fresolution=FILE This option specifies the linker resolution file.
- This option is only meaningful in conjunction with '-fwpa' and as
- option to pass through to the LTO linker plugin.
+ * -fresolution=FILE This option specifies the linker resolution
+ file. This option is only meaningful in conjunction with `-fwpa'
+ and as option to pass through to the LTO linker plugin.

File: gccint.info, Node: Match and Simplify, Next: Funding, Prev: LTO, Up: Top
@@ -40608,11 +41065,13 @@ File: gccint.info, Node: Match and Simplify, Next: Funding, Prev: LTO, Up: T
25 Match and Simplify
*********************
-The GIMPLE and GENERIC pattern matching project match-and-simplify tries
-to address several issues.
+The GIMPLE and GENERIC pattern matching project match-and-simplify
+tries to address several issues.
1. unify expression simplifications currently spread and duplicated
- over separate files like fold-const.c, gimple-fold.c and builtins.c
+ over separate files like fold-const.c, gimple-fold.c and
+ builtins.c
+
2. allow for a cheap way to implement building and simplifying
non-trivial GIMPLE expressions, avoiding the need to go through
building and simplifying GENERIC via fold_buildN and then
@@ -40641,27 +41100,27 @@ File: gccint.info, Node: GIMPLE API, Next: The Language, Up: Match and Simpli
tree, gimple_seq *, tree (*)(tree))
-- GIMPLE function: tree gimple_simplify (enum tree_code, tree, tree,
tree, tree, gimple_seq *, tree (*)(tree))
- -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree,
- tree, gimple_seq *, tree (*)(tree))
- -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree,
- tree, tree, gimple_seq *, tree (*)(tree))
- -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree,
+ -- GIMPLE function: tree gimple_simplify (enum built_in_function,
tree, tree, gimple_seq *, tree (*)(tree))
+ -- GIMPLE function: tree gimple_simplify (enum built_in_function,
+ tree, tree, tree, gimple_seq *, tree (*)(tree))
+ -- GIMPLE function: tree gimple_simplify (enum built_in_function,
+ tree, tree, tree, gimple_seq *, tree (*)(tree))
The main GIMPLE API entry to the expression simplifications
mimicing that of the GENERIC fold_{unary,binary,ternary} functions.
thus providing n-ary overloads for operation or function. The
additional arguments are a gimple_seq where built statements are
-inserted on (if 'NULL' then simplifications requiring new statements are
-not performed) and a valueization hook that can be used to tie
+inserted on (if `NULL' then simplifications requiring new statements
+are not performed) and a valueization hook that can be used to tie
simplifications to a SSA lattice.
- In addition to those APIs 'fold_stmt' is overloaded with a valueization
-hook:
+ In addition to those APIs `fold_stmt' is overloaded with a
+valueization hook:
-- bool: fold_stmt (gimple_stmt_iterator *, tree (*)(tree));
- Ontop of these a 'fold_buildN'-like API for GIMPLE is introduced:
+ Ontop of these a `fold_buildN'-like API for GIMPLE is introduced:
-- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum
tree_code, tree, tree, tree (*valueize) (tree) = NULL);
@@ -40674,13 +41133,13 @@ hook:
built_in_function, tree, tree, tree (*valueize) (tree) =
NULL);
-- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum
- built_in_function, tree, tree, tree, tree (*valueize) (tree) =
- NULL);
+ built_in_function, tree, tree, tree, tree (*valueize) (tree)
+ = NULL);
-- GIMPLE function: tree gimple_convert (gimple_seq *, location_t,
tree, tree);
- which is supposed to replace 'force_gimple_operand (fold_buildN (...),
-...)' and calls to 'fold_convert'. Overloads without the 'location_t'
+ which is supposed to replace `force_gimple_operand (fold_buildN (...),
+...)' and calls to `fold_convert'. Overloads without the `location_t'
argument exist. Built statements are inserted on the provided sequence
and simplification is performed using the optional valueization hook.
@@ -40699,47 +41158,48 @@ an example from the match.pd file:
@0)
This example contains all required parts of an expression
-simplification. A simplification is wrapped inside a '(simplify ...)'
-expression. That contains at least two operands - an expression that is
-matched with the GIMPLE or GENERIC IL and a replacement expression that
-is returned if the match was successful.
+simplification. A simplification is wrapped inside a `(simplify ...)'
+expression. That contains at least two operands - an expression that
+is matched with the GIMPLE or GENERIC IL and a replacement expression
+that is returned if the match was successful.
- Expressions have an operator ID, 'bit_and' in this case. Expressions
-can be lower-case tree codes with '_expr' stripped off or builtin
-function code names in all-caps, like 'BUILT_IN_SQRT'.
+ Expressions have an operator ID, `bit_and' in this case. Expressions
+can be lower-case tree codes with `_expr' stripped off or builtin
+function code names in all-caps, like `BUILT_IN_SQRT'.
- '@n' denotes a so-called capture. It captures the operand and lets you
-refer to it in other places of the match-and-simplify. In the above
-example it is refered to in the replacement expression. Captures are
-'@' followed by a number or an identifier.
+ `@n' denotes a so-called capture. It captures the operand and lets
+you refer to it in other places of the match-and-simplify. In the
+above example it is refered to in the replacement expression. Captures
+are `@' followed by a number or an identifier.
(simplify
(bit_xor @0 @0)
{ build_zero_cst (type); })
- In this example '@0' is mentioned twice which constrains the matched
+ In this example `@0' is mentioned twice which constrains the matched
expression to have two equal operands. This example also introduces
operands written in C code. These can be used in the expression
-replacements and are supposed to evaluate to a tree node which has to be
-a valid GIMPLE operand (so you cannot generate expressions in C code).
+replacements and are supposed to evaluate to a tree node which has to
+be a valid GIMPLE operand (so you cannot generate expressions in C
+code).
(simplify
(trunc_mod integer_zerop@0 @1)
(if (!integer_zerop (@1)))
@0)
- Here '@0' captures the first operand of the trunc_mod expression which
-is also predicated with 'integer_zerop'. Expression operands may be
+ Here `@0' captures the first operand of the trunc_mod expression which
+is also predicated with `integer_zerop'. Expression operands may be
either expressions, predicates or captures. Captures can be
unconstrained or capture expresions or predicates.
This example introduces an optional operand of simplify, the
-if-expression. This condition is evaluated after the expression matched
-in the IL and is required to evaluate to true to enable the replacement
-expression. The expression operand of the 'if' is a standard C
-expression which may contain references to captures.
+if-expression. This condition is evaluated after the expression
+matched in the IL and is required to evaluate to true to enable the
+replacement expression. The expression operand of the `if' is a
+standard C expression which may contain references to captures.
- A 'if' expression can be used to specify a common condition for
+ A `if' expression can be used to specify a common condition for
multiple simplify patterns, avoiding the need to repeat that multiple
times:
@@ -40773,25 +41233,26 @@ times:
})
#endif
- In the above example, '@2' captures the result of the expression '(addr
-@0)'. For outermost expression only its type can be captured, and the
-keyword 'type' is reserved for this purpose. The above example also
-gives a way to conditionalize patterns to only apply to 'GIMPLE' or
-'GENERIC' by means of using the pre-defined preprocessor macros 'GIMPLE'
-and 'GENERIC' and using preprocessor directives.
+ In the above example, `@2' captures the result of the expression
+`(addr @0)'. For outermost expression only its type can be captured,
+and the keyword `type' is reserved for this purpose. The above example
+also gives a way to conditionalize patterns to only apply to `GIMPLE'
+or `GENERIC' by means of using the pre-defined preprocessor macros
+`GIMPLE' and `GENERIC' and using preprocessor directives.
(simplify
(bit_and:c integral_op_p@0 (bit_ior:c (bit_not @0) @1))
(bit_and @1 @0))
Here we introduce flags on match expressions. There is currently a
-single flag, 'c', which denotes that the expression should be also
+single flag, `c', which denotes that the expression should be also
matched commutated. Thus the above match expression is really the
following four match expressions:
- (bit_and integral_op_p@0 (bit_ior (bit_not @0) @1)) (bit_and (bit_ior
-(bit_not @0) @1) integral_op_p@0) (bit_and integral_op_p@0 (bit_ior @1
-(bit_not @0))) (bit_and (bit_ior @1 (bit_not @0)) integral_op_p@0)
+ (bit_and integral_op_p@0 (bit_ior (bit_not @0) @1)) (bit_and
+(bit_ior (bit_not @0) @1) integral_op_p@0) (bit_and integral_op_p@0
+(bit_ior @1 (bit_not @0))) (bit_and (bit_ior @1 (bit_not @0))
+integral_op_p@0)
Usual canonicalizations you know from GENERIC expressions are applied
before matching, so for example constant operands always come second in
@@ -40804,8 +41265,8 @@ commutative expressions.
(op @0 integer_zerop)
@0))
- A 'for' expression can be used to repeat a pattern for each operator
-specified, substituting 'op'. 'for' can be nested and a 'for' can have
+ A `for' expression can be used to repeat a pattern for each operator
+specified, substituting `op'. `for' can be nested and a `for' can have
multiple operators to iterate.
(for opa (plus minus)
@@ -40813,24 +41274,24 @@ multiple operators to iterate.
(for opc (plus minus)
(simplify...
- In this example the pattern will be repeated four times with 'opa, opb,
-opc' being 'plus, minus, plus', 'plus, minus, minus', 'minus, plus,
-plus', 'minus, plus, minus'.
+ In this example the pattern will be repeated four times with `opa,
+opb, opc' being `plus, minus, plus', `plus, minus, minus', `minus,
+plus, plus', `minus, plus, minus'.
- To avoid repeating operator lists in 'for' you can name them via
+ To avoid repeating operator lists in `for' you can name them via
(define_operator_list pmm plus minus mult)
- and use them in 'for' operator lists where they get expanded.
+ and use them in `for' operator lists where they get expanded.
(for opa (pmm trunc_div)
(simplify...
- So this example iterates over 'plus', 'minus', 'mult' and 'trunc_div'.
+ So this example iterates over `plus', `minus', `mult' and `trunc_div'.
Using operator lists can also remove the need to explicitely write a
-'for'. All operator list uses that appear in a 'simplify' or 'match'
-pattern in operator positions will implicitely be added to a new 'for'.
+`for'. All operator list uses that appear in a `simplify' or `match'
+pattern in operator positions will implicitely be added to a new `for'.
For example
(define_operator_list SQRT BUILT_IN_SQRTF BUILT_IN_SQRT BUILT_IN_SQRTL)
@@ -40847,7 +41308,7 @@ For example
(SQRT (POW @0 @1))
(POW (abs @0) (mult @1 { built_real (TREE_TYPE (@1), dconsthalf); }))))
- Another building block are 'with' expressions in the result expression
+ Another building block are `with' expressions in the result expression
which nest the generated code in a new C block followed by its argument:
(simplify
@@ -40855,37 +41316,37 @@ which nest the generated code in a new C block followed by its argument:
(with { tree utype = unsigned_type_for (type); }
(convert (mult (convert:utype @0) (convert:utype @1)))))
- This allows code nested in the 'with' to refer to the declared
+ This allows code nested in the `with' to refer to the declared
variables. In the above case we use the feature to specify the type of
-a generated expression with the ':type' syntax where 'type' needs to be
-an identifier that refers to the desired type. Usually the types of the
-generated result expressions are determined from the context, but
+a generated expression with the `:type' syntax where `type' needs to be
+an identifier that refers to the desired type. Usually the types of
+the generated result expressions are determined from the context, but
sometimes like in the above case it is required that you specify them
explicitely.
As intermediate conversions are often optional there is a way to avoid
the need to repeat patterns both with and without such conversions.
-Namely you can mark a conversion as being optional with a '?':
+Namely you can mark a conversion as being optional with a `?':
(simplify
(eq (convert@0 @1) (convert? @2))
(eq @1 (convert @2)))
- which will match both '(eq (convert @1) (convert @2))' and '(eq
+ which will match both `(eq (convert @1) (convert @2))' and `(eq
(convert @1) @2)'. The optional converts are supposed to be all either
-present or not, thus '(eq (convert? @1) (convert? @2))' will result in
+present or not, thus `(eq (convert? @1) (convert? @2))' will result in
two patterns only. If you want to match all four combinations you have
-access to two additional conditional converts as in '(eq (convert1? @1)
+access to two additional conditional converts as in `(eq (convert1? @1)
(convert2? @2))'.
Predicates available from the GCC middle-end need to be made available
-explicitely via 'define_predicates':
+explicitely via `define_predicates':
(define_predicates
integer_onep integer_zerop integer_all_onesp)
You can also define predicates using the pattern matching language and
-the 'match' form:
+the `match' form:
(match negate_expr_p
INTEGER_CST
@@ -40894,11 +41355,11 @@ the 'match' form:
(match negate_expr_p
(negate @0))
- This shows that for 'match' expressions there is 't' available which
+ This shows that for `match' expressions there is `t' available which
captures the outermost expression (something not possible in the
-'simplify' context). As you can see 'match' has an identifier as first
+`simplify' context). As you can see `match' has an identifier as first
operand which is how you refer to the predicate in patterns. Multiple
-'match' for the same identifier add additional cases where the predicate
+`match' for the same identifier add additional cases where the predicate
matches.
Predicates can also match an expression in which case you need to
@@ -40936,8 +41397,8 @@ to free software developers--the Free Software Foundation, and others.
The way to convince distributors to do this is to demand it and expect
it from them. So when you compare distributors, judge them partly by
-how much they give to free software development. Show distributors they
-must compete to be the one who gives the most.
+how much they give to free software development. Show distributors
+they must compete to be the one who gives the most.
To make this approach work, you must insist on numbers that you can
compare, such as, "We will donate ten dollars to the Frobnitz project
@@ -40947,8 +41408,8 @@ for comparison.
Even a precise fraction "of the profits from this disk" is not very
meaningful, since creative accounting and unrelated business decisions
-can greatly alter what fraction of the sales price counts as profit. If
-the price you pay is $50, ten percent of the profit is probably less
+can greatly alter what fraction of the sales price counts as profit.
+If the price you pay is $50, ten percent of the profit is probably less
than a dollar; it might be a few cents, or nothing at all.
Some redistributors do development work themselves. This is useful
@@ -40958,8 +41419,8 @@ difference than others. For example, maintaining a separate version of
a program contributes very little; maintaining the standard version of a
program for the whole community contributes much. Easy new ports
contribute little, since someone else would surely do them; difficult
-ports such as adding a new CPU to the GNU Compiler Collection contribute
-more; major new features or packages contribute the most.
+ports such as adding a new CPU to the GNU Compiler Collection
+contribute more; major new features or packages contribute the most.
By establishing the idea that supporting further development is "the
proper thing to do" when distributing free software for a fee, we can
@@ -40983,8 +41444,8 @@ now widely used; though these systems are often referred to as "Linux",
they are more accurately called GNU/Linux systems.
For more information, see:
- <http://www.gnu.org/>
- <http://www.gnu.org/gnu/linux-and-gnu.html>
+ `http://www.gnu.org/'
+ `http://www.gnu.org/gnu/linux-and-gnu.html'

File: gccint.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top
@@ -40994,7 +41455,7 @@ GNU General Public License
Version 3, 29 June 2007
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
@@ -41014,27 +41475,27 @@ GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
- When we speak of free software, we are referring to freedom, not price.
-Our General Public Licenses are designed to make sure that you have the
-freedom to distribute copies of free software (and charge for them if
-you wish), that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs, and that you know you can do these things.
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
+these rights or asking you to surrender the rights. Therefore, you
+have certain responsibilities if you distribute copies of the software,
+or if you modify it: responsibilities to respect the freedom of others.
- For example, if you distribute copies of such a program, whether gratis
-or for a fee, you must pass on to the recipients the same freedoms that
-you received. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
- Developers that use the GNU GPL protect your rights with two steps: (1)
-assert copyright on the software, and (2) offer you this License giving
-you legal permission to copy, distribute and/or modify it.
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
@@ -41043,15 +41504,16 @@ changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so. This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software. The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products. If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
+modified versions of the software inside them, although the
+manufacturer can do so. This is fundamentally incompatible with the
+aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for
+individuals to use, which is precisely where it is most unacceptable.
+Therefore, we have designed this version of the GPL to prohibit the
+practice for those products. If such problems arise substantially in
+other domains, we stand ready to extend this provision to those domains
+in future versions of the GPL, as needed to protect the freedom of
+users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
@@ -41088,8 +41550,8 @@ TERMS AND CONDITIONS
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
- infringement under applicable copyright law, except executing it on
- a computer or modifying a private copy. Propagation includes
+ infringement under applicable copyright law, except executing it
+ on a computer or modifying a private copy. Propagation includes
copying, distribution (with or without modification), making
available to the public, and in some countries other activities as
well.
@@ -41103,8 +41565,8 @@ TERMS AND CONDITIONS
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to
- the extent that warranties are provided), that licensees may convey
- the work under this License, and how to view a copy of this
+ the extent that warranties are provided), that licensees may
+ convey the work under this License, and how to view a copy of this
License. If the interface presents a list of user commands or
options, such as a menu, a prominent item in the list meets this
criterion.
@@ -41112,8 +41574,8 @@ TERMS AND CONDITIONS
1. Source Code.
The "source code" for a work means the preferred form of the work
- for making modifications to it. "Object code" means any non-source
- form of a work.
+ for making modifications to it. "Object code" means any
+ non-source form of a work.
A "Standard Interface" means an interface that either is an
official standard defined by a recognized standards body, or, in
@@ -41124,10 +41586,10 @@ TERMS AND CONDITIONS
The "System Libraries" of an executable work include anything,
other than the work as a whole, that (a) is included in the normal
form of packaging a Major Component, but which is not part of that
- Major Component, and (b) serves only to enable use of the work with
- that Major Component, or to implement a Standard Interface for
- which an implementation is available to the public in source code
- form. A "Major Component", in this context, means a major
+ Major Component, and (b) serves only to enable use of the work
+ with that Major Component, or to implement a Standard Interface
+ for which an implementation is available to the public in source
+ code form. A "Major Component", in this context, means a major
essential component (kernel, window system, and so on) of the
specific operating system (if any) on which the executable work
runs, or a compiler used to produce the work, or an object code
@@ -41135,15 +41597,15 @@ TERMS AND CONDITIONS
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
- work) run the object code and to modify the work, including scripts
- to control those activities. However, it does not include the
- work's System Libraries, or general-purpose tools or generally
+ work) run the object code and to modify the work, including
+ scripts to control those activities. However, it does not include
+ the work's System Libraries, or general-purpose tools or generally
available free programs which are used unmodified in performing
those activities but which are not part of the work. For example,
- Corresponding Source includes interface definition files associated
- with source files for the work, and the source code for shared
- libraries and dynamically linked subprograms that the work is
- specifically designed to require, such as by intimate data
+ Corresponding Source includes interface definition files
+ associated with source files for the work, and the source code for
+ shared libraries and dynamically linked subprograms that the work
+ is specifically designed to require, such as by intimate data
communication or control flow between those subprograms and other
parts of the work.
@@ -41160,22 +41622,22 @@ TERMS AND CONDITIONS
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running
- a covered work is covered by this License only if the output, given
- its content, constitutes a covered work. This License acknowledges
- your rights of fair use or other equivalent, as provided by
- copyright law.
+ a covered work is covered by this License only if the output,
+ given its content, constitutes a covered work. This License
+ acknowledges your rights of fair use or other equivalent, as
+ provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise
remains in force. You may convey covered works to others for the
- sole purpose of having them make modifications exclusively for you,
- or provide you with facilities for running those works, provided
- that you comply with the terms of this License in conveying all
- material for which you do not control copyright. Those thus making
- or running the covered works for you must do so exclusively on your
- behalf, under your direction and control, on terms that prohibit
- them from making any copies of your copyrighted material outside
- their relationship with you.
+ sole purpose of having them make modifications exclusively for
+ you, or provide you with facilities for running those works,
+ provided that you comply with the terms of this License in
+ conveying all material for which you do not control copyright.
+ Those thus making or running the covered works for you must do so
+ exclusively on your behalf, under your direction and control, on
+ terms that prohibit them from making any copies of your
+ copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section
@@ -41192,8 +41654,8 @@ TERMS AND CONDITIONS
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License
- with respect to the covered work, and you disclaim any intention to
- limit operation or modification of the work as a means of
+ with respect to the covered work, and you disclaim any intention
+ to limit operation or modification of the work as a means of
enforcing, against the work's users, your or third parties' legal
rights to forbid circumvention of technological measures.
@@ -41263,8 +41725,8 @@ TERMS AND CONDITIONS
b. Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
- written offer, valid for at least three years and valid for as
- long as you offer spare parts or customer support for that
+ written offer, valid for at least three years and valid for
+ as long as you offer spare parts or customer support for that
product model, to give anyone who possesses the object code
either (1) a copy of the Corresponding Source for all the
software in the product that is covered by this License, on a
@@ -41274,31 +41736,32 @@ TERMS AND CONDITIONS
to copy the Corresponding Source from a network server at no
charge.
- c. Convey individual copies of the object code with a copy of the
- written offer to provide the Corresponding Source. This
+ c. Convey individual copies of the object code with a copy of
+ the written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially,
and only if you received the object code with such an offer,
in accord with subsection 6b.
d. Convey the object code by offering access from a designated
- place (gratis or for a charge), and offer equivalent access to
- the Corresponding Source in the same way through the same
+ place (gratis or for a charge), and offer equivalent access
+ to the Corresponding Source in the same way through the same
place at no further charge. You need not require recipients
to copy the Corresponding Source along with the object code.
If the place to copy the object code is a network server, the
- Corresponding Source may be on a different server (operated by
- you or a third party) that supports equivalent copying
- facilities, provided you maintain clear directions next to the
- object code saying where to find the Corresponding Source.
+ Corresponding Source may be on a different server (operated
+ by you or a third party) that supports equivalent copying
+ facilities, provided you maintain clear directions next to
+ the object code saying where to find the Corresponding Source.
Regardless of what server hosts the Corresponding Source, you
- remain obligated to ensure that it is available for as long as
- needed to satisfy these requirements.
+ remain obligated to ensure that it is available for as long
+ as needed to satisfy these requirements.
e. Convey the object code using peer-to-peer transmission,
provided you inform other peers where the object code and
Corresponding Source of the work are being offered to the
general public at no charge under subsection 6d.
+
A separable portion of the object code, whose source code is
excluded from the Corresponding Source as a System Library, need
not be included in conveying the object code work.
@@ -41306,8 +41769,8 @@ TERMS AND CONDITIONS
A "User Product" is either (1) a "consumer product", which means
any tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
- incorporation into a dwelling. In determining whether a product is
- a consumer product, doubtful cases shall be resolved in favor of
+ incorporation into a dwelling. In determining whether a product
+ is a consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
"normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the
@@ -41338,11 +41801,11 @@ TERMS AND CONDITIONS
The requirement to provide Installation Information does not
include a requirement to continue to provide support service,
- warranty, or updates for a work that has been modified or installed
- by the recipient, or for the User Product in which it has been
- modified or installed. Access to a network may be denied when the
- modification itself materially and adversely affects the operation
- of the network or violates the rules and protocols for
+ warranty, or updates for a work that has been modified or
+ installed by the recipient, or for the User Product in which it
+ has been modified or installed. Access to a network may be denied
+ when the modification itself materially and adversely affects the
+ operation of the network or violates the rules and protocols for
communication across the network.
Corresponding Source conveyed, and Installation Information
@@ -41372,8 +41835,8 @@ TERMS AND CONDITIONS
Notwithstanding any other provision of this License, for material
you add to a covered work, you may (if authorized by the copyright
- holders of that material) supplement the terms of this License with
- terms:
+ holders of that material) supplement the terms of this License
+ with terms:
a. Disclaiming warranty or limiting liability differently from
the terms of sections 15 and 16 of this License; or
@@ -41383,8 +41846,9 @@ TERMS AND CONDITIONS
Legal Notices displayed by works containing it; or
c. Prohibiting misrepresentation of the origin of that material,
- or requiring that modified versions of such material be marked
- in reasonable ways as different from the original version; or
+ or requiring that modified versions of such material be
+ marked in reasonable ways as different from the original
+ version; or
d. Limiting the use for publicity purposes of names of licensors
or authors of the material; or
@@ -41403,10 +41867,11 @@ TERMS AND CONDITIONS
you received it, or any part of it, contains a notice stating that
it is governed by this License along with a term that is a further
restriction, you may remove that term. If a license document
- contains a further restriction but permits relicensing or conveying
- under this License, you may add to a covered work material governed
- by the terms of that license document, provided that the further
- restriction does not survive such relicensing or conveying.
+ contains a further restriction but permits relicensing or
+ conveying under this License, you may add to a covered work
+ material governed by the terms of that license document, provided
+ that the further restriction does not survive such relicensing or
+ conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
@@ -41422,13 +41887,13 @@ TERMS AND CONDITIONS
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights
- under this License (including any patent licenses granted under the
- third paragraph of section 11).
+ under this License (including any patent licenses granted under
+ the third paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -41440,10 +41905,10 @@ TERMS AND CONDITIONS
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, you do not qualify to receive new licenses
- for the same material under section 10.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, you do not qualify to receive new
+ licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
@@ -41457,7 +41922,7 @@ TERMS AND CONDITIONS
by modifying or propagating a covered work, you indicate your
acceptance of this License to do so.
- 10. Automatic Licensing of Downstream Recipients.
+ 10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
@@ -41471,21 +41936,21 @@ TERMS AND CONDITIONS
covered work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or
- could give under the previous paragraph, plus a right to possession
- of the Corresponding Source of the work from the predecessor in
- interest, if the predecessor has it or can get it with reasonable
- efforts.
+ could give under the previous paragraph, plus a right to
+ possession of the Corresponding Source of the work from the
+ predecessor in interest, if the predecessor has it or can get it
+ with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you
- may not impose a license fee, royalty, or other charge for exercise
- of rights granted under this License, and you may not initiate
- litigation (including a cross-claim or counterclaim in a lawsuit)
- alleging that any patent claim is infringed by making, using,
- selling, offering for sale, or importing the Program or any portion
- of it.
+ may not impose a license fee, royalty, or other charge for
+ exercise of rights granted under this License, and you may not
+ initiate litigation (including a cross-claim or counterclaim in a
+ lawsuit) alleging that any patent claim is infringed by making,
+ using, selling, offering for sale, or importing the Program or any
+ portion of it.
- 11. Patents.
+ 11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based.
@@ -41505,15 +41970,15 @@ TERMS AND CONDITIONS
Each contributor grants you a non-exclusive, worldwide,
royalty-free patent license under the contributor's essential
patent claims, to make, use, sell, offer for sale, import and
- otherwise run, modify and propagate the contents of its contributor
- version.
+ otherwise run, modify and propagate the contents of its
+ contributor version.
In the following three paragraphs, a "patent license" is any
express agreement or commitment, however denominated, not to
enforce a patent (such as an express permission to practice a
- patent or covenant not to sue for patent infringement). To "grant"
- such a patent license to a party means to make such an agreement or
- commitment not to enforce a patent against the party.
+ patent or covenant not to sue for patent infringement). To
+ "grant" such a patent license to a party means to make such an
+ agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent
license, and the Corresponding Source of the work is not available
@@ -41543,35 +42008,36 @@ TERMS AND CONDITIONS
conditioned on the non-exercise of one or more of the rights that
are specifically granted under this License. You may not convey a
covered work if you are a party to an arrangement with a third
- party that is in the business of distributing software, under which
- you make payment to the third party based on the extent of your
- activity of conveying the work, and under which the third party
- grants, to any of the parties who would receive the covered work
- from you, a discriminatory patent license (a) in connection with
- copies of the covered work conveyed by you (or copies made from
- those copies), or (b) primarily for and in connection with specific
- products or compilations that contain the covered work, unless you
- entered into that arrangement, or that patent license was granted,
- prior to 28 March 2007.
+ party that is in the business of distributing software, under
+ which you make payment to the third party based on the extent of
+ your activity of conveying the work, and under which the third
+ party grants, to any of the parties who would receive the covered
+ work from you, a discriminatory patent license (a) in connection
+ with copies of the covered work conveyed by you (or copies made
+ from those copies), or (b) primarily for and in connection with
+ specific products or compilations that contain the covered work,
+ unless you entered into that arrangement, or that patent license
+ was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
- 12. No Surrender of Others' Freedom.
+ 12. No Surrender of Others' Freedom.
- If conditions are imposed on you (whether by court order, agreement
- or otherwise) that contradict the conditions of this License, they
- do not excuse you from the conditions of this License. If you
- cannot convey a covered work so as to satisfy simultaneously your
- obligations under this License and any other pertinent obligations,
- then as a consequence you may not convey it at all. For example,
- if you agree to terms that obligate you to collect a royalty for
- further conveying from those to whom you convey the Program, the
- only way you could satisfy both those terms and this License would
- be to refrain entirely from conveying the Program.
+ If conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot convey a covered work so as to satisfy
+ simultaneously your obligations under this License and any other
+ pertinent obligations, then as a consequence you may not convey it
+ at all. For example, if you agree to terms that obligate you to
+ collect a royalty for further conveying from those to whom you
+ convey the Program, the only way you could satisfy both those
+ terms and this License would be to refrain entirely from conveying
+ the Program.
- 13. Use with the GNU Affero General Public License.
+ 13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
@@ -41582,21 +42048,22 @@ TERMS AND CONDITIONS
General Public License, section 13, concerning interaction through
a network will apply to the combination as such.
- 14. Revised Versions of this License.
+ 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new
- versions of the GNU General Public License from time to time. Such
- new versions will be similar in spirit to the present version, but
- may differ in detail to address new problems or concerns.
+ versions of the GNU General Public License from time to time.
+ Such new versions will be similar in spirit to the present
+ version, but may differ in detail to address new problems or
+ concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU
General Public License "or any later version" applies to it, you
have the option of following the terms and conditions either of
- that numbered version or of any later version published by the Free
- Software Foundation. If the Program does not specify a version
- number of the GNU General Public License, you may choose any
- version ever published by the Free Software Foundation.
+ that numbered version or of any later version published by the
+ Free Software Foundation. If the Program does not specify a
+ version number of the GNU General Public License, you may choose
+ any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that
@@ -41608,24 +42075,24 @@ TERMS AND CONDITIONS
author or copyright holder as a result of your choosing to follow a
later version.
- 15. Disclaimer of Warranty.
+ 15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
- APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
+ APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
- MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
NECESSARY SERVICING, REPAIR OR CORRECTION.
- 16. Limitation of Liability.
+ 16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
- AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
- DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+ AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
+ FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
@@ -41633,7 +42100,7 @@ TERMS AND CONDITIONS
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
- 17. Interpretation of Sections 15 and 16.
+ 17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
@@ -41642,6 +42109,7 @@ TERMS AND CONDITIONS
connection with the Program, unless a warranty or assumption of
liability accompanies a copy of the Program in return for a fee.
+
END OF TERMS AND CONDITIONS
===========================
@@ -41653,9 +42121,9 @@ possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
- To do so, attach the following notices to the program. It is safest to
-attach them to the start of each source file to most effectively state
-the exclusion of warranty; and each file should have at least the
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
@@ -41672,20 +42140,20 @@ the exclusion of warranty; and each file should have at least the
General Public License for more details.
You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
+ along with this program. If not, see `http://www.gnu.org/licenses/'.
Also add information on how to contact you by electronic and paper
mail.
- If the program does terminal interaction, make it output a short notice
-like this when it starts in an interactive mode:
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
PROGRAM Copyright (C) YEAR NAME OF AUTHOR
- This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
- under certain conditions; type 'show c' for details.
+ under certain conditions; type `show c' for details.
- The hypothetical commands 'show w' and 'show c' should show the
+ The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
@@ -41693,14 +42161,14 @@ use an "about box".
You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. For more information on this, and how to apply and follow
-the GNU GPL, see <http://www.gnu.org/licenses/>.
+the GNU GPL, see `http://www.gnu.org/licenses/'.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
-please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
+please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.

File: gccint.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top
@@ -41711,7 +42179,7 @@ GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
+ `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -41736,21 +42204,21 @@ GNU Free Documentation License
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book. We
- recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it can
- be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright 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, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
- the license if you copy, modify or distribute the work in a way
- requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "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 containing the
Document or a portion of it, either copied verbatim, or with
@@ -41768,12 +42236,12 @@ GNU Free Documentation License
regarding them.
The "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 above definition of Secondary then it
- is not allowed to be designated as Invariant. The Document may
- contain zero Invariant Sections. If the Document does not identify
- any Invariant Sections then there are none.
+ 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 above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -41784,27 +42252,27 @@ GNU Free Documentation License
A "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 generic text editors or (for images composed
- of pixels) generic paint programs or (for drawings) some widely
- available drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of formats
- suitable for input to text formatters. A copy made in an otherwise
- Transparent file format whose markup, or absence 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".
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence 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".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and standard-conforming
- simple HTML, PostScript or PDF designed for human modification.
- Examples of transparent image formats include PNG, XCF and JPG.
- Opaque formats include proprietary formats that can be read and
- edited only by proprietary word processors, SGML or XML for which
- the DTD and/or processing tools are not generally available, and
- the machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -41842,8 +42310,8 @@ GNU Free Documentation License
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow the
- conditions in section 3.
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -41857,11 +42325,12 @@ GNU Free Documentation License
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on the
- covers in addition. Copying with changes limited to the covers, as
- long as they preserve the title of the Document and satisfy these
- conditions, can be treated as verbatim copying in other respects.
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -41869,39 +42338,40 @@ GNU Free Documentation License
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with
- each Opaque copy a computer-network location from which the general
- network-using public has access to download using public-standard
- network protocols a complete Transparent copy of the Document, free
- of added material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of Opaque
- copies in quantity, to ensure that this Transparent copy will
- remain thus accessible at the stated location until at least one
- year after the last time you distribute an Opaque copy (directly or
- through your agents or retailers) of that edition to the public.
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies,
- to give them a chance to provide you with an updated version of the
- Document.
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with the
- Modified Version filling the role of the Document, thus licensing
- distribution and modification of the Modified Version to whoever
- possesses a copy of it. In addition, you must do these things in
- the Modified Version:
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the
- History section of the Document). You may use the same title
- as a previous version if the original publisher of that
- version gives permission.
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -41931,30 +42401,31 @@ GNU Free Documentation License
I. Preserve the section Entitled "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, 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.
+ 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, 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.
J. Preserve the network location, if any, given in 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 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.
+ previous versions it was based on. These may be placed in
+ the "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.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section
- all the substance and tone of each of the contributor
+ 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.
- L. Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the
- equivalent are not considered part of the section titles.
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -41967,11 +42438,11 @@ GNU Free Documentation License
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain 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 be distinct from any other
- section titles.
+ 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 be distinct from any
+ other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -41980,15 +42451,15 @@ GNU Free Documentation License
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of
- the list of Cover Texts in the Modified Version. Only one passage
- of Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover, previously added
- by you or by arrangement made by the same entity you are acting on
- behalf of, you may not add another; but you may replace the old
- one, on explicit permission from the previous publisher that added
- the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -41998,8 +42469,8 @@ GNU Free Documentation License
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination all
- of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -42026,20 +42497,20 @@ GNU Free Documentation License
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the documents
- in all other respects.
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
7. AGGREGATION WITH INDEPENDENT WORKS
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
+ 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 the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -42084,8 +42555,8 @@ GNU Free Documentation License
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -42097,33 +42568,33 @@ GNU Free Documentation License
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, receipt of a copy of some or all of the
- same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, receipt of a copy of some or all of
+ the same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- <http://www.gnu.org/copyleft/>.
+ `http://www.gnu.org/copyleft/'.
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 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 Foundation. If the
- Document does not specify a version number 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
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number 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 statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
@@ -42153,6 +42624,7 @@ GNU Free Documentation License
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
+
ADDENDUM: How to use this License for your documents
====================================================
@@ -42169,7 +42641,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the "with...Texts." line with this:
+replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -42180,9 +42652,9 @@ combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of free
-software license, such as the GNU General Public License, to permit
-their use in free software.
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.

File: gccint.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top
@@ -42190,9 +42662,9 @@ File: gccint.info, Node: Contributors, Next: Option Index, Prev: GNU Free Doc
Contributors to GCC
*******************
-The GCC project would like to thank its many contributors. Without them
-the project would not have been nearly as successful as it has been.
-Any omissions in this list are accidental. Feel free to contact
+The GCC project would like to thank its many contributors. Without
+them the project would not have been nearly as successful as it has
+been. Any omissions in this list are accidental. Feel free to contact
<law@redhat.com> or <gerald@pfeifer.com> if you have been left out or
some of your contributions are not listed. Please keep this list in
alphabetical order.
@@ -42325,7 +42797,7 @@ alphabetical order.
* The GNU Classpath project for all of their merged runtime code.
* Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work,
- '--help', and other random hacking.
+ `--help', and other random hacking.
* Michael Cook for libstdc++ cleanup patches to reduce warnings.
@@ -42345,8 +42817,8 @@ alphabetical order.
* Paul Dale for his work to add uClinux platform support to the m68k
backend.
- * Dario Dariol contributed the four varieties of sample programs that
- print a copy of their source.
+ * Dario Dariol contributed the four varieties of sample programs
+ that print a copy of their source.
* Russell Davidson for fstream and stringstream fixes in libstdc++.
@@ -42361,19 +42833,19 @@ alphabetical order.
* Gabriel Dos Reis for contributions to G++, contributions and
maintenance of GCC diagnostics infrastructure, libstdc++-v3,
- including 'valarray<>', 'complex<>', maintaining the numerics
- library (including that pesky '<limits>' :-) and keeping up-to-date
- anything to do with numbers.
+ including `valarray<>', `complex<>', maintaining the numerics
+ library (including that pesky `<limits>' :-) and keeping
+ up-to-date anything to do with numbers.
* Ulrich Drepper for his work on glibc, testing of GCC using glibc,
- ISO C99 support, CFG dumping support, etc., plus support of the C++
- runtime libraries including for all kinds of C interface issues,
- contributing and maintaining 'complex<>', sanity checking and
- disbursement, configuration architecture, libio maintenance, and
- early math work.
+ ISO C99 support, CFG dumping support, etc., plus support of the
+ C++ runtime libraries including for all kinds of C interface
+ issues, contributing and maintaining `complex<>', sanity checking
+ and disbursement, configuration architecture, libio maintenance,
+ and early math work.
* Franc,ois Dumont for his work on libstdc++-v3, especially
- maintaining and improving 'debug-mode' and associative and
+ maintaining and improving `debug-mode' and associative and
unordered containers.
* Zdenek Dvorak for a new loop unroller and various fixes.
@@ -42425,10 +42897,11 @@ alphabetical order.
* Peter Gerwinski for various bug fixes and the Pascal front end.
* Kaveh R. Ghazi for his direction via the steering committee,
- amazing work to make '-W -Wall -W* -Werror' useful, and testing GCC
- on a plethora of platforms. Kaveh extends his gratitude to the
- CAIP Center at Rutgers University for providing him with computing
- resources to work on Free Software from the late 1980s to 2010.
+ amazing work to make `-W -Wall -W* -Werror' useful, and testing
+ GCC on a plethora of platforms. Kaveh extends his gratitude to
+ the CAIP Center at Rutgers University for providing him with
+ computing resources to work on Free Software from the late 1980s
+ to 2010.
* John Gilmore for a donation to the FSF earmarked improving GNU
Java.
@@ -42440,21 +42913,21 @@ alphabetical order.
support, improved leaf function register allocation, and his
direction via the steering committee.
- * Jonny Grant for improvements to 'collect2's' '--help'
+ * Jonny Grant for improvements to `collect2's' `--help'
documentation.
- * Anthony Green for his '-Os' contributions, the moxie port, and Java
- front end work.
+ * Anthony Green for his `-Os' contributions, the moxie port, and
+ Java front end work.
- * Stu Grossman for gdb hacking, allowing GCJ developers to debug Java
- code.
+ * Stu Grossman for gdb hacking, allowing GCJ developers to debug
+ Java code.
* Michael K. Gschwind contributed the port to the PDP-11.
* Richard Biener for his ongoing middle-end contributions and bug
fixes and for release management.
- * Ron Guilmette implemented the 'protoize' and 'unprotoize' tools,
+ * Ron Guilmette implemented the `protoize' and `unprotoize' tools,
the support for Dwarf symbolic debugging information, and much of
the support for System V Release 4. He has also worked heavily on
the Intel 386 and 860 support.
@@ -42473,8 +42946,8 @@ alphabetical order.
series 300.
* Michael Hayes for various thankless work he's done trying to get
- the c30/c40 ports functional. Lots of loop and unroll improvements
- and fixes.
+ the c30/c40 ports functional. Lots of loop and unroll
+ improvements and fixes.
* Dara Hazeghi for wading through myriads of target-specific bug
reports.
@@ -42508,8 +42981,8 @@ alphabetical order.
* Falk Hueffner for working on C and optimization bug reports.
- * Bernardo Innocenti for his m68k work, including merging of ColdFire
- improvements and uClinux support.
+ * Bernardo Innocenti for his m68k work, including merging of
+ ColdFire improvements and uClinux support.
* Christian Iseli for various bug fixes.
@@ -42562,13 +43035,13 @@ alphabetical order.
* Richard Kenner of the New York University Ultracomputer Research
Laboratory wrote the machine descriptions for the AMD 29000, the
DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the
- support for instruction attributes. He also made changes to better
- support RISC processors including changes to common subexpression
- elimination, strength reduction, function calling sequence
- handling, and condition code support, in addition to generalizing
- the code for frame pointer elimination and delay slot scheduling.
- Richard Kenner was also the head maintainer of GCC for several
- years.
+ support for instruction attributes. He also made changes to
+ better support RISC processors including changes to common
+ subexpression elimination, strength reduction, function calling
+ sequence handling, and condition code support, in addition to
+ generalizing the code for frame pointer elimination and delay slot
+ scheduling. Richard Kenner was also the head maintainer of GCC
+ for several years.
* Mumit Khan for various contributions to the Cygwin and Mingw32
ports and maintaining binary releases for Microsoft Windows hosts,
@@ -42594,11 +43067,11 @@ alphabetical order.
* Asher Langton and Mike Kumbera for contributing Cray pointer
support to GNU Fortran, and for other GNU Fortran improvements.
- * Jeff Law for his direction via the steering committee, coordinating
- the entire egcs project and GCC 2.95, rolling out snapshots and
- releases, handling merges from GCC2, reviewing tons of patches that
- might have fallen through the cracks else, and random but extensive
- hacking.
+ * Jeff Law for his direction via the steering committee,
+ coordinating the entire egcs project and GCC 2.95, rolling out
+ snapshots and releases, handling merges from GCC2, reviewing tons
+ of patches that might have fallen through the cracks else, and
+ random but extensive hacking.
* Walter Lee for work on the TILE-Gx and TILEPro ports.
@@ -42627,7 +43100,7 @@ alphabetical order.
* Weiwen Liu for testing and various bug fixes.
- * Manuel Lo'pez-Iba'n~ez for improving '-Wconversion' and many other
+ * Manuel Lo'pez-Iba'n~ez for improving `-Wconversion' and many other
diagnostics fixes and improvements.
* Dave Love for his ongoing work with the Fortran front end and
@@ -42644,13 +43117,14 @@ alphabetical order.
* Greg McGary for random fixes and (someday) bounded pointers.
* Andrew MacLeod for his ongoing work in building a real EH system,
- various code generation improvements, work on the global optimizer,
- etc.
+ various code generation improvements, work on the global
+ optimizer, etc.
* Vladimir Makarov for hacking some ugly i960 problems, PowerPC
- hacking improvements to compile-time performance, overall knowledge
- and direction in the area of instruction scheduling, and design and
- implementation of the automaton based instruction scheduler.
+ hacking improvements to compile-time performance, overall
+ knowledge and direction in the area of instruction scheduling, and
+ design and implementation of the automaton based instruction
+ scheduler.
* Bob Manson for his behind the scenes work on dejagnu.
@@ -42689,7 +43163,7 @@ alphabetical order.
* Mark Mitchell for his direction via the steering committee,
mountains of C++ work, load/store hoisting out of loops, alias
- analysis improvements, ISO C 'restrict' support, and serving as
+ analysis improvements, ISO C `restrict' support, and serving as
release manager from 2000 to 2011.
* Alan Modra for various GNU/Linux bits and testing.
@@ -42699,9 +43173,9 @@ alphabetical order.
* Jason Molenda for major help in the care and feeding of all the
services on the gcc.gnu.org (formerly egcs.cygnus.com)
- machine--mail, web services, ftp services, etc etc. Doing all this
- work on scrap paper and the backs of envelopes would have been...
- difficult.
+ machine--mail, web services, ftp services, etc etc. Doing all
+ this work on scrap paper and the backs of envelopes would have
+ been... difficult.
* Catherine Moore for fixing various ugly problems we have sent her
way, including the haifa bug which was killing the Alpha & PowerPC
@@ -42713,8 +43187,8 @@ alphabetical order.
initial IA-64 port.
* Stephen Moshier contributed the floating point emulator that
- assists in cross-compilation and permits support for floating point
- numbers wider than 64 bits and for ISO C99 support.
+ assists in cross-compilation and permits support for floating
+ point numbers wider than 64 bits and for ISO C99 support.
* Bill Moyer for his behind the scenes work on various issues.
@@ -42737,9 +43211,9 @@ alphabetical order.
* NeXT, Inc. donated the front end that supports the Objective-C
language.
- * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to the
- search engine setup, various documentation fixes and other small
- fixes.
+ * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to
+ the search engine setup, various documentation fixes and other
+ small fixes.
* Geoff Noer for his work on getting cygwin native builds working.
@@ -42747,8 +43221,8 @@ alphabetical order.
tracking web pages, GIMPLE tuples, and assorted fixes.
* David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64,
- FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and related
- infrastructure improvements.
+ FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and
+ related infrastructure improvements.
* Alexandre Oliva for various build infrastructure improvements,
scripts and amazing testing work, including keeping libtool issues
@@ -42760,8 +43234,8 @@ alphabetical order.
* Rainer Orth for random MIPS work, including improvements to GCC's
o32 ABI support, improvements to dejagnu's MIPS support, Java
- configuration clean-ups and porting work, and maintaining the IRIX,
- Solaris 2, and Tru64 UNIX ports.
+ configuration clean-ups and porting work, and maintaining the
+ IRIX, Solaris 2, and Tru64 UNIX ports.
* Hartmut Penner for work on the s390 port.
@@ -42811,7 +43285,7 @@ alphabetical order.
* David Ronis inspired and encouraged Craig to rewrite the G77
documentation in texinfo format by contributing a first pass at a
- translation of the old 'g77-0.5.16/f/DOC' file.
+ translation of the old `g77-0.5.16/f/DOC' file.
* Ken Rose for fixes to GCC's delay slot filling code.
@@ -42843,8 +43317,8 @@ alphabetical order.
* Tobias Schlu"ter for work on GNU Fortran.
* Bernd Schmidt for various code generation improvements and major
- work in the reload pass, serving as release manager for GCC 2.95.3,
- and work on the Blackfin and C6X ports.
+ work in the reload pass, serving as release manager for GCC
+ 2.95.3, and work on the Blackfin and C6X ports.
* Peter Schmid for constant testing of libstdc++--especially
application testing, going above and beyond what was requested for
@@ -42859,7 +43333,7 @@ alphabetical order.
* Dodji Seketeli for numerous C++ bug fixes and debug info
improvements.
- * Tim Shen for major work on '<regex>'.
+ * Tim Shen for major work on `<regex>'.
* Joel Sherrill for his direction via the steering committee, RTEMS
contributions and RTEMS testing.
@@ -42874,8 +43348,8 @@ alphabetical order.
from the LWG (thereby keeping GCC in line with updates from the
ISO).
- * Franz Sirl for his ongoing work with making the PPC port stable for
- GNU/Linux.
+ * Franz Sirl for his ongoing work with making the PPC port stable
+ for GNU/Linux.
* Andrey Slepuhin for assorted AIX hacking.
@@ -42890,12 +43364,12 @@ alphabetical order.
* Randy Smith finished the Sun FPA support.
* Ed Smith-Rowland for his continuous work on libstdc++-v3, special
- functions, '<random>', and various improvements to C++11 features.
+ functions, `<random>', and various improvements to C++11 features.
* Scott Snyder for queue, iterator, istream, and string fixes and
libstdc++ testsuite entries. Also for providing the patch to G77
- to add rudimentary support for 'INTEGER*1', 'INTEGER*2', and
- 'LOGICAL*1'.
+ to add rudimentary support for `INTEGER*1', `INTEGER*2', and
+ `LOGICAL*1'.
* Zdenek Sojka for running automated regression testing of GCC and
reporting numerous bugs.
@@ -42919,8 +43393,8 @@ alphabetical order.
* John Stracke for his Java HTTP protocol fixes.
- * Mike Stump for his Elxsi port, G++ contributions over the years and
- more recently his vxworks contributions
+ * Mike Stump for his Elxsi port, G++ contributions over the years
+ and more recently his vxworks contributions
* Jeff Sturm for Java porting help, bug fixes, and encouragement.
@@ -42974,8 +43448,8 @@ alphabetical order.
* Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML
guidance.
- * Dean Wakerley for converting the install documentation from HTML to
- texinfo in time for GCC 3.0.
+ * Dean Wakerley for converting the install documentation from HTML
+ to texinfo in time for GCC 3.0.
* Krister Walfridsson for random bug fixes.
@@ -42983,8 +43457,8 @@ alphabetical order.
* Stephen M. Webb for time and effort on making libstdc++ shadow
files work with the tricky Solaris 8+ headers, and for pushing the
- build-time header tree. Also, for starting and driving the
- '<regex>' effort.
+ build-time header tree. Also, for starting and driving the
+ `<regex>' effort.
* John Wehle for various improvements for the x86 code generator,
related infrastructure improvements to help x86 code generation,
@@ -43006,8 +43480,8 @@ alphabetical order.
* Bob Wilson from Tensilica, Inc. for the Xtensa port.
* Jim Wilson for his direction via the steering committee, tackling
- hard problems in various places that nobody else wanted to work on,
- strength reduction and other loop optimizations.
+ hard problems in various places that nobody else wanted to work
+ on, strength reduction and other loop optimizations.
* Paul Woegerer and Tal Agmon for the CRX port.
@@ -43030,6 +43504,7 @@ alphabetical order.
* Gilles Zunino for help porting Java to Irix.
+
The following people are recognized for their contributions to GNAT,
the Ada front end of GCC:
* Bernard Banner
@@ -43126,102 +43601,102 @@ the Ada front end of GCC:
* Samuel Tardieu
+
The following people are recognized for their contributions of new
features, bug reports, testing and integration of classpath/libgcj for
GCC version 4.1:
- * Lillian Angel for 'JTree' implementation and lots Free Swing
+ * Lillian Angel for `JTree' implementation and lots Free Swing
additions and bug fixes.
- * Wolfgang Baer for 'GapContent' bug fixes.
+ * Wolfgang Baer for `GapContent' bug fixes.
- * Anthony Balkissoon for 'JList', Free Swing 1.5 updates and mouse
- event fixes, lots of Free Swing work including 'JTable' editing.
+ * Anthony Balkissoon for `JList', Free Swing 1.5 updates and mouse
+ event fixes, lots of Free Swing work including `JTable' editing.
* Stuart Ballard for RMI constant fixes.
- * Goffredo Baroncelli for 'HTTPURLConnection' fixes.
+ * Goffredo Baroncelli for `HTTPURLConnection' fixes.
- * Gary Benson for 'MessageFormat' fixes.
+ * Gary Benson for `MessageFormat' fixes.
- * Daniel Bonniot for 'Serialization' fixes.
+ * Daniel Bonniot for `Serialization' fixes.
- * Chris Burdess for lots of gnu.xml and http protocol fixes, 'StAX'
- and 'DOM xml:id' support.
+ * Chris Burdess for lots of gnu.xml and http protocol fixes, `StAX'
+ and `DOM xml:id' support.
- * Ka-Hing Cheung for 'TreePath' and 'TreeSelection' fixes.
+ * Ka-Hing Cheung for `TreePath' and `TreeSelection' fixes.
* Archie Cobbs for build fixes, VM interface updates,
- 'URLClassLoader' updates.
+ `URLClassLoader' updates.
* Kelley Cook for build fixes.
- * Martin Cordova for Suggestions for better 'SocketTimeoutException'.
+ * Martin Cordova for Suggestions for better `SocketTimeoutException'.
- * David Daney for 'BitSet' bug fixes, 'HttpURLConnection' rewrite and
- improvements.
+ * David Daney for `BitSet' bug fixes, `HttpURLConnection' rewrite
+ and improvements.
* Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo
- 2D support. Lots of imageio framework additions, lots of AWT and
+ 2D support. Lots of imageio framework additions, lots of AWT and
Free Swing bug fixes.
- * Jeroen Frijters for 'ClassLoader' and nio cleanups, serialization
- fixes, better 'Proxy' support, bug fixes and IKVM integration.
+ * Jeroen Frijters for `ClassLoader' and nio cleanups, serialization
+ fixes, better `Proxy' support, bug fixes and IKVM integration.
- * Santiago Gala for 'AccessControlContext' fixes.
+ * Santiago Gala for `AccessControlContext' fixes.
- * Nicolas Geoffray for 'VMClassLoader' and 'AccessController'
+ * Nicolas Geoffray for `VMClassLoader' and `AccessController'
improvements.
- * David Gilbert for 'basic' and 'metal' icon and plaf support and
+ * David Gilbert for `basic' and `metal' icon and plaf support and
lots of documenting, Lots of Free Swing and metal theme additions.
- 'MetalIconFactory' implementation.
+ `MetalIconFactory' implementation.
- * Anthony Green for 'MIDI' framework, 'ALSA' and 'DSSI' providers.
+ * Anthony Green for `MIDI' framework, `ALSA' and `DSSI' providers.
- * Andrew Haley for 'Serialization' and 'URLClassLoader' fixes, gcj
+ * Andrew Haley for `Serialization' and `URLClassLoader' fixes, gcj
build speedups.
- * Kim Ho for 'JFileChooser' implementation.
+ * Kim Ho for `JFileChooser' implementation.
- * Andrew John Hughes for 'Locale' and net fixes, URI RFC2986 updates,
- 'Serialization' fixes, 'Properties' XML support and generic branch
- work, VMIntegration guide update.
+ * Andrew John Hughes for `Locale' and net fixes, URI RFC2986
+ updates, `Serialization' fixes, `Properties' XML support and
+ generic branch work, VMIntegration guide update.
- * Bastiaan Huisman for 'TimeZone' bug fixing.
+ * Bastiaan Huisman for `TimeZone' bug fixing.
* Andreas Jaeger for mprec updates.
- * Paul Jenner for better '-Werror' support.
+ * Paul Jenner for better `-Werror' support.
- * Ito Kazumitsu for 'NetworkInterface' implementation and updates.
+ * Ito Kazumitsu for `NetworkInterface' implementation and updates.
- * Roman Kennke for 'BoxLayout', 'GrayFilter' and 'SplitPane', plus
- bug fixes all over. Lots of Free Swing work including styled text.
+ * Roman Kennke for `BoxLayout', `GrayFilter' and `SplitPane', plus
+ bug fixes all over. Lots of Free Swing work including styled text.
- * Simon Kitching for 'String' cleanups and optimization suggestions.
+ * Simon Kitching for `String' cleanups and optimization suggestions.
- * Michael Koch for configuration fixes, 'Locale' updates, bug and
+ * Michael Koch for configuration fixes, `Locale' updates, bug and
build fixes.
* Guilhem Lavaux for configuration, thread and channel fixes and
- Kaffe integration. JCL native 'Pointer' updates. Logger bug
- fixes.
+ Kaffe integration. JCL native `Pointer' updates. Logger bug fixes.
* David Lichteblau for JCL support library global/local reference
cleanups.
* Aaron Luchko for JDWP updates and documentation fixes.
- * Ziga Mahkovec for 'Graphics2D' upgraded to Cairo 0.5 and new regex
+ * Ziga Mahkovec for `Graphics2D' upgraded to Cairo 0.5 and new regex
features.
- * Sven de Marothy for BMP imageio support, CSS and 'TextLayout'
- fixes. 'GtkImage' rewrite, 2D, awt, free swing and date/time fixes
+ * Sven de Marothy for BMP imageio support, CSS and `TextLayout'
+ fixes. `GtkImage' rewrite, 2D, awt, free swing and date/time fixes
and implementing the Qt4 peers.
- * Casey Marshall for crypto algorithm fixes, 'FileChannel' lock,
- 'SystemLogger' and 'FileHandler' rotate implementations, NIO
- 'FileChannel.map' support, security and policy updates.
+ * Casey Marshall for crypto algorithm fixes, `FileChannel' lock,
+ `SystemLogger' and `FileHandler' rotate implementations, NIO
+ `FileChannel.map' support, security and policy updates.
* Bryce McKinlay for RMI work.
@@ -43232,45 +43707,46 @@ GCC version 4.1:
* Rainer Orth for build fixes.
- * Andrew Overholt for 'File' locking fixes.
+ * Andrew Overholt for `File' locking fixes.
- * Ingo Proetel for 'Image', 'Logger' and 'URLClassLoader' updates.
+ * Ingo Proetel for `Image', `Logger' and `URLClassLoader' updates.
- * Olga Rodimina for 'MenuSelectionManager' implementation.
+ * Olga Rodimina for `MenuSelectionManager' implementation.
- * Jan Roehrich for 'BasicTreeUI' and 'JTree' fixes.
+ * Jan Roehrich for `BasicTreeUI' and `JTree' fixes.
* Julian Scheid for documentation updates and gjdoc support.
* Christian Schlichtherle for zip fixes and cleanups.
* Robert Schuster for documentation updates and beans fixes,
- 'TreeNode' enumerations and 'ActionCommand' and various fixes, XML
+ `TreeNode' enumerations and `ActionCommand' and various fixes, XML
and URL, AWT and Free Swing bug fixes.
* Keith Seitz for lots of JDWP work.
* Christian Thalinger for 64-bit cleanups, Configuration and VM
- interface fixes and 'CACAO' integration, 'fdlibm' updates.
+ interface fixes and `CACAO' integration, `fdlibm' updates.
- * Gael Thomas for 'VMClassLoader' boot packages support suggestions.
+ * Gael Thomas for `VMClassLoader' boot packages support suggestions.
- * Andreas Tobler for Darwin and Solaris testing and fixing, 'Qt4'
- support for Darwin/OS X, 'Graphics2D' support, 'gtk+' updates.
+ * Andreas Tobler for Darwin and Solaris testing and fixing, `Qt4'
+ support for Darwin/OS X, `Graphics2D' support, `gtk+' updates.
- * Dalibor Topic for better 'DEBUG' support, build cleanups and Kaffe
- integration. 'Qt4' build infrastructure, 'SHA1PRNG' and
- 'GdkPixbugDecoder' updates.
+ * Dalibor Topic for better `DEBUG' support, build cleanups and Kaffe
+ integration. `Qt4' build infrastructure, `SHA1PRNG' and
+ `GdkPixbugDecoder' updates.
* Tom Tromey for Eclipse integration, generics work, lots of bug
fixes and gcj integration including coordinating The Big Merge.
* Mark Wielaard for bug fixes, packaging and release management,
- 'Clipboard' implementation, system call interrupts and network
- timeouts and 'GdkPixpufDecoder' fixes.
+ `Clipboard' implementation, system call interrupts and network
+ timeouts and `GdkPixpufDecoder' fixes.
+
- In addition to the above, all of which also contributed time and energy
-in testing GCC, we would like to thank the following for their
+ In addition to the above, all of which also contributed time and
+energy in testing GCC, we would like to thank the following for their
contributions to testing:
* Michael Abd-El-Malek
@@ -43439,9 +43915,9 @@ File: gccint.info, Node: Option Index, Next: Concept Index, Prev: Contributor
Option Index
************
-GCC's command line options are indexed here without any initial '-' or
-'--'. Where an option has both positive and negative forms (such as
-'-fOPTION' and '-fno-OPTION'), relevant entries in the manual are
+GCC's command line options are indexed here without any initial `-' or
+`--'. Where an option has both positive and negative forms (such as
+`-fOPTION' and `-fno-OPTION'), relevant entries in the manual are
indexed under the most appropriate form; it may sometimes be useful to
look up both forms.
@@ -43464,3604 +43940,3577 @@ Concept Index
* Menu:
-* '!' in constraint: Multi-Alternative. (line 47)
-* '#' in constraint: Modifiers. (line 78)
-* '#' in template: Output Template. (line 66)
+* ! in constraint: Multi-Alternative. (line 47)
+* # in constraint: Modifiers. (line 78)
+* # in template: Output Template. (line 66)
* #pragma: Misc. (line 387)
-* '$' in constraint: Multi-Alternative. (line 56)
-* '%' in constraint: Modifiers. (line 52)
+* $ in constraint: Multi-Alternative. (line 56)
+* % in constraint: Modifiers. (line 52)
* % in GTY option: GTY Options. (line 18)
-* '%' in template: Output Template. (line 6)
-* '&' in constraint: Modifiers. (line 25)
-* (gimple_stmt_iterator: GIMPLE API. (line 30)
+* % in template: Output Template. (line 6)
+* & in constraint: Modifiers. (line 25)
+* (: GIMPLE API. (line 31)
* (nil): RTL Objects. (line 73)
-* '*' in constraint: Modifiers. (line 83)
-* '*' in template: Output Statement. (line 29)
-* *gimple_build_asm_vec: 'GIMPLE_ASM'. (line 6)
-* *gimple_build_assign: 'GIMPLE_ASSIGN'. (line 6)
-* *gimple_build_assign <1>: 'GIMPLE_ASSIGN'. (line 18)
-* *gimple_build_assign <2>: 'GIMPLE_ASSIGN'. (line 29)
-* *gimple_build_assign <3>: 'GIMPLE_ASSIGN'. (line 35)
-* *gimple_build_bind: 'GIMPLE_BIND'. (line 6)
-* *gimple_build_call: 'GIMPLE_CALL'. (line 6)
-* *gimple_build_call_from_tree: 'GIMPLE_CALL'. (line 15)
-* *gimple_build_call_vec: 'GIMPLE_CALL'. (line 23)
-* *gimple_build_catch: 'GIMPLE_CATCH'. (line 6)
-* *gimple_build_cond: 'GIMPLE_COND'. (line 6)
-* *gimple_build_cond_from_tree: 'GIMPLE_COND'. (line 14)
-* *gimple_build_debug_bind: 'GIMPLE_DEBUG'. (line 6)
-* *gimple_build_eh_filter: 'GIMPLE_EH_FILTER'. (line 6)
-* *gimple_build_goto: 'GIMPLE_GOTO'. (line 6)
-* *gimple_build_label: 'GIMPLE_LABEL'. (line 6)
-* *gimple_build_omp_atomic_load: 'GIMPLE_OMP_ATOMIC_LOAD'.
- (line 6)
-* *gimple_build_omp_atomic_store: 'GIMPLE_OMP_ATOMIC_STORE'.
- (line 6)
-* *gimple_build_omp_continue: 'GIMPLE_OMP_CONTINUE'.
- (line 6)
-* *gimple_build_omp_critical: 'GIMPLE_OMP_CRITICAL'.
- (line 6)
-* *gimple_build_omp_for: 'GIMPLE_OMP_FOR'. (line 6)
-* *gimple_build_omp_parallel: 'GIMPLE_OMP_PARALLEL'.
- (line 6)
-* *gimple_build_omp_sections: 'GIMPLE_OMP_SECTIONS'.
- (line 6)
-* *gimple_build_omp_single: 'GIMPLE_OMP_SINGLE'.
- (line 6)
-* *gimple_build_resx: 'GIMPLE_RESX'. (line 6)
-* *gimple_build_return: 'GIMPLE_RETURN'. (line 6)
-* *gimple_build_switch: 'GIMPLE_SWITCH'. (line 6)
-* *gimple_build_try: 'GIMPLE_TRY'. (line 6)
-* '+' in constraint: Modifiers. (line 12)
-* '-fsection-anchors': Special Accessors. (line 117)
-* '-fsection-anchors' <1>: Anchored Addresses. (line 6)
-* '/c' in RTL dump: Flags. (line 221)
-* '/f' in RTL dump: Flags. (line 229)
-* '/i' in RTL dump: Flags. (line 274)
-* '/j' in RTL dump: Flags. (line 286)
-* '/s' in RTL dump: Flags. (line 245)
-* '/u' in RTL dump: Flags. (line 296)
-* '/v' in RTL dump: Flags. (line 328)
-* '0' in constraint: Simple Constraints. (line 128)
-* '<' in constraint: Simple Constraints. (line 47)
-* '=' in constraint: Modifiers. (line 8)
-* '>' in constraint: Simple Constraints. (line 59)
-* '?' in constraint: Multi-Alternative. (line 41)
+* * in constraint: Modifiers. (line 83)
+* * in template: Output Statement. (line 29)
+* *gimple_build_asm_vec: GIMPLE_ASM. (line 9)
+* *gimple_build_assign: GIMPLE_ASSIGN. (line 7)
+* *gimple_build_bind: GIMPLE_BIND. (line 8)
+* *gimple_build_call: GIMPLE_CALL. (line 8)
+* *gimple_build_call_from_tree: GIMPLE_CALL. (line 16)
+* *gimple_build_call_vec: GIMPLE_CALL. (line 25)
+* *gimple_build_catch: GIMPLE_CATCH. (line 8)
+* *gimple_build_cond: GIMPLE_COND. (line 8)
+* *gimple_build_cond_from_tree: GIMPLE_COND. (line 16)
+* *gimple_build_debug_bind: GIMPLE_DEBUG. (line 8)
+* *gimple_build_eh_filter: GIMPLE_EH_FILTER. (line 8)
+* *gimple_build_goto: GIMPLE_GOTO. (line 7)
+* *gimple_build_label: GIMPLE_LABEL. (line 7)
+* *gimple_build_omp_atomic_load: GIMPLE_OMP_ATOMIC_LOAD.
+ (line 8)
+* *gimple_build_omp_atomic_store: GIMPLE_OMP_ATOMIC_STORE.
+ (line 8)
+* *gimple_build_omp_continue: GIMPLE_OMP_CONTINUE.
+ (line 8)
+* *gimple_build_omp_critical: GIMPLE_OMP_CRITICAL.
+ (line 8)
+* *gimple_build_omp_for: GIMPLE_OMP_FOR. (line 9)
+* *gimple_build_omp_parallel: GIMPLE_OMP_PARALLEL.
+ (line 8)
+* *gimple_build_omp_sections: GIMPLE_OMP_SECTIONS.
+ (line 8)
+* *gimple_build_omp_single: GIMPLE_OMP_SINGLE. (line 8)
+* *gimple_build_resx: GIMPLE_RESX. (line 7)
+* *gimple_build_return: GIMPLE_RETURN. (line 7)
+* *gimple_build_switch: GIMPLE_SWITCH. (line 8)
+* *gimple_build_try: GIMPLE_TRY. (line 8)
+* + in constraint: Modifiers. (line 12)
+* -fsection-anchors <1>: Anchored Addresses. (line 6)
+* -fsection-anchors: Special Accessors. (line 120)
+* /c in RTL dump: Flags. (line 221)
+* /f in RTL dump: Flags. (line 229)
+* /i in RTL dump: Flags. (line 274)
+* /j in RTL dump: Flags. (line 286)
+* /s in RTL dump: Flags. (line 245)
+* /u in RTL dump: Flags. (line 296)
+* /v in RTL dump: Flags. (line 328)
+* 0 in constraint: Simple Constraints. (line 130)
+* < in constraint: Simple Constraints. (line 48)
+* = in constraint: Modifiers. (line 8)
+* > in constraint: Simple Constraints. (line 61)
+* ? in constraint: Multi-Alternative. (line 41)
* \: Output Template. (line 46)
-* '^' in constraint: Multi-Alternative. (line 52)
+* ^ in constraint: Multi-Alternative. (line 52)
* __absvdi2: Integer library routines.
- (line 106)
+ (line 107)
* __absvsi2: Integer library routines.
- (line 105)
+ (line 106)
* __addda3: Fixed-point fractional library routines.
- (line 44)
+ (line 45)
* __adddf3: Soft float library routines.
- (line 22)
+ (line 23)
* __adddq3: Fixed-point fractional library routines.
- (line 31)
+ (line 33)
* __addha3: Fixed-point fractional library routines.
- (line 41)
+ (line 43)
* __addhq3: Fixed-point fractional library routines.
- (line 29)
+ (line 30)
* __addqq3: Fixed-point fractional library routines.
- (line 27)
+ (line 29)
* __addsa3: Fixed-point fractional library routines.
- (line 43)
+ (line 44)
* __addsf3: Soft float library routines.
- (line 21)
+ (line 22)
* __addsq3: Fixed-point fractional library routines.
- (line 30)
+ (line 31)
* __addta3: Fixed-point fractional library routines.
- (line 45)
+ (line 47)
* __addtf3: Soft float library routines.
- (line 23)
+ (line 25)
* __adduda3: Fixed-point fractional library routines.
- (line 51)
+ (line 53)
* __addudq3: Fixed-point fractional library routines.
- (line 39)
+ (line 41)
* __adduha3: Fixed-point fractional library routines.
- (line 47)
+ (line 49)
* __adduhq3: Fixed-point fractional library routines.
- (line 35)
+ (line 37)
* __adduqq3: Fixed-point fractional library routines.
- (line 33)
+ (line 35)
* __addusa3: Fixed-point fractional library routines.
- (line 49)
+ (line 51)
* __addusq3: Fixed-point fractional library routines.
- (line 37)
+ (line 39)
* __adduta3: Fixed-point fractional library routines.
- (line 53)
+ (line 55)
* __addvdi3: Integer library routines.
- (line 110)
+ (line 111)
* __addvsi3: Integer library routines.
- (line 109)
+ (line 110)
* __addxf3: Soft float library routines.
- (line 25)
+ (line 27)
* __ashlda3: Fixed-point fractional library routines.
- (line 350)
+ (line 351)
* __ashldi3: Integer library routines.
- (line 13)
+ (line 14)
* __ashldq3: Fixed-point fractional library routines.
- (line 338)
+ (line 340)
* __ashlha3: Fixed-point fractional library routines.
- (line 348)
+ (line 349)
* __ashlhq3: Fixed-point fractional library routines.
- (line 336)
+ (line 337)
* __ashlqq3: Fixed-point fractional library routines.
- (line 335)
+ (line 336)
* __ashlsa3: Fixed-point fractional library routines.
- (line 349)
+ (line 350)
* __ashlsi3: Integer library routines.
- (line 12)
+ (line 13)
* __ashlsq3: Fixed-point fractional library routines.
- (line 337)
+ (line 338)
* __ashlta3: Fixed-point fractional library routines.
- (line 351)
+ (line 353)
* __ashlti3: Integer library routines.
- (line 14)
+ (line 15)
* __ashluda3: Fixed-point fractional library routines.
- (line 357)
+ (line 359)
* __ashludq3: Fixed-point fractional library routines.
- (line 346)
+ (line 348)
* __ashluha3: Fixed-point fractional library routines.
- (line 353)
+ (line 355)
* __ashluhq3: Fixed-point fractional library routines.
- (line 342)
+ (line 344)
* __ashluqq3: Fixed-point fractional library routines.
- (line 340)
+ (line 342)
* __ashlusa3: Fixed-point fractional library routines.
- (line 355)
+ (line 357)
* __ashlusq3: Fixed-point fractional library routines.
- (line 344)
+ (line 346)
* __ashluta3: Fixed-point fractional library routines.
- (line 359)
+ (line 361)
* __ashrda3: Fixed-point fractional library routines.
- (line 370)
+ (line 371)
* __ashrdi3: Integer library routines.
- (line 18)
+ (line 19)
* __ashrdq3: Fixed-point fractional library routines.
- (line 366)
-* __ashrha3: Fixed-point fractional library routines.
(line 368)
+* __ashrha3: Fixed-point fractional library routines.
+ (line 369)
* __ashrhq3: Fixed-point fractional library routines.
- (line 364)
+ (line 365)
* __ashrqq3: Fixed-point fractional library routines.
- (line 363)
+ (line 364)
* __ashrsa3: Fixed-point fractional library routines.
- (line 369)
+ (line 370)
* __ashrsi3: Integer library routines.
- (line 17)
+ (line 18)
* __ashrsq3: Fixed-point fractional library routines.
- (line 365)
+ (line 366)
* __ashrta3: Fixed-point fractional library routines.
- (line 371)
+ (line 373)
* __ashrti3: Integer library routines.
- (line 19)
+ (line 20)
* __bid_adddd3: Decimal float library routines.
- (line 23)
+ (line 25)
* __bid_addsd3: Decimal float library routines.
- (line 19)
+ (line 21)
* __bid_addtd3: Decimal float library routines.
- (line 27)
+ (line 29)
* __bid_divdd3: Decimal float library routines.
- (line 66)
+ (line 68)
* __bid_divsd3: Decimal float library routines.
- (line 62)
+ (line 64)
* __bid_divtd3: Decimal float library routines.
- (line 70)
+ (line 72)
* __bid_eqdd2: Decimal float library routines.
- (line 258)
+ (line 259)
* __bid_eqsd2: Decimal float library routines.
- (line 256)
+ (line 257)
* __bid_eqtd2: Decimal float library routines.
- (line 260)
+ (line 261)
* __bid_extendddtd2: Decimal float library routines.
- (line 91)
+ (line 92)
* __bid_extendddtf: Decimal float library routines.
- (line 139)
+ (line 140)
* __bid_extendddxf: Decimal float library routines.
- (line 133)
+ (line 134)
* __bid_extenddfdd: Decimal float library routines.
- (line 146)
+ (line 147)
* __bid_extenddftd: Decimal float library routines.
- (line 106)
+ (line 107)
* __bid_extendsddd2: Decimal float library routines.
- (line 87)
+ (line 88)
* __bid_extendsddf: Decimal float library routines.
- (line 127)
+ (line 128)
* __bid_extendsdtd2: Decimal float library routines.
- (line 89)
+ (line 90)
* __bid_extendsdtf: Decimal float library routines.
- (line 137)
+ (line 138)
* __bid_extendsdxf: Decimal float library routines.
- (line 131)
+ (line 132)
* __bid_extendsfdd: Decimal float library routines.
- (line 102)
+ (line 103)
* __bid_extendsfsd: Decimal float library routines.
- (line 144)
+ (line 145)
* __bid_extendsftd: Decimal float library routines.
- (line 104)
+ (line 105)
* __bid_extendtftd: Decimal float library routines.
- (line 148)
+ (line 149)
* __bid_extendxftd: Decimal float library routines.
- (line 108)
+ (line 109)
* __bid_fixdddi: Decimal float library routines.
- (line 169)
+ (line 170)
* __bid_fixddsi: Decimal float library routines.
- (line 161)
+ (line 162)
* __bid_fixsddi: Decimal float library routines.
- (line 167)
+ (line 168)
* __bid_fixsdsi: Decimal float library routines.
- (line 159)
+ (line 160)
* __bid_fixtddi: Decimal float library routines.
- (line 171)
+ (line 172)
* __bid_fixtdsi: Decimal float library routines.
- (line 163)
+ (line 164)
* __bid_fixunsdddi: Decimal float library routines.
- (line 186)
+ (line 187)
* __bid_fixunsddsi: Decimal float library routines.
- (line 177)
+ (line 178)
* __bid_fixunssddi: Decimal float library routines.
- (line 184)
+ (line 185)
* __bid_fixunssdsi: Decimal float library routines.
- (line 175)
+ (line 176)
* __bid_fixunstddi: Decimal float library routines.
- (line 188)
+ (line 189)
* __bid_fixunstdsi: Decimal float library routines.
- (line 179)
+ (line 180)
* __bid_floatdidd: Decimal float library routines.
- (line 204)
+ (line 205)
* __bid_floatdisd: Decimal float library routines.
- (line 202)
+ (line 203)
* __bid_floatditd: Decimal float library routines.
- (line 206)
+ (line 207)
* __bid_floatsidd: Decimal float library routines.
- (line 195)
+ (line 196)
* __bid_floatsisd: Decimal float library routines.
- (line 193)
+ (line 194)
* __bid_floatsitd: Decimal float library routines.
- (line 197)
+ (line 198)
* __bid_floatunsdidd: Decimal float library routines.
- (line 222)
+ (line 223)
* __bid_floatunsdisd: Decimal float library routines.
- (line 220)
+ (line 221)
* __bid_floatunsditd: Decimal float library routines.
- (line 224)
+ (line 225)
* __bid_floatunssidd: Decimal float library routines.
- (line 213)
+ (line 214)
* __bid_floatunssisd: Decimal float library routines.
- (line 211)
+ (line 212)
* __bid_floatunssitd: Decimal float library routines.
- (line 215)
+ (line 216)
* __bid_gedd2: Decimal float library routines.
- (line 276)
+ (line 277)
* __bid_gesd2: Decimal float library routines.
- (line 274)
+ (line 275)
* __bid_getd2: Decimal float library routines.
- (line 278)
+ (line 279)
* __bid_gtdd2: Decimal float library routines.
- (line 303)
+ (line 304)
* __bid_gtsd2: Decimal float library routines.
- (line 301)
+ (line 302)
* __bid_gttd2: Decimal float library routines.
- (line 305)
+ (line 306)
* __bid_ledd2: Decimal float library routines.
- (line 294)
+ (line 295)
* __bid_lesd2: Decimal float library routines.
- (line 292)
+ (line 293)
* __bid_letd2: Decimal float library routines.
- (line 296)
+ (line 297)
* __bid_ltdd2: Decimal float library routines.
- (line 285)
+ (line 286)
* __bid_ltsd2: Decimal float library routines.
- (line 283)
+ (line 284)
* __bid_lttd2: Decimal float library routines.
- (line 287)
+ (line 288)
* __bid_muldd3: Decimal float library routines.
- (line 52)
+ (line 54)
* __bid_mulsd3: Decimal float library routines.
- (line 48)
+ (line 50)
* __bid_multd3: Decimal float library routines.
- (line 56)
+ (line 58)
* __bid_nedd2: Decimal float library routines.
- (line 267)
+ (line 268)
* __bid_negdd2: Decimal float library routines.
- (line 77)
+ (line 78)
* __bid_negsd2: Decimal float library routines.
- (line 75)
+ (line 76)
* __bid_negtd2: Decimal float library routines.
- (line 79)
+ (line 80)
* __bid_nesd2: Decimal float library routines.
- (line 265)
+ (line 266)
* __bid_netd2: Decimal float library routines.
- (line 269)
+ (line 270)
* __bid_subdd3: Decimal float library routines.
- (line 37)
+ (line 39)
* __bid_subsd3: Decimal float library routines.
- (line 33)
+ (line 35)
* __bid_subtd3: Decimal float library routines.
- (line 41)
+ (line 43)
* __bid_truncdddf: Decimal float library routines.
- (line 152)
+ (line 153)
* __bid_truncddsd2: Decimal float library routines.
- (line 93)
+ (line 94)
* __bid_truncddsf: Decimal float library routines.
- (line 123)
+ (line 124)
* __bid_truncdfsd: Decimal float library routines.
- (line 110)
+ (line 111)
* __bid_truncsdsf: Decimal float library routines.
- (line 150)
+ (line 151)
* __bid_trunctddd2: Decimal float library routines.
- (line 97)
+ (line 98)
* __bid_trunctddf: Decimal float library routines.
- (line 129)
+ (line 130)
* __bid_trunctdsd2: Decimal float library routines.
- (line 95)
+ (line 96)
* __bid_trunctdsf: Decimal float library routines.
- (line 125)
+ (line 126)
* __bid_trunctdtf: Decimal float library routines.
- (line 154)
+ (line 155)
* __bid_trunctdxf: Decimal float library routines.
- (line 135)
+ (line 136)
* __bid_trunctfdd: Decimal float library routines.
- (line 118)
+ (line 119)
* __bid_trunctfsd: Decimal float library routines.
- (line 114)
+ (line 115)
* __bid_truncxfdd: Decimal float library routines.
- (line 116)
+ (line 117)
* __bid_truncxfsd: Decimal float library routines.
- (line 112)
+ (line 113)
* __bid_unorddd2: Decimal float library routines.
- (line 234)
+ (line 235)
* __bid_unordsd2: Decimal float library routines.
- (line 232)
+ (line 233)
* __bid_unordtd2: Decimal float library routines.
- (line 236)
+ (line 237)
* __bswapdi2: Integer library routines.
- (line 161)
+ (line 162)
* __bswapsi2: Integer library routines.
- (line 160)
-* __builtin_classify_type: Varargs. (line 48)
-* __builtin_next_arg: Varargs. (line 39)
-* __builtin_saveregs: Varargs. (line 22)
-* __chkp_bndcl: Misc. (line 649)
-* __chkp_bndcu: Misc. (line 655)
-* __chkp_bndldx: Misc. (line 643)
-* __chkp_bndmk: Misc. (line 630)
-* __chkp_bndret: Misc. (line 661)
-* __chkp_bndstx: Misc. (line 637)
-* __chkp_intersect: Misc. (line 667)
-* __chkp_narrow: Misc. (line 672)
-* __chkp_sizeof: Misc. (line 678)
+ (line 161)
+* __builtin_classify_type: Varargs. (line 51)
+* __builtin_next_arg: Varargs. (line 42)
+* __builtin_saveregs: Varargs. (line 24)
+* __chkp_bndcl: Misc. (line 651)
+* __chkp_bndcu: Misc. (line 657)
+* __chkp_bndldx: Misc. (line 645)
+* __chkp_bndmk: Misc. (line 632)
+* __chkp_bndret: Misc. (line 662)
+* __chkp_bndstx: Misc. (line 639)
+* __chkp_intersect: Misc. (line 669)
+* __chkp_narrow: Misc. (line 674)
+* __chkp_sizeof: Misc. (line 679)
* __clear_cache: Miscellaneous routines.
- (line 9)
+ (line 10)
* __clzdi2: Integer library routines.
- (line 130)
+ (line 131)
* __clzsi2: Integer library routines.
- (line 129)
+ (line 130)
* __clzti2: Integer library routines.
- (line 131)
+ (line 132)
* __cmpda2: Fixed-point fractional library routines.
- (line 450)
+ (line 451)
* __cmpdf2: Soft float library routines.
- (line 163)
+ (line 164)
* __cmpdi2: Integer library routines.
- (line 86)
+ (line 87)
* __cmpdq2: Fixed-point fractional library routines.
- (line 439)
+ (line 441)
* __cmpha2: Fixed-point fractional library routines.
- (line 448)
+ (line 449)
* __cmphq2: Fixed-point fractional library routines.
- (line 437)
+ (line 438)
* __cmpqq2: Fixed-point fractional library routines.
- (line 436)
+ (line 437)
* __cmpsa2: Fixed-point fractional library routines.
- (line 449)
+ (line 450)
* __cmpsf2: Soft float library routines.
- (line 162)
+ (line 163)
* __cmpsq2: Fixed-point fractional library routines.
- (line 438)
+ (line 439)
* __cmpta2: Fixed-point fractional library routines.
- (line 451)
+ (line 453)
* __cmptf2: Soft float library routines.
- (line 164)
+ (line 165)
* __cmpti2: Integer library routines.
- (line 87)
+ (line 88)
* __cmpuda2: Fixed-point fractional library routines.
- (line 456)
+ (line 458)
* __cmpudq2: Fixed-point fractional library routines.
- (line 446)
+ (line 448)
* __cmpuha2: Fixed-point fractional library routines.
- (line 453)
+ (line 455)
* __cmpuhq2: Fixed-point fractional library routines.
- (line 443)
+ (line 444)
* __cmpuqq2: Fixed-point fractional library routines.
- (line 441)
+ (line 443)
* __cmpusa2: Fixed-point fractional library routines.
- (line 455)
+ (line 456)
* __cmpusq2: Fixed-point fractional library routines.
- (line 444)
+ (line 446)
* __cmputa2: Fixed-point fractional library routines.
- (line 458)
+ (line 460)
* __CTOR_LIST__: Initialization. (line 25)
* __ctzdi2: Integer library routines.
- (line 137)
+ (line 138)
* __ctzsi2: Integer library routines.
- (line 136)
+ (line 137)
* __ctzti2: Integer library routines.
- (line 138)
+ (line 139)
* __divda3: Fixed-point fractional library routines.
- (line 226)
+ (line 227)
* __divdc3: Soft float library routines.
- (line 250)
+ (line 252)
* __divdf3: Soft float library routines.
- (line 47)
+ (line 48)
* __divdi3: Integer library routines.
- (line 24)
+ (line 25)
* __divdq3: Fixed-point fractional library routines.
- (line 221)
-* __divha3: Fixed-point fractional library routines.
(line 223)
+* __divha3: Fixed-point fractional library routines.
+ (line 225)
* __divhq3: Fixed-point fractional library routines.
- (line 219)
+ (line 220)
* __divqq3: Fixed-point fractional library routines.
- (line 217)
+ (line 219)
* __divsa3: Fixed-point fractional library routines.
- (line 225)
+ (line 226)
* __divsc3: Soft float library routines.
- (line 248)
+ (line 250)
* __divsf3: Soft float library routines.
- (line 46)
+ (line 47)
* __divsi3: Integer library routines.
- (line 23)
+ (line 24)
* __divsq3: Fixed-point fractional library routines.
- (line 220)
+ (line 221)
* __divta3: Fixed-point fractional library routines.
- (line 227)
+ (line 229)
* __divtc3: Soft float library routines.
- (line 252)
+ (line 254)
* __divtf3: Soft float library routines.
- (line 48)
+ (line 50)
* __divti3: Integer library routines.
- (line 25)
+ (line 26)
* __divxc3: Soft float library routines.
- (line 254)
+ (line 256)
* __divxf3: Soft float library routines.
- (line 50)
+ (line 52)
* __dpd_adddd3: Decimal float library routines.
- (line 21)
+ (line 23)
* __dpd_addsd3: Decimal float library routines.
- (line 17)
+ (line 19)
* __dpd_addtd3: Decimal float library routines.
- (line 25)
+ (line 27)
* __dpd_divdd3: Decimal float library routines.
- (line 64)
+ (line 66)
* __dpd_divsd3: Decimal float library routines.
- (line 60)
+ (line 62)
* __dpd_divtd3: Decimal float library routines.
- (line 68)
+ (line 70)
* __dpd_eqdd2: Decimal float library routines.
- (line 257)
+ (line 258)
* __dpd_eqsd2: Decimal float library routines.
- (line 255)
+ (line 256)
* __dpd_eqtd2: Decimal float library routines.
- (line 259)
+ (line 260)
* __dpd_extendddtd2: Decimal float library routines.
- (line 90)
+ (line 91)
* __dpd_extendddtf: Decimal float library routines.
- (line 138)
+ (line 139)
* __dpd_extendddxf: Decimal float library routines.
- (line 132)
+ (line 133)
* __dpd_extenddfdd: Decimal float library routines.
- (line 145)
+ (line 146)
* __dpd_extenddftd: Decimal float library routines.
- (line 105)
+ (line 106)
* __dpd_extendsddd2: Decimal float library routines.
- (line 86)
+ (line 87)
* __dpd_extendsddf: Decimal float library routines.
- (line 126)
+ (line 127)
* __dpd_extendsdtd2: Decimal float library routines.
- (line 88)
+ (line 89)
* __dpd_extendsdtf: Decimal float library routines.
- (line 136)
+ (line 137)
* __dpd_extendsdxf: Decimal float library routines.
- (line 130)
+ (line 131)
* __dpd_extendsfdd: Decimal float library routines.
- (line 101)
+ (line 102)
* __dpd_extendsfsd: Decimal float library routines.
- (line 143)
+ (line 144)
* __dpd_extendsftd: Decimal float library routines.
- (line 103)
+ (line 104)
* __dpd_extendtftd: Decimal float library routines.
- (line 147)
+ (line 148)
* __dpd_extendxftd: Decimal float library routines.
- (line 107)
+ (line 108)
* __dpd_fixdddi: Decimal float library routines.
- (line 168)
+ (line 169)
* __dpd_fixddsi: Decimal float library routines.
- (line 160)
+ (line 161)
* __dpd_fixsddi: Decimal float library routines.
- (line 166)
+ (line 167)
* __dpd_fixsdsi: Decimal float library routines.
- (line 158)
+ (line 159)
* __dpd_fixtddi: Decimal float library routines.
- (line 170)
+ (line 171)
* __dpd_fixtdsi: Decimal float library routines.
- (line 162)
+ (line 163)
* __dpd_fixunsdddi: Decimal float library routines.
- (line 185)
+ (line 186)
* __dpd_fixunsddsi: Decimal float library routines.
- (line 176)
+ (line 177)
* __dpd_fixunssddi: Decimal float library routines.
- (line 183)
+ (line 184)
* __dpd_fixunssdsi: Decimal float library routines.
- (line 174)
+ (line 175)
* __dpd_fixunstddi: Decimal float library routines.
- (line 187)
+ (line 188)
* __dpd_fixunstdsi: Decimal float library routines.
- (line 178)
+ (line 179)
* __dpd_floatdidd: Decimal float library routines.
- (line 203)
+ (line 204)
* __dpd_floatdisd: Decimal float library routines.
- (line 201)
+ (line 202)
* __dpd_floatditd: Decimal float library routines.
- (line 205)
+ (line 206)
* __dpd_floatsidd: Decimal float library routines.
- (line 194)
+ (line 195)
* __dpd_floatsisd: Decimal float library routines.
- (line 192)
+ (line 193)
* __dpd_floatsitd: Decimal float library routines.
- (line 196)
+ (line 197)
* __dpd_floatunsdidd: Decimal float library routines.
- (line 221)
+ (line 222)
* __dpd_floatunsdisd: Decimal float library routines.
- (line 219)
+ (line 220)
* __dpd_floatunsditd: Decimal float library routines.
- (line 223)
+ (line 224)
* __dpd_floatunssidd: Decimal float library routines.
- (line 212)
+ (line 213)
* __dpd_floatunssisd: Decimal float library routines.
- (line 210)
+ (line 211)
* __dpd_floatunssitd: Decimal float library routines.
- (line 214)
+ (line 215)
* __dpd_gedd2: Decimal float library routines.
- (line 275)
+ (line 276)
* __dpd_gesd2: Decimal float library routines.
- (line 273)
+ (line 274)
* __dpd_getd2: Decimal float library routines.
- (line 277)
+ (line 278)
* __dpd_gtdd2: Decimal float library routines.
- (line 302)
+ (line 303)
* __dpd_gtsd2: Decimal float library routines.
- (line 300)
+ (line 301)
* __dpd_gttd2: Decimal float library routines.
- (line 304)
+ (line 305)
* __dpd_ledd2: Decimal float library routines.
- (line 293)
+ (line 294)
* __dpd_lesd2: Decimal float library routines.
- (line 291)
+ (line 292)
* __dpd_letd2: Decimal float library routines.
- (line 295)
+ (line 296)
* __dpd_ltdd2: Decimal float library routines.
- (line 284)
+ (line 285)
* __dpd_ltsd2: Decimal float library routines.
- (line 282)
+ (line 283)
* __dpd_lttd2: Decimal float library routines.
- (line 286)
+ (line 287)
* __dpd_muldd3: Decimal float library routines.
- (line 50)
+ (line 52)
* __dpd_mulsd3: Decimal float library routines.
- (line 46)
+ (line 48)
* __dpd_multd3: Decimal float library routines.
- (line 54)
+ (line 56)
* __dpd_nedd2: Decimal float library routines.
- (line 266)
+ (line 267)
* __dpd_negdd2: Decimal float library routines.
- (line 76)
+ (line 77)
* __dpd_negsd2: Decimal float library routines.
- (line 74)
+ (line 75)
* __dpd_negtd2: Decimal float library routines.
- (line 78)
+ (line 79)
* __dpd_nesd2: Decimal float library routines.
- (line 264)
+ (line 265)
* __dpd_netd2: Decimal float library routines.
- (line 268)
+ (line 269)
* __dpd_subdd3: Decimal float library routines.
- (line 35)
+ (line 37)
* __dpd_subsd3: Decimal float library routines.
- (line 31)
+ (line 33)
* __dpd_subtd3: Decimal float library routines.
- (line 39)
+ (line 41)
* __dpd_truncdddf: Decimal float library routines.
- (line 151)
+ (line 152)
* __dpd_truncddsd2: Decimal float library routines.
- (line 92)
+ (line 93)
* __dpd_truncddsf: Decimal float library routines.
- (line 122)
+ (line 123)
* __dpd_truncdfsd: Decimal float library routines.
- (line 109)
+ (line 110)
* __dpd_truncsdsf: Decimal float library routines.
- (line 149)
+ (line 150)
* __dpd_trunctddd2: Decimal float library routines.
- (line 96)
+ (line 97)
* __dpd_trunctddf: Decimal float library routines.
- (line 128)
+ (line 129)
* __dpd_trunctdsd2: Decimal float library routines.
- (line 94)
+ (line 95)
* __dpd_trunctdsf: Decimal float library routines.
- (line 124)
+ (line 125)
* __dpd_trunctdtf: Decimal float library routines.
- (line 153)
+ (line 154)
* __dpd_trunctdxf: Decimal float library routines.
- (line 134)
+ (line 135)
* __dpd_trunctfdd: Decimal float library routines.
- (line 117)
+ (line 118)
* __dpd_trunctfsd: Decimal float library routines.
- (line 113)
+ (line 114)
* __dpd_truncxfdd: Decimal float library routines.
- (line 115)
+ (line 116)
* __dpd_truncxfsd: Decimal float library routines.
- (line 111)
+ (line 112)
* __dpd_unorddd2: Decimal float library routines.
- (line 233)
+ (line 234)
* __dpd_unordsd2: Decimal float library routines.
- (line 231)
+ (line 232)
* __dpd_unordtd2: Decimal float library routines.
- (line 235)
+ (line 236)
* __DTOR_LIST__: Initialization. (line 25)
* __eqdf2: Soft float library routines.
- (line 193)
+ (line 194)
* __eqsf2: Soft float library routines.
- (line 192)
+ (line 193)
* __eqtf2: Soft float library routines.
- (line 194)
+ (line 195)
* __extenddftf2: Soft float library routines.
- (line 67)
-* __extenddfxf2: Soft float library routines.
(line 68)
+* __extenddfxf2: Soft float library routines.
+ (line 69)
* __extendsfdf2: Soft float library routines.
- (line 64)
-* __extendsftf2: Soft float library routines.
(line 65)
-* __extendsfxf2: Soft float library routines.
+* __extendsftf2: Soft float library routines.
(line 66)
+* __extendsfxf2: Soft float library routines.
+ (line 67)
* __ffsdi2: Integer library routines.
- (line 143)
-* __ffsti2: Integer library routines.
(line 144)
+* __ffsti2: Integer library routines.
+ (line 145)
* __fixdfdi: Soft float library routines.
- (line 87)
+ (line 88)
* __fixdfsi: Soft float library routines.
- (line 80)
+ (line 81)
* __fixdfti: Soft float library routines.
- (line 93)
+ (line 94)
* __fixsfdi: Soft float library routines.
- (line 86)
+ (line 87)
* __fixsfsi: Soft float library routines.
- (line 79)
+ (line 80)
* __fixsfti: Soft float library routines.
- (line 92)
+ (line 93)
* __fixtfdi: Soft float library routines.
- (line 88)
+ (line 89)
* __fixtfsi: Soft float library routines.
- (line 81)
+ (line 82)
* __fixtfti: Soft float library routines.
- (line 94)
+ (line 95)
* __fixunsdfdi: Soft float library routines.
- (line 107)
+ (line 108)
* __fixunsdfsi: Soft float library routines.
- (line 100)
+ (line 101)
* __fixunsdfti: Soft float library routines.
- (line 114)
+ (line 115)
* __fixunssfdi: Soft float library routines.
- (line 106)
+ (line 107)
* __fixunssfsi: Soft float library routines.
- (line 99)
+ (line 100)
* __fixunssfti: Soft float library routines.
- (line 113)
+ (line 114)
* __fixunstfdi: Soft float library routines.
- (line 108)
+ (line 109)
* __fixunstfsi: Soft float library routines.
- (line 101)
+ (line 102)
* __fixunstfti: Soft float library routines.
- (line 115)
+ (line 116)
* __fixunsxfdi: Soft float library routines.
- (line 109)
+ (line 110)
* __fixunsxfsi: Soft float library routines.
- (line 102)
+ (line 103)
* __fixunsxfti: Soft float library routines.
- (line 116)
+ (line 117)
* __fixxfdi: Soft float library routines.
- (line 89)
+ (line 90)
* __fixxfsi: Soft float library routines.
- (line 82)
+ (line 83)
* __fixxfti: Soft float library routines.
- (line 95)
+ (line 96)
* __floatdidf: Soft float library routines.
- (line 127)
+ (line 128)
* __floatdisf: Soft float library routines.
- (line 126)
+ (line 127)
* __floatditf: Soft float library routines.
- (line 128)
-* __floatdixf: Soft float library routines.
(line 129)
+* __floatdixf: Soft float library routines.
+ (line 130)
* __floatsidf: Soft float library routines.
- (line 121)
+ (line 122)
* __floatsisf: Soft float library routines.
- (line 120)
+ (line 121)
* __floatsitf: Soft float library routines.
- (line 122)
-* __floatsixf: Soft float library routines.
(line 123)
+* __floatsixf: Soft float library routines.
+ (line 124)
* __floattidf: Soft float library routines.
- (line 133)
+ (line 134)
* __floattisf: Soft float library routines.
- (line 132)
+ (line 133)
* __floattitf: Soft float library routines.
- (line 134)
-* __floattixf: Soft float library routines.
(line 135)
+* __floattixf: Soft float library routines.
+ (line 136)
* __floatundidf: Soft float library routines.
- (line 145)
+ (line 146)
* __floatundisf: Soft float library routines.
- (line 144)
+ (line 145)
* __floatunditf: Soft float library routines.
- (line 146)
-* __floatundixf: Soft float library routines.
(line 147)
+* __floatundixf: Soft float library routines.
+ (line 148)
* __floatunsidf: Soft float library routines.
- (line 139)
+ (line 140)
* __floatunsisf: Soft float library routines.
- (line 138)
+ (line 139)
* __floatunsitf: Soft float library routines.
- (line 140)
-* __floatunsixf: Soft float library routines.
(line 141)
+* __floatunsixf: Soft float library routines.
+ (line 142)
* __floatuntidf: Soft float library routines.
- (line 151)
+ (line 152)
* __floatuntisf: Soft float library routines.
- (line 150)
+ (line 151)
* __floatuntitf: Soft float library routines.
- (line 152)
-* __floatuntixf: Soft float library routines.
(line 153)
+* __floatuntixf: Soft float library routines.
+ (line 154)
* __fractdadf: Fixed-point fractional library routines.
- (line 635)
+ (line 636)
* __fractdadi: Fixed-point fractional library routines.
- (line 632)
+ (line 633)
* __fractdadq: Fixed-point fractional library routines.
- (line 615)
-* __fractdaha2: Fixed-point fractional library routines.
(line 616)
+* __fractdaha2: Fixed-point fractional library routines.
+ (line 617)
* __fractdahi: Fixed-point fractional library routines.
- (line 630)
+ (line 631)
* __fractdahq: Fixed-point fractional library routines.
- (line 613)
+ (line 614)
* __fractdaqi: Fixed-point fractional library routines.
- (line 629)
+ (line 630)
* __fractdaqq: Fixed-point fractional library routines.
- (line 612)
+ (line 613)
* __fractdasa2: Fixed-point fractional library routines.
- (line 617)
+ (line 618)
* __fractdasf: Fixed-point fractional library routines.
- (line 634)
+ (line 635)
* __fractdasi: Fixed-point fractional library routines.
- (line 631)
+ (line 632)
* __fractdasq: Fixed-point fractional library routines.
- (line 614)
+ (line 615)
* __fractdata2: Fixed-point fractional library routines.
- (line 618)
+ (line 619)
* __fractdati: Fixed-point fractional library routines.
- (line 633)
+ (line 634)
* __fractdauda: Fixed-point fractional library routines.
- (line 626)
+ (line 627)
* __fractdaudq: Fixed-point fractional library routines.
- (line 622)
-* __fractdauha: Fixed-point fractional library routines.
(line 624)
+* __fractdauha: Fixed-point fractional library routines.
+ (line 625)
* __fractdauhq: Fixed-point fractional library routines.
- (line 620)
+ (line 621)
* __fractdauqq: Fixed-point fractional library routines.
- (line 619)
+ (line 620)
* __fractdausa: Fixed-point fractional library routines.
- (line 625)
+ (line 626)
* __fractdausq: Fixed-point fractional library routines.
- (line 621)
+ (line 622)
* __fractdauta: Fixed-point fractional library routines.
- (line 627)
+ (line 629)
* __fractdfda: Fixed-point fractional library routines.
- (line 1024)
+ (line 1025)
* __fractdfdq: Fixed-point fractional library routines.
- (line 1021)
-* __fractdfha: Fixed-point fractional library routines.
(line 1022)
+* __fractdfha: Fixed-point fractional library routines.
+ (line 1023)
* __fractdfhq: Fixed-point fractional library routines.
- (line 1019)
+ (line 1020)
* __fractdfqq: Fixed-point fractional library routines.
- (line 1018)
+ (line 1019)
* __fractdfsa: Fixed-point fractional library routines.
- (line 1023)
+ (line 1024)
* __fractdfsq: Fixed-point fractional library routines.
- (line 1020)
+ (line 1021)
* __fractdfta: Fixed-point fractional library routines.
- (line 1025)
+ (line 1026)
* __fractdfuda: Fixed-point fractional library routines.
- (line 1032)
+ (line 1033)
* __fractdfudq: Fixed-point fractional library routines.
- (line 1029)
-* __fractdfuha: Fixed-point fractional library routines.
(line 1030)
+* __fractdfuha: Fixed-point fractional library routines.
+ (line 1031)
* __fractdfuhq: Fixed-point fractional library routines.
- (line 1027)
+ (line 1028)
* __fractdfuqq: Fixed-point fractional library routines.
- (line 1026)
+ (line 1027)
* __fractdfusa: Fixed-point fractional library routines.
- (line 1031)
+ (line 1032)
* __fractdfusq: Fixed-point fractional library routines.
- (line 1028)
+ (line 1029)
* __fractdfuta: Fixed-point fractional library routines.
- (line 1033)
+ (line 1034)
* __fractdida: Fixed-point fractional library routines.
- (line 974)
+ (line 975)
* __fractdidq: Fixed-point fractional library routines.
- (line 971)
-* __fractdiha: Fixed-point fractional library routines.
(line 972)
+* __fractdiha: Fixed-point fractional library routines.
+ (line 973)
* __fractdihq: Fixed-point fractional library routines.
- (line 969)
+ (line 970)
* __fractdiqq: Fixed-point fractional library routines.
- (line 968)
+ (line 969)
* __fractdisa: Fixed-point fractional library routines.
- (line 973)
+ (line 974)
* __fractdisq: Fixed-point fractional library routines.
- (line 970)
+ (line 971)
* __fractdita: Fixed-point fractional library routines.
- (line 975)
+ (line 976)
* __fractdiuda: Fixed-point fractional library routines.
- (line 982)
+ (line 983)
* __fractdiudq: Fixed-point fractional library routines.
- (line 979)
-* __fractdiuha: Fixed-point fractional library routines.
(line 980)
+* __fractdiuha: Fixed-point fractional library routines.
+ (line 981)
* __fractdiuhq: Fixed-point fractional library routines.
- (line 977)
+ (line 978)
* __fractdiuqq: Fixed-point fractional library routines.
- (line 976)
+ (line 977)
* __fractdiusa: Fixed-point fractional library routines.
- (line 981)
+ (line 982)
* __fractdiusq: Fixed-point fractional library routines.
- (line 978)
+ (line 979)
* __fractdiuta: Fixed-point fractional library routines.
- (line 983)
+ (line 984)
* __fractdqda: Fixed-point fractional library routines.
- (line 543)
+ (line 544)
* __fractdqdf: Fixed-point fractional library routines.
- (line 565)
+ (line 566)
* __fractdqdi: Fixed-point fractional library routines.
- (line 562)
+ (line 563)
* __fractdqha: Fixed-point fractional library routines.
- (line 541)
+ (line 542)
* __fractdqhi: Fixed-point fractional library routines.
- (line 560)
+ (line 561)
* __fractdqhq2: Fixed-point fractional library routines.
- (line 539)
+ (line 540)
* __fractdqqi: Fixed-point fractional library routines.
- (line 559)
+ (line 560)
* __fractdqqq2: Fixed-point fractional library routines.
- (line 538)
+ (line 539)
* __fractdqsa: Fixed-point fractional library routines.
- (line 542)
+ (line 543)
* __fractdqsf: Fixed-point fractional library routines.
- (line 564)
+ (line 565)
* __fractdqsi: Fixed-point fractional library routines.
- (line 561)
+ (line 562)
* __fractdqsq2: Fixed-point fractional library routines.
- (line 540)
+ (line 541)
* __fractdqta: Fixed-point fractional library routines.
- (line 544)
+ (line 545)
* __fractdqti: Fixed-point fractional library routines.
- (line 563)
+ (line 564)
* __fractdquda: Fixed-point fractional library routines.
- (line 555)
+ (line 557)
* __fractdqudq: Fixed-point fractional library routines.
- (line 550)
-* __fractdquha: Fixed-point fractional library routines.
(line 552)
+* __fractdquha: Fixed-point fractional library routines.
+ (line 554)
* __fractdquhq: Fixed-point fractional library routines.
- (line 547)
+ (line 548)
* __fractdquqq: Fixed-point fractional library routines.
- (line 545)
+ (line 547)
* __fractdqusa: Fixed-point fractional library routines.
- (line 554)
+ (line 555)
* __fractdqusq: Fixed-point fractional library routines.
- (line 548)
+ (line 550)
* __fractdquta: Fixed-point fractional library routines.
- (line 557)
+ (line 559)
* __fracthada2: Fixed-point fractional library routines.
- (line 571)
+ (line 572)
* __fracthadf: Fixed-point fractional library routines.
- (line 589)
+ (line 590)
* __fracthadi: Fixed-point fractional library routines.
- (line 586)
+ (line 587)
* __fracthadq: Fixed-point fractional library routines.
- (line 569)
+ (line 570)
* __fracthahi: Fixed-point fractional library routines.
- (line 584)
+ (line 585)
* __fracthahq: Fixed-point fractional library routines.
- (line 567)
+ (line 568)
* __fracthaqi: Fixed-point fractional library routines.
- (line 583)
+ (line 584)
* __fracthaqq: Fixed-point fractional library routines.
- (line 566)
+ (line 567)
* __fracthasa2: Fixed-point fractional library routines.
- (line 570)
+ (line 571)
* __fracthasf: Fixed-point fractional library routines.
- (line 588)
+ (line 589)
* __fracthasi: Fixed-point fractional library routines.
- (line 585)
+ (line 586)
* __fracthasq: Fixed-point fractional library routines.
- (line 568)
+ (line 569)
* __fracthata2: Fixed-point fractional library routines.
- (line 572)
+ (line 573)
* __fracthati: Fixed-point fractional library routines.
- (line 587)
+ (line 588)
* __fracthauda: Fixed-point fractional library routines.
- (line 580)
+ (line 581)
* __fracthaudq: Fixed-point fractional library routines.
- (line 576)
-* __fracthauha: Fixed-point fractional library routines.
(line 578)
+* __fracthauha: Fixed-point fractional library routines.
+ (line 579)
* __fracthauhq: Fixed-point fractional library routines.
- (line 574)
+ (line 575)
* __fracthauqq: Fixed-point fractional library routines.
- (line 573)
+ (line 574)
* __fracthausa: Fixed-point fractional library routines.
- (line 579)
+ (line 580)
* __fracthausq: Fixed-point fractional library routines.
- (line 575)
+ (line 576)
* __fracthauta: Fixed-point fractional library routines.
- (line 581)
+ (line 583)
* __fracthida: Fixed-point fractional library routines.
- (line 942)
+ (line 943)
* __fracthidq: Fixed-point fractional library routines.
- (line 939)
-* __fracthiha: Fixed-point fractional library routines.
(line 940)
+* __fracthiha: Fixed-point fractional library routines.
+ (line 941)
* __fracthihq: Fixed-point fractional library routines.
- (line 937)
+ (line 938)
* __fracthiqq: Fixed-point fractional library routines.
- (line 936)
+ (line 937)
* __fracthisa: Fixed-point fractional library routines.
- (line 941)
+ (line 942)
* __fracthisq: Fixed-point fractional library routines.
- (line 938)
+ (line 939)
* __fracthita: Fixed-point fractional library routines.
- (line 943)
+ (line 944)
* __fracthiuda: Fixed-point fractional library routines.
- (line 950)
+ (line 951)
* __fracthiudq: Fixed-point fractional library routines.
- (line 947)
-* __fracthiuha: Fixed-point fractional library routines.
(line 948)
+* __fracthiuha: Fixed-point fractional library routines.
+ (line 949)
* __fracthiuhq: Fixed-point fractional library routines.
- (line 945)
+ (line 946)
* __fracthiuqq: Fixed-point fractional library routines.
- (line 944)
+ (line 945)
* __fracthiusa: Fixed-point fractional library routines.
- (line 949)
+ (line 950)
* __fracthiusq: Fixed-point fractional library routines.
- (line 946)
+ (line 947)
* __fracthiuta: Fixed-point fractional library routines.
- (line 951)
+ (line 952)
* __fracthqda: Fixed-point fractional library routines.
- (line 497)
+ (line 498)
* __fracthqdf: Fixed-point fractional library routines.
- (line 513)
+ (line 514)
* __fracthqdi: Fixed-point fractional library routines.
- (line 510)
+ (line 511)
* __fracthqdq2: Fixed-point fractional library routines.
- (line 494)
-* __fracthqha: Fixed-point fractional library routines.
(line 495)
+* __fracthqha: Fixed-point fractional library routines.
+ (line 496)
* __fracthqhi: Fixed-point fractional library routines.
- (line 508)
+ (line 509)
* __fracthqqi: Fixed-point fractional library routines.
- (line 507)
+ (line 508)
* __fracthqqq2: Fixed-point fractional library routines.
- (line 492)
+ (line 493)
* __fracthqsa: Fixed-point fractional library routines.
- (line 496)
+ (line 497)
* __fracthqsf: Fixed-point fractional library routines.
- (line 512)
+ (line 513)
* __fracthqsi: Fixed-point fractional library routines.
- (line 509)
+ (line 510)
* __fracthqsq2: Fixed-point fractional library routines.
- (line 493)
+ (line 494)
* __fracthqta: Fixed-point fractional library routines.
- (line 498)
+ (line 499)
* __fracthqti: Fixed-point fractional library routines.
- (line 511)
+ (line 512)
* __fracthquda: Fixed-point fractional library routines.
- (line 505)
+ (line 506)
* __fracthqudq: Fixed-point fractional library routines.
- (line 502)
-* __fracthquha: Fixed-point fractional library routines.
(line 503)
+* __fracthquha: Fixed-point fractional library routines.
+ (line 504)
* __fracthquhq: Fixed-point fractional library routines.
- (line 500)
+ (line 501)
* __fracthquqq: Fixed-point fractional library routines.
- (line 499)
+ (line 500)
* __fracthqusa: Fixed-point fractional library routines.
- (line 504)
+ (line 505)
* __fracthqusq: Fixed-point fractional library routines.
- (line 501)
+ (line 502)
* __fracthquta: Fixed-point fractional library routines.
- (line 506)
+ (line 507)
* __fractqida: Fixed-point fractional library routines.
- (line 924)
+ (line 925)
* __fractqidq: Fixed-point fractional library routines.
- (line 921)
-* __fractqiha: Fixed-point fractional library routines.
(line 922)
+* __fractqiha: Fixed-point fractional library routines.
+ (line 923)
* __fractqihq: Fixed-point fractional library routines.
- (line 919)
+ (line 920)
* __fractqiqq: Fixed-point fractional library routines.
- (line 918)
+ (line 919)
* __fractqisa: Fixed-point fractional library routines.
- (line 923)
+ (line 924)
* __fractqisq: Fixed-point fractional library routines.
- (line 920)
+ (line 921)
* __fractqita: Fixed-point fractional library routines.
- (line 925)
+ (line 926)
* __fractqiuda: Fixed-point fractional library routines.
- (line 933)
+ (line 934)
* __fractqiudq: Fixed-point fractional library routines.
- (line 929)
-* __fractqiuha: Fixed-point fractional library routines.
(line 931)
+* __fractqiuha: Fixed-point fractional library routines.
+ (line 932)
* __fractqiuhq: Fixed-point fractional library routines.
- (line 927)
+ (line 928)
* __fractqiuqq: Fixed-point fractional library routines.
- (line 926)
+ (line 927)
* __fractqiusa: Fixed-point fractional library routines.
- (line 932)
+ (line 933)
* __fractqiusq: Fixed-point fractional library routines.
- (line 928)
+ (line 929)
* __fractqiuta: Fixed-point fractional library routines.
- (line 934)
+ (line 936)
* __fractqqda: Fixed-point fractional library routines.
- (line 473)
+ (line 474)
* __fractqqdf: Fixed-point fractional library routines.
- (line 491)
+ (line 492)
* __fractqqdi: Fixed-point fractional library routines.
- (line 488)
+ (line 489)
* __fractqqdq2: Fixed-point fractional library routines.
- (line 470)
-* __fractqqha: Fixed-point fractional library routines.
(line 471)
+* __fractqqha: Fixed-point fractional library routines.
+ (line 472)
* __fractqqhi: Fixed-point fractional library routines.
- (line 486)
+ (line 487)
* __fractqqhq2: Fixed-point fractional library routines.
- (line 468)
+ (line 469)
* __fractqqqi: Fixed-point fractional library routines.
- (line 485)
+ (line 486)
* __fractqqsa: Fixed-point fractional library routines.
- (line 472)
+ (line 473)
* __fractqqsf: Fixed-point fractional library routines.
- (line 490)
+ (line 491)
* __fractqqsi: Fixed-point fractional library routines.
- (line 487)
+ (line 488)
* __fractqqsq2: Fixed-point fractional library routines.
- (line 469)
+ (line 470)
* __fractqqta: Fixed-point fractional library routines.
- (line 474)
+ (line 475)
* __fractqqti: Fixed-point fractional library routines.
- (line 489)
+ (line 490)
* __fractqquda: Fixed-point fractional library routines.
- (line 482)
+ (line 483)
* __fractqqudq: Fixed-point fractional library routines.
- (line 478)
-* __fractqquha: Fixed-point fractional library routines.
(line 480)
+* __fractqquha: Fixed-point fractional library routines.
+ (line 481)
* __fractqquhq: Fixed-point fractional library routines.
- (line 476)
+ (line 477)
* __fractqquqq: Fixed-point fractional library routines.
- (line 475)
+ (line 476)
* __fractqqusa: Fixed-point fractional library routines.
- (line 481)
+ (line 482)
* __fractqqusq: Fixed-point fractional library routines.
- (line 477)
+ (line 478)
* __fractqquta: Fixed-point fractional library routines.
- (line 483)
+ (line 485)
* __fractsada2: Fixed-point fractional library routines.
- (line 595)
+ (line 596)
* __fractsadf: Fixed-point fractional library routines.
- (line 611)
+ (line 612)
* __fractsadi: Fixed-point fractional library routines.
- (line 608)
+ (line 609)
* __fractsadq: Fixed-point fractional library routines.
- (line 593)
-* __fractsaha2: Fixed-point fractional library routines.
(line 594)
+* __fractsaha2: Fixed-point fractional library routines.
+ (line 595)
* __fractsahi: Fixed-point fractional library routines.
- (line 606)
+ (line 607)
* __fractsahq: Fixed-point fractional library routines.
- (line 591)
+ (line 592)
* __fractsaqi: Fixed-point fractional library routines.
- (line 605)
+ (line 606)
* __fractsaqq: Fixed-point fractional library routines.
- (line 590)
+ (line 591)
* __fractsasf: Fixed-point fractional library routines.
- (line 610)
+ (line 611)
* __fractsasi: Fixed-point fractional library routines.
- (line 607)
+ (line 608)
* __fractsasq: Fixed-point fractional library routines.
- (line 592)
+ (line 593)
* __fractsata2: Fixed-point fractional library routines.
- (line 596)
+ (line 597)
* __fractsati: Fixed-point fractional library routines.
- (line 609)
+ (line 610)
* __fractsauda: Fixed-point fractional library routines.
- (line 603)
+ (line 604)
* __fractsaudq: Fixed-point fractional library routines.
- (line 600)
-* __fractsauha: Fixed-point fractional library routines.
(line 601)
+* __fractsauha: Fixed-point fractional library routines.
+ (line 602)
* __fractsauhq: Fixed-point fractional library routines.
- (line 598)
+ (line 599)
* __fractsauqq: Fixed-point fractional library routines.
- (line 597)
+ (line 598)
* __fractsausa: Fixed-point fractional library routines.
- (line 602)
+ (line 603)
* __fractsausq: Fixed-point fractional library routines.
- (line 599)
+ (line 600)
* __fractsauta: Fixed-point fractional library routines.
- (line 604)
+ (line 605)
* __fractsfda: Fixed-point fractional library routines.
- (line 1008)
+ (line 1009)
* __fractsfdq: Fixed-point fractional library routines.
- (line 1005)
-* __fractsfha: Fixed-point fractional library routines.
(line 1006)
+* __fractsfha: Fixed-point fractional library routines.
+ (line 1007)
* __fractsfhq: Fixed-point fractional library routines.
- (line 1003)
+ (line 1004)
* __fractsfqq: Fixed-point fractional library routines.
- (line 1002)
+ (line 1003)
* __fractsfsa: Fixed-point fractional library routines.
- (line 1007)
+ (line 1008)
* __fractsfsq: Fixed-point fractional library routines.
- (line 1004)
+ (line 1005)
* __fractsfta: Fixed-point fractional library routines.
- (line 1009)
+ (line 1010)
* __fractsfuda: Fixed-point fractional library routines.
- (line 1016)
+ (line 1017)
* __fractsfudq: Fixed-point fractional library routines.
- (line 1013)
-* __fractsfuha: Fixed-point fractional library routines.
(line 1014)
+* __fractsfuha: Fixed-point fractional library routines.
+ (line 1015)
* __fractsfuhq: Fixed-point fractional library routines.
- (line 1011)
+ (line 1012)
* __fractsfuqq: Fixed-point fractional library routines.
- (line 1010)
+ (line 1011)
* __fractsfusa: Fixed-point fractional library routines.
- (line 1015)
+ (line 1016)
* __fractsfusq: Fixed-point fractional library routines.
- (line 1012)
+ (line 1013)
* __fractsfuta: Fixed-point fractional library routines.
- (line 1017)
+ (line 1018)
* __fractsida: Fixed-point fractional library routines.
- (line 958)
+ (line 959)
* __fractsidq: Fixed-point fractional library routines.
- (line 955)
-* __fractsiha: Fixed-point fractional library routines.
(line 956)
+* __fractsiha: Fixed-point fractional library routines.
+ (line 957)
* __fractsihq: Fixed-point fractional library routines.
- (line 953)
+ (line 954)
* __fractsiqq: Fixed-point fractional library routines.
- (line 952)
+ (line 953)
* __fractsisa: Fixed-point fractional library routines.
- (line 957)
+ (line 958)
* __fractsisq: Fixed-point fractional library routines.
- (line 954)
+ (line 955)
* __fractsita: Fixed-point fractional library routines.
- (line 959)
+ (line 960)
* __fractsiuda: Fixed-point fractional library routines.
- (line 966)
+ (line 967)
* __fractsiudq: Fixed-point fractional library routines.
- (line 963)
-* __fractsiuha: Fixed-point fractional library routines.
(line 964)
+* __fractsiuha: Fixed-point fractional library routines.
+ (line 965)
* __fractsiuhq: Fixed-point fractional library routines.
- (line 961)
+ (line 962)
* __fractsiuqq: Fixed-point fractional library routines.
- (line 960)
+ (line 961)
* __fractsiusa: Fixed-point fractional library routines.
- (line 965)
+ (line 966)
* __fractsiusq: Fixed-point fractional library routines.
- (line 962)
+ (line 963)
* __fractsiuta: Fixed-point fractional library routines.
- (line 967)
+ (line 968)
* __fractsqda: Fixed-point fractional library routines.
- (line 519)
+ (line 520)
* __fractsqdf: Fixed-point fractional library routines.
- (line 537)
+ (line 538)
* __fractsqdi: Fixed-point fractional library routines.
- (line 534)
+ (line 535)
* __fractsqdq2: Fixed-point fractional library routines.
- (line 516)
-* __fractsqha: Fixed-point fractional library routines.
(line 517)
+* __fractsqha: Fixed-point fractional library routines.
+ (line 518)
* __fractsqhi: Fixed-point fractional library routines.
- (line 532)
+ (line 533)
* __fractsqhq2: Fixed-point fractional library routines.
- (line 515)
+ (line 516)
* __fractsqqi: Fixed-point fractional library routines.
- (line 531)
+ (line 532)
* __fractsqqq2: Fixed-point fractional library routines.
- (line 514)
+ (line 515)
* __fractsqsa: Fixed-point fractional library routines.
- (line 518)
+ (line 519)
* __fractsqsf: Fixed-point fractional library routines.
- (line 536)
+ (line 537)
* __fractsqsi: Fixed-point fractional library routines.
- (line 533)
+ (line 534)
* __fractsqta: Fixed-point fractional library routines.
- (line 520)
+ (line 521)
* __fractsqti: Fixed-point fractional library routines.
- (line 535)
+ (line 536)
* __fractsquda: Fixed-point fractional library routines.
- (line 528)
+ (line 529)
* __fractsqudq: Fixed-point fractional library routines.
- (line 524)
-* __fractsquha: Fixed-point fractional library routines.
(line 526)
+* __fractsquha: Fixed-point fractional library routines.
+ (line 527)
* __fractsquhq: Fixed-point fractional library routines.
- (line 522)
+ (line 523)
* __fractsquqq: Fixed-point fractional library routines.
- (line 521)
+ (line 522)
* __fractsqusa: Fixed-point fractional library routines.
- (line 527)
+ (line 528)
* __fractsqusq: Fixed-point fractional library routines.
- (line 523)
+ (line 524)
* __fractsquta: Fixed-point fractional library routines.
- (line 529)
+ (line 531)
* __fracttada2: Fixed-point fractional library routines.
- (line 642)
+ (line 643)
* __fracttadf: Fixed-point fractional library routines.
- (line 663)
+ (line 664)
* __fracttadi: Fixed-point fractional library routines.
- (line 660)
+ (line 661)
* __fracttadq: Fixed-point fractional library routines.
- (line 639)
-* __fracttaha2: Fixed-point fractional library routines.
(line 640)
+* __fracttaha2: Fixed-point fractional library routines.
+ (line 641)
* __fracttahi: Fixed-point fractional library routines.
- (line 658)
+ (line 659)
* __fracttahq: Fixed-point fractional library routines.
- (line 637)
+ (line 638)
* __fracttaqi: Fixed-point fractional library routines.
- (line 657)
+ (line 658)
* __fracttaqq: Fixed-point fractional library routines.
- (line 636)
+ (line 637)
* __fracttasa2: Fixed-point fractional library routines.
- (line 641)
+ (line 642)
* __fracttasf: Fixed-point fractional library routines.
- (line 662)
+ (line 663)
* __fracttasi: Fixed-point fractional library routines.
- (line 659)
+ (line 660)
* __fracttasq: Fixed-point fractional library routines.
- (line 638)
+ (line 639)
* __fracttati: Fixed-point fractional library routines.
- (line 661)
+ (line 662)
* __fracttauda: Fixed-point fractional library routines.
- (line 653)
+ (line 655)
* __fracttaudq: Fixed-point fractional library routines.
- (line 648)
-* __fracttauha: Fixed-point fractional library routines.
(line 650)
+* __fracttauha: Fixed-point fractional library routines.
+ (line 652)
* __fracttauhq: Fixed-point fractional library routines.
- (line 645)
+ (line 646)
* __fracttauqq: Fixed-point fractional library routines.
- (line 643)
+ (line 645)
* __fracttausa: Fixed-point fractional library routines.
- (line 652)
+ (line 653)
* __fracttausq: Fixed-point fractional library routines.
- (line 646)
+ (line 648)
* __fracttauta: Fixed-point fractional library routines.
- (line 655)
+ (line 657)
* __fracttida: Fixed-point fractional library routines.
- (line 990)
+ (line 991)
* __fracttidq: Fixed-point fractional library routines.
- (line 987)
-* __fracttiha: Fixed-point fractional library routines.
(line 988)
+* __fracttiha: Fixed-point fractional library routines.
+ (line 989)
* __fracttihq: Fixed-point fractional library routines.
- (line 985)
+ (line 986)
* __fracttiqq: Fixed-point fractional library routines.
- (line 984)
+ (line 985)
* __fracttisa: Fixed-point fractional library routines.
- (line 989)
+ (line 990)
* __fracttisq: Fixed-point fractional library routines.
- (line 986)
+ (line 987)
* __fracttita: Fixed-point fractional library routines.
- (line 991)
+ (line 992)
* __fracttiuda: Fixed-point fractional library routines.
- (line 999)
+ (line 1000)
* __fracttiudq: Fixed-point fractional library routines.
- (line 995)
-* __fracttiuha: Fixed-point fractional library routines.
(line 997)
+* __fracttiuha: Fixed-point fractional library routines.
+ (line 998)
* __fracttiuhq: Fixed-point fractional library routines.
- (line 993)
+ (line 994)
* __fracttiuqq: Fixed-point fractional library routines.
- (line 992)
+ (line 993)
* __fracttiusa: Fixed-point fractional library routines.
- (line 998)
+ (line 999)
* __fracttiusq: Fixed-point fractional library routines.
- (line 994)
+ (line 995)
* __fracttiuta: Fixed-point fractional library routines.
- (line 1000)
+ (line 1002)
* __fractudada: Fixed-point fractional library routines.
- (line 857)
+ (line 858)
* __fractudadf: Fixed-point fractional library routines.
- (line 880)
+ (line 881)
* __fractudadi: Fixed-point fractional library routines.
- (line 877)
+ (line 878)
* __fractudadq: Fixed-point fractional library routines.
- (line 853)
-* __fractudaha: Fixed-point fractional library routines.
(line 855)
+* __fractudaha: Fixed-point fractional library routines.
+ (line 856)
* __fractudahi: Fixed-point fractional library routines.
- (line 875)
+ (line 876)
* __fractudahq: Fixed-point fractional library routines.
- (line 851)
+ (line 852)
* __fractudaqi: Fixed-point fractional library routines.
- (line 874)
+ (line 875)
* __fractudaqq: Fixed-point fractional library routines.
- (line 850)
+ (line 851)
* __fractudasa: Fixed-point fractional library routines.
- (line 856)
+ (line 857)
* __fractudasf: Fixed-point fractional library routines.
- (line 879)
+ (line 880)
* __fractudasi: Fixed-point fractional library routines.
- (line 876)
+ (line 877)
* __fractudasq: Fixed-point fractional library routines.
- (line 852)
+ (line 853)
* __fractudata: Fixed-point fractional library routines.
- (line 858)
+ (line 860)
* __fractudati: Fixed-point fractional library routines.
- (line 878)
+ (line 879)
* __fractudaudq: Fixed-point fractional library routines.
- (line 866)
-* __fractudauha2: Fixed-point fractional library routines.
(line 868)
+* __fractudauha2: Fixed-point fractional library routines.
+ (line 870)
* __fractudauhq: Fixed-point fractional library routines.
- (line 862)
+ (line 864)
* __fractudauqq: Fixed-point fractional library routines.
- (line 860)
+ (line 862)
* __fractudausa2: Fixed-point fractional library routines.
- (line 870)
+ (line 872)
* __fractudausq: Fixed-point fractional library routines.
- (line 864)
+ (line 866)
* __fractudauta2: Fixed-point fractional library routines.
- (line 872)
+ (line 874)
* __fractudqda: Fixed-point fractional library routines.
- (line 764)
+ (line 766)
* __fractudqdf: Fixed-point fractional library routines.
- (line 790)
+ (line 791)
* __fractudqdi: Fixed-point fractional library routines.
- (line 786)
+ (line 787)
* __fractudqdq: Fixed-point fractional library routines.
- (line 759)
-* __fractudqha: Fixed-point fractional library routines.
(line 761)
+* __fractudqha: Fixed-point fractional library routines.
+ (line 763)
* __fractudqhi: Fixed-point fractional library routines.
- (line 784)
+ (line 785)
* __fractudqhq: Fixed-point fractional library routines.
- (line 756)
+ (line 757)
* __fractudqqi: Fixed-point fractional library routines.
- (line 782)
+ (line 784)
* __fractudqqq: Fixed-point fractional library routines.
- (line 754)
+ (line 756)
* __fractudqsa: Fixed-point fractional library routines.
- (line 763)
+ (line 764)
* __fractudqsf: Fixed-point fractional library routines.
- (line 789)
+ (line 790)
* __fractudqsi: Fixed-point fractional library routines.
- (line 785)
+ (line 786)
* __fractudqsq: Fixed-point fractional library routines.
- (line 757)
+ (line 759)
* __fractudqta: Fixed-point fractional library routines.
- (line 766)
+ (line 768)
* __fractudqti: Fixed-point fractional library routines.
- (line 787)
+ (line 789)
* __fractudquda: Fixed-point fractional library routines.
- (line 778)
+ (line 780)
* __fractudquha: Fixed-point fractional library routines.
- (line 774)
+ (line 776)
* __fractudquhq2: Fixed-point fractional library routines.
- (line 770)
+ (line 772)
* __fractudquqq2: Fixed-point fractional library routines.
- (line 768)
+ (line 770)
* __fractudqusa: Fixed-point fractional library routines.
- (line 776)
+ (line 778)
* __fractudqusq2: Fixed-point fractional library routines.
- (line 772)
+ (line 774)
* __fractudquta: Fixed-point fractional library routines.
- (line 780)
+ (line 782)
* __fractuhada: Fixed-point fractional library routines.
- (line 798)
+ (line 799)
* __fractuhadf: Fixed-point fractional library routines.
- (line 821)
+ (line 822)
* __fractuhadi: Fixed-point fractional library routines.
- (line 818)
+ (line 819)
* __fractuhadq: Fixed-point fractional library routines.
- (line 794)
-* __fractuhaha: Fixed-point fractional library routines.
(line 796)
+* __fractuhaha: Fixed-point fractional library routines.
+ (line 797)
* __fractuhahi: Fixed-point fractional library routines.
- (line 816)
+ (line 817)
* __fractuhahq: Fixed-point fractional library routines.
- (line 792)
+ (line 793)
* __fractuhaqi: Fixed-point fractional library routines.
- (line 815)
+ (line 816)
* __fractuhaqq: Fixed-point fractional library routines.
- (line 791)
+ (line 792)
* __fractuhasa: Fixed-point fractional library routines.
- (line 797)
+ (line 798)
* __fractuhasf: Fixed-point fractional library routines.
- (line 820)
+ (line 821)
* __fractuhasi: Fixed-point fractional library routines.
- (line 817)
+ (line 818)
* __fractuhasq: Fixed-point fractional library routines.
- (line 793)
+ (line 794)
* __fractuhata: Fixed-point fractional library routines.
- (line 799)
+ (line 801)
* __fractuhati: Fixed-point fractional library routines.
- (line 819)
+ (line 820)
* __fractuhauda2: Fixed-point fractional library routines.
- (line 811)
+ (line 813)
* __fractuhaudq: Fixed-point fractional library routines.
- (line 807)
+ (line 809)
* __fractuhauhq: Fixed-point fractional library routines.
- (line 803)
+ (line 805)
* __fractuhauqq: Fixed-point fractional library routines.
- (line 801)
+ (line 803)
* __fractuhausa2: Fixed-point fractional library routines.
- (line 809)
+ (line 811)
* __fractuhausq: Fixed-point fractional library routines.
- (line 805)
+ (line 807)
* __fractuhauta2: Fixed-point fractional library routines.
- (line 813)
+ (line 815)
* __fractuhqda: Fixed-point fractional library routines.
- (line 701)
+ (line 702)
* __fractuhqdf: Fixed-point fractional library routines.
- (line 722)
+ (line 723)
* __fractuhqdi: Fixed-point fractional library routines.
- (line 719)
+ (line 720)
* __fractuhqdq: Fixed-point fractional library routines.
- (line 698)
-* __fractuhqha: Fixed-point fractional library routines.
(line 699)
+* __fractuhqha: Fixed-point fractional library routines.
+ (line 700)
* __fractuhqhi: Fixed-point fractional library routines.
- (line 717)
+ (line 718)
* __fractuhqhq: Fixed-point fractional library routines.
- (line 696)
+ (line 697)
* __fractuhqqi: Fixed-point fractional library routines.
- (line 716)
+ (line 717)
* __fractuhqqq: Fixed-point fractional library routines.
- (line 695)
+ (line 696)
* __fractuhqsa: Fixed-point fractional library routines.
- (line 700)
+ (line 701)
* __fractuhqsf: Fixed-point fractional library routines.
- (line 721)
+ (line 722)
* __fractuhqsi: Fixed-point fractional library routines.
- (line 718)
+ (line 719)
* __fractuhqsq: Fixed-point fractional library routines.
- (line 697)
+ (line 698)
* __fractuhqta: Fixed-point fractional library routines.
- (line 702)
+ (line 703)
* __fractuhqti: Fixed-point fractional library routines.
- (line 720)
+ (line 721)
* __fractuhquda: Fixed-point fractional library routines.
- (line 712)
+ (line 714)
* __fractuhqudq2: Fixed-point fractional library routines.
- (line 707)
-* __fractuhquha: Fixed-point fractional library routines.
(line 709)
+* __fractuhquha: Fixed-point fractional library routines.
+ (line 711)
* __fractuhquqq2: Fixed-point fractional library routines.
- (line 703)
+ (line 705)
* __fractuhqusa: Fixed-point fractional library routines.
- (line 711)
+ (line 712)
* __fractuhqusq2: Fixed-point fractional library routines.
- (line 705)
+ (line 707)
* __fractuhquta: Fixed-point fractional library routines.
- (line 714)
+ (line 716)
* __fractunsdadi: Fixed-point fractional library routines.
- (line 1554)
+ (line 1555)
* __fractunsdahi: Fixed-point fractional library routines.
- (line 1552)
+ (line 1553)
* __fractunsdaqi: Fixed-point fractional library routines.
- (line 1551)
+ (line 1552)
* __fractunsdasi: Fixed-point fractional library routines.
- (line 1553)
+ (line 1554)
* __fractunsdati: Fixed-point fractional library routines.
- (line 1555)
+ (line 1556)
* __fractunsdida: Fixed-point fractional library routines.
- (line 1706)
+ (line 1707)
* __fractunsdidq: Fixed-point fractional library routines.
- (line 1703)
-* __fractunsdiha: Fixed-point fractional library routines.
(line 1704)
+* __fractunsdiha: Fixed-point fractional library routines.
+ (line 1705)
* __fractunsdihq: Fixed-point fractional library routines.
- (line 1701)
+ (line 1702)
* __fractunsdiqq: Fixed-point fractional library routines.
- (line 1700)
+ (line 1701)
* __fractunsdisa: Fixed-point fractional library routines.
- (line 1705)
+ (line 1706)
* __fractunsdisq: Fixed-point fractional library routines.
- (line 1702)
+ (line 1703)
* __fractunsdita: Fixed-point fractional library routines.
- (line 1707)
+ (line 1708)
* __fractunsdiuda: Fixed-point fractional library routines.
- (line 1718)
+ (line 1720)
* __fractunsdiudq: Fixed-point fractional library routines.
- (line 1713)
-* __fractunsdiuha: Fixed-point fractional library routines.
(line 1715)
+* __fractunsdiuha: Fixed-point fractional library routines.
+ (line 1717)
* __fractunsdiuhq: Fixed-point fractional library routines.
- (line 1710)
+ (line 1711)
* __fractunsdiuqq: Fixed-point fractional library routines.
- (line 1708)
+ (line 1710)
* __fractunsdiusa: Fixed-point fractional library routines.
- (line 1717)
+ (line 1718)
* __fractunsdiusq: Fixed-point fractional library routines.
- (line 1711)
+ (line 1713)
* __fractunsdiuta: Fixed-point fractional library routines.
- (line 1720)
+ (line 1722)
* __fractunsdqdi: Fixed-point fractional library routines.
- (line 1538)
+ (line 1539)
* __fractunsdqhi: Fixed-point fractional library routines.
- (line 1536)
+ (line 1537)
* __fractunsdqqi: Fixed-point fractional library routines.
- (line 1535)
+ (line 1536)
* __fractunsdqsi: Fixed-point fractional library routines.
- (line 1537)
+ (line 1538)
* __fractunsdqti: Fixed-point fractional library routines.
- (line 1539)
+ (line 1541)
* __fractunshadi: Fixed-point fractional library routines.
- (line 1544)
+ (line 1545)
* __fractunshahi: Fixed-point fractional library routines.
- (line 1542)
+ (line 1543)
* __fractunshaqi: Fixed-point fractional library routines.
- (line 1541)
+ (line 1542)
* __fractunshasi: Fixed-point fractional library routines.
- (line 1543)
+ (line 1544)
* __fractunshati: Fixed-point fractional library routines.
- (line 1545)
+ (line 1546)
* __fractunshida: Fixed-point fractional library routines.
- (line 1662)
+ (line 1663)
* __fractunshidq: Fixed-point fractional library routines.
- (line 1659)
-* __fractunshiha: Fixed-point fractional library routines.
(line 1660)
+* __fractunshiha: Fixed-point fractional library routines.
+ (line 1661)
* __fractunshihq: Fixed-point fractional library routines.
- (line 1657)
+ (line 1658)
* __fractunshiqq: Fixed-point fractional library routines.
- (line 1656)
+ (line 1657)
* __fractunshisa: Fixed-point fractional library routines.
- (line 1661)
+ (line 1662)
* __fractunshisq: Fixed-point fractional library routines.
- (line 1658)
+ (line 1659)
* __fractunshita: Fixed-point fractional library routines.
- (line 1663)
+ (line 1664)
* __fractunshiuda: Fixed-point fractional library routines.
- (line 1674)
+ (line 1676)
* __fractunshiudq: Fixed-point fractional library routines.
- (line 1669)
-* __fractunshiuha: Fixed-point fractional library routines.
(line 1671)
+* __fractunshiuha: Fixed-point fractional library routines.
+ (line 1673)
* __fractunshiuhq: Fixed-point fractional library routines.
- (line 1666)
+ (line 1667)
* __fractunshiuqq: Fixed-point fractional library routines.
- (line 1664)
+ (line 1666)
* __fractunshiusa: Fixed-point fractional library routines.
- (line 1673)
+ (line 1674)
* __fractunshiusq: Fixed-point fractional library routines.
- (line 1667)
+ (line 1669)
* __fractunshiuta: Fixed-point fractional library routines.
- (line 1676)
+ (line 1678)
* __fractunshqdi: Fixed-point fractional library routines.
- (line 1528)
+ (line 1529)
* __fractunshqhi: Fixed-point fractional library routines.
- (line 1526)
+ (line 1527)
* __fractunshqqi: Fixed-point fractional library routines.
- (line 1525)
+ (line 1526)
* __fractunshqsi: Fixed-point fractional library routines.
- (line 1527)
+ (line 1528)
* __fractunshqti: Fixed-point fractional library routines.
- (line 1529)
+ (line 1530)
* __fractunsqida: Fixed-point fractional library routines.
- (line 1640)
+ (line 1641)
* __fractunsqidq: Fixed-point fractional library routines.
- (line 1637)
-* __fractunsqiha: Fixed-point fractional library routines.
(line 1638)
+* __fractunsqiha: Fixed-point fractional library routines.
+ (line 1639)
* __fractunsqihq: Fixed-point fractional library routines.
- (line 1635)
+ (line 1636)
* __fractunsqiqq: Fixed-point fractional library routines.
- (line 1634)
+ (line 1635)
* __fractunsqisa: Fixed-point fractional library routines.
- (line 1639)
+ (line 1640)
* __fractunsqisq: Fixed-point fractional library routines.
- (line 1636)
+ (line 1637)
* __fractunsqita: Fixed-point fractional library routines.
- (line 1641)
+ (line 1642)
* __fractunsqiuda: Fixed-point fractional library routines.
- (line 1652)
+ (line 1654)
* __fractunsqiudq: Fixed-point fractional library routines.
- (line 1647)
-* __fractunsqiuha: Fixed-point fractional library routines.
(line 1649)
+* __fractunsqiuha: Fixed-point fractional library routines.
+ (line 1651)
* __fractunsqiuhq: Fixed-point fractional library routines.
- (line 1644)
+ (line 1645)
* __fractunsqiuqq: Fixed-point fractional library routines.
- (line 1642)
+ (line 1644)
* __fractunsqiusa: Fixed-point fractional library routines.
- (line 1651)
+ (line 1652)
* __fractunsqiusq: Fixed-point fractional library routines.
- (line 1645)
+ (line 1647)
* __fractunsqiuta: Fixed-point fractional library routines.
- (line 1654)
+ (line 1656)
* __fractunsqqdi: Fixed-point fractional library routines.
- (line 1523)
+ (line 1524)
* __fractunsqqhi: Fixed-point fractional library routines.
- (line 1521)
+ (line 1522)
* __fractunsqqqi: Fixed-point fractional library routines.
- (line 1520)
+ (line 1521)
* __fractunsqqsi: Fixed-point fractional library routines.
- (line 1522)
+ (line 1523)
* __fractunsqqti: Fixed-point fractional library routines.
- (line 1524)
+ (line 1525)
* __fractunssadi: Fixed-point fractional library routines.
- (line 1549)
+ (line 1550)
* __fractunssahi: Fixed-point fractional library routines.
- (line 1547)
+ (line 1548)
* __fractunssaqi: Fixed-point fractional library routines.
- (line 1546)
+ (line 1547)
* __fractunssasi: Fixed-point fractional library routines.
- (line 1548)
+ (line 1549)
* __fractunssati: Fixed-point fractional library routines.
- (line 1550)
+ (line 1551)
* __fractunssida: Fixed-point fractional library routines.
- (line 1684)
+ (line 1685)
* __fractunssidq: Fixed-point fractional library routines.
- (line 1681)
-* __fractunssiha: Fixed-point fractional library routines.
(line 1682)
+* __fractunssiha: Fixed-point fractional library routines.
+ (line 1683)
* __fractunssihq: Fixed-point fractional library routines.
- (line 1679)
+ (line 1680)
* __fractunssiqq: Fixed-point fractional library routines.
- (line 1678)
+ (line 1679)
* __fractunssisa: Fixed-point fractional library routines.
- (line 1683)
+ (line 1684)
* __fractunssisq: Fixed-point fractional library routines.
- (line 1680)
+ (line 1681)
* __fractunssita: Fixed-point fractional library routines.
- (line 1685)
+ (line 1686)
* __fractunssiuda: Fixed-point fractional library routines.
- (line 1696)
+ (line 1698)
* __fractunssiudq: Fixed-point fractional library routines.
- (line 1691)
-* __fractunssiuha: Fixed-point fractional library routines.
(line 1693)
+* __fractunssiuha: Fixed-point fractional library routines.
+ (line 1695)
* __fractunssiuhq: Fixed-point fractional library routines.
- (line 1688)
+ (line 1689)
* __fractunssiuqq: Fixed-point fractional library routines.
- (line 1686)
+ (line 1688)
* __fractunssiusa: Fixed-point fractional library routines.
- (line 1695)
+ (line 1696)
* __fractunssiusq: Fixed-point fractional library routines.
- (line 1689)
+ (line 1691)
* __fractunssiuta: Fixed-point fractional library routines.
- (line 1698)
+ (line 1700)
* __fractunssqdi: Fixed-point fractional library routines.
- (line 1533)
+ (line 1534)
* __fractunssqhi: Fixed-point fractional library routines.
- (line 1531)
+ (line 1532)
* __fractunssqqi: Fixed-point fractional library routines.
- (line 1530)
+ (line 1531)
* __fractunssqsi: Fixed-point fractional library routines.
- (line 1532)
+ (line 1533)
* __fractunssqti: Fixed-point fractional library routines.
- (line 1534)
+ (line 1535)
* __fractunstadi: Fixed-point fractional library routines.
- (line 1559)
+ (line 1560)
* __fractunstahi: Fixed-point fractional library routines.
- (line 1557)
+ (line 1558)
* __fractunstaqi: Fixed-point fractional library routines.
- (line 1556)
+ (line 1557)
* __fractunstasi: Fixed-point fractional library routines.
- (line 1558)
+ (line 1559)
* __fractunstati: Fixed-point fractional library routines.
- (line 1560)
+ (line 1562)
* __fractunstida: Fixed-point fractional library routines.
- (line 1729)
+ (line 1730)
* __fractunstidq: Fixed-point fractional library routines.
- (line 1725)
-* __fractunstiha: Fixed-point fractional library routines.
(line 1727)
+* __fractunstiha: Fixed-point fractional library routines.
+ (line 1728)
* __fractunstihq: Fixed-point fractional library routines.
- (line 1723)
+ (line 1724)
* __fractunstiqq: Fixed-point fractional library routines.
- (line 1722)
+ (line 1723)
* __fractunstisa: Fixed-point fractional library routines.
- (line 1728)
+ (line 1729)
* __fractunstisq: Fixed-point fractional library routines.
- (line 1724)
+ (line 1725)
* __fractunstita: Fixed-point fractional library routines.
- (line 1730)
+ (line 1732)
* __fractunstiuda: Fixed-point fractional library routines.
- (line 1744)
+ (line 1746)
* __fractunstiudq: Fixed-point fractional library routines.
- (line 1738)
-* __fractunstiuha: Fixed-point fractional library routines.
(line 1740)
+* __fractunstiuha: Fixed-point fractional library routines.
+ (line 1742)
* __fractunstiuhq: Fixed-point fractional library routines.
- (line 1734)
+ (line 1736)
* __fractunstiuqq: Fixed-point fractional library routines.
- (line 1732)
+ (line 1734)
* __fractunstiusa: Fixed-point fractional library routines.
- (line 1742)
+ (line 1744)
* __fractunstiusq: Fixed-point fractional library routines.
- (line 1736)
+ (line 1738)
* __fractunstiuta: Fixed-point fractional library routines.
- (line 1746)
+ (line 1748)
* __fractunsudadi: Fixed-point fractional library routines.
- (line 1620)
+ (line 1622)
* __fractunsudahi: Fixed-point fractional library routines.
- (line 1616)
+ (line 1618)
* __fractunsudaqi: Fixed-point fractional library routines.
- (line 1614)
+ (line 1616)
* __fractunsudasi: Fixed-point fractional library routines.
- (line 1618)
+ (line 1620)
* __fractunsudati: Fixed-point fractional library routines.
- (line 1622)
+ (line 1624)
* __fractunsudqdi: Fixed-point fractional library routines.
- (line 1594)
+ (line 1596)
* __fractunsudqhi: Fixed-point fractional library routines.
- (line 1590)
+ (line 1592)
* __fractunsudqqi: Fixed-point fractional library routines.
- (line 1588)
+ (line 1590)
* __fractunsudqsi: Fixed-point fractional library routines.
- (line 1592)
+ (line 1594)
* __fractunsudqti: Fixed-point fractional library routines.
- (line 1596)
+ (line 1598)
* __fractunsuhadi: Fixed-point fractional library routines.
- (line 1604)
+ (line 1606)
* __fractunsuhahi: Fixed-point fractional library routines.
- (line 1600)
+ (line 1602)
* __fractunsuhaqi: Fixed-point fractional library routines.
- (line 1598)
+ (line 1600)
* __fractunsuhasi: Fixed-point fractional library routines.
- (line 1602)
+ (line 1604)
* __fractunsuhati: Fixed-point fractional library routines.
- (line 1606)
+ (line 1608)
* __fractunsuhqdi: Fixed-point fractional library routines.
- (line 1575)
+ (line 1576)
* __fractunsuhqhi: Fixed-point fractional library routines.
- (line 1573)
+ (line 1574)
* __fractunsuhqqi: Fixed-point fractional library routines.
- (line 1572)
+ (line 1573)
* __fractunsuhqsi: Fixed-point fractional library routines.
- (line 1574)
+ (line 1575)
* __fractunsuhqti: Fixed-point fractional library routines.
- (line 1576)
+ (line 1578)
* __fractunsuqqdi: Fixed-point fractional library routines.
- (line 1568)
+ (line 1570)
* __fractunsuqqhi: Fixed-point fractional library routines.
- (line 1564)
+ (line 1566)
* __fractunsuqqqi: Fixed-point fractional library routines.
- (line 1562)
+ (line 1564)
* __fractunsuqqsi: Fixed-point fractional library routines.
- (line 1566)
+ (line 1568)
* __fractunsuqqti: Fixed-point fractional library routines.
- (line 1570)
+ (line 1572)
* __fractunsusadi: Fixed-point fractional library routines.
- (line 1611)
+ (line 1612)
* __fractunsusahi: Fixed-point fractional library routines.
- (line 1609)
+ (line 1610)
* __fractunsusaqi: Fixed-point fractional library routines.
- (line 1608)
+ (line 1609)
* __fractunsusasi: Fixed-point fractional library routines.
- (line 1610)
+ (line 1611)
* __fractunsusati: Fixed-point fractional library routines.
- (line 1612)
+ (line 1614)
* __fractunsusqdi: Fixed-point fractional library routines.
- (line 1584)
+ (line 1586)
* __fractunsusqhi: Fixed-point fractional library routines.
- (line 1580)
+ (line 1582)
* __fractunsusqqi: Fixed-point fractional library routines.
- (line 1578)
+ (line 1580)
* __fractunsusqsi: Fixed-point fractional library routines.
- (line 1582)
+ (line 1584)
* __fractunsusqti: Fixed-point fractional library routines.
- (line 1586)
+ (line 1588)
* __fractunsutadi: Fixed-point fractional library routines.
- (line 1630)
+ (line 1632)
* __fractunsutahi: Fixed-point fractional library routines.
- (line 1626)
+ (line 1628)
* __fractunsutaqi: Fixed-point fractional library routines.
- (line 1624)
+ (line 1626)
* __fractunsutasi: Fixed-point fractional library routines.
- (line 1628)
+ (line 1630)
* __fractunsutati: Fixed-point fractional library routines.
- (line 1632)
+ (line 1634)
* __fractuqqda: Fixed-point fractional library routines.
- (line 671)
+ (line 672)
* __fractuqqdf: Fixed-point fractional library routines.
- (line 694)
+ (line 695)
* __fractuqqdi: Fixed-point fractional library routines.
- (line 691)
+ (line 692)
* __fractuqqdq: Fixed-point fractional library routines.
- (line 667)
-* __fractuqqha: Fixed-point fractional library routines.
(line 669)
+* __fractuqqha: Fixed-point fractional library routines.
+ (line 670)
* __fractuqqhi: Fixed-point fractional library routines.
- (line 689)
+ (line 690)
* __fractuqqhq: Fixed-point fractional library routines.
- (line 665)
+ (line 666)
* __fractuqqqi: Fixed-point fractional library routines.
- (line 688)
+ (line 689)
* __fractuqqqq: Fixed-point fractional library routines.
- (line 664)
+ (line 665)
* __fractuqqsa: Fixed-point fractional library routines.
- (line 670)
+ (line 671)
* __fractuqqsf: Fixed-point fractional library routines.
- (line 693)
+ (line 694)
* __fractuqqsi: Fixed-point fractional library routines.
- (line 690)
+ (line 691)
* __fractuqqsq: Fixed-point fractional library routines.
- (line 666)
+ (line 667)
* __fractuqqta: Fixed-point fractional library routines.
- (line 672)
+ (line 674)
* __fractuqqti: Fixed-point fractional library routines.
- (line 692)
+ (line 693)
* __fractuqquda: Fixed-point fractional library routines.
- (line 684)
+ (line 686)
* __fractuqqudq2: Fixed-point fractional library routines.
- (line 678)
-* __fractuqquha: Fixed-point fractional library routines.
(line 680)
+* __fractuqquha: Fixed-point fractional library routines.
+ (line 682)
* __fractuqquhq2: Fixed-point fractional library routines.
- (line 674)
+ (line 676)
* __fractuqqusa: Fixed-point fractional library routines.
- (line 682)
+ (line 684)
* __fractuqqusq2: Fixed-point fractional library routines.
- (line 676)
+ (line 678)
* __fractuqquta: Fixed-point fractional library routines.
- (line 686)
+ (line 688)
* __fractusada: Fixed-point fractional library routines.
- (line 828)
+ (line 829)
* __fractusadf: Fixed-point fractional library routines.
- (line 849)
+ (line 850)
* __fractusadi: Fixed-point fractional library routines.
- (line 846)
+ (line 847)
* __fractusadq: Fixed-point fractional library routines.
- (line 825)
-* __fractusaha: Fixed-point fractional library routines.
(line 826)
+* __fractusaha: Fixed-point fractional library routines.
+ (line 827)
* __fractusahi: Fixed-point fractional library routines.
- (line 844)
+ (line 845)
* __fractusahq: Fixed-point fractional library routines.
- (line 823)
+ (line 824)
* __fractusaqi: Fixed-point fractional library routines.
- (line 843)
+ (line 844)
* __fractusaqq: Fixed-point fractional library routines.
- (line 822)
+ (line 823)
* __fractusasa: Fixed-point fractional library routines.
- (line 827)
+ (line 828)
* __fractusasf: Fixed-point fractional library routines.
- (line 848)
+ (line 849)
* __fractusasi: Fixed-point fractional library routines.
- (line 845)
+ (line 846)
* __fractusasq: Fixed-point fractional library routines.
- (line 824)
+ (line 825)
* __fractusata: Fixed-point fractional library routines.
- (line 829)
+ (line 830)
* __fractusati: Fixed-point fractional library routines.
- (line 847)
+ (line 848)
* __fractusauda2: Fixed-point fractional library routines.
- (line 839)
+ (line 841)
* __fractusaudq: Fixed-point fractional library routines.
- (line 835)
-* __fractusauha2: Fixed-point fractional library routines.
(line 837)
+* __fractusauha2: Fixed-point fractional library routines.
+ (line 839)
* __fractusauhq: Fixed-point fractional library routines.
- (line 832)
+ (line 833)
* __fractusauqq: Fixed-point fractional library routines.
- (line 830)
+ (line 832)
* __fractusausq: Fixed-point fractional library routines.
- (line 833)
+ (line 835)
* __fractusauta2: Fixed-point fractional library routines.
- (line 841)
+ (line 843)
* __fractusqda: Fixed-point fractional library routines.
- (line 730)
+ (line 731)
* __fractusqdf: Fixed-point fractional library routines.
- (line 753)
+ (line 754)
* __fractusqdi: Fixed-point fractional library routines.
- (line 750)
+ (line 751)
* __fractusqdq: Fixed-point fractional library routines.
- (line 726)
-* __fractusqha: Fixed-point fractional library routines.
(line 728)
+* __fractusqha: Fixed-point fractional library routines.
+ (line 729)
* __fractusqhi: Fixed-point fractional library routines.
- (line 748)
+ (line 749)
* __fractusqhq: Fixed-point fractional library routines.
- (line 724)
+ (line 725)
* __fractusqqi: Fixed-point fractional library routines.
- (line 747)
+ (line 748)
* __fractusqqq: Fixed-point fractional library routines.
- (line 723)
+ (line 724)
* __fractusqsa: Fixed-point fractional library routines.
- (line 729)
+ (line 730)
* __fractusqsf: Fixed-point fractional library routines.
- (line 752)
+ (line 753)
* __fractusqsi: Fixed-point fractional library routines.
- (line 749)
+ (line 750)
* __fractusqsq: Fixed-point fractional library routines.
- (line 725)
+ (line 726)
* __fractusqta: Fixed-point fractional library routines.
- (line 731)
+ (line 733)
* __fractusqti: Fixed-point fractional library routines.
- (line 751)
+ (line 752)
* __fractusquda: Fixed-point fractional library routines.
- (line 743)
+ (line 745)
* __fractusqudq2: Fixed-point fractional library routines.
- (line 737)
-* __fractusquha: Fixed-point fractional library routines.
(line 739)
+* __fractusquha: Fixed-point fractional library routines.
+ (line 741)
* __fractusquhq2: Fixed-point fractional library routines.
- (line 735)
+ (line 737)
* __fractusquqq2: Fixed-point fractional library routines.
- (line 733)
+ (line 735)
* __fractusqusa: Fixed-point fractional library routines.
- (line 741)
+ (line 743)
* __fractusquta: Fixed-point fractional library routines.
- (line 745)
+ (line 747)
* __fractutada: Fixed-point fractional library routines.
- (line 891)
+ (line 893)
* __fractutadf: Fixed-point fractional library routines.
- (line 917)
+ (line 918)
* __fractutadi: Fixed-point fractional library routines.
- (line 913)
+ (line 914)
* __fractutadq: Fixed-point fractional library routines.
- (line 886)
-* __fractutaha: Fixed-point fractional library routines.
(line 888)
+* __fractutaha: Fixed-point fractional library routines.
+ (line 890)
* __fractutahi: Fixed-point fractional library routines.
- (line 911)
+ (line 912)
* __fractutahq: Fixed-point fractional library routines.
- (line 883)
+ (line 884)
* __fractutaqi: Fixed-point fractional library routines.
- (line 909)
+ (line 911)
* __fractutaqq: Fixed-point fractional library routines.
- (line 881)
+ (line 883)
* __fractutasa: Fixed-point fractional library routines.
- (line 890)
+ (line 891)
* __fractutasf: Fixed-point fractional library routines.
- (line 916)
+ (line 917)
* __fractutasi: Fixed-point fractional library routines.
- (line 912)
+ (line 913)
* __fractutasq: Fixed-point fractional library routines.
- (line 884)
+ (line 886)
* __fractutata: Fixed-point fractional library routines.
- (line 893)
+ (line 895)
* __fractutati: Fixed-point fractional library routines.
- (line 914)
+ (line 916)
* __fractutauda2: Fixed-point fractional library routines.
- (line 907)
+ (line 909)
* __fractutaudq: Fixed-point fractional library routines.
- (line 901)
-* __fractutauha2: Fixed-point fractional library routines.
(line 903)
+* __fractutauha2: Fixed-point fractional library routines.
+ (line 905)
* __fractutauhq: Fixed-point fractional library routines.
- (line 897)
+ (line 899)
* __fractutauqq: Fixed-point fractional library routines.
- (line 895)
+ (line 897)
* __fractutausa2: Fixed-point fractional library routines.
- (line 905)
+ (line 907)
* __fractutausq: Fixed-point fractional library routines.
- (line 899)
+ (line 901)
* __gedf2: Soft float library routines.
- (line 205)
+ (line 206)
* __gesf2: Soft float library routines.
- (line 204)
+ (line 205)
* __getf2: Soft float library routines.
- (line 206)
+ (line 207)
* __gtdf2: Soft float library routines.
- (line 223)
+ (line 224)
* __gtsf2: Soft float library routines.
- (line 222)
+ (line 223)
* __gttf2: Soft float library routines.
- (line 224)
+ (line 225)
* __ledf2: Soft float library routines.
- (line 217)
+ (line 218)
* __lesf2: Soft float library routines.
- (line 216)
+ (line 217)
* __letf2: Soft float library routines.
- (line 218)
+ (line 219)
* __lshrdi3: Integer library routines.
- (line 30)
+ (line 31)
* __lshrsi3: Integer library routines.
- (line 29)
+ (line 30)
* __lshrti3: Integer library routines.
- (line 31)
+ (line 32)
* __lshruda3: Fixed-point fractional library routines.
- (line 388)
+ (line 390)
* __lshrudq3: Fixed-point fractional library routines.
- (line 382)
-* __lshruha3: Fixed-point fractional library routines.
(line 384)
+* __lshruha3: Fixed-point fractional library routines.
+ (line 386)
* __lshruhq3: Fixed-point fractional library routines.
- (line 378)
+ (line 380)
* __lshruqq3: Fixed-point fractional library routines.
- (line 376)
+ (line 378)
* __lshrusa3: Fixed-point fractional library routines.
- (line 386)
+ (line 388)
* __lshrusq3: Fixed-point fractional library routines.
- (line 380)
+ (line 382)
* __lshruta3: Fixed-point fractional library routines.
- (line 390)
+ (line 392)
* __ltdf2: Soft float library routines.
- (line 211)
+ (line 212)
* __ltsf2: Soft float library routines.
- (line 210)
+ (line 211)
* __lttf2: Soft float library routines.
- (line 212)
+ (line 213)
* __main: Collect2. (line 15)
* __moddi3: Integer library routines.
- (line 36)
+ (line 37)
* __modsi3: Integer library routines.
- (line 35)
+ (line 36)
* __modti3: Integer library routines.
- (line 37)
+ (line 38)
* __morestack_current_segment: Miscellaneous routines.
- (line 45)
-* __morestack_initial_sp: Miscellaneous routines.
(line 46)
+* __morestack_initial_sp: Miscellaneous routines.
+ (line 47)
* __morestack_segments: Miscellaneous routines.
- (line 44)
+ (line 45)
* __mulda3: Fixed-point fractional library routines.
- (line 170)
+ (line 171)
* __muldc3: Soft float library routines.
- (line 239)
+ (line 241)
* __muldf3: Soft float library routines.
- (line 39)
+ (line 40)
* __muldi3: Integer library routines.
- (line 42)
+ (line 43)
* __muldq3: Fixed-point fractional library routines.
- (line 157)
+ (line 159)
* __mulha3: Fixed-point fractional library routines.
- (line 167)
+ (line 169)
* __mulhq3: Fixed-point fractional library routines.
- (line 155)
+ (line 156)
* __mulqq3: Fixed-point fractional library routines.
- (line 153)
+ (line 155)
* __mulsa3: Fixed-point fractional library routines.
- (line 169)
+ (line 170)
* __mulsc3: Soft float library routines.
- (line 237)
+ (line 239)
* __mulsf3: Soft float library routines.
- (line 38)
+ (line 39)
* __mulsi3: Integer library routines.
- (line 41)
+ (line 42)
* __mulsq3: Fixed-point fractional library routines.
- (line 156)
+ (line 157)
* __multa3: Fixed-point fractional library routines.
- (line 171)
+ (line 173)
* __multc3: Soft float library routines.
- (line 241)
+ (line 243)
* __multf3: Soft float library routines.
- (line 40)
+ (line 42)
* __multi3: Integer library routines.
- (line 43)
+ (line 44)
* __muluda3: Fixed-point fractional library routines.
- (line 177)
+ (line 179)
* __muludq3: Fixed-point fractional library routines.
- (line 165)
+ (line 167)
* __muluha3: Fixed-point fractional library routines.
- (line 173)
+ (line 175)
* __muluhq3: Fixed-point fractional library routines.
- (line 161)
+ (line 163)
* __muluqq3: Fixed-point fractional library routines.
- (line 159)
+ (line 161)
* __mulusa3: Fixed-point fractional library routines.
- (line 175)
+ (line 177)
* __mulusq3: Fixed-point fractional library routines.
- (line 163)
+ (line 165)
* __muluta3: Fixed-point fractional library routines.
- (line 179)
+ (line 181)
* __mulvdi3: Integer library routines.
- (line 114)
+ (line 115)
* __mulvsi3: Integer library routines.
- (line 113)
+ (line 114)
* __mulxc3: Soft float library routines.
- (line 243)
+ (line 245)
* __mulxf3: Soft float library routines.
- (line 42)
+ (line 44)
* __nedf2: Soft float library routines.
- (line 199)
+ (line 200)
* __negda2: Fixed-point fractional library routines.
- (line 298)
+ (line 299)
* __negdf2: Soft float library routines.
- (line 55)
+ (line 56)
* __negdi2: Integer library routines.
- (line 46)
+ (line 47)
* __negdq2: Fixed-point fractional library routines.
- (line 288)
+ (line 289)
* __negha2: Fixed-point fractional library routines.
- (line 296)
+ (line 297)
* __neghq2: Fixed-point fractional library routines.
- (line 286)
+ (line 287)
* __negqq2: Fixed-point fractional library routines.
- (line 285)
+ (line 286)
* __negsa2: Fixed-point fractional library routines.
- (line 297)
+ (line 298)
* __negsf2: Soft float library routines.
- (line 54)
+ (line 55)
* __negsq2: Fixed-point fractional library routines.
- (line 287)
+ (line 288)
* __negta2: Fixed-point fractional library routines.
- (line 299)
+ (line 300)
* __negtf2: Soft float library routines.
- (line 56)
+ (line 57)
* __negti2: Integer library routines.
- (line 47)
+ (line 48)
* __neguda2: Fixed-point fractional library routines.
- (line 303)
+ (line 305)
* __negudq2: Fixed-point fractional library routines.
- (line 294)
+ (line 296)
* __neguha2: Fixed-point fractional library routines.
- (line 300)
+ (line 302)
* __neguhq2: Fixed-point fractional library routines.
- (line 291)
+ (line 292)
* __neguqq2: Fixed-point fractional library routines.
- (line 289)
+ (line 291)
* __negusa2: Fixed-point fractional library routines.
- (line 302)
+ (line 303)
* __negusq2: Fixed-point fractional library routines.
- (line 292)
+ (line 294)
* __neguta2: Fixed-point fractional library routines.
- (line 305)
+ (line 307)
* __negvdi2: Integer library routines.
- (line 118)
+ (line 119)
* __negvsi2: Integer library routines.
- (line 117)
+ (line 118)
* __negxf2: Soft float library routines.
- (line 57)
+ (line 58)
* __nesf2: Soft float library routines.
- (line 198)
+ (line 199)
* __netf2: Soft float library routines.
- (line 200)
+ (line 201)
* __paritydi2: Integer library routines.
- (line 150)
+ (line 151)
* __paritysi2: Integer library routines.
- (line 149)
+ (line 150)
* __parityti2: Integer library routines.
- (line 151)
+ (line 152)
* __popcountdi2: Integer library routines.
- (line 156)
+ (line 157)
* __popcountsi2: Integer library routines.
- (line 155)
+ (line 156)
* __popcountti2: Integer library routines.
- (line 157)
+ (line 158)
* __powidf2: Soft float library routines.
- (line 232)
+ (line 233)
* __powisf2: Soft float library routines.
- (line 231)
+ (line 232)
* __powitf2: Soft float library routines.
- (line 233)
-* __powixf2: Soft float library routines.
(line 234)
+* __powixf2: Soft float library routines.
+ (line 235)
* __satfractdadq: Fixed-point fractional library routines.
- (line 1152)
-* __satfractdaha2: Fixed-point fractional library routines.
(line 1153)
+* __satfractdaha2: Fixed-point fractional library routines.
+ (line 1154)
* __satfractdahq: Fixed-point fractional library routines.
- (line 1150)
+ (line 1151)
* __satfractdaqq: Fixed-point fractional library routines.
- (line 1149)
+ (line 1150)
* __satfractdasa2: Fixed-point fractional library routines.
- (line 1154)
+ (line 1155)
* __satfractdasq: Fixed-point fractional library routines.
- (line 1151)
+ (line 1152)
* __satfractdata2: Fixed-point fractional library routines.
- (line 1155)
+ (line 1156)
* __satfractdauda: Fixed-point fractional library routines.
- (line 1165)
+ (line 1166)
* __satfractdaudq: Fixed-point fractional library routines.
- (line 1160)
-* __satfractdauha: Fixed-point fractional library routines.
(line 1162)
+* __satfractdauha: Fixed-point fractional library routines.
+ (line 1164)
* __satfractdauhq: Fixed-point fractional library routines.
- (line 1158)
+ (line 1159)
* __satfractdauqq: Fixed-point fractional library routines.
- (line 1156)
+ (line 1158)
* __satfractdausa: Fixed-point fractional library routines.
- (line 1164)
+ (line 1165)
* __satfractdausq: Fixed-point fractional library routines.
- (line 1159)
+ (line 1160)
* __satfractdauta: Fixed-point fractional library routines.
- (line 1166)
+ (line 1168)
* __satfractdfda: Fixed-point fractional library routines.
- (line 1505)
+ (line 1506)
* __satfractdfdq: Fixed-point fractional library routines.
- (line 1502)
-* __satfractdfha: Fixed-point fractional library routines.
(line 1503)
+* __satfractdfha: Fixed-point fractional library routines.
+ (line 1504)
* __satfractdfhq: Fixed-point fractional library routines.
- (line 1500)
+ (line 1501)
* __satfractdfqq: Fixed-point fractional library routines.
- (line 1499)
+ (line 1500)
* __satfractdfsa: Fixed-point fractional library routines.
- (line 1504)
+ (line 1505)
* __satfractdfsq: Fixed-point fractional library routines.
- (line 1501)
+ (line 1502)
* __satfractdfta: Fixed-point fractional library routines.
- (line 1506)
+ (line 1507)
* __satfractdfuda: Fixed-point fractional library routines.
- (line 1514)
+ (line 1515)
* __satfractdfudq: Fixed-point fractional library routines.
- (line 1510)
-* __satfractdfuha: Fixed-point fractional library routines.
(line 1512)
+* __satfractdfuha: Fixed-point fractional library routines.
+ (line 1513)
* __satfractdfuhq: Fixed-point fractional library routines.
- (line 1508)
+ (line 1509)
* __satfractdfuqq: Fixed-point fractional library routines.
- (line 1507)
+ (line 1508)
* __satfractdfusa: Fixed-point fractional library routines.
- (line 1513)
+ (line 1514)
* __satfractdfusq: Fixed-point fractional library routines.
- (line 1509)
+ (line 1510)
* __satfractdfuta: Fixed-point fractional library routines.
- (line 1515)
+ (line 1517)
* __satfractdida: Fixed-point fractional library routines.
- (line 1455)
+ (line 1456)
* __satfractdidq: Fixed-point fractional library routines.
- (line 1452)
-* __satfractdiha: Fixed-point fractional library routines.
(line 1453)
+* __satfractdiha: Fixed-point fractional library routines.
+ (line 1454)
* __satfractdihq: Fixed-point fractional library routines.
- (line 1450)
+ (line 1451)
* __satfractdiqq: Fixed-point fractional library routines.
- (line 1449)
+ (line 1450)
* __satfractdisa: Fixed-point fractional library routines.
- (line 1454)
+ (line 1455)
* __satfractdisq: Fixed-point fractional library routines.
- (line 1451)
+ (line 1452)
* __satfractdita: Fixed-point fractional library routines.
- (line 1456)
+ (line 1457)
* __satfractdiuda: Fixed-point fractional library routines.
- (line 1463)
+ (line 1464)
* __satfractdiudq: Fixed-point fractional library routines.
- (line 1460)
-* __satfractdiuha: Fixed-point fractional library routines.
(line 1461)
+* __satfractdiuha: Fixed-point fractional library routines.
+ (line 1462)
* __satfractdiuhq: Fixed-point fractional library routines.
- (line 1458)
+ (line 1459)
* __satfractdiuqq: Fixed-point fractional library routines.
- (line 1457)
+ (line 1458)
* __satfractdiusa: Fixed-point fractional library routines.
- (line 1462)
+ (line 1463)
* __satfractdiusq: Fixed-point fractional library routines.
- (line 1459)
+ (line 1460)
* __satfractdiuta: Fixed-point fractional library routines.
- (line 1464)
+ (line 1465)
* __satfractdqda: Fixed-point fractional library routines.
- (line 1097)
+ (line 1098)
* __satfractdqha: Fixed-point fractional library routines.
- (line 1095)
+ (line 1096)
* __satfractdqhq2: Fixed-point fractional library routines.
- (line 1093)
+ (line 1094)
* __satfractdqqq2: Fixed-point fractional library routines.
- (line 1092)
+ (line 1093)
* __satfractdqsa: Fixed-point fractional library routines.
- (line 1096)
+ (line 1097)
* __satfractdqsq2: Fixed-point fractional library routines.
- (line 1094)
+ (line 1095)
* __satfractdqta: Fixed-point fractional library routines.
- (line 1098)
+ (line 1099)
* __satfractdquda: Fixed-point fractional library routines.
- (line 1109)
+ (line 1111)
* __satfractdqudq: Fixed-point fractional library routines.
- (line 1104)
-* __satfractdquha: Fixed-point fractional library routines.
(line 1106)
+* __satfractdquha: Fixed-point fractional library routines.
+ (line 1108)
* __satfractdquhq: Fixed-point fractional library routines.
- (line 1101)
+ (line 1102)
* __satfractdquqq: Fixed-point fractional library routines.
- (line 1099)
+ (line 1101)
* __satfractdqusa: Fixed-point fractional library routines.
- (line 1108)
+ (line 1109)
* __satfractdqusq: Fixed-point fractional library routines.
- (line 1102)
+ (line 1104)
* __satfractdquta: Fixed-point fractional library routines.
- (line 1111)
+ (line 1113)
* __satfracthada2: Fixed-point fractional library routines.
- (line 1118)
+ (line 1119)
* __satfracthadq: Fixed-point fractional library routines.
- (line 1116)
+ (line 1117)
* __satfracthahq: Fixed-point fractional library routines.
- (line 1114)
+ (line 1115)
* __satfracthaqq: Fixed-point fractional library routines.
- (line 1113)
+ (line 1114)
* __satfracthasa2: Fixed-point fractional library routines.
- (line 1117)
+ (line 1118)
* __satfracthasq: Fixed-point fractional library routines.
- (line 1115)
+ (line 1116)
* __satfracthata2: Fixed-point fractional library routines.
- (line 1119)
+ (line 1120)
* __satfracthauda: Fixed-point fractional library routines.
- (line 1130)
+ (line 1132)
* __satfracthaudq: Fixed-point fractional library routines.
- (line 1125)
-* __satfracthauha: Fixed-point fractional library routines.
(line 1127)
+* __satfracthauha: Fixed-point fractional library routines.
+ (line 1129)
* __satfracthauhq: Fixed-point fractional library routines.
- (line 1122)
+ (line 1123)
* __satfracthauqq: Fixed-point fractional library routines.
- (line 1120)
+ (line 1122)
* __satfracthausa: Fixed-point fractional library routines.
- (line 1129)
+ (line 1130)
* __satfracthausq: Fixed-point fractional library routines.
- (line 1123)
+ (line 1125)
* __satfracthauta: Fixed-point fractional library routines.
- (line 1132)
+ (line 1134)
* __satfracthida: Fixed-point fractional library routines.
- (line 1423)
+ (line 1424)
* __satfracthidq: Fixed-point fractional library routines.
- (line 1420)
-* __satfracthiha: Fixed-point fractional library routines.
(line 1421)
+* __satfracthiha: Fixed-point fractional library routines.
+ (line 1422)
* __satfracthihq: Fixed-point fractional library routines.
- (line 1418)
+ (line 1419)
* __satfracthiqq: Fixed-point fractional library routines.
- (line 1417)
+ (line 1418)
* __satfracthisa: Fixed-point fractional library routines.
- (line 1422)
+ (line 1423)
* __satfracthisq: Fixed-point fractional library routines.
- (line 1419)
+ (line 1420)
* __satfracthita: Fixed-point fractional library routines.
- (line 1424)
+ (line 1425)
* __satfracthiuda: Fixed-point fractional library routines.
- (line 1431)
+ (line 1432)
* __satfracthiudq: Fixed-point fractional library routines.
- (line 1428)
-* __satfracthiuha: Fixed-point fractional library routines.
(line 1429)
+* __satfracthiuha: Fixed-point fractional library routines.
+ (line 1430)
* __satfracthiuhq: Fixed-point fractional library routines.
- (line 1426)
+ (line 1427)
* __satfracthiuqq: Fixed-point fractional library routines.
- (line 1425)
+ (line 1426)
* __satfracthiusa: Fixed-point fractional library routines.
- (line 1430)
+ (line 1431)
* __satfracthiusq: Fixed-point fractional library routines.
- (line 1427)
+ (line 1428)
* __satfracthiuta: Fixed-point fractional library routines.
- (line 1432)
+ (line 1433)
* __satfracthqda: Fixed-point fractional library routines.
- (line 1063)
+ (line 1064)
* __satfracthqdq2: Fixed-point fractional library routines.
- (line 1060)
-* __satfracthqha: Fixed-point fractional library routines.
(line 1061)
+* __satfracthqha: Fixed-point fractional library routines.
+ (line 1062)
* __satfracthqqq2: Fixed-point fractional library routines.
- (line 1058)
+ (line 1059)
* __satfracthqsa: Fixed-point fractional library routines.
- (line 1062)
+ (line 1063)
* __satfracthqsq2: Fixed-point fractional library routines.
- (line 1059)
+ (line 1060)
* __satfracthqta: Fixed-point fractional library routines.
- (line 1064)
+ (line 1065)
* __satfracthquda: Fixed-point fractional library routines.
- (line 1071)
+ (line 1072)
* __satfracthqudq: Fixed-point fractional library routines.
- (line 1068)
-* __satfracthquha: Fixed-point fractional library routines.
(line 1069)
+* __satfracthquha: Fixed-point fractional library routines.
+ (line 1070)
* __satfracthquhq: Fixed-point fractional library routines.
- (line 1066)
+ (line 1067)
* __satfracthquqq: Fixed-point fractional library routines.
- (line 1065)
+ (line 1066)
* __satfracthqusa: Fixed-point fractional library routines.
- (line 1070)
+ (line 1071)
* __satfracthqusq: Fixed-point fractional library routines.
- (line 1067)
+ (line 1068)
* __satfracthquta: Fixed-point fractional library routines.
- (line 1072)
+ (line 1073)
* __satfractqida: Fixed-point fractional library routines.
- (line 1401)
+ (line 1402)
* __satfractqidq: Fixed-point fractional library routines.
- (line 1398)
-* __satfractqiha: Fixed-point fractional library routines.
(line 1399)
+* __satfractqiha: Fixed-point fractional library routines.
+ (line 1400)
* __satfractqihq: Fixed-point fractional library routines.
- (line 1396)
+ (line 1397)
* __satfractqiqq: Fixed-point fractional library routines.
- (line 1395)
+ (line 1396)
* __satfractqisa: Fixed-point fractional library routines.
- (line 1400)
+ (line 1401)
* __satfractqisq: Fixed-point fractional library routines.
- (line 1397)
+ (line 1398)
* __satfractqita: Fixed-point fractional library routines.
- (line 1402)
+ (line 1403)
* __satfractqiuda: Fixed-point fractional library routines.
- (line 1413)
+ (line 1415)
* __satfractqiudq: Fixed-point fractional library routines.
- (line 1408)
-* __satfractqiuha: Fixed-point fractional library routines.
(line 1410)
+* __satfractqiuha: Fixed-point fractional library routines.
+ (line 1412)
* __satfractqiuhq: Fixed-point fractional library routines.
- (line 1405)
+ (line 1406)
* __satfractqiuqq: Fixed-point fractional library routines.
- (line 1403)
+ (line 1405)
* __satfractqiusa: Fixed-point fractional library routines.
- (line 1412)
+ (line 1413)
* __satfractqiusq: Fixed-point fractional library routines.
- (line 1406)
+ (line 1408)
* __satfractqiuta: Fixed-point fractional library routines.
- (line 1415)
+ (line 1417)
* __satfractqqda: Fixed-point fractional library routines.
- (line 1042)
+ (line 1043)
* __satfractqqdq2: Fixed-point fractional library routines.
- (line 1039)
-* __satfractqqha: Fixed-point fractional library routines.
(line 1040)
+* __satfractqqha: Fixed-point fractional library routines.
+ (line 1041)
* __satfractqqhq2: Fixed-point fractional library routines.
- (line 1037)
+ (line 1038)
* __satfractqqsa: Fixed-point fractional library routines.
- (line 1041)
+ (line 1042)
* __satfractqqsq2: Fixed-point fractional library routines.
- (line 1038)
+ (line 1039)
* __satfractqqta: Fixed-point fractional library routines.
- (line 1043)
+ (line 1044)
* __satfractqquda: Fixed-point fractional library routines.
- (line 1054)
+ (line 1056)
* __satfractqqudq: Fixed-point fractional library routines.
- (line 1049)
-* __satfractqquha: Fixed-point fractional library routines.
(line 1051)
+* __satfractqquha: Fixed-point fractional library routines.
+ (line 1053)
* __satfractqquhq: Fixed-point fractional library routines.
- (line 1046)
+ (line 1047)
* __satfractqquqq: Fixed-point fractional library routines.
- (line 1044)
+ (line 1046)
* __satfractqqusa: Fixed-point fractional library routines.
- (line 1053)
+ (line 1054)
* __satfractqqusq: Fixed-point fractional library routines.
- (line 1047)
+ (line 1049)
* __satfractqquta: Fixed-point fractional library routines.
- (line 1056)
+ (line 1058)
* __satfractsada2: Fixed-point fractional library routines.
- (line 1139)
+ (line 1140)
* __satfractsadq: Fixed-point fractional library routines.
- (line 1137)
-* __satfractsaha2: Fixed-point fractional library routines.
(line 1138)
+* __satfractsaha2: Fixed-point fractional library routines.
+ (line 1139)
* __satfractsahq: Fixed-point fractional library routines.
- (line 1135)
+ (line 1136)
* __satfractsaqq: Fixed-point fractional library routines.
- (line 1134)
+ (line 1135)
* __satfractsasq: Fixed-point fractional library routines.
- (line 1136)
+ (line 1137)
* __satfractsata2: Fixed-point fractional library routines.
- (line 1140)
+ (line 1141)
* __satfractsauda: Fixed-point fractional library routines.
- (line 1147)
+ (line 1148)
* __satfractsaudq: Fixed-point fractional library routines.
- (line 1144)
-* __satfractsauha: Fixed-point fractional library routines.
(line 1145)
+* __satfractsauha: Fixed-point fractional library routines.
+ (line 1146)
* __satfractsauhq: Fixed-point fractional library routines.
- (line 1142)
+ (line 1143)
* __satfractsauqq: Fixed-point fractional library routines.
- (line 1141)
+ (line 1142)
* __satfractsausa: Fixed-point fractional library routines.
- (line 1146)
+ (line 1147)
* __satfractsausq: Fixed-point fractional library routines.
- (line 1143)
+ (line 1144)
* __satfractsauta: Fixed-point fractional library routines.
- (line 1148)
+ (line 1149)
* __satfractsfda: Fixed-point fractional library routines.
- (line 1489)
+ (line 1490)
* __satfractsfdq: Fixed-point fractional library routines.
- (line 1486)
-* __satfractsfha: Fixed-point fractional library routines.
(line 1487)
+* __satfractsfha: Fixed-point fractional library routines.
+ (line 1488)
* __satfractsfhq: Fixed-point fractional library routines.
- (line 1484)
+ (line 1485)
* __satfractsfqq: Fixed-point fractional library routines.
- (line 1483)
+ (line 1484)
* __satfractsfsa: Fixed-point fractional library routines.
- (line 1488)
+ (line 1489)
* __satfractsfsq: Fixed-point fractional library routines.
- (line 1485)
+ (line 1486)
* __satfractsfta: Fixed-point fractional library routines.
- (line 1490)
+ (line 1491)
* __satfractsfuda: Fixed-point fractional library routines.
- (line 1497)
+ (line 1498)
* __satfractsfudq: Fixed-point fractional library routines.
- (line 1494)
-* __satfractsfuha: Fixed-point fractional library routines.
(line 1495)
+* __satfractsfuha: Fixed-point fractional library routines.
+ (line 1496)
* __satfractsfuhq: Fixed-point fractional library routines.
- (line 1492)
+ (line 1493)
* __satfractsfuqq: Fixed-point fractional library routines.
- (line 1491)
+ (line 1492)
* __satfractsfusa: Fixed-point fractional library routines.
- (line 1496)
+ (line 1497)
* __satfractsfusq: Fixed-point fractional library routines.
- (line 1493)
+ (line 1494)
* __satfractsfuta: Fixed-point fractional library routines.
- (line 1498)
+ (line 1499)
* __satfractsida: Fixed-point fractional library routines.
- (line 1439)
+ (line 1440)
* __satfractsidq: Fixed-point fractional library routines.
- (line 1436)
-* __satfractsiha: Fixed-point fractional library routines.
(line 1437)
+* __satfractsiha: Fixed-point fractional library routines.
+ (line 1438)
* __satfractsihq: Fixed-point fractional library routines.
- (line 1434)
+ (line 1435)
* __satfractsiqq: Fixed-point fractional library routines.
- (line 1433)
+ (line 1434)
* __satfractsisa: Fixed-point fractional library routines.
- (line 1438)
+ (line 1439)
* __satfractsisq: Fixed-point fractional library routines.
- (line 1435)
+ (line 1436)
* __satfractsita: Fixed-point fractional library routines.
- (line 1440)
+ (line 1441)
* __satfractsiuda: Fixed-point fractional library routines.
- (line 1447)
+ (line 1448)
* __satfractsiudq: Fixed-point fractional library routines.
- (line 1444)
-* __satfractsiuha: Fixed-point fractional library routines.
(line 1445)
+* __satfractsiuha: Fixed-point fractional library routines.
+ (line 1446)
* __satfractsiuhq: Fixed-point fractional library routines.
- (line 1442)
+ (line 1443)
* __satfractsiuqq: Fixed-point fractional library routines.
- (line 1441)
+ (line 1442)
* __satfractsiusa: Fixed-point fractional library routines.
- (line 1446)
+ (line 1447)
* __satfractsiusq: Fixed-point fractional library routines.
- (line 1443)
+ (line 1444)
* __satfractsiuta: Fixed-point fractional library routines.
- (line 1448)
+ (line 1449)
* __satfractsqda: Fixed-point fractional library routines.
- (line 1078)
+ (line 1079)
* __satfractsqdq2: Fixed-point fractional library routines.
- (line 1075)
-* __satfractsqha: Fixed-point fractional library routines.
(line 1076)
+* __satfractsqha: Fixed-point fractional library routines.
+ (line 1077)
* __satfractsqhq2: Fixed-point fractional library routines.
- (line 1074)
+ (line 1075)
* __satfractsqqq2: Fixed-point fractional library routines.
- (line 1073)
+ (line 1074)
* __satfractsqsa: Fixed-point fractional library routines.
- (line 1077)
+ (line 1078)
* __satfractsqta: Fixed-point fractional library routines.
- (line 1079)
+ (line 1080)
* __satfractsquda: Fixed-point fractional library routines.
- (line 1089)
+ (line 1090)
* __satfractsqudq: Fixed-point fractional library routines.
- (line 1084)
-* __satfractsquha: Fixed-point fractional library routines.
(line 1086)
+* __satfractsquha: Fixed-point fractional library routines.
+ (line 1088)
* __satfractsquhq: Fixed-point fractional library routines.
- (line 1082)
+ (line 1083)
* __satfractsquqq: Fixed-point fractional library routines.
- (line 1080)
+ (line 1082)
* __satfractsqusa: Fixed-point fractional library routines.
- (line 1088)
+ (line 1089)
* __satfractsqusq: Fixed-point fractional library routines.
- (line 1083)
+ (line 1084)
* __satfractsquta: Fixed-point fractional library routines.
- (line 1090)
+ (line 1092)
* __satfracttada2: Fixed-point fractional library routines.
- (line 1174)
+ (line 1175)
* __satfracttadq: Fixed-point fractional library routines.
- (line 1171)
-* __satfracttaha2: Fixed-point fractional library routines.
(line 1172)
+* __satfracttaha2: Fixed-point fractional library routines.
+ (line 1173)
* __satfracttahq: Fixed-point fractional library routines.
- (line 1169)
+ (line 1170)
* __satfracttaqq: Fixed-point fractional library routines.
- (line 1168)
+ (line 1169)
* __satfracttasa2: Fixed-point fractional library routines.
- (line 1173)
+ (line 1174)
* __satfracttasq: Fixed-point fractional library routines.
- (line 1170)
+ (line 1171)
* __satfracttauda: Fixed-point fractional library routines.
- (line 1185)
+ (line 1187)
* __satfracttaudq: Fixed-point fractional library routines.
- (line 1180)
-* __satfracttauha: Fixed-point fractional library routines.
(line 1182)
+* __satfracttauha: Fixed-point fractional library routines.
+ (line 1184)
* __satfracttauhq: Fixed-point fractional library routines.
- (line 1177)
+ (line 1178)
* __satfracttauqq: Fixed-point fractional library routines.
- (line 1175)
+ (line 1177)
* __satfracttausa: Fixed-point fractional library routines.
- (line 1184)
+ (line 1185)
* __satfracttausq: Fixed-point fractional library routines.
- (line 1178)
+ (line 1180)
* __satfracttauta: Fixed-point fractional library routines.
- (line 1187)
+ (line 1189)
* __satfracttida: Fixed-point fractional library routines.
- (line 1471)
+ (line 1472)
* __satfracttidq: Fixed-point fractional library routines.
- (line 1468)
-* __satfracttiha: Fixed-point fractional library routines.
(line 1469)
+* __satfracttiha: Fixed-point fractional library routines.
+ (line 1470)
* __satfracttihq: Fixed-point fractional library routines.
- (line 1466)
+ (line 1467)
* __satfracttiqq: Fixed-point fractional library routines.
- (line 1465)
+ (line 1466)
* __satfracttisa: Fixed-point fractional library routines.
- (line 1470)
+ (line 1471)
* __satfracttisq: Fixed-point fractional library routines.
- (line 1467)
+ (line 1468)
* __satfracttita: Fixed-point fractional library routines.
- (line 1472)
+ (line 1473)
* __satfracttiuda: Fixed-point fractional library routines.
- (line 1480)
+ (line 1481)
* __satfracttiudq: Fixed-point fractional library routines.
- (line 1476)
-* __satfracttiuha: Fixed-point fractional library routines.
(line 1478)
+* __satfracttiuha: Fixed-point fractional library routines.
+ (line 1479)
* __satfracttiuhq: Fixed-point fractional library routines.
- (line 1474)
+ (line 1475)
* __satfracttiuqq: Fixed-point fractional library routines.
- (line 1473)
+ (line 1474)
* __satfracttiusa: Fixed-point fractional library routines.
- (line 1479)
+ (line 1480)
* __satfracttiusq: Fixed-point fractional library routines.
- (line 1475)
+ (line 1476)
* __satfracttiuta: Fixed-point fractional library routines.
- (line 1481)
+ (line 1483)
* __satfractudada: Fixed-point fractional library routines.
- (line 1350)
+ (line 1351)
* __satfractudadq: Fixed-point fractional library routines.
- (line 1345)
-* __satfractudaha: Fixed-point fractional library routines.
(line 1347)
+* __satfractudaha: Fixed-point fractional library routines.
+ (line 1349)
* __satfractudahq: Fixed-point fractional library routines.
- (line 1343)
+ (line 1344)
* __satfractudaqq: Fixed-point fractional library routines.
- (line 1341)
+ (line 1343)
* __satfractudasa: Fixed-point fractional library routines.
- (line 1349)
+ (line 1350)
* __satfractudasq: Fixed-point fractional library routines.
- (line 1344)
+ (line 1345)
* __satfractudata: Fixed-point fractional library routines.
- (line 1351)
+ (line 1353)
* __satfractudaudq: Fixed-point fractional library routines.
- (line 1359)
-* __satfractudauha2: Fixed-point fractional library routines.
(line 1361)
+* __satfractudauha2: Fixed-point fractional library routines.
+ (line 1363)
* __satfractudauhq: Fixed-point fractional library routines.
- (line 1355)
+ (line 1357)
* __satfractudauqq: Fixed-point fractional library routines.
- (line 1353)
+ (line 1355)
* __satfractudausa2: Fixed-point fractional library routines.
- (line 1363)
+ (line 1365)
* __satfractudausq: Fixed-point fractional library routines.
- (line 1357)
+ (line 1359)
* __satfractudauta2: Fixed-point fractional library routines.
- (line 1365)
+ (line 1367)
* __satfractudqda: Fixed-point fractional library routines.
- (line 1274)
+ (line 1276)
* __satfractudqdq: Fixed-point fractional library routines.
- (line 1269)
-* __satfractudqha: Fixed-point fractional library routines.
(line 1271)
+* __satfractudqha: Fixed-point fractional library routines.
+ (line 1273)
* __satfractudqhq: Fixed-point fractional library routines.
- (line 1266)
+ (line 1267)
* __satfractudqqq: Fixed-point fractional library routines.
- (line 1264)
+ (line 1266)
* __satfractudqsa: Fixed-point fractional library routines.
- (line 1273)
+ (line 1274)
* __satfractudqsq: Fixed-point fractional library routines.
- (line 1267)
+ (line 1269)
* __satfractudqta: Fixed-point fractional library routines.
- (line 1276)
+ (line 1278)
* __satfractudquda: Fixed-point fractional library routines.
- (line 1288)
+ (line 1290)
* __satfractudquha: Fixed-point fractional library routines.
- (line 1284)
+ (line 1286)
* __satfractudquhq2: Fixed-point fractional library routines.
- (line 1280)
+ (line 1282)
* __satfractudquqq2: Fixed-point fractional library routines.
- (line 1278)
+ (line 1280)
* __satfractudqusa: Fixed-point fractional library routines.
- (line 1286)
+ (line 1288)
* __satfractudqusq2: Fixed-point fractional library routines.
- (line 1282)
+ (line 1284)
* __satfractudquta: Fixed-point fractional library routines.
- (line 1290)
+ (line 1292)
* __satfractuhada: Fixed-point fractional library routines.
- (line 1302)
+ (line 1304)
* __satfractuhadq: Fixed-point fractional library routines.
- (line 1297)
-* __satfractuhaha: Fixed-point fractional library routines.
(line 1299)
+* __satfractuhaha: Fixed-point fractional library routines.
+ (line 1301)
* __satfractuhahq: Fixed-point fractional library routines.
- (line 1294)
+ (line 1295)
* __satfractuhaqq: Fixed-point fractional library routines.
- (line 1292)
+ (line 1294)
* __satfractuhasa: Fixed-point fractional library routines.
- (line 1301)
+ (line 1302)
* __satfractuhasq: Fixed-point fractional library routines.
- (line 1295)
+ (line 1297)
* __satfractuhata: Fixed-point fractional library routines.
- (line 1304)
+ (line 1306)
* __satfractuhauda2: Fixed-point fractional library routines.
- (line 1316)
+ (line 1318)
* __satfractuhaudq: Fixed-point fractional library routines.
- (line 1312)
+ (line 1314)
* __satfractuhauhq: Fixed-point fractional library routines.
- (line 1308)
+ (line 1310)
* __satfractuhauqq: Fixed-point fractional library routines.
- (line 1306)
+ (line 1308)
* __satfractuhausa2: Fixed-point fractional library routines.
- (line 1314)
+ (line 1316)
* __satfractuhausq: Fixed-point fractional library routines.
- (line 1310)
+ (line 1312)
* __satfractuhauta2: Fixed-point fractional library routines.
- (line 1318)
+ (line 1320)
* __satfractuhqda: Fixed-point fractional library routines.
- (line 1223)
+ (line 1224)
* __satfractuhqdq: Fixed-point fractional library routines.
- (line 1220)
-* __satfractuhqha: Fixed-point fractional library routines.
(line 1221)
+* __satfractuhqha: Fixed-point fractional library routines.
+ (line 1222)
* __satfractuhqhq: Fixed-point fractional library routines.
- (line 1218)
+ (line 1219)
* __satfractuhqqq: Fixed-point fractional library routines.
- (line 1217)
+ (line 1218)
* __satfractuhqsa: Fixed-point fractional library routines.
- (line 1222)
+ (line 1223)
* __satfractuhqsq: Fixed-point fractional library routines.
- (line 1219)
+ (line 1220)
* __satfractuhqta: Fixed-point fractional library routines.
- (line 1224)
+ (line 1225)
* __satfractuhquda: Fixed-point fractional library routines.
- (line 1234)
+ (line 1236)
* __satfractuhqudq2: Fixed-point fractional library routines.
- (line 1229)
-* __satfractuhquha: Fixed-point fractional library routines.
(line 1231)
+* __satfractuhquha: Fixed-point fractional library routines.
+ (line 1233)
* __satfractuhquqq2: Fixed-point fractional library routines.
- (line 1225)
+ (line 1227)
* __satfractuhqusa: Fixed-point fractional library routines.
- (line 1233)
+ (line 1234)
* __satfractuhqusq2: Fixed-point fractional library routines.
- (line 1227)
+ (line 1229)
* __satfractuhquta: Fixed-point fractional library routines.
- (line 1236)
+ (line 1238)
* __satfractunsdida: Fixed-point fractional library routines.
- (line 1833)
+ (line 1834)
* __satfractunsdidq: Fixed-point fractional library routines.
- (line 1829)
-* __satfractunsdiha: Fixed-point fractional library routines.
(line 1831)
+* __satfractunsdiha: Fixed-point fractional library routines.
+ (line 1832)
* __satfractunsdihq: Fixed-point fractional library routines.
- (line 1827)
+ (line 1828)
* __satfractunsdiqq: Fixed-point fractional library routines.
- (line 1826)
+ (line 1827)
* __satfractunsdisa: Fixed-point fractional library routines.
- (line 1832)
+ (line 1833)
* __satfractunsdisq: Fixed-point fractional library routines.
- (line 1828)
+ (line 1829)
* __satfractunsdita: Fixed-point fractional library routines.
- (line 1834)
+ (line 1836)
* __satfractunsdiuda: Fixed-point fractional library routines.
- (line 1848)
+ (line 1850)
* __satfractunsdiudq: Fixed-point fractional library routines.
- (line 1842)
-* __satfractunsdiuha: Fixed-point fractional library routines.
(line 1844)
+* __satfractunsdiuha: Fixed-point fractional library routines.
+ (line 1846)
* __satfractunsdiuhq: Fixed-point fractional library routines.
- (line 1838)
+ (line 1840)
* __satfractunsdiuqq: Fixed-point fractional library routines.
- (line 1836)
+ (line 1838)
* __satfractunsdiusa: Fixed-point fractional library routines.
- (line 1846)
+ (line 1848)
* __satfractunsdiusq: Fixed-point fractional library routines.
- (line 1840)
+ (line 1842)
* __satfractunsdiuta: Fixed-point fractional library routines.
- (line 1850)
+ (line 1852)
* __satfractunshida: Fixed-point fractional library routines.
- (line 1785)
+ (line 1786)
* __satfractunshidq: Fixed-point fractional library routines.
- (line 1781)
-* __satfractunshiha: Fixed-point fractional library routines.
(line 1783)
+* __satfractunshiha: Fixed-point fractional library routines.
+ (line 1784)
* __satfractunshihq: Fixed-point fractional library routines.
- (line 1779)
+ (line 1780)
* __satfractunshiqq: Fixed-point fractional library routines.
- (line 1778)
+ (line 1779)
* __satfractunshisa: Fixed-point fractional library routines.
- (line 1784)
+ (line 1785)
* __satfractunshisq: Fixed-point fractional library routines.
- (line 1780)
+ (line 1781)
* __satfractunshita: Fixed-point fractional library routines.
- (line 1786)
+ (line 1788)
* __satfractunshiuda: Fixed-point fractional library routines.
- (line 1800)
+ (line 1802)
* __satfractunshiudq: Fixed-point fractional library routines.
- (line 1794)
-* __satfractunshiuha: Fixed-point fractional library routines.
(line 1796)
+* __satfractunshiuha: Fixed-point fractional library routines.
+ (line 1798)
* __satfractunshiuhq: Fixed-point fractional library routines.
- (line 1790)
+ (line 1792)
* __satfractunshiuqq: Fixed-point fractional library routines.
- (line 1788)
+ (line 1790)
* __satfractunshiusa: Fixed-point fractional library routines.
- (line 1798)
+ (line 1800)
* __satfractunshiusq: Fixed-point fractional library routines.
- (line 1792)
+ (line 1794)
* __satfractunshiuta: Fixed-point fractional library routines.
- (line 1802)
+ (line 1804)
* __satfractunsqida: Fixed-point fractional library routines.
- (line 1759)
+ (line 1760)
* __satfractunsqidq: Fixed-point fractional library routines.
- (line 1755)
-* __satfractunsqiha: Fixed-point fractional library routines.
(line 1757)
+* __satfractunsqiha: Fixed-point fractional library routines.
+ (line 1758)
* __satfractunsqihq: Fixed-point fractional library routines.
- (line 1753)
+ (line 1754)
* __satfractunsqiqq: Fixed-point fractional library routines.
- (line 1752)
+ (line 1753)
* __satfractunsqisa: Fixed-point fractional library routines.
- (line 1758)
+ (line 1759)
* __satfractunsqisq: Fixed-point fractional library routines.
- (line 1754)
+ (line 1755)
* __satfractunsqita: Fixed-point fractional library routines.
- (line 1760)
+ (line 1762)
* __satfractunsqiuda: Fixed-point fractional library routines.
- (line 1774)
+ (line 1776)
* __satfractunsqiudq: Fixed-point fractional library routines.
- (line 1768)
-* __satfractunsqiuha: Fixed-point fractional library routines.
(line 1770)
+* __satfractunsqiuha: Fixed-point fractional library routines.
+ (line 1772)
* __satfractunsqiuhq: Fixed-point fractional library routines.
- (line 1764)
+ (line 1766)
* __satfractunsqiuqq: Fixed-point fractional library routines.
- (line 1762)
+ (line 1764)
* __satfractunsqiusa: Fixed-point fractional library routines.
- (line 1772)
+ (line 1774)
* __satfractunsqiusq: Fixed-point fractional library routines.
- (line 1766)
+ (line 1768)
* __satfractunsqiuta: Fixed-point fractional library routines.
- (line 1776)
+ (line 1778)
* __satfractunssida: Fixed-point fractional library routines.
- (line 1810)
+ (line 1811)
* __satfractunssidq: Fixed-point fractional library routines.
- (line 1807)
-* __satfractunssiha: Fixed-point fractional library routines.
(line 1808)
+* __satfractunssiha: Fixed-point fractional library routines.
+ (line 1809)
* __satfractunssihq: Fixed-point fractional library routines.
- (line 1805)
+ (line 1806)
* __satfractunssiqq: Fixed-point fractional library routines.
- (line 1804)
+ (line 1805)
* __satfractunssisa: Fixed-point fractional library routines.
- (line 1809)
+ (line 1810)
* __satfractunssisq: Fixed-point fractional library routines.
- (line 1806)
+ (line 1807)
* __satfractunssita: Fixed-point fractional library routines.
- (line 1811)
+ (line 1812)
* __satfractunssiuda: Fixed-point fractional library routines.
- (line 1822)
+ (line 1824)
* __satfractunssiudq: Fixed-point fractional library routines.
- (line 1817)
-* __satfractunssiuha: Fixed-point fractional library routines.
(line 1819)
+* __satfractunssiuha: Fixed-point fractional library routines.
+ (line 1821)
* __satfractunssiuhq: Fixed-point fractional library routines.
- (line 1814)
+ (line 1815)
* __satfractunssiuqq: Fixed-point fractional library routines.
- (line 1812)
+ (line 1814)
* __satfractunssiusa: Fixed-point fractional library routines.
- (line 1821)
+ (line 1822)
* __satfractunssiusq: Fixed-point fractional library routines.
- (line 1815)
+ (line 1817)
* __satfractunssiuta: Fixed-point fractional library routines.
- (line 1824)
+ (line 1826)
* __satfractunstida: Fixed-point fractional library routines.
- (line 1862)
+ (line 1864)
* __satfractunstidq: Fixed-point fractional library routines.
- (line 1857)
-* __satfractunstiha: Fixed-point fractional library routines.
(line 1859)
+* __satfractunstiha: Fixed-point fractional library routines.
+ (line 1861)
* __satfractunstihq: Fixed-point fractional library routines.
- (line 1854)
+ (line 1855)
* __satfractunstiqq: Fixed-point fractional library routines.
- (line 1852)
+ (line 1854)
* __satfractunstisa: Fixed-point fractional library routines.
- (line 1861)
+ (line 1862)
* __satfractunstisq: Fixed-point fractional library routines.
- (line 1855)
+ (line 1857)
* __satfractunstita: Fixed-point fractional library routines.
- (line 1864)
+ (line 1866)
* __satfractunstiuda: Fixed-point fractional library routines.
- (line 1878)
+ (line 1880)
* __satfractunstiudq: Fixed-point fractional library routines.
- (line 1872)
-* __satfractunstiuha: Fixed-point fractional library routines.
(line 1874)
+* __satfractunstiuha: Fixed-point fractional library routines.
+ (line 1876)
* __satfractunstiuhq: Fixed-point fractional library routines.
- (line 1868)
+ (line 1870)
* __satfractunstiuqq: Fixed-point fractional library routines.
- (line 1866)
+ (line 1868)
* __satfractunstiusa: Fixed-point fractional library routines.
- (line 1876)
+ (line 1878)
* __satfractunstiusq: Fixed-point fractional library routines.
- (line 1870)
+ (line 1872)
* __satfractunstiuta: Fixed-point fractional library routines.
- (line 1880)
+ (line 1882)
* __satfractuqqda: Fixed-point fractional library routines.
- (line 1199)
+ (line 1201)
* __satfractuqqdq: Fixed-point fractional library routines.
- (line 1194)
-* __satfractuqqha: Fixed-point fractional library routines.
(line 1196)
+* __satfractuqqha: Fixed-point fractional library routines.
+ (line 1198)
* __satfractuqqhq: Fixed-point fractional library routines.
- (line 1191)
+ (line 1192)
* __satfractuqqqq: Fixed-point fractional library routines.
- (line 1189)
+ (line 1191)
* __satfractuqqsa: Fixed-point fractional library routines.
- (line 1198)
+ (line 1199)
* __satfractuqqsq: Fixed-point fractional library routines.
- (line 1192)
+ (line 1194)
* __satfractuqqta: Fixed-point fractional library routines.
- (line 1201)
+ (line 1203)
* __satfractuqquda: Fixed-point fractional library routines.
- (line 1213)
+ (line 1215)
* __satfractuqqudq2: Fixed-point fractional library routines.
- (line 1207)
-* __satfractuqquha: Fixed-point fractional library routines.
(line 1209)
+* __satfractuqquha: Fixed-point fractional library routines.
+ (line 1211)
* __satfractuqquhq2: Fixed-point fractional library routines.
- (line 1203)
+ (line 1205)
* __satfractuqqusa: Fixed-point fractional library routines.
- (line 1211)
+ (line 1213)
* __satfractuqqusq2: Fixed-point fractional library routines.
- (line 1205)
+ (line 1207)
* __satfractuqquta: Fixed-point fractional library routines.
- (line 1215)
+ (line 1217)
* __satfractusada: Fixed-point fractional library routines.
- (line 1326)
+ (line 1327)
* __satfractusadq: Fixed-point fractional library routines.
- (line 1323)
-* __satfractusaha: Fixed-point fractional library routines.
(line 1324)
+* __satfractusaha: Fixed-point fractional library routines.
+ (line 1325)
* __satfractusahq: Fixed-point fractional library routines.
- (line 1321)
+ (line 1322)
* __satfractusaqq: Fixed-point fractional library routines.
- (line 1320)
+ (line 1321)
* __satfractusasa: Fixed-point fractional library routines.
- (line 1325)
+ (line 1326)
* __satfractusasq: Fixed-point fractional library routines.
- (line 1322)
+ (line 1323)
* __satfractusata: Fixed-point fractional library routines.
- (line 1327)
+ (line 1328)
* __satfractusauda2: Fixed-point fractional library routines.
- (line 1337)
+ (line 1339)
* __satfractusaudq: Fixed-point fractional library routines.
- (line 1333)
-* __satfractusauha2: Fixed-point fractional library routines.
(line 1335)
+* __satfractusauha2: Fixed-point fractional library routines.
+ (line 1337)
* __satfractusauhq: Fixed-point fractional library routines.
- (line 1330)
+ (line 1331)
* __satfractusauqq: Fixed-point fractional library routines.
- (line 1328)
+ (line 1330)
* __satfractusausq: Fixed-point fractional library routines.
- (line 1331)
+ (line 1333)
* __satfractusauta2: Fixed-point fractional library routines.
- (line 1339)
+ (line 1341)
* __satfractusqda: Fixed-point fractional library routines.
- (line 1247)
+ (line 1248)
* __satfractusqdq: Fixed-point fractional library routines.
- (line 1242)
-* __satfractusqha: Fixed-point fractional library routines.
(line 1244)
+* __satfractusqha: Fixed-point fractional library routines.
+ (line 1246)
* __satfractusqhq: Fixed-point fractional library routines.
- (line 1240)
+ (line 1241)
* __satfractusqqq: Fixed-point fractional library routines.
- (line 1238)
+ (line 1240)
* __satfractusqsa: Fixed-point fractional library routines.
- (line 1246)
+ (line 1247)
* __satfractusqsq: Fixed-point fractional library routines.
- (line 1241)
+ (line 1242)
* __satfractusqta: Fixed-point fractional library routines.
- (line 1248)
+ (line 1250)
* __satfractusquda: Fixed-point fractional library routines.
- (line 1260)
+ (line 1262)
* __satfractusqudq2: Fixed-point fractional library routines.
- (line 1254)
-* __satfractusquha: Fixed-point fractional library routines.
(line 1256)
+* __satfractusquha: Fixed-point fractional library routines.
+ (line 1258)
* __satfractusquhq2: Fixed-point fractional library routines.
- (line 1252)
+ (line 1254)
* __satfractusquqq2: Fixed-point fractional library routines.
- (line 1250)
+ (line 1252)
* __satfractusqusa: Fixed-point fractional library routines.
- (line 1258)
+ (line 1260)
* __satfractusquta: Fixed-point fractional library routines.
- (line 1262)
+ (line 1264)
* __satfractutada: Fixed-point fractional library routines.
- (line 1377)
+ (line 1379)
* __satfractutadq: Fixed-point fractional library routines.
- (line 1372)
-* __satfractutaha: Fixed-point fractional library routines.
(line 1374)
+* __satfractutaha: Fixed-point fractional library routines.
+ (line 1376)
* __satfractutahq: Fixed-point fractional library routines.
- (line 1369)
+ (line 1370)
* __satfractutaqq: Fixed-point fractional library routines.
- (line 1367)
+ (line 1369)
* __satfractutasa: Fixed-point fractional library routines.
- (line 1376)
+ (line 1377)
* __satfractutasq: Fixed-point fractional library routines.
- (line 1370)
+ (line 1372)
* __satfractutata: Fixed-point fractional library routines.
- (line 1379)
+ (line 1381)
* __satfractutauda2: Fixed-point fractional library routines.
- (line 1393)
+ (line 1395)
* __satfractutaudq: Fixed-point fractional library routines.
- (line 1387)
-* __satfractutauha2: Fixed-point fractional library routines.
(line 1389)
+* __satfractutauha2: Fixed-point fractional library routines.
+ (line 1391)
* __satfractutauhq: Fixed-point fractional library routines.
- (line 1383)
+ (line 1385)
* __satfractutauqq: Fixed-point fractional library routines.
- (line 1381)
+ (line 1383)
* __satfractutausa2: Fixed-point fractional library routines.
- (line 1391)
+ (line 1393)
* __satfractutausq: Fixed-point fractional library routines.
- (line 1385)
+ (line 1387)
* __splitstack_find: Miscellaneous routines.
- (line 15)
+ (line 18)
* __ssaddda3: Fixed-point fractional library routines.
- (line 66)
+ (line 67)
* __ssadddq3: Fixed-point fractional library routines.
- (line 61)
-* __ssaddha3: Fixed-point fractional library routines.
(line 63)
+* __ssaddha3: Fixed-point fractional library routines.
+ (line 65)
* __ssaddhq3: Fixed-point fractional library routines.
- (line 59)
+ (line 60)
* __ssaddqq3: Fixed-point fractional library routines.
- (line 57)
+ (line 59)
* __ssaddsa3: Fixed-point fractional library routines.
- (line 65)
+ (line 66)
* __ssaddsq3: Fixed-point fractional library routines.
- (line 60)
+ (line 61)
* __ssaddta3: Fixed-point fractional library routines.
- (line 67)
+ (line 69)
* __ssashlda3: Fixed-point fractional library routines.
- (line 401)
+ (line 402)
* __ssashldq3: Fixed-point fractional library routines.
- (line 397)
-* __ssashlha3: Fixed-point fractional library routines.
(line 399)
+* __ssashlha3: Fixed-point fractional library routines.
+ (line 400)
* __ssashlhq3: Fixed-point fractional library routines.
- (line 395)
+ (line 396)
* __ssashlsa3: Fixed-point fractional library routines.
- (line 400)
+ (line 401)
* __ssashlsq3: Fixed-point fractional library routines.
- (line 396)
+ (line 397)
* __ssashlta3: Fixed-point fractional library routines.
- (line 402)
+ (line 404)
* __ssdivda3: Fixed-point fractional library routines.
- (line 260)
+ (line 261)
* __ssdivdq3: Fixed-point fractional library routines.
- (line 255)
-* __ssdivha3: Fixed-point fractional library routines.
(line 257)
+* __ssdivha3: Fixed-point fractional library routines.
+ (line 259)
* __ssdivhq3: Fixed-point fractional library routines.
- (line 253)
+ (line 254)
* __ssdivqq3: Fixed-point fractional library routines.
- (line 251)
+ (line 253)
* __ssdivsa3: Fixed-point fractional library routines.
- (line 259)
+ (line 260)
* __ssdivsq3: Fixed-point fractional library routines.
- (line 254)
+ (line 255)
* __ssdivta3: Fixed-point fractional library routines.
- (line 261)
+ (line 263)
* __ssmulda3: Fixed-point fractional library routines.
- (line 192)
+ (line 193)
* __ssmuldq3: Fixed-point fractional library routines.
- (line 187)
-* __ssmulha3: Fixed-point fractional library routines.
(line 189)
+* __ssmulha3: Fixed-point fractional library routines.
+ (line 191)
* __ssmulhq3: Fixed-point fractional library routines.
- (line 185)
+ (line 186)
* __ssmulqq3: Fixed-point fractional library routines.
- (line 183)
+ (line 185)
* __ssmulsa3: Fixed-point fractional library routines.
- (line 191)
+ (line 192)
* __ssmulsq3: Fixed-point fractional library routines.
- (line 186)
+ (line 187)
* __ssmulta3: Fixed-point fractional library routines.
- (line 193)
+ (line 195)
* __ssnegda2: Fixed-point fractional library routines.
- (line 315)
+ (line 316)
* __ssnegdq2: Fixed-point fractional library routines.
- (line 312)
-* __ssnegha2: Fixed-point fractional library routines.
(line 313)
+* __ssnegha2: Fixed-point fractional library routines.
+ (line 314)
* __ssneghq2: Fixed-point fractional library routines.
- (line 310)
+ (line 311)
* __ssnegqq2: Fixed-point fractional library routines.
- (line 309)
+ (line 310)
* __ssnegsa2: Fixed-point fractional library routines.
- (line 314)
+ (line 315)
* __ssnegsq2: Fixed-point fractional library routines.
- (line 311)
+ (line 312)
* __ssnegta2: Fixed-point fractional library routines.
- (line 316)
+ (line 317)
* __sssubda3: Fixed-point fractional library routines.
- (line 128)
+ (line 129)
* __sssubdq3: Fixed-point fractional library routines.
- (line 123)
-* __sssubha3: Fixed-point fractional library routines.
(line 125)
+* __sssubha3: Fixed-point fractional library routines.
+ (line 127)
* __sssubhq3: Fixed-point fractional library routines.
- (line 121)
+ (line 122)
* __sssubqq3: Fixed-point fractional library routines.
- (line 119)
+ (line 121)
* __sssubsa3: Fixed-point fractional library routines.
- (line 127)
+ (line 128)
* __sssubsq3: Fixed-point fractional library routines.
- (line 122)
+ (line 123)
* __sssubta3: Fixed-point fractional library routines.
- (line 129)
+ (line 131)
* __subda3: Fixed-point fractional library routines.
- (line 106)
+ (line 107)
* __subdf3: Soft float library routines.
- (line 30)
+ (line 31)
* __subdq3: Fixed-point fractional library routines.
- (line 93)
+ (line 95)
* __subha3: Fixed-point fractional library routines.
- (line 103)
+ (line 105)
* __subhq3: Fixed-point fractional library routines.
- (line 91)
+ (line 92)
* __subqq3: Fixed-point fractional library routines.
- (line 89)
+ (line 91)
* __subsa3: Fixed-point fractional library routines.
- (line 105)
+ (line 106)
* __subsf3: Soft float library routines.
- (line 29)
+ (line 30)
* __subsq3: Fixed-point fractional library routines.
- (line 92)
+ (line 93)
* __subta3: Fixed-point fractional library routines.
- (line 107)
+ (line 109)
* __subtf3: Soft float library routines.
- (line 31)
+ (line 33)
* __subuda3: Fixed-point fractional library routines.
- (line 113)
+ (line 115)
* __subudq3: Fixed-point fractional library routines.
- (line 101)
+ (line 103)
* __subuha3: Fixed-point fractional library routines.
- (line 109)
+ (line 111)
* __subuhq3: Fixed-point fractional library routines.
- (line 97)
+ (line 99)
* __subuqq3: Fixed-point fractional library routines.
- (line 95)
+ (line 97)
* __subusa3: Fixed-point fractional library routines.
- (line 111)
+ (line 113)
* __subusq3: Fixed-point fractional library routines.
- (line 99)
+ (line 101)
* __subuta3: Fixed-point fractional library routines.
- (line 115)
+ (line 117)
* __subvdi3: Integer library routines.
- (line 122)
+ (line 123)
* __subvsi3: Integer library routines.
- (line 121)
+ (line 122)
* __subxf3: Soft float library routines.
- (line 33)
+ (line 35)
* __truncdfsf2: Soft float library routines.
- (line 75)
+ (line 76)
* __trunctfdf2: Soft float library routines.
- (line 72)
+ (line 73)
* __trunctfsf2: Soft float library routines.
- (line 74)
+ (line 75)
* __truncxfdf2: Soft float library routines.
- (line 71)
+ (line 72)
* __truncxfsf2: Soft float library routines.
- (line 73)
+ (line 74)
* __ucmpdi2: Integer library routines.
- (line 92)
-* __ucmpti2: Integer library routines.
(line 93)
+* __ucmpti2: Integer library routines.
+ (line 95)
* __udivdi3: Integer library routines.
- (line 52)
+ (line 54)
* __udivmoddi4: Integer library routines.
- (line 59)
-* __udivmodti4: Integer library routines.
(line 61)
+* __udivmodti4: Integer library routines.
+ (line 63)
* __udivsi3: Integer library routines.
- (line 50)
+ (line 52)
* __udivti3: Integer library routines.
- (line 54)
+ (line 56)
* __udivuda3: Fixed-point fractional library routines.
- (line 244)
+ (line 246)
* __udivudq3: Fixed-point fractional library routines.
- (line 238)
-* __udivuha3: Fixed-point fractional library routines.
(line 240)
+* __udivuha3: Fixed-point fractional library routines.
+ (line 242)
* __udivuhq3: Fixed-point fractional library routines.
- (line 234)
+ (line 236)
* __udivuqq3: Fixed-point fractional library routines.
- (line 232)
+ (line 234)
* __udivusa3: Fixed-point fractional library routines.
- (line 242)
+ (line 244)
* __udivusq3: Fixed-point fractional library routines.
- (line 236)
+ (line 238)
* __udivuta3: Fixed-point fractional library routines.
- (line 246)
+ (line 248)
* __umoddi3: Integer library routines.
- (line 69)
+ (line 71)
* __umodsi3: Integer library routines.
- (line 67)
+ (line 69)
* __umodti3: Integer library routines.
- (line 71)
+ (line 73)
* __unorddf2: Soft float library routines.
- (line 172)
+ (line 173)
* __unordsf2: Soft float library routines.
- (line 171)
+ (line 172)
* __unordtf2: Soft float library routines.
- (line 173)
+ (line 174)
* __usadduda3: Fixed-point fractional library routines.
- (line 83)
+ (line 85)
* __usaddudq3: Fixed-point fractional library routines.
- (line 77)
-* __usadduha3: Fixed-point fractional library routines.
(line 79)
+* __usadduha3: Fixed-point fractional library routines.
+ (line 81)
* __usadduhq3: Fixed-point fractional library routines.
- (line 73)
+ (line 75)
* __usadduqq3: Fixed-point fractional library routines.
- (line 71)
+ (line 73)
* __usaddusa3: Fixed-point fractional library routines.
- (line 81)
+ (line 83)
* __usaddusq3: Fixed-point fractional library routines.
- (line 75)
+ (line 77)
* __usadduta3: Fixed-point fractional library routines.
- (line 85)
+ (line 87)
* __usashluda3: Fixed-point fractional library routines.
- (line 419)
+ (line 421)
* __usashludq3: Fixed-point fractional library routines.
- (line 413)
-* __usashluha3: Fixed-point fractional library routines.
(line 415)
+* __usashluha3: Fixed-point fractional library routines.
+ (line 417)
* __usashluhq3: Fixed-point fractional library routines.
- (line 409)
+ (line 411)
* __usashluqq3: Fixed-point fractional library routines.
- (line 407)
+ (line 409)
* __usashlusa3: Fixed-point fractional library routines.
- (line 417)
+ (line 419)
* __usashlusq3: Fixed-point fractional library routines.
- (line 411)
+ (line 413)
* __usashluta3: Fixed-point fractional library routines.
- (line 421)
+ (line 423)
* __usdivuda3: Fixed-point fractional library routines.
- (line 278)
+ (line 280)
* __usdivudq3: Fixed-point fractional library routines.
- (line 272)
-* __usdivuha3: Fixed-point fractional library routines.
(line 274)
+* __usdivuha3: Fixed-point fractional library routines.
+ (line 276)
* __usdivuhq3: Fixed-point fractional library routines.
- (line 268)
+ (line 270)
* __usdivuqq3: Fixed-point fractional library routines.
- (line 266)
+ (line 268)
* __usdivusa3: Fixed-point fractional library routines.
- (line 276)
+ (line 278)
* __usdivusq3: Fixed-point fractional library routines.
- (line 270)
+ (line 272)
* __usdivuta3: Fixed-point fractional library routines.
- (line 280)
+ (line 282)
* __usmuluda3: Fixed-point fractional library routines.
- (line 210)
+ (line 212)
* __usmuludq3: Fixed-point fractional library routines.
- (line 204)
-* __usmuluha3: Fixed-point fractional library routines.
(line 206)
+* __usmuluha3: Fixed-point fractional library routines.
+ (line 208)
* __usmuluhq3: Fixed-point fractional library routines.
- (line 200)
+ (line 202)
* __usmuluqq3: Fixed-point fractional library routines.
- (line 198)
+ (line 200)
* __usmulusa3: Fixed-point fractional library routines.
- (line 208)
+ (line 210)
* __usmulusq3: Fixed-point fractional library routines.
- (line 202)
+ (line 204)
* __usmuluta3: Fixed-point fractional library routines.
- (line 212)
+ (line 214)
* __usneguda2: Fixed-point fractional library routines.
- (line 329)
+ (line 331)
* __usnegudq2: Fixed-point fractional library routines.
- (line 324)
-* __usneguha2: Fixed-point fractional library routines.
(line 326)
+* __usneguha2: Fixed-point fractional library routines.
+ (line 328)
* __usneguhq2: Fixed-point fractional library routines.
- (line 321)
+ (line 322)
* __usneguqq2: Fixed-point fractional library routines.
- (line 319)
+ (line 321)
* __usnegusa2: Fixed-point fractional library routines.
- (line 328)
+ (line 329)
* __usnegusq2: Fixed-point fractional library routines.
- (line 322)
+ (line 324)
* __usneguta2: Fixed-point fractional library routines.
- (line 331)
+ (line 333)
* __ussubuda3: Fixed-point fractional library routines.
- (line 146)
+ (line 148)
* __ussubudq3: Fixed-point fractional library routines.
- (line 140)
-* __ussubuha3: Fixed-point fractional library routines.
(line 142)
+* __ussubuha3: Fixed-point fractional library routines.
+ (line 144)
* __ussubuhq3: Fixed-point fractional library routines.
- (line 136)
+ (line 138)
* __ussubuqq3: Fixed-point fractional library routines.
- (line 134)
+ (line 136)
* __ussubusa3: Fixed-point fractional library routines.
- (line 144)
+ (line 146)
* __ussubusq3: Fixed-point fractional library routines.
- (line 138)
+ (line 140)
* __ussubuta3: Fixed-point fractional library routines.
- (line 148)
-* abort: Portability. (line 20)
-* abs: Arithmetic. (line 200)
-* 'abs' and attributes: Expressions. (line 83)
-* absence_set: Processor pipeline description.
- (line 223)
-* 'absM2' instruction pattern: Standard Names. (line 564)
-* absolute value: Arithmetic. (line 200)
+ (line 150)
+* abort: Portability. (line 21)
+* abs: Arithmetic. (line 199)
+* abs and attributes: Expressions. (line 85)
* ABS_EXPR: Unary and Binary Expressions.
(line 6)
+* absence_set: Processor pipeline description.
+ (line 224)
+* absM2 instruction pattern: Standard Names. (line 569)
+* absolute value: Arithmetic. (line 199)
* access to operands: Accessors. (line 6)
* access to special operands: Special Accessors. (line 6)
* accessors: Accessors. (line 6)
-* ACCUMULATE_OUTGOING_ARGS: Stack Arguments. (line 48)
-* 'ACCUMULATE_OUTGOING_ARGS' and stack frames: Function Entry.
- (line 133)
-* ACCUM_TYPE_SIZE: Type Layout. (line 87)
-* ADA_LONG_TYPE_SIZE: Type Layout. (line 25)
+* ACCUM_TYPE_SIZE: Type Layout. (line 88)
+* ACCUMULATE_OUTGOING_ARGS: Stack Arguments. (line 49)
+* ACCUMULATE_OUTGOING_ARGS and stack frames: Function Entry. (line 135)
+* ADA_LONG_TYPE_SIZE: Type Layout. (line 26)
* Adding a new GIMPLE statement code: Adding a new GIMPLE statement code.
(line 6)
-* ADDITIONAL_REGISTER_NAMES: Instruction Output. (line 14)
-* 'addM3' instruction pattern: Standard Names. (line 260)
-* 'addMODEcc' instruction pattern: Standard Names. (line 1094)
-* 'addptrM3' instruction pattern: Standard Names. (line 266)
-* address constraints: Simple Constraints. (line 162)
-* addressing modes: Addressing Modes. (line 6)
-* address_operand: Machine-Independent Predicates.
- (line 62)
-* address_operand <1>: Simple Constraints. (line 166)
-* addr_diff_vec: Side Effects. (line 313)
-* 'addr_diff_vec', length of: Insn Lengths. (line 26)
+* ADDITIONAL_REGISTER_NAMES: Instruction Output. (line 15)
+* addM3 instruction pattern: Standard Names. (line 263)
+* addMODEcc instruction pattern: Standard Names. (line 1099)
+* addptrM3 instruction pattern: Standard Names. (line 269)
+* addr_diff_vec: Side Effects. (line 315)
+* addr_diff_vec, length of: Insn Lengths. (line 26)
* ADDR_EXPR: Storage References. (line 6)
-* addr_vec: Side Effects. (line 308)
-* 'addr_vec', length of: Insn Lengths. (line 26)
-* ADJUST_FIELD_ALIGN: Storage Layout. (line 195)
+* addr_vec: Side Effects. (line 310)
+* addr_vec, length of: Insn Lengths. (line 26)
+* address constraints: Simple Constraints. (line 164)
+* address_operand <1>: Simple Constraints. (line 168)
+* address_operand: Machine-Independent Predicates.
+ (line 63)
+* addressing modes: Addressing Modes. (line 6)
+* ADJUST_FIELD_ALIGN: Storage Layout. (line 197)
* ADJUST_INSN_LENGTH: Insn Lengths. (line 41)
-* ADJUST_REG_ALLOC_ORDER: Allocation Order. (line 22)
+* ADJUST_REG_ALLOC_ORDER: Allocation Order. (line 23)
* aggregates as return values: Aggregate Return. (line 6)
* alias: Alias analysis. (line 6)
-* 'allocate_stack' instruction pattern: Standard Names. (line 1408)
* ALL_REGS: Register Classes. (line 17)
+* allocate_stack instruction pattern: Standard Names. (line 1416)
* alternate entry points: Insns. (line 146)
* anchored addresses: Anchored Addresses. (line 6)
-* and: Arithmetic. (line 158)
-* 'and' and attributes: Expressions. (line 50)
-* 'and', canonicalization of: Insn Canonicalizations.
- (line 51)
-* 'andM3' instruction pattern: Standard Names. (line 276)
+* and: Arithmetic. (line 157)
+* and and attributes: Expressions. (line 50)
+* and, canonicalization of: Insn Canonicalizations.
+ (line 52)
+* andM3 instruction pattern: Standard Names. (line 279)
* ANNOTATE_EXPR: Unary and Binary Expressions.
(line 6)
* annotations: Annotations. (line 6)
* APPLY_RESULT_SIZE: Scalar Return. (line 112)
-* ARGS_GROW_DOWNWARD: Frame Layout. (line 34)
+* ARG_POINTER_CFA_OFFSET: Frame Layout. (line 196)
+* ARG_POINTER_REGNUM: Frame Registers. (line 41)
+* ARG_POINTER_REGNUM and virtual registers: Regs and Memory. (line 65)
+* arg_pointer_rtx: Frame Registers. (line 104)
+* ARGS_GROW_DOWNWARD: Frame Layout. (line 35)
* argument passing: Interface. (line 36)
* arguments in registers: Register Arguments. (line 6)
* arguments on stack: Stack Arguments. (line 6)
-* ARG_POINTER_CFA_OFFSET: Frame Layout. (line 194)
-* ARG_POINTER_REGNUM: Frame Registers. (line 40)
-* 'ARG_POINTER_REGNUM' and virtual registers: Regs and Memory.
- (line 65)
-* arg_pointer_rtx: Frame Registers. (line 104)
* arithmetic library: Soft float library routines.
(line 6)
-* arithmetic shift: Arithmetic. (line 173)
-* arithmetic shift with signed saturation: Arithmetic. (line 173)
-* arithmetic shift with unsigned saturation: Arithmetic. (line 173)
+* arithmetic shift: Arithmetic. (line 172)
+* arithmetic shift with signed saturation: Arithmetic. (line 172)
+* arithmetic shift with unsigned saturation: Arithmetic. (line 172)
* arithmetic, in RTL: Arithmetic. (line 6)
-* ARITHMETIC_TYPE_P: Types for C++. (line 59)
+* ARITHMETIC_TYPE_P: Types for C++. (line 61)
* array: Types. (line 6)
* ARRAY_RANGE_REF: Storage References. (line 6)
* ARRAY_REF: Storage References. (line 6)
* ARRAY_TYPE: Types. (line 6)
-* ashift: Arithmetic. (line 173)
-* 'ashift' and attributes: Expressions. (line 83)
-* ashiftrt: Arithmetic. (line 190)
-* 'ashiftrt' and attributes: Expressions. (line 83)
-* 'ashlM3' instruction pattern: Standard Names. (line 539)
-* 'ashrM3' instruction pattern: Standard Names. (line 549)
-* ASM_APP_OFF: File Framework. (line 76)
-* ASM_APP_ON: File Framework. (line 69)
-* ASM_COMMENT_START: File Framework. (line 64)
-* ASM_DECLARE_FUNCTION_NAME: Label Output. (line 108)
-* ASM_DECLARE_FUNCTION_SIZE: Label Output. (line 123)
-* ASM_DECLARE_OBJECT_NAME: Label Output. (line 136)
-* ASM_DECLARE_REGISTER_GLOBAL: Label Output. (line 164)
-* ASM_FINAL_SPEC: Driver. (line 81)
-* ASM_FINISH_DECLARE_OBJECT: Label Output. (line 172)
-* ASM_FORMAT_PRIVATE_NAME: Label Output. (line 398)
-* asm_fprintf: Instruction Output. (line 150)
-* ASM_FPRINTF_EXTENSIONS: Instruction Output. (line 160)
-* ASM_GENERATE_INTERNAL_LABEL: Label Output. (line 382)
-* asm_input: Side Effects. (line 295)
-* 'asm_input' and '/v': Flags. (line 76)
-* ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX: Exception Handling. (line 80)
-* asm_noperands: Insns. (line 304)
-* ASM_NO_SKIP_IN_TEXT: Alignment Output. (line 78)
-* 'asm_operands' and '/v': Flags. (line 76)
-* 'asm_operands', RTL sharing: Sharing. (line 45)
-* 'asm_operands', usage: Assembler. (line 6)
-* ASM_OUTPUT_ADDR_DIFF_ELT: Dispatch Tables. (line 8)
-* ASM_OUTPUT_ADDR_VEC_ELT: Dispatch Tables. (line 25)
-* ASM_OUTPUT_ALIGN: Alignment Output. (line 85)
-* ASM_OUTPUT_ALIGNED_BSS: Uninitialized Data. (line 45)
-* ASM_OUTPUT_ALIGNED_COMMON: Uninitialized Data. (line 29)
-* ASM_OUTPUT_ALIGNED_DECL_COMMON: Uninitialized Data. (line 36)
-* ASM_OUTPUT_ALIGNED_DECL_LOCAL: Uninitialized Data. (line 89)
-* ASM_OUTPUT_ALIGNED_LOCAL: Uninitialized Data. (line 82)
-* ASM_OUTPUT_ALIGN_WITH_NOP: Alignment Output. (line 90)
-* ASM_OUTPUT_ASCII: Data Output. (line 54)
-* ASM_OUTPUT_CASE_END: Dispatch Tables. (line 50)
-* ASM_OUTPUT_CASE_LABEL: Dispatch Tables. (line 37)
-* ASM_OUTPUT_COMMON: Uninitialized Data. (line 9)
-* ASM_OUTPUT_DEBUG_LABEL: Label Output. (line 370)
-* ASM_OUTPUT_DEF: Label Output. (line 419)
-* ASM_OUTPUT_DEF_FROM_DECLS: Label Output. (line 426)
-* ASM_OUTPUT_DWARF_DELTA: SDB and DWARF. (line 77)
-* ASM_OUTPUT_DWARF_OFFSET: SDB and DWARF. (line 86)
-* ASM_OUTPUT_DWARF_PCREL: SDB and DWARF. (line 92)
-* ASM_OUTPUT_DWARF_TABLE_REF: SDB and DWARF. (line 97)
-* ASM_OUTPUT_DWARF_VMS_DELTA: SDB and DWARF. (line 81)
-* ASM_OUTPUT_EXTERNAL: Label Output. (line 299)
-* ASM_OUTPUT_FDESC: Data Output. (line 63)
-* ASM_OUTPUT_FUNCTION_LABEL: Label Output. (line 16)
-* ASM_OUTPUT_INTERNAL_LABEL: Label Output. (line 27)
-* ASM_OUTPUT_LABEL: Label Output. (line 8)
-* ASM_OUTPUT_LABELREF: Label Output. (line 321)
-* ASM_OUTPUT_LABEL_REF: Label Output. (line 343)
-* ASM_OUTPUT_LOCAL: Uninitialized Data. (line 69)
-* ASM_OUTPUT_MAX_SKIP_ALIGN: Alignment Output. (line 94)
-* ASM_OUTPUT_MEASURED_SIZE: Label Output. (line 51)
-* ASM_OUTPUT_OPCODE: Instruction Output. (line 35)
-* ASM_OUTPUT_POOL_EPILOGUE: Data Output. (line 112)
-* ASM_OUTPUT_POOL_PROLOGUE: Data Output. (line 76)
-* ASM_OUTPUT_REG_POP: Instruction Output. (line 206)
-* ASM_OUTPUT_REG_PUSH: Instruction Output. (line 201)
-* ASM_OUTPUT_SIZE_DIRECTIVE: Label Output. (line 45)
-* ASM_OUTPUT_SKIP: Alignment Output. (line 72)
-* ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 83)
-* ASM_OUTPUT_SPECIAL_POOL_ENTRY: Data Output. (line 87)
-* ASM_OUTPUT_SYMBOL_REF: Label Output. (line 336)
-* ASM_OUTPUT_TYPE_DIRECTIVE: Label Output. (line 98)
-* ASM_OUTPUT_WEAKREF: Label Output. (line 231)
-* ASM_OUTPUT_WEAK_ALIAS: Label Output. (line 445)
-* ASM_PREFERRED_EH_DATA_FORMAT: Exception Handling. (line 66)
-* ASM_SPEC: Driver. (line 73)
-* ASM_STABD_OP: DBX Options. (line 34)
-* ASM_STABN_OP: DBX Options. (line 41)
-* ASM_STABS_OP: DBX Options. (line 28)
-* ASM_WEAKEN_DECL: Label Output. (line 223)
-* ASM_WEAKEN_LABEL: Label Output. (line 210)
+* AS_NEEDS_DASH_FOR_PIPED_INPUT: Driver. (line 89)
+* ashift: Arithmetic. (line 172)
+* ashift and attributes: Expressions. (line 85)
+* ashiftrt: Arithmetic. (line 189)
+* ashiftrt and attributes: Expressions. (line 85)
+* ashlM3 instruction pattern: Standard Names. (line 544)
+* ashrM3 instruction pattern: Standard Names. (line 554)
+* ASM_APP_OFF: File Framework. (line 78)
+* ASM_APP_ON: File Framework. (line 71)
+* ASM_COMMENT_START: File Framework. (line 66)
+* ASM_DECLARE_FUNCTION_NAME: Label Output. (line 111)
+* ASM_DECLARE_FUNCTION_SIZE: Label Output. (line 126)
+* ASM_DECLARE_OBJECT_NAME: Label Output. (line 139)
+* ASM_DECLARE_REGISTER_GLOBAL: Label Output. (line 168)
+* ASM_FINAL_SPEC: Driver. (line 82)
+* ASM_FINISH_DECLARE_OBJECT: Label Output. (line 176)
+* ASM_FORMAT_PRIVATE_NAME: Label Output. (line 402)
+* asm_fprintf: Instruction Output. (line 151)
+* ASM_FPRINTF_EXTENSIONS: Instruction Output. (line 162)
+* ASM_GENERATE_INTERNAL_LABEL: Label Output. (line 386)
+* asm_input: Side Effects. (line 297)
+* asm_input and /v: Flags. (line 76)
+* ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX: Exception Handling. (line 82)
+* ASM_NO_SKIP_IN_TEXT: Alignment Output. (line 79)
+* asm_noperands: Insns. (line 308)
+* asm_operands and /v: Flags. (line 76)
+* asm_operands, RTL sharing: Sharing. (line 45)
+* asm_operands, usage: Assembler. (line 6)
+* ASM_OUTPUT_ADDR_DIFF_ELT: Dispatch Tables. (line 9)
+* ASM_OUTPUT_ADDR_VEC_ELT: Dispatch Tables. (line 26)
+* ASM_OUTPUT_ALIGN: Alignment Output. (line 86)
+* ASM_OUTPUT_ALIGN_WITH_NOP: Alignment Output. (line 91)
+* ASM_OUTPUT_ALIGNED_BSS: Uninitialized Data. (line 46)
+* ASM_OUTPUT_ALIGNED_COMMON: Uninitialized Data. (line 30)
+* ASM_OUTPUT_ALIGNED_DECL_COMMON: Uninitialized Data. (line 38)
+* ASM_OUTPUT_ALIGNED_DECL_LOCAL: Uninitialized Data. (line 91)
+* ASM_OUTPUT_ALIGNED_LOCAL: Uninitialized Data. (line 83)
+* ASM_OUTPUT_ASCII: Data Output. (line 55)
+* ASM_OUTPUT_CASE_END: Dispatch Tables. (line 51)
+* ASM_OUTPUT_CASE_LABEL: Dispatch Tables. (line 38)
+* ASM_OUTPUT_COMMON: Uninitialized Data. (line 10)
+* ASM_OUTPUT_DEBUG_LABEL: Label Output. (line 374)
+* ASM_OUTPUT_DEF: Label Output. (line 423)
+* ASM_OUTPUT_DEF_FROM_DECLS: Label Output. (line 431)
+* ASM_OUTPUT_DWARF_DELTA: SDB and DWARF. (line 78)
+* ASM_OUTPUT_DWARF_OFFSET: SDB and DWARF. (line 87)
+* ASM_OUTPUT_DWARF_PCREL: SDB and DWARF. (line 93)
+* ASM_OUTPUT_DWARF_TABLE_REF: SDB and DWARF. (line 98)
+* ASM_OUTPUT_DWARF_VMS_DELTA: SDB and DWARF. (line 82)
+* ASM_OUTPUT_EXTERNAL: Label Output. (line 303)
+* ASM_OUTPUT_FDESC: Data Output. (line 64)
+* ASM_OUTPUT_FUNCTION_LABEL: Label Output. (line 17)
+* ASM_OUTPUT_INTERNAL_LABEL: Label Output. (line 29)
+* ASM_OUTPUT_LABEL: Label Output. (line 9)
+* ASM_OUTPUT_LABEL_REF: Label Output. (line 347)
+* ASM_OUTPUT_LABELREF: Label Output. (line 325)
+* ASM_OUTPUT_LOCAL: Uninitialized Data. (line 70)
+* ASM_OUTPUT_MAX_SKIP_ALIGN: Alignment Output. (line 95)
+* ASM_OUTPUT_MEASURED_SIZE: Label Output. (line 53)
+* ASM_OUTPUT_OPCODE: Instruction Output. (line 36)
+* ASM_OUTPUT_POOL_EPILOGUE: Data Output. (line 114)
+* ASM_OUTPUT_POOL_PROLOGUE: Data Output. (line 77)
+* ASM_OUTPUT_REG_POP: Instruction Output. (line 208)
+* ASM_OUTPUT_REG_PUSH: Instruction Output. (line 203)
+* ASM_OUTPUT_SIZE_DIRECTIVE: Label Output. (line 47)
+* ASM_OUTPUT_SKIP: Alignment Output. (line 73)
+* ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 85)
+* ASM_OUTPUT_SPECIAL_POOL_ENTRY: Data Output. (line 89)
+* ASM_OUTPUT_SYMBOL_REF: Label Output. (line 340)
+* ASM_OUTPUT_TYPE_DIRECTIVE: Label Output. (line 101)
+* ASM_OUTPUT_WEAK_ALIAS: Label Output. (line 449)
+* ASM_OUTPUT_WEAKREF: Label Output. (line 235)
+* ASM_PREFERRED_EH_DATA_FORMAT: Exception Handling. (line 67)
+* ASM_SPEC: Driver. (line 74)
+* ASM_STABD_OP: DBX Options. (line 36)
+* ASM_STABN_OP: DBX Options. (line 43)
+* ASM_STABS_OP: DBX Options. (line 29)
+* ASM_WEAKEN_DECL: Label Output. (line 227)
+* ASM_WEAKEN_LABEL: Label Output. (line 214)
+* assemble_name: Label Output. (line 8)
+* assemble_name_raw: Label Output. (line 28)
* assembler format: File Framework. (line 6)
* assembler instructions in RTL: Assembler. (line 6)
-* ASSEMBLER_DIALECT: Instruction Output. (line 172)
-* assemble_name: Label Output. (line 8)
-* assemble_name_raw: Label Output. (line 27)
+* ASSEMBLER_DIALECT: Instruction Output. (line 174)
* assigning attribute values to insns: Tagging Insns. (line 6)
-* ASSUME_EXTENDED_UNWIND_CONTEXT: Frame Registers. (line 165)
+* ASSUME_EXTENDED_UNWIND_CONTEXT: Frame Registers. (line 164)
* asterisk in template: Output Statement. (line 29)
-* AS_NEEDS_DASH_FOR_PIPED_INPUT: Driver. (line 88)
-* 'atan2M3' instruction pattern: Standard Names. (line 647)
-* atomic: GTY Options. (line 203)
-* 'atomic_addMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_add_fetchMODE' instruction pattern: Standard Names.
- (line 1839)
-* 'atomic_andMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_and_fetchMODE' instruction pattern: Standard Names.
- (line 1839)
-* 'atomic_compare_and_swapMODE' instruction pattern: Standard Names.
- (line 1746)
-* 'atomic_exchangeMODE' instruction pattern: Standard Names. (line 1798)
-* 'atomic_fetch_addMODE' instruction pattern: Standard Names.
- (line 1824)
-* 'atomic_fetch_andMODE' instruction pattern: Standard Names.
- (line 1824)
-* 'atomic_fetch_nandMODE' instruction pattern: Standard Names.
- (line 1824)
-* 'atomic_fetch_orMODE' instruction pattern: Standard Names. (line 1824)
-* 'atomic_fetch_subMODE' instruction pattern: Standard Names.
- (line 1824)
-* 'atomic_fetch_xorMODE' instruction pattern: Standard Names.
- (line 1824)
-* 'atomic_loadMODE' instruction pattern: Standard Names. (line 1777)
-* 'atomic_nandMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_nand_fetchMODE' instruction pattern: Standard Names.
- (line 1839)
-* 'atomic_orMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_or_fetchMODE' instruction pattern: Standard Names. (line 1839)
-* 'atomic_storeMODE' instruction pattern: Standard Names. (line 1787)
-* 'atomic_subMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_sub_fetchMODE' instruction pattern: Standard Names.
- (line 1839)
-* 'atomic_test_and_set' instruction pattern: Standard Names. (line 1856)
-* 'atomic_xorMODE' instruction pattern: Standard Names. (line 1810)
-* 'atomic_xor_fetchMODE' instruction pattern: Standard Names.
- (line 1839)
-* attr: Expressions. (line 163)
+* atan2M3 instruction pattern: Standard Names. (line 652)
+* atomic: GTY Options. (line 196)
+* atomic_add_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_addMODE instruction pattern: Standard Names. (line 1820)
+* atomic_and_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_andMODE instruction pattern: Standard Names. (line 1820)
+* atomic_compare_and_swapMODE instruction pattern: Standard Names.
+ (line 1756)
+* atomic_exchangeMODE instruction pattern: Standard Names. (line 1808)
+* atomic_fetch_addMODE instruction pattern: Standard Names. (line 1834)
+* atomic_fetch_andMODE instruction pattern: Standard Names. (line 1834)
+* atomic_fetch_nandMODE instruction pattern: Standard Names. (line 1834)
+* atomic_fetch_orMODE instruction pattern: Standard Names. (line 1834)
+* atomic_fetch_subMODE instruction pattern: Standard Names. (line 1834)
+* atomic_fetch_xorMODE instruction pattern: Standard Names. (line 1834)
+* atomic_loadMODE instruction pattern: Standard Names. (line 1787)
+* atomic_nand_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_nandMODE instruction pattern: Standard Names. (line 1820)
+* atomic_or_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_orMODE instruction pattern: Standard Names. (line 1820)
+* atomic_storeMODE instruction pattern: Standard Names. (line 1797)
+* atomic_sub_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_subMODE instruction pattern: Standard Names. (line 1820)
+* atomic_test_and_set instruction pattern: Standard Names. (line 1866)
+* atomic_xor_fetchMODE instruction pattern: Standard Names. (line 1849)
+* atomic_xorMODE instruction pattern: Standard Names. (line 1820)
* attr <1>: Tagging Insns. (line 54)
+* attr: Expressions. (line 165)
+* attr_flag: Expressions. (line 140)
* attribute expressions: Expressions. (line 6)
* attribute specifications: Attr Example. (line 6)
* attribute specifications example: Attr Example. (line 6)
+* ATTRIBUTE_ALIGNED_VALUE: Storage Layout. (line 179)
* attributes: Attributes. (line 6)
* attributes, defining: Defining Attributes.
(line 6)
* attributes, target-specific: Target Attributes. (line 6)
-* ATTRIBUTE_ALIGNED_VALUE: Storage Layout. (line 177)
-* attr_flag: Expressions. (line 138)
-* autoincrement addressing, availability: Portability. (line 20)
+* autoincrement addressing, availability: Portability. (line 21)
* autoincrement/decrement addressing: Simple Constraints. (line 30)
* automata_option: Processor pipeline description.
- (line 304)
+ (line 305)
* automaton based pipeline description: Processor pipeline description.
(line 6)
-* automaton based pipeline description <1>: Processor pipeline description.
- (line 49)
* automaton based scheduler: Processor pipeline description.
(line 6)
* AVOID_CCMODE_COPIES: Values in Registers.
- (line 150)
+ (line 153)
* backslash: Output Template. (line 46)
-* barrier: Insns. (line 176)
-* 'barrier' and '/f': Flags. (line 107)
-* 'barrier' and '/v': Flags. (line 44)
-* BASE_REG_CLASS: Register Classes. (line 111)
+* barrier: Insns. (line 177)
+* barrier and /f: Flags. (line 107)
+* barrier and /v: Flags. (line 44)
+* BASE_REG_CLASS: Register Classes. (line 114)
* basic block: Basic Blocks. (line 6)
* Basic Statements: Basic Statements. (line 6)
* basic-block.h: Control Flow. (line 6)
-* basic_block: Basic Blocks. (line 6)
* BASIC_BLOCK: Basic Blocks. (line 14)
+* basic_block: Basic Blocks. (line 6)
* BB_HEAD, BB_END: Maintaining the CFG.
- (line 76)
-* bb_seq: GIMPLE sequences. (line 72)
-* BIGGEST_ALIGNMENT: Storage Layout. (line 162)
-* BIGGEST_FIELD_ALIGNMENT: Storage Layout. (line 188)
+ (line 77)
+* bb_seq: GIMPLE sequences. (line 73)
+* BIGGEST_ALIGNMENT: Storage Layout. (line 164)
+* BIGGEST_FIELD_ALIGNMENT: Storage Layout. (line 190)
* BImode: Machine Modes. (line 22)
* BIND_EXPR: Unary and Binary Expressions.
(line 6)
* BINFO_TYPE: Classes. (line 6)
* bit-fields: Bit-Fields. (line 6)
-* BITFIELD_NBYTES_LIMITED: Storage Layout. (line 398)
-* BITS_BIG_ENDIAN: Storage Layout. (line 11)
-* 'BITS_BIG_ENDIAN', effect on 'sign_extract': Bit-Fields. (line 8)
-* BITS_PER_UNIT: Machine Modes. (line 354)
-* BITS_PER_WORD: Storage Layout. (line 50)
-* bitwise complement: Arithmetic. (line 154)
-* bitwise exclusive-or: Arithmetic. (line 168)
-* bitwise inclusive-or: Arithmetic. (line 163)
-* bitwise logical-and: Arithmetic. (line 158)
* BIT_AND_EXPR: Unary and Binary Expressions.
(line 6)
* BIT_IOR_EXPR: Unary and Binary Expressions.
@@ -47070,27 +47519,36 @@ Concept Index
(line 6)
* BIT_XOR_EXPR: Unary and Binary Expressions.
(line 6)
-* BLKmode: Machine Modes. (line 185)
-* 'BLKmode', and function return values: Calls. (line 23)
-* 'blockage' instruction pattern: Standard Names. (line 1609)
-* Blocks: Blocks. (line 6)
+* BITFIELD_NBYTES_LIMITED: Storage Layout. (line 402)
+* BITS_BIG_ENDIAN: Storage Layout. (line 12)
+* BITS_BIG_ENDIAN, effect on sign_extract: Bit-Fields. (line 8)
+* BITS_PER_UNIT: Machine Modes. (line 355)
+* BITS_PER_WORD: Storage Layout. (line 51)
+* bitwise complement: Arithmetic. (line 153)
+* bitwise exclusive-or: Arithmetic. (line 167)
+* bitwise inclusive-or: Arithmetic. (line 162)
+* bitwise logical-and: Arithmetic. (line 157)
+* BLKmode: Machine Modes. (line 186)
+* BLKmode, and function return values: Calls. (line 23)
* BLOCK_FOR_INSN, gimple_bb: Maintaining the CFG.
- (line 28)
-* BLOCK_REG_PADDING: Register Arguments. (line 242)
-* BND32mode: Machine Modes. (line 209)
-* BND64mode: Machine Modes. (line 209)
-* bool: Misc. (line 992)
+ (line 29)
+* BLOCK_REG_PADDING: Register Arguments. (line 244)
+* blockage instruction pattern: Standard Names. (line 1619)
+* Blocks: Blocks. (line 6)
+* BND32mode: Machine Modes. (line 210)
+* BND64mode: Machine Modes. (line 210)
+* bool: Misc. (line 998)
+* BOOL_TYPE_SIZE: Type Layout. (line 44)
* BOOLEAN_TYPE: Types. (line 6)
-* BOOL_TYPE_SIZE: Type Layout. (line 43)
* branch prediction: Profile information.
(line 24)
-* BRANCH_COST: Costs. (line 104)
-* break_out_memory_refs: Addressing Modes. (line 134)
+* BRANCH_COST: Costs. (line 105)
+* break_out_memory_refs: Addressing Modes. (line 135)
* BREAK_STMT: Statements for C++. (line 6)
-* BSS_SECTION_ASM_OP: Sections. (line 67)
+* BSS_SECTION_ASM_OP: Sections. (line 68)
* bswap: Arithmetic. (line 246)
-* 'bswapM2' instruction pattern: Standard Names. (line 557)
-* 'btruncM2' instruction pattern: Standard Names. (line 665)
+* bswapM2 instruction pattern: Standard Names. (line 562)
+* btruncM2 instruction pattern: Standard Names. (line 670)
* build0: Macros and Functions.
(line 16)
* build1: Macros and Functions.
@@ -47105,160 +47563,154 @@ Concept Index
(line 21)
* build6: Macros and Functions.
(line 22)
-* 'builtin_longjmp' instruction pattern: Standard Names. (line 1506)
-* 'builtin_setjmp_receiver' instruction pattern: Standard Names.
- (line 1496)
-* 'builtin_setjmp_setup' instruction pattern: Standard Names.
- (line 1485)
-* BYTES_BIG_ENDIAN: Storage Layout. (line 23)
-* 'BYTES_BIG_ENDIAN', effect on 'subreg': Regs and Memory. (line 219)
-* byte_mode: Machine Modes. (line 367)
+* builtin_longjmp instruction pattern: Standard Names. (line 1516)
+* builtin_setjmp_receiver instruction pattern: Standard Names.
+ (line 1506)
+* builtin_setjmp_setup instruction pattern: Standard Names. (line 1495)
+* byte_mode: Machine Modes. (line 368)
+* BYTES_BIG_ENDIAN: Storage Layout. (line 24)
+* BYTES_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 221)
* C statements for assembler output: Output Statement. (line 6)
-* cache: GTY Options. (line 125)
-* call: Flags. (line 221)
+* C_COMMON_OVERRIDE_OPTIONS: Run-time Target. (line 137)
+* c_register_pragma: Misc. (line 410)
+* c_register_pragma_with_expansion: Misc. (line 412)
+* cache: GTY Options. (line 124)
* call <1>: Side Effects. (line 92)
-* 'call' instruction pattern: Standard Names. (line 1151)
-* 'call' usage: Calls. (line 10)
-* 'call', in 'call_insn': Flags. (line 33)
-* 'call', in 'mem': Flags. (line 81)
+* call: Flags. (line 221)
+* call instruction pattern: Standard Names. (line 1156)
+* call usage: Calls. (line 10)
+* call, in call_insn: Flags. (line 33)
+* call, in mem: Flags. (line 81)
* call-clobbered register: Register Basics. (line 35)
-* call-clobbered register <1>: Register Basics. (line 46)
-* call-clobbered register <2>: Register Basics. (line 53)
* call-saved register: Register Basics. (line 35)
-* call-saved register <1>: Register Basics. (line 46)
-* call-saved register <2>: Register Basics. (line 53)
* call-used register: Register Basics. (line 35)
-* call-used register <1>: Register Basics. (line 46)
-* call-used register <2>: Register Basics. (line 53)
-* calling conventions: Stack and Calling. (line 6)
-* calling functions in RTL: Calls. (line 6)
* CALL_EXPR: Unary and Binary Expressions.
(line 6)
* call_insn: Insns. (line 95)
-* 'call_insn' and '/c': Flags. (line 33)
-* 'call_insn' and '/f': Flags. (line 107)
-* 'call_insn' and '/i': Flags. (line 24)
-* 'call_insn' and '/j': Flags. (line 161)
-* 'call_insn' and '/s': Flags. (line 49)
-* 'call_insn' and '/s' <1>: Flags. (line 148)
-* 'call_insn' and '/u': Flags. (line 19)
-* 'call_insn' and '/u' <1>: Flags. (line 39)
-* 'call_insn' and '/u' or '/i': Flags. (line 29)
-* 'call_insn' and '/v': Flags. (line 44)
+* call_insn and /c: Flags. (line 33)
+* call_insn and /f: Flags. (line 107)
+* call_insn and /i: Flags. (line 24)
+* call_insn and /j: Flags. (line 161)
+* call_insn and /s: Flags. (line 49)
+* call_insn and /u: Flags. (line 19)
+* call_insn and /u or /i: Flags. (line 29)
+* call_insn and /v: Flags. (line 44)
* CALL_INSN_FUNCTION_USAGE: Insns. (line 101)
-* 'call_pop' instruction pattern: Standard Names. (line 1179)
-* CALL_POPS_ARGS: Stack Arguments. (line 138)
-* CALL_REALLY_USED_REGISTERS: Register Basics. (line 45)
-* CALL_USED_REGISTERS: Register Basics. (line 34)
+* call_pop instruction pattern: Standard Names. (line 1184)
+* CALL_POPS_ARGS: Stack Arguments. (line 139)
+* CALL_REALLY_USED_REGISTERS: Register Basics. (line 46)
+* CALL_USED_REGISTERS: Register Basics. (line 35)
* call_used_regs: Register Basics. (line 59)
-* 'call_value' instruction pattern: Standard Names. (line 1171)
-* 'call_value_pop' instruction pattern: Standard Names. (line 1179)
+* call_value instruction pattern: Standard Names. (line 1176)
+* call_value_pop instruction pattern: Standard Names. (line 1184)
+* calling conventions: Stack and Calling. (line 6)
+* calling functions in RTL: Calls. (line 6)
+* can_create_pseudo_p: Standard Names. (line 75)
+* can_fallthru: Basic Blocks. (line 67)
* canadian: Configure Terms. (line 6)
-* CANNOT_CHANGE_MODE_CLASS: Register Classes. (line 533)
-* 'CANNOT_CHANGE_MODE_CLASS' and subreg semantics: Regs and Memory.
- (line 276)
+* CANNOT_CHANGE_MODE_CLASS: Register Classes. (line 538)
+* CANNOT_CHANGE_MODE_CLASS and subreg semantics: Regs and Memory.
+ (line 280)
* canonicalization of instructions: Insn Canonicalizations.
(line 6)
-* 'canonicalize_funcptr_for_compare' instruction pattern: Standard Names.
- (line 1340)
-* can_create_pseudo_p: Standard Names. (line 75)
-* can_fallthru: Basic Blocks. (line 67)
+* canonicalize_funcptr_for_compare instruction pattern: Standard Names.
+ (line 1347)
* caret: Multi-Alternative. (line 52)
-* 'casesi' instruction pattern: Standard Names. (line 1272)
-* CASE_VECTOR_MODE: Misc. (line 26)
-* CASE_VECTOR_PC_RELATIVE: Misc. (line 39)
-* CASE_VECTOR_SHORTEN_MODE: Misc. (line 30)
-* 'cbranchMODE4' instruction pattern: Standard Names. (line 1140)
-* cc0: Regs and Memory. (line 303)
+* CASE_VECTOR_MODE: Misc. (line 27)
+* CASE_VECTOR_PC_RELATIVE: Misc. (line 40)
+* CASE_VECTOR_SHORTEN_MODE: Misc. (line 31)
+* casesi instruction pattern: Standard Names. (line 1278)
+* cbranchMODE4 instruction pattern: Standard Names. (line 1145)
* cc0 <1>: CC0 Condition Codes.
(line 6)
-* 'cc0', RTL sharing: Sharing. (line 27)
-* cc0_rtx: Regs and Memory. (line 329)
-* CC1PLUS_SPEC: Driver. (line 63)
-* CC1_SPEC: Driver. (line 55)
-* CCmode: Machine Modes. (line 178)
-* CCmode <1>: MODE_CC Condition Codes.
- (line 6)
+* cc0: Regs and Memory. (line 307)
+* cc0, RTL sharing: Sharing. (line 27)
+* cc0_rtx: Regs and Memory. (line 333)
+* CC1_SPEC: Driver. (line 56)
+* CC1PLUS_SPEC: Driver. (line 64)
* cc_status: CC0 Condition Codes.
(line 6)
* CC_STATUS_MDEP: CC0 Condition Codes.
- (line 16)
+ (line 17)
* CC_STATUS_MDEP_INIT: CC0 Condition Codes.
- (line 22)
-* CDImode: Machine Modes. (line 204)
-* 'ceilM2' instruction pattern: Standard Names. (line 681)
+ (line 23)
+* CCmode <1>: MODE_CC Condition Codes.
+ (line 6)
+* CCmode: Machine Modes. (line 179)
+* CDImode: Machine Modes. (line 205)
* CEIL_DIV_EXPR: Unary and Binary Expressions.
(line 6)
* CEIL_MOD_EXPR: Unary and Binary Expressions.
(line 6)
-* CFA_FRAME_BASE_OFFSET: Frame Layout. (line 226)
+* ceilM2 instruction pattern: Standard Names. (line 686)
+* CFA_FRAME_BASE_OFFSET: Frame Layout. (line 228)
* CFG verification: Maintaining the CFG.
- (line 117)
+ (line 119)
* CFG, Control Flow Graph: Control Flow. (line 6)
* cfghooks.h: Maintaining the CFG.
(line 6)
-* cgraph_finalize_function: Parsing pass. (line 51)
-* chain_circular: GTY Options. (line 167)
-* chain_next: GTY Options. (line 167)
-* chain_prev: GTY Options. (line 167)
+* cgraph_finalize_function: Parsing pass. (line 52)
+* chain_circular: GTY Options. (line 162)
+* chain_next: GTY Options. (line 162)
+* chain_prev: GTY Options. (line 162)
* change_address: Standard Names. (line 47)
-* CHAR_TYPE_SIZE: Type Layout. (line 38)
-* 'check_stack' instruction pattern: Standard Names. (line 1426)
-* CHImode: Machine Modes. (line 204)
+* CHAR_TYPE_SIZE: Type Layout. (line 39)
+* check_stack instruction pattern: Standard Names. (line 1434)
+* CHImode: Machine Modes. (line 205)
* CILK_PLUS: Cilk Plus Transformation.
(line 6)
* class definitions, register: Register Classes. (line 6)
* class preference constraints: Class Preferences. (line 6)
* class, scope: Classes. (line 6)
+* CLASS_MAX_NREGS: Register Classes. (line 526)
+* CLASS_TYPE_P: Types for C++. (line 65)
* classes of RTX codes: RTL Classes. (line 6)
* CLASSTYPE_DECLARED_CLASS: Classes. (line 6)
* CLASSTYPE_HAS_MUTABLE: Classes. (line 85)
* CLASSTYPE_NON_POD_P: Classes. (line 90)
-* CLASS_MAX_NREGS: Register Classes. (line 521)
-* CLASS_TYPE_P: Types for C++. (line 63)
-* Cleanups: Cleanups. (line 6)
* CLEANUP_DECL: Statements for C++. (line 6)
* CLEANUP_EXPR: Statements for C++. (line 6)
* CLEANUP_POINT_EXPR: Unary and Binary Expressions.
(line 6)
* CLEANUP_STMT: Statements for C++. (line 6)
-* 'clear_cache' instruction pattern: Standard Names. (line 1916)
-* CLEAR_INSN_CACHE: Trampolines. (line 98)
-* CLEAR_RATIO: Costs. (line 204)
+* Cleanups: Cleanups. (line 6)
+* clear_cache instruction pattern: Standard Names. (line 1926)
+* CLEAR_INSN_CACHE: Trampolines. (line 99)
+* CLEAR_RATIO: Costs. (line 205)
* clobber: Side Effects. (line 106)
* clrsb: Arithmetic. (line 215)
-* 'clrsbM2' instruction pattern: Standard Names. (line 746)
+* clrsbM2 instruction pattern: Standard Names. (line 751)
* clz: Arithmetic. (line 222)
-* 'clzM2' instruction pattern: Standard Names. (line 753)
-* CLZ_DEFINED_VALUE_AT_ZERO: Misc. (line 304)
-* 'cmpmemM' instruction pattern: Standard Names. (line 894)
-* 'cmpstrM' instruction pattern: Standard Names. (line 873)
-* 'cmpstrnM' instruction pattern: Standard Names. (line 860)
+* CLZ_DEFINED_VALUE_AT_ZERO: Misc. (line 305)
+* clzM2 instruction pattern: Standard Names. (line 758)
+* cmpmemM instruction pattern: Standard Names. (line 899)
+* cmpstrM instruction pattern: Standard Names. (line 878)
+* cmpstrnM instruction pattern: Standard Names. (line 865)
* code generation RTL sequences: Expander Definitions.
(line 6)
-* code iterators in '.md' files: Code Iterators. (line 6)
-* codes, RTL expression: RTL Objects. (line 47)
-* code_label: Insns. (line 125)
+* code iterators in .md files: Code Iterators. (line 6)
* CODE_LABEL: Basic Blocks. (line 50)
-* 'code_label' and '/i': Flags. (line 59)
-* 'code_label' and '/v': Flags. (line 44)
+* code_label: Insns. (line 125)
+* code_label and /i: Flags. (line 59)
+* code_label and /v: Flags. (line 44)
* CODE_LABEL_NUMBER: Insns. (line 125)
-* COImode: Machine Modes. (line 204)
+* codes, RTL expression: RTL Objects. (line 47)
+* COImode: Machine Modes. (line 205)
* COLLECT2_HOST_INITIALIZATION: Host Misc. (line 32)
-* COLLECT_EXPORT_LIST: Misc. (line 866)
+* COLLECT_EXPORT_LIST: Misc. (line 870)
* COLLECT_SHARED_FINI_FUNC: Macros for Initialization.
- (line 43)
+ (line 44)
* COLLECT_SHARED_INIT_FUNC: Macros for Initialization.
- (line 32)
+ (line 33)
* commit_edge_insertions: Maintaining the CFG.
- (line 105)
-* compare: Arithmetic. (line 46)
-* 'compare', canonicalization of: Insn Canonicalizations.
- (line 36)
+ (line 107)
+* compare: Arithmetic. (line 43)
+* compare, canonicalization of: Insn Canonicalizations.
+ (line 37)
* comparison_operator: Machine-Independent Predicates.
- (line 110)
+ (line 111)
* compiler passes and files: Passes. (line 6)
-* complement, bitwise: Arithmetic. (line 154)
+* complement, bitwise: Arithmetic. (line 153)
* COMPLEX_CST: Constant expressions.
(line 6)
* COMPLEX_EXPR: Unary and Binary Expressions.
@@ -47273,16 +47725,19 @@ Concept Index
* COMPOUND_LITERAL_EXPR: Unary and Binary Expressions.
(line 6)
* COMPOUND_LITERAL_EXPR_DECL: Unary and Binary Expressions.
- (line 377)
+ (line 378)
* COMPOUND_LITERAL_EXPR_DECL_EXPR: Unary and Binary Expressions.
- (line 377)
-* computed jump: Edges. (line 127)
+ (line 378)
+* computed jump: Edges. (line 128)
* computing the length of an insn: Insn Lengths. (line 6)
-* concat: Regs and Memory. (line 381)
-* concatn: Regs and Memory. (line 387)
+* concat: Regs and Memory. (line 385)
+* concatn: Regs and Memory. (line 391)
* cond: Comparisons. (line 90)
-* 'cond' and attributes: Expressions. (line 37)
-* condition code register: Regs and Memory. (line 303)
+* cond and attributes: Expressions. (line 37)
+* cond_exec: Side Effects. (line 254)
+* COND_EXPR: Unary and Binary Expressions.
+ (line 6)
+* condition code register: Regs and Memory. (line 307)
* condition code status: Condition Code. (line 6)
* condition codes: Comparisons. (line 20)
* conditional execution: Conditional Execution.
@@ -47290,70 +47745,67 @@ Concept Index
* Conditional Expressions: Conditional Expressions.
(line 6)
* conditions, in patterns: Patterns. (line 43)
-* cond_exec: Side Effects. (line 253)
-* COND_EXPR: Unary and Binary Expressions.
- (line 6)
-* configuration file: Filesystem. (line 6)
* configuration file <1>: Host Misc. (line 6)
+* configuration file: Filesystem. (line 6)
* configure terms: Configure Terms. (line 6)
* CONJ_EXPR: Unary and Binary Expressions.
(line 6)
* const: Constants. (line 140)
-* const0_rtx: Constants. (line 21)
* CONST0_RTX: Constants. (line 160)
-* const1_rtx: Constants. (line 21)
+* const0_rtx: Constants. (line 21)
* CONST1_RTX: Constants. (line 160)
-* const2_rtx: Constants. (line 21)
+* const1_rtx: Constants. (line 21)
* CONST2_RTX: Constants. (line 160)
+* const2_rtx: Constants. (line 21)
+* CONST_DECL: Declarations. (line 6)
+* const_double: Constants. (line 37)
+* const_double, RTL sharing: Sharing. (line 29)
+* CONST_DOUBLE_LOW: Constants. (line 54)
+* const_double_operand: Machine-Independent Predicates.
+ (line 21)
+* const_fixed: Constants. (line 93)
+* const_int: Constants. (line 8)
+* const_int and attribute tests: Expressions. (line 47)
+* const_int and attributes: Expressions. (line 10)
+* const_int, RTL sharing: Sharing. (line 23)
+* const_int_operand: Machine-Independent Predicates.
+ (line 16)
+* const_string: Constants. (line 112)
+* const_string and attributes: Expressions. (line 20)
+* const_true_rtx: Constants. (line 31)
+* const_vector: Constants. (line 100)
+* const_vector, RTL sharing: Sharing. (line 32)
+* CONST_WIDE_INT: Constants. (line 67)
+* CONST_WIDE_INT_ELT: Constants. (line 89)
+* CONST_WIDE_INT_NUNITS: Constants. (line 84)
+* CONST_WIDE_INT_VEC: Constants. (line 80)
* constant attributes: Constant Attributes.
(line 6)
* constant definitions: Constant Definitions.
(line 6)
-* constants in constraints: Simple Constraints. (line 68)
-* CONSTANT_ADDRESS_P: Addressing Modes. (line 28)
-* CONSTANT_ALIGNMENT: Storage Layout. (line 241)
-* CONSTANT_P: Addressing Modes. (line 35)
+* CONSTANT_ADDRESS_P: Addressing Modes. (line 29)
+* CONSTANT_ALIGNMENT: Storage Layout. (line 245)
+* CONSTANT_P: Addressing Modes. (line 36)
* CONSTANT_POOL_ADDRESS_P: Flags. (line 10)
-* CONSTANT_POOL_BEFORE_FUNCTION: Data Output. (line 68)
+* CONSTANT_POOL_BEFORE_FUNCTION: Data Output. (line 69)
+* constants in constraints: Simple Constraints. (line 70)
* constm1_rtx: Constants. (line 21)
* constraint modifier characters: Modifiers. (line 6)
-* constraint, matching: Simple Constraints. (line 140)
+* constraint, matching: Simple Constraints. (line 142)
+* constraint_num: C Constraint Interface.
+ (line 31)
+* constraint_satisfied_p: C Constraint Interface.
+ (line 44)
* constraints: Constraints. (line 6)
* constraints, defining: Define Constraints. (line 6)
* constraints, machine specific: Machine Constraints.
(line 6)
* constraints, testing: C Constraint Interface.
(line 6)
-* constraint_num: C Constraint Interface.
- (line 30)
-* constraint_satisfied_p: C Constraint Interface.
- (line 42)
* CONSTRUCTOR: Unary and Binary Expressions.
(line 6)
* constructors, automatic calls: Collect2. (line 15)
* constructors, output of: Initialization. (line 6)
-* CONST_DECL: Declarations. (line 6)
-* const_double: Constants. (line 37)
-* 'const_double', RTL sharing: Sharing. (line 29)
-* CONST_DOUBLE_LOW: Constants. (line 54)
-* const_double_operand: Machine-Independent Predicates.
- (line 20)
-* const_fixed: Constants. (line 93)
-* const_int: Constants. (line 8)
-* 'const_int' and attribute tests: Expressions. (line 47)
-* 'const_int' and attributes: Expressions. (line 10)
-* 'const_int', RTL sharing: Sharing. (line 23)
-* const_int_operand: Machine-Independent Predicates.
- (line 15)
-* const_string: Constants. (line 112)
-* 'const_string' and attributes: Expressions. (line 20)
-* const_true_rtx: Constants. (line 31)
-* const_vector: Constants. (line 100)
-* 'const_vector', RTL sharing: Sharing. (line 32)
-* CONST_WIDE_INT: Constants. (line 67)
-* CONST_WIDE_INT_ELT: Constants. (line 89)
-* CONST_WIDE_INT_NUNITS: Constants. (line 84)
-* CONST_WIDE_INT_VEC: Constants. (line 80)
* container: Containers. (line 6)
* CONTINUE_STMT: Statements for C++. (line 6)
* contributors: Contributors. (line 6)
@@ -47363,143 +47815,132 @@ Concept Index
* conversions: Conversions. (line 6)
* CONVERT_EXPR: Unary and Binary Expressions.
(line 6)
-* 'copysignM3' instruction pattern: Standard Names. (line 727)
-* copy_rtx: Addressing Modes. (line 189)
+* copy_rtx: Addressing Modes. (line 190)
* copy_rtx_if_shared: Sharing. (line 64)
-* 'cosM2' instruction pattern: Standard Names. (line 593)
+* copysignM3 instruction pattern: Standard Names. (line 732)
+* cosM2 instruction pattern: Standard Names. (line 598)
* costs of instructions: Costs. (line 6)
-* CPLUSPLUS_CPP_SPEC: Driver. (line 50)
-* CPP_SPEC: Driver. (line 43)
-* CP_INTEGRAL_TYPE: Types for C++. (line 55)
+* CP_INTEGRAL_TYPE: Types for C++. (line 57)
* cp_namespace_decls: Namespaces. (line 49)
* CP_TYPE_CONST_NON_VOLATILE_P: Types for C++. (line 33)
* CP_TYPE_CONST_P: Types for C++. (line 24)
* cp_type_quals: Types for C++. (line 6)
-* cp_type_quals <1>: Types for C++. (line 16)
* CP_TYPE_RESTRICT_P: Types for C++. (line 30)
* CP_TYPE_VOLATILE_P: Types for C++. (line 27)
-* CQImode: Machine Modes. (line 204)
+* CPLUSPLUS_CPP_SPEC: Driver. (line 51)
+* CPP_SPEC: Driver. (line 44)
+* CQImode: Machine Modes. (line 205)
* cross compilation and floating point: Floating Point. (line 6)
-* crtl->args.pops_args: Function Entry. (line 104)
-* crtl->args.pretend_args_size: Function Entry. (line 110)
+* CRT_CALL_STATIC_FUNCTION: Sections. (line 121)
+* crtl->args.pops_args: Function Entry. (line 106)
+* crtl->args.pretend_args_size: Function Entry. (line 112)
* crtl->outgoing_args_size: Stack Arguments. (line 48)
* CRTSTUFF_T_CFLAGS: Target Fragment. (line 15)
* CRTSTUFF_T_CFLAGS_S: Target Fragment. (line 19)
-* CRT_CALL_STATIC_FUNCTION: Sections. (line 120)
-* CSImode: Machine Modes. (line 204)
-* 'cstoreMODE4' instruction pattern: Standard Names. (line 1101)
-* CTImode: Machine Modes. (line 204)
-* 'ctrapMM4' instruction pattern: Standard Names. (line 1578)
+* CSImode: Machine Modes. (line 205)
+* cstoreMODE4 instruction pattern: Standard Names. (line 1106)
+* CTImode: Machine Modes. (line 205)
+* ctrapMM4 instruction pattern: Standard Names. (line 1588)
* ctz: Arithmetic. (line 230)
-* 'ctzM2' instruction pattern: Standard Names. (line 762)
-* CTZ_DEFINED_VALUE_AT_ZERO: Misc. (line 305)
-* CUMULATIVE_ARGS: Register Arguments. (line 140)
-* current_function_is_leaf: Leaf Functions. (line 50)
-* current_function_uses_only_leaf_regs: Leaf Functions. (line 50)
+* CTZ_DEFINED_VALUE_AT_ZERO: Misc. (line 306)
+* ctzM2 instruction pattern: Standard Names. (line 767)
+* CUMULATIVE_ARGS: Register Arguments. (line 142)
+* current_function_is_leaf: Leaf Functions. (line 51)
+* current_function_uses_only_leaf_regs: Leaf Functions. (line 51)
* current_insn_predicate: Conditional Execution.
(line 27)
-* C_COMMON_OVERRIDE_OPTIONS: Run-time Target. (line 136)
-* c_register_pragma: Misc. (line 407)
-* c_register_pragma_with_expansion: Misc. (line 409)
-* DAmode: Machine Modes. (line 154)
+* DAmode: Machine Modes. (line 155)
* data bypass: Processor pipeline description.
- (line 105)
-* data bypass <1>: Processor pipeline description.
- (line 196)
+ (line 106)
* data dependence delays: Processor pipeline description.
(line 6)
* Data Dependency Analysis: Dependency analysis.
(line 6)
* data structures: Per-Function Data. (line 6)
-* DATA_ABI_ALIGNMENT: Storage Layout. (line 233)
-* DATA_ALIGNMENT: Storage Layout. (line 220)
-* DATA_SECTION_ASM_OP: Sections. (line 52)
-* DBR_OUTPUT_SEQEND: Instruction Output. (line 133)
-* dbr_sequence_length: Instruction Output. (line 133)
-* DBX_BLOCKS_FUNCTION_RELATIVE: DBX Options. (line 100)
-* DBX_CONTIN_CHAR: DBX Options. (line 63)
-* DBX_CONTIN_LENGTH: DBX Options. (line 53)
-* DBX_DEBUGGING_INFO: DBX Options. (line 8)
-* DBX_FUNCTION_FIRST: DBX Options. (line 94)
-* DBX_LINES_FUNCTION_RELATIVE: DBX Options. (line 106)
-* DBX_NO_XREFS: DBX Options. (line 47)
-* DBX_OUTPUT_MAIN_SOURCE_FILENAME: File Names and DBX. (line 8)
-* DBX_OUTPUT_MAIN_SOURCE_FILE_END: File Names and DBX. (line 33)
+* DATA_ABI_ALIGNMENT: Storage Layout. (line 237)
+* DATA_ALIGNMENT: Storage Layout. (line 224)
+* DATA_SECTION_ASM_OP: Sections. (line 53)
+* DBR_OUTPUT_SEQEND: Instruction Output. (line 135)
+* dbr_sequence_length: Instruction Output. (line 134)
+* DBX_BLOCKS_FUNCTION_RELATIVE: DBX Options. (line 103)
+* DBX_CONTIN_CHAR: DBX Options. (line 66)
+* DBX_CONTIN_LENGTH: DBX Options. (line 56)
+* DBX_DEBUGGING_INFO: DBX Options. (line 9)
+* DBX_FUNCTION_FIRST: DBX Options. (line 97)
+* DBX_LINES_FUNCTION_RELATIVE: DBX Options. (line 109)
+* DBX_NO_XREFS: DBX Options. (line 50)
+* DBX_OUTPUT_MAIN_SOURCE_FILE_END: File Names and DBX. (line 34)
+* DBX_OUTPUT_MAIN_SOURCE_FILENAME: File Names and DBX. (line 9)
* DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END: File Names and DBX.
- (line 41)
-* DBX_OUTPUT_SOURCE_LINE: DBX Hooks. (line 8)
-* DBX_REGISTER_NUMBER: All Debuggers. (line 8)
-* DBX_REGPARM_STABS_CODE: DBX Options. (line 84)
-* DBX_REGPARM_STABS_LETTER: DBX Options. (line 89)
-* DBX_STATIC_CONST_VAR_CODE: DBX Options. (line 79)
-* DBX_STATIC_STAB_DATA_SECTION: DBX Options. (line 70)
-* DBX_TYPE_DECL_STABS_CODE: DBX Options. (line 75)
-* DBX_USE_BINCL: DBX Options. (line 112)
-* DCmode: Machine Modes. (line 199)
+ (line 42)
+* DBX_OUTPUT_SOURCE_LINE: DBX Hooks. (line 9)
+* DBX_REGISTER_NUMBER: All Debuggers. (line 9)
+* DBX_REGPARM_STABS_CODE: DBX Options. (line 87)
+* DBX_REGPARM_STABS_LETTER: DBX Options. (line 92)
+* DBX_STATIC_CONST_VAR_CODE: DBX Options. (line 82)
+* DBX_STATIC_STAB_DATA_SECTION: DBX Options. (line 73)
+* DBX_TYPE_DECL_STABS_CODE: DBX Options. (line 78)
+* DBX_USE_BINCL: DBX Options. (line 115)
+* DCmode: Machine Modes. (line 200)
* DDmode: Machine Modes. (line 93)
* De Morgan's law: Insn Canonicalizations.
- (line 51)
+ (line 52)
* dead_or_set_p: define_peephole. (line 65)
-* DEBUGGER_ARG_OFFSET: All Debuggers. (line 36)
-* DEBUGGER_AUTO_OFFSET: All Debuggers. (line 27)
* debug_expr: Debug Information. (line 22)
* DEBUG_EXPR_DECL: Declarations. (line 6)
-* debug_insn: Insns. (line 236)
-* DEBUG_SYMS_TEXT: DBX Options. (line 24)
+* debug_insn: Insns. (line 239)
+* DEBUG_SYMS_TEXT: DBX Options. (line 25)
+* DEBUGGER_ARG_OFFSET: All Debuggers. (line 37)
+* DEBUGGER_AUTO_OFFSET: All Debuggers. (line 28)
* decimal float library: Decimal float library routines.
(line 6)
-* declaration: Declarations. (line 6)
-* declarations, RTL: RTL Declarations. (line 6)
-* DECLARE_LIBRARY_RENAMES: Library Calls. (line 8)
* DECL_ALIGN: Declarations. (line 6)
* DECL_ANTICIPATED: Functions for C++. (line 42)
* DECL_ARGUMENTS: Function Basics. (line 36)
* DECL_ARRAY_DELETE_OPERATOR_P: Functions for C++. (line 158)
+* DECL_ARTIFICIAL <1>: Function Properties.
+ (line 47)
+* DECL_ARTIFICIAL <2>: Function Basics. (line 6)
* DECL_ARTIFICIAL: Working with declarations.
(line 24)
-* DECL_ARTIFICIAL <1>: Function Basics. (line 6)
-* DECL_ARTIFICIAL <2>: Function Properties.
- (line 47)
* DECL_ASSEMBLER_NAME: Function Basics. (line 6)
-* DECL_ASSEMBLER_NAME <1>: Function Basics. (line 19)
-* DECL_ATTRIBUTES: Attributes. (line 21)
+* DECL_ATTRIBUTES: Attributes. (line 22)
* DECL_BASE_CONSTRUCTOR_P: Functions for C++. (line 88)
* DECL_COMPLETE_CONSTRUCTOR_P: Functions for C++. (line 84)
* DECL_COMPLETE_DESTRUCTOR_P: Functions for C++. (line 98)
-* DECL_CONSTRUCTOR_P: Functions for C++. (line 77)
* DECL_CONST_MEMFUNC_P: Functions for C++. (line 71)
+* DECL_CONSTRUCTOR_P: Functions for C++. (line 77)
* DECL_CONTEXT: Namespaces. (line 31)
* DECL_CONV_FN_P: Functions for C++. (line 105)
* DECL_COPY_CONSTRUCTOR_P: Functions for C++. (line 92)
* DECL_DESTRUCTOR_P: Functions for C++. (line 95)
-* DECL_EXTERNAL: Declarations. (line 6)
+* DECL_EXTERN_C_FUNCTION_P: Functions for C++. (line 46)
* DECL_EXTERNAL <1>: Function Properties.
(line 25)
-* DECL_EXTERN_C_FUNCTION_P: Functions for C++. (line 46)
+* DECL_EXTERNAL: Declarations. (line 6)
* DECL_FUNCTION_MEMBER_P: Functions for C++. (line 61)
-* DECL_FUNCTION_SPECIFIC_OPTIMIZATION: Function Basics. (line 6)
* DECL_FUNCTION_SPECIFIC_OPTIMIZATION <1>: Function Properties.
(line 61)
-* DECL_FUNCTION_SPECIFIC_TARGET: Function Basics. (line 6)
+* DECL_FUNCTION_SPECIFIC_OPTIMIZATION: Function Basics. (line 6)
* DECL_FUNCTION_SPECIFIC_TARGET <1>: Function Properties.
(line 55)
+* DECL_FUNCTION_SPECIFIC_TARGET: Function Basics. (line 6)
* DECL_GLOBAL_CTOR_P: Functions for C++. (line 108)
* DECL_GLOBAL_DTOR_P: Functions for C++. (line 112)
-* DECL_INITIAL: Declarations. (line 6)
* DECL_INITIAL <1>: Function Basics. (line 51)
+* DECL_INITIAL: Declarations. (line 6)
* DECL_LINKONCE_P: Functions for C++. (line 50)
* DECL_LOCAL_FUNCTION_P: Functions for C++. (line 38)
* DECL_MAIN_P: Functions for C++. (line 34)
+* DECL_NAME <1>: Namespaces. (line 20)
+* DECL_NAME <2>: Function Basics. (line 6)
* DECL_NAME: Working with declarations.
(line 7)
-* DECL_NAME <1>: Function Basics. (line 6)
-* DECL_NAME <2>: Function Basics. (line 9)
-* DECL_NAME <3>: Namespaces. (line 20)
* DECL_NAMESPACE_ALIAS: Namespaces. (line 35)
* DECL_NAMESPACE_STD_P: Namespaces. (line 45)
+* DECL_NON_THUNK_FUNCTION_P: Functions for C++. (line 138)
* DECL_NONCONVERTING_P: Functions for C++. (line 80)
* DECL_NONSTATIC_MEMBER_FUNCTION_P: Functions for C++. (line 68)
-* DECL_NON_THUNK_FUNCTION_P: Functions for C++. (line 138)
* DECL_OVERLOADED_OPERATOR_P: Functions for C++. (line 102)
* DECL_PURE_P: Function Properties.
(line 40)
@@ -47513,49 +47954,52 @@ Concept Index
* DECL_VIRTUAL_P: Function Properties.
(line 44)
* DECL_VOLATILE_MEMFUNC_P: Functions for C++. (line 74)
-* 'decrement_and_branch_until_zero' instruction pattern: Standard Names.
- (line 1309)
+* declaration: Declarations. (line 6)
+* declarations, RTL: RTL Declarations. (line 6)
+* DECLARE_LIBRARY_RENAMES: Library Calls. (line 9)
+* decrement_and_branch_until_zero instruction pattern: Standard Names.
+ (line 1316)
* default: GTY Options. (line 88)
* default_file_start: File Framework. (line 8)
-* DEFAULT_GDB_EXTENSIONS: DBX Options. (line 17)
-* DEFAULT_PCC_STRUCT_RETURN: Aggregate Return. (line 34)
-* DEFAULT_SIGNED_CHAR: Type Layout. (line 123)
-* define_address_constraint: Define Constraints. (line 99)
+* DEFAULT_GDB_EXTENSIONS: DBX Options. (line 18)
+* DEFAULT_PCC_STRUCT_RETURN: Aggregate Return. (line 35)
+* DEFAULT_SIGNED_CHAR: Type Layout. (line 124)
+* define_address_constraint: Define Constraints. (line 107)
* define_asm_attributes: Tagging Insns. (line 73)
* define_attr: Defining Attributes.
(line 6)
* define_automaton: Processor pipeline description.
(line 53)
* define_bypass: Processor pipeline description.
- (line 196)
+ (line 197)
+* define_c_enum: Constant Definitions.
+ (line 49)
* define_code_attr: Code Iterators. (line 6)
* define_code_iterator: Code Iterators. (line 6)
* define_cond_exec: Conditional Execution.
(line 13)
* define_constants: Constant Definitions.
(line 6)
-* define_constraint: Define Constraints. (line 45)
+* define_constraint: Define Constraints. (line 48)
* define_cpu_unit: Processor pipeline description.
(line 68)
-* define_c_enum: Constant Definitions.
- (line 49)
* define_delay: Delay Slots. (line 25)
* define_enum: Constant Definitions.
(line 118)
-* define_enum_attr: Defining Attributes.
- (line 83)
* define_enum_attr <1>: Constant Definitions.
(line 136)
+* define_enum_attr: Defining Attributes.
+ (line 83)
* define_expand: Expander Definitions.
(line 11)
* define_insn: Patterns. (line 6)
-* 'define_insn' example: Example. (line 6)
+* define_insn example: Example. (line 6)
* define_insn_and_split: Insn Splitting. (line 170)
* define_insn_reservation: Processor pipeline description.
- (line 105)
+ (line 106)
* define_int_attr: Int Iterators. (line 6)
* define_int_iterator: Int Iterators. (line 6)
-* define_memory_constraint: Define Constraints. (line 80)
+* define_memory_constraint: Define Constraints. (line 88)
* define_mode_attr: Substitutions. (line 6)
* define_mode_iterator: Defining Mode Iterators.
(line 6)
@@ -47565,23 +48009,21 @@ Concept Index
(line 6)
* define_query_cpu_unit: Processor pipeline description.
(line 90)
-* define_register_constraint: Define Constraints. (line 26)
+* define_register_constraint: Define Constraints. (line 28)
* define_reservation: Processor pipeline description.
- (line 185)
+ (line 186)
* define_special_predicate: Defining Predicates.
(line 6)
* define_split: Insn Splitting. (line 32)
-* define_subst: Define Subst. (line 6)
-* define_subst <1>: Define Subst Example.
+* define_subst <1>: Subst Iterators. (line 6)
+* define_subst <2>: Define Subst Output Template.
(line 6)
-* define_subst <2>: Define Subst Pattern Matching.
+* define_subst <3>: Define Subst Pattern Matching.
(line 6)
-* define_subst <3>: Define Subst Output Template.
+* define_subst <4>: Define Subst Example.
(line 6)
-* define_subst <4>: Define Subst. (line 14)
-* define_subst <5>: Subst Iterators. (line 6)
+* define_subst: Define Subst. (line 6)
* define_subst_attr: Subst Iterators. (line 6)
-* define_subst_attr <1>: Subst Iterators. (line 26)
* defining attributes and their values: Defining Attributes.
(line 6)
* defining constraints: Define Constraints. (line 6)
@@ -47594,93 +48036,89 @@ Concept Index
* defining RTL sequences for code generation: Expander Definitions.
(line 6)
* delay slots, defining: Delay Slots. (line 6)
-* deletable: GTY Options. (line 132)
+* deletable: GTY Options. (line 131)
* DELETE_IF_ORDINARY: Filesystem. (line 79)
* Dependent Patterns: Dependent Patterns. (line 6)
* desc: GTY Options. (line 88)
* destructors, output of: Initialization. (line 6)
* deterministic finite state automaton: Processor pipeline description.
(line 6)
-* deterministic finite state automaton <1>: Processor pipeline description.
- (line 304)
* DFmode: Machine Modes. (line 76)
-* digits in constraint: Simple Constraints. (line 128)
+* digits in constraint: Simple Constraints. (line 130)
* DImode: Machine Modes. (line 45)
-* directory options .md: Including Patterns. (line 47)
* DIR_SEPARATOR: Filesystem. (line 18)
* DIR_SEPARATOR_2: Filesystem. (line 19)
+* directory options .md: Including Patterns. (line 44)
* disabling certain registers: Register Basics. (line 73)
* dispatch table: Dispatch Tables. (line 8)
-* div: Arithmetic. (line 116)
-* 'div' and attributes: Expressions. (line 83)
-* division: Arithmetic. (line 116)
-* division <1>: Arithmetic. (line 130)
-* division <2>: Arithmetic. (line 136)
-* 'divM3' instruction pattern: Standard Names. (line 276)
-* 'divmodM4' instruction pattern: Standard Names. (line 519)
+* div: Arithmetic. (line 115)
+* div and attributes: Expressions. (line 85)
+* division: Arithmetic. (line 115)
+* divM3 instruction pattern: Standard Names. (line 279)
+* divmodM4 instruction pattern: Standard Names. (line 524)
+* DO_BODY: Statements for C++. (line 6)
+* DO_COND: Statements for C++. (line 6)
+* DO_STMT: Statements for C++. (line 6)
* dollar sign: Multi-Alternative. (line 56)
-* DOLLARS_IN_IDENTIFIERS: Misc. (line 452)
-* 'doloop_begin' instruction pattern: Standard Names. (line 1331)
-* 'doloop_end' instruction pattern: Standard Names. (line 1319)
+* DOLLARS_IN_IDENTIFIERS: Misc. (line 454)
+* doloop_begin instruction pattern: Standard Names. (line 1338)
+* doloop_end instruction pattern: Standard Names. (line 1326)
* DONE: Expander Definitions.
(line 77)
* DONT_USE_BUILTIN_SETJMP: Exception Region Output.
- (line 77)
-* DOUBLE_TYPE_SIZE: Type Layout. (line 52)
-* DO_BODY: Statements for C++. (line 6)
-* DO_COND: Statements for C++. (line 6)
-* DO_STMT: Statements for C++. (line 6)
+ (line 79)
+* DOUBLE_TYPE_SIZE: Type Layout. (line 53)
* DQmode: Machine Modes. (line 118)
* driver: Driver. (line 6)
-* DRIVER_SELF_SPECS: Driver. (line 8)
+* DRIVER_SELF_SPECS: Driver. (line 9)
* dump examples: Dump examples. (line 6)
* dump setup: Dump setup. (line 6)
* dump types: Dump types. (line 6)
* dump verbosity: Dump output verbosity.
(line 6)
-* DUMPFILE_FORMAT: Filesystem. (line 67)
-* dump_basic_block: Dump types. (line 29)
-* dump_generic_expr: Dump types. (line 31)
-* dump_gimple_stmt: Dump types. (line 33)
+* dump_basic_block: Dump types. (line 30)
+* dump_generic_expr: Dump types. (line 33)
+* dump_gimple_stmt: Dump types. (line 36)
* dump_printf: Dump types. (line 6)
-* DWARF2_ASM_LINE_DEBUG_INFO: SDB and DWARF. (line 49)
-* DWARF2_DEBUGGING_INFO: SDB and DWARF. (line 12)
-* DWARF2_FRAME_INFO: SDB and DWARF. (line 29)
-* DWARF2_FRAME_REG_OUT: Frame Registers. (line 151)
+* DUMPFILE_FORMAT: Filesystem. (line 67)
+* DWARF2_ASM_LINE_DEBUG_INFO: SDB and DWARF. (line 50)
+* DWARF2_DEBUGGING_INFO: SDB and DWARF. (line 13)
+* DWARF2_FRAME_INFO: SDB and DWARF. (line 30)
+* DWARF2_FRAME_REG_OUT: Frame Registers. (line 150)
* DWARF2_UNWIND_INFO: Exception Region Output.
- (line 38)
-* DWARF_ALT_FRAME_RETURN_COLUMN: Frame Layout. (line 152)
+ (line 40)
+* DWARF_ALT_FRAME_RETURN_COLUMN: Frame Layout. (line 154)
* DWARF_CIE_DATA_ALIGNMENT: Exception Region Output.
- (line 89)
-* DWARF_FRAME_REGISTERS: Frame Registers. (line 109)
-* DWARF_FRAME_REGNUM: Frame Registers. (line 143)
+ (line 91)
+* DWARF_FRAME_REGISTERS: Frame Registers. (line 110)
+* DWARF_FRAME_REGNUM: Frame Registers. (line 142)
* DWARF_REG_TO_UNWIND_COLUMN: Frame Registers. (line 134)
-* DWARF_ZERO_REG: Frame Layout. (line 163)
-* DYNAMIC_CHAIN_ADDRESS: Frame Layout. (line 90)
-* 'E' in constraint: Simple Constraints. (line 87)
+* DWARF_ZERO_REG: Frame Layout. (line 165)
+* DYNAMIC_CHAIN_ADDRESS: Frame Layout. (line 92)
+* E in constraint: Simple Constraints. (line 89)
* earlyclobber operand: Modifiers. (line 25)
* edge: Edges. (line 6)
* edge in the flow graph: Edges. (line 6)
* edge iterators: Edges. (line 15)
* edge splitting: Maintaining the CFG.
- (line 105)
-* EDGE_ABNORMAL: Edges. (line 127)
-* EDGE_ABNORMAL, EDGE_ABNORMAL_CALL: Edges. (line 171)
-* EDGE_ABNORMAL, EDGE_EH: Edges. (line 95)
-* EDGE_ABNORMAL, EDGE_SIBCALL: Edges. (line 121)
-* EDGE_FALLTHRU, force_nonfallthru: Edges. (line 85)
-* 'EDOM', implicit usage: Library Calls. (line 59)
+ (line 107)
+* EDGE_ABNORMAL: Edges. (line 128)
+* EDGE_ABNORMAL, EDGE_ABNORMAL_CALL: Edges. (line 172)
+* EDGE_ABNORMAL, EDGE_EH: Edges. (line 96)
+* EDGE_ABNORMAL, EDGE_SIBCALL: Edges. (line 122)
+* EDGE_FALLTHRU, force_nonfallthru: Edges. (line 86)
+* EDOM, implicit usage: Library Calls. (line 59)
* EH_FRAME_IN_DATA_SECTION: Exception Region Output.
- (line 19)
+ (line 20)
* EH_FRAME_SECTION_NAME: Exception Region Output.
- (line 9)
-* 'eh_return' instruction pattern: Standard Names. (line 1512)
-* EH_RETURN_DATA_REGNO: Exception Handling. (line 6)
-* EH_RETURN_HANDLER_RTX: Exception Handling. (line 38)
-* EH_RETURN_STACKADJ_RTX: Exception Handling. (line 21)
+ (line 10)
+* eh_return instruction pattern: Standard Names. (line 1522)
+* EH_RETURN_DATA_REGNO: Exception Handling. (line 7)
+* EH_RETURN_HANDLER_RTX: Exception Handling. (line 39)
+* EH_RETURN_STACKADJ_RTX: Exception Handling. (line 22)
* EH_TABLES_CAN_BE_READ_ONLY: Exception Region Output.
- (line 28)
-* EH_USES: Function Entry. (line 155)
+ (line 29)
+* EH_USES: Function Entry. (line 158)
* ei_edge: Edges. (line 43)
* ei_end_p: Edges. (line 27)
* ei_last: Edges. (line 23)
@@ -47689,100 +48127,102 @@ Concept Index
* ei_prev: Edges. (line 39)
* ei_safe_safe: Edges. (line 47)
* ei_start: Edges. (line 19)
-* ELIMINABLE_REGS: Elimination. (line 46)
+* ELIMINABLE_REGS: Elimination. (line 47)
* ELSE_CLAUSE: Statements for C++. (line 6)
* Embedded C: Fixed-point fractional library routines.
(line 6)
* Empty Statements: Empty Statements. (line 6)
* EMPTY_CLASS_EXPR: Statements for C++. (line 6)
-* EMPTY_FIELD_BOUNDARY: Storage Layout. (line 311)
+* EMPTY_FIELD_BOUNDARY: Storage Layout. (line 315)
* Emulated TLS: Emulated TLS. (line 6)
* enabled: Disable Insn Alternatives.
(line 6)
-* ENDFILE_SPEC: Driver. (line 155)
-* endianness: Portability. (line 20)
+* ENDFILE_SPEC: Driver. (line 156)
+* endianness: Portability. (line 21)
* ENTRY_BLOCK_PTR, EXIT_BLOCK_PTR: Basic Blocks. (line 10)
-* enum reg_class: Register Classes. (line 70)
+* enum reg_class: Register Classes. (line 72)
* ENUMERAL_TYPE: Types. (line 6)
* enumerations: Constant Definitions.
(line 49)
* epilogue: Function Entry. (line 6)
-* 'epilogue' instruction pattern: Standard Names. (line 1550)
-* EPILOGUE_USES: Function Entry. (line 149)
+* epilogue instruction pattern: Standard Names. (line 1560)
+* EPILOGUE_USES: Function Entry. (line 152)
* eq: Comparisons. (line 52)
-* 'eq' and attributes: Expressions. (line 83)
-* equal: Comparisons. (line 52)
-* eq_attr: Expressions. (line 104)
+* eq and attributes: Expressions. (line 85)
+* eq_attr: Expressions. (line 106)
* EQ_EXPR: Unary and Binary Expressions.
(line 6)
-* 'errno', implicit usage: Library Calls. (line 71)
+* equal: Comparisons. (line 52)
+* errno, implicit usage: Library Calls. (line 71)
* EXACT_DIV_EXPR: Unary and Binary Expressions.
(line 6)
* examining SSA_NAMEs: SSA. (line 214)
-* exception handling: Edges. (line 95)
* exception handling <1>: Exception Handling. (line 6)
-* 'exception_receiver' instruction pattern: Standard Names. (line 1477)
+* exception handling: Edges. (line 96)
+* exception_receiver instruction pattern: Standard Names. (line 1486)
* exclamation point: Multi-Alternative. (line 47)
* exclusion_set: Processor pipeline description.
- (line 223)
-* exclusive-or, bitwise: Arithmetic. (line 168)
+ (line 224)
+* exclusive-or, bitwise: Arithmetic. (line 167)
* EXIT_EXPR: Unary and Binary Expressions.
(line 6)
-* EXIT_IGNORE_STACK: Function Entry. (line 137)
+* EXIT_IGNORE_STACK: Function Entry. (line 140)
* expander definitions: Expander Definitions.
(line 6)
-* 'expM2' instruction pattern: Standard Names. (line 622)
-* expression: Expression trees. (line 6)
-* expression codes: RTL Objects. (line 47)
+* expM2 instruction pattern: Standard Names. (line 627)
* EXPR_FILENAME: Working with declarations.
(line 14)
* EXPR_LINENO: Working with declarations.
(line 20)
-* expr_list: Insns. (line 540)
+* expr_list: Insns. (line 548)
* EXPR_STMT: Statements for C++. (line 6)
* EXPR_STMT_EXPR: Statements for C++. (line 6)
-* 'extendMN2' instruction pattern: Standard Names. (line 952)
-* extensible constraints: Simple Constraints. (line 171)
-* EXTRA_SPECS: Driver. (line 182)
-* 'extv' instruction pattern: Standard Names. (line 1043)
-* 'extvM' instruction pattern: Standard Names. (line 988)
-* 'extvmisalignM' instruction pattern: Standard Names. (line 998)
-* 'extzv' instruction pattern: Standard Names. (line 1061)
-* 'extzvM' instruction pattern: Standard Names. (line 1012)
-* 'extzvmisalignM' instruction pattern: Standard Names. (line 1015)
-* 'F' in constraint: Simple Constraints. (line 92)
+* expression: Expression trees. (line 6)
+* expression codes: RTL Objects. (line 47)
+* extendMN2 instruction pattern: Standard Names. (line 957)
+* extensible constraints: Simple Constraints. (line 173)
+* EXTRA_SPECS: Driver. (line 183)
+* extv instruction pattern: Standard Names. (line 1048)
+* extvM instruction pattern: Standard Names. (line 993)
+* extvmisalignM instruction pattern: Standard Names. (line 1003)
+* extzv instruction pattern: Standard Names. (line 1066)
+* extzvM instruction pattern: Standard Names. (line 1017)
+* extzvmisalignM instruction pattern: Standard Names. (line 1020)
+* F in constraint: Simple Constraints. (line 94)
* FAIL: Expander Definitions.
(line 83)
-* fall-thru: Edges. (line 68)
+* fall-thru: Edges. (line 69)
* FATAL_EXIT_CODE: Host Misc. (line 6)
* FDL, GNU Free Documentation License: GNU Free Documentation License.
(line 6)
* features, optional, in system conventions: Run-time Target.
(line 59)
* ffs: Arithmetic. (line 210)
-* 'ffsM2' instruction pattern: Standard Names. (line 736)
+* ffsM2 instruction pattern: Standard Names. (line 741)
* FIELD_DECL: Declarations. (line 6)
+* file_end_indicate_exec_stack: File Framework. (line 41)
* files and passes of the compiler: Passes. (line 6)
* files, generated: Files. (line 6)
-* file_end_indicate_exec_stack: File Framework. (line 39)
* final_absence_set: Processor pipeline description.
- (line 223)
-* FINAL_PRESCAN_INSN: Instruction Output. (line 60)
+ (line 224)
+* FINAL_PRESCAN_INSN: Instruction Output. (line 61)
* final_presence_set: Processor pipeline description.
- (line 223)
-* final_sequence: Instruction Output. (line 144)
-* FIND_BASE_TERM: Addressing Modes. (line 117)
+ (line 224)
+* final_sequence: Instruction Output. (line 145)
+* FIND_BASE_TERM: Addressing Modes. (line 119)
+* FINI_ARRAY_SECTION_ASM_OP: Sections. (line 114)
+* FINI_SECTION_ASM_OP: Sections. (line 99)
* finite state automaton minimization: Processor pipeline description.
- (line 304)
-* FINI_ARRAY_SECTION_ASM_OP: Sections. (line 113)
-* FINI_SECTION_ASM_OP: Sections. (line 98)
-* FIRST_PARM_OFFSET: Frame Layout. (line 65)
-* 'FIRST_PARM_OFFSET' and virtual registers: Regs and Memory.
- (line 65)
-* FIRST_PSEUDO_REGISTER: Register Basics. (line 8)
-* FIRST_STACK_REG: Stack Registers. (line 26)
+ (line 305)
+* FIRST_PARM_OFFSET: Frame Layout. (line 67)
+* FIRST_PARM_OFFSET and virtual registers: Regs and Memory. (line 65)
+* FIRST_PSEUDO_REGISTER: Register Basics. (line 9)
+* FIRST_STACK_REG: Stack Registers. (line 27)
* FIRST_VIRTUAL_REGISTER: Regs and Memory. (line 51)
* fix: Conversions. (line 66)
+* FIX_TRUNC_EXPR: Unary and Binary Expressions.
+ (line 6)
+* fix_truncMN2 instruction pattern: Standard Names. (line 944)
* fixed register: Register Basics. (line 15)
* fixed-point fractional library: Fixed-point fractional library routines.
(line 6)
@@ -47791,100 +48231,97 @@ Concept Index
* FIXED_CST: Constant expressions.
(line 6)
* FIXED_POINT_TYPE: Types. (line 6)
-* FIXED_REGISTERS: Register Basics. (line 14)
+* FIXED_REGISTERS: Register Basics. (line 15)
* fixed_regs: Register Basics. (line 59)
-* 'fixMN2' instruction pattern: Standard Names. (line 919)
-* 'fixunsMN2' instruction pattern: Standard Names. (line 928)
-* 'fixuns_truncMN2' instruction pattern: Standard Names. (line 943)
-* 'fix_truncMN2' instruction pattern: Standard Names. (line 939)
-* FIX_TRUNC_EXPR: Unary and Binary Expressions.
- (line 6)
+* fixMN2 instruction pattern: Standard Names. (line 924)
+* fixuns_truncMN2 instruction pattern: Standard Names. (line 948)
+* fixunsMN2 instruction pattern: Standard Names. (line 933)
* flags in RTL expression: Flags. (line 6)
* float: Conversions. (line 58)
-* floating point and cross compilation: Floating Point. (line 6)
-* 'floatMN2' instruction pattern: Standard Names. (line 911)
-* 'floatunsMN2' instruction pattern: Standard Names. (line 915)
* FLOAT_EXPR: Unary and Binary Expressions.
(line 6)
* float_extend: Conversions. (line 33)
-* FLOAT_LIB_COMPARE_RETURNS_BOOL: Library Calls. (line 32)
-* FLOAT_STORE_FLAG_VALUE: Misc. (line 286)
+* FLOAT_LIB_COMPARE_RETURNS_BOOL: Library Calls. (line 33)
+* FLOAT_STORE_FLAG_VALUE: Misc. (line 287)
* float_truncate: Conversions. (line 53)
-* FLOAT_TYPE_SIZE: Type Layout. (line 48)
-* FLOAT_WORDS_BIG_ENDIAN: Storage Layout. (line 41)
-* 'FLOAT_WORDS_BIG_ENDIAN', (lack of) effect on 'subreg': Regs and Memory.
- (line 224)
-* 'floorM2' instruction pattern: Standard Names. (line 657)
+* FLOAT_TYPE_SIZE: Type Layout. (line 49)
+* FLOAT_WORDS_BIG_ENDIAN: Storage Layout. (line 42)
+* FLOAT_WORDS_BIG_ENDIAN, (lack of) effect on subreg: Regs and Memory.
+ (line 226)
+* floating point and cross compilation: Floating Point. (line 6)
+* floatMN2 instruction pattern: Standard Names. (line 916)
+* floatunsMN2 instruction pattern: Standard Names. (line 920)
* FLOOR_DIV_EXPR: Unary and Binary Expressions.
(line 6)
* FLOOR_MOD_EXPR: Unary and Binary Expressions.
(line 6)
+* floorM2 instruction pattern: Standard Names. (line 662)
* flow-insensitive alias analysis: Alias analysis. (line 6)
* flow-sensitive alias analysis: Alias analysis. (line 6)
-* fma: Arithmetic. (line 112)
-* 'fmaM4' instruction pattern: Standard Names. (line 286)
-* 'fmodM3' instruction pattern: Standard Names. (line 575)
-* 'fmsM4' instruction pattern: Standard Names. (line 293)
-* 'fnmaM4' instruction pattern: Standard Names. (line 299)
-* 'fnmsM4' instruction pattern: Standard Names. (line 305)
-* FORCE_CODE_SECTION_ALIGN: Sections. (line 144)
-* force_reg: Standard Names. (line 36)
+* fma: Arithmetic. (line 111)
+* fmaM4 instruction pattern: Standard Names. (line 289)
+* fmodM3 instruction pattern: Standard Names. (line 580)
+* fmsM4 instruction pattern: Standard Names. (line 296)
+* fnmaM4 instruction pattern: Standard Names. (line 302)
+* fnmsM4 instruction pattern: Standard Names. (line 308)
* FOR_BODY: Statements for C++. (line 6)
* FOR_COND: Statements for C++. (line 6)
* FOR_EXPR: Statements for C++. (line 6)
* FOR_INIT_STMT: Statements for C++. (line 6)
* FOR_STMT: Statements for C++. (line 6)
* for_user: GTY Options. (line 82)
+* FORCE_CODE_SECTION_ALIGN: Sections. (line 145)
+* force_reg: Standard Names. (line 36)
+* fract_convert: Conversions. (line 82)
+* FRACT_TYPE_SIZE: Type Layout. (line 68)
* fractional types: Fixed-point fractional library routines.
(line 6)
-* 'fractMN2' instruction pattern: Standard Names. (line 961)
-* 'fractunsMN2' instruction pattern: Standard Names. (line 976)
-* fract_convert: Conversions. (line 82)
-* FRACT_TYPE_SIZE: Type Layout. (line 67)
+* fractMN2 instruction pattern: Standard Names. (line 966)
+* fractunsMN2 instruction pattern: Standard Names. (line 981)
* frame layout: Frame Layout. (line 6)
-* FRAME_ADDR_RTX: Frame Layout. (line 114)
-* FRAME_GROWS_DOWNWARD: Frame Layout. (line 30)
-* 'FRAME_GROWS_DOWNWARD' and virtual registers: Regs and Memory.
+* FRAME_ADDR_RTX: Frame Layout. (line 116)
+* FRAME_GROWS_DOWNWARD: Frame Layout. (line 31)
+* FRAME_GROWS_DOWNWARD and virtual registers: Regs and Memory.
(line 69)
-* FRAME_POINTER_CFA_OFFSET: Frame Layout. (line 212)
+* FRAME_POINTER_CFA_OFFSET: Frame Layout. (line 214)
* frame_pointer_needed: Function Entry. (line 34)
-* FRAME_POINTER_REGNUM: Frame Registers. (line 13)
-* 'FRAME_POINTER_REGNUM' and virtual registers: Regs and Memory.
+* FRAME_POINTER_REGNUM: Frame Registers. (line 14)
+* FRAME_POINTER_REGNUM and virtual registers: Regs and Memory.
(line 74)
* frame_pointer_rtx: Frame Registers. (line 104)
* frame_related: Flags. (line 229)
-* 'frame_related', in 'insn', 'call_insn', 'jump_insn', 'barrier', and 'set': Flags.
+* frame_related, in insn, call_insn, jump_insn, barrier, and set: Flags.
(line 107)
-* 'frame_related', in 'mem': Flags. (line 85)
-* 'frame_related', in 'reg': Flags. (line 94)
-* 'frame_related', in 'symbol_ref': Flags. (line 165)
+* frame_related, in mem: Flags. (line 85)
+* frame_related, in reg: Flags. (line 94)
+* frame_related, in symbol_ref: Flags. (line 165)
* frequency, count, BB_FREQ_BASE: Profile information.
(line 30)
-* 'ftruncM2' instruction pattern: Standard Names. (line 934)
-* function: Functions. (line 6)
+* ftruncM2 instruction pattern: Standard Names. (line 939)
* function <1>: Functions for C++. (line 6)
+* function: Functions. (line 6)
* function call conventions: Interface. (line 6)
* function entry and exit: Function Entry. (line 6)
* function entry point, alternate function entry point: Edges.
- (line 180)
+ (line 181)
* function properties: Function Properties.
(line 6)
* function-call insns: Calls. (line 6)
-* functions, leaf: Leaf Functions. (line 6)
-* FUNCTION_ARG_OFFSET: Register Arguments. (line 210)
-* FUNCTION_ARG_PADDING: Register Arguments. (line 217)
-* FUNCTION_ARG_REGNO_P: Register Arguments. (line 265)
-* FUNCTION_BOUNDARY: Storage Layout. (line 159)
-* FUNCTION_DECL: Functions. (line 6)
+* FUNCTION_ARG_OFFSET: Register Arguments. (line 212)
+* FUNCTION_ARG_PADDING: Register Arguments. (line 219)
+* FUNCTION_ARG_REGNO_P: Register Arguments. (line 267)
+* FUNCTION_BOUNDARY: Storage Layout. (line 161)
* FUNCTION_DECL <1>: Functions for C++. (line 6)
-* FUNCTION_MODE: Misc. (line 341)
-* FUNCTION_PROFILER: Profiling. (line 8)
+* FUNCTION_DECL: Functions. (line 6)
+* FUNCTION_MODE: Misc. (line 342)
+* FUNCTION_PROFILER: Profiling. (line 9)
* FUNCTION_TYPE: Types. (line 6)
* FUNCTION_VALUE: Scalar Return. (line 52)
* FUNCTION_VALUE_REGNO_P: Scalar Return. (line 78)
+* functions, leaf: Leaf Functions. (line 6)
* fundamental type: Types. (line 6)
-* 'G' in constraint: Simple Constraints. (line 96)
-* 'g' in constraint: Simple Constraints. (line 118)
+* g in constraint: Simple Constraints. (line 120)
+* G in constraint: Simple Constraints. (line 98)
* garbage collector, invocation: Invoking the garbage collector.
(line 6)
* garbage collector, troubleshooting: Troubleshooting. (line 6)
@@ -47893,55 +48330,55 @@ Concept Index
* gcov_type: Profile information.
(line 41)
* ge: Comparisons. (line 72)
-* 'ge' and attributes: Expressions. (line 83)
+* ge and attributes: Expressions. (line 85)
+* GE_EXPR: Unary and Binary Expressions.
+ (line 6)
+* GEN_ERRNO_RTX: Library Calls. (line 72)
* gencodes: RTL passes. (line 18)
* general_operand: Machine-Independent Predicates.
- (line 104)
-* GENERAL_REGS: Register Classes. (line 22)
+ (line 105)
+* GENERAL_REGS: Register Classes. (line 23)
* generated files: Files. (line 6)
* generating assembler output: Output Statement. (line 6)
* generating insns: RTL Template. (line 6)
-* GENERIC: Parsing pass. (line 6)
* GENERIC <1>: GENERIC. (line 6)
+* GENERIC: Parsing pass. (line 6)
* generic predicates: Machine-Independent Predicates.
(line 6)
* genflags: RTL passes. (line 18)
-* GEN_ERRNO_RTX: Library Calls. (line 71)
-* get_attr: Expressions. (line 99)
+* get_attr: Expressions. (line 101)
* get_attr_length: Insn Lengths. (line 52)
-* GET_CLASS_NARROWEST_MODE: Machine Modes. (line 344)
+* GET_CLASS_NARROWEST_MODE: Machine Modes. (line 345)
* GET_CODE: RTL Objects. (line 47)
* get_frame_size: Elimination. (line 34)
* get_insns: Insns. (line 34)
* get_last_insn: Insns. (line 34)
-* GET_MODE: Machine Modes. (line 291)
-* GET_MODE_ALIGNMENT: Machine Modes. (line 331)
-* GET_MODE_BITSIZE: Machine Modes. (line 315)
-* GET_MODE_CLASS: Machine Modes. (line 305)
-* GET_MODE_FBIT: Machine Modes. (line 322)
-* GET_MODE_IBIT: Machine Modes. (line 318)
-* GET_MODE_MASK: Machine Modes. (line 326)
-* GET_MODE_NAME: Machine Modes. (line 302)
-* GET_MODE_NUNITS: Machine Modes. (line 340)
-* GET_MODE_SIZE: Machine Modes. (line 312)
-* GET_MODE_UNIT_SIZE: Machine Modes. (line 334)
-* GET_MODE_WIDER_MODE: Machine Modes. (line 308)
+* GET_MODE: Machine Modes. (line 292)
+* GET_MODE_ALIGNMENT: Machine Modes. (line 332)
+* GET_MODE_BITSIZE: Machine Modes. (line 316)
+* GET_MODE_CLASS: Machine Modes. (line 306)
+* GET_MODE_FBIT: Machine Modes. (line 323)
+* GET_MODE_IBIT: Machine Modes. (line 319)
+* GET_MODE_MASK: Machine Modes. (line 327)
+* GET_MODE_NAME: Machine Modes. (line 303)
+* GET_MODE_NUNITS: Machine Modes. (line 341)
+* GET_MODE_SIZE: Machine Modes. (line 313)
+* GET_MODE_UNIT_SIZE: Machine Modes. (line 335)
+* GET_MODE_WIDER_MODE: Machine Modes. (line 309)
* GET_RTX_CLASS: RTL Classes. (line 6)
* GET_RTX_FORMAT: RTL Classes. (line 131)
* GET_RTX_LENGTH: RTL Classes. (line 128)
-* 'get_thread_pointerMODE' instruction pattern: Standard Names.
- (line 1887)
+* get_thread_pointerMODE instruction pattern: Standard Names.
+ (line 1897)
* geu: Comparisons. (line 72)
-* 'geu' and attributes: Expressions. (line 83)
-* GE_EXPR: Unary and Binary Expressions.
- (line 6)
+* geu and attributes: Expressions. (line 85)
* GGC: Type Information. (line 6)
* ggc_collect: Invoking the garbage collector.
(line 6)
-* GIMPLE: Parsing pass. (line 13)
-* GIMPLE <1>: Gimplification pass.
+* GIMPLE <1>: GIMPLE. (line 6)
+* GIMPLE <2>: Gimplification pass.
(line 6)
-* GIMPLE <2>: GIMPLE. (line 6)
+* GIMPLE: Parsing pass. (line 14)
* GIMPLE API: GIMPLE API. (line 6)
* GIMPLE class hierarchy: Class hierarchy of GIMPLE statements.
(line 6)
@@ -47950,536 +48387,509 @@ Concept Index
* GIMPLE instruction set: GIMPLE instruction set.
(line 6)
* GIMPLE sequences: GIMPLE sequences. (line 6)
-* GIMPLE statement iterators: Basic Blocks. (line 78)
* GIMPLE statement iterators <1>: Maintaining the CFG.
- (line 33)
+ (line 34)
+* GIMPLE statement iterators: Basic Blocks. (line 78)
* gimple_addresses_taken: Manipulating GIMPLE statements.
- (line 89)
-* 'GIMPLE_ASM': 'GIMPLE_ASM'. (line 6)
-* gimple_asm_clobber_op: 'GIMPLE_ASM'. (line 39)
-* gimple_asm_input_op: 'GIMPLE_ASM'. (line 23)
-* gimple_asm_nclobbers: 'GIMPLE_ASM'. (line 20)
-* gimple_asm_ninputs: 'GIMPLE_ASM'. (line 14)
-* gimple_asm_noutputs: 'GIMPLE_ASM'. (line 17)
-* gimple_asm_output_op: 'GIMPLE_ASM'. (line 31)
-* gimple_asm_set_clobber_op: 'GIMPLE_ASM'. (line 43)
-* gimple_asm_set_input_op: 'GIMPLE_ASM'. (line 27)
-* gimple_asm_set_output_op: 'GIMPLE_ASM'. (line 35)
-* gimple_asm_set_volatile: 'GIMPLE_ASM'. (line 54)
-* gimple_asm_string: 'GIMPLE_ASM'. (line 47)
-* gimple_asm_volatile_p: 'GIMPLE_ASM'. (line 51)
-* 'GIMPLE_ASSIGN': 'GIMPLE_ASSIGN'. (line 6)
-* gimple_assign_cast_p: Logical Operators. (line 158)
-* gimple_assign_cast_p <1>: 'GIMPLE_ASSIGN'. (line 104)
-* gimple_assign_lhs: 'GIMPLE_ASSIGN'. (line 62)
-* gimple_assign_lhs_ptr: 'GIMPLE_ASSIGN'. (line 65)
-* gimple_assign_rhs1: 'GIMPLE_ASSIGN'. (line 68)
-* gimple_assign_rhs1_ptr: 'GIMPLE_ASSIGN'. (line 71)
-* gimple_assign_rhs2: 'GIMPLE_ASSIGN'. (line 75)
-* gimple_assign_rhs2_ptr: 'GIMPLE_ASSIGN'. (line 78)
-* gimple_assign_rhs3: 'GIMPLE_ASSIGN'. (line 82)
-* gimple_assign_rhs3_ptr: 'GIMPLE_ASSIGN'. (line 85)
-* gimple_assign_rhs_class: 'GIMPLE_ASSIGN'. (line 56)
-* gimple_assign_rhs_code: 'GIMPLE_ASSIGN'. (line 52)
-* gimple_assign_set_lhs: 'GIMPLE_ASSIGN'. (line 89)
-* gimple_assign_set_rhs1: 'GIMPLE_ASSIGN'. (line 92)
-* gimple_assign_set_rhs2: 'GIMPLE_ASSIGN'. (line 96)
-* gimple_assign_set_rhs3: 'GIMPLE_ASSIGN'. (line 100)
+ (line 90)
+* GIMPLE_ASM: GIMPLE_ASM. (line 6)
+* gimple_asm_clobber_op: GIMPLE_ASM. (line 41)
+* gimple_asm_input_op: GIMPLE_ASM. (line 25)
+* gimple_asm_nclobbers: GIMPLE_ASM. (line 21)
+* gimple_asm_ninputs: GIMPLE_ASM. (line 15)
+* gimple_asm_noutputs: GIMPLE_ASM. (line 18)
+* gimple_asm_output_op: GIMPLE_ASM. (line 33)
+* gimple_asm_set_clobber_op: GIMPLE_ASM. (line 45)
+* gimple_asm_set_input_op: GIMPLE_ASM. (line 29)
+* gimple_asm_set_output_op: GIMPLE_ASM. (line 37)
+* gimple_asm_set_volatile: GIMPLE_ASM. (line 56)
+* gimple_asm_string: GIMPLE_ASM. (line 48)
+* gimple_asm_volatile_p: GIMPLE_ASM. (line 52)
+* GIMPLE_ASSIGN: GIMPLE_ASSIGN. (line 6)
+* gimple_assign_cast_p <1>: GIMPLE_ASSIGN. (line 105)
+* gimple_assign_cast_p: Logical Operators. (line 160)
+* gimple_assign_lhs: GIMPLE_ASSIGN. (line 63)
+* gimple_assign_lhs_ptr: GIMPLE_ASSIGN. (line 66)
+* gimple_assign_rhs1: GIMPLE_ASSIGN. (line 69)
+* gimple_assign_rhs1_ptr: GIMPLE_ASSIGN. (line 72)
+* gimple_assign_rhs2: GIMPLE_ASSIGN. (line 76)
+* gimple_assign_rhs2_ptr: GIMPLE_ASSIGN. (line 79)
+* gimple_assign_rhs3: GIMPLE_ASSIGN. (line 83)
+* gimple_assign_rhs3_ptr: GIMPLE_ASSIGN. (line 86)
+* gimple_assign_rhs_class: GIMPLE_ASSIGN. (line 58)
+* gimple_assign_rhs_code: GIMPLE_ASSIGN. (line 53)
+* gimple_assign_set_lhs: GIMPLE_ASSIGN. (line 90)
+* gimple_assign_set_rhs1: GIMPLE_ASSIGN. (line 93)
+* gimple_assign_set_rhs2: GIMPLE_ASSIGN. (line 97)
+* gimple_assign_set_rhs3: GIMPLE_ASSIGN. (line 101)
* gimple_bb: Manipulating GIMPLE statements.
- (line 17)
-* 'GIMPLE_BIND': 'GIMPLE_BIND'. (line 6)
-* gimple_bind_add_seq: 'GIMPLE_BIND'. (line 34)
-* gimple_bind_add_stmt: 'GIMPLE_BIND'. (line 31)
-* gimple_bind_append_vars: 'GIMPLE_BIND'. (line 18)
-* gimple_bind_block: 'GIMPLE_BIND'. (line 39)
-* gimple_bind_body: 'GIMPLE_BIND'. (line 22)
-* gimple_bind_set_block: 'GIMPLE_BIND'. (line 44)
-* gimple_bind_set_body: 'GIMPLE_BIND'. (line 26)
-* gimple_bind_set_vars: 'GIMPLE_BIND'. (line 14)
-* gimple_bind_vars: 'GIMPLE_BIND'. (line 11)
+ (line 18)
+* GIMPLE_BIND: GIMPLE_BIND. (line 6)
+* gimple_bind_add_seq: GIMPLE_BIND. (line 36)
+* gimple_bind_add_stmt: GIMPLE_BIND. (line 32)
+* gimple_bind_append_vars: GIMPLE_BIND. (line 19)
+* gimple_bind_block: GIMPLE_BIND. (line 40)
+* gimple_bind_body: GIMPLE_BIND. (line 23)
+* gimple_bind_set_block: GIMPLE_BIND. (line 45)
+* gimple_bind_set_body: GIMPLE_BIND. (line 28)
+* gimple_bind_set_vars: GIMPLE_BIND. (line 15)
+* gimple_bind_vars: GIMPLE_BIND. (line 12)
* gimple_block: Manipulating GIMPLE statements.
- (line 20)
-* gimple_build: GIMPLE API. (line 34)
-* gimple_build <1>: GIMPLE API. (line 36)
-* gimple_build <2>: GIMPLE API. (line 38)
-* gimple_build <3>: GIMPLE API. (line 41)
-* gimple_build <4>: GIMPLE API. (line 44)
-* gimple_build_nop: 'GIMPLE_NOP'. (line 6)
-* gimple_build_omp_master: 'GIMPLE_OMP_MASTER'.
- (line 6)
-* gimple_build_omp_ordered: 'GIMPLE_OMP_ORDERED'.
- (line 6)
-* gimple_build_omp_return: 'GIMPLE_OMP_RETURN'.
- (line 6)
-* gimple_build_omp_section: 'GIMPLE_OMP_SECTION'.
- (line 6)
-* gimple_build_omp_sections_switch: 'GIMPLE_OMP_SECTIONS'.
- (line 13)
-* gimple_build_wce: 'GIMPLE_WITH_CLEANUP_EXPR'.
- (line 6)
-* 'GIMPLE_CALL': 'GIMPLE_CALL'. (line 6)
-* gimple_call_arg: 'GIMPLE_CALL'. (line 65)
-* gimple_call_arg_ptr: 'GIMPLE_CALL'. (line 69)
-* gimple_call_chain: 'GIMPLE_CALL'. (line 56)
-* gimple_call_copy_skip_args: 'GIMPLE_CALL'. (line 90)
-* gimple_call_fn: 'GIMPLE_CALL'. (line 37)
-* gimple_call_fndecl: 'GIMPLE_CALL'. (line 45)
-* gimple_call_lhs: 'GIMPLE_CALL'. (line 28)
-* gimple_call_lhs_ptr: 'GIMPLE_CALL'. (line 31)
-* gimple_call_noreturn_p: 'GIMPLE_CALL'. (line 87)
-* gimple_call_num_args: 'GIMPLE_CALL'. (line 62)
-* gimple_call_return_type: 'GIMPLE_CALL'. (line 53)
-* gimple_call_set_arg: 'GIMPLE_CALL'. (line 74)
-* gimple_call_set_chain: 'GIMPLE_CALL'. (line 59)
-* gimple_call_set_fn: 'GIMPLE_CALL'. (line 41)
-* gimple_call_set_fndecl: 'GIMPLE_CALL'. (line 50)
-* gimple_call_set_lhs: 'GIMPLE_CALL'. (line 34)
-* gimple_call_set_tail: 'GIMPLE_CALL'. (line 79)
-* gimple_call_tail_p: 'GIMPLE_CALL'. (line 84)
-* 'GIMPLE_CATCH': 'GIMPLE_CATCH'. (line 6)
-* gimple_catch_handler: 'GIMPLE_CATCH'. (line 19)
-* gimple_catch_set_handler: 'GIMPLE_CATCH'. (line 26)
-* gimple_catch_set_types: 'GIMPLE_CATCH'. (line 23)
-* gimple_catch_types: 'GIMPLE_CATCH'. (line 12)
-* gimple_catch_types_ptr: 'GIMPLE_CATCH'. (line 15)
-* gimple_code: Manipulating GIMPLE statements.
+ (line 21)
+* gimple_build: GIMPLE API. (line 36)
+* gimple_build_nop: GIMPLE_NOP. (line 7)
+* gimple_build_omp_master: GIMPLE_OMP_MASTER. (line 7)
+* gimple_build_omp_ordered: GIMPLE_OMP_ORDERED. (line 7)
+* gimple_build_omp_return: GIMPLE_OMP_RETURN. (line 7)
+* gimple_build_omp_section: GIMPLE_OMP_SECTION. (line 7)
+* gimple_build_omp_sections_switch: GIMPLE_OMP_SECTIONS.
(line 14)
-* 'GIMPLE_COND': 'GIMPLE_COND'. (line 6)
-* gimple_cond_code: 'GIMPLE_COND'. (line 20)
-* gimple_cond_false_label: 'GIMPLE_COND'. (line 59)
-* gimple_cond_lhs: 'GIMPLE_COND'. (line 29)
-* gimple_cond_make_false: 'GIMPLE_COND'. (line 63)
-* gimple_cond_make_true: 'GIMPLE_COND'. (line 66)
-* gimple_cond_rhs: 'GIMPLE_COND'. (line 37)
-* gimple_cond_set_code: 'GIMPLE_COND'. (line 24)
-* gimple_cond_set_false_label: 'GIMPLE_COND'. (line 54)
-* gimple_cond_set_lhs: 'GIMPLE_COND'. (line 33)
-* gimple_cond_set_rhs: 'GIMPLE_COND'. (line 41)
-* gimple_cond_set_true_label: 'GIMPLE_COND'. (line 49)
-* gimple_cond_true_label: 'GIMPLE_COND'. (line 45)
-* gimple_convert: GIMPLE API. (line 47)
+* gimple_build_wce: GIMPLE_WITH_CLEANUP_EXPR.
+ (line 7)
+* GIMPLE_CALL: GIMPLE_CALL. (line 6)
+* gimple_call_arg: GIMPLE_CALL. (line 66)
+* gimple_call_arg_ptr: GIMPLE_CALL. (line 71)
+* gimple_call_chain: GIMPLE_CALL. (line 57)
+* gimple_call_copy_skip_args: GIMPLE_CALL. (line 92)
+* gimple_call_fn: GIMPLE_CALL. (line 38)
+* gimple_call_fndecl: GIMPLE_CALL. (line 46)
+* gimple_call_lhs: GIMPLE_CALL. (line 29)
+* gimple_call_lhs_ptr: GIMPLE_CALL. (line 32)
+* gimple_call_noreturn_p: GIMPLE_CALL. (line 88)
+* gimple_call_num_args: GIMPLE_CALL. (line 63)
+* gimple_call_return_type: GIMPLE_CALL. (line 54)
+* gimple_call_set_arg: GIMPLE_CALL. (line 76)
+* gimple_call_set_chain: GIMPLE_CALL. (line 60)
+* gimple_call_set_fn: GIMPLE_CALL. (line 42)
+* gimple_call_set_fndecl: GIMPLE_CALL. (line 51)
+* gimple_call_set_lhs: GIMPLE_CALL. (line 35)
+* gimple_call_set_tail: GIMPLE_CALL. (line 80)
+* gimple_call_tail_p: GIMPLE_CALL. (line 85)
+* GIMPLE_CATCH: GIMPLE_CATCH. (line 6)
+* gimple_catch_handler: GIMPLE_CATCH. (line 20)
+* gimple_catch_set_handler: GIMPLE_CATCH. (line 28)
+* gimple_catch_set_types: GIMPLE_CATCH. (line 24)
+* gimple_catch_types: GIMPLE_CATCH. (line 13)
+* gimple_catch_types_ptr: GIMPLE_CATCH. (line 16)
+* gimple_code: Manipulating GIMPLE statements.
+ (line 15)
+* GIMPLE_COND: GIMPLE_COND. (line 6)
+* gimple_cond_code: GIMPLE_COND. (line 21)
+* gimple_cond_false_label: GIMPLE_COND. (line 60)
+* gimple_cond_lhs: GIMPLE_COND. (line 30)
+* gimple_cond_make_false: GIMPLE_COND. (line 64)
+* gimple_cond_make_true: GIMPLE_COND. (line 67)
+* gimple_cond_rhs: GIMPLE_COND. (line 38)
+* gimple_cond_set_code: GIMPLE_COND. (line 26)
+* gimple_cond_set_false_label: GIMPLE_COND. (line 56)
+* gimple_cond_set_lhs: GIMPLE_COND. (line 34)
+* gimple_cond_set_rhs: GIMPLE_COND. (line 42)
+* gimple_cond_set_true_label: GIMPLE_COND. (line 51)
+* gimple_cond_true_label: GIMPLE_COND. (line 46)
+* gimple_convert: GIMPLE API. (line 49)
* gimple_copy: Manipulating GIMPLE statements.
- (line 146)
-* 'GIMPLE_DEBUG': 'GIMPLE_DEBUG'. (line 6)
-* 'GIMPLE_DEBUG_BIND': 'GIMPLE_DEBUG'. (line 6)
-* gimple_debug_bind_get_value: 'GIMPLE_DEBUG'. (line 46)
-* gimple_debug_bind_get_value_ptr: 'GIMPLE_DEBUG'. (line 50)
-* gimple_debug_bind_get_var: 'GIMPLE_DEBUG'. (line 43)
-* gimple_debug_bind_has_value_p: 'GIMPLE_DEBUG'. (line 68)
-* gimple_debug_bind_p: Logical Operators. (line 162)
-* gimple_debug_bind_reset_value: 'GIMPLE_DEBUG'. (line 64)
-* gimple_debug_bind_set_value: 'GIMPLE_DEBUG'. (line 59)
-* gimple_debug_bind_set_var: 'GIMPLE_DEBUG'. (line 55)
+ (line 147)
+* GIMPLE_DEBUG: GIMPLE_DEBUG. (line 6)
+* GIMPLE_DEBUG_BIND: GIMPLE_DEBUG. (line 6)
+* gimple_debug_bind_get_value: GIMPLE_DEBUG. (line 48)
+* gimple_debug_bind_get_value_ptr: GIMPLE_DEBUG. (line 53)
+* gimple_debug_bind_get_var: GIMPLE_DEBUG. (line 45)
+* gimple_debug_bind_has_value_p: GIMPLE_DEBUG. (line 70)
+* gimple_debug_bind_p: Logical Operators. (line 164)
+* gimple_debug_bind_reset_value: GIMPLE_DEBUG. (line 66)
+* gimple_debug_bind_set_value: GIMPLE_DEBUG. (line 62)
+* gimple_debug_bind_set_var: GIMPLE_DEBUG. (line 58)
* gimple_def_ops: Manipulating GIMPLE statements.
- (line 93)
-* 'GIMPLE_EH_FILTER': 'GIMPLE_EH_FILTER'. (line 6)
-* gimple_eh_filter_failure: 'GIMPLE_EH_FILTER'. (line 18)
-* gimple_eh_filter_set_failure: 'GIMPLE_EH_FILTER'. (line 27)
-* gimple_eh_filter_set_types: 'GIMPLE_EH_FILTER'. (line 22)
-* gimple_eh_filter_types: 'GIMPLE_EH_FILTER'. (line 11)
-* gimple_eh_filter_types_ptr: 'GIMPLE_EH_FILTER'. (line 14)
-* gimple_eh_must_not_throw_fndecl: 'GIMPLE_EH_FILTER'. (line 32)
-* gimple_eh_must_not_throw_set_fndecl: 'GIMPLE_EH_FILTER'. (line 36)
+ (line 94)
+* GIMPLE_EH_FILTER: GIMPLE_EH_FILTER. (line 6)
+* gimple_eh_filter_failure: GIMPLE_EH_FILTER. (line 19)
+* gimple_eh_filter_set_failure: GIMPLE_EH_FILTER. (line 29)
+* gimple_eh_filter_set_types: GIMPLE_EH_FILTER. (line 24)
+* gimple_eh_filter_types: GIMPLE_EH_FILTER. (line 12)
+* gimple_eh_filter_types_ptr: GIMPLE_EH_FILTER. (line 15)
+* gimple_eh_must_not_throw_fndecl: GIMPLE_EH_FILTER. (line 34)
+* gimple_eh_must_not_throw_set_fndecl: GIMPLE_EH_FILTER. (line 38)
* gimple_expr_code: Manipulating GIMPLE statements.
- (line 30)
+ (line 31)
* gimple_expr_type: Manipulating GIMPLE statements.
- (line 23)
-* 'GIMPLE_GOTO': 'GIMPLE_GOTO'. (line 6)
-* gimple_goto_dest: 'GIMPLE_GOTO'. (line 9)
-* gimple_goto_set_dest: 'GIMPLE_GOTO'. (line 12)
+ (line 24)
+* GIMPLE_GOTO: GIMPLE_GOTO. (line 6)
+* gimple_goto_dest: GIMPLE_GOTO. (line 10)
+* gimple_goto_set_dest: GIMPLE_GOTO. (line 13)
* gimple_has_mem_ops: Manipulating GIMPLE statements.
- (line 71)
+ (line 72)
* gimple_has_ops: Manipulating GIMPLE statements.
- (line 68)
+ (line 69)
* gimple_has_volatile_ops: Manipulating GIMPLE statements.
- (line 133)
-* 'GIMPLE_LABEL': 'GIMPLE_LABEL'. (line 6)
-* gimple_label_label: 'GIMPLE_LABEL'. (line 10)
-* gimple_label_set_label: 'GIMPLE_LABEL'. (line 13)
+ (line 134)
+* GIMPLE_LABEL: GIMPLE_LABEL. (line 6)
+* gimple_label_label: GIMPLE_LABEL. (line 11)
+* gimple_label_set_label: GIMPLE_LABEL. (line 14)
* gimple_loaded_syms: Manipulating GIMPLE statements.
- (line 121)
+ (line 122)
* gimple_locus: Manipulating GIMPLE statements.
- (line 41)
+ (line 42)
* gimple_locus_empty_p: Manipulating GIMPLE statements.
- (line 47)
+ (line 48)
* gimple_modified_p: Manipulating GIMPLE statements.
- (line 129)
-* 'GIMPLE_NOP': 'GIMPLE_NOP'. (line 6)
-* gimple_nop_p: 'GIMPLE_NOP'. (line 9)
+ (line 130)
* gimple_no_warning_p: Manipulating GIMPLE statements.
- (line 50)
-* gimple_num_ops: Logical Operators. (line 76)
+ (line 51)
+* GIMPLE_NOP: GIMPLE_NOP. (line 6)
+* gimple_nop_p: GIMPLE_NOP. (line 10)
* gimple_num_ops <1>: Manipulating GIMPLE statements.
- (line 74)
-* 'GIMPLE_OMP_ATOMIC_LOAD': 'GIMPLE_OMP_ATOMIC_LOAD'.
+ (line 75)
+* gimple_num_ops: Logical Operators. (line 78)
+* GIMPLE_OMP_ATOMIC_LOAD: GIMPLE_OMP_ATOMIC_LOAD.
(line 6)
-* gimple_omp_atomic_load_lhs: 'GIMPLE_OMP_ATOMIC_LOAD'.
- (line 16)
-* gimple_omp_atomic_load_rhs: 'GIMPLE_OMP_ATOMIC_LOAD'.
+* gimple_omp_atomic_load_lhs: GIMPLE_OMP_ATOMIC_LOAD.
+ (line 18)
+* gimple_omp_atomic_load_rhs: GIMPLE_OMP_ATOMIC_LOAD.
+ (line 26)
+* gimple_omp_atomic_load_set_lhs: GIMPLE_OMP_ATOMIC_LOAD.
+ (line 14)
+* gimple_omp_atomic_load_set_rhs: GIMPLE_OMP_ATOMIC_LOAD.
+ (line 22)
+* GIMPLE_OMP_ATOMIC_STORE: GIMPLE_OMP_ATOMIC_STORE.
+ (line 6)
+* gimple_omp_atomic_store_set_val: GIMPLE_OMP_ATOMIC_STORE.
+ (line 13)
+* gimple_omp_atomic_store_val: GIMPLE_OMP_ATOMIC_STORE.
+ (line 17)
+* gimple_omp_body: GIMPLE_OMP_PARALLEL.
(line 24)
-* gimple_omp_atomic_load_set_lhs: 'GIMPLE_OMP_ATOMIC_LOAD'.
- (line 12)
-* gimple_omp_atomic_load_set_rhs: 'GIMPLE_OMP_ATOMIC_LOAD'.
- (line 20)
-* 'GIMPLE_OMP_ATOMIC_STORE': 'GIMPLE_OMP_ATOMIC_STORE'.
+* GIMPLE_OMP_CONTINUE: GIMPLE_OMP_CONTINUE.
(line 6)
-* gimple_omp_atomic_store_set_val: 'GIMPLE_OMP_ATOMIC_STORE'.
- (line 11)
-* gimple_omp_atomic_store_val: 'GIMPLE_OMP_ATOMIC_STORE'.
- (line 15)
-* gimple_omp_body: 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_continue_control_def: GIMPLE_OMP_CONTINUE.
+ (line 14)
+* gimple_omp_continue_control_def_ptr: GIMPLE_OMP_CONTINUE.
+ (line 19)
+* gimple_omp_continue_control_use: GIMPLE_OMP_CONTINUE.
+ (line 28)
+* gimple_omp_continue_control_use_ptr: GIMPLE_OMP_CONTINUE.
+ (line 33)
+* gimple_omp_continue_set_control_def: GIMPLE_OMP_CONTINUE.
(line 23)
-* 'GIMPLE_OMP_CONTINUE': 'GIMPLE_OMP_CONTINUE'.
+* gimple_omp_continue_set_control_use: GIMPLE_OMP_CONTINUE.
+ (line 37)
+* GIMPLE_OMP_CRITICAL: GIMPLE_OMP_CRITICAL.
(line 6)
-* gimple_omp_continue_control_def: 'GIMPLE_OMP_CONTINUE'.
- (line 12)
-* gimple_omp_continue_control_def_ptr: 'GIMPLE_OMP_CONTINUE'.
- (line 17)
-* gimple_omp_continue_control_use: 'GIMPLE_OMP_CONTINUE'.
- (line 26)
-* gimple_omp_continue_control_use_ptr: 'GIMPLE_OMP_CONTINUE'.
+* gimple_omp_critical_name: GIMPLE_OMP_CRITICAL.
+ (line 14)
+* gimple_omp_critical_name_ptr: GIMPLE_OMP_CRITICAL.
+ (line 18)
+* gimple_omp_critical_set_name: GIMPLE_OMP_CRITICAL.
+ (line 23)
+* GIMPLE_OMP_FOR: GIMPLE_OMP_FOR. (line 6)
+* gimple_omp_for_clauses: GIMPLE_OMP_FOR. (line 18)
+* gimple_omp_for_clauses_ptr: GIMPLE_OMP_FOR. (line 21)
+* gimple_omp_for_cond: GIMPLE_OMP_FOR. (line 81)
+* gimple_omp_for_final: GIMPLE_OMP_FOR. (line 49)
+* gimple_omp_for_final_ptr: GIMPLE_OMP_FOR. (line 52)
+* gimple_omp_for_incr: GIMPLE_OMP_FOR. (line 59)
+* gimple_omp_for_incr_ptr: GIMPLE_OMP_FOR. (line 62)
+* gimple_omp_for_index: GIMPLE_OMP_FOR. (line 29)
+* gimple_omp_for_index_ptr: GIMPLE_OMP_FOR. (line 32)
+* gimple_omp_for_initial: GIMPLE_OMP_FOR. (line 39)
+* gimple_omp_for_initial_ptr: GIMPLE_OMP_FOR. (line 42)
+* gimple_omp_for_pre_body: GIMPLE_OMP_FOR. (line 68)
+* gimple_omp_for_set_clauses: GIMPLE_OMP_FOR. (line 25)
+* gimple_omp_for_set_cond: GIMPLE_OMP_FOR. (line 78)
+* gimple_omp_for_set_final: GIMPLE_OMP_FOR. (line 56)
+* gimple_omp_for_set_incr: GIMPLE_OMP_FOR. (line 65)
+* gimple_omp_for_set_index: GIMPLE_OMP_FOR. (line 36)
+* gimple_omp_for_set_initial: GIMPLE_OMP_FOR. (line 46)
+* gimple_omp_for_set_pre_body: GIMPLE_OMP_FOR. (line 73)
+* GIMPLE_OMP_MASTER: GIMPLE_OMP_MASTER. (line 6)
+* GIMPLE_OMP_ORDERED: GIMPLE_OMP_ORDERED. (line 6)
+* GIMPLE_OMP_PARALLEL: GIMPLE_OMP_PARALLEL.
+ (line 6)
+* gimple_omp_parallel_child_fn: GIMPLE_OMP_PARALLEL.
+ (line 44)
+* gimple_omp_parallel_child_fn_ptr: GIMPLE_OMP_PARALLEL.
+ (line 49)
+* gimple_omp_parallel_clauses: GIMPLE_OMP_PARALLEL.
(line 31)
-* gimple_omp_continue_set_control_def: 'GIMPLE_OMP_CONTINUE'.
- (line 21)
-* gimple_omp_continue_set_control_use: 'GIMPLE_OMP_CONTINUE'.
+* gimple_omp_parallel_clauses_ptr: GIMPLE_OMP_PARALLEL.
(line 35)
-* 'GIMPLE_OMP_CRITICAL': 'GIMPLE_OMP_CRITICAL'.
- (line 6)
-* gimple_omp_critical_name: 'GIMPLE_OMP_CRITICAL'.
- (line 12)
-* gimple_omp_critical_name_ptr: 'GIMPLE_OMP_CRITICAL'.
+* gimple_omp_parallel_combined_p: GIMPLE_OMP_PARALLEL.
(line 16)
-* gimple_omp_critical_set_name: 'GIMPLE_OMP_CRITICAL'.
- (line 21)
-* 'GIMPLE_OMP_FOR': 'GIMPLE_OMP_FOR'. (line 6)
-* gimple_omp_for_clauses: 'GIMPLE_OMP_FOR'. (line 17)
-* gimple_omp_for_clauses_ptr: 'GIMPLE_OMP_FOR'. (line 20)
-* gimple_omp_for_cond: 'GIMPLE_OMP_FOR'. (line 80)
-* gimple_omp_for_final: 'GIMPLE_OMP_FOR'. (line 48)
-* gimple_omp_for_final_ptr: 'GIMPLE_OMP_FOR'. (line 51)
-* gimple_omp_for_incr: 'GIMPLE_OMP_FOR'. (line 58)
-* gimple_omp_for_incr_ptr: 'GIMPLE_OMP_FOR'. (line 61)
-* gimple_omp_for_index: 'GIMPLE_OMP_FOR'. (line 28)
-* gimple_omp_for_index_ptr: 'GIMPLE_OMP_FOR'. (line 31)
-* gimple_omp_for_initial: 'GIMPLE_OMP_FOR'. (line 38)
-* gimple_omp_for_initial_ptr: 'GIMPLE_OMP_FOR'. (line 41)
-* gimple_omp_for_pre_body: 'GIMPLE_OMP_FOR'. (line 67)
-* gimple_omp_for_set_clauses: 'GIMPLE_OMP_FOR'. (line 23)
-* gimple_omp_for_set_cond: 'GIMPLE_OMP_FOR'. (line 76)
-* gimple_omp_for_set_final: 'GIMPLE_OMP_FOR'. (line 54)
-* gimple_omp_for_set_incr: 'GIMPLE_OMP_FOR'. (line 64)
-* gimple_omp_for_set_index: 'GIMPLE_OMP_FOR'. (line 34)
-* gimple_omp_for_set_initial: 'GIMPLE_OMP_FOR'. (line 44)
-* gimple_omp_for_set_pre_body: 'GIMPLE_OMP_FOR'. (line 71)
-* 'GIMPLE_OMP_MASTER': 'GIMPLE_OMP_MASTER'.
- (line 6)
-* 'GIMPLE_OMP_ORDERED': 'GIMPLE_OMP_ORDERED'.
- (line 6)
-* 'GIMPLE_OMP_PARALLEL': 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_parallel_data_arg: GIMPLE_OMP_PARALLEL.
+ (line 58)
+* gimple_omp_parallel_data_arg_ptr: GIMPLE_OMP_PARALLEL.
+ (line 63)
+* gimple_omp_parallel_set_child_fn: GIMPLE_OMP_PARALLEL.
+ (line 54)
+* gimple_omp_parallel_set_clauses: GIMPLE_OMP_PARALLEL.
+ (line 39)
+* gimple_omp_parallel_set_combined_p: GIMPLE_OMP_PARALLEL.
+ (line 20)
+* gimple_omp_parallel_set_data_arg: GIMPLE_OMP_PARALLEL.
+ (line 67)
+* GIMPLE_OMP_RETURN: GIMPLE_OMP_RETURN. (line 6)
+* gimple_omp_return_nowait_p: GIMPLE_OMP_RETURN. (line 14)
+* gimple_omp_return_set_nowait: GIMPLE_OMP_RETURN. (line 11)
+* GIMPLE_OMP_SECTION: GIMPLE_OMP_SECTION. (line 6)
+* gimple_omp_section_last_p: GIMPLE_OMP_SECTION. (line 12)
+* gimple_omp_section_set_last: GIMPLE_OMP_SECTION. (line 16)
+* GIMPLE_OMP_SECTIONS: GIMPLE_OMP_SECTIONS.
(line 6)
-* gimple_omp_parallel_child_fn: 'GIMPLE_OMP_PARALLEL'.
- (line 42)
-* gimple_omp_parallel_child_fn_ptr: 'GIMPLE_OMP_PARALLEL'.
- (line 47)
-* gimple_omp_parallel_clauses: 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_sections_clauses: GIMPLE_OMP_SECTIONS.
(line 30)
-* gimple_omp_parallel_clauses_ptr: 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_sections_clauses_ptr: GIMPLE_OMP_SECTIONS.
(line 33)
-* gimple_omp_parallel_combined_p: 'GIMPLE_OMP_PARALLEL'.
- (line 15)
-* gimple_omp_parallel_data_arg: 'GIMPLE_OMP_PARALLEL'.
- (line 56)
-* gimple_omp_parallel_data_arg_ptr: 'GIMPLE_OMP_PARALLEL'.
- (line 61)
-* gimple_omp_parallel_set_child_fn: 'GIMPLE_OMP_PARALLEL'.
- (line 52)
-* gimple_omp_parallel_set_clauses: 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_sections_control: GIMPLE_OMP_SECTIONS.
+ (line 17)
+* gimple_omp_sections_control_ptr: GIMPLE_OMP_SECTIONS.
+ (line 21)
+* gimple_omp_sections_set_clauses: GIMPLE_OMP_SECTIONS.
(line 37)
-* gimple_omp_parallel_set_combined_p: 'GIMPLE_OMP_PARALLEL'.
- (line 19)
-* gimple_omp_parallel_set_data_arg: 'GIMPLE_OMP_PARALLEL'.
- (line 65)
-* 'GIMPLE_OMP_RETURN': 'GIMPLE_OMP_RETURN'.
- (line 6)
-* gimple_omp_return_nowait_p: 'GIMPLE_OMP_RETURN'.
- (line 13)
-* gimple_omp_return_set_nowait: 'GIMPLE_OMP_RETURN'.
- (line 10)
-* 'GIMPLE_OMP_SECTION': 'GIMPLE_OMP_SECTION'.
- (line 6)
-* 'GIMPLE_OMP_SECTIONS': 'GIMPLE_OMP_SECTIONS'.
- (line 6)
-* gimple_omp_sections_clauses: 'GIMPLE_OMP_SECTIONS'.
- (line 29)
-* gimple_omp_sections_clauses_ptr: 'GIMPLE_OMP_SECTIONS'.
- (line 32)
-* gimple_omp_sections_control: 'GIMPLE_OMP_SECTIONS'.
- (line 16)
-* gimple_omp_sections_control_ptr: 'GIMPLE_OMP_SECTIONS'.
- (line 20)
-* gimple_omp_sections_set_clauses: 'GIMPLE_OMP_SECTIONS'.
- (line 35)
-* gimple_omp_sections_set_control: 'GIMPLE_OMP_SECTIONS'.
- (line 24)
-* gimple_omp_section_last_p: 'GIMPLE_OMP_SECTION'.
- (line 11)
-* gimple_omp_section_set_last: 'GIMPLE_OMP_SECTION'.
- (line 15)
-* gimple_omp_set_body: 'GIMPLE_OMP_PARALLEL'.
+* gimple_omp_sections_set_control: GIMPLE_OMP_SECTIONS.
(line 26)
-* 'GIMPLE_OMP_SINGLE': 'GIMPLE_OMP_SINGLE'.
- (line 6)
-* gimple_omp_single_clauses: 'GIMPLE_OMP_SINGLE'.
- (line 13)
-* gimple_omp_single_clauses_ptr: 'GIMPLE_OMP_SINGLE'.
- (line 16)
-* gimple_omp_single_set_clauses: 'GIMPLE_OMP_SINGLE'.
- (line 19)
-* gimple_op: Logical Operators. (line 79)
+* gimple_omp_set_body: GIMPLE_OMP_PARALLEL.
+ (line 28)
+* GIMPLE_OMP_SINGLE: GIMPLE_OMP_SINGLE. (line 6)
+* gimple_omp_single_clauses: GIMPLE_OMP_SINGLE. (line 14)
+* gimple_omp_single_clauses_ptr: GIMPLE_OMP_SINGLE. (line 17)
+* gimple_omp_single_set_clauses: GIMPLE_OMP_SINGLE. (line 21)
* gimple_op <1>: Manipulating GIMPLE statements.
- (line 80)
-* gimple_ops: Logical Operators. (line 82)
-* gimple_ops <1>: Manipulating GIMPLE statements.
- (line 77)
+ (line 81)
+* gimple_op: Logical Operators. (line 81)
* gimple_op_ptr: Manipulating GIMPLE statements.
- (line 83)
-* 'GIMPLE_PHI': 'GIMPLE_PHI'. (line 6)
-* gimple_phi_arg: 'GIMPLE_PHI'. (line 24)
-* gimple_phi_arg <1>: SSA. (line 62)
-* gimple_phi_arg_def: SSA. (line 68)
-* gimple_phi_arg_edge: SSA. (line 65)
-* gimple_phi_capacity: 'GIMPLE_PHI'. (line 6)
-* gimple_phi_num_args: 'GIMPLE_PHI'. (line 10)
-* gimple_phi_num_args <1>: SSA. (line 58)
-* gimple_phi_result: 'GIMPLE_PHI'. (line 15)
-* gimple_phi_result <1>: SSA. (line 55)
-* gimple_phi_result_ptr: 'GIMPLE_PHI'. (line 18)
-* gimple_phi_set_arg: 'GIMPLE_PHI'. (line 28)
-* gimple_phi_set_result: 'GIMPLE_PHI'. (line 21)
+ (line 84)
+* gimple_ops <1>: Manipulating GIMPLE statements.
+ (line 78)
+* gimple_ops: Logical Operators. (line 84)
+* GIMPLE_PHI: GIMPLE_PHI. (line 6)
+* gimple_phi_arg <1>: SSA. (line 63)
+* gimple_phi_arg: GIMPLE_PHI. (line 25)
+* gimple_phi_arg_def: SSA. (line 69)
+* gimple_phi_arg_edge: SSA. (line 66)
+* gimple_phi_capacity: GIMPLE_PHI. (line 7)
+* gimple_phi_num_args <1>: SSA. (line 59)
+* gimple_phi_num_args: GIMPLE_PHI. (line 11)
+* gimple_phi_result <1>: SSA. (line 56)
+* gimple_phi_result: GIMPLE_PHI. (line 16)
+* gimple_phi_result_ptr: GIMPLE_PHI. (line 19)
+* gimple_phi_set_arg: GIMPLE_PHI. (line 30)
+* gimple_phi_set_result: GIMPLE_PHI. (line 22)
* gimple_plf: Manipulating GIMPLE statements.
- (line 64)
-* 'GIMPLE_RESX': 'GIMPLE_RESX'. (line 6)
-* gimple_resx_region: 'GIMPLE_RESX'. (line 12)
-* gimple_resx_set_region: 'GIMPLE_RESX'. (line 15)
-* 'GIMPLE_RETURN': 'GIMPLE_RETURN'. (line 6)
-* gimple_return_retval: 'GIMPLE_RETURN'. (line 9)
-* gimple_return_set_retval: 'GIMPLE_RETURN'. (line 12)
-* gimple_seq_add_seq: GIMPLE sequences. (line 30)
-* gimple_seq_add_stmt: GIMPLE sequences. (line 24)
-* gimple_seq_alloc: GIMPLE sequences. (line 61)
-* gimple_seq_copy: GIMPLE sequences. (line 65)
-* gimple_seq_deep_copy: GIMPLE sequences. (line 36)
-* gimple_seq_empty_p: GIMPLE sequences. (line 69)
-* gimple_seq_first: GIMPLE sequences. (line 43)
-* gimple_seq_init: GIMPLE sequences. (line 58)
-* gimple_seq_last: GIMPLE sequences. (line 46)
-* gimple_seq_reverse: GIMPLE sequences. (line 39)
-* gimple_seq_set_first: GIMPLE sequences. (line 53)
-* gimple_seq_set_last: GIMPLE sequences. (line 49)
-* gimple_seq_singleton_p: GIMPLE sequences. (line 78)
+ (line 66)
+* GIMPLE_RESX: GIMPLE_RESX. (line 6)
+* gimple_resx_region: GIMPLE_RESX. (line 13)
+* gimple_resx_set_region: GIMPLE_RESX. (line 16)
+* GIMPLE_RETURN: GIMPLE_RETURN. (line 6)
+* gimple_return_retval: GIMPLE_RETURN. (line 10)
+* gimple_return_set_retval: GIMPLE_RETURN. (line 14)
+* gimple_seq_add_seq: GIMPLE sequences. (line 32)
+* gimple_seq_add_stmt: GIMPLE sequences. (line 26)
+* gimple_seq_alloc: GIMPLE sequences. (line 62)
+* gimple_seq_copy: GIMPLE sequences. (line 67)
+* gimple_seq_deep_copy: GIMPLE sequences. (line 37)
+* gimple_seq_empty_p: GIMPLE sequences. (line 70)
+* gimple_seq_first: GIMPLE sequences. (line 44)
+* gimple_seq_init: GIMPLE sequences. (line 59)
+* gimple_seq_last: GIMPLE sequences. (line 47)
+* gimple_seq_reverse: GIMPLE sequences. (line 40)
+* gimple_seq_set_first: GIMPLE sequences. (line 55)
+* gimple_seq_set_last: GIMPLE sequences. (line 51)
+* gimple_seq_singleton_p: GIMPLE sequences. (line 79)
* gimple_set_block: Manipulating GIMPLE statements.
- (line 38)
+ (line 39)
* gimple_set_def_ops: Manipulating GIMPLE statements.
- (line 96)
+ (line 98)
* gimple_set_has_volatile_ops: Manipulating GIMPLE statements.
- (line 136)
+ (line 138)
* gimple_set_locus: Manipulating GIMPLE statements.
- (line 44)
+ (line 45)
* gimple_set_op: Manipulating GIMPLE statements.
- (line 86)
+ (line 87)
* gimple_set_plf: Manipulating GIMPLE statements.
- (line 60)
+ (line 62)
* gimple_set_use_ops: Manipulating GIMPLE statements.
- (line 103)
+ (line 105)
* gimple_set_vdef_ops: Manipulating GIMPLE statements.
- (line 117)
+ (line 119)
* gimple_set_visited: Manipulating GIMPLE statements.
- (line 53)
+ (line 55)
* gimple_set_vuse_ops: Manipulating GIMPLE statements.
- (line 110)
-* gimple_simplify: GIMPLE API. (line 6)
-* gimple_simplify <1>: GIMPLE API. (line 8)
-* gimple_simplify <2>: GIMPLE API. (line 10)
-* gimple_simplify <3>: GIMPLE API. (line 12)
-* gimple_simplify <4>: GIMPLE API. (line 14)
-* gimple_simplify <5>: GIMPLE API. (line 16)
+ (line 112)
+* gimple_simplify: GIMPLE API. (line 8)
* gimple_statement_base: Tuple representation.
(line 14)
* gimple_statement_with_ops: Tuple representation.
(line 96)
* gimple_stored_syms: Manipulating GIMPLE statements.
- (line 125)
-* 'GIMPLE_SWITCH': 'GIMPLE_SWITCH'. (line 6)
-* gimple_switch_default_label: 'GIMPLE_SWITCH'. (line 41)
-* gimple_switch_index: 'GIMPLE_SWITCH'. (line 24)
-* gimple_switch_label: 'GIMPLE_SWITCH'. (line 31)
-* gimple_switch_num_labels: 'GIMPLE_SWITCH'. (line 14)
-* gimple_switch_set_default_label: 'GIMPLE_SWITCH'. (line 45)
-* gimple_switch_set_index: 'GIMPLE_SWITCH'. (line 27)
-* gimple_switch_set_label: 'GIMPLE_SWITCH'. (line 36)
-* gimple_switch_set_num_labels: 'GIMPLE_SWITCH'. (line 19)
-* 'GIMPLE_TRY': 'GIMPLE_TRY'. (line 6)
-* gimple_try_catch_is_cleanup: 'GIMPLE_TRY'. (line 19)
-* gimple_try_cleanup: 'GIMPLE_TRY'. (line 26)
-* gimple_try_eval: 'GIMPLE_TRY'. (line 22)
-* gimple_try_kind: 'GIMPLE_TRY'. (line 15)
-* gimple_try_set_catch_is_cleanup: 'GIMPLE_TRY'. (line 30)
-* gimple_try_set_cleanup: 'GIMPLE_TRY'. (line 38)
-* gimple_try_set_eval: 'GIMPLE_TRY'. (line 34)
+ (line 126)
+* GIMPLE_SWITCH: GIMPLE_SWITCH. (line 6)
+* gimple_switch_default_label: GIMPLE_SWITCH. (line 43)
+* gimple_switch_index: GIMPLE_SWITCH. (line 25)
+* gimple_switch_label: GIMPLE_SWITCH. (line 33)
+* gimple_switch_num_labels: GIMPLE_SWITCH. (line 16)
+* gimple_switch_set_default_label: GIMPLE_SWITCH. (line 47)
+* gimple_switch_set_index: GIMPLE_SWITCH. (line 29)
+* gimple_switch_set_label: GIMPLE_SWITCH. (line 38)
+* gimple_switch_set_num_labels: GIMPLE_SWITCH. (line 21)
+* GIMPLE_TRY: GIMPLE_TRY. (line 6)
+* gimple_try_catch_is_cleanup: GIMPLE_TRY. (line 20)
+* gimple_try_cleanup: GIMPLE_TRY. (line 27)
+* gimple_try_eval: GIMPLE_TRY. (line 23)
+* gimple_try_kind: GIMPLE_TRY. (line 16)
+* gimple_try_set_catch_is_cleanup: GIMPLE_TRY. (line 32)
+* gimple_try_set_cleanup: GIMPLE_TRY. (line 40)
+* gimple_try_set_eval: GIMPLE_TRY. (line 35)
* gimple_use_ops: Manipulating GIMPLE statements.
- (line 100)
+ (line 101)
* gimple_vdef_ops: Manipulating GIMPLE statements.
- (line 114)
+ (line 115)
* gimple_visited_p: Manipulating GIMPLE statements.
- (line 57)
+ (line 58)
* gimple_vuse_ops: Manipulating GIMPLE statements.
- (line 107)
-* gimple_wce_cleanup: 'GIMPLE_WITH_CLEANUP_EXPR'.
- (line 10)
-* gimple_wce_cleanup_eh_only: 'GIMPLE_WITH_CLEANUP_EXPR'.
- (line 17)
-* gimple_wce_set_cleanup: 'GIMPLE_WITH_CLEANUP_EXPR'.
- (line 13)
-* gimple_wce_set_cleanup_eh_only: 'GIMPLE_WITH_CLEANUP_EXPR'.
- (line 20)
-* 'GIMPLE_WITH_CLEANUP_EXPR': 'GIMPLE_WITH_CLEANUP_EXPR'.
+ (line 108)
+* gimple_wce_cleanup: GIMPLE_WITH_CLEANUP_EXPR.
+ (line 11)
+* gimple_wce_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR.
+ (line 18)
+* gimple_wce_set_cleanup: GIMPLE_WITH_CLEANUP_EXPR.
+ (line 15)
+* gimple_wce_set_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR.
+ (line 22)
+* GIMPLE_WITH_CLEANUP_EXPR: GIMPLE_WITH_CLEANUP_EXPR.
(line 6)
-* gimplification: Parsing pass. (line 13)
* gimplification <1>: Gimplification pass.
(line 6)
-* gimplifier: Parsing pass. (line 13)
-* gimplify_assign: 'GIMPLE_ASSIGN'. (line 41)
+* gimplification: Parsing pass. (line 14)
+* gimplifier: Parsing pass. (line 14)
+* gimplify_assign: GIMPLE_ASSIGN. (line 43)
* gimplify_expr: Gimplification pass.
(line 18)
* gimplify_function_tree: Gimplification pass.
(line 18)
* GLOBAL_INIT_PRIORITY: Functions for C++. (line 141)
* global_regs: Register Basics. (line 59)
-* 'GO_IF_LEGITIMATE_ADDRESS': Addressing Modes. (line 90)
+* GO_IF_LEGITIMATE_ADDRESS: Addressing Modes. (line 91)
* greater than: Comparisons. (line 60)
-* greater than <1>: Comparisons. (line 64)
-* greater than <2>: Comparisons. (line 72)
-* gsi_after_labels: Sequence iterators. (line 74)
-* gsi_bb: Sequence iterators. (line 82)
-* gsi_commit_edge_inserts: Sequence iterators. (line 193)
+* gsi_after_labels: Sequence iterators. (line 76)
+* gsi_bb: Sequence iterators. (line 83)
* gsi_commit_edge_inserts <1>: Maintaining the CFG.
- (line 105)
-* gsi_commit_one_edge_insert: Sequence iterators. (line 188)
-* gsi_end_p: Sequence iterators. (line 59)
+ (line 107)
+* gsi_commit_edge_inserts: Sequence iterators. (line 194)
+* gsi_commit_one_edge_insert: Sequence iterators. (line 190)
* gsi_end_p <1>: Maintaining the CFG.
- (line 48)
-* gsi_for_stmt: Sequence iterators. (line 156)
-* gsi_insert_after: Sequence iterators. (line 145)
+ (line 49)
+* gsi_end_p: Sequence iterators. (line 60)
+* gsi_for_stmt: Sequence iterators. (line 157)
* gsi_insert_after <1>: Maintaining the CFG.
- (line 60)
-* gsi_insert_before: Sequence iterators. (line 134)
+ (line 61)
+* gsi_insert_after: Sequence iterators. (line 147)
* gsi_insert_before <1>: Maintaining the CFG.
- (line 66)
-* gsi_insert_on_edge: Sequence iterators. (line 173)
+ (line 67)
+* gsi_insert_before: Sequence iterators. (line 136)
* gsi_insert_on_edge <1>: Maintaining the CFG.
- (line 105)
-* gsi_insert_on_edge_immediate: Sequence iterators. (line 183)
-* gsi_insert_seq_after: Sequence iterators. (line 152)
-* gsi_insert_seq_before: Sequence iterators. (line 141)
-* gsi_insert_seq_on_edge: Sequence iterators. (line 177)
-* gsi_last: Sequence iterators. (line 49)
+ (line 107)
+* gsi_insert_on_edge: Sequence iterators. (line 174)
+* gsi_insert_on_edge_immediate: Sequence iterators. (line 185)
+* gsi_insert_seq_after: Sequence iterators. (line 154)
+* gsi_insert_seq_before: Sequence iterators. (line 143)
+* gsi_insert_seq_on_edge: Sequence iterators. (line 179)
* gsi_last <1>: Maintaining the CFG.
- (line 44)
-* gsi_last_bb: Sequence iterators. (line 55)
-* gsi_link_after: Sequence iterators. (line 113)
-* gsi_link_before: Sequence iterators. (line 103)
-* gsi_link_seq_after: Sequence iterators. (line 108)
-* gsi_link_seq_before: Sequence iterators. (line 97)
-* gsi_move_after: Sequence iterators. (line 159)
-* gsi_move_before: Sequence iterators. (line 164)
-* gsi_move_to_bb_end: Sequence iterators. (line 169)
-* gsi_next: Sequence iterators. (line 65)
+ (line 45)
+* gsi_last: Sequence iterators. (line 50)
+* gsi_last_bb: Sequence iterators. (line 56)
+* gsi_link_after: Sequence iterators. (line 115)
+* gsi_link_before: Sequence iterators. (line 105)
+* gsi_link_seq_after: Sequence iterators. (line 110)
+* gsi_link_seq_before: Sequence iterators. (line 99)
+* gsi_move_after: Sequence iterators. (line 161)
+* gsi_move_before: Sequence iterators. (line 166)
+* gsi_move_to_bb_end: Sequence iterators. (line 171)
* gsi_next <1>: Maintaining the CFG.
- (line 52)
-* gsi_one_before_end_p: Sequence iterators. (line 62)
-* gsi_prev: Sequence iterators. (line 68)
+ (line 53)
+* gsi_next: Sequence iterators. (line 66)
+* gsi_one_before_end_p: Sequence iterators. (line 63)
* gsi_prev <1>: Maintaining the CFG.
- (line 56)
-* gsi_remove: Sequence iterators. (line 88)
+ (line 57)
+* gsi_prev: Sequence iterators. (line 69)
* gsi_remove <1>: Maintaining the CFG.
- (line 72)
-* gsi_replace: Sequence iterators. (line 128)
-* gsi_seq: Sequence iterators. (line 85)
-* gsi_split_seq_after: Sequence iterators. (line 118)
-* gsi_split_seq_before: Sequence iterators. (line 123)
-* gsi_start: Sequence iterators. (line 39)
+ (line 73)
+* gsi_remove: Sequence iterators. (line 90)
+* gsi_replace: Sequence iterators. (line 130)
+* gsi_seq: Sequence iterators. (line 86)
+* gsi_split_seq_after: Sequence iterators. (line 120)
+* gsi_split_seq_before: Sequence iterators. (line 125)
* gsi_start <1>: Maintaining the CFG.
- (line 40)
-* gsi_start_bb: Sequence iterators. (line 45)
-* gsi_stmt: Sequence iterators. (line 71)
-* gsi_stmt_ptr: Sequence iterators. (line 79)
+ (line 41)
+* gsi_start: Sequence iterators. (line 40)
+* gsi_start_bb: Sequence iterators. (line 46)
+* gsi_stmt: Sequence iterators. (line 72)
+* gsi_stmt_ptr: Sequence iterators. (line 80)
* gt: Comparisons. (line 60)
-* 'gt' and attributes: Expressions. (line 83)
-* gtu: Comparisons. (line 64)
-* 'gtu' and attributes: Expressions. (line 83)
-* GTY: Type Information. (line 6)
+* gt and attributes: Expressions. (line 85)
* GT_EXPR: Unary and Binary Expressions.
(line 6)
-* 'H' in constraint: Simple Constraints. (line 96)
-* HAmode: Machine Modes. (line 146)
+* gtu: Comparisons. (line 64)
+* gtu and attributes: Expressions. (line 85)
+* GTY: Type Information. (line 6)
+* H in constraint: Simple Constraints. (line 98)
+* HAmode: Machine Modes. (line 147)
+* HANDLE_PRAGMA_PACK_WITH_EXPANSION: Misc. (line 444)
* HANDLER: Statements for C++. (line 6)
* HANDLER_BODY: Statements for C++. (line 6)
* HANDLER_PARMS: Statements for C++. (line 6)
-* HANDLE_PRAGMA_PACK_WITH_EXPANSION: Misc. (line 442)
* hard registers: Regs and Memory. (line 9)
-* HARD_FRAME_POINTER_IS_ARG_POINTER: Frame Registers. (line 57)
-* HARD_FRAME_POINTER_IS_FRAME_POINTER: Frame Registers. (line 50)
-* HARD_FRAME_POINTER_REGNUM: Frame Registers. (line 19)
-* HARD_REGNO_CALLER_SAVE_MODE: Caller Saves. (line 10)
-* HARD_REGNO_CALL_PART_CLOBBERED: Register Basics. (line 52)
+* HARD_FRAME_POINTER_IS_ARG_POINTER: Frame Registers. (line 58)
+* HARD_FRAME_POINTER_IS_FRAME_POINTER: Frame Registers. (line 51)
+* HARD_FRAME_POINTER_REGNUM: Frame Registers. (line 20)
+* HARD_REGNO_CALL_PART_CLOBBERED: Register Basics. (line 53)
+* HARD_REGNO_CALLER_SAVE_MODE: Caller Saves. (line 11)
* HARD_REGNO_MODE_OK: Values in Registers.
- (line 57)
+ (line 58)
* HARD_REGNO_NREGS: Values in Registers.
- (line 10)
+ (line 11)
* HARD_REGNO_NREGS_HAS_PADDING: Values in Registers.
- (line 24)
+ (line 25)
* HARD_REGNO_NREGS_WITH_PADDING: Values in Registers.
- (line 42)
+ (line 43)
* HARD_REGNO_RENAME_OK: Values in Registers.
- (line 117)
+ (line 119)
* HAS_INIT_SECTION: Macros for Initialization.
- (line 18)
-* HAS_LONG_COND_BRANCH: Misc. (line 8)
-* HAS_LONG_UNCOND_BRANCH: Misc. (line 17)
+ (line 19)
+* HAS_LONG_COND_BRANCH: Misc. (line 9)
+* HAS_LONG_UNCOND_BRANCH: Misc. (line 18)
* HAVE_DOS_BASED_FILE_SYSTEM: Filesystem. (line 11)
-* HAVE_POST_DECREMENT: Addressing Modes. (line 11)
-* HAVE_POST_INCREMENT: Addressing Modes. (line 10)
-* HAVE_POST_MODIFY_DISP: Addressing Modes. (line 17)
-* HAVE_POST_MODIFY_REG: Addressing Modes. (line 23)
-* HAVE_PRE_DECREMENT: Addressing Modes. (line 9)
-* HAVE_PRE_INCREMENT: Addressing Modes. (line 8)
-* HAVE_PRE_MODIFY_DISP: Addressing Modes. (line 16)
-* HAVE_PRE_MODIFY_REG: Addressing Modes. (line 22)
-* HCmode: Machine Modes. (line 199)
+* HAVE_POST_DECREMENT: Addressing Modes. (line 12)
+* HAVE_POST_INCREMENT: Addressing Modes. (line 11)
+* HAVE_POST_MODIFY_DISP: Addressing Modes. (line 18)
+* HAVE_POST_MODIFY_REG: Addressing Modes. (line 24)
+* HAVE_PRE_DECREMENT: Addressing Modes. (line 10)
+* HAVE_PRE_INCREMENT: Addressing Modes. (line 9)
+* HAVE_PRE_MODIFY_DISP: Addressing Modes. (line 17)
+* HAVE_PRE_MODIFY_REG: Addressing Modes. (line 23)
+* HCmode: Machine Modes. (line 200)
* HFmode: Machine Modes. (line 61)
* high: Constants. (line 150)
* HImode: Machine Modes. (line 29)
-* 'HImode', in 'insn': Insns. (line 268)
-* HONOR_REG_ALLOC_ORDER: Allocation Order. (line 36)
+* HImode, in insn: Insns. (line 272)
+* HONOR_REG_ALLOC_ORDER: Allocation Order. (line 37)
* host configuration: Host Config. (line 6)
* host functions: Host Common. (line 6)
* host hooks: Host Common. (line 6)
* host makefile fragment: Host Fragment. (line 6)
* HOST_BIT_BUCKET: Filesystem. (line 51)
* HOST_EXECUTABLE_SUFFIX: Filesystem. (line 45)
-* HOST_HOOKS_EXTRA_SIGNALS: Host Common. (line 11)
-* HOST_HOOKS_GT_PCH_ALLOC_GRANULARITY: Host Common. (line 43)
-* HOST_HOOKS_GT_PCH_GET_ADDRESS: Host Common. (line 15)
-* HOST_HOOKS_GT_PCH_USE_ADDRESS: Host Common. (line 24)
+* HOST_HOOKS_EXTRA_SIGNALS: Host Common. (line 12)
+* HOST_HOOKS_GT_PCH_ALLOC_GRANULARITY: Host Common. (line 45)
+* HOST_HOOKS_GT_PCH_GET_ADDRESS: Host Common. (line 17)
+* HOST_HOOKS_GT_PCH_USE_ADDRESS: Host Common. (line 26)
* HOST_LACKS_INODE_NUMBERS: Filesystem. (line 89)
* HOST_LONG_FORMAT: Host Misc. (line 45)
* HOST_LONG_LONG_FORMAT: Host Misc. (line 41)
* HOST_OBJECT_SUFFIX: Filesystem. (line 40)
* HOST_PTR_PRINTF: Host Misc. (line 49)
-* HOT_TEXT_SECTION_NAME: Sections. (line 42)
+* HOT_TEXT_SECTION_NAME: Sections. (line 43)
* HQmode: Machine Modes. (line 110)
-* 'i' in constraint: Simple Constraints. (line 68)
-* 'I' in constraint: Simple Constraints. (line 79)
+* I in constraint: Simple Constraints. (line 81)
+* i in constraint: Simple Constraints. (line 70)
* identifier: Identifiers. (line 6)
* IDENTIFIER_LENGTH: Identifiers. (line 22)
* IDENTIFIER_NODE: Identifiers. (line 6)
@@ -48488,63 +48898,68 @@ Concept Index
* IDENTIFIER_TYPENAME_P: Identifiers. (line 33)
* IEEE 754-2008: Decimal float library routines.
(line 6)
-* IFCVT_MACHDEP_INIT: Misc. (line 567)
-* IFCVT_MODIFY_CANCEL: Misc. (line 561)
-* IFCVT_MODIFY_FINAL: Misc. (line 555)
-* IFCVT_MODIFY_INSN: Misc. (line 549)
-* IFCVT_MODIFY_MULTIPLE_TESTS: Misc. (line 541)
-* IFCVT_MODIFY_TESTS: Misc. (line 531)
* IF_COND: Statements for C++. (line 6)
* IF_STMT: Statements for C++. (line 6)
* if_then_else: Comparisons. (line 80)
-* 'if_then_else' and attributes: Expressions. (line 32)
-* 'if_then_else' usage: Side Effects. (line 56)
+* if_then_else and attributes: Expressions. (line 32)
+* if_then_else usage: Side Effects. (line 56)
+* IFCVT_MACHDEP_INIT: Misc. (line 568)
+* IFCVT_MODIFY_CANCEL: Misc. (line 562)
+* IFCVT_MODIFY_FINAL: Misc. (line 556)
+* IFCVT_MODIFY_INSN: Misc. (line 550)
+* IFCVT_MODIFY_MULTIPLE_TESTS: Misc. (line 543)
+* IFCVT_MODIFY_TESTS: Misc. (line 532)
* IMAGPART_EXPR: Unary and Binary Expressions.
(line 6)
-* Immediate Uses: SSA Operands. (line 258)
+* Immediate Uses: SSA Operands. (line 261)
* immediate_operand: Machine-Independent Predicates.
- (line 10)
-* IMMEDIATE_PREFIX: Instruction Output. (line 153)
+ (line 11)
+* IMMEDIATE_PREFIX: Instruction Output. (line 155)
+* in_struct: Flags. (line 245)
+* in_struct, in code_label and note: Flags. (line 59)
+* in_struct, in insn and jump_insn and call_insn: Flags. (line 49)
+* in_struct, in insn, call_insn, jump_insn and jump_table_data: Flags.
+ (line 148)
+* in_struct, in subreg: Flags. (line 187)
* include: Including Patterns. (line 6)
-* INCLUDE_DEFAULTS: Driver. (line 327)
-* inclusive-or, bitwise: Arithmetic. (line 163)
-* INCOMING_FRAME_SP_OFFSET: Frame Layout. (line 183)
-* INCOMING_REGNO: Register Basics. (line 86)
-* INCOMING_REG_PARM_STACK_SPACE: Stack Arguments. (line 73)
-* INCOMING_RETURN_ADDR_RTX: Frame Layout. (line 139)
-* INCOMING_STACK_BOUNDARY: Storage Layout. (line 154)
-* INDEX_REG_CLASS: Register Classes. (line 140)
-* 'indirect_jump' instruction pattern: Standard Names. (line 1268)
+* INCLUDE_DEFAULTS: Driver. (line 328)
+* inclusive-or, bitwise: Arithmetic. (line 162)
+* INCOMING_FRAME_SP_OFFSET: Frame Layout. (line 185)
+* INCOMING_REG_PARM_STACK_SPACE: Stack Arguments. (line 74)
+* INCOMING_REGNO: Register Basics. (line 87)
+* INCOMING_RETURN_ADDR_RTX: Frame Layout. (line 141)
+* INCOMING_STACK_BOUNDARY: Storage Layout. (line 156)
+* INDEX_REG_CLASS: Register Classes. (line 143)
+* indirect_jump instruction pattern: Standard Names. (line 1274)
* indirect_operand: Machine-Independent Predicates.
- (line 70)
+ (line 71)
* INDIRECT_REF: Storage References. (line 6)
-* initialization routines: Initialization. (line 6)
-* INITIAL_ELIMINATION_OFFSET: Elimination. (line 84)
-* INITIAL_FRAME_ADDRESS_RTX: Frame Layout. (line 81)
-* INITIAL_FRAME_POINTER_OFFSET: Elimination. (line 34)
-* INIT_ARRAY_SECTION_ASM_OP: Sections. (line 106)
-* INIT_CUMULATIVE_ARGS: Register Arguments. (line 161)
-* INIT_CUMULATIVE_INCOMING_ARGS: Register Arguments. (line 189)
-* INIT_CUMULATIVE_LIBCALL_ARGS: Register Arguments. (line 183)
-* INIT_ENVIRONMENT: Driver. (line 305)
-* INIT_EXPANDERS: Per-Function Data. (line 36)
+* INIT_ARRAY_SECTION_ASM_OP: Sections. (line 107)
+* INIT_CUMULATIVE_ARGS: Register Arguments. (line 164)
+* INIT_CUMULATIVE_INCOMING_ARGS: Register Arguments. (line 191)
+* INIT_CUMULATIVE_LIBCALL_ARGS: Register Arguments. (line 185)
+* INIT_ENVIRONMENT: Driver. (line 306)
+* INIT_EXPANDERS: Per-Function Data. (line 39)
* INIT_EXPR: Unary and Binary Expressions.
(line 6)
-* init_machine_status: Per-Function Data. (line 42)
+* init_machine_status: Per-Function Data. (line 45)
* init_one_libfunc: Library Calls. (line 15)
-* INIT_SECTION_ASM_OP: Sections. (line 90)
* INIT_SECTION_ASM_OP <1>: Macros for Initialization.
- (line 9)
+ (line 10)
+* INIT_SECTION_ASM_OP: Sections. (line 91)
+* INITIAL_ELIMINATION_OFFSET: Elimination. (line 85)
+* INITIAL_FRAME_ADDRESS_RTX: Frame Layout. (line 83)
+* INITIAL_FRAME_POINTER_OFFSET: Elimination. (line 35)
+* initialization routines: Initialization. (line 6)
* inlining: Target Attributes. (line 95)
* insert_insn_on_edge: Maintaining the CFG.
- (line 105)
+ (line 107)
* insn: Insns. (line 63)
-* 'insn' and '/f': Flags. (line 107)
-* 'insn' and '/j': Flags. (line 157)
-* 'insn' and '/s': Flags. (line 49)
-* 'insn' and '/s' <1>: Flags. (line 148)
-* 'insn' and '/u': Flags. (line 39)
-* 'insn' and '/v': Flags. (line 44)
+* insn and /f: Flags. (line 107)
+* insn and /j: Flags. (line 157)
+* insn and /s: Flags. (line 49)
+* insn and /u: Flags. (line 39)
+* insn and /v: Flags. (line 44)
* insn attributes: Insn Attributes. (line 6)
* insn canonicalization: Insn Canonicalizations.
(line 6)
@@ -48554,35 +48969,40 @@ Concept Index
* insn splitting: Insn Splitting. (line 6)
* insn-attr.h: Defining Attributes.
(line 34)
-* insns: Insns. (line 6)
-* insns, generating: RTL Template. (line 6)
-* insns, recognizing: RTL Template. (line 6)
* INSN_ANNULLED_BRANCH_P: Flags. (line 39)
-* INSN_CODE: Insns. (line 295)
+* INSN_CODE: Insns. (line 299)
* INSN_DELETED_P: Flags. (line 44)
* INSN_FROM_TARGET_P: Flags. (line 49)
-* insn_list: Insns. (line 540)
-* INSN_REFERENCES_ARE_DELAYED: Misc. (line 469)
-* INSN_SETS_ARE_DELAYED: Misc. (line 458)
+* insn_list: Insns. (line 548)
+* INSN_REFERENCES_ARE_DELAYED: Misc. (line 471)
+* INSN_SETS_ARE_DELAYED: Misc. (line 460)
* INSN_UID: Insns. (line 23)
-* INSN_VAR_LOCATION: Insns. (line 236)
+* INSN_VAR_LOCATION: Insns. (line 239)
+* insns: Insns. (line 6)
+* insns, generating: RTL Template. (line 6)
+* insns, recognizing: RTL Template. (line 6)
* instruction attributes: Insn Attributes. (line 6)
* instruction latency time: Processor pipeline description.
(line 6)
-* instruction latency time <1>: Processor pipeline description.
- (line 105)
-* instruction latency time <2>: Processor pipeline description.
- (line 196)
* instruction patterns: Patterns. (line 6)
* instruction splitting: Insn Splitting. (line 6)
-* 'insv' instruction pattern: Standard Names. (line 1067)
-* 'insvM' instruction pattern: Standard Names. (line 1019)
-* 'insvmisalignM' instruction pattern: Standard Names. (line 1029)
-* int iterators in '.md' files: Int Iterators. (line 6)
-* INT16_TYPE: Type Layout. (line 216)
-* INT32_TYPE: Type Layout. (line 217)
-* INT64_TYPE: Type Layout. (line 218)
-* INT8_TYPE: Type Layout. (line 215)
+* insv instruction pattern: Standard Names. (line 1072)
+* insvM instruction pattern: Standard Names. (line 1024)
+* insvmisalignM instruction pattern: Standard Names. (line 1034)
+* int iterators in .md files: Int Iterators. (line 6)
+* INT16_TYPE: Type Layout. (line 217)
+* INT32_TYPE: Type Layout. (line 218)
+* INT64_TYPE: Type Layout. (line 219)
+* INT8_TYPE: Type Layout. (line 216)
+* INT_FAST16_TYPE: Type Layout. (line 233)
+* INT_FAST32_TYPE: Type Layout. (line 234)
+* INT_FAST64_TYPE: Type Layout. (line 235)
+* INT_FAST8_TYPE: Type Layout. (line 232)
+* INT_LEAST16_TYPE: Type Layout. (line 225)
+* INT_LEAST32_TYPE: Type Layout. (line 226)
+* INT_LEAST64_TYPE: Type Layout. (line 227)
+* INT_LEAST8_TYPE: Type Layout. (line 224)
+* INT_TYPE_SIZE: Type Layout. (line 12)
* INTEGER_CST: Constant expressions.
(line 6)
* INTEGER_TYPE: Types. (line 6)
@@ -48590,163 +49010,147 @@ Concept Index
* interfacing to GCC output: Interface. (line 6)
* interlock delays: Processor pipeline description.
(line 6)
-* intermediate representation lowering: Parsing pass. (line 13)
-* INTMAX_TYPE: Type Layout. (line 192)
-* INTPTR_TYPE: Type Layout. (line 239)
+* intermediate representation lowering: Parsing pass. (line 14)
+* INTMAX_TYPE: Type Layout. (line 193)
+* INTPTR_TYPE: Type Layout. (line 240)
* introduction: Top. (line 6)
-* INT_FAST16_TYPE: Type Layout. (line 232)
-* INT_FAST32_TYPE: Type Layout. (line 233)
-* INT_FAST64_TYPE: Type Layout. (line 234)
-* INT_FAST8_TYPE: Type Layout. (line 231)
-* INT_LEAST16_TYPE: Type Layout. (line 224)
-* INT_LEAST32_TYPE: Type Layout. (line 225)
-* INT_LEAST64_TYPE: Type Layout. (line 226)
-* INT_LEAST8_TYPE: Type Layout. (line 223)
-* INT_TYPE_SIZE: Type Layout. (line 11)
* INVOKE__main: Macros for Initialization.
- (line 50)
-* in_struct: Flags. (line 245)
-* 'in_struct', in 'code_label' and 'note': Flags. (line 59)
-* 'in_struct', in 'insn' and 'jump_insn' and 'call_insn': Flags.
- (line 49)
-* 'in_struct', in 'insn', 'call_insn', 'jump_insn' and 'jump_table_data': Flags.
- (line 148)
-* 'in_struct', in 'subreg': Flags. (line 187)
-* ior: Arithmetic. (line 163)
-* 'ior' and attributes: Expressions. (line 50)
-* 'ior', canonicalization of: Insn Canonicalizations.
(line 51)
-* 'iorM3' instruction pattern: Standard Names. (line 276)
-* IRA_HARD_REGNO_ADD_COST_MULTIPLIER: Allocation Order. (line 44)
-* IS_ASM_LOGICAL_LINE_SEPARATOR: Data Output. (line 123)
-* is_gimple_addressable: Logical Operators. (line 113)
-* is_gimple_asm_val: Logical Operators. (line 117)
-* is_gimple_assign: Logical Operators. (line 149)
-* is_gimple_call: Logical Operators. (line 152)
-* is_gimple_call_addr: Logical Operators. (line 120)
-* is_gimple_constant: Logical Operators. (line 128)
-* is_gimple_debug: Logical Operators. (line 155)
-* is_gimple_ip_invariant: Logical Operators. (line 137)
-* is_gimple_ip_invariant_address: Logical Operators. (line 142)
-* is_gimple_mem_ref_addr: Logical Operators. (line 124)
-* is_gimple_min_invariant: Logical Operators. (line 131)
-* is_gimple_omp: Logical Operators. (line 166)
-* is_gimple_val: Logical Operators. (line 107)
-* iterators in '.md' files: Iterators. (line 6)
+* ior: Arithmetic. (line 162)
+* ior and attributes: Expressions. (line 50)
+* ior, canonicalization of: Insn Canonicalizations.
+ (line 52)
+* iorM3 instruction pattern: Standard Names. (line 279)
+* IRA_HARD_REGNO_ADD_COST_MULTIPLIER: Allocation Order. (line 46)
+* IS_ASM_LOGICAL_LINE_SEPARATOR: Data Output. (line 125)
+* is_gimple_addressable: Logical Operators. (line 115)
+* is_gimple_asm_val: Logical Operators. (line 119)
+* is_gimple_assign: Logical Operators. (line 151)
+* is_gimple_call: Logical Operators. (line 154)
+* is_gimple_call_addr: Logical Operators. (line 122)
+* is_gimple_constant: Logical Operators. (line 130)
+* is_gimple_debug: Logical Operators. (line 157)
+* is_gimple_ip_invariant: Logical Operators. (line 139)
+* is_gimple_ip_invariant_address: Logical Operators. (line 144)
+* is_gimple_mem_ref_addr: Logical Operators. (line 126)
+* is_gimple_min_invariant: Logical Operators. (line 133)
+* is_gimple_omp: Logical Operators. (line 168)
+* is_gimple_val: Logical Operators. (line 109)
+* iterators in .md files: Iterators. (line 6)
* IV analysis on GIMPLE: Scalar evolutions. (line 6)
* IV analysis on RTL: loop-iv. (line 6)
* JMP_BUF_SIZE: Exception Region Output.
- (line 82)
+ (line 84)
* jump: Flags. (line 286)
-* 'jump' instruction pattern: Standard Names. (line 1146)
+* jump instruction pattern: Standard Names. (line 1151)
* jump instruction patterns: Jump Patterns. (line 6)
-* jump instructions and 'set': Side Effects. (line 56)
-* 'jump', in 'call_insn': Flags. (line 161)
-* 'jump', in 'insn': Flags. (line 157)
-* 'jump', in 'mem': Flags. (line 70)
-* Jumps: Jumps. (line 6)
-* JUMP_ALIGN: Alignment Output. (line 8)
+* jump instructions and set: Side Effects. (line 56)
+* jump, in call_insn: Flags. (line 161)
+* jump, in insn: Flags. (line 157)
+* jump, in mem: Flags. (line 70)
+* JUMP_ALIGN: Alignment Output. (line 9)
* jump_insn: Insns. (line 73)
-* 'jump_insn' and '/f': Flags. (line 107)
-* 'jump_insn' and '/s': Flags. (line 49)
-* 'jump_insn' and '/s' <1>: Flags. (line 148)
-* 'jump_insn' and '/u': Flags. (line 39)
-* 'jump_insn' and '/v': Flags. (line 44)
+* jump_insn and /f: Flags. (line 107)
+* jump_insn and /s: Flags. (line 49)
+* jump_insn and /u: Flags. (line 39)
+* jump_insn and /v: Flags. (line 44)
* JUMP_LABEL: Insns. (line 80)
-* JUMP_TABLES_IN_TEXT_SECTION: Sections. (line 150)
* jump_table_data: Insns. (line 166)
-* 'jump_table_data' and '/s': Flags. (line 148)
-* 'jump_table_data' and '/v': Flags. (line 44)
-* LABEL_ALIGN: Alignment Output. (line 57)
-* LABEL_ALIGN_AFTER_BARRIER: Alignment Output. (line 26)
-* LABEL_ALTERNATE_NAME: Edges. (line 180)
+* jump_table_data and /s: Flags. (line 148)
+* jump_table_data and /v: Flags. (line 44)
+* JUMP_TABLES_IN_TEXT_SECTION: Sections. (line 151)
+* Jumps: Jumps. (line 6)
+* LABEL_ALIGN: Alignment Output. (line 58)
+* LABEL_ALIGN_AFTER_BARRIER: Alignment Output. (line 27)
* LABEL_ALT_ENTRY_P: Insns. (line 146)
+* LABEL_ALTERNATE_NAME: Edges. (line 181)
* LABEL_DECL: Declarations. (line 6)
* LABEL_KIND: Insns. (line 146)
* LABEL_NUSES: Insns. (line 142)
* LABEL_PRESERVE_P: Flags. (line 59)
* label_ref: Constants. (line 127)
-* 'label_ref' and '/v': Flags. (line 65)
-* 'label_ref', RTL sharing: Sharing. (line 35)
+* label_ref and /v: Flags. (line 65)
+* label_ref, RTL sharing: Sharing. (line 35)
* LABEL_REF_NONLOCAL_P: Flags. (line 65)
-* language-dependent trees: Language-dependent trees.
- (line 6)
-* language-independent intermediate representation: Parsing pass.
- (line 13)
* lang_hooks.gimplify_expr: Gimplification pass.
(line 18)
* lang_hooks.parse_file: Parsing pass. (line 6)
+* language-dependent trees: Language-dependent trees.
+ (line 6)
+* language-independent intermediate representation: Parsing pass.
+ (line 14)
* large return values: Aggregate Return. (line 6)
-* LAST_STACK_REG: Stack Registers. (line 30)
+* LAST_STACK_REG: Stack Registers. (line 31)
* LAST_VIRTUAL_REGISTER: Regs and Memory. (line 51)
-* 'lceilMN2': Standard Names. (line 722)
+* lceilMN2: Standard Names. (line 727)
* LCSSA: LCSSA. (line 6)
-* LDD_SUFFIX: Macros for Initialization.
- (line 121)
* LD_FINI_SWITCH: Macros for Initialization.
- (line 28)
+ (line 29)
* LD_INIT_SWITCH: Macros for Initialization.
- (line 24)
+ (line 25)
+* LDD_SUFFIX: Macros for Initialization.
+ (line 122)
* le: Comparisons. (line 76)
-* 'le' and attributes: Expressions. (line 83)
+* le and attributes: Expressions. (line 85)
+* LE_EXPR: Unary and Binary Expressions.
+ (line 6)
* leaf functions: Leaf Functions. (line 6)
-* leaf_function_p: Standard Names. (line 1230)
-* LEAF_REGISTERS: Leaf Functions. (line 23)
-* LEAF_REG_REMAP: Leaf Functions. (line 37)
-* left rotate: Arithmetic. (line 195)
-* left shift: Arithmetic. (line 173)
-* LEGITIMATE_PIC_OPERAND_P: PIC. (line 31)
-* LEGITIMIZE_RELOAD_ADDRESS: Addressing Modes. (line 150)
-* length: GTY Options. (line 47)
+* leaf_function_p: Standard Names. (line 1236)
+* LEAF_REG_REMAP: Leaf Functions. (line 39)
+* LEAF_REGISTERS: Leaf Functions. (line 25)
+* left rotate: Arithmetic. (line 194)
+* left shift: Arithmetic. (line 172)
+* LEGITIMATE_PIC_OPERAND_P: PIC. (line 32)
+* LEGITIMIZE_RELOAD_ADDRESS: Addressing Modes. (line 153)
+* length: GTY Options. (line 50)
* less than: Comparisons. (line 68)
* less than or equal: Comparisons. (line 76)
* leu: Comparisons. (line 76)
-* 'leu' and attributes: Expressions. (line 83)
-* LE_EXPR: Unary and Binary Expressions.
- (line 6)
-* 'lfloorMN2': Standard Names. (line 717)
+* leu and attributes: Expressions. (line 85)
+* lfloorMN2: Standard Names. (line 722)
* LIB2FUNCS_EXTRA: Target Fragment. (line 11)
+* LIB_SPEC: Driver. (line 108)
* LIBCALL_VALUE: Scalar Return. (line 56)
-* 'libgcc.a': Library Calls. (line 6)
+* libgcc.a: Library Calls. (line 6)
* LIBGCC2_CFLAGS: Target Fragment. (line 8)
-* LIBGCC2_GNU_PREFIX: Type Layout. (line 102)
-* LIBGCC2_UNWIND_ATTRIBUTE: Misc. (line 1097)
-* LIBGCC_SPEC: Driver. (line 115)
+* LIBGCC2_GNU_PREFIX: Type Layout. (line 103)
+* LIBGCC2_UNWIND_ATTRIBUTE: Misc. (line 1104)
+* LIBGCC_SPEC: Driver. (line 116)
* library subroutine names: Library Calls. (line 6)
-* LIBRARY_PATH_ENV: Misc. (line 509)
-* LIB_SPEC: Driver. (line 107)
-* LIMIT_RELOAD_CLASS: Register Classes. (line 296)
-* LINK_COMMAND_SPEC: Driver. (line 236)
-* LINK_EH_SPEC: Driver. (line 142)
-* LINK_GCC_C_SEQUENCE_SPEC: Driver. (line 232)
-* LINK_LIBGCC_SPECIAL_1: Driver. (line 227)
-* LINK_SPEC: Driver. (line 100)
+* LIBRARY_PATH_ENV: Misc. (line 511)
+* LIMIT_RELOAD_CLASS: Register Classes. (line 300)
+* LINK_COMMAND_SPEC: Driver. (line 237)
+* LINK_EH_SPEC: Driver. (line 143)
+* LINK_GCC_C_SEQUENCE_SPEC: Driver. (line 233)
+* LINK_LIBGCC_SPECIAL_1: Driver. (line 228)
+* LINK_SPEC: Driver. (line 101)
* list: Containers. (line 6)
* Liveness representation: Liveness information.
(line 6)
-* load address instruction: Simple Constraints. (line 162)
-* LOAD_EXTEND_OP: Misc. (line 59)
-* 'load_multiple' instruction pattern: Standard Names. (line 136)
-* Local Register Allocator (LRA): RTL passes. (line 187)
-* LOCAL_ALIGNMENT: Storage Layout. (line 254)
+* lo_sum: Arithmetic. (line 24)
+* load address instruction: Simple Constraints. (line 164)
+* LOAD_EXTEND_OP: Misc. (line 60)
+* load_multiple instruction pattern: Standard Names. (line 137)
+* Local Register Allocator (LRA): RTL passes. (line 188)
+* LOCAL_ALIGNMENT: Storage Layout. (line 258)
* LOCAL_CLASS_P: Classes. (line 73)
-* LOCAL_DECL_ALIGNMENT: Storage Layout. (line 291)
-* LOCAL_INCLUDE_DIR: Driver. (line 312)
-* LOCAL_LABEL_PREFIX: Instruction Output. (line 151)
-* LOCAL_REGNO: Register Basics. (line 100)
+* LOCAL_DECL_ALIGNMENT: Storage Layout. (line 295)
+* LOCAL_INCLUDE_DIR: Driver. (line 313)
+* LOCAL_LABEL_PREFIX: Instruction Output. (line 153)
+* LOCAL_REGNO: Register Basics. (line 101)
+* LOG_LINKS: Insns. (line 318)
* Logical Operators: Logical Operators. (line 6)
-* logical-and, bitwise: Arithmetic. (line 158)
-* LOGICAL_OP_NON_SHORT_CIRCUIT: Costs. (line 272)
-* 'logM2' instruction pattern: Standard Names. (line 630)
-* LOG_LINKS: Insns. (line 314)
-* 'longjmp' and automatic variables: Interface. (line 52)
-* LONG_ACCUM_TYPE_SIZE: Type Layout. (line 92)
-* LONG_DOUBLE_TYPE_SIZE: Type Layout. (line 57)
-* LONG_FRACT_TYPE_SIZE: Type Layout. (line 72)
-* LONG_LONG_ACCUM_TYPE_SIZE: Type Layout. (line 97)
-* LONG_LONG_FRACT_TYPE_SIZE: Type Layout. (line 77)
-* LONG_LONG_TYPE_SIZE: Type Layout. (line 32)
-* LONG_TYPE_SIZE: Type Layout. (line 21)
+* logical-and, bitwise: Arithmetic. (line 157)
+* LOGICAL_OP_NON_SHORT_CIRCUIT: Costs. (line 273)
+* logM2 instruction pattern: Standard Names. (line 635)
+* LONG_ACCUM_TYPE_SIZE: Type Layout. (line 93)
+* LONG_DOUBLE_TYPE_SIZE: Type Layout. (line 58)
+* LONG_FRACT_TYPE_SIZE: Type Layout. (line 73)
+* LONG_LONG_ACCUM_TYPE_SIZE: Type Layout. (line 98)
+* LONG_LONG_FRACT_TYPE_SIZE: Type Layout. (line 78)
+* LONG_LONG_TYPE_SIZE: Type Layout. (line 33)
+* LONG_TYPE_SIZE: Type Layout. (line 22)
+* longjmp and automatic variables: Interface. (line 52)
* Loop analysis: Loop representation.
(line 6)
* Loop manipulation: Loop manipulation. (line 6)
@@ -48754,30 +49158,29 @@ Concept Index
* Loop representation: Loop representation.
(line 6)
* Loop-closed SSA form: LCSSA. (line 6)
-* looping instruction patterns: Looping Patterns. (line 6)
-* LOOP_ALIGN: Alignment Output. (line 40)
+* LOOP_ALIGN: Alignment Output. (line 41)
* LOOP_EXPR: Unary and Binary Expressions.
(line 6)
+* looping instruction patterns: Looping Patterns. (line 6)
* lowering, language-dependent intermediate representation: Parsing pass.
- (line 13)
-* lo_sum: Arithmetic. (line 25)
-* 'lrintMN2': Standard Names. (line 707)
-* 'lroundMN2': Standard Names. (line 712)
-* lshiftrt: Arithmetic. (line 190)
-* 'lshiftrt' and attributes: Expressions. (line 83)
+ (line 14)
+* lrintMN2: Standard Names. (line 712)
+* lroundMN2: Standard Names. (line 717)
* LSHIFT_EXPR: Unary and Binary Expressions.
(line 6)
-* 'lshrM3' instruction pattern: Standard Names. (line 549)
+* lshiftrt: Arithmetic. (line 189)
+* lshiftrt and attributes: Expressions. (line 85)
+* lshrM3 instruction pattern: Standard Names. (line 554)
* lt: Comparisons. (line 68)
-* 'lt' and attributes: Expressions. (line 83)
+* lt and attributes: Expressions. (line 85)
+* LT_EXPR: Unary and Binary Expressions.
+ (line 6)
* LTGT_EXPR: Unary and Binary Expressions.
(line 6)
* lto: LTO. (line 6)
* ltrans: LTO. (line 6)
* ltu: Comparisons. (line 68)
-* LT_EXPR: Unary and Binary Expressions.
- (line 6)
-* 'm' in constraint: Simple Constraints. (line 17)
+* m in constraint: Simple Constraints. (line 17)
* machine attributes: Target Attributes. (line 6)
* machine description macros: Target Macros. (line 6)
* machine descriptions: Machine Desc. (line 6)
@@ -48789,158 +49192,158 @@ Concept Index
(line 6)
* machine_mode: Machine Modes. (line 6)
* macros, target description: Target Macros. (line 6)
-* 'maddMN4' instruction pattern: Standard Names. (line 472)
-* makefile fragment: Fragments. (line 6)
-* makefile targets: Makefile. (line 6)
-* MAKE_DECL_ONE_ONLY: Label Output. (line 253)
+* maddMN4 instruction pattern: Standard Names. (line 477)
+* MAKE_DECL_ONE_ONLY: Label Output. (line 257)
* make_safe_from: Expander Definitions.
(line 151)
-* MALLOC_ABI_ALIGNMENT: Storage Layout. (line 173)
+* makefile fragment: Fragments. (line 6)
+* makefile targets: Makefile. (line 6)
+* MALLOC_ABI_ALIGNMENT: Storage Layout. (line 175)
* Manipulating GIMPLE statements: Manipulating GIMPLE statements.
(line 6)
+* mark_hook: GTY Options. (line 137)
* marking roots: GGC Roots. (line 6)
-* mark_hook: GTY Options. (line 139)
* MASK_RETURN_ADDR: Exception Region Output.
- (line 34)
+ (line 35)
* Match and Simplify: Match and Simplify. (line 6)
-* matching constraint: Simple Constraints. (line 140)
-* matching operands: Output Template. (line 49)
-* match_dup: RTL Template. (line 73)
* match_dup <1>: define_peephole2. (line 28)
-* 'match_dup' and attributes: Insn Lengths. (line 16)
+* match_dup: RTL Template. (line 73)
+* match_dup and attributes: Insn Lengths. (line 16)
+* match_op_dup: RTL Template. (line 163)
* match_operand: RTL Template. (line 16)
-* 'match_operand' and attributes: Expressions. (line 55)
+* match_operand and attributes: Expressions. (line 55)
* match_operator: RTL Template. (line 95)
-* match_op_dup: RTL Template. (line 163)
-* match_parallel: RTL Template. (line 172)
* match_par_dup: RTL Template. (line 219)
-* match_scratch: RTL Template. (line 58)
+* match_parallel: RTL Template. (line 172)
* match_scratch <1>: define_peephole2. (line 28)
-* 'match_test' and attributes: Expressions. (line 64)
+* match_scratch: RTL Template. (line 58)
+* match_test and attributes: Expressions. (line 64)
+* matching constraint: Simple Constraints. (line 142)
+* matching operands: Output Template. (line 49)
* math library: Soft float library routines.
(line 6)
* math, in RTL: Arithmetic. (line 6)
+* MATH_LIBRARY: Misc. (line 504)
* matherr: Library Calls. (line 59)
-* MATH_LIBRARY: Misc. (line 502)
-* 'maxM3' instruction pattern: Standard Names. (line 311)
-* MAX_BITSIZE_MODE_ANY_INT: Machine Modes. (line 358)
-* MAX_BITSIZE_MODE_ANY_MODE: Machine Modes. (line 364)
-* MAX_BITS_PER_WORD: Storage Layout. (line 54)
-* MAX_CONDITIONAL_EXECUTE: Misc. (line 524)
-* MAX_FIXED_MODE_SIZE: Storage Layout. (line 436)
-* MAX_MOVE_MAX: Misc. (line 105)
-* MAX_OFILE_ALIGNMENT: Storage Layout. (line 208)
-* MAX_REGS_PER_ADDRESS: Addressing Modes. (line 42)
-* MAX_STACK_ALIGNMENT: Storage Layout. (line 202)
-* maybe_undef: GTY Options. (line 148)
-* may_trap_p, tree_could_trap_p: Edges. (line 114)
+* MAX_BITS_PER_WORD: Storage Layout. (line 55)
+* MAX_BITSIZE_MODE_ANY_INT: Machine Modes. (line 359)
+* MAX_BITSIZE_MODE_ANY_MODE: Machine Modes. (line 365)
+* MAX_CONDITIONAL_EXECUTE: Misc. (line 526)
+* MAX_FIXED_MODE_SIZE: Storage Layout. (line 441)
+* MAX_MOVE_MAX: Misc. (line 106)
+* MAX_OFILE_ALIGNMENT: Storage Layout. (line 212)
+* MAX_REGS_PER_ADDRESS: Addressing Modes. (line 43)
+* MAX_STACK_ALIGNMENT: Storage Layout. (line 205)
+* maxM3 instruction pattern: Standard Names. (line 314)
+* may_trap_p, tree_could_trap_p: Edges. (line 115)
+* maybe_undef: GTY Options. (line 145)
* mcount: Profiling. (line 12)
-* MD_EXEC_PREFIX: Driver. (line 267)
-* MD_FALLBACK_FRAME_STATE_FOR: Exception Handling. (line 93)
-* MD_HANDLE_UNWABI: Exception Handling. (line 112)
-* MD_STARTFILE_PREFIX: Driver. (line 295)
-* MD_STARTFILE_PREFIX_1: Driver. (line 300)
-* mem: Regs and Memory. (line 370)
-* 'mem' and '/c': Flags. (line 81)
-* 'mem' and '/f': Flags. (line 85)
-* 'mem' and '/j': Flags. (line 70)
-* 'mem' and '/u': Flags. (line 134)
-* 'mem' and '/v': Flags. (line 76)
-* 'mem', RTL sharing: Sharing. (line 40)
-* memory model: Memory model. (line 6)
-* memory reference, nonoffsettable: Simple Constraints. (line 254)
-* memory references in constraints: Simple Constraints. (line 17)
-* 'memory_barrier' instruction pattern: Standard Names. (line 1616)
-* MEMORY_MOVE_COST: Costs. (line 53)
-* memory_operand: Machine-Independent Predicates.
- (line 57)
-* MEM_ADDR_SPACE: Special Accessors. (line 48)
+* MD_EXEC_PREFIX: Driver. (line 268)
+* MD_FALLBACK_FRAME_STATE_FOR: Exception Handling. (line 94)
+* MD_HANDLE_UNWABI: Exception Handling. (line 114)
+* MD_STARTFILE_PREFIX: Driver. (line 296)
+* MD_STARTFILE_PREFIX_1: Driver. (line 301)
+* mem: Regs and Memory. (line 374)
+* mem and /c: Flags. (line 81)
+* mem and /f: Flags. (line 85)
+* mem and /j: Flags. (line 70)
+* mem and /u: Flags. (line 134)
+* mem and /v: Flags. (line 76)
+* mem, RTL sharing: Sharing. (line 40)
+* MEM_ADDR_SPACE: Special Accessors. (line 49)
* MEM_ALIAS_SET: Special Accessors. (line 9)
-* MEM_ALIGN: Special Accessors. (line 45)
-* MEM_EXPR: Special Accessors. (line 19)
+* MEM_ALIGN: Special Accessors. (line 46)
+* MEM_EXPR: Special Accessors. (line 20)
* MEM_KEEP_ALIAS_SET_P: Flags. (line 70)
* MEM_NOTRAP_P: Flags. (line 81)
-* MEM_OFFSET: Special Accessors. (line 31)
-* MEM_OFFSET_KNOWN_P: Special Accessors. (line 27)
+* MEM_OFFSET: Special Accessors. (line 32)
+* MEM_OFFSET_KNOWN_P: Special Accessors. (line 28)
* MEM_POINTER: Flags. (line 85)
* MEM_READONLY_P: Flags. (line 134)
* MEM_REF: Storage References. (line 6)
-* 'mem_signal_fenceMODE' instruction pattern: Standard Names.
- (line 1875)
-* MEM_SIZE: Special Accessors. (line 39)
-* MEM_SIZE_KNOWN_P: Special Accessors. (line 35)
-* 'mem_thread_fenceMODE' instruction pattern: Standard Names.
- (line 1867)
+* mem_signal_fenceMODE instruction pattern: Standard Names. (line 1885)
+* MEM_SIZE: Special Accessors. (line 40)
+* MEM_SIZE_KNOWN_P: Special Accessors. (line 36)
+* mem_thread_fenceMODE instruction pattern: Standard Names. (line 1877)
* MEM_VOLATILE_P: Flags. (line 76)
+* memory model: Memory model. (line 6)
+* memory reference, nonoffsettable: Simple Constraints. (line 256)
+* memory references in constraints: Simple Constraints. (line 17)
+* memory_barrier instruction pattern: Standard Names. (line 1626)
+* MEMORY_MOVE_COST: Costs. (line 54)
+* memory_operand: Machine-Independent Predicates.
+ (line 58)
* METHOD_TYPE: Types. (line 6)
-* MINIMUM_ALIGNMENT: Storage Layout. (line 304)
-* MINIMUM_ATOMIC_ALIGNMENT: Storage Layout. (line 181)
-* 'minM3' instruction pattern: Standard Names. (line 311)
-* minus: Arithmetic. (line 38)
-* 'minus' and attributes: Expressions. (line 83)
-* 'minus', canonicalization of: Insn Canonicalizations.
+* MIN_UNITS_PER_WORD: Storage Layout. (line 65)
+* MINIMUM_ALIGNMENT: Storage Layout. (line 308)
+* MINIMUM_ATOMIC_ALIGNMENT: Storage Layout. (line 183)
+* minM3 instruction pattern: Standard Names. (line 314)
+* minus: Arithmetic. (line 36)
+* minus and attributes: Expressions. (line 85)
+* minus, canonicalization of: Insn Canonicalizations.
(line 27)
* MINUS_EXPR: Unary and Binary Expressions.
(line 6)
-* MIN_UNITS_PER_WORD: Storage Layout. (line 64)
* MIPS coprocessor-definition macros: MIPS Coprocessors. (line 6)
* miscellaneous register hooks: Miscellaneous Register Hooks.
(line 6)
* mnemonic attribute: Mnemonic Attribute. (line 6)
-* mod: Arithmetic. (line 136)
-* 'mod' and attributes: Expressions. (line 83)
-* mode classes: Machine Modes. (line 225)
-* mode iterators in '.md' files: Mode Iterators. (line 6)
+* mod: Arithmetic. (line 135)
+* mod and attributes: Expressions. (line 85)
+* mode classes: Machine Modes. (line 226)
+* mode iterators in .md files: Mode Iterators. (line 6)
* mode switching: Mode Switching. (line 6)
-* MODES_TIEABLE_P: Values in Registers.
- (line 127)
-* MODE_ACCUM: Machine Modes. (line 255)
-* MODE_BASE_REG_CLASS: Register Classes. (line 116)
-* MODE_BASE_REG_REG_CLASS: Register Classes. (line 122)
-* MODE_CC: Machine Modes. (line 274)
+* MODE_ACCUM: Machine Modes. (line 256)
+* MODE_BASE_REG_CLASS: Register Classes. (line 119)
+* MODE_BASE_REG_REG_CLASS: Register Classes. (line 125)
* MODE_CC <1>: MODE_CC Condition Codes.
(line 6)
-* MODE_CODE_BASE_REG_CLASS: Register Classes. (line 129)
-* MODE_COMPLEX_FLOAT: Machine Modes. (line 266)
-* MODE_COMPLEX_INT: Machine Modes. (line 263)
-* MODE_DECIMAL_FLOAT: Machine Modes. (line 243)
-* MODE_FLOAT: Machine Modes. (line 239)
-* MODE_FRACT: Machine Modes. (line 247)
-* MODE_FUNCTION: Machine Modes. (line 270)
-* MODE_INT: Machine Modes. (line 231)
-* MODE_PARTIAL_INT: Machine Modes. (line 235)
-* MODE_POINTER_BOUNDS: Machine Modes. (line 279)
-* MODE_RANDOM: Machine Modes. (line 284)
-* MODE_UACCUM: Machine Modes. (line 259)
-* MODE_UFRACT: Machine Modes. (line 251)
+* MODE_CC: Machine Modes. (line 275)
+* MODE_CODE_BASE_REG_CLASS: Register Classes. (line 133)
+* MODE_COMPLEX_FLOAT: Machine Modes. (line 267)
+* MODE_COMPLEX_INT: Machine Modes. (line 264)
+* MODE_DECIMAL_FLOAT: Machine Modes. (line 244)
+* MODE_FLOAT: Machine Modes. (line 240)
+* MODE_FRACT: Machine Modes. (line 248)
+* MODE_FUNCTION: Machine Modes. (line 271)
+* MODE_INT: Machine Modes. (line 232)
+* MODE_PARTIAL_INT: Machine Modes. (line 236)
+* MODE_POINTER_BOUNDS: Machine Modes. (line 280)
+* MODE_RANDOM: Machine Modes. (line 285)
+* MODE_UACCUM: Machine Modes. (line 260)
+* MODE_UFRACT: Machine Modes. (line 252)
+* MODES_TIEABLE_P: Values in Registers.
+ (line 129)
* modifiers in constraints: Modifiers. (line 6)
* MODIFY_EXPR: Unary and Binary Expressions.
(line 6)
-* MODIFY_JNI_METHOD_CALL: Misc. (line 873)
-* 'modM3' instruction pattern: Standard Names. (line 276)
-* modulo scheduling: RTL passes. (line 123)
-* MOVE_MAX: Misc. (line 100)
-* MOVE_MAX_PIECES: Costs. (line 199)
-* MOVE_RATIO: Costs. (line 148)
-* 'movM' instruction pattern: Standard Names. (line 11)
-* 'movmemM' instruction pattern: Standard Names. (line 787)
-* 'movmisalignM' instruction pattern: Standard Names. (line 125)
-* 'movMODEcc' instruction pattern: Standard Names. (line 1081)
-* 'movstr' instruction pattern: Standard Names. (line 822)
-* 'movstrictM' instruction pattern: Standard Names. (line 119)
-* 'msubMN4' instruction pattern: Standard Names. (line 495)
-* 'mulhisi3' instruction pattern: Standard Names. (line 448)
-* 'mulM3' instruction pattern: Standard Names. (line 276)
-* 'mulqihi3' instruction pattern: Standard Names. (line 452)
-* 'mulsidi3' instruction pattern: Standard Names. (line 452)
-* mult: Arithmetic. (line 93)
-* 'mult' and attributes: Expressions. (line 83)
-* 'mult', canonicalization of: Insn Canonicalizations.
+* MODIFY_JNI_METHOD_CALL: Misc. (line 877)
+* modM3 instruction pattern: Standard Names. (line 279)
+* modulo scheduling: RTL passes. (line 124)
+* MOVE_MAX: Misc. (line 101)
+* MOVE_MAX_PIECES: Costs. (line 200)
+* MOVE_RATIO: Costs. (line 149)
+* movM instruction pattern: Standard Names. (line 11)
+* movmemM instruction pattern: Standard Names. (line 792)
+* movmisalignM instruction pattern: Standard Names. (line 126)
+* movMODEcc instruction pattern: Standard Names. (line 1086)
+* movstr instruction pattern: Standard Names. (line 827)
+* movstrictM instruction pattern: Standard Names. (line 120)
+* msubMN4 instruction pattern: Standard Names. (line 500)
+* mulhisi3 instruction pattern: Standard Names. (line 453)
+* mulM3 instruction pattern: Standard Names. (line 279)
+* mulqihi3 instruction pattern: Standard Names. (line 457)
+* mulsidi3 instruction pattern: Standard Names. (line 457)
+* mult: Arithmetic. (line 92)
+* mult and attributes: Expressions. (line 85)
+* mult, canonicalization of: Insn Canonicalizations.
(line 27)
-* 'mult', canonicalization of <1>: Insn Canonicalizations.
- (line 91)
+* MULT_EXPR: Unary and Binary Expressions.
+ (line 6)
+* MULT_HIGHPART_EXPR: Unary and Binary Expressions.
+ (line 6)
* MULTIARCH_DIRNAME: Target Fragment. (line 170)
-* MULTILIB_DEFAULTS: Driver. (line 252)
+* MULTILIB_DEFAULTS: Driver. (line 253)
* MULTILIB_DIRNAMES: Target Fragment. (line 44)
* MULTILIB_EXCEPTIONS: Target Fragment. (line 70)
* MULTILIB_EXTRA_OPTS: Target Fragment. (line 132)
@@ -48950,103 +49353,98 @@ Concept Index
* MULTILIB_REQUIRED: Target Fragment. (line 82)
* MULTILIB_REUSE: Target Fragment. (line 103)
* multiple alternative constraints: Multi-Alternative. (line 6)
-* MULTIPLE_SYMBOL_SPACES: Misc. (line 482)
-* multiplication: Arithmetic. (line 93)
-* multiplication with signed saturation: Arithmetic. (line 93)
-* multiplication with unsigned saturation: Arithmetic. (line 93)
-* MULT_EXPR: Unary and Binary Expressions.
- (line 6)
-* MULT_HIGHPART_EXPR: Unary and Binary Expressions.
- (line 6)
-* 'n' in constraint: Simple Constraints. (line 73)
+* MULTIPLE_SYMBOL_SPACES: Misc. (line 484)
+* multiplication: Arithmetic. (line 92)
+* multiplication with signed saturation: Arithmetic. (line 92)
+* multiplication with unsigned saturation: Arithmetic. (line 92)
+* n in constraint: Simple Constraints. (line 75)
+* N_REG_CLASSES: Register Classes. (line 83)
* name: Identifiers. (line 6)
* named address spaces: Named Address Spaces.
(line 6)
* named patterns and conditions: Patterns. (line 49)
* names, pattern: Standard Names. (line 6)
* namespace, scope: Namespaces. (line 6)
-* NAMESPACE_DECL: Declarations. (line 6)
* NAMESPACE_DECL <1>: Namespaces. (line 6)
-* NATIVE_SYSTEM_HEADER_COMPONENT: Driver. (line 322)
+* NAMESPACE_DECL: Declarations. (line 6)
+* NATIVE_SYSTEM_HEADER_COMPONENT: Driver. (line 323)
* ne: Comparisons. (line 56)
-* 'ne' and attributes: Expressions. (line 83)
-* 'nearbyintM2' instruction pattern: Standard Names. (line 689)
-* neg: Arithmetic. (line 82)
-* 'neg' and attributes: Expressions. (line 83)
-* 'neg', canonicalization of: Insn Canonicalizations.
+* ne and attributes: Expressions. (line 85)
+* NE_EXPR: Unary and Binary Expressions.
+ (line 6)
+* nearbyintM2 instruction pattern: Standard Names. (line 694)
+* neg: Arithmetic. (line 81)
+* neg and attributes: Expressions. (line 85)
+* neg, canonicalization of: Insn Canonicalizations.
(line 27)
* NEGATE_EXPR: Unary and Binary Expressions.
(line 6)
-* negation: Arithmetic. (line 82)
-* negation with signed saturation: Arithmetic. (line 82)
-* negation with unsigned saturation: Arithmetic. (line 82)
-* 'negM2' instruction pattern: Standard Names. (line 561)
+* negation: Arithmetic. (line 81)
+* negation with signed saturation: Arithmetic. (line 81)
+* negation with unsigned saturation: Arithmetic. (line 81)
+* negM2 instruction pattern: Standard Names. (line 566)
* nested functions, trampolines for: Trampolines. (line 6)
-* nested_ptr: GTY Options. (line 156)
+* nested_ptr: GTY Options. (line 152)
* next_bb, prev_bb, FOR_EACH_BB, FOR_ALL_BB: Basic Blocks. (line 25)
* NEXT_INSN: Insns. (line 30)
-* NEXT_OBJC_RUNTIME: Library Calls. (line 82)
-* NE_EXPR: Unary and Binary Expressions.
- (line 6)
+* NEXT_OBJC_RUNTIME: Library Calls. (line 83)
* nil: RTL Objects. (line 73)
* NM_FLAGS: Macros for Initialization.
- (line 110)
+ (line 111)
+* NO_DBX_BNSYM_ENSYM: DBX Hooks. (line 26)
+* NO_DBX_FUNCTION_END: DBX Hooks. (line 20)
+* NO_DBX_GCC_MARKER: File Names and DBX. (line 28)
+* NO_DBX_MAIN_SOURCE_DIRECTORY: File Names and DBX. (line 23)
+* NO_DOLLAR_IN_LABEL: Label Output. (line 67)
+* NO_DOT_IN_LABEL: Label Output. (line 73)
+* NO_FUNCTION_CSE: Costs. (line 269)
+* NO_IMPLICIT_EXTERN_C: Misc. (line 382)
+* NO_PROFILE_COUNTERS: Profiling. (line 28)
+* NO_REGS: Register Classes. (line 17)
+* NON_LVALUE_EXPR: Unary and Binary Expressions.
+ (line 6)
* nondeterministic finite state automaton: Processor pipeline description.
- (line 304)
+ (line 305)
* nonimmediate_operand: Machine-Independent Predicates.
- (line 100)
-* nonlocal goto handler: Edges. (line 171)
-* 'nonlocal_goto' instruction pattern: Standard Names. (line 1450)
-* 'nonlocal_goto_receiver' instruction pattern: Standard Names.
- (line 1467)
+ (line 101)
+* nonlocal goto handler: Edges. (line 172)
+* nonlocal_goto instruction pattern: Standard Names. (line 1458)
+* nonlocal_goto_receiver instruction pattern: Standard Names.
+ (line 1475)
* nonmemory_operand: Machine-Independent Predicates.
- (line 96)
-* nonoffsettable memory reference: Simple Constraints. (line 254)
-* NON_LVALUE_EXPR: Unary and Binary Expressions.
- (line 6)
-* 'nop' instruction pattern: Standard Names. (line 1263)
+ (line 97)
+* nonoffsettable memory reference: Simple Constraints. (line 256)
+* nop instruction pattern: Standard Names. (line 1269)
* NOP_EXPR: Unary and Binary Expressions.
(line 6)
* normal predicates: Predicates. (line 31)
-* not: Arithmetic. (line 154)
-* 'not' and attributes: Expressions. (line 50)
+* not: Arithmetic. (line 153)
+* not and attributes: Expressions. (line 50)
* not equal: Comparisons. (line 56)
-* 'not', canonicalization of: Insn Canonicalizations.
+* not, canonicalization of: Insn Canonicalizations.
(line 27)
-* note: Insns. (line 183)
-* 'note' and '/i': Flags. (line 59)
-* 'note' and '/v': Flags. (line 44)
+* note: Insns. (line 185)
+* note and /i: Flags. (line 59)
+* note and /v: Flags. (line 44)
* NOTE_INSN_BASIC_BLOCK: Basic Blocks. (line 50)
-* NOTE_INSN_BASIC_BLOCK <1>: Basic Blocks. (line 52)
-* NOTE_INSN_BLOCK_BEG: Insns. (line 208)
-* NOTE_INSN_BLOCK_END: Insns. (line 208)
-* NOTE_INSN_DELETED: Insns. (line 198)
-* NOTE_INSN_DELETED_LABEL: Insns. (line 203)
-* NOTE_INSN_EH_REGION_BEG: Insns. (line 214)
-* NOTE_INSN_EH_REGION_END: Insns. (line 214)
-* NOTE_INSN_FUNCTION_BEG: Insns. (line 221)
-* NOTE_INSN_VAR_LOCATION: Insns. (line 225)
-* NOTE_LINE_NUMBER: Insns. (line 183)
-* NOTE_SOURCE_FILE: Insns. (line 183)
-* NOTE_VAR_LOCATION: Insns. (line 225)
+* NOTE_INSN_BLOCK_BEG: Insns. (line 210)
+* NOTE_INSN_BLOCK_END: Insns. (line 210)
+* NOTE_INSN_DELETED: Insns. (line 200)
+* NOTE_INSN_DELETED_LABEL: Insns. (line 205)
+* NOTE_INSN_EH_REGION_BEG: Insns. (line 216)
+* NOTE_INSN_EH_REGION_END: Insns. (line 216)
+* NOTE_INSN_FUNCTION_BEG: Insns. (line 223)
+* NOTE_INSN_VAR_LOCATION: Insns. (line 227)
+* NOTE_LINE_NUMBER: Insns. (line 185)
+* NOTE_SOURCE_FILE: Insns. (line 185)
+* NOTE_VAR_LOCATION: Insns. (line 227)
* NOTICE_UPDATE_CC: CC0 Condition Codes.
- (line 30)
-* NO_DBX_BNSYM_ENSYM: DBX Hooks. (line 25)
-* NO_DBX_FUNCTION_END: DBX Hooks. (line 19)
-* NO_DBX_GCC_MARKER: File Names and DBX. (line 27)
-* NO_DBX_MAIN_SOURCE_DIRECTORY: File Names and DBX. (line 22)
-* NO_DOLLAR_IN_LABEL: Label Output. (line 64)
-* NO_DOT_IN_LABEL: Label Output. (line 70)
-* NO_FUNCTION_CSE: Costs. (line 268)
-* NO_IMPLICIT_EXTERN_C: Misc. (line 381)
-* NO_PROFILE_COUNTERS: Profiling. (line 27)
-* NO_REGS: Register Classes. (line 17)
+ (line 31)
+* NUM_MACHINE_MODES: Machine Modes. (line 298)
+* NUM_MODES_FOR_MODE_SWITCHING: Mode Switching. (line 31)
* Number of iterations analysis: Number of iterations.
(line 6)
-* NUM_MACHINE_MODES: Machine Modes. (line 297)
-* NUM_MODES_FOR_MODE_SWITCHING: Mode Switching. (line 30)
-* N_REG_CLASSES: Register Classes. (line 81)
-* 'o' in constraint: Simple Constraints. (line 23)
+* o in constraint: Simple Constraints. (line 23)
* OACC_CACHE: OpenACC. (line 6)
* OACC_DATA: OpenACC. (line 6)
* OACC_DECLARE: OpenACC. (line 6)
@@ -49057,12 +49455,12 @@ Concept Index
* OACC_LOOP: OpenACC. (line 6)
* OACC_PARALLEL: OpenACC. (line 6)
* OACC_UPDATE: OpenACC. (line 6)
-* OBJC_GEN_METHOD_LABEL: Label Output. (line 454)
-* OBJC_JBLEN: Misc. (line 1092)
+* OBJC_GEN_METHOD_LABEL: Label Output. (line 459)
+* OBJC_JBLEN: Misc. (line 1099)
* OBJECT_FORMAT_COFF: Macros for Initialization.
- (line 96)
-* offsettable address: Simple Constraints. (line 23)
+ (line 97)
* OFFSET_TYPE: Types. (line 6)
+* offsettable address: Simple Constraints. (line 23)
* OImode: Machine Modes. (line 51)
* Omega a solver for linear programming problems: Omega. (line 6)
* OMP_ATOMIC: OpenMP. (line 6)
@@ -49077,18 +49475,18 @@ Concept Index
* OMP_SECTION: OpenMP. (line 6)
* OMP_SECTIONS: OpenMP. (line 6)
* OMP_SINGLE: OpenMP. (line 6)
-* 'one_cmplM2' instruction pattern: Standard Names. (line 784)
+* one_cmplM2 instruction pattern: Standard Names. (line 789)
* operand access: Accessors. (line 6)
-* Operand Access Routines: SSA Operands. (line 116)
+* Operand Access Routines: SSA Operands. (line 119)
* operand constraints: Constraints. (line 6)
-* Operand Iterators: SSA Operands. (line 116)
+* Operand Iterators: SSA Operands. (line 119)
* operand predicates: Predicates. (line 6)
* operand substitution: Output Template. (line 6)
-* Operands: Operands. (line 6)
-* operands: SSA Operands. (line 6)
* operands <1>: Patterns. (line 55)
+* operands: SSA Operands. (line 6)
+* Operands: Operands. (line 6)
* operator predicates: Predicates. (line 6)
-* 'optc-gen.awk': Options. (line 6)
+* optc-gen.awk: Options. (line 6)
* OPTGROUP_ALL: Optimization groups.
(line 25)
* OPTGROUP_INLINE: Optimization groups.
@@ -49107,110 +49505,112 @@ Concept Index
* optimization info file names: Dump files and streams.
(line 6)
* Optimization infrastructure for GIMPLE: Tree SSA. (line 6)
-* OPTIMIZE_MODE_SWITCHING: Mode Switching. (line 8)
+* OPTIMIZE_MODE_SWITCHING: Mode Switching. (line 9)
* option specification files: Options. (line 6)
+* OPTION_DEFAULT_SPECS: Driver. (line 26)
* optional hardware or system features: Run-time Target. (line 59)
-* options, directory search: Including Patterns. (line 47)
-* OPTION_DEFAULT_SPECS: Driver. (line 25)
+* options, directory search: Including Patterns. (line 44)
* order of register allocation: Allocation Order. (line 6)
* ordered_comparison_operator: Machine-Independent Predicates.
- (line 115)
+ (line 116)
* ORDERED_EXPR: Unary and Binary Expressions.
(line 6)
* Ordering of Patterns: Pattern Ordering. (line 6)
-* ORIGINAL_REGNO: Special Accessors. (line 53)
-* other register constraints: Simple Constraints. (line 171)
+* ORIGINAL_REGNO: Special Accessors. (line 54)
+* other register constraints: Simple Constraints. (line 173)
* outgoing_args_size: Stack Arguments. (line 48)
-* OUTGOING_REGNO: Register Basics. (line 93)
-* OUTGOING_REG_PARM_STACK_SPACE: Stack Arguments. (line 79)
+* OUTGOING_REG_PARM_STACK_SPACE: Stack Arguments. (line 80)
+* OUTGOING_REGNO: Register Basics. (line 94)
* output of assembler code: File Framework. (line 6)
* output statements: Output Statement. (line 6)
* output templates: Output Template. (line 6)
-* output_asm_insn: Output Statement. (line 52)
-* OUTPUT_QUOTED_STRING: File Framework. (line 106)
-* OVERLAPPING_REGISTER_NAMES: Instruction Output. (line 20)
+* output_asm_insn: Output Statement. (line 53)
+* OUTPUT_QUOTED_STRING: File Framework. (line 108)
+* OVERLAPPING_REGISTER_NAMES: Instruction Output. (line 21)
* OVERLOAD: Functions for C++. (line 6)
-* OVERRIDE_ABI_FORMAT: Register Arguments. (line 153)
+* OVERRIDE_ABI_FORMAT: Register Arguments. (line 155)
* OVL_CURRENT: Functions for C++. (line 6)
* OVL_NEXT: Functions for C++. (line 6)
-* 'p' in constraint: Simple Constraints. (line 162)
-* PAD_VARARGS_DOWN: Register Arguments. (line 234)
-* parallel: Side Effects. (line 209)
+* p in constraint: Simple Constraints. (line 164)
+* PAD_VARARGS_DOWN: Register Arguments. (line 236)
+* parallel: Side Effects. (line 210)
* parameters, c++ abi: C++ ABI. (line 6)
* parameters, miscellaneous: Misc. (line 6)
* parameters, precompiled headers: PCH Target. (line 6)
* parity: Arithmetic. (line 242)
-* 'parityM2' instruction pattern: Standard Names. (line 777)
-* PARM_BOUNDARY: Storage Layout. (line 133)
+* parityM2 instruction pattern: Standard Names. (line 782)
+* PARM_BOUNDARY: Storage Layout. (line 135)
* PARM_DECL: Declarations. (line 6)
* PARSE_LDD_OUTPUT: Macros for Initialization.
- (line 125)
+ (line 127)
* pass dumps: Passes. (line 6)
+* pass_duplicate_computed_gotos: Edges. (line 162)
* passes and files of the compiler: Passes. (line 6)
* passing arguments: Interface. (line 36)
-* pass_duplicate_computed_gotos: Edges. (line 161)
* PATH_SEPARATOR: Filesystem. (line 31)
-* PATTERN: Insns. (line 284)
+* PATTERN: Insns. (line 288)
* pattern conditions: Patterns. (line 43)
* pattern names: Standard Names. (line 6)
* Pattern Ordering: Pattern Ordering. (line 6)
* patterns: Patterns. (line 6)
-* pc: Regs and Memory. (line 357)
-* 'pc' and attributes: Insn Lengths. (line 20)
-* 'pc', RTL sharing: Sharing. (line 25)
-* PCC_BITFIELD_TYPE_MATTERS: Storage Layout. (line 330)
-* PCC_STATIC_STRUCT_RETURN: Aggregate Return. (line 64)
-* PC_REGNUM: Register Basics. (line 107)
-* pc_rtx: Regs and Memory. (line 362)
+* pc: Regs and Memory. (line 361)
+* pc and attributes: Insn Lengths. (line 20)
+* pc, RTL sharing: Sharing. (line 25)
+* PC_REGNUM: Register Basics. (line 108)
+* pc_rtx: Regs and Memory. (line 366)
+* PCC_BITFIELD_TYPE_MATTERS: Storage Layout. (line 334)
+* PCC_STATIC_STRUCT_RETURN: Aggregate Return. (line 65)
* PDImode: Machine Modes. (line 40)
-* peephole optimization, RTL representation: Side Effects. (line 243)
+* peephole optimization, RTL representation: Side Effects. (line 244)
* peephole optimizer definitions: Peephole Definitions.
(line 6)
* per-function data: Per-Function Data. (line 6)
* percent sign: Output Template. (line 6)
* PHI nodes: SSA. (line 31)
* PIC: PIC. (line 6)
-* PIC_OFFSET_TABLE_REGNUM: PIC. (line 15)
-* PIC_OFFSET_TABLE_REG_CALL_CLOBBERED: PIC. (line 25)
+* PIC_OFFSET_TABLE_REG_CALL_CLOBBERED: PIC. (line 26)
+* PIC_OFFSET_TABLE_REGNUM: PIC. (line 16)
* pipeline hazard recognizer: Processor pipeline description.
(line 6)
-* pipeline hazard recognizer <1>: Processor pipeline description.
- (line 53)
* Plugins: Plugins. (line 6)
* plus: Arithmetic. (line 14)
-* 'plus' and attributes: Expressions. (line 83)
-* 'plus', canonicalization of: Insn Canonicalizations.
+* plus and attributes: Expressions. (line 85)
+* plus, canonicalization of: Insn Canonicalizations.
(line 27)
* PLUS_EXPR: Unary and Binary Expressions.
(line 6)
-* Pmode: Misc. (line 329)
+* Pmode: Misc. (line 330)
* pmode_register_operand: Machine-Independent Predicates.
- (line 34)
+ (line 35)
* pointer: Types. (line 6)
-* POINTERS_EXTEND_UNSIGNED: Storage Layout. (line 76)
* POINTER_PLUS_EXPR: Unary and Binary Expressions.
(line 6)
-* POINTER_SIZE: Storage Layout. (line 70)
+* POINTER_SIZE: Storage Layout. (line 71)
* POINTER_TYPE: Types. (line 6)
-* popcount: Arithmetic. (line 238)
-* 'popcountM2' instruction pattern: Standard Names. (line 771)
-* pops_args: Function Entry. (line 104)
+* POINTERS_EXTEND_UNSIGNED: Storage Layout. (line 77)
* pop_operand: Machine-Independent Predicates.
- (line 87)
+ (line 88)
+* popcount: Arithmetic. (line 238)
+* popcountM2 instruction pattern: Standard Names. (line 776)
+* pops_args: Function Entry. (line 106)
* portability: Portability. (line 6)
* position independent code: PIC. (line 6)
-* POSTDECREMENT_EXPR: Unary and Binary Expressions.
- (line 6)
-* POSTINCREMENT_EXPR: Unary and Binary Expressions.
- (line 6)
* post_dec: Incdec. (line 25)
* post_inc: Incdec. (line 30)
* post_modify: Incdec. (line 33)
* post_order_compute, inverted_post_order_compute, walk_dominator_tree: Basic Blocks.
(line 34)
-* POWI_MAX_MULTS: Misc. (line 961)
-* 'powM3' instruction pattern: Standard Names. (line 638)
+* POSTDECREMENT_EXPR: Unary and Binary Expressions.
+ (line 6)
+* POSTINCREMENT_EXPR: Unary and Binary Expressions.
+ (line 6)
+* POWI_MAX_MULTS: Misc. (line 967)
+* powM3 instruction pattern: Standard Names. (line 643)
* pragma: Misc. (line 387)
+* pre_dec: Incdec. (line 8)
+* PRE_GCC3_DWARF_FRAME_REGISTERS: Frame Registers. (line 127)
+* pre_inc: Incdec. (line 22)
+* pre_modify: Incdec. (line 51)
* PREDECREMENT_EXPR: Unary and Binary Expressions.
(line 6)
* predefined macros: Run-time Target. (line 6)
@@ -49220,283 +49620,272 @@ Concept Index
(line 6)
* predict.def: Profile information.
(line 24)
-* PREFERRED_DEBUGGING_TYPE: All Debuggers. (line 41)
-* PREFERRED_RELOAD_CLASS: Register Classes. (line 249)
-* PREFERRED_STACK_BOUNDARY: Storage Layout. (line 147)
-* prefetch: Side Effects. (line 323)
-* 'prefetch' and '/v': Flags. (line 214)
-* 'prefetch' instruction pattern: Standard Names. (line 1593)
+* PREFERRED_DEBUGGING_TYPE: All Debuggers. (line 42)
+* PREFERRED_RELOAD_CLASS: Register Classes. (line 253)
+* PREFERRED_STACK_BOUNDARY: Storage Layout. (line 149)
+* prefetch: Side Effects. (line 325)
+* prefetch and /v: Flags. (line 214)
+* prefetch instruction pattern: Standard Names. (line 1603)
* PREFETCH_SCHEDULE_BARRIER_P: Flags. (line 214)
* PREINCREMENT_EXPR: Unary and Binary Expressions.
(line 6)
* presence_set: Processor pipeline description.
- (line 223)
+ (line 224)
* preserving SSA form: SSA. (line 74)
* preserving virtual SSA form: SSA. (line 182)
-* pretend_args_size: Function Entry. (line 110)
+* pretend_args_size: Function Entry. (line 112)
* prev_active_insn: define_peephole. (line 60)
* PREV_INSN: Insns. (line 26)
-* pre_dec: Incdec. (line 8)
-* PRE_GCC3_DWARF_FRAME_REGISTERS: Frame Registers. (line 126)
-* pre_inc: Incdec. (line 22)
-* pre_modify: Incdec. (line 52)
-* PRINT_OPERAND: Instruction Output. (line 95)
-* PRINT_OPERAND_ADDRESS: Instruction Output. (line 122)
-* PRINT_OPERAND_PUNCT_VALID_P: Instruction Output. (line 115)
-* 'probe_stack' instruction pattern: Standard Names. (line 1442)
-* 'probe_stack_address' instruction pattern: Standard Names. (line 1435)
+* PRINT_OPERAND: Instruction Output. (line 96)
+* PRINT_OPERAND_ADDRESS: Instruction Output. (line 124)
+* PRINT_OPERAND_PUNCT_VALID_P: Instruction Output. (line 117)
+* probe_stack instruction pattern: Standard Names. (line 1450)
+* probe_stack_address instruction pattern: Standard Names. (line 1443)
* processor functional units: Processor pipeline description.
(line 6)
-* processor functional units <1>: Processor pipeline description.
- (line 68)
* processor pipeline description: Processor pipeline description.
(line 6)
-* product: Arithmetic. (line 93)
+* product: Arithmetic. (line 92)
* profile feedback: Profile information.
(line 14)
* profile representation: Profile information.
(line 6)
-* PROFILE_BEFORE_PROLOGUE: Profiling. (line 34)
-* PROFILE_HOOK: Profiling. (line 22)
+* PROFILE_BEFORE_PROLOGUE: Profiling. (line 35)
+* PROFILE_HOOK: Profiling. (line 23)
* profiling, code generation: Profiling. (line 6)
-* program counter: Regs and Memory. (line 358)
+* program counter: Regs and Memory. (line 362)
* prologue: Function Entry. (line 6)
-* 'prologue' instruction pattern: Standard Names. (line 1531)
-* PROMOTE_MODE: Storage Layout. (line 87)
+* prologue instruction pattern: Standard Names. (line 1541)
+* PROMOTE_MODE: Storage Layout. (line 88)
* pseudo registers: Regs and Memory. (line 9)
* PSImode: Machine Modes. (line 32)
-* PTRDIFF_TYPE: Type Layout. (line 163)
-* purge_dead_edges: Edges. (line 103)
+* PTRDIFF_TYPE: Type Layout. (line 164)
* purge_dead_edges <1>: Maintaining the CFG.
- (line 81)
-* push address instruction: Simple Constraints. (line 162)
-* 'pushM1' instruction pattern: Standard Names. (line 253)
-* PUSH_ARGS: Stack Arguments. (line 17)
-* PUSH_ARGS_REVERSED: Stack Arguments. (line 25)
+ (line 82)
+* purge_dead_edges: Edges. (line 104)
+* push address instruction: Simple Constraints. (line 164)
+* PUSH_ARGS: Stack Arguments. (line 18)
+* PUSH_ARGS_REVERSED: Stack Arguments. (line 26)
* push_operand: Machine-Independent Predicates.
- (line 80)
-* push_reload: Addressing Modes. (line 176)
-* PUSH_ROUNDING: Stack Arguments. (line 31)
+ (line 81)
+* push_reload: Addressing Modes. (line 177)
+* PUSH_ROUNDING: Stack Arguments. (line 32)
+* pushM1 instruction pattern: Standard Names. (line 256)
* PUT_CODE: RTL Objects. (line 47)
-* PUT_MODE: Machine Modes. (line 294)
-* PUT_REG_NOTE_KIND: Insns. (line 346)
-* PUT_SDB_: SDB and DWARF. (line 109)
-* QCmode: Machine Modes. (line 199)
+* PUT_MODE: Machine Modes. (line 295)
+* PUT_REG_NOTE_KIND: Insns. (line 352)
+* PUT_SDB_: SDB and DWARF. (line 110)
+* QCmode: Machine Modes. (line 200)
* QFmode: Machine Modes. (line 57)
* QImode: Machine Modes. (line 25)
-* 'QImode', in 'insn': Insns. (line 268)
+* QImode, in insn: Insns. (line 272)
* QQmode: Machine Modes. (line 106)
-* qualified type: Types. (line 6)
* qualified type <1>: Types for C++. (line 6)
+* qualified type: Types. (line 6)
* querying function unit reservations: Processor pipeline description.
(line 90)
* question mark: Multi-Alternative. (line 41)
-* quotient: Arithmetic. (line 116)
-* 'r' in constraint: Simple Constraints. (line 64)
+* quotient: Arithmetic. (line 115)
+* r in constraint: Simple Constraints. (line 66)
* RDIV_EXPR: Unary and Binary Expressions.
(line 6)
-* READONLY_DATA_SECTION_ASM_OP: Sections. (line 62)
+* READONLY_DATA_SECTION_ASM_OP: Sections. (line 63)
* real operands: SSA Operands. (line 6)
-* REALPART_EXPR: Unary and Binary Expressions.
- (line 6)
-* REAL_ARITHMETIC: Floating Point. (line 64)
+* REAL_ARITHMETIC: Floating Point. (line 66)
* REAL_CST: Constant expressions.
(line 6)
-* REAL_LIBGCC_SPEC: Driver. (line 124)
+* REAL_LIBGCC_SPEC: Driver. (line 125)
* REAL_NM_FILE_NAME: Macros for Initialization.
- (line 105)
+ (line 106)
* REAL_TYPE: Types. (line 6)
-* REAL_VALUES_EQUAL: Floating Point. (line 31)
-* REAL_VALUES_LESS: Floating Point. (line 37)
-* REAL_VALUE_ABS: Floating Point. (line 81)
-* REAL_VALUE_ATOF: Floating Point. (line 48)
-* REAL_VALUE_FIX: Floating Point. (line 40)
-* REAL_VALUE_ISINF: Floating Point. (line 58)
-* REAL_VALUE_ISNAN: Floating Point. (line 61)
-* REAL_VALUE_NEGATE: Floating Point. (line 78)
-* REAL_VALUE_NEGATIVE: Floating Point. (line 55)
-* REAL_VALUE_TO_TARGET_DECIMAL128: Data Output. (line 147)
-* REAL_VALUE_TO_TARGET_DECIMAL32: Data Output. (line 145)
-* REAL_VALUE_TO_TARGET_DECIMAL64: Data Output. (line 146)
-* REAL_VALUE_TO_TARGET_DOUBLE: Data Output. (line 143)
-* REAL_VALUE_TO_TARGET_LONG_DOUBLE: Data Output. (line 144)
-* REAL_VALUE_TO_TARGET_SINGLE: Data Output. (line 142)
-* REAL_VALUE_TYPE: Floating Point. (line 25)
-* REAL_VALUE_UNSIGNED_FIX: Floating Point. (line 43)
-* recognizing insns: RTL Template. (line 6)
+* REAL_VALUE_ABS: Floating Point. (line 82)
+* REAL_VALUE_ATOF: Floating Point. (line 50)
+* REAL_VALUE_FIX: Floating Point. (line 41)
+* REAL_VALUE_ISINF: Floating Point. (line 59)
+* REAL_VALUE_ISNAN: Floating Point. (line 62)
+* REAL_VALUE_NEGATE: Floating Point. (line 79)
+* REAL_VALUE_NEGATIVE: Floating Point. (line 56)
+* REAL_VALUE_TO_TARGET_DECIMAL128: Data Output. (line 149)
+* REAL_VALUE_TO_TARGET_DECIMAL32: Data Output. (line 147)
+* REAL_VALUE_TO_TARGET_DECIMAL64: Data Output. (line 148)
+* REAL_VALUE_TO_TARGET_DOUBLE: Data Output. (line 145)
+* REAL_VALUE_TO_TARGET_LONG_DOUBLE: Data Output. (line 146)
+* REAL_VALUE_TO_TARGET_SINGLE: Data Output. (line 144)
+* REAL_VALUE_TYPE: Floating Point. (line 26)
+* REAL_VALUE_UNSIGNED_FIX: Floating Point. (line 45)
+* REAL_VALUES_EQUAL: Floating Point. (line 32)
+* REAL_VALUES_LESS: Floating Point. (line 38)
+* REALPART_EXPR: Unary and Binary Expressions.
+ (line 6)
* recog_data.operand: Instruction Output. (line 54)
-* RECORD_TYPE: Types. (line 6)
+* recognizing insns: RTL Template. (line 6)
* RECORD_TYPE <1>: Classes. (line 6)
+* RECORD_TYPE: Types. (line 6)
* redirect_edge_and_branch: Profile information.
(line 71)
* redirect_edge_and_branch, redirect_jump: Maintaining the CFG.
- (line 90)
-* 'reduc_plus_scal_M' instruction pattern: Standard Names. (line 350)
-* 'reduc_smax_M' instruction pattern: Standard Names. (line 317)
-* 'reduc_smax_scal_M' instruction pattern: Standard Names. (line 340)
-* 'reduc_smin_M' instruction pattern: Standard Names. (line 317)
-* 'reduc_smin_scal_M' instruction pattern: Standard Names. (line 340)
-* 'reduc_splus_M' instruction pattern: Standard Names. (line 333)
-* 'reduc_umax_M' instruction pattern: Standard Names. (line 325)
-* 'reduc_umax_scal_M' instruction pattern: Standard Names. (line 345)
-* 'reduc_umin_M' instruction pattern: Standard Names. (line 325)
-* 'reduc_umin_scal_M' instruction pattern: Standard Names. (line 345)
-* 'reduc_uplus_M' instruction pattern: Standard Names. (line 333)
+ (line 92)
+* reduc_plus_scal_M instruction pattern: Standard Names. (line 353)
+* reduc_smax_M instruction pattern: Standard Names. (line 320)
+* reduc_smax_scal_M instruction pattern: Standard Names. (line 343)
+* reduc_smin_M instruction pattern: Standard Names. (line 320)
+* reduc_smin_scal_M instruction pattern: Standard Names. (line 343)
+* reduc_splus_M instruction pattern: Standard Names. (line 336)
+* reduc_umax_M instruction pattern: Standard Names. (line 328)
+* reduc_umax_scal_M instruction pattern: Standard Names. (line 348)
+* reduc_umin_M instruction pattern: Standard Names. (line 328)
+* reduc_umin_scal_M instruction pattern: Standard Names. (line 348)
+* reduc_uplus_M instruction pattern: Standard Names. (line 336)
* reference: Types. (line 6)
* REFERENCE_TYPE: Types. (line 6)
* reg: Regs and Memory. (line 9)
-* 'reg' and '/f': Flags. (line 94)
-* 'reg' and '/i': Flags. (line 89)
-* 'reg' and '/v': Flags. (line 98)
-* 'reg', RTL sharing: Sharing. (line 17)
-* register allocation order: Allocation Order. (line 6)
-* register class definitions: Register Classes. (line 6)
-* register class preference constraints: Class Preferences. (line 6)
-* register pairs: Values in Registers.
- (line 69)
-* Register Transfer Language (RTL): RTL. (line 6)
-* register usage: Registers. (line 6)
-* registers arguments: Register Arguments. (line 6)
-* registers in constraints: Simple Constraints. (line 64)
-* REGISTER_MOVE_COST: Costs. (line 9)
-* REGISTER_NAMES: Instruction Output. (line 8)
-* register_operand: Machine-Independent Predicates.
- (line 29)
-* REGISTER_PREFIX: Instruction Output. (line 150)
-* REGISTER_TARGET_PRAGMAS: Misc. (line 387)
-* REGMODE_NATURAL_SIZE: Values in Registers.
- (line 49)
-* REGNO_MODE_CODE_OK_FOR_BASE_P: Register Classes. (line 172)
-* REGNO_MODE_OK_FOR_BASE_P: Register Classes. (line 150)
-* REGNO_MODE_OK_FOR_REG_BASE_P: Register Classes. (line 160)
-* REGNO_OK_FOR_BASE_P: Register Classes. (line 146)
-* REGNO_OK_FOR_INDEX_P: Register Classes. (line 186)
-* REGNO_REG_CLASS: Register Classes. (line 105)
-* regs_ever_live: Function Entry. (line 21)
-* regular expressions: Processor pipeline description.
- (line 6)
-* regular expressions <1>: Processor pipeline description.
- (line 105)
-* REG_ALLOC_ORDER: Allocation Order. (line 8)
-* REG_BR_PRED: Insns. (line 526)
-* REG_BR_PROB: Insns. (line 519)
+* reg and /f: Flags. (line 94)
+* reg and /i: Flags. (line 89)
+* reg and /v: Flags. (line 98)
+* reg, RTL sharing: Sharing. (line 17)
+* REG_ALLOC_ORDER: Allocation Order. (line 9)
+* REG_BR_PRED: Insns. (line 534)
+* REG_BR_PROB: Insns. (line 527)
* REG_BR_PROB_BASE, BB_FREQ_BASE, count: Profile information.
(line 82)
* REG_BR_PROB_BASE, EDGE_FREQUENCY: Profile information.
(line 52)
-* REG_CC_SETTER: Insns. (line 491)
-* REG_CC_USER: Insns. (line 491)
+* REG_CC_SETTER: Insns. (line 498)
+* REG_CC_USER: Insns. (line 498)
+* REG_CLASS_CONTENTS: Register Classes. (line 93)
* reg_class_contents: Register Basics. (line 59)
-* REG_CLASS_CONTENTS: Register Classes. (line 91)
* reg_class_for_constraint: C Constraint Interface.
- (line 48)
-* REG_CLASS_NAMES: Register Classes. (line 86)
-* REG_CROSSING_JUMP: Insns. (line 405)
-* REG_DEAD: Insns. (line 357)
+ (line 50)
+* REG_CLASS_NAMES: Register Classes. (line 88)
+* REG_CROSSING_JUMP: Insns. (line 411)
+* REG_DEAD: Insns. (line 363)
* REG_DEAD, REG_UNUSED: Liveness information.
(line 32)
-* REG_DEP_ANTI: Insns. (line 513)
-* REG_DEP_OUTPUT: Insns. (line 509)
-* REG_DEP_TRUE: Insns. (line 506)
-* REG_EH_REGION, EDGE_ABNORMAL_CALL: Edges. (line 109)
-* REG_EQUAL: Insns. (line 420)
-* REG_EQUIV: Insns. (line 420)
-* REG_EXPR: Special Accessors. (line 58)
-* REG_FRAME_RELATED_EXPR: Insns. (line 532)
+* REG_DEP_ANTI: Insns. (line 520)
+* REG_DEP_OUTPUT: Insns. (line 516)
+* REG_DEP_TRUE: Insns. (line 513)
+* REG_EH_REGION, EDGE_ABNORMAL_CALL: Edges. (line 110)
+* REG_EQUAL: Insns. (line 426)
+* REG_EQUIV: Insns. (line 426)
+* REG_EXPR: Special Accessors. (line 60)
+* REG_FRAME_RELATED_EXPR: Insns. (line 540)
* REG_FUNCTION_VALUE_P: Flags. (line 89)
-* REG_INC: Insns. (line 373)
-* 'reg_label' and '/v': Flags. (line 65)
-* REG_LABEL_OPERAND: Insns. (line 387)
-* REG_LABEL_TARGET: Insns. (line 396)
+* REG_INC: Insns. (line 379)
+* reg_label and /v: Flags. (line 65)
+* REG_LABEL_OPERAND: Insns. (line 393)
+* REG_LABEL_TARGET: Insns. (line 402)
+* reg_names <1>: Instruction Output. (line 108)
* reg_names: Register Basics. (line 59)
-* reg_names <1>: Instruction Output. (line 107)
-* REG_NONNEG: Insns. (line 379)
-* REG_NOTES: Insns. (line 321)
-* REG_NOTE_KIND: Insns. (line 346)
-* REG_OFFSET: Special Accessors. (line 62)
-* REG_OK_STRICT: Addressing Modes. (line 99)
-* REG_PARM_STACK_SPACE: Stack Arguments. (line 58)
-* 'REG_PARM_STACK_SPACE', and 'TARGET_FUNCTION_ARG': Register Arguments.
- (line 56)
+* REG_NONNEG: Insns. (line 385)
+* REG_NOTE_KIND: Insns. (line 352)
+* REG_NOTES: Insns. (line 325)
+* REG_OFFSET: Special Accessors. (line 64)
+* REG_OK_STRICT: Addressing Modes. (line 100)
+* REG_PARM_STACK_SPACE: Stack Arguments. (line 59)
+* REG_PARM_STACK_SPACE, and TARGET_FUNCTION_ARG: Register Arguments.
+ (line 57)
* REG_POINTER: Flags. (line 94)
-* REG_SETJMP: Insns. (line 414)
-* REG_UNUSED: Insns. (line 366)
+* REG_SETJMP: Insns. (line 420)
+* REG_UNUSED: Insns. (line 372)
* REG_USERVAR_P: Flags. (line 98)
-* REG_VALUE_IN_UNWIND_CONTEXT: Frame Registers. (line 158)
-* REG_WORDS_BIG_ENDIAN: Storage Layout. (line 35)
+* REG_VALUE_IN_UNWIND_CONTEXT: Frame Registers. (line 157)
+* REG_WORDS_BIG_ENDIAN: Storage Layout. (line 36)
+* register allocation order: Allocation Order. (line 6)
+* register class definitions: Register Classes. (line 6)
+* register class preference constraints: Class Preferences. (line 6)
+* register pairs: Values in Registers.
+ (line 69)
+* Register Transfer Language (RTL): RTL. (line 6)
+* register usage: Registers. (line 6)
+* REGISTER_MOVE_COST: Costs. (line 10)
+* REGISTER_NAMES: Instruction Output. (line 9)
+* register_operand: Machine-Independent Predicates.
+ (line 30)
+* REGISTER_PREFIX: Instruction Output. (line 152)
+* REGISTER_TARGET_PRAGMAS: Misc. (line 388)
+* registers arguments: Register Arguments. (line 6)
+* registers in constraints: Simple Constraints. (line 66)
+* REGMODE_NATURAL_SIZE: Values in Registers.
+ (line 50)
+* REGNO_MODE_CODE_OK_FOR_BASE_P: Register Classes. (line 176)
+* REGNO_MODE_OK_FOR_BASE_P: Register Classes. (line 153)
+* REGNO_MODE_OK_FOR_REG_BASE_P: Register Classes. (line 163)
+* REGNO_OK_FOR_BASE_P: Register Classes. (line 149)
+* REGNO_OK_FOR_INDEX_P: Register Classes. (line 190)
+* REGNO_REG_CLASS: Register Classes. (line 108)
+* regs_ever_live: Function Entry. (line 21)
+* regular expressions: Processor pipeline description.
+ (line 6)
* relative costs: Costs. (line 6)
-* RELATIVE_PREFIX_NOT_LINKDIR: Driver. (line 262)
-* reloading: RTL passes. (line 170)
-* reload_completed: Standard Names. (line 1230)
-* 'reload_in' instruction pattern: Standard Names. (line 98)
+* RELATIVE_PREFIX_NOT_LINKDIR: Driver. (line 263)
+* reload_completed: Standard Names. (line 1236)
+* reload_in instruction pattern: Standard Names. (line 99)
* reload_in_progress: Standard Names. (line 57)
-* 'reload_out' instruction pattern: Standard Names. (line 98)
-* remainder: Arithmetic. (line 136)
-* 'remainderM3' instruction pattern: Standard Names. (line 584)
-* reorder: GTY Options. (line 182)
+* reload_out instruction pattern: Standard Names. (line 99)
+* reloading: RTL passes. (line 171)
+* remainder: Arithmetic. (line 135)
+* remainderM3 instruction pattern: Standard Names. (line 589)
+* reorder: GTY Options. (line 176)
* representation of RTL: RTL. (line 6)
* reservation delays: Processor pipeline description.
(line 6)
-* 'restore_stack_block' instruction pattern: Standard Names. (line 1356)
-* 'restore_stack_function' instruction pattern: Standard Names.
- (line 1356)
-* 'restore_stack_nonlocal' instruction pattern: Standard Names.
- (line 1356)
-* rest_of_decl_compilation: Parsing pass. (line 51)
-* rest_of_type_compilation: Parsing pass. (line 51)
+* rest_of_decl_compilation: Parsing pass. (line 52)
+* rest_of_type_compilation: Parsing pass. (line 52)
+* restore_stack_block instruction pattern: Standard Names. (line 1363)
+* restore_stack_function instruction pattern: Standard Names.
+ (line 1363)
+* restore_stack_nonlocal instruction pattern: Standard Names.
+ (line 1363)
* RESULT_DECL: Declarations. (line 6)
* return: Side Effects. (line 72)
-* 'return' instruction pattern: Standard Names. (line 1204)
+* return instruction pattern: Standard Names. (line 1209)
* return values in registers: Scalar Return. (line 6)
-* returning aggregate values: Aggregate Return. (line 6)
-* returning structures and unions: Interface. (line 10)
-* RETURN_ADDRESS_POINTER_REGNUM: Frame Registers. (line 64)
-* RETURN_ADDR_IN_PREVIOUS_FRAME: Frame Layout. (line 133)
-* RETURN_ADDR_OFFSET: Exception Handling. (line 59)
-* RETURN_ADDR_RTX: Frame Layout. (line 122)
+* RETURN_ADDR_IN_PREVIOUS_FRAME: Frame Layout. (line 135)
+* RETURN_ADDR_OFFSET: Exception Handling. (line 60)
+* RETURN_ADDR_RTX: Frame Layout. (line 124)
+* RETURN_ADDRESS_POINTER_REGNUM: Frame Registers. (line 65)
* RETURN_EXPR: Statements for C++. (line 6)
* RETURN_STMT: Statements for C++. (line 6)
* return_val: Flags. (line 274)
-* 'return_val', in 'call_insn': Flags. (line 24)
-* 'return_val', in 'reg': Flags. (line 89)
-* 'return_val', in 'symbol_ref': Flags. (line 202)
+* return_val, in call_insn: Flags. (line 24)
+* return_val, in reg: Flags. (line 89)
+* return_val, in symbol_ref: Flags. (line 202)
+* returning aggregate values: Aggregate Return. (line 6)
+* returning structures and unions: Interface. (line 10)
* reverse probability: Profile information.
(line 66)
* REVERSE_CONDITION: MODE_CC Condition Codes.
- (line 92)
+ (line 93)
* REVERSIBLE_CC_MODE: MODE_CC Condition Codes.
- (line 77)
-* right rotate: Arithmetic. (line 195)
-* right shift: Arithmetic. (line 190)
-* 'rintM2' instruction pattern: Standard Names. (line 697)
+ (line 78)
+* right rotate: Arithmetic. (line 194)
+* right shift: Arithmetic. (line 189)
+* rintM2 instruction pattern: Standard Names. (line 702)
* RISC: Processor pipeline description.
(line 6)
-* RISC <1>: Processor pipeline description.
- (line 223)
* roots, marking: GGC Roots. (line 6)
-* rotate: Arithmetic. (line 195)
-* rotate <1>: Arithmetic. (line 195)
-* rotatert: Arithmetic. (line 195)
-* 'rotlM3' instruction pattern: Standard Names. (line 549)
-* 'rotrM3' instruction pattern: Standard Names. (line 549)
-* 'roundM2' instruction pattern: Standard Names. (line 673)
+* rotate: Arithmetic. (line 194)
+* rotatert: Arithmetic. (line 194)
+* rotlM3 instruction pattern: Standard Names. (line 554)
+* rotrM3 instruction pattern: Standard Names. (line 554)
* ROUND_DIV_EXPR: Unary and Binary Expressions.
(line 6)
* ROUND_MOD_EXPR: Unary and Binary Expressions.
(line 6)
-* ROUND_TYPE_ALIGN: Storage Layout. (line 427)
+* ROUND_TYPE_ALIGN: Storage Layout. (line 432)
+* roundM2 instruction pattern: Standard Names. (line 678)
* RSHIFT_EXPR: Unary and Binary Expressions.
(line 6)
* RTL addition: Arithmetic. (line 14)
* RTL addition with signed saturation: Arithmetic. (line 14)
* RTL addition with unsigned saturation: Arithmetic. (line 14)
* RTL classes: RTL Classes. (line 6)
-* RTL comparison: Arithmetic. (line 46)
+* RTL comparison: Arithmetic. (line 43)
* RTL comparison operations: Comparisons. (line 6)
* RTL constant expression types: Constants. (line 6)
* RTL constants: Constants. (line 6)
* RTL declarations: RTL Declarations. (line 6)
-* RTL difference: Arithmetic. (line 38)
+* RTL difference: Arithmetic. (line 36)
* RTL expression: RTL Objects. (line 6)
* RTL expressions for arithmetic: Arithmetic. (line 6)
* RTL format: RTL Classes. (line 72)
@@ -49515,9 +49904,9 @@ Concept Index
* RTL side effect expressions: Side Effects. (line 6)
* RTL strings: RTL Objects. (line 6)
* RTL structure sharing assumptions: Sharing. (line 6)
-* RTL subtraction: Arithmetic. (line 38)
-* RTL subtraction with signed saturation: Arithmetic. (line 38)
-* RTL subtraction with unsigned saturation: Arithmetic. (line 38)
+* RTL subtraction: Arithmetic. (line 36)
+* RTL subtraction with signed saturation: Arithmetic. (line 36)
+* RTL subtraction with unsigned saturation: Arithmetic. (line 36)
* RTL sum: Arithmetic. (line 14)
* RTL vectors: RTL Objects. (line 6)
* RTL_CONST_CALL_P: Flags. (line 19)
@@ -49529,833 +49918,829 @@ Concept Index
* RTX_FRAME_RELATED_P: Flags. (line 107)
* run-time conventions: Interface. (line 6)
* run-time target specification: Run-time Target. (line 6)
-* 's' in constraint: Simple Constraints. (line 100)
+* s in constraint: Simple Constraints. (line 102)
* SAD_EXPR: Vectors. (line 6)
-* same_type_p: Types. (line 86)
-* SAmode: Machine Modes. (line 150)
-* 'satfractMN2' instruction pattern: Standard Names. (line 969)
-* 'satfractunsMN2' instruction pattern: Standard Names. (line 982)
-* satisfies_constraint_: C Constraint Interface.
- (line 36)
+* same_type_p: Types. (line 88)
+* SAmode: Machine Modes. (line 151)
* sat_fract: Conversions. (line 90)
+* satfractMN2 instruction pattern: Standard Names. (line 974)
+* satfractunsMN2 instruction pattern: Standard Names. (line 987)
+* satisfies_constraint_: C Constraint Interface.
+ (line 37)
* SAVE_EXPR: Unary and Binary Expressions.
(line 6)
-* 'save_stack_block' instruction pattern: Standard Names. (line 1356)
-* 'save_stack_function' instruction pattern: Standard Names. (line 1356)
-* 'save_stack_nonlocal' instruction pattern: Standard Names. (line 1356)
-* SBSS_SECTION_ASM_OP: Sections. (line 75)
+* save_stack_block instruction pattern: Standard Names. (line 1363)
+* save_stack_function instruction pattern: Standard Names. (line 1363)
+* save_stack_nonlocal instruction pattern: Standard Names. (line 1363)
+* SBSS_SECTION_ASM_OP: Sections. (line 76)
* Scalar evolutions: Scalar evolutions. (line 6)
* scalars, returned as values: Scalar Return. (line 6)
* SCHED_GROUP_P: Flags. (line 148)
-* SCmode: Machine Modes. (line 199)
-* scratch: Regs and Memory. (line 294)
-* scratch operands: Regs and Memory. (line 294)
-* 'scratch', RTL sharing: Sharing. (line 35)
+* SCmode: Machine Modes. (line 200)
+* scratch: Regs and Memory. (line 298)
+* scratch operands: Regs and Memory. (line 298)
+* scratch, RTL sharing: Sharing. (line 35)
* scratch_operand: Machine-Independent Predicates.
- (line 49)
-* SDATA_SECTION_ASM_OP: Sections. (line 57)
-* SDB_ALLOW_FORWARD_REFERENCES: SDB and DWARF. (line 127)
-* SDB_ALLOW_UNKNOWN_REFERENCES: SDB and DWARF. (line 122)
-* SDB_DEBUGGING_INFO: SDB and DWARF. (line 8)
-* SDB_DELIM: SDB and DWARF. (line 115)
-* SDB_OUTPUT_SOURCE_LINE: SDB and DWARF. (line 132)
+ (line 50)
+* SDATA_SECTION_ASM_OP: Sections. (line 58)
+* SDB_ALLOW_FORWARD_REFERENCES: SDB and DWARF. (line 128)
+* SDB_ALLOW_UNKNOWN_REFERENCES: SDB and DWARF. (line 123)
+* SDB_DEBUGGING_INFO: SDB and DWARF. (line 9)
+* SDB_DELIM: SDB and DWARF. (line 116)
+* SDB_OUTPUT_SOURCE_LINE: SDB and DWARF. (line 133)
* SDmode: Machine Modes. (line 88)
-* 'sdot_prodM' instruction pattern: Standard Names. (line 355)
-* search options: Including Patterns. (line 47)
-* SECONDARY_INPUT_RELOAD_CLASS: Register Classes. (line 391)
-* SECONDARY_MEMORY_NEEDED: Register Classes. (line 447)
-* SECONDARY_MEMORY_NEEDED_MODE: Register Classes. (line 466)
-* SECONDARY_MEMORY_NEEDED_RTX: Register Classes. (line 457)
-* SECONDARY_OUTPUT_RELOAD_CLASS: Register Classes. (line 392)
-* SECONDARY_RELOAD_CLASS: Register Classes. (line 390)
+* sdot_prodM instruction pattern: Standard Names. (line 358)
+* search options: Including Patterns. (line 44)
+* SECONDARY_INPUT_RELOAD_CLASS: Register Classes. (line 396)
+* SECONDARY_MEMORY_NEEDED: Register Classes. (line 452)
+* SECONDARY_MEMORY_NEEDED_MODE: Register Classes. (line 471)
+* SECONDARY_MEMORY_NEEDED_RTX: Register Classes. (line 462)
+* SECONDARY_OUTPUT_RELOAD_CLASS: Register Classes. (line 397)
+* SECONDARY_RELOAD_CLASS: Register Classes. (line 395)
* SELECT_CC_MODE: MODE_CC Condition Codes.
- (line 6)
-* sequence: Side Effects. (line 258)
+ (line 7)
+* sequence: Side Effects. (line 260)
* Sequence iterators: Sequence iterators. (line 6)
* set: Side Effects. (line 15)
-* 'set' and '/f': Flags. (line 107)
-* 'setmemM' instruction pattern: Standard Names. (line 833)
-* SETUP_FRAME_ADDRESSES: Frame Layout. (line 100)
-* SET_ASM_OP: Label Output. (line 423)
-* SET_ASM_OP <1>: Label Output. (line 434)
+* set and /f: Flags. (line 107)
+* SET_ASM_OP: Label Output. (line 426)
* set_attr: Tagging Insns. (line 31)
* set_attr_alternative: Tagging Insns. (line 49)
-* set_bb_seq: GIMPLE sequences. (line 75)
+* set_bb_seq: GIMPLE sequences. (line 76)
* SET_DEST: Side Effects. (line 69)
* SET_IS_RETURN_P: Flags. (line 157)
* SET_LABEL_KIND: Insns. (line 146)
* set_optab_libfunc: Library Calls. (line 15)
-* SET_RATIO: Costs. (line 216)
+* SET_RATIO: Costs. (line 217)
* SET_SRC: Side Effects. (line 69)
-* 'set_thread_pointerMODE' instruction pattern: Standard Names.
- (line 1887)
+* set_thread_pointerMODE instruction pattern: Standard Names.
+ (line 1897)
* SET_TYPE_STRUCTURAL_EQUALITY: Types. (line 6)
-* SET_TYPE_STRUCTURAL_EQUALITY <1>: Types. (line 81)
+* setmemM instruction pattern: Standard Names. (line 838)
+* SETUP_FRAME_ADDRESSES: Frame Layout. (line 102)
* SFmode: Machine Modes. (line 69)
* sharing of RTL components: Sharing. (line 6)
-* shift: Arithmetic. (line 173)
-* SHIFT_COUNT_TRUNCATED: Misc. (line 112)
+* shift: Arithmetic. (line 172)
+* SHIFT_COUNT_TRUNCATED: Misc. (line 113)
* SHLIB_SUFFIX: Macros for Initialization.
- (line 133)
-* SHORT_ACCUM_TYPE_SIZE: Type Layout. (line 82)
-* SHORT_FRACT_TYPE_SIZE: Type Layout. (line 62)
-* SHORT_IMMEDIATES_SIGN_EXTEND: Misc. (line 86)
-* SHORT_TYPE_SIZE: Type Layout. (line 15)
-* 'sibcall_epilogue' instruction pattern: Standard Names. (line 1563)
-* sibling call: Edges. (line 121)
+ (line 135)
+* SHORT_ACCUM_TYPE_SIZE: Type Layout. (line 83)
+* SHORT_FRACT_TYPE_SIZE: Type Layout. (line 63)
+* SHORT_IMMEDIATES_SIGN_EXTEND: Misc. (line 87)
+* SHORT_TYPE_SIZE: Type Layout. (line 16)
+* sibcall_epilogue instruction pattern: Standard Names. (line 1573)
+* sibling call: Edges. (line 122)
* SIBLING_CALL_P: Flags. (line 161)
-* signed division: Arithmetic. (line 116)
-* signed division with signed saturation: Arithmetic. (line 116)
-* signed maximum: Arithmetic. (line 141)
-* signed minimum: Arithmetic. (line 141)
+* SIG_ATOMIC_TYPE: Type Layout. (line 215)
* sign_extend: Conversions. (line 23)
* sign_extract: Bit-Fields. (line 8)
-* 'sign_extract', canonicalization of: Insn Canonicalizations.
- (line 87)
-* SIG_ATOMIC_TYPE: Type Layout. (line 214)
+* sign_extract, canonicalization of: Insn Canonicalizations.
+ (line 88)
+* signed division: Arithmetic. (line 115)
+* signed division with signed saturation: Arithmetic. (line 115)
+* signed maximum: Arithmetic. (line 140)
+* signed minimum: Arithmetic. (line 140)
* SImode: Machine Modes. (line 37)
* simple constraints: Simple Constraints. (line 6)
* simple_return: Side Effects. (line 86)
-* 'simple_return' instruction pattern: Standard Names. (line 1219)
-* 'sincosM3' instruction pattern: Standard Names. (line 609)
-* 'sinM2' instruction pattern: Standard Names. (line 601)
-* SIZETYPE: Type Layout. (line 153)
-* SIZE_ASM_OP: Label Output. (line 33)
-* SIZE_TYPE: Type Layout. (line 137)
-* skip: GTY Options. (line 76)
-* SLOW_BYTE_ACCESS: Costs. (line 117)
-* SLOW_UNALIGNED_ACCESS: Costs. (line 132)
-* smax: Arithmetic. (line 141)
-* smin: Arithmetic. (line 141)
-* sms, swing, software pipelining: RTL passes. (line 123)
-* 'smulM3_highpart' instruction pattern: Standard Names. (line 464)
+* simple_return instruction pattern: Standard Names. (line 1225)
+* sincosM3 instruction pattern: Standard Names. (line 614)
+* sinM2 instruction pattern: Standard Names. (line 606)
+* SIZE_ASM_OP: Label Output. (line 35)
+* SIZE_TYPE: Type Layout. (line 138)
+* SIZETYPE: Type Layout. (line 154)
+* skip: GTY Options. (line 77)
+* SLOW_BYTE_ACCESS: Costs. (line 118)
+* SLOW_UNALIGNED_ACCESS: Costs. (line 133)
+* smax: Arithmetic. (line 140)
+* smin: Arithmetic. (line 140)
+* sms, swing, software pipelining: RTL passes. (line 124)
+* smulM3_highpart instruction pattern: Standard Names. (line 469)
* soft float library: Soft float library routines.
(line 6)
-* special: GTY Options. (line 244)
+* special: GTY Options. (line 237)
* special predicates: Predicates. (line 31)
* SPECS: Target Fragment. (line 191)
* speed of instructions: Costs. (line 6)
-* splitting instructions: Insn Splitting. (line 6)
* split_block: Maintaining the CFG.
- (line 97)
+ (line 99)
+* splitting instructions: Insn Splitting. (line 6)
* SQmode: Machine Modes. (line 114)
* sqrt: Arithmetic. (line 206)
-* 'sqrtM2' instruction pattern: Standard Names. (line 567)
+* sqrtM2 instruction pattern: Standard Names. (line 572)
* square root: Arithmetic. (line 206)
-* SSA: SSA. (line 6)
-* 'ssaddM3' instruction pattern: Standard Names. (line 276)
-* 'ssadM' instruction pattern: Standard Names. (line 364)
-* 'ssashlM3' instruction pattern: Standard Names. (line 539)
-* SSA_NAME_DEF_STMT: SSA. (line 216)
-* SSA_NAME_VERSION: SSA. (line 221)
-* 'ssdivM3' instruction pattern: Standard Names. (line 276)
-* 'ssmaddMN4' instruction pattern: Standard Names. (line 487)
-* 'ssmsubMN4' instruction pattern: Standard Names. (line 511)
-* 'ssmulM3' instruction pattern: Standard Names. (line 276)
-* 'ssnegM2' instruction pattern: Standard Names. (line 561)
-* 'sssubM3' instruction pattern: Standard Names. (line 276)
-* 'ssum_widenM3' instruction pattern: Standard Names. (line 373)
-* ss_abs: Arithmetic. (line 200)
-* ss_ashift: Arithmetic. (line 173)
-* ss_div: Arithmetic. (line 116)
-* ss_minus: Arithmetic. (line 38)
-* ss_mult: Arithmetic. (line 93)
-* ss_neg: Arithmetic. (line 82)
+* ss_abs: Arithmetic. (line 199)
+* ss_ashift: Arithmetic. (line 172)
+* ss_div: Arithmetic. (line 115)
+* ss_minus: Arithmetic. (line 36)
+* ss_mult: Arithmetic. (line 92)
+* ss_neg: Arithmetic. (line 81)
* ss_plus: Arithmetic. (line 14)
* ss_truncate: Conversions. (line 43)
+* SSA: SSA. (line 6)
+* SSA_NAME_DEF_STMT: SSA. (line 217)
+* SSA_NAME_VERSION: SSA. (line 222)
+* ssaddM3 instruction pattern: Standard Names. (line 279)
+* ssadM instruction pattern: Standard Names. (line 367)
+* ssashlM3 instruction pattern: Standard Names. (line 544)
+* ssdivM3 instruction pattern: Standard Names. (line 279)
+* ssmaddMN4 instruction pattern: Standard Names. (line 492)
+* ssmsubMN4 instruction pattern: Standard Names. (line 516)
+* ssmulM3 instruction pattern: Standard Names. (line 279)
+* ssnegM2 instruction pattern: Standard Names. (line 566)
+* sssubM3 instruction pattern: Standard Names. (line 279)
+* ssum_widenM3 instruction pattern: Standard Names. (line 377)
* stack arguments: Stack Arguments. (line 6)
* stack frame layout: Frame Layout. (line 6)
* stack smashing protection: Stack Smashing Protection.
(line 6)
-* STACK_ALIGNMENT_NEEDED: Frame Layout. (line 47)
-* STACK_BOUNDARY: Storage Layout. (line 139)
-* STACK_CHECK_BUILTIN: Stack Checking. (line 31)
-* STACK_CHECK_FIXED_FRAME_SIZE: Stack Checking. (line 82)
-* STACK_CHECK_MAX_FRAME_SIZE: Stack Checking. (line 73)
-* STACK_CHECK_MAX_VAR_SIZE: Stack Checking. (line 89)
-* STACK_CHECK_MOVING_SP: Stack Checking. (line 53)
-* STACK_CHECK_PROBE_INTERVAL_EXP: Stack Checking. (line 45)
-* STACK_CHECK_PROTECT: Stack Checking. (line 62)
-* STACK_CHECK_STATIC_BUILTIN: Stack Checking. (line 38)
-* STACK_DYNAMIC_OFFSET: Frame Layout. (line 73)
-* 'STACK_DYNAMIC_OFFSET' and virtual registers: Regs and Memory.
+* STACK_ALIGNMENT_NEEDED: Frame Layout. (line 48)
+* STACK_BOUNDARY: Storage Layout. (line 141)
+* STACK_CHECK_BUILTIN: Stack Checking. (line 32)
+* STACK_CHECK_FIXED_FRAME_SIZE: Stack Checking. (line 83)
+* STACK_CHECK_MAX_FRAME_SIZE: Stack Checking. (line 74)
+* STACK_CHECK_MAX_VAR_SIZE: Stack Checking. (line 90)
+* STACK_CHECK_MOVING_SP: Stack Checking. (line 54)
+* STACK_CHECK_PROBE_INTERVAL_EXP: Stack Checking. (line 46)
+* STACK_CHECK_PROTECT: Stack Checking. (line 63)
+* STACK_CHECK_STATIC_BUILTIN: Stack Checking. (line 39)
+* STACK_DYNAMIC_OFFSET: Frame Layout. (line 75)
+* STACK_DYNAMIC_OFFSET and virtual registers: Regs and Memory.
(line 83)
-* STACK_GROWS_DOWNWARD: Frame Layout. (line 8)
-* STACK_PARMS_IN_REG_PARM_AREA: Stack Arguments. (line 89)
-* STACK_POINTER_OFFSET: Frame Layout. (line 57)
-* 'STACK_POINTER_OFFSET' and virtual registers: Regs and Memory.
+* STACK_GROWS_DOWNWARD: Frame Layout. (line 9)
+* STACK_PARMS_IN_REG_PARM_AREA: Stack Arguments. (line 90)
+* STACK_POINTER_OFFSET: Frame Layout. (line 58)
+* STACK_POINTER_OFFSET and virtual registers: Regs and Memory.
(line 93)
-* STACK_POINTER_REGNUM: Frame Registers. (line 8)
-* 'STACK_POINTER_REGNUM' and virtual registers: Regs and Memory.
+* STACK_POINTER_REGNUM: Frame Registers. (line 9)
+* STACK_POINTER_REGNUM and virtual registers: Regs and Memory.
(line 83)
* stack_pointer_rtx: Frame Registers. (line 104)
-* 'stack_protect_set' instruction pattern: Standard Names. (line 1897)
-* 'stack_protect_test' instruction pattern: Standard Names. (line 1907)
-* STACK_PUSH_CODE: Frame Layout. (line 16)
-* STACK_REGS: Stack Registers. (line 19)
-* STACK_REG_COVER_CLASS: Stack Registers. (line 22)
-* STACK_SAVEAREA_MODE: Storage Layout. (line 443)
-* STACK_SIZE_MODE: Storage Layout. (line 454)
-* STACK_SLOT_ALIGNMENT: Storage Layout. (line 275)
+* stack_protect_set instruction pattern: Standard Names. (line 1907)
+* stack_protect_test instruction pattern: Standard Names. (line 1917)
+* STACK_PUSH_CODE: Frame Layout. (line 17)
+* STACK_REG_COVER_CLASS: Stack Registers. (line 23)
+* STACK_REGS: Stack Registers. (line 20)
+* STACK_SAVEAREA_MODE: Storage Layout. (line 448)
+* STACK_SIZE_MODE: Storage Layout. (line 459)
+* STACK_SLOT_ALIGNMENT: Storage Layout. (line 279)
* standard pattern names: Standard Names. (line 6)
-* STANDARD_STARTFILE_PREFIX: Driver. (line 274)
-* STANDARD_STARTFILE_PREFIX_1: Driver. (line 281)
-* STANDARD_STARTFILE_PREFIX_2: Driver. (line 288)
-* STARTFILE_SPEC: Driver. (line 147)
-* STARTING_FRAME_OFFSET: Frame Layout. (line 38)
-* 'STARTING_FRAME_OFFSET' and virtual registers: Regs and Memory.
+* STANDARD_STARTFILE_PREFIX: Driver. (line 275)
+* STANDARD_STARTFILE_PREFIX_1: Driver. (line 282)
+* STANDARD_STARTFILE_PREFIX_2: Driver. (line 289)
+* STARTFILE_SPEC: Driver. (line 148)
+* STARTING_FRAME_OFFSET: Frame Layout. (line 39)
+* STARTING_FRAME_OFFSET and virtual registers: Regs and Memory.
(line 74)
* Statement and operand traversals: Statement and operand traversals.
(line 6)
* Statement Sequences: Statement Sequences.
(line 6)
-* Statements: Statements. (line 6)
+* statements <1>: Statements for C++. (line 6)
* statements: Function Properties.
(line 6)
-* statements <1>: Statements for C++. (line 6)
+* Statements: Statements. (line 6)
* Static profile estimation: Profile information.
(line 24)
* static single assignment: SSA. (line 6)
-* STATIC_CHAIN_INCOMING_REGNUM: Frame Registers. (line 77)
-* STATIC_CHAIN_REGNUM: Frame Registers. (line 76)
-* 'stdarg.h' and register arguments: Register Arguments. (line 51)
-* STDC_0_IN_SYSTEM_HEADERS: Misc. (line 350)
+* STATIC_CHAIN_INCOMING_REGNUM: Frame Registers. (line 78)
+* STATIC_CHAIN_REGNUM: Frame Registers. (line 77)
+* stdarg.h and register arguments: Register Arguments. (line 51)
+* STDC_0_IN_SYSTEM_HEADERS: Misc. (line 351)
* STMT_EXPR: Unary and Binary Expressions.
(line 6)
* STMT_IS_FULL_EXPR_P: Statements for C++. (line 22)
* storage layout: Storage Layout. (line 6)
-* STORE_FLAG_VALUE: Misc. (line 201)
-* 'store_multiple' instruction pattern: Standard Names. (line 159)
-* strcpy: Storage Layout. (line 228)
-* STRICT_ALIGNMENT: Storage Layout. (line 325)
+* STORE_FLAG_VALUE: Misc. (line 202)
+* store_multiple instruction pattern: Standard Names. (line 160)
+* strcpy: Storage Layout. (line 231)
+* STRICT_ALIGNMENT: Storage Layout. (line 329)
* strict_low_part: RTL Declarations. (line 9)
-* strict_memory_address_p: Addressing Modes. (line 186)
+* strict_memory_address_p: Addressing Modes. (line 187)
* STRING_CST: Constant expressions.
(line 6)
* STRING_POOL_ADDRESS_P: Flags. (line 165)
-* 'strlenM' instruction pattern: Standard Names. (line 904)
+* strlenM instruction pattern: Standard Names. (line 909)
* structure value address: Aggregate Return. (line 6)
+* STRUCTURE_SIZE_BOUNDARY: Storage Layout. (line 321)
* structures, returning: Interface. (line 10)
-* STRUCTURE_SIZE_BOUNDARY: Storage Layout. (line 317)
-* 'subM3' instruction pattern: Standard Names. (line 276)
+* subM3 instruction pattern: Standard Names. (line 279)
* SUBOBJECT: Statements for C++. (line 6)
* SUBOBJECT_CLEANUP: Statements for C++. (line 6)
* subreg: Regs and Memory. (line 97)
-* 'subreg' and '/s': Flags. (line 187)
-* 'subreg' and '/u': Flags. (line 180)
-* 'subreg' and '/u' and '/v': Flags. (line 170)
-* 'subreg', in 'strict_low_part': RTL Declarations. (line 9)
-* SUBREG_BYTE: Regs and Memory. (line 285)
+* subreg and /s: Flags. (line 187)
+* subreg and /u: Flags. (line 180)
+* subreg and /u and /v: Flags. (line 170)
+* subreg, in strict_low_part: RTL Declarations. (line 9)
+* SUBREG_BYTE: Regs and Memory. (line 289)
* SUBREG_PROMOTED_UNSIGNED_P: Flags. (line 170)
* SUBREG_PROMOTED_UNSIGNED_SET: Flags. (line 180)
* SUBREG_PROMOTED_VAR_P: Flags. (line 187)
-* SUBREG_REG: Regs and Memory. (line 285)
-* subst iterators in '.md' files: Subst Iterators. (line 6)
+* SUBREG_REG: Regs and Memory. (line 289)
+* subst iterators in .md files: Subst Iterators. (line 6)
* SUCCESS_EXIT_CODE: Host Misc. (line 12)
* SUPPORTS_INIT_PRIORITY: Macros for Initialization.
- (line 57)
-* SUPPORTS_ONE_ONLY: Label Output. (line 262)
-* SUPPORTS_WEAK: Label Output. (line 236)
-* SWITCHABLE_TARGET: Run-time Target. (line 164)
+ (line 58)
+* SUPPORTS_ONE_ONLY: Label Output. (line 266)
+* SUPPORTS_WEAK: Label Output. (line 240)
* SWITCH_BODY: Statements for C++. (line 6)
* SWITCH_COND: Statements for C++. (line 6)
* SWITCH_STMT: Statements for C++. (line 6)
-* symbolic label: Sharing. (line 20)
-* SYMBOL_FLAG_ANCHOR: Special Accessors. (line 117)
-* SYMBOL_FLAG_EXTERNAL: Special Accessors. (line 99)
-* SYMBOL_FLAG_FUNCTION: Special Accessors. (line 92)
-* SYMBOL_FLAG_HAS_BLOCK_INFO: Special Accessors. (line 113)
-* SYMBOL_FLAG_LOCAL: Special Accessors. (line 95)
-* SYMBOL_FLAG_SMALL: Special Accessors. (line 104)
-* SYMBOL_FLAG_TLS_SHIFT: Special Accessors. (line 108)
+* SWITCHABLE_TARGET: Run-time Target. (line 165)
+* SYMBOL_FLAG_ANCHOR: Special Accessors. (line 120)
+* SYMBOL_FLAG_EXTERNAL: Special Accessors. (line 102)
+* SYMBOL_FLAG_FUNCTION: Special Accessors. (line 95)
+* SYMBOL_FLAG_HAS_BLOCK_INFO: Special Accessors. (line 116)
+* SYMBOL_FLAG_LOCAL: Special Accessors. (line 98)
+* SYMBOL_FLAG_SMALL: Special Accessors. (line 107)
+* SYMBOL_FLAG_TLS_SHIFT: Special Accessors. (line 111)
* symbol_ref: Constants. (line 117)
-* 'symbol_ref' and '/f': Flags. (line 165)
-* 'symbol_ref' and '/i': Flags. (line 202)
-* 'symbol_ref' and '/u': Flags. (line 10)
-* 'symbol_ref' and '/v': Flags. (line 206)
-* 'symbol_ref', RTL sharing: Sharing. (line 20)
-* SYMBOL_REF_ANCHOR_P: Special Accessors. (line 117)
-* SYMBOL_REF_BLOCK: Special Accessors. (line 130)
-* SYMBOL_REF_BLOCK_OFFSET: Special Accessors. (line 135)
-* SYMBOL_REF_CONSTANT: Special Accessors. (line 78)
-* SYMBOL_REF_DATA: Special Accessors. (line 82)
-* SYMBOL_REF_DECL: Special Accessors. (line 67)
-* SYMBOL_REF_EXTERNAL_P: Special Accessors. (line 99)
+* symbol_ref and /f: Flags. (line 165)
+* symbol_ref and /i: Flags. (line 202)
+* symbol_ref and /u: Flags. (line 10)
+* symbol_ref and /v: Flags. (line 206)
+* symbol_ref, RTL sharing: Sharing. (line 20)
+* SYMBOL_REF_ANCHOR_P: Special Accessors. (line 120)
+* SYMBOL_REF_BLOCK: Special Accessors. (line 133)
+* SYMBOL_REF_BLOCK_OFFSET: Special Accessors. (line 138)
+* SYMBOL_REF_CONSTANT: Special Accessors. (line 81)
+* SYMBOL_REF_DATA: Special Accessors. (line 85)
+* SYMBOL_REF_DECL: Special Accessors. (line 69)
+* SYMBOL_REF_EXTERNAL_P: Special Accessors. (line 102)
* SYMBOL_REF_FLAG: Flags. (line 206)
-* 'SYMBOL_REF_FLAG', in 'TARGET_ENCODE_SECTION_INFO': Sections.
- (line 277)
-* SYMBOL_REF_FLAGS: Special Accessors. (line 86)
-* SYMBOL_REF_FUNCTION_P: Special Accessors. (line 92)
-* SYMBOL_REF_HAS_BLOCK_INFO_P: Special Accessors. (line 113)
-* SYMBOL_REF_LOCAL_P: Special Accessors. (line 95)
-* SYMBOL_REF_SMALL_P: Special Accessors. (line 104)
-* SYMBOL_REF_TLS_MODEL: Special Accessors. (line 108)
+* SYMBOL_REF_FLAG, in TARGET_ENCODE_SECTION_INFO: Sections. (line 277)
+* SYMBOL_REF_FLAGS: Special Accessors. (line 89)
+* SYMBOL_REF_FUNCTION_P: Special Accessors. (line 95)
+* SYMBOL_REF_HAS_BLOCK_INFO_P: Special Accessors. (line 116)
+* SYMBOL_REF_LOCAL_P: Special Accessors. (line 98)
+* SYMBOL_REF_SMALL_P: Special Accessors. (line 107)
+* SYMBOL_REF_TLS_MODEL: Special Accessors. (line 111)
* SYMBOL_REF_USED: Flags. (line 197)
* SYMBOL_REF_WEAK: Flags. (line 202)
-* 'sync_addMODE' instruction pattern: Standard Names. (line 1662)
-* 'sync_andMODE' instruction pattern: Standard Names. (line 1662)
-* 'sync_compare_and_swapMODE' instruction pattern: Standard Names.
- (line 1622)
-* 'sync_iorMODE' instruction pattern: Standard Names. (line 1662)
-* 'sync_lock_releaseMODE' instruction pattern: Standard Names.
- (line 1727)
-* 'sync_lock_test_and_setMODE' instruction pattern: Standard Names.
- (line 1701)
-* 'sync_nandMODE' instruction pattern: Standard Names. (line 1662)
-* 'sync_new_addMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_new_andMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_new_iorMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_new_nandMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_new_subMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_new_xorMODE' instruction pattern: Standard Names. (line 1694)
-* 'sync_old_addMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_old_andMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_old_iorMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_old_nandMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_old_subMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_old_xorMODE' instruction pattern: Standard Names. (line 1677)
-* 'sync_subMODE' instruction pattern: Standard Names. (line 1662)
-* 'sync_xorMODE' instruction pattern: Standard Names. (line 1662)
-* SYSROOT_HEADERS_SUFFIX_SPEC: Driver. (line 176)
-* SYSROOT_SUFFIX_SPEC: Driver. (line 171)
-* 't-TARGET': Target Fragment. (line 6)
+* symbolic label: Sharing. (line 20)
+* sync_addMODE instruction pattern: Standard Names. (line 1672)
+* sync_andMODE instruction pattern: Standard Names. (line 1672)
+* sync_compare_and_swapMODE instruction pattern: Standard Names.
+ (line 1632)
+* sync_iorMODE instruction pattern: Standard Names. (line 1672)
+* sync_lock_releaseMODE instruction pattern: Standard Names. (line 1737)
+* sync_lock_test_and_setMODE instruction pattern: Standard Names.
+ (line 1711)
+* sync_nandMODE instruction pattern: Standard Names. (line 1672)
+* sync_new_addMODE instruction pattern: Standard Names. (line 1704)
+* sync_new_andMODE instruction pattern: Standard Names. (line 1704)
+* sync_new_iorMODE instruction pattern: Standard Names. (line 1704)
+* sync_new_nandMODE instruction pattern: Standard Names. (line 1704)
+* sync_new_subMODE instruction pattern: Standard Names. (line 1704)
+* sync_new_xorMODE instruction pattern: Standard Names. (line 1704)
+* sync_old_addMODE instruction pattern: Standard Names. (line 1687)
+* sync_old_andMODE instruction pattern: Standard Names. (line 1687)
+* sync_old_iorMODE instruction pattern: Standard Names. (line 1687)
+* sync_old_nandMODE instruction pattern: Standard Names. (line 1687)
+* sync_old_subMODE instruction pattern: Standard Names. (line 1687)
+* sync_old_xorMODE instruction pattern: Standard Names. (line 1687)
+* sync_subMODE instruction pattern: Standard Names. (line 1672)
+* sync_xorMODE instruction pattern: Standard Names. (line 1672)
+* SYSROOT_HEADERS_SUFFIX_SPEC: Driver. (line 177)
+* SYSROOT_SUFFIX_SPEC: Driver. (line 172)
+* t-TARGET: Target Fragment. (line 6)
* table jump: Basic Blocks. (line 67)
-* 'tablejump' instruction pattern: Standard Names. (line 1292)
+* tablejump instruction pattern: Standard Names. (line 1298)
* tag: GTY Options. (line 88)
* tagging insns: Tagging Insns. (line 6)
* tail calls: Tail Calls. (line 6)
-* TAmode: Machine Modes. (line 158)
+* TAmode: Machine Modes. (line 159)
* target attributes: Target Attributes. (line 6)
* target description macros: Target Macros. (line 6)
* target functions: Target Structure. (line 6)
* target hooks: Target Structure. (line 6)
* target makefile fragment: Target Fragment. (line 6)
* target specifications: Run-time Target. (line 6)
-* targetm: Target Structure. (line 6)
-* targets, makefile: Makefile. (line 6)
-* TARGET_ABSOLUTE_BIGGEST_ALIGNMENT: Storage Layout. (line 168)
-* TARGET_ADDRESS_COST: Costs. (line 308)
+* TARGET_ABSOLUTE_BIGGEST_ALIGNMENT: Storage Layout. (line 170)
* TARGET_ADDR_SPACE_ADDRESS_MODE: Named Address Spaces.
- (line 43)
+ (line 45)
* TARGET_ADDR_SPACE_CONVERT: Named Address Spaces.
- (line 85)
+ (line 88)
* TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P: Named Address Spaces.
- (line 61)
+ (line 63)
* TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS: Named Address Spaces.
- (line 69)
+ (line 72)
* TARGET_ADDR_SPACE_POINTER_MODE: Named Address Spaces.
- (line 36)
+ (line 38)
* TARGET_ADDR_SPACE_SUBSET_P: Named Address Spaces.
- (line 76)
+ (line 79)
* TARGET_ADDR_SPACE_VALID_POINTER_MODE: Named Address Spaces.
- (line 50)
-* TARGET_ALIGN_ANON_BITFIELD: Storage Layout. (line 402)
-* TARGET_ALLOCATE_INITIAL_VALUE: Misc. (line 809)
-* TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS: Misc. (line 1114)
-* TARGET_ALWAYS_STRIP_DOTDOT: Driver. (line 246)
-* TARGET_ARG_PARTIAL_BYTES: Register Arguments. (line 95)
+ (line 52)
+* TARGET_ADDRESS_COST: Costs. (line 310)
+* TARGET_ALIGN_ANON_BITFIELD: Storage Layout. (line 406)
+* TARGET_ALLOCATE_INITIAL_VALUE: Misc. (line 814)
+* TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS: Misc. (line 1121)
+* TARGET_ALWAYS_STRIP_DOTDOT: Driver. (line 247)
+* TARGET_ARG_PARTIAL_BYTES: Register Arguments. (line 98)
* TARGET_ARM_EABI_UNWINDER: Exception Region Output.
- (line 133)
-* TARGET_ARRAY_MODE_SUPPORTED_P: Register Arguments. (line 345)
-* TARGET_ASAN_SHADOW_OFFSET: Misc. (line 1142)
-* TARGET_ASM_ALIGNED_DI_OP: Data Output. (line 9)
-* TARGET_ASM_ALIGNED_HI_OP: Data Output. (line 7)
-* TARGET_ASM_ALIGNED_SI_OP: Data Output. (line 8)
-* TARGET_ASM_ALIGNED_TI_OP: Data Output. (line 10)
-* TARGET_ASM_ASSEMBLE_UNDEFINED_DECL: Label Output. (line 203)
-* TARGET_ASM_ASSEMBLE_VISIBILITY: Label Output. (line 273)
-* TARGET_ASM_BYTE_OP: Data Output. (line 6)
-* TARGET_ASM_CAN_OUTPUT_MI_THUNK: Function Entry. (line 202)
-* TARGET_ASM_CLOSE_PAREN: Data Output. (line 133)
-* TARGET_ASM_CODE_END: File Framework. (line 57)
+ (line 135)
+* TARGET_ARRAY_MODE_SUPPORTED_P: Register Arguments. (line 349)
+* TARGET_ASAN_SHADOW_OFFSET: Misc. (line 1149)
+* TARGET_ASM_ALIGNED_DI_OP: Data Output. (line 10)
+* TARGET_ASM_ALIGNED_HI_OP: Data Output. (line 8)
+* TARGET_ASM_ALIGNED_SI_OP: Data Output. (line 9)
+* TARGET_ASM_ALIGNED_TI_OP: Data Output. (line 11)
+* TARGET_ASM_ASSEMBLE_UNDEFINED_DECL: Label Output. (line 208)
+* TARGET_ASM_ASSEMBLE_VISIBILITY: Label Output. (line 278)
+* TARGET_ASM_BYTE_OP: Data Output. (line 7)
+* TARGET_ASM_CAN_OUTPUT_MI_THUNK: Function Entry. (line 207)
+* TARGET_ASM_CLOSE_PAREN: Data Output. (line 135)
+* TARGET_ASM_CODE_END: File Framework. (line 59)
* TARGET_ASM_CONSTRUCTOR: Macros for Initialization.
- (line 68)
-* TARGET_ASM_DECLARE_CONSTANT_NAME: Label Output. (line 149)
-* TARGET_ASM_DECL_END: Data Output. (line 38)
+ (line 69)
+* TARGET_ASM_DECL_END: Data Output. (line 39)
+* TARGET_ASM_DECLARE_CONSTANT_NAME: Label Output. (line 154)
* TARGET_ASM_DESTRUCTOR: Macros for Initialization.
- (line 82)
-* TARGET_ASM_EMIT_EXCEPT_PERSONALITY: Dispatch Tables. (line 80)
-* TARGET_ASM_EMIT_EXCEPT_TABLE_LABEL: Dispatch Tables. (line 73)
-* TARGET_ASM_EMIT_UNWIND_LABEL: Dispatch Tables. (line 61)
-* TARGET_ASM_EXTERNAL_LIBCALL: Label Output. (line 309)
-* TARGET_ASM_FILE_END: File Framework. (line 35)
-* TARGET_ASM_FILE_START: File Framework. (line 8)
-* TARGET_ASM_FILE_START_APP_OFF: File Framework. (line 16)
-* TARGET_ASM_FILE_START_FILE_DIRECTIVE: File Framework. (line 29)
-* TARGET_ASM_FINAL_POSTSCAN_INSN: Instruction Output. (line 82)
-* TARGET_ASM_FUNCTION_BEGIN_EPILOGUE: Function Entry. (line 59)
-* TARGET_ASM_FUNCTION_END_PROLOGUE: Function Entry. (line 53)
-* TARGET_ASM_FUNCTION_EPILOGUE: Function Entry. (line 65)
-* TARGET_ASM_FUNCTION_PROLOGUE: Function Entry. (line 9)
-* TARGET_ASM_FUNCTION_RODATA_SECTION: Sections. (line 213)
-* TARGET_ASM_FUNCTION_SECTION: File Framework. (line 121)
+ (line 83)
+* TARGET_ASM_EMIT_EXCEPT_PERSONALITY: Dispatch Tables. (line 82)
+* TARGET_ASM_EMIT_EXCEPT_TABLE_LABEL: Dispatch Tables. (line 74)
+* TARGET_ASM_EMIT_UNWIND_LABEL: Dispatch Tables. (line 63)
+* TARGET_ASM_EXTERNAL_LIBCALL: Label Output. (line 313)
+* TARGET_ASM_FILE_END: File Framework. (line 37)
+* TARGET_ASM_FILE_START: File Framework. (line 9)
+* TARGET_ASM_FILE_START_APP_OFF: File Framework. (line 17)
+* TARGET_ASM_FILE_START_FILE_DIRECTIVE: File Framework. (line 31)
+* TARGET_ASM_FINAL_POSTSCAN_INSN: Instruction Output. (line 84)
+* TARGET_ASM_FUNCTION_BEGIN_EPILOGUE: Function Entry. (line 61)
+* TARGET_ASM_FUNCTION_END_PROLOGUE: Function Entry. (line 55)
+* TARGET_ASM_FUNCTION_EPILOGUE: Function Entry. (line 68)
+* TARGET_ASM_FUNCTION_PROLOGUE: Function Entry. (line 11)
+* TARGET_ASM_FUNCTION_RODATA_SECTION: Sections. (line 215)
+* TARGET_ASM_FUNCTION_SECTION: File Framework. (line 124)
* TARGET_ASM_FUNCTION_SWITCHED_TEXT_SECTIONS: File Framework.
- (line 131)
-* TARGET_ASM_GLOBALIZE_DECL_NAME: Label Output. (line 194)
-* TARGET_ASM_GLOBALIZE_LABEL: Label Output. (line 185)
-* TARGET_ASM_INIT_SECTIONS: Sections. (line 159)
-* TARGET_ASM_INTEGER: Data Output. (line 25)
-* TARGET_ASM_INTERNAL_LABEL: Label Output. (line 352)
-* TARGET_ASM_JUMP_ALIGN_MAX_SKIP: Alignment Output. (line 21)
+ (line 134)
+* TARGET_ASM_GLOBALIZE_DECL_NAME: Label Output. (line 199)
+* TARGET_ASM_GLOBALIZE_LABEL: Label Output. (line 190)
+* TARGET_ASM_INIT_SECTIONS: Sections. (line 160)
+* TARGET_ASM_INTEGER: Data Output. (line 27)
+* TARGET_ASM_INTERNAL_LABEL: Label Output. (line 357)
+* TARGET_ASM_JUMP_ALIGN_MAX_SKIP: Alignment Output. (line 22)
* TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP: Alignment Output.
- (line 34)
-* TARGET_ASM_LABEL_ALIGN_MAX_SKIP: Alignment Output. (line 68)
-* TARGET_ASM_LOOP_ALIGN_MAX_SKIP: Alignment Output. (line 53)
-* TARGET_ASM_LTO_END: File Framework. (line 52)
-* TARGET_ASM_LTO_START: File Framework. (line 47)
-* TARGET_ASM_MARK_DECL_PRESERVED: Label Output. (line 315)
-* TARGET_ASM_MERGEABLE_RODATA_PREFIX: Sections. (line 221)
-* TARGET_ASM_NAMED_SECTION: File Framework. (line 113)
-* TARGET_ASM_OPEN_PAREN: Data Output. (line 132)
-* TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA: Data Output. (line 42)
-* TARGET_ASM_OUTPUT_ANCHOR: Anchored Addresses. (line 42)
-* TARGET_ASM_OUTPUT_DWARF_DTPREL: SDB and DWARF. (line 103)
-* TARGET_ASM_OUTPUT_IDENT: File Framework. (line 100)
-* TARGET_ASM_OUTPUT_MI_THUNK: Function Entry. (line 160)
-* TARGET_ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 91)
-* TARGET_ASM_RECORD_GCC_SWITCHES: File Framework. (line 162)
-* TARGET_ASM_RECORD_GCC_SWITCHES_SECTION: File Framework. (line 207)
-* TARGET_ASM_RELOC_RW_MASK: Sections. (line 168)
-* TARGET_ASM_SELECT_RTX_SECTION: Sections. (line 230)
-* TARGET_ASM_SELECT_SECTION: Sections. (line 179)
-* TARGET_ASM_TM_CLONE_TABLE_SECTION: Sections. (line 226)
-* TARGET_ASM_TRAMPOLINE_TEMPLATE: Trampolines. (line 28)
+ (line 36)
+* TARGET_ASM_LABEL_ALIGN_MAX_SKIP: Alignment Output. (line 69)
+* TARGET_ASM_LOOP_ALIGN_MAX_SKIP: Alignment Output. (line 54)
+* TARGET_ASM_LTO_END: File Framework. (line 54)
+* TARGET_ASM_LTO_START: File Framework. (line 49)
+* TARGET_ASM_MARK_DECL_PRESERVED: Label Output. (line 320)
+* TARGET_ASM_MERGEABLE_RODATA_PREFIX: Sections. (line 222)
+* TARGET_ASM_NAMED_SECTION: File Framework. (line 116)
+* TARGET_ASM_OPEN_PAREN: Data Output. (line 134)
+* TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA: Data Output. (line 44)
+* TARGET_ASM_OUTPUT_ANCHOR: Anchored Addresses. (line 44)
+* TARGET_ASM_OUTPUT_DWARF_DTPREL: SDB and DWARF. (line 105)
+* TARGET_ASM_OUTPUT_IDENT: File Framework. (line 102)
+* TARGET_ASM_OUTPUT_MI_THUNK: Function Entry. (line 165)
+* TARGET_ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 94)
+* TARGET_ASM_RECORD_GCC_SWITCHES: File Framework. (line 165)
+* TARGET_ASM_RECORD_GCC_SWITCHES_SECTION: File Framework. (line 209)
+* TARGET_ASM_RELOC_RW_MASK: Sections. (line 169)
+* TARGET_ASM_SELECT_RTX_SECTION: Sections. (line 232)
+* TARGET_ASM_SELECT_SECTION: Sections. (line 181)
+* TARGET_ASM_TM_CLONE_TABLE_SECTION: Sections. (line 227)
+* TARGET_ASM_TRAMPOLINE_TEMPLATE: Trampolines. (line 29)
* TARGET_ASM_TTYPE: Exception Region Output.
- (line 127)
-* TARGET_ASM_UNALIGNED_DI_OP: Data Output. (line 13)
-* TARGET_ASM_UNALIGNED_HI_OP: Data Output. (line 11)
-* TARGET_ASM_UNALIGNED_SI_OP: Data Output. (line 12)
-* TARGET_ASM_UNALIGNED_TI_OP: Data Output. (line 14)
-* TARGET_ASM_UNIQUE_SECTION: Sections. (line 201)
-* TARGET_ASM_UNWIND_EMIT: Dispatch Tables. (line 87)
-* TARGET_ASM_UNWIND_EMIT_BEFORE_INSN: Dispatch Tables. (line 93)
-* TARGET_ATOMIC_ALIGN_FOR_MODE: Misc. (line 1161)
-* TARGET_ATOMIC_ASSIGN_EXPAND_FENV: Misc. (line 1167)
-* TARGET_ATOMIC_TEST_AND_SET_TRUEVAL: Misc. (line 1152)
-* TARGET_ATTRIBUTE_TABLE: Target Attributes. (line 10)
-* TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P: Target Attributes. (line 17)
-* TARGET_BINDS_LOCAL_P: Sections. (line 308)
-* TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED: Misc. (line 906)
-* TARGET_BRANCH_TARGET_REGISTER_CLASS: Misc. (line 899)
-* TARGET_BUILD_BUILTIN_VA_LIST: Register Arguments. (line 285)
+ (line 129)
+* TARGET_ASM_UNALIGNED_DI_OP: Data Output. (line 14)
+* TARGET_ASM_UNALIGNED_HI_OP: Data Output. (line 12)
+* TARGET_ASM_UNALIGNED_SI_OP: Data Output. (line 13)
+* TARGET_ASM_UNALIGNED_TI_OP: Data Output. (line 15)
+* TARGET_ASM_UNIQUE_SECTION: Sections. (line 202)
+* TARGET_ASM_UNWIND_EMIT: Dispatch Tables. (line 89)
+* TARGET_ASM_UNWIND_EMIT_BEFORE_INSN: Dispatch Tables. (line 94)
+* TARGET_ATOMIC_ALIGN_FOR_MODE: Misc. (line 1169)
+* TARGET_ATOMIC_ASSIGN_EXPAND_FENV: Misc. (line 1175)
+* TARGET_ATOMIC_TEST_AND_SET_TRUEVAL: Misc. (line 1159)
+* TARGET_ATTRIBUTE_TABLE: Target Attributes. (line 11)
+* TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P: Target Attributes. (line 19)
+* TARGET_BINDS_LOCAL_P: Sections. (line 309)
+* TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED: Misc. (line 911)
+* TARGET_BRANCH_TARGET_REGISTER_CLASS: Misc. (line 903)
+* TARGET_BUILD_BUILTIN_VA_LIST: Register Arguments. (line 287)
* TARGET_BUILTIN_CHKP_FUNCTION: Misc. (line 624)
-* TARGET_BUILTIN_DECL: Misc. (line 603)
-* TARGET_BUILTIN_RECIPROCAL: Addressing Modes. (line 261)
-* TARGET_BUILTIN_SETJMP_FRAME_VALUE: Frame Layout. (line 107)
-* TARGET_CALLEE_COPIES: Register Arguments. (line 127)
-* TARGET_CALL_ARGS: Varargs. (line 123)
+* TARGET_BUILTIN_DECL: Misc. (line 605)
+* TARGET_BUILTIN_RECIPROCAL: Addressing Modes. (line 264)
+* TARGET_BUILTIN_SETJMP_FRAME_VALUE: Frame Layout. (line 109)
+* TARGET_C_PREINCLUDE: Misc. (line 362)
+* TARGET_CALL_ARGS: Varargs. (line 127)
* TARGET_CALL_FUSAGE_CONTAINS_NON_CALLEE_CLOBBERS: Miscellaneous Register Hooks.
- (line 6)
-* TARGET_CANNOT_FORCE_CONST_MEM: Addressing Modes. (line 234)
-* TARGET_CANNOT_MODIFY_JUMPS_P: Misc. (line 886)
-* TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P: Register Classes. (line 581)
+ (line 7)
+* TARGET_CALLEE_COPIES: Register Arguments. (line 130)
+* TARGET_CAN_ELIMINATE: Elimination. (line 75)
+* TARGET_CAN_FOLLOW_JUMP: Misc. (line 801)
+* TARGET_CAN_INLINE_P: Target Attributes. (line 166)
+* TARGET_CAN_USE_DOLOOP_P: Misc. (line 767)
+* TARGET_CANNOT_FORCE_CONST_MEM: Addressing Modes. (line 237)
+* TARGET_CANNOT_MODIFY_JUMPS_P: Misc. (line 890)
+* TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P: Register Classes. (line 587)
+* TARGET_CANONICAL_VA_LIST_TYPE: Register Arguments. (line 308)
* TARGET_CANONICALIZE_COMPARISON: MODE_CC Condition Codes.
- (line 55)
-* TARGET_CANONICAL_VA_LIST_TYPE: Register Arguments. (line 306)
-* TARGET_CAN_ELIMINATE: Elimination. (line 73)
-* TARGET_CAN_FOLLOW_JUMP: Misc. (line 795)
-* TARGET_CAN_INLINE_P: Target Attributes. (line 165)
-* TARGET_CAN_USE_DOLOOP_P: Misc. (line 759)
-* TARGET_CASE_VALUES_THRESHOLD: Misc. (line 46)
+ (line 57)
+* TARGET_CASE_VALUES_THRESHOLD: Misc. (line 47)
* TARGET_CC_MODES_COMPATIBLE: MODE_CC Condition Codes.
- (line 120)
-* TARGET_CHECK_PCH_TARGET_FLAGS: PCH Target. (line 26)
-* TARGET_CHECK_STRING_OBJECT_FORMAT_ARG: Run-time Target. (line 119)
-* TARGET_CHKP_BOUND_MODE: Misc. (line 696)
-* TARGET_CHKP_BOUND_TYPE: Misc. (line 694)
-* TARGET_CHKP_FUNCTION_VALUE_BOUNDS: Varargs. (line 182)
-* TARGET_CHKP_INITIALIZE_BOUNDS: Misc. (line 702)
-* TARGET_CHKP_MAKE_BOUNDS_CONSTANT: Misc. (line 698)
-* TARGET_CLASS_LIKELY_SPILLED_P: Register Classes. (line 489)
-* TARGET_CLASS_MAX_NREGS: Register Classes. (line 505)
-* TARGET_COMMUTATIVE_P: Misc. (line 802)
-* TARGET_COMPARE_VERSION_PRIORITY: Misc. (line 736)
-* TARGET_COMP_TYPE_ATTRIBUTES: Target Attributes. (line 25)
-* TARGET_CONDITIONAL_REGISTER_USAGE: Register Basics. (line 59)
-* TARGET_CONST_ANCHOR: Misc. (line 1125)
-* TARGET_CONST_NOT_OK_FOR_DEBUG_P: Addressing Modes. (line 230)
-* TARGET_CONVERT_TO_TYPE: Misc. (line 1079)
-* TARGET_CPU_CPP_BUILTINS: Run-time Target. (line 8)
-* TARGET_CSTORE_MODE: Register Classes. (line 604)
-* TARGET_CXX_ADJUST_CLASS_AT_DEFINITION: C++ ABI. (line 86)
-* TARGET_CXX_CDTOR_RETURNS_THIS: C++ ABI. (line 37)
-* TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT: C++ ABI. (line 61)
-* TARGET_CXX_COOKIE_HAS_SIZE: C++ ABI. (line 24)
-* TARGET_CXX_DECL_MANGLING_CONTEXT: C++ ABI. (line 92)
-* TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY: C++ ABI. (line 52)
-* TARGET_CXX_GET_COOKIE_SIZE: C++ ABI. (line 17)
-* TARGET_CXX_GUARD_MASK_BIT: C++ ABI. (line 11)
-* TARGET_CXX_GUARD_TYPE: C++ ABI. (line 6)
-* TARGET_CXX_IMPLICIT_EXTERN_C: Misc. (line 373)
-* TARGET_CXX_IMPORT_EXPORT_CLASS: C++ ABI. (line 28)
-* TARGET_CXX_KEY_METHOD_MAY_BE_INLINE: C++ ABI. (line 42)
-* TARGET_CXX_LIBRARY_RTTI_COMDAT: C++ ABI. (line 68)
-* TARGET_CXX_USE_AEABI_ATEXIT: C++ ABI. (line 73)
-* TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT: C++ ABI. (line 79)
-* TARGET_C_PREINCLUDE: Misc. (line 361)
-* TARGET_DEBUG_UNWIND_INFO: SDB and DWARF. (line 36)
-* TARGET_DECIMAL_FLOAT_SUPPORTED_P: Storage Layout. (line 507)
-* TARGET_DECLSPEC: Target Attributes. (line 72)
-* TARGET_DEFAULT_PACK_STRUCT: Misc. (line 446)
-* TARGET_DEFAULT_SHORT_ENUMS: Type Layout. (line 129)
-* TARGET_DEFAULT_TARGET_FLAGS: Run-time Target. (line 55)
-* TARGET_DEFERRED_OUTPUT_DEFS: Label Output. (line 437)
-* TARGET_DELAY_SCHED2: SDB and DWARF. (line 65)
-* TARGET_DELAY_VARTRACK: SDB and DWARF. (line 69)
-* TARGET_DELEGITIMIZE_ADDRESS: Addressing Modes. (line 221)
-* TARGET_DIFFERENT_ADDR_DISPLACEMENT_P: Register Classes. (line 574)
+ (line 122)
+* TARGET_CHECK_PCH_TARGET_FLAGS: PCH Target. (line 28)
+* TARGET_CHECK_STRING_OBJECT_FORMAT_ARG: Run-time Target. (line 121)
+* TARGET_CHKP_BOUND_MODE: Misc. (line 699)
+* TARGET_CHKP_BOUND_TYPE: Misc. (line 696)
+* TARGET_CHKP_FUNCTION_VALUE_BOUNDS: Varargs. (line 188)
+* TARGET_CHKP_INITIALIZE_BOUNDS: Misc. (line 708)
+* TARGET_CHKP_MAKE_BOUNDS_CONSTANT: Misc. (line 703)
+* TARGET_CLASS_LIKELY_SPILLED_P: Register Classes. (line 494)
+* TARGET_CLASS_MAX_NREGS: Register Classes. (line 511)
+* TARGET_COMMUTATIVE_P: Misc. (line 807)
+* TARGET_COMP_TYPE_ATTRIBUTES: Target Attributes. (line 27)
+* TARGET_COMPARE_VERSION_PRIORITY: Misc. (line 742)
+* TARGET_CONDITIONAL_REGISTER_USAGE: Register Basics. (line 60)
+* TARGET_CONST_ANCHOR: Misc. (line 1132)
+* TARGET_CONST_NOT_OK_FOR_DEBUG_P: Addressing Modes. (line 232)
+* TARGET_CONVERT_TO_TYPE: Misc. (line 1085)
+* TARGET_CPU_CPP_BUILTINS: Run-time Target. (line 9)
+* TARGET_CSTORE_MODE: Register Classes. (line 611)
+* TARGET_CXX_ADJUST_CLASS_AT_DEFINITION: C++ ABI. (line 87)
+* TARGET_CXX_CDTOR_RETURNS_THIS: C++ ABI. (line 38)
+* TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT: C++ ABI. (line 62)
+* TARGET_CXX_COOKIE_HAS_SIZE: C++ ABI. (line 25)
+* TARGET_CXX_DECL_MANGLING_CONTEXT: C++ ABI. (line 93)
+* TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY: C++ ABI. (line 54)
+* TARGET_CXX_GET_COOKIE_SIZE: C++ ABI. (line 18)
+* TARGET_CXX_GUARD_MASK_BIT: C++ ABI. (line 12)
+* TARGET_CXX_GUARD_TYPE: C++ ABI. (line 7)
+* TARGET_CXX_IMPLICIT_EXTERN_C: Misc. (line 374)
+* TARGET_CXX_IMPORT_EXPORT_CLASS: C++ ABI. (line 30)
+* TARGET_CXX_KEY_METHOD_MAY_BE_INLINE: C++ ABI. (line 43)
+* TARGET_CXX_LIBRARY_RTTI_COMDAT: C++ ABI. (line 69)
+* TARGET_CXX_USE_AEABI_ATEXIT: C++ ABI. (line 74)
+* TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT: C++ ABI. (line 80)
+* TARGET_DEBUG_UNWIND_INFO: SDB and DWARF. (line 37)
+* TARGET_DECIMAL_FLOAT_SUPPORTED_P: Storage Layout. (line 512)
+* TARGET_DECLSPEC: Target Attributes. (line 73)
+* TARGET_DEFAULT_PACK_STRUCT: Misc. (line 448)
+* TARGET_DEFAULT_SHORT_ENUMS: Type Layout. (line 130)
+* TARGET_DEFAULT_TARGET_FLAGS: Run-time Target. (line 56)
+* TARGET_DEFERRED_OUTPUT_DEFS: Label Output. (line 441)
+* TARGET_DELAY_SCHED2: SDB and DWARF. (line 66)
+* TARGET_DELAY_VARTRACK: SDB and DWARF. (line 70)
+* TARGET_DELEGITIMIZE_ADDRESS: Addressing Modes. (line 223)
+* TARGET_DIFFERENT_ADDR_DISPLACEMENT_P: Register Classes. (line 580)
* TARGET_DLLIMPORT_DECL_ATTRIBUTES: Target Attributes. (line 55)
-* TARGET_DWARF_CALLING_CONVENTION: SDB and DWARF. (line 16)
+* TARGET_DWARF_CALLING_CONVENTION: SDB and DWARF. (line 18)
* TARGET_DWARF_FRAME_REG_MODE: Exception Region Output.
- (line 113)
-* TARGET_DWARF_HANDLE_FRAME_UNSPEC: Frame Layout. (line 171)
+ (line 115)
+* TARGET_DWARF_HANDLE_FRAME_UNSPEC: Frame Layout. (line 174)
* TARGET_DWARF_REGISTER_SPAN: Exception Region Output.
- (line 104)
-* TARGET_EDOM: Library Calls. (line 59)
-* TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS: Emulated TLS. (line 67)
-* TARGET_EMUTLS_GET_ADDRESS: Emulated TLS. (line 18)
-* TARGET_EMUTLS_REGISTER_COMMON: Emulated TLS. (line 23)
-* TARGET_EMUTLS_TMPL_PREFIX: Emulated TLS. (line 44)
-* TARGET_EMUTLS_TMPL_SECTION: Emulated TLS. (line 35)
-* TARGET_EMUTLS_VAR_ALIGN_FIXED: Emulated TLS. (line 62)
-* TARGET_EMUTLS_VAR_FIELDS: Emulated TLS. (line 48)
-* TARGET_EMUTLS_VAR_INIT: Emulated TLS. (line 55)
-* TARGET_EMUTLS_VAR_PREFIX: Emulated TLS. (line 40)
-* TARGET_EMUTLS_VAR_SECTION: Emulated TLS. (line 30)
-* TARGET_ENCODE_SECTION_INFO: Sections. (line 251)
-* 'TARGET_ENCODE_SECTION_INFO' and address validation: Addressing Modes.
- (line 82)
-* 'TARGET_ENCODE_SECTION_INFO' usage: Instruction Output. (line 127)
-* TARGET_END_CALL_ARGS: Varargs. (line 137)
-* TARGET_ENUM_VA_LIST_P: Register Arguments. (line 289)
+ (line 106)
+* TARGET_EDOM: Library Calls. (line 60)
+* TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS: Emulated TLS. (line 68)
+* TARGET_EMUTLS_GET_ADDRESS: Emulated TLS. (line 19)
+* TARGET_EMUTLS_REGISTER_COMMON: Emulated TLS. (line 24)
+* TARGET_EMUTLS_TMPL_PREFIX: Emulated TLS. (line 45)
+* TARGET_EMUTLS_TMPL_SECTION: Emulated TLS. (line 36)
+* TARGET_EMUTLS_VAR_ALIGN_FIXED: Emulated TLS. (line 63)
+* TARGET_EMUTLS_VAR_FIELDS: Emulated TLS. (line 49)
+* TARGET_EMUTLS_VAR_INIT: Emulated TLS. (line 57)
+* TARGET_EMUTLS_VAR_PREFIX: Emulated TLS. (line 41)
+* TARGET_EMUTLS_VAR_SECTION: Emulated TLS. (line 31)
+* TARGET_ENCODE_SECTION_INFO: Sections. (line 253)
+* TARGET_ENCODE_SECTION_INFO and address validation: Addressing Modes.
+ (line 83)
+* TARGET_ENCODE_SECTION_INFO usage: Instruction Output. (line 128)
+* TARGET_END_CALL_ARGS: Varargs. (line 141)
+* TARGET_ENUM_VA_LIST_P: Register Arguments. (line 292)
* TARGET_EXCEPT_UNWIND_INFO: Exception Region Output.
- (line 45)
-* TARGET_EXECUTABLE_SUFFIX: Misc. (line 860)
-* TARGET_EXPAND_BUILTIN: Misc. (line 613)
-* TARGET_EXPAND_BUILTIN_SAVEREGS: Varargs. (line 64)
-* TARGET_EXPAND_TO_RTL_HOOK: Storage Layout. (line 513)
+ (line 48)
+* TARGET_EXECUTABLE_SUFFIX: Misc. (line 864)
+* TARGET_EXPAND_BUILTIN: Misc. (line 615)
+* TARGET_EXPAND_BUILTIN_SAVEREGS: Varargs. (line 67)
+* TARGET_EXPAND_TO_RTL_HOOK: Storage Layout. (line 518)
* TARGET_EXPR: Unary and Binary Expressions.
(line 6)
-* TARGET_EXTRA_INCLUDES: Misc. (line 971)
-* TARGET_EXTRA_LIVE_ON_ENTRY: Tail Calls. (line 20)
-* TARGET_EXTRA_PRE_INCLUDES: Misc. (line 978)
+* TARGET_EXTRA_INCLUDES: Misc. (line 978)
+* TARGET_EXTRA_LIVE_ON_ENTRY: Tail Calls. (line 21)
+* TARGET_EXTRA_PRE_INCLUDES: Misc. (line 985)
* TARGET_FIXED_CONDITION_CODE_REGS: MODE_CC Condition Codes.
- (line 105)
-* TARGET_FIXED_POINT_SUPPORTED_P: Storage Layout. (line 510)
-* target_flags: Run-time Target. (line 51)
+ (line 107)
+* TARGET_FIXED_POINT_SUPPORTED_P: Storage Layout. (line 515)
+* target_flags: Run-time Target. (line 52)
* TARGET_FLAGS_REGNUM: MODE_CC Condition Codes.
- (line 133)
+ (line 134)
* TARGET_FLOAT_EXCEPTIONS_ROUNDING_SUPPORTED_P: Run-time Target.
- (line 183)
-* TARGET_FLT_EVAL_METHOD: Type Layout. (line 110)
-* TARGET_FN_ABI_VA_LIST: Register Arguments. (line 301)
-* TARGET_FOLD_BUILTIN: Misc. (line 719)
-* TARGET_FORCE_AT_COMP_DIR: SDB and DWARF. (line 60)
-* TARGET_FORMAT_TYPES: Misc. (line 999)
-* TARGET_FRAME_POINTER_REQUIRED: Elimination. (line 8)
-* TARGET_FUNCTION_ARG: Register Arguments. (line 10)
-* TARGET_FUNCTION_ARG_ADVANCE: Register Arguments. (line 198)
-* TARGET_FUNCTION_ARG_BOUNDARY: Register Arguments. (line 252)
-* TARGET_FUNCTION_ARG_ROUND_BOUNDARY: Register Arguments. (line 258)
-* TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P: Target Attributes. (line 93)
-* TARGET_FUNCTION_INCOMING_ARG: Register Arguments. (line 71)
-* TARGET_FUNCTION_OK_FOR_SIBCALL: Tail Calls. (line 6)
-* TARGET_FUNCTION_VALUE: Scalar Return. (line 9)
-* TARGET_FUNCTION_VALUE_REGNO_P: Scalar Return. (line 96)
-* TARGET_GENERATE_VERSION_DISPATCHER_BODY: Misc. (line 752)
-* TARGET_GEN_CCMP_FIRST: Misc. (line 926)
-* TARGET_GEN_CCMP_NEXT: Misc. (line 937)
-* TARGET_GET_DRAP_RTX: Misc. (line 1108)
-* TARGET_GET_FUNCTION_VERSIONS_DISPATCHER: Misc. (line 745)
-* TARGET_GET_PCH_VALIDITY: PCH Target. (line 6)
-* TARGET_GET_RAW_ARG_MODE: Aggregate Return. (line 81)
-* TARGET_GET_RAW_RESULT_MODE: Aggregate Return. (line 76)
-* TARGET_GIMPLE_FOLD_BUILTIN: Misc. (line 729)
-* TARGET_GIMPLIFY_VA_ARG_EXPR: Register Arguments. (line 311)
-* TARGET_HANDLE_C_OPTION: Run-time Target. (line 73)
-* TARGET_HANDLE_OPTION: Run-time Target. (line 59)
+ (line 185)
+* TARGET_FLT_EVAL_METHOD: Type Layout. (line 111)
+* TARGET_FN_ABI_VA_LIST: Register Arguments. (line 303)
+* TARGET_FOLD_BUILTIN: Misc. (line 725)
+* TARGET_FORCE_AT_COMP_DIR: SDB and DWARF. (line 61)
+* TARGET_FORMAT_TYPES: Misc. (line 1005)
+* TARGET_FRAME_POINTER_REQUIRED: Elimination. (line 9)
+* TARGET_FUNCTION_ARG: Register Arguments. (line 12)
+* TARGET_FUNCTION_ARG_ADVANCE: Register Arguments. (line 201)
+* TARGET_FUNCTION_ARG_BOUNDARY: Register Arguments. (line 255)
+* TARGET_FUNCTION_ARG_ROUND_BOUNDARY: Register Arguments. (line 261)
+* TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P: Target Attributes. (line 95)
+* TARGET_FUNCTION_INCOMING_ARG: Register Arguments. (line 74)
+* TARGET_FUNCTION_OK_FOR_SIBCALL: Tail Calls. (line 8)
+* TARGET_FUNCTION_VALUE: Scalar Return. (line 11)
+* TARGET_FUNCTION_VALUE_REGNO_P: Scalar Return. (line 97)
+* TARGET_GEN_CCMP_FIRST: Misc. (line 932)
+* TARGET_GEN_CCMP_NEXT: Misc. (line 943)
+* TARGET_GENERATE_VERSION_DISPATCHER_BODY: Misc. (line 759)
+* TARGET_GET_DRAP_RTX: Misc. (line 1115)
+* TARGET_GET_FUNCTION_VERSIONS_DISPATCHER: Misc. (line 752)
+* TARGET_GET_PCH_VALIDITY: PCH Target. (line 7)
+* TARGET_GET_RAW_ARG_MODE: Aggregate Return. (line 82)
+* TARGET_GET_RAW_RESULT_MODE: Aggregate Return. (line 77)
+* TARGET_GIMPLE_FOLD_BUILTIN: Misc. (line 735)
+* TARGET_GIMPLIFY_VA_ARG_EXPR: Register Arguments. (line 314)
+* TARGET_HANDLE_C_OPTION: Run-time Target. (line 75)
+* TARGET_HANDLE_OPTION: Run-time Target. (line 62)
* TARGET_HARD_REGNO_SCRATCH_OK: Values in Registers.
- (line 141)
-* TARGET_HAS_IFUNC_P: Misc. (line 1156)
-* TARGET_HAS_NO_HW_DIVIDE: Library Calls. (line 52)
-* TARGET_HAVE_CONDITIONAL_EXECUTION: Misc. (line 920)
+ (line 144)
+* TARGET_HAS_IFUNC_P: Misc. (line 1163)
+* TARGET_HAS_NO_HW_DIVIDE: Library Calls. (line 53)
+* TARGET_HAVE_CONDITIONAL_EXECUTION: Misc. (line 925)
* TARGET_HAVE_CTORS_DTORS: Macros for Initialization.
- (line 63)
-* TARGET_HAVE_NAMED_SECTIONS: File Framework. (line 139)
-* TARGET_HAVE_SRODATA_SECTION: Sections. (line 297)
-* TARGET_HAVE_SWITCHABLE_BSS_SECTIONS: File Framework. (line 144)
-* TARGET_HAVE_TLS: Sections. (line 317)
-* TARGET_INIT_BUILTINS: Misc. (line 587)
+ (line 64)
+* TARGET_HAVE_NAMED_SECTIONS: File Framework. (line 141)
+* TARGET_HAVE_SRODATA_SECTION: Sections. (line 298)
+* TARGET_HAVE_SWITCHABLE_BSS_SECTIONS: File Framework. (line 146)
+* TARGET_HAVE_TLS: Sections. (line 318)
+* TARGET_IN_SMALL_DATA_P: Sections. (line 294)
+* TARGET_INIT_BUILTINS: Misc. (line 588)
* TARGET_INIT_DWARF_REG_SIZES_EXTRA: Exception Region Output.
- (line 119)
-* TARGET_INIT_LIBFUNCS: Library Calls. (line 15)
-* TARGET_INIT_PIC_REG: Register Arguments. (line 91)
-* TARGET_INSERT_ATTRIBUTES: Target Attributes. (line 80)
-* TARGET_INSTANTIATE_DECLS: Storage Layout. (line 521)
-* TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN: Misc. (line 1032)
-* TARGET_INVALID_BINARY_OP: Misc. (line 1051)
-* TARGET_INVALID_CONVERSION: Misc. (line 1038)
-* TARGET_INVALID_PARAMETER_TYPE: Misc. (line 1057)
-* TARGET_INVALID_RETURN_TYPE: Misc. (line 1064)
-* TARGET_INVALID_UNARY_OP: Misc. (line 1044)
-* TARGET_INVALID_WITHIN_DOLOOP: Misc. (line 776)
-* TARGET_IN_SMALL_DATA_P: Sections. (line 293)
-* TARGET_KEEP_LEAF_WHEN_PROFILED: Profiling. (line 39)
-* TARGET_LEGITIMATE_ADDRESS_P: Addressing Modes. (line 48)
-* TARGET_LEGITIMATE_COMBINED_INSN: Misc. (line 790)
-* TARGET_LEGITIMATE_CONSTANT_P: Addressing Modes. (line 213)
-* TARGET_LEGITIMIZE_ADDRESS: Addressing Modes. (line 129)
-* TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT: Register Classes. (line 589)
-* TARGET_LIBCALL_VALUE: Scalar Return. (line 65)
-* TARGET_LIBC_HAS_FUNCTION: Library Calls. (line 77)
-* TARGET_LIBFUNC_GNU_PREFIX: Library Calls. (line 24)
-* TARGET_LIBGCC_CMP_RETURN_MODE: Storage Layout. (line 463)
+ (line 121)
+* TARGET_INIT_LIBFUNCS: Library Calls. (line 16)
+* TARGET_INIT_PIC_REG: Register Arguments. (line 93)
+* TARGET_INSERT_ATTRIBUTES: Target Attributes. (line 82)
+* TARGET_INSTANTIATE_DECLS: Storage Layout. (line 526)
+* TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN: Misc. (line 1039)
+* TARGET_INVALID_BINARY_OP: Misc. (line 1058)
+* TARGET_INVALID_CONVERSION: Misc. (line 1045)
+* TARGET_INVALID_PARAMETER_TYPE: Misc. (line 1064)
+* TARGET_INVALID_RETURN_TYPE: Misc. (line 1071)
+* TARGET_INVALID_UNARY_OP: Misc. (line 1051)
+* TARGET_INVALID_WITHIN_DOLOOP: Misc. (line 783)
+* TARGET_KEEP_LEAF_WHEN_PROFILED: Profiling. (line 40)
+* TARGET_LEGITIMATE_ADDRESS_P: Addressing Modes. (line 50)
+* TARGET_LEGITIMATE_COMBINED_INSN: Misc. (line 795)
+* TARGET_LEGITIMATE_CONSTANT_P: Addressing Modes. (line 216)
+* TARGET_LEGITIMIZE_ADDRESS: Addressing Modes. (line 132)
+* TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT: Register Classes. (line 597)
+* TARGET_LIB_INT_CMP_BIASED: Library Calls. (line 43)
+* TARGET_LIBC_HAS_FUNCTION: Library Calls. (line 79)
+* TARGET_LIBCALL_VALUE: Scalar Return. (line 66)
+* TARGET_LIBFUNC_GNU_PREFIX: Library Calls. (line 25)
+* TARGET_LIBGCC_CMP_RETURN_MODE: Storage Layout. (line 468)
* TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P: Register Arguments.
- (line 369)
-* TARGET_LIBGCC_SDATA_SECTION: Sections. (line 131)
-* TARGET_LIBGCC_SHIFT_COUNT_MODE: Storage Layout. (line 469)
-* TARGET_LIB_INT_CMP_BIASED: Library Calls. (line 42)
-* TARGET_LOAD_BOUNDS_FOR_ARG: Varargs. (line 153)
-* TARGET_LOAD_RETURNED_BOUNDS: Varargs. (line 172)
-* TARGET_LOOP_UNROLL_ADJUST: Misc. (line 952)
-* TARGET_LRA_P: Register Classes. (line 548)
-* TARGET_MACHINE_DEPENDENT_REORG: Misc. (line 572)
-* TARGET_MANGLE_ASSEMBLER_NAME: Label Output. (line 328)
-* TARGET_MANGLE_DECL_ASSEMBLER_NAME: Sections. (line 241)
-* TARGET_MANGLE_TYPE: Storage Layout. (line 525)
-* TARGET_MAX_ANCHOR_OFFSET: Anchored Addresses. (line 38)
-* TARGET_MD_ASM_CLOBBERS: Misc. (line 491)
-* TARGET_MEMBER_TYPE_FORCES_BLK: Storage Layout. (line 415)
-* TARGET_MEMMODEL_CHECK: Misc. (line 1147)
-* TARGET_MEMORY_MOVE_COST: Costs. (line 79)
-* TARGET_MEM_CONSTRAINT: Addressing Modes. (line 107)
+ (line 373)
+* TARGET_LIBGCC_SDATA_SECTION: Sections. (line 132)
+* TARGET_LIBGCC_SHIFT_COUNT_MODE: Storage Layout. (line 474)
+* TARGET_LOAD_BOUNDS_FOR_ARG: Varargs. (line 158)
+* TARGET_LOAD_RETURNED_BOUNDS: Varargs. (line 177)
+* TARGET_LOOP_UNROLL_ADJUST: Misc. (line 959)
+* TARGET_LRA_P: Register Classes. (line 553)
+* TARGET_MACHINE_DEPENDENT_REORG: Misc. (line 573)
+* TARGET_MANGLE_ASSEMBLER_NAME: Label Output. (line 332)
+* TARGET_MANGLE_DECL_ASSEMBLER_NAME: Sections. (line 243)
+* TARGET_MANGLE_TYPE: Storage Layout. (line 530)
+* TARGET_MAX_ANCHOR_OFFSET: Anchored Addresses. (line 39)
+* TARGET_MD_ASM_CLOBBERS: Misc. (line 494)
+* TARGET_MEM_CONSTRAINT: Addressing Modes. (line 109)
* TARGET_MEM_REF: Storage References. (line 6)
-* TARGET_MERGE_DECL_ATTRIBUTES: Target Attributes. (line 45)
-* TARGET_MERGE_TYPE_ATTRIBUTES: Target Attributes. (line 37)
-* TARGET_MIN_ANCHOR_OFFSET: Anchored Addresses. (line 32)
-* TARGET_MIN_DIVISIONS_FOR_RECIP_MUL: Misc. (line 90)
-* TARGET_MODE_AFTER: Mode Switching. (line 57)
-* TARGET_MODE_DEPENDENT_ADDRESS_P: Addressing Modes. (line 196)
-* TARGET_MODE_EMIT: Mode Switching. (line 42)
-* TARGET_MODE_ENTRY: Mode Switching. (line 64)
-* TARGET_MODE_EXIT: Mode Switching. (line 71)
-* TARGET_MODE_NEEDED: Mode Switching. (line 50)
-* TARGET_MODE_PRIORITY: Mode Switching. (line 78)
-* TARGET_MODE_REP_EXTENDED: Misc. (line 175)
-* TARGET_MS_BITFIELD_LAYOUT_P: Storage Layout. (line 479)
-* TARGET_MUST_PASS_IN_STACK: Register Arguments. (line 64)
-* 'TARGET_MUST_PASS_IN_STACK', and 'TARGET_FUNCTION_ARG': Register Arguments.
- (line 56)
-* TARGET_NARROW_VOLATILE_BITFIELD: Storage Layout. (line 408)
-* TARGET_NO_REGISTER_ALLOCATION: SDB and DWARF. (line 73)
-* TARGET_N_FORMAT_TYPES: Misc. (line 1004)
-* TARGET_OBJC_CONSTRUCT_STRING_OBJECT: Run-time Target. (line 88)
-* TARGET_OBJC_DECLARE_CLASS_DEFINITION: Run-time Target. (line 109)
+* TARGET_MEMBER_TYPE_FORCES_BLK: Storage Layout. (line 421)
+* TARGET_MEMMODEL_CHECK: Misc. (line 1155)
+* TARGET_MEMORY_MOVE_COST: Costs. (line 81)
+* TARGET_MERGE_DECL_ATTRIBUTES: Target Attributes. (line 47)
+* TARGET_MERGE_TYPE_ATTRIBUTES: Target Attributes. (line 39)
+* TARGET_MIN_ANCHOR_OFFSET: Anchored Addresses. (line 33)
+* TARGET_MIN_DIVISIONS_FOR_RECIP_MUL: Misc. (line 92)
+* TARGET_MODE_AFTER: Mode Switching. (line 59)
+* TARGET_MODE_DEPENDENT_ADDRESS_P: Addressing Modes. (line 199)
+* TARGET_MODE_EMIT: Mode Switching. (line 44)
+* TARGET_MODE_ENTRY: Mode Switching. (line 65)
+* TARGET_MODE_EXIT: Mode Switching. (line 72)
+* TARGET_MODE_NEEDED: Mode Switching. (line 51)
+* TARGET_MODE_PRIORITY: Mode Switching. (line 79)
+* TARGET_MODE_REP_EXTENDED: Misc. (line 177)
+* TARGET_MS_BITFIELD_LAYOUT_P: Storage Layout. (line 485)
+* TARGET_MUST_PASS_IN_STACK: Register Arguments. (line 67)
+* TARGET_MUST_PASS_IN_STACK, and TARGET_FUNCTION_ARG: Register Arguments.
+ (line 57)
+* TARGET_N_FORMAT_TYPES: Misc. (line 1010)
+* TARGET_NARROW_VOLATILE_BITFIELD: Storage Layout. (line 412)
+* TARGET_NO_REGISTER_ALLOCATION: SDB and DWARF. (line 74)
+* TARGET_OBJC_CONSTRUCT_STRING_OBJECT: Run-time Target. (line 90)
+* TARGET_OBJC_DECLARE_CLASS_DEFINITION: Run-time Target. (line 111)
* TARGET_OBJC_DECLARE_UNRESOLVED_CLASS_REFERENCE: Run-time Target.
- (line 104)
-* TARGET_OBJECT_SUFFIX: Misc. (line 855)
-* TARGET_OBJFMT_CPP_BUILTINS: Run-time Target. (line 45)
-* TARGET_OFFLOAD_OPTIONS: Misc. (line 1190)
+ (line 106)
+* TARGET_OBJECT_SUFFIX: Misc. (line 859)
+* TARGET_OBJFMT_CPP_BUILTINS: Run-time Target. (line 46)
+* TARGET_OFFLOAD_OPTIONS: Misc. (line 1199)
* TARGET_OMIT_STRUCT_RETURN_REG: Scalar Return. (line 117)
-* TARGET_OPTF: Misc. (line 986)
-* TARGET_OPTION_DEFAULT_PARAMS: Run-time Target. (line 160)
-* TARGET_OPTION_FUNCTION_VERSIONS: Target Attributes. (line 157)
-* TARGET_OPTION_INIT_STRUCT: Run-time Target. (line 156)
-* TARGET_OPTION_OPTIMIZATION_TABLE: Run-time Target. (line 142)
-* TARGET_OPTION_OVERRIDE: Target Attributes. (line 144)
-* TARGET_OPTION_POST_STREAM_IN: Target Attributes. (line 125)
-* TARGET_OPTION_PRAGMA_PARSE: Target Attributes. (line 137)
-* TARGET_OPTION_PRINT: Target Attributes. (line 131)
-* TARGET_OPTION_RESTORE: Target Attributes. (line 119)
-* TARGET_OPTION_SAVE: Target Attributes. (line 112)
-* TARGET_OPTION_VALID_ATTRIBUTE_P: Target Attributes. (line 100)
-* TARGET_OS_CPP_BUILTINS: Run-time Target. (line 41)
-* TARGET_OVERRIDES_FORMAT_ATTRIBUTES: Misc. (line 1008)
-* TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT: Misc. (line 1014)
-* TARGET_OVERRIDES_FORMAT_INIT: Misc. (line 1018)
-* TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE: Run-time Target. (line 126)
-* TARGET_PASS_BY_REFERENCE: Register Arguments. (line 115)
-* TARGET_PCH_VALID_P: PCH Target. (line 11)
-* TARGET_POSIX_IO: Misc. (line 516)
-* TARGET_PREFERRED_OUTPUT_RELOAD_CLASS: Register Classes. (line 284)
-* TARGET_PREFERRED_RELOAD_CLASS: Register Classes. (line 213)
-* TARGET_PREFERRED_RENAME_CLASS: Register Classes. (line 201)
-* TARGET_PREPARE_PCH_SAVE: PCH Target. (line 34)
-* TARGET_PRETEND_OUTGOING_VARARGS_NAMED: Varargs. (line 144)
-* TARGET_PROFILE_BEFORE_PROLOGUE: Sections. (line 301)
-* TARGET_PROMOTED_TYPE: Misc. (line 1071)
-* TARGET_PROMOTE_FUNCTION_MODE: Storage Layout. (line 109)
-* TARGET_PROMOTE_PROTOTYPES: Stack Arguments. (line 10)
-* TARGET_PTRMEMFUNC_VBIT_LOCATION: Type Layout. (line 256)
-* TARGET_RECORD_OFFLOAD_SYMBOL: Misc. (line 1185)
-* TARGET_REF_MAY_ALIAS_ERRNO: Register Arguments. (line 322)
-* TARGET_REGISTER_MOVE_COST: Costs. (line 31)
-* TARGET_REGISTER_PRIORITY: Register Classes. (line 553)
-* TARGET_REGISTER_USAGE_LEVELING_P: Register Classes. (line 564)
-* TARGET_RELAXED_ORDERING: Misc. (line 1023)
-* TARGET_RESOLVE_OVERLOADED_BUILTIN: Misc. (line 708)
-* TARGET_RETURN_IN_MEMORY: Aggregate Return. (line 15)
+* TARGET_OPTF: Misc. (line 992)
+* TARGET_OPTION_DEFAULT_PARAMS: Run-time Target. (line 161)
+* TARGET_OPTION_FUNCTION_VERSIONS: Target Attributes. (line 159)
+* TARGET_OPTION_INIT_STRUCT: Run-time Target. (line 158)
+* TARGET_OPTION_OPTIMIZATION_TABLE: Run-time Target. (line 144)
+* TARGET_OPTION_OVERRIDE: Target Attributes. (line 145)
+* TARGET_OPTION_POST_STREAM_IN: Target Attributes. (line 127)
+* TARGET_OPTION_PRAGMA_PARSE: Target Attributes. (line 139)
+* TARGET_OPTION_PRINT: Target Attributes. (line 133)
+* TARGET_OPTION_RESTORE: Target Attributes. (line 121)
+* TARGET_OPTION_SAVE: Target Attributes. (line 114)
+* TARGET_OPTION_VALID_ATTRIBUTE_P: Target Attributes. (line 102)
+* TARGET_OS_CPP_BUILTINS: Run-time Target. (line 42)
+* TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE: Run-time Target. (line 127)
+* TARGET_OVERRIDES_FORMAT_ATTRIBUTES: Misc. (line 1014)
+* TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT: Misc. (line 1020)
+* TARGET_OVERRIDES_FORMAT_INIT: Misc. (line 1024)
+* TARGET_PASS_BY_REFERENCE: Register Arguments. (line 118)
+* TARGET_PCH_VALID_P: PCH Target. (line 13)
+* TARGET_POSIX_IO: Misc. (line 518)
+* TARGET_PREFERRED_OUTPUT_RELOAD_CLASS: Register Classes. (line 289)
+* TARGET_PREFERRED_RELOAD_CLASS: Register Classes. (line 218)
+* TARGET_PREFERRED_RENAME_CLASS: Register Classes. (line 206)
+* TARGET_PREPARE_PCH_SAVE: PCH Target. (line 35)
+* TARGET_PRETEND_OUTGOING_VARARGS_NAMED: Varargs. (line 149)
+* TARGET_PROFILE_BEFORE_PROLOGUE: Sections. (line 302)
+* TARGET_PROMOTE_FUNCTION_MODE: Storage Layout. (line 113)
+* TARGET_PROMOTE_PROTOTYPES: Stack Arguments. (line 11)
+* TARGET_PROMOTED_TYPE: Misc. (line 1077)
+* TARGET_PTRMEMFUNC_VBIT_LOCATION: Type Layout. (line 258)
+* TARGET_RECORD_OFFLOAD_SYMBOL: Misc. (line 1193)
+* TARGET_REF_MAY_ALIAS_ERRNO: Register Arguments. (line 325)
+* TARGET_REGISTER_MOVE_COST: Costs. (line 33)
+* TARGET_REGISTER_PRIORITY: Register Classes. (line 558)
+* TARGET_REGISTER_USAGE_LEVELING_P: Register Classes. (line 570)
+* TARGET_RELAXED_ORDERING: Misc. (line 1029)
+* TARGET_RESOLVE_OVERLOADED_BUILTIN: Misc. (line 714)
+* TARGET_RETURN_IN_MEMORY: Aggregate Return. (line 17)
* TARGET_RETURN_IN_MSB: Scalar Return. (line 124)
-* TARGET_RETURN_POPS_ARGS: Stack Arguments. (line 98)
-* TARGET_RTX_COSTS: Costs. (line 277)
-* TARGET_SCALAR_MODE_SUPPORTED_P: Register Arguments. (line 329)
-* TARGET_SCHED_ADJUST_COST: Scheduling. (line 35)
-* TARGET_SCHED_ADJUST_PRIORITY: Scheduling. (line 50)
-* TARGET_SCHED_ALLOC_SCHED_CONTEXT: Scheduling. (line 294)
-* TARGET_SCHED_CLEAR_SCHED_CONTEXT: Scheduling. (line 309)
-* TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK: Scheduling. (line 101)
-* TARGET_SCHED_DFA_NEW_CYCLE: Scheduling. (line 255)
-* TARGET_SCHED_DFA_POST_ADVANCE_CYCLE: Scheduling. (line 172)
-* TARGET_SCHED_DFA_POST_CYCLE_INSN: Scheduling. (line 156)
-* TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE: Scheduling. (line 165)
-* TARGET_SCHED_DFA_PRE_CYCLE_INSN: Scheduling. (line 144)
-* TARGET_SCHED_DISPATCH: Scheduling. (line 363)
-* TARGET_SCHED_DISPATCH_DO: Scheduling. (line 368)
-* TARGET_SCHED_EXPOSED_PIPELINE: Scheduling. (line 372)
-* TARGET_SCHED_FINISH: Scheduling. (line 122)
-* TARGET_SCHED_FINISH_GLOBAL: Scheduling. (line 137)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK: Scheduling. (line 235)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BEGIN: Scheduling. (line 223)
+* TARGET_RETURN_POPS_ARGS: Stack Arguments. (line 100)
+* TARGET_RTX_COSTS: Costs. (line 279)
+* TARGET_SCALAR_MODE_SUPPORTED_P: Register Arguments. (line 332)
+* TARGET_SCHED_ADJUST_COST: Scheduling. (line 37)
+* TARGET_SCHED_ADJUST_PRIORITY: Scheduling. (line 52)
+* TARGET_SCHED_ALLOC_SCHED_CONTEXT: Scheduling. (line 297)
+* TARGET_SCHED_CLEAR_SCHED_CONTEXT: Scheduling. (line 312)
+* TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK: Scheduling. (line 103)
+* TARGET_SCHED_DFA_NEW_CYCLE: Scheduling. (line 258)
+* TARGET_SCHED_DFA_POST_ADVANCE_CYCLE: Scheduling. (line 174)
+* TARGET_SCHED_DFA_POST_CYCLE_INSN: Scheduling. (line 158)
+* TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE: Scheduling. (line 167)
+* TARGET_SCHED_DFA_PRE_CYCLE_INSN: Scheduling. (line 146)
+* TARGET_SCHED_DISPATCH: Scheduling. (line 366)
+* TARGET_SCHED_DISPATCH_DO: Scheduling. (line 371)
+* TARGET_SCHED_EXPOSED_PIPELINE: Scheduling. (line 375)
+* TARGET_SCHED_FINISH: Scheduling. (line 123)
+* TARGET_SCHED_FINISH_GLOBAL: Scheduling. (line 140)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK: Scheduling. (line 237)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BEGIN: Scheduling. (line 226)
* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD: Scheduling.
- (line 179)
+ (line 182)
* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD: Scheduling.
- (line 207)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END: Scheduling. (line 240)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_FINI: Scheduling. (line 250)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_INIT: Scheduling. (line 245)
-* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE: Scheduling. (line 229)
-* TARGET_SCHED_FREE_SCHED_CONTEXT: Scheduling. (line 313)
-* TARGET_SCHED_FUSION_PRIORITY: Scheduling. (line 382)
-* TARGET_SCHED_GEN_SPEC_CHECK: Scheduling. (line 335)
-* TARGET_SCHED_H_I_D_EXTENDED: Scheduling. (line 289)
-* TARGET_SCHED_INIT: Scheduling. (line 111)
-* TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN: Scheduling. (line 161)
-* TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN: Scheduling. (line 153)
-* TARGET_SCHED_INIT_GLOBAL: Scheduling. (line 129)
-* TARGET_SCHED_INIT_SCHED_CONTEXT: Scheduling. (line 298)
-* TARGET_SCHED_ISSUE_RATE: Scheduling. (line 11)
-* TARGET_SCHED_IS_COSTLY_DEPENDENCE: Scheduling. (line 267)
-* TARGET_SCHED_MACRO_FUSION_P: Scheduling. (line 87)
-* TARGET_SCHED_MACRO_FUSION_PAIR_P: Scheduling. (line 91)
-* TARGET_SCHED_NEEDS_BLOCK_P: Scheduling. (line 328)
-* TARGET_SCHED_REASSOCIATION_WIDTH: Scheduling. (line 377)
-* TARGET_SCHED_REORDER: Scheduling. (line 58)
-* TARGET_SCHED_REORDER2: Scheduling. (line 75)
-* TARGET_SCHED_SET_SCHED_CONTEXT: Scheduling. (line 305)
-* TARGET_SCHED_SET_SCHED_FLAGS: Scheduling. (line 347)
-* TARGET_SCHED_SMS_RES_MII: Scheduling. (line 354)
-* TARGET_SCHED_SPECULATE_INSN: Scheduling. (line 316)
-* TARGET_SCHED_VARIABLE_ISSUE: Scheduling. (line 22)
-* TARGET_SECONDARY_RELOAD: Register Classes. (line 312)
-* TARGET_SECTION_TYPE_FLAGS: File Framework. (line 149)
-* TARGET_SETUP_INCOMING_VARARGS: Varargs. (line 71)
-* TARGET_SETUP_INCOMING_VARARG_BOUNDS: Varargs. (line 188)
-* TARGET_SET_CURRENT_FUNCTION: Misc. (line 837)
-* TARGET_SET_DEFAULT_TYPE_ATTRIBUTES: Target Attributes. (line 33)
-* TARGET_SET_UP_BY_PROLOGUE: Tail Calls. (line 29)
-* TARGET_SHIFT_TRUNCATION_MASK: Misc. (line 138)
-* TARGET_SIMD_CLONE_ADJUST: Addressing Modes. (line 413)
+ (line 211)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END: Scheduling. (line 242)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_FINI: Scheduling. (line 252)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_INIT: Scheduling. (line 247)
+* TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE: Scheduling. (line 232)
+* TARGET_SCHED_FREE_SCHED_CONTEXT: Scheduling. (line 316)
+* TARGET_SCHED_FUSION_PRIORITY: Scheduling. (line 386)
+* TARGET_SCHED_GEN_SPEC_CHECK: Scheduling. (line 339)
+* TARGET_SCHED_H_I_D_EXTENDED: Scheduling. (line 292)
+* TARGET_SCHED_INIT: Scheduling. (line 113)
+* TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN: Scheduling. (line 163)
+* TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN: Scheduling. (line 155)
+* TARGET_SCHED_INIT_GLOBAL: Scheduling. (line 132)
+* TARGET_SCHED_INIT_SCHED_CONTEXT: Scheduling. (line 302)
+* TARGET_SCHED_IS_COSTLY_DEPENDENCE: Scheduling. (line 269)
+* TARGET_SCHED_ISSUE_RATE: Scheduling. (line 12)
+* TARGET_SCHED_MACRO_FUSION_P: Scheduling. (line 88)
+* TARGET_SCHED_MACRO_FUSION_PAIR_P: Scheduling. (line 93)
+* TARGET_SCHED_NEEDS_BLOCK_P: Scheduling. (line 332)
+* TARGET_SCHED_REASSOCIATION_WIDTH: Scheduling. (line 381)
+* TARGET_SCHED_REORDER: Scheduling. (line 60)
+* TARGET_SCHED_REORDER2: Scheduling. (line 77)
+* TARGET_SCHED_SET_SCHED_CONTEXT: Scheduling. (line 308)
+* TARGET_SCHED_SET_SCHED_FLAGS: Scheduling. (line 351)
+* TARGET_SCHED_SMS_RES_MII: Scheduling. (line 357)
+* TARGET_SCHED_SPECULATE_INSN: Scheduling. (line 320)
+* TARGET_SCHED_VARIABLE_ISSUE: Scheduling. (line 24)
+* TARGET_SECONDARY_RELOAD: Register Classes. (line 318)
+* TARGET_SECTION_TYPE_FLAGS: File Framework. (line 152)
+* TARGET_SET_CURRENT_FUNCTION: Misc. (line 841)
+* TARGET_SET_DEFAULT_TYPE_ATTRIBUTES: Target Attributes. (line 34)
+* TARGET_SET_UP_BY_PROLOGUE: Tail Calls. (line 31)
+* TARGET_SETUP_INCOMING_VARARG_BOUNDS: Varargs. (line 195)
+* TARGET_SETUP_INCOMING_VARARGS: Varargs. (line 76)
+* TARGET_SHIFT_TRUNCATION_MASK: Misc. (line 140)
+* TARGET_SIMD_CLONE_ADJUST: Addressing Modes. (line 418)
* TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN: Addressing Modes.
- (line 405)
-* TARGET_SIMD_CLONE_USABLE: Addressing Modes. (line 417)
+ (line 411)
+* TARGET_SIMD_CLONE_USABLE: Addressing Modes. (line 422)
* TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P: Register Arguments.
- (line 377)
-* TARGET_SPILL_CLASS: Register Classes. (line 597)
-* TARGET_SPLIT_COMPLEX_ARG: Register Arguments. (line 273)
+ (line 381)
+* TARGET_SPILL_CLASS: Register Classes. (line 605)
+* TARGET_SPLIT_COMPLEX_ARG: Register Arguments. (line 275)
* TARGET_STACK_PROTECT_FAIL: Stack Smashing Protection.
- (line 16)
+ (line 17)
* TARGET_STACK_PROTECT_GUARD: Stack Smashing Protection.
- (line 6)
-* TARGET_STATIC_CHAIN: Frame Registers. (line 90)
-* TARGET_STORE_BOUNDS_FOR_ARG: Varargs. (line 163)
-* TARGET_STORE_RETURNED_BOUNDS: Varargs. (line 177)
-* TARGET_STRICT_ARGUMENT_NAMING: Varargs. (line 107)
-* TARGET_STRING_OBJECT_REF_TYPE_P: Run-time Target. (line 114)
-* TARGET_STRIP_NAME_ENCODING: Sections. (line 288)
-* TARGET_STRUCT_VALUE_RTX: Aggregate Return. (line 44)
+ (line 7)
+* TARGET_STATIC_CHAIN: Frame Registers. (line 92)
+* TARGET_STORE_BOUNDS_FOR_ARG: Varargs. (line 168)
+* TARGET_STORE_RETURNED_BOUNDS: Varargs. (line 183)
+* TARGET_STRICT_ARGUMENT_NAMING: Varargs. (line 112)
+* TARGET_STRING_OBJECT_REF_TYPE_P: Run-time Target. (line 116)
+* TARGET_STRIP_NAME_ENCODING: Sections. (line 290)
+* TARGET_STRUCT_VALUE_RTX: Aggregate Return. (line 45)
* TARGET_SUPPORTS_SPLIT_STACK: Stack Smashing Protection.
- (line 25)
-* TARGET_SUPPORTS_WEAK: Label Output. (line 244)
-* TARGET_SUPPORTS_WIDE_INT: Misc. (line 1198)
+ (line 27)
+* TARGET_SUPPORTS_WEAK: Label Output. (line 248)
+* TARGET_SUPPORTS_WIDE_INT: Misc. (line 1208)
* TARGET_TERMINATE_DW2_EH_FRAME_INFO: Exception Region Output.
- (line 98)
-* TARGET_TRAMPOLINE_ADJUST_ADDRESS: Trampolines. (line 74)
-* TARGET_TRAMPOLINE_INIT: Trampolines. (line 54)
-* TARGET_UNSPEC_MAY_TRAP_P: Misc. (line 828)
+ (line 100)
+* TARGET_TRAMPOLINE_ADJUST_ADDRESS: Trampolines. (line 75)
+* TARGET_TRAMPOLINE_INIT: Trampolines. (line 56)
+* TARGET_UNSPEC_MAY_TRAP_P: Misc. (line 833)
* TARGET_UNWIND_TABLES_DEFAULT: Exception Region Output.
- (line 72)
-* TARGET_UNWIND_WORD_MODE: Storage Layout. (line 475)
-* TARGET_UPDATE_STACK_BOUNDARY: Misc. (line 1104)
-* TARGET_USES_WEAK_UNWIND_INFO: Exception Handling. (line 123)
-* TARGET_USE_ANCHORS_FOR_SYMBOL_P: Anchored Addresses. (line 53)
-* TARGET_USE_BLOCKS_FOR_CONSTANT_P: Addressing Modes. (line 248)
-* TARGET_USE_BLOCKS_FOR_DECL_P: Addressing Modes. (line 255)
-* TARGET_USE_BY_PIECES_INFRASTRUCTURE_P: Costs. (line 164)
-* TARGET_USE_JCR_SECTION: Misc. (line 1086)
-* TARGET_USE_PSEUDO_PIC_REG: Register Arguments. (line 87)
-* TARGET_VALID_DLLIMPORT_ATTRIBUTE_P: Target Attributes. (line 66)
-* TARGET_VALID_POINTER_MODE: Register Arguments. (line 317)
-* TARGET_VECTORIZE_ADD_STMT_COST: Addressing Modes. (line 367)
+ (line 74)
+* TARGET_UNWIND_WORD_MODE: Storage Layout. (line 480)
+* TARGET_UPDATE_STACK_BOUNDARY: Misc. (line 1111)
+* TARGET_USE_ANCHORS_FOR_SYMBOL_P: Anchored Addresses. (line 55)
+* TARGET_USE_BLOCKS_FOR_CONSTANT_P: Addressing Modes. (line 251)
+* TARGET_USE_BLOCKS_FOR_DECL_P: Addressing Modes. (line 257)
+* TARGET_USE_BY_PIECES_INFRASTRUCTURE_P: Costs. (line 167)
+* TARGET_USE_JCR_SECTION: Misc. (line 1093)
+* TARGET_USE_PSEUDO_PIC_REG: Register Arguments. (line 89)
+* TARGET_USES_WEAK_UNWIND_INFO: Exception Handling. (line 126)
+* TARGET_VALID_DLLIMPORT_ATTRIBUTE_P: Target Attributes. (line 68)
+* TARGET_VALID_POINTER_MODE: Register Arguments. (line 320)
+* TARGET_VECTOR_ALIGNMENT: Storage Layout. (line 272)
+* TARGET_VECTOR_MODE_SUPPORTED_P: Register Arguments. (line 343)
+* TARGET_VECTORIZE_ADD_STMT_COST: Addressing Modes. (line 373)
* TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES: Addressing Modes.
- (line 350)
-* TARGET_VECTORIZE_BUILTIN_CONVERSION: Addressing Modes. (line 312)
-* TARGET_VECTORIZE_BUILTIN_GATHER: Addressing Modes. (line 398)
-* TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD: Addressing Modes. (line 271)
-* TARGET_VECTORIZE_BUILTIN_TM_LOAD: Addressing Modes. (line 390)
-* TARGET_VECTORIZE_BUILTIN_TM_STORE: Addressing Modes. (line 394)
+ (line 353)
+* TARGET_VECTORIZE_BUILTIN_CONVERSION: Addressing Modes. (line 315)
+* TARGET_VECTORIZE_BUILTIN_GATHER: Addressing Modes. (line 404)
+* TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD: Addressing Modes. (line 273)
+* TARGET_VECTORIZE_BUILTIN_TM_LOAD: Addressing Modes. (line 395)
+* TARGET_VECTORIZE_BUILTIN_TM_STORE: Addressing Modes. (line 399)
* TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST: Addressing Modes.
- (line 297)
+ (line 300)
* TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION: Addressing Modes.
- (line 324)
-* TARGET_VECTORIZE_DESTROY_COST_DATA: Addressing Modes. (line 385)
-* TARGET_VECTORIZE_FINISH_COST: Addressing Modes. (line 378)
-* TARGET_VECTORIZE_INIT_COST: Addressing Modes. (line 358)
-* TARGET_VECTORIZE_PREFERRED_SIMD_MODE: Addressing Modes. (line 343)
+ (line 327)
+* TARGET_VECTORIZE_DESTROY_COST_DATA: Addressing Modes. (line 390)
+* TARGET_VECTORIZE_FINISH_COST: Addressing Modes. (line 384)
+* TARGET_VECTORIZE_INIT_COST: Addressing Modes. (line 361)
+* TARGET_VECTORIZE_PREFERRED_SIMD_MODE: Addressing Modes. (line 346)
* TARGET_VECTORIZE_SUPPORT_VECTOR_MISALIGNMENT: Addressing Modes.
- (line 333)
+ (line 337)
+* TARGET_VECTORIZE_VEC_PERM_CONST_OK: Addressing Modes. (line 311)
* TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE: Addressing Modes.
- (line 303)
-* TARGET_VECTORIZE_VEC_PERM_CONST_OK: Addressing Modes. (line 308)
-* TARGET_VECTOR_ALIGNMENT: Storage Layout. (line 268)
-* TARGET_VECTOR_MODE_SUPPORTED_P: Register Arguments. (line 340)
-* TARGET_VTABLE_DATA_ENTRY_DISTANCE: Type Layout. (line 309)
-* TARGET_VTABLE_ENTRY_ALIGN: Type Layout. (line 303)
-* TARGET_VTABLE_USES_DESCRIPTORS: Type Layout. (line 292)
-* TARGET_WANT_DEBUG_PUB_SECTIONS: SDB and DWARF. (line 55)
-* TARGET_WARN_FUNC_RETURN: Tail Calls. (line 35)
-* TARGET_WEAK_NOT_IN_ARCHIVE_TOC: Label Output. (line 280)
-* TCmode: Machine Modes. (line 199)
+ (line 306)
+* TARGET_VTABLE_DATA_ENTRY_DISTANCE: Type Layout. (line 311)
+* TARGET_VTABLE_ENTRY_ALIGN: Type Layout. (line 305)
+* TARGET_VTABLE_USES_DESCRIPTORS: Type Layout. (line 294)
+* TARGET_WANT_DEBUG_PUB_SECTIONS: SDB and DWARF. (line 56)
+* TARGET_WARN_FUNC_RETURN: Tail Calls. (line 36)
+* TARGET_WEAK_NOT_IN_ARCHIVE_TOC: Label Output. (line 284)
+* targetm: Target Structure. (line 7)
+* targets, makefile: Makefile. (line 6)
+* TCmode: Machine Modes. (line 200)
* TDmode: Machine Modes. (line 97)
* TEMPLATE_DECL: Declarations. (line 6)
* Temporaries: Temporaries. (line 6)
* termination routines: Initialization. (line 6)
* testing constraints: C Constraint Interface.
(line 6)
-* TEXT_SECTION_ASM_OP: Sections. (line 37)
+* TEXT_SECTION_ASM_OP: Sections. (line 38)
* TFmode: Machine Modes. (line 101)
* The Language: The Language. (line 6)
* THEN_CLAUSE: Statements for C++. (line 6)
-* THREAD_MODEL_SPEC: Driver. (line 162)
+* THREAD_MODEL_SPEC: Driver. (line 163)
* THROW_EXPR: Unary and Binary Expressions.
(line 6)
* THUNK_DECL: Declarations. (line 6)
* THUNK_DELTA: Declarations. (line 6)
* TImode: Machine Modes. (line 48)
-* 'TImode', in 'insn': Insns. (line 268)
-* TLS_COMMON_ASM_OP: Sections. (line 80)
-* TLS_SECTION_ASM_FLAG: Sections. (line 85)
-* 'tm.h' macros: Target Macros. (line 6)
+* TImode, in insn: Insns. (line 272)
+* TLS_COMMON_ASM_OP: Sections. (line 81)
+* TLS_SECTION_ASM_FLAG: Sections. (line 86)
+* tm.h macros: Target Macros. (line 6)
* TQFmode: Machine Modes. (line 65)
* TQmode: Machine Modes. (line 122)
+* TRAMPOLINE_ALIGNMENT: Trampolines. (line 49)
+* TRAMPOLINE_SECTION: Trampolines. (line 40)
+* TRAMPOLINE_SIZE: Trampolines. (line 45)
* trampolines for nested functions: Trampolines. (line 6)
-* TRAMPOLINE_ALIGNMENT: Trampolines. (line 48)
-* TRAMPOLINE_SECTION: Trampolines. (line 39)
-* TRAMPOLINE_SIZE: Trampolines. (line 44)
-* TRANSFER_FROM_TRAMPOLINE: Trampolines. (line 110)
-* 'trap' instruction pattern: Standard Names. (line 1573)
-* tree: Tree overview. (line 6)
+* TRANSFER_FROM_TRAMPOLINE: Trampolines. (line 111)
+* trap instruction pattern: Standard Names. (line 1583)
* tree <1>: Macros and Functions.
(line 6)
+* tree: Tree overview. (line 6)
* Tree SSA: Tree SSA. (line 6)
* TREE_CHAIN: Macros and Functions.
(line 6)
@@ -50376,9 +50761,9 @@ Concept Index
(line 6)
* TREE_LIST: Containers. (line 6)
* TREE_OPERAND: Expression trees. (line 6)
-* TREE_PUBLIC: Function Basics. (line 6)
* TREE_PUBLIC <1>: Function Properties.
(line 28)
+* TREE_PUBLIC: Function Basics. (line 6)
* TREE_PURPOSE: Containers. (line 6)
* TREE_READONLY: Function Properties.
(line 37)
@@ -50396,36 +50781,35 @@ Concept Index
(line 6)
* tree_to_uhwi: Constant expressions.
(line 6)
+* TREE_TYPE <1>: Types for C++. (line 6)
+* TREE_TYPE <2>: Function Basics. (line 47)
+* TREE_TYPE <3>: Expression trees. (line 6)
+* TREE_TYPE <4>: Working with declarations.
+ (line 11)
+* TREE_TYPE <5>: Types. (line 6)
* TREE_TYPE: Macros and Functions.
(line 6)
-* TREE_TYPE <1>: Types. (line 6)
-* TREE_TYPE <2>: Working with declarations.
- (line 11)
-* TREE_TYPE <3>: Expression trees. (line 6)
-* TREE_TYPE <4>: Expression trees. (line 17)
-* TREE_TYPE <5>: Function Basics. (line 47)
-* TREE_TYPE <6>: Types for C++. (line 6)
* TREE_VALUE: Containers. (line 6)
* TREE_VEC: Containers. (line 6)
* TREE_VEC_ELT: Containers. (line 6)
* TREE_VEC_LENGTH: Containers. (line 6)
-* TRULY_NOOP_TRUNCATION: Misc. (line 162)
-* truncate: Conversions. (line 38)
-* 'truncMN2' instruction pattern: Standard Names. (line 947)
+* TRULY_NOOP_TRUNCATION: Misc. (line 163)
* TRUNC_DIV_EXPR: Unary and Binary Expressions.
(line 6)
* TRUNC_MOD_EXPR: Unary and Binary Expressions.
(line 6)
-* TRUTH_ANDIF_EXPR: Unary and Binary Expressions.
- (line 6)
+* truncate: Conversions. (line 38)
+* truncMN2 instruction pattern: Standard Names. (line 952)
* TRUTH_AND_EXPR: Unary and Binary Expressions.
(line 6)
-* TRUTH_NOT_EXPR: Unary and Binary Expressions.
+* TRUTH_ANDIF_EXPR: Unary and Binary Expressions.
(line 6)
-* TRUTH_ORIF_EXPR: Unary and Binary Expressions.
+* TRUTH_NOT_EXPR: Unary and Binary Expressions.
(line 6)
* TRUTH_OR_EXPR: Unary and Binary Expressions.
(line 6)
+* TRUTH_ORIF_EXPR: Unary and Binary Expressions.
+ (line 6)
* TRUTH_XOR_EXPR: Unary and Binary Expressions.
(line 6)
* TRY_BLOCK: Statements for C++. (line 6)
@@ -50437,292 +50821,270 @@ Concept Index
(line 6)
* type: Types. (line 6)
* type declaration: Declarations. (line 6)
-* TYPENAME_TYPE: Types for C++. (line 6)
-* TYPENAME_TYPE_FULLNAME: Types. (line 6)
-* TYPENAME_TYPE_FULLNAME <1>: Types for C++. (line 6)
-* TYPEOF_TYPE: Types for C++. (line 6)
+* TYPE_ALIGN <1>: Types for C++. (line 6)
* TYPE_ALIGN: Types. (line 6)
-* TYPE_ALIGN <1>: Types. (line 30)
-* TYPE_ALIGN <2>: Types for C++. (line 6)
-* TYPE_ALIGN <3>: Types for C++. (line 44)
-* TYPE_ARG_TYPES: Types. (line 6)
* TYPE_ARG_TYPES <1>: Types for C++. (line 6)
-* TYPE_ASM_OP: Label Output. (line 76)
-* TYPE_ATTRIBUTES: Attributes. (line 24)
+* TYPE_ARG_TYPES: Types. (line 6)
+* TYPE_ASM_OP: Label Output. (line 79)
+* TYPE_ATTRIBUTES: Attributes. (line 25)
* TYPE_BINFO: Classes. (line 6)
-* TYPE_BUILT_IN: Types for C++. (line 66)
+* TYPE_BUILT_IN: Types for C++. (line 68)
* TYPE_CANONICAL: Types. (line 6)
-* TYPE_CANONICAL <1>: Types. (line 41)
-* TYPE_CONTEXT: Types. (line 6)
* TYPE_CONTEXT <1>: Types for C++. (line 6)
+* TYPE_CONTEXT: Types. (line 6)
* TYPE_DECL: Declarations. (line 6)
+* TYPE_FIELDS <1>: Classes. (line 6)
+* TYPE_FIELDS <2>: Types for C++. (line 6)
* TYPE_FIELDS: Types. (line 6)
-* TYPE_FIELDS <1>: Types for C++. (line 6)
-* TYPE_FIELDS <2>: Classes. (line 6)
* TYPE_HAS_ARRAY_NEW_OPERATOR: Classes. (line 96)
* TYPE_HAS_DEFAULT_CONSTRUCTOR: Classes. (line 81)
* TYPE_HAS_MUTABLE_P: Classes. (line 86)
* TYPE_HAS_NEW_OPERATOR: Classes. (line 93)
+* TYPE_MAIN_VARIANT <1>: Types for C++. (line 6)
* TYPE_MAIN_VARIANT: Types. (line 6)
-* TYPE_MAIN_VARIANT <1>: Types. (line 19)
-* TYPE_MAIN_VARIANT <2>: Types for C++. (line 6)
* TYPE_MAX_VALUE: Types. (line 6)
-* TYPE_METHODS: Classes. (line 6)
-* TYPE_METHOD_BASETYPE: Types. (line 6)
* TYPE_METHOD_BASETYPE <1>: Types for C++. (line 6)
+* TYPE_METHOD_BASETYPE: Types. (line 6)
+* TYPE_METHODS: Classes. (line 6)
* TYPE_MIN_VALUE: Types. (line 6)
+* TYPE_NAME <1>: Types for C++. (line 6)
* TYPE_NAME: Types. (line 6)
-* TYPE_NAME <1>: Types. (line 33)
-* TYPE_NAME <2>: Types for C++. (line 6)
-* TYPE_NAME <3>: Types for C++. (line 47)
* TYPE_NOTHROW_P: Functions for C++. (line 154)
-* TYPE_OFFSET_BASETYPE: Types. (line 6)
* TYPE_OFFSET_BASETYPE <1>: Types for C++. (line 6)
-* TYPE_OPERAND_FMT: Label Output. (line 87)
+* TYPE_OFFSET_BASETYPE: Types. (line 6)
+* TYPE_OPERAND_FMT: Label Output. (line 90)
* TYPE_OVERLOADS_ARRAY_REF: Classes. (line 104)
* TYPE_OVERLOADS_ARROW: Classes. (line 107)
* TYPE_OVERLOADS_CALL_EXPR: Classes. (line 100)
* TYPE_POLYMORPHIC_P: Classes. (line 77)
-* TYPE_PRECISION: Types. (line 6)
* TYPE_PRECISION <1>: Types for C++. (line 6)
+* TYPE_PRECISION: Types. (line 6)
+* TYPE_PTR_P: Types for C++. (line 74)
* TYPE_PTRDATAMEM_P: Types for C++. (line 6)
-* TYPE_PTRDATAMEM_P <1>: Types for C++. (line 69)
-* TYPE_PTRFN_P: Types for C++. (line 76)
+* TYPE_PTRFN_P: Types for C++. (line 78)
+* TYPE_PTROB_P: Types for C++. (line 81)
* TYPE_PTROBV_P: Types for C++. (line 6)
-* TYPE_PTROB_P: Types for C++. (line 79)
-* TYPE_PTR_P: Types for C++. (line 72)
-* TYPE_QUAL_CONST: Types. (line 6)
* TYPE_QUAL_CONST <1>: Types for C++. (line 6)
-* TYPE_QUAL_RESTRICT: Types. (line 6)
+* TYPE_QUAL_CONST: Types. (line 6)
* TYPE_QUAL_RESTRICT <1>: Types for C++. (line 6)
-* TYPE_QUAL_VOLATILE: Types. (line 6)
+* TYPE_QUAL_RESTRICT: Types. (line 6)
* TYPE_QUAL_VOLATILE <1>: Types for C++. (line 6)
+* TYPE_QUAL_VOLATILE: Types. (line 6)
* TYPE_RAISES_EXCEPTIONS: Functions for C++. (line 149)
+* TYPE_SIZE <1>: Types for C++. (line 6)
* TYPE_SIZE: Types. (line 6)
-* TYPE_SIZE <1>: Types. (line 25)
-* TYPE_SIZE <2>: Types for C++. (line 6)
-* TYPE_SIZE <3>: Types for C++. (line 39)
* TYPE_STRUCTURAL_EQUALITY_P: Types. (line 6)
-* TYPE_STRUCTURAL_EQUALITY_P <1>: Types. (line 77)
-* TYPE_UNQUALIFIED: Types. (line 6)
* TYPE_UNQUALIFIED <1>: Types for C++. (line 6)
+* TYPE_UNQUALIFIED: Types. (line 6)
* TYPE_VFIELD: Classes. (line 6)
-* UDAmode: Machine Modes. (line 170)
-* udiv: Arithmetic. (line 130)
-* 'udivM3' instruction pattern: Standard Names. (line 276)
-* 'udivmodM4' instruction pattern: Standard Names. (line 536)
-* 'udot_prodM' instruction pattern: Standard Names. (line 356)
-* UDQmode: Machine Modes. (line 138)
-* UHAmode: Machine Modes. (line 162)
-* UHQmode: Machine Modes. (line 130)
-* UINT16_TYPE: Type Layout. (line 220)
-* UINT32_TYPE: Type Layout. (line 221)
-* UINT64_TYPE: Type Layout. (line 222)
-* UINT8_TYPE: Type Layout. (line 219)
-* UINTMAX_TYPE: Type Layout. (line 203)
-* UINTPTR_TYPE: Type Layout. (line 240)
-* UINT_FAST16_TYPE: Type Layout. (line 236)
-* UINT_FAST32_TYPE: Type Layout. (line 237)
-* UINT_FAST64_TYPE: Type Layout. (line 238)
-* UINT_FAST8_TYPE: Type Layout. (line 235)
-* UINT_LEAST16_TYPE: Type Layout. (line 228)
-* UINT_LEAST32_TYPE: Type Layout. (line 229)
-* UINT_LEAST64_TYPE: Type Layout. (line 230)
-* UINT_LEAST8_TYPE: Type Layout. (line 227)
-* 'umaddMN4' instruction pattern: Standard Names. (line 483)
-* umax: Arithmetic. (line 149)
-* 'umaxM3' instruction pattern: Standard Names. (line 276)
-* umin: Arithmetic. (line 149)
-* 'uminM3' instruction pattern: Standard Names. (line 276)
-* umod: Arithmetic. (line 136)
-* 'umodM3' instruction pattern: Standard Names. (line 276)
-* 'umsubMN4' instruction pattern: Standard Names. (line 507)
-* 'umulhisi3' instruction pattern: Standard Names. (line 455)
-* 'umulM3_highpart' instruction pattern: Standard Names. (line 469)
-* 'umulqihi3' instruction pattern: Standard Names. (line 455)
-* 'umulsidi3' instruction pattern: Standard Names. (line 455)
+* TYPENAME_TYPE: Types for C++. (line 6)
+* TYPENAME_TYPE_FULLNAME <1>: Types for C++. (line 6)
+* TYPENAME_TYPE_FULLNAME: Types. (line 6)
+* TYPEOF_TYPE: Types for C++. (line 6)
+* UDAmode: Machine Modes. (line 171)
+* udiv: Arithmetic. (line 129)
+* udivM3 instruction pattern: Standard Names. (line 279)
+* udivmodM4 instruction pattern: Standard Names. (line 541)
+* udot_prodM instruction pattern: Standard Names. (line 359)
+* UDQmode: Machine Modes. (line 139)
+* UHAmode: Machine Modes. (line 163)
+* UHQmode: Machine Modes. (line 131)
+* UINT16_TYPE: Type Layout. (line 221)
+* UINT32_TYPE: Type Layout. (line 222)
+* UINT64_TYPE: Type Layout. (line 223)
+* UINT8_TYPE: Type Layout. (line 220)
+* UINT_FAST16_TYPE: Type Layout. (line 237)
+* UINT_FAST32_TYPE: Type Layout. (line 238)
+* UINT_FAST64_TYPE: Type Layout. (line 239)
+* UINT_FAST8_TYPE: Type Layout. (line 236)
+* UINT_LEAST16_TYPE: Type Layout. (line 229)
+* UINT_LEAST32_TYPE: Type Layout. (line 230)
+* UINT_LEAST64_TYPE: Type Layout. (line 231)
+* UINT_LEAST8_TYPE: Type Layout. (line 228)
+* UINTMAX_TYPE: Type Layout. (line 204)
+* UINTPTR_TYPE: Type Layout. (line 241)
+* umaddMN4 instruction pattern: Standard Names. (line 488)
+* umax: Arithmetic. (line 148)
+* umaxM3 instruction pattern: Standard Names. (line 279)
+* umin: Arithmetic. (line 148)
+* uminM3 instruction pattern: Standard Names. (line 279)
+* umod: Arithmetic. (line 135)
+* umodM3 instruction pattern: Standard Names. (line 279)
+* umsubMN4 instruction pattern: Standard Names. (line 512)
+* umulhisi3 instruction pattern: Standard Names. (line 460)
+* umulM3_highpart instruction pattern: Standard Names. (line 474)
+* umulqihi3 instruction pattern: Standard Names. (line 460)
+* umulsidi3 instruction pattern: Standard Names. (line 460)
* unchanging: Flags. (line 296)
-* 'unchanging', in 'call_insn': Flags. (line 19)
-* 'unchanging', in 'jump_insn', 'call_insn' and 'insn': Flags.
- (line 39)
-* 'unchanging', in 'mem': Flags. (line 134)
-* 'unchanging', in 'subreg': Flags. (line 170)
-* 'unchanging', in 'subreg' <1>: Flags. (line 180)
-* 'unchanging', in 'symbol_ref': Flags. (line 10)
+* unchanging, in call_insn: Flags. (line 19)
+* unchanging, in jump_insn, call_insn and insn: Flags. (line 39)
+* unchanging, in mem: Flags. (line 134)
+* unchanging, in subreg: Flags. (line 170)
+* unchanging, in symbol_ref: Flags. (line 10)
* UNEQ_EXPR: Unary and Binary Expressions.
(line 6)
* UNGE_EXPR: Unary and Binary Expressions.
(line 6)
* UNGT_EXPR: Unary and Binary Expressions.
(line 6)
-* unions, returning: Interface. (line 10)
-* UNION_TYPE: Types. (line 6)
* UNION_TYPE <1>: Classes. (line 6)
-* UNITS_PER_WORD: Storage Layout. (line 60)
-* UNKNOWN_TYPE: Types. (line 6)
+* UNION_TYPE: Types. (line 6)
+* unions, returning: Interface. (line 10)
+* UNITS_PER_WORD: Storage Layout. (line 61)
* UNKNOWN_TYPE <1>: Types for C++. (line 6)
+* UNKNOWN_TYPE: Types. (line 6)
* UNLE_EXPR: Unary and Binary Expressions.
(line 6)
-* UNLIKELY_EXECUTED_TEXT_SECTION_NAME: Sections. (line 48)
+* UNLIKELY_EXECUTED_TEXT_SECTION_NAME: Sections. (line 49)
* UNLT_EXPR: Unary and Binary Expressions.
(line 6)
* UNORDERED_EXPR: Unary and Binary Expressions.
(line 6)
* unshare_all_rtl: Sharing. (line 58)
-* unsigned division: Arithmetic. (line 130)
-* unsigned division with unsigned saturation: Arithmetic. (line 130)
+* unsigned division: Arithmetic. (line 129)
+* unsigned division with unsigned saturation: Arithmetic. (line 129)
* unsigned greater than: Comparisons. (line 64)
-* unsigned greater than <1>: Comparisons. (line 72)
* unsigned less than: Comparisons. (line 68)
-* unsigned less than <1>: Comparisons. (line 76)
-* unsigned minimum and maximum: Arithmetic. (line 149)
+* unsigned minimum and maximum: Arithmetic. (line 148)
* unsigned_fix: Conversions. (line 77)
* unsigned_float: Conversions. (line 62)
* unsigned_fract_convert: Conversions. (line 97)
* unsigned_sat_fract: Conversions. (line 103)
-* unspec: Side Effects. (line 298)
* unspec <1>: Constant Definitions.
(line 111)
-* unspec_volatile: Side Effects. (line 298)
+* unspec: Side Effects. (line 300)
* unspec_volatile <1>: Constant Definitions.
(line 99)
-* 'untyped_call' instruction pattern: Standard Names. (line 1189)
-* 'untyped_return' instruction pattern: Standard Names. (line 1252)
+* unspec_volatile: Side Effects. (line 300)
+* untyped_call instruction pattern: Standard Names. (line 1194)
+* untyped_return instruction pattern: Standard Names. (line 1258)
* UPDATE_PATH_HOST_CANONICALIZE (PATH): Filesystem. (line 59)
* update_ssa: SSA. (line 74)
-* update_stmt: Manipulating GIMPLE statements.
- (line 140)
* update_stmt <1>: SSA Operands. (line 6)
+* update_stmt: Manipulating GIMPLE statements.
+ (line 141)
* update_stmt_if_modified: Manipulating GIMPLE statements.
- (line 143)
+ (line 144)
* UQQmode: Machine Modes. (line 126)
-* 'usaddM3' instruction pattern: Standard Names. (line 276)
-* 'usadM' instruction pattern: Standard Names. (line 365)
-* USAmode: Machine Modes. (line 166)
-* 'usashlM3' instruction pattern: Standard Names. (line 539)
-* 'usdivM3' instruction pattern: Standard Names. (line 276)
+* us_ashift: Arithmetic. (line 172)
+* us_minus: Arithmetic. (line 36)
+* us_mult: Arithmetic. (line 92)
+* us_neg: Arithmetic. (line 81)
+* us_plus: Arithmetic. (line 14)
+* us_truncate: Conversions. (line 48)
+* usaddM3 instruction pattern: Standard Names. (line 279)
+* usadM instruction pattern: Standard Names. (line 368)
+* USAmode: Machine Modes. (line 167)
+* usashlM3 instruction pattern: Standard Names. (line 544)
+* usdivM3 instruction pattern: Standard Names. (line 279)
* use: Side Effects. (line 168)
+* USE_C_ALLOCA: Host Misc. (line 19)
+* USE_LD_AS_NEEDED: Driver. (line 136)
+* USE_LOAD_POST_DECREMENT: Costs. (line 234)
+* USE_LOAD_POST_INCREMENT: Costs. (line 229)
+* USE_LOAD_PRE_DECREMENT: Costs. (line 244)
+* USE_LOAD_PRE_INCREMENT: Costs. (line 239)
+* USE_SELECT_SECTION_FOR_FUNCTIONS: Sections. (line 194)
+* USE_STORE_POST_DECREMENT: Costs. (line 254)
+* USE_STORE_POST_INCREMENT: Costs. (line 249)
+* USE_STORE_PRE_DECREMENT: Costs. (line 264)
+* USE_STORE_PRE_INCREMENT: Costs. (line 259)
* used: Flags. (line 314)
-* 'used', in 'symbol_ref': Flags. (line 197)
-* user: GTY Options. (line 251)
+* used, in symbol_ref: Flags. (line 197)
+* user: GTY Options. (line 243)
* user gc: User GC. (line 6)
-* USER_LABEL_PREFIX: Instruction Output. (line 152)
-* USE_C_ALLOCA: Host Misc. (line 19)
-* USE_LD_AS_NEEDED: Driver. (line 135)
-* USE_LOAD_POST_DECREMENT: Costs. (line 233)
-* USE_LOAD_POST_INCREMENT: Costs. (line 228)
-* USE_LOAD_PRE_DECREMENT: Costs. (line 243)
-* USE_LOAD_PRE_INCREMENT: Costs. (line 238)
-* USE_SELECT_SECTION_FOR_FUNCTIONS: Sections. (line 193)
-* USE_STORE_POST_DECREMENT: Costs. (line 253)
-* USE_STORE_POST_INCREMENT: Costs. (line 248)
-* USE_STORE_PRE_DECREMENT: Costs. (line 263)
-* USE_STORE_PRE_INCREMENT: Costs. (line 258)
+* USER_LABEL_PREFIX: Instruction Output. (line 154)
* USING_STMT: Statements for C++. (line 6)
-* 'usmaddMN4' instruction pattern: Standard Names. (line 491)
-* 'usmsubMN4' instruction pattern: Standard Names. (line 515)
-* 'usmulhisi3' instruction pattern: Standard Names. (line 459)
-* 'usmulM3' instruction pattern: Standard Names. (line 276)
-* 'usmulqihi3' instruction pattern: Standard Names. (line 459)
-* 'usmulsidi3' instruction pattern: Standard Names. (line 459)
-* 'usnegM2' instruction pattern: Standard Names. (line 561)
-* USQmode: Machine Modes. (line 134)
-* 'ussubM3' instruction pattern: Standard Names. (line 276)
-* 'usum_widenM3' instruction pattern: Standard Names. (line 374)
-* us_ashift: Arithmetic. (line 173)
-* us_minus: Arithmetic. (line 38)
-* us_mult: Arithmetic. (line 93)
-* us_neg: Arithmetic. (line 82)
-* us_plus: Arithmetic. (line 14)
-* us_truncate: Conversions. (line 48)
-* UTAmode: Machine Modes. (line 174)
-* UTQmode: Machine Modes. (line 142)
-* 'V' in constraint: Simple Constraints. (line 43)
+* usmaddMN4 instruction pattern: Standard Names. (line 496)
+* usmsubMN4 instruction pattern: Standard Names. (line 520)
+* usmulhisi3 instruction pattern: Standard Names. (line 464)
+* usmulM3 instruction pattern: Standard Names. (line 279)
+* usmulqihi3 instruction pattern: Standard Names. (line 464)
+* usmulsidi3 instruction pattern: Standard Names. (line 464)
+* usnegM2 instruction pattern: Standard Names. (line 566)
+* USQmode: Machine Modes. (line 135)
+* ussubM3 instruction pattern: Standard Names. (line 279)
+* usum_widenM3 instruction pattern: Standard Names. (line 378)
+* UTAmode: Machine Modes. (line 175)
+* UTQmode: Machine Modes. (line 143)
+* V in constraint: Simple Constraints. (line 43)
+* VA_ARG_EXPR: Unary and Binary Expressions.
+ (line 6)
* values, returned by functions: Scalar Return. (line 6)
+* VAR_DECL: Declarations. (line 6)
+* var_location: Debug Information. (line 14)
* varargs implementation: Varargs. (line 6)
* variable: Declarations. (line 6)
* Variable Location Debug Information in RTL: Debug Information.
(line 6)
-* VAR_DECL: Declarations. (line 6)
-* var_location: Debug Information. (line 14)
-* 'vashlM3' instruction pattern: Standard Names. (line 553)
-* 'vashrM3' instruction pattern: Standard Names. (line 553)
-* VA_ARG_EXPR: Unary and Binary Expressions.
- (line 6)
-* 'vcondMN' instruction pattern: Standard Names. (line 213)
-* vector: Containers. (line 6)
-* vector operations: Vector Operations. (line 6)
-* VECTOR_CST: Constant expressions.
- (line 6)
-* VECTOR_STORE_FLAG_VALUE: Misc. (line 293)
+* vashlM3 instruction pattern: Standard Names. (line 558)
+* vashrM3 instruction pattern: Standard Names. (line 558)
+* vcondMN instruction pattern: Standard Names. (line 214)
* vec_concat: Vector Operations. (line 28)
* vec_duplicate: Vector Operations. (line 33)
-* 'vec_extractM' instruction pattern: Standard Names. (line 203)
-* 'vec_initM' instruction pattern: Standard Names. (line 208)
-* 'vec_load_lanesMN' instruction pattern: Standard Names. (line 165)
+* vec_extractM instruction pattern: Standard Names. (line 204)
+* vec_initM instruction pattern: Standard Names. (line 209)
+* vec_load_lanesMN instruction pattern: Standard Names. (line 166)
* VEC_LSHIFT_EXPR: Vectors. (line 6)
* vec_merge: Vector Operations. (line 11)
* VEC_PACK_FIX_TRUNC_EXPR: Vectors. (line 6)
* VEC_PACK_SAT_EXPR: Vectors. (line 6)
-* 'vec_pack_sfix_trunc_M' instruction pattern: Standard Names.
- (line 400)
-* 'vec_pack_ssat_M' instruction pattern: Standard Names. (line 393)
+* vec_pack_sfix_trunc_M instruction pattern: Standard Names. (line 404)
+* vec_pack_ssat_M instruction pattern: Standard Names. (line 397)
* VEC_PACK_TRUNC_EXPR: Vectors. (line 6)
-* 'vec_pack_trunc_M' instruction pattern: Standard Names. (line 386)
-* 'vec_pack_ufix_trunc_M' instruction pattern: Standard Names.
- (line 400)
-* 'vec_pack_usat_M' instruction pattern: Standard Names. (line 393)
-* 'vec_permM' instruction pattern: Standard Names. (line 223)
-* 'vec_perm_constM' instruction pattern: Standard Names. (line 239)
+* vec_pack_trunc_M instruction pattern: Standard Names. (line 390)
+* vec_pack_ufix_trunc_M instruction pattern: Standard Names. (line 404)
+* vec_pack_usat_M instruction pattern: Standard Names. (line 397)
+* vec_perm_constM instruction pattern: Standard Names. (line 242)
+* vec_permM instruction pattern: Standard Names. (line 224)
* VEC_RSHIFT_EXPR: Vectors. (line 6)
* vec_select: Vector Operations. (line 19)
-* 'vec_setM' instruction pattern: Standard Names. (line 198)
-* 'vec_shr_M' instruction pattern: Standard Names. (line 380)
-* 'vec_store_lanesMN' instruction pattern: Standard Names. (line 187)
-* 'vec_unpacks_float_hi_M' instruction pattern: Standard Names.
- (line 421)
-* 'vec_unpacks_float_lo_M' instruction pattern: Standard Names.
- (line 421)
-* 'vec_unpacks_hi_M' instruction pattern: Standard Names. (line 407)
-* 'vec_unpacks_lo_M' instruction pattern: Standard Names. (line 407)
-* 'vec_unpacku_float_hi_M' instruction pattern: Standard Names.
- (line 421)
-* 'vec_unpacku_float_lo_M' instruction pattern: Standard Names.
- (line 421)
-* 'vec_unpacku_hi_M' instruction pattern: Standard Names. (line 414)
-* 'vec_unpacku_lo_M' instruction pattern: Standard Names. (line 414)
+* vec_setM instruction pattern: Standard Names. (line 199)
+* vec_shr_M instruction pattern: Standard Names. (line 384)
+* vec_store_lanesMN instruction pattern: Standard Names. (line 188)
* VEC_UNPACK_FLOAT_HI_EXPR: Vectors. (line 6)
* VEC_UNPACK_FLOAT_LO_EXPR: Vectors. (line 6)
* VEC_UNPACK_HI_EXPR: Vectors. (line 6)
* VEC_UNPACK_LO_EXPR: Vectors. (line 6)
+* vec_unpacks_float_hi_M instruction pattern: Standard Names.
+ (line 426)
+* vec_unpacks_float_lo_M instruction pattern: Standard Names.
+ (line 426)
+* vec_unpacks_hi_M instruction pattern: Standard Names. (line 411)
+* vec_unpacks_lo_M instruction pattern: Standard Names. (line 411)
+* vec_unpacku_float_hi_M instruction pattern: Standard Names.
+ (line 426)
+* vec_unpacku_float_lo_M instruction pattern: Standard Names.
+ (line 426)
+* vec_unpacku_hi_M instruction pattern: Standard Names. (line 419)
+* vec_unpacku_lo_M instruction pattern: Standard Names. (line 419)
* VEC_WIDEN_MULT_HI_EXPR: Vectors. (line 6)
* VEC_WIDEN_MULT_LO_EXPR: Vectors. (line 6)
-* 'vec_widen_smult_even_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_smult_hi_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_smult_lo_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_smult_odd_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_sshiftl_hi_M' instruction pattern: Standard Names.
- (line 441)
-* 'vec_widen_sshiftl_lo_M' instruction pattern: Standard Names.
- (line 441)
-* 'vec_widen_umult_even_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_umult_hi_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_umult_lo_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_umult_odd_M' instruction pattern: Standard Names.
- (line 430)
-* 'vec_widen_ushiftl_hi_M' instruction pattern: Standard Names.
- (line 441)
-* 'vec_widen_ushiftl_lo_M' instruction pattern: Standard Names.
- (line 441)
+* vec_widen_smult_even_M instruction pattern: Standard Names.
+ (line 435)
+* vec_widen_smult_hi_M instruction pattern: Standard Names. (line 435)
+* vec_widen_smult_lo_M instruction pattern: Standard Names. (line 435)
+* vec_widen_smult_odd_M instruction pattern: Standard Names. (line 435)
+* vec_widen_sshiftl_hi_M instruction pattern: Standard Names.
+ (line 446)
+* vec_widen_sshiftl_lo_M instruction pattern: Standard Names.
+ (line 446)
+* vec_widen_umult_even_M instruction pattern: Standard Names.
+ (line 435)
+* vec_widen_umult_hi_M instruction pattern: Standard Names. (line 435)
+* vec_widen_umult_lo_M instruction pattern: Standard Names. (line 435)
+* vec_widen_umult_odd_M instruction pattern: Standard Names. (line 435)
+* vec_widen_ushiftl_hi_M instruction pattern: Standard Names.
+ (line 446)
+* vec_widen_ushiftl_lo_M instruction pattern: Standard Names.
+ (line 446)
+* vector: Containers. (line 6)
+* vector operations: Vector Operations. (line 6)
+* VECTOR_CST: Constant expressions.
+ (line 6)
+* VECTOR_STORE_FLAG_VALUE: Misc. (line 294)
* verify_flow_info: Maintaining the CFG.
- (line 117)
+ (line 119)
* virtual operands: SSA Operands. (line 6)
* VIRTUAL_INCOMING_ARGS_REGNUM: Regs and Memory. (line 59)
* VIRTUAL_OUTGOING_ARGS_REGNUM: Regs and Memory. (line 87)
@@ -50730,463 +51092,458 @@ Concept Index
* VIRTUAL_STACK_VARS_REGNUM: Regs and Memory. (line 69)
* VLIW: Processor pipeline description.
(line 6)
-* VLIW <1>: Processor pipeline description.
- (line 223)
-* 'vlshrM3' instruction pattern: Standard Names. (line 553)
+* vlshrM3 instruction pattern: Standard Names. (line 558)
* VMS: Filesystem. (line 37)
-* VMS_DEBUGGING_INFO: VMS Debug. (line 8)
-* void: Misc. (line 685)
-* void <1>: Misc. (line 690)
-* VOIDmode: Machine Modes. (line 192)
+* VMS_DEBUGGING_INFO: VMS Debug. (line 9)
+* void: Misc. (line 687)
* VOID_TYPE: Types. (line 6)
+* VOIDmode: Machine Modes. (line 193)
* volatil: Flags. (line 328)
-* 'volatil', in 'insn', 'call_insn', 'jump_insn', 'code_label', 'jump_table_data', 'barrier', and 'note': Flags.
+* volatil, in insn, call_insn, jump_insn, code_label, jump_table_data, barrier, and note: Flags.
(line 44)
-* 'volatil', in 'label_ref' and 'reg_label': Flags. (line 65)
-* 'volatil', in 'mem', 'asm_operands', and 'asm_input': Flags.
- (line 76)
-* 'volatil', in 'reg': Flags. (line 98)
-* 'volatil', in 'subreg': Flags. (line 170)
-* 'volatil', in 'subreg' <1>: Flags. (line 180)
-* 'volatil', in 'symbol_ref': Flags. (line 206)
+* volatil, in label_ref and reg_label: Flags. (line 65)
+* volatil, in mem, asm_operands, and asm_input: Flags. (line 76)
+* volatil, in reg: Flags. (line 98)
+* volatil, in subreg: Flags. (line 170)
+* volatil, in symbol_ref: Flags. (line 206)
* volatile memory references: Flags. (line 329)
-* 'volatile', in 'prefetch': Flags. (line 214)
+* volatile, in prefetch: Flags. (line 214)
* voting between constraint alternatives: Class Preferences. (line 6)
-* 'vrotlM3' instruction pattern: Standard Names. (line 553)
-* 'vrotrM3' instruction pattern: Standard Names. (line 553)
-* walk_dominator_tree: SSA. (line 227)
+* vrotlM3 instruction pattern: Standard Names. (line 558)
+* vrotrM3 instruction pattern: Standard Names. (line 558)
+* walk_dominator_tree: SSA. (line 228)
* walk_gimple_op: Statement and operand traversals.
- (line 30)
+ (line 32)
* walk_gimple_seq: Statement and operand traversals.
- (line 47)
+ (line 50)
* walk_gimple_stmt: Statement and operand traversals.
- (line 10)
-* WCHAR_TYPE: Type Layout. (line 171)
-* WCHAR_TYPE_SIZE: Type Layout. (line 179)
-* which_alternative: Output Statement. (line 58)
+ (line 13)
+* WCHAR_TYPE: Type Layout. (line 172)
+* WCHAR_TYPE_SIZE: Type Layout. (line 180)
+* which_alternative: Output Statement. (line 59)
* WHILE_BODY: Statements for C++. (line 6)
* WHILE_COND: Statements for C++. (line 6)
* WHILE_STMT: Statements for C++. (line 6)
* whopr: LTO. (line 6)
-* WIDEST_HARDWARE_FP_SIZE: Type Layout. (line 116)
-* 'window_save' instruction pattern: Standard Names. (line 1544)
-* WINT_TYPE: Type Layout. (line 184)
-* WORDS_BIG_ENDIAN: Storage Layout. (line 28)
-* 'WORDS_BIG_ENDIAN', effect on 'subreg': Regs and Memory. (line 215)
-* word_mode: Machine Modes. (line 367)
-* WORD_REGISTER_OPERATIONS: Misc. (line 53)
+* WIDEST_HARDWARE_FP_SIZE: Type Layout. (line 117)
+* window_save instruction pattern: Standard Names. (line 1554)
+* WINT_TYPE: Type Layout. (line 185)
+* word_mode: Machine Modes. (line 368)
+* WORD_REGISTER_OPERATIONS: Misc. (line 54)
+* WORDS_BIG_ENDIAN: Storage Layout. (line 29)
+* WORDS_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 217)
* wpa: LTO. (line 6)
-* 'X' in constraint: Simple Constraints. (line 122)
-* 'x-HOST': Host Fragment. (line 6)
-* XCmode: Machine Modes. (line 199)
-* XCOFF_DEBUGGING_INFO: DBX Options. (line 12)
+* X in constraint: Simple Constraints. (line 124)
+* x-HOST: Host Fragment. (line 6)
+* XCmode: Machine Modes. (line 200)
+* XCOFF_DEBUGGING_INFO: DBX Options. (line 13)
* XEXP: Accessors. (line 6)
* XFmode: Machine Modes. (line 82)
* XImode: Machine Modes. (line 54)
* XINT: Accessors. (line 6)
-* 'xm-MACHINE.h': Filesystem. (line 6)
-* 'xm-MACHINE.h' <1>: Host Misc. (line 6)
-* xor: Arithmetic. (line 168)
-* 'xor', canonicalization of: Insn Canonicalizations.
- (line 78)
-* 'xorM3' instruction pattern: Standard Names. (line 276)
+* xm-MACHINE.h <1>: Host Misc. (line 6)
+* xm-MACHINE.h: Filesystem. (line 6)
+* xor: Arithmetic. (line 167)
+* xor, canonicalization of: Insn Canonicalizations.
+ (line 79)
+* xorM3 instruction pattern: Standard Names. (line 279)
* XSTR: Accessors. (line 6)
* XVEC: Accessors. (line 41)
* XVECEXP: Accessors. (line 48)
* XVECLEN: Accessors. (line 44)
* XWINT: Accessors. (line 6)
* zero_extend: Conversions. (line 28)
-* 'zero_extendMN2' instruction pattern: Standard Names. (line 957)
+* zero_extendMN2 instruction pattern: Standard Names. (line 962)
* zero_extract: Bit-Fields. (line 30)
-* 'zero_extract', canonicalization of: Insn Canonicalizations.
- (line 87)
+* zero_extract, canonicalization of: Insn Canonicalizations.
+ (line 88)

Tag Table:
-Node: Top1789
-Node: Contributing4971
-Node: Portability5700
-Node: Interface7488
-Node: Libgcc10529
-Node: Integer library routines12356
-Node: Soft float library routines19324
-Node: Decimal float library routines31262
-Node: Fixed-point fractional library routines47020
-Node: Exception handling routines147416
-Node: Miscellaneous routines148523
-Node: Languages150643
-Node: Source Tree152190
-Node: Configure Terms152772
-Node: Top Level155728
-Node: gcc Directory159215
-Node: Subdirectories160167
-Node: Configuration162335
-Node: Config Fragments163055
-Node: System Config164280
-Node: Configuration Files165216
-Node: Build168033
-Node: Makefile168445
-Ref: Makefile-Footnote-1175249
-Ref: Makefile-Footnote-2175396
-Node: Library Files175470
-Node: Headers176032
-Node: Documentation178115
-Node: Texinfo Manuals178974
-Node: Man Page Generation181303
-Node: Miscellaneous Docs183216
-Node: Front End184603
-Node: Front End Directory188277
-Node: Front End Config189593
-Node: Front End Makefile192409
-Node: Back End196177
-Node: Testsuites199958
-Node: Test Idioms200889
-Node: Test Directives204287
-Node: Directives204814
-Node: Selectors215111
-Node: Effective-Target Keywords216467
-Ref: arm_neon_ok224330
-Ref: arm_neonv2_ok224488
-Ref: arm_neon_fp16_ok224660
-Ref: arm_vfp3_ok225100
-Node: Add Options235574
-Node: Require Support236891
-Node: Final Actions239398
-Node: Ada Tests244563
-Node: C Tests245894
-Node: libgcj Tests250289
-Node: LTO Testing251416
-Node: gcov Testing253064
-Node: profopt Testing256054
-Node: compat Testing257769
-Node: Torture Tests262009
-Node: Options263624
-Node: Option file format264065
-Node: Option properties271054
-Node: Passes284604
-Node: Parsing pass285494
-Node: Cilk Plus Transformation289027
-Node: Gimplification pass292409
-Node: Pass manager294254
-Node: Tree SSA passes296100
-Node: RTL passes317285
-Node: Optimization info329589
-Node: Dump setup330408
-Node: Optimization groups331537
-Node: Dump files and streams332426
-Node: Dump output verbosity333624
-Node: Dump types334680
-Node: Dump examples336170
-Node: GENERIC337516
-Node: Deficiencies339392
-Node: Tree overview339633
-Node: Macros and Functions343757
-Node: Identifiers344582
-Node: Containers346191
-Node: Types347348
-Node: Declarations359422
-Node: Working with declarations359917
-Node: Internal structure365521
-Node: Current structure hierarchy365905
-Node: Adding new DECL node types367998
-Node: Attributes372282
-Node: Expression trees373526
-Node: Constant expressions375280
-Node: Storage References378576
-Node: Unary and Binary Expressions382095
-Node: Vectors402243
-Node: Statements407438
-Node: Basic Statements407970
-Node: Blocks412477
-Node: Statement Sequences413881
-Node: Empty Statements414214
-Node: Jumps414788
-Node: Cleanups415441
-Node: OpenMP417208
-Node: OpenACC423053
-Node: Functions424094
-Node: Function Basics424565
-Node: Function Properties428249
-Node: Language-dependent trees431030
-Node: C and C++ Trees431917
-Node: Types for C++434821
-Node: Namespaces439791
-Node: Classes442897
-Node: Functions for C++447974
-Node: Statements for C++454225
-Node: C++ Expressions462998
-Node: Java Trees464503
-Node: GIMPLE464616
-Node: Tuple representation468281
-Node: Class hierarchy of GIMPLE statements475286
-Node: GIMPLE instruction set480289
-Node: GIMPLE Exception Handling481921
-Node: Temporaries483833
-Ref: Temporaries-Footnote-1485151
-Node: Operands485216
-Node: Compound Expressions485977
-Node: Compound Lvalues486211
-Node: Conditional Expressions486973
-Node: Logical Operators487632
-Node: Manipulating GIMPLE statements494496
-Node: Tuple specific accessors500432
-Node: 'GIMPLE_ASM'501269
-Node: 'GIMPLE_ASSIGN'503656
-Node: 'GIMPLE_BIND'508366
-Node: 'GIMPLE_CALL'510186
-Node: 'GIMPLE_CATCH'514220
-Node: 'GIMPLE_COND'515376
-Node: 'GIMPLE_DEBUG'518177
-Node: 'GIMPLE_EH_FILTER'521556
-Node: 'GIMPLE_LABEL'523125
-Node: 'GIMPLE_GOTO'523744
-Node: 'GIMPLE_NOP'524273
-Node: 'GIMPLE_OMP_ATOMIC_LOAD'524641
-Node: 'GIMPLE_OMP_ATOMIC_STORE'525643
-Node: 'GIMPLE_OMP_CONTINUE'526348
-Node: 'GIMPLE_OMP_CRITICAL'527833
-Node: 'GIMPLE_OMP_FOR'528833
-Node: 'GIMPLE_OMP_MASTER'532255
-Node: 'GIMPLE_OMP_ORDERED'532639
-Node: 'GIMPLE_OMP_PARALLEL'533039
-Node: 'GIMPLE_OMP_RETURN'535814
-Node: 'GIMPLE_OMP_SECTION'536465
-Node: 'GIMPLE_OMP_SECTIONS'537131
-Node: 'GIMPLE_OMP_SINGLE'538747
-Node: 'GIMPLE_PHI'539699
-Node: 'GIMPLE_RESX'540984
-Node: 'GIMPLE_RETURN'541709
-Node: 'GIMPLE_SWITCH'542289
-Node: 'GIMPLE_TRY'544170
-Node: 'GIMPLE_WITH_CLEANUP_EXPR'545948
-Node: GIMPLE sequences546831
-Node: Sequence iterators550037
-Node: Adding a new GIMPLE statement code558494
-Node: Statement and operand traversals559869
-Node: Tree SSA562461
-Node: Annotations564249
-Node: SSA Operands564654
-Node: SSA578728
-Node: Alias analysis589760
-Node: Memory model593534
-Node: RTL594893
-Node: RTL Objects597081
-Node: RTL Classes600955
-Node: Accessors606001
-Node: Special Accessors608395
-Node: Flags614182
-Node: Machine Modes628946
-Node: Constants642594
-Node: Regs and Memory650681
-Node: Arithmetic668569
-Node: Comparisons678614
-Node: Bit-Fields682906
-Node: Vector Operations684458
-Node: Conversions686339
-Node: RTL Declarations690837
-Node: Side Effects691658
-Node: Incdec708668
-Node: Assembler712004
-Node: Debug Information713549
-Node: Insns714746
-Node: Calls741167
-Node: Sharing743760
-Node: Reading RTL746871
-Node: Control Flow747862
-Node: Basic Blocks749631
-Node: Edges755085
-Node: Profile information763714
-Node: Maintaining the CFG768398
-Node: Liveness information774260
-Node: Loop Analysis and Representation776386
-Node: Loop representation777496
-Node: Loop querying785059
-Node: Loop manipulation787875
-Node: LCSSA790236
-Node: Scalar evolutions792305
-Node: loop-iv795549
-Node: Number of iterations797471
-Node: Dependency analysis800277
-Node: Omega806641
-Node: Machine Desc808217
-Node: Overview810780
-Node: Patterns812820
-Node: Example816328
-Node: RTL Template817789
-Node: Output Template828445
-Node: Output Statement832408
-Node: Predicates836747
-Node: Machine-Independent Predicates839665
-Node: Defining Predicates844609
-Node: Constraints850572
-Node: Simple Constraints852041
-Node: Multi-Alternative864881
-Node: Class Preferences868008
-Node: Modifiers868900
-Node: Machine Constraints873633
-Node: Disable Insn Alternatives931235
-Node: Define Constraints934727
-Node: C Constraint Interface941512
-Node: Standard Names944662
-Ref: shift patterns969007
-Ref: prologue instruction pattern1014154
-Ref: window_save instruction pattern1014647
-Ref: epilogue instruction pattern1014924
-Node: Pattern Ordering1032494
-Node: Dependent Patterns1033730
-Node: Jump Patterns1035350
-Ref: Jump Patterns-Footnote-11037497
-Node: Looping Patterns1037545
-Node: Insn Canonicalizations1042274
-Node: Expander Definitions1046859
-Node: Insn Splitting1055073
-Node: Including Patterns1064676
-Node: Peephole Definitions1066460
-Node: define_peephole1067713
-Node: define_peephole21074043
-Node: Insn Attributes1077109
-Node: Defining Attributes1078291
-Ref: define_enum_attr1081784
-Node: Expressions1082820
-Node: Tagging Insns1089570
-Node: Attr Example1093923
-Node: Insn Lengths1096296
-Node: Constant Attributes1099704
-Node: Mnemonic Attribute1100880
-Node: Delay Slots1102399
-Node: Processor pipeline description1105622
-Ref: Processor pipeline description-Footnote-11124440
-Node: Conditional Execution1124764
-Node: Define Subst1128247
-Node: Define Subst Example1130283
-Node: Define Subst Pattern Matching1133277
-Node: Define Subst Output Template1134503
-Node: Constant Definitions1136573
-Ref: define_enum1140355
-Node: Iterators1140843
-Node: Mode Iterators1141421
-Node: Defining Mode Iterators1142399
-Node: Substitutions1143893
-Node: Examples1146135
-Node: Code Iterators1147583
-Node: Int Iterators1149862
-Node: Subst Iterators1152308
-Node: Target Macros1154000
-Node: Target Structure1157012
-Node: Driver1159128
-Node: Run-time Target1177940
-Node: Per-Function Data1187651
-Node: Storage Layout1190415
-Node: Type Layout1216172
-Node: Registers1229798
-Node: Register Basics1230772
-Node: Allocation Order1236210
-Node: Values in Registers1238694
-Node: Leaf Functions1246172
-Node: Stack Registers1249031
-Node: Register Classes1250303
-Node: Stack and Calling1282112
-Node: Frame Layout1282678
-Node: Exception Handling1293646
-Node: Stack Checking1299856
-Node: Frame Registers1304668
-Node: Elimination1312933
-Node: Stack Arguments1317161
-Node: Register Arguments1324343
-Node: Scalar Return1345388
-Node: Aggregate Return1351845
-Node: Caller Saves1356034
-Node: Function Entry1356776
-Node: Profiling1367868
-Node: Tail Calls1369978
-Node: Stack Smashing Protection1371879
-Node: Miscellaneous Register Hooks1373542
-Node: Varargs1374408
-Node: Trampolines1384517
-Node: Library Calls1390560
-Node: Addressing Modes1395244
-Node: Anchored Addresses1416167
-Node: Condition Code1418810
-Node: CC0 Condition Codes1421137
-Node: MODE_CC Condition Codes1424383
-Node: Costs1431191
-Node: Scheduling1448053
-Node: Sections1471231
-Node: PIC1486924
-Node: Assembler Format1488983
-Node: File Framework1490121
-Ref: TARGET_HAVE_SWITCHABLE_BSS_SECTIONS1497053
-Node: Data Output1500323
-Node: Uninitialized Data1508269
-Node: Label Output1513280
-Node: Initialization1536626
-Node: Macros for Initialization1542587
-Node: Instruction Output1549306
-Node: Dispatch Tables1559935
-Node: Exception Region Output1564335
-Node: Alignment Output1571358
-Node: Debugging Info1575961
-Node: All Debuggers1576631
-Node: DBX Options1579486
-Node: DBX Hooks1584924
-Node: File Names and DBX1586233
-Node: SDB and DWARF1588345
-Node: VMS Debug1594605
-Node: Floating Point1595192
-Node: Mode Switching1599084
-Node: Target Attributes1603520
-Node: Emulated TLS1612230
-Node: MIPS Coprocessors1615620
-Node: PCH Target1616779
-Node: C++ ABI1618621
-Node: Named Address Spaces1623415
-Node: Misc1628324
-Ref: TARGET_SHIFT_TRUNCATION_MASK1635061
-Node: Host Config1691718
-Node: Host Common1692786
-Node: Filesystem1695160
-Node: Host Misc1699275
-Node: Fragments1701724
-Node: Target Fragment1702919
-Node: Host Fragment1713547
-Node: Collect21713787
-Node: Header Dirs1716423
-Node: Type Information1717846
-Node: GTY Options1721122
-Node: Inheritance and GTY1732774
-Ref: Inheritance and GTY-Footnote-11734337
-Node: User GC1734607
-Node: GGC Roots1738346
-Node: Files1739059
-Node: Invoking the garbage collector1741766
-Node: Troubleshooting1743271
-Node: Plugins1744346
-Node: Plugins loading1745475
-Node: Plugin API1746345
-Node: Plugins pass1753903
-Node: Plugins GC1755874
-Node: Plugins description1757592
-Node: Plugins attr1758128
-Node: Plugins recording1760402
-Node: Plugins gate1761252
-Node: Plugins tracking1761843
-Node: Plugins building1762431
-Node: LTO1764221
-Node: LTO Overview1765093
-Node: LTO object file layout1770925
-Node: IPA1775555
-Node: WHOPR1784520
-Node: Internal flags1789209
-Node: Match and Simplify1790620
-Node: GIMPLE API1791574
-Node: The Language1794196
-Node: Funding1803039
-Node: GNU Project1805538
-Node: Copying1806187
-Node: GNU Free Documentation License1843699
-Node: Contributors1868820
-Node: Option Index1907588
-Node: Concept Index1908465
+Node: Top1842
+Node: Contributing5024
+Node: Portability5765
+Node: Interface7553
+Node: Libgcc10593
+Node: Integer library routines12434
+Node: Soft float library routines19402
+Node: Decimal float library routines31339
+Node: Fixed-point fractional library routines47096
+Node: Exception handling routines147494
+Node: Miscellaneous routines148601
+Node: Languages150721
+Node: Source Tree152270
+Node: Configure Terms152852
+Node: Top Level155810
+Node: gcc Directory159296
+Node: Subdirectories160246
+Node: Configuration162413
+Node: Config Fragments163133
+Node: System Config164362
+Node: Configuration Files165298
+Node: Build168123
+Node: Makefile168535
+Ref: Makefile-Footnote-1175338
+Ref: Makefile-Footnote-2175483
+Node: Library Files175555
+Node: Headers176117
+Node: Documentation178200
+Node: Texinfo Manuals179059
+Node: Man Page Generation181392
+Node: Miscellaneous Docs183307
+Node: Front End184701
+Node: Front End Directory188394
+Node: Front End Config189714
+Node: Front End Makefile192540
+Node: Back End196322
+Node: Testsuites200119
+Node: Test Idioms201050
+Node: Test Directives204447
+Node: Directives204974
+Node: Selectors215284
+Node: Effective-Target Keywords216642
+Ref: arm_neon_ok224510
+Ref: arm_neonv2_ok224668
+Ref: arm_neon_fp16_ok224840
+Ref: arm_vfp3_ok225280
+Node: Add Options235750
+Node: Require Support237067
+Node: Final Actions239574
+Node: Ada Tests244741
+Node: C Tests246073
+Node: libgcj Tests250496
+Node: LTO Testing251623
+Node: gcov Testing253270
+Node: profopt Testing256257
+Node: compat Testing257972
+Node: Torture Tests262212
+Node: Options263829
+Node: Option file format264269
+Node: Option properties271259
+Node: Passes284817
+Node: Parsing pass285707
+Node: Cilk Plus Transformation289242
+Node: Gimplification pass292629
+Node: Pass manager294474
+Node: Tree SSA passes296319
+Node: RTL passes317518
+Node: Optimization info329839
+Node: Dump setup330657
+Node: Optimization groups331779
+Node: Dump files and streams332662
+Node: Dump output verbosity333853
+Node: Dump types334904
+Node: Dump examples336394
+Node: GENERIC337736
+Node: Deficiencies339611
+Node: Tree overview339852
+Node: Macros and Functions343979
+Node: Identifiers344804
+Node: Containers346415
+Node: Types347572
+Node: Declarations359668
+Node: Working with declarations360163
+Node: Internal structure365769
+Node: Current structure hierarchy366153
+Node: Adding new DECL node types368247
+Node: Attributes372532
+Node: Expression trees373777
+Node: Constant expressions375530
+Node: Storage References378836
+Node: Unary and Binary Expressions382355
+Node: Vectors402506
+Node: Statements407697
+Node: Basic Statements408229
+Node: Blocks412736
+Node: Statement Sequences414140
+Node: Empty Statements414473
+Node: Jumps415047
+Node: Cleanups415700
+Node: OpenMP417468
+Node: OpenACC423303
+Node: Functions424335
+Node: Function Basics424806
+Node: Function Properties428491
+Node: Language-dependent trees431273
+Node: C and C++ Trees432159
+Node: Types for C++435063
+Node: Namespaces440041
+Node: Classes443148
+Node: Functions for C++448226
+Node: Statements for C++454479
+Node: C++ Expressions463249
+Node: Java Trees464750
+Node: GIMPLE464863
+Node: Tuple representation468525
+Node: Class hierarchy of GIMPLE statements475503
+Node: GIMPLE instruction set480506
+Node: GIMPLE Exception Handling482190
+Node: Temporaries484104
+Ref: Temporaries-Footnote-1485419
+Node: Operands485482
+Node: Compound Expressions486244
+Node: Compound Lvalues486478
+Node: Conditional Expressions487240
+Node: Logical Operators487898
+Node: Manipulating GIMPLE statements494763
+Node: Tuple specific accessors500697
+Node: `GIMPLE_ASM'501534
+Node: `GIMPLE_ASSIGN'503922
+Node: `GIMPLE_BIND'508632
+Node: `GIMPLE_CALL'510451
+Node: `GIMPLE_CATCH'514484
+Node: `GIMPLE_COND'515640
+Node: `GIMPLE_DEBUG'518441
+Node: `GIMPLE_EH_FILTER'521825
+Node: `GIMPLE_LABEL'523394
+Node: `GIMPLE_GOTO'524013
+Node: `GIMPLE_NOP'524542
+Node: `GIMPLE_OMP_ATOMIC_LOAD'524910
+Node: `GIMPLE_OMP_ATOMIC_STORE'525912
+Node: `GIMPLE_OMP_CONTINUE'526616
+Node: `GIMPLE_OMP_CRITICAL'528101
+Node: `GIMPLE_OMP_FOR'529100
+Node: `GIMPLE_OMP_MASTER'532522
+Node: `GIMPLE_OMP_ORDERED'532905
+Node: `GIMPLE_OMP_PARALLEL'533305
+Node: `GIMPLE_OMP_RETURN'536081
+Node: `GIMPLE_OMP_SECTION'536731
+Node: `GIMPLE_OMP_SECTIONS'537397
+Node: `GIMPLE_OMP_SINGLE'539012
+Node: `GIMPLE_PHI'539963
+Node: `GIMPLE_RESX'541247
+Node: `GIMPLE_RETURN'541972
+Node: `GIMPLE_SWITCH'542552
+Node: `GIMPLE_TRY'544431
+Node: `GIMPLE_WITH_CLEANUP_EXPR'546208
+Node: GIMPLE sequences547091
+Node: Sequence iterators550297
+Node: Adding a new GIMPLE statement code558755
+Node: Statement and operand traversals560130
+Node: Tree SSA562730
+Node: Annotations564516
+Node: SSA Operands564921
+Node: SSA579001
+Node: Alias analysis590033
+Node: Memory model593813
+Node: RTL595176
+Node: RTL Objects597364
+Node: RTL Classes601238
+Node: Accessors606285
+Node: Special Accessors608679
+Node: Flags614449
+Node: Machine Modes629211
+Node: Constants642863
+Node: Regs and Memory650949
+Node: Arithmetic668850
+Node: Comparisons678903
+Node: Bit-Fields683195
+Node: Vector Operations684747
+Node: Conversions686629
+Node: RTL Declarations691127
+Node: Side Effects691948
+Node: Incdec708963
+Node: Assembler712298
+Node: Debug Information713843
+Node: Insns715041
+Node: Calls741475
+Node: Sharing744068
+Node: Reading RTL747178
+Node: Control Flow748170
+Node: Basic Blocks749938
+Node: Edges755394
+Node: Profile information764026
+Node: Maintaining the CFG768710
+Node: Liveness information774573
+Node: Loop Analysis and Representation776699
+Node: Loop representation777809
+Node: Loop querying785374
+Node: Loop manipulation788207
+Node: LCSSA790575
+Node: Scalar evolutions792647
+Node: loop-iv795891
+Node: Number of iterations797817
+Node: Dependency analysis800626
+Node: Omega806993
+Node: Machine Desc808569
+Node: Overview811132
+Node: Patterns813173
+Node: Example816681
+Node: RTL Template818142
+Node: Output Template828798
+Node: Output Statement832763
+Node: Predicates837102
+Node: Machine-Independent Predicates840020
+Node: Defining Predicates844965
+Node: Constraints850930
+Node: Simple Constraints852399
+Node: Multi-Alternative865255
+Node: Class Preferences868382
+Node: Modifiers869274
+Node: Machine Constraints874006
+Node: Disable Insn Alternatives931720
+Node: Define Constraints935209
+Node: C Constraint Interface941996
+Node: Standard Names945136
+Ref: shift patterns969480
+Ref: prologue instruction pattern1014654
+Ref: window_save instruction pattern1015147
+Ref: epilogue instruction pattern1015422
+Node: Pattern Ordering1032993
+Node: Dependent Patterns1034229
+Node: Jump Patterns1035849
+Ref: Jump Patterns-Footnote-11037993
+Node: Looping Patterns1038039
+Node: Insn Canonicalizations1042767
+Node: Expander Definitions1047358
+Node: Insn Splitting1055570
+Node: Including Patterns1065172
+Node: Peephole Definitions1066952
+Node: define_peephole1068205
+Node: define_peephole21074536
+Node: Insn Attributes1077602
+Node: Defining Attributes1078784
+Ref: define_enum_attr1082272
+Node: Expressions1083307
+Node: Tagging Insns1090056
+Node: Attr Example1094409
+Node: Insn Lengths1096783
+Node: Constant Attributes1100191
+Node: Mnemonic Attribute1101367
+Node: Delay Slots1102886
+Node: Processor pipeline description1106109
+Ref: Processor pipeline description-Footnote-11124922
+Node: Conditional Execution1125244
+Node: Define Subst1128724
+Node: Define Subst Example1130758
+Node: Define Subst Pattern Matching1133752
+Node: Define Subst Output Template1134977
+Node: Constant Definitions1137047
+Ref: define_enum1140829
+Node: Iterators1141317
+Node: Mode Iterators1141895
+Node: Defining Mode Iterators1142873
+Node: Substitutions1144367
+Node: Examples1146608
+Node: Code Iterators1148056
+Node: Int Iterators1150335
+Node: Subst Iterators1152778
+Node: Target Macros1154470
+Node: Target Structure1157482
+Node: Driver1159597
+Node: Run-time Target1178407
+Node: Per-Function Data1188105
+Node: Storage Layout1190870
+Node: Type Layout1216643
+Node: Registers1230273
+Node: Register Basics1231247
+Node: Allocation Order1236682
+Node: Values in Registers1239170
+Node: Leaf Functions1246659
+Node: Stack Registers1249517
+Node: Register Classes1250789
+Node: Stack and Calling1282652
+Node: Frame Layout1283218
+Node: Exception Handling1294190
+Node: Stack Checking1300410
+Node: Frame Registers1305221
+Node: Elimination1313486
+Node: Stack Arguments1317713
+Node: Register Arguments1324894
+Node: Scalar Return1345952
+Node: Aggregate Return1352408
+Node: Caller Saves1356596
+Node: Function Entry1357339
+Node: Profiling1368441
+Node: Tail Calls1370555
+Node: Stack Smashing Protection1372456
+Node: Miscellaneous Register Hooks1374119
+Node: Varargs1374985
+Node: Trampolines1385107
+Node: Library Calls1391150
+Node: Addressing Modes1395834
+Node: Anchored Addresses1416776
+Node: Condition Code1419425
+Node: CC0 Condition Codes1421752
+Node: MODE_CC Condition Codes1424998
+Node: Costs1431803
+Node: Scheduling1448670
+Node: Sections1471854
+Node: PIC1487547
+Node: Assembler Format1489607
+Node: File Framework1490745
+Ref: TARGET_HAVE_SWITCHABLE_BSS_SECTIONS1497686
+Node: Data Output1500951
+Node: Uninitialized Data1508904
+Node: Label Output1513915
+Node: Initialization1537273
+Node: Macros for Initialization1543235
+Node: Instruction Output1549958
+Node: Dispatch Tables1560593
+Node: Exception Region Output1564993
+Node: Alignment Output1572021
+Node: Debugging Info1576623
+Node: All Debuggers1577293
+Node: DBX Options1580148
+Node: DBX Hooks1585597
+Node: File Names and DBX1586906
+Node: SDB and DWARF1589018
+Node: VMS Debug1595278
+Node: Floating Point1595865
+Node: Mode Switching1599757
+Node: Target Attributes1604190
+Node: Emulated TLS1612900
+Node: MIPS Coprocessors1616290
+Node: PCH Target1617449
+Node: C++ ABI1619291
+Node: Named Address Spaces1624083
+Node: Misc1628997
+Ref: TARGET_SHIFT_TRUNCATION_MASK1635734
+Node: Host Config1692436
+Node: Host Common1693504
+Node: Filesystem1695883
+Node: Host Misc1699998
+Node: Fragments1702447
+Node: Target Fragment1703642
+Node: Host Fragment1714275
+Node: Collect21714515
+Node: Header Dirs1717151
+Node: Type Information1718574
+Node: GTY Options1721854
+Node: Inheritance and GTY1733502
+Ref: Inheritance and GTY-Footnote-11735065
+Node: User GC1735333
+Node: GGC Roots1739068
+Node: Files1739784
+Node: Invoking the garbage collector1742491
+Node: Troubleshooting1743994
+Node: Plugins1745070
+Node: Plugins loading1746199
+Node: Plugin API1747068
+Node: Plugins pass1754627
+Node: Plugins GC1756596
+Node: Plugins description1758311
+Node: Plugins attr1758846
+Node: Plugins recording1761117
+Node: Plugins gate1761967
+Node: Plugins tracking1762558
+Node: Plugins building1763146
+Node: LTO1764935
+Node: LTO Overview1765807
+Node: LTO object file layout1771639
+Node: IPA1776271
+Node: WHOPR1785236
+Node: Internal flags1789927
+Node: Match and Simplify1791339
+Node: GIMPLE API1792300
+Node: The Language1794922
+Node: Funding1803771
+Node: GNU Project1806269
+Node: Copying1806918
+Node: GNU Free Documentation License1844449
+Node: Contributors1869589
+Node: Option Index1908360
+Node: Concept Index1909237

End Tag Table
diff --git a/gcc/doc/gcj-dbtool.1 b/gcc/doc/gcj-dbtool.1
index 0a14e324e0..d079e14656 100644
--- a/gcc/doc/gcj-dbtool.1
+++ b/gcc/doc/gcj-dbtool.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCJ-DBTOOL 1"
-.TH GCJ-DBTOOL 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCJ-DBTOOL 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/gcj.1 b/gcc/doc/gcj.1
index 57a808e4bc..bf19943ea6 100644
--- a/gcc/doc/gcj.1
+++ b/gcc/doc/gcj.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCJ 1"
-.TH GCJ 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCJ 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -156,7 +155,7 @@ of the same options as gcc. This manual only documents the
options specific to \fBgcj\fR.
.SH "OPTIONS"
.IX Header "OPTIONS"
-.SS "Input and output files"
+.Sh "Input and output files"
.IX Subsection "Input and output files"
A \fBgcj\fR command is like a \fBgcc\fR command, in that it
consists of a number of options and file names. The following kinds
@@ -204,7 +203,7 @@ but not when using \f(CW\*(C`\-C\*(C'\fR or \f(CW\*(C`\-\-resource\*(C'\fR.
(This is an extension beyond the what plain \fBgcc\fR allows.)
(If more than one input file is specified, all must currently
be \f(CW\*(C`.java\*(C'\fR files, though we hope to fix this.)
-.SS "Input Options"
+.Sh "Input Options"
.IX Subsection "Input Options"
\&\fBgcj\fR has options to control where it looks to find files it needs.
For instance, \fBgcj\fR might need to load a class that is referenced
@@ -278,7 +277,7 @@ issue an error if it isn't found.
.IX Item "-fsource=VERSION"
This option is used to choose the source version accepted by
\&\fBgcj\fR. The default is \fB1.5\fR.
-.SS "Encodings"
+.Sh "Encodings"
.IX Subsection "Encodings"
The Java programming language uses Unicode throughout. In an effort to
integrate well with other locales, \fBgcj\fR allows \fI.java\fR files
@@ -301,7 +300,7 @@ to platform (since they are not standardized anywhere). However,
\&\fBgcj\fR implements the encoding named \fB\s-1UTF\-8\s0\fR internally, so if
you choose to use this for your source files you can be assured that it
will work on every host.
-.SS "Warnings"
+.Sh "Warnings"
.IX Subsection "Warnings"
\&\fBgcj\fR implements several warnings. As with other generic
\&\fBgcc\fR warnings, if an option of the form \f(CW\*(C`\-Wfoo\*(C'\fR enables a
@@ -331,7 +330,7 @@ This is the same as \fBgcc\fR's \f(CW\*(C`\-Wunused\*(C'\fR.
.IX Item "-Wall"
This is the same as \f(CW\*(C`\-Wredundant\-modifiers \-Wextraneous\-semicolon
\&\-Wunused\*(C'\fR.
-.SS "Linking"
+.Sh "Linking"
.IX Subsection "Linking"
To turn a Java application into an executable program,
you need to link it with the needed libraries, just as for C or \*(C+.
@@ -392,7 +391,7 @@ link time, it can omit the referred to classes. The result is usually
runtime. Caution must be used when using this option. For more
details see:
<\fBhttp://gcc.gnu.org/wiki/Statically%20linking%20libgcj\fR>
-.SS "Code Generation"
+.Sh "Code Generation"
.IX Subsection "Code Generation"
In addition to the many \fBgcc\fR options controlling code generation,
\&\fBgcj\fR has several options specific to itself.
@@ -440,9 +439,9 @@ It is safe to use this option if you are sure your code will never throw an
.IP "\fB\-fjni\fR" 4
.IX Item "-fjni"
With \fBgcj\fR there are two options for writing native methods: \s-1CNI\s0
-and \s-1JNI. \s0 By default \fBgcj\fR assumes you are using \s-1CNI. \s0 If you are
+and \s-1JNI\s0. By default \fBgcj\fR assumes you are using \s-1CNI\s0. If you are
compiling a class with native methods, and these methods are implemented
-using \s-1JNI,\s0 then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes
+using \s-1JNI\s0, then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes
\&\fBgcj\fR to generate stubs which will invoke the underlying \s-1JNI\s0
methods.
.IP "\fB\-fno\-assert\fR" 4
@@ -479,7 +478,7 @@ So this flag isn't very useful yet, except to partially override
\&\f(CW\*(C`\-\-disable\-assertions\*(C'\fR.
.IP "\fB\-findirect\-dispatch\fR" 4
.IX Item "-findirect-dispatch"
-\&\fBgcj\fR has a special binary compatibility \s-1ABI,\s0 which is enabled
+\&\fBgcj\fR has a special binary compatibility \s-1ABI\s0, which is enabled
by the \f(CW\*(C`\-findirect\-dispatch\*(C'\fR option. In this mode, the code
generated by \fBgcj\fR honors the binary compatibility guarantees
in the Java Language Specification, and the resulting object files do
@@ -490,10 +489,10 @@ interpreted and compiled code.
Note that, at present, \f(CW\*(C`\-findirect\-dispatch\*(C'\fR can only be used
when compiling \fI.class\fR files. It will not work when compiling
from source. \s-1CNI\s0 also does not yet work with the binary compatibility
-\&\s-1ABI. \s0 These restrictions will be lifted in some future release.
+\&\s-1ABI\s0. These restrictions will be lifted in some future release.
.Sp
-However, if you compile \s-1CNI\s0 code with the standard \s-1ABI,\s0 you can call
-it from code built with the binary compatibility \s-1ABI.\s0
+However, if you compile \s-1CNI\s0 code with the standard \s-1ABI\s0, you can call
+it from code built with the binary compatibility \s-1ABI\s0.
.IP "\fB\-fbootstrap\-classes\fR" 4
.IX Item "-fbootstrap-classes"
This option can be use to tell \f(CW\*(C`libgcj\*(C'\fR that the compiled classes
@@ -512,13 +511,13 @@ the ability to use certain reflection capabilities of the standard
Java runtime environment. When set all meta-data except for that
which is needed to obtain correct runtime semantics is eliminated.
.Sp
-For code that does not use reflection (i.e. serialization, \s-1RMI, CORBA\s0
+For code that does not use reflection (i.e. serialization, \s-1RMI\s0, \s-1CORBA\s0
or call methods in the \f(CW\*(C`java.lang.reflect\*(C'\fR package),
\&\f(CW\*(C`\-freduced\-reflection\*(C'\fR will result in proper operation with a
savings in executable code size.
.Sp
-\&\s-1JNI \s0(\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI
-\&\s0(\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full
+\&\s-1JNI\s0 (\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI\s0
+(\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full
reflection meta-data. Because of this, it is an error to use these options
with \f(CW\*(C`\-freduced\-reflection\*(C'\fR.
.Sp
@@ -526,9 +525,9 @@ with \f(CW\*(C`\-freduced\-reflection\*(C'\fR.
a \f(CW\*(C`SecurityManager\*(C'\fR may not work properly. Also calling
\&\f(CW\*(C`Class.forName()\*(C'\fR may fail if the calling method has no
reflection meta-data.
-.SS "Configure-time Options"
+.Sh "Configure-time Options"
.IX Subsection "Configure-time Options"
-Some \fBgcj\fR code generations options affect the resulting \s-1ABI,\s0 and
+Some \fBgcj\fR code generations options affect the resulting \s-1ABI\s0, and
so can only be meaningfully given when \f(CW\*(C`libgcj\*(C'\fR, the runtime
package, is configured. \f(CW\*(C`libgcj\*(C'\fR puts the appropriate options from
this group into a \fBspec\fR file which is read by \fBgcj\fR. These
diff --git a/gcc/doc/gcj.info b/gcc/doc/gcj.info
index 32b828ad1d..71378d548d 100644
--- a/gcc/doc/gcj.info
+++ b/gcc/doc/gcj.info
@@ -1,4 +1,5 @@
-This is gcj.info, produced by makeinfo version 5.2 from gcj.texi.
+This is doc/gcj.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-5.2.0/gcc-5.2.0/gcc/java/gcj.texi.
Copyright (C) 2001-2015 Free Software Foundation, Inc.
@@ -16,8 +17,9 @@ is included in the section entitled "GNU Free Documentation License".
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.
+
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
* Gcj: (gcj). Ahead-of-time compiler for the Java language
@@ -43,8 +45,6 @@ START-INFO-DIR-ENTRY
into one system-wide database.
END-INFO-DIR-ENTRY
-
-
Copyright (C) 2001-2015 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
@@ -61,8 +61,8 @@ is included in the section entitled "GNU Free Documentation License".
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
-software. Copies published by the Free Software Foundation raise funds
-for GNU development.
+software. Copies published by the Free Software Foundation raise
+funds for GNU development.

File: gcj.info, Node: Top, Next: Copying, Up: (dir)
@@ -70,16 +70,16 @@ File: gcj.info, Node: Top, Next: Copying, Up: (dir)
Introduction
************
-This manual describes how to use 'gcj', the GNU compiler for the Java
-programming language. 'gcj' can generate both '.class' files and object
-files, and it can read both Java source code and '.class' files.
+This manual describes how to use `gcj', the GNU compiler for the Java
+programming language. `gcj' can generate both `.class' files and
+object files, and it can read both Java source code and `.class' files.
* Menu:
* Copying:: The GNU General Public License
* GNU Free Documentation License::
How you can share and copy this manual
-* Invoking gcj:: Compiler options supported by 'gcj'
+* Invoking gcj:: Compiler options supported by `gcj'
* Compatibility:: Compatibility between gcj and other tools for Java
* Invoking jcf-dump:: Print information about class files
* Invoking gij:: Interpreting Java bytecodes
@@ -103,7 +103,7 @@ GNU General Public License
Version 3, 29 June 2007
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
@@ -131,9 +131,9 @@ want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
+these rights or asking you to surrender the rights. Therefore, you
+have certain responsibilities if you distribute copies of the software,
+or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
@@ -152,15 +152,16 @@ changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so. This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software. The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products. If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
+modified versions of the software inside them, although the
+manufacturer can do so. This is fundamentally incompatible with the
+aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for
+individuals to use, which is precisely where it is most unacceptable.
+Therefore, we have designed this version of the GPL to prohibit the
+practice for those products. If such problems arise substantially in
+other domains, we stand ready to extend this provision to those domains
+in future versions of the GPL, as needed to protect the freedom of
+users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
@@ -197,8 +198,8 @@ TERMS AND CONDITIONS
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
- infringement under applicable copyright law, except executing it on
- a computer or modifying a private copy. Propagation includes
+ infringement under applicable copyright law, except executing it
+ on a computer or modifying a private copy. Propagation includes
copying, distribution (with or without modification), making
available to the public, and in some countries other activities as
well.
@@ -212,8 +213,8 @@ TERMS AND CONDITIONS
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to
- the extent that warranties are provided), that licensees may convey
- the work under this License, and how to view a copy of this
+ the extent that warranties are provided), that licensees may
+ convey the work under this License, and how to view a copy of this
License. If the interface presents a list of user commands or
options, such as a menu, a prominent item in the list meets this
criterion.
@@ -221,8 +222,8 @@ TERMS AND CONDITIONS
1. Source Code.
The "source code" for a work means the preferred form of the work
- for making modifications to it. "Object code" means any non-source
- form of a work.
+ for making modifications to it. "Object code" means any
+ non-source form of a work.
A "Standard Interface" means an interface that either is an
official standard defined by a recognized standards body, or, in
@@ -233,10 +234,10 @@ TERMS AND CONDITIONS
The "System Libraries" of an executable work include anything,
other than the work as a whole, that (a) is included in the normal
form of packaging a Major Component, but which is not part of that
- Major Component, and (b) serves only to enable use of the work with
- that Major Component, or to implement a Standard Interface for
- which an implementation is available to the public in source code
- form. A "Major Component", in this context, means a major
+ Major Component, and (b) serves only to enable use of the work
+ with that Major Component, or to implement a Standard Interface
+ for which an implementation is available to the public in source
+ code form. A "Major Component", in this context, means a major
essential component (kernel, window system, and so on) of the
specific operating system (if any) on which the executable work
runs, or a compiler used to produce the work, or an object code
@@ -244,15 +245,15 @@ TERMS AND CONDITIONS
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
- work) run the object code and to modify the work, including scripts
- to control those activities. However, it does not include the
- work's System Libraries, or general-purpose tools or generally
+ work) run the object code and to modify the work, including
+ scripts to control those activities. However, it does not include
+ the work's System Libraries, or general-purpose tools or generally
available free programs which are used unmodified in performing
those activities but which are not part of the work. For example,
- Corresponding Source includes interface definition files associated
- with source files for the work, and the source code for shared
- libraries and dynamically linked subprograms that the work is
- specifically designed to require, such as by intimate data
+ Corresponding Source includes interface definition files
+ associated with source files for the work, and the source code for
+ shared libraries and dynamically linked subprograms that the work
+ is specifically designed to require, such as by intimate data
communication or control flow between those subprograms and other
parts of the work.
@@ -269,22 +270,22 @@ TERMS AND CONDITIONS
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running
- a covered work is covered by this License only if the output, given
- its content, constitutes a covered work. This License acknowledges
- your rights of fair use or other equivalent, as provided by
- copyright law.
+ a covered work is covered by this License only if the output,
+ given its content, constitutes a covered work. This License
+ acknowledges your rights of fair use or other equivalent, as
+ provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise
remains in force. You may convey covered works to others for the
- sole purpose of having them make modifications exclusively for you,
- or provide you with facilities for running those works, provided
- that you comply with the terms of this License in conveying all
- material for which you do not control copyright. Those thus making
- or running the covered works for you must do so exclusively on your
- behalf, under your direction and control, on terms that prohibit
- them from making any copies of your copyrighted material outside
- their relationship with you.
+ sole purpose of having them make modifications exclusively for
+ you, or provide you with facilities for running those works,
+ provided that you comply with the terms of this License in
+ conveying all material for which you do not control copyright.
+ Those thus making or running the covered works for you must do so
+ exclusively on your behalf, under your direction and control, on
+ terms that prohibit them from making any copies of your
+ copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section
@@ -301,8 +302,8 @@ TERMS AND CONDITIONS
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License
- with respect to the covered work, and you disclaim any intention to
- limit operation or modification of the work as a means of
+ with respect to the covered work, and you disclaim any intention
+ to limit operation or modification of the work as a means of
enforcing, against the work's users, your or third parties' legal
rights to forbid circumvention of technological measures.
@@ -372,8 +373,8 @@ TERMS AND CONDITIONS
b. Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
- written offer, valid for at least three years and valid for as
- long as you offer spare parts or customer support for that
+ written offer, valid for at least three years and valid for
+ as long as you offer spare parts or customer support for that
product model, to give anyone who possesses the object code
either (1) a copy of the Corresponding Source for all the
software in the product that is covered by this License, on a
@@ -383,31 +384,32 @@ TERMS AND CONDITIONS
to copy the Corresponding Source from a network server at no
charge.
- c. Convey individual copies of the object code with a copy of the
- written offer to provide the Corresponding Source. This
+ c. Convey individual copies of the object code with a copy of
+ the written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially,
and only if you received the object code with such an offer,
in accord with subsection 6b.
d. Convey the object code by offering access from a designated
- place (gratis or for a charge), and offer equivalent access to
- the Corresponding Source in the same way through the same
+ place (gratis or for a charge), and offer equivalent access
+ to the Corresponding Source in the same way through the same
place at no further charge. You need not require recipients
to copy the Corresponding Source along with the object code.
If the place to copy the object code is a network server, the
- Corresponding Source may be on a different server (operated by
- you or a third party) that supports equivalent copying
- facilities, provided you maintain clear directions next to the
- object code saying where to find the Corresponding Source.
+ Corresponding Source may be on a different server (operated
+ by you or a third party) that supports equivalent copying
+ facilities, provided you maintain clear directions next to
+ the object code saying where to find the Corresponding Source.
Regardless of what server hosts the Corresponding Source, you
- remain obligated to ensure that it is available for as long as
- needed to satisfy these requirements.
+ remain obligated to ensure that it is available for as long
+ as needed to satisfy these requirements.
e. Convey the object code using peer-to-peer transmission,
provided you inform other peers where the object code and
Corresponding Source of the work are being offered to the
general public at no charge under subsection 6d.
+
A separable portion of the object code, whose source code is
excluded from the Corresponding Source as a System Library, need
not be included in conveying the object code work.
@@ -415,8 +417,8 @@ TERMS AND CONDITIONS
A "User Product" is either (1) a "consumer product", which means
any tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
- incorporation into a dwelling. In determining whether a product is
- a consumer product, doubtful cases shall be resolved in favor of
+ incorporation into a dwelling. In determining whether a product
+ is a consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
"normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the
@@ -447,11 +449,11 @@ TERMS AND CONDITIONS
The requirement to provide Installation Information does not
include a requirement to continue to provide support service,
- warranty, or updates for a work that has been modified or installed
- by the recipient, or for the User Product in which it has been
- modified or installed. Access to a network may be denied when the
- modification itself materially and adversely affects the operation
- of the network or violates the rules and protocols for
+ warranty, or updates for a work that has been modified or
+ installed by the recipient, or for the User Product in which it
+ has been modified or installed. Access to a network may be denied
+ when the modification itself materially and adversely affects the
+ operation of the network or violates the rules and protocols for
communication across the network.
Corresponding Source conveyed, and Installation Information
@@ -481,8 +483,8 @@ TERMS AND CONDITIONS
Notwithstanding any other provision of this License, for material
you add to a covered work, you may (if authorized by the copyright
- holders of that material) supplement the terms of this License with
- terms:
+ holders of that material) supplement the terms of this License
+ with terms:
a. Disclaiming warranty or limiting liability differently from
the terms of sections 15 and 16 of this License; or
@@ -492,8 +494,9 @@ TERMS AND CONDITIONS
Legal Notices displayed by works containing it; or
c. Prohibiting misrepresentation of the origin of that material,
- or requiring that modified versions of such material be marked
- in reasonable ways as different from the original version; or
+ or requiring that modified versions of such material be
+ marked in reasonable ways as different from the original
+ version; or
d. Limiting the use for publicity purposes of names of licensors
or authors of the material; or
@@ -512,10 +515,11 @@ TERMS AND CONDITIONS
you received it, or any part of it, contains a notice stating that
it is governed by this License along with a term that is a further
restriction, you may remove that term. If a license document
- contains a further restriction but permits relicensing or conveying
- under this License, you may add to a covered work material governed
- by the terms of that license document, provided that the further
- restriction does not survive such relicensing or conveying.
+ contains a further restriction but permits relicensing or
+ conveying under this License, you may add to a covered work
+ material governed by the terms of that license document, provided
+ that the further restriction does not survive such relicensing or
+ conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
@@ -531,13 +535,13 @@ TERMS AND CONDITIONS
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights
- under this License (including any patent licenses granted under the
- third paragraph of section 11).
+ under this License (including any patent licenses granted under
+ the third paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -549,10 +553,10 @@ TERMS AND CONDITIONS
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, you do not qualify to receive new licenses
- for the same material under section 10.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, you do not qualify to receive new
+ licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
@@ -566,7 +570,7 @@ TERMS AND CONDITIONS
by modifying or propagating a covered work, you indicate your
acceptance of this License to do so.
- 10. Automatic Licensing of Downstream Recipients.
+ 10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
@@ -580,21 +584,21 @@ TERMS AND CONDITIONS
covered work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or
- could give under the previous paragraph, plus a right to possession
- of the Corresponding Source of the work from the predecessor in
- interest, if the predecessor has it or can get it with reasonable
- efforts.
+ could give under the previous paragraph, plus a right to
+ possession of the Corresponding Source of the work from the
+ predecessor in interest, if the predecessor has it or can get it
+ with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you
- may not impose a license fee, royalty, or other charge for exercise
- of rights granted under this License, and you may not initiate
- litigation (including a cross-claim or counterclaim in a lawsuit)
- alleging that any patent claim is infringed by making, using,
- selling, offering for sale, or importing the Program or any portion
- of it.
+ may not impose a license fee, royalty, or other charge for
+ exercise of rights granted under this License, and you may not
+ initiate litigation (including a cross-claim or counterclaim in a
+ lawsuit) alleging that any patent claim is infringed by making,
+ using, selling, offering for sale, or importing the Program or any
+ portion of it.
- 11. Patents.
+ 11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based.
@@ -614,15 +618,15 @@ TERMS AND CONDITIONS
Each contributor grants you a non-exclusive, worldwide,
royalty-free patent license under the contributor's essential
patent claims, to make, use, sell, offer for sale, import and
- otherwise run, modify and propagate the contents of its contributor
- version.
+ otherwise run, modify and propagate the contents of its
+ contributor version.
In the following three paragraphs, a "patent license" is any
express agreement or commitment, however denominated, not to
enforce a patent (such as an express permission to practice a
- patent or covenant not to sue for patent infringement). To "grant"
- such a patent license to a party means to make such an agreement or
- commitment not to enforce a patent against the party.
+ patent or covenant not to sue for patent infringement). To
+ "grant" such a patent license to a party means to make such an
+ agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent
license, and the Corresponding Source of the work is not available
@@ -652,35 +656,36 @@ TERMS AND CONDITIONS
conditioned on the non-exercise of one or more of the rights that
are specifically granted under this License. You may not convey a
covered work if you are a party to an arrangement with a third
- party that is in the business of distributing software, under which
- you make payment to the third party based on the extent of your
- activity of conveying the work, and under which the third party
- grants, to any of the parties who would receive the covered work
- from you, a discriminatory patent license (a) in connection with
- copies of the covered work conveyed by you (or copies made from
- those copies), or (b) primarily for and in connection with specific
- products or compilations that contain the covered work, unless you
- entered into that arrangement, or that patent license was granted,
- prior to 28 March 2007.
+ party that is in the business of distributing software, under
+ which you make payment to the third party based on the extent of
+ your activity of conveying the work, and under which the third
+ party grants, to any of the parties who would receive the covered
+ work from you, a discriminatory patent license (a) in connection
+ with copies of the covered work conveyed by you (or copies made
+ from those copies), or (b) primarily for and in connection with
+ specific products or compilations that contain the covered work,
+ unless you entered into that arrangement, or that patent license
+ was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
- 12. No Surrender of Others' Freedom.
+ 12. No Surrender of Others' Freedom.
- If conditions are imposed on you (whether by court order, agreement
- or otherwise) that contradict the conditions of this License, they
- do not excuse you from the conditions of this License. If you
- cannot convey a covered work so as to satisfy simultaneously your
- obligations under this License and any other pertinent obligations,
- then as a consequence you may not convey it at all. For example,
- if you agree to terms that obligate you to collect a royalty for
- further conveying from those to whom you convey the Program, the
- only way you could satisfy both those terms and this License would
- be to refrain entirely from conveying the Program.
+ If conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot convey a covered work so as to satisfy
+ simultaneously your obligations under this License and any other
+ pertinent obligations, then as a consequence you may not convey it
+ at all. For example, if you agree to terms that obligate you to
+ collect a royalty for further conveying from those to whom you
+ convey the Program, the only way you could satisfy both those
+ terms and this License would be to refrain entirely from conveying
+ the Program.
- 13. Use with the GNU Affero General Public License.
+ 13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
@@ -691,21 +696,22 @@ TERMS AND CONDITIONS
General Public License, section 13, concerning interaction through
a network will apply to the combination as such.
- 14. Revised Versions of this License.
+ 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new
- versions of the GNU General Public License from time to time. Such
- new versions will be similar in spirit to the present version, but
- may differ in detail to address new problems or concerns.
+ versions of the GNU General Public License from time to time.
+ Such new versions will be similar in spirit to the present
+ version, but may differ in detail to address new problems or
+ concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU
General Public License "or any later version" applies to it, you
have the option of following the terms and conditions either of
- that numbered version or of any later version published by the Free
- Software Foundation. If the Program does not specify a version
- number of the GNU General Public License, you may choose any
- version ever published by the Free Software Foundation.
+ that numbered version or of any later version published by the
+ Free Software Foundation. If the Program does not specify a
+ version number of the GNU General Public License, you may choose
+ any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that
@@ -717,24 +723,24 @@ TERMS AND CONDITIONS
author or copyright holder as a result of your choosing to follow a
later version.
- 15. Disclaimer of Warranty.
+ 15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
- APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
+ APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
- MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
NECESSARY SERVICING, REPAIR OR CORRECTION.
- 16. Limitation of Liability.
+ 16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
- AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
- DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+ AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
+ FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
@@ -742,7 +748,7 @@ TERMS AND CONDITIONS
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
- 17. Interpretation of Sections 15 and 16.
+ 17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
@@ -751,6 +757,7 @@ TERMS AND CONDITIONS
connection with the Program, unless a warranty or assumption of
liability accompanies a copy of the Program in return for a fee.
+
END OF TERMS AND CONDITIONS
===========================
@@ -781,7 +788,7 @@ state the exclusion of warranty; and each file should have at least the
General Public License for more details.
You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
+ along with this program. If not, see `http://www.gnu.org/licenses/'.
Also add information on how to contact you by electronic and paper
mail.
@@ -790,11 +797,11 @@ mail.
notice like this when it starts in an interactive mode:
PROGRAM Copyright (C) YEAR NAME OF AUTHOR
- This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
- under certain conditions; type 'show c' for details.
+ under certain conditions; type `show c' for details.
- The hypothetical commands 'show w' and 'show c' should show the
+ The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
@@ -802,14 +809,14 @@ use an "about box".
You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. For more information on this, and how to apply and follow
-the GNU GPL, see <http://www.gnu.org/licenses/>.
+the GNU GPL, see `http://www.gnu.org/licenses/'.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
-please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
+please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.

File: gcj.info, Node: GNU Free Documentation License, Next: Invoking gcj, Prev: Copying, Up: Top
@@ -820,7 +827,7 @@ GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
+ `http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -845,21 +852,21 @@ GNU Free Documentation License
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book. We
- recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it can
- be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright 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, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
- the license if you copy, modify or distribute the work in a way
- requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "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 containing the
Document or a portion of it, either copied verbatim, or with
@@ -877,12 +884,12 @@ GNU Free Documentation License
regarding them.
The "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 above definition of Secondary then it
- is not allowed to be designated as Invariant. The Document may
- contain zero Invariant Sections. If the Document does not identify
- any Invariant Sections then there are none.
+ 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 above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -893,27 +900,27 @@ GNU Free Documentation License
A "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 generic text editors or (for images composed
- of pixels) generic paint programs or (for drawings) some widely
- available drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of formats
- suitable for input to text formatters. A copy made in an otherwise
- Transparent file format whose markup, or absence 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".
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence 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".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and standard-conforming
- simple HTML, PostScript or PDF designed for human modification.
- Examples of transparent image formats include PNG, XCF and JPG.
- Opaque formats include proprietary formats that can be read and
- edited only by proprietary word processors, SGML or XML for which
- the DTD and/or processing tools are not generally available, and
- the machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
@@ -951,8 +958,8 @@ GNU Free Documentation License
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow the
- conditions in section 3.
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
@@ -966,11 +973,12 @@ GNU Free Documentation License
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on the
- covers in addition. Copying with changes limited to the covers, as
- long as they preserve the title of the Document and satisfy these
- conditions, can be treated as verbatim copying in other respects.
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
@@ -978,39 +986,40 @@ GNU Free Documentation License
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with
- each Opaque copy a computer-network location from which the general
- network-using public has access to download using public-standard
- network protocols a complete Transparent copy of the Document, free
- of added material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of Opaque
- copies in quantity, to ensure that this Transparent copy will
- remain thus accessible at the stated location until at least one
- year after the last time you distribute an Opaque copy (directly or
- through your agents or retailers) of that edition to the public.
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies,
- to give them a chance to provide you with an updated version of the
- Document.
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with the
- Modified Version filling the role of the Document, thus licensing
- distribution and modification of the Modified Version to whoever
- possesses a copy of it. In addition, you must do these things in
- the Modified Version:
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the
- History section of the Document). You may use the same title
- as a previous version if the original publisher of that
- version gives permission.
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
@@ -1040,30 +1049,31 @@ GNU Free Documentation License
I. Preserve the section Entitled "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, 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.
+ 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, 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.
J. Preserve the network location, if any, given in 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 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.
+ previous versions it was based on. These may be placed in
+ the "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.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section
- all the substance and tone of each of the contributor
+ 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.
- L. Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the
- equivalent are not considered part of the section titles.
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
@@ -1076,11 +1086,11 @@ GNU Free Documentation License
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain 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 be distinct from any other
- section titles.
+ 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 be distinct from any
+ other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
@@ -1089,15 +1099,15 @@ GNU Free Documentation License
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of
- the list of Cover Texts in the Modified Version. Only one passage
- of Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover, previously added
- by you or by arrangement made by the same entity you are acting on
- behalf of, you may not add another; but you may replace the old
- one, on explicit permission from the previous publisher that added
- the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
@@ -1107,8 +1117,8 @@ GNU Free Documentation License
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination all
- of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
@@ -1135,20 +1145,20 @@ GNU Free Documentation License
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the documents
- in all other respects.
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
7. AGGREGATION WITH INDEPENDENT WORKS
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
+ 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 the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
@@ -1193,8 +1203,8 @@ GNU Free Documentation License
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly and
- finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly
+ and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
@@ -1206,33 +1216,33 @@ GNU Free Documentation License
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from you
- under this License. If your rights have been terminated and not
- permanently reinstated, receipt of a copy of some or all of the
- same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from
+ you under this License. If your rights have been terminated and
+ not permanently reinstated, receipt of a copy of some or all of
+ the same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- <http://www.gnu.org/copyleft/>.
+ `http://www.gnu.org/copyleft/'.
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 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 Foundation. If the
- Document does not specify a version number 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
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number 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 statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
@@ -1262,6 +1272,7 @@ GNU Free Documentation License
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
+
ADDENDUM: How to use this License for your documents
====================================================
@@ -1278,7 +1289,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -1289,9 +1300,9 @@ combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of free
-software license, such as the GNU General Public License, to permit
-their use in free software.
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.

File: gcj.info, Node: Invoking gcj, Next: Compatibility, Prev: GNU Free Documentation License, Up: Top
@@ -1299,9 +1310,9 @@ File: gcj.info, Node: Invoking gcj, Next: Compatibility, Prev: GNU Free Docum
1 Invoking gcj
**************
-As 'gcj' is just another front end to 'gcc', it supports many of the
+As `gcj' is just another front end to `gcc', it supports many of the
same options as gcc. *Note Option Summary: (gcc)Option Summary. This
-manual only documents the options specific to 'gcj'.
+manual only documents the options specific to `gcj'.
* Menu:
@@ -1319,37 +1330,41 @@ File: gcj.info, Node: Input and output files, Next: Input Options, Up: Invoki
1.1 Input and output files
==========================
-A 'gcj' command is like a 'gcc' command, in that it consists of a number
-of options and file names. The following kinds of input file names are
-supported:
+A `gcj' command is like a `gcc' command, in that it consists of a
+number of options and file names. The following kinds of input file
+names are supported:
-'FILE.java'
+`FILE.java'
Java source files.
-'FILE.class'
+
+`FILE.class'
Java bytecode files.
-'FILE.zip'
-'FILE.jar'
- An archive containing one or more '.class' files, all of which are
+
+`FILE.zip'
+`FILE.jar'
+ An archive containing one or more `.class' files, all of which are
compiled. The archive may be compressed. Files in an archive
- which don't end with '.class' are treated as resource files; they
- are compiled into the resulting object file as 'core:' URLs.
-'@FILE'
+ which don't end with `.class' are treated as resource files; they
+ are compiled into the resulting object file as `core:' URLs.
+
+`@FILE'
A file containing a whitespace-separated list of input file names.
- (Currently, these must all be '.java' source files, but that may
+ (Currently, these must all be `.java' source files, but that may
change.) Each named file is compiled, just as if it had been on
the command line.
-'LIBRARY.a'
-'LIBRARY.so'
-'-lLIBNAME'
- Libraries to use when linking. See the 'gcc' manual.
- You can specify more than one input file on the 'gcj' command line,
-in which case they will all be compiled. If you specify a '-o FILENAME'
+`LIBRARY.a'
+`LIBRARY.so'
+`-lLIBNAME'
+ Libraries to use when linking. See the `gcc' manual.
+
+ You can specify more than one input file on the `gcj' command line,
+in which case they will all be compiled. If you specify a `-o FILENAME'
option, all the input files will be compiled together, producing a
single output file, named FILENAME. This is allowed even when using
-'-S' or '-c', but not when using '-C' or '--resource'. (This is an
-extension beyond the what plain 'gcc' allows.) (If more than one input
-file is specified, all must currently be '.java' files, though we hope
+`-S' or `-c', but not when using `-C' or `--resource'. (This is an
+extension beyond the what plain `gcc' allows.) (If more than one input
+file is specified, all must currently be `.java' files, though we hope
to fix this.)

@@ -1358,79 +1373,79 @@ File: gcj.info, Node: Input Options, Next: Encodings, Prev: Input and output
1.2 Input Options
=================
-'gcj' has options to control where it looks to find files it needs. For
-instance, 'gcj' might need to load a class that is referenced by the
-file it has been asked to compile. Like other compilers for the Java
-language, 'gcj' has a notion of a "class path". There are several
+`gcj' has options to control where it looks to find files it needs.
+For instance, `gcj' might need to load a class that is referenced by
+the file it has been asked to compile. Like other compilers for the
+Java language, `gcj' has a notion of a "class path". There are several
options and environment variables which can be used to manipulate the
-class path. When 'gcj' looks for a given class, it searches the class
-path looking for matching '.class' or '.java' file. 'gcj' comes with a
-built-in class path which points at the installed 'libgcj.jar', a file
+class path. When `gcj' looks for a given class, it searches the class
+path looking for matching `.class' or `.java' file. `gcj' comes with a
+built-in class path which points at the installed `libgcj.jar', a file
which contains all the standard classes.
In the text below, a directory or path component can refer either to
-an actual directory on the filesystem, or to a '.zip' or '.jar' file,
-which 'gcj' will search as if it is a directory.
+an actual directory on the filesystem, or to a `.zip' or `.jar' file,
+which `gcj' will search as if it is a directory.
-'-IDIR'
- All directories specified by '-I' are kept in order and prepended
+`-IDIR'
+ All directories specified by `-I' are kept in order and prepended
to the class path constructed from all the other options. Unless
- compatibility with tools like 'javac' is important, we recommend
- always using '-I' instead of the other options for manipulating the
+ compatibility with tools like `javac' is important, we recommend
+ always using `-I' instead of the other options for manipulating the
class path.
-'--classpath=PATH'
+`--classpath=PATH'
This sets the class path to PATH, a colon-separated list of paths
(on Windows-based systems, a semicolon-separate list of paths).
This does not override the builtin ("boot") search path.
-'--CLASSPATH=PATH'
- Deprecated synonym for '--classpath'.
+`--CLASSPATH=PATH'
+ Deprecated synonym for `--classpath'.
-'--bootclasspath=PATH'
+`--bootclasspath=PATH'
Where to find the standard builtin classes, such as
- 'java.lang.String'.
+ `java.lang.String'.
-'--extdirs=PATH'
+`--extdirs=PATH'
For each directory in the PATH, place the contents of that
directory at the end of the class path.
-'CLASSPATH'
+`CLASSPATH'
This is an environment variable which holds a list of paths.
The final class path is constructed like so:
- * First come all directories specified via '-I'.
+ * First come all directories specified via `-I'.
- * If '--classpath' is specified, its value is appended. Otherwise,
- if the 'CLASSPATH' environment variable is specified, then its
- value is appended. Otherwise, the current directory ('"."') is
+ * If `--classpath' is specified, its value is appended. Otherwise,
+ if the `CLASSPATH' environment variable is specified, then its
+ value is appended. Otherwise, the current directory (`"."') is
appended.
- * If '--bootclasspath' was specified, append its value. Otherwise,
- append the built-in system directory, 'libgcj.jar'.
+ * If `--bootclasspath' was specified, append its value. Otherwise,
+ append the built-in system directory, `libgcj.jar'.
- * Finally, if '--extdirs' was specified, append the contents of the
+ * Finally, if `--extdirs' was specified, append the contents of the
specified directories at the end of the class path. Otherwise,
append the contents of the built-in extdirs at
- '$(prefix)/share/java/ext'.
+ `$(prefix)/share/java/ext'.
- The classfile built by 'gcj' for the class 'java.lang.Object' (and
-placed in 'libgcj.jar') contains a special zero length attribute
-'gnu.gcj.gcj-compiled'. The compiler looks for this attribute when
-loading 'java.lang.Object' and will report an error if it isn't found,
+ The classfile built by `gcj' for the class `java.lang.Object' (and
+placed in `libgcj.jar') contains a special zero length attribute
+`gnu.gcj.gcj-compiled'. The compiler looks for this attribute when
+loading `java.lang.Object' and will report an error if it isn't found,
unless it compiles to bytecode (the option
-'-fforce-classes-archive-check' can be used to override this behavior in
-this particular case.)
+`-fforce-classes-archive-check' can be used to override this behavior
+in this particular case.)
-'-fforce-classes-archive-check'
+`-fforce-classes-archive-check'
This forces the compiler to always check for the special zero
- length attribute 'gnu.gcj.gcj-compiled' in 'java.lang.Object' and
+ length attribute `gnu.gcj.gcj-compiled' in `java.lang.Object' and
issue an error if it isn't found.
-'-fsource=VERSION'
- This option is used to choose the source version accepted by 'gcj'.
- The default is '1.5'.
+`-fsource=VERSION'
+ This option is used to choose the source version accepted by
+ `gcj'. The default is `1.5'.

File: gcj.info, Node: Encodings, Next: Warnings, Prev: Input Options, Up: Invoking gcj
@@ -1439,23 +1454,23 @@ File: gcj.info, Node: Encodings, Next: Warnings, Prev: Input Options, Up: In
=============
The Java programming language uses Unicode throughout. In an effort to
-integrate well with other locales, 'gcj' allows '.java' files to be
-written using almost any encoding. 'gcj' knows how to convert these
+integrate well with other locales, `gcj' allows `.java' files to be
+written using almost any encoding. `gcj' knows how to convert these
encodings into its internal encoding at compile time.
- You can use the '--encoding=NAME' option to specify an encoding (of a
-particular character set) to use for source files. If this is not
-specified, the default encoding comes from your current locale. If your
-host system has insufficient locale support, then 'gcj' assumes the
-default encoding to be the 'UTF-8' encoding of Unicode.
+ You can use the `--encoding=NAME' option to specify an encoding (of
+a particular character set) to use for source files. If this is not
+specified, the default encoding comes from your current locale. If
+your host system has insufficient locale support, then `gcj' assumes
+the default encoding to be the `UTF-8' encoding of Unicode.
- To implement '--encoding', 'gcj' simply uses the host platform's
-'iconv' conversion routine. This means that in practice 'gcj' is
+ To implement `--encoding', `gcj' simply uses the host platform's
+`iconv' conversion routine. This means that in practice `gcj' is
limited by the capabilities of the host platform.
- The names allowed for the argument '--encoding' vary from platform to
-platform (since they are not standardized anywhere). However, 'gcj'
-implements the encoding named 'UTF-8' internally, so if you choose to
+ The names allowed for the argument `--encoding' vary from platform
+to platform (since they are not standardized anywhere). However, `gcj'
+implements the encoding named `UTF-8' internally, so if you choose to
use this for your source files you can be assured that it will work on
every host.
@@ -1465,33 +1480,33 @@ File: gcj.info, Node: Warnings, Next: Linking, Prev: Encodings, Up: Invoking
1.4 Warnings
============
-'gcj' implements several warnings. As with other generic 'gcc'
-warnings, if an option of the form '-Wfoo' enables a warning, then
-'-Wno-foo' will disable it. Here we've chosen to document the form of
+`gcj' implements several warnings. As with other generic `gcc'
+warnings, if an option of the form `-Wfoo' enables a warning, then
+`-Wno-foo' will disable it. Here we've chosen to document the form of
the warning which will have an effect - the default being the opposite
of what is listed.
-'-Wredundant-modifiers'
- With this flag, 'gcj' will warn about redundant modifiers. For
- instance, it will warn if an interface method is declared 'public'.
+`-Wredundant-modifiers'
+ With this flag, `gcj' will warn about redundant modifiers. For
+ instance, it will warn if an interface method is declared `public'.
-'-Wextraneous-semicolon'
- This causes 'gcj' to warn about empty statements. Empty statements
+`-Wextraneous-semicolon'
+ This causes `gcj' to warn about empty statements. Empty statements
have been deprecated.
-'-Wno-out-of-date'
- This option will cause 'gcj' not to warn when a source file is
- newer than its matching class file. By default 'gcj' will warn
+`-Wno-out-of-date'
+ This option will cause `gcj' not to warn when a source file is
+ newer than its matching class file. By default `gcj' will warn
about this.
-'-Wno-deprecated'
+`-Wno-deprecated'
Warn if a deprecated class, method, or field is referred to.
-'-Wunused'
- This is the same as 'gcc''s '-Wunused'.
+`-Wunused'
+ This is the same as `gcc''s `-Wunused'.
-'-Wall'
- This is the same as '-Wredundant-modifiers -Wextraneous-semicolon
+`-Wall'
+ This is the same as `-Wredundant-modifiers -Wextraneous-semicolon
-Wunused'.

@@ -1502,59 +1517,62 @@ File: gcj.info, Node: Linking, Next: Code Generation, Prev: Warnings, Up: In
To turn a Java application into an executable program, you need to link
it with the needed libraries, just as for C or C++. The linker by
-default looks for a global function named 'main'. Since Java does not
+default looks for a global function named `main'. Since Java does not
have global functions, and a collection of Java classes may have more
-than one class with a 'main' method, you need to let the linker know
-which of those 'main' methods it should invoke when starting the
+than one class with a `main' method, you need to let the linker know
+which of those `main' methods it should invoke when starting the
application. You can do that in any of these ways:
- * Specify the class containing the desired 'main' method when you
- link the application, using the '--main' flag, described below.
+ * Specify the class containing the desired `main' method when you
+ link the application, using the `--main' flag, described below.
+
* Link the Java package(s) into a shared library (dll) rather than an
- executable. Then invoke the application using the 'gij' program,
- making sure that 'gij' can find the libraries it needs.
- * Link the Java packages(s) with the flag '-lgij', which links in the
- 'main' routine from the 'gij' command. This allows you to select
- the class whose 'main' method you want to run when you run the
- application. You can also use other 'gij' flags, such as '-D'
- flags to set properties. Using the '-lgij' library (rather than
- the 'gij' program of the previous mechanism) has some advantages:
+ executable. Then invoke the application using the `gij' program,
+ making sure that `gij' can find the libraries it needs.
+
+ * Link the Java packages(s) with the flag `-lgij', which links in
+ the `main' routine from the `gij' command. This allows you to
+ select the class whose `main' method you want to run when you run
+ the application. You can also use other `gij' flags, such as `-D'
+ flags to set properties. Using the `-lgij' library (rather than
+ the `gij' program of the previous mechanism) has some advantages:
it is compatible with static linking, and does not require
configuring or installing libraries.
- These 'gij' options relate to linking an executable:
+ These `gij' options relate to linking an executable:
-'--main=CLASSNAME'
+`--main=CLASSNAME'
This option is used when linking to specify the name of the class
- whose 'main' method should be invoked when the resulting executable
- is run.
+ whose `main' method should be invoked when the resulting
+ executable is run.
-'-DNAME[=VALUE]'
- This option can only be used with '--main'. It defines a system
+`-DNAME[=VALUE]'
+ This option can only be used with `--main'. It defines a system
property named NAME with value VALUE. If VALUE is not specified
then it defaults to the empty string. These system properties are
initialized at the program's startup and can be retrieved at
- runtime using the 'java.lang.System.getProperty' method.
+ runtime using the `java.lang.System.getProperty' method.
-'-lgij'
+`-lgij'
Create an application whose command-line processing is that of the
- 'gij' command.
+ `gij' command.
- This option is an alternative to using '--main'; you cannot use
+ This option is an alternative to using `--main'; you cannot use
both.
-'-static-libgcj'
+`-static-libgcj'
This option causes linking to be done against a static version of
the libgcj runtime library. This option is only available if
corresponding linker support exists.
*Caution:* Static linking of libgcj may cause essential parts of
libgcj to be omitted. Some parts of libgcj use reflection to load
- classes at runtime. Since the linker does not see these references
- at link time, it can omit the referred to classes. The result is
- usually (but not always) a 'ClassNotFoundException' being thrown at
- runtime. Caution must be used when using this option. For more
- details see: <http://gcc.gnu.org/wiki/Statically%20linking%20libgcj>
+ classes at runtime. Since the linker does not see these
+ references at link time, it can omit the referred to classes. The
+ result is usually (but not always) a `ClassNotFoundException'
+ being thrown at runtime. Caution must be used when using this
+ option. For more details see:
+ `http://gcc.gnu.org/wiki/Statically%20linking%20libgcj'

File: gcj.info, Node: Code Generation, Next: Configure-time Options, Prev: Linking, Up: Invoking gcj
@@ -1562,183 +1580,186 @@ File: gcj.info, Node: Code Generation, Next: Configure-time Options, Prev: Li
1.6 Code Generation
===================
-In addition to the many 'gcc' options controlling code generation, 'gcj'
-has several options specific to itself.
+In addition to the many `gcc' options controlling code generation,
+`gcj' has several options specific to itself.
-'-C'
- This option is used to tell 'gcj' to generate bytecode ('.class'
+`-C'
+ This option is used to tell `gcj' to generate bytecode (`.class'
files) rather than object code.
-'--resource RESOURCE-NAME'
- This option is used to tell 'gcj' to compile the contents of a
- given file to object code so it may be accessed at runtime with the
- core protocol handler as 'core:/RESOURCE-NAME'. Note that
+`--resource RESOURCE-NAME'
+ This option is used to tell `gcj' to compile the contents of a
+ given file to object code so it may be accessed at runtime with
+ the core protocol handler as `core:/RESOURCE-NAME'. Note that
RESOURCE-NAME is the name of the resource as found at runtime; for
- instance, it could be used in a call to 'ResourceBundle.getBundle'.
+ instance, it could be used in a call to `ResourceBundle.getBundle'.
The actual file name to be compiled this way must be specified
separately.
-'-ftarget=VERSION'
- This can be used with '-C' to choose the version of bytecode
- emitted by 'gcj'. The default is '1.5'. When not generating
+`-ftarget=VERSION'
+ This can be used with `-C' to choose the version of bytecode
+ emitted by `gcj'. The default is `1.5'. When not generating
bytecode, this option has no effect.
-'-d DIRECTORY'
- When used with '-C', this causes all generated '.class' files to be
- put in the appropriate subdirectory of DIRECTORY. By default they
- will be put in subdirectories of the current working directory.
+`-d DIRECTORY'
+ When used with `-C', this causes all generated `.class' files to
+ be put in the appropriate subdirectory of DIRECTORY. By default
+ they will be put in subdirectories of the current working
+ directory.
-'-fno-bounds-check'
- By default, 'gcj' generates code which checks the bounds of all
+`-fno-bounds-check'
+ By default, `gcj' generates code which checks the bounds of all
array indexing operations. With this option, these checks are
omitted, which can improve performance for code that uses arrays
extensively. Note that this can result in unpredictable behavior
if the code in question actually does violate array bounds
constraints. It is safe to use this option if you are sure that
- your code will never throw an 'ArrayIndexOutOfBoundsException'.
+ your code will never throw an `ArrayIndexOutOfBoundsException'.
-'-fno-store-check'
+`-fno-store-check'
Don't generate array store checks. When storing objects into
arrays, a runtime check is normally generated in order to ensure
- that the object is assignment compatible with the component type of
- the array (which may not be known at compile-time). With this
- option, these checks are omitted. This can improve performance for
- code which stores objects into arrays frequently. It is safe to
- use this option if you are sure your code will never throw an
- 'ArrayStoreException'.
-
-'-fjni'
- With 'gcj' there are two options for writing native methods: CNI
- and JNI. By default 'gcj' assumes you are using CNI. If you are
+ that the object is assignment compatible with the component type
+ of the array (which may not be known at compile-time). With this
+ option, these checks are omitted. This can improve performance
+ for code which stores objects into arrays frequently. It is safe
+ to use this option if you are sure your code will never throw an
+ `ArrayStoreException'.
+
+`-fjni'
+ With `gcj' there are two options for writing native methods: CNI
+ and JNI. By default `gcj' assumes you are using CNI. If you are
compiling a class with native methods, and these methods are
- implemented using JNI, then you must use '-fjni'. This option
- causes 'gcj' to generate stubs which will invoke the underlying JNI
+ implemented using JNI, then you must use `-fjni'. This option
+ causes `gcj' to generate stubs which will invoke the underlying JNI
methods.
-'-fno-assert'
- Don't recognize the 'assert' keyword. This is for compatibility
+`-fno-assert'
+ Don't recognize the `assert' keyword. This is for compatibility
with older versions of the language specification.
-'-fno-optimize-static-class-initialization'
- When the optimization level is greater or equal to '-O2', 'gcj'
+`-fno-optimize-static-class-initialization'
+ When the optimization level is greater or equal to `-O2', `gcj'
will try to optimize the way calls into the runtime are made to
initialize static classes upon their first use (this optimization
- isn't carried out if '-C' was specified.) When compiling to native
- code, '-fno-optimize-static-class-initialization' will turn this
+ isn't carried out if `-C' was specified.) When compiling to native
+ code, `-fno-optimize-static-class-initialization' will turn this
optimization off, regardless of the optimization level in use.
-'--disable-assertions[=CLASS-OR-PACKAGE]'
+`--disable-assertions[=CLASS-OR-PACKAGE]'
Don't include code for checking assertions in the compiled code.
- If '=CLASS-OR-PACKAGE' is missing disables assertion code
+ If `=CLASS-OR-PACKAGE' is missing disables assertion code
generation for all classes, unless overridden by a more specific
- '--enable-assertions' flag. If CLASS-OR-PACKAGE is a class name,
- only disables generating assertion checks within the named class or
- its inner classes. If CLASS-OR-PACKAGE is a package name, disables
- generating assertion checks within the named package or a
+ `--enable-assertions' flag. If CLASS-OR-PACKAGE is a class name,
+ only disables generating assertion checks within the named class
+ or its inner classes. If CLASS-OR-PACKAGE is a package name,
+ disables generating assertion checks within the named package or a
subpackage.
By default, assertions are enabled when generating class files or
when not optimizing, and disabled when generating optimized
binaries.
-'--enable-assertions[=CLASS-OR-PACKAGE]'
+`--enable-assertions[=CLASS-OR-PACKAGE]'
Generates code to check assertions. The option is perhaps
misnamed, as you still need to turn on assertion checking at
run-time, and we don't support any easy way to do that. So this
flag isn't very useful yet, except to partially override
- '--disable-assertions'.
-
-'-findirect-dispatch'
- 'gcj' has a special binary compatibility ABI, which is enabled by
- the '-findirect-dispatch' option. In this mode, the code generated
- by 'gcj' honors the binary compatibility guarantees in the Java
- Language Specification, and the resulting object files do not need
- to be directly linked against their dependencies. Instead, all
- dependencies are looked up at runtime. This allows free mixing of
- interpreted and compiled code.
-
- Note that, at present, '-findirect-dispatch' can only be used when
- compiling '.class' files. It will not work when compiling from
+ `--disable-assertions'.
+
+`-findirect-dispatch'
+ `gcj' has a special binary compatibility ABI, which is enabled by
+ the `-findirect-dispatch' option. In this mode, the code
+ generated by `gcj' honors the binary compatibility guarantees in
+ the Java Language Specification, and the resulting object files do
+ not need to be directly linked against their dependencies.
+ Instead, all dependencies are looked up at runtime. This allows
+ free mixing of interpreted and compiled code.
+
+ Note that, at present, `-findirect-dispatch' can only be used when
+ compiling `.class' files. It will not work when compiling from
source. CNI also does not yet work with the binary compatibility
- ABI. These restrictions will be lifted in some future release.
+ ABI. These restrictions will be lifted in some future release.
However, if you compile CNI code with the standard ABI, you can
call it from code built with the binary compatibility ABI.
-'-fbootstrap-classes'
- This option can be use to tell 'libgcj' that the compiled classes
+`-fbootstrap-classes'
+ This option can be use to tell `libgcj' that the compiled classes
should be loaded by the bootstrap loader, not the system class
loader. By default, if you compile a class and link it into an
- executable, it will be treated as if it was loaded using the system
- class loader. This is convenient, as it means that things like
- 'Class.forName()' will search 'CLASSPATH' to find the desired
+ executable, it will be treated as if it was loaded using the
+ system class loader. This is convenient, as it means that things
+ like `Class.forName()' will search `CLASSPATH' to find the desired
class.
-'-freduced-reflection'
- This option causes the code generated by 'gcj' to contain a reduced
- amount of the class meta-data used to support runtime reflection.
- The cost of this savings is the loss of the ability to use certain
- reflection capabilities of the standard Java runtime environment.
- When set all meta-data except for that which is needed to obtain
- correct runtime semantics is eliminated.
-
- For code that does not use reflection (i.e. serialization, RMI,
- CORBA or call methods in the 'java.lang.reflect' package),
- '-freduced-reflection' will result in proper operation with a
+`-freduced-reflection'
+ This option causes the code generated by `gcj' to contain a
+ reduced amount of the class meta-data used to support runtime
+ reflection. The cost of this savings is the loss of the ability to
+ use certain reflection capabilities of the standard Java runtime
+ environment. When set all meta-data except for that which is
+ needed to obtain correct runtime semantics is eliminated.
+
+ For code that does not use reflection (i.e. serialization, RMI,
+ CORBA or call methods in the `java.lang.reflect' package),
+ `-freduced-reflection' will result in proper operation with a
savings in executable code size.
- JNI ('-fjni') and the binary compatibility ABI
- ('-findirect-dispatch') do not work properly without full
- reflection meta-data. Because of this, it is an error to use these
- options with '-freduced-reflection'.
+ JNI (`-fjni') and the binary compatibility ABI
+ (`-findirect-dispatch') do not work properly without full
+ reflection meta-data. Because of this, it is an error to use
+ these options with `-freduced-reflection'.
*Caution:* If there is no reflection meta-data, code that uses a
- 'SecurityManager' may not work properly. Also calling
- 'Class.forName()' may fail if the calling method has no reflection
+ `SecurityManager' may not work properly. Also calling
+ `Class.forName()' may fail if the calling method has no reflection
meta-data.
+

File: gcj.info, Node: Configure-time Options, Prev: Code Generation, Up: Invoking gcj
1.7 Configure-time Options
==========================
-Some 'gcj' code generations options affect the resulting ABI, and so can
-only be meaningfully given when 'libgcj', the runtime package, is
-configured. 'libgcj' puts the appropriate options from this group into
-a 'spec' file which is read by 'gcj'. These options are listed here for
-completeness; if you are using 'libgcj' then you won't want to touch
-these options.
+Some `gcj' code generations options affect the resulting ABI, and so
+can only be meaningfully given when `libgcj', the runtime package, is
+configured. `libgcj' puts the appropriate options from this group into
+a `spec' file which is read by `gcj'. These options are listed here
+for completeness; if you are using `libgcj' then you won't want to
+touch these options.
-'-fuse-boehm-gc'
+`-fuse-boehm-gc'
This enables the use of the Boehm GC bitmap marking code. In
- particular this causes 'gcj' to put an object marking descriptor
+ particular this causes `gcj' to put an object marking descriptor
into each vtable.
-'-fhash-synchronization'
- By default, synchronization data (the data used for 'synchronize',
- 'wait', and 'notify') is pointed to by a word in each object. With
- this option 'gcj' assumes that this information is stored in a hash
- table and not in the object itself.
+`-fhash-synchronization'
+ By default, synchronization data (the data used for `synchronize',
+ `wait', and `notify') is pointed to by a word in each object.
+ With this option `gcj' assumes that this information is stored in a
+ hash table and not in the object itself.
-'-fuse-divide-subroutine'
+`-fuse-divide-subroutine'
On some systems, a library routine is called to perform integer
division. This is required to get exception handling correct when
dividing by zero.
-'-fcheck-references'
+`-fcheck-references'
On some systems it's necessary to insert inline checks whenever
accessing an object via a reference. On other systems you won't
- need this because null pointer accesses are caught automatically by
- the processor.
+ need this because null pointer accesses are caught automatically
+ by the processor.
-'-fuse-atomic-builtins'
+`-fuse-atomic-builtins'
On some systems, GCC can generate code for built-in atomic
operations. Use this option to force gcj to use these builtins
when compiling Java code. Where this capability is present it
should be automatically detected, so you won't usually need to use
this option.
+

File: gcj.info, Node: Compatibility, Next: Invoking jcf-dump, Prev: Invoking gcj, Up: Top
@@ -1746,14 +1767,14 @@ File: gcj.info, Node: Compatibility, Next: Invoking jcf-dump, Prev: Invoking
**************************************
As we believe it is important that the Java platform not be fragmented,
-'gcj' and 'libgcj' try to conform to the relevant Java specifications.
+`gcj' and `libgcj' try to conform to the relevant Java specifications.
However, limited manpower and incomplete and unclear documentation work
-against us. So, there are caveats to using 'gcj'.
+against us. So, there are caveats to using `gcj'.
* Menu:
-* Limitations::
-* Extensions::
+* Limitations::
+* Extensions::

File: gcj.info, Node: Limitations, Next: Extensions, Up: Compatibility
@@ -1763,29 +1784,30 @@ File: gcj.info, Node: Limitations, Next: Extensions, Up: Compatibility
This list of compatibility issues is by no means complete.
- * 'gcj' implements the JDK 1.2 language. It supports inner classes
- and the new 1.4 'assert' keyword. It does not yet support the Java
- 2 'strictfp' keyword (it recognizes the keyword but ignores it).
+ * `gcj' implements the JDK 1.2 language. It supports inner classes
+ and the new 1.4 `assert' keyword. It does not yet support the
+ Java 2 `strictfp' keyword (it recognizes the keyword but ignores
+ it).
- * 'libgcj' is largely compatible with the JDK 1.2 libraries.
- However, 'libgcj' is missing many packages, most notably
- 'java.awt'. There are also individual missing classes and methods.
+ * `libgcj' is largely compatible with the JDK 1.2 libraries.
+ However, `libgcj' is missing many packages, most notably
+ `java.awt'. There are also individual missing classes and methods.
We currently do not have a list showing differences between
- 'libgcj' and the Java 2 platform.
+ `libgcj' and the Java 2 platform.
- * Sometimes the 'libgcj' implementation of a method or class differs
+ * Sometimes the `libgcj' implementation of a method or class differs
from the JDK implementation. This is not always a bug. Still, if
- it affects you, it probably makes sense to report it so that we can
- discuss the appropriate response.
+ it affects you, it probably makes sense to report it so that we
+ can discuss the appropriate response.
- * 'gcj' does not currently allow for piecemeal replacement of
- components within 'libgcj'. Unfortunately, programmers often want
+ * `gcj' does not currently allow for piecemeal replacement of
+ components within `libgcj'. Unfortunately, programmers often want
to use newer versions of certain packages, such as those provided
by the Apache Software Foundation's Jakarta project. This has
- forced us to place the 'org.w3c.dom' and 'org.xml.sax' packages
- into their own libraries, separate from 'libgcj'. If you intend to
+ forced us to place the `org.w3c.dom' and `org.xml.sax' packages
+ into their own libraries, separate from `libgcj'. If you intend to
use these classes, you must link them explicitly with
- '-l-org-w3c-dom' and '-l-org-xml-sax'. Future versions of 'gcj'
+ `-l-org-w3c-dom' and `-l-org-xml-sax'. Future versions of `gcj'
may not have this restriction.

@@ -1794,57 +1816,58 @@ File: gcj.info, Node: Extensions, Prev: Limitations, Up: Compatibility
2.2 Extra features unique to gcj
================================
-The main feature of 'gcj' is that it can compile programs written in the
-Java programming language to native code. Most extensions that have
-been added are to facilitate this functionality.
+The main feature of `gcj' is that it can compile programs written in
+the Java programming language to native code. Most extensions that
+have been added are to facilitate this functionality.
- * 'gcj' makes it easy and efficient to mix code written in Java and
+ * `gcj' makes it easy and efficient to mix code written in Java and
C++. *Note About CNI::, for more info on how to use this in your
programs.
* When you compile your classes into a shared library using
- '-findirect-dispatch' then add them to the system-wide classmap.db
- file using 'gcj-dbtool', they will be automatically loaded by the
- 'libgcj' system classloader. This is the new, preferred
+ `-findirect-dispatch' then add them to the system-wide classmap.db
+ file using `gcj-dbtool', they will be automatically loaded by the
+ `libgcj' system classloader. This is the new, preferred
classname-to-library resolution mechanism. *Note Invoking
gcj-dbtool::, for more information on using the classmap database.
* The old classname-to-library lookup mechanism is still supported
- through the 'gnu.gcj.runtime.VMClassLoader.library_control'
+ through the `gnu.gcj.runtime.VMClassLoader.library_control'
property, but it is deprecated and will likely be removed in some
- future release. When trying to load a class 'gnu.pkg.SomeClass'
+ future release. When trying to load a class `gnu.pkg.SomeClass'
the system classloader will first try to load the shared library
- 'lib-gnu-pkg-SomeClass.so', if that fails to load the class then it
- will try to load 'lib-gnu-pkg.so' and finally when the class is
- still not loaded it will try to load 'lib-gnu.so'. Note that all
- '.'s will be transformed into '-'s and that searching for inner
+ `lib-gnu-pkg-SomeClass.so', if that fails to load the class then
+ it will try to load `lib-gnu-pkg.so' and finally when the class is
+ still not loaded it will try to load `lib-gnu.so'. Note that all
+ `.'s will be transformed into `-'s and that searching for inner
classes starts with their outermost outer class. If the class
cannot be found this way the system classloader tries to use the
- 'libgcj' bytecode interpreter to load the class from the standard
+ `libgcj' bytecode interpreter to load the class from the standard
classpath. This process can be controlled to some degree via the
- 'gnu.gcj.runtime.VMClassLoader.library_control' property; *Note
+ `gnu.gcj.runtime.VMClassLoader.library_control' property; *Note
libgcj Runtime Properties::.
- * 'libgcj' includes a special 'gcjlib' URL type. A URL of this form
- is like a 'jar' URL, and looks like
- 'gcjlib:/path/to/shared/library.so!/path/to/resource'. An access
- to one of these URLs causes the shared library to be 'dlopen()'d,
+ * `libgcj' includes a special `gcjlib' URL type. A URL of this form
+ is like a `jar' URL, and looks like
+ `gcjlib:/path/to/shared/library.so!/path/to/resource'. An access
+ to one of these URLs causes the shared library to be `dlopen()'d,
and then the resource is looked for in that library. These URLs
are most useful when used in conjunction with
- 'java.net.URLClassLoader'. Note that, due to implementation
+ `java.net.URLClassLoader'. Note that, due to implementation
limitations, currently any such URL can be accessed by only one
class loader, and libraries are never unloaded. This means some
- care must be exercised to make sure that a 'gcjlib' URL is not
+ care must be exercised to make sure that a `gcjlib' URL is not
accessed by more than one class loader at once. In a future
release this limitation will be lifted, and such libraries will be
mapped privately.
- * A program compiled by 'gcj' will examine the 'GCJ_PROPERTIES'
+ * A program compiled by `gcj' will examine the `GCJ_PROPERTIES'
environment variable and change its behavior in some ways. In
- particular 'GCJ_PROPERTIES' holds a list of assignments to global
- properties, such as would be set with the '-D' option to 'java'.
- For instance, 'java.compiler=gcj' is a valid (but currently
- meaningless) setting.
+ particular `GCJ_PROPERTIES' holds a list of assignments to global
+ properties, such as would be set with the `-D' option to `java'.
+ For instance, `java.compiler=gcj' is a valid (but currently
+ meaningless) setting.
+

File: gcj.info, Node: Invoking jcf-dump, Next: Invoking gij, Prev: Compatibility, Up: Top
@@ -1852,37 +1875,37 @@ File: gcj.info, Node: Invoking jcf-dump, Next: Invoking gij, Prev: Compatibil
3 Invoking jcf-dump
*******************
-This is a class file examiner, similar to 'javap'. It will print
+This is a class file examiner, similar to `javap'. It will print
information about a number of classes, which are specified by class name
or file name.
-'-c'
+`-c'
Disassemble method bodies. By default method bodies are not
printed.
-'--print-constants'
+`--print-constants'
Print the constant pool. When printing a reference to a constant
also print its index in the constant pool.
-'--javap'
- Generate output in 'javap' format. The implementation of this
+`--javap'
+ Generate output in `javap' format. The implementation of this
feature is very incomplete.
-'--classpath=PATH'
-'--CLASSPATH=PATH'
-'-IDIRECTORY'
-'-o FILE'
- These options as the same as the corresponding 'gcj' options.
+`--classpath=PATH'
+`--CLASSPATH=PATH'
+`-IDIRECTORY'
+`-o FILE'
+ These options as the same as the corresponding `gcj' options.
-'--help'
+`--help'
Print help, then exit.
-'--version'
+`--version'
Print version number, then exit.
-'-v, --verbose'
+`-v, --verbose'
Print extra information while running. Implies
- '--print-constants'.
+ `--print-constants'.

File: gcj.info, Node: Invoking gij, Next: Invoking gcj-dbtool, Prev: Invoking jcf-dump, Up: Top
@@ -1890,100 +1913,100 @@ File: gcj.info, Node: Invoking gij, Next: Invoking gcj-dbtool, Prev: Invoking
4 Invoking gij
**************
-'gij' is a Java bytecode interpreter included with 'libgcj'. 'gij' is
+`gij' is a Java bytecode interpreter included with `libgcj'. `gij' is
not available on every platform; porting it requires a small amount of
assembly programming which has not been done for all the targets
-supported by 'gcj'.
+supported by `gcj'.
- The primary argument to 'gij' is the name of a class or, with '-jar',
-a jar file. Options before this argument are interpreted by 'gij';
-remaining options are passed to the interpreted program.
+ The primary argument to `gij' is the name of a class or, with
+`-jar', a jar file. Options before this argument are interpreted by
+`gij'; remaining options are passed to the interpreted program.
- If a class name is specified and this class does not have a 'main'
-method with the appropriate signature (a 'static void' method with a
-'String[]' as its sole argument), then 'gij' will print an error and
+ If a class name is specified and this class does not have a `main'
+method with the appropriate signature (a `static void' method with a
+`String[]' as its sole argument), then `gij' will print an error and
exit.
- If a jar file is specified then 'gij' will use information in it to
-determine which class' 'main' method will be invoked.
+ If a jar file is specified then `gij' will use information in it to
+determine which class' `main' method will be invoked.
- 'gij' will invoke the 'main' method with all the remaining
+ `gij' will invoke the `main' method with all the remaining
command-line options.
- Note that 'gij' is not limited to interpreting code. Because
-'libgcj' includes a class loader which can dynamically load shared
-objects, it is possible to give 'gij' the name of a class which has been
-compiled and put into a shared library on the class path.
+ Note that `gij' is not limited to interpreting code. Because
+`libgcj' includes a class loader which can dynamically load shared
+objects, it is possible to give `gij' the name of a class which has
+been compiled and put into a shared library on the class path.
-'-cp PATH'
-'-classpath PATH'
+`-cp PATH'
+`-classpath PATH'
Set the initial class path. The class path is used for finding
class and resource files. If specified, this option overrides the
- 'CLASSPATH' environment variable. Note that this option is ignored
- if '-jar' is used.
+ `CLASSPATH' environment variable. Note that this option is
+ ignored if `-jar' is used.
-'-DNAME[=VALUE]'
+`-DNAME[=VALUE]'
This defines a system property named NAME with value VALUE. If
- VALUE is not specified then it defaults to the empty string. These
- system properties are initialized at the program's startup and can
- be retrieved at runtime using the 'java.lang.System.getProperty'
- method.
+ VALUE is not specified then it defaults to the empty string.
+ These system properties are initialized at the program's startup
+ and can be retrieved at runtime using the
+ `java.lang.System.getProperty' method.
-'-ms=NUMBER'
- Equivalent to '-Xms'.
+`-ms=NUMBER'
+ Equivalent to `-Xms'.
-'-mx=NUMBER'
- Equivalent to '-Xmx'.
+`-mx=NUMBER'
+ Equivalent to `-Xmx'.
-'-noverify'
- Do not verify compliance of bytecode with the VM specification. In
- addition, this option disables type verification which is otherwise
- performed on BC-ABI compiled code.
+`-noverify'
+ Do not verify compliance of bytecode with the VM specification. In
+ addition, this option disables type verification which is
+ otherwise performed on BC-ABI compiled code.
-'-X'
-'-XARGUMENT'
- Supplying '-X' by itself will cause 'gij' to list all the supported
- '-X' options. Currently these options are supported:
+`-X'
+`-XARGUMENT'
+ Supplying `-X' by itself will cause `gij' to list all the
+ supported `-X' options. Currently these options are supported:
- '-XmsSIZE'
+ `-XmsSIZE'
Set the initial heap size.
- '-XmxSIZE'
+ `-XmxSIZE'
Set the maximum heap size.
- '-XssSIZE'
+ `-XssSIZE'
Set the thread stack size.
- Unrecognized '-X' options are ignored, for compatibility with other
- runtimes.
+ Unrecognized `-X' options are ignored, for compatibility with
+ other runtimes.
-'-jar'
- This indicates that the name passed to 'gij' should be interpreted
+`-jar'
+ This indicates that the name passed to `gij' should be interpreted
as the name of a jar file, not a class.
-'--help'
-'-?'
+`--help'
+`-?'
Print help, then exit.
-'--showversion'
+`--showversion'
Print version number and continue.
-'--fullversion'
+`--fullversion'
Print detailed version information, then exit.
-'--version'
+`--version'
Print version number, then exit.
-'-verbose'
-'-verbose:class'
- Each time a class is initialized, print a short message on standard
- error.
+`-verbose'
+`-verbose:class'
+ Each time a class is initialized, print a short message on
+ standard error.
- 'gij' also recognizes and ignores the following options, for
-compatibility with existing application launch scripts: '-client',
-'-server', '-hotspot', '-jrockit', '-agentlib', '-agentpath', '-debug',
-'-d32', '-d64', '-javaagent', '-noclassgc', '-verify', and
-'-verifyremote'.
+ `gij' also recognizes and ignores the following options, for
+compatibility with existing application launch scripts: `-client',
+`-server', `-hotspot', `-jrockit', `-agentlib', `-agentpath', `-debug',
+`-d32', `-d64', `-javaagent', `-noclassgc', `-verify', and
+`-verifyremote'.

File: gcj.info, Node: Invoking gcj-dbtool, Next: Invoking jv-convert, Prev: Invoking gij, Up: Top
@@ -1991,102 +2014,103 @@ File: gcj.info, Node: Invoking gcj-dbtool, Next: Invoking jv-convert, Prev: I
5 Invoking gcj-dbtool.
**********************
-'gcj-dbtool' is a tool for creating and manipulating class file mapping
-databases. 'libgcj' can use these databases to find a shared library
+`gcj-dbtool' is a tool for creating and manipulating class file mapping
+databases. `libgcj' can use these databases to find a shared library
corresponding to the bytecode representation of a class. This
functionality is useful for ahead-of-time compilation of a program that
-has no knowledge of 'gcj'.
+has no knowledge of `gcj'.
- 'gcj-dbtool' works best if all the jar files added to it are compiled
-using '-findirect-dispatch'.
+ `gcj-dbtool' works best if all the jar files added to it are
+compiled using `-findirect-dispatch'.
- Note that 'gcj-dbtool' is currently available as "preview
+ Note that `gcj-dbtool' is currently available as "preview
technology". We believe it is a reasonable way to allow
application-transparent ahead-of-time compilation, but this is an
unexplored area. We welcome your comments.
-'-n DBFILE [SIZE]'
+`-n DBFILE [SIZE]'
This creates a new database. Currently, databases cannot be
resized; you can choose a larger initial size if desired. The
default size is 32,749.
-'-a DBFILE JARFILE LIB'
-'-f DBFILE JARFILE LIB'
+`-a DBFILE JARFILE LIB'
+`-f DBFILE JARFILE LIB'
This adds a jar file to the database. For each class file in the
jar, a cryptographic signature of the bytecode representation of
the class is recorded in the database. At runtime, a class is
looked up by its signature and the compiled form of the class is
- looked for in the corresponding shared library. The '-a' option
- will verify that LIB exists before adding it to the database; '-f'
+ looked for in the corresponding shared library. The `-a' option
+ will verify that LIB exists before adding it to the database; `-f'
skips this check.
-'[-][-0] -m DBFILE DBFILE,[DBFILE]'
+`[`-'][`-0'] -m DBFILE DBFILE,[DBFILE]'
Merge a number of databases. The output database overwrites any
existing database. To add databases into an existing database,
include the destination in the list of sources.
- If '-' or '-0' are used, the list of files to read is taken from
- standard input instead of the command line. For '-0', Input
+ If `-' or `-0' are used, the list of files to read is taken from
+ standard input instead of the command line. For `-0', Input
filenames are terminated by a null character instead of by
whitespace. Useful when arguments might contain white space. The
GNU find -print0 option produces input suitable for this mode.
-'-t DBFILE'
+`-t DBFILE'
Test a database.
-'-l DBFILE'
+`-l DBFILE'
List the contents of a database.
-'-p'
+`-p'
Print the name of the default database. If there is no default
- database, this prints a blank line. If LIBDIR is specified, use it
- instead of the default library directory component of the database
- name.
+ database, this prints a blank line. If LIBDIR is specified, use
+ it instead of the default library directory component of the
+ database name.
-'--help'
+`--help'
Print a help message, then exit.
-'--version'
-'-v'
+`--version'
+`-v'
Print version information, then exit.
+

File: gcj.info, Node: Invoking jv-convert, Next: Invoking grmic, Prev: Invoking gcj-dbtool, Up: Top
6 Invoking jv-convert
*********************
-'jv-convert' ['OPTION'] ... [INPUTFILE [OUTPUTFILE]]
+`jv-convert' [`OPTION'] ... [INPUTFILE [OUTPUTFILE]]
- 'jv-convert' is a utility included with 'libgcj' which converts a
-file from one encoding to another. It is similar to the Unix 'iconv'
+ `jv-convert' is a utility included with `libgcj' which converts a
+file from one encoding to another. It is similar to the Unix `iconv'
utility.
- The encodings supported by 'jv-convert' are platform-dependent.
+ The encodings supported by `jv-convert' are platform-dependent.
Currently there is no way to get a list of all supported encodings.
-'--encoding NAME'
-'--from NAME'
+`--encoding NAME'
+`--from NAME'
Use NAME as the input encoding. The default is the current
locale's encoding.
-'--to NAME'
- Use NAME as the output encoding. The default is the 'JavaSrc'
- encoding; this is ASCII with '\u' escapes for non-ASCII characters.
+`--to NAME'
+ Use NAME as the output encoding. The default is the `JavaSrc'
+ encoding; this is ASCII with `\u' escapes for non-ASCII characters.
-'-i FILE'
+`-i FILE'
Read from FILE. The default is to read from standard input.
-'-o FILE'
+`-o FILE'
Write to FILE. The default is to write to standard output.
-'--reverse'
+`--reverse'
Swap the input and output encodings.
-'--help'
+`--help'
Print a help message, then exit.
-'--version'
+`--version'
Print version information, then exit.

@@ -2095,49 +2119,49 @@ File: gcj.info, Node: Invoking grmic, Next: Invoking gc-analyze, Prev: Invoki
7 Invoking grmic
****************
-'grmic' ['OPTION'] ... CLASS ...
+`grmic' [`OPTION'] ... CLASS ...
- 'grmic' is a utility included with 'libgcj' which generates stubs for
-remote objects.
+ `grmic' is a utility included with `libgcj' which generates stubs
+for remote objects.
Note that this program isn't yet fully compatible with the JDK
-'grmic'. Some options, such as '-classpath', are recognized but
+`grmic'. Some options, such as `-classpath', are recognized but
currently ignored. We have left these options undocumented for now.
- Long options can also be given with a GNU-style leading '--'. For
-instance, '--help' is accepted.
+ Long options can also be given with a GNU-style leading `--'. For
+instance, `--help' is accepted.
-'-keep'
-'-keepgenerated'
- By default, 'grmic' deletes intermediate files. Either of these
+`-keep'
+`-keepgenerated'
+ By default, `grmic' deletes intermediate files. Either of these
options causes it not to delete such files.
-'-v1.1'
- Cause 'grmic' to create stubs and skeletons for the 1.1 protocol
+`-v1.1'
+ Cause `grmic' to create stubs and skeletons for the 1.1 protocol
version.
-'-vcompat'
- Cause 'grmic' to create stubs and skeletons compatible with both
+`-vcompat'
+ Cause `grmic' to create stubs and skeletons compatible with both
the 1.1 and 1.2 protocol versions. This is the default.
-'-v1.2'
- Cause 'grmic' to create stubs and skeletons for the 1.2 protocol
+`-v1.2'
+ Cause `grmic' to create stubs and skeletons for the 1.2 protocol
version.
-'-nocompile'
+`-nocompile'
Don't compile the generated files.
-'-verbose'
- Print information about what 'grmic' is doing.
+`-verbose'
+ Print information about what `grmic' is doing.
-'-d DIRECTORY'
- Put output files in DIRECTORY. By default the files are put in the
- current working directory.
+`-d DIRECTORY'
+ Put output files in DIRECTORY. By default the files are put in
+ the current working directory.
-'-help'
+`-help'
Print a help message, then exit.
-'-version'
+`-version'
Print version information, then exit.

@@ -2146,18 +2170,18 @@ File: gcj.info, Node: Invoking gc-analyze, Next: Invoking aot-compile, Prev:
8 Invoking gc-analyze
*********************
-'gc-analyze' ['OPTION'] ... [FILE]
+`gc-analyze' [`OPTION'] ... [FILE]
- 'gc-analyze' prints an analysis of a GC memory dump to standard out.
+ `gc-analyze' prints an analysis of a GC memory dump to standard out.
The memory dumps may be created by calling
-'gnu.gcj.util.GCInfo.enumerate(String namePrefix)' from java code. A
+`gnu.gcj.util.GCInfo.enumerate(String namePrefix)' from java code. A
memory dump will be created on an out of memory condition if
-'gnu.gcj.util.GCInfo.setOOMDump(String namePrefix)' is called before the
-out of memory occurs.
+`gnu.gcj.util.GCInfo.setOOMDump(String namePrefix)' is called before
+the out of memory occurs.
- Running this program will create two files: 'TestDump001' and
-'TestDump001.bytes'.
+ Running this program will create two files: `TestDump001' and
+`TestDump001.bytes'.
import gnu.gcj.util.*;
import java.util.*;
@@ -2179,21 +2203,21 @@ out of memory occurs.
gc-analyze -v TestDump001
-'--verbose'
-'-v'
+`--verbose'
+`-v'
Verbose output.
-'-p TOOL-PREFIX'
- Prefix added to the names of the 'nm' and 'readelf' commands.
+`-p TOOL-PREFIX'
+ Prefix added to the names of the `nm' and `readelf' commands.
-'-d DIRECTORY'
+`-d DIRECTORY'
Directory that contains the executable and shared libraries used
when the dump was generated.
-'--help'
+`--help'
Print a help message, then exit.
-'--version'
+`--version'
Print version information, then exit.

@@ -2202,41 +2226,42 @@ File: gcj.info, Node: Invoking aot-compile, Next: Invoking rebuild-gcj-db, Pr
9 Invoking aot-compile
**********************
-'aot-compile' is a script that searches a directory for Java bytecode
-(as class files, or in jars) and uses 'gcj' to compile it to native code
-and generate the databases from it.
+`aot-compile' is a script that searches a directory for Java bytecode
+(as class files, or in jars) and uses `gcj' to compile it to native
+code and generate the databases from it.
-'-M, --make=PATH'
- Specify the path to the 'make' executable to use.
+`-M, --make=PATH'
+ Specify the path to the `make' executable to use.
-'-C, --gcj=PATH'
- Specify the path to the 'gcj' executable to use.
+`-C, --gcj=PATH'
+ Specify the path to the `gcj' executable to use.
-'-D, --dbtool=PATH'
- Specify the path to the 'gcj-dbtool' executable to use.
+`-D, --dbtool=PATH'
+ Specify the path to the `gcj-dbtool' executable to use.
-'-m, --makeflags=FLAGS'
- Specify flags to pass to 'make' during the build.
+`-m, --makeflags=FLAGS'
+ Specify flags to pass to `make' during the build.
-'-c, --gcjflags=FLAGS'
- Specify flags to pass to 'gcj' during compilation, in addition to
+`-c, --gcjflags=FLAGS'
+ Specify flags to pass to `gcj' during compilation, in addition to
'-fPIC -findirect-dispatch -fjni'.
-'-l, --ldflags=FLAGS'
- Specify flags to pass to 'gcj' during linking, in addition to
+`-l, --ldflags=FLAGS'
+ Specify flags to pass to `gcj' during linking, in addition to
'-Wl,-Bsymbolic'.
-'-e, --exclude=PATH'
+`-e, --exclude=PATH'
Do not compile PATH.
+

File: gcj.info, Node: Invoking rebuild-gcj-db, Next: About CNI, Prev: Invoking aot-compile, Up: Top
10 Invoking rebuild-gcj-db
**************************
-'rebuild-gcj-db' is a script that merges the per-solib databases made by
-'aot-compile' into one system-wide database so 'gij' can find the
+`rebuild-gcj-db' is a script that merges the per-solib databases made by
+`aot-compile' into one system-wide database so `gij' can find the
solibs.

@@ -2279,9 +2304,9 @@ File: gcj.info, Node: Basic concepts, Next: Packages, Up: About CNI
In terms of languages features, Java is mostly a subset of C++. Java
has a few important extensions, plus a powerful standard class library,
but on the whole that does not change the basic similarity. Java is a
-hybrid object-oriented language, with a few native types, in addition to
-class types. It is class-based, where a class may have static as well
-as per-object fields, and static as well as instance methods.
+hybrid object-oriented language, with a few native types, in addition
+to class types. It is class-based, where a class may have static as
+well as per-object fields, and static as well as instance methods.
Non-static methods may be virtual, and may be overloaded. Overloading
is resolved at compile time by matching the actual argument types
against the parameter types. Virtual methods are implemented using
@@ -2291,13 +2316,13 @@ method. Classes are organized in a package hierarchy.
All of the listed attributes are also true of C++, though C++ has
extra features (for example in C++ objects may be allocated not just on
-the heap, but also statically or in a local stack frame). Because 'gcj'
-uses the same compiler technology as G++ (the GNU C++ compiler), it is
-possible to make the intersection of the two languages use the same ABI
-(object representation and calling conventions). The key idea in CNI is
-that Java objects are C++ objects, and all Java classes are C++ classes
-(but not the other way around). So the most important task in
-integrating Java and C++ is to remove gratuitous incompatibilities.
+the heap, but also statically or in a local stack frame). Because
+`gcj' uses the same compiler technology as G++ (the GNU C++ compiler),
+it is possible to make the intersection of the two languages use the
+same ABI (object representation and calling conventions). The key idea
+in CNI is that Java objects are C++ objects, and all Java classes are
+C++ classes (but not the other way around). So the most important task
+in integrating Java and C++ is to remove gratuitous incompatibilities.
You write CNI code as a regular C++ source file. (You do have to use
a Java/CNI-aware C++ compiler, specifically a recent version of G++.)
@@ -2312,14 +2337,14 @@ and then must include one header file for each Java class it uses, e.g.:
#include <java/util/Date.h>
#include <java/lang/IndexOutOfBoundsException.h>
-These header files are automatically generated by 'gcjh'.
+These header files are automatically generated by `gcjh'.
CNI provides some functions and macros to make using Java objects and
primitive types from C++ easier. In general, these CNI functions and
-macros start with the 'Jv' prefix, for example the function
-'JvNewObjectArray'. This convention is used to avoid conflicts with
+macros start with the `Jv' prefix, for example the function
+`JvNewObjectArray'. This convention is used to avoid conflicts with
other libraries. Internal functions in CNI start with the prefix
-'_Jv_'. You should not call these; if you find a need to, let us know
+`_Jv_'. You should not call these; if you find a need to, let us know
and we will try to come up with an alternate solution.
11.1.1 Limitations
@@ -2330,7 +2355,7 @@ freed from the shackles of Java, a CNI C++ class must adhere to the
rules of the Java programming language.
For example: it is not possible to declare a method in a CNI class
-that will take a C string ('char*') as an argument, or to declare a
+that will take a C string (`char*') as an argument, or to declare a
member variable of some non-Java datatype.

@@ -2345,9 +2370,10 @@ sub-packages. Every class belongs to either an unnamed package or a
package that has a hierarchical and globally unique name.
A Java package is mapped to a C++ "namespace". The Java class
-'java.lang.String' is in the package 'java.lang', which is a sub-package
-of 'java'. The C++ equivalent is the class 'java::lang::String', which
-is in the namespace 'java::lang' which is in the namespace 'java'.
+`java.lang.String' is in the package `java.lang', which is a
+sub-package of `java'. The C++ equivalent is the class
+`java::lang::String', which is in the namespace `java::lang' which is
+in the namespace `java'.
Here is how you could express this:
@@ -2365,7 +2391,7 @@ Here is how you could express this:
...
};
-The 'gcjh' tool automatically generates the necessary namespace
+The `gcjh' tool automatically generates the necessary namespace
declarations.
11.2.1 Leaving out package names
@@ -2374,20 +2400,20 @@ declarations.
Always using the fully-qualified name of a java class can be tiresomely
verbose. Using the full qualified name also ties the code to a single
package making code changes necessary should the class move from one
-package to another. The Java 'package' declaration specifies that the
-following class declarations are in the named package, without having to
-explicitly name the full package qualifiers. The 'package' declaration
-can be followed by zero or more 'import' declarations, which allows
-either a single class or all the classes in a package to be named by a
-simple identifier. C++ provides something similar with the 'using'
-declaration and directive.
+package to another. The Java `package' declaration specifies that the
+following class declarations are in the named package, without having
+to explicitly name the full package qualifiers. The `package'
+declaration can be followed by zero or more `import' declarations, which
+allows either a single class or all the classes in a package to be
+named by a simple identifier. C++ provides something similar with the
+`using' declaration and directive.
In Java:
import PACKAGE-NAME.CLASS-NAME;
allows the program text to refer to CLASS-NAME as a shorthand for the
-fully qualified name: 'PACKAGE-NAME.CLASS-NAME'.
+fully qualified name: `PACKAGE-NAME.CLASS-NAME'.
To achieve the same effect C++, you have to do this:
@@ -2397,8 +2423,8 @@ Java can also cause imports on demand, like this:
import PACKAGE-NAME.*;
-Doing this allows any class from the package PACKAGE-NAME to be referred
-to only by its class-name within the program text.
+Doing this allows any class from the package PACKAGE-NAME to be
+referred to only by its class-name within the program text.
The same effect can be achieved in C++ like this:
@@ -2418,33 +2444,34 @@ example) so CNI provides a special C++ type for each primitive Java
type:
*Java type* *C/C++ typename* *Description*
-'char' 'jchar' 16 bit Unicode character
-'boolean' 'jboolean' logical (true or false) values
-'byte' 'jbyte' 8-bit signed integer
-'short' 'jshort' 16 bit signed integer
-'int' 'jint' 32 bit signed integer
-'long' 'jlong' 64 bit signed integer
-'float' 'jfloat' 32 bit IEEE floating point number
-'double' 'jdouble' 64 bit IEEE floating point number
-'void' 'void' no value
+`char' `jchar' 16 bit Unicode character
+`boolean' `jboolean' logical (true or false) values
+`byte' `jbyte' 8-bit signed integer
+`short' `jshort' 16 bit signed integer
+`int' `jint' 32 bit signed integer
+`long' `jlong' 64 bit signed integer
+`float' `jfloat' 32 bit IEEE floating point number
+`double' `jdouble' 64 bit IEEE floating point number
+`void' `void' no value
When referring to a Java type You should always use these C++
-typenames (e.g.: 'jint') to avoid disappointment.
+typenames (e.g.: `jint') to avoid disappointment.
11.3.1 Reference types associated with primitive types
------------------------------------------------------
In Java each primitive type has an associated reference type, e.g.:
-'boolean' has an associated 'java.lang.Boolean.TYPE' class. In order to
-make working with such classes easier GCJ provides the macro
-'JvPrimClass':
+`boolean' has an associated `java.lang.Boolean.TYPE' class. In order
+to make working with such classes easier GCJ provides the macro
+`JvPrimClass':
-- macro: JvPrimClass type
- Return a pointer to the 'Class' object corresponding to the type
+ Return a pointer to the `Class' object corresponding to the type
supplied.
JvPrimClass(void) => java.lang.Void.TYPE
+

File: gcj.info, Node: Reference types, Next: Interfaces, Prev: Primitive types, Up: About CNI
@@ -2453,22 +2480,22 @@ File: gcj.info, Node: Reference types, Next: Interfaces, Prev: Primitive type
A Java reference type is treated as a class in C++. Classes and
interfaces are handled this way. A Java reference is translated to a
-C++ pointer, so for instance a Java 'java.lang.String' becomes, in C++,
-'java::lang::String *'.
+C++ pointer, so for instance a Java `java.lang.String' becomes, in C++,
+`java::lang::String *'.
CNI provides a few built-in typedefs for the most common classes:
*Java type* *C++ typename* *Description*
-'java.lang.Object' 'jobject' Object type
-'java.lang.String' 'jstring' String type
-'java.lang.Class' 'jclass' Class type
-
- Every Java class or interface has a corresponding 'Class' instance.
-These can be accessed in CNI via the static 'class$' field of a class.
-The 'class$' field is of type 'Class' (and not 'Class *'), so you will
-typically take the address of it.
-
- Here is how you can refer to the class of 'String', which in Java
-would be written 'String.class':
+`java.lang.Object' `jobject' Object type
+`java.lang.String' `jstring' String type
+`java.lang.Class' `jclass' Class type
+
+ Every Java class or interface has a corresponding `Class' instance.
+These can be accessed in CNI via the static `class$' field of a class.
+The `class$' field is of type `Class' (and not `Class *'), so you will
+typically take the address of it.
+
+ Here is how you can refer to the class of `String', which in Java
+would be written `String.class':
using namespace java::lang;
doSomething (&String::class$);
@@ -2482,13 +2509,14 @@ File: gcj.info, Node: Interfaces, Next: Objects and Classes, Prev: Reference
A Java class can "implement" zero or more "interfaces", in addition to
inheriting from a single base class.
- CNI allows CNI code to implement methods of interfaces. You can also
-call methods through interface references, with some limitations.
+ CNI allows CNI code to implement methods of interfaces. You can
+also call methods through interface references, with some limitations.
- CNI doesn't understand interface inheritance at all yet. So, you can
-only call an interface method when the declared type of the field being
-called matches the interface which declares that method. The workaround
-is to cast the interface reference to the right superinterface.
+ CNI doesn't understand interface inheritance at all yet. So, you
+can only call an interface method when the declared type of the field
+being called matches the interface which declares that method. The
+workaround is to cast the interface reference to the right
+superinterface.
For example if you have:
@@ -2502,8 +2530,8 @@ is to cast the interface reference to the right superinterface.
void b();
}
- and declare a variable of type 'B' in C++, you can't call 'a()'
-unless you cast it to an 'A' first.
+ and declare a variable of type `B' in C++, you can't call `a()'
+unless you cast it to an `A' first.

File: gcj.info, Node: Objects and Classes, Next: Class Initialization, Prev: Interfaces, Up: About CNI
@@ -2514,13 +2542,13 @@ File: gcj.info, Node: Objects and Classes, Next: Class Initialization, Prev:
11.6.1 Classes
--------------
-All Java classes are derived from 'java.lang.Object'. C++ does not have
-a unique root class, but we use the C++ class 'java::lang::Object' as
-the C++ version of the 'java.lang.Object' Java class. All other Java
-classes are mapped into corresponding C++ classes derived from
-'java::lang::Object'.
+All Java classes are derived from `java.lang.Object'. C++ does not
+have a unique root class, but we use the C++ class `java::lang::Object'
+as the C++ version of the `java.lang.Object' Java class. All other
+Java classes are mapped into corresponding C++ classes derived from
+`java::lang::Object'.
- Interface inheritance (the 'implements' keyword) is currently not
+ Interface inheritance (the `implements' keyword) is currently not
reflected in the C++ mapping.
11.6.2 Object fields
@@ -2528,18 +2556,18 @@ reflected in the C++ mapping.
Each object contains an object header, followed by the instance fields
of the class, in order. The object header consists of a single pointer
-to a dispatch or virtual function table. (There may be extra fields _in
-front of_ the object, for example for memory management, but this is
-invisible to the application, and the reference to the object points to
-the dispatch table pointer.)
+to a dispatch or virtual function table. (There may be extra fields
+_in front of_ the object, for example for memory management, but this
+is invisible to the application, and the reference to the object points
+to the dispatch table pointer.)
The fields are laid out in the same order, alignment, and size as in
-C++. Specifically, 8-bit and 16-bit native types ('byte', 'short',
-'char', and 'boolean') are _not_ widened to 32 bits. Note that the Java
-VM does extend 8-bit and 16-bit types to 32 bits when on the VM stack or
-temporary registers.
+C++. Specifically, 8-bit and 16-bit native types (`byte', `short',
+`char', and `boolean') are _not_ widened to 32 bits. Note that the
+Java VM does extend 8-bit and 16-bit types to 32 bits when on the VM
+stack or temporary registers.
- If you include the 'gcjh'-generated header for a class, you can
+ If you include the `gcjh'-generated header for a class, you can
access fields of Java classes in the _natural_ way. For example, given
the following Java class:
@@ -2567,9 +2595,9 @@ the following Java class:
------------------------
CNI does not strictly enforce the Java access specifiers, because Java
-permissions cannot be directly mapped into C++ permission. Private Java
-fields and methods are mapped to private C++ fields and methods, but
-other fields and methods are mapped to public fields and methods.
+permissions cannot be directly mapped into C++ permission. Private
+Java fields and methods are mapped to private C++ fields and methods,
+but other fields and methods are mapped to public fields and methods.

File: gcj.info, Node: Class Initialization, Next: Object allocation, Prev: Objects and Classes, Up: About CNI
@@ -2578,41 +2606,44 @@ File: gcj.info, Node: Class Initialization, Next: Object allocation, Prev: Ob
=========================
Java requires that each class be automatically initialized at the time
-of the first active use. Initializing a class involves initializing the
-static fields, running code in class initializer methods, and
+of the first active use. Initializing a class involves initializing
+the static fields, running code in class initializer methods, and
initializing base classes. There may also be some implementation
-specific actions, such as allocating 'String' objects corresponding to
+specific actions, such as allocating `String' objects corresponding to
string literals in the code.
- The GCJ compiler inserts calls to 'JvInitClass' at appropriate places
-to ensure that a class is initialized when required. The C++ compiler
-does not insert these calls automatically--it is the programmer's
-responsibility to make sure classes are initialized. However, this is
-fairly painless because of the conventions assumed by the Java system.
-
- First, 'libgcj' will make sure a class is initialized before an
-instance of that object is created. This is one of the responsibilities
-of the 'new' operation. This is taken care of both in Java code, and in
-C++ code. When G++ sees a 'new' of a Java class, it will call a routine
-in 'libgcj' to allocate the object, and that routine will take care of
-initializing the class. Note however that this does not happen for Java
-arrays; you must allocate those using the appropriate CNI function. It
-follows that you can access an instance field, or call an instance
-(non-static) method and be safe in the knowledge that the class and all
-of its base classes have been initialized.
+ The GCJ compiler inserts calls to `JvInitClass' at appropriate
+places to ensure that a class is initialized when required. The C++
+compiler does not insert these calls automatically--it is the
+programmer's responsibility to make sure classes are initialized.
+However, this is fairly painless because of the conventions assumed by
+the Java system.
+
+ First, `libgcj' will make sure a class is initialized before an
+instance of that object is created. This is one of the
+responsibilities of the `new' operation. This is taken care of both in
+Java code, and in C++ code. When G++ sees a `new' of a Java class, it
+will call a routine in `libgcj' to allocate the object, and that
+routine will take care of initializing the class. Note however that
+this does not happen for Java arrays; you must allocate those using the
+appropriate CNI function. It follows that you can access an instance
+field, or call an instance (non-static) method and be safe in the
+knowledge that the class and all of its base classes have been
+initialized.
Invoking a static method is also safe. This is because the Java
compiler adds code to the start of a static method to make sure the
-class is initialized. However, the C++ compiler does not add this extra
-code. Hence, if you write a native static method using CNI, you are
-responsible for calling 'JvInitClass' before doing anything else in the
-method (unless you are sure it is safe to leave it out).
+class is initialized. However, the C++ compiler does not add this
+extra code. Hence, if you write a native static method using CNI, you
+are responsible for calling `JvInitClass' before doing anything else in
+the method (unless you are sure it is safe to leave it out).
Accessing a static field also requires the class of the field to be
-initialized. The Java compiler will generate code to call 'JvInitClass'
-before getting or setting the field. However, the C++ compiler will not
-generate this extra code, so it is your responsibility to make sure the
-class is initialized before you access a static field from C++.
+initialized. The Java compiler will generate code to call
+`JvInitClass' before getting or setting the field. However, the C++
+compiler will not generate this extra code, so it is your
+responsibility to make sure the class is initialized before you access
+a static field from C++.

File: gcj.info, Node: Object allocation, Next: Memory allocation, Prev: Class Initialization, Up: About CNI
@@ -2629,9 +2660,9 @@ expression", e.g.:
objects have to be explicitly deleted; in Java they are automatically
deleted by the garbage collector. Using CNI, you can allocate a new
Java object using standard C++ syntax and the C++ compiler will allocate
-memory from the garbage collector. If you have overloaded constructors,
-the compiler will choose the correct one using standard C++ overload
-resolution rules.
+memory from the garbage collector. If you have overloaded
+constructors, the compiler will choose the correct one using standard
+C++ overload resolution rules.
For example:
@@ -2643,17 +2674,17 @@ File: gcj.info, Node: Memory allocation, Next: Arrays, Prev: Object allocatio
11.9 Memory allocation
======================
-When allocating memory in CNI methods it is best to handle out-of-memory
-conditions by throwing a Java exception. These functions are provided
-for that purpose:
+When allocating memory in CNI methods it is best to handle
+out-of-memory conditions by throwing a Java exception. These functions
+are provided for that purpose:
-- Function: void* JvMalloc (jsize SIZE)
- Calls malloc. Throws 'java.lang.OutOfMemoryError' if allocation
+ Calls malloc. Throws `java.lang.OutOfMemoryError' if allocation
fails.
-- Function: void* JvRealloc (void* PTR, jsize SIZE)
- Calls realloc. Throws 'java.lang.OutOfMemoryError' if reallocation
- fails.
+ Calls realloc. Throws `java.lang.OutOfMemoryError' if
+ reallocation fails.
-- Function: void JvFree (void* PTR)
Calls free.
@@ -2668,10 +2699,10 @@ While in many ways Java is similar to C and C++, it is quite different
in its treatment of arrays. C arrays are based on the idea of pointer
arithmetic, which would be incompatible with Java's security
requirements. Java arrays are true objects (array types inherit from
-'java.lang.Object'). An array-valued variable is one that contains a
+`java.lang.Object'). An array-valued variable is one that contains a
reference (pointer) to an array object.
- Referencing a Java array in C++ code is done using the 'JArray'
+ Referencing a Java array in C++ code is done using the `JArray'
template, which as defined as follows:
class __JArray : public java::lang::Object
@@ -2688,7 +2719,7 @@ template, which as defined as follows:
T& operator[](jint i) { return data[i]; }
};
- There are a number of 'typedef's which correspond to 'typedef's from
+ There are a number of `typedef's which correspond to `typedef's from
the JNI. Each is the type of an array holding objects of the relevant
type:
@@ -2704,19 +2735,19 @@ type:
typedef JArray<jdouble> *jdoubleArray;
-- Method on template<class T>: T* elements (JArray<T> ARRAY)
- This template function can be used to get a pointer to the elements
- of the 'array'. For instance, you can fetch a pointer to the
- integers that make up an 'int[]' like so:
+ This template function can be used to get a pointer to the
+ elements of the `array'. For instance, you can fetch a pointer to
+ the integers that make up an `int[]' like so:
extern jintArray foo;
jint *intp = elements (foo);
The name of this function may change in the future.
- -- Function: jobjectArray JvNewObjectArray (jsize LENGTH, jclass KLASS,
- jobject INIT)
+ -- Function: jobjectArray JvNewObjectArray (jsize LENGTH, jclass
+ KLASS, jobject INIT)
This creates a new array whose elements have reference type.
- 'klass' is the type of elements of the array and 'init' is the
+ `klass' is the type of elements of the array and `init' is the
initial value put into every slot in the array.
using namespace java::lang;
@@ -2753,9 +2784,10 @@ File: gcj.info, Node: Methods, Next: Strings, Prev: Arrays, Up: About CNI
=============
Java methods are mapped directly into C++ methods. The header files
-generated by 'gcjh' include the appropriate method definitions.
-Basically, the generated methods have the same names and _corresponding_
-types as the Java methods, and are called in the natural manner.
+generated by `gcjh' include the appropriate method definitions.
+Basically, the generated methods have the same names and
+_corresponding_ types as the Java methods, and are called in the
+natural manner.
11.11.1 Overloading
-------------------
@@ -2764,12 +2796,12 @@ Both Java and C++ provide method overloading, where multiple methods in
a class have the same name, and the correct one is chosen (at compile
time) depending on the argument types. The rules for choosing the
correct method are (as expected) more complicated in C++ than in Java,
-but given a set of overloaded methods generated by 'gcjh' the C++
+but given a set of overloaded methods generated by `gcjh' the C++
compiler will choose the expected one.
Common assemblers and linkers are not aware of C++ overloading, so
-the standard implementation strategy is to encode the parameter types of
-a method into its assembly-level name. This encoding is called
+the standard implementation strategy is to encode the parameter types
+of a method into its assembly-level name. This encoding is called
"mangling", and the encoded name is the "mangled name". The same
mechanism is used to implement Java overloading. For C++/Java
interoperability, it is important that both the Java and C++ compilers
@@ -2779,7 +2811,7 @@ use the _same_ encoding scheme.
----------------------
Static Java methods are invoked in CNI using the standard C++ syntax,
-using the '::' operator rather than the '.' operator.
+using the `::' operator rather than the `.' operator.
For example:
@@ -2799,15 +2831,15 @@ For example:
---------------------------
Constructors are called implicitly as part of object allocation using
-the 'new' operator.
+the `new' operator.
For example:
java::lang::Integer *x = new java::lang::Integer(234);
Java does not allow a constructor to be a native method. This
-limitation can be coded round however because a constructor can _call_ a
-native method.
+limitation can be coded round however because a constructor can _call_
+a native method.
11.11.4 Instance methods
------------------------
@@ -2845,35 +2877,35 @@ File: gcj.info, Node: Strings, Next: Mixing with C++, Prev: Methods, Up: Abo
=============
CNI provides a number of utility functions for working with Java Java
-'String' objects. The names and interfaces are analogous to those of
+`String' objects. The names and interfaces are analogous to those of
JNI.
-- Function: jstring JvNewString (const jchar* CHARS, jsize LEN)
- Returns a Java 'String' object with characters from the array of
+ Returns a Java `String' object with characters from the array of
Unicode characters CHARS up to the index LEN in that array.
-- Function: jstring JvNewStringLatin1 (const char* BYTES, jsize LEN)
- Returns a Java 'String' made up of LEN bytes from BYTES.
+ Returns a Java `String' made up of LEN bytes from BYTES.
-- Function: jstring JvNewStringLatin1 (const char* BYTES)
- As above but the length of the 'String' is 'strlen(BYTES)'.
+ As above but the length of the `String' is `strlen(BYTES)'.
-- Function: jstring JvNewStringUTF (const char* BYTES)
- Returns a 'String' which is made up of the UTF encoded characters
+ Returns a `String' which is made up of the UTF encoded characters
present in the C string BYTES.
-- Function: jchar* JvGetStringChars (jstring STR)
- Returns a pointer to an array of characters making up the 'String'
+ Returns a pointer to an array of characters making up the `String'
STR.
-- Function: int JvGetStringUTFLength (jstring STR)
Returns the number of bytes required to encode the contents of the
- 'String' STR in UTF-8.
+ `String' STR in UTF-8.
-- Function: jsize JvGetStringUTFRegion (jstring STR, jsize START,
jsize LEN, char* BUF)
- Puts the UTF-8 encoding of a region of the 'String' STR into the
- buffer 'buf'. The region to fetch is marked by START and LEN.
+ Puts the UTF-8 encoding of a region of the `String' STR into the
+ buffer `buf'. The region to fetch is marked by START and LEN.
Note that BUF is a buffer, not a C string. It is _not_ null
terminated.
@@ -2906,7 +2938,7 @@ None of the following is possible with CNI:
.
.
.
- } // 'uint' is not a valid Java type, neither is 'char*'
+ } // `uint' is not a valid Java type, neither is `char*'
Of course, it is ok to use C/C++ types within the scope of a method:
@@ -2923,8 +2955,8 @@ Of course, it is ok to use C/C++ types within the scope of a method:
---------------
The above restriction can be problematic, so CNI includes the
-'gnu.gcj.RawData' class. The 'RawData' class is a "non-scanned
-reference" type. In other words variables declared of type 'RawData'
+`gnu.gcj.RawData' class. The `RawData' class is a "non-scanned
+reference" type. In other words variables declared of type `RawData'
can contain any data and are not checked by the compiler or memory
manager in any way.
@@ -2964,13 +2996,13 @@ Here are some examples:
11.13.2 RawDataManaged
----------------------
-'gnu.gcj.RawDataManaged' is another type used to indicate special data
-used by native code. Unlike the 'RawData' type, fields declared as
-'RawDataManaged' will be "marked" by the memory manager and considered
+`gnu.gcj.RawDataManaged' is another type used to indicate special data
+used by native code. Unlike the `RawData' type, fields declared as
+`RawDataManaged' will be "marked" by the memory manager and considered
for garbage collection.
- Native data which is allocated using CNI's 'JvAllocBytes()' function
-and stored in a 'RawDataManaged' will be automatically freed when the
+ Native data which is allocated using CNI's `JvAllocBytes()' function
+and stored in a `RawDataManaged' will be automatically freed when the
Java object it is associated with becomes unreachable.
11.13.3 Native memory allocation
@@ -2982,22 +3014,22 @@ Java object it is associated with becomes unreachable.
but will be freed if no references to it are discovered.
This function can be useful if you need to associate some native
- data with a Java object. Using a CNI's special 'RawDataManaged'
- type, native data allocated with 'JvAllocBytes' will be
+ data with a Java object. Using a CNI's special `RawDataManaged'
+ type, native data allocated with `JvAllocBytes' will be
automatically freed when the Java object itself becomes
unreachable.
11.13.4 Posix signals
---------------------
-On Posix based systems the 'libgcj' library uses several signals
+On Posix based systems the `libgcj' library uses several signals
internally. CNI code should not attempt to use the same signals as
-doing so may cause 'libgcj' and/or the CNI code to fail.
+doing so may cause `libgcj' and/or the CNI code to fail.
- SIGSEGV is used on many systems to generate 'NullPointerExceptions'.
-SIGCHLD is used internally by 'Runtime.exec()'. Several other signals
+ SIGSEGV is used on many systems to generate `NullPointerExceptions'.
+SIGCHLD is used internally by `Runtime.exec()'. Several other signals
(that vary from platform to platform) can be used by the memory manager
-and by 'Thread.interrupt()'.
+and by `Thread.interrupt()'.

File: gcj.info, Node: Exception Handling, Next: Synchronization, Prev: Mixing with C++, Up: About CNI
@@ -3010,19 +3042,20 @@ are not yet perfectly integrated. The main issue is that the run-time
type information facilities of the two languages are not integrated.
Still, things work fairly well. You can throw a Java exception from
-C++ using the ordinary 'throw' construct, and this exception can be
+C++ using the ordinary `throw' construct, and this exception can be
caught by Java code. Similarly, you can catch an exception thrown from
-Java using the C++ 'catch' construct.
+Java using the C++ `catch' construct.
Here is an example:
if (i >= count)
throw new java::lang::IndexOutOfBoundsException();
- Normally, G++ will automatically detect when you are writing C++ code
-that uses Java exceptions, and handle them appropriately. However, if
-C++ code only needs to execute destructors when Java exceptions are
-thrown through it, GCC will guess incorrectly. Sample problematic code:
+ Normally, G++ will automatically detect when you are writing C++
+code that uses Java exceptions, and handle them appropriately.
+However, if C++ code only needs to execute destructors when Java
+exceptions are thrown through it, GCC will guess incorrectly. Sample
+problematic code:
struct S { ~S(); };
@@ -3034,12 +3067,12 @@ thrown through it, GCC will guess incorrectly. Sample problematic code:
bar();
}
- The usual effect of an incorrect guess is a link failure, complaining
-of a missing routine called '__gxx_personality_v0'.
+ The usual effect of an incorrect guess is a link failure,
+complaining of a missing routine called `__gxx_personality_v0'.
You can inform the compiler that Java exceptions are to be used in a
translation unit, irrespective of what it might think, by writing
-'#pragma GCC java_exceptions' at the head of the file. This '#pragma'
+`#pragma GCC java_exceptions' at the head of the file. This `#pragma'
must appear before any functions that throw or catch exceptions, or run
destructors when exceptions are thrown through them.
@@ -3050,18 +3083,19 @@ File: gcj.info, Node: Synchronization, Next: Invocation, Prev: Exception Hand
=====================
Each Java object has an implicit monitor. The Java VM uses the
-instruction 'monitorenter' to acquire and lock a monitor, and
-'monitorexit' to release it.
+instruction `monitorenter' to acquire and lock a monitor, and
+`monitorexit' to release it.
- The corresponding CNI macros are 'JvMonitorEnter' and 'JvMonitorExit'
-(JNI has similar methods 'MonitorEnter' and 'MonitorExit').
+ The corresponding CNI macros are `JvMonitorEnter' and
+`JvMonitorExit' (JNI has similar methods `MonitorEnter' and
+`MonitorExit').
The Java source language does not provide direct access to these
-primitives. Instead, there is a 'synchronized' statement that does an
-implicit 'monitorenter' before entry to the block, and does a
-'monitorexit' on exit from the block. Note that the lock has to be
+primitives. Instead, there is a `synchronized' statement that does an
+implicit `monitorenter' before entry to the block, and does a
+`monitorexit' on exit from the block. Note that the lock has to be
released even when the block is abnormally terminated by an exception,
-which means there is an implicit 'try finally' surrounding
+which means there is an implicit `try finally' surrounding
synchronization locks.
From C++, it makes sense to use a destructor to release a lock. CNI
@@ -3087,16 +3121,16 @@ might become this C++ code:
CODE;
}
- Java also has methods with the 'synchronized' attribute. This is
-equivalent to wrapping the entire method body in a 'synchronized'
+ Java also has methods with the `synchronized' attribute. This is
+equivalent to wrapping the entire method body in a `synchronized'
statement. (Alternatively, an implementation could require the caller
to do the synchronization. This is not practical for a compiler,
because each virtual method call would have to test at run-time if
-synchronization is needed.) Since in 'gcj' the 'synchronized' attribute
-is handled by the method implementation, it is up to the programmer of a
-synchronized native method to handle the synchronization (in the C++
-implementation of the method). In other words, you need to manually add
-'JvSynchronize' in a 'native synchronized' method.
+synchronization is needed.) Since in `gcj' the `synchronized'
+attribute is handled by the method implementation, it is up to the
+programmer of a synchronized native method to handle the synchronization
+(in the C++ implementation of the method). In other words, you need to
+manually add `JvSynchronize' in a `native synchronized' method.

File: gcj.info, Node: Invocation, Next: Reflection, Prev: Synchronization, Up: About CNI
@@ -3105,23 +3139,22 @@ File: gcj.info, Node: Invocation, Next: Reflection, Prev: Synchronization, U
================
CNI permits C++ applications to make calls into Java classes, in
-addition to allowing Java code to call into C++. Several functions,
+addition to allowing Java code to call into C++. Several functions,
known as the "invocation API", are provided to support this.
-- Function: jint JvCreateJavaVM (JvVMInitArgs* VM_ARGS)
-
- Initializes the Java runtime. This function performs essential
+ Initializes the Java runtime. This function performs essential
initialization of the threads interface, garbage collector,
- exception handling and other key aspects of the runtime. It must
- be called once by an application with a non-Java 'main()' function,
- before any other Java or CNI calls are made. It is safe, but not
- recommended, to call 'JvCreateJavaVM()' more than once provided it
- is only called from a single thread. The VMARGS parameter can be
- used to specify initialization parameters for the Java runtime. It
- may be 'NULL'.
+ exception handling and other key aspects of the runtime. It must
+ be called once by an application with a non-Java `main()'
+ function, before any other Java or CNI calls are made. It is
+ safe, but not recommended, to call `JvCreateJavaVM()' more than
+ once provided it is only called from a single thread. The VMARGS
+ parameter can be used to specify initialization parameters for the
+ Java runtime. It may be `NULL'.
JvVMInitArgs represents a list of virtual machine initialization
- arguments. 'JvCreateJavaVM()' ignores the version field.
+ arguments. `JvCreateJavaVM()' ignores the version field.
typedef struct JvVMOption
{
@@ -3146,40 +3179,40 @@ known as the "invocation API", are provided to support this.
jboolean ignoreUnrecognized;
} JvVMInitArgs;
- 'JvCreateJavaVM()' returns '0' upon success, or '-1' if the runtime
- is already initialized.
+ `JvCreateJavaVM()' returns `0' upon success, or `-1' if the
+ runtime is already initialized.
- _Note:_ In GCJ 3.1, the 'vm_args' parameter is ignored. It is
+ _Note:_ In GCJ 3.1, the `vm_args' parameter is ignored. It is
recognized and used as of release 4.0.
-- Function: java::lang::Thread* JvAttachCurrentThread (jstring NAME,
java::lang::ThreadGroup* GROUP)
Registers an existing thread with the Java runtime. This must be
called once from each thread, before that thread makes any other
- Java or CNI calls. It must be called after 'JvCreateJavaVM'. NAME
- specifies a name for the thread. It may be 'NULL', in which case a
+ Java or CNI calls. It must be called after `JvCreateJavaVM'. NAME
+ specifies a name for the thread. It may be `NULL', in which case a
name will be generated. GROUP is the ThreadGroup in which this
- thread will be a member. If it is 'NULL', the thread will be a
+ thread will be a member. If it is `NULL', the thread will be a
member of the main thread group. The return value is the Java
- 'Thread' object that represents the thread. It is safe to call
- 'JvAttachCurrentThread()' more than once from the same thread. If
+ `Thread' object that represents the thread. It is safe to call
+ `JvAttachCurrentThread()' more than once from the same thread. If
the thread is already attached, the call is ignored and the current
thread object is returned.
-- Function: jint JvDetachCurrentThread ()
- Unregisters a thread from the Java runtime. This should be called
- by threads that were attached using 'JvAttachCurrentThread()',
- after they have finished making calls to Java code. This ensures
+ Unregisters a thread from the Java runtime. This should be called
+ by threads that were attached using `JvAttachCurrentThread()',
+ after they have finished making calls to Java code. This ensures
that any resources associated with the thread become eligible for
- garbage collection. This function returns '0' upon success, or
- '-1' if the current thread is not attached.
+ garbage collection. This function returns `0' upon success, or
+ `-1' if the current thread is not attached.
11.16.1 Handling uncaught exceptions
------------------------------------
If an exception is thrown from Java code called using the invocation
API, and no handler for the exception can be found, the runtime will
-abort the application. In order to make the application more robust, it
+abort the application. In order to make the application more robust, it
is recommended that code which uses the invocation API be wrapped by a
top-level try/catch block that catches all Java exceptions.
@@ -3188,13 +3221,13 @@ top-level try/catch block that catches all Java exceptions.
The following code demonstrates the use of the invocation API. In this
example, the C++ application initializes the Java runtime and attaches
-itself. The 'java.lang.System' class is initialized in order to access
-its 'out' field, and a Java string is printed. Finally, the thread is
+itself. The `java.lang.System' class is initialized in order to access
+its `out' field, and a Java string is printed. Finally, the thread is
detached from the runtime once it has finished making Java calls.
Everything is wrapped with a try/catch block to provide a default
handler for any uncaught exceptions.
- The example can be compiled with 'c++ -c test.cc; gcj test.o'.
+ The example can be compiled with `c++ -c test.cc; gcj test.o'.
// test.cc
#include <gcj/cni.h>
@@ -3233,14 +3266,17 @@ File: gcj.info, Node: Reflection, Prev: Invocation, Up: About CNI
Reflection is possible with CNI code, it functions similarly to how it
functions with JNI.
- The types 'jfieldID' and 'jmethodID' are as in JNI.
+ The types `jfieldID' and `jmethodID' are as in JNI.
The functions:
- * 'JvFromReflectedField',
- * 'JvFromReflectedMethod',
- * 'JvToReflectedField'
- * 'JvToFromReflectedMethod'
+ * `JvFromReflectedField',
+
+ * `JvFromReflectedMethod',
+
+ * `JvToReflectedField'
+
+ * `JvToFromReflectedMethod'
will be added shortly, as will other functions corresponding to JNI.
@@ -3250,20 +3286,20 @@ File: gcj.info, Node: System properties, Next: Resources, Prev: About CNI, U
12 System properties
********************
-The runtime behavior of the 'libgcj' library can be modified by setting
+The runtime behavior of the `libgcj' library can be modified by setting
certain system properties. These properties can be compiled into the
-program using the '-DNAME[=VALUE]' option to 'gcj' or by setting them
+program using the `-DNAME[=VALUE]' option to `gcj' or by setting them
explicitly in the program by calling the
-'java.lang.System.setProperty()' method. Some system properties are
+`java.lang.System.setProperty()' method. Some system properties are
only used for informational purposes (like giving a version number or a
user name). A program can inspect the current value of a property by
-calling the 'java.lang.System.getProperty()' method.
+calling the `java.lang.System.getProperty()' method.
* Menu:
-* Standard Properties:: Standard properties supported by 'libgcj'
+* Standard Properties:: Standard properties supported by `libgcj'
* GNU Classpath Properties:: Properties found in Classpath based libraries
-* libgcj Runtime Properties:: Properties specific to 'libgcj'
+* libgcj Runtime Properties:: Properties specific to `libgcj'

File: gcj.info, Node: Standard Properties, Next: GNU Classpath Properties, Up: System properties
@@ -3274,176 +3310,178 @@ File: gcj.info, Node: Standard Properties, Next: GNU Classpath Properties, Up
The following properties are normally found in all implementations of
the core libraries for the Java language.
-'java.version'
- The 'libgcj' version number.
+`java.version'
+ The `libgcj' version number.
-'java.vendor'
- Set to 'The Free Software Foundation, Inc.'
+`java.vendor'
+ Set to `The Free Software Foundation, Inc.'
-'java.vendor.url'
- Set to <http://gcc.gnu.org/java/>.
+`java.vendor.url'
+ Set to `http://gcc.gnu.org/java/'.
-'java.home'
- The directory where 'gcj' was installed. Taken from the '--prefix'
- option given to 'configure'.
+`java.home'
+ The directory where `gcj' was installed. Taken from the `--prefix'
+ option given to `configure'.
-'java.class.version'
+`java.class.version'
The class format version number supported by the libgcj byte code
- interpreter. (Currently '46.0')
+ interpreter. (Currently `46.0')
-'java.vm.specification.version'
- The Virtual Machine Specification version implemented by 'libgcj'.
- (Currently '1.0')
+`java.vm.specification.version'
+ The Virtual Machine Specification version implemented by `libgcj'.
+ (Currently `1.0')
-'java.vm.specification.vendor'
+`java.vm.specification.vendor'
The name of the Virtual Machine specification designer.
-'java.vm.specification.name'
- The name of the Virtual Machine specification (Set to 'Java Virtual
- Machine Specification').
+`java.vm.specification.name'
+ The name of the Virtual Machine specification (Set to `Java
+ Virtual Machine Specification').
-'java.vm.version'
- The 'gcj' version number.
+`java.vm.version'
+ The `gcj' version number.
-'java.vm.vendor'
- Set to 'The Free Software Foundation, Inc.'
+`java.vm.vendor'
+ Set to `The Free Software Foundation, Inc.'
-'java.vm.name'
- Set to 'GNU libgcj'.
+`java.vm.name'
+ Set to `GNU libgcj'.
-'java.specification.version'
+`java.specification.version'
The Runtime Environment specification version implemented by
- 'libgcj'. (Currently set to '1.3')
+ `libgcj'. (Currently set to `1.3')
-'java.specification.vendor'
+`java.specification.vendor'
The Runtime Environment specification designer.
-'java.specification.name'
- The name of the Runtime Environment specification (Set to 'Java
+`java.specification.name'
+ The name of the Runtime Environment specification (Set to `Java
Platform API Specification').
-'java.class.path'
+`java.class.path'
The paths (jar files, zip files and directories) used for finding
class files.
-'java.library.path'
+`java.library.path'
Directory path used for finding native libraries.
-'java.io.tmpdir'
+`java.io.tmpdir'
The directory used to put temporary files in.
-'java.compiler'
+`java.compiler'
Name of the Just In Time compiler to use by the byte code
- interpreter. Currently not used in 'libgcj'.
+ interpreter. Currently not used in `libgcj'.
-'java.ext.dirs'
+`java.ext.dirs'
Directories containing jar files with extra libraries. Will be
used when resolving classes.
-'java.protocol.handler.pkgs'
- A '|' separated list of package names that is used to find classes
- that implement handlers for 'java.net.URL'.
+`java.protocol.handler.pkgs'
+ A `|' separated list of package names that is used to find classes
+ that implement handlers for `java.net.URL'.
-'java.rmi.server.codebase'
- A list of URLs that is used by the 'java.rmi.server.RMIClassLoader'
+`java.rmi.server.codebase'
+ A list of URLs that is used by the `java.rmi.server.RMIClassLoader'
to load classes from.
-'jdbc.drivers'
+`jdbc.drivers'
A list of class names that will be loaded by the
- 'java.sql.DriverManager' when it starts up.
+ `java.sql.DriverManager' when it starts up.
-'file.separator'
+`file.separator'
The separator used in when directories are included in a filename
- (normally '/' or '\' ).
+ (normally `/' or `\' ).
-'file.encoding'
- The default character encoding used when converting platform native
- files to Unicode (usually set to '8859_1').
+`file.encoding'
+ The default character encoding used when converting platform
+ native files to Unicode (usually set to `8859_1').
-'path.separator'
+`path.separator'
The standard separator used when a string contains multiple paths
- (normally ':' or ';'), the string is usually not a valid character
+ (normally `:' or `;'), the string is usually not a valid character
to use in normal directory names.)
-'line.separator'
- The default line separator used on the platform (normally '\n',
- '\r' or a combination of those two characters).
+`line.separator'
+ The default line separator used on the platform (normally `\n',
+ `\r' or a combination of those two characters).
-'policy.provider'
+`policy.provider'
The class name used for the default policy provider returned by
- 'java.security.Policy.getPolicy'.
+ `java.security.Policy.getPolicy'.
-'user.name'
+`user.name'
The name of the user running the program. Can be the full name,
the login name or empty if unknown.
-'user.home'
+`user.home'
The default directory to put user specific files in.
-'user.dir'
+`user.dir'
The current working directory from which the program was started.
-'user.language'
- The default language as used by the 'java.util.Locale' class.
+`user.language'
+ The default language as used by the `java.util.Locale' class.
-'user.region'
- The default region as used by the 'java.util.Local' class.
+`user.region'
+ The default region as used by the `java.util.Local' class.
-'user.variant'
+`user.variant'
The default variant of the language and region local used.
-'user.timezone'
- The default timezone as used by the 'java.util.TimeZone' class.
+`user.timezone'
+ The default timezone as used by the `java.util.TimeZone' class.
-'os.name'
+`os.name'
The operating system/kernel name that the program runs on.
-'os.arch'
+`os.arch'
The hardware that we are running on.
-'os.version'
+`os.version'
The version number of the operating system/kernel.
-'awt.appletWarning'
+`awt.appletWarning'
The string to display when an untrusted applet is displayed.
- Returned by 'java.awt.Window.getWarningString()' when the window is
+ Returned by `java.awt.Window.getWarningString()' when the window is
"insecure".
-'awt.toolkit'
+`awt.toolkit'
The class name used for initializing the default
- 'java.awt.Toolkit'. Defaults to 'gnu.awt.gtk.GtkToolkit'.
+ `java.awt.Toolkit'. Defaults to `gnu.awt.gtk.GtkToolkit'.
-'http.proxyHost'
+`http.proxyHost'
Name of proxy host for http connections.
-'http.proxyPort'
+`http.proxyPort'
Port number to use when a proxy host is in use.
+

File: gcj.info, Node: GNU Classpath Properties, Next: libgcj Runtime Properties, Prev: Standard Properties, Up: System properties
12.2 GNU Classpath Properties
=============================
-'libgcj' is based on the GNU Classpath (Essential Libraries for Java) a
+`libgcj' is based on the GNU Classpath (Essential Libraries for Java) a
GNU project to create free core class libraries for use with virtual
machines and compilers for the Java language. The following properties
are common to libraries based on GNU Classpath.
-'gcj.dumpobject'
+`gcj.dumpobject'
Enables printing serialization debugging by the
- 'java.io.ObjectInput' and 'java.io.ObjectOutput' classes when set
+ `java.io.ObjectInput' and `java.io.ObjectOutput' classes when set
to something else then the empty string. Only used when running a
debug build of the library.
-'gnu.classpath.vm.shortname'
- This is a succinct name of the virtual machine. For 'libgcj', this
- will always be 'libgcj'.
+`gnu.classpath.vm.shortname'
+ This is a succinct name of the virtual machine. For `libgcj',
+ this will always be `libgcj'.
-'gnu.classpath.home.url'
+`gnu.classpath.home.url'
A base URL used for finding system property files (e.g.,
- 'classpath.security'). By default this is a 'file:' URL pointing
- to the 'lib' directory under 'java.home'.
+ `classpath.security'). By default this is a `file:' URL pointing
+ to the `lib' directory under `java.home'.
+

File: gcj.info, Node: libgcj Runtime Properties, Prev: GNU Classpath Properties, Up: System properties
@@ -3451,96 +3489,97 @@ File: gcj.info, Node: libgcj Runtime Properties, Prev: GNU Classpath Propertie
12.3 libgcj Runtime Properties
==============================
-The following properties are specific to the 'libgcj' runtime and will
+The following properties are specific to the `libgcj' runtime and will
normally not be found in other core libraries for the java language.
-'java.fullversion'
- The combination of 'java.vm.name' and 'java.vm.version'.
+`java.fullversion'
+ The combination of `java.vm.name' and `java.vm.version'.
-'java.vm.info'
- Same as 'java.fullversion'.
+`java.vm.info'
+ Same as `java.fullversion'.
-'impl.prefix'
- Used by the 'java.net.DatagramSocket' class when set to something
+`impl.prefix'
+ Used by the `java.net.DatagramSocket' class when set to something
else then the empty string. When set all newly created
- 'DatagramSocket's will try to load a class
- 'java.net.[impl.prefix]DatagramSocketImpl' instead of the normal
- 'java.net.PlainDatagramSocketImpl'.
+ `DatagramSocket's will try to load a class
+ `java.net.[impl.prefix]DatagramSocketImpl' instead of the normal
+ `java.net.PlainDatagramSocketImpl'.
-'gnu.gcj.progname'
- The class or binary name that was used to invoke the program. This
- will be the name of the "main" class in the case where the 'gij'
+`gnu.gcj.progname'
+ The class or binary name that was used to invoke the program. This
+ will be the name of the "main" class in the case where the `gij'
front end is used, or the program binary name in the case where an
application is compiled to a native binary.
-'gnu.gcj.user.realname'
+`gnu.gcj.user.realname'
The real name of the user, as taken from the password file. This
may not always hold only the user's name (as some sites put extra
information in this field). Also, this property is not available
on all platforms.
-'gnu.gcj.runtime.NameFinder.use_addr2line'
- Whether an external process, 'addr2line', should be used to
- determine line number information when tracing the stack. Setting
- this to 'false' may suppress line numbers when printing stack
+`gnu.gcj.runtime.NameFinder.use_addr2line'
+ Whether an external process, `addr2line', should be used to
+ determine line number information when tracing the stack. Setting
+ this to `false' may suppress line numbers when printing stack
traces and when using the java.util.logging infrastructure.
However, performance may improve significantly for applications
that print stack traces or make logging calls frequently.
-'gnu.gcj.runtime.NameFinder.show_raw'
+`gnu.gcj.runtime.NameFinder.show_raw'
Whether the address of a stack frame should be printed when the
- line number is unavailable. Setting this to 'true' will cause the
+ line number is unavailable. Setting this to `true' will cause the
name of the object and the offset within that object to be printed
when no line number is available. This allows for off-line
decoding of stack traces if necessary debug information is
- available. The default is 'false', no raw addresses are printed.
+ available. The default is `false', no raw addresses are printed.
-'gnu.gcj.runtime.NameFinder.remove_unknown'
+`gnu.gcj.runtime.NameFinder.remove_unknown'
Whether stack frames for non-java code should be included in a
- stack trace. The default value is 'true', stack frames for
- non-java code are suppressed. Setting this to 'false' will cause
+ stack trace. The default value is `true', stack frames for
+ non-java code are suppressed. Setting this to `false' will cause
any non-java stack frames to be printed in addition to frames for
the java code.
-'gnu.gcj.runtime.VMClassLoader.library_control'
+`gnu.gcj.runtime.VMClassLoader.library_control'
This controls how shared libraries are automatically loaded by the
- built-in class loader. If this property is set to 'full', a full
+ built-in class loader. If this property is set to `full', a full
search is done for each requested class. If this property is set
- to 'cache', then any failed lookups are cached and not tried again.
- If this property is set to 'never' (the default), then lookups are
+ to `cache', then any failed lookups are cached and not tried again.
+ If this property is set to `never' (the default), then lookups are
never done. For more information, *Note Extensions::.
-'gnu.gcj.runtime.endorsed.dirs'
- This is like the standard 'java.endorsed.dirs', property, but
+`gnu.gcj.runtime.endorsed.dirs'
+ This is like the standard `java.endorsed.dirs', property, but
specifies some extra directories which are searched after the
standard endorsed directories. This is primarily useful for
- telling 'libgcj' about additional libraries which are ordinarily
+ telling `libgcj' about additional libraries which are ordinarily
incorporated into the JDK, and which should be loaded by the
- bootstrap class loader, but which are not yet part of 'libgcj'
+ bootstrap class loader, but which are not yet part of `libgcj'
itself for some reason.
-'gnu.gcj.jit.compiler'
- This is the full path to 'gcj' executable which should be used to
- compile classes just-in-time when 'ClassLoader.defineClass' is
- called. If not set, 'gcj' will not be invoked by the runtime; this
- can also be controlled via 'Compiler.disable'.
+`gnu.gcj.jit.compiler'
+ This is the full path to `gcj' executable which should be used to
+ compile classes just-in-time when `ClassLoader.defineClass' is
+ called. If not set, `gcj' will not be invoked by the runtime;
+ this can also be controlled via `Compiler.disable'.
-'gnu.gcj.jit.options'
+`gnu.gcj.jit.options'
This is a space-separated string of options which should be passed
- to 'gcj' when in JIT mode. If not set, a sensible default is
+ to `gcj' when in JIT mode. If not set, a sensible default is
chosen.
-'gnu.gcj.jit.cachedir'
- This is the directory where cached shared library files are stored.
- If not set, JIT compilation is disabled. This should never be set
- to a directory that is writable by any other user.
+`gnu.gcj.jit.cachedir'
+ This is the directory where cached shared library files are
+ stored. If not set, JIT compilation is disabled. This should
+ never be set to a directory that is writable by any other user.
-'gnu.gcj.precompiled.db.path'
+`gnu.gcj.precompiled.db.path'
This is a sequence of file names, each referring to a file created
- by 'gcj-dbtool'. These files will be used by 'libgcj' to find
+ by `gcj-dbtool'. These files will be used by `libgcj' to find
shared libraries corresponding to classes that are loaded from
- bytecode. 'libgcj' often has a built-in default database; it can
- be queried using 'gcj-dbtool -p'.
+ bytecode. `libgcj' often has a built-in default database; it can
+ be queried using `gcj-dbtool -p'.
+

File: gcj.info, Node: Resources, Next: Index, Prev: System properties, Up: Top
@@ -3548,20 +3587,20 @@ File: gcj.info, Node: Resources, Next: Index, Prev: System properties, Up: T
13 Resources
************
-While writing 'gcj' and 'libgcj' we have, of course, relied heavily on
+While writing `gcj' and `libgcj' we have, of course, relied heavily on
documentation from Sun Microsystems. In particular we have used The
Java Language Specification (both first and second editions), the Java
Class Libraries (volumes one and two), and the Java Virtual Machine
Specification. In addition we've used Sun's online documentation.
- The current 'gcj' home page is <http://gcc.gnu.org/java/>.
+ The current `gcj' home page is `http://gcc.gnu.org/java/'.
- For more information on GCC, see <http://gcc.gnu.org/>.
+ For more information on GCC, see `http://gcc.gnu.org/'.
- Some 'libgcj' testing is done using the Mauve test suite. This is a
+ Some `libgcj' testing is done using the Mauve test suite. This is a
free software Java class library test suite which is being written
-because the JCK is not free. See <http://www.sourceware.org/mauve/> for
-more information.
+because the JCK is not free. See `http://www.sourceware.org/mauve/'
+for more information.

File: gcj.info, Node: Index, Prev: Resources, Up: Top
@@ -3574,81 +3613,79 @@ Index
* class path: Input Options. (line 6)
* class$: Reference types. (line 20)
-* elements on template<class T>: Arrays. (line 45)
+* elements on template<class T>: Arrays. (line 46)
* FDL, GNU Free Documentation License: GNU Free Documentation License.
(line 6)
* GCJ_PROPERTIES: Extensions. (line 56)
-* GCJ_PROPERTIES <1>: Extensions. (line 56)
* jclass: Reference types. (line 16)
* jobject: Reference types. (line 16)
* jstring: Reference types. (line 16)
-* JvAllocBytes: Mixing with C++. (line 98)
-* JvAttachCurrentThread: Invocation. (line 54)
-* JvCreateJavaVM: Invocation. (line 10)
+* JvAllocBytes: Mixing with C++. (line 99)
+* JvAttachCurrentThread: Invocation. (line 55)
+* JvCreateJavaVM: Invocation. (line 11)
* JvDetachCurrentThread: Invocation. (line 68)
-* JvFree: Memory allocation. (line 18)
-* JvGetArrayLength: Arrays. (line 85)
-* JvGetStringChars: Strings. (line 24)
-* JvGetStringUTFLength: Strings. (line 28)
-* JvGetStringUTFRegion: Strings. (line 32)
-* JvMalloc: Memory allocation. (line 10)
-* JvNewBooleanArray: Arrays. (line 82)
-* JvNewObjectArray: Arrays. (line 55)
-* JvNewString: Strings. (line 10)
-* JvNewStringLatin1: Strings. (line 14)
-* JvNewStringLatin1 <1>: Strings. (line 17)
-* JvNewStringUTF: Strings. (line 20)
-* JvPrimClass: Primitive types. (line 35)
-* JvRealloc: Memory allocation. (line 14)
+* JvFree: Memory allocation. (line 19)
+* JvGetArrayLength: Arrays. (line 86)
+* JvGetStringChars: Strings. (line 25)
+* JvGetStringUTFLength: Strings. (line 29)
+* JvGetStringUTFRegion: Strings. (line 34)
+* JvMalloc: Memory allocation. (line 11)
+* JvNewBooleanArray: Arrays. (line 83)
+* JvNewObjectArray: Arrays. (line 57)
+* JvNewString: Strings. (line 11)
+* JvNewStringLatin1: Strings. (line 15)
+* JvNewStringUTF: Strings. (line 21)
+* JvPrimClass: Primitive types. (line 36)
+* JvRealloc: Memory allocation. (line 15)

Tag Table:
-Node: Top2679
-Node: Copying4098
-Node: GNU Free Documentation License41630
-Node: Invoking gcj66754
-Node: Input and output files67517
-Node: Input Options69039
-Node: Encodings72314
-Node: Warnings73520
-Node: Linking74633
-Node: Code Generation77566
-Node: Configure-time Options84342
-Node: Compatibility86082
-Node: Limitations86601
-Node: Extensions88179
-Node: Invoking jcf-dump91270
-Node: Invoking gij92215
-Node: Invoking gcj-dbtool95471
-Node: Invoking jv-convert97932
-Node: Invoking grmic99011
-Node: Invoking gc-analyze100397
-Node: Invoking aot-compile101838
-Node: Invoking rebuild-gcj-db102786
-Node: About CNI103096
-Node: Basic concepts104555
-Node: Packages107451
-Node: Primitive types109779
-Node: Reference types111456
-Node: Interfaces112540
-Node: Objects and Classes113451
-Node: Class Initialization115646
-Node: Object allocation117989
-Node: Memory allocation118779
-Node: Arrays119411
-Node: Methods122221
-Node: Strings125042
-Node: Mixing with C++126546
-Node: Exception Handling130019
-Node: Synchronization131654
-Node: Invocation133643
-Node: Reflection138595
-Node: System properties139053
-Node: Standard Properties139930
-Node: GNU Classpath Properties144361
-Node: libgcj Runtime Properties145407
-Node: Resources149910
-Node: Index150724
+Node: Top2729
+Node: Copying4148
+Node: GNU Free Documentation License41698
+Node: Invoking gcj66841
+Node: Input and output files67604
+Node: Input Options69130
+Node: Encodings72404
+Node: Warnings73610
+Node: Linking74723
+Node: Code Generation77662
+Node: Configure-time Options84442
+Node: Compatibility86182
+Node: Limitations86666
+Node: Extensions88248
+Node: Invoking jcf-dump91342
+Node: Invoking gij92287
+Node: Invoking gcj-dbtool95538
+Node: Invoking jv-convert98004
+Node: Invoking grmic99083
+Node: Invoking gc-analyze100469
+Node: Invoking aot-compile101910
+Node: Invoking rebuild-gcj-db102859
+Node: About CNI103169
+Node: Basic concepts104628
+Node: Packages107524
+Node: Primitive types109852
+Node: Reference types111530
+Node: Interfaces112619
+Node: Objects and Classes113530
+Node: Class Initialization115725
+Node: Object allocation118067
+Node: Memory allocation118857
+Node: Arrays119489
+Node: Methods122299
+Node: Strings125120
+Node: Mixing with C++126624
+Node: Exception Handling130095
+Node: Synchronization131729
+Node: Invocation133719
+Node: Reflection138655
+Node: System properties139116
+Node: Standard Properties139993
+Node: GNU Classpath Properties144425
+Node: libgcj Runtime Properties145472
+Node: Resources149974
+Node: Index150788

End Tag Table
diff --git a/gcc/doc/gcov-tool.1 b/gcc/doc/gcov-tool.1
index 4671b6f718..4e914b4c8a 100644
--- a/gcc/doc/gcov-tool.1
+++ b/gcc/doc/gcov-tool.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCOV-TOOL 1"
-.TH GCOV-TOOL 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCOV-TOOL 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/gcov.1 b/gcc/doc/gcov.1
index 143004eb96..01872fd99b 100644
--- a/gcc/doc/gcov.1
+++ b/gcc/doc/gcov.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GCOV 1"
-.TH GCOV 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GCOV 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -210,7 +209,7 @@ in fine-tuning the performance of your programs. \fBgprof\fR gives
timing information you can use along with the information you get from
\&\fBgcov\fR.
.PP
-\&\fBgcov\fR works only on code compiled with \s-1GCC. \s0 It is not
+\&\fBgcov\fR works only on code compiled with \s-1GCC\s0. It is not
compatible with any other profiling or test coverage mechanism.
.SH "OPTIONS"
.IX Header "OPTIONS"
@@ -640,7 +639,7 @@ profiling code first attempts to read in an existing \fI.gcda\fR file; if
the file doesn't match the executable (differing number of basic block
counts) it will ignore the contents of the file. It then adds in the
new execution counts and finally writes the data to the file.
-.SS "Using \fBgcov\fP with \s-1GCC\s0 Optimization"
+.Sh "Using \fBgcov\fP with \s-1GCC\s0 Optimization"
.IX Subsection "Using gcov with GCC Optimization"
If you plan to use \fBgcov\fR to help optimize your code, you must
first compile your program with two special \s-1GCC\s0 options:
diff --git a/gcc/doc/gfdl.7 b/gcc/doc/gfdl.7
index 81fa3b7232..343891362f 100644
--- a/gcc/doc/gfdl.7
+++ b/gcc/doc/gfdl.7
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GFDL 7"
-.TH GFDL 7 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GFDL 7 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -142,9 +141,9 @@
gfdl \- GNU Free Documentation License
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-.SS "\s-1GNU\s0 Free Documentation License"
+.Sh "\s-1GNU\s0 Free Documentation License"
.IX Subsection "GNU Free Documentation License"
-.SS "Version 1.3, 3 November 2008"
+.Sh "Version 1.3, 3 November 2008"
.IX Subsection "Version 1.3, 3 November 2008"
.Vb 2
\& Copyright (c) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
@@ -179,7 +178,7 @@ whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
.IP "1." 4
.IX Item "1."
-\&\s-1APPLICABILITY AND DEFINITIONS\s0
+\&\s-1APPLICABILITY\s0 \s-1AND\s0 \s-1DEFINITIONS\s0
.Sp
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
@@ -235,13 +234,13 @@ of text. A copy that is not \*(L"Transparent\*(R" is called \*(L"Opaque\*(R".
Examples of suitable formats for Transparent copies include plain
\&\s-1ASCII\s0 without markup, Texinfo input format, LaTeX input
format, \s-1SGML\s0 or \s-1XML\s0 using a publicly available
-\&\s-1DTD,\s0 and standard-conforming simple \s-1HTML,\s0
+\&\s-1DTD\s0, and standard-conforming simple \s-1HTML\s0,
PostScript or \s-1PDF\s0 designed for human modification. Examples
-of transparent image formats include \s-1PNG, XCF\s0 and
-\&\s-1JPG. \s0 Opaque formats include proprietary formats that can be
+of transparent image formats include \s-1PNG\s0, \s-1XCF\s0 and
+\&\s-1JPG\s0. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, \s-1SGML\s0 or
\&\s-1XML\s0 for which the \s-1DTD\s0 and/or processing tools are
-not generally available, and the machine-generated \s-1HTML,\s0
+not generally available, and the machine-generated \s-1HTML\s0,
PostScript or \s-1PDF\s0 produced by some word processors for
output purposes only.
.Sp
@@ -255,13 +254,13 @@ preceding the beginning of the body of the text.
The \*(L"publisher\*(R" means any person or entity that distributes copies
of the Document to the public.
.Sp
-A section \*(L"Entitled \s-1XYZ\*(R"\s0 means a named subunit of the Document whose
+A section \*(L"Entitled \s-1XYZ\s0\*(R" means a named subunit of the Document whose
title either is precisely \s-1XYZ\s0 or contains \s-1XYZ\s0 in parentheses following
text that translates \s-1XYZ\s0 in another language. (Here \s-1XYZ\s0 stands for a
specific section name mentioned below, such as \*(L"Acknowledgements\*(R",
\&\*(L"Dedications\*(R", \*(L"Endorsements\*(R", or \*(L"History\*(R".) To \*(L"Preserve the Title\*(R"
of such a section when you modify the Document means that it remains a
-section \*(L"Entitled \s-1XYZ\*(R"\s0 according to this definition.
+section \*(L"Entitled \s-1XYZ\s0\*(R" according to this definition.
.Sp
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
@@ -271,7 +270,7 @@ implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
.IP "2." 4
.IX Item "2."
-\&\s-1VERBATIM COPYING\s0
+\&\s-1VERBATIM\s0 \s-1COPYING\s0
.Sp
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
@@ -287,7 +286,7 @@ You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
.IP "3." 4
.IX Item "3."
-\&\s-1COPYING IN QUANTITY\s0
+\&\s-1COPYING\s0 \s-1IN\s0 \s-1QUANTITY\s0
.Sp
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
@@ -443,7 +442,7 @@ imply endorsement of any Modified Version.
.RE
.IP "5." 4
.IX Item "5."
-\&\s-1COMBINING DOCUMENTS\s0
+\&\s-1COMBINING\s0 \s-1DOCUMENTS\s0
.Sp
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
@@ -468,7 +467,7 @@ and any sections Entitled \*(L"Dedications\*(R". You must delete all
sections Entitled \*(L"Endorsements.\*(R"
.IP "6." 4
.IX Item "6."
-\&\s-1COLLECTIONS OF DOCUMENTS\s0
+\&\s-1COLLECTIONS\s0 \s-1OF\s0 \s-1DOCUMENTS\s0
.Sp
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
@@ -482,7 +481,7 @@ License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
.IP "7." 4
.IX Item "7."
-\&\s-1AGGREGATION WITH INDEPENDENT WORKS\s0
+\&\s-1AGGREGATION\s0 \s-1WITH\s0 \s-1INDEPENDENT\s0 \s-1WORKS\s0
.Sp
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
@@ -551,7 +550,7 @@ reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
.IP "10." 4
.IX Item "10."
-\&\s-1FUTURE REVISIONS OF THIS LICENSE\s0
+\&\s-1FUTURE\s0 \s-1REVISIONS\s0 \s-1OF\s0 \s-1THIS\s0 \s-1LICENSE\s0
.Sp
The Free Software Foundation may publish new, revised versions
of the \s-1GNU\s0 Free Documentation License from time to time. Such new
@@ -579,7 +578,7 @@ Document.
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
-\&\*(L"Massive Multiauthor Collaboration\*(R" (or \*(L"\s-1MMC\*(R"\s0) contained in the
+\&\*(L"Massive Multiauthor Collaboration\*(R" (or \*(L"\s-1MMC\s0\*(R") contained in the
site means any set of copyrightable works thus published on the \s-1MMC\s0
site.
.Sp
@@ -594,14 +593,14 @@ in part, as part of another Document.
.Sp
An \s-1MMC\s0 is \*(L"eligible for relicensing\*(R" if it is licensed under this
License, and if all works that were first published under this License
-somewhere other than this \s-1MMC,\s0 and subsequently incorporated in whole
-or in part into the \s-1MMC, \\fIs0\fR\|(1) had no cover texts or invariant sections,
+somewhere other than this \s-1MMC\s0, and subsequently incorporated in whole
+or in part into the \s-1MMC\s0, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
.Sp
The operator of an \s-1MMC\s0 Site may republish an \s-1MMC\s0 contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the \s-1MMC\s0 is eligible for relicensing.
-.SS "\s-1ADDENDUM:\s0 How to use this License for your documents"
+.Sh "\s-1ADDENDUM:\s0 How to use this License for your documents"
.IX Subsection "ADDENDUM: How to use this License for your documents"
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
diff --git a/gcc/doc/gfortran.1 b/gcc/doc/gfortran.1
index 25ede88491..d6c790434b 100644
--- a/gcc/doc/gfortran.1
+++ b/gcc/doc/gfortran.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GFORTRAN 1"
-.TH GFORTRAN 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GFORTRAN 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -182,7 +181,7 @@ by type. Explanations are in the following sections.
\&\-fdefault\-real\-8 \-fdollar\-ok \-ffixed\-line\-length\-\fR\fIn\fR
\&\fB\-ffixed\-line\-length\-none \-ffree\-form \-ffree\-line\-length\-\fR\fIn\fR
\&\fB\-ffree\-line\-length\-none \-fimplicit\-none \-finteger\-4\-integer\-8
-\&\-fmax\-identifier\-length \-fmodule\-private \-fno\-fixed\-form \-fno\-range\-check
+\&\-fmax\-identifier\-length \-fmodule\-private \-ffixed\-form \-fno\-range\-check
\&\-fopenacc \-fopenmp \-freal\-4\-real\-10 \-freal\-4\-real\-16 \-freal\-4\-real\-8
\&\-freal\-8\-real\-10 \-freal\-8\-real\-16 \-freal\-8\-real\-4 \-std=\fR\fIstd\fR\fB \fR
.IP "\fIPreprocessing Options\fR" 4
@@ -233,7 +232,7 @@ by type. Explanations are in the following sections.
\&\-fno\-automatic \-fno\-protect\-parens \-fno\-underscoring
\&\-fsecond\-underscore \-fpack\-derived \-frealloc\-lhs \-frecursive
\&\-frepack\-arrays \-fshort\-enums \-fstack\-arrays\fR
-.SS "Options controlling Fortran dialect"
+.Sh "Options controlling Fortran dialect"
.IX Subsection "Options controlling Fortran dialect"
The following options control the details of the Fortran dialect
accepted by the compiler:
@@ -279,7 +278,7 @@ backslash character to \*(L"C\-style\*(R" escape characters. The following
combinations are expanded \f(CW\*(C`\ea\*(C'\fR, \f(CW\*(C`\eb\*(C'\fR, \f(CW\*(C`\ef\*(C'\fR, \f(CW\*(C`\en\*(C'\fR,
\&\f(CW\*(C`\er\*(C'\fR, \f(CW\*(C`\et\*(C'\fR, \f(CW\*(C`\ev\*(C'\fR, \f(CW\*(C`\e\e\*(C'\fR, and \f(CW\*(C`\e0\*(C'\fR to the \s-1ASCII\s0
characters alert, backspace, form feed, newline, carriage return,
-horizontal tab, vertical tab, backslash, and \s-1NUL,\s0 respectively.
+horizontal tab, vertical tab, backslash, and \s-1NUL\s0, respectively.
Additionally, \f(CW\*(C`\ex\*(C'\fR\fInn\fR, \f(CW\*(C`\eu\*(C'\fR\fInnnn\fR and
\&\f(CW\*(C`\eU\*(C'\fR\fInnnnnnnn\fR (where each \fIn\fR is a hexadecimal digit) are
translated into the Unicode characters corresponding to the specified code
@@ -334,7 +333,7 @@ compilation sentinels in free form and \f(CW\*(C`c$\*(C'\fR, \f(CW\*(C`*$\*(C'\f
OpenACC runtime library to be linked in.
.Sp
Note that this is an experimental feature, incomplete, and subject to
-change in future versions of \s-1GCC. \s0 See
+change in future versions of \s-1GCC\s0. See
<\fBhttps://gcc.gnu.org/wiki/OpenACC\fR> for more information.
.IP "\fB\-fopenmp\fR" 4
.IX Item "-fopenmp"
@@ -429,8 +428,8 @@ language standard, and warnings are given for the Fortran 77 features
that are permitted but obsolescent in later standards. \fB\-std=f2008ts\fR
allows the Fortran 2008 standard including the additions of the
Technical Specification (\s-1TS\s0) 29113 on Further Interoperability of Fortran
-with C and \s-1TS 18508\s0 on Additional Parallel Features in Fortran.
-.SS "Enable and customize preprocessing"
+with C and \s-1TS\s0 18508 on Additional Parallel Features in Fortran.
+.Sh "Enable and customize preprocessing"
.IX Subsection "Enable and customize preprocessing"
Preprocessor related options. See section
\&\fBPreprocessing and conditional compilation\fR for more detailed
@@ -618,7 +617,7 @@ by the linemarkers.
.IX Item "-Uname"
Cancel any previous definition of \fIname\fR, either built in or provided
with a \fB\-D\fR option.
-.SS "Options to request or suppress errors and warnings"
+.Sh "Options to request or suppress errors and warnings"
.IX Subsection "Options to request or suppress errors and warnings"
Errors are diagnostic messages that report that the \s-1GNU\s0 Fortran compiler
cannot compile the relevant piece of source code. The compiler will
@@ -773,10 +772,10 @@ While technically legal these usually indicate that an error has been made.
This currently produces a warning under the following circumstances:
.RS 4
.IP "*" 4
-An \s-1INTEGER SELECT\s0 construct has a \s-1CASE\s0 that can never be matched as its
+An \s-1INTEGER\s0 \s-1SELECT\s0 construct has a \s-1CASE\s0 that can never be matched as its
lower value is greater than its upper value.
.IP "*" 4
-A \s-1LOGICAL SELECT\s0 construct has three \s-1CASE\s0 statements.
+A \s-1LOGICAL\s0 \s-1SELECT\s0 construct has three \s-1CASE\s0 statements.
.IP "*" 4
A \s-1TRANSFER\s0 specifies a source that is shorter than the destination.
.IP "*" 4
@@ -861,7 +860,7 @@ time. This option is implied by \fB\-Wall\fR.
Turns all warnings into errors.
.PP
Some of these have no effect when compiling programs written in Fortran.
-.SS "Options for debugging your program or \s-1GNU\s0 Fortran"
+.Sh "Options for debugging your program or \s-1GNU\s0 Fortran"
.IX Subsection "Options for debugging your program or GNU Fortran"
\&\s-1GNU\s0 Fortran has various special options that are used for debugging
either your program or the \s-1GNU\s0 Fortran compiler.
@@ -893,8 +892,8 @@ exceptions: \fBinvalid\fR (invalid floating point operation, such as
in a floating point operation), \fBinexact\fR (loss of precision
during operation), and \fBdenormal\fR (operation performed on a
denormal value). The first five exceptions correspond to the five
-\&\s-1IEEE 754\s0 exceptions, whereas the last one (\fBdenormal\fR) is not
-part of the \s-1IEEE 754\s0 standard but is available on some common
+\&\s-1IEEE\s0 754 exceptions, whereas the last one (\fBdenormal\fR) is not
+part of the \s-1IEEE\s0 754 standard but is available on some common
architectures such as x86.
.Sp
The first three exceptions (\fBinvalid\fR, \fBzero\fR, and
@@ -926,7 +925,7 @@ action \fBcore\fR), the Fortran runtime library tries to output a
backtrace of the error. \f(CW\*(C`\-fno\-backtrace\*(C'\fR disables the backtrace
generation. This option only has influence for compilation of the
Fortran main program.
-.SS "Options for directory search"
+.Sh "Options for directory search"
.IX Subsection "Options for directory search"
These options affect how \s-1GNU\s0 Fortran searches
for files specified by the \f(CW\*(C`INCLUDE\*(C'\fR directive and where it searches
@@ -958,7 +957,7 @@ The default is the current directory.
.IX Item "-fintrinsic-modules-path dir"
This option specifies the location of pre-compiled intrinsic modules, if
they are not in the default location expected by the compiler.
-.SS "Influencing the linking step"
+.Sh "Influencing the linking step"
.IX Subsection "Influencing the linking step"
These options come into play when the compiler links object files into an
executable output file. They are meaningless if the compiler is not doing
@@ -969,7 +968,7 @@ On systems that provide \fIlibgfortran\fR as a shared and a static
library, this option forces the use of the static version. If no
shared version of \fIlibgfortran\fR was built when the compiler was
configured, this option has no effect.
-.SS "Influencing runtime behavior"
+.Sh "Influencing runtime behavior"
.IX Subsection "Influencing runtime behavior"
These options affect the runtime behavior of programs compiled with \s-1GNU\s0 Fortran.
.IP "\fB\-fconvert=\fR\fIconversion\fR" 4
@@ -1004,7 +1003,7 @@ negative in the \f(CW\*(C`SIGN\*(C'\fR intrinsic. \fB\-fno\-sign\-zero\fR does
print the negative sign of zero values (or values rounded to zero for I/O)
and regards zero as positive number in the \f(CW\*(C`SIGN\*(C'\fR intrinsic for
compatibility with Fortran 77. The default is \fB\-fsign\-zero\fR.
-.SS "Options for code generation conventions"
+.Sh "Options for code generation conventions"
.IX Subsection "Options for code generation conventions"
These machine-independent options control the interface conventions
used in code generation.
@@ -1036,7 +1035,7 @@ extra argument in the calling sequence that points to where to
store the return value. Under the default \s-1GNU\s0 calling conventions, such
functions simply return their results as they would in \s-1GNU\s0
C\-\-\-default \f(CW\*(C`REAL\*(C'\fR functions return the C type \f(CW\*(C`float\*(C'\fR, and
-\&\f(CW\*(C`COMPLEX\*(C'\fR functions return the \s-1GNU C\s0 type \f(CW\*(C`complex\*(C'\fR.
+\&\f(CW\*(C`COMPLEX\*(C'\fR functions return the \s-1GNU\s0 C type \f(CW\*(C`complex\*(C'\fR.
Additionally, this option implies the \fB\-fsecond\-underscore\fR
option, unless \fB\-fno\-second\-underscore\fR is explicitly requested.
.Sp
diff --git a/gcc/doc/gij.1 b/gcc/doc/gij.1
index e16823229d..43a9b06083 100644
--- a/gcc/doc/gij.1
+++ b/gcc/doc/gij.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GIJ 1"
-.TH GIJ 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GIJ 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/gpl.7 b/gcc/doc/gpl.7
index 45e0048b78..f7adb056ce 100644
--- a/gcc/doc/gpl.7
+++ b/gcc/doc/gpl.7
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GPL 7"
-.TH GPL 7 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GPL 7 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -142,9 +141,9 @@
gpl \- GNU General Public License
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-.SS "\s-1GNU\s0 General Public License"
+.Sh "\s-1GNU\s0 General Public License"
.IX Subsection "GNU General Public License"
-.SS "Version 3, 29 June 2007"
+.Sh "Version 3, 29 June 2007"
.IX Subsection "Version 3, 29 June 2007"
.Vb 1
\& Copyright (c) 2007 Free Software Foundation, Inc. <http://fsf.org/>
@@ -152,7 +151,7 @@ gpl \- GNU General Public License
\& Everyone is permitted to copy and distribute verbatim copies of this
\& license document, but changing it is not allowed.
.Ve
-.SS "Preamble"
+.Sh "Preamble"
.IX Subsection "Preamble"
The \s-1GNU\s0 General Public License is a free, copyleft license for
software and other kinds of works.
@@ -185,7 +184,7 @@ freedoms that you received. You must make sure that they, too,
receive or can get the source code. And you must show them these
terms so they know their rights.
.PP
-Developers that use the \s-1GNU GPL\s0 protect your rights with two steps:
+Developers that use the \s-1GNU\s0 \s-1GPL\s0 protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
.PP
@@ -204,7 +203,7 @@ individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the \s-1GPL\s0 to prohibit the
practice for those products. If such problems arise substantially in
other domains, we stand ready to extend this provision to those
-domains in future versions of the \s-1GPL,\s0 as needed to protect the
+domains in future versions of the \s-1GPL\s0, as needed to protect the
freedom of users.
.PP
Finally, every program is threatened constantly by software patents.
@@ -216,7 +215,7 @@ assures that patents cannot be used to render the program non-free.
.PP
The precise terms and conditions for copying, distribution and
modification follow.
-.SS "\s-1TERMS AND CONDITIONS\s0"
+.Sh "\s-1TERMS\s0 \s-1AND\s0 \s-1CONDITIONS\s0"
.IX Subsection "TERMS AND CONDITIONS"
.IP "0. Definitions." 4
.IX Item "0. Definitions."
@@ -751,26 +750,26 @@ author or copyright holder as a result of your choosing to follow a
later version.
.IP "15. Disclaimer of Warranty." 4
.IX Item "15. Disclaimer of Warranty."
-\&\s-1THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \*(L"AS IS\*(R" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
-CORRECTION.\s0
+\&\s-1THERE\s0 \s-1IS\s0 \s-1NO\s0 \s-1WARRANTY\s0 \s-1FOR\s0 \s-1THE\s0 \s-1PROGRAM\s0, \s-1TO\s0 \s-1THE\s0 \s-1EXTENT\s0 \s-1PERMITTED\s0 \s-1BY\s0
+\&\s-1APPLICABLE\s0 \s-1LAW\s0. \s-1EXCEPT\s0 \s-1WHEN\s0 \s-1OTHERWISE\s0 \s-1STATED\s0 \s-1IN\s0 \s-1WRITING\s0 \s-1THE\s0 \s-1COPYRIGHT\s0
+\&\s-1HOLDERS\s0 \s-1AND/OR\s0 \s-1OTHER\s0 \s-1PARTIES\s0 \s-1PROVIDE\s0 \s-1THE\s0 \s-1PROGRAM\s0 \*(L"\s-1AS\s0 \s-1IS\s0\*(R" \s-1WITHOUT\s0
+\&\s-1WARRANTY\s0 \s-1OF\s0 \s-1ANY\s0 \s-1KIND\s0, \s-1EITHER\s0 \s-1EXPRESSED\s0 \s-1OR\s0 \s-1IMPLIED\s0, \s-1INCLUDING\s0, \s-1BUT\s0 \s-1NOT\s0
+\&\s-1LIMITED\s0 \s-1TO\s0, \s-1THE\s0 \s-1IMPLIED\s0 \s-1WARRANTIES\s0 \s-1OF\s0 \s-1MERCHANTABILITY\s0 \s-1AND\s0 \s-1FITNESS\s0 \s-1FOR\s0
+A \s-1PARTICULAR\s0 \s-1PURPOSE\s0. \s-1THE\s0 \s-1ENTIRE\s0 \s-1RISK\s0 \s-1AS\s0 \s-1TO\s0 \s-1THE\s0 \s-1QUALITY\s0 \s-1AND\s0
+\&\s-1PERFORMANCE\s0 \s-1OF\s0 \s-1THE\s0 \s-1PROGRAM\s0 \s-1IS\s0 \s-1WITH\s0 \s-1YOU\s0. \s-1SHOULD\s0 \s-1THE\s0 \s-1PROGRAM\s0 \s-1PROVE\s0
+\&\s-1DEFECTIVE\s0, \s-1YOU\s0 \s-1ASSUME\s0 \s-1THE\s0 \s-1COST\s0 \s-1OF\s0 \s-1ALL\s0 \s-1NECESSARY\s0 \s-1SERVICING\s0, \s-1REPAIR\s0 \s-1OR\s0
+\&\s-1CORRECTION\s0.
.IP "16. Limitation of Liability." 4
.IX Item "16. Limitation of Liability."
-\&\s-1IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
-CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM \s0(\s-1INCLUDING BUT
-NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
-LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
-TO OPERATE WITH ANY OTHER PROGRAMS\s0), \s-1EVEN IF SUCH HOLDER OR OTHER
-PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\s0
+\&\s-1IN\s0 \s-1NO\s0 \s-1EVENT\s0 \s-1UNLESS\s0 \s-1REQUIRED\s0 \s-1BY\s0 \s-1APPLICABLE\s0 \s-1LAW\s0 \s-1OR\s0 \s-1AGREED\s0 \s-1TO\s0 \s-1IN\s0 \s-1WRITING\s0
+\&\s-1WILL\s0 \s-1ANY\s0 \s-1COPYRIGHT\s0 \s-1HOLDER\s0, \s-1OR\s0 \s-1ANY\s0 \s-1OTHER\s0 \s-1PARTY\s0 \s-1WHO\s0 \s-1MODIFIES\s0 \s-1AND/OR\s0
+\&\s-1CONVEYS\s0 \s-1THE\s0 \s-1PROGRAM\s0 \s-1AS\s0 \s-1PERMITTED\s0 \s-1ABOVE\s0, \s-1BE\s0 \s-1LIABLE\s0 \s-1TO\s0 \s-1YOU\s0 \s-1FOR\s0 \s-1DAMAGES\s0,
+\&\s-1INCLUDING\s0 \s-1ANY\s0 \s-1GENERAL\s0, \s-1SPECIAL\s0, \s-1INCIDENTAL\s0 \s-1OR\s0 \s-1CONSEQUENTIAL\s0 \s-1DAMAGES\s0
+\&\s-1ARISING\s0 \s-1OUT\s0 \s-1OF\s0 \s-1THE\s0 \s-1USE\s0 \s-1OR\s0 \s-1INABILITY\s0 \s-1TO\s0 \s-1USE\s0 \s-1THE\s0 \s-1PROGRAM\s0 (\s-1INCLUDING\s0 \s-1BUT\s0
+\&\s-1NOT\s0 \s-1LIMITED\s0 \s-1TO\s0 \s-1LOSS\s0 \s-1OF\s0 \s-1DATA\s0 \s-1OR\s0 \s-1DATA\s0 \s-1BEING\s0 \s-1RENDERED\s0 \s-1INACCURATE\s0 \s-1OR\s0
+\&\s-1LOSSES\s0 \s-1SUSTAINED\s0 \s-1BY\s0 \s-1YOU\s0 \s-1OR\s0 \s-1THIRD\s0 \s-1PARTIES\s0 \s-1OR\s0 A \s-1FAILURE\s0 \s-1OF\s0 \s-1THE\s0 \s-1PROGRAM\s0
+\&\s-1TO\s0 \s-1OPERATE\s0 \s-1WITH\s0 \s-1ANY\s0 \s-1OTHER\s0 \s-1PROGRAMS\s0), \s-1EVEN\s0 \s-1IF\s0 \s-1SUCH\s0 \s-1HOLDER\s0 \s-1OR\s0 \s-1OTHER\s0
+\&\s-1PARTY\s0 \s-1HAS\s0 \s-1BEEN\s0 \s-1ADVISED\s0 \s-1OF\s0 \s-1THE\s0 \s-1POSSIBILITY\s0 \s-1OF\s0 \s-1SUCH\s0 \s-1DAMAGES\s0.
.IP "17. Interpretation of Sections 15 and 16." 4
.IX Item "17. Interpretation of Sections 15 and 16."
If the disclaimer of warranty and limitation of liability provided
@@ -779,9 +778,9 @@ reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
-.SS "\s-1END OF TERMS AND CONDITIONS\s0"
+.Sh "\s-1END\s0 \s-1OF\s0 \s-1TERMS\s0 \s-1AND\s0 \s-1CONDITIONS\s0"
.IX Subsection "END OF TERMS AND CONDITIONS"
-.SS "How to Apply These Terms to Your New Programs"
+.Sh "How to Apply These Terms to Your New Programs"
.IX Subsection "How to Apply These Terms to Your New Programs"
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
@@ -830,7 +829,7 @@ use an \*(L"about box\*(R".
.PP
You should also get your employer (if you work as a programmer) or school,
if any, to sign a \*(L"copyright disclaimer\*(R" for the program, if necessary.
-For more information on this, and how to apply and follow the \s-1GNU GPL,\s0 see
+For more information on this, and how to apply and follow the \s-1GNU\s0 \s-1GPL\s0, see
<\fBhttp://www.gnu.org/licenses/\fR>.
.PP
The \s-1GNU\s0 General Public License does not permit incorporating your
diff --git a/gcc/doc/grmic.1 b/gcc/doc/grmic.1
index a299f79db8..5669ee0951 100644
--- a/gcc/doc/grmic.1
+++ b/gcc/doc/grmic.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GRMIC 1"
-.TH GRMIC 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH GRMIC 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -148,8 +147,8 @@ grmic \- Generate stubs for Remote Method Invocation
\&\fBgrmic\fR is a utility included with \f(CW\*(C`libgcj\*(C'\fR which generates
stubs for remote objects.
.PP
-Note that this program isn't yet fully compatible with the \s-1JDK
-\&\s0\fBgrmic\fR. Some options, such as \fB\-classpath\fR, are
+Note that this program isn't yet fully compatible with the \s-1JDK\s0
+\&\fBgrmic\fR. Some options, such as \fB\-classpath\fR, are
recognized but currently ignored. We have left these options
undocumented for now.
.PP
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 783116e679..d8d393985c 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3408,13 +3408,24 @@ not support option @option{-mabi=ilp32}.
To enable a workaround for the Cortex-A53 erratum number 835769 by default
(for all CPUs regardless of -mcpu option given) at configure time use the
@option{--enable-fix-cortex-a53-835769} option. This will enable the fix by
-default and can be explicitly disabled during during compilation by passing the
+default and can be explicitly disabled during compilation by passing the
@option{-mno-fix-cortex-a53-835769} option. Conversely,
@option{--disable-fix-cortex-a53-835769} will disable the workaround by
default. The workaround is disabled by default if neither of
@option{--enable-fix-cortex-a53-835769} or
@option{--disable-fix-cortex-a53-835769} is given at configure time.
+To enable a workaround for the Cortex-A53 erratum number 843419 by default
+(for all CPUs regardless of -mcpu option given) at configure time use the
+@option{--enable-fix-cortex-a53-843419} option. This workaround is applied at
+link time. Enabling the workaround will cause GCC to pass the relevant option
+to the linker. It can be explicitly disabled during compilation by passing the
+@option{-mno-fix-cortex-a53-843419} option. Conversely,
+@option{--disable-fix-cortex-a53-843419} will disable the workaround by default.
+The workaround is disabled by default if neither of
+@option{--enable-fix-cortex-a53-843419} or
+@option{--disable-fix-cortex-a53-843419} is given at configure time.
+
@html
<hr />
@end html
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 520c2c51ce..f84a1994aa 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -511,6 +511,7 @@ Objective-C and Objective-C++ Dialects}.
-momit-leaf-frame-pointer -mno-omit-leaf-frame-pointer @gol
-mtls-dialect=desc -mtls-dialect=traditional @gol
-mfix-cortex-a53-835769 -mno-fix-cortex-a53-835769 @gol
+-mfix-cortex-a53-843419 -mno-fix-cortex-a53-843419 @gol
-march=@var{name} -mcpu=@var{name} -mtune=@var{name}}
@emph{Adapteva Epiphany Options}
@@ -1075,7 +1076,7 @@ See RS/6000 and PowerPC Options.
-maes -mpclmul -mfsgsbase -mrdrnd -mf16c -mfma -mprefetchwt1 @gol
-mclflushopt -mxsavec -mxsaves @gol
-msse4a -m3dnow -mpopcnt -mabm -mbmi -mtbm -mfma4 -mxop -mlzcnt @gol
--mbmi2 -mfxsr -mxsave -mxsaveopt -mrtm -mlwp -mmpx -mthreads @gol
+-mbmi2 -mfxsr -mxsave -mxsaveopt -mrtm -mlwp -mmpx -mmwaitx -mthreads @gol
-mno-align-stringops -minline-all-stringops @gol
-minline-stringops-dynamically -mstringop-strategy=@var{alg} @gol
-mmemcpy-strategy=@var{strategy} -mmemset-strategy=@var{strategy} @gol
@@ -2703,10 +2704,10 @@ int i = @{ 2.2 @}; // error: narrowing from double to int
This flag is included in @option{-Wall} and @option{-Wc++11-compat}.
-With @option{-std=c++11}, @option{-Wno-narrowing} suppresses for
-non-constants the diagnostic required by the standard. Note that this
-does not affect the meaning of well-formed code; narrowing conversions
-are still considered ill-formed in SFINAE context.
+With @option{-std=c++11}, @option{-Wno-narrowing} suppresses the diagnostic
+required by the standard. Note that this does not affect the meaning
+of well-formed code; narrowing conversions are still considered
+ill-formed in SFINAE context.
@item -Wnoexcept @r{(C++ and Objective-C++ only)}
@opindex Wnoexcept
@@ -12312,6 +12313,14 @@ Enable or disable the workaround for the ARM Cortex-A53 erratum number 835769.
This involves inserting a NOP instruction between memory instructions and
64-bit integer multiply-accumulate instructions.
+@item -mfix-cortex-a53-843419
+@itemx -mno-fix-cortex-a53-843419
+@opindex mfix-cortex-a53-843419
+@opindex mno-fix-cortex-a53-843419
+Enable or disable the workaround for the ARM Cortex-A53 erratum number 843419.
+This erratum workaround is made at link time and this will only pass the
+corresponding flag to the linker.
+
@item -march=@var{name}
@opindex march
Specify the name of the target architecture, optionally suffixed by one or
@@ -20208,7 +20217,8 @@ The default is to not print debug information.
Generate code that runs on @var{cpu-type}, which is the name of a system
representing a certain processor type. Possible values for
@var{cpu-type} are @samp{g5}, @samp{g6}, @samp{z900}, @samp{z990},
-@samp{z9-109}, @samp{z9-ec}, @samp{z10}, @samp{z196}, and @samp{zEC12}.
+@samp{z9-109}, @samp{z9-ec}, @samp{z10}, @samp{z196}, @samp{zEC12},
+and @samp{z13}.
When generating code using the instructions available on z/Architecture,
the default is @option{-march=z900}. Otherwise, the default is
@option{-march=g5}.
@@ -22289,7 +22299,7 @@ in ordinary CPU registers instead.
@opindex mno-fancy-math-387
Some 387 emulators do not support the @code{sin}, @code{cos} and
@code{sqrt} instructions for the 387. Specify this option to avoid
-generating those instructions. This option is the default on FreeBSD,
+generating those instructions. This option is the default on
OpenBSD and NetBSD@. This option is overridden when @option{-march}
indicates that the target CPU always has an FPU and so the
instruction does not need emulation. These
@@ -22625,10 +22635,13 @@ preferred alignment to @option{-mpreferred-stack-boundary=2}.
@need 200
@itemx -mmpx
@opindex mmpx
+@need 200
+@itemx -mmwaitx
+@opindex mmwaitx
These switches enable the use of instructions in the MMX, SSE,
SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER, AVX512CD,
SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A, FMA4, XOP, LWP, ABM,
-BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX or 3DNow!@:
+BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX, MWAITX or 3DNow!@:
extended instruction sets. Each has a corresponding @option{-mno-} option
to disable use of these instructions.
diff --git a/gcc/doc/jcf-dump.1 b/gcc/doc/jcf-dump.1
index d9ff405e74..9e5510f950 100644
--- a/gcc/doc/jcf-dump.1
+++ b/gcc/doc/jcf-dump.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "JCF-DUMP 1"
-.TH JCF-DUMP 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH JCF-DUMP 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/jv-convert.1 b/gcc/doc/jv-convert.1
index 50d4b7cb22..a208af283e 100644
--- a/gcc/doc/jv-convert.1
+++ b/gcc/doc/jv-convert.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "JV-CONVERT 1"
-.TH JV-CONVERT 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH JV-CONVERT 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index bc1ec9d4f0..bbd91c2367 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -3027,6 +3027,27 @@ Altivec vector register
@item wa
Any VSX register if the -mvsx option was used or NO_REGS.
+When using any of the register constraints (@code{wa}, @code{wd},
+@code{wf}, @code{wg}, @code{wh}, @code{wi}, @code{wj}, @code{wk},
+@code{wl}, @code{wm}, @code{ws}, @code{wt}, @code{wu}, @code{wv},
+@code{ww}, or @code{wy}) that take VSX registers, you must use
+@code{%x<n>} in the template so that the correct register is used.
+Otherwise the register number output in the assembly file will be
+incorrect if an Altivec register is an operand of a VSX instruction
+that expects VSX register numbering.
+
+@smallexample
+asm ("xvadddp %x0,%x1,%x2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+@end smallexample
+
+is correct, but:
+
+@smallexample
+asm ("xvadddp %0,%1,%2" : "=wa" (v1) : "wa" (v2), "wa" (v3));
+@end smallexample
+
+is not correct.
+
@item wd
VSX vector register to hold vector double data or NO_REGS.
diff --git a/gcc/doc/rebuild-gcj-db.1 b/gcc/doc/rebuild-gcj-db.1
index e919eb8c32..4af88c6b0e 100644
--- a/gcc/doc/rebuild-gcj-db.1
+++ b/gcc/doc/rebuild-gcj-db.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -38,8 +46,6 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
-. ds C`
-. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -47,27 +53,20 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.\"
-.\" Avoid warning from groff about undefined register 'F'.
-.de IX
+.ie \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-.nr rF 0
-.if \n(.g .if rF .nr rF 1
-.if (\n(rF:(\n(.g==0)) \{
-. if \nF \{
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. nr % 0
+. rr F
+.\}
+.el \{\
+. de IX
..
-. if !\nF==2 \{
-. nr % 0
-. nr F 2
-. \}
-. \}
.\}
-.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -133,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "REBUILD-GCJ-DB 1"
-.TH REBUILD-GCJ-DB 1 "2015-04-22" "gcc-5.1.0" "GNU"
+.TH REBUILD-GCJ-DB 1 "2015-07-16" "gcc-5.2.0" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
View Lorry Controller Status