Re: Question about reworking internals manual

[Ian Lance Taylor <iant at google dot com>]

Jerry Quinn <jlquinn@optonline.net> writes:

> I'm looking at reworking the sections on trees in the internals manual
> and had a question about how to proceed.  Right now, the information is
> spread between the GENERIC chapter and Trees chapter.  The Trees chapter
> interleaves a lot of C and C++-specific info in with GENERIC info.
>
> What I'd like to do is the following:
>
> 1) Make GENERIC the chapter that talks about the front end
> representation.
>
> 2) Extract those portions of Trees that really talk about GENERIC (a
> large part of it) and integrate that into the GENERIC chapter
>
> 3) Make the remainder part of a section on language-dependent trees
>
> The problem I see is that doing the whole thing at once will make for a
> large hard-to-review patch.  But to do it in steps will result in an
> inconsistent document until a good part of the work is done.
>
> Any suggestions about the best way to proceed?

Personally, I think a large patch will be acceptable for this kind of
thing.

Of course, most of the compiler uses GIMPLE now.  GIMPLE is yet
another IR, although it does still use GENERIC for things like types
and memory addresses.

Thanks for working on this.

Ian