This is the mail archive of the
mailing list for the GCC project.
Re: [Patch] Remove gccbug from bugreport.texi, take 3
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- To: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- Cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, Gerald Pfeifer<pfeifer at dbai dot tuwien dot ac dot at>, gcc-patches at gcc dot gnu dot org
- Date: Wed, 14 May 2003 23:22:13 +0200
- Subject: Re: [Patch] Remove gccbug from bugreport.texi, take 3
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <Pine.LNX.email@example.com>
Wolfgang Bangerth wrote:
The Fortran maintainer should be able to advise on what
bugs.html ought to have in the way of Fortran-specific information to
replace this text in the manual.
Toon, that's for you now: in the patch earlier in this thread, I try to
throw out most of the bug reporting instructions from the manuals, and
just refer to bugs.html. The only things fortran-wise that don't seem to
be covered there are
a) the extension of preprocessed fortran sources
b) what to do with INCLUDEd files
Point a) seems to be easily addressed by just adding .f to the list of
extensions of preprocessed files (is this always right, i.e. independent
of whether .F, .fpp, .r, ... was used before preprocessing?), but for b)
we'd need another paragraph, I guess. What's you opinion?
Just give the user the option of:
1. Include the INCLUDEd files in a text editor before submitting the
2. Or submit a tar file with .f source and INCLUDEd files.
It's not that we get tons of bug reports that way - I can deal with that
(I know how to put bug reports into "feedback" mode if something's
Thanks for dealing with this !
Toon Moene - mailto:firstname.lastname@example.org - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc-g95.sourceforge.net/ (under construction)