37
# svn diff svn://gcc.gnu.org/svn/gcc/tags/ubuntu/gcc-4_2_3-release svn://gcc.gnu.org/svn/gcc/branches/ubuntu/gcc-4_2-branch \
37
# svn diff svn://gcc.gnu.org/svn/gcc/tags/ubuntu/gcc-4_2_4-release svn://gcc.gnu.org/svn/gcc/branches/ubuntu/gcc-4_2-branch \
38
38
# | awk '/^Index:.*\.class/ {skip=1; next} /^Index:/ { skip=0 } skip==0'
40
Index: gcc/doc/sourcebuild.texi
41
===================================================================
42
--- gcc/doc/sourcebuild.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
43
+++ gcc/doc/sourcebuild.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
46
Common definitions for manuals.
49
The GNU General Public License.
51
A copy of @file{texinfo.tex} known to work with the GCC manuals.
52
Index: gcc/doc/options.texi
53
===================================================================
54
--- gcc/doc/options.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
55
+++ gcc/doc/options.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
58
@chapter Option specification files
59
@cindex option specification files
60
-@cindex @samp{opts.sh}
61
+@cindex @samp{optc-gen.awk}
63
Most GCC command-line options are described by special option
64
definition files, the names of which conventionally end in
65
Index: gcc/doc/gcc.texi
66
===================================================================
67
--- gcc/doc/gcc.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
68
+++ gcc/doc/gcc.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
76
@c ---------------------------------------------------------------------
78
Index: gcc/doc/gccint.texi
79
===================================================================
80
--- gcc/doc/gccint.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
81
+++ gcc/doc/gccint.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
89
@c ---------------------------------------------------------------------
91
Index: gcc/doc/invoke.texi
92
===================================================================
93
--- gcc/doc/invoke.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
94
+++ gcc/doc/invoke.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
96
@gccoptlist{-d@var{letters} -dumpspecs -dumpmachine -dumpversion @gol
97
-fdump-noaddr -fdump-unnumbered -fdump-translation-unit@r{[}-@var{n}@r{]} @gol
98
-fdump-class-hierarchy@r{[}-@var{n}@r{]} @gol
99
--fdump-ipa-all -fdump-ipa-cgraph @gol
100
+-fdump-ipa-all -fdump-ipa-cgraph -fdump-ipa-inline @gol
102
-fdump-tree-original@r{[}-@var{n}@r{]} @gol
103
-fdump-tree-optimized@r{[}-@var{n}@r{]} @gol
104
--fdump-tree-inlined@r{[}-@var{n}@r{]} @gol
105
-fdump-tree-cfg -fdump-tree-vcg -fdump-tree-alias @gol
107
-fdump-tree-ssa@r{[}-@var{n}@r{]} -fdump-tree-pre@r{[}-@var{n}@r{]} @gol
108
@@ -1173,12 +1172,31 @@
109
Supported by GCC}, for details of these standard versions. This option
110
is currently only supported when compiling C or C++.
112
+The compiler can accept several base standards, such as @samp{c89} or
113
+@samp{c++98}, and GNU dialects of those standards, such as
114
+@samp{gnu89} or @samp{gnu++98}. By specifing a base standard, the
115
+compiler will accept all programs following that standard and those
116
+using GNU extensions that do not contradict it. For example,
117
+@samp{-std=c89} turns off certain features of GCC that are
118
+incompatible with ISO C90, such as the @code{asm} and @code{typeof}
119
+keywords, but not other GNU extensions that do not have a meaning in
120
+ISO C90, such as omitting the middle term of a @code{?:}
121
+expression. On the other hand, by specifing a GNU dialect of a
122
+standard, all features the compiler support are enabled, even when
123
+those features change the meaning of the base standard and some
124
+strict-conforming programs may be rejected. The particular standard
125
+is used by @option{-pedantic} to identify which features are GNU
126
+extensions given that version of the standard. For example
127
+@samp{-std=gnu89 -pedantic} would warn about C++ style @samp{//}
128
+comments, while @samp{-std=gnu99 -pedantic} would not.
130
A value for this option must be provided; possible values are
135
-ISO C90 (same as @option{-ansi}).
136
+Support all ISO C90 programs (certain GNU extensions that conflict
137
+with ISO C90 are disabled). Same as @option{-ansi} for C code.
140
ISO C90 as modified in amendment 1.
141
@@ -1192,31 +1210,23 @@
142
names @samp{c9x} and @samp{iso9899:199x} are deprecated.
145
-Default, ISO C90 plus GNU extensions (including some C99 features).
146
+GNU dialect of ISO C90 (including some C99 features). This
147
+is the default for C code.
151
-ISO C99 plus GNU extensions. When ISO C99 is fully implemented in GCC,
152
+GNU dialect of ISO C99. When ISO C99 is fully implemented in GCC,
153
this will become the default. The name @samp{gnu9x} is deprecated.
156
-The 1998 ISO C++ standard plus amendments.
157
+The 1998 ISO C++ standard plus amendments. Same as @option{-ansi} for
161
-The same as @option{-std=c++98} plus GNU extensions. This is the
162
-default for C++ code.
163
+GNU dialect of @option{-std=c++98}. This is the default for
167
-Even when this option is not specified, you can still use some of the
168
-features of newer standards in so far as they do not conflict with
169
-previous C standards. For example, you may use @code{__restrict__} even
170
-when @option{-std=c99} is not specified.
172
-The @option{-std} options specifying some version of ISO C have the same
173
-effects as @option{-ansi}, except that features that were not in ISO C90
174
-but are in the specified version (for example, @samp{//} comments and
175
-the @code{inline} keyword in ISO C99) are not disabled.
178
@opindex fgnu89-inline
179
The option @option{-fgnu89-inline} tells GCC to use the traditional
180
@@ -4148,12 +4158,15 @@
184
-Enables all inter-procedural analysis dumps; currently the only produced
185
-dump is the @samp{cgraph} dump.
186
+Enables all inter-procedural analysis dumps.
189
Dumps information about call-graph optimization, unused function removal,
190
and inlining decisions.
193
+Dump after function inlining.
197
@item -fdump-tree-@var{switch}
198
@@ -4206,9 +4219,6 @@
200
Dump after all tree based optimization, to @file{@var{file}.optimized}.
203
-Dump after function inlining, to @file{@var{file}.inlined}.
206
@opindex fdump-tree-gimple
207
Dump each function before and after the gimplification pass to a file. The
208
Index: gcc/java/gcj.texi
209
===================================================================
210
--- gcc/java/gcj.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
211
+++ gcc/java/gcj.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
217
+@include gpl_v3.texi
221
Index: gcc/ada/gnat_rm.texi
222
===================================================================
223
--- gcc/ada/gnat_rm.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
224
+++ gcc/ada/gnat_rm.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
229
-Copyright @copyright{} 1995-2004, Free Software Foundation
230
+Copyright @copyright{} 1995-2004, 2005, 2006, 2007, 2008 Free Software
233
Permission is granted to copy, distribute and/or modify this document
234
under the terms of the GNU Free Documentation License, Version 1.2
235
@@ -1679,7 +1680,7 @@
236
pragma applies. If more than one function name exists of this name in
237
the declarative part you must use the @code{Parameter_Types} and
238
@code{Result_Type} parameters is mandatory to achieve the required
239
-unique designation. @var{subtype_ mark}s in these parameters must
240
+unique designation. @var{subtype_mark}s in these parameters must
241
exactly match the subtypes in the corresponding function specification,
242
using positional notation to match parameters with subtype marks.
243
The form with an @code{'Access} attribute can be used to match an
244
@@ -6755,7 +6756,7 @@
248
-The maximum line length is 255 characters an the maximum length of a
249
+The maximum line length is 255 characters and the maximum length of a
250
lexical element is also 255 characters.
253
@@ -7914,7 +7915,7 @@
254
causes two separate arguments @code{-labc} and @code{-ldef} to be passed to the
255
linker. The order of linker options is preserved for a given unit. The final
256
list of options passed to the linker is in reverse order of the elaboration
257
-order. For example, linker options fo a body always appear before the options
258
+order. For example, linker options for a body always appear before the options
259
from the corresponding package spec.
262
@@ -14185,7 +14186,7 @@
265
for I in Cr_Var2'range loop
266
- Cr_Var2 (I) := =-1;
271
Index: gcc/ada/gnat_ugn.texi
272
===================================================================
273
--- gcc/ada/gnat_ugn.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
274
+++ gcc/ada/gnat_ugn.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
279
-Copyright @copyright{} 1995-2005, Free Software Foundation
280
+Copyright @copyright{} 1995-2005, 2006, 2007, 2008 Free Software
283
Permission is granted to copy, distribute and/or modify this document
284
under the terms of the GNU Free Documentation License, Version 1.2
285
@@ -5225,9 +5226,9 @@
286
@cindex @option{-gnatVf} (@command{gcc})
287
In the absence of this switch, validity checking occurs only for discrete
288
values. If @option{-gnatVf} is specified, then validity checking also applies
289
-for floating-point values, and NaN's and infinities are considered invalid,
290
+for floating-point values, and NaNs and infinities are considered invalid,
291
as well as out of range values for constrained types. Note that this means
292
-that standard @code{IEEE} infinity mode is not allowed. The exact contexts
293
+that standard IEEE infinity mode is not allowed. The exact contexts
294
in which floating-point values are checked depends on the setting of other
295
options. For example,
296
@option{^-gnatVif^VALIDITY_CHECKING=(IN_PARAMS,FLOATS)^} or
297
@@ -6146,7 +6147,7 @@
298
methods see @ref{Wide Character Encodings}.
299
Note that brackets coding is always accepted, even if one of the other
300
options is specified, so for example @option{-gnatW8} specifies that both
301
-brackets and @code{UTF-8} encodings will be recognized. The units that are
302
+brackets and UTF-8 encodings will be recognized. The units that are
303
with'ed directly or indirectly will be scanned using the specified
304
representation scheme, and so if one of the non-brackets scheme is
305
used, it must be used consistently throughout the program. However,
306
@@ -8762,7 +8763,7 @@
308
Using @command{gnatmake} along with the
309
@option{^-m (minimal recompilation)^/MINIMAL_RECOMPILATION^}
310
-switch provides a mechanism for avoiding unnecessary rcompilations. Using
311
+switch provides a mechanism for avoiding unnecessary recompilations. Using
313
you can update the comments/format of your
314
source files without having to recompile everything. Note, however, that
315
@@ -11429,7 +11430,7 @@
319
-Comments in project files have the same syntax as in Ada, two consecutives
320
+Comments in project files have the same syntax as in Ada, two consecutive
321
hyphens through the end of the line.
324
@@ -14085,7 +14086,7 @@
328
-The switches can be :
329
+The switches can be:
332
@item ^-a^/ALL_FILES^
333
@@ -14454,14 +14455,14 @@
335
As specified in the section about @command{gnatfind}, the pattern can be a
336
regular expression. Actually, there are to set of regular expressions
337
-which are recognized by the program :
338
+which are recognized by the program:
341
@item globbing patterns
342
These are the most usual regular expression. They are the same that you
343
generally used in a Unix shell command line, or in a DOS session.
345
-Here is a more formal grammar :
346
+Here is a more formal grammar:
350
@@ -14472,7 +14473,7 @@
351
term ::= elmt elmt -- concatenation (elmt then elmt)
352
term ::= * -- any string of 0 or more characters
353
term ::= ? -- matches any character
354
-term ::= [char @{char@}] -- matches any character listed
355
+term ::= [char @{char@}] -- matches any character listed
356
term ::= [char - char] -- matches any character in range
359
@@ -14489,9 +14490,9 @@
363
-regexp ::= term @{| term@} -- alternation (term or term ...)
364
+regexp ::= term @{| term@} -- alternation (term or term ...)
366
-term ::= item @{item@} -- concatenation (item then item)
367
+term ::= item @{item@} -- concatenation (item then item)
369
item ::= elmt -- match elmt
370
item ::= elmt * -- zero or more elmt's
371
@@ -14512,7 +14513,7 @@
375
-Following are a few examples :
376
+Following are a few examples:
380
@@ -14523,7 +14524,7 @@
383
will match any string which has only lowercase characters in it (and at
385
+least one character.
389
@@ -14534,7 +14535,7 @@
390
@subsection General Usage
393
-For the following examples, we will consider the following units :
394
+For the following examples, we will consider the following units:
398
@@ -14630,9 +14631,9 @@
399
@subsection Using gnatxref with vi
401
@code{gnatxref} can generate a tags file output, which can be used
402
-directly from @file{vi}. Note that the standard version of @file{vi}
403
+directly from @command{vi}. Note that the standard version of @command{vi}
404
will not work properly with overloaded symbols. Consider using another
405
-free implementation of @file{vi}, such as @file{vim}.
406
+free implementation of @command{vi}, such as @command{vim}.
409
$ gnatxref -v gnatfind.adb > tags
410
@@ -14642,7 +14643,7 @@
411
will generate the tags file for @code{gnatfind} itself (if the sources
412
are in the search path!).
414
-From @file{vi}, you can then use the command @samp{:tag @i{entity}}
415
+From @command{vi}, you can then use the command @samp{:tag @i{entity}}
416
(replacing @i{entity} by whatever you are looking for), and vi will
417
display a new file with the corresponding declaration of entity.
419
@@ -17920,7 +17921,7 @@
421
# The directories for the libraries
422
# (This macro expands the list of CSC to the list of shared libraries, you
423
-# could simply use the expanded form :
424
+# could simply use the expanded form:
425
# LIB_DIR=aa/lib/libaa.so bb/lib/libbb.so cc/lib/libcc.so
426
LIB_DIR=$@{foreach dir,$@{CSC_LIST@},$@{dir@}/lib/lib$@{dir@}.so@}
428
@@ -19481,7 +19482,7 @@
429
an html file for every ada file, and a global file called @file{index.htm}.
430
This file is an index of every identifier defined in the files.
432
-The available ^switches^options^ are the following ones :
433
+The available ^switches^options^ are the following ones:
437
@@ -19571,7 +19572,7 @@
439
On Unix systems, you may want to modify the first line of the script
440
@code{gnathtml}, to explicitly tell the Operating system where Perl
441
-is. The syntax of this line is :
442
+is. The syntax of this line is:
444
#!full_path_name_to_perl
446
Index: gcc/fortran/gfortran.texi
447
===================================================================
448
--- gcc/fortran/gfortran.texi (.../tags/ubuntu/gcc-4_2_3-release) (revision 134648)
449
+++ gcc/fortran/gfortran.texi (.../branches/ubuntu/gcc-4_2-branch) (revision 134648)
450
@@ -1497,7 +1497,7 @@
451
@c GNU General Public License
452
@c ---------------------------------------------------------------------
455
+@include gpl_v3.texi