From: fx Date: Fri, 20 Nov 1998 09:00:31 +0000 (+0000) Subject: Regenerated. X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0be2599e9fb203e8bcc4b0630af8cdae6949a626;p=platform%2Fupstream%2Flinaro-gcc.git Regenerated. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@23734 138bc75d-0d04-0410-961f-82ee72b054a4 --- diff --git a/gcc/f/BUGS b/gcc/f/BUGS index 2f13628..703393f 100644 --- a/gcc/f/BUGS +++ b/gcc/f/BUGS @@ -44,6 +44,10 @@ port, build, and install `g77', *Note Problems Installing::. Fixed in `egcs' version 1.1. + * `g77' fails to warn about use of a "live" iterative-DO variable as + an implied-DO variable in a `WRITE' or `PRINT' statement (although + it does warn about this in a `READ' statement). + * A compiler crash, or apparently infinite run time, can result when compiling complicated expressions involving `COMPLEX' arithmetic (especially multiplication). @@ -144,11 +148,12 @@ port, build, and install `g77', *Note Problems Installing::. 0.6 should solve most or all remaining problems (such as cross-compiling involving 64-bit machines). - * Maintainers of gcc report that the back end definitely has "broken" - support for `COMPLEX' types. Based on their input, it seems many - of the problems affect only the more-general facilities for gcc's - `__complex__' type, such as `__complex__ int' (where the real and - imaginary parts are integers) that GNU Fortran does not use. + * Maintainers of `gcc' report that the back end definitely has + "broken" support for `COMPLEX' types. Based on their input, it + seems many of the problems affect only the more-general facilities + for gcc's `__complex__' type, such as `__complex__ int' (where the + real and imaginary parts are integers) that GNU Fortran does not + use. Version 0.5.20 of `g77' works around this problem by not using the back end's support for `COMPLEX'. The new option @@ -156,15 +161,13 @@ port, build, and install `g77', *Note Problems Installing::. the same "broken" mechanism as that used by versions of `g77' prior to 0.5.20. - * 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 - `-fPIC', as in when compiling for ELF targets. 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 *without* the `-O' option. + * `g77' sometimes produces invalid assembler code when using the + `-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 `egcs' version 1.1. + Fixed in `egcs' version 1.0.2. * `g77' currently inserts needless padding for things like `COMMON A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'