Skip to content

R
riscv-gcc-1
Commit d9b9ee64 by Dave Love
Options

Rebuilt. 

From-SVN: r21398
parent 7935f0d5
Showing with 815 additions and 675 deletions
gcc/f/BUGS
...@@ -15,26 +15,46 @@ separating them out. ...@@ -15,26 +15,46 @@ separating them out.
For information on bugs that might afflict people who configure, For information on bugs that might afflict people who configure,
port, build, and install `g77', *Note Problems Installing::. port, build, and install `g77', *Note Problems Installing::.
* `g77''s version of `gcc', and probably `g77' itself, cannot be * `g77' sometimes crashes when compiling code containing the
reliably used with the `-O2' option (or higher) on Digital construct `CMPLX(0.)' or similar. This is a `gcc' back-end bug.
Semiconductor Alpha AXP machines. The problem is most immediately It can be worked around using `-fno-emulate-complex', though that
noticed in differences discovered by `make compare' following a might trigger other, older bugs. Compiling without optimization
bootstrap build using `-O2'. It also manifests itself as a is another work-around.
failure to compile `DATA' statements such as `DATA R/7./'
correctly; in this case, `R' might be initialized to `4.0'.
Until this bug is fixed, use only `-O1' or no optimization. Fixed in `egcs' 1.1.
* Automatic arrays aren't working on HP-UX systems, at least in
HP-UX version 10.20. Writing into them apparently causes
over-writing of statically declared data in the main program.
This probably means the arrays themselves are being
under-allocated, or pointers to them being improperly handled,
e.g. not passed to other procedures as they should be.
* Some Fortran code has been found to be miscompiled by `g77' built
on `gcc' version 2.8.1 on m68k-next-nextstep3 configurations when
using the `-O2' option. Even a C function is known to miscompile
on that configuration when using the `-O2 -funroll-loops' options.
Fixed in `egcs'.
* A code-generation bug afflicts Intel x86 targets when `-O2' is
specified compiling, for example, an old version of the `DNRM2'
routine. The x87 coprocessor stack is being mismanaged in cases
where assigned `GOTO' and `ASSIGN' are involved.
Fixed in `egcs' version 1.1.
* A compiler crash, or apparently infinite run time, can result when
compiling complicated expressions involving `COMPLEX' arithmetic
(especially multiplication).
Fixed in `egcs' version 1.1.
* Something about `g77''s straightforward handling of label * Something about `g77''s straightforward handling of label
references and definitions sometimes prevents the GBE from references and definitions sometimes prevents the GBE from
unrolling loops. Until this is solved, try inserting or removing unrolling loops. Until this is solved, try inserting or removing
`CONTINUE' statements as the terminal statement, using the `END DO' `CONTINUE' statements as the terminal statement, using the `END DO'
form instead, and so on. (Probably improved, but not wholly form instead, and so on.
fixed, in 0.5.21.)
* The `g77' command itself should more faithfully process options
the way the `gcc' command does. For example, `gcc' accepts
abbreviated forms of long options, `g77' generally doesn't.
* Some confusion in diagnostics concerning failing `INCLUDE' * Some confusion in diagnostics concerning failing `INCLUDE'
statements from within `INCLUDE''d or `#include''d files. statements from within `INCLUDE''d or `#include''d files.
...@@ -117,37 +137,12 @@ port, build, and install `g77', *Note Problems Installing::. ...@@ -117,37 +137,12 @@ port, build, and install `g77', *Note Problems Installing::.
information might even lead to all relevant products working information might even lead to all relevant products working
together properly sooner. together properly sooner.
* `g77' currently inserts needless padding for things like `COMMON
A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
on machines like x86, because the back end insists that `IPAD' be
aligned to a 4-byte boundary, but the processor has no such
requirement (though it's good for performance).
It is possible that this is not a real bug, and could be considered
a performance feature, but it might be important to provide the
ability to Fortran code to specify minimum padding for aggregate
areas such as common blocks--and, certainly, there is the
potential, with the current setup, for interface differences in
the way such areas are laid out between `g77' and other compilers.
* `g77' doesn't work perfectly on 64-bit configurations such as the * `g77' doesn't work perfectly on 64-bit configurations such as the
Alpha. This problem is expected to be largely resolved as of Digital Semiconductor ("DEC") Alpha.
version 0.5.20, and further addressed by 0.5.21. Version 0.6
should solve most or all related problems (such as 64-bit machines
other than Digital Semiconductor ("DEC") Alphas).
One known bug that causes a compile-time crash occurs when This problem is largely resolved as of version 0.5.23. Version
compiling code such as the following with optimization: 0.6 should solve most or all remaining problems (such as
cross-compiling involving 64-bit machines).
SUBROUTINE CRASH (TEMP)
INTEGER*2 HALF(2)
REAL TEMP
HALF(1) = NINT (TEMP)
END
It is expected that a future version of `g77' will have a fix for
this problem, almost certainly by the time `g77' supports the
forthcoming version 2.8.0 of `gcc'.
* Maintainers of gcc report that the back end definitely has "broken" * Maintainers of gcc report that the back end definitely has "broken"
support for `COMPLEX' types. Based on their input, it seems many support for `COMPLEX' types. Based on their input, it seems many
...@@ -169,3 +164,55 @@ port, build, and install `g77', *Note Problems Installing::. ...@@ -169,3 +164,55 @@ port, build, and install `g77', *Note Problems Installing::.
in the gcc back end, and it apparently occurs only when compiling in the gcc back end, and it apparently occurs only when compiling
sufficiently complicated functions *without* the `-O' option. sufficiently complicated functions *without* the `-O' option.
Fixed in `egcs' version 1.1.
* `g77' currently inserts needless padding for things like `COMMON
A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
on machines like x86, because the back end insists that `IPAD' be
aligned to a 4-byte boundary, but the processor has no such
requirement (though it is usually good for performance).
The `gcc' back end needs to provide a wider array of
specifications of alignment requirements and preferences for
targets, and front ends like `g77' should take advantage of this
when it becomes available.
* The x86 target's `-malign-double' option no longer reliably aligns
double-precision variables and arrays when they are placed in the
stack frame.
This can significantly reduce the performance of some applications,
even on a run-to-run basis (that is, performance measurements can
vary fairly widely depending on whether frequently used variables
are properly aligned, and that can change from one program run to
the next, even from one procedure call to the next).
Versions 0.5.22 and earlier of `g77' included a patch to `gcc'
that enabled this, but that patch has been deemed an improper
(probably buggy) one for version 2.8 of `gcc' and for `egcs'.
Note that version 1.1 of `egcs' aligns double-precision variables
and arrays when they are in static storage even if
`-malign-double' is not specified.
There is ongoing investigation into how to make `-malign-double'
work properly, also into how to make it unnecessary to get all
double-precision variables and arrays aligned when such alignment
would not violate the relevant specifications for processor and
inter-procedural interfaces.
For a suite of programs to test double-precision alignment, see
`ftp://alpha.gnu.org/gnu/g77/align/'.
* The `libf2c' routines that perform some run-time arithmetic on
`COMPLEX' operands were modified circa version 0.5.20 of `g77' to
work properly even in the presence of aliased operands.
While the `g77' and `netlib' versions of `libf2c' differ on how
this is accomplished, the main differences are that we believe the
`g77' version works properly even in the presence of *partially*
aliased operands.
However, these modifications have reduced performance on targets
such as x86, due to the extra copies of operands involved.
gcc/f/INSTALL
...@@ -3,14 +3,15 @@ compiler. Copyright (C) 1995, 1996 Free Software Foundation, Inc. You ...@@ -3,14 +3,15 @@ compiler. Copyright (C) 1995, 1996 Free Software Foundation, Inc. You
may copy, distribute, and modify it freely as long as you preserve this may copy, distribute, and modify it freely as long as you preserve this
copyright notice and permission notice. copyright notice and permission notice.
Note most of this information is out of date and superceded by the EGCS
install procedures. It is provided for historical reference only.
Installing GNU Fortran Installing GNU Fortran
********************** **********************
The following information describes how to install `g77'. The following information describes how to install `g77'.
Note that, for `egcs' users, much of this information is obsolete,
and is superceded by the `egcs' installation procedures. Such
information is explicitly flagged as such.
The information in this file generally pertains to dealing with The information in this file generally pertains to dealing with
*source* distributions of `g77' and `gcc'. It is possible that some of *source* distributions of `g77' and `gcc'. It is possible that some of
this information will be applicable to some *binary* distributions of this information will be applicable to some *binary* distributions of
...@@ -24,13 +25,16 @@ from source and package up as a binary distribution are ongoing. ...@@ -24,13 +25,16 @@ from source and package up as a binary distribution are ongoing.
Prerequisites Prerequisites
============= =============
*Version info:* For `egcs' users, the following information is
superceded by the `egcs' installation instructions.
The procedures described to unpack, configure, build, and install The procedures described to unpack, configure, build, and install
`g77' assume your system has certain programs already installed. `g77' assume your system has certain programs already installed.
The following prerequisites should be met by your system before you The following prerequisites should be met by your system before you
follow the `g77' installation instructions: follow the `g77' installation instructions:
`gzip' `gzip' and `tar'
To unpack the `gcc' and `g77' distributions, you'll need the To unpack the `gcc' and `g77' distributions, you'll need the
`gunzip' utility in the `gzip' distribution. Most UNIX systems `gunzip' utility in the `gzip' distribution. Most UNIX systems
already have `gzip' installed. If yours doesn't, you can get it already have `gzip' installed. If yours doesn't, you can get it
...@@ -45,24 +49,24 @@ follow the `g77' installation instructions: ...@@ -45,24 +49,24 @@ follow the `g77' installation instructions:
1.2.4. (The version of GNU `tar' used to package this release is 1.2.4. (The version of GNU `tar' used to package this release is
1.12.) 1.12.)
`gcc-2.7.2.3.tar.gz' `gcc-2.8.1.tar.gz'
You need to have this, or some other applicable, version of `gcc' You need to have this, or some other applicable, version of `gcc'
on your system. The version should be an exact copy of a on your system. The version should be an exact copy of a
distribution from the FSF. Its size is approximately 7.1MB. distribution from the FSF. Its size is approximately 8.4MB.
If you've already unpacked `gcc-2.7.2.3.tar.gz' into a directory If you've already unpacked `gcc-2.8.1.tar.gz' into a directory
(named `gcc-2.7.2.3') called the "source tree" for `gcc', you can (named `gcc-2.8.1') called the "source tree" for `gcc', you can
delete the distribution itself, but you'll need to remember to delete the distribution itself, but you'll need to remember to
skip any instructions to unpack this distribution. skip any instructions to unpack this distribution.
Without an applicable `gcc' source tree, you cannot build `g77'. Without an applicable `gcc' source tree, you cannot build `g77'.
You can obtain an FSF distribution of `gcc' from the FSF. You can obtain an FSF distribution of `gcc' from the FSF.
`g77-0.5.22.tar.gz' `g77-0.5.24.tar.gz'
You probably have already unpacked this package, or you are You probably have already unpacked this package, or you are
reading an advance copy of these installation instructions, which reading an advance copy of these installation instructions, which
are contained in this distribution. The size of this package is are contained in this distribution. The size of this package is
approximately 1.5MB. approximately 1.4MB.
You can obtain an FSF distribution of `g77' from the FSF, the same You can obtain an FSF distribution of `g77' from the FSF, the same
way you obtained `gcc'. way you obtained `gcc'.
...@@ -74,46 +78,45 @@ Enough disk space ...@@ -74,46 +78,45 @@ Enough disk space
you install). you install).
The sizes shown below assume all languages distributed in The sizes shown below assume all languages distributed in
`gcc-2.7.2.3', plus `g77', will be built and installed. These `gcc-2.8.1', plus `g77', will be built and installed. These sizes
sizes are indicative of GNU/Linux systems on Intel x86 running are indicative of GNU/Linux systems on Intel x86 running COFF and
COFF and on Digital Alpha (AXP) systems running ELF. These should on Digital Alpha (AXP) systems running ELF. These should be
be fairly representative of 32-bit and 64-bit systems, fairly representative of 32-bit and 64-bit systems, respectively.
respectively.
Note that all sizes are approximate and subject to change without Note that all sizes are approximate and subject to change without
notice! They are based on preliminary releases of g77 made shortly notice! They are based on preliminary releases of g77 made shortly
before the public beta release. before the public beta release.
-- `gcc' and `g77' distributions occupy 8.6MB packed, 35MB -- `gcc' and `g77' distributions occupy 10MB packed, 40MB
unpacked. These consist of the source code and documentation, unpacked. These consist of the source code and documentation,
plus some derived files (mostly documentation), for `gcc' and plus some derived files (mostly documentation), for `gcc' and
`g77'. Any deviations from these numbers for different kinds `g77'. Any deviations from these numbers for different kinds
of systems are likely to be very minor. of systems are likely to be very minor.
-- A "bootstrap" build requires an additional 67.3MB for a -- A "bootstrap" build requires an additional 91MB for a total
total of 102MB on an ix86, and an additional 98MB for a total of 132MB on an ix86, and an additional 136MB for a total of
of 165MB on an Alpha. 177MB on an Alpha.
-- Removing `gcc/stage1' after the build recovers 10.7MB for a -- Removing `gcc/stage1' after the build recovers 13MB for a
total of 91MB on an ix86, and recovers ??MB for a total of total of 119MB on an ix86, and recovers 21MB for a total of
??MB on an Alpha. 155MB on an Alpha.
After doing this, the integrity of the build can still be After doing this, the integrity of the build can still be
verified via `make compare', and the `gcc' compiler modified verified via `make compare', and the `gcc' compiler modified
and used to build itself for testing fairly quickly, using and used to build itself for testing fairly quickly, using
the copy of the compiler kept in `gcc/stage2'. the copy of the compiler kept in `gcc/stage2'.
-- Removing `gcc/stage2' after the build further recovers -- Removing `gcc/stage2' after the build further recovers 39MB
27.3MB for a total of 64.3MB, and recovers ??MB for a total for a total of 80MB, and recovers 57MB for a total of 98MB on
of ??MB on an Alpha. an Alpha.
After doing this, the compiler can still be installed, After doing this, the compiler can still be installed,
especially if GNU `make' is used to avoid gratuitous rebuilds especially if GNU `make' is used to avoid gratuitous rebuilds
(or, the installation can be done by hand). (or, the installation can be done by hand).
-- Installing `gcc' and `g77' copies 14.9MB onto the `--prefix' -- Installing `gcc' and `g77' copies 23MB onto the `--prefix'
disk for a total of 79.2MB on an ix86, and copies ??MB onto disk for a total of 103MB on an ix86, and copies 31MB onto
the `--prefix' disk for a total of ??MB on an Alpha. the `--prefix' disk for a total of 130MB on an Alpha.
After installation, if no further modifications and builds of After installation, if no further modifications and builds of
`gcc' or `g77' are planned, the source and build directory may be `gcc' or `g77' are planned, the source and build directory may be
...@@ -139,57 +142,26 @@ Enough disk space ...@@ -139,57 +142,26 @@ Enough disk space
without replacing existing installed versions (assuming they have without replacing existing installed versions (assuming they have
different version numbers). different version numbers).
`patch'
Although you can do everything `patch' does yourself, by hand,
without much trouble, having `patch' installed makes installation
of new versions of GNU utilities such as `g77' so much easier that
it is worth getting. You can obtain `patch' the same way you
obtained `gcc' and `g77'.
In any case, you can apply patches by hand--patch files are
designed for humans to read them.
The version of GNU `patch' used to develop this release is
2.5.
`make' `make'
Your system must have `make', and you will probably save yourself Your system must have `make', and you will probably save yourself
a lot of trouble if it is GNU `make' (sometimes referred to as a lot of trouble if it is GNU `make' (sometimes referred to as
`gmake'). `gmake'). In particular, you probably need GNU `make' to build
outside the source directory (with `configure''s `--srcdir'
option.)
The version of GNU `make' used to develop this release is The version of GNU `make' used to develop this release is
3.76.1. 3.76.1.
`cc' `cc'
Your system must have a working C compiler. Your system must have a working C compiler. If it doesn't, you
might be able to obtain a prebuilt binary of some version of `gcc'
from the network or on CD-ROM, perhaps from the FSF. The best
source of information about binaries is probably a system-specific
Usenet news group, initially via its FAQ.
*Note Installing GNU CC: (gcc)Installation, for more information *Note Installing GNU CC: (gcc)Installation, for more information
on prerequisites for installing `gcc'. on prerequisites for installing `gcc'.
`bison'
If you do not have `bison' installed, you can usually work around
any need for it, since `g77' itself does not use it, and `gcc'
normally includes all files generated by running it in its
distribution. You can obtain `bison' the same way you obtained
`gcc' and `g77'.
The version of GNU `bison' used to develop this release is
1.25.
*Note Missing bison?::, for information on how to work around not
having `bison'.
`makeinfo'
If you are missing `makeinfo', you can usually work around any
need for it. You can obtain `makeinfo' the same way you obtained
`gcc' and `g77'.
The version of GNU `makeinfo' used to develop this release is
1.68, from GNU `texinfo' version 3.11.
*Note Missing makeinfo?::, for information on getting around the
lack of `makeinfo'.
`sed' `sed'
All UNIX systems have `sed', but some have a broken version that All UNIX systems have `sed', but some have a broken version that
cannot handle configuring, building, or installing `gcc' or `g77'. cannot handle configuring, building, or installing `gcc' or `g77'.
...@@ -217,6 +189,61 @@ Enough disk space ...@@ -217,6 +189,61 @@ Enough disk space
for themselves how they want to modify the procedures described for themselves how they want to modify the procedures described
below to suit the needs of their installation. below to suit the needs of their installation.
`autoconf'
The version of GNU `autoconf' used to develop this release is
2.12.
`autoconf' is not needed in the typical case of installing `gcc'
and `g77'. *Note Missing tools?::, for information on when it
might be needed and how to work around not having it.
`bison'
The version of GNU `bison' used to develop this release is
1.25.
`bison' is not needed in the typical case of installing `gcc' and
`g77'. *Note Missing tools?::, for information on when it might
be needed and how to work around not having it.
`gperf'
The version of GNU `gperf' used to develop this release is
2.5.
`gperf' is not needed in the typical case of installing `gcc' and
`g77'. *Note Missing tools?::, for information on when it might
be needed and how to work around not having it.
`makeinfo'
The version of GNU `makeinfo' used to develop this release is
1.68.
`makeinfo' is part of the GNU `texinfo' package; `makeinfo'
version 1.68 is distributed as part of GNU `texinfo' version
3.11.
`makeinfo' is not needed in the typical case of installing `gcc'
and `g77'. *Note Missing tools?::, for information on when it
might be needed and how to work around not having it.
An up-to-date version of GNU `makeinfo' is still convenient when
obtaining a new version of a GNU distribution such as `gcc' or
`g77', as it allows you to obtain the `.diff.gz' file instead of
the entire `.tar.gz' distribution (assuming you have installed
`patch').
`patch'
The version of GNU `patch' used to develop this release is
2.5.
Beginning with `g77' version 0.5.23, it is no longer necessary to
patch the `gcc' back end to build `g77'.
An up-to-date version of GNU `patch' is still convenient when
obtaining a new version of a GNU distribution such as `gcc' or
`g77', as it allows you to obtain the `.diff.gz' file instead of
the entire `.tar.gz' distribution (assuming you have installed the
tools needed to rebuild derived files, such as `makeinfo').
Problems Installing Problems Installing
=================== ===================
...@@ -247,21 +274,12 @@ bootstrap build to automate the process of first building `gcc' using ...@@ -247,21 +274,12 @@ bootstrap build to automate the process of first building `gcc' using
the working C compiler you have, then building `g77' and rebuilding the working C compiler you have, then building `g77' and rebuilding
`gcc' using that just-built `gcc', and so on. `gcc' using that just-built `gcc', and so on.
Patching GNU CC Necessary Patching GNU CC
......................... ...............
`g77' currently requires application of a patch file to the gcc
compiler tree. The necessary patches should be folded in to the
mainline gcc distribution.
Some combinations of versions of `g77' and `gcc' might actually `g77' no longer requires application of a patch file to the `gcc'
*require* no patches, but the patch files will be provided anyway as compiler tree. In fact, no such patch file is distributed with `g77'.
long as there are more changes expected in subsequent releases. These This is as of version 0.5.23 and `egcs' version 1.0.
patch files might contain unnecessary, but possibly helpful, patches.
As a result, it is possible this issue might never be resolved, except
by eliminating the need for the person configuring `g77' to apply a
patch by hand, by going to a more automated approach (such as
configure-time patching).
Building GNU CC Necessary Building GNU CC Necessary
......................... .........................
...@@ -270,31 +288,50 @@ Building GNU CC Necessary ...@@ -270,31 +288,50 @@ Building GNU CC Necessary
and other non-Fortran items, but, for now, an easy way to do that is and other non-Fortran items, but, for now, an easy way to do that is
not yet established. not yet established.
Missing strtoul Missing strtoul or bsearch
............... ..........................
*Version info:* The following information does not apply to the
`egcs' version of `g77'.
On SunOS4 systems, linking the `f771' program used to produce an
error message concerning an undefined symbol named `_strtoul', because
the `strtoul' library function is not provided on that system.
Other systems have, in the past, been reported to not provide their
own `strtoul' or `bsearch' function.
Some versions `g77' tried to default to providing bare-bones
versions of `bsearch' and `strtoul' automatically, but every attempt at
this has failed for at least one kind of system.
To limit the failures to those few systems actually missing the
required routines, the bare-bones versions are still provided, in
`gcc/f/proj.c', if the appropriate macros are defined. These are
`NEED_BSEARCH' for `bsearch' and `NEED_STRTOUL' for `NEED_STRTOUL'.
Therefore, if you are sure your system is missing `bsearch' or
`strtoul' in its library, define the relevant macro(s) before building
`g77'. This can be done by editing `gcc/f/proj.c' and inserting either
or both of the following `#define' statements before the comment shown:
On SunOS4 systems, linking the `f771' program produces an error /* Insert #define statements here. */
message concerning an undefined symbol named `_strtoul'.
#define NEED_BSEARCH
This is not a `g77' bug. *Note Patching GNU Fortran::, for #define NEED_STRTOUL
information on a workaround provided by `g77'.
Then, continue configuring and building `g77' as usual.
The proper fix is either to upgrade your system to one that provides
a complete ANSI C environment, or improve `gcc' so that it provides one Or, you can define these on the `make' command line. To build with
for all the languages and configurations it supports. the bundled `cc' on SunOS4, for example, try:
make bootstrap BOOT_CFLAGS='-O2 -g -DNEED_STRTOUL'
*Note:* In earlier versions of `g77', an automated workaround for
this problem was attempted. It worked for systems without `_strtoul', If you then encounter problems compiling `gcc/f/proj.c', it might be
substituting the incomplete-yet-sufficient version supplied with `g77' due to a discrepancy between how `bsearch' or `strtoul' are defined by
for those systems. However, the automated workaround failed that file and how they're declared by your system's header files.
mysteriously for systems that appeared to have conforming ANSI C
environments, and it was decided that, lacking resources to more fully In that case, you'll have to use some basic knowledge of C to work
investigate the problem, it was better to not punish users of those around the problem, perhaps by editing `gcc/f/proj.c' somewhat.
systems either by requiring them to work around the problem by hand or
by always substituting an incomplete `strtoul()' implementation when
their systems had a complete, working one. Unfortunately, this meant
inconveniencing users of systems not having `strtoul()', but they're
using obsolete (and generally unsupported) systems anyway.
Cleanup Kills Stage Directories Cleanup Kills Stage Directories
............................... ...............................
...@@ -304,49 +341,37 @@ create the various `stageN' directories and their subdirectories, so ...@@ -304,49 +341,37 @@ create the various `stageN' directories and their subdirectories, so
developers and expert installers wouldn't have to reconfigure after developers and expert installers wouldn't have to reconfigure after
cleaning up. cleaning up.
Missing `gperf'? That help has arrived as of version 0.5.23 of `g77' and version 1.1
................ of `egcs'. Configuration itself no longer creates any particular
directories that are unique to `g77'. The build procedures in
`Make-lang.in' take care of that, on demand.
If a build aborts trying to invoke `gperf', that strongly suggests LANGUAGES Macro Ignored
an improper method was used to create the `gcc' source directory, such .......................
as the UNIX `cp -r' command instead of `cp -pr', since this problem
very likely indicates that the date-time-modified information on the
`gcc' source files is incorrect.
The proper solution is to recreate the `gcc' source directory from a Prior to version 0.5.23 of `g77' and version 1.1 of `egcs', `g77'
`gcc' distribution known to be provided by the FSF. would sometimes ignore the absence of `f77' and `F77' in the
`LANGUAGES' macro definition used for the `make' command being
processed.
It is possible you might be able to temporarily work around the As of `g77' version 0.5.23 and `egcs' version 1.1, `g77' now obeys
problem, however, by trying these commands: this macro in all relevant situations.
sh# cd gcc However, in versions of `gcc' through 2.8.1, non-`g77' portions of
sh# touch c-gperf.h `gcc', such as `g++', are known to go ahead and perform various
sh# language-specific activities when their respective language strings do
not appear in the `LANGUAGES' macro in effect during that invocation of
These commands update the date-time-modified information for the `make'.
file produced by the invocation of `gperf' in the current versions of
`gcc', so that `make' no longer believes it needs to update it. This
file should already exist in a `gcc' distribution, but mistakes made
when copying the `gcc' directory can leave the modification information
set such that the `gperf' input files look more "recent" than the
corresponding output files.
If the above does not work, definitely start from scratch and avoid It is expected that these remaining problems will be fixed in a
copying the `gcc' using any method that does not reliably preserve future version of `gcc'.
date-time-modified information, such as the UNIX `cp -r' command (use
`cp -pr' instead).
System-specific Problems System-specific Problems
------------------------ ------------------------
If your system is based on a Digital Alpha (AXP) architecture and A linker bug on some versions of AIX 4.1 might prevent building when
employs a 64-bit operating system (such as GNU/Linux), you might `g77' is built within `gcc'. It might also occur when building within
consider using `egcs' instead of versions of `g77' based on versions of `egcs'. *Note LINKFAIL::.
`gcc' prior to 2.8. `http://www.cygnus.com/egcs' for information on
`egcs', or obtain a copy from `ftp://egcs.cygnus.com/pub/egcs'.
If your system is Irix 6, to obtain a working version of `gcc',
`http://reality.sgi.com/knobi/gcc-2.7.2.x-on-irix-6.2-6.3'.
Cross-compiler Problems Cross-compiler Problems
----------------------- -----------------------
...@@ -382,12 +407,13 @@ reasons. ...@@ -382,12 +407,13 @@ reasons.
combinations of machines. For example, it might not know how to combinations of machines. For example, it might not know how to
handle floating-point constants. handle floating-point constants.
* Improvements to the way `libf2c' is built could make building * Improvements to the way `libg2c' is built could make building
`g77' as a cross-compiler easier--for example, passing and using `g77' as a cross-compiler easier--for example, passing and using
`$(LD)' and `$(AR)' in the appropriate ways. `$(LD)' and `$(AR)' in the appropriate ways. (This is improved in
the `egcs' version of `g77', especially as of version 1.1.)
* There are still some challenges putting together the right * There are still some challenges putting together the right
run-time libraries (needed by `libf2c') for a target system, run-time libraries (needed by `libg2c') for a target system,
depending on the systems involved in the configuration. (This is depending on the systems involved in the configuration. (This is
a general problem with cross-compilation, and with `gcc' in a general problem with cross-compilation, and with `gcc' in
particular.) particular.)
...@@ -453,8 +479,8 @@ reporting (immediate flagging of errors during writes) versus ...@@ -453,8 +479,8 @@ reporting (immediate flagging of errors during writes) versus
asynchronous, or, more precisely, buffered error reporting (detection asynchronous, or, more precisely, buffered error reporting (detection
of errors might be delayed). of errors might be delayed).
`libf2c' supports flagging write errors immediately when it is built `libg2c' supports flagging write errors immediately when it is built
with the `ALWAYS_FLUSH' macro defined. This results in a `libf2c' that with the `ALWAYS_FLUSH' macro defined. This results in a `libg2c' that
runs slower, sometimes quite a bit slower, under certain runs slower, sometimes quite a bit slower, under certain
circumstances--for example, accessing files via the networked file circumstances--for example, accessing files via the networked file
system NFS--but the effect can be more reliable, robust file I/O. system NFS--but the effect can be more reliable, robust file I/O.
...@@ -462,18 +488,16 @@ system NFS--but the effect can be more reliable, robust file I/O. ...@@ -462,18 +488,16 @@ system NFS--but the effect can be more reliable, robust file I/O.
If you know that Fortran programs requiring this level of precision If you know that Fortran programs requiring this level of precision
of error reporting are to be compiled using the version of `g77' you of error reporting are to be compiled using the version of `g77' you
are building, you might wish to modify the `g77' source tree so that are building, you might wish to modify the `g77' source tree so that
the version of `libf2c' is built with the `ALWAYS_FLUSH' macro defined, the version of `libg2c' is built with the `ALWAYS_FLUSH' macro defined,
enabling this behavior. enabling this behavior.
To do this, find this line in `f/runtime/configure.in' in your `g77' To do this, find this line in `f/runtime/f2c.h' in your `g77' source
source tree: tree:
dnl AC_DEFINE(ALWAYS_FLUSH) /* #define ALWAYS_FLUSH */
Remove the leading `dnl ', so the line begins with `AC_DEFINE(', and Remove the leading `/* ', so the line begins with `#define', and the
run `autoconf' in that file's directory. (Or, if you don't have trailing ` */'.
`autoconf', you can modify `f2c.h.in' in the same directory to include
the line `#define ALWAYS_FLUSH' after `#define F2C_INCLUDE'.)
Then build or rebuild `g77' as appropriate. Then build or rebuild `g77' as appropriate.
...@@ -558,6 +582,9 @@ support 64-bit systems. ...@@ -558,6 +582,9 @@ support 64-bit systems.
Quick Start Quick Start
=========== ===========
*Version info:* For `egcs' users, the following information is
superceded by the `egcs' installation instructions.
This procedure configures, builds, and installs `g77' "out of the This procedure configures, builds, and installs `g77' "out of the
box" and works on most UNIX systems. Each command is identified by a box" and works on most UNIX systems. Each command is identified by a
unique number, used in the explanatory text that follows. For the most unique number, used in the explanatory text that follows. For the most
...@@ -575,81 +602,51 @@ is assumed that the source distributions themselves already reside in ...@@ -575,81 +602,51 @@ is assumed that the source distributions themselves already reside in
`/usr/FSF', a naming convention used by the author of `g77' on his own `/usr/FSF', a naming convention used by the author of `g77' on his own
system: system:
/usr/FSF/gcc-2.7.2.3.tar.gz /usr/FSF/gcc-2.8.1.tar.gz
/usr/FSF/g77-0.5.22.tar.gz /usr/FSF/g77-0.5.24.tar.gz
Users of the following systems should not blindly follow these
quick-start instructions, because of problems their systems have coping
with straightforward installation of `g77':
* SunOS4
Instead, see *Note Complete Installation::, for detailed information
on how to configure, build, and install `g77' for your particular
system. Also, see *Note Known Causes of Trouble with GNU Fortran:
Trouble, for information on bugs and other problems known to afflict the
installation process, and how to report newly discovered ones.
If your system is *not* on the above list, and *is* a UNIX system or If you vary *any* of the steps below, you might run into trouble,
one of its variants, you should be able to follow the instructions including possibly breaking existing programs for other users of your
below. If you vary *any* of the steps below, you might run into system. Before doing so, it is wise to review the explanations of some
trouble, including possibly breaking existing programs for other users of the steps. These explanations follow this list of steps.
of your system. Before doing so, it is wise to review the explanations
of some of the steps. These explanations follow this list of steps.
sh[ 1]# cd /usr/src sh[ 1]# cd /usr/src
sh[ 2]# gunzip -c < /usr/FSF/gcc-2.7.2.3.tar.gz | tar xf - sh[ 2]# gunzip -c < /usr/FSF/gcc-2.8.1.tar.gz | tar xf -
[Might say "Broken pipe"...that is normal on some systems.] [Might say "Broken pipe"...that is normal on some systems.]
sh[ 3]# gunzip -c < /usr/FSF/g77-0.5.22.tar.gz | tar xf - sh[ 3]# gunzip -c < /usr/FSF/g77-0.5.24.tar.gz | tar xf -
["Broken pipe" again possible.] ["Broken pipe" again possible.]
sh[ 4]# ln -s gcc-2.7.2.3 gcc sh[ 4]# ln -s gcc-2.8.1 gcc
sh[ 5]# ln -s g77-0.5.22 g77 sh[ 5]# ln -s g77-0.5.24 g77
sh[ 6]# mv -i g77/* gcc sh[ 6]# mv -i g77/* gcc
[No questions should be asked by mv here; or, you made a mistake.] [No questions should be asked by mv here; or, you made a mistake.]
sh[ 7]# patch -p1 -E -V t -d gcc < gcc/f/gbe/2.7.2.3.diff sh[ 7]# cd gcc
[Unless patch complains about rejected patches, this step worked.] sh[ 8]# ./configure --prefix=/usr
sh[ 8]# cd gcc
sh[ 9]# touch f77-install-ok
[Do not do the above if your system already has an f77
command, unless you've checked that overwriting it
is okay.]
sh[10]# touch f2c-install-ok
[Do not do the above if your system already has an f2c
command, unless you've checked that overwriting it
is okay. Else, touch f2c-exists-ok.]
sh[11]# ./configure --prefix=/usr
[Do not do the above if gcc is not installed in /usr/bin. [Do not do the above if gcc is not installed in /usr/bin.
You might need a different --prefix=..., as You might need a different --prefix=..., as
described below.] described below.]
sh[12]# make bootstrap sh[ 9]# make bootstrap
[This takes a long time, and is where most problems occur.] [This takes a long time, and is where most problems occur.]
sh[13]# make compare sh[10]# make compare
[This verifies that the compiler is `sane'. Only [This verifies that the compiler is `sane'.
the file `f/zzz.o' (aka `tmp-foo1' and `tmp-foo2') If any files are printed, you have likely found a g77 bug.]
should be in the list of object files this command
prints as having different contents. If other files
are printed, you have likely found a g77 bug.]
sh[14]# rm -fr stage1 sh[11]# rm -fr stage1
sh[15]# make -k install sh[12]# make -k install
[The actual installation.] [The actual installation.]
sh[16]# g77 -v sh[13]# g77 -v
[Verify that g77 is installed, obtain version info.] [Verify that g77 is installed, obtain version info.]
sh[17]# sh[14]#
*Note Updating Your Info Directory: Updating Documentation, for *Note Updating Your Info Directory: Updating Documentation, for
information on how to update your system's top-level `info' directory information on how to update your system's top-level `info' directory
...@@ -664,17 +661,17 @@ Step 1: `cd /usr/src' ...@@ -664,17 +661,17 @@ Step 1: `cd /usr/src'
your system knew where to look for the source code for the your system knew where to look for the source code for the
installed version of `g77' and `gcc' in any case. installed version of `g77' and `gcc' in any case.
Step 3: `gunzip -d < /usr/FSF/g77-0.5.22.tar.gz | tar xf -' Step 3: `gunzip -d < /usr/FSF/g77-0.5.24.tar.gz | tar xf -'
It is not always necessary to obtain the latest version of `g77' It is not always necessary to obtain the latest version of `g77'
as a complete `.tar.gz' file if you have a complete, earlier as a complete `.tar.gz' file if you have a complete, earlier
distribution of `g77'. If appropriate, you can unpack that earlier distribution of `g77'. If appropriate, you can unpack that earlier
version of `g77', and then apply the appropriate patches to version of `g77', and then apply the appropriate patches to
achieve the same result--a source tree containing version achieve the same result--a source tree containing version
0.5.22 of `g77'. 0.5.24 of `g77'.
Step 4: `ln -s gcc-2.7.2.3 gcc' Step 4: `ln -s gcc-2.8.1 gcc'
Step 5: `ln -s g77-0.5.22 g77' Step 5: `ln -s g77-0.5.24 g77'
These commands mainly help reduce typing, and help reduce visual These commands mainly help reduce typing, and help reduce visual
clutter in examples in this manual showing what to type to install clutter in examples in this manual showing what to type to install
`g77'. `g77'.
...@@ -684,7 +681,7 @@ Step 5: `ln -s g77-0.5.22 g77' ...@@ -684,7 +681,7 @@ Step 5: `ln -s g77-0.5.22 g77'
Step 6: `mv -i g77/* gcc' Step 6: `mv -i g77/* gcc'
After doing this, you can, if you like, type `rm g77' and `rmdir After doing this, you can, if you like, type `rm g77' and `rmdir
g77-0.5.22' to remove the empty directory and the symbol link to g77-0.5.24' to remove the empty directory and the symbol link to
it. But, it might be helpful to leave them around as quick it. But, it might be helpful to leave them around as quick
reminders of which version(s) of `g77' are installed on your reminders of which version(s) of `g77' are installed on your
system. system.
...@@ -692,57 +689,19 @@ Step 6: `mv -i g77/* gcc' ...@@ -692,57 +689,19 @@ Step 6: `mv -i g77/* gcc'
*Note Unpacking::, for information on the contents of the `g77' *Note Unpacking::, for information on the contents of the `g77'
directory (as merged into the `gcc' directory). directory (as merged into the `gcc' directory).
Step 7: `patch -p1 ...' Step 8: `./configure --prefix=/usr'
If you are using GNU `patch' version 2.5 or later, this should This is where you specify that the `g77' and `gcc' executables are
produce a list of files patched. (Other versions of `patch' might to be installed in `/usr/bin/', the `g77' and `gcc' documentation
not work properly.) is to be installed in `/usr/info/' and `/usr/man/', and so on.
If messages about "fuzz", "offset", or especially "reject files"
are printed, it might mean you applied the wrong patch file. If
you believe this is the case, it is best to restart the sequence
after deleting (or at least renaming to unused names) the
top-level directories for `g77' and `gcc' and their symbolic links.
After this command finishes, the `gcc' directory might have old
versions of several files as saved by `patch'. To remove these,
after `cd gcc', type `rm -i *.~*~'.
*Note Merging Distributions::, for more information.
*Note:* `gcc' versions circa 2.7.2.2 and 2.7.2.3 are known to have
slightly differing versions of the `gcc/ChangeLog' file, depending
on how they are obtained. You can safely ignore diagnostics
`patch' reports when patching this particular file, since it is
purely a documentation file for implementors. See
`gcc/f/gbe/2.7.2.3.diff' for more information.
Step 9: `touch f77-install-ok'
Don't do this if you don't want to overwrite an existing version
of `f77' (such as a native compiler, or a script that invokes
`f2c'). Otherwise, installation will overwrite the `f77' command
and the `f77' man pages with copies of the corresponding `g77'
material.
*Note Installing `f77': Installing f77, for more information.
Step 10: `touch f2c-install-ok'
Don't do this if you don't want to overwrite an existing
installation of `libf2c' (though, chances are, you do). Instead,
`touch f2c-exists-ok' to allow the installation to continue
without any error messages about `/usr/lib/libf2c.a' already
existing.
*Note Installing `f2c': Installing f2c, for more information.
Step 11: `./configure --prefix=/usr'
This is where you specify that the `g77' executable is to be
installed in `/usr/bin/', the `libf2c.a' library is to be
installed in `/usr/lib/', and so on.
You should ensure that any existing installation of the `gcc' You should ensure that any existing installation of the `gcc'
executable is in `/usr/bin/'. Otherwise, installing `g77' so that executable is in `/usr/bin/'.
it does not fully replace the existing installation of `gcc' is
likely to result in the inability to compile Fortran programs. However, if that existing version of `gcc' is not 2.8.1, or if you
simply wish to avoid risking overwriting it with a newly built
copy of the same version, you can specify `--prefix=/usr/local'
(which is the default) or some other path, and invoke the newly
installed version directly from that path's `bin' directory.
*Note Where in the World Does Fortran (and GNU CC) Go?: Where to *Note Where in the World Does Fortran (and GNU CC) Go?: Where to
Install, for more information on determining where to install Install, for more information on determining where to install
...@@ -750,28 +709,30 @@ Step 11: `./configure --prefix=/usr' ...@@ -750,28 +709,30 @@ Step 11: `./configure --prefix=/usr'
configuration process triggered by invoking the `./configure' configuration process triggered by invoking the `./configure'
script. script.
Step 12: `make bootstrap' Step 9: `make bootstrap'
*Note Installing GNU CC: (gcc)Installation, for information on the *Note Installing GNU CC: (gcc)Installation, for information on the
kinds of diagnostics you should expect during this procedure. kinds of diagnostics you should expect during this procedure.
*Note Building gcc::, for complete `g77'-specific information on *Note Building gcc::, for complete `g77'-specific information on
this step. this step.
Step 13: `make compare' Step 10: `make compare'
*Note Where to Port Bugs: Bug Lists, for information on where to *Note Where to Port Bugs: Bug Lists, for information on where to
report that you observed more than `f/zzz.o' having different report that you observed files having different contents during
contents during this phase. this phase.
*Note How to Report Bugs: Bug Reporting, for information on *how* *Note How to Report Bugs: Bug Reporting, for information on *how*
to report bugs like this. to report bugs like this.
Step 14: `rm -fr stage1' Step 11: `rm -fr stage1'
You don't need to do this, but it frees up disk space. You don't need to do this, but it frees up disk space.
Step 15: `make -k install' Step 12: `make -k install'
If this doesn't seem to work, try: If this doesn't seem to work, try:
make -k install install-libf77 install-f2c-all make -k install install-libf77
Or, make sure you're using GNU `make'.
*Note Installation of Binaries::, for more information. *Note Installation of Binaries::, for more information.
...@@ -779,7 +740,7 @@ Step 15: `make -k install' ...@@ -779,7 +740,7 @@ Step 15: `make -k install'
information on entering this manual into your system's list of information on entering this manual into your system's list of
texinfo manuals. texinfo manuals.
Step 16: `g77 -v' Step 13: `g77 -v'
If this command prints approximately 25 lines of output, including If this command prints approximately 25 lines of output, including
the GNU Fortran Front End version number (which should be the same the GNU Fortran Front End version number (which should be the same
as the version number for the version of `g77' you just built and as the version number for the version of `g77' you just built and
...@@ -815,6 +776,13 @@ Step 16: `g77 -v' ...@@ -815,6 +776,13 @@ Step 16: `g77 -v'
Hello World # 10 Hello World # 10
sh# sh#
If invoking `g77' doesn't seem to work, the problem might be that
you've installed it in a location that is not in your shell's
search path. For example, if you specified `--prefix=/gnu', and
`/gnu/bin' is not in your `PATH' environment variable, you must
explicitly specify the location of the compiler via `/gnu/bin/g77
-o smtest smtest.f'.
After proper installation, you don't need to keep your gcc and g77 After proper installation, you don't need to keep your gcc and g77
source and build directories around anymore. Removing them can source and build directories around anymore. Removing them can
free up a lot of disk space. free up a lot of disk space.
...@@ -822,6 +790,9 @@ Step 16: `g77 -v' ...@@ -822,6 +790,9 @@ Step 16: `g77 -v'
Complete Installation Complete Installation
===================== =====================
*Version info:* For `egcs' users, the following information is
mostly superceded by the `egcs' installation instructions.
Here is the complete `g77'-specific information on how to configure, Here is the complete `g77'-specific information on how to configure,
build, and install `g77'. build, and install `g77'.
...@@ -847,10 +818,10 @@ generally only the documentation is immediately usable. ...@@ -847,10 +818,10 @@ generally only the documentation is immediately usable.
A sequence of commands typically used to unpack `gcc' and `g77' is: A sequence of commands typically used to unpack `gcc' and `g77' is:
sh# cd /usr/src sh# cd /usr/src
sh# gunzip -c /usr/FSF/gcc-2.7.2.3.tar.gz | tar xf - sh# gunzip -c /usr/FSF/gcc-2.8.1.tar.gz | tar xf -
sh# gunzip -c /usr/FSF/g77-0.5.22.tar.gz | tar xf - sh# gunzip -c /usr/FSF/g77-0.5.24.tar.gz | tar xf -
sh# ln -s gcc-2.7.2.3 gcc sh# ln -s gcc-2.8.1 gcc
sh# ln -s g77-0.5.22 g77 sh# ln -s g77-0.5.24 g77
sh# mv -i g77/* gcc sh# mv -i g77/* gcc
*Notes:* The commands beginning with `gunzip...' might print `Broken *Notes:* The commands beginning with `gunzip...' might print `Broken
...@@ -869,7 +840,7 @@ and the top level of just the `g77' source tree (prior to issuing the ...@@ -869,7 +840,7 @@ and the top level of just the `g77' source tree (prior to issuing the
All three entries should be moved (or copied) into a `gcc' source All three entries should be moved (or copied) into a `gcc' source
tree (typically named after its version number and as it appears in the tree (typically named after its version number and as it appears in the
FSF distributions--e.g. `gcc-2.7.2.3'). FSF distributions--e.g. `gcc-2.8.1').
`g77/f' is the subdirectory containing all of the code, `g77/f' is the subdirectory containing all of the code,
documentation, and other information that is specific to `g77'. The documentation, and other information that is specific to `g77'. The
...@@ -881,10 +852,9 @@ from a single FSF distribution. They also help people encountering an ...@@ -881,10 +852,9 @@ from a single FSF distribution. They also help people encountering an
unmerged `g77' source tree for the first time. unmerged `g77' source tree for the first time.
*Note:* Please use *only* `gcc' and `g77' source trees as *Note:* Please use *only* `gcc' and `g77' source trees as
distributed by the FSF. Use of modified versions, such as the distributed by the FSF. Use of modified versions is likely to result
Pentium-specific-optimization port of `gcc', is likely to result in in problems that appear to be in the `g77' code but, in fact, are not.
problems that appear to be in the `g77' code but, in fact, are not. Do Do not use such modified versions unless you understand all the
not use such modified versions unless you understand all the
differences between them and the versions the FSF distributes--in which differences between them and the versions the FSF distributes--in which
case you should be able to modify the `g77' (or `gcc') source trees case you should be able to modify the `g77' (or `gcc') source trees
appropriately so `g77' and `gcc' can coexist as they do in the stock appropriately so `g77' and `gcc' can coexist as they do in the stock
...@@ -893,22 +863,18 @@ FSF distributions. ...@@ -893,22 +863,18 @@ FSF distributions.
Merging Distributions Merging Distributions
--------------------- ---------------------
After merging the `g77' source tree into the `gcc' source tree, the After merging the `g77' source tree into the `gcc' source tree, you
final merge step is done by applying the pertinent patches the `g77' have put together a complete `g77' source tree.
distribution provides for the `gcc' source tree.
Read the file `gcc/f/gbe/README', and apply the appropriate patch As of version 0.5.23, `g77' no longer modifies the version number of
file for the version of the GNU CC compiler you have, if that exists. `gcc', nor does it patch `gcc' itself.
If the directory exists but the appropriate file does not exist, you
are using either an old, unsupported version, or a release one that is
newer than the newest `gcc' version supported by the version of `g77'
you have.
As of version 0.5.18, `g77' modifies the version number of `gcc' via `g77' still depends on being merged with an appropriate version of
the pertinent patches. This is done because the resulting version of `gcc'. For version 0.5.24 of `g77', the specific version of `gcc'
`gcc' is deemed sufficiently different from the vanilla distribution to supported is 2.8.1.
make it worthwhile to present, to the user, information signaling the
fact that there are some differences. However, other versions of `gcc' might be suitable "hosts" for this
version of `g77'.
GNU version numbers make it easy to figure out whether a particular GNU version numbers make it easy to figure out whether a particular
version of a distribution is newer or older than some other version of version of a distribution is newer or older than some other version of
...@@ -924,9 +890,10 @@ create.) ...@@ -924,9 +890,10 @@ create.)
If your version of `gcc' is older than the oldest version supported If your version of `gcc' is older than the oldest version supported
by `g77' (as casually determined by listing the contents of by `g77' (as casually determined by listing the contents of
`gcc/f/gbe/'), you should obtain a newer, supported version of `gcc'. `gcc/f/INSTALL/', which contains these installation instructions in
(You could instead obtain an older version of `g77', or try and get plain-text format), you should obtain a newer, supported version of
your `g77' to work with the old `gcc', but neither approach is `gcc'. (You could instead obtain an older version of `g77', or try and
get your `g77' to work with the old `gcc', but neither approach is
recommended, and you shouldn't bother reporting any bugs you find if you recommended, and you shouldn't bother reporting any bugs you find if you
take either approach, because they're probably already fixed in the take either approach, because they're probably already fixed in the
newer versions you're not using.) newer versions you're not using.)
...@@ -934,191 +901,26 @@ newer versions you're not using.) ...@@ -934,191 +901,26 @@ newer versions you're not using.)
If your version of `gcc' is newer than the newest version supported If your version of `gcc' is newer than the newest version supported
by `g77', it is possible that your `g77' will work with it anyway. If by `g77', it is possible that your `g77' will work with it anyway. If
the version number for `gcc' differs only in the PATCH field, you might the version number for `gcc' differs only in the PATCH field, you might
as well try applying the `g77' patch that is for the newest version of as well try that version of `gcc'. Since it has the same MAJOR and
`gcc' having the same MAJOR and MINOR fields, as this is likely to work. MINOR fields, the resulting combination is likely to work.
So, for example, if a particular version of `g77' has support for So, for example, if a particular version of `g77' has support for
`gcc' versions 2.7.0 and 2.7.1, it is likely that `gcc-2.7.2' would `gcc' versions 2.8.0 and 2.8.1, it is likely that `gcc-2.8.2' would
work well with `g77' by using the `2.7.1.diff' patch file provided with work well with `g77'.
`g77' (aside from some offsets reported by `patch', which usually are
harmless).
However, `gcc-2.8.0' would almost certainly not work with that However, `gcc-2.9.0' would almost certainly not work with that
version of `g77' no matter which patch file was used, so a new version version of `g77' without appropriate modifications, so a new version of
of `g77' would be needed (and you should wait for it rather than `g77' would be needed (and you should wait for it rather than bothering
bothering the maintainers--*note User-Visible Changes: Changes.). the maintainers--*note User-Visible Changes: Changes.).
This complexity is the result of `gcc' and `g77' being separate This complexity is the result of `gcc' and `g77' being separate
distributions. By keeping them separate, each product is able to be distributions. By keeping them separate, each product is able to be
independently improved and distributed to its user base more frequently. independently improved and distributed to its user base more frequently.
However, `g77' often requires changes to contemporary versions of However, the GBE interface defined by `gcc' typically undergoes some
`gcc'. Also, the GBE interface defined by `gcc' typically undergoes incompatible changes at least every time the MINOR field of the version
some incompatible changes at least every time the MINOR field of the number is incremented, and such changes require corresponding changes to
version number is incremented, and such changes require corresponding the `g77' front end (FFE).
changes to the `g77' front end (FFE).
It is hoped that the GBE interface, and the `gcc' and `g77' products
in general, will stabilize sufficiently for the need for hand-patching
to disappear.
If you are using GNU `patch' version 2.5 or later, this should
produce a list of files patched. (Other versions of `patch' might not
work properly.)
If messages about "fuzz", "offset", or especially "reject files" are
printed, it might mean you applied the wrong patch file. If you
believe this is the case, it is best to restart the sequence after
deleting (or at least renaming to unused names) the top-level
directories for `g77' and `gcc' and their symbolic links. That is
because `patch' might have partially patched some `gcc' source files,
so reapplying the correct patch file might result in the correct
patches being applied incorrectly (due to the way `patch' necessarily
works).
After `patch' finishes, the `gcc' directory might have old versions
of several files as saved by `patch'. To remove these, after `cd gcc',
type `rm -i *.~*~'.
*Note:* `gcc' versions circa 2.7.2.2 and 2.7.2.3 are known to have
slightly differing versions of the `gcc/ChangeLog' file, depending on
how they are obtained. You can safely ignore diagnostics `patch'
reports when patching this particular file, since it is purely a
documentation file for implementors. See `gcc/f/gbe/2.7.2.3.diff' for
more information.
*Note:* `g77''s configuration file `gcc/f/config-lang.in' ensures
that the source code for the version of `gcc' being configured has at
least one indication of being patched as required specifically by `g77'.
This configuration-time checking should catch failure to apply the
correct patch and, if so caught, should abort the configuration with an
explanation. *Please* do not try to disable the check, otherwise `g77'
might well appear to build and install correctly, and even appear to
compile correctly, but could easily produce broken code.
`LC_ALL=C TZ=UTC0 diff -rcp2N' is used to create the patch files in
`gcc/f/gbe/'.
Installing `f77'
----------------
You should decide whether you want installation of `g77' to also
install an `f77' command. On systems with a native `f77', this is not
normally desired, so `g77' does not do this by default.
If you want `f77' installed, create the file `f77-install-ok' (e.g.
via the UNIX command `touch f77-install-ok') in the source or build
top-level directory (the same directory in which the `g77' `f'
directory resides, not the `f' directory itself), or edit
`gcc/f/Make-lang.in' and change the definition of the
`F77_INSTALL_FLAG' macro appropriately.
Usually, this means that, after typing `cd gcc', you would type
`touch f77-install-ok'.
When you enable installation of `f77', either a link to or a direct
copy of the `g77' command is made. Similarly, `f77.1' is installed as
a man page.
(The `uninstall' target in the `gcc/Makefile' also tests this macro
and file, when invoked, to determine whether to delete the installed
copies of `f77' and `f77.1'.)
*Note:* No attempt is yet made to install a program (like a shell
script) that provides compatibility with any other `f77' programs.
Only the most rudimentary invocations of `f77' will work the same way
with `g77'.
Installing `f2c'
----------------
Currently, `g77' does not include `f2c' itself in its distribution.
However, it does include a modified version of the `libf2c'. This
version is normally compatible with `f2c', but has been modified to
meet the needs of `g77' in ways that might possibly be incompatible
with some versions or configurations of `f2c'.
Decide how installation of `g77' should affect any existing
installation of `f2c' on your system.
If you do not have `f2c' on your system (e.g. no `/usr/bin/f2c', no
`/usr/include/f2c.h', and no `/usr/lib/libf2c.a', `/usr/lib/libF77.a',
or `/usr/lib/libI77.a'), you don't need to be concerned with this item.
If you do have `f2c' on your system, you need to decide how users of
`f2c' will be affected by your installing `g77'. Since `g77' is
currently designed to be object-code-compatible with `f2c' (with very
few, clear exceptions), users of `f2c' might want to combine
`f2c'-compiled object files with `g77'-compiled object files in a
single executable.
To do this, users of `f2c' should use the same copies of `f2c.h' and
`libf2c.a' that `g77' uses (and that get built as part of `g77').
If you do nothing here, the `g77' installation process will not
overwrite the `include/f2c.h' and `lib/libf2c.a' files with its own
versions, and in fact will not even install `libf2c.a' for use with the
newly installed versions of `gcc' and `g77' if it sees that
`lib/libf2c.a' exists--instead, it will print an explanatory message
and skip this part of the installation.
To install `g77''s versions of `f2c.h' and `libf2c.a' in the
appropriate places, create the file `f2c-install-ok' (e.g. via the UNIX
command `touch f2c-install-ok') in the source or build top-level
directory (the same directory in which the `g77' `f' directory resides,
not the `f' directory itself), or edit `gcc/f/Make-lang.in' and change
the definition of the `F2C_INSTALL_FLAG' macro appropriately.
Usually, this means that, after typing `cd gcc', you would type
`touch f2c-install-ok'.
Make sure that when you enable the overwriting of `f2c.h' and
`libf2c.a' as used by `f2c', you have a recent and properly configured
version of `bin/f2c' so that it generates code that is compatible with
`g77'.
If you don't want installation of `g77' to overwrite `f2c''s existing
installation, but you do want `g77' installation to proceed with
installation of its own versions of `f2c.h' and `libf2c.a' in places
where `g77' will pick them up (even when linking `f2c'-compiled object
files--which might lead to incompatibilities), create the file
`f2c-exists-ok' (e.g. via the UNIX command `touch f2c-exists-ok') in
the source or build top-level directory, or edit `gcc/f/Make-lang.in'
and change the definition of the `F2CLIBOK' macro appropriately.
Patching GNU Fortran
--------------------
If you're using a SunOS4 system, you'll need to make the following
change to `gcc/f/proj.h': edit the line reading
#define FFEPROJ_STRTOUL 1 ...
by replacing the `1' with `0'. Or, you can avoid editing the source by
adding
CFLAGS='-DFFEPROJ_STRTOUL=0 -g -O'
to the command line for `make' when you invoke it. (`-g' is the
default for `CFLAGS'.)
This causes a minimal version of `strtoul()' provided as part of the
`g77' distribution to be compiled and linked into whatever `g77'
programs need it, since some systems (like SunOS4 with only the bundled
compiler and its runtime) do not provide this function in their system
libraries.
Similarly, a minimal version of `bsearch()' is available and can be
enabled by editing a line similar to the one for `strtoul()' above in
`gcc/f/proj.h', if your system libraries lack `bsearch()'. The method
of overriding `X_CFLAGS' may also be used.
These are not problems with `g77', which requires an ANSI C
environment. You should upgrade your system to one that provides a
full ANSI C environment, or encourage the maintainers of `gcc' to
provide one to all `gcc'-based compilers in future `gcc' distributions.
*Note Problems Installing::, for more information on why `strtoul()'
comes up missing and on approaches to dealing with this problem that
have already been tried.
Where in the World Does Fortran (and GNU CC) Go? Where in the World Does Fortran (and GNU CC) Go?
------------------------------------------------ ------------------------------------------------
...@@ -1128,8 +930,8 @@ Where in the World Does Fortran (and GNU CC) Go? ...@@ -1128,8 +930,8 @@ Where in the World Does Fortran (and GNU CC) Go?
this information is given to the configuration tool and used during the this information is given to the configuration tool and used during the
build itself. build itself.
A `g77' installation necessarily requires installation of a A `g77' installation normally includes installation of a
`g77'-aware version of `gcc', so that the `gcc' command recognizes Fortran-aware version of `gcc', so that the `gcc' command recognizes
Fortran source files and knows how to compile them. Fortran source files and knows how to compile them.
For this to work, the version of `gcc' that you will be building as For this to work, the version of `gcc' that you will be building as
...@@ -1138,24 +940,27 @@ the system. ...@@ -1138,24 +940,27 @@ the system.
Sometimes people make the mistake of installing `gcc' as Sometimes people make the mistake of installing `gcc' as
`/usr/local/bin/gcc', leaving an older, non-Fortran-aware version in `/usr/local/bin/gcc', leaving an older, non-Fortran-aware version in
`/usr/bin/gcc'. (Or, the opposite happens.) This can result in `g77' `/usr/bin/gcc'. (Or, the opposite happens.) This can result in `gcc'
being unable to compile Fortran source files, because when it calls on being unable to compile Fortran source files, because when the older
`gcc' to do the actual compilation, `gcc' complains that it does not version of `gcc' is invoked, it complains that it does not recognize
recognize the language, or the file name suffix. the language, or the file name suffix.
So, determine whether `gcc' already is installed on your system, So, determine whether `gcc' already is installed on your system,
and, if so, *where* it is installed, and prepare to configure the new and, if so, *where* it is installed, and prepare to configure the new
version of `gcc' you'll be building so that it installs over the version of `gcc' you'll be building so that it installs over the
existing version of `gcc'. existing version of `gcc'.
You might want to back up your existing copy of `bin/gcc', and the You might want to back up your existing copy of `/usr/bin/gcc', and
entire `lib/' directory, before you perform the actual installation (as the entire `/usr/lib' directory, before you perform the actual
described in this manual). installation (as described in this manual).
Existing `gcc' installations typically are found in `/usr' or Existing `gcc' installations typically are found in `/usr' or
`/usr/local'. If you aren't certain where the currently installed `/usr/local'. (This means the commands are installed in `/usr/bin' or
version of `gcc' and its related programs reside, look at the output of `/usr/local/bin', the libraries in `/usr/lib' or `/usr/local/lib', and
this command: so on.)
If you aren't certain where the currently installed version of `gcc'
and its related programs reside, look at the output of this command:
gcc -v -o /tmp/delete-me -xc /dev/null -xnone gcc -v -o /tmp/delete-me -xc /dev/null -xnone
...@@ -1174,7 +979,8 @@ true for any package, not just `g77', though in this case it is ...@@ -1174,7 +979,8 @@ true for any package, not just `g77', though in this case it is
intentional that `g77' overwrites `gcc' if it is already installed--it intentional that `g77' overwrites `gcc' if it is already installed--it
is unusual that the installation process for one distribution is unusual that the installation process for one distribution
intentionally overwrites a program or file installed by another intentionally overwrites a program or file installed by another
distribution.) distribution, although, in this case, `g77' is an augmentation of the
`gcc' distribution.)
Another reason to back up the existing version first, or make sure Another reason to back up the existing version first, or make sure
you can restore it easily, is that it might be an older version on you can restore it easily, is that it might be an older version on
...@@ -1191,12 +997,12 @@ Configuring GNU CC ...@@ -1191,12 +997,12 @@ Configuring GNU CC
`g77' is configured automatically when you configure `gcc'. There `g77' is configured automatically when you configure `gcc'. There
are two parts of `g77' that are configured in two different are two parts of `g77' that are configured in two different
ways--`g77', which "camps on" to the `gcc' configuration mechanism, and ways--`g77', which "camps on" to the `gcc' configuration mechanism, and
`libf2c', which uses a variation of the GNU `autoconf' configuration `libg2c', which uses a variation of the GNU `autoconf' configuration
system. system.
Generally, you shouldn't have to be concerned with either `g77' or Generally, you shouldn't have to be concerned with either `g77' or
`libf2c' configuration, unless you're configuring `g77' as a `libg2c' configuration, unless you're configuring `g77' as a
cross-compiler. In this case, the `libf2c' configuration, and possibly cross-compiler. In this case, the `libg2c' configuration, and possibly
the `g77' and `gcc' configurations as well, might need special the `g77' and `gcc' configurations as well, might need special
attention. (This also might be the case if you're porting `gcc' to a attention. (This also might be the case if you're porting `gcc' to a
whole new system--even if it is just a new operating system on an whole new system--even if it is just a new operating system on an
...@@ -1207,19 +1013,27 @@ existing, supported CPU.) ...@@ -1207,19 +1013,27 @@ existing, supported CPU.)
Pay special attention to the `--prefix=' option, which you almost Pay special attention to the `--prefix=' option, which you almost
certainly will need to specify. certainly will need to specify.
(Note that `gcc' installation information is provided as a straight (Note that `gcc' installation information is provided as a
text file in `gcc/INSTALL'.) plain-text file in `gcc/INSTALL'.)
The information printed by the invocation of `./configure' should The information printed by the invocation of `./configure' should
show that the `f' directory (the Fortran language) has been configured. show that the `f' directory (the Fortran language) has been configured.
If it does not, there is a problem. If it does not, there is a problem.
*Note:* Configuring with the `--srcdir' argument is known to work *Note:* Configuring with the `--srcdir' argument, or by starting in
with GNU `make', but it is not known to work with other variants of an empty directory and typing a command such as `../gcc/configure' to
`make'. Irix5.2 and SunOS4.1 versions of `make' definitely won't work build with separate build and source directories, is known to work with
outside the source directory at present. `g77''s portion of the GNU `make', but it is known to not work with other variants of `make'.
`configure' script issues a warning message about this when you Irix5.2 and SunOS4.1 versions of `make' definitely won't work outside
configure for building binaries outside the source directory. the source directory at present.
`g77''s portion of the `configure' script used to issue a warning
message about this when configuring for building binaries outside the
source directory, but no longer does this as of version 0.5.23.
Instead, `g77' simply rejects most common attempts to build it using
a non-GNU `make' when the build directory is not the same as the source
directory, issuing an explanatory diagnostic.
Building GNU CC Building GNU CC
--------------- ---------------
...@@ -1232,14 +1046,14 @@ or `gcc/Makefile', but if you do that, you're on your own. One change ...@@ -1232,14 +1046,14 @@ or `gcc/Makefile', but if you do that, you're on your own. One change
is almost *certainly* going to cause failures: removing `c' or `f77' is almost *certainly* going to cause failures: removing `c' or `f77'
from the definition of the `LANGUAGES' macro. from the definition of the `LANGUAGES' macro.
After configuring `gcc', which configures `g77' and `libf2c' After configuring `gcc', which configures `g77' and `libg2c'
automatically, you're ready to start the actual build by invoking automatically, you're ready to start the actual build by invoking
`make'. `make'.
*Note:* You *must* have run `./configure' before you run `make', *Note:* You *must* have run the `configure' script in `gcc' before
even if you're using an already existing `gcc' development directory, you run `make', even if you're using an already existing `gcc'
because `./configure' does the work to recognize that you've added development directory, because `./configure' does the work to recognize
`g77' to the configuration. that you've added `g77' to the configuration.
There are two general approaches to building GNU CC from scratch: There are two general approaches to building GNU CC from scratch:
...@@ -1285,12 +1099,6 @@ large number of object files to ensure they're identical). ...@@ -1285,12 +1099,6 @@ large number of object files to ensure they're identical).
you can type `rm -fr stage1' to remove the binaries built during Stage you can type `rm -fr stage1' to remove the binaries built during Stage
1. 1.
*Note:* *Note Object File Differences::, for information on expected
differences in object files produced during Stage 2 and Stage 3 of a
bootstrap build. These differences will be encountered as a result of
using the `make compare' or similar command sequence recommended by the
GNU CC installation documentation.
Also, *Note Installing GNU CC: (gcc)Installation, for important Also, *Note Installing GNU CC: (gcc)Installation, for important
information on building `gcc' that is not described in this `g77' information on building `gcc' that is not described in this `g77'
manual. For example, explanations of diagnostic messages and whether manual. For example, explanations of diagnostic messages and whether
...@@ -1305,15 +1113,10 @@ object-compatible with the version of `gcc' you want to build as part ...@@ -1305,15 +1113,10 @@ object-compatible with the version of `gcc' you want to build as part
of building `g77', you can save time and disk space by doing a straight of building `g77', you can save time and disk space by doing a straight
build. build.
To build just the C and Fortran compilers and the necessary run-time To build just the compilers along with the necessary run-time
libraries, issue the following command: libraries, issue the following command:
make -k CC=gcc LANGUAGES=f77 all g77 make -k CC=gcc
(The `g77' target is necessary because the `gcc' build procedures
apparently do not automatically build command drivers for languages in
subdirectories. It's the `all' target that triggers building
everything except, apparently, the `g77' command itself.)
If you run into problems using this method, you have two options: If you run into problems using this method, you have two options:
...@@ -1328,7 +1131,8 @@ Fortran: Trouble. ...@@ -1328,7 +1131,8 @@ Fortran: Trouble.
However, understand that many problems preventing a straight build However, understand that many problems preventing a straight build
from working are not `g77' problems, and, in such cases, are not likely from working are not `g77' problems, and, in such cases, are not likely
to be addressed in future versions of `g77'. to be addressed in future versions of `g77'. Consider treating them as
`gcc' bugs instead.
Pre-installation Checks Pre-installation Checks
----------------------- -----------------------
...@@ -1341,52 +1145,51 @@ work. ...@@ -1341,52 +1145,51 @@ work.
them when they work: them when they work:
sh# cd /usr/src/gcc sh# cd /usr/src/gcc
sh# ./g77 --driver=./xgcc -B./ -v sh# ./g77 -B./ -v
g77 version 0.5.22 g77 version 0.5.24
./xgcc -B./ -v -fnull-version -o /tmp/gfa18047 ... Driving: ./g77 -B./ -v -c -xf77-version /dev/null -xnone
Reading specs from ./specs Reading specs from ./specs
gcc version 2.7.2.3.f.2 gcc version 2.8.1
./cpp -lang-c -v -isystem ./include -undef ... cpp -lang-c -v -isystem ./include -undef -D__GNUC__=2 ...
GNU CPP version 2.7.2.3.f.2 (Linux/Alpha) GNU CPP version 2.8.1 (Alpha GNU/Linux with ELF)
#include "..." search starts here: #include "..." search starts here:
#include <...> search starts here: #include <...> search starts here:
./include include
/usr/local/include /usr/alpha-linux/include
/usr/alpha-unknown-linux/include /usr/lib/gcc-lib/alpha-linux/2.8.1/include
/usr/lib/gcc-lib/alpha-unknown-linux/2.7.2.3.f.2/include
/usr/include /usr/include
End of search list. End of search list.
./f771 /tmp/cca18048.i -fset-g77-defaults -quiet -dumpbase ... ./f771 -fnull-version -quiet -dumpbase g77-version.f -version ...
GNU F77 version 2.7.2.3.f.2 (Linux/Alpha) compiled ... GNU F77 version 2.8.1 (alpha-linux) compiled ...
GNU Fortran Front End version 0.5.22 compiled: ... GNU Fortran Front End version 0.5.24
as -nocpp -o /tmp/cca180481.o /tmp/cca18048.s as -nocpp -o /tmp/cca14485.o /tmp/cca14485.s
ld -G 8 -O1 -o /tmp/gfa18047 /usr/lib/crt0.o -L. ... ld -m elf64alpha -G 8 -O1 -dynamic-linker /lib/ld-linux.so.2 ...
__G77_LIBF77_VERSION__: 0.5.22 /tmp/cca14485
@(#)LIBF77 VERSION 19970404 __G77_LIBF77_VERSION__: 0.5.24
__G77_LIBI77_VERSION__: 0.5.22 @(#)LIBF77 VERSION 19970919
@(#) LIBI77 VERSION pjw,dmg-mods 19970816 __G77_LIBI77_VERSION__: 0.5.24
__G77_LIBU77_VERSION__: 0.5.22 @(#) LIBI77 VERSION pjw,dmg-mods 19980405
@(#) LIBU77 VERSION 19970609 __G77_LIBU77_VERSION__: 0.5.24
@(#) LIBU77 VERSION 19970919
sh# ./xgcc -B./ -v -o /tmp/delete-me -xc /dev/null -xnone sh# ./xgcc -B./ -v -o /tmp/delete-me -xc /dev/null -xnone
Reading specs from ./specs Reading specs from ./specs
gcc version 2.7.2.3.f.2 gcc version 2.8.1
./cpp -lang-c -v -isystem ./include -undef ... ./cpp -lang-c -v -isystem ./include -undef ...
GNU CPP version 2.7.2.3.f.2 (Linux/Alpha) GNU CPP version 2.8.1 (Alpha GNU/Linux with ELF)
#include "..." search starts here: #include "..." search starts here:
#include <...> search starts here: #include <...> search starts here:
./include include
/usr/local/include /usr/alpha-linux/include
/usr/alpha-unknown-linux/include /usr/lib/gcc-lib/alpha-linux/2.8.1/include
/usr/lib/gcc-lib/alpha-unknown-linux/2.7.2.3.f.2/include
/usr/include /usr/include
End of search list. End of search list.
./cc1 /tmp/cca18063.i -quiet -dumpbase null.c -version ... ./cc1 /tmp/cca18063.i -quiet -dumpbase null.c -version ...
GNU C version 2.7.2.3.f.2 (Linux/Alpha) compiled ... GNU C version 2.8.1 (alpha-linux) compiled ...
as -nocpp -o /tmp/cca180631.o /tmp/cca18063.s as -nocpp -o /tmp/cca180631.o /tmp/cca18063.s
ld -G 8 -O1 -o /tmp/delete-me /usr/lib/crt0.o -L. ... ld -m elf64alpha -G 8 -O1 -dynamic-linker /lib/ld-linux.so.2 ...
/usr/lib/crt0.o: In function `__start': /usr/lib/crt1.o: In function `_start':
crt0.S:110: undefined reference to `main' ../sysdeps/alpha/elf/start.S:77: undefined reference to `main'
/usr/lib/crt0.o(.lita+0x28): undefined reference to `main' ../sysdeps/alpha/elf/start.S:77: undefined reference to `main'
sh# sh#
(Note that long lines have been truncated, and `...' used to (Note that long lines have been truncated, and `...' used to
...@@ -1410,7 +1213,7 @@ use the following commands to invoke them. ...@@ -1410,7 +1213,7 @@ use the following commands to invoke them.
To invoke `g77', type: To invoke `g77', type:
/usr/src/gcc/g77 --driver=/usr/src/gcc/xgcc -B/usr/src/gcc/ ... /usr/src/gcc/g77 -B/usr/src/gcc/ ...
To invoke `gcc', type: To invoke `gcc', type:
...@@ -1422,7 +1225,7 @@ Installation of Binaries ...@@ -1422,7 +1225,7 @@ Installation of Binaries
After configuring, building, and testing `g77' and `gcc', when you After configuring, building, and testing `g77' and `gcc', when you
are ready to install them on your system, type: are ready to install them on your system, type:
make -k CC=gcc LANGUAGES=f77 install make -k CC=gcc install
As described in *Note Installing GNU CC: (gcc)Installation, the As described in *Note Installing GNU CC: (gcc)Installation, the
values for the `CC' and `LANGUAGES' macros should be the same as those values for the `CC' and `LANGUAGES' macros should be the same as those
...@@ -1434,83 +1237,179 @@ might have to supply the same definitions you used when building the ...@@ -1434,83 +1237,179 @@ might have to supply the same definitions you used when building the
final stage) or if you deviated from the instructions for a straight final stage) or if you deviated from the instructions for a straight
build. build.
If the above command does not install `libf2c.a' as expected, try If the above command does not install `libg2c.a' as expected, try
this: this:
make -k ... install install-libf77 install-f2c-all make -k ... install install-libf77
We don't know why some non-GNU versions of `make' sometimes require We don't know why some non-GNU versions of `make' sometimes require
this alternate command, but they do. (Remember to supply the this alternate command, but they do. (Remember to supply the
appropriate definitions for `CC' and `LANGUAGES' where you see `...' in appropriate definition for `CC' where you see `...' in the above
the above command.) command.)
Note that using the `-k' option tells `make' to continue after some Note that using the `-k' option tells `make' to continue after some
installation problems, like not having `makeinfo' installed on your installation problems, like not having `makeinfo' installed on your
system. It might not be necessary for your system. system. It might not be necessary for your system.
*Note:* `g77' no longer installs files not directly part of `g77',
such as `/usr/bin/f77', `/usr/lib/libf2c.a', and `/usr/include/f2c.h',
or their `/usr/local' equivalents.
*Note Distributing Binaries::, for information on how to accommodate
systems with no existing non-`g77' `f77' compiler and systems with
`f2c' installed.
Updating Your Info Directory Updating Your Info Directory
---------------------------- ----------------------------
As part of installing `g77', you should make sure users of `info' As part of installing `g77', you should make sure users of `info'
can easily access this manual on-line. Do this by making sure a line can easily access this manual on-line.
such as the following exists in `/usr/info/dir', or in whatever file is
the top-level file in the `info' directory on your system (perhaps `g77' does this automatically by invoking the `install-info' command
`/usr/local/info/dir': when you use `make install' to install `g77'.
If that fails, or if the `info' directory it updates is not the one
normally accessed by users, consider invoking it yourself. For example:
install-info --info-dir=/usr/info /usr/info/g77.info
The above example assumes the `g77' documentation already is
installed in `/usr/info' and that `/usr/info/dir' is the file you wish
to update. Adjust the command accordingly, if those assumptions are
wrong.
Missing tools?
--------------
A build of `gcc' might fail due to one or more tools being called
upon by `make' (during the build or install process), when those tools
are not installed on your system.
This situation can result from any of the following actions
(performed by you or someone else):
* Changing the source code or documentation yourself (as a developer
or technical writer).
* Applying a patch that changes the source code or documentation
(including, sometimes, the official patches distributed by the
FSF).
* Deleting the files that are created by the (missing) tools.
The `make maintainer-clean' command is supposed to delete these
files, so invoking this command without having all the appropriate
tools installed is not recommended.
* Creating the source directory using a method that does not
preserve the date-time-modified information in the original
distribution.
For example, the UNIX `cp -r' command copies a directory tree
without preserving the date-time-modified information. Use `cp
-pr' instead.
The reason these activities cause `make' to try and invoke tools
that it probably wouldn't when building from a perfectly "clean" source
directory containing `gcc' and `g77' is that some files in the source
directory (and the corresponding distribution) aren't really source
files, but *derived* files that are produced by running tools with the
corresponding source files as input. These derived files "depend", in
`make' terminology, on the corresponding source files.
* g77: (g77). The GNU Fortran programming language. `make' determines that a file that depends on another needs to be
updated if the date-time-modified information for the source file shows
that it is newer than the corresponding information for the derived
file.
If the menu in `dir' is organized into sections, `g77' probably If it makes that determination, `make' runs the appropriate commands
belongs in a section with a name such as one of the following: (specified in the "Makefile") to update the derived file, and this
process typically calls upon one or more installed tools to do the work.
* Fortran Programming The "safest" approach to dealing with this situation is to recreate
the `gcc' and `g77' source directories from complete `gcc' and `g77'
distributions known to be provided by the FSF.
* Writing Programs Another fairly "safe" approach is to simply install the tools you
need to complete the build process. This is especially appropriate if
you've changed the source code or applied a patch to do so.
* Programming Languages However, if you're certain that the problem is limited entirely to
incorrect date-time-modified information, that there are no
discrepancies between the contents of source files and files derived
from them in the source directory, you can often update the
date-time-modified information for the derived files to work around the
problem of not having the appropriate tools installed.
* Languages Other Than C On UNIX systems, the simplest way to update the date-time-modified
information of a file is to use the use the `touch' command.
* Scientific/Engineering Tools How to use `touch' to update the derived files updated by each of
the tools is described below. *Note:* New versions of `g77' might
change the set of files it generates by invoking each of these tools.
If you cannot figure out for yourself how to handle such a situation,
try an older version of `g77' until you find someone who can (or until
you obtain and install the relevant tools).
* GNU Compilers Missing `autoconf'?
...................
If you cannot install `autoconf', make sure you have started with a
*fresh* distribution of `gcc' and `g77', do *not* do `make
maintainer-clean', and, to ensure that `autoconf' is not invoked by
`make' during the build, type these commands:
sh# cd gcc/f/runtime
sh# touch configure libU77/configure
sh# cd ../../..
sh#
Missing `bison'? Missing `bison'?
---------------- ................
If you cannot install `bison', make sure you have started with a If you cannot install `bison', make sure you have started with a
*fresh* distribution of `gcc', do *not* do `make maintainer-clean' (in *fresh* distribution of `gcc', do *not* do `make maintainer-clean',
other versions of `gcc', this was called `make realclean'), and, to and, to ensure that `bison' is not invoked by `make' during the build,
ensure that `bison' is not invoked by `make' during the build, type type these commands:
these commands:
sh# cd gcc sh# cd gcc
sh# touch c-parse.c c-parse.h cexp.c sh# touch bi-parser.c bi-parser.h c-parse.c c-parse.h cexp.c
sh# touch cp/parse.c cp/parse.h objc-parse.c sh# touch cp/parse.c cp/parse.h objc-parse.c
sh# cd ..
sh# sh#
These commands update the date-time-modified information for all the Missing `gperf'?
files produced by the various invocations of `bison' in the current ................
versions of `gcc', so that `make' no longer believes it needs to update
them. All of these files should already exist in a `gcc' distribution,
but the application of patches to upgrade to a newer version can leave
the modification information set such that the `bison' input files look
more "recent" than the corresponding output files.
*Note:* New versions of `gcc' might change the set of files it If you cannot install `gperf', make sure you have started with a
generates by invoking `bison'--if you cannot figure out for yourself *fresh* distribution of `gcc', do *not* do `make maintainer-clean',
how to handle such a situation, try an older version of `gcc' until you and, to ensure that `gperf' is not invoked by `make' during the build,
find someone who can (or until you obtain and install `bison'). type these commands:
sh# cd gcc
sh# touch c-gperf.h
sh# cd ..
sh#
Missing `makeinfo'? Missing `makeinfo'?
------------------- ...................
If `makeinfo' is needed but unavailable when installing (via `make
install'), some files, like `libg2c.a', might not be installed, because
once `make' determines that it cannot invoke `makeinfo', it cancels any
further processing.
If you cannot install `makeinfo', either use the `-k' option when If you cannot install `makeinfo', an easy work-around is to specify
invoking make to specify any of the `install' or related targets, or `MAKEINFO=true' on the `make' command line, or to specify the `-k'
specify `MAKEINFO=echo' on the `make' command line. option (`make -k install').
If you fail to do one of these things, some files, like `libf2c.a', Another approach is to force the relevant files to be up-to-date by
might not be installed, because the failed attempt by `make' to invoke typing these commands and then re-trying the installation step:
`makeinfo' causes it to cancel any further processing.
sh# cd gcc
sh# touch f/g77.info f/BUGS f/INSTALL f/NEWS
sh# cd ..
sh#
Distributing Binaries Distributing Binaries
===================== =====================
...@@ -1526,33 +1425,62 @@ installed. ...@@ -1526,33 +1425,62 @@ installed.
where `g77' could be considered the native compiler for Fortran and where `g77' could be considered the native compiler for Fortran and
`gcc' for C, etc.), you should definitely configure `g77' for `gcc' for C, etc.), you should definitely configure `g77' for
installation in `/usr/bin' instead of `/usr/local/bin'. Specify the installation in `/usr/bin' instead of `/usr/local/bin'. Specify the
`--prefix=/usr' option when running `./configure'. You might also want `--prefix=/usr' option when running `./configure'.
to set up the distribution so the `f77' command is a link to
`g77'--just make an empty file named `f77-install-ok' in the source or You might also want to set up the distribution so the `f77' command
build directory (the one in which the `f' directory resides, not the is a link to `g77', although a script that accepts "classic" UNIX `f77'
`f' directory itself) when you specify one of the `install' or options and translates the command-line to the appropriate `g77'
`uninstall' targets in a `make' command. command line would be more appropriate. If you do this, *please* also
provide a "man page" in `man/man1/f77.1' describing the command. (A
For a system that might already have `f2c' installed, you definitely link to `man/man1/g77.1' is appropriate if `bin/f77' is a link to
will want to make another empty file (in the same directory) named `bin/g77'.)
either `f2c-exists-ok' or `f2c-install-ok'. Use the former if you
don't want your distribution to overwrite `f2c'-related files in For a system that might already have `f2c' installed, consider
existing systems; use the latter if you want to improve the likelihood whether inter-operation with `g77' will be important to users of `f2c'
that users will be able to use both `f2c' and `g77' to compile code for on that system. If you want to improve the likelihood that users will
a single program without encountering link-time or run-time be able to use both `f2c' and `g77' to compile code for a single program
incompatibilities. without encountering link-time or run-time incompatibilities, make sure
that, whenever they intend to combine `f2c'-produced code with
(Make sure you clearly document, in the "advertising" for your `g77'-produced code in an executable, they:
* Use the `lib/gcc-lib/.../include/g2c.h' file generated by the
`g77' build in place of the `f2c.h' file that normally comes with
`f2c' (or versions of `g77' prior to 0.5.23) when compiling *all*
of the `f2c'-produced C code
* Link to the `lib/gcc-lib/.../libg2c.a' library built by the `g77'
build instead of the `libf2c.a' library that normally comes with
`f2c' (or versions of `g77' prior to 0.5.23)
How you choose to effect the above depends on whether the existing
installation of `f2c' must be maintained.
In any case, it is important to try and ensure that the installation
keeps working properly even after subsequent re-installation of `f2c',
which probably involves overwriting `/usr/local/lib/libf2c.a' and
`/usr/local/include/f2c.h', or similar.
At least, copying `libg2c.a' and `g2c.h' into the appropriate
"public" directories allows users to more easily select the version of
`libf2c' they wish to use for a particular build. The names are
changed by `g77' to make this coexistence easier to maintain; even if
`f2c' is installed later, the `g77' files normally installed by its
installation process aren't disturbed. Use of symbolic links from one
set of files to another might result in problems after a subsequent
reinstallation of either `f2c' or `g77', so be sure to alert users of
your distribution accordingly.
(Make sure you clearly document, in the description of your
distribution, how installation of your distribution will affect distribution, how installation of your distribution will affect
existing installations of `gcc', `f2c', `f77', `libf2c.a', and so on. existing installations of `gcc', `f2c', `f77', `libf2c.a', and so on.
Similarly, you should clearly document any requirements you assume are Similarly, you should clearly document any requirements you assume will
met by users of your distribution.) be met by users of your distribution.)
For other systems with native `f77' (and `cc') compilers, configure For other systems with native `f77' (and `cc') compilers, configure
`g77' as you (or most of your audience) would configure `gcc' for their `g77' as you (or most of your audience) would configure `gcc' for their
installations. Typically this is for installation in `/usr/local', and installations. Typically this is for installation in `/usr/local', and
would not include a copy of `g77' named `f77', so users could still use would not include a new version of `/usr/bin/f77' or
the native `f77'. `/usr/local/bin/f77', so users could still use the native `f77'.
In any case, for `g77' to work properly, you *must* ensure that the In any case, for `g77' to work properly, you *must* ensure that the
binaries you distribute include: binaries you distribute include:
...@@ -1561,17 +1489,11 @@ binaries you distribute include: ...@@ -1561,17 +1489,11 @@ binaries you distribute include:
This is the command most users use to compile Fortran. This is the command most users use to compile Fortran.
`bin/gcc' `bin/gcc'
This is the command all users use to compile Fortran, either This is the command some users use to compile Fortran, typically
directly or indirectly via the `g77' command. The `bin/gcc' when compiling programs written in other languages at the same
executable file must have been built from a `gcc' source tree into time. The `bin/gcc' executable file must have been built from a
which a `g77' source tree was merged and configured, or it will `gcc' source tree into which a `g77' source tree was merged and
not know how to compile Fortran programs. configured, or it will not know how to compile Fortran programs.
`bin/f77'
In installations with no non-GNU native Fortran compiler, this is
the same as `bin/g77'. Otherwise, it should be omitted from the
distribution, so the one on already on a particular system does
not get overwritten.
`info/g77.info*' `info/g77.info*'
This is the documentation for `g77'. If it is not included, users This is the documentation for `g77'. If it is not included, users
...@@ -1591,35 +1513,36 @@ binaries you distribute include: ...@@ -1591,35 +1513,36 @@ binaries you distribute include:
Documentation. Documentation.
`man/man1/g77.1' `man/man1/g77.1'
This is the short man page for `g77'. It is out of date, but you This is the short man page for `g77'. It is not always kept
might as well include it for people who really like man pages. up-to-date, but you might as well include it for people who really
like "man" pages.
`man/man1/f77.1' `lib/gcc-lib'
In installations where `f77' is the same as `g77', this is the This is the directory containing the "private" files installed by
same as `man/man1/g77.1'. Otherwise, it should be omitted from and for `gcc', `g77', `g++', and other GNU compilers.
the distribution, so the one already on a particular system does
not get overwritten.
`lib/gcc-lib/.../f771' `lib/gcc-lib/.../f771'
This is the actual Fortran compiler. This is the actual Fortran compiler.
`lib/gcc-lib/.../libf2c.a' `lib/gcc-lib/.../libg2c.a'
This is the run-time library for `g77'-compiled programs. This is the run-time library for `g77'-compiled programs.
Whether you want to include the slightly updated (and possibly Whether you want to include the slightly updated (and possibly
improved) versions of `cc1', `cc1plus', and whatever other binaries get improved) versions of `cc1', `cc1plus', and whatever other binaries get
rebuilt with the changes the GNU Fortran distribution makes to the GNU rebuilt with the changes the GNU Fortran distribution makes to the GNU
back end, is up to you. These changes are highly unlikely to break any back end, is up to you. These changes are highly unlikely to break any
compilers, and it is possible they'll fix back-end bugs that can be compilers, because they involve doing things like adding to the list of
demonstrated using front ends other than GNU Fortran's. acceptable compiler options (so, for example, `cc1plus' accepts, and
ignores, options that only `f771' actually processes).
Please assure users that unless they have a specific need for their Please assure users that unless they have a specific need for their
existing, older versions of `gcc' command, they are unlikely to existing, older versions of `gcc' command, they are unlikely to
experience any problems by overwriting it with your version--though experience any problems by overwriting it with your version--though
they could certainly protect themselves by making backup copies first! they could certainly protect themselves by making backup copies first!
Otherwise, users might try and install your binaries in a "safe" place,
find they cannot compile Fortran programs with your distribution Otherwise, users might try and install your binaries in a "safe"
(because, perhaps, they're picking up their old version of the `gcc' place, find they cannot compile Fortran programs with your distribution
(because, perhaps, they're invoking their old version of the `gcc'
command, which does not recognize Fortran programs), and assume that command, which does not recognize Fortran programs), and assume that
your binaries (or, more generally, GNU Fortran distributions in your binaries (or, more generally, GNU Fortran distributions in
general) are broken, at least for their system. general) are broken, at least for their system.
......
gcc/f/NEWS
...@@ -11,9 +11,10 @@ with the most recent version first. ...@@ -11,9 +11,10 @@ with the most recent version first.
The changes are generally listed in order: The changes are generally listed in order:
1. Code-generation and run-time-library bugs 1. Code-generation and run-time-library bug-fixes
2. Compiler and run-time-library crashes involving valid code 2. Compiler and run-time-library crashes involving valid code that
have been fixed
3. New features 3. New features
...@@ -28,6 +29,175 @@ with the most recent version first. ...@@ -28,6 +29,175 @@ with the most recent version first.
This order is not strict--for example, some items involve a This order is not strict--for example, some items involve a
combination of these elements. combination of these elements.
In `egcs' 1.1:
==============
* `g77' no longer produces incorrect code and initial values for
`EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural"
ordering of members vis-a-vis their types, require initial padding.
* `g77' no longer crashes when compiling code containing
specification statements such as `INTEGER(KIND=7) PTR'.
* `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
expressions when they are used as arguments in procedure calls.
This change applies only to global (filewide) analysis, making it
consistent with how `g77' actually generates code for these cases.
Previously, `g77' treated these expressions as denoting special
"pointer" arguments for the purposes of filewide analysis.
* The `g77' driver now ensures that `-lg2c' is specified in the link
phase prior to any occurrence of `-lm'. This prevents
accidentally linking to a routine in the SunOS4 `-lm' library when
the generated code wants to link to the one in `libf2c' (`libg2c').
* `g77' emits more debugging information when `-g' is used.
This new information allows, for example, `which __g77_length_a'
to be used in `gdb' to determine the type of the phantom length
argument supplied with `CHARACTER' variables.
This information pertains to internally-generated type, variable,
and other information, not to the longstanding deficiencies
vis-a-vis `COMMON' and `EQUIVALENCE'.
* The F90 `DATE_AND_TIME' intrinsic now is supported.
* The F90 `SYSTEM_CLOCK' intrinsic allows the optional arguments
(except for the `Count' argument) to be omitted.
* Upgrade to `libf2c' as of 1998-06-18.
* Improve documentation and indexing.
In 0.5.23:
==========
* This release contains several regressions against version 0.5.22
of `g77', due to using the "vanilla" `gcc' back end instead of
patching it to fix a few bugs and improve performance in a few
cases.
*Note Actual Bugs We Haven't Fixed Yet: Actual Bugs, available in
plain-text format in `gcc/f/BUGS', for information on the known
bugs in this version, including the regressions.
Features that have been dropped from this version of `g77' due to
their being implemented via `g77'-specific patches to the `gcc'
back end in previous releases include:
- Support for `__restrict__' keyword, the options
`-fargument-alias', `-fargument-noalias', and
`-fargument-noalias-global', and the corresponding
alias-analysis code.
(Version 1.0.1 of `egcs' has the alias-analysis code, but not
the `__restrict__' keyword. `egcs' `g77' users benefit from
the alias-analysis code despite the lack of the
`__restrict__' keyword, which is a C-language construct.)
- Support for the GNU compiler options `-fmove-all-movables',
`-freduce-all-givs', and `-frerun-loop-opt'.
(Version 1.0.1 of `egcs' supports these options. `g77' users
of `egcs' benefit from them even if they are not explicitly
specified, because the defaults are optimized for `g77'
users.)
- Support for the `-W' option warning about integer division by
zero.
- The Intel x86-specific option `-malign-double' applying to
stack-allocated data as well as statically-allocate data.
Note that the `gcc/f/gbe/' subdirectory has been removed from this
distribution as a result of `g77' no longer including patches for
the `gcc' back end.
* Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
beyond the end of its `CHARACTER' argument, and in the `libU77'
intrinsics `GMTime' and `LTime' that overwrote their arguments.
* Support `gcc' version 2.8, and remove support for prior versions
of `gcc'.
* Remove support for the `--driver' option, as `g77' now does all
the driving, just like `gcc'.
* `CASE DEFAULT' no longer crashes `g77'.
* Valid combinations of `EXTERNAL', passing that external as a dummy
argument without explicitly giving it a type, and, in a subsequent
program unit, referencing that external as an external function
with a different type no longer crash `g77'.
* `g77' no longer installs the `f77' command and `f77.1' man page in
the `/usr' or `/usr/local' heirarchy, even if the `f77-install-ok'
file exists in the source or build directory. See the
installation documentation for more information.
* `g77' no longer installs the `libf2c.a' library and `f2c.h'
include file in the `/usr' or `/usr/local' heirarchy, even if the
`f2c-install-ok' or `f2c-exists-ok' files exist in the source or
build directory. See the installation documentation for more
information.
* The `libf2c.a' library produced by `g77' has been renamed to
`libg2c.a'. It is installed only in the `gcc' "private" directory
heirarchy, `gcc-lib'. This allows system administrators and users
to choose which version of the `libf2c' library from `netlib' they
wish to use on a case-by-case basis. See the installation
documentation for more information.
* The `f2c.h' include (header) file produced by `g77' has been
renamed to `g2c.h'. It is installed only in the `gcc' "private"
directory heirarchy, `gcc-lib'. This allows system administrators
and users to choose which version of the include file from
`netlib' they wish to use on a case-by-case basis. See the
installation documentation for more information.
* The `g77' command now expects the run-time library to be named
`libg2c.a' instead of `libf2c.a', to ensure that a version other
than the one built and installed as part of the same `g77' version
is picked up.
* The `-Wunused' option no longer issues a spurious warning about
the "master" procedure generated by `g77' for procedures
containing `ENTRY' statements.
* `g77''s version of `libf2c' separates out the setting of global
state (such as command-line arguments and signal handling) from
`main.o' into distinct, new library archive members.
This should make it easier to write portable applications that
have their own (non-Fortran) `main()' routine properly set up the
`libf2c' environment, even when `libf2c' (now `libg2c') is a
shared library.
* During the configuration and build process, `g77' creates
subdirectories it needs only as it needs them, thus avoiding
unnecessary creation of, for example, `stage1/f/runtime' when
doing a non-bootstrap build. Other cleaning up of the
configuration and build process has been performed as well.
* `install-info' now used to update the directory of Info
documentation to contain an entry for `g77' (during installation).
* Some diagnostics have been changed from warnings to errors, to
prevent inadvertent use of the resulting, probably buggy, programs.
These mostly include diagnostics about use of unsupported features
in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
about truncations of various sorts of constants.
* Improve documentation and indexing.
* Upgrade to `libf2c' as of 1998-04-20.
This should fix a variety of problems, including those involving
some uses of the `T' format specifier, and perhaps some build
(porting) problems as well.
In 0.5.22: In 0.5.22:
========== ==========
......
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