http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47196
--- Comment #2 from Daniel Franke <dfranke at gcc dot gnu.org> 2011-01-07
12:44:17 UTC ---
(In reply to comment #1)
> c) Build libquadmath but no Fortran REAL(16) support
> If one wants to save a few KiB for Fortran but wants to us libquadmath,
> e.g, with C/C++
This would be
--enable-libquadmath --disable-libquadmath-support ?
Why should disable-libquadmath-support affect Fortran only (besides that the
docs say so)? I'd read this as "build libquadmath, but disable any usage within
gcc".
> d) Don't build libquadmath, but support libquadmath-based REAL(16) in gfortran
> Useful only if the system has already a (compatible) libquadmath
> installation libgfortran then links "-lquadmath" but the user/builder has
> to make sure that it is in the -I and the -L paths.
I think it would make much more sense to set the the libquadmath-support flag
implicitly in most cases, i.e. instead of the currently necessary
--disable-libquadmath --disable-libquadmath-support
a simple
--disable-libquadmath
to turn off everything related to libquadmath would do. If one does not want to
build libquadmath of gcc but have libquadmath support for any(!) language,
library and headers to be user supplied, then use
--disable-libquadmath --enable-libquadmath-support
to override the implicit setting of --enable-libquadmath-support.
Wouldn't that be much more intuitive and easier for the users?
