This is the mail archive of the gcc-patches@gcc.gnu.org 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, fortran] PR28585: Add Fortran 2003 NEW_LINE intrinsic function


FX Coudert wrote:
2. when submitting a patch, we need to know what is the extent of your testing. The usual minimal testing is "built and regression- tested on [build-triplet]", if you have run the testsuite for the freshly built compiler; for doc changes, you probably also want to "make info && make html" to be sure TeXinfo accepts your changes (and mention that).

That's actually insufficient for .texi changes. The info and html files are both produced by makeinfo (that's the name of the program; don't confuse it with "make info", which calls it!) with different flags, and thus it's unlikely that one will find errors that the other doesn't.


However, the dvi files are produced by texi2pdf, which handles a number of things quite differently, and often has errors that don't show up in the html or info production.

Thus, a reasonable minimum amount of testing for the documentation is "make dvi" and either "make info" or "make html". Of course, to be fully certain you can run all three, but if you're only doing two, "dvi" is not the one to drop.

- Brooks


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