This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Regenerating libgfortran files
- From: François-Xavier Coudert <fxcoudert at gmail dot com>
- To: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
- Date: Sun, 26 Jun 2005 14:58:55 +0200
- Subject: Regenerating libgfortran files
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=kEoCqfsueYyHkwlfa3R70DE1zhVY4op3BcZL0FxIrmVzV8LROQ58J0HvYUzyR7Q+vink7hkzTJbNgq3B+H+Mwsjxcy2FuGLa5F+9kuzJQgNF/m1HZnTPciRm1N2R5vjH77LOHhXI1loDZRJWciCZct34irhcQZMC1QLH+Tjwji4=
- Reply-to: François-Xavier Coudert <fxcoudert at gmail dot com>
Hi all,
First the good news: I have finished regtesting a patch to the
front-end to enable library calls for real(10), real(16) and
integer(16) kinds, and although I thought the front-end would a real
pain to patch, I found it rather easy and there's no regression.
Now, I need to add libgfortran support for these large kinds. I think
I can figure out how to modify the m4 code, but I don't know how to
regenerate the files after that. I read contradictory information
about this process, and whether it is supposed to work or not. Can
someone give me a quick overview of this (pointers to doc welcome).
FX