This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [RFC] Generalizing the library to arbitrary floating-point modes
Tobi and Francois-Xavier,
I was wondering if it wasn't possible to use some autoconf magic to not generate
those files in cases where there are no corresponding datatypes (i.e. all the
*16.* files on i686). Of course that wouldn't solve the underlying problem
that there are a lot of files being generated, it would only reduce their
number. A possible solution to the problem of generating many files might be
the approach taken in intrinsics/mvbits.c, which could probably also be
replicated in m4, by writing all specific versions into a single file.
(Personally, I find cpp a more readable language than m4.)
Would the way round this be to use the C names for the types, rather
than the kind?
eg. matmul_i.c, matmul_l.c, matmul_ll.c, matmul_f.c, matmul_d.c and
matmul_ld.c, with the C-types matching the functon names. The fortran
front-end could then sort out what kind a long double is and make
adjustments accordingly.
Cheers
Paul