summaryrefslogtreecommitdiff
path: root/gcc/f/bugs.texi
diff options
context:
space:
mode:
authorlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1998-09-01 09:13:22 +0000
committerlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1998-09-01 09:13:22 +0000
commite21ccb79071fcd2914fbe23f67a83711702af3c8 (patch)
tree02e411b39902b571176f102c526ac5d00da1c083 /gcc/f/bugs.texi
parent2071bbc7085ffd060650f03b86e0dc934abc3ffb (diff)
downloadgcc-e21ccb79071fcd2914fbe23f67a83711702af3c8.tar.gz
* bugs.texi, g77.1, g77.texi, intdoc.in, news.texi: Doc updates from Craig. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@22153 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/f/bugs.texi')
-rw-r--r--gcc/f/bugs.texi23
1 files changed, 13 insertions, 10 deletions
diff --git a/gcc/f/bugs.texi b/gcc/f/bugs.texi
index 436caa49b94..af18d80cdbc 100644
--- a/gcc/f/bugs.texi
+++ b/gcc/f/bugs.texi
@@ -5,7 +5,7 @@
@c The text of this file appears in the file BUGS
@c in the G77 distribution, as well as in the G77 manual.
-@c 1998-07-15
+@c 1998-09-01
@ifclear BUGSONLY
@node Actual Bugs
@@ -73,6 +73,13 @@ and @code{ASSIGN} are involved.
Fixed in @code{egcs} version 1.1.
@item
+@code{g77} fails to warn about
+use of a ``live'' iterative-DO variable
+as an implied-DO variable
+in a @samp{WRITE} or @samp{PRINT} statement
+(although it does warn about this in a @samp{READ} statement).
+
+@item
A compiler crash, or apparently infinite run time,
can result when compiling complicated expressions
involving @code{COMPLEX} arithmetic
@@ -231,17 +238,13 @@ by versions of @code{g77} prior to 0.5.20.
@cindex -fPIC option
@cindex options, -fPIC
@item
-There seem to be some problems with passing constants, and perhaps
-general expressions (other than simple variables/arrays), to procedures
-when compiling on some systems (such as i386) with @samp{-fPIC}, as in
-when compiling for ELF targets.
+@code{g77} sometimes produces invalid assembler code
+when using the @samp{-fPIC} option (such as compiling for ELF targets)
+on the Intel x86 architecture target.
The symptom is that the assembler complains about invalid opcodes.
-This bug is in the gcc back end,
-and it apparently occurs only when
-compiling sufficiently complicated functions @emph{without} the
-@samp{-O} option.
+This bug is in the gcc back end.
-Fixed in @code{egcs} version 1.1.
+Fixed in @code{egcs} version 1.0.2.
@cindex padding
@cindex structures