egcs_1_1_branch egcs/gcc/f/bugs.texi

[craig at jcb-sc dot com]

Committed.  (Decided it was worth sneaking these last bug doc items
into 1.1.2.)

        tq vm, (burley)


1999-03-03  Craig Burley  <craig@jcb-sc.com>

	* bugs.texi: Update with latest bug-fixes from 1.2.
	Remove fixed bugs.
  
*** g77-d/gcc/f/bugs.texi.~1~	Fri Feb 26 15:59:43 1999
--- g77-d/gcc/f/bugs.texi	Wed Mar  3 10:13:51 1999
***************
*** 6,10 ****
  @c in the G77 distribution, as well as in the G77 manual.
  
! @c 1999-02-26
  
  @ifclear BUGSONLY
--- 6,10 ----
  @c in the G77 distribution, as well as in the G77 manual.
  
! @c 1999-03-03
  
  @ifclear BUGSONLY
***************
*** 14,23 ****
  
  This section identifies bugs that @code{g77} @emph{users}
! might run into.
  This includes bugs that are actually in the @code{gcc}
  back end (GBE) or in @code{libf2c}, because those
  sets of code are at least somewhat under the control
! of (and necessarily intertwined with) @code{g77}, so it
! isn't worth separating them out.
  
  For information on bugs that might afflict people who
--- 14,26 ----
  
  This section identifies bugs that @code{g77} @emph{users}
! might run into in this version of @code{g77}.
  This includes bugs that are actually in the @code{gcc}
  back end (GBE) or in @code{libf2c}, because those
  sets of code are at least somewhat under the control
! of (and necessarily intertwined with) @code{g77},
! so it isn't worth separating them out.
! 
! For information on bugs in @emph{other} versions of @code{g77},
! @ref{News,,News About GNU Fortran}.
  
  For information on bugs that might afflict people who
*************** configure, port, build, and install @cod
*** 27,30 ****
--- 30,47 ----
  @itemize @bullet
  @item
+ The @code{IDate} Intrinsic (VXT)
+ fails to return the year in the documented, non-Y2K-compliant range
+ of 0--99,
+ instead returning 100 for the year 2000.
+ 
+ Fixed in @code{egcs} 1.2.
+ 
+ @item
+ Year 2000 (Y2K) compliance information
+ is missing from the documentation.
+ 
+ Fixed in @code{egcs} 1.2.
+ 
+ @item
  @code{g77} crashes when compiling
  I/O statements using keywords that define @code{INTEGER} values,
*************** Fixed in @code{egcs} 1.2.
*** 36,58 ****
  
  @item
! @code{g77} fails to warn about a reference to a function
! when the corresponding @emph{subsequent} function program unit
! disagrees with the reference concerning the type of the function.
  
  Fixed in @code{egcs} 1.2.
  
  @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,
  at least in HP-UX version 10.20.
  Writing into them apparently causes over-writing
--- 53,71 ----
  
  @item
! The @samp{-ax} option is not obeyed when compiling Fortran programs.
! (It is not passed to the @file{f771} driver.)
  
  Fixed in @code{egcs} 1.2.
  
  @item
! @code{g77} fails to warn about a reference to a function
! when the corresponding @emph{subsequent} function program unit
! disagrees with the reference concerning the type of the function.
  
! Fixed in @code{egcs} 1.2.
  
  @item
  @c Tim Prince discovered this.
! 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
*************** e.g. not passed to other procedures as t
*** 63,93 ****
  
  @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 -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
--- 76,79 ----
*************** in a @samp{WRITE} or @samp{PRINT} statem
*** 97,108 ****
  
  @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
--- 83,86 ----
*************** The new option @samp{-fno-emulate-comple
*** 249,265 ****
  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 gcc back end.
- 
- Fixed in @code{egcs} version 1.0.2.
  
  @cindex padding
--- 227,230 ----