summaryrefslogtreecommitdiff
path: root/gcc/f
diff options
context:
space:
mode:
authorburley <burley@138bc75d-0d04-0410-961f-82ee72b054a4>1999-05-06 05:31:40 +0000
committerburley <burley@138bc75d-0d04-0410-961f-82ee72b054a4>1999-05-06 05:31:40 +0000
commitfe6e089c2e1bf40f12f67a93163305ad895eb245 (patch)
tree66a9f10093bbc6ab6092da09be4270fc78f7baec /gcc/f
parentbc4283b72ae0e286d951a969290db119b7c3a17c (diff)
downloadgcc-fe6e089c2e1bf40f12f67a93163305ad895eb245.tar.gz
update derived files
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@26804 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/f')
-rw-r--r--gcc/f/BUGS9
-rw-r--r--gcc/f/NEWS6
2 files changed, 7 insertions, 8 deletions
diff --git a/gcc/f/BUGS b/gcc/f/BUGS
index b40c7aea948..f97b75e3949 100644
--- a/gcc/f/BUGS
+++ b/gcc/f/BUGS
@@ -40,14 +40,7 @@ via `http://egcs.cygnus.com/onlinedocs/g77_bugs.html'. Follow the
port, build, and install `g77', see "Problems Installing" in
`egcs/gcc/f/INSTALL'.
- The following information was last updated on 1999-04-20:
-
- * Automatic arrays possibly 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.
+ The following information was last updated on 1999-05-06:
* `g77' fails to warn about use of a "live" iterative-DO variable as
an implied-DO variable in a `WRITE' or `PRINT' statement (although
diff --git a/gcc/f/NEWS b/gcc/f/NEWS
index 182e3e3b896..9096ebfc6dc 100644
--- a/gcc/f/NEWS
+++ b/gcc/f/NEWS
@@ -110,6 +110,12 @@ In `egcs' 1.2 (versus 1.1.2):
recognized by `g77' as if they ended in `.for' and `.fpp',
respectively.
+ * The order of arguments to the *subroutine* forms of the `CTime',
+ `DTime', `ETime', and `TtyNam' intrinsics has been swapped. The
+ argument serving as the returned value for the corresponding
+ function forms now is the *second* argument, making these
+ consistent with the other subroutine forms of `libU77' intrinsics.
+
* `g77' now warns about a reference to an intrinsic that has an
interface that is not Year 2000 (Y2K) compliant. Also, the
`libg2c' has been changed to increase the likelihood of catching