https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400

--- Comment #12 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Created attachment 61532
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61532&action=edit
Regeneration script

Attached is a shell script, to be placed in libgfortran/, that can be run in
that directory to regenerated all files. If people agree with this approach, I
would then remove the hackish "maintainer mode" code from
libgfortran/Makefile.am, leading to behavior that is identical to other GCC
runtime libraries:
  - maintainer mode regenerates automake/autoconf files
  - regeneration of library code is done manually by developers, through a
script

I think this is definitely more robust. Let me know what you think.

------------

Applying that script should lead to no difference, but it does not :) it leads
to a lot of whitespace changes, demonstrating why we need to change the current
situation is: those whitespace changes, introduced in the m4 files in this
commit

commit 5e918a4db9e4a5bdbeafec6881fa8b22a55d3789
Author: Thomas Koenig <tkoe...@gcc.gnu.org>
Date:   2024-09-24 21:59:10 +0200

            * m4/ifunction.m4: Whitespace fix.

has not been included in the regenerated files, almost one year later.

Reply via email to