Index: bugreport.texi =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/doc/bugreport.texi,v retrieving revision 1.2.22.1 diff -u -r1.2.22.1 bugreport.texi --- bugreport.texi 24 Jan 2003 15:52:51 -0000 1.2.22.1 +++ bugreport.texi 6 Apr 2003 23:03:55 -0000 @@ -103,6 +103,7 @@ @section Where to Report Bugs @cindex bug report mailing lists @kindex gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org + Send bug reports for the GNU Compiler Collection to @email{gcc-bugs@@gcc.gnu.org}. In accordance with the GNU-wide convention, in which bug reports for tool ``foo'' are sent Index: extend.texi =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/doc/extend.texi,v retrieving revision 1.109.2.7 diff -u -r1.109.2.7 extend.texi --- extend.texi 3 Apr 2003 20:25:01 -0000 1.109.2.7 +++ extend.texi 6 Apr 2003 23:03:59 -0000 @@ -486,7 +486,6 @@ @c the above section title wrapped and causes an underfull hbox.. i @c changed it from "within" to "in". --mew 4feb93 - A compound statement enclosed in parentheses may appear as an expression in GNU address@hidden This allows you to use loops, switches, and local variables within an expression. @@ -1033,6 +1032,7 @@ @cindex lvalues, generalized @cindex extensions, @code{?:} @cindex @code{?:} extensions + Compound expressions, conditional expressions and casts are allowed as lvalues provided their operands are lvalues. This means that you can take their addresses or store values into them. @@ -7188,7 +7188,6 @@ @node Template Instantiation @section Where's the Template? - @cindex template instantiation C++ templates are the first language feature to require more @@ -7334,7 +7333,6 @@ @node Bound member functions @section Extracting the function pointer from a bound pointer to member function - @cindex pmf @cindex pointer to member function @cindex bound pointer to member function Index: gcov.texi =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/doc/gcov.texi,v retrieving revision 1.11.14.2 diff -u -r1.11.14.2 gcov.texi --- gcov.texi 4 Feb 2003 01:55:36 -0000 1.11.14.2 +++ gcov.texi 6 Apr 2003 23:03:59 -0000 @@ -194,14 +194,15 @@ @end table -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 @address@hidden in the -current directory. These contain the coverage information of the source -file they correspond to. One @file{.gcov} file is produced for each -source file containing code, which was compiled to produce the data -files. The @file{.gcov} files contain the ':' separated fields along -with program source code. The format is address@hidden 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. @command{gcov} produces files called address@hidden@var{mangledname}.gcov} in the current directory. These contain +the coverage information of the source file they correspond to. +One @file{.gcov} file is produced for each source file containing code, +which was compiled to produce the data files. The @file{.gcov} files +contain the ':' separated fields along with program source code. The +format is @smallexample @var{execution_count}:@var{line_number}:@var{source line text} Index: invoke.texi =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/doc/invoke.texi,v retrieving revision 1.209.2.20 diff -u -r1.209.2.20 invoke.texi --- invoke.texi 2 Apr 2003 07:14:29 -0000 1.209.2.20 +++ invoke.texi 6 Apr 2003 23:04:05 -0000 @@ -66,7 +66,6 @@ @cindex options, GCC command @c man begin DESCRIPTION - 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 @option{-c} option @@ -4837,6 +4836,7 @@ @node Spec Files @section Specifying subprocesses and the switches to pass to them @cindex Spec Files + @command{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 @@ -6277,6 +6277,7 @@ @node MN10200 Options @subsection MN10200 Options @cindex MN10200 options + These @option{-m} options are defined for Matsushita MN10200 architectures: @table @gcctabopt @@ -6292,6 +6293,7 @@ @node MN10300 Options @subsection MN10300 Options @cindex MN10300 options + These @option{-m} options are defined for Matsushita MN10300 architectures: @table @gcctabopt @@ -7230,6 +7232,10 @@ @node Darwin Options @subsection Darwin Options @cindex Darwin options + +These options are defined for operating systems running the Darwin operating +system. These are useful for compatibility with other Mac OS compilers. + @table @gcctabopt @item -all_load @opindex all_load @@ -10888,7 +10894,6 @@ @cindex environment variables @c man begin ENVIRONMENT - 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 Index: objc.texi =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/doc/objc.texi,v retrieving revision 1.7.4.1 diff -u -r1.7.4.1 objc.texi --- objc.texi 27 Jan 2003 10:25:37 -0000 1.7.4.1 +++ objc.texi 6 Apr 2003 23:04:05 -0000 @@ -25,7 +25,6 @@ @node Executing code before main, Type encoding, Objective-C, Objective-C @section @code{+load}: Executing code before main - The GNU Objective-C runtime provides a way that allows you to execute code before the execution of the program enters the @code{main} function. The code is executed on a per-class and a per-category basis,