This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, doc, wwwdocs] gfortan+libcpp
- From: Tobias Burnus <burnus at net-b dot de>
- To: Daniel Franke <franke dot daniel at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 22 May 2008 00:34:07 +0200
- Subject: Re: [patch, doc, wwwdocs] gfortan+libcpp
- References: <200805210923.31714.franke.daniel@gmail.com>
Daniel Franke wrote:
As promised, here's the documentation for the changes in preprocessing (plus
something noted by Tobias which I take the liberty to add as well). The
attached patch also includes the wwwdocs-update as requested by FX.
a) Can you add a line break between "<a" and "href=" then the line is
not ~108 but only ~77 Characters long.
+ external preprocessor. The <a href="http://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html";>
b) GCC doc patch is obvious.
c) gfortran.texi: OK
d) invoke.texi:
- "-dM": You write that this will show the predefined macros. I think it should work as in CPP:
"If you use -dM without the -E option, -dM is interpreted as a synonym for -fdump-rtl-mach."
Currently, "-dM" dumps the RTL march. Is is really intended that gfortran w/o -E still shows the predefined macros?
+@item -imultilib @var{dir}
+@opindex @code{imultilib @var{dir}}
+@cindex preprocessing, include path
+Use @var{dir} as a subdirectory of the directory containing target-specific
+C++ headers.
Do we need this -imultilib? And if yes, why?
Otherwise it looks ok.
Tobias