Re: g77 configuring, docs (was Re: 970825 Snapshot Available)

[Craig Burley <burley@gnu.ai.mit.edu>]

>I'm tempted to do both a gcc2 -> egcs and f77dev -> egcs merge
>as soon as we get the first release out the door.  I don't think
>we want to introduce too much new code this close to a release.

The patches to fix up the g77 docs are *very* safe, in case
you're wondering -- aside from deleting a gratuitous (and
non-conforming-in-ANSI-C ;-) comma after the last item in
an enum, they affect only the documentation, not the compiler
or the library.  (I'm referring to patches to intdoc.c, intrin.h,
the intdoc.in->intdoc.h renaming, and so on.)

Generally, the fixes I'm making to other parts of g77 are quite
safe too, because I have a release coming up in less than a week,
but only alpha testing and the release itself will "prove" just
how safe these fixes are.

One of the reasons I did the intdoc.in->intdoc.h change *now*,
instead of putting it off, is that I wanted to reduce the size
of future .diff files that would be needed to make the effective
rename.  g77 0.5.20 already had intdoc.h, it is true, but it
was quite small compared to the one pending for 0.5.21, which is
"full" (every single intrinsic documented!), so it seemed like
now was a worthwhile time to switch.

In the larger scale of egcs, I doubt this concern would amount
to much, as I expect the part of a future release->release patch
to rename intdoc.in to intdoc.h will amount to less than 1% of
the total patch.  ;-)

        tq vm, (burley)