This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Remove gccbug from bugreport.texi, take 3

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
   source code;

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 missing :-)

Thanks for dealing with this !

Toon Moene - - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77:
GNU Fortran 95: (under construction)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]