Skip to content

R
riscv-gcc-1
Commit 75393169 by Joseph Myers Committed by Joseph Myers
Options

Version.c, [...]: Update G77 version number to 0.5.27. 

libf2c:
	* libF77/Version.c, libI77/Version.c, libU77/Version.c: Update G77
	version number to 0.5.27.

gcc:
	* README, cpp.texi, gcc.texi, version.c: Update version number to
	3.1.
	* cpp.1, gcov.1, gcc.1: Regenerate.

gcc/f:
	* version.c, root.texi: Update GCC version number to 3.1.  Update
	G77 version number to 0.5.27.
	* BUGS, NEWS: Regenerate.

From-SVN: r39901
parent 51d0f328
Showing with 182 additions and 108 deletions
gcc/ChangeLog
2001-02-19 Joseph S. Myers <jsm28@cam.ac.uk>
* README, cpp.texi, gcc.texi, version.c: Update version number to
3.1.
* cpp.1, gcov.1, gcc.1: Regenerate.
2001-02-19 Neil Booth <neil@daikokuya.demon.co.uk> 2001-02-19 Neil Booth <neil@daikokuya.demon.co.uk>
* cppfiles.c (stack_include_file): Generate dependencies * cppfiles.c (stack_include_file): Generate dependencies
......
gcc/README
This directory contains the GNU Compiler Collection (GCC) version 2.96. This directory contains the GNU Compiler Collection (GCC) version 3.1.
It includes all of the support for compiling C, C++, Objective C, Fortran, It includes all of the support for compiling C, C++, Objective C, Fortran,
Java, and Chill. Java, and Chill.
......
gcc/cpp.1
.\" Automatically generated by Pod::Man version 1.1 .\" Automatically generated by Pod::Man version 1.1
.\" Wed Jan 24 19:43:25 2001 .\" Mon Feb 19 19:32:17 2001
.\" .\"
.\" Standard preamble: .\" Standard preamble:
.\" ====================================================================== .\" ======================================================================
...@@ -138,7 +138,7 @@ ...@@ -138,7 +138,7 @@
.\" ====================================================================== .\" ======================================================================
.\" .\"
.IX Title "CPP 1" .IX Title "CPP 1"
.TH CPP 1 "gcc-2.97" "2001-01-24" "GNU" .TH CPP 1 "gcc-3.1" "2001-02-19" "GNU"
.UC .UC
.SH "NAME" .SH "NAME"
cpp \- The C Preprocessor cpp \- The C Preprocessor
...@@ -385,6 +385,36 @@ Requests \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR, and \fB\-Wwhite-space\fR ...@@ -385,6 +385,36 @@ Requests \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR, and \fB\-Wwhite-space\fR
.IX Item "-Wtraditional" .IX Item "-Wtraditional"
Warn about certain constructs that behave differently in traditional and Warn about certain constructs that behave differently in traditional and
\&\s-1ISO\s0 C. \&\s-1ISO\s0 C.
.RS 4
.Ip "\(bu" 4
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 \s-1ISO\s0 C.
.Ip "\(bu" 4
In traditional C, some preprocessor directives did not exist.
Traditional preprocessors would only consider a line to be a directive
if the \fB#\fR appeared in column 1 on the line. Therefore
\&\fB\-Wtraditional\fR warns about directives that traditional C
understands but would ignore because the \fB#\fR does not appear as the
first character on the line. It also suggests you hide directives like
\&\fB#pragma\fR not understood by traditional C by indenting them. Some
traditional implementations would not recognise \fB#elif\fR, so it
suggests avoiding it altogether.
.Ip "\(bu" 4
A function-like macro that appears without arguments.
.Ip "\(bu" 4
The unary plus operator.
.Ip "\(bu" 4
The `U' integer constant suffix. (Traditonal 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 can lead to spurious warnings
as they do not necessarily reflect whether the code in question is any
less portable to traditional C given that suitable backup definitions
are provided.
.RE
.RS 4
.RE
.Ip "\fB\-Wundef\fR" 4 .Ip "\fB\-Wundef\fR" 4
.IX Item "-Wundef" .IX Item "-Wundef"
Warn if an undefined identifier is evaluated in an \fB#if\fR directive. Warn if an undefined identifier is evaluated in an \fB#if\fR directive.
...@@ -510,7 +540,10 @@ suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main sour ...@@ -510,7 +540,10 @@ suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main sour
file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the
object file name for that source file, a colon, and the names of all the object file name for that source file, a colon, and the names of all the
included files, including those coming from \fB\-include\fR or included files, including those coming from \fB\-include\fR or
\&\fB\-imacros\fR command line options. If there are many included files \&\fB\-imacros\fR command line options. Unless specified explicitly (with
\&\fB\-MT\fR or \fB\-MQ\fR), the object file name consists of the basename
of the source file with any suffix replaced with object file suffix.
If there are many included files
then the rule is split into several lines using \fB\e\fR\-newline. then the rule is split into several lines using \fB\e\fR\-newline.
.Ip "\fB\-MM\fR" 4 .Ip "\fB\-MM\fR" 4
.IX Item "-MM" .IX Item "-MM"
......
gcc/cpp.texi
...@@ -43,7 +43,7 @@ into another language, under the above conditions for modified versions. ...@@ -43,7 +43,7 @@ into another language, under the above conditions for modified versions.
@c @finalout @c @finalout
@title The C Preprocessor @title The C Preprocessor
@subtitle Last revised January 2001 @subtitle Last revised January 2001
@subtitle for GCC version 2 @subtitle for GCC version 3
@author Richard M. Stallman @author Richard M. Stallman
@page @page
@vskip 2pc @vskip 2pc
......
gcc/f/BUGS
...@@ -2,17 +2,16 @@ _Note:_ This file is automatically generated from the files ...@@ -2,17 +2,16 @@ _Note:_ This file is automatically generated from the files
`bugs0.texi' and `bugs.texi'. `BUGS' is _not_ a source file, although `bugs0.texi' and `bugs.texi'. `BUGS' is _not_ a source file, although
it is normally included within source distributions. it is normally included within source distributions.
This file lists known bugs in the GCC-2.97 version of the GNU This file lists known bugs in the GCC-3.1 version of the GNU Fortran
Fortran compiler. Copyright (C) 1995,1996,1997,1998,1999,2000 Free compiler. Copyright (C) 1995,1996,1997,1998,1999,2000 Free Software
Software Foundation, Inc. You may copy, distribute, and modify it Foundation, Inc. You may copy, distribute, and modify it freely as
freely as long as you preserve this copyright notice and permission long as you preserve this copyright notice and permission notice.
notice.
Known Bugs In GNU Fortran Known Bugs In GNU Fortran
************************* *************************
This section identifies bugs that `g77' _users_ might run into in This section identifies bugs that `g77' _users_ might run into in
the GCC-2.97 version of `g77'. This includes bugs that are actually in the GCC-3.1 version of `g77'. This includes bugs that are actually in
the `gcc' back end (GBE) or in `libf2c', because those sets of code are the `gcc' back end (GBE) or in `libf2c', because those sets of code are
at least somewhat under the control of (and necessarily intertwined at least somewhat under the control of (and necessarily intertwined
with) `g77', so it isn't worth separating them out. with) `g77', so it isn't worth separating them out.
...@@ -28,8 +27,8 @@ particularly concentrated on any version of this information that is ...@@ -28,8 +27,8 @@ particularly concentrated on any version of this information that is
distributed as part of a _released_ `g77'. distributed as part of a _released_ `g77'.
In particular, while this information is intended to apply to the In particular, while this information is intended to apply to the
GCC-2.97 version of `g77', only an official _release_ of that version GCC-3.1 version of `g77', only an official _release_ of that version is
is expected to contain documentation that is most consistent with the expected to contain documentation that is most consistent with the
`g77' product in that version. `g77' product in that version.
An online, "live" version of this document (derived directly from An online, "live" version of this document (derived directly from
......
gcc/f/ChangeLog
2001-02-19 Joseph S. Myers <jsm28@cam.ac.uk>
* version.c, root.texi: Update GCC version number to 3.1. Update
G77 version number to 0.5.27.
* BUGS, NEWS: Regenerate.
Sun Feb 4 15:52:44 2001 Richard Kenner <kenner@vlsi1.ultra.nyu.edu> Sun Feb 4 15:52:44 2001 Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
* com.c (ffecom_init_0): Call fatal_error instead of fatal. * com.c (ffecom_init_0): Call fatal_error instead of fatal.
......
gcc/f/NEWS
...@@ -2,7 +2,7 @@ _Note:_ This file is automatically generated from the files ...@@ -2,7 +2,7 @@ _Note:_ This file is automatically generated from the files
`news0.texi' and `news.texi'. `NEWS' is _not_ a source file, although `news0.texi' and `news.texi'. `NEWS' is _not_ a source file, although
it is normally included within source distributions. it is normally included within source distributions.
This file lists news about the GCC-2.97 version (and some other This file lists news about the GCC-3.1 version (and some other
versions) of the GNU Fortran compiler. Copyright (C) versions) of the GNU Fortran compiler. Copyright (C)
1995,1996,1997,1998,1999,2000 Free Software Foundation, Inc. You may 1995,1996,1997,1998,1999,2000 Free Software Foundation, Inc. You may
copy, distribute, and modify it freely as long as you preserve this copy, distribute, and modify it freely as long as you preserve this
...@@ -52,8 +52,8 @@ particularly concentrated on any version of this information that is ...@@ -52,8 +52,8 @@ particularly concentrated on any version of this information that is
distributed as part of a _released_ `g77'. distributed as part of a _released_ `g77'.
In particular, while this information is intended to apply to the In particular, while this information is intended to apply to the
GCC-2.97 version of `g77', only an official _release_ of that version GCC-3.1 version of `g77', only an official _release_ of that version is
is expected to contain documentation that is most consistent with the expected to contain documentation that is most consistent with the
`g77' product in that version. `g77' product in that version.
Nevertheless, information on _previous_ releases of `g77', below, is Nevertheless, information on _previous_ releases of `g77', below, is
......
gcc/f/root.texi
...@@ -3,8 +3,8 @@ ...@@ -3,8 +3,8 @@
@c (e.g. a release branch in the CVS repository for gcc), @c (e.g. a release branch in the CVS repository for gcc),
@c clear this and set the version information correctly. @c clear this and set the version information correctly.
@set DEVELOPMENT @set DEVELOPMENT
@set version-g77 0.5.26 @set version-g77 0.5.27
@set version-gcc 2.97 @set version-gcc 3.1
@set email-general gcc@@gcc.gnu.org @set email-general gcc@@gcc.gnu.org
@set email-bugs gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org @set email-bugs gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org
......
gcc/f/version.c
const char *ffe_version_string = "0.5.26 20010219 (experimental)"; const char *ffe_version_string = "0.5.27 20010219 (experimental)";
gcc/gcc.1
.\" Automatically generated by Pod::Man version 1.1 .\" Automatically generated by Pod::Man version 1.1
.\" Wed Jan 24 19:43:11 2001 .\" Mon Feb 19 19:32:03 2001
.\" .\"
.\" Standard preamble: .\" Standard preamble:
.\" ====================================================================== .\" ======================================================================
...@@ -138,7 +138,7 @@ ...@@ -138,7 +138,7 @@
.\" ====================================================================== .\" ======================================================================
.\" .\"
.IX Title "GCC 1" .IX Title "GCC 1"
.TH GCC 1 "gcc-2.97" "2001-01-24" "GNU" .TH GCC 1 "gcc-3.1" "2001-02-19" "GNU"
.UC .UC
.SH "NAME" .SH "NAME"
gcc \- \s-1GNU\s0 project C and \*(C+ compiler gcc \- \s-1GNU\s0 project C and \*(C+ compiler
...@@ -217,9 +217,9 @@ in the following sections. ...@@ -217,9 +217,9 @@ in the following sections.
\&\-fhuge-objects \-fno-implicit-templates \&\-fhuge-objects \-fno-implicit-templates
\&\-fno-implicit-inline-templates \&\-fno-implicit-inline-templates
\&\-fno-implement-inlines \-fms-extensions \&\-fno-implement-inlines \-fms-extensions
\&\-fname-mangling-version-\fR\fIn\fR \fB\-fno-operator-names \&\-fno-operator-names
\&\-fno-optional-diags \-fpermissive \&\-fno-optional-diags \-fpermissive
\&\-frepo \-fno-rtti \-fsquangle \-ftemplate-depth-\fR\fIn\fR \&\-frepo \-fno-rtti \-ftemplate-depth-\fR\fIn\fR
\&\fB\-fuse-cxa-atexit \-fvtable-thunks \-nostdinc++ \&\fB\-fuse-cxa-atexit \-fvtable-thunks \-nostdinc++
\&\-fno-default-inline \-Wctor-dtor-privacy \&\-fno-default-inline \-Wctor-dtor-privacy
\&\-Wnon-virtual-dtor \-Wreorder \&\-Wnon-virtual-dtor \-Wreorder
...@@ -261,8 +261,8 @@ in the following sections. ...@@ -261,8 +261,8 @@ in the following sections.
\&\-Wstrict-prototypes \-Wtraditional\fR \&\-Wstrict-prototypes \-Wtraditional\fR
.Ip "\fIDebugging Options\fR" 4 .Ip "\fIDebugging Options\fR" 4
.IX Item "Debugging Options" .IX Item "Debugging Options"
\&\fB\-a \-ax \-d\fR\fIletters\fR \fB\-fdump-unnumbered \-fdump-translation-unit-\fR\fIfile\fR \&\fB\-a \-ax \-d\fR\fIletters\fR \fB\-fdump-unnumbered \-fdump-translation-unit=\fR\fIfile\fR
\&\fB\-fpretend-float \-fprofile-arcs \-ftest-coverage \&\fB\-fdump-class-layout=\fR\fIfile\fR \fB\-fpretend-float \-fprofile-arcs \-ftest-coverage
\&\-g \-g\fR\fIlevel\fR \fB\-gcoff \-gdwarf \-gdwarf-1 \-gdwarf-1+ \-gdwarf-2 \&\-g \-g\fR\fIlevel\fR \fB\-gcoff \-gdwarf \-gdwarf-1 \-gdwarf-1+ \-gdwarf-2
\&\-ggdb \-gstabs \-gstabs+ \-gxcoff \-gxcoff+ \&\-ggdb \-gstabs \-gstabs+ \-gxcoff \-gxcoff+
\&\-p \-pg \-print-file-name=\fR\fIlibrary\fR \fB\-print-libgcc-file-name \&\-p \-pg \-print-file-name=\fR\fIlibrary\fR \fB\-print-libgcc-file-name
...@@ -290,7 +290,8 @@ in the following sections. ...@@ -290,7 +290,8 @@ in the following sections.
\&\-fsingle-precision-constant \-fssa \&\-fsingle-precision-constant \-fssa
\&\-fstrength-reduce \-fstrict-aliasing \-fthread-jumps \-ftrapv \&\-fstrength-reduce \-fstrict-aliasing \-fthread-jumps \-ftrapv
\&\-funroll-all-loops \-funroll-loops \&\-funroll-all-loops \-funroll-loops
\&\-O \-O0 \-O1 \-O2 \-O3 \-Os\fR \&\-\-param\fR \fIname\fR\fB=\fR\fIvalue\fR
\&\fB\-O \-O0 \-O1 \-O2 \-O3 \-Os\fR
.Ip "\fIPreprocessor Options\fR" 4 .Ip "\fIPreprocessor Options\fR" 4
.IX Item "Preprocessor Options" .IX Item "Preprocessor Options"
\&\fB\-$ \-A\fR\fIquestion\fR\fB=\fR\fIanswer\fR \fB\-A-\fR\fIquestion\fR[\fB=\fR\fIanswer\fR] \&\fB\-$ \-A\fR\fIquestion\fR\fB=\fR\fIanswer\fR \fB\-A-\fR\fIquestion\fR[\fB=\fR\fIanswer\fR]
...@@ -482,12 +483,11 @@ in the following sections. ...@@ -482,12 +483,11 @@ in the following sections.
\&\fB\-mintel-syntax \-mieee-fp \-mno-fancy-math-387 \&\fB\-mintel-syntax \-mieee-fp \-mno-fancy-math-387
\&\-mno-fp-ret-in-387 \-msoft-float \-msvr3\-shlib \&\-mno-fp-ret-in-387 \-msoft-float \-msvr3\-shlib
\&\-mno-wide-multiply \-mrtd \-malign-double \&\-mno-wide-multiply \-mrtd \-malign-double
\&\-mreg-alloc=\fR\fIlist\fR \fB\-mregparm=\fR\fInum\fR \&\-malign-jumps=\fR\fInum\fR \fB\-malign-loops=\fR\fInum\fR
\&\fB\-malign-jumps=\fR\fInum\fR \fB\-malign-loops=\fR\fInum\fR
\&\fB\-malign-functions=\fR\fInum\fR \fB\-mpreferred-stack-boundary=\fR\fInum\fR \&\fB\-malign-functions=\fR\fInum\fR \fB\-mpreferred-stack-boundary=\fR\fInum\fR
\&\fB\-mthreads \-mno-align-stringops \-minline-all-stringops \&\fB\-mthreads \-mno-align-stringops \-minline-all-stringops
\&\-mpush-args \-maccumulate-outgoing-args \-m128bit-long-double \&\-mpush-args \-maccumulate-outgoing-args \-m128bit-long-double
\&\-m96bit-long-double\fR \&\-m96bit-long-double \-mregparm=\fR\fInum\fR
.Sp .Sp
\&\fI\s-1HPPA\s0 Options\fR \&\fI\s-1HPPA\s0 Options\fR
.Sp .Sp
...@@ -1246,19 +1246,6 @@ errors if these functions are not inlined everywhere they are called. ...@@ -1246,19 +1246,6 @@ errors if these functions are not inlined everywhere they are called.
.IX Item "-fms-extensions" .IX Item "-fms-extensions"
Disable pedantic warnings about constructs used in \s-1MFC\s0, such as implicit Disable pedantic warnings about constructs used in \s-1MFC\s0, such as implicit
int and getting a pointer to member function via non-standard syntax. int and getting a pointer to member function via non-standard syntax.
.Ip "\fB\-fname-mangling-version-\fR\fIn\fR" 4
.IX Item "-fname-mangling-version-n"
Control the way in which names are mangled. Version 0 is compatible
with versions of g++ before 2.8. Version 1 is the default. Version 1
will allow correct mangling of function templates. For example,
version 0 mangling does not mangle foo<int, double> and foo<int, char>
given this declaration:
.Sp
.Vb 1
\& template <class T, class U> void foo(T t);
.Ve
Like all options that change the \s-1ABI\s0, all \*(C+ code, \fIincluding
libgcc\fR must be built with the same setting of this option.
.Ip "\fB\-fno-operator-names\fR" 4 .Ip "\fB\-fno-operator-names\fR" 4
.IX Item "-fno-operator-names" .IX Item "-fno-operator-names"
Do not treat the operator name keywords \f(CW\*(C`and\*(C'\fR, \f(CW\*(C`bitand\*(C'\fR, Do not treat the operator name keywords \f(CW\*(C`and\*(C'\fR, \f(CW\*(C`bitand\*(C'\fR,
...@@ -1287,21 +1274,6 @@ functions for use by the \*(C+ runtime type identification features ...@@ -1287,21 +1274,6 @@ functions for use by the \*(C+ runtime type identification features
of the language, you can save some space by using this flag. Note that of the language, you can save some space by using this flag. Note that
exception handling uses the same information, but it will generate it as exception handling uses the same information, but it will generate it as
needed. needed.
.Ip "\fB\-fsquangle\fR" 4
.IX Item "-fsquangle"
.PD 0
.Ip "\fB\-fno-squangle\fR" 4
.IX Item "-fno-squangle"
.PD
\&\fB\-fsquangle\fR will enable a compressed form of name mangling for
identifiers. In particular, it helps to shorten very long names by recognizing
types and class names which occur more than once, replacing them with special
short \s-1ID\s0 codes. This option also requires any \*(C+ libraries being used to
be compiled with this option as well. The compiler has this disabled (the
equivalent of \fB\-fno-squangle\fR) by default.
.Sp
Like all options that change the \s-1ABI\s0, all \*(C+ code, \fIincluding
libgcc.a\fR must be built with the same setting of this option.
.Ip "\fB\-ftemplate-depth-\fR\fIn\fR" 4 .Ip "\fB\-ftemplate-depth-\fR\fIn\fR" 4
.IX Item "-ftemplate-depth-n" .IX Item "-ftemplate-depth-n"
Set the maximum instantiation depth for template classes to \fIn\fR. Set the maximum instantiation depth for template classes to \fIn\fR.
...@@ -1402,13 +1374,27 @@ new-style casts (\fBstatic_cast\fR, \fBreinterpret_cast\fR, and ...@@ -1402,13 +1374,27 @@ new-style casts (\fBstatic_cast\fR, \fBreinterpret_cast\fR, and
\&\fBconst_cast\fR) are less vulnerable to unintended effects. \&\fBconst_cast\fR) are less vulnerable to unintended effects.
.Ip "\fB\-Woverloaded-virtual (\*(C+ only)\fR" 4 .Ip "\fB\-Woverloaded-virtual (\*(C+ only)\fR" 4
.IX Item "-Woverloaded-virtual ( only)" .IX Item "-Woverloaded-virtual ( only)"
Warn when a derived class function declaration may be an error in Warn when a function declaration hides virtual functions from a
defining a virtual function. In a derived class, the base class. For example, in:
definitions of virtual functions must match the type signature of a .Sp
virtual function declared in the base class. With this option, the .Vb 3
compiler warns when you define a function with the same name as a \& struct A {
virtual function, but with a type signature that does not match any \& virtual void f();
declarations from the base class. \& };
.Ve
.Vb 3
\& struct B: public A {
\& void f(int);
\& };
.Ve
the \f(CW\*(C`A\*(C'\fR class version of \f(CW\*(C`f\*(C'\fR is hidden in \f(CW\*(C`B\*(C'\fR, and code
like this:
.Sp
.Vb 2
\& B* b;
\& b->f();
.Ve
will fail to compile.
.Ip "\fB\-Wno-pmf-conversions (\*(C+ only)\fR" 4 .Ip "\fB\-Wno-pmf-conversions (\*(C+ only)\fR" 4
.IX Item "-Wno-pmf-conversions ( only)" .IX Item "-Wno-pmf-conversions ( only)"
Disable the diagnostic for converting a bound pointer to member function Disable the diagnostic for converting a bound pointer to member function
...@@ -1941,9 +1927,31 @@ Warn about certain constructs that behave differently in traditional and ...@@ -1941,9 +1927,31 @@ Warn about certain constructs that behave differently in traditional and
\&\s-1ISO\s0 C. \&\s-1ISO\s0 C.
.RS 4 .RS 4
.Ip "\(bu" 4 .Ip "\(bu" 4
Macro arguments occurring within string constants in the macro body. Macro parameters that appear within string literals in the macro body.
These would substitute the argument in traditional C, but are part of In traditional C macro replacement takes place within string literals,
the constant in \s-1ISO\s0 C. but does not in \s-1ISO\s0 C.
.Ip "\(bu" 4
In traditional C, some preprocessor directives did not exist.
Traditional preprocessors would only consider a line to be a directive
if the \fB#\fR appeared in column 1 on the line. Therefore
\&\fB\-Wtraditional\fR warns about directives that traditional C
understands but would ignore because the \fB#\fR does not appear as the
first character on the line. It also suggests you hide directives like
\&\fB#pragma\fR not understood by traditional C by indenting them. Some
traditional implementations would not recognise \fB#elif\fR, so it
suggests avoiding it altogether.
.Ip "\(bu" 4
A function-like macro that appears without arguments.
.Ip "\(bu" 4
The unary plus operator.
.Ip "\(bu" 4
The `U' integer constant suffix, or the `F' or `L' floating point
constant suffixes. (Traditonal 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 can lead to spurious warnings as they do not
necessarily reflect whether the code in question is any less portable to
traditional C given that suitable backup definitions are provided.
.Ip "\(bu" 4 .Ip "\(bu" 4
A function declared external in one block and then used after the end of A function declared external in one block and then used after the end of
the block. the block.
...@@ -1960,10 +1968,6 @@ typically represent bit patterns, are not warned about. ...@@ -1960,10 +1968,6 @@ typically represent bit patterns, are not warned about.
.Ip "\(bu" 4 .Ip "\(bu" 4
Usage of \s-1ISO\s0 string concatenation is detected. Usage of \s-1ISO\s0 string concatenation is detected.
.Ip "\(bu" 4 .Ip "\(bu" 4
A function macro appears without arguments.
.Ip "\(bu" 4
The unary plus operator.
.Ip "\(bu" 4
Initialization of automatic aggregates. Initialization of automatic aggregates.
.Ip "\(bu" 4 .Ip "\(bu" 4
Identifier conflicts with labels. Traditional C lacks a separate Identifier conflicts with labels. Traditional C lacks a separate
...@@ -1974,14 +1978,6 @@ omitted. This is done under the assumption that the zero initializer in ...@@ -1974,14 +1978,6 @@ omitted. This is done under the assumption that the zero initializer in
user code appears conditioned on e.g. \f(CW\*(C`_\|_STDC_\|_\*(C'\fR to avoid missing user code appears conditioned on e.g. \f(CW\*(C`_\|_STDC_\|_\*(C'\fR to avoid missing
initializer warnings and relies on default initialization to zero in the initializer warnings and relies on default initialization to zero in the
traditional C case. traditional C case.
.Ip "\(bu" 4
The `U' integer constant suffix, or the `F' or `L' floating point
constant suffixes. (Traditonal 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 can lead to spurious warnings as they do not
necessarily reflect whether the code in question is any less portable to
traditional C given that suitable backup definitions are provided.
.RE .RE
.RS 4 .RS 4
.RE .RE
...@@ -2572,10 +2568,18 @@ When doing debugging dumps (see \-d option above), suppress instruction ...@@ -2572,10 +2568,18 @@ When doing debugging dumps (see \-d option above), suppress instruction
numbers and line number note output. This makes it more feasible to numbers and line number note output. This makes it more feasible to
use diff on debugging dumps for compiler invocations with different use diff on debugging dumps for compiler invocations with different
options, in particular with and without \-g. options, in particular with and without \-g.
.Ip "\fB\-fdump-translation-unit-\fR\fIfile\fR \fB(C and \*(C+ only)\fR" 4 .Ip "\fB\-fdump-translation-unit=\fR\fIfile\fR \fB(C and \*(C+ only)\fR" 4
.IX Item "-fdump-translation-unit-file (C and only)" .IX Item "-fdump-translation-unit=file (C and only)"
Dump a representation of the tree structure for the entire translation Dump a representation of the tree structure for the entire translation
unit to \fIfile\fR. unit to \fIfile\fR.
.Ip "\fB\-fdump-class_layout=\fR\fIfile\fR \fB(\*(C+ only)\fR" 4
.IX Item "-fdump-class_layout=file ( only)"
.PD 0
.Ip "\fB\-fdump-class_layout (\*(C+ only)\fR" 4
.IX Item "-fdump-class_layout ( only)"
.PD
Dump a representation of each class's heirarchy to \fIfile\fR, or
\&\f(CW\*(C`stderr\*(C'\fR if not specified.
.Ip "\fB\-fpretend-float\fR" 4 .Ip "\fB\-fpretend-float\fR" 4
.IX Item "-fpretend-float" .IX Item "-fpretend-float"
When running a cross-compiler, pretend that the target machine uses the When running a cross-compiler, pretend that the target machine uses the
...@@ -3130,6 +3134,25 @@ of registers left over after register allocation. This optimization ...@@ -3130,6 +3134,25 @@ of registers left over after register allocation. This optimization
will most benefit processors with lots of registers. It can, however, will most benefit processors with lots of registers. It can, however,
make debugging impossible, since variables will no longer stay in make debugging impossible, since variables will no longer stay in
a ``home register''. a ``home register''.
.Ip "\fB\*(--param\fR \fIname\fR\fB=\fR\fIvalue\fR" 4
.IX Item "param name=value"
In some places, \s-1GCC\s0 uses various constants to control the amount of
optimization that is done. For example, \s-1GCC\s0 will not inline functions
that contain more that a certain number of instructions. You can
control some of these constants on the command-line using the
\&\fB\*(--param\fR option.
.Sp
In each case, the \fIvalue\fR is a integer. The allowable choices for
\&\fIname\fR are given in the following table:
.RS 4
.Ip "\fBmax-inline-insns\fR" 4
.IX Item "max-inline-insns"
If an function contains more than this many instructions, it
will not be inlined. This option is precisely equivalent to
\&\fB\-finline-limit\fR.
.RE
.RS 4
.RE
.Sh "Options Controlling the Preprocessor" .Sh "Options Controlling the Preprocessor"
.IX Subsection "Options Controlling the Preprocessor" .IX Subsection "Options Controlling the Preprocessor"
These options control the C preprocessor, which is run on each C source These options control the C preprocessor, which is run on each C source
...@@ -3220,8 +3243,10 @@ Instead of outputting the result of preprocessing, output a rule ...@@ -3220,8 +3243,10 @@ Instead of outputting the result of preprocessing, output a rule
suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main source suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main source
file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the
object file name for that source file, a colon, and the names of all the object file name for that source file, a colon, and the names of all the
included files. If there are many included files then the rule is split included files. Unless overridden explicitly, the object file name
into several lines using \fB\e\fR\-newline. consists of the basename of the source file with any suffix replaced with
object file suffix. If there are many included files then the
rule is split into several lines using \fB\e\fR\-newline.
.Sp .Sp
\&\fB\-M\fR implies \fB\-E\fR. \&\fB\-M\fR implies \fB\-E\fR.
.Ip "\fB\-MM\fR" 4 .Ip "\fB\-MM\fR" 4
...@@ -3528,11 +3553,16 @@ of these is when the application wishes to throw and catch exceptions ...@@ -3528,11 +3553,16 @@ of these is when the application wishes to throw and catch exceptions
across different shared libraries. In that case, each of the libraries across different shared libraries. In that case, each of the libraries
as well as the application itself should use the shared \fIlibgcc\fR. as well as the application itself should use the shared \fIlibgcc\fR.
.Sp .Sp
At present the \s-1GCC\s0 driver makes no attempt to recognize the situations Therefore, whenever you specify the \fB\-shared\fR option, the \s-1GCC\s0
in which the shared \fIlibgcc\fR should be used, and defaults to using driver automatically adds \fB\-shared-libgcc\fR, unless you explicitly
the static \fIlibgcc\fR always. This will likely change in the future, specify \fB\-static-libgcc\fR. The G++ driver automatically adds
at which time \fB\-static-libgcc\fR becomes useful as a means for \&\fB\-shared-libgcc\fR when you build a main executable as well because
overriding \s-1GCC\s0's choice. for \*(C+ programs that is typically the right thing to do.
(Exception-handling will not work reliably otherwise.)
.Sp
However, when linking a main executable written in C, you must
explicitly say \fB\-shared-libgcc\fR if you want to use the shared
\&\fIlibgcc\fR.
.Ip "\fB\-symbolic\fR" 4 .Ip "\fB\-symbolic\fR" 4
.IX Item "-symbolic" .IX Item "-symbolic"
Bind references to global symbols when building a shared object. Warn Bind references to global symbols when building a shared object. Warn
...@@ -3569,8 +3599,10 @@ libraries and for parts of the compiler: ...@@ -3569,8 +3599,10 @@ libraries and for parts of the compiler:
Add the directory \fIdir\fR to the head of the list of directories to be Add the directory \fIdir\fR to the head of the list of directories to be
searched for header files. This can be used to override a system header searched for header files. This can be used to override a system header
file, substituting your own version, since these directories are file, substituting your own version, since these directories are
searched before the system header file directories. If you use more searched before the system header file directories. However, you should
than one \fB\-I\fR option, the directories are scanned in left-to-right not use this option to add directories that contain vendor-supplied
system header files (use \fB\-isystem\fR for that). If you use more than
one \fB\-I\fR option, the directories are scanned in left-to-right
order; the standard system directories come after. order; the standard system directories come after.
.Ip "\fB\-I-\fR" 4 .Ip "\fB\-I-\fR" 4
.IX Item "-I-" .IX Item "-I-"
...@@ -5963,13 +5995,6 @@ functions. ...@@ -5963,13 +5995,6 @@ functions.
In addition, seriously incorrect code will result if you call a In addition, seriously incorrect code will result if you call a
function with too many arguments. (Normally, extra arguments are function with too many arguments. (Normally, extra arguments are
harmlessly ignored.) harmlessly ignored.)
.Ip "\fB\-mreg-alloc=\fR\fIregs\fR" 4
.IX Item "-mreg-alloc=regs"
Control the default allocation order of integer registers. The
string \fIregs\fR is a series of letters specifying a register. The
supported letters are: \f(CW\*(C`a\*(C'\fR allocate \s-1EAX\s0; \f(CW\*(C`b\*(C'\fR allocate \s-1EBX\s0;
\&\f(CW\*(C`c\*(C'\fR allocate \s-1ECX\s0; \f(CW\*(C`d\*(C'\fR allocate \s-1EDX\s0; \f(CW\*(C`S\*(C'\fR allocate \s-1ESI\s0;
\&\f(CW\*(C`D\*(C'\fR allocate \s-1EDI\s0; \f(CW\*(C`B\*(C'\fR allocate \s-1EBP\s0.
.Ip "\fB\-mregparm=\fR\fInum\fR" 4 .Ip "\fB\-mregparm=\fR\fInum\fR" 4
.IX Item "-mregparm=num" .IX Item "-mregparm=num"
Control how many registers are used to pass integer arguments. By Control how many registers are used to pass integer arguments. By
......
gcc/gcc.texi
...@@ -170,13 +170,13 @@ instead of in the original English. ...@@ -170,13 +170,13 @@ instead of in the original English.
@sp 1 @sp 1
@c The version number appears five times more in this file. @c The version number appears five times more in this file.
@center for gcc-2.97 @center for gcc-3.1
@page @page
@vskip 0pt plus 1filll @vskip 0pt plus 1filll
Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998, Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998,
1999, 2000, 2001 Free Software Foundation, Inc. 1999, 2000, 2001 Free Software Foundation, Inc.
@sp 2 @sp 2
For GCC Version 2.97@* For GCC Version 3.1@*
@sp 1 @sp 1
Published by the Free Software Foundation @* Published by the Free Software Foundation @*
59 Temple Place - Suite 330@* 59 Temple Place - Suite 330@*
...@@ -213,19 +213,19 @@ instead of in the original English. ...@@ -213,19 +213,19 @@ instead of in the original English.
@ifset USING @ifset USING
This manual documents how to run, install and port the GNU This manual documents how to run, install and port the GNU
compiler, as well as its new features and incompatibilities, and how to compiler, as well as its new features and incompatibilities, and how to
report bugs. It corresponds to GCC version 2.97. report bugs. It corresponds to GCC version 3.1.
@end ifset @end ifset
@end ifset @end ifset
@ifclear INTERNALS @ifclear INTERNALS
This manual documents how to run and install the GNU compiler, This manual documents how to run and install the GNU compiler,
as well as its new features and incompatibilities, and how to report as well as its new features and incompatibilities, and how to report
bugs. It corresponds to GCC version 2.97. bugs. It corresponds to GCC version 3.1.
@end ifclear @end ifclear
@ifclear USING @ifclear USING
This manual documents how to port the GNU compiler, This manual documents how to port the GNU compiler,
as well as its new features and incompatibilities, and how to report as well as its new features and incompatibilities, and how to report
bugs. It corresponds to GCC version 2.97. bugs. It corresponds to GCC version 3.1.
@end ifclear @end ifclear
@menu @menu
......
gcc/gcov.1
.\" Automatically generated by Pod::Man version 1.1 .\" Automatically generated by Pod::Man version 1.1
.\" Wed Jan 3 20:06:14 2001 .\" Mon Feb 19 19:31:56 2001
.\" .\"
.\" Standard preamble: .\" Standard preamble:
.\" ====================================================================== .\" ======================================================================
...@@ -138,7 +138,7 @@ ...@@ -138,7 +138,7 @@
.\" ====================================================================== .\" ======================================================================
.\" .\"
.IX Title "GCOV 1" .IX Title "GCOV 1"
.TH GCOV 1 "gcc-2.97" "2001-01-03" "GNU" .TH GCOV 1 "gcc-3.1" "2001-02-19" "GNU"
.UC .UC
.SH "NAME" .SH "NAME"
gcov \- coverage testing tool gcov \- coverage testing tool
......
gcc/version.c
#include "gansidecl.h" #include "gansidecl.h"
#include "version.h" #include "version.h"
const char *const version_string = "2.97 20010219 (experimental)"; const char *const version_string = "3.1 20010219 (experimental)";
libf2c/ChangeLog
2001-02-19 Joseph S. Myers <jsm28@cam.ac.uk>
* libF77/Version.c, libI77/Version.c, libU77/Version.c: Update G77
version number to 0.5.27.
2001-02-08 Geoffrey Keating <geoffk@redhat.com> 2001-02-08 Geoffrey Keating <geoffk@redhat.com>
* configure.in: Don't run AC_PROG_CC_WORKS, because * configure.in: Don't run AC_PROG_CC_WORKS, because
......
libf2c/libF77/Version.c
...@@ -3,7 +3,7 @@ static char junk[] = "\n@(#)LIBF77 VERSION 20000929\n"; ...@@ -3,7 +3,7 @@ static char junk[] = "\n@(#)LIBF77 VERSION 20000929\n";
/* /*
*/ */
char __G77_LIBF77_VERSION__[] = "0.5.26 20010219 (experimental)"; char __G77_LIBF77_VERSION__[] = "0.5.27 20010219 (experimental)";
/* /*
2.00 11 June 1980. File version.c added to library. 2.00 11 June 1980. File version.c added to library.
......
libf2c/libI77/Version.c
...@@ -3,7 +3,7 @@ static char junk[] = "\n@(#) LIBI77 VERSION pjw,dmg-mods 20001205\n"; ...@@ -3,7 +3,7 @@ static char junk[] = "\n@(#) LIBI77 VERSION pjw,dmg-mods 20001205\n";
/* /*
*/ */
char __G77_LIBI77_VERSION__[] = "0.5.26 20010219 (experimental)"; char __G77_LIBI77_VERSION__[] = "0.5.27 20010219 (experimental)";
/* /*
2.01 $ format added 2.01 $ format added
......
libf2c/libU77/Version.c
static char junk[] = "\n@(#) LIBU77 VERSION 19980709\n"; static char junk[] = "\n@(#) LIBU77 VERSION 19980709\n";
char __G77_LIBU77_VERSION__[] = "0.5.26 20010219 (experimental)"; char __G77_LIBU77_VERSION__[] = "0.5.27 20010219 (experimental)";
#include <stdio.h> #include <stdio.h>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment