[Fortran, committed] Remove all non-historical mention of (Fortran Front-end) version 0.6.
Toon Moene
toon@moene.indiv.nluug.nl
Fri Feb 1 14:46:00 GMT 2002
L.S.,
I removed all non-historical mention of (future) Fortran Front-end
version 0.6 from the f/ directory.
Make bootstrap (C and Fortran), make check (Fortran only) and make
install on i686-pc-linux-gnu.
Patch attached.
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
-------------- next part --------------
2002-02-01 Toon Moene <toon@moene.indiv.nluug.nl>
* bad.def: Remove non-historical reference to version 0.6.
* bugs.texi: Ditto.
* com.c: Ditto.
* ffe.texi: Ditto.
* proj.h: Ditto.
* g77.texi: Ditto.
*** bad.def.orig Wed Jan 23 21:50:50 2002
--- bad.def Fri Feb 1 20:17:50 2002
*************** LONG("Quadruple-precision floating-point
*** 661,665 ****
SHORT("Quadruple-precision floating-point unsupported"))
FFEBAD_MSG (FFEBAD_TOO_BIG_INIT, WARN,
! LONG("Initialization of large (%B-unit) aggregate area `%A' at %0 currently very slow and takes lots of memory during g77 compile -- to be improved in 0.6")
SHORT("This could take a while (initializing `%A' at %0)..."))
FFEBAD_MSG (FFEBAD_BLOCKDATA_STMT, FATAL,
--- 661,665 ----
SHORT("Quadruple-precision floating-point unsupported"))
FFEBAD_MSG (FFEBAD_TOO_BIG_INIT, WARN,
! LONG("Initialization of large (%B-unit) aggregate area `%A' at %0 slow and takes lots of memory during g77 compile")
SHORT("This could take a while (initializing `%A' at %0)..."))
FFEBAD_MSG (FFEBAD_BLOCKDATA_STMT, FATAL,
*** bugs.texi.orig Sun Jun 10 13:20:25 2001
--- bugs.texi Fri Feb 1 20:18:21 2002
*************** Included with this item is the fact that
*** 121,126 ****
that, on IEEE-754/854-compliant systems, @samp{0./0.} should produce a NaN
and no warning instead of the value @samp{0.} and a warning.
- This is to be fixed in version 0.6, when @code{g77} will use the
- @code{gcc} back end's constant-handling mechanisms to replace its own.
@cindex compiler speed
--- 121,124 ----
*************** For example, @samp{REAL A(1000000)} foll
*** 139,143 ****
takes up way too much time and space, including
the size of the generated assembler file.
- This is to be mitigated somewhat in version 0.6.
Version 0.5.18 improves cases like this---specifically,
--- 137,140 ----
*************** such as the Digital Semiconductor (``DEC
*** 233,238 ****
This problem is largely resolved as of version 0.5.23.
- Version 0.6 should solve most or all remaining problems
- (such as cross-compiling involving 64-bit machines).
@cindex padding
--- 230,233 ----
*** com.c.orig Wed Jan 23 21:50:50 2002
--- com.c Fri Feb 1 20:18:55 2002
*************** ffecom_init_0 ()
*** 11824,11829 ****
(int) TREE_INT_CST_LOW (TYPE_SIZE (TREE_TYPE (null_pointer_node))));
warning ("properly unless they all are 32 bits wide");
! warning ("Please keep this in mind before you report bugs. g77 should");
! warning ("support non-32-bit machines better as of version 0.6");
}
#endif
--- 11824,11828 ----
(int) TREE_INT_CST_LOW (TYPE_SIZE (TREE_TYPE (null_pointer_node))));
warning ("properly unless they all are 32 bits wide");
! warning ("Please keep this in mind before you report bugs.");
}
#endif
*** ffe.texi.orig Wed Nov 17 19:36:40 1999
--- ffe.texi Fri Feb 1 20:21:20 2002
***************
*** 12,19 ****
This chapter describes some aspects of the design and implementation
of the @code{g77} front end.
- Much of the information below applies not to current
- releases of @code{g77},
- but to the 0.6 rewrite being designed and implemented
- as of late May, 1999.
To find about things that are ``To Be Determined'' or ``To Be Done'',
--- 12,15 ----
*************** to facilities outside of @code{g77}, suc
*** 590,598 ****
Names of intrinsics will probably be matchable in any case,
- However, there probably won't be any option to require
- a particular mixed-case appearance of intrinsics
- (as there was for @code{g77} prior to version 0.6),
- because that's painful to maintain,
- and probably nobody uses it.
(How @samp{external SiN; r = sin(x)} would be handled is TBD.
--- 586,589 ----
*** proj.h.orig Sat May 26 11:40:38 2001
--- proj.h Fri Feb 1 20:22:12 2002
*************** the Free Software Foundation, 59 Temple
*** 33,37 ****
#if (GCC_VERSION < 2000)
! #error "You have to use gcc 2.x to build g77 (might be fixed in g77-0.6)."
#endif
--- 33,37 ----
#if (GCC_VERSION < 2000)
! #error "You have to use gcc 2.x to build g77."
#endif
*** g77.texi.orig Mon Dec 17 21:07:47 2001
--- g77.texi Fri Feb 1 20:24:53 2002
*************** for @code{INTEGER*1}, @code{INTEGER*2},
*** 360,365 ****
This inspired Craig to add further support,
even though the resulting support
! would still be incomplete, because version 0.6 is still
! a ways off.
@item
--- 360,364 ----
This inspired Craig to add further support,
even though the resulting support
! would still be incomplete.
@item
*************** Email @email{gnu@@gnu.org} for informati
*** 426,433 ****
Another important way to support work on GNU Fortran is to volunteer
to help out.
- Work is needed on documentation, testing, porting
- to various machines, and in some cases, coding (although major
- changes planned for version 0.6 make it difficult to add manpower to this
- area).
Email @email{@value{email-general}} to volunteer for this work.
--- 425,428 ----
*************** are explicitly left to the implementatio
*** 3562,3569 ****
standards.
GNU Fortran currently tries to be somewhat like a few popular compilers
! (@command{f2c}, Digital (``DEC'') Fortran, and so on), though a cleaner default
! definition along with more
! flexibility offered by command-line options is likely to be offered
! in version 0.6.
This section describes how @command{g77} interprets source lines.
--- 3557,3561 ----
standards.
GNU Fortran currently tries to be somewhat like a few popular compilers
! (@command{f2c}, Digital (``DEC'') Fortran, and so on).
This section describes how @command{g77} interprets source lines.
*************** information to decide how to interpret t
*** 3606,3623 ****
constants.
- Note that this default behavior probably will change for version 0.6,
- when it will presumably be available via a command-line option.
- The default as of version 0.6 is planned to be a ``pure visual''
- model, where tabs are immediately
- converted to spaces and otherwise have no effect, so the way a typical
- user sees source lines produces a consistent result no matter how the
- spacing in those source lines is actually implemented via tabs, spaces,
- and trailing tabs/spaces before newline.
- Command-line options are likely to be added to specify whether all or
- just-tabbed lines are to be extended to 132 or full input-line length,
- and perhaps even an option will be added to specify the truncated-line
- behavior to which some Digital compilers default (and which affects
- the way continued character/Hollerith constants are interpreted).
-
@node Short Lines
@subsection Short Lines
--- 3598,3601 ----
*************** to fund a comprehensive project to creat
*** 8880,8885 ****
@command{g77} doesn't allow intrinsics in @code{PARAMETER} statements.
- This feature is considered to be absolutely vital, even though it
- is not standard-conforming, and is scheduled for version 0.6.
Related to this, @command{g77} doesn't allow non-integral
--- 8858,8861 ----
*************** alleviate this problem).
*** 8985,8990 ****
@command{g77} doesn't fully support @code{INTEGER*2}, @code{LOGICAL*1},
and similar.
- Version 0.6 will provide full support for this very
- popular set of features.
In the meantime, version 0.5.18 provides rudimentary support
for them.
--- 8961,8964 ----
*************** machines will result in automatic suppor
*** 9005,9009 ****
@code{INTEGER*2}, @code{INTEGER*8}, maybe even @code{REAL*16},
and so on.
- This is scheduled for version 0.6.
@node Array Bounds Expressions
--- 8979,8982 ----
*************** item pointed to won't be modified
*** 9616,9621 ****
Probably the best solution for now, but not quite trivial
to implement in the general case.
- Worth considering after @command{g77} 0.6 is considered
- pretty solid.
@end itemize
--- 9589,9592 ----
*************** useful warnings).
*** 10468,10489 ****
@emph{Note:} Currently, the text of the line and a pointer to the column
is printed in most @command{g77} diagnostics.
- Probably, as of version 0.6, @command{g77} will
- no longer print the text of the source line, instead printing
- the column number following the file name and line number in
- a form that GNU Emacs recognizes.
- This change is expected to speed up and reduce the memory usage
- of the @command{g77} compiler.
- @c
- @c Say this when it is true -- hopefully 0.6, maybe 0.7 or later. --burley
- @c
- @c GNU Fortran always tries to compile your program if possible; it never
- @c gratuitously rejects a program whose meaning is clear merely because
- @c (for instance) it fails to conform to a standard. In some cases,
- @c however, the Fortran standard specifies that certain extensions are
- @c forbidden, and a diagnostic @emph{must} be issued by a conforming
- @c compiler. The @option{-pedantic} option tells GNU Fortran to issue warnings
- @c in such cases; @option{-pedantic-errors} says to make them errors instead.
- @c This does not mean that @emph{all} non-ANSI constructs get warnings
- @c or errors.
@xref{Warning Options,,Options to Request or Suppress Warnings}, for
--- 10439,10442 ----
*************** libraries are installed) after building.
*** 11552,11557 ****
Better info on how @command{g77} works and how to port it is needed.
- Much of this should be done only after the redesign planned for
- 0.6 is complete.
@xref{Front End}, which contains some information
--- 11505,11508 ----
More information about the Gcc-patches
mailing list