diff options
| author | Craig Burley <craig@jcb-sc.com> | 1999-03-02 20:30:27 +0000 |
|---|---|---|
| committer | Craig Burley <burley@gcc.gnu.org> | 1999-03-02 15:30:27 -0500 |
| commit | 1d770e13090536d4506a1a2a0e6eb45c2a6edcd3 (patch) | |
| tree | c7b3a1b9befae70636f324d39d41ac9df9e682de | |
| parent | 0aa692fc03e59a5794e4386d7a9e87ec085704a1 (diff) | |
| download | gcc-1d770e13090536d4506a1a2a0e6eb45c2a6edcd3.zip gcc-1d770e13090536d4506a1a2a0e6eb45c2a6edcd3.tar.gz gcc-1d770e13090536d4506a1a2a0e6eb45c2a6edcd3.tar.bz2 | |
clarify g77 bug-reporting docs
From-SVN: r25541
| -rw-r--r-- | gcc/f/ChangeLog | 5 | ||||
| -rw-r--r-- | gcc/f/g77.texi | 35 |
2 files changed, 26 insertions, 14 deletions
diff --git a/gcc/f/ChangeLog b/gcc/f/ChangeLog index 65e502d..d80094d 100644 --- a/gcc/f/ChangeLog +++ b/gcc/f/ChangeLog @@ -1,3 +1,8 @@ +1999-03-02 Craig Burley <craig@jcb-sc.com> + + * g77.texi (Bug Reporting): Clarify whether to use -E. + Clarify other instructions. + 1999-02-25 Richard Henderson <rth@cygnus.com> * lang-specs.h: Define __FAST_MATH__ when appropriate. diff --git a/gcc/f/g77.texi b/gcc/f/g77.texi index 3c62e10..c26daa3 100644 --- a/gcc/f/g77.texi +++ b/gcc/f/g77.texi @@ -14,7 +14,7 @@ @c %**start of header @setfilename g77.info -@set last-up-date 1999-02-25 +@set last-up-date 1999-03-02 @set version-g77 0.5.24 @set email-general egcs@@egcs.cygnus.com @set email-bugs egcs-bugs@@egcs.cygnus.com @@ -13747,23 +13747,30 @@ the bug in the current version of GNU Fortran. @cindex programs, cpp @pindex cpp A complete input file that will reproduce the bug. -If the bug is in the compiler proper (@file{f771}) and -you are using the C preprocessor, run your -source file through the C preprocessor by doing @samp{g77 -E -@var{sourcefile} > @var{outfile}}, then include the contents of -@var{outfile} in the bug report. (When you do this, use the same -@samp{-I}, @samp{-D} or @samp{-U} options that you used in actual + +If your source file(s) require preprocessing +(for example, their names have suffixes like +@samp{.F}, @samp{.fpp}, @samp{.FPP}, and @samp{.r}), +and the bug is in the compiler proper (@file{f771}) +or in a subsequent phase of processing, +run your source file through the C preprocessor +by doing @samp{g77 -E @var{sourcefile} > @var{newfile}}. +Then, include the contents of @var{newfile} in the bug report. +(When you do this, use the same preprocessor options---such as +@samp{-I}, @samp{-D}, and @samp{-U}---that you used in actual compilation.) A single statement is not enough of an example. In order to compile it, -it must be embedded in a complete file of compiler input; and the bug -might depend on the details of how this is done. - -Without a real example one can compile, all anyone can do about your bug -report is wish you luck. It would be futile to try to guess how to -provoke the bug. For example, bugs in register allocation and reloading -frequently depend on every little detail of the function they happen in. +it must be embedded in a complete file of compiler input. +The bug might depend on the details of how this is done. + +Without a real example one can compile, +all anyone can do about your bug report is wish you luck. +It would be futile to try to guess how to provoke the bug. +For example, bugs in register allocation and reloading +can depend on every little detail of the source and include files +that trigger them. @item @cindex included files |