Skip to content

R
riscv-gcc-1
Commit bf1fc762 by Craig Burley
Options

Update NEWS derived file 

From-SVN: r25747
parent f8e1d0a1
Showing with 32 additions and 26 deletions
gcc/f/NEWS
...@@ -71,12 +71,18 @@ at `http://egcs.cygnus.com/onlinedocs/g77_news.html'. ...@@ -71,12 +71,18 @@ at `http://egcs.cygnus.com/onlinedocs/g77_news.html'.
In `egcs' 1.2 (versus 1.1.2): In `egcs' 1.2 (versus 1.1.2):
============================= =============================
1. Fix `g77' so it no longer crashes when compiling I/O statements 1. `g77' no longer generates bad code for assignments, or other
conversions, of `REAL' or `COMPLEX' constant expressions to type
`INTEGER(KIND=2)' (often referred to as `INTEGER*8').
For example, `INTEGER*8 J; J = 4E10' now works as documented.
2. Fix `g77' so it no longer crashes when compiling I/O statements
using keywords that define `INTEGER' values, such as `IOSTAT=J', using keywords that define `INTEGER' values, such as `IOSTAT=J',
where J is other than default `INTEGER' (such as `INTEGER*2'). where J is other than default `INTEGER' (such as `INTEGER*2').
Instead, it issues a diagnostic. Instead, it issues a diagnostic.
2. The `-ax' option is now obeyed when compiling Fortran programs. 3. The `-ax' option is now obeyed when compiling Fortran programs.
(It is passed to the `f771' driver.) (It is passed to the `f771' driver.)
* Source file names with the suffixes `.FOR' and `.FPP' now are * Source file names with the suffixes `.FOR' and `.FPP' now are
...@@ -89,11 +95,11 @@ In `egcs' 1.2 (versus 1.1.2): ...@@ -89,11 +95,11 @@ In `egcs' 1.2 (versus 1.1.2):
references to the implementations of these intrinsics using the references to the implementations of these intrinsics using the
`EXTERNAL' mechanism (which would avoid the new warnings). `EXTERNAL' mechanism (which would avoid the new warnings).
3. `g77' now warns about a reference to a function when the 4. `g77' now warns about a reference to a function when the
corresponding *subsequent* function program unit disagrees with corresponding *subsequent* function program unit disagrees with
the reference concerning the type of the function. the reference concerning the type of the function.
4. Improve documentation and indexing, including information on Year 5. Improve documentation and indexing, including information on Year
2000 (Y2K) compliance. 2000 (Y2K) compliance.
In 0.5.24 and `egcs' 1.1.2 (versus 0.5.23 and 1.1.1): In 0.5.24 and `egcs' 1.1.2 (versus 0.5.23 and 1.1.1):
...@@ -136,14 +142,14 @@ In 0.5.24 and `egcs' 1.1.1 (versus 0.5.23 and 1.1): ...@@ -136,14 +142,14 @@ In 0.5.24 and `egcs' 1.1.1 (versus 0.5.23 and 1.1):
In `egcs' 1.1 (versus 0.5.24): In `egcs' 1.1 (versus 0.5.24):
============================== ==============================
5. Fix `g77' crash compiling code containing the construct 6. Fix `g77' crash compiling code containing the construct
`CMPLX(0.)' or similar. `CMPLX(0.)' or similar.
6. Fix `g77' crash (or apparently infinite run-time) when compiling 7. Fix `g77' crash (or apparently infinite run-time) when compiling
certain complicated expressions involving `COMPLEX' arithmetic certain complicated expressions involving `COMPLEX' arithmetic
(especially multiplication). (especially multiplication).
7. Fix a code-generation bug that afflicted Intel x86 targets when 8. Fix a code-generation bug that afflicted Intel x86 targets when
`-O2' was specified compiling, for example, an old version of the `-O2' was specified compiling, for example, an old version of the
`DNRM2' routine. `DNRM2' routine.
...@@ -159,25 +165,25 @@ In `egcs' 1.1 (versus 0.5.24): ...@@ -159,25 +165,25 @@ In `egcs' 1.1 (versus 0.5.24):
In `egcs' 1.1 (versus `egcs' 1.0.3): In `egcs' 1.1 (versus `egcs' 1.0.3):
==================================== ====================================
8. Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte 9. Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
beyond the end of its `CHARACTER' argument, and in the `libU77' beyond the end of its `CHARACTER' argument, and in the `libU77'
intrinsics `GMTime' and `LTime' that overwrote their arguments. intrinsics `GMTime' and `LTime' that overwrote their arguments.
9. Assumed arrays with negative bounds (such as `REAL A(-1:*)') no 10. Assumed arrays with negative bounds (such as `REAL A(-1:*)') no
longer elicit spurious diagnostics from `g77', even on systems longer elicit spurious diagnostics from `g77', even on systems
with pointers having different sizes than integers. with pointers having different sizes than integers.
This bug is not known to have existed in any recent version of This bug is not known to have existed in any recent version of
`gcc'. It was introduced in an early release of `egcs'. `gcc'. It was introduced in an early release of `egcs'.
10. Valid combinations of `EXTERNAL', passing that external as a dummy 11. Valid combinations of `EXTERNAL', passing that external as a dummy
argument without explicitly giving it a type, and, in a subsequent argument without explicitly giving it a type, and, in a subsequent
program unit, referencing that external as an external function program unit, referencing that external as an external function
with a different type no longer crash `g77'. with a different type no longer crash `g77'.
11. `CASE DEFAULT' no longer crashes `g77'. 12. `CASE DEFAULT' no longer crashes `g77'.
12. The `-Wunused' option no longer issues a spurious warning about 13. The `-Wunused' option no longer issues a spurious warning about
the "master" procedure generated by `g77' for procedures the "master" procedure generated by `g77' for procedures
containing `ENTRY' statements. containing `ENTRY' statements.
...@@ -202,25 +208,25 @@ In `egcs' 1.1 (versus `egcs' 1.0.3): ...@@ -202,25 +208,25 @@ In `egcs' 1.1 (versus `egcs' 1.0.3):
`libf2c' environment, even when `libf2c' (now `libg2c') is a `libf2c' environment, even when `libf2c' (now `libg2c') is a
shared library. shared library.
13. `g77' no longer installs the `f77' command and `f77.1' man page in 14. `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' the `/usr' or `/usr/local' heirarchy, even if the `f77-install-ok'
file exists in the source or build directory. See the file exists in the source or build directory. See the
installation documentation for more information. installation documentation for more information.
14. `g77' no longer installs the `libf2c.a' library and `f2c.h' 15. `g77' no longer installs the `libf2c.a' library and `f2c.h'
include file in the `/usr' or `/usr/local' heirarchy, even if the 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 `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
build directory. See the installation documentation for more build directory. See the installation documentation for more
information. information.
15. The `libf2c.a' library produced by `g77' has been renamed to 16. The `libf2c.a' library produced by `g77' has been renamed to
`libg2c.a'. It is installed only in the `gcc' "private" directory `libg2c.a'. It is installed only in the `gcc' "private" directory
heirarchy, `gcc-lib'. This allows system administrators and users heirarchy, `gcc-lib'. This allows system administrators and users
to choose which version of the `libf2c' library from `netlib' they to choose which version of the `libf2c' library from `netlib' they
wish to use on a case-by-case basis. See the installation wish to use on a case-by-case basis. See the installation
documentation for more information. documentation for more information.
16. The `f2c.h' include (header) file produced by `g77' has been 17. The `f2c.h' include (header) file produced by `g77' has been
renamed to `g2c.h'. It is installed only in the `gcc' "private" renamed to `g2c.h'. It is installed only in the `gcc' "private"
directory heirarchy, `gcc-lib'. This allows system administrators directory heirarchy, `gcc-lib'. This allows system administrators
and users to choose which version of the include file from and users to choose which version of the include file from
...@@ -232,11 +238,11 @@ In `egcs' 1.1 (versus `egcs' 1.0.3): ...@@ -232,11 +238,11 @@ In `egcs' 1.1 (versus `egcs' 1.0.3):
than the one built and installed as part of the same `g77' version than the one built and installed as part of the same `g77' version
is picked up. is picked up.
17. During the configuration and build process, `g77' creates 18. During the configuration and build process, `g77' creates
subdirectories it needs only as it needs them. Other cleaning up subdirectories it needs only as it needs them. Other cleaning up
of the configuration and build process has been performed as well. of the configuration and build process has been performed as well.
18. `install-info' now used to update the directory of Info 19. `install-info' now used to update the directory of Info
documentation to contain an entry for `g77' (during installation). documentation to contain an entry for `g77' (during installation).
* Some diagnostics have been changed from warnings to errors, to * Some diagnostics have been changed from warnings to errors, to
...@@ -245,28 +251,28 @@ In `egcs' 1.1 (versus `egcs' 1.0.3): ...@@ -245,28 +251,28 @@ In `egcs' 1.1 (versus `egcs' 1.0.3):
in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
about truncations of various sorts of constants. about truncations of various sorts of constants.
19. Improve compilation of `FORMAT' expressions so that a null byte is 20. Improve compilation of `FORMAT' expressions so that a null byte is
appended to the last operand if it is a constant. This provides a appended to the last operand if it is a constant. This provides a
cleaner run-time diagnostic as provided by `libf2c' for statements cleaner run-time diagnostic as provided by `libf2c' for statements
like `PRINT '(I1', 42'. like `PRINT '(I1', 42'.
20. Improve documentation and indexing. 21. Improve documentation and indexing.
21. The upgrade to `libf2c' as of 1998-06-18 should fix a variety of 22. The upgrade to `libf2c' as of 1998-06-18 should fix a variety of
problems, including those involving some uses of the `T' format problems, including those involving some uses of the `T' format
specifier, and perhaps some build (porting) problems as well. specifier, and perhaps some build (porting) problems as well.
In 0.5.24 and `egcs' 1.1 (versus 0.5.23): In 0.5.24 and `egcs' 1.1 (versus 0.5.23):
========================================= =========================================
22. `g77' no longer produces incorrect code and initial values for 23. `g77' no longer produces incorrect code and initial values for
`EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural" `EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural"
ordering of members vis-a-vis their types, require initial padding. ordering of members vis-a-vis their types, require initial padding.
23. `g77' no longer crashes when compiling code containing 24. `g77' no longer crashes when compiling code containing
specification statements such as `INTEGER(KIND=7) PTR'. specification statements such as `INTEGER(KIND=7) PTR'.
24. `g77' no longer crashes when compiling code such as `J = SIGNAL(1, 25. `g77' no longer crashes when compiling code such as `J = SIGNAL(1,
2)'. 2)'.
* `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary" * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
...@@ -297,9 +303,9 @@ In 0.5.24 and `egcs' 1.1 (versus 0.5.23): ...@@ -297,9 +303,9 @@ In 0.5.24 and `egcs' 1.1 (versus 0.5.23):
* The F90 `System_Clock' intrinsic allows the optional arguments * The F90 `System_Clock' intrinsic allows the optional arguments
(except for the `Count' argument) to be omitted. (except for the `Count' argument) to be omitted.
25. Upgrade to `libf2c' as of 1998-06-18. 26. Upgrade to `libf2c' as of 1998-06-18.
26. Improve documentation and indexing. 27. Improve documentation and indexing.
In previous versions: In previous versions:
===================== =====================
......
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