From c4a920a09799d850ca8a34ac99ce7b4c30d4d58f Mon Sep 17 00:00:00 2001 From: Craig Burley Date: Tue, 2 Mar 1999 21:14:32 +0000 Subject: delete fixed bugs, describe one as appropriate news From-SVN: r25547 --- gcc/f/bugs.texi | 63 ++------------------------------------------------------- 1 file changed, 2 insertions(+), 61 deletions(-) (limited to 'gcc/f/bugs.texi') diff --git a/gcc/f/bugs.texi b/gcc/f/bugs.texi index 961b67b..5be1cb2 100644 --- a/gcc/f/bugs.texi +++ b/gcc/f/bugs.texi @@ -9,7 +9,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-09-01 +@c 1999-03-03 @ifclear BUGSONLY @node Actual Bugs @@ -30,18 +30,8 @@ configure, port, build, and install @code{g77}, @itemize @bullet @item -@code{g77} sometimes crashes when compiling code -containing the construct @samp{CMPLX(0.)} or similar. -This is a @code{gcc} back-end bug. -It can be worked around using @samp{-fno-emulate-complex}, -though that might trigger other, older bugs. -Compiling without optimization is another work-around. - -Fixed in @code{egcs} 1.1. - -@item @c Tim Prince discovered this. -Automatic arrays aren't working on HP-UX systems, +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. @@ -50,34 +40,6 @@ or pointers to them being improperly handled, e.g. not passed to other procedures as they should be. @item -@c Toon Moene discovered these. -Some Fortran code has been found to be miscompiled -by @code{g77} built on @code{gcc} version 2.8.1 -on m68k-next-nextstep3 configurations -when using the @samp{-O2} option. -Even a C function is known to miscompile -on that configuration -when using the @samp{-O2 -funroll-loops} options. - -Fixed in @code{egcs}. - -@cindex DNRM2 -@cindex stack, 387 coprocessor -@cindex ix86 -@cindex x86 -@cindex -O2 -@item -A code-generation bug afflicts -Intel x86 targets when @samp{-O2} is specified -compiling, for example, an old version of -the @samp{DNRM2} routine. -The x87 coprocessor stack is being -mismanaged in cases where assigned @code{GOTO} -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 @@ -85,14 +47,6 @@ 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 -(especially multiplication). - -Fixed in @code{egcs} version 1.1. - -@item Something about @code{g77}'s straightforward handling of label references and definitions sometimes prevents the GBE from unrolling loops. @@ -238,19 +192,6 @@ The new option @samp{-fno-emulate-complex} avoids the work-around, reverting to using the same ``broken'' mechanism as that used by versions of @code{g77} prior to 0.5.20. -@cindex ELF support -@cindex support, ELF -@cindex -fPIC option -@cindex options, -fPIC -@item -@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 @code{gcc} back end. - -Fixed in @code{egcs} version 1.0.2. - @cindex padding @cindex structures @cindex common blocks -- cgit v1.1